CN115190169A

CN115190169A - Communication method, device and system

Info

Publication number: CN115190169A
Application number: CN202110369739.XA
Authority: CN
Inventors: 陈泽昊; 李永翠; 葛翠丽
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-04-02
Filing date: 2021-04-02
Publication date: 2022-10-14
Also published as: WO2022206617A1

Abstract

The application provides a communication method, a communication device and a communication system, which relate to the technical field of communication. The scheme comprises the following steps: the method comprises the steps that a first network element obtains migration completion time of each first application server in one or more first application servers related to the first network element aiming at an application context of a terminal; the application context is information of a first application of the terminal on a second application server, and the second application server is a server which provides service for the terminal at present; the first network element sends migration completion time of each first application server for the application context of the terminal to the second network element, and the migration completion time of the application context is used for determining a target application server which provides service for the terminal in one or more first application servers.

Description

Communication method, device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method, apparatus, and system.

Background

In the process of running an edge application, when a terminal moves, for example, the terminal between Edge Data Networks (EDNs) and the terminal between local Area Data networks (laddns), the currently serving edge application server may not be able to continue to serve the currently running application, or the currently serving edge application server is not an optimal application server that can serve the terminal, and other edge application servers may be better suited to serve an application client on the terminal, so that a new edge application server (called a target edge application server, T-EAS) needs to be used to replace the currently serving edge application server (called a source edge application server, S-EAS) to serve the terminal, and in the process, the relevant application context needs to be migrated from S-EAS to T-EAS, which may cause the application service to be temporarily suspended or interrupted, thereby affecting the continuity of the service and the user experience.

How to select the target edge application server is an urgent technical problem to be solved in order to make the selected new EAS have as low influence on the application outage as possible so as to better serve the terminal.

Disclosure of Invention

The embodiment of the application provides a communication method, a communication device and a communication system, and the method is used for realizing that the migration completion time of each first application server respectively aiming at the application context of a terminal is referred when the target application server is selected for the terminal, so that the selected target application server can better provide service for the terminal.

In order to achieve the above purpose, the embodiments of the present application provide the following technical solutions:

in a first aspect, an embodiment of the present application provides a communication method, where the method includes: the first network element acquires migration completion time of each first application server in one or more first application servers associated with the first network element for the application context of the terminal. And the first network element sends the migration completion time of each first application server for the application context of the terminal to the second network element. The application context is information of a first application for the terminal on a second application server currently serving the terminal. The migration completion time of each first application server for the application context of the terminal is used for determining a target application server which provides services for the terminal in one or more first application servers.

The embodiment of the present application provides a communication method, in a process of replacing an application server providing a service for a terminal from a second application server to a target application server, an application context of the terminal on the second application server needs to be migrated to the target application server, although one or more first application servers can provide a service for the terminal, since migration completion times required for migrating the application context to each first application server are different, and in an application context migration process, the application service of the terminal is temporarily suspended or interrupted, so that the migration completion times may affect operation of a first application of the terminal, based on which, a first network element in the embodiment of the present application obtains the migration completion times of the application context of each first application server for the terminal. Then, the first network element provides the migration completion time of the application context of each first application server for the terminal to the second network element. Therefore, the second network element can be assisted to select the target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal, the influence of the migration completion time on the running interruption of the application is reduced as much as possible, and the selected target application server can better provide service for the terminal.

In a possible implementation manner of the present application, the acquiring, by a first network element, migration completion time of an application context of a terminal by each first application server in one or more first application servers associated with the first network element includes: the first network element acquires the migration completion time of the application context of each first application server aiming at the terminal from each first application server. In the scheme, the first application server calculates the migration completion time of the application context of each terminal, so that the processing burden of the first network element is reduced.

In a possible implementation manner of the present application, before the first network element obtains, from each first application server, a migration completion time of an application context of each first application server for the terminal, the method provided in an embodiment of the present application further includes: the first network element transmits a first request message for requesting a migration completion time of the application context of the terminal by the first application server to each first application server. To enable the first application server to provide the migration completion time of the application context for the terminal to the first network element based on the request from the first network element.

In one possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element sends one or more of second related information of the second application server and the size of the application context to each first application server. The second relevant information comprises one or more of location information, load information or network conditions of the second application server. By providing the first application server with information (e.g., one or more of second related information of the second application server, size of the application context) for calculating the migration completion time, the process of the first application server obtaining the information by itself is avoided.

It should be noted that the first relevant information/the second relevant information referred to in the embodiments of the present application include any information that has an influence on determining the migration completion time of the application context of the migrated terminal, and are not limited to one or more of location information, load information, or network conditions, and the present application is only described by taking location information, load information, or network conditions as an example.

Optionally, the first request message includes one or more of second related information of the second application server and a size of the application context, so that signaling overhead can be reduced.

Optionally, in a case that the first network element does not provide one or more of the second related information of the second application server and the size of the application context to the first application server, the first application server may obtain the second related information of the second application server and one or more of the size of the application context by itself for calculating the migration completion time, for example, the first application server may obtain one or more of the second related information of the second application server and the size of the application context from the first enabling server or the second application server. Then one or more of the identity of the first enabling server, the identity of the second application server may be included in the first request message. It should be noted that, in the case that the first network element is the second enabling server, it indicates that the terminal is replaced with the enabling server providing the service, and at this time, the first request message carries one or more of the identifier of the first enabling server and the identifier of the second application server. And under the condition that the first network element is the third enabling server, the enabling server for providing the service for the terminal is not replaced, and the first request message carries the identifier of the second application server. The first enabling server is an enabling server which provides services for the terminal before the enabling server is replaced, and the first enabling server is associated with the second application server. The second enabling server is the enabling server which provides service for the terminal after replacement. The third enabling server is the enabling server which provides service for the terminal currently.

In a possible implementation manner of the present application, the acquiring, by a first network element, migration completion time of an application context of a terminal by each first application server in one or more first application servers associated with the first network element includes: the first network element receives a migration completion time of each first application server for the application context of the terminal from the third network element. The third network element is a data analysis network element or an edge configuration server or a policy control network element. And the third network element calculates the migration completion time of each first application server for the application context of the terminal, so that the processing burden of the first network element is reduced.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element transmits a second request message for requesting migration completion time of each first application server for the application context of the terminal to the third network element.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: and the first network element sends one or more of the first relevant information of each first application server, the second relevant information of each second application server and the size of the application context to the third network element. Wherein the first relevant information comprises one or more of location information, load information, or network conditions of the first application server. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. This avoids the third network element collecting the information itself.

In a possible implementation manner of the present application, one or more of the first related information of each first application server, the second related information of each second application server, and the size of the application context is carried in the second request message, so that the signaling overhead can be reduced.

It should be noted that, in a case where the first network element does not provide one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context to the third network element, the third network element may obtain the first related information of each first application server from each first application server, or obtain one or more of the second related information of the second application server and the size of the application context from the first enabling server or the second application server, according to the identifier of each first application server provided by the first network element in the second request message. One or more of an identification of each first application server, an identification of the first enabling server, and an identification of the second application server may be included in the second request message.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: and the first network element acquires one or more items of second relevant information and the size of the application context of the second application server.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element obtains first relevant information of each first application server.

In a possible implementation manner of the present application, the acquiring, by a first network element, migration completion time of an application context of a terminal by each first application server in one or more first application servers associated with the first network element includes: the first network element acquires one or more of first related information of each first application server, second related information of the second application server, and the size of the application context. And the first network element determines the migration completion time of the application context of each first application server aiming at the terminal according to one or more of the first relevant information of each first application server, the second relevant information of the second application server and the size of the application context. The scheme can realize that the first network element calculates the migration completion time of each application context of each first application server aiming at the terminal according to the acquired information.

In a possible implementation manner of the present application, the obtaining, by the first network element, one or more of the second relevant information of the second application server and the size of the application context includes: the first network element receives one or more of second relevant information, size of the application context from the second application server and/or a second application server of the first enabled server. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, before the first network element receives one or more of second relevant information of the second application server from the second application server and/or the first enabling server, and a size of the application context, the method provided in an embodiment of the present application further includes: the first network element sends a third request message for requesting one or more of second related information of the second application server, and the size of the application context to the second application server and/or the first enabling server.

In a possible implementation manner of the present application, the acquiring, by the first network element, the first relevant information of each first application server includes: the first network element sends a fourth request message for requesting the first relevant information of the first application server to each first application server. The first network element receives respective first related information of each first application server.

In a possible implementation manner of the present application, in a case that the first network element is a second enabling server, the method provided in the embodiment of the present application further includes: the first network element receives an identification of a first enabling server from a second network element, the first enabling server being associated with a second application server.

In a possible implementation manner of the present application, the first network element is a third enabling server or a second enabling server, and the second network element is an Edge Enabled Client (EEC) or a second application server. Specifically, in a scenario where the replacement of the enabling server occurs, the first network element may be, for example, a second enabling server, and the second network element is an EEC. The first enabling server is the enabling server which provides the server for the terminal before the enabling server is replaced. The second enabling server is the enabling server which provides service for the terminal after replacement. In a scenario that the enabling server is not replaced for the terminal, the first network element is a third enabling server, the second network element is an EEC, and the third enabling server is the enabling server currently accessed by the terminal. Alternatively, in a scenario in which the enabling server is replaced for the terminal, the first network element may be, for example, the first enabling server, and the second network element may be the second application server.

In a second aspect, an embodiment of the present application provides a communication method, including: the first network element obtains the second information. The second information includes one or more of first related information of each of one or more first application servers associated with the first network element, second related information of the second application server, and a size of the application context. The application context is information of a first application of the terminal on a second application server which currently provides services for the terminal. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. The first relevant information includes one or more of location information, load information, or network conditions of the first application server. And the first network element sends second information to the second network element, wherein the second information is used for determining a target application server which provides services for the terminal in one or more first application servers.

The embodiment of the application provides a communication method, in the process of replacing an application server providing service for a terminal from a second application server to a target application server, an application context of the terminal on the second application server needs to be migrated to the target application server, although one or more first application servers can provide service for the terminal, since there is a difference in migration completion time required for migrating the application context to each first application server, since the application service of the terminal is temporarily suspended or interrupted in the application context migration process, the migration completion time may affect the operation of a first application of the terminal, and based on this, a first network element obtains second information and provides the second information to a second network element. Since the second information comprises one or more of first related information of each of the one or more first application servers associated with the first network element, second related information of the second application server, and size of the application context. And the content included in the second information may be used to determine the migration completion time of the application context of each first application server for the terminal, so that after the first network element provides the second information to the second network element, the second network element is facilitated to determine, according to the second information, a target application server for providing a service for the terminal from the one or more first application servers.

In a possible implementation manner of the present application, the obtaining, by the first network element, one or more of the second relevant information of the second application server and the size of the application context includes: the first network element receives one or more of second related information of a second application server from the second application server or a first enabling server, the first enabling server being associated with the second application server, and a size of the application context.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: and the first network element sends a third request message to the second application server or the first enabling server. The third request message is used for requesting one or more of second related information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the acquiring, by the first network element, the first relevant information of each first application server includes: the first network element sends a fourth request message to each first application server. The fourth request message is for requesting the first relevant information of the first application server. The first network element receives respective first related information of each first application server.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element receives identification information of the first enabling server from the second network element. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, before the first network element obtains the first related information of each first application server, the method provided in the embodiment of the present application further includes: the first network element receives a fifth request message sent by the first enabling server, wherein the fifth request message is used for requesting first relevant information of at least one second application server associated with the first network element.

In a possible implementation manner of the present application, the fifth request message includes first indication information, where the first indication information is used to indicate that the first network element provides the first related information of each second application server associated with the first network element.

In a third aspect, an embodiment of the present application provides a communication method, where the method includes: the second network element receives a migration completion time of an application context of each of the one or more first application servers for the terminal from the first network element. And the second network element determines a target application server for providing service for the terminal from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

In a possible implementation manner of the present application, before the second network element receives, from the first network element, a migration completion time of each of the one or more first application servers of the first network element for the application context of the terminal, a method provided in an embodiment of the present application further includes: and the second network element sends the identification of the first enabling server to the first network element, and the first enabling server is associated with the second application server. This is so that the first network element determines the enabling server that previously served the terminal.

In a fourth aspect, an embodiment of the present application provides a communication method, where the method includes: the second network element receives second information from the first network element, wherein the second information includes one or more of first related information of each of the one or more first application servers, second related information of the second application server, and a size of the application context. The application context is information of a first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present; the second relevant information comprises one or more of location information, load information, or network conditions of the second application server; the first relevant information comprises one or more of location information, load information, or network conditions of the first application server; and the second network element determines a target application server from the one or more first application servers according to the second information, wherein the target application server is used for providing services for the terminal.

In a possible implementation manner of the present application, before the second network element receives the second information, the method provided in the embodiment of the present application further includes: and the second network element sends the identification information of the first enabling server to the first network element. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, the determining, by the second network element, the target application server from the one or more first application servers according to the second information includes: and the second network element determines the migration completion time of the application context of each first application server aiming at the terminal according to the second information. And the second network element determines a target application server from the one or more first application servers according to the migration completion time of the application context of each first application server for the terminal.

In a fifth aspect, an embodiment of the present application provides a communication method, including: the method comprises the steps that a first application server determines the migration completion time of an application context of a terminal aiming at the first application server, wherein the application context is information of a first application of the terminal on a second application server which provides service for the terminal at present; the first application server sends the migration completion time of the application context of the first application server for the terminal to the first network element.

In one possible implementation manner of the present application, the determining, by the first application server, a migration completion time of the application context of the terminal by the first application server includes: the first application server acquires one or more items of second related information of the second application server and the size of the application context. The first application server determines the migration completion time of the application context of the terminal according to one or more of the first relevant information of the first application server, the second relevant information of the second application server and the size of the application context.

In a possible implementation manner of the present application, before the first application server determines a migration completion time of the application context of the terminal by the first application server, the method provided in the embodiment of the present application may further include: the first application server receives a first request message from a first network element. The first request message is used for requesting the migration completion time of the application context of the terminal by the first application server.

In a possible implementation manner of the present application, the obtaining, by the first application server, one or more of the second relevant information of the second application server and the size of the application context includes: the first application server obtains one or more of second related information of the second application server and the size of the application context from the first network element or the second application server or the first enabling server. For example, the first application server may obtain the identification information of the second application server or the first enabling server from the first network element. For example, the first request message carries an identifier of the second application server or an identifier of the first enabling server. Specifically, in a scenario where the enabling server is replaced for the terminal, the first request message carries an identifier of the second application server and/or an identifier of the first enabling server. In a scenario of replacing an enabling server for a terminal, the first request message carries an identifier of the second application server, and at this time, the first network element is a third enabling server.

In a possible implementation manner of the present application, the obtaining, by the first application server, one or more of second relevant information of the second application server and a size of the application context from the first network element, the second application server, or the first enabling server includes: the first application server receives one or more of second relevant information, size of the application context from the first network element or the second application server of the first enabled server. The information may be actively sent to the first application server by the first network element or the second application server or the first enabling server, or may be sent to the first application server again based on the trigger of the first application server.

In a possible implementation manner of the present application, the first application server receives one or more of the second relevant information and the size of the application context from the first network element, specifically, the first request message includes one or more of the second relevant information and the size of the application context of the second application server.

In one possible implementation manner of the present application, the first application server receives one or more of the second related information and the size of the application context from the second application server or the second application server of the first enabling server, and may further include the first application server sending a request message for requesting one or more of the second related information and the size of the application context of the second application server to the second application server or the first enabling server.

In a sixth aspect, an embodiment of the present application provides a communication method, including: the third network element determines a migration completion time of an application context for the terminal of each of the one or more first application servers, the application context being information of a first application for the terminal on a second application server currently serving the terminal. And the third network element sends the migration completion time of each first application server for the application context of the terminal to the first network element.

In one possible implementation manner of the present application, the determining, by the third network element, a migration completion time of an application context of the terminal for each of the one or more first application servers includes: the third network element obtains the first related information of each first application server, and/or the third network element obtains one or more of the second related information of the second application server and the size of the application context. The third network element is based on one or more of the following information: and determining the migration completion time of the application context of each first application server aiming at the terminal according to the first relevant information of each first application server, the second relevant information of each second application server and the size of the application context.

In a possible implementation manner of the present application, before the third network element determines a migration completion time of an application context of a terminal for each of one or more first application servers, the method provided in an embodiment of the present application further includes: the third network element receives one or more of the first relevant information of each first application server, the second relevant information of the second application server, and the size of the application context from the first network element. Wherein the first relevant information comprises one or more of location information, load information, or network conditions of the first application server. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. This avoids the third network element collecting the information itself.

In a possible implementation manner of the present application, before the third network element determines a migration completion time of an application context of a terminal for each of one or more first application servers, the method provided in an embodiment of the present application further includes: the third network element receives a second request message from the first network element, the second request message being used for requesting migration completion time of the application context of the terminal by each of the one or more first application servers. For example, the second request message carries one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context.

It should be noted that, in addition to acquiring one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context from the first network element, the third network element may collect the respective first related information of each first application server from each first application server, and at this time, the first network element may provide the identifier of each first application server to the third network element. The third network element may also obtain one or more of the second relevant information of the second application server and the size of the application context from the second application server or the first enabling server, and at this time, the third network element may obtain the identifier of the second application server or the identifier of the first enabling server from the first network element, which is not limited in this embodiment of the present application.

In a seventh aspect, an embodiment of the present application provides a communication apparatus, which may implement the method in the first aspect or any possible implementation manner of the first aspect, and therefore may also implement the beneficial effects in the first aspect or any possible implementation manner of the first aspect. The communication device may be the first network element, or may be a device that supports the first network element to implement the method in the first aspect or any possible implementation manner of the first aspect, for example, a chip applied in the first network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. For example, the processing unit is configured to obtain a migration completion time of each of the one or more first application servers associated with the first network element for the application context of the terminal. The communication unit transmits, to the second network element, a migration completion time of each of the first application servers for the application context of the terminal. The application context is information for a first application for the terminal on a second application server that is currently serving the terminal. The migration completion time of each first application server for the application context of the terminal is used for determining a target application server which provides services for the terminal in one or more first application servers.

In a possible implementation manner of the present application, the processing unit is configured to obtain, from each first application server, a migration completion time of an application context of each first application server for the terminal through the communication unit.

In one possible implementation manner of the present application, the communication unit is configured to send, to each first application server, a first request message for requesting a migration completion time of an application context of the terminal by the first application server.

In one possible implementation manner of the present application, the communication unit is configured to send one or more of second related information of the second application server and a size of the application context to each first application server. The second relevant information includes one or more of location information, load information, or network conditions of the second application server.

Optionally, in a case that the first network element does not provide one or more of the second related information of the second application server and the size of the application context to the first application server, the first application server may obtain the second related information of the second application server and one or more of the size of the application context by itself for calculating the migration completion time, for example, the first application server may obtain one or more of the second related information of the second application server and the size of the application context from the first enabling server or the second application server. Then one or more of the identity of the first enabling server, the identity of the second application server may be included in the first request message. It should be noted that, in the case that the first network element is the second enabling server, the enabling server that provides services for the terminal is changed from the first enabling server to the second enabling server, and at this time, the first request message carries one or more of the identifier of the first enabling server and the identifier of the second application server. And under the condition that the first network element is the third enabling server, the enabling server for providing the service for the terminal is not replaced, and the first request message carries the identifier of the second application server. The first enabling server is an enabling server for providing services for the terminal before replacement, the first enabling server is associated with the second application server, and the second enabling server is an enabling server for providing services for the terminal after replacement of the enabling server. The third enabling server is the enabling server which provides service for the terminal currently.

In a possible implementation manner of the present application, the processing unit is configured to receive, through the communication unit, a migration completion time of an application context of each first application server for the terminal from the third network element. The third network element is a data analysis network element or an edge configuration server or a policy control network element.

In a possible implementation manner of the present application, the communication unit is further configured to send, to the third network element, a second request message for requesting a migration completion time of the application context of each first application server for the terminal.

In a possible implementation manner of the present application, the communication unit is further configured to send, by the first network element, to the third network element, one or more of the first relevant information of each first application server, the second relevant information of the second application server, and the size of the application context. Wherein the first relevant information comprises one or more of location information, load information, or network conditions of the first application server.

In a possible implementation manner of the present application, one or more of the first relevant information of each first application server, the second relevant information of each second application server, and the size of the application context are carried in the second request message, so that the signaling overhead can be reduced.

In a possible implementation manner of the present application, the communication unit is further configured to obtain one or more of second relevant information of the second application server and a size of the application context.

In a possible implementation manner of the present application, the communication unit is further configured to obtain first related information of each first application server.

