FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR AUTOMATICALLY PARSING
CONFIGURATIONS”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR AUTOMATICALLY PARSING
CONFIGURATIONS
5 FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for automatically parsing configurations. 10
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include 15 certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
20 [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
25 services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being
30 deployed, promising even faster data speeds, low latency, and the ability to connect
2

multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
5 [0004] Network management applications need to determine the configuration of a network, and then present the configuration to a user or to another process or application. Parsing systems provide the capability to manage the parameter dictionary and configuration database of network elements across the multiple vendors and software packages. These systems provide for enabling or disabling 10 the parsing of any parameter and can define the logic to parse the configuration of network elements.
[0005] For the existing systems there is no automated technique available to read/parse the configuration of nodes in the network. As the network can hold the
15 configuration of multiple software packages at a time, it becomes a very hectic task to do it manually. Also, there are multiple vendors available in the market which have different configuration format and syntax. Hence, to do the parsing manually becomes very difficult for the large number of different vendors with many different software packages at the same time. Further, since the technology is changing or
20 evolving very fast, many new parameters get added or configured in the network on almost a daily or weekly basis. Therefore, to find out what new parameters have been added and their respective current value in the network becomes another challenge to telecom companies. This is currently happening through manually exchanging of the files with respective team/clients. And this takes time to realize
25 which causes delay in optimization of network during that period of time.
[0006] Thus, there exists an imperative need in the art to provide a method and a system for automatically parsing configurations.
3

OBJECTS OF THE INVENTION
[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. 5
[0008] It is an object of the present disclosure to provide a system and a method to automatically parsing configurations parameter dictionary and configuration database of network elements across multiple vendors.
10 [0009] It is yet another object of the present disclosure to provide a solution that can assist in dynamically enabling or disabling the parsing of any parameter and can define the new logic to parse.
[0010] It is yet another object of the present disclosure to provide a solution that 15 can parse the network configuration automatically for any node type.
[0011] It is yet another object of the present disclosure to provide a solution in which a new software release can be auto detected, and configuration can be parsed automatically. 20
[0012] It is yet another object of the present disclosure to provide a solution in which a user can configure parsing rule/logic to read any specific parameter of any particular software package.
25 [0013] It is yet another object of the present disclosure to provide a solution in which a user has flexibility to define default parsing rule for any new software package for no definition available.
[0014] It is yet another object of the present disclosure to provide a solution in 30 which the user has flexibility to enable/disable the parsing of any parameter or Software package.
4

[0015] It is yet another object of the present disclosure to provide a solution in which the identifiers of the parameters can be separately configured.
5 [0016] It is yet another object of the present disclosure to provide a solution which provides a feature of generating email notifications if any new software package have been configured.
[0017] It is yet another object of the present disclosure to provide a solution in 10 which users have multiple options to define parsing rule, either select the parameters and their parsing logic manually or can be done through bulk upload which holds multiple parameters and respective parsing rules in single sheet.
[0018] It is yet another object of the present disclosure to provide a solution in 15 which users can download any release data and their history.
[0019] It is yet another object of the present disclosure to provide a solution in which is able to search any configuration details.
20 SUMMARY
[0020] 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 25 subject matter.
[0021] An aspect of the present disclosure relates to a method for automatically
parsing configurations. The method includes receiving, by a transceiver unit, a
selection of one or more vendors. The method further includes receiving, by the
30 transceiver unit, a selection of at least one of one or more identifiers, one or more
5

parameters, and one or more command options. The method further includes creating, by a package creator unit, a node type, and a software package. The method further includes receiving, by the transceiver unit, a selection related to a package upload type functionality, and a selection related to a parsing control value 5 associated with the one or more parameters. The method further includes implementing, by a configuration manager, the selected package upload type functionality. The method further includes running, by a scheduling unit, a job scheduler to trigger a parser job, wherein the job scheduler is run in an event a set of parsing rules exist. Thereafter, the method includes parsing, by a parsing unit, a 10 node-configuration data based on the set of parsing rules.
[0022] In an aspect, post the creating, by the package creator unit, a software package, the method comprises: generating, by the package creator unit, one of: a success notification indicating a successful creation of the software package, and 15 an error notification indicating a prior existence of the software package.
[0023] In an aspect, the package upload type functionality is one of a bulk upload functionality and a manual upload functionality.
20 [0024] In an aspect, the manual upload functionality procedure comprises: adding a set of details, the set of details comprising the one or more identifiers, the one or more parameters, and the one or more command options; submitting a request based on the addition of details; performing a first validation based on the added details; generating one of a successful first validation notification, and an error first
25 validation notification, wherein the successful first validation notification is generated in an event the added details are correct, and the unsuccessful first validation notification is generated in an event the added details are incorrect; creating the set of parsing rules in an event the successful first validation notification is generated; and storing the set of parsing rules in a database in a
30 storage unit.
6

[0025] In an aspect, the bulk upload functionality procedure comprises: adding a set of configuration details based on a predefined upload template; uploading the set of configurations details, generating a notification wherein the notification is 5 one of a successful upload completion notification, and an unsuccessful upload completion notification; performing a second validation based on the set of configuration details and the successful upload completion notification; marking, one of: a success second validation status and a failure second validation status, wherein the success second validation status is marked in an event the set of
10 configuration details are correct, and the failure second validation status is marked in an event the set of configuration details are incorrect; mapping the identifiers with the one or more parameters, and the one or more command options based on the success second validation status; and creating the set of parsing rules in an event of generation of the success second validation status.
15
[0026] In an aspect, the method further comprising storing, in a database at the storage unit, a parsed data based on the parsing of the node-configuration data.
[0027] In an aspect, the selection related to the parsing control value associated 20 with the one or more parameters comprises a selection for one of enabling and disabling the parsing of the one or more parameters.
[0028] In an aspect, the method further comprising receiving, at the transceiver unit, a request for replication, the request comprising a data indicating the created 25 software package; and replicating, by the package creator unit, a new software package based on the received request and the created software package.
[0029] In an aspect, the method further comprising: receiving, at the transceiver
unit, a request for modifying a status of the created software package, wherein the
30 request is one of an enable package request and a disable package request; and
7

performing, by the configuration manager, a status modification action on the created software package, wherein an enable action is performed in an event the enable package request is received, and a disable action is performed in an event the disable package request is received. 5
[0030] In an aspect, the method further comprising receiving, at the transceiver unit, a request for deleting the created software package; and deleting, by the configuration manager, the created software package.
10 [0031] Another aspect of the present disclosure provides a system for automatically parsing configurations. The system includes a transceiver unit configured to receive a selection of one or more vendors; receive a selection of at least one of one or more identifiers, one or more parameters, and one or more command options. The system further includes a package creator unit connected to at least the transceiver unit,
15 wherein the package creator unit is configured to create a node type and a software package. The transceiver unit is further configured to receive a selection related to a package upload type functionality, and a selection related to a parsing control value associated with the one or more parameters. The system further includes a configuration manager connected to at least the package creator unit, wherein the
20 configuration manager is configured to implement the selected package upload type functionality. The system further includes a scheduling unit connected to at least the configuration manager, wherein the scheduling unit is configured to run a job scheduler to trigger a parser job file, wherein the job scheduler is run in an event a set of parsing rules exist. The system further includes a parsing unit connected to at
25 least the scheduling unit, wherein the parsing unit is configured to parse a node-configuration data based on the set of parsing rules.
[0032] An aspect of the present disclosure provides a non-transitory computer-readable storage medium storing instruction for automatically parsing 30 configurations, the storage medium comprising executable code which, when
8

executed by one or more units of a system, causes: a transceiver unit to: receive a selection of one or more vendors; receive a selection of at least one of one or more identifiers, one or more parameters, and one or more command options; a package creator unit connected to at least the transceiver unit, wherein the package creator 5 unit to create a node type and a software package; wherein the transceiver unit is further configured to receive a selection related to a package upload type functionality, and a selection related to a parsing control value associated with the one or more parameters; a configuration manager connected to at least the package creator unit, wherein the configuration manager to implement the selected package
10 upload type functionality; a scheduling unit connected to at least the configuration manager, wherein the scheduling unit to run a job scheduler to trigger a parser job file, wherein the job scheduler is run in an event a set of parsing rules exist; and a parsing unit connected to at least the scheduling unit, wherein the parsing unit to parse a node-configuration data based on the set of parsing rules.
15
BRIEF DESCRIPTION OF DRAWINGS
[0033] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
20 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated
25 by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
9

[0034] FIG. 1 illustrates an exemplary block diagram of a front end parser module for implementation of a system for automatically parsing configurations, in accordance with exemplary embodiments of the present disclosure.
5 [0035] FIG. 2 illustrates an exemplary block diagram of a system for automatically parsing configurations, in accordance with exemplary embodiments of the present disclosure.
[0036] FIG. 3 illustrates an exemplary method flow diagram indicating the process 10 for automatically parsing configurations, in accordance with exemplary embodiments of the present disclosure.
[0037] FIGs. 4A & 4B illustrate an exemplary implementation of the process for automatically parsing configurations, in accordance with exemplary embodiments 15 of the present disclosure.
[0038] FIG. 5 illustrates an exemplary block diagram of a computing device upon which an embodiment of the present disclosure may be implemented.
20 [0039] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DESCRIPTION
25 [0040] 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 can each be used independently of one
30 another or with any combination of other features. An individual feature may not
10

address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in 5 which like reference numerals refer to the same parts throughout the different drawings.
[0041] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
10 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.
15
[0042] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or
20 limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
25
[0043] 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, networks, processes, and other
30 components may be shown as components in block diagram form in order not to
11

obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
5 [0044] 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 can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process 10 is terminated when its operations are completed but could have additional steps not included in a figure.
[0045] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the
15 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
20 “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.
25 [0046] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the
30 other user devices. The user equipment may have a processor, a display, a memory,
12

a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For 5 instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
10
[0047] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a
15 plurality of microprocessors, one or more microprocessors in association with a 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
20 the present disclosure. More specifically, the processor is a hardware processor.
[0048] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of
25 technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
30
13

[0049] Radio Access Technology (RAT) refers to the technology used by mobile
devices/ user equipment (UE) to connect to a cellular network. It refers to the
specific protocol and standards that govern the way devices communicate with base
stations, which are responsible for providing the wireless connection. Further, each
5 RAT has its own set of protocols and standards for communication, which define
the frequency bands, modulation techniques, and other parameters used for
transmitting and receiving data. Examples of RATs include GSM (Global System
for Mobile Communications), CDMA (Code Division Multiple Access), UMTS
(Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
10 and 5G. The choice of RAT depends on a variety of factors, including the network
infrastructure, the available spectrum, and the mobile device's/device's capabilities.
Mobile devices often support multiple RATs, allowing them to connect to different
types of networks and provide optimal performance based on the available network
resources.
15
[0050] As used herein, a job file is an XML file that defines the data collection and
processing. The job includes the retrieval of the configuration data.
[0051] As used herein, parser job file refers to applying the parsing rules to 20 interpret, organize, or reformat the job file data as per the system's operational requirements.
[0052] As used herein, node configuration data refers to the data that allows the user to customize and optimize the settings for individual nodes in cluster based on 25 the set of parsing rules.
[0053] As discussed in the background section, For the existing systems there is no automated technique available to read/parse the configuration of nodes in the network. As the network can hold the configuration of multiple software packages 30 at a time, it becomes a very hectic task to do it manually. Also, there are multiple vendors available in the market which have different configuration format and
14

syntax. Hence, to do the parsing manually becomes very difficult for the large number of different vendors with many different software packages at the same time. Further, since the technology is changing or evolving very fast, many new parameters get added or configured in the network on almost a daily or weekly 5 basis. Therefore, to find out what new parameters have been added and their respective current value in the network becomes another challenge to telecom companies. This is currently happening through manually exchanging of the files with respective team/clients. And this takes time to realize which causes delay in optimization of network during that period of time.
10
[0054] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing an automated and efficient system for parsing and managing network configurations across multiple vendors and software packages. The proposed solution introduces a front-end parser
15 that automates the management of a parameter dictionary and configuration databases, thereby eliminating the need for manual intervention. This automation significantly reduces the workload and potential errors associated with manual parsing of configurations, particularly when dealing with multiple vendors who use different formats and syntaxes. Moreover, the invention enables the dynamic
20 addition, modification, and management of parsing rules and configurations, allowing network operators to quickly adapt to technological changes and newly introduced parameters in the network. This feature is especially crucial given the rapid pace of technological advancements in telecommunications. The system's capability to automatically detect new software releases and parse configurations
25 accordingly minimizes delays in network optimization that occur due to the manual exchange of configuration files and information between teams or clients. Additionally, the proposed solution offers enhanced flexibility through features that allow users to manually define parsing rules or upload them in bulk via predefined templates. This flexibility ensures that the system can accommodate a wide range
30 of user preferences and operational scenarios, further streamlining the configuration
15

management process. The combination of these functionalities within the system not only addresses the inefficiencies found in previous methods but also enhances overall network management and responsiveness, leading to improved service delivery and network performance. 5
[0055] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0056] Referring to FIG. 1, an exemplary block diagram of a front end parser 10 module [100] for implementation of a system for automatically parsing configurations is shown, in accordance with exemplary embodiments of the present disclosure. The front end parser module [100] comprises a user interface [102], a database [104], a load balancer module [106], a web server [108], an application server [110], a reporting server [112], a gateway server [114], and a job module 15 [116].
[0057] At the user interface [102], users can interact with the system, making selections and inputs that initiate the configuration management process. The actions are then processed by the application server [110], for the application logic,
20 handling the creation, updating, and deletion of software packages and node types. The load balancer module [106] ensures that the system's workload is distributed evenly across multiple servers to optimize resource utilization and response time. The load balancer module [106] directs traffic to the web server [108], which is responsible for serving the user interface [102] and facilitating the user's
25 interactions with the system. The web server [108] interacts with the database [104], which stores all the parsed configuration data, as well as the parsing rules created by the users. This is where all the node-configuration data is ingested after being processed. Reporting server [112] generate reports on the configuration data and parsing activities, providing insights and analytics for system monitoring and
30 decision-making. The gateway server [114] acts as a mediator for different network
16

requests and facilitate in interfacing with external systems or APIs, for interactions such as authentication and security measures. The job module [116] manages scheduled tasks, such as triggering parsing jobs as per the parsing rules defined in the system. The jobs could involve parsing the node-configuration data based on 5 new or updated rules.
[0058] FIG. 2 illustrates an exemplary block diagram of a system [200] for automatically parsing configurations, in accordance with exemplary embodiments of the present disclosure. As shown in FIG. 2, the system [200] comprises a
10 Transceiver Unit [202], a Package Creator Unit [204], a Configuration Manager [206], a Scheduling Unit [208], a Parsing Unit [210], and a Storage Unit [212] wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. Also, in FIG. 2 only a few units are shown, however, the system [200]
15 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.
[0059] The system [200] for automatically parsing configurations comprises a 20 transceiver unit [202] configured to receive a selection of one or more vendors. The system [200] interfaces with various network elements provided by different manufacturers. Through a user interface, which may be integrated with the transceiver unit [202], users can select from a range of vendors whose network configurations they wish to manage. The selection may notify the system of the 25 specific vendors' configuration syntax and format that will need to be parsed, ensuring compatibility and enabling the system to handle the diverse configurations across the multi-vendor network landscape.
[0060] The system [200] for automatically parsing configurations comprises a 30 transceiver unit [202] configured to receive a selection of one or more vendors .
17

Through the user interface, which is likely integrated with the transceiver unit [202], users can select from a range of vendors whose network configurations they wish to manage. This selection informs the system of the specific vendors' configuration syntax and format that will need to be parsed, ensuring compatibility 5 and enabling the system to handle the diverse configurations across the multi-vendor network landscape.
[0061] The transceiver unit [202] is further configured to receive a selection of at least one of one or more identifiers, one or more parameters, and one or more
10 command options. Identifiers may include unique references for network elements, such as IP addresses or node names or service access point (SAP) identifier. Parameters could be specific settings within the network elements that dictate their operation, such as port numbers, protocol types, or bandwidth limits. Command options may refer to the particular commands used to navigate the configurations,
15 extract necessary data, or apply changes. By allowing selections among these categories, the transceiver unit [202] can handle a wide range of configuration tasks tailored to the network's requirements. The system [200] can thus effectively parse relevant data, whether it is to interpret the current configuration state, apply new configurations, or update existing ones.
20
[0062] The package creator unit [204] is connected to at least the transceiver unit [202]. The package creator unit [204] is configured to create a node type and a software package. The package creator unit [204] enables the definition and establishment of the various network elements that are to be managed. The package
25 creator unit [204] translates the selections received from the transceiver unit [202] regarding vendors, identifiers, parameters, and command options into actionable configurations within the system’s database. Upon creation of a new node type or software package, the package creator unit [204] can generate notifications to inform the user of the successful addition or potential conflicts, such as duplications
30 with existing entries. The package creator unit [204] thus facilitates in maintaining
18

an up-to-date and accurate network configuration repository, which is essential for the efficient and automated parsing and managing of network configurations across the different vendors and software packages integrated into the system.
5 [0063] After completing the process of creating the software package, the package creator unit [204] generates a notification about the outcome of the creation process. If the software package creation is successful, the package creator unit [204] produces a success notification. The success notification confirms to the user or system administrator that the new software package has been properly set up within
10 the system. Conversely, if there is an issue such as the software package already existing within the system, the package creator unit [204] issues an error notification. The error notification alerts the user or system administrator to the fact that the intended new software package was not created because a package with the same designation is already present in the system's database. The feedback
15 mechanism ensures clarity and avoids confusion in the system's operation, maintaining the integrity of the software package inventory.
[0064] The transceiver unit [202] is further configured to receive a selection related to a package upload type functionality, and a selection related to a parsing control
20 value associated with the one or more parameters. The selection related to the parsing control value associated with the one or more parameters comprises a selection for one of enabling and disabling the parsing of the one or more parameters. The transceiver unit [202] is configured to handle different methods of uploading configuration data into the system [200], whether it is via a bulk upload
25 functionality, where the one or more parameters can be inputted simultaneously, or via a manual upload functionality, where the one or more parameters are entered individually. Additionally, the transceiver unit [202] is equipped to manage control values that determine the parsing behaviour for the parameters in question. Control values may include enabling or disabling the parsing functionality for specific
19

parameters, which provides users with the flexibility to dictate how the system processes different sets of configuration data.
[0065] The manual upload functionality procedure comprises adding a set of details 5 that encompass one or more identifiers, parameters, and command options related to the network elements. Once these details are entered, the user submits a request for the system to process this information. Following the submission, the system performs a first validation to verify the correctness of the entered details. If the details are confirmed to be accurate and meet the system’s criteria, a successful first
10 validation notification is generated, signifying the validity of the information provided. Conversely, if there are errors or discrepancies found in the details, an error first validation notification is produced, alerting the user to the issues that need resolution. Upon generating a successful first validation notification, the system proceeds to create a set of parsing rules. The set of parsing rules are derived from
15 the validated details and are configured for the specific requirements of the network configuration data being processed. Finally, the newly created set of parsing rules is stored in a database within the storage unit [212].
[0066] The bulk upload functionality procedure comprises several steps to
20 efficiently handle and validate a large volume of configuration data. Initially, it
involves adding a set of configuration details based on a predefined upload
template. This template is designed to facilitate the orderly input of data, ensuring
that all necessary details such as identifiers, parameters, and command options are
correctly formatted and complete. Once the configuration details are added to the
25 template, the entire set is uploaded to the system. Following the upload, a
notification is generated to indicate the outcome. This notification can either be a
successful upload complete notification, confirming that the data has been
successfully received by the system, or an unsuccessful upload completion
notification, indicating that an issue occurred during the upload process. If the
30 upload is successful, the system performs a second validation to ensure that the
20

details in the uploaded data are correct and adhere to expected standards. Depending on the outcome of this validation, a success second validation status or a failure second validation status is marked. The success second validation status is assigned if all details are correct, while the failure second validation status is assigned if any 5 discrepancies or errors are found in the data. Following a successful second validation, the system proceeds to map the identifiers with their corresponding parameters and command options. Finally, upon successful mapping, a set of parsing rules is created. The rules are based on the successfully validated and mapped configuration details. The newly created parsing rules are then stored and 10 utilized for parsing and managing the network configurations as per the system's requirements. This bulk upload functionality significantly streamlines the process of handling large volumes of configuration data, enhancing efficiency and reducing the potential for errors.
15 [0067] The configuration manager [206] is connected to at least the package creator unit [204]. The configuration manager [206] is configured to implement the selected package upload type functionality. The configuration manager [206] executes the necessary processes based on whether a user has chosen to use the bulk upload functionality or manual upload functionality for entering configuration data.
20 This involves overseeing the actual application of the upload, ensuring that the data entered aligns with the system's expected formats and structures. Upon the successful upload of data, the configuration manager [206] may also be responsible for invoking other system processes that may include validation of the data, triggering parsing operations, or notifying users of the upload status. The
25 configuration manager [206] thus acts as an orchestrator for the configuration data handling, ensuring that the system's database is correctly updated with the new or altered configuration information.
[0068] The scheduling unit [208] is connected to at least the configuration manager 30 [206]. The scheduling unit [208] is configured to run a job scheduler to trigger a
21

parser job file, wherein the job scheduler is run in an event a set of parsing rules exist. The scheduling unit [208] is responsible for automating the process of configuration parsing by initiating pre-defined tasks at scheduled times or under specific conditions. When the configuration manager [206] confirms that a 5 complete set of parsing rules is available and correctly set up, the scheduling unit [208] proceeds to execute the parser job. The job includes the system retrieving the configuration data and applying the parsing rules to interpret, organize, or reformat the data as per the system's operational requirements. The automation provided by the scheduling unit [208] ensures that parsing operations are performed consistently 10 and without the need for manual intervention, leading to greater efficiency and reliability in the management of network configurations.
[0069] The parsing unit [210] is connected to at least the scheduling unit [208]. The parsing unit [210] is configured to parse node-configuration data based on the set
15 of parsing rules. Once the scheduling unit [208] triggers the parser job, the parsing unit [210] interprets and analyses the configuration data of network nodes using the set of parsing rules that have been defined. The set of parsing rules dictate how the configuration data should be read, understood, and potentially transformed into a standardized format suitable for storage, reporting, or further processing. The
20 parsing unit [210] operates by applying these rules to extract relevant information from the raw configuration data, ensuring that the data adheres to the expected structure and content needed by the system for effective network management.
[0070] The transceiver unit [202] is further configured to store, in a database at the 25 storage unit [212], a parsed data based on the parsing of the node-configuration data. After the parsing unit [210] processes the configuration data of network nodes according to the established parsing rules, the results, now in a parsed and potentially reformatted state, are securely saved. The storage of this parsed data in the database located at the storage unit [212] allows for reliable retrieval, 30 management, and analysis in future operations. It provides a consolidated
22

repository where the structured data can be accessed for monitoring, managing, and optimizing network performance, ensuring that the system maintains an accurate and up-to-date reflection of the network's configuration state.
5 [0071] The transceiver unit [202] is further configured to receive a request for replication, the request comprising data indicating the created software package. This feature allows users or automated systems to initiate the duplication of an existing software package configuration. Upon receiving such a request, the transceiver unit [202] processes and forwards it to the appropriate system
10 component for action. The package creator unit [204] is further configured to replicate a new software package based on the received request and the created software package. Once it receives the replication request from the transceiver unit [202], the package creator unit [204] uses the details of the existing software package to create a new, identical copy of it.
15
[0072] The transceiver unit [202] is configured to receive a request for modifying the status of the created software package, wherein the request is one of an enable package request and a disable package request. This capability allows system users or automated processes to dynamically manage the activation status of software
20 packages within the network. By sending a request to the transceiver unit [202], users can specify whether a particular software package should be activated (enabled) or deactivated (disabled), depending on the operational requirements or changes in the network configuration. The configuration manager [206] is configured to perform a status modification action on the created software package,
25 wherein an enable action is performed in an event the enable package request is received, and a disable action is performed in an event the disable package request is received. Upon receiving the command from the transceiver unit [202], the configuration manager [206] executes the specified action, either enabling or disabling the software package.
30
23

[0073] The transceiver unit [202] is further configured to receive a request for deleting the created software package. This feature allows users or system administrators to initiate the removal of an existing software package from the system. By sending a deletion request to the transceiver unit [202], it enables the 5 system to process these instructions and take the necessary actions to eliminate the specified package, thus maintaining the relevance and efficiency of the network configuration database. The configuration manager [206] is further configured to delete the created software package. Once it receives the deletion request from the transceiver unit [202], the configuration manager [206] proceeds with the actual 10 removal of the software package from the system's records thus preventing clutter and potential conflicts within the system by ensuring that only current and necessary software packages are retained.
[0074] Referring to FIG. 3 an exemplary method flow diagram [300], for 15 automatically parsing configurations in accordance with exemplary embodiments of the present invention is shown. In an implementation the method [300] is performed by the system [200]. As shown in FIG. 3, the method [300] starts at step [302].
20 [0075] At step [304], the method [300] as disclosed by the present disclosure comprises receiving, by a transceiver unit [202], a selection of one or more vendors. The transceiver unit [202] enables interfacing with various network elements provided by different manufacturers. Through the user interface, which is likely integrated with the transceiver unit [202], users can select from a range of vendors
25 whose network configurations they wish to manage. This selection informs the system of the specific vendors' configuration syntax and format that will need to be parsed, ensuring compatibility and enabling the system to handle the diverse configurations across the multi-vendor network landscape.
24

[0076] Next, at step [306], the method [300] as disclosed by the present disclosure comprises receiving, by the transceiver unit [202], a selection of at least one of one or more identifiers, one or more parameters, and one or more command options. The one or more identifiers may include unique references for network elements, 5 such as IP addresses or node names. Parameters could be specific settings within the network elements that dictate their operation, such as port numbers, protocol types, or bandwidth limits. Command options may refer to the particular commands used to navigate the configurations, extract necessary data, or apply changes. By allowing selections among these categories, the transceiver unit [202] can handle a 10 wide range of configuration tasks tailored to the network's requirements. The system [200] can thus effectively parse relevant data, whether it is to interpret the current configuration state, apply new configurations, or update existing ones.
[0077] Next, at step [308], the method [300] as disclosed by the present disclosure
15 comprises creating, by a package creator unit [204], a node type and a software
package. The package creator unit [204] enables the definition and establishment
of the various network elements that are to be managed. The package creator unit
[204] translates the selections received from the transceiver unit [202] regarding
vendors, identifiers, parameters, and command options into actionable
20 configurations within the system’s database. Upon creation of a new node type or
software package, the package creator unit [204] can generate notifications to
inform the user of the successful addition or potential conflicts, such as duplications
with existing entries. The package creator unit [204] thus facilitates in maintaining
an up-to-date and accurate network configuration repository, which is essential for
25 the efficient and automated parsing and managing of network configurations across
the different vendors and software packages integrated into the system.
[0078] After completing the process of creating the software package, the package
creator unit [204] generates a notification about the outcome of the creation process.
30 If the software package creation is successful, the package creator unit [204]
25

produces a success notification. The success notification confirms to the user or system administrator that the new software package has been properly set up within the system. Conversely, if there is an issue such as the software package already existing within the system, the package creator unit [204] issues an error 5 notification. The error notification alerts the user or system administrator to the fact that the intended new software package was not created because a package with the same designation is already present in the system's database. The feedback mechanism ensures clarity and avoids confusion in the system's operation, maintaining the integrity of the software package inventory.
10
[0079] Next, at step [310], the method [300] as disclosed by the present disclosure comprises receiving, by the transceiver unit [202], a selection related to a package upload type functionality, and a selection related to a parsing control value associated with the one or more parameters. The selection related to the parsing
15 control value associated with the one or more parameters comprises a selection for one of enabling and disabling the parsing of the one or more parameters. The transceiver unit [202] is configured to handle different methods of uploading configuration data into the system [200], whether it is via a bulk upload functionality, where the one or more parameters can be inputted simultaneously, or
20 via a manual upload functionality, where the one or more parameters are entered individually. Additionally, the transceiver unit [202] is equipped to manage control values that determine the parsing behaviour for the parameters in question. Control values may include enabling or disabling the parsing functionality for specific parameters, which provides users with the flexibility to dictate how the system
25 processes different sets of configuration data.
[0080] Next, at step [312], the method [300] as disclosed by the present disclosure
comprises implementing, by a configuration manager [206], the selected package
upload type functionality. The configuration manager [206] executes the necessary
30 processes based on whether a user has chosen to use the bulk upload functionality
26

or manual upload functionality for entering configuration data. This involves overseeing the actual application of the upload, ensuring that the data entered aligns with the system's expected formats and structures. Upon the successful upload of data, the configuration manager [206] may also be responsible for invoking other 5 system processes that may include validation of the data, triggering parsing operations, or notifying users of the upload status. The configuration manager [206] thus acts as an orchestrator for the configuration data handling, ensuring that the system's database is correctly updated with the new or altered configuration information.
10
[0081] Next, at step [314], the method [300] as disclosed by the present disclosure comprises running, by a scheduling unit [208], a job scheduler to trigger a parser job, wherein the job scheduler is run in an event a set of parsing rules exist. The scheduling unit [208] is responsible for automating the process of configuration
15 parsing by initiating pre-defined tasks at scheduled times or under specific conditions. When the configuration manager [206] confirms that a complete set of parsing rules is available and correctly set up, the scheduling unit [208] proceeds to execute the parser job. The job includes the system retrieving the configuration data and applying the parsing rules to interpret, organize, or reformat the data as per the
20 system's operational requirements. The automation provided by the scheduling unit [208] ensures that parsing operations are performed consistently and without the need for manual intervention, leading to greater efficiency and reliability in the management of network configurations.
25 [0082] Next, at step [316], the method [300] as disclosed by the present disclosure comprises parsing, by a parsing unit [210], a node-configuration data based on the set of parsing rules. Once the scheduling unit [208] triggers the parser job, the parsing unit [210] interprets and analyses the configuration data of network nodes using the set of parsing rules that have been defined. The set of parsing rules dictate
30 how the configuration data should be read, understood, and potentially transformed
27

into a standardized format suitable for storage, reporting, or further processing. The parsing unit [210] operates by applying these rules to extract relevant information from the raw configuration data, ensuring that the data adheres to the expected structure and content needed by the system for effective network management. 5
[0083] Thereafter, the method terminates at step [318].
[0084] Referring to FIGs. 4A & 4B, exemplary implementation of the process for automatically parsing configurations, in accordance with exemplary embodiments 10 of the present disclosure. As shown in FIG. 4A & 4B, the method [400] starts at step [402].
[0085] At step [404], the process initiates with the user selecting specific vendors, such as vendor 1 or vendor 2, to configure the system's parsing capabilities to the 15 correct configuration formats and syntaxes provided by these vendors.
[0086] At step [406], once the vendor is selected, the user interacts with the front-end parser.
20 [0087] At step 408, the user is then given the option to input identifiers. Identifiers might include unique names or addresses for devices.
[0088] At step 410, the user is then given the option to input parameters. The
parameters could refer to settings within these devices.
25
[0089] At step 412, the user is then given the option to input command options for
the configuration management of network elements. The command options might
pertain to the commands required to alter these settings.
30 [0090] At step 414, following the input selection, the user moves to the package creation phase.
28

[0091] At step 416, determination to ascertain whether an attempt is made to create a package that exists within the system.
[0092] At step 418, in case a package already exists within the system an error 5 notification alerts the user to select a different package name.
[0093] At step 420, in case the package doesn’t exist within the system a success message is indicated that the new package has been created.
10 [0094] At step 422, the user is given the following options after creating a new package. The options include (A.) the user is given an option to replicate the package. Once the replication request is received, the system [200] uses the details of the existing software package to create a new, identical copy of it. (B.) The user is given an option to specify whether a particular software package should be
15 activated (enabled) or deactivated (disabled), depending on the operational requirements or changes in the network configuration. Upon receiving the command from user, the system [200] executes the specified action, either enabling or disabling the software package. (C.) The user is given an option to define default parsing rule for any new package that has been created. (D.) The user is given an
20 option to delete the newly created software package. Once the system [200] receives
the deletion request from the user, the system [200] proceeds with the actual
removal of the software package from the system's records, thus preventing clutter
and potential conflicts within the system by ensuring that only current and
necessary software packages are retained.
25
[0095] The user is then presented with two distinct pathways for adding
configuration details to the system: manual entry or bulk upload.
[0096] At step 424, manual entry option is presented. 30
29

[0097] At step 426, manual entry allows the user for a detailed, entry-by-entry approach to input various configurations such as identifiers, parameters, and command details manually.
5 [0098] At step 428, further in manual processing after the submission of identifiers, parameters and command details, the system checks for pre-existing identifiers, parameters, or commands to prevent duplication.
[0099] At step 430, if a conflict is detected, an error is displayed promoting the user 10 to correct the issue.
[0100] At step 432, if the identifier/parameter does not exist, the system creates the parsing rules and maps to the appropriate identifiers, parameters, and commands.
15 [0101] At step 434, it is determined to ascertain whether the parsing rules are created/generated and mapped to appropriate identifiers, parameters, and commands.
[0102] At step 436, an error is shown in case the parsing rules are not 20 created/generated and mapped to appropriate identifiers, parameters, and commands.
[0103] At step 438, in case the parsing rules are created/generated and mapped to appropriate identifiers, parameters, and commands, the data related to the said 25 created and mapped identifiers, parameters, and commands are ingested in the form of dictionary tables to be stored in a database.
[0104] At step 440, bulk upload option is presented.
30 [0105] At step 442, bulk upload option allows the user to upload a preformatted spreadsheet files for example an excel files (.xlsx), to import several configurations at once.
30

[0106] At step 444, it is checked whether the spreadsheet file format is correct or valid.
5 [0107] At step 446, in case the spreadsheet file format is incorrect, an error is displayed prompting the user to upload the correct or valid file format.
[0108] At step 448, in case, the spreadsheets file format is correct, the file is
uploaded, and the user receives a status mail.
10
[0109] At step 450, the system [200] validates the file headers.
[0110] At step 452, it is checked whether the file header is validated or not.
15 [0111] At step 454, if validation fails at any point, the system [200] halts further processing and informs the respective stakeholder of the error.
[0112] At step 456, if the validation is passed, the file headers are iterated/processed for each record to create corresponding parsing rules and mapped 20 identifiers with parameters and commands.
[0113] At step 458, it is checked whether the validation of file headers is passed or failed.
25 [0114] At step 460, in case validation of file headers fails, the system writes status as failed along with remark in the same spreadsheet.
[0115] At step 462, in case validation of file headers passes, the system writes status as passed and the outcomes of these validations are reflected in the spreadsheets 30 (such as excel sheet). In an exemplary aspect, the longest data in the form of dictionary table are stored in the database.
31

[0116] At step 464, the spreadsheets (such as excel sheet) is stored on a shared drive for future reference.
[0117] At step 466, notification emails are sent to respective users/stakeholders 5 with updates on the process outcomes, ensuring transparency and keeping relevant parties informed of the system's activities.
[0118] At step 468, the parsing process is triggered based on the ingested rules. In
an exemplary aspect, the ingested rules are stored in the database.
10
[0119] At step 470, for both manual and bulk upload methods, once parsing rules
are set, the system may engage with a Distributed Cluster, which includes
Distributed File System (DFS) and Hbase, for large-scale data storage and
processing, and a database for structured data storage.
15
[0120] At step 472, a configuration management (CM) processing engine, is
initiated to parse the configuration data following the ingested rules. In an
exemplary aspect, the processing engine performs tasks in a distributed computing
cluster.
20
[0121] Thereafter, the process terminates at step [474].
[0122] FIG. 5 illustrates an exemplary block diagram of a computing device [500] (Also, referred to herein as computer system [500]) upon which an embodiment of
25 the present disclosure may be implemented. In an implementation, the computing device implements the method for automatically parsing configurations using the system [200]. In another implementation, the computing device itself implements the method for automatically parsing configurations by using one or more units configured within the computing device, wherein said one or more units are capable
30 of implementing the features as disclosed in the present disclosure.
32

[0123] The computing device [500] may include a bus [502] or other communication mechanism for communicating information, and a processor [504] coupled with bus [502] for processing information. The processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also 5 include a main memory [506], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [504]. Such
10 instructions, when stored in non-transitory storage media accessible to the processor [504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static information and
15 instructions for the processor [504].
[0124] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a
20 display [512], such as a cathode ray tube (CRT), for displaying information to a computer user. An input device [514], including alphanumeric and other keys, may be coupled to the bus [502] for communicating information and command selections to the processor [504]. Another type of user input device may be a cursor controller [516], such as a mouse, a trackball, or cursor direction keys, for
25 communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512]. This inputs 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.
33

[0125] The computing device [500] may implement the techniques described herein using customized hard-wired logic, one or more Application-Specific Integrated Circuits (ASICs) or Field Programmable Gate Arrays (FPGAs), firmware and/or program logic which in combination with the computing device 5 [500] causes or programs the computing device [500] to be a special-purpose machine. According to one embodiment, the techniques herein are performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage 10 medium, such as the storage device [510]. Execution of the sequences of instructions contained in the main memory [506] causes the processor [504] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
15 [0126] The computing device [500] also may include a communication interface [518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
20 a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [518] 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 [518] sends and receives electrical,
25 electromagnetic or optical signals that carry digital data streams representing various types of information.
[0127] The computing device [500] can send messages and receive data, including
program code, through the network(s), the network link [520] and the
30 communication interface 518. In the Internet example, a server [530] might transmit
34

a requested code for an application program through the Internet [528], the Internet Service Provider (ISP) [526], the local network [522], host [524] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other 5 non-volatile storage for later execution.
[0128] The computing device [500] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [500] include, but are not limited only to, personal computers,
10 laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device [500] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their
15 versatility in various technological applications.
[0129] An aspect of the present disclosure provides a non-transitory computer-readable storage medium storing instruction for automatically parsing configurations, the storage medium comprising executable code which, when
20 executed by one or more units of a system, causes: a transceiver unit [202] to: receive a selection of one or more vendors; receive a selection of at least one of one or more identifiers, one or more parameters, and one or more command options; a package creator unit [204] connected to at least the transceiver unit [202], wherein the package creator unit [204] to create a node type and a software package; wherein
25 the transceiver unit [202] is further configured to receive a selection related to a package upload type functionality, and a selection related to a parsing control value associated with the one or more parameters; a configuration manager [206] connected to at least the package creator unit [204], wherein the configuration manager [206] to implement the selected package upload type functionality; a
30 scheduling unit [208] connected to at least the configuration manager [206], wherein the scheduling unit [208] to run a job scheduler to trigger a parser job file,
35

wherein the job scheduler is run in an event a set of parsing rules exist; and a parsing unit [210] connected to at least the scheduling unit [208], wherein the parsing unit [210] to parse a node-configuration data based on the set of parsing rules.
5 [0130] As is evident from the above, the present disclosure provides a technically advanced solution for automatically parsing configuration of networks The present solution automates parameter dictionary and configuration database of network elements across multiple vendors. Also, the present solution can assist in dynamically enabling or disabling the parsing of any parameter and can define the
10 new logic to parse. Further, the present solution can parse the network configuration automatically for any node type, for example, IDSC, ODSC, gNodeB, etc. Implementing the features of the present invention, a new software release can be auto detected, and configuration can be parsed automatically. Further, using the present solution, a user can configure parsing rule/logic to read any specific
15 parameter of any particular software package, and also the user has flexibility to: define default parsing rule for any new software package for no definition available; enable/disable the parsing of any parameter or Software package. Further, the present solution provides users with multiple options to define parsing rule, either select the parameters and their parsing logic manually or can be done through bulk
20 upload which holds multiple parameters and respective parsing rules in single sheet. Further, the present solutions enables users to download any release data and their history. Also, implementing the features of the present invention, one is able to search any configuration details.
25 [0131] 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
30 functionality of specific units, as disclosed in the disclosure, should not be construed as limiting the scope of the present disclosure. Consequently, alternative
36

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
5 [0132] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to 10 be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
37

We Claim:
1. A method for automatically parsing configurations, the method comprising:
- receiving, by a transceiver unit [202], a selection of one or more
5 vendors;
- receiving, by the transceiver unit [202], a selection of at least one of one
or more identifiers, one or more parameters, and one or more command
options;
- creating, by a package creator unit [204], a node type and a software
10 package;
- receiving, by the transceiver unit [202], a selection related to a package
upload type functionality, and a selection related to a parsing control
value associated with the one or more parameters;
- implementing, by a configuration manager [206], the selected package
15 upload type functionality;
- running, by a scheduling unit [208], a job scheduler to trigger a parser
job wherein the job scheduler is run in an event a set of parsing rules
exist; and
- parsing, by a parsing unit [210], a node-configuration data based on the
20 set of parsing rules.

25

2. The method as claimed in claim 1, wherein post the creating, by the package
creator unit [204], a software package, the method comprises:
- generating, by the package creator unit [204], one of: a success
notification indicating a successful creation of the software package, and
an error notification indicating a prior existence of the software package.

30

3. The method as claimed in claim 1 wherein the package upload type functionality is one of a bulk upload functionality and a manual upload functionality.

38

5
10
15

4. The method as claimed in claim 3, wherein the manual upload functionality comprises:
- adding a set of details, the set of details comprising the one or more identifiers, the one or more parameters, and the one or more command options;
- submitting a request based on the addition of the set of details;
- performing a first validation based on the added set of details;
- generating one of a successful first validation notification, and an error first validation notification, wherein the successful first validation notification is generated in an event the added details are correct, and an unsuccessful first validation notification is generated in an event the added details are incorrect;
- creating the set of parsing rules in an event the successful first validation notification is generated; and
- storing the set of parsing rules in a database in a storage unit [212].

5. The method as claimed in claim 3, wherein the bulk upload functionality
comprises:
20 - adding a set of configuration details based on a predefined upload
template;
- uploading the set of configurations details,
- generating a notification wherein the notification is one of a successful upload completion notification, and an unsuccessful upload completion
25 notification;
- performing a second validation based on the set of configuration details and the successful upload completion notification;
- marking, one of: a success second validation status and a failure second validation status, wherein the success second validation status is marked
30 in an event the set of configuration details are correct, and the failure
39

5
10
15

second validation status is marked in an event the set of configuration details are incorrect;
- mapping the identifiers with the one or more parameters, and the one or more command options based on the success second validation status; and
- creating the set of parsing rules in an event of generation of the success second validation status.
6. The method as claimed in claim 4, the method further comprising:
- storing, in a database at the storage unit [212], a parsed data based on
the parsing of the node-configuration data.
7. The method as claimed in claim 1 wherein the selection related to the
parsing control value associated with the one or more parameters comprises
a selection for one of enabling and disabling the parsing of the one or more
parameters.

8. The method as claimed in claim 1 further comprising:
- receiving, at the transceiver unit [202], a request for replication, the
20 request comprising a data indicating the created software package; and
- replicating, by the package creator unit [204], a new software package
based on the received request and the created software package.
9. The method as claimed in claim 1 further comprising:
25 - receiving, at the transceiver unit [202], a request for modifying a status
of the created software package, wherein the request is one of an enable package request and a disable package request; and
- performing, by the configuration manager [206], a status modification
action on the created software package, wherein an enable action is
30 performed in an event the enable package request is received, and a
40

disable action is performed in an event the disable package request is received.
10. The method as claimed in claim 1 further comprising:
5 - receiving, at the transceiver unit [202], a request for deleting the created
software package; and
- deleting, by the configuration manager [206], the created software
package.
10 11. A system for automatically parsing configurations, the system comprising:
- a transceiver unit [202] configured to:
o receive a selection of one or more vendors;
o receive a selection of at least one of one or more identifiers, one
or more parameters, and one or more command options;
15 - a package creator unit [204] connected to at least the transceiver unit
[202], wherein the package creator unit [204] is configured to create a
node type and a software package;
wherein the transceiver unit [202] is further configured to receive a selection
related to a package upload type functionality, and a selection related to a
20 parsing control value associated with the one or more parameters;
- a configuration manager [206] connected to at least the package creator
unit [204], wherein the configuration manager [206] is configured to
implement the selected package upload type functionality;
- a scheduling unit [208] connected to at least the configuration manager
25 [206], wherein the scheduling unit [208] is configured to run a job
scheduler to trigger a parser job file, wherein the job scheduler is run in an event a set of parsing rules exist; and
- a parsing unit [210] connected to at least the scheduling unit [208],
wherein the parsing unit [210] is configured to parse a node-
30 configuration data based on the set of parsing rules.
41

5

12. The system as claimed in claim 11, wherein the package creator unit [204], post the creation of the software package, is configured to: - generate one of: a success notification indicating a successful creation
of the software package, and an error notification indicating a prior
existence of the software package.

10

13. The system as claimed in claim 11 wherein the package upload type functionality is one of a bulk upload functionality and a manual functionality.

14. The system as claimed in claim 13, wherein the manual upload functionality comprises:
- adding a set of details, the set of details comprising the one or more
15 identifiers, the one or more parameters, and the one or more command
options;
- submitting a request based on the addition of the set of details;
- performing a first validation based on the added set of details;
- generating one of a successful first validation notification, and an error 20 first validation notification, wherein the successful first validation
notification is generated in an event the added details are correct, and an unsuccessful first validation notification is generated in an event the added details are incorrect;
- creating the set of parsing rules in an event the successful first validation 25 notification is generated; and
- storing the set of parsing rules in a database in a storage unit [212].
15. The system as claimed in claim 13, wherein the bulk upload functionality comprises:
42

5
10
15

-
-
-
-
-
-
-

adding a set of configuration details based on a predefined upload
template;
uploading the set of configurations details,
generating a notification, wherein the notification is one of a successful
upload complete notification, and an unsuccessful upload completion
notification;
performing a second validation based on the set of configuration details
and the successful upload completion notification;
marking, one of: a success second validation status and a failure second
validation status, wherein the success second validation status is marked
in an event the set of configuration details are correct, and the failure
second validation status is marked in an event the set of configuration
details are incorrect;
mapping the identifiers with the one or more parameters, and the one or
more command options; and
creating the set of parsing rules in an event of generation of the success
second validation status.

16. The system as claimed in claim 14, wherein the transceiver unit [202] is
20 further configured to:
- store, in a database at the storage unit [212], a parsed data based on the parsing of the node-configuration data.
17. The system as claimed in claim 11 wherein the selection related to the
25 parsing control value associated with the one or more parameters comprises
a selection for one of enabling and disabling the parsing of the one or more parameters.
18. The system as claimed in claim 11 wherein:
43

- the transceiver unit [202] is further configured to receive a request for
replication, the request comprising a data indicating the created software
package; and
- the package creator unit [204] is further configured to replicate a new
5 software package based on the received request and the created software
package.
19. The system as claimed in claim 11 wherein:
- the transceiver unit [202] is configured to receive a request for
10 modifying a status of the created software package, wherein the request
is one of an enable package request and a disable package request; and
- the configuration manager [206] is configured to perform a status
modification action on the created software package, wherein an enable
action is performed in an event the enable package request is received,
15 and a disable action is performed in an event the disable package request
is received.
20. The system as claimed in claim 11 wherein:
- the transceiver unit [202] is further configured to receive a request for
20 deleting the created software package; and
- the configuration manager [206] is further configured to delete the
created software package.