Method and system for seamless service continuity in edge computing

Abstract

Accordingly, embodiments of the present disclosure disclose a method for seamless service continuity. The method includes: receiving service-related data packets from a first server (110a, 112a, 118); determining that a UE (102) is located in a service area served by both the first server (110a, 112a, 118) and a second server (110b, 112b); establishing a connection between the UE (102) and the second server (110b) based on the determination that the UE (102) is located in the service area; sending information related to the connection between the UE (102) and the second server (110b, 112b) to the first server (110a, 112a, 118); receiving information from the first server (110a, 112a, 118) including a notification indicating completion of transmission of an application context indicating a service to the second server (110b, 112b); switching the connection from the first server (110a, 112a, 118) to the second server (110b, 112b) based on the received information including the notification; receiving, in response to the switching of the connection, end data packets related to the service from the first server (110a, 112a, 118); and continuing the service using the connection established with the second server (110b, 112b) based on the received end data packets.

Description

Technical Field

[0001] The present disclosure relates to edge computing and, more particularly, to methods and systems for providing seamless service continuity during a handover of a service being provided to a user equipment from a source data network to a target data network in an edge computing network system. This application is based on and claims priority to Indian Application No. 201941039601, filed on Sep. 30, 2019, the disclosure of which is incorporated herein by reference. Background Art

[0002] The development of edge computing in wireless communication has changed the way data is processed and disposed of across millions of devices globally. The large-scale growth of artificial intelligence and the Internet of Things (IoT) has stimulated the development of edge computing network systems. Edge computing supports new applications that require real-time computing power as it has capabilities such as lower latency, higher bandwidth, and less backhaul traffic. Applications such as VR gaming, autonomous vehicles, robots, video processing, and network-assisted processing are highly dependent on edge computing capabilities.

[0003] Generally, in a wireless network system, a user equipment (UE) connects to the nearest data network or application server to utilize services. The data network can be a non-edge cloud data network or an edge data network. Each edge data network includes an edge enabler server (ES) for managing application servers, which is called an edge application server (EAS) when deployed in an edge data network (EDN), and a cloud application server (CloudAS) if deployed in a non-edge cloud data network. Now, whenever the UE hands over from a source data network to a target data network, the application context associated with the service being used by the UE needs to be transferred from the source data network to the target data network. However, the currently adopted methods perform the transfer of the application context when the UE has already handed over to the target data network or when the UE is about to hand over to the target data network, and both cases result in a significant lag in the service or, in the worst case, service interruption.

[0004] In view of the above, there is a need for a system or method for providing seamless service continuity to the UE during a handover from a source data network to a target data network.

[0005] Therefore, it is desirable to address the above disadvantages or deficiencies or at least provide a useful alternative. Summary of the Invention

[0006] Technical Problem

[0007] The main objective of the embodiments of this document is to provide a method and system for providing seamless service continuity to a user equipment (UE) in a wireless communication network system during the handover of the UE from a source data network to a target data network.

[0008] Another objective of the embodiments of this document is to enable an application service provider to deploy one or more overlapping service areas between a source data network and a target data network. Another objective of the embodiments of this document is to define operation rules specific to each of the one or more overlapping service areas so as to provide seamless service continuity to the UE during the handover from the source data network to the target data network. The one or more overlapping service areas correspond to service areas that fall within the service areas of multiple data networks. For example but not limited to, an overlapping service area may correspond to an area where services are available from a cloud data network or an edge data network, or an overlapping service area may correspond to an area where services are available from more than one edge data network.

[0009] Accordingly, the embodiments of this document disclose a method for providing seamless service continuity by a user equipment (UE) in a distributed wireless network system. The method includes: receiving a service-related data packet from a first server; determining that the UE is located in a service area served by both the first server and a second server; based on the determination that the UE is located in the service area, establishing a connection between the UE and the second server; sending information related to the connection between the UE and the second server to the first server; receiving from the first server information including a notification indicating the completion of the transfer of the application context of the service to the second server; based on the received information including the notification, switching the connection from the first server to the second server; in response to the switching of the connection, receiving a service-related end data packet from the first server; and based on the received end data packet, continuing the service using the connection established with the second server.

[0010] Accordingly, the embodiments of this document disclose another method for providing seamless service continuity by a first server in a distributed wireless network system. The method includes: sending a service-related data packet to a user equipment (UE); when sending the service-related data packet, receiving information related to the connection between the UE and a second server from the UE; in response to receiving the information related to the connection between the UE and the second server, sending to the UE information including a notification indicating the completion of the transfer of the application context of the service to the second server; in response to sending the information including the notification, sending a service-related end data packet to the UE; and disconnecting the connection between the UE and the first server.

[0011] Accordingly, embodiments herein disclose another method for providing seamless service continuity by a second server in a distributed wireless network system. The method includes: receiving a connection request from a user equipment (UE); sending a connection response indicating acceptance of the connection request to the UE; after the connection between the UE and a first server is switched to a connection between the UE and the second server, sending information related to the connection between the UE and the second server to the first server; and after sending the information related to the connection between the UE and the second server, sending service-related data packets to the UE.

[0012] Accordingly, embodiments herein disclose another method for providing seamless service continuity by a third server in a distributed wireless network system. The method includes: sending information indicating the availability of a service from a second server to a user equipment (UE); in response to the UE receiving the information indicating the availability of the service from the second server, receiving from the UE information that the UE is located in a service area served by both a first server and the second server; and in response to receiving the information that the UE is located in the service area, sending operation rules of the service area to the UE.

[0013] Accordingly, embodiments herein disclose a UE for providing service continuity in a wireless communication network system. The UE includes: a transceiver; and at least one processor configured to receive service-related data packets from a first server; determine that the UE is located in a service area served by both a first server and a second server; based on determining that the UE is located in the service area, establish a connection between the UE and the second server; send information related to the connection between the UE and the second server to the first server; receive from the first server information including a notification indicating completion of transfer of an application context of the service to the second server; based on receiving the information including the notification, switch the connection from the first server to the second server; in response to the switch of the connection, receive end data packets related to the service from the first server; and based on the received end data packets, continue the service using the connection established with the second server.

[0014] Accordingly, embodiments herein disclose a first server for providing service continuity in a wireless communication network system. The first server includes: a transceiver; and at least one processor configured to send service-related data packets to a user equipment (UE); when sending the service-related data packets, receive from the UE information related to the connection between the UE and a second server; in response to receiving the information related to the connection between the UE and the second server, send to the UE information including a notification indicating completion of transfer of an application context of the service to the second server; in response to sending the information including the notification, send end data packets related to the service to the UE; and disconnect the connection between the UE and the first server.

[0015] Accordingly, embodiments herein disclose a second server for providing service continuity in a wireless communication network system. The second server includes: a transceiver; and at least one processor configured to receive a connection request from a user equipment (UE); send a connection response indicating acceptance of the connection request to the UE; after the connection of the UE with a first server is switched to the connection of the UE with the second server, send information related to the connection of the UE with the second server to the first server; and after sending the information related to the connection of the UE with the second server, send service-related data packets to the UE.

[0016] Accordingly, embodiments herein disclose a third server for providing service continuity in a wireless communication network system. The third server includes: a transceiver; and at least one processor configured to send information indicating that a service is available from a second server to a user equipment (UE); in response to the UE receiving the information indicating that the service is available from the second server, receive from the UE information that the UE is located in a service area served by both a first server and the second server; and in response to receiving the information that the UE is located in the service area, send operation rules of the service area to the UE.

[0017] These and other aspects of the embodiments herein will be better understood and appreciated when considered in conjunction with the following description and the accompanying drawings. However, it should be understood that although the following description points out preferred embodiments and many of its specific details, the description is given by way of illustration and not limitation. Many changes and modifications can be made within the scope of the embodiments herein without departing from the scope of the embodiments herein, and the embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The method and system are shown in the drawings, and in all the drawings, the same reference numerals represent corresponding parts in each drawing. Referring to the drawings, the embodiments herein will be better understood from the following description, in which:

[0019] Figure 1 The network architecture of a wireless network system (100) for providing seamless service continuity to a UE according to embodiments disclosed herein is shown;

[0020] Figure 2A and Figure 2B collectively show a network environment scenario of a UE switching from a first data network to a second data network according to the prior art;

[0021] Figure 3 A network environment scenario for transmitting an application context during a UE's handover from a cloud data network to an edge data network using an overlapping service area according to embodiments disclosed herein is shown;

[0022] Figure 4A and Figure 4B illustrates a network environment scenario for transmitting an application context during a handover of a UE from a second edge data network to a first edge data network using an overlapping service area as disclosed herein;

[0023] Figure 5 illustrates a network environment scenario for transmitting an application context during a handover of a UE from a source EDN to a target EDN using an overlapping service area as disclosed herein;

[0024] Figure 6 illustrates another network environment scenario for transmitting an application context during a handover of a UE from a cloud data network to an edge data network using a single overlapping service area as disclosed herein;

[0025] Figure 7 illustrates another network scenario for transmitting an application context between a source EDN and a target EDN during a handover of a UE from a source EDN to a target EDN using a single overlapping service area as disclosed herein;

[0026] Figure 8A and Figure 8B collectively illustrate a sequence diagram representing the respective steps of a method for providing seamless service continuity during a handover of a UE from a first EDN to a second EDN as disclosed herein;

[0027] Figure 9 illustrates a hardware component diagram of a UE as disclosed herein;

[0028] Figure 10 illustrates a hardware component diagram of an ECS as disclosed herein;

[0029] Figure 11 illustrates a hardware component diagram of an EES as disclosed herein;

[0030] Figure 12 illustrates a hardware component diagram of an EAS as disclosed herein;

[0031] Figure 13A and Figure 13B collectively illustrate a flowchart showing a method for providing seamless service continuity in a distributed wireless network system (100) during a handover of a UE from a first data network to a second data network as disclosed herein; and

[0032] Figure 14Another flowchart is shown that illustrates a method for providing seamless service continuity in a distributed wireless network system during a handover of a UE from a first data network to a second data network in accordance with embodiments disclosed herein. DETAILED DESCRIPTION

[0033] Embodiments herein and their various features and advantageous details are more fully explained with reference to the non-limiting embodiments shown in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure embodiments herein. In addition, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" as used herein refers to a non-exclusive or. The examples used herein are merely for ease of understanding the manner in which embodiments herein can be practiced and further enable those skilled in the art to practice embodiments herein. Therefore, these examples should not be construed as limiting the scope of embodiments herein.

[0034] In accordance with the traditions of the art, embodiments can be described and illustrated in terms of blocks that perform one or more of the described functions. These blocks (which may be referred to herein as units or modules, etc.) are physically implemented by analog or digital circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and can optionally be driven by firmware. For example, the circuitry can be embodied in one or more semiconductor chips or on a substrate carrier such as a printed circuit board. The circuitry constituting the blocks can be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware performing some of the functions of the block and a processor performing other functions of the block. Each block of an embodiment can be physically divided into two or more interacting and discrete blocks without departing from the scope of the invention. Similarly, the blocks of an embodiment can be physically combined into more complex blocks without departing from the scope of the invention.

