A method and apparatus for notifying business continuity events

Abstract

This application provides a method and apparatus for notifying business continuity events, aiming to provide valuable information to the application layer to help trigger application context migration. The method can be applied to an Edge Enabled Server (EES), and includes: receiving a subscription message from a first device, the subscription message requesting subscription to business continuity event notification; and sending a notification message to the first device when the conditions for the business continuity event notification are met. The EES can be a source EES, and the first device can be a source EAS or an EEC. Alternatively, the EES can be a target EES, and the first device can be a target EAS.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for notifying business continuity events. Background Technology

[0002] With the widespread deployment of various cloud computing resources within networks, the same application is often deployed simultaneously across multiple edge data networks. Servers of the same application deployed on different edge data networks can provide the same services and are functionally equivalent. After connecting to the network, a terminal device selects the nearest application instance in the edge data network to execute its services. Due to the mobility of terminal devices, the application instance previously selected by the terminal device may no longer be able to adequately provide services. To meet the service continuity requirements of the application, the network reselects a new application instance in the nearest edge data network for the terminal device to continue its services, thus completing the switch from the source application instance to the target application instance.

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

[0004] How to trigger the migration of the application context is a problem that needs to be solved. Summary of the Invention

[0005] This application provides a method and apparatus for notifying business continuity events, with the aim of providing valuable information to the application layer to help the application layer trigger application context migration.

[0006] Firstly, a method for notifying business continuity events is provided. This method can be applied to an Edge Enabled Server (EES), and includes the following steps: receiving a subscription message from a first device, the subscription message being used to request subscription to business continuity event notifications; and sending a notification message to the first device when the conditions for the business continuity event notification are met. Thus, by subscribing to notifications, the EES can notify the first device of business continuity events, enabling the first device to trigger application context migration based on the EES notification.

[0007] Secondly, a method for notifying business continuity events is provided. This method can be applied to a first device and includes the following steps: sending a subscription message to an Edge Enablement Server (EES), the subscription message being used to request subscription to business continuity event notifications; and receiving a notification message from the EES. Thus, by subscribing to notifications, the first device can receive notifications of business continuity events from the EES, enabling the first device to trigger application context migration based on the EES notification.

[0008] Thirdly, a communication device is provided. This communication device can be an edge-enabled server (EES), a device within an edge-enabled server (EES) (e.g., a chip, a chip system, or a circuit), or a device compatible with an edge-enabled server (EES). In one design, the communication device may include modules corresponding to the methods / operations / steps / actions described in the first aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software. In another design, the communication device may include a processing module and a communication module. The processing module is used to invoke the communication module to perform receiving and / or sending functions. The communication module may further include a receiving module and a sending module.

[0009] For example: a receiving module is configured to receive a subscription message from a first device, the subscription message being used to request subscription to a business continuity event notification; a sending module is configured to send a notification message to the first device when the conditions for the business continuity event notification are met.

[0010] Fourthly, a communication device is provided. This communication device can be a first device, a component within the first device (e.g., a chip, a chip system, or a circuit), or a device compatible with the first device. In one design, the communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software. In another design, the communication device may include a processing module and a communication module. The processing module is used to invoke the communication module to perform receiving and / or sending functions. The communication module may further include a receiving module and a sending module.

[0011] For example: a sending module is configured to send a subscription message to the Edge Enablement Server (EES), the subscription message being used to request subscription to business continuity event notifications; a receiving module is configured to receive notification messages from the EES. Thus, by subscribing to notifications, the first device can receive business continuity event notifications from the EES, enabling the first device to trigger application context migration based on the EES notifications.

[0012] In conjunction with any one of the first, second, third, or fourth aspects, this application provides several possible designs, as detailed below.

[0013] In one possible design, the EES is the source EES, and the first device is an edge-enabled client (EEC). The EEC subscribes to service continuity events from the source EES, which provides information for determining the application context to trigger the connection. It can also obtain the target EAS for triggering the connection or switch application data to the target EAS, thus reducing the implementation and processing logic of the EEC.

[0014] In one possible design, the EES is the source EES, and the first device is the source EAS. The source EAS subscribes to service continuity events from the source EES, which provides information for determining the application context to trigger the connection. It can also obtain the target EAS for triggering the connection or switch application data to the target EAS, thus reducing the implementation and processing logic of the source EAS.

[0015] In one possible design, the EES is the target EES, and the first device is the target EAS. By subscribing to service continuity events from the target EES through the target EAS, the target EAS can obtain the context for proactively receiving pushed content or proactively requesting the application context of the terminal device from the source EAS. This reduces the implementation and processing logic of the target EAS.

[0016] In one possible design, the notification message includes an event type that indicates the type of event that triggered the business continuity event notification.

[0017] In one possible design, the EES is the source EES; the event types include any one or more of the following: the terminal device moves across the edge data network (EDN); load; application context transfer; application migration; the terminal device's address changes.

[0018] In one possible design, the EES is the source EES; the event types include any one or more of the following: the terminal device moves across the edge data network (EDN); load; application context transfer; application migration; the terminal device's address changes.

[0019] In one possible design, the EES is a source EES, and the first device is a source EAS; the event type also includes any one or more of the following: service recovery; service interruption; application context recovery.

[0020] In one possible design, the EES is the source EES, and the first device is the edge-enabled client EEC; the event type also includes: the address of the edge application server EAS serving the terminal device corresponding to the EEC changes.

[0021] In one possible design, the EES is the target EES, and the first network element is the target EAS; the event type includes any one or more of the following: the terminal device moves across the edge data network (EDN); service recovery; service interruption; application context transfer; application context migration; the address of the terminal device changes.

[0022] In one possible design, the EES is the target EES, the first device is the target EAS, and the notification message includes one or more of the following: information about the source EAS; the identifier of the terminal device; and the address for obtaining the application context.

[0023] In one possible design, the subscription message includes the conditions for the business continuity event notification, or the conditions for the business continuity event notification are set by the EES.

[0024] In one possible design, the subscription message contains at least one of the identifiers of the terminal device or the application.

[0025] In addition to the first aspect, besides the possible designs provided above, some other possible designs can be provided, as detailed below.

[0026] In one possible design, the EES is a source EES; when the source EES determines any one or more of the following, it sends a notification message to the first device: the terminal device's location moves out of the service area of ​​the source EDN or source EAS; the terminal device's Data Network Access Identifier (DNAI) changes, and the location of the terminal device is determined to have moved out of the service area of ​​the source EDN or source EAS based on the changed DNAI; a message requesting the transfer of application context is received from the first device; a message requesting the migration of application context is received from the first device; the source EAS transfers context to the target EAS; a message requesting the migration of context is received from the target EES; a message requesting the transfer of context is received from the target EES; the source EAS is overloaded or the source EDN is determined to be overloaded; the source EES initiates an application context migration.

[0027] In one possible design, the EES is the source EES, the first network element is the EEC, and the step of sending a notification message to the first device when the conditions for the service continuity event notification are met includes: when the source EES determines any one or more of the following, it sends a notification message to the first device: the target EAS has a different address from the source EAS; the source EAS begins to transmit application context to the target EAS; the application context transmission is completed; the source EAS requests to switch the network user plane path of the terminal device; the source EES requests to switch the network user plane path of the terminal device.

[0028] In one possible design, the EES is the source EES, and the first network element is the source EES. When the source EES determines that the terminal device is roaming, it sends a notification message to the first device.

[0029] In one possible design, the source EES determines that the terminal device is roaming by obtaining indication information from the AMF or SMF, which is used to indicate that the terminal device is roaming.

[0030] In one possible design, the EES is the target EES, and the first device is the target EAS; when the source EES receives any one or more of the following, it sends a notification message to the first device: an EAS discovery request message from the source EES; a message requesting the transfer of application context; a message requesting the migration of application context; signaling or data packets containing application context.

[0031] In addition, in conjunction with the third aspect, besides the possible designs provided above, some other possible designs can be provided, as detailed below.

[0032] In one possible design, the device is a source EES; the processing module is specifically configured to, upon determining any one or more of the following, send a notification message to the first device via the sending module: the terminal device's location moves out of the service area of ​​the source EDN or source EAS; the terminal device's Data Network Access Identifier (DNAI) changes, and the location of the terminal device is determined to have moved out of the service area of ​​the source EDN or source EAS based on the changed DNAI; a message requesting the transfer of application context is received from the first device; a message requesting the migration of application context is received from the first device; the source EAS transfers context to the target EAS; a message requesting the migration of context is received from the target EES; a message requesting the transfer of context is received from the target EES; the source EAS is overloaded or the source EDN is determined to be overloaded; the source EES initiates an application context migration.

[0033] In one possible design, the device is a source EES, the first network element is an EEC, and the processing module is specifically used to send a notification message to the first device through the sending module when any one or more of the following are determined: the address of the target EAS is different from that of the source EAS; the source EAS begins to transmit application context to the target EAS; the application context transmission is completed; the source EAS requests to switch the network user plane path of the terminal device; the source EES requests to switch the network user plane path of the terminal device.

[0034] In one possible design, the device is a source EES, and the first network element is a source EAS. When the source EES determines that the terminal device is roaming, it sends a notification message to the first device.

