Method and system for managing event routing

Abstract

The present disclosure relates to a method and a system for managing event routing. In one example, a resource breach event creation request may be received from a first node. The resource breach event creation request may include a resource usage data associated with a Network Function (NF). Thereafter, the resource breach event creation request may be transmitted to a Capacity Monitoring Management Platform (CMP), and a response may be received from the CMP. The response may include the resource breach event. The response may be generated by the CMP based on a resource breach event determined by comparing the resource usage data, which may be extracted from the received resource breach event creation request, with a pre-defined threshold. Thereafter, a second node may be notified about the resource breach event.

Description

METHOD AND SYSTEM FOR MANAGING EVENT ROUTINGFIELD OF INVENTION

[0001] Embodiments of the present disclosure relate generally to the field of wireless communication systems. More particularly, embodiment of the present disclosure relates to a method and system for managing event routing of one or more microservices.BACKGROUND

[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the 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] Traditionally, in relation to the disclosed invention, seemingly manifests several substantial inefficiencies and vulnerabilities primarily revolving around the management and routing of interactions within microservices in conventional systems. One of the significant issues in the prior art is the inefficiency in the interaction flow.

[0005] Traditional systems often facilitated the routing of request / response via the same service that also catered to the main functionalities, leading to an interaction flow that was not only slow and inefficient but also highly susceptible to failures, causing considerable delays in operations and impacting overall system performance. Moreover, the lack of a specialized interface for the explicit management of event routing among different microservices is another glaring problem in the prior art. This absence meant that the interaction and communication between microservices were more cumbersome and less optimized, leading to poor coordination and inefficient system processes. This lack of a dedicated interface made it difficult to ensure seamless communication and interaction among the different services, often resulting in fragmented and disjointed system operations. In addition to this, the absence of a robust subscription and notification framework in the prior systems likely led to suboptimal transmission and coordination of events among the microservices. Without such a framework, the efficient and accurate relay of standard platform events became a challenge, causing potential mismanagement and operational bottlenecks, impacting the seamless flow of information and overall system coherence.

[0006] Furthermore, the prior solutions possibly did not focus on implementing asynchronous event-based solutions and might not have emphasized high availability and fault tolerance. Such a lack of emphasis on these crucial aspects would render the systems vulnerable to disruptions, with no immediate mechanisms for recovery or continuity in place, thereby affecting the reliability and availability of services to the end-users.

[0007] Finally, the operational complexities associated with managing various events, like create task events and resource breach events, were likely elevated due to inefficient routing and management interfaces, leading to more convoluted operations and a higher propensity for errors.

[0008] The prior art's limitations and inefficiencies underline a critical need for innovations in event routing and management of microservices to address these prevalent challenges and bolster the robustness, efficiency, and reliability of systems in this domain.

[0009] Thus, there exists an imperative need in the art for a system and method for enhanced event routing and management of microservices, that aims to ensure seamless interaction, high availability, and fault tolerance, overcoming the inefficiencies and susceptibilities to failure inherent in traditional systems.SUMMARY

[0010] 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.

[0011] An aspect of the present disclosure may relate to a method for managing event routing. The method comprises receiving, by a transceiver unit at an Event Routing Manager (ERM), a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF). The method further comprises transmitting, by the transceiver unit at the ERM, the resource breach event creation request to a Capacity Monitoring Management Platform (CMP). Based on the transmitted resource breach event creation request, the method further comprise receiving, by the transceiver unit, a response from the CMP, wherein the response comprises the resource breach event, and wherein the response is generated by the CMP. On receiving the resource breach event creation request from the ERM, the CMP extracts the resource usage data associated with the NF. Based on a comparison of the resource usage data with a pre-defined threshold, the CMP determines a resource breach event associated with the NF. The CMP generates the response based on the determined resource breach event. The method further comprises notifying, by a notifying unit at the ERM, a second node about the resource breach event.

[0012] In an exemplary aspect of the present disclosure, the first node is a Platform Scheduler.

[0013] In an exemplary aspect of the present disclosure, the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

[0014] In an exemplary aspect of the present disclosure, the method further comprises authenticating, by an authentication unit, the received resource breach event creation request. Based on a successful authentication, the method further comprises transmitting, by the transceiver unit, the resource breach event creation request to the CMP.

[0015] In an exemplary aspect of the present disclosure, the Event Routing Manager (ERM) and the Capacity Monitoring Management Platform (CMP) are communicatively coupled over a CP EM interface.

[0016] In an exemplary aspect of the present disclosure, the resource breach event creation request and the response between the ERM and CMP are communicated via a REST application programming interface (API) over hypertext transfer protocol (HTTP).

[0017] In an exemplary aspect of the present disclosure, the resource breach event creation request and the response exchanged between the ERM and CMP is in JSON format.

