A communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and device, which are used to solve the problem that application context cannot be migrated between two edge data network centers. The method comprises: an edge configuration server (ECS) receiving a first request message, the first request message being used to discover an edge enable server (EES), and the request message indicating a communication requirement for a target EES; the ECS determining at least one EES satisfying the communication requirement; and the ECS sending a response message, the response message carrying information of the at least one EES. In the embodiments of the present application, the communication requirement for the target EES is indicated in the request message used to discover the EES, so that when the application context is switched, a target EES which has no communication connection with a source EES, or the communication connection type or the communication connection quality of which cannot satisfy the communication requirement of the application context migration, can be avoided, thereby guaranteeing the service continuity of the application.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of communication, and in particular, to a communication method and device. BACKGROUND

[0002] With the large deployment of various cloud computing resources in the network, the same application is often deployed in multiple edge data networks at the same time. The servers of the same application deployed in different edge data networks can provide the same service and have functional equivalence. After accessing the network, the terminal device selects an application instance in the nearest edge data network to perform the service. Due to the mobility of the terminal device, the application instance previously selected by the terminal device may not be able to continue to provide the service for the terminal device well. In order to adapt to the service continuity requirement of the application, the network reselects a new application instance in the nearest edge data network for the terminal device to continue the service. The switching from the source application instance to the target application instance is completed.

[0003] When the data service of the terminal device is switched from the source application instance to the target application instance, since the source application instance and the target application instance belong to different edge data networks, there may be isolation / firewall between the two edge data networks and they cannot communicate with each other, resulting in that the application context cannot be migrated between the two edge data networks. SUMMARY

[0004] Embodiments of the present application provide a communication method and device, which are used to solve the problem that the application context cannot be migrated between two edge data networks.

[0005] In a first aspect, a communication method is provided, which can be applied to an edge configuration server (ECS), and the method comprises the following steps: the ECS receives a first request message, the first request message is used to discover an edge enabler server (EES), and the request message indicates a communication requirement for a target EES; the ECS determines at least one EES that meets the communication requirement; and the ECS sends a response message, and the response message carries information of the at least one EES. In the embodiments of the present application, the communication requirement for the target EES is indicated in the request message used to discover the EES, so that when the application context is switched, a target EES that has no communication connection with the source EES, or the communication connection type or the communication connection quality of which cannot meet the communication requirement of the application context migration can be avoided, thereby the service continuity of the application can be ensured.

[0006] In a possible design, the ECS receives configuration information of the first EES, including the source EES and / or the target EES, before receiving the first request message, where the configuration information of the first EES includes information of a second EES that supports communication with the first EES. With the above design, the ECS can obtain the topological connection relationship of the EES, so that when performing application context switching, the target EES that has a communication connection with the source EES can be selected, thereby guaranteeing service continuity of the application.

[0007] In a possible design, the first EES includes one or more EESs.

[0008] In a possible design, the configuration information of the first EES further includes information of a communication connection between the first EES and a second EES. With the above design, the ECS can obtain the topological connection relationship of the EES and the information of the communication connection, so that when performing application context switching, the target EES that meets the communication requirement of the application context migration in terms of the type or quality of the communication connection can be selected, thereby guaranteeing service continuity of the application.

[0009] In a possible design, the ECS sends a second request message to a policy control function (PCF) or a session management function (SMF) network element, where the second request message is used to request establishment of a user plane function (UPF) tunnel between a UPF network element connected to the source EES and a UPF network element connected to the target EES. With the above design, the source EES and the target EES can communicate, thereby realizing migration of the application context.

[0010] In a possible design, the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, a type of the communication connection between the source EES and the target EES, and a quality parameter of the communication connection between the source EES and the target EES. With the above design, the ECS can discover the target EES that meets the communication quality.

[0011] In a possible design, the first request message carries information of the source EES. With the above design, the ECS can determine the source EES, thereby discovering the target EES that has a communication connection with the source EES.

[0012] In a possible design, the first request information carries indication information, where the indication information is used to indicate that the target EES is used for application context migration. Through the above design, the process of discovering the EES can be associated with the application context migration.

[0013] In a second aspect, a communication method is provided, which can be applied to a terminal device, and the method includes the following steps: the terminal device sends a first request message to an ECS, where the first request message is used to discover an EES, and the first request message indicates a communication requirement for a target EES; and the terminal device receives a response message from the ECS, where the response message carries information of at least one EES that meets the communication requirement. In embodiments of this application, by indicating the communication requirement for the target EES in the request message used to discover the EES, when the application context is switched, a target EES that has no communication connection with a source EES, or a target EES whose communication connection type or communication connection quality cannot meet the communication requirement of the application context migration, can be avoided, thereby ensuring the service continuity of the application.

[0014] In a possible design, the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, a type of communication connection between the source EES and the target EES, and a quality parameter of the communication connection between the source EES and the target EES. Through the above design, the ECS can discover the target EES that meets the communication quality.

[0015] In a possible design, the first request message carries information of the source EES. Through the above design, the ECS can determine the source EES, and thus can discover the target EES that has a communication connection with the source EES.

[0016] In a possible design, the first request information carries indication information, where the indication information is used to indicate that the target EES is used for application context migration. Through the above design, the process of discovering the EES can be associated with the application context migration.

[0017] In a third aspect, a communication method is provided, which can be applied to an edge application server (EAS), and the method comprises the following steps: a first EAS sends a first request message to a first EES, the first request message is used to discover a target EAS for application context migration of the first EAS, and the first request message indicates a communication requirement for migrating the application context. The first EAS acquires a response message of the first request message from the first EES, and the response message comprises information of an EAS satisfying the communication requirement. In the embodiment of the application, the first EAS sends the communication requirement for migrating the application context to the first EES, so that the first EES can indicate the communication requirement for the target EES in the request message for discovering the EES, and thus when the application context is switched, a target EES without a communication connection with the source EES, or a target EES with a communication connection type or a communication connection quality that cannot satisfy the communication requirement for migrating the application context can be avoided, and thus the service continuity of the application can be ensured.

[0018] In a possible design, the communication requirement comprises a quality parameter of a communication connection for migrating the application context and / or a type of the communication connection for migrating the application context. Through the above design, the source EES can select a target EES satisfying the communication quality requirement.

[0019] In a fourth aspect, a communication method is provided, which can be applied to an EES, and the method comprises the following steps: a first edge enabler server (EES) sends a first request message to an edge configuration server (ECS), the first request message is used to discover an EES, and the first request message indicates a first communication requirement for a target EES; and the first EES receives a response message from the ECS, and the response message carries information of at least one EES satisfying the first communication requirement. In the embodiment of the application, the communication requirement for the target EES is indicated in the request message for discovering the EES, so that when the application context is switched, a target EES without a communication connection with the source EES, or a target EES with a communication connection type or a communication connection quality that cannot satisfy the communication requirement for migrating the application context can be avoided, and thus the service continuity of the application can be ensured.

[0020] In a possible design, the first EES receives a second communication requirement from a first edge application server (EAS), and the second communication requirement is used to indicate a communication requirement of the EAS for migrating the application context. Through the above design, the source EES can acquire the communication requirement for migrating the application context.

[0021] In one possible design, the second communication requirement includes quality parameters of the communication connection for migrating the application context and / or the type of communication connection for migrating the application context. This design allows the source EES to obtain the communication quality requirements for the application context migration.

[0022] In one possible design, the second communication requirement also includes at least one of the following: the target EES supports communication with the first EES, the type of communication connection between the first EES and the target EES, and the quality parameters of the communication connection between the first EES and the target EES. This design allows the ECS to discover target EES that meet the required communication quality.

[0023] In one possible design, the first request message carries information about the first EES. This design allows the ECS to identify the source EES, thereby enabling it to discover target EES that have a communication connection with the source EES.

[0024] In one possible design, the first request information carries indication information, which instructs the target EES to be used for application uplink migration. This design links the process of discovering an EES with application context migration.

[0025] Fifthly, a communication method is provided, which can be applied to an Application Executor System (EES). The method includes the following steps: a target EES receives a first request message from a terminal device, the first request message requesting the target EES to discover a target Application Executor System (EAS) for migrating the application context of the terminal device, and the request message contains a communication requirement for application context migration; when the target EES determines that an EAS meeting the requirement exists, the target EES sends a response message to the terminal device, the response message carrying information about the required EAS. In this embodiment, the target EES can determine whether a communication connection meeting the communication requirement exists with the source EES based on the communication requirement, thereby avoiding selecting a target EES that has no communication connection with the source EES, or whose communication connection type or quality cannot meet the communication requirements for application context migration, thus ensuring application service continuity.

[0026] In one possible design, the target EES sends a second request message to a PCF or SMF network element. This second request message requests the establishment of a UPF tunnel between the user plane function UPF network element connected to the source EES and the UPF network element connected to the target EES. This design enables communication between the source and target EES, thereby facilitating application context migration.

[0027] In one possible design, the communication requirements include: the target EES supporting communication with the source EES, the type of communication connection for the application context migration, and the quality parameters of the communication connection for the application context migration. This design allows the ECS to discover target EES that meet the required communication quality.

[0028] Sixthly, a communication method is provided, which can be applied to a terminal device. The method includes the following steps: the terminal device sends a first request message to a target EES, the request message requesting the target EES to discover a target Edge Application Server (EAS) for migrating the application context of the terminal device, and the request message includes a communication requirement for application context migration; the terminal device receives a response message from the target EES, the response message containing information about an EAS that meets the requirement. In this embodiment, the target EES can determine whether it has a communication connection with the source EES that meets the communication requirement based on the communication requirement, thereby avoiding the selection of a target EES that does not have a communication connection with the source EES, or whose communication connection type or quality cannot meet the communication requirements for application context migration, thus ensuring application service continuity.

[0029] In one possible design, the communication requirements include: the target EES supporting communication with the source EES, the type of communication connection for the application context migration, and the quality parameters of the communication connection for the application context migration. This design allows the ECS to discover target EES that meet the required communication quality.

[0030] In a seventh aspect, a communication method is provided, which can be applied to an ECS. The method includes the following steps: the ECS receives a request message for discovering an External Executable System (EES); the ECS sends a response message carrying information about a first EES, wherein the information about the first EES includes information about a second EES that supports communication with the first EES. In this embodiment, by sending EES topology connection information to the terminal device, the ECS can avoid selecting a target EES that has no communication connection with the source EES, or whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0031] In one possible design, the first EES includes one or more EES.

[0032] In one possible design, the second EES includes one or more EES.

[0033] In one possible design, the information of the first EES also includes information about the communication connection between the first EES and the second EES. This design avoids selecting a target EES whose communication connection cannot meet the communication requirements of application context migration, thus ensuring application business continuity.

