System and method for configuration management (CM) recipe builder

Abstract

A recipe builder (108) and method (700) for creating a configuration management (CM) recipe. An interfacing unit (212) provides a plurality of recipe creation options to a user. The plurality of recipe creation options comprises a bulk upload option, a manual creation option, and a parsing rules updation option. The interfacing unit (212) receives at least one recipe creation option selected by the user and one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user. A processing unit (214) creates the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

Description

SYSTEM AND METHOD FOR CONFIGURATION MANAGEMENT (CM) RECIPE BUILDERRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to systems and methods for configuration management (CM) recipe builder.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term “Recipe” refers to a predefined set of instructions, guidelines, or a template that outlines the steps and parameters required to configure network devices, ensuring they work together efficiently and securely.

[0005] The term “Recipe Builder” refers to a system or an application that allows users to create, customize, and organize recipes. The recipe builder provides an interface where users may provide inputs and select options. The recipe buildercreates recipes based on the inputs and selected options. The recipe builder displays created recipes over the interface.

[0006] The term “Configuration Management” refers to the process of systematically managing and controlling the configurations of a system or network by identifying, organizing, and maintaining the various components and settings, and ensuring they are consistent, reliable, and secure.BACKGROUND

[0007] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0008] As wireless technologies are evolving, there is a need to cope with the 5G requirements and deliver a high level of service to the users. In order to meet the user’s demand, there is requirement of configuration management (CM) of the network. The configuration management helps to control and monitor the actual configuration on the network elements and network resources. The configuration management maintains network integrity by automating the monitoring, auditing, updating, validating, and reporting of cell site configurations. In a 5G environment, there is requirement of numerous new cell sites to be deployed. The network operators need to configure network resources of the new sites to assure correct and effective operation of the network. Configuring the complex new sites take many hours. The new configuration may lead to a set of errors with invalid ranges, invalid values and so on. While some of these issues can be identified and corrected during the deployment stage, this inevitably translates into more service hours and lengthy delays. Further, over time the configuration of network nodes may change (e.g., due to newly added services). Additionally, many telecommunications nodes operateusing firmware that can be updated periodically. In both new and existing communication networks, a major challenge is testing and troubleshooting to ensure the network operators identify the causes of any performance issues. The traditional techniques fail to accurately detect the root cause of the radio node performance degradation. The traditional techniques for updating the telecommunications node configuration require a lot of manual effort by the telecom operators. Thus, the traditional techniques are inefficient and time-consuming. Therefore, there is a need for an improved system and a method that overcomes the limitations of the prior arts and efficiently updates the telecommunications node configuration and optimizes the performance of the network.SUMMARY

[0009] In an exemplary embodiment, the present disclosure relates to a method for creating a configuration management (CM) recipe. The method comprises providing, by an interfacing unit, a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. The method comprises receiving, by the interfacing unit, at least one recipe creation option selected by the user and receiving, by the interfacing unit, one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user, and creating, by a processing unit, the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

[0010] In some embodiments, the method further comprises displaying, by the interfacing unit, the created CM recipe on a recipe listing page.

[0011] In some embodiments, the method further comprises receiving, by the interfacing unit, at least one operation to be performed on the created CM recipe from the user. The at least one operation comprises download, delete, set as default, andremove as default. The method comprises performing, by the processing unit, the at least one received operation on the created CM recipe.

[0012] In some embodiments, the method further comprises generating, upon receiving the selection of the bulk upload option from the user, by the processing unit, a template having one header corresponding to each of the one or more configuration parameters to be downloaded and filled by the user and uploading, by the interfacing unit, a filled template having at least one value in each header corresponding to each of the one or more configuration parameters filled by the user. The method further comprises processing, by the processing unit, the filled template to create the CM recipe based on the received filled template.

[0013] In some embodiments, the method comprises providing, upon receiving the selection of the manual creation option, by the interfacing unit, one or more input options. The one or more input options comprise command, script and library. The method comprises receiving, by the interfacing unit, at least one input option selected by the user and creating, by the processing unit, the CM recipe based on the at least one received input option.

[0014] In some embodiments, the method further comprises receiving, upon receiving the selection of the parsing rules option, by the interfacing unit, one or more parameters selected by the user, parsing, by the processing unit, the one or more parameters selected by the user and creating, by the processing unit, the CM recipe based on the parsing.

[0015] In some embodiments, the one or more configuration parameters comprise a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, a network element (NE) type and an execution order.

[0016] In some embodiments, the method further comprises validating, by the processing unit, the created CM recipe based on a set of predefined validation rules.

[0017] In some embodiments, the method further comprises sending, by the processing unit, a notification corresponding to at least one created recipe to the user. The notification comprises a name of recipe creator, a status of the recipe and a linkcorresponding to the created recipe. The status of the recipe is at least one of an initial state, a drafted state, a failed state, and a created state.

[0016] In another exemplary embodiment, the present disclosure relates to a recipe builder for creating a configuration management (CM) recipe. The recipe builder comprises an interfacing unit. The interfacing unit is configured to provide a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. The recipe builder is configured to receive at least one recipe creation option selected by the user and receive one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user. A processing unit is coupled to the interfacing unit and configured to create the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

[0017] In some embodiments, the interfacing unit is configured to display the created CM recipe on a recipe listing page.

[0018] In some embodiments, the interfacing unit is configured to receive at least one operation to be performed on the created CM recipe from the user. The at least one operation comprises download, delete, set as default, and remove as default. The processing unit is configured to perform the at least one received operation on the created CM recipe.

[0019] In some embodiments, upon receiving selection of the bulk upload option from the user, the processing unit is configured to generate a template having one header corresponding to each of the one or more configuration parameters to be downloaded and filled by the user. The interfacing unit is configured to upload a filled template having at least one value in each header corresponding to each of the one or more configuration parameters filled by the user. The processing unit is configured to process the filled template to create the CM recipe based on the received filled template.

[0020] In some embodiments, upon receiving the selection of the manual creation option, the interfacing unit is configured to provide one or more inputoptions. The one or more input options comprise command, script and library. The interfacing unit is configured to receive at least one input option selected by the user. The processing unit is configured to create the CM recipe based on the at least one received input option.

[0021] In some embodiments, upon receiving the selection of the parsing rules option, the interfacing unit is configured to receive one or more parameters selected by the user. The processing unit configured to process the one or more parameters selected by the user and create the CM recipe based on the parsing.

[0022] In some embodiments, the one or more configuration parameters comprise a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, a network element (NE) type and an execution order.

[0023] In some embodiments, the processing unit is configured to validate the created CM recipe based on a set of predefined validation rules.

[0024] In some embodiments, the processing unit is configured to send a notification corresponding to at least one created recipe to the user. The notification comprises a name of recipe creator, a status of the recipe and a link corresponding to the created recipe. The status of the recipe is at least one of an initial state, a drafted state, a failed state, and a created state.

[0025] In yet another exemplary embodiment, the user equipment is communicatively coupled with the recipe builder. The coupling comprises steps of receiving, by the recipe builder, a connection request from the UE, sending, by the recipe builder, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request, the recipe builder is configured to create a configuration management (CM) recipe. The recipe builder comprises an interfacing unit. The interfacing unit is configured to provide a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. The recipe builder is configured to receive at least one recipe creation option selected by the user and receive one or more inputs corresponding toone or more configuration parameters corresponding to the at least one selected recipe creation option by the user. A processing unit is coupled to the interfacing unit and configured to create the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

[0018] In yet another exemplary aspect, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for creating a configuration management (CM) recipe. The method comprises providing, by an interfacing unit, a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. The method comprises receiving, by the interfacing unit, at least one recipe creation option selected by the user and receiving, by the interfacing unit, one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user, and creating, by a processing unit, the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

