Method, apparatus, and electronic device for migrating application context

Abstract

Embodiments of the present application provide a method, device and electronic equipment for migrating application context. The method comprises: receiving, by a source edge enable server (EES), a request from a source edge application server (EAS) for exchanging application context data with a target EAS, wherein the application context data relates to an application to be migrated from the source EAS to the target EAS; sending the request from the source EES to a target EES; receiving, by the source EES, a response from the target EES comprising connection information for migrating the application context data; and sending the response to the source EAS, wherein the application context data is exchanged directly between the source EAS and the target EAS based on the connection information.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 275,370, filed November 3, 2021, with the United States Patent and Trademark Office, and U.S. Patent Application No. 17 / 979,399, filed November 2, 2022, the disclosures of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to 5th generation (5G) media streaming (5GMS), and more specifically to a method, apparatus, and electronic device for migrating application context. Background Technology

[0004] The fifth-generation (5G) standard for broadband networks allows applications to run on edge networks, enabling high bandwidth, low latency, and distributed processing.

[0005] 3GPP TS23.558 (3GPP; Technical Specification Group Services and Systems; Architecture for Enabling Edge Applications (Rev. 17), V2.0.0) defines a general architecture for enabling edge applications, including the discovery of hardware capabilities for edge components. 3GPP TS26.501 (3GPP TS26.501, 3GPP; Technical Specification Group Services and Systems; 5G Media Streaming (5GMS); General Description and Architecture (Rev. 16), V16.3.1) defines a general architecture for 5G media streaming applications, and TS26.512 defines the application programming interface (API) for calling this architecture. 3GPP TR 26.803 (3GPP; Technical Specification Group Services and Systems; Study on 5G Media Streaming Extensions for Edge Processing (Rev. 17), V1.5.1) also addresses 5GMS and edge processing.

[0006] The 5G edge architecture defined in 3GPP TS23.558 only supports the migration of actual data through the 5G edge architecture and via the individual hubs within it. However, such migration may not be very efficient. Application servers in the network can have more efficient direct connections. Summary of the Invention

[0007] According to one or more embodiments, a method for migrating application context via a fifth-generation (5G) edge network includes: receiving a request from a source edge application server (EAS) via a source edge enabling server (EES) to exchange application context data with a target EAS, wherein the application context data pertains to an application to be migrated from the source EAS to the target EAS; sending the request from the source EES to the target EES; receiving a response from the target EES via the source EES including connection information for migrating the application context data; and sending a response to the source EAS, wherein the application context data is exchanged directly between the source EAS and the target EAS based on the connection information.

[0008] According to one or more embodiments, an apparatus for migrating application context via a fifth-generation (5G) edge network includes: at least one memory configured to store program code; and at least one processor configured to read the program code and operate according to the instructions of the program code, the program code including: a first receiving code configured to cause the at least one processor to receive a request from a source edge application server (EAS) via a source edge enabling server (EES) to exchange application context data with a target EAS, wherein the application context data relates to an application to be migrated from the source EAS to the target EAS; a first sending code configured to cause the at least one processor to send a request from the source EES to the target EES; a second receiving code configured to cause the at least one processor to receive a response from the target EES via the source EES including connection information for migrating the application context data; and a second sending code configured to cause the at least one processor to send a response to the source EAS, wherein the application context data is exchanged directly between the source EAS and the target EAS based on the connection information.

[0009] According to one or more embodiments, a non-volatile computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device for migrating application context via a fifth-generation (5G) edge network, cause one or more processors to: receive a request from a source edge application server (EAS) via a source edge enable server (EES) to exchange application context data with a target EAS, wherein the application context data pertains to an application to be migrated from the source EAS to the target EES; send a request from the source EES to the target EES; receive a response from the target EES via the source EES including connection information for migrating the application context data; and send a response to the source EAS, wherein the application context data is exchanged directly between the source EAS and the target EAS based on the connection information. Attached Figure Description

[0010] Other features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings, in which:

[0011] Figure 1 This is a diagram illustrating an environment in which the methods, apparatus, and systems described herein can be implemented according to embodiments.

[0012] Figure 2 yes Figure 1 A block diagram of example components of one or more devices.

