Method and device for service continuity in edge data network

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for service continuity by a leading edge enabler server (EES) in an edge data network (EDN) is provided. The method may comprise receiving a first edge application server (EAS) information provisioning request, from a edge enabler client (EEC) of a user equipment (UE); and based on receiving the first EAS information provisioning request, transmitting a second EAS information provisioning request including an identifier (ID) of source-EAS (S-EAS) associated with the UE to a partner EES associated with the S-EAS.

Description

METHOD AND DEVICE FOR SERVICE CONTINUITY IN EDGE DATA NETWORK

[0001] The proposed embodiments relate to telecommunication network system. More particularly present disclosure relates to edge service continuity support in edge node sharing.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] As per the Global System for Mobile Communications (GSMA), operators in the 5G era have a significant opportunity to monetize the capabilities of their networks. Operators want to make assets and capabilities consistently available across networks. Hence, a collaboration of operators, called an operator platform (OP), is defined to provide federated edge computing infrastructure to give application providers access to a larger service area. The federation of operators allows one operator (lead operator) to expose the capabilities of the other operators (partner operators) to 3rd party service providers or their own subscribers. The operator that shares the details with authorized recipients is called a lead operator, and the operator who provides or shares the application details is called a partner operator.

[0009] One of the important services of the federation is the Edge Node sharing service. Edge node sharing is a scenario wherein an operator, when serving requests originating from User Equipment (UEs), decides to provide the application from the Edge nodes of a partner operator where the application is available. Multiple scenarios provide the importance of Edge Node sharing service in the federation of operators for edge computing. Considering a scenario where in a city, two operators (operator-1 and operator-2) have deployed an edge network. However, a specific application is hosted only in the edge network provided by operator-2. Without federation, all subscribers of operator-1 will not have access to the specific application while using the edge network. The federation of operator-1 and operator-2 allows operator-1 to expose all applications. The operator-1 exposes applications based on service level agreements to all the subscribers of operator-1.

[0010] Further, as per the 3GPP-defined architecture for enabling edge applications, the 3GPP defines an Edge Enabler Layer (EEL) in TS 23.558. The EEL exposes applications (APIs) to support capabilities such as service provisioning registration, application server discovery, capability exposure to AS, and support for service continuity. Application Clients (ACs) in the User Equipment (UE) can locate and connect with the most suitable Edge Application Server (EAS) available in the Edge Data Network (EDN) using the capabilities provided by the EEL.

[0011] As shown in FIG. 1, in EEL, the S-EAS (105) serves the UE (101) in a specific service area. The S-EAS (105) serves the UE (101) based on the UE's location. So, when a UE (101) moves from one location to another, the S-EAS (105), which is connected to the AC in the UE (101), needs to be replaced with another T-EAS (109) depending on the service area to provide a better service experience to the user and UE (101). The EEL provides a service continuity feature for minimizing the application layer service interruption. In TS 23.558, the service continuity feature is supported by defining information elements and procedures for an Application Context Relocation (ACR). The ACR procedures enable the transfer of EEC context from one S-EES (103) (i.e., Source EES or S-EEC) to another T-EES (107) (Target EES or T-EES).

[0012] The S-EAS (105) with which the AC / UE (101) is connected to and receiving service in the UE's (101) current location is called a Source EAS (S-EAS). The S-EAS (105) with which the UE / AC (101) will be connected to receive service in the UE's new location is called Target EAS (T-EAS) (109). The S-EES with which the EEC and S-EAS are registered is called a Source EES (S-EES) (103). The T-EES (107) with which the T-EAS is registered and EEC will be registered in order to receive service is called Target EES (T-EES) (107).

[0013] In 3GPP, the ACR procedures include direct interaction between S-EAS (105) and S-EES (103) to receive information about the ACR procedure, such as ACR detection, ACR decision, ACR management events, etc. Further, EEC / UE (101) and S-EAS (105) are registered with the same S-EES (103). However, in an edge node sharing scenario, it is possible that S-EAS (105) may not be directly connected to S-EES (103). In this scenario, the EEC in UE (101) is registered with one EES of the lead OP, and the S-EAS (105) registers with a different EES of the partner OP. Therefore, it is necessary to enhance the 3GPP-defined ACR procedures to enable service continuity in the edge node sharing case, such that the S-EAS in the partner OP receives ACR-related information and events from the S-EES of the lead OP.

[0014] Thus, it is desired to address the above-mentioned disadvantages or other shortcomings or at least provide a useful alternative.

[0015] The principal object of the embodiments herein is to service continuity support in edge node sharing.

[0016] Another object of the invention is to enable service continuity in edge node sharing when S-EAS is not directly connected to EES in lead operator.

[0017] Yet another object of the invention is to enable service continuity in edge node sharing cases, such that the S-EAS (which is in the partner OP / partner node) receives the ACR-related information and events from S-EES (which is in the lead OP / source node).

[0018] Yet another object of the invention is to enable S-EAS to receive ACR information from S-EES in an edge node sharing scenario.

[0019] Yet another object of the invention is to enable the EES of partner operators to subscribe to the EES of the source operator on behalf of the S-EAS.

[0020] Yet another object of the invention is to transmit information related to the EES from the source operator to the S-EAS through the EES of the partner operator.

[0021] According to an embodiment of the present disclosure, a method for service continuity by a leading edge enabler server (EES) in an edge data network (EDN) is provided. The method may comprise receiving a first edge application server (EAS) information provisioning request, from a edge enabler client (EEC) of a user equipment (UE); and based on receiving the first EAS information provisioning request, transmitting a second EAS information provisioning request including an identifier (ID) of source-EAS (S-EAS) associated with the UE to a partner EES associated with the S-EAS.

[0022] According to an embodiment of the present disclosure, a method for service continuity by a partner edge enabler server (EES) in an edge data network (EDN) is provided. The method may comprise receiving an edge application server (EAS) information provisioning request including an identifier (ID) of source-EAS (S-EAS) from a leading EES; and based on receiving the EAS information provisioning request, transmitting an EES information provisioning request to the S-EAS.

[0023] According to an embodiment of the present disclosure, a device for a leading edge enabler server (EES) in an edge data network (EDN) is provided. The device may comprise a transceiver; and at least one processor connected to the transceiver. The at least one processor may be configured to receive a first edge application server (EAS) information provisioning request, from a edge enabler client (EEC) of a user equipment (UE); and based on receiving the first EAS information provisioning request, transmit a second EAS information provisioning request including an identifier (ID) of source-EAS (S-EAS) associated with the UE to a partner EES associated with the S-EAS.