[0034] In one possible design, the communication connection information includes at least one of the following: the type of communication connection between the first EES and the second EES, and the quality parameters of the communication connection between the first EES and the second EES. This design avoids selecting a target EES whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0035] Eighthly, a communication method is provided, which can be applied to a terminal device. The method includes the following steps: the terminal device sends a first request message to an ECS (Elastic Compute Service), the first request message being used to obtain an Edge Enabler Server (EES); the terminal device receives a response message from the ECS, the response message carrying information about a first EES, wherein the information about the first EES includes information about a second EES that supports communication with the first EES. In this embodiment, by sending EES topology connection information to the terminal device, the ECS can prevent the terminal device from selecting a target EES that has no communication connection with the source EES, or whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0036] In one possible design, the first EES includes one or more EES.

[0037] In one possible design, the second EES includes one or more EES.

[0038] In one possible design, the information of the first EES also includes information about the communication connection between the first EES and the second EES. This design avoids selecting a target EES whose communication connection cannot meet the communication requirements of application context migration, thus ensuring application business continuity.

[0039] In one possible design, the communication connection information includes at least one of the following: the type of communication connection between the first EES and the second EES, and the quality parameters of the communication connection between the first EES and the second EES. This design avoids selecting a target EES whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0040] In one possible design, the terminal device determines a target EES based on the information with the first EES, wherein the target EES satisfies the communication requirements for application context migration.

[0041] In one possible design, the communication requirements include at least one of the following: the target EES supports communication with the source EES, the type of communication connection for application context migration, and the quality parameters of the communication connection for application context migration. This design avoids selecting a target EES whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0042] Ninthly, a communication method is provided, which can be applied to SMF network elements. The method includes the following steps: the core network device detects a first event, the first event being used by the core network device to select a new Data Network Access Identifier (DNAI); the core network device determines a target DNAI, and the target edge enable server (EES) corresponding to the target DNAI supports communication with the source EES. In this embodiment, the network side selects the DNAI corresponding to the EES that has a communication connection with the source EES when selecting the DNAI, thereby ensuring that the EES corresponding to the target DNAI has a communication connection with the source EES. This avoids selecting a target EES that does not have a communication connection with the source EES, or whose communication connection type or quality cannot meet the application context migration requirements, thus ensuring the service continuity of the application.

[0043] In one possible design, the core network device receives a request message from an application function (AF) network element. This request message is used to obtain information about the target DNAI and includes a communication requirement for the target DNAI. The first core network device then sends a response message to the AF network element, which includes the target DNAI. Through this design, the core network device can obtain the communication requirement for the target DNAI.

[0044] In one possible design, the communication requirements for the target DNAI include at least one of the following: the target EES corresponding to the target DNAI supports communication with the source EES; the type of communication connection between the source EES and the target EES; and the quality parameters of the communication connection between the source EES and the target EES. This design avoids selecting a target DNAI whose communication connection type or quality cannot meet the communication requirements of application context migration, thereby ensuring application service continuity.

[0045] In one possible design, before the core network device determines the DNAI, the first core network device acquires information about the source EES and the target EES. Through this design, the core network device can obtain the topology connection information of the EES, thereby selecting a target DNAI that meets communication requirements.

[0046] A tenth aspect provides a communication method applicable to an SMF (Service Context Provider). The method includes the following steps: a first core network device receives a first message from an Application Function (AF) network element, the first message requesting the establishment of a UPF tunnel between a first User Plane Function (UPF) network element connected to a source EES and a second UPF network element connected to a target EES. The request message carries target routing information used to determine the second UPF. The first core network device obtains tunnel information of the second UPF network element based on the target routing information. The first core network device sends a forwarding rule to the first UPF network element, the forwarding rule instructing the first UPF network element to forward data from the source EES to the second UPF network element, the forwarding rule carrying the tunnel information of the second UPF network element. Through this embodiment, a communication connection can be established between a source EES and a target EES, thereby enabling application context migration.

[0047] In one possible design, the AF element can be the source EES, the target EES, or the ECS.

[0048] In one possible design, the target routing information includes the target DNAI and / or target N6 routing information.

[0049] In one possible design, the first core network device obtains the tunnel information of the second UPF network element based on the target routing information, including: if the target routing information is within the service range of the first core network device, then the first core network device determines the tunnel information of the second UPF based on the target routing information. Through this design, the SMF network element can obtain the tunnel information of the second UPF network element locally.

[0050] In one possible design, the first core network device sends the aforementioned forwarding rule to the second UPF. The forwarding rule is also used to instruct the second UPF to forward data from the first UPF network element to the target EES. The forwarding rule also carries the tunnel information of the first UPF.

[0051] In one possible design, the first core network device obtains the tunnel information of the second UPF network element based on the target routing information, including: if the target routing information is not within the service range of the first core network device, the first core network device determines the second core network device based on the target routing information; the first core network device sends a second message to the second core network device, the second message being used to request the establishment of a UPF tunnel between the first UPF and the second UPF, the second message carrying the target routing information and the tunnel information of the first UPF network element; the first core network device receives a third message sent by the second core network device, the third message carrying the address information of the second UPF. Through the above design, the SMF can obtain the second UPF within the service range of other SMFs.

[0052] Eleventhly, this application provides a communication device, which may be a communication equipment or a chip or chipset within a communication equipment. The communication equipment may be an ECS, a terminal device, an EAS, an EES, or a core network device such as an SMF network element. The device may include a processing unit and a transceiver unit. When the device is a communication equipment, the processing unit may be a processor, and the transceiver unit may be a transceiver. The device may also include a storage module, which may be a memory. The storage module stores instructions, and the processing unit executes the instructions stored in the storage module to cause the ECS to perform the corresponding functions of the first or seventh aspect described above; or, the processing unit executes the instructions stored in the storage module to cause the terminal device to perform the corresponding functions of the second, sixth, or eighth aspect described above; or, the processing unit executes the instructions stored in the storage module to cause the EAS to perform the corresponding functions of the third aspect described above; or, the processing unit executes the instructions stored in the storage module to cause the EES to perform the corresponding functions of the fourth or fifth aspect described above; or, the processing unit executes the instructions stored in the storage module to cause the core network device to perform the corresponding functions of the ninth or tenth aspect described above. When the device is a chip or chipset within a communication device, the processing unit can be a processor, and the transceiver unit can be an input / output interface, pins, or circuits, etc. The processing unit executes instructions stored in the storage module to cause the ECS to perform the corresponding functions of the first or seventh aspect described above; or, the processing unit executes instructions stored in the storage module to cause the terminal device to perform the corresponding functions of the second, sixth, or eighth aspect described above; or, the processing unit executes instructions stored in the storage module to cause the EAS to perform the corresponding functions of the third aspect described above; or, the processing unit executes instructions stored in the storage module to cause the EES to perform the corresponding functions of the fourth or fifth aspect described above; or, the processing unit executes instructions stored in the storage module to cause the core network equipment to perform the corresponding functions of the ninth or tenth aspect described above. The storage module can be a storage module within the chip or chipset (e.g., registers, caches, etc.), or it can be a storage module located outside the chip or chipset within the base station (e.g., read-only memory, random access memory, etc.).

[0053] Eleventhly, embodiments of this application provide a communication device, which includes a communication interface and a processor. The communication interface is used for communication between the device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other devices may be network devices. The processor is used to invoke a set of programs, instructions, or data to execute the methods described in the first aspect or various possible designs of the first aspect, or the methods described in the seventh aspect or various possible designs of the seventh aspect. The device may further include a memory for storing programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the methods described in the first aspect or various possible designs of the first aspect, or the methods described in the seventh aspect or various possible designs of the seventh aspect.

[0054] In a twelfth aspect, embodiments of this application provide a communication device including a communication interface and a processor. The communication interface is used for communication between the device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other devices may be terminal devices. The processor is used to invoke a set of programs, instructions, or data to execute the methods described in the second aspect or various possible design descriptions of the second aspect, the sixth aspect or various possible design descriptions of the sixth aspect, and the eighth aspect or various possible design descriptions of the eighth aspect. The device may further include a memory for storing programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the methods described in the second aspect or various possible design descriptions of the second aspect, the sixth aspect or various possible design descriptions of the sixth aspect, and the eighth aspect or various possible design descriptions of the eighth aspect.

[0055] In a thirteenth aspect, embodiments of this application provide a communication device including a communication interface and a processor. The communication interface is used for communication between the device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other devices may be terminal devices. The processor is used to invoke a set of programs, instructions, or data to execute the methods described in the third aspect or various possible designs of the third aspect. The device may further include a memory for storing programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the methods described in the third aspect or various possible designs of the third aspect.

[0056] In a fourteenth aspect, embodiments of this application provide a communication device including a communication interface and a processor. The communication interface is used for communication between the device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other devices may be terminal devices. The processor is used to invoke a set of programs, instructions, or data to execute the methods described in the fourth aspect or various possible designs of the fourth aspect, or the fifth aspect or various possible designs of the fifth aspect. The device may further include a memory for storing the programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the methods described in the fourth aspect or various possible designs of the fourth aspect, or the fifth aspect or various possible designs of the fifth aspect.

[0057] In a fifteenth aspect, embodiments of this application provide a communication device including a communication interface and a processor. The communication interface is used for communication between the device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other devices may be terminal devices. The processor is used to invoke a set of programs, instructions, or data to execute the methods described in the ninth aspect or various possible designs of the ninth aspect, or the tenth aspect or various possible designs of the tenth aspect. The device may further include a memory for storing the programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the methods described in the ninth aspect or various possible designs of the ninth aspect, or the tenth aspect or various possible designs of the tenth aspect.

[0058] In a sixteenth aspect, embodiments of this application also provide a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the method described in any one of the first to tenth aspects, and in each of the possible designs of the first to tenth aspects, to be performed.

[0059] In a seventeenth aspect, embodiments of this application provide a chip system including a processor and potentially a memory, for implementing the methods described in any one of the first to tenth aspects, and in each possible design of any one of the first to tenth aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0060] Eighteenth aspect: A computer program product containing instructions is provided that, when run on a computer, causes the method described in any of the first to tenth aspects above, and in each of the possible designs of the first to tenth aspects, to be executed.

[0061] The technical effects of any of the implementation methods in aspects eleven through eighteen can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0062] Figure 1 A schematic diagram of an MEC network architecture provided for an embodiment of this application;

[0063] Figure 2 A schematic diagram of the architecture of a communication network provided in an embodiment of this application;

[0064] Figure 3 A schematic diagram illustrating a migration application context provided in an embodiment of this application;

[0065] Figure 4 A schematic diagram illustrating an enhanced EES registration process and an EES discovery process provided for embodiments of this application;

[0066] Figure 5 A schematic diagram illustrating the establishment of a UPF tunnel, provided as an embodiment of this application;

