WO2025017728A1

WO2025017728A1 - Method and system for automated management of parameter configurations across multi-vendor network elements

Info

Publication number: WO2025017728A1
Application number: PCT/IN2024/051304
Authority: WO
Inventors: Sundaresh -; Aayush Bhatnagar; Pradeep Kumar Bhatnagar; Chaitanya Reddy POLSONI; Vivek Patel; Ritesh Kumar; Diksha BAKRIYA; Mukesh Kumar; Rishi KOUL
Original assignee: Jio Platforms Limited
Priority date: 2023-07-19
Filing date: 2024-07-18
Publication date: 2025-01-23

Abstract

The present disclosure relates to a method [300] and a system [200] for automated management of parameter configurations across multi-vendor network elements, the method [300] comprising the steps of selecting at least one vendor from a plurality of vendors in a network environment. The method [300] comprises generating, a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified. The method [300] comprises validating accuracy and compatibility of the set of instructions of the generated configuration recipe.

Description

METHOD AND SYSTEM FOR AUTOMATED MANAGEMENT OF PARAMETER CONFIGURATIONS ACROSS MULTI-VENDOR NETWORK ELEMENTS

FIELD OF INVENTION

[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for automated management of parameter configurations across multi-vendor network elements.

BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third- generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The upcoming sixth-generation (6G) technology is anticipated to bring transformative advancements, including operation in the terahertz (THz) frequency range for data transfer rates up to 1 terabit per second (Tbps), deep integration of Al for optimized network management, and ultra-low latency for realtime applications like holographic communication and immersive AR/VR experiences. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] Conventional approaches to handling changes in parameters require manual configuration for each network element. This process is highly time-consuming and inefficient, especially in large networks where thousands of parameters may need modifications. In a multi-vendor environment, each vendor has a unique set of parameters and associated commands. This heterogeneity makes the management process more complex, requiring specialized knowledge about each vendor's specific configuration requirements. Traditional methods do not account for on-the-fly changes. If the network or software versions change, the whole process of setting rules needs to be repeated, which increases the possibility of errors and inconsistencies. The manual processes of the prior art don't scale well. As the size and complexity of the networks grows, managing parameter changes becomes progressively more challenging and labor-intensive. In the traditional systems, there is no central repository for storing and managing the parameter change commands for different vendors, node types, and software versions. This absence makes the management process cumbersome and prone to errors. Prior methods often require manual intervention for each parameter change, resulting in higher costs and increased potential for human error. There is a lack of automation for routine tasks, such as scheduling and applying sequences of commands, which can significantly slow down network operations and configuration management.

[0005] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks and to provide a method and system for automated management of parameter configurations across multi-vendor network elements.

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 automated management of parameter configurations across multi-vendor network elements, the method comprising the steps of selecting, by a selecting unit, at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. The method further comprises generating, by a generating unit, a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs. The method further comprises validating, by a validating unit, accuracy and compatibility of the set of instructions of the generated configuration recipe. The method further comprises automatically deploying, by a deploying unit, the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

[0008] In an exemplary aspect of the present disclosure, wherein generating the configuration recipe comprises at least one of manual input, bulk data upload, and parsing rules derived from pre-existing configurations.

[0009] In an exemplary aspect of the present disclosure, wherein prior to the selection of the at least one recipe template from the set of recipe templates, the step of generating the configuration recipe further comprises accessing, by a processing unit, the central repository database that stores the set of recipe templates, wherein the set of set of recipe templates corresponds to the set of parameters, network element types, and software versions.

[0010] In an exemplary aspect of the present disclosure, the method comprises generating, by an alerting unit, an alert if none of the recipe templates matches with the at least one network element and the set of parameters to be modified.

[0011] In an exemplary aspect of the present disclosure, the method comprises generating, by an alerting unit, an alert if the generated configuration recipe fails to validate.

[0012] In an exemplary aspect of the present disclosure, the method comprises storing, by a storing unit, the generated recipe in the central repository database.

[0013] Another aspect of the present disclosure may relate to a system for automated management of parameter configurations across multi-vendor network elements, the system comprises a selecting unit configured to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. The system further comprises a generating unit connected to at least the selecting unit, wherein the generating unit configured to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs. The system comprises a validating unit connected to at least the generating unit, wherein the validating unit configured to validate accuracy and compatibility of the set of instructions of the generated recipe. The system further comprises a deploying unit connected to at least the validating unit, wherein the deploying unit configured to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