[0013] Figure 3 This is a diagram of a 5G edge network architecture according to an embodiment.

[0014] Figure 4 This is a flowchart of an example process for migrating an application context according to an embodiment.

[0015] Figure 5 This is a flowchart of an example process for migrating an application context according to an embodiment. Detailed Implementation

[0016] Figure 1 This is a schematic diagram of an environment 100 in which the methods, apparatus, and systems described herein can be implemented according to embodiments. Figure 1 As shown, environment 100 may include user equipment 110, platform 120, and network 130. The devices in environment 100 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0017] User equipment 110 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information related to platform 120. For example, user equipment 110 may include computing devices (e.g., desktop computers, laptop computers, tablet computers, handheld computers, smart speakers, servers, etc.), mobile phones (e.g., smartphones, cordless phones, etc.), wearable devices (e.g., smart glasses or smartwatches), or similar devices. In some embodiments, user equipment 110 may receive information from and / or send information to platform 120.

[0018] Platform 120 includes one or more devices as described elsewhere herein. In some embodiments, platform 120 may include a cloud server or a group of cloud servers. In some embodiments, platform 120 may be designed to be modular, allowing software components to be swapped in or out as needed. This allows platform 120 to be easily and / or quickly reconfigured for different purposes.

[0019] In some implementations, as shown in the figures, platform 120 may be hosted in a cloud computing environment 122. It is worth noting that while the implementations described herein describe platform 120 as hosted in a cloud computing environment 122, in some implementations, platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0020] The cloud computing environment 122 includes the environment of the hosting platform 120. The cloud computing environment 122 can provide services such as computing, software, data access, and storage, without requiring end users (e.g., user equipment 110) to know the physical location and configuration of the systems and / or devices of the hosting platform 120. As shown in the figure, the cloud computing environment 122 may include a set of computing resources 124 (collectively referred to as "computing resources 124" and individually as "computing resource 124").

[0021] Computing resource 124 includes one or more personal computers, workstations, server devices, or other types of computing and / or communication devices. In some embodiments, computing resource 124 may host platform 120. Cloud resources may include computing instances executing in computing resource 124, storage devices provided in computing resource 124, data migration devices provided by computing resource 124, etc. In some embodiments, computing resource 124 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0022] Further as Figure 1 As shown, computing resources 124 include a set of cloud resources, such as one or more applications (APP) 124-1, one or more virtual machines (VM) 124-2, virtualized storage (VS) 124-3, one or more hypervisors (HYP) 124-4, etc.

[0023] Application 124-1 includes one or more software applications that can be provided to, or accessed by, user device 110 and / or platform 120. Application 124-1 does not require the installation and execution of any software applications on user device 110. For example, application 124-1 may include software associated with platform 120, and / or any other software available through cloud computing environment 122. In some implementations, an application 124-1 may send / receive information to or from one or more other applications 124-1 via virtual machine 124-2.

[0024] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs, similar to a physical machine. Virtual machine 124-2 can be a system virtual machine or a process virtual machine, depending on the extent to which virtual machine 124-2 uses and corresponds to any real machine. A system virtual machine can provide a complete system platform that supports the execution of a complete operating system (OS). A process virtual machine can execute a single program and can support a single process. In some implementations, virtual machine 124-2 can execute on behalf of a user (e.g., user device 110) and can manage the infrastructure of cloud computing environment 122, such as data management, synchronization, or long-term data migration.

[0025] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that utilize virtualization technology within the storage systems or devices of computing resource 124. In some implementations, the type of virtualization within the context of the storage system may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage so that the storage system can be accessed without regard to physical storage or heterogeneous architecture. Separation allows storage system administrators to flexibly manage end-user storage. File virtualization can eliminate the dependency between data accessed at the file level and the location of physical storage files. This can optimize storage usage, server consolidation, and / or performance for non-disruptive file migration.

[0026] Hypervisor 124-4 provides hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer such as computing resource 124. Hypervisor 124-4 can provide a virtual operating platform to the guest operating systems and manage their execution. Multiple instances of various operating systems can share virtualized hardware resources.

