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

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR AUTOMATICALLY SCHEDULING OF A TASK
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

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

FIELD OF THE INVENTION
[0001] The present invention relates to scheduling systems, more particularly relates to a method and a system of automatically scheduling of a task.
BACKGROUND OF THE INVENTION
[0002] In modern digital landscape, organizations rely heavily on computer systems to perform a multitude of tasks, ranging from file management to data analysis to communication to automated backup. While there are existing software tools that offer task scheduling capabilities, they often focus on specific task types or lack the versatility to handle a wide variety of computer-associated tasks.
[0003] While server-based technologies have been used in various applications, the integration of a centralized scheduling platform within the management and orchestration (MANO) with a server-based infrastructure to manage diverse tasks has not been fully explored. The related art may include server- based solutions for specific domains, but a unified platform within the MANO catering to a wide range of task types and industries remains an unaddressed need. The MANO is a key architectural framework within the Network Functions Virtualization (NFV) ecosystem, responsible for managing and orchestrating virtualized network functions (VNFs) and the underlying infrastructure. The MANO includes multiple microservices such as platform foundation services, platform core services and platform resource adapters and utilities. The coordinating multiple microservices to work seamlessly within the MANO framework requires robust orchestration mechanisms, particularly when dealing with tasks that span across various network functions and physical locations.
[0004] Traditional scheduling systems might not fully leverage the potential of automation, customization, and cross-task coordination that is demanded in today's fast-paced computing environment.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and system for automatically scheduling of a task.
[0006] In one aspect of the present invention, the system for automatically scheduling of the task is disclosed. The system includes a receiving unit configured to receive a request from a user to create or modify and schedule a task. The system further includes a checking unit configured to check whether the task is pre-scheduled at a centralized platform. The system further includes a scheduler unit configured to create the scheduled task when the task is not pre-scheduled at the centralized platform.
[0007] In an embodiment, the request includes one or more user preferences to schedule the task. The one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task.
[0008] In an embodiment, upon checking whether the task is pre-scheduled at the centralized platform, a notifying unit is configured to notify the user by a failure message.
[0009] In an embodiment, upon checking whether the task is not pre-scheduled at the centralized platform, the notifying unit is configured to notify the user by a success message.
[0010] In an embodiment, to create the scheduled task, when the task is not pre-scheduled at the centralized platform the system includes triggering unit configured to trigger the scheduled task at a scheduled time at the centralized platform. The system further includes a notifying unit configured to notify, an initiation of the task to the user. The notification includes providing information to the user pertaining to a timeline for completion of the task as per a user-defined timeline.
[0011] In an embodiment, the user allows to set the user-defined timeline via a user interface module of a User Equipment (UE) in real time.
[0012] In an embodiment, the user allows to pre-set frequency of notifications that the user can receive in run time pertaining to scheduling the task.
[0013] In an embodiment, the task pertains to at least one of, a backup of a running Virtual network functions (VNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure.
[0014] In an embodiment, upon creating the scheduled task, the created scheduled task is stored at the centralized platform.
[0015] In an embodiment, the centralized platform is in communication with a Backup and Restore (BR) instance. The BR instance is enabled to create, update and delete the one or more tasks at the centralized platform as per instructions from the user.
[0016] In an embodiment, the centralized platform is connected to a plurality of instances. In the event a current instance fails, then in real time, the current instance is replaced with a new instance in order to schedule and process the task at the centralized platform without any delay.
[0017] In another aspect of the present invention, the method for automatically scheduling of the task is disclosed. The method includes the step of receiving a request from a user to create or modify and schedule a task. The method further includes the step of checking whether the task is pre-scheduled at a centralized platform. The method further includes the step of creating the scheduled task when the task is not pre-scheduled at the centralized platform.
[0018] 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 user to create or modify and schedule a task. The processor is configured to check whether the task is pre-scheduled at a centralized platform. The processor is configured to create the scheduled task when the task is not pre-scheduled at the centralized platform.
[0019] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to transmit a request to schedule ta task to the one or more processors in order to avail one or more services.
[0020] 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
[0021] 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.
[0022] FIG. 1 is an exemplary block diagram of an environment for automatically scheduling of a task, according to one or more embodiments of the present invention;
[0023] FIG. 2 is an exemplary block diagram of a system for automatically scheduling of the task, according to one or more embodiments of the present invention;
[0024] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0025] FIG. 4 is an exemplary block diagram of a centralized platform architecture, according to one or more embodiments of the present invention;
[0026] FIG. 5 is a signal flow diagram for automatically scheduling of the task, according to one or more embodiments of the present invention; and
[0027] FIG. 6 is a schematic representation of a method of automatically scheduling of the task, according to one or more embodiments of the present invention.
[0028] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0029] 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.
[0030] 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.
[0031] 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.
[0032] The present invention discloses a method and a system for automatically scheduling a task. To schedule the task, whether the task is prescheduled or not is checked at the centralized platform present at the Management and Orchestration (MANO). The centralized platform disclosed enables Backup and Restore Resources (BR) instance present at the MANO to create, update and delete a variety of tasks. The centralized platform enables centralized scheduling rather than doing operations at respective systems. The centralized platform as disclosed in an aspect may be configured to create different types of tasks i.e., Application Programming Interface (API), File Transfer Protocol (FTP), Event or Query. The system and method as disclosed enables the centralized platform to send notification of the task periodically as defined by the user or the platform. The frequency of the notification may be modified real-time, or run-time. Further the centralized platform has high availability. Thereby enabling another instance to take over if the current instance goes down or fails during processing of the request.
[0033] FIG. 1 illustrates an exemplary block diagram of an environment 100 for automatically scheduling of a task, 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 automatically scheduling of the task. The task refers to a specific operation or set of operations that need to be performed automatically at a scheduled time. The task includes, but is not limited to, backup operations, restoration operations, Application programming Interface (API) or File Transfer Protocol (FTP) operations, event or query based actions. The scheduled time is a time period determined in advance when the task is intended to be executed.
[0034] 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”.
[0035] 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.
[0036] 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.
[0037] 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.
[0038] 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.
[0039] 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 automatically schedule the task. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0040] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0041] FIG. 2 is an exemplary block diagram of the system 108 for automatically scheduling of the task, according to one or more embodiments of the present invention.
[0042] 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 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.
[0043] 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.
[0044] 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.
[0045] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 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.
[0046] In order for the system 108 to automatically schedule the task, 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, a checking unit 212, a notifying unit 214, a scheduler unit 216, and a triggering unit 222 communicably coupled to each other for automatically scheduling of the task. Further, the system 108 is communicably coupled to a centralized platform 218. The centralized platform 218 is connected to a Backup and Restore (BR) instance 220.
[0047] In one embodiment, the one or more modules includes, but not limited to, the receiving unit 210, the checking unit 212, the notifying unit 214, the scheduler unit 216, and the triggering unit 222 can be used in combination or interchangeably for automatically scheduling of the task.
[0048] The receiving unit 210, the checking unit 212, the notifying unit 214, the scheduler unit 216, and the triggering unit 222 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.
[0049] In one embodiment, the receiving unit 210 is configured to receive a request from a user via the UE 102. The user refers to an individual or entity that interacts with the system 108 to request the creation and scheduling of tasks. The user is at least one of network administrator or operator or end user. The request is received from the user to create or modify and schedule the task. The request refers to an input or command sent by the user to initiate the creation and scheduling of the task. The request includes one or more user preferences to schedule the task. The one or more user preferences refer to specific choices or configurations that the user can specify to tailor how the task should be created and scheduled. The one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task.
[0050] In an embodiment, the API is a set of protocols and tools that allows different software applications to communicate with each other. The type of API includes, but is not limited to, Representational State Transfer (REST) API, Simple Object Access Protocol (SOAP) API, graphQL API, WebSocket API. The REST API is based on standard HTTP methods (GET, POST, PUT, DELETE) and is designed to be simple, stateless, and scalable. The SOAP API is a protocol that uses Extensible Markup Language (XML) for messaging and provides more extensive security and transactional features. The graphQL is a query language for APIs that allows the user to request only the required data. The WebSocket API is a protocol that provides full-duplex communication channels over a single, long-lived connection. In an embodiment API is a kind of task in which any API needs to be invoke at a particular interval of time.
[0051] In an embodiment, the FTP is a standard network protocol used to transfer files between a client and the server 104 over the network 106. The client refers to a software application or the UE 102 that initiates a connection to the server 104 to perform file transfer operations. The FTP includes, but is not limited to, a standard FTP and a Secure FTP (SFTP). The standard FTP is a basic form of the FTP, used for transferring files between the client and the server 104. The SFTP is a secure version of FTP that uses Secure Shell (SSH) to encrypt the data transfer. In an embodiment, the FTP is a task in which a scheduler works for specific period of time and transfers data/file from source to destination location.
[0052] In an embodiment, the event or query refers to a condition or trigger that initiates or defines the scheduling of the task. The event includes, but is not limited to, a system alert, a change in network status, or the completion of another task. The query includes checking certain data conditions, such as the availability of resources or the status of a particular component. For instance, the user might choose to schedule the task based on a specific network event, such as a Virtual Network Function (VNF) failure, or based on a query result, such as whether a backup file exists. In an embodiment, the event is a task in which any event needs to be invoked on pre decided interval and the query is a type of task in which any query needs to be executed periodically.
[0053] In an embodiment, the task pertains to at least one of, a backup of a running Virtual network functions (VNF) instance and a Container Network Function (CNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure. The VNF is a software implementation of a network function that runs on virtualized infrastructure, such as a virtual machine or container, instead of dedicated hardware. Examples of VNFs include firewalls, load balancers, routers 5th Generation (5G) core nodes such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF). The backup of the running VNF instance includes creating a copy of the current state of a running VNF instance, including its configuration, data, and operational status. The backup ensures that all the essential information is saved and can be restored later if needed. The Virtual Network Function Component (VNFC) is a smaller, modular part of the VNF. The VNFCs work together to perform the overall function of the VNF. The VNFC is a software module or a microservice that handles a specific function within the VNF. The restoration task includes bringing a failed VNF or VNFC back to its operational state after a failure. The restoration task is crucial for maintaining the availability and reliability of network services. In an embodiment, task refers to a specific operation or set of operations that the system 108 is responsible for scheduling, managing, and executing. The task includes, but not limited to, backup operation, restoration operations, scheduling and triggering, execution monitoring, management operations.
[0054] Upon receiving the request from the user, the checking unit 212 is configured to check whether the task is pre-scheduled at the centralized platform 218. The pre-scheduling involves checking if the task, as requested by the user, has been previously defined and is already queued or configured to be executed at a specified time or under certain conditions. The centralized platform 218 refers to a unified system or infrastructure that manages, coordinates, and stores tasks related to network operations, such as scheduling, executing, and monitoring tasks like backups and restorations of VNFs. The centralized platform 218 acts as a control center for managing the tasks across the network 106.
[0055] Upon checking whether the task is pre-scheduled at the centralized platform 218, the notifying unit 214 is configured to notify the user by a failure message. The user is notified by the failure message, when the task is pre-scheduled at the centralized platform 218. Alternatively, upon checking whether the task is pre-scheduled at the centralized platform 218, the notifying unit 214 is configured to notify the user by a success message, when the task is not pre-scheduled at the centralized platform 218.
[0056] The scheduler unit 216 is configured to create the scheduled task if the task is not pre-scheduled at the centralized platform 218. The scheduled task is created by triggering the scheduled task at the scheduled time at the centralized platform 218. More specifically, the triggering unit 222 is configured to trigger the scheduled task at the scheduled time at the centralized platform 218. The term triggering refers to the process of starting the task at the scheduled time. The scheduled task refers to the task that has been planned and set to be executed at a scheduled time. The scheduled time is a time period determined in advance when the task is intended to be executed. The scheduled time can be at least one of, fixed time (for example, task is set to run at a specific date and time i.e., 3:00 PM on August 15, 2024) and a recurring interval (for example, task is set to repeat at regular intervals i.e., task is set to run every day at 2:00 AM).
[0057] Upon triggering the scheduled task, the notifying unit 214 is configured to notify the user, via a notification, regarding the initiation of the task. The notification includes providing information to the user pertaining to a timeline for completion of the task as per a user-defined timeline. The timeline for completion of the task is the estimated or expected time by which the task will be completed. The user-defined timeline is the timeline set by the user when the task is scheduled. In an embodiment, the user allows to set the user-defined timeline via the UE 102 in real time. Further, the user is also allowed to pre-set frequency of notifications that the user can receive in run time pertaining to scheduling the task. The pre-set frequency is the interval or frequency at which notifications are sent to the user about the task. More specifically, the user is allowed to set the interval for receiving the notification regarding the status of the progress of the scheduled task. For example, the user might choose to receive notifications every 30 minutes or every hour.
[0058] Upon creating the scheduled task, the created scheduled task is stored at the centralized platform 218. In an embodiment, the centralized platform 218 is in communication with the Backup and Restore (BR) instance 220. The BR instance 220 is enabled to create, update and delete the one or more tasks at the centralized platform 218 based on the request received from the user. The BR instance 220 is a specialized, independent software component that manages the creation, updating, and deletion of backup and restore tasks within the centralized platform 218. In an embodiment, the BR instance 220 is deployed as a containerized microservice.
[0059] In an embodiment, the centralized platform 218 is connected to a plurality of instances. The instance refers to a specific, operational copy or deployment of the centralized platform 218. The plurality of instances refers to multiple operational instances of the centralized platform 218 that are set up to handle the scheduling and processing of tasks. In the event a current instance fails, then the current instance is replaced with a new instance in real time. The current instance is replaced with the new instance in order to schedule and process the task at the centralized platform 218 without any delay.
[0060] By scheduling the tasks automatically, the system 108 helps in solving the problem of scheduling jobs. Further, the system 108 enhance the efficiency, reliability, and flexibility of task scheduling and management in the network 106. The system 108 automates the task scheduling and prevents duplication of scheduling the task by checking whether the task is already scheduled or not. Further, the system 108 also provides real-time notifications to users regarding the status of scheduled tasks, including both success and failure notifications. By automating the task scheduling and execution process, the system 108 optimizes the use of network resources, ensuring that tasks are performed at the most appropriate times and with minimal impact on overall network performance.
[0061] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 102a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0062] As mentioned earlier in FIG. 1, each of the first UE 102a, the second UE 102b, and the third UE 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0063] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 102a to transmit the request to schedule the task to the one or more processors 202 in order to avail one or more services.
[0064] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured to automate the scheduling of the task. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. Further, the system 108 is communicably coupled to a centralized platform 218. The centralized platform 218 is connected to a Backup and Restore (BR) instances 220. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0065] Further, the processor 202 includes the receiving unit 210, the checking unit 212, the notifying unit 214, the scheduler unit 216 and the triggering unit 222. The operations and functions of the receiving unit 210, the checking unit 212, the notifying unit 214, the scheduler unit 216 and the triggering unit 222 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0066] FIG. 4 is an exemplary block diagram of an architecture 400 of the centralized platform 218, according to one or more embodiments of the present invention.
[0067] The architecture 400 includes a Graphical User Interface (GUI) 402, a Command Line Interface (CLI) 404, an Event Routing Manager (ERM) 406, an Edge Load Balancer (LB) 408, an Elastic Load Balancer (ELB) 410, a Cron and schedulers management 412, Elastic Search (ES)- Database (DB) client 414, an Elastic Search (ES) 416, a VNF manager 418, a plurality of virtual machines (VM) 420. The Cron and schedulers management 412 includes Cron management, task management, Fault, Configuration, Accounting, Performance, and Security (FCAP’s) management, event handling, High Availability (HA) and fault tolerance, data modeling framework.
[0068] In an embodiment, the request is received from the GUI 402 and the CLI 404 for scheduling the tasks at the cron & scheduler management 412. The request includes one or more user preferences to schedule the task. The one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task. The task pertains to at least one of, the backup of the running Virtual network functions (VNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure.
[0069] Upon receiving the request from the ELB 410, the Cron and schedulers management 412 checks and verifies if the task has already been scheduled or not with the help of the ES-DB 414. If the task is not scheduled, the Cron and schedulers management 412creates scheduled task and stores the scheduled task in the ES 416 via the ES-DB client 414. The ES-DB client 414 refers to a client interface that interacts with the ES 416 in storing the task. The ES 416 acts as the database 208.
[0070] In an embodiment, upon checking whether the task is scheduled or not, the ERM 406 notifies the user via the GUI 402 by the success and failure message. The success message is transmitted to the user when the task is scheduled. The failure message is transmitted to the user when the task is not scheduled. Upon creating the scheduled task, the Cron and schedulers management 412 triggers the scheduled task at the scheduled time.
[0071] In an embodiment, the ERM interacts with the edge load balancer 408 and the elastic load balancer (ELB) 410 in transmitting the requests. The edge load balancer 408 distributes the incoming request received from the GUI 402 and the CLI 404. The elastic load balancer (ELB) 410 distributed the load among the plurality of virtual machines 420.
[0072] In an embodiment, the Cron and schedulers management 412 manages and schedules the task with the help of the Cron management, task management, FCAP’s management, event handling, HA and Fault tolerance, data modeling framework. The Cron management handles the scheduling of tasks. The Cron management execute tasks at scheduled times according to predefined Cron jobs. The Cron jobs refer to automated tasks or scripts that are scheduled to run at specific times or intervals using the Cron service. The task management is responsible for managing tasks which involve creating, scheduling, monitoring, and deleting tasks. The event handling manages event-driven tasks, responding to specific triggers or conditions of the tasks. The HA and fault tolerance ensures that task scheduling and execution are resilient to failures. The FCAP’s management maintains operational standards and ensures that the tasks are managed properly. The data modeling framework ensures that the tasks are categorized, prioritized and managed properly.
[0073] In an embodiment, the VNF manager 418 manages the plurality of virtual machine 420 in executing the tasks. If at least one of the plurality of virtual machines 420 fails, the VNF manager 418 replaces the failed VM with the new VM from the plurality of virtual machines 420 to schedule and process the task.
[0074] FIG. 5 is a signal flow diagram for automatically scheduling of the task, according to one or more embodiments of the present invention.
[0075] At step 502, the request from the user via the UE 102 for creating or modifying and scheduling the task is transmitted to the centralized platform 218 from the BR instance 220. In an embodiment, the request is at least one of HTTP request.
[0076] At step 504, upon receiving the request the centralized platform 218 checks whether the task is prescheduled or not.
[0077] At step 506, upon checking, if the task is pre-scheduled at the centralized platform 218, the failure message is transmitted to the BR instance 220. Alternatively, upon checking if the task is not pre-scheduled at the centralized platform 218, the success message is transmitted to the BR instance 220.
[0078] At step 508, upon checking if the task is not pre-scheduled, the centralized platform 218 creates the scheduled task and stores it in the elastic search 416.
[0079] At step 510, upon creating the scheduled task, the scheduled task is triggered by the centralized platform 218 at the scheduled time.
[0080] At step 512, subsequently, the centralized platform 218 notifies the initiation of the task to the BR instance 220. The notification includes providing information to the user pertaining to the timeline for completion of the task as per the user-defined timeline.
[0081] FIG. 6 is a flow diagram of a method 600 for automatically scheduling of the task, 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.
[0082] At step 602, the method 600 includes the step of receiving the request from the user to create or modify and schedule the task by the receiving unit 210. The request includes one or more user preferences to schedule the task. The one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task. The task pertains to at least one of, a backup of a running Virtual network functions (VNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure.
[0083] At step 604, the method 600 includes the step of checking whether the task is pre-scheduled at the centralized platform 218 by the checking unit 212. Upon checking if the task is not pre-scheduled at the centralized platform 218, the notifying unit 214 notifies the user by the failure message. Alternatively, upon checking if the task is per-scheduled at the centralized platform 218, the notifying unit 214 notifies the user by the success message.
[0084] At step 606, the method 600 includes the step of creating the scheduled task when the task is not pre-scheduled at the centralized platform 218 by the scheduler unit 216. In an embodiment, the triggering unit 222 is configured to trigger the scheduled task at the scheduled time at the centralized platform 218. Thereafter, the notifying unit 214 is configured to notify the initiation of the task to the user. The notification includes providing information to the user pertaining to the timeline for completion of the task as per the user-defined timeline. In an embodiment, the user is allowed to set the user-defined timeline via the UE 102 in real time. Further, the user is also allowed to pre-set frequency of notifications that the user can receive in run time pertaining to scheduling the task. Upon creating the scheduled task, the created scheduled task is stored at the centralized platform 218.
[0085] In an embodiment, the centralized platform 218 is in communication with the BR instance 220. The BR instance 220 is configured to create, update and delete the one or more tasks at the centralized platform 218 as per the instructions from the user. In an embodiment, the centralized platform 218 is connected to the plurality of instances. In the event, if the current instance fails, then the current instance is replaced with the new instance in order to schedule and process the task at the centralized platform 218 without any delay.
[0086] 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 user to create and schedule the task. The processor 202 is further configured to check whether the task is pre-scheduled at the centralized platform 218. The processor 202 is further configured to create the scheduled task when the task is not pre-scheduled at the centralized platform 218.
[0087] 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.
[0088] The present disclosure incorporates technical advancement in solving the problem of scheduling jobs. Further, the present invention enhances the efficiency, reliability, and flexibility of task scheduling and management in the network. The present invention automates the task scheduling and prevents duplication of scheduling the task by checking whether the task is already scheduled or not. Further, the present invention also provides real-time notifications to users regarding the status of scheduled tasks, including both success and failure notifications. By automating the task scheduling and execution process, the present invention optimizes the use of network resources, ensuring that tasks are performed at the most appropriate times and with minimal impact on overall network performance. Furthermore,, the present invention enhances the automation and reliability of task scheduling within MANO by reducing the risk of human error, ensuring timely execution of critical tasks, and maintaining high availability and fault tolerance across the network.
[0089] 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

[0090] Environment- 100
[0091] User Equipment (UE)- 102
[0092] Server- 104
[0093] Network- 106
[0094] System -108
[0095] Processor- 202
[0096] Memory- 204
[0097] User Interface- 206
[0098] Database- 208
[0099] Receiving Unit- 210
[00100] Checking Unit- 212
[00101] Notifying unit- 214
[00102] scheduler Unit- 216
[00103] Centralized Platform- 218
[00104] BR instance- 220
[00105] One or more Primary Processors- 302
[00106] Memory- 304
[00107] Graphical User Interface (GUI)- 402
[00108] Command Line Interface (CLI)- 404
[00109] Event Routing Manager (ERM)-406
[00110] Edge Load Balancer (LB) -408
[00111] Elastic Load Balancer (ELB) -410
[00112] Cron and schedulers management -412
[00113] Elastic Search (ES)- Database (DB) client -414
[00114] Elastic Search (ES)-416
[00115] VNF manager-418
[00116] Plurality of virtual machines (VM)-420
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for automatically scheduling of a task, the method (600) comprises the steps of:
receiving, by one or more processors (202), a request from a user via User Equipment (UE) (102) to create or modify and schedule a task;
checking, by the one or more processors (202), whether the task is pre-scheduled at a centralized platform (218); and
creating, by the one or more processors (202), the scheduled task when the task is not pre-scheduled at the centralized platform (218).

2. The method (600) as claimed in claim 1, wherein the request includes one or more user preferences to schedule the task, wherein the one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task.

3. The method (600) as claimed in claim 1, wherein upon checking, whether the task is pre-scheduled at the centralized platform (218), the one or more processors (202) is configured to, notify the user by a failure message, when the task is pre-scheduled at the centralized platform (218).

4. The method (600) as claimed in claim 1, wherein upon checking, whether the task is pre-scheduled at the centralized platform, the one or more processors (202) is configured to, notify the user by a success message, when the task is not pre-scheduled at the centralized platform (218).

5. The method (600) as claimed in claim 1, wherein the step of, creating, the scheduled task, when the task is not pre-scheduled at the centralized platform (218), includes the steps of:
triggering, by the one or more processors (202), the scheduled task at a scheduled time at the centralized platform (218); and
notifying, by the one or more processors (202), initiation of the task to the user, wherein the notification includes providing information to the user pertaining to a timeline for completion of the task as per a user-defined timeline.

6. The method (600) as claimed in claim 5, wherein the one or more processors (202), allows the user to set the user-defined timeline via a User Equipment (UE) (102) in real time.

7. The method (600) as claimed in claim 1, wherein the one or more processors (202), allows the user to pre-set frequency of notifications that the user can receive in run time pertaining to scheduling the task.

8. The method (600) as claimed in claim 1, wherein the task pertains to at least one of, a backup of a running Virtual network functions (VNF) instance and Container Network Functions (CNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure.

9. The method (600) as claimed in claim 1, wherein upon creating the scheduled task, the one or more processors (202), stores the created scheduled task at the centralized platform.

10. The method (600) as claimed in claim 1, wherein the one or more processors (202) is in communication with the centralized platform (218) and a Backup and Restore (BR) instance (220), wherein the one or more processors (202) enables the BR instance (220) to create, update and delete the one or more tasks at the centralized platform (218) as per instructions from the user.

11. The method (600) as claimed in claim 1, wherein the one or more processors (202), is connected to a plurality of instances, wherein in the event a current instance fails, then the one or more processors (202) is configured to replace in real time, the current instance with a new instance in order to schedule and process the task at the centralized platform without any delay.

12. A system (108) for automatically scheduling of a task, the system (108) comprising:
a receiving unit (210), configured to receive, a request from a user via User Equipment (UE) (102) to create or modify and schedule a task;
a checking unit (212), configured to, check, whether the task is pre-scheduled at a centralized platform (218); and
a scheduler unit (216), configured to create, the scheduled task when the task is not pre-scheduled at the centralized platform (218).

13. The system (108) as claimed in claim 12, wherein the request includes one or more user preferences to schedule the task, wherein the one or more user preferences includes at least one of, type of an Application Programming Interface (API), type of a File Transfer Protocol (FTP) and a type of an event or query to be used to schedule the task.

14. The system (108) as claimed in claim 12, wherein upon checking, whether the task is pre-scheduled at the centralized platform (218), a notifying unit (214) is configured to notify the user by a failure message, when the task is pre-scheduled at the centralized platform (218).

15. The system as claimed in claim 12, wherein upon checking whether the task is pre-scheduled at the centralized platform (218), the notifying unit (214) is configured to notify the user by a success message, when the task is not pre-scheduled at the centralized platform (218).

16. The system (108) as claimed in claim 12, wherein to create, the scheduled task, when the task is not pre-scheduled at the centralized platform (218) the system (108) comprises:
triggering unit (222), configured to trigger the scheduled task at a scheduled time at the centralized platform (218); and
notifying unit (214), configured to notify an initiation of the task to the user, wherein the notification includes providing information to the user pertaining to a timeline for completion of the task as per a user-defined timeline.

17. The system (108) as claimed in claim 16, wherein the user allows to set the user-defined timeline via a user interface in real time.

18. The system (108) as claimed in claim 16, wherein the user allows to pre-set frequency of notifications that the user can receive in run time pertaining to scheduling the task.

19. The system (108) as claimed in claim 12, wherein the task pertains to at least one of, a backup of a running Virtual network functions (VNF) instance and Container Network Functions (CNF) instance, restoration in case of any VNF/ Virtual Network Function Component (VNFC) failure.

20. The system (108) as claimed in claim 12, wherein upon creating the scheduled task, the created scheduled task is stored at the centralized platform (218).

21. The system (108) as claimed in claim 12, wherein the centralized platform (218) is in communication with a Backup and Restore (BR) instance (220), wherein the BR instance (220) is enabled to create, update and delete the one or more tasks at the centralized platform (218) as per instructions from the user.

22. The system (108) as claimed in claim 12, wherein the centralized platform (218) is connected to a plurality of instances, wherein in the event a current instance fails, then in real time, the current instance is replaced with a new instance in order to schedule and process the task at the centralized platform (218) without any delay.

23. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
transmit, a request to schedule a task to the one or more processors (202) in order to avail one or more services; and
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.