[0035] In one possible design, the processing module is further configured to: obtain indication information from the AMF or SMF, the indication information being used to indicate that the terminal device is roaming.

[0036] In one possible design, the device is a target EES, and the first device is a target EAS; the processing module is specifically used to send a notification message to the first device through the sending module when any one or more of the following are determined: an EAS discovery request message from the source EES; a message requesting the transfer of application context; a message requesting the migration of application context; signaling or data packets containing application context.

[0037] Fifthly, a communication device is provided, comprising a communication interface and a processor. The communication interface is used for communication between the communication device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface, and the other devices may be network devices or other terminals. The processor is used to invoke a set of programs, instructions, or data to execute the method described in the first aspect. The communication device may further include a memory for storing programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the method described in the first aspect.

[0038] Sixthly, a communication device is provided, comprising a communication interface and a processor. The communication interface is used for communication between the communication device and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface, and the other devices may be network devices or other terminals. The processor is used to invoke a set of programs, instructions, or data to execute the method described in the second aspect above. The communication device may further include a memory for storing programs, instructions, or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, it can implement the method described in the second aspect above.

[0039] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the method described in the first aspect to be performed.

[0040] Eighthly, this application also provides a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the method described in the second aspect to be performed.

[0041] Ninthly, embodiments of this application provide a chip system including a processor and potentially a memory for implementing the methods described in the first aspect. The chip system may be composed of chips or may include chips and other discrete devices.

[0042] In a tenth aspect, embodiments of this application provide a chip system including a processor and potentially a memory, for implementing the method described in the second aspect above. The chip system may be composed of chips or may include chips and other discrete devices.

[0043] Eleventhly, embodiments of this application provide a communication system comprising the apparatus as described in the third aspect and the apparatus as described in the fourth aspect. Alternatively, the communication system comprises the apparatus as described in the fifth aspect and the apparatus as described in the sixth aspect.

[0044] In a twelfth aspect, a computer program product containing instructions is provided that, when run on a computer, causes the method described in the first aspect above to be executed.

[0045] In a thirteenth aspect, a computer program product containing instructions is provided that, when run on a computer, causes the method described in the second aspect above to be executed. Attached Figure Description

[0046] Figure 1 This is a schematic diagram of the communication system architecture in an embodiment of this application;

[0047] Figure 2 This is one of the flowcharts illustrating the notification method for business continuity events in this application.

[0048] Figure 3 This is a second flowchart illustrating the notification method for business continuity events in this application.

[0049] Figure 4 This is the third flowchart illustrating the notification method for business continuity events in this application.

[0050] Figure 5 This is the fourth flowchart illustrating the notification method for business continuity events in this application.

[0051] Figure 6 This is a schematic diagram illustrating the operation process of the target EAS after receiving a notification message from the target EES in an embodiment of this application.

[0052] Figure 7 This is one of the flowcharts illustrating the application of the context transition method in the embodiments of this application;

[0053] Figure 8 This is the second flowchart illustrating the application of the context transition method in the embodiments of this application;

[0054] Figure 9 This is the third flowchart illustrating the application of the context transition method in this application embodiment;

[0055] Figure 10 This is the fourth flowchart illustrating the notification method for business continuity events in this application.

[0056] Figure 11 This is one of the schematic diagrams of the communication device structure in the embodiments of this application;

[0057] Figure 12 This is the second schematic diagram of the communication device structure in the embodiments of this application. Detailed Implementation

[0058] This application provides a method and apparatus for notifying business continuity events. The method and apparatus are based on the same inventive concept. Since the methods and apparatus solve problems based on similar principles, their implementations can be mutually referenced, and repeated details will not be elaborated further. In the description of this application's embodiments, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "At least one" in this application refers to one or more; "multiple" refers to two or more. Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order.

[0059] The business continuity event notification method provided in this application embodiment can be applied to fourth-generation (4G) communication systems, fifth-generation (5G) communication systems, or various future communication systems.

[0060] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0061] Figure 1 This illustration shows a possible communication system architecture to which the notification method for business continuity events provided in this application is applicable. (See also...) Figure 1 As shown, the communication system may include terminal devices, a 3GPP network, and an edge data network (EDN). The terminal devices may include application clients (AC) and edge enabler clients (EEC). The EDN may include edge application servers (EAS) and edge enabler servers (EES). The communication system may also include an edge configuration server (ECS).

[0062] A communication system may include one or more devices. It may also include one or more EDNs.

[0063] The functions of each device or module in the communication system are described below.

[0064] Terminal equipment, also known as user equipment (UE), mobile station (MS), or mobile terminal (MT), is a device that provides voice or data connectivity to users, and can also be an Internet of Things (IoT) device. Examples of terminal equipment include handheld devices with wireless connectivity and in-vehicle devices. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Furthermore, a terminal device can also be a chip.

[0065] EDN: A common understanding is that an EDN corresponds to only one data network, a special local data network (localDN) that includes edge-enabled functions. It can be identified using DNAI and DNN, and is a network logical concept. Another understanding of EDN is that it is a peer concept of the central cloud, which can be understood as a local data center. "Local" can be a geographical concept. EDN can be identified using DNAI and can contain multiple local data networks (localDNs).

[0066] Application Client (AC): This is the peer entity of EAS on the terminal device side. The AC is used by application users to obtain application services from the application server. An application client is a client program on the terminal side. It can connect to application servers in the cloud to obtain application services, or it can connect to EAS deployed and running in one or more EDNs to obtain application services.

[0067] EAS: Also known as application instance, edge application, edge application server, edge application instance, MEC application, MEC application server, EAS function, etc. In this application's embodiments, it is uniformly referred to as EAS. Specifically, EAS refers to a server application, such as a social media software, augmented reality (AR), or virtual reality (VR) instance deployed on an EDN. An application can deploy EAS in one or more EDNs. EAS deployed in different EDNs can be considered different EASs of the same application; they can share a domain name, use an internet protocol (IP) address, or use different IP addresses.

[0068] EES (Enterprise Edge Provider): Provides enabling or supporting capabilities for application instances deployed in EDN, better supporting application deployment in EDN. It supports edge application registration, UE authentication and authorization, and provides UEs with application instance IP address information. It can also further support obtaining application instance identifiers and IP address information and sending this information to the edge data network configuration server. EES is deployed in EDN. Generally, an EAS (Enterprise Application Server) registers with an EES, or an EAS's information is configured on an EES through the management system. This EES can be called the EES associated with that EAS. The EES controls (or manages) the EAS registered (or configured) on that EES. Application instances registered on an EES generally refer to those that have been instantiated but have not yet started providing services to clients; or application instances configured on an EES by the management system, generally with application installation packages configured on the EES but not yet instantiated; or application instances running on the EES, generally already providing services to clients; it can also include application instances that have not yet been deployed but can be deployed on the EES.

[0069] EEC: This is the peer entity of EES on the terminal device side. EEC is used to register EEC information and application client information with EES, perform security authentication and authorization, obtain EAS IP address from EES, and provide edge computing enabling capabilities to application clients, such as the EAS discovery service returning the EAS address, such as IP address or URL, to the application client.

[0070] ECS: Responsible for EDN configuration, such as providing EES information to end devices. It can also directly provide application instance information to end devices, and interact with DNS to obtain application instance information. Furthermore, it can obtain and store application instance and IP address information from other functional entities.

[0071] In this process, application users sign service agreements with application providers to obtain services. Application users communicate with the EAS (Edge Enablement System) by logging into the application client on their terminal device. The enabling client (e.g., EEC) is a middleware layer, typically located within the operating system or between the application client and the operating system. The application client can obtain edge enabling services from the enabling client via an application programming interface (API).

[0072] It should be noted that in the embodiments of this application, the various devices or functional modules can communicate with each other through interfaces or interact using service-oriented interfaces. Figure 1 Examples of interface names between various devices or functional modules are provided. However, these interface names are merely examples and can be replaced with other names; this application does not limit the specific names used.

[0073] The various devices or functional modules included in the communication system may also be referred to by other names. Optionally, the functional modules in the embodiments of this application may be implemented by one device, or by multiple devices, or by one or more functional modules within a single device. The embodiments of this application do not specifically limit this. It is understood that the various functions involved in the embodiments of this application may be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0074] It should be noted that the embodiments of this application do not limit the distribution of each functional module or each device. Optionally, each functional module may also include other functional entities formed by the fusion of any of the above-mentioned functional modules.

[0075] An application can be deployed across multiple edge data networks, providing seamless services to clients. Due to the mobile nature of terminal devices, the server-side (EAS) providing application services to clients on those devices may change, moving from one EAS in one edge data network to another EAS for the same application within the same edge data network, or vice versa. This involves migrating (or switching) the terminal's application services between EES and EAS in different edge data networks. This situation, where the application server providing services to an application on a terminal device changes from one EAS to another, can be termed application migration. In this application, application migration can be further understood as the migration of the application's context during the migration process; or, equivalently, application migration can also be understood as the migration of the application's context.

[0076] In this embodiment, application context migration can be the migration of the application context corresponding to the application client on the terminal device from the source EAS to the target EAS. This application context migration satisfies the application's business continuity requirements.