[0027] Network 130 includes one or more wired and / or wireless networks. For example, network 130 may include cellular networks (e.g., fifth-generation (5G) networks, Long-Term Evolution (LTE) networks, third-generation (3G) networks, Code Division Multiple Access (CDMA) networks, etc.), Public Land Mobile Networks (PLMNs), Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks (MANs), telephone networks (e.g., Public Switched Telephone Networks (PSTNs)), private networks, self-organizing networks, intranets, the Internet, fiber-optic networks, etc., and / or combinations of these or other types of networks.

[0028] Figure 1 The number and arrangement of devices and networks shown are provided as an example. In reality, with... Figure 1 Compared to the devices and / or networks shown, there can be more devices and / or networks, fewer devices and / or networks, different devices and / or networks, or different arrangements of devices and / or networks. Furthermore, Figure 1 The two or more devices shown can be implemented within a single device, or Figure 1 The single device shown can be implemented as multiple distributed devices. Alternatively, a group of devices in environment 100 (e.g., one or more devices) can perform one or more functions described as being performed by another group of devices in environment 100.

[0029] Figure 2 yes Figure 1 A block diagram of example components for one or more devices. Device 200 may correspond to user device 110 and / or platform 120. Figure 2 As shown, device 200 may include bus 210, processor 220, memory 230, storage component 240, input component 250, output component 260 and communication interface 270.

[0030] Bus 210 includes components that allow communication between components of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 is a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or another type of processing component. In some embodiments, processor 220 includes one or more processors that can be programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions for use by processor 220.

[0031] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), optical disks (CDs), digital versatile disks (DVDs), floppy disks, cassette tapes, magnetic tapes, and / or other types of non-volatile computer-readable media, and corresponding drives.

[0032] Input component 250 includes components that allow device 200 to receive information, such as a touchscreen display, keyboard, keypad, mouse, buttons, switches, and / or microphone. Alternatively, input component 250 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, accelerometer, gyroscope, and / or actuator). Output component 260 includes components that provide output information from device 200, such as a display, speaker, and / or one or more light-emitting diodes (LEDs).

[0033] Communication interface 270 includes transceiver-like components (e.g., a transceiver and / or separate receiver and transmitter) that enable device 200 to communicate with other devices, for example, via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 270 may allow device 200 to receive information from and / or provide information to another device. For example, communication interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0034] Device 200 can perform one or more processes described herein. Device 200 can perform these processes in response to processor 220 executing software instructions stored in a non-volatile computer-readable medium (e.g., memory 230 and / or storage component 240). Computer-readable medium is defined herein as a non-volatile memory device. A memory device includes storage space within a single physical storage device or storage space distributed across multiple physical storage devices.

[0035] Software instructions can be read into memory 230 and / or storage component 240 from another computer-readable medium or from another device via communication interface 270. When executed, the software instructions stored in memory 230 and / or storage component 240 can cause processor 220 to perform one or more processes described herein. Alternatively or additionally, hardware wiring circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.

[0036] Figure 2 The number and arrangement of components shown are provided as an example. In fact, with... Figure 2 Compared to the components shown, device 200 may include more components, fewer components, different components, or components arranged differently. Alternatively, a set of components of device 200 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 200.

[0037] Figure 3 This is a diagram of a 5G edge network architecture 300 according to an embodiment. Edge data network (EDN) 301 is a local data network. One or more edge application servers (EAS) 302 and one or more edge enable servers (EES) 303 are included within EDN 301. In an embodiment, one or more EAS 302 may include a source EAS 302a and a target EAS 302b, and one or more EES 303 may include a source EES 303a and a target EES 303b, as described below regarding... Figure 3 A more detailed discussion follows. In this embodiment, one or more EES 303s may communicate with each other using Link Enhanced Data Rate GSM Evolution Technology Version 9 (EDGE-9). An Edge Configuration Server (ECS) 304 provides configuration related to the EES 303, including details of the EDN 301 that hosts the EES 303. A User Equipment (UE) 305 includes an Application Client (AC) 306 and an Edge Enabled Client (EEC) 307. EAS 302, EES 303, and ECS 304 may interact with the 3GPP core network 308.

