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

METHOD AND SYSTEM FOR NETWORK CONFIGURATION VERIFICATION USING A GOLDEN CONFIGURATION TEMPLATE (GCT)
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network configuration verification systems. More particularly, embodiments of the present disclosure relate to methods and systems for network configuration verification using a Golden Configuration Template (GCT).
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In the field of telecommunication, a network configuration is a process of assigning one or more network settings, one or more policies, one or more flows and one or more controls. Further, a correct network configuration is important to support a flow of network traffic via

the network. Additionally, accurate configurations in the network not only enhance security but also enhance stability. After, completion of the network configuration process in the respective network, the configurations are validated or verified to ensure that all the network configurations operate error-free and without any issues.
[0005] In the conventional era, a manual approach was followed by an administrator for validating or verifying that all the network configurations operate as desired, however, the manual approach does not provide accurate results when the network expands. Further, with the development in telecommunications, several network configuration verification systems and devices were introduced to ensure that the network configurations operate error-free and without any issue. The network configuration verification systems and devices conduct one or more tests such as a test for routing black holes, a test for node and end point isolation, a test for load-balanced paths in the network to identify issues associated with the network configurations. However, the currently available network configuration verification systems and devices consume a lot of time and additional resources to conduct all the tests to identify the issues. Moreover, some of the currently available network configuration verification systems and devices compare all the network configurations associated with the network with a set of parameters to identify the issues, which ultimately requires additional time and additional resources.
[0006] Hence, the existing network verification systems and devices are time-consuming and operate on one or more error-prone tasks such as a comparison of one or more parameters related to the configuration of network with a plurality of templates or pre-define configuration lists, especially when dealing with a large number of network instances. Moreover, existing solutions for network configuration verification fail to schedule a comparison of the network configuration which leads to numerous inefficiencies and missed opportunities for optimizing the network performance.
[0007] Currently, in the field of telecommunications, there is no easy way to generate one or more comprehensive reports on configuration compliance and non-compliance, and this lacuna makes it complex for the administrator to identify all the issues efficiently and rapidly, and to take one or more corrective actions with respect to the identified issues. Also, the existing solution fails to handle a large number of network instances simultaneously. This lack of scalability makes it difficult to manage large-scale networks efficiently.

[0008] Therefore, due to aforementioned drawbacks, there is a requirement of an enhanced solution for network configuration verification that may be based on a Golden Configuration Template (GCT).
SUMMARY
[0009] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0010] An aspect of the present disclosure may relate to a method for network configuration verification using a Golden Configuration Template (GCT). The method comprises receiving, by a receiving unit, a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances. The method further comprises receiving, by the receiving unit, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT. The method further comprises distributing, by the distributing unit, one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices. The method further comprises comparing, by a comparing unit, via the one or more CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT and determining, by a determining unit, via the one or more CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
[0011] In an exemplary aspect of the present disclosure, the compliance status is at least one of a positive compliance status and a negative compliance status, wherein the positive compliance status is determined in an event when each of the one or more network instances in a target batch is a successful match with the GCT, and wherein the negative compliance status is determined in an event when at least one of the one or more network instances in the target batch is an unsuccessful match with the GCT.

[0012] In an exemplary aspect of the present disclosure, the method further comprises generating a report based on the determination of the compliance status of each of the network instances.
[0013] In an exemplary aspect of the present disclosure, the present disclosure further comprises receiving, by the receiving unit, a second request comprising at least one or more of a Node Type, a Network Instance, and a Software version for each of the plurality of network instances.
[0014] In an exemplary aspect of the present disclosure, the one or more batches are distributed by the distributing unit among the CM microservices based on the second request.
[0015] In an exemplary aspect of the present disclosure, the method further comprises storing, by the distributing unit, results of the comparison in a storage unit.
[0016] In an exemplary aspect of the present disclosure, the method further comprises determining, by the determining unit, a compliance percentage and a non-compliance percentage for each network instance of the plurality of network instances based on the determined compliance status associated with each network instance of the plurality of network instances.
[0017] In an exemplary aspect of the present disclosure, the method further comprises scheduling, by the scheduling unit, a periodic comparison operation at a user-defined time-period.
[0018] Another aspect of the present disclosure may relate to a system for network configuration verification using a Golden Configuration Template (GCT). The system comprises a receiving unit configured to receive a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances. The receiving unit is further configured to receive, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT. The system comprises a distributing unit connected to at least the receiving unit, the distributing unit configured to distribute, one or more batches comprising one or more network instances from the plurality of network instances among a Configuration Management (CM) microservices. The system