[0018] In an exemplary aspect of the present disclosure, pursuant to transmission of the resource breach event creation request to the CMP, the method further comprises receiving, by the transceiver unit, a failure response from the CMP, wherein the failure response corresponds to an unavailable status of the CMP. Based on the received failure response, the method further comprises transmitting, by the transceiver unit, the resource breach event creation request to another instance of said CMP.

[0019] In an exemplary aspect of the present disclosure, the second node is a Network Function Virtualization Platform Decision Analytics (NPDA) unit.

[0020] Another aspect of the present disclosure may relate to a system for managing event routing. The system comprises an Event Routing Manager (ERM). The ERM comprises a processing unit and a transceiver unit connected at least to the processing unit. The transceiver unit is configured to receive a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF). The transceiver unit is further configured to transmit the resource breach event creation request to a Capacity Monitoring Management Platform (CMP). Based on the transmitted resource breach event creation request, the transceiver unit is further configured to receive a response from the CMP, wherein the response comprises the resource breach event, and wherein the response is generated by the CMP. On receiving the resource breach event creation request from the ERM, the CMP extracts the resource usage data associated with the NF. Based on a comparison of the resource usage data with a pre-defined threshold, the CMP determines a resource breach event associated with the NF. The CMP generates the response based on the determined resource breach event. The system further comprises a notifying unit connected at least to the transceiver unit. The notifying unit is configured to notify a second node about the resource breach event.

[0021] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing event routing. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit, at an Event Routing Manager (ERM), to receive a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF). Further, the instructions include executable code which, when executed, causes the transceiver unit, at the ERM, to transmit the resource breach event creation request to a Capacity Monitoring Management Platform (CMP). Further, the instructions include executable code which, when executed, causes the transceiver unit to receive a response from the CMP, based on the transmitted resource breach event creation request, wherein the response comprises the resource breach event. The response is generated by the CMP. On receiving the resource breach event creation request from the ERM, the CMP extracts the resource usage data associated with the NF. Based on a comparison of the resource usage data with a pre-defined threshold, the CMP determines a resource breach event associated with the NF. The CMP generates the response based on the determined resource breach event. Further, the instructions include executable code which, when executed, causes a notifying unit, at the ERM, to notify a second node about the resource breach event.OBJECTS OF THE DISCLOSURE

[0022] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0023] It is an object of the present disclosure to provide a system and a method for managing event routing of one or more microservices.

[0024] It is an object of the present disclosure to provide a system and a method for managing event routing of microservices that ensures accurate and reliable transmission of breached responses between differing microservices, rectifying potential inaccuracies and transmission failures inherent in conventional systems.

[0025] It is another object of the present disclosure to provide a system and a method for managing event routing of microservices that facilitates seamless and efficient interaction among all microservices by utilizing a specialized interface for managing both request and response routing, overcoming the inefficiencies of traditional systems.

[0026] It is another object of the present disclosure to provide a system and a method for managing event routing of microservices that employs a subscription and notification framework, enabling each microservice to systematically register and manage standard platform events, ensuring optimal information flow and coordination.

[0027] It is another object of the present disclosure to provide a system and a method for managing event routing of microservices that promotes high availability and fault tolerance through asynchronous event-based implementation, maintaining reliable and continuous operation during instance failures or system downtimes.

[0028] It is another object of the present disclosure to provide a system and a method for managing event routing of microservices that optimizes operational efficiency and time management by simplifying the handling of various events, leading to streamlined processes and enhanced productivity.

[0029] It is yet another object of the present disclosure to provide a system and a method for managing event routing of microservices that improves response mechanisms to resource breach events, facilitating proficient management of instantiation and termination events, and thereby elevating overall system performance and user satisfaction.DESCRIPTION OF THE DRAWINGS

[0030] 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.

[0031] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture.

[0032] 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.

[0033] FIG. 3 illustrates an exemplary block diagram of a system for managing event routing, in accordance with exemplary implementations of the present disclosure.

[0034] FIG. 4 illustrates an exemplary network environment for managing event routing, in accordance with exemplary implementations of the present disclosure.

[0035] FIG. 5 illustrates an exemplary signalling diagram for managing event routing in accordance with exemplary implementations of the present disclosure.

[0036] FIG. 6 illustrates a method flow diagram for managing event routing, in accordance with exemplary implementations of the present disclosure.

[0037] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0038] 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.

[0039] 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.

[0040] 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 skill 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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 wireless communication 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 unit(s) which are required to implement the features of the present disclosure.

[0045] 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.

[0046] As used herein “interface” or “user interface 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.

[0047] 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.

[0048] As used herein the transceiver unit include 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.

[0049] 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 method and system of managing event routing.

[0050] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0051] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture / platform

[0100] , in accordance with exemplary implementation of the present disclosure. The MANO architecture

[0100] may be developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of a network node(s) etc / service(s). 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 as provided by the present disclosure may comprise one or more components of the MANO architecture

[0100] , The MANO architecture

[0100] may be used to automatically 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. In an implementation, the system may comprise a NFV Platform Decision Analytics (NPDA)

[1096] component.