In a possible implementation manner of the present application, the processing unit is configured to obtain, through the communication unit, one or more of first relevant information of each first application server, second relevant information of the second application server, and a size of the application context. And the processing unit is used for determining the migration completion time of the application context of each first application server aiming at the terminal according to one or more items of the first relevant information of each first application server, the second relevant information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the communication unit is specifically configured to receive one or more of second related information from the second application server and/or the second application server of the first enabling server, and a size of the application context. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, the communication unit is further configured to send, to the second application server and/or the first enabling server, a third request message for requesting one or more of the second relevant information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the communication unit is further configured to send, to each first application server, a fourth request message for requesting the first relevant information of the first application server. The first network element receives respective first related information of each first application server.

In a possible implementation manner of the present application, in a case that the first network element is the second enabling server, the communication unit is further configured to receive, by the first network element, an identifier of the first enabling server from the second network element, where the first enabling server is associated with the second application server.

In a possible implementation manner of the present application, the first network element is a third enabling server or a second enabling server, and the second network element is an Edge Enabled Client (EEC) or a second application server. Specifically, in a scenario where an enabling server for providing services for the terminal is replaced, the first network element may be, for example, a second enabling server, and the second network element is an EEC. The first enabling server is the enabling server which provides the server for the terminal before replacement. The second enabling server is the enabling server which provides service for the terminal after replacement. In a scenario that the enabling server for providing service for the terminal is not replaced, the first network element is a third enabling server, the second network element is an EEC, and at this time, the third enabling server is the enabling server currently accessed by the terminal. Alternatively, in a scenario where an enabling server for serving the terminal is replaced, the first network element may be, for example, a first enabling server, and the second network element may be a second application server.

Illustratively, when the communication device is a chip or a system of chips within the first network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, etc. The processing unit executes the instructions stored by the storage unit to cause the first network element to implement the first aspect or one of the possible implementations of the first aspect. The storage unit may be a storage unit (e.g., a register, a cache, etc.) within the chip, or a storage unit (e.g., a read-only memory, a random access memory, etc.) external to the chip within the first network element.

In an eighth aspect, embodiments of the present application provide a communication apparatus, which may implement the method in the second aspect or any possible implementation manner of the second aspect, and therefore may also achieve the beneficial effects in the second aspect or any possible implementation manner of the second aspect. The communication device may be the first network element, or may be a device that supports the first network element to implement the second aspect or the method in any possible implementation manner of the second aspect, for example, a chip applied in the first network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. And a communication unit for acquiring the second information. The second information includes one or more of first related information of each of one or more first application servers associated with the first network element, second related information of the second application server, and a size of the application context. The application context is information of a first application of the terminal on a second application server which currently provides services for the terminal. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. The first relevant information includes one or more of location information, load information, or network conditions of the first application server. And the communication unit is further used for sending second information to the second network element, wherein the second information is used for determining a target application server which provides services for the terminal in one or more first application servers.

In a possible implementation manner of the present application, the obtaining, by the first network element, one or more of the second relevant information of the second application server and the size of the application context includes: a communication unit for acquiring second information, comprising: a communication unit, configured to receive one or more of second related information of the second application server or the first enabled server and a size of the application context. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, the communication unit is further configured to send a third request message to the second application server or the first enabling server. The third request message is used for requesting one or more of second related information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the communication unit is further configured to send a fourth request message to each first application server. The fourth request message is for requesting the first relevant information of the first application server. And the communication unit is used for receiving the respective first related information of each first application server.

In a possible implementation manner of the present application, the communication unit is further configured to receive identification information of the first enabling server from the second network element. The first enabling server is associated with a second application server.

In a possible implementation manner of the present application, the communication unit is further configured to receive a fifth request message sent from the first enabling server, where the fifth request message is used to request the first relevant information of the at least one second application server associated with the first network element.

Illustratively, when the communication device is a chip or a system of chips within the first network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, or the like. The processing unit executes the instructions stored by the storage unit to cause the first network element to implement a communication method as described in the second aspect or any one of the possible implementations of the second aspect. The storage unit may be a storage unit (e.g., a register, a cache, etc.) within the chip, or a storage unit (e.g., a read-only memory, a random access memory, etc.) external to the chip within the first network element.

In a ninth aspect, embodiments of the present application provide a communication apparatus, which may implement the method in any possible implementation manner of the third aspect or the third aspect, and therefore may also implement the beneficial effects in any possible implementation manner of the third aspect or the third aspect. The communication device may be a second network element, or may be a device that supports the second network element to implement the third aspect or the method in any possible implementation manner of the third aspect, for example, a chip applied in the second network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. A communication unit, configured to receive a migration completion time of an application context of a terminal for each of one or more first application servers from a first network element. The communication unit is used for determining a target application server for providing service for the terminal from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

In a possible implementation manner of the present application, the communication unit is further configured to send identification information of a first enabling server to the first network element, where the first enabling server is associated with the second application server.

Illustratively, when the communication device is a chip or a system of chips within the second network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, or the like. The processing unit executes the instructions stored in the storage unit to enable the second network element to implement one of the communication methods described in the third aspect or any one of the possible implementation manners of the third aspect. The storage unit may be a storage unit (e.g., a register, a buffer, etc.) in the chip, or a storage unit (e.g., a read-only memory, a random access memory, etc.) in the second network element, which is located outside the chip.

In a tenth aspect, embodiments of the present application provide a communication apparatus, which may implement the method in the fourth aspect or any possible implementation manner of the fourth aspect, and therefore can also achieve the beneficial effects in the fourth aspect or any possible implementation manner of the fourth aspect. The communication device may be a second network element, or may be a device that supports the second network element to implement the fourth aspect or the method in any possible implementation manner of the fourth aspect, for example, a chip applied in the second network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. A communication unit, configured to receive second information from the first network element, where the second information includes one or more of first related information of each of the one or more first application servers, second related information of the second application server, and a size of the application context. The application context is information of a first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present; the second relevant information comprises one or more of location information, load information, or network conditions of the second application server; the first relevant information comprises one or more of location information, load information, or network conditions of the first application server; and the processing unit is used for determining a target application server from the one or more first application servers according to the second information, and the target application server is used for providing services for the terminal.

In a possible implementation manner of the present application, the communication unit is further configured to send, to the first network element, identification information of the first enabling server. The first enabling server is associated with a second application server.

In a possible implementation manner of the application, the processing unit is configured to determine, according to the second information, a migration completion time of the application context of each first application server for the terminal. And the processing unit is used for determining a target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

Illustratively, when the communication device is a chip or a system of chips within the second network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, or the like. The processing unit executes the instructions stored by the storage unit to cause the second network element to implement a communication method as described in the fourth aspect or any one of the possible implementations of the fourth aspect. The storage unit may be a storage unit (e.g., a register, a cache, etc.) within the chip, or a storage unit (e.g., a read-only memory, a random access memory, etc.) external to the chip within the second network element.

In an eleventh aspect, embodiments of the present application provide a communication apparatus, which may implement the method in any possible implementation manner of the fifth aspect or the fifth aspect, and therefore, may also implement the beneficial effects in any possible implementation manner of the fifth aspect or the fifth aspect. The communication device may be the first application server, or may be a device supporting the first application server to implement the method of the fifth aspect or any possible implementation manner of the fifth aspect, for example, a chip applied to the first application server. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. The processing unit is used for determining the migration completion time of the application context of the terminal aiming at the first application server, wherein the application context is information of the first application aiming at the terminal on a second application server which provides service for the terminal currently. A communication unit, configured to send, to the first network element, a migration completion time of an application context of the terminal by the first application server.

In a possible implementation manner of the present application, the communication unit is configured to obtain one or more of second relevant information of the second application server and a size of the application context. And the processing unit is used for determining the migration completion time of the application context of the terminal by the first application server according to one or more of the first relevant information of the first application server, the second relevant information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the communication unit is further configured to receive a first request message from the first network element. The first request message is used for requesting the migration completion time of the application context of the terminal by the first application server.

In a possible implementation manner of the present application, the communication unit is configured to obtain one or more of second relevant information of the second application server and a size of the application context from the first network element or the second application server or the first enabling server. For example, the first application server may obtain the identification information of the second application server or the first enabling server from the first network element. For example, the first request message carries an identifier of the second application server or an identifier of the first enabling server. Specifically, in a scenario where an enabling server providing a service for a terminal is replaced, the first request message carries an identifier of the second application server and/or an identifier of the first enabling server. In a scenario that an enabling server providing services for the terminal is not replaced, the first request message carries an identifier of the second application server, and at this time, the first network element is a third enabling server.

In a possible implementation manner of the present application, the communication unit is configured to receive one or more of second related information and a size of an application context from the first network element or the second application server of the first enabled server. The information may be actively sent to the first application server by the first network element or the second application server or the first enabling server, or may be sent to the first application server again based on the trigger of the first application server.

In a possible implementation manner of the present application, the communication unit is configured to receive one or more of the second relevant information and the size of the application context from the first network element, specifically, the first request message includes one or more of the second relevant information of the second application server and the size of the application context.

In a possible implementation manner of the present application, the communication unit is further configured to send, to the second application server or the first enabling server, a request message for requesting one or more of the second related information of the second application server and the size of the application context.

Illustratively, when the communication device is a chip or a chip system within the first application server, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, etc. The processing unit executes the instructions stored by the storage unit to cause the first application server to implement a communication method as described in the fifth aspect or any one of the possible implementations of the fifth aspect. The storage unit may be a storage unit (e.g., a register, a cache, etc.) within the chip, or may be a storage unit (e.g., a read-only memory, a random access memory, etc.) within the first application server that is external to the chip.

In a twelfth aspect, embodiments of the present application provide a communication apparatus, which may implement the method in the sixth aspect or any possible implementation manner of the sixth aspect, and therefore may also achieve the beneficial effects in the sixth aspect or any possible implementation manner of the sixth aspect. The communication device may be a third network element, or may be a device that supports the third network element to implement the method in the sixth aspect or any possible implementation manner of the sixth aspect, for example, a chip applied in the third network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

An example, an embodiment of the present application provides a communication apparatus, including: the device comprises a communication unit and a processing unit, wherein the processing unit is used for processing information. The processing unit is used for determining the migration completion time of the application context of the terminal aiming at each first application server in one or more first application servers, and the application context is information of the first application aiming at the terminal on a second application server which provides service for the terminal currently. A communication unit, configured to send, to the first network element, a migration completion time of each first application server for an application context of the terminal.

In a possible implementation manner of the present application, the communication unit is configured to obtain the first related information of each first application server, and/or the communication unit is configured to obtain one or more of the second related information of the second application server and a size of the application context. A processing unit to determine one or more of the following information: the first relevant information of each first application server, the second relevant information of each second application server and the size of the application context determine the migration completion time of the application context of each first application server aiming at the terminal.

In a possible implementation manner of the present application, the communication unit is further configured to receive one or more of first relevant information of each first application server, second relevant information of the second application server, and a size of the application context from the first network element. Wherein the first relevant information comprises one or more of location information, load information, or network conditions of the first application server. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. This avoids the third network element collecting the information itself.

In a possible implementation manner of the present application, the communication unit is further configured to receive, by the third network element, a second request message from the first network element, where the second request message is used to request a migration completion time of an application context of the terminal for each of the one or more first application servers. For example, the second request message carries one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context.

It should be noted that, in addition to acquiring one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context from the first network element, the communication unit may collect the respective first related information of each first application server from each first application server, and then the communication unit may provide the identification of each first application server to the third network element. The communication unit is further configured to obtain, from the second application server or the first enabling server, one or more of second related information of the second application server and a size of the application context, where the communication unit may also be configured to obtain, from the first network element, an identifier of the second application server or an identifier of the first enabling server, which is not limited in this embodiment of the present application.

In a thirteenth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the first aspect to the first aspect.

In a fourteenth aspect, the present application provides a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the second aspect to the second aspect.

In a fifteenth aspect, the present application provides a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the third aspect to the third aspect.

In a sixteenth aspect, the present application provides a computer-readable storage medium, in which a computer program or an instruction is stored, and when the computer program or the instruction runs on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the fourth aspect to the fourth aspect.

In a seventeenth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the fifth aspect to the fifth aspect.

In an eighteenth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the sixth aspect to the sixth aspect.

In a nineteenth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the method of communication described in the first aspect or in the various possible implementations of the first aspect.

In a twentieth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the second aspect or one of the communication methods described in the various possible implementations of the second aspect.

In a twenty-first aspect, embodiments of the present application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform the third aspect or one of the communication methods described in the various possible implementations of the third aspect.

In a twenty-second aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform a method of communication as described in the fourth aspect or in various possible implementations of the fourth aspect.

In a twenty-third aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform a communication method as described in the fifth aspect or in various possible implementations of the fifth aspect.

In a twenty-fourth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform a communication method described in the various possible implementations of the sixth aspect or the sixth aspect.

In a twenty-fifth aspect, embodiments of the present application provide a communications device for implementing various methods in various possible designs of any one of the first to sixth aspects described above. The communication device may be the first network element, or a device including the first network element, or a component (e.g., a chip) applied in the first network element. Alternatively, the communication device may be the second network element or a device including the second network element, or the communication device may be a component (e.g., a chip) applied in the second network element. The communication device may be the third network element, or a device including the third network element, or a component (e.g., a chip) applied in the third network element. Or the communication device may be the first application server, or a device including the first application server, or a component (e.g., a chip) applied to the first application server. The communication device comprises modules and units corresponding to the implementation of the method, and the modules and units can be implemented by hardware, software or hardware to execute corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

In a twenty-sixth aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor and a communication interface. Wherein the processor executes computer-executable instructions or programs stored in the communication device when the communication device is run to cause the communication device to perform a method as in any one of the various possible designs of any one of the first, second, third, fourth, fifth, or sixth aspects described above. For example, the communication device may be the first network element, or a component applied in the first network element. For example, the communication device may be a third network element, or a component applied in a third network element. For example, the communication device is a second network element, or a component applied in a second network element. For example, the communication device may be the first application server, or a component applied in the first application server.

It should be understood that the communication device described in the twenty-sixth aspect may further include: a bus and a memory for storing code and data. Optionally, the at least one processor communication interface and the memory are coupled to each other.

In a twenty-seventh aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer executable instructions or programs stored in the memory when the communication device is run to cause the communication device to perform a method as set forth in any one of the various possible designs of the first aspect or any one of the first aspects. For example, the communication device may be the first network element or a chip applied in the first network element.

In a twenty-eighth aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer-executable instructions or programs stored in the memory when the communication apparatus is run to cause the communication apparatus to perform a method as set forth in any of the various possible implementations of the second aspect or any of the second aspects above. For example, the communication device may be the first network element or a chip applied in the first network element.

In a twenty-ninth aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer executable instructions or programs stored in the memory when the communication device is run to cause the communication device to perform a method as set forth in any of the various possible designs of the third aspect or the any of the third aspects. For example, the communication device may be the second network element or a chip applied in the second network element.

In a thirtieth aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer executable instructions or programs stored in the memory when the communication device is run to cause the communication device to perform the method of any of the various possible designs of the fourth aspect or any of the fourth aspects as described above. For example, the communication device may be the second network element or a chip applied in the second network element.

In a thirty-first aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer-executable instructions or programs stored in the memory when the communication device is run to cause the communication device to perform the method of any of the various possible designs of the fifth aspect or any of the fifth aspects as described above. For example, the communication device may be the first application server, or a chip applied in the first application server.

In a thirty-second aspect, an embodiment of the present application provides a communication apparatus, including: at least one processor. Wherein at least one processor is coupled to a memory, the processor executing computer executable instructions or programs stored in the memory when the communication device is run to cause the communication device to perform a method as set forth in any one of the various possible designs of the sixth aspect or the sixth aspect. For example, the communication device may be a third network element or a chip applied in the third network element.

It should be understood that the memory described in any of the twenty-sixth aspect to the thirty-second aspect may also be replaced by a storage medium, which is not limited by the embodiment of the present application. In a possible implementation, the memory described in any of the twenty-sixth to thirty-second aspects may be a memory internal to the communication device, but of course, the memory may also be external to the communication device, but the at least one processor may still execute the computer-executable instructions or programs stored in the memory.

In a thirty-third aspect, an embodiment of the present application provides a communication apparatus, which includes one or more modules, configured to implement the method of any one of the first, second, third, fourth, fifth, and sixth aspects described above, where the one or more modules may correspond to respective steps of the method of any one of the first, second, third, fourth, fifth, and sixth aspects described above.

In a thirty-fourth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement the first aspect or one of the communication methods described in the various possible implementations of the first aspect. The communication interface is used for communicating with other modules outside the chip.

In a thirty-fifth aspect, embodiments of the present application provide a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the various possible implementations of the second aspect or the second aspect. The communication interface is used for communicating with other modules outside the chip.

In a sixteenth aspect, the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the third aspect or various possible implementations of the third aspect. The communication interface is used for communicating with other modules outside the chip.

In a thirty-seventh aspect, the present application provides a chip, which includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the fourth aspect or various possible implementations of the fourth aspect. The communication interface is used for communicating with other modules outside the chip.

In a thirty-eighth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the various possible implementations of the fifth aspect or the fifth aspect. The communication interface is used for communicating with other modules outside the chip.

In a thirty-ninth aspect, the present application provides a chip, which includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the sixth aspect or the various possible implementations of the sixth aspect. The communication interface is used for communicating with other modules outside the chip.

In particular, the chip provided in the embodiments of the present application further includes a memory for storing a computer program or instructions.

In a fortieth aspect, an embodiment of the present application provides a communication system, including: a first network element and a second network element, wherein the first network element is configured to implement the communication method described in the first aspect or any possible implementation of the first aspect. The second network element is configured to implement the communication method described in any possible implementation manner of the third aspect.

Optionally, the communication system may further include: a third network element, and/or one or more first application servers. Wherein the third network element is configured to implement the communication method described in any possible implementation of the sixth aspect or the sixth aspect. The first application server application implements the communication method of the fifth aspect or any possible implementation of the fifth aspect.

In a fortieth aspect, an embodiment of the present application provides a communication system, including: a first network element and a second network element. Wherein the first network element is configured to implement the communication method described in the second aspect or any possible implementation of the second aspect. The second network element is configured to implement the communication method described in any possible implementation manner of the fourth aspect.

Optionally, the communication system may further include: one or more first application servers applying the communication method described in any possible implementation of the fifth aspect or the fifth aspect.

In a forty-second aspect, an embodiment of the present application provides a communication method, including: the first network element receives first information from the second network element. The first information is a migration completion time of the expected application context. The method comprises the steps that a first network element obtains migration completion time of an application context of a terminal in one or more associated first application servers; the application context is information of the first application for the terminal on the second application server. The second application server is an application server currently providing services for the terminal. The first network element determines at least one target application server from the one or more first application servers based on the first information.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element sends information of at least one target application server to the second network element.

In one possible implementation manner of the application, the migration completion time of the application context of the target application server for the terminal is less than or equal to the expected migration completion time of the application context.

It should be noted that, for specific implementation of the "obtaining the migration completion time of the application context of each first application server for the terminal" in the forty-second aspect, reference may be made to the relevant description in the first aspect, and details are not repeated here.

In a possible implementation manner of the present application, in a case that the first network element is a second enabling server, the method provided in the embodiment of the present application further includes: the first network element receives address information of a first enabling server from a second network element, the first enabling server being associated with the second application server.

It should be noted that, for the description of "about the first network element and the second network element" in the forty-second aspect, reference may be made to the description in the first aspect, and details are not described here.

In a forty-third aspect, an embodiment of the present application provides a communication method, including: the method comprises the steps that a first network element obtains migration completion time of an application context of each first application server aiming at a terminal in one or more associated first application servers; the application context is information of a first application for the terminal on a second application server, which is an application server currently serving the terminal. The first network element determines at least one target application server from the one or more first application servers.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the first network element receives first information from the second network element, the first information being a migration completion time of an expected application context. The first network element determining at least one target application server from one or more first application servers, comprising: the first network element determines at least one target application server from the one or more first application servers based on the expected migration completion time of the application context.

In a possible implementation manner of the present application, the method provided in the embodiment of the present application may further include: the first network element receives address information of a first enabling server from a second network element.

It should be noted that, for specific implementation of the "obtaining migration completion time of the application context of each first application server for the terminal" in the forty-third aspect, reference may be made to the relevant description in the first aspect, and details are not repeated here.

It should be noted that, for the description of "about the first network element and the second network element" in the forty-third aspect, reference may be made to the description in the first aspect, and details are not described here.

In a fourteenth aspect, an embodiment of the present application provides a communication method, where the method includes: and the second network element sends first information to the first network element, wherein the first information is the migration completion time of the expected application context. The second network element receives information of at least one target application server from the first network element. The target application server is capable of providing a service for the terminal. The application context is information of a first application for the terminal on a second application server, which is an application server currently serving the terminal.