[0024] In one aspect, the objectives are achieved by providing a method for edge service continuity in edge node sharing. The method includes receiving an EAS information provisioning request message from a User Equipment (UE) by an Edge Enabler Server (EES) in a lead operator to provide Edge Application Server (EAS) specific information. The EES of the lead operator is associated with the UE, which is in the coverage area of the EES. The method includes transmitting by an EES of the lead operator, EAS information provisioning request message to an EES of a partner operator of the federation to provide selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS), which is in the partner operator. Further, the method includes receiving, by an EES of the lead operator, subscription request message from the EES of the partner operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of, a notification target address of the S-EAS or the EES of the partner operator, EES ID of the partner operator and ECSP ID of the EES of the partner operator. The method further includes accepting by an EES of the lead operator, subscription requested by the EES of the partner operator to ensure providing notification about Application Context Relocation (ACR) management events from the EES towards S-EAS through the EES of the partner operator. The method includes detecting by an EES of the lead operator, occurrence of the ACR management event based on subscription criteria as received in the subscription request message. Furthermore, the method includes notifying by an EES of the lead operator, about the occurrence of the ACR management event to the EES of the partner operator or the S-EAS based on the notification target address included in the subscription request message.

[0025] In an embodiment, the EAS information provisioning request message comprises EAS ID of the S-EAS, EES ID of the lead operator, ECSP ID of the EES of the lead operator.

[0026] In an embodiment, the S-EAS is not directly connected to the EES of the lead operator.

[0027] In an embodiment, the S-EAS and the UE are not connected to the same EES of the lead operator.

[0028] Accordingly, the embodiment herein is to provide a method for edge service continuity in edge node sharing. The method includes receiving, by an EES of a partner operator, the EAS information provisioning request message from an EES of a lead operator to provide a selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS). Further, the method includes transmitting by the EES of the partner operator, EES information message to S-EAS to provide EES information. The EES information message comprises at least one of an EES ID of the EES of the lead operator, and ECSP ID of the EES of the partner operator. Further, the method includes receiving by the EES of the partner operator subscription request message from the S-EAS to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of lead operator, and a EES end point of the lead operator. Further, the method includes transmitting by the EES of the partner operator subscription request message to the EES of the lead operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of, a notification target address of the at least one of the S-EAS or the EES of the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator and. Further, the method includes subscribing by the EES of the partner operator to the EES of the lead operator on behalf of the S-EAS based on the subscription request message to perform Application Context Relocation (ACR) management events reception. Further, the method includes maintaining by the EES of the partner operator connectivity between the S-EAS and the EES of the lead operator during ACR management events.

[0029] In an embodiment, the EAS information provisioning request message comprises EAS ID of the S-EAS, a list of Application Context Relocation scenarios, a federation context identifier, EES ID of the lead operator, ECSP ID of the EES of the lead operator.

[0030] In an embodiment, the S-EAS is not directly connected to the EES of the lead operator.

[0031] In an embodiment, the S-EAS and the UE at the lead operator is not connected through the same EES of the lead operator.

[0032] Accordingly, the embodiment herein is to provide a method for edge service continuity in edge node sharing. The method includes receiving, by an S-EAS, an EES information message from EES of a partner operator. The EES information message comprises at least one of an EES ID of the EES of the lead operator, and ECSP ID of the EES of the partner operator ,. Further, the method includes initiating a connection with EES of the lead operator based on the EES information message. Further, the method includes transmitting, by an S-EAS, a subscription request message to the EES of the partner operator to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of the EES of the lead operator, and a EES end point in the lead operator. Also, the method includes subscribing, by the S-EAS, to the EES of the lead operator to perform Application Context Relocation (ACR) management events reception. Further, the method includes receiving, by the S-EAS, a notification about occurrence of ACR event from the EES of the lead operator or through the EES of the partner operator to perform ACR. Further, the method includes performing the ACR event through the EES of the partner operator or through the EES of the lead operator.

[0033] In an embodiment, the S-EAS is not directly connected to the EES of the lead operator.

[0034] In an embodiment, the S-EAS and the UE at the source node is not connected through the same EES of the lead operator.

[0035] Accordingly, the embodiment herein is to provide an EES of a lead operator for edge continuity support in edge node sharing. The EES comprises a processor and an edge service continuity controller, coupled to the processor. The edge service continuity controller receives an Edge Application Server (EAS) information provisioning request message from a User Equipment (UE) to provide EAS specific information. The EES in lead operator is associated with the UE, wherein the UE is in coverage area of the EES. Further, the edge service continuity controller transmits the EAS information provisioning request message to an EES of a partner operator of the federation to provide a selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS) and the S-EAS is in the partner operator. Further, the edge service continuity controller receives a subscription request message from the EES of the partner operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a notification target address of the at least one of the S-EAS or the EES of the partner operator, EES ID of the partner operator, and ECSP ID of the EES of the partner operator. Further, the edge service continuity controller accepts the subscription requested by the EES of the partner operator to ensure providing notification about Application Context Relocation (ACR) management events from the EES towards S-EAS through the EES of the partner operator. Further, the edge service continuity controller detects an occurrence of the ACR management event based on subscription criteria as received in subscription request message. Further, the edge service continuity controller notifies about the occurrence of the ACR management event to the EES of the partner operator or the S-EAS based on the notification target address included in the subscription request message.

[0036] Accordingly, the embodiment herein is to provide an EES of a partner operator for edge continuity support in edge node sharing. The EES of the partner operator comprises a processor and an edge service continuity controller, coupled to the processor. The edge service continuity controller receives the EAS information provisioning request message from an EES of a lead operator to provide a selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS). Further, the edge service continuity controller transmits the EES information message to S-EAS to provide EES information. The EES information message comprises at least one of an EES ID of the EES of the lead operator, and ECSP ID of the EES of the partner operator. Further, the edge service continuity controller receives a subscription request message from the S-EAS to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of lead operator, and a EES end point of the lead operator. Further, the edge service continuity controller transmits the subscription request message to the EES of the lead operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a notification target address of the at least one of the S-EAS or the EES of the partner operator, EES ID of the partner operator, and ECSP ID of the EES of the partner operator. Further, edge service continuity controller subscribes to the EES of the lead operator on behalf of the S-EAS based on the subscription request message to perform Application Context Relocation (ACR) management events reception. Further, the edge service continuity controller maintains connectivity between the S-EAS and the EES of the lead operator during ACR management events.

