Method and apparatus for managing edge enabled servers (EES) in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed herein is a method of a first edge enabled server (EES) in an edge network, the edge network comprising a first EES and a second EES. The method comprises the following steps: receiving a context push request message for a context transmission process from a second EES; in response to the push request message, verifying and authorizing the second EES; and if the second EES is authorized and the first EES and the second EES are part of the same set of EES of the edge network, storing first information included in the context push request message for synchronization with the second EES, and transmitting a context push response message to the second EES, wherein the first information comprises at least one of a list of a context of an Edge Enable Client (EEC) or a list of a configuration file of an Edge Application Server (EAS), and the first information comprises at least one of a list of a context of an Edge Enable Client (EEC) or a list of a configuration file of an EAS.

Description

Technical Field

[0001] The present invention relates to wireless communications and more particularly to a method and apparatus for managing an edge enabling server (EES) in a communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called millimeter waves including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC) and massive machine type communication (mMTC), there has been ongoing standardization on beamforming and massive MIMO for mitigating radio wave path loss in mmWave and increasing radio wave transmission distance in mmWave, parameter sets supporting dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services that 5G mobile communication technology is to support, there is an ongoing discussion on the improvement and performance enhancement of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as: V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE satellite direct communication for providing coverage in areas where communication with terrestrial networks is not available), and positioning.

