System and method for managing parsing rules for network elements in a communication network

Abstract

The present disclosure relates to a system (102) and a method (600) for managing parsing rules for network elements in a communication network (104). The method (600) includes receiving input from a user equipment (UE) (106) for managing the parsing rules corresponding to the network elements; extracting at least one parsing rule corresponding to attributes associated with the network element from the received input; validating the at least one extracted parsing rule corresponding to the attributes based on predefined validation rules; determining a presence of the at least one parsing rule corresponding to the attributes in a database (208); managing at least one existing parsing rule corresponding to the attributes by performing a first set of operations if the at least one parsing rule corresponding to the attributes for the network element is present in the database (208).

Description

SYSTEM AND METHOD FOR MANAGING PARSING RULES FOR NETWORK ELEMENTS IN A COMMUNICATION NETWORKRESERVATION 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.FIELD OF DISCLOSURE

[0002] The present disclosure generally relates to the field of wireless communication networks. More particularly, the present disclosure relates to a system and method for managing parsing rules for network elements in a communication network.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 “Parsing Rules,” as used hereinafter in the specification, refers to a set of predefined or user-defined instructions or conditions that govern how data is extracted, interpreted, and structured from input sources, such as configuration documents (e.g., markup language files such as configuration management extensible markup language (CM XML) files). In the context of network elements like evolved NodeB (eNodeB), the parsing rules define how specific parameters, commands, and configuration details (e.g., from a Parameter List Descriptor (PLD)) are identified, validated, and mapped for further processing.

[0005] The term “Commands”, used hereinafter in the specification, refers to executable instructions generated by a system to perform specific operations on configuration parameters of a network element, such as an eNodeB. The commands are derived based on validated parsing rules and are used to retrieve, modify, add, delete, activate, deactivate, or reset parameters associated with the network element.

[0006] The term ‘Configuration Management (CM) Module”, used hereinafter in the specification, refers to a specialized component within a network management system responsible for handling configuration and reconfiguration of network elements, such as eNodeBs or 5G nodes. The CM module manages a lifecycle of configuration parameters by facilitating a parsing of configuration data, validation and application of parsing rules, and generation and execution of commands.

[0007] The term “CM XML files,” used hereinafter in the specification, refers to structured data files used in mobile networks (e.g., 5G) to store and transfer configuration parameters of network elements, such as eNodeBs. The CM XML files follow amarkup language (e.g., extensible markup language (XML)) standards and contain detailed information about network element’s configuration, including hardware details, software versions, radio parameters, and service-related settings.

[0008] The term “XML”, used hereinafter in the specification, refers to a markup language designed to store, transport, and structure data in a human- readable and machine -readable format. The XML defines a set of rules for encoding documents in a structured way, allowing users to create custom tags based on the data requirements.

[0009] The term “network elements,” used hereinafter in the specification, refers to individual hardware or software components within a telecommunication network that perform specific network functions. The network elements include but are not limited to, radio base stations (e.g., eNodeBs, next-generation (gNodeBs)), routers, switches, gateways, firewalls, and core network nodes. Each networkelement is responsible for managing specific aspects of data transmission, signal processing, and network control, playing a crucial role in maintaining end-to-end connectivity, quality of service, and network operations across mobile and fixed- line infrastructure.

[0010] The term “Parameter List Descriptor (PLD),” used hereinafter in the specification, refers to a structured representation or dataset that outlines and catalogs various configuration parameters associated with a network element. The PLD defines a set of parameters, their respective attributes, allowable values, constraints, and relationships. The PLD serves as a reference for interpreting, extracting, and managing parameters within configuration documents (e.g., CM XML files), enabling a system to apply parsing rules and execute parameter-related commands accurately in line with network management and configuration operations.

[0011] The term “Parameters,” used hereinafter in the specification, refers to control variables associated with network elements that define operational characteristics, behaviors, and settings. The parameters are essential for controlling and optimizing the performance of the network element, and the parameters are extracted, modified, or validated using parsing rules and parameter commands within network management systems.

[0012] The term “identifiers,” used hereinafter in the specification, refers to unique codes assigned to network elements or parameters to distinguish them within a network or database.

[0013] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0014] 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 onlyto enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0015] Wireless communication technology has evolved significantly over the past few decades. The first generation (1G) was based on analog technology, offering only voice services. The second generation (2G) introduced text messaging and basic data services. The third generation (3G) brought high-speed internet access, mobile video calls, and location-based services. The fourth generation (4G) revolutionized communication with significantly faster data speeds, broader network coverage, and enhanced security protocols. Currently, the ongoing deployment of fifth generation (5G) technology promises even higher data rates, ultra-low latency, and the ability to connect a vast number of devices simultaneously. As network technology has evolved, a task of managing network elements and configuration parameters of the network elements has grown increasingly complex.

[0016] In mobile communication networks, managing the configuration parameters for the network elements, such as evolved NodeBs (eNBs), is essential for ensuring optimal network performance and service continuity. These configuration parameters are retrieved or modified through a parsing of configuration documents (e.g., configuration management (CM) extensible markup language (XML) files) and execution of specific commands. Conventional systems rely on backend-driven approaches, where the parsing rules and parameter command logic are predefined and static. The conventional system often lacks the flexibility to adapt to dynamic network conditions, varying software versions, or vendor-specific customizations.

[0017] Furthermore, any modification or addition of the parsing rules or commands requires backend development and deployment cycles, leading to inefficiencies such as slower response times to network changes, delayed rollouts, and increased risk of configuration errors. Additionally, the conventional systems lack robust mechanisms to automatically adapt parsing and command logic to aspecific software version of the network element, leading to parsing failures or misinterpretation of parameters when the network element versions are upgraded or differ across the network. Another challenge is the increased operational complexity when integrating new network elements, as the static nature of these systems makes it difficult to scale and accommodate diverse network configurations. Also, the reliance on manual intervention in backend processes increases the potential for human error, further complicating the management of network configurations.

[0018] Thus, there is a need for an improved system and method that can effectively manage and optimize network element configurations by enabling dynamic, user-defined parsing rules and command logic.OBJECTIVES OF THE PRESENT DISCLOSURE

[0019] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0020] An objective of the present disclosure is to provide a user-friendly interface that allows users to define parsing rules and commands from a front-end user interface (UI).

[0021] Another objective of the present disclosure is to enable extraction and modification of network parameters associated with a parameter list descriptor (PLD) in a network element, by applying user-defined parsing rules and commands, while ensuring compatibility and accuracy through a precheck process that verifies a version of the network element prior to execution.

[0022] Yet another objective of the present disclosure is to ensure seamless integration of user-defined parsing rules and commands across all CM modules, enhancing accuracy and efficiency of retrieving or modifying parameters in a system in relation to configuration documents (e.g., markup language files such as CM XML files) of network elements.

[0023] Yet another objective of the present disclosure is to enable dynamic adaptability to network elements by implementing parsing and command logic tailored to a specific software version of a network element, thus reducing misconfigurations and increasing operational flexibility.

[0024] Another objective of the present disclosure is to streamline a process of defining, validating, and applying parsing rules and commands, eliminating the need for backend-driven code changes and reducing the operational effort required for network configuration management.

[0025] Other objectives 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.SUMMARY

[0026] In an exemplary embodiment, the present invention discloses a method for managing parsing rules for at least one network element in a communication network. The method includes receiving, by a receiving unit, input from a user equipment (UE) pertaining to managing the parsing rules corresponding to the at least one network element. The method further includes extracting, by a processing unit, at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input. The method further includes validating, by the processing unit, the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The method further includes upon validation of the at least one extracted parsing rule, determining, by the processing unit, a presence of the at least one parsing rule corresponding to the at least one attribute in a database. The method further includes managing, by the processing unit, at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database.

[0027] In some embodiments, the at least one attribute includes an identifier, a parameter and a command.

[0028] In some embodiments, the at least one network element is identified based on a unique identifier and an associated software version.

[0029] In some embodiments, the first set of operations includes updating, deleting, and replacing.

[0030] In some embodiments, the method includes adding, by the processing unit, the at least one validated parsing rule corresponding to the at least one attribute as a new parsing rule if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is absent in the database.