Forty-fifth aspect, embodiments of the present application provide a communication apparatus, which may implement the method of the forty-second aspect or any possible implementation manner of the forty-second aspect, and therefore can also achieve the beneficial effects of any possible implementation manner of the forty-second aspect or the forty-second aspect. The communication device may be a first network element, or may be a device that supports the first network element to implement the method in the forty-second aspect or any possible implementation manner of the forty-second aspect, for example, a chip applied in the first network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

For example, the communication apparatus includes a communication unit and a processing unit, where the processing unit is configured to support the first network element to implement the forty-second aspect or the related actions processed by the first network element in any possible implementation manner of the forty-second aspect. The communication unit is configured to support actions related to the transceiving by the first network element in the implementation of the forty-second aspect or any possible implementation manner of the forty-second aspect.

In a sixteenth aspect, embodiments of the present application provide a communication apparatus, which may implement the method in the forty-third aspect or any possible implementation manner of the forty-third aspect, and therefore may also implement the beneficial effects in the forty-second aspect or any possible implementation manner of the forty-second aspect. The communication device may be a first network element, or may be a device that supports the first network element to implement the method in the forty-third aspect or any possible implementation manner of the forty-third aspect, for example, a chip applied in the first network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

For example, the communication apparatus includes a communication unit and a processing unit, where the processing unit is configured to support the first network element to implement the forty-third aspect or a related action processed by the first network element in any possible implementation manner of the forty-third aspect. The communication unit is configured to support actions related to the transceiving by the first network element in any possible implementation manner of the forty-third aspect or the forty-third aspect of the first network element.

In a forty-seventh aspect, the present embodiments provide a communication apparatus, which may implement the method in the forty-fourth aspect or any possible implementation manner of the forty-fourth aspect, and therefore, the beneficial effects in the forty-fourth aspect or any possible implementation manner of the forty-fourth aspect can also be achieved. The communication device may be a second network element, or may also be a device that supports the second network element to implement the method in the fourteenth aspect or any possible implementation manner of the fourteenth aspect, for example, a chip applied to the second network element. The communication device may implement the above method by software, hardware, or by executing corresponding software by hardware.

For example, the communication apparatus includes a communication unit and a processing unit, where the processing unit is configured to support the second network element to implement the fourteenth aspect or relevant actions processed by the second network element in any possible implementation manner of the fourteenth aspect. The communication unit is configured to support the second network element to implement the fourteenth aspect or relevant actions of transceiving by the second network element in any possible implementation manner of the fourteenth aspect.

In a forty-eighth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement a communication method described in the forty-second aspect or the forty-second aspect in various possible implementations. The communication interface is used for communicating with other modules outside the chip.

In a forty-ninth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, and the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the forty-third aspect or the forty-third aspect in various possible implementations. The communication interface is used for communicating with other modules outside the chip.

In a fifty-fourth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one of the communication methods described in the forty-fourth aspect or the various possible implementations of the forty-fourth aspect. The communication interface is used for communicating with other modules outside the chip.

In a fifty-first aspect, the embodiments herein provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the forty-second aspect to the forty-second aspect.

In a fifty-second aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of possible implementation manners of the forty-third aspect to the forty-third aspect.

In a fifty-third aspect, the present application provides a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are run on a computer, the computer is caused to execute a communication method as described in any one of the possible implementation manners of the forty-fourth aspect to the forty-fourth aspect.

In a fifty-fourth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform a method of communication as described in the forty-second aspect or in various possible implementations of the forty-second aspect.

In a fifty-fifth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the method of communication described in the forty-third aspect or in the various possible implementations of the forty-third aspect.

In a sixteenth aspect, embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, cause the computer to perform a communication method as described in the various possible implementations of the forty-fourth or forty-fourth aspect.

In a fifty-seventh aspect, an embodiment of the present application provides a communication system, including a first network element and a second network element, where the first network element is configured to perform the methods described in the foregoing forty-second/forty-third aspect and various possible implementations thereof. The second network element is configured to perform the method described in the forty-fourth and various possible implementations.

Any one of the above-provided apparatuses, computer storage media, computer program products, chips, or communication systems is configured to execute the above-provided corresponding methods, and therefore, the beneficial effects that can be achieved by the apparatuses, the computer storage media, the computer program products, the chips, or the communication systems can refer to the beneficial effects of the corresponding schemes in the above-provided corresponding methods, and are not described herein again.

Drawings

Fig. 1a is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 1b is a schematic architecture diagram of another communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of an architecture of an NWDAF network element and Network Function (NF) communication in a 5GC according to an embodiment of the present application;

Fig. 3 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 4 is a flowchart illustrating an overall application context migration process according to an embodiment of the present disclosure;

fig. 5.1 to 5.5 are schematic diagrams illustrating a specific process of application context migration according to an embodiment of the present application;

FIGS. 5.6-5.7 are schematic diagrams of different request models provided by embodiments of the present application;

fig. 5.8 is a specific flowchart of another application context migration provided in the embodiment of the present application;

fig. 6.1 is a schematic flowchart of a communication method according to an embodiment of the present application;

fig. 6.2 is a schematic flow chart of another communication method provided in the embodiment of the present application;

fig. 7 is a flowchart illustrating a further communication method according to an embodiment of the present application;

FIGS. 8-22 are schematic diagrams illustrating a detailed flow chart of a T-EAS provided by an embodiment of the present application;

fig. 23 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

In order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish identical items or similar items with substantially the same functions and actions. For example, the first application server and the second application server are only used for distinguishing different application servers, and the sequence of the first application server and the second application server is not limited. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

It is noted that the words "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present relevant concepts in a concrete fashion.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

The technical scheme of the application can be applied to various communication systems, such as: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunications System (UMTS), a universal microwave access (WiMAX) communication system, a Public Land Mobile Network (PLMN) system, a device-to-device (D2D) network system or a machine-to-machine (M2M) network system, a future 5G communication system, and the like.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and it can be known by a person of ordinary skill in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems with the evolution of the network architecture and the occurrence of a new service scenario.

As shown in fig. 1a, an embodiment of the present application provides a communication system 100, where the communication system 100 includes: a source enabled server 101, a target enabled server 102, an Edge Enabled Client (EEC) 103. Wherein the source enabled server 101 is able to communicate with the target enabled server 102. The target-enabled server 102 is capable of communicating with the edge-enabled client 103. The edge-enabled client 103 is a peer entity of the source-enabled server 101, the target-enabled server 102 on the side of the terminal 104.

Wherein, the source enabling server 101 is an enabling server for providing service for the terminal 104 before the application context is migrated. The target enabling server 102 is an EES that is reselected by the EEC103 for the terminal 104 when the source enabling server 101 cannot continue to serve the terminal 104. For example, in an actual process, due to the movement of the terminal 104 or the failure/shutdown/overload of the source enable server 101 or the presence of an enable server that is more suitable for providing services to the terminal 104, at this time, the source enable server 101 may no longer provide services to the terminal 104 or may no longer be an EES that is most suitable for serving the terminal 104, at this time, the EEC103 first triggers a service provision (service provisioning) procedure to obtain the target enable server 102 that provides services to the terminal 104. In this process, the EEC103 interacts with an Edge Configuration Server (ECS) 108. Of course, the process of obtaining the target enabling server 102 may also be initiated by the source enabling server 101. If the flow is initiated by the source enabling server 101 to acquire the target enabling server 102, it can be regarded as a "acquire T-EES" flow (retrieve T-EES).

Optionally, as shown in fig. 1a, the communication system 100 further includes: the source application server 105. The terminal 104 is capable of communicating application data with the source application server 105. The source application server 105 is associated with the source enabled server 101, that is, the source application server 105 is registered with one source enabled server 101, or information of one source application server 105 is configured on the source enabled server 101 through the management system. The origin enabling server 101 is referred to as the enabling server associated with the origin application server 105. The origin enabled server 101 controls/manages the origin application server 105 registered/configured on the origin enabled server 101.

It will be appreciated that the source application server 105 is the application server that is currently serving the terminal 104. I.e. the terminal 104 accesses the edge data network via the source application server 105. The source application server 105 typically has the application context of the terminal 104 therein.

Wherein, the source enabling server 101 and the source application server 105 belong to the same EDN1. The target enabled server 102 and the one or more target application servers 106 belong to the same EDN2.EDN1 and EDN2 may be the same EDN or different EDNs, and different EDNs are exemplified in fig. 1 a. Here, the EDN1 may be regarded as a source EDN of the terminal 104, and the EDN2 may be regarded as a target EDN of the terminal 104 after the EDN is replaced.

Application context: refers to operational state information associated with a terminal or a group of terminals, or a group of data associated with an application client on the source-enabled server 101. Optionally, the context of the subscription of the one or more terminals at the source application server 105 and the core network, such as the transaction identifier of the subscription, may also be included. Optionally, the context of the one or more terminals on an Edge Enable Server (EES), such as the transaction identifier of the subscription of the source application server 105 to the one or more terminals, is also included.

In a case where the source application server 105 cannot continue to provide services for the terminal 104, for example, when the terminal 104 moves outside a service area of the source application server 105, for example, terminal movement between Edge Data Networks (EDNs), terminal movement between laddns, the source application server 105 may not continue to provide services for currently running applications, or the source application server 105 is not already an optimal application server that can provide services for the terminal 104, and other application servers may be better suited to serve application clients on the terminal 104, an application server needs to be reselected to provide services for the terminal 104. To better serve the terminal 104, the eec103 may reselect an application server for the terminal 104 to serve the terminal 104. Based on this, the EEC103 may trigger the target enabled server 102 to discover one or more target application servers 106 that may serve the terminal 104. Or the source enabling server 101 or the source application server 105 triggers the target enabling server 102 to discover one or more target application servers 106 that can serve the terminal 104. The target enabling server 102 is configured to discover one or more target application servers 106 capable of providing services for the terminal, and determine one or more of a migration completion time of each target application server 106 for the application context of the terminal 104 or location information, load information, network conditions, location information of the source application server 105, load information, network conditions, and size of the application context of each target application server 106, so as to facilitate subsequent replacement of the application server providing services for the terminal 104 from the source application server 105 to one or more target application servers in the target application servers 106. At this time, the EEC103 first triggers a service provisioning (service provisioning) procedure to trigger the target enabling server 102 for serving the terminal 104. The EEC interacts with an Edge Configuration Server (ECS) 108 in this flow. Of course, the flow triggering the acquisition of the target enabling server 102 may also be initiated by the source enabling server 101, and if the flow is initiated by the S-EES, the flow may be regarded as a "acquisition T-EES" flow (retrieve T-EES).

Optionally, as shown in fig. 1a, the communication system 100 provided in the embodiment of the present application may further include: a data analysis network element 107 or an ECS108.

Wherein the data analysis network element 107 or the ECS108 is capable of calculating the migration completion time of the application context of each target application server 106 for the terminal 104 according to the information provided by the target enabling server 102 for determining the migration completion time of the application context of each target application server 106 for the terminal 104. For example, the information for determining the migration completion time of each target application server 106 for the application context of the terminal 104 may include: one or more of location information, load information, network conditions, location information of source application server 105, load information, network conditions, size of application context for each target application server 106.

The data analysis network element 107 may belong to a network element in 5GC, or may belong to a network management element. For example, the data analysis network element 107 may be a network data analysis function (NWDAF) network element in the 5GC, a Management Data Analysis Function (MDAF) network element of a network manager, or even a data analysis network element on the RAN side.

As shown in fig. 2, taking the data analysis network element 107 as an NWDAF network element as an example, fig. 2 (a) is data collection, that is, NWDAF invokes services of other 5GC network elements to collect a framework used by input information required for network analysis; fig. 2 (B) is an architecture in which the NWDAF sends the analysis data to the network element subscribing to or requesting the analysis data by providing the NWDAF service. The NWDAF provides network data analysis at the slice level for other network elements, providing network analysis information (i.e., load level information) at the network slice instance level, without needing to know the current subscribing terminal using the slice.

The architecture shown in FIG. 1a may be referred to as: the scenario of replacement of an enabling server, i.e. the enabling server of terminal 104 is replaced from source enabling server 101 to target enabling server 102.

As shown in fig. 1b, an embodiment of the present application provides a communication system, which includes: an enable server 108, an Edge Enable Client (EEC) 103.

Wherein the third enabling server 100 is the enabling server currently serving the terminal 104. The edge-enabled client 103 is a peer entity enabling the server 108 on the side of the terminal 104.

As shown in FIG. 1b, an enablement server 108 is deployed in the EDN. The enabling server 108 is configured to discover one or more target application servers 106 that may serve the terminal and determine a migration completion time for each target application server 106 for the application context of the terminal 104, which facilitates subsequent replacement of the application server serving the terminal 104 from the source application server 105 to one or more of the target application servers 106.

Optionally, the communication system shown in fig. 1b may further include: the source application server 105. The source application server 105 is the application server that is currently serving the terminal 104. Here, the source application server 105 is generally registered with the enable server 108, or information of one source application server 105 is arranged on the enable server 108 through the management system. The enabling server 108 is referred to as the enabling server associated with the origin application server 105. The enabling server 108 controls/manages the source application server 105 registered/configured on the enabling server 108.

The architecture shown in FIG. 1b may be referred to as: the scenario of the enable server not being replaced, i.e., the enable server serving the terminal 104 is not being replaced.

It is worth noting that the source application server 105, one or more target application servers 106, the enabling server 108, the source enabling server 101, and the target enabling server 102 shown in fig. 1b and 1a are all deployed on an Edge Data Network (EDN). In a general understanding, an EDN corresponds to a data network, is a special local data network (local DN), contains edge-enabled functionality, can use Data Network Access Identifier (DNAI) and Data Network Name (DNN) identifiers, and is a network logic concept. Another understanding of the EDN is that the EDN is a peer-to-peer concept of a central cloud, which may be understood as a local data center (concept of geographic location), may be identified using DNAI, and may contain a plurality of local data networks (local DNs).

The various servers deployed in the EDN may be referred to as edge servers, for example, an enabled server may be referred to as an Edge Enabled Server (EES). The application server may be referred to as an Edge Application Server (EAS).

The functional entities and interfaces involved in the embodiments of the present application are briefly described as follows:

application example/edge application: applications deployed in an edge data network are referred to as application instances. In particular, a server application (e.g., social media software, augmented Reality (AR), virtual Reality (VR)) deploys an instance (instance) running on the EDN. An application may deploy one or more EAS in one or more EDNs, and the EAS deployed to run in different EDNs may be considered different EAS of an application, which may share a domain name, may use an anycast IP address, or may use different IP addresses. EAS may also be referred to as an edge application (server), an application instance, an edge application instance, a multi-access edge computing (MEC) application (server), an EAS function, and the like.

An Application Client (AC) is a peer entity of the edge application on the UE side. The application client is used for an application user (i.e., a terminal (user)) to obtain an application service from an application server. The application client is a client program applied on the terminal side, and the application client can be connected to an application server on the cloud to acquire application services, and can also be connected to an EAS (electronic article surveillance) deployed and operated in one or more EDNs to acquire the application services.

Edge Enable Server (EES): some enabling capabilities can be provided for the application instances deployed in the EDN, and the deployment situation of the application in the MEC can be better supported. The method can support registration of edge application, authentication and authorization of UE, and provide IP address information of application instance for the terminal. The method can further support the acquisition of the identification and the IP address information of the application instance, and further send the identification and the IP address information of the application instance to the edge data network configuration server. The EES is deployed in the EDN. Typically, EAS is registered with or otherwise configured by the management system on an EES, referred to as the EAS associated EES, which controls/manages the EAS registered/configured on the EES.

Edge Enabled Client (EEC): is a peer entity of the EES at the terminal side. The EEC is used to register information of the EEC and information of the application client with the EES, perform security authentication and authorization, obtain an IP address of the EAS from the EES, provide an edge computing enabling capability to the application client, such as the EAS discovery service returning the IP address of the EAS to the application client.

Edge Configuration Server (ECS): is responsible for the configuration of the EDN, such as providing the UE with information of the EES. The information of the application instance can also be directly provided for the terminal, and the terminal interacts with the DNS of the application to acquire the information of the application instance. And further acquiring and storing the information of the application instance and the IP address from other functional entities.

The application user signs a service agreement with an application provider so as to provide services for the application user, and the application user logs in an application client on the terminal and communicates with the EAS through the connection of the application client. The enabling client is a middleware layer, and is generally located in the operating system, or is located between the application client and the operating system. The application client may obtain the edge-enabled service from the enabling client in the form of an Application Programming Interface (API).

The communication between the AC and the EEC in the embodiment of the application is an EDGE-5 interface communication. The EEC and the EES communicate over an EDGE-1 interface. The EEC and ECS communicate via an EDGE-4 interface. The core network and the ECS communicate over an EDGE8 interface. The core network and the EAS communicate via an EDGE-7 interface. The core network and each EES communicate through EDGE-2 interface. The EAS and EES communicate via the EDGE-3 interface. The EES communicate with each other via an EDGE-9 interface. The ECS and EES communicate over the EDGE-6 interface.

The terminal involved in the embodiment of the application is a device with a wireless communication function, and can be deployed on land, including indoors or outdoors, and is handheld or vehicle-mounted. And can also be deployed on the water surface (such as a ship and the like). And may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). A terminal, also referred to as User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), a terminal device, and the like, is a device for providing voice and/or data connectivity to a user. For example, the terminal includes a handheld device, a vehicle-mounted device, and the like having a wireless connection function. Currently, the terminal may be: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile Internet Device (MID), wearable device (e.g., smart watch, smart bracelet, pedometer, etc.), vehicle-mounted device (e.g., automobile, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), virtual Reality (VR) device, augmented Reality (AR) device, wireless terminal in industrial control (industrial control), smart home device (e.g., refrigerator, television, air conditioner, electric meter, etc.), smart robot, workshop device, wireless terminal in self drive (self drive), wireless terminal in remote surgery (remote medical supply), wireless terminal in smart grid (smart grid), wireless terminal in transportation safety (transportation safety), wireless terminal in smart city (smart city) or wireless terminal in smart grid (smart city), wireless terminal in smart airplane, unmanned plane, etc., such as a flying robot, unmanned plane, etc. In a possible application scenario, the terminal is a terminal which often works on the ground, such as an in-vehicle device. In the present application, for convenience of description, a Chip disposed in the device, such as a System-On-a-Chip (SOC) Chip, a baseband Chip, or the like, or another Chip having a communication function may also be referred to as a terminal.

The terminal can be a vehicle with a corresponding communication function, or a vehicle-mounted communication device, or other embedded communication devices, or can be a user handheld communication device, including a mobile phone, a tablet computer, and the like.

As an example, in the embodiment of the present application, the terminal may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

Fig. 3 shows a hardware structure diagram of a communication device provided in an embodiment of the present application. The hardware structures of the first network element, the second network element, the third network element, and the first application server in the embodiment of the present application may refer to the structure shown in fig. 3. The communication device comprises a processor 31, a communication line 34 and at least one transceiver (which is only exemplary in fig. 3 and illustrated as comprising a communication interface 33).

The processor 31 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication link 34 may include a path for transmitting information between the aforementioned components.

The communication interface 33 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

Optionally, the communication device may also include a memory 32.

The memory 32 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate and coupled to the processor via a communication line 35. The memory 32 may also be integrated with the processor 31.

The memory 32 is used for storing computer-executable instructions for executing the scheme of the application, and is controlled by the processor 31 to execute. The processor 31 is configured to execute computer-executable instructions stored in the memory 52, so as to implement the communication method provided by the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 31 may include one or more CPUs, such as CPU0 and CPU1 in fig. 3, as one embodiment.

In particular implementations, the communication device may include multiple processors, such as processor 31 and processor 35 in fig. 3, as one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

ACR (application context relocation) is understood to be the whole flow from detecting a demand to clearing up the whole flow, i.e. the whole flow for 5 cases of 4 phases as shown in fig. 4.

ACT (application context transfer), is understood to be the process by which an application context is migrated from a source application server 105 to a target application server 106.

In the embodiment of the present application, the migration completion time of the application context may be referred to as: ACT completion time, or ACT delay.

In practice, when the terminal 104 migrates from the source application server 105 to a target EAS in one or more target application servers 106, the application context of the terminal 104 on the source application server 105 needs to be migrated to the target application server.

Currently, the application context migration framework is shown in fig. 4, and can be mainly divided into four phases:

stage 1. Detection of application context migration: i.e. determining that the context migration may be required, the detecting entity detects some events such as a location change of the terminal 104, or an update of the user plane path of the terminal 104.

Stage 2. Decision of application context migration: the decision entity determines that an application context migration is required.

Stage 3. Execution of application context migration: the application context is primarily transferred from the source application server (source EAS, S-EAS) (i.e., source application server 105) to the target EAS (T-EAS). And may further include information notifying the terminal 104 of T-EAS, information about the completion of the application context migration and T-EAS (e.g., address of T-EAS, N6 routing information for T-EAS, etc.) for notifying the network of the completion of the application context migration.