[0067] Figure 6 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0068] Figure 7 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0069] Figure 8 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0070] Figure 9 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0071] Figure 10 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0072] Figure 11 A schematic diagram illustrating an application context migration process provided in an embodiment of this application;

[0073] Figure 12 A schematic diagram illustrating the process of establishing a UPF tunnel, provided for an embodiment of this application;

[0074] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0075] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0076] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0077] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0078] Reference Figure 1 In the SA6 multi-access edge computing (MEC) research of the 3rd generation partnership project (3GPP), the following architecture model was defined:

[0079] Edge data network (EDN) can be understood in two ways. First, an EDN corresponds to only one data network; it's a special local data network (DN) containing edge-enabled functions and can be identified using a Data Network Access Identifier (DN accEES Identifier, DNAI) and a Data Network Name (DNN). It's a logical network concept. Second, an EDN is a peer-to-peer concept of a central cloud, which can be understood as a local data center (geographical concept). It can be identified using DNAI and can contain multiple local data networks (localDNs). Taking the "App Store" application on Huawei phones as an example, a central cloud for the "App Store" can be set up at the Shenzhen headquarters. To facilitate use by users in Beijing and Shanghai, separate local EDN networks for the "App Store" can be set up in Beijing and Shanghai respectively. Subsequently, users in Beijing can access application services through the local EDN network set up in Beijing, while users in Shanghai can access application services through the local EDN network set up in Shanghai. Each EDN network provides application services to users based on proximity, offering a higher quality network experience.

[0080] An application instance, or edge application, refers to an application deployed within an EDN. Specifically, it refers to a server application, such as social media software, augmented reality (AR), or virtual reality (VR) applications, deployed and running as an instance within an EDN. An application can deploy one or more edge application servers (EAS) across one or more EDNs. EAS deployed and running in different EDNs can be considered different EASs of the same application; they can share a domain name, use a single anycast IP address, or use different IP addresses, etc., without limitation. EAS is also known as an application instance, edge application instance, MEC application server, or EAS functionality.

[0081] An application client (AC) is a peer entity of EAS on the terminal device side. ACs are used by application users to obtain application services from EAS. An AC is a client program on the terminal side; it can connect to EAS in the central cloud to obtain application services, or it can connect to EAS deployed and running in one or more EDNs to obtain application services.

[0082] Edge enabler servers (EES) provide enabling capabilities for instances deployed in EDN, better supporting application deployments in MEC. For example, EES can support edge application registration, authentication and authorization of terminal devices, and provide application instance IP address information to terminal devices. Furthermore, EES can also retrieve application instance identifiers and IP address information and send them to ECS. EES is deployed within the EDN. Generally, an EAS is registered to an EES, or an EAS's information is configured on an EES through a management system. This EES is called the EES associated with that EAS, and it can control, manage, register, or configure the EAS associated with it.

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

[0084] The edge configuration server (ECS) is responsible for EDN configuration, such as providing EES information to end devices. It can also provide application instance information to end devices, and interact with application DNS to obtain application instance information. Furthermore, it can obtain and store application instance and IP address information from other functional entities.

[0085] For example, the EEC can obtain the ECS address through any of the following five methods:

[0086] 1) The ECS address can be pre-configured in the EEC;

[0087] 2) The AC can configure the ECS address to the EEC;

[0088] 3) The user specifies an ECS on the terminal device, that is, the user selects an ECS from the ECS list by operating the terminal device, and the terminal device can indicate the ECS to the EEC;

[0089] 4) The EEC can determine the ECS address based on the public land mobile network (PLMN) ID;

[0090] 5) The 5G core network (5G core, 5GC) configures the ECS address to the UE, and the UE can send the ECS address received through 5GC to the EEC.

[0091] like Figure 2 As shown, the network architecture defined in 3GPP standard TS 23.501 includes: a radio access network (RAN) and a core network. Different access network devices can be connected via the Xn interface, and access network devices and the core network can be connected via the NG interface.

[0092] The RAN (Radio Access Network) is used to implement functions related to radio access, such as providing radio resource management, quality of service management, data encryption, and compression for terminal equipment. For example, access network equipment can include the following types:

[0093] 1. Next-generation node (gNB) provides terminal devices with control plane and / or user plane protocols and functions for new radio (NR) and connects to the core network. For example, the 5G core network (5G GC).

[0094] 2. Next-generation evolved Node B (ng-eNB) provides terminal equipment with control plane and / or user plane protocols and functions of evolved universal terrestrial radio accEES (E-UTRA) and connects to the core network. For example, 5GC.

[0095] Optionally, the access network equipment can consist of centralized units (CUs) and distributed units (DUs). This allows for the functional splitting of the original access network equipment, deploying some functions in the CU and the remaining functions in the DU. Multiple DUs can share a single CU, saving costs and facilitating network expansion. CUs and DUs can be connected via a FI interface. A CU can represent the access network equipment connected to the core network via an NG interface, and it can also represent the access network equipment connected to other access network equipment via an Xn interface. Furthermore, the functions of the CU can be further divided into:

[0096] 1. Central unit-control plane (CU-CP): This mainly includes the RRC layer in the CU and the control plane in the PDCP layer;

[0097] 2. Central unit–user plane (CU-UP): This mainly includes the SDAP layer in the CU and the user plane in the PDCP layer.

[0098] The core network is primarily used to manage terminal devices and provide communication capabilities with the external network. Core network equipment may include one or more of the following network elements:

[0099] User plane function (UPF) network elements are primarily responsible for forwarding and receiving user data. In downlink transmission, the UPF network element receives user data from the data network (DN) and transmits it to the terminal device via the access network equipment. In uplink transmission, the UPF network element receives user data from the terminal device via the access network equipment and forwards the user data to the DN. Optionally, the transmission resources and scheduling functions provided to the terminal device within the UPF network element can be managed and controlled by the SMF network element.

[0100] Access and Mobility Management Function (ACCEES) network element: mainly responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0101] Session Management Function (SMF) network elements are primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0102] Policy control function (PCF) network element: It mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.

[0103] Application function (AF) network elements: These mainly support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0104] Unified data management (UDM) network elements are mainly used for generating authentication credentials, processing user identifiers (such as storing and managing permanent user identities), controlling access authorization, and managing subscription data.

[0105] It should be noted that the network elements in the core network described above may have different names in different communication systems. Figure 2 The schematic diagram shown is illustrated using a fifth-generation mobile communication system as an example and is not intended to limit this application.

[0106] Optional, Figure 2 The network architecture shown may also include: terminal devices. A terminal device, often simply referred to as a terminal, is a device with wireless transceiver capabilities. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as on ships); and they can be deployed in the air (such as on airplanes, balloons, and satellites). These terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in autonomous driving, wireless terminal devices in telemedicine, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes, etc. Terminal equipment can also be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal equipment in future fifth-generation (5G) networks, or terminal equipment in future evolved public land mobile networks (PLMNs), etc. Terminal equipment may also be referred to as user equipment (UE), access terminal equipment, in-vehicle terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, wireless communication equipment, UE agent, or UE device, etc. Terminal equipment can be fixed or mobile. This application embodiment does not limit this.

[0107] Optional, Figure 2The network architecture shown may also include a data network (DN). A DN can be a network that provides data transmission services to users. For example, a DN can be an IP multi-media service network or an internetwork. A DN may include multiple application servers. Terminal devices can establish Protocol Data Unit (PDU) sessions from the terminal device to the DN to access it. A data network may have one or more local data networks (Local DNs), which are data network access points (accEES points) located near the user's point of attachment.

[0108] In the embodiments of this application, the above Figure 1 The ECS, EES, and EAS in the illustrated architecture can be configured in one or more of the aforementioned DNs. Alternatively, it can be described as follows: the aforementioned DNs include one or more EDNs, each EDN including EES and EAS, and may also contain ECS. In addition, an application center cloud platform can also be configured in the aforementioned DNs. The application center cloud platform and the aforementioned EAS can be considered equivalent concepts. Each EAS can provide application services to users locally, while the application center cloud platform can provide application services to all users. The application center cloud platform can also be called a central cloud platform. In the following description, the central cloud platform is used as an example. Taking the "Huawei Music" client as an example, the relationship between the EDN network and the central cloud platform is illustrated: A central cloud platform for "Huawei Music" can be set up at the Shenzhen headquarters, which can provide services to "Huawei Music" clients for users worldwide. Simultaneously, to facilitate the provision of music services to users in Beijing and Shanghai, Huawei Music EAS can be deployed in the EDN networks of Beijing and Shanghai respectively. Subsequently, users in Beijing can access the Huawei Music EAS in the corresponding EDN network in Beijing to obtain Huawei Music services. Users in Shanghai can access Huawei Music's EAS within the corresponding EDN network in Shanghai to obtain Huawei Music services. Furthermore, if the EDN network in Beijing or Shanghai fails, or if the corresponding Huawei Music EAS experiences problems such as overload, or is unable to provide certain services, users in Beijing or Shanghai can access Huawei Music's central cloud platform located in Shenzhen to obtain the corresponding music services.

[0109] With the widespread deployment of various cloud computing resources within networks, the same application is often deployed simultaneously across multiple EDNs. Servers of the same application deployed in different EDNs can provide the same services and are functionally equivalent. After connecting to the network, terminal devices select the nearest EAS in the EDN to execute services. Due to the mobility of terminal devices, the EAS previously selected by the terminal device may not be able to provide services effectively. To meet the service continuity requirements of applications, the network selects a new, nearby EAS for the terminal device to continue providing services.

[0110] When the data service of a terminal device switches from the source EAS to the target EAS, the connection of the terminal device will be interrupted because the source EAS and the target EAS belong to different EDNs. In order to maintain service continuity, the application context in the source EAS can be migrated to the target EAS. This process is called application migration or application context migration.

[0111] The source EAS and target EAS may belong to different EDNs, and there may be isolation or firewalls between the two EDNs preventing them from communicating. Therefore, the application context in the source EAS may not be able to be migrated to the target EAS. For example, Figure 3 As shown, as the UE moves, it switches from EDN#1 to EDN#2. Because EDN#1 and EDN#2 cannot communicate, the UE's application context cannot be migrated to EDN#2.

[0112] Based on this, embodiments of this application provide a communication method and apparatus. By selecting an EAS that can communicate with the source EAS as the target EAS for application context migration, the success rate of application context migration can be improved. The method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve problems are similar, the implementations of the apparatus and method can refer to each other, and repeated details will not be elaborated further.