[0031] In some embodiments, the method includes executing, by the processing unit, at least one command for performing a second set of operations on at least one parameter for the at least one network element based on the at least one parsing rule.

[0032] In some embodiments, the second set of operations includes retrieving, modifying, adding, deleting, activating, deactivating, and resetting to default values.

[0033] In some embodiments, the one or more predefined validation rules includes syntax validation, version compatibility check, range and constraint validation.

[0034] In an exemplary embodiment, a system for managing parsing rules for at least one network element in a communication network is disclosed. The system includes a receiving unit configured to receive input from a user equipment (UE) pertaining to managing the parsing rules corresponding to at least one network element. The system further includes a processing unit communicatively coupled to the receiving unit. The processing unit is configured to receive the input from the receiving unit. The processing unit includes an extraction module configured to extract at least one parsing rule corresponding to at least one attribute associatedwith the at least one network element from the received input. The processing unit further includes a validation module configured to validate the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The processing unit further includes a rule determination module configured to determine a presence of the at least one parsing rule corresponding to the at least one attribute in a database upon validation of the at least one extracted parsing rule. The processing unit further includes a managing module configured to manage at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database.

[0035] In some embodiments, the at least one attribute includes an identifier, a parameter and a command.

[0036] In some embodiments, the at least one network element is identified based on a unique identifier and an associated software version.

[0037] In some embodiments, the first set of operations includes updating, deleting, and replacing.

[0038] In some embodiments, the processing unit includes a rule creation module configured to add the at least one validated parsing rule corresponding to the at least one attribute as a new parsing rule if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is absent in the database.

[0039] In some embodiments, the processing unit includes an execution module configured to execute at least one command for performing a second set of operations on at least one parameter for the at least one network element based on the at least one parsing rule.

[0040] In some embodiments, the second set of operations includes retrieving, modifying, adding, deleting, activating, deactivating, and resetting to default values.

[0041] In some embodiments, the one or more predefined validation rules includes syntax validation, version compatibility check, range and constraint validation.

[0042] In an exemplary embodiment, a user equipment (UE) communicatively coupled with a communication network is disclosed. The coupling includes steps of receiving, by the communication network, a connection request from the UE. The coupling further includes sending, by the communication network, an acknowledgment of the connection request to the UE. The coupling further includes transmitting a plurality of signals in response to the connection request. The UE is connected with a system configured to manage parsing rules for at least network element in the communication network. The system includes a receiving unit configured to receive input from a user equipment (UE) pertaining to managing the parsing rules corresponding to at least one network element. The system further includes a processing unit communicatively coupled to the receiving unit. The processing unit is configured to receive the input from the receiving unit. The processing unit includes an extraction module configured to extract at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input. The processing unit further includes a validation module configured to validate the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The processing unit further includes a rule determination module configured to determine a presence of the at least one parsing rule corresponding to the at least one attribute in a database upon validation of the at least one extracted parsing rule. The processing unit further includes a managing module configured to manage at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule correspondingto the at least one attribute for the at least one network element is present in the database.

[0043] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing parsing rules for at least one network element in a communication network. The method includes receiving, by a receiving unit, input from a user equipment (UE) pertaining to managing the parsing rules corresponding to the at least one network element. The method further includes extracting, by a processing unit, at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input. The method further includes validating, by the processing unit, the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The method further includes upon validation of the at least one extracted parsing rule, determining, by the processing unit, a presence of the at least one parsing rule corresponding to the at least one attribute in a database. The method further includes managing, by the processing unit, at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database.

[0044] 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.BRIEF DESCRIPTION OF DRAWINGS

[0045] 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 theprinciples 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0046] FIG. 1 illustrates an exemplary network architecture for implementing a system for managing parsing rules for network elements in a communication network, in accordance with embodiments of the present disclosure.

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

[0048] FIG. 3 illustrates an exemplary system architecture for managing the parsing rules, in accordance with an embodiment of the present disclosure.

[0049] FIG. 4 illustrates an exemplary flow diagram of a process for employing the parsing rules in the system, in accordance with an embodiment of the present disclosure.

[0050] FIGS. 5A-5F illustrates exemplary user interfaces for managing the parsing rules, in accordance with an embodiment of the present disclosure.

[0051] FIG. 6 illustrates a flowchart of a method for managing the parsing rules for the network elements in the communication network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 7 illustrates an exemplary computer system in which, or with which, the system and the method of the present disclosure may be implemented.

[0053] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - System104- Communication Network106-1, 106-2... 106-N - User Equipment108-1, 108-2... 108-N - Users200 - Receiving Unit202 - Memory204 - Interfacing Unit206 - Processing Unit208 - Database210 - Validation Module212 - Extraction Module214 - Rule Determination Module216 - Managing Module218 - Rule Creation Module220 - Execution Module300 - System Architecture302 - Web Portals304 - Load Balancer306 - Web Servers308 - Application Servers310 - Gateway Servers312 - Reporting Servers314 - Distributed File System (DFS)316 - Service Servers318-1 - Relational Database Management System318-2 - Non-Relational Database Management System320 - Monitoring Unit322 - Execution Unit400 - Process Flow500A-500F - User Interfaces600 - Method700 - Computer system710 - External storage device720 - Bus730 - Main memory740 - Read only memory750 - Mass storage device760 - Communication port(s)770 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0054] In the following description, for the purposes of explanation, various specific details are set forth 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.

[0055] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0056] 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 to avoid obscuring the embodiments.

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

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

[0059] 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 features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0060] The terminology used herein is to describe 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 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.

[0061] As used herein, an “electronic device” or “portable electronic device” or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device can receive and / or transmit one or parameters, performing fiinction(s),communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP -enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

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

[0063] Aspects of this disclosure are directed to a system and a method for managing dynamic parsing rules and parameter commands for network elements, such as evolved Node B (eNBs), within a mobile communication network. Conventional configuration management systems rely on static, backend-driven parsing rules and command templates that are hardcoded into a system. Such rigid systems often fail to accommodate changing requirements of the network elements, including varying software versions and vendor-specific customizations. As a result, such systems are prone to inefficiencies, extended response times to networkchanges, and increased risks of misconfigurations when updating or modifying network parameters.

[0064] The present disclosure introduces a user-driven, front-end configurable system that allows users to define the parsing rules and parameter commands specific to attributes and software versions of the network elements. The system validates the user-defined parsing rules and dynamically applies the corresponding parsing rules and command execution tailored to configuration documents (e.g., markup language files such as configuration management (CM) extensible markup language (XML) files) of the network elements. This approach offers significant improvements over traditional backend-heavy models by providing the users with direct control over the parsing rules and command definitions. The present disclosure ensures a more adaptable configuration management system that reduces human errors, enhances process efficiency, and ensures compatibility across different software versions of the network elements.

[0065] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 7.

[0066] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (102) for managing parsing rules for network elements in a communication network (104), in accordance with embodiments of the present disclosure.

[0067] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or one or more user equipment (UE) (106-1, 106-2. . . 106- N) that may be associated with one or more users (108-1, 108-2... 108-N) and the system (102) in an environment. In an embodiment, the one or more UE (106-1, 106-2... 106-N) may be communicated to the system (102) through the communication network (104). A person of ordinary skill in the art will understand that the one or more UE (106-1, 106-2. . . 106-N) may be individually referred to as the UE (106) and collectively referred to as the UE (106). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “UE” may beused interchangeably throughout the disclosure. Although three UE (106) are depicted in the FIG. 1, however any number of the UE (106) may be included without departing from the scope of the ongoing description. Similarly, a person of ordinary skill in the art will understand that the one or more users (108-1, 108- 2... 108-N) may be individually referred to as the user (108) and collectively referred to as the users (108).

[0068] In an embodiment, the UE (106) may include smart devices operating in a smart environment, for example, an internet of things (loT) system. In such embodiment, the UE (106) may include but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting systems, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users (108) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (106) may include, but not be limited to, intelligent multi-sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0069] In an embodiment, the UE (106) 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 head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a global positioning system (GPS) device, a laptop, 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.