[0037] Accordingly, the embodiment herein is to provide a Source-EAS (S-EAS) for edge continuity support in edge node sharing. The S-EAS comprises a processor and an edge service continuity controller, coupled to the processor. The edge service continuity controller receives an EES information message from EES of a partner operator. The EES information message comprises at least one of an EES ID of the EES of the lead operator, and ECSP ID of the EES of the partner operator. Further, the edge service continuity controller initiates a connection with EES of the lead operator based on the EES information message. Further, the edge service continuity controller transmits a subscription request message to the EES of the partner operator to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of the EES of the lead operator, and a EES end point in the lead operator. Also, the edge service continuity controller subscribes to the EES of the lead operator to perform Application Context Relocation (ACR) management events reception. Further, the edge service continuity controller receives a notification about occurrence of ACR event from the EES of the lead operator or through the EES of the partner operator to perform ACR. Further, the edge service continuity controller performs the ACR event through the EES of the partner operator or through the EES of the lead operator.

[0038] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0039] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0040] FIG. 1 is a schematic diagram that illustrates edge service continuity according to prior art.

[0041] FIG. 2A is a schematic diagram that illustrates edge service continuity in an edge node sharing scenario according to the embodiment as disclosed herein.

[0042] FIG. 2B is a sequence diagram that illustrates an interaction between UE, S-EES, S-EAS, and P-EES for ensuring service continuity support in edge node sharing according to the embodiment as disclosed herein.

[0043] FIG. 3A is a block diagram of an EES of the lead operator for ensuring service continuity support in edge node sharing, according to the embodiment disclosed herein.

[0044] FIG. 3B is a block diagram that illustrates an EES of the partner operator for ensuring service continuity support in edge node sharing, according to the embodiment disclosed herein.

[0045] FIG. 3C is a block diagram of S-EAS, ensuring service continuity support in edge node sharing, according to the embodiment disclosed herein.

[0046] FIG. 4 is a flow diagram that illustrates a method by EES of the lead operator for edge service continuity in edge node sharing, according to the embodiment disclosed herein.

[0047] FIG. 5 is a flow diagram that illustrates a method by EES of the partner operator for edge service continuity in edge node sharing, according to the embodiment disclosed herein.

[0048] FIG. 6 is a flow diagram that illustrates a method by S-EAS for edge service continuity in edge node sharing, according to the embodiment disclosed herein.

[0049] It may be noted that, to the extent possible, like reference numerals have been used to represent like elements in the drawing. Furthermore, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not necessarily have been drawn to scale. For example, the dimensions of some of the elements in the drawing may be exaggerated relative to other elements to improve the understanding of aspects of the invention. Further, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the invention, so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0050] The embodiments herein, along with their various features and advantageous details, are explained more fully with reference to the non-limiting embodiments illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted to avoid unnecessarily obscuring the embodiments herein. Further, 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. The term "or," as used herein, refers to a non-exclusive or unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0051] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which are referred to herein as managers, units, modules, hardware components, or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and may optionally be driven by firmware and software. The circuits, for example, may be embodied in one or more semiconductor chips or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may 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 to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the proposed method.

[0052] The accompanying drawings are used to help easily understand various technical features, and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms "first," "second," etc. are used herein to describe various elements, these elements are not limited by these terms. These terms are generally used to distinguish one element from another.

[0053] In the era of 5G networks, operators have a significant opportunity to monetize the capabilities of their networks. To achieve this, the concept of operator platform (OP) has been defined, which provides federated edge computing infrastructure to give application providers access to a larger service area. One of the important services of the federation is the Edge Node sharing service, which allows an operator to provide an application from the edge nodes of a partner operator where the application is available. However, in an edge node sharing scenario, it is possible that the S-EAS may not be directly connected to S-EES, which can result in service interruptions and other disadvantages. Therefore, there is a need to enhance the 3GPP-defined ACR procedures to enable service continuity in the edge node sharing case.

[0054] Accordingly, the embodiments disclose a method for edge service continuity in edge node sharing. The method includes receiving an Edge Application Server (EAS) information provisioning request message from a User Equipment (UE) by an Edge Enabler Server (EES) in a lead operator to provide EAS specific information. The EES of the lead operator is associated with the UE, which is in the coverage area of the EES. Further, the method includes transmitting EAS information provisioning request message by the EES of the lead operator to an EES of a partner operator of the federation to provide selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS), and the S-EAS is in the partner operator. Furthermore, the method includes receiving subscription request message from the EES of the partner operator by the EES of the lead operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a federation context identifier, a notification target address of the S-EAS or the EES of the partner operator, and EAS ID of the S-EAS. The method includes accepting subscription requested by the EES of the partner operator by the EES of the lead operator to ensure providing notification about Application Context Relocation (ACR) management events from the EES towards S-EAS through the EES of the partner operator. Further, the method includes detecting EES occurrence of the ACR management event based on subscription criteria as received in the subscription request message by the EES of the lead operator. The method includes notifying the EES of the partner operator or the S-EAS about the occurrence of the ACR management event by the EES in the lead operator based on the notification target address included in the subscription request message.

[0055] Accordingly, the embodiments disclose a method for edge service continuity in edge node sharing. The method includes receiving, by an EES of a partner operator, the EAS information provisioning request message from an EES of a lead operator to provide selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS). Furthermore, the method includes transmitting, by the EES of the partner operator, the EES information message to S-EAS to provide EES information. The EES information message comprises at least one of an EES ID of the EES of the lead operator, an EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, an EEC ID, an AC ID, and selected ACR scenarios. Further, the method includes receiving, by the EES of the partner operator, a subscription request message from the S-EAS to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of the lead operator, and an EES endpoint of the lead operator. Further, the method includes transmitting, by the EES of the partner operator, the subscription request message to the EES of the lead operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a federation context identifier, a notification target address of the S-EAS or the EES of the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator, and EAS ID of the S-EAS. Further, the method includes subscribing, by the EES of the partner operator, to the EES of the lead operator on behalf of the S-EAS based on the subscription request message to perform Application Context Relocation (ACR) management events reception. Furthermore, the method includes maintaining, by the EES of the partner operator, connectivity between the S-EAS and the EES of the lead operator during ACR management events.

[0056] Accordingly, the embodiments disclose a method for edge service continuity in edge node sharing. The method includes receiving an EES information message from an EES of a partner operator by an S-EAS. The EES information message comprises at least one of an EES ID of the EES of the lead operator, an EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, an EEC ID, an AC ID, and selected ACR scenarios. Further, the method includes initiating a connection with the EES of the lead operator based on the EES information message by the S-EAS. Furthermore, the method includes transmitting a subscription request message to the EES of the partner operator to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is unable to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of the EES of the lead operator, and an EES endpoint in the lead operator. Further, the method includes subscribing by the S-EAS in the partner operator to the EES of the lead operator to perform Application Context Relocation (ACR) management events reception. Further, the method includes receiving a notification about the occurrence of an ACR event from the EES of the lead operator or through the EES of the partner operator to perform ACR by the S-EAS. Furthermore, the method includes performing the ACR event through the EES of the partner operator or through the EES of the lead operator by the S-EAS.