[0014] Another aspect of the present disclosure may relate to a user equipment for automated management of parameter configurations across multi-vendor network elements, the user equipment comprising a system, the system further comprising a selecting unit configured to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels; a generating unit configured to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs; a validating unit configured to validate accuracy and compatibility of the set of instructions of the generated recipe; and a deploying unit configured to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element. [0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for automated management of parameter configurations across multi-vendor network elements, the instructions include executable code which, when executed by one or more units of a system, causes: a selecting unit of the system to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. Further, the instructions include executable code which, when executed by one or more units of a system, causes a generating unit of the system to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs. Further, the instructions include executable code which, when executed by one or more units of a system, causes a validating unit of the system to validate accuracy and compatibility of the set of instructions of the generated recipe. Further, the instructions include executable code which, when executed by one or more units of a system, causes a deploying unit of the system to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

OBJECTS OF THE DISCLOSURE

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

[0017] It is an object of the present disclosure to provide a system and a method for automated management of parameter configurations across multi-vendor network elements.

[0018] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that automates the process of managing parameter configurations across network elements from different vendors. This reduces the need for manual intervention, thereby reducing human error and increasing efficiency. [0019] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that reduces the time and resources required to manage parameter configurations across different network elements, increasing the overall efficiency of network operations.

[0020] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that creates a central repository for storing all parameter change commands for different vendors, node types, and software versions. This allows for easier access and management of these commands.

[0021] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that provides a system that can dynamically adapt to changes in the network or software versions, allowing for on-the-fly modifications based on pre-configured rules.

[0022] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that is designed to handle the management of parameter configurations for networks of varying sizes and complexities, thus providing a scalable solution.

[0023] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that offers a flexible solution that can handle varying functionalities across multiple versions of network elements.

[0024] It is another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that provides customizable templates that can be applied to any parameter change, enabling users to tailor the configuration process to their specific needs.

[0025] It is yet another object of the present disclosure to provide a system and method for automated management of parameter configurations across multi-vendor network elements that interacts with a vendor's Element Management System (EMS) for any configuration change, ensuring that changes occur in a structured and defined manner. DESCRIPTION OF THE DRAWINGS

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

[0027] FIG. 1 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.

[0028] FIG. 2 illustrates an exemplary block diagram of a system for automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary implementations of the present disclosure.

[0029] FIG. 3 illustrates a method flow diagram for automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary implementations of the present disclosure.

[0030] FIG. 4 illustrates an exemplary system architecture indicating the process automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary embodiments of the present disclosure.

[0031] FIG. 5 illustrates an exemplary flow diagram indicating the process automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary embodiments of the present disclosure.

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

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

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

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

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

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

[0038] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0039] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

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

[0042] gNodeB" (gNB) refers to the base station component in 5G (fifth-generation) wireless networks. It is an essential element of the Radio Access Network (RAN) responsible for transmitting and receiving wireless signals to and from user devices, such as smartphones, tablets, and Internet of Things (loT) devices. As in 5G networks, there are similar components in other generations of wireless networks. Here are a few examples: Base Transceiver Station (BTS): In 2G (second-generation) networks, the BTS serves as the base station responsible for transmitting and receiving wireless signals. It connects mobile devices to the cellular network infrastructure. NodeB: in 3G (third-generation) networks, the NodeB is the base station component that enables wireless communication. It facilitates the transmission and reception of signals between user devices and the network. eNodeB: in 4G (fourth-generation) LTE (Long-Term Evolution) networks, the eNodeB serves as the base station. It supports high-speed data transmission, low latency, and improved network capacity. Access Point (AP): In Wi-Fi networks, an access point functions as a central hub that enables wireless devices to connect to a wired network. It provides a wireless interface for devices to access the network and facilitates communication between them. The examples illustrate the base station components in different generations of wireless networks, such as BTS in 2G, NodeB in 3G, eNodeB in 4G LTE, and gNodeB in 5G. Each component plays a crucial role in facilitating wireless connectivity and communication between user devices and the network infrastructure.

[0043] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0044] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system. [0045] 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 automated management of parameter configurations across multi-vendor network elements.

[0046] As discussed in the background section, cconventional approaches to handling changes in parameters requires manual configuration for each network element. This process is highly timeconsuming and inefficient, especially in large networks where thousands of parameters may need modifications. In a multi-vendor environment, each vendor has a unique set of parameters and associated commands. This heterogeneity makes the management process more complex, requiring specialized knowledge about each vendor's specific configuration requirements. Traditional methods do not account for on-the-fly changes. If the network or software versions change, the whole process of setting rules needs to be repeated, which increases the possibility of errors and inconsistencies. The manual processes of the prior art don't scale well. As the size and complexity of the network grows, managing parameter changes becomes progressively more challenging and labor-intensive. In the traditional system, there is no central repository for storing and managing the parameter change commands for different vendors, node types, and software versions. This absence makes the management process cumbersome and prone to errors. Prior methods often require manual intervention for each parameter change, resulting in higher costs and increased potential for human error. There is a lack of automation for routine tasks, such as scheduling and applying sequences of commands, which can significantly slow down network operations and configuration management.