comprises a comparing unit connected to at least the distributing unit, the comparing unit configured to compare via the CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT and, a determining unit connected to at least the comparing unit, the determining unit is configured to determine via the CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
[0019] Yet another aspect of the present disclosure may relate to a User Equipment (UE) for network configuration verification using a Golden Configuration Template (GCT), the UE comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to: transmit, to a system via a user interface (UI), a request to compare current configurations of a plurality of network instances with a Golden Configuration Template (GCT), and receiving, from the system at the UI, a response comprising a compliance status for each of the one or more network instances based on the request, wherein the response comprising the compliance status for each of the one or more network instances is received based on: receiving, by the system, the GCT corresponding to a predefined configuration for the plurality of network instances; distributing, by the system, one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices; comparing, by the system via the one or more CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT; and determining, by the system, via the one or more CM microservices, based on the comparison, the compliance status for each of the one or more network instances.
[0020] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for network configuration verification using a Golden Configuration Template (GCT), and the instructions include executable code which, when executed by one or more units of a system, causes: a receiving unit of the system to receive a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances; and to receive, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT. Further, the instructions include executable code which, when executed, causes a distributing unit of the system to distribute, one or more batches comprising one or more network instances from the plurality of network instances among a Configuration Management (CM) microservices.

Further, the instructions include executable code which, when executed, causes a comparing unit of the system to compare via the CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GC. Further, the instructions include executable code which, when executed, causes a determining unit of the system to determine via the CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
OBJECTS OF THE INVENTION
[0021] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0022] It is an object of the present disclosure to provide a method and system for network configuration verification using a Golden Configuration Template (GCT).
[0023] It is another object of the present disclosure to provide a solution that aims to automate a process of comparing a current configuration of network instances with a Golden Configuration Template (GCT) for eliminating the need for time-consuming manual comparison.
[0024] It is another object of the present disclosure to provide a solution that enables one or more network administrators to schedule network configuration comparisons at convenient times, thereby improving the efficiency of network management.
[0025] It is another object of the present disclosure to provide a solution that aims to automatically calculate and report a compliance percentage and a non-compliance percentage, providing valuable insights into a network configuration status and potential issues.
[0026] It is another object of the present disclosure to provide a solution that delivers a detailed non-compliance sheet for each network instance, highlighting specific non-compliance parameters that need corrective action.

[0027] It is another object of the present disclosure to provide a solution that handles a large number of network instances simultaneously, making the solution suitable for large-scale network management tasks.
[0028] It is another object of the present disclosure to provide a solution that improves network management efficiency by splitting network instances into batches and assigning them to multiple Configuration Management (CM) microservices.
[0029] It is yet another object of the present disclosure to provide a solution that streamlines the network management process, increases efficiency, reduces errors, and ultimately enhances network performance.
BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0031] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0032] FIG. 2 illustrates an exemplary block diagram of a system for network configuration verification using a Golden Configuration Template (GCT), in accordance with exemplary implementations of the present disclosure.

[0033] FIG. 3 illustrates a method flow diagram for network configuration verification using a Golden Configuration Template (GCT) in accordance with exemplary implementations of the present disclosure.
[0034] FIG. 4 illustrates an exemplary method flow diagram for network configuration verification using a Golden Configuration Template (GCT), in accordance with exemplary implementations of the present disclosure is shown.
[0035] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0036] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0037] 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.
[0038] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0039] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0040] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0041] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0042] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited

to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
[0043] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0044] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0045] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0046] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0047] As discussed in the background section, the existing network verification systems and devices are time-consuming and operate on one or more error-prone tasks such as comparison

of one or more parameters related to a configuration of network with a plurality of templates or pre-define configuration lists, especially when dealing with a large number of network instances. Moreover, the existing solutions for network configuration verification fail to schedule the configuration comparison, which leads to numerous inefficiencies and missed opportunities for optimizing a network performance. Currently, in the field of telecommunications, there is no easy way to generate one or more comprehensive reports on a configuration compliance and a configuration non-compliance, and this lacuna makes it complex for the administrator to identify all the issues efficiently and rapidly and to take one or more corrective actions with respect to the identified issues. Also, the existing solution fails to handle a large number of network instances simultaneously. This lack of scalability made it difficult to manage large-scale networks efficiently. Hence, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a novel solution for network configuration verification using a Golden Configuration Template (GCT), by receiving a GCT corresponding to a predefined configuration for a plurality of network instances and thereafter receiving a request to compare current configurations of a plurality of network instances with the GCT. Further, one or more batches comprising one or more network instances from the plurality of network instances are distributed among one or more Configuration Management (CM) microservices. Thereafter, the current configuration of the one or more network instances in the one or more batches is compared with the GCT to determine a compliance status of the one or more network instances.
[0048] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in accordance with an exemplary implementation of the present disclosure. In an implementation, the computing device [100] may also implement a method for network configuration verification using a Golden Configuration Template (GCT) utilising the system. In another implementation, the computing device [100] itself implements the method for network configuration verification using the Golden Configuration Template (GCT), by using one or more units configured within the computing device [1000], wherein the said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0049] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a processor [104] coupled with the bus [102]