And 4, applying the cleaning work after the context migration: multiple entities are involved, such as an Application Client (AC) initiating a new socket connection to T-EAS, etc.

SA6 currently defines several context migration schemes and procedures as follows:

the first scheme is as follows: as shown in fig. 5.1, the EEC detects that application context migration (e.g. terminal location update) is required. The EEC obtains the information of the T-EES from the ECS. The EEC triggers the T-EES to perform the step of discovering the T-EAS. The EEC obtains the information of the T-EAS discovered by the T-EES from the T-EES. The EEC triggers the AC, which decides whether and when to perform application context migration. After the AC decides to perform application context migration, the AC triggers S-EAS. The S-EAS sends the application context to the T-EAS. After the application context migration, the AC switches the application data of the terminal to T-EAS.

Scheme II: as shown in fig. 5.2, the EEC detects that context migration is needed, determines whether and when the EEC performs context migration, and after the EEC determines to perform context migration, the EEC acquires T-EAS information from a source EES (S-EES), the EEC notifies the S-EAS to perform context migration through the S-EES, and the S-EAS sends an application context to the T-EAS. After the context migration, the AC switches the application data to T-EAS.

The third scheme is as follows: as shown in fig. 5.3, the S-EES detects that context migration is required, the S-EES sends context migration information to the S-EAS, the S-EAS decides whether and when to perform context migration, the S-EAS acquires T-EAS information after the S-EAS decides to perform context migration, and the S-EAS sends application context to the T-EAS. After the context migration, the AC switches the application data to T-EAS.

And the scheme is as follows: as shown in FIG. 5.4, when EEC, S-EAS and S-EES detect that context migration is needed, S-EES decides whether and when to perform context migration, and after S-EES decides to perform application context migration, S-EES obtains T-EES information through ECS, determines T-EAS, and S-EES sends ACR notification to S-EAS, and S-EAS sends application context to T-EAS. After the context migration, the AC switches the application data to T-EAS.

And a fifth scheme: as shown in fig. 5.5, the EEC detects that context migration is needed, the EEC notifies the T-EES that context relocation may need to be applied, the T-EES decides whether and when to perform context migration, and after the T-EES decides to perform context migration, the T-EES acquires T-EAS information and sends an ACR request message to the T-EAS. The T-EAS initiates an application context transfer between the S-EAS and the T-EAS. After the context migration, the AC switches the application data to T-EAS.

In the various application context migration schemes described above, T-EAS discovery and selection is involved. Two approaches to T-EAS discovery are defined above: EEC initiated T-EAS discovery, and S-EAS/S-EES initiated T-EAS discovery. These two ways are described separately:

1) EEC initiated T-EAS discovery

EEC initiated T-EAS discovery reuses EEC initiated EAS discovery procedures. The EEC requests or subscribes EAS from the EES and may carry EAS screening conditions. The EES returns or notifies the EEC of the EAS (at least one) that the condition is satisfied.

The EEC-initiated EAS discovery procedure may use a "request-response" model or a "subscription-notification" model. The specific process is as follows:

as shown in fig. 5.6, the request-response model. I.e. the EEC sends an EAS discovery request (discovery request) to the EES. The EES authenticates and discovers T-EAS. The EES sends an EAS discovery response (discovery response) to the EEC. The EAS discovery request may include an EEC ID (identifier) and security authentication, and may include an EAS selection screening condition, where the screening condition includes an EAS ID, EAS address information, an EAS service range, whether to support service continuity, and the like. The EAS discovery response includes at least one T-EAS, one EAS configuration file (EAS profile) for each T-EAS. The EAS profile is a table of relevant parameters of the EAS, including an ID (identifier) of the T-EAS, address information, may include an AC ID (identifying an AC that the EAS may service), a service scope of the EAS, a corresponding DNAI, and the like.

As shown in fig. 5.7, the subscription-notification model. As shown in (a) of fig. 5.7, the subscription process includes:

1. the EEC transmits an EAS discovery subscription request (EAS discovery subscription request) to the EES. Wherein, the EAS discovery subscription request contains EEC ID, security authentication and notification trigger condition, the condition indicates the transmission time of the EAS discovery notification, including EAS availability change; the discovery subscription request may also include EAS selection screening conditions including EAS ID, EAS address information, may include EAS service scope, whether service continuity is supported, etc.

2. The EES performs security authentication (Authorization check).

3. The EES transmits an EAS discovery subscription response (EAS discovery subscription response) including a subscription success response to the EEC.

The notification process, as shown in (B) of fig. 5.7, includes:

1. and the notification triggering condition in the subscription process is met.

2. The EES sends an EAS discovery notification (EAS discovery notification) to the EEC, which contains at least one T-EAS, one EAS profile for each T-EAS. EAS profile is the same as the request-response flow, and is not described here.

It should be noted that the EES in fig. 5.6 and 5.7 may be replaced by T-EES. However, when the following applications relate to the subscription-notification model and the request-response model, reference may be made to the description herein, and the details will not be repeated.

As shown in fig. 5.8, the S-EAS/S-EES initiated T-EAS discovery procedure provided for embodiments of the present application is only used in the application context migration procedure. The S-EES requests T-EAS from the T-EES, or the S-EAS requests T-EAS from the T-EES through the S-EES, and T-EAS screening conditions can be carried. The T-EES returns the T-EAS (at least one) satisfying the condition to the S-EES, and if the T-EAS is initiated, the S-EES also forwards the T-EAS (at least one) to the S-EAS. The S-EAS/S-EES initiated T-EAS discovery procedure is as follows:

1. the S-EAS sends an EAS discovery request to the S-EES. The EAS discovery request contains the information element of the EEC initiated EAS discovery request-response model step 1 (EEC ID is replaced by S-EAS ID) and may also contain the location information of the terminal and the target DNAI (association potential T-EAS).

2. The S-EES, upon receiving the EAS discovery request, decides to perform application context relocation (i.e., application context migration).

3. And interacting the S-EES with the ECS to obtain the T-EES.

4. The S-EES sends an EAS discovery request to the T-EES. The EAS discovery request contains the information element identical to step 1 (S-EAS ID is replaced with S-EES ID).

5. The T-EES sends an EAS discovery response to the S-EES. The EAS discovery response contains cells that are in accordance with the discovery request-response model step 3.

6. The S-EES forwards the EAS discovery response to the S-EAS.

It will be appreciated that

steps

1 and 5 are optional steps, and are only performed if the process is S-EAS initiated.

As can be seen from the above processes, the EAS discovery response/notification message may include one or more T-EAS and its profile, so that when multiple T-EAS are returned, the EEC/S-EAS/S-EES needs to select one T-EAS from the multiple T-EAS. The 3GPP SA6#42E conference discusses the selection criteria for T-EAS and passes the conclusion of selecting T-EAS based on the EAS Service Key Performance indicator (EAS Service KPI). The Key Performance Indicator (KPI) of EAS service is one item in the EAS profile, and contains several KPIs related to EAS interaction with the AC. The details are shown in table 1 below:

TABLE 1

However, since different applications have different requirements for service continuity, they have different latency requirements for application context migration. For example, V2X (vehicle to electronics) traffic has a much more stringent requirement for migration delay than video traffic. However, the application context migration delay information corresponding to the EAS is not included in the EAS service KPI, and the information element which is enough for the EEC/S-EAS/S-EES to determine the application context migration delay corresponding to the EAS is not included. In addition, even all cells that may be contained in the EAS profile in the EAS discovery response/notification message do not contain either the migration delay information corresponding to the EAS or cells sufficient to determine the delay information. Therefore, EEC/S-EAS/S-EES cannot perform T-EAS selection according to the application context migration delay information.

Based on this, the embodiment of the present application provides a communication method, in which a first network element acquires information (for example, a migration completion time of an application context of a terminal to which each first application server is directed) for determining a migration completion time of the application context of the terminal to which each first application server is directed (or the migration completion time of the application context of the terminal to which each first application server is directed), and then sends the information of the migration completion time of the application context of the terminal to which each first application server is directed to a second network element, so that the second network element may, when selecting the first application server for providing a service for the terminal, base on the migration completion time of the application context of the terminal to which each first application server is directed, thereby enabling the selected first application server to better provide the service for the terminal.

In the embodiment of the present application, a specific structure of an execution subject of one communication method is not particularly limited as long as communication can be performed by one communication method according to the embodiment of the present application by running a program in which a code of one communication method of the embodiment of the present application is recorded. For example, an execution main body of a communication method provided in the embodiment of the present application may be a functional module capable of calling a program and executing the program in the first network element, or a communication device, such as a chip, applied in the first network element. An execution main body of the communication method provided in the embodiment of the present application may be a functional module capable of calling a program and executing the program in the second network element, or a communication device, such as a chip, applied in the second network element. This is not limited in this application. The following embodiments describe the implementation subject of a communication method as a first network element and a second network element.

As shown in fig. 6.1, fig. 6.1 is a communication method provided in this embodiment, where the method includes:

step 601, the first network element obtains migration completion time (transfer completion time) of each first application server for an application context (application context) of the terminal in one or more first application servers associated with the first network element.

The application context is a set of data related to the application client on the application server, the application server is an application server for providing service for the terminal, and the application context exists in a second application server before the application context is migrated. The second application server is an application server currently providing services for the terminal. The first application server is used for providing services for the terminal.

It can be understood that the first application server is an application server recommended by the first network element to the second network element and capable of providing a service for the terminal when the second application server does not meet the requirement for serving the terminal.

As an example, the second application server may be considered not to meet the requirement for serving the terminal when there is a situation, such as a location change of the terminal, such as the terminal being out of the service range of the second application server, or the second application server being out of order, down, overloaded, or not being the most suitable server for serving the terminal.

It is worth noting that the migration completion time of the application context refers to the time required for the application context to start migrating from the second application server to the first application server. Due to the difference in load information/network conditions/location between different second application servers, etc., there is a difference in the duration required for the same application context to migrate to different second application servers.

It is to be understood that the one or more first application servers may be all or a portion of n first application servers discovered by the first network element based on an EAS discovery request from the second network element, n being an integer greater than or equal to 1. For example, the one or more first application servers are application servers that comply with EAS discovery screening criteria carried in EAS discovery requests.

It should be noted that the one or more first application servers associated with the first network element may also be referred to as: the first network element is associated with one or more first application servers, and the association can refer to: the one or more first application servers are registered in the first network element such that the first network element can control/manage the first application servers registered/configured on the first network element.

Step 602, the first network element sends migration completion time of each first application server for the application context of the terminal to the second network element. Accordingly, the second network element receives the migration completion time of the application context of each first application server for the terminal from the first network element.

And each first application server is used for determining a target application server which provides services for the terminal in one or more first application servers according to the migration completion time of the application context of the terminal.

In an embodiment of the present application, the migration completion time of the application context for the terminal by each first application server may be carried in the same message, for example, both carried in message 1. The signaling overhead between the first network element and the second network element can be reduced by carrying the signaling overhead in the same message. For example, message 1{ (T-EAS 1, T1), …, (T-EASn, tn) }, where T denotes migration completion time and T-EASn denotes the identity of the first application server.

As an example, the identifier of the first application server may be address information of the first application server or other parameters that can identify the first application server, which is not limited in this embodiment of the present application.

In an embodiment of the present application, the migration completion time of each first application server for the application context of the terminal may be carried in different messages, for example, the migration completion time of the first application server 1 for the application context of the terminal is carried in the message 1, and the migration completion time of the first application server 2 for the application context of the terminal is carried in the message 2, which is not limited in this embodiment of the present application.

In addition, taking as an example that the migration completion time of each first application server for the application context of the terminal is carried in the message 1, optionally, the message 1 may further include an EAS profile of each first application server. In an aspect, the migration completion time of the application context of the first application server 1 for the terminal may be located in the EAS profile of the first application server 1. On the other hand, the migration completion time of the application context of the first application server 1 for the terminal may not be located in the EAS profile of the first application server 1.

In an optional embodiment of the present application, the first network element may send, to the second network element, a migration completion time of a part of the one or more first application servers for the application context of the terminal. For example, the first network element may filter migration completion times of one or more first application servers for the application context of the terminal, for example, remove the longest migration completion time or the migration completion time exceeding the preset time, and send the remaining migration completion times of the first application servers for the application context of the terminal that meet the requirements to the second network element.

In a possible implementation, if the first network element receives a second message from the second network element before performing step 601, where the second message is used to request that the first network element provide migration completion time of the application context of the terminal for each first application server capable of providing the service for the terminal associated with the first network element, then the message 1 may be a response message for the second message. For example, as shown in fig. 5.6, the second message is an EAS discovery request. Message 1 may be an EAS discovery response. For example, as shown in fig. 5.7, the second message is an EAS discovery subscription request, and message 1 may be an EAS discovery notification or an EAS discovery subscription response.

Step 603, the second network element selects a target application server from the one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

As an example, the migration completion time of the target application server for the application context of the terminal is the shortest of the one or more first application servers, so that the influence of the migration completion time on the running interruption of the application can be minimized. Or as an example, the migration completion time of the application context of the terminal by the target application server is less than or equal to a preset time, where the preset time may be set by a predefined value or according to needs, and this is not limited in this embodiment of the application.

As another example, if there are two first application servers in the one or more first application servers that have the same migration completion time for the application context of the terminal and are the lowest, the second network element may select one first application server from the two first application servers as the target application server, or refer to the description in the prior art in a manner of selecting the target application server from the two first application servers, which is not described herein again.

In another embodiment of the present application, the above step 602 may be replaced by: the first network element determines a target application server from the one or more first application servers according to the migration completion time of the application context of each first application server for the terminal. The target application server is used for providing services for the terminal. Accordingly, step 603 may be replaced by: the first network element sends the information of the target application server to the second network element, and correspondingly, the second network element receives the information of the target application server from the first network element and determines the target application server according to the information of the target application server.

In an optional embodiment, the first network element may further send, to the second network element, a migration completion time of the application context of the terminal for the target application server.

For the first network element determining the specific implementation of the target application server from the one or more first application servers according to the migration completion time of the application context of each first application server for the terminal, reference may be made to the specific implementation of selecting the target application server by the second network element, which is not described herein again.

The embodiment of the present application provides a communication method, in a process of replacing an application server providing a service for a terminal from a second application server to a target application server, an application context of the terminal on the second application server needs to be migrated to the target application server, although one or more first application servers can provide a service for the terminal, since there is a difference in migration completion time required for migrating the application context to each first application server, since in an application context migration process, the application service of the terminal is temporarily suspended or interrupted, the migration completion time may affect operation of a first application of the terminal, based on which, a first network element in this application embodiment obtains the migration completion time of each first application server for the application context of the terminal, and then provides the migration completion time of each first application server for the application context of the terminal to a second network element. Therefore, the second network element can be assisted to select the target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal, the influence of the migration completion time on the running interruption of the application is reduced as much as possible, and the selected target application server can better provide service for the terminal.

In an embodiment of the present application, an embodiment of the present application provides a communication method, including: the migration completion time of each first application server aiming at the application context of the terminal is one or more first application servers related to a first network element; the first application server is used for providing services for the terminal. The application context is information of a first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present; and the first network element determines at least one target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

As an example, the method provided in this embodiment of the present application may further include step 601-1 shown in fig. 6.2, before the first network element determines at least one target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal. Accordingly, the determining, by the first network element, at least one target application server from one or more first application servers according to the migration completion time of the application context of the terminal for each first application server may be implemented by the following step 603-1.

As shown in fig. 6.2, fig. 6.2 is another communication method provided in the embodiment of the present application, where the method includes:

step 601-1, the second network element sends the first information to the first network element. Accordingly, the first network element receives the first information from the second network element. The first information is a migration completion time of the expected application context.

As an example, the first information may be carried in message X. For example, the message X may be an EAS discovery subscription request as shown in fig. 5.7, or the message X may be an EAS discovery request as shown in fig. 5.6, which is not limited in this embodiment.

It is understood that the first information is a requirement of the second network element for the migration completion time of the application context, that is, the application context migration time of the discovered or selected target application server (e.g., T-EAS) and the second application server (e.g., S-EAS) cannot exceed this time. The first network element may select at least one T-EAS from the one or more discovered first application servers based on the first information. As a specific example, if the expected migration completion time of the application context is 10 ms, it means that the application context migration time between the found or selected T-EAS and S-EAS cannot exceed 10 ms. It is to be understood that the expected migration completion time of the application context may be a migration completion time of the application context specific to the terminal or the class of terminals, i.e. it may have different expected migration completion times of the application context for different terminals or different classes of terminals. Or the expected migration completion time of the application context is the same for different terminals or classes of terminals.

Step 602-1, the first network element obtains migration completion time of an application context of each first application server for the terminal in one or more associated first application servers. The application context is information of a first application for the terminal on a second application server, which is an application server currently serving the terminal.

For a specific implementation of step 602-1, reference may be made to the description of any one of cases 1 to 3, which is not described herein again.

Wherein, the step 602-1 and the step 601-1 do not distinguish the sequence.

Step 603-1, the first network element determines at least one target application server from the one or more first application servers according to the first information.

As a possible implementation: the first network element determines one or more first application servers, of the plurality of first application servers, for which the migration completion time of the application context for the terminal is less than or equal to the expected migration completion time of the application context, as a target application server.

Step 604-1, the first network element sends information of at least one target application server to the second network element. Accordingly, the second network element receives information from the at least one target application server of the first network element.

If message X is an EAS discovery subscription request, information for at least one target application server may be carried in the EAS discovery notification. If message X is an EAS discovery request, information for at least one target application server may be carried in the EAS discovery response.

After step 604-1, the second network element may select a target application server from the at least one target application server to provide a service for the terminal.

In one possible implementation, the first network element may further send, to the second network element, a migration completion time of each of the at least one target application server for the application context of the terminal. Thus, when the number of the at least one target application server is two or more, the second network element can select one target application server to provide services for the terminal according to the migration completion time of each target application server for the application context of the terminal.

According to the scheme, the first network element can screen at least one target application server meeting the requirement from the migration completion time of each first application server for the application context of the terminal according to the first information from the second network element. And provided to the second network element so that the second network element selects a target application server serving the terminal from the at least one target application server.

The schemes described in fig. 6.1, 6.2 and 7 in the embodiments of the present application may be applied to the following scenarios:

scenario 1), no replacement of enabled servers.

In scenario 1), in conjunction with fig. 1b, the currently enabled server (e.g., the enabled server 108) serving the terminal is still the most suitable enabled server for serving the terminal, in other words, the source application server 105 cannot serve the terminal, resulting in the need to replace the application server serving the terminal, but the EES serving the terminal is not changed.

In scenario 1), the first network element may be a third enabling server. The second network element may be an enabling client or a second application server. In connection with FIG. 1b, for example, the third enabling server may be enabling server 108. The enabled client may be the EEC103. The second application server may be the origin application server 105.

Scenario 2), change enabled server.

In scenario 2), as shown in fig. 1a, due to the movement of the terminal or other reasons, the EES (e.g., the source enabled server 101) currently serving the terminal can no longer provide the service for the terminal, or is no longer the E-enabled server best suited for the terminal, or there is currently a target enabled server 102 better suited for providing the service for the terminal. The enabling server that provides the server for the terminal changes from the source enabling server 101 to the target enabling server 102. The origin enabled server 101 is associated with an origin application server 105. The source-enabled server 101 is an enabled server that serves the terminal before replacing the enabled server.

Thus, in scenario 2), the first network element may be a second enabling server. The second network element may be an enabling client or a second application server or a first enabling server. If the second network element is an enabling client, the enabling client has access to the second enabling server. As shown in FIG. 1a, a second enabling server is a target enabling server 102. The enabled client may be the EEC103. The second application server may be the origin application server 105. The first enabling server is the origin enabling server 101.

In an embodiment of the present application, optionally, before step 601, the method provided in the embodiment of the present application may further include: the second network element sends a request message (e.g., an EAS discovery request as shown in fig. 5.6 or an EAS discovery subscription request as shown in fig. 5.7) to the first network element. Accordingly, the first network element receives a request message from the second network element. The request message is used for requesting the first network element to acquire the migration completion time of the application context of the terminal, which is targeted by the first application server capable of providing the service for the terminal and is discovered by the first network element.

Optionally, in scenario 1) where the enabling server is not replaced, the request message may include an identifier of the second application server and/or location information/address information of the second application server. This facilitates the first network element to determine the application server currently serving the terminal and to subsequently obtain the required information (e.g. size of application context, second relevant information) from the second application server.

In scenario 2) of replacing the enabled server, an identification of the first enabled server (e.g., address information of the first enabled server) may be included in the request message. This is so that the first network element determines the enabling server that previously served the terminal in order to obtain the required information (e.g. the size of the application context, the second relevant information) from the first enabling server.