[0052] As shown in FIG. 1, the MANO architecture

[0100] comprises a user interface layer

[0102] , a network function virtualization (NFV) and software defined network (SDN) design function module

[0104] , a platform foundation services module

[0106] , a platform core services module

[0108] and a platform resource adaptors and utilities module

[0112] All the components may be 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.

[0053] The NFV and SDN design function module

[0104] comprises a VNF lifecycle manager

[1042] , a VNF catalog

[1044] , a network services catalog

[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

[1042] may be responsible for deciding on which server of the communication network the microservice may be instantiated. The VNF lifecycle manager

[1042] may manage the overall flow of incoming / outgoing requests during interaction with the user. The VNF lifecycle manager

[1042] may be responsible for determining which sequence to be followed for executing the process. For e.g. in an AMF network function of thecommunication network (such as a 5G network), sequence for execution of processes Pl and P2 etc. The VNF catalog VNF CATALOG stores the metadata of all the VNFs (also CNFs in some cases). The network services catalog

[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

[1042] , the CNF lifecycle manager

[1052] may be similarly used for the CNFs lifecycle management.

[0054] The platforms foundation services module

[0106] comprises a microservices elastic load balancer

[1062] , an identity & 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] may be used for maintaining the load balancing of the request for the services. The identity & access manager

[1064] may be used for logging purposes. The command line interface (CLI)

[1066] may be used to provide commands to execute certain processes which requires changes during the run time. The central logging manager

[1068] may be responsible for keeping the logs of every service. These logs are generated by the MANO platform

[0100] , These logs may be used for debugging purposes. The event routing manager

[1070] may be responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.

[0055] The platform core services module

[0108] comprises NFV infrastructure monitoring manager

[1082] , an assure manager

[1084] , a performance manager

[1086] , a policy execution engine

[1088] , a capacity monitoring manager

[1090] , a release management (mgmt.) repository

[1092] , a configuration manager & golden configuration template (GCT)

[1094] , an NFV platform decision analytics

[1096] , a platform NoSQL DB

[1098] , a platform schedulers and cron jobs

[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] may monitor the infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager

[1084] may be responsible for supervising the alarms the vendor may be generating. The performance manager

[1086] may be responsible for managing the performance counters. The policy execution engine (PEE)

[1088] may be responsible for managing all the policies. The capacity monitoring manager (CMM)

[1090] may be responsible for sending the request to the PEE

[1088] , The release management repository (RMR)

[1092] may be responsible for managing the releases and the images of all ofthe vendor’s network nodes. The configuration 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 (PEE)

[1088] , the configuration manager & (GCT)

[1094] and the (NPDA)

[1096] work together. The platform NoSQL DB

[1098] may be a platform database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. It may be noted that the platform NoSQL DB

[1098] may be just a narrower implementation of the present disclosure, and any other kind of structure for the database may be implemented for the platform database such as relational or non-relational database. The platform schedulers and cron jobs

[1100] may schedule 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 backups on demand in case of server failure. The microservice auditor

[1104] audits the microservices. For e.g., in a hypothetical case, instances not being instantiated by the MANO architecture

[0100] may be using the network resources. In such case, the microservice auditor

[1104] audits and informs the same so that resources can be released for services running in the MANO architecture

[0100] , The audit assures that the services only run on the MANO platform

[0100] , The platform operations, administration and maintenance manager

[1106] may be used for newer instances that are spawning.

[0056] The platform resource adaptors and utilities module

[0112] further comprises a platform external API adaptor and gateway

[1122] , a generic decoder and indexer (XML, CSV, JSON)

[1124] , a service adaptor

[1126] , an API adaptor

[1128] , and aNFV gateway

[1130] , The platform external API adaptor and gateway

[1122] may be responsible for handling the external services (to the MANO platform

[0100] ) that requires the network resources. The generic decoder and indexer (XML, CSV, JSON)

[1124] may get directly the data of the vendor system in the XML, CSV, JSON format. The service adaptor

[1126] may be the interface provided between the telecom cloud and the MANO architecture

[0100] for communication. The Service Adaptor (SA) is a microservices-based system designed to deploy and manage Container Network Functions (CNFs) and their components (CNFCs) across nodes. It offers REST endpoints for key operations, including uploading container images to a registry, terminating CNFC instances, and creating volumes and networks. CNFs, which are network functions packaged as containers, may consist of multiple CNFCs. The Service Adaptor facilitates the deployment, configuration, and management of these components by interacting with API, ensuring proper setup and scalability within a containerized environment. This approach provides a modular and flexible framework for handling network functions in a virtualized network setup.

[0057] The API adaptor

[1128] may be used to connect with the virtual machines (VMs). The NFV gateway

[1130] may be responsible for providing the path to each services going to / incoming from the MANO architecture

[0100] ,

[0058] FIG. 2 illustrates an exemplary block diagram of a computing device

[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 managing event routing utilising the system. In another implementation, the computing device

[0200] itself implements the method for managing event routing using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0059] 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 memory

[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] ,

[0060] 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 via the 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, forcommunicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] , This 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.