[0005] In addition, there has been ongoing standardization on air interface architecture / protocols for 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 nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (NR's two-step RACH) for simplifying the random access procedure. There is also ongoing standardization on system architecture / services for 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the already exponentially growing number of connected devices will be connected to the communication network, and it is accordingly expected that enhanced functionality and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., improving 5G performance and reducing complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] In addition, such development of 5G mobile communication systems will serve as the basis for not only developing new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and high-dimensional spatial multiplexing technology of RIS (reconfigurable smart surface), but also developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for utilizing satellites and AI (artificial intelligence) from the design stage to achieve system optimization and internalize end-to-end AI support functions, and next-generation distributed computing technology for implementing services with a complexity that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources.

[0008] Typically, the 5th generation (5G) technology is expected to have high-speed data transmission that has increased many times compared to the previous generation of networks. In order to reduce latency, edge computing is required to bring computing resources close to the end user. In the existing approach, the 3rd Generation Partnership Project (3GPP) has defined EEL. EEL specifies an edge enabling client (EEC), which provides the client functions of EEL to support application clients (Application Clients, AC) in user equipment (UE). EEL also specifies an edge enabling server (EES), which provides the server-side functions of EEL to support edge application servers (Edge Application Server, EAS). EES plays an important role and exposes application programming interfaces (Application Programming Interface, API) to support capabilities such as registration, application server discovery, capability exposure to AC, and support for service continuity. AC locates and connects to a suitable EAS available in the edge data network (Edge Data Network, EDN) based on the capabilities provided by EES.

[0009] In order to provide effective services to AC and EAS, EEL must be resilient, i.e. EEL continues to provide services to AC and EAS in case of EES failure. To be resilient, EEL has the ability to recover from failures and also maintain the durability of service reliability during failures. It is necessary to make EEL services resilient to EES failures. Summary of the invention

[0010] The main purpose of the embodiments herein is to provide a system and method for handling edge enabling server (EES) failures in edge networks. In the proposed method, a cloud network is configured to back up EES content in the event of an EES failure. The proposed method has the ability to recover from failures and maintain persistence of service reliability in the event of an EES failure.

[0011] Another object of embodiments herein is to provide a system and method for sending a push request message to a backup EES to synchronize content stored in a source EES.

[0012] It is yet another object of embodiments herein to provide a system and method for sending a pull request message to a source EES to back up content from the source EES to a backup EES.

[0013] It is yet another object of embodiments herein to provide systems and methods for synchronizing content between a source EES and a backup EES based on an EES data repository.

[0014] Therefore, an embodiment of the present invention provides a method for a first edge enabling server in an edge network including a first EES and a second EES. The method includes: receiving a context push request message for a context transfer process from a second EES; responding to the push request message, verifying and authorizing the second EES; and storing first information included in the context push request message for synchronization with the second EES, and sending a context push response message to the second EES, wherein the first information includes at least one of a list of edge enabling client (EEC) contexts or a list of edge application server (EAS) profiles, in the case where the second EES is authorized and the first EES and the second EES are part of the same EES set of the edge network.

[0015] In an embodiment, the first information further includes an indication for context synchronization between the first EES and the second EES.The second information included in the context push response message includes at least one of a list of EEC contexts, a list of EAS profiles, and an indication for context synchronization between the first EES and the second EES.

[0016] Therefore, an embodiment of the present invention provides a method for a second edge enabling server (EES) in an edge network, the edge network comprising at least one first EES and a second EES. The method comprises: sending a context push request message for a context transfer process to the at least one first EES; and receiving a context push response message from the at least one first EES when the second EES is authorized and the at least one first EES and the second EES are part of the same EES set of the edge network, wherein the first information included in the context push request message is stored in the at least one first EES, and wherein the first information comprises at least one of a list of edge enabling client (EEC) contexts or a list of edge application server (EAS) profiles.

[0017] In an embodiment, the first information included in the context push request message also includes an indication for content synchronization between the at least one first EES and the second EES. The method also includes sending an EES registration request message including an indication for the at least one second EES to an edge configuration server (ECS).

[0018] In an embodiment, the second information included in the context push response message includes at least one of a list of EEC contexts, a list of EAS profiles, or an indication for context synchronization between the first EES and the second EES.

[0019] Therefore, embodiments of the present invention provide a first edge enabling server (EES) in an edge network including a first EES and a second EES. The first EES includes: a memory; a communicator; and a processor coupled to the memory and the communicator, and is configured to: receive a context push request message for a context transfer process from the second EES, verify and authorize the second EES in response to the push request message, and, if the second EES is authorized and the first EES and the second EES are part of the same EES set of the edge network, store the first information included in the context push request message for synchronization with the second EES, and send a context push response message to the second EES, wherein the first information includes at least one of a list of edge enabling client (EEC) contexts or a list of edge application server (EAS) profiles.

[0020] In an embodiment, the first information also includes an indication for context synchronization between the first EES and the second EES. And, the second information included in the context push response message includes at least one of a list of EEC contexts, a list of EAS profiles, or an indication for context synchronization between the first EES and the second EES.

[0021] Therefore, an embodiment of the present invention provides a second edge enabling server (EES) in an edge network, the edge network including at least one first EES and a second EES, the second EES including: a memory; a communicator; and a processor coupled to the memory and the communicator, and configured to: send a context push request message for a context transfer process to the at least one first EES, and receive a context push response message from the at least one first EES when the second EES is authorized and the at least one first EES and the second EES are part of the same EES set of the edge network, wherein the first information included in the context push request message is stored in the at least one first EES, and wherein the first information includes at least one of a list of edge enabling client (EEC) contexts or a list of edge application server (EAS) profiles.

[0022] In an embodiment, the first information included in the context push request message also includes an indication for content synchronization between at least one first EES and a second EES. The processor is further configured to send an EES registration request message including an indication for at least one second EES to an edge configuration server (ECS).

[0023] In an embodiment, the second information included in the context push response message includes at least one of a list of EEC contexts, a list of EAS profiles, or an indication for context synchronization between the first EES and the second EES.

[0024] Therefore, an embodiment of the present invention provides a method for handling EES failures to generate a service elastic EEL in an edge network. The method includes receiving a push request message from a first EES in a plurality of EESs by a second EES in a plurality of EESs to back up content stored at the first EES to synchronize with the second EES. In addition, the method includes verifying and authorizing the first EES based on a push request message received from the first EES by the second EES. The method also includes backing up content stored in the first EES by the second EES by storing the content in the second EES based on the push request message.

[0025] In an embodiment, the push request message includes content that needs to be backed up at the second EES. The content includes a list of EEC contexts associated with the first EES, a list of EAS profiles associated with the first EES, an indication to back up content associated with the first EES, details about subscriptions on different edge interfaces, and a list of second EESs from a plurality of EESs configured at the first EES for backing up content for synchronization.

[0026] Therefore, embodiments herein provide a method for handling EES failures to generate service resilience in an EEL of an edge network. The method includes receiving, by a first EES among a plurality of EESs, a pull request message from a second EES among a plurality of EESs to back up content stored at the first EES for synchronization with the second EES, and authorizing, by the first EES, the second EES based on the pull request message received from the second EES. The method also includes sending, by the second EES, a response including content stored in the first EES to back up at the second EES based on the pull request message.

[0027] In an embodiment, the response to the pull request message includes content that needs to be backed up at the second EES. The content includes a list of EEC contexts associated with the first EES, a list of EAS profiles associated with the first EES, an indication to back up content associated with the first EES, details about subscriptions on different edge interfaces, and a list of second EESs from a plurality of EESs configured at the first EES for backing up content for synchronization.

[0028] In an embodiment, the contents of a list regarding a second EES from the plurality of EESs and an identification of the set of EESs are provided by a first EES to an edge configuration server (ECS) in an EEL of an edge network.

[0029] In an embodiment, the method includes storing, by an ECS in an EEL of an edge network, a list of a second EES of a plurality of EESs and an identification of an EES set. The method includes receiving, by the ECS, a service provisioning request message from the EEC. The method also includes sending, by the ECS, a service provisioning response message to the EEC for storing a service provisioning response message by the EEC.

[0030] In an embodiment, the service provisioning response message includes the content of the plurality of second EESs and an identification of an EES set. The EES set includes a list of the first EES and the second EES.

[0031] Accordingly, the embodiments herein provide a method for handling EES failures to make the EEL in the edge network have service resilience. The method includes receiving a push request message from a first EES in a plurality of EESs by an EES data repository to back up the content stored at the first EES to synchronize with a second EES. The method includes authorizing the first EES by the EES data repository based on a push request message received from the first EES. In addition, the method includes storing content for backup and synchronization with the second EES by the EES data repository based on the received push request message. The method also includes receiving a pull request message from a second EES in a plurality of EESs by the EES data repository to obtain content stored by the first EES for synchronization with the second EES. The EES data repository includes the content of the first EES for synchronization with at least one second EES associated with the first EES in the EEL of the edge network. In addition, the method includes sending content by the EES data repository to back up at the second EES.

[0032] Therefore, the embodiments herein provide a system for handling failures of EES so that the EES in the edge network has service resilience. The EEL in the edge network includes a first EES and a second EES in a plurality of EESs. The second EES includes a memory, a processor coupled to the memory, a communicator coupled to the processor, and an EES elasticity controller coupled to the memory, the processor, and the communicator. The EES elasticity controller is configured to receive a push request message from a first EES in a plurality of EESs to back up content stored at the first EES so as to synchronize with the second EES, and enable communication between the second EES and the EEC in the EEL of the edge network. The EES elasticity controller is configured to verify and authorize the first EES based on a push request message received from the first EES. The EES elasticity controller is also configured to back up content stored in the first EES by storing the content in the second EES based on a push request message.

[0033] Therefore, the embodiments herein provide a system for handling EES failures to enable an EEL in an edge network to have service resilience. The EEL in the edge network includes a first EES and a second EES in a plurality of EESs. The first EES includes a memory, a processor coupled to the memory, a communicator coupled to the processor, and an EES resilience controller coupled to the memory, the processor, and the communicator. The EES resilience controller is configured to receive a pull request message from a second EES in a plurality of EESs to back up content stored at the first EES so as to synchronize with the second EES and enable communication between the second EES and the EEC in the EEL of the edge network. The EES resilience controller is configured to verify and authorize the second EES based on a pull request message received from the second EES. The EES resilience controller is also configured to send a response including content stored at the first EES to a backup at the second EES based on the pull request message.

[0034] Therefore, embodiments herein provide a system for handling EES failures to enable an EEL in an edge network to have service resilience. The EEL in the edge network includes an EES data repository. The EES data repository includes a memory, a processor coupled to the memory, a communicator coupled to the processor, and an EES resilience controller coupled to the memory, the processor, and the communicator. The EES resilience controller is configured to receive a push request message from a first EES in a plurality of EESs to back up content stored at the first EES for synchronization with a second EES. The EES resilience controller is configured to authorize the first EES based on a push request message received from the first EES. The EES resilience controller is configured to store content for backup and synchronization with a second EES based on the received push request message. The EES resilience controller is also configured to receive the pull request message from a second EES in a plurality of EESs to obtain content stored by the first EES for synchronization with the second EES, and to enable communication between the second EES and an EEC in the EEL of the edge network. The EES data repository includes the content of the first EES for synchronization with a second EES associated with the first EES in the EEL of the edge network. Additionally, the EES resiliency controller is configured to send the content to a second EES for backup.

[0035] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better appreciated and understood. However, it should be understood that the following description, although indicating preferred embodiments and many of their specific details, is given by way of illustration and not limitation. Without departing from the spirit of this article, many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] Figure 1a is a block diagram of a first EES according to an embodiment disclosed herein;

[0038] Figure 1b is a block diagram of a second EES according to embodiments disclosed herein;

[0039] Figure 2 is a flow chart illustrating a method for synchronizing a first EES and a second EES based on a push mechanism according to an embodiment disclosed herein;

[0040] Figure 3 is a flow chart illustrating a method for synchronizing a first EES and a second EES based on a pull mechanism according to an embodiment as disclosed herein;

[0041] Figure 4a An interface connecting a first EES and an EES data repository according to an embodiment disclosed herein is shown;