[0070] In an embodiment, the UE (106) may include, but is not limited to, any electrical, electronic, electro-mechanical, or equipment, or a combination of one ormore of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a general-purpose computer, a desktop, a personal digital assistant, a mainframe computer, or any other computing device. In another embodiment, the UE (106) 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 (108) or the entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (106) may not be restricted to the mentioned devices and various other devices may be used.

[0071] Referring to FIG. 1, the UE (106) may communicate with the system (102) through a set of executable instructions residing on any operating system. In an embodiment, the set of executable instructions may include, but not limited to, a user interface (UI) application, an agent, a software client, and so forth, configured to facilitate interaction between the UE (106) and the system (102). The set of executable instructions may be configured to transmit user inputs, receive system responses, and display outputs associated with defining parsing rules, configuring commands for parameters, or executing network management tasks.

[0072] In an embodiment, the UE (106) may communicate with the system (102) through the communication network (104) for sending or receiving various types of data. In an exemplary embodiment, the data may be, but not limited to, configuration data (e.g., parsing rules for a specific network element), operational commands (i.e., commands related to managing the network elements, such as retrieving, updating, deleting, activating the parameters), network element information (e.g., network element identifiers, software versions), and so forth. In an embodiment, the communication network (104) may include at least one of a 5G network, a 6G network, or the like. The communication network (104) may enable the UE (106) to communicate with other devices in the network architecture (100) and / or with the system (102). The communication network (104) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the communication network (104) may be implemented as,or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a virtual private network (VPN), the Internet or the like.

[0073] In an embodiment, the communication network (104) may include, by way of example but not limitation, 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. The communication network (104) may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, the internet, the 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. In an embodiment, the system (102) may be connected to backend servers (not shown).

[0074] In an embodiment, the UE (106) is communicatively coupled with the communication network (104). The communication network (104) may receive a connection request from the UE (106). The communication network (104) may send an acknowledgment of the connection request to the UE (106). The UE (106) may transmit a plurality of signals in response to the connection request.

[0075] Although the 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).

[0076] FIG. 2 illustrates an exemplary block diagram of the system (102) for managing the parsing rules for the network elements, in accordance with embodiments of the present disclosure.

[0077] FIG. 2, with reference to FIG. 1, illustrates the system (102), which includes a receiving unit (200), a memory (202), an interfacing unit (204), a processing unit (206), and a database (208). The processing unit (206) includes a validation module (210), an extraction module (212), a rule determination module (214), a managing module (216), a rule creation module (218) and an execution module (220).

[0078] The receiving unit (200) is configured to receive input from the UE (106) through the communication network (104), where the input pertains to the management of the parsing rules corresponding to the network elements. In an embodiment, the input may be provided by the user (108) through a front-end user interface (UI) presented on the UE (106), such as, but not limited to, a web-based dashboard, a graphical user interface (GUI), a command-line interface (CLI), and so forth. For example, through the UI, the user (108) may define and upload structured data files (e.g., XML, JSON, CSV files) containing the parsing rules, parameter definitions (commands), network element identifiers (e.g., eNB IDs, site codes), software versioning information, parameter-command mappings associated with the network elements, and so forth. In another example, the user (108) may upload configuration documents, such as a CM file of the network element, which may be in formats such as, but not limited to, XML, JSON, and so forth. The CM file may include current configuration data of the network element, such as, but not limited to, parameters, values, hardware / software version details, network settings, and so forth. In an embodiment, the configuration document may be stored in the database (208). In another embodiment, the CM document may be provided by the user (108) in the input. Alternatively, the user (108) may directly input custom parsing logic and parameter-specific commands relevant to the network elements. In an exemplary embodiment, the parsing rules may define how the system (102) should read and interpret the configuration document that includes theconfiguration and parameters of the network elements. In an embodiment, the parsing rules may be designed to handle configuration data (parameter name and corresponding values) from different equipment manufacturers despite variations in formats and command structures. In an exemplary embodiment, the parsing rules automatically processes the parameters (e.g., frequency bands, power levels) and organizes the parameters into a structured dictionary. This eliminates manual entry, reducing errors and improving efficiency. For example, if the configuration document defines the parameter as <parameter name = “freq band” value =”78” / >, the parsing rules extract and store it in a parsed dictionary as {“freq band”: “78”}. In an embodiment, the extracted parameter data may be stored in the database (208) that maintains configuration of various network elements.

[0079] The commands may be instructions on how the system (102) should process the parameters from the configuration document (e.g., retrieve, update, or change the parameters) based on the parsing rules.

[0080] In an embodiment, the user (108) may specify the parsing rules for attributes such as, but not limited to, identifiers, parameters, and associated commands, along with version-specific details associated with each network element. In other words, the input provided by the user (108) may represent how the attributes of the network elements should be parsed, validated and executed within the system (102). In an embodiment, the network elements may include, but are not limited to, evolved NodeBs (eNBs), base stations, small cells, macro cells, distributed antenna systems (DAS), or other similar components present within the communication network (104). The network elements may be identified based on unique identifiers and software versions. For example, the network element, such as the eNB, may be identified using its unique identifier (e.g., eNB ID: 12345) and software version (e.g., v21.5.3), which are extracted from the input.

[0081] In an embodiment, the receiving unit (200) may be configured to receive the input through secure communication channels, such as, but not limited to, representational state transfer application programming interfaces (REST APIs),web portals, dedicated user interfaces, and so forth. Further, the receiving unit (200) may be configured to transmit the received input to the processing unit (206) for further validation and execution within the system (102).

[0082] The memory (202) may be a non-transitory computer-readable storage medium configured to store instructions or routines. As used herein, the term “instructions” may refer to a sequence of commands that are written in a programming language and may be executed by the processing unit (206) to perform tasks associated with the system (102). The memory (202) may include any non-transitory storage device including, for example, but not limited to, a volatile memory such as a random-access memory (RAM) or a non-volatile memory such as an erasable programmable read-only memory (EPROM), a flash memory, and the like . Embodiments of the present invention are intended to include or otherwise type of the memory (202) including known related art and / or later developed technologies.

[0083] In an embodiment, the interfacing unit (204) may include a variety of interfaces, such as the interfaces for data input and output devices (RO), storage devices, and the like. The interfacing unit (204) may facilitate communication through the system (102). The interfacing unit (204) may also provide a communication pathway for various other units / modules of the system (102).

[0084] In an embodiment, the database (208) may be a configuration database that may offer functionality to manage, capture, store, and retrieve the parsing rules, parameter definitions, parameter-command mappings, network element identifiers, versioning information (i.e., version details of the network elements or the configuration document) and so forth. For example, the parsing rules defines how configuration is interpreted and processed (e.g., extract <parameter name = X> value 43, validate range, and update the value of the parameter). The parameter definitions specify attributes of configuration parameters, such as, data type, permissible values, dependencies, and so forth. The parameter-command mappings establish relationships between the parameters and the corresponding commandsfor retrieval or modification (e.g., parameter X - command: GET X enB ID). The network identifiers include unique identifiers such as eNB IDs, site codes, or any other network element-specific references. The versioning information maintains version details of network elements and configuration documents to ensure compatibility during parsing and execution.

[0085] The database (208) is designed to interact seamlessly with other modules of the system (102), such as the validation module (210), the extraction module (212), the rule determination module (214), the managing module (216), the rule creation module (218) and the execution module (220), to support functionality of the system (102) effectively. The database (208) may store the data that may be generated as a result of functionalities implemented by any of the modules of the processing unit (206). In an embodiment, the database (208) may be separate from the system (102).

[0086] The modules are controlled by the processing unit (206), which executes the instructions retrieved from the memory (202). The processing unit (206) further interacts with the interfacing unit (204) to facilitate user interaction and to provide options for managing and configuring the system (102). The processing unit (206) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions.

[0087] The validation module (210) is communicatively coupled to the receiving unit (200), to receive the input from the receiving unit (200). The validation module (210) may be configured to validate the input, whether the input is in the form of files or data. The validation module (210) may be configured to validate key elements associated with the received input, such as, but not limited to, file headers (e.g., file type, creation date, source ID), mandatory fields (e.g., network element identifiers, software versions), structural integrity (e.g., XML schema compliance, tag hierarchy consistency, and so forth). In an exemplaryembodiment, the validation module (210) may be configured to validate the file headers to ensure that the file is correctly identified and properly structured according to a required format, such as XML, JSON, or other predefined types.

