WO2025017662A1

WO2025017662A1 - Method and system for failure management in a network

Info

Publication number: WO2025017662A1
Application number: PCT/IN2024/051221
Authority: WO
Inventors: Aayush Bhatnagar; Ankit Murarka; Rizwan Ahmad; Kapil Gill; Rahul Verma; Arpit Jain; Shashank Bhushan; Kamal Malik; Chaitanya V MALI; Supriya De; Kumar Debashish; Tilala Mehul; Kothagundla Vinay Kumar
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-07-14
Filing date: 2024-07-13
Publication date: 2025-01-23
Anticipated expiration: 2026-01-14

Abstract

The present disclosure relates to a system (108) and a method (600) for failure management in a network (106) The system (108) includes a receiving unit (210) configured to receive a request from North Bound Interface (NBI). The system (108) further includes an execution unit (212) configured to execute a workflow pertaining to the request. The system (108) further includes an initiating unit (216) configured to initiate an availability check of the workflow at a network hosted by a South Bound Interface (SBI). The system (108) further includes a pausing unit (218) configured to pause the execution of the workflow in response to unavailability of the SBI. The system (108) further includes a routing unit (220) configured to route the paused workflow pertaining to the request to a queue.

Description

METHOD AND SYSTEM FOR FAILURE MANAGEMENT IN A NETWORK

FIELD OF THE INVENTION

[0001] The present invention relates to process and flow management in the network, more particularly relates to method and system for failure management in a network.

BACKGROUND OF THE INVENTION

[0002] The conventional telecom server handling process or flow in the network, usually shuts down a node upon detecting a process or flow failure. Shutting down a node increases the latency in the system and also affects the efficiency of the network.

[0003] Hence there is a need in the art for a system and a method to handle process or failure without shutting down the node.

SUMMARY OF THE INVENTION

[0004] One or more embodiments of the present disclosure provide a method and a system for failure management in a network.

[0005] In one aspect of the present invention, the system for failure management in the network is disclosed. The system includes a receiving unit configured to receive a request from North Bound Interface (NBI). The system further includes an execution unit configured to execute a workflow pertaining to the request. The system further includes an initiating unit configured to initiate an availability check of the workflow at a network hosted by a South Bound Interface (SBI). The system further includes a pausing unit configured to pause the execution of the workflow in response to unavailability of the SBI. The system further includes a routing unit configured to route the paused workflow pertaining to the request to a queue. [0006] In an embodiment, a fetching unit is configured to fetch the information regarding the workflow from a cache. In an embodiment, the receiving unit is further configured to receive a notification pertaining to the availability of the SBI.

[0007] In an embodiment, a resuming unit configured to resume the execution of the workflow in response to receipt of the notification pertaining to the availability of the SBI subsequent to pausing of the execution of the workflow.

[0008] In an embodiment, a transmitting unit is configured to transmit the workflow pertaining to the request to the network hosted by the SBI in response to resuming of the execution of the workflow.

[0009] In an embodiment, the SBI is deemed to be unavailable if an issue at the SBI results in failure of the execution of the workflow.

[0010] In another aspect of the present invention, the method of failure management in the network is disclosed. The method includes the step of receiving a request from a North Bound Interface (NBI). The method further includes the step of executing a workflow pertaining to the request. The method further includes the step of initiating an availability check of the workflow at a network hosted by a South Bound Interface (SBI). The method further includes the step of pausing the execution of the workflow in response to unavailability of the SBI based on initiating the availability check. The method further includes the step of routing the paused workflow pertaining to the request to a queue.

[0011] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive a request from a North Bound Interface (NBI). The processor is further configured to execute a workflow pertaining to the request. The processor is further configured to initiate an availability check of the workflow at a network hosted by a South Bound Interface (SBI). The processor is further configured to pause the execution of the workflow in response to unavailability of the SBI. The processor is further configured to route the paused workflow pertaining to the request to a queue.

[0012] 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

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

[0014] FIG. 1 is an exemplary block diagram of an environment for failure management in a network, according to one or more embodiments of the present invention;

[0015] FIG. 2 is an exemplary block diagram of a system for failure management in the network, according to one or more embodiments of the present invention; [0016] FIG. 3 is an exemplary architecture which can be implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;

