Method for determining edge application server (EAS), and communication apparatus

Abstract

The present application relates to the technical field of communications, and provides a method for determining an edge application server (EAS), and a communication apparatus. The method comprises: sending a first request message to a first ECS, wherein the first request message is used for requesting to acquire EES information, the first request message comprises a group identifier and service provider information, the service provider information is used for indicating PLMN information and / or ECSP information corresponding to a plurality of terminals in a terminal group; receiving a first response message from the first ECS, wherein the first response message comprises the group identifier, and information of a first EES; sending a second request message to the first EES, wherein the second request message is used for requesting to acquire EAS information, and the second request message comprises the group identifier and the service provider information; and receiving a second response message from the first EES, wherein the second response message comprises the group identifier, and information of a first EAS, and the first EAS is the EAS corresponding to the terminal group. The method can ensure fairness in acquiring services by terminal devices in a terminal group.

Description

Method and communication device for determining edge application server EAS

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on April 2, 2024, with application number 202410397971.8 and application name “Method and Communication Device for Determining Edge Application Server EAS”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a method for determining an edge application server (EAS), a communication device, and a computer-readable storage medium. Background Art

[0003] Edge computing (EC), also known as mobile edge computing (MEC), refers to the use of an open platform integrating network, computing, storage, and application core capabilities at the edge of the network close to data sources and terminal devices to provide the closest services.

[0004] In the 3rd Generation Partnership Project (3GPP) edge system, one or more Edge Application Servers (EAS) can be deployed near multiple application consumers. For example, one or more EASs and Edge Enabler Servers (EES) can be deployed in the edge data network (EDN) of the system. The edge configuration server (ECS) and EES assist user equipment (UE) in connecting to the EAS. Under the 3GPP technical standard, multiple UEs in the same group can connect to the same EAS to obtain application services, or they can connect to different EASs to obtain application services; however, in some business scenarios (for example, multiple UEs in the same group team up to play games), considering that the service capabilities of different EASs may not be the same, if multiple UEs in the same group are connected to different EASs, not only will the application context need to be synchronized, but the fairness of service acquisition for each UE in the same group will also be affected. Summary of the Invention

[0005] The present application provides a method, communication device, and computer-readable storage medium for determining an edge application server (EAS), which can ensure fairness in accessing services for multiple terminal devices in a terminal group. The present application provides the following technical solutions:

[0006] In a first aspect, a method for determining an edge application server EAS is provided, which can be executed by a terminal device (e.g., a first terminal), or by a module (e.g., a processor, a chip, or a chip system) applied to the terminal device, or by a logic module or software that can implement all or part of the terminal device functions. The method includes: sending a first request message to a first edge configuration server ECS, the first request message is used to request to obtain edge enabling server EES information, the first request message includes a group identifier and service provider information, the group identifier is an identifier of a terminal group corresponding to multiple terminals, the terminal group includes a first terminal, and the service provider information is used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group; receiving a first response message from the first ECS, the first response message includes the group identifier and information of the first EES; sending a second request message to the first EES, the second request message is used to request to obtain EAS information, the second request message includes the group identifier and service provider information; receiving a second response message from the first EES, the second response message includes the group identifier and information of the first EAS, the first EAS is the EAS corresponding to the terminal group.

[0007] In the above scheme, the first request message sent by the terminal device to the first ECS includes a group identifier and service provider information, wherein the group identifier and service provider information can enable the first ECS to select an EES (for example, the first EES) that can be used (or connected) together for multiple terminal devices (for example, UE-A) in the terminal group, and enable the EES to select an EAS (for example, the first EAS) that can be accessed (or connected) together for multiple terminal devices in the terminal group. Multiple terminals in the terminal group are connected to the same EAS, which not only avoids the synchronization of application contexts between different EASs, but also ensures fairness in the service acquisition of each terminal device in the terminal group.

[0008] In a possible implementation, the first EES is an EES corresponding to multiple terminals in the terminal group.

[0009] When the first EES allows terminals of different service providers in the terminal group to use (or connect to) it, it means that the first EES can be used as a shared EES; multiple terminals in the terminal group can be connected to the same EAS (for example, the first EAS) through the first EES, thereby ensuring fairness in the access to services by each terminal device in the terminal group.

[0010] In a possible implementation manner, the PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

[0011] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0012] In the second aspect, a method for determining an edge application server EAS is provided, which can be executed by a terminal device (for example, a second terminal), or by a module applied to the terminal device (for example, a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the terminal device functions. The method includes: sending a third request message to the second edge configuration server ECS, the third request message is used to request to obtain edge enabling server EES information, the third request message includes a group identifier and service provider information, the group identifier is an identifier of a terminal group corresponding to multiple terminals, the terminal group includes the second terminal, and the service provider information is used to indicate the PLMN information and / or ECSP information corresponding to the multiple terminals in the terminal group; receiving a third response message from the second ECS, the third response message includes the group identifier, information of the first EES, and information of the second EES, the first EES is the EES corresponding to the terminal group, and the second EES is the EES corresponding to the second terminal.

[0013] In the above scheme, the terminal device sends a third request message including a group identifier and service provider information to the second ECS, and the group identifier and service provider information is conducive to the determination of the first EES and the second EES; the terminal device determines the shared EES (for example, the first EES) corresponding to the terminal group by receiving the third response message, so that multiple terminals in the terminal group can be connected to the same EAS through the shared EES, which not only avoids the synchronization of application contexts between different EASs, but also ensures the fairness of service acquisition for each terminal device in the terminal group.

[0014] In one possible implementation, the method further includes: sending a fifth request message to the second EES, the fifth request message being used to request EAS information, the fifth request message including the group identifier, service provider information, and information of the first EES; and receiving a fifth response message from the second EES, the fifth response message including the group identifier and information of the first EAS, the first EAS being the EAS corresponding to the terminal group.

[0015] In the above scheme, the terminal device sends a fifth request message including information of the first EES to the second EES, so that the second EES can obtain the EAS (for example, the first EAS) corresponding to the terminal device (for example, the first terminal) through the first EES, thereby realizing that other terminals in the terminal group (for example, the second terminal other than the first terminal) and the first terminal are connected to the same EAS (for example, the first EAS). This not only avoids the synchronization of application contexts between different EASs, but also ensures the fairness of service acquisition for each terminal device in the terminal group.

[0016] In a possible implementation, the service provider information includes: PLMN information including a PLMN identifier, and / or ECSP information including an ECSP identifier.

[0017] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0018] In a third aspect, a method for determining an edge application server EAS is provided, which can be executed by a network device (e.g., a first edge configuration server ECS), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a first request message from a first terminal, the first request message being used to request information about an edge enabling server EES, the first request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including a first terminal, the service provider information being used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group; determining a first EES based on the service provider information, the first EES being the EES corresponding to the terminal group; and sending a first response message to the first terminal, the first response message including information about the group identifier and the first EES.

[0019] A network device (e.g., a first ECS) receives a first request message including a group identifier and service provider information from a first terminal; the first ECS determines a first EES that can be commonly used (or connected) for multiple terminal devices (e.g., UE-A) in the terminal group based on the service provider information, so as to select an EAS (e.g., the first EAS) that can be commonly accessed for multiple terminal devices in the terminal group through the first EES, thereby ensuring fairness in service acquisition for each terminal device in the terminal group.

[0020] In a possible implementation, the method further includes: receiving a fourth request message from the second ECS, the fourth request message being used to request acquisition of EES information, the fourth request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to the multiple terminals, the terminal group including the second terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the multiple terminals in the terminal group; determining the first EES based on the service provider information; and sending a fourth response message to the second ECS, the fourth response message including the group identifier and information of the first EES.

[0021] The network device (e.g., the first ECS) determines the first EES based on the service provider information in the fourth request message, and feeds back the first EES to the second ECS through the fourth response message, so that the terminal served by the network device (e.g., the first terminal served by the first ECS) can be connected to the same EAS as the terminal served by the second ECS in the same group (e.g., the second terminal served by the second ECS), thereby avoiding unfair services for users in the same group due to connecting to different EASs.

[0022] In a possible implementation manner, the PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

[0023] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0024] In a fourth aspect, a method for determining an edge application server EAS is provided. The method can be executed by a network device (e.g., a first edge enabling server EES), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a second request message from a first terminal, the second request message being used to request EAS information, the second request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including the first terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group; determining a first EAS based on the service provider information; and sending a second response message to the first terminal, the second response message including the group identifier and information about the first EAS.

[0025] The network device (e.g., the first EES) receives a second request message including a group identifier and service provider information, and selects a shared EAS (e.g., the first EAS) from multiple EASs deployed on the EES based on the service provider information, which allows multiple terminal devices in the terminal group to access the shared EAS. This not only avoids synchronization of application contexts between different EASs, but also ensures fairness in service acquisition for each terminal device in the terminal group.

[0026] In a possible implementation, the method further includes: receiving a sixth request message from the second EES, the sixth request message being used to request EAS information, the sixth request message including a group identifier and service provider information; determining, based on the service provider information, that the first EAS is the EAS corresponding to multiple terminals in the terminal group; and sending a sixth response message to the second EES, the sixth response message including the group identifier and information of the first EAS.

[0027] The network device (e.g., the first EES) receives the sixth request message including the group identifier and the service provider information, and determines the shared EAS (e.g., the first EAS) to which multiple terminal devices in the terminal group access based on the service provider information; and then sends the shared EAS to the second EES to ensure that the second terminal in the terminal group is connected to the same EAS as the first terminal, thereby achieving fairness in obtaining services.

[0028] In a possible implementation manner, the PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

[0029] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0030] In a fifth aspect, a method for determining an edge application server EAS is provided. The method can be executed by a network device (e.g., a second edge configuration server ECS), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a third request message from a second terminal, the third request message being used to request information about an edge enabling server EES, the third request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including a second terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group; and sending a third response message to the second terminal, the third response message including the group identifier and information about a first EES, the first EES being the EES corresponding to the terminal group.

[0031] The network device (e.g., the second ECS) receives a third request message including a group identifier and service provider information from the second terminal, and sends information of the first EES to the second terminal, so that the second terminal obtains a shared EAS (e.g., the first EAS) through the first EES and connects to the same EAS as the first terminal, thereby achieving fairness in obtaining services for each terminal device in the terminal group.

[0032] In one possible implementation, before sending the third response message to the second terminal, the method also includes: sending a fourth request message to the first ECS based on the service provider information, the fourth request message is used to request to obtain EES information, and the fourth request message includes a group identifier and service provider information; receiving a fourth response message from the first ECS, the fourth response message includes the group identifier and information of the first EES.

[0033] The network device (for example, the second ECS) sends a fourth request message to the first ECS based on the service provider information to obtain the information of the first EES through the first ECS, so that the second terminal obtains the first EAS corresponding to the terminal group through the first EES, thereby connecting the second terminal and the first terminal to the same first EAS to ensure fairness in obtaining services for each terminal device.

[0034] In a possible implementation, the third response message further includes information about the second EES, where the second EES is the EES corresponding to the second terminal.

[0035] In a possible implementation manner, the PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

[0036] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0037] In a sixth aspect, a method for determining an edge application server EAS is provided. The method can be executed by a network device (e.g., a second edge enabling server EES), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a fifth request message from a second terminal, the fifth request message being used to request EAS information, the fifth request message including a group identifier, service provider information, and information about a first EES, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including a second terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group; and sending a fifth response message to the second terminal, the fifth response message including a group identifier and information about the first EAS.

[0038] The network device (e.g., the second EES) receives the fifth request message to obtain information of the first EES, so as to obtain the first EAS corresponding to the terminal group based on the information of the first EES; the network device feeds back the information of the first EAS to the second terminal through the fifth response message, so that the second terminal and the first terminal in the same group are connected to the same EAS (e.g., the first EAS) to ensure fair service.

[0039] In one possible implementation, before sending the fifth response message to the second terminal, the method also includes: determining to send a sixth request message to the first EES based on the information of the first EES, the sixth request message is used to request to obtain EAS information, and the sixth request message includes a group identifier and service provider information; receiving a sixth response message from the first EES, the sixth response message includes a group identifier and information of the first EAS, and the first EAS is the EAS corresponding to the terminal group.

[0040] The network device (e.g., the second EES) receives the fifth request message and obtains the first EAS corresponding to the terminal group through the first EES, so as to feedback the information of the first EAS to the second terminal, so that the second terminal and the first terminal in the same group are connected to the same EAS (e.g., the first EAS) to ensure fairness in obtaining services.

[0041] In a possible implementation manner, the PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

[0042] Typically, different terminals may be in network services provided by different service providers. The PLMN identifier and / or ECSP identifier can accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for the terminals.

[0043] In a seventh aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a terminal device (e.g., a third terminal), or by a module (e.g., a processor, chip, or chip system) applied to the terminal device, or by a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: obtaining a second EAS, where the second EAS is the EAS corresponding to the terminal group, and the third terminal is one of the multiple terminals corresponding to the terminal group; and sending a seventh request message to the third EAS, where the seventh request message includes a group identifier, an identifier of the second EAS, and second service provider information, where the group identifier is the identifier of the terminal group, and the second service provider information is PLMN information or ECSP information supported by the second EAS.

[0044] The terminal device (for example, the third terminal) obtains the second EAS corresponding to the terminal group and sends the information of the second EAS to the third EES through the seventh request, so that other terminals in the terminal group can obtain the information of the second EAS, thereby achieving the purpose of sharing the second EAS with each terminal in the terminal group.

[0045] In an eighth aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a network device (e.g., a third EES), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a seventh request message from a third terminal, the seventh request message including a group identifier, an identifier of a second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, and the second EAS being the EAS corresponding to the terminal group; and sending an eighth request message to the first ECS-ER, the eighth request message including a group identifier, an identifier of the second EAS, and second service provider information.

[0046] The network device (for example, the third EES) obtains the seventh request message including the second EAS identifier, and sends the second EAS identifier to the first ECS-ER through the eighth request message, so that the first ECS-ER shares the second EAS identifier with the ECS-ERs of other terminals in the terminal group (for example, the second ECS-ER), so that other terminals in the terminal group (for example, the fourth terminal) obtain the second EAS identifier through their corresponding ECS-ER (for example, the second ECS-ER), thereby achieving the purpose of connecting each terminal in the terminal group to the same EAS (for example, the second EAS).