[0042] Figure 4b is a block diagram of an EES data repository according to an embodiment disclosed herein;

[0043] Figure 5 is a flow chart illustrating a method for sending a list of a second EES to an EEC according to an embodiment disclosed herein; and

[0044] Figure 6 is a flow chart illustrating a method for synchronizing a first EES and a second EES by an EES data repository according to embodiments disclosed herein. DETAILED DESCRIPTION

[0045] The embodiments of this article and their various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of this article. In addition, the various embodiments described herein are not necessarily mutually exclusive, because 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 intended only to facilitate understanding of the manner in which the embodiments of this article can be practiced, and further enable those skilled in the art to practice the embodiments of this article. Therefore, the examples should not be interpreted as limiting the scope of the embodiments of this article.

[0046] The terms "comprises," "comprising," "includes," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a setup, apparatus, or method that includes a list of components or steps includes not only those components or steps, but may include other components or steps not expressly listed or inherent to such setup, apparatus, or method. In other words, one or more elements in a system or device followed by "comprising" does not exclude the presence of other or additional elements in the system or method without more constraints.

[0047] It should be understood that the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces. " / " means "and / or", for example, "first / second node" means the first node and the second node, or either the first node or the second node.

[0048] The term "includes" or "may include" means that there are corresponding disclosed functions, operations or components that can be used in various embodiments of the present disclosure, and one or more additional functions, operations or components are not limited. Terms such as "includes" and / or "having" may be interpreted as indicating a certain characteristic, quantity, step, operation, constituent element, component or combination thereof, but may not be interpreted as excluding the possibility of the existence or addition of one or more other characteristics, quantities, steps, operations, constituent elements, components or combinations thereof.

[0049] The term "or" used in various embodiments of the present disclosure includes any or all combinations of the listed terms. For example, the expression "A or B" may include A, may include B, or may include both A and B.

[0050] It should be understood that the combination of the blocks and flowcharts in each flowchart can be performed by computer program instructions. Since the computer program instructions can be equipped in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate a device for performing the functions described in the blocks in conjunction with each flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable memory that can be oriented to a computer or other programmable data processing device to implement the functions in a specified manner, the instructions stored in the computer-usable or computer-readable memory can produce a product including an instruction device for performing the functions described in conjunction with the blocks in each flowchart. Since the computer program instructions can be equipped in a computer or other programmable data processing device, the instructions that generate the process executed by the computer as a series of operations are executed on the computer or other programmable data processing device and the operation of the computer or other programmable data processing device can provide operations for performing the functions described in conjunction with the (one or more) blocks in each flowchart.

[0051] In addition, each box can represent a module, a fragment or a portion of a code including one or more executable instructions for performing a specified logical function. In addition, it should be noted that in some alternative execution examples, the functions mentioned in the box can occur in different orders. For example, depending on the corresponding functions, two boxes shown in succession can be executed substantially simultaneously or in reverse order.

[0052] As used herein, the term "unit" means a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A unit plays a certain role. However, the term "unit" is not limited to meaning a software or hardware element. A "unit" can be configured in a storage medium that can be addressed, or can be configured to reproduce one or more processors. Therefore, as an example, a "unit" includes elements such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data architectures, tables, arrays, and variables. The functions provided in an element or "unit" can be combined with additional elements, or can be divided into sub-elements or sub-units. In addition, an element or "unit" can be implemented to reproduce one or more central processing units (CPUs) in a device or a secure multimedia card. According to an embodiment of the present disclosure, a "... unit" can include one or more processors.