[0047] Thus, there exists an imperative need in the art to provide a method and system for automated management of parameter configurations across multi-vendor network elements. The proposed invention addresses these issues by automating the configuration management process, providing flexibility and scalability, and streamlining the overall network parameter configuration across multiple software versions and vendors. By doing so, it significantly reduces the time, effort, and errors associated with manual configuration changes, ultimately improving the efficiency and effectiveness of network operations.

[0048] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (also referred to herein as a computer system [100]) 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 [100] may also implement a method for managing one or more notifications in a production system utilising the system. In another implementation, the computing device [100] itself implements the method for managing one or more notifications in a production system using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0049] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for example, a general -purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104], The main memory [106] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [104], Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104],

[0050] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], 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 [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104], Another type of user input device may be a cursor controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112], 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. [0051] The computing device [100] 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 [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106], Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110], Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] 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.

[0052] The computing device [100] also may include a communication interface [118] coupled to the bus [102], The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122], For example, the communication interface [118] 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 [118] 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 [118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0053] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication interface [118], In the Internet example, a server [130] might transmit a requested code for an application program through the Internet [128], the ISP [126], the host [124], the local network [122] and the communication interface [118], The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.

[0054] Referring to FIG. 2, an exemplary block diagram of a system [200] for automated management of parameter configurations across multi-vendor network elements, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one selecting unit [201], at least one generating unit [202], at least one validating unit [203], at least one deploying unit [204], at least one processing unit [205], at least one alerting unit [206] and at least one storage unit [207], Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [200] should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device/ user equipment [100] to implement the features of the present disclosure. The system [200] may be a part of the user device [100]/ or may be independent of but in communication with the user device [100] (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.

[0055] The system [200] is configured for automated management of parameter configurations across multi-vendor network elements, with the help of the interconnection between the components/units of the system [200],

[0056] In an exemplary implementation, parameter configuration refers to the process of setting and adjusting various operational parameters within network elements. These parameters could include IP addresses, routing protocols, bandwidth allocations, and security settings.

[0057] In an example, the multivendor network elements refer to network devices or components (such as a router, switch, or firewall) manufactured by different vendors.

[0058] The system for automated management of parameter configurations across multi-vendor network elements, comprises a selecting unit [201] configured to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. In an implementation, the system [200] may comprise a recipe builder from which the vendor may be selected from a list of vendors at an interface of the recipe builder which displays the list. The recipe builder may maintain the list of vendors for configuration.

[0059] In an example, the network environment encompasses the entire infrastructure of interconnected devices, systems, and components that facilitate communication and data transfer. This includes hardware, software, protocols, and standards used in the network. The sizes may range from small, simple devices to large, complex systems. The complexity levels denote the degree of complexity in terms of configuration, capabilities, and functionalities.

[0060] The present disclosure encompasses the selecting unit [201] is responsible for choosing at least one vendor from multiple vendors present in a network environment. This environment consists of numerous network elements, which vary in size and complexity and come from various vendors. The network elements could include devices like routers, switches, firewalls, etc., that perform various network functions. The selecting a vendor from a plurality of vendors in a network process could involve assessing the type of network elements from each vendor present in the network, their functionalities, and their compatibility with the automated system. The selection could be determined based on the needs of the network, such as optimizing performance, managing resources, or improving security.

[0061] The system [200] further comprises, a generating unit [202] connected to at least the selecting unit [201], wherein the generating unit [202] configured to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs. The present disclosure encompasses that the generating unit [202] generates the configuration recipe which is a set of instructions used to modify the parameters of a network element. These may be commands, scripts, or procedures. The selection process involves choosing configuration templates based on the characteristics of the network element and the parameters to be modified. In an implementation, the recipe builder may perform the parameter configurations of network elements. Further, the recipe builder can store various configuration recipes which can be applied whenever an operator/user chooses to at a click of a button. A configuration recipe may include commands to change any parameter across any version of any network element type of any vendor. Additionally, a configuration recipe may provide an option to replicate a complete set of commands for all or most parameters associated with a vendor specific network element type across different software versions. [0062] In an example, the modifying involves altering the existing parameter settings of a network element. This may include updating software versions, changing security settings, or adjusting performance parameters.

[0063] These recipes are essentially pre-configured scripts that include all the necessary commands to modify a specific parameter in a network element. This process could involve network engineers or system administrators creating these recipes manually, uploading them from an external source like a text file or an Excel sheet, or automatically generating them using parsing rules, which analyses the network element and its configurations to create the required commands. These templates can be customized based on specific user inputs to meet particular configuration needs. The set of parameters are the values that define how a network element operates. Parameters can include IP addresses, routing protocols, or security settings associated with the at least one network element. The central repository database is a centralized storage location where all the recipe templates are kept. These templates are chosen based on their compatibility with the network element and can be customized through user inputs wherein generating the configuration recipe comprises at least one of manual input, bulk data upload, and parsing rules derived from pre-existing configurations.

[0064] In an example, the user inputs refer to the data provided by the user to modify the configuration recipe to specific requirements. This may include specific parameter values and desired outcomes. In an implementation, the operator/user may customise a recipe template using the recipe builder by providing custom configurations for parameters to modify and map with related commands.

[0065] The system [200] further comprises a validating unit [203] connected to at least the generating unit [202], wherein the validating unit [203] is configured to validate accuracy and compatibility of the set of instructions of the generated recipe. The present disclosure encompasses the validating unit [203] to verify that the set of instructions in the configuration recipe is correct. This ensures that the created recipes are accurate, efficient, and compatible with the network elements. This might involve steps like syntax checking, which verifies the correctness of the commands; functional testing, which checks if the recipe achieves the desired result when applied to a network element; and compatibility testing, which ensures that the recipe works correctly with the network elements of the selected vendor. [0066] The system [200] further comprises a deploying unit [204] connected to at least the validating unit [203], wherein the deploying unit [204] is configured to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element. The present disclosure encompasses the deploying unit [204] is responsible for applying the validated configuration recipes to the network elements. The validated recipe refers to the configuration recipe that has been checked and confirmed by the validating unit [203] for accuracy and compatibility. The deployment is executed through the EMS, which is a centralized system used to manage and monitor network elements. The EMS facilitates the application of configuration changes across the network. The EMS provides tools for configuration, monitoring, and troubleshooting of network devices. The deployment involves applying the stored recipes to the network elements whenever needed. This could involve the system identifying the network elements that require configuration changes, selecting the appropriate recipes from the database, and then executing the commands on the network elements. This process could be automated, reducing the workload on the network operations team.

[0067] The system [200] comprises a processing unit [205], wherein prior to the selection of the at least one recipe template from the set of recipe templates, the processing unit is configured to access the central repository database that stores the set of recipe templates, wherein the set of set of recipe templates corresponds to the set of parameters, network element types, and software versions. In an example, the set of parameters include IP addresses, routing protocols, bandwidth allocations, security settings, QoS settings and VLAN IDs. The network elements, such as routers, switches, firewalls, access points, modems, servers, and network controllers, are included, each with varying sizes and complexity levels. The method ensures that recipe templates are defined to include different software versions, including operating system versions, firmware versions, application software versions, and protocol support versions. The central repository database stores the validated recipes, which acts as a hub for all the configuration command recipes. The database might have sophisticated features for managing the recipes, like search functions, categorization based on vendors or network elements, and version control to track the changes made to the recipes. The present disclosure encompasses the processing unit [205] is responsible for handling data operations before selecting the appropriate recipe template. This processing unit [205] is central in accessing the central repository database where all recipe templates are stored. By accessing this database, the processing unit [205] ensures that the selection of recipe templates is aligned with the specific parameters, types of network elements in the configuration process. The accessing involves retrieving data from a repository or database. It means obtaining the relevant recipe templates from the central repository to generate the configuration recipe.

[0068] The system [200] further comprises an alerting unit [206] that is configured to generate an alert if none of the recipe templates matches with the at least one network element and the set of parameters to be modified. The alerting unit [206] is configured to generate an alert if the generated configuration recipe fails to validate. The present disclosure encompasses that the alerting unit [206] monitors the configuration process and issues notifications when specific conditions are met. The generating alert involves creating a notification or warning if certain conditions are met, such as when no matching recipe template is found or if the generated configuration recipe fails validation. If none of the available recipe templates match the requirements of the network element and the parameters to be modified, the alerting unit generates an alert.

[0069] In an example, the alert may be in the form of a message, email, or dashboard notification. Similarly, if the configuration recipe generated fails to validate, indicating inaccuracies or compatibility issues, another alert is triggered.

[0070] The system [200] further provides user empowerment and flexibility in managing command recipes. Users can download any configuration command recipe from the central database to their local device. This feature can be used to back up important command recipes, share recipes with other teams or systems, or for further analysis or modification using local tools. Users have the ability to modify existing command recipes. This might involve altering commands, adjusting parameters, or changing sequences of operations based on new requirements or insights. This feature allows for customizability and flexibility in managing network configurations. Users can remove command recipes from the central database. This function can be used to clear out obsolete or redundant recipes, ensuring that the database remains relevant and manageable. Users can mark any command recipe as the default recipe. This feature could be used to establish a baseline configuration for a given network element type, software version, or vendor. If a specific command recipe for a certain situation doesn't exist, the system can fall back to this default recipe. By providing this interactive interface, the system [200] ensures that users can easily and effectively manage their configuration command recipes. Whether it's making small adjustments to adapt to changing network conditions, or performing large-scale recipe management, this user interface makes these tasks efficient and straightforward. [0071] Referring to FIG. 3 an exemplary method flow diagram [300] for automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200], Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302],