[0047] In the ninth aspect, a method for determining an edge application server EAS is provided. The method can be executed by a network device (for example, a first ECS-ER), or by a module applied to the network device (for example, a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the network device functions. The method includes: receiving an eighth request message from a third EES, the eighth request message including a group identifier, an identifier of a second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, and the second EAS being the EAS corresponding to the terminal group; determining, based on the second service provider information, to send query information to a second ECS-ER; sending a ninth request message to the second ECS-ER, the ninth request message being used to instruct the second ECS-ER to migrate a fourth terminal from the third EAS to the second EAS, the ninth request message including the group identifier, the identifier of the second EAS, and the second service provider information, the third EAS being a non-shared EAS to which the fourth terminal is currently connected, and the terminal group including the fourth terminal; and receiving a ninth response message from the second ECS-ER, the ninth response message including the group identifier and the second service provider information.

[0048] The network device (for example, the first ECS-ER) obtains the eighth request message through the third EES, and determines to send query information to the second ECS-ER based on the second service provider information in the eighth request message; then sends a ninth request message to the second ECS-ER to instruct the fourth terminal served by the second ECS-ER to migrate from the third EAS to the second EAS, so that the fourth terminal and the third terminal are connected to the same second EAS, thereby achieving fairness in obtaining services between different terminals.

[0049] In the tenth aspect, a method for determining an edge application server EAS is provided, which can be executed by a network device (e.g., a second ECS-ER), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device function. The method includes: receiving query information from the first ECS-ER; receiving a ninth request message from the first ECS-ER, the ninth request message being used to instruct to migrate the fourth terminal from the third EAS to the second EAS, the ninth request message including a group identifier, an identifier of the second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to multiple terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, the second EAS being the EAS corresponding to the terminal group, the third EAS being the non-shared EAS to which the fourth terminal is currently connected, and the terminal group including the fourth terminal; and sending a ninth response message to the first ECS-ER, the ninth response message including the group identifier and the second service provider information.

[0050] The network device (e.g., the second ECS-ER) obtains a ninth request message including information related to the second EAS from the first ECS-ER, so as to determine the EAS (e.g., the second EAS) to which the fourth terminal needs to switch based on the content of the ninth request message, so that the fourth terminal and other terminals in the terminal group (e.g., the third terminal) are connected to the same EAS (e.g., the second EAS) to obtain fair service.

[0051] In a possible implementation, the method further includes: receiving an eleventh request message from the fourth EES, the eleventh request message including a group identifier, an identifier of the third EAS, and third service provider information, the third service provider information being PLMN information or ECSP information supported by the third EAS; determining, based on the second service provider information, whether to instruct the fourth terminal to migrate from the third EAS to the second EAS; and when it is determined that the fourth terminal is to be instructed to migrate from the third EAS to the second EAS, sending an eleventh response message to the fourth EES, the eleventh response message being used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

[0052] The network device (e.g., the second ECS-ER) can determine whether to migrate the fourth terminal from the third EAS to the second EAS based on the second service provider information to ensure that the fourth terminal can connect to the same EAS (e.g., the second EAS) as other terminals in the same group (e.g., the third terminal) to obtain fair service.

[0053] In an eleventh aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a terminal device (e.g., a fourth terminal), or by a module (e.g., a processor, chip, or chip system) implemented in the terminal device, or by a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: obtaining a third EAS, where the third EAS is a non-shared EAS to which the fourth terminal is currently connected, and the fourth terminal is one of multiple terminals corresponding to a terminal group; and sending a tenth request message to the fourth EAS, where the tenth request message includes a group identifier, an identifier of the third EAS, and third service provider information, where the group identifier is an identifier of the terminal group, and the third service provider information is information about service providers supported by the third EAS.

[0054] After the fourth terminal is connected to the third EAS, it can send a tenth request message to the fourth EES to obtain the information of the shared EAS corresponding to the terminal group (for example, the information of the second EAS), so that the fourth terminal and other terminals in the same group (for example, the third terminal) are connected to the same EAS (for example, the second EAS) to ensure fairness in obtaining services.

[0055] In a twelfth aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a network device (e.g., a fourth EES), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a tenth request message from a fourth terminal, the tenth request message including a group identifier, an identifier of a third EAS, and third service provider information, the group identifier being an identifier of a terminal group, the third EAS not belonging to the EAS corresponding to the terminal group, and the third service provider information being PLMN information or ECSP information supported by the third EAS; and sending a tenth response message to the fourth terminal, the tenth response message being used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

[0056] The network device (e.g., the fourth EES) receives the tenth request message from the fourth terminal, and feeds back a tenth response message to the fourth terminal based on the content of the tenth request message to instruct the fourth terminal to migrate from the third EAS to the second EAS, so that the fourth terminal and other terminals in the terminal group (e.g., the third terminal) are connected to the same EAS (e.g., the second EAS) to ensure fairness in obtaining services.

[0057] In one possible implementation, before sending the tenth response message to the fourth terminal, the method further includes: sending an eleventh request message to the second ECS-ER, the eleventh request message including the group identifier, the identifier of the third EAS, and the third service provider information; receiving the eleventh response message from the second ECS-ER, the eleventh response message being used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

[0058] In a thirteenth aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a terminal device (e.g., a fifth terminal), or by a module (e.g., a processor, a chip, or a chip system) applied to the terminal device, or by a logic module or software that can implement all or part of the terminal device functions. The method includes: obtaining a fourth EAS, where the fourth EAS is the EAS corresponding to the terminal group, and the fifth terminal is one of the multiple terminals corresponding to the terminal group; sending a twelfth request message to the third ECS, where the twelfth request message includes a group identifier, fourth service provider information, and fifth service provider information, where the group identifier is the identifier of the terminal group, the fourth service provider information is the PLMN information and / or ECSP information corresponding to the terminal group, and the fifth service provider information is information of a fifth EES or information of a fourth EAS, where the fifth EES is the EES corresponding to the terminal group, and the fourth EAS is the EAS corresponding to the terminal group.

[0059] The terminal device (for example, the fifth terminal) obtains the fourth EAS corresponding to the terminal group, and sends the fifth EES or the fourth EAS and other related information to the third ECS through the twelfth request message, so that other terminals in the terminal group can obtain the fifth EES or the fourth EAS and other related information, thereby enabling each terminal in the terminal group to be connected to the same EAS (for example, the fourth EAS) through the fifth EES or the fourth EAS and other related information, so as to ensure fairness in the acquisition of services by each terminal in the terminal group.

[0060] In a fourteenth aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a network device (e.g., a third ECS), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a twelfth request message from a fifth terminal, the twelfth request message including a group identifier, fourth service provider information, and fifth service provider information, the group identifier being an identifier of a terminal group, the fourth service provider information being PLMN information and / or ECSP information corresponding to the terminal group, the fifth service provider information being information of a fifth EES or information of a fourth EAS, the fifth EES being the EES corresponding to the terminal group, and the fourth EAS being the EAS corresponding to the terminal group; and determining, based on the twelfth request message, to send a thirteenth request message to the fourth ECS, the thirteenth request message including the group identifier, the fourth service provider information, and the fifth service provider information.

[0061] The network device (for example, the third ECS) receives the twelfth request message from the fifth terminal, and determines to send the thirteenth request message to the fourth ECS based on the twelfth request message, so that the fourth ECS obtains relevant information such as the fifth EES or the fourth EAS, and then the fourth ECS determines the shared EAS (for example, the fourth EAS) to which the sixth terminal needs to connect based on the relevant information such as the fifth EES or the fourth EAS, so that the sixth terminal and other terminals in the same group (for example, the fifth terminal) are connected to the same fourth EAS to ensure fairness in obtaining services.

[0062] In a fifteenth aspect, a method for determining an edge application server (EAS) is provided. The method can be executed by a network device (e.g., a fourth ECS), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device function. The method includes: receiving a thirteenth request message from a third ECS, the thirteenth request message including a group identifier, fourth service provider information, and fifth service provider information, the group identifier being an identifier of a terminal group, the fourth service provider information being PLMN information and / or ECSP information corresponding to the terminal group, the fifth service provider information being information of a fifth EES or information of a fourth EAS, the fifth EES being the EES corresponding to the terminal group, and the fourth EAS being the EAS corresponding to the terminal group; and storing the group identifier, fourth service provider information, and fifth service provider information in the thirteenth request message.

[0063] The network device (e.g., the fourth ECS) receives the thirteenth request message through the third ECS and stores the group identifier, the fourth service provider information, and the fifth service provider information in the thirteenth request message, so that the sixth terminal and other terminals in the same group (e.g., the fifth terminal) can connect to the same fourth EAS to ensure fairness in obtaining services.

[0064] In a possible implementation, the method further includes: receiving a fourteenth request message from a sixth terminal, the fourteenth request message including a group identifier and sixth service provider information, the group identifier being an identifier of a terminal group, the terminal group including the sixth terminal, and the sixth service provider information being PLMN information and / or ECSP information corresponding to the terminal group; determining the fifth EES based on the fourteenth request message; and sending a fourteenth response message to the sixth terminal, the fourteenth response message including the group identifier and information of the fifth EES.

[0065] In the sixteenth aspect, a method for determining an edge application server EAS is provided, which can be executed by a terminal device (e.g., a sixth terminal), or by a module (e.g., a processor, a chip, or a chip system) applied to the terminal device, or by a logic module or software that can implement all or part of the terminal device functions. The method includes: sending a fourteenth request message to a fourth ECS, the fourteenth request message including a group identifier and sixth service provider information, the group identifier being an identifier of a terminal group, the terminal group including a sixth terminal, and the sixth service provider information being PLMN information and / or ECSP information corresponding to the terminal group; sending a fifteenth request message to a fifth EES, the fifteenth request message being used to request EAS information, the fifteenth request message being used to request EAS information, the fifteenth request message including a group identifier, sixth service provider information, and EAS filtering information, the sixth service provider information including PLMN information and / or ECSP information corresponding to the terminal group, the EAS filtering information including information of the fourth EAS, and the fourth EAS being the EAS corresponding to the terminal group.

[0066] The terminal device (for example, the sixth terminal) sends the fourteenth request message to the fourth ECS and the fifteenth request message to the fifth EES to obtain the information of the fourth EAS corresponding to the terminal group, and connects itself and other terminals in the same group (for example, the fifth terminal) to the same fourth EAS to ensure fairness in obtaining services.

[0067] In the seventeenth aspect, a method for determining an edge application server EAS is provided. The method can be executed by a network device (e.g., a fifth EES), or by a module (e.g., a processor, a chip, or a chip system) applied to the network device, or by a logic module or software that can implement all or part of the network device functions. The method includes: receiving a fifteenth request message from a sixth terminal, the fifteenth request message being used to request EAS information, the fifteenth request message including a group identifier, sixth service provider information, and EAS filtering information, the group identifier being an identifier of a terminal group, the terminal group including the sixth terminal, the sixth service provider information including PLMN information and / or ECSP information corresponding to the terminal group, the EAS filtering information including information of a fourth EAS, the fourth EAS being the EAS corresponding to the terminal group; determining the fourth EAS based on the fifteenth request message; and sending a fifteenth response message to the sixth terminal, the fifteenth response message including the group identifier and information of the fourth EAS.

[0068] The network device (e.g., the fifth EES) receives the fifteenth request message from the sixth terminal, determines the information of the fourth EAS based on the fifteenth request message, and sends the information of the fourth EAS to the sixth terminal through the fifteenth response message, so that the sixth terminal and other terminals in the same group (e.g., the fifth terminal) are connected to the same fourth EAS to ensure fairness in obtaining services.

[0069] In aspect 18, a communication device is provided, which may be a terminal device (e.g., a first terminal or a second terminal, etc.), or a module (e.g., a processor, a chip, or a chip system, etc.) applied to a terminal device, or a logical node, a logical module, or software that can implement all or part of the functions of the terminal device. The communication device includes a processor and, optionally, a memory. The memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions in the memory; when the processor executes the computer program or instructions stored in the memory, the communication device executes the method performed by the terminal device in the above method embodiment.

[0070] In the nineteenth aspect, a communication device is provided. The communication device can be a network device (for example, a first ECS or a first ECS-ER, etc.), or it can be executed by a module (such as a processor, a chip, or a chip system, etc.) applied to the network device, or it can be a logical node, a logical module, or software that can realize all or part of the network device functions. The communication device includes a processor and, optionally, a memory. The memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions in the memory; when the processor executes the computer program or instructions stored in the memory, the communication device executes the method performed by the network device in the above method embodiment.

[0071] In the twentieth aspect, a computer program product is provided, which includes: a computer program code, and when the computer program code is run, the method performed by the terminal device in the above aspects is executed.

[0072] In a twenty-first aspect, a computer program product is provided, the computer program product comprising: a computer program code, which, when run, enables the methods performed by the network device in the above aspects to be executed.

[0073] In a twenty-second aspect, the present application provides a chip system comprising a processor configured to implement the functions of a terminal device in the methods of the aforementioned aspects. In one possible design, the chip system further comprises a memory configured to store program instructions and / or data. The chip system may be composed solely of a chip or may include a chip and other discrete components.

[0074] In a twenty-third aspect, the present application provides a chip system comprising a processor configured to implement the network device functions described in the aforementioned methods. In one possible design, the chip system further comprises a memory configured to store program instructions and / or data. The chip system may be comprised solely of a chip or may include a chip and other discrete components.

[0075] In the twenty-fourth aspect, the present application provides a computer-readable storage medium, which includes a computer program or instructions. When the computer program or instructions are executed, the methods performed by the terminal device in the above aspects are implemented.

[0076] In a twenty-fifth aspect, the present application provides a computer-readable storage medium, which includes a computer program or instructions. When the computer program or instructions are executed, the methods performed by the network device in the above aspects are implemented.

[0077] In aspect 26, an embodiment of the present application provides a communication system, comprising: the communication device of the above-mentioned aspects 1 to 6, or the communication device of the above-mentioned aspects 7 to 12, or the communication device of the above-mentioned aspects 13 to 17.

[0078] In aspect 27, an embodiment of the present application provides another communication system, comprising at least two of the following communication devices: a communication device for executing the above-mentioned first aspect; a communication device for executing the above-mentioned second aspect; a communication device for executing the above-mentioned third aspect; a communication device for executing the above-mentioned fourth aspect; a communication device for executing the above-mentioned fifth aspect; a communication device for executing the above-mentioned sixth aspect; a communication device for executing the above-mentioned seventh aspect; a communication device for executing the above-mentioned eighth aspect; a communication device for executing the above-mentioned ninth aspect; a communication device for executing the above-mentioned tenth aspect; a communication device for executing the above-mentioned eleventh aspect; and a communication device for executing the above-mentioned twelfth aspect.

[0079] In aspect 28, an embodiment of the present application provides another communication system, comprising at least two of the following communication devices: a communication device for executing the above-mentioned first aspect; a communication device for executing the above-mentioned second aspect; a communication device for executing the above-mentioned third aspect; a communication device for executing the above-mentioned fourth aspect; a communication device for executing the above-mentioned fifth aspect; a communication device for executing the above-mentioned sixth aspect; a communication device for executing the above-mentioned seventh aspect; a communication device for executing the above-mentioned eighth aspect; a communication device for executing the above-mentioned ninth aspect; a communication device for executing the above-mentioned tenth aspect; a communication device for executing the above-mentioned eleventh aspect; a communication device for executing the above-mentioned twelfth aspect; a communication device for executing the above-mentioned thirteenth aspect; a communication device for executing the above-mentioned fourteenth aspect; a communication device for executing the above-mentioned fifteenth aspect; a communication device for executing the above-mentioned sixteenth aspect; and a communication device for executing the above-mentioned seventeenth aspect.

[0080] Any of the communication devices, computer storage media, computer program products, chips, or communication systems provided above can be used to execute the methods provided in the first to seventeenth aspects. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding schemes in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] FIG1 is a schematic diagram of a possible, non-limiting communication system provided in an embodiment of the present application;

[0082] FIG2 is a schematic diagram of a network structure of a communication system provided in an embodiment of the present application;

[0083] FIG3 is a schematic diagram of a structure of communication between a network device and a terminal device provided in an embodiment of the present application;

[0084] FIG4 is a schematic diagram of a 3GPP edge system architecture provided in an embodiment of the present application;

[0085] FIG5 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0086] FIG6 is a schematic diagram of another application scenario provided by an embodiment of the present application;

[0087] FIG7A is a schematic diagram of a method 700 for determining an edge application server EAS provided in an embodiment of the present application;

[0088] FIG7B is a schematic diagram of a method 700A for multiple terminals in a terminal group to obtain group identifiers provided by an embodiment of the present application;

[0089] FIG7C is a schematic diagram of a shared EAS registration process according to an embodiment of the present application;

[0090] FIG7D is a schematic diagram of a non-shared EAS registration process according to an embodiment of the present application;

[0091] FIG8 is a schematic diagram of a method 800 for determining an edge application server EAS provided in an embodiment of the present application;

[0092] FIG9 is a schematic diagram of a method 900 for determining an edge application server EAS provided in an embodiment of the present application;

[0093] FIG10 is a schematic diagram of a method 1000 for determining an edge application server EAS provided in an embodiment of the present application;

[0094] FIG11 is a schematic diagram of an application example of determining an edge application server EAS according to an embodiment of the present application;

[0095] FIG12 is a schematic diagram of another application example of determining an edge application server EAS provided in an embodiment of the present application;

[0096] FIG13 is a schematic diagram of an application example of another method for determining an edge application server EAS according to an embodiment of the present application;

[0097] FIG14 is a schematic diagram of another application example of determining an edge application server EAS provided in an embodiment of the present application;

[0098] FIG15 is a schematic structural diagram of a communication device 1500 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0099] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0100] In the description of the present application, "at least one of the following items" or similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, a and b and c, wherein a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the 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 between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit quantity and execution order, and words such as "first" and "second" do not limit necessarily different.

[0101] It should be understood that, in this application, “in case of”, “if”, “when”, “if” and similar expressions can be used interchangeably.

[0102] It should be noted that, in this application, words such as "exemplarily" or "for example" are used to indicate giving an example, illustration, or explanation. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being a preferred implementation over other embodiments or designs. The use of words such as "exemplarily" or "for example" in this application is intended to present the relevant concepts in a concrete manner.

[0103] The technical solutions of the embodiments of the present application can be applied to various communication systems, including long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, fifth generation (5G) mobile communication systems or new radio access technologies (NR). The technical solutions provided in the present application can also be applied to future communication systems, such as sixth generation (6G) mobile communication systems.

[0104] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0105] Figure 1 shows a schematic diagram of a possible, non-limiting communication system 100. As shown in Figure 1 , the communication system includes at least one network device (such as 220 in Figure 1 ) and at least one terminal device (such as 230 and 240 in Figure 1 ). The network device, which may also be referred to as a radio access network (RAN) node or RAN device, facilitates wireless access for the terminal device.

[0106] The network device may be a base station, which may broadly cover the following various names or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), next generation evolved NodeB (ng-eNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNodeB (MeNB), secondary eNodeB (SeNB), multi standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP) in wireless fidelity (WIFI) system, transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), etc. The base station can be a macro base station, a micro base station, a pico base station, a small station, a relay station, a balloon station, a relay node, a donor node, or the like, or a combination thereof.

[0107] A base station may also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. A base station may also be a network device in a 6G network, a device that performs base station functions in a future communication system, etc. A base station may support networks with the same or different access technologies. A base station may be fixed or mobile. For example, a helicopter or a drone may be configured to act as a mobile base station, and one or more cells may move according to the location of the mobile base station. In other examples, a helicopter or a drone may be configured to be used as a device for communicating with another base station. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0108] In a network structure of a communication system, as shown in Figure 2, the network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a radio access device including both a CU node and a DU node. The radio access device including both a CU node and a DU node separates the protocol layers of the gNB in ​​the NR system, centrally controlling some protocol layer functions in the CU and distributing some or all of the remaining protocol layer functions in the DU, which is then centrally controlled by the CU.

[0109] Optionally, as shown in Figure 2, the CU can also be divided into a central unit-control plane (CU-CP) and a central unit-user plane (CU-UP). The CU-CP is responsible for control plane functions, mainly including RRC and the packet data convergence protocol (PDCP) corresponding to the control plane, namely PDCP-C. PDCP-C is mainly responsible for encryption and decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, mainly including the service data adaptation protocol (SDAP) and the PDCP corresponding to the user plane (ie, PDCP-U).

[0110] SDAP is primarily responsible for processing data within the core network and mapping flows to bearers. PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface. It connects to the DU via the F1 control plane, or F1-C. The CU-UP connects to the DU via the F1 user plane, or F1-U. Alternatively, PDCP-C may also reside in the CU-UP.

[0111] In an optional embodiment, the communication system shown in Figure 1 may further include: a core network device (such as 210 in Figure 1). The core network device refers to a device in the core network (CN) that provides service support for the terminal device.

[0112] For example, core network devices may include: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one. Among them, the AMF entity can be responsible for access management and mobility management of terminal devices; the SMF entity can be responsible for session management, such as user session establishment; the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network.

[0113] It should be noted that the entities in this application may also be referred to as network elements or functional entities. For example, the AMF entity may also be referred to as an AMF network element or an AMF functional entity. For example, the SMF entity may also be referred to as an SMF network element or an SMF functional entity, etc.

[0114] A terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as a ship, etc.); it can also be deployed in the air (for example, on an airplane, balloon, and satellite). The embodiments of this application do not limit the scenario in which the terminal device is located.

[0115] The terminal device may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wireless modem, a handheld device (handset), a laptop computer, a machine type communication (MTC) terminal, and may also be a wireless terminal used in scenarios such as virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, transportation safety, smart city, and smart home.

[0116] In this application, the aforementioned terminal devices and chips applicable to the aforementioned terminal devices are collectively referred to as terminal devices. It should be understood that the embodiments of this application do not limit the specific technology and specific device form adopted by the terminal devices.

[0117] As an example, the communication between the network device (e.g., 220) and the terminal device (e.g., 230) in the communication system shown in Figure 1 can be carried out in the form shown in Figure 3; as shown in Figure 3, the terminal device includes a processor 101, a memory 102 and a transceiver 103, and the transceiver 103 includes a transmitter 1031, a receiver 1032 and an antenna 1033.

[0118] The network device includes a processor 201, a memory 202, and a transceiver 203. The transceiver 203 includes a transmitter 2031, a receiver 2032, and an antenna 2033. The receiver 1032 can be configured to receive transmission control information via the antenna 1033, and the transmitter 1031 can be configured to send transmission feedback information to the network device via the antenna 1033. The transmitter 2031 can be configured to send transmission control information to a terminal device via the antenna 2033, and the receiver 2032 can be configured to receive transmission feedback information sent by the terminal device via the antenna 2033.

[0119] Before introducing the method for determining the edge application server EAS proposed in this application, a brief explanation of the relevant terms involved in this application is first given.

[0120] (1) Edge Data Network (EDN)

[0121] Typically, an EDN corresponds to a data network, which can be understood as a local data network (local DN). The EDN includes edge-enabling functions and can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logic concept.

[0122] Another understanding of EDN is that EDN is a peer-to-peer concept of the central cloud. It can be understood as a local data center (that is, a geographical location concept), and can also be identified using DNAI; EDN can include multiple local data networks (local DNs).

[0123] (2) Edge Application Server (EAS)

[0124] EAS can also be called application instance, edge application, edge application instance, Mobile Edge Computing (MEC) application (server) or EAS function, etc.; among them, application instance can refer to an application deployed in the edge data network; in other words, application instance can refer to an instance of a server application deployed and running in the EDN, where the server application can refer to social media software, augmented reality (AR) or virtual reality (VR), etc.

[0125] An application can deploy one or more EAS in one or more EDNs. EAS deployed and running in different EDNs can be understood as different EAS for the same application. These different EAS can share a domain name and use a single IP address, or they can use different IP addresses.

[0126] (3) Application client (AC)

[0127] The AC can be understood as the peer entity of the edge application EAS on the user equipment (UE) side. The AC is used by users to obtain application services from the application server.

