WO2025057246A1

WO2025057246A1 - Method and system to manage one or more tasks in a network

Info

Publication number: WO2025057246A1
Application number: PCT/IN2024/051766
Authority: WO
Inventors: Aayush Bhatnagar; Ankit Murarka; Rizwan Ahmad; Kapil Gill; Arpit Jain; Shashank Bhushan; Jugal Kishore; Meenakshi Sarohi; Kumar Debashish; Supriya Kaushik DE; Gaurav Kumar; Kishan Sahu; Gaurav Saxena; Vinay Gayki; Mohit Bhanwria; Durgesh KUMAR; Rahul Kumar
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-09-14
Filing date: 2024-09-16
Publication date: 2025-03-20
Anticipated expiration: 2026-03-14

Abstract

The present disclosure relates to a system (108) and a method (500) to manage one or more tasks in a network (106) The system (108) includes a transceiver (210) to, receive, a request from an Inventory Manger (IM) (222). The system (108) includes a checking unit (214) to check, from a storage unit (212), whether the one or more tasks are pre-scheduled or not pre-scheduled. The system (108) includes a creating unit (216), configured to create the one or more tasks at the storage unit (212). The system (108) includes the transceiver (210) to transmit a response to the IM (222) and receive instructions from the IM (222) to perform the one or more tasks. The system (108) includes a trigger unit (218), to trigger one or more tasks at a scheduled time. The system (108) includes a notifying unit (220), to notify the IM (222).

Description

METHOD AND SYSTEM TO MANAGE ONE OR MORE TASKS IN A

NETWORK

FIELD OF THE INVENTION

[0001] The present invention relates to communication network management, more particularly relates to a method and a system to manage one or more tasks in a network.

BACKGROUND OF THE INVENTION

[0002] A communication network comprises of many network elements which are configured to operate in specific manners to improve credibility of the communication network. The network incorporates inventories to safe -keep resources and mechanism to efficiently distribute resources to all NFs (Network Functions) in the network so as to process the service requests. Inventory Management (IM) service maintains the virtual inventory and limited physical inventory. The IM maintains the relation between physical and virtual resources with respect to overlay to manage storage memory allocation. Also, the IM describes physical and virtual resources in view of different attributes using updates from external micro-service. Thus, the data accuracy of inventory depends on the micro-services which create, update, delete these resources and at the same time update these events with IM. Other services can query IM relations, attributes etc. using Query APIs provided by IM.

[0003] There are many tasks and services which are run by various micro-services, and they utilize network resources for that. There has to be constant monitoring to ensure freeing the resources after the task is performed. In order to complete various call flows, many services require scheduling tasks to perform. Implementing the same feature in every service is time consuming and makes things complicated. There is a need to introduce a dedicated service and interface to accomplish regulated scheduling jobs and with provision to cancel a scheduled job if required. [0004] There is a therefore a requirement for a system and method thereof to incorporate a request when any external micro-service wants to schedule a task.

[0005] Further, there is a requirement for a system and method to have an interface which enables efficient scheduling of tasks for micro-services to perform certain jobs such as reserving resources and freeing resources.

SUMMARY OF THE INVENTION

[0006] One or more embodiments of the present disclosure provide a method and system to manage one or more tasks in a network.

[0007] In one aspect of the present invention, the system to manage the one or more tasks in the network is disclosed. The system includes a transceiver configured to, receive, a request from an Inventory Manger (IM) to schedule one or more tasks in the network. The system further includes a checking unit, configured to, check, from a storage unit, whether the one or more tasks are pre-scheduled or not pre-scheduled. The system further includes a creating unit, configured to create the one or more tasks at the storage unit, when the one or more tasks are not pre-scheduled. The system further includes the transceiver configured to transmit to the IM, a response related to the one or more tasks scheduled at the storage unit and receive, instructions from the IM to perform the one or more tasks based on transmitting the response to the IM. The system further includes a trigger unit, configured to trigger one or more tasks at a scheduled time based on the instructions received from the IM. The system further includes a notifying unit, configured to notify the IM, once the one or more tasks are completed.

[0008] In an embodiment, the request is a Hypertext Transfer Protocol (HTTP) request, the request includes details of the one or more tasks which are required to be scheduled at the storage unit.

[0009] In an embodiment, the creating unit, stores, the one or more tasks at the storage unit once the one or more tasks are created. [0010] In an embodiment, the response is at least one of a failure response when the one or more tasks are pre-scheduled at the storage unit.

[0011] In an embodiment, the response is at least one of a success response when the one or more tasks are created and scheduled.

[0012] In an embodiment, the checking unit is configured to check from a storage unit whether the one or more tasks are pre-scheduled or not pre-scheduled, by extracting, data related to the one or more tasks from the received request. The checking unit is further configured to check if the extracted data is present at the storage unit, if determined that the extracted data is present at the storage unit, the checking unit, infers that the one or more tasks are pre-scheduled at the storage unit and if determined that the extracted data is not present at the storage unit, the checking unit, infers that the one or more tasks are not pre-scheduled at the storage unit.

[0013] In an embodiment, the one or more tasks include at least one of, instantiation, termination or deletion of one or more network functions.

[0014] In an embodiment, the trigger unit, triggers the one or more tasks at the scheduled time based on the instructions received from the IM, by identifying, a type of the one or more tasks and reserving or un-reserving, one or more resources for the one or more tasks based on the type of the tasks.

[0015] In an embodiment, when the one or more tasks is instantiation, the trigger unit reserves the one or more resources for instantiation of the one or more network functions.

[0016] In an embodiment, the trigger unit un-reserves the one or more resources once the instantiation of the one or more network functions is completed.