[0057] Accordingly, the embodiments disclose an EES of a lead operator for edge continuity support in edge node sharing. The EES comprises a processor and an edge service continuity controller coupled to the processor. The edge service continuity controller receives an Edge Application Server (EAS) information provisioning request message from a User Equipment (UE) to provide EAS-specific information. The EES of the lead operator is associated with the UE. Furthermore, the edge service continuity controller transmits the EAS information provisioning request message to an EES of a partner operator of the federation to provide selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS), and the S-EAS is in the partner operator. Further, the edge service continuity controller receives a subscription request message from the EES of the partner operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a federation context identifier, a notification target address of the S-EAS or the EES of the partner operator, and EAS ID of the S-EAS. Further, the edge service continuity controller accepts the subscription requested by the EES of the partner operator to ensure providing notification about Application Context Relocation (ACR) management events from the EES towards S-EAS through the EES of the partner operator. Furthermore, the edge service continuity controller detects an occurrence of the ACR management event based on subscription criteria as received in the subscription request message. Further, the edge service continuity controller notifies about the occurrence of the ACR management event to the EES of the partner operator or the S-EAS based on the notification target address included in the subscription request message.

[0058] Accordingly, the embodiments disclose an EES of a partner operator for edge continuity support in edge node sharing. The EES of the partner operator comprises a processor and an edge service continuity controller, coupled to the processor. The edge service continuity controller receives the EAS information provisioning request message from an EES of a lead operator to provide a selected EAS information. The EES of the partner operator is associated with a source-EAS (S-EAS). Further, the edge service continuity controller transmits the EES information message to S-EAS to provide EES information. The EES information message comprises at least one of an EES ID of the EES of the lead operator, an EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, an EEC ID, an AC ID and selected ACR scenarios. Further, the edge service continuity controller receives a subscription request message from the S-EAS to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of lead operator, and a EES end point of the lead operator. Further, the edge service continuity controller transmits the subscription request message to the EES of the lead operator to subscribe on behalf of the S-EAS. The subscription request message comprises at least one of a federation context identifier, a notification target address of the at least one of the S-EAS or the EES of the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator, and EAS ID of the S-EAS. Further, edge service continuity controller subscribes to the EES of the lead operator on behalf of the S-EAS based on the subscription request message to perform Application Context Relocation (ACR) management events reception. Further, the edge service continuity controller maintains connectivity between the S-EAS and the EES of the lead operator during ACR management events.

[0059] Accordingly, the embodiments disclose a Source-EAS (S-EAS) for edge continuity support in edge node sharing. The S-EAS comprises a processor and an edge service continuity controller, coupled to the processor. The edge service continuity controller receives an EES information message from EES of a partner operator. The EES information message comprises at least one of an EES ID of the EES of the lead operator, an EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, an EEC ID, an AC ID and selected ACR scenarios. Further, the edge service continuity controller initiates a connection with EES of the lead operator based on the EES information message. Further, the edge service continuity controller transmits a subscription request message to the EES of the partner operator to subscribe with the EES of the lead operator on behalf of the S-EAS when the S-EAS is not able to connect to the EES of the lead operator. The subscription request message comprises a notification target address of the S-EAS, EES ID of the EES of the lead operator, and a EES end point in the lead operator. Also, the edge service continuity controller subscribes to the EES of the lead operator to perform Application Context Relocation (ACR) management events reception. Further, the edge service continuity controller receives a notification about occurrence of ACR event from the EES of the lead operator or through the EES of the partner operator to perform ACR. Further, the edge service continuity controller performs the ACR event through the EES of the partner operator or through the EES of the lead operator.

[0060] The proposed solution for service continuity support in edge node sharing is a significant development in the field of telecommunications. Edge node sharing is a common practice among operators to reduce costs and improve network efficiency. However, it poses a challenge for service continuity as the EES of the lead operator may not be directly connected to the S-EAS deployed in the partner operator. The proposed solution addresses this challenge by enabling service continuity between the EES of the lead operator and the S-EAS through the EES of the partner operator.

[0061] The proposed solution enhances the ACR procedures to enable service continuity in edge node sharing cases. ACR procedures are essential for service continuity as they allow the S-EAS to receive information and events from the EES of the lead operator. The proposed solution ensures that the S-EAS in the partner operator receives the ACR related information and events from the EES of the lead operator, thus enabling service continuity.

[0062] Further, the proposed solution ensures the transmission of EES information to the S-EAS during the edge sharing scenario through the EES of the partner operator. This is a critical aspect of service continuity as it ensures that the S-EAS has access to all the necessary information to provide uninterrupted services to the end-users. Further, the proposed solution allows the EES to notify the occurrence of an event to the S-EAS through the EES of the partner operator. This feature ensures that the S-EAS is aware of any issues or events that may affect service continuity and can take appropriate measures to address them.

[0063] Furthermore, the proposed solution for service continuity support in edge node sharing is a significant development in the field of telecommunications. It addresses the challenge of service continuity in edge node sharing scenarios and enhances the ACR procedures to ensure uninterrupted services to end-users. The proposed solution also ensures the transmission of EES information and allows for the notification of events to the S-EAS, thus providing a comprehensive solution for service continuity support in edge node sharing.

[0064] FIG. 2A is a schematic diagram that illustrates edge service continuity in an edge node sharing scenario according to the disclosed embodiment. As shown in FIG. 2A, consider a UE (207) associated with an EES (201) in the lead operator. The EES (201) in the lead operator may be referred to as a leading EES. Furthermore, the S-EAS (205) is associated with the EES (203) in the partner operator. The EES (203) in the partner operator may be referred to as a partner EES. Also, the S-EAS (205) is not directly connected to the EES (201) in the lead operator. Consider the UE (207) moving from a Edge Data Network (EDN) to another EDN. Since the S-EAS (205) is not directly connected to the EES (201), during the handover of the UE (207) from the S-EAS to the target EAS (T-EAS), it is necessary to perform Application Context Relocation (ACR) from the S-EAS (205) to the Target-EAS (211). To perform the ACR, the EES (201) in the lead operator needs to interact with the S-EAS (205) and the T-EAS (211) through the target EES (T-EES) (209).