[0072] In an example, parameter configuration refers to the process of setting and adjusting various operational parameters within network elements. These parameters could include IP addresses, routing protocols, bandwidth allocations, and security settings.

[0073] In an example, the multivendor network element is a network device or component (such as a router, switch, or firewall) manufactured by different vendors.

[0074] At step 304, the method comprises, selecting, by a selecting unit [201], at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. In an implementation, the system [200] may comprise a recipe builder from which the vendor may be selected from a list of vendors at an interface of the recipe builder which displays the list. The recipe builder may maintain the list of vendors for configuration.

[0075] In an example, the network environment encompasses the entire infrastructure of interconnected devices, systems, and components that facilitate communication and data transfer. This includes hardware, software, protocols, and standards used in the network. The sizes may range from small, simple devices to large, complex systems. The complexity levels denote the degree of complexity in terms of configuration, capabilities, and functionalities.

[0076] The present disclosure encompasses the selecting unit [201] is responsible for choosing at least one vendor from multiple vendors present in a network environment. This environment consists of numerous network elements, which vary in size and complexity and come from various vendors. The network elements could include devices like routers, switches, firewalls, etc., that perform various network functions. The selecting a vendor from a plurality of vendors in a network process could involve assessing the type of network elements from each vendor present in the network, their functionalities, and their compatibility with the automated system. The selection could be determined based on the needs of the network, such as optimizing performance, managing resources, or improving security.