[0017] FIG. 4 is a signal flow diagram for failure management in the network if a southbound interface (SBI) is unavailable, according to one or more embodiments of the present invention;

[0018] FIG. 5 is a signal flow diagram for failure management in the network if the SBI is available, according to one or more embodiments of the present invention; and

[0019] FIG. 6 is a schematic representation of a method for failure management in the network, according to one or more embodiments of the present invention.

[0020] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION

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

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

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

[0024] The present invention provides a method and system for handling an issue faced by a southbound interface due to which any process may get impacted, then Fulfillment Management System (FMS) will pause the process automatically with the help of Artificial Intelligence /Machine Learning (AI/ML). Later on, when the problem gets resolved then it will resume the same process.

[0025] FIG. 1 illustrates an exemplary block diagram of an environment 100 for failure management in a network, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for failure management in the network 106.

[0026] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”. [0027] In an embodiment, the UE 102 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 environment 100 includes the server 104 accessible via the network 106. The server 104 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.

[0029] The network 106 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 106 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.

[0030] The network 106 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 106 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.

[0031] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to manage the failure in the network 106. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.

[0032] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.

[0033] FIG. 2 is an exemplary block diagram of the system 108 for failure management in the network 106, according to one or more embodiments of the present invention.

[0034] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 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 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may 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.

[0036] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.

[0037] The database 208 is one of, but not limited to, a centralized database, a cloudbased 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 208 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] In order for the system 108 for failure management in the network 106, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 210, an execution unit 212, a fetching unit 214, an initiating unit 216, a pausing unit 218, a routing unit 220, a resuming unit 222, a transmitting unit 224 communicably coupled to each other for failure management in the network 106.

[0039] In one embodiment, the one or more modules includes, but not limited to, the receiving unit 210, the execution unit 212, the fetching unit 214, the initiating unit 216, the pausing unit 218, the routing unit 220, the resuming unit 222, the transmitting unit 224 can be used in combination or interchangeably for failure management in the network 106.

[0040] The receiving unit 210, the execution unit 212, the fetching unit 214 the initiating unit 216, the pausing unit 218, the routing unit 220, the resuming unit 222, the transmitting unit 224 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 202. 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 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.

[0041] In one embodiment, the receiving unit 210 is configured to receive a request from a North Bound Interface (NBI). The request includes, but not limited to, provisioning order (network inventory, service provisioning, & network configuration), data retrieval requests, control and management requests, provisioning requests, monitoring and alerting requests, diagnostic and troubleshooting requests, security management requests. The 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. The lower-level network component includes, but not limited to, switches, routers, Access Points (APs), Network Interface Cards (NICs), hubs, firewalls and network load balancers. The higher-level or more central component includes, but not limited to, Software-Defined Networking (SDN) controller, Network Management System (NMS), orchestration platform, policy management server, network analytics platform, Service Function Chaining (SFC) controller, and cloud orchestrator.

[0042] Upon receiving the request from the NBI, the fetching unit 214 is configured to fetch the information regarding a workflow pertaining to the received request from a cache. The workflow is a series of steps or tasks or communication links (for example, API) that are executed in a specific sequence to achieve a particular goal or objective. The workflows include, but are not limited to, policy-based workflow, service provisioning workflow, traffic engineering workflow, event-driven workflow, and analytics-driven workflow. The information regarding the workflow is at least one of metadata and attributes. The information regarding the workflow pertaining to the request includes, but not limited to, nodes, node names, addresses, API signatures, sequence of node, endpoints, parameter, schemas, and other related to provisioning of requests etc.

[0043] Upon fetching the information regarding the workflow pertaining to the received request, the execution unit 212 is configured to execute the workflow pertaining to the request.

[0044] After executing the workflow pertaining to the request, the initiating unit 216 is configured to initiate an availability check of the workflow at the network 106 hosted by a South Bound Interface (SBI). The SBI is the API or protocol that allows the higher-level component to send commands to lower- level network components. In an embodiment, the availability check can be health check or load status like actual capacity vs current capacity in central processing unit (CPU), memory, network etc. of microservices/ nodes that are received at an Artificial Intelligence/ Machine Learning (AI/ML) node. In an embodiment, the network 106 consists of multiple network nodes connected using REST API based SBI. These multiple network nodes together fulfil the particular request received from the NBI in the sequence or workflow.