[0017] In an embodiment, when the instantiation is not completed within a predefined time interval, the trigger unit un-reserves the one or more resources allocated to the one or more network functions. [0018] In an embodiment, the trigger unit further changes, the status of the one or more resources depending on a usage of the one or more resources in the network.

[0019] In another aspect of the present invention, the method to manage the one or more tasks in the network is disclosed. The method includes the step of receiving a request from an Inventory Manger (IM) to schedule one or more tasks in the network. The method further includes the step of checking from a storage unit whether the one or more tasks are pre-scheduled or not pre-scheduled. The method further includes the step of creating one or more tasks at the storage unit, when the one or more tasks are not pre-scheduled. The method further includes the step of transmitting to the IM a response related to the one or more tasks scheduled at the storage unit. The method further includes the step of receiving instructions from the IM to perform the one or more tasks based on transmitting the response to the IM. The method further includes the step of triggering the one or more tasks at a scheduled time based on the instructions received from the IM. The method further includes the step of notifying the IM, once the one or more tasks are completed.

[0020] 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 an Inventory Manger (IM) to schedule one or more tasks in the network. The processor is configured to check, from a storage unit, whether the one or more tasks are pre-scheduled or not pre-scheduled. The processor is configured to create the one or more tasks at the storage unit, when the one or more tasks are not pre-scheduled. The processor is configured to transmit, to the IM, a response related to the one or more tasks scheduled at the storage unit. The processor is configured to receive instructions from the IM to perform the one or more tasks based on transmitting the response to the IM. The processor is configured to trigger one or more tasks at a scheduled time based on the instructions received from the IM. The processor is configured to notify the IM, once the one or more tasks are completed. [0021] 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

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

[0023] FIG. 1 is an exemplary block diagram of an environment to manage one or more tasks in a network, according to one or more embodiments of the present invention;

[0024] FIG. 2 is an exemplary block diagram of a system to manage the one or more tasks in the network, according to one or more embodiments of the present invention;

[0025] FIG. 3a is an exemplary representation of an interface in the network and FIG.3b is a block diagram of an architecture of the system to manage the one or more tasks in the network utilizing an Inventory Manager (IM)_Platform Scheduler & Cron Job Micro Service (PSC) interface, according to one or more embodiments of the present invention;

[0026] FIG. 4 is a signal flow diagram pertaining to the system to manage the one or more tasks in the network, according to one or more embodiments of the present invention;

[0027] FIG. 5 is a schematic representation of a method of system to manage the one or more tasks in the network, according to one or more embodiments of the present invention; and

[0028] FIG. 6 illustrates an architecture framework (e.g., MANO architecture framework), in which the present invention can be implemented in accordance with one or more embodiments of the present invention.

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

DETAILED DESCRIPTION OF THE INVENTION

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

[0031] 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. [0032] 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.

[0033] The present invention relates to a dedicated interface for scheduling tasks for other micro-services, including reserving resources, un-reserving resources, deleting and adding tasks. The present invention includes a policy scheduler and Cron job manager (PSC), the interface, a database and a scheduler. In the present invention, a Physical and Virtual Inventory Manager (PVIM) sends data to PSC which schedules a task as per requests received from other micro-services to be executed at a configured time by means of the interface. If the requirement to perform the scheduled task ceases, then the PSC is also configured to cancel the task. Thus, optimum task management is achieved. The interface is compatible with all other micro-services and therefore, scheduling tasks and performing the same is done with ease.

[0034] FIG. 1 illustrates an exemplary block diagram of an environment 100 to manage one or more task in a network 106, 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, the network 106 and a system 108 communicably coupled to each other to manage the one or more tasks in the network 106. [0035] The one or more tasks refer to actions or operations that need to be executed within the network 106. The one or more tasks include, but not limited to, instantiation of network functions, termination of network functions, deletion of network functions, scaling, monitoring and resources reservation. The managing of the one or more tasks in the network 106 involves a structured workflow, ensuring that the tasks are executed efficiently, resources are allocated correctly, and the network operates smoothly. The structured workflow includes, but is not limited to, task scheduling and request handling, task creation and storage, resources management, task execution, task monitoring and status update, handling failures and timeouts, and task completion.

[0036] 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”.

[0037] 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 a smartphone, 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.

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

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

[0040] 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 V OIP or some combination thereof.

[0041] 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 one or more tasks 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. [0042] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.

[0043] FIG. 2 is an exemplary block diagram of the system 108 to manage the one or more tasks in the network 106, according to one or more embodiments of the present invention.

[0044] 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. In an embodiment, an inventory manager (IM) 222 is communicably coupled with the system 108. 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 processor 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.

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

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

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

[0048] In order for the system 108 to manage the one or more tasks 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 transceiver 210, a storage unit 212, a checking unit 214, a creating unit 216, a trigger unit 218, and a notifying unit 220 communicably coupled to each other for managing the one or more tasks in the network 106.

[0049] In one embodiment, the one or more modules, the transceiver 210, the storage unit 212, the checking unit 214, the creating unit 216, the trigger unit 218, and the notifying unit 220 can be used in combination or interchangeably for managing the one or more tasks in the network 106.

[0050] The transceiver 210, the storage unit 212, the checking unit 214, the creating unit 216, the trigger unit 218, and the notifying unit 220 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.

[0051] In one embodiment, the transceiver 210 is configured to receive a request from the IM 222. The IM 222 is responsible for overseeing and managing the resources and assets within the network 106. The IM 222 ensures the availability of both physical and virtual resources required to support various network services and functions. The IM 222 includes, but is not limited to resource tracking, task scheduling, orchestration, provisioning, and resources status updates. In an embodiment, the IM 222 is at least one of Physical and Virtual Inventory Manager (PVIM).