[0061] 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 more sequences 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.

[0062] 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.

[0063] 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.

[0064] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for managing event routing, is shown, in accordance with the exemplary implementations of the present disclosure. In one example, the system

[0300] may be implemented as or within an Event Routing Manager (ERM). Such Event Routing Manager (ERM) may be considered to be similar to the ERM

[1070] as may be understood in conjunction with the FIG. 1.

[0065] In another example, as depicted in FIG. 3, the system

[0300] may include the ERM [300A], The ERM [300A] may include at least one transceiver unit

[0302] , at least one authentication unit

[0304] , and at least one notifying unit

[0306] , and at least one processing unit

[0308] ,

[0066] The system

[0300] may also include additional components in communication with the ERM [300 A], which have not been depicted in FIG. 3, and would be understood to a person skilled in the art. The explanation for the same has not been provided here again for the sake of brevity.

[0067] Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in FIG. 3, all units shown within the system

[0300] should also be assumed to be connected to each other. 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 / user equipment to implement the features of the present disclosure. 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.

[0068] The system

[0300] may be configured for managing event routing, with the help of the interconnection between the components / units of the system

[0300] , The management is made possible through the interconnection and communication between various components of the system

[0300] ,

[0069] The system

[0300] may be in communication with other network entities / components, as depicted in FIG. 4. Referring to FIG. 4, an exemplary network environment

[0400] for implementing the system

[0300] for managing event routing, in accordance with exemplary implementations of the present disclosure, is shown.

[0070] The manner in which the Event Routing Manager [300 A] interacts with different network entities / components of the network environment

[0400] for managing event routing has been depicted in FIG. 5.

[0071] FIG. 5 illustrates an exemplary signalling diagram for managing event routing in accordance with exemplary implementations of the present disclosure.

[0072] It may be noted that the FIG. 3, FIG. 4, and FIG. 5 are explained in conjunction in the foregoing description for explanation / description of the present disclosure.

[0073] In one example, for managing event routing, initially, the Capacity Management Monitoring Platform (CMP)

[0402] is a microservice that may act as subscriber.

[0074] For example, during operation, the transceiver unit

[0302] , of the Event Routing Manager [300A], may receive a resource breach event creation request from a first node

[0502] , The resource breach event creation request may include a resource usage data associated with a Network Function (NF). This has been depicted by Step

[0506] in FIG. 4.

[0075] In an implementation of the present disclosure, the first node

[0502] may be a node which may be responsible for monitoring the plurality of Network Functions (NFs) in the network and their respective resource usage. In another example, the first node

[0502] may be a Platform Scheduler.

[0076] The NF may include, but are not limited to, a Virtual Network Function (VNF) or a Container Network Function (CNF), each of which may consist of multiple components, such as VNF Components (VNFC) or CNF Components (CNFC). The resource usage data captured within the request may include metrics such as CPU utilization, memory consumption, bandwidth usage, or other resource parameters that indicate the operational load of the NF.

[0077] In another example, the resource breach event creation request may originate from the Platform Scheduler. The Platform Scheduler is a microservice that may monitor the resource usage and accordingly generates the resource breach event creation request and transmits it to the ERM [300A],

[0078] Once the resource breach event creation request is received at the ERM [300A], the authentication unit

[0304] may authenticate the received resource breach event creation request. This has been depicted by Step

[0508] in FIG. 5.

[0079] The authentication unit

[0304] is responsible for verifying the validity of the resource breach event creation request. The authentication confirms that the request originates from a valid and authorized source, such as the first node (e.g., a Platform Scheduler), and has not been altered with or sent by an unauthorized entity. The authentication process may include verifying credentials, tokens, or any security mechanisms fixed within the request.

[0080] Upon successful authentication, the transceiver unit

[0302] may transmit the resource breach event creation request to the Capacity Monitoring Management Platform (CMP)

[0402] for further processing. This has been depicted by Step

[0510] in FIG. 5.

[0081] The CMP

[0402] is responsible for monitoring and managing network resources. In one example, the CMP

[0402] , on receiving the resource breach event creation request, may store the same in the database

[0404] ,

[0082] In an example, the Event Routing Manager (ERM) [300 A] and the Capacity Monitoring Management Platform (CMP)

[0402] may be communicatively coupled over a CP EM interface.

[0083] The CP EM interface serves as the communication link between the ERM [300 A] and the CMP

[0402] , This interface allows the resource breach event creation request, as well as the corresponding responses, to be exchanged between the ERM [300 A] and the CMP

[0402] in an efficient manner.

[0084] Continuing further, upon receiving the resource breach event creation request, the CMP

[0402] generates a response. This has been depicted by Step

[0512] in FIG. 5.

[0085] In one example, pursuant to transmission of the resource breach event creation request to the CMP

[0402] , the transceiver unit