Since the process of determining the migration completion time of the application context of each first application server for the terminal by the first network element is different in different scenarios, the following description will be introduced to the specific implementation from different situations, and the relevant steps in the embodiments shown in fig. 6.1 and 6.2 may refer to the descriptions in case 1) to case 3):

case 1), the first application server determines the migration completion time of the application context of the terminal and sends the migration completion time to the first network element.

In an embodiment of the present application, a process is provided for a first network element to determine a migration completion time of an application context of each first application server for a terminal. The process comprises the following steps:

step A1, the first network element sends a first request message to each first application server. Accordingly, each first application server receives a first request message from a first network element.

The first request message is used for requesting the migration completion time of the application context of the terminal by the first application server.

In one possible implementation, the first request message may include first indication information, where the first indication information is used to request a migration completion time of the application context of the terminal by the first application server.

In another possible implementation, the first request message includes one or more of second related information of the second application server and a size of the application context.

The second related information related to the embodiment of the present application may refer to various information related to the second application server, which may affect the migration completion time of the application context, and is not limited to one or more of location information, load information, or network condition of the second application server. Therefore, the process that the first application server obtains one or more of the second relevant information and the size of the application context by itself is avoided.

For example, the location information of the application server related to the embodiment of the present application may be a geographic location (e.g., longitude and latitude, street, etc.), a topological location (e.g., TA ID, cell ID, etc.), or access information (e.g., DNAI, etc.), which is described herein in a unified manner and will not be described in detail later.

It is worth noting that providing the location information of the second application server facilitates the first application server to determine the distance to the second application server according to the location information of the first application server. This is because the migration completion time spent in migrating the application context to the first application server a is generally higher than the migration completion time spent in migrating the application context to the first application server B, taking into account the distance that affects the migration completion time, wherein the distance between the first application server a and the second application server is greater than the distance between the first application server B and the second application server.

The network condition referred to in the embodiments of the present application may refer to a network condition between the first application server and the second application server, including but not limited to one or more of the following: bandwidth, packet loss rate, etc. The network condition of the first application server or the network condition of the second application server may both refer to the network conditions described above.

Step A2, each first application server sends migration completion time of the application context of the terminal to the first network element. Correspondingly, the first network element acquires the migration completion time of the application context of each first application server aiming at the terminal from each first application server.

In an embodiment of the present application, before step A2, a method provided in an embodiment of the present application may further include: and the first application server determines the migration completion time of the application context of the terminal according to one or more of the first relevant information, the second relevant information and the size of the application context.

The first related information related to the embodiment of the present application may refer to various information related to the first application server, which may affect the migration completion time of the application context, and is not limited to one or more of location information, load information, or network conditions corresponding to the first application server.

If the first application server does not obtain the size of the second relevant information and the application context from the first network element, the first application server may request the size of the second relevant information and the application context from the first network element/the second application server or the first enabling server, which is not limited in this embodiment of the application.

In one possible implementation of the present application, if each first application server actively sends the migration completion time of the respective application context for the terminal to the first network element, the above step A1 may be omitted.

In another possible implementation of the present application, in case that the first network element requests each first application server to send a respective migration completion time of the application context for the terminal to the first network element, then step A1 is retained. Also in this case, the first network element may first send the first request message. The first network element then provides one or more of second relevant information of the second application server, and a size of the application context to the first application server based on the feedback of each first application server. For example, if the first network element sends the first request message to the first application server 1 and the first application server 2, and the first application server 1 feeds back that the size of the application context does not exist at the first application server 1, the first network element may send the size of the application context to the first application server 1 again. If the first application server 2 does not have the location information of the second application server as fed back by the first application server 2, the first network element may send the location information of the second application server to the first application server 2 again.

It should be noted that, each first application server may obtain, from the first network element, one or more of the second related information of the second application server and the size of the application context, and may also obtain, from another network element (for example, the second application server or the first enabling server), one or more of the second related information of the second application server and the size of the application context, which is not limited in this embodiment of the present application. For example, after receiving the first request message, the first application server obtains one or more of second relevant information of the second application server and the size of the application context from the second application server.

This case 1) may be applicable to scenario 1) and scenario 2) above, in scenario 1), before sending the first request message, the first network element may further: and acquiring one or more of second relevant information of the second application server and the size of the application context from the second application server.

In scenario 2), before the first network element performs step A1, the following steps may also be performed: the first network element obtains one or more of second related information of the second application server and the size of the application context from the first enabling server.

In an optional embodiment of the present application, the first enabling server and/or the second application server may actively send one or more of the second relevant information of the second application server, and the size of the application context to the first network element.

For example, the second enabling server/the first enabling server and/or the second application server may store one or more items of the second related information and/or the application context size in advance. Alternatively, the first enabling server may obtain one or more of the second relevant information and/or the application context size from the second application server.

The second enabling server may store the first related information of each first application server in advance, so that the step of the second enabling server acquiring one or more items of the first related information from each first application server may be omitted.

In an optional embodiment of the present application, before the first network element obtains one or more of second relevant information of the second application server and a size of the application context from the first enabling server and/or the second application server, the method provided in an embodiment of the present application may further include: the first network element sends a third request message to the first enabling server and/or the second application server. Accordingly, the first enabling server and/or the second application server receives the third request message from the first network element.

Wherein the third request message is used for requesting one or more of second related information of the second application server and the size of the application context.

Optionally, the third request message includes third indication information, where the third indication information is used to request one or more of second relevant information of the second application server and a size of the application context.

As an example, the first network element may obtain an identification of the first enabling server or an identification of the second application server from the second network element. The identifier of the first enabling server or the identifier of the second application server may be provided by the second network element to the first network element actively, or may be provided by the second network element to the first network element based on a request of the first network element, which is not limited in this embodiment of the application.

As an example, the identification of the first enabled server may be address information of the first enabled server. For example, the address information of the first enabling server may be an IP address, a Full Qualified Domain Name (FQDN), a Uniform Resource Identifier (URI), and the like.

The identity (such as ID) of the second application server is used to identify a specific service, e.g. SA6 video, SA6 game, etc. Application servers that may provide a particular service share the identity of the same application server.

Case 2), the first network element receives a migration completion time of the application context of the terminal from the third network element.

In an embodiment of the present application, another process for determining a migration completion time of an application context of each first application server for a terminal is provided in an embodiment of the present application. The process comprises the following steps:

step A3, the first network element sends a second request message to the third network element, and correspondingly, the third network element receives the second request message from the first network element.

The second request message is used for requesting the migration completion time of each first application server for the application context of the terminal.

In one possible implementation, the second request message includes second indication information, and the second indication information is used for requesting migration completion time of each first application server for the application context of the terminal.

In one possible implementation, the second request message includes: one or more of first related information of each first application server, second related information of the second application server, and a size of the application context. This avoids the third network element collecting the information of the migration completion time of the computing application context by itself.

In a possible implementation, in a scenario where the enabling server is not replaced, the second request message may further include identification or address information of each first application server and/or identification or address information of the second application server. In this way, even if the first network element does not provide the third network element with one or more of the first related information of each first application server, the second related information of the second application server, and the size of the application context, the third network element may obtain the respective first related information from each first application server according to the identification or address information of each first application server. And/or the third network element may obtain one or more of second relevant information of the second application server and the size of the application context from the second application server according to the identification or address information of the second application server.

Alternatively, in a scenario of replacing the enabling server, the second request message may include: identification or address information of each first application server, identification or address information of a first enabling server, identification or address information of a second application server. In this way, the third network element may obtain one or more of the second relevant information of the second application server and the size of the application context from the first enabling server according to the identification or address information of the first enabling server.

For example, the third network element is a network element capable of determining a migration completion time of the application context of each first application server for the terminal. For example, the third network element is a data analysis network element, an edge configuration server, a Policy Control Function (PCF) network element, or an open network function (NEF) network element.

And step A4, the third network element determines the migration completion time of the application context of each first application server aiming at the terminal according to one or more of the first relevant information, the size of the application context and the second relevant information of each first application server.

It should be noted that, if the second request message does not carry one or more of the first related information, the size of the application context, and the second related information of each first application server, the third network element may collect the related information from the corresponding network element by itself, and the specific process may refer to the description in the following embodiment, and is not described herein again.

And step A5, the third network element sends the migration completion time of each first application server aiming at the application context of the terminal to the first network element. Accordingly, the first network element receives the migration completion time of the application context of each first application server for the terminal from the third network element.

In a possible embodiment of the present application, in this embodiment of the present application, the third network element may actively send the migration completion time of the application context of each first application server for the terminal to the first network element, where step A3 may be omitted.

This case 2) may be applicable to scenario 1) and scenario 2) above, in scenario 1), the first network element may further: and acquiring one or more of second relevant information of the second application server and the size of the application context from the second application server.

In scenario 2), before sending the second request message, the first network element may further: and acquiring one or more items of second relevant information of the second application server and the size of the application context from the first enabling server.

In case 2), the specific implementation of the first network element obtaining one or more of the second relevant information of the second application server and the size of the application context from the first enabling server and/or the second application server may refer to the description in case 1), which is not described herein again.

In case 2) the first network element may further, before sending the second request message: and acquiring respective first related information of each first application server from each first application server.

In a possible embodiment of the application, each first application server actively sends respective first related information of each first application server to the first network element.

In another possible embodiment of the present application, before the first network element obtains the respective first relevant information of each first application server from each first application server, the method provided in this embodiment of the present application may further include: the first network element sends a fourth request message to each first application server, wherein the fourth request message is used for requesting the first relevant information of the first application server.

It should be noted that, in the case that each first application server actively sends the respective first related information to the first network element, the process of sending the fourth request message by the first network element may be omitted.

As an example, the fourth request message includes fourth indication information, and the fourth indication information is used for requesting the first relevant information of the first application server.

Case 3), determining, by the first network element, a migration completion time of the application context of each first application server for the terminal.

In an embodiment of the present application, the present application provides a further procedure in which the first network element determines a migration completion time of an application context of each first application server for the terminal. The process comprises the following steps:

in the mode 3-1, the first network element obtains one or more of the first relevant information of each first application server, the second relevant information of each second application server, and the size of the application context.

In one possible embodiment of the present application, the above-mentioned mode 3-1 can be implemented by: the first network element obtains one or more of second relevant information of the second application server and the size of the application context from the second application server and/or a first enabling server, and the first enabling server is associated with the second application server.

Specifically, in the case that the first network element is the second enabling server, the first network element obtains one or more of the second relevant information of the second application server and the size of the application context from the first enabling server and/or the second application server. At this time, the first enabling server may obtain one or more of second relevant information of the second application server and the size of the application context from the second application server.

And in the case that the first network element is the third enabling server, the first network element acquires one or more of second related information of the second application server and the size of the application context from the second application server.

In one possible implementation, the second application server and/or the first enabling server may actively send one or more of second related information of the second application server, a size of the application context to the first network element.

In another possible implementation, the second application server and/or the first enabling server receives a request message from the first network element, the request message requesting one or more of second relevant information of the second application server, a size of the application context. And then, the second application server and/or the first enabling server sends one or more of second relevant information of the second application server and the size of the application context to the first network element.

Based on this, before the first network element receives one or more of the second relevant information from the second application server and/or the second application server of the first enabling server, and the size of the application context, the method provided in this embodiment of the present application may further include: and the first network element sends a third request message to the second application server and/or the first enabling server, and correspondingly, the second application server and/or the first enabling server receives the third request message from the first network element.

For the first enabling server, the first enabling server may obtain one or more of second relevant information of the second application server and size of the application context from the second application server. The second application server may send one or more of second related information of the second application server, a size of the application context to the first enabling server on its own initiative or based on a request of the first enabling server.

In the mode 3-2, the first network element determines the migration completion time of the application context of each first application server for the terminal according to one or more of the first relevant information of each first application server, the second relevant information of the second application server, and the size of the application context.

One possible specific implementation manner is that the first network element determines an application context transmission bit rate between the first application server and the second application server according to the first relevant information and the second relevant information, and then calculates a migration completion time of the application context according to the transmission bit rate and the size of the application context, for example, the migration completion time of the application context is equal to the product of the size of the application context and the application context transmission bit rate.

In case 3), the first network element obtaining the first related information of each first application server may be implemented by: the first network element sends a fourth request message to each first application server, wherein the fourth request message is used for requesting the first relevant information of the first application server. The first network element receives respective first related information of each first application server.

The above describes the process of the first network element obtaining the migration completion time of the application context of each first application server for the terminal from different angles, respectively.

In a possible embodiment of the present application, in a scenario of replacing an enabling server, in a case that a first network element is a second enabling server, and a second network element is an enabling client, a method provided in an embodiment of the present application further includes: the second network element sends an identification (such as address information) of the first enabling server to the first network element. Accordingly, the second network element receives the identification of the first enabling server from the first network element. Providing the identity of the first enabling server facilitates the first network element in determining that the terminal was previously served by the first enabling server, and one or more of the size of the application context and the second related information of the second application server may be obtained from the first enabling server.

As shown in fig. 7, fig. 7 is another communication method provided in the embodiment of the present application, where the communication method includes:

step 701, the first network element obtains the second information.

Wherein the second information includes one or more of first related information of each of one or more first application servers associated with the first network element, second related information of the second application server, and size of the application context.

The application context is information of the first application aiming at the terminal on the second application server. The second application server is an application server currently providing services for the terminal. The second relevant information includes one or more of location information, load information, or network conditions of the second application server. The first relevant information includes one or more of location information, load information, or network conditions of the first application server.

Step 702, the first network element sends the second information to the second network element. Accordingly, the second network element receives the second information from the first network element. The second information is used for determining a target application server which provides services for the terminal in one or more first application servers.

As an example, the first network element may send a first message to the second network element, where the first message carries the second information.

In a possible implementation, if the first network element receives a second message from the second network element before performing step 701, the second message requesting the first network element to provide information required for determining the migration completion time of the application context of the first application server for the terminal, the first message may be a response message to the second message. For example, the second message may be an EAS discovery request and the first message may be an EAS discovery response. For example, the second message is an EAS discovery subscription request, and the first message may be an EAS discovery notification or an EAS subscription response.

And step 703, the second network element determines a target application server providing services for the terminal from the one or more first application servers according to the second information.

In one possible implementation manner of the present application, step 703 may be implemented by: and the second network element determines the migration completion time of the application context of each first application server aiming at the terminal according to the second information. And the second network element determines a target application server for providing service for the terminal from one or more first application servers according to the migration completion time of the application context of each first application server for the terminal.

The embodiment of the application provides a communication method, in the process of replacing an application server providing services for a terminal from a second application server to a target application server, application context of the terminal on the second application server needs to be migrated to the target application server, although one or more first application servers can provide services for the terminal, because of difference of migration completion time required by migration of the application context to each first application server, the migration completion time can affect operation of a first application of the terminal due to temporary suspension or interruption of the application service of the terminal in the application context migration process, and based on the difference, a first network element obtains second information and provides the second information to a second network element. Since the second information comprises one or more of first related information of each of the one or more first application servers associated with the first network element, second related information of the second application server, and size of the application context. And the content included in the second information may be used to determine the migration completion time of each first application server for the application context of the terminal, so that after the first network element provides the second information to the second network element, the second network element is facilitated to determine, according to the second information, a target application server for providing a service for the terminal from the one or more first application servers.

In scenario 1) in combination with scenario 1) and scenario 2) described above, the first network element in the embodiment shown in fig. 7 may be a third enabling server. The second network element may be an enabling client or a second application server. As shown in fig. 1b, the third enabling server may be the enabling server 108. The second application server may be the origin application server 105. The enabled client may be the EEC103.

The first network element in the embodiment shown in fig. 7 in scenario 2) may be a second enabling server and the second network element may be an enabling client. The enabling client has now accessed the second enabling server. In all embodiments of scenario 2), alternatively, the first network element may be the second enabling server or the first enabling server, the first application server, the ECS. The second network element may be the first enabling server or the second application server. As shown in FIG. 1a, the second enabled server may be a target enabled server 102. The second application server may be the origin application server 105. The enabled client may be the EEC103. The first enabling server may be the source enabling server 101.

In one possible implementation manner of the present application, the step 701 may be implemented by: the first network element receives one or more of second relevant information, a size of the application context, from the second application server or a second application server of the first enabled server. The first enabling server is associated with a second application server.

In one possible implementation of the present application, the second application server or the first enabling server may actively send one or more of the second related information of the second application server, the size of the application context, to the first network element.

In one possible implementation of the present application, before the first network element receives one or more of second relevant information from the second application server or the second application server of the first enabling server, and a size of the application context, the method provided in the embodiment of the present application further includes: and the first network element sends a third request message to the second application server or the first enabling server, and correspondingly, the second application server or the first enabling server receives the third request message from the first network element. The third request message is used for requesting one or more of second related information of the second application server and the size of the application context.

For the content of the third request message, reference may be made to the description in the above embodiments, and details are not repeated here.

In one possible embodiment of the present application, the method provided in the embodiment of the present application further includes: the first network element receives address information of a first enabling server from a second network element, the first enabling server being associated with the second application server.

In a possible implementation of the present application, reference may be made to the description in the foregoing embodiment for a process of the first network element acquiring the first related information of each first application server, and details are not described here again.

In a possible embodiment of the present application, before the first network element obtains the first related information of each first application server, the method provided in the embodiment of the present application further includes: and the first enabling server sends a fifth request message to the first network element, and correspondingly, the first network element receives the fifth request message sent by the first enabling server. The fifth request message is used for requesting the first relevant information of at least one second application server associated with the first network element.

As an example, the fifth request message includes fifth indication information, and the fifth indication information is used for requesting the first related information of the at least one second application server associated with the first network element.

With reference to scenario 1) above, taking the first network element as a third enabling server, the second network element as an EEC, the first application server as a T-EAS, and the second application server as an S-EAS, as shown in fig. 8, a method for selecting a T-EAS provided in an embodiment of the present application includes:

step 801, the EEC sends an EAS discovery request to the EES, and accordingly, the EES receives the EAS discovery request from the EEC. Wherein the EAS discovery request includes an identification of the EAS.

Optionally, the EAS discovery request may also include a migration completion time for the desired application context.

Step 802, the EES authenticates the EEC.

The specific implementation of step 802 may refer to the description in the prior art, and is not described herein again.

In case the authentication is passed, the EES discovers one or more T-EAS, step 803.

Step 804, the EES determines a migration completion time of each of the one or more T-EAS for the application context of the terminal.

In one possible implementation, step 804 may be implemented by: the EES acquires one or more of the size of the application context for the terminal on the S-EAS, and second related information of the S-EAS. The EES obtains first correlation information for each T-EAS. The EES determines a migration completion time of each T-EAS for the application context of the terminal according to one or more of the first correlation information of each T-EAS, the second correlation information of the S-EAS, and the size of the application context.

For example, taking T-EAS as T-EAS3 as an example, the EES determines the migration completion time of the application context of the T-EAS3 for the terminal according to one or more of the first relevant information of the T-EAS3, the size of the application context, and the second relevant information of the S-EAS.

As a possible implementation: one or more of the EES acquiring the size of the application context for the terminal on the S-EAS and the second related information of the S-EAS may be implemented by the embodiment shown in fig. 10.

As a possible implementation: acquiring one or more of the first correlation information, the S-EAS second correlation information for each T-EAS with respect to the EES may be accomplished by the embodiment shown in fig. 11.

Optionally, after step 804, as shown in fig. 8, the method provided in the embodiment of the present application may further include: either of case a and case B. Therein, case a may include step 805a and step 806a. Case B may include step 805B and step 806B.

Step 805a, the EES selects T-EAS1 according to the migration completion time of each T-EAS application context for the terminal.

As an example, one possible option is that the migration completion time of the application context for the terminal of the T-EAS1 selected by the EES is the shortest of the one or more T-EAS. Alternatively, another possible option is that the migration completion time of the application context for the terminal of the T-EAS1 selected by the EES is lower than the expected migration completion time of the application context, which is not limited in this embodiment of the present application. T-EAS1 may then represent at least one T-EAS having an application context migration completion time lower than the expected application context migration completion time.

Step 806a, the EES sends an EAS discovery response to the EEC. Accordingly, the EEC receives an EAS discovery response from the EES. Wherein the EAS discovery response includes information for T-EAS1. For example, the information of T-EAS1 is used to identify T-EAS1. For example, the information of T-EAS1 may be address information, identification, etc. of T-EAS1.

Optionally, in the case that the information of the T-EAS1 is included in the EAS discovery response, the EES may further send information indicating a migration completion time of the application context for the terminal by the T-EAS1 to the EEC. For example, the information indicating the migration completion time of the application context of the terminal by the T-EAS1 may be the migration completion time of the application context of the terminal by the T-EAS1, or one or more of the first relevant information of the T-EAS1, the second relevant information of the S-EAS, and the size of the application context, which is not limited in this embodiment of the present application.