[0038] EES 303 provides the support functions required by EAS 302 and EEC 307. The functionality of EES 303 may include: providing configuration information for EEC 307 to enable it to exchange application data services with EAS; supporting API callers and API opening functions, such as those specified in 3GPP TS23.222; interacting with 3GPP core network 308 to access network functions directly (e.g., via PCF) or indirectly (e.g., via Service Capability Open Function (SCEF) / NEF / SCEF+NEF); supporting application context migration; supporting the external exposure of 3GPP network and service capabilities to EAS 302 via link EDGE-3; supporting registration (i.e., registration, update, and deregistration) functionality for EEC 307 and EAS; and supporting on-demand triggering of EAS 302 instantiation.

[0039] EEC 307 provides the support functions required by AC. The functionality of EEC 307 may include: retrieving and providing configuration information to enable it to exchange application data traffic with EAS 302; and discovering EAS 302 available in EDN 301.

[0040] ECS 304 provides the support functions required for the connection between EEC 307 and EES 303. The functionality of ECS 304 includes: providing edge configuration information for EEC 307, such as information for EEC 307 to connect with EES 303 (e.g., service area information applicable to LADN) and information for establishing a connection with EES 303 (e.g., URI); supporting registration functionality (i.e., registration, update, and deregistration) for EES 303; supporting API call procedures and API opening functions as specified in 3GPP TS23.222; and the ability to interact with 3GPP core network 308 to access network functions directly (e.g., PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF).

[0041] AC 306 is an application residing in UE 305 that performs client functions.

[0042] EAS 302 is an application server residing in EDN 301, performing server functions. AC 306 connects to EAS 302 to leverage the advantages of edge computing to utilize application services. The application's server functions may be available only as EAS 302. However, some server functions may also be available at the edge and in the cloud, as EAS 302 residing in the cloud and the application server, respectively. The server functions provided by EAS 302 and its cloud application server counterparts may be the same or different; if they are different, the application data services exchanged with AC may also be different. EAS 302 can consume 3GPP Core Network 308 capabilities in different ways. For example, if it is a trusted entity of 3GPP Core Network 308, it can directly call the 3GPP Core Network 308 function APIs; it can call 3GPP Core Network 308 capabilities through EES 303; and it can call 3GPP Core Network 308 capabilities through capability opening functions such as SCEF or NEF.

[0043] Architecture 300 may include several different interfaces for enabling edge applications, which may be referred to as reference points. For example, link EDGE-1 may be a reference point enabling interaction between EES 303 and EEC 307. This link supports: registering and deregistering EEC 307 with EES 303; retrieving and providing EAS 302 configuration information; and discovering EAS 302 available in EDN 301.

[0044] Link EDGE-2 can serve as a reference point enabling interaction between EES 303 and 3GPP core network 308. This link supports, for example, access to the SCEF and NEF APIs defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, and 3GPP TS29.122; or access to 3GPP core network 308 functions and APIs to retrieve network capability information using an EES 303 deployed within the MNO trust domain (see Clause 5.13 of 3GPP TS23.501, 3GPP TS23.503, and 3GPP TS23.682). Considering different deployment models, link EDGE-2 can reuse 3GPP reference points or interfaces from EPS or 5GS.

[0045] Link EDGE-3 can serve as a reference point enabling interaction between EES 303 and EAS 302. This link supports: registering EAS 302 using availability information (e.g., time constraints, location constraints); deregistering EAS 302 from EES 303; discovering information about target EAS 302 to support application context migration; providing information on network capability access (e.g., location information, Quality of Service (QoS) related information); and requesting the establishment of a data session with a specific QoS between AC and EAS 302.

[0046] Link EDGE-4 can serve as a reference point enabling communication between ECS 304 and EEC 307. This link supports providing edge configuration information to EEC 307.

[0047] Link EDGE-5 can serve as a reference point for enabling interaction between the AC and EEC 307.

[0048] Link EDGE-6 can serve as a reference point enabling interaction between ECS 304 and EES 303. This link supports: registering EES 303 information with ECS 304.

[0049] Link EDGE-7 can serve as a reference point enabling interaction between EAS 302 and 3GPP core network 308. This link supports, for example, access to the SCEF and NEF APIs defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, and 3GPP TS29.122; or access to 3GPP core network 308 functions and APIs to retrieve network capability information using EAS 302 deployed within the MNO trust domain (see Clause 5.13 of 3GPP TS23.501 and 3GPP TS23.682). Considering different deployment models, link EDGE-7 can reuse 3GPP reference points or interfaces from EPS or 5GS.