[0077] At step 306, the method [300] comprises, generating, by a generating unit [202] , a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs. The present disclosure encompasses the generating unit [202] generates the configuration recipe which is set of instructions used to modify the parameters of a network element. The selection process involves choosing configuration templates based on the characteristics of the network element and the parameters to be modified. In an implementation, the recipe builder may perform the parameter configurations of network elements. Further, the recipe builder can store various configuration recipes which can be applied whenever an operator/user chooses to at a click of a button. A configuration recipe may include commands to change any parameter across any version of any network element type of any vendor. Additionally, a configuration recipe may provide an option to replicate a complete set of commands for all or most parameters associated with a vendor specific network element type across different software versions.

[0078] In an example, the modifying involves altering the existing parameter settings of a network element. This could include updating software versions, changing security settings, or adjusting performance parameters.

[0079] These recipes are essentially pre-configured scripts that include all the necessary commands to modify a specific parameter in a network element. This process could involve network engineers or system administrators creating these recipes manually, uploading them from an external source like a text file or an Excel sheet, or automatically generating them using parsing rules, which analyses the network element and its configurations to create the required commands. These templates can be customized based on specific user inputs to meet particular configuration needs.

[0080] The set of parameters are the values that define how a network element operates. Parameters can include things like IP addresses, routing protocols, or security settings associated with the at least one network element. The central repository database is a centralized storage location where all the recipe templates are kept. These templates are chosen based on their compatibility with the network element and can be customized through user inputs wherein generating the configuration recipe comprises at least one of manual input, bulk data upload, and parsing rules derived from pre-existing configurations.

[0081] In an example, the user inputs refer to the data provided by the user to modify the configuration recipe to specific requirements. This may include specific parameter values and desired outcomes. In an implementation, the operator/user may customise a recipe template using the recipe builder by providing custom configurations for parameters to modify and map with related commands.

[0082] At step 308, the method [300] comprises, validating, by a validating unit [203], accuracy and compatibility of the set of instructions of the generated configuration recipe. The present disclosure encompasses the validating unit [203] to verify that the set of instructions in the configuration recipe is correct. To ensure that the created recipes are accurate, efficient, and compatible with the network elements. This might involve steps like syntax checking, which verifies the correctness of the commands; functional testing, which checks if the recipe achieves the desired result when applied to a network element; and compatibility testing, which ensures that the recipe works correctly with the network elements of the selected vendor.

