Method and system for facilitating an interconnection between a plurality of microservices
Patent Information
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- JIO PLATFORMS LTD
- Filing Date
- 2024-09-13
- Publication Date
- 2026-07-08
Smart Images
Figure IN2024051752_20032025_PF_FP_ABST
Abstract
Description
METHOD AND SYSTEM FOR FACILITATING AN INTERCONNECTION BETWEEN A PLURALITY OF MICROSERVICESFIELD OF DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for facilitating an interconnection between a plurality of microservices (MS).BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] The interaction between a Platform Scheduler (PS) microservice and other microservices may introduce latency in the network, especially if the scheduler has to request information / resources from other microservices, thereby affecting system performance. In the current existing solutions, service outages due to scheduling job s / tasks can disrupt communication. As the system grows, the scheduler may need to handle an increasing number of requests to coordinate tasks.
[0005] Thus, there exists an imperative need in the art for a system and method for facilitating an interconnection between a plurality of microservices, which the present disclosure aims to address.SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for facilitating an interconnection between a plurality of microservices. The method includes receiving, by a transceiver unit at a microservice platform, a request from one or more microservices to create at least one task. Next, the method includes determining, by a determination unit at the microservice platform, whether the requested at least one task already exists in a database. Next, the method includes generating, by a generation unit at the microservice platform, the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist. Next, the method includes scheduling, by a scheduling unit at the microservice platform, the generated at least one task based on a predefined criteria. Next, the method includes receiving, by the transceiver unit at the microservice platform, a trigger for execution of the scheduled at least one task. Next, the method includes fetching, by a fetching unit at the microservice platform, one or more task details from a set of task details stored in a database based on the received trigger. Thereafter, the method includes transmitting, by the transceiver unit at the microservice platform, the fetched one or more task details associated with the request to the one or more microservices for execution.
[0008] In an exemplary aspect of the present disclosure, the task corresponds to at least one of creating task, modifying task, viewing task, and deleting task.
[0009] In an exemplary aspect of the present disclosure, the method further comprises storing, by a storing unit at the microservice platform, the generated at least one task and one or more task details in the database.
[0010] In an exemplary aspect of the present disclosure, wherein the method further comprises an execution unit at the microservice platform configured to initiate the execution of at least one task at the one or more microservices.
[0011] In an exemplary aspect of the present disclosure, the method further comprises determining further comprises querying, by a querying unit, the database to find the at least one task corresponding to the request.
[0012] Another aspect of the present disclosure may relate to a system for facilitating an interconnection between a plurality of microservices. The system comprising a microservice platform. The microservice platform comprising a transceiver unit configured to receive a request from one or more microservices to create at least one task; a determination unit configured to determine whether the at least one task already exists in a database; a generation unit configured to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exists; a scheduling unit configured to schedule the created at least one task based on a predefined criteria; the transceiver unit further configured to a trigger for execution of the scheduled at least one task; a fetching unit configured to fetch one or more task details from a set of task details stored in a database based on the received trigger; the transceiver unit is further configured to transmit the fetched one or more task details associated with the request to the one or more microservices for execution.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for facilitating an interconnection between a plurality of microservices, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive a request from one or more microservices to create at least one task; a determination unit of the system to determine whether the at least one task already exists in a database; a generation unit of the system to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist; a scheduling unit of the system to schedule the created at least one task based on a predefined criteria; the transceiver unit of the system further to a trigger for execution of the scheduled at least one task; a fetching unit of the system to fetch one or more task details from a set of task details stored in a database based on the received trigger; the transceiver unit of the system further to transmit the fetched one or more task details associated with the request to the one or more microservices for execution.OBJECTS OF THE DISCLOSURE
[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for facilitating interaction between one or more microservice with a platform scheduler microservice.
[0016] It is another object of the present disclosure to provide a solution for ensuring platform scheduler and cron jobs (PSC) MS interaction with Elasticsearch (NS) for data storage, enrichment, analysis and visualization.
[0017] It is yet another object of the present disclosure enables other microservices to create, update, visualize and delete variety of tasks at a centralised platform rather than doing operations at their own system and further, ensures PSC MS interaction with Elasticsearch (NS) for scalable and faster performance.DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0019] FIG. 1 illustrates an exemplary block diagram of a management and orchestration (MANO) architecture.
[0020] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0021] FIG. 3 illustrates an exemplary block diagram of a system for facilitating an interconnection between a plurality of microservices, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 4 illustrates a method flow diagram for facilitating an interconnection between a plurality of microservices, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 5 illustrates a sequence flow diagram for facilitating an interconnection between a plurality of microservices, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 6 illustrates an exemplary system architecture of a platform scheduler and cron jobs (PSC / PS) microservice, in accordance with exemplary implementations of the present disclosure.
[0025] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION
[0026] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0027] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0028] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skills in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0029] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0030] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.
[0031] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0032] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wirelesscommunication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0033] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0034] As used herein “interface” or “user interfaces” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0035] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0036] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.
[0037] As used herein, the term Platform Scheduler (PS) microservice or Platform Scheduler and cron jobs (PSC OR PS) microservice is interchangeably used in the specification.
[0038] As used herein, Platform schedulers and cron jobs (PSC / PS) schedules the task such as but not limited to triggering of an event, traversing the network graph etc.
[0039] As used herein, load balancer refers to such as, device, unit, server or service which manages incoming and outgoing network traffic load. Load balancer stores details of the at least available servers, server details, storage, microservices and microservice instances. Load balancer manages the traffic load by directing and distributing incoming or outgoing traffic to the healthy servers or resources.
[0040] As used herein, microservice refers to such as, unit, node, server loosely coupled, independent deployable services specialized for performing specific functions and business services and communicating with other services through well-defined interfaces or application programming interfaces (APIs).
[0041] As used herein, Edge Load Balancer (ELB) refers to a service, unit, platform for managing and distributing incoming traffic efficiently across a group of supported servers, microservices and units in a manner that may increase speed and performance of the network. ELB is used to send the requests between the active instances of one microservice to another microservice.
[0042] As used herein, Event Routing Management (ERM) refers to such as, node, server, service or platform for monitoring and triggering various actions or responses within the system based on detected events. For example, for any microservice instance down, the ERM may trigger any alert for taking an action to overcome the service breakdown condition in the network. ERM is used to send the requests between publisher microservice to subscriber microservice.
[0043] As used herein, PSC service acts as a centralised platform that helps to create and schedule jobs on behalf of other microservices. To perform creating tasks and scheduling jobs, PSC needs to maintain the data in Elasticsearch (NS) so that data can be used for future uses. So, with the help of this PSC MS interacts with Elasticsearch (NS) for fetching the data and providing the relevant information to other MS so that the latter MS can use that data to perform its own business logic.
[0044] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system for facilitating an interconnection between a plurality of microservices. The present disclosure is implemented with the help of various components of a management and orchestration (MANO) architecture.
[0045] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0046] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture
[0100] , in accordance with the exemplary implementation of the present disclosure. The MANO architecture
[0100] is developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of a network node(s) etc. The MANO architecture
[0100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native / Container Network Function (CNF). The system may comprise one or more components of the MANO architecture. The MANO architecture
[0100] is used to auto-instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform.
[0047] As shown in FIG. 1, the MANO architecture
[0100] comprises a user interface layer, a network function virtualization (NFV) and software defined network (SDN) design function module
[0104] ; a platforms foundation services module
[0106] , a platform core services module
[0108] and a platform resource adapters and utilities module
[0112] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0048] The NFV and SDN design function module
[0104] further comprises a VNF lifecycle manager (compute)
[1042] ; a VNF catalogue
[1044] ; a network services catalogue
[1046] ; a network slicing and service chaining manager
[1048] ; a physical and virtual resource manager
[1050] and a CNF lifecycle manager
[1052] , The VNF lifecycle manager (compute)
[1042] is responsible for on which server of the communication network the microservice will be instantiated. The VNF lifecycle manager (compute)
[1042] will manage the overall flow of incoming / outgoing requests during interaction with the user. The VNF lifecycle manager (compute)
[1042] is responsible for determining which sequence to be followed for executing theprocess. For e.g. in an AMF network function of the communication network (such as a 5G network), sequence for execution of processes Pl and P2 etc The VNF catalogue
[1044] stores the metadata of all the VNFs (also CNFs in some cases). The network services catalogue
[1046] stores the information of the services that need to be run. The network slicing and service chaining manager
[1048] manages the slicing (an ordered and connected sequence of network service / network functions (NFs)) that must be applied to a specific networked data packet. The physical and virtual resource manager
[1050] stores the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager (compute)
[1042] , the CNF lifecycle manager
[1052] is similarly used for the CNFs lifecycle management.
[0049] The platforms foundation services module
[0106] further comprises a microservices elastic load balancer
[1062] ; an identify & access manager
[1064] ; a command line interface (CLI)
[1066] ; a central logging manager
[1068] ; and an event routing manager
[1070] , The microservices elastic load balancer
[1062] is used for maintaining the load balancing of the request for the services. The identify & access manager
[1064] is used for logging purposes. The command line interface (CLI)
[1066] is used to provide commands to execute certain processes which require changes during the run time. The central logging manager
[1068] is responsible for keeping the logs of every service. The logs are generated by the MANO architecture
[0100] , The logs are used for debugging purposes. The event routing manager
[1070] is responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.
[0050] The platforms core services module
[0108] further comprises NFV infrastructure monitoring manager
[1082] ; an assure manager
[1084] ; a performance manager
[1086] ; a policy execution engine (PEGN)
[1088] ; a capacity monitoring manager
[1090] ; a release management (mgmt.) repository
[1092] ; a configuration manager & (GCT)
[1094] ; an NFV platform decision analytics (NPDA)
[1096] ; a platform NoSQL DB
[1098] ; a platform schedulers and cron jobs (PSC / PS)
[1100] ; a VNF backup & upgrade manager
[1102] ; a micro service auditor
[1104] ; and a platform operations, administration and maintenance manager
[1106] , The NFV infrastructure monitoring manager
[1082] monitors the infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager
[1084] is responsible for supervising the alarms the vendor is generating. The performance manager
[1086] is responsible for manging the performance counters. The policy execution engine (PEGN)
[1088] is responsible for all the managing the policies. The capacity monitoring manager (CPM)
[1090] is responsible for sending the request to the PEGN
[1088] , The release management (mgmt ) repository (RMR)
[1092] is responsible for managing the releases and the images of all the vendor network node. Theconfiguration manager & (GCT)
[1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA)
[1096] helps in deciding the priority of using the network resources. It is further noted that the policy execution engine (PEGN)
[1088] , the configuration manager & (GCT)
[1094] and the (NPDA)
[1096] work together. The platform NoSQL DB
[1098] is a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. The platform schedulers and cron jobs (PSC / PS)
[1100] schedules the task such as but not limited to triggering of an event, traverse the network graph etc. The VNF backup & upgrade manager
[1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backup on demand in case of server failure. The micro service auditor
[1104] audits the microservices. For e.g., in a hypothetical case, instances not being instantiated by the MANO architecture
[0100] using the network resources then the micro service auditor
[1104] audits and informs the same so that resources can be released for services running in the MANO architecture
[0100] , thereby assuring the services only run on the MANO architecture
[0100] , The platform operations, administration and maintenance manager
[1106] is used for newer instances that are spawning.
[0051] The platform resource adapters and utilities module
[0112] further comprises a platform external API adaptor and gateway
[1122] ; a generic decoder and indexer (XML, CSV, JSON)
[1124] ; a docker swarm adaptor
[1126] ; an OpenStack API adapter
[1128] ; and a NFV gateway
[1130] , The platform external API adaptor and gateway
[1122] is responsible for handling the external services (to the MANO architecture
[0100] ) that requires the network resources. The generic decoder and indexer (XML, CSV, JSON)
[1124] gets directly the data of the vendor system in the XML, CSV, JSON format. The docker swarm adaptor
[1126] is the interface provided between the telecom cloud and the MANO architecture
[0100] for communication. The OpenStack API adapter
[1128] ; is used to connect with the virtual machines (VMs). The NFV gateway
[1130] is responsible for providing the path to each service going to / incoming from the MANO architecture
[0100] ,
[0052] The present disclosure can be implemented on a computing device
[0200] (also referred herein as a computer system
[0200] ) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device
[0200] may also implement a method for facilitating an interconnection between a plurality of microservices utilising the system. In another implementation, the computing device
[0200] itself implements the method for facilitating an interconnection between a plurality of microservices using one or more units configured withinthe computing device
[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0053] The computing device
[0200] may include a bus
[0202] or other communication mechanism for communicating information, and a hardware processor
[0204] coupled with bus
[0202] for processing information. The hardware processor
[0204] may be, for example, a general-purpose microprocessor. The computing device
[0200] may also include a main memory
[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus
[0202] for storing information and instructions to be executed by the processor
[0204] , The main memoiy
[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor
[0204] Such instructions, when stored in non-transitory storage media accessible to the processor
[0204] , render the computing device
[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device
[0200] further includes a read only memory (ROM)
[0208] or other static storage device coupled to the bus
[0202] for storing static information and instructions for the processor
[0204] ,
[0054] A storage device
[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus
[0202] for storing information and instructions. The computing device
[0200] may be coupled viathe bus
[0202] to a display
[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device
[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus
[0202] for communicating information and command selections to the processor
[0204] , Another type of user input device may be a cursor controller
[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor
[0204] , and for controlling cursor movement on the display
[0212] , The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0055] The computing device
[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device
[0200] causes or programs the computing device
[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device
[0200] in response to the processor
[0204] executing one or moresequences of one or more instructions contained in the main memory
[0206] , Such instructions may be read into the main memory
[0206] from another storage medium, such as the storage device
[0210] , Execution of the sequences of instructions contained in the main memory
[0206] causes the processor
[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0056] The computing device
[0200] also may include a communication interface
[0218] coupled to the bus
[0202] , The communication interface
[0218] provides a two-way data communication coupling to a network link
[0220] that is connected to a local network
[0222] , For example, the communication interface
[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface
[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface
[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0057] The computing device
[0200] can send messages and receive data, including program code, through the network(s), the network link
[0220] and the communication interface
[0218] , In the Internet example, a server
[0230] might transmit a requested code for an application program through the Internet
[0228] , the ISP
[0226] , the local network
[0222] , the host
[0224] and the communication interface
[0218] , The received code may be executed by the processor
[0204] as it is received, and / or stored in the storage device
[0210] , or other non-volatile storage for later execution.
[0058] Referring to FIG. 3, an exemplary block diagram of a system
[0300] for facilitating an interconnection between a plurality of microservices is shown, in accordance with the exemplary implementations of the present disclosure. The system
[0300] comprises at least one transceiver unit
[0302] , at least one determination unit
[0304] , at least one generation unit
[0306] , at least one scheduling unit
[0308] , at least one fetching unit
[0310] , at least one execution unit
[0312] , and at least one querying unit
[0314] , Also, all of the components / units of the system
[0300] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 3 only a few units are shown, however, the system
[0300] may comprise multiple such units or the system
[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system
[0300] may be present in a user device toimplement the features of the present invention. The system
[0300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system
[0300] may reside in a server or a network entity. In yet another implementation, the system
[0300] may reside partly in the server / network entity and partly in the user device.
[0059] The system
[0300] is configured for facilitating an interconnection between a plurality of microservices, with the help of the interconnection between the components / units of the system
[0300] , The system
[0300] comprises a microservice platform [300a] In an exemplary aspect, the microservice platform [300a] is a Platform Schedulers & Cron Jobs (PSC / PS)
[1100] , The components / units of the system
[0300] implemented at the microservice platform [300a],
[0060] The system
[0300] comprises a transceiver unit
[0302] , The transceiver unit
[0302] is configured to receive a request from one or more microservices (MS) to create at least one task. The transceiver unit
[0302] at the network platform [300a] is configured to receive the request for creating the at least one task from one or more microservices such as, but not limited to, micro service auditor
[1104] and release management repository MS
[1092] , The task corresponds to at least one of creating task, modifying task, viewing task, and deleting task. In an implementation, at least the task may be associated with auditing of the resources in the network for micro service auditor
[1104] , In an implementation, at least the task may be associated with and releasing resources in the network for release management repository MS
[1092] , In an implementation, the request is received from the one or more microservices (MS) in a format that includes, but not limited only to HTTP format or JSON format.
[0061] The request includes information such as task details, metadata, and other necessary parameters required for the task to be executed. For example, when a microservice responsible for managing user data needs to initiate a backup process, it sends a request to the transceiver unit
[0302] , The transceiver unit
[0302] then receives this request, which includes details about the backup task, such as the type of data to be backed up, the schedule for the backup, and any other relevant instructions. After receiving the request, the transceiver unit
[0302] passes this information along to other components within the system
[0300] , initiating the process of determining whether this task already exists, generating the task if it does not, and scheduling it for execution.
[0062] The system
[0300] comprises a determination unit
[0304] , The determination unit
[0304] is communicatively attached with the transceiver unit
[0302] , The transceiver unit
[0302] sends at leastone task request to the determination unit
[0304] , The determination unit
[0304] at the microservice platform [300a] is configured to determine whether the at least one task already exists in a database. In an implementation, the determination unit
[0304] is configured to determine whether the task associated with auditing of the resources in the network for micro service auditor
[1104] and the task may be associated with and releasing resources in the network for release management repository MS
[1092] exist or not. The system
[0300] further comprises a Querying Unit
[0314] , The Querying Unit
[0314] is configured to query the database to find the at least one task corresponding to the request. In an implementation, the database may store at least one task associated with one or more microservices.
[0063] For example, if a microservice requests the creation of a task for processing customer orders, the transceiver unit
[0302] forwards this task request to the determination unit
[0304] , The determination unit
[0304] then queries the database to check if a task with similar parameters, such as customer order identifier (ID), order type, or execution schedule, already exists. If the determination unit
[0304] finds a matching task in the database, it prevents the creation of a duplicate task by notifying other components in the system that no new task is required.
[0064] The system
[0300] comprises a generation unit
[0306] , The determination unit
[0304] is communicatively attached with the generation unit
[0306] , The determination unit
[0304] determines whether the at least one task already exists or not. If the at least one task already does not exist, the determination unit
[0304] is configured to send the request to generate the at least one task to the generation unit
[0306] , The generation unit
[0306] at the microservice platform [300a] is configured to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist. For example, consider a scenario where a microservice submits a request to process a data migration task. After the transceiver unit
[0302] receives the request and forwards it to the determination unit
[0304] , the determination unit
[0304] checks the database and finds no existing task with similar migration parameters. At this point, the generation unit
[0306] takes over and generates a new task. The task may include details such as the source and destination of the data, the type of data to be migrated, and any time constraints or conditions under which the migration should occur.
[0065] The system
[0300] further comprises a storing unit
[0316] , The storing unit
[0316] is configured to store the generated at least one task and the one or more task details in the database. In an implementation, the storing unit
[0316] may be an elastic search server or database. The elastic search server or database may store task details for the generated at least one task such as, taskname, task identifier, associated micro service (MS) name, creation timestamp, and scheduled time-period for the execution etc.
[0066] The system
[0300] comprises a scheduling unit
[0308] , The generation unit
[0306] is communicatively coupled with the scheduling unit
[0308] , The scheduling unit
[0308] at the microservice platform [300a] is configured to schedule the created at least one task based on a predefined criteria. In an implementation, the scheduling unit
[0308] is configured to schedule the created task based on the predefined criteria such as, but not limited to, periodically, hourly, predefined priority, availability of resources, performance, scalability and cost. In an implementation, the predefined criteria may be received with the received HTTP request.
[0067] For example, when a new task is generated for performing a data analysis operation, the scheduling unit
[0308] examines the predefined criteria, which could include factors such as the priority level of the task, the availability of system resources, or the time window during which the task must be completed. Based on these criteria, the scheduling unit
[0308] assigns a time slot or execution sequence to the task. If the system is busy processing other high-priority tasks, the scheduling unit
[0308] might delay the execution of the new task until resources are available. In another example, if the task involves routine system maintenance, the scheduling unit
[0308] may assign the task to run during off-peak hours, ensuring minimal disruption to ongoing services. The scheduling criteria can be configured to align with business rules, performance goals, or specific service-level agreements (SLAs).
[0068] The scheduling unit
[0308] is communicatively coupled with the transceiver unit
[0302] , The scheduling unit
[0308] is configured to send the details of the scheduled task to the transceiver unit
[0302] , The transceiver unit
[0302] is further configured to a trigger for execution of the scheduled at least one task. In an implementation, the transceiver unit
[0302] is configured to send the trigger to a fetching unit
[0310] for executing at least one task at the scheduled time. In an implementation, for the Micro Service Auditor MS
[1104] the auditing of resources has been scheduled at per hour or network administrator configured period.
[0069] Once the task has been scheduled based on predefined criteria, the transceiver unit
[0302] monitors the execution conditions, such as time or specific system events, and triggers the task when these conditions are met. For example, if a task is scheduled to run at midnight for generating a report, the scheduling unit
[0308] sends the details of this scheduled task, including the exact execution time, to the transceiver unit
[0302] , At the designated time, the transceiver unit
[0302] activates the task by sending a trigger signal to the relevant system components, prompting theexecution of the task. In an exemplary implementation, the trigger for task execution might be based on the completion of a prerequisite task or the availability of specific system resources. The transceiver unit
[0302] can also receive external triggers from other microservices or system events that indicate the conditions for execution have been met. For example, if a data backup task is scheduled to execute only after a data import operation is completed, the transceiver unit
[0302] would wait for a signal from the importing microservice before triggering the backup task.
[0070] The system
[0300] comprises a fetching unit
[0310] , The fetching unit
[0310] is communicatively coupled with the transceiver unit
[0302] , The fetching unit
[0310] is configured to receive the trigger from the transceiver unit
[0302] , Further, the fetching unit
[0310] is configured to fetch one or more task details from a set of task details stored in a database based on the received trigger. In an implementation, the fetching unit
[0310] may fetch one or more task details such as, task name, task identifier, associated micro service (MS) name, creation timestamp, and scheduled time-period for the execution etc. based on the trigger from the database.
[0071] For example, when a task for generating an analytics report is triggered by the transceiver unit
[0302] , the fetching unit
[0310] retrieves the associated task details from the database. These details might include parameters such as the specific data to be analysed, the timeframe for the report, and any user-specific configurations that were previously stored when the task was created. In an exemplary implementation, if the task involves sending a notification to a set of users, the fetching unit
[0310] would retrieve details such as the list of recipients, the message content, and the notification settings.
[0072] The fetching unit
[0310] sends the fetched one or more task details to the transceiver unit
[0302] , The transceiver unit
[0302] of the system
[0300] is further configured to transmit the fetched one or more task details associated with the request to the one or more microservices for execution. The transceiver unit
[0302] is configured to communicate with an execution unit
[0312] , The execution unit
[0312] is configured to execute at the at least one task. The execution unit
[0312] at the microservice platform [300a] is configured to initiate the execution of at least one task at the one or more microservices. In an implementation, the execution unit
[0312] is configured to execute the audit task at Micro Service Auditor MS
[1104] after receiving the fetched task details from the fetching unit
[0310] ,
[0073] For example, a microservice has requested a task to process a set of financial transactions. Once the fetching unit
[0310] retrieves the relevant task details, such as transaction IDs, customer information, and processing rules, it sends this data to the transceiver unit
[0302] , The transceiverunit
[0302] then transmits the data to the microservice responsible for handling the transaction processing. This allows the microservice to execute the task accurately, following the predefined rules and using the detailed information provided. In an exemplary implementation, if a microservice needs to generate a customer notification, the transceiver unit
[0302] would transmit the fetched task details, including customer contact information and the message content, to the notification microservice The microservice would then use this information to send the notification such that the task is executed properly according to the original request.
[0074] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0075] Referring to FIG 4 an exemplary method flow diagram
[0400] , for facilitating an interconnection between a plurality of microservices, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method
[0400] is performed by the system
[0300] , As shown in FIG. 4, the method
[0400] starts at step
[0402] ,
[0076] At step
[0404] , the method
[0400] as disclosed by the present disclosure comprises receiving, by a transceiver unit
[0302] at a microservice platform, a request from one or more microservices to create at least one task. The transceiver unit
[0302] at the network platform [300a] may receive the request for creating the at least one task from one or more microservices such as, but not limited to, micro service auditor
[1104] and release management repository MS
[1092] , The task corresponds to at least one of creating task, modifying task, viewing task, and deleting task. In an implementation, at least the task may be associated with auditing of the resources in the network for micro service auditor
[1104] , In an implementation, at least the task may be associated with and releasing resources in the network for release management repository MS
[1092] , In an implementation, the request is received from the one or more microservices (MS) such as, but not limited to, in from of HTTP or JSON format.
[0077] Next, at step
[0406] , the method
[0400] as disclosed by the present disclosure comprises determining, by a determination unit
[0304] at the microservice platform [300a], whether the requested at least one task already exists in a database. The transceiver unit
[0302] sends at least one task request to the determination unit
[0304] , In an implementation, the determination unit
[0304] may determine whether the task associated with auditing of the resources in the network for micro service auditor MS
[1104] and the task may be associated with and releasing resources in the network for release management repository MS
[1092] exist or not in the database. The system
[0300] further comprises a Querying Unit
[0314] , The Querying Unit
[0314] may query the database to find the at least one task corresponding to the request. In an implementation, the database may store at least one task associated with one or more microservices.
[0078] Next, at step
[0408] , the method
[0400] as disclosed by the present disclosure comprises generating, by a generation unit
[0306] at the microservice platform, the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist. If the at least one task already does not exist, the determination unit
[0304] may send the request to generate the at least one task to the generation unit
[0306] , The generation unit
[0306] at the microservice platform [300a] may generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist. The system
[0300] further comprises a storing unit
[0316] , The storing unit
[0316] may store the generated at least one task and the one or more task details in the database. In an implementation, the storing unit
[0316] may be elastic search server or database. The elastic search server or database may store task details for the generated at least one task such as, task name, task identifier, associated micro service (MS) name, creation timestamp, and scheduled time-period for the execution etc.
[0079] Next, at step
[0410] , the method
[0400] as disclosed by the present disclosure comprises scheduling, by a scheduling unit
[0308] at the microservice platform [300a], the generated at least one task based on a predefined criteria. In an implementation, the scheduling unit
[0308] may schedule the created task based on the predefined criteria such as, but not limited to, periodically, hourly, predefined priority, availability of resources, performance, scalability and cost. In an implementation, the predefined criteria may be received during the receiving of the HTTP request.
[0080] Next, at step
[0412] , the method
[0400] as disclosed by the present disclosure comprises receiving, by the transceiver unit
[0302] at the microservice platform, a trigger for execution of the scheduled at least one task. The method
[0400] implemented by the scheduling unit
[0308] may send the details of the scheduled task to the transceiver unit
[0302] , The transceiver unit
[0302] may furtherreceive a trigger for execution of the scheduled at least one task. In an implementation, the transceiver unit
[0302] may send the trigger to a fetching unit
[0310] for executing at least one task at the scheduled time. In an implementation, for the Micro Service Auditor
[1104] the auditing of resources has been scheduling at per hour or network administrator configured period.
[0081] Next, at step
[0414] , the method
[0400] as disclosed by the present disclosure comprises fetching, by a fetching unit
[0310] at the microservice platform [300a], one or more task details from a set of task details stored in a database based on the received trigger. The fetching unit
[0310] may receive the trigger from the transceiver unit
[0302] , Further, the fetching unit
[0310] may fetch one or more task details from a set of task details stored in a database based on the received trigger. In an implementation, the fetching unit
[0310] may fetch one or more task details such as, task name, task identifier, associated micro service (MS) name, creation timestamp, and scheduled time-period for the execution etc. based on the trigger from the database.
[0082] Next, at step
[0415] , the method
[0400] as disclosed by the present disclosure comprises transmitting, by the transceiver unit
[0302] at the microservice platform, the fetched one or more task details associated with the request to the one or more microservices for execution. The execution unit
[0312] may execute at the at least one task. The execution unit
[0312] at the microservice platform [300a] may initiate the execution at least one task at the one or more microservices. In an implementation, the execution unit
[0312] may execute an audit task at Micro Service Auditor MS
[1104] after receiving the fetched task details from the fetching unit
[0310] ,
[0083] Thereafter, the method
[0400] terminates at step
[0418] ,
[0084] FIG. 5 illustrates a sequence flow diagram
[0500] for facilitating an interconnection between a plurality of microservices, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 5, the sequence flow
[0500] comprises a Platform Schedulers & Cron lobs (PSC / PS)
[1100] , a Microservice (MS)
[0506] and a Elasticsearch (NS)
[0504] ,
[0085] At step SI, the MS
[0506] sends a HTTP request or JSON request to create and schedule a task request to the PSC / PS
[1100] , The task request is sent using either an HTTP or JSON format and is received by the Platform Schedulers & Cron Jobs (PSC / PS)
[1100] , The MS
[0506] may initiate the request for a variety of tasks, such as scheduling data backups, report generation, or any other predefined task.
[0086] At step S2, the PSC / PS
[1100] checks if the request task from the MS
[0506] exists or not via NS
[0504] , The elasticsearch (NS)
[0504] acts as a server or a distributed search and analytics engine. NS
[0504] is used for data ingestion, enrichment, storage, analysis, and visualization. NS
[0504] can process JSON requests and give back JSON data. Elasticsearch (NS)
[0504] is a distributed search and analytics engine that facilitates data management within the system. It functions not only as a search engine but also serves as a database, providing capabilities for data ingestion, storage, enrichment, analysis, and visualization. Elasticsearch (NS)
[0504] stores task- related information such as task names, execution schedules, timestamps, and other relevant details such that the data is easily retrievable when needed. It processes JSON requests from the Platform Schedulers & Cron Jobs (PSC / PS)
[1100] and provides JSON responses, enabling the efficient management of tasks by storing and retrieving information.
[0087] At step S3, in response to the request, the NS
[0504] sends a response to PSC / PS
[1100] about whether the task exists or not.
[0088] At step S4, if the task does not exist, the PSC / PS
[1100] sends a failure response to the MS
[0506] ,
[0089] At step S5, PSC / PS
[1100] creates tasks and stores at the NS
[0504] , The NS
[0504] stores the created task with task details such as, task name, MS
[0506] name, timestamp, execution scheduled time and the like.
[0090] At step S6, after creating the task, PSC / PS
[1100] schedules the task for the MS
[0506] ,
[0091] At step S7, the PSC / PS
[0110] sends a response to the MS
[0506] for a task successfully created and scheduled for the MS
[0506] ,
[0092] At step S8, the PSC / PS
[1100] sends a task trigger at a scheduled time to the MS
[0506] ,
[0093] At step S9, the PSC / PS
[1100] fetches relevant details about the task and task details from the NS
[0504] , Relevant details typically refer to metadata about the task, such as timestamps, task status (e.g., pending, in-progress, or completed), the microservice that created the task, and any predefined execution schedules. These details ensure that the system can track the progress and state of each task over time Elasticsearch allows these details to be quickly accessed and updated, providing fast and scalable querying capabilities.
[0094] Further, task details refers to more specific information directly tied to the task itself. For instance, if a microservice creates a task to back up a database, the task details might include the task name (e.g., "Database Backup"), parameters such as the database being backed up (e g., "CustomerOrdersDB"), the location where the backup will be stored (e.g., " / backups / orders / "), and the frequency or timing of execution (e.g., "every 24 hours at 2 AM").
[0095] At step S10, the NS
[0504] provides relevant stored task information to the PSC / PS
[1100] , Relevant stored task information includes key data such as the task name, ID, microservice origin, creation timestamp, scheduled execution time, task parameters, and status, all stored in Elasticsearch (NS)
[0504] For example, a backup task might include details like "OrderDB Backup," scheduled for daily execution, with parameters like the database name and backup location.
[0096] At step SI 1, the PSC / PS
[1100] notifies the MS
[0506] with relevant task details via HTTP request.
[0097] At step S12, MS
[0506] executes tasks based on the request body and attributes received from the PSC / PS
[1100] , The request body and attributes refers to the information and parameters included in a request sent from the MS
[0506] to the Platform Schedulers & Cron Jobs (PSC / PS)
[1100] system when initiating or executing a task. The request body contains structured data, in JSON format, detailing the task requirements such as task type, execution timing, and any necessary inputs. Attributes refer to additional parameters or metadata that further define how the task should be processed or executed. For example, if a microservice wants to schedule a database backup task, the request body might include the task name ("Database Backup"), execution time ("02:00 AM"), and the database to back up ("CustomerOrdersDB") The attributes could specify additional configurations such as the backup location ("file_path" : " / backups / orders / ") or priority level ("priority": "high").
[0098] Referring to FIG. 6 illustrates an exemplary system architecture
[0600] of a platform scheduler and cron jobs (PSC / PS) microservice, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 6, the system architecture
[0600] of PSC microservice comprises a CRON & Schedulers Management
[0602] , a Cron Management
[0604] , a Task Management
[0606] , a FCAP Management
[0608] , an Event Handling
[0610] , a high availability (HA) and Fault Tolerance
[0612] , a Data Modelling Framework
[0614] , a ES-DB Client
[0616] , a ERM
[0618] , a ES
[0620] , an ELB
[0622] , a VNF manager
[0624] , VM
[0626] (VM1 [626a],. ,VMn [626n]), a GUI Interface
[0628] , a CLI interface
[0630] and EDGE-LB
[0632] ,
[0099] CRON & Schedulers Management
[0602] is used for scheduling of the cron jobs. CRON & Schedulers Management
[0602] is responsible for managing cron jobs and scheduling them at appropriate intervals. Cron jobs are recurring tasks that need to be executed at specified times or based on a regular schedule. The CRON & Schedulers Management
[0602] handles the scheduling logic such that tasks are triggered at the right time and in the correct sequence, considering potential overlaps or delays. For example, if a microservice needs to perform a backup every hour, the CRON & Schedulers Management ensures this task is initiated and monitored.
[0100] Cron Management
[0604] is used to manage all the active and inactive crons created at PSC end. The Cron Management
[0604] works in tandem with the scheduling module to manage all active and inactive cron jobs created by the PSC. The Cron Management
[0604] tracks the lifecycle of each cron job, including its creation, activation, deactivation, and deletion. This ensures that only relevant and necessary cron jobs are actively consuming resources. For example, if ajob is temporarily unnecessary, it can be deactivated to conserve system resources.
[0101] Task Management
[0606] is used to manage all the active and inactive tasks created at PSC end. The Task Management oversees all active and inactive tasks within the system. These tasks could involve a wide range of operations, such as data ingestion, processing, or analysis. For example, if a data aggregation task is set to run after receiving new data from external sources, this module manages its initiation and monitors its progress.
[0102] FCAP management
[0608] manages all the counters and alarms created at PSC. The FCAP Management
[0608] deals with managing fault counters, alarms, and performance metrics within the PSC environment. The FCAP Management
[0608] ensures the health of the platform by monitoring for irregularities or system failures For example, if a task or cron fails to execute as expected, FCAP Management raises an alarm for the operations team to investigate.
[0103] Event Handling
[0610] manages all the events between microservices. The Event Handling module
[0610] facilitates in managing communication between microservices. It handles both inbound and outbound events, allowing microservices to communicate status updates, request information, or trigger tasks in other services. For example, if a microservice completes processing a dataset, it can send an event notification to another microservice, triggering it to initiate its own task.
[0104] High Availability (HA) and Fault Tolerance
[0612] handles all the requests if one running instance goes down, then another active instance will complete that request. The HA and fault tolerance
[0612] manages requests in the event of a failure in any of the microservices. If one running instance goes down, another active instance takes over to complete the request. This prevents system downtime and ensures that ongoing operations are not interrupted. For example, if a server hosting a microservice crashes, HA and Fault Tolerance immediately redirect the task to another server without disrupting the user experience.
[0105] Data Modelling Framework
[0614] is used to manage and check incoming and outgoing format data at PSC end. The Data Modelling Framework
[0614] governs the structure and format of incoming and outgoing data so as to maintain consistency across all microservices when exchanging data. For example, when data is fetched from the Elasticsearch (ES) database, it is transformed into the required format by this framework before being sent to the requesting microservice.
[0106] ERM
[0618] is Event Routing Manager which is used to send the requests between publisher microservice to subscriber microservice. The ERM
[0618] manages the routing of events between publisher and subscriber microservices for enabling asynchronous communication between services. For example, when a task is completed, the ERM
[0618] facilitates that the notification is routed to the correct subscriber microservice for further action.
[0107] ELB
[0622] is Edge Load balancer which is used to send the requests between the active instances of one microservice to another microservice. The ELB manages load distribution between the various instances of a microservice such that the system resources are used efficiently by distributing incoming requests evenly across the available instances. The ELB prevents any single instance from being overwhelmed by too many requests. For example, during peak traffic, the ELB distributes requests to different instances of a microservice to maintain optimal performance.
[0108] ES-DB Client
[0616] and ES
[0620] manage task related data for the microservices at PSC end. The ES-DB Client
[0616] serves as an interface between the PSC and the Elasticsearch (ES) database
[0620] , which stores all relevant data for tasks and jobs. ES
[0620] acts as a distributed search and analytics engine or a database, making it highly scalable for managing large amounts of data for real-time data access and analytics. For example, when a task is created, the ES-DB Client
[0616] stores all task details in ES
[0620] , allowing for quick retrieval when needed.
[0109] VNF manager
[0624] manages the one or more VM
[0626] in a virtual environment in a network functions virtualization (NFV) architecture or virtualized infrastructure. The VNF Manager
[0624] manages the virtualization of network functions and resources within the PSC system The VNF manager
[0624] oversees the allocation and management of virtual machines (VM1 [626a], ..VMn [626n]) that support the execution of tasks in a virtualized infrastructure for environments requiring scalability, as additional virtual machines can be provisioned on demand.
[0110] GUI
[0628] is used to communicate with ERM
[0618] for sending the request to the microservices. The GUI
[0628] provides a user-friendly interface for interacting with the PSC system, allowing administrators or users to monitor task status, schedule jobs, and review system health.
[0111] CLI
[0630] is used to communicate or trigger the EDGE-LB
[0632] for manging the load of the microservices. The CLI
[0630] serves a similar function but is intended for advanced users who prefer text-based commands to interact with the system. Both interfaces enable users to trigger events, create tasks, or check system metrics. The EDGE-LB
[0632] is responsible for managing load across edge devices or services in the network for optimal performance and service delivery by balancing requests and workloads across geographically distributed servers or devices.
[0112] All components and units communicate with each-other for scheduling and managing a task request. In a used case scenario, for example three instances of the PSC microservices, such as, instance 1, instance 2 and instance 3 are available in the network. If one of the instances, such as instance 2 goes down, these components / units switch or schedule the task of the instance 2 to the instance 1 or instance 3 based on predefined criteria and maintain the high availability of the network.
[0113] The present disclosure may relate to a non-transitory computer readable storage medium storing instructions for facilitating an interconnection between a plurality of microservices, the instructions include executable code which, when executed by one or more units of a system
[0300] , causes: a transceiver unit
[0302] of the system
[0300] to receive a request from one or more microservices to create at least one task request; a determination unit
[0304] of the system
[0300] to determine whether the at least one task already exists; a generation unit
[0306] of the system
[0300] to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist, a scheduling unit
[0308] of the system
[0300] to schedule the created at least one task based on a predefined criteria; the transceiver unit
[0302] of the system
[0300] further to a trigger for execution of the scheduled at least one task; a fetching unit
[0310] of the system
[0300] to fetch one or more task details from a set of task details stored in a database based on the received trigger; the transceiver unit
[0302] of the system
[0300] further to transmit the fetched one or more task details associated with the request to the one or more microservices for execution.
[0114] As is evident from the above, the present disclosure provides a technically advanced method for facilitating interaction between one or more microservice with a platform scheduler microservice. The present disclosure provides a solution for ensuring PSC MS interaction with Elasticsearch(NS) for data storage, enrichment, analysis and visualization. Also, the present disclosure enables other microservices to create, update, visualize and delete a variety of tasks at a centralised platform rather than doing operations at their own system and further, ensures PSC MS interaction with Elasticsearch(NS) for scalable and faster performance.
[0115] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
Claims
We Claim:
1. A method for facilitating an interconnection between a plurality of microservices, the method comprising:5 - receiving, by a transceiver unit [302] at a microservice platform [300a], a request from one or more microservices to create at least one task; determining, by a determination unit [304] at the microservice platform [300a], whether the requested at least one task already exists in a database;- generating, by a generation unit [306] at the microservice platform [300a], the at least oneID task corresponding to the request in an event it is determined that the at least one task does not already exist; scheduling, by a scheduling unit [308] at the microservice platform [300a], the generated at least one task based on a predefined criteria;- receiving, by the transceiver unit [302] at the microservice platform [300a], a trigger for15 execution of the scheduled at least one task;- fetching, by a fetching unit [310] at the microservice platform [300a], one or more task details from a set of task details stored in the database based on the received trigger; and transmitting, by the transceiver unit [302] at the microservice platform [300a], the fetched one or more task details associated with the request to the one or more microservices for20 execution.
2. The method as claimed in claim 1, wherein the task corresponds to at least one of creating task, modifying task, viewing task, and deleting task.25 3. The method as claimed in claim 1, wherein the method comprises storing, by a storing unit at the microservice platform [300a], the generated at least one task and one or more task details in the database.
4. The method as claimed in claim 1, wherein the method further comprises an execution unit30 [31 ] at the microservice platform [300a] configured to initiate the execution at least one task at the one or more microservices5. The method as claimed in claim 1, wherein determining further comprises querying, by a Querying Unit [314], the database to find the at least one task corresponding to the request.
6. A system for facilitating an interconnection between a plurality of microservices, the system comprising: a microservice platform [300a] comprising: o a transceiver unit [302] configured to receive a request from one or more microservices to create at least one task; o a determination unit [304] configured to determine whether the at least one task already exists in a database; o a generation unit [306] configured to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist; o a scheduling unit [308] configured to schedule the created at least one task based on a predefined criteria; o the transceiver unit [302] further configured to a trigger for execution of the scheduled at least one task; o a fetching unit [310] configured to fetch one or more task details from a set of task details stored in the database based on the received trigger; and o the transceiver unit [302] is further configured to transmit the fetched one or more task details associated with the request to the one or more microservices for execution.
7. The system as claimed in claim 6, wherein the task corresponds to at least one of creating task, modifying task, viewing task, and deleting task.
8. The system as claimed in claim 6, wherein the system comprises storing at a storing unit [316] at the microservice platform [300a], the generated at least one task and the one or more task details in the database.
9. The system as claimed in claim 6, wherein system further comprises an execution unit [312] at the microservice platform [300a] configured to initiate the execution at least one task at the one or more microservices10. The system as claimed in claim 6, wherein the system further comprises a Querying Unit [314] configured to query the database to find the at least one task corresponding to the request.
11. A non-transitory computer readable storage medium storing instructions for facilitating an interconnection between a plurality of microservices, the instructions include executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [302] of the system [300] to receive a request from one or more microservices to create at least one task request; a determination unit [304] of the system [300] to determine whether the at least one task already exists; a generation unit [306] of the system [300] to generate the at least one task corresponding to the request in an event it is determined that the at least one task does not already exist; a scheduling unit [308] of the system [300] to schedule the created at least one task based on a predefined criteria; the transceiver unit [302] of the system [300] further to a trigger for execution of the scheduled at least one task; a fetching unit [310] of the system [300] to fetch one or more task details from a set of task details stored in a database based on the received trigger; and the transceiver unit [302] of the system [300] further to transmit the fetched one or more task details associated with the request to the one or more microservices for execution.