[0035] The accompanying drawings are used to facilitate an easy understanding of various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the present disclosure should be construed as extending to any variations, equivalents, and alternatives other than those specifically set forth in the accompanying drawings. Although terms such as first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0036] Accordingly, embodiments of the present disclosure implement a method for providing service continuity in a wireless communication network system. The method includes a UE consuming services from one of a first EAS (when the UE is connected to an edge data network) and a cloud AS (when the UE is connected to a non-edge cloud data network). Further, the method includes determining, by at least one EEC of the UE, a first EES associated with the first EAS, and the first EAS, that the current location of the UE is served by a second EAS and one of the first EAS and the cloud AS. The method further includes transmitting, by the at least one EEC, the first EES, and the first EAS, an application context associated with the service to the second EAS based on determining that the current location of the UE is served by the second EAS and one of the first EAS and the cloud AS. The method further includes the UE establishing connections with both the second EAS and a second EES associated with the second EAS, and the UE continuing the service using the connections established with both the second EAS and the second EES.

[0037] In an example, in existing methods, there is a lack of understanding of when to initiate the transmission of an application context associated with a service used by a UE whenever the UE switches from a first data network (which can also be interchangeably referred to as a "source data network") to a second data network (which can also be interchangeably referred to as a "target data network"). In traditional methods, there are two possible options, including a) triggering the transmission of the application context before the UE switches to the target data network, and b) triggering the transmission of the application context after the UE switches to the target data network. However, in both of these options, it is difficult to precisely determine how much time before the UE's switch to the target data network the application context transmission should be initiated, or how much time after the UE's switch to the target data network the application context transmission should be initiated. Due to the above-mentioned lack of understanding of the initiation time of the application context transmission during the UE's switch from the source data network to the target data network, users may experience a significant lag or interruption in the service continuity of the application services used by the UE.

[0038] Different from traditional methods and systems, the proposed method can be used to apply the operating rules that the UE, the source data network, and the target data network should follow during the UE's switch from the source data network to the target data network. The proposed method helps to deploy one or more overlapping regions between the source data network and the target data network, and also defines certain operating rules for each of the one or more overlapping regions.

[0039] The operating rules guide the UE, the source data network, and the target data network to transmit the application context during the UE's switch from the source data network to the target data network in order to achieve uninterrupted seamless service continuity.

[0040] In the proposed method, each deployed overlapping area is associated with a set of operation rules that are incorporated within the UE such that the UE, together with the source data network, decides to trigger the transfer of the application context when switching to the target data network without impeding the service continuity related to the application services consumed by the UE. In an alternative embodiment, the set of operation rules may be incorporated within the source data network or the target data network such that when the UE moves from the source data network to the target data network, the data network indicates and coordinates the transfer of the application context.

[0041] In an embodiment, the area or location served by the source data network, the target data network, or the overlapping service area between the source data network and the target data network may be defined as but not limited to a geographical area or a list of cell identifiers (IDs), or a list of tracking area identifiers (TAIs), or a list of data network access identifiers (DNAIs), or a combination thereof. In the case of cell IDs, tracking area identifiers (TAIs), and data network access identifiers (DNAIs), the overlapping area may be determined as the list of cell IDs, the list of tracking area identifiers (TAIs), and the list of data network access identifiers (DNAIs) common between the source data network and the target data network.

[0042] In an embodiment, the service area is an application-specific service area and may or may not be directly related to the edge data network area. The edge computing service provider, together with the application provider, is responsible for designing the service area for the application such that there is an overlap as described in the present invention according to the service continuity requirements of the application.

[0043] Now referring to the drawings, and more particularly to Figure 1 and Figures 3 - 14 wherein like reference numerals throughout the drawings always denote corresponding features, there are shown preferred embodiments.

[0044] Figure 1The network architecture of a wireless network system (100) for providing seamless service continuity to a UE according to an embodiment of the present invention disclosed herein is shown. The distributed wireless network system (100) includes a UE (102), a plurality of Edge Data Networks (EDNs) (108a - 108n), a Cloud Data Network (116), an Edge Configuration Server (ECS) (114), a service provider (122), and a 3rd Generation Partnership Project (3GPP) network (124). The UE (102) includes an Application Client (AC) (104) and an Edge Enabler Client (EEC) (106). Each of the plurality of EDNs (108a - 108n), such as the first EDN (108a), includes one or more Edge Application Servers and an Edge Enabler Server (EES), for example, the first EDN (108a) includes a first EAS (110a), another first EAS (110a’), and a first EES (112a), the second EDN (108b) includes a second EAS (110b) and a second EES (112b), the third EDN (108c) includes a third EAS (110c) and a third EES (112c), and so on. The Cloud Data Network (116) includes a Cloud Application Server (118).

[0045] To run an application within the UE (102), the AC (104), with the help of the EEC (106), connects to the Cloud AS (118) or at least one EAS (110a) to utilize the services of the application hosted by the Cloud AS (118) or at least one EAS (110a). The UE (102) connects to the Cloud Data Network (116) or the EDN (108a) based on the guidelines provided by the ECS (114), as the ECS (114) is a centralized server having information related to all the data networks within the system (100). The service provider (122) presents application services related to applications hosted by data networks such as the Cloud Data Network (116) or the EDNs (108a - 108n) to the UE (102) via the Internet. The UE (102), the EDNs (108a - 108n), the Cloud Data Network (116), the service provider (122), and the ECS (116) communicate with each other via the 3GPP network (124).

[0046] In an embodiment, the UE (102) can be, for example but not limited to, a cellular phone, a tablet, a virtual reality device, a smart phone, a laptop, a Personal Digital Assistant (PDA), a Global Positioning System, a multimedia device, a video device, an Internet of Things (IoT) device, and a smart watch. The 3GPP network (124) maintains communication standards according to the protocols defined in the 3rd Generation Partnership Project for Mobile Telecommunications.

[0047] AC (104) is an application installed in the UE that interacts with a corresponding application server such as the cloud AS (118) or the EAS (110a) at the EDN (108a) to run edge-capable applications in the UE (102). The ECS (114) initially provides information to the UE (102) to connect to the nearest EDN (108) to utilize edge application services. The functions of the ECS (114) include providing the UE (102) with service area configurations such that it is clear which service areas overlap with which service areas, and explicitly indicating the overlapping areas as the first overlapping service area or the second overlapping service area. The ECS (114) also provides the UE (102) with operation rules for the overlapping areas, and the operation rules set guidelines for the UE (102) so that the UE (102) knows the steps to take when switching from the service area of the first data network to the service area of the second data network, i.e., when switching from the connected data network (which can also be referred to as the "source data network" or the "first data network") to another data network (which can also be referred to as the "target data network" or the "second data network"). In an alternative embodiment, such guidelines can be pre-configured in the UE (102), where it is not required for the ECS (114) to provide them to the UE (102). The ECS (114) can also provide the UE (102) with edge computing service area details in a format that the UE (102) can determine the overlapping areas and related rules. In an alternative embodiment, the UE can switch from the service area of one EAS to the service area of another EAS within the same EDN (108). For example, the UE can switch from the service area of the first EAS (110a) to the service area of another first EAS (110a’) in the first EDN (108a). The service provider (122) is configured to strategically deploy one or more overlapping service areas within the source data network and the target data network. The service provider (122) determines the appropriate number of overlapping service areas to be deployed between the data networks, and determines the size of the overlapping service areas, based on factors such as the data traffic volume between the data networks, the estimated size of the application context related to the application services hosted by the data networks, the bandwidth requirements of the application services hosted by the data networks, the number of users who have subscribed to the application services hosted by the data networks, etc. In an alternative embodiment, the service provider can plan different overlapping service areas for each EAS (110a, 110a’, 110b...110n) running in the EDN (108) based on the specific requirements of the EAS (110a, 110a’, 110b...110n). The physical size of these overlapping areas can be variable and can be determined based on application requirements (such as the minimum time required to achieve meaningful application context synchronization).For example, for some applications, the size of the application context may be large and it may take a long time to synchronize between the first EAS (110a) and the second EAS (110b). Therefore, the size of the overlapping region should be large enough to ensure successful synchronization before the UE (102) moves out of the region of the second EAS (110b). One or more overlapping service regions correspond to the service regions served by both the first data network and the second data network. Alternatively or additionally, one or more overlapping service regions correspond to the service regions where services are available from at least two EASs from the same EDN (108), for example, the overlapping region between the service regions of EAS (110a) and EAS (110a’). In an alternative embodiment, the service regions and the overlapping service regions may correspond to the service regions of respective EASs (110a, 110b...110n) and the overlaps between the service regions of these EASs (110a, 110b...110n). A method of maintaining the service region as the service region of the data network similar to the method provided in the present invention can also be applied in such a system. The ECS (114) defines one or more operation rules for each overlapping service region and sends these operation rules as guidelines to the UE (102). It should be noted that the first data network may be the cloud data network (116), and the second data network may be the EDN (108a), and vice versa. Alternatively, the first data network may be the EDN (108a), and the second data network may be another EDN (108b) from multiple EDNs (108a - 108n). The UE (102) receives the guidelines from the ECS (114) and accordingly interacts with the EEC (106), AC (104), and the source data network for transmitting the application context related to the application services consumed by the UE (102) when switching from the first data network to the second data network.

[0048] The EEC (106) is configured to provide the support functions required by the AC (104). The functions of the EEC (106) include identifying that the UE (102) is present in one or more overlapping service regions, identifying the target data network closest to the UE (102), and initiating the transmission of the application context during the handover of the UE (102) from the first data network to the second data network. The EAS (110) is an application server residing in the EDN (108) that performs server functions.

[0049] In an embodiment, whenever the UE (102) moves from the source data network from which the UE is currently consuming application services (which may also be referred to as the "first data network") to a target data network (which may also be referred to as the "second data network") (the target data network will become the data network closest to the UE (102) within a short period of time or is already the data network closest to the UE (102)), the UE (102) traverses one or more overlapping service areas. Accordingly, during the handover of the UE (102) from the source data network to the target data network, the UE (102) is configured to determine that the UE (102) is present in one or more overlapping service areas. Based on the current location of the UE (102) (where the UE receives application services from both the first data network and the second data network), it is determined that the UE (102) is present in one or more overlapping service areas. Based on the determination that the UE (102) is present in one or more overlapping service areas, the UE (102) implements the guidelines associated with the corresponding overlapping service area. The UE (102) also notifies the corresponding source server, such as the first EES (112a), to initiate the transfer of the application context to the target data network according to the guidelines. In an embodiment, the area or location served by the data network (116 or 108) or the overlapping service area between the data networks (116 or 108) may be defined as but not limited to a geographical area or a list of cell identifiers (ID) or a list of tracking area identifiers (TAI) or a list of data network access identifiers (DNAI) or a combination thereof. In the case of cell ID, tracking area identifier (TAI), and data network access identifier (DNAI), the overlapping area may be determined as the list of cell IDs, the list of tracking area identifiers (TAI), and the list of data network access identifiers (DNAI) common to the target data networks (116 or 108).

[0050] In an embodiment, the service area is an application-specific service area and may or may not be directly related to the data network area. The service provider (122), together with the application provider, is responsible for designing the service area for the application such that, according to the service continuity requirements of the application, there is an overlap as described in the present invention. In addition, it should be noted that, for the sake of brevity, only one UE (102), one service provider (122), and one cloud data network (116) are shown in Figure 1 ; however, it is obvious to those of ordinary skill in the art that there may also be more than one UE (102), more than one service provider (122), and more than one cloud data network (116) in the system (100).