for processing information. The processor [104] may be, for example, a general-purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main memory [106] may also be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
[0050] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid Crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104]. Another type of user input device may be a cursor controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0051] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described

herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0052] The computing device [100] also may include a communication interface [118] coupled
5 to the bus [102]. The communication interface [118] provides a two-way data communication
coupling to a network link [120] that is connected to a local network [122]. The local network [122] is further connected to a host [124]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
10 As another example, the communication interface [118] may be a local area network (LAN)
card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
15
[0053] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication interface [118]. In the Internet example, a server [130] might transmit a requested code for an application program through the Internet [128], the ISP [126], the local network [122] and the
20 communication interface [118]. The received code may be executed by the processor [104] as
it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0054] Referring to FIG. 2, an exemplary block diagram of a system [200] for network
25 configuration verification using a Golden Configuration Template (GCT) is shown, in
accordance with the exemplary implementations of the present disclosure. The system [200]
comprises at least one receiving unit [202], at least one distributing unit [204], at least one
comparing unit [206], at least one determining unit [208], at least one reporting unit [210], at
least one scheduling unit [212] and at least one storage unit [214]. Also, all of the components/
30 units of the system [200] are assumed to be connected to each other unless otherwise indicated
below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an
14

implementation, the system [200] may be present in a user device to implement the features of
the present disclosure. The system [200] may be a part of the user device / or may be
independent of, but in communication with the user device (may also referred herein as a UE).
In another implementation, the system [200] may reside in a server or a network entity. In yet
5 another implementation, the system [200] may reside partly in the server/ network entity and
partly in the user device.
[0055] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented
10 interchangeably. While specific embodiments may disclose a particular functionality of these
units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the
15 intended functionality described herein, are considered to be encompassed within the scope of
the present disclosure.
[0056] The system [200] is configured for network configuration verification using the Golden
Configuration Template (GCT), with the help of the interconnection between the
20 components/units of the system [200].
[0057] In order to verify the network configuration, the receiving unit [202] is configured to receive the Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances.
25
[0058] The Golden Configuration Template (GCT) is a network configuration version used for compliance management for the plurality of network instances as an ideal network configuration against which one or more network configurations from one or more similar devices may be compared. In other words, the GCT is a standard network configuration
30 template to which the network configuration should comply.
[0059] Further, the receiving unit [202] may receive the GCT according to the type of network or according to a set of rules defined by the network administrator. Also, the GCT may be
15

stored in the storage unit [214] or a server. The GCT may include a set of rules, a set of formats, a set of pre-defined values associated with at least the one or more network instances.
[0060] The present disclosure encompasses that the GCT may be created by the network
5 administrator for the network. The Golden Configuration Template (GCT) corresponds to a
framework that determines optimal settings for a key parameters associated with a particular network, such as compute related parameters, resource related parameters, defined parameters by an application, network configurations etc, to ensure it a performance, a stability, and a reliability of the network, Further, the GCT may also include plurality of fields such as a name
10 field, a device association field, and a configuration selection field. The name field refers to a
name of the GCT associated with a particular network instance, the name field may be a unique name without any space characters. The name field may include only one or more letters, one or more numbers, one or more underscore or one or more hyphen. The device association field may display a list of devices associated with the network and the network administrator may
15 add/update/delete/re-order one or more details associated with devices present in the list of
devices. Further the network administrator may select a source to derive the GCT. For instance, the administrator may select the source as one or more sources managed or associated with the devices, which means that the GCT is seeded from a running configuration of the associated devices that is selected by the network administrator. For another instance, the administrator
20 may select the source as an archived configuration. The archived configuration refers to a pre-
stored configuration file that includes one or more configurations of the network. Further saved configuration file may be automatically saved by one or more storage devices associated with the network or may be manually saved by the network administrator. Additionally, the network administrator may update the GCT according to requirements of the network.
25
[0061] The present disclosure encompasses that the receiving unit [202] which is configured to receive a second request, wherein the second request comprises at least one or more of a node type, a network instance, and a software version for each of the plurality of network instances.
30
[0062] The present disclosure encompasses that the node type may refer to a classification which defines one or more characteristics and responsibilities of the node within the network. The network instance may refer to one or more devices associated with the network. The
16