[0053] As is conventional in the art, embodiments are described and illustrated according to the blocks that perform the described one or more functions. These blocks, referred to herein as managers, units, modules, hardware components, etc., 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, hard-wired circuits, etc.), and are optionally driven by firmware and software. For example, the circuit is implemented in one or more semiconductor chips, or is implemented on substrate supports such as printed circuit boards, etc. The circuits that constitute the blocks are implemented by dedicated hardware, or by a processor (for example, one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware that performs some functions of the block and a processor that performs other functions of the block. Without departing from the scope of the proposed method, each block of the embodiment is physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of the proposed method, the blocks of the embodiment are physically combined into more complex blocks.

[0054] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the proposed method is interpreted as extending to any changes, equivalents and substitutes other than those specifically set forth 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 element.

[0055] Therefore, embodiments of the present invention provide a method for handling EES failures to generate a service elastic EEL in an edge network. The method includes receiving a push request message from a first EES in a plurality of EESs by a second EES in a plurality of EESs to back up content stored at the first EES so as to synchronize with the second EES. In addition, the method includes verifying and authorizing the first EES based on a push request message received from the first EES by the second EES. The method also includes backing up content stored in the first EES by the second EES by storing the content in the second EES based on the push request message.

[0056] Therefore, the embodiments herein provide a method for handling EES failures to generate service resilience in an EEL of an edge network. The method includes receiving a pull request message from a second EES in a plurality of EESs by a first EES in a plurality of EESs to back up content stored at the first EES for synchronization with the second EES, and enabling communication between the second EES and the EEC in the EEL of the edge network. In addition, the method includes verifying and authorizing the second EES by the first EES based on a pull request message received from the second EES. The method also includes sending a response by the second EES including content stored in the first EES to back up in the second EES based on the pull request message.

[0057] Accordingly, the embodiments herein provide a method for handling EES failures so that the EEL in the edge network has service resilience. The method includes receiving a push request message from a first EES in a plurality of EESs by an EES data repository to back up the content stored at the first EES to synchronize with a second EES. The method includes authorizing the first EES by the EES data repository based on a push request message received from the first EES. In addition, the method includes storing content for backup and synchronization with a second EES by the EES data repository based on the received push request message. The method also includes receiving a pull request message from a second EES in a plurality of EESs by the EES data repository to obtain content stored by the first EES for synchronization with the second EES, and enabling communication between the second EES and the EEC in the EEL of the edge network. The EES data repository includes the content of the first EES for synchronization with at least one second EES associated with the first EES in the EEL of the edge network. In addition, the method includes sending a response containing content to be backed up at the second EES by the EES data repository.

[0058] Therefore, the embodiments herein provide a system for handling failures of EES so that the EEL in the edge network has service resilience. The EEL in the edge network includes a first EES and a second EES in a plurality of EESs. The second EES includes a memory, a processor coupled to the memory, a communicator coupled to the processor, and an EES elastic controller coupled to the memory, the processor, and the communicator. The EES elastic controller is configured to receive a push request message from a first EES in a plurality of EESs to back up content stored at the first EES so as to synchronize with the second EES, and to enable communication between the second EES and the EEC in the EEL of the edge network. The EES elastic controller is configured to verify and authorize the first EES based on a push request message received from the first EES. The EES elastic controller is also configured to back up content stored in the first EES by storing the content in the second EES based on a push request message.

[0059] Therefore, the embodiments herein provide a system for handling EES failures to make the EEL in the edge network have service resilience. The EEL in the edge network includes a first EES and a second EES in a plurality of EESs. The first EES includes a memory, a processor coupled to the memory, and a communicator coupled to the processor, and an EES resilience controller coupled to the memory, the processor, and the communicator. The EES resilience controller is configured to receive a pull request message from a second EES in a plurality of EESs to back up the content stored at the first EES so as to synchronize with the second EES, and enable communication between the EEC in the second EES and the EEL of the edge network. The EES resilience controller is configured to verify and authorize the second EES based on the pull request message received from the second EES. The EES resilience controller is also configured to send a response including the content stored at the first EES to the backup at the second EES based on the pull request message.

[0060] Therefore, embodiments herein provide a system for handling EES failures to enable an EEL in an edge network to have service resilience. The EEL in the edge network includes an EES data repository. The EES data repository includes a memory, a processor coupled to the memory, and a communicator coupled to the processor, and an EES resilience controller coupled to the memory, the processor, and the communicator. The EES resilience controller is configured to receive a push request message from a first EES in a plurality of EESs to back up content stored at the first EES for synchronization with a second EES. The EES resilience controller is configured to authorize the first EES based on a push request message received from the first EES. The EES resilience controller is configured to store content for backup and synchronization with a second EES based on the received push request message. The EES resilience controller is also configured to receive a pull request message from a second EES in a plurality of EESs to obtain content stored by the first EES for synchronization with the second EES, and to enable communication between the second EES and an EEC in the EEL of the edge network. The EES data repository includes the content of the first EES for synchronization with a second EES associated with the first EES in the EEL of the edge network. Additionally, the EES resiliency controller is configured to send the content to a second EES for backup.

[0061] In conventional methods, when EES faces any failure problem, such as unfortunate shutdown, system crash, hardware failure, software failure, etc., the conventional method does not have any effective way to handle the failure problem. Due to the sudden failure of EES, AC and EAS are affected by not receiving data from EES in a consistent manner.

[0062] Unlike conventional methods, in order to provide effective services to AC and EAS, EEL continues to provide services to AC and EAS in the event of a source EES failure. EEL has the ability to recover from failures and maintain the durability of service reliability in the event of failures. The proposed method provides a system and method for handling failures of source EES and allowing EEL to have service resilience to failures of source EES.

[0063] Unlike the traditional method, once the source EES faces any failure problem, the source EES performs a synchronization operation to synchronize the content to the backup EES configured under the source EES. Once the source EES synchronizes the content to the backup EES, AC and EAS receive services from the backup EES.

[0064] The terms "secondary EES" and "backup EES" are used interchangeably throughout this specification.

[0065] The terms "first EES" and "primary or source EES" are used interchangeably throughout this specification.

[0066] In an embodiment, to ensure that the EEL continues to provide services to the AC and EAS in the event of a failure of each EES registered to the ECS, the service provider provides a list of backup EESs. Each backup EES list has a backup EES list identifier to identify the backup EES list.

[0067] Referring now to the drawings, and more particularly to FIGS. 1 to Figure 6 , wherein like reference characters denote corresponding features consistently throughout the Figures, there are shown preferred embodiments.

[0068] Figure 1aA block diagram of a first EES (100a) according to an embodiment as disclosed herein is illustrated. The first EES (100a) includes a memory (101a), a processor (102a) coupled to the memory (101a), a communicator (103a) coupled to the processor (102a), and an EES elasticity controller (104a) connected to the memory (101a), the processor (102a) and the communicator (103a). The EES elasticity controller (104a) is configured to receive a pull request message from a second EES (100b) of a plurality of EESs (100a-n) to back up content stored at the first EES (100a) for synchronization with the second EES (100b), and to enable communication between the second EES (100b) and an EEC (not shown in the figure) in an EEL of an edge network. The EES elasticity controller (104a) is configured to verify the second EES (100b) based on the pull request message received from the second EES (100b). Furthermore, the EES elasticity controller (104a) is configured to send the content stored in the first EES (100a) to back up the second EES (100b) based on the pull request message.

[0069] The memory (101a) is configured to store instructions to be executed by the processor (102a). The memory (101a) includes a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable memory (EEPROM). In addition, in some examples, the memory (101a) is considered to be a non-transitory storage medium. The term "non-transitory" indicates that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" is not interpreted as the memory (101a) being non-removable. In some examples, the memory (101a) is configured to store a larger amount of information. In some examples, the non-transitory storage medium stores data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0070] The processor (102a) includes one or more processors. The one or more processors are general-purpose processors such as a central processing unit (CPU), an application processor (AP), a graphics processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-specific processor such as a neural processing unit (NPU). The processor (102a) includes multiple cores and is configured to execute instructions stored in the memory (101a).

[0071] In an embodiment, the communicator (103a) includes electronic circuitry specific to a standard implementing wired or wireless communications.The communicator (103a) is configured to communicate internally between internal hardware components of the first EES (100a) and to communicate with external devices via one or more networks.

[0072] In an embodiment, the response to the pull request message includes content that needs to be backed up at the second EES (100b). The content includes a list of EEC contexts associated with the first EES, a list of EAS profiles associated with the first EES, an indication to back up content associated with the first EES, details about subscriptions on different edge interfaces, and a list of second EESs from multiple EESs configured at the first EES for backing up content for synchronization, wherein the indication indicates a request for EES synchronization. The indication also indicates a Boolean flag with a true / false value or a name of a message or a name of an event or any other content.

[0073] In an embodiment, the first EES (100a) further includes a database (107a) configured to store a list of EEC contexts associated with the first EES, a list of EAS profiles associated with the first EES, details about subscriptions on different edge interfaces, and a list of second EESs from the plurality of EESs (100a-n).

[0074] In an embodiment, the EES elastic controller (104a) includes a pull request receiver (105a), a verifier (106a), an authorizer (108a), and a pull response transmitter (109a). The pull request receiver (105a) receives a pull request message from a second EES (100b) and sends the pull request message to the verifier (106a). The verifier (106a) is configured to verify the second EES (100b) based on the pull request message received from the second EES (100b). The verifier (106a) checks the identity of the second EES (100b) by comparing the list of the second EES stored in the database (107a). After comparison, the verifier (106a) sends the verification result to the authorizer (108a). The authorizer (108a) is configured to check the result received from the verifier (106a). When the second EES (100b) is successfully authenticated, the authorizer (108a) authorizes the second EES (100b). When the authentication result fails, the authorizer (108a) rejects the pull request message received from the second EES (100b). The authentication failure indicates that the second EES is not a backup of the first EES (100a), and the second EES is not in the same EES set of the first EES.

[0075] In an embodiment, the EES set refers to a set including a plurality of EESs (101a-n). Among the plurality of EESs (101a-n), at least one EES acts as a source EES, and the remaining EESs act as backup EESs.

[0076] In an embodiment, upon successful authentication, the authorizer (108a) sends an authorization message to the pull response transmitter (109a). The pull response transmitter (109a) sends the authorization message to the second EES (100b), wherein the authorization message indicates that the second EES (100b) is authorized based on the success of the authentication result received from the authenticator (106a).

[0077] In an embodiment, when the verification result fails, the authorizer (108a) sends a rejection message to the pull response transmitter (109a). The pull response transmitter (109a) sends the rejection message to the second EES (100b), wherein the rejection message is transmitted to the second EES (100b) to reject the second EES based on the failed verification result received from the verifier (106a).

[0078] The EES elastic controller (104a) is implemented by processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and is optionally driven by firmware. For example, the circuits are implemented in one or more semiconductor chips, or on a substrate support such as a printed circuit board.

[0079] At least one of the multiple modules / components of the EES elastic controller (104a) is implemented by an AI model. Functions associated with the AI ​​model are performed by the memory (101a) and the processor (102a). One or more processors control the processing of input data according to predefined operating rules or AI models stored in non-volatile memory and volatile memory. The predefined operating rules or artificial intelligence models are provided by training or learning.

[0080] Here, providing by learning means making an AI model of predefined operation rules or desired characteristics by applying a learning process to a plurality of learning data. The learning is performed in the device itself that executes the AI ​​according to the embodiment, and / or is implemented by a separate server / system.

[0081] The AI ​​model consists of multiple neural network layers. Each layer has multiple weight values, and the layer operation is performed by the calculation of the previous layer and the operation of multiple weights. Examples of neural networks include, but are not limited to, convolutional neural networks (CNNs), deep neural networks (DNNs), recurrent neural networks (RNNs), restricted Boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), generative adversarial networks (GANs), and deep Q networks.