[0052] The request received from the IM 222 pertains to schedule the one or more tasks in the network 106. The one or more tasks include at least one of, instantiation, termination or deletion of one or more network functions. The one or more network functions refer to distinct functional components within the network 106 that perform tasks necessary for the operation of telecommunications services. The one or more network functions includes, but not limited to, routing, firewalling, load balancing, or packet inspection, Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), and Unified Data Management (UDM). The instantiation of one or more network functions refers to the process of creating and launching one or more network functions to make them operational. The termination of one or more network functions refers to the controlled shutdown or stopping of one or more network functions that are no longer required. The deletion of the one or more network functions refers to the complete removal of network functions, including their configurations and associated data, from the system 108.

[0053] The request is at least one of, Hypertext Transfer Protocol (HTTP) request. The request includes details of the one or more tasks which are required to be scheduled at the storage unit 212. The request is a communication sent by the IM 222 to inform the system 108 that the one or more tasks that need to be scheduled and executed in the network 106. The request includes, but is not limited to task type, task identifier (ID), task parameters, scheduling time, resource requirements, dependencies, task expiration, and error handling instructions.

[0054] Upon receiving the request from the IM 222, the checking unit 214 is configured to check from the storage unit 212 whether the one or more tasks are prescheduled or not pre-scheduled. The pre- scheduling refers to the process of determining and reserving the one or more tasks in advance, before they are executed in the system 108. Further, the checking unit 214 checks from the storage unit 212 whether the one or more tasks are pre-scheduled or not pre-scheduled by extracting the data related to the one or more tasks from the received request. The data refers to the information related to the one or more tasks included in the received request. The data includes but is not limited to, task identifier (ID), task type, task parameter, scheduling information, resources requirements, dependencies, priority. Upon extracting the data related to the one or more tasks, the checking unit 214 is configured to check whether the extracted data is present in the storage unit 212. Upon checking if the extracted data is present at the storage unit 212, the one or more tasks are determined to be pre-scheduled at the storage unit 212. Alternatively, upon checking if the extracted data is not present at the storage unit 212, the one or more tasks are determined to be not pre-scheduled at the storage unit 212. [0055] Upon checking if the one or more tasks are not pre-scheduled at the storage unit 212, the creating unit 216 is configured to create the one or more tasks at the storage unit 212. Subsequently, once the one or more tasks are created, the creating unit 216 stores the one or more tasks at the storage unit 212. Upon creating and storing the one or more tasks at the storage unit 212, the transceiver 210 is configured to transmit a response to the IM 222. The response is related to the scheduling of the one or more tasks at the storage unit 212. When the one or more tasks are pre-scheduled at the storage unit 212, the response transmitted to the IM 222 is at least one of a failure response. The failure response is a message sent to the IM 222 indicating that the requested one or more tasks are already pre-scheduled at the storage unit 212. Alternatively, when the one or more tasks are created and scheduled at the storage unit 212, the response transmitted to the IM 222 is at least one of a success response. The success response is a message sent to the IM 222 indicating that the requested one or more tasks have been successfully created and scheduled at the storage unit 222.

[0056] Upon transmitting the response to the IM 222, the transceiver 210 is configured to receive instructions from the IM 222 to perform the one or more tasks. In particular, upon receiving the success response, the IM 222 transmits the instructions to perform the one or more tasks. Upon receiving the instructions from the IM 222, the trigger unit 218 is configured to trigger the one or more tasks at a scheduled time. The scheduled time is a time period determined in advance when the one or more tasks are intended to be executed. The trigger unit 218 triggers the one or more tasks at the scheduled time by identifying a type of the one or more tasks. The type of the one or more tasks includes, but is not limited to, instantiation, termination, deletion. Upon identifying the type of the one or more tasks, the trigger unit 218 is configured to reserve or un-reserve one or more resources for the one or more tasks based on the type of the one or more tasks. The one or more resources refer to the various types of computational, storage, and network-related assets that are required for the operation, instantiation, termination, or deletion of network functions. The one or more resources includes Central Processing Unit (CPU), memory, disk space, and bandwidth. Reserving the one or more resources refers to the allocation of one or more resources, such as computing power, memory, storage, and bandwidth, that are necessary to perform tasks related to the one or more network functions. Un-reserving the one or more resources refers to the deallocation of network resources, such as computing power, memory, storage, and bandwidth, that are necessary to perform specific tasks related to the one or more network functions.

[0057] In an embodiment, when the one or more tasks relate to instantiation, the trigger unit 218, reserves the one or more resources for instantiation of the one or more network functions. For example, when a new network function like a UPF is instantiated, the trigger unit 218 allocates sufficient CPU, memory, storage, and network capacity for the function to be deployed and operate efficiently. Subsequently, once the instantiation of the one or more network functions is completed, the trigger unit 218 un-reserves the one or more resources. Alternatively, when the instantiation is not completed within a pre-defined time interval, the trigger unit 218, un-reserves the one or more resources allocated to the one or more network functions. The predefined time interval is a duration set in advance, used to establish a deadline or timeframe for the completion of the one or more tasks. In particular, the pre-defined time interval refers to the time limit within which the instantiation of network functions should be completed. In an embodiment, the trigger unit 218 changes the status of the one or more resources depending on a usage of the one or more resources in the network 106. The status of the one or more resources refers to the current state or condition of the one or more resources. The status of the one or more resources includes, but not limited to, reserved, available, fully utilized, partially utilized, idle, healthy, degraded, faulty, active, released, and pending. In particular, the trigger unit 218 can change the state of resources based on ongoing network demands or function performance. The trigger unit 218 adjusts the status of the resources as needed. For example, when a resource is initially reserved for instantiation, the status changes to "Reserved" and when the task is completed, the status is changed to "Active". If the resource is no longer needed, the status may be updated to "Available. Upon triggering the one or more tasks, the notifying unit 220 is configured to notify the IM 222 once the one or more tasks are completed.