[0050] Link EDGE-8 can serve as a reference point enabling interaction between ECS 304 and 3GPP core network 308. This link supports, for example, access to the SCEF and NEF APIs defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, and 3GPP TS29.122; and access to 3GPP core network 308 functions and APIs to retrieve network capability information using an ECS 304 deployed within the MNO trust domain (see Clause 5.13 of 3GPP TS23.501 and 3GPP TS23.682). Considering different deployment models, link EDGE-8 can reuse 3GPP reference points or interfaces from EPS or 5GS.

[0051] AC 306 can send a query to EES 303 via EEC 307 to discover suitable EASs. In this query, AC 306 includes an EAS discovery filter, which defines the characteristics required for a suitable EAS. In the response, EEC 307 provides AC 306 with a list of matching EASs and some of their characteristics. AC 306 then selects the best EAS from the list.

[0052] In the architecture described above, depending on changes in the UE's location or required resources, it may be necessary to migrate or move an application running on one of the EAS 302 (e.g., source EAS 302a) to another EAS 302 (e.g., target EAS 302b). In this case, since the application running in source EAS 302a has some context, it is necessary to migrate that context to the target EAS (target EAS 302b).

[0053] The 5G edge architecture defined in 3GPP TS23.558 defines a method for migration via two hubs:

[0054] Source EAS 302a◇Source EES 304a◇Target EES 304b◇Target EAS 302b

[0055] The EDGE-9 API provides a mechanism for this migration. However, in this approach, the actual application context data (which can be large) must be migrated through the path described above.

[0056] Therefore, embodiments can provide a method for migration by reference. In this case, connection information for migration between source EAS 302a and target EAS 302b can be exchanged between source EES 304a and target EES 304b, but the actual data migration can occur directly between source EAS 302a and target EAS 302b. As a result, embodiments can provide a mechanism to signal connection information between two application servers, such as two EAS 302s, without incurring the burden of data migration.

[0057] In this case, one of the following pieces of information can be provided as connection information, which can also be referred to as application context properties:

[0058] 1. From source EAS 302a to target EAS 302b:

[0059] a. Source address of application context storage

[0060] b. Unique application context ID

[0061] c. Supported protocols

[0062] d. Security Information

[0063] e. Expiry Date

[0064] 2. From target EAS 302b to source EAS 302a:

[0065] a. Target address of application context storage

[0066] b. Unique application context ID

[0067] c. Supported protocols

[0068] d. Security Information

[0069] e. Expiry Date

[0070] In an embodiment, information c, d, and e, as well as any additional information, can be stored in a scheme, and a scheme identifier can be used to signal the scheme. For example, in an embodiment, the following information can be provided:

[0071] 1. From source EAS 302a to target EAS 302b:

[0072] a. Source address of application context storage

[0073] b. Unique application context ID

[0074] c. Scheme identifier

[0075] d. Plan

[0076] 2. From target EAS 302b to source EAS 302a:

[0077] a. Target address of application context storage

[0078] b. Unique application context ID

[0079] c. Scheme identifier

[0080] d. Plan

[0081] Figure 4 This is a flowchart of an example process 400 for migrating an application context according to an embodiment. Figure 4 As shown, in operation 402, source EAS 302a may send a request to source EES 303a. In an embodiment, this request may include a request to exchange application context attributes with target EAS 302b. In an embodiment, the context attributes may correspond to or include connection information. In operation 404, source EES 303a may send the request to target EES 303b. In an embodiment, source EES 303a and target EES 303b may communicate using an EDGE-9 link. In operation 406, target EES 303b may send the request to target EAS 302b. In operation 408, target EAS 302b may respond by sending a response to target EES 303b that includes context attributes and / or connection information. In operation 410, target EES may send the response to source EES 303a. In operation 412, source EES 303a may send the response to source EAS 302a. In operation 414, the source EAS 302a may use information in the response, such as context attributes and / or connection information, to migrate context, such as application context data, to the target EAS 302b.