[0082] The learning process is a method for training a predetermined target device (e.g., a robot) using a plurality of learning data to enable, allow, or control the target device to make a determination or prediction. Examples of the learning process include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0083] Figure 1b A block diagram of a second EES (100b) according to an embodiment as disclosed herein is illustrated. The second EES (100b) includes a memory (101b), a processor (102b) coupled to the memory (101b), a communicator (103b) coupled to the processor (102b), and an EES elastic controller (104b) connected to the memory (101b), the processor (102b) and the communicator (103b). The EES elastic controller (104b) is configured to receive a push request message from a first EES (100a) among a plurality of EESs (100a-n) to back up content stored at the second EES (100b) for synchronization with the first EES (100a), and to enable communication between the first EES (100a) and an EEC (not shown in the figure) in an EEL of an edge network. The EES elastic controller (104b) is configured to authenticate the first EES (100a) based on the push request message received from the first EES (100a). Furthermore, the EES elastic controller (104b) is configured to send the content stored in the second EES (100b) to back up the first EES (100a) based on the push request message.

[0084] The memory (101b) is configured to store instructions to be executed by the processor (102b). The memory (101b) includes a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of EPROM or EEPROM memory. In addition, the memory (101b) is considered to be, for example, a non-temporary storage medium. The term "non-temporary" indicates that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-temporary" should not be interpreted as the memory (101b) being non-removable. In some examples, the memory (101b) is configured to store a larger amount of information. In some examples, the non-temporary storage medium stores data that can change over time (e.g., in RAM or cache).

[0085] The processor (102b) includes one or more processors. The one or more processors are general-purpose processors (such as CPUs, APs, etc.), graphics processing units (such as GPUs, VPUs), and / or AI-specific processors (such as NPUs). The processor (102b) includes multiple cores and is configured to execute instructions stored in the memory (101b).

[0086] In an embodiment, the communicator (103b) includes electronic circuitry specific to a standard implementing wired or wireless communications.The communicator (103b) is configured to communicate internally between internal hardware components of the second EES (100b) and to communicate with external devices via one or more networks.

[0087] In an embodiment, the push request message includes content that needs to be backed up at the second EES (100b). The content includes a list of EEC contexts associated with the first EES, a list of EAS profiles associated with the first EES, an indication to back up content associated with the first EES, details about subscriptions on different edge interfaces, and a list of second EESs from a plurality of EESs configured at the first EES for backing up content for synchronization.

[0088] In an embodiment, the second EES (100b) further includes a database (107b) configured to store content received from the first EES (100a) based on the received push request message, details about subscriptions on different edge interfaces, and an identifier of the first EES (100a) among the multiple EESs (100a-n).

[0089] In an embodiment, the EES elastic controller (104b) includes a push request receiver (105b), a verifier (106b), an authorizer (108b) and a push response transmitter (109b). The push request receiver (105b) receives a push request message from a first EES (100a) and sends the push request message to the verifier (106b). The verifier (106b) is configured to verify the first EES (100a) based on the push request message received from the first EES (100a). The verifier (106b) is configured to check the identity of the first EES (100a) by comparing with an identifier of the first EES (100a) in a plurality of EESs (100a-n) stored in a database (107b). After the comparison, the verifier (106b) sends the result to the authorizer (108b). The authorizer (108b) is configured to check the result received from the verifier (106b). Upon successful authentication, the authorizer (108b) authorizes the first EES (100a) to back up the content stored in the first EES (100a), and when the authentication result fails, the authorizer (108b) rejects the push request message received from the first EES (100a). The failed authentication indicates that the first EES is not the source of the second EES (100b) and the first EES is not in the same EES set of the second EES.

[0090] In an embodiment, when the verification result is successful, the authorizer (108b) sends an authorization message to the push response transmitter (109b). The push response transmitter (109b) sends the authorization message to the first EES (100a), wherein the authorization message indicates the successful authorization of the first EES (100a) based on the verification result received from the authenticator (106b).

[0091] In an embodiment, when the verification result fails, the authorizer (108b) sends a rejection message to the push response transmitter (109b). The push response transmitter (109b) sends the rejection message to the first EES (100a), wherein the rejection message is transmitted to the first EES (100a) to reject the first EES based on the failed verification result received from the verifier (106b).

[0092] The EES elastic controller (104b) is implemented by processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and is optionally driven by firmware. For example, the circuits are implemented in one or more semiconductor chips, or on a substrate support such as a printed circuit board.

[0093] At least one of the multiple modules / components of the EES elastic controller (104b) is implemented by an AI model. Functions associated with the AI ​​model are executed by the memory (101b) and the processor (102b). One or more processors control the processing of input data according to predefined operating rules or AI models stored in non-volatile memory and volatile memory. The predefined operating rules or artificial intelligence models are provided by training or learning.

[0094] Here, providing by learning means making an AI model of predefined operation rules or desired characteristics by applying a learning process to a plurality of learning data. The learning is performed in the device itself that executes the AI ​​according to the embodiment, and / or is implemented by a separate server / system.