software version may refer to an identification or declaration number which indicates when the respective software version was released or updated.
[0063] As used herein “node type” (also may be referred herein as a network node type)
5 categorizes different functional entities within the network based on their specific roles and
responsibilities such as routing, switching, and service delivery within a network core. Further, some of the examples of the node type are Radio Access Network (RAN) Nodes, Gateway Nodes, Service Nodes, etc.
10 [0064] As used herein “software version for each of the plurality of network instances” may
refer to a distinct iteration of software deployed across the plurality of network instances within the network. Further, the software version is identified by a unique combination of version numbers, patches, or releases, indicating specific enhancements, bug fixes, or changes implemented by network operators or vendors for the plurality of network instances.
15
[0065] Thereafter, the receiving unit [202] is configured to receive, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT. The present disclosure encompasses that the plurality of network instances may refer to one or more devices or one or more software programs, one or more platforms, one or more virtual
20 machines associated with the respective network. The present disclosure further encompasses
that the request may be initiated by a network administrator via the UI. The present disclosure further encompasses that the request may include a detail about the network to be verified and the respective GCT to be considered for verification of the network.
25 [0066] Further, the distributing unit [204] is configured to distribute, one or more batches
comprising one or more network instances from the plurality of network instances among a Configuration Management (CM) microservices.
[0067] The present disclosure encompasses that the one or more batches are distributed by the
30 receiving unit [202] among the CM microservices based on the second request.
[0068] As used herein “CM microservice” refer to a component within a network architecture of the network that handles network configuration-related tasks, such as managing a dynamic network configuration data of network elements and services, wherein the network elements
17

and services include parameters such as network settings, service configurations, and
operational profiles, which ensures proper functionality and performance of the network.
Further, the CM microservice may facilitate efficient and centralized management of the
network configuration changes, updates, and a distribution across the network to ensure a
5 consistency and a reliability in delivery of the services.
[0069] The present disclosure encompasses that the distributing unit [204] may distribute the one or more batches according to one or more distribution protocols. The one or more distribution protocols may be a pre-defined distribution protocol and/or an administrator
10 defined distribution protocol that may be stored in the storage unit [214]. The one or more
distribution protocols may include a set of rules which may guide the distributing unit [204] to distribute the one or more batches comprising the one or more network instances from the plurality of network instances among the CM microservices. Further, the said set of rules which may guide the distributing unit [204] to distribute the one or more batches may be further based
15 on one or more of the node types, the network instance, and the software version for each of
the plurality of network instances.
[0070] Further, the comparing unit [206] is configured to compare, via the CM microservices,
the current configuration of each of the one or more network instances in each of the one or
20 more batches with the GCT.
[0071] Further, in an implementation of the present disclosure, in an event if any difference is
identified between a current configuration of a target network instance and a respective
predefined configuration defined in the GCT that is associated with the target network instance,
25 then that difference is recorded as a failure of the said current configuration of the target
network instance.
[0072] The present disclosure encompasses that the storage unit [214] is configured to store
30 the result of the comparison.
[0073] The present disclosure encompasses that the comparing unit [206] is configured to compare one or more values of the current configuration of each of the one or more network
18

instances in each of the one or more batches with one or more predefined values associated with the current configuration in the GCT.
[0074] The present disclosure encompasses that the comparing unit [206] may utilize one or
5 more comparison protocols. The one or more comparison protocols may be pre-defined by the
administrator and may be stored in the storage unit [214]. The one or more comparison
protocols may include a set of comparison rules that may guide the comparing unit [206] to
compare the one or more values of the current configuration of each of the one or more network
instances in each of the one or more batches with the one or more predefined values associated
10 with the each of the one or more network instance in the GCT.
[0075] For instance, the comparing unit [206] may compare a value of a schema version in the configuration of a network instance A with a predefined value of schema version in the GCT that is associated with the network instance A. 15
[0076] Thereafter, the determining unit [208] is configured to determine, via the CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
20 [0077] The present disclosure encompasses that the determining unit [208] is further
configured to determine a compliance percentage and a non-compliance percentage for each network instance of the plurality of network instances based on the determined compliance status associated with each network instance of the plurality of network instances.
25 [0078] The present disclosure encompasses that the compliance status is at least one of a
positive compliance status and a negative compliance status, wherein the positive compliance status is determined in an event when each of the one or more network instances in a target batch is a successful match with the GCT, and wherein the negative compliance status is determined in an event when at least one of the one or more network instances in the target
30 batch is an unsuccessful match with the GCT.
[0079] For instance, a schema version in a network configuration D of a network instance B has a value “SCZ7.4.0/2”, whereas a predefined schema version for the network configuration D of the network instance B in the GCT is “SCZ7.4.0/1”. The comparing unit [206] forwards
19