[0065] Furthermore, the EES (201) in the lead operator transmits the EAS information provisioning request message to the EES (203) in the partner operator to provide the selected EAS information. The EAS information provisioning request message can include, but is not limited to, the EAS ID of the S-EAS, a list of Application Context Relocation scenarios, a federation context identifier, EES ID of the lead operator, and ECSP ID of the EES of the lead operator. Upon receiving the EAS information provisioning request message, the EES (203) in the partner operator transmits the EES information message to the S-EAS (205) through edge 3. Further, the S-EAS (205) tries to initiate the connection with the EES (201) of the lead operator in response to receiving the EES information message. The S-EAS (205) subscribes to the EES (201) in the lead operator to perform ACR management events reception when the connection is successfully established between the S-EAS (205) and the EES (201).

[0066] Furthermore, the S-EAS (205) transmits the subscription request message to the EES (203) in the partner operator through edge 3 reference point to subscribe to EES (201) in the lead operator on behalf of the S-EAS (205) when the S-EAS (205) could not successfully establish the connection with the EES (201) in the lead operator. Upon receiving the subscription request message, the EES (203) in the partner operator transmits the subscription request message to the EES (201) in the lead operator to subscribe on behalf of the S-EAS (205). The EES (201) in the lead operator accepts the subscription request message, and the EES (203) in the partner operator subscribes to the EES (201) in the lead operator.

[0067] Upon the subscription, the EES (201) in the lead operator detects an occurrence of the ACR management event based on the subscription criteria received in the subscription request message. Furthermore, the EES (201) in the lead operator notifies the EES (203) in the partner operator about the occurrence of the ACR management event when a notification target address of the EES (203) in the partner operator is included in the subscription request message. Further, the EES (201) in the lead operator notifies the S-EAS (205) about the occurrence of the ACR management event when a notification target address of the S-EAS (205) is included in the subscription request message.

[0068] Further, the EES (203) in the partner operator maintains the connectivity between the S-EAS (205) and the EES (201) in the lead operator during the ACR management event reception. The S-EAS (205) performs the ACR event through EES (203) in the partner operator or through the EES (201) in the lead operator.

[0069] FIG. 2B is a sequence diagram that illustrates an interaction between UE, S-EES, S-EAS, and Partner EES (P-EES) for ensuring service continuity support in edge node sharing according to the embodiment as disclosed herein.

[0070] To maintain service continuity support in an edge node sharing scenario, at step S1, the UE (207) transmits an EAS information provisioning request message to the EES (201) in the lead operator to provide EAS-specific information.

[0071] At step S2, the EES (201) in the lead operator transmits the EAS information provisioning request message to the EES (203) in the partner operator of the federation to provide the selected EAS information. The EAS information provisioning request message can include, but is not limited to, the EAS ID of the S-EAS, a list of Application Context Relocation scenarios, a federation context identifier, EES ID of the lead operator, and the ECSP ID of the EES of the lead operator.

[0072] Upon receiving information from EES (201) in the lead operator, atStep S3, the partner operator's EES (203) transmits an EES information message to the S-EAS (205) based on Edge computing service provider (ECSP) policies. The EES (203) is associated with the S-EAS (205). The EES information message includes information related to the EES (201) in the lead operator. For example, the EES information message can include, but is not limited to, an EES ID of the EES of the lead operator, an EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, an EEC ID, an AC ID, and selected ACR scenarios.

[0073] Upon receiving the EES information, if the S-EAS (205) is unable to connect with EES (201) in the lead operator based on ECSP policiesat step S4,the S-EAS (205) transmits a subscription request message to the EES (203) in the partner operator to subscribe with EES (201) in the lead operator on behalf of the S-EAS (205). The subscription request message can include, but is not limited to, a notification target address of the S-EAS, EES ID of the lead operator, and an EES endpoint of the lead operator. The notification target address is the address of the S-EAS.

[0074] At step S5, the EES (203) in the partner operator subscribes to the EES (201) in the lead operator. The EES (203) in the partner operator subscribes to the EES (201) in the lead operator for one or more events, such as UE location, AC information exposure, UE identifier, and the like. The EES (203) in the partner operator maintains the same subscription context between the EES (201) in the lead operator and the S-EAS (205). The subscription between the EES (203) in the partner operator and the S-EAS (205) uses the same subscription ID and subscription context information as the subscription between the EES (203) in the partner operator and the EES (201) in the lead operator.

[0075] At step S6, the EES (201) in the lead operator detects an occurrence of the ACR management event based on subscription criteria received in the subscription request message.

[0076] At step S7, further, the EES (201) in the lead operator notifies the EES (203) in the partner operator about the occurrence of the ACR management event when the notification target address of the EES (203) of the partner operator is included in the subscription request message. Also, in an embodiment as shown inStep S8, the EES (201) in the lead operator notifies the S-EAS (205) about the occurrence of the ACR management event when the notification target address of the S-EAS (205) is included in the subscription request message.

[0077] At Step S9, the S-EAS (205) performs the ACR management event as notified by the EES (203) in the partner operator or the EES (201) in the lead operator.

[0078] FIG. 3A is a block diagram of a EES in lead operator for ensuring service continuity support in edge node sharing, according to the embodiment as disclosed herein.

[0079] The EES (201) of the lead operator includes a processor (301), a memory (303), an I / O interface (305), and an edge service continuity controller (307). Furthermore, the processor (301) of the EES (201) of the lead operator communicates with the memory (303), the I / O interface (305), and the edge service continuity controller (307). The processor (301) is configured to execute instructions stored in the memory (303) and to perform various processes. The processor (301) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0080] Furthermore, the memory (303) of the EES (201) of the lead operator includes storage locations that can be addressed through the processor (301). The memory (303) is not limited to volatile or non-volatile memory and can include one or more computer-readable storage media. Non-volatile storage elements, such as magnetic hard discs, optical discs, floppy discs, flash memories, EPROM, or EEPROM memories, can also be included in the memory (303). Further, the memory (303) of the EES (201) in the lead operator can store various information received from at least one of the UE (207), the S-EAS (205), and the EES (203) in the partner operator. For example, the memory can store information such as an indication of the occurrence of an event from the UE (207), a target notification address from at least one of the S-EAS (205) or the EES (203) of the partner operator, information included in the subscription request message, and the like.

[0081] The I / O interface (305) transmits information between the memory (303) and external peripheral devices, which are input-output devices associated with the EES (201) of the lead operator. The I / O interface (305) receives various information from the S-EAS (205) and the EES (203) of the partner operator to ensure edge service continuity in edge sharing scenarios. This information can include, but is not limited to, an EAS information provisioning request message from the UE (207) and the subscription request message from the EES (203) of the partner operator to subscribe on behalf of the S-EAS (205).