[0026] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.OBJECTS OF THE DISCLOSURE

[0027] Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0028] An object of the present disclosure is to provide a system and a method for configuration management (CM) recipe builder.

[0029] Another object of the present disclosure is to create multiple recipes for different CM modules through a bulk upload option.

[0030] Yet another object of the present disclosure is to perform multiple actions (e.g., delete, send, upload, set as default, remove as default, etc.) on the created recipes through an interfacing unit (e.g., user interface (UI)).

[0031] Yet another object of the present disclosure is to check status (e.g., initialize, draft, created, failed, etc.) of the created recipes on a home page of the CM recipe builder.

[0032] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0033] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated 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.

[0034] FIG. 1 illustrates an exemplary network architecture implementing a system for creating a configuration management (CM) recipe, in accordance with embodiments of the present disclosure.

[0035] FIG. 2 illustrates an exemplary block diagram of the system, in accordance with embodiments of the present disclosure.

[0036] FIG. 3 illustrates an exemplary system architecture for creating the CM recipe, in accordance with an embodiment of the present disclosure.

[0037] FIG. 4 illustrates an exemplary flow diagram for creating the CM recipe, in accordance with an embodiment of the present disclosure.

[0038] FIG. 5 illustrates an exemplary flow diagram for Bulk upload / Manual creation / Parsing Rules option selection for creating the CM recipe, in accordance with an embodiment of the present disclosure.

[0039] FIGs. 6A-6I illustrate exemplary user interfaces for a CM recipe builder, in accordance with an embodiment of the present disclosure.

[0040] FIG. 7 illustrates another exemplary flow diagram of the method for creating the CM recipe, in accordance with embodiments of the present disclosure.

[0041] FIG. 8 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.

[0042] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 Network architecture102-1, 102-2...102-N Users104-1, 104-2...104-N User equipment106 Network108 System200 Block Diagram of System202 One or more processor(s)204 Memory206 I / O interface(s)208 Processing engine210 Database212 Interfacing Unit214 Processing Unit220 Other Modules300 System Architecture302 Web Portals304 Load Balancer306 Web Servers308 Application Servers310 Gateway Servers312 Reporting Servers314 Distributed File System (DFS)316 Service318-1 Database318-2 Database Management System320 VM tool400 Flow diagram500 Flow diagram600A-600I User Interface700 Method Flow Diagram800 Computer System810 External Storage Device820 Bus830 Main Memory840 Read-Only Memory850 Mass Storage Device860 Communication Ports870 ProcessorDETAILED DESCRIPTION

[0043] 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 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. 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 which like reference numerals refer to the same parts throughout the different drawings.

[0044] 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 thefunction and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0045] 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 components may be shown as components in block diagram form in order not to 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.

[0046] Also, it is noted that individual embodiments may be described as a process that 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 is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0047] 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 like the term“comprising” as an open transition word without precluding any additional or other elements.

[0048] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0049] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. 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 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.

[0050] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that manyembodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0051] As wireless technologies are evolving, there is a need to cope with the 5G requirements and deliver a high level of service to the users. In order to meet the user’s demand, there is requirement of configuration management (CM) of the network. The configuration management helps to control and monitor the actual configuration on the network elements and network resources. The configuration management maintains network integrity by automating the monitoring, auditing, updating, validating, and reporting of cell site configurations. In a 5G environment, there is requirement of numerous new cell sites to be deployed. The network operators need to configure network resources of the new sites to assure correct and effective operation of the network. Configuring the complex new sites take many hours. The new configuration may lead to a set of errors with invalid ranges, invalid values and so on. While some of these issues can be identified and corrected during the deployment stage, this inevitably translates into more service hours and lengthy delays. Further, over time the configuration of network nodes may change (e.g., due to newly added services). Additionally, many telecommunications nodes operate using firmware that can be updated periodically. In both new and existing communication networks, a major challenge is testing and troubleshooting to ensure the network operators identify the causes of any performance issues. The traditional techniques fail to accurately detect the root cause of the radio node performance degradation. The traditional techniques for updating the telecommunications node configuration require a lot of manual effort by the telecom operators. Thus, the traditional techniques are inefficient and time-consuming. Therefore, there is a need for an improved system and a method that overcomes the limitations of the prior artsand efficiently updates the telecommunications node configuration and optimizes the performance of the network.

[0052] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for configuration management (CM) recipe creation. A recipe (set of instructions or processes) is created for configuration management in the network. The user selects a create recipe via an interfacing unit. One of plurality of recipe creation options (a bulk upload, a manual creation, parsing rules) is selected. A recipe is created based on selection of one of plurality of recipe creation options. The created recipe is displayed on the interfacing unit. One of plurality of operations comprising download, delete, set as default, remove as default is performed on the created recipe.

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

[0054] FIG. 1 illustrates an exemplary network architecture implementing a system for creating a configuration management (CM) recipe, in accordance with embodiments of the present disclosure.

[0055] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2...102-N) in an environment. The network architecture (100) may also include a network entity (110) and a network (106).

[0056] A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.

[0057] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device. The user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touch pad, touch enabled screen, electronic pen, and the like.

[0058] In an embodiment, each of the user equipment (104-1, 104-2... 104-N) includes an interfacing unit via which the user (102) may provide one or more user inputs (e.g., request).

[0059] In an exemplary embodiment, the network (106) may include, but not be limited to, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an exemplary embodiment, the network (106) may include, but not be limited to, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0060] In an embodiment, the user equipment (104) is communicatively coupled with the system (108). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) may be configured for creating a configuration management (CM) recipe.

[0061] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0062] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for creating the CM recipe, in accordance with embodiments of the present disclosure.

[0063] FIG. 2 with reference to FIG. 1 , illustrates the block diagram (200) of the system (108) for creating the CM recipe, in accordance with embodiments of the present disclosure.

[0064] The system (108) includes one or more processor(s) (202), a memory (204), a processing engine (208), a database (210), and an interface(s) (206). In an exemplary embodiment, the processing engine (208) may include one or more engines selected from any of an interfacing unit (212), a processing unit (214), and other modules (220) having functions that may include but are not limited to testing, storage, and peripheral functions.

[0065] In an embodiment, the one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured tofetch and execute computer-readable instructions stored in the memory (204) of the system (108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0066] In an embodiment, the interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (RO), storage devices, and the like. The interface(s) (206) may facilitate communication through the processor(s) (202). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108).

[0067] The interface(s) (206) is included within the system (108) to serve as a medium for data exchange, configured to facilitate user interaction with the mobile application. The interface(s) (206) may be composed of interfaces for data input and output devices, storage devices, and the like, providing a communication pathway for the various components of the system (108). Examples of such components include, but are not limited to, the processing unit / engine(s) (208) and the database (210).

[0068] In an embodiment, the processing unit / engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208).

[0069] In such examples, the system (108) may comprise the machine -readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0070] In an embodiment, the database (210) is configured for serving as a centralized repository for storing and retrieving various operational data. The database (210) is designed to interact seamlessly with other components of the system (102) to support the system's functionality effectively. The database (210) may store data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (108).

[0071] As illustrated in Fig. 2, the memory (204) and the one or more processors (202) may be configured to execute a set of instructions stored in the memory (204). These instructions may orchestrate a series of operations involving various components to streamline CM recipe creation.

[0072] In an operative aspect, the system (108) may function as a recipe builder. In an aspect, recipe builder is also referred as CM recipe builder. A person of ordinary skill in the art will appreciate that the terms “System”, “Recipe builder” and “CM recipe builder” may be used interchangeably throughout the disclosure.