[0113] In this embodiment, the EES registration and selection process can be enhanced to allow the ECS to obtain the topology connection relationship of the EES, or the topology connection relationship of the EES can be configured in the ECS through the edge management system (used to manage the resources of the edge data network and manage the EES). This allows the EES to determine other EES connected to the source EES, and thus can provide feedback on the target EES that has a communication connection with the source EES during the application context migration process. For details, please refer to Embodiments 1 to 3 of this application.

[0114] The enhanced EES registration process may include: enhancing the configuration information of the EES, that is, including the topology connection information of the EES in the configuration information of the EES. The topology connection information can indicate the information of other EES that have communication connections with the EES. For details, please refer to Embodiments 1 to 3 of this application.

[0115] Enhancing the EES selection process can include indicating latency or path requirements for the migration when an application migration is triggered.

[0116] For example, for application context relocation (ACR) triggered by the terminal device side, the service provisioning request, application context relocation request, or full application context relocation request can be enhanced so that the service provisioning request, ACR request, or full ACR request can indicate the communication requirements for the target EES. See Embodiment 1 of this application for details.

[0117] For example, for an ACR initiated by the EAS side, the EAS discovery request from the EAS can also indicate the communication requirement for the target EES. See Embodiment 2 of this application for details.

[0118] For example, in an ACR initiated by the EES side, the message requesting the EES to discover the target EES can also indicate the communication requirement for the target EES. See Embodiment 3 of this application for details.

[0119] For example, such as Figure 4 As shown, the configuration information for EES#2 can carry the topology connection information for EES2. The service configuration request sent by EEC or the EES retrieve request sent by EES#1 can indicate the communication requirements for the target EES.

[0120] Alternatively, in this embodiment of the application, the EES registration and EAS selection process can be enhanced so that the target EES can obtain the communication requirements for the target EAS, thereby determining whether it has a communication connection with the source EES that meets the communication requirements.

[0121] The enhanced EES registration process may include: enhanced EES configuration information, specifically, the EES configuration information including its topology connection information, which can indicate information about other EESs that have communication connections with this EES. The enhanced EAS selection process may include: a message sent by the terminal device to the target EES for EAS discovery, which can indicate the communication requirement for the target EES. See Embodiment 4 of this application for details.

[0122] Alternatively, in this embodiment of the application, the EES registration and EES selection process can be enhanced so that the EEC can obtain the topology connection information of the EES, thereby selecting the EES that meets the communication requirements of the target EES as the target EES.

[0123] The enhanced EES registration process may include: enhancing the EES's configuration information, specifically including the EES's topology connection information, which can indicate information about other EESs that have communication connections with this EES. The enhanced EES selection process may include: the ECS sending the EES's topology connection information to the EEC in a service provisioning response message. See Embodiment 5 of this application for details.

[0124] Alternatively, in this embodiment, the topological connection information of the EES can be obtained through the SMF, thereby selecting a DNAI that meets the requirements. See Embodiment Six of this application for details.

[0125] Furthermore, this application also provides a method for establishing a UPF tunnel between two UPFs that are respectively connected to each other via EES, as detailed in Embodiment Seven of this application. For example, as Figure 5 As shown.

[0126] It should be noted that the "communication requirements for the target EES" mentioned in the embodiments of this application can also be called "communication requirements for application context migration" or "communication requirements for migrating application context". It is understood that "communication requirements for the target EES", "communication requirements for application context migration", "communication requirements for migrating application context", "requirements for application context migration" and "requirements for migrating application context" can be equivalently substituted for each other.

[0127] The "communication connection between the source EES and the target EES" described in the embodiments of this application can also be called the "communication connection for application context migration" or "communication connection for migrating application context". It is understood that the "communication connection between the source EES and the target EES", "communication connection for application context migration" and "communication connection for migrating application context" can be used interchangeably.

[0128] It is understood that the "communication requirement" mentioned in the embodiments of this application can be understood as the requirement for a communication connection, and can also be referred to as "connection requirement," "requirement," "path requirement," etc. "Communication requirement," "connection requirement," "path requirement," and "requirement" can be understood to have the same meaning.

[0129] The following describes seven embodiments of this application.

[0130] Example 1:

[0131] Embodiment 1 of this application can be applied to scenarios where application context migration (application migration) is initiated by a terminal device (e.g., the EEC in the terminal device).

[0132] In Embodiment 1 of this application, the terminal device sends a request message to the ECS. This request message is used to obtain the EES, and the request message can indicate a communication requirement for the target EES. Therefore, the ECS can provide the terminal device with an EES that meets the communication requirement.

[0133] like Figure 6 The diagram shows the specific process of Embodiment 1. This process may include, but is not limited to, the EES registration process, the initial access process of the terminal device to EAS, and the application context migration process.

[0134] The EES registration process can be summarized as follows:

[0135] S601, the first EES sends a registration request to the ECS, and the registration request may carry the configuration information of the first EES.

[0136] The configuration information of the first EES includes information about the second EES that supports communication with it. For example, the configuration information of the first EES may include its topology connection information (also known as allowed connection information or allowed connection EES information), which may indicate information about the second EES that supports communication with it. The topology connection information of the first EES may include a list of edge computing service provider (ECSP) vendor identifiers, or a list of EES identifiers, or a list of endpoint information. The ECSP vendor identifier list may include the ECSP vendor identifiers of the second EES that support communication with the first EES. The EES identifier list may include the identifiers of the second EES that support communication with the first EES. The endpoint information list may include endpoint information of the second EES that supports communication with the first EES; for example, the endpoint information may be a set of IP addresses / fully qualified domain names (FQDNs) / uniform resource identifiers (URIs) / uniform resource locators (URLs), etc.

[0137] The first EES may include one or more EES, and the first EES may include EES 1 and EES 2.

[0138] The second EES may include one or more EES.

[0139] Optionally, the topology connection information may also include information about the communication connection between the first EES and the second EES. The information about the communication connection between the first EES and the second EES may include at least one of the following: the type of communication connection and the quality parameters of the communication connection.

[0140] The communication connection between the first EES and the second EES can be of various types, including but not limited to: IP connection, leased line connection, UPF tunnel connection, etc. The leased line connection can be a dedicated IP-based network connection, characterized by: short network path (e.g., a single-hop IP connection, or no or very few IP routers between the two endpoints), exclusive access to resources along the path, and high security. The communication quality of a leased line connection is higher than that of a typical IP routing connection.

[0141] The quality parameters of the communication connection between the first EES and the second EES may include, but are not limited to, bandwidth, latency, jitter, etc. The quality of the communication connection between the first EES and the second EES can be a statistical value over a period of time, a real-time value, or a predicted value.

[0142] Optionally, the configuration information of the first EES may also include at least one of the following: the first EES identification (ID), the first EES endpoint information, a list of EAS identifiers registered to the first EES, etc. The configuration information of the first EES may also include its security credentials. Furthermore, the configuration information of the first EES may include the registration validity period. To maintain the validity of the registration, the first EES may send a registration update request to the ECS before the registration validity period expires. If the ECS does not receive a registration update request within the registration validity period, the ECS can assume that the first EES has registered.

[0143] For example, the configuration information of the first EES can be shown in Table 1.

[0144] Table 1

[0145]

[0146] S602, ECS stores the configuration information of the first EES.

[0147] It should be noted that this registration process is an optional step. This registration process can also be used as a standalone implementation. Furthermore, the EES registration process and the initial access process of the terminal device to the EAS do not need to be executed consecutively; that is, the initial access process of the terminal device to the EAS can be executed at any interval after S602. The ECS can also obtain the EES topology connection information through other means, such as obtaining the EES topology connection information through the edge management system, or obtaining the topology connection information of the EDN where the EES is located through the edge management system. If the EDN where the EES is located has specific connection communication, it can be assumed that the EES deployed therein also shares the topology connection information of that EDN.

[0148] The initial access process for terminal devices to EAS may specifically include:

[0149] S603, the terminal device (e.g., the terminal device's EEC) sends a service configuration request to the ECS. This request message is used to discover the EES. The request message may contain the EEC's security credentials, the terminal device's identifier such as the generic public subscription identifier (GPSI), connection information, the terminal's location, and the AC configuration information (AC profile) in the terminal device.

[0150] S604, ECS performs authorization checks on terminal devices.

[0151] If the check passes, the ECS can select one or more EES based on the service configuration request. Specifically, the ECS can select an EES whose service area includes the location of the terminal device, or an EES whose registered EES list includes an EES ID matching the AC profile, etc.

[0152] S605, the ECS sends a service configuration request response message to the terminal device, which carries information about one or more EES that have been discovered.

[0153] S606, the terminal device (e.g., the EEC of the terminal device) sends an EAS discovery request message to EES 1 of the above one or more EESs. The EAS discovery request message may carry an EAS discovery filter, which may include the filtering parameters of EAS.

[0154] For example, EAS discovery filters can be shown in Table 2.

[0155] Table 2

[0156]

[0157] S607, EES 1 sends a response message to the terminal device for an EAS discovery request message. The response message carries a first EAS, wherein the first EAS includes one or more EAS that satisfy the EAS discovery filter.

[0158] S608, the terminal device selects EAS 1 in the first EAS for connection.

[0159] For example, the EEC of the terminal device can pass the first EAS to the AC through inter-layer interaction. The AC selects EAS 1 in the first EAS and connects to EAS 1 to perform application layer business interaction.

[0160] It should be noted that the initial connection process of this terminal device to EAS is an optional step.

[0161] The application context migration process may specifically include:

[0162] S609, The terminal device determines that an event triggering an application context migration has occurred.

[0163] For example, the terminal device detects that an event triggering an application context transition has occurred, or EES 1 detects that an event triggering an application context transition has occurred and notifies the terminal device.

[0164] For example, events that trigger application context migration may include, but are not limited to: the terminal device moving out of the service area of ​​the current EAS (i.e., EAS 1), or the EEC receiving a message from the SMF to establish a new session, or the EEC receiving a new IP prefix, etc.

[0165] Step S609 is an optional step.

[0166] S610, the terminal device (e.g., the terminal device's EEC) sends a service configuration request to the ECS. This request message is used to discover the EES, and the service configuration request can indicate the communication requirements for the target EES.

[0167] The service configuration request can indicate the communication requirements for the target EES. This can be done by explicitly carrying specific communication requirement parameters in the service configuration request message, or by implicitly indicating the index, pointer, or handle of the configuration file to which the communication requirements for the target EES belong.

[0168] For example, the communication requirements for the target EES may include at least one of the following: the target EES supports communication with the source EES (i.e., EES 1), the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES. These communication requirements for the target EES may be included in the application client profile (AC profile) or as a service key performance indicator (KPI) of the EAS.

[0169] Optionally, the communication requirements for the target EES may also include the ACR completion time.

[0170] The types of communication connections between EESs can include, but are not limited to, IP connections, leased line connections, UPF tunnel connections, etc.

[0171] The quality parameters of a communication connection may include, but are not limited to, bandwidth, latency, jitter, etc. For example, latency can be an acceptable migration time, an expected migration time, etc. The quality of the communication connection between EESs can be a statistical value over a period of time, a real-time value, or a predicted value.

[0172] It is understandable that "the target EES supports communication with the source EES" can be implicitly indicated. For example, when the communication requirements between the source EES and the target EES include the type of communication connection between the source EES and the target EES and the quality parameters of the communication connection between the source EES and the target EES, it can be implicitly indicated that the target EES needs to support communication with the source EES.

[0173] For example, in the implicit indication method, the communication requirements for the target EES, i.e., the ACR requirements, can be included in the application client profile (AC profile) or the edge application server profile (EAS profile). The message can carry the application client identifier (AC ID), the edge application server identifier (EAS ID), or the edge application server endpoint information (EAS endpoint) (which can be in the format of FQDN, IP address, URI, URL, etc.). The ECS can use the above information as an index to obtain the specific parameter information of "communication requirements for the target EES" in the ECS local or EES or edge management system.

[0174] Optionally, the request message may also carry information about the source EES, such as the source EES identifier or endpoint information. This source EES is connected to the EEC, provides edge services to the EEC, is registered with the source EAS, and can provide edge services to the EAS. The source EAS is the EAS connected to the application client on the terminal device that is about to undergo application context migration.

[0175] Optionally, the request message sent by the terminal device may instruct the target EES to perform application context migration, or the request message may instruct the discovery EES to perform application context migration with the source EES.

[0176] Optionally, the request message may explicitly carry indication information, which indicates that the target EES is used for application context migration, or that the discovered EES is for performing application context migration with the source EES. Alternatively, the request message may implicitly indicate that the target EES is used for application context migration or that the discovered EES is for performing application context migration with the source EES. For example, if the request message carries information about the source EES and / or a communication requirement for the target EES, it may implicitly indicate that the target EES is used for application context migration or that the discovered EES is for performing application context migration with the source EES.

[0177] Optionally, the request message may also include EEC security credentials, terminal device identifiers such as GPSI, connection information, location, and AC profile.

[0178] S611, the ECS sends a response message to the terminal device for a service configuration request. The response message carries information about a third EES, wherein the third EES includes one or more EES that meet the communication requirements.

[0179] S612, the terminal device (e.g., the EEC of the terminal device) sends an EAS discovery request message to EES 2 in the third EES. The EAS discovery request message may carry an EAS discovery filter, which may include the filtering parameters of EAS.

[0180] Optionally, the ECS can also trigger the core network equipment to establish a UPF tunnel between the UPF network element connected to the source EES and the UPF network element connected to the target EES (i.e., EES 2). See Embodiment Seven of this application.

[0181] S612 is similar to S606, and you can refer to step S606 above for details. It will not be repeated here.

[0182] S613, EES 2 sends a response message to the terminal device for the EAS discovery request message, the response message carrying a second EAS, wherein the second EAS includes one or more EAS that satisfy the EAS discovery filter.

[0183] S614, the terminal device selects EAS 2 in the second EAS as the target EAS.

[0184] S614 is similar to S608, and you can refer to step S608 above for details. It will not be repeated here.

[0185] S615, the terminal device (e.g., the terminal device's AC) triggers the transfer of the application context from EAS 1 to EAS 2.

[0186] S616, the terminal device switches the application connection from EAS 1 to EAS 2 and interacts with EAS 2 for application layer logic.

[0187] Steps S612 to S616 are all optional.

[0188] The solution in Implementation Example 1 avoids selecting a target EES that has no communication connection with the source EES or whose communication connection type or quality cannot meet the requirements of application context migration when performing application context switching, thereby ensuring the business continuity of the application.

[0189] Example 2:

[0190] Embodiment 2 of this application can be applied to scenarios of application context migration (application migration) initiated by the source EAS.

[0191] like Figure 7 The diagram shows the specific process of Embodiment 2. This process may include, but is not limited to, the EES registration process, the initial access process of the terminal device to EAS, and the application context migration process.

[0192] The registration process for EES can be found in steps S601 to S602 of the embodiment, and will not be repeated here. The registration process for EES is an optional step.

[0193] The process of initial access to EAS for terminal devices is described in steps S603 to S608 of the embodiment, and will not be repeated here. The process of initial access to EAS for terminal devices is an optional step.

[0194] The application context migration process may specifically include:

[0195] S709, EAS 1 detected an event that triggered an application context transition.

[0196] For example, events that trigger application context migration may include, but are not limited to: the terminal device moving out of the current EAS service area, or the EEC receiving a message from the SMF to establish a new session, or the EEC receiving a new IP prefix, etc.

[0197] S710, EAS 1 sends a first EAS discovery request to EES 1. The first EAS discovery request is used to obtain the target EAS for application context migration, and the first EAS discovery request indicates the communication requirements for application context migration (or may also be referred to as the communication requirements for the target EAS / EES).

[0198] The first EAS discovery request can indicate the communication requirements for application context migration. This can be done by explicitly carrying specific communication requirement parameters in the first EAS discovery request message, or by implicitly indicating that the first EAS discovery request message carries the index, pointer, or handle of the configuration file to which the communication requirements for the target EES belong.

[0199] For example, in the explicit indication method, the first EAS discovery request carries parameters of the communication requirements for the specific application context migration.

[0200] For example, in the implicit indication method, the communication requirements for application context migration can be included in the application client profile (AC profile) or the edge application server profile (EAS profile). The first EAS discovery request message can carry the application client identifier (AC ID), the edge application server identifier (EAS ID), or the edge application server endpoint information (EAS endpoint) (which can be in the format of FQDN, IP address, URI, URL, etc.). EES can use the above information as an index to obtain the specific parameter information of "communication requirements for application context migration" in the EES local or edge management system.

[0201] Optionally, the first EAS discovery request may also carry the identifier of EAS 1 and an EAS discovery filter. The EAS discovery filter can refer to the EAS discovery filter described in S606 of Embodiment 1 above. Furthermore, communication requirements for application context migration can also be included in the EAS discovery filter.

[0202] Optionally, the first EAS discovery request may also carry the target DNAI.

[0203] The communication requirements for application context migration may include at least one of the following: the target EES supports communication with the source EES, the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

[0204] Optionally, the communication requirements for the target EES may also include the ACR completion time.

[0205] The type of communication connection for migrating the application context may include, but is not limited to, IP connection, leased line connection, UPF tunnel connection, etc.

[0206] The quality parameters for migrating the communication connection of the application context may include, but are not limited to, bandwidth, latency, jitter, etc. For example, latency may be an acceptable migration duration, an expected migration duration, etc. The quality of the communication connection between EESs may be a statistical value over a period of time, a real-time value, or a predicted value.

[0207] It is understandable that "the target EES supports communication with the source EES" can be implicitly indicated. For example, when the communication requirements of migrating the application context include the type of communication connection to the application context and the quality parameters of the communication connection to the application context, it can be implicitly indicated that the target EES needs to support communication with the source EES.

[0208] Steps S709 and S710 are both optional.

[0209] S711, EES 1 sends a request message to ECS, which is used to obtain the target EES for application context migration, and the request message indicates the communication requirement for the target EES.

[0210] The specific parameters for the communication requirements of the target EES can be either the same as the communication requirements for application context migration sent by EAS, or the specific parameters for the new communication requirements of the target EES generated by EES 1 based on the communication requirements for application context migration.

[0211] This request message is similar to the service configuration request described in S610 of Embodiment 1 of this application. For details, please refer to the relevant description in step S610 of Embodiment 1 of this application, which will not be repeated here.

[0212] S712, the ECS sends a response message to the request message to EES 1. The response message carries information about the second EES, which may include one or more EES that meet the communication requirement.

[0213] S713, EES 1 sends a second EAS discovery request message to EES 2 in the second EES mentioned above. The second EAS discovery request message may carry an EAS discovery filter, which may include EAS filtering parameters.

[0214] The EAS discovery filter can be the EAS discovery filter carried in the first EAS discovery request.

[0215] Optionally, the ECS can also trigger the core network equipment to establish a UPF tunnel between the UPF network element connected to the source EES (i.e., EES 1) and the UPF network element connected to the target EES (i.e., EES 2). See Embodiment Seven of this application.

[0216] S714, EES 2 sends a response message to EES 1 for a second EAS discovery request message. The response message carries information about the second EAS, which includes one or more EAS that meet the requirements.

[0217] S715, EES 1 sends a response message to EAS 1 for the first EAS discovery request message, which carries the second EAS.

[0218] S716, EAS 1 transfers the application context from EAS 1 to EAS 2.

[0219] EAS 2 is the target EAS selected by EAS 1 from the second EAS mentioned above.

[0220] S717, the terminal device switches the application connection from EAS 1 to EAS 2 and interacts with EAS 2 for application layer logic.

[0221] Steps S713 to S717 are all optional.

[0222] The solution in Implementation Example 2 avoids selecting a target EES that has no communication connection with the source EES or whose communication connection type or quality cannot meet the requirements of application context migration when performing application context switching, thereby ensuring the business continuity of the application.

[0223] Example 3:

[0224] like Figure 8 The diagram shows the specific process of Embodiment 3. This process may include, but is not limited to, the EES registration process, the initial access process of the terminal device to EAS, and the application context migration process.

[0225] The registration process for EES can be found in steps S601 to S602 of the embodiment, and will not be repeated here. The registration process for EES is an optional step.

[0226] The process of initial access to EAS for terminal devices is described in steps S603 to S608 of the embodiment, and will not be repeated here. The process of initial access to EAS for terminal devices is an optional step.

[0227] S809, EAS 1 sends a first message to EES 1, which requests EES 1 to manage the migration of the application context of the terminal device, and the first message indicates the communication requirement for migrating the application context. For example, the first request message may be a full ACR request.

[0228] For example, the migration of application contexts of terminal devices managed by EES 1 may include: EES 1 being responsible for triggering event monitoring, discovering the target EAS, transferring (or transferring) the application context from the source EAS to the target EAS, notifying the EAS and EEC of the progress of application context migration (such as the selected target EAS, the completion of application context migration), and routing that affects the network user plane.

[0229] For details on the communication requirements for migrating application contexts, please refer to the relevant description of the communication requirements for migrating application contexts in S710 of the above embodiment 2, which will not be repeated here.

[0230] S810, EES 1 detected an event that triggered an application context transition.

[0231] For example, events that trigger application context migration may include, but are not limited to: the terminal device moving out of the current EAS service area, or the EEC receiving a message from the SMF to establish a new session, or the EEC receiving a new IP prefix, etc.

[0232] Steps S809 to S810 are all optional.

[0233] For details of S811 to S814, please refer to S711 to S714 of the above embodiment 2, which will not be repeated here.

[0234] S815, EES 1 sends a first notification message to EAS 1, which is used to instruct EAS 1 to freeze the application context of the terminal device or to indicate that the transmission of the application context is about to begin.

[0235] S816, EES 1 transfers the application context from EAS 1 to EAS 2.

[0236] Optionally, the application context can be stored in a shared area accessible by both EES 1 and EAS 1.

[0237] S817, EES 1 sends a second notification message to the terminal device. The second notification message is used to notify the terminal device to switch to EAS 2 or to indicate that the application context migration is complete.

[0238] Optionally, the second notification message may also include information about EAS2.

[0239] S818, the terminal device switches the application connection from EAS 1 to EAS 2 and interacts with EAS 2 for application layer logic.

[0240] Steps S813 to S818 are all optional.

[0241] The solution in Implementation Example 3 avoids selecting a target EES that has no communication connection with the source EES or whose communication connection type or quality cannot meet the requirements of application context migration when performing application context switching, thereby ensuring the continuity of application services.

[0242] Example 4:

[0243] Embodiment 4 of this application can be applied to scenarios where application context migration (application migration) is initiated by a terminal device (e.g., the EEC in the terminal device).

[0244] like Figure 9 The diagram shows the specific process of Example 4. This process may include, but is not limited to, the EES registration process, the initial access process of the terminal device to EAS, and the application context migration process.

[0245] The registration process for EES can be found in steps S601 to S602 of the embodiment, and will not be repeated here. The registration process for EES is an optional step.

[0246] The process of initial access to EAS for terminal devices is described in steps S603 to S608 of the embodiment, and will not be repeated here. The process of initial access to EAS for terminal devices is an optional step.

[0247] The application context migration process may specifically include:

[0248] S909 to S911 are similar to S609 to S611 in Embodiment 1, except that in S610 of Embodiment 1, the service configuration request indicates a communication requirement for the target EES, while in S910 of Embodiment 4, the service configuration request does not indicate a communication requirement for the target EES. In S611 of Embodiment 1, all EES included in the second EES fed back by the ECS meet the communication requirement, while in S911 of Embodiment 4, there may be EES in the second EES fed back by the ECS that do not meet the communication requirement.

[0249] S912, the terminal device (e.g., the terminal device's EEC) sends an EAS discovery request message to EES 2 in the second EES, which may indicate the need for application context migration.

[0250] Optionally, the request message may also carry ACR indication information, which indicates that the request message is used to discover an EAS for application context migration, or indicates that the request message requests the discovered EAS for application context migration.

[0251] The specific requirements for application context migration can be found in the descriptions of the communication requirements of the target EES in the three embodiments above, and will not be repeated here.

[0252] Optionally, the EAS discovery request message may carry an EAS discovery filter. The description of the EAS discovery filter in S606 of Embodiment 1 above can be found here and will not be repeated. Specific parameters regarding the application context migration requirements can be included in the EAS discovery filter.

[0253] S913, EES 2 determines whether it meets the application context migration requirement with EES 1. If not, proceed to step S914; if yes, proceed to step S915.

[0254] Optionally, EES 2 can also send a request message to ECS, which carries information about EES 1, information about EES 2, and the communication requirements between the source EES and the target EES. This allows ECS to determine whether EES 2 and EES 1 have a communication connection that meets the communication requirements.

[0255] S914, EES 2 sends a failure indication to the terminal device. This failure indication may indicate that there is no EAS that meets the communication requirement, or that the communication requirement cannot be met.

[0256] Optionally, the failure indication can also indicate which communication requirement is not met. For example, it can indicate that communication with the source EES is not supported, that there is no communication connection type required by the communication requirement between the source EES, or that the communication connection with the source EES does not meet the communication quality requirements.

[0257] Optionally, EES 2 can also trigger the core network device to establish a UPF tunnel between the UPF connected to EES 1 and the UPF connected to EES 2. The process by which the ECS triggers the core network device to establish a UPF tunnel between the UPF connected to EES 1 and the UPF connected to EES 2 can be found in Embodiment Seven of this application.

[0258] S914 is an optional step.

[0259] S915, EES 1 sends a response message to the terminal device for the EAS discovery request message. The response message carries information about a second EAS, which includes one or more EAS that meet the communication requirement.

[0260] S916, the terminal device selects EAS 2 from the second EAS as the target EAS.

[0261] S917, the application context is transferred from EAS 1 to EAS 2.

[0262] For example, EAS 1 can send the application context to EAS 2 via push, or EAS 2 can obtain the application context via pull.

[0263] Optionally, EES 2 may send a first notification message to EAS 2, which may carry information from EAS 1.

[0264] In step S918, EAS 2 sends a second notification message to EES 2. This second notification message can indicate that the application context transfer is complete or that the application context is ready to provide services to the user. Step S918 can be an optional step.

[0265] S919, EES 2 sends a third notification message to the terminal device. This third notification message can be used to instruct the terminal device to switch the application connection to EES 2.

[0266] S920, the terminal device switches the application connection from EAS 1 to EAS 2 and interacts with EAS 2 for application layer logic.

[0267] S906 to S920 are all optional steps.

[0268] The solution in Example 4 avoids selecting a target EES that has no communication connection with the source EES or whose communication connection type or quality cannot meet the requirements of application context migration when performing application context switching, thereby ensuring the business continuity of the application.

[0269] Example 5:

[0270] Embodiment 5 of this application can be applied to scenarios involving application context migration (application migration) initiated by a terminal device.

[0271] like Figure 10 As shown, the specific process of Embodiment 2 is provided. This process may include, but is not limited to, the EES registration process, the process of the terminal device initially accessing EAS, and the process of application context migration.

[0272] The registration process for EES can be found in steps S601-S602 of the embodiment, and will not be repeated here. The registration process for EES is optional.

[0273] The initial access process for terminal devices to EAS may specifically include:

[0274] S1003, the terminal device (e.g., the terminal device's EEC) sends a service configuration request to the ECS. This request message is used to discover the EES.

[0275] The request message may include EEC security credentials, terminal device identifiers such as GPSI, connection information, terminal device location, and AC profile in the terminal device.

[0276] S1004, ECS performs authorization checks on terminal devices.

[0277] If the check passes, the ECS can select a first EES based on the service configuration request. The first EES includes one or more EES. For example, the ECS can select an EES whose service area includes the location of the terminal device, or select an EES from the registered EAS list that includes an EAS ID that matches the AC profile, etc.

[0278] S1005, the ECS sends a service configuration request response message to the terminal device. The response message carries information about the first EES and the connection topology information of the first EES.

[0279] The connection topology information of the first EES can be found in the description of the connection topology information of the first EES in S601 of the above embodiment.

[0280] S1006 to S1008 can be referred to S606 to S608 of the above embodiment 1, and will not be repeated here.

[0281] It should be noted that the initial connection process of this terminal device to EAS is an optional step.

[0282] The application context migration process may specifically include:

[0283] S1009, The terminal device determines that an event triggering an application context migration has occurred.

[0284] For example, the terminal device detects that an event triggering an application context transition has occurred, or EES 1 detects that an event triggering an application context transition has occurred and notifies the terminal device.

[0285] For example, events that trigger application context migration may include, but are not limited to: the terminal device moving out of the current EAS service area, or the EEC receiving a message from the SMF to establish a new session, or the EEC receiving a new IP prefix, etc.

[0286] S1009 is an optional step.

[0287] S1010, the terminal device (e.g., the EEC of the terminal device) sends a service configuration request to the ECS. This request message is used to discover the EES.

[0288] S1011, the ECS sends a service configuration request response message to the terminal device. The response message carries information about the second EES, wherein the second EES includes one or more EES.

[0289] S1012, the terminal device selects an EES 2 that meets the communication requirements as the target EES.

[0290] The communication requirements can be found in the communication requirements for the target EES or the communication requirements for application context migration in the above embodiments, and will not be repeated here.

[0291] S1013 to S1017 can be S612 to S616 of the above embodiment 1, and will not be repeated here.

[0292] The solution in Example 5 enables the avoidance of selecting a target EES that has no communication connection with the source EES or whose communication connection type or quality cannot meet the requirements of application context migration when performing application context switching, thereby ensuring the business continuity of the application.

[0293] Example 6:

[0294] like Figure 11 As shown, the specific process of Embodiment Six may include, but is not limited to:

[0295] S1101, the NRF network element, UDR network element, or NEF network element receives the topology connection information of the first EES. The topology connection information of the first EES can be found in the relevant description of Embodiment 1 above, and will not be repeated here.

[0296] In one implementation, the NRF network element can receive a registration message from the first EES, the registration message containing the configuration information of the first EES, and the configuration information of the first EES containing the topology connection information of the EES.

[0297] In one implementation, the UDR network element can obtain the configuration information of the first EES from the first EES or ECS through a service parameter pre-configuration message. The configuration information of the first EES includes its topology connection information. Alternatively, the first EES or ECS can send its topology connection information to the UDR network element, and may also send the first EES endpoint information and the DNAI associated with the first EES to the UDR network element. This implementation is also applicable to NEF network elements.

[0298] S1102, the NRF network element, UDR network element, or NEF network element stores the topology connection information of the first EES.

[0299] Steps S1101 and S1102 are optional.

[0300] S1103, the AF network element (e.g., the source ESS) sends a request message to the PCF network element / NEF network element. The request message is used to subscribe to DNAI change events and contains a communication requirement for the target DNAI.

[0301] The communication requirements for the target DNAI include at least one of the following: the target EES corresponding to the target DNAI supports communication with the source EES; the type of communication connection between the source EES and the target EES corresponding to the target DNAI; and the quality parameters of the communication connection between the source EES and the target EES corresponding to the target DNAI.

[0302] Optionally, the communication requirements for the target DNAI may also include the ACR completion time.

[0303] The type of communication connection and the quality parameters of the communication connection can be found in the relevant descriptions in the above embodiments.

[0304] S1104, the PCF network element sends the communication request to the SMF network element in the SMF session.

[0305] Steps S1103 and S1104 are optional.

[0306] S1105, the SMF network element detects the first event, which is used by the SMF network element to select a new DNAI.

[0307] S1106, the SMF network element determines the target DNAI, and the target EES corresponding to the target DNAI supports communication with the source EES.

[0308] In one implementation, the SMF network element can determine a target DNAI based on the communication requirement and the connection topology information of the first EES. The EES corresponding to the target DNAI has a communication connection with the source EES corresponding to the source DNAI that meets the communication requirement.

[0309] Among them, the SMF network element can obtain the topology connection information of EES from the UDR network element, or from the NRF network element, or from the NEF network element, or the SMF network element can obtain the topology connection information of pre-configured EES from the local network.

[0310] S1107, the SMF network element sends a notification message to the AF network element, which can carry the target DNAI information.

[0311] Optionally, the notification message may also carry indication information, which indicates that the EES corresponding to the target DNAI has a communication connection with the source EES that meets the communication requirements.

[0312] In Embodiment Six of this application, the network side selects the DNAI corresponding to the EES that has a communication connection with the source EES when selecting the DNAI, thereby ensuring that the EES corresponding to the target DNAI has a communication connection with the source EES. This avoids selecting a target EES that does not have a communication connection with the source EES, or whose communication connection type or quality cannot meet the application context migration requirements, thus ensuring the service continuity of the application.

[0313] Example 7:

[0314] Embodiment 7 of this application provides a method for establishing a UPF tunnel between two UPFs that are respectively connected to each other via EES. Figure 12 As shown, the specific process of Embodiment Seven may include, but is not limited to:

[0315] S1201, the source AF network element sends a first message to the first SMF network element. This first message is used to request the establishment of a UPF tunnel between the source UPF network element and the target UPF network element. The first request message may include target routing information, which can be used to determine the target UPF network element.

[0316] The source UPF network element can be a UPF network element connected to the source EES. The destination UPF network element can be a UPF network element connected to the destination EES.

[0317] For example, the first message may be referred to as a transport service request.

[0318] Optionally, the first message may include QoS requirements. It may also include the identifier or IP address of the terminal device.

[0319] The first message may also contain source routing information, which can be used to determine the source UPF, or it can be used to determine the sender of the data.

[0320] Among them, the source AF network element can be the source EES.

[0321] Alternatively, step S1201 can also be executed by the target AF network element, such as the target EES. Or, it can be executed by the ECS.

[0322] In one implementation, the AF network element can also send the first message to the PCF network element, and the PCF network element will then send the information carried in the first message to the first SMF network element. Alternatively, the AF can send the first message to the PCF via the NEF.

[0323] In one possible implementation, the SMF network element can also determine the source routing information of the source UPF network element corresponding to the terminal device based on the terminal device's identifier or IP address.

[0324] S1202, the first SMF network element searches for a second SMF network element that can serve the target routing information.

[0325] In one implementation, if the target routing information is within the service range of the first SMF network element, and the second SMF network element is the same as the first SMF network element, then the first SMF network element can locally select the target UPF network element corresponding to the target routing information.

[0326] If the target routing information is not within the service range of the first SMF network element, the first SMF network element can discover the second SMF network element that serves the target routing information through the NRF network element.

[0327] Optionally, if the second SMF network element and the first SMF network element are two different network elements, the following steps S1203a to S1203e can be executed:

[0328] S1203a, the first SMF network element can send a second message to the second SMF network element. The second message is used to request the establishment of a UPF tunnel between the source UPF network element and the target UPF network element. The second message may include QoS requirements, target routing information, and source routing information.

[0329] S1203b, the second SMF network element selects the target UPF corresponding to the target routing information. Specifically, the second SMF can select the target UPF based on the target routing information.

[0330] S1203c, the second SMF network element sends a third message to the selected target UPF network element. This third message may contain forwarding rules, which instruct the source UPF network element to forward data from the source AF to the target UPF network element. The forwarding rules carry tunnel information of the source UPF network element. For example, if the forwarding rule contains the IP address and port number of the source AF, it instructs the source UPF to forward data packets whose source address is the IP address and port number of the source AF to the target UPF network element. As another example, if the forwarding rule contains the IP address and port number of both the source and target AF, it instructs the source UPF to forward data packets whose source address is the IP address and port number of the source AF and whose destination address is the IP address and port number of the target AF to the target UPF network element.

[0331] Optionally, the third message may also include QoS requirements.

[0332] S1203d, the target UPF network element sends a response message of the third message to the second SMF network element.

[0333] S1203e, the second SMF network element sends a response message of the second message to the first SMF network element. The response message contains the tunnel information of the target UPF network element, which may include the IP address and port number.

[0334] S1204, the first SMF network element sends a fourth message to the source UPF network element. This fourth message contains the aforementioned forwarding rules. The forwarding rules instruct the target UPF network element to forward data from the source UPF to the target AF network element. The forwarding rules carry the tunnel information of the target UPF network element. For example, if the forwarding rules contain the IP address and port number of the source UPF and the IP address and port number of the target AF, then the target UPF is instructed to forward data packets whose source address is the IP address and port number of the source UPF and whose destination address is the IP address and port number of the target AF to the target UPF network element.

[0335] S1205, the source UPF network element sends a response message for the fourth message to the first SMF network element.

[0336] S1206, the first SMF / PCF sends a response message of the first message to the AF network element. The response message may carry service interface information (such as the IP address and port number of the source UPF). The service interface information may be allocated by the first SMF network element or the source UPF network element and is used by the source EES to send application context data.

[0337] S1207, the source AF network element sends the application context data to the source UPF network element, the source UPF network element sends the application context data to the target UPF network element, and the target UPF network element forwards the application context data to the target AF network element.

[0338] The source AF can be the source EES or the source EAS, and the destination AF can be the corresponding destination EES or destination EAS. Alternatively, if the source AF is an ECS, then the source routing information is used to indicate the source EES, and the destination routing information is used to indicate the destination EES. In this case, the data sender is no longer the source AF, but the data originator. Therefore, the forwarding rule no longer contains the IP address or port number of the source AF, but contains the IP address or port number of the data originator.

[0339] Based on the above embodiments, this application also provides a communication device, see below. Figure 13 As shown, the communication device 1300 may include a processing unit 1301 and a transceiver unit 1302. The transceiver unit 1302 is used by the communication device 1300 to perform communication transmissions, such as receiving or sending information (frames, messages, or data) as described in Embodiments 1 to 7. The processing unit 1301 is used to perform actions other than sending and receiving, such as determining actions, judging actions, selecting actions, controlling and managing the actions of the communication device 1300, etc. The processing unit 1301 can also control the steps performed by the transceiver unit 1302.

[0340] For example, the communication device 1300 may be a communication device in the above embodiments, or a processor in the communication device, or a chip or chip system in the communication device, or a functional module in the communication device, etc., wherein the communication device may be an ECS or a terminal device or an EES or an EAS or an SMF, etc.

[0341] Specifically, the communication device 1300 is used to implement the above. Figures 6-8 In the illustrated embodiment, the functions of the ECS may specifically include:

[0342] The transceiver unit 1302 is configured to receive a first request message, the first request message being used to discover an EES, and the request message indicating a communication requirement for a target EES; the processing unit 1301 is configured to determine at least one EES that satisfies the communication requirement; the transceiver unit 1302 is further configured to: send a response message, the response message carrying information about the at least one EES.

[0343] Optionally, the transceiver unit 1302 is further configured to: receive configuration information of a first EES before receiving the first request message, wherein the first EES includes a source EES and / or the target EES, and the configuration information of the first EES includes information of a second EES that supports communication with the first EES.

[0344] For example, the configuration information of the first EES may also include information on the communication connection between the first EES and the second EES.

[0345] For example, the communication requirements include at least one of the following: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

[0346] For example, the first request message carries information about the source EES.

[0347] For example, the first request information carries indication information, which is used to instruct the target EES to use for application context migration.

[0348] The communication device 1300 is used to implement the above. Figure 6 In the illustrated embodiment, the terminal device may specifically include: a transceiver unit 1302 for communicating with an ECS; a processing unit 1301 for sending a first request message to the ECS via the transceiver unit 1302, the first request message being used to discover an Edge Enabled Server (EES) and indicating a communication requirement for a target EES; and receiving a response message from the ECS via the transceiver unit 1302, the response message carrying information about at least one EES that meets the communication requirement.

[0349] For example, the communication requirements include at least one of the following: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

[0350] For example, the first request message carries information about the source EES.

[0351] For example, the first request information carries indication information, which is used to instruct the target EES to use for application context migration.

[0352] The communication device 1300 is used to implement the above. Figure 7 or Figure 8In the illustrated embodiment, the function of the source EES (i.e., EES 1) may specifically include: a transceiver unit 1302 for communicating with the ECS; a processing unit 1301 for sending a first request message to the ECS through the transceiver unit 1302, the first request message being used to discover an EES and indicating a first communication requirement for the target EES; and receiving a response message from the ECS through the transceiver unit 1302, the response message carrying information about at least one EES that satisfies the first communication requirement.

[0353] Optionally, the processing unit 1301 is further configured to: receive a second communication request from the first EAS via the transceiver unit 1302, the second communication request being used to indicate the communication request of the EAS for the application context migration.

[0354] For example, the second communication requirement includes quality parameters of the communication connection for migrating the application context and / or the type of communication connection for migrating the application context.

[0355] For example, the second communication requirement also includes at least one of the following: the target EES supports communication with the first EES, the type of communication connection between the first EES and the target EES, and the quality parameters of the communication connection between the first EES and the target EES.

[0356] For example, the first request message carries information about the first EES.

[0357] For example, the first request information carries indication information, which is used to instruct the target EES to apply uplink migration.

[0358] The communication device 1300 is used to implement the above. Figure 9 In the illustrated embodiment, the function of the target EES (i.e., EES 2) may specifically include: a transceiver unit 1302, configured to: receive a first request message from a terminal device, the first request message being used to request the target EES to discover a target edge application server (EAS) for migrating the application context of the terminal device, and the request message containing a communication requirement for application context migration; a processing unit 1301, configured to determine that an EAS that meets the communication requirement exists; the transceiver unit 1302 is further configured to, when the processing unit 1301 determines that an EAS that meets the communication requirement exists, send a response message to the terminal device, the response message carrying information about the EAS that meets the communication requirement.

[0359] For example, the communication requirements include: the target EES supports communication with the source EES, the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

[0360] The communication device 1300 is used to implement the above. Figure 9 In the illustrated embodiment, the terminal device may specifically include: a transceiver unit 1302 for communicating with a target EES; a processing unit 1301 for sending a first request message to the target EES through the transceiver unit 1302, the request message requesting the target EES to discover a target edge application server (EAS) for migrating the application context of the terminal device, and the request message containing a communication requirement for application context migration; and receiving a response message from the target EES through the transceiver unit 1302, the response message containing information about an EAS that meets the communication requirement.

[0361] For example, the communication requirements include: the target EES supports communication with the source EES, the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

[0362] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The functional units in the embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0363] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0364] It is understood that the functions or implementations of the various modules in the embodiments of this application can be further referred to the relevant descriptions in the method embodiments.

[0365] In one possible approach, the communication device can be as follows: Figure 14 As shown, the device can be a communication device or a chip within a communication device, wherein the communication device can be an ECS, a terminal device, or an EES as described in the above embodiments. The device may include a processor 1401, a communication interface 1402, and a memory 1403. The processing unit 1301 can be the processor 1401. The transceiver unit 1302 can be the communication interface 1402.

[0366] The processor 1401 can be a CPU, a digital processing unit, or something similar. The communication interface 1402 can be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device also includes a memory 1403 for storing the program executed by the processor 1401. The memory 1403 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory 1403 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited to this.

[0367] The processor 1401 is used to execute the program code stored in the memory 1403, specifically to perform the actions of the processing unit 1301, which will not be described in detail here. The communication interface 1402 is specifically used to perform the actions of the transceiver unit 1302, which will not be described in detail here.

[0368] This application embodiment does not limit the specific connection medium between the communication interface 1402, processor 1401, and memory 1403. This application embodiment... Figure 14 The memory 1403, processor 1401, and communication interface 1402 are connected via a bus 1404. Figure 14 The connections between other components are shown in bold lines only and are not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0369] This application also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0370] This application also provides a computer program product for storing a computer program. When the computer program is executed by a computer, the computer can implement the communication method provided in the above method embodiments.

[0371] This application also provides a chip coupled to a memory, which is used to implement the communication method provided in the above method embodiments.

[0372] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0373] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0374] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0375] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0376] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: The edge configuration server (ECS) receives a first request message, which is used to discover the edge enable server (EES). The request message indicates a communication requirement for the target EES, and the communication requirement includes that the target EES supports communication with the source EES. The ECS determines at least one EES that meets the communication requirements based on the EES topology connection information, wherein the EES topology connection information includes EES that have a communication connection with the source EES. The ECS sends a response message, which carries information about the at least one EES.