[0082] Therefore, context attributes and / or connection information can be exchanged between the source EAS 302a and the target EAS 302b via the EDGE-9 interface, through the source EES 304a and the target EES 304b. The actual data migration of the application context can occur directly between the source EAS 302a and the target EAS 302b. Thus, in this embodiment, an edge network can be used to exchange context attributes, and different networks can be used to exchange the actual data migration corresponding to the application context data.

[0083] In this embodiment, connection information can be stored in a RESTful resource that represents state transitions. The resource can contain all the information needed to migrate from or to a point, including a Uniform Resource Locator (URL), a protocol such as HTTP POST or GET, authentication and / or encryption / decryption required for the migration, and an expiration time, the application context's capture time, and a unique ID for the application context. A RESTful resource can be, for example, a JavaScript Notation (JSON) object containing this information.

[0084] Therefore, in this embodiment, the connection information may be small, and the migration of this information can be efficient and fast. In this embodiment, application context migration can occur between two source and target application servers, such as two EAS 302s, using a preferred protocol, thus potentially making the migration even faster. In this embodiment, the connection information can be updated before the actual data migration. In this case, the cost of the update is minimal.

[0085] Accordingly, embodiments can provide application context migration information in a 5G edge network, wherein connection information for migrating application content data is transmitted via the 5G edge network and its enabling server, while the actual migration data occurs directly between two edge application servers. The connection information provides the source or destination of the application context data, as well as supported protocols, a unique context ID, security and authentication information, the migration expiration date and time, and any other additional information. Furthermore, embodiments can provide RESTful resources for the connection information, wherein data is stored in RESTful resources, and HTTP methods are used to send, retrieve, update, and delete this data.

[0086] Figure 5 This is a flowchart of an example process 500 for enabling edge applications according to an embodiment. Figure 5 One or more processing boxes can be defined by the above regarding Figures 1 to 4 Any of the components discussed can be used to perform this.

[0087] like Figure 5 As shown, process 500 may include receiving a request from a source edge application server (EAS) via a source edge enabling server (EES) to exchange application context data with a target EAS, wherein the application context data relates to an application to be migrated from the source EAS to the target EAS (block 502). In an embodiment, the source EES may correspond to source EES 303a, the source EAS may correspond to source EAS 302a, the target EES may correspond to target EES 303b, and the target EAS may correspond to target EAS 302b.

[0088] like Figure 5 As further shown, process 500 may include sending a request from the source EES to the target EES (box 504).

[0089] like Figure 5 As further shown, process 500 may include receiving a response (box 506) from the target EES via the source EES, including connection information for migrating application context data.

[0090] like Figure 5 As further shown, process 500 may include sending a response to the source EAS (block 508). In an embodiment, application context data may be exchanged directly between the source EAS and the target EAS based on connection information.

[0091] In this embodiment, a 5G edge network can be used to send requests and responses, and application context data can be exchanged without going through the 5G edge network.

[0092] In this embodiment, a request can be sent from the source EES to the target EES using the EDGE-9 interface, and a response can be sent from the target EES to the source EES using the EDGE-9 interface.

[0093] In an embodiment, a request may include at least one of the following: a source address corresponding to the storage of application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the source EAS, an expiration time associated with the request, and security information associated with the request.

[0094] In an embodiment, the connection information may include at least one of the following: a target address corresponding to the storage of application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the target EAS, an expiration time associated with at least one of the requests and responses, and security information associated with at least one of the requests and responses.

[0095] In an embodiment, at least one of the request and response may include a scheme identifier for signaling a scheme corresponding to application context data.

[0096] In this embodiment, connection information may be stored in a RESTful resource, and the RESTful resource may include Hypertext Transfer Protocol (HTTP) information for exchanging application context data.

[0097] Although Figure 5 An example block diagram of process 500 is shown, but in some implementations, process 500 may include... Figure 5The boxes depicted in the diagram may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes of process 500 may be executed in parallel.

[0098] Furthermore, the proposed methods can be implemented using processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-volatile computer-readable medium to perform one or more of the proposed methods.

[0099] The above-described technology can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

[0100] The embodiments disclosed herein can be used individually or in combination in any order. Furthermore, each of the embodiments (and their methods) can be implemented using processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored on a non-volatile computer-readable medium.

[0101] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations are possible based on the foregoing disclosure, or modifications and variations may be derived from practice of the embodiments.