[0077] In this embodiment, the edge data network where the terminal device's application originally resided is referred to as the source edge data network, and the new edge data network to which the terminal device's application switches is referred to as the target edge data network. The EAS running the application in the source edge data network is called the source EAS, and the EES associated with the source EAS is called the source EES.

[0078] Application instances typically run on virtual machines in a data center. The source EAS and the source edge enabler server may be located in the same physical data center, on the same physical device, or on different physical devices. Similarly, the EAS in the target edge data network capable of running the application is called the target EAS, and the EES associated with the target EAS is called the target EES. Alternatively, the target EAS is the EAS that receives (or accepts) the application that needs to be migrated. The target EAS and the target edge enabler server may be located in the same physical data center, on the same physical device, or on different physical devices.

[0079] In this embodiment, the EAS provides services to application users who have signed service agreements with application providers. Application users communicate with the EAS by logging into the application client on their terminal devices. The EEC (Edge Enabler) typically resides within the operating system or is located between the application client and the operating system. The application client can obtain edge enabling services from the enabling client via an application programming interface (API), and the EAS can obtain edge enabling services from the enabling server via an API.

[0080] When a terminal device moves from a source edge data network to a target edge data network, the source EAS serving the current application user may no longer be the optimal server providing services. The quality of services obtained by the user from that source EAS may degrade; for example, the user plane path to access application services may not be optimal, causing latency or interruption of application services. To reduce application service latency and ensure application service continuity, application context migration is required. Application context migration can also be understood as EAS redirection or EAS switching. Therefore, the application context of the terminal device needs to be synchronously migrated from the source EAS to the target EAS. The migration of the terminal device's application context can be achieved with the assistance of both the source EES and the target EES. This application's embodiments will illustrate how to achieve the migration of the terminal device's application context with the assistance of the source EES and / or the target EES.

[0081] like Figure 2 As shown, the specific process of the business continuity event notification method provided in this application is as follows.

[0082] This method can be applied to EES.

[0083] S201, The first device sends a subscription message to the EES, and the EES receives the subscription message from the first device.

[0084] Subscription messages are used to request subscription to business continuity event notifications. This subscription message can be called a service continuity event subscribe request message or a service continuity subscribe request message.

[0085] Business continuity events can also be understood as application context migration events or events related to application context migration. Therefore, this subscription message can also be understood as a request to subscribe to application context migration event notifications.

[0086] S202, EES saves the subscription information in the subscription message.

[0087] This step is optional, and the subscription information can be the information or parameters carried in the subscription message. Specifically, the EES stores the identifier of the first device and the information or parameters carried in the subscription message.

[0088] S203. When the conditions for business continuity event notification are met, EES sends a notification message to the first device, and the first device receives the notification message from EES.

[0089] This notification message can be called a service continuity event subscribe response message or a service continuity event subscribe response message. This message is used to indicate whether the subscription request from the first device is accepted or rejected. When the EES accepts the subscription request, this subscription response indicates a successful subscription. When the EES rejects the subscription request, this response indicates a rejection of the subscription or a subscription failure.

[0090] In this way, by subscribing to notifications, EES can notify the first device of business continuity events, so that the first device can trigger the migration of the application context based on the notification from EES.

[0091] The following provides supplementary descriptions of optional implementation methods for the notification method of business continuity events in the embodiments of this application.

[0092] The first device can obtain business continuity events from EES via an API. Specifically, EES provides a service API for business continuity events, and the operations of this service API include... Figure 2 The subscription in this embodiment may also include at least one operation of subscription update or subscription cancellation. Step S201 can be understood as the first device calling the EES API.

[0093] Optionally, the conditions for business continuity event notifications can be set by EES or obtained from subscription messages. The conditions for business continuity event notifications can also be called business continuity event notification filters, used to indicate the expectation of receiving business continuity event notifications that match the conditions or filters. In other words, it can be understood as expecting to receive a business continuity event notification message when the event (or information) indicated by the condition or filter occurs.

[0094] The subscription message may also include an identifier for the terminal device, indicating that the subscription message is used to request business continuity event notifications for that terminal device. The subscription message may also include an identifier for the application or service, indicating that the subscription message is used to request business continuity event notifications for that application or service. The application identifier can be an EAS identifier (ID), an FQDN, an AC ID, or a combination of EAS ID, FQDN, and AC ID.

[0095] Of course, the subscription message can include the identifier of the terminal device and the identifier of the application. This indicates that the subscription message is used to request business continuity event notifications for the application on that terminal device.

[0096] It is understandable that this subscription message can also request subscriptions for business continuity event notifications at other granularities.

[0097] When the subscription message includes conditions for the business continuity event notification, those conditions may include the identifier of the terminal device and / or the identifier of the application. That is, the identifier of the terminal device and / or the identifier of the application can be included as part of the conditions for the business continuity event notification in the subscription message.

[0098] The subscription message may also include an event type. This event type indicates the type of event that triggers the business continuity event notification. When the subscription message includes conditions for the business continuity event notification, those conditions may include an event type, indicating an expectation to receive business continuity event notifications related to that event type. This can also be understood as expecting to receive a business continuity event notification message when the event indicated by the event type occurs.

[0099] In S203, when the conditions for a business continuity event notification are related to one or more event types, the notification message may also include the relevant event types.

[0100] Event type can also be called cause value.

[0101] The following section discusses the specific types of the first device and the EES. Figure 2 The examples provide further scenario extensions.

[0102] like Figure 3 As shown, EES is the source EES, and the relevant introduction to the source EES has been described above.

[0103] The first device could be an EEC.

[0104] S301, EEC sends a subscription message to EES, and the source EES receives the subscription message from EEC.

[0105] Subscription messages are used to request subscription to business continuity event notifications. For a detailed description of subscription messages, please refer to step S201; further details will not be provided here.

[0106] S302, Source EES stores subscription information.

[0107] This step is optional. The subscription information can be the information or parameters carried in the subscription message. For a detailed description of how the source EES saves the subscription information, please refer to step S202, which will not be repeated here.

[0108] S303. When the conditions for business continuity event notification are met, the source EES sends a notification message to the EEC, and the EEC receives the notification message from the source EES.

[0109] like Figure 4 As shown, EES is the source EES, and the relevant introduction to the source EES has been described above.

[0110] The first device can be the source EAS. The relevant introduction to the source EAS has been described above and will not be repeated here.

[0111] S401, Source EAS sends a subscription message to Source EES, and Source EES receives the subscription message from Source EAS.

[0112] Subscription messages are used to request subscription to business continuity event notifications. For a detailed description of subscription messages, please refer to step S201; further details will not be provided here.

[0113] S402, Source EES stores subscription information.

[0114] This step is optional. The subscription information can be the information or parameters carried in the subscription message. For a detailed description of how the source EES saves the subscription information, please refer to step S202, which will not be repeated here.

[0115] S403. When the conditions for business continuity event notification are met, the source EES sends a notification message to the source EAS, and the source EAS receives the notification message from the source EES.

[0116] like Figure 5 As shown, EES is the target EES, and the relevant introduction to the target EES has been described above.

[0117] The first device can be the target EAS. The relevant introduction of the target EAS has been described above and will not be repeated here.

[0118] S501, the target EAS sends a subscription message to the target EES, and the target EES receives the subscription message from the target EAS.

[0119] Subscription messages are used to request subscription to business continuity event notifications. For a detailed description of subscription messages, please refer to step S201; further details will not be provided here.

[0120] S502, the target EES stores subscription information.

[0121] This step is optional. The subscription information can be the information or parameters carried in the subscription message. For a detailed description of how the source EES saves the subscription information, please refer to step S202, which will not be repeated here.

[0122] S503. When the conditions for business continuity event notification are met, the target EES sends a notification message to the target EAS, and the target EAS receives the notification message from the target EES.

[0123] The following are Figures 3-5 The optional implementation methods of the embodiments are further described.

[0124] based on Figure 3 In this embodiment, the event type may include any one or more of the following:

[0125] Terminal device mobility; terminal device movement across EDN; prediction of terminal device movement across EDN; load; application context transfer; application context migration; change of terminal device address; service recovery; service interruption; application context recovery.

[0126] Application context transfer can include one or more of the following: application context push, application context fetch, or application context transfer completion. Application context migration is also called application migration. Application context migration can include application context migration start and / or application context migration completion. Load can include application migration start and / or application migration completion.

[0127] Before sending a notification message to the EEC, the source EES (Enterprise Service Provider) in S303 needs to determine whether an event satisfying the business continuity event notification conditions (hereinafter referred to as notification conditions) has occurred or whether information regarding the notification conditions has been detected. Satisfying the notification conditions can be equivalently understood as meeting the notification conditions or matching the notification conditions. Specifically, the source EES can send a notification message to the EEC when it detects or determines any one or more of the following 1) to 14), which can also be understood as the source EES determining that the notification conditions are met when it detects or determines any one or more of the following 1) to 14). The source EES can determine that the current source EAS cannot provide the terminal device with the service that meets the business request, or determine that the terminal device's service has been downgraded or interrupted, when it detects or determines any one or more of the following 1) to 14). The source EES can determine that the terminal device needs to connect to the target EAS, or determine that the terminal device needs to switch its application layer data connection to the target EAS, when it detects or determines any one or more of the following 1) to 14). The source EES can determine that the terminal device needs to perform application context migration, or determine that one or more applications on the terminal device need to perform application context migration, when it detects or determines any one or more of the following 1) to 14).

