DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR CONFIGURING ONE OR MORE ATTRIBUTES OF NODES IN A NETWORK

2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of telecommunications and network management, more particularly relates to a method and system for configuring one or more attributes of nodes in a network.
BACKGROUND OF THE INVENTION
[0002] Network nodes in mobile communication networks usually operate multiple instances. Southbound application program interfaces (hereinafter referred to as “Southbound APIs”) are used to communicate between the higher-level network components such as SDN Controller and lower-level network components such as the switches and routers of the network. Southbound APIs can be open-source or proprietary.
[0003] Currently, any changes in Southbound APIs require code level changes to be made. Due to this, lot of time and effort is required for development and integration. Further, to cater to provisioning of new southbound APIs, additional development and integration effort is required.
[0004] There is a need for a modified system and method that can facilitate configuring the southbound APIs with minimum development and integration effort.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present invention provides a method and a system for configuring one or more attributes of nodes in a network.
[0006] In one aspect of the present invention, the method for configuring one or more attributes of nodes in the network. The method includes the step of receiving a request from a user equipment via a user interface for configuring the one or more attributes of a first node. The method further includes the step of identifying at least one configuration operation to configure the one or more attributes of the first node based on the received request. The method further includes the step of receiving a response from a second node in the network pertaining to attributes associated with the second node. The method further includes the step of determining if at least a portion of the one or more attributes of the first node matches with the attributes associated with the second node based on comparing the request with the response. The method further based on the determining that at least the portion of the one or more attributes of the first node matches with the attributes associated with the second node includes the step of retrieving a configuration logic from a cache data store based on the identified at least one configuration operation from the request. The method further includes the step of dynamically configuring the one or more attributes of the first node by applying the configuration logic retrieved from the cache data store.
[0007] In one embodiment, the one or more attributes is in the form of at least one of, keys and values.
[0008] In one embodiment, the at least one configuration operation pertains to, add, modify, delete, concatenate, match and replace the attribute keys and values.
[0009] In one embodiment, the step of, receiving, a response from a second node in the network pertaining to attributes associated with the second node, includes the step of pinging the second node to receive information pertaining to the attributes associated with the second node.
[0010] In one embodiment, the step of retrieving a configuration logic from a cache data store based on the identified at least one configuration operation from the request, includes the steps of mapping the identified at least one configuration operation with a plurality of configuration logics present in the cache data store. The method further includes the steps of identifying the configuration logic based on the mapping.
[0011] In another aspect of the present invention, a system for configuring one or more attributes of nodes in a network. The system includes a transceiver configured to receive a request from a user equipment via a user interface for configuring the one or more attributes of a first node and further configured to receive a response from a second node in the network pertaining to attributes associated with the second node. The system further includes an identification unit configured to identify at least one configuration operation to configure the one or more attributes of the first node based on the received request. The system further includes a determining unit configured to determine if at least a portion of the one or more attributes of the first node matches with the attributes associated with the second node based on comparing the request with the response. Further based on determining that at least the portion of the one or more attributes of the first node matches with the attributes associated with the second node the system includes a retrieving unit, configured to, retrieve, a configuration logic from a cache data store based on the identified at least one configuration operation from the request. The system further includes a configuring unit, configured to dynamically configure the one or more attributes of the first node by applying the configuration logic retrieved from the cache data store.
[0012] In another aspect of the present invention, a User Equipment (UE) is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors are coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit a request to configure one or more attributes of a first node to the one or more processers.
[0013] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor, causes the processor to receive a request from a user equipment via a user interface, for configuring the one or more attributes of a first node. The processor is further configured to identify at least one configuration operation to configure the one or more attributes of the first node based on the received request. The processor is further configured to receive a response from a second node in the network pertaining to attributes associated with the second node. The processor is further configured to determine if at least a portion of the one or more attributes of the first node matches with the attributes associated with the second node based on comparing the request with the response. The processor further based on determining that at least the portion of the one or more attributes of the first node matches with the attributes associated with the second node, retrieve, a configuration logic from a cache data store based on the identified at least one configuration operation from the request. The processor is further configured to dynamically configure one or more attributes of the first node by applying the configuration logic retrieved from the cache data store.
[0014] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0016] FIG. 1 is an exemplary block diagram of an environment for configuring one or more attributes of nodes in a network, according to one or more embodiments of the present disclosure;
[0017] FIG. 2 is an exemplary block diagram of a system for configuring the one or more attributes of nodes in the network, the system comprising, according to one or more embodiments of the present disclosure;
[0018] FIG. 3 is a schematic representation of a workflow of the system of FIG. 2 communicably coupled with a User equipment (UE), according to one or more embodiments of the present disclosure;
[0019] FIG. 4 is an exemplary block diagram of an architecture can be implemented in the system of FIG.2, according to one or more embodiments of the present disclosure;
[0020] FIG. 5 is a workflow diagram illustrating configuring Southbound API, according to one or more embodiments of the present disclosure; and
[0021] FIG. 6 is a flow chart illustrating a method for configuring the one or more attributes of nodes in the network, according to one or more embodiments of the present disclosure.
[0022] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[0023] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0024] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0025] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0026] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for configuring one or more attributes of nodes 125 in a network 105, according to one or more embodiments of the present disclosure. The environment 100 includes the network 105, a User Equipment (UE) 110, a server 115, a system 120, and the plurality of nodes 125. The term “nodes” and “plurality of nodes” are collectively and interchangeably used herein. For the purpose of description and explanation, the description will be explained with respect to the plurality of nodes 125, or to be more specific will be explained with respect to the first node, a second node, and should nowhere be construed as limiting the scope of the present disclosure. The UE 110 aids a user to interact with the system 120 for transmitting a request to configure one or more attributes of the first node to one or more processors 205 (shown in FIG.3). The one or more attributes refer to specific settings, or parameters of the node 125 (such as a router, switch, server, etc.) that can be defined, modified, or monitored. The one or more attributes determine the behavior, performance, and security of the node 125.
[0027] Let’s consider for an example, the one or more attributes of the router define configuration of network interfaces including IP addresses, subnet masks, and operational states. The one or more attributes of the switch manages network loops and ensures redundancy by blocking certain ports to prevent loops. The one or more attributes of the server monitors metrics such as CPU usage, memory utilization, disk I/O, and network throughput that are monitored to assess server performance.
[0028] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0029] For the purpose of description and explanation, the description will be explained with respect to the UE 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the first UE 110a, the second UE 110b, and the third UE 110c is configured to connect to the server 115 via the network 105. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0030]
The network 105 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 network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0031] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0032] The network 105 may also 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 network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0033] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0034] The environment 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity. However, for the purpose of description, the system 120 is illustrated as remotely coupled with the server 115, without deviating from the scope of the present disclosure.
[0035] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0036] FIG. 2 illustrates an exemplary block diagram of the system 120 for configuring the one or more attributes of nodes 125 in the network 105, according to one or more embodiments of the present disclosure.
[0037] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 215 and a database 245. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0038] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium which may be fetched and executed to display the enriched data to the user via the user interface 215 in order to perform analysis. The memory 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0039] In an embodiment, the user interface 215 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as Input/Output (I/O) devices, storage devices, and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120.
[0040] In an embodiment, the database 245 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, and so forth. The foregoing examples of database 245 types are non-limiting and may not be mutually exclusive e.g., the database can be both commercial and cloud-based, or both relational and open-source, etc. In another embodiment, the database 245 can be used as a cache data store 410 (shown in FIG.4).
[0041] In order for the system 120 for configuring the one or more attributes of nodes 125 in the network 105, the processor 205 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a transceiver 220, an identification unit 225, a determining unit 230, a retrieving unit 235 and a configuring unit 240 communicably coupled to each other for configuring the one or more attributes of the nodes 125 in the network 105.
[0042] In one embodiment, the one or more modules includes, but not limited to, the transceiver 220, the identification unit 225, the determining unit 230, the retrieving unit 235 and the configuring unit 240 can be used in combination or interchangeably for configuring the one or more attributes of the nodes 125 in the network 105.
[0043] The transceiver 220, the identification unit 225, the determining unit 230, the retrieving unit 235 and the configuring unit 240 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0044] The transceiver 220 is configured to receive a request from the UE 110 via the user interface 215. In an embodiment, the request pertains to configuring the one or more attributes of the first node. In an embodiment, the one or more attributes is in the form of at least one of, keys and values. In another embodiment, the one or more attributes include network configuration attributes, performance attributes, security attributes, operational attributes and Quality of Service (QoS) attributes. As used herein, the keys represent the specific attributes or settings that can be configured on the first node 125a. Let us consider for an example, the keys include IP address, subnet mask, gateway, and the like. As used herein, the values are the specific configurations or parameters assigned to each key. Let us consider for an example, the values include 192.168.1.1 for IP address, 255.255.255.0 for subnet mask, and 192.168.1.254 for gateway.
[0045] Upon receiving the request from the UE 110 via the user interface 215, the identification unit 225 is configured to identify at least one configuration operation to configure the one or more attributes of the first node 125a based on the received request. In an embodiment, the at least one configuration operation pertains to, add, modify, delete, concatenate, match and replace the attribute keys and values. The at least one configuration operation refers to any action performed to change the settings, or parameters of the first node 125a. The at least one configuration operation is performed through a series of steps that involve receiving the request, identifying the necessary operations, and executing the operations to configure the one or more attributes of the first node 125a. Let us consider for example, add, modify, delete, concatenate, match and replace the attribute keys and values based on a response of the second node 125b.
[0046] Upon identifying the at least one configuration operation to configure the one or more attributes of the first node 125a, the transceiver 220 is configured to receive the response from the second node 125b in the network 105 pertaining to attributes associated with the second node 125b. The response typically provides information about a current state or configuration details of the second node 125b after the at least one configuration operation is performed on the first node 125a. The second node 125b is configured to ping the receive information pertaining to the attributes associated with the second node. The response aids to confirm that the configuration made on the first node 125a is successfully matching to the associated attributes on the second node 125b.
[0047] Upon receiving the response from the second node 125b in the network 105, the determining unit 230 is configured to determine if at least a portion of the one or more attributes of the first node 125a matches with at least a portion of the one or more attributes associated with the second node 125b based on comparing the request with the response. The relevant attributes are extracted from both the request and the response. For instance, it might focus on extracting source IP addresses, destination IP addresses, or specific headers that are critical for identification or classification. The determining unit 230 is configured to compare these extracted attributes between the first node 125a and the second node 125b. Further, the determining unit 230 is configured to check if the one or more attributes from the request sent by the first node 125a match the one or more attributes from the response received by the second node 125b.
[0048] As per one embodiment, if the one or more attributes from the request sent by the first node 125a is match with the one or more attributes from the response received by the second node 125b, then the retrieving unit 235 is configured to retrieve a configuration logic from a cache data store 410 based on the identified at least one configuration operation from the request. The configuration logic is retrieved based on determining that at least the portion of the one or more attributes of the first node matches with the at least the portion of the one or more attributes associated with the second node. The configuration logic refers to the set of rules, instructions, or scripts that dictate how the nodes 125 is configured under various conditions.
[0049] The retrieved configuration logic is then applied to all nodes 125. Let’s consider for an example, how each node is configured round-robin model or least connections to distribute traffic in the first node 125a. Periodic health checks are set up (for e.g., every 5 seconds) to ensure backend servers are responsive. The first node 125a enables auto-scaling to add or remove backend servers based on predefined CPU and memory usage thresholds. Similarly, the second node 125b utilizes the same traffic distribution model (round-robin or least connections) for consistency, implementing the same health check intervals and methods as the first node 125a, and configure auto-scaling with the same thresholds as the first node 125a to ensure synchronized scaling actions. Then the configuration logic of the first node 125a is same as the configuration logic of the second node 125b. In this regard, the configuration logic of the first node 125a is retrieved to configure the logic for the second node 125b as well.
[0050] The retrieving unit 235 is configured to analyze the configuration operations identified in the request. Further the retrieving unit 235 is configured to map the identified at least one configuration operation with a plurality of configuration logics present in the cache data store 410. The retrieving unit 235 is configured to map the identified at least one configuration operation to predefined or stored configuration logics available in the cache data store 410. The configuration logic is identified based on the mapping. Based on the identified configuration logic, the retrieving unit 235 is configured to retrieve relevant configuration logic from the cache data store 410 for configuration process.
[0051] Upon identifying the configuration logic, the configuring unit 240 is configured to dynamically configure the one or more attributes of the first node 125a by applying the configuration logic retrieved from the cache data store 410. The configuring unit 240 is configured to apply the retrieved configuration logic to dynamically configure the one or more attributes of the first node 125a. The configuration process adjusts the one or more attributes such as network settings, operational parameters, security policies, or other relevant configurations as dictated by the retrieved configuration logic. The configuration adjustments are based on the operational context, ensuring that the one or more attributes of the first node 125a align with the desired configuration state defined by the retrieved configuration logic.
[0052] By doing so the system 120 for dynamically configuring the one or more attributes of the first node 125a by applying the configuration logic retrieved from the cache data store 410 without requiring new release, downtime or code level changes. The system 120 saves development and integration effort, increasing system flexibility to cater for any changes in the nodes 125.
[0053] FIG. 3 is a schematic representation of a workflow of the system of FIG. 2 communicably coupled with a User equipment (UE), according to one or more embodiments of the present disclosure. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 120 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0054] As mentioned earlier in FIG. 1, the UE 110 may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.
[0055] The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to transmit the request to configure the one or more attributes of the first node to the one or more processors 205.
[0056] As illustrated in FIG. 2, the system 120 includes the one or more processors 205, the memory 210, the user interface 215, and the database 245. The operations and functions of the one or more processors 205, the memory 210, the user interface 215, and the database 245 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0057] As illustrated in FIG. 2, the system 120 includes the transceiver 220, the identification unit 225, the determining unit 230, the retrieving unit 235 and the configuring unit 240. The operations and functions of the transceiver 220, the identification unit 225, the determining unit 230, the retrieving unit 235 and the configuring unit 240 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0058] FIG. 4 is an exemplary architecture 400 which can be implemented in the system 120 of the FIG.2, according to one or more embodiments of the present invention. The exemplary embodiment as illustrated in the FIG. 4 includes the user interface 215, a dynamic routing manager 404, a distributed database 408 having a distributed data lake 412, the cache data store 410, a dynamic activator 414, a workflow manager 418, a message broker 424, a graph database 422, an operation and management module 426 and a load balancer 428.
[0059] Generally, attributes of data storage for a network node keep changing. For example, if a node initially saved a mobile number attribute as a ten-digit number and seeks to change a format of the mobile number as follows: the ten-digit number with a prefix of “+91”, then such changes should be reflected easily without code changes. The user may change the configuration of storing the mobile number in the node 125 via the user interface 215. In another embodiment, derivation logic of the attribute can also undergo change, such changes are reflected in the API by making changes to the configuration file associated with the node 125, via the user interface 215. The configuration changes are stored in the cache data store 410. As a result, integration of the configuration changes with the API is made convenient.
[0060] The dynamic routing manager 404 is a system designed to manage and optimize the routing of data packets in real-time based on current network conditions, policies, and demands. The dynamic routing manager 404 ensures that data takes the most efficient and effective path through the network 105, adapting to changes such as traffic load, link failures, and varying bandwidth requirements.
[0061] The distributed data lake 412 is an architectural approach to storing and managing vast amounts of structured and unstructured data across multiple locations or systems. The distributed data lake 412 leverages distributed computing and storage technologies to provide scalable, flexible, and efficient data storage solutions, enabling organizations to manage and analyze large datasets seamlessly.
[0062] The workflow manager 418 is a system designed to automate and manage various operational processes within the network 105. The primary function of the workflow manager 418 is to streamline, coordinate, and monitor complex tasks, ensuring efficient and consistent execution of workflows. To integrate the configuration changes into the API, the workflow manager 418 is configured to read the configuration and stored in the cache data store 410.
[0063] The workflow manager 418 is configured to instruct the dynamic activator 414, to execute the state for the workflow based on the configuration. The dynamic activator 414 is a system or component that dynamically enables and manages network functions, services, or resources in response to changing conditions, demands, and configurations within the network 105. The dynamic activator 414 is configured to retrieve information from the cache data store 410 to execute the state.
[0064] For example, the configuration information may include a type of mapping to be performed, which index of a request received from the node 125 is to be chosen, a substring to create from the index, and an attribute to map, and any other configuration data stored therein. Based on the mapping and attribute information, relevant attributes or codes are communicated by the dynamic activator 414 to the second node.
[0065] The message broker 424 is an intermediary software component that facilitates communication between different systems or applications by translating messages from the messaging protocol of the transmitter to the messaging protocol of the receiver. The message broker 424 acts as a middleware that helps decouple services and allows them to communicate asynchronously, ensuring reliable and scalable message delivery.
[0066] Th graph database 422 is a database designed to store, manage, and query data structured as graphs, which consist of nodes (entities), edges (relationships), and properties (attributes) that describe the characteristics of nodes and edges.
[0067] The operation and management module 426 refers to a set of tools, processes, and functionalities designed to oversee, control, and maintain the efficient operation of the network 105. The operation and management module 426 encompasses the tasks necessary to ensure that the network 105 performs optimally, remains secure, and provides the required services reliably.
[0068] The load balancer 428 is a device or software application that distributes network 105 or application traffic across multiple servers to ensure no single server becomes overwhelmed. By balancing the load, it helps optimize resource use, maximize throughput, minimize response time, and prevent overload on any single server. The load balancer 428 is essential in ensuring the high availability and reliability of applications.
[0069] FIG. 5 is a workflow diagram illustrating configuring a Southbound Application Programming Interface (API), according to one or more embodiments of the present disclosure.
[0070] The North Bound Interface (NBI) is an application programming interface (API) or protocol that allows a lower-level network component to communicate with a higher-level or more central component, while conversely the South Bound Interface (SBI) allows the higher-level component to send commands to the lower-level network components.
[0071] The southbound API is an interface that facilitates communication and interaction between a network controller or management system and the underlying network devices (such as router, switches, base stations, and the like). The one or more attributes are defined in a schema of the southbound interface. The schema of the southbound interface defines the structure and organization of the API that allows the network controller to interact with network devices (such as the first node 125a and the second node 125b). The schema includes, but not limited to, various components, such as endpoints, data models, protocols, and operations.
[0072] As shown, at 1, a request from the NBI interface 505, is received by the system 120. The NBI interface 505 provides an abstraction layer that exposes network capabilities, status information, and configuration options to higher-level applications or services. The NBI interface 505 facilitates the exchange of data and commands between management systems (like software-defined networking (SDN) controllers or network management software) and network elements (such as routers, switches, or other devices). In an example, the request can have information regarding the “layer” and “MetroSuper Core” of the first node 125a. The system 120 is configured to forward the request with the information regarding “layer” and “MetroSuper Core” to the first node 125a.
[0073] Based on the request, the first node 125a, gives a response at 3, where the response includes an “equipment identifier” and value “INMUKLYNJ5BGNB0001MA2A08251”. The system 120 is configured to receive the response and based on the configuration file, is configured to retrieve the 3rd and 4th digit of the equipment identifier received. The 3rd and 4th digit indicate a circle in the second node 125b belongs to. Herein, the 3rd and 4th digit are “MU” which indicates the second node 125b belongs to the city circle of “Mumbai”, as MU is a code for Mumbai.
[0074] Further, based on the configuration, at 4, the system 120 is configured to forward the circle id, for example, “MU” (MU denotes the circle id for Mumbai) to the second node 125b. Upon completion of the communication, the system 120 is configured to send a completion response to the NBI interface 505. Various other operations can also be configured to be performed on the request, such as match, concatenate, substring selection, dynamic concatenation, choosing within a number range, replacing a string with another predefined attribute and the like.
[0075] FIG. 6 is a flow chart illustrating a method for configuring the one or more attributes of nodes in the network, according to one or more embodiments of the present disclosure. For the purpose of description, the method is described with the embodiments as illustrated in FIG.2 and should nowhere be construed as limiting the scope of the present disclosure.
[0076] At step 605, the method 600 includes the step of receiving the request from the UE 110 via the user interface 215 by the transceiver 220. In an embodiment, the request pertains to configuring the one or more attributes of the first node. In an embodiment, the one or more attributes is in the form of at least one of, keys and values. In another embodiment, the one or more attributes include network configuration attributes, performance attributes, security attributes, operational attributes and Quality of Service (QoS) attributes.
[0077] At step 610, the method 600 includes the step of identifying the at least one configuration operation to configure the one or more attributes of the first node 125a based on the received request by the identification unit 225. In an embodiment, the at least one configuration operation pertains to, add, modify, delete, concatenate, match and replace the attribute keys and values. The at least one configuration operation refers to any action performed to change the settings, or parameters of the first node 125a.
[0078] At step 615, the method 600 includes the step of receiving the response from the second node 125b in the network 105 pertaining to attributes associated with the second node 125b by the transceiver 220. The response typically provides information about a current state or configuration details of the second node 125b after the at least one configuration operation is performed on the first node 125a. The second node 125b is configured to ping the receive information pertaining to the attributes associated with the second node. The response aids to confirm that the configuration made on the first node 125a is successfully matching to the associated attributes on the second node 125b.
[0079] At step 620, the method 600 includes the step of determining if at least the portion of the one or more attributes of the first node 125a matches with at least the portion of the one or more attributes associated with the second node 125b based on comparing the request with the response by the determining unit 230. The relevant attributes are extracted from both the request and the response. For instance, it might focus on extracting source IP addresses, destination IP addresses, or specific headers that are critical for identification or classification. The determining unit 230 is configured to compare these extracted attributes between the first node 125a and the second node 125b. Further, the determining unit 230 is configured to check if the one or more attributes from the request sent by the first node 125a match the one or more attributes from the response received by the second node 125b.
[0080] At step 625, the method 600 includes the step of retrieving the configuration logic from the cache data store 410 based on the identified at least one configuration operation from the request by the retrieving unit 235. The configuration logic is retrieved based on determining that at least the portion of the one or more attributes of the first node matches with the attributes associated with the second node. The configuration logic refers to the set of rules, instructions, or scripts that dictate how the nodes 125 is configured under various conditions.
[0081] Further, the retrieving unit 235 is configured to analyze the configuration operations identified in the request. Further the retrieving unit 235 is configured to map the identified at least one configuration operation with a plurality of configuration logics present in the cache data store 410. The retrieving unit 235 is configured to map the identified at least one configuration operation to predefined or stored configuration logics available in the cache data store 410. The configuration logic is identified based on the mapping. Based on the identified configuration logic, the retrieving unit 235 is configured to retrieve relevant configuration logic from the cache data store 410 for configuration process.
[0082] At step 630, the method 600 includes the step of dynamically configuring the one or more attributes of the first node 125a by applying the configuration logic retrieved from the cache data store 410 by the configuring unit 240. The configuring unit 240 is configured to apply the retrieved configuration logic to dynamically configure the one or more attributes of the first node 125a. The configuration process adjusts the one or more attributes such as network settings, operational parameters, security policies, or other relevant configurations as dictated by the retrieved configuration logic. The configuration adjustments are based on the operational context, ensuring that the one or more attributes of the first node 125a align with the desired configuration state defined by the retrieved configuration logic.
[0083] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0084] The present disclosure incorporates technical advancement that facilitates configuration of the one or more attributes of nodes in the network. The present disclosure is dynamically configured the one or more attributes of the first node 125a by applying the configuration logic retrieved from the cache data store 410. So, if there is any change offered by the user interface including changes in existing one or more attributes can be handled by changing the configuration from the system by the user. By doing so, the present disclosure saves development and integration effort, increasing system flexibility to cater for any changes in the nodes 125, and without requires new release, downtime or code level changes.
[0085] The present invention provides various advantages for configuring the one or more attributes of nodes in the network which is done easily without development and integration effort. By the configuration logic, different keys and values for the one or more attributes can be assigned, which reduces overall development time. A plurality of services can be impacted dynamically and conveniently. Through the user interface, the plurality of configurations from which the attributes value can be derived and defined by the user. Support for plurality of types of mappings is provided. Further, the user interface of any user can be configured or catered by changing the key or value of the nodes.
[0086] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS
[0087] Environment – 100
[0088] Network – 105
[0089] User Equipment – 110
[0090] Server – 115
[0091] System – 120
[0092] Plurality of nodes- 125
[0093] Processor -205
[0094] Memory – 210
[0095] User Interface– 215
[0096] Transceiver - 220
[0097] Identification unit - 225
[0098] Determining unit - 230
[0099] Retrieving unit – 235
[00100] Configuring unit – 240
[00101] Database- 245
[00102] Dynamic Routing Manager- 404
[00103] Distributed database- 408
[00104] Cache data store- 410
[00105] Distributed data lake-412
[00106] Dynamic activator- 414
[00107] Workflow manager- 418
[00108] Graph database-422
[00109] Message broker- 424
[00110] Operation and management module- 426
[00111] NBI-505
,CLAIMS:CLAIMS
We Claim:
1. A method (600) for configuring one or more attributes of nodes (125) in a network (105), the method (600) comprises the steps of:
receiving (605), by one or more processors (205), a request, from a user equipment (110) via a user interface (215), for configuring the one or more attributes of a first node (125a);
identifying (610), by the one or more processors (205), at least one configuration operation to configure the one or more attributes of the first node (125a) based on the received request;
receiving (615), by the one or more processors (205), a response from a second node (125b) in the network (105) pertaining to attributes associated with the second node (125b);
determining (620), by the one or more processors (205), if at least a portion of the one or more attributes of the first node (125a) matches with at least a portion of the one or more attributes associated with the second node (125b) based on comparing the request with the response;
based on determining that at least the portion of the one or more attributes of the first node (125a) matches with the attributes associated with the second node (125b), retrieving (625), by the one or more processors (205), a configuration logic from a cache data store (410) based on the identified at least one configuration operation from the request; and
dynamically configuring (630), by the one or more processors (205), the one or more attributes of the first node (125a) by applying the configuration logic retrieved from the cache data store (410).