As an example, information indicating the migration completion time of the application context of the T-EAS1 for the terminal is carried in the EAS discovery response to save signaling overhead between network elements.

By executing step 805a and step 806a after step 804, the embodiment of the present application may select, by the EES, the T-EAS1 capable of providing the service to the terminal according to the migration completion time of each T-EAS application context for the terminal.

Optionally, after step 804, as shown in fig. 8, the method provided in the embodiment of the present application may further include: step 805b and step 806b.

Step 805b, the EES sends an EAS discovery response to the EEC. Accordingly, the EEC receives an EAS discovery response from the EES.

Wherein, the EAS discovery response comprises the migration completion time of each T-EAS in the one or more T-EAS aiming at the application context of the terminal.

In one possible implementation, the EAS profile for each T-EAS may also be included in the EAS discovery response.

It should be noted that the migration completion time of the application context of a T-EAS for a terminal may be included in the EAS profile of the T-EAS or may not be included in the EAS profile. For example, the migration completion time of the application context of the terminal by the T-EASn may be contained in the EAS profile of the T-EASn.

Step 806b, the EEC selects T-EAS2 from the one or more T-EAS based on the migration completion time of each T-EAS application context for the terminal.

It should be noted that, for the specific implementation of step 806b, reference may be made to the specific implementation of step 805a, and details are not described here. T-EAS2 and T-EAS1 may be the same T-EAS or different T-EAS.

It should be noted that after step 804, if the EES performs step 805a and step 806a, step 805b and step 806b may be omitted, or if the EES performs step 805b and step 806b, step 805a and step 806a may be omitted, which is not limited in this embodiment of the present application.

In one embodiment of the present application, after the EES determines a migration completion time of each T-EAS application context for the terminal, the EES may screen at least one T-EAS from the one or more T-EAS. Then, the EES transmits migration completion time of each of the at least one T-EAS for the application context of the terminal to the EEC. For example, the EES may reject the T-EAS with the highest migration completion time or reject the T-EAS higher than a preset time threshold value, so as to screen out at least one T-EAS.

In the embodiment shown in fig. 8, if the EAS discovery request in step 801 carries the migration completion time of the expected application context, when step 803 is executed, the EES discovers the T-EAS according to the migration completion time of the expected application context received in step 801, for example, the discovered T-EAS must be a T-EAS which can satisfy that the migration time of the application context is less than or equal to the migration completion time of the expected application context; or after step 804, the EES determines information of at least one or more T-EAS from the migration completion time corresponding to the one or more T-EAS determined in step 804 according to the migration completion time of the expected application context received in step 801. After step 804, the EES sends information of at least one T-EAS to the EEC. The EES may not perform either of case a and case B at this time. Optionally, the migration completion time of the application context of the at least one T-EAS for the terminal is less than or equal to the migration completion time of the expected application context.

Migration completion time of the expected application context carried in the EAS discovery request. The expected migration completion time of the application context indicates a need for a migration time of the application context for discovery or selection of the T-EAS. As a specific example, if the expected migration completion time of the application context is 10 ms, it means that the application context migration time between the found or selected T-EAS and S-EAS cannot exceed 10 ms.

With reference to scenario 1, as shown in fig. 9, another method for selecting T-EAS provided in this embodiment of the present application is exemplified by taking a first network element as an EES, a second network element as an EEC, a first application server as T-EAS, and a second application server as S-EAS, and the method includes:

step 901, execute the complete EEC to subscribe EAS discovery procedure to the EES. The process is prior art and aims to trigger an EAS discovery notification process when a trigger condition is met.

Step 902, the EAS discovery notification trigger condition is satisfied, and the EES triggers the notification process.

For example, optionally, in step 902, the EEC sends the migration completion time of the expected application context to the EES.

Step 903, the EES discovers one or more T-EAS.

Step 904 and step 804 are not described herein again.

Step 905a and synchronization step 805a, which are not described herein again.

Step 906a, the EES sends an EAS discovery notification to the EEC. Accordingly, the EEC receives an EAS discovery notification from the EES. Wherein the EAS discovery notification includes information of T-EAS 1.

Optionally, the information content carried in the EAS discovery notification may refer to the message content carried in the EAS discovery response in step 806a, which is not described herein again.

By executing step 905a and step 906a after step 904, the embodiment of the present application may select, by the EES, the T-EAS capable of providing the service to the terminal according to the migration completion time of each T-EAS application context for the terminal.

Optionally, after step 904, the embodiment shown in fig. 9 may further include step 905b and step 906b.

Step 905b, the EES sends an EAS discovery notification to the EEC. Accordingly, the EEC receives an EEC send EAS discovery notification from the EES. Wherein, the EAS discovery notification includes a migration completion time of each of the one or more T-EAS for the application context of the terminal.

Optionally, an EAS profile for each T-EAS may also be included in the EAS discovery response.

It should be noted that the migration completion time of the application context for the terminal by a T-EAS may or may not be included in the EAS profile of the T-EAS.

Step 906b, the EEC selects T-EAS2 from the one or more T-EAS according to the migration completion time of each T-EAS for the application context of the terminal.

It should be noted that, after the step 904, if the EES performs the step 905a and the step 906a, the step 905b and the step 906b may be omitted, or if the EES performs the step 905b and the step 906b, the step 905a and the step 906a may be omitted, which is not limited in the embodiment of the present application.

In the embodiment shown in fig. 9, if the EAS discovery request in step 901 carries the migration completion time of the expected application context, when step 903 is executed, the EES discovers T-EAS according to the migration completion time of the expected application context received in step 901. For example, the discovered T-EAS must be one that can satisfy an application context migration time less than or equal to the expected application context migration completion time; or after step 904, the EES determines information of at least one or more T-EAS from the migration completion time corresponding to the one or more T-EAS determined in step 904 according to the migration completion time of the expected application context received in step 901. Following step 904, the EES sends information of at least one T-EAS to the EEC. The EES may not perform either of case a and case B at this time. Optionally, the migration completion time of the application context of the at least one T-EAS for the terminal is less than or equal to the migration completion time of the expected application context.

The embodiment shown in fig. 9 differs from the embodiment shown in fig. 8 in that: in fig. 8, the "request-response" model is based on the EEC initiated T-EAS discovery procedure, while fig. 9 is based on the "subscription procedure" of the EAS discovery subscription-notification model.

As shown in fig. 10, fig. 10 is a flowchart for an EES provided in an embodiment of the present application to acquire one or more of a size of an application context for a terminal and second related information of the S-EAS, where the method includes:

step 1001, EES sends request message 1 to S-EAS. Accordingly, the S-EAS receives the request message 1 from the EES.

Wherein the request message 1 is used for requesting one or more of the size of the application context of the terminal, and the second related information of the S-EAS. For example, the request message 1 may include an identifier of the terminal, so that the S-EAS determines the terminal corresponding to the size of the application context provided to the EES, for example, the application context of multiple applications exists on the S-EAS, and then the S-EAS provides the application context of the multiple applications to the EES as the application context of the terminal, which may be referred to as a terminal-granular application context. Or the request message 1 may further include an identification of the first application, which facilitates the S-EAS to determine the size of the application context of the first application providing the terminal to the EES, which may be referred to as application context of application granularity. Or the request message 1 may further include an identifier of the EEC, so that the S-EAS determines the EEC corresponding to the application context provided to the EES.

As an example, in case the EES stores location information of S-EAS, the request message 1 is used to request one or more of size of application context, load information of S-EAS, network condition.

As another example, in case the EES does not store location information of the S-EAS, the request message 1 may be used to request location information of the S-EAS in addition to one or more of size of application context, load information of the S-EAS, and network condition of the S-EAS. Of course, in the case of having the size of the application context and the load information of the S-EAS in the EES, the request message 1 is used to request one or more of the network condition of the S-EAS and the location information of the S-EAS.

Step 1002, the S-EAS sends a response message 1 to the EES. Accordingly, the EES receives the response message 1 from the S-EAS. Wherein, the response message 1 includes one or more of the size of the application context, and the second related information of the S-EAS.

It should be noted that in a scenario where the S-EAS actively provides the EES with one or more of the second relevant information of the S-EAS and the size of the application context, the step 1001 may be omitted.

As shown in fig. 11, fig. 11 is a flowchart for acquiring first relevant information of each T-EAS by an EES according to an embodiment of the present application, and in fig. 11, for example, one or more T-EAS include T-EAS1, … T-EASn, the method includes:

Step 1101, EES sends request message 2 to each of T-EAS1, … T-EASn. Accordingly, each T-EAS receives request message 2 from the EES.

Wherein the request message 2 is used to request one or more of load information, location information, network conditions of the T-EAS.

It should be noted that the request message 2 sent by the EES to different T-EAS devices may or may not have the same requested content. For example, if the EES does not have the location information of T-EAS1 but has the location information of T-EAS2, the request message 2 sent by the EES to the T-EAS1 is also used to request the location information of the T-EAS1, but the request message 2 sent by the EES to the T-EAS2 does not need to request the location information of the T-EAS 2.

As an example, the request message 2 includes indication information 2, and the indication information 2 is used for requesting one or more of load information, location information, and network condition of the T-EAS.

Step 1102, each T-EAS sends a response message 2 to the EES. Accordingly, the EES receives a response message 2 from each T-EAS.

Wherein, the response message 2 of one T-EAS comprises one or more of the load information, the position information and the network condition of the T-EAS.

It should be noted that the information provided by different T-EAS devices to the EES may be the same or different, for example, T-EAS1 provides the EES with the load information, network status, and T-EAS2 provides the EES with the load information, network status, and location information of T-EAS 1. Alternatively, T-EAS1 and T-EAS2 each provide respective load information and network conditions to the EES.

It is noted that the step 1101 may be omitted in a scenario where the T-EAS actively provides one or more of load information, location information, and network conditions of the T-EAS to the EES.

It should be noted that fig. 11 only illustrates the information required by the EES to obtain from the S-EAS, but of course, the EES in fig. 11 may be replaced by S-EES/T-EES, and similarly, in a scenario where no EAS replacement occurs, the T-EAS may be replaced by the EAS currently serving the terminal.

In conjunction with scenario 2, due to overload of the mobile terminal or the EES (which may be referred to as S-EES and corresponds to the first enabling server in this application) currently serving the terminal, or due to shutdown or failure of the S-EES, or other reasons, the S-EES may no longer serve the terminal, or may no longer be the EES best suited to serve the terminal. At this time, the EEC first triggers a service provisioning (service provisioning) procedure, in which the EEC interacts with the ECS to obtain the identification and address information of the T-EES. It is understood that the T-EES is an EES capable of providing a service to the terminal. In this case, it is assumed that the EEC has access to the T-EES. Then, as shown in fig. 12, taking the first network element as a T-EES, the second network element as an EEC, the first application server as a T-EAS, and the second application server as an S-EAS as an example, a method for selecting a T-EAS provided in this embodiment of the present application includes:

Step 1201, the EEC obtains the address information of the T-EES and accesses the T-EES.

For example, step 1201 may be implemented as follows: the manner of acquiring the T-EES address information by the EEC may be to acquire the T-EES address information from the ECS through a service provisioning process.

Step 1202, EEC sends an EAS discovery request to T-EES. Accordingly, the T-EES receives an EAS discovery request from the EEC.

The EAS discovery request in step 801 differs from the EAS discovery request in step 1202 in that at least one of the following two of the EAS discovery requests in step 1202:

(1) Location information of the S-EAS. The location information may be a geographic location (e.g., latitude and longitude, neighborhood, etc.), a topological location (e.g., TA ID, cell ID, etc.), or access information (e.g., DNAI, etc.). Wherein, the S-EAS is the EAS currently serving the terminal, i.e. the EAS serving the terminal before the terminal accesses the T-EAS.

(2) Address information for the S-EES, and the S-EAS ID. Wherein, the address information of the S-EES can be IP address, FQDN, URI and the like; the S-EAS ID identifies a particular service, such as SA6 video, SA6 gaming, etc. EAS that may provide a particular service share the same EAS ID.

Optionally, the EAS discovery request may also include an identification of the S-EAS.

Steps 1203 to 1205, and steps 802 to 804 are not described herein again.

Steps 1206a to 1207b, and synchronization steps 805a to 806a, which are not described herein again.

Step 1206b to step 1207b, and step 805b to step 806b, which are not described herein again.

In the embodiment shown in FIG. 12, if the EAS discovery request in step 1202 carries the expected migration completion time of the application context. The steps following step 1205 may be replaced by the following steps: the T-EES transmits information of at least one T-EAS to the EEC. Optionally, the migration completion time of the application context of the at least one T-EAS for the terminal is less than or equal to the migration completion time of the expected application context.

In the embodiment shown in fig. 12, if the EAS discovery request in step 1202 carries the migration completion time of the expected application context, when step 1204 is executed, the T-EES discovers the T-EAS according to the migration completion time of the expected application context received in step 1202, for example, the discovered T-EAS must be a T-EAS which can satisfy that the migration time of the application context is less than or equal to the migration completion time of the expected application context. Or if the EAS discovery request in step 1202 carries the expected migration completion time of the application context, after step 1205, the T-EES determines information of at least one or more T-EAS from the migration completion time corresponding to the one or more T-EAS determined in step 1205 according to the expected migration completion time of the application context received in step 1202. After step 1205, the T-EES sends information of at least one T-EAS to the EEC. At this time, the T-EES may not perform either of case A and case B. Optionally, the migration completion time of the application context of the at least one T-EAS for the terminal is less than or equal to the migration completion time of the expected application context.

With reference to scenario 2, taking the first network element as a T-EES and the second network element as an EEC as an example, as shown in fig. 13, another method for selecting a T-EAS provided in this embodiment of the present application includes:

a subscription flow part and a notification part, wherein the subscription flow part comprises steps 1301 to 1303, and the notification part comprises steps 1304 to 1307b:

step 1301, the EEC discovers the T-EES.

For the specific implementation of step 1301, reference may be made to the description in step 1201 above, and details are not described here again.

Step 1302, the EEC sends an EAS discovery subscription request to the T-EES. Accordingly, the T-EES receives an EAS discovery subscription request from the EEC. The EAS discovery subscription request is for subscribing to the second information. The second information is used to determine a migration completion time of each T-EAS application context for the terminal.

And step 1303, the T-EES sends an EAS subscription response to the EEC under the condition that the authentication is passed. Accordingly, the EEC receives the EAS subscription response from the T-EES.

The EAS subscription response is used to notify the EEC that the subscription is successful (or the subscription is failed), and includes information such as the ID or valid time of the subscription.

Step 1304, T-EES triggers an EAS discovery notification.

Step 1305, the T-EES discovers one or more T-EAS.

Step 1306, the T-EES determines a migration completion time for each of the one or more T-EAS for the application context of the terminal.

For specific implementation of step 1306, reference may be made to the embodiment described in any one of fig. 14 to fig. 16, which is not described herein again.

Step 1307a to step 1308a, and synchronization step 905a to step 905b.

Step 1307b to step 1308b, and synchronization step 905b to step 906b.

In the embodiment shown in fig. 13, if the EAS discovery subscription request in step 1302 carries the expected migration completion time of the application context. The steps following step 1306 may be replaced by the steps of: the T-EES sends information of at least one T-EAS to the EEC. Optionally, the migration completion time of the application context of the at least one T-EAS for the terminal is less than or equal to the expected migration completion time of the application context.

In the embodiments shown in fig. 8 to 13, in the T-EAS discovery process, the EES/T-EES determine the migration completion time of each T-EAS for the application context of the terminal, and select one T-EAS according to the migration completion time corresponding to each T-EAS, or send the migration completion time corresponding to each T-EAS to the EEC, and the EEC selects the T-EAS according to the migration completion time corresponding to each T-EAS, thereby achieving the technical effect of selecting the T-EAS according to the migration completion time corresponding to each T-EAS.

As shown in fig. 14, a process of determining migration completion time corresponding to each T-EAS for a first network element in the embodiment of the present application is shown, where the method takes the first network element as a T-EES as an example, and the method includes:

step 1401, the T-EES sends a request message 3 to the S-EES. Accordingly, the S-EES receives the request message 3 from the T-EES.

Wherein the request message 3 is for requesting the size of the application context of the terminal and/or second related information of the S-EAS. Optionally, the request message 3 includes an identification of the S-EAS.

Optionally, the request message 5 includes indication information, where the indication information is used to request the size of the application context of the terminal and/or second relevant information of the S-EAS. Optionally, the request message 3 further includes an identifier of the terminal, so that the S-EES can provide the T-EES with the size of the application context of the terminal with granularity of the terminal and/or second related information of the S-EAS. Or the request message 3 also includes the identity of the first application. The S-EES may then provide the T-EES with the size of the application context of the terminal, and/or second relevant information of the S-EAS, as a strength of the first application of the terminal.

Step 1402, providing the size of the application context of the terminal and/or the second related information of the S-EAS to the T-EES in response to the request message 3,S-EES from the T-EES. Accordingly, the T-EES receives the size of the application context from the terminal of the S-EES, and/or second relevant information of the S-EAS.

It should be noted that the step 1401 may be omitted in case that the S-EES actively transmits the size of the application context of the terminal, and/or the second related information of the S-EAS to the T-EES.

It should be noted that in the case where the T-EES has the size of the application context of the terminal, and/or the second related information of the S-EAS, the above-mentioned steps 1401 and 1402 may be omitted. In case the T-EES does not have the size of the application context of the terminal and/or the second related information of the S-EAS, then steps 1401 and 1402 need to be performed.

It should be noted that, in the case that the size of the application context of the terminal is not included in the S-EES, and/or the second related information of the S-EAS is not included in the S-EES, the method may further include: and the S-EES obtains the size of the application context of the terminal and/or second related information of the S-EAS from the S-EAS.

Step 1403, T-EES discovers one or more T-EAS.

Step 1404, the T-EES sends a request message 4 to each T-EAS. Accordingly, each T-EAS receives a request message 4 from a T-EES.

Wherein the request message 4 is for requesting first relevant information of the T-EAS. It is worth mentioning that the request message 4 does not need to request the location information of the T-EAS if the T-EES has the location information of the T-EAS stored therein.

Step 1405, each T-EAS providing respective first correlation information to the T-EESs.

It should be noted that if at least one of each of the T-EAS devices actively sends the first correlation information to the T-EES, then the T-EES does not need to perform step 1404.

And step 1406, the T-EES determines the migration completion time of the application context of each T-EAS aiming at the terminal according to one or more of the first relevant information, the second relevant information and the size of the application context of each T-EAS.

It should be noted that, the above steps 1401 to 1402 and the steps 1404 to 1405 do not distinguish a sequence, and only the T-EES can acquire the above information before executing the step 1406, which is not limited in this embodiment of the present application.

In the embodiment shown in fig. 14, the T-EES determines the migration completion time of the application context for the terminal by acquiring the respective first related information of each T-EAS from each T-EAS, and the size of the application context and the second related information of the S-EAS. Wherein, the T-EES acquires the load information of the T-EAS from the T-EAS, acquires the position information of the T-EAS from the T-EES or the T-EAS, and acquires the size of the application context and the second related information of the S-EAS from the S-EES or the flow for calling the embodiment.

As shown in fig. 15, fig. 15 is another method for determining a migration completion time of each T-EAS application context for a terminal according to an embodiment of the present application, where in fig. 15, for example, one or more T-EAS include T-EAS1, … …, and T-EAS2n, where n is an integer greater than or equal to 1, the method includes:

step 1501 to step 1503, and synchronization step 1401 to step 1403, which are not described herein again.

Step 1504a, the T-EES sends a request message 5 to the T-EAS1, and accordingly, the T-EAS1 receives the request message 5 from the T-EES.

Wherein the request message 5 is for requesting the T-EAS1 for a migration completion time of the application context of the terminal.

Optionally, the request message 5 carries the size of the application context and second related information of the S-EAS.

Step 1505a, the T-EAS1 determines the migration completion time of the application context of the T-EAS1 for the terminal according to one or more of the second related information of the S-EAS, the first related information of the T-EAS1 and the size of the application context.

It is worth mentioning that if the T-EES does not provide the size of the application context, the second relevant information of the S-EAS to the T-EAS1, the T-EAS1 may further obtain the size of the application context, the second relevant information of the S-EAS from the T-EES/S-EAS after receiving the request message 5.

Step 1506a, T-EAS1 sends T-EAS1 migration completion time for the application context of the terminal to T-EES. Accordingly, the T-EES receives the migration completion time of the application context of the T-EAS1 for the terminal from the T-EAS 1.

Step 1504b, the T-EES sends a request message 6 to the T-EASn. Accordingly, T-EAS2 receives request message 6 from the T-EES. Wherein the request message 6 is used for requesting the migration completion time of the application context of the terminal for the T-EAS 2.

Optionally, the request message 6 carries the size of the application context and second related information of the S-EAS.