[0128] 1) The location of the terminal device moves out of the service area of ​​the source EDN or source EAS, which can also be understood as the location of the terminal device moving out of the best service area of ​​the source EDN or source EAS.

[0129] 2) If the Data Network Access Identifier (DNAI) of a terminal device changes, the location of the terminal device is determined based on the changed DNAI, and the device moves out of the service area of ​​the source EDN or source EAS. This can also be understood as determining the location of the terminal device based on the changed DNAI, moving it out of the optimal service area of ​​the source EDN or source EAS. Alternatively, the current DNAI may not belong to a set of DNAIs associated with the source EES (a set of DNAIs associated with the source EES can be understood as a set of DNAIs associated with the EDN where the source EES is located).

[0130] 3) Receive a message from the first device requesting the transfer of application context, such as an application context transfer / deliver request.

[0131] 4) Receive a message from the first device requesting the migration of the application context, such as an application context relocation request;

[0132] 5) The source EAS transmits the context to the target EAS;

[0133] 6) Receive the target EES request to migrate the context, for example, the message could be an application context relocation request;

[0134] 7) Receive a message from the target EES requesting a transfer context. The message name can be "application context transfer / deliver / retrieve request." The purpose of the message is to request the application context of the terminal device. For example, the target EES requests the source EES to obtain the context of the source EES, and then the target EES requests the application context of the terminal device of the source EES from the source EES, and the source EES requests the application context of the terminal device from the source EES.

[0135] 8) Source EAS overload or source EDN overload confirmed;

[0136] 9) Source EES initiates application context migration.

[0137] 10) The address of the target EAS that will provide services to the terminal device is different from that of the source EAS (or it can be understood that the address of the EAS serving the UE application has changed).

[0138] 11) The source EAS begins transferring the application context to the target EAS;

[0139] 12) Application context transfer complete;

[0140] 13) The source EAS requests the network user plane path (UP path) of the switching terminal device;

[0141] 14) The source EES requests to switch the network user plane path of the terminal device.

[0142] In S303, the notification message may also include a specific event category. The event category can be a cause value or cause code, used to indicate the event or cause that triggered (or caused) the business continuity event notification message. The event category or cause value can be a set of enumerated values, such as a set of string enumerated values ​​or a set of numeric enumerated values.

[0143] For example, when the source EES determines or detects 1) or 2) above, it can carry the event type (or cause value) in the notification message as: terminal device mobility; terminal device has made a cross-EDN (inter-EDN) move; or it is predicted that the terminal device will send a cross-EDN move.

[0144] When the source EES determines or detects the above 3), 4), 5), 10), or 12), the cause value can be carried in the notification message as: the source EES triggers application context migration.

[0145] When the source EES determines or detects 6) or 7) above, it can carry the event type (or cause value) as: Target EES requests application context in the notification message.

[0146] When the source EES determines or detects the above 8), the event type (or cause value) can be carried in the notification message as: source EES overload.

[0147] When the source EES determines or detects the above 10), it can carry the event type (or cause value) as: Service (serving) EAS information has changed in the notification message.

[0148] When the source EES determines or detects the above 13), it can include the event type (or cause value) as: User plane path switching in the notification message.

[0149] The notification message in S303 may also include: information about the target EAS, the IP address or URL of the target EAS.

[0150] After receiving the notification message from the source EES, the EEC can perform the following operations:

[0151] (1) Request information about the target EAS from the source EES. For example, if the notification message carries the reason value as: terminal device mobility, terminal device moving across EDN, prediction that the terminal device will send a cross-EDN move, or source EAS overload, etc.; or (2) the EEC initiates a configuration request to the ECS to obtain a new EES and obtains the target EAS information from the new EES; or (3) the EEC directly initiates an application instance discovery request to the target EES that has already been obtained (obtained before receiving the notification message) to obtain the target EAS information. Further, the application context migration process can be executed.

[0152] If the EEC has already obtained information about the target EAS, the EEC can also perform the following operations: establish a connection with the target EAS, including establishing a new socket connection with the AC. Alternatively, the EEC can send information about the target EAS to the AC, triggering the AC to establish an application layer connection with the target EAS. Or, the EEC can notify the AC that the application context transmission is complete, triggering the AC to switch the uplink application data to the target EAS.

[0153] based on Figure 4 In this embodiment, the event type may include any one or more of the following: terminal device mobility; terminal device moving across EDN; prediction that the terminal device will send a cross-EDN move; load; application context transfer; application context migration; change of terminal device address; change of EAS address of the terminal device corresponding to the serving EEC.

[0154] Application context transfer can include one or more of the following: application context push, application context fetch, or application context transfer completion. Application context migration is also called application migration. Application context migration can include application context migration start and / or application context migration completion. Load can include application migration start and / or application migration completion.

[0155] Before sending a notification message to the source EAS, the source EES (Entity Executor System) in S403 needs to determine whether an event satisfying the service continuity event notification conditions (hereinafter referred to as notification conditions) has occurred or whether information meeting the notification conditions has been detected. Satisfying the notification conditions can be equivalently understood as meeting the notification conditions or matching the notification conditions. Specifically, the source EES can send a notification message to the source EAS when it detects or determines any one or more of the above 1) to 9), or it can be understood that the source EES can determine that the notification conditions are met when it detects or determines any one or more of the above 1) to 9). Optionally, the source EES can also send a notification message to the source EAS when it detects or determines that a terminal device is roaming. This can also be understood as the source EES determining that the notification conditions are met when it detects or determines that a terminal device is roaming.

[0156] When the source EES detects or determines any one or more of the above 1) to 9), or when it determines that the terminal device is roaming, it determines that the current source EAS cannot provide services that meet the service requests of the terminal device, or determines that the terminal device's services are downgraded or interrupted. When the source EES detects or determines any one or more of the above 1) to 9), or when it determines that the terminal device is roaming, it determines that the terminal device needs to connect to the target EAS. When the source EES detects or determines any one or more of the above 1) to 9), or when it determines that the terminal device is roaming, it determines that the terminal device needs to perform application context migration, or determines that one or more applications on the terminal device need to perform application context migration (which can also be understood as the EAS serving the terminal device's application corresponding to the S-EAS needing to be changed). When the source EES detects or determines any one or more of the above 1) to 9), or when it determines that the terminal device is roaming, it determines that the S-EAS needs to transfer or migrate the terminal device's application context.

[0157] In S403, this notification message is used to indicate the occurrence of a business continuity event. The notification message may also include a specific event type, which can be a cause value (or cause code). For a detailed description of the event type and cause value, please refer to the description in the preceding embodiments; it will not be repeated here.

[0158] When the source EES determines or detects the above 1), 2), or when the terminal device is roaming, or when the UE's IP address changes, it can include the following cause value in the notification message: terminal device mobility; terminal device moving across EDN; or prediction that the terminal device will send a cross-EDN move.

[0159] When the source EES determines or detects the above 3) or 4), the cause value can be carried in the notification message as: the terminal device (e.g., EEC) triggers application context migration.

[0160] When the source EES determines or detects 6) or 7) above, it can include the cause value as: Target EES requests application context in the notification message.

[0161] When the source EES determines or detects the above 8), the cause value can be carried in the notification message as: source EES overload or source EDN overload.

[0162] When the source EES determines or detects the above 2), the cause value can be carried in the notification message as: User plane path switching.

[0163] The notification message in S403 may also include: information about the target EAS, the IP address or URL of the target EAS.

[0164] After receiving a notification message from the source EES, the source EAS can perform any of the following operations:

[0165] (1) Request information about the target EAS from the source EES. Further steps can be taken to perform the application context migration process.

[0166] (2) Initiate an application context migration request to the source EES, requesting the EES to find the target EES and assist in the transfer of the terminal application context.

[0167] (3) Initiate an application context transfer request to the source EES to request the application context of the source EES auxiliary transmission terminal.

[0168] (4) Send application context data to the source EES.

[0169] (5) Notify the AC of the address of the target application instance.

[0170] (6) Send application context data to the target EAS.

[0171] based on Figure 5 In this embodiment, the event type may include any one or more of the following: a terminal device moves across EDNs; service recovery; service interruption; application context transfer; application context migration; a change in the terminal device's address. Application context transfer may include one or more of application context push, application context pull, or application context transfer completion. Application context migration is also referred to as application migration. Application context migration may include application context migration start and / or application context migration completion.