[0128] AC can refer to the client program applied on the terminal side; on the one hand, AC can connect to the application server on the cloud to obtain application services, and on the other hand, it can connect to the EAS deployed and running in one or more EDNs to obtain application services.

[0129] (4) Edge Enabling Server (EES)

[0130] EES can provide some enabling capabilities for application instances deployed in EDN, better support the deployment of applications in MEC, support edge application registration, UE authentication and authorization, and provide UE with IP address information of application instances.

[0131] In addition, EES can further support obtaining the identification and IP address information of the application instance, and further send the identification and IP address information of the application instance to the edge data network configuration server.

[0132] The EES is deployed in the EDN. Generally, an EAS is registered on an EES, or an EAS's information is configured on an EES through a management system. The EES is also called the EES associated with the EAS. The EES controls and manages the EAS registered and configured on the EES.

[0133] (5) Edge enabler client (EEC)

[0134] The EEC can be understood as the UE-side counterpart of the EES. It registers EEC and AC information with the EES, performs security authentication and authorization, obtains the EAS IP address from the EES, and provides edge computing capabilities to the AC. For example, the EAS discovery service returns the EAS IP address to the AC.

[0135] It should be noted that application users sign a service agreement with the application provider (e.g., edge computing service provider) to provide services to application users. Application users log in to the AC on the terminal device and communicate through the connection between the AC and the EAS. The EEC of the terminal device can be a middleware layer, generally located in the operating system; or it can be located between the AC and the operating system (OS). The AC can obtain edge enabling services from the EEC through the application program interface (API).

[0136] (6) Edge Configuration Server ECS

[0137] The ECS is responsible for configuring the EDN. For example, it can provide EES information to the UE, directly provide application instance information to the UE, interact with the application's DNS to obtain application instance information, and obtain and save application instance and IP address information from other functional entities.

[0138] (7) 3GPP Stand Alone 6 (SA6) edge application architecture and functional model

[0139] As shown in Figure 4, in a 3GPP edge system, one or more EASs and EESs are deployed in the edge data network (EDN). The EES provides the support functions required by the EAS and EEC. The EES provides functions such as monitoring user equipment (UE), allowing application data traffic exchange with the EAS, and assisting in application context relocation. The UE includes one or more ACs and EECs. The AC resides on the UE and is assisted by the EEC on the UE. The ECS provides configuration related to the EES. The ECS and EES assist the UE in connecting to the EAS. With the assistance of the ECS and EES, the EEC can select an EAS from the available EASs and establish a communication connection between the AC and the selected EAS.

[0140] The application architecture shown in Figure 4 also includes reference points EDGE-1 to EDGE-9, where the EDGE-1 reference point supports interaction between EES and EEC, such as supporting registration from EEC to EES, acquisition of EAS configuration information, and discovery of target EAS in EDN; the EDGE-2 reference point supports interaction between EES and 3GPP core network; the EDGE-3 reference point supports interaction between EES and EAS; the EDGE-4 reference point supports interaction between ECS and EEC; the EDGE-5 reference point supports interaction between AC and EEC; the EDGE-6 reference point supports interaction between ECS and EES; the EDGE-7 reference point supports interaction between EAS and 3GPP CN; the EDGE-8 reference point supports interaction between ECS and 3GPP CN; and the EDGE-9 reference point supports interaction between two EESs.

[0141] (8) Application context migration framework based on the application architecture shown in Figure 4

[0142] The application context migration framework can be divided into four stages:

[0143] (1) Detect that application context relocation may be required: This is to determine if application context relocation may be required. This is usually performed by a detection entity, for example, when the UE location changes or the UE user plane path is updated.

[0144] (2) Decision on application context migration: The detection entity in step (1) informs the decision-making entity(ies), which then decides if application context relocation is needed.

[0145] (3) Execution of application context migration: The decision entity in step (2) notifies the execution entity to perform application context relocation, that is, to transfer the application context from the source EAS to (i.e., transfer) the target EAS, and notifies the terminal side of the target EAS information, notifies the network of the completion of the context migration, and the relevant information of the target EAS (such as the address of the target EAS, the N6 routing information corresponding to the target EAS, etc.).

[0146] It should be noted that the decision making entity, detection entity and execution entity can be the same.

[0147] (4) Cleanup after application context migration: The entity executing step (3) informs all relevant entities to perform post application context relocation actions; for example, the AC initiates a new socket connection to the target EAS, etc.

[0148] (9) EES discovery and EAS discovery process

[0149] The SA6 standard defines the EES platform discovery and EAS discovery processes. This process provides EES platform discovery and application layer instance (e.g., EAS) discovery. EES acts as a local DNS server, and the UE obtains the address of the application instance (e.g., EAS) from the MEC platform. The architecture and functionality are designed to use a two-level discovery mechanism: first discovering the EES platform, then discovering EAS from the EES platform.

[0150] For example, (1) the EEC on the terminal side requests to discover the EES from the ECS (i.e., the UE discovers the EES through the ECS)

[0151] 1) The EEC requests / subscribes to the platform EES corresponding to the UE location (for example, the EES corresponding to the UE's current location or the EES that is available (or connected) nearby) from the ECS. The EEC discovers the EES / EDN of interest from the ECS; where " / " represents or.

[0152] 2) The ECS platform provides detailed information about EAS. The ECS obtains the data network access identifier (DNAI) based on the UE's location and combines the DNAI, fully qualified domain name (FQDN), and EES profile to select the appropriate EES for each application. The EES selection can be based on the UE location and other optional filters.

[0153] 3) ECS obtains the current / potential DNAI corresponding to the UE.

[0154] 4) The EEC obtains information about one or more EESs from the ECS.

[0155] (2) EEC discovers EAS from EES (i.e. EEC discovers EAS through EES)

[0156] 1) Initially, the EEC discovers the application to be used (or connected) from the EES.

[0157] 2) EES matches the information of registered applications; EES matches the edge application instance EAS that meets the user's request based on the information of locally registered / online edge application instances and the discovery filter parameters provided by the user; if multiple EESs meet the requirements, multiple edge application instances EAS can be returned.

[0158] 3) EES returns EAS information to EEC; EEC provides EAS to AC; AC connects to the EAS.

[0159] (10) Public land mobile network (PLMN) and edge computing service provider (ECSP)

[0160] PLMN refers to a network established and operated by the government or an operator approved by it to provide land mobile communication services to the public. For example, the PLMN ID of service provider A is X1, and the PLMN ID of service provider B is X2.

[0161] ECSP generally refers to a service provider that provides edge computing services. For example, the ECSPID of service provider B is X3.

[0162] It should be noted that, for example, the application provider corresponding to application 1 is F1; the application provider F1 can request the PLMN or ECSP to deploy the server corresponding to application 1 in its own network; for example, the PLMN (or ECSP) can deploy ECS and EES in the network; accordingly, the EEC deployed by the PLMN (or ECSP) on the terminal device (for example, UE), that is, the EEC is also provided by the corresponding PLMN (or ECSP).

[0163] (11) EAS deployment and sharing

[0164] EAS can be shared. For example, PLMN B / ECSP B requests PLMN A / ECSP A to deploy EAS. PLMN A / ECSP A can then share the deployed EAS with users of PLMN B / ECSP B. That is, the EAS can now be used by users of PLMN A / ECSP A and users of PLMN B / ECSP B. The EAS can be deployed by PLMN A / ECSP A. Based on the cooperative relationship between PLMN A / ECSP A and PLMN B / ECSP B, PLMN A / ECSP A can determine that the EAS can be shared with PLMN B / ECSP B.

[0165] It should be noted that "A" (or "B") is used to exemplify the service provider A (or B); the " / " involved in the text means or.

[0166] In some cases, for example, when UE-B is in the service area of ​​PLMN A / ECSP A, even if PLMN B / ECSP B has not deployed EES and EAS within the service area of ​​PLMN A / ECSP A, UE-B can still connect to the nearest shared EAS-1, and the PLMN (serving PLMN / serving ECSP) currently accessed by UE-B is PLMN B or ECSP B. For example, if ECSP#B, to which UE-B belongs, has not deployed EAS for UE-B within the service area of ​​PLMN A / ECSP A, UE-B can connect to the sharable EAS-1 deployed by ECSP#A, which is closer to UE-B, as shown in 501 in FIG5 (a).

[0167] In some cases, UE-B is in the service area of ​​PLMN A / ECSP A. Even if PLMN B / ECSP B does not deploy EES and EAS within the service area of ​​PLMN A / ECSP A, UE-B can still connect to the nearest shared EAS-1. In this case, the PLMN (serving PLMN) currently accessed by UE-B is PLMN A, or the ECSP (serving ECSP) currently accessed by UE-B is ECSP A. For example, ECSP#B, to which UE-B belongs, does not deploy EAS for UE-B within the service area of ​​PLMN A / ECSP A. However, UE-B can connect to the shareable EAS-1 deployed by ECSP#A, which is closer to UE-B.

[0168] EAS deployment varies in different scenarios. For example, in some scenarios, an EAS-1 is deployed on an EES-A1 that can be shared by users of PLMN B / ECSP B (e.g., UE-B) and users of PLMN A / ECSP A (e.g., UE-A). It should be noted that EES-A1 is an EES deployed in PLMN A / ECSP A that can provide services to users of PLMN A / ECSP A. This is shown as 502 in Figure 5(a).

[0169] In other scenarios, for an EES-A1 of a certain EESID, not only EAS-1 that can be used by PLMN B / ECSP B users (e.g., UE-B) and PLMN A / ECSP A users (e.g., UE-A) is deployed, but also EAS-A that can be used by PLMN A / ECSP A users is deployed, as shown in 503 in (b) of FIG5 . It should be noted that ECS-A is deployed by PLMN A or ECSP A.

[0170] In other words, for a group of UEs using the same application (for example, application 1), on the one hand, the group of UEs can be connected to the same EAS to reduce signaling interactions between EASs. For example, as shown in (a) in Figure 6, UE1, UE2, and UE3 are a group of UEs using application X. At this time, UE1, UE2, and UE3 are connected to the same EAS-1, for example, EAS-1(B), to obtain edge computing services. In this case, EAS-1(B) can process the application context information of a group of UEs.

[0171] On the other hand, the group of UEs can be connected to different EASs, and each UE can be connected to an EAS that is closer to obtain better service key performance indicators (KPIs). In this case, application contexts need to be synchronized between EASs, that is, EAS-1X, EAS-2X, and EAS-3X need to synchronize the application context information corresponding to UE1, UE2, and UE3 respectively; for example, as shown in (b) of Figure 6, UE1 to UE3 are connected to different EAS-1X, EAS-2X, and EAS-3X respectively through different EESs.

[0172] The above briefly describes the relevant terms involved in this application. The following describes the method for determining the edge application server EAS proposed in this application.

[0173] As can be seen from the background technology, in some business scenarios (for example, multiple UEs team up to play games), considering that the service capabilities provided by different EASs may not be the same, if multiple UEs in the same group are connected to different EASs, fairness between users may be affected. For example, when UE-B (i.e., a user of PLMN B / ECSP B) and UE-A (i.e., a user of PLMN A / ECSP A) are in the same group, UE-B and UE-A may be connected to different EASs. In this case, not only does it need to synchronize application contexts, but it also affects fairness between users.

[0174] Therefore, the present application proposes a method for determining an edge application server EAS, which enables the same group of UEs to be connected to the same EAS, thereby eliminating the need to synchronize application contexts, thereby ensuring fairness in obtaining services for each UE in the same group.

[0175] As shown in FIG. 7A , a method 700 for determining an edge application server EAS is shown. Before introducing the method 700 , a brief introduction to the execution subject of the method 700 is first given.

[0176] The first ECS (or first EES) involved in method 700 can be a network device, or a chip, chip system, or processor applied to the network device, or a logical node, logic module or software that can realize all or part of the network device functions; the first terminal can be a terminal device, or a chip, chip system, or processor applied to the terminal device, or a logical node, logic module or software that can realize all or part of the terminal functions.

[0177] Illustratively, the network device may be the network device 210 in Figure 1 ; the terminal device may be the terminal device 230 or the terminal device 240 in Figure 1 . It should be noted that the network device and the terminal device may have the receiver structure shown in Figure 3 .

[0178] The following embodiment describes the method 700 for determining an edge application server EAS as an example in which the execution subject is a first terminal, a first ECS, and a first EES. The method 700 includes steps 701 to 704, which are described in detail below:

[0179] It should be noted that, before executing step 701, the first terminal will first log in to the server to obtain a group identifier; the first terminal is any terminal in the terminal group; multiple terminals in the terminal group may belong to different service providers (e.g., PLMN and / or ECSP); FIG7B shows a method 700A for multiple terminals in a terminal group to obtain a group identifier, and the method 700A includes steps 7011 to 7014, which are specifically as follows:

[0180] Step 7011: The AC of each terminal (for example, the first terminal) among the multiple terminals logs in (or connects) to a server (for example, a login server) and sends a team request message to the server. The team request message includes (or carries): PLMN information or ECSP information corresponding to each terminal (for example, the first terminal), wherein the PLMN information includes but is not limited to a PLMN identifier (PLMN ID), and the ECSP information includes but is not limited to an ECSP identifier (ECSPID).

[0181] Step 7012: The server may determine a terminal group (or a group of UEs or multiple UEs or multiple terminals) based on teaming request messages sent by multiple terminals, and assign a group ID to the terminal group; then determine the PLMN information and / or ECSP information corresponding to the terminal group based on the PLMN information or ECSP information of each terminal (e.g., the first terminal), and generate service provider information using the PLMN information and / or ECSP information corresponding to each terminal.

[0182] For example, terminal group 1 includes UE1 and UE2. Teaming request message 1 sent by UE1 includes that the service provider supported by UE1 is PLMN A; teaming request message 2 sent by UE2 includes that the service provider supported by UE2 is ECSP B; the server teams UE and UE2 according to teaming request message 1 and teaming request message 2, and assigns group ID 001; the server then generates service provider information 1 corresponding to group ID 001 according to PLMN A and ECSP B; the service provider information 1 includes PLMN A and ECSP B.

[0183] It should be noted that the PLMN information may be a PLMN list for recording PLMN information (eg, PLMN identifier); and the ECSP information may be an ECSP list for recording ECSP information (eg, ECSP identifier).

[0184] In some embodiments, the service provider information list is a PLMN list or an ECSP list; in other embodiments, the service provider information list can be a PLMN and ECSP list formed by PLMN information and ECSP information, or can be a PLMN list and an ECSP information list. The PLMN list includes PLMN identifiers, etc., and the ECSP list includes ECSP identifiers, etc.

[0185] Step 7013: The server sends the group identifier and service provider information (eg, a service provider information list) to multiple terminals in the terminal group. In one possible implementation, the group identifier and service provider information are sent to ACs on multiple terminals in the terminal group.

[0186] Step 7014: The AC of each terminal sends a request message 1 to its corresponding EEC. The request message 1 may include at least one of the following information: requested EASID information, application identification information, application group identification (application group ID) and service provider information (for example, PLMN list and / or ECSP list information).

[0187] It should be noted that, in some embodiments, the application group identifier may refer to the above-mentioned group identifier; the request message 1 may refer to an AC registration request message, and the specific content carried by the AC registration request message is not limited in this application; the AC registration request message includes an AC profile, an application group profile, a group ID, and service provider information (for example, a PLMN list and / or ECSP list information).

[0188] Optionally, the method 700A may further include:

[0189] Step 7015: The EEC of each terminal sends a response message 1 to its corresponding AC; the response message 1 is used to indicate whether the request message 1 is successfully received or processed. The response message 1 may refer to a registration response message; this application does not limit the specific content carried by the registration response message. The registration response message is used to notify each AC of the success or failure of the registration.

[0190] It should be noted that steps 7011-7013 can be implemented in other ways, that is, the AC can have local configuration information, or the AC can determine a group of UEs based on the user's choice. At this time, the AC can determine a group of UEs by itself, and determine the group identifier (group ID) corresponding to the group of UEs, as well as a group of service provider information corresponding to the group identifier.

[0191] The first ECS may correspond to one or more EESs, wherein the one or more EESs may be registered on the first ECS so that the first ECS can manage the one or more EESs. In addition, the first ECS may also obtain information about multiple EESs through the operation administration and maintenance (OAM) system. Different EESs may allow terminals corresponding to different service providers to use (or connect to) them.

[0192] For example, EES-1 allows UEs served by service providers A and / or B to use (or connect to) EES-2; and EES-2 allows UEs served by service providers B and C to use (or connect to) EES-2.

[0193] In some embodiments, the EES can obtain EAS information when the EAS is registered with the EES, or obtain EAS related information through the operation, maintenance and management (OAM) system configuration; for example, one or more EASs can be registered on a single EES, and the EAS can be a shared EAS or a non-shared EAS; wherein, the shared EAS can be used (or connected) by terminals of the PLMN and / or, used (or connected) by terminals of the ECSP, while the non-shared EAS can generally be used (or connected) by terminals of a designated service provider (e.g., PLMN or ECSP).

[0194] It should be noted that the service providers (eg, PLMN or ECSP) supported by EES can be determined by deploying their own service providers, or by requiring EAS-supported service providers (eg, PLMN or ECSP) to be registered on their own platforms.

[0195] FIG7C shows a schematic diagram of a process for registering a shared EAS with a first EES and vice versa. The following uses the example of registering a shared EAS with a first EES to describe a method 700B for the first EES to obtain information about the shared EAS. The method 700B includes the following steps:

