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
SYSTEM AND METHOD FOR MANAGING OPERATION OF 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 wireless communication networks, more particularly relates to a method and system for managing operation of the wireless communication network.
BACKGROUND OF THE INVENTION
[0002] In existing methods and systems, if a number of Application Programming Interfaces (APIs) sends requests to perform an operation (or task or workflow) to a north bound interface (or north bound system) then, the north bound interface receives the requests from the number of APIs and performs the operation (or task) one by one. It will be cumbersome task at the north bound interface and time-consuming process. In an example, if a first API and a second API send a first request and a second request to perform an operation (or task) to the north bound interface, the north bound interface receives the first request and the second request from the first API and the second API, respectively. The north bound interface performs the operation associated with the first request first and then performs the operation associated with the second request.
[0003] Further, if any new task associated with a business requirement is received at the north bound interface from a new API then, the existing methods and systems encounter multiple problems, such as, inflight orders, time to monetize, time to deploy and make it ready, redeployment in production etc. Hence, there is a need for systems and methods for managing operation of a network upon detecting the business requirement.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for managing operation of a network.
[0005] In one aspect of the present invention, a method for managing operation of the network is disclosed. The method includes the step of receiving, by one or more processors, at least one request pertaining to modification of the network based on a user requirement via a user interface. The method includes the step of processing, by the one or more processors, a workflow based on the at least one request. The process includes at least one of: creating or updating the workflow. The method includes the step of executing, by the one or more processors, the processed workflow and one or more active workflows to manage the operation of the network.
[0006] In one embodiment, the user requirement is at least addition of a service for a customer and setting up a Subscriber Identity Module (SIM) for a customer.
[0007] In another embodiment, modification of the network pertains to addition or removal of an interface or a node in the network.
[0008] In yet another embodiment, on processing the workflow, the method includes the step of storing, by the one or more processors, the workflow in a database.
[0009] In yet another embodiment, the one or more active workflows pertains to the operational workflows of the network.
[0010] In another aspect of the present invention, a system for managing operation of the network is disclosed. The system includes a receiving unit configured to receive at least one request pertaining to modification of the network based on a user requirement via a user interface. The system includes a processing unit configured to process a workflow based on the at least one request. The processing includes at least creating or updating the workflow. The system includes an executing unit configured to execute the processed workflow and one or more active workflows to manage the operation of the network.
[0011] 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 coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit the request to fetch the subscriber profile from the database. The UE is configured to render enriched data pertaining to the subscriber profile with the trace data utilizing the user interface.
[0012] 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 is disclosed. The processor is configured to receive at least one request pertaining to modification of the network based on a user requirement via a user interface. The processor is configured to process a workflow based on the at least one request, wherein the processing comprises at least creating or updating the workflow. The processor is configured to execute, the processed workflow and one or more active workflows to manage the operation of the network.
[0013] 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
[0014] 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.
[0015] FIG. 1 is an exemplary block diagram of an environment for managing operation of a network, according to one or more embodiments of the present invention;
[0016] FIG. 2 is an exemplary block diagram of the system for managing operation of the network, according to one or more embodiments of the present invention;
[0017] FIG. 3 is a schematic representation of workflow of the system of FIG. 2, according to one or more embodiments of the present invention;
[0018] 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 invention;
[0019] FIG. 5 is an operational flow diagram illustrating managing operation of the network, according to one or more embodiments of the present invention; and
[0020] FIG. 6 is a flow diagram illustrating a method for managing operation of the network, according to one or more embodiments of the present invention.
[0021] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0022] 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.
[0023] 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.
[0024] 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.
[0025] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing operation of a network 105, according to one or more embodiments of the present invention. The environment 100 includes a network 105, a User Equipment (UE) 110, a server 115, and a system 120. The UE 110 aids a user to interact with the system 120 for transmitting at least one request pertaining to modification of the network 105 to one or more processors 305 (shown in FIG. 3). The operation of a network involves the combination of monitoring, processing user requests, executing workflows, for optimization and failure management, and maintaining comprehensive records for traceability and analysis. This approach ensures efficient, reliable, and scalable network operations.
[0026] 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 UE 110 from 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.
[0027] In an embodiment, each of the first UE 110a, the second UE 110b, and the third UE 110c 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.
[0028] 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.
[0029] 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, a defense facility, or any other facility that provides content.
[0030] The environment 100 further includes the plurality of network nodes 125. The term plurality of network nodes refers to a group or collection of plurality of network nodes within the network 105. The plurality of network nodes 125 are individual devices or points within the network 105 where data can be created, received, transmitted, or stored. In an embodiment, the plurality of network nodes 125 include, but not limited to, servers, routers, and switches.
[0031] The environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first UE110a, the second UE110b, and the third UE110c via the network 105. The system 120 is configured for stitching the subscriber profile with the trace data. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity, as per multiple embodiments of the present invention.
[0032] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0033] FIG. 2 is an exemplary block diagram of the system 108 for managing operation of the network 105, according to one or more embodiments of the present invention.
[0034] The system 120 includes a processor 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 or more processors 205, or to be more specific will be explained with respect to the processor 205 and should nowhere be construed as limiting the scope of the present disclosure. The one or more processor 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.
[0035] 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 create or share data packets over a network service. The memory 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0036] The user interface 215 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), 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. Examples of the one or more components include, but are not limited to, the UE110, and the database 245.
[0037] The database 245 is configured to store the number of workflows. 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, a cache databases, and so forth. The foregoing examples of database 250 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0038] Further, the processor 205, 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.
[0039] In order for the system 120 to manage operation of the network 105. The processor 205 includes a receiving unit 220, a processing unit 225, an executing unit 230, and a storing unit 235 communicably coupled to each other. In an embodiment, operations and functionalities of the receiving unit 220, the processing unit 225, the executing unit 230, and the storing unit 235 can be used in combination or interchangeably.
[0040] The receiving unit 220 is configured to receive at least one request pertaining to modification of the network 105 based on a user requirement via the user interface 215. In an embodiment, the at least one request relates to adding a new service, setting up a SIM card, or adding a new network node. In an embodiment, the user requirement is at least addition of a service for a customer and setting up a Subscriber Identity Module (SIM) for a customer. In one embodiment, modification of the network 105 pertains to addition or removal of an interface or a node in the network 105. The interface/node is a connection point within the network 105 that can create, receive, or transmit data. The interface/node can be devices or points that serve as a redistribution point or an endpoint of communication within the network 105.
[0041] The at least one request is classified based on its type (e.g., service addition, SIM setup, node addition). The workflow consists of the plurality of network nodes 125. Before creation of the workflow, the plurality of network nodes 125 needs to be created. Once the plurality of network nodes 125 are created, in order to this, the system 120 is configured to create the workflow. The classified at least one request is mapped to the created workflow. The created workflow is validated to ensure it meets all the requirements of the at least one request. The workflow might need to be approved by a network administrator or an automated approval system before processing.
[0042] In an embodiment, the workflow for the at least one request includes, but not limited to, a service addition workflow, a SIM setup workflow, and a node addition workflow, and the like. Let’s consider for an example, the user submits the node addition request. The integration of the new network node, including location, network design, and configuration are planned. The necessary components for a new network node such as a fifth network node 510e (shown in FIG.5) are procured. The new network node is installed at the designated location. The new network node is configured to ensure it integrates seamlessly with existing network elements. The new network node is deployed on runtime before making the provision. Further, continuously monitor the new network node to ensure stability and performance.
[0043] Upon receiving the at least one request pertaining to modification of the network 105, the processing unit 225 is configured to process the workflow based on the at least one request. The processing includes at least creating or updating the workflow. The workflow is created to handle the addition of the new service, ensuring all necessary configurations and provisioning steps are included. The processing unit 225 is configured to update the workflow by adding new steps to accommodate the at least one request based on the requirements. Let us consider, the fifth network node 510e needs to be added to the workflow. The workflow is sequentially processed from one network node to another network node. For example, processing the workflow from a first network node 510a (shown in FIG.5) to a second network node 510b (shown in FIG.5), the second network node 510b to a third network node 510c (shown in FIG.5), and the third network node 510c to a fourth network node 510d (shown in FIG.5). Based on the requirements, the fifth network node 510e needs to be added to the workflow. In order to this, the fifth network node 510e is added to the same workflow on runtime without impacting the running process.
[0044] Upon processing the workflow, the executing unit 230 is configured to execute the processed workflow and one or more active workflows to manage the operation of the network 105. In an embodiment, the one or more active workflows pertains to operational workflows of the network 105. The processed workflow coordinates with other system components to implement the changes such as network services. In an embodiment, the network services are provisioned for the customer, and the SIM card is configured and activated. The fifth network node 510e is added and configured, expanding the network’s coverage.
[0045] As per one embodiment, the one or more active workflows are the set of processes or tasks that are currently being executed within the system 120. The one or more active workflows are designed to manage various operations by following predefined steps and rules, ensuring that each task is completed in a correct order and within the specified parameters. The one or more active workflows can span across different components or units of the system 120, coordinating actions and the data flow to achieve desired outcomes.
[0046] Upon executing the processed workflow, the storing unit 235 is configured to store the workflow in the database 245 on processing of the workflow. Upon executing the processed workflow, the storing unit 235 is configured to store the details of the executed workflows in the database 245.
[0047] Let us consider for an example of stored workflow in the database 245,
• Request ID: 12345
• Workflow Type: New Service Provisioning, SIM Card Setup, Network Node Addition
• Status: Completed
• Timestamp: YYYY-MM-DD HH:MM
• Details:
• Service Provisioning: Success
• SIM Card Setup: Success
• Network Node Addition: Success
[0048] By doing so, the system 120 is configured to automate and streamline the network modification processes, reducing manual intervention, and supports a variety of network modifications, enabling easy expansion or reconfiguration, and improves user experience.
[0049] FIG. 3 is a schematic representation of the workflow of the system of FIG. 2, according to one or more embodiments of the present invention. More specifically, FIG. 3 illustrates the system 120 configured for managing operation of the network 105. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0050] As mentioned earlier in FIG.1, In an embodiment, the first UE 110a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, modems, routers, switches, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity. The scope of the first UE 110a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications. This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms. In an embodiment, the first UE 110a can be associated with multiple users. Each of the first UE 110a is communicatively coupled with the processor 205.
[0051] The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120. 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 fetch the subscriber profile from the first database 240.
[0052] Furthermore, the one or more primary processors 305 within the first UE 110a are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor 205 capability to manage operation of the network 105. The operational synergy between the one or more primary processors 305 and the additional processors, guided by the executable instructions stored in the memory 310.
[0053] As mentioned earlier 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.
[0054] Further, the processor 205 includes the receiving unit 220, the processing unit 225, the executing unit 230, and the storing unit 235. The operations and functions of the receiving unit 220, the processing unit 225, the executing unit 230, and the storing unit 235 are already explained in FIG. 2. Hence, 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. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0055] FIG. 4 is an exemplary block diagram of an architecture 400 that can be implemented in the system of FIG. 3, according to one or more embodiments of the present invention.
[0056] In an embodiment, the architecture 400 pertains to the system 120 which includes, the user interface 215, a dynamic routing manager 404, a distributed database 408 having a distributed data lake 412, a 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.
[0057] In an embodiment, the user interface 215 provides an interface for the user to transmit the at least one request pertaining to modification of the network 105. Further, the user interface 215 receives the at least one request from the user and creates the workflow and transmits it to the workflow manager 418 via the operation and management module 426. The workflow manager 418 performs the necessary functions to execute the at least one request.
[0058] 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.
[0059] The workflow manager 418 is configured to instruct the dynamic activator 414, to execute the state for the workflow for managing the operation of the network 105. 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.
[0060] The operation of workflow is stored in the distributed data lake 412 is included in the distributed database 408. The operation and management module 426 communicates with the workflow manager 418 and the dynamic activator 414. The operation and management module 426 is communicated with a user interface service module (e.g., the user interface 215, and the dynamic routing manager 404.
[0061] Further, the workflow manager 418 communicated with the dynamic activator 414. Further, the workflow manager 418 communicates with the user interface service module. In one embodiment, the storing unit 235 of the processor 205 includes the distributed database 408 having the distributed data lake 412, the cache data store 410 and the graph database 422 in combination which configured to store data pertaining to the modification of the network 105.
[0062] 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 a transmitter to the messaging protocol of a 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.
[0063] 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.
[0064] The load balancer 428 is a device or software application that distributes the network 105 or application traffic across different types of 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.
[0065] In an embodiment, the load balancer 428 is communicably coupled with the dynamic activator 414 and the user interface 215. The load balancer 428 dynamically distributes the network traffic pertaining to the at least one request among the other entities in the system 120.
[0066] The user creates the at least one workflow (or operation or task) using the user interface 215 and the at least one request is stored in the graph database 422. The 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. The workflow manager 418 executes the at least one workflow, and relevant operations associated with the at least one request is stored in the distributed database 408 and the cache data store 410 by using the graph database 422.
[0067] The user can update or create the new workflow using the user interface 215 and the new workflow is stored in the graph database 422. Further, the workflow manager 418 executes the new workflow and relevant operations associated with the new workflow stored in the distributed database 408 and the cache data store 410 by using the graph database 422. Similar operations are applicable for removing the workflow in the system 120.
[0068] FIG. 5 is an operational block diagram for managing operation of the network, according to one or more embodiments of the present disclosure.
[0069] In an embodiment, the block diagram 500 includes a North Bound Interface (NBI) 505, the system 120, a first network node 510a, a second network node 510b, a third network node 510c, a fourth network node 510d, and a fifth network node 510e. The number of network nodes 510a-510e are illustrative purpose only and is not limiting the scope of the invention. The first network node 510a, the second network node 510b, the third network node 510c, the fourth network node 510d, and the fifth network node 510e are coupled with each other. The first network node 510a, the second network node 510b, the third network node 510c, the fourth network node 510d, and the fifth network node 510e can be, for example, but not limited to a base station, a server, a network entity or the like.
[0070] The first network node 510a is associated with a first API. The second network node 510b is associated with a second API. The third network node 510c is associated with a third API. The fourth network node 510d is associated with a fourth API. The fifth network node 510e is associated with a fifth API.
[0071] At step 1, the NBI 505 sends a provisioning request to the system 120. The provisioning request is made within the network operation team to set up, configure, or manage resources, services, or accounts. The provisioning process involves allocating and configuring the necessary resources to ensure the requested service or resource is operational and meets specified requirements. Based on the provisioning request, at step 2, the system 120 sends an acknowledgement back to the NBI 505.
[0072] At step 5a, the system 120 processes the provisioning request and makes provisioning on the first network node 510a. At step 5b, the first network node 510a sends a response related to the processed provisioning request to the system 120. Further, the system 120 analyses the response of a success rate and a failure rate. In an embodiment, the system 120 sets the condition for switching from one network node to another network node. The condition may include at least one attribute for meeting the business requirement. In an embodiment, the condition may include at least one state for defining a level of an operation. The condition is set by the user or the system 120. In an example, the system 120 moves to the operation for the second network node 510b upon receiving an 80-percentage success rate at the first network node 510a. In another example, the system 120 moves to operation for the second network node 510b upon receiving a 10-percentage failure rate at the first network node 510a.
[0073] At step 5c, the system 120 processes the provisioning request and makes provisioning on the second network node 510b. At step 5d, the second network node 510b sends a response related to the processed provisioning request to the system 120. At step 5e, the system 120 processes the provisioning request and makes provisioning on the third network node 310c. At step 5f, the third network node 310c sends a response related to the processed provisioning request to the system 120. At step 5g, the system 120 processes the provisioning request and makes provisioning on the fourth network node 510d. At step 5h, the fourth network node 510d sends a response related to the processed provisioning request to the system 120.
[0074] At step 5i, the system 120 processes the provisioning request and makes provisioning on the fifth network node 510e. The provisioning actions include configurations, resource allocations, or service setups required for the request. The provisioning request is made within the network operation team to set up, configure, or manage resources, services, or accounts. The provisioning process involves allocating and configuring the necessary resources to ensure the requested service or resource is operational and meets specified requirements. Before processing the provisioning request, on the fifth network node 510e, the system 120 is configured to dynamically add the fifth network node 510e at runtime. At step 5j, the fifth network node 510e sends a response related to the processed provisioning request to the system 120. The fifth network node 510e is added on runtime before making the provision on it.
[0075] FIG. 6 is a flow diagram illustrating a method 600 for managing operation of the network 105, according to one or more embodiments of the present disclosure. For the purpose of description, the method 600 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 at least one request pertaining to modification of the network 105 based on the user requirement via the user interface 215 by the receiving unit 220. In an embodiment, the at least one request relates to adding a new service, setting up a SIM card, or adding a new network node. In an embodiment, the user requirement is at least addition of a service for a customer and setting up a Subscriber Identity Module (SIM) for a customer. In one embodiment, modification of the network 105 pertains to addition or removal of an interface or a node in the network 105.
[0077] At step 610, the method 600 includes the step of processing the workflow based on the at least one request by the processing unit 225 based on receiving the at least one request pertaining to modification of the network 105. The processing includes at least creating or updating the workflow. The workflow is created to handle the addition of the new service, ensuring all necessary configurations and provisioning steps are included. Another workflow is created for the SIM card setup, detailing the steps required to configure and activate the SIM. An existing workflow is updated to include steps for adding a new network node, ensuring it is integrated into the network 105 and configured properly.
[0078] At step 615, the method 600 includes the step of executing the processed workflow and one or more active workflows to manage the operation of the network 105 by the executing unit 230. In an embodiment, the one or more active workflows pertains to operational workflows of the network 105. The processed workflow coordinates with other system components to implement the changes such as network services are provisioned for the customer, and the SIM card is configured and activated. The fifth network node 510e is added and configured, expanding the network’s coverage.
[0079] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to receive at least one request pertaining to modification of the network 105 based on a user requirement via a user interface 215. The processor 205 is configured to process a workflow based on the at least one request. The processing includes at least creating or updating the workflow. The processor 205 is configured to execute the processed workflow and one or more active workflows to manage the operation of the network 105.
[0080] 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.
[0081] The present disclosure provides technical advancement for fully configuring the network nodes and also changes can be made by an end user through the user interface only. If any provisioning needs to be done on the four network nodes and the workflow is created and running. Due to the additional requirement, if the provisioning needs to be done on the fifth network node also can be added dynamically from the system. By doing so, the present disclosure saves the complexity, development, time and integration effort. Further, the system is configured to automate and streamline the network modification processes, reducing manual intervention, and supports a variety of network modifications, enabling easy expansion or reconfiguration, and improves user experience.
[0082] 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

[0083] Environment - 100
[0084] Network-105
[0085] User equipment- 110
[0086] Server - 115
[0087] System -120
[0088] Processor - 205
[0089] Memory - 210
[0090] User interface-21
[0091] Receiving unit – 220
[0092] Processing unit– 225
[0093] Executing unit – 230
[0094] Storing unit– 235
[0095] Database-240
[0096] Primary processor- 305
[0097] Memory- 310
[0098] Dynamic routing manager- 404
[0099] Distributed database- 408
[00100] Distributed data lake- 412
[00101] Cache data store- 410
[00102] Dynamic activator- 414
[00103] Workflow manager- 418
[00104] Graph database- 422
[00105] Message broker- 424
[00106] Operation and management module- 426
[00107] Load balancer- 428
[00108] NBI- 505
[00109] First network node-510a
[00110] Second network node-510b
[00111] Third network node- 510c
[00112] Fourth network node-510d
[00113] Fifth network node-510e

,CLAIMS:CLAIMS
We Claim:
1. A method (600) of managing operation of a network (105), the method (600) comprising the steps of:
receiving (605), by one or more processors (205), at least one request pertaining to modification of the network (105) based on a user requirement via a user interface (215);
processing (610), by the one or more processors (205), a workflow based on the at least one request, wherein the processing comprises at least one of: creating or updating of the workflow; and
executing (615), by the one or more processors (205), the processed workflow and one or more active workflows to manage the operation of the network (105).

2. The method (600) as claimed in claim 1, wherein the user requirement is at least addition of a service for a customer and setting up a Subscriber Identity Module (SIM) for a customer.

3. The method (600) as claimed in claim 1, wherein modification of the network (105) pertains to addition or removal of an interface or a node in the network (105).

4. The method (600) as claimed in claim 1, wherein on processing the workflow, the method (600) comprises the step of storing, by the one or more processors (205), the workflow in a database (240).

5. The method (600) as claimed in claim 1, wherein the one or more active workflows pertains to operational workflows of the network (105).

6. A system (120) for managing operation of a network (105), the system (120) comprising:
a receiving unit (220) configured to receive, at least one request pertaining to modification of the network (105) based on a user requirement via a user interface (215);
a processing unit (225) configured to process, a workflow based on the at least one request, wherein the processing comprises at least creating or updating of the workflow;
an executing unit (230) configured to execute, the processed workflow and one or more active workflows to manage the operation of the network (105).

7. The system (120) as claimed in claim 6, wherein the user requirement is at least addition of a service for a customer and setting up a Subscriber Identity Module (SIM) for a customer.

8. The system (120) as claimed in claim 6, wherein modification of the network (105) pertains to addition or removal of an interface or a node in the network (105).

9. The system (120) as claimed in claim 6, comprising a storing unit (235) configured to store, the workflow in a database (240) on processing of the workflow.

10. The system (120) as claimed in claim 6, wherein the one or more active workflows pertains to operational workflows of the network (105).

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 at least one request pertaining to modification of the network (105) to the one or more processors (205);
wherein the one or more processors (205) are configured to perform the steps as claimed in claim 1.