[0083] At step 310, the method [300] comprises, automatically deploying, by a deploying unit [204], the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element. The present disclosure encompasses the deploying unit [204] is responsible for applying the validated configuration recipes to the network elements. The present disclosure encompasses the validated recipe refers to the configuration recipe that has been checked and confirmed by the validating unit [203] for accuracy and compatibility. The deployment is executed through the EMS, which is a centralized system used to manage and monitor network elements. The EMS facilitates the application of configuration changes across the network. The EMS provides tools for configuration, monitoring, and troubleshooting of network devices. The deployment involves applying the stored recipes to the network elements whenever needed. This could involve the system identifying the network elements that require configuration changes, selecting the appropriate recipes from the database, and then executing the commands on the network elements. This process could be automated, reducing the workload on the network operations team. [0084] The method [300] further comprises, wherein prior to the selection of the at least one recipe template from the set of recipe templates, the step of generating the configuration recipe further comprises accessing, by a processing unit [205], the central repository database that stores the set of recipe templates, wherein the set of set of recipe templates corresponds to the set of parameters, network element types, and software versions. In an example, the set of parameters include IP addresses, routing protocols, bandwidth allocations, security settings, QoS settings and VLAN IDs. The network elements, such as routers, switches, firewalls, access points, modems, servers, and network controllers, are included, each with varying sizes and complexity levels. The method ensures that recipe templates are defined to include different software versions, including operating system versions, firmware versions, application software versions, and protocol support versions. The present disclosure encompasses the processing unit [205] is responsible for handling data operations before selecting the appropriate recipe template. This processing unit [205] is central in accessing the central repository database where all recipe templates are stored. By accessing this database, the processing unit [205] ensures that the selection of recipe templates is aligned with the specific parameters, types of network elements in the configuration process. The accessing involves retrieving data from a repository or database. It means obtaining the relevant recipe templates from the central repository to generate the configuration recipe.

[0085] The method [300] comprises generating, by an alerting unit [206], an alert if none of the recipe templates matches with the at least one network element and the set of parameters to be modified, wherein the method comprises generating, by an alerting unit [206], an alert if the generated configuration recipe fails to validate, wherein the method comprises storing, by a storage unit [207], the generated recipe in the central repository database. The present disclosure encompasses the altering unit [206] monitoring the configuration process and issuing notifications when specific conditions are met. The generating alert involves creating a notification or warning if certain conditions are met, such as when no matching recipe template is found or if the generated configuration recipe fails validation. If none of the available recipe templates match the requirements of the network element and the parameters to be modified, the alerting unit [206] generates an alert. Similarly, if the configuration recipe generated fails validation, indicating inaccuracies or compatibility issues, another alert is triggered. Additionally, the system includes a storage unit [207], which is responsible for archiving the generated recipes in the central repository database.

[0086] Thereafter, the method terminates at step ([312]). [0087] Referring to FIG. 4 that illustrates an exemplary system architecture [400] indicating the process for automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary embodiments of the present disclosure.

[0088] The components of the system architecture [400] as shown in FIG. 4 are illustrated below:

[0089] Load Balancer (Shared LB) [410]: The load balancer distributes incoming network traffic across multiple servers to ensure no single server becomes overwhelmed, which improves response times and system reliability. It acts as an entry point to the system [400] to manage traffic before it reaches the Web Servers [411],

[0090] Web Servers [411]: These handle HTTP requests from clients, serving web pages and web applications, which is linked to the Shared LB, which routes incoming traffic to them.

[0091] API Gateway Server [412]: This acts as an entry point for all client requests that access the backend services. It handles request routing, composition, and protocol translation which lie between the Web Servers [411] and the App Servers [413], ensuring secure and streamlined API requests.

[0092] App Servers [413]: The App Servers [413] host the business logic and handle application operations. They process requests received from the API Gateway Server which connect to the Oracle Database [403] for data storage, retrieval, and management.

[0093] Oracle Database [403]: A relational database management system used for storing and managing large volumes of structured data which is centralized data storage that is accessed by the App Servers [413] for processing client requests.

[0094] Schedulers [404]: The Schedulers [404] manage scheduled tasks and background jobs within the system, such as periodic data processing or maintenance tasks which is directly interacts with the Oracle Database [403] and the application servers to execute scheduled tasks.

[0095] Superset Dashboard [405]: A data visualization tool that provides insights and analytics on system performance and data trends that pulls data from the Oracle Database [403] for generating real-time reports and visualizations. [0096] RAN Core [409]: This consists of multiple microservices (MSI, MS2, MS3). This is the core network component responsible for processing requests and sending responses back to the initial requestor. It receives requests from the Schedulers [404] and sends responses back through the same channel.