[0058] Therefore, the system 108 helps in reducing the overhead of development, validation, integration, and testing efforts. The system 108 reduces redundant task creation and manages scheduling efficiently. The system 108 enhances the reliability and accuracy of task scheduling and execution. The system 108 ensures that the resources are allocated efficiently and only when needed, reducing wastage and improving overall network performance.

[0059] FIG. 3a is an exemplary representation of an interface in the network 106. FIG.3b is a block diagram of an architecture 300 of the system 108 to manage the one or more tasks in the network 106 utilizing an Inventory Manager (IM)_Platform Scheduler & Cron Job Micro Service (PSC) interface, according to one or more embodiments of the present invention.

[0060] As shown in FIG. 3a, a communication channel is established between the IM 222 and a Platform Scheduler & Cron Job (PSC) 302 Micro Service. The PSC 302 is capable of running tasks at a pre-defined time interval configured as per the user. The user is at least one of the network operator, system administrator. The PSC 302 has some inbuilt Cron schedulers of 1 minute, 15-minute, 1 day or 1 hour and also it can create customized Crons. The Cron is a time -based job scheduler, the Cron allows users to schedule jobs such as commands or scripts to run automatically at specified intervals. The communication channel is an interface. In an embodiment, the interface is at least one of, an Inventory Manager_Platform Scheduler & Cron Job Micro Service (IM_PSC) interface. The IM_PSC interface is a set of protocols and methods used to manage and coordinate scheduling tasks, such as Cron jobs, within the network 106. The IM_PSC interface ensures that tasks are scheduled, executed, and monitored efficiently according to predefined rules and configurations. [0061] As shown in the FIG. 3b, the architecture 300 includes the PSC 302, the IM 222 and the database 208.

[0062] In an embodiment, the PSC 302 receives the request from the IM 222 to schedule the one or more tasks in the network 106. The request is at least one of HTTP request. The request includes details of the one or more tasks which are required to be scheduled at the database 208. The one or more tasks include at least one of, instantiation, termination or deletion of the one or more network functions. Upon receiving the request from the IM 222, the PSC 302 checks whether the one or more tasks are pre-scheduled or not prescheduled. The PSC 302 checks whether the one or more tasks are pre-scheduled or not prescheduled by extracting the data related to the one or more tasks from the received request. Upon extracting the data, the PSC 302 checks whether the extracted data is present at the database 208. Upon checking if the extracted data is present at the database 208, the PSC 302 determines that the one or more tasks are pre-scheduled at the database 208. Alternatively, upon checking, if the extracted data is not present at the database 208, the PSC 302 determines that the one or more tasks are not pre-scheduled at the database 208.

[0063] Upon checking whether the one or more tasks are pre-scheduled or not prescheduled, the PSC 302 creates the one or more tasks at the database 208. In particular, the PSC 302 creates the one or more tasks at the database 208, when the one or more tasks are not pre-scheduled at the database 208. Upon creating the one or more tasks, the PSC 302 stores the created one or more tasks at the database 208.

[0064] Upon creating and storing the one or more tasks at the database 208, the PSC 302 transmits the response to the IM 222. The response is related to the one or more tasks scheduled at the database 208. The response is at least one of, the failure response and the success response. In particular, when the one or more tasks are pre-scheduled at the database 208, the failure response is transmitted to the IM 222. Alternatively, when the one or more tasks are created and scheduled at the database 208, the success response is transmitted to the IM 222. Thereafter, upon receiving the response from

Y1 the PSC 302, the IM 222 transmits the instructions to perform the one or more tasks to the PSC 302.

[0065] Upon receiving the instructions from the IM 222, the PSC 302 triggers the one or more tasks at the scheduled time. The PSC 302 triggers the one or more tasks at the scheduled time by identifying the type of the one or more tasks. The type of the one or more tasks is at least one of, instantiation, termination or deletion of the one or more network functions. Upon identifying the type of the one or more tasks, the PSC 302 reserves or un-reserves the one or more resources for the one or more tasks. In an embodiment, when the one or more tasks relate to instantiation, the PSC 302 reserves the one or more resources for instantiation of the one or more network functions. Subsequently, once the instantiation of the one or more network functions is completed, the PSC 302 un-reserves the one or more resources. Alternatively, when the instantiation is not completed within a pre-defined time interval, the PSC 302, unreserves the one or more resources allocated to the one or more network functions. In an embodiment, the PSC 302 changes the status of the one or more resources depending on a usage of the one or more resources in the network 106. Upon triggering the one or more tasks, the PSC 302 notifies or transmits the response to the IM 222 that the one or more tasks are completed.

[0066] FIG. 4 is a signal flow diagram to manage the one or more tasks in the network 106, according to one or more embodiments of the present invention.