[0073] The recipe builder (108) is configured for creating a configuration management (CM) recipe. The recipe builder (108) comprises the interfacing unit (212) and the processing unit (214).

[0074] In an aspect, the interfacing unit (212) may also be referred to as a user interface. In an aspect, the interfacing unit (212) may be a graphical user interface (GUI), a command line interface (CLI), or an application programming interface (API). In an aspect, the GUI refers to a user interface that allows users to interact with the devices through visual elements (e.g., icons, windows, and menus). In an aspect, the command-line Interface (CLI) refers to a text-based user interface where the userinteracts with the device by typing commands into a terminal or console. In an aspect, the application-programming interface (API) refers to a set of rules and protocols that allows different software applications or systems to communicate with each other. It defines the methods and data structures that applications can use to interact with the software component, operating system, or service. A person of ordinary skill in the art will appreciate that the terms “interfacing unit” and “user interface” may be used interchangeably throughout the disclosure.

[0075] The interfacing unit (212) is configured to provide a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. In an aspect, the user may be a network administrator or a network operator. The network administrator is responsible for managing, maintaining, and troubleshooting the network infrastructure. The network operator manages, maintains, and operates the network. The network operator provides network services, ensuring connectivity for customers, businesses, and organizations, and are typically responsible for the infrastructure, network operations, and service delivery within a specific geographic area or globally.

[0076] The interfacing unit (212) is configured to receive at least one recipe creation option selected by the user. The interfacing unit (212) is configured to receive one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user. The one or more configuration parameters include a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, a network element (NE) type. The status of the recipe is at least one of an initial state, a drafted state, a failed state, and a created state.

[0077] In the bulk upload option, the processing unit (214) is configured to generate a template having one header corresponding to each of the one or more configuration parameters to be downloaded and filled by the user. The interfacing unit (212) is configured to upload a filled template having at least one value in each header corresponding to each of the one or more configuration parameters filled bythe user and the processing unit (214) is configured to process the filled template to create the CM recipe based on the received filled template. In an aspect, upon selecting the bulk upload option by the user, the template is generated. The template may be in spread sheet format (e.g., excel file). The template comprises one header corresponding to each of the configuration parameters. The headers comprise a recipe name, a recipe type, a software version, a vendor, a network element type, an execution order, etc. The user fills data corresponding to each header.

[0078] In an aspect, the recipe name refers to name given by the user to the recipe. In an example, for random access network (RAN) parameter change, the recipe name is RPC. For software upgradation the recipe name is SW_Upgrade.

[0079] In an aspect, the recipe type refers to a type of operation performed. In an example, software upgradation, sector grow, carrier grow, remote electrical tilt, automatic tilt optimization, etc.

[0080] In an aspect, software version refers to a specific iteration or release of a software product, which is identified by a unique version number. This number typically reflects changes, updates, or enhancements made to the software.

[0081] In an aspect, the vendor refers to an entity that develops, maintains, and sells products or services.

[0082] In an aspect, the network element type refers to a classification or category of devices or components within the network that perform specific functions to enable communication, data transmission, or network management. These elements are typically categorized based on their role or functionality within the network. In an example, the network element type comprises base station, router, modem, business support system, operation support system, customer premises equipment (CPE), network controllers, load balancers, gateway, switches, etc.

[0083] In an aspect, the execution order refers to the sequence or arrangement in which commands are carried out.

[0084] In bulk upload option, data corresponding to one or more recipes are filled. In an example, for recipe 1, data comprises recipe name = 2211RR, recipe type = random access network (RAN) parameter change (RPC), a software version = 12.2,vendor = XYZ, network element type = Macro. For recipe 2, data comprises recipe name = 1122RR, recipe type = software upgrade (SW_Upgrade), a software version = 12.4, vendor = ABC, network element type = Macro. For recipe 3, recipe name = 1212RR, recipe type = RAN parameter change (RPC), a software version = 12.6, vendor = PQR, network element type = Macro. The recipes (i.e., recipe 1, recipe 2 and recipe 3) are filled in the template.

[0085] The filled template is uploaded / saved in the database (210). The processing unit (214) processes the filled template, i.e., checking its correctness, ensuring that all required fields are filled, and that the data meets the required format (e.g., dates, numbers, field format, etc.). If the filled template is in the correct format, the CM recipe is created for the bulk upload option. If the filled template is not in the correct format, an error is displayed to the user.

[0086] In an aspect, in the manual creation option, the interfacing unit (212) is configured to provide one or more input options. The one or more input options comprise command and script. The interfacing unit (212) is configured to receive at least one input option selected by the user. The processing unit (214) is configured to create the CM recipe based on the at least one received input option.

[0087] In an aspect, the command type refers to a specific category or classification of commands in system, software, or application that instructs it to perform a particular action or operation. In an example, the command comprises retrieve, output, change, etc.

[0088] In an aspect, the script refers to a series of commands executed to perform an operation.

[0089] In an aspect, in the manual creation option, two subsequent options are displayed on the interfacing unit (212) (i.e., basic details and create recipe). In the basic details, fields such as a recipe name, a recipe type, a software version, a vendor, a NE type are to be filled by the user. In an example, the recipe type comprises a remote electrical tilt, an automatic tilt optimization, a package upgradation, a new sector grow, and a new carrier grow, etc.