2. The method as described in claim 1, characterized in that, Before the Edge Configuration Server (ECS) receives the first request message, the method further includes: The ECS receives configuration information from a first EES, which includes a source EES and / or the target EES. The configuration information of the first EES includes information about a second EES that supports communication with the first EES.

3. The method as described in claim 2, characterized in that, The configuration information of the first EES also includes information on the communication connection between the first EES and the second EES.

4. The method as described in claim 1, characterized in that, The communication requirements also include at least one of the following: the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

5. The method as described in claim 1, characterized in that, The first request message carries information about the source EES.

6. The method according to any one of claims 1-5, characterized in that, The first request message carries indication information, which is used to instruct the target EES to perform application context migration.

7. A communication method, characterized in that, include: The terminal device sends a first request message to the edge configuration server (ECS). The first request message is used to discover the edge enable server (EES), and the first request message indicates a communication requirement for the target EES. The communication requirement includes that the target EES supports communication with the source EES. The terminal device receives a response message from the ECS. The response message carries information about at least one EES that meets the communication requirements. The at least one EES that meets the communication requirements is determined based on EES topology connection information, which includes EES that have a communication connection with the source EES.

8. The method as described in claim 7, characterized in that, The communication requirements also include at least one of the following: the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

9. The method as described in claim 7, characterized in that, The first request message carries information about the source EES.

