WO2022067830A1 - 一种应用上下文的迁移方法及装置 - Google Patents

一种应用上下文的迁移方法及装置 Download PDF

Info

Publication number
WO2022067830A1
WO2022067830A1 PCT/CN2020/119763 CN2020119763W WO2022067830A1 WO 2022067830 A1 WO2022067830 A1 WO 2022067830A1 CN 2020119763 W CN2020119763 W CN 2020119763W WO 2022067830 A1 WO2022067830 A1 WO 2022067830A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
information
context
application context
edge
Prior art date
Application number
PCT/CN2020/119763
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 华为技术有限公司
Priority to EP20955850.1A priority Critical patent/EP4210360A4/en
Priority to JP2023519762A priority patent/JP2023544573A/ja
Priority to CN202080105719.5A priority patent/CN116325835A/zh
Priority to CA3194460A priority patent/CA3194460A1/en
Priority to AU2020470244A priority patent/AU2020470244A1/en
Priority to PCT/CN2020/119763 priority patent/WO2022067830A1/zh
Publication of WO2022067830A1 publication Critical patent/WO2022067830A1/zh
Priority to US18/192,980 priority patent/US20230239675A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • 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/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for migrating application contexts.
  • EES edge data network
  • EES edge application server
  • EES edge enabler server
  • EEC edge enabler client
  • the UE deployed with the AC may move.
  • the EAS currently providing services may not be able to continue to provide services for the AC currently running on the moving UE.
  • the application context related to the EAS currently providing the service needs to be migrated.
  • EEC or EES detects that application uplink migration is required, it is usually necessary to determine the target EAS for application context migration based on the communication method and discovery mechanism of the MEC architecture, and notify the EAS currently providing services to perform application context migration. In this way, there are many signaling interactions, and the delay is long, which affects the operation of the application.
  • the present application provides a method and device for migrating application contexts, so that by delegating the migration of application contexts to edge-enabled functional entities such as EEC/EES, the edge-enabled functional entities can decide to migrate application contexts by themselves, which can reduce signaling interaction, Shorten the latency of application context migration.
  • edge-enabled functional entities such as EEC/EES
  • an embodiment of the present application provides a method for migrating an application context, the method comprising: receiving first information from an application function entity, where the first information is used to instruct to migrate an application context associated with the application function entity ; when a triggering event for the migration of the application context occurs, determine to migrate the application context according to the first information.
  • the application function entity hosts the migration of its associated application context to the edge enabling function entity, and when the edge enabling function entity detects that the application context needs to be migrated, it can decide on its own to migrate the application context , which can reduce the signaling interaction for migrating application context, shorten the delay of application context migration, help the normal operation of the service, and reduce the time when the service operation of the terminal application client is affected or interrupted.
  • the method further includes: performing one or more of the following operations according to the first information: detecting a trigger event of the migration of the application context; discovering the target application function entity, The target application function entity is used for receiving the application context; transmitting the application context to the edge-enabled function entity associated with the target application function entity; sending the information of the target application function entity to the application function entity related terminal equipment; sending the application context migration information to the core network element; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.
  • the receiving the first information from the application function entity includes: receiving registration information from the application function entity, where the registration information includes the first information.
  • the method further includes: receiving first condition information from an application function entity, where the first condition information is used to indicate a first validation condition of the first information.
  • the first validating condition includes any one or more of the following: validating duration of the first information, validating period of the first information, applicable to the first information , the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application function entity is overloaded.
  • the method further includes: receiving second condition information from the application function entity, where the second condition information is used to indicate a second valid condition of the first information, the The second validating condition is different from the first validating condition.
  • the method further includes: receiving the application context from the application function entity.
  • the method before receiving the application context from the application function entity, the method further includes: sending a storage address of the application context to the application function entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • an embodiment of the present application provides a method for migrating application contexts, including: sending first information to an edge-enabled functional entity, where the first information is used to indicate an application context associated with the migrating application functional entity; receiving data from an edge-enabled functional entity Response information sent by the enabled functional entity in response to the first information.
  • the edge-enabled functional entity is hosted with the migration of the application context.
  • the edge-enabled functional entity detects that the application context needs to be migrated, it can decide to migrate the application context by itself, which can reduce the time required for migrating the application context. Signaling interaction shortens the delay of application context migration, helps the normal operation of the service, and reduces the time when the service operation of the terminal application client is affected or interrupted.
  • the first information is further used to instruct the edge-enabled functional entity to perform one or more of the following operations: detect a trigger event for the migration of the application context; discover a target application a functional entity, the target application functional entity is configured to receive the application context; transmit the application context to an edge-enabled functional entity associated with the target application functional entity; send the information of the target application functional entity to the target application functional entity sending the application context migration information to the core network element; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.
  • the sending the first information to the edge-enabled functional entity includes: sending registration information to the edge-enabled functional entity, where the registration information includes the first information.
  • the method further includes: sending first condition information to the edge-enabled functional entity, where the first condition information is used to indicate a first validation condition of the first information.
  • the first condition information includes any one or more of the following: a validity period of the first information, a validity period of the first information, and a valid period of the first information.
  • the application client, the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, and the application function entity is overloaded.
  • the method further includes: sending second condition information to the edge-enabled functional entity, where the second condition information is used to indicate a second valid condition of the first information, The second validation condition is different from the first validation condition.
  • the method further includes: sending the application context to the edge-enabled functional entity.
  • the method before sending the application context to the edge-enabled functional entity, the method further includes: receiving a storage address of the application context from the edge-enabled functional entity; Based on the storage address, the application context is sent to the edge-enabled entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • an embodiment of the present application provides an apparatus for migrating an application context
  • the apparatus includes: a communication module configured to receive first information from an application function entity, where the first information is used to instruct the application function to be migrated an application context associated with an entity; and a processing module, configured to determine to migrate the application context according to the first information when a trigger event for the migration of the application context occurs.
  • the application function entity hosts the migration of its associated application context to the edge enabling function entity, and when the edge enabling function entity detects that the application context needs to be migrated, it can decide on its own to migrate the application context , which can reduce the signaling interaction for migrating application context, shorten the delay of application context migration, help the normal operation of the service, and reduce the time when the service operation of the terminal application client is affected or interrupted.
  • the processing module is further configured to perform one or more of the following operations according to the first information: detecting a triggering event of the migration of the application context; discovering a target application functional entity , the target application function entity is used to receive the application context; transmit the application context to the edge-enabled function entity associated with the target application function entity; send the information of the target application function entity to the application terminal equipment related to the functional entity; sending the information about the migration of the application context to the core network element; wherein, the application corresponding to the application functional entity is the same as the application corresponding to the target application functional entity.
  • the communication module is specifically configured to receive registration information from the application function entity, where the registration information includes the first information.
  • the communication module is further configured to receive first condition information from an application function entity, where the first condition information is used to indicate a first effective condition of the first information.
  • the first validating condition includes any one or more of the following: validating duration of the first information, validating period of the first information, applicable to the first information , the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application function entity is overloaded.
  • the communication module is further configured to receive second condition information from the application function entity, where the second condition information is used to indicate a second validation condition of the first information , the second validating condition is different from the first validating condition.
  • the communication module is further configured to receive the application context from the application function entity.
  • the communication module before receiving the application context from the application function entity, the communication module is further configured to send the storage address of the application context to the application function entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • an embodiment of the present application provides an apparatus for migrating application contexts, including: a communication module configured to send first information to an edge-enabled functional entity, where the first information is used to indicate an application associated with the migration of the application functional entity a context; a communication module, further configured to receive response information sent from the edge-enabled functional entity in response to the first information.
  • the edge-enabled functional entity is hosted with the migration of the application context.
  • the edge-enabled functional entity detects that the application context needs to be migrated, it can decide to migrate the application context by itself, which can reduce the time required for migrating the application context. Signaling interaction shortens the delay of application context migration, helps the normal operation of the service, and reduces the time when the service operation of the terminal application client is affected or interrupted.
  • the first information is further used to instruct the edge-enabled functional entity to perform one or more of the following operations: detecting a triggering event of the migration of the application context; discovering a target application function
  • the target application function entity is used for receiving the application context; transmitting the application context to the edge-enabled function entity associated with the target application function entity; sending the information of the target application function entity to the A terminal device related to an application function entity; sending the information about the migration of the application context to the core network element; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.
  • the communication module is further configured to send registration information to the edge-enabled functional entity, where the registration information includes the first information.
  • the communication module is further configured to send first condition information to the edge-enabled functional entity, where the first condition information is used to indicate first validation of the first information condition.
  • the first condition information includes any one or more of the following: a validity period of the first information, a validity period of the first information, and a valid period of the first information.
  • the application client, the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, and the application function entity is overloaded.
  • the communication module is further configured to send second condition information to the edge-enabled functional entity, where the second condition information is used to indicate second validation of the first information condition, the second validating condition is different from the first validating condition.
  • the communication module is further configured to send the application context to the edge-enabled functional entity.
  • the communication module before sending the application context to the edge-enabled functional entity, is further configured to receive storage of the application context from the edge-enabled functional entity address; based on the storage address, sending the application context to the edge-enabled entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • an embodiment of the present application provides a communication device, including: a processor and a memory;
  • the memory for storing computer programs
  • the processor is configured to execute the computer program stored in the memory, so that the method in any one of the optional embodiments of any one of the first aspect to the second aspect is performed.
  • a communication device includes: a processor and an interface circuit
  • the interface circuit for receiving code instructions and transmitting them to the processor
  • the processor is configured to execute the code instructions to cause the method in any one of the optional embodiments of any one of the first to second aspects above to be performed.
  • a seventh aspect is a computer-readable storage medium, the computer-readable storage medium stores instructions, when the instructions are executed, so that any one of the above-mentioned first to third aspects can be The method of the selected embodiment is performed.
  • an embodiment of the present application provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed, makes any one of the first aspect to the second aspect above The method in an alternative embodiment is performed.
  • FIG. 1 is a schematic diagram of a MEC architecture model provided by an embodiment of the present application.
  • FIG. 2 is one of the schematic flowcharts of the method for migrating an application context provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of an EAS registering with an EES according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of an AC registering with the EEC according to an embodiment of the present application
  • FIG. 5 is a schematic flowchart of a method for an EAS instructing an EES to migrate an application context according to an embodiment of the present application
  • FIG. 6 is the second schematic flowchart of a method for migrating an application context provided by an embodiment of the present application
  • FIG. 7 is a schematic flowchart of an EEC registering with an EES according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of an EEC discovering an EAS through an EES provided by an embodiment of the present application
  • FIG. 9 is a schematic flowchart of a method for synchronizing application contexts provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a method for an EAS instructing an EES to migrate an application context according to an embodiment of the present application
  • FIG. 11 is a structural block diagram of an apparatus for migrating application contexts provided by an embodiment of the present application.
  • FIG. 12 is one of schematic structural diagrams of a communication device provided by an embodiment of the present application.
  • FIG. 13 is a second schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the embodiments of the present application can be applied to a 4G system, a 5G system or a future mobile communication system, and are specifically applied to a multi-access edge computing (MEC) architecture.
  • MEC multi-access edge computing
  • Figure 1 is a schematic diagram of an MEC architecture model, which illustrates the edge application server and edge enablement server on the edge data network side, as well as the application client and edge enablement client on the terminal device side.
  • the edge data network corresponds to a data network deployed at the edge, which can be a local data network (local DN) or a local area data network (LADN).
  • Edge data networks include edge-enabled functions, which can be identified using data network access identifier (DNAI) and data network name (DNN) or using data network name and data network service area (service area) ) logo. Or it can be understood that the edge data network can be regarded as a data center deployed locally relative to the central cloud.
  • DNAI can be used to identify edge data networks, and an edge data network can contain multiple local data networks (local DNs).
  • Edge application server indicating the server application deployed in the edge data network
  • EAS Edge application server
  • MEC application server
  • EAS function etc.
  • applications such as social media software, augmented reality (AR), and virtual reality (VR) are deployed and run on application instances (instances) of the EDN.
  • An application may deploy one or more EASs in one or more EDNs, and EASs deployed and running in different EDNs may be regarded as different EASs of an application.
  • Different EASs of an application can share a domain name; different EASs of an application can use an anycast IP address or different IP addresses.
  • the edge application server EAS may also include the application context of the application corresponding to the EAS.
  • the application context may also include the context of one or more application users using the application on the EAS, for example, an application context using the application.
  • the application context may also include contexts of subscriptions between one or more application users using the application in the EAS and the core network, such as subscription transaction identifiers and the like.
  • the edge enabler server is deployed in the EDN, and can provide edge computing enabling services for the application instance deployed in the EDN, namely the aforementioned EAS, to better support the deployment and operation of applications in the MEC.
  • EES can support EAS registration, authentication and authentication of terminal equipment (user equipment, UE) or authentication and authorization of edge-enabled clients, and provides UE with application instance information including such as IP address information.
  • an EAS can be registered on an EES, or the information of an EAS can be configured on an EES through the management system, then the EES is called the EES associated with the EAS, and the EES can control (manage) the registration or It is the EAS configured on the EES or the service EES of the EAS.
  • EES also supports obtaining the information of the application instance, including the identification of the application instance and the address information (such as IP address information) of the application instance, and further sends the information of the application instance such as the identification of the application instance to the edge data network configuration server (edge configuration server). , ECS).
  • the ECS is responsible for the configuration of the EDN, such as providing EES information to the UE, providing EAS information to the UE, and interacting with the application's DNS to obtain the EAS information. Further, the application instance and IP address information can also be obtained and saved from other functional entities.
  • the MEC architecture model illustrated in FIG. 1 also illustrates the aforementioned ECS.
  • the application client (application client, AC) is a client program applied on the terminal device side, and is the peer entity of the EAS on the terminal device side, and the application client is used by the application user (user) to obtain the application service from the application server.
  • the application client can connect to the application server on the cloud to obtain the application service, and can also connect to the EAS where the application is deployed and running in one or more EDNs to obtain the application service.
  • the edge enabler client is the peer entity of the EES on the terminal device side.
  • the EEC is used to register the EEC information and the application client AC information with the EES, perform security authentication and authentication, and obtain it from the EES.
  • the information of the EAS includes, for example, the address information of the EAS (eg, IP address) and provides edge computing enabling capabilities to the application client.
  • the EEC discovery service can return the IP address of the EAS to the application client.
  • a communication connection is established between the aforementioned application client AC on the terminal device side and the edge application server EAS; and a communication connection is established between the edge enabling client EEC on the terminal device side and the edge enabling server EES.
  • the application user signs a service agreement with the application provider, and can log in to the application client AC deployed on the terminal device to use the application, and interactively transmit application data (application data) through the communication connection between the application client AC and the EAS;
  • the service provided by the edge-enabled server EES is obtained from the edge-enabled client EEC by the application client AC in the form of an application programming interface (application program interface, API).
  • the MEC architecture as shown in FIG. 1 includes the following two-level discovery mechanism, that is, the EEC discovers the EES from the ECS and the EEC discovers the EAS from the EES.
  • the EEC discovers the EES from the ECS, including the following process: the EEC discovers the EES or EDN it is interested in by requesting or subscribing to the ECS, and obtains information of one or more ESSs, such as the information of the EES corresponding to the location of the UE.
  • EEC discovering EAS from EES includes the following process: EEC requests the target edge application instance EAS to be accessed from EES, and the optional EEC indicates the discovery filtering parameters provided by the application user in the request; EES according to its local registered or called The information of the online EAS, and/or the discovery filtering parameters provided by the application user, matches one or more EASs that satisfy the request, and feeds back the information of the one or more EASs that satisfy the request to the EEC.
  • the EEC may provide the application client AC with the information of one or more EASs that it has received, so that the AC is connected to the aforementioned EAS.
  • the terminal equipment UE deployed with the application client may move, for example, the UE moves from an area corresponding to one EDN to an area corresponding to another EDN.
  • the edge application server currently providing services may not be able to continue to provide services for the application client currently running on the aforementioned moving UE, or the edge application server currently providing services may no longer be able to provide services.
  • the optimal edge application server that provides services to the application client on the UE there are other edge application servers that are more suitable for serving the application client on the UE.
  • a new edge application server needs to be selected to replace the aforementioned edge application server (may be referred to as the source edge application server) that currently provides services, and the new edge application server is used to provide services for the application client on the UE.
  • the application service will be temporarily suspended or interrupted, and the application context of the application client on the source edge needs to be migrated to the new edge application server, so that the application client can connect to the target edge Quickly continue business behind the application server to reduce the impact of application outages.
  • EEC/EES detects the need for application uplink migration, it usually needs to determine the target EAS for application context migration based on the communication method and discovery mechanism of the MEC architecture, and notify the EAS currently providing the service to migrate the application context. In this way, there are many signaling interactions, and the delay is long, which affects the operation of the application.
  • the embodiments of the present application provide a method and apparatus for migrating application contexts, by allowing (or, can be described as "request”, “delegation”) edge-enabled functional entities such as the aforementioned EEC/EES managed application context migration,
  • the edge enabling functional entity is responsible for the decision to migrate the application context, and even authorizes all the operations of the application context migration, in order to reduce the signaling interaction with the EAS and shorten the delay of the application context migration. Since the principles of the method and the device for solving the problem are the same, the method part and the device part of the embodiments can be referred to each other, and the repeated parts will not be repeated.
  • the multiple involved in the embodiments of the present application refers to two or more.
  • "And/or" which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/" generally indicates that the associated objects are an "or" relationship.
  • first, second, etc. may be used to describe various data in the embodiments of the present invention, these data should not be limited to these terms. These terms are only used to distinguish the various data from each other.
  • an embodiment of the present application provides a method for migrating an application context, and the method can be applied to the aforementioned MEC architecture model.
  • the method includes the following procedures.
  • an application function entity sends first information to the application function entity, where the first information is used to instruct to migrate an application context associated with the application function entity.
  • the first information may be a request message, and the request message is used for requesting to migrate the application context associated with the application function entity.
  • the first information may also be a message that simultaneously requests and subscribes to the application context migration, that is, requests to migrate the application context and subscribe to the notification of the application context migration.
  • the first information may be a service API (service API), and the API may be provided by EES or EEC.
  • service API service API
  • migration can be understood as relocation
  • migration of the application context associated with the application function entity can be understood as: through a series of operations, the service (serving) EAS of one, more or all application users served by the application function entity is finally removed from the source EAS switches to target EAS.
  • the first information can also be a parameter in a message, which is used to indicate the service or operation of migrating the application context
  • the parameter can be a set of enumeration values, such as ⁇ application context migration event detection (detection), application context migration Merge of one or more of decision, application context migration execution, application context post migration cleanup ⁇ .
  • application context migration event detection (detection) & application context migration decision (decision) & application context migration execution (execution) & application context post-migration cleanup (cleanup) it means The edge-enabled functional entity performs the above-mentioned services or operations.
  • the first information may also be indicated using a specific bit of a parameter.
  • the application functional entity may indicate the application client or edge application server in the aforementioned MEC architecture; the edge enabled functional entity may indicate the edge enabled client or edge enabled functional entity in the aforementioned MEC architecture.
  • the application functional entity may be an edge application server EAS, and the edge enabling functional entity may be an edge enabling server EES; in another optional implementation manner, the application functional entity may be an application program client.
  • the edge-enabled functional entity may be the edge-enabled client EEC.
  • the application context associated with the application function entity indicates the application context corresponding to the application function entity.
  • the application context may specifically include one or more or all application user-related application contexts associated with the application function entity.
  • the application context includes identification information, where the identification information is used to uniquely identify the application context of an application user.
  • the aforementioned identification information may be a UE identification such as an IP address, a user permanent identifier (subscription permanent identifier, SUPI), etc., and the aforementioned identification information may also be the identification of the application client.
  • a uniform resource locator uniform resource locator
  • the edge enabling functional entity may also send response information of the first information to the application functional entity in response to the foregoing first information.
  • the edge enabling functional entity determines to migrate the application context according to the first information.
  • the edge-enabled functional entity when it detects the movement of the terminal device related to the aforementioned application functional entity, it may determine that a business continuity event occurs, that is, a trigger event that detects the migration of the application context can be understood as the edge-enabled functional entity. Some events can be detected, and based on these timings, application context migration may be required.
  • the application function entity hosts the migration of its associated application context to the edge enabling function entity, and when the edge enabling function entity detects that the application context needs to be migrated, it can decide on its own to migrate the application context , which can reduce the signaling interaction for migrating application context, shorten the delay of application context migration, help the normal operation of the service, and reduce the time when the service operation of the terminal application client is affected or interrupted.
  • the application functional entity is an edge application server EAS
  • the edge enabling functional entity is an edge enabling server EES
  • the edge enabling functional entity may also perform one of the following (1) to (5) Item or actions:
  • the target application function entity may be an edge application server EAS.
  • the EES may discover the target EAS, and migrate the application context associated with the EAS that sends the first information to the target EAS.
  • the aforementioned application corresponding to the EAS sending the first information is the same as the application corresponding to the target EAS, that is, the target EAS and the EAS sending the first information are two different application instances of the same application.
  • the target application function entity is the same as the application corresponding to the target application function entity (that is, the target EAS is the same as the application function entity).
  • the EAS sending the first information is two different application instances of the same application).
  • the information of the target application function entity includes the registration information of the target application function entity on its associated edge-enabled function entity, so that the application client whose application is deployed on the terminal device can be reconnected to the target application. functional entity.
  • the core network element may be a network capability exposure function (network expose function, NEF) network element, a session management function (session management function, SMF) network element, etc.
  • NEF network expose function
  • SMF session management function
  • the application functional entity is the application client AC
  • the edge-enabled functional entity is the edge-enabled client EEC
  • the edge-enabled functional entity may also perform the following (1) to (3) One or more actions:
  • the target application function entity may be an edge application server EAS.
  • the EES may discover the target EAS, and migrate the application context associated with the EAS that sends the first information to the target EAS.
  • the aforementioned application corresponding to the EAS sending the first information is the same as the application corresponding to the target EAS, that is, the target EAS and the EAS sending the first information are two different application instances of the same application.
  • the target application function entity Send the information of the target application function entity to the terminal equipment related to the application function entity; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity (that is, the target EAS is the same as the application function entity).
  • the EAS sending the first information is two different application instances of the same application).
  • the information of the target application function entity includes the registration information of the target application function entity on its associated edge-enabled function entity, so that the application client whose application is deployed on the terminal device can be reconnected to the target application. functional entity.
  • the first information may also specifically indicate an application context-related operation (or service) associated with the migration application functional entity, and the edge enabling functional entity receives the first information and executes the The operation indicated by the first message.
  • the operation can indicate an independent operation, which contains only one atomic function, and the atomic function can also be called atomic operation or atomic service); or the operation can indicate a composite operation, which includes multiple operations. an atomic function. It is more flexible to host part of the permissions related to migrating application contexts to edge-enabled functional entities.
  • the EAS may use the first information to instruct the EES to implement one, more or all of the following: detecting a triggering event for the migration of the application context, deciding to migrate the application context, discovering The target EAS, transfers the application context from the EAS to the target EAS or the target EES, and sends the information of the target EAS to the terminal device.
  • conditions that need to be satisfied by the edge-enabled functional entity to implement the indication of the first information may also be set.
  • the application function entity may send first condition information to the edge enablement function entity, where the first condition information is used to indicate the first validation condition of the first information.
  • the application functional entity may send the first condition information together with the first information to the edge enabling functional entity, or may send the first information and the first condition information to the edge enabling functional entity separately, which is not the case in this embodiment of the present application. be limited.
  • the first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applicable, the application The migration duration of the context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application function entity is overloaded.
  • the effective duration of the first information indicates that the edge enabling functional entity can implement the indication of the first information within a specified duration from when the edge enabling functional entity receives the first information;
  • the effective period of the first information indicates that the edge enabling functional entity
  • the functional entity may implement the indication of the first information within the aforementioned effective period;
  • the application client to which the first information is applicable may be the UE identity, the IP address of the UE, the identity of the application client, or the identity of the edge-enabled client etc., this parameter specifically indicates that the edge enabling function entity can implement the indication of the first information for the application context of the application user of the application client on the corresponding terminal device using the UE identifier, optionally if the first valid condition does not contain the first information
  • the applicable application client means that the edge-enabled functional entity can implement the indication of the first information for the application context of all application users.
  • the fact that the migration duration of the application context is less than the preset time threshold indicates that the edge-enabled functional entity can implement the indication of the first information only when the migration duration of the application context is less than the preset time threshold.
  • the fact that the size of the application context is smaller than the preset size threshold indicates that the edge-enabled functional entity can implement the indication of the first information only when the size of the application context is smaller than the preset size threshold.
  • the application function entity overload is used to indicate that the application function entity can implement the indication of the first information in the case of overload.
  • a condition that needs to be satisfied to support the modification of the edge-enabled functional entity to implement the indication of the first information can also be set.
  • the application functional entity may also send second condition information to the edge enabled functional entity, where the second condition information is used to indicate a second validation condition of the first information, and the second validation condition is different in the first effective condition.
  • the second validating condition and the first validating condition contain the same parameters but have different values of the parameters.
  • the first effective condition and the second effective condition both include the effective duration of the first information, but the specific effective durations are different.
  • the settings for the preset time threshold in the first validating condition and the second validating condition are different, and so on.
  • the second validating condition and the first validating condition contain different parameters.
  • the second validation condition includes the application client to which the first information is applicable, and the first validation condition does not include the application client to which the first information is applicable.
  • the edge-enabled functional entity may also acquire the application context associated with the application functional entity, so as to implement, for example, the size judgment of the application context, the determination of the migration duration of the application context, and the execution of the application context. Context transfer (transfer) and other operations.
  • the EAS uses the first information to instruct the EES to migrate the application context associated with the EAS.
  • the EAS may send its associated application context to the EES.
  • the EAS may send the application context to the EES based on a storage address (or called a hosting address) that the EES can access.
  • the storage address stores the application context.
  • the storage address that can be accessed by the EES can be implemented by referring to either of the following two methods.
  • the first way a hosting address that can be configured locally in EAS. This address is the application context that needs to be migrated or synchronized for one or more application users whose services are stored by EAS. EAS saves the application context to be migrated in the hosting address.
  • the EES can send a storage address to the EAS on its own initiative or at the request of the EAS, so that the EAS synchronizes the application context to the EES based on the aforementioned storage address.
  • the EAS may assign an identifier to the application context of each user, and the identifier may be the identifier of the application user, or the identifier may be the terminal corresponding to the client used by the application user.
  • the IP address of the device or the identifier of the terminal device, or the identifier may be other types of application context identifiers.
  • the EAS may periodically synchronize the latest application context with the EES, for example every 5s, and the application context may be stored in an overlay manner or in an append manner.
  • the append mode if the application context exceeds the preset size, the application context saved at the earliest time may be discarded, or each application context saved for relocation carries timestamp or checkpoint information.
  • the application context associated with the AC is stored in the EAS where the application corresponding to the AC deploys and runs in the EDN.
  • the application context can be stored in the EES by referring to the following two methods: the first method: the AC interacts with the EAS, and requests the EAS to synchronize the application context to the EES.
  • the EEC needs to request the EES associated with the aforementioned EAS to synchronize the application context, and the EES requests the EAS to synchronize the application context, and the EAS can synchronize the application context to the EES.
  • the foregoing application context migration method may be implemented based on the registration process of the application function entity.
  • the first information may be included in the registration information of the application functional entity and transmitted to the edge enabled functional entity.
  • a process of EAS registering with EES includes the following steps.
  • the EAS sends a registration request (registration request) message or a registration update request (registration update request) message to the EES, where the registration request message or the registration update request message carries registration information, and the registration information includes the aforementioned first information.
  • the registration information may be an EAS profile, and the first information contained in the EAS profile may be referred to as application migration delegation indication (relocation delegate indication), application migration permission, or application migration agent, or application migration decision permission, application migration decision Licensing, or Application Migration Decision Agent, etc.
  • the EAS profile includes the contents shown in Table 1 below.
  • the EES sends a registration response (registration response) message or a registration update response (registration update response) message to the EAS.
  • the EAS may carry the storage address (or, the hosting address) of the application context in the registration response message or the registration update response message, which is used to instruct the EAS to send the application context to the EES.
  • the application context is the application context that needs to be synchronized during migration.
  • the storage address of the application context can be an IP address and a port number, or a URL address.
  • EES sending the application context to EES can be understood as EAS saving the application context in a storage address identified by a storage address. in the unit.
  • the EES can read the application context in the storage unit identified by the storage address, that is, EAS and EES can be two logical function modules in the same node, and the aforementioned application context transfer can be through the sharing and permission of the storage space of the application context. It is realized by management, which is different from the traditional way of data exchange between two nodes through physical cables.
  • the storage address and the storage unit corresponding to the storage address may be managed by the EES.
  • the EES may decide to migrate the application context on its own, and implement related operations for migrating the application context.
  • the related operations include one, more or all of the following: EES discovery Target EAS; EES transfers the application context to the target EAS or the EES associated with the target EAS; EES notifies the EEC that the application context switching is completed, and sends the information of the target EAS to the EEC; EES sends the application context migration information to the 3GPP core network element , such as the information of the target EAS, the information of the N6 corresponding to the target EAS.
  • the relevant operations include one, more or all of the following: the EES discovers the target EAS; the EES notifies the source EAS of the address of the target EAS or the EES request source
  • the EAS transmits the application context to the target EAS; the EES notifies the EEC that the application context switching is completed, and sends the information of the target EAS to the EEC; the EES sends the application context migration information to the 3GPP core network element, such as the information of the target EAS, the target EAS corresponds to information on the N6.
  • the optional EES associated with the target EAS can replace the target EAS to determine whether to receive the migration of the aforementioned application context; at this time, the EES transmits the application context to the EES associated with the target EAS, and the EES associated with the target EAS can also replace the EES.
  • the target EAS determines whether to receive the application context.
  • the EES may further perform: detecting a triggering event of the migration of the application context.
  • a process of registering an AC with an EEC includes the following steps.
  • the AC sends a registration request (registration request) message or a registration update request (registration update request) message to the EEC, where the registration request message or the registration update request message carries registration information, and the registration information includes the aforementioned first information.
  • the registration information may be an AC profile, and the first indication information included in the AC profile may be referred to as application migration delegation indication (relocation delegate indication), application migration permission, or application migration agent, or application migration decision permission, application migration Migration decision permission, or application migration decision agent, etc.
  • the AC profile includes the contents shown in Table 2 below.
  • the EEC sends a registration response (registration response) message or a registration update response (registrationup date response) message to the AC.
  • the EEC can make its own decision to migrate the application context, and perform operations related to migrating the application context. For example, the EEC obtains the information of the target EES from the ECS, and the EEC obtains the information of the target EAS from the target EES, wherein the target EES is associated with the target EAS. ; The EEC triggers the AC, the AC triggers the source EAS, and the source EAS sends the application context to the target EAS. After the application context migration, the AC switches the application data to the target EAS.
  • the EEC notifies the target EES that application context relocation may be required; the target EES obtains information of the target EAS and sends an ACR request message to the target EAS; the target EAS initiates application context transfer between the source EAS and the target EAS.
  • the AC switches the application data to the target EAS.
  • the EEC obtains target EAS information from the source EES, and the EEC notifies the source EAS to migrate the application context through the source EES; the source EAS sends the application context to the target EAS. After the application context is migrated, the AC switches the application data to the target EAS.
  • the permission related to the migration application context can be dynamically hosted to the edge-enabled functional entity.
  • the edge-enabled functional entity needs to implement the permission related to the migration application context under specific conditions.
  • a method flow of an EAS instructing an EES to migrate an application context includes the following steps.
  • the EAS sends a first request message to the EES.
  • the first request message is used for requesting to host (delegate) the application context migration to the EES, or the first request message is used to request migration of the application context associated with the application function entity.
  • the first request message may also be a message that simultaneously requests and subscribes to the application context migration, that is, requests to migrate the application context and subscribe to the notification of the application context migration.
  • the first information may be a service API (service API), and the API may be provided by EES; the first request message may also be described as the delegation of decision rights for application context migration, a hosting request message, a context migration request, or a full service context Migration requests, etc.
  • the first request message contains an indication or request to the EES to make a decision on application context migration.
  • the EAS may send the first request message to the EES when the service is idle or when the service is predicted to be idle.
  • the first request message carries the foregoing first information and first condition information; specifically, the first information may be a relocation delegation indication for application context migration.
  • the delegation instruction of the application context migration includes delegating the decision right of the application context migration to the EES.
  • the first condition information is used to indicate the first validating condition of the first information. For the content included in the first validating condition, reference may be made to the foregoing embodiment, which is not repeated in this embodiment of the present application.
  • the EES may save the received first information and the first condition information.
  • the EES sends a first response message to the EAS in response to the first request message.
  • the first response message may carry a transaction identifier (transaction id), and the transaction identifier is used for the EAS to subsequently operate the aforementioned first information, or the transaction identifier is used to mark the aforementioned first information and the first information stored by the EES. a conditional message. It is convenient for the subsequent EAS to update the escrow transaction or cancel the escrow transaction.
  • transaction id transaction identifier
  • conditional message It is convenient for the subsequent EAS to update the escrow transaction or cancel the escrow transaction.
  • the first response message may carry a storage address of the application context to instruct the EAS to synchronize the application context to the EES based on the aforementioned storage address.
  • the EES can migrate the application context at its own discretion, and perform operations related to migrating the application context, such as EES discovering the target EAS; EES notifying the source EAS of the address of the target EAS, or EES requesting the source EAS to transmit the application context to the target EAS; EES notifies The EEC application context switch is completed, and the information of the target EAS is sent to the EEC; the EES sends the information of the migration of the application context to the 3GPP core network element, such as the information of the target EAS and the information of the N6 corresponding to the target EAS.
  • the EES associated with the optional target EAS may replace the target EAS to determine whether to receive the aforementioned migration of the application context.
  • the EAS sends a managed update request message to the EES, where the managed update request message is used to request to update the foregoing first information and/or the first condition information.
  • the hosting update request message may also be referred to as a delegation or hosting request message for application context migration, or a second request message, or other messages, as long as it is used to request updating of the aforementioned first information and/or the first condition information, which is not limited in this embodiment of the present application.
  • the hosting update request message carries second condition information, where the second condition information is used to indicate a second validation condition of the first information.
  • the escrow update request message also carries the aforementioned transaction identifier, so that the EES can determine the escrow transaction to be updated by the EAS according to the transaction identifier.
  • the hosting update request message can carry second condition information, and the second condition information includes the valid duration of the aforementioned updated first information. . Then, after the EES receives the hosting update request message carrying the second condition information, if the saved first condition information includes the content of the effective duration of the first information, this content is replaced with the updated first content. The effective duration of the information; if the originally saved first condition information does not include the effective duration of the first information, the above-mentioned updated effective duration of the first information is added to the first condition information.
  • the EES sends a second response message to the EAS in response to the hosting update request message.
  • the second response message may carry a transaction identifier (transaction id), and the transaction identifier is used to mark the EAS to delegate the decision-making power of the application context migration or the managed transaction to the EES, or the transaction identifier is used to mark the EES.
  • transaction id a transaction identifier
  • the saved first information and first condition information It is convenient for the subsequent EAS to update the escrow transaction or cancel the escrow transaction.
  • the second response message may carry a storage address of the application context to instruct the EAS to synchronize the application context to the EES based on the aforementioned storage address.
  • the EAS sends an escrow cancellation request message to the EES.
  • the hosting cancellation request message is used to request cancellation of the migration of the application context or hosting to the EES. It should be noted that the hosting cancellation request message may also be referred to as the delegation of application context migration or the hosting cancellation request message for application context migration, or a third request message, or other messages, as long as it is used to request cancellation of EES for application context migration.
  • the hosting can be used, which is not limited in this embodiment of the present application.
  • the escrow cancellation request message also carries the aforementioned transaction identifier and/or the first information, so that the EES can determine the escrow transaction to be cancelled by the EAS according to the transaction identifier and/or the first information.
  • the EAS may send a hosting cancellation request message to the EES when the service enters the peak time or predicts that the service will enter the peak time.
  • the EES sends a third response message to the EAS in response to the hosting cancellation request message, where the third response message is used to indicate that the EES agrees to the hosting cancellation request message, that is, the EES agrees to cancel its decision right on application context migration.
  • an embodiment of the present application also provides a method for instructing migration of application contexts between edge-enabled functional entities.
  • an embodiment of the present application provides another method for migrating application contexts, and the method can be applied to the aforementioned MEC architecture model.
  • the method includes the following procedures.
  • the first edge-enabled functional entity sends first information to the second edge-enabled functional entity, where the first information is used to indicate an application context associated with the migration application functional entity.
  • the application functional entity is an application functional entity registered on the first edge-enabled functional entity.
  • the first edge-enabled functional entity may be an edge-enabled server in the aforementioned MEC architecture
  • the second edge-enabled functional entity may be an edge-enabled client in the aforementioned MEC architecture.
  • the application function entity may be an edge application server registered on the edge enabled server.
  • the first information may be carried in an EEC registration response message (EEC registration response) sent by the EES to the EEC, and the first information may also be carried in other messages sent by the EES to the EEC.
  • EEC registration response EEC registration response
  • the first information may be referred to as application migration delegation indication (relocation delegation indication), and the application migration delegation indication may further include delegating the decision right of application migration to the EEC.
  • the second edge enabling functional entity may determine that a service continuity event occurs when detecting the movement of the terminal device related to the aforementioned application functional entity, that is, detecting a triggering event of the migration of the application context.
  • the edge-enabled server hosts the migration of the application context to the edge-enabled client.
  • the edge-enabled client detects that the application context needs to be migrated, the edge-enabled client can decide to migrate the application context by itself, which can reduce the number of migrations.
  • the signaling interaction of the application context shortens the delay and helps the normal operation of the business.
  • the edge-enabled server may be preconfigured with the first information.
  • the foregoing application context migration method may be implemented based on the registration process of the edge-enabled client to the edge-enabled server.
  • a flow of EEC registering with EES or registering update with EES includes the following steps.
  • the EEC sends a registration request (registration request) message or a registration update request (registrationup date request) message to the EES, where the registration request message or the registration update request message carries registration information, and the registration information may be an EEC profile.
  • the EEC profile contains the contents described in Table 3 below.
  • the EES sends a registration response (registration response) message or a registration update response (registration update response) message to the EEC.
  • the EAS may carry the first information preconfigured in the EES in the registration response message or the registration update response message to instruct the EEC to migrate the application context.
  • the first information may come from the EAS or be preconfigured in the EES.
  • the foregoing method for migrating application contexts may be implemented based on a process in which an edge-enabled client requests an edge-enabled server to discover an edge application server.
  • a process of EEC discovering EAS through EES includes the following steps.
  • the EEC sends an EAS discovery request (EAS discovery request) message to the EES.
  • EAS discovery request EAS discovery request
  • the EAS discovery request message carries the EEC ID and security credentials.
  • the EAS discovery request message carries an EAS discovery filter parameter, where the EAS discovery filter parameter is used to indicate the target EAS or the category of the target EAS (for example, a game application).
  • the EES sends an EAS discovery response (EAS discovery response) message to the EEC.
  • EAS discovery response EAS discovery response
  • the EAS discovery response message carries the information of the discovered EAS; wherein, the information of the EAS includes the registration information of the EAS, and the registration information of the EAS includes the aforementioned first information.
  • the EAS discovery response message carries an EAS profile, and the EAS profile includes a relocation delegate indication for application migration.
  • the EES can determine the discovered EAS according to the EAS discovery filter parameter, so that the EAS discovery response message carries the discovered EAS information.
  • the embodiment of the present application also provides a solution for configuring the migration of the application context of some applications for the edge-enabled functional entity in advance.
  • a set of application lists may be configured on the edge-enabled server EES, and the migration of the application context of any application in the application list is delegated to the EES, or the EES has the ability to migrate the application context in the application list. Permissions for any app's app context.
  • the application list includes one or more EAS identifiers, and any EAS identifier is used to indicate that the migration of the application context of the application corresponding to the EAS identifier is delegated to the EES.
  • the application corresponding to the EAS identifier refers to an application deployed and running on the EAS indicated by the EAS identifier.
  • a set of application lists configured on the EES includes EAS#ID1 and EAS#ID2.
  • EAS#ID1 indicates that the migration of the application context of the application deployed and run on the EAS identified as ID1 is delegated to the EES
  • EAS#ID2 indicates that the migration of the application context of the application deployed and run on the EAS identified as ID2 is delegated to EES.
  • the EES can query the pre-configured application list to determine that the application context is the application context of an application in the application list, that is, to determine the decision-making power of the application context migration. Delegated to the EES, which in turn can determine to migrate the application context.
  • the edge application server EAS that any application deploys and runs on the EDN can be configured with hosting indication information, and the hosting indication information is used to indicate the decision of the application context migration of any application. Authority is delegated to EES.
  • the escrow indication information may be the aforementioned first information, and the escrow indication information is specifically configured in the EAS profile.
  • an embodiment of the present application further provides a schematic flowchart of a method for synchronizing application contexts.
  • the EAS determines whether the EAS is locally configured with a hosting address. Among them, the hosting indication information is configured in the EAS.
  • the escrow address may be obtained by EAS from EES upon registration.
  • the EAS in the case that there is no available escrow address locally in the EAS, the EAS sends a request message for requesting a storage address to the EES.
  • the request message may carry the identifier of the application user of the application context to be migrated, and the identifier may be the IP address of the terminal device corresponding to the client used by the application user or the identifier of the terminal device.
  • the EES In response to the foregoing request message of the EAS, the EES sends a response message of the request message to the EAS.
  • the response message carries the storage address allocated by the EES for the EAS.
  • the response message also carries an identifier of the application context to be migrated, where the identifier is specified by the EES.
  • the identifier may be the identifier of the application user, or the identifier may be the IP address of the terminal device corresponding to the client used by the application user or the identifier of the terminal device, or the identifier may be other types of application context identifiers.
  • the EAS synchronizes the application context to be migrated to the EES based on the locally available hosting address or the storage address indicated by the EES.
  • the application context includes an identifier for identifying the application context, and the identifier may be the identifier of the application context received from the EES, or the identifier of the application context specified by the EAS.
  • a set of application lists may be configured on the edge-enabled client EEC, and the migration of the application context of any application in the application list is delegated to the EEC, or the EEC is equipped with Migration of the app context of any app in the app list.
  • the application list includes one or more EAS identifiers, and any EAS identifier is used to indicate that the migration of the application context of the application corresponding to the EAS identifier is delegated to the EES.
  • the application corresponding to the EAS identifier refers to an application deployed and running on the EAS indicated by the EAS identifier.
  • a set of application lists configured on the EEC includes EAS#ID1 and EAS#ID2.
  • EAS#ID1 indicates that the migration of the application context of the application deployed and running on the EAS identified as ID1 is delegated to the EEC
  • EAS#ID2 indicates that the migration of the application context of the application deployed and running on the EAS identified as ID2 is delegated to EEC.
  • the EEC can query the pre-configured application list to determine that the application context is the application context of an application in the application list, that is, to determine the decision-making power of the application context migration. Delegated to the EEC, which in turn can determine to migrate the application context.
  • a method flow of an EAS instructing an EES to migrate an application context includes the following steps.
  • the EAS sends an application context migration (subscription) request to the source EES.
  • the application context migration (subscription) request optionally includes an application context migration service mode, and the service mode may be a full service mode.
  • the application context migration (subscription) request is used to request EES to perform all operations related to the application context. These operations include detecting the triggering event of the application context clear migration, deciding that the application context needs to be migrated, executing the migration of the application context, and some cleaning operations after the migration. , and further these operations also include notifying the EEC of the information of the target EAS (specifically including the access address of the target EAS, such as an IP address), and notifying the mobile communication network of the application migration information.
  • the request message optionally contains the identifiers of one or more application users, and the identifiers may be the identifiers or IP addresses of the terminals where the clients used by the application users are located. If the request does not contain the identifier of the application user, it can be understood that the EAS requests the EES to perform the foregoing related operations of application context migration for all application users of the EAS service.
  • the application context migration (subscription) request or the application context migration service mode may be regarded as the aforementioned first information.
  • the source EES sends an application context migration (subscription) response to the EAS.
  • the response message may contain an address for application context synchronization, and the address may be an IP address and a port number, or a URL.
  • This address is used by EAS to store and update the application context that needs to be migrated to this address.
  • the application context may be a context that needs to be migrated for one or more users of the EAS service.
  • the address EES can access to read the application context that needs to be migrated. For the detailed description of the address, reference may be made to the corresponding description in the foregoing embodiments.
  • the source EES detects a trigger event of the application context.
  • the source EES may subscribe the user plane path management event notification to the core network element, and receive the user plane path management event notification message from the core network element, and the message carries the target.
  • DNAI the target DNAI indicates that the EAS may potentially be deployed at the corresponding location of the target DNAI.
  • the source EES may also subscribe to the location of the UE and its changes from terminal devices corresponding to one or more application users, so as to obtain the latest location of the one or more terminal devices.
  • the source EES may also remotely locate one or more terminal devices corresponding to application users from the core network element to subscribe to the location of the UE and its changes, so as to obtain the latest location of the one or more terminal devices.
  • the source EES may determine that the one or more application users may need to migrate the application context according to the user plane path management event notification and the location of its target DNAI or UE.
  • the source EES decides that the one or more application users need to migrate the application context. For example, the source EES may move out of the service area (or called the best service area) corresponding to the current source EES according to the position of the UE, thereby judging that the application context needs to be migrated.
  • the service area or called the best service area
  • the source EES may send a notification message of application context migration to the source EAS when it is determined to execute the application context for one or more application users, notifying the source EAS that the one or more users need to migrate the application context . It further includes notifying EAS that the application context that needs to be migrated is ready.
  • the source EES sends an EES request message to the edge configuration server ECS, for obtaining a target EES that matches the location or target DNAI corresponding to the one or more users and can provide information of the target EAS of the application service.
  • the source EES obtains the target EES from the ECS, it sends an EAS request message to the target EES to request the transfer of the application context of the one or more users.
  • the target EES determines the target EAS and the target EAS can accept the application context
  • the target EES sends a response message to the source EES, indicating that the application context is accepted.
  • the request message sent by the source EES to the target EES can also be used to obtain the information of the target EAS that provides the service of the application.
  • the source EES obtains the information of the target EAS from the target EES.
  • step S1007 after step S1002 and before step S1008, the source EAS synchronizes the application context to be migrated to the source EES.
  • the source EAS synchronizes the application context to be migrated to the source EES.
  • the source EES determines that the target EAS can accept the application context
  • the source EES reads the application context to be migrated from the foregoing address, and transmits the application context to the target EES.
  • the target EES stores the received application context in a specific storage address to identify the storage area.
  • the target EES sends an application context migration notification message to the target EAS, which is used to notify the target EAS that there is an application context that needs to be received.
  • the message may include address information for reading the application context, which corresponds to the storage address where the target EES stores the application context in S1008. This step is optional.
  • the target EAS sends an application context acquisition request to the target EES, and the request message user requests to acquire the application context. This step is optional.
  • the target EES sends an application context acquisition response to the target EAS, which is used to indicate an acceptance request message.
  • the target EES after receiving the application context, the target EES sends the application context to the target EAS.
  • the way that the target EAS and the target EES process the application context is, for example, through the mapping of storage addresses or the copying or cutting of the application context in different storage spaces on the same physical storage device.
  • the context is similar, and reference may also be made to the corresponding descriptions in the foregoing embodiments.
  • the source EES sends an application context migration notification message to the EEC, where the message is used to indicate that the application context transfer is completed, and the message may include information of the target EAS, which may specifically be the information of the EAS. IP address and port number. Further, the EEC sends a notification message to the AC to notify the AC that the application context transfer is completed, and further includes the information of the target EAS.
  • the source EES sends an application context migration notification message to the source EAS, where the message is used to indicate that the application context transfer is completed.
  • the source EES sends a message of application migration to the core network element. Specifically, it includes address information of the target EAS, routing information of the target N6, and the like. This S1015 is not shown in FIG. 10 .
  • an embodiment of the present application provides an application context migration apparatus 1100 , where the apparatus 1100 includes a communication module 1101 and a processing module 1102 .
  • the application context migrating apparatus 1100 may be applied to an edge-enabled functional entity.
  • the application context migrating apparatus 1100 may be an edge-enabled functional entity, or may be applied to an edge-enabled functional entity, or may be applied to an edge-enabled functional entity.
  • a communication module 1101, configured to receive first information from an application function entity, where the first information is used to indicate migration of an application context associated with the application function entity;
  • the processing module 1102 is configured to determine to migrate the application context according to the first information when a triggering event of the migration of the application context occurs.
  • the application function entity hosts the migration of its associated application context to the edge enabling function entity, and when the edge enabling function entity detects that the application context needs to be migrated, it can decide on its own to migrate the application context , which can reduce the signaling interaction for migrating application context, shorten the delay of application context migration, help the normal operation of the service, and reduce the time when the service operation of the terminal application client is affected or interrupted.
  • the processing module 1102 is further configured to perform one or more of the following operations according to the first information: detecting a triggering event of the migration of the application context; discovering a target application function The target application function entity is used for receiving the application context; transmitting the application context to the edge-enabled function entity associated with the target application function entity; sending the information of the target application function entity to the A terminal device related to an application function entity; sending the information about the migration of the application context to the core network element; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.
  • the communication module 1101 is specifically configured to receive registration information from the application function entity, where the registration information includes the first information.
  • the communication module 1101 is further configured to receive first condition information from an application function entity, where the first condition information is used to indicate a first validation condition of the first information.
  • the first validating condition includes any one or more of the following: validating duration of the first information, validating period of the first information, applicable to the first information , the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application function entity is overloaded.
  • the communication module 1101 is further configured to receive second condition information from the application function entity, where the second condition information is used to indicate the second validation of the first information condition, the second validating condition is different from the first validating condition.
  • the communication module 1101 is further configured to receive the application context from the application function entity.
  • the communication module 1101 before receiving the application context from the application function entity, the communication module 1101 is further configured to send the storage address of the application context to the application function entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • the application context migrating apparatus 1100 can be applied to an application functional entity.
  • the application context migrating apparatus 1100 can be an application functional entity, or can be applied to an application functional entity, or can support the execution of an application functional entity. Apparatus for data transmission method. The function or execution process of the modules in the apparatus 1100 for migrating the application context of the application functional entity will be described in detail below.
  • the processing module 1102 is configured to determine the first information.
  • the communication module 1101 is configured to send first information to the edge-enabled functional entity, where the first information is used to indicate the application context associated with the migration application functional entity; the communication module 1101 is further configured to receive a response from the edge-enabled functional entity response information sent to the first information.
  • the edge-enabled functional entity is hosted with the migration of the application context.
  • the edge-enabled functional entity detects that the application context needs to be migrated, it can decide to migrate the application context by itself, which can reduce the time required for migrating the application context. Signaling interaction shortens the delay of application context migration, helps the normal operation of the service, and reduces the time when the service operation of the terminal application client is affected or interrupted.
  • the first information is further used to instruct the edge-enabled functional entity to perform one or more of the following operations: detecting a triggering event of the migration of the application context; discovering a target application function
  • the target application function entity is used for receiving the application context; transmitting the application context to the edge-enabled function entity associated with the target application function entity; sending the information of the target application function entity to the A terminal device related to an application function entity; sending the information about the migration of the application context to the core network element; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.
  • the communication module 1101 is further configured to send registration information to the edge-enabled functional entity, where the registration information includes the first information.
  • the processing module 1102 is further configured to determine the first condition information; the communication module 1101 is further configured to send the first condition information to the edge-enabled functional entity, the The first condition information is used to indicate a first validation condition of the first information.
  • the first condition information includes any one or more of the following: an effective duration of the first information, an effective period of the first information, and an effective period of the first information.
  • the application client, the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, and the application function entity is overloaded.
  • the processing module 1102 is further configured to determine second condition information; the communication module 1101 is further configured to send second condition information to the edge enabled functional entity, the The second condition information is used to indicate a second validating condition of the first information, and the second validating condition is different from the first validating condition.
  • the communication module 1101 is further configured to send the application context to the edge-enabled functional entity.
  • the communication module 1101 before sending the application context to the edge-enabled functional entity, is further configured to receive the application context from the edge-enabled functional entity a storage address; based on the storage address, sending the application context to the edge-enabled entity.
  • the application context includes identification information, and the identification information is used to uniquely identify the application context.
  • an embodiment of the present application provides a communication apparatus 1200 .
  • the communication device 1200 may be a chip or a system of chips.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication apparatus 1200 may include at least one processor 1210, and the communication apparatus 1200 may further include at least one memory 1220 for storing computer programs, program instructions and/or data. Memory 1220 and processor 1210 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1210 may cooperate with the memory 1220.
  • the memory 1220 stores necessary computer programs, program instructions and/or data for implementing any of the above embodiments; the processor 1210 may execute the computer programs stored in the memory 1220 to complete the methods in any of the above embodiments.
  • at least one of the at least one memory 1220 may be included in the processor 1210 .
  • the communication apparatus 1200 may further include a transceiver 1230, and the communication apparatus 1200 may exchange information with other devices through the transceiver 1230.
  • the transceiver 1230 can be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.
  • the communication device 1200 can be applied to an edge-enabled functional entity, and the specific communication device 1200 can be an edge-enabled functional entity, or can support an edge-enabled functional entity to implement any of the above-mentioned An apparatus for edge-enabled functional entity functionality in one embodiment.
  • the memory 1220 holds the necessary computer programs, program instructions and/or data to implement the functions of the edge-enabled functional entities in any of the above-described embodiments.
  • the processor 1210 can execute the computer program stored in the memory 1220 to complete the method for executing the edge-enabled functional entity in any of the foregoing embodiments.
  • the communication apparatus 1200 may be applied to an application functional entity, and the specific communication apparatus 1200 may be an application functional entity or an application functional entity capable of supporting the application in any of the above-mentioned embodiments.
  • the memory 1220 holds the necessary computer programs, program instructions and/or data to implement the functions of the application functional entities in any of the above-described embodiments.
  • the processor 1210 can execute the computer program stored in the memory 1220 to complete the method executed by the application functional entity in any of the foregoing embodiments.
  • the specific connection medium between the transceiver 1230, the processor 1210, and the memory 1220 is not limited in the embodiments of the present application.
  • the memory 1220, the processor 1210, and the transceiver 1230 are connected through a bus in FIG. 12, and the bus is represented by a thick line in FIG. 12.
  • the connection between other components is only for schematic illustration. It is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is shown in FIG. 12, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which may implement or The methods, steps and logic block diagrams disclosed in the embodiments of this application are executed.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or may also be a volatile memory (volatile memory), for example Random-access memory (RAM).
  • the memory may also be, but is not limited to, any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing computer programs, program instructions and/or data.
  • the embodiment of the present application further provides another communication apparatus 1300, including: an interface circuit 1310 and a processor 1320; the interface circuit 1310 is configured to receive code instructions and transmit them to the processor; the processor 1320 , used to run code instructions to execute the method executed by the edge-enabled functional entity or the method executed by the application functional entity in any of the foregoing embodiments.
  • the embodiments of the present application further provide a computer-readable storage medium, where an instruction is stored in the computer-readable storage medium, and when the instruction is executed, the method for executing the edge-enabled functional entity in any of the foregoing embodiments A method implemented or performed by an application functional entity is implemented.
  • the computer-readable storage medium may include: a USB flash drive, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.
  • an embodiment of the present application further provides a chip, including a processor, for supporting the communication device to implement the edge-enabled functional entity or the application functional entity in the above method embodiments. functions involved.
  • the chip is connected to a memory or the chip includes a memory for storing necessary program instructions and data of the communication device.
  • 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