[0082] The edge service continuity controller (307) communicates with the I / O interface (305) and memory (303) for edge service continuity in edge node sharing. The edge service continuity controller (307) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components. The edge service continuity controller (307) of the EES (201) in the lead operator receives the EAS information provisioning request message from the UE (207). The UE (207) and the EES (201) in the lead operator are associated with each other. Further, the UE (207) is in the coverage area of the EES (201) in the lead operator and is moving from the source node to the target node. However, the UE (207) is not in the partner operator.

[0083] Further, the edge service continuity controller (307) transmits the EAS information provisioning request message to the EES (203) in the partner operator of the federation to provide a selected EAS information. The EAS information provisioning request message can include, but not limited to EAS ID of the S-EAS (205), a list of Application Context Relocation scenarios, EES ID of the lead operator, ECSP ID of the EES of the lead operator, and the federation context identifier. The federation context identifier is an unique identifier to identify federation relation between two operators. Upon transmitting, the edge service continuity controller (307) receives the subscription request message from the EES (203) of the partner operator to subscribe on behalf of the S-EAS (205), when the EES (201) is not able to connect with the S-EAS (205). The subscription request message can include but not limited to the federation context identifier, the notification target address of the at least one of the S-EAS (205) or the EES (203) of the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator, and EAS ID of the S-EAS (205).

[0084] Furthermore, the Edge Service Continuity Controller (307) accepts the subscription requested by the EES (203) of the partner operator to ensure the provision of notifications about Application Context Relocation (ACR) management events from the EES (201) towards S-EAS (205) through the EES (203) of the partner operator. Further, the Edge Service Continuity Controller (307) detects the occurrence of the ACR management event based on subscription criteria as received in the subscription request message. Furthermore, the Edge Service Continuity Controller (307) notifies the EES (203) of the partner operator or the S-EAS (205) about the occurrence of the ACR management event based on the notification target address included in the subscription request message.

[0085] FIG. 3B is a block diagram that illustrates an EES of a partner operator for ensuring service continuity support in edge node sharing according to the embodiment as disclosed herein. The EES (203) of the partner operator includes a processor (309), a memory (311), an I / O interface (313), and an edge service continuity controller (315). Furthermore, the processor (309) of the EES (203) in the partner operator communicates with the memory (311), the I / O interface (313), and the edge service continuity controller (315). The processor (309) is configured to execute instructions stored in the memory (311) and to perform various processes. The processor (309) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0086] Furthermore, the memory (311) of the EES (203) in the partner operator includes storage locations that can be addressed through the processor (309). The memory (311) is not limited to volatile or non-volatile memory and can include one or more computer-readable storage media. Non-volatile storage elements, such as magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories, can also be included in the memory (311).

[0087] Further, the memory (311) of the EES (203) in the partner operator can store various information received from at least one of the UE (207), the S-EAS (205), and the EES (201) of the lead operator. For instance, the memory (311) can store information such as an indication of the occurrence of an event from the EES (201) in the lead operator, a target notification address from the S-EAS (205), and other related information.

[0088] The I / O interface (313) is responsible for transmitting information between the memory (311) and external peripheral devices. These peripheral devices are the input-output devices associated with the EES (203) in the partner operator. The I / O interface (313) receives various pieces of information from the S-EAS (205) and the EES (201) in the lead operator to ensure edge service continuity in an edge sharing scenario. This information can include, but is not limited to, an EAS information provisioning request message from the EES (201) in the lead operator and a subscription request message from the S-EAS (205) to subscribe to the EES (201) in the lead operator.

[0089] The edge service continuity controller (315) communicates with the I / O interface (313) and memory (311) to ensure edge service continuity in edge node sharing. The edge service continuity controller (315) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0090] The edge service controller (315) of the EES (203) in the partner operator receives the EAS information provisioning request message from the EES (201) in the lead operator to provide selected EAS information. The EES (203) in the partner operator is associated with the S-EAS (205) directly. Furthermore, the edge service continuity controller (315) transmits the EES information message to S-EAS (205) to provide EES information related to the EES (201) in the lead operator. The EES information can include, but is not limited to, the EES ID of the EES (201) in the lead operator, an EES endpoint of the EES (201) in the lead operator, ECSP ID of the EES of the partner operator, the EEC ID, an AC ID, and selected ACR scenarios.

[0091] Further, the edge service continuity controller (315) receives the subscription request message from the S-EAS (205) to subscribe with the EES (201) in the lead operator on behalf of the S-EAS (205) when the S-EAS (205) is not able to connect to the EES (201) in the lead operator. The subscription request message can include, but is not limited to, the notification target address of the S-EAS (205), EES ID of the lead operator, and the EES endpoint of the lead operator.

[0092] In an embodiment, the EES (203) of the partner operator subscribes to the EES (201) in the lead operator for any other events like the UE location, the AC information exposure, the UE Identifier.

[0093] In an embodiment, the EES (203) of the partner operator on behalf of the S-EAS (205) acts as a consumer for a session with a QoS API as exposed by the EES (201) in the lead operator. The EES (203) of the partner operator creates, updates, and revoke sessions on behalf of the S-EAS (205) in order to support the setup of a data session between the AC and the EAS with a specific QoS.

[0094] In an embodiment, the EES (203) in the partner operator on behalf of the S-EAS (205) acts as a consumer for an application traffic influence trigger the API as exposed by the EES (201) in the lead operator.

[0095] In an embodiment, all the APIs as exposed by the S-EES (103) towards the S-EAS over the EDGE-3 interface, are also exposed towards the P-EES (111) over EDGE-9 interface. All the APIs are like the UE Location, the App Client Information, the UE Identifier, the session with QoS, the Target EAS Discovery, the App Context Relocation, the EEL Managed ACR, the selected Target EAS, and the ACR Status Update.

[0096] Upon receiving the subscription request message, the edge service continuity controller (315) transmits it to the EES (201) of the lead operator to subscribe on behalf of the S-EAS (205). Further, the edge service continuity controller (315) subscribes to the EES (201) in the lead operator on behalf of the S-EAS (205) based on the subscription request message to perform ACR management events reception. Furthermore, the edge service continuity controller (315) maintains connectivity between the S-EAS (205) and the EES (201) in the lead operator during ACR management events.

[0097] FIG. 3C is a block diagram of S-EAS, ensuring service continuity support in edge node sharing, according to the embodiment disclosed herein. The S-EAS (205) includes a processor (317), a memory (319), an I / O interface (321), and an edge service continuity controller (323). Furthermore, the processor (317) of the S-EAS (205) communicates with the memory (319), the I / O interface (321), and the edge service continuity controller (323). The processor (317) is configured to execute instructions stored in the memory (319) and to perform various processes. The processor (317) can include one or several processors, such as a general-purpose processor like a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit like a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor like a neural processing unit (NPU).