10. The method according to any one of claims 7-9, characterized in that, The first request message carries indication information, which is used to instruct the target EES to perform application context migration.

11. A communication method, characterized in that, include: The first edge enabling server (EES) sends a first request message to the edge configuration server (ECS). The first request message is used to discover the edge enabling server (EES) and indicates a first communication requirement for the target EES. The first communication requirement includes that the target EES supports communication with the first EES. The first EES receives a response message from the ECS. The response message carries information about at least one EES that meets the first communication requirement. The at least one EES that meets the communication requirement is determined based on EES topology connection information, which includes EES that have a communication connection with the first EES.

12. The method as described in claim 11, characterized in that, The method further includes: The first EES receives a second communication request from the first edge application server (EAS), the second communication request being used to indicate the communication request of the EAS for application context migration.

13. The method as described in claim 12, characterized in that, The second communication requirement includes quality parameters of the communication connection for migrating the application context and / or the type of communication connection for migrating the application context.

14. The method as described in claim 11, characterized in that, The first communication requirement also includes at least one of the following: the type of communication connection between the first EES and the target EES, and the quality parameters of the communication connection between the first EES and the target EES.

15. The method as described in claim 11, characterized in that, The first request message carries information about the first EES.

16. The method according to any one of claims 11-15, characterized in that, The first request message carries indication information, which is used to instruct the target EES to apply uplink migration.

