Method and system for routing a request through an interface

Abstract

The present disclosure relates to a method and a system for routing a request via an interface The method comprises registering, by a registration unit [302], at an event routing manager (ERM), an event from a service auditor. The method comprises receiving, by a transceiver unit [304], a request associated with the event from the service. The method comprises determining, by a determination unit [306] an event data associated with the request. The method comprises transmitting, by the transceiver unit [304], the request to a service auditor via the interface based on the event data. The method comprises sending, by the transceiver unit [304], from the ERM, the event to the service.

Description

METHOD AND SYSTEM FOR ROUTING A REQUEST THROUGH AN INTERFACEFIELD OF THE DISCLOSURE

[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to routing a request via an interface. More particularly, embodiments of the present disclosure relate to routing an event via an interface.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] A network function virtualization and software defined network (NFV SDN) platform has been built to act as a single platform to manage all the VNFs and CNFs being deployed in a telecom network. As the platform is completely based on microservice architecture, it is highly scalable and will be able to handle hundreds of NFV. The platform is completely event driven and is based on standard REST APIs. For computing resources, the AU needs to send requests to multiple microservices or instances of same microservices. Further, AU also receives multiple requests from multiple microservice. This creates following issues exists in the existing network management systems:- Request routing troubles- Operational issues for new request subscriber and publisher- Service was getting impacted- Same request cannot be reused.

[0004] Auditor service (AU) audits the resources in terms of physical memory, RAM and CPU at Inventory Manager. It brings inventory in close sync with real time available / used resources and minimizes the mismatch between Inventory Manager (IM) and real time hardware. The data accuracy depends primarily on Swarm Adaptor (SA) and Inventory Manager (IM).

[0005] Thus, there exists an imperative need in the art to optimize system performance by enhancing operation capability and simplifying routing request based on robust communication between Event Routing Manager (ERM) and Microservices Auditor (MAUD).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 routing a request via an interface. The method comprises registering, by a registration unit, at an event routing manager (ERM), an event from a service auditor. Further, the method comprises receiving, by a transceiver unit, at the ERM, a request associated with the event from the service. Furthermore, the method comprises determining, by a determination unit, at the ERM, an event data associated with the request. Hereinafter, the method comprises transmitting, by the transceiver unit, from the ERM the request to a service auditor via the interface based on the event data. Further, the method comprises sending, by the transceiver unit, from the ERM, the event to the service.

[0008] In an exemplary aspect of the present disclosure, the event data comprises an event type data, a publisher data and a subscriber data.

[0009] In an exemplary aspect of the present disclosure, the event type data is one of an event type and an event acknowledgement type.

[0010] In an exemplary aspect of the present disclosure, the event type data of the event is the event type.

[0011] In an exemplary aspect of the present disclosure, the publisher data associated with the event is the service auditor (SA) and the subscriber data associated with the event is the service.

[0012] In an exemplary aspect of the present disclosure, sending, by the transceiver unit, from the ERM, the event to the service comprises receiving, by the transceiver unit, at the service auditor, the event for the service.

[0013] In an exemplary aspect of the present disclosure, the interface routes the request to and from the service auditor.

[0014] Another aspect of the present disclosure may relate to a method for routing a request via an interface. The method comprises registering, by a registration unit, at an event routing manager (ERM), an event from a service. Further, the method comprises receiving, by a transceiver unit, at the ERM, a request associated with the event from the service auditor via the interface. Furthermore, the method comprises determining, by a determination unit, at the ERM, an event data associated with the request. Hereinafter, the method comprises transmitting, by the transceiver unit, from the ERM the request to a service based on the event data. Further, the method comprises sending, by the transceiver unit, from the ERM the event to the service auditor via the interface.

[0015] In an exemplary aspect of the present disclosure, the event data comprises an event type data, a publisher data and a subscriber data.

[0016] In an exemplary aspect of the present disclosure, the event type data is one of an event type and an event acknowledgement type.

[0017] In an exemplary aspect of the present disclosure, the event type data of the event is the event type.

[0018] In an exemplary aspect of the present disclosure, the publisher data associated with the event is the service and the subscriber data associated with the data is the service auditor.