[0090] In the create recipe of the manual creation option, the interfacing unit (212) provides two options i.e., new recipe or existing recipe. In the existing recipe, a previously created recipe is selected. In the new recipe, the interfacing unit (212) provides one or more input options (i.e., command, script. In the command input option, the user provides the commands corresponding to the recipe. In the command input option, the fields (such as NE type, execution order, sequence, command type, command syntax, identifier, etc.) are to be filled by the user.

[0091] After filling the fields for command input option, the user may select create option on the interfacing unit (212). The processing unit (214) performs processing of the fields (i.e., validation of data format, number, etc.). After validation, the recipe is created based on fields.

[0092] In the script input option of the manual creation option, the user provides the script (series of commands) corresponding to the recipe. Based on the script, the recipe is created.

[0093] After the filling the fields, the interfacing unit (212) displays the filled fields to the user. The interfacing unit (212) provides two options (i.e., “Save” or “Previous”). The user may select the previous option if the user wants to make changes in the filled fields. The user may select the save option if the filled fields are correct. After selecting the save option, the fields for the recipe are saved. The recipe is created based on the saved fields.

[0094] In an aspect, in the parsing rules option, the interfacing unit (212) is configured to receive one or more parameters selected by the user. The processing unit (214) is configured to process the one or more parameters selected by the user and create the CM recipe based on the parsing. The parsing rule option is used to get the values corresponding to the one or more parameters. In the parsing rule, the userinputs values corresponding to identifiers, commands, and parameters. The inputted values corresponding to identifiers, commands, and parameters are stored as parsing rules in the database (210). In an example, user requires details corresponding to the cell in the network. The user enters a command such as get info corresponding to the cell. The processing unit (214) parses the entered command. Then, the command and cell parameters are parsed with the parsing rules. If the command and its parameters exist according to the parsing rules, then the values corresponding to the parameters are provided to the user.

[0095] The processing unit (214) is coupled to the interfacing unit (212) and configured to create the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters. In an aspect, the processing unit (214) creates the CM recipe based on the inputs corresponding to the one or more configuration parameters. The recipe created is based on the following combination of fields: Recipe Name + Recipe Type + Software version + Vendor + NE Type.

[0096] The interfacing unit (212) is configured to display the created CM recipe on a recipe listing page. In the recipe listing page, all created CM recipes are displayed. Details corresponding to the created CM recipes are displayed on the listing page. The details corresponding to the created CM recipes comprise a status of the recipe, a recipe identifier, a recipe name, a recipe type, a software version, a recipe vendor, network element (NE) type, etc.

[0097] In an aspect, the status of the created CM recipe refers to current state or condition of the recipe that has been created. The status of the created CM recipe comprises initialize, draft, created and failed. The initialize status refers to a status of the recipe after submission of the recipe. The draft status refers to a status of the recipe in which the recipe content validation is performed. The failed status refers to a status of the recipe in which the recipe content validation is failed. The created status refers to a status of the recipe in which the recipe content validation is successful.

[0098] The processing unit (214) is configured to validate the created CM recipe based on a set of predefined validation rules. In an aspect, the created CM recipe is processed to determine whether it adheres to the validation rules (i.e., file format, data format, all fields are filled, etc.). The validation rules are predefined by the user. The set of predefined validation rules is stored in the database (210). The processing unit (214) validates the created CM recipe by matching details of the created CM recipe to the set of predefined validation rules. If the details of the created CM recipe match with the set of predefined validation rules, then the created CM recipe is validated (i.e., the status of the recipe is set as “created”). If the details of the created CM recipe do not match with the set of predefined validation rules, then the created CM recipe is not validated (i.e., the status of the recipe is set as “Failed”).

[0099] In an example, details corresponding to the created CM recipes are shown in the recipe listing page as follows:

[0100] The interfacing unit (212) is configured to receive at least one operation to be performed on the created CM recipe from the user. The at least one operation comprises download, delete, set as default, and remove as default. The processing unit (214) is configured to perform the at least one received operation on the created CM recipe. In an operative aspect, a dot menu is available on each of the recipe in the recipe listing page. The dot menu shows one or more operation options such as download, delete, set as default and remove as default. The user may select any one of the operations for each recipe. The selected operation is performed on the recipe.

[0101] The user may download all recipes in the recipe listing page using the download button. All recipes are downloaded in the spreadsheet (e.g., excel file). Thespread sheet comprises details such as recipe status, recipe identifier, recipe name, recipe type, software version, recipe vendor, NE type, user details, created date and time, etc. In an example, details are shown as follows:

[0102] The processing unit (214) is configured to send a notification corresponding to at least one created recipe to the user. The notification comprises a name of recipe creator, the status of the recipe and a link corresponding to the created recipe. In an aspect, the notification may be at least one of an electronic mail (e-mail), a short message service, or an in-app notification. The notification is sent to the user (i.e., creator of recipe) and other related users. The notification may be sent in one or more ways. The one or more ways comprise a notification for Bulk upload / Individual creation of recipes and a notification when the user (i.e., recipe creator) sends multiple recipes.

[0103] In an aspect, the notification for the bulk upload option contains data about the bulk uploading of recipes and information about the recipes.

[0104] In an aspect, when the user uploads the created CM recipe in the notification on the interfacing unit (212), the interfacing unit (212) displays an error to the user. The error may comprise an incorrect file format, incorrect number of sheets, an incorrect software version. In the incorrect file format, file extension is not correct. In the incorrect number of sheets, the interfacing unit (212) displays “please provide correct number of sheets in file”. In the incorrect software version / NE type, the interfacing unit (212) displays “SW Version is not present” or “NE type is not present”.

[0105] Furthermore, while processing the uploaded template, blanks values are checked in header and in recipe information. The blank value in any header indicates missing / incorrect header information in the recipe details. The blank Value in any recipe information indicates missing / incorrect values found in the recipe details.

[0106] If the recipe already exists while uploading, the interfacing unit (212) displays the recipe (with details such as the recipe ID, recipe type and software version) already exists.

[0107] In an aspect, in upload functionality, the new template for upload recipe (including execution order) is shared, and the notification for the same is also added.

[0108] The execution order column is added in a single recipe download sheet and a recipe command sheet in the manual creation option on the interfacing unit (212).

[0109] In an aspect, the system (108) provides flexibility to the user to create recipes for a plurality of CM modules through the bulk upload, the manual creation and the parsing rules. A plurality of user actions is performed on multiple creation recipes after the selection of the recipe from the interfacing unit (212). In an aspect, the plurality of CM modules comprises radio access network (RAN) configuration, core network configuration, service management configuration, network management and monitoring configuration, and security configuration. In an aspect, the recipes corresponding to radio access network (RAN) configuration comprise base station (e.g., NodeB, eNodeB, gNodeB) configuration recipe, load balancing configuration recipe, carrier aggregation configuration recipe, cell coverage and reselectionconfiguration recipe, etc. The recipes corresponding to core network configuration comprise the gateway configuration recipe, mobility management entity configuration recipe, and policy and charging rules configuration recipe. The recipes corresponding to service management configuration comprises quality of service configuration recipe, data service configuration recipe, voice service configuration recipe, multimedia service configuration recipe, customer management configuration recipe, etc. The recipes of network management and monitoring configuration comprise fault management configuration recipe, performance monitoring configuration recipe, network devices configuration management recipe, network availability monitoring recipe, traffic analysis and optimization recipe, etc. The recipes corresponding to security configuration comprise network access control configuration recipe, firewall configuration recipe, encryption configuration recipe, security logging and monitoring configuration recipe, and secure remote access configuration recipe.

[0110] In an aspect, the CM modules may use the created recipe to perform functions.

[0111] FIG. 3 illustrates an exemplary system architecture (300) for creating the CM recipe, in accordance with an embodiment of the present disclosure.

[0112] FIG. 3 with reference to FIGs. 1 and 2, illustrates the system architecture (300) for creating the CM recipe.

[0113] Referring to FIG. 3, the system architecture (300) comprises a plurality of web portals (302), a load balancer (304), a plurality of web servers (306), a plurality of application servers (308), a gateway server (310), a plurality of reporting servers (312), a distributed file system (DFS) (314), a plurality of services (316), a database (318-1), a database management system (318-2) and virtual machine (VM) tools (320).

[0114] The web portals (302) may be configured to receive at least one configuration update command from a user or a network operator. In an example, the at least one configuration update command may include at least parsing rule and at least one command corresponding to at least one parameter. In an example, to updatethe configuration of the network node, the network operator may apply / update a plurality of parsing rules, a plurality of identifiers, and a plurality of parameter values. In another example, the network operator may update configuration of the network node based on a software version already running on that network node. In an example, the network operator may update the software version running on the network node. The web portals (302) may be configured to receive a plurality of application programming interface (API) request(s) from a plurality of UEs. In an aspect, the API requests may get hit when an event related to any node configuration update request is detected from the UE.

[0115] The load balancer (304) may be configured to receive the plurality of API requests. The load balancer (304) may be configured to select a web server from the plurality of web servers (306) and forward the received API requests to the selected application server. The load balancer (304) may be configured to distribute plurality of API requests across the plurality of web servers (306) ensuring no single server is overburdened. The load balancer (304) may be configured to distribute incoming network traffic across the web servers. The load balancer (304) may be configured to adjust the distribution of requests dynamically to ensure optimal resource utilization. The load balancer (304) may be configured to monitor the health and performance of each web server and directs incoming data based on a set of algorithms (round-robin, least connections, etc.). The load balancer (304) may be configured to determine the web server based upon a number of parameters and forward the received data to the determined web server. In an example, the number of parameters may include number of active requests serving by each web server, and a threshold of requests to be served.

[0116] In an aspect, the load balancer (304) may be a dedicated load balancer. In an example, the load balancer (304) may configure to use POST as a request method supported by a Hypertext Transfer Protocol (HTTP) used by the World Wide Web. The POST request method requests a webserver to accept the data enclosed in the body of the request message, most likely for storing it. The POST request method is often used when uploading a file or when submitting a completed web form. Inanother aspect, when a specific server of the plurality of servers gets heavily loaded, the load balancer (304) may direct the incoming request to other servers. In another aspect, the plurality of servers may be configured in such a way that when a specific server fails, the other servers may take over to enable high availability (HA).

[0117] The plurality of web servers (306) is software and hardware that uses HTTP (Hypertext Transfer Protocol) and other protocols to respond to API requests made over the World Wide Web. The main job of a web server is to display website content through storing, processing and delivering webpages to users. Besides HTTP, the plurality of web servers (306) also supports SMTP (Simple Mail Transfer Protocol) and FTP (File Transfer Protocol), used for email, file transfer and storage. The web server hardware is connected to the internet and allows data to be exchanged with other connected devices, while web server software controls how a user accesses hosted files. In an aspect, the plurality of web servers (306) may be configured to process the received API requests and generates a plurality of processed API requests.

[0118] The plurality of web servers (306) may be configured to transmit the processed API requests to the plurality of application servers (308) and the plurality of gateway servers (310).

[0119] The plurality of application servers (308) may be configured to receive the requests from the plurality of web servers (306) and further may be configured to process the received requests. The application server may be configured to validate the received configuration update command (API request) by employing a set of formatting rules. In an aspect, the application server may be configured to transmit the validates API requests (commands) to the plurality of reporting servers (312). In an example, the application server is a software framework that provides an environment in which applications can run, regardless of the application itself or its function. The applications are dedicated to the efficient execution of procedures (programs, routines, scripts, etc.) for supporting construction of applications. The application server may act as a set of components accessible to a software developerthrough an API (application program interface) defined by a platform itself, for example.

[0120] The plurality of reporting servers (312) may be configured to generate a report having the validated commands. In an example, the plurality of reporting servers (312) may be configured to forward the generated report to the database management system (318-2), and the database (318-1). In an aspect, the database (318-1) may be a relational database. In an aspect, the database (318-1) may be coupled with non-relational database. The non-relational database is configured to store the data with Date wise partition. In an example, the non-relational database is a column-oriented non-relational database management system. In an aspect, the relational database may include a Table name. In another aspect, the database (318-1) may transmit the received data back to the plurality of the UEs through / via the plurality of servers and the load balancer (304). In an example, the database management system includes a Distributed File System (DFS). In an aspect, the nonrelational database may be configured to operate with the Distributed File System (DFS). DFS is a distributed file system that handles large data sets running on commodity hardware. In an aspect, a plurality of hive tables may be created on DFS partitioned data for further use cases and reporting. In an aspect, the database (318-1) may operate with the DFS (314) for performing the various spark jobs. The DFS operates as a distributed file system designed to run on commodity hardware. The DFS is fault-tolerant and designed to be deployed on low-cost, commodity hardware.

[0121] In an aspect, the plurality of API gateway servers (310) is linked to the plurality of service servers (or a plurality of micro services). In another aspect, the request / data from the plurality of service servers may be further transmitted to the database (318-1) and the database management system (318-2).

[0122] The virtual machine (VM) tool (320) may be configured to monitor and manage various applications running with the database (318-1). In an example, the VM tool (320) is a software used to manage and optimize the performance of applications running on the Virtual Machine (VM). The VM tools help developersand system administrators diagnose and solve problems related to application performance, memory management, and thread management.

[0123] In an aspect, an option “Create Recipe” is selected on an interfacing unit (212) (of CM Recipe Builder). One of the options such as Bulk Upload, Manual, and Parsing Rules is selected for the recipe creation. The recipe is created using one of the selections from Bulk Upload, Manual, and Parsing Rules. On selecting the manual upload option, the user can select a plurality of recipes available on the interfacing unit (212). After creation of recipe, the created recipe is visible in a recipe listing page. The user can download / delete / set as default the selected particular recipe using 3 dot option. The CM Recipe Builder (108) provides flexibility to the user to create recipes for different CM modules through bulk upload. A plurality of user actions is performed on multiple recipes after selection of the recipe from the interfacing unit (212).

[0124] In an implementation, the user can create recipes. The created recipes are submitted to the MS team without changing the user role. Multiple actions (e.g., Delete, send, Bulk upload) are added for multiple recipes. A “Set as Default” option is used to make a recipe being used by a module in a default manner. This helps the end user to define execution of method of procedure (MOP) in the recipe builder (108) one time only and same will be used for all requested operations using a workorder (WO) creation.

[0125] FIG. 4 illustrates an exemplary flow diagram (400) for creating the CM recipe, in accordance with an embodiment of the present disclosure.

[0126] FIG. 4 with reference to FIGs. 1-3, illustrates creation of the CM recipe using the system (108).

[0127] At step 402, selecting an option “Create Recipe” on the interfacing unit (212). In an aspect, the user may select “Create Recipe” option on the interfacing unit to create a new CM recipe.

[0128] At step 404, selecting one of the options such as bulk upload, manual, and parsing rules. In an aspect, the one or more options corresponding to the recipecreation is displayed on the interfacing unit (212). The one or more options comprises bulk upload, manual, and parsing rules.

[0129] At step 406, recipe is created using one selected option from bulk upload, manual, and parsing rules. In an aspect, the user may select one of recipe creation options. The recipe is created based on the selected recipe creation option.

[0130] At step 408, on selecting manual upload, the user can select one recipe from a plurality of recipes available on the coverage platform (CP). In an aspect, the user selects one recipe from the plurality of recipes in manual upload option.

[0131] At step 410, after creation of recipe, the created recipe is visible in a recipe listing page. In an aspect, the recipe is created based on the selected recipe option. The created recipe is displayed on the recipe listing page on the interfacing unit (212).

[0132] At step 412, the user can download / delete / set as default the selected particular recipe using 3 dot option. In an aspect, download / delete / set as default options are displayed on the interfacing unit (212). The user may select one recipe from the recipe listing page and perform one of download / delete / set as default options on the selected recipe. In the download option, the user may download the selected recipe. In the delete option, the user may delete the selected recipe. In the set as default option, the user may set the selected recipe as the default.

[0133] FIG. 5 illustrates an exemplary flow diagram (500) for performing recipe validation, in accordance with an embodiment of the present disclosure.

[0134] FIG. 5 with reference to FIG. 2 illustrates the flow for performing recipe validation using the interfacing unit (212) and the processing unit (214) of the system (108).

[0135] At step 502, selection of one of the options bulk upload / parsing rules. In an aspect, the interfacing unit (212) displays options such as bulk upload / parsing rules. Details corresponding to one or more recipes are filled in the bulk upload option by the user through the interfacing unit (212). In the parsing rules, the user inputs values corresponding to identifiers, commands, and parameters. The inputted values corresponding to identifiers, commands, and parameters are stored as parsingrules in the database. When the user requires details corresponding to the network entity in the network. The user enters a command such as get info corresponding to the network entity. The processing unit (214) parses the entered command. Then, the command and parameters corresponding to the network entity are parsed with the parsing rules. If the command and its parameters exist according to the parsing rules, then the values corresponding to the parameters are provided to the user.

[0136] At step 504, getting the recipe request. In an aspect, the user may send the recipe request on the interfacing unit (212).

[0137] At step 506, ingesting recipe details in the database (210). In an aspect, the details corresponding to the recipe are inputted by the user. The inputted details corresponding to the recipe are stored in the database (210). In an aspect, the details comprise the recipe name, the recipe type, the software version, the vendor, the network element (NE) type. In an example, the recipe name = 2211RR, the recipe type = random access network (RAN) parameter change (RPC), the software version = 12.2, the vendor = XYZ, the NE type = Macro base station.

[0138] At step 508, checking whether content of the recipe is valid. In an aspect, the content of the recipe is processed by the processing unit (214) to validate the content of the recipe. The processing of the recipe comprises checking of data format, all fields are filled or not, software version, NE type, etc.

[0139] At step 510, on detecting that the content of the recipe is valid, marking the recipe creation is successful. In an aspect, upon detecting the content of the recipe is valid, the recipe creation is marked as recipe created successfully. In the recipe listing page, the status of the recipe is displayed as “Created”.

[0140] At step 512, on detecting that the content of the recipe is not valid, marking the recipe creation is failed. In an aspect, upon detecting the content of the recipe is not valid, the recipe creation is marked as recipe not created. In the recipe listing page, the status of the recipe is displayed as “Failed”.

[0141] FIGs. 6A-6I illustrate exemplary user interfaces (600A-600I) for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0142] FIG. 6A-6I with reference to FIG. 2 for the CM recipe builder (108).