Step 1505b, the T-EASn determines a migration completion time of the application context of the T-EASn for the terminal according to the second related information of the S-EAS, and one or more of the first related information of the T-EASn and the size of the application context.

And step 1506b, the T-EASn sends the migration completion time of the application context of the T-EASn aiming at the terminal to the T-EES. Accordingly, the T-EES receives the migration completion time of the T-EAS2 for the application context of the terminal from the T-EASn.

For the specific implementation of step 1505 b-step 1506b, reference may be made to the description of step 1505 a-step 1506a, which is not described herein again.

Fig. 16 is another method for determining a migration completion time of each T-EAS application context for a terminal according to an embodiment of the present application, where fig. 16 takes as an example that one or more T-EAS include T-EAS1, …, and T-EASn, and the method includes:

Step 1601 to step 1603, and step 1401 to step 1403 are synchronized, and are not described here again.

Step 1604a, the T-EES sends a request message 7 to T-EAS 1. Accordingly, T-EAS1 receives request message 7 from the T-EES.

Wherein the request message 7 is used to request the first relevant information of the T-EAS 1. For example, the request message 7 carries indication information 7, and the indication information 7 is used for requesting the first relevant information of the T-EAS 1.

Step 1605a, T-EAS1 sends one or more of load information, location information, network conditions of T-EAS1 to T-EES. Accordingly, the T-EES receives one or more of load information, location information, network conditions of the T-EAS1 from the T-EAS 1.

Step 1604b, the T-EES sends a request message 8 to the T-EASn. Accordingly, T-EASn receives the request message 8 from T-EES.

Wherein the request message 8 is used for requesting the first related information of the T-EASn. For example, the request message 8 carries indication information 8, where the indication information 8 is used to request the first relevant information of T-EASn.

It is worth noting that T-EES can obtain the load information of T-EAS1, but obtain the load information and the position information of T-EASn.

Step 1605b, T-EASn sends one or more items of load information, location information and network condition of T-EASn to T-EES. Accordingly, the T-EES receives one or more of load information, location information, network conditions of the T-EASn from the T-EASn.

Step 1606, the T-EES sends a request message 9 to the ECS or NWDAF network element. Accordingly, the ECS or NWDAF network element receives the request message 9 from the T-EES.

Wherein the request message 9 is used for requesting the migration completion time of each T-EAS in the T-EAS1, … and T-EASn for the application context of the terminal. Optionally, the request message 9 carries indication information 9. This indication information 9 is used to request the migration completion time of each of the T-EAS1, …, T-EASn for the application context of the terminal.

Optionally, the request message 9 includes one or more of the following information: first correlation information of each T-EAS, size of application context, second correlation information of S-EAS.

It should be noted that, in the case where the T-EES has the first correlation information for each T-EAS, the above steps 1604a to 1605a and steps 1604b to 1605b may be omitted. If there is a portion of the first correlation information for the T-EAS on the T-EES, then the step of obtaining the first correlation information from the T-EAS may be omitted.

It should be noted that, in the case where there is the size of the application context in the T-EES or the second related information of the S-EAS, the above steps 1601 to 1602 may be omitted.

Step 1607, the ECS or NWDAF network element determines the migration completion time of the application context of each T-EAS for the terminal according to one or more of the first relevant information of each T-EAS, the second relevant information of the S-EAS, and the size of the application context.

It should be noted that, in the case that the first relevant information of each T-EAS, the size of the application context, and the second relevant information of S-EAS are not included in the request message 9, the ECS or NWDAF network element may further include, before performing step 1607: and the ECS or NWDAF network element acquires one or more of the first relevant information of each T-EAS, the second relevant information of each S-EAS and the size of the application context. As an example, the ECS or NWDAF network element may obtain one or more of the first relevant information of each T-EAS, the second relevant information of each S-EAS, and the size of the application context from the T-EES, and then the T-EES may obtain the required information by performing steps 1601 to 1602, steps 1604a to 1605a, steps 1604b to 1605b, and so on, and provide the information to the ECS or NWDAF network element. As another example, the ECS or NWDAF network element may obtain respective first correlation information for each T-EAS from each T-EAS and second correlation information for the size of the application context, S-EAS, from the S-EAS or S-TEES. An identification such as address information for S-EAS or S-TEES may be provided by the T-EES to the ECS or NWDAF, such as an identification such as address information for S-EAS or S-TEES carried in the request message 9.

Step 1608, the ECS or NWDAF network element provides the migration completion time for the application context of each T-EAS for the terminal to the T-EES.

It is worth mentioning that the ECS or NWDAF network element may be replaced by any non-edge deployment and may determine the migration completion time of each T-EAS for the application context of the terminal according to the application context size and the location and load information of the S-EAS and each T-EAS, for example, the ECS or NWDAF network element may be replaced by a NEF network element or a PCF network element.

With reference to scenario 1) above, taking the first network element as a third enabling server (e.g., an EES), the second network element as an EEC, the first application server is a T-EAS, and the second application server is an S-EAS, as shown in fig. 17, for example, a method for selecting a T-EAS provided in an embodiment of the present application includes:

step 1701 to step 1703, and step 801 to step 803 are synchronized, and are not described herein again.

In step 1704, the EES determines one or more of location information, load information, or network conditions for each of the one or more T-EAS devices.

For specific implementation of step 1704, reference may be made to the related description in the embodiment shown in fig. 11, and details are not repeated here.

It should be noted that if the EES has the location information, the load information or the network condition of each T-EAS, step 1704 may be omitted, and if the EES does not have the location information, the load information or the network condition of each T-EAS or only has part of the above information or the location information, the load information or the network condition of part of the T-EAS, the EES may obtain the rest of the required information in the manner shown in fig. 11.

Step 1705, the EES determines the size of the application context of the terminal and one or more of location information, load information or network conditions of the S-EAS.

For the implementation of step 1705, reference may be made to the description in the embodiment shown in fig. 10, and details are not repeated here.

It should be noted that if the EES has the size of the application context and the location information, the load information or the network condition of the S-EAS, the step 1705 may be omitted, and if the EES does not have the size of the application context and the location information, the load information or the network condition of the S-EAS or has only part of the above information, the EES may obtain the required information in the manner shown in fig. 10.

Step 1706, the EES sends an EAS discovery response to the EEC. Accordingly, the EEC receives an EAS discovery response from the EES.

Wherein the EAS discovery response includes one or more of the following information: a size of the application context, and one or more of location information, load information, or network conditions of the S-EAS, and one or more of location information, load information, or network conditions of each T-EAS.

Step 1707, EEC based on one or more of the following information: the size of the application context, and one or more of location information, load information, or network conditions of the S-EAS, and one or more of location information, load information, or network conditions of each of the T-EAS, selecting one of the T-EAS from the one or more T-EAS to serve the terminal.

As an example, step 1707 may be implemented by: the EEC is based on one or more of the following information: the method comprises the steps of determining the size of an application context, one or more of position information, load information or network conditions of S-EAS, one or more of position information, load information or network conditions of each T-EAS, and determining the migration completion time of the application context of a terminal respectively aimed at by each T-EAS. The EEC selects one T-EAS from one or more T-EAS to provide service for the terminal according to the migration completion time of the application context of the terminal for which each T-EAS is respectively aimed.

For example, the EEC determines the migration completion time of the application context of the terminal for which the T-EAS1 is intended, based on the size of the application context and one or more of the location information, load information, or network condition of the S-EAS, and one or more of the location information, load information, or network condition of the T-EAS 1.

With reference to scenario 2, taking a first network element as a T-EES, a second network element as an EEC, a first application server as a T-EAS, and a second network element as an S-EAS as examples, as shown in fig. 18, a method for selecting a T-EAS provided in an embodiment of the present application includes:

step 1801 to step 1804, and synchronization step 1201 to step 1204, which are not described herein again.

Step 1805, the EES determines one or more of location information, load information, or network conditions for each of the one or more T-EAS devices.

It should be noted that, in the embodiment shown in fig. 18, the detailed implementation of step 1805 may refer to the descriptions at step 1404 to step 1405, and is not described here again.

Step 1806, the EES determines the size of the application context and one or more of location information, load information or network conditions of the S-EAS.

It should be noted that, in the embodiment shown in fig. 18, the specific implementation of step 1806 may refer to the descriptions at step 1401 to step 1402.

Step 1807 to step 1808, and step 1706 to step 1707, which are not described herein again.

With reference to scenario 1, taking a first network element as an EES and a second network element as an EEC as an example, an embodiment of the present application provides another method for determining a T-EAS, as shown in fig. 19, where the method includes:

step 1901 to step 1903, and step 901 to step 903.

Step 1904 to step 1905, and step 1704 to step 1705, which are not described herein again.

Step 1906, EES sends an EAS discovery notification to the EEC. The EEC receives an EAS discovery notification from the EES.

Wherein the EAS discovery notification includes one or more of the following information: a size of the application context, and one or more of location information, load information, or network conditions of the S-EAS, and one or more of location information, load information, or network conditions of each T-EAS.

Step 1907 and synchronization step 1707, which are not described herein again.

In combination with scenario 2), taking a first network element as a T-EES and a second network element as an EEC as an example, the embodiment of the present application provides another method for determining a T-EAS, where the method includes:

step 2001, EEC finds T-EES.

For the specific implementation of step 2001, reference may be made to the description of step 1301, and details are not described here.

Step 2002, the EEC sends an EAS discovery subscription request to the T-EES. Accordingly, the T-EES receives an EAS discovery subscription request from the EEC. Wherein the EAS discovery subscription request is for subscribing to the second information. The second information is used to determine a migration completion time of each T-EAS application context for the terminal.

Optionally, the EAS discovery subscription request carries address information of the S-EES, so that the T-EES can determine the address of the S-EES that served the terminal before. Optionally, the EAS discovery subscription request further carries one or more of location information or identifiers of the S-EAS, so that the T-EES may determine which S-EAS is currently serving the terminal, so as to obtain, when performing step 2007, the size of the application context and one or more of location information, load information or network condition of the S-EAS from the S-EAS.

Step 2003, in case of passing the authentication, the T-EES sends an EAS subscription response to the EEC. Accordingly, the EEC receives an EAS subscription response from the T-EES.

The above-described steps 2001 to 2003 may be regarded as a subscription (Subscribe) process.

Step 2004, the T-EES triggers an EAS discovery notification.

In step 2005, the T-EES discovers one or more T-EAS's.

Reference may be made to the description of the other embodiments above, which are not repeated here.

Step 2006, the T-EES determines one or more of location information, load information, or network conditions for each of the one or more T-EAS.

For the specific implementation of step 2006, reference may be made to the related description at 1805, which is not described herein again.

Step 2007, the T-EES determines the size of the application context of the terminal, and one or more of location information, load information or network conditions of the S-EAS.

For specific implementation of step 2007, reference may be made to the related description at 1806, and details are not repeated here.

It is worth noting that step 2007 may be omitted if there is a size of the application context of the terminal at the T-EES, and one or more of location information, load information or network conditions of the S-EAS.

Step 2008 to step 2009, and step 1906 to step 1907, which are not described herein again.

In both the embodiment shown in fig. 20 and the embodiment shown in fig. 19, in scene 2, information X for determining the migration completion time of the application context of each first application server for the terminal is provided to the EEC by the T-EES. For example, the information X includes one or more of the following: an application context size, and one or more of location information, load information, or network conditions of the S-EAS, location information, load information, or network conditions of each T-EAS. A T-EAS serving the terminal is selected by the EEC based on the information X. The difference lies in that: the embodiment shown in FIG. 19 employs an EEC initiated T-EAS discovery flow "request-response" model. While figure 20 employs the EEC-initiated T-EAS discovery flow "subscribe-notify" model.

As shown in fig. 21, in combination with scenario 2, taking a first network element as a T-EES and a second network element as an S-EES as an example, an embodiment of the present application provides another method for selecting a T-EAS, where the method includes:

step 2101, S-EAS sends an EAS discovery request 10 to S-EES. Accordingly, the S-EES receives an EAS discovery request 10 from the S-EAS.

Wherein the EAS discovery request 10 is for requesting the S-EES to provide a migration completion time for each of the T-EAS that can serve the terminal for the application context of the terminal.

The EAS discovery request 10 includes the S-EAS ID, and the information used by the S-EAS side to determine the migration completion time, including but not limited to the following: one or more of location information of the S-EAS, load information of the S-EAS, network conditions of the S-EAS, and a size of an application context of the terminal.

If any of the information (e.g., location information for S-EAS) is also stored in the S-EES, then the information need not contain such information for S-EAS.

Step 2102, S-EES, upon receiving the EAS discovery request 10 from S-EAS, determines to perform ACR. I.e. the subsequent steps are performed.

It will be appreciated that steps 2102 and 2101 are performed if and only if the process is an S-EAS initiated T-EAS discovery process.

Step 2103, the S-EES interacts with the ECS to obtain the ID and address information of the T-EES so as to access the T-EES.

The specific implementation of step 2103 can refer to the description in the prior art, and is not described here again.

Step 2104, the S-EES sends an EAS discovery request 11 to the T-EES, which in turn receives the EAS discovery request 11 from the S-EES.

Wherein the EAS discovery request 11 is for requesting the T-EES to provide a migration completion time of each application context for the terminal in the discovered T-EAS.

As an example, the EAS discovery request 11 includes: location information of the S-EAS, network condition of the S-EAS, load information of the S-EAS, and size of the application context. Optionally, the EAS discovery request 11 may also include an identification of the S-EES, an identification of the S-EAS.

If step 2101 is performed, one or more of the location information of the S-EAS, the network condition of the S-EAS, the load information of the S-EAS, and the size of the application context may be acquired through step 2101, or the S-EES locally stores the location information of the S-EAS, the network condition of the S-EAS, the load information of the S-EAS, and partial information of the size of the application context.

If step 2101 is not performed, the S-EES may acquire all or part of the location information of the S-EAS, the network condition of the S-EAS, the load information of the S-EAS, and the size of the application context from the S-EAS by the method described in the embodiment shown in FIGS. 10 and 11.

Step 2105, the T-EES determines one or more T-EAS.

Step 2106, the T-EES determines a migration completion time for each of the one or more T-EAS for the application context of the terminal.

In an alternative embodiment of the present application, after step 2106, the embodiment shown in fig. 21 may further include step 2107a and step 2108a.

Step 2107a, the T-EES selects T-EAS1 according to the migration completion time of each T-EAS for the application context of the terminal.

By way of example, one possible selection manner is that the migration completion time of the application context of the T-EAS1 selected by the T-EES for the terminal is the shortest of one or more T-EAS, in which case the number of the selected T-EAS1 is one, or the migration completion time of the application context of the T-EAS1 selected by the T-EES for the terminal is lower than the migration completion time of the preset application context, which is not limited in the embodiment of the present application.

Step 2108a, the T-EES sends an EAS discovery response 11 to the S-EES, which in turn receives the EAS discovery response 11 from the T-EES. Among other things, EAS discovery response 11 is information of T-EAS1.

Optionally, in case that the information of T-EAS1 is included in the EAS discovery response 11, the T-EES may further transmit information indicating a migration completion time of the application context of the T-EAS1 for the terminal to the S-EES. For example, the information indicating the migration completion time of the application context of the terminal by the T-EAS1 may be the migration completion time of the application context of the terminal by the T-EAS1, which is not limited in this embodiment of the present application.

As an example, information indicating the migration completion time of the application context for the terminal by T-EAS1 is carried in the EAS discovery response 11.

Optionally, in the case that the embodiment shown in fig. 21 is triggered by S-EAS, then optionally, as shown in fig. 21, after step 2108a, the method may further include:

steps 2109a, S-EES send a discovery response message 10 to S-EAS. Accordingly, the S-EAS receives an EAS discovery response 10 from the S-EES. Among other things, the information of T-EAS1 in EAS discovery response 10.

It is noted that in the case where the embodiment shown in FIG. 21 is triggered by S-EES, then step 2109a may be omitted.

In an alternative embodiment of the present application, as shown in fig. 21, after step 2106, the method provided in this embodiment of the present application may further include:

step 2107b, the T-EES sends an EAS discovery response 12 to the S-EES. Accordingly, the S-EES receives an EAS discovery response 12 from the T-EES. Wherein the EAS discovery response 12 includes a migration completion time for each of the one or more T-EAS for the application context of the terminal.

Optionally, an EAS profile for each T-EAS may also be included in the EAS discovery response 12.

It should be noted that, in the case that the process of the present application is triggered by the S-EES, after step 2107b, optionally, the method provided in this embodiment of the present application further includes:

Step 2108b, the S-EES selects the T-EAS2 serving the terminal from the one or more T-EAS according to the migration completion time of each T-EAS for the application context of the terminal.

It is worth noting that in the case where the process of the present application is triggered by S-EAS, after step 2107b, the present application embodiment may perform either of the following cases C and D:

the case C includes steps 2108b to 2109b. Case D includes: step 2108c to step 2109c.

Step 2109b, the S-EES sends an EAS discovery response 13 to the S-EAS, which in turn receives the EAS discovery response 13 from the S-EES. Wherein the EAS discovery response includes information for T-EAS2. Optionally, the EAS discovery response 13 may further include a migration completion time of the application context of the terminal for T-EAS2.

It is worth noting that after the S-EAS receives the information of T-EAS2, the S-EAS may treat T-EAS2 as the EAS that serves the terminal, or if the S-EAS determines that T-EAS2 is not in demand, the above step 2101 may be re-executed.

Step 2108c, the S-EES sends an EAS discovery response 14 to the S-EAS, which in turn receives the EAS discovery response 14 from the S-EES. The EAS discovery response 14 includes therein the migration completion time of each T-EAS application context for the terminal.

Step 2109c, the S-EAS selects a T-EAS serving the terminal from the one or more T-EAS according to the migration completion time of each T-EAS for the application context of the terminal.

It is worth noting that, with continued reference to fig. 21, in the case where the first network element is an S-EES, the second network element may be an S-EAS. Alternatively, in case the first network element is a T-EES, the second network element may be an S-EAS, or an S-EES.

The embodiment shown in fig. 21 is implemented by the T-EES determining the migration completion time of each T-EAS application context for the terminal in the S-EAS/S-EES initiated T-EAS discovery procedure. Then, the T-EES may select one T-EAS according to the migration completion time of each T-EAS application context for the terminal, or transmit the migration completion time of each T-EAS application context for the terminal to the S-EES/S-EAS. In the latter case, the T-EAS is selected by the S-EES/S-EAS according to the migration completion time of the application context for the terminal for each T-EAS, thereby achieving the technical effect of selecting the T-EAS according to the migration completion time of the application context.

Step 2201 to step 2203, and step 2101 to step 2103, which are not described herein again.

Step 2204, S-EES sends an EAS discovery request 14 to T-EES. Accordingly, the T-EES receives an EAS discovery request 14 from the S-EES. The EAS discovery request 14 is for requesting provision of first relevant information for each of the T-EAS that may serve the terminal. It is worth noting that since the S-EES does not know which T-EAS the terminal can be served by specifically, the EAS discovery request 14 is also used to request the T-EAS the T-EES can serve the terminal. Optionally, the EAS discovery request 14 may also carry some requirement information, so that the T-EES screens the T-EAS that satisfies the requirement information and can provide service to the terminal.

Optionally, the EAS discovery request 14 carries indication information 14. The indication information 14 is used to request first related information of each of the T-EAS that can provide a service to the terminal.

The request message 14/indication information 14 may also not indicate the specific content of the request, only indicating that the first relevant information is requested.

Step 2205, the T-EES discovers one or more T-EAS that can serve the terminal.

For specific implementation, reference may be made to the description at step 2005 above, which is not described herein again.

In step 2206, the T-EES obtains first correlation information for each of one or more T-EAS that may serve the terminal.

For the specific implementation of step 2206, reference may be made to the description in fig. 11, and specifically, the EES in fig. 11 may be replaced by the T-EES.

Step 2207, T-EES sends an EAS discovery response 14 to S-EES. Accordingly, the S-EES receives an EAS discovery response 14 from the T-EES.

The EAS discovery response 14 includes, among other things, first relevant information for each of one or more T-EAS devices that may serve the terminal.

It is worth noting that the T-EES may provide load information or network conditions for each T-EAS to the S-EES. For example, if only a portion of the first relevant information is requested in the request message, the T-EES may return only the requested portion to the S-EES ". For example, in the case where the EAS discovery response 14 does not request location information, the T-EES may provide the S-EES with load information or network conditions for each T-EAS. For example, where the EAS discovery response 14 requests location information, network conditions, load information, the T-EES may provide the location information, network conditions, load information for each T-EAS to the S-EES.

Steps 2208a, S-EES determine migration completion time of each respective application context for the terminal according to one or more of the first correlation information of each T-EAS, the second correlation information of the S-EAS, and the size of the application context.