[0088] In addition to the file headers, the validation module (210) may also be configured to ensure that all mandatory fields and sections are present within the input. In an embodiment, the mandatory fields may be predefined based on the identifiers of the network element (eNodeB ID, site code, cell ID, location information, or hardware / software version) or configuration parameters that are essential for accurate parsing. For example, if certain parameters are required for the configuration of the specific network element, the validation module (210) ensures that the required parameters are included in the input. In an embodiment, the validation module (210) may also be configured to check for any required parameter values or attributes, confirming that no essential data is missing. As an example, if the eNodeB ID is missing from the input, the validation module (210) flags an error, as it is required for uniquely identifying the network element. Similarly, the validation module (210) verifies that the software version details match the expected format; if missing or incorrect, the parsing process is halted. In an embodiment, if the input fails any part of validation checks, the validation module (210) may be configured to mark the input as invalid and generate a specific error message, prompting the user (108) to correct the issue before proceeding. In another embodiment, if the input passes all validation checks, the validation module (210) may be configured to generate a signal indicating a valid input. In such an embodiment, the validation module (210) may be configured to transmit the generated signal to the extraction module (212).

[0089] The extraction module (212) is communicatively coupled to the validation module (210) and receives the signal from the validation module (210). The extraction module (212) is configured to extract the parsing rules and the commands from the validated input based on the received signal. In an embodiment, the extraction module (212) may be configured to analyze the validated input and extract at least one parsing rule corresponding to the attributes associated with thenetwork elements. In an exemplary embodiment, the extraction module (212) may be configured to extract the parsing rule by identifying and isolating relevant components from the input, such as attribute identifiers (e.g., parameter names, tags), parameter values, command types, and conditional logic or patterns specified by the user (108).

[0090] In such an exemplary embodiment, the extraction module (212) may utilize parsing techniques (e.g., XML / JSON parsers, regular expressions, tokenization) to locate and retrieve the parsing rules from the received input. For instance, if the input is an XML document, the extraction module (212) may be configured to navigate through XML nodes to identify and extract specific tags and associated values that define how parameters of the corresponding network element should be processed or configured. In an alternative embodiment, the extraction module (212) may also be configured to extract version-specific rules. In other words, the extraction module (212) may be configured to extract the parsing rules that may be applied to a particular software version or a specific type of the network element. The extraction module (212) may be configured to transmit the extracted parsing rules to the validation module (210) for further processing.

[0091] Further, in an embodiment, the extraction module (212) may be configured to extract the commands from the validated input. In an exemplary embodiment, the extraction module (212) may be configured to identify parameterspecific command definitions provided within the input, such as, but not limited to, command types, an execution syntax, parameter dependencies, any associated conditions, and so forth. The extraction module (212) may be configured to apply similar parsing techniques (e.g., pattern matching, rule-based extraction) to locate command blocks within the input. For example, in the case of the XML document, the extraction module (212) may be configured to parse command-specific XML nodes to extract executable command templates associated with each parameter. The extracted executable commands may then be organized based on the type of the network elements and corresponding software versions, ensuring compatibility with the specific network element. For example, a command to set a parametervalue on eNodeB-A (version 12.1) is different from a command to set a parameter value on eNodeB-B (version 15.0). The extraction module (212) may be configured to transmit the extracted commands to the validation module (210).

[0092] The validation module (210) is configured to validate the extracted commands against predefined rules (e.g., command syntax rules, parameter range checks) specific to the system (102). In an exemplary embodiment, the validation module (210) may be configured to check whether each command is correctly formatted according to a predefined syntax and structure. For example, the predefined syntax and structure may include verifying that each command includes the required parameters, operators, and values, ensuring that the command adheres to the expected format for execution. In another exemplary embodiment, the validation module (210) may be configured to cross-reference the extracted commands against a set of known and valid command templates that specify a necessary command structure for the corresponding network element. In yet another exemplary embodiment, the validation module (210) may be configured to validate that the extracted commands are appropriate for the specific software version or type of network element indicated in the input. For example, a command such as “CHG PAR A 50” may only be valid for the network elements of the type gNodeB with software release 18.x and may be flagged as invalid for LTE eNodeBs running older releases.

[0093] In an embodiment, if the extracted commands fail any validation checks, the validation module (210) may be configured to mark the extracted commands as invalid and generate an error notification or log entry indicating the reason for invalidation (e.g., syntax error, version mismatch).

[0094] In another embodiment, if the extracted commands successfully pass all validation checks, the validation module (210) may be configured to store the validated commands in the database (208) (e.g., configuration command repository) for subsequent processing, such as execution of the commands on the network elements.

[0095] The validation module (210) is also configured to validate the extracted parsing rules corresponding to the at least one attribute to ensure that the parsing rules are accurate, compliant and suitable for execution with the communication network (104). In one exemplary embodiment, the validation module (210) may be configured to first detect and verify the software version of the network element as part of a precheck process prior to performing any parsing rule validation. In an exemplary embodiment, the validation module (210) may be configured to automatically extract the software version of the network element from the input associated with the network element.

[0096] In another embodiment, the validation module (210) may be configured to retrieve the software version of the network element from the database (208) that stores version-related information corresponding to the network element. Once the software version is extracted, the validation module (210) may be configured to validate the extracted parsing rules using a set of predefined validation rules, including, but not limited to, syntax validation, version compatibility check, range and constraint validation, and so forth. The version compatibility check ensures that the parsing rules are suitable and valid for the extracted software version (e.g., certain commands or parameters may only be valid for specific eNB software releases) of the network element. The syntax validation ensures that the parsing rules follow a correct structural format and required syntax, such as correct XML tags, attribute names, or key-value pairs necessary for proper parsing. The range and constraint validation verifies that the parameter values defined within the parsing rules fall within acceptable limits and comply with the system (102) or network constraints. Thereby, the validation module (210) is configured to ensure that the parsing rules are both syntactically correct and tailored to the specific network element version’s configuration requirements.

[0097] The validation module (210) may be configured to transmit the validated parsing rules to the rule determination module (214). The rule determination module (214) is communicatively coupled to the validation module (210) and receives the validated parsing rules from the validation module (210).The rule determination module (214) is configured to determine a presence of the validated parsing rules corresponding to the at least one attribute in the database (208). In an exemplary embodiment, the rule determination module (214) may be configured to query the database (208) using a combination of elements extracted from each validated parsing rule. The element may include, but is not limited to, network element identifiers (e.g., unique IDs, site codes), software version details, specific parameter-command mappings within the parsing rule, and the like. The rule determination module (214) may be configured to use the extracted elements to identify corresponding records in the database (208) associated with the corresponding network element. Based on the identification, the rule determination module (214) may be configured to determine whether the parsing rule is already present in the database (208) for the corresponding network element. In an embodiment, if a corresponding parsing rule is present in the database (208), the rule determination module (214) may be configured to generate a first signal indicating the presence of the parsing rule in the database (208). The rule determination module (214) may be configured to transmit the generated first signal to the managing module (216). In another embodiment, if the corresponding parsing rule is not present in the database (208), then the rule determination module (214) may be configured to generate a second signal indicating the absence of the parsing rule in the database (208). In such embodiment, the rule determination module (214) may be configured to transmit the generated second signal to the rule creation module (218).

[0098] The managing module (216) is communicatively coupled to the rule determination module (214) and receives the first signal from the rule determination module (214). The managing module (216) is configured to manage an existing parsing rule corresponding to the attributes based on the received first signal. The managing module (216) is configured to manage the existing parsing rule by performing a first set of operations. The first set of operations may be, but not limited to, updating, deleting, replacing, and so forth. In other words, the managingmodule (216) may be configured to update the existing parsing rule with the latest validated parsing rule in the database (208).

[0099] The rule creation module (218) is communicatively coupled to the rule determination module (214) and receives the second signal from the rule determination module (214). The rule creation module (218) is configured to add the at least one validated parsing rule corresponding to the attribute as anew parsing rule in the database (208) based on the received second signal. This process ensures that the database (208) maintains up-to-date and version-appropriate parsing rules aligned with the specific network element configurations.