[0102] As used in this article, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software.

[0103] Even if combinations of features are stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible embodiments. In fact, many of these features can be combined in ways not specifically stated in the claims and / or disclosed in the specification. While each dependent claim listed below may be directly subordinated to only one claim, the disclosure of possible embodiments includes each dependent claim combined with each other claim in the group of claims.

[0104] Elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, the articles “a” and “an” as used herein are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, the term “group” as used herein is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” The term “an” or similar language is used where only one item is referred to. Furthermore, the terms “having,” “possessing,” “containing,” etc., as used herein are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise.

Claims

1. A method for migrating application contexts, characterized in that, The method includes: The source edge enabling server (EES) receives a request from the source edge application server (EAS) to exchange application context data with the target EAS, wherein the application context data relates to the application to be migrated from the source EAS to the target EAS. The request is sent from the source EES to the target EES; Receive a response from the target EES via the source EES, including connection information for migrating the application context data; and Send the response to the source EAS. The application context data is exchanged directly between the source EAS and the target EAS based on the connection information.

2. The method according to claim 1, characterized in that, The request and the response were sent using a 5G edge network. The application context data is not exchanged through the 5G edge network.

3. The method according to claim 1, characterized in that, The request is sent from the source EES to the target EES using the Enhanced Data Rate Global System for Mobile Communications Evolution Version 9 (EDGE-9) interface. The response is sent from the target EES to the source EES using the EDGE-9 interface.

4. The method according to claim 1, characterized in that, The request includes at least one of the following: a source address corresponding to the storage of the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the source EAS, an expiration time associated with the request, and security information associated with the request.

5. The method according to claim 1, characterized in that, The connection information includes at least one of the following: the target address corresponding to the storage of the application context data, the application context identifier corresponding to the application context data, at least one protocol supported by the target EAS, an expiration time associated with at least one of the request and the response, and security information associated with at least one of the request and the response.

6. The method according to claim 1, characterized in that, At least one of the request and the response includes a scheme identifier for signaling a scheme corresponding to the application context data.

7. The method according to claim 1, characterized in that, The connection information is stored in a RESTful resource that represents state transitions. The RESTful resource includes Hypertext Transfer Protocol (HTTP) information used to exchange application context data.

8. A device for migrating application contexts, characterized in that, The device includes: The first receiving module is configured to receive a request from the source edge application server (EAS) via the source edge enabling server (EES) to exchange application context data with the target EAS, wherein the application context data relates to an application to be migrated from the source EAS to the target EAS. The first sending module is used to send the request from the source EES to the target EES; The second receiving module is configured to receive a response, including connection information for migrating the application context data, from the target EES via the source EES; and The second sending module is used to send the response to the source EAS. The application context data is exchanged directly between the source EAS and the target EAS based on the connection information.

9. The device according to claim 8, characterized in that, The request and the response were sent using a 5G edge network. The application context data is not exchanged through the 5G edge network.

10. The device according to claim 8, characterized in that, The request is sent from the source EES to the target EES using the EDGE-9 (Enhanced Data Rate GSMA Evolution Technology version 9) interface. The response is sent from the target EES to the source EES using the EDGE-9 interface.

11. The device according to claim 8, characterized in that, The request includes at least one of the following: a source address corresponding to the storage of the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the source EAS, an expiration time associated with the request, and security information associated with the request.

12. The device according to claim 8, characterized in that, The connection information includes at least one of the following: the target address corresponding to the storage of the application context data, the application context identifier corresponding to the application context data, at least one protocol supported by the target EAS, an expiration time associated with at least one of the request and the response, and security information associated with at least one of the request and the response.

13. The device according to claim 8, characterized in that, At least one of the request and the response includes a scheme identifier for signaling a scheme corresponding to the application context data.

14. The device according to claim 8, characterized in that, The connection information is stored in a RESTful resource that represents state transitions. The RESTful resource includes Hypertext Transfer Protocol (HTTP) information used to exchange application context data.

15. An electronic device, characterized in that, The method includes a memory for storing computer-readable instructions; and a processor for reading the computer-readable instructions and executing the method according to any one of claims 1 to 7 as instructed by the computer-readable instructions.

Images