[0143] FIG. 6A illustrates an exemplary user interface (600A) for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0144] Referring to FIG. 6A, the user can create recipe by using a CM recipe creator. A link to that particular recipe creator page is as:

[0145] Coverage Platform (CP) Administration -> Module -> Configuration Management (CM) -> CM Recipe.

[0146] FIG. 6B illustrates an exemplary user interface (600B) to create the CM recipe for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0147] Referring to FIG. 6B, in order to create the CM recipe, the user hits the create recipe button. After hitting the create recipe button, new user interface (UI) window opens. The user provides various inputs via the UI window as shown in FIG. 6B.

[0148] In the UI, there are 3 options available such as a bulk upload, a manual, a parsing rule.

[0149] On bulk type selection, the user needs to fill downloaded template and then upload the template.

[0150] On selection of manual option, user needs to enter the information on the UI.

[0151] In the parsing rules, the user needs to enter identifiers, commands and parameters.

[0152] FIG. 6C illustrates an exemplary user interface (600C) with manual option selection for CM recipe creation for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0153] Referring to FIG. 6C, on selection of manual option, the user needs to enter into the UI page for further process.

[0154] The UI page of the manual option displays two options such as basic details and create recipe. Upon selecting the basic details option, the user needs to fill details such as recipe identifier (ID), recipe name, recipe type, software version, vendor.