[0051] In an alternative embodiment, the UE (102) moves from the service area of an EAS (110a) from which the UE is currently consuming application services to the service area of an EAS (110a') that will soon be or is already the closest EAS to the UE (102), and the UE (102) passes through one or more overlapping service areas. Accordingly, during the handover of the UE (102) from the service area of the EAS (110a) to the service area of the EAS (110a'), the UE (102) is configured to determine that the UE (102) is present in one or more overlapping service areas. The determination that the UE (102) is present in one or more overlapping service areas is based on the current location of the UE (102) where the UE receives application services from both the EAS (110a) and the EAS (110a'). Based on the determination that the UE (102) is present in one or more overlapping service areas, the UE (102) implements the guidelines associated with the corresponding overlapping service areas. The UE (102) also notifies the corresponding source server, such as the first EAS (110a), to initiate the transfer of the application context to the EAS (110a') according to the guidelines.

[0052] In addition, Figures 3 - 14 details different steps involved in implementing guidelines including operating rules associated with each overlapping service area during the handover of the UE (102) from a source data network to a target data network to provide seamless service continuity. In addition, Figure 2A and Figure 2B further explain the drawbacks in existing systems due to the lack of understanding of the initiation time for capturing or transferring the application context during the handover of the UE (102) from a source data network to a target data network. Capturing the application context means that data related to the application context is collected and prepared for transfer, for example, by packing the data related to the application context into a specific format for transfer.

[0053] Figure 2A and Figure 2B show network environment scenarios (200) and (210) of the handover of the UE (102) from a first data network to a second data network according to the prior art.

[0054] The first data network and the second data network can be a cloud data network (116) or an edge data network (108). The UE (102) moves from the service area (202) of the first data network to the service area (204) of the second data network. Thus, the first data network is considered the source data network, and the second data network is considered the target data network. The service area (202) may also be referred to hereinafter as the "source service area (202)". The service area (204) may also be referred to hereinafter as the "target service area (204)".

[0055] In traditional methods, during the handover of the UE (102) from the source service area (402) to the target service area (204), two options are considered to initiate the capture and transfer of the application context. Option 1, where the capture and transfer of the application context are initiated when the UE is about to move to the target service area (204). Option 2, where the capture and transfer of the application context are initiated after the UE has moved to the target service area (204).

[0056] Figure 2A Illustrates the scenario (200) explained in Option 1, while Figure 2B Illustrates the scenario (210) explained in Option 2. Both Option 1 and Option 2 will provide a similar service experience because both options have the following problems: a) lack of understanding of exactly when to freeze the application context, because for seamless service continuity, the application context needs to be available at the target application server of the target data network before the UE (102) hands over to the target service area (204).

[0057] If the capture and transfer of the application context are initiated just before the AC (104) switches from the source application server of the source data network to the target application server, there is still uncertainty about: the exact time to initiate the capture and transfer of the application context, and what will happen to the service when the context is transferred considering that the size of the application context may be large for a particular application.

[0058] Furthermore, if the capture and transfer of the application context are initiated long before the AC (104) switches from the source application server to the target application server, there is still uncertainty about: a) the exact time to initiate the capture and transfer of the application context, b) whether the service continues after the application context is captured, or c) whether the captured context is updated at the source application server.

[0059] Similarly, if the application context is captured and transmitted just after the AC (104) switches from the source application server to the target application server, there remains uncertainty regarding whether the service continues at the source application server after the application context is transmitted, how the source application server knows that the AC (104) is switching, and whether any latency is caused and how the caused latency is handled (since it is important to handle latency correctly if the size of the application context is large).

[0060] Due to the above series of problems, there will be a significant lag in service continuity in the service, or in the worst case, service interruption may occur. For specific types of applications that require high reliability and uninterrupted service, the options listed above will not provide service continuity.

[0061] Accordingly, the solution proposed in the present invention overcomes the above problems in the traditional method and solves the problem of service lag or service interruption during the handover of the UE (102) from the source data network to the target data network.

[0062] Figure 3 A network environment scenario (300) is shown for transmitting an application context during a handover of a UE from a cloud data network (116) to a first EDN (108a) using an overlapping service area, according to an embodiment disclosed herein.

[0063] As Figure 3 shown, there is a non-overlapping service area (302) of the first EDN (108a), a non-overlapping service area (304) of the cloud data network (116), and two overlapping service areas (306 and 308) where the service is available from both the cloud data network (116) and the first EDN (108a).

[0064] In an embodiment, the UE (102) moves from the cloud data network (116) towards the first EDN (108a), which means that the source data network of the UE (102) is the cloud data network (116), and the target data network of the UE (102) is the first EDN (108a). When moving from the cloud data network (116) towards the first EDN (108a), the UE (102) first enters the first overlapping service area (306). The UE (102) determines that the current location of the UE (102) has changed from the non - overlapping service area (304) of the cloud data network (116) to the first overlapping service area (306). The UE (102) may obtain an input from the GPS unit of the UE (102) or the modem unit of the UE (102). In an alternative embodiment, the cloud AS (118) of the cloud data network (116) may also determine that the UE (102) is present in the first overlapping service area (306) based on determining that the UE (102) is at a first location where application services from both the cloud data network (116) and the first EDN (108a) are available. Based on the determination that the UE (102) is present in the first overlapping service area (306), the UE (102) executes one or more operation rules received from the ECS (114) associated with the first overlapping service area (306). In an embodiment, the one or more operation rules associated with the first overlapping service area (306) are: a) establish a connection between the EEC (106) and the first EES (112a) when the AC (104) is connected to the cloud AS (118), and b) initiate the capture of the application context of the application services running at the UE (102) for transmitting the application context to the target application server, which is the first EAS (110a) of the first EDN (108a). In other words, the UE (102) requests the cloud data network (116) to capture the application context of the application services running at the UE (102) in order to transmit the captured application context from the cloud data network (116) to the first EAS (110a) of the first EDN (108a).

[0065] In an embodiment, the UE (102) further moves from a first overlapping service area (306) to a second overlapping service area (308). Based on determining that the UE (102) is present in a second location where application services from both the cloud data network (116) and the first EDN (108a) are available, the UE (102) determines that the current location of the UE (102) has changed from the first overlapping service area (306) to the second overlapping service area (308). In an alternative embodiment, the cloud AS (118) of the cloud data network (116) may also determine that the UE (102) is present in the second overlapping service area (308). Based on the determination that the UE (102) is present in the second overlapping service area (308), the UE (102) executes one or more operation rules received from the ECS (114) associated with the second overlapping service area (308). In an embodiment, the one or more operation rules associated with the second overlapping service area (308) are: a) maintain the established connection of the EEC (106) with the first EES (112a), b) establish a connection of the AC (104) with the first EAS (110a), and c) initiate the transfer of the application context of the application service running at the UE (102) to a target application server, where the target application server is the first EAS (110a) of the first EDN (108a). In other words, the UE (102) requests the cloud data network (116) to transfer the captured application context to the first EAS (110a) of the first EDN (108a).

[0066] When the UE (102) enters the non-overlapping service area (302) of the EDN (108a) from the second overlapping service area (308), the UE (102) switches from the cloud data network (116) to the first EDN (108a), and the first EAS (110a) has received the application context required to seamlessly resume the application service running at the UE (102) to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the first EDN (108a), the first EES (112a) sends a message about the establishment of the connection of the UE (102) with the first EDN (108a) to the cloud data network (116), and correspondingly, the cloud AS (118) sends an end data packet or an end marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application service from the first EAS (110a).

[0067] Figure 4A A network environment scenario (400) for transferring application context during the handover of the UE from the second EDN (108b) to the first EDN (108a) using overlapping service areas according to embodiments disclosed herein is shown.

[0068] As Figure 4A shown, there are non - overlapping service areas (402) of the first EDN (108a), non - overlapping service areas (404) of the second EDN (108b), and two overlapping service areas (406 and 408) where services from both the first cloud data network and the EDN (108a) are available.

[0069] In an embodiment, the UE (102) moves from the second EDN (108b) to the first EDN (108a), which means that the source data network of the UE (102) is the second EDN (108b), and the target data network of the UE (102) is the first EDN (108a). When moving from the second EDN (108b) to the first EDN (108a), the UE (102) first enters the first overlapping service area (406). Based on determining that the UE (102) is in a first location where application services from both the cloud data network (116) and the edge data network (108a) are available, the UE (102) determines that its current location has changed from the non - overlapping service area (404) of the second EDN (108b) to the first overlapping service area (406). In an alternative embodiment, the second EES (112b) or the second EAS (110b) of the second EDN (108b) can also determine that the UE (102) is in the first overlapping service area (406). Based on the determination that the UE (102) is in the first overlapping service area (406), the UE (102) executes one or more operation rules received from the ECS (114) associated with the first overlapping service area (406). According to the embodiment, one or more operation rules associated with the first overlapping service area (406) are: a) establish a connection between the EEC (106) and the first EES (112a) of the first EDN (108a) together with the already established connection with the second EES (112b) of the second EDN (108b), while the AC (104) is connected to the second EAS (110b) of the second EDN (108b), and b) initiate the capture of the application context of the application services running at the UE (102) for transmitting the application context to the first EAS (110a) of the EDN (108a). In other words, the UE (102) requests the first EAS (110a’) to capture the application context of the application services running at the UE (102) in order to transmit the captured application context from the second EAS (110b) of the second EDN (108b) to the first EAS (110a) of the first EDN (108a).

[0070] In a first overlapping service area (406), the quality of service (QoS) of the application service provided by the second EAS (110b) of the second EDN (108b) is better than the QoS of the application service provided by the first EAS (110a) of the first EDN (108a). It should be noted that various factors may lead to better QoS of the application service of the second EAS (110b) of the second EDN (108b) in the first overlapping service area (406), such as but not limited to, the proximity distance between the UE (102) and the second EDN (108b) in the first overlapping service area (406) is less than the proximity distance between the UE (102) and the first EDN (108a), the data transmission rate provided by the second EDN (108b) in the first overlapping service area (406) is greater than the data transmission rate of the first EDN (108a), the signal-to-noise ratio (SNR) of the second EDN (108b) in the first overlapping service area (406) is less than the SNR of the first EDN (108a), and the network topology of the second EDN (108b) in the first overlapping service area (406) can provide better service than the network topology of the first EDN (108a).

[0071] In an embodiment, the UE (102) further moves from the first overlapping service area (406) to the second overlapping service area (408). Based on determining that the UE (102) is present in a second location where application services from both the cloud data network (116) and the edge data network (108a) are available, the UE (102) determines that the current location of the UE (102) has changed from the first overlapping service area (406) to the second overlapping service area (408). In an alternative embodiment, the second EES (112b) or the second EAS (110b) may also determine that the UE (102) is present in the second overlapping service area (408). Based on the determination that the UE (102) is present in the second overlapping service area (408), the UE (102) executes one or more operation rules received from the ECS (114) associated with the second overlapping service area (408). According to an embodiment, the one or more operation rules associated with the second overlapping service area (408) are: a) maintain the established connection between the EEC (106) and the first EES (112a) together with the established connection with the second EES (112b), b) establish a connection between the AC (104) and the first EAS (110a), and c) initiate the transfer of the application context of the application service running at the UE (102) to the first EAS (110a) of the EDN (108a). In other words, the UE (102) requests the second EAS (110b) to transfer the captured application context of the application service running at the UE (102) to the first EAS (110a) of the EDN (108a).