[0098] Furthermore, the memory (319) of the S-EAS (205) includes storage locations that are addressable through the processor (317). The memory (319) is not limited to volatile or non-volatile memory. Further, the memory (319) can include one or more computer-readable storage media. Non-volatile storage elements, such as magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories or electrically erasable and programmable memories, can also be included in the memory (319).

[0099] Further, the memory (319) of the S-EAS (205) can store various information received from at least one of the EES (201) in the lead operator and EES (203) in the partner operator. For instance, the memory (319) can store information such as indications of the occurrence of an event from the EES (201) in the lead operator or EES (203) in the partner operator, among other things.

[0100] The I / O interface (321) is responsible for transmitting information between the memory (319) and external peripheral devices. These peripheral devices are the input-output devices associated with the S-EAS (205). The I / O interface (321) receives and transmits various pieces of information from the EES (201) in the lead operator and the EES (203) in the partner operator to ensure edge service continuity in edge sharing scenarios. This information can include, but is not limited to, an EES information message from the EES (203) in the partner operator and a subscription request message to the EES (203) in the partner operator.

[0101] The edge service continuity controller (323) communicates with the I / O interface (321) and memory (319) to ensure edge service continuity in edge node sharing. The edge service continuity controller (323) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components. The edge service continuity controller (323) of the S-EAS (205) receives the EES information message from the EES (203) in the partner operator. The EES information message can include, but is not limited to, the EES ID of the EES of the lead operator, the EES endpoint of the EES of the lead operator, ECSP ID of the EES of the partner operator, the EEC ID, an AC ID, and selected ACR scenarios.

[0102] Furthermore, the edge service continuity controller (323) initiates a connection with the EES (201) of the lead operator based on the EES information message, in accordance with ESCP policies. If the edge service continuity controller (323) is unable to connect with the EES (201) in the lead operator, it transmits a subscription request message to the EES (203) in the partner operator, on behalf of the S-EAS (205), to subscribe with the EES (201) in the lead operator.

[0103] Further, if the edge service continuity controller (323) is able to connect with the EES (201) in the lead operator, the S-EAS (205) subscribes directly to the EES (201) in the lead operator.

[0104] Furthermore, the edge service continuity controller (323) receives a notification from the EES (201) in the lead operator and the EES (203) in the partner operator about the occurrence of the ACR event. The edge service continuity controller (323) receives the notification based on the notification target address included in the subscription request message. For instance, when the address of the EES (203) in the partner operator is included in the notification target address, the edge service continuity controller (323) receives the notification from the EES (203) in the partner operator. In another embodiment, when the address of the S-EAS (205) is included in the notification target address, the edge service continuity controller (323) receives the notification from the EES (201) in the lead operator.

[0105] Further, the edge service continuity controller (323) performs the ACR event through the EES (203) in the partner operator or through the EES (201) in the lead operator.

[0106] FIG. 4 is a flow diagram that illustrates a method by EES for lead operator in edge service continuity in edge node sharing according to the embodiment as disclosed herein.

[0107] At block 401, the method includes receiving the Edge Application Server (EAS) information provisioning request message from the UE (207) to provide EAS-specific information. The EES (201) in the lead operator is associated with the UE (207). Further, the UE (207) is in the coverage area of the EES (201).

[0108] At block 403, the method includes transmitting the EAS information provisioning request message to the EES (203) in the partner operator of the federation to provide selected EAS information. The EES (203) in the partner operator is associated with an S-EAS (205), and the S-EAS (205) is in the partner operator.

[0109] At block 405, the method includes receiving a subscription request message from the EES (203) of the partner operator to subscribe on behalf of the S-EAS (205). The subscription request message comprises at least one of the federation context identifier, the notification target address of at least one of the S-EAS (205) or the EES of the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator, and the EAS ID of the S-EAS (205).

[0110] At block 407, the method includes accepting the subscription requested by the EES (203) of the partner operator to ensure the provision of notification about ACR management events from the EES (201) towards S-EAS (205) through the EES (203) of the partner operator.

[0111] At block 409, the method includes detecting the occurrence of the ACR management event based on the subscription criteria as received in the subscription request message.

[0112] At block 411, the method includes notifying about the occurrence of the ACR management event to the EES (203) of the partner operator or the S-EAS (205) based on the notification target address included in the subscription request message.

[0113] FIG. 5 is a flow diagram that illustrates a method by EES and partner operator for edge service continuity in edge node sharing, according to the embodiment disclosed herein. At block 501, the method includes receiving the EAS information provisioning request message from an EES of a lead operator to provide selected EAS information. The EES (203) in the partner operator is associated with the S-EAS (205).

[0114] At block 503, the method includes transmitting the EES information message to S-EAS (205) to provide EES information. The EES information message can include, but is not limited to, at least one of the EES ID of the EES of the lead operator, the EES endpoint of the EES (201) in the lead operator, ECSP ID of the EES of the partner operator, the EEC ID, an AC ID, and selected ACR scenarios.

[0115] At block 505, the method includes receiving the subscription request message from the S-EAS (205) to subscribe with the EES (201) in the lead operator on behalf of the S-EAS (205) when the S-EAS (205) is not able to connect to the EES (201) in the lead operator. The subscription request message can include, but is not limited to, the notification target address of the S-EAS (205), EES ID of the lead operator, and the EES endpoint of the lead operator.

[0116] At block 507, the method includes transmitting the subscription request message to the EES (201) in the lead operator to subscribe on behalf of the S-EAS (205). The subscription request message can include, but is not limited to, the federation context identifier, the notification target address of at least one of the S-EAS (205) or the EES (201) in the partner operator, EES ID of the partner operator, ECSP ID of the EES of the partner operator, and the EAS ID of the S-EAS.

[0117] At block 509, the method includes subscribing to the EES (201) in the lead operator on behalf of the S-EAS (205) based on the subscription request message to perform ACR management events reception.

[0118] At block 511, the method includes maintaining connectivity between the S-EAS (205) and the EES (201) in the lead operator during ACR management events.

[0119] FIG. 6 is a flow diagram that illustrates a method by S-EAS for edge service continuity in edge node sharing according to the embodiment as disclosed herein. At block 601, the method includes receiving the EES information message from EES (203) in the partner operator. The EES information message can include, but is not limited to, the EES ID of the EES (201) in the lead operator, an EES endpoint of the EES (201) in the lead operator, an EEC ID, an AC ID, and selected ACR scenarios.