[0155] In an example, a plurality of recipe types corresponding to the network (e.g., 4G and 5G) available in the user interface such as Remote Electrical Tilt (RET), Automatic Tilt optimization (ATO), Pkg upgrade, New Sector grow, New Carrier Grow, Service Barring, RAN Parameter Change (RPC).

[0156] In an example, for the RET, recipes for different operations are selected based on a recipe name, i.e., RET_ONLY, RET_WITH_TESTCMD and a recipe type is fixed as RET. In an example, for the ATO, recipes for the different operations are selected based on Recipe name, i.e., ATO_COMPLETE_RECIPE, ATO_RET_ONLY_RECIPE and ATO_TX_ATTEN_ONLY_RECIPE and the recipe type is ATO.

[0157] Furthermore, the recipe created is based on the following combination of fields:Recipe Name + Recipe Type + Software version + Vendor + NE Type.

[0158] FIG. 6D illustrates an exemplary user interface (600D) with manual option selection for CM recipe creation for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0159] After filling all details (such as recipe name, recipe type, software version, vendor, NE type), the user hits “Next” button. After hitting the “NEXT” button, another window with selection of New recipe / existing recipe option is shown in the user interface.

[0160] On clicking the “New Recipe” radio button, there is a “Type” option on the right side of the user interface. The type option comprises command and script.

[0161] In the new recipe, command and script options are shown. In the command option, the user may enter the command to create the recipe. In script option, the user may enter the script (i.e., series of commands) to create the recipe.

[0162] In the existing recipe option, the existing recipe is selected from the database (210).

[0163] FIG. 6E illustrates an exemplary user interface (600E) with “New recipe” with Command in manual option selection for CM recipe creation for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0164] On selecting “Command” type in the “New Recipe” option, the user is requested to fill all the necessary details and then proceed with the save button. The recipe statuses are an initialize status, a draft status, a failed status, and a created status. In an aspect, the initialize status refers to a status of the recipe after submission of the recipe. The draft status refers to a status of the recipe in which the recipe content validation is performed. The failed status refers to a status of the recipe in which the recipe content validation is failed. The created status refers to a status of the recipe in which the recipe content validation is successful.

[0165] FIG. 6F illustrates an exemplary user interface (600F) with created recipes for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0166] After submission of the Recipe, the recipe will be available at home page of the CM recipe in the user interface. As illustrated in FIG. 6F, all the recipe which are created will be visible on home page of CM Recipe as shown in the user interface.

[0167] As shown in FIG. 6F, 5 created recipes are displayed. For each of the created recipes, the user interface displays status of the recipe, recipe ID, recipe name, recipe type, recipe version, software (SW) version, recipe vendor and NE type.

[0168] The user can download all recipe listing using “Download” button from the recipe listing page in the user interface.

[0169] FIG. 6G illustrates an example user interface (600G) with recipe listing for the CM recipe builder (108), in accordance with an embodiment of the present disclosure.

[0170] As illustrated in FIG. 6G, the listing is having 3 Dot menu available on each of the recipe listing. Using the Dot menu, user can download, delete, set as default or remove as Default any particular selected recipe.

[0171] After selection of “Set as Default”, “Remove as Default” also available on the user interface.

[0172] FIG. 6H illustrates an example user interface (600H) with “Email functionality - bulk upload / individual creation of recipes”, in accordance with an embodiment of the present disclosure.

[0173] Notifications (e.g., Emails) in all the cases are sent to all active users on the role “CM Recipe Creator”. Only the email matter and attachment may change in case of bulk upload. The bulk option contains a notification to the user about the bulk uploading of recipes and attachments containing the recipe information.

[0174] FIG. 61 illustrates an example user interface (6001) with “Email functionality - multiple recipes send through “Send to MS”, in accordance with an embodiment of the present disclosure.

[0175] As illustrated in FIG. 61, the multiple recipes can be sent through “Send to MS”.

[0176] Further, after uploading the template, notifications on UI are as follows:• Incorrect file format- Error: File extension is not correct.• Incorrect number of sheets- Error: Please provide the correct number of sheets in the file. - One sheet without any specific name.• Error: SW Version or NE type is not present. While processing the Upload template:In an aspect, for any missing values, the user interface displays following errors:• Blank value in any header: Missing / incorrect header information in recipe details• Blank value in any recipe information: Missing / incorrect values found in recipe details.

[0177] If the recipe already exists, then getting following notification:“Recipe Id XXXXX already exists for Recipe Type RPC and Software version XXXX ”.

[0178] For Upload functionality:Share the new template for upload recipe having execution order.Add the notification messages.

[0179] The execution order column is also added in single recipe download sheet and recipe command sheet in the manual screen.

[0180] FIG. 7 illustrates another exemplary flow diagram of the method (700) for creating the CM recipe, in accordance with embodiments of the present disclosure.

[0181] FIG. 7 with reference to FIGs. 1 and 2 illustrate the method (700) for creating the CM recipe using the interfacing unit (212) and the processing unit (214) of the system (108).

[0182] At step 702, the method (700) comprises providing, by the interfacing unit (212), a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option.

[0183] At step 704, the method (700) includes receiving, by the interfacing unit (212), at least one recipe creation option selected by the user.