[0072] In the second overlapping service area (408), the QoS of the application service provided by the first EAS (110a) of the first EDN (108a) is better than the QoS of the application service provided by the second EAS (110b) of the second EDN (108b). It should be noted that various factors may lead to better QoS of the application service of the first EAS (110a) of the first EDN (108a) in the second overlapping service area (408), such as but not limited to, the proximity distance between the UE (102) and the first EDN (108a) in the second overlapping service area (408) is less than the proximity distance between the UE (102) and the second EDN (108b), the data transmission rate provided by the first EDN (108a) in the second overlapping service area (408) is greater than the data transmission rate of the second EDN (108b), the SNR of the first EDN (108a) in the second overlapping service area (408) is less than the SNR of the second EDN (108b), and the network topology of the first EDN (108a) in the second overlapping service area (408) can provide better services than the network topology of the second EDN (108b).

[0073] When the UE (102) enters the non - overlapping service area (402) of the EDN (108a) from the second overlapping service area (408), the UE (102) switches from the second EDN (108b) to the first EDN (108a), and the first EAS (110a) has received the application context required to seamlessly resume the application service running at the UE (102) so as to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the first EDN (108a), the first EES (112a) sends a message about the establishment of the connection of the UE (102) with the first EDN (108a) to the second EDN (108b), and correspondingly, the second EAS (110b) sends an end - of - data packet or end - of - marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application service from the first EAS (110a).

[0074] When the UE (102) is in the overlapping area, the process of transferring the application context from the source data network to the target data network should be a continuous process, that is, any change at the source application server (the application server to which the AC (104) is connected) should be immediately reflected in the target application server. There are many ways to achieve this, such as:

[0075] The source application server can imitate or forward requests from the AC (104) to the target application server and clear the responses from the target application server.

[0076] AC (104) can be connected to cloud AS (118) or EAS (110a, 110b... 110n), copy requests, and process responses from the source application server (decided based on operation rules associated with the overlapping service area).

[0077] The source application server can correspond to one of cloud AS (118) or EAS (110a, 110b... 110n), and the target application server can also correspond to one of cloud AS (118) or EAS (110a, 110b... 110n). However, the source application server should be a different server from the target application server.

[0078] Figure 4B A network environment scenario (420) for transmitting an application context during a handover of a UE from the service area of a first EAS (110a’) to the service area of a first EAS (110a) using an overlapping service area according to an embodiment disclosed herein is shown.

[0079] As Figure 4A shown, there is a non - overlapping service area (410) of the first EAS (110a), a non - overlapping service area (416) of the first EAS (110a’), and two overlapping service areas (412 and 414) where services of both the first EAS (110a) and the first EAS (110a’) from the first EDN (108a) are available. When the UE moves from the first EAS (110a’) to the first EAS (110a), the first EAS (110a’) is the source EAS (110a’), and the first EAS (110a) is the target EAS. Thus, the first EAS (110a’) can also be referred to as “source EAS (110a’)”, and the first EAS (110a) can also be referred to as “target EAS (110a)”.

[0080] In an embodiment, the UE (102) moves from a source EAS (110a’) to a target EAS (110a). When moving from the source EAS (110a’) to the target EAS (110a), the UE (102) first enters a first overlapping service area (412). Based on determining a first location in which application services from both the source EAS (110a’) and the target EAS (110a) are available, the UE (102) determines that its current location has changed from a non-overlapping service area (416) of the source EAS (110a’) to the first overlapping service area (412). In an alternative embodiment, the EES (112a) may also determine that the UE (102) is present in the first overlapping service area (412). Based on the determination that the UE (102) is present in the first overlapping service area (412), the UE (102) executes one or more operation rules received from the ECS (114) that are associated with the first overlapping service area (412). According to an embodiment, the one or more operation rules associated with the first overlapping service area (412) are: a) maintaining the connection of the AC (104) with the source EAS (110a’), and b) initiating the capture of the application context of the application services running at the UE (102) for transmitting the application context to the target EAS (110a). In other words, the UE (102) requests the first EAS (110a’) to capture the application context of the application services running at the UE (102) so as to transmit the captured application context from the first EAS (110a’) to the first EAS (110a).

[0081] In the first overlapping service area (412), the quality of service (QoS) of the application services provided by the source EAS (110a’) is better than the QoS of the application services provided by the target EAS (110a).

[0082] In an embodiment, the UE (102) further moves from the first overlapping service area (412) to the second overlapping service area (414). Based on determining that the UE (102) is present at a second location where application services from both the target EAS (110a) and the source EAS (110a') are available, the UE (102) determines that the current location of the UE (102) has changed from the first overlapping service area (412) to the second overlapping service area (414). Based on the determination that the UE (102) is present in the second overlapping service area (414), the UE (102) executes one or more operation rules received from the ECS (114) associated with the second overlapping service area (414). According to an embodiment, the one or more operation rules associated with the second overlapping service area (414) are: a) establish a connection between the AC (104) and the target EAS (110a), and b) initiate the transfer of the application context of the application service running at the UE (102) to the target EAS (110a). In other words, the UE (102) requests the first EAS (110a') to transfer the captured application context to the first EAS (110a).

[0083] In the second overlapping service area (414), the QoS of the application service provided by the target EAS (110a) is better than the QoS of the application service provided by the source EAS (110a'). It should be noted that various factors may result in better QoS of the application service of the target EAS (110a) in the second overlapping service area (414), such as, but not limited to, the proximity distance between the UE (102) and the target EAS (110a) in the second overlapping service area (414) being less than the proximity distance between the UE (102) and the source EAS (110a'), the data transfer rate provided by the target EAS (110a) in the second overlapping service area (414) being greater than the data transfer rate of the source EAS (110a'), the SNR of the target EAS (110a) in the second overlapping service area (414) being less than the SNR of the source EAS (110a'), and the network topology of the target EAS (110a) in the second overlapping service area (414) being able to provide better service than the network topology of the source EAS (110a').

[0084] When the UE (102) enters the non-overlapping service area (410) of the target EAS (110a) from the second overlapping service area (414), the UE (102) switches from the source EAS (110a') to the target EAS (110a), and the target EAS (110a) has received the application context required to seamlessly resume the application services running at the UE (102) so as to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the target EAS (110a), the first EES (112a) sends a message about the establishment of the connection of the UE (102) with the target EAS (110a) to the source EAS (110a'), and correspondingly, the source EAS (110a') sends an end data packet or an end marker packet to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application services from the target EAS (110a).

[0085] Figure 5 A network environment scenario (500) for transmitting an application context during a handover of a UE from a source EDN to a target EDN using an overlapping service area according to an embodiment disclosed herein is shown.

[0086] As Figure 5 shown, there are three edge data networks, a first EDN (108a), a second EDN (108b), and a third EDN (108c). Correspondingly, if the UE (102) moves from the third EDN (108c) to the first EDN (108a), the third EDN (108c) is considered the source EDN, and the first EDN (108a) is considered the target EDN. Similarly, if the UE (102) moves from the second EDN (108b) to the first EDN (108a), the second EDN (108b) is considered the source EDN, and the first EDN (108a) is considered the target EDN. Correspondingly, based on the connection with the UE (102), each of the first EDN (108a), the second EDN (108b), and the third EDN (108c) can be considered a source EDN or a target EDN.

[0087] Figure 5Shows the non-overlapping service areas (502) of the first EDN (108a), the non-overlapping service areas (504) of the second EDN (108b), the non-overlapping service areas (506) of the third EDN (108c), the first overlapping service area (508) and the second overlapping service area (510), the third overlapping service area (512) and the fourth overlapping service area (514), the fifth overlapping service area (516) and the sixth overlapping service area (518), and the seventh overlapping service area (520). In the first overlapping service area (508) and the second overlapping service area (510), the application service is available from both the first EDN (108a) and the third EDN (108c). In the third overlapping service area (512) and the fourth overlapping service area (514), the application service is available from both the first EDN (108a) and the second EDN (108b). In the fifth overlapping service area (516) and the sixth overlapping service area (518), the application service is available from both the third EDN (108c) and the second EDN (108b). In the seventh overlapping service area (520), the application service is available from the first EDN (108a), the second EDN (108b), and the third EDN (108c).

[0088] In an embodiment, the UE (102) moves from the service area (506) of the third EDN (108c) to the service area (502) of the first EDN (108a). When moving from the service area (506) of the third EDN (108c) to the service area (502) of the first EDN (108a), the UE (102) first enters the first overlapping service area (508). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non-overlapping service area (506) of the third EDN (108c) to the first overlapping service area (508). The AC (104) can obtain input from the GPS unit of the UE (102), or the EEC (106) of the UE (102) obtains input from the modem unit of the UE (102). The AC (104) of the UE (102) tracks the GPS position, and the EEC (106) of the UE (102) tracks whether the modem inputs together with the GPS position. The EEC (106) of the UE (102) can use the phone API to obtain the cell ID or tracking area ID, etc. In an alternative embodiment, the third EAS (110c) of the third EDN (108c) can also determine that the UE (102) is present in the first overlapping service area (508). Based on the determination that the UE (102) is present in the first overlapping service area (508), the UE (102) executes one or more operation rules associated with the first overlapping service area (508) received from (or can be pre-configured in the UE (102)) one of the ECS (114), the third EDN (108c). In an embodiment, one or more operation rules associated with the overlapping service area (508) are: a) establish a connection between the EEC (106) and the first EES (112a) of the first EDN (108a) in addition to the connection already established between the EEC (106) and the third EES (112c) of the third EDN (108c), while the AC (104) is connected to the third EAS (110c) of the third EDN (108c), and b) initiate the capture of the application context of the application service running at the UE (102) for transmitting the application context to the first EAS (110a) of the first EDN (108a).

[0089] In an embodiment, the UE (102) further moves from the first overlapping service area (508) to the second overlapping service area (510). The EEC (106) or the AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the first overlapping service area (508) to the second overlapping service area (510). In an alternative embodiment, the third EAS (110c) of the third EDN (108c) may also determine that the UE (102) is present in the second overlapping service area (510). Based on the determination that the UE (102) is present in the second overlapping service area (510), the UE (102) executes one or more operation rules associated with the second overlapping service area (510) received from the ECS (114), the third EDN (108c) (or may be pre-configured in the UE (102)). In an embodiment, the one or more operation rules associated with the second overlapping service area (510) are: a) maintain the established connection between the EEC (106) and the first EES (112a) of the first EDN (108a) together with the established connection with the third EES (112c) of the third EDN (108c), b) establish a connection between the AC (104) and the first EAS (110a), and c) initiate the transfer of the captured application context of the application service running at the UE (102) to the first EAS (110a) of the first EDN (108a).

[0090] When the UE (102) enters the non-overlapping service area (502) of the first EDN (108a) from the second overlapping service area (510), the UE (102) switches from the third EDN (108c) to the first EDN (108a), and the first EAS (110a) has received the application context required to seamlessly resume the application service running at the UE (102) so as to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the first EDN (108a), the first EES (112a) sends a message about the establishment of the connection of the UE (102) with the first EDN (108a) to the third EDN (108c), and in response to this message, the third EDN (108c) sends an end data packet or an end marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application service from the first EAS (110a).