[0019] In an exemplary aspect of the present disclosure, sending, by the transceiver unit, from the ERM the event to the service auditor via the interface comprises receiving, by the transceiver unit, at the service, the event for the service auditor.

[0020] In an exemplary aspect of the present disclosure, the interface routes the request to and from the service auditor.

[0021] Yet another aspect of the present disclosure may relate to a system for routing a request via an interface. The system comprises a registration unit. The registration unit is configured to register, at an event routing manager (ERM), an event from a service auditor. The system furthercomprises a transceiver unit. The transceiver unit is configured to receive, at the ERM, a request associated with the event from the service. The system further comprises a determination unit. The determination unit is configured to determine, at the ERM, an event data associated with the request. The transceiver unit is configured to transmit, from the ERM the request to a service auditor via the interface based on the event data. Further, the transceiver unit is configured to send, from the ERM, the event to the service.

[0022] Yet another aspect of the present disclosure may relate to a system for routing a request via an interface. The system comprises a registration unit. The registration unit is configured to register, at an event routing manager (ERM), an event from a service. The system comprises a transceiver unit. The transceiver unit is configured to receive, at the ERM, a request associated with the event from the service auditor via the interface. The system further comprises a determination unit. The determination unit is configured to determine, at the ERM, an event data associated with the request. The transceiver unit is further configured to transmit, from the ERM the request to a service based on the event data. Further, the transceiver unit is configured to send, from the ERM, the event to the service auditor via the interface.

[0023] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for routing a request via an interface, the instructions include executable code which, when executed by one or more units of a system cause a registration unit to register, at an event routing manager (ERM), an event from a service auditor via the interface. The instructions when executed by the system further cause a registration unit to register, at an event routing manager (ERM), an event from a service auditor. The instructions when executed by the system further cause a transceiver unit to receive, at the ERM, a request associated with the event from the service. The instructions when executed by the system further cause a determination unit to determine, at the ERM, an event data associated with the request. The instructions when executed by the system further cause the transceiver unit to transmit, from the ERM, the request to a service auditor via the interface based on the event data. The instructions when executed by the system further cause the transceiver unit to send, from the ERM, the event to the service.

[0024] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium, storing instructions for routing a request via an interface, the instructions include executable code which, when executed by one or more units of a system cause a registration unit to register, at an event routing manager (ERM), an event from a service auditorvia the interface. The instructions when executed by the system further cause a transceiver unit to receive, at the ERM, a request associated with the event from the service. The instructions when executed by the system further cause a determination unit to determine, at the ERM, an event data associated with the request. The instructions when executed by the system further cause the transceiver unit, to transmit, from the ERM, the request to a service based on the event data. The instructions when executed by the system further cause the transceiver unit to send, from the ERM, the event to the service auditor via the interface.OBJECTS OF THE DISCLOSURE

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

[0026] It is an object of the present disclosure to provide a system and a method optimizing system performance by enhancing operation capability and simplifying routing request based on robust communication between Event Routing Manager (ERM) and Microservices Auditor (MAUD) via AU_EM interface.

[0027] It is another object of the present disclosure to provide a solution to enhance request reusability and avoid any Nonservice impact.

[0028] It is yet another object of the present disclosure to simplify operational issue of adding / modifying request subscriber publisher.DESCRIPTION OF THE DRAWINGS

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

[0030] FIG. 1 illustrates an exemplary block diagram representation of management and orchestration (MANO) architecture / platform, in accordance with exemplary implementation of the present disclosure.

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

[0032] FIG. 3 illustrates an exemplary block diagram of a system for routing a request via an interface, in accordance with exemplary implementations of the present disclosure.

[0033] FIG. 4 illustrates an implementation of the system for routing a request via an interface, in accordance with exemplary implementations of the present disclosure.

[0034] FIG. 5 illustrates a method flow diagram for routing a request via an interface, in accordance with exemplary implementations of the present disclosure.

[0035] FIG. 6 illustrates another method flow diagram for routing a request via an interface, in accordance with exemplary implementations of the present disclosure.

[0036] FIG. 7 illustrates an implementation of the method for routing a request via an interface, 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 microprocessorsin 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 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.

