Claims:1. A system for secure management and configuration of hardware interfaces associated with a network, the system including:
an embedded system configured to identify and expose a plurality of hardware interfaces as respective configuration application program interfaces (APIs);
the respective configuration APIs being respectively configured to be plugged into a target system to perform a plurality of steps, the steps including:
establishing an simple network management protocol link (SNMP) communication link;
collecting data associated with the hardware interfaces by means of interface agent;
populating the interfaces’ classes with the collected data; and
mapping the populated classes to respective individual APIs; and
wherein the respective individual APIs are generic;
wherein the APIs are deployable;
wherein the APIs are capable of a third-party software integration;
wherein the respective individual APIs are capable of being plugged into a plurality of other embedded systems; and
wherein the plurality of hardware interfaces includes various types of hardware interfaces.
2. The system as claimed in claim 1, wherein the plurality of steps are wrapped in a single service call to the hardware interface.
3. The system as claimed in claim 2, wherein the embedded system further includes a web server module, an operating system, a virtual machine, and various types of hardware interfaces.
4. The system as claimed in claim 3, wherein the APIs includes modules associated with session, manager, service, and interface; and wherein the manager module is configured to create, request, respond, and maintain an SNMP profile associated with a respective hardware interface.
5. The system according to claim 4, wherein the system is utilized with respect to hardware interfaces associated with a full stack architecture that covers management aspects from a physical layer to an application layer, of an OSI model.
6. The system as claimed in claim 5, wherein the plurality of hardware interfaces are capable of correspondence with an SNMP manager by means of an in-built network agent.
7. The system as claimed in claim 6, wherein the correspondence aspect between the plurality of hardware interfaces and the SNMP manager includes requesting a parameter associated with a given hardware interface, and interacting with the hardware interface by means of an acknowledgement from the hardware interface.
8. The system as claimed in claim 7, wherein, when the embedded system identifies more than one hardware interface from amongst the plurality of hardware interfaces with the hardware interfaces being of a same type, the hardware interfaces are represented as a multiple instance of an MIB associated with the hardware interfaces using context name from the SNMP profile.
9. The system as claimed in claim 8, wherein the context name is a slot number of the hardware interface in a chassis, the slot number being capable of representing the hardware interface at an API endpoint.
10. The system according to claim 9, wherein the embedded system is configured to perform in real-time.
, Description:TECHNICAL FIELD
[001] The present disclosure generally relates to full stack architectures, and more specifically, to a full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.

BACKGROUND
[002] Background description includes information that can be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[003] With the advent of the world wide web (WWW) and the development of computer and communication technology, network management of communication devices becomes increasingly complicated. Most of the components used in enterprise network have built-in network agents that can respond to issues associated with a given Simple Network Management Protocol (SNMP) network management system. To configure those devices, a given device’s Management Information Base (MIBS) needs to be shared with a third-party management software having SNMP support. Sharing of MIBS with third-party involves risk when, for instance, an SNMP v2 is the only version supported on the agent side. While an element manager can offer many benefits for an organization, for example flexibility and development cost saving, it can also create challenges in terms of security, particularly with regards to a management system installed on a third-party system.
[004] In addition, there is also a particular challenge with regards to the integration of a legacy system with a modern system. In most of the cases, they have their own proprietary desktop application, or an SNMP based management to manage the system. These systems complicate integration efforts but replacing them isn’t always a viable option. These issues would invariably restrain product-based companies from modernizing their legacy system.
[005] In the current art, disclosures pertaining to full stack architectures are present. For example, patent document no. 201821007151 pertains to a three-layered architecture that can support real time visualization while US patent document no. US20180026829A1 pertains to a device or vendor independent network switch management via embedded management controller stack. While these documents address network management issues, they have not however addressed aspects of secure network management with regards to associated various types of hardware interfaces. Therefore, there is a need in the art to provide a reliable and efficient full stack architecture for secure network monitoring and configuration of hardware interfaces that can be utilized in both legacy and modern systems.
[006] All publications herein are incorporated by reference to the same extent as if each individual publication or patent application were specifically and individually indicated to be incorporated by reference. Where a definition or use of a term in an incorporated reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply.
[007] In some embodiments, the numbers expressing quantities or dimensions of items, and so forth, used to describe and claim certain embodiments of the invention are to be understood as being modified in some instances by the term “about.” Accordingly, in some embodiments, the numerical parameters set forth in the written description and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by a particular embodiment. In some embodiments, the numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of some embodiments of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as practicable. The numerical values presented in some embodiments of the invention may contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.
[008] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
[009] Groupings of alternative elements or embodiments of the invention disclosed herein are not to be construed as limitations. Each group member can be referred to and claimed individually or in any combination with other members of the group or other elements found herein. One or more members of a group can be included in, or deleted from, a group for reasons of convenience and/or patentability. When any such inclusion or deletion occurs, the specification is herein deemed to contain the group as modified thus fulfilling the written description of all groups used in the appended claims.