[0067] At step 402, the IM 222 transmits the request to the PSC 302. The request is to schedule the one or more tasks in the network 106. The request is at least one of HTTP request. The request includes details of the one or more tasks which are required to be scheduled at the elastic search (ES) database 402. The one or more tasks include at least one of, instantiation, termination or deletion of the one or more network functions. [0068] At step 404, upon receiving the request from the IM 222, the PSC 302 checks whether the one or more tasks are pre-scheduled or not prescheduled at the elastic search (ES) database 402. The ES database 402 provides a scalable and efficient solution for indexing, searching, and analyzing large datasets in real-time. In particular ES 402, stores the results of the execution of the one or more tasks and data related to the one or more tasks. In an embodiment, the ES database 402 is at least one of the database 208. The PSC 302 checks whether the one or more tasks are pre-scheduled or not prescheduled by extracting the data related to the one or more tasks from the received request. Upon extracting the data, the PSC 302 checks whether the extracted data is present at the ES database 402. Upon checking if the extracted data is present at the ES database 402, the PSC 302 determines that the one or more tasks are prescheduled at the ES database 402. Alternatively, upon checking, if the extracted data is not present at the ES database 402, the PSC 302 determines that the one or more tasks are not pre-scheduled at the ES database 402.

[0069] At step 406, upon checking whether the one or more tasks are pre-scheduled or not pre-scheduled, the PSC 302 creates the one or more tasks at the ES database 402. In particular, the PSC creates the one or more tasks at the ES database 402, when the one or more tasks are not pre-scheduled at the ES 402. Upon creating the one or more tasks, the PSC 302 stores the created one or more tasks at the ES database 402.

[0070] At step 408, upon creating and storing the one or more tasks, the PSC 302 transmits the response related to the one or more tasks scheduled at the ES 402 to the IM 222. The response is at least one of, the failure response and the success response. In particular, when the one or more tasks are pre-scheduled at the ES database 402, the failure response is transmitted to the IM 222. Alternatively, when the one or more tasks are created and scheduled at the ES database 402, the success response is transmitted to the IM 222.

[0071] At step 410, upon receiving the response from the PSC 302, the IM 222 transmits the instruction to perform the one or more tasks to the PSC 302. [0072] At step 412, upon receiving the instructions from the IM 222, the PSC 302 triggers the one or more tasks at the scheduled time. The PSC 302 triggers the one or more tasks at the scheduled time by identifying the type of the one or more tasks. The type of the one or more tasks is at least one of, instantiation, termination or deletion of the one or more network functions. Upon identifying the type of the one or more tasks, the PSC 302 reserves or un-reserves the one or more resources for the one or more tasks. For instance, when the one or more tasks relate to instantiation, the PSC 302 reserves the one or more resources for instantiation of the one or more network functions. Subsequently, once the instantiation of the one or more network functions is completed, the PSC 302 un-reserves the one or more resources. Alternatively, when the instantiation is not completed within a pre-defined time interval, the PSC 302, unreserves the one or more resources allocated to the one or more network functions. In an embodiment, the PSC 302 changes the status of the one or more resources depending on a usage of the one or more resources in the network 106.

[0073] At step 414, upon triggering the one or more tasks, the PSC 302 notifies or transmits the response indicating that the one or more tasks are completed to the IM 222.

[0074] FIG. 5 is a flow diagram of a method 500 to manage the one or more tasks in the network 106, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.

[0075] At step 502, the method 500 includes the step of receiving the request from the IM 222 to schedule the one or more tasks in the network 106 by the transceiver 210. The request is at least one of the HTTP requests. The request includes details of the one or more tasks which are required to be scheduled at the storage unit 212. The one or more tasks include at least one of, instantiation, termination or deletion of the one or more network functions. [0076] At step 504, the method 500 includes the step of checking whether the one or more tasks are pre-scheduled or not pre-scheduled from the storage unit 212. The checking unit 214 is configured to check whether the one or more tasks are prescheduled or not pre-scheduled by extracting the data related to the one or more tasks from the received request. Upon extracting the data, the checking unit 214 is configured to check if the extracted data is present at the storage unit 212. Upon checking if the extracted data is present at the storage unit 212, the one or more tasks are determined to be pre-scheduled at the storage unit 212. Alternatively, upon checking if the extracted data is not present at the storage unit 212, the one or more tasks are determined to be not pre-scheduled at the storage unit 212.

[0077] At step 506, the method 500 includes the step of creating the one or more tasks by the creating unit 216 at the storage unit 212, when the one or more tasks are not pre-scheduled. Upon creation of the one or more tasks, the creating unit 216 stores the one or more tasks at the storage unit 212.

[0078] At step 508, the method 500 includes the step of transmitting the response related to the one or more tasks scheduled at the storage unit 212 to the IM 222 by the transceiver 210.

[0079] At step 510, the method 500 includes the step of receiving the instructions from the IM 222 to perform the one or more tasks by the transceiver 210 based on transmitting the response to the IM 222.

[0080] At step 512, the method 500 includes the step of triggering the one or more tasks at the scheduled time based on the instructions received from the IM 222 by the trigger unit 218. The trigger unit 218 triggers the one or more tasks by identifying the type of the one or more tasks. Based on the type of the tasks, the trigger unit 218 reserves or un-reserves the one or more resources for the one or more tasks. In an embodiment, when the one or more tasks are instantiated, the trigger unit 218 reserves the one or more resources for instantiation of the one or more network functions. Subsequently, once the instantiation of the one or more network functions is completed, the trigger unit 218 un-reserves the one or more resources. Alternatively, when the instantiation is not completed within a pre-defined time interval, the trigger unit 218, un-reserves the one or more resources allocated to the one or more network functions. In an embodiment, trigger unit 218 changes the status of the one or more resources depending on the usage of the one or more resources in the network 106.

[0081] At step 514, the method 500 includes the step of notifying the IM 222, once the one or more tasks are completed by the notifying unit 220.

[0082] FIG. 6 illustrates an architecture framework 600 (e.g., MANO architecture framework), in which the present invention can be implemented in accordance with one or more embodiments of the present invention. The system architecture 600 includes the user interface 206, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 602, a platform foundation service module 604, a platform core service module 606, and a platform resource adapter and utilities module 608.