this difference to the determining unit [208]. The determining unit [208] further determines the
compliance status according to the difference identified by the comparing unit [206]. More
particularly, in this scenario, the determining unit [208] may determine the compliance status
as the negative compliance status. However, in case the schema version D in both (i.e., the
5 network configuration and the GCT) have a same value, then the determining unit [208] may
provide the positive compliance status.
[0080] The present disclosure encompasses that the system comprises the reporting unit [210]
that is configured to generate a report based on the determination of the compliance status for
10 each of the one or more network instances.
[0081] The present disclosure encompasses that the compliance percentage indicates that all
the configurations such as one or more proper controls, one or more policies, one or more
settings associated with each of the one or more network instances are in compliance with a
15 predefined network configuration associated with the one or more network instances in the
GCT.
[0082] The present disclosure encompasses that the non- compliance percentage indicates that
one or more configurations, such as the one or more proper controls, the one or more policies,
20 and the one or more settings associated with each of the one or more network instances do not
comply with the predefined network configuration associated with the one or more network instances in the GCT.
[0083] The present disclosure encompasses that the reporting unit [210] may use one or more
25 report generation protocols for generating the report. Further the one or more report generation
protocols may be a pre-defined report generation protocol or a network administrator defined report generation protocol that may be further stored in the storage unit [214].
[0084] The present disclosure encompasses that the reporting unit [210] may generate the
30 report according to one or more formats defined in the storage unit [214]. The reporting unit
[210] may utilize one or more visualization tools or visualization techniques for generating the report.
20

[0085] The present disclosure encompasses that the system comprises a scheduling unit [212]
configured to schedule a periodic comparison operation at a user-defined time-period. For
example, the scheduling unit [212] is configured to schedule the periodic comparison operation
to compare the current configuration of each of the one or more network instances in each of
5 the one or more batches with the GCT after every 30 days in a preferred time slot, like 9: 00 to
12:00.
[0086] Referring to FIG. 3, an exemplary method [300] flow diagram for network
configuration verification using a Golden Configuration Template (GCT), in accordance with
10 exemplary implementations of the present disclosure is shown. In an implementation the
method [300] is performed by the system [200]. Also, as shown in FIG. 3, the method [300] starts at step [302].
[0087] Next, at step [304], the method [300] comprises receiving, by a receiving unit [202],
15 the Golden Configuration Template (GCT) corresponding to a predefined configuration for a
plurality of network instances.
[0088] The Golden Configuration Template (GCT) is a network configuration version used for
compliance management as an ideal network configuration against which one or more network
20 configurations from one or more similar devices may be compared. In other words, the GCT is
standard network configuration template to which the network configuration should comply.
[0089] Further, the receiving unit [202] may receive the GCT according to the type of network,
or according to a set of rules defined by the network administrator. Also, the GCT may be
25 stored in the storage unit [214] or a server. The GCT may include a set of rules, a set of formats,
a set of pre-defined values associated with at least the one or more network instances.
[0090] The present disclosure encompasses that the GCT may be created by the network
administrator for the network. The GCT may also include plurality of fields such as a name
30 field, a device association field, a configuration selection field. The name field refers to a name
of the GCT associated with a particular network instance. The name field may be a unique name without any space characters. The name field may include only one or more letters, one or more numbers, one or more underscore or one or more hyphen. The device association field may display a list of devices associated with the network and the network administrator may
21

add/update/delete/re-order one or more details associated with devices present in the list of
devices. Further the network administrator may select a source to derive the GCT. For instance,
the administrator may select the source as one or more sources managed or associated with the
devices, which means that the GCT is seeded from a running configuration of the associated
5 devices that is selected by the network administrator. In another instance, the administrator
may select the source as an archived configuration. The archived configuration refers to a saved
configuration file that includes one or more configurations of the network. Further, the saved
configuration file may be automatically saved by one or more storage devices associated with
the network or may be manually saved by the network administrator. Additionally, the network
10 administrator may update the GCT according to requirements of the network.
[0091] The present disclosure encompasses that the method [300] further comprises, receiving, by the receiving unit [202], a second request comprising at least one of a Node Type, a Network Instance, and a Software version for each of the plurality of network instances.
15
[0092] The present disclosure encompasses that the node type may refer to a classification which defines one or more characteristics and responsibilities of the node within the network. The network instance may refer to one or more devices associated with the network. The software version may refer to an identification or declaration number which indicates when the
20 respective software version was released or updated.
[0093] As used herein “node type” (also referred herein as a network node type) categorizes
different functional entities within the network based on their specific roles and responsibilities
such as routing, switching, and service delivery within a network core. Further, some of the
25 examples of the node type are Radio Access Network (RAN) Nodes, Gateway Nodes, Service
Nodes, etc.
[0094] As used herein “software version for each of the plurality of network instances” may
refer to a distinct iteration of software deployed across the plurality of network instances within
30 the network. Further, the software version is identified by a unique combination of version
numbers, patches, or releases, indicating specific enhancements, bug fixes, or changes implemented by network operators or vendors for the plurality of network instances.
22