[0172] Before sending a notification message to the target EAS in S503, the target EES needs to determine whether the event satisfying the service continuity event notification conditions (hereinafter referred to as notification conditions) has occurred or whether the notification condition information has been detected. Satisfying the notification conditions can be equivalently understood as matching the notification conditions. Specifically, the target EES can send a notification message to the target EAS upon receiving any one or more of the information in sections 1-4 below. This can also be understood as the target EES confirming that the notification conditions are met upon receiving any one or more of the information in sections 1-4 below. The target EES can determine, upon receiving any one or more of the information in sections 1-4 below, that the current source EAS cannot provide the terminal device with the service requested by the terminal device, or that the terminal device's service has been downgraded or interrupted. The target EES can determine, upon receiving any one or more of the information in sections 1-4 below, that the terminal device needs to switch to the target EAS. The target EES can determine, upon receiving any one or more of the information in sections 1-4 below, that a terminal device's application context has been migrated to the T-EAS. The target EES can determine, upon receiving any one or more of the information in sections 1-4 below, that a terminal device's application context has been transmitted to the T-EAS.

[0173] The information received by the target EES may include:

[0174] 1. EAS discovery request message from the source EES;

[0175] 2. Request the transmission of application context;

[0176] 3. A message requesting the migration of the application context;

[0177] 4. Signaling or data packets containing application context.

[0178] The message in which the target EES receives a request to transfer application context may include: (1) the target EES receiving a context transfer request from a terminal containing a terminal identifier (UE identifier, EEC identifier, or AC identifier) ​​and at least one parameter of T-EAS, S-EES, or S-EAS; or the target EES receiving a context transfer request from a source EES. The context transfer request may be an application context transfer / deliver request; or (2) the target EES receiving a context transfer request from a source EES, which may carry the address of the target EES and optionally also carry the identifier of the terminal device.

[0179] The target EES receiving a message requesting relocation of the application context may include: (1) the target EES receiving an application context relocation request sent by the source EES; or (2) the target EES receiving a context relocation request sent by the terminal device containing a terminal identifier (UE identifier, EEC identifier, or AC identifier) ​​and at least one parameter of T-EAS, S-EES, and S-EAS, wherein the context relocation request may be an application context relocation request. Or (3) the target EES receiving a context transmission request sent by the terminal device containing a terminal identifier (UE identifier, EEC identifier, or AC identifier) ​​and at least one parameter of T-EAS, S-EES, and S-EAS, wherein the context transmission request may be an application context recovery request or an application context synchronization request.

[0180] The notification message in S503 may include information about the source EAS, such as the address of the source EAS, or the addresses of both the source EAS and the source EES. The notification message in S503 may also include the identifier of the terminal device. The notification message in S503 may also include the address for obtaining the application context.

[0181] In S503, this notification message is used to indicate the occurrence of a business continuity event. The notification message may also include a specific event type, which can be a cause value or cause code.

[0182] When the target EES identifies or detects 2, 3, or 4 above, it can include the reason value "Terminal device initiates application context migration" in the notification message.

[0183] When the target EES identifies or detects 1 or 4 above, it can include the following reason value in the notification message: the target EES or the target EES pushes the application context of the terminal device, or there is an application context that needs to be received.

[0184] When the target EES determines or detects any of the above 1, 2, 3 or 4, it can include the reason value "The serving EES information has changed" in the notification message.

[0185] The notification message in S503 may also include: information about the source EAS (e.g., the IP address or URL of the source EAS), and the new IP address of the terminal device. The notification message may also carry information for obtaining user context (e.g., URL, IP address, and / or port number), which may originate from the target EES (the information is generated by the target EES, in which case the application context transmission path is source EAS to source EES to target EES and back to target EAS), or from the source EAS (the information is generated by the target EES, in which case the application context transmission path is source EAS to target EAS, without passing through source EES and target EES). The notification message also includes information about the source EAS and the terminal device.

[0186] After receiving the notification message from the target EES, the target EAS can perform the following operations:

[0187] (1) When the target EAS receives the application context of the terminal device being pushed, or receives the application context migration request of the terminal device, or agrees to receive the migration of the application client of the terminal device, or agrees to provide services for the application client of the terminal device, then: the target EAS calls the context receiving service API of the target EES; or the target EAS sends a context receiving request message to the target EES. The target EAS carries the address (e.g., URL or IP address and port number) of the application context received from the target EES in the request message.

[0188] (2) The target EAS can call the APIs provided by the target EES for application context migration, application context synchronization, or application context recovery to obtain the application context from the source EAS, source EES, or target EES terminal device. At this time, the target EAS specifies at least one of the identifiers of the source EES, source EAS, or terminal device to obtain the application context of the terminal device from the source EAS.

[0189] Optionally, after receiving a notification message from the target EES, the target EAS can perform the following operations: Figure 6 Let me give an example.

[0190] S601. The target EAS calls the application context request service API of the target EES to obtain the application context.

[0191] The API's input parameters include the address for retrieving the application context. In one implementation, the address may include the address information of the source EAS and the terminal device information; in this case, the API's input parameters may also include the information of the EES corresponding to the source EAS. In yet another implementation, the address is provided by the source EES, meaning the application context is generated by the source EES. For example, the source EES finds the memory address block of the application context corresponding to the terminal device and uses the data corresponding to that address block as the application context.

[0192] S602. If the target EAS does not specify the source EES corresponding to the source EAS, the target EES will find the source EES corresponding to the source EAS based on the source EAS.

[0193] For example, if the target EES previously cached the corresponding source EES for the source EAS, or if the source EES is configured with a mapping between EES and EES service address ranges, then the target EES will match the corresponding source EES based on the target EAS's address information. The target EES calls the source EES's context request service API, whose input parameters include the source EAS's address and the terminal device's information. The source EES's context request service API can also be called the context transport service API.

[0194] S603. Optionally, if the source EAS is responsible for managing the UE context, the source EES further sends a service continuity notification message, i.e., the notification message corresponding to API-1, to the source EAS. Otherwise, if the source EES manages the UE's application context, the source EES directly executes step S605.

[0195] S604. If the source EAS accepts the request, the source EAS calls the source EES's context transport service API.

[0196] The source EAS can carry the terminal device's application context data in this API and indicate that the context request is accepted.

[0197] S605, the source EES sends the context received from the source EES to the target EES, or the source EES obtains the application context data of the terminal device and sends it to the target EES.

[0198] The application context data of a terminal device can be, for example, a specific memory block on a virtual machine. For instance, the source EES locates the memory address block corresponding to the application context of the terminal device and uses the data corresponding to that address block as the application context.

[0199] S606, The target EES sends the application context data of the terminal device to the target EAS.

[0200] S607, Application context of transmission terminal equipment.

[0201] If the data volume is large, during the process of S601 to S606, the target EAS can negotiate with the source EAS or source EES to use out-of-band, that is, the application context data is transmitted in an independent media data channel instead of in the signaling message. After S601 to S606 are completed, the source EAS or source EES will send the data to the target EAS in the data channel.

[0202] It should be noted that, in the embodiments of this application, Figure 3 , Figure 4 and Figure 5 Implementation examples may coexist, or some examples may be present. This application's embodiments trigger application context migration through a subscription notification service between the source EES and the source EAS and / or EEC, and through a subscription notification service between the target EES and the target EAS. The following description, using an application context migration process in an application scenario as an example, further details the notification method for business continuity events provided by this application's embodiments.

[0203] Figure 7 The example assumes that the source EAS has already obtained information from the source EES.

[0204] S701, The source EAS calls the source EES's EAS discovery request (edge ​​application server discovery request) service.

[0205] The source EAS can become unavailable when it detects that it can no longer provide services that meet the service requirements of the terminal device. For example, the source EAS may find that its load exceeds a preset threshold, or the EAS may detect that the terminal device has moved out of the source EAS's service area or out of the EDN where the current EAS is located. Alternatively, the source EAS may have previously subscribed to service continuity event notifications from the EES and received such notifications. Specifically, the service continuity event notifications may include event types such as terminal device movement / terminal device movement out of the EDN or the source EAS's (optimal) service area, terminal device roaming, change of terminal device IP address, or EDN or EAS overload.

[0206] S702. When the source EES receives an EAS discovery request, it checks whether the requesting source EES is authorized to perform EAS discovery operations. If authorization is granted, further, if the source EES determines that there is an EAS requesting services locally, it can directly execute S705. Otherwise, the source EES sends an EES request message to the ECS to request the acquisition of an EES. This EES request message may also carry the application's identifier, the terminal device's identifier, or the terminal device's location. The ECS retrieves information about EES matching the EES request message (referred to as the target EES) based on the EES request message and returns the information about the matching target EES to the source EES.

[0207] S703. The source EES calls the target EES's EAS discovery request service. This EAS discovery request can carry the application's identifier, as well as the identifier or location of the terminal device.

[0208] S704. The target EES selects a target EAS that matches the EAS discovery request and returns the target EAS to the source EES.

[0209] S705, the source EES sends an EAS discovery response message to the source EAS, which carries information about the discovered target EAS.

[0210] The source EES can send a service continuity event notification message to the EES after step S701. This message can carry an event type indicating that the EAS of the service terminal has changed, and further carry the address information of the target EAS.

[0211] pass Figure 7 In this example, the source EAS obtains information about the target EAS.

[0212] Figure 8 The example assumes that the source EAS has already obtained information from the source EES.

[0213] S801, The source EAS sends an application context transfer request or an application context delivery request to the source EES.