[0083] The NFV and SDN design function module 602 is crucial for modernizing network infrastructure by enabling virtualized, scalable, and programmable network functions and management systems, particularly within the framework of CNFs. The platform foundation service module 604 refers to the underlying services and infrastructure components that support and enable the deployment, operation, and management of containerized network functions. The platform foundation service module 604 provides the essential capabilities and resources required for the CNF environment to function effectively.

[0084] The platform core service module 606 refers to the fundamental services and components that are essential for the core functionality and operation of containerized network functions. These services are critical for the effective deployment, execution, and management of CNFs, providing the necessary support and infrastructure for their operation. The platform resource adapter and utilities module 608 refers to a set of components and tools designed to manage and adapt various resources and services necessary for the operation of CNFs. The platform resource adapter and utilities module 608 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.

[0085] The NFV and SDN design function module 602 includes a Virtual Network Function (VNF) lifecycle manager 602a, a VNF catalog 602b, a network service catalog 602c, a network slicing and service chaining manager 602d, a physical and virtual resource manager 602e, and a CNF lifecycle manager 602f.

[0086] The VNF lifecycle manager 602a is responsible for managing the entire lifecycle of VNFs. The VNF lifecycle manager 602a ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 602b (referred to as a CNF catalog) is a repository or registry that stores information about various containerized network functions and their configurations. The VNF catalog 602b serves as a central reference for managing and deploying CNFs, providing details about their capabilities, requirements, and how they can be used within the network environment. The network service catalog 602c is a comprehensive repository that organizes and manages the information related to network services composed of multiple CNFs or other network functions. The network service catalog 602c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.

[0087] The network slicing and service chaining manager 602d is a crucial component responsible for orchestrating and managing network slicing and service chaining functionalities. The network slicing and service chaining functionalities are essential for efficiently utilizing network resources and delivering tailored network services in a dynamic and scalable manner. The physical and virtual resource manager 602e is a critical component responsible for overseeing and managing both physical and virtual resources required to support the deployment, operation, and scaling of CNFs. The physical and virtual resource manager 602e ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.

[0088] Further, the CNF lifecycle manager 602f is a component responsible for overseeing the entire lifecycle of containerized network functions. This includes the management of CNFs from their initial deployment through ongoing operation and maintenance, up to their eventual decommissioning. The CNF lifecycle manager 602f ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.

[0089] The platform foundation service module 604 includes a microservice elastic load balancer 604a, an identity and access manager 604b, a command line interface 604c, a central logging manager 604d and an event routing manager 604e.

[0090] The microservice elastic load balancer 604a is a specific type of load balancer designed to dynamically distribute network traffic across a set of microservices running in a containerized environment. The primary purpose of the microservice elastic load balancer 604a is to ensure efficient resource utilization, maintain high availability, and improve the performance of network services by evenly distributing incoming traffic among multiple instances of microservices. The identity and access manager 604b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 604b ensures that only authorized users and systems can access specific resources, and it enforces policies related to identity verification, authentication, authorization, and auditing within the CNF ecosystem.

[0091] The central logging manager 604d is a component responsible for aggregating, managing, and analyzing log data from various containerized network functions and associated infrastructure components. The central logging manager 604d ensures that logs are collected from disparate sources, consolidated into a single repository, and made accessible for monitoring, troubleshooting, and auditing purposes. The event routing manager 604e is a component responsible for handling the distribution and routing of events and notifications generated by various parts of the CNF environment. The event routing manager 604e includes events related to system status, performance metrics, errors, and other operational or application -level events. The event routing manager 604e ensures that these events are efficiently routed to the appropriate consumers, such as monitoring systems, alerting systems, or logging infrastructure, for further processing and action.

[0092] The platform core service module 606 includes an NFV infrastructure monitoring manager 606a, an assurance manager 606b, a performance manager 606c, a policy execution engine 606d, a capacity monitoring manager 606e, a release management repository 606f, a configuration manager and GCT 606g, a NFV platform decision analytics unit 606h, a platform NoSQL DB 606i, a platform scheduler and Cron Jobs module 606j, a VNF backup & upgrade manager 606k, a micro service auditor 6061, and a platform operation, administration and maintenance manager 606m.

[0093] The NFV infrastructure monitoring manager 606a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 606a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 606a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager 606a integrates with monitoring tools to ensure reliable operation of CNFs.

[0094] The assurance manager 606b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manager 606c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 606d enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 606d executes policies related to security, resource allocation, and service quality. Further, the policy execution engine 606d executes policies, translates policy rules into actionable configurations and enforces compliance across CNFs.

[0095] The capacity monitoring manager 606e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository 606f stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository 606f keeps track of different versions of CNFs.

[0096] The configuration manager and Generic Configuration Tool (GCT) 606g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 606h analyzes data from a NFV platform to support decision-making and strategic planning.

[0097] The platform NoSQL database (DB) 606i is used for storing and managing large volumes of unstructured or semi-structured data within the CNF environment. The platform scheduler and Cron Jobs module 606j manage scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manager 606k oversees the backup and upgrade processes for VNFs within the CNF environment.

[0098] The micro service auditor 6061 monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 606m manages the overall operation, administration, and maintenance of the CNF platform.

[0099] The platform resource adapter and utilities module 608 includes a platform external API adaptor and gateway 608a, a generic decoder and indexer 608b, a swarm adaptor 608c, an API adaptor 608d and a NFV gateway 608e.

[00100] The platform external API adaptor and gateway 608a facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer 608b decode and indexes various types of data and logs within the CNF environment. The swarm adaptor 608c facilitates communication between a swarm cluster and the CNF environment, including container deployment, scaling, and management.