一种应用上下文的迁移方法及装置，以期将应用上下文的迁移委派给边缘使能功能实体，由边缘使能功能实体可以自行决策迁移应用上下文，减少信令交互，缩短应用上下文迁移的时延。该方法包括：接收来自应用功能实体的第一信息，第一信息用于指示迁移应用功能实体关联的应用上下文（S201）；当发生应用上下文的迁移的触发事件时，根据第一信息确定对应用上下文进行迁移（S202）。

Description

一种应用上下文的迁移方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种应用上下文的迁移方法及装置。
背景技术
在多接入边缘计算(multi-access edge computing，MEC)架构中，通过边缘数据网络(edge data network，EDN)为终端设备(user equipment，UE)提供网络服务。具体的，EDN上部署有边缘应用服务器(edge application server，EAS)，EAS为UE侧的应用客户端(application client，AC)提供服务。EDN上部署有可对EAS进行管理的边缘使能服务器(edge enabler server，EES)，UE侧还部署有边缘使能客户端(edge enabler client，EEC)，EEC可对AC进行管理，并可将AC的信息传输给EES。
在边缘应用运行的过程中，部署有AC的UE存在移动的情况，当UE移动到当前的服务区之外，当前提供服务的EAS可能无法继续为当前运行在前述移动的UE上的AC提供服务，则需要将当前提供服务的EAS相关的应用上下文进行迁移。
目前EEC或者EES在检测到需要进行应用上行文迁移时，通常需基于MEC架构的通信方式以及发现机制，确定应用上下文迁移的目标EAS，并通知给当前提供服务的EAS以进行应用上下文的迁移。这样的方式信令交互繁多，时延较长，影响应用的运行。
发明内容
本申请提供一种应用上下文的迁移方法及装置，以期通过将应用上下文的迁移委派给边缘使能功能实体如EEC/EES，边缘使能功能实体可以自行决策迁移应用上下文，能够减少信令交互，缩短应用上下文迁移的时延。
第一方面，本申请实施例提供一种应用上下文的迁移方法，所述方法包括：接收来自应用功能实体的第一信息，所述第一信息用于指示迁移所述应用功能实体关联的应用上下文；当发生所述应用上下文的迁移的触发事件时，根据所述第一信息确定对所述应用上下文进行迁移。
本申请实施例中，应用功能实体将对其关联的应用上下文的迁移托管至边缘使能功能实体，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实现方式中，所述方法还包括：根据所述第一信息，执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实现方式中，所述接收来自应用功能实体的第一信息，包括：接收来自所述应用功能实体的注册信息，所述注册信息包含所述第一信息。
在一种可选的实现方式中，所述方法还包括：接收来自应用功能实体的第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实现方式中，所述第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
在一种可选的实现方式中，所述方法还包括：接收来自所述应用功能实体的第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实现方式中，所述方法还包括：接收来自所述应用功能实体的所述应用上下文。
在一种可选的实现方式中，在接收来自所述应用功能实体的所述应用上下文之前，所述方法还包括：向所述应用功能实体发送所述应用上下文的存储地址。
在一种可选的实现方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
第二方面，本申请实施例提供一种应用上下文的迁移方法，包括：向边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文；接收来自边缘使能功能实体的响应于所述第一信息发送的响应信息。
本申请实施例中，边缘使能功能实体被托管有应用上下文的迁移，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实现方式中，所述第一信息，还用于指示所述边缘使能功能实体执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实现方式中，所述向边缘使能功能实体发送第一信息，包括：向所述边缘使能功能实体发送注册信息，所述注册信息包含所述第一信息。
在一种可选的实现方式中，所述方法还包括：向所述边缘使能功能实体发送第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实现方式中，所述第一条件信息包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息生效的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值、所述应用功能实体过载。
在一种可选的实现方式中，所述方法还包括：向所述边缘使能功能实体发送第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实现方式中，在向边缘使能功能实体发送第一信息之后，所述方法还包 括：向所述边缘使能功能实体发送所述应用上下文。
在一种可选的实现方式中，在向所述边缘使能功能实体发送所述应用上下文之前，所述方法还包括：接收来自所述边缘使能功能实体的所述应用上下文的存储地址；基于所述存储地址，向所述边缘使能实体发送所述应用上下文。
在一种可选的实现方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
第三方面，本申请实施例提供一种应用上下文的迁移装置，所述装置包括：通信模块，用于接收来自应用功能实体的第一信息，所述第一信息用于指示迁移所述应用功能实体关联的应用上下文；处理模块，用于在发生所述应用上下文的迁移的触发事件时，根据所述第一信息确定对所述应用上下文进行迁移。
本申请实施例中，应用功能实体将对其关联的应用上下文的迁移托管至边缘使能功能实体，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实现方式中，所述处理模块，还用于根据所述第一信息，执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实现方式中，所述通信模块，具体用于接收来自所述应用功能实体的注册信息，所述注册信息包含所述第一信息。
在一种可选的实现方式中，所述通信模块，还用于接收来自应用功能实体的第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实现方式中，所述第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
在一种可选的实现方式中，所述通信模块，还用于接收来自所述应用功能实体的第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实现方式中，所述通信模块，还用于接收来自所述应用功能实体的所述应用上下文。
在一种可选的实现方式中，在接收来自所述应用功能实体的所述应用上下文之前，所述通信模块，还用于向所述应用功能实体发送所述应用上下文的存储地址。
在一种可选的实现方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
第四方面，本申请实施例提供一种应用上下文的迁移装置，包括：通信模块，用于向边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文；通信模块，还用于接收来自边缘使能功能实体的响应于所述第一信息发送的响应信 息。
本申请实施例中，边缘使能功能实体被托管有应用上下文的迁移，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实现方式中，所述第一信息还用于指示所述边缘使能功能实体执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实现方式中，所述通信模块，还用于向所述边缘使能功能实体发送注册信息，所述注册信息包含所述第一信息。
在一种可选的实现方式中，所述通信模块，还用于向所述边缘使能功能实体发送第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实现方式中，所述第一条件信息包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息生效的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值、所述应用功能实体过载。
在一种可选的实现方式中，所述通信模块，还用于向所述边缘使能功能实体发送第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实现方式中，在向边缘使能功能实体发送第一信息之后，所述通信模块，还用于向所述边缘使能功能实体发送所述应用上下文。
在一种可选的实现方式中，在向所述边缘使能功能实体发送所述应用上下文之前，所述通信模块，还用于接收来自所述边缘使能功能实体的所述应用上下文的存储地址；基于所述存储地址，向所述边缘使能实体发送所述应用上下文。
在一种可选的实现方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
第五方面，本申请实施例提供一种通信装置，包括：处理器和存储器；
所述存储器，用于存储计算机程序；
所述处理器，用于执行所述存储器中存储的计算机程序，以使得第一方面至第二方面中任一方面的任一项可选的实施方式中的方法被执行。
第六方面，一种通信装置，包括：处理器和接口电路；
所述接口电路，用于接收代码指令并传输至所述处理器；
所述处理器用于运行所述代码指令以使得上述第一方面至第二方面中任一方面的任一项可选的实施方式中的方法被执行。
第七方面，一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，以使得上述第一方面至第三方面中任一方面的任一项可选的实施方式中的方法被执行。
第八方面，本申请实施例提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述第一方面至第二方面中任一方面的任一项可选的实施方式中的方法被执行。
上述第五方面至第八方面可以达到的技术效果请参照上述第一方面至第二方面中相应技术方案可以带来的技术效果说明，此处不再重复赘述。
附图说明
图1为本申请实施例提供的一种MEC架构模型示意图；
图2为本申请实施例提供的应用上下文的迁移方法流程示意图之一；
图3为本申请实施例提供的一种EAS向EES注册的流程示意图；
图4为本申请实施例提供的一种AC向EEC注册的流程示意图；
图5为本申请实施例提供的一种EAS向EES指示迁移应用上下文的方法流程示意图；
图6为本申请实施例提供的应用上下文的迁移方法流程示意图之二；
图7为本申请实施例提供的一种EEC向EES注册的流程示意图；
图8为本申请实施例提供的一种EEC通过EES发现EAS的流程示意图；
图9为本申请实施例提供的一种同步应用上下文的方法流程示意图；
图10为本申请实施例提供的一种EAS向EES指示迁移应用上下文的方法流程示意图；
图11为本申请实施例提供的一种应用上下文的迁移装置的结构框图；
图12为本申请实施例提供的一种通信装置的结构示意图之一；
图13为本申请实施例提供的一种通信装置的结构示意图之二。
具体实施方式
本申请实施例可应用于4G系统、5G系统或者将来的移动通信系统，并具体应用于多接入边缘计算(multi-access edge computing，MEC)架构中。
下面将结合附图，对本申请实施例进行详细描述。
如图1所示的一种MEC架构模型示意图，示意出了边缘数据网络侧的边缘应用服务器以及边缘使能服务器，以及终端设备侧的应用客户端、边缘使能客户端。
其中，边缘数据网络(edge data network，EDN)对应一个部署在边缘的数据网络，可以是本地数据网络(local DN)或本地区域数据网络(local area data network，LADN)。边缘数据网络包含边缘使能功能，可以采用数据网络接入标识符(data network access identifier，DNAI)和数据网络名称(data network name，DNN)标识或者使用数据网络名称和数据网络服务区域(service area)标识。或者可以理解，边缘数据网络可以被视为一个相对于中心云部署在本地的数据中心。可使用DNAI来标识边缘数据网络，一个边缘数据网络可以包含多个本地数据网络(local DN)。
边缘应用服务器(edge application server，EAS)，指示部署在边缘数据网络中的服务器应用程序，也可称为应用实例、边缘应用实例、MEC应用(服务器)、EAS功能等。例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等应用部署运行在EDN的应用实例(instance)。其中，一个应用可在一个或多个EDN中部署一个或多个EAS，部署运行在不同EDN中的EAS可以视为是一个应用的不同EAS。 一个应用的不同EAS可以共享一个域名；一个应用的不同EAS可以使用一个任播IP地址，也可以使用不同的IP地址。边缘应用服务器EAS上还可包含有该EAS对应的应用的应用上下文，可选的，该应用上下文还可包含使用该应用的一个或多个应用用户在EAS上的上下文，例如使用该应用的一个或多个应用用户相关的运行状态信息、EAS对于该一个或多个应用用户的订阅的事务标识。可选的，该应用上下文也可以包含使用该应用的一个或多个应用用户在EAS与核心网的订阅的上下文例如订阅的事务标识等。
边缘使能服务器(edge enabler server，EES)部署在EDN中，可以为部署在EDN中的应用实例即前述EAS提供边缘计算使能服务，以更好的支持应用在MEC的部署和运行。EES可以支持EAS的注册、对终端设备(user equipment，UE)的认证和鉴权或对边缘使能客户端的认证和授权，为UE提供应用实例的信息包括如IP地址信息等。一般情况下，可将一个EAS注册到一个EES上，或者，可通过管理系统将一个EAS的信息配置在一个EES上，则该EES称为该EAS关联的EES，EES可控制(管理)注册或者是配置在该EES上的EAS或者是该EAS的服务EES。EES还支持获取应用实例的信息包括如应用实例的标识和应用实例的地址信息(如IP地址信息)，并进一步将应用实例的信息如应用实例的标识发送给边缘数据网络配置服务器(edge configuration server，ECS)。其中，ECS负责EDN的配置，例如向UE提供EES的信息，向UE提供EAS的信息，以及和应用的DNS交互获取EAS的信息等。进一步还可从其他功能实体获取并保存应用实例和IP地址的信息。如图1示意的MEC架构模型，还示意出了前述ECS。
应用客户端(application client，AC)为应用在终端设备侧的客户端程序，是EAS在终端设备侧的对等实体，应用客户端用于应用用户(user)从应用服务器获取应用业务。应用客户端可以连接到云上的应用服务器获取应用业务，也可以连接到应用部署运行在一个或多个EDN中的EAS以获取应用业务。
边缘使能客户端(edge enabler client，EEC)是EES在终端设备侧的对等实体，EEC用于向EES注册EEC的信息及应用客户端AC的信息，执行安全认证和鉴权，从EES获取EAS的信息包括如EAS的地址信息(如IP地址)以及向应用客户端提供边缘计算使能能力，例如EEC发现服务可将EAS的IP地址返回给应用客户端。
如图1所示，前述终端设备侧的应用客户端AC与边缘应用服务器EAS之间建立通信连接；终端设备侧的边缘使能客户端EEC与边缘使能服务器EES之间建立通信连接。应用用户与应用提供商签订服务协议，可以登录部署在终端设备上的应用客户端AC的方式使用该应用，并通过应用客户端AC与EAS的通信连接交互传输应用数据(application data)；还可通过应用客户端AC以应用编程接口(application program interface，API)的方式，从边缘使能客户端EEC获取边缘使能服务器EES所提供的服务。
按照目前标准的定义，如图1所述的MEC架构包括如下两级发现机制，即EEC从ECS发现EES以及EEC从EES发现EAS。首先，EEC从ECS发现EES包括如下流程：EEC向ECS以请求或者订阅的方式发现其感兴趣的EES或者EDN，获取一个或多个ESS的信息，例如获知UE所处位置对应的EES的信息。其次，EEC从EES发现EAS包括如下流程：EEC向EES请求其所要访问的目标边缘应用实例EAS，可选的EEC在请求中指示出应用用户提供的发现过滤参数；EES根据其本地已注册或称已上线的EAS的信息，和/或者应用用户所提供的发现过滤参数，匹配满足请求的一个或多个EAS，并向EEC反馈满足请求的一个或多个EAS的信息。进而EEC可以将其收到的一个或多个EAS的信息提供 给应用程序客户端AC，以使得AC连接到前述EAS。
在边缘应用运行的过程中，部署有应用程序客户端的终端设备UE存在移动的情况，例如UE从一个EDN对应的区域移动到另一个EDN对应的区域。当终端设备移动到当前的服务区之外，当前提供服务的边缘应用服务器可能无法继续为当前运行在前述移动的UE上的应用程序客户端提供服务，或者当前提供服务的边缘应用服务器已经不是可以为该UE上的应用程序客户端提供服务的最优边缘应用服务器，存在其他的边缘应用服务器更适合为UE上的应用程序客户端服务。则需要选择新的边缘应用程序服务器替换前述当前提供服务的边缘应用服务器(可称为，源边缘应用服务器)，使用新的边缘应用服务器为该UE上的应用程序客户端提供服务。在此过程中会引起应用服务短暂挂起或中断，则需要将源边缘应用在该应用程序客户端的应用上下文迁移至新的边缘应用程序服务器中，以使得应用程序客户端可以在连接到目标边缘应用程序服务器后快速继续进行的业务，以降低应用运行中断的影响。
目前EEC/EES在检测到需要进行应用上行文迁移时，通常需基于MEC架构的通信方式以及发现机制，确定应用上下文迁移的目标EAS，并通知给当前提供服务的EAS以进行应用上下文的迁移。这样的方式信令交互繁多，时延较长，影响应用的运行。
基于此，本申请实施例提供一种应用上下文的迁移方法及装置，通过许可(或者，可描述为“请求”、“委派”)边缘使能功能实体如前述EEC/EES托管应用上下文的迁移，由边缘使能功能实体负责决策迁移应用上下文，甚至全权代理应用上下文迁移的全部操作，以期减少和EAS的信令交互、缩短应用上下文迁移的时延。由于方法及装置解决问题的原理相同，因此方法部分与装置部分实施例可以相互参见，重复之处不再赘述。
本申请实施例中涉及的多个，是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。另外，应当理解，尽管在本发明实施例中可能采用术语第一、第二等来描述各数据、但这些数据不应限于这些术语。这些术语仅用来将各数据彼此区分开。
下面将结合附图，对本申请实施例提供的应用上下文的迁移方法进行详细描述。
如图2所示，本申请实施例提供一种应用上下文的迁移方法，该方法可应用于前述MEC架构模型。该方法包括如下流程。
S201，应用功能实体向发送第一信息，所述第一信息用于指示迁移所述应用功能实体关联的应用上下文。
其中，该第一信息可以是一个请求消息，该请求消息用于请求迁移所述应用功能实体关联的应用上下文。该第一信息还可以是一个同时具备请求和订阅所述应用上下文迁移的消息，即请求对所述应用上下文进行迁移，并订阅该应用上下文迁移的通知。该第一信息可以是一个服务API(service API)，该API可以由EES或EEC提供。其中，迁移可以理解为relocation，迁移所述应用功能实体关联的应用上下文可以理解为：通过一系列操作最终将该应用功能实体服务的一个、多个或全部应用用户的服务(serving)EAS从源EAS切换为目标EAS。另外该第一信息还可以是一个消息中的参数，用于指示迁移应用上下文的服务或操作，该参数可以为一组枚举值如{应用上下文的迁移事件监测(detection)、应用上下文的迁移决策(decision)、应用上下文的迁移执行(execution)、应用上下文的迁移后的清理(cleanup)}中的一个或多个的合并。示例性的，若该参数为“应用上下文的迁 移事件监测(detection)&应用上下文的迁移决策(decision)&应用上下文的迁移执行(execution)&应用上下文的迁移后的清理(cleanup)”，表示边缘使能功能实体执行上述服务或操作。该第一信息还可以是使用一个参数的特定比特(bit)位来指示。
其中，应用功能实体可指示前述MEC架构中的应用程序客户端或者是边缘应用服务器；边缘使能功能实体可指示前述MEC架构中的边缘使能客户端或者边缘使能功能实体。一种可选的实施方式中，应用功能实体可以是边缘应用服务器EAS，边缘使能功能实体可以是边缘使能服务器EES；另一种可选的实施方式中，应用功能实体可以是应用程序客户端AC，边缘使能功能实体可以是边缘使能客户端EEC。
应用功能实体关联的应用上下文指示该应用功能实体所对应的应用上下文，可选的，该应用上下文具体可以包括该应用功能实体关联的一个或多个或全部应用用户相关的应用上下文。可选的，应用上下文包含标识信息，所述标识信息用于唯一标识一个应用用户的应用上下文。示例性的，若需区分不同应用用户相关的应用上下文，前述标识信息可以是UE标识如IP地址、用户永久标识符(subscription permanent identifier，SUPI)等，此外前述标识信息也可以是应用客户端的标识如统一资源定位器(uniform resource locator，URL)地址。
可选的，边缘使能功能实体还可响应于前述第一信息，向应用功能实体发送第一信息的响应信息。
S202，当发生所述应用上下文的迁移的触发事件时，边缘使能功能实体根据所述第一信息确定对所述应用上下文进行迁移。
可选的，边缘使能功能实体在检测到前述应用功能实体相关的终端设备移动时，可确定发生业务连续性事件，即检测到应用上下文的迁移的触发事件，可以理解为边缘使能功能实体可以检测到一些事件，并根据这些时间判断可能需要进行应用上下文迁移。
本申请实施例中，应用功能实体将对其关联的应用上下文的迁移托管至边缘使能功能实体，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实施方式中，应用功能实体为边缘应用服务器EAS，边缘使能功能实体为边缘使能服务器EES；边缘使能功能实体还可执行如下(1)～(5)中的一项或多项操作：
(1)检测所述应用上下文的迁移的触发事件。
(2)发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；其中，目标应用功能实体可以是边缘应用服务器EAS。EES可以发现目标EAS，并将前述发送第一信息的EAS关联的应用上下文迁移至该目标EAS。前述发送第一信息的EAS对应的应用与目标EAS对应的应用相同，即目标EAS与发送第一信息的EAS为同一个应用的两个不同应用实例。
(3)将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同，即目标EAS与发送第一信息的EAS为同一个应用的两个不同应用实例。
(4)将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同(即目标EAS 与发送第一信息的EAS为同一个应用的两个不同应用实例)。可选的，目标应用功能实体的信息包括该目标应用功能实体在其关联的边缘使能功能实体上的注册信息，以使得前述应用部署在终端设备上的应用程序客户端能够重连接到目标应用功能实体。
(5)将所述应用上下文的迁移的信息发送至核心网网元；其中，核心网网元可以是为网络能力开放功能(network expose function，NEF)网元，会话管理功能(session management function，SMF)网元等。
在一种可选的实施方式中，应用功能实体为应用客户端AC，边缘使能功能实体为边缘使能客户端EEC；边缘使能功能实体还可执行如下(1)～(3)中的一项或多项操作：
(1)检测所述应用上下文的迁移的触发事件。
(2)发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；其中，目标应用功能实体可以是边缘应用服务器EAS。EES可以发现目标EAS，并将前述发送第一信息的EAS关联的应用上下文迁移至该目标EAS。前述发送第一信息的EAS对应的应用与目标EAS对应的应用相同，即目标EAS与发送第一信息的EAS为同一个应用的两个不同应用实例。
(3)将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同(即目标EAS与发送第一信息的EAS为同一个应用的两个不同应用实例)。可选的，目标应用功能实体的信息包括该目标应用功能实体在其关联的边缘使能功能实体上的注册信息，以使得前述应用部署在终端设备上的应用程序客户端能够重连接到目标应用功能实体。
在一种可选的实施方式中，第一信息还可具体指示出迁移应用功能实体关联的应用上下文相关的操作(或称，服务)，则边缘使能功能实体在收到第一信息，执行第一信息所指示的操作。其中，该操作可以指示独立的一项操作，该一项操作只包含一个原子功能，该原子功能也可以称为原子操作或原子服务)；或者该操作可以指示一个复合操作，该复合操作包括多个原子功能。将涉及迁移应用上下文的部分权限托管给边缘使能功能实体，更加灵活。示例性的，以前述EAS向EES发送第一信息为例，EAS可通过第一信息指示EES实施以下中一项、多项或者全部：检测应用上下文的迁移的触发事件、决策迁移应用上下文、发现目标EAS、将应用上下文从EAS传送(transfer)至目标EAS或目标EES、将目标EAS的信息发送给终端设备。
在一种可选的实施方式中，还可设定边缘使能功能实体实施第一信息的指示所需满足的条件。可选的，应用功能实体可向边缘使能功能实体发送第一条件信息，该第一条件信息用于指示第一信息的第一生效条件。其中，应用功能实体可将第一条件信息与第一信息一起发送给边缘使能功能实体，也可以分开发送第一信息和第一条件信息给边缘使能功能实体，本申请实施例对此不进行限定。
可选的，第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
其中，第一信息的生效时长指示边缘使能功能实体接收到第一信息时起的指定时长内，边缘使能功能实体可以实施第一信息的指示；所述第一信息的生效时段指示边缘使能功能实体在前述生效时段内可以实施第一信息的指示；所述第一信息所适用的应用客户端可以为UE标识、UE的IP地址、应用程序客户端的标识、或边缘使能客户端的标识等，该参 数具体指示边缘使能功能实体可以针对使用该UE标识对应终端设备上应用客户端的应用用户的应用上下文，实施第一信息的指示，可选的若第一有效条件未包含第一信息所适用的应用客户端，则表示边缘使能功能实体可以针对所有应用用户的应用上下文实施第一信息的指示。所述应用上下文的迁移时长小于预设时间阈值指示边缘使能功能实体在应用上下文的迁移时长小于预设时间阈值的情况下，才可以实施第一信息的指示。所述应用上下文的大小小于预设大小阈值指示边缘使能功能实体在所述应用上下文的大小小于预设大小阈值的情况下，才可以实施第一信息的指示。所述应用功能实体过载用于表示应用功能实体可在过载的情况下，可以实施第一信息的指示。
可选的，还可设定支持更改边缘使能功能实体实施第一信息的指示所需满足的条件。示例性的一种方式，应用功能实体还可向边缘使能功能实体发送第二条件信息，该第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。一种可能的设计中，第二生效条件和第一生效条件包含相同的参数但参数的取值不同。例如，第一生效条件和第二生效条件中均包含第一信息的生效时长，但具体的生效时长不同。又如，第一生效条件和第二生效条件中针对预设时间阈值的设定不同等。另一种可能的设计中，第二生效条件和第一生效条件包含不同的参数。例如第二生效条件包含第一信息所适用的应用客户端，而第一生效条件不包含第一信息所适应的应用客户端。
在一种可选的实施方式中，边缘使能功能实体还可获取应用功能实体所关联的应用上下文，以便于实施诸如对于应用上下文的大小判断，对于应用上下文的迁移时长的确定，执行对应用上下文的传送(transfer)等操作。
可选的，若是EAS通过第一信息指示EES迁移EAS关联的应用上下文。EAS可将其关联的应用上下文发送给EES。具体的，EAS可基于EES能够访问的存储地址(或称托管地址)将应用上下文发送给EES。其中，该存储地址存储了应用上下文，可选的，关于EES能够访问的存储地址可参照如下两种方式任一种实施。第一种方式：可在EAS本地配置的托管地址，该地址是用于EAS存储其服务的一个或多个应用用户的需要迁移或同步的应用上下文，EAS将需迁移的应用上下文保存在该托管地址。第二种方式：EES可以主动或者是在EAS的请求下，向EAS发送存储地址，以使得EAS基于前述存储地址，将应用上下文同步给EES。为了区分该EAS服务的多个应用用户的应用上下文，EAS可以为每个用户的应用上下文分配一个标识，该标识可以是应用用户的标识，或者该标识可以是应用用户所使用客户端对应的终端设备的IP地址或终端设备的标识，或者该标识可以是其他类型的应用上下文标识。为了保持需要迁移的应用上下文的是最新的，EAS可以周期性例如每隔5s向EES同步最新的应用上下文，该应用上下文可以是以覆盖的方式存储，或者以追加的方式存储。在追加方式下，如果应用上下文超过预设大小，则可以丢弃时间最早保存的应用上下文，或者每次保存的用于迁移(relocation)的应用上下文都携带时间戳或检查点(checkpoint)信息。
可选的，若是AC通过第一信息指示EEC迁移AC关联的应用上下文，AC关联的应用上下文保存于AC对应的应用在EDN中部署运行的EAS。则可参照如下两种方式将该应用上下文存储到EES：第一种方式：AC和EAS交互，请求EAS将应用上下文同步到EES。第二种方式：EEC需要向前述EAS关联的EES请求同步应用上下文，EES向EAS请求同步应用上下文，则EAS可以将应用上下文同步到EES。
以下结合对于不同应用特性的考虑，对于上述应用上下文的迁移方法的实现过程进行 详细说明。
对于一些应用，例如业务运行比较平稳的应用例如视频应用，可以允许在任意时刻执行应用上下文的迁移。在一种可选的实施方式中，上述应用上下文的迁移方法可以基于应用功能实体的注册流程实现。则进一步可选的，第一信息可被包含在应用功能实体的注册信息中传输至边缘使能功能实体。
示例性的，如图3所示的一种EAS向EES注册的流程，包括如下步骤。
S301，EAS向EES发送注册请求(registration request)消息或者注册更新请求(registrationup date request)消息，该注册请求消息或者注册更新请求消息中携带注册信息，该注册信息包含前述第一信息。可选的，注册信息可以是EAS profile，EAS profile中包含的第一信息可以称为应用迁移委派指示(relocation delegate indication)、应用迁移许可、或应用迁移代理、或应用迁移决策许可、应用迁移决策许可、或应用迁移决策代理等。可选的，EAS profile包括如下表1所示的内容。
表1
Figure PCTCN2020119763-appb-000001
Figure PCTCN2020119763-appb-000002
S302，EES向EAS发送注册响应(registration response)消息或者注册更新响应(registration update response)消息。
可选的，EAS可以在注册响应消息或者注册更新响应消息中，携带应用上下文的存储地址(或称，托管地址)，用于指示EAS将应用上下文发送到EES。该应用上下文为迁移时所需要同步的应用上下文。该应用上下文的存储地址可以为IP地址和端口号，或者为一个URL地址。在边缘数据网络环境中，一般EES和EAS均部署在一个数据中心，并可能部署在同一存储资源上，则EAS将应用上下文发送到EES可以理解为EAS将应用上下文保存在一个存储地址标识的存储单元中。而EES可读取该存储地址标识的存储单元中的应用上下文，即EAS和EES可以是同一个节点中的两个逻辑功能模块，前述应用上下文传送可以是通过应用上下文的存储空间的共享和权限管理来实现，与传统的两个节点之间通过物理线缆进行数据交换的方式不同。其中，存储地址及该存储地址对应的存储单元可以由EES进行管理。
S303，当发生应用上下文的迁移的触发事件时，若EES基于EAS的注册信息判断该应用上下文的迁移委派给了EES，则可确定对应用上下文进行迁移。
可选的，EES可以自行决策迁移应用上下文，实施迁移应用上下文的相关操作，例如当第一信息指示EES迁移应用上下文包含传送应用上下文时，相关操作包括以下一项、多项或全部：EES发现目标EAS；EES将应用上下文传送到目标EAS或目标EAS关联的EES；EES通知EEC应用上下文切换完成，并将目标EAS的信息发送给EEC；EES向3GPP核心网网元发送应用上下文的迁移的信息，例如目标EAS的信息，目标EAS对应的N6的信息。当第一信息指示EES迁移应用上下文不包含传送应用上下文或EES没有应用上下文时，相关操作包括以下一项、多项或全部：EES发现目标EAS；EES通知源EAS目标EAS的地址或EES请求源EAS向目标EAS传送应用上下文；EES通知EEC应用上下文切换完成，并将目标EAS的信息发送给EEC；EES向3GPP核心网网元发送应用上下文的迁移的信息，例如目标EAS的信息，目标EAS对应的N6的信息。另外，可选的目标EAS关联的EES可代替该目标EAS，确定是否接收前述应用上下文的迁移；此时，EES将应用上下文传送到目标EAS关联的EES，该目标EAS关联的EES还可以代替该目标EAS确定是否接收应用上下文。另外，EES根据EAS注册信息中的第一信息，还可以执行：检测应用上下文的迁移的触发事件。
示例性的，如图4所示的一种AC向EEC的注册流程，包括如下步骤。
S401，AC向EEC发送注册请求(registration request)消息或者注册更新请求(registrationup date request)消息，该注册请求消息或者注册更新请求消息中携带注册信息，该注册信息包含前述第一信息。可选的，注册信息可以是AC profile，AC profile中包 含的第一指示信息可以称为应用迁移的委派指示(relocation delegate indication)、应用迁移许可、或应用迁移代理、或应用迁移决策许可、应用迁移决策许可、或应用迁移决策代理等。可选的，AC profile包括如下表2所示的内容。
表2
Figure PCTCN2020119763-appb-000003
S402，EEC向AC发送注册响应(registration response)消息或者注册更新响应(registrationup date response)消息。
S403，当发生应用上下文的迁移的触发事件时，若EEC基于AC的注册信息判断该应用上下文的迁移委派给了EEC，则可确定对应用上下文进行迁移。
可选的，EEC可在自行决策迁移应用上下文，实施迁移应用上下文的相关操作，例如EEC从ECS获取目标EES的信息，EEC从该目标EES获取目标EAS的信息，其中，目标EES与目标EAS关联；EEC触发AC，AC触发源EAS，源EAS将应用上下文发给至目标EAS。在应用上下文迁移之后，AC将应用数据切换到目标EAS。又如，EEC通知目标EES可能需要应用上下文重定位；目标EES获取目标EAS的信息，向目标EAS发送ACR请求消息；目标EAS发起源EAS和目标EAS之间的应用上下文传输。在上下文迁移之后，AC将应用数据切换到目标EAS。又如，EEC从源EES上获取目标EAS信息，EEC通过源EES通知源EAS进行应用上下文的迁移；源EAS将应用上下文发送至目标EAS。在应用上下文迁移后，AC将应用数据切换到目标EAS。
对于一些应用，例如业务运行存在尖峰或者低峰，也即忙碌或者空闲的情况的应用，可以动态的将迁移应用上下文相关的权限托管给边缘使能功能实体，可选的，可采用前述至少第一信息的生效条件的方式，设定边缘使能功能实体需在特定的条件下实施迁移应用 上下文相关的权限。
示例性的，如图5示意出一种EAS向EES指示迁移应用上下文的方法流程，包括如下步骤。
S501，EAS发送第一请求消息给EES。其中，第一请求消息用于请求将应用上下文迁移托管(委派)给EES，或理解第一请求消息用于请求迁移所述应用功能实体关联的应用上下文。还可以理解第一请求消息还可以是一个同时具备请求和订阅所述应用上下文迁移的消息，即请求对所述应用上下文进行迁移，并订阅该应用上下文迁移的通知。该第一信息可以是一个服务API(service API)，该API可以由EES提供；第一请求消息也可以描述为应用上下文迁移的决策权委派、托管请求消息、上下文迁移请求、或全服务的上下文迁移请求等。第一请求消息包含指示或请求EES对应用上下文迁移做出决策。
可选的，EAS可以在业务空闲或者预测业务将要空闲时，发送第一请求消息给EES。
可选的，如图5所示，第一请求消息中携带前述第一信息和第一条件信息；具体的，第一信息可以是应用上下文迁移的委派指示(relocation delegate indication)。可选地，该应用上下文迁移的委派指示包含将应用上下文迁移的决策权委派给EES。第一条件信息用于指示第一信息的第一生效条件，第一生效条件所包括的内容可参照前述实施例，本申请实施例对此不再进行赘述。可选的，EES可将收到的第一信息和第一条件信息保存下来。
S502，EES响应于第一请求消息发送第一响应消息给EAS。
可选的，第一响应消息中可携带事务标识(transaction id)，该事务标识用于EAS后续对前述第一信息后续进行操作，或者该事务标识用于标记EES保存的前述第一信息和第一条件信息。便于后续EAS更新托管事务或者取消托管事务。
可选的，第一响应消息中可携带应用上下文的存储地址，用以指示EAS基于前述存储地址将应用上下文同步给EES。
S503，当发生应用上下文的迁移的触发事件时，若EES基于EAS的发送第一请求消息判断该应用上下文的迁移委派给了EES且满足第一条件信息，则可确定对应用上下文进行迁移。
可选的，EES可在自行决策迁移应用上下文，实施迁移应用上下文的相关操作，例如EES发现目标EAS；EES通知源EAS目标EAS的地址，或者EES请求源EAS向目标EAS传送应用上下文；EES通知EEC应用上下文切换完成，并将目标EAS的信息发送给EEC；EES向3GPP核心网网元发送应用上下文的迁移的信息，例如目标EAS的信息，目标EAS对应的N6的信息。另外，可选的目标EAS关联的EES可代替该目标EAS，确定是否接收前述应用上下文的迁移。
S504，EAS向EES发送托管更新请求消息，托管更新请求消息用于请求更新前述第一信息和/或者第一条件信息。需要说明的是，托管更新请求消息也可称为应用上下文迁移的委派或托管请求消息，或者第二请求消息，或者其他的消息，只要其作用为请求更新前述第一信息和/或者第一条件信息即可，本申请实施例对此不进行限定。
可选的，托管更新请求消息中携带第二条件信息，第二条件信息用于指示第一信息的第二生效条件。可选的，托管更新请求消息中还携带有前述事务标识，以使得EES可以根据事务标识确定EAS所要更新的托管事务。其中，第二生效条件与第一生效条件的不同可参照前述实施例，本申请实施例对此不再进行赘述。
示例性的，若EAS需要更新托管的时长，即更新第一信息的有效时长；则可在托管更 新请求消息中携带第二条件信息，该第二条件信息包括前述更新的第一信息的有效时长。则EES在收到携带该第二条件信息的托管更新请求消息后，若保存下来的第一条件信息包含第一信息的生效时长这一项内容，则将这一项内容替换为更新的第一信息的生效时长；若原保存下来的第一条件信息不包括第一信息的生效时长这一内容，则在第一条件信息中添加前述更新的第一信息的生效时长。
S505，EES响应于托管更新请求消息发送第二响应消息给EAS。
可选的，第二响应消息中可携带事务标识(transaction id)，该事务标识用于标记EAS将应用上下文迁移的决策权委派或称托管给EES的托管事务，或者该事务标识用于标记EES保存的前述第一信息和第一条件信息。便于后续EAS更新托管事务或者取消托管事务。
可选的，第二响应消息中可携带应用上下文的存储地址，用以指示EAS基于前述存储地址将应用上下文同步给EES。
S506，EAS向EES发送托管取消请求消息。托管取消请求消息用于请求取消将应用上下文的迁移委派或托管给EES的。需要说明的是，托管取消请求消息也可称为应用上下文迁移的委派或应用上下文迁移的托管取消请求消息，或者第三请求消息，或者其他的消息，只要其作用为请求取消EES对应用上下文迁移的托管即可，本申请实施例对此不进行限定。
可选的，托管取消请求消息中还携带有前述事务标识和/或第一信息，以使得EES可以根据事务标识和/或第一信息，确定EAS所要取消的托管事务。可选的，EAS可以在业务进入尖峰时刻或者预测业务将要进入尖峰时刻时，发送托管取消请求消息给EES。
S507，EES响应于托管取消请求消息发送第三响应消息给EAS，第三响应消息用于指示EES同意托管取消请求消息，也即EES同意取消其对应用上下文迁移的决策权。
另外，本申请实施例还提供一种应用于边缘使能功能实体之间指示迁移应用上下文的方法。
如图6所示，本申请实施例提供另一种应用上下文的迁移方法，该方法可应用于前述MEC架构模型。该方法包括如下流程。
S601，第一边缘使能功能实体向第二边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文。该应用功能实体为在第一边缘使能功能实体上注册的应用功能实体。
其中，第一边缘使能功能实体可以为前述MEC架构中的边缘使能服务器，第二边缘使能功能实体可以为前述MEC架构中的边缘使能客户端。应用功能实体可以是在边缘使能服务器上注册的边缘应用服务器。该第一信息可以承载在EES向EEC发送的EEC注册响应消息(EEC registration response)中，该第一信息还可以承载在EES向EEC发送的其他消息中。第一信息可以称为应用迁移的委派指示(relocation delegate indication)，该应用迁移的委派指示还可以包含将应用迁移的决策权委派给EEC。
S602，当发生所述应用上下文的迁移的触发事件时，第二边缘使能功能实体根据所述第一信息确定对所述应用上下文进行迁移。
可选的，第二边缘使能功能实体在检测到前述应用功能实体相关的终端设备移动时，可确定发生业务连续性事件，即检测到应用上下文的迁移的触发事件。
本申请实施例中，边缘使能服务器将应用上下文迁移托管至边缘使能客户端，边缘使能客户端在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短时延，有助于业务的正常运行。
在一种可选的实施方式中，边缘使能服务器中可以预先配置有第一信息。可选的，上述应用上下文的迁移方法可以基于边缘使能客户端向边缘使能服务器的注册流程实现。
示例性的，如图7所示的一种EEC向EES注册或者向EES注册更新的流程，包括如下步骤。
S701，EEC向EES发送注册请求(registration request)消息或者注册更新请求(registrationup date request)消息，该注册请求消息或者注册更新请求消息中携带注册信息，该注册信息可以是EEC profile。具体的，EEC profile包含如下表3所述的内容。
表3
Figure PCTCN2020119763-appb-000004
S702，EES向EEC发送注册响应(registration response)消息或者注册更新响应(registration update response)消息。
可选的，EAS可以在注册响应消息或者注册更新响应消息中，携带EES中所预配置的第一信息，以指示EEC迁移应用上下文。该第一信息可以来自于EAS或者预配置在EES。
S703，当EEC检测到应用上下文的迁移的触发事件时，若EEC基于EES发送的注册响应消息或者注册更新响应消息，判断该应用上下文迁移的委派给了EEC，则可确定对应用上下文进行迁移。
在另一种可选的实施方式中，上述应用上下文的迁移方法可以基于边缘使能客户端向边缘使能服务器请求发现边缘应用服务器的流程实现。
示例性的，如图8所示的一种EEC通过EES发现EAS的流程，包括如下步骤。
S801，EEC向EES发送EAS发现请求(EAS discovery request)消息。
可选的，EAS发现请求消息中携带EEC ID和安全凭据。可选的，EAS发现请求消息中携带EAS发现过滤参数，该EAS发现过滤参数用于指示目标EAS或目标EAS的类别(例如，游戏类应用程序)。
S802，EES向EEC发送EAS发现响应(EAS discovery response)消息。
其中，EAS发现响应消息中携带已发现的EAS的信息；其中，EAS的信息包括EAS的 注册信息，该EAS的注册信息中包含前述第一信息。具体的，例如EAS发现响应消息中携带EAS profile，该EAS profile中包含有应用迁移的委派指示(relocation delegate indication)。可选的，若EAS发现请求消息中携带EAS发现过滤参数，EES可以根据该EAS发现过滤参数，确定已发现的EAS，从而在EAS发现响应消息中携带已发现的EAS的信息。
S803，当发生应用上下文的迁移的触发事件时，若EEC基于EES发送的EAS发现响应消息，判断该应用上下文迁移的委派给了EES，则可确定对应用上下文进行迁移。
进一步，本申请实施例还提供一种预先为边缘使能功能实体配置部分应用的应用上下文的迁移的方案。
一种可选的实施方式中，可以在边缘使能服务器EES上配置一组应用列表，该应用列表中的任一应用的应用上下文的迁移被委派给EES，或者说EES具备迁移该应用列表中任一应用的应用上下文的权限。可选的，应用列表中包含一个或多个EAS标识，任一EAS标识用于指示该EAS标识所对应的应用的应用上下文的迁移被委派给EES。其中，EAS标识所对应的应用指的是部署运行在EAS标识所指示EAS的应用。例如EES上配置的一组应用列表包含EAS#ID1和EAS#ID2。其中，EAS#ID1指示在标识为ID1的EAS上部署运行的应用的应用上下文的迁移被委派给EES，EAS#ID2指示在标识为ID2的EAS上部署运行的应用的应用上下文的迁移被委派给EES。
基于此，当EES检测到应用上下文的迁移的触发事件时，EES可以通过查询预配置的应用列表，判断该应用上下文为应用列表中某一应用的应用上下文，即判断该应用上下文迁移的决策权委派给了EES，进而EES可确定对该应用上下文进行迁移。
可选的，针对前述应用列表中的任一应用，可以该任一应用在EDN上部署运行的边缘应用服务器EAS配置托管指示信息，托管指示信息用于指示该任一应用的应用上下文迁移的决策权被委派给EES。可选的，该托管指示信息可以是前述第一信息，具体的在EAS profile中配置该托管指示信息。
可选的，对于边缘应用服务器EAS而言，若EAS中配置了托管指示信息，则EAS可以将应用上下文同步至ESS。如图9所示，本申请实施例还提供一种同步应用上下文的方法流程示意图。
S901，EAS判断EAS本地是否配置托管地址。其中，EAS中配置了托管指示信息。
S902，在EAS本地有可用托管地址(或称，存储地址)的情况下，将需迁移的应用上下文保存在该托管地址。该托管地址可以是EAS在注册时从EES获取的。
S903，在EAS本地不存在可用托管地址的情况下，EAS向EES发送用于请求存储地址的请求消息。其中，请求消息中可以携带需迁移的应用上下文的应用用户的标识，该标识可以是应用用户所使用客户端对应的终端设备的IP地址或终端设备的标识。
S904，EES响应于EAS的前述请求消息，向EAS发送该请求消息的响应消息。其中，该响应消息中携带EES为EAS分配的存储地址。可选的，该响应消息中还携带需迁移的应用上下文的标识，该标识由EES指定。该标识可以是应用用户的标识，或者该标识可以是应用用户所使用客户端对应的终端设备的IP地址或终端设备的标识，或者该标识可以是其他类型的应用上下文标识。
S905，EAS基于本地可用的托管地址或者EES指示的存储地址，将需迁移的应用上下文同步到EES。可选的，应用上下文中包含用于标识该应用上下文的标识，该标识可以是 从EES接收到的应用上下文的标识，或者是由EAS指定的应用上下文的标识。
在另一种可选的实施方式中，可以在边缘使能客户端EEC上配置一组应用列表，该应用列表中的任一应用的应用上下文的迁移被委派给EEC，或者说EEC具备对于该应用列表中任一应用的应用上下文的迁移。可选的，应用列表中包含一个或多个EAS标识，任一EAS标识用于指示该EAS标识所对应的应用的应用上下文的迁移被委派给EES。其中，EAS标识所对应的应用指的是部署运行在EAS标识所指示EAS的应用。例如EEC上配置的一组应用列表包含EAS#ID1和EAS#ID2。其中，EAS#ID1指示在标识为ID1的EAS上部署运行的应用的应用上下文的迁移被委派给EEC，EAS#ID2指示在标识为ID2的EAS上部署运行的应用的应用上下文的迁移被委派给EEC。
基于此，当EEC检测到应用上下文的迁移的触发事件时，EEC可以通过查询预配置的应用列表，判断该应用上下文为应用列表中某一应用的应用上下文，即判断该应用上下文迁移的决策权委派给了EEC，进而EEC可确定对该应用上下文进行迁移。
示例性的，如图10示意出一种EAS向EES指示迁移应用上下文的方法流程，包括如下步骤。
S1001，EAS向源EES发送应用上下文迁移(订阅)请求。其中，应用上下文迁移(订阅)请求可选地包含应用上下文迁移服务模式，服务模式可以为全服务(full service)模式。应用上下文迁移(订阅)请求用于请求EES执行对应用上下文相关的全部操作，这些操作包括检测应用上下文明迁移的触发事件、决策应用上下文需要迁移、执行应用上下文的迁移、迁移后的一些清理操作，进一步这些操作还包括通知EEC目标EAS的信息(具体包括目标EAS的接入地址如IP地址)，通知移动通信网络应用迁移的信息。该请求消息中可选地包含一个或多个应用用户的标识，该标识可以是应用用户所使用的客户端所在的终端的标识或IP地址。如果该请求不包含应用用户的标识，则可以理解EAS请求EES对该EAS服务的全部应用用户执行应用上下文迁移的前述相关操作。该应用上下文迁移(订阅)请求或该应用上下文迁移服务模式可以视为前述第一信息。
S1002，源EES向EAS发送应用上下文迁移(订阅)响应。该响应消息中可以包含用于应用上下文同步的地址，该地址可以是IP地址和端口号，还可以是一个URL。该地址用于EAS向该地址存储并更新需要迁移的应用上下文。应用上下文可以是该EAS服务的一个或多个用户的需要迁移的上下文。该地址EES可以访问读取需要迁移的应用上下文。对于该地址的详细描述可以参考前述实施例中的对应描述。
S1003，源EES检测应用上下文的触发事件。可选地，源EES可以在收到S1001的请求消息后，向核心网网元订阅用户面路径管理事件通知，并从核心网网元收到用户面路径管理事件通知消息，该消息中携带目标DNAI，该目标DNAI指示EAS可能潜在部署在该目标DNAI对应的位置。可选地，源EES还可以从一个或多个应用用户对应的终端设备订阅UE的位置及其改变，从而得到该一个或多个终端设备最新的位置。可选地，源EES还可以从核心网网元定远一个或多个应用用户对应的终端设备订阅UE的位置及其改变，从而得到该一个或多个终端设备最新的位置。源EES可以根据用户面路径管理事件通知及其目标DNAI或UE的位置，判断该一个或多个应用用户的可能需要应用上下文的迁移。
S1004，源EES决策该一个或多个应用用户的需要应用上下文的迁移。例如，源EES可以根据UE的位置移动出当前源EES对应的服务区域(或称为最佳服务的区域)，从而判断需要进行应用上下文的迁移。
S1005，可选地，源EES可以在确定对一个或多个应用用户执行应用上下文时，向源EAS发送应用上下文迁移的通知消息，通知源EAS该一个或多个用户的需要进行应用上下文的迁移。进一步还包括通知EAS准备好需要迁移的应用上下文。
S1006，源EES向边缘配置服务器ECS发送EES请求消息，用于获取匹配该一个或多个用户对应的位置或目标DNAI并且可以提供该应用的服务的目标EAS的信息的目标EES。源EES在从ECS获取到目标EES后，向目标EES发送EAS请求消息，用于请求传送该一个或多个用户的应用上下文，在目标EES确定目标EAS且目标EAS可以接受该应用上下文后，目标EES向源EES发送响应消息，指示接受该应用上下文，进一步源EES向目标EES发送的请求消息还可以用于获取提供该应用的服务的目标EAS的信息。可选地，源EES从目标EES获取到目标EAS的信息。
S1007，在步骤S1002之后，步骤S1008之前，源EAS向源EES同步需要迁移的应用上下文。对于源EAS向源EES同步应用上下文的描述可以参考前述实施例中的对应描述。
S1008，源EES在确定目标EAS可以接受该应用上下文时，源EES从前述地址读取需要迁移的应用上下文，并将该应用上下文传送至目标EES。目标EES将接收到的应用上下文保存特定存储地址标识存储区域。
S1009，目标EES向目标EAS发送应用上下文迁移通知消息，用于通知目标EAS有应用上下文需要接收。该消息中可以包含读取应用上下文的地址信息，对应于S1008中目标EES存储应用上下文的存储地址。该步骤可选。
S1010，目标EAS向目标EES发送应用上下文获取请求，该请求消息用户请求获取该应用上下文。该步骤可选。
S1011，目标EES向目标EAS发送应用上下文获取响应，用于指示接受请求消息。
S1012，目标EES在接收到应用上下文后，将应用上下文发送给目标EAS。可以理解为目标EAS和目标EES处理应用上下文的方式例如是通过存储地址的映射或应用上下文在同一个物理存储设备上不同存储空间的拷贝或剪切实现，具体和前述源EAS和源EES处理应用上下文的方式类似，还可以参考前述实施例中的对应描述。
S1013，可选地，在应用上下文传送完成后，源EES向EEC发送应用上下文迁移通知消息，该消息中用于指示应用上下文传送完成，该消息中可以包含目标EAS的信息，具体可以是EAS的IP地址和端口号。进一步EEC向AC发送通知消息，通知AC应用上下文传送完成，进一步还包含目标EAS的信息。
S1014，可选地，在应用上下文传送完成后，源EES向源EAS发送应用上下文迁移通知消息，该消息中用于指示应用上下文传送完成。
S1015，可选地，源EES向核心网网元发送应用迁移的消息。具体地包含目标EAS的地址信息、目标N6的路由信息等。图10中未示意出该S1015。
基于同一构思，参见图10，本申请实施例提供了一种应用上下文的迁移装置1100，该装置1100包括通信模块1101和处理模块1102。
(一)该应用上下文的迁移装置1100可以应用于边缘使能功能实体，具体的，该应用上下文的迁移装置1100可以是边缘使能功能实体，或者可以是应用于边缘使能功能实体，或者可以能够支持边缘使能功能实体执行数据传输方法的装置。以下对应用于边缘使能功能实体的应用上下文的迁移装置1100中模块的功能或者执行过程进行详细说明。
通信模块1101，用于接收来自应用功能实体的第一信息，所述第一信息用于指示迁移 所述应用功能实体关联的应用上下文；
处理模块1102，用于在发生所述应用上下文的迁移的触发事件时，根据所述第一信息确定对所述应用上下文进行迁移。
本申请实施例中，应用功能实体将对其关联的应用上下文的迁移托管至边缘使能功能实体，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实施方式中，所述处理模块1102，还用于根据所述第一信息，执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实施方式中，所述通信模块1101，具体用于接收来自所述应用功能实体的注册信息，所述注册信息包含所述第一信息。
在一种可选的实施方式中，所述通信模块1101，还用于接收来自应用功能实体的第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实施方式中，所述第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
在一种可选的实施方式中，所述通信模块1101，还用于接收来自所述应用功能实体的第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实施方式中，所述通信模块1101，还用于接收来自所述应用功能实体的所述应用上下文。
在一种可选的实施方式中，在接收来自所述应用功能实体的所述应用上下文之前，所述通信模块1101，还用于向所述应用功能实体发送所述应用上下文的存储地址。
在一种可选的实施方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
(二)该应用上下文的迁移装置1100可以应用于应用功能实体，具体的，该应用上下文的迁移装置1100可以是应用功能实体，或者可以是应用于应用功能实体，或者可以能够支持应用功能实体执行数据传输方法的装置。以下对应用于应用功能实体的应用上下文的迁移装置1100中模块的功能或者执行过程进行详细说明。
处理模块1102，用于确定第一信息。
通信模块1101，用于向边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文；通信模块1101，还用于接收来自边缘使能功能实体的响应于所述第一信息发送的响应信息。
本申请实施例中，边缘使能功能实体被托管有应用上下文的迁移，边缘使能功能实体在检测到需要迁移该应用上下文时，可自行决策对该应用上下文进行迁移，能够减少迁移 应用上下文的信令交互，缩短应用上下文迁移的时延，有助于业务的正常运行，减少终端应用客户端的业务运行被影响或打断的时间。
在一种可选的实施方式中，所述第一信息还用于指示所述边缘使能功能实体执行如下一项或多项操作：检测所述应用上下文的迁移的触发事件；发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；将所述应用上下文的迁移的信息发送至核心网网元；其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
在一种可选的实施方式中，所述通信模块1101，还用于向所述边缘使能功能实体发送注册信息，所述注册信息包含所述第一信息。
在一种可选的实施方式中，所述处理模块1102，还用于确定第一条件信息；所述通信模块1101，还用于向所述边缘使能功能实体发送第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
在一种可选的实施方式中，所述第一条件信息包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息生效的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值、所述应用功能实体过载。
在一种可选的实施方式中，所述处理模块1102，还用于确定第二条件信息；所述通信模块1101，还用于向所述边缘使能功能实体发送第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
在一种可选的实施方式中，在向边缘使能功能实体发送第一信息之后，所述通信模块1101，还用于向所述边缘使能功能实体发送所述应用上下文。
在一种可选的实施方式中，在向所述边缘使能功能实体发送所述应用上下文之前，所述通信模块1101，还用于接收来自所述边缘使能功能实体的所述应用上下文的存储地址；基于所述存储地址，向所述边缘使能实体发送所述应用上下文。
在一种可选的实施方式中，所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
基于同一构思，如图12所示，本申请实施例提供一种通信装置1200。示例性地，通信装置1200可以是芯片或芯片系统。可选的，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置1200可以包括至少一个处理器1210，通信装置1200还可以包括至少一个存储器1220，用于存储计算机程序、程序指令和/或数据。存储器1220和处理器1210耦合。
本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1210可能和存储器1220协同操作。存储器1220保存实施上述任一实施例中必要计算机程序、程序指令和/或数据；处理器1210可能执行存储器1220中存储的计算机程序，完成上述任一实施例中的方法。可选的，至少一个存储器1220中的至少一个可以包括于处理器1210中。
通信装置1200中还可以包括收发器1230，通信装置1200可以通过收发器1230和其它设备进行信息交互。收发器1230可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。
在一种可能的实施方式中，该通信装置1200可以应用于边缘使能功能实体，具体通信装置1200可以是边缘使能功能实体，也可以是能够支持边缘使能功能实体，实现上述涉及的任一实施例中边缘使能功能实体的功能的装置。存储器1220保存实现上述任一实施例中的边缘使能功能实体的功能的必要计算机程序、程序指令和/或数据。处理器1210可执行存储器1220存储的计算机程序，完成上述任一实施例中边缘使能功能实体执行的方法。
在又一种可能的实施方式中，该通信装置1200可以应用于应用功能实体，具体通信装置1200可以是应用功能实体，也可以是能够支持应用功能实体，实现上述涉及的任一实施例中应用功能实体的功能的装置。存储器1220保存实现上述任一实施例中的应用功能实体的功能的必要计算机程序、程序指令和/或数据。处理器1210可执行存储器1220存储的计算机程序，完成上述任一实施例中应用功能实体执行的方法。
本申请实施例中不限定上述收发器1230、处理器1210以及存储器1220之间的具体连接介质。本申请实施例在图12中以存储器1220、处理器1210以及收发器1230之间通过总线连接，总线在图12中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实施或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实施存储功能的装置，用于存储计算机程序、程序指令和/或数据。
基于以上实施例，参见图13，本申请实施例还提供另一种通信装置1300，包括：接口电路1310和处理器1320；接口电路1310，用于接收代码指令并传输至处理器；处理器1320，用于运行代码指令以执行上述任一实施例中边缘使能功能实体执行的方法或者应用功能实体执行的方法。
基于以上实施例，本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有指令，当指令被执行时，使上述任一实施例中边缘使能功能实体执行的方法被实施或者应用功能实体执行的方法被实施。该计算机可读存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
为了实现上述图11～图13的通信装置的功能，本申请实施例还提供一种芯片，包括处理器，用于支持该通信装置实现上述方法实施例中边缘使能功能实体或应用功能实体所涉及的功能。在一种可能的设计中，该芯片与存储器连接或者该芯片包括存储器，该存储器用于保存该通信装置必要的程序指令和数据。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产 品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (39)

  1. 一种应用上下文的迁移方法，其特征在于，所述方法包括：
    接收来自应用功能实体的第一信息，所述第一信息用于指示迁移所述应用功能实体关联的应用上下文；
    当发生所述应用上下文的迁移的触发事件时，根据所述第一信息确定对所述应用上下文进行迁移。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述第一信息，执行如下一项或多项操作：
    检测所述应用上下文的迁移的触发事件；
    发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；
    将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；
    将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；
    将所述应用上下文的迁移的信息发送至核心网网元；
    其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
  3. 如权利要求1或2所述的方法，其特征在于，所述接收来自应用功能实体的第一信息，包括：
    接收来自所述应用功能实体的注册信息，所述注册信息包含所述第一信息。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    接收来自应用功能实体的第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
  5. 如权利要求3所述的方法，其特征在于，所述第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
  6. 如权利要求4或5所述的方法，其特征在于，所述方法还包括：
    接收来自所述应用功能实体的第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述应用功能实体的所述应用上下文。
  8. 如权利要求7所述的方法，其特征在于，在接收来自所述应用功能实体的所述应用上下文之前，所述方法还包括：
    向所述应用功能实体发送所述应用上下文的存储地址。
  9. 如权利要求1-8任一项所述的方法，其特征在于：
    所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
  10. 一种应用上下文的迁移方法，其特征在于，包括：
    向边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文；
    接收来自边缘使能功能实体的响应于所述第一信息发送的响应信息。
  11. 如权利要求10所述的方法，其特征在于，所述第一信息，还用于指示所述边缘使 能功能实体执行如下一项或多项操作：
    检测所述应用上下文的迁移的触发事件；
    发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；
    将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；
    将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；
    将所述应用上下文的迁移的信息发送至核心网网元；
    其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
  12. 如权利要求10或11所述的方法，其特征在于，所述向边缘使能功能实体发送第一信息，包括：
    向所述边缘使能功能实体发送注册信息，所述注册信息包含所述第一信息。
  13. 如权利要求10-12任一项所述的方法，其特征在于，所述方法还包括：
    向所述边缘使能功能实体发送第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
  14. 如权利要求13所述的方法，其特征在于，所述第一条件信息包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息生效的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值、所述应用功能实体过载。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    向所述边缘使能功能实体发送第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
  16. 如权利要求10-15任一项所述的方法，其特征在于，在向边缘使能功能实体发送第一信息之后，所述方法还包括：
    向所述边缘使能功能实体发送所述应用上下文。
  17. 如权利要求16所述的方法，其特征在于，在向所述边缘使能功能实体发送所述应用上下文之前，所述方法还包括：
    接收来自所述边缘使能功能实体的所述应用上下文的存储地址；
    基于所述存储地址，向所述边缘使能实体发送所述应用上下文。
  18. 如权利要求10-17任一项所述的方法，其特征在于：
    所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
  19. 一种应用上下文的迁移装置，其特征在于，所述装置包括：
    通信模块，用于接收来自应用功能实体的第一信息，所述第一信息用于指示迁移所述应用功能实体关联的应用上下文；
    处理模块，用于在发生所述应用上下文的迁移的触发事件时，根据所述第一信息确定对所述应用上下文进行迁移。
  20. 如权利要求19所述的装置，其特征在于，所述处理模块，还用于根据所述第一信息，执行如下一项或多项操作：
    检测所述应用上下文的迁移的触发事件；
    发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；
    将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；
    将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；
    将所述应用上下文的迁移的信息发送至核心网网元；
    其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
  21. 如权利要求19或20所述的装置，其特征在于，所述通信模块，具体用于接收来自所述应用功能实体的注册信息，所述注册信息包含所述第一信息。
  22. 如权利要求19-21任一项所述的装置，其特征在于，所述通信模块，还用于接收来自应用功能实体的第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
  23. 如权利要求21所述的装置，其特征在于，所述第一生效条件包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息所适用的应用客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值，或所述应用功能实体过载。
  24. 如权利要求22或23所述的装置，其特征在于，所述通信模块，还用于接收来自所述应用功能实体的第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
  25. 如权利要求19-24任一项所述的装置，其特征在于，所述通信模块，还用于接收来自所述应用功能实体的所述应用上下文。
  26. 如权利要求25所述的装置，其特征在于，在接收来自所述应用功能实体的所述应用上下文之前，所述通信模块，还用于向所述应用功能实体发送所述应用上下文的存储地址。
  27. 如权利要求19-26任一项所述的装置，其特征在于：所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
  28. 一种应用上下文的迁移装置，其特征在于，包括：
    通信模块，用于向边缘使能功能实体发送第一信息，所述第一信息用于指示迁移应用功能实体关联的应用上下文；
    通信模块，还用于接收来自边缘使能功能实体的响应于所述第一信息发送的响应信息。
  29. 如权利要求28所述的装置，其特征在于，所述第一信息还用于指示所述边缘使能功能实体执行如下一项或多项操作：
    检测所述应用上下文的迁移的触发事件；
    发现目标应用功能实体，所述目标应用功能实体用于接收所述应用上下文；
    将所述应用上下文传输到所述目标应用功能实体关联的边缘使能功能实体；
    将所述目标应用功能实体的信息发送至所述应用功能实体相关的终端设备；
    将所述应用上下文的迁移的信息发送至核心网网元；
    其中，所述应用功能实体对应的应用与所述目标应用功能实体对应的应用相同。
  30. 如权利要求28或29所述的装置，其特征在于，所述通信模块，还用于向所述边缘使能功能实体发送注册信息，所述注册信息包含所述第一信息。
  31. 如权利要求28-30任一项所述的装置，其特征在于，所述通信模块，还用于向所述边缘使能功能实体发送第一条件信息，所述第一条件信息用于指示所述第一信息的第一生效条件。
  32. 如权利要求31所述的装置，其特征在于，所述第一条件信息包括以下任意一项或多项：所述第一信息的生效时长、所述第一信息的生效时段、所述第一信息生效的应用 客户端、所述应用上下文的迁移时长小于预设时间阈值、所述应用上下文的大小小于预设大小阈值、所述应用功能实体过载。
  33. 如权利要求31或32所述的装置，其特征在于，所述通信模块，还用于向所述边缘使能功能实体发送第二条件信息，所述第二条件信息用于指示所述第一信息的第二生效条件，所述第二生效条件不同于所述第一生效条件。
  34. 如权利要求28-33任一项所述的装置，其特征在于，在向边缘使能功能实体发送第一信息之后，所述通信模块，还用于向所述边缘使能功能实体发送所述应用上下文。
  35. 如权利要求34所述的装置，其特征在于，在向所述边缘使能功能实体发送所述应用上下文之前，所述通信模块，还用于接收来自所述边缘使能功能实体的所述应用上下文的存储地址；基于所述存储地址，向所述边缘使能实体发送所述应用上下文。
  36. 如权利要求28-35任一项所述的装置，其特征在于：所述应用上下文包含标识信息，所示标识信息用于唯一标识所述应用上下文。
  37. 一种通信装置，其特征在于，包括：处理器和存储器；
    所述存储器，用于存储计算机程序；
    所述处理器，用于执行所述存储器中存储的计算机程序，以使得如权利要求1至9中任一项所述的方法或者如权利要求10至18中任一项所述的方法被执行。
  38. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器用于运行所述代码指令以使得如权利要求1至9中任一项所述的方法或者如权利要求10至18中任一项所述的方法被执行。
  39. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被执行时，以使得如权利要求1至9中任一项所述的方法或者如权利要求10至18中任一项所述的方法被实现。