[0097] Further, with reference to the system architecture [400], client requests are routed through the Shared LB to one of the Web Servers [411], The Web Servers [411] forward these requests to the API Gateway Server [412], The API Gateway Server [412] directs the requests to the appropriate App Servers [413], The App Servers [413] query or update the Oracle Database [403] as needed. Schedulers [404] manage any background tasks or scheduled jobs that may involve further database interaction or application processing. The data required for analytics is fetched by the Superset Dashboard [405] from the Oracle Database [403], The requests that require processing by the RAN Core [409] are sent, and responses are handled accordingly.

[0098] Firewalls [402]: These ensure secure data flow and prevent unauthorized access between different system components.

[0099] The system architecture [400] provides load balancing, where Shared LB and multiple servers ensure high availability and fault tolerance.

[0100] The system architecture [400] provides a modular design, which allows for scalability and easy maintenance of individual components without affecting the entire system.

[0101] Referring to FIG. 5 that illustrates an exemplary flow diagram [500] indicating the process automated management of parameter configurations across multi-vendor network elements, in accordance with exemplary embodiments of the present disclosure. The various blocks as shown in the flow diagram [500] and the process flow between the blocks is further explained below:

[0102] Manual Input [501]: This refers to the manual creation of command recipes by the user. The user would input each command, step by step, into the system. This method would be particularly useful for creating custom recipes for unique or specific tasks that are not covered by existing recipes. The user would have full control over the process, allowing them to customize the recipe to their precise needs. [0103] Bulk Upload [502]: In cases where a large number of command recipes need to be created, manual input can become time-consuming and tedious. Therefore, the system also allows for bulk upload. The user can create a file containing multiple command recipes and upload it to the system. This can be done using various file formats such as CSV, Excel, or XML [519], Once uploaded, the system processes the file and adds the contained recipes to its database [505],

[0104] Parsing Rules [503]: The automated method of creating command recipes involves parsing rules [503], These rules are designed to automatically generate command recipes based on predefined conditions or parameters. The parsing rules read and interpret the data and create the appropriate command sequences based on that interpretation. This method can create large numbers of recipes quickly and accurately, reducing the workload on the user and minimizing the risk of human error.

[0105] The process begins with the selection of a vendor [506], The Recipe Builder [507] can handle both manual [501], bulk upload [502] and parsing rules [503] based methods for creating recipes.

[0106] In the Manual Method [501], there are two branches based on an existing recipe [508] and for a new recipe [509], When a search for an existing recipe [510] in the database is performed, if recipe is not found, then error notification will be shown to the user that recipe is not found [512] else if found, then recipe and their commands can be added [514], When user choses to submit, then based on the details [515] of recipe, it will be verified and based on the correctness the recipe is created at [516] and then ingested with its associated commands [504] in the database [505], If the verification fails, error message is prompted at [530], A new recipe [509] can be created either by entering all the details [511] manually or through uploading a file containing the recipe details. After validation of recipe [517] is completed then it is ingested into the oracle database [505], If the details entered are not correct, then a message is displayed to the user to enter correct details [518],

[0107] In Bulk Upload Method [502], user can add entries by uploading [519] files which can be uploaded from upload section screen. Once the template is uploaded and validated [520], then the user will get notification about successful upload [521], Internally all the validation [520] will happen and if anything is wrong or missing then write status is set to fail [529] with remark in same uploaded sheet. If record is correct, then recipe and commands ingested [524] in database and write status is set to pass for the uploaded template. Write status sheet is updated on shared location and mail is sent to respective stack holder with attachment of status sheet [525], If data validation is successful, the data is ingested into the database [505], and status is updated on shared drive [526],

[0108] Parsing Rules [503]: User can create recipe in bulk through parsing rules [527], To execute it, user needs to choose node type & software version for which user wants to create the recipe. Once the user clicks on submit then parsing rule entry is added in the database [505], Scheduler will create recipe & commands through parsing rules [528] defined by front end parser and ingest the same in oracle database [505],

[0109] On recipe listing page, there are options a user can use: user can download recipe and their command details; user can edit existing recipe details. When user clicks on send to micro service then final verification of recipe will happen and that created recipe can be used by other modules. The other option is to delete existing recipe from system. The user can also mark any recipe as default which can be used if recipe of required version does not exist in system.

[0110] Ingest Recipe & Commands [504]: Data is ingested into the Oracle database [505] and the status of the data ingestion is marked as 'pass' in the uploaded sheet [524],

[OHl] Notifications and Storage: An email with the status and any necessary attachments is sent to the relevant stakeholders [525], The Excel file is stored on a shared drive [526] for future reference.

[0112] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for automated management of parameter configurations across multivendor network elements, the instructions include executable code which, when executed by one or more units of a system, causes: a selecting unit [201] of the system to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels. Further, the instructions include executable code which, when executed by one or more units of a system, causes a generating unit [202] of the system to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs; a validating unit [203] of the system to validate accuracy and compatibility of the set of instructions of the generated recipe. Further, the instructions include executable code which, when executed by one or more units of a system, causes a deploying unit [204] of the system to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