[0095] At step [306], the method [300] comprises receiving, by the receiving unit [202], via a
user interface (UI), a request to compare current configurations of a plurality of network
instances with the GCT. The present disclosure encompasses that the plurality of network
instances may refer to one or more devices or one or more software programs, one or more
5 platforms, one or more virtual machines associated with the respective network. The present
disclosure encompasses that the request may be initiated by a network administrator via the UI. The present disclosure encompasses that the request may include a detail about the network to be verified and the respective GCT to be considered for verification of the network.
10 [0096] At step [308], the method [300] comprises distributing, by the distributing unit [204],
one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices.
[0097] The present disclosure encompasses that the one or more batches are distributed by the
15 distributing unit [204] among the CM microservices based on the second request.
[0098] As used herein “CM microservice” refers to a component within a network architecture of the network that handles network configuration-related tasks such as managing a dynamic network configuration data of network elements and services, wherein the network elements
20 and services includes parameters such as network settings, service configurations, and
operational profiles which ensures proper functionality and performance of the network. Further, the CM microservice may facilitate efficient and centralized management of the network configuration changes, updates, and a distribution across the network to ensure a consistency and a reliability in delivery of the services.
25
[0099] The present disclosure encompasses that the distributing unit [204] may distribute the one or more batches according to one or more distribution protocols. The one or more distribution protocols may be a pre-defined distribution protocol and/or an administrator defined distribution protocol that may be stored in the storage unit [214]. The one or more
30 distribution protocols may include a set of rules which may guide the distributing unit [204] to
distribute the one or more batches comprising the one or more network instances from the plurality of network instances among the CM microservices. Further, the said set of rules which may guide the distributing unit [204] to distribute the one or more batches may be further based
23

on one or more of the node types, the network instance, and the software version for each of the plurality of network instances.
[0100] At step [310], the method [300] comprises comparing, by a comparing unit [206], via
5 the one or more CM microservices, the current configuration of each of the one or more
network instances in each of the one or more batches with the GCT.
[0101] Further, in an implementation of the present disclosure, in an event if any difference is
identified between a current configuration of a target network instance and a respective
10 predefined configuration defined in the GCT that is associated with the target network instance,
then that difference is recorded as a failure of the said current configuration of the target network instance.
[0102] The present disclosure encompasses that the method comprises storing, by the
15 distributing unit [204], results of the comparison in a storage unit [214].
[0103] The present disclosure encompasses that the comparing unit [206] is configured to
compare one or more values of the current configuration of each of the one or more network
instances in each of the one or more batches with one or more predefined values associated
20 with the current configuration in the GCT.
[0104] The present disclosure encompasses that the comparing unit [206] may utilize one or
more comparison protocols. The one or more comparison protocols may be pre-defined by the
administrator and may be stored in the storage unit [214]. The one or more comparison
25 protocols may include a set of comparison rules that may guide the comparing unit [206] to
compare the one or more values of the current configuration of each of the one or more network instances in each of the one or more batches with the one or more predefined values associated with the each of the one or more network instances in the GCT.
30 [0105] For instance, the comparing unit [206] may compare a value of a schema version in the
configuration of a network instance A with a predefined value of schema version in the GCT that is associated with the network instance A.
24

[0106] At step [312], the method [300] comprises determining, by a determining unit [208] via the one or more CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
5 [0107] The method [300] terminates at step [314].
[0108] The present disclosure encompasses that the determining unit [208] is further
configured to determine a compliance percentage and a non-compliance percentage for each
network instance of the plurality of network instances based on the determined compliance
10 status associated with each network instance of the plurality of network instances.
[0109] The present disclosure encompasses that the compliance status is at least one of a
positive compliance status and a negative compliance status, wherein the positive compliance
status is determined in an event each of the one or more network instances in a target batch is
15 a successful match with the GCT, and wherein the negative compliance status is determined in
an event at least one of the one or more network instances in the target batch is an unsuccessful match with the GCT.
[0110] For instance, a schema version in a network configuration D of a network instance B
20 has a value “SCZ7.4.0/2”, whereas a predefined schema version for the network configuration
D of the network instance B in the GCT is “SCZ7.4.0/1”, the comparing unit [206] forwards
this difference to the determining unit [208]. The determining unit [208] further determines the
compliance status according to the difference identified by the comparing unit [206]. More
particularly, in this scenario, the determining unit [208] may determine the compliance status
25 as the negative compliance status. However, in case the schema version D in both (i.e., the
network configuration and the GCT) have a same value, then the determining unit [208] may provide the positive compliance status.
[0111] The present disclosure encompasses that the method [300] further comprises
30 generating, via a reporting unit [210], a report based on the determination of the compliance
status of each of the network instances.
[0112] The present disclosure encompasses that the reporting unit [210] may use one or more report generation protocols for generating the report. Further the one or more report generation
25