PCT/CN2020/119763 2020-09-30 2020-09-30 一种应用上下文的迁移方法及装置 WO2022067830A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP20955850.1A EP4210360A4 (en) 2020-09-30 2020-09-30 METHOD AND DEVICE FOR MIGRING APPLICATION CONTEXT
JP2023519762A JP2023544573A (ja) 2020-09-30 2020-09-30 アプリケーションコンテキスト再配置方法およびアプリケーションコンテキスト再配置装置
CN202080105719.5A CN116325835A (zh) 2020-09-30 2020-09-30 一种应用上下文的迁移方法及装置
CA3194460A CA3194460A1 (en) 2020-09-30 2020-09-30 Application context relocation method and apparatus
AU2020470244A AU2020470244A1 (en) 2020-09-30 2020-09-30 Application context relocation method and apparatus
PCT/CN2020/119763 WO2022067830A1 (zh) 2020-09-30 2020-09-30 一种应用上下文的迁移方法及装置
US18/192,980 US20230239675A1 (en) 2020-09-30 2023-03-30 Application context relocation method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119763 WO2022067830A1 (zh) 2020-09-30 2020-09-30 一种应用上下文的迁移方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/192,980 Continuation US20230239675A1 (en) 2020-09-30 2023-03-30 Application context relocation method and apparatus