[0091] In another embodiment, the UE (102) moves from the service area (504) of the second EDN (108b) to the service area (502) of the first EDN (108a). When moving from the service area (504) of the second EDN (108b) to the service area (502) of the first EDN (108a), the UE (102) first enters the third overlapping service area (512). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non-overlapping service area (504) of the second EDN (108b) to the third overlapping service area (512). In an alternative embodiment, the second EAS (110b) of the second EDN (108b) may also determine that the UE (102) is present in the third overlapping service area (512). Based on the determination that the UE (102) is present in the third overlapping service area (512), the UE (102) executes one or more operation rules associated with the third overlapping service area (512) received from (or pre-configured in the UE (102)) the ECS (114), the second EDN (108b). In an embodiment, the one or more operation rules associated with the third overlapping service area (512) are: a) establish a connection between the EEC (106) and the first EES (112a) in addition to the connection already established between the EEC (106) and the second EES (112b), while the AC (104) is connected to the second EAS (110b) of the second EDN (108b), and b) initiate the capture of the application context of the application service running at the UE (102) for transmitting the application context to the first EAS (110a) of the first EDN (108a).

[0092] The UE (102) further moves from the third overlapping service area (512) to the fourth overlapping service area (514). The EEC (106) or the AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the third overlapping service area (512) to the fourth overlapping service area (514). In an alternative embodiment, the second EAS (110b) or the second EES (112b) of the second EDN (108b) may also determine that the UE (102) is present in the fourth overlapping service area (514). Based on the determination that the UE (102) is present in the fourth overlapping service area (514), the UE (102) executes one or more operation rules associated with the fourth overlapping service area (514). According to an embodiment, the one or more operation rules associated with the fourth overlapping service area (514) are: a) maintaining the established connection between the EEC (106) and the first EES (112a) together with the connection already established with the second EES (112b), b) establishing a connection between the AC (104) and the first EAS (110a), and c) initiating the transfer of the application context of the application service running at the UE (102) to the first EAS (110a) of the first EDN (108a).

[0093] When the UE (102) enters the non-overlapping service area (502) of the first EDN (108a) from the fourth overlapping service area (514), the UE (102) switches from the second EDN (108b) (which may also be referred to as the "source EDN (108b)") to the first EDN (108a) (which may also be referred to as the "target EDN (108a)"). The first EAS (110a) has received the application context required to seamlessly resume the application service running at the UE (102) so as to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the first EDN (108a), the first EES (112a) sends a message about the establishment of the connection of the UE (102) with the first EDN (108a) to the second EDN (108b), and in response to this message, the second EDN (108b) sends an end data packet or an end marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application service from the first EAS (110a).

[0094] In another embodiment, the UE (102) moves from the service area (504) of the second EDN (108b) to the service area (506) of the third EDN (108c). When moving from the service area (504) of the second EDN (108b) to the service area (506) of the third EDN (108c), the UE (102) first enters the fifth overlapping service area (516). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non - overlapping service area (504) of the second EDN (108b) to the fifth overlapping service area (516). In an alternative embodiment, the second EAS (110b) of the second EDN (108b) may also determine that the UE (102) is present in the fifth overlapping service area (516). Based on the determination that the UE (102) is present in the fifth overlapping service area (516), the UE (102) executes one or more operating rules associated with the fifth overlapping service area (516). According to an embodiment, the one or more operating rules associated with the fifth overlapping service area (516) are: a) establish a connection between the EEC (106) and the third EES (112c) in addition to the already established connection between the EEC (106) and the second EES (112b), while the AC (104) is connected to the EAS (110b) of the second EDN (108b), and b) initiate the capture of the application context of the application services running at the UE (102) for transmitting the application context to the third EAS (110c) of the third EDN (108c).

[0095] The UE (102) further moves from the fifth overlapping service area (516) to the sixth overlapping service area (518). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the fifth overlapping service area (516) to the sixth overlapping service area (518). In an alternative embodiment, the second EAS (110b) of the second EDN (108b) may also determine that the UE (102) is present in the sixth overlapping service area (518). Based on the determination that the UE (102) is present in the sixth overlapping service area (518), the UE (102) executes one or more operating rules associated with the sixth overlapping service area (518). According to an embodiment, the one or more operating rules associated with the sixth overlapping service area (518) are: a) maintain the established connection between the EEC (106) and the third EES (112c) together with the already established connection with the second EES (112b), b) establish a connection between the AC (104) and the third EAS (110c), and c) initiate the transmission of the captured application context of the application services running at the UE (102) to the third EAS (110c) of the third EDN (108c).

[0096] When the UE (102) enters the non-overlapping service area (506) of the third EDN (108c) from the sixth overlapping service area (518), the UE (102) switches from the second EDN (108b) (which may also be referred to as the "source EDN (108b)") to the third EDN (108c) (which may also be referred to as the "target EDN (108c)"). The third EAS (110c) has received the application context required to seamlessly resume the application services running at the UE (102) so as to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the third EDN (108c), the third EES (112c) sends a message regarding the establishment of the connection of the UE (102) with the third EDN (108c) to the second EDN (108b), and in response to this message, the second EDN (108b) sends an end data packet or an end marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application services from the third EAS (110c).

[0097] In another embodiment, when the UE (102) is present in the seventh overlapping service area (520), the UE executes one or more operating rules associated with the seventh overlapping service area (520), and these operating rules are: a) connect the EEC (106) to the first EES (112a), the second EES (112b), and the third EES (112c); b) determine whether the UE (102) is from the first overlapping service area (508), and under this determination, maintain the connection between the AC (104) and the third EAS (110c) and initiate the capture and transmission of the application context with both the first EAS (110a) and the second EAS (110b); c) determine whether the UE (102) is from the second overlapping service area (510), and under this determination, maintain the connection between the AC (104) and the first EAS (110a) and initiate the capture and transmission of the application context with both the second EAS (110b) and the third EAS (110c); d) determine whether the UE (102) is from the third overlapping service area (512), and under this determination, maintain the connection between the AC (104) and the second EAS (110b) and initiate the capture and transmission of the application context with both the third EAS (110c) and the first EAS (110a); e) determine whether the UE (102) is from the fourth overlapping service area (514), and under this determination, maintain the connection between the AC (104) and the first EAS (110a) and initiate the capture and transmission of the application context with both the second EAS (110b) and the third EAS (110c); f) determine whether the UE (102) is from the fifth overlapping service area (516), and under this determination, maintain the connection between the AC (104) and the second EAS (110b) and initiate the capture and transmission of the application context with both the first EAS (110a) and the third EAS (110c); and g) determine whether the UE (102) is from the sixth overlapping service area (518), and under this determination, maintain the connection between the AC (104) and the third EAS (110c) and initiate the capture and transmission of the application context with both the first EAS (110a) and the second EAS (110b). In addition, when the UE (102) moves to any one of the non-overlapping service areas (502) of the first EDN (108a), the non-overlapping service area (504) of the second EDN (108b), or the non-overlapping service area (506) of the third EDN (108c), the target EAS of the target EDN corresponding to the non-overlapping area where the UE moves has received the application context related to the application service running in the UE (102) to seamlessly resume the application service, thereby providing the user with a seamless service continuity experience.

[0098] It should be noted that the two overlapping service areas between two edge data networks (108) or between the cloud data network (116) and an edge data network (108) are shown for illustrative purposes only, and one of ordinary skill in the art will understand that fewer or more than two overlapping service areas may also be deployed between two edge data networks (108), or between the cloud data network (116) and an edge data network (108). Figure 6 and Figure 7 An illustrative example of a UE (102) switching between data networks with a single overlapping service area is shown in Figure 7 .

[0099] Figure 6 Another network environment scenario (600) for transferring an application context during a handover of a UE from the cloud data network (116) to a first EDN (108a) using a single overlapping service area, in accordance with embodiments disclosed herein, is shown in Figure 6 .

[0100] As Figure 6 shown, there is a non - overlapping service area (602) of the first EDN (108a), a non - overlapping service area (606) of the cloud data network (116), and an overlapping service area (604) in which services from both the cloud data network (116) and the first EDN (108a) are available.

[0101] In an embodiment, the UE (102) moves from the service area (606) of the cloud data network (116) to the service area (602) of the first EDN (108a), which means that the source data network of the UE (102) is the cloud data network (116), and the target data network of the UE (102) is the first EDN (108a). When moving from the cloud data network (116) to the first EDN (108a), the UE (102) enters the overlapping service area (604). The UE (102) determines that the current location of the UE (102) has changed from the non-overlapping service area (606) of the cloud data network (116) to the overlapping service area (604). In an alternative embodiment, the cloud AS (118) of the cloud data network (116) may also determine that the UE (102) is present in the overlapping service area (604). Based on the determination that the UE (102) is present in the overlapping service area (604), the UE (102) executes one or more operation rules received from the ECS (114) associated with the overlapping service area (604). According to the embodiment, the one or more operation rules associated with the overlapping service area (604) are: a) establish a connection between the EEC (106) and the first EES (112a), while the AC (104) is connected to the cloud AS (118), b) establish a connection between the AC (104) and the first EAS (110a), while maintaining the connection between the AC (104) and the cloud AS (118), and b) initiate the capture and transmission of the application context of the application service running at the UE (102) for transmitting the application context to the target application server, where the target application server is the first EAS (110a) of the first EDN (108a). In other words, the UE (102) requests the cloud AS (110) to capture the application context of the application service running at the UE (102) and transmit the captured application context to the first EAS (110a) of the first EDN (108a).

[0102] When the UE (102) enters the non-overlapping service area (602) of the first EDN (108a) from the overlapping service area (604), the UE (102) switches from the cloud data network (116) to the first EDN (108a), and the first EAS (110a) has received the application context required to seamlessly resume the application services running at the UE (102) to provide the user with a seamless service continuity experience. In addition, when the UE (102) switches to the EDN (108a), the first EES (112a) sends a message to the cloud data network (116) regarding the establishment of the connection of the UE (102) with the first EDN (108a), and correspondingly, the cloud AS (118) sends an end data packet or an end marker packet related to the application service to the AC (104), and disconnects the connection with the AC (104) of the UE (102). The UE (102) continues to utilize the application services from the first EAS (110a).

[0103] Figure 7 A network environment scenario (700) for transmitting application context during the handover of a UE from a source EDN to a target EDN (using a single overlapping service area between the source EDN and the target EDN) according to an embodiment disclosed herein is shown.

[0104] As Figure 7 shown, there are three edge data networks, the first EDN (108a), the second EDN (108b), and the third EDN (108c). Correspondingly, if the UE (102) moves from the third EDN (108c) to the first EDN (108a), the third EDN (108c) is considered the source EDN, and the first EDN (108a) is considered the target EDN. Similarly, if the UE (102) moves from the second EDN (108b) to the first EDN (108a), the second EDN (108b) is considered the source EDN, and the first EDN (108a) is considered the target EDN. Correspondingly, based on the connection with the UE (102), each of the first EDN (108a), the second EDN (108b), and the third EDN (108c) can be considered a source EDN or a target EDN.

[0105] Figure 7Shows the non-overlapping service areas (702) of the first EDN (108a), the non-overlapping service areas (704) of the second EDN (108b), the non-overlapping service areas (706) of the third EDN (108c), the first overlapping service area (708), the second overlapping service area (710), the third overlapping service area (712), and the fourth overlapping service area (714). In the first overlapping service area (708), the application service is available from both the first EDN (108a) and the second EDN (108b). In the second overlapping service area (710), the application service is available from both the third EDN (108c) and the second EDN (108b). In the third overlapping service area (712), the application service is available from both the third EDN (108c) and the first EDN (108a). In the fourth overlapping service area (714), the application service is available from the first EDN (108a), the second EDN (108b), and the third EDN (108c).