[0095] The AI ​​model consists of multiple neural network layers. Each layer has multiple weight values, and the layer operation is performed by the calculation of the previous layer and the operation of multiple weights. Examples of neural networks include, but are not limited to, CNN, DNN, RNN, RBM, DBN, BRDNN, GAN, and Deep Q Network.

[0096] The learning process is a method for training a predetermined target device (e.g., a robot) using a plurality of learning data to enable, allow, or control the target device to make a determination or prediction. Examples of the learning process include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0097] Figure 2 is a flow chart (200) illustrating a method for synchronizing a first EES (100a) and a second EES (100b) based on a push mechanism according to embodiments as disclosed herein.

[0098] The terms "push request message", "context push request" and "push mechanism" are used interchangeably throughout the specification.

[0099] In step 210, in order to synchronize with all backup EES (100b-n), the primary / source EES (100a) sends an EEC context push request to each backup EES (100b) in the plurality of backup EES (100b-n). The context push request additionally contains information required for synchronization as shown in Table 1. The context push request includes content such as a list of EEC contexts, a list of EAS profiles, an indication of backup EES synchronization, a backup EES list identifier, and details about subscriptions on different edge interfaces. The list of EEC contexts indicates the number of EECs that obtain services from the first EES (100a). The EEC context list of the context push request is sent to the plurality of backup EES (100b-n) to synchronize with the plurality of backup EES (100b-n). The list of EAS profiles indicates the number of EASs registered with the first EES (100a). The list of EAS profiles of the context push request is sent to the plurality of backup EES (100b-n) to synchronize with the plurality of backup EES (100b-n). The backup EES synchronization indication indicates a request for synchronizing content with a plurality of backup EESs (100b-n). The backup EES list identifier indicates the number of backup EESs (100b-n) configured under the first EES (100a).

[0100]

Table 1

[0101]

[0102] At step 220, once the backup EES (100b) receives the context push request from the source / primary EES (100a), the backup EES (100b) authenticates and authorizes the primary / source EES (100a) based on the received context push request.

[0103] At step 230, when the primary / source EES (100a) is authorized and part of the same EES set, the backup EES (100b) requests storage content stored at the primary / source EES based on a push and information for synchronization, such as an EEC context list and an EAS profile list.

[0104] In an embodiment, the first EES sends content, as shown in Table 1, to synchronize with the backup EES (100b-n) in a separate request message. The various actions, behaviors, blocks, steps, etc. in the method are performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. are omitted, added, modified, skipped, etc. without departing from the scope of the proposed method.

[0105] Figure 3is a flow chart (300) illustrating a method for synchronizing a first EES (100a) and a second EES (100b) based on a pull mechanism according to embodiments as disclosed herein.

[0106] The terms "pull mechanism", "contextual pull request", and "pull request message" are used interchangeably throughout this specification.

[0107] In step 310, in order to synchronize with the primary / source EES (100a), the backup EES (100b) sends an EES context pull request to the primary / source EES (100a). The context pull request further includes an indication for indicating that the context pull request is for content or context synchronization, as shown in Table 2. The context pull request includes content, such as an indication of backup EES synchronization and a backup EES list identifier. The indication of backup EES synchronization represents a request for synchronizing content with multiple backup EESs (100b-n). The backup EES list identifier represents the number of backup EESs (100b-n) configured under the first EES (100a).

[0108]

Table 2

[0109]

[0110] At step 320, once the primary / source EES (100a) receives the EES context pull request, the primary / source EES (100a) authenticates and authorizes the backup EES (100b).

[0111] At step 330, when the backup EES (100b) is authorized (check if the backup EES is part of the backup EES list in the EES set), the source EES (100a) sends a context pull response containing the content stored at the primary / source EES (100a) to be backed up at the backup EES based on the pull request. The context pull response includes information such as a list of EEC contexts, a list of EAS profiles as specified in Table 3.

[0112]

Table 3

[0113]

[0114] In an embodiment, the second EES (100b) sends a request to the first EES (100a) to send content for synchronization with the second EES (100b) in any other request message. The various actions, behaviors, blocks, steps, etc. in the method are performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. are omitted, added, modified, skipped, etc. without departing from the scope of the proposed method.

[0115] Figure 4a An interface connecting a first EES (100a) and an EES data repository (400) according to an embodiment disclosed herein is shown. In order to synchronize with a primary / source EES (100a), an EES data repository (400) is defined that stores all information (e.g., EEC context list, EAS configuration file list, etc.) that needs to be synchronized with each backup EES (100b) in a plurality of backup EESs (100b-n). Each backup EES (100b) in a plurality of backup EESs (100b-n) in the backup EES list can access the EES data repository (400).

[0116] In an embodiment, an interface between a first EES (100a) and an EES data repository (400) is defined, which is referred to as interface-X or edge-X or edge-N, etc. The interface supports a process for the first EES (100a) to store or update data to synchronize with other backup EESs in a backup EES list. The interface also supports a process for an authorized backup EES to access or obtain data stored in the EES data repository (400).

[0117] In an embodiment, in order to store or update data to an EES data repository (400), a first EES (100a) sends a push request message containing its data (or content) to the EES data repository (400) to store or update (modify / delete) data, such as a list of EEC contexts, a list of EAS profiles, and details about subscriptions on different edge interfaces. The request also includes a backup EES list identifier. The EES data repository (400) authorizes the first EES (100a), and when the first EES (100a) is authorized, the EES data repository (400) stores the data received from the first EES (100a).

[0118] In an embodiment, to obtain or acquire data from the EES data repository (400), the second EES (100b) sends a pull request message to the EES data repository (400), which includes a backup EES list identifier and an EES detail message (whose data needs to be acquired). The EES data repository (400) authorizes the second EES (100b), and when the second EES (100b) is authorized, the EES data repository (400) provides the data in a pull response message.

[0119] Figure 4bA block diagram of an EES data repository (400) according to an embodiment disclosed herein is shown. The EES data repository (400) includes a memory (401), a processor (402) coupled to the memory (401), a communicator (403) coupled to the processor (402), and an EES repository controller (404) coupled to the memory (401), the processor (402) and the communicator (403). The EES repository controller (404) is configured to receive a push request message from a first EES (100a) of a plurality of EESs (100a-n) to back up content stored in the first EES (100a) for synchronization with a second EES (100b). The EES repository controller (404) is further configured to authorize the first EES (100a) based on the push request message received from the first EES (100a). In addition, the EES repository controller (404) is configured to store content for backup and synchronization with a second EES (100b) based on the received push request message. The EES data repository (400) further comprises a database (408) configured to store content received from the first EES (100a) based on the received push request message, details about subscriptions on different edge interfaces, and an identifier of the first EES (100a) of the plurality of EESs (100a-n)