Publications (1)

Publication Number Publication Date
WO2022067830A1 true WO2022067830A1 (zh) 2022-04-07

Family

ID=80949479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119763 WO2022067830A1 (zh) 2020-09-30 2020-09-30 一种应用上下文的迁移方法及装置

Country Status (7)

Country Link
US (1) US20230239675A1 (zh)
EP (1) EP4210360A4 (zh)
JP (1) JP2023544573A (zh)
CN (1) CN116325835A (zh)
AU (1) AU2020470244A1 (zh)
CA (1) CA3194460A1 (zh)
WO (1) WO2022067830A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021137579A1 (ko) * 2020-01-03 2021-07-08 삼성전자 주식회사 에지 컴퓨팅 시스템에서 어플리케이션 컨텍스트 재배치 조정 방법 및 장치
CN112491944A (zh) * 2020-09-02 2021-03-12 中兴通讯股份有限公司 边缘应用发现方法及装置、边缘应用服务支持方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018539A (zh) * 2016-01-27 2017-08-04 中兴通讯股份有限公司 应用的移动性的处理方法及装置
CN110167092A (zh) * 2018-02-11 2019-08-23 大唐移动通信设备有限公司 一种业务迁移的方法及装置
US20190387448A1 (en) * 2018-06-18 2019-12-19 Google Llc Fifth Generation New Radio Edge Computing Mobility Management
CN111225348A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种应用实例迁移的方法及多接入边缘计算主机
US20200196203A1 (en) * 2018-12-17 2020-06-18 Verizon Patent And Licensing Inc. Method and system for edge computing handover service

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018539A (zh) * 2016-01-27 2017-08-04 中兴通讯股份有限公司 应用的移动性的处理方法及装置
CN110167092A (zh) * 2018-02-11 2019-08-23 大唐移动通信设备有限公司 一种业务迁移的方法及装置
US20190387448A1 (en) * 2018-06-18 2019-12-19 Google Llc Fifth Generation New Radio Edge Computing Mobility Management
CN111225348A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种应用实例迁移的方法及多接入边缘计算主机
US20200196203A1 (en) * 2018-12-17 2020-06-18 Verizon Patent And Licensing Inc. Method and system for edge computing handover service