[0196] Step 7021: The shared EAS (e.g., EAS-1) sends an EAS registration request message to the first EES (e.g., EES#A1); the EAS registration request message may generally carry the first EAS identification information, the first EAS address information, and the PLMN information or ECSP information supported (or allowed) by the shared EAS (e.g., the user corresponding to the PLMN or ECSP can obtain services from the EAS).

[0197] The first EAS identification information includes but is not limited to the shared EAS ID, and the first EAS address information includes but is not limited to the shared EAS Internet protocol (IP) address and uniform resource locator (URL) address.

[0198] For example, when a shared EAS can be used by users of PLMN B and PLMN A, and the EAS is deployed by PLMN A with which the home / lead PLMN B requests cooperation, the supported PLMN information includes PLMN B and PLMN A. When a shared EAS can be used by users of ECSP B and ECSP A, and the EAS is deployed by ECSP A with which the home / lead ECSP B requests cooperation, the supported ECSP information includes ECSP B and ECSP A.

[0199] Optionally, the method 700B may further include step 7022: after the first EES receives the EAS registration request message, the first EES may determine PLMN information (e.g., PLMN B and PLMN A) corresponding to the shared EAS, or ECSP information (e.g., ECSP B and ECSP A).

[0200] In some embodiments, the first EES may further determine the PLMN information corresponding to the first EES. For example, the PLMN information (or ECSP information) supported by the first EES may be determined based on the PLMN information (or ECSP information) supported by the shared EAS.

[0201] In some other embodiments, the first EES may also determine the ECSP information (or PLMN information) corresponding to the first EES according to the shared EAS and the ECSP (or PLMN) supported by the first EES.

[0202] Step 7023: The first EES sends an EAS response message to the shared EAS; the EAS response message is used to indicate whether the shared EAS registration is successful or failed.

[0203] It should be noted that steps 7021 to 7023 may be replaced by the first EES obtaining the PLMN information (or ECPS information) corresponding to the shared EAS in a pre-configured manner. For example, the above information may be configured on the first EES through the OAM system.

[0204] As shown in FIG7C , a method 700C for registering a first EES with a first ECS includes the following steps:

[0205] Step 7031: The first EES sends an EES registration request message to the first ECS (e.g., ECS-A); the EES registration request message may carry identification information of the first EES, address information of the first EES, PLMN information (or ECSP information) supported by the first EES, and / or PLMN information (or ECSP information) supported by the shared EAS; optionally, the EES registration request message may also carry identification information of the shared EAS (e.g., the shared EAS identifier) ​​and address information of the shared EAS.

[0206] Among them, the PLMN information supported by the first EES is used to indicate the terminal use (or connection) of the PLMN supported by the first EES; the ECSP information supported by the first EES is used to indicate the terminal use (or connection) of the ECSP supported by the first EES; the PLMN information supported by the shared EAS is used to indicate the terminal use (or connection) of the PLMN supported by the shared EAS; the ECSP information supported by the shared EAS is used to indicate the terminal use (or connection) of the ECSP supported by the shared EAS.

[0207] It should be noted that the first EES identification information includes but is not limited to the ID of the first EES, and the first EES address information includes but is not limited to the IP address and URL address of the first EES; the PLMN information (or ECSP information) supported by the first EES can be determined by sharing the EAS supported PLMN information (or ECSP information).

[0208] For example, taking a shared EAS that can be shared (i.e., jointly used (or connected)) by multiple terminals served by ECSP A and ECSP B as an example, when the shared EAS sends an EAS registration request message to the first EES, the EES registration request message needs to carry the PLMN information (or ECSP information) supported by the shared EAS, so that the first EES can determine that it supports sharing of terminals served by ECSP A and ECSP B.

[0209] For another example, if the first EES is deployed by ECSP A, it means that the first EES allows terminals served by ECSP A to use (or connect to) the service. If the EES registration request message carries the PLMN information (or ECSP information) supported by the shared EAS, the PLMN information (or ECSP information) supported by the first EES can be determined based on the PLMN information (or ECSP information) supported by the shared EAS.

[0210] For example, if a first EES is deployed by ECSP A, the first EES supports the use (or connection) of terminals served by ECSP A. However, a shared EAS supports (or allows) the use (or connection) of terminals served by ECSP A and ECSP B. Therefore, the first EES can determine, based on the information about ECSP A and ECSP B supported by the shared EAS, that the first EES can also be used (or connected) by terminals served by ECSP A and ECSP B.

[0211] Step 7032: After receiving the EES registration request message, the first ECS may determine the PLMN information (eg, PLMN B and PLMN A) or ECSP information (eg, ECSP B and ECSP A) corresponding to the EES.

[0212] In some embodiments, the first ECS may further determine the PLMN information (or ECSP information) supported by the first EES based on the PLMN (or ECSP information) supported by the shared EAS.

[0213] In some other embodiments, the first ECS may further determine the ECSP information / PLMN information corresponding to the first EES according to the shared EAS and the ECSP / PLMN supported by the first EES.

[0214] Step 7033: The first ECS sends an EES response message to the EES; the EES response message is used to indicate whether the EES registration is successful or failed.

[0215] It should be noted that steps 7031 to 7033 may be replaced by the first ECS obtaining the PLMN information (or ECPS information) corresponding to the first EES in a pre-configured manner. For example, the above information may be configured on the first ECS through the OAM system.

[0216] It should be noted that there is no limitation on the execution order of method 700B and method 700C.

[0217] FIG7D shows a flowchart of a non-shared EAS (e.g., the third EAS or the fifth EAS described below) registering with an EES and vice versa. The following uses the registration of a non-shared EAS with a first EES as an example to illustrate a method 700D for the first EES to obtain information about the non-shared EAS. The method 700D includes the following steps:

[0218] Step 7041: The non-shared EAS (e.g., EAS-A) sends an EAS registration request message 1 to the first EES (e.g., EES-A2). The EAS registration request message 1 may generally carry the second EAS identification information, the second EAS address information, and the PLMN information (or ECSP information) supported (or allowed) by the second EAS (e.g., PLMN ID information or ECSPID information allowed to be accessed).

[0219] Among them, the second EAS identification information includes but is not limited to the ID of the non-shared EAS, and the second EAS address information includes but is not limited to the IP address and URL address of the non-shared EAS; the PLMN information supported by the second EAS is used to indicate that the non-shared EAS can be connected to the terminal of the service provider indicated by the above PLMN information (for example, PLMN ID) to obtain the services of the edge application; the ECSP information supported by the non-shared EAS is used to indicate that the non-shared EAS can be connected to the terminal of the service provider indicated by the above ECSP information (for example, ECSPID) to obtain the services of the edge application.

[0220] Step 7042: After receiving the EAS registration request message 1, the first EES may determine the PLMN information (eg, PLMN A) or ECSP information (eg, ECSP A) corresponding to the non-shared EAS.

[0221] Step 7043: The first EES sends EAS response information 1 to the non-shared EAS; the EAS response information 1 is used to indicate whether the non-shared EAS registration is successful or failed.

[0222] As shown in FIG7D , a method 700E for registering a first EES with a first ECS includes the following steps:

[0223] Step 7051: The first EES sends an EES registration request message 1 to the first ECS (e.g., ECS-A); the EES registration request message 1 may carry the first EES identification information, the first EES address information, and the PLMN information (or ECSP information) supported by the first EES, and / or carry the PLMN information (or ECSP information) supported by non-shared EAS.

[0224] Among them, the PLMN information supported by the first EES is used to indicate the terminal use (or connection) of the PLMN supported by the first EES; the ECSP information supported by the first EES is used to indicate the terminal use (or connection) of the ECSP supported by the first EES; the PLMN information supported by the non-shared EAS is used to indicate the terminal use (or connection) of the non-shared EAS supported PLMN; the ECSP information supported by the non-shared EAS is used to indicate the terminal use (or connection) of the non-shared EAS supported ECSP.

[0225] It should be noted that the PLMN information (or ECSP information) supported by the non-shared EAS is the same as the PLMN information (or ECSP information) supported by the first EES.

[0226] Step 7052: After the first ECS receives the EES registration request message, the first ECS may determine the PLMN information (eg, PLMN A) or ECSP information (eg, ECSP A) corresponding to the first EES.

[0227] Step 7053: The first ECS sends EES response information 1 to the EES; the EES response information 1 is used to indicate whether the EES registration is successful or failed.

[0228] It should be noted that a terminal of a PLMN (or ECSP) or a terminal corresponding to a PLMN (or ECSP) can be understood as a terminal belonging to a certain PLMN (or ECSP), or can be understood as a terminal located within a service area provided by a certain PLMN (or ECSP).

[0229] It should also be noted that steps 7051 to 7053 can be replaced by the first ECS obtaining the PLMN information (or ECPS information) corresponding to the first EES through pre-configuration. For example, the above information can be configured on the first ECS through the OAM system.

[0230] Before introducing steps 701 to 704, it should be noted that the meaning of "supported" in "PLMNs or ECSPs supported by EES / EAS / ECS" can also be understood as "allowed," "corresponding," or "attributed," etc., and this application does not limit this. In addition, the PLMN / ECSP corresponding to a terminal device (e.g., a first terminal, a second terminal, etc.) can also be understood as the PLMN / ECSP to which the terminal device belongs, or as the PLMN / ECSP currently being served by the terminal device, and this application does not limit this.

[0231] It should also be noted that, in addition to including the group identifier and service provider information, the request message involved below (for example, the first request message, the second request message, etc.) may also include application information in some scenarios, wherein the application information includes at least one of an application identifier (application ID), an AC identifier (AC ID) corresponding to a terminal (for example, the first terminal, the second terminal, etc.), or an EAS identifier (EAS ID). For example, application information corresponding to at least one EES corresponding to the ECS. In addition, ECS-related entities (for example, the first ECS, the second ECS, the first ECS-ER, the second ECS-ER, etc.) may determine EES / EAS in combination with application information in addition to determining EES / EAS based on the group identifier and service provider information, and this application does not limit this; similarly, EES (for example, the first EES, the second EES, etc.) may determine EAS in combination with application information in addition to determining EAS based on the group identifier and service provider information, and this application does not limit this. Due to limited space, some examples may not illustrate the scenario where ECS / EES combines application information to determine EES or EAS. However, this does not mean that ECS / EES cannot combine application information to determine EES / EAS.

[0232] Steps 701 to 704 are described in detail below:

[0233] Step 701: The first terminal sends a first request message to the first ECS, where the first request message is used to request edge enabling server EES information. The first request message includes a group identifier and service provider information. The group identifier is an identifier of a terminal group corresponding to multiple terminals, and the terminal group includes the first terminal. The service provider information is used to indicate PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group. Accordingly, the first ECS receives the first request message from the first terminal.

[0234] Among them, the group identifier can refer to a string of characters, such as 000001 or 0A000B01, etc., which can be designed according to the actual application scenario and is not limited in this application.

[0235] The above-mentioned service provider information can also be understood as PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group corresponding to the group identifier; for example, the PLMN information can be represented in the form of a PLMN list, and / or the ECSP information can also be represented in the form of an ECSP list; in actual applications, the PLMN information (or ECSP information) can also be expressed in other available data forms, and this application does not limit this.

[0236] The PLMN information includes but is not limited to a PLMN identifier, and / or the ECSP information includes but is not limited to an ECSP identifier. Since different terminals may be in network services provided by different service providers, the PLMN identifier and / or ECSP identifier can be used to accurately distinguish the network services of different terminals, thereby facilitating matching of appropriate EES and EAS for each terminal.

[0237] It should be noted that the identifier involved below (for example, the identifier of the third terminal, etc.) can refer to a string of characters, such as a digital string (for example, 0002020020), a character string (ERJRT) or a digital character string (274352EKTKG), etc. The specific form of the identifier is not limited in this application and can be designed according to the specific application scenario.

[0238] In some embodiments, the first request message includes the group identifier and the service provider information, which can also be understood as the first request message including the service provider information corresponding to the group identifier; the first request message can refer to a service provisioning request message; the service configuration request message can carry (or include) the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier (PLMN ID list / ECSPID list information corresponding to the group ID); wherein, the service provider information carrying the group identifier is used to indicate that the service provider corresponding to the terminal group includes the PLMN ID and ECSPID, or the service provider corresponding to the terminal group includes the PLMN ID, or the service provider corresponding to the terminal group includes the ECSPID.

[0239] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP list information corresponding to the terminal group includes information about two service providers, ECSP A and ECSP B, where "A" and "B" represent service provider identifiers. The manner in which multiple terminals in the terminal group obtain the above group identifier and service provider information can be referred to the relevant description of method 700A below.

[0240] The first terminal (for example, UE-A) sends a first request message to the first ECS (for example, ECS-A, where ECS-A represents the ECS corresponding to / deployed by service provider A) through EEC. The first ECS receives the first request message and determines a shared EES (for example, the first EES below) from multiple EESs based on the service provider information in the first request message.

[0241] It should be noted that, when multiple terminals use the same application and request to form a team to perform services, the application service provider may determine a group of UEs based on certain principles, that is, group the multiple terminals into one group.

[0242] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP list information corresponding to the terminal group includes information about two service providers, ECSP A and ECSP B. The first ECS selects an EES (for example, the first EES below) from multiple EESs managed by the first ECS based on the ECSP list information corresponding to the terminal group that can support terminal access of both ECSP A and ECSP B.

[0243] Step 702: The first ECS determines at least one EES according to the group identifier and service provider information in the first request message.

[0244] In some implementations, after receiving the first request message, the first ECS selects an EES (e.g., the first EES) that matches the PLMN information (or ECSP information) from at least one EES corresponding to the first ECS based on the PLMN information (or ECSP information) corresponding to the group identifier and the PLMN information (or ECSP information) corresponding to the EES associated with the first ECS.

[0245] Optionally, in some scenarios, the first request message may also include application information (for example, at least one of an application identifier, an AC identifier corresponding to the first terminal, etc.). After the first ECS receives the first request message, it can select an EES (for example, the first EES) that matches the PLMN information (or ECSP information) from at least one EES corresponding to the first ECS based on the group identifier, the PLMN information (or ECSP information) corresponding to the group identifier, and the application information.

[0246] Here, "match" can be understood as the multiple PLMN information (or ECSP information) corresponding to the EES can cover the PLMN information (or ECSP information) corresponding to the group identifier; here, "match" can have two meanings: one layer can refer to the multiple PLMNs (or ECSPs) supported by the EES being the same as the PLMN information (or ECSP information) corresponding to the group identifier; the other layer can refer to the multiple PLMNs (or ECSPs) corresponding to the EES including the PLMN information (or ECSP information) corresponding to the group identifier.

[0247] For example, after receiving the first request message, the first ECS (e.g., ECS-A) compares the ECSP information corresponding to the group identifier (e.g., the ECSPID list) with the ECSP information supported by the multiple EESs corresponding to the first ECS, thereby determining the first EES (e.g., EES-A1). The ECSP information supported by the multiple EESs can be understood as the ECSP information corresponding to each EES (or the service provider to which it belongs). For example, EES1 is deployed by ECSP A, so the service provider information corresponding to EES1 is related to ECSP A. In some scenarios, the service provider information corresponding to EES1 can also be determined based on the cooperative relationship between service providers, or the service provider information corresponding to EES1 can also be determined based on the service provider information of its corresponding EAS.

[0248] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. If the first EES on the first ECS supports ECSPs A and B, the first ECS may determine that the shared EES corresponding to the terminal group is the first EES (for example, EES-A1).

[0249] In another implementation, the ECSP information supported by the first EES is ECSP A, and the ECSP information supported by the EAS (for example, shared EAS-1) is ECSP A and ECSP B. Since the EAS (for example, shared EAS-1) is deployed on the first EES, the first ECS can determine that the EES corresponding to the terminal group is the first EES based on the ECSP information supported by the first EES, the ECSP information supported by the EAS, and the ECSP information corresponding to the terminal group.

[0250] In another implementation, after receiving the first request message, the first ECS selects at least one EES that matches the PLMN information (or ECSP information) from at least one EES associated with the ECS based on the PLMN information (or ECSP information) corresponding to the group identifier and the PLMN information (or ECSP information) corresponding to the EES associated with the ECS. For a specific determination method, refer to the description of the first ECS determining the at least one EES in step 702. In this case, step 704 needs to be executed.

[0251] In another implementation, the first ECS may not perform step 702 , that is, the first ECS may not determine the first EES or may not determine at least one EES. In this case, step 704 needs to be performed.

[0252] Step 703: The first ECS sends a first response message to the first terminal. The first response message includes information of at least one EES. Accordingly, the first terminal receives the first response message from the first ECS.

[0253] Among them, the first response message may refer to a service provisioning response message; the service configuration response message includes at least one EES information (EES information), and the at least one EES information includes at least one EES ID, at least one EES address (EES endpoint), at least one EES corresponding PLMN information (or ECSP information) or at least one EES corresponding EAS corresponding PLMN information (or ECSP information), etc.; wherein, the EES address may refer to the IP address or URL address of the EES, etc.

[0254] In some embodiments, the first response message (e.g., a service configuration response message) includes information about the first EES. Specifically, when the first ECS determines the first EES in step 702, the first response message may include at least one of the EES ID or EES address information corresponding to the first EES. Optionally, the PLMN information (or ECSP information) corresponding to the EES may or may not be included in the first response message.

[0255] In other embodiments, the first response message (e.g., a service configuration response message) includes information of multiple EESs, including information of a first EES, wherein the first EES is one of the multiple EESs. The multiple EES information includes information such as the ID of each EES, each EES address (EES endpoint), and the PLMN information (or ECSP information) corresponding to each EES. In this case, the first ECS may determine at least one EES in step 702, or the first ECS may not perform step 702; in this case, the first ECS may send the first response message (e.g., information of at least one EES corresponding to the first ECS) to the first terminal.

[0256] Step 704: After receiving the first response message of the first ECS, the first terminal determines the first EES according to the first response message.

[0257] In some embodiments, the first response message includes information of the first EES. The first terminal can determine that the EES required to be used (or connected) to obtain EAS (or discover EAS) is the first EES based on the information of the first EES carried in the first response message.

[0258] In other embodiments, the first response message includes multiple EES information, and the first terminal determines the information of the first EES from the multiple EES information based on the PLMN information (or ECSP information) corresponding to the terminal group, thereby determining that the EES to be used (or connected) is the first EES.

[0259] For example, the PLMN information corresponding to the terminal group includes PLMN A and PLMN B, and the first response information includes EES1 information and EES2 information, wherein the PLMN information included in the EES1 information indicates that the service provider supported by EES1 is PLMN A, and the PLMN information included in the EES2 information indicates that the service providers supported by EES2 are PLMN A and PLMN B. The first terminal compares the PLMN information corresponding to the terminal group with the PLMN information included in EES1 and the PLMN information included in EES2, and determines that EES2 is the EES corresponding to the terminal group, that is, the first EES is EES2.

[0260] Optionally, after determining the first EES, the first terminal may report the determined first EES to the first ECS. Specifically, the first terminal may send the group identifier corresponding to the first terminal and the first EES information corresponding to the group identifier to the first ECS, where the first EES information includes at least one of the first EES ID and the EES address information.

[0261] Step 705: The first terminal sends a second request message to the first EES. The second request message is used to request EAS information. The second request message includes a group identifier and service provider information corresponding to the group identifier. Accordingly, the first EES receives the second request message from the first terminal.

[0262] It should be noted that the above-mentioned first EES is the EES corresponding to multiple terminals in the terminal group; in other words, the EES can be used (or connected) as a shared EES by each terminal in the terminal group; and the first EAS is the EAS corresponding to the terminal group; in other words, the EAS can be used (or connected) as a shared EAS by each terminal in the terminal group; multiple terminals in the terminal group are connected to the same EAS (for example, the first EAS), which is conducive to achieving fairness in service acquisition for each terminal.

[0263] The above-mentioned second request message including the group identifier and service provider information can also be understood as the second request message including the group identifier and the service provider information corresponding to the group identifier; optionally, in addition to the group identifier and service provider information, the second request message may also include application information (for example, at least one of the application identifier, the AC identifier corresponding to the first terminal, etc.).

[0264] The second request message may refer to an EAS discovery request message; the EAS discovery request message may include a group identifier, PLMN information and / or ECSP information corresponding to the group identifier, and application information; the service provider information of the group identifier is used to indicate the PLMN ID and ECSPID corresponding to multiple terminals in the terminal group.

[0265] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP list corresponding to the terminal group includes information of two service providers, ECSP A and ECSP B.

[0266] Step 706: The first EES determines at least one EAS according to the second request message.

[0267] In some embodiments, after the first EES receives the second request message from the first terminal, it selects at least one EAS (for example, including the first EAS) that matches the PLMN information (or ECSP information) from at least one EES corresponding to the EES based on the PLMN information and / or ECSP information corresponding to the group identifier in the second request message (for example, the EAS discovery request message) and the PLMN information (or ECSP information) corresponding to the EAS associated with the EES; at this time, step 708 needs to be executed, that is, the UE needs to determine the first EAS from the at least one EAS received.

[0268] In another implementation, the first EES may not execute step 706 , that is, the first EES may not determine the first EAS or at least one EAS. In this case, step 708 needs to be executed.

[0269] In one example, when the multiple PLMN (or ECSP) information supported by the first EAS is the same as the multiple PLMN (or ECSP) information indicated by the PLMN information (or ECSP information) corresponding to the group identifier, or the multiple PLMN (or ECSP) information supported by the first EAS includes the multiple PLMN (or ECSP) information indicated by the PLMN information (or ECSP information) corresponding to the group identifier, the first EES determines that the first EAS (for example, shared EAS-1) is the shared EAS of the terminal group.

[0270] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The service providers (for example, ECSPs) supported by EAS are ECSP A and ECSP B. The EES can determine, based on the ECSPs supported by the EAS, that the shared EAS corresponding to the terminal group is the first EAS. The first EAS is commonly connected to terminals that can be served by ECSP A and ECSP B.

[0271] Step 707: The first EES sends a second response message to the first terminal, where the second response message includes information of at least one EAS. Correspondingly, the first terminal receives the second response message of the first EES.

[0272] Among them, the second response message may refer to an EAS discovery response message; the EAS discovery response message includes at least one EAS information (EAS information), and the at least one EAS information includes the EAS ID, at least one EAS address (EAS endpoint), at least one EAS corresponding PLMN information (or ECSP information) or at least one EES corresponding EAS corresponding PLMN information (or ECSP information), etc.; wherein, the EAS address may refer to the EAS IP address or URL address, etc.

[0273] In some embodiments, the second response message (e.g., EAS discovery response message) includes information about the first EAS. Specifically, when the first EES determines the first EAS in step 706, the second response message may include at least one of the EAS ID or EAS address information corresponding to the first EAS. Optionally, the PLMN information (or ECSP information) corresponding to the EAS may or may not be included in the second response message.

[0274] In other embodiments, the second response message (e.g., an EAS discovery response message) includes multiple EAS information, including information about a first EAS, where the first EAS is one of the multiple EASs. The multiple EAS information includes the ID of each EAS, each EAS address, and the PLMN information (or ECSP information) corresponding to each EAS. In this case, the first EES may determine at least one EAS in step 706, or the first EES may not perform step 706; in this case, the first EES may send the second response message (e.g., the at least one EAS information corresponding to the first EES) to the first terminal.

[0275] Step 708: The first terminal determines the first EAS according to the second response message.

[0276] In some embodiments, the second response message includes the first EAS information, and the first terminal may determine that the EAS to be used (or connected) is the first EAS according to the first EAS information carried in the second response message.

[0277] In other embodiments, the second response message includes multiple EAS information. The first terminal can determine the information of the first EAS from the multiple EAS information based on the PLMN information (or ECSP information) corresponding to the terminal group, thereby determining that the EES to be used (or connected) is the first EAS.

[0278] For example, the ECSP information corresponding to the terminal group includes ECSP A and ECSP B, and the first response information includes EAS1 information and EAS2 information. The ECSP information included in the EAS1 information indicates that the service provider supported by EAS1 is ECSP A, and the ECSP information included in the EAS2 information indicates that the service providers supported by EAS2 are ECSP A and ECSP B. The first terminal compares the ECSP information corresponding to the terminal group with the ECSP information included in EAS1 and the ECSP information included in EAS2, and determines that EAS2 is the EAS corresponding to the terminal group, that is, the first EAS is EAS2.

[0279] Optionally, after determining the first EAS, the first terminal may report the determined first EAS to the first EES. Specifically, the first terminal may send the group identifier corresponding to the first terminal and first EAS information corresponding to the group identifier to the first EES, where the first EAS information includes at least one of the first EAS ID and EAS address information.

[0280] After the first terminal determines the first EAS, it can connect to the first EAS, thereby connecting to the same EAS as other terminals in the terminal group. This not only avoids synchronization of application contexts between different EASs, but also ensures fairness in obtaining services for each terminal device in the terminal group.

[0281] In the above-mentioned method 700, the first request message sent by the terminal device to the first ECS includes a group identifier and corresponding service provider information, wherein the group identifier and the corresponding service provider information enable the first ECS to select an EES (for example, a first EES) that can be used (or connected) together for multiple terminal devices (for example, UE-A) in the terminal group, and enable the EES to select an EAS (for example, a first EAS) that can be accessed (or connected) together for multiple terminal devices in the terminal group. Multiple terminals in the terminal group are connected to the same EAS, which not only avoids the synchronization of application contexts between different EASs, but also ensures fairness in the service acquisition of each terminal device in the terminal group.

[0282] The above describes method 700 for the first terminal in a terminal group to obtain a shared EAS (eg, the first EAS). Next, a method 800 for the second terminal in the terminal group to determine an EAS is described with reference to FIG8 . Before describing method 800 , a brief description is first given of the execution body of method 800 .

[0283] The second ECS (or second EES) involved in method 800 can be a network device, or a chip, chip system, or processor applied to the network device, or a logical node, logic module or software that can realize all or part of the network device functions; the second terminal can be a terminal device, or a chip, chip system, or processor applied to the terminal device, or a logical node, logic module or software that can realize all or part of the terminal functions.

[0284] Illustratively, the network device may be the network device 210 in Figure 1 ; the terminal device may be the terminal device 230 or the terminal device 240 in Figure 1 . It should be noted that the network device and the terminal device may have the receiver structure shown in Figure 3 .

[0285] The following embodiment describes the method 800 for determining an EAS by taking the second terminal, the second ECS, and the second EES as an example. The method 800 includes the following steps:

[0286] Step 801: The second terminal sends a third request message to the second ECS, where the third request message is used to request EES information. The third request message includes a group identifier and service provider information (i.e., the service provider information corresponding to the terminal group or the service provider information corresponding to the group identifier). The group identifier is an identifier of a terminal group corresponding to multiple terminals, and the terminal group includes the second terminal. The service provider information is used to indicate the PLMN information and / or ECSP information corresponding to the multiple terminals in the terminal group.

[0287] For the description of the group identifier and service provider information, please refer to the description of the group identifier and service provider information in step 701 above, which will not be repeated here. Optionally, in addition to including the group identifier and service provider information, the third request message may also include application information (e.g., at least one of the application identifier and the AC identifier corresponding to the second terminal).

[0288] The second terminal is a terminal in the terminal group other than the first terminal; for example, the terminal group includes a first terminal, a second terminal and a third terminal, wherein the first terminal may be UE-A, the second terminal is UE-B and the third terminal is UE-C.

[0289] The third request message includes the group identifier and the service provider information, which can also be understood as the third request message including the service provider information carrying the group identifier; the third request message can refer to a service configuration request message; the service configuration request message can carry the PLMN information and / or ECSP information corresponding to the group identifier; the role of the third request message is similar to that of the first request message, and reference can be made to the relevant description of the first request message in the above step 701, which will not be repeated here.

[0290] Step 802: After receiving the third request message from the second terminal, the second ECS sends a fourth request message to the first ECS. The fourth request message is used to request EES information. The fourth request message includes a group identifier and service provider information (i.e., the service provider information corresponding to the terminal group or the service provider information corresponding to the group identifier).

[0291] Among them, the first ECS is usually the ECS corresponding to the first terminal, that is, the ECSPID / PLMN ID corresponding to the first ECS is consistent with the ECSPID / PLMN ID corresponding to the first terminal; the second ECS is usually the ECS corresponding to the second terminal, that is, the ECSP ID / PLMN ID corresponding to the second ECS is consistent with the ECSPID / PLMN ID corresponding to the second terminal.

[0292] It should also be noted that, optionally, the second ECS can determine the first ECS based on the service provider information corresponding to the group identifier carried in the third request message and the service provider information corresponding to other ECSs; optionally, the second ECS can also determine the first ECS based on the service provider information corresponding to the second terminal; specifically, when the service provider information corresponding to the group identifier carried in the third request message is ECSP A / PLMN A, and ECSP B / PLMN B, the service provider information corresponding to the second ECS and the second terminal is ECSP B / PLMN B, and the service provider information corresponding to the first ECS is ECSP A / PLMN A. At this time, the second ECS can determine that it needs to send a fourth request message to the first ECS to obtain EES information.

[0293] After receiving the third request message from the second terminal, the second ECS sends a fourth request message to the first ECS. The fourth request message may also be a service configuration request message. The service configuration request message may carry a group identifier and the PLMN information and / or ECSP information corresponding to the group identifier. Optionally, in addition to the group identifier and service provider information, the fourth request message may also include application information (e.g., at least one of an application identifier and an AC identifier corresponding to the second terminal).

[0294] Step 803: The first ECS determines the first EES according to the group identifier and service provider information in the fourth request message.

[0295] Optionally, the first ECS further determines the first EES according to the group identifier, service provider information, and application information of the fourth request message.

[0296] For example, in some scenarios, the first ECS determines the first EES based on the group identifier in the fourth request message, the service provider information and application information corresponding to the group identifier, the application information corresponding to at least one EES corresponding to the ECS, and / or the ECSP information (or PLMN information) supported by the at least one EES.

[0297] It should be noted that when the first ECS has determined that the first EES is the EES corresponding to the terminal group for other terminals (for example, the first terminal) in the terminal group (specifically refer to step 702 above), the first ECS can directly determine the first EES for the second terminal (or the second ECS) based on the group identifier and / or application message in the fourth request message; when the first ECS has not determined a shared EES for each terminal in the terminal group, the first ECS can determine the first EES based on the group identifier of the fourth request message, the service provider information and application information corresponding to the group identifier, and the application information corresponding to at least one EES corresponding to the ECS, and / or the ECSP information (or PLMN information) supported by the at least one EES. The way in which the first ECS determines the first EES based on the fourth request message can refer to the process in which the first ECS determines the first EES based on the first request message in step 702 above. For example, the fourth request message here corresponds to the first request message in step 701.

[0298] Step 804: The first ECS sends a fourth response message to the second ECS. Correspondingly, the second ECS receives the fourth response message, which includes the group identifier and information about the first EES.

[0299] The fourth response message may also refer to a service configuration response message; the service configuration response message may carry information of the first EES, such as the first EES address, the ID of the first EES, the PLMN information (or ECSP information) corresponding to the first EES, or the PLMN information (or ECSP information) corresponding to the EAS corresponding to the first EES. The second ECS may determine relevant information of the first EES based on the fourth response message.

[0300] Optionally, the second ECS determines the second EES.

[0301] After receiving the fourth response message, the second ECS determines that it has obtained the information of the first EES from the first ECS. At this time, the second ECS determines a second EES (for example, EES-B) in the area served by its corresponding service provider (for example, ECSP B). The second EES is used by the second terminal to send an EAS discovery request message.

[0302] It should be noted that the detailed process of the second ECS determining the first EES in steps 801 to 804 can refer to the process of the first terminal determining the first EES in steps 701 to 704 above; that is, the detailed process of steps 801 to 804 can be obtained by replacing the first terminal in steps 701 to 704 with the second ECS.

[0303] Step 805: The second ECS sends a third response message to the second terminal. The third response message includes information about the first EES and / or information about the second EES. The information about the first EES is the EES in ECSP A / PLMN A, which can specifically provide services for a terminal group (e.g., the first terminal). The information about the second EES is the EES in ECSP B / PLMN B, which can specifically provide services for users of ECSP B and PLMN B. It should be noted that when the second ECS does not determine the second EES, the third response message does not carry information about the second EES.

[0304] The third response message may also be referred to as a service configuration response message; the service configuration response message includes EES information, such as at least one of an EES address and an EES ID, etc. The EES information includes information about the first EES and / or information about the second EES.

[0305] The second ECS sends a third response message to the second terminal; accordingly, the second terminal receives the third response message from the second ECS, and sends an EAS discovery request message (eg, the fifth request message below) to the second EES based on the second EES information in the third response message.

[0306] Step 806: After receiving the third response message, the second terminal sends a fifth request message to the second EES. In response, the second EES receives the fifth request message from the second terminal. The fifth request message is used to request EAS information and includes the group identifier, service provider information, and information about the first EES. The function of the fifth request message is similar to that of the second request message. For details about the second request message in step 705 above, please refer to the description of the second request message and will not be repeated here.

[0307] Step 807: The second EES sends a sixth request message to the first EES based on the information of the first EES. Correspondingly, the first EES receives the sixth request message from the second EES. The sixth request message is used to request EAS information and includes a group identifier and service provider information.

[0308] The sixth request message may be an EAS discovery request message; the EAS discovery request message may carry PLMN information and / or ECSP information corresponding to the group identifier. The function of the sixth request message is similar to that of the second request message. For details about the second request message in step 705 above, please refer to the description thereof and will not be repeated here.

[0309] Optionally, the fifth request message (or the sixth request message) may include application information (eg, at least one of an application identifier and an AC identifier corresponding to the second terminal) in addition to the group identifier and the service provider information.

[0310] Step 808: In some examples, the first EES can determine the first EAS (i.e., the EAS corresponding to multiple terminals in the terminal group) based on the group identifier in the sixth request message, the service provider information and application information corresponding to the group identifier, the application information corresponding to at least one EAS corresponding to the EES, and / or the ECSP information (or PLMN information) supported by the at least one EAS.

[0311] It should be noted that when the first EES has determined that the first EAS is the EAS corresponding to the terminal group for other terminals (for example, the first terminal) in the terminal group (specifically, refer to step 706 above), the first EES can directly determine the first EAS for the second terminal (or the second ECS) based on the group identifier in the sixth request message, the service provider information corresponding to the group identifier, and the application information; when the first EES has not determined a shared EAS for each terminal in the terminal group, the first EES can determine the first EAS based on the group identifier in the sixth request message, the service provider information and application information corresponding to the group identifier, and the application information corresponding to at least one EAS corresponding to the EES, and / or the ECSP information (or PLMN information) supported by the at least one EAS. The method for the first EES to determine the first EAS can refer to step 706 above.

[0312] Step 809: The first EES sends a sixth response message to the second EES, where the sixth response message includes the group identifier and information of the first EAS; accordingly, the second EES receives the sixth response message.

[0313] The sixth response message may refer to an EAS discovery response message, which may carry EAS information, such as an EAS address (EAS endpoint), etc. The EAS information may refer to information of the first EAS.

[0314] The first EES sends a sixth response message to the second EES to notify the second EES of the information of the first EAS, including information such as the first EAS address (EAS endpoint).

[0315] Step 810: The second EES sends a fifth response message to the second terminal, where the fifth response message includes the group identifier and information of the first EAS.

[0316] After receiving the fifth response message, the second EES sends a fifth response message to the second terminal (e.g., UE-A); the second terminal receives the fifth response message and determines to establish a communication connection with the first EAS based on the information of the first EAS (e.g., the identifier of the first EAS, etc.), so that the second terminal and other terminals in the terminal group (e.g., the first terminal) are connected to the same first EAS, thereby achieving fairness in obtaining EAS services for each terminal in the terminal group. For a detailed description of the second EES sending the fifth response message to the second terminal, please refer to the relevant description of the first EES sending the second response message to the first terminal in step 707 above.

[0317] Step 811: The second terminal determines the first EAS according to the fifth response message.

[0318] It should be noted that, for a detailed description of step 811 , reference may be made to the description of the first terminal determining the first EAS according to the second response message in step 708 , which will not be repeated here.

[0319] In addition, it should be noted that, in addition to determining the first EES through the second ECS (for example, steps 801 to 804), the second terminal can also directly send a third request message to the first ECS without having to transfer the third request message multiple times through the second ECS to determine the first EES. In addition, in addition to determining the first EAS through the second EES (for example, steps 805 to 812), the second terminal can also determine the first EAS directly through the first EES, and this application does not limit this.

[0320] In some scenarios, the first EES can determine the first EAS, the second EES can also determine the first EAS, or the first terminal can determine the first EAS; for example, when the first EES does not determine the first EAS, the first EES will be able to determine the relevant information of the first EAS (for example, the service provider information corresponding to the EAS, etc.) and send it to the second EES. At this time, the second EES can determine the first EAS based on the relevant information of the first EAS and the service provider information corresponding to the group identifier. Similarly, when neither the first EES nor the second EES determines the first EAS, the first EES will be able to determine the relevant information of the first EAS (for example, the service provider information corresponding to the EAS, etc.) and send it to the second EES. The second EES can send the relevant information that can determine the first EAS (for example, the service provider information corresponding to the EAS, etc.) to the second terminal. At this time, the second terminal can determine the first EAS based on the relevant information of the first EAS and the service provider information corresponding to the group identifier.

[0321] In summary, in the above scheme, the second terminal sends a third request message including a group identifier and service provider information to the second ECS, and the group identifier and service provider information can be used to determine the first EES and the second EES; the second terminal sends a third request message to the second EES, so that the second EES can obtain the first EAS according to the service provider information in the third request message, thereby realizing that each terminal in the terminal group is connected to the same first EAS, which not only avoids the synchronization of application contexts between different EASs, but also ensures the fairness of service acquisition for each terminal device in the terminal group.

[0322] Methods 700 and 800 are described above. Now, a method 900 for determining an edge application server EAS will be described below in conjunction with FIG. 9 . Before introducing the method 900 , a brief introduction will be given to the execution subject of the method 900 .

[0323] The third EES (or fourth EES or first ECS-ER or second ECS-ER) involved in method 900 can be a network device, or a chip, chip system, or processor applied to the network device, or a logical node, logic module, or software that can implement all or part of the network device functions; the third terminal (or fourth terminal) can be a terminal device, or a chip, chip system, or processor applied to the terminal device, or a logical node, logic module, or software that can implement all or part of the terminal functions.

[0324] Illustratively, the network device may be the network device 210 in Figure 1 ; the terminal device may be the terminal device 230 or the terminal device 240 in Figure 1 . It should be noted that the network device and the terminal device may have the receiver structure shown in Figure 3 .

[0325] It should be noted that the "ER" in the ECS entity (edge ​​repository, ER) can be understood as a functional module in the ECS, or a hardware module or chip independent of the ECS. This application does not limit the specific form of the ECS-ER. The ECS-ER can also be described as a central binding server (CBS).

[0326] The following embodiment describes the method 900 for determining an EAS by taking the third terminal, the fourth terminal, the third EES, the fourth EES, the first ECS-ER, and the second ECS-ER as an example. The method 900 includes the following steps:

[0327] Step 901: A third terminal obtains a second EAS, where the third terminal is one of the multiple terminals corresponding to the terminal group.

[0328] It should be noted that the third terminal can perform EES discovery and EAS discovery through the above "(9) EES discovery and EAS discovery process" to obtain the second EAS; for example, ECS selects the shareable EES#1 for the third terminal; the third terminal requests EES#1 to discover EAS, and EES#1 determines the second EAS for the third terminal.

[0329] Step 902: The third terminal sends a seventh request message to the third EES. The seventh request message includes a group identifier, an identifier of the second EAS, and second service provider information. The group identifier is an identifier of the terminal group, and the second service provider information is PLMN information or ECSP information supported by the second EAS. The terminal group includes the third terminal, and the second EAS is the EAS corresponding to the terminal group.

[0330] Optionally, in some scenarios, the seventh request message may include application information (for example, at least one of the application identifier, the AC identifier corresponding to the third terminal, and the ID of the second EAS) in addition to the group identifier, the identifier of the second EAS, and the second service provider information.

[0331] The seventh request message may be a group binding request message; the group binding request message includes but is not limited to the ID of the third terminal, the application information of the third terminal, the group identifier, the address (endpoint) of the second EAS, and the service provider corresponding to the third terminal (for example, PLMN A or ECSP B); the information of the second EAS includes the address information of the second EAS, the PLMN and / or ECSP information supported by the second EAS, for example, the ECSP information includes ECSP A and ECSP B.

[0332] Optionally, in some scenarios, the first ECS-ER feeds back a seventh response message to the third EES, where the seventh response message is used to notify the third terminal of a processing result of the seventh request message.

[0333] Step 903: The third EES sends an eighth request message to the first ECS-ER. The eighth request message includes the group identifier, the identifier of the second EAS, and the second service provider information.

[0334] Optionally, in some scenarios, the eighth request message may include application information (for example, at least one of the application identifier, the AC identifier corresponding to the third terminal, and the ID of the second EAS) in addition to the group identifier, the identifier of the second EAS, and the second service provider information.

[0335] Among them, the eighth request message can be a group binding request message (group binding request); the group binding request message includes but is not limited to the ID of the third terminal, the application information of the third terminal, the group identifier, the address (endpoint) information of the second EAS and the service provider corresponding to the third terminal (PLMN A or ECSP B).

[0336] It should be noted that the PLMN / ECSP corresponding to the third EES and the first ECS-ER are the same, that is, the PLMN or ECSP for deploying the third EES and the first ECS-ER are the same.

[0337] Optionally, in some scenarios, the first ECS-ER feeds back an eighth response message to the third EES, and the eighth response message may be used to notify the third EES of the processing result of the eighth request message.

[0338] Step 904: The first ECS-ER determines to send query information to the second ECS-ER based on the second service provider information. Accordingly, the second ECS-ER receives the query information from the first ECS-ER. The query information is used to query group information for the third terminal. This group information includes, but is not limited to, a group identifier for the terminal group to which the third terminal belongs and PLMN information and / or ECSP information corresponding to multiple terminals in the terminal group. Based on the group information, the first ECS-ER can determine the ECS-ERs corresponding to the multiple terminals in the terminal group.

[0339] It should be noted that the first ECS-ER can determine the second ECS-ER in the following manner:

[0340] In a possible implementation, the first ECS-ER may determine the second ECS-ER according to the second service provider information of the second EAS corresponding to the third terminal and the corresponding service provider information of the second ECS-ER stored in the first ECS-ER.

[0341] In another possible implementation, the first ECS-ER may further determine the second ECS-ER based on the service provider information corresponding to the group identifier; for example, if the service providers corresponding to the group identifier are PLMN A and PLMN B, the first ECS-ER may send query information to the ECS-ER corresponding to PLMN A and the ECS-ER corresponding to PLMN B, respectively.

[0342] Step 905: The first ECS-ER sends a ninth request message to the second ECS-ER; accordingly, the second ECS-ER receives a ninth request message from the first ECS-ER, the ninth request message including a group identifier, an identifier of the second EAS, and information about the second service provider; the ninth request message is used to instruct the second ECS-ER to migrate the terminal device corresponding to the second ECS-ER (e.g., the fourth terminal below) and the terminal device corresponding to the group identifier in the ninth request message (e.g., the fourth terminal below) to a shared EAS (e.g., the second EAS). It should be noted that the terminal device corresponding to the second ECS-ER (e.g., the fourth terminal below) means that the service provider information of the second ECS-ER and the terminal device is consistent, and the terminal device may subsequently be connected to at least one of the ECS, EES, or EAS of the corresponding service provider.

[0343] Optionally, in some scenarios, the ninth request message may include application information (for example, at least one of the application identifier, the AC identifier corresponding to the third terminal, and the ID of the second EAS) in addition to the group identifier, the identifier of the second EAS, and the second service provider information.

[0344] Step 906: the second ECS-ER sends a ninth response message to the first ECS-ER; accordingly, the first ECS-ER receives a ninth response message from the second ECS-ER, the ninth response message including the group identifier and the second service provider information.

[0345] Step 907: the fourth terminal obtains a third EAS, where the third EAS is the EAS to which the fourth terminal is currently connected, and the fourth terminal is one of the multiple terminals corresponding to the terminal group.

[0346] The way in which the fourth terminal obtains the third EAS may refer to the way in which the third terminal obtains the second EAS in step 901, which will not be repeated here.

[0347] Step 908: The fourth terminal sends a tenth request message to the fourth EES; accordingly, the fourth EES receives the tenth request message; the tenth request message includes a group identifier, an identifier of a third EAS, and third service provider information, where the group identifier is an identifier of the terminal group, and the third service provider information is PLMN information or ECSP information supported by the third EAS;

[0348] Optionally, in some scenarios, the tenth request message may include application information (for example, at least one of the application identifier, the AC identifier corresponding to the fourth terminal, and the ID of the third EAS) in addition to the group identifier, the identifier of the third EAS, and the third service provider information.

[0349] Among them, the tenth request message can be a group binding request message; the group binding request message may include but is not limited to the ID of the fourth terminal, the group identifier and the third service provider information and the application information corresponding to the fourth terminal; wherein the third service provider information includes the address of the third EAS and the service provider corresponding to the fourth terminal (for example, PLMN A or ECSP B), wherein the address of the third EAS includes an IP address or a URL address, etc.

[0350] Step 909: before the fourth EES sends the tenth response message to the fourth terminal, the fourth EES sends an eleventh request message to the second ECS-ER, where the eleventh request message includes the group identifier, the identifier of the third EAS, and the third service provider information.

[0351] Optionally, in some scenarios, the eleventh request message may include application information (for example, at least one of the application identifier, the AC identifier corresponding to the fourth terminal, and the ID of the third EAS) in addition to the group identifier, the identifier of the third EAS, and the third service provider information. The eleventh request message may be a group binding request message; the group binding request message may include, but is not limited to, the ID of the fourth terminal, the group identifier, the third service provider information, and the application information.

[0352] Step 910: The second ECS-ER determines whether to instruct the fourth terminal to migrate from the third EAS to the second EAS based on the second service provider information corresponding to the second EAS.

[0353] The second ECS-ER may determine whether to instruct the fourth terminal to migrate from the third EAS to the second EAS based on the second service provider information (eg, PLMN information and / or ECSP information) corresponding to the second EAS sent by the first ECS-ER.

[0354] In some scenarios, for example, when the service provider information corresponding to the fourth terminal is partially or completely the same as the second service provider information corresponding to the second EAS, it means that the second EAS can provide services for the fourth terminal. At this time, the second ECS-ER can instruct the fourth terminal to migrate from the third EAS to the second EAS.

[0355] Step 911: When the second ECS-ER determines that the fourth terminal has migrated from the third EAS to the second EAS, the second ECS-ER sends an eleventh response message to the fourth EES. The eleventh response message is used to instruct the fourth terminal to migrate from the third EAS to the second EAS. The eleventh response message can be a group binding response message; the group binding response message includes a group identifier and information about the second EAS.

[0356] Step 912: The fourth EES sends a tenth response message to the fourth terminal; accordingly, the fourth terminal receives the tenth response message; the tenth response message is used to instruct the fourth terminal to migrate from the third EAS to the second EAS; the tenth response message can be a group binding response message; the group binding response message includes the group identifier and information of the second EAS.

[0357] In some cases, each terminal in the terminal group may be connected to a different EAS, for example, the third terminal is connected to a shared EAS (for example, the second EAS), and the fourth terminal is connected to a non-shared EAS (for example, the third EAS); the terminal device can enable the fourth terminal to migrate from the third EAS to the shared second EAS through the interaction between the ECS-ERs corresponding to different terminals (for example, the interaction between the first ECS-ER and the second ECS-ER), so as to realize that multiple terminals in the terminal group are connected to the same second EAS, which not only avoids the synchronization of application contexts between different EASs, but also ensures the fairness of service acquisition for each terminal device in the terminal group.

[0358] Methods 700, 800, and 900 are introduced above. Now, a method 1000 for determining an edge application server EAS is introduced in conjunction with FIG10. Before introducing the method 1000, a brief introduction is first given to the execution subject of the method 1000.

[0359] The third ECS (or fourth ECS or fifth EES) involved in method 1000 can be a network device, or a chip, chip system, or processor applied in the network device, or a logical node, logic module or software that can realize all or part of the network device functions; the fifth terminal (or sixth terminal) can be a terminal device, or a chip, chip system, or processor applied to the terminal device, or a logical node, logic module or software that can realize all or part of the terminal functions.

[0360] Illustratively, the network device may be the network device 210 in Figure 1 ; the terminal device may be the terminal device 230 or the terminal device 240 in Figure 1 . It should be noted that the network device and the terminal device may have the receiver structure shown in Figure 3 .

[0361] The following embodiment describes the method 1000 for determining an EAS as an example in which the fifth terminal, the sixth terminal, the fifth EES, the third ECS, and the fourth ECS are executed. The method 1000 includes the following steps:

[0362] Step 1001: The fifth terminal obtains a fourth EAS. The fourth EAS is the EAS corresponding to the terminal group, that is, the common EAS (common EAS) corresponding to the terminal group, which can also be understood as a shared EAS. The fifth terminal is one of the multiple terminals corresponding to the terminal group.

[0363] It should be noted that the fifth terminal can perform EES discovery and EAS discovery through the "(9) EES discovery and EAS discovery process" above to obtain the fourth EAS. For example, the ECS selects a common EES-A1 for the fifth terminal. The fifth terminal requests EES-A1 to discover the EAS, and EES-A1 determines the fourth EAS for the fifth terminal. The fifth terminal can also obtain the fourth EAS through method 700. For details, please refer to the method for obtaining the first EAS in method 700.

[0364] It should be noted that when the fifth terminal (for example, UE-B) sends an EAS discovery request message to EES-A1, the request message may include but is not limited to the group identifier and the PLMN (or ECSP) information corresponding to the terminal group; optionally, in addition to the group identifier and the PLMN (or ECSP) information corresponding to the terminal group, the request message may also include application information (for example, at least one of the application identifier, the AC identifier corresponding to the fifth terminal, the common EES-A1 identifier, etc.).

[0365] EES-A1 determines the common EAS for the fifth terminal as EES-A1 based on the group identifier and EASID. In addition, EES-A1 stores the group identifier, application information, and determined common EES-A1 information (eg, EES-A1 address information).

[0366] Step 1002: The fifth terminal sends a twelfth request message to the third ECS. The twelfth request message includes a group identifier, fourth service provider information, and fifth service provider information. The group identifier is an identifier of the terminal group. The fourth service provider information is the PLMN information and / or ECSP information corresponding to the terminal group. The fifth service provider information is information of the fifth EES or information of the fourth EAS. The fifth EES is the EES corresponding to the terminal group, and the fourth EAS is the EAS corresponding to the terminal group.

[0367] Optionally, in addition to the group identifier, the fourth service provider information and the fifth service provider information, the twelfth request message may also include application information (for example, at least one of the application identifier, the AC identifier corresponding to the fifth terminal, the identifier of the fifth EES, etc.).

[0368] Among them, the twelfth request message can be a first common EES announcement request (common EES information announcement request) or a first common EAS information announcement request (common EAS information announcement request); the first common EES announcement request (or the first common EAS announcement request) can include a group identifier, fourth service provider information, fifth service provider information and application information; wherein, the fourth service provider information is the service provider information corresponding to the terminal group (that is, the service provider information corresponding to the group identifier).

[0369] For example, the fourth service provider information includes: a PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier; the fifth service provider information is information of the fifth EES or information of the fourth EAS, wherein the information of the fifth EES (i.e., the selected common EES information) includes EESID (e.g., EES-A1 ID), address information of EES (e.g., EES-A1), and PLMN information or ECSP information (e.g., PLMN ID or ECSPID) allowed (or supported) by EES; the information of the fourth EAS (i.e., the selected common EAS information) includes EASID (e.g., EAS-1 ID), address information of EAS (e.g., EAS-1), and PLMN information or ECSP information (e.g., PLMN ID or ECSPID) allowed (or supported) by EAS.

[0370] Optionally, in some scenarios, the third ECS feeds back a twelfth response message to the fifth terminal, and the twelfth response message may be used to notify the third ECS of the processing result of the twelfth request message.

[0371] Step 1003: The third ECS receives the twelfth request message from the fifth terminal, and determines to send the thirteenth request message to the fourth ECS based on the twelfth request message; accordingly, the fourth ECS receives the thirteenth request message from the third ECS; the thirteenth request message includes the group identifier, the fourth service provider information and the fifth service provider information; the fourth ECS is the ECS corresponding to a terminal other than the fifth terminal in the terminal group (for example, the sixth terminal).

[0372] Optionally, in addition to the group identifier, the fourth service provider information and the fifth service provider information, the thirteenth request message may also include application information (for example, at least one of the application identifier, the AC identifier corresponding to the fifth terminal, the identifier of the fifth EES, etc.).

[0373] The thirteenth request message may be a second common EES announce request (or a second common EAS announce request); the second common EES announce request (or a second common EAS announce request) includes a group identifier, fourth service provider information, fifth service provider information, and application information.

[0374] For example, the third ECS sends the common EES information (for example, EES-A1) corresponding to the group terminal and the PLMN or ECSP information corresponding to the common EES to the corresponding ECS-A (or ECS-C) in the same group based on the PLMN information or ECSP information corresponding to the common EES (or common EAS), or sends the common EAS information (for example, EAS-1) corresponding to the terminal group and the PLMN or ECSP information corresponding to the common EAS to the corresponding ECS-A (or ECS-C) in the same group.

[0375] It should be noted that the third ECS can determine the fourth ECS in the following manner:

[0376] In a possible implementation, the third ECS may determine the fourth ECS according to the fourth service provider information corresponding to the fifth terminal and the service provider information corresponding to the fourth ECS stored in the third ECS.

[0377] In another possible implementation manner, the third ECS may also determine the fourth ECS based on the fourth service provider information (i.e., the service provider information corresponding to the group identifier); for example, the service providers corresponding to the group identifier are PLMN A and PLMN B. The third ECS may send a thirteenth request message to the ECS corresponding to PLMN A (an example of the fourth ECS) and the ECS corresponding to PLMN B (another example of the fourth ECS), respectively.

[0378] Optionally, in some scenarios, the third ECS feeds back a thirteenth response message to the fourth ECS, and the thirteenth response message may be used to notify the fourth ECS of the processing result of the thirteenth request message.

[0379] Step 1004: The fourth ECS stores the common EES (or common EAS) information corresponding to the group identifier in the thirteenth request message; for example, the fourth ECS (for example, ECS-A) can store the address information of the common EES (or common EAS) and the PLMN (or ECSP) information corresponding to the common EES (or common EAS); optionally, the fourth ECS can also store the common EESID (or common EASID) corresponding to the group identifier and some application information, etc.

[0380] When another terminal device in the terminal group (for example, the sixth terminal) needs to obtain edge computing services, the terminal device will perform EES discovery and EAS discovery. The specific steps are as follows:

[0381] Step 1005: The sixth terminal sends a fourteenth request message to the fourth ECS. Accordingly, the fourth ECS receives the fourteenth request message from the sixth terminal. The fourteenth request message includes a group identifier and sixth service provider information. The terminal group includes the sixth terminal. The sixth service provider information is the PLMN information and / or ECSP information corresponding to the terminal group.

[0382] Optionally, in addition to the group identifier and the sixth service provider information, the fourteenth request message may also include application information (for example, at least one of the application identifier and the AC identifier corresponding to the sixth terminal).

[0383] The fourteenth request message may be a service provisioning request message; the service provisioning request message includes a group ID, service provider information corresponding to the group ID, and application information. For example, the service provider information corresponding to the group ID may be a PLMN ID list / ECSP ID list information corresponding to the group ID (group ID-PLMN ID list / ECSPID list information).

[0384] Step 1006: The fourth ECS sends a fourteenth response message to the sixth terminal, the fourteenth response message including the group identifier and information about the fifth EES. The tenth response message may be a service provisioning response message; the service provisioning response message includes information about the fifth EES; the information about the fifth EES may include the address (EES endpoint) of the fifth EES.

[0385] Step 1007: The sixth terminal (e.g., UE-A) sends a fifteenth request message to the fifth EES (e.g., common EES-A1), and accordingly, the fifth EES receives the fifteenth request message from the sixth terminal; the fifteenth request message is used to request EAS information, and the fifteenth request message includes a group identifier, sixth service provider information, and EAS filtering information; optionally, the fifteenth request message may also include application information (e.g., application identifier, service provider information corresponding to the group identifier, application information, etc.).

[0386] Among them, the sixth service provider information includes the PLMN information and / or ECSP information corresponding to the terminal group, and the EAS filtering information includes the information of the fourth EAS, which is used to filter out the fourth EAS, and the fourth EAS is the EAS corresponding to the terminal group; the fifteenth request message can be an EAS discovery request message; the EAS discovery request message can include an EAS discovery filter, a group identifier, the service provider information corresponding to the group identifier, and an application identifier; wherein the service provider information corresponding to the group identifier can be the PLMN identifier list / ECSP identifier list information corresponding to the group identifier, and the EAS filtering information can be an EAS discovery filter, which is used to determine the fourth EAS corresponding to the sixth terminal (that is, the common EAS corresponding to the terminal group).

[0387] Step 1008: The fifth EES determines, according to the fifteenth request message, that the shared EAS corresponding to the sixth terminal is the fourth EAS.

[0388] The fifth EES selects (or determines) that the fourth EAS is EAS-1 for the sixth terminal from the EASs deployed on the fifth EES based on the group identifier, the sixth service provider information, and the EAS filtering information (e.g., the fourth EAS) in the fifteenth request message. At this point, the sixth terminal (e.g., UE-A) and the fifth terminal (e.g., UE-B) obtain the same EAS-1.

[0389] Step 1009: The fifth EES sends a fifteenth response message to the sixth terminal, and the fifteenth response message includes the group identifier and the information of the fourth EAS; the fifteenth response message can be an EAS discovery response message; the EAS discovery response message includes the group identifier and the information of the fourth EAS; the information of the fourth EAS includes the address (EES endpoint) information of the fourth EAS.

[0390] The sixth terminal migrates from the previously connected EAS (e.g., the non-shared fifth EAS) to the fourth EAS based on the fourth EAS information, thereby connecting the sixth terminal and the fifth terminal in the terminal group to the same fourth EAS. The method for connecting other terminals in the terminal group to the fourth EAS can refer to the method for migrating the sixth terminal to the fourth EAS, which will not be repeated here. Finally, multiple terminals in the terminal group are all connected to the same fourth EAS to ensure fairness in accessing services for multiple terminals in the terminal group.

[0391] In method 1000, the sixth terminal connects to the same fourth EAS as the fifth terminal through information of the fifth EES and the fourth EAS shared by the third ECS corresponding to the fifth terminal, so as to achieve fairness in obtaining services for multiple terminals in the terminal group.

[0392] The following further illustrates methods 700 to 1000 with reference to specific application scenarios. It should be noted that the following specific embodiments are merely partial examples of the above methods 700 to 1000 and are only used to further explain the above methods 700 to 1000. They should not be construed as limiting the application scenarios of the above methods 700 to 1000.

[0393] As shown in Figures 11 and 12, respectively, a method 1100 and a method 1200 for determining an edge application server EAS are shown. In methods 1100 and 1200, UE-A (corresponding to the first terminal) represents a terminal in the service area of ​​service provider A (ECSP A), UE-B (corresponding to the second terminal) represents a terminal in the service area of ​​service provider B (ECSP B), ECS-A (corresponding to the first ECS) represents the ECS corresponding to UE-A, and ECS-B (corresponding to the second ECS) represents the ECS corresponding to UE-B; taking the terminal group including UE-A and UE-B as an example, the process steps of method 1100 are shown in (b) of Figure 11, and method 1100 includes:

[0394] Step 1101: As shown in (a) of Figure 11, in Example 1 (case#1) or Example 2 (case#1), shared EAS-1 sends an EAS registration request message to EES-A1. The EAS registration request message carries the PLMN ID or ECSPID information to which the EAS is allowed to access, that is, the EAS can be connected by the UE of the above PLMN or ECSP and obtain the services of the edge application.

[0395] As can be seen from Examples 1 and 2 shown in (a) of Figure 11, UE-B is connected to the shared EAS-1 in the ECSP A service area through the two-level discovery process of EES and EAS, and UE-A is connected to the non-shared EAS-A in the ECSP A service area through the two-level discovery process of EES and EAS.

[0396] As can be seen from Examples 1 and 2, shared EAS-1 and non-shared EAS-A can be registered on the same EES-A1, or they can be registered on different EESs (for example, shared EAS-1 is registered on EES-A1, and non-shared EAS-A is registered on EES-A2).

[0397] Step 1102: EES-A1 sends an EES registration request message to ECS-A. The EES registration request message may carry PLMN information (or ECSP information) supported by EES and EAS, indicating the PLMN (or ECSP) supported by EES and EAS.

[0398] It should be noted that when EAS can be shared by ECSP A and ECSP B, if EES is deployed with ECSP A, the ECSP supported by EES may be ECSP A. In this case, the registration request message needs to carry information about the ECSPs supported by EAS. In another implementation, the ECSP supported by EES may be determined based on the ECSPs supported by EAS. For example, if EES is deployed with ECSP A and EAS can be shared by ECSP A and ECSP B, the ECSPs supported by EES may also be ECSP A and ECSP B.

[0399] It should be noted that in Example 1 (case #1) or Example 2 (case #1), the method of EAS-A registering with EES-A2 and EES-A2 registering with ECS-A is similar to the registration method of shared EAS above, and will not be repeated here.

[0400] Step 1103: UE-A sends a service provisioning request message (for example, the first request message above) to ECS-A through EEC. The service configuration request message may carry a group ID, a PLMN ID list corresponding to the group ID, and / or ECSP ID list information (PLMN ID list / ECSPID list information corresponding to the group ID), which is used to indicate the PLMN information and / or ECSP information corresponding to each terminal in the terminal group.

[0401] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP list information corresponding to the terminal group includes information of two service providers, ECSP A and ECSP B.

[0402] Step 1104: ECS-A determines the PLMN indicated by the list information and / or the EES corresponding to the PLMN, such as EES-A1, based on the PLMN identification list and / or ECSP identification list information corresponding to the terminal group and the PLMN information (or ECSP information) supported by the EES and EAS deployed on ECS-A.

[0403] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP information of the terminal group includes ECSP A and ECSP B. If EES-A1 supports ECSP A and ECSP B, ECS-A can determine that the shared EES of the terminal group is EES-A1 based on the ECSP information.

[0404] In another implementation, the ECSP supported by EES-A1 is ECSP A, and the ECSPs supported by EAS-1 are ECSP A and ECSP B. ECS-A can determine that the EES corresponding to the terminal group is EES-A1 (corresponding to the first EES above) based on the ECSP supported by EES-A1 and the ECSP supported by EAS-1.

[0405] Step 1105: ECS-A sends a service provisioning response message (corresponding to the first response message above) to UE-A; the service response message includes the group identifier and EES information (EES information); the EES information includes EES endpoint information, for example, the service response message includes the group identifier and EES-A1 information.

[0406] Step 1106: UE-A's EEC sends an EAS discovery request message (corresponding to the second request message above) to EES-A1. The EAS discovery request message carries the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, which is used to indicate the PLMN information and / or ECSP information corresponding to the terminal group.

[0407] For example, the terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP information corresponding to the terminal group is ECSP A and ECSP B. The manner in which UE-A obtains the above-mentioned group identifier and PLMN identifier list and / or ECSP identifier list information can be referred to above method 700A and is not further described here.

[0408] Step 1107: EES-A1 determines the EAS (e.g., EAS-1) corresponding to the terminal group (corresponding to the first EAS above) based on the PLMN identification list and / or ECSP identification list information corresponding to the terminal group, as well as the PLMN information and / or ECSP information supported by each EAS registered on EES-A1.

[0409] For example, the terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. If EAS-1 supports ECSP A and ECSP B, EES-A1 can determine that the EAS corresponding to the terminal group is EAS-1.

[0410] Step 1108: EES-A1 sends an EAS discovery response message (corresponding to the second response message above) to UE-A; the EAS discovery response message includes a group identifier and EAS information; the EAS information includes EAS address (EAS endpoint) information, for example, the EAS discovery response message includes a group identifier and address information of EAS-1.

[0411] FIG12 shows another method 1200 for determining an edge application server EAS, the method 1200 comprising the following steps:

[0412] Step 1201: UE-B sends a first service configuration request message (corresponding to the third request message described above) to ECS-B via the EEC. The service configuration request message may carry a PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, indicating the PLMN information and / or ECSP information corresponding to the terminal group. For example, the terminal group includes UE#1 and UE#2. If UE#1 is a user of ECSP A and UE#2 is a user of ECSP B, then the ECSP information corresponding to the terminal group is ECSP A and ECSP B.

[0413] Step 1202: ECS-B sends a second service configuration request message (corresponding to the fourth request message above) to ECS-A. The second service configuration request message may carry a PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, which is used to indicate the PLMN information and / or ECSP information corresponding to the terminal group.

[0414] Step 1203: ECS-A determines the PLMN indicated by the list information and / or the EES corresponding to the PLMN, for example, EES-A1, based on the PLMN identification list corresponding to the terminal group, the ECSP identification list information, the application information, or at least one of the PLMNs supported by the EES and EAS deployed on ECS-A (or ECSP information).

[0415] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. The ECSP information of the terminal group includes ECSP A and ECSP B. If EES-A1 supports ECSP A and ECSP B, ECS-A can determine that the shared EES of the terminal group is EES-A1 based on the ECSP information.

[0416] In another implementation, the ECSP supported by EES-A1 is ECSP A, and the ECSPs supported by EAS-1 are ECSP A and ECSP B. ECS-A can determine that the shared EES corresponding to the terminal group is EES-A1 (corresponding to the first EES above) based on the ECSP supported by EES-A1 and the ECSP supported by EAS-1.

[0417] Step 1204: ECS-A sends a first service configuration response message (corresponding to the fourth response message above) to ECS-B; the first service configuration response message may carry information of EES-A1, such as the address of EES-A1.

[0418] Step 1205: ECS-B determines that the EES corresponding to UE-B is EES-B (corresponding to the second EES mentioned above) in the service area of ​​service provider B.

[0419] Step 1206: ECS-B sends a second service configuration response message (corresponding to the third response message) to UE-B; the second service configuration response message includes: information of EES-B, such as endpoint information of EES-B.

[0420] Step 1207: UE-B sends a first EAS discovery request message to EES-B via the EEC. The first EAS discovery request message may carry a PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, which is used to indicate the PLMN information and / or ECSP information corresponding to the terminal group. For example, the terminal group includes UE#1 and UE#2. If UE#1 is a user of ECSP A and UE#2 is a user of ECSP B, then the ECSPs corresponding to the terminal group are ECSP A and ECSP B.

[0421] Step 1208: EES-B sends a second EAS discovery request message to EES-A1. The first EAS discovery request message may carry the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, which is used to indicate the PLMN information and / or ECSP information corresponding to the terminal group.

[0422] Step 1209: EES-A1 determines EAS-1 (corresponding to the first EAS mentioned above) corresponding to the terminal group based on the PLMN identification list and / or ECSP identification list information, as well as the PLMN information and / or ECSP information supported by each EAS registered on EES-A1.

[0423] For example, a terminal group includes UE#1 and UE#2, where UE#1 is a user of ECSP A and UE#2 is a user of ECSP B. If EAS-1 supports ECSP A and ECSP B, EES-A1 can determine that the shared EAS corresponding to the terminal group is EAS-1.

[0424] Step 1210: EES-A1 sends a first EAS discovery response message (corresponding to the sixth response message above) to EES-B; the EAS discovery response message may carry information of EAS-1, such as the EAS-1 address and other information.

[0425] Step 1211: EES-B sends a second EAS discovery response message (corresponding to the fifth response message above) to UE-B; the second EAS discovery response message includes the group identifier and information of EAS-1.

[0426] Another method 1300 for determining an EAS is described below in conjunction with FIG13 . Taking the example of a terminal group including UE-A and UE-B, where UE-A corresponds to the fourth terminal and UE-B corresponds to the third terminal, the method 1300 includes the following steps:

[0427] It should be noted that when UE-B obtains the information of the shared EAS-1, it can carry the information of the currently connected (serving PLMN); if UE-B needs to connect to the shared EAS, UE-B can request ECS-A to obtain the information of EES-A1 through ECS-B to further obtain the information of the shared EAS-1, or UE-B selects EES-B through ECS-B to obtain the information of the shared EAS-B.

[0428] Step 1301: After UE-B obtains information about the shared EAS-1 (corresponding to the second EAS), UE-B sends a first group binding request message (corresponding to the seventh request message) to EAS-B; the first group binding request includes but is not limited to a group identifier, EAS-1 address information, PLMN information (or ECSP information) corresponding to UE-B, and application information (for example, at least one of an application identifier, an EAS-1 identifier, and an AC identifier of UE-B). The EAS-1 address information is used to indicate PLMN information and / or ECSP information supported by EAS-1, for example, the ECSP information includes ECSP A and ECSP B; for example, the ECSP corresponding to UE-B is ECSP B.

[0429] Step 1302: EES-B sends a second group binding request message (corresponding to the eighth request message) to ECS-ER-B (corresponding to the first ECS-ER); the second group binding request message includes but is not limited to UE-B's ID, group identifier, EAS-1 address information, PLMN information corresponding to UE-B (or ECSP information) and application information (for example, at least one of the application identifier, EAS-1 identifier, UE-B's AC identifier, etc.).

[0430] Step 1303: ECS-ER-B sends query group information (corresponding to the query information described above) to the corresponding ECS-ER-A based on the PLMN and / or ECSP information supported by EAS-1. As described in method 1100 above, EAS-1 is deployed within the service area of ​​service provider A, and EAS-1 corresponds to ECS-ER-A.

[0431] Step 1304: ECS-ER-B sends a third group binding request message (corresponding to the ninth request message above) to ECS-ER-A (corresponding to the second ECS-ER); the third group binding request message includes UE-B's identifier, group identifier, EAS-1 address information, PLMN information (or ECSP information) corresponding to UE-B, and application information (for example, at least one of the application identifier, EAS-1 identifier, UE-B's AC identifier, etc.).

[0432] Optionally, the third group binding request message may be used to instruct ECS-ER-A to migrate UE-A (corresponding to the fourth terminal) from the currently connected EAS-A (corresponding to the third EAS) to EAS-1 (corresponding to the second EAS).

[0433] Step 1305: ECS-ER-A sends a first set of binding response messages (corresponding to the ninth response message) to ECS-ER-B.

[0434] For UE-A, UE-A obtains the information of the non-shared EAS-A through existing technology (for example, the third terminal obtains the relevant description of the second EAS in step 901).

[0435] Step 1306: UE-A sends a fourth group binding request message (corresponding to the tenth request message) to EES-A1 (corresponding to the fourth EES).

[0436] The fourth group binding request message includes: UE-A's ID, group identifier, EAS-A address information, PLMN information or ECSP information corresponding to UE-A, and application information (for example, at least one of the application identifier, UE-A's ACID, or EAS-A identifier), wherein the EAS-A address information is used to indicate the PLMN information or ECSP information supported by EAS-A, for example, the ECSP information includes ECSP A and ECSP B; for example, the ECSP corresponding to UE-A is ECSP A.