[0184] In an aspect, upon receiving the selection of the bulk upload option from the user, the processing unit (214) generates a template with one header corresponding to each of the one or more configuration parameters to be downloaded and filled out by the user. The interfacing unit (212) uploads a filled template with at least one value in each header corresponding to each of the one or more configuration parameters filled by the user. The processing unit (214) processes the filled template to create the CM recipe based on the received filled template. In an aspect, upon selecting the bulk upload option by the user, the template is generated. The template may be in spread sheet format (e.g., excel file). The template comprises one headercorresponding to each of the configuration parameters. The headers comprise a recipe name, a recipe type, a software version, a vendor, a network element type, an execution order, etc. The user fills data corresponding to each header. In bulk upload option, data corresponding to one or more recipes are filled. In an example, for recipe 1, data comprises recipe name = 2211RR, recipe type = random access network (RAN) parameter change (RPC), a software version = 12.2, vendor = XYZ, network element type = Macro. For recipe 2, data comprises recipe name = 1122RR, recipe type = software upgrade (SW_Upgrade), a software version = 12.4, vendor = ABC, network element type = Macro. For recipe 3, recipe name = 1212RR, recipe type = RAN parameter change (RPC), a software version = 12.6, vendor = PQR, network element type = Macro. The recipes (i.e., recipe 1, recipe 2 and recipe 3) are filled in the template. The filled template is uploaded / saved in the database (210). The processing unit (214) processes the filled template, i.e., checking its correctness, ensuring that all required fields are filled, and that the data meets the required format (e.g., dates, numbers, field format, etc.). If the filled template is in the correct format, the CM recipe is created for the bulk upload option. If the filled template is not in the correct format, an error is displayed to the user.

[0185] In an aspect, upon receiving the selection of the manual creation option, the interfacing unit (212) displays one or more input options. The one or more input options comprise command and script. The interfacing unit (212) receives at least one input option selected by the user. The processing unit (214) creates the CM recipe based on the at least one received input option. In an aspect, in the manual creation option, two subsequent options are displayed on the interfacing unit (212) (i.e., basic details and create recipe). In the basic details, fields such as a recipe name, a recipe type, a software version, a vendor, a NE type are to be filled by the user. In an example, the recipe type comprises a remote electrical tilt, an automatic tilt optimization, a package upgradation, a new sector grow, and a new carrier grow, etc.

[0186] In the create recipe of the manual creation option, the interfacing unit (212) provides two options i.e., new recipe or existing recipe. In the existing recipe, a previously created recipe is selected. In the new recipe, the interfacing unit (212)provides one or more input options (i.e., command, script. In the command input option, the user provides the commands corresponding to the recipe. In the command input option, the fields (such as NE type, execution order, sequence, command type, command syntax, identifier, etc.) are to be filled by the user. After filling the fields for command input option, the user may select create option on the interfacing unit (212). The processing unit (214) performs processing of the fields (i.e., validation of data format, number, etc.). After validation, the recipe is created based on fields.

[0187] In the script input option of the manual creation option, the user provides the script (series of commands) corresponding to the recipe. Based on the script, the recipe is created. After the filling the fields, the user interface displays the filled fields to the user. The interfacing unit (212) provides two options (i.e., “Save” or “Previous”). The user may select the previous option if the user wants to make changes in the filled fields. The user may select the save option if the filled fields are correct. After selecting the save option, the fields for the recipe are saved. The recipe is created based on the saved fields.

[0188] In an aspect, upon receiving the selection of the parsing rules option, the interfacing unit (212) receives one or more parameters selected by the user. The processing unit (214) parsing the one or more parameters selected by the user and creates the CM recipe based on the parsing. In the parsing rule, the user inputs values corresponding to identifiers, commands, and parameters. The inputted values corresponding to identifiers, commands, and parameters are stored as parsing rules in the database (210). In an example, user requires details corresponding to the cell in the network. The user enters a command such as get info corresponding to the cell. The processing unit parses the entered command. Then, the command and cell parameters are parsed with the parsing rules. If the command and its parameters exist according to the parsing rules, then the values corresponding to the parameters are provided to the user.

[0189] At step 706, the method (700) includes receiving, by the interfacing unit (212), one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user. The oneor more configuration parameters include a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, and a network element (NE) type.

[0190] At step 708, the method (700) includes creating, by the processing unit (214), the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters. In an aspect, the processing unit (214) creates the CM recipe based on the inputs corresponding to the one or more configuration parameters. The recipe created is based on the following combination of fields: Recipe Name + Recipe Type + Software version + Vendor + NE Type.

[0191] In an aspect, the method (700) further comprises displaying, by the interfacing unit (212), the created CM recipe on a recipe listing page. In the recipe listing page, all created CM recipes are displayed. Details corresponding to the created CM recipes are displayed on the listing page. The details corresponding to the created CM recipes comprise a status of the recipe, a recipe identifier, a recipe name, a recipe type, a software version, a recipe vendor, network element (NE) type, etc. The status of the created CM recipe comprises initialize, draft, created and failed.

[0192] In an aspect, the method (700) further comprises receiving, by the interfacing unit (212), at least one operation to be performed on the created CM recipe from the user. The at least one operation comprises download, delete, set as default, and remove as default. The processing unit performs the at least one received operation on the created CM recipe. In an operative aspect, a dot menu is available on each of the recipe in the recipe listing page. The dot menu shows one or more operation options such as download, delete, set as default and remove as default. The user may select any one of the operations for each recipe. The selected operation is performed on the recipe. The user may download all recipes in the recipe listing page using the download button. All recipes are downloaded in the spreadsheet (e.g., excel file). The spread sheet comprises details such as recipe status, recipe identifier, recipe name, recipe type, software version, recipe vendor, NE type, user details, created date and time, etc.

[0193] In an aspect, the method (700) further comprises validating, by the processing unit (214), the created CM recipe based on a set of predefined validation rules. In an aspect, the created CM recipe is processed to determine whether it adheres to the validation rules (i.e., file format, data format, all fields are filled, etc.). The validation rules are predefined by the user. The set of predefined validation rules is stored in the database (210). The processing unit (214) validates the created CM recipe by matching details of the created CM recipe to the set of predefined validation rules. If the details of the created CM recipe match with the set of predefined validation rules, then the created CM recipe is validated (i.e., the status of the recipe is set as “created”). If the details of the created CM recipe do not match with the set of predefined validation rules, then the created CM recipe is not validated (i.e., the status of the recipe is set as “Failed”).

[0194] In an aspect, the method (700) further comprises sending, by the processing unit (214), a notification corresponding to at least one created recipe to the user. The notification comprises a name of recipe creator, the status of the recipe and a link corresponding to the created recipe. In an aspect, the notification may be at least one of an electronic mail (e-mail), a short message service, or an in-app notification. The notification is sent to the user (i.e., creator of recipe) and other related users. The notification may be sent in one or more ways. The one or more ways comprise a notification for Bulk upload / Individual creation of recipes and a notification when the user (i.e., recipe creator) sends multiple recipes. In an aspect, the notification for the bulk upload option contains data about the bulk uploading of recipes and information about the recipes.

[0195] FIG. 8 illustrates an exemplary computer system (800) in which or with which embodiments of the present disclosure may be implemented.

[0196] As shown in FIG. 8, the computer system (800) may include an external storage device (810), a bus (820), a main memory (830), a read-only memory (840), a mass storage device (850), communication port(s) (860), and a processor (870). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (870) may includevarious modules associated with embodiments of the present disclosure. The communication port(s) (860) may be any of an RS-232 port for use with a modembased dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (860) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0197] The main memory (830) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (840) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (870). The mass storage device (850) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (850) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Lirewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0198] The bus (820) communicatively couples the processor (870) with the other memory, storage, and communication blocks. The bus (820) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (870) to the computer system.