[0106] In an embodiment, the UE (102) moves from the service area (706) of the third EDN (108c) to the service area (702) of the first EDN (108a). When moving from the service area (706) of the third EDN (108c) to the service area (702) of the first EDN (108a), the UE (102) enters the third overlapping service area (712). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non-overlapping service area (706) of the third EDN (108c) to the third overlapping service area (712). In an alternative embodiment, the third EAS (110c) of the third EDN (108c) may also determine that the UE (102) is present in the third overlapping service area (712). Based on the determination that the UE (102) is present in the third overlapping service area (712), the UE (102) executes one or more operation rules associated with the third overlapping service area (712). In an embodiment, one or more operation rules associated with the third overlapping service area (712) are: a) establish a connection between the EEC (106) and the first EES (112a) of the first EDN (108a) in addition to the connection already established between the EEC (106) and the third EES (112c) of the third EDN (108c), and b) initiate the capture and transfer of the application context of the application service running at the UE (102) to the first EAS (110a) of the first EDN (108a). One or more operation rules associated with the third overlapping service area (712) also include: a) determine whether the UE is entering the third overlapping service area (712) from the fourth overlapping service area (714), b) when it is determined that the UE is entering from the fourth overlapping service area (714), establish a connection between the AC (104) and the first EAS (110a) of the first EDN (108a) while the AC (104) is connected to the third EAS (110c) of the third EDN (108c), and c) initiate the capture and transfer of the application context between the third EAS (110c) of the third EDN (108c) and the first EAS (110a) of the first EDN (108a).

[0107] In another embodiment, the UE (102) moves from the service area (704) of the second EDN (108b) to the service area (702) of the first EDN (108a). When moving from the service area (704) of the second EDN (108b) to the service area (702) of the first EDN (108a), the UE (102) enters the first overlapping service area (708). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non - overlapping service area (704) of the second EDN (108b) to the first overlapping service area (708). In an alternative embodiment, the second EAS (110b) of the second EDN (108b) may also determine that the UE (102) is present in the first overlapping service area (708). Based on the determination that the UE (102) is present in the first overlapping service area (708), the UE (102) executes one or more operation rules associated with the first overlapping service area (708). In an embodiment, the one or more operation rules associated with the first overlapping service area (708) are: a) establish a connection between the EEC (106) and the first EES (112a) of the first EDN (108a) in addition to the connection already established between the EEC (106) and the second EES (112b) of the second EDN (108b), and b) initiate the capture and transfer of the application context of the application service running at the UE (102) to the first EAS (110a) of the first EDN (108a). The one or more operation rules associated with the first overlapping service area (708) further include: a) determine whether the UE is entering the first overlapping service area (708) from the fourth overlapping service area (714), b) when it is determined that the UE is entering from the fourth overlapping service area (714), establish a connection between the AC (104) and the first EAS (110a) of the first EDN (108a) while the AC (104) is connected to the second EAS (110b) of the second EDN (108b), and initiate the capture and transfer of the application context between the second EAS (110b) of the second EDN (108b) and the first EAS (110a) of the first EDN (108a).

[0108] In another embodiment, the UE (102) moves from the service area (704) of the second EDN (108b) to the service area (706) of the third EDN (108c). When moving from the service area (704) of the second EDN (108b) to the service area (706) of the third EDN (108c), the UE (102) enters the second overlapping service area (710). The EEC (106) or AC (104) of the UE (102) determines that the current location of the UE (102) has changed from the non-overlapping service area (704) of the second EDN (108b) to the second overlapping service area (710). In an alternative embodiment, the second EAS (110b) of the second EDN (108b) may also determine that the UE (102) is present in the second overlapping service area (710). Based on the determination that the UE (102) is present in the second overlapping service area (710), the UE (102) executes one or more operation rules associated with the second overlapping service area (710). According to an embodiment, the one or more operation rules associated with the second overlapping service area (710) are: a) establish a connection between the EEC (106) and the third EES (112c) of the third EDN (108c) in addition to the connection already established between the EEC (106) and the second EES (112b) of the second EDN (108b), and b) initiate the capture and transfer of the application context of the application service running at the UE (102) to the third EAS (110c) of the third EDN (108c). The one or more operation rules associated with the second overlapping service area (710) further include: a) determine whether the UE is entering the second overlapping service area (710) from the fourth overlapping service area (714), b) when it is determined that the UE is entering from the fourth overlapping service area (714), establish a connection between the AC (104) and the third EAS (110c) of the third EDN (108c) while the AC (104) is connected to the second EAS (110b) of the second EDN (108b), and initiate the capture and transfer of the application context between the second EAS (110b) of the second EDN (108b) and the third EAS (110c) of the third EDN (108c).

[0109] In another embodiment, when the UE (102) is present in the fourth overlapping service area (714), the UE executes one or more operating rules associated with the fourth overlapping service area (714), and these operating rules are: a) connect the EEC (106) with the first EES (112a) of the first EDN (108a), the second EES (112b) of the second EDN (108b), and the third EES (112c) of the third EDN (108c); b) establish a connection between the AC (104) and at least one of the first EAS (110a) of the first EDN (108a), the second EAS (110b) of the second EDN (108b), or the third EAS (110c) of the third EDN (108c), or continue the connection between the AC (104) and the source EAS of the source EDN; and c) initiate the capture and transmission of the application context of the first EAS (110a) of the first EDN (108a), the second EAS (110b) of the second EDN (108b), or the third EAS (110c) of the third EDN (108c). Therefore, when the UE (102) moves to any one of the non-overlapping service areas (702) of the first EDN (108a), the non-overlapping service areas (704) of the second EDN (108b), or the non-overlapping service areas (706) of the third EDN (108c), the target EAS of the target EDN has received the application context related to the application service running in the UE (102) to seamlessly resume the application service, thereby providing the user with a seamless service continuity experience.

[0110] Figure 8A and Figure 8B collectively show a sequence diagram representing a method (800) for providing seamless service continuity in a distributed wireless network system (100) during a handover of a UE from a first EDN (108a) to a second EDN (108b) according to an embodiment disclosed herein.

[0111] According to an embodiment of the present disclosure, the UE (102) travels from the first EDN (108a) to the second EDN (108b) and executes the method (800) to achieve seamless service continuity for the UE during the handover from the first EDN (108a) to the second EDN (108b). Accordingly, the first EDN (108a) is the source EDN of the UE (102) because the UE (102) is currently connected to the first EDN (108a), and the second EDN (108b) is the target EDN of the UE (102) because the UE (102) will be connected to the second EDN (108b) within a short period of time.

[0112] At step 802, the UE (102) receives application service availability information from the EES (112a) of the first EDN (108a) via the EEC (106). At step 804, the UE (102) receives application data packets related to the application service being consumed by the UE (102) from the EAS (110a) of the first EDN (108a) via the AC (104). At step 806, the UE (102) receives EDN service availability information of the second EDN (108b) from the ECS (114) via the EEC (106). At step 808, the UE (102) determines that the application service is available via both the first EDN (108a) and the second EDN (108b) based on the received application service availability information and EDN service availability information. At step 810, the UE (102) detects that the UE (102) is present in an overlapping service area based on the determination that both the first EDN (108a) and the second EDN (108b) in the current location of the UE (102) provide the application service running at the UE (102). At step 812, when it is determined that the UE (102) is present in the overlapping service area, the UE (102) notifies the ECS (114) via the EEC (106) that the UE is present in the overlapping service area. At step 814, the ECS (114) sends one or more operation rules associated with the overlapping service area to the UE (102). At step 816, the UE (102) executes the received one or more operation rules associated with the overlapping service area on the UE (102) to achieve seamless service continuity when switching from the first EDN (108a) to the second EDN (108b). Alternatively, one or more operation rules related to the overlapping service area can be pre-configured into the UE (102) or in the data network, and thus eliminate the need for steps 812 and 814.

[0113] At step 816, the execution of one or more operation rules includes steps 818 - 838. At step 818, the UE (102) sends a connection request to the second EES (112b) of the second EDN (108b) via the EEC (106). At 820, the second EES (112b) of the second EDN (108b) sends an acceptance of the connection request to the UE (102). In an alternative embodiment, if the EEC has a prior connection with the second EES (112b) of the second EDN (108b), steps 818 and 820 are skipped. At 822, the UE (102) notifies the first EES (112a) of the first EDN (108a) about the connection with the second EES (112b) of the second EDN (108b), and receives an acknowledgement from the first EES (112a) of the first EDN (108a). In an alternative embodiment, the EEC (106) of the UE (102) notifies the AC (104) of the UE (102) about the connection with the second EES (112b) of the second EDN (108b).

[0114] At step 824, when receiving a notification from the UE (102), the first EES (112a) of the first EDN (108a) requests the first EAS (110a) of the first EDN (108a) to capture the application context of the application service running at the first EAS (110a). In other words, the first EES (112a) of the first EDN (108a) initiates the capture of the application context of the application service running at the first EAS (110a) by triggering the first EAS (110a) of the first EDN (108a). In an alternative embodiment, the AC (104) of the UE (102) initiates the capture of the application context of the application service running at the first EAS (110a) of the first EDN (108a) by triggering the first EAS (110a) of the first EDN (108a). In other words, the AC (104) of the UE (102) requests the first EAS (110a) of the first EDN (108a) to capture the application context of the application service running at the first EAS (110a). At step 826, the first EAS (110a) of the first EDN (108a) transmits the application context to the second EAS (110b) of the second EDN (108b). At step 828, upon successfully receiving the application context, the second EAS (110b) of the second EDN (108b) sends an acknowledgment indicating the receipt of the application context to the first EAS (110a) of the first EDN (108a). At step 830, the first EES (112a) of the first EDN (108a) sends a context transfer completion notification to the EEC (106) of the UE (102). At step 832, the AC (104) of the UE (102) switches from the first EAS (110a) of the first EDN (108a) to the second EAS (110b) of the second EDN (108b). At step 834, the second EAS (110b) of the second EDN (108b) notifies the first EAS (110a) of the first EDN (108a) of the establishment of the connection with the UE (102). At step 836, upon receiving the notification from the second EAS (110b) of the second EDN (108b), the first EAS (110a) of the first EDN (108a) sends an end data packet or an end marker packet to the AC (104) of the UE (102) and disconnects the connection with the AC (104) of the UE (102). At step 838, the UE (102) continues to utilize the application service from the second EAS (110b) of the second EDN (108b).

[0115] In an alternative embodiment, steps 824 - 836 may be performed without the participation of the UE (102), but based on the first EES (112a) and the first EDN (108a), it is determined that the UE (102) is located at a position where both the first EDN (108a) and the second EDN (108b) provide services to the UE (102).

[0116] Accordingly, based on the UE being present in the overlapping service area, one or more operation rules to be followed by the UE are configured, providing a better understanding to the source EDN and the target EDN of when and how to initiate the capture and transfer of the application context, such that when the UE (102) enters the target EDN, the application context already exists for resuming the application services running at the UE (102). Thus, during the handover of the UE (102) from the source EDN (which is the first EDN (108a)) to the target EDN (which is the second EDN (108b)), no significant service latency or service interruption occurs.

[0117] Figure 9 A component diagram of a UE (900) for utilizing seamless service continuity during handover of the UE (900) from a source data network to a target data network according to an embodiment disclosed herein is shown. The UE (900) is Figure 1 an example of the UE (102) shown in