[0437] Step 1307: EES-A1 sends a fifth group binding request message (corresponding to the eleventh request message) to ECS-ER-A; the fifth group binding request message includes: UE-A's ID, group identifier, EAS-A address information, PLMN information corresponding to UE-A (or ECSP information), and application information (for example, at least one of the application identifier, UE-A's ACID, or EAS-A identifier).

[0438] Step 1308: ECS-ER-A may determine whether to migrate the user (eg, UE-A) on ECSP A to the shared EAS-1 based on information such as the PLMN (or ECSP) corresponding to UE-A sent by ECS-ER-B.

[0439] Step 1309: ECS-ER-A sends a second set of binding response messages (corresponding to the eleventh response message) to EES-A1; the eleventh response message instructs UE-A to migrate from EAS-A (corresponding to the third EAS) to EAS-1 (corresponding to the second EAS).

[0440] Step 1310: EES-A1 sends a third group binding response message (corresponding to the tenth response message) to UE-A; the third group binding response message includes the group identifier and EAS-1 information, which is used to instruct UE-A to migrate from EAS-A to the second EAS.

[0441] As shown in Figure 14, another method 1400 for determining EAS is shown. Taking the terminal group including UE-A, UE-B and UE-C as an example, the specific process steps of the method 1400 are as follows (see (b) in Figure 14):