protocols may be a pre-defined report generation protocols or a network administrator defined report generation protocols that may be further stored in the storage unit [214].
[0113] The present disclosure encompasses that the reporting unit [210] may generate the
5 report according to one or more formats defined in the storage unit [214]. The reporting unit
[210] may utilize one or more visualization tools or visualization techniques for generating the report.
[0114] The present disclosure encompasses that the method [300] comprises determining, by
10 the determining unit [208], a compliance percentage and a non-compliance percentage for each
network instance of the plurality of network instances based on the determined compliance status associated with each network instance of the plurality of network instances.
[0115] The present disclosure encompasses that the compliance percentage indicates that all
15 the configurations such as one or more proper controls, one or more policies, one or more
settings associated with each of the network instances are in compliance with a predefined network configuration associated with the one or more network instances in the GCT.
[0116] The present disclosure encompasses that the non-compliance percentage indicates that
20 one or more configurations such as the one or more proper controls, the one or more policies,
the one or more settings associated with each of the network instances do not comply with the predefined network configuration associated with the one or more network instances in the GCT.
25 [0117] The present disclosure encompasses that the method comprises scheduling, by the
scheduling unit [212], a periodic comparison operation at a user-defined time-period. For example, the scheduling unit [212] is configured to schedule the periodic comparison operation to compare the current configuration of each of the one or more network instances in each of the one or more batches with the GCT after every 30 days in a preferred time slot, like 9: 00 to
30 12:00.
[0118] Referring to FIG. 4, an exemplary flow diagram of a method [400] for network configuration verification using a Golden Configuration Template (GCT), in accordance with
26

exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [200].
[0119] The method [400] starts at step S1, next at step S2, a file is uploaded to the system [200]. The file may be an excel file and may include a data related to one or more configurations within a network such as a node type, a network instance and a software version.
[0120] At step S3, the uploaded file is validated via one or more validation protocols.
[0121] Further, the validation is passed to an elastic load balancer (ELB) at step S4. The ELB divides the network instances among multiple Configuration Management (CM) microservices at step S5. Further, in an instance, the ELB divides one or more batches comprising one or more network instances, from the network instances among the multiple Configuration Management (CM) microservices.
[0122] After receiving the request at the CM microservices, each CM microservice compares the one or more configurations of the allotted network instances with the GCT and store a compliance/non-compliance percentage in a persist storage at step S6.
[0123] The method [400] terminates at step S7.
[0124] The present disclosure further discloses a User Equipment (UE) for network configuration verification using a Golden Configuration Template (GCT), the UE comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to: transmit, to a system [200], via a user interface (UI), a request to compare current configurations of a plurality of network instances with a Golden Configuration Template (GCT), and receiving, from the system [200] at the UI, a response comprising a compliance status for each of the one or more network instances based on the request, wherein the response comprising the compliance status for each of the one or more network instances is received based on: receiving, by the system [200], the GCT corresponding to a predefined configuration for the plurality of network instances; distributing, by the system [200], one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices; comparing, by the system [200] via the one or more CM microservices, the current configuration of each of the one or more

network instances in each of the one or more batches with the GCT; and determining, by the system [200] via the one or more CM microservices, based on the comparison, the compliance status for each of the one or more network instances.
[0125] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for network configuration verification using a Golden Configuration Template (GCT) and the instructions include an executable code which, when executed by one or more units of a system [200], causes: a receiving unit [202] of the system [200] to receive a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances; and the receiving unit [202] to receive, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT. Further, the instructions include executable code which, when executed, causes a distributing unit [204] of the system to distribute, one or more batches comprising one or more network instances from the plurality of network instances among a Configuration Management (CM) microservices. Further, the instructions include executable code which, when executed, causes a comparing unit [206] of the system [200] to compare via the CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT. Further, the instructions include executable code which, when executed, causes a determining unit [208] of the system [200] to determine via the CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
[0126] As is evident from the above, the present disclosure provides a technically advanced solution for network configuration verification using a Golden Configuration Template (GCT). The present solution aims to automate the process of comparing a current configuration of network instances with the Golden Configuration Template (GCT) for eliminating the need of time-consuming manual comparison. Also, the present solution enables one or more network administrators to schedule configuration comparisons at convenient times, thereby improving an efficiency of network management process. The present solution also aims to automatically calculate and report compliance and non-compliance percentages, thus providing valuable insights into a network configuration status and potential issues. The present solution delivers a detailed non-compliance sheet for each network instance, highlighting specific non-compliance parameters that are in the need of a corrective action. Further the present solution manages a large number of network instances simultaneously, making the solution suitable for