[00101] The API adaptor 608d provides an interface for the CNF platform to interact with APIs, enabling operations such as provisioning, scaling, and managing virtual resources. The NFV gateway 608e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.

[00102] In an embodiment the interface IM_PS is between the physical and virtual resource manager 602e and the Platform scheduler and Cron Jobs module 606j.

[00103] 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 IM 222 to schedule one or more tasks in the network 106. The processor 202 is further configured to check, from the storage unit 212, whether the one or more tasks are pre-scheduled or not pre-scheduled. The processor 202 is further configured to create the one or more tasks at the storage unit 212, when the one or more tasks are not pre-scheduled. The processor 202 is further configured to transmit, to the IM 222, the response related to the one or more tasks scheduled at the storage unit 212. The processor 202 is further configured to receive instructions from the IM 222 to perform the one or more tasks based on transmitting the response to the IM 222. The processor 202 is further configured to trigger one or more tasks at the scheduled time based on the instructions received from the IM 222. The processor 202 is further configured to notify, the IM 222, once the one or more tasks are completed.

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

[00105] The present disclosure incorporates the technical advancement of reducing the time required to schedule tasks in a network by automating the scheduling process at the IM level. By providing a mechanism to automatically un-reserve resources in case of VNF (Virtualized Network Function) or CNF (Cloud Native Network Function) instantiation failures, the present invention enhances the resource optimization. The present invention enriches performance data for CNFs and VNFs by leveraging scheduling capabilities, allowing the IM service to manage and track resources more effectively. The present invention enhances the efficiency of communication between microservices. The interface of the present invention allows for scheduled start and stop events related to performance data enrichment. Thus, the present invention ensures that the network performance data is gathered and processed efficiently without impacting real-time network functions. The present invention reduces the complexity and maintenance effort, by freeing up development resources and improving scalability for handling multiple network functions.

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

[00107] Environment- 100

[00108] User Equipment (UE)- 102

[00109] Server- 104

[00110] Network- 106

[00111] System -108

[00112] Processor- 202

[00113] Memory- 204

[00114] User Interface- 206

[00115] Database- 208

[00116] Transceiver - 210

[00117] Storage Unit- 212

[00118] Checking unit- 214

[00119] Creating Unit- 216

[00120] Trigger Unit- 218

[00121] Notifying Unit- 220

[00122] Inventory manager (IM)- 222

[00123] PSC- 302

[00124] Elastic Search (ES)- 402

[00125] NFV and SDN design function module -602

[00126] Virtual Network Function (VNF) lifecycle manager -602a,

[00127] VNF catalog -602b,

[00128] Network service catalog -602c,

[00129] Network slicing and service chaining manager -602d,

[00130] Physical and virtual resource manager -602e,

[00131] CNF lifecycle manager -602f

[00132] Platform foundation service module -604

[00133] Microservice elastic load balancer -604a

[00134] Identity and access manager -604b [00135] Command line interface -604c

[00136] Central logging manager -604d

[00137] Event routing manager -604e

[00138] Platform core service module -606

[00139] NFV infrastructure monitoring manager -606a,

[00140] Assurance manager -606b,

[00141] Performance manager -606c,

[00142] Policy execution engine -606d,

[00143] Capacity monitoring manager -606e

[00144] Release management repository -606f

[00145] Configuration manager and GCT -606g

[00146] NFV platform decision analytics unit -606h

[00147] Platform NoSQE DB -606i

[00148] Platform scheduler and Cron Jobs module -606j

[00149] VNF backup & upgrade manager -606k

[00150] Micro service auditor -6061

[00151] Platform operation, administration and maintenance manager -606m

[00152] Platform resource adapter and utilities module 608

[00153] Platform external API adaptor and gateway -608a

[00154] Generic decoder and indexer -608b

[00155] Swarm adaptor -608c

[00156] API adaptor -608d

[00157] NFV gateway -608e

Claims

CLAIMS: We Claim:

1. A method (500) to manage one or more tasks in a network (106), the method (500) comprising the steps of: receiving, by one or more processors (202), a request from an Inventory Manger (IM) (222) to schedule one or more tasks in the network (106); checking, by the one or more processors (202), from a storage unit (212), whether the one or more tasks are pre-scheduled or not pre-scheduled; creating, by the one or more processors (202), the one or more tasks at the storage unit, when the one or more tasks are not pre-scheduled; transmitting, by the one or more processors (202), to the IM (222), a response related to the one or more tasks scheduled at the storage unit (212); receiving, by the one or more processors (202), instructions from the IM (222) to perform the one or more tasks based on transmitting the response to the IM (222); triggering, by the one or more processors (202), the one or more tasks at a scheduled time based on the instructions received from the IM (222); and notifying, by the one or more processors (202), the IM (222), once the one or more tasks are completed.

2. The method (500) as claimed in claim 1, wherein the request is a Hypertext Transfer Protocol (HTTP) request, the request includes details of the one or more tasks which are required to be scheduled at the storage unit (212).

3. The method (500) as claimed in claim 1, wherein the step of, creating the one or more tasks at the storage unit (212), when the one or more tasks are not prescheduled, further includes the step of: storing, by the one or more processors (202), the one or more tasks at the storage unit (212).

4. The method (500) as claimed in claim 1, wherein the step of, transmitting, a response of the one or more tasks scheduled at the storage unit (212), includes the step of: transmitting, by the one or more processors (202), a failure response when the one or more tasks are pre-scheduled at the storage unit (212).