[0442] Step 1401: UE-B (corresponding to the fifth terminal above) can obtain information that the shared EAS is EAS-1 (corresponding to the first EAS above) and the shared EES is EES-A1 through method 700 or method 1100, where EES-A1 and EAS-1 are servers deployed in the ECSP A service area.

[0443] It should be noted that in some scenarios, sharing can also be described as common, identical, or the same, etc., and this application does not limit this.

[0444] It should also be noted that, as shown in (a) in Figure 14, in Example 1 (case #1) or Example 2 (case #1), shared EAS-1 sends an EAS registration request message to EES-A1, and EES-A1 sends an EES registration request to ECS-A, completing the registration of EAS-1 and EES-A1.

[0445] As can be seen from Example 1 and Example 2 shown in (a) of FIG14 , UE-B obtains the shared EAS-1 in the ECSP A service area through the EES discovery process and the EAS discovery process.

[0446] As can be seen from Examples 1 and 2, shared EAS-1 and non-shared EAS-A can be registered on the same EES-A1, or on different EESs (for example, shared EAS-1 is registered on EES-A1, and non-shared EAS-A is registered on EES-A2). EES-A1 can be registered on both ECS-A in the ESCP A service area and ECS-C in the ESCP C service area.

[0447] It should be noted that when UE-B sends an EAS discovery request message to EES-A1, the request message includes but is not limited to the group identifier, application information (for example, at least one of the application identifier, the AC identifier corresponding to UE-B, or the identifier of EES-A1), and the PLMN (or ECSP) information corresponding to the terminal group; EES-A1 determines that the common EAS for UE-B is EAS-1 based on the group identifier, application information, and the PLMN (or ECSP) information corresponding to the terminal group. In addition, EES-A1 stores the group identifier, EASID (for example, the common EAS-1 ID), application information, and the determined common EAS-1 information (for example, the address information of EAS-1).

[0448] Step 1402: UE-B sends a first common (or shared) EES information announcement request (corresponding to the twelfth request message) to ECS-B (corresponding to the third ECS), or a first common (or shared) EAS announcement request (corresponding to the twelfth request message); the first common EES announcement request (or the first common EAS announcement request) includes UE-B's ID, group identifier, PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, selected common EES (or common EAS) information and application information (for example, at least one of the application identifier, AC identifier corresponding to UE-B, etc.).

[0449] The selected common EES information includes EESID (e.g., EES-A1 ID), address information of EES (e.g., EES-A1), and PLMN information or ECSP information (e.g., PLMN ID or ECSPID) allowed (or supported) by EES; the selected common EAS information includes EASID (e.g., EAS-1 ID), address information of EAS (e.g., EAS-1), and PLMN information or ECSP information (e.g., PLMN ID or ECSPID) allowed (or supported) by EAS.

[0450] It should be noted that the above-mentioned common EES (or common EAS) may be the EES (or EAS) corresponding to the terminal group, or it may be the EES or EAS corresponding to a terminal in the terminal group (for example, the first EES or EAS corresponding to UE-A in the terminal group); the terminal device (for example, UE-B through servers such as ECS-B) sends the common EES (or common EAS) information to the ECS (for example, ECS-A or ECS-C) corresponding to the terminal group that supports ECSPID and / or PLMN ID.

[0451] Step 1403: ECS-B sends a second common EES announcement request (or a second common EAS announcement request) (corresponding to the thirteenth request message) to ECS-A; the second common EES announcement request (or the second common EAS announcement request) includes the group identifier, the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, the selected common EES (or common EAS) information (for example, the address information of the EES or EAS, etc.) and application information (for example, at least one of the application identifier, the AC identifier corresponding to UE-B, etc.).

[0452] Optionally, the second common EES announcement request (or the second common EAS announcement request) may further include PLMN information or ECSP information (allowed PLMN or ECSP information) corresponding to the common EES (or common EAS).

[0453] For example, ECS-B sends the common EES information (for example, EES-A1) corresponding to the terminal group and the PLMN (or ECSP information) corresponding to the common EES (or common EAS) to the corresponding ECS-A (or ECS-C) in the same group based on the PLMN information (or ECSP information) (corresponding to the fifth service provider information) corresponding to the common EES (or common EAS), or sends the common EAS information (for example, EAS-1) corresponding to the terminal group and the PLMN (or ECSP information) corresponding to the common EAS to the corresponding ECS-A (or ECS-C) in the same group.

[0454] Step 1404: ECS-A (or ECS-C) stores the common EES (or common EAS) information corresponding to the group identifier; for example, ECS-A (or ECS-C) may store the address information of the common EES (or common EAS) and the PLMN (or ECSP) information corresponding to the common EES (or common EAS); optionally, ECS-A (or ECS-C) may also store the common EESID (or common EASID) corresponding to the group identifier and some application information.

[0455] When another terminal device in the terminal group (for example, UE-A or UE-C) needs to obtain edge computing services, the terminal device will perform EES discovery and EAS discovery. The specific steps are as follows:

[0456] Step 1405: UE-A (corresponding to the sixth terminal above) sends a service configuration request message (corresponding to the fourteenth request message) to ECS-A (corresponding to the fourth ECS); the service configuration request message includes: group identifier, PLMN identifier list (ECSP identifier list) information corresponding to the group identifier and application information (for example, application identifier, at least one of the AC identifier corresponding to UE-A, etc.).

[0457] Step 1406: ECS-A (or ECS-C) determines that the common EES corresponding to the terminal group is EES-A1 (or the common EAS is EAS-1) based on the stored group ID and the common EES (or common EAS) information corresponding to the group ID.

[0458] For example, ECS-A (or ECS-C) determines that the common EES corresponding to the terminal group is EES-A1 (or the common EAS is EAS-1) based on the stored address information of the common EES (or common EAS) and the PLMN (or ECSP) information corresponding to the common EES (or common EAS); optionally, based on the common EESID (or common EASID) corresponding to the stored group identifier and some application information.

[0459] Step 1407: ECS-A sends a service configuration response message (corresponding to the fourteenth response message) to UE-A (or UE-C); the service response message includes information of the fifth EES; the information of the fifth EES may include address information of EES-A1 (or address information of EAS-1).

[0460] Step 1408: UE-A (or UE-C) sends an EAS discovery request message (corresponding to the fifteenth request message) to EES-A1 (corresponding to the fifth EES). The EAS discovery request message may include the EAS discovery filter, the group identifier, and the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier.

[0461] Optionally, the EAS discovery request message may further include a group identifier, PLMN information or ECSP information supported by UE-A, and application information (eg, at least one of an application identifier and an AC identifier corresponding to UE-A).

[0462] Step 1409: EES-A1 determines that the common EAS for UE-A is EAS-1 (corresponding to the fourth EAS) based on the group ID in the EAS discovery request message, the PLMN ID list and / or ECSP ID list information corresponding to the group ID, and the EAS discovery filter. At this point, UE-A (or UE-C) and UE-B obtain the same EAS-1.

[0463] Optionally, EES-A1 determines that the common EAS is EAS-1 (corresponding to the fourth EAS) according to the group identifier in the EAS discovery request message, the PLMN identifier list and / or ECSP identifier list information corresponding to the group identifier, and the application information.

[0464] Step 1410: EES-A1 sends an EAS response message (corresponding to the fifteenth response message) to UE-A (or UE-C); the EAS response message includes the group identifier and EAS-1 information (eg, EAS-1 address information).

[0465] For example, the terminal group includes three terminal devices, UE-A, UE-B, and UE-C. UE-A, UE-B, and UE-C can be connected to the same EAS-1 through method 1400, thereby ensuring fairness in service acquisition for each terminal in the terminal group.

[0466] As shown in Figure 15, the present application provides a schematic structural diagram of another communication device 1500. In one possible implementation, the communication device 1500 can be a terminal device (or network device), or can be executed by a module (such as a processor, chip, or chip system) applied to the terminal device (or network device), or can be a logical node, logical module, or software that can implement all or part of the functions of the terminal device (or network device).

[0467] In a possible implementation, the communication device 1500 may be a chip or a chip system, wherein the chip system may be composed of chips, or may include chips and other discrete devices.

[0468] When the communication device 1500 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, integrated circuit, or logic circuit integrated on the chip.

[0469] Optionally, the device in the transceiver unit used to implement the receiving function can be regarded as a receiving unit, which corresponds to the input circuit of the chip; the device in the transceiver unit used to implement the sending function can be regarded as a sending unit, which corresponds to the output circuit of the chip, that is, the transceiver unit includes a receiving unit and a sending unit.

[0470] In one possible implementation, the communication device 1500 may include a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 communicate with each other. It is understood that the interface circuit 1520 may be a transceiver or an input / output interface, wherein the transceiver includes a transmitter and / or a receiver, the transmitter is used to implement a transmission function, and the receiver is used to implement a reception function.

[0471] Optionally, the communication device 1500 may further include a memory 1530, wherein the memory 1530 communicates with the processor 1510 and the interface circuit 1520 via an internal connection path. The memory 1530 is used to store computer programs and instructions, and the processor 1510 can execute the computer programs and instructions stored in the memory 1530.

[0472] In one possible implementation, the communication device 1500 is used to implement the various processes and operations corresponding to the terminal device (or network device) in the above method.

[0473] It should be understood that the communication device 1500 can be specifically a terminal device (or network device) in the above method, or a chip or chip system. Correspondingly, the interface circuit 1520 can be a transceiver circuit of the chip, which is not limited here.

[0474] Specifically, the communication device 1500 can be used to perform the various operations and / or processes corresponding to the terminal device (or network device) in the above-mentioned method embodiments. Optionally, the memory 1530 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.

[0475] For example, the memory may further store device type information. The processor 1510 may be configured to execute instructions stored in the memory, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is configured to execute the various operations and / or processes corresponding to the terminal device (or network device) in the above method.

[0476] During implementation, each operation of the above method can be performed by hardware integrated logic circuits in a processor or by software instructions. The operations of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in the processor.

[0477] The software module can be located in a storage medium known in the art, such as a random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable memory (EEPM), or register. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, performs the operations of the above method. To avoid repetition, a detailed description is omitted here.

[0478] It should be noted that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each operation of the above method embodiment can be completed by an integrated logic circuit of the hardware in the processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The disclosed methods, operations and logic block diagrams in the embodiments of the present application can be implemented or executed.

[0479] A general-purpose processor can be a microprocessor or any conventional processor. The operations of the methods disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules within the decoding processor. The software modules can be located in a storage medium well-established in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, performs the operations of the methods described above.

[0480] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache.

[0481] By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0482] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, it enables the computer to execute the various operations or processes performed by the terminal device (or network device) in the above method.