OBJECTS OF THE PRESENT DISCLOSURE
[0010] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0011] It is an object of the present disclosure to provide a full stack architecture for secure network monitoring and configuration that allows non-sharing of MIBS with third party management software.
[0012] It is another object of the present disclosure to provide a full stack architecture for secure network monitoring and configuration that can be used for any product having n types of hardware interfaces of different numbers in contrast to approaches relying solely on a specific product with fixed type and number of interfaces.
[0013] It is another object of the present disclosure to provide a full stack architecture for secure network monitoring and configuration that allows integration of legacy systems with modern third party systems without changing existing implementation details.
[0014] It is another object of the present disclosure to provide a full stack architecture for secure network monitoring and configuration having a modular software design.
[0015] It is another object of the present disclosure to provide a full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0016] It is another object of the present disclosure to provide a simple and effective full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0017] It is another object of the present disclosure to provide a reliable and efficient full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0018] It is another object of the present disclosure to provide a robust full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.

SUMMARY
[0019] The present disclosure generally relates to full stack architectures, and more specifically, to a full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0020] This summary is provided to introduce simplified concepts of a system for time bound availability check of an entity, which are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended for use in determining/limiting the scope of the claimed subject matter.
[0021] An aspect of the present disclosure pertains to a system for secure management and configuration of hardware interfaces associated with a network. The system includes an embedded system configured to identify and expose a plurality of hardware interfaces as respective configuration application program interfaces (APIs). The respective configuration APIs being respectively configured to be plugged into a target system to perform a plurality of steps. The steps includes establishing an simple network management protocol link (SNMP) communication link; collecting data associated with the hardware interfaces by means of interface agent; populating the interfaces’ classes with the collected data; and mapping the populated classes to respective individual APIs.
[0022] In an aspect, the respective individual APIs are generic.
[0023] In an aspect, the APIs are deployable.
[0024] In an aspect, the APIs are capable of a third-party software integration.
[0025] In an aspect, the respective individual APIs are capable of being plugged into a plurality of other embedded systems.
[0026] In an aspect, the plurality of hardware interfaces includes various types of hardware interfaces.
[0027] In an aspect, the plurality of steps are wrapped in a single service call to the hardware interface.
[0028] In an aspect, the embedded system further includes a web server module, an operating system, a virtual machine, or a voice gateway chassis.
[0029] In an aspect, the APIs includes modules associated with session, manager, service, and interface; and wherein the manager module is configured to create, request, respond, and maintain an SNMP profile associated with a respective hardware interface.
[0030] In an aspect, the system is utilized with respect to hardware interfaces associated with a full stack architecture that covers management aspects from a physical layer to an application layer, of an open systems interconnection (OSI) model.
[0031] In an aspect, the plurality of hardware interfaces are capable of correspondence with an SNMP manager by means of an in-built network agent.
[0032] In an aspect, the correspondence aspect between the plurality of hardware interfaces and the SNMP manager includes requesting a parameter associated with a given hardware interface, and interacting with the hardware interface by means of an acknowledgement from the hardware interface.
[0033] In an aspect, when the embedded system identifies more than one hardware interface from amongst the plurality of hardware interfaces with the hardware interfaces being of a same type, the hardware interfaces are represented as a multiple instance of an MIB associated with the hardware interfaces using context name from the SNMP profile.
[0034] In an aspect, the context name is a slot number of the hardware interface, the slot number being capable of representing the hardware interface at an API endpoint. The slot number of hardware interface can be associated witha chassis. The hardware interface in question can be associated with a chassis.
[0035] In an aspect, the embedded system is configured to perform in real-time.
[0036] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.