5. The method (500) as claimed in claim 1, wherein the step of, transmitting, a response of the one or more tasks scheduled at the storage unit (212), includes the step of: transmitting, by the one or more processors (202), a success response when the one or more tasks are created and scheduled.

6. The method (500) as claimed in claim 1, wherein the step of, checking, from a storage unit (212), whether the one or more tasks are pre-scheduled or not pre- scheduled, includes the steps of: extracting, by the one or more processors (202), data related to the one or more tasks from the received request; checking, by the one or more processors (202), if the extracted data is present at the storage unit (212); if determined that the extracted data is present at the storage unit, inferring by the one or more processors (202), that the one or more tasks are prescheduled at the storage unit (212); and if determined that the extracted data is not present at the storage unit (212), inferring, by the one or more processors (202), that the one or more tasks are not pre-scheduled at the storage unit (212).

7. The method (500) as claimed in claim 1, wherein the one or more tasks include at least one of, instantiation, termination or deletion of one or more network functions.

8. The method (500) as claimed in claim 1, wherein the step of, triggering, the one or more tasks at a scheduled time based on the instructions received from the IM (222), includes the steps of: identifying, by the one or more processors (202), a type of the one or more tasks; reserving or un-reserving, by the one or more processors (202), one or more resources for the one or more tasks based on the type of the tasks.

9. The method (500) as claimed in claim 6, wherein when the one or more tasks is instantiation, the one or more processors (202), reserves one or more resources for instantiation of the one or more network functions.

10. The method (500) as claimed in claim 8, wherein the one or more processors (202), un-reserves the one or more resources once the instantiation of the one or more network functions is completed.

11. The method (500) as claimed in claim 7, wherein when the instantiation is not completed within a pre-defined time interval, the one or more processors (202), un-reserves the one or more resources allocated to the one or more network functions.

12. The method (500) as claimed in claim 1, wherein the method (500) further comprising: changing, by the one or more processors (202), a status of the one or more resources depending on a usage of the one or more resources in the network.

13. A system (108) to manage one or more tasks in a network (106), the system (108) comprising: a transceiver (210), configured to, receive, a request from an Inventory Manger (IM) (222) to schedule one or more tasks in the network (106); a checking unit (214), configured to, check, from a storage unit (212), whether the one or more tasks are pre-scheduled or not pre-scheduled; a creating unit (216), configured to, create, the one or more tasks at the storage unit, when the one or more tasks are not pre-scheduled; the transceiver (210), configured to: transmit, to the IM (222), a response related to the one or more tasks scheduled at the storage unit (212); and receive, instructions from the IM (222) to perform the one or more tasks based on transmitting the response to the IM (222); a trigger unit (218), configured to, trigger, the one or more tasks at a scheduled time based on the instructions received from the IM (222); and a notifying unit (220), configured to, notify, the IM (222), once the one or more tasks are completed.

14. The system (108) as claimed in claim 13, wherein the request is a Hypertext Transfer Protocol (HTTP) request, the request includes details of the one or more tasks which are required to be scheduled at the storage unit (212).

15. The system (108) as claimed in claim 13, wherein the creating unit (216), stores, the one or more tasks at the storage unit (212) once the one or more tasks are created.

16. The system (108) as claimed in claim 13, wherein the response is at least one of a failure response when the one or more tasks are pre-scheduled at the storage unit (212).

17. The system (108) as claimed in claim 13, wherein the response is at least one of a success response when the one or more tasks are created and scheduled.

18. The system (108) as claimed in claim 13, wherein the checking unit (214), configured to check from a storage unit (212), whether the one or more tasks are pre-scheduled or not pre-scheduled, by: extracting, data related to the one or more tasks from the received request; checking, if the extracted data is present at the storage unit (212); if determined that the extracted data is present at the storage unit (212), the checking unit (214), infers that the one or more tasks are pre-scheduled at the storage unit (212); and if determined that the extracted data is not present at the storage unit (212), the checking unit (214), infers that the one or more tasks are not prescheduled at the storage unit (212).

19. The system (108) as claimed in claim 13, wherein the one or more tasks include at least one of, instantiation, termination or deletion of one or more network functions.

20. The system (108) as claimed in claim 13, wherein the trigger unit (218), triggers the one or more tasks at the scheduled time based on the instructions received from the IM (222), by: identifying, a type of the one or more tasks; and reserving or un-reserving, one or more resources for the one or more tasks based on the type of the tasks.

21. The system (108) as claimed in claim 18, wherein when the one or more tasks is instantiation, the trigger unit (218), reserves the one or more resources for instantiation of the one or more network functions.

22. The system (108) as claimed in claim 18, wherein the trigger unit (218), unreserves the one or more resources once the instantiation of the one or more network functions is completed.

23. The system (108) as claimed in claim 18, wherein when the instantiation is not completed within a pre-defined time interval, the trigger unit (218), un-reserves the one or more resources allocated to the one or more network functions.

24. The system (108) as claimed in claim 13, wherein the trigger unit (218) further: changes, a status of the one or more resources depending on a usage of the one or more resources in the network (106).

25. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (202), causes the processor (202) to: receive, a request from an Inventory Manger (IM) (222) to schedule one or more tasks in the network (106); check, from a storage unit (212), whether the one or more tasks are prescheduled or not pre-scheduled; create, the one or more tasks at the storage unit (212), when the one or more tasks are not pre-scheduled; transmit, to the IM (222), a response related to the one or more tasks scheduled at the storage unit (212); receive, instructions from the IM (222) to perform the one or more tasks based on transmitting the response to the IM (222); trigger, the one or more tasks at a scheduled time based on the instructions received from the IM (222); and notify, the IM (222), once the one or more tasks are completed.