[0113] As is evident from the above, the present disclosure provides a technically advanced solution for automated management of parameter configurations across multi-vendor network elements. The present solution introduces an automated system for managing parameter configurations across multi-vendor network elements, significantly improving upon traditional manual methods. This system automates the configuration process, reducing the time and effort required to modify thousands of parameters in large networks. It addresses the complexities associated with multi-vendor environments by providing a centralized repository for storing and managing parameter change commands specific to each vendor.

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

[0115] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

WE CLAIM:

1. A method [300] for automated management of parameter configurations across multi-vendor network elements, the method comprising the steps of: selecting, by a selecting unit [201], at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels; generating, by a generating unit [202], a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs;

- validating, by a validating unit [203], accuracy and compatibility of the set of instructions of the generated configuration recipe; and automatically deploying, by a deploying unit [204], the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

2. The method [300] as claimed in claim 1, wherein generating the configuration recipe comprises at least one of manual input, bulk data upload, and parsing rules derived from preexisting configurations.

3. The method [300] as claimed in claim 1, wherein prior to the selection of the at least one recipe template from the set of recipe templates, the step of generating the configuration recipe further comprises: accessing, by a processing unit [205], the central repository database that stores the set of recipe templates, wherein the set of set of recipe templates corresponds to the set of parameters, network element types, and software versions.

4. The method [300] as claimed in claim 1, wherein the method comprises generating, by an alerting unit [206], an alert if none of the recipe templates matches with the at least one network element and the set of parameters to be modified.

5. The method [300] as claimed in claim 1, wherein the method comprises generating, by an alerting unit [206], an alert if the generated configuration recipe fails to validate.

6. The method [300] as claimed in claim 1, wherein the method comprises storing, by a storage unit [207], the generated recipe in the central repository database.

7. A system [200] for automated management of parameter configurations across multi-vendor network elements, the system comprises: a selecting unit [201] configured to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels; a generating unit [202] connected to at least the selecting unit [201], wherein the generating unit [202] configured to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs; a validating unit [203] connected to at least the generating unit [202], wherein the validating unit [203] configured to validate accuracy and compatibility of the set of instructions of the generated recipe; and a deploying unit [204] connected to at least the validating unit [203], wherein the deploying unit [204] configured to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

8. The system [200] as claimed in claim 7, wherein generating the configuration recipe comprises at least one of manual input, bulk data upload, and parsing rules derived from preexisting configurations.

9. The system [200] as claimed in claim 7, wherein the system comprises a processing unit [205], wherein prior to the selection of the at least one recipe template from the set of recipe templates, the processing unit is configured to access the central repository database that stores the set of recipe templates, wherein the set of set of recipe templates corresponds to the set of parameters, network element types, and software versions.

10. The system [200] as claimed in claim 7, wherein the system comprises an alerting unit [206] is configured to generate an alert if none of the recipe templates matches with the at least one network element and the set of parameters to be modified.

11. The system [200] as claimed in claim 7, wherein the system comprises an alerting unit [206] configured to generate an alert if the generated configuration recipe fails to validate.

12. The system [200] as claimed in claim 7, wherein the system comprises a storage unit [207] configured to store the generated recipe in the central repository database.

13. A user equipment for automated management of parameter configurations across multivendor network elements, the user equipment comprising a system [200], the system [200] further comprising: a selecting unit [201] configured to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels; a generating unit [202] configured to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs; a validating unit [203] configured to validate accuracy and compatibility of the set of instructions of the generated recipe; and a deploying unit [204] configured to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.

14. A non-transitory computer readable storage medium storing instruction for automated management of parameter configurations across multi-vendor network elements, the instructions include executable code which, when executed by one or more units of a system [200] causes: a selecting unit [201] to select at least one vendor from a plurality of vendors in a network environment, wherein the at least one vendor corresponds to at least one network element of a plurality of network elements, and wherein the plurality of network elements comprises network elements of one or more sizes and one or more complexity levels; a generating unit [202] to generate a configuration recipe for modifying a set of parameters associated with the at least one network element, wherein the configuration recipe comprises a set of instructions corresponding to the at least one network element, based on a selection of at least one recipe template from a set of recipe templates stored in a central repository database that matches the at least one network element and the set of parameters to be modified, wherein the recipe templates in the set of recipe templates are customizable based on user inputs; a validating unit [203] to validate accuracy and compatibility of the set of instructions of the generated recipe; and a deploying unit [204] to automatically deploy the validated recipe to the at least one network element, wherein the automatic deployment is performed on an element management system (EMS) of the at least one network element.