[0045] In response to initiating the availability check of the workflow at the network 106 hosted by SBI, if the SBI is unavailable, the pausing unit 218 is configured to pause the execution of the workflow. The SBI is deemed to be unavailable if an issue at the SBI results in failure of the execution of the workflow. In an embodiment, the issue at the SBI may be the process failure at the SBI nodes.

[0046] Upon pausing the execution of the workflow, the routing unit 220 is configured to route the paused workflow pertaining to the request to a queue. The queue is a data structure or a resource that stores and manages a sequence of elements in the order they are received. The queue is at least one of request queue. Subsequent to pausing the execution of the workflow, if the SBI is available, then the receiving unit 210 is configured to receive a notification pertaining to the availability of the SBI.

[0047] Further subsequent to pausing the execution of the workflow, the resuming unit 222 is configured to resume the execution of the workflow, in response to receipt of the notification pertaining to the availability of the SBI.

[0048] In response to resuming of the execution of the workflow, the transmitting unit 224 is configured to transmit the workflow pertaining to the request hosted by the SBI. Therefore, the system 108 efficiently and effectively handles the process or a flow failure in the network 106. Further, the process or flow failure in the network 106 can be prevented. [0049] FIG. 3 is an exemplary architecture 300 implemented in the system 108 for failure management in the network 106, according to one or more embodiments of the present invention.

[0050] According to the exemplary embodiment, the system 108 may include, but may not be limited to, an operation and management unit 302, the workflow manager 304, the dynamic activator 318, a message broker 306, a graph database 308, a distributed data lake 310, a cache data store 312, a load balancer 314, the user interface 206, and a dynamic routing management 316.

[0051] In an embodiment, the request is received from the NBI via user interface 206. Upon receiving the request from the NBI, the request is transmitted to the workflow manager 304 via the operation and management unit 302 for creating the workflow pertaining to the request. Thereafter, the workflow manager 304 transmits the workflow pertaining to the request to the dynamic activator 318 for execution. In response to execution of the workflow pertaining to the request, the information regarding the workflow is stored at the distributed data lake 310 and a cache data store 312. The distributed data lake 310 is a data storage repository that centralizes, organizes, and protects large amounts of structured, semi-structured, and unstructured data pertaining to the details associated with the execution of the workflow. The cache data store 312 helps in storing recently stored data or frequently accessed data pertaining to the details associated with the execution of the workflows.

[0052] In an embodiment, the workflow manager 304 initiates the availability check of the workflow at the network hosted by the SBI. If the SBI is unavailable based on initiating the availability check, the execution of the workflow at the dynamic activator 318 is paused. The SBI is deemed to be unavailable if the issue at the SBI results in failure of the execution of the workflow. Subsequently, the paused workflow pertaining to the request is routed to the queue at the message broker 306. Further, the workflow manager 304 includes a message broker 306 and a graph database 308. The message broker 306 stores the paused workflow pertaining to the request in queue. [0053] In an embodiment, subsequent to pausing of the execution of the workflow, if the SBI is available, the notification pertaining to the availability of the SBI is received at the workflow manager 304. Upon receiving the notification pertaining to the availability of the SBI, the execution of the workflow is resumed at the dynamic activator 318. In response to resuming the execution of the workflow, the workflow pertaining to the request to the network 106 hosted by the SBI is transmitted to the dynamic activator 318 for execution.

[0054] In an embodiment, the load balancer 314 is communicably coupled with the dynamic activator 318 and the user interface 206. The load balancer 314 dynamically balances the multiple requests received from the NBI.

[0055] FIG. 4 is a signal flow diagram for failure management in the network 106 if a southbound interface (SBI) is unavailable, according to one or more embodiments of the present invention.

[0056] At step 402, the FMS receives the request from the NBI. The FMS is hosted in the server 104 and the NBI is communicably connected with the plurality of UEs 102 or consumer network nodes/network functions accessing the network 106. The plurality of UEs 102 like cellphone or mobile configured to send a request to the NBI.

[0057] At step 404, upon receiving the request from the NBI, the FMS fetches the details pertaining to the request from the CacheDataStore.