BRIEF DESCRIPTION OF THE DRAWINGS
[0037] The diagrams are for illustration only, which thus is not a limitation of the present disclosure, and wherein:
[0038] FIGs. 1A-1D illustrates multiple variants of voice gateway chassis as associated with hardware interfaces for use in association with an architecture associated with a system to securely manage and configure a network, in accordance with an embodiment of the present disclosure.
[0039] FIG. 2 illustrates a flowchart associated with SNMP agent development and in particular, showing the functions of a system to securely manage and configure a network, in accordance with an embodiment of the present disclosure.
[0040] FIG. 3 illustrates a three layer architecture associated with a system to securely manage and configure a network, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION
[0041] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[0042] In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.
[0043] Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, and firmware and/or by human operators.
[0044] Various methods described herein may be practiced by combining one or more machine-readable storage media containing the code according to the present invention with appropriate standard computer hardware to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, routines, subroutines, or subparts of a computer program product.
[0045] If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
[0046] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
[0047] Exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. These exemplary embodiments are provided only for illustrative purposes and so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those of ordinary skill in the art. The invention disclosed may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Various modifications will be readily apparent to persons skilled in the art. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure). Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.
[0048] Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named element.
[0049] Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The term “machine-readable storage medium” or “computer-readable storage medium” includes, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).A machine-readable medium may include a non-transitory medium in which data may be stored and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-program product may include code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
[0050] Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks.
[0051] Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
[0052] Each of the appended claims defines a separate invention, which for infringement purposes is recognized as including equivalents to the various elements or limitations specified in the claims. Depending on the context, all references below to the "invention" may in some cases refer to certain specific embodiments only. In other cases, it will be recognized that references to the "invention" will refer to subject matter recited in one or more, but not necessarily all, of the claims.
[0053] All methods described herein may be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.
[0054] Various terms as used herein are shown below. To the extent a term used in a claim is not defined below, it should be given the broadest definition persons in the pertinent art have given that term as reflected in printed publications and issued patents at the time of filing.
[0055] The present disclosure generally relates to full stack architectures, and more specifically, to a full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0056] The present approach disclosed herein creates an MIB (Management Information Base) for each manageable interface. SNMP agent will use the existing product specific implementation to populate the data of MIB variables. It will reply for all SNMP requests. Each interface will be exposed as a resource using Restful Web services. There will be a separate API to manage each interface and can be integrated with any third-party software. This approach is being applied on Communication System management.
[0057] This approach will allow the management of Legacy Systems to be managed using WWW without modifying the underlying implementation. This approach can be used and implemented in all type of hardware systems with multiple interfaces.
[0058] The present disclosure provides a three level layered architecture for network monitoring and configuration system. The first layer or layer 1 is an interface level module consisting of a card process. The second layer or layer 2 is a data Collection module consisting of an SNMP agent. The third layer or layer 3 is an API Module.
[0059] FIGs. 1A-1D illustrates multiple variants of voice gateway chassis as associated with hardware interfaces for use in association with an architecture associated with a system to securely manage and configure a network , in accordance with an embodiment of the present disclosure. FIG. 1 depicts a single card chassis while FIG. 2 depicts a multiple card chassis. FIG. 3 depicts a multiple card chassis having n number of each type as herein mentioned while FIG. 4 depicts a multiple card chassis with n types of a varying number as herein mentioned.
[0060] Referring now to FIGs.1A-1D again, it illustrates a generalized embodiment of communication system. For purpose of this disclosure communication system can include any interface or aggregate of interfaces operable to voice. For example communication system can be an analog/digital system including only a single analog/digital interface card; an analog/digital system including multiple analog/digital cards, a system including different types of interface cards of same number, a system including different types of interface cards of different number, or any other communication system chassis and may vary in size, shape, performance, types of interface, number of interface and price. Further system can include bus to transmit information between interface cards. Further interface card can also include an embedded device such as a System-on-a-Chip (SoC), storage device memory card that can store our Interface process, SNMP Agent, Web server, Web pages and any other executable code to manage the system.
[0061] FIG. 3 illustrates a three layer architecture associated with a system to securely manage and configure a network, in accordance with an embodiment of the present disclosure. At 301, Layer 1is responsible for running card process (or process associated with a hardware interface) to collect register and counter data, version and other parameter values from the Interface. It will convert the data into information that can be queried and transfer data to layer 2 using inter-process communication. A card process can be a functionality or a feature as associated with a hardware interface as can be appreciated by a person skilled in the art.
[0062] At 302, Layer 2 layer is of SNMP Agent (not shown), data is queried from card process. SNMP agent resides on the managed System. It can be a software that runs on a piece of network equipment (host, radio, router, printer, gateway or others) and that maintains information about its configuration and current state in a database. The agent collects data from the managed device and translates that information into a format that can be passed over the network using SNMP.
[0063] Referring now to FIG. 2, at 205A, 205B, 206, in every MIB the objects are divided into two categories, among which are highlighted here in particular: (1) Interface: contains general information of the telephony interface; and(2) Ports: contains information relating to the hardware ports of the interface.FIG. 2 is also a simplified diagram illustrating a strategy to create a hierarchical structure of parameters for a hardware interface. Interface data can be organized in two ways i.e., scalar data (at 205A) and tabular data (at 205B). Data unique to interface is organized in scalar format and data unique to interface ports is organized in tabular format.
[0064] Referring again to FIG. 3, at 303, layer 3 is an API layer. It is based on representational state transfer (RESTful) web services which can be part of a web based GUI which is a part of Network Monitoring System's User Interface (UI). The user can interact with the system in this layer. This layer consists of modules like Session, Manager, Service and Interface Module.
[0065] The plurality of manager module in the API can further include a SNMP profile creation method, Request method, Response method and a unique ID maintenance method. SNMP profile creation method is responsible for creating a SNMP profile with User Name, Security name, Security level, Authentication Protocol, Authentication key and Encryption key. Unique ID maintenance method is responsible for maintaining the unique ID’s of all the objects of MIBS. Request/response methods contacts an SNMP agent using OID’s to query or modify the database at the agent.
[0066] Services Module converts the SNMP MIB of each interface to distinguishable entities with interface generic information as normal types and port information as a separate entity. Each distinguishable entity is a resource. Every hardware interface(card) is exposed as an individual API and uniquely identified by a URI.API can be used by any third-party NMS for integration. Instead of giving MIBS and control of Manager to the third party, only API information is sufficient for integration. It implements a bunch of RESTful API’s to accomplish a robust management of Communication System.
[0067] REST style of Web Service development offers great simplicity, flexibility and hence is being adopted in several domains. REST style reduces the load on servers considerably and hence the additional non-configuration services in the Communication System can be easily developed and deployed.
[0068] Outcome of layer 3 includes various endpoints that exposes hardware interfaces to the external parties.
[0069] Referring now to FIG. 1D, various cards of different types and numbers are installed in a given System. Mapping of interface cards to the API endpoints is given in the following URLs: (i) GET/system/interface/analog/1 :API Endpoint to get the information of analog card installed into first slot of communication System; (ii) GET /system/interface/digital/2/ports/ :API Endpoint to get the information of all ports of digital card installed into second slot of communication System; (iii) GET /system/interface/digital/2/port/1/ :API Endpoint to get the information of first port of digital card installed into second slot of communication System; (iv) GET /system/interface/radio/3/port/2/gain/ :API Endpoint to get the Gain value of second port of radio card installed into third slot of communication System; (v) PUT /system/interface/media/1/channel/2/mode / :API Endpoint to change the Mode of second channel of Media compression card installed into first slot of communication system.Method POST and DELETE are restricted since No of ports/channels are fixed in interface cards. Method on a particular endpoint can be allowed based on the requirement.
[0070] Referring now to FIG. 3, it illustrates a system for providing a interface API for use in managing an interface of Communication System, in accordance with anembodiment. In next layer at the top, these API’s can be used by third party software to configure the interfaces of the system.
[0071] In accordance with an embodiment, described herein is a system and full Stack Architecture for the management of various hardware interfaces from the physical layer (Back end) till application layer (Front end) of OSI model. It will expose the hardware Interfaces as configuration API by using embedded web server module, embedded Linux, and embedded JVM and so on. The configuration API can be plugged into the target system to perform a plurality of steps required for managing the interfaces, including enabling SNMP communication from the local environment to system. The plurality of steps can be wrapped in single service call to the hardware interface; and can include creating a session, establishing a SNMP communication link, collecting the interface data from the interface agent, populating the entity interfaces classes with the data and mapping it to individual API. The API is generic and can be plugged into a plurality of Communication products.
[0072] The present disclosure provides the following enumerated benefits while other benefits can readily be inferred by a person skilled in the art and information pertaining to such disclosure are intended to be covered by this disclosure. Thus, without any limitations as to the following, benefits include: (i)This approach does not require sharing of MIBS with third party management software;(ii) This approach is mainly focused on communication systems having multiple variants of telephony interfaces cards i.e. analog interface cards, digital telephony cards, radio interface, media compression cards and hybrid cards; (iii) This approach can also be used for any product having n types of hardware interfaces of different numbers in contrast to approaches relying solely on a specific product with fixed type and number of interfaces; (iv) it will also allow integration of legacy systems with modern third party systems without changing existing implementation details;(v) it will expose each hardware interface as an API that can be integrated with any third-party standard-compliant management software; (vi) This approach also has a modular software design. It allows replacing or adding any component (module) i.e. any interface card without affecting the rest of the system. And each module can work independently with any other software; (vii) It enables human users to be free from complicated hardware interfaces and API enables developers to integrate with any third party software easily; (viii) It allows proper decoupling between different interfaces by exposing them as different endpoints of API; (ix) It allows creation of API that would be used by clients (or yourself).
[0073] The present disclosure is directed to a full stack architecture that covers the management aspects of hardware interfaces from the physical layer (Back end) till application layer (User interface) of OSI model. The present disclosure also pertains to an architecture for monitoring and configuration of a system that includes different types of hardware interfaces (Cards) through a deployable API. In an embodiment, this includes any numbers and types of hardware interfaces. In an aspect, each interface MIB is mapped to an individual API that can be integrated with any third-party software. In an aspect, the hardware interfaces are generic and pluggable to a plurality of different types of embedded system.
[0074] In accordance with an embodiment, described herein is a system and full Stack Architecture for the management of various hardware interfaces from the physical layer (Back end) till application layer (Front end) of OSI model. It will expose the hardware Interfaces as configuration API by using embedded web server module, embedded Linux, and embedded JVM and so on. The configuration API can be plugged into the target system to perform a plurality of steps required for managing the interfaces, including enabling SNMP communication from the local environment to system. The plurality of steps can be wrapped in single service call to the hardware interface; and can include creating a session, establishing a SNMP communication link, collecting the interface data from the interface agent, populating the entity interfaces classes with the data and mapping it to individual API. The API is generic and can be plugged into a plurality of Communication products.
[0075] In an aspect, the architecture is used for monitoring and configuration of the interfaces, wherein the interfaces should have built-in network agents that can respond to an SNMP manager. The configuration functionality allows requesting the parameters of interfaces and changing them with the interface acknowledgement. In an aspect, different number of same hardware interfaces in a given communication system are represented as multiple instances of an MIB using Context Name. In an aspect, the Slot No of the hardware interfaces in system is the value of Context Name field as associated with the SNMP protocol, which again will be used as unique ID of the API endpoint. In an aspect, real time data from interface card to API, any change in configuration will be performed based on the acknowledgement from the Interface.
[0076] The present disclosure is envisioned to be performed using appropriate physical devices that may be appreciated by a person skilled in the art. As such all physical devices comprising respective various physical materials serve their respective functions and all such materials and their respective manufacturing methods are intended to be covered by this disclosure.
[0077] Thus, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures can be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function can be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named.
[0078] While embodiments of the present invention have been illustrated and described, it will be clear that the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents will be apparent to those skilled in the art, without departing from the spirit and scope of the invention, as described in the claim.
[0079] In the foregoing description, numerous details are set forth. It will be apparent, however, to one of ordinary skill in the art having the benefit of this disclosure, that the present invention can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, to avoid obscuring the present invention.
[0080] As used herein, and unless the context dictates otherwise, the term "coupled to" is intended to include both direct coupling (in which two elements that are coupled to each other contact each other)and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used synonymously. Within the context of this document terms "coupled to" and "coupled with" are also used euphemistically to mean “communicatively coupled with” over a network, where two or more devices are able to exchange data with each other over the network, possibly via one or more intermediary device.
[0081] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps can be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C …. and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
[0082] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention can be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE PRESENT DISCLOSURE
[0083] The present disclosure provides a full stack architecture for secure network monitoring and configuration that allows non-sharing of MIBS with third party management software.
[0084] The present disclosure provides a full stack architecture for secure network monitoring and configuration that can be used for any product having n types of hardware interfaces of different numbers in contrast to approaches relying solely on a specific product with fixed type and number of interfaces.
[0085] The present disclosure provides a full stack architecture for secure network monitoring and configuration that allows integration of legacy systems with modern third party systems without changing existing implementation details.
[0086] The present disclosure provides a full stack architecture for secure network monitoring and configuration having a modular software design.
[0087] The present disclosure provides a full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0088] The present disclosure provides a simple and effective full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0089] The present disclosure provides a reliable and efficient full stack architecture for secure network monitoring and configuration that can be utilized in both legacy and modern systems.
[0090] The present disclosure provides a robust full stack architecture forsecure network monitoring and configuration that can be utilized in both legacy and modern systems.