[0302] may receive a failure response from the CMP

[0402] , The failure response may correspond to an unavailable status of the CMP

[0402] , This failure response indicates that the CMP is in an unavailable status, meaning that the CMP is either not functioning properly, temporarily down, or unable to process the request due to technical issues.

[0086] Based on the detecting by the processing unit

[0308] at the ERM [300A] the failure response, the ERM [300 A] may transmit the resource breach event creation request to another instance of said CMP [not shown]. For example, upon receiving this failure response, the processing unit

[0308] initiates a recovery action. Specifically, it will attempt to transmit the resource breach event creation request via transceiver unit

[0302] to another available instance of the CMP which may act as a secondary CMP.

[0087] The ERM [300A] may keep transmitting the resource breach event creation request to one or another instances of said CMP [not shown] until an available CMP receives the request and starts processing it, which is determined by the processing unit

[0308] at ERM [300A] by a success response from the CMP.

[0088] In another example, for processing the resource breach event creation request, the CMP

[0402] may use the resource usage data provided in the request to assess whether a resource breach has occurred, and accordingly generate a response. This response includes the resource breach event, which is an indication that a breach in resource usage has been identified for the associated Network Function (NF). This has been depicted by Step

[0512] in FIG. 5.

[0089] The response from the CMP is generated through a process that begins when the CMP receives the resource breach event creation request from the Event Routing Manager (ERM) [300A], For example, the CMP

[0402] , on receiving the resource breach event creation request from the ERM [300A], may extract the resource usage data associated with the NF. This resource usage data includes metrics such as CPU usage, memory consumption, bandwidth usage, or other relevant parameters that help monitor the performance of the NF.

[0090] The extracted data is then analysed by the CMP, by comparing the same with a predefined threshold to determine whether the resource usage exceeds the predefined thresholds set for the NF. This comparison allows the CMP to determine whether the resource usage exceeds the acceptable limits.

[0091] The predefined threshold is the maximum allowable level of resource usage for a Network Function (NF) before a resource breach event is triggered.

[0092] For example, if the CPU usage threshold for a particular NF is set at 80%, and the actual usage exceeds this limit, it would indicate a potential resource breach. These thresholds are determined based on performance requirements, capacity planning.

[0093] If the resource usage is found to be greater than the predefined threshold, the CMP concludes that a resource breach event is associated with the NF. This determination is serious, as it signals potential performance issues or the risk of service degradation. Following this determination, the CMP generates a response, as depicted by Step

[0512] in FIG. 5, that summarizes the findings regarding the resource breach event. This response may include relevant details about the breach, such as the type of resource that was breached, the extent of the overutilization, and any recommendations for corrective actions.

[0094] In another example, the CMP

[0402] , after generating the response, may store the same in the Database

[0404] ,

[0095] Continuing further, once the response has been generated by the CMP, the CMP may now act as a producer. The CMP transmits the response to the ERM [300A], This has been depicted by Step

[0514] in FIG. 5.

[0096] In an example, the resource breach event creation request and the response between the ERM [300A] and CMP

[0402] are communicated via a REST application programming interface (API) over hypertext transfer protocol (HTTP).

[0097] Using a REST API allows for effective way to facilitate communication between the ERM and CMP. The RESTful APIs are designed to use stateless communication, which means each request from the client (in this case, the ERM) contains all the information necessary for the server (the CMP) to fulfill the request.

[0098] In another example, the resource breach event creation request and the response exchanged between the ERM [300A] and CMP

[0402] is in JSON format.

[0099] The JSON format is commonly used in web APIs because it capably represents structured data. In this scenario, both the request sent to the CMP and the response received from the CMP are summarized in JSON format, allowing clear and structured communication of the resource usage data and the resulting breach event information.

[0100] Once the ERM [300 A] receives the response from the CMP, which includes the resource breach event, the notifying unit

[0306] may notify a second node

[0504] about the resource breach event. This has been depicted by Step

[0516] in FIG. 5.

[0101] The notifying unit

[0306] within the Event Routing Manager (ERM) [300A] takes action by notifying a second node

[0504] about the occurrence of this resource breach event. This notification is important for informing other components of the network about the resource status, enabling them to take necessary actions, such as scaling resources, adjusting workloads, or executing predefined mitigation strategies to address the breach.

[0102] In an example, the second node

[0504] is a Network Function Virtualization Platform Decision Analytics (NPDA) unit.

[0103] The second node

[0504] that receives the notification about the resource breach event is a Network Function Virtualization Platform Decision Analytics (NPDA) unit. The NPDA unit is a microservice designed to analyse data and make decisions regarding resource allocation and management within a virtualized network environment.

[0104] Referring to FIG. 6, an exemplary method flow diagram

[0600] for managing event routing, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0600] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 6, the method

[0600] starts at Step

[0602] .

[0105] In one example, for managing event routing, initially, the Capacity Monitoring Management Platform (CMP)

[0402] is a microservice that may act as subscriber.