[0058] At step 406, upon fetching the details, the workflow is executed by the FMS pertaining to the request received from the NBI.

[0059] At step 408, upon executing the workflow pertaining to the request received from the NBI, the FMS forwards the executed workflow pertaining to the request to the AI/ML module. Further, the AI/ML module initiates the process of availability check of the workflow at the network 106 hosted by the SBI. [0060] At step 410, receiving the unavailability of the SBI at the AI/ML module after initiating the process of availability check of the workflow at the network 106 hosted by the SBI.

[0061] At step 412, after receiving the unavailability of the SBI, the AI/ML module transmits the pause request to the FMS for pausing the execution of the workflow.

[0062] At step 414, upon pausing the execution of the workflow at the FMS, the FMS routes the paused workflow pertaining to the request to the Queue (Request_Queue).

[0063] FIG. 5 is a signal flow diagram for failure management in the network 106 if the SBI is available, according to one or more embodiments of the present invention.

[0064] At step 502, the FMS receives a request from the NBI. The FMS is hosted in the server 104 and the NBI is communicably connected with the plurality of UEs 102 accessing the network 106. The plurality of UEs 102 like cellphone or mobile configured to send a request to the NBI.

[0065] At step 504, upon receiving the request from the NBI, the FMS fetches the details pertaining to the request from the CacheDataStore.

[0066] At step 506, simultaneously, the workflow is executed by the FMS pertaining to the request received from the NBI.

[0067] At step 508, upon executing the workflow pertaining to the request received from the NBI, the AI/ML module initiates the process of availability check of the workflow at the network 106 hosted by the SBI.

[0068] At step 510, receiving the notification on availability of the SBI at the AI/ML module after initiating the process of availability check of the workflow at the network 106 hosted by the SBI. [0069] At step 512, after receiving the notification on availability of the SBI, the AI/ML module transmits the resume request to the FMS for resuming the execution of the workflow.

[0070] At step 514, upon resuming the execution of the workflow at the FMS, the FMS transmits the request to Request_Queue for retrieving the data from the Request_Queue.

[0071] At step 516, upon retrieving the data from the Request_Queue, the workflow pertaining to the request is transmitted to the network 106 hasted by the SBI.

[0072] FIG. 6 is a flow diagram of a method 600 for failure management in the network 106, according to one or more embodiments of the present invention. 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.

[0073] At step 602, the method 600 includes the step of receiving the request from the NBI by the receiving unit 210. In response to receiving the request from the NBI, the method 600 comprises the step of fetching the information regarding the workflow pertaining to the request from a cache by the fetching unit 214.

[0074] At step 604, the method 600 includes the step of executing the workflow pertaining to the request by the execution unit 212

[0075] At step 606, the method 600 includes the step of initiating the availability check of the workflow at the network hosted by the SBI by the initiating unit 216.

[0076] At step 608, the method 600 includes the step of pausing the execution of the workflow in response to unavailability of the SBI based on initiating the availability check by the pausing unit 218. The SBI is deemed to be unavailable if an issue at the SBI results in failure of the execution of the workflow. [0077] At step 610, the method 600 includes the step of routing the paused workflow pertaining to the request to the queue by the routing unit 220. Further, the method comprises the step of receiving the notification pertaining to the availability of the SBI in response to availability of the workflow subsequent to pausing of the execution of the workflow. Further, the method comprises the step of resuming the execution of the workflow in response to receipt of the notification pertaining to the availability of the SBI by the resuming unit 222. Further, the method further comprises the step of transmitting the workflow pertaining to the request to the network hosted by the SBI in response to resuming of the execution of the workflow by the transmitting unit 224.

[0078] 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 202. The processor 202 is configured to receive the request from the NBI. The processor 202 is further configured to execute the workflow pertaining to the request. The processor 202 is further configured to initiate the availability check of the workflow at the network 106 hosted by the SBI. The processor 202 is further configured to pause the execution of the workflow in response to unavailability of the SBI. The processor 202 is further configured to route the paused workflow pertaining to the request to the queue.

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