[0100] The execution module (220) is communicatively coupled to the database (208). The execution module (220) is configured to execute at least one command for performing a second set of operations on at least one parameter associated with the network element based on the parsing rules present in the database (208). The execution module (220) operates based on the validated parsing rules available in the database (208). The second set of operations may include, but is not limited to, retrieving, modifying, adding, deleting, activating, deactivating, resetting the at least one parameter to default values, and so forth. In an embodiment, the execution module (220) is configured to interpret a command logic defined within the validated parsing rules and execute the corresponding commands on the parameters of the corresponding network elements.

[0101] In an exemplary embodiment, the execution module (220) may be configured to map each parameter-command pair from the validated parsing rule to a corresponding action on the network element. In an embodiment, the execution module (220) may be further configured to establish a communication with the network element to perform instructed operations in real-time or as part of a scheduled process. The commands may be executed in accordance with the software version of the network element and specific configuration formats defined in the parsing rules to ensure compatibility and correctness during network element configuration changes or maintenance activities.

[0102] FIG. 3 illustrates an exemplary system architecture (300) for managing the parsing rules, in accordance with an embodiment of the present disclosure.

[0103] FIG. 3, with reference to FIG. 1 and FIG. 2, illustrate the system architecture (300), that includes a plurality of web portals (302), a load balancer (304), a plurality of web servers (306), a plurality of application servers (308), a plurality of gateway servers (310), a plurality of reporting servers (312), a distributed fde system (DFS) (314), a plurality of service servers (316), a relational database management system (318-1), a non-relational database management system (318-2), a monitoring unit (320), and an execution unit (322).

[0104] The web portals (302) may be configured to receive at least one configuration update command from the user (108) 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 update the configuration of a network element (e.g., eNB), the network operator may apply / update a plurality of parsing rules, a plurality of network element identifiers, and a plurality of parameter values. In another example, the network operator may update the configuration of the network element based on a software version already running on the network element. In an example, the network operator may update the software version running on the network element. The web portals (302) may be configured to receive a plurality of application programming interface (API) request(s) from the plurality of UEs (106). In an aspect, the API requests may get hit when an event related to any node configuration update request is detected from the UE (106).

[0105] 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 web server (306). The load balancer (304) may be configured to distribute the plurality of API requests across the plurality of web servers (306), ensuring no single server is overburdened. The load balancer (304) may beconfigured to distribute incoming network traffic across the web servers (306). The load balancer (304) may be configured to dynamically adjust the distribution of API requests to ensure optimal resource utilization. The load balancer (304) may be configured to monitor the health and performance of each web server (306) and direct 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 (306) based upon a number of parameters and forward the received data to the determined web server (306). In an example, the number of parameters may include a number of active requests served by each web server (306) and a threshold of requests to be served.

[0106] In an aspect, the load balancer (304) may be a dedicated load balancer. In an example, the load balancer (304) may be configured to use POST as a request method supported by a hypertext transfer protocol (HTTP) used by a world wide web (WWW). The POST request method requests the web server (306) to accept the data enclosed in a body of a 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. In another aspect, when a specific server of the plurality of web servers (306) gets heavily loaded, the load balancer (304) may direct the incoming request to other web servers (306). In another aspect, the plurality of web servers (306) may be configured in such a way that when a specific server fails, other servers may take over to enable high availability (HA).

[0107] The plurality of web servers (306) is software and hardware that uses the HTTP and other protocols to respond to the API requests made over the WWW. The main job of the web server (306) is to display website content by storing, processing, and delivering web pages to the users (108). Besides the HTTP, the plurality of web servers (306) also supports a simple mail transfer protocol (SMTP) and a file transfer protocol (FTP), used for electronic (e)-mail, file transfer and storage. The web server hardware is connected to the internet and allows data to be exchanged with other connected devices, while a web server software controls how the user (108) access hosted file. In an aspect, the plurality of web servers (306)may be configured to process the received API requests and generate a plurality of processed API requests. 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).

[0108] 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 plurality of application servers (308) 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 (308) may be configured to transmit the validated API requests (commands) to the plurality of reporting servers (312). In an example, the application server (308) 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 the construction of applications. The application server (308) may act as a set of components accessible to a software developer through an API (application program interface) defined by a platform itself.

[0109] 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 DFS (314) and the relational database management system (318-1). In an aspect, the the relational database management system (318-1) may be coupled with the DFS (314). The DFS (314) is configured to store the data with Date wise partition. For example, the DFS (314) is a column-oriented non-relational database management system. In an aspect, the relational database management system (318-1) may include a Table name. In another aspect, the relational database management system (318-1) may transmit the received data back to the plurality of the UEs (106) through / via the plurality of servers and the load balancer (304). The DFS (314) 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 andreporting. In an aspect, the relational database management system (318-1) may operate with the DFS (314) for performing various spark jobs. The DFS (314) operates as a distributed fde system designed to run on commodity hardware. The DFS (314) is fault-tolerant and designed to be deployed on low-cost, commodity hardware.

[0110] In an aspect, the plurality of API gateway servers (310) is linked to the plurality of service servers (316) (or aplurality of micro services). In another aspect, the request / data from the plurality of service servers (316) may be further transmitted to the DFS (314) and the non-relational database management system (318-2).

[0111] The monitoring unit (320) may be configured to monitor and manage various applications running with the relational database management system (318- 1). For example, the monitoring unit (320) may be a Java virtual machine (JVM) tool. The JVM tool is a software used to manage and optimize the performance of Java applications running on a java virtual machine (JVM). The JVM tools help developers and system administrators to diagnose and solve problems related to Java application performance, memory management, and thread management.

[0112] The execution unit (322) may be configured to execute a job to read the configuration of the network element. In an example, the execution unit (322) may be a spark cluster. In an aspect, the execution unit (322) may be configured to employ a parallel processing framework that supports in-memory processing to boost the performance of big -data analytic applications.

[0113] In an operative aspect, the system (102) may be configured to employ following functionalities: The system (102) enables the users (108) to define the parsing rules through the UI, allowing for network element-specific configurations. The parsing rules facilitate a structured interpretation of configuration parameters, performance metrics, and control signals associated with the network elements. Once the parsing rules are defined, the system (102) applies the parsing rules to extract parameters from the PLD, focusing on key aspects related to 5Gtechnologies. The extracted parameters may include 5G-specific characteristics, such as, but not limited to, millimeter-wave frequency settings, massive MIMO (Multiple-Input Multiple-Output) configurations, network slicing details, and other advanced radio or core network features. Subsequently, based on the extracted parameters, the system (102) is configured to generate appropriate commands or actions aligned with an operational context of the 5G network elements. The commands may be used to improve network performance, meet standards, or enable features like quality of service (QoS) control or dynamic resource allocation.

[0114] Prior to parsing and command execution, the system (102) performs a compatibility check to ensure successfully interfacing with the target network element and associated 5G network infrastructure. The compatibility check includes validating a software version of the network element and confirming the availability of required resources to execute the parsing rules and commands in compliance with 5G protocols and standards.

[0115] Furthermore, the system (102) adapts its parsing and command execution logic dynamically based on the identified software version and capabilities of the network element. Since different versions of the network elements may introduce new features, updated protocols, or optimizations, the system (102) ensures that its parsing logic and generated commands are version- aware. This approach allows the system (102) to function efficiently across diverse network element deployments while maintaining compatibility with evolving 5G network architectures.

[0116] FIG. 4 illustrates an exemplary flow diagram of a process (400) for employing the parsing rules in the system (102), in accordance with an embodiment of the present disclosure.

[0117] FIG. 4, with reference to, FIG. 1, FIG. 2 and FIG. 6, illustrates the flow diagram of the process (400) for employing the parsing rules in the system (102).

[0118] At step (402), the process (400) includes receiving a command request from the user (108) for managing the parsing rules and the parameter-specificcommands related to the network elements. The command request may include uploading the document or providing data through the UI. The document includes the parsing rules and the parameter-specific commands corresponding to attributes such as the identifier, the parameter, and the command for the selected network element.

[0119] At step (404), the process (400) includes validating the mandatory fields and file header details of the document associated with the received command request. In an aspect, validating the mandatory fields may include one or more criteria, for example, checking the presence and correctness of mandatory attributes such as the identifier, parameter, and command fields within the document, along with validating the file header structure to ensure compliance with a predefined format or schema required for parsing and further processing.

