WO2022179218A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022179218A1
WO2022179218A1 PCT/CN2021/133186 CN2021133186W WO2022179218A1 WO 2022179218 A1 WO2022179218 A1 WO 2022179218A1 CN 2021133186 W CN2021133186 W CN 2021133186W WO 2022179218 A1 WO2022179218 A1 WO 2022179218A1
Authority
WO
WIPO (PCT)
Prior art keywords
ees
communication
target
information
eas
Prior art date
Application number
PCT/CN2021/133186
Other languages
English (en)
French (fr)
Inventor
葛翠丽
杨艳梅
胡雅婕
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022179218A1 publication Critical patent/WO2022179218A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method and apparatus.
  • the same application is often deployed in multiple edge data networks at the same time.
  • Servers of the same application deployed in different edge data networks can provide the same services and have functional equivalence.
  • the terminal device accesses the network, it will select the application instance in the nearest edge data network to execute the service. Due to the mobility of the terminal device, the application instance selected by the terminal device may not be able to continue to provide services for the terminal device.
  • the network re-selects a new edge data network for the terminal device. The application instance continues to conduct business. Complete the switch from the source application instance to the target application instance.
  • Embodiments of the present application provide a communication method and apparatus, which are used to solve the problem that application contexts cannot be migrated between two edge data network centers.
  • a communication method is provided.
  • the method can be applied to an edge configuration server (ECS).
  • ECS edge configuration server
  • the method includes the following steps: the ECS receives a first request message, and the first request message is used to discover the edge configuration server.
  • an edge enabler server (EES) and the request message indicates a communication requirement for the target EES; the ECS determines at least one EES that satisfies the communication requirement; the ECS sends a response message, the response message carries all information about at least one EES.
  • the application context switch by indicating the communication requirement for the target EES in the request message for discovering the EES, when the application context switch is performed, it is possible to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection.
  • the target EES that cannot meet the communication requirements of application context migration, so that the business continuity of the application can be guaranteed.
  • the edge configuration server ECS before the edge configuration server ECS receives the first request message, the ECS respectively receives configuration information of the first EES, where the first EES includes the source EES and/or the target EES, wherein , the configuration information of the first EES includes information of a second EES supporting communication with the first EES.
  • the ECS can obtain the topological connection relationship of the EES, so that when the application context is switched, the target ESS that has a communication connection with the source EES can be selected to ensure the service continuity of the application.
  • the first EES includes one or more EESs.
  • the configuration information of the first EES further includes information of the communication connection between the first EES and the second EES.
  • ECS can obtain the topological connection relationship and communication connection information of EES, so that during application context switching, it can select the target EES whose communication connection type or communication connection quality meets the communication requirements of application context migration. Business continuity for applications.
  • the ECS sends a second request message to a policy control function (policy control function, PCF) or a session management function (sEESion management function, SMF) network element, where the second request message is used to request establishment 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.
  • policy control function policy control function
  • SMF session management function
  • the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, the source EES Quality parameter of the communication connection between the EES and the target EES.
  • the ECS can find the target EES that satisfies the communication quality.
  • the first request message carries the information of the source EES.
  • the ECS can determine the source EES, so that the target EES that has a communication connection with the source EES can be found.
  • 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.
  • a communication method is provided.
  • the method can be applied to a terminal device.
  • the method includes the following steps: the terminal device sends a first request message to the ECS, where the first request message is used to discover the EES, and the first request message is used to discover the EES.
  • the request message indicates a communication requirement for the target EES; 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.
  • the terminal device by indicating the communication requirement for the target EES in the request message for discovering the EES, when the application context switch is performed, it is possible to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection.
  • the target EES that cannot meet the communication requirements of application context migration, so that the business continuity of the application can be guaranteed.
  • the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, the source EES Quality parameter of the communication connection between the EES and the target EES.
  • the ECS can find the target EES that satisfies the communication quality.
  • the first request message carries the information of the source EES.
  • the ECS can determine the source EES, so that the target EES that has a communication connection with the source EES can be found.
  • 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.
  • a communication method is provided, the method can be applied to an edge application server (edge application server, EAS), the method includes the following steps: the first EAS sends a first request message to the first EES, the first request The message is used to discover a target EAS for application context migration with 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, where the response message includes information of an EAS that meets the communication requirement.
  • edge application server edge application server
  • 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, so that the application
  • context switching it is possible to avoid selecting a target EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection cannot meet the communication requirements of the application context migration, thereby ensuring the business continuity of the application.
  • the communication requirement includes a quality parameter of a communication connection for migrating the application context and/or a type of communication connection for migrating the application context.
  • a communication method in a fourth aspect, can be applied to EES, and the method includes the following steps: a first edge enablement server EES sends a first request message to an edge configuration server ECS, where the first request message is used for discovery EES, and the first request message indicates the first communication requirement for the target EES; the first EES receives a response message from the ECS, the response message carries at least one communication requirement that satisfies the first communication requirement EES information.
  • the communication requirement for the target EES in the request message for discovering the EES when the application context switch is performed, it is possible to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection.
  • the target EES that cannot meet the communication requirements of application context migration, so that the business continuity of the application can be guaranteed.
  • the first EES receives a second communication requirement from the first edge application server EAS, where the second communication requirement is used to indicate the communication requirement of the EAS for the application context migration.
  • the source EES can obtain the communication requirements of the application context migration.
  • the second communication requirement includes a quality parameter of a communication connection for migrating the application context and/or a type of communication connection for migrating the application context.
  • the second communication requirement further includes at least one item of the following information: the target EES supports communication with the first EES, and communication between the first EES and the target EES Type of connection, quality parameters of the communication connection between the first EES and the target EES.
  • the ECS can find the target EES that satisfies the communication quality.
  • the first request message carries the information of the first EES.
  • the ECS can determine the source EES, so that the target EES that has a communication connection with the source EES can be found.
  • the first request information carries indication information, where the indication information is used to indicate that the target EES is used to apply uplink migration.
  • a communication method in a fifth aspect, can be applied to an EES, and the method includes the following steps: a target EES receives a first request message from a terminal device, where the first request message is used to request the target EES to discover and migrate The target EAS of the application context of the terminal device, and the request message includes the communication requirement for the application context migration; when the target EES determines that there is an EAS that meets the requirement, the target EES sends to the terminal device. A response message, where the response message carries the information of the required EAS.
  • the target EES can determine whether there is a communication connection with the source EES that meets the communication requirements according to the communication requirements, so as to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection cannot satisfy the application context migration
  • the communication requirements of the target EES so that the business continuity of the application can be guaranteed.
  • the target EES sends a second request message to the PCF network element or the SMF network element, where the second request message is used to request to establish the user plane function UPF network element connected to the source EES and the Describe the UPF tunnel between the UPF network elements connected to the target EES.
  • the source EES and the target EES can communicate, so that application context migration can be realized.
  • the communication requirement includes: the target EES supports communication with the source EES, the type of the communication connection of the application context migration, and the quality parameter of the communication connection of the application context migration.
  • a communication method in a sixth aspect, can be applied to a terminal device, and the method includes the following steps: the terminal device sends a first request message to a target EES, where the request message is used to request the target EES to discover and migrate the The target edge application server EAS of 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, and the response message includes a response message that satisfies the requirement EAS information.
  • the target EES can determine whether there is a communication connection with the source EES that meets the communication requirements according to the communication requirements, so as to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection cannot satisfy the application context migration
  • the communication requirements of the target EES so that the business continuity of the application can be guaranteed.
  • the communication requirement includes: the target EES supports communication with the source EES, the type of the communication connection of the application context migration, and the quality parameter of the communication connection of the application context migration.
  • a communication method in a seventh aspect, can be applied to an ECS, and the method includes the following steps: the ECS receives a request message, the request message is used to discover the EES; the ECS sends a response message, the response message carries the first Information of an EES, wherein the information of the first EES includes information of a second EES supporting communication with the first EES.
  • the ECS sends the EES topology connection information to the terminal device, so that the terminal device can avoid selecting a target EES that has no communication connection with the source EES, or the communication connection type or communication connection quality cannot satisfy the application context migration. The communication requirements of the target EES, so that the business continuity of the application can be guaranteed.
  • the first EES includes one or more EESs.
  • the second EES includes one or more EESs.
  • the information of the first EES further includes information of the communication connection between the first EES and the second EES.
  • the information of the communication connection includes at least one of the following information: the type of the communication connection between the first EES and the second EES, the type of the communication connection between the first EES and the second EES Quality parameter for communication connections between EESs.
  • a communication method can be applied to a terminal device, and the method includes the following steps: the terminal device sends a first request message to the ECS, where the first request message is used to obtain the edge enabled server EES; The terminal device receives a response message from the ECS, where the response message carries information of a first EES, where the information of the first EES includes information of a second EES that supports communication with the first EES.
  • the ECS sends the EES topology connection information to the terminal device, so that the terminal device can avoid selecting a target EES that has no communication connection with the source EES, or the communication connection type or communication connection quality cannot satisfy the application context migration. The communication requirements of the target EES, so that the business continuity of the application can be guaranteed.
  • the first EES includes one or more EESs.
  • the second EES includes one or more EESs.
  • the information of the first EES further includes information of the communication connection between the first EES and the second EES.
  • the information of the communication connection includes at least one of the following information: the type of the communication connection between the first EES and the second EES, the type of the communication connection between the first EES and the second EES Quality parameter for communication connections between EESs.
  • the terminal device determines a target EES according to the information with the first EES, where the target EES meets the communication requirement of application context migration.
  • the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, the type of the communication connection for the application context migration, the communication for the application context migration Connection quality parameter.
  • a communication method can be applied to an SMF network element, and the method includes the following steps: the core network device detects a first event, and the first event is used by the core network device to select a new The data network access identifier DNAI; the core network device determines the target DNAI, and the target edge enabling server EES corresponding to the target DNAI supports communication with the source EES.
  • 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, and can avoid selecting an EES that has no communication connection with the source EES.
  • the communication connection, or the type of the communication connection or the quality of the communication connection cannot meet the target EES of the application context migration, so that the service continuity of the application can be guaranteed.
  • the core network device receives a request message sent by the application function AF network element, the request message is used to obtain the information of the target DNAI, and the request message includes the communication requirements for the target DNAI;
  • the first core network device sends a response message to the request message to the AF network element, where the response message includes the target DNAI.
  • the core network equipment can obtain the communication requirements for the target DNAI.
  • the communication requirement for the target DNAI includes at least one of the following pieces of information: the target EES corresponding to the target DNAI supports communication with the source EES, the communication between the source EES and the target EES The type of communication connection between the source EES and the target EES, the quality parameter of the communication connection.
  • the first core network device obtains the information of the source EES and the information of the target EES.
  • the core network device can obtain the topology connection information of the EES, so as to select the target DNAI that meets the communication requirements.
  • a tenth aspect provides a communication method, which can be applied to SMF.
  • the method includes the following steps: a first core network device receives a first message sent from an application function AF network element, where the first message is used to request a setup
  • the first core network device obtains the tunnel information of the second UPF network element according to the target routing information; the first core network device sends a forwarding rule to the first UPF network element, the forwarding rule It is used to instruct the first UPF network element to forward the data from the source EES to the second UPF network element, and the forwarding rule carries the tunnel information of the second UPF network element.
  • the AF network element may be the source EES or the target EES or the ECS.
  • the target routing information includes target DNAI and/or target N6 routing information.
  • the first core network device acquires the tunnel information of the second UPF network element according to the target routing information, including: if the target routing information is in the service of the first core network device within the range, the first core network device determines the tunnel information of the second UPF according to the target routing information.
  • the SMF network element can locally obtain the tunnel information of the second UPF network element.
  • the first core network device sends the foregoing forwarding rule to the second UPF, where the forwarding rule is further used to instruct the second UPF to forward the data from the network element of the first UPF to the second UPF.
  • the target EES performs forwarding, and the forwarding rule also carries the tunnel information of the first UPF.
  • the first core network device acquires the tunnel information of the second UPF network element according to the target routing information, including: if the target routing information is not in the service of the first core network device within the range, the first core network device determines a second core network device according to the target routing information; the first core network device sends a second message to the second core network device, and the second message uses requesting to establish a UPF tunnel between the first UPF and the second UPF, the second message carries the target routing information and the tunnel information of the first UPF network element; the first core network device Receive a third message sent by the second core network device, where the third message carries address information of the second UPF.
  • the SMF can obtain the second UPF within the service range of other SMFs.
  • the present application provides a communication device, which may be a communication device, or a chip or a chipset in the communication device, wherein the communication device may be an ECS or a terminal device or an EAS or EES or a core network device Such as SMF network element.
  • the apparatus may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiver unit may be a transceiver; the apparatus may further include a storage module, which may be a memory; the storage module is used for storing instructions, and the processing unit Execute the instructions stored in the storage module, so that the ECS performs the corresponding functions of the first aspect or the seventh aspect, or the processing unit executes the instructions stored in the storage module, so that the terminal device executes the second aspect or the seventh aspect.
  • the processing unit executes the instructions stored in the storage module, so that the EAS performs the corresponding functions in the third aspect above, or the processing unit executes the storage module.
  • the instructions stored in the module so that the EES performs the corresponding functions in the fourth aspect or the fifth aspect, or the processing unit executes the instructions stored in the storage module, so that the core network device performs the corresponding functions in the ninth aspect or the tenth aspect. .
  • the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module, the The processing unit executes the instructions stored in the storage module, so that the ECS performs the corresponding function of the first aspect or the seventh aspect, or the processing unit executes the instructions stored in the storage module, so that the terminal device executes the second aspect. Or the corresponding function of the sixth aspect or the eighth aspect, or, the processing unit executes the instructions stored in the storage module, so that the EAS performs the corresponding function in the third aspect, or the processing unit executes the storage module.
  • the storage module may be a storage module (eg, register, cache, etc.) within the chip or chipset, or may be a storage module (eg, read-only memory, random access memory, etc.) located outside the chip or chipset within the base station memory, etc.).
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of interface, and the other device may be a network device.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the first aspect or each possible design of the first aspect or the method described in the seventh aspect or each possible design of the seventh aspect.
  • the apparatus may also 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, the processor can implement the first aspect or the method described in each possible design of the first aspect or the seventh aspect or
  • the seventh aspect describes the method of each possible design.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of interface, and other devices may be terminal devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the second aspect or each possible design of the second aspect, the method described in the sixth aspect or each possible design of the sixth aspect, the eighth aspect or the eighth aspect Aspects of each possible design description method.
  • the apparatus may also 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, the method described in the second aspect or each possible design of the second aspect, the sixth aspect or the sixth aspect can be implemented.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of interface, and other devices may be terminal devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the third aspect or each possible design of the third aspect.
  • the apparatus may also 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, the method described in the third aspect or each possible design of the third aspect can be implemented.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of interface, and other devices may be terminal devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the fourth aspect or each possible design of the fourth aspect and the method described in the fifth aspect or each possible design of the fifth aspect.
  • the apparatus may also 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, the method described in the fourth aspect or each possible design of the fourth aspect, the fifth aspect or the fourth aspect can be implemented. Five aspects of each possible design description method.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of interface, and other devices may be terminal devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the ninth aspect or each possible design of the ninth aspect, and the tenth aspect or the method described in each possible design of the tenth aspect.
  • the apparatus may also 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, the method described in the ninth aspect or each possible design of the ninth aspect, the tenth aspect or the third aspect can be implemented. Ten aspects of each possible design description method.
  • the embodiments of the present application further provide a computer-readable storage medium, where computer-readable instructions are stored in the computer-readable storage medium, and when the computer-readable instructions are executed on a computer, such as The method described in any one of the first to tenth aspects and each possible design of any one of the first to tenth aspects is performed.
  • an embodiment of the present application provides a chip system, where the chip system includes a processor, and may further include a memory, for implementing any one of the foregoing first to tenth aspects, and the first to sixth aspects The method of each possible design of any of the ten aspects.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a nineteenth aspect provides a computer program product comprising instructions that, when run on a computer, cause any of the above-mentioned first to tenth aspects, and any of the first to tenth aspects The methods described in each possible design of the aspect are performed.
  • FIG. 1 is a schematic diagram of the architecture of a MEC network according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the architecture of a communication network provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a migration application context provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an enhanced EES registration process and an EES discovery process provided by an embodiment of the present application
  • FIG. 5 is a schematic diagram of establishing a UPF tunnel according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of an application context migration provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of establishing a UPF tunnel according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and the words “first” and “second” are not necessarily different.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • Edge data network an understanding is that EDN only corresponds to one data network, and is a special local data network (local, data network, DN), including edge enabling functions, which can use data network connection.
  • the input identifier (DN accEES identifier, DNAI) and the data network name (DNN) identifier are the logical concepts of the network.
  • EDN is the peer-to-peer concept of central cloud, which can be understood as a local data center (geographical location concept), which can be identified by DNAI and can contain multiple local data networks (local DN). Taking the "App Market” application in Huawei's mobile phone as an example, a central cloud of "App Market” can be set up at the Shenzhen headquarters.
  • Beijing and Shanghai can respectively set up a local EDN network of "application market”. Subsequently, users in Beijing can obtain application services through the local EDN network of the "App Market” set up in Beijing. On the other hand, users in Shanghai can obtain application services through the local EDN network of the "application market” set up in Shanghai.
  • Each EDN network provides application services for each user nearby, which can provide users with a higher-quality network experience.
  • An application instance or edge application an application deployed in the EDN is called an application instance. Specifically, it refers to a server application, such as social media software, augmented reality (AR), virtual reality (virtual reality, VR) deployed in the EDN instance (instance).
  • An application can deploy one or more edge application servers (EAS) in one or more EDNs. EAS deployed and running in different EDNs can be considered as different EASs of an application, and they can share a domain name. One anycast IP address may be used, or different IP addresses may be used, which is not limited.
  • EAS is also called application instance, edge application instance, MEC application server, EAS function, etc.
  • the application client is the peer entity of the EAS on the terminal device side. AC is used by application users to obtain application services from EAS.
  • the AC is a client program applied on the terminal side.
  • the AC can connect to the EAS on the central cloud to obtain application services, or connect to the EAS deployed and run in one or more EDNs to obtain service applications.
  • the edge enabler server can provide enabling capabilities for instances deployed in EDN, and can better support the deployment of applications in MEC.
  • EES can support registration of edge applications, authentication and authentication of terminal devices, and provide IP address information of application instances for terminal devices. Further, the EES can also support obtaining the identification and IP address information of the application instance, and sending the identification and IP address information of the application instance to the ECS.
  • EES is deployed in EDN.
  • an EAS is registered with an EES, or the information of an EAS is configured on an EES through a management system, the EES is called the EES associated with the EAS, and the EES can control, manage, register or configure the EES associated with the EES.
  • the edge enabler client is the peer entity of the EES on the terminal device side.
  • EEC is used to register EEC information and application client information with EES, perform security authentication and authentication, obtain EAS IP address from EES, and provide edge computing enabling capabilities to application clients, such as EAS discovery service, EAS IP address The address is returned to the application client.
  • the edge configuration server is responsible for EDN configuration, such as providing EES information to terminal devices.
  • the information of the application instance can also be provided to the terminal device, and the information of the application instance can be obtained by interacting with the DNS of the application. Further, information such as application instances and IP addresses can also be obtained and saved from other functional entities.
  • the EEC can obtain the address of the ECS in any of the following five ways:
  • ECS address of ECS can be pre-configured in EEC
  • the AC can configure the address of the ECS to the EEC
  • the user specifies an ECS on the terminal device, that is, the user selects an ECS in the ECS list by operating the terminal device, and the terminal device can indicate the ECS to the EEC;
  • the EEC can determine the ECS address according to the public land mobile network (PLMN) ID;
  • the 5G core network (5G core, 5GC) configures the ECS address to the UE, and the UE can send the ECS address received through the 5GC to the EEC.
  • the network architecture defined in the 3GPP standard TS 23.501 is as follows, including: a radio access network (radio accEES network, RAN) and a core network.
  • a radio access network radio accEES network, RAN
  • RAN radio access network
  • Different access network devices can be connected through the Xn interface, and the access network device and the core network can be connected through the NG interface.
  • the RAN is used to implement functions related to wireless access.
  • the RAN can provide functions such as wireless resource management, quality of service management, data encryption and compression for terminal equipment.
  • the access network equipment may include the following types:
  • the next generation nodeB provides terminal equipment with protocols and functions of the new radio (new radio, NR) control plane and/or user plane, and accesses the core network.
  • new radio new radio
  • NR new radio
  • 5G core network 5th generation core, 5GC
  • ng-eNB Next generation evolved Node B
  • E-UTRA evolved universal terrestrial radio accEES
  • the access network equipment may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), the functions of the original access network equipment can be split, and the original access network equipment can be split. Some functions of the device are placed in the CU, and the rest of the functions are deployed in the DU. Multiple DUs share one CU, which saves costs and facilitates network expansion.
  • the CU and DU can be connected through the FI interface.
  • the CU can be connected to the core network on behalf of the access network device through the NG interface, and the CU can also be connected to other access network devices on behalf of the access network device through the Xn interface.
  • the functions of CU can also be divided into:
  • CU-CP Central unit-control plane: mainly includes the RRC layer in the CU and the control plane in the PDCP layer;
  • CU-UP Central unit-user plane: mainly includes the SDAP layer in the CU and the user plane in the PDCP layer.
  • the core network is mainly used to manage the terminal equipment and provide the function of communicating with the external network.
  • Core network equipment may include one or more of the following network elements:
  • UPF network element mainly responsible for forwarding and receiving user data.
  • the UPF network element can receive user data from the data network (DN) and transmit it to the terminal equipment through the access network equipment; in the uplink transmission, the UPF network element can receive the user data from the terminal equipment through the access network equipment User data, forward the user data to the DN.
  • the transmission resources and scheduling functions in the UPF network element that provide services for the terminal equipment may be managed and controlled by the SMF network element.
  • Access and mobility management function (accEES and mobility management function, AMF) network element: mainly responsible for the mobility management in the mobile network, such as user location update, user registration network, user switching, etc.
  • Session management function mainly responsible for session management in the mobile network, such as session establishment, modification, release. Specific functions include assigning IP addresses to users and selecting UPF network elements that provide packet forwarding functions.
  • PCF Policy control function
  • Application function (AF) network element mainly supports 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.
  • Unified data management (UDM) network element It is mainly used for generating authentication credential, user identification processing (such as storing and managing user permanent identity, etc.), access authorization control and contract data management, etc.
  • the network elements in the above-mentioned core network may have different names.
  • the fifth-generation mobile communication system is used as an example for description, which is not intended to limit the present application.
  • the network architecture shown in FIG. 2 may further include: terminal equipment.
  • Terminal equipment which can be referred to as terminal for short, is a device with wireless transceiver functions. Terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); In the air (eg on airplanes, balloons and satellites, etc.).
  • the terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, and a wireless terminal in industrial control (industrial control).
  • VR virtual reality
  • AR augmented reality
  • the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (sEESion initiation protocol, SIP) phone, a wireless local loop (wirelEES local loop, WLL) station, a personal digital assistant (PDA), a wireless communication functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future fifth generation (5G) networks or future evolved public land mobile communication networks ( Terminal equipment in public land mobile network, PLMN), etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • Terminal equipment may also sometimes 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 equipment, wireless communication equipment, UE proxy or UE device, etc.
  • Terminal devices can also be stationary or mobile. This embodiment of the present application does not limit this.
  • the network architecture shown in FIG. 2 may further include: a data network (DN).
  • a DN may be a network that provides data transmission services to users.
  • the DN may be an IP multi-media service network or an internetwork.
  • Multiple application servers can be included in the DN.
  • the terminal device may establish a protocol data unit (protocol data unit, PDU) session from the terminal device to the DN to access the DN.
  • PDU protocol data unit
  • a data network may have one or more local data networks (local data network, Local DN), and these local data networks are data network access points (accEES points) close to the user attachment point (point of attachment).
  • the ECS, EES, and EAS in the architecture shown in the foregoing FIG. 1 may be configured in the foregoing one or more DNs.
  • the above DN includes one or more EDNs, and each EDN includes EES and EAS, and may also include ECS.
  • the above DN may also be configured with an application center cloud platform.
  • the application center cloud platform and the above EAS can be considered as equivalent concepts.
  • Each EAS can provide application services to users nearby, and the application center cloud platform can provide application services to all users.
  • the application center cloud platform can also be called the central cloud platform. In the following description, the central cloud platform is used as an example for description.
  • a central cloud platform about “Huawei Music” can be set up at the Shenzhen headquarters, and the central cloud platform can serve as the "Huawei Music” for global users.
  • the client provides the service.
  • Huawei Music's EAS can be deployed on the EDN networks in Beijing and Shanghai respectively.
  • users in Beijing can access the EAS of Huawei Music in the EDN network corresponding to Beijing to obtain Huawei Music services.
  • Users in Shanghai can access the EAS of Huawei Music in the corresponding EDN network in Shanghai to obtain Huawei Music services.
  • the same application is often deployed in multiple EDNs at the same time.
  • Servers of the same application deployed in different EDNs can provide the same services and have functional equivalence.
  • the terminal device accesses the network, it will select the EAS in the nearest EDN to execute the service. Due to the mobility of the terminal equipment, the EAS selected by the terminal equipment may not be able to continue to provide services for the terminal equipment. In order to meet the service continuity requirements of the application, the network selects a new EAS for the terminal equipment to continue the service.
  • the connection of the terminal equipment will be interrupted.
  • the application context in the source EAS can be migrated to Target EAS, this process is called application migration or application context migration.
  • the source EAS and the target EAS may belong to different EDNs, and there may be isolation between the two EDNs/firewalls that cannot communicate with each other, so the application context in the source EAS may not be migrated to the target EAS. For example, as shown in FIG. 3 , as the UE moves, the UE switches from EDN#1 to EDN#2. Since EDN#1 and EDN#2 cannot communicate, the application context of the UE cannot be migrated to EDN#2.
  • the embodiments of the present application provide a communication method and apparatus.
  • an EAS that can communicate with a source EAS as a target EAS for application context migration
  • the success rate of migrating application contexts can be improved.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • the EES registration and EES selection processes can be enhanced, so that the ECS side can obtain the topological connection relationship of the EES, or use the edge management system (used to manage the resources of the edge data network and manage the EES) to connect the EES topological relationship. It is configured on the ECS, so that other EESs connected to the EES can be determined, and then the target EESs that are communicatively connected with the source EES can be fed back during the application context migration process. For details, refer to Embodiment 1 to Embodiment 3 of the present application.
  • 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, and the topology connection information may indicate the information of other EESs that have communication connections with the EES.
  • 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 may indicate the information of other EESs that have communication connections with the EES.
  • Enhancing the EES selection process may include indicating latency or path requirements for migration when triggering application migration.
  • the service provisioning request (service provisioning request) or the application context relocation request (ACR request) or the complete application context relocation request (full ACR request) can be enhanced. , so that the service provisioning request or ACR request or full ACR request can indicate the communication requirement for the target EES.
  • ACR application context relocation
  • the EAS discovery (EAS discover) requested by the EAS may also indicate the communication requirement for the target EES.
  • EAS discover the EAS discovery requested by the EAS may also indicate the communication requirement for the target EES.
  • the communication requirement for the target EES may also be indicated in the message of the EES requesting to discover the EES.
  • Embodiment 3 of the present application refers to Embodiment 3 of the present application.
  • the configuration information of EES#2 may carry the topology connection information of EES2.
  • the service configuration request sent by EEC or the EES acquisition request (EES retrieve request) sent by EES#1 may indicate the communication requirements for the target EES.
  • the EES registration and EAS selection processes can be enhanced, so that the target EES can obtain the communication requirements for the target EAS, so as to determine whether it has a communication connection with the source EES that meets the communication requirements.
  • 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, and the topology connection information may indicate information of other EESs that have communication connections with the EES.
  • the enhanced EAS selection procedure may include: a message for discovering the EAS sent by the terminal device to the target EES may indicate a communication requirement for the target EAS. For details, refer to Embodiment 4 of the present application.
  • the EES registration and EES selection processes can be enhanced, so that the EEC can obtain the topology connection information of the EES, so that the EES that meets the communication requirements for the target EES can be selected as the target EES.
  • 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, and the topology connection information may indicate information of other EESs that have communication connections with the EES.
  • the enhanced EES selection process may include: the ECS may send the EES topology connection information to the EEC in the service provisioning response message. For details, refer to Embodiment 5 of the present application.
  • the topological connection information of the EES may be obtained through the SMF, so that the DNAI that meets the requirements may be selected.
  • the DNAI that meets the requirements may be selected.
  • the present application also provides a method for establishing a UPF tunnel between two UPFs connected to two EESs respectively.
  • a method for establishing a UPF tunnel between two UPFs connected to two EESs respectively For details, refer to Embodiment 7 of the present application. For example, as shown in Figure 5.
  • the “communication connection between the source EES and the target EES” described in the embodiments of this application may also be referred to as “the communication connection for application context migration” or “the communication connection for migrating application context”.
  • “Communication connection between target EES”, “communication connection for application context migration”, and “communication connection for migration of application context” can be equivalently replaced with each other.
  • connection requirements requirements for communication connections
  • path requirements requirements for communication connections
  • Communication requirements requirements for communication connections
  • connection requirements requirements for communication connections
  • path requirements requirements for communication connections
  • Communication requirements requirements for communication connections
  • Embodiment 1 of the present application may be applied to a scenario in which a terminal device (eg, an EEC in the terminal device) initiates application context migration (application migration).
  • a terminal device eg, an EEC in the terminal device
  • application context migration application migration
  • the terminal device sends a request message to the ECS, where the request message is used to acquire the EES, and the request message may indicate a communication requirement for the target EES.
  • the ECS can feed back the EES that meets the communication requirement to the terminal device.
  • Embodiment 1 it is a specific process of Embodiment 1, and the process may include, but is not limited to, an EES registration process, a terminal device initial access EAS process, and an application context migration process.
  • the registration process of EES can be as follows:
  • the first EES sends a registration request to the ECS respectively, where the registration request may carry configuration information of the first EES.
  • the configuration information of the first EES includes information of a second EES that supports communication with the first EES.
  • the configuration information of the first EES may include topology connection information of the first EES (which may also be referred to as connection-allowing information or EES-connection-allowing information), and the topology connection information may indicate that the first EES supports communication with the first EES.
  • the topology connection information of the first EES may include an edge computing service provider (edge computing service provider, ECSP) provider identification list, or an EES identification list, or an endpoint information list.
  • the list of ECSP provider identifiers may include the ECSP provider identifiers of the second EES that support communication with the first EES.
  • the list of EES identities may include identities of second EESs that support communication with the first EES.
  • the endpoint information list may include endpoint information of a second EES that supports communicating with the first EES.
  • the endpoint information may be a group of IP addresses/fully qualified domain names (fully qualified domain names, FQDN)/uniform resource identifiers Identifier (uniform resource identifier, URI) / uniform resource locator (uniform resource locator, URL) and so on.
  • the first EES may include one or more EESs, and the first EES may include EES 1 and EES 2.
  • the second EES may include one or more EESs.
  • the topology connection information may further include information on the communication connection between the first EES and the second EES.
  • the information of the communication connection between the first EES and the second EES may include at least one item of the following information: the type of the communication connection, and the quality parameter of the communication connection.
  • the type of the communication connection between the first EES and the second EES may include, but is not limited to, an IP connection, a dedicated line connection, a UPF tunnel connection, and the like.
  • the leased line connection may be an IP-based dedicated network connection, and the leased line connection may have: a short network path (for example, the leased line connection may be a one-hop IP, or there is no IP router or the number of IP routers between two endpoints of the leased line connection Rarely), exclusive resources on the path, and high security features.
  • the communication quality of the private line connection is higher than that of the general IP routing connection.
  • the quality parameters of the communication connection between the first EES and the second EES may include, but are not limited to, bandwidth, delay, jitter, and the like.
  • the quality of the communication connection between the first EES and the second EES may be a statistical value within a period of time, a real-time value, or a predicted value.
  • the configuration information of the first EES may further include at least one of the following information: the first EES identification (identification, ID), the endpoint (Endpoint) information of the first EES, the EAS registered with the first EES list of identities, etc.
  • the configuration information of the first EES further includes the security credentials of the first EES.
  • the configuration information of the first EES may further include the valid time of the registration. In order to maintain the validity of the registration, the first EES may send a registration update request to the ECS before the valid time of the registration expires. If the ECS does not receive the registration update request within the valid time of the registration, the ECS may consider that the first EES has been deregistered.
  • the configuration information of the first EES may be as shown in Table 1.
  • the ECS saves the configuration information of the first EES.
  • this registration process is an optional step.
  • the registration process can also be used alone as an embodiment.
  • the registration process of the EES and the process of the terminal device initially accessing the EAS may not be performed continuously in time, that is, the process of the terminal device initially accessing the EAS may be performed at any time interval after the execution of S602.
  • the ECS can also obtain the topology connection information of the EES in other ways, such as obtaining the topology connection information of the EES through the edge management system, or obtaining the topology connection information of the EDN where the EES is located through the edge management system. connection communication, it can be considered that the EES deployed in it also shares the topology connection information of the EDN.
  • the process of the terminal equipment initially accessing the EAS may specifically include:
  • the terminal device (for example, the EEC of the terminal device) sends a service configuration request to the ECS, where the request message is used to discover the EES.
  • the request message may include the security credentials of the EEC, the identity of the terminal device such as a generic public subscription identifier (GPSI), etc., connection information, the location of the terminal, and the AC configuration information (AC profile) in the terminal device, etc. .
  • the ECS performs authorization check on the terminal device.
  • ECS can select one or more EESs according to the service configuration request.
  • the ECS can select the EES that includes the location of the terminal device in the service area, the EES that matches the EAS ID of the AC profile in the registered EAS list, and the like.
  • the ECS sends a response message of the service configuration request to the terminal device, where the response message carries the information of the discovered one or more EESs.
  • the terminal device (for example, the EEC of the terminal device) sends an EAS discovery request message to the EES 1 in the above-mentioned one or more EESs, where the EAS discovery request message may carry an EAS discovery filter, and the EAS discovery filter may include filtering parameters of the EAS .
  • the EAS discovery filter can be as shown in Table 2.
  • EES 1 sends a response message of the EAS discovery request message to the terminal device, where the response message carries the first EAS, wherein the first EAS includes one or more EASs that satisfy the EAS discovery filter.
  • the terminal device selects EAS 1 in the first EAS to connect.
  • the EEC of the terminal device can hand over the first EAS to the AC through inter-layer interaction, and the AC selects EAS 1 in the first EAS and connects to the EAS 1 to perform service interaction at the application layer.
  • process of initially accessing the EAS by the terminal device is an optional step.
  • the process of application context migration can specifically include:
  • the terminal device determines that an event that triggers application context migration occurs.
  • the terminal device detects the occurrence of an event triggering application context migration, or the EES 1 detects the occurrence of an event triggering application context migration and notifies the terminal device.
  • the events that trigger application context migration may include, but are not limited to: the terminal device moves out of the service area of the current EAS (that is, EAS 1), or the EEC receives a message of a new session of the SMF, or the EEC receives a new IP address. prefix, etc.
  • step S609 is an optional step.
  • the terminal device (for example, the EEC of the terminal device) sends a service configuration request to the ECS, where the request message is used to discover the EES, and the service configuration request may indicate the communication requirement for the target EES.
  • the service configuration request may indicate that the communication requirement for the target EES may be explicitly carried in the service configuration request message with specific communication requirement parameters, or may also be an implicit indication, that is, the service configuration request to the target EES Index or pointer or handle to the configuration file to which the communication requirement belongs.
  • the communication requirement for the target EES may include at least one of the following information: the target EES supports communication with the source EES (ie EES 1), the type of communication connection between the source EES and the target EES, the source EES Quality parameter of the communication connection with the target EES.
  • the communication requirements for the target EES can be included in the application client profile (AC profile), or as a service key indicator information (service KPI) of the EAS.
  • the communication requirements for the target EES may also include the completion time of the ACR.
  • the types of communication connections between EESs may include, but are not limited to, IP connections, dedicated line connections, UPF tunnel connections, and the like.
  • the quality parameters of the communication connection may include, but are not limited to, bandwidth, delay, jitter, and the like.
  • the delay may be an acceptable migration duration, a desired migration duration, or the like.
  • the quality of the communication connection between the EESs may be a statistical value within a period of time, a real-time value, or a predicted value.
  • the target EES supports communication with the source EES may be indicated implicitly, 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, The quality parameter of the communication connection between the source EES and the target EES may implicitly indicate that the target EES needs to support communication with the source EES.
  • the communication requirements for the target EES may be included in the application client profile (AC profile) or the edge application server profile (EAS profile), then the The message can carry application client identification (AC ID) or edge application server identification (EAS ID) or edge application server endpoint information (EAS endpoint) (which can be in the format of FQDN, IP address, URI, URL, etc.), and ECS can use the above
  • the information refers to the specific parameter information of the "communication requirements for the target EES" obtained locally in the ECS or in the EES or edge management system.
  • the request message may also carry information of the source EES, such as the identity of the source EES or endpoint information and the like.
  • the source EES is an EES connected to the EEC and provides edge services for the EEC
  • the source EES is an EES registered by the source EAS
  • the source EES can provide edge services for the EAS, where the source EAS is an application to be performed on the terminal device The EAS to which the application client of the context migration is connected.
  • the request message sent by the terminal device may indicate that the target EES is used for application context migration, or the request message may indicate that the discovery EES is for performing application context migration with the source EES.
  • the request message may display carrying indication information, where the indication information is used to indicate that the target EES is used for application context migration, or that the discovery of the EES is to perform application context migration with the source EES.
  • the request message may implicitly indicate that the target EES is used for application context migration or that the discovery EES is to perform application context migration with the source EES.
  • the formula indicates that the target EES is used for application context transfer or that the discovery EES is to perform application context transfer with the source EES.
  • the request message may also include the security credentials of the EEC, the identification of the terminal device such as GPSI, etc., connection information, location and AC profile, etc.
  • the ECS sends a response message to the terminal device for the service configuration request, where the response message carries information of a third EES, where the third EES includes one or more EESs that meet the communication requirement.
  • the terminal device (for example, the EEC of the terminal device) sends an EAS discovery request message to EES 2 in the third EES, where the EAS discovery request message may carry an EAS discovery filter, and the EAS discovery filter may include EAS filtering parameters.
  • the ECS may also trigger the core network device 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 (ie, EES 2). Please refer to the seventh embodiment of the present application.
  • S612 is similar to S606.
  • step S606 is similar to the above-mentioned step S606, which will not be repeated here.
  • EES 2 sends a response message of the EAS discovery request message to the terminal device, where the response message carries a second EAS, where the second EAS includes one or more EASs that satisfy the EAS discovery filter.
  • the terminal device selects EAS 2 in the second EAS as the target EAS.
  • S614 is similar to S608. For details, please refer to the above-mentioned step S608, which will not be repeated here.
  • the terminal device (for example, the AC of the terminal device) triggers the transfer of the application context from EAS 1 to EAS 2.
  • the terminal device switches the application connection from EAS 1 to EAS 2, and performs application layer logic interaction with EAS 2.
  • steps S612 to S616 are all optional steps.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the second embodiment of the present application can be applied to the scenario of application context migration (application migration) initiated by the source EAS.
  • Embodiment 2 it is a specific process of Embodiment 2, and the process may include, but is not limited to, an EES registration process, a terminal device initial access EAS process, and an application context migration process.
  • the registration process of the EES may refer to the registration process described in steps S601 to S602 in the embodiment, which will not be repeated here, and the registration process of the EES is an optional step.
  • the process of application context migration can specifically include:
  • EAS 1 detects the occurrence of an event that triggers application context migration.
  • the events triggering application context migration may include, but are not limited to, the terminal device moving out of the service area of the current EAS, or the EEC receiving a message of a new session of the SMF, or the EEC receiving a new IP prefix, and so on.
  • EAS 1 sends a first EAS discovery request to EES 1, the first EAS discovery request is used to obtain the target EAS of application context migration, and the first EAS discovery request indicates the communication requirement of application context migration (or may also be referred to as the target EAS for application context migration). EAS/EES communication requirements).
  • the first EAS discovery request may indicate that the communication requirement for application context migration may be explicitly carried in the first EAS discovery request message with specific communication requirement parameters, or may be an implicit indication, that is, the first EAS discovery request
  • the EAS discovery request message carries the index or pointer or handle of the configuration file to which the communication requirement for the target EES belongs.
  • the first EAS discovery request carries the parameters of the specific communication requirement of the application context migration.
  • the communication requirement of application context migration may be included in the application client profile (AC profile) or the edge application server profile (EAS profile), then the first EAS discovery request message It can carry application client identification (AC ID) or edge application server identification (EAS ID) or 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 The index obtains the specific parameter information of "communication requirements for application context migration" in the EES local or edge management system.
  • the first EAS discovery request may also carry the identifier of EAS 1 and the EAS discovery filter.
  • EAS discovery filter reference may be made to the EAS discovery filter described in S606 in the first embodiment above.
  • the communication requirements of application context migration can also be included in the EAS discovery filter.
  • the first EAS discovery request may also carry the target DNAI.
  • the communication requirement of application context migration may include at least one of the following information: target EES supports communication with the source EES, type of communication connection for migration of the application context, and quality parameters of the communication connection for migration of the application context.
  • the communication requirements for the target EES may also include the completion time of the ACR.
  • the types of communication connections for migrating the application context may include, but are not limited to, IP connections, dedicated line connections, UPF tunnel connections, and the like.
  • the quality parameters of the communication connection for migrating the application context may include, but are not limited to, bandwidth, delay, jitter, and the like.
  • the delay may be an acceptable migration duration, a desired migration duration, or the like.
  • the quality of the communication connection between the EESs may be a statistical value within a period of time, a real-time value, or a predicted value.
  • the target EES supports communication with the source EES may be implicitly indicated, for example, when the communication requirements for migrating the application context include the type of communication connection for migrating the application context, the When communicating the quality parameter of the connection, it may be implicitly indicated that the target EES needs to support communication with the source EES.
  • steps S709 and S710 are both optional steps.
  • the EES 1 sends a request message to the ECS, where the request message is used to obtain the target EES for application context migration, and the request message indicates the communication requirement for the target EES.
  • the specific parameters of the communication requirements of the target EES may be equivalent to the communication requirements of the application context migration sent by the EAS, or may be the specific parameters of the communication requirements of the new target EES generated by the EES 1 according to the communication requirements of the application context migration.
  • the request message is similar to the service configuration request described in S610 in Embodiment 1 of the present application. For details, please refer to the relevant description in Step S610 in Embodiment 1 of the present application, which will not be repeated here.
  • the ECS sends a response message of the request message to EES 1, where the response message carries the information of the second EES, and the second EES may include one or more EESs that meet the communication requirement.
  • EES 1 sends a second EAS discovery request message to EES 2 in the above-mentioned second EES, where the second EAS discovery request message may carry an EAS discovery filter, and the EAS discovery filter may include filtering parameters of the EAS.
  • the EAS discovery filter may be the EAS discovery filter carried in the first EAS discovery request.
  • the ECS may also trigger the core network device to establish a UPF tunnel between the UPF network element connected to the source EES (ie EES 1) and the UPF network element connected to the target EES (ie EES 2). Please refer to the seventh embodiment of the present application.
  • EES 2 sends a response message of the second EAS discovery request message to EES 1, where the response message carries the information of the second EAS, and the second EAS includes one or more EASs that meet the requirements.
  • EES 1 sends a response message of the first EAS discovery request message to EAS 1, where the response message carries the second EAS.
  • EAS 1 transmits the application context from EAS 1 to EAS 2.
  • EAS 2 is the target EAS selected by EAS 1 from the above-mentioned second EAS.
  • the terminal device switches the application connection from EAS 1 to EAS 2, and performs application layer logic interaction with EAS 2.
  • steps S713 to S717 are all optional steps.
  • Embodiment 2 it is possible to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection cannot meet the target EES for application context migration during application context switching, thereby ensuring the business continuity of the application. sex.
  • the process may include but not limited to the registration process of the EES, the process of the terminal device initially accessing the EAS, and the process of application context migration.
  • the registration process of the EES may refer to the registration process described in steps S601 to S602 in the embodiment, which will not be repeated here, and the registration process of the EES is an optional step.
  • the EAS 1 sends a first message to the EES 1, where the first message is used to request the EES 1 to manage the migration of the application context of the terminal device, and the first message indicates the communication requirement for the migration of the application context.
  • the first request message may be a full ACR request.
  • the EES 1 manages the migration of the application context of the terminal device, which may include: the EES 1 is responsible for triggering event monitoring, the discovery of the target EAS, the transmission (or transfer) of the application context from the source EAS to the target EAS, and the monitoring of the EAS and the target EAS. Notification of EEC application context migration progress (such as selected target EAS, application context migration completion), and routes affecting the user plane of the network.
  • EES 1 detects the occurrence of an event that triggers application context migration.
  • the events triggering application context migration may include, but are not limited to, the terminal device moving out of the service area of the current EAS, or the EEC receiving a message of a new session of the SMF, or the EEC receiving a new IP prefix, and so on.
  • steps S809 to S810 are all optional steps.
  • EES 1 sends the same first notification message to EAS 1, where the first notification message 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 start.
  • EES 1 transfers the application context from EAS 1 to EAS 2.
  • the application context can be stored in a shared area accessible by both EES 1 and EAS 1.
  • EES 1 sends a second notification message to the terminal device, where 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 completed.
  • the second notification message may further include EAS2 information.
  • the terminal device switches the application connection from EAS 1 to EAS 2, and performs application layer logic interaction with EAS 2.
  • steps S813 to S818 are all optional steps.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • Embodiment 4 of the present application may be applied to a scenario where a terminal device (eg, an EEC in the terminal device) initiates application context migration (application migration).
  • a terminal device eg, an EEC in the terminal device
  • application context migration application migration
  • the process may include, but is not limited to, an EES registration process, a terminal device initial access EAS process, and an application context migration process.
  • the registration process of the EES may refer to the registration process described in steps S601 to S602 in the embodiment, which will not be repeated here, and the registration process of the EES is an optional step.
  • the process of application context migration can specifically include:
  • S909 to S911 are similar to S609 to S611 of the first embodiment, except that the service configuration request in S610 of the first embodiment indicates the communication requirements for the target EES, while the service configuration request in S910 of the fourth embodiment communication needs.
  • the EES included in the second EES fed back by the ECS in S611 of the first embodiment all meet the communication requirement, while the second EES fed back by the ECS in the fourth embodiment may include EESs that do not meet the communication requirement.
  • the terminal device (for example, the EEC of the terminal device) sends an EAS discovery request message to the EES 2 in the second EES, where the EAS discovery request message may indicate the requirement of application context migration.
  • the request message also carries ACR indication information, where the indication information is used to indicate that the request message is used to discover that the EAS will be used for application context migration, or to indicate that the request message requests the discovered EAS to be used for application context migration.
  • the EAS discovery request message may carry an EAS discovery filter.
  • EAS discovery filter reference may be made to the relevant description of the EAS discovery filter in S606 of the first embodiment, which will not be repeated here.
  • the specific parameters of the requirement of application context migration may be included in the EAS discovery filter.
  • EES 2 judges whether and EES 1 exists to meet the requirement of context migration of the application. If no, go to step S914; if yes, go to step S915.
  • the EES 2 may also send a request message to the ECS, where the request message carries the information of the EES 1, the information of the EES 2, and the communication requirements between the source EES and the target EES. Therefore, the ECS can determine whether there is a communication connection between the EES 2 and the EES 1 that meets the communication requirement.
  • EES 2 sends a failure indication to the terminal device.
  • the failure indication may indicate that there is no EAS that meets the communication requirement, or the communication requirement cannot be met.
  • the failure indication may also indicate which one of the communication requirements is not met. For example, it may indicate that communication with the source EES is not supported, that there is no communication connection type required for communication with the source EES, and The communication connection between the source EESs does not meet the communication quality required by the communication requirement, and so on.
  • EES 2 may 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 ECS may 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.
  • S914 is an optional step.
  • EES 1 sends a response message of the EAS discovery request message to the terminal device, where the response message carries the information of the second EAS, and the second EAS includes one or more EASs that meet the communication requirement.
  • the terminal device selects EAS 2 in the second EAS as the target EAS.
  • EAS 1 may be sent to EAS 2 by means of push, or it may be that EAS 2 may obtain the application context by means of pull.
  • EES 2 may send a first notification message to EAS 2, where the notification message may carry information of EAS 1.
  • the EAS 2 sends a second notification message to the EES 2, where the second notification message may indicate that the application context transmission is completed, or the application context is ready, and the user can be provided with services.
  • S918 can be an optional step.
  • EES 2 sends a third notification message to the terminal device.
  • the third notification message may be used to instruct the terminal device to switch the application connection to EAS 2.
  • the terminal device switches the application connection from EAS 1 to EAS 2, and performs application layer logic interaction with EAS 2.
  • the steps S906 to S920 are optional.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the fifth embodiment of the present application may be applied to a scenario of application context migration (application migration) initiated by a terminal device.
  • Embodiment 2 a specific process of Embodiment 2 is provided, and the process may include, but is not limited to, an EES registration process, a terminal device initial access EAS process, and an application context migration process.
  • the process of the terminal equipment initially accessing the EAS may specifically include:
  • the terminal device (for example, the EEC of the terminal device) sends a service configuration request to the ECS, where the request message is used to discover the EES.
  • the request message may include the security credentials of the EEC, the identification of the terminal device such as GPSI, etc., connection information, the location of the terminal device, and the AC profile in the terminal device.
  • the ECS performs authorization check on the terminal device.
  • the ECS may select the first EES according to the service configuration request, and the first EES includes one or more EESs. For example, the ECS may select an EES that includes the location of the terminal device in the service area, or select an EES that includes an EAS ID matching the AC profile in the registered EAS list.
  • the ECS sends a response message to the terminal device for the service configuration request, where the response message carries the information of the first EES and the connection topology information of the first EES.
  • connection topology information of the first EES For the connection topology information of the first EES, reference may be made to the description about the connection topology information of the first EES in S601 of the first embodiment.
  • process of initially accessing the EAS by the terminal device is an optional step.
  • the process of application context migration can specifically include:
  • the terminal device determines that an event that triggers application context migration occurs.
  • the terminal device detects the occurrence of an event triggering application context migration, or the EES 1 detects the occurrence of an event triggering application context migration and notifies the terminal device.
  • the events triggering application context migration may include, but are not limited to, the terminal device moving out of the service area of the current EAS, or the EEC receiving a message of a new session of the SMF, or the EEC receiving a new IP prefix, and so on.
  • S1009 is an optional step.
  • the terminal device (for example, the EEC of the terminal device) sends a service configuration request to the ECS, where the request message is used to discover the EES.
  • the ECS sends a response message to the terminal device for the service configuration request, where the response message carries information of a second EES, where the second EES includes one or more EESs.
  • the terminal device selects an EES 2 that meets the communication requirement in the second EES as the target EES.
  • S1013 to S1017 may be S612 to S616 of the above-mentioned first embodiment, and details are not repeated here.
  • Embodiment 5 it is possible to avoid selecting an EES that has no communication connection with the source EES, or the type of communication connection or the quality of the communication connection cannot meet the target EES for application context migration during application context switching, thereby ensuring the business continuity of the application. sex.
  • Embodiment 6 is a diagrammatic representation of Embodiment 6
  • Embodiment 6 may include but is not limited to:
  • the NRF network element or the UDR network element or the NEF network element receives the topology connection information of the first EES.
  • the topology connection information of the first EES reference may be made to the relevant description of the foregoing Embodiment 1, and details are not repeated here.
  • the NRF network element may receive a registration message of the first EES, where the registration message includes configuration information of the first EES, and the configuration information of the first EES includes topology connection information of the EES.
  • the UDR network element may obtain configuration information of the first EES from the first EES or ECS through a service parameter provisioning message, where the configuration information of the first EES includes topology connection information of the first EES.
  • the first EES or ECS sends the topology connection information of the first EES 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.
  • the NRF network element or the UDR network element or the NEF network element stores the topology connection information of the first EES.
  • steps S1101 and S1102 are optional steps.
  • the AF network element (for example, the source ESS) sends a request message to the PCF network element/NEF network element, where the request message is used to subscribe to the DNAI change event, and the request message includes the communication requirements for the target DNAI.
  • the communication requirement for the target DNAI includes at least one of the following pieces of information: the target EES corresponding to the target DNAI supports communication with the source EES, and between the source EES and the target EES corresponding to the target DNAI The type of the communication connection, the quality parameter of the communication connection between the source EES and the target EES corresponding to the target DNAI.
  • the communication requirement for the target DNAI may also include the completion time of the ACR.
  • the PCF network element sends the communication requirement to the SMF network element in the SMF session.
  • steps S1103 and S1104 are optional steps.
  • the SMF network element detects a first event, where the first event is used for the SMF network element to select a new DNAI.
  • the SMF network element determines a target DNAI, and the target EES corresponding to the target DNAI supports communication with the source EES.
  • the SMF network element may determine a target DNAI according to the communication requirement and the connection topology information of the first EES, and the EES corresponding to the target DNAI and the source EES corresponding to the source DNAI have a communication connection that meets the communication requirement.
  • the SMF network element can obtain the EES topology connection information from the UDR network element, or obtain the EES topology connection information from the NRF network element, or obtain the EES topology connection information from the NEF network element, or the SMF network element obtains the pre-configured configuration locally. Topological connection information of EES.
  • the SMF network element sends a notification message to the AF network element, where the notification message may carry the information of the target DNAI.
  • the notification message may also carry indication information, where the indication information is used to indicate that the EES corresponding to the target DNAI has a communication connection that meets the communication requirements with the source EES.
  • the network side selects the DNAI corresponding to the EES that has a communication connection with the source EES, thereby ensuring that the EES corresponding to the target DNAI has a communication connection with the source EES, and can avoid selecting an EES that has a communication connection with the source EES.
  • Embodiment 7 is a diagrammatic representation of Embodiment 7:
  • Embodiment 7 of the present application provides a method for establishing a UPF tunnel between two UPFs connected to two EESs respectively. As shown in FIG. 12 , the specific process of Embodiment 7 may include but is not limited to:
  • the source AF network element sends a first message to the first SMF network element, where the first message is used to request to establish a UPF tunnel between the source UPF network element and the target UPF network element.
  • the first request message may include target routing information, and the target routing information may be used to determine the target UPF network element.
  • the source UPF network element may be a UPF network element connected to the source EES.
  • the target UPF network element may be a UPF network element to which the target EES is connected.
  • the first message may be referred to as a transmission service request.
  • the first message may contain QoS requirements. It may also include the identification or IP address of the terminal device.
  • the first message may further include source routing information, and the source routing information may be used to determine the source UPF, or the source routing information may also be used to determine the sending end of the data.
  • the source AF network element may be the source EES.
  • step S1201 may also be performed by the target AF network element, such as the target EES. Alternatively, it can also be performed by ECS.
  • the AF network element may also send the first message to the PCF network element, and the PCF network element sends the information carried in the first message to the first SMF network element.
  • the AF may also send the first message to the PCF via the NEF.
  • the SMF network element may also determine the source routing information of the source UPF network element corresponding to the terminal device according to the identifier or IP address of the terminal device.
  • the first SMF network element searches for a second SMF network element that can serve the target routing information.
  • the first SMF network element can locally select the corresponding SMF network element.
  • the target UPF network element for the target routing information is within the service range of the first SMF network element, and the second SMF network element and the first SMF network element are the same SMF network element.
  • the first SMF network element may discover the second SMF network element serving the target routing information through the NRF network element.
  • the following S1203a to S1203e may be performed:
  • the first SMF network element may send a second message to the second SMF network element, where the second message is used to request to establish 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.
  • the second SMF network element selects a target UPF corresponding to the target routing information.
  • the second SMF may select the target UPF according to the target routing information.
  • the second SMF network element sends a third message to the selected target UPF network element, where the third message may include a forwarding rule, and the forwarding rule instructs the source UPF network element to forward the data from the source AF to the target UPF network element Forwarding, the forwarding rule carries the tunnel information of the source UPF network element. For example, if the forwarding rule includes the IP address and port number of the source AF, the source UPF instructs the source UPF to forward the data packet to the target UPF network element when the source address of the received data packet is the IP address and port number of the source AF.
  • the forwarding rule includes the IP address and port number of the source AF, and the IP address and port number of the destination AF, it indicates that the source UPF receives the data packet with the source address and port number of the source AF and the destination address as the AF.
  • the IP address and port number of the target AF's IP address and port number are forwarded to the target UPF network element.
  • the third message may further include the QOS requirement.
  • the target UPF network element sends a response message of the third message to the second SMF network element.
  • the second SMF network element sends a response message of the second message to the first SMF network element, where the response message includes tunnel information of the target UPF network element, and the tunnel information may include an IP address and a port number.
  • the first SMF network element sends a fourth message to the source UPF network element, where the fourth message includes the foregoing forwarding rule, and the forwarding rule instructs the target UPF network element to forward the data from the source UPF to the target AF network element
  • the forwarding rule carries the tunnel information of the target UPF network element. For example, if the forwarding rule contains the IP address and port number of the source UPF and the IP address and port number of the destination AF, it indicates that the destination UPF receives a packet whose source address is the source UPF's IP address and port number and whose destination address is AF. IP address and port number The data packets with the IP address and port number of the target AF are forwarded to the target UPF network element.
  • the source UPF network element sends a response message of the fourth message to the first SMF network element.
  • the first SMF/PCF sends a response message of the first message to the AF network element, where the response message may carry service interface information (for example, the IP address and port number of the source UPF), and the service interface information may be provided by the first SMF network element.
  • service interface information for example, the IP address and port number of the source UPF
  • the service interface information may be provided by the first SMF network element.
  • 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
  • the target UPF network element forwards the application context data to the target AF network element.
  • the source AF may be the source EES or the source EAS, and the target AF may be the corresponding target EES or the target EAS.
  • the source AF is an ECS
  • the source routing information is used to indicate the source EES
  • the target routing information is used to indicate the target EES.
  • the data sender can no longer be the source AF, but the data sender. It is no longer the IP address or port number of the source AF, but the IP address or port number of the originating end of the included data.
  • the communication apparatus 1300 may include a processing unit 1301 and a transceiver unit 1302 .
  • the transceiver unit 1302 is used for the communication device 1300 to perform communication transmission.
  • the processing unit 1301 is configured to perform actions other than the transceiving actions, such as determining actions, judging actions, selecting actions, controlling and managing actions of the communication device 1300, and so on.
  • the processing unit 1301 may also control the steps performed by the transceiving unit 1302 .
  • the communication apparatus 1300 may be the communication device in the above-mentioned embodiments, or the processor in the communication device, or the chip or chip system in the communication device, or a functional module in the communication device, etc., wherein the communication The device can be ECS or terminal device or EES or EAS or SMF and so on.
  • the communication apparatus 1300 when used to implement the functions of the ECS in the embodiments shown in FIG. 6 to FIG. 8 , it may specifically include:
  • the transceiver unit 1302 is configured to receive a first request message, the first request message is used to discover the EES, and the request message indicates the communication requirement for the target EES; the processing unit 1301 is configured to determine that at least one request satisfies the communication requirement The sending and receiving unit 1302 is further configured to: send a response message, where the response message carries the information of the at least one EES.
  • the transceiver unit 1302 is further configured to: before receiving the first request message, respectively receive configuration information of a first EES, where the first EES includes a source EES and/or the target EES, wherein , the configuration information of the first EES includes information of a second EES supporting communication with the first EES.
  • the configuration information of the first EES further includes information of a communication connection between the first EES and the second EES.
  • the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, the source EES and the source EES. Describe the quality parameters of the communication connection between the target EESs.
  • the first request message carries information of the source EES.
  • 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.
  • the communication apparatus 1300 When the communication apparatus 1300 is used to implement the functions of the terminal device in the embodiment shown in FIG. 6, it may specifically include: a transceiver unit 1302 for communicating with the ECS; a processing unit 1301 for using the transceiver unit 1301 1302 sends a first request message to the ECS, the first request message is used to discover the edge-enabled server EES, and the first request message indicates the communication requirement for the target EES; and, received by the transceiver unit 1302 A response message from the ECS, where the response message carries information of at least one EES that meets the communication requirement.
  • the communication requirement includes at least one of the following information: the target EES supports communication with the source EES, the type of communication connection between the source EES and the target EES, the source EES and the source EES. Describe the quality parameters of the communication connection between the target EESs.
  • the first request message carries information of the source EES.
  • 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.
  • the communication apparatus 1300 When the communication apparatus 1300 is used to implement the function of the source EES (ie EES 1) in the embodiment shown in FIG. 7 or FIG. 8, it 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 transceiving unit 1302, where the first request message is used to discover the EES, and the first request message indicates the first communication requirement for the target EES; and , receiving a response message from the ECS through the transceiver unit 1302, where the response message carries information of at least one EES that meets the first communication requirement.
  • a transceiver unit 1302 for communicating with the ECS
  • a processing unit 1301 for sending a first request message to the ECS through the transceiving unit 1302, where the first request message is used to discover the EES, and the first request message indicates the first communication requirement for the target EES
  • the processing unit 1301 is further configured to: receive, through the transceiver unit 1302, a second communication requirement from the first EAS, where the second communication requirement is used to indicate that the EAS needs to migrate the application context. communication needs.
  • the second communication requirement includes a quality parameter of the communication connection for migrating the application context and/or the type of the communication connection for migrating the application context.
  • the second communication requirement further includes at least one item of the following information: the target EES supports communication with the first EES, and the type of communication connection between the first EES and the target EES , the quality parameter of the communication connection between the first EES and the target EES.
  • the first request message carries the information of the first EES.
  • the first request information carries indication information, where the indication information is used to indicate that the target EES is used to apply uplink migration.
  • the communication apparatus 1300 When the communication apparatus 1300 is used to implement the function of the target EES (that is, the EES 2) in the embodiment shown in FIG. 9, it may specifically include: a transceiver unit 1302, configured to: receive a first request message from a terminal device, The first request message is used to request the target EES to discover the target edge application server EAS that migrates the application context of the terminal device, and the request message includes the communication requirements for the application context migration; the processing unit 1301 is used to determine There is an EAS that meets the communication requirement; the transceiver unit 1302 is further configured to send a response message to the terminal device when the processing unit 1301 determines that there is an EAS that meets the communication requirement, where the response message carries the Information about the EAS that describes the communication needs.
  • a transceiver unit 1302 configured to: receive a first request message from a terminal device, The first request message is used to request the target EES to discover the target edge application server EAS that migrates the application context of the terminal device, and the request message
  • the communication requirement includes: the target EES supports communication with the source EES, the type of the communication connection for migrating the application context, and the quality parameter of the communication connection for migrating the application context.
  • the communication apparatus 1300 When the communication apparatus 1300 is used to implement the functions of the terminal device in the embodiment shown in FIG. 9, it may specifically include: a transceiver unit 1302 for communicating with the target EES; a processing unit 1301 for using the transceiver unit 1301 Unit 1302 sends a first request message to the target EES, where the request message is used to request the target EES to discover a target edge application server EAS that migrates the application context of the terminal device, and the request message includes a request for the application context migration and receiving a response message from the target EES through the transceiving unit 1302, where the response message includes the information of the EAS that meets the communication requirement.
  • a transceiver unit 1302 for communicating with the target EES
  • a processing unit 1301 for using the transceiver unit 1301
  • Unit 1302 sends a first request message to the target EES, where the request message is used to request the target EES to discover a target edge application server EAS that migrates the application context of the terminal device, and
  • the communication requirement includes: the target EES supports communication with the source EES, the type of the communication connection for migrating the application context, and the quality parameter of the communication connection for migrating the application context.
  • each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .
  • the communication apparatus may be as shown in FIG. 14 , and the apparatus may be a communication device or a chip in the communication device, where the communication device may be the ECS or the terminal device or the EES in the foregoing embodiment.
  • the apparatus may include a processor 1401 , a communication interface 1402 , and a memory 1403 .
  • the processing unit 1301 may be the processor 1401 .
  • the transceiver unit 1302 may be the communication interface 1402 .
  • the processor 1401 may be a CPU, or a digital processing unit or the like.
  • the communication interface 1402 may be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip or the like.
  • the apparatus further includes: a memory 1403 for storing programs executed by the processor 1401 .
  • the memory 1403 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or may be a volatile memory (volatile memory), such as random access memory (random access memory) -access memory, RAM).
  • Memory 1403 is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the processor 1401 is configured to execute the program code stored in the memory 1403, and is specifically configured to execute the actions of the above-mentioned processing unit 1301, which will not be repeated in this application.
  • the communication interface 1402 is specifically configured to perform the actions of the above-mentioned transceiver unit 1302, and details are not described herein again in this application.
  • connection medium between the communication interface 1402 , the processor 1401 , and the memory 1403 is not limited in the embodiments of the present application.
  • the memory 1403, the processor 1401, and the communication interface 1402 are connected through a bus 1404 in FIG. 14.
  • the bus is represented by a thick line in FIG. 14, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is shown in FIG. 14, but it does not mean that there is only one bus or one type of bus.
  • Embodiments of the present application further provide a computer-readable storage medium for storing computer software instructions that need to be executed to execute the above-mentioned processor, which includes a program to be executed to execute the above-mentioned processor.
  • Embodiments of the present application further provide a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiments.
  • An embodiment of the present application further provides a chip, where the chip is coupled with a memory, and the chip is used to implement the communication method provided by the above method embodiments.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may 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.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Abstract