[0118] The UE (900) includes a processor (905), a communication interface (910), a memory (915), an edge-aware application (920), an edge-enabled client (EEC) (925) associated with the edge-aware application (920), and an application client (AC) (930) associated with the edge-aware application (920), as well as a context transfer controller (935). The components of the UE (900) provided herein may not be exhaustive, and the UE (900) may include more or fewer components than Figure 9 those depicted. Additionally, two or more components may be embodied in a single component, and / or a component may be configured using multiple sub-components to achieve the desired functionality. Some components of the UE (900) may be configured using hardware elements, firmware elements, and / or combinations thereof.

[0119] The processor (905) is coupled to a memory (915), a communication interface (910), a context transfer controller (935), an edge awareness application (920), an EEC (925), and an AC (930). The processor (905) is configured to execute instructions stored in the memory (915) and perform various processes. The communication interface (910) is configured for internal communication between internal hardware components and with external devices via one or more networks. The communication interface (910) may be referred to as a transceiver. The AC (930) is Figure 1 an example of the AC (104) in Figure 1 and the EEC (925) is an example of the EEC (106) in

[0120] The processor (905) may include one or more processing units (e.g., in a multi-core configuration).

[0121] The memory (915) stores instructions to be executed by the processor (905). The memory (915) may include non-volatile storage elements. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or in the form of an electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (915) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (915) is immovable. In some examples, the memory (915) may be configured to store a larger amount of information than memory. In a particular example, the non-transitory storage medium may store data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0122] In an embodiment, before the UE (900) switches to the second EDN (108b), the EEC (925) and the AC (930) are initially connected to the first EDN (108a). After the UE (900) switches to the second EDN (108b), the EEC (925) and the AC (930) are connected to the second EDN (108b).

[0123] In an embodiment, the processor (905) is configured to determine a change in the current location of the UE (900). The processor (905) is further configured to determine, with the help of the EEC (925) or the AC (930), that the UE (900) is moving from the service area of a first EDN (108a) to the service area of a second EDN (108b). Alternatively, the processor (905) is further configured to determine, with the help of the EEC (925) or the AC (930), that the UE (900) is moving from the service area of a first EAS (110a’) to the service area of a first EAS (110a) within the same EDN (108a). Upon this determination, the processor (905) sends a context transfer initiation request to the context transfer controller (935). Upon receiving the request from the processor (905), the context transfer controller (935) determines whether the UE (900) is present in an overlapping service area among one or more overlapping service areas between the first EDN (108a) and the second EDN (108b), or in the overlapping service area between the first EAS (110a) and the first EAS (110a’). Based on the UE (900) being present in the overlapping service area, the context transfer controller (935) executes one or more operation rules associated with the overlapping service area. The context transfer controller (935) also determines the Internet Protocol (IP) address of the second EDN (108b) and starts transferring the application context related to the edge-aware application (920) running at the UE (900). The context transfer controller (935) is further configured to manage the connections of the EEC (925) and the AC (930) with the first EDN (108a) and the second EDN (108b) based on one or more operation rules associated with the overlapping service area. The context transfer controller (935) is further configured to notify the AC (930) about the connection of the UE (900) to the second EDN (108b) or to the target EAS (110a), and accordingly instruct the first EDN (108a) to send an end data packet or an end marker packet to the AC (104) and disconnect the connection of the AC (104) with the UE (102).

[0124] Figure 10 The component diagram of an edge configuration server (ECS) (1000) for providing seamless service continuity during the handover of a UE (102) from a source data network to a target data network according to an embodiment disclosed herein is shown. The ECS (1000) is Figure 1 an example of the ECS (114) shown.

[0125] The ECS (1000) includes a processor (1002), a communication interface (1006), a memory (1004), a service area configuration controller (1008), and a service area configuration database (1010). The components of the ECS (1000) provided herein may not be exhaustive, and the ECS (1000) may include more or fewer components than Figure 10 depicted in. Additionally, two or more components may be embodied in a single component, and / or one component may be configured using multiple sub-components to achieve the desired functionality. Some components of the ECS (1000) may be configured using hardware elements, firmware elements, and / or combinations thereof.

[0126] The processor (1002) is coupled to the memory (1004), the communication interface (1006), the service area configuration controller (1008), and the service area configuration database (1010). The processor (1002) is configured to execute instructions stored in the memory (1004) and perform various processes. The communication interface (1006) is configured for internal communication between internal hardware components and for communication with external devices via one or more networks. The communication interface (1006) may be referred to as a transceiver.

[0127] The processor (1002) may include one or more processing units (e.g., in a multi-core configuration).

[0128] The memory (1004) stores instructions to be executed by the processor (1002). The memory (1004) may include non-volatile storage elements. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or the form of an electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (1004) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (1004) is non-removable. In some examples, the memory (1004) may be configured to store a larger amount of information than memory. In a particular example, the non-transitory storage medium may store data that may change over time (e.g., in random access memory (RAM) or a cache).

[0129] The processor (1002) may also be operatively coupled to a service area configuration database (1010). The database (1010) is any computer-operated hardware suitable for storing and / or retrieving data. The database (1010) may include, but is not limited to, a storage area network (SAN) and / or a network attached storage (NAS) system. In other embodiments, the database (1010) may be external to the ECS (1000) and may be accessed by the ECS (1000) using a storage interface. A storage interface is any component capable of providing access to the database (1010) to the processor (1002).

[0130] In an embodiment, the processor (1002) is configured to receive a data network connection request from the UE (102) and is further configured to present details of the most recently available data network hosting the application services required by the UE (102). In an embodiment, the processor (1002) is further configured to store details of all data networks in the memory (1004) and also store details of the service areas between the data networks in the service area configuration database (1010). The processor (1002) is further configured to send one or more operation rules related to overlapping service areas to the UE (102) via the service area configuration controller (1008).

[0131] Embodiments disclosed herein may be implemented using at least one hardware device and performing network management functions to control elements.

[0132] Figure 11 A component diagram of an edge enabled server (EES) (1100) for providing seamless service continuity during a handover of the UE (102) from a source data network to a target data network, according to embodiments disclosed herein, is shown. When the EDN (108a) acts as the source data network, the EES (1100) is an example of a first EES (112a) of the first EDN (108a).

[0133] The EES (1100) includes a processor (1102), a communication interface (1106), a memory (1104), an application service management controller (1110), and a context transfer controller (1108). The components of the EES (1100) provided herein may not be exhaustive, and the EES (1100) may include more or fewer components than those Figure 11 depicted. Additionally, two or more components may be embodied in a single component, and / or one component may be configured using multiple sub-components to achieve the desired functionality. Some components of the EES (1100) may be configured using hardware elements, firmware elements, and / or combinations thereof.

[0134] A processor (1102) is coupled to a memory (1104), a communication interface (1106), an application service management controller (1110), and a context transfer controller (1108). The processor (1102) is configured to execute instructions stored in the memory (1104) and perform various processes. The communication interface (1106) is configured to communicate internally between internal hardware components and with external devices via one or more networks. The communication interface (1106) may be referred to as a transceiver.

[0135] The processor (1102) may include one or more processing units (e.g., in a multi-core configuration).

[0136] The memory (1104) stores instructions to be executed by the processor (1102). The memory (1104) may include non-volatile storage elements. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or the form of an electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (1030) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (1104) is immovable. In some examples, the memory (1104) may be configured to store a larger amount of information than memory. In a particular example, the non-transitory storage medium may store data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0137] In an example embodiment, the EES (1100) may act as a source EES in a source edge data network of a UE (102) that hosts multiple EASs (110a - 110n). To facilitate the EES function as a source EES, the processor (1002) is configured to receive registration requests from multiple EASs (110) via the communication interface (1120). The received registration requests are authenticated by the processor (1102) for secure data communication. Upon successful authentication, the EASs (110a - 110n) register with the EES (1100). The processor (1102) is also configured to instruct to store the registration details of the EASs (110a - 110n). The registration details of the EASs (110a - 110n) include a list of service areas served by the EASs (110a - 110n), the locations of the EASs (110a - 110n), the registration information of the EASs (110a - 110n) with the source EES, the availability information of the EASs (110a - 110n), and the identifiers of the EASs (110a - 110n).

[0138] The application service management controller (1110) is configured to obtain different parameters related to each application service associated with the EES (1100), such as the bandwidth requirement of the application service, the size of the application context of the application service, and the like.

[0139] In an embodiment, the processor (1102) is configured to determine the movement of the UE (102) from the service area of the first EDN (108a) to the service area of the second EDN (108b). In response to this determination, the processor (1102) sends a context transfer initiation request to the context transfer controller (1108). Upon receiving the request from the processor (1102), the context transfer controller (1108) determines whether the UE (102) is present in an overlapping service area among one or more overlapping service areas between the first EDN (108a) and the second EDN (108b). Based on the UE (102) being present in the overlapping service area, the context transfer controller (1108) executes one or more operation rules associated with the overlapping service area provided by the UE (102). The context transfer controller (1108) also determines the Internet Protocol (IP) address of the second EDN (108b) and starts transferring the application context related to the application service running at the UE (102). The context transfer controller (1108) is also configured to notify the EEC (925) about the connection of the UE (102) to the second EDN (108b). The context transfer controller (1108) is also configured to instruct the first EAS (110a) of the first EDN (108a) to send an end data packet or an end marker packet to the AC (104) and disconnect the connection with the AC (104) accordingly.

[0140] Embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control elements.

[0141] Figure 12 A component diagram of an edge application server (EES) (1200) for providing seamless service continuity during the handover of a UE (102) from a source data network to a target data network according to embodiments disclosed herein is shown. When the EDN (108a) is the source data network, the EAS (1200) is an example of the EAS (110a) of the first EDN (108a).

[0142] The EAS (1200) includes a processor (1202), a communication interface (1206), a memory (1204), an application service management controller (1210), and a context transfer controller (1208). The components of the EAS (1200) provided herein may not be exhaustive, and the EAS (1200) may include more than Figure 11More or fewer components than those depicted. Additionally, two or more components may be embodied in a single component, and / or a component may be configured using multiple sub-components to achieve the desired functionality. Some components of the EAS (1200) may be configured using hardware elements, firmware elements, and / or combinations thereof.

[0143] The processor (1202) is coupled to the memory (1204), the communication interface (1206), the application service management controller (1210), and the context transfer controller (1208). The processor (1202) is configured to execute instructions stored in the memory (1204) and perform various processes. The communication interface (1206) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The communication interface (1206) may be referred to as a transceiver.

[0144] The processor (1202) may include one or more processing units (e.g., in a multi-core configuration).

[0145] The memory (1204) stores instructions to be executed by the processor (1202). The memory (1204) may include non-volatile storage elements. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or in the form of an electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (1030) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (1204) is non-removable. In some examples, the memory (1204) may be configured to store a larger amount of information than memory. In a particular example, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0146] In an example embodiment, the EAS (1200) may act as a source EAS in the source edge data network of the UE (102). To facilitate the EAS function as a source EAS, the processor (1202) is configured to connect to the AC (104) of the UE (102) and send an application context for an application service running on the UE (102).

[0147] The application service management controller (1210) is configured to obtain different parameters related to each UE (102) and EES (1200) associated with the EAS (1200), such as the Internet Protocol (IP) address of the most recent EDN or the IP address of the UE (102), or the IP address of the EDN (108) connected to the EAS (1200), the service area of the EDN (108), the overlapping service area between the EDNs (108), and so on.