[0120] At step (406), if the command request fails to meet a validation criterion at step (404), the process (400) marks the upload command request as invalid and terminates further processing of the command request.

[0121] At step (408), the process (400) includes validating the commands that passed the previous header and mandatory field validation. This step includes validating each command against predefined rules or logic specific to the system (102). The validation may include verifying whether the command is valid for the corresponding network element or the software version of the network element, checking whether a command syntax complies with system-specific constraints. For example, a valid CHG PARAMETER command follows a correct syntax, such as CHG PARAMETER TX POWER == 20. Similarly, a validRTRV PARAMETER command like RTRV PARAMETER BANDWIDTH == 100 allows the system (102) to fetch the specified parameter value without errors.

[0122] At step (410), the process (400) includes identifying and marking the commands that fail the validation performed in step (408) as invalid. For example, if a CHG PARAMETER or RTRV PARAMETER command uses incorrectsyntax (e.g., missing an operator in THRESHOLD = 50 instead of THRESHOLD == 50), then the corresponding command is marked as invalid.

[0123] At step (412), the process (400) includes storing the validated input commands into the database (208). In other words, if all the input commands of the command request pass the validation in step (408), then the validated input commands may be stored into the database (208).

[0124] At step (414), the process (400) includes checking whether the parsing rules already exist in the database (208) for the validated commands. In an aspect, process (400) may include querying the database (208) to verify if the predefined parsing rule is available to parse the configuration document of the network element for extracting the attributes corresponding to the validated commands. If the parsing rule exists in the database (208), the process (400) proceeds to step (416) and if the parsing rule does not exist in the database (208), the process (400) proceeds to step (418).

[0125] At step (416), the process (400) includes updating the existing parsing rules and proceeds to step (420). This step may include revising the syntax, structure, or logic of the existing parsing rules to accommodate new network configurations, software version changes, or updated operational standards. Once the parsing rules are updated, the process (400) proceeds to step (420).

[0126] At step (418), the process (400) includes ingesting new parsing rules and proceeds to step (420), where the newly defined parsing rules that were previously not present in the database (208) are accepted and integrated. After successful ingestion, the process (400) advances to step (420).

[0127] At step (420), the process (400) includes storing the updated or ingested parsing rules in the database (208). This step ensures that the modified or newly added parsing rules are persistently saved for future retrieval and application during parsing and command execution workflows.

[0128] FIGS. 5A-5F illustrates exemplary user interfaces (500A-500F) for managing the parsing rules, in accordance with an embodiment of the present disclosure.

[0129] FIGS. 5A-5F, with reference to FIG. 1, FIG. 2 and FIG. 6, illustrates the user interfaces (500A-500F).

[0130] FIG. 5A illustrates a user interface (500A) showing a parsing rule update tab, in accordance with an embodiment of the present disclosure. In an aspect, the user interface (500A) may be configured to enable the user (108) to update the parsing rules for the identifiers. In an embodiment, the user (108) may be able to reach a parsing rule update tab using a path, “XYZ (in an example, hosting platform)AdministrationModule managementConfiguration Management Parsing Rule.”

[0131] The user interface (500A) shows 3 options (tabs) under the parsing rule update tab, i.e., an Identifier List, a Command List and a Parameter List.

[0132] In an example, when the user (108) clicks on the “Identifier List”, a list of types of network elements with details of software versions is visible to the user (108). As soon as the user (108) clicks on any of the above three tabs, the user (108) is migrated to a listing page, which may further include the type of network element (eNB) and software version tab. After clicking on the Identifier List and specific software (SW) version tab, a new window may be available, as shown in FIG. 5B.

[0133] As shown in FIG. 5A, the user interface (500A) may include two options (i.e., a download option and an add option) at a top right comer of the user interface (500A). The download option enables the user (108) to download an entire list of present contents of a software package version by selecting a check box against each software version. In an embodiment, a downloaded sheet (report) may contain entire contents of multiple packages in a single sheet. The users (108) may select multiple package (PKG) versions and download them. Further, the add option enables the user (108) to add the software version and the type of network element(eNB), which further has contents of every parameter. In an aspect, every software package has 3 dots for a sub-menu, as shown in the user interface (500A).

[0134] FIG. 5B illustrates a user interface (500B) displaying a drop-down list with various options to be performed corresponding to the network element, in accordance with an embodiment of the present disclosure. As shown in FIG. 5B, various options may include a replicate option, an activate option, a deactivate option, a remove option, a deletion option, and so forth. Using the replicate option, the user (108) may replicate an existing software version to a newer software version, and the user (108) may enter the software PKG version in a window that may pop up and then submit to replicate. The pop-up window may contain all previous details, and the software PKG version field may be used as user input. For example, replicating the PKG 7.0.0 to PKG 7.5.0.

[0135] Using the activate option, the user (108) may activate the parsing of a particular software PKG version, and using the deactivate option, the user (108) may deactivate the software PKG version when the software PKG becomes obsolete, and the PKG may be deactivated to stop the parsing.

[0136] The delete option may be available for all individual entries, and using the delete option, the user (108) may be able to delete entries associated with the identifier.

[0137] FIG. 5C illustrates a user interface (500C) displaying multiple properties of a selected network element, in accordance with an embodiment of the present disclosure. When the user (108) clicks on the software PKG version of the selected network element, the user interface (500C) may appear, showing multiple rows related to the software PKG version (e.g., 9.0.0-03). The software PKG version may include various fields such as a parameter family (general naming not required for input), a parameter list descriptor (PLD), an identifier name, an actual value range (including Extensible Markup Eanguage (XML) values), a local site manager (LSM) to XML map (showing LSM to XML mapping), status, and vendor’s name.

[0138] FIG. 5D illustrates a user interface (500D) displaying a drop-down list with various actions corresponding to multiple properties of the selected network element, in accordance with an embodiment of the present disclosure. As shown in FIG. 5D, each row may include four options: edit, delete, activate, and deactivate, along with a description option. In an embodiment, selecting the edit option may open a dialog box containing all column fields, allowing the user (108) to modify and save an updated entry. The activate and deactivate options enable or disable the entry for the respective PLD. In an aspect, bulk activation and deactivation may be performed on multiple identifier entries, and bulk deletion may also be carried out for selected identifier entries. In an aspect, a dialog box may appear to confirm the action of the user (108) before proceeding.

[0139] The user interface (500D) further includes four options at the top right comer, such as a download option, a history option, an add option, and an upload option. The download option enables the user (108) to download a complete list of contents for selected software package versions by selecting corresponding checkboxes. Downloaded files may consolidate the contents of multiple software packages into a single sheet, enabling a bulk download functionality. In an aspect, a search option is also provided that is limited to searching for the software package versions and does not extend to internal package contents. The history option displays records of any modifications or deletions made to software package names, as shown in the corresponding window. For the download option, the parameter family field is mandatory, while for the upload, the parameter family field is optional. All other fields are mandatory in both cases.

[0140] In an aspect, the history option displays a record of all changes made to the entries by authorized users (108). However, downloading the history log is available to all users (108), regardless of their modification rights. The upload option enables the user (108) to upload a template having selected options as per the format. The add button enables the user (108) to add a new identifier entry into the table. In an aspect, a pop-up window may appear, displaying all the column fields, such as the parameter family (optional), the PLD name (mandatory), theidentifier with range, actual value range (as per LSM values), the LSM to XML map, the software version and the vendor’s name.

[0141] In an aspect, the delete and edit options may be restricted to the users (108) who have been authorized to make such changes. All other users (108) may not be able to see the delete and edit options. Using the description option, the user (108) may add a description corresponding to the identifier so that it is easy for each authorized user (108) to gain insight into current settings.