Also Published As

Publication number Publication date
EP4210360A4 (en) 2023-11-15
CA3194460A1 (en) 2022-04-07
JP2023544573A (ja) 2023-10-24
CN116325835A (zh) 2023-06-23
US20230239675A1 (en) 2023-07-27
AU2020470244A1 (en) 2023-06-01
EP4210360A1 (en) 2023-07-12

Similar Documents

Publication Publication Date Title
US10523545B2 (en) System and method for managing VoIP session continuity information using logical scalable units
US10630779B2 (en) System and method for using VoIP session continuity information using logical scalable units
US11190602B2 (en) Communication method and communications device
JP5671297B2 (ja) Ｉｍｓネットワークを介してマルチメディア・サービスを最適化するための方法及びシステム
US10146848B2 (en) Systems and methods for autonomous, scalable, and distributed database management
EP3238096B1 (en) System and method for discovering a lan synchronization candidate for a synchronized content management system
CN115039391A (zh) 用于提供边缘计算服务的方法和装置
US20230239675A1 (en) Application context relocation method and apparatus
JP7237195B2 (ja) 通信方法、装置、エンティティ及びコンピュータプログラム
CN111327668B (zh) 网络管理方法、装置、设备和存储介质
CN117561703A (zh) 一种实例化边缘应用服务器的方法和装置
WO2022016558A1 (zh) 一种业务连续性事件的通知方法及装置
EP3065379A1 (en) System and method for volte session continuation using logical scalable units
KR20220047034A (ko) Mec 서비스를 제공하기 위한 방법 및 장치
KR20210044566A (ko) ＷｅｂＲＴＣ를 이용한 다자간 영상통화 제어 시스템 및 방법
WO2023241465A1 (zh) T-ees发现方法及相关装置
WO2023185654A1 (zh) 一种通信方法及装置
CN115412530B (zh) 一种多集群场景下服务的域名解析方法及系统
RU2783809C2 (ru) Способ связи и устройство связи
WO2023246681A1 (zh) 一种通信方法及装置
WO2023185567A1 (zh) 发现应用服务器的方法和装置
US20200112613A1 (en) Method for providing user-centric work space
CN116896558A (zh) 一种通信方法及装置
WO2020034955A1 (zh) 通信方法和通信设备
CN117311924A (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: 20955850

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023519762

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3194460

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2020955850

Country of ref document: EP

Effective date: 20230406

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020470244

Country of ref document: AU

Date of ref document: 20200930

Kind code of ref document: A