[0148] In an embodiment, the processor (1202) is configured to determine the movement of the UE (102) from the service area of the first EDN (108a) to the service area of the second EDN (108b). In response to this determination, the processor (1202) sends a context transfer initiation request to the context transfer controller (1208). Upon receiving the request from the processor (1202), the context transfer controller (1208) determines whether the UE (102) is present in an overlapping service area among one or more overlapping service areas between the first EDN (108a) and the second EDN (108b). This determination can be based on an explicit indication received from the AC (104) or the EES (112). Based on the presence of the UE (102) in the overlapping service area or the received indication, the context transfer controller (1208) executes one or more operation rules associated with the overlapping service area provided by the UE (102). The context transfer controller (1208) further determines the (IP) address of the second EDN (108b) and starts transmitting the application context related to the application service running at the UE (102). The context transfer controller (1208) may also be configured to notify the AC (930) about the connection of the UE (102) to the second EDN (108b). The context transfer controller (1208) is also configured to send an end data packet or an end marker packet to the second EAS (110b) AC (104) and disconnect the connection with the AC (104) accordingly.

[0149] Embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control elements.

[0150] Figure 13A and Figure 13B collectively show a flowchart of a method (1300) for providing seamless service continuity during a handover of a UE (102) from a source data network to a target data network according to embodiments disclosed herein.

[0151] At S1302, method (1300) includes facilitating a service provider (122) to deploy one or more overlapping service areas between a first data network and a second data network. In an example embodiment, the first data network and the second data network may correspond to a cloud data network (116) and an edge data network (108a - 108n). Alternatively, the first data network may also correspond to the service area of a source EAS (110a’), and the second data network may correspond to the service area of a target EAS (110a).

[0152] At S1304, method (1300) includes an ECS (114) defining one or more operation rules for each of the one or more deployed overlapping service areas.

[0153] At S1306, method (1300) includes an ECS (114) configuring one or more operation rules in a UE (102). The operation rules may be pre - configured in the UE (102), or may be configured in the UE (102) based on a request received from the UE (102).

[0154] At S1308, method (1300) includes a UE (102) receiving an application service from the first data network.

[0155] At S1310, method (1300) includes a UE (102), or an application server of the first data network (such as a cloud AS (118) or an EAS (110a - 110n)), or an EES (112) determining a movement of the UE (102) from a service area of the first data network to a service area of the second data network.

[0156] At S1312, method (1300) includes a UE (102), or an application server of the first data network, or an EES (112) determining that the UE (102) is present in one or more overlapping service areas between the first data network and the second data network based on a determination that the UE is in a location where application services are provided by both the first data network and the second data network.

[0157] At S1314, method (1300) includes a UE (102) executing one or more operation rules associated with a configured overlapping service area that the UE (102) has moved into when switching from the first data network to the second data network.

[0158] At S1316, method (1300) includes capturing an application context related to an application service being provided to UE (102) by an application server (Cloud AS (118) or EAS (110)) of a first data network or by UE (102) or by EES (112).

[0159] At S1318, method (1300) includes connecting AC (104) to an application server (Cloud AS (118) or EAS (110)) of a second data network by UE (102) based on a determination that the second data network provides better QoS.

[0160] At S1320, method (1300) includes initiating transmission of the captured application context related to the application service running at UE (102) to an application server (Cloud AS (118) or EAS (110)) of a second data network by UE (102) or by an application server (Cloud AS (118) or EAS (110)) of a first data network.

[0161] At S1322, method (1300) includes disconnecting AC (104) from an application server (Cloud AS (118) or EAS (110)) of a first data network by UE (102) upon successful transmission of the application context.

[0162] In an alternative embodiment, steps S1318 and S1320 may occur in parallel or in the reverse order.

[0163] At S1324, method (1300) includes UE (102) continuing the application service from the second data network.

[0164] The various actions, behaviors, blocks, steps, etc. in method (1300) in the flowchart may be performed in the presented order, in a different order, or simultaneously. Additionally, in some embodiments, some actions, behaviors, blocks, steps, etc. may be omitted, added, modified, skipped without departing from the scope of the present invention.

[0165] Figure 14 Is a flowchart showing a method (1400) for providing seamless service continuity during a handover of UE (102) from a source data network to a target data network according to embodiments disclosed herein. Steps (S1402 - S1410) are performed by a processor (905).

[0166] At S1402, method (1400) includes, when the UE (102) is connected to the first EDN (108a), the UE (102) receiving services from the first EAS (110a), and when the UE (102) is connected to the cloud data network (116), receiving services from the cloud AS (118).

[0167] At S1404, method (1400) includes at least one of the EEC (106) of the UE (102), the first EES (112a) associated with the first EAS (110a), and the first EAS (110a) determining that the current location of the UE (102) is served by both the second EAS (110b) and one of the first EAS (110a) and the cloud AS (118).

[0168] At S1406, method (1400) includes triggering the first EAS (110a) based on determining that the current location of the UE (102) is served by both the second EAS (110b) and one of the first EAS (110a) and the cloud AS (118), and initiating the transmission of a service-related application context by at least one of the EEC (106) and the first EES (112a). In another embodiment, method (1400) includes at least one of the first EAS (110a) and the first EES (112a) transmitting the service-related application context to the second EAS (110b).

[0169] At S1408, method (1400) includes the UE (102) establishing connections to both the second EAS (110b) and the second EES (112b) associated with the second EAS (110b).

[0170] At S1410, method (1400) includes the UE (102) disconnecting from the services using the first EAS (110a) and the first EES (112a).

[0171] At S1412, method (1400) includes the UE (102) continuing the services using the connections established to both the second EAS (110b) and the second EES (112b).

[0172] The various actions, behaviors, blocks, steps, etc. in the flowchart (S1400) may be performed in the presented order, in a different order, or simultaneously. Additionally, in some embodiments, some actions, behaviors, blocks, steps, etc. may be omitted, added, modified, skipped without departing from the scope of the present invention.

[0173] The foregoing description of specific embodiments will so fully disclose the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt such specific embodiments for various applications without departing from the general concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Accordingly, although the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments described herein.

Claims

1. A method for a user equipment UE to provide service continuity in a wireless communication network system, the method comprises: Connecting to a first edge application server EAS; Receiving data packets related to the service from the first EAS; Identifying a second EAS that provides the service at the location of the UE, wherein the second EAS is different from the first EAS; Sending information about the connection to a second EES associated with the second EAS to a first edge enabling server EES associated with the first EAS; Initiating, by an application client in the UE, capture of the application context of the service to transfer the application context of the service from the first EAS to the second EAS; and Connecting to the service from the second EAS and disconnecting from the service from the first EAS.

2. The method according to claim 1, further comprises: Receiving service availability information about the connection to the second EES and the second EAS from an edge configuration server ECS.

3. The method according to claim 2, further comprises: In response to the service availability information, sending information that the UE is in the service area to the ECS; In response to the information that the UE is in the service area, receiving the operation rules of the service area from the ECS; and Executing the received operation rules.

4. The method according to claim 1, wherein, The first EES and the first EAS are included in a first edge data network EDN, and wherein the second EES and the second EAS are included in a second EDN.

5. A method for a first edge application server EAS to provide service continuity in a wireless communication network system, the method comprises: Connecting to a user equipment UE; Sending data packets related to the service to the UE; Receiving from the UE information related to the connection of the UE to a second EAS, wherein capture of the application context of the service is initiated by an application client in the UE to transfer the application context of the service from the first EAS to the second EAS; Sending to the UE information including a notification indicating completion of the transfer of the application context of the service to the second EAS; In response to receiving a notification of the establishment of the connection of the UE to the second EAS, sending an end data packet related to the service to the UE; and Disconnecting the connection of the UE.

6. The method according to claim 5, further comprises: Receiving from the UE a request for capturing the application context of the service and transferring the captured application context of the service to the second EAS; In response to receiving the request, capturing the application context of the service and sending the captured application context of the service to the second EAS, In response to sending the captured application context of the service to the second EAS, receiving from the second EAS a response indicating confirmation of the captured application context of the service.

7. The method according to claim 5, wherein, The first EAS and the first Edge Enable Server EES associated with the first EAS are included in a first Edge Data Network EDN, and wherein, the second EAS and the second EES associated with the second EAS are included in a second EDN.

8. A method for providing service continuity by a second Edge Application Server EAS in a wireless communication network system, the method comprising: receiving a connection request from a User Equipment UE; sending a connection response to the UE indicating that the connection request is accepted; after the connection of the UE with the first EAS is switched to the connection of the UE with the second EAS, sending information related to the connection of the UE with the second EAS to the first EAS; and after sending the information related to the connection of the UE with the second EAS, sending data packets related to the service to the UE, wherein, the capture of the application context of the service is initiated by an application client in the UE to transfer the application context of the service from the first EAS to the second EAS.

9. The method according to claim 8, further comprising: receiving the application context of the service from the first EAS; and sending a response indicating confirmation of the application context of the service to the first EAS.

10. A User Equipment UE for providing service continuity in a wireless communication network system, the UE comprising: a transceiver; and at least one processor, coupled to the transceiver and configured to: connect to a first Edge Application Server EAS, receive data packets related to the service from the first EAS, identify a second EAS providing the service at the location of the UE, wherein the second EAS is different from the first EAS, send information about the connection to a second EES associated with the second EAS to a first Edge Enable Server EES associated with the first EAS, initiate the capture of the application context of the service by an application client in the UE to transfer the application context of the service from the first EAS to the second EAS, and connect to the service from the second EAS and disconnect from the service from the first EAS.

11. The UE according to claim 10, wherein, the at least one processor is configured to: receive service availability information about the connection to the second EES and the second EAS from an Edge Configuration Server ECS.

12. The UE according to claim 11, wherein, the at least one processor is configured to: send information that the UE is located in a service area to the ECS in response to the service availability information, receive the operation rules of the service area from the ECS in response to the information that the UE is located in the service area, and execute the received operation rules.

13. The UE according to claim 10, wherein, the first EES and the first EAS are included in a first Edge Data Network EDN, and Wherein, the second EES and the second EAS are included in the second EDN.

14. A first edge application server EAS for providing service continuity in a wireless communication network system, the first EAS comprising: a transceiver; and at least one processor, coupled to the transceiver and configured to: connect to a user equipment UE, send data packets related to the service to the UE, receive information related to the connection between the UE and a second EAS from the UE, wherein the capture of the application context of the service is initiated by an application client in the UE to transfer the application context of the service from the first EAS to the second EAS, send information including a notification indicating the completion of the transfer of the application context of the service to the second EAS to the UE, in response to receiving a notification of the establishment of the connection between the UE and the second EAS, send an end data packet related to the service to the UE, and disconnect the connection of the UE.

15. A second edge application server EAS for providing service continuity in a wireless communication network system, the second EAS comprising: a transceiver; and at least one processor, coupled to the transceiver and configured to: receive a connection request from a user equipment UE, send a connection response indicating that the connection request is accepted to the UE, after the connection between the UE and the first EAS is switched to the connection between the UE and the second EAS, send information related to the connection between the UE and the second EAS to the first EAS, and after sending the information related to the connection between the UE and the second EAS, send data packets related to the service to the UE, wherein the capture of the application context of the service is initiated by an application client in the UE to transfer the application context of the service from the first EAS to the second EAS.

Images