[0142] FIG. 5E illustrates a user interface (500E) showing parameters associated with the network element, in accordance with an embodiment of the present disclosure. When the user (108) clicks on the parameter list option, as shown in FIG. 5A, the user interface (500E) is displayed. Upon selecting the software PKG version, the user interface (500E) presents various fields, such as the parameter family, the PLD, the parameter name, the parameter value (which includes XML values), the software version, and the vendor’s name. For each row, action options such as edit, delete, activate, deactivate, and so forth are provided. In an aspect, clicking the edit option opens a dialog box containing the mentioned fields, enables the user (108) to modify values and saves the entry. The activate and deactivate options allow the user (108) to enable or disable a specific parameter for the corresponding PLD. In an aspect, dialog boxes may appear wherever required to seek user confirmation. In an aspect, the user interface (500E) may allow single or multiple delete actions, single or multiple activate actions, or deactivate actions.

[0143] Further, the user interface (500E) may include additional functionalities, such as, but not limited to, a history button, bulk activate and deactivate options, an add button, bulk upload and download options, a delete option, an edit option, a free search option, a horizontal or vertical scroll option, and so forth.

[0144] In an aspect, the history button enables the user (108) to view a log of all changes made to the entries by any authorized user (108). However, the optionto download the log history is available to all users (108), regardless of modification rights.

[0145] Further, in an aspect, the bulk activate and deactivate options allow the user (108) to enable or disable multiple parameters simultaneously, while a bulk delete option enables the user (108) to select and remove multiple parameter entries at once. Pop-up windows may appear when performing bulk activate and deactivate operations or deleting single or multiple entries, providing a user-friendly interface for user confirmation.

[0146] In an aspect, the add button allows the user (108) to insert new parameters into the table. When the add button is clicked, a pop-up window appears, displaying all relevant column fields, such as the parameter family, the PLD name, the parameter name, the parameter value, the software version, and the vendor’s name. While defining the parameter, the user (108) may also specify retrieve (RTRV) and change (CHG) commands, which determine how the parameter is to be retrieved or modified, including an associated command syntax. The command syntax incorporates the identifier, which is derived from XML values within the identifier list and applied according to configurations read from the configuration management documents.

[0147] Further, in an aspect, bulk upload and download options are provided, allowing the user (108) to either download specific fields by selecting the corresponding fields or download the entire parameter list if no fields are selected. All row information is available for download; however, during bulk upload, the parameter family field is optional.

[0148] In an aspect, the delete and edit options may be restricted to the user (108) with necessary authorization. In other words, the users (108) without modification rights will not have access to or be able to view the delete and edit options.

[0149] Further, the free search option may be provided, which allows the user (108) to search for the parameter names within entries related to the specificsoftware PKG version. In an aspect, the horizontal and vertical scroll options enable the user (108) to navigate through all the fields and rows effectively. The scrolling capability is crucial and is incorporated across all pages to ensure seamless data management.

[0150] FIG. 5F illustrates a user interface (500F) displaying commands associated with the selected software version, in accordance with an embodiment of the present disclosure. When the user (108) selects the command list option, as shown in FIG. 5A, the user interface (500F) is displayed. The user interface (500F) presents a list of available commands, such as the retrieve (RTRV) and change (CHG) commands, corresponding to the selected software version.

[0151] FIG. 6 illustrates a flowchart of a method (600) implemented by the system (102) for managing the parsing rules for the network elements in the communication network (104), in accordance with an embodiment of the present disclosure.

[0152] FIG. 6, with reference to FIG. 1 and FIG. 2, illustrates the method (600) for managing the parsing rules by using the receiving unit (200) and the processing unit (206) of the system (102).

[0153] At step (602), the method (600) includes receiving, by the receiving unit (200), the input from the UE (106) pertaining to managing the parsing rules corresponding to the at least one network element. The input may be provided by the user (108) through the front-end UI of the UE (106). The input may include, but not limited to, the parsing rules (e.g., parameter values must be within a predefined range, parameters should follow a specific format, and so forth) and the parameterspecific commands (change command, retrieve command, delete command, and so forth). In an embodiment, the network elements may include, but are not limited to, evolved NodeBs (eNBs), base stations, small cells, macro cells, distributed antenna systems (DAS), or other similar components present within the communication network infrastructure. The network elements may be identified based on the unique identifier and the software versions.

[0154] At step (604), the method (600) includes extracting, by the processing unit (206), the parsing rules corresponding to the attributes associated with the network elements from the received input. The attributes may be, but are not limited to, identifiers (e.g., eNB_ID == 7890), parameters (e.g., BANDWIDTH == 20 MHz) and commands (e g., CHG PARAMETER BANDWIDTH). In an embodiment, the method (600) includes extracting the parameter-specific commands associated with the network elements from the received input.

[0155] At step (606), the method (600) includes validating, by the processing unit (206), at least one extracted parsing rule corresponding to the attributes based on predefined validation rules. This step includes first detecting and verifying the software version of the network element as part of the precheck process before performing any parsing rule validation. This step further includes automatically or manually extracting the software version from the input data (containing the CM file) or from the database (208) associated with the corresponding network element. Once the software version is extracted, step (606) includes validating the extracted parsing rules using the set of predefined validation rules, including but not limited to, syntax validation, version compatibility check, range and constraint validation, and so forth. Step (606) also may include validating the extracted commands against the predefined rules (e.g., command syntax rules, parameter range checks, mandatory field presence, allowed operators) that are specific to the system (102).

[0156] At step (608), the method (600) includes upon validation of the at least one extracted parsing rule, determining, by the processing unit (206), the presence of the at least one parsing rule corresponding to the at least one attribute in a database (208). This step includes querying the database (208) using the combination of the elements extracted from each validated parsing rule to identify corresponding records in the database (208) associated with the network element. The element may include, but is not limited to, network element identifiers (e.g., unique IDs, site codes), software version details, specific parameter-command mappings present within the parsing rule, and so forth. In an embodiment, based on the identification, if the at least one parsing rule is present in the database (208), themethod (600) may proceed to a step (610). In another embodiment, the method (600) includes adding, by the processing unit (206), the at least one validated parsing rule corresponding to the attribute as a new parsing rule in the database (208), if the at least one parsing rule is absent in the database (208).

[0157] At step (610), the method (600) includes managing, by the processing unit (206), at least one existing parsing rule corresponding to the attributes by performing the first set of operations. The first set of operations includes, but is not limited to, updating, deleting, replacing, and so forth.

[0158] Upon validating and updating the parsing rules in the database (208), the method (600) includes executing, by the processing unit (206), the at least one command for performing a second set of operations on at least one parameter associated with the network element based on the parsing rules present in the database (208). The second set of operations may include, but is not limited to, retrieving, modifying, adding, deleting, activating, deactivating, and resetting the at least one parameter to default values.

[0159] FIG. 7 illustrates an exemplary computer system (700) in which, or with which, the system (102) and the method (600) of the present disclosure may be implemented. As shown in FIG. 7, the computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read-only memory (740), a mass storage device (750), a communication port (760), and a processor (770). A person skilled in the art will appreciate that the computer system (700) may include more than one processor (770) and the communication ports (760). The processor (770) may include various modules associated with embodiments of the present disclosure.

[0160] In an embodiment, the external storage device (710) may be any device that is commonly known in the art, such as, but not limited to, a memory card, a memory stick, a solid-state drive, a hard disk drive (HDD), and so forth.

[0161] In an embodiment, the bus (720) may be communicatively coupled with the processor(s) (770) with the other memory, storage, and communication blocks.The bus (720) may be, e.g., a peripheral component interconnect (PCI) / PCI Extended (PCI-X) bus, a small computer system interface (SCSI), a 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 (770) to the computer system (700).

[0162] In an embodiment, the main memory (730) may be a random-access memory (RAM), or any other dynamic storage device commonly known in the art. The Read-only memory (740) 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 (770).

[0163] In an embodiment, the mass storage device (750) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, a parallel advanced technology attachment (PATA) or a serial advanced technology attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having universal serial bus (USB) and / or Firewire interfaces), one or more optical discs, redundant array of independent disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0164] Further, the communication port (760) may be any of an RS-232 port for use with a modem-based 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 (760) may be chosen depending on the communication network (104), such a local area network (LAN), wide area network (WAN), or any network to which the computer system (700) connects.

[0165] Optionally, operator and administrative interfaces, e.g., a display, a keyboard, a joystick, and a cursor control device, may also be coupled to the bus (720) to support a direct operator interaction with the computer system (700). Other operator and administrative interfaces may be provided through networkconnections connected through the communication port (760). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (700) limit the scope of the present disclosure.