[0120] The memory (401) is configured to store instructions to be executed by the processor (402). The memory (401) includes a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of EPROM or EEPROM memory. In addition, the memory (401) is considered to be, for example, a non-transitory storage medium. The term "non-transitory" indicates that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" is not to be interpreted as the memory (401) being non-removable. In some examples, the memory (401) is configured to store larger amounts of information. In some examples, the non-transitory storage medium stores data that can change over time (e.g., in RAM or cache).

[0121] The processor (402) includes one or more processors. The one or more processors are general-purpose processors (such as CPUs, APs, etc.), graphics processing units (such as GPUs, VPUs), and / or AI-specific processors (such as NPUs). The processor (402) includes multiple cores and is configured to execute instructions stored in the memory (401).

[0122] In an embodiment, the communicator (403) includes electronic circuitry specific to a standard for implementing wired or wireless communications.The communicator (403) is configured to communicate internally between internal hardware components of the EES data repository (400) and to communicate with external devices via one or more networks.

[0123] In an embodiment, an EES data repository (400) is configured to receive a pull request message from a second EES (100b) of a plurality of EESs (100b-n) to obtain content stored by a first EES (100a) for synchronization with the second EES (100b), and to enable communication between the second EES (100b) and an EEC (not shown) in an EEL of an edge network. The EES data repository (400) includes the content of the first EES (100a) for synchronization with a second EES (100b) associated with the first EES (100a) in the EEL of the edge network. In addition, the EES data repository (400) is configured to send the content to the second EES (100b) for backup.

[0124] In an embodiment, an EES data repository (400) includes a push request receiver (405), a push request validator (406), a push request authorizer (407), and a pull response transmitter (412). The push request receiver (405) of the EES data repository (400) is configured to receive a pull request message from a second EES (100b) of a plurality of EESs (100b-n) to obtain content stored by a first EES (100a) for synchronization with the second EES (100b). The push request validator (406) of the EES data repository (400) is configured to check the identity of the first EES (100a) by comparing with an identifier of the first EES (100a) of the plurality of EESs (100a-n) stored in a database (408). The push request authorizer (407) of the EES data repository (400) is configured to authorize the first EES (100a) based on the push request message received from the first EES (100a). Once the first EES (100a) is authorized, the content from the first EES (100a) is stored in the database (408).

[0125] In an embodiment, an EES data repository (400) includes a pull request receiver (409), a pull request validator (410), and a pull request authorizer (411). The pull request receiver (409) of the EES data repository (400) is configured to receive a pull request message from a second EES (100b) of a plurality of EESs (100b-n) to obtain content stored by a first EES (100a) for synchronization with the second EES (100b). The pull request validator (410) of the EES data repository (400) is configured to check the identity of the second EES (100b) by comparing with an identifier of the second EES (100b) in the plurality of EESs (100a-n) stored in a database (408). The pull request authorizer (411) of the EES data repository (400) is configured to authorize the second EES (100b) based on the pull request message received from the second EES (100b). Once the second EES (100a) is authorized, the content in the database (408) is sent to the second EES (100b) via the pull response transmitter (412).

[0126] The EES repository controller (404) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and is optionally driven by firmware. For example, the circuitry is implemented in one or more semiconductor chips, or on a substrate support such as a printed circuit board.

[0127] At least one of the multiple modules / components of the EES repository controller (404) is implemented by an AI model. Functions associated with the AI ​​model are performed by the memory 401 and the processor 402. One or more processors control the processing of input data according to predefined operating rules or AI models stored in non-volatile memory and volatile memory. The predefined operating rules or artificial intelligence models are provided by training or learning.

[0128] Here, providing by learning means making an AI model of predefined operation rules or desired characteristics by applying a learning process to a plurality of learning data. The learning is performed in the device itself that executes the AI ​​according to the embodiment, and / or is implemented by a separate server / system.

[0129] The AI ​​model consists of multiple neural network layers. Each layer has multiple weight values, and the layer operation is performed by the calculation of the previous layer and the operation of multiple weights. Examples of neural networks include, but are not limited to, CNN, DNN, RNN, RBM, DBN, BRDNN, GAN, and Deep Q Network.

[0130] The learning process is a method for training a predetermined target device (e.g., a robot) using a plurality of learning data to enable, allow, or control the target device to make a determination or prediction. Examples of the learning process include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0131] Figure 5 is a flow chart (500) illustrating a method for sending a list of a second EES to an EEC according to embodiments disclosed herein.

[0132] At step 510, the method includes configuring, by the service provider, a list of backup EESs for the first EES (100a).

[0133] At step 520, the method includes: the first EES (100a) performs EES registration, wherein the EES registration message further includes a backup EES list and a backup EES list identifier as shown in Table 4. The first EES (100a) indicates the backup EES list to the ECS (600) in the EES registration.

[0134]

Table 4

[0135] Information / Content illustrate Backing up the EES list Provide backup EES list Backup EES list identifier Identifies a list of backup EES.

[0136] At step 530, the method includes the ECS (600) storing a list of backup EESs for each first EES (100a) of the plurality of EESs (100a-n).

[0137] At step 540, the method includes, once the ECS (600) receives the service provisioning request from the EEC, the ECS sends a service provisioning response to the EEC, wherein the service provisioning response includes a list of EESs in the ECS, an EES set identifier, and a list of backup EESs, as shown in Table 5. The list of backup EESs in the service provisioning response is the same as the list of backup EESs provided when the EES is registered, or a subset thereof.

[0138]

Table 5

[0139] Information / Content illustrate Backing up the EES list Provide backup EES list Backup EES list identifier Identifies a list of backup EES.

[0140] At step 550, the method includes the EEC storing a list of backup EESs for each first EES (100a) of the plurality of first EESs (100a-n). When the first EES (to which the EEC is registered) is unavailable, the EEC uses one of the backup EESs to further communicate and receive services.

[0141] The various actions, behaviors, blocks, steps, etc. in the method are performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. are omitted, added, modified, skipped, etc. without departing from the scope of the proposed method.

[0142] The terms "service provisioning request" and "service provisioning request message" are used interchangeably throughout the specification, and the terms "service provisioning response" and "service provisioning response message" are used interchangeably throughout the specification.

[0143] In an embodiment, the service provisioning request message includes a list of backup EESs and a backup EES list identifier, and the service provisioning response message includes a list of backup EESs or a prioritized list of backup EESs.

[0144] Figure 6 is a flow chart (600) illustrating a method for synchronizing a first EES (100a) and a second EES (100b) by an EES data repository (400) according to embodiments disclosed herein.

[0145] At step 610, the method includes receiving a push request message from a first EES (100a) of a plurality of EESs (100a-n) to back up content stored in the first EES (100a) for synchronization with a second EES (100b).

[0146] At step 620, the method includes authorizing the first EES (100a) based on the push request message received from the first EES (100a).