[0214] This can also be understood as the source EAS calling the source EES's context transfer service API, or the source EAS calling the source EES's context delivery service API. The API input parameters can also be considered as the parameters carried in the application context migration request. The application context migration request carries the target EAS's address information (such as IP address, IP address and port number, or URL). Optionally, the application context migration request also carries information corresponding to the target EES (the target EES is the EES registered with the target EAS) and the terminal device's identification information. If the terminal identification information is specified, it indicates that the application context of that terminal device is being transferred. If the terminal identification information is not specified, it can indicate the migration of all application contexts related to that application, which can include the application contexts corresponding to all terminal devices served by the source EAS. If the application context data is small, the source EAS can directly carry the application context data in the application context migration request message. Furthermore, the application context migration request can also carry the context migration capabilities supported by the source EAS, such as compression methods and / or transmission protocols, and security information such as context encryption / decryption keys or materials used to generate the keys. When the application context data is large, the context can be sent out-of-band, and the application context migration request can also carry the application context retrieval address information.

[0215] S802. If the source EAS does not carry the target EES information, the source EES obtains the target EES information based on the target EAS's address information. The target EES information includes the target EES's address (such as IP address, IP address and port number, or URL).

[0216] Specifically, the source EES can obtain target EES information in any of the following ways.

[0217] (1) The IP address of the target EAS is the IP address of the EES.

[0218] (2) Obtain the address of the corresponding EES through DNS by using some fields in the URL of the target EAS.

[0219] (3) The source EES is pre-configured with a mapping relationship between the address information of other EESs and their supported address list. The address list may be an IP address range, a set of IP addresses, or a set of URLs. The source ESS selects an EES that matches the address information of the target EES, and the address of the target EES is located in the address list supported by that EES.

[0220] (4) The source EES sends a request message to the ECS to request information about the target EES. This request message carries the address of the target EES. The ECS is pre-configured with a mapping between the address information of other EESs and their supported address lists, such as IP address ranges, a set of IP addresses, or a list of URLs. The ECS selects an EES whose address matches the target EES's address information; the target EES's address is located in the address list supported by that EES. The ECS then returns the address of the target EES to the original EES.

[0221] S803, The source EES sends a context transfer request or a context delivery request to the target EES.

[0222] The context migration request carries one or more parameters of the transport media supported by EES for context migration, such as compression method, transport protocol, supported security capabilities (algorithm, key), or source address information (IP address and port number) of the source EES context transmission, or address (IP or URL) for obtaining the application context. The context migration request also carries information sent by EAS in S801, which can be placed in a container.

[0223] This step can be understood as the source EES calling the target EES's context transfer request service API, or calling the target EES's context delivery request service API.

[0224] Optionally, the context migration request message may carry application context data.

[0225] S804a. The target EES sends a service continuity event notification message to the target EAS. This service continuity event notification message carries the service continuity event (or trigger) type. The specific time type can be referred to the description related to the target EES sending service continuity event notifications to the target EAS in the previous embodiments. For example, the service continuity event (or trigger) is the transmission of application context; or the service continuity event (or trigger) is the delivery of application context; or the service continuity event (or trigger) is the push of application context. Optionally, the service continuity event notification message carries the address (IP or URL) for obtaining the application context. This address can be provided by the source EAS (e.g., carried in S801), generated by the source EES and carried in S803, or generated by the target EES. Optionally, the service continuity event notification message can carry application context data.

[0226] S804b: The target EAS sends an ACK confirmation message. This step is optional.

[0227] S805a: If the target EAS accepts the application context of the terminal device, but S804a did not carry the application context, then the target EAS sends an application context receive request to the target EES. This can be understood as the target EAS calling the context receive service API of the target EES. Alternatively, it can be understood as the target EAS calling the context transmission data interface provided by the target EES. The application context receive request can carry media parameters supported by the target EAS (such as IP address, port, protocol, etc.).

[0228] S805b: The target EES returns an acknowledgment (ACK) message to the target EAS. This ACK message may carry media parameters of the transmission context between the target EES and the target EAS (such as IP address and port or URL, transmission protocol, encoding format, compression format, etc.), and may also carry the parameters carried by the target EAS in step 801 (the container in SS803). The ACK message may also carry address information (IP address and port number, or URL) used to obtain the application context. This address information may be from the target EES, or from the source EAS, or from the source EES.

[0229] S806. The target EES replies to the source EES with an application context migration response message or an application context transfer message. The application context migration response message may carry the transport media parameters for the application context migration selected (or supported) by the target EES {such as compression method, transport protocol, supported security capabilities (algorithm, key), and the address information (IP address and port number) for the target EES to receive the context transfer}.

[0230] This step can be understood as a callback of the API in S803.

[0231] S807, the source EES replies to the source EAS with an application context migration response message or an application context transfer message.

[0232] The application context migration response message carries media description information for the source EAS to send the context, such as the source EES receiving application context media parameters {IP address and port number, protocol, and optionally, supported security capabilities (algorithm, key)}. Alternatively, it may also carry the target EAS receiving application context media parameters (from step 805a).

[0233] This step can be understood as a callback of the API in S801.

[0234] S808. If out-of-band mode is used, the source EAS sends the terminal device application context data to the source EES.

[0235] Figure 5 In the embodiment, S503 can occur Figure 8 In step S804a of the embodiment.

[0236] like Figure 9 As shown, the notification method for business continuity events provided in this application embodiment is described in further detail, taking into account the application context migration process in an application scenario. The specific process is as follows.

[0237] S901, The source EAS sends a message to the source EES, for example, the message is an application context relocation request, and the source EES receives the message from the source EAS.

[0238] This message can carry the following parameters: terminal device information, such as at least one of the following: terminal device identifier, terminal device location, application client identifier, or application user identifier. The application context migration request can also carry application identifiers, such as FQDN, URL, EAS ID, and source EAS address information, such as IP address or URL address.

[0239] In one implementation, S901 can also be implemented in the following way: via a service API call. That is, the source EAS calls the application context migration API of the source EES, providing the API's input parameters, which are the same as those in the migration request. Here, "application" refers to executable software that can perform certain functions, such as various applications (APPs) on a mobile terminal.

[0240] S902. Obtain the address of the target EES from the source EES. The address of the target EES can be, for example, an IP address, port number, or URL address. It is also possible to obtain the identifier of the target EES from the source EES.

[0241] The source EES can obtain the address of the target EES from the edge data network configuration server (EDN CS).

[0242] S903. The source EES sends an application context relocation request to the target EES to request the application context, and the target EES receives the application context relocation request from the source EES.

[0243] An application context migration request may include the identifier of at least one terminal device, the identifier of the application, the address information of the source EAS, and the subscription context related to the core network.

[0244] The target EES selects or determines the target EAS based on the application context migration request.

[0245] S904. The target EES sends an application context relocation response to the source EES, and the source EES receives the application context relocation response from the target EES.

[0246] The application context relocation response indicates whether to allow (or accept) the relocation of an application on a given terminal device, or whether to accept the relocation of that application on that terminal device. Allowing the relocation of an application on a given terminal device can be understood as allowing the relocation of the application's context on that terminal device, or accepting the relocation of the application's context on that terminal device. The target EES can determine whether to allow the relocation of the application on that terminal device based on whether the EAS information it manages includes the EAS corresponding to that application on that terminal device, or based on the load status of the EAS corresponding to that application on that terminal device.

[0247] The following steps may also be optionally included after S903 and before S904.

[0248] S905, the target EES sends an application context relocation request message to the target EAS to request the relocation of the application context of the terminal device. The target EAS receives the application context relocation request message from the target EES.

[0249] Among them, the target EAS is the target EES determined in step S903.

[0250] The message includes the identifier of the terminal device, and may also include information about the core network elements connected to the application on that terminal device. The application on that terminal device corresponds to the same application as the target EAS.

[0251] S906, the target EAS returns an application context migration response message to the target EES in response to the message received in S905. The target EES receives the application context migration response message from the target EAS.

[0252] The response message may carry information about the terminal device, and the explanation of the terminal device information can be found in the explanation of terminal device information above.

[0253] Following S904, the following steps may also be included.

[0254] S907. The source EES sends a response message to the source EAS in response to the message received in S901. For example, if the message in S901 is an application context migration request, the response message is an application context migration response message. The source EAS receives the response message from the source EES. For example, the source EAS receives the application context migration response message from the source EES.

[0255] This message can be used to indicate that the source EAS can begin migrating the application on the terminal device, or it can be understood as indicating that the application context of the terminal device can begin to be transmitted, or indicating that the context transmission channel has been established. The message may contain: information about the terminal device, the address of the target EAS (the IP address or URL address of the target EAS), and receiving information for transmitting the application context, such as the IP address and / or port number of the receiving side (target EES or target EAS).

[0256] S908, the context of the application of the transmission terminal equipment.

[0257] In one implementation, the source EES transfers the application context of the terminal device to the target EES, and the target EES receives the application context of the terminal device sent by the source EES.

[0258] The source EES and the target EES can transfer context using the negotiated port for application migration.

[0259] In another implementation, the source EAS migrates the application context of the terminal device to the target EAS, and the target EAS receives the application context of the terminal device sent by the source EAS.

[0260] The source EAS and the target EAS can transfer context according to the port allocated to the target EAS for application migration in S906.