[0120] At block 603, the method includes initiating the connection with the EES (201) in the lead operator based on the EES information message.

[0121] At block 605, the method includes transmitting the subscription request message to the EES (203) in the partner operator to subscribe with the EES (201) in the lead operator on behalf of the S-EAS (205) when the S-EAS (205) is not able to connect to the EES (201) in the lead operator. The subscription request message can include, but is not limited to, the notification target address of the S-EAS (205), EES ID of the EES (201) in the lead operator, and an EES endpoint in the lead operator.

[0122] At block 607, the method includes subscribing to the EES (201) lead operator to perform ACR management events reception.

[0123] At block 609, the method includes receiving the notification about the occurrence of ACR event from the EES (201) in the lead operator or through the EES (203) in the partner operator to perform ACR.

[0124] At block 611, the method includes performing the ACR event through the EES (203) in the partner operator or through the EES (201) in the lead operator.

[0125] The various actions, acts, blocks, steps, or the like in the method are performed in the order presented, in a different order, or simultaneously. Furthermore, in some embodiments, some of the actions, acts, blocks, steps, or the like are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method.

[0126] Unlike the conventional mechanism the proposed invention provides an efficient and cost-effective solution to the problem of service continuity in edge node sharing scenarios. By enabling the S-EAS to receive ACR-related information and events from the EES of lead operator, the invention ensures that the service continuity is maintained even in cases where multiple operators are sharing the same physical infrastructure. This is achieved by leveraging the existing network infrastructure and protocols, which significantly reduces the cost and complexity of the system.

[0127] Further, the proposed invention also provides a more effective solution for the S-EAS to receive the ACR information from the S-EES in an edge node sharing scenario. This is achieved by enabling the S-EAS to efficiently process and interpret the ACR information received from the EES of the lead operator. The proposed invention represents a significant advancement in the field of edge node sharing. By providing a more efficient and cost-effective solution for service continuity, the invention has the potential to revolutionize the way telecommunications operators share physical infrastructure and provide services in the network.

[0128] Furthermore, the proposed invention enhances the operator platform as defined by the GSMA. The GSMA is a group of operators, has defined an operator platform that aims to provide seamless connectivity to users, regardless of the operator they are using. However, the current platform does not support service continuity across operators, which can result in disruptions in service for users. The proposed invention addresses this issue by enhancing the operator platform to support service continuity across operators. This means that users will be able to switch between operators without any disruption in service, which will significantly improve their experience.

[0129] In addition to supporting service continuity across operators, the proposed invention also provides a solution to provide the S-EES details to the S-EAS. Furthermore, the proposed invention also provides a solution to notify ACR management events to the S-EAS. The proposed invention enables the operator platform to notify the S-EAS of any ACR management events, which will enable the S-EAS to track the usage of services more accurately. This will be beneficial for both the operators and the users, as it will enable the operators to track the users accurately for the services they use, and it will enable the users to track their usage more easily

[0130] The foregoing description of the specific embodiments will fully reveal the general nature of the embodiments herein, such that others can readily modify and / or adapt such specific embodiments for various applications without departing from the generic concept. 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. Thus, while 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 modifications within the scope of the embodiments as described herein.

Claims

1.A method for service continuity by a leading edge enabler server (EES) in an edge data network (EDN), the method comprising:receiving a first edge application server (EAS) information provisioning request, from a edge enabler client (EEC) of a user equipment (UE);based on receiving the first EAS information provisioning request, transmitting a second EAS information provisioning request including an identifier (ID) of source-EAS (S-EAS) associated with the UE to a partner EES associated with the S-EAS.2.The method of claim 1, wherein the second EAS information provisioning request further comprises at least one of a list of application context relocation (ACR) scenarios, and an ID of the leading EES.3.The method of claim 1, further comprising:receiving a subscribe request related to an ACR management event associated with the S-EAS, from the partner EES; andtransmitting a notification related to the ACR management event to the partner EES to send the notification to the S-EAS.4.The method of claim 3, wherein the first EAS information provisioning request, the second information provisioning request, the subscribe request related to the ACR management event, and the notification related to the ACR management event are communicated over an edge-9 reference point.5.The method of claim 2, wherein the notification related to the ACR management event is transmitted to the S-EAS from the partner EES over an edge-3 reference point.6.A method for service continuity by a partner edge enabler server (EES) in an edge data network (EDN), the method comprising:receiving an edge application server (EAS) information provisioning request including an identifier (ID) of source-EAS (S-EAS) from a leading EES; andbased on receiving the EAS information provisioning request, transmitting an EES information provisioning request to the S-EAS.7.The method of claim 6, wherein the EAS information provisioning request further comprises at least one of a list of application context relocation (ACR) scenarios, and an ID of the leading EES.8.The method of claim 6, further comprising:receiving a first subscribe request related to an ACR management event, from the S-EAS; andbased on receiving the first subscribe request related to the ACR management event, transmitting a second subscribe request related to the ACR management event, to the leading EES.9.The method of claim 8, further comprising:receiving a notification related to the ACR management event from the leading EES; andtransmitting the received notification related to the ACR management event to the S-EAS.10.The method of claim 9, wherein the EAS information provisioning request, the second subscribe request related to the ACR management event, and the notification related to the ACR management event from the leading EES are communicated over an edge-9 reference point, andwherein the EES information provisioning request, the first subscribe request related to the ACR management event, and the notification related to the ACR management event to the S-EAS are communicated over an edge-3 reference point.11.A device for a leading edge enabler server (EES) in an edge data network (EDN), the device comprising:a transceiver; andat least one processor connected to the transceiver, wherein the at least one processor is configured to:receive a first edge application server (EAS) information provisioning request, from a edge enabler client (EEC) of a user equipment (UE); andbased on receiving the first EAS information provisioning request, transmit a second EAS information provisioning request including an identifier (ID) of source-EAS (S-EAS) associated with the UE to a partner EES associated with the S-EAS.12.The device of claim 11, wherein the second EAS information provisioning request further comprises at least one of a list of application context relocation (ACR) scenarios, and an ID of the leading EES.13.The device of claim 11, wherein the at least one processor is configured to:receive a subscribe request related to an ACR management event associated with the S-EAS, from the partner EES; andtransmit a notification related to the ACR management event to the partner EES to send the notification to the S-EAS.14.The device of claim 13, wherein the first EAS information provisioning request, the second information provisioning request, the subscribe request related to the ACR management event, and the notification related to the ACR management event are communicated over an edge-9 reference point.15.The device of claim 12, wherein the notification related to the ACR management event is transmitted to the S-EAS from the partner EES over an edge-3 reference point.

Images