large-scale network management tasks. The present solution improves network management efficiency by splitting network instances into batches and assigning them to multiple Configuration Management (CM) microservices. Hence, the present solution streamlines the network management process, increase efficiency, reduce errors, and ultimately enhances network performance.
[0127] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method [300] for network configuration verification using a Golden Configuration
Template (GCT), the method [300] comprising:
receiving, by a receiving unit [202], a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances;
receiving, by the receiving unit [202] via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT;
distributing, by a distributing unit [204], one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices;
comparing, by a comparing unit [206] via the one or more CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT; and
determining, by a determining unit [208] via the one or more CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
2. The method [300] as claimed in claim 1, wherein the compliance status is at least one of a positive compliance status and a negative compliance status, wherein the positive compliance status is determined in an event each of the one or more network instances in a target batch is a successful match with the GCT, and wherein the negative compliance status is determined in an event at least one of the one or more network instances in the target batch is an unsuccessful match with the GCT.
3. The method [300] as claimed in claim 1, comprises generating a report based on the determination of the compliance status of each of the network instances.
4. The method [300] as claimed in claim 1, the method [300] further comprises, receiving, by the receiving unit [202], a second request comprising at least one of a Node Type, a Network Instance, and a Software version for each of the plurality of network instances.
5. The method [300] as claimed in claim 4, wherein the one or more batches are distributed by the distributing unit [204] among the CM microservices based on the second request.

6. The method [300] as claimed in claim 1, wherein the method [300] comprises storing, by the distributing unit [204], results of the comparison in a storage unit [214].
7. The method [300] as claimed in claim 2, wherein the method [300] comprises determining, by the determining unit [208], a compliance percentage and a non-compliance percentage for each network instance of the plurality of network instances based on the determined compliance status associated with each network instance of the plurality of network instances.
8. The method [300] as claimed in claim 1, wherein the method [300] comprises scheduling, by a scheduling unit [212], a periodic comparison operation at a user-defined time-period.
9. A system [200] for network configuration verification using a Golden Configuration Template (GCT), the system [200] comprises:
a receiving unit [202] configured to receive a Golden Configuration Template (GCT) corresponding to a predefined configuration for a plurality of network instances;
the receiving unit [202] configured to receive, via a user interface (UI), a request to compare current configurations of a plurality of network instances with the GCT;
a distributing unit [204] connected to at least the receiving unit [202], the distributing unit [204] configured to distribute, one or more batches comprising one or more network instances from the plurality of network instances among a Configuration Management (CM) microservices;
a comparing unit [206] connected to at least the distributing unit [204], the comparing unit [206] configured to compare via the CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT; and
a determining unit [208] connected to at least the comparing unit [206], the determining unit [208] configured to determine via the CM microservices, based on the comparison, a compliance status for each of the one or more network instances.
10. The system [200] as claimed in claim 9, wherein the compliance status is at least one of a
positive compliance status and a negative compliance status, wherein the positive
compliance status is determined in an event each of the one or more network instances in a
target batch is a successful match with the GCT, and wherein the negative compliance status

is determined in an event at least one of the one or more network instances in the target batch is an unsuccessful match with the GCT.
11. The system [200] as claimed in claim 9, wherein the system [200] comprises a reporting unit [210] configured to generate a report based on the determination of the compliance status for each of the one or more network instances.
12. The system [200] as claimed in claim 9, wherein the receiving unit [202] is further configured to receive a second request, wherein the second request comprises at least one or a Node Type, a Network Instance, and a Software version for each of the plurality of network instances.
13. The system [200] as claimed in claim 12, wherein the one or more batches are distributed by the distributing unit [204] among the CM microservices based on the second request.
14. The system [200] as claimed in claim 9, wherein the system [200] further comprises a storage unit [214] configured to store result of the comparison.
15. The system [200] as claimed in claim 10, wherein the determining unit [208] is further configured to determine a compliance percentage and a non-compliance percentage for each network instance of the plurality of network instances based on the determined compliance status associated with each network instance of the plurality of network instances.
16. The system [200] as claimed in claim 9, wherein the system [200] comprises a scheduling unit [212] configured to schedule a periodic comparison operation at a user-defined time-period.
17. A User Equipment (UE) for network configuration verification using a Golden Configuration Template (GCT), the UE comprising:

- a memory; and
- a processor coupled to the memory, wherein the processor is configured to:
o transmit, to a system [200] via a user interface (UI), a request to compare current configurations of a plurality of network instances with a Golden Configuration Template (GCT), and

o receiving, from the system [200] at the UI, a response comprising a compliance status for each of the one or more network instances based on the request, wherein the response comprising the compliance status for each of the one or more network instances is received based on:
receiving, by the system [200], the GCT corresponding to a predefined configuration for the plurality of network instances,
distributing, by the system [200], one or more batches comprising one or more network instances from the plurality of network instances among one or more Configuration Management (CM) microservices,
comparing, by the system [200] via the one or more CM microservices, the current configuration of each of the one or more network instances in each of the one or more batches with the GCT, and
determining, by the system [200] via the one or more CM microservices, based on the comparison, the compliance status for each of the one or more network instances.