[0261] In another implementation, the source EAS can transmit the context of the application of the terminal device to the target EES through the source EES, and the target EES will then forward the received context of the application of the terminal device to the target EAS.

[0262] S909, Optionally, the source EAS sends an application context migration success notification message to the source EES.

[0263] based on Figure 9 Example, Figures 3-5 The operation of some devices in the embodiment can be Figure 9 Some steps of the embodiment are implemented.

[0264] For example, when the source EES sends a notification message to the EEC in S303, the source EES can trigger the sending of a notification message to the EEC after receiving the application context migration response message in S907.

[0265] When the source EES detects or determines that the conditions for service continuity event notification are met, the source EES can determine that the conditions for service continuity event notification are met after step S901. Receiving the message requesting application context migration from the first device, as described in step 4) above, can occur in step S901. The address of the target EAS being different from that of the source EAS, as described in step 10) above, can occur after step S904. The transmission of context from the source EAS to the target EAS, as described in step 5) above, can occur in step S908.

[0266] The completion of the application context transfer in step 12 above can be determined in S909.

[0267] The above-mentioned 13) can be determined when the source EES receives a message from the source EAS requesting a switch of the network user plane path of the terminal device.

[0268] Among the information received by the target EES, the EAS discovery request message from the source EES described in point 1 can occur in S903.

[0269] The message requesting the transmission of application context described in point 2 of the information received by the target EES above can occur in S903.

[0270] like Figure 10 As shown, the notification method for business continuity events provided in this application embodiment is described in further detail, taking into account the process of implementing application context business continuity in an application scenario. The specific process is as follows.

[0271] S1001, EEC sends an application context migration event notification subscription message to the source EES, and the source EES receives the business continuity event notification subscription message from EEC.

[0272] The specific description of this step is the same as S301. S1001 can be triggered when an application client registers with the EEC, an application client calls the EEC's edge application server discovery API, the EEC is installed on the operating system of the application client, or the EEC obtains the EES from the ECS after completing the business configuration process.

[0273] S1002, Source EES stores subscription information.

[0274] The specific description of this step is the same as that in S302.

[0275] S1003. The source EES returns a response message to the EEC regarding the subscribed message. This step is optional.

[0276] After accepting the subscription request from the EEC, the source EES returns a subscription message to the EEC, indicating that the subscription was successful.

[0277] Steps S1001 to S1003 and the subsequent business continuity event notifications sent from the source EES to the EEC can form a service API (referred to here as API-1) provided by the source EES, which can provide business continuity event notifications to the EEC.

[0278] S1004. Optionally, the application client and the source application edge server establish a connection to exchange application services and data.

[0279] S1005, the source EAS sends an application context migration event notification subscription message to the source EES, and the source EES receives the business continuity event notification subscription message from the source EAS.

[0280] The specific description of this step is the same as S401. The source EAS can trigger S1005 when the application client connects to the EAS, or when the source EAS registers with the EES.

[0281] S1006, Source EES stores subscription information.

[0282] The specific description of this step is the same as that of S402.

[0283] S1007. The source EES returns a response message to the source EAS regarding the subscribed message. This step is optional.

[0284] After accepting the subscription request from the source EAS, the source EES returns a subscription message to the source EAS, indicating that the subscription was successful.

[0285] Steps S1005 to S1007 and the subsequent business continuity event notifications sent from the source EES to the source EAS can form a service API (referred to here as API-2) provided by the source EES, which can provide business continuity event notifications to the EAS.

[0286] S1008, The target EAS sends an application context migration event notification subscription message to the target EES, and the source EES receives the business continuity event notification subscription message from the target EAS.

[0287] The specific description of this step is the same as S501. The target EAS can trigger S1005 at an opportune time after it is registered with the EES.

[0288] S1009, Target EES stores subscription information.

[0289] The specific description of this step is the same as in S502.

[0290] S1010, The target EES returns a response message to the target EAS regarding the subscribed message. This step is optional.

[0291] After accepting the subscription request from the target EAS, the target EES returns a subscription message to the target EAS, indicating that the subscription was successful.

[0292] Steps S1008 to S1010 and the subsequent business continuity event notifications sent from the source EES to the source EAS can form a service API (referred to here as API-3) provided by the target EES, which can provide business continuity event notifications to the EAS.

[0293] API-2 and API-3 can also be combined into a single API (referred to here as API-X). This API can provide business continuity event notifications corresponding to those in API-2 and API-3 without distinguishing whether the subscriber is the source EAS or the target EAS. EEC calls to API-1, source EAS calls to API-2, and target EAS calls to API-3 are executed independently, or they can be executed together.

[0294] The functions implemented in S1011-S1016 below are the service APIs for EAS discovery provided by the source EES (here referred to as API-4).

[0295] S1011, The source EAS calls the source EES's EAS discovery request service (edge ​​application server discovery request).

[0296] For details on this step, please refer to S701.

[0297] S1012. The source EES obtains information about the target EAS. If there is no information about the EAS that matches the request in S1011, the source EES obtains the message from the target EES.

[0298] For a detailed description of this step, please refer to S702.

[0299] S1013, The source EES calls the target EES's EAS discovery request service.

[0300] For a detailed description of this step, please refer to S703.

[0301] S1014. The target EES selects the target EAS that meets the EAS discovery request.

[0302] For a detailed description of this step, please refer to S704.

[0303] S1015, The target EES sends an EAS discovery response message to the source EES.

[0304] The EAS discovery response message contains information about the target EAS.

[0305] S1016. The source EES sends an EAS discovery response message to the source EAS.

[0306] For a detailed description of this step, please refer to S705.

[0307] S1017. After the target EES receives the request message in step S1013 and selects the target EAS, the target EES sends a service continuity event notification to the target EAS. S1017 is the notification message corresponding to API-3. This message further includes the address information of the source EAS and the identifier of the terminal device.

[0308] The functions implemented in S1018 to S1025 below are the service APIs (referred to here as API-5) provided by the source EES for the transport application context. Specifically:

[0309] S1018. The source EAS sends an application context transfer request or an application context delivery request to the source EES.

[0310] For a detailed description of this step, please refer to S801.

[0311] S1019. The source EES sends a context transfer request or a context delivery request to the target EES.

[0312] For a detailed description of this step, please refer to S802 and S803.

[0313] S1020, the target EES sends a business continuity event notification message to the target EAS.

[0314] For a detailed description of this step, please refer to S804a.

[0315] S1021, Response message to notification sent by the target EAS.

[0316] For a detailed description of this step, please refer to S804b.

[0317] S1022, The target EAS calls the context receiving service API of the target EES.

[0318] For a detailed description of this step, please refer to S805a.

[0319] S1023, The target EES returns an acknowledgment (ACK) message to the target EAS.

[0320] For a detailed description of this step, please refer to S805b.

[0321] S1024. The target EES replies to the source EES with an application context migration response message or an application context transfer message.

[0322] For a detailed description of this step, please refer to S806.

[0323] S1025, The source EES replies to the source EAS with an application context migration response message or an application context transfer message.

[0324] For a detailed description of this step, please refer to S807.

[0325] The functionalities of API-4 and API-5 can be combined into a single API (referred to here as API-Y). This API enables application migration on the terminal, specifically the migration of the terminal application context. For a detailed description of its functionality, please refer to... Figure 9 Description of the illustrated embodiment.

[0326] S1026. The source EAS sends the terminal device application context data to the source EES.

[0327] For a detailed description of this step, please refer to S808.

[0328] S1027. The source EES sends a business continuity event notification message to the EEC.

[0329] This step corresponds to the API-1 notification message. The notification can carry the event type: context transfer, or context transfer complete. Furthermore, the notification message also includes the address information of the target EAS. This step is optional.

[0330] S1028, EEC provides corresponding event notifications and information to AC.

[0331] The EEC can provide the AC with events such as: context transfer, or context transfer complete. Furthermore, the EEC can also provide the AC with the address information of the target EAS. This step is optional.

[0332] The functions implemented in S1029, S1032, and S1033 below are the user plane path switching service API (referred to here as API-6) provided by the source EES. Specifically:

[0333] S1029. The source EAS sends a user plane path switching request to the source EES. This is used to request that the user's user plane path be switched to the target path.

[0334] S1032, The source EES invokes the network's AF request or sends an AF request confirmation message to the network. This is used to instruct the network layer to switch the user plane path corresponding to the application on the terminal device.

[0335] S1033. The source EES sends a user plane path switching response to the source EAS. This step is optional.

[0336] When the source EES receives the message in S1029, it can send a service continuity event notification message corresponding to API-1 to the EEC. This notification message can also indicate that the event type is user plane path switching.

[0337] S1031, EEC provides corresponding event notifications and information to AC.

[0338] The EEC can provide the AC with the event: User plane path switch completed. This step is optional. The AC can then switch business data to the target EAS.

[0339] S1034. After the application context migration and user plane path switching are completed, the AC's application data can use the latest user plane path to interact with the target EAS.

[0340] It is understandable that API-1, API-2, API-3, API-4, API-5, API-6, API-X, API-Y, etc. can all be executed independently or in combination.