[0106] At Step

[0604] , the method

[0600] comprises receiving, by a transceiver unit

[0302] at an Event Routing Manager (ERM) [300A], a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF).

[0107] For example, during operation, the transceiver unit

[0302] , of the Event Routing Manager [300A], may receive a resource breach event creation request from a first node

[0502] , The resourcebreach event creation request may include a resource usage data associated with a Network Function (NF).

[0108] In an implementation of the present disclosure, the first node

[0502] may be a node which may be responsible for monitoring the plurality of Network Functions (NFs) in the network and their respective resource usage. In another example, the first node

[0502] may be a Platform Scheduler.

[0109] The NF may include, but are not limited to, a Virtual Network Function (VNF) or a Container Network Function (CNF), each of which may consist of multiple components, such as VNF Components (VNFC) or CNF Components (CNFC). The resource usage data captured within the request may include metrics such as CPU utilization, memory consumption, bandwidth usage, or other resource parameters that indicate the operational load of the NF.

[0110] In another example, the resource breach event creation request may originate from the Platform Scheduler. The Platform Scheduler is a microservice that may monitor the resource usage and accordingly generates the resource breach event creation request and transmits it to the ERM [300A],[OHl] Once the resource breach event creation request is received at the ERM [300A], the authentication unit

[0304] may authenticate the received resource breach event creation request.

[0112] The authentication unit

[0304] is responsible for verifying the validity of the resource breach event creation request. The authentication confirms that the request originates from a valid and authorized source, such as the first node (e.g., a Platform Scheduler), and has not been altered with or sent by an unauthorized entity. The authentication process may include verifying credentials, tokens, or any security mechanisms fixed within the request.

[0113] At Step

[0606] , the method

[0600] comprises transmitting, by the transceiver unit at the ERM, the resource breach event creation request creation request to a Capacity Monitoring Management Platform (CMP).

[0114] Upon successful authentication, the transceiver unit

[0302] may transmit the resource breach event creation request to the Capacity Monitoring Management Platform (CMP)

[0402] for further processing.

[0115] The CMP

[0402] is responsible for monitoring and managing network resources.

[0116] In an example, the Event Routing Manager (ERM) [300 A] and the Capacity Monitoring Management Platform (CMP)

[0402] may be communicatively coupled over a CP EM interface.

[0117] The CP EM interface serves as the communication link between the ERM [300 A] and the CMP

[0402] , This interface allows the resource breach event creation request, as well as the corresponding responses, to be exchanged between the ERM [300 A] and the CMP

[0402] in an efficient manner.

[0118] At Step

[0608] , the method

[0600] comprises receiving, by the transceiver unit, a response from CMP based on the transmitted resource breach event creation request. The response may include the resource breach event. The response is generated by the CMP. The CMP, on receiving the resource breach event creation request from the ERM, extracts the resource usage data associated with the NF. Thereafter, based on a comparison of the resource usage data with a predefined threshold, the CMP determines a resource breach event associated with the NF, and generates a response based on the determined resource breach event.

[0119] Continuing further, upon receiving the resource breach event creation request, the CMP

[0402] generates a response.

[0120] In one example, pursuant to transmission of the resource breach event creation request to the CMP

[0402] , the transceiver unit

[0302] may receive a failure response from the CMP

[0402] , The failure response may correspond to an unavailable status of the CMP

[0402] , This failure response indicates that the CMP is in an unavailable status, meaning that the CMP is either not functioning properly, temporarily down, or unable to process the request due to technical issues.

[0121] Based on the detecting by the processing unit

[0308] at the ERM [300A] the failure response, the ERM [300 A] may transmit the resource breach event creation request to another instance of said CMP [not shown]. For example, upon receiving this failure response, the processing unit

[0308] initiates a recovery action. Specifically, it will attempt to transmit the resource breach event creation request via transceiver unit

[0302] to another available instance of the CMP which may act as a secondary CMP.

[0122] The ERM [300A] may keep transmitting the resource breach event creation request to one or another instances of said CMP [not shown] until an available CMP receives the request and starts processing it, which is determined by the processing unit

[0308] at ERM [300A] by a success response from the CMP.

[0123] In another example, for processing the resource breach event creation request, the CMP

[0402] may use the resource usage data provided in the request to assess whether a resource breach has occurred, and accordingly generate a response. This response includes the resource breach event, which is an indication that a breach in resource usage has been identified for the associated Network Function (NF).

[0124] The response from the CMP is generated through a process that begins when the CMP receives the resource breach event creation request from the Event Routing Manager (ERM) [300A], For example, the CMP

[0402] , on receiving the resource breach event creation request from the ERM [300A], may extract the resource usage data associated with the NF. This resource usage data includes metrics such as CPU usage, memory consumption, bandwidth usage, or other relevant parameters that help monitor the performance of the NF.

[0125] The extracted data is then analysed by the CMP, by comparing the same with a predefined threshold to determine whether the resource usage exceeds the predefined thresholds set for the NF. This comparison allows the CMP to determine whether the resource usage exceeds the acceptable limits.