Optionally, after step 2208a, as shown in fig. 22, the method provided in the embodiment of the present application may perform any one of case E and case F. Therein, case E includes step 2209a and step 2210a. Case F includes step 2209b and step 2210b.

Steps 2209a, S-EES select T-EAS1 based on the migration completion time of each T-EAS application context for the terminal.

For a specific implementation, reference may be made to the process of selecting T-EAS1 by EES in step 805a, which is not described herein again.

Steps 2210a, S-EES transmit an EAS discovery response 15 to S-EAS. Accordingly, the S-EAS receives the EAS discovery response 15 from the S-EES. The EAS discovery response 15 includes, among other things, information for T-EAS1. For example, the information of T-EAS1 is used to identify T-EAS1. For example, the information of T-EAS1 may be address information, identification, etc. of T-EAS1.

Optionally, in case that the information of T-EAS1 is included in the EAS discovery response 15, the S-EES may also transmit information indicating a migration completion time of the application context of the terminal for T-EAS1 to the S-EAS. For example, the information indicating the migration completion time of the application context of the terminal by the T-EAS1 may be the migration completion time of the application context of the terminal by the T-EAS1, or one or more of first related information of the T-EAS1, second related information of the S-EAS, and a size of the application context, which is not limited in this embodiment of the present application.

As an example, information indicating the migration completion time of the application context for the terminal by T-EAS1 is carried in the EAS discovery response 15 to save signaling overhead between network elements.

Optionally, after step 2208a, as shown in fig. 22, the method provided in this embodiment of the present application may further include: step 2209b and step 2210b.

Step 2209b, S-EES sends an EAS discovery response 16 to S-EAS. Accordingly, the S-EAS receives an EAS discovery response 16 from the S-EES.

Wherein the EAS discovery response 16 includes a migration completion time for each of the one or more T-EAS for the application context of the terminal.

In one possible implementation, the EAS profile for each T-EAS may also be included in the EAS discovery response 16.

It should be noted that the migration completion time of the application context for the terminal by a T-EAS may or may not be included in the EAS profile of the T-EAS. For example, the migration completion time of the application context of the terminal by the T-EASn may be contained in the EAS profile of the T-EASn.

Step 2210b, S-EAS, selects T-EAS2 from the one or more T-EAS according to the migration completion time of each T-EAS for the application context of the terminal.

It is to be noted that, the specific implementation of step 2210b may refer to the specific implementation of step 805a described above, and is not described herein again. T-EAS2 and T-EAS1 may be the same T-EAS or different T-EAS.

It is to be noted that, after step 2208, step 2209b and step 2210b may be omitted if step 2209a and step 2210a are executed by the S-EES, or step 2209a and step 2210a may be omitted if step 2209b and step 2210b are executed by the S-EES, which is not limited in the embodiment of the present application.

Alternatively, after step 2207, the method provided in this embodiment of the present application may further include: step 2208b and step 2209c.

Wherein step 2208b, the S-EES provides the S-EAS with first correlation information of each of one or more T-EAS that can serve the terminal.

Step 2209c, the S-EAS determines the T-EAS1 for providing service for the terminal according to one or more of the first relevant information of each T-EAS, the second relevant information of the S-EAS and the size of the application context.

For a specific implementation of step 2209c, reference may be made to one or more of the above-mentioned T-ESS/S-EES for determining the T-EAS1 for providing the service to the terminal according to the first relevant information of each T-EAS, the second relevant information of S-EAS, and the size of the application context, which will not be described herein again.

The above description mainly introduces the scheme of the embodiment of the present application from the perspective of the network element. It is to be understood that each network element, for example, the first network element, the second network element, etc., includes corresponding structures and/or software modules for performing each function in order to implement the above-described functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the first network element and the second network element may be divided according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

The method of the embodiment of the present application is described above with reference to fig. 6.1 to fig. 22, and a communication device performing the method provided by the embodiment of the present application is described below. Those skilled in the art will understand that the method and the apparatus can be combined and referred to each other, and the communication apparatus provided in the embodiments of the present application can perform the steps performed by the first network element or the second network element in the above communication method.

In the case of employing an integrated unit, fig. 23 shows a communication apparatus as referred to in the above-described embodiment, which may include: a communication module 2313, and a processing module 2312.

In an alternative implementation, the communications apparatus can also include a storage module 2311 for storing program codes and data for the communications apparatus.

An example is that the communication device is a first network element, or a chip applied in the first network element. In this case, the communication module 2313 is used to support the communication device in communicating with an external network element (e.g., a second network element). For example, the communication module 2313 is configured to perform the transceiving operation of the first network element in the foregoing method embodiment. Processing module 2312 is configured to perform the processing operations of the first network element in the above-described method embodiments.

For example, in a possible embodiment of the present application, the communication module 2313 is configured to perform the sending action performed by the first network element in step 602 of fig. 6.1 of the foregoing embodiment. A processing module 2312 is used to enable the communication device to perform the processing actions performed by the first network element in the above embodiments, such as step 601. And other steps performed by the first network element.

For example, in a possible embodiment of the present application, the communication module 2313 is configured to perform the receiving action performed by the first network element in step 601-1 of fig. 6.2 of the foregoing embodiment. A processing module 2312 is configured to enable the communication device to perform the processing actions performed by the first network element in the above embodiments, such as step 602-1 and step 603-1. And other steps performed by the first network element.

For example, in another possible embodiment of the present application, the communication module 2313 is configured to perform the sending action performed by the first network element in step 702 of fig. 7 of the foregoing embodiment. A processing module 2312 is configured to enable the communication apparatus to perform the processing actions performed by the first network element in the foregoing embodiments, such as step 701 and step 702. And other steps performed by the first network element.

In one example, the communication device is a second network element or a chip applied in the second network element. In this case, the communication module 2313 is used to support the communication device in communicating with an external network element (e.g., a first network element). For example, the communication module 2313 is configured to perform the transceiving operation of the second network element in the above method embodiment. Processing module 2312 is configured to perform the processing operations of the second network element in the above-described method embodiments. And other steps performed by the second network element.

For example, in a possible embodiment of the present application, the communication module 2313 is configured to perform the receiving action performed by the second network element in step 602 of fig. 6.1 of the foregoing embodiment. A processing module 2312 is configured to enable the communication device to perform the processing actions performed by the second network element in the above embodiments, such as step 603.

For example, in another possible embodiment of the present application, the communication module 2313 is configured to perform the sending action performed by the second network element in step 601-1 of fig. 6.2 of the foregoing embodiment. A processing module 2312 configured to enable the communications apparatus to perform the processing actions performed by the second network element in the above embodiments, such as step 604-1.

For example, in another possible embodiment of the present application, the communication module 2313 is configured to perform the receiving action performed by the second network element in step 702 of fig. 7 of the foregoing embodiment. A processing module 2312 is configured to enable the communication apparatus to perform the processing actions performed by the second network element in the foregoing embodiments, such as step 703.

It should be noted that the communication module 2313 shown in fig. 23 may be replaced by a communication unit, and the processing module 2312 may also be replaced by a processing unit. The memory module 2311 may also be replaced with a memory unit. The processing unit is used for controlling and managing the operation of the communication device, and for example, the processing unit is used for executing the steps of information/data processing in the communication device. The communication unit is used for supporting the steps of information/data transmission or reception of the communication device.

In one possible implementation, the communication unit may include a receiving unit for receiving a signal and a transmitting unit for transmitting a signal.

The processing module 2312 may be a processor or controller such as a central processing unit, general purpose processor, digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module may be a memory.

When the processing module 2312 is the processor 33 or the processor 35, the communication module 2313 is the transceiver 33, and the storage module 2311 is the memory 32, the communication device according to the present application may be the communication device shown in fig. 3.

The above communication module may be a communication interface of the apparatus for receiving signals from other apparatuses. For example, when the device is implemented in the form of a chip, the communication module is a communication interface for the chip to receive signals from other chips or devices or to transmit signals.

Fig. 24 is a schematic structural diagram of a chip 240 according to an embodiment of the present application. Chip 240 includes one or more (including two) processors 2410 and a communication interface 2430.

Optionally, the chip 240 further includes a memory 2440, and the memory 2440 may include a read-only memory and a random access memory, and provides operating instructions and data to the processor 2410. A portion of the memory 2440 may also include non-volatile random access memory (NVRAM).

In some embodiments, memory 2440 stores elements, execution modules or data structures, or a subset thereof, or an expanded set thereof.

In the embodiment of the present application, by calling an operation instruction stored in the memory 2440 (the operation instruction may be stored in an operating system), a corresponding operation is performed.

The processor 2410 controls processing operations of the first network element, the second network element, the third network element, and the first application server, and the processor 2410 may also be referred to as a Central Processing Unit (CPU).

Memory 2440 can include both read-only memory and random-access memory, and provides instructions and data to processor 2410. A portion of the memory 2440 may also include NVRAM. For example, in-application memory 2440, communication interface 2430, and memory 2440 are coupled by bus system 2420, wherein bus system 2420 can include a power bus, a control bus, and a status signal bus, among others, in addition to a data bus. But for purposes of clarity, the various busses are labeled in figure 24 as the bus system 2420.

The method disclosed in the embodiments of the present application may be implemented in the processor 2410 or implemented by the processor 2410. The processor 2410 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 2410. The processor 2410 may be a general purpose processor, a Digital Signal Processor (DSP), an ASIC, an FPGA (field-programmable gate array) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 2440, and the processor 2410 reads the information in the memory 2440 and performs the steps of the method in conjunction with its hardware.

In a possible implementation, the communication interface 2430 is configured to perform the steps of receiving and transmitting of the first network element in the embodiments shown in fig. 6.1, fig. 6.2 or fig. 7. The processor 2410 is configured to perform the steps of the processing of the first network element in the embodiments illustrated in fig. 6.1, 6.2, or 7.

In a possible implementation, the communication interface 2430 is configured to perform the steps of receiving and transmitting of the second network element in the embodiments shown in fig. 6.1, fig. 6.2 or fig. 7. The processor 2410 is configured to perform the steps of the processing for the second network element in the embodiments illustrated in fig. 6.1, 6.2, or 7.

In one aspect, a computer-readable storage medium is provided, in which instructions are stored, which when executed, implement the steps performed by the first network element as in fig. 6.1, 6.2 or 7.

In one aspect, a computer-readable storage medium is provided, in which instructions are stored, which when executed, implement the steps performed by the second network element as in fig. 6.1, 6.2 or 7.

In one aspect, a computer program product comprising instructions is provided, the computer program product comprising instructions that, when executed, implement the steps performed by the first network element as in fig. 6.1, 6.2 or 7.

In one aspect, a computer program product comprising instructions is provided, which when executed, implements the steps performed by the second network element as in fig. 6.1, 6.2 or 7.

In one aspect, a chip is provided, which is applied in a first terminal, and includes at least one processor and a communication interface, where the communication interface is coupled to the at least one processor, and the processor is configured to execute instructions to implement the steps performed by a first network element as in fig. 6.1, fig. 6.2, or fig. 7.

In one aspect, a chip is provided, the chip is applied in a first terminal, and the chip includes at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the processor is configured to execute instructions to implement the steps performed by the second network element in fig. 6.1, fig. 6.2, or fig. 7.

An embodiment of the present application provides a communication system, including: a first network element and a second network element. Wherein the first terminal is configured to perform the steps as performed by the first network element in fig. 6.1. The second network element is configured to perform the steps performed by the second network element in fig. 6.1.

An embodiment of the present application provides a communication system, including: a first network element and a second network element. Wherein the first terminal is configured to perform the steps as performed by the first network element in fig. 6.2. The second network element is configured to perform the steps performed by the second network element in fig. 6.2.

An embodiment of the present application provides a communication system, including: a first network element and a second network element. Wherein the first terminal is configured to perform the steps as performed by the first network element in fig. 7. The second network element is configured to perform the steps performed by the second network element in fig. 7.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, special purpose computer, computer network, network appliance, user equipment, or other programmable device. The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or optical media such as Digital Video Disks (DVDs); but also semiconductor media such as Solid State Drives (SSDs). While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art 25 in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include such modifications and variations.

Claims

1. A method of communication, comprising:

a first network element acquires migration completion time of an application context of a terminal in one or more associated first application servers; the first application server is used for providing service for the terminal, the application context is information aiming at the first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present;

and the first network element determines at least one target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

2. The method of claim 1, further comprising:

The first network element receives first information from a second network element, wherein the first information is migration completion time of an expected application context;

the determining, by the first network element, at least one target application server from one or more first application servers according to the migration completion time of the application context of the terminal by each of the first application servers includes:

and the first network element determines at least one target application server according to the first information and the migration completion time of the application context of each first application server for the terminal.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and the first network element sends the information of at least one target application server to a second network element.

4. The method according to claim 2 or 3, wherein the migration completion time of the application context of the at least one target application server for the terminal is less than or equal to the migration completion time of the expected application context.

5. A method of communication, comprising:

a first network element acquires migration completion time of an application context of a terminal in one or more first application servers associated with the first network element; the application context is information of a first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present;

And the first network element sends second information to a second network element, wherein the second information comprises migration completion time of each first application server for the application context of the terminal, and the second information is used for determining a target application server which provides a service for the terminal in one or more first application servers.

6. The method according to any one of claims 1 to 5, wherein the obtaining, by the first network element, the migration completion time of the application context of each first application server for the terminal includes:

the first network element acquires migration completion time of each application context of the terminal from each first application server.

7. The method according to claim 6, wherein the first network element obtains the migration completion time of the application context of each first application server for the terminal from each first application server, and the method further comprises:

the first network element sends a first request message to each first application server, wherein the first request message is used for requesting the migration completion time of the first application server for the application context of the terminal;

Wherein the first request message includes one or more of second relevant information of the second application server and a size of the application context, and the second relevant information includes one or more of location information, load information, or network conditions of the second application server.

8. The method according to any one of claims 1 to 5, wherein the obtaining, by the first network element, the migration completion time of the application context of each first application server for the terminal includes:

the first network element receives migration completion time of each first application server from a third network element for the application context of the terminal, wherein the third network element is a data analysis network element or an edge configuration server.

9. The method of claim 8, further comprising:

the first network element sends a second request message to the third network element, where the second request message is used to request a migration completion time of each first application server for an application context of the terminal, and the second request message includes: one or more of first relevant information for each of the first application servers, second relevant information for the second application server, a size of the application context, the first relevant information including one or more of location information, load information, or network conditions for the first application server; the second relevant information includes one or more of location information, load information, or network conditions of the second application server.

10. The method according to claim 7 or 9, characterized in that the method further comprises:

the first network element acquires one or more of second relevant information of the second application server and the size of the application context.

11. The method according to any one of claims 1 to 5, wherein the obtaining, by the first network element, the migration completion time of the application context of each first application server for the terminal includes:

the first network element acquires one or more of first relevant information of each first application server, second relevant information of each second application server and the size of the application context;

the first network element determines migration completion time of each first application server aiming at the application context of the terminal according to one or more of the first relevant information, the second relevant information and the size of the application context of each first application server.

12. The method according to claim 10 or 11, wherein the obtaining, by the first network element, one or more of second relevant information of the second application server and a size of the application context comprises:

The first network element receives one or more of second relevant information of the second application server and/or size of the application context from the second application server and/or a first enabling server, wherein the first enabling server is associated with the second application server.

13. The method of claim 12, further comprising:

the first network element sends a third request message to the second application server and/or the first enabling server, where the third request message is used to request one or more of second relevant information of the second application server and the size of the application context.

14. The method according to any of claims 11 to 13, wherein the obtaining, by the first network element, the first relevant information of each of the first application servers comprises:

the first network element sends a fourth request message to each first application server, wherein the fourth request message is used for requesting first related information of the first application server;

the first network element receives the respective first relevant information of each first application server.

15. The method of any one of claims 1 to 14, further comprising:

The first network element receives address information of a first enabling server from the second network element, wherein the first enabling server is associated with the second application server.

16. A method of communication, comprising:

a first network element acquires second information, wherein the second information comprises one or more of first related information of each first application server in one or more first application servers associated with the first network element, second related information of a second application server and the size of an application context;

the application context is information of a first application of the terminal on the second application server, and the second application server is an application server which provides service for the terminal at present;

the second relevant information comprises one or more of location information, load information, or network conditions of the second application server;

the first relevant information comprises one or more of location information, load information, or network conditions of the first application server;

and the first network element sends the second information to a second network element, wherein the second information is used for determining a target application server which provides service for the terminal in one or more first application servers.

17. The method of claim 16, wherein the obtaining, by the first network element, one or more of second relevant information of the second application server and a size of the application context comprises:

the first network element receives one or more of second relevant information of the second application server, the size of the application context from the second application server or a first enabling server associated with the second application server.

18. The method of claim 17, further comprising:

the first network element sends a third request message to the second application server or the first enabling server, wherein the third request message is used for requesting one or more of second relevant information of the second application server and the size of the application context.

19. The method according to any one of claims 16 to 18, wherein the obtaining, by the first network element, the first relevant information of each of the first application servers comprises:

the first network element sends a fourth request message to each first application server, wherein the fourth request message is used for requesting first relevant information of the first application server;

20. The method of any one of claims 16 to 19, further comprising:

21. The method according to any of claims 16 to 20, wherein before the first network element obtains the first related information of each of the first application servers, the method further comprises:

the first network element receives a fifth request message from a first enabling server, wherein the fifth request message is used for requesting first relevant information of the second application server associated with the first network element.

22. The method of claim 21, wherein the fifth request message comprises first indication information, and wherein the first indication information is used to indicate that the first network element provides first relevant information of the second application server associated with the first network element.

23. A method of communication, comprising:

The method comprises the steps that a second network element receives migration completion time of each first application server aiming at an application context of a terminal in one or more first application servers from the first network element, wherein the application context is information of a first application aiming at the terminal on the second application server, and the second application server is an application server which provides service for the terminal at present;

and the second network element determines a target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal, wherein the target application server is used for providing services for the terminal.

24. A method of communication, comprising:

the second network element receives second information from the first network element, wherein the second information comprises one or more of first related information of each of one or more first application servers, second related information of a second application server, and size of an application context;

the application context is information of a first application of the terminal on the second application server, and the second application server is an application server which provides service for the terminal at present; the second relevant information comprises one or more of location information, load information, or network conditions of the second application server;

and the second network element determines a target application server for providing services for the terminal from one or more first application servers according to the second information.

25. The method of claim 24, further comprising:

and the second network element sends address information of a first enabling server to the first network element, wherein the first enabling server is associated with the second application server.

26. The method according to claim 24 or 25, wherein the second network element determines a target application server from one or more of the first application servers according to the second information, comprising:

the second network element determines the migration completion time of each first application server for the application context of the terminal according to the second information;

and the second network element determines the target application server from one or more first application servers according to the migration completion time of each first application server for the application context of the terminal.

27. A method of communication, comprising:

the second network element sends first information to the first network element, wherein the first information is migration completion time of an expected application context; the application context is information of a first application of a terminal on a second application server, and the second application server is an application server which provides service for the terminal at present;

and the second network element receives information of at least one target application server from the first network element, wherein the target application server can be used for providing services for the terminal.

28. The method of claim 27, wherein the migration completion time of the application context of the target application server for the terminal is less than or equal to the expected migration completion time of the application context.

29. The method of any one of claims 23 to 28, further comprising:

30. A method of communication, comprising:

the method comprises the steps that a first application server determines the migration completion time of an application context of a terminal aiming at the first application server, wherein the application context is information aiming at a first application of the terminal on a second application server, and the second application server is an application server which provides service for the terminal at present;

And the first application server sends the migration completion time of the application context of the first application server aiming at the terminal to a first network element.

31. The method of claim 30, further comprising:

the first application server receives a first request message from the first network element, where the first request message is used to request a migration completion time of the first application server for an application context of the terminal.

32. The method of claim 31, wherein the first request message includes one or more of second related information of the second application server, a size of the application context, and wherein the second related information includes one or more of location information, load information, or network conditions of the second application server.

33. A computer readable storage medium having stored therein instructions which, when executed, implement the method of any of claims 1 to 19, or the method of any of claims 20 to 24, or the method of any of claims 25 to 16.

34. A chip comprising a processor coupled to a communication interface, the processor being configured to execute a computer program or instructions to implement a method according to any one of claims 1 to 22, or a method according to any one of claims 23 to 29, or a method according to any one of claims 30 to 32, the communication interface being configured to communicate with a module other than the chip.

35. A communications apparatus, comprising: at least one processor coupled with a memory, the at least one processor to execute instructions stored in the memory to perform the method of any one of claims 1 to 22, or the method of any one of claims 23 to 29, or the method of any one of claims 30 to 32.

36. A communication system, comprising: a first network element for performing the method of any of claims 1 to 22 and a second network element for performing the method of any of claims 23 to 29.