[0483] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores program code. When the program code runs on a computer, the computer executes the various operations or processes performed by the terminal device (or network device) in the above method.

[0484] According to the method provided in the embodiment of the present application, the present application also provides a communication system, which includes one or more terminal devices and one or more network devices in the aforementioned method.

[0485] In some further embodiments, the present application provides another communication system, which includes at least two communication devices (or communication apparatuses) for executing the aforementioned method; the communication device (or communication apparatus) may include the above-mentioned terminal device and / or network device.

[0486] The above-mentioned various apparatus embodiments correspond completely to the method embodiments, and the corresponding modules or units perform the corresponding operations. For example, the communication unit (transceiver) performs the receiving or sending operations in the method embodiments, and other operations except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be based on the corresponding method embodiments. There can be one or more processors.

[0487] In the embodiments of this application, each term and English abbreviation is provided for convenience of description and shall not constitute any limitation to this application. This application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0488] It should be understood that the term "and / or" as used herein describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the associated objects.

[0489] Those skilled in the art will appreciate that the various illustrative logical blocks and operations described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0490] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can be based on the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0491] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another system, or ignoring or not implementing certain features.

[0492] On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.

[0493] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0494] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0495] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, the functions can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs).

[0496] When the computer program instructions (program) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium.

[0497] For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).