[0147] At step 630, the method includes storing the content for backup and synchronizing with the second EES (100b) based on the received push request message.

[0148] At step 640, the method includes receiving a pull request message from a second EES (100b) of the plurality of EESs (100a-n) to obtain content stored by the first EES (100a) for synchronization with the second EES (100b).

[0149] At step 650, the method includes sending the content to a second EES (100b) for backup.

[0150] The various actions, behaviors, blocks, steps, etc. in the method are performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. are omitted, added, modified, skipped, etc. without departing from the scope of the proposed method.

[0151] In an embodiment, the indication in the pull request message is used to indicate to the primary EES (100a) that the request is for content synchronization.

[0152] In an embodiment, the list of EEC contexts in the pull response message and the push request message is used to provide registered EECs for synchronization.

[0153] In an embodiment, the list of EAS profiles in the pull response message and the push request message is used to provide the registered EAS for synchronization.

[0154] In an embodiment, the list of backup EESs in the EES registration request message instructs the ECS about the backup EESs to be used in the service provisioning response.

[0155] In an embodiment, the list of backup EES in the service provisioning response informs the EEC about the backup EES to be used when no response to any service request is received from the primary EES (100a).

[0156] In an embodiment, the EES data repository (400) stores all information required for synchronization between backup EES lists.

[0157] In an embodiment, the interface between the first EES (100a) and the EES data repository (400) is configured to support storing, updating, and retrieving data for synchronization.

[0158] In an embodiment, the first EES (100a) provides a list of backup EESs to the EEC in an EEC registration response.

[0159] In an embodiment, the first EES (100a) provides a list of backup EESs to the EAS in an EAS Registration Response.

[0160] In an embodiment, the first EES (100a) provides a list of backup EESs to the EEC in an EAS discovery response.

[0161] In an embodiment, a list of backup EESs is provided to the EEC, the list containing the backup EESs in a prioritized order, wherein when the primary EES (100a) is unresponsive, the EEC initiates communication to the backup EESs in the provided order.

[0162] In an embodiment, a list of backup EESs is provided to the EAS, the list containing the backup EESs in a prioritized order, wherein when the primary EES (100a) is unresponsive, the EAS initiates communication to the backup EESs in the provided order.

[0163] In an embodiment, when the primary EES (100a) is not responding (due to a failure) and the EEC or EAS first attempts to reach the backup EES from the backup EES list, the EEC or EAS implicitly registers to the backup EES (100b).

[0164] In an embodiment, the EAS is registered to all backup EESs in the backup EES list.

[0165] In an embodiment, synchronization of data between the backup EES from the backup EES list and the primary EESs (100a) occurs regularly (ie, periodically or when the primary EES is scheduled to shut down).

[0166] In an embodiment, the list of backup EESs includes EESs from different EDNs.

[0167] The above description of specific embodiments will fully reveal the general nature of the embodiments herein so that others can easily modify and / or adjust the various applications of such specific embodiments by applying current knowledge without departing from the general concepts, and therefore, such adjustments and modifications are intended to be understood as being within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced by modification within the scope of the embodiments as described herein.

Claims

1. A method of a first edge enabling server (EES) in an edge network, the edge network comprising a first EES and a second EES, wherein the method comprises: receiving a context push request message for a context transfer process from the second EES; In response to the push request message, verify and authorize the second EES; as well as storing the first information included in the context push request message for synchronization with the second EES, and sending a context push response message to the second EES, if the second EES is authorized and the first EES and the second EES are part of the same set of EESs of the edge network, The first information includes at least one of a list of edge enabling client (EEC) contexts and a list of edge application server (EAS) configuration files.

2. The method according to claim 1, in, The first information also includes an indication for context synchronization between the first EES and the second EES.

3. The method according to claim 1, in, The second information included in the context push response message includes at least one of a list of the EEC contexts, a list of the EAS profiles, and an indication for context synchronization between the first EES and the second EES.

4. A method for a second edge enabling server (EES) in an edge network, the edge network comprising at least a first EES and a second EES, the method comprising: Sending a context push request message for a context transfer process to the at least one first EES; as well as receiving a context push response message from the at least one first EES if the second EES is authorized and the at least one first EES and the second EES are part of the same set of EESs of the edge network, wherein the first information included in the context push request message is stored in the at least one first EES, and The first information includes at least one of a list of edge enabling client (EEC) contexts and a list of edge application server (EAS) configuration files.

5. The method according to claim 4, in, The first information included in the context push request message also includes an indication for content synchronization between the at least one first EES and the second EES.

6. The method according to claim 4, further comprising: An EES registration request message is sent to an edge configuration server (ECS), the EES registration request message including an indication for the at least one second EES.

7. The method according to claim 4, in, The second information included in the context push response message includes at least one of a list of the EEC contexts, a list of the EAS profiles, and an indication for context synchronization between the first EES and the second EES.

8. A first edge enabling server (EES) in an edge network, the edge network comprising the first EES and a second EES, wherein the first EES comprises: Memory; communicator; and a processor coupled to the memory and the communicator and configured to: receiving a context push request message for a context transfer process from the second EES, authenticating and authorizing the second EES in response to the push request message, and storing the first information included in the context push request message for synchronization with the second EES, and sending a context push response message to the second EES, if the second EES is authorized and the first EES and the second EES are part of the same set of EESs of the edge network, The first information includes at least one of a list of edge enabling client (EEC) contexts and a list of edge application server (EAS) configuration files.

9. The first EES according to claim 8, in, The first information also includes an indication for context synchronization between the first EES and the second EES.

10. The first EES according to claim 8, in, The second information included in the context push response message includes at least one of a list of the EEC contexts, a list of the EAS profiles, and an indication for context synchronization between the first EES and the second EES.

11. A second edge enabling server (EES) in an edge network, the edge network comprising at least one first EES and the second EES, the second EES comprising: Memory; communicator; and a processor coupled to the memory and the communicator and configured to: sending a context push request message for a context transfer process to the at least one first EES, and receiving a context push response message from the at least one first EES if the second EES is authorized and the at least one first EES and the second EES are part of the same set of EESs of the edge network, wherein the first information included in the context push request message is stored in the at least one first EES, and The first information includes at least one of a list of edge enabling client (EEC) contexts and a list of edge application server (EAS) configuration files.

12. The second EES according to claim 11, in, The first information included in the context push request message also includes an indication for content synchronization between the at least one first EES and the second EES.

13. The second EES according to claim 11, wherein: The processor is further configured to: An EES registration request message is sent to an edge configuration server (ECS), the EES registration request message including an indication for the at least one second EES.

14. The second EES according to claim 11, in, The second information included in the context push response message includes at least one of a list of the EEC contexts, a list of the EAS profiles, and an indication for context synchronization between the first EES and the second EES.

Images