2. The method (600) as claimed in claim 1, wherein the one or more attributes is in the form of at least one of, keys and values.

3. The method (600) as claimed in claim 1, wherein the at least one configuration operation pertains to, add, modify, delete, concatenate, match and replace the attribute keys and values.

4. The method (600) as claimed in claim 1, wherein the step of, receiving, a response from a second node (125b) in the network (105) pertaining to attributes associated with the second node (125b), includes the step of:
pinging, by the one or more processors (205), the second node (125b) to receive information pertaining to the attributes associated with the second node (125b).

5. The method (600) as claimed in claim 1, wherein the step of, retrieving, a configuration logic from a cache data store (410) based on the identified at least one configuration operation from the request, includes the steps of:
mapping, by the one or more processors (205), the identified at least one configuration operation with a plurality of configuration logics present in the cache data store (410);
identifying, by the one or more processors (205), the configuration logic based on the mapping.

6. A system (120) for configuring one or more attributes of nodes (125) in a network (105), the system comprising:
a transceiver (220), configured to, receive, a request, from a user equipment (110) via a user interface (215), for configuring the one or more attributes of a first node (125a);
an identification unit (225), configured to, identify, at least one configuration operation to configure the one or more attributes of the first node (125a) based on the received request;
the transceiver (220), configured to, receive, a response from a second node (125b) in the network (105) pertaining to attributes associated with the second node (125b);
a determining unit (230), configured to, determine, if at least a portion of the one or more attributes of the first node (125a) matches with the attributes associated with the second node (125b) based on comparing the request with the response;
based on determining that at least a portion of the one or more attributes of the first node (125a) matches with at least a portion of the one or more attributes associated with the second node (125b), a retrieving unit (235), configured to, retrieve, a configuration logic from a cache data store (410) based on the identified at least one configuration operation from the request; and
a configuring unit (240), configured to, dynamically configure, the one or more attributes of the first node (125a) by applying the configuration logic retrieved from the cache data store (410).

7. The system (120) as claimed in claim 6, wherein the one or more attributes is in the form of at least one of, keys and values.

8. The system (120) as claimed in claim 6, wherein the at least one configuration operation pertains to, add, modify, delete, concatenate, match and replace the attribute keys and values.

9. The system (120) as claimed in claim 6, wherein the transceiver, receives, a response from a second node (125b) in the network (105) pertaining to attributes associated with the second node (125b), by:
pinging, the second node (125b) to receive information pertaining to the attributes associated with the second node (125b).

10. The system (120) as claimed in claim 6, wherein the retrieving unit (235), retrieves, a configuration logic from a cache data store (410) based on the identified at least one configuration operation from the request, by:
mapping, the identified at least one configuration operation with a plurality of configuration logics present in the cache data store (410);
identifying, the configuration logic based on the mapping.

11. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to:
transmit, a request to configure one or more attributes of a first node (125a) to the one or more processors (205);
wherein the one or more processors (205) is configured to perform the steps as claimed in claim 1.