本申请实施例提供一种通信方法及装置，用于解决应用上下文无法在两个边缘数据网络中心迁移的问题。该方法包括：边缘配置服务器(ECS)接收第一请求消息，第一请求消息用于发现边缘使能服务器(EES)，且请求消息指示对目标EES的通信需求；ECS确定至少一个满足通信需求的EES；ECS发送响应消息，响应消息携带至少一个EES的信息。本申请实施例中通过在用于发现EES的请求消息中指示对目标EES的通信需求，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2021年02月24日提交中国专利局、申请号为202110209614.0、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
随着各类云计算资源在网络内的大量部署，同一应用往往同时部署于多个边缘数据网络中。部署在不同的边缘数据网络的同一应用的服务器可以提供相同的业务，具有功能上的等价性。终端设备在接入网络后，会选择就近的边缘数据网络中的应用实例执行业务。由于终端设备具有移动性，可能终端设备之前选择的应用实例不能很好的为该终端设备继续提供业务，为了适应应用的业务连续性需求，网络为终端设备重新就近选择一个新的边缘数据网络中的应用实例继续进行业务。完成从源应用实例到目标应用实例的切换。
在终端设备的数据业务从源应用实例切换到目标应用实例时，由于源应用实例和目标应用实例属于不同的边缘数据网络，两个边缘数据网络之间可能存在隔离/防火墙而无法相互通信，导致应用上下文无法在两个边缘数据网络中心迁移。
发明内容
本申请实施例提供一种通信方法及装置，用于解决应用上下文无法在两个边缘数据网络中心迁移的问题。
第一方面，提供一种通信方法，该方法可以应用于边缘配置服务器(edge configuration server，ECS)，该方法包括以下步骤：ECS接收第一请求消息，所述第一请求消息用于发现边缘使能服务器(edge enabler server，EES)，且所述请求消息指示对目标EES的通信需求；所述ECS确定至少一个满足所述通信需求的EES；所述ECS发送响应消息，所述响应消息携带所述至少一个EES的信息。本申请实施例中通过在用于发现EES的请求消息中指示对目标EES的通信需求，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，在边缘配置服务器ECS接收所述第一请求消息之前，所述ECS分别接收第一EES的配置信息，所述第一EES包括源EES和/或所述目标EES，其中，所述第一EES的配置信息包括支持与所述第一EES进行通信的第二EES的信息。通过上述设计，ECS可以获取EES的拓扑连接关系，从而可以在进行应用上下文切换时，可以选择与源EES有通信连接的目标ESS从而可以保证应用的业务连续性。
在一个可能的设计中，第一EES包括一个或多个EES。
在一个可能的设计中，所述第一EES的配置信息还包括所述第一EES与第二EES之 间的通信连接的信息。通过上述设计，ECS可以获取EES的拓扑连接关系以及通信连接的信息，从而可以在进行应用上下文切换时，可以选择通信连接类型或通信连接质量满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述ECS向策略控制功能(policy control function，PCF)或者会话管理功能(sEESion management function，SMF)网元发送第二请求消息，所述第二请求消息用于请求建立所述源EES所连接的用户面功能UPF网元与所述目标EES连接的UPF网元之间的UPF隧道。通过上述设计，使得源EES和目标EES之间可以通信，从而可以实现应用上下文的迁移。
在一个可能的设计中，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。通过上述设计，使得ECS可以发现满足通信质量的目标EES。
在一个可能的设计中，所述第一请求消息携带源EES的信息。通过上述设计，使得ECS可以确定源EES，从而可以发现与源EES有通信连接的目标EES。
在一个可能的设计中，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。通过上述设计，可以将发现EES的过程与应用上下文迁移关联起来。
第二方面，提供一种通信方法，该方法可以应用于终端设备，该方法包括以下步骤：终端设备向ECS发送第一请求消息，所述第一请求消息用于发现EES，且所述第一请求消息指示对目标EES的通信需求；所述终端设备接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述通信需求的EES的信息。本申请实施例中通过在用于发现EES的请求消息中指示对目标EES的通信需求，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。通过上述设计，使得ECS可以发现满足通信质量的目标EES。
在一个可能的设计中，所述第一请求消息携带源EES的信息。通过上述设计，使得ECS可以确定源EES，从而可以发现与源EES有通信连接的目标EES。
在一个可能的设计中，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。通过上述设计，可以将发现EES的过程与应用上下文迁移关联起来。
第三方面，提供一种通信方法，该方法可以应用于边缘应用服务器(edge application server，EAS)，该方法包括以下步骤：第一EAS向第一EES发送第一请求消息，所述第一请求消息用于发现与所述第一EAS进行应用上下文迁移的目标EAS，且所述第一请求消息指示迁移所述应用上下文的通信需求。所述第一EAS从所述第一EES获取所述第一请求消息的响应消息，所述响应消息中包含满足所述通信需求的EAS的信息。本申请实施例中，第一EAS通过向第一EES发送迁移所述应用上下文的通信需求，使得第一EES可以在用于发现EES的请求消息中指示对目标EES的通信需求，使得在进行应用上下文切 换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述通信需求包括迁移所述应用上下文的通信连接的质量参数和/或迁移所述应用上下文的通信连接的类型。通过上述设计，使得源EES可以选择满足通信质量要求的目标EES。
第四方面，提供一种通信方法，该方法可以应用于EES，该方法包括以下步骤：第一边缘使能服务器EES向边缘配置服务器ECS发送第一请求消息，所述第一请求消息用于发现EES，且所述第一请求消息指示所述对目标EES的第一通信需求；所述第一EES接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述第一通信需求的EES的信息。本申请实施例中通过在用于发现EES的请求消息中指示对目标EES的通信需求，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述第一EES接收来自第一边缘应用服务器EAS的第二通信需求，所述第二通信需求用于指示所述EAS对所述应用上下文迁移的通信需求。通过上述设计，使得源EES可以获取所述应用上下文迁移的通信需求。
在一个可能的设计中，所述第二通信需求包括迁移所述应用上下文的通信连接的质量参数和/或迁移所述应用上下文的通信连接的类型。通过上述设计，使得源EES可以获取所述应用上下文迁移的通信质量要求。
在一个可能的设计中，所述第二通信需求还包括如下信息中至少一项：所述目标EES支持与所述第一EES进行通信、所述第一EES与所述目标EES之间的通信连接的类型、所述第一EES与所述目标EES之间的通信连接的质量参数。通过上述设计，使得ECS可以发现满足通信质量的目标EES。
在一个可能的设计中，所述第一请求消息携带所述第一EES的信息。通过上述设计，使得ECS可以确定源EES，从而可以发现与源EES有通信连接的目标EES。
在一个可能的设计中，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上行文迁移。通过上述设计，可以将发现EES的过程与应用上下文迁移关联起来。
第五方面，提供一种通信方法，该方法可以应用于EES，该方法包括以下步骤：目标EES接收来自终端设备的第一请求消息，所述第一请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标EAS，且所述请求消息包含对应用上下文迁移的通信需求；当所述目标EES确定存在满足所述需求的EAS时，所述目标EES向所述终端设备发送响应消息，所述响应消息携带所述需求的EAS的信息。本申请实施例中目标EES可以根据通信需求判断是够与源EES存在满足通信需求的通信连接，从而可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述目标EES向PCF网元或者SMF网元发送第二请求消息，所述第二请求消息用于请求建立所述源EES所连接的用户面功能UPF网元与所述目标EES连接的UPF网元之间的UPF隧道。通过上述设计，使得源EES和目标EES之间可以通信，从而可以实现应用上下文的迁移。
在一个可能的设计中，所述通信需求包括：所述目标EES支持与所述源EES进行通信、所述应用上下文迁移的通信连接的类型、所述应用上下文迁移的通信连接的质量参数。通过上述设计，使得ECS可以发现满足通信质量的目标EES。
第六方面，提供一种通信方法，该方法可以应用于终端设备，该方法包括以下步骤：终端设备向目标EES发送第一请求消息，所述请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；所述终端设备接收来自所述目标EES的响应消息，所述响应消息包含满足所述需求的EAS的信息。本申请实施例中目标EES可以根据通信需求判断是够与源EES存在满足通信需求的通信连接，从而可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述通信需求包括：所述目标EES支持与所述源EES进行通信、所述应用上下文迁移的通信连接的类型、所述应用上下文迁移的通信连接的质量参数。通过上述设计，使得ECS可以发现满足通信质量的目标EES。
第七方面，提供一种通信方法，该方法可以应用于ECS，该方法包括以下步骤：ECS接收请求消息，所述请求消息用于发现EES；所述ECS发送响应消息，所述响应消息携带第一EES的信息，其中，所述第一EES的信息包括支持与所述第一EES进行通信的第二EES的信息。本申请实施例中，ECS通过向终端设备发送EES的拓扑连接信息，使得终端设备在选择目标EES时可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，第一EES包括一个或多个EES。
在一个可能的设计中，第二EES包括一个或多个EES。
在一个可能的设计中，所述第一EES的信息还包括所述第一EES与所述第二EES之间的通信连接的信息。通过上述设计，可以避免选择一个通信连接不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述通信连接的信息包括如下信息中至少一项：所述第一EES与所述第二EES之间的通信连接的类型、所述第一EES与所述第二EES之间的通信连接的质量参数。通过上述设计，可以避免选择一个通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
第八方面，提供一种通信方法，该方法可以应用于终端设备，该方法包括以下步骤：终端设备向ECS发送第一请求消息，所述第一请求消息用于获取边缘使能服务器EES；所述终端设备接收来自所述ECS的响应消息，所述响应消息携带第一EES的信息，其中，所述第一EES的信息包括支持与所述第一EES进行通信的第二EES的信息。本申请实施例中，ECS通过向终端设备发送EES的拓扑连接信息，使得终端设备在选择目标EES时可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，第一EES包括一个或多个EES。
在一个可能的设计中，第二EES包括一个或多个EES。
在一个可能的设计中，所述第一EES的信息还包括所述第一EES与所述第二EES之 间的通信连接的信息。通过上述设计，可以避免选择一个通信连接不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述通信连接的信息包括如下信息中至少一项：所述第一EES与所述第二EES之间的通信连接的类型、所述第一EES与所述第二EES之间的通信连接的质量参数。通过上述设计，可以避免选择一个通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述终端设备根据所述带第一EES的信息确定目标EES，其中，所述目标EES满足应用上下文迁移的通信需求。
在一个可能的设计中，所述通信需求包括如下信息中至少一项：所述目标EES支持与所述源EES进行通信、所述应用上下文迁移的通信连接的类型、所述应用上下文迁移的通信连接的质量参数。通过上述设计，可以避免选择一个通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标EES，从而可以保证应用的业务连续性。
第九方面，提供一种通信方法，该方法可以应用于SMF网元，该方法包括以下步骤：所述核心网设备检测到第一事件，所述第一事件用于所述核心网设备选择新的数据网络接入标识符DNAI；所述核心网设备确定目标DNAI，所述目标DNAI对应的目标边缘使能服务器EES支持与所述源EES进行通信。本申请实施例中，由网络侧在选择DNAI时候就选择与源EES有通信连接的EES对应的DNAI，进而保障该目标DNAI对应的EES与源EES有通信连接，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
在一个可能的设计中，所述核心网设备接收应用功能AF网元发送的请求消息，所述请求消息用于获取所述目标DNAI的信息，所述请求消息中包含对目标DNAI的通信需求；所述第一核心网设备向所述AF网元发送所述请求消息的响应消息，所述响应消息中包含所述目标DNAI。通过上述设计，核心网设备可以获取对目标DNAI的通信需求。
在一个可能的设计中，所述对目标DNAI的通信需求包括如下信息中至少一项：所述目标DNAI对应的所述目标EES支持与所述源EES进行通信、所述源EES与目标EES之间的通信连接的类型、所述源EES与所述目标EES的通信连接的质量参数。通过上述设计，可以避免选择一个通信连接类型或通信连接质量不能满足应用上下文迁移的通信需求的目标DNAI，从而可以保证应用的业务连续性。
在一个可能的设计中，在所述核心网设备确定DNAI之前，所述第一核心网设备获取所述源EES的信息与所述目标EES的信息。通过上述设计，核心网设备可以获取EES的拓扑连接信息，从而可以选择满足通信需求的目标DNAI。
第十方面，提供一种通信方法，该方法可以应用于SMF，该方法包括以下步骤：第一核心网设备接收来自应用功能AF网元发送的第一消息，所述第一消息用于请求建立源EES所连接的第一用户面功能UPF网元与目标EES连接的第二UPF网元之间的UPF隧道，所述请求消息携带所述目标路由信息，所述目标路由信息用于确定第二UPF；所述第一核心网设备根据所述目标路由信息获取所述第二UPF网元的隧道信息；所述第一核心网设备向所述第一UPF网元发送转发规则，所述转发规则用于指示所述第一UPF网元将来自所述源EES的数据向所述第二UPF网元进行转发，所述转发规则携带所述第二UPF网元的隧道信息。通过本申请实施例，可以建立源EES和目标EES之间的通信连接，从而可以实现应用上下文的迁移。
在一个可能的设计中，AF网元可以为源EES或者目标EES或者ECS。
在一个可能的设计中，目标路由信息包含目标DNAI和/或目标N6路由信息。
在一个可能的设计中，所述第一核心网设备根据所述目标路由信息获取所述第二UPF网元的隧道信息，包括：若所述目标路由信息在所述第一核心网设备的服务范围内，则所述第一核心网设备根据所述目标路由信息确定所述第二UPF的隧道信息。通过上述设计，SMF网元可以在本地获取第二UPF网元的隧道信息。
在一个可能的设计中，所述第一核心网设备向所述第二UPF发送上述转发规则，所述转发规则还用于指示所述第二UPF将来自所述第一UPF网元的数据向目标EES进行转发，所述转发规则还携带所述第一UPF的隧道信息。
在一个可能的设计中，所述第一核心网设备根据所述目标路由信息获取所述第二UPF网元的隧道信息，包括：若所述目标路由信息不在所述第一核心网设备的服务范围内，则所述第一核心网设备根据所述目标路由信息确定第二核心网设备；所述第一核心网设备向所述第二核心网设备发送第二消息，所述第二消息用于请求在所述第一UPF和所述第二UPF之间建立UPF隧道，所述第二消息携带所述目标路由信息以及所述第一UPF网元的隧道信息；所述第一核心网设备接收所述第二核心网设备发送的第三消息，所述第三消息携带所述第二UPF的地址信息。通过上述设计，SMF可以获取其他SMF服务范围内的第二UPF。
第十一方面，本申请提供一种通信装置，该装置可以是通信设备，也可以是通信设备内的芯片或芯片组，其中，通信设备可以为ECS或者终端设备或者EAS或者EES或者核心网设备如SMF网元。该装置可以包括处理单元和收发单元。当该装置是通信设备时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使ECS执行上述第一方面或第七方面相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第二方面或第六方面或第八方面相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使EAS执行上述第三方面中相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使EES执行上述第四方面或第五方面中相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使核心网设备执行上述第九方面或第十方面中相应的功能。当该装置是通信设备内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，该处理单元执行该存储模块所存储的指令，以使ECS执行上述第一方面或第七方面相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第二方面或第六方面或第八方面相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使EAS执行上述第三方面中相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使EES执行上述第四方面或第五方面中相应的功能，或者，该处理单元执行该存储模块所存储的指令，以使核心网设备执行上述第九方面或第十方面中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是该基站内的位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十二方面，本申请实施例提供一种通信装置，该装置包括通信接口和处理器，所述通信接口用于该装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口 可以是收发器、电路、总线、模块或其它类型的接口，其它设备可以为网络设备。处理器用于调用一组程序、指令或数据，执行上述第一方面或第一方面各个可能的设计描述的方法或者上述第七方面或第七方面各个可能的设计描述的方法。所述装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第一方面或第一方面各个可能的设计描述的方法或者上述第七方面或第七方面各个可能的设计描述的方法。
第十三方面，本申请实施例提供一种通信装置，该装置包括通信接口和处理器，所述通信接口用于该装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的接口，其它设备可以为终端设备。处理器用于调用一组程序、指令或数据，执行上述第二方面或第二方面各个可能的设计描述的方法、第六方面或第六方面各个可能的设计描述的方法、第八方面或第八方面各个可能的设计描述的方法。所述装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第二方面或第二方面各个可能的设计描述的方法、第六方面或第六方面各个可能的设计描述的方法、第八方面或第八方面各个可能的设计描述的方法。
第十四方面，本申请实施例提供一种通信装置，该装置包括通信接口和处理器，所述通信接口用于该装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的接口，其它设备可以为终端设备。处理器用于调用一组程序、指令或数据，执行上述第三方面或第三方面各个可能的设计描述的方法。所述装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第三方面或第三方面各个可能的设计描述的方法。
第十五方面，本申请实施例提供一种通信装置，该装置包括通信接口和处理器，所述通信接口用于该装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的接口，其它设备可以为终端设备。处理器用于调用一组程序、指令或数据，执行上述第四方面或第四方面各个可能的设计描述的方法、第五方面或第五方面各个可能的设计描述的方法。所述装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第四方面或第四方面各个可能的设计描述的方法、第五方面或第五方面各个可能的设计描述的方法。
第十六方面，本申请实施例提供一种通信装置，该装置包括通信接口和处理器，所述通信接口用于该装置与其它设备进行通信，例如数据或信号的收发。示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的接口，其它设备可以为终端设备。处理器用于调用一组程序、指令或数据，执行上述第九方面或第九方面各个可能的设计描述的方法、第十方面或第十方面各个可能的设计描述的方法。所述装置还可以包括存储器，用于存储处理器调用的程序、指令或数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的、指令或数据时，可以实现上述第九方面或第九方面各个可能的设计描述的方法、第十方面或第十方面各个可能的设计描述的方法。
第十七方面，本申请实施例中还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可读指令，当所述计算机可读指令在计算机上运行时，使得如第一方 面至第十方面中任一方面、以及第一方面至第十方面中任一方面各个可能的设计所述的方法被执行。
第十八方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述第一方面至第十方面中任一方面、以及第一方面至第十方面中任一方面各个可能的设计所述的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十九方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得如上述第一方面至第十方面中任一方面、以及第一方面至第十方面中任一方面各个可能的设计所述的方法被执行。
其中，第十一方面至第十九方面中任一种实现方式所带来的技术效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种MEC网络的架构示意图；
图2为本申请实施例提供的一种通信网络的架构示意图；
图3为本申请实施例提供的一种迁移应用上下文的示意图；
图4为本申请实施例提供的一种增强EES注册流程以及EES发现流程的示意图；
图5为本申请实施例提供的一种建立UPF隧道的示意图；
图6为本申请实施例提供的一种应用上下文迁移的流程示意图；
图7为本申请实施例提供的一种应用上下文迁移的流程示意图；
图8为本申请实施例提供的一种应用上下文迁移的流程示意图；
图9为本申请实施例提供的一种应用上下文迁移的流程示意图；
图10为本申请实施例提供的一种应用上下文迁移的流程示意图；
图11为本申请实施例提供的一种应用上下文迁移的流程示意图；
图12为本申请实施例提供的一种建立UPF隧道的流程示意图；
图13为本申请实施例提供的一种通信装置的结构示意图；
图14为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第 一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
参照图1，在第三代合作伙伴计划(3rd generation partnership project，3GPP)的SA6的多接入边缘计算(multi-accEES edge computing，MEC)研究中，定义了如下架构模型：
边缘数据网络(edge data network，EDN)，一种理解为，EDN只对应一个数据网络，是一个特别的本地数据网络(local，data network，DN)，包含边缘使能功能，可以使用数据网络接入标识符(DN accEES identifier，DNAI)和数据网络标识(data network name，DNN)标识，是网络逻辑概念。另一种理解为，EDN是中心云的对等概念，可以理解为是一个本地的数据中心(地理位置概念)，可以使用DNAI来标识，可以包含多个本地数据网络(local DN)。以华为手机中的“应用市场”应用程序为例，在深圳总部可以设置一个“应用市场”的中心云。为了方便北京和上海的用户使用，北京和上海可分别设置一个“应用市场”的本地EDN网络。后续，北京的用户可通过北京设置的“应用市场”的本地EDN网络，来获取应用服务。而上海用户可通过上海设置的“应用市场”的本地EDN网络，来获取应用服务，各EDN网络就近为各用户提供应用服务，可给用户提供更高质量的网络体验。
应用实例或边缘应用，部署在EDN中的应用称为应用实例。具体是指一个服务器应用程序，例如社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)部署运行在EDN中的实例(instance)。一个应用可以在一个或多个EDN中部署一个或多个边缘应用服务器(edge application server，EAS)，部署运行在不同的EDN中的EAS可以认为是一个应用的不同EAS，它们可以共享一个域名，可以使用一个任播IP地址，也可以使用不同的IP地址等，不作限定。EAS还称为应用实例、边缘应用实例、MEC应用服务器、EAS功能等。
应用客户端(application client，AC)，是EAS在终端设备侧的对等实体。AC用于应用用户从EAS中获取应用业务。AC是应用在终端侧的客户端程序，AC可以连接到中心云上的EAS获取应用业务，也可以连接到部署运行在一个或多个EDN中的EAS以获取业务应用。
边缘使能服务器(edge enabler server，EES)，可以为部署在EDN中的实例提供使能能力，可以更好的支持应用在MEC的部署情况。例如，EES可以支持边缘应用的注册，对终端设备的认证和鉴权，为终端设备提供应用实例的IP地址信息等。进一步的，EES还可支持获取应用实例的标识和IP地址信息，并将应用实例的标识和IP地址信息发送给ECS。EES部署在EDN中。一般情况下，EAS注册到一个EES上，或者，通过管理系统将一个EAS的信息配置在一个EES上，该EES称为该EAS关联的EES，EES可以控制、管理、注册或配置在该EES关联的EAS等。
边缘使能客户端(edge enabler client，EEC)，是EES在终端设备侧的对等实体。EEC用于向EES注册EEC的信息及应用客户端的信息、执行安全认证和鉴权、从EES获取EAS的IP地址、向应用客户端提供边缘计算使能能力，如EAS发现服务，将EAS的IP地址返回给应用客户端。
边缘配置服务器(edge configuration server，ECS)，负责EDN的配置，如向终端设备提供EES的信息。还可以向终端设备提供应用实例的信息，以及和应用的DNS交互获取应用实例的信息。进一步，还可以从其他功能实体获取并保存应用实例和IP地址的信息等。
示例性的，EEC可以通过如下五种方式中任一种获取ECS的地址：
1)EEC中可以预先配置ECS的地址；
2)AC可以将ECS的地址配置给EEC；
3)用户在终端设备上指定一个ECS，即用户通过操作终端设备在ECS列表中选择一个ECS，终端设备可以向EEC指示该ECS；
4)EEC可以根据公共陆地移动网络(public land mobile network，PLMN)ID确定ECS地址；
5)5G核心网(5G core，5GC)将ECS地址配置到UE，UE可以将通过5GC接收到的ECS地址发送给EEC。
如图2所示，3GPP标准TS 23.501中定义的网络架构如下，包括：无线接入网络(radio accEES network，RAN)和核心网。不同接入网设备之间可通过Xn接口连接，接入网设备与核心网之间可通过NG接口连接。
RAN用于实现无线接入有关的功能，例如RAN可以为终端设备提供无线资源管理、服务质量管理、数据加密和压缩等功能。示例地，接入网设备可以包括以下几种类型：
1、下一代节点(next generation nodeB，gNB)，为终端设备提供新无线(new radio，NR)的控制面和/或用户面的协议和功能，并且接入到核心网。例如，5G核心网(5th generation core，5GC)。
2、下一代演进型节点(next generation evolved Node B，ng-eNB)，为终端设备提供演进的通用陆地无线接入(evolved universal terrestrial radio accEES，E-UTRA)的控制面和/或用户面的协议和功能，并且接入到核心网。例如，5GC等。
可选的，接入网设备可以由集中式单元(central unit，CU)和分布式单元(distributed unit，DU)构成，即可对原接入网设备的功能进行拆分，将原接入网设备的部分功能部置在CU，剩余的部分功能部署在DU，多个DU共用一个CU，节省成本，易于网络扩展。CU和DU之间可通过FI接口连接。CU可以代表接入网设备通过NG接口与核心网相连，CU还可以代表接入网设备通过Xn接口和其它接入网设备相连。更进一步的，CU的功能还可被划分为：
1、集中单元-控制平面(central unit–control plane，CU-CP)：主要包括了CU中的RRC层，以及PDCP层中的控制面；
2、集中单元-用户平面(central unit–user plane，CU-UP)：主要包括了CU中的SDAP层，以及PDCP层中的用户面。
核心网主要用于对终端设备进行管理，并提供与外网通信的功能。核心网设备可包括以下中的一个或多个网元：
用户面功能(user plane function，UPF)网元：主要负责用户数据的转发和接收。在下行传输中，UPF网元可以从数据网络(data network，DN)接收用户数据，通过接入网设备传输给终端设备；在上行传输中，UPF网元可以通过接入网设备从终端设备接收用户数据，向DN转发该用户数据。可选的，UPF网元中为终端设备提供服务的传输资源和调度功能可以由SMF网元管理控制。
接入和移动管理功能(accEES and mobility management function，AMF)网元：主要负责移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。
会话管理功能(sEESion management function，SMF)网元：主要负责移动网络中的会话管理，如会话建立、修改、释放。具体功能如为用户分配IP地址、选择提供报文转发功能的UPF网元等。
策略控制功能(policy control function，PCF)网元：主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。
应用功能(application function，AF)网元：主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
统一数据管理(unified data management，UDM)网元：主要用于生成认证信任状，用户标识处理(如存储和管理用户永久身份等)，接入授权控制和签约数据管理等。
需要说明的是，在不同的通信系统中，上述核心网中的网元可以有不同的名称。在上述图2所示的示意图中，是以第五代移动通信系统为例进行说明的，并不作为对本申请的限定。
可选的，图2所示的网络架构中，还可包括：终端设备。终端设备可以简称为终端，是一种具有无线收发功能的设备，终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机、平板电脑、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶中的无线终端设备、远程医疗中的无线终端设备、智能电网中的无线终端设备、运输安全中的无线终端设备、智慧城市中的无线终端设备、或智慧家庭中的无线终端设备等。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(sEESion initiation protocol，SIP)电话、无线本地环路(wirelEES local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来第五代(the 5th generation，5G)网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。终端设备有时也可以称为用户设备(user equipment，UE)、接入终端设备、车载终端设备、工业控制终端设备、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、无线通信设备、UE代理或UE装置等。终端设备也可以是固定的或者移动的。本申请实施例对此并不限定。
可选的，图2所示的网络架构中，还可包括：数据网络(data network，DN)。DN可以是为用户提供数据传输服务的网络。例如，DN可以是IP多媒体业务(IP multi-media service)网络或互联网络。DN中可包括多个应用服务器。其中，终端设备可以建立从终端设备到DN的协议数据单元(protocol data unit，PDU)会话，来访问DN。其中，一个数据网络可以有一个或多个本地数据网络(local data network，Local DN)，这些本地数据网络为靠近用户附着点(point of attachment)的数据网络接入点(accEES point)。
在本申请实施例中，上述图1所示架构中的ECS、EES和EAS可以配置于上述一个或多个DN中。或者，可描述为，上述DN中包括一个或多个EDN，每个EDN包括EES和EAS，还可以包含ECS。除此之外，上述DN中还可配置有应用中心云平台。应用中心 云平台与上述EAS可以认为是对等的概念。每个EAS可以就近为用户提供应用服务，而应用中心云平台可以为所有用户提供应用服务。应用中心云平台，还可称为中心云平台。在以下描述中，以中心云平台为例进行描述。以“华为音乐”客户端为例说明，说明EDN网络与中心云平台的关系：在深圳总部可以设置一个关于“华为音乐”的中心云平台，该中心云平台可以为全球用户的“华为音乐”客户端提供服务。同时为了方便给北京和上海的用户提供音乐服务，可以分别在北京地区和上海地区的EDN网络部署华为音乐的EAS。此后，北京地区的用户，可访问北京对应的EDN网络中的华为音乐的EAS，以获取华为音乐服务。而上海地区的用户，可以访问上海对应的EDN网络中的华为音乐的EAS，以获取华为音乐服务。进一步，当北京地区或上海地区的EDN网络故障，或者对应的华为音乐EAS出现问题，如过载等，或者，不能提供某些特定的服务时，北京地区或上海地区的用户，可访问位于深圳地区的华为音乐的中心云平台，以获取相应音乐服务。
随着各类云计算资源在网络内的大量部署，同一应用往往同时部署于多个EDN中。部署在不同的EDN的同一应用的服务器可以提供相同的业务，具有功能上的等价性。终端设备在接入网络后，会选择就近的EDN中的EAS执行业务。由于终端设备具有移动性，可能终端设备之前选择的EAS不能很好的为该终端设备继续提供业务，为了适应应用的业务连续性需求，网络为终端设备重新就近选择一个新的EAS继续进行业务。
在终端设备的数据业务从源EAS切换到目标EAS时，由于源EAS和目标EAS属于不同的EDN，会造成终端设备连接的中断，为了保持业务连续性，可以将源EAS中的应用上下文迁移至目标EAS，这个过程称为应用迁移或应用上下文迁移。
源EAS和目标EAS可能属于不同的EDN，两个EDN之间可能存在隔离/防火墙无法相互通信，因此源EAS中的应用上下文可能无法迁移至目标EAS。例如，如图3所示，随着UE移动，UE由EDN#1切换到EDN#2，由于EDN#1和EDN#2之间无法通信，导致UE的应用上下文无法迁移到EDN#2。
基于此，本申请实施例提供一种通信方法及装置，通过选择可以与源EAS进行通信的EAS作为应用上下文迁移的目标EAS，从而可以提高迁移应用上下文的成功率。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请实施例中可以通过增强EES注册和EES选择流程，使得ECS侧可以获取EES的拓扑连接关系，或者通过边缘管理系统(用于管理边缘数据网络的资源以及管理EES)将EES的拓扑连接关系配置在ECS，从而可以确定EES连接的其他EES，进而可以在应用上下文迁移过程中反馈与源EES有通信连接的目标EES。具体可以参阅本申请实施例一～实施例三。
其中，增强EES注册过程可以包括：增强EES的配置信息，即在EES的配置信息中包括该EES的拓扑连接信息，拓扑连接信息可以指示与该EES有通信连接的其他EES的信息，具体可以参阅本申请实施例一～实施例三。
增强EES选择流程可以包括：在触发应用迁移时指示对迁移的时延或路径需求。
例如，对于终端设备侧触发的应用上下文迁移(application context relocation，ACR)，可以增强服务配置请求(service provisioning request)或应用上下文迁移请求(ACR request)或完整的应用上下文迁移请求(full ACR request)，使得service provisioning request或ACR request或full ACR request可以指示对目标EES的通信需求。具体可以参阅本申请实施例 一。
又例如，对于EAS侧发起的ACR，EAS请求的EAS发现(EAS discover)也可以指示对目标EES的通信需求。具体可以参阅本申请实施例二。
又例如，对于EES侧发起的ACR，EES请求发现EES的消息中也可以指示对目标EES的通信需求。具体可以参阅本申请实施例三。
例如，如图4所示，EES#2的配置信息中可以携带EES 2的拓扑连接信息。EEC发送的服务配置请求或者EES#1发送的EES获取请求(EES retrieve request)中可以指示对目标EES的通信需求。
或者，本申请实施例中可以通过增强EES注册和EAS选择流程，使得目标EES可以获取对目标EAS的通信需求，从而可以判断自身是否与源EES存在满足通信需求的通信连接。
其中，增强EES注册过程可以包括：增强EES的配置信息，即在EES的配置信息中包括该EES的拓扑连接信息，拓扑连接信息可以指示与该EES有通信连接的其他EES的信息。增强EAS选择流程可以包括：终端设备向目标EES发送的用于发现EAS的消息可以指示对目标EAS的通信需求。具体可以参阅本申请实施例四。
或者，本申请实施例中可以通过增强EES注册和EES选择流程，使得EEC可以获取EES的拓扑连接信息，从而可以选择满足对目标EES的通信需求的EES作为目标EES。
其中，增强EES注册过程可以包括：增强EES的配置信息，即在EES的配置信息中包括该EES的拓扑连接信息，拓扑连接信息可以指示与该EES有通信连接的其他EES的信息。增强EES选择流程可以包括：ECS可以在service provisioning response消息中，将EES的拓扑连接信息发给EEC。具体可以参阅本申请实施例五。
或者，本申请实施例中可以通过SMF获取EES的拓扑连接信息，从而可以选择满足要求的DNAI。具体可以参阅本申请实施例六。
此外，本申请还提供一种在两个EES分别连接的UPF之间建立UPF隧道的方法，具体可以参阅本申请实施例七。例如，如图5所示。
需要说明的是，本申请实施例中所述的“对目标EES的通信需求”也可以称为“应用上下文迁移的通信需求”或者“迁移应用上下文的通信需求”，可以理解的，“对目标EES的通信需求”、“应用上下文迁移的通信需求”、“迁移应用上下文的通信需求”、“应用上下文迁移的需求”、“迁移应用上下文的需求”相互之间可以等效替换。
本申请实施例中所述的“源EES与目标EES之间的通信连接”也可以称为“应用上下文迁移的通信连接”或者“迁移应用上下文的通信连接”，可以理解的，“源EES与目标EES之间的通信连接”、“应用上下文迁移的通信连接”、“迁移应用上下文的通信连接”相互之间可以等效替换。
可以理解的，本申请实施例中所述的“通信需求”可以理解为对通信连接的需求，也可以称为“连接需求”、“需求”、“路径需求”等。“通信需求”、“连接需求”、“路径需求”与“需求”可以理解为相同的含义。
以下介绍本申请的七个实施例。
实施例一：
本申请实施例一可以应用于由终端设备(例如终端设备中的EEC)发起应用上下文迁移(应用迁移)的场景。
在本申请实施例一中，终端设备向ECS发送请求消息，该请求消息用于获取EES，且该请求消息可以指示对目标EES的通信需求。从而，ECS可以向终端设备反馈满足该通信需求的EES。
如图6所示，为实施例一的具体流程，该流程可以包括但不限于EES的注册流程、终端设备初始接入EAS的过程、以及应用上下文迁移的过程。
EES的注册流程具体可以如下：
S601，第一EES分别向ECS发送注册请求，该注册请求可以携带第一EES的配置信息。
第一EES的配置信息包括支持与该第一EES进行通信的第二EES的信息。例如，第一EES的配置信息可以包括该第一EES的拓扑连接信息(也可以称为允许连接的信息或允许连接EES的信息)，该拓扑连接信息可以指示支持与该第一EES进行通信的第二EES的信息。第一EES的拓扑连接信息可以包括边缘计算服务提供商(edge computing service provider，ECSP)供应商标识列表，或EES标识列表，或端点信息列表。其中，ECSP供应商标识列表可以包括支持与该第一EES进行通信的第二EES的ECSP供应商标识。EES标识列表可以包括支持与该第一EES进行通信的第二EES的标识。端点信息列表可以包括支持与该第一EES进行通信的第二EES的端点信息，示例性的，该端点信息可以是一组IP地址/全限定域名(fully qualified domain name，FQDN)/统一资源标志符(uniform resource identifier，URI)/统一资源定位符(uniform resource locator，URL)等等。
其中，第一EES可以包括一个或多个EES，第一EES可以包括EES 1和EES 2。
第二EES可以包括一个或多个EES。
可选的，拓扑连接信息还可以包括该第一EES与第二EES之间的通信连接的信息。第一EES与第二EES之间的通信连接的信息可以包括如下信息中至少一项：通信连接的类型、通信连接的质量参数。
其中，第一EES与第二EES之间的通信连接的类型可以但不限于包括：IP连接、专线连接、UPF隧道连接等等。其中，专线连接可以为基于IP的专用网络连接，该专线连接可以具备：网络路径短(例如，专线连接可以为一跳IP，或专线连接的两个端点之间没有IP路由器或者IP路由器的数量很少)，路径上的资源独占，安全性高等特征。专线连接的通信质量要高于一般IP路由连接。
第一EES与第二EES之间的通信连接的质量参数可以但不限于包括：带宽、时延、抖动等。其中，第一EES与第二EES之间的通信连接的质量可以一段时间内统计的数值，也可以是实时数值，也可以是预测的数值。
可选的，第一EES的配置信息还可以包括如下信息中至少一项：该第一EES标识(identification，ID)、该第一EES的端点(Endpoint)信息、注册到该第一EES的EAS的标识列表等等。第一EES的配置信息中还包含该第一EES的安全凭证。该第一EES的配置信息中还可以包含注册的有效时间，为了维护注册的有效性，第一EES可以在注册的有效时间过期之前，向ECS发送注册更新请求。如果ECS在注册的有效时间内没有收到注册更新请求，ECS则可以认为该第一EES去注册了。
示例性的，第一EES的配置信息可以如表1所示。
表1
Figure PCTCN2021133186-appb-000001
S602，ECS保存第一EES的配置信息。
需要说明的是，该注册过程为可选的步骤。该注册过程也可以单独作为一个实施例。并且，EES的注册过程和终端设备初始接入EAS的过程在时间上可以不是连续执行的，即执行完S602可以间隔任意时间执行终端设备初始接入EAS的过程。其中，ECS还可以通过其他方式获取EES的拓扑连接信息，例如通过边缘管理系统获取EES的拓扑连接信息，或者通过边缘管理系统获取EES所在的EDN的拓扑连接信息，如果EES所在的EDN存在特定的连接通信，则可以认为部署在其中的EES也共享该EDN的拓扑连接信息。
终端设备初始接入EAS的过程具体可以包括：
S603，终端设备(例如，可以是终端设备的EEC)向ECS发送服务配置请求，该请求消息用于发现EES。该请求消息中可以包含EEC的安全凭证、终端设备的标识如通用公有签约者标识(generic public subscription identifier，GPSI)等、连接信息、终端的位置和终端设备中AC的配置信息(AC profile)等。
S604，ECS对终端设备进行授权检查。
如果检查通过后，ECS可以根据服务配置请求选择一个或多个EES。其中，ECS可以选择服务区域中包含该终端设备的位置的EES、注册的EAS列表中包括匹配AC profile的EAS ID的EES等。
S605，ECS向终端设备发送服务配置请求的响应消息，该响应消息携带所发现的一个或多个EES的信息。
S606，终端设备(例如终端设备的EEC)向上述一个或多个EES中的EES 1发送EAS发现请求消息，该EAS发现请求消息可以携带EAS发现过滤器，EAS发现过滤器可以包括EAS的过滤参数。
示例性的，EAS发现过滤器可以如表2所示。
表2
Figure PCTCN2021133186-appb-000002
S607，EES 1向终端设备发送EAS发现请求消息的响应消息，该响应消息携带第一EAS，其中，第一EAS包括一个或多个满足EAS发现过滤器的EAS。
S608，终端设备选择第一EAS中的EAS 1进行连接。
例如，终端设备的EEC可以将第一EAS通过层间交互上递给AC，AC选择第一EAS中的EAS 1，并连接到该EAS 1进行应用层的业务交互。
需要说明的是，该终端设备初始接入EAS的过程为可选的步骤。
应用上下文迁移的过程具体可以包括：
S609，终端设备确定触发应用上下文迁移的事件发生。
例如，终端设备检测到触发应用上下文迁移的事件发生，或者，EES 1检测到触发应用上下文迁移的事件发生并通知给终端设备。
示例性的，触发应用上下文迁移的事件可以但不限于包括：终端设备移动出当前EAS(即EAS 1)的服务区域，或EEC收到SMF的新建会话的消息，或EEC收到一个新的IP前缀等等。
其中，步骤S609为一个可选的步骤。
S610，终端设备(例如，可以是终端设备的EEC)向ECS发送服务配置请求，该请求消息用于发现EES，且该服务配置请求可以指示对目标EES的通信需求。
其中，该服务配置请求可以指示对目标EES的通信需求可以是在该服务配置请求消息中显式携带具体的通信需求参数，或者也可以是隐式指示方式，即该服务配置请求对目标EES的通信需求所属配置文件的索引或指针或句柄。
示例性的，对目标EES的通信需求可以包括如下信息中至少一项：目标EES支持与所述源EES(即EES 1)进行通信、源EES与目标EES之间的通信连接的类型、源EES与目标EES之间的通信连接的质量参数。其中，对目标EES的通信需求可以包含在应用客户端配置文件(AC profile)中，或者作为EAS的一种服务关键指标信息(service KPI)。
可选的，对目标EES的通信需求还可以包括ACR的完成时间。
EES之间的通信连接的类型可以但不限于包括：IP连接、专线连接、UPF隧道连接等等。
通信连接的质量参数可以但不限于包括：带宽、时延、抖动等。示例性的，时延可以为可接受的迁移时长、期望的迁移时长等。其中，EES之间的通信连接的质量可以一段时间内统计的数值，也可以是实时数值，也可以是预测的数值。
可以理解的，“目标EES支持与所述源EES进行通信”可以是隐式指示的，例如，当源EES与目标EES之间的通信需求包括源EES与目标EES之间的通信连接的类型、源EES与目标EES之间的通信连接的质量参数时，可以隐式指示目标EES需要支持与所述源EES进行通信。
示例性的，对于隐式指示方式，对目标EES的通信需求，亦即ACR的需求，可以包含在应用客户端配置文件(AC profile)，或者边缘应用服务器配置文件(EAS profile)中，则该消息中可以携带应用客户端标识(AC ID)或者边缘应用服务器标识(EAS ID)或者边缘应用服务器端点信息(EAS endpoint)(可以是FQDN，IP地址，URI，URL等格式)，ECS可以使用上述信息为索引在ECS本地或EES或边缘管理系统中获取到“对目标EES的通信需求”具体参数信息。
可选的，请求消息中还可以携带源EES的信息，例如源EES的标识或端点信息等等。该源EES为EEC连接的，为EEC提供边缘服务的EES，该源EES为源EAS所注册的EES，并且该源EES可以为该EAS提供边缘服务，其中，源EAS为终端设备上即将进行应用上下文迁移的应用客户端所连接的EAS。
可选的，终端设备发送的请求消息可以指示目标EES用于应用上下文迁移，或者，请求消息可以指示发现EES是为了与源EES执行应用上下文迁移。
可选的，请求消息中可以显示携带指示信息，该指示信息用于指示目标EES用于应用上下文迁移，或者，指示发现EES是为了与源EES执行应用上下文迁移。或者，请求消息可以隐式指示目标EES用于应用上下文迁移或者发现EES是为了与源EES执行应用上下文迁移，例如，若请求消息携带源EES的信息和/或对目标EES的通信需求，可以隐式指示目标EES用于应用上下文迁移或者发现EES是为了与源EES执行应用上下文迁移。
可选的，该请求消息中还可以包含EEC的安全凭证、终端设备的标识如GPSI等、连接信息、的位置和AC profile等。
S611，ECS向终端设备发送服务配置请求的响应消息，该响应消息携带第三EES的信息，其中，第三EES包括一个或多个满足该通信需求的EES。
S612，终端设备(例如终端设备的EEC)向第三EES中的EES 2发送EAS发现请求消息，该EAS发现请求消息可以携带EAS发现过滤器，EAS发现过滤器可以包括EAS的过滤参数。
可选的，ECS还可以触发核心网设备在源EES连接的UPF网元与目标EES(即EES 2)连接的UPF网元之间建立UPF隧道。可以参阅本申请实施例七。
S612与S606类似，具体可以参阅上述步骤S606，这里不再重复赘述。
S613，EES 2向终端设备发送EAS发现请求消息的响应消息，该响应消息携带第二EAS，其中，第二EAS包括一个或多个满足EAS发现过滤器的EAS。
S614，终端设备选择第二EAS中的EAS 2作为目标EAS。
S614与S608类似，具体可以参阅上述步骤S608，这里不再重复赘述。
S615，终端设备(例如终端设备的AC)触发应用上下文从EAS 1传输到EAS 2。
S616，终端设备将应用连接从EAS 1切换到EAS 2，与EAS 2进行应用层逻辑的交互。
其中，步骤S612～S616均为可选的步骤。
通过实施例一的方案，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例二：
本申请实施例二可以应用于由源EAS发起的应用上下文迁移(应用迁移)的场景。
如图7所示，为实施例二的具体流程，该流程可以包括但不限于EES的注册流程、终端设备初始接入EAS的过程、以及应用上下文迁移的过程。
其中，EES的注册流程可以参阅实施例中步骤S601～S602所述注册流程，这里不再重复赘述，EES的注册流程为可选的步骤。
终端设备初始接入EAS的过程参阅实施例中步骤S603～S608所述终端设备初始接入EAS的过程，这里不再重复赘述，终端设备初始接入EAS的过程为可选的步骤。
应用上下文迁移的过程具体可以包括：
S709，EAS 1检测到触发应用上下文迁移的事件发生。
示例性的，触发应用上下文迁移的事件可以但不限于包括：终端设备移动出当前EAS的服务区域，或EEC收到SMF的新建会话的消息，或EEC收到一个新的IP前缀等等。
S710，EAS 1向EES 1发送第一EAS发现请求，第一EAS发现请求用于获取应用上下文迁移的目标EAS，且第一EAS发现请求指示应用上下文迁移的通信需求(或者也可以称为对目标EAS/EES的通信需求)。
其中，该第一EAS发现请求可以指示对应用上下文迁移的通信需求可以是在该第一EAS发现请求消息中显式携带具体的通信需求参数，或者也可以是隐式指示方式，即该第一EAS发现请求消息中携带对目标EES的通信需求所属配置文件的索引或指针或句柄。
示例性的，对于显式指示方式，第一EAS发现请求中携带具体的应用上下文迁移的通信需求的参数。
示例性的，对于隐式指示方式，应用上下文迁移的通信需求可以包含在应用客户端配置文件(AC profile)，或者边缘应用服务器配置文件(EAS profile)中，则该第一EAS发现请求消息中可以携带应用客户端标识(AC ID)或者边缘应用服务器标识(EAS ID)或者边缘应用服务器端点信息(EAS endpoint)(可以是FQDN，IP地址，URI，URL等格式)，EES可以使用上述信息为索引在EES本地或边缘管理系统中获取到“应用上下文迁移的通信需求”具体参数信息。
可选的，第一EAS发现请求中还可以携带EAS 1的标识、EAS发现过滤器。其中，EAS发现过滤器可以参阅上述实施例一中S606所述的EAS发现过滤器。其中，应用上下文迁移的通信需求也可以包含在EAS发现过滤器中。
可选的，第一EAS发现请求中还可以携带目标DNAI。
应用上下文迁移的通信需求可以包括如下信息中至少一项：目标EES支持与所述源EES进行通信、迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数。
可选的，对目标EES的通信需求还可以包括ACR的完成时间。
迁移所述应用上下文的通信连接的类型可以但不限于包括：IP连接、专线连接、UPF隧道连接等等。
迁移所述应用上下文的通信连接的质量参数可以但不限于包括：带宽、时延、抖动等。示例性的，时延可以为可接受的迁移时长、期望的迁移时长等。其中，EES之间的通信连接的质量可以一段时间内统计的数值，也可以是实时数值，也可以是预测的数值。
可以理解的，“目标EES支持与所述源EES进行通信”可以是隐式指示的，例如，当迁移应用上下文的通信需求包括迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数时，可以隐式指示目标EES需要支持与所述源EES进行通信。
其中，步骤S709和S710均为可选的步骤。
S711，EES 1向ECS发送请求消息，该请求消息用于获取用于应用上下文迁移的目标EES，且该请求消息指示对目标EES的通信需求。
其中，对目标EES的通信需求的具体参数，可以是等同于EAS发送的应用上下文迁移的通信需求，也可以是EES 1根据应用上下文迁移的通信需求生成新的目标EES的通信需求的具体参数。
该请求消息，与本申请实施例一中S610所述服务配置请求类似，具体可以参阅本申请实施例一中步骤S610中相关描述，这里不再重复赘述。
S712，ECS向EES 1发送请求消息的响应消息，该响应消息携带第二EES的信息，第二EES可以包括一个或多个满足该通信需求的EES。
S713，EES 1向上述第二EES中的EES 2发送第二EAS发现请求消息，该第二EAS发现请求消息可以携带EAS发现过滤器，EAS发现过滤器可以包括EAS的过滤参数。
其中，EAS发现过滤器可以为第一EAS发现请求中所携带的EAS发现过滤器。
可选的，ECS还可以触发核心网设备在源EES(即EES 1)连接的UPF网元与目标EES(即EES 2)连接的UPF网元之间建立UPF隧道。可以参阅本申请实施例七。
S714，EES 2向EES 1发送第二EAS发现请求消息的响应消息，该响应消息携带第二EAS的信息，第二EAS包括一个或多个满足要求的EAS。
S715，EES 1向EAS 1发送第一EAS发现请求消息的响应消息，该响应消息携带第二EAS。
S716，EAS 1将应用上下文从EAS 1传输到EAS 2。
其中，EAS 2为EAS 1从上述第二EAS中选择的目标EAS。
S717，终端设备将应用连接从EAS 1切换到EAS 2，与EAS 2进行应用层逻辑的交互。
其中，步骤S713～S717均为可选的步骤。
通过实施例二的方案，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例三：
如图8所示，为实施例三的具体流程，该流程可以包括但不限于EES的注册流程、终端设备初始接入EAS的过程、以及应用上下文迁移的过程。
其中，EES的注册流程可以参阅实施例中步骤S601～S602所述注册流程，这里不再重复赘述，EES的注册流程为可选的步骤。
终端设备初始接入EAS的过程参阅实施例中步骤S603～S608所述终端设备初始接入EAS的过程，这里不再重复赘述，终端设备初始接入EAS的过程为可选的步骤。
S809，EAS 1向EES 1发送第一消息，该第一消息用于请求EES 1管理终端设备的应用上下文的迁移，且第一消息指示迁移应用上下文的通信需求。示例性的，该第一请求消息可以是full ACR request。
示例性的，EES 1管理终端设备的应用上下文的迁移，可以包括：EES 1负责触发事件监测、目标EAS的发现、应用上下文的从源EAS到目标EAS的传输(或称转移)、对EAS和EEC的应用上下文迁移进展的通知(如选中的目标EAS、应用上下文迁移完成)、影响网络用户面的路由等。
迁移应用上下文的通信需求具体可以参阅上述实施例二的S710中关于迁移应用上下文的通信需求的相关描述，这里不再重复赘述。
S810，EES 1检测到触发应用上下文迁移的事件发生。
示例性的，触发应用上下文迁移的事件可以但不限于包括：终端设备移动出当前EAS的服务区域，或EEC收到SMF的新建会话的消息，或EEC收到一个新的IP前缀等等。
其中，步骤S809～S810均为可选的步骤。
S811～S814具体可以参阅上述实施例二的S711～S714，这里不再重复赘述。
S815，EES 1向EAS 1发送同第一通知消息，该第一通知消息用于指示EAS 1冻结终端设备的应用上下文或者指示应用上下文的传输即将开始。
S816，EES 1将应用上下文从EAS 1传输到EAS 2。
可选的，该应用上下文可以存储在EES 1和EAS 1均可以访问的共享区域。
S817，EES 1向终端设备发送第二通知消息，第二通知消息用于通知终端设备切换到EAS 2，或指示应用上下文迁移完成。
可选地，第二通知消息还可以包含EAS2的信息。
S818，终端设备将应用连接从EAS 1切换到EAS 2，与EAS 2进行应用层逻辑的交互。
其中，步骤S813～S818均为可选的步骤。
通过实施例三的方案，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例四：
本申请实施例四可以应用于由终端设备(例如终端设备中的EEC)发起应用上下文迁移(应用迁移)的场景。
如图9所示，为实施例四的具体流程，该流程可以包括但不限于EES的注册流程、终端设备初始接入EAS的过程、以及应用上下文迁移的过程。
其中，EES的注册流程可以参阅实施例中步骤S601～S602所述注册流程，这里不再重复赘述，EES的注册流程为可选的步骤。
终端设备初始接入EAS的过程参阅实施例中步骤S603～S608所述终端设备初始接入EAS的过程，这里不再重复赘述，终端设备初始接入EAS的过程为可选的步骤。
应用上下文迁移的过程具体可以包括：
S909～S911，与上述实施例一的S609～S611类似，区别在于：实施例一的S610中服务配置请求指示对目标EES的通信需求，而实施例四的S910中服务配置请求没有指示对目标EES的通信需求。实施例一的S611中ECS反馈的第二EES中包括的EES均满足该通信需求，而实施例四的S911中ECS反馈的第二EES中可能存在不满足通信需求的EES。
S912，终端设备(例如终端设备的EEC)向第二EES中的EES 2发送EAS发现请求消息，该EAS发现请求消息可以指示应用上下文迁移的需求。
可选地，该请求消息中还携带ACR指示信息，该指示信息用于指示该请求消息用于发现EAS将用于应用上下文迁移，或指示该请求消息请求发现的EAS用于应用上下文迁移。
其中，应用上下文迁移的需求具体可以参阅上述三个实施例中对目标EES的通信需求的相关描述，这里不再重复赘述。
可选的，该EAS发现请求消息可以携带EAS发现过滤器，EAS发现过滤器可以参阅上述实施例一的S606中EAS发现过滤器的相关描述，这里不再重复赘述。其中，应用上下文迁移的需求的具体参数可以包含在EAS发现过滤器中。
S913，EES 2判断是否和EES 1存在满足该应用上下文迁移的需求。若否，执行步骤S914；若是，执行步骤S915。
可选的，EES 2也可以向ECS发送请求消息，该请求消息携带EES 1的信息、EES 2的信息以及源EES与所述目标EES之间的通信需求。从而ECS可以判断EES 2是否和EES 1存在满足该通信需求的通信连接。
S914，EES 2向终端设备发送失败指示。其中，该失败指示可以指示无满足通信需求的EAS，或者不能满足该通信需求。
可选的，该失败指示还可以指示不满足通信需求中的哪一项，例如，可以指示不支持与源EES进行通信、指示与源EES之间不存在通信需求要求的通信连接类型、指示与源EES之间的通信连接不满足通信需求要求的通信质量等等。
可选的，EES 2还可以触发核心网设备在EES 1连接的UPF与EES 2连接的UPF之间建立UPF隧道。其中，ECS触发核心网设备在EES 1连接的UPF与EES 2连接的UPF之间建立UPF隧道的过程可以参阅本申请实施例七。
其中，S914为一个可选的步骤。
S915，EES 1向终端设备发送EAS发现请求消息的响应消息，该响应消息携带第二EAS的信息，第二EAS包括一个或多个满足该通信需求的EAS。
S916，终端设备选择第二EAS中的EAS 2作为目标EAS。
S917，应用上下文从EAS 1传输到EAS 2。
示例性的，可以是EAS 1通过推送方式发给EAS 2，也可以是EAS 2通过拉取方式获取到应用上下文。
可选的，EES 2可以向EAS 2发送第一通知消息，该通知消息可以携带EAS 1的信息。
S918，EAS 2向EES 2发送第二通知消息，该第二通知消息可以指示应用上下文传输完成，或者应用上下文准备完毕，可以为用户提供服务。其中，S918可以为一个可选的步 骤。
S919，EES 2向终端设备发送第三通知消息。该第三通知消息可以用于指示终端设备将应用连接切换到EAS 2。
S920，终端设备将应用连接从EAS 1切换到EAS 2，与EAS 2进行应用层逻辑的交互。
其中，S906～S920均为可选的步骤。
通过实施例四的方案，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例五：
本申请实施例五可以应用于由终端设备发起的应用上下文迁移(应用迁移)的场景。
如图10所示，提供实施例二的具体流程，该流程可以包括但不限于EES的注册流程、终端设备初始接入EAS的过程、以及应用上下文迁移的过程。
其中，EES的注册流程可以参阅实施例中步骤S601～S602所述注册流程，这里不再重复赘述。EES的注册流程为可选的步骤。
终端设备初始接入EAS的过程具体可以包括：
S1003，终端设备(例如，可以是终端设备的EEC)向ECS发送服务配置请求，该请求消息用于发现EES。
该请求消息中可以包含EEC的安全凭证、终端设备的标识如GPSI等、连接信息、终端设备的位置和终端设备中AC profile等。
S1004，ECS对终端设备进行授权检查。
如果检查通过后，ECS可以根据服务配置请求选择第一EES，第一EES包括一个或多个EES。例如ECS可以选择服务区域中包含该终端设备的位置的EES，或者选择注册的EAS列表中包括匹配AC profile的EAS ID的EES等。
S1005，ECS向终端设备发送服务配置请求的响应消息，该响应消息携带第一EES的信息，以及第一EES的连接拓扑信息。
其中，第一EES的连接拓扑信息可以参阅上述实施例一的S601中关于第一EES的连接拓扑信息的描述。
S1006～S1008可以参阅上述实施例一的S606～S608，这里不再重复赘述。
需要说明的是，该终端设备初始接入EAS的过程为可选的步骤。
应用上下文迁移的过程具体可以包括：
S1009，终端设备确定触发应用上下文迁移的事件发生。
例如，终端设备检测到触发应用上下文迁移的事件发生，或者，EES 1检测到触发应用上下文迁移的事件发生并通知给终端设备。
示例性的，触发应用上下文迁移的事件可以但不限于包括：终端设备移动出当前EAS的服务区域，或EEC收到SMF的新建会话的消息，或EEC收到一个新的IP前缀等等。
其中，S1009为一个可选的步骤。
S1010，终端设备(例如，可以是终端设备的EEC)向ECS发送服务配置请求，该请求消息用于发现EES。
S1011，ECS向终端设备发送服务配置请求的响应消息，该响应消息携带第二EES的信息，其中，第二EES包括一个或多个EES。
S1012，终端设备在该第二EES中选择一个满足通信需求的EES 2作为目标EES。
其中，通信需求可以参阅上述实施例中对目标EES的通信需求或者应用上下文迁移的通信需求，这里不再重复赘述。
S1013～S1017可以上述实施例一的S612～S616，这里不再重复赘述。
通过实施例五的方案，使得在进行应用上下文切换时，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例六：
如图11所示，实施例六的具体流程可以但不限于包括：
S1101，NRF网元或UDR网元或NEF网元接收第一EES的拓扑连接信息。其中，第一EES的拓扑连接信息可以参阅上述实施例一的相关描述，这里不再赘述。
一种实现方式中，NRF网元可以接收第一EES的注册消息，注册消息中包含第一EES的配置信息，第一EES的配置信息包含EES的拓扑连接信息。
一种实现方式中，UDR网元可以通过服务参数预配消息从第一EES或ECS获取第一EES的配置信息，第一EES的配置信息包含第一EES的拓扑连接信息。或者，第一EES或ECS将第一EES的拓扑连接信息发送给UDR网元，还可以将第一EES端点信息、第一EES关联的DNAI发送给UDR网元。该实现方式也适用于NEF网元。
S1102，NRF网元或UDR网元或NEF网元保存第一EES的拓扑连接信息。
其中，步骤S1101和S1102为可选的步骤。
S1103，AF网元(例如可以是源ESS)向PCF网元/NEF网元发送请求消息，所述请求消息用于订阅DNAI变化事件，且所述请求消息包含对目标DNAI的通信需求。
所述对目标DNAI的通信需求包括如下信息中至少一项：所述目标DNAI对应的所述目标EES支持与所述源EES进行通信、所述源EES与所述目标DNAI对应的目标EES之间的通信连接的类型、所述源EES与所述目标DNAI对应的所述目标EES的通信连接的质量参数。
可选的，对目标DNAI的通信需求还可以包括ACR的完成时间。
通信连接的类型、通信连接的质量参数可以参阅上述实施例中的相关描述。
S1104，PCF网元在SMF会话中将该通信需求发送给SMF网元。
其中，步骤S1103和S1104为可选的步骤。
S1105，SMF网元检测到第一事件，所述第一事件用于SMF网元选择新的DNAI。
S1106，SMF网元确定目标DNAI，所述目标DNAI对应的目标EES支持与所述源EES进行通信。
一种实现方式中，SMF网元可以根据该通信需求以及第一EES的连接拓扑信息确定一个目标DNAI，该目标DNAI对应的EES与源DNAI对应的源EES有符合该通信需求的通信连接。
其中，SMF网元可以从UDR网元获取EES的拓扑连接信息，或者从NRF网元获取EES的拓扑连接信息，或者从NEF网元获取EES的拓扑连接信息，或者SMF网元从本地获取预配置EES的拓扑连接信息。
S1107，SMF网元向AF网元发送通知消息，该通知消息可以携带目标DNAI的信息。
可选地，该通知消息还可以携带指示信息，指示信息用于指示目标DNAI对应的EES 与源EES有满足通信要求的通信连接。
本申请实施例六中，由网络侧在选择DNAI时候就选择与源EES有通信连接的EES对应的DNAI，进而保障该目标DNAI对应的EES与源EES有通信连接，可以避免选择一个与源EES没有通信连接，或者通信连接类型或通信连接质量不能满足应用上下文迁移的目标EES，从而可以保证应用的业务连续性。
实施例七：
本申请实施例七提供的一种在两个EES分别连接的UPF之间建立UPF隧道的方法。如图12所示，实施例七的具体流程可以包括但不限于：
S1201，源AF网元向第一SMF网元发送第一消息，该第一消息用于请求在源UPF网元和目标UPF网元之间建立UPF隧道。其中，该第一请求消息可以包括目标路由信息，该目标路由信息可以用于确定目标UPF网元。
其中，源UPF网元可以为源EES连接的UPF网元。目标UPF网元可以为目标EES连接的UPF网元。
示例性的，该第一消息可以称为传输服务请求。
可选的，该第一消息中可以包含QoS需求。还可以包括终端设备的标识或IP地址。
该第一消息中还可以包含源路由信息，源路由信息可以用于确定源UPF，或者，源路由信息也可以用于确定数据的发送端。
其中，源AF网元可以是源EES。
或者，步骤S1201也可以由目标AF网元执行，例如目标EES。或者，也可以由ECS执行。
一种实现方式中，AF网元也可以向PCF网元发送该第一消息，PCF网元将该第一消息中携带的信息发送给第一SMF网元。其中AF也可以经过NEF向PCF发送该第一消息。
一种可能的实施方式中，SMF网元也可以根据终端设备的标识或IP地址确定该终端设备对应的源UPF网元的源路由信息。
S1202，第一SMF网元寻找能服务目标路由信息的第二SMF网元。
一种实现方式中，如果目标路由信息在第一SMF网元的服务范围内，第二SMF网元与第一SMF网元为同一个SMF网元，则第一SMF网元可以在本地选择对应于目标路由信息的目标UPF网元。
如果目标路由信息不在第一SMF网元的服务范围内，第一SMF网元可以通过NRF网元发现服务目标路由信息的第二SMF网元。
可选的，如果第二SMF网元与第一SMF网元为两个不同的网元，可以执行如下S1203a～S1203e：
S1203a，第一SMF网元可以向第二SMF网元发送第二消息，所述第二消息用于请求在源UPF网元和目标UPF网元之间建立UPF隧道。该第二消息中可以包含QoS需求、目标路由信息、以及源路由信息。
S1203b，第二SMF网元选择对应于目标路由信息的目标UPF。其中，第二SMF可以根据目标路由信息选择目标UPF。
S1203c，第二SMF网元向选择的目标UPF网元发送第三消息，该第三消息中可以包含转发规则，转发规则指示源UPF网元将来自所述源AF的数据向目标UPF网元进行转发，所述转发规则携带源UPF网元的隧道信息。例如转发规则包含源AF的IP地址和端口号， 则指示源UPF在收到数据包的源地址为该源AF的IP地址和端口号的数据包，则向目标UPF网元转发。再例如，转发规则包含源AF的IP地址和端口号目标AF的IP地址和端口号，则指示源UPF在收到数据包的源地址为该源AF的IP地址和端口号且目的地址为AF的IP地址和端口号目标AF的IP地址和端口号的数据包，则向目标UPF网元转发。
可选的，该第三消息中还可以包含QOS需求。
S1203d，目标UPF网元向第二SMF网元发送第三消息的响应消息。
S1203e，第二SMF网元向第一SMF网元发送第二消息的响应消息，该响应消息中包含目标UPF网元的隧道信息，该隧道信息可以包含IP地址和端口号。
S1204，第一SMF网元向源UPF网元发送第四消息，该第四消息中包含上述转发规则，转发规则指示目标UPF网元将来自所述源UPF的数据向目标AF网元进行转发，转发规则携带目标UPF网元的隧道信息。例如，转发规则包含源UPF的IP地址和端口号目标AF的IP地址和端口号，则指示目标UPF在收到数据包的源地址为该源UPF的IP地址和端口号且目的地址为AF的IP地址和端口号目标AF的IP地址和端口号的数据包，则向目标UPF网元转发。
S1205，源UPF网元向第一SMF网元发送第四消息的响应消息。
S1206，第一SMF/PCF向AF网元发送第一消息的响应消息，该响应消息中可以携带服务接口信息(例如源UPF的IP地址和端口号)，该服务接口信息可以由第一SMF网元或者源UPF网元分配，用于源EES发送应用上下文数据。
S1207，源AF网元将应用上下文数据发送至源UPF网元，源UPF网元将该应用上下文数据发给目标UPF网元，目标UPF网元向目标AF网元转发该应用上下文数据。
其中源AF可以为源EES，或源EAS，目标AF可以为对应的目标EES或目标EAS。或者源AF为ECS，则源路由信息用于指示源EES，目标路由信息用于指示目标EES，此时发数据的可以不再是源AF，而是数据的发端，则转发规则中的包含的不再是源AF的IP地址或端口号，而是包含的数据发端的IP地址或端口号。
基于以上实施例，本申请实施例还提供了一种通信装置，参阅图13所示，通信装置1300可以包括处理单元1301和收发单元1302。其中，所述收发单元1302用于所述通信装置1300进行通信传输，例如，上述实施例一～实施例七中接收信息(帧、消息或数据)或发送信息(帧、消息或数据)，所述处理单元1301用于执行收发动作以外的动作，例如确定动作、判断动作、选择动作、对所述通信装置1300的动作进行控制管理，等等。所述处理单元1301还可以控制所述收发单元1302执行的步骤。
示例性的，该通信装置1300可以是上述实施例中的通信设备，或通信设备中的处理器，或者通信设备中的芯片或者芯片系统，或者是通信设备中的一个功能模块等，其中，通信设备可以为ECS或者终端设备或者EES或者EAS或者SMF等等。
具体的，在所述通信装置1300用于实现上述图6-图8所示的实施例中ECS的功能时，具体可以包括：
收发单元1302，用于接收第一请求消息，所述第一请求消息用于发现EES，且所述请求消息指示对目标EES的通信需求；处理单元1301，用于确定至少一个满足所述通信需求的EES；所述收发单元1302，还用于：发送响应消息，所述响应消息携带所述至少一个EES的信息。
可选的，所述收发单元1302，还用于：在接收所述第一请求消息之前，分别接收第一 EES的配置信息，所述第一EES包括源EES和/或所述目标EES，其中，所述第一EES的配置信息包括支持与所述第一EES进行通信的第二EES的信息。
示例性的，所述第一EES的配置信息还包括所述第一EES与所述第二EES之间的通信连接的信息。
示例性的，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。
示例性的，所述第一请求消息携带源EES的信息。
示例性的，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。
在所述通信装置1300用于实现上述图6所示的实施例中终端设备的功能时，具体可以包括：收发单元1302，用于与ECS进行通信；处理单元1301，用于通过所述收发单元1302向所述ECS发送第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述第一请求消息指示对目标EES的通信需求；以及，通过所述收发单元1302接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述通信需求的EES的信息。
示例性的，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。
示例性的，所述第一请求消息携带源EES的信息。
示例性的，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。
在所述通信装置1300用于实现上述图7或图8所示的实施例中源EES(即EES 1)的功能时，具体可以包括：收发单元1302，用于与ECS进行通信；处理单元1301，用于通过所述收发单元1302向所述ECS发送第一请求消息，所述第一请求消息用于发现EES，且所述第一请求消息指示所述对目标EES的第一通信需求；以及，通过所述收发单元1302接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述第一通信需求的EES的信息。
可选的，所述处理单元1301，还用于：通过所述收发单元1302接收来自第一EAS的第二通信需求，所述第二通信需求用于指示所述EAS对所述应用上下文迁移的通信需求。
示例性的，所述第二通信需求包括迁移所述应用上下文的通信连接的质量参数和/或迁移所述应用上下文的通信连接的类型。
示例性的，所述第二通信需求还包括如下信息中至少一项：所述目标EES支持与所述第一EES进行通信、所述第一EES与所述目标EES之间的通信连接的类型、所述第一EES与所述目标EES之间的通信连接的质量参数。
示例性的，所述第一请求消息携带所述第一EES的信息。
示例性的，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上行文迁移。
在所述通信装置1300用于实现上述图9所示的实施例中目标EES(即EES 2)的功能时，具体可以包括：收发单元1302，用于：接收来自终端设备的第一请求消息，所述第一请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服 务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；处理单元1301，用于确定存在满足所述通信需求的EAS；所述收发单元1302，还用于当所述处理单元1301确定存在满足所述通信需求的EAS时，向所述终端设备发送响应消息，所述响应消息携带所述通信需求的EAS的信息。
示例性的，所述通信需求包括：所述目标EES支持与源EES进行通信、迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数。
在所述通信装置1300用于实现上述图9所示的实施例中终端设备的功能时，具体可以包括：收发单元1302，用于与目标EES进行通信；处理单元1301，用于通过所述收发单元1302向所述目标EES发送第一请求消息，所述请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；以及，通过所述收发单元1302接收来自所述目标EES的响应消息，所述响应消息包含满足所述通信需求的EAS的信息。
示例性的，所述通信需求包括：所述目标EES支持与源EES进行通信、迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
可以理解的是，本申请实施例中各个模块的功能或者实现可以进一步参考方法实施例的相关描述。
一种可能的方式中，通信装置可以如图14所示，该装置可以是通信设备或者通信设备中的芯片，其中该通信设备可以为上述实施例中的ECS或者终端设备或者EES。该装置可以包括处理器1401，通信接口1402，存储器1403。其中，处理单元1301可以为处理器1401。收发单元1302可以为通信接口1402。
处理器1401，可以是一个CPU，或者为数字处理单元等等。通信接口1402可以是收发器、也可以为接口电路如收发电路等、也可以为收发芯片等等。该装置还包括：存储器1403，用于存储处理器1401执行的程序。存储器1403可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器1403是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质，但不限于此。
处理器1401用于执行存储器1403存储的程序代码，具体用于执行上述处理单元1301 的动作，本申请在此不再赘述。通信接口1402具体用于执行上述收发单元1302的动作，本申请在此不再赘述。
本申请实施例中不限定上述通信接口1402、处理器1401以及存储器1403之间的具体连接介质。本申请实施例在图14中以存储器1403、处理器1401以及通信接口1402之间通过总线1404连接，总线在图14中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例还提供了一种计算机可读存储介质，用于存储为执行上述处理器所需执行的计算机软件指令，其包含用于执行上述处理器所需执行的程序。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的通信方法。
本申请实施例还提供一种芯片，所述芯片与存储器耦合，所述芯片用于实现上述方法实施例提供的通信方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    边缘配置服务器ECS接收第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述请求消息指示对目标EES的通信需求；
    所述ECS确定至少一个满足所述通信需求的EES；
    所述ECS发送响应消息，所述响应消息携带所述至少一个EES的信息。
  2. 如权利要求1所述的方法，其特征在于，在边缘配置服务器ECS接收所述第一请求消息之前，所述方法还包括：
    所述ECS分别接收第一EES的配置信息，所述第一EES包括源EES和/或所述目标EES，其中，所述第一EES的配置信息包括支持与所述第一EES进行通信的第二EES的信息。
  3. 如权利要求2所述的方法，其特征在于，所述第一EES的配置信息还包括所述第一EES与所述第二EES之间的通信连接的信息。
  4. 一种通信方法，其特征在于，包括：
    终端设备向边缘配置服务器ECS发送第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述第一请求消息指示对目标EES的通信需求；
    所述终端设备接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述通信需求的EES的信息。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。
  6. 如权利要求1-5任一项所述的方法，其特征在于，所述第一请求消息携带源EES的信息。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。
  8. 一种通信方法，其特征在于，包括：
    第一边缘使能服务器EES向边缘配置服务器ECS发送第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述第一请求消息指示对目标EES的第一通信需求；
    所述第一EES接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述第一通信需求的EES的信息。
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第一EES接收来自第一边缘应用服务器EAS的第二通信需求，所述第二通信需求用于指示所述EAS对所述应用上下文迁移的通信需求。
  10. 如权利要求9所述的方法，其特征在于，所述第二通信需求包括迁移所述应用上下文的通信连接的质量参数和/或迁移所述应用上下文的通信连接的类型。
  11. 如权利要求8-10任一项所述的方法，其特征在于，所述第二通信需求还包括如下信息中至少一项：所述目标EES支持与所述第一EES进行通信、所述第一EES与所述目标EES之间的通信连接的类型、所述第一EES与所述目标EES之间的通信连接的质量参数。
  12. 如权利要求8-11任一项所述的方法，其特征在于，所述第一请求消息携带所述第一EES的信息。
  13. 如权利要求8-12任一项所述的方法，其特征在于，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上行文迁移。
  14. 一种通信方法，其特征在于，包括：
    目标边缘使能服务器EES接收来自终端设备的第一请求消息，所述第一请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；
    当所述目标EES确定存在满足所述通信需求的EAS时，所述目标EES向所述终端设备发送响应消息，所述响应消息携带所述通信需求的EAS的信息。
  15. 一种通信方法，其特征在于，包括：
    终端设备向目标边缘使能服务器EES发送第一请求消息，所述请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；
    所述终端设备接收来自所述目标EES的响应消息，所述响应消息包含满足所述通信需求的EAS的信息。
  16. 如权利要求14或15所述的方法，其特征在于，所述通信需求包括：所述目标EES支持与源EES进行通信、迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数。
  17. 一种通信装置，其特征在于，包括：
    收发单元，用于接收第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述请求消息指示对目标EES的通信需求；
    处理单元，用于确定至少一个满足所述通信需求的EES；
    所述收发单元，还用于：发送响应消息，所述响应消息携带所述至少一个EES的信息。
  18. 如权利要求17所述的装置，其特征在于，所述收发单元，还用于：
    在接收所述第一请求消息之前，分别接收第一EES的配置信息，所述第一EES包括源EES和/或所述目标EES，其中，所述第一EES的配置信息包括支持与所述第一EES进行通信的第二EES的信息。
  19. 如权利要求18所述的装置，其特征在于，所述第一EES的配置信息还包括所述第一EES与所述第二EES之间的通信连接的信息。
  20. 一种通信装置，其特征在于，包括：
    收发单元，用于与边缘配置服务器ECS进行通信；
    处理单元，用于通过所述收发单元向所述ECS发送第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述第一请求消息指示对目标EES的通信需求；以及，通过所述收发单元接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述通信需求的EES的信息。
  21. 如权利要求17-20任一项所述的装置，其特征在于，所述通信需求包括如下信息中至少一项：所述目标EES支持与源EES进行通信、所述源EES与所述目标EES之间的通信连接的类型、所述源EES与所述目标EES之间的通信连接的质量参数。
  22. 如权利要求17-21任一项所述的装置，其特征在于，所述第一请求消息携带源EES 的信息。
  23. 如权利要求17-22任一项所述的装置，其特征在于，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上下文迁移。
  24. 一种通信装置，其特征在于，包括：
    收发单元，用于与边缘配置服务器ECS进行通信；
    处理单元，用于通过所述收发单元向所述ECS发送第一请求消息，所述第一请求消息用于发现边缘使能服务器EES，且所述第一请求消息指示对目标EES的第一通信需求；以及，
    通过所述收发单元接收来自所述ECS的响应消息，所述响应消息携带至少一个满足所述第一通信需求的EES的信息。
  25. 如权利要求24所述的装置，其特征在于，所述处理单元，还用于：
    通过所述收发单元接收来自第一边缘应用服务器EAS的第二通信需求，所述第二通信需求用于指示所述EAS对所述应用上下文迁移的通信需求。
  26. 如权利要求25所述的装置，其特征在于，所述第二通信需求包括迁移所述应用上下文的通信连接的质量参数和/或迁移所述应用上下文的通信连接的类型。
  27. 如权利要求24-26任一项所述的装置，其特征在于，所述第二通信需求还包括如下信息中至少一项：所述目标EES支持与所述第一EES进行通信、所述第一EES与所述目标EES之间的通信连接的类型、所述第一EES与所述目标EES之间的通信连接的质量参数。
  28. 如权利要求24-27任一项所述的装置，其特征在于，所述第一请求消息携带所述第一EES的信息。
  29. 如权利要求24-28任一项所述的装置，其特征在于，所述第一请求信息携带指示信息，所述指示信息用于指示所述目标EES用于应用上行文迁移。
  30. 一种通信装置，其特征在于，包括：
    收发单元，用于：接收来自终端设备的第一请求消息，所述第一请求消息用于请求所述目标边缘使能服务器EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；
    处理单元，用于确定存在满足所述通信需求的EAS；
    所述收发单元，还用于当所述处理单元确定存在满足所述通信需求的EAS时，向所述终端设备发送响应消息，所述响应消息携带所述通信需求的EAS的信息。
  31. 一种通信装置，其特征在于，包括：
    收发单元，用于与目标边缘使能服务器EES进行通信；
    处理单元，用于通过所述收发单元向所述目标EES发送第一请求消息，所述请求消息用于请求所述目标EES发现迁移所述终端设备的应用上下文的目标边缘应用服务器EAS，且所述请求消息包含对应用上下文迁移的通信需求；以及
    通过所述收发单元接收来自所述目标EES的响应消息，所述响应消息包含满足所述通信需求的EAS的信息。
  32. 如权利要求30或31所述的装置，其特征在于，所述通信需求包括：所述目标EES支持与源EES进行通信、迁移所述应用上下文的通信连接的类型、迁移所述应用上下文的通信连接的质量参数。
  33. 一种计算机可读存储介质，其特征在于，所述计算机存储介质中存储有计算机可读指令，当所述计算机可读指令在通信装置上运行时，如权利要求1～16任一项所述的方法被执行。
PCT/CN2021/133186 2021-02-24 2021-11-25 一种通信方法及装置 WO2022179218A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110209614.0A CN114980223A (zh) 2021-02-24 2021-02-24 一种通信方法及装置
CN202110209614.0 2021-02-24

Publications (1)

Publication Number Publication Date
WO2022179218A1 true WO2022179218A1 (zh) 2022-09-01

Family

ID=82973125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/133186 WO2022179218A1 (zh) 2021-02-24 2021-11-25 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN114980223A (zh)
WO (1) WO2022179218A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067547A1 (zh) * 2022-09-30 2024-04-04 华为技术有限公司 用于获取终端信息的方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190191344A1 (en) * 2017-12-15 2019-06-20 Industrial Technology Research Institute Mobile edge platform servers and user equipment context migration management methods thereof
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置
CN112187495A (zh) * 2019-07-01 2021-01-05 阿里巴巴集团控股有限公司 终端与服务器的通信方法、通信系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190191344A1 (en) * 2017-12-15 2019-06-20 Industrial Technology Research Institute Mobile edge platform servers and user equipment context migration management methods thereof
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置
CN112187495A (zh) * 2019-07-01 2021-01-05 阿里巴巴集团控股有限公司 终端与服务器的通信方法、通信系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Target EAS selection", 3GPP DRAFT; S6-202169, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20201116 - 20201124, 11 November 2020 (2020-11-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051953648 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067547A1 (zh) * 2022-09-30 2024-04-04 华为技术有限公司 用于获取终端信息的方法和装置

Also Published As

Publication number Publication date
CN114980223A (zh) 2022-08-30

Similar Documents

Publication Publication Date Title
US11122027B2 (en) End-to-end M2M service layer sessions
JP6785376B2 (ja) ＩｏＴデバイスコネクティビティ、ディスカバリ、ネットワーキング
US11671373B2 (en) Systems and methods for supporting traffic steering through a service function chain
WO2022012310A1 (zh) 一种通信方法及装置
EP3836515B1 (en) Communication method and communication device for reducing complexity in processing of service instances.
CN111279316A (zh) 网络中的应用功能及其控制
EP4192184A1 (en) Pdu session establishment method, terminal device, and chip system
WO2022048261A1 (zh) 边缘应用发现方法及装置、边缘应用服务支持方法及装置
JP6982100B2 (ja) Ｉｐバージョンの選択
WO2021218595A1 (zh) 一种地址获取方法及装置
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
WO2022179218A1 (zh) 一种通信方法及装置
Shetty et al. 5G Overview
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2020211538A1 (zh) 一种数据传输方法及装置
WO2023143212A1 (zh) 一种通信方法及装置
JP2022502975A (ja) サイドリンクリソース制御のための方法および装置
WO2022141528A1 (zh) 一种确定mec接入点的方法及装置
WO2024032245A1 (zh) 通信方法和通信装置
WO2023185690A1 (zh) 一种通信方法、装置及设备
WO2022160861A1 (zh) 通信方法及装置
TWI836328B (zh) 通信方法及裝置
WO2023050781A1 (zh) 一种通信方法及通信装置
US20240121309A1 (en) Managing content provider multi-path policies
WO2023151491A1 (zh) 请求应用功能的方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21927642

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21927642

Country of ref document: EP

Kind code of ref document: A1