[0080] The present disclosure incorporates technical advancement of efficiently and effectively handling the process or flow failure in the network. Further, the failure of the process or flow is prevented by using the present disclosure. In particular, when any southbound interface is facing any issue due to which a specific process/flow may get impacted, then FMS will pause that process. Due to this, any process failures will be prevented.

[0081] 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

[0082] Environment- 100

[0083] User Equipment (UE)- 102

[0084] Server- 104

[0085] Network- 106

[0086] System -108

[0087] Processor- 202

[0088] Memory- 204

[0089] User Interface- 206

[0090] Database- 208

[0091] Receiving Unit- 210

[0092] Execution Unit- 212

[0093] Fetching Unit- 214

[0094] Initiating Unit- 216

[0095] Pausing Unit- 218

[0096] Routing Unit- 220

[0097] Resuming Unit-222

[0098] Transmitting Unit- 224

[0099] Operation and Management Unit -302

[00100] Workflow Manager -304

[00101] Message Broker -306

[00102] Graph Database -308

[00103] Distributed Data Lake -310

[00104] Cache data store -312

[00105] Load Balancer -314

[00106] Dynamic Routing Manager -316

[00107] Dynamic Activator -318

Claims

We Claim:

1. A method (600) of failure management in a network, the method (600) comprising the steps of: receiving, by one or more processors (202), a request from a North Bound Interface (NBI); executing, by the one or more processors (202), a workflow pertaining to the request; initiating, by the one or more processors (202), an availability check of the workflow at a network hosted by a South Bound Interface (SBI); pausing, by the one or more processors (202), the execution of the workflow in response to unavailability of the SBI based on initiating the availability check; and routing, by the one or more processors (202), the paused workflow pertaining to the request to a queue.

2. The method (600) as claimed in claim 1 , wherein in response to receiving the request, the method (600) comprises the step of fetching the information regarding the workflow from a cache.

3. The method (600) as claimed in claim 1, wherein the method (600) comprises the step of, receiving, by the one or more processor (202), a notification pertaining to the availability of the SBI in response to availability of the workflow subsequent to pausing of the execution of the workflow.

4. The method (600) as claimed in claim 3, wherein the method (600) comprises the step of resuming, by the one or more processors (202), the execution of the workflow in response to receipt of the notification pertaining to the availability of the SBI.

5. The method (600) as claimed in claim 4, wherein the method further comprises the step of transmitting, by the one or more processors (202), the workflow pertaining to the request to the network hosted by the SBI in response to resuming of the execution of the workflow.

6. The method (600) as claimed in claim 1, wherein the SBI is deemed to be unavailable if an issue at the SBI results in failure of the execution of the workflow.

7. A system (108) for failure management in a network, the system (108) comprising: a receiving unit (210) configured to receive, a request from a North Bound Interface (NBI); an execution unit (212) configure to execute, a workflow pertaining to the request; an initiating unit (216) configured to initiate, an availability check of the workflow at a network hosted by a South Bound Interface (SBI); a pausing unit (218) configured to pause, the execution of the workflow in response to unavailability of the SBI; and a routing unit (220) configured to route, by the one or more processors, the paused workflow pertaining to the request to a queue.

8. The system (108) as claimed in claim 7, comprising a fetching unit (214) configured to fetch, the information regarding the workflow from a cache.

9. The system (108) as claimed in claim 7, wherein the receiving unit (210) is further configured to receive, a notification pertaining to the availability of the SBI.

10. The system (108) as claimed in claim 9, comprising a resuming unit (222) configured to resume, the execution of the workflow in response to receipt of the notification pertaining to the availability of the SBI subsequent to pausing of the execution of the workflow.

11. The system (108) as claimed in claim 10, further comprising a transmitting unit (224) configured to transmit, the workflow pertaining to the request to the network hosted by the SBI in response to resuming of the execution of the workflow.

12. The system (108) as claimed in claim 7, wherein the SBI is deemed to be unavailable if an issue at the SBI results in failure of the execution of the workflow.

13. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (202), cause the processor (202) to: receive, a request from a North Bound Interface (NBI); execute, a workflow pertaining to the request; initiate, an availability check of the workflow at a network hosted by a South Bound Interface (SBI); pause, the execution of the workflow in response to unavailability of the SBI; and route, the paused workflow pertaining to the request to a queue.