[0166] The exemplary computer system (700) is configured to execute a computer program product including 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 (600) for managing parsing rules for at least one network element in a communication network (104). The method (600) includes receiving, by a receiving unit (200), input from a user equipment (UE) (106) pertaining to managing the parsing rules corresponding to the at least one network element. The method (600) further includes extracting, by a processing unit (206), at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input. The method (600) further includes validating, by the processing unit (206), the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The method (600) further includes upon validation of the at least one extracted parsing rule, determining, by the processing unit (206), a presence of the at least one parsing rule corresponding to the at least one attribute in a database (208). The method (600) further includes managing, by the processing unit (206), at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database (208).

[0167] In an exemplary embodiment, a user equipment (UE) (106) communicatively coupled with a communication network (104) is disclosed. The coupling includes steps of receiving, by the communication network (104), a connection request from the UE (106). The coupling further includes sending, by the communication network (104), an acknowledgment of the connection request to the UE (106). The coupling further includes transmitting a plurality of signals inresponse to the connection request. The UE (106) is connected with a system (102) configured to manage parsing rules for at least network element in the communication network (104). The system (102) includes a receiving unit (200) configured to receive an input from the UE (106) pertaining to manage the parsing rules corresponding to the at least one network element. The system (102) further includes a processing unit (206) communicatively coupled to the receiving unit (200). The processing unit (206) is configured to receive the input from the receiving unit (200). The processing unit (206) includes an extraction module (212) configured to extract at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input. The processing unit (206) further includes a validation module (210) configured to validate the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules. The processing unit (206) further includes a rule determination module (214) configured to determine a presence of the at least one parsing rule corresponding to the at least one attribute in a database (208) upon validation of the at least one extracted parsing rule. The processing unit (206) further includes a managing module (216) configured to manage at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database (208).

[0168] The present disclosure provides a technical advancement related to managing and optimizing parsing rules and parameter commands for network elements within a communication network. This advancement overcomes the limitations of conventional systems by introducing a flexible, user-driven solution for defining the parsing rules and commands tailored to specific network element attributes and software versions. The disclosed system enables real-time configuration management by allowing users to define the parsing rules and commands through an intuitive front-end interface, which are then validated anddynamically applied based on network element’s configuration documents (e.g., CM XML data).

[0169] By providing the users with the ability to adapt the parsing rule and parameter command execution to the evolving needs of the network, the system significantly improves operational efficiency, reduces risks of misconfigurations, and ensures compatibility across varying software versions of the network elements. This advancement results in a more agile and scalable network management solution, ultimately enhancing network performance, and optimizing configuration workflows.

[0170] 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 or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.ADVANCEMENTS OF THE PRESENT DISCLOSURE

[0171] The present disclosure described herein above has several technical advantages as follows:

[0172] The present disclosure provides a system and method for dynamically defining and managing parsing rules and parameter commands for network elements, overcoming limitations of conventional static backend-driven approaches and enhancing user flexibility.

[0173] The present disclosure enables real-time validation and dynamic application of parsing rules and commands based on specific attributes and software versions of network elements, ensuring accurate and adaptive configuration management.

[0174] The present disclosure reduces operational inefficiencies by empowering users with the ability to define parsing logic and parameter commands through an intuitive front-end interface, streamlining network configuration processes and improving response times to changes in network conditions.

[0175] The present disclosure minimizes the risk of misconfigurations, human errors, and delays in configuration updates by automating the validation and application of parsing rules, ensuring consistent and reliable operation across varying network element versions.

[0176] The present disclosure provides a more agile and scalable network management solution, resulting in enhanced compatibility, reduced operational costs, and optimized network performance across different network deployments and software environments.

Claims

CLAIMS1. A method (600) for managing parsing rules for at least one network element in a communication network (104), the method (600) comprising steps of: receiving, by a receiving unit (200), input from a user equipment (UE) (106) pertaining to managing the parsing rules corresponding to the at least one network element; extracting, by a processing unit (206), at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input; validating, by the processing unit (206), the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules; upon validation of the at least one extracted parsing rule, determining, by the processing unit (206), a presence of the at least one parsing rule corresponding to the at least one attribute in a database (208); and managing, by the processing unit (206), at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database (208).

2. The method (600) as claimed in claim 1, wherein the at least one attribute comprises an identifier, a parameter and a command.

3. The method (600) as claimed in claim 1, wherein the at least one network element is identified based on a unique identifier and an associated software version.

4. The method (600) as claimed in claim 1, wherein the first set of operations comprises updating, deleting, and replacing.

5. The method (600) as claimed in claim 1, further comprising adding, by the processing unit (206), the at least one validated parsing rule corresponding to the at least one attribute as a new parsing rule if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is absent in the database (208).

6. The method (600) as claimed in claim 1, further comprising executing, by the processing unit (206), at least one command for performing a second set of operations on at least one parameter for the at least one network element based on the at least one parsing rule.

7. The method (600) as claimed in claim 6, wherein the second set of operations comprises retrieving, modifying, adding, deleting, activating, deactivating, and resetting to default values.

8. The method (600) as claimed in claim 1 , wherein the one or more predefined validation rules comprises syntax validation, version compatibility check, range and constraint validation.

9. A system (102) for managing parsing rules for at least one network element in a communication network (104), the system (102) comprising: a receiving unit (200) configured to receive input from a user equipment (UE) (106) pertaining to managing the parsing rules corresponding to the at least one network element; a processing unit (206) communicatively coupled to the receiving unit (200), wherein the processing unit (206) is configured to receive the input from the receiving unit (200), wherein the processing unit (206) comprises: an extraction module (212) configured to extract at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input;a validation module (210) configured to validate the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules; a rule determination module (214) configured to determine a presence of the at least one parsing rule corresponding to the at least one attribute in a database (208) upon validation of the at least one extracted parsing rule; and a managing module (216) configured to manage at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database (208).

10. The system (102) as claimed in claim 9, wherein the at least one attribute comprises an identifier, a parameter and a command.

11. The system (102) as claimed in claim 9, wherein the at least one network element is identified based on a unique identifier and an associated software version.

12. The system (102) as claimed in claim 9, wherein the first set of operations comprises updating, deleting, and replacing.

13. The system (102) as claimed in claim 9, wherein the processing unit (206) comprises a rule creation module (218) configured to add the at least one validated parsing rule corresponding to the at least one attribute as a new parsing rule if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is absent in the database (208).

14. The system (102) as claimed in claim 9, wherein the processing unit (206) further comprises an execution module (220) configured to execute at leastone command for performing a second set of operations on at least one parameter for the at least one network element based on the at least one parsing rule.

15. The system (102) as claimed in claim 14, wherein the second set of operations comprises retrieving, modifying, adding, deleting, activating, deactivating, and resetting to default values.

16. The system (102) as claimed in claim 9, wherein the one or more predefined validation rules comprises syntax validation, version compatibility check, range and constraint validation.

17. A user equipment (UE) (106) communicatively coupled with a communication network (104), the coupling comprises steps of: receiving, by the communication network (104), a connection request from the UE (106); sending, by the communication network (104), an acknowledgment of the connection request to the UE (106); and transmitting a plurality of signals in response to the connection request, wherein the UE (106) is connected with a system (102) configured to manage parsing rules for at least network element in the communication network (104), as claimed in claim 8.

18. 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 execute a method (600) for managing parsing rules for at least one network element in a communication network (104), the method (600) comprising steps of: receiving, by a receiving unit (200), input from a user equipment (UE) (106) pertaining to managing the parsing rules corresponding to the at least one network element;extracting, by a processing unit (206), at least one parsing rule corresponding to at least one attribute associated with the at least one network element from the received input; validating, by the processing unit (206), the at least one extracted parsing rule corresponding to the at least one attribute based on one or more predefined validation rules; upon validation of the at least one extracted parsing rule, determining, by the processing unit (206), a presence of the at least one parsing rule corresponding to the at least one attribute in a database (208); and managing, by the processing unit (206), at least one existing parsing rule corresponding to the at least one attribute by performing a first set of operations if the at least one parsing rule corresponding to the at least one attribute for the at least one network element is present in the database (208).

Images