[0341] The methods provided in the embodiments of this application above have been described from the perspective of interaction between various devices such as the source EES, source EAS, EEC, target EES, or target EAS. This application also provides a communication device to implement the functions of the methods provided in the embodiments of this application above. The communication device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0342] like Figure 11As shown, based on the same technical concept, this application embodiment also provides a communication device 1100. The communication device 1100 can be a source EES, source EAS, EEC, target EES, or target EAS; it can also be a device within the source EES, source EAS, EEC, target EES, or target EAS; or it can be used in conjunction with a source EES, source EAS, EEC, target EES, or target EAS. In one design, the communication device 1100 may include modules corresponding to the methods / operations / steps / actions performed by the source EES, source EAS, EEC, target EES, or target EAS in the above method embodiments. These modules can be hardware circuits, software, or a combination of hardware circuits and software. In one design, the communication device 1100 may include a processing module 1101 and a communication module 1102. The processing module 1101 is used to call the communication module 1102 to perform receiving and / or sending functions. The communication module 1102 further includes a receiving module 1102-1 and a sending module 1102-2.

[0343] For example, when the communication device 1100 is used to perform operations performed by the Edge Enabled Server (EES):

[0344] The receiving module 1102-1 is used to receive a subscription message from the first device, the subscription message being used to request subscription to business continuity event notification; the sending module 1102-2 is used to send a notification message to the first device when the conditions for the business continuity event notification are met.

[0345] When the communication device 1100 is used to perform the operation performed by the first device:

[0346] The sending module 1102-2 is used to send a subscription message to the Edge Enabled Server (EES), the subscription message being used to request subscription to service continuity event notifications; the receiving module 1102-1 is used to receive notification messages from the EES.

[0347] The EES is the source EES, and the first device can be an EEC or a source EAS.

[0348] EES is the target EES, and the first device can be the target EAS.

[0349] The receiving module 1102-1 and the sending module 1102-2 can also be used to perform other operations performed by the source EES, EEC, source EAS, target EES or target EAS in the above method embodiments, which will not be described in detail here.

[0350] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0351] like Figure 12 The diagram shows a communication device 1200 provided in an embodiment of this application, used to implement the functions of the source EES, source EAS, EEC, target EES, or target EAS in the above-described method. This communication device can be a source EES, source EAS, EEC, target EES, or target EAS, or it can be a device within the source EES, source EAS, EEC, target EES, or target EAS, or a device compatible with the source EES, source EAS, EEC, target EES, or target EAS. The communication device 1200 can be a chip system. In this embodiment, the chip system can be composed of chips or may include chips and other discrete devices. The communication device 1200 includes at least one processor 1220 for implementing the method provided in this embodiment. The communication device 1200 may also include a communication interface 1210. In this embodiment, the communication interface can be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 1210 allows the device in the communication device 1200 to communicate with other devices.

[0352] The processor 1220 and the communication interface 1210 can be used to execute the steps or operations performed by the source EES, source EAS, EEC, target EES or target EAS in the above method embodiments, which will not be described in detail here.

[0353] The communication device 1200 may further include at least one memory 1230 for storing program instructions and / or data. The memory 1230 is coupled to the processor 1220. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1220 may operate in conjunction with the memory 1230. The processor 1220 may execute program instructions stored in the memory 1230. At least one of the at least one memory may be included in the processor.

[0354] This application embodiment does not limit the specific connection medium between the communication interface 1210, processor 1220, and memory 1230. This application embodiment... Figure 12The memory 1230, processor 1220, and communication interface 1210 are connected via a bus 1240. Figure 12 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 12 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0355] When communication devices 1100 and 1200 are specifically chips or chip systems, the communication module 1102 and communication interface 1210 can output or receive baseband signals. When communication devices 1100 and 1200 are specifically devices, the communication module 1102 and communication interface 1210 can output or receive radio frequency signals.

[0356] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0357] In this embodiment, the memory 1230 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in this embodiment can also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0358] Some or all of the operations and functions performed by the source EES, source EAS, EEC, target EES, or target EAS described in the above method embodiments of this application can be implemented using chips or integrated circuits.

[0359] To achieve the above Figure 11 or Figure 12Regarding the functions of the aforementioned communication device, this application embodiment also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the source EES, source EAS, EEC, target EES, or target EAS in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing necessary program instructions and data for the communication device.

[0360] This application provides a computer-readable storage medium storing a computer program, the computer program including instructions for performing the above-described method embodiments.

[0361] This application provides a computer program product containing instructions that, when run on a computer, cause the above-described method embodiments to be executed.

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

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

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

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

[0366] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

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

Claims

1. A method for notifying business continuity events, applied to a source edge enable server (EES), characterized in that, include: Receive a subscription message from a first device, the subscription message being used to request subscription to service continuity event notifications associated with the terminal device; When the conditions for the business continuity event notification are met, a notification message is sent to the first device; The notification message is used by the first device to trigger the migration of the application context. The notification message also includes an event type, which indicates the type of event for the business continuity event notification. The event type includes the completion of the application context transmission.

2. The method as described in claim 1, characterized in that, The first device is the Source Edge Application Server (EAS); The event types also include any one or more of the following: service recovery; service interruption; application context recovery.

3. The method as described in claim 1, characterized in that, The first device is an edge-enabled client (EEC). The event type also includes: the address of the edge application server (EAS) serving the terminal device corresponding to the EEC changes.

4. The method according to any one of claims 1-3, characterized in that, When the conditions for the business continuity event notification are met, sending a notification message to the first device includes: When the source EES determines any one or more of the following, a notification message is sent to the first device: The terminal device moves out of the service area of ​​the source EDN or source EAS. The data network access identifier (DNAI) of the terminal device changes, and the location of the terminal device is determined based on the changed DNAI, causing it to move out of the service area of ​​the source EDN or source EAS. A message requesting the transmission of application context is received from the first device; A message requesting the migration of the application context was received from the first device; The source EAS transmits the context to the target EAS; Receive the message from the target EES requesting a migration context; Receive the message requesting the transport context from the target EES; Source EAS overload or source EDN overload; The source EES initiates an application context migration.

5. The method as described in claim 1 or 3, characterized in that, The first device is an EEC. The step of sending a notification message to the first device when the conditions for the business continuity event notification are met includes: sending a notification message to the first device when the source EES determines any one or more of the following: The target EAS has a different address than the source EAS; The source EAS begins transmitting the application context to the target EAS; Application context transfer complete; The source EAS requests to switch the network user plane path of the terminal device. The source EES requests a switch of the network user plane path of the terminal device.

6. The method as described in claim 1 or 2, characterized in that, The first device is the source EAS. When the conditions for the service continuity event notification are met, sending a notification message to the first device includes: When the source EES determines that the terminal device is roaming, it sends a notification message to the first device.

7. The method as described in claim 6, characterized in that, The source EES detects that the terminal device is roaming, including: The source EES obtains indication information from the AMF or SMF, and the indication information is used to indicate that the terminal device is roaming.

8. The method according to any one of claims 1-3 or 7, characterized in that: The subscription message contains the conditions for the business continuity event notification, or the conditions for the business continuity event notification are set by the source EES.

9. The method according to any one of claims 1-3 or 7, characterized in that: The subscription message contains at least one of the identifier of the terminal device or the identifier of the application.

10. A method for notifying business continuity events, characterized in that, include: The first device sends a subscription message to the Source Edge Enabler Server (EES), the subscription message being used to request subscription to service continuity event notifications associated with the terminal device; The source EES receives the subscription message; When the conditions for the business continuity event notification are met, the source EES sends a notification message to the first device; wherein, the notification message is used by the first device to trigger the migration of the application context, and the notification message also includes an event type, which is used to indicate the type of event for the business continuity event notification, and the event type includes the completion of the application context transmission; The first device receives the notification message.

11. The method as described in claim 10, characterized in that, When the conditions for the business continuity event notification are met, sending a notification message to the first device includes: When the source EES determines any one or more of the following, a notification message is sent to the first device: The data network access identifier (DNAI) of the terminal device changes, and the location of the terminal device is determined based on the changed DNAI, causing it to move out of the service area of ​​the source EDN or source EAS.

12. The method as described in claim 10 or 11, characterized in that: The subscription message contains the conditions for the business continuity event notification.

13. The method as described in claim 10 or 11, characterized in that: The subscription message contains at least one of the identifier of the terminal device or the identifier of the application.

14. A communication device, characterized in that, The apparatus is used to perform the method as described in any one of claims 1-9.

15. A communication device, characterized in that, The apparatus is used to perform the method as described in any one of claims 10-13.

16. A communication device, characterized in that, include: A processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the method as described in any one of claims 1-9 to be performed.

17. A communication device, characterized in that, include: A processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the method as described in any one of claims 10-13 to be performed.

18. A communication system, characterized in that, It includes the apparatus as described in claim 14 and the apparatus as described in claim 15; or it includes the apparatus as described in claim 16 and the apparatus as described in claim 17.

19. A computer-readable storage medium, characterized in that, The computer storage medium stores computer-readable instructions, which, when executed on a communication device, execute the method as described in any one of claims 1-9, or execute the method as described in any one of claims 10-13.

Images