[0199] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (820) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (860). Components described above are meantonly to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0200] The present disclosure provides technical advancement related to recipe creation for different configuration modules (CMs). This advancement addresses the limitations of existing solutions by providing system and method for configuration management (CM) recipe builder. Multiple recipes for different CM modules are created through a bulk upload option, manual and parsing rules. Multiple actions (e.g., delete, send, upload, set as default, remove as default, etc.) are performed on the created recipes through the interfacing unit. Status (e.g., initialize, draft, created, failed, etc.) of the created recipes is checked on a home page of the CM recipe builder. The user defines the execution method of the procedure (MOP) in the recipe builder one time only, and the same will be used for all requested operations using work order (WO) creation.

[0201] The exemplary computer system (800) is configured to execute a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for creating a configuration management (CM) recipe. The method comprises providing, by an interfacing unit, a plurality of recipe creation options to a user. The plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option. The method comprises receiving, by the interfacing unit, at least one recipe creation option selected by the user and receiving, by the interfacing unit, one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user, and creating, by a processing unit, the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

[0202] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions orexamples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.ADVANCEMENTS OF PRESENT DISCLOSURE

[0203] As is evident from the above, the present disclosure provides a system and a method for configuration management (CM) recipe builder. The recipe is created using one of the selections from Bulk Upload, Manual, and Parsing Rules. On selecting the manual upload option, the user can select a plurality of recipes available on the coverage platform (CP). After creation of recipe, the created recipe is visible in a recipe listing page. The user can download / delete / set as default the selected particular recipe using 3 dot option. The CM Recipe Builder provides flexibility to the user to create recipes for different CM modules through bulk upload. A plurality of user actions is performed on multiple recipes after selection of the recipe from the UI. A “Set as Default” option is used to make a recipe being used by a module in a default manner. This helps the end user to define execution of method of procedure (MOP) in the recipe builder one time only and same will be used for all requested operations using a workorder (WO) creation.

Claims

We claim:

1. A method (700) for creating a configuration management (CM) recipe, the method (700) comprising: providing (702), by an interfacing unit (212), a plurality of recipe creation options to a user, wherein the plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option; receiving (704), by the interfacing unit (212), at least one recipe creation option selected by the user; receiving (706), by the interfacing unit (212), one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user; and creating (708), by a processing unit (214), the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

2. The method (700) as claimed in claim 1 further comprising: displaying, by the interfacing unit (212), the created CM recipe on a recipe listing page.

3. The method (700) as claimed in claim 1 further comprising: receiving, by the interfacing unit (212), at least one operation to be performed on the created CM recipe from the user, wherein the at least one operation comprises download, delete, set as default, and remove as default; andperforming, by the processing unit (214), the at least one received operation on the created CM recipe.

4. The method (700) as claimed in claim 1, further comprising: generating, upon receiving the selection of the bulk upload option from the user, by the processing unit (214), a template having one header corresponding to each of the one or more configuration parameters to be downloaded and filled by the user; uploading, by the interfacing unit (212), a filled template having at least one value in each header corresponding to each of the one or more configuration parameters filled by the user; and processing, by the processing unit (214), the filled template to create the CM recipe based on the received filled template.

5. The method (700) as claimed in claim 1, further comprising: providing, upon receiving the selection of the manual creation option, by the interfacing unit (212), one or more input options, wherein the one or more input options comprise command and script; receiving, by the interfacing unit (212), at least one input option selected by the user; and creating, by the processing unit (214), the CM recipe based on the at least one received input option.

6. The method (700) as claimed in claim 1, further comprising: receiving, upon receiving the selection of the parsing rules option, by the interfacing unit (212), one or more parameters selected by the user;parsing, by the processing unit (214), the one or more parameters selected by the user; and creating, by the processing unit (214), the CM recipe based on the parsing.

7. The method (700) as claimed in claim 1, wherein the one or more configuration parameters comprise a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, a network element (NE) type and an execution order.

8. The method (700) as claimed in claim 1, further comprising: validating, by the processing unit (214), the created CM recipe based on a set of predefined validation rules.

9. The method as claimed in claim 1, further comprising: sending, by the processing unit (214), a notification corresponding to at least one created recipe to the user, wherein the notification comprises a name of recipe creator, a status of the recipe and a link corresponding to the created recipe, and wherein the status of the recipe is at least one of an initial state, a drafted state, a failed state, and a created state.

10. A recipe builder (108) for creating a configuration management (CM) recipe, the recipe builder (108) comprising: an interfacing unit (212) configured to: provide a plurality of recipe creation options to a user, wherein the plurality of recipe creation options comprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option;receive at least one recipe creation option selected by the user; and receive one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user; and a processing unit (214) coupled to the interfacing unit (212) and configured to: create the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

11. The recipe builder (108) as claimed in claim 10, wherein the interfacing unit(212) is configured to display the created CM recipe on a recipe listing page.

12. The recipe builder (108) as claimed in claim 10, wherein the interfacing unit (212) is configured to receive at least one operation to be performed on the created CM recipe from the user, wherein the at least one operation comprises download, delete, set as default, and remove as default; and the processing unit (214) is configured to perform the at least one received operation on the created CM recipe.

13. The recipe builder (108) as claimed in claim 10, wherein upon receiving selection of the bulk upload option from the user, the processing unit (214) is configured to generate a template having one header corresponding to each of the one or more configuration parameters to be downloaded and filled by the user;the interfacing unit (212) is configured to upload a filled template having at least one value in each header corresponding to each of the one or more configuration parameters filled by the user; and the processing unit (214) is configured to process the filled template to create the CM recipe based on the received filled template.

14. The recipe builder (108) as claimed in claim 10, wherein upon receiving the selection of the manual creation option, the interfacing unit (212) is configured to: provide one or more input options, wherein the one or more input options comprise command, script and library; and receive at least one input option selected by the user; and the processing unit (214) configured to create the CM recipe based on the at least one received input option.

15. The recipe builder (108) as claimed in claim 10, wherein upon receiving the selection of the parsing rules option, the interfacing unit (212) is configured to receive one or more parameters selected by the user; and the processing unit (214) configured to: process the one or more parameters selected by the user; and create the CM recipe based on the parsing.

16. The recipe builder (108) as claimed in claim 10, wherein the one or more configuration parameters comprise a recipe identity (ID), a recipe name, a recipe type, a recipe version, a software (SW) version, a recipe vendor, a network element (NE) type, and an execution order.

17. The recipe builder (108) as claimed in claim 10, wherein the processing unit (214) is configured to validate the created CM recipe based on a set of predefined validation rules.

18. The recipe builder (108) as claimed in claim 10, wherein the processing unit (214) is configured to send a notification corresponding to at least one created recipe to the user, wherein the notification comprises a name of recipe creator, a status of the recipe and a link corresponding to the created recipe, and wherein the status of the recipe is at least one of an initial state, a drafted state, a failed state, and a created state.

19. A user equipment (UE) (104) communicatively coupled with a recipe builder (108), the coupling comprises steps of: receiving, by the recipe builder (108), a connection request from the UE (104); sending, by the recipe builder (108), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the recipe builder (108) is configured to create a configuration management (CM) recipe, as claimed in claim 10.

20. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (700) for creating a configuration management (CM) recipe, the method (700) comprising: providing (702), by an interfacing unit (212), a plurality of recipe creation options to a user, wherein the plurality of recipe creation optionscomprises at least one or more of a bulk upload option, a manual creation option, and a parsing rules option; receiving (704), by the interfacing unit (212), at least one recipe creation option selected by the user; receiving (706), by the interfacing unit (212), one or more inputs corresponding to one or more configuration parameters corresponding to the at least one selected recipe creation option by the user; and creating (708), by a processing unit (214), the CM recipe based on the received one or more inputs corresponding to the one or more configuration parameters.

Images