[0126] The predefined threshold is the maximum allowable level of resource usage for a Network Function (NF) before a resource breach event is triggered.

[0127] For example, if the CPU usage threshold for a particular NF is set at 80%, and the actual usage exceeds this limit, it would indicate a potential resource breach. These thresholds are determined based on performance requirements, capacity planning.

[0128] If the resource usage is found to be greater than the predefined threshold, the CMP concludes that a resource breach event is associated with the NF. This determination is serious, as it signals potential performance issues or the risk of service degradation. Following this determination, the CMP generates a response, that summarizes the findings regarding the resource breach event. This response may include relevant details about the breach, such as the type ofresource that was breached, the extent of the overutilization, and any recommendations for corrective actions.

[0129] Once the response has been generated by the CMP, the CMP may now act as a producer. The CMP transmits the response to the ERM [300A],

[0130] In an example, the resource breach event creation request and the response between the ERM [300A] and CMP

[0402] are communicated via a REST application programming interface (API) over hypertext transfer protocol (HTTP).

[0131] In another example, the resource breach event creation request and the response exchanged between the ERM [300A] and CMP

[0402] is in JSON format.

[0132] At Step

[0610] , the method

[0600] comprises notifying, by the notifying unit at the ERM, a second node

[0504] about the resource breach event.

[0133] Once the ERM [300 A] receives the response from the CMP, which includes the resource breach event, the notifying unit

[0306] may notify a second node

[0504] about the resource breach event.

[0134] The notifying unit

[0306] within the Event Routing Manager (ERM) [300A] takes action by notifying a second node

[0504] about the occurrence of this resource breach event. This notification is important for informing other components of the network about the resource status, enabling them to take necessary actions, such as scaling resources, adjusting workloads, or executing predefined mitigation strategies to address the breach.

[0135] In an example, the second node

[0504] is a Network Function Virtualization Platform Decision Analytics (NPDA) unit.

[0136] The second node

[0504] that receives the notification about the resource breach event is a Network Function Virtualization Platform Decision Analytics (NPDA) unit. The NPDA unit is a microservice designed to analyse data and make decisions regarding resource allocation and management within a virtualized network environment.

[0137] Thereafter, the method

[0600] terminates at Step

[0612] .

[0138] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing event routing. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit

[0302] , at an Event Routing Manager (ERM), to receive a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF). Further, the instructions include executable code which, when executed, causes the transceiver unit, at the ERM, to transmit the resource breach event creation request to a Capacity Monitoring Management Platform (CMP). Further, the instructions include executable code which, when executed, causes the transceiver unit to receive a response from the CMP, based on the transmitted resource breach event creation request, wherein the response comprises the resource breach event. The response is generated by the CMP. On receiving the resource breach event creation request from the ERM, the CMP extracts the resource usage data associated with the NF. Based on a comparison of the resource usage data with a pre-defined threshold, the CMP determines a resource breach event associated with the NF. The CMP generates the response based on the determined resource breach event. Further, the instructions include executable code which, when executed, causes a notifying unit

[0306] , at the ERM, to notify a second node about the resource breach event.

[0139] As is evident from the above, the present disclosure provides a technically advanced solution for managing event routing of microservices. The present solution employs a specifically designed interface, referred to as CP EM, for administrating the routing of requests and responses between the various microservices involved in the system. This interface is integral in establishing a streamlined communication pathway among different microservices, allowing them to interact and exchange information efficiently. The CP EM interface operates based on a subscription and notification framework. This means that it adheres to a model where each microservice can subscribe to receive notifications about certain events or updates within the system. By subscribing to such interface, the microservices are ensuring that they are always informed about occurrences that are pertinent to their function, promoting real-time synchronization and coordination among them. This framework is fundamental in ensuring that all microservices are not only constantly updated on the system’s state but also able to react promptly to any changes, thereby maintaining the accuracy and reliability of the system’s overall operation.

[0140] The present subject matter also enables systematic and precise routing of events within the system, ensuring each event is directed appropriately through predefined pathways, enhancing theefficiency and accuracy of the event management process. The ERM manages and directs the flow of events through the CP EM interface. It acts as a mediator, facilitating the communication and transfer of events between the interface and the rest of the system. This involves taking in events, processing them, and routing them through the CP EM interface to or from the CP, maintaining smooth and structured flow within the system. Crucially, only the permitted events, predefined at the ERM, are allowed to be routed, ensuring that every event that passes through adheres to the established rules and protocols of the system.

[0141] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations 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.

[0142] 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.

Claims

We Claim:

1. A method for managing event routing, the method comprising: receiving, by a transceiver unit [302] at an Event Routing Manager (ERM) [300A], a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF);- transmitting, by the transceiver unit [302] at the ERM [300A], the resource breach event creation request to a Capacity Monitoring Management Platform (CMP);- based on the transmitted resource breach event creation request, receiving, by the transceiver unit [302], a response from the CMP, wherein the response comprises the resource breach event, and wherein the response is generated by the CMP based on: o on receiving the resource breach event creation request from the ERM [300A], extracting the resource usage data associated with the NF; o based on a comparison of the resource usage data with a pre-defined threshold, determining a resource breach event associated with the NF; and o generating a response based on the determined resource breach event; and notifying, by a notifying unit [306] at the ERM [300A], a second node about the resource breach event.

2. The method as claimed in claim 1, wherein the first node is a Platform Scheduler.

3. The method as claimed in claim 1, wherein the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

4. The method as claimed in claim 1, further comprising: authenticating, by an authentication unit [304], the received resource breach event creation request; and- based on a successful authentication, transmitting, by the transceiver unit [302], the resource breach event creation request to the CMP.

5. The method as claimed in claim 1, wherein the Event Routing Manager (ERM) [300 A] and the Capacity Monitoring Management Platform (CMP) are communicatively coupled over a CP EM interface.

6. The method as claimed in claim 1, wherein the resource breach event creation request and the response between the ERM [300 A] and CMP are communicated via a REST application programming interface (API) over hypertext transfer protocol (HTTP).

7. The method as claimed in claim 1, wherein the resource breach event creation request and the response exchanged between the ERM [300A]and CMP is in JSON format.

8. The method as claimed in claim 1, further comprising: pursuant to transmission of the resource breach event creation request to the CMP, receiving, by the transceiver unit [302], a failure response from the CMP, wherein the failure response corresponds to an unavailable status of the CMP; and based on the received failure response, transmitting, by the transceiver unit [302], the resource breach event creation request to another instance of said CMP.

9. The method as claimed in claim 1, wherein the second node is a Network Function Virtualization Platform Decision Analytics (NPDA) unit.

10. A system for managing event routing, the system comprising an Event Routing Manager (ERM) [300A], the ERM [300 A] comprising: a processing unit [308]; and a transceiver unit [302] connected at least to the processing unit [308], wherein the transceiver unit [302] is configured to: o receive a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF); o transmit the resource breach event creation request to a Capacity Monitoring Management Platform (CMP); o based on the transmitted resource breach event creation request, receive a response from the CMP, wherein the response comprises the resource breach event, and wherein the response is generated by the CMP based on:■ on receiving the resource breach event creation request from the ERM [300A], extracting the resource usage data associated with the NF;■ based on a comparison of the resource usage data with a pre-defined threshold, determining a resource breach event associated with the NF; and■ generating a response based on the determined resource breach event; and a notifying unit [342] connected at least to the transceiver unit, wherein the notifying unit is configured to notify a second node about the resource breach event.

11. The system as claimed in claim 10, wherein the first node is a Platform Scheduler.

12. The system as claimed in claim 10, wherein the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

13. The system as claimed in claim 10, further comprising: an authentication unit [304] configured to authenticate the received resource breach event creation request; and■ the transceiver unit [302] further configured to transmit the resource breach event creation request to the CMP, based on a successful authentication.

14. The system as claimed in claim 10, wherein the Event Routing Manager (ERM) [300A] and the Capacity Monitoring Management Platform (CMP) are communicatively coupled over a CP EM interface.

15. The system as claimed in claim 10, wherein the resource breach event creation request and the response between the ERM [300A]and CMP are communicated via a REST application programming interface (API) over hypertext transfer protocol (HTTP).

16. The system as claimed in claim 10, wherein the resource breach event creation request and the response exchanged between the ERM [300A] and CMP is in JSON format.

17. The system as claimed in claim 10, wherein the transceiver unit [302] is further configured to: pursuant to transmission of the resource breach event creation request to the CMP, receive a failure response from the CMP, wherein the failure response corresponds to an unavailable status of the CMP; and based on the received failure response, transmit the resource breach event creation request to another instance of said CMP.

18. The system as claimed in claim 10, wherein the second node is a Network Function Virtualization Platform Decision Analytics (NPDA) unit.

19. A non-transitory computer-readable storage medium storing instructions for managing event routing, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [302], at an Event Routing Manager (ERM) [300A], to receive a resource breach event creation request from a first node, wherein the resource breach event creation request comprises a resource usage data associated with a Network Function (NF);- the transceiver unit [302], at the ERM [300A], to transmit the resource breach event creation request to a Capacity Monitoring Management Platform (CMP);■■ the transceiver unit [302] to receive a response from the CMP, based on the transmitted resource breach event creation request, wherein the response comprises the resource breach event, and wherein the response is generated by the CMP based on: o on receiving the resource breach event creation request from the ERM [300A], extracting the resource usage data associated with the NF; o based on a comparison of the resource usage data with a pre-defined threshold, determining a resource breach event associated with the NF; and o generating a response based on the determined resource breach event; and a notifying unit [306], at the ERM [300A], to notify a second node about the resource breach event.

Images