[0498] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the contributing part or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the operations of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0499] The above embodiments are intended only to illustrate the technical solutions of the present application and are not intended to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they may still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein with equivalents; and such modifications or replacements do not deviate from the essence of the corresponding technical solutions within the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for determining an edge application server (EAS), characterized in that: Applied to a first terminal, the method includes: Sending a first request message to a first edge configuration server ECS, where the first request message is used to request obtaining edge enabling server EES information, the first request message including a group identifier and service provider information, where the group identifier is an identifier of a terminal group corresponding to multiple terminals, the terminal group including the first terminal, and the service provider information is used to indicate public land mobile network PLMN information and / or edge computing service provider ECSP information corresponding to the multiple terminals in the terminal group; receiving a first response message from the first ECS, where the first response message includes the group identifier and information about the first EES; Sending a second request message to the first EES, where the second request message is used to request obtaining EAS information, and the second request message includes the group identifier and the service provider information; A second response message of the first EES is received, where the second response message includes the group identifier and information of the first EAS, where the first EAS is the EAS corresponding to the terminal group.

2. The method according to claim 1, characterized in that The first EES is an EES corresponding to multiple terminals in the terminal group.

3. A method for determining an edge application server EAS, characterized in that: Applied to the second terminal, the method includes: Sending a third request message to the second edge configuration server ECS, where the third request message is used to request obtaining edge enabling server EES information, the third request message including a group identifier and service provider information, where the group identifier is an identifier of a terminal group corresponding to multiple terminals, the terminal group including the second terminal, and the service provider information is used to indicate PLMN information and / or ECSP information corresponding to the multiple terminals in the terminal group; A third response message of the second ECS is received, where the third response message includes the group identifier, information of a first EES, and information of a second EES, where the first EES is the EES corresponding to the terminal group, and the second EES is the EES corresponding to the second terminal.

4. The method according to claim 3, characterized in that The method further comprises: Sending a fifth request message to the second EES, where the fifth request message is used to request EAS information, and the fifth request message includes the group identifier, the service provider information, and information of the first EES; A fifth response message of the second EES is received, where the fifth response message includes the group identifier and information of the first EAS, where the first EAS is the EAS corresponding to the terminal group.

5. A method for determining an edge application server EAS, characterized in that: Applied to a first edge configuration server ECS, the method includes: receiving a first request message from a first terminal, where the first request message is used to request obtaining edge enabling server (EES) information, the first request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the first terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the plurality of terminals in the terminal group; Determine a first EES according to the service provider information, where the first EES is the EES corresponding to the terminal group; A first response message is sent to the first terminal, where the first response message includes the group identifier and information about the first EES.

6. The method according to claim 5, characterized in that The method further comprises: receiving a fourth request message from the second ECS, the fourth request message being used to request obtaining EES information, the fourth request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to the plurality of terminals, the terminal group including the second terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the plurality of terminals in the terminal group; Determine a first EES according to the service provider information; A fourth response message is sent to the second ECS, where the fourth response message includes the group identifier and information about the first EES.

7. A method for determining an edge application server EAS, characterized in that: Applied to a first edge enabling server EES, the method includes: receiving a second request message from the first terminal, the second request message being used to request obtaining EAS information, the second request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the first terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the plurality of terminals in the terminal group; determining a first EAS according to the service provider information; A second response message is sent to the first terminal, where the second response message includes the group identifier and information about the first EAS.

8. The method according to claim 7, characterized in that The method further comprises: receiving a sixth request message from the second EES, the sixth request message being used to request obtaining EAS information, the sixth request message including the group identifier and the service provider information; Determining, according to the service provider information, that the first EAS is the EAS corresponding to the multiple terminals in the terminal group; The sixth response message is sent to the second EES, where the sixth response message includes the group identifier and information of the first EAS.

9. A method for determining an edge application server EAS, characterized in that: Applied to the second edge configuration server ECS, the method includes: receiving a third request message from the second terminal, the third request message being used to request obtaining edge enabling server EES information, the third request message including a group identifier and service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the second terminal, and the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the plurality of terminals in the terminal group; A third response message is sent to the second terminal, where the third response message includes the group identifier and information of the first EES, where the first EES is the EES corresponding to the terminal group.

10. The method according to claim 9, characterized in that Before sending the third response message to the second terminal, the method further includes: Sending a fourth request message to the first ECS according to the service provider information, where the fourth request message is used to request obtaining EES information, and the fourth request message includes the group identifier and the service provider information; A fourth response message is received from the first ECS, where the fourth response message includes the group identifier and information of the first EES.

11. The method according to claim 9 or 10, characterized in that The third response message also includes information about the second EES, where the second EES is the EES corresponding to the second terminal.

12. A method for determining an edge application server (EAS), characterized in that: Applied to a second edge enabling server EES, the method includes: receiving a fifth request message from the second terminal, the fifth request message being used to request obtaining EAS information, the fifth request message including a group identifier, service provider information, and information of a first EES, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the second terminal, the service provider information being used to indicate PLMN information and / or ECSP information corresponding to the plurality of terminals in the terminal group, and the first EES being the EES corresponding to the terminal group; A fifth response message is sent to the second terminal, where the fifth response message includes the group identifier and information about the first EAS.

13. The method according to claim 12, characterized in that Before sending the fifth response message to the second terminal, the method further includes: determining, based on the information of the first EES, to send a sixth request message to the first EES, where the sixth request message is used to request obtaining EAS information, and the sixth request message includes the group identifier and the service provider information; A sixth response message is received from the first EES, where the sixth response message includes the group identifier and information of a first EAS, where the first EAS is the EAS corresponding to the terminal group.

14. The method according to any one of claims 1 to 13, characterized in that The PLMN information includes a PLMN identifier, and / or the ECSP information includes an ECSP identifier.

15. A method for determining an edge application server (EAS), characterized in that: Applied to a third terminal, the method includes: Acquire a second EAS, where the second EAS is an EAS corresponding to a terminal group, and the third terminal is one of multiple terminals corresponding to the terminal group; A seventh request message is sent to the third EES, where the seventh request message includes a group identifier, an identifier of the second EAS, and second service provider information. The group identifier is an identifier of the terminal group, the second service provider information is PLMN information or ECSP information supported by the second EAS, and the second EAS is the EAS corresponding to the terminal group.

16. A method for determining an edge application server (EAS), characterized in that: Applied to the third EES, the method comprises: receiving a seventh request message from a third terminal, the seventh request message including a group identifier, an identifier of a second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, and the second EAS being the EAS corresponding to the terminal group; An eighth request message is sent to the first ECS-ER, where the eighth request message includes the group identifier, the identifier of the second EAS, and the second service provider information.

17. A method for determining an edge application server (EAS), characterized in that: Applied to the first ECS-ER, the method comprises: receiving an eighth request message from a third EES, the eighth request message including a group identifier, an identifier of a second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, and the second EAS being the EAS corresponding to the terminal group; Determine, based on the second service provider information, to send query information to the second ECS-ER; Sending a ninth request message to the second ECS-ER, the ninth request message being used to instruct the second ECS-ER to migrate the fourth terminal from the third EAS to the second EAS, the ninth request message including a group identifier, an identifier of the second EAS, and information about the second service provider, the third EAS being a non-shared EAS to which the fourth terminal is currently connected, and the terminal group including the fourth terminal; A ninth response message is received from the second ECS-ER, where the ninth response message includes a group identifier and second service provider information.

18. A method for determining an edge application server (EAS), characterized in that: Applied to the second ECS-ER, the method comprises: receiving query information from the first ECS-ER; receiving a ninth request message from the first ECS-ER, the ninth request message being used to instruct migration of the fourth terminal from the third EAS to the second EAS, the ninth request message including a group identifier, an identifier of the second EAS, and second service provider information, the group identifier being an identifier of a terminal group corresponding to a plurality of terminals, the terminal group including the third terminal, the second service provider information being PLMN information or ECSP information supported by the second EAS, the second EAS being an EAS corresponding to the terminal group, the third EAS being a non-shared EAS to which the fourth terminal is currently connected, and the terminal group including the fourth terminal; A ninth response message is sent to the first ECS-ER, where the ninth response message includes the group identifier and the second service provider information.

19. The method according to claim 18, characterized in that The method further comprises: receiving an eleventh request message from the fourth EES, the eleventh request message including a group identifier, an identifier of the third EAS, and third service provider information, the third service provider information being PLMN information or ECSP information supported by the third EAS; determining, according to the second service provider information, whether to instruct the fourth terminal to migrate from the third EAS to the second EAS; When it is determined to instruct the fourth terminal to migrate from the third EAS to the second EAS, an eleventh response message is sent to the fourth EAS, where the eleventh response message is used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

20. A method for determining an edge application server (EAS), characterized in that: Applied to a fourth terminal, the method includes: Acquire a third EAS, where the third EAS is a non-shared EAS to which the fourth terminal is currently connected, and the fourth terminal is one of the multiple terminals corresponding to the terminal group; A tenth request message is sent to the fourth EES, where the tenth request message includes a group identifier, an identifier of the third EAS, and third service provider information, where the group identifier is an identifier of the terminal group, and the third service provider information is PLMN information or ECSP information supported by the third EAS.

21. A method for determining an edge application server (EAS), characterized in that: Applied to the fourth EES, the method comprises: receiving a tenth request message from the fourth terminal, the tenth request message including a group identifier, an identifier of a third EAS, and third service provider information, wherein the group identifier is an identifier of the terminal group, the third EAS is a non-shared EAS to which the fourth terminal is currently connected, and the third service provider information is PLMN information or ECSP information supported by the third EAS; A tenth response message is sent to the fourth terminal, where the tenth response message is used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

22. The method according to claim 21, characterized in that Before sending the tenth response message to the fourth terminal, the method further includes: Sending an eleventh request message to the second ECS-ER, the eleventh request message including the group identifier, the identifier of the third EAS, and the third service provider information; An eleventh response message is received from the second ECS-ER, where the eleventh response message is used to instruct the fourth terminal to migrate from the third EAS to the second EAS.

23. A communication device, characterized in that: The communication device includes a module for executing the method according to any one of claims 1, 2 and 14, or includes a module for executing the method according to claim 3 or 14, or includes a module for executing the method according to any one of claims 5, 6 and 14, or includes a module for executing the method according to any one of claims 7, 8 and 14, or includes a module for executing the method according to any one of claims 9 to 11 and 14, or includes a module for executing the method according to any one of claims 12 to 14, or includes a module for executing the method according to claim 15, or includes a module for executing the method according to claim 16, or includes a module for executing the method according to claim 17, or includes a module for executing the method according to claim 18 or 19, or includes a module for executing the method according to claim 20, or includes a module for executing the method according to claim 21 or 22.

24. A communication device, characterized in that: The communication device includes: a processor; The processor is configured to execute a computer program or instruction in the memory. When the computer program or instruction is executed by the processor, the communication device implements the method according to any one of claims 1, 2, and 14, or the communication device implements the method according to claim 3 or 14, or the communication device implements the method according to any one of claims 5, 6, and 14, or the communication device implements the method according to any one of claims 7, 8, and 14, or the communication device implements the method according to any one of claims 9 to 11 and 14, or the communication device implements the method according to any one of claims 12 to 14, or the communication device implements the method according to claim 15, or the communication device implements the method according to claim 16, or the communication device implements the method according to claim 17, or the communication device implements the method according to claim 18 or 19, or the communication device implements the method according to claim 20, or the communication device implements the method according to claim 21 or 22.

25. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the processor is caused to perform the method of any one of claims 1, 2 and 14, or the method of claim 3 or 14, or the method of any one of claims 5, 6 and 14, or the method of any one of claims 7, 8 and 14, or the method of any one of claims 9 to 11 and 14, or the method of any one of claims 12 to 14, or the method of claim 15, or the method of claim 16, or the method of claim 17, or the method of claim 18 or 19, or the method of claim 20, or the method of claim 21 or 22.

26. A communication system, characterized in that: including at least two of the following communication devices: A communication device for executing the method according to claim 1 or 2; A communication device for executing the method according to claim 3 or 4; A communication device for executing the method according to claim 5 or 6; A communication device for executing the method according to claim 7 or 8; A communication device for performing the method according to any one of claims 9 to 11; A communication device for performing the method according to any one of claims 12 to 14; A communication device for performing the method of claim 15; A communication device for performing the method of claim 16; A communication device for performing the method of claim 17; A communication device for performing the method of claim 18 or 19; A communication device for performing the method of claim 20; A communication device for executing the method of claim 21 or 22.

Images