17. A communication method, characterized in that, include: The target edge enable server (EES) receives a first request message from the terminal device. The first request message is used to request the target EES to discover the target edge application server (EAS) for migrating the application context of the terminal device. The request message contains a communication requirement for the application context migration, and the communication requirement includes that the target EES supports communication with the source EES. When the target EES determines that there exists an EAS that meets the communication requirements, the target EES sends a response message to the terminal device. The response message carries information about the EAS that meets the communication requirements. The EAS that meets the communication requirements is determined based on the EES topology connection information, which includes EES that have a communication connection with the source EES.

18. The method as described in claim 17, characterized in that, The communication requirements also include at least one of the following: the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

19. A communication method, characterized in that, include: The terminal device sends a first request message to the target edge enable server (EES). The request message is used to request the target EES to discover the target edge application server (EAS) for migrating the application context of the terminal device. The request message contains a communication requirement for the application context migration, and the communication requirement includes that the target EES supports communication with the source EES. The terminal device receives a response message from the target EES. The response message contains information about an EAS that meets the communication requirements. The EAS that meets the communication requirements is determined based on EES topology connection information, which includes EES that have a communication connection with the source EES.

20. The method as described in claim 19, characterized in that, The communication requirements also include at least one of the following: the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

21. A communication device, characterized in that, include: The transceiver unit is configured to receive a first request message, the first request message being used to discover an edge enable server (EES), and the request message indicating a communication requirement for a target EES, the communication requirement including that the target EES supports communication with a source EES; A processing unit is configured to determine at least one EES that meets the communication requirements based on EES topology connection information, wherein the EES topology connection information includes EES that have a communication connection with the source EES. The transceiver unit is further configured to: send a response message, the response message carrying information of the at least one EES.

22. The apparatus as claimed in claim 21, characterized in that, The transceiver unit is further configured to: Before receiving the first request message, configuration information of a first EES is received, wherein the first EES includes a source EES and / or the target EES, and the configuration information of the first EES includes information of a second EES that supports communication with the first EES.

23. The apparatus as claimed in claim 22, characterized in that, The configuration information of the first EES also includes information on the communication connection between the first EES and the second EES.

24. The apparatus as claimed in claim 21, characterized in that, The communication requirements also include at least one of the following: the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

25. The apparatus as claimed in claim 21, characterized in that, The first request message carries information about the source EES.

26. The apparatus according to any one of claims 21-25, characterized in that, The first request message carries indication information, which is used to instruct the target EES to perform application context migration.

27. A communication device, characterized in that, include: The transceiver unit is used to communicate with the edge configuration server (ECS). The processing unit is configured to send a first request message to the ECS via the transceiver unit, the first request message being used to discover an Edge Enabled Server (EES), and the first request message indicating a communication requirement for a target EES, the communication requirement including that the target EES supports communication with a source EES; and to receive a response message from the ECS via the transceiver unit, the response message carrying information about at least one EES that meets the communication requirement, the at least one EES that meets the communication requirement being determined based on EES topology connection information, the EES topology connection information including EES that have a communication connection with the source EES.

28. The apparatus as claimed in claim 27, characterized in that, The communication requirements also include at least one of the following: the type of communication connection between the source EES and the target EES, and the quality parameters of the communication connection between the source EES and the target EES.

29. The apparatus as claimed in claim 27, characterized in that, The first request message carries information about the source EES.

30. The apparatus according to any one of claims 27-29, characterized in that, The first request message carries indication information, which is used to instruct the target EES to perform application context migration.

31. A communication device, characterized in that, The device is applied to a first edge-enabled server (EES) and includes: The transceiver unit is used to communicate with the edge configuration server (ECS). The processing unit is configured to send a first request message to the ECS via the transceiver unit. The first request message is used to discover the EES, and the first request message indicates a first communication requirement for the target EES, the first communication requirement including that the target EES supports communication with the first EES; and... The transceiver unit receives a response message from the ECS. The response message carries information about at least one EES that meets the first communication requirement. The at least one EES that meets the communication requirement is determined based on EES topology connection information, which includes EES that have a communication connection with the first EES.

32. The apparatus as claimed in claim 31, characterized in that, The processing unit is further configured to: The transceiver unit receives a second communication request from the first edge application server (EAS), the second communication request being used to indicate the EAS's communication request for application context migration.

33. The apparatus as claimed in claim 32, characterized in that, The second communication requirement includes quality parameters of the communication connection for migrating the application context and / or the type of communication connection for migrating the application context.

34. The apparatus as claimed in claim 31, characterized in that, The first communication requirement also includes at least one of the following: the type of communication connection between the first EES and the target EES, and the quality parameters of the communication connection between the first EES and the target EES.

35. The apparatus as claimed in claim 31, characterized in that, The first request message carries information about the first EES.

36. The apparatus according to any one of claims 31-35, characterized in that, The first request message carries indication information, which is used to instruct the target EES to apply uplink migration.

37. A communication device, characterized in that, include: The transceiver unit is configured to: receive a first request message from a terminal device, wherein the first request message is configured to request the target edge enable server (EES) to discover the target edge application server (EAS) for migrating the application context of the terminal device, and the request message contains a communication requirement for the application context migration, wherein the communication requirement includes that the target EES supports communication with the source EES. Processing unit, configured to determine the existence of an EAS that satisfies the communication requirements; The transceiver unit is further configured to send a response message to the terminal device when the processing unit determines that there is an EAS that meets the communication requirements. The response message carries information about the EAS that meets the communication requirements. The EAS that meets the communication requirements is determined based on EES topology connection information, and the EES topology connection information includes EES that have a communication connection with the source EES.

38. The apparatus as claimed in claim 37, characterized in that, The communication requirements also include at least one of the following: the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

39. A communication device, characterized in that, include: The transceiver unit is used to communicate with the target edge enable server (EES). The processing unit is configured to send a first request message to the target EES through the transceiver unit. The request message is used to request the target EES to discover the target edge application server (EAS) for migrating the application context of the terminal device. The request message contains a communication requirement for the application context migration, and the communication requirement includes that the target EES supports communication with the source EES. as well as The transceiver unit receives a response message from the target EES. The response message contains information about an EAS that meets the communication requirements. The EAS that meets the communication requirements is determined based on EES topology connection information, which includes EES that have a communication connection with the source EES.

40. The apparatus as claimed in claim 39, characterized in that, The communication requirements also include at least one of the following: the type of communication connection for migrating the application context, and the quality parameters of the communication connection for migrating the application context.

41. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed on a communication device, perform the method as described in any one of claims 1 to 20.

Images