[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 pluralityof 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 routing a request via an interface.

[0050] 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] is developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of network node(s) / service(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

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

[0051] 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 platforms foundation services module

[0106] , a platform core services module

[0108] and a platform resource adapters and utilities module

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

[0052] The NFV and SDN design function module

[0104] comprises a VNF lifecycle manager (compute)

[1042] , a VNF catalog

[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 fordeciding on which server of the communication network, the microservice will be instantiated. The VNF lifecycle manager (compute)

[1042] may 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 the process. 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 catalog

[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 used for the CNFs lifecycle management.

[0053] The platforms foundation services module

[0106] 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. These logs are generated by the MANO platform

[0100] , These 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.

[0054] The platforms 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 & 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 (MAUD)

[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 managing the performance counters. The policy execution engine (PEGN)

[1088] is responsible for all the managing thepolicies. The capacity monitoring manager (CMM)

[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. 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 (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

[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 platform

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

[1106] is used for newer instances that are spawning.

[0055] 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 service 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 platform

[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 service 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 services going to / incoming from the MANO architecture

[0100] ,

[0056] 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 routing a request via an interface utilising the system. In another implementation, the computing device

[0200] itself implements the method for routing a requestvia an interface, 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.

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

[0058] 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, for communicating 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.

[0059] 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 areperformed 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.

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

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

[0062] The present disclosure is implemented by a system

[0300] (as shown in FIG. 3) and a system

[0400] (as shown in FIG. 4). In an implementation, the system

[0300] and the system

[0400] may include the computing device

[0200] (as shown in FIG. 2). It is further noted that the computing device

[0200] is able to perform the steps of a method

[0600] (as shown in FIG. 6) and a method

[0700] (as shown in FIG. 7).

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

[0300] for routing a request via an interface is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one registration unit

[0302] , at least one transceiverunit

[0304] and at least one determination unit

[0306] , 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 the figures all units shown within the system 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 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.

[0064] The system

[0300] is configured for routing a request via an interface, with the help of the interconnection between the components / units of the system

[0300] ,

[0065] The interface routes the request to and from a service auditor. The interface is an SA EM interface. The SA EM interface is used to route all the incoming request to service auditor and all the outgoing request from the service auditor. The SA EM interface follows a subscription and notification model based on the events published to the SA EM interface. The SA EM interface works in a high availability mode and if one instance goes down during the routing of the request, then another available instance of the SA EM interface performs the routing of the request. The SA EM interface is configured to manage the requests in parallel to make the interface smooth and more responsive.

[0066] The registration unit

[0302] is configured to register an event from the service auditor at the event routing manager (ERM)

[1070] as depicted in FIG. 1. For registration of the event, the transceiver unit

[0304] is configured to receive, at the ERM

[1070] , the request associated with the event from the service. The ERM

[1070] may register the event based on determining an event data associated with the event. In an implementation of the present disclosure, each service auditor registers the events associated with each of the service, with the ERM

[1070] , For each event, there can be multiple subscribers. Whenever the event of interest of a subscriber is received, the notification is sent by the ERM

[1070] to the subscribers informing of the event.

[0067] The transceiver unit

[0304] is configured to receive, at the ERM

[1070] , a request associated with the event from the service auditor. In one example, if the service wants to send the request to the service auditor, the request may be sent via a hypertext transfer protocol (HTTP) request.

[0068] In the present disclosure, for example, the service auditor is a microservice which is implemented as part of the larger architecture. For instance, the service auditor may be the MAUD

[1104] as depicted in FIG. 1. Further the request message includes parameters required for an application programming interface (API) related to a process / event for which message request is sent. For example, the request message includes parameters like event name, an event type, and the like. In an implementation, the event name is the name of the API. For example:An exemplary implementation for the event name may be GET CNFC INVENTORY AUDIT. This event is for fetching the audit report of actual and allocated resources used by a Container network function (CNF) ranging over various nodes in a region. In one example, the request message may be to identify the RAM and CPU usage of another service instance (MS).

[0069] The determination unit

[0306] is configured to determine the event data associated with the request. The determination may be done at the SA EM interface. The event data includes but may not be limited to an event type data, a publisher data and a subscriber data. In one example, the event type data is one of an event type and an event acknowledgement type. In an example, the event type data of the event is the event type.

[0070] In one example, if the event type data is the event type, then the ERM

[1070] may forward the request to a publisher based on the publisher data. If the event type data is the event acknowledgment type, then the ERM

[1070] may forward the request to a subscriber based on the subscriber data. The publisher data associated with the event is the service auditor and the subscriber data associated with the event is the service. In an implementation of the present disclosure, when the service wants to send the request to the service auditor, the publisher is the service auditor, and the subscriber is the service sending the request.

[0071] Based on the event data, the transceiver unit

[0304] is configured to transmit the request to the service auditor via the interface from the ERM

[1070] , The transceiver unit

[0304] is further configured to send, from the ERM, the event to the service. For sending the event to the service, the transceiver unit

[0304] is configured to receive the event for the service at the service auditor.

[0072] In another exemplary scenario, if the service wants to send a request to a second service from the service auditor, the request may be sent via the hypertext transfer protocol (HTTP).

[0073] The registration unit

[0302] is configured to register, at the ERM

[1070] , an event from the service. In an implementation of the present disclosure, each service registers the events associated with each of the service, with the ERM

[1070] for one or more subscribers that may be interested in the event.

[0074] The transceiver unit

[0304] is configured to receive, at the ERM

[1070] , a request associated with the event from the service auditor via the SA EM interface. In one example, if the service wants to send the request to another service, the request may be sent via a hypertext transfer protocol (HTTP) request.

[0075] The determination unit

[0306] , configured to determine an event data associated with the event at the SA EM interface. In one example, the event type data of the event is the event type. In the present example, the publisher data associated with the event is the service and the subscriber data associated with the data is the service auditor.

[0076] Based on the event data, where the auditor service is the subscriber data, the transceiver unit

[0304] is configured to transmit, from the ERM, the request to a service based on the event data.

[0077] The transceiver unit

[0304] is configured to send, from the ERM, the event to the service auditor via the interface. For sending, the transceiver unit

[0304] is configured to receive, at the service, the event for the service auditor.

[0078] Referring to FIG. 4, an implementation of the system

[0400] for outing a request via an interface, in accordance with exemplary implementations of the present disclosure is shown.

[0079] The system

[0400] comprises one or more microservices

[0402] , the ERM

[1070] , an AU_EM interface

[0404] and the micro service auditor (MAUD)

[1104] ,

[0080] The one or more microservices

[0402] refers to a random microservice that sends the event to the MAUD

[1104] or may send the request to any other microservice from the MAUD

[1104] , The one or more microservices

[0402] sends one or more events to the ERM

[1070] , For each event,there can be multiple subscribers. The events include the list of subscribers. Whenever an event of interest for a subscriber is received, the notification is sent by the ERM

[1070] to the subscriber informing of the event.

[0081] The ERM

[1070] is an event routing manager, which is used to route all the incoming request to the MAUD

[1104] and all the outgoing request from the MAUD

[1104] , This interface follows a subscription and notification model based on the events which are published to it. Each micro service registers its standard platform events with the ERM. For each event, there can be multiple subscribers. Whenever the event of interest is received, the notification are sent by the ERM to the subscribers informing them of the said event.

[0082] The AU EM interface

[0404] routes the request to and from the MAUD

[1104] , The AU EM interface

[0404] follows a subscription and notification model based on the events published to the AU EM interface

[0404] , Each of microservice registers its standard platform events with the ERM

[1070] , For each event, there can be multiple subscribers. Whenever the event of interest is received, the notification is sent by the ERM

[1070] to the subscribers informing the subscribers of the event. The AU EM interface

[0404] works in a high availability mode. If one instance of the AU EM interface

[0404] goes down during the routing of the request, then another available instance of the AU EM interface

[0404] performs the routing of the request. The AU EM interface

[0404] is configured to manage the requests in parallel to make the interface smooth and more responsive.

[0083] The MAUD

[1104] is configured to audit the resources in terms of physical memory, RAM and CPU at Inventory Manager. The MAUD

[1104] brings inventory in synchronization with real time available or used resources. The MAUD

[1104] minimizes the mismatch between Inventory Manager (IM) and real time hardware. The MAUD

[1104] detects whether hosts contains lesser / more containers than the amount present in inventory managed by IM. It accordingly sends API request to IM to update its inventory. The MAUD

[1104] interacts with the Microservices to fetch the real time data using various APIs.

[0084] In one embodiment, when the MAUD

[1104] is the subscriber, the MAUD

[1104] sends request to the ERM

[1070] for two events. The two events include a first event of IM and the second event for Swarm Manager. When the IM and Swarm Manager publishes the requested events at the ERM

[1070] , then the ERM

[1070] forwards the events to the MAUD

[1104] , The MAUD

[1104] extracts event data from both the events, where the event data comprises resourceinformation requested by the MAUD

[1104] , The MAUD

[1104] compares the resource information from both the events to prepare an audit report.

[0085] In another embodiment, where the MAUD

[1104] is the publisher. A user interface (UI) where the UI may be a command line interface (CLI) or any of the one or more microservices

[0402] acting as the subscriber. The UI / CLI or the one or more microservices sends a request for the audit report. The MAUD

[1104] registers the audit report at the ERM

[1070] as an event. Whenever the UI / CLI / one or more microservices sends the request to the ERM

[1070] for the audit report. The ERM

[1070] sends the request to the MAUD

[1104] , and the MAUD

[1104] publishes the event for the audit report to the ERM

[1070] , Further, the ERM

[1070] forwards the audit report to the subscribers.

[0086] Referring to FIG. 5, an exemplary method flow diagram

[0500] for routing a request via an interface, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0500] 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. 5, the method

[0500] starts at step

[0502] ,

[0087] The interface to route the request is configured to route the request to and from the service auditor. The interface is an SA EM interface. The SA EM interface is used to route all the incoming request to service auditor and all the outgoing request from the service auditor. The SA EM interface follows a subscription and notification model based on the events published to the SA EM interface. Each service registers its standard platform events with the ERM

[1070] , For each event, there can be multiple subscribers. Whenever the event of interest of a subscriber is received, the notification is sent by the ERM

[1070] to the subscribers informing of the event.

[0088] The SA EM interface works in a high availability mode and if one instance goes down during the routing of the request, then another available instance of the SA EM interface performs the routing of the request. The SA EM interface is configured to manage the requests in parallel to make the interface smooth and more responsive.

[0089] At step

[0504] , the method comprises registering, by a registration unit

[0302] , at an event routing manager (ERM)

[1070] , an event from a service auditor. In an implementation of the present disclosure, each service registers the events associated with each of the service, with the ERM

[1070] , For each event, there can be multiple subscribers. Whenever the event of interest ofa subscriber is received, the notification is sent by the ERM

[1070] to the subscribers informing of the event.

[0090] At step

[0506] , the method comprises receiving, by a transceiver unit

[0304] , at the ERM, a request associated with the event from the service. In one example, if the service wants to send the request to the service auditor, the request may be sent via a hypertext transfer protocol (HTTP) request.

[0091] In the present disclosure, for example, the service auditor is a microservice which is implemented as part of the larger architecture. For instance, the service auditor may be the MAUD

[1104] as depicted in FIG. 1. Further the request message includes parameters required for an application programming interface (API) related to a process / event for which message request is sent. For example, the request message includes parameters like event name, an event type, and the like. In an implementation, the event name is the name of the API. For example:X-Event-Name=GET_DETAILS_FROM_TARGET_MS

[0092] An exemplary implementation for the event name may be GET CNFC INVENTORY AUDIT. This event is for fetching the audit report of actual and allocated resources used by a CNF ranging over various nodes in a region. In one example, the request message may be to identify the RAM and CPU usage of another service instance (MS).

[0093] Next at step

[0508] , the method comprises determining, by a determination unit

[0306] , at the ERM

[1070] , an event data associated with the request. The determination may be done at the SA EM interface. The event data includes but may not be limited to an event type data, a publisher data and a subscriber data. In one example, the event type data is one of an event type and an event acknowledgement type. In an example, the event type data of the event is the event type.

[0094] In one example, if the event type data is the event type, then the ERM

[1070] may forward the request to a publisher based on the publisher data. If the event type data is the event acknowledgment type, then the ERM

[1070] may forward the request to a subscriber based on the subscriber data. The publisher data associated with the event is the service auditor and the subscriber data associated with the event is the service. In an implementation of the present disclosure, when the service wants to send the request to the service auditor, the publisher is the service auditor, and the subscriber is the service sending the request. The ERM

[1070] may check if the publisher data in the request is the auditor service.

[0095] Next at step

[0510] , the method comprises transmitting, by the transceiver unit

[0304] , from the ERM

[1070] , the request to the service auditor via the interface based on the event data based on the checking of the publisher data. In another example, if the service auditor is not associated with the publisher data and is associated with the subscriber data, the request may not proceed further.

[0096] Further at step

[0512] , the method comprises sending, by the transceiver unit

[0304] , from the ERM

[1070] , the event to the service. For sending the event to the service, the transceiver unit

[0304] is configured to receive the event for the service at the service auditor.

[0097] The method

[0500] terminates at step

[0514] ,

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

[0600] for routing a request via an interface, 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] ,

[0099] At step

[0604] , the method comprises registering, by a registration unit

[0302] , at an event routing manager (ERM), an event from a service. Each service registers the events associated with each of the service, with the ERM

[1070] for one or more subscribers that may be interested in the event.

[0100] At step

[0606] , the method comprises receiving, by a transceiver unit

[0304] , at the ERM, a request associated with the event from the service auditor via the interface. In one example, if the service wants to send the request to another service, the request may be sent via a hypertext transfer protocol (HTTP) request.

[0101] Next at step

[0608] , the method comprises determining, by a determination unit

[0306] , at the ERM

[1070] , an event data associated with the request. In one example, the event type data of the event is the event type. In the present example, the publisher data associated with the event is the service and the subscriber data associated with the data is the service auditor (SA).

[0102] Next at step

[0610] , the method comprises transmitting, by the transceiver unit

[0304] , from the ERM

[1070] the request to a service based on the event data. The event is transmitted to the service auditor, if the service auditor is associated with the subscriber data. In another example, if the service auditor is not associated with the subscriber data and is associated with the publisher data, the request may not proceed further.

[0103] Next at step

[0610] , the method comprises sending, by the transceiver unit

[0304] , from the ERM

[1070] the event to the service auditor via the interface. For sending the event to the service, the transceiver unit

[0304] is configured to receive the event for the service at the service auditor.

[0104] The method

[0600] terminates at step

[0614] ,

[0105] Referring to FIG. 7, an implementation of the method flow

[0700] for routing a request via an interface. The method starts at step

[0702] ,

[0106] At step

[0704] , the method

[0500] may check if any of the one or more microservices

[0502] wants to send the request associated with the event to the MAUD

[1104] , Based on the checking, if any of the one or more microservice

[0402] wants to send the request, the method may proceed to step

[0706] ,

[0107] At step

[0706] , the event contained in the request will be registered with the ERM

[1070] , Further, the event registration includes publisher data and the subscriber data. The ERM

[1070] stores the microservice

[0402] sending the request in the subscriber data, and the MAUD

[1104] , may be stored as the publisher data. The method proceeds to step

[0710] ,

[0108] At step

[0710] , the AU_EM interface

[0404] will check if the publisher in the event is the MAUD

[1104] or not. If the publisher is the MAUD

[1104] , the method proceeds to step

[0812] ,

[0109] At step

[0712] , the request will be sent to the MAUD

[1104] , In an example, if the publisher is not the MAUD

[1104] , the request will not be sent and a fail response may be sent to the microservice

[0402] sending the request.

[0110] Further the method terminates at step

[0714] ,

[0111] In continuation to the step

[0704] , where the method

[0500] may check if any of the one or more microservices

[0502] wants to send the request associated with the event to the MAUD

[1104] , If on checking, if any of the one or more microservice

[0402] does not want to send the request to the MAUD

[1104] , the method proceeds to step

[0708] ,

[0112] At step

[0708] , it will be checked if the microservice

[0402] wants to send the request from the MAUD

[1104] to any other microservice. If the microservice

[0402] does not want to send the request from the MAUD

[1104] the method will go back to start from step

[0702] , If the microservice

[0402] wants to send the request from the MAUD

[1104] to any other microservice, the method proceeds to step

[0716] ,

[0113] At step

[0716] , the method includes registering the event at the ERM

[1070] , The event includes the subscriber data and the publisher data. The subscriber data includes the MAUD

[1104] and the publisher data includes any other microservice associated with the request.

[0114] Further at step

[0718] , the method includes the AU EM interface

[0404] to check if the subscriber data is the MAUD

[1104] or not. If the subscriber data is the MAUD

[1104] , the method proceeds to step

[0720] ,

[0115] At step

[0720] , the event associated with the request is received at the other microservice from the MAUD

[1104] , The other microservice may send the acknowledgment based on the receiving of the event. If the subscriber data is not the MAUD

[1104] , the request will not be sent to the microservice and a fail response may be sent back to the microservice sending the request.

[0116] The method terminates at step

[0722] ,

[0117] The present disclosure further discloses a non-transitory computer readable storage medium, storing instructions for routing a request via an interface, the instructions include executable code which, when executed by one or more units of a system, cause a registration unit

[0302] to register, at an event routing manager (ERM)

[1070] , an event from a service. The instructions when executed by the system further cause a transceiver unit

[0304] to receive, at the ERM

[1070] , a request associated with the event from the service auditor. The instructions when executed by the system further cause a determination unit

[0306] to determine, at the ERM, an event data associated with the request. The instructions when executed by the system further cause the transceiver unit

[0304] to transmit, from the ERM

[1070] , the request to a service auditor via theinterface based on the event data. The instructions when executed by the system further cause the transceiver unit

[0304] to send, from the ERM

[1070] , the event to the service.

[0118] The present disclosure further discloses a non-transitory computer readable storage medium, storing instructions for routing a request via an interface, the instructions include executable code which, when executed by one or more units of a system, cause a registration unit

[0302] to register, at an event routing manager (ERM)

[1070] , an event from a service. The instructions when executed by the system further cause a transceiver unit

[0304] to receive, at the ERM

[1070] , a request associated with the event from the service. The instructions when executed by the system further cause a determination unit

[0306] to determine, at the ERM

[1070] , an event data associated with the request. The instructions when executed by the system further cause the transceiver unit

[0304] , to transmit, from the ERM

[1070] , the request to a service based on the event data. The instructions when executed by the system further cause the transceiver unit

[0304] to send, from the ERM

[1070] , the event to the service auditor via the interface.

[0119] As is evident from the above, the present disclosure provides a technically advanced solution for routing a request and an event via an interface. The present solution provides a system and a method optimizing system performance by enhancing operation capability and simplifying routing request based on robust communication between Event Routing Manager (ERM) and Microservices Auditor (MAUD) via AU EM interface. The present disclosure further provides a solution to enhance request reusability and avoid any Nonservice impact. Further, the present disclosure simplifies operational issue of adding / modifying request subscriber publisher.

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

[0121] 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 construedas 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 routing a request through an interface, the method comprising: registering, by a registration unit [302], at an event routing manager (ERM) [1070], an event from a service auditor; receiving, by a transceiver unit [304], at the ERM [1070], a request associated with the event from the service; determining, by a determination unit [306], at the ERM [1070], an event data associated with the request; transmitting, by the transceiver unit [304], from the ERM [1070], the request to a service auditor (SA) via the interface based on the event data; and sending, by the transceiver unit [304], from the ERM [1070], the event to the service.

2. The method as claimed in claim 1, wherein the event data comprises an event type data, a publisher data and a subscriber data.

3. The method as claimed in claim 2, wherein the event type data is one of an event type and an event acknowledgement type.

4. The method as claimed in claim 3, wherein the event type data of the event is the event type.

5. The method as claimed in claim 2, wherein the publisher data associated with the event is the service auditor and the subscriber data associated with the event is the service.

6. The method as claimed in claim 1, wherein sending, by the transceiver unit [304], from the ERM [1070], the event to the service comprises: receiving, by a transceiver unit [304], at the service auditor, the event for the service.

7. The method as claimed in claim 1, wherein the interface is an SA EM interface.

8. A method for routing a request through an interface, the method comprising: registering, by a registration unit [302], at an event routing manager (ERM) [1070], an event from a service ;receiving, by a transceiver unit [304], at the ERM [1070], a request associated with the event from the service auditor via the interface; determining, by a determination unit [306], at the ERM [1070], an event data associated with the request; transmitting, by the transceiver unit [304], from the ERM [1070], the request to a service based on the event data; and sending, by the transceiver unit [304], from the ERM [1070], the event to the service auditor (SA) via the interface.

9. The method as claimed in claim 8, wherein the event data comprises an event type data, a publisher data and a subscriber data.

10. The method as claimed in claim 9, wherein the event type data is one of an event type and an event acknowledgement type.

11. The method as claimed in claim 10, wherein the event type data of the event is the event type.

12. The method as claimed in claim 9, wherein the publisher data associated with the event is the service and the subscriber data associated with the data is the service auditor.

13. The method as claimed in claim 8, wherein sending, by the transceiver unit [304], from the ERM [1070] the event to the service auditor via the interface comprises: receiving, by a transceiver unit [3048], at the service, the event for the service auditor (SA).

14. The method as claimed in claim 8, wherein the interface is an SA EM interface.

15. A system for routing a request through an interface, the system comprising: a registration unit [302], configured to register, at an event routing manager (ERM) [1070], an event from a service auditor; a transceiver unit [304], configured to receive, at the ERM [1070], a request associated with the event from the service; a determination unit [306], configured to determine, at the ERM [1070], an event data associated with the request;the transceiver unit [304], configured to transmit, from the ERM [1070], the request to a service auditor (SA) via the interface based on the event data; and the transceiver unit [304], configured to send, from the ERM [1070], the event to the service.

16. The system as claimed in claim 15, wherein the event data comprises an event type data, a publisher data and a subscriber data.

17. The system as claimed in claim 16, wherein the event type data is one of an event type and an event acknowledgement type.

18. The system as claimed in claim 17, wherein the event type data of the event is the event type.

19. The system as claimed in claim 16, wherein the publisher data associated with the event is the service auditor and the subscriber data associated with the event is the service.

20. The system as claimed in claim 15, wherein for sending, by the transceiver unit [304], from the ERM [1070], the event to the service, the system comprises: a transceiver unit [304], configured to receive, at the service auditor, the event for the service.

21. The system as claimed in claim 15, wherein the interface is an SA EM interface.

22. A system for routing a request through an interface, the system comprising: a registration unit [302], configured to register, at an event routing manager (ERM) [1070], an event from a service; a transceiver unit [304], configured to receive, at the ERM [1070], a request associated with the event from the service auditor via the interface; a determination unit [306], configured to determine, at the ERM [1070], an event data associated with the request; the transceiver unit [304], configured to transmit, from the ERM [1070], the request to a service based on the event data; and the transceiver unit [304], configured to send, from the ERM [1070], the event to the service auditor via the interface.

23. The system as claimed in claim 22, wherein the event data comprises an event type data, a publisher data and a subscriber data.

24. The system as claimed in claim 23, wherein the event type data is one of an event type and an event acknowledgement type.

25. The system as claimed in claim 24, wherein the event type data of the event is the event type.

26. The system as claimed in claim 23, wherein the publisher data associated with the event is the service and the subscriber data associated with the data is the service auditor (SA).

27. The system as claimed in claim 22, wherein for sending, by the transceiver unit [304], from the ERM [1070] the event to the service auditor via the interface, the system comprises: a transceiver unit [304], configured to receive, at the service, the event for the service auditor (SA).

28. The system as claimed in claim 22, wherein the interface is an SA EM interface.

29. A non-transitory computer-readable storage medium storing instructions for routing a request via an interface, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: a registration unit [302] to register, at an event routing manager (ERM), an event from a service auditor; a transceiver unit [304] to receive, at the ERM, a request associated with the event from the service; a determination unit [306] to determine, at the ERM, an event data associated with the registered request;- the transceiver unit [304] to transmit, from the ERM the request to a service auditor via the interface based on the event data; and- the transceiver unit [304] to send, from the ERM, the event to the service.

30. A non-transitory computer-readable storage medium storing instructions for routing a request via an interface, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: a registration unit [302] to register, at an event routing manager (ERM), an event from a service; a transceiver unit [304] to receive, at the ERM, a request associated with the event from the service auditor via the interface; a determination unit [306] to determine, at the ERM, an event data associated with the registered request; - the transceiver unit [304] to transmit, from the ERM the request to a service based on the event data; and- the transceiver unit [304], configured to send, from the ERM the event to the service auditor via the interface.

Images