Patent information
IP India · live recordAbstract
The present disclosure relates to a method and a system for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100]. The disclosure encompasses receiving a create task request associated with the task to be scheduled at the PSC service [1100] from a capacity and performance monitoring manager (CP) [1090]. The create task request defines a task schedule for the task. The disclosure further encompasses identifying whether a status associated with the create task request is positive or negative and creating the task at the PSC service [1100] for scheduling when the positive status is determined. The present disclosure further encompasses scheduling the task based on the task schedule. [FIG. 4]
Applicants
1Inventors
19Claims
16Specification
Show full textCollapse
FORM 2 THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003 COMPLETE SPECIFICATION (See section 10 and rule 13) “METHOD AND SYSTEM FOR SCHEDULING A TASK BY A PLATFORM SCHEDULER AND CRON JOBS SERVICE” We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India. The following specification particularly describes the invention and the manner in which it is to be performed. 2 METHOD AND SYSTEM FOR SCHEDULING A TASK BY A PLATFORM SCHEDULER AND CRON JOBS SERVICE FIELD OF THE DISCLOSURE 5
[0001] Embodiments of the present disclosure generally relate to the field of network performance management. More particularly, embodiments of the present disclosure relate to scheduling a task by a platform scheduler and cron jobs (PSC) service. 10 BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include 15 certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art. 20 [0003] A scheduler service is a system that manages the execution of jobs, typically based on a schedule or some other trigger. A scheduler service with event-driven architecture, makes the jobs highly available, compatible with distributed environments, extendable and monitorable. With the right technology stack and design, one can develop a custom scheduler service that meets specific needs. The 25 scheduling systems are integrated with microservices architecture to optimize computational resources and enhance the performance of applications. Schedulers play an essential role in the management of computational resources. They are responsible for allocating resources to various tasks, ensuring that each task receives the resources it requires to execute efficiently. In a microservices 30 environment, a scheduler can be used to manage the distribution of tasks among the 3 various services, ensuring that the overall system operates efficiently. Schedulers are particularly important in a microservices environment because they help to manage the complexity of dealing with multiple, independent services. They can help to ensure that each service is given the resources it needs to function effectively and can also help 5 to manage the interdependencies between services, ensuring that they work together effectively. However, the current network systems face a critical challenge in efficiently managing and scheduling jobs/tasks within various network components such as microservice(s). The scheduler services for task creation and scheduling are struggling to effectively coordinate with the network functions. 10
[0004] Moreover, the network component(s) such as a capacity and performance monitoring manager/ capacity monitoring manager (CP) primary function revolves around monitoring resource usages, including CPU, RAM, storage, bandwidth, and various parameters. The CP primarily interacts with a centralised platform such as 15 platform scheduler & cron job (PSC) service by continuously sending queries and receiving event acknowledgments for breached events, wherein the resource usage may end up surpassing predefined threshold values. Further, the core services of the PSC service are struggling to effectively coordinate with the CP. Therefore, this process has proven to be inefficient and prone to delays, leading to suboptimal task 20 scheduling in the network systems.
[0005] Therefore, there exists an imperative need in the art to develop methods and systems to overcome the limitations posed above by streamlining the communication and interaction between the network components, such as between 25 the CP and the PSC for overcoming inefficient task scheduling. Thus, the present disclosure provides methods and systems for efficient task management at the PSC services. OBJECTS OF THE DISCLOSURE 30 4
[0006] This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the description. In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present disclosure is to substantially reduce the limitations 5 and drawbacks of the prior arts as described hereinabove.
[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. 10
[0008] It is an object of the present disclosure to provide a solution for automatically scheduling a task by a platform scheduler and cron jobs (PSC) service. 15 [0009] Another object of the present disclosure is to allow receipt of http request to create and schedule a task request.
[0010] Yet another object of the present disclosure is reduction in network development, network validation, network integration, and network testing efforts 20 of the network personnel.
[0011] Yet another object of the present disclosure is the centralization of the task management. 25 SUMMARY
[0012] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed 30 subject matter. 5
[0013] An aspect of the present disclosure may relate to a method for scheduling a task by a platform scheduler and cron jobs (PSC) service. The method comprises receiving, by a transceiver unit at the platform scheduler and cron jobs (PSC) service from a Capacity and 5 Performance monitoring manager (CP), a create task request associated with a task. The create task request comprises a task schedule for the task. The method further comprises identifying, by an identification unit at the platform scheduler and cron jobs (PSC) service, a status associated with the create task request. The status is at least one of a positive status and a negative status. The 10 method further comprises creating, by an execution unit at the platform scheduler and cron jobs (PSC) service , the task based on the positive status. And the method further comprises scheduling, by the execution unit at the platform scheduler and cron jobs (PSC) service , the task based on the task schedule. 15 [0014] In an exemplary aspect of the present disclosure, the positive status associated with the create task request indicates non-existence of the requested task at the platform scheduler and cron jobs (PSC) service.
[0015] In an exemplary aspect of the present disclosure, the negative status 20 associated with the create task request indicates pre-existence of the requested task at the platform scheduler and cron jobs (PSC) service.
[0016] In an exemplary aspect of the present disclosure, the method further comprises transmitting by the transceiver unit from the platform scheduler and cron 25 jobs (PSC) service to the CP, a failure response in an event the negative status associated with the create task request is identified by the identification unit at the platform scheduler and cron jobs (PSC) service.
[0017] In an exemplary aspect of the present disclosure, prior to creating the task 30 based on the positive status, the method comprises determining, by the 6 identification unit at the platform scheduler and cron jobs (PSC) service, a breach condition associated with the task, based on a predefined task capacity. The method further comprises transmitting, by the transceiver unit from the platform scheduler and cron jobs (PSC) service to the CP, an event acknowledgement message in an 5 event the breach condition associated with the task is determined.
[0018] In an exemplary aspect of the present disclosure, the method further comprises storing, by a storage unit, the created task in a database. The method further comprises transmitting, by the transceiver unit, a success response from the 10 platform scheduler and cron jobs service (PSC) to the CP. The method further comprises triggering, by the execution unit at the platform scheduler and cron jobs service (PSC), the task based on task schedule. And the method further comprises transmitting, by the transceiver unit from the platform scheduler and cron jobs service (PSC), a notification to the CP based on the triggering of the task. 15
[0019] In an exemplary aspect of the present disclosure, the CP, determines a usage of one or more resources on receiving the notification based on triggering of the task. 20 [0020] In an exemplary aspect of the present disclosure, the scheduling for the task comprises at least a daily scheduling, a weekly scheduling and a monthly scheduling.
[0021] In an exemplary aspect of the present disclosure, a frequency of the 25 notification is configurable at run time of the task.
[0022] Another aspect of the present disclosure may relate to a system for scheduling a task by a platform scheduler and cron jobs (PSC) service . The system comprises a transceiver unit at the platform scheduler and cron jobs (PSC) service 30 , configured to receive, a create task request associated with the task, from a Capacity and Performance monitoring manager (CP). The create task request 7 comprises a task schedule for the task. The system further comprises an identification unit at the platform scheduler and cron jobs (PSC) service , configured to identify, a status associated with the create task request. The status is at least one of a positive status and a negative status. The system further comprises an execution unit, at the platform 5 scheduler and cron jobs (PSC) service , configured to create, the task based on the positive status. The execution unit is further configured to schedule, the task based on the task schedule.
[0023] Another aspect of the present disclosure may relate to a non-transitory 10 computer-readable storage medium storing instruction for scheduling a task by a platform scheduler and cron jobs (PSC) service, the storage medium comprising executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, a create task request associated with the task, from a Capacity and Performance monitoring manager (CP). The create task request 15 comprises a task schedule for the task. Further, the executable code which, when executed, causes an identification unit to identify, a status associated with the create task request. The status is at least one of a positive status and a negative status. Further, the executable code which, when executed, causes an execution unit to create, the task based on the positive status. Further, the executable code which, 20 when executed, causes the execution unit to schedule, the task based on the task schedule. DESCRIPTION OF DRAWINGS 25 [0024] 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 30 disclosure. Some drawings may indicate the components using block diagrams and 8 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. 5
[0025] FIG.1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture [100].
[0026] FIG. 2 illustrates an exemplary block diagram of a computing device [200] 10 upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0027] FIG. 3 illustrates an exemplary block diagram of a system [300] for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100], in 15 accordance with exemplary implementations of the present disclosure.
[0028] FIG. 4 illustrates an exemplary method [400] flow diagram for scheduling the task by the platform scheduler and cron jobs (PSC) service [1100], in accordance with the exemplary embodiments of the present disclosure. 20
[0029] FIG. 5 illustrates another exemplary flow chart depicting a network environment [500] showing interaction between a capacity and performance monitoring manager (CP) [1090], a platform scheduler and cron jobs (PSC) service
[11001100] and an Elastic Search (ES) database [504] for scheduling the task, in 25 accordance with exemplary embodiments of the present disclosure.
[0030] FIG. 6 illustrates another exemplary block diagram of a system [600] for scheduling the task, in accordance with exemplary embodiments of the present disclosure. 30 9
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure. DETAILED DESCRIPTION 5
[0032] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific 10 details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of 15 the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0033] The ensuing description provides exemplary embodiments only, and is not 20 intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the 25 disclosure as set forth.
[0034] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the disclosure. These terms are not 30 intended to limit the scope of the disclosure or imply any specific functionality or 10 limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without 5 departing from the scope of the disclosure as defined herein.
[0035] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these 10 specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments. 15
[0036] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or 20 concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0037] The word “exemplary” and/or “demonstrative” is used herein to mean 25 serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques 30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms 11 “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements. 5
[0038] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing 10 function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low 15 Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, 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 device as may be obvious to a person skilled in 20 the art for implementation of the features of the present disclosure.
[0039] Further, the user device and/or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry 25 for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processor (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other 30 type of integrated circuits, etc. The processor may perform signal coding data 12 processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0040] As used herein, “a 5 user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The 10 user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of 15 a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0041] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a 20 form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective 25 functions.
[0042] As used herein, “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define 30 communication or interaction of one or more modules or one or more units with 13 each other, which also includes the methods, functions, or procedures that may be called.
[0043] All modules, units, components used herein, unless explicitly excluded herein, may be software 5 modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array 10 circuits (FPGA), any other type of integrated circuits, etc.
[0044] As used herein, the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system 15 and/or connected with the system.
[0045] As discussed in the background section, the current known solutions have several shortcomings. The capacity and monitoring manager (CP) primarily interacts with a centralised platform such as platform scheduler & cron job (PSC) 20 service by continuously sending queries and receiving event acknowledgments for breached events, wherein the resource usage may end up surpassing predefined threshold values. The core services of the PSC service are struggling to effectively coordinate with the CP. Therefore, this process has proven to be inefficient and prone to delays, leading to suboptimal task scheduling in the network systems. The 25 present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology for scheduling a task by the PSC service. The present disclosure is implemented with the help of various components of a management and orchestration (MANO) architecture. 14
[0046] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture/ platform [100], in accordance with exemplary implementation of the present disclosure. The MANO architecture [100] is developed for managing telecom cloud infrastructure automatically, mana 5 ging design or deployment design, managing instantiation of a network node(s) etc. The MANO architecture [100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native/ Container Network Function (CNF). The MANO architecture [100] is used to auto-instantiate the VNFs into the corresponding environment of the present disclosure so that it could help 10 in onboarding other vendor(s) CNFs and VNFs to the platform.
[0047] As shown in FIG. 1, the MANO architecture [100] comprises a user interface layer, a network function virtualization (NFV) and software defined network (SDN) design function module [104]; a platforms foundation services 15 module [106], a platform core services module [108] and a platform resource adapters and utilities module [112], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. 20 [0048] The NFV and SDN design function module [104] further comprises a VNF lifecycle manager (compute) [1042]; a VNF catalogue [1044]; a network services catalogue [1046]; a network slicing and service chaining manager [1048]; a physical and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF lifecycle manager (compute) [1042] is responsible for determining on 25 which server of the communication network the microservice will be instantiated. The VNF lifecycle manager (compute) [1042] will manage the overall flow of incoming/ outgoing requests during interaction with the user. The VNF lifecycle manager (compute) [1042] is responsible for determining which sequence to be followed for executing the process. For e.g. in an AMF network function of the 30 communication network (such as a 5G network), sequence for execution of 15 processes P1 and P2 etc. The VNF catalogue [1044] stores the metadata of all the VNFs (also CNFs in some cases). The network services catalogue [1046] stores the information of the services that need to be run. The network slicing and service chaining manager [1048] manages the slicing (an ordered and connected sequence of network service/ network 5 functions (NFs)) that must be applied to a specific networked data packet. The physical and virtual resource manager [1050] stores the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager (compute) [1042], the CNF lifecycle manager [1052] is similarly used for the CNFs lifecycle management. 10
[0049] The platforms foundation services module [106] further comprises a microservices elastic load balancer [1062]; an identify & access manager [1064]; a command line interface (CLI) [1066]; a central logging manager [1068]; and an event routing manager [1070]. The microservices elastic load balancer [1062] is 15 used for maintaining the load balancing of the request for the services. The identify & access manager [1064] is used for logging purposes. The command line interface (CLI) [1066] is used to provide commands to execute certain processes which require changes during the run time. The central logging manager [1068] is responsible for keeping the logs of every services. Theses logs are generated by the 20 MANO platform [100]. These logs are used for debugging purposes. The event routing manager [1070] is responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.
[0050] The platforms core services module [108] further comprises NFV 25 infrastructure monitoring manager [1082]; an assure manager [1084]; a performance manager [1086]; a policy execution engine [1088]; a capacity monitoring manager [1090]; a release management (mgmt.) repository [1092]; a configuration manager & (Golden Configuration Template (GCT)) [1094]; an NFV platform decision analytics [1096]; a platform NoSQL DB [1098]; a platform 30 schedulers and cron jobs [1100]; a VNF backup & upgrade manager [1102]; a micro 16 service auditor [1104]; and a platform operations, administration and maintenance manager [1106]. The NFV infrastructure monitoring manager [1082] monitors the infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager [1084] is responsible for supervising the alarms the vendor 5 is generating. The performance manager [1086] is responsible for manging the performance counters. The policy execution engine [1088] is responsible for managing all the policies. The capacity monitoring manager (CP) [1090] is responsible for sending the request to the policy execution engine [1088]. The capacity and performance monitoring manager/ capacity monitoring manger (CP) 10 [1090] is capable of monitoring usage of network resources such as but not limited to CPU utilization, RAM utilization and storage utilization across all the instances of the virtual infrastructure manager (VIM) or simply the NFV infrastructure monitoring manager [1082]. The CP [1090] is also capable of monitoring said network resources for each instance of the VNF. The CP [1090] is responsible for 15 constantly tracking the network resource utilization. The release management (mgmt.) repository [1092] is responsible for managing the releases and the images of all the vendor network nodes. The configuration manager & (GCT) [1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics [1096] helps in deciding the priority of using the network resources. It is 20 further noted that the policy execution engine [1088], the configuration manager & (GCT) [1094] and the NFV platform decision analytics [1096] work together. The platform NoSQL DB [1098] is a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. The platform schedulers and cron jobs [1100] schedules the task such as but not limited to triggering of an 25 event, traversing the network graph etc. The VNF backup & upgrade manager
[1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backups on demand in case of server failure. The micro service auditor [1104] audits the microservices. For e.g., in a hypothetical case, instances not being instantiated by the MANO architecture [100] and using the network resources then 30 the micro service auditor [1104] audits and informs the same so that resources can 17 be released for services running in the MANO architecture [100], thereby assuring the services only run on the MANO platform [100]. The platform operations, administration and maintenance manager [1106] is used for newer instances that are spawning. 5
[0051] The platform resource adapters and utilities module [112] further comprises a platform external API adaptor and gateway [1122]; a generic decoder and indexer (XML, CSV, JSON) [1124]; a docker swarm adaptor [1126]; an OpenStack API adapter [1128]; and a NFV gateway [1130]. The platform external API adaptor and 10 gateway [1122] is responsible for handling the external services (to the MANO platform [100]) that require the network resources. The generic decoder and indexer (XML, CSV, JSON) [1124] gets directly the data of the vendor system in the XML, CSV, JSON format. The docker swarm adaptor [1126] is the interface provided between the telecom cloud and the MANO architecture [100] for communication. 15 The OpenStack API adapter [1128] is used to connect with the virtual machines (VMs). The NFV gateway [1130] is responsible for providing the path to each services going to/incoming from the MANO architecture [100].
[0052] The present disclosure can be implemented on a computing device [200] as 20 shown in FIG. 2. The computing device [200] implements the present disclosure in accordance with the MANO architecture (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing 25 device [200] may also implement a method [400] (as shown in FIG. 4) for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100] (as shown in FIG. 1) utilising a system [300] (as shown in FIG. 3) and a system [600] (as shown in FIG. 6). In another implementation, the computing device [200] itself implements the method [400] for scheduling a task by the PSC service [1100] in a 30 communication network using one or more units configured within the computing 18 device [200], wherein said one or more units can implement the features as disclosed in the present disclosure.
[0053] The computing device [200] may include a bus [202] or other communication mechanism 5 for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202] 10 for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special15 purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 20 [0054] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for 25 displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction 30 information and command selections to the processor [204], and for controlling 19 cursor movement on the display [212]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0055] 5 The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the 10 computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the 15 process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0056] The computing device [200] also may include a communication interface 20 [218] coupled to the bus [202]. The communication interface [218] provides a twoway data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of 25 telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing 30 various types of information. 20
[0057] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code 5 for an application program through the Internet [228], the ISP [226], the local network [222], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution. 10
[0058] The present disclosure is implemented by the system [300] (as shown in FIG. 3). The system [300] may be implemented using the computing device [200] (as shown in FIG. 2). In an implementation, the computing device [200] may be connected to the system [300] to perform the present disclosure. Referring to FIG. 15 3, an exemplary block diagram of the system [300] for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100] in a communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one platform scheduler and cron jobs (PSC) service [1100] and at least one capacity and performance 20 monitoring manager (also known as CP) [1090]. The PSC service [1100] acts as a centralised platform which helps to create and schedule jobs on behalf of other micro services. The PSC service [1100] interacts with multiple microservices like the capacity and performance monitoring manager (CP) [1090]. The CP [1090] constantly tracks the network resource utilization. The CP [1090] tracks usage of 25 each resource such as CPU, RAM and storage across all VIM sites. The CP [1090] is also capable of monitoring these parameters for each instance of the VNF. The CP [1090] tags each resource with a threshold value, which is user-defined. The PSC service [1100] further comprises at least one transceiver unit [304], at least one identification unit [308], at least one execution unit [310] and at least one storage 30 unit [312]. The storage unit [312] further comprises at least one database [3122]. 21 Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG. 3, all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units 5 or the system [300] may comprise any such number of said units, as required to implement the features of the present disclosure. In an implementation, the system [300] may reside in a server or a network entity. In another implementation, the system [300] may reside partly in the server/ network entity. 10
[0059] The system [300] is configured for scheduling a task by the PSC service
[1100], with the help of the interconnection between the components/units of the system [300]. The scheduling here involves assigning or prioritizing network resources to a core network component (such as network node/ function) for 15 carrying out the execution of the intended objectives of the network component. The network resources may include processors, network links, memories etc. The scheduling of tasks in the communication network helps in minimizing network problems such as delays and allows to automate recurring tasks, such as backups, data synchronization and maintenance jobs. 20
[0060] The transceiver unit [304] at the PSC service [1100], is configured to receive, a create task request associated with the task, from CP [1090]. The create task request comprises a task schedule for the task. Further, the create task request comprises parameters such as Task type, Task frequency, Task periodicity, Task 25 counter and Task information. The Task type may be for example, an API creation, an FTP, an EVENT creation or a QUERY. The Task frequency can be periodic such as done daily, weekly, monthly or one-time execution as per the requirement of the operations team or configuration of the CP [1090]. The Task periodicity may define the time period when the task is to be scheduled. The Task counter defines the 30 number of task notifications. The Task information defines details related to resources such as name, identifier, address and threshold value of usage. An 22 example of a tasks may be such as, creating an event to clear cache weekly. The PSC service [1100] may include a network component that works as a task manager for managing the sequence of network tasks. The PSC service [1100] may also employ a fixed queueing algorithm for governing the scheduling of the task. The create task request is responsible 5 for defining the initial stages or actions for the task execution.
[0061] The identification unit [308] at the PSC service [1100], is configured to identify, a status associated with the create task request. The status is at least one of 10 a positive status and a negative status.
[0062] The execution unit [310], at the PSC service [1100], is configured to create, the task based on the positive status. The execution unit [310] is further configured to schedule, the task based on the task schedule. 15
[0063] In an exemplary aspect of the present disclosure, the positive status associated with the create task request indicates non-existence of the requested task at the PSC service [1100]. The non-existence is indicative of the fact that the requested task is not in the scheduler’s queue comprising a list of tasks. The non20 existence also indicates that the task has not been created or scheduled for execution.
[0064] In an exemplary aspect of the present disclosure, the negative status associated with the create task request indicates pre-existence of the requested task 25 at the PSC [1100]. The pre-existence is indicative of the fact that the requested task is present in the scheduler’s queue comprising list of tasks. The pre-existence of the task indicates that the task has been created or scheduled for execution. The execution unit [310] only creates task which have positive status, which ensures there is no overlapping of the tasks. It is to be noted that the non-existence or pre30 existence of the task is identified by identification unit [308], which compares one 23 or more attributes of the created task stored at the database [3122], such as Task ID (identifier).
[0065] In an exemplary aspect of the present disclosure, the transceiver unit [304] is further configured to transmit, 5 from the PSC service [1100] to the CP monitoring manager [1090], a failure response in an event the negative status associated with the create task request is identified by the identification unit [308] at the PSC service
[1100]. The failure response represents that the task creation failed as the requested task was present in the scheduler’s queue. In an implementation, if a similar task is 10 identified, then the identified similar Task ID is sent in the failure response along with error code associated with the negative status.
[0066] In an exemplary aspect of the present disclosure, prior to creating the task based on the positive status, the identification unit [308] of the system [300] is 15 further configured to determine a breach condition associated with the task, based on a predefined task capacity. The transceiver unit [304] is further configured to transmit, from the PSC service [1100] to the CP monitoring manager [1090], an event acknowledgement message in an event the breach condition associated with the task is determined. The event acknowledgement message refers to a notification 20 sent when the breach is detected where the task is being monitored by the CP [1090] for specific conditions. The breach condition associated with the task, based on a predefined task capacity, indicates that the network resources are overwhelmed or over utilised and the PSC service [1100] is not in a situation to handle additional capacity for the tasks. 25
[0067] In an exemplary aspect of the present disclosure, the storage unit [312] is further configured to store the created task in a database [3122]. The transceiver unit [304] is further configured to transmit a success response from the PSC service
[1100] to the CP [1090]. It is to be noted that the success response comprises 30 attributes such as but not limited to a success code, a Task name, Task ID etc. The 24 execution unit [310] is further configured to trigger the task based on the task schedule. The transceiver unit [304] is further configured to transmit a notification to the CP [1090] based on the triggering of the task.
[0068] In an exemplary 5 aspect of the present disclosure, the CP [1090] is configured to determine a usage of one or more resources, on receiving the notification based on triggering of the task. The CP [1090] constantly tracks the network resource utilization of the resources assigned to the task. The CP [1090] tags each resource with a threshold value, which is user-defined. When PSC service 10 [1100] triggers a notification to the CP [1090] at scheduled time, then CP [1090] gathers current resource level and compares with threshold tagged and takes appropriate action when the current usage of resource exceeds this value.
[0069] In an exemplary aspect of the present disclosure, the scheduling for the task 15 comprises at least a daily scheduling, a weekly scheduling and a monthly scheduling.
[0070] In an exemplary aspect of the present disclosure, a frequency of the notification is configurable at run time of the task. It is pertinent to note that the 20 frequency of the notification is configurable by a user at the run time of the task via a graphical user interface (GUI) [604] (as shown in FIG.6) or a command line interface (CLI) [606] (as shown in FIG.6). Thus, the GUI [604] or the CLI [606] of the PSC service [1100] enables the user to create a task about which notification needs to be sent periodically or just one time, thereby giving notification of the 25 created and triggered tasks as per requirement of the user.
[0071] Referring to FIG. 4, an exemplary method flow diagram [400] for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100], in accordance with exemplary implementations of the present disclosure is shown. 30 The scheduling here involves assigning or prioritizing network resources to a core 25 network component (such as network node/ function) for carrying out the execution of the intended objectives of the network component. The network resources may include processors, network links, memories etc., based on the scheduling. The scheduling of the task in the communication network helps in minimizing network problems such as delays, 5 and allows to automate recurring tasks, such as backups, data synchronization and maintenance jobs. In an implementation the method [400] is performed by the system [300] (as shown in FIG. 3). In another implementation, the method [400] is performed by the system [600] (as shown in FIG. 6). Further, in an implementation, the system [300] may be present in a server device to 10 implement the features of the present disclosure. Furthermore, in an implementation, the system [600] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402]. 15 [0072] At step [404], the method [400] comprises receiving, by a transceiver unit
[304] at the platform scheduler and cron jobs (PSC) service [1100] from a Capacity and Performance monitoring manager (CP) [1090], a create task request associated with the task. Further, the create task request comprises parameters such as Task type, Task frequency, Task periodicity, Task counter and Task information. The 20 Task type may be for example, an API creation, an FTP, an EVENT creation or a QUERY. The Task frequency can be periodic such as done daily, weekly, monthly or one time execution as per the requirement of the operations team or configuration of the CP [1090]. The Task periodicity may define the time period when the task is to be scheduled. The Task counter defines the number of task notifications. The 25 Task information defines details related to resources such as name, identifier, address and threshold value of usage. An example of a tasks may be such as, creating an event to clear cache weekly. The PSC service [1100] may include a network component that works as arbiter over a particular network node for managing the sequence of network tasks. The PSC service [1100] may also employ 26 a fixed queueing algorithm for governing the scheduling of the task. The create task request is responsible for defining the initial stages or actions for the task execution.
[0073] At step [406], the method [400] comprises identifying, by an identification unit [308] at the PSC service 5 [1100], a status associated with the create task request. The status is at least one of a positive status and a negative status.
[0074] At step [408], the method [400] further comprises creating, by an execution unit [310] at the PSC service [1100], the task based on the positive status. 10
[0075] At step [410], the method [400] further comprises scheduling, by the execution unit [310] at the PSC service [1100], the task based on the task schedule.
[0076] In an exemplary aspect of the present disclosure, the positive status 15 associated with the create task request indicates non-existence of the requested task at the PSC service [1100]. The non-existence is indicative of the fact that the requested task is not in the scheduler’s queue comprising a list of tasks. The nonexistence also indicates that the task has not been created or scheduled for execution. 20
[0077] In an exemplary aspect of the present disclosure, the negative status associated with the create task request indicates pre-existence of the requested task at the PSC service [1100]. The pre-existence is indicative of the fact that the requested task is existing in the scheduler’s queue comprising list of tasks. The pre25 existence of the task indicates that the task has been created or scheduled for execution. The execution unit [310] only creates task which have positive status, which ensures there is no overlapping of the tasks. It is to be noted that the nonexistence or pre-existence of the task is identified by identification unit [308], which compares one or more attributes of the created task stored at the database [3122]. 30 27
[0078] In an exemplary aspect of the present disclosure, the method [400] further comprises transmitting by the transceiver unit [304] from the PSC service [1100] to the CP [1090], a failure response in an event the negative status associated with the create task request is identified by the identification unit [308] at the PSC service
[1100]. The failure 5 response represents that the task creation failed as the requested task was present in the scheduler’s queue. If similar task is identified, then the identified similar task ID is sent in the failure response along with error code associated with negative status. 10 [0079] In an exemplary aspect of the present disclosure, prior to creating the task based on the positive status, the method [400] comprises determining, by the identification unit [308] at the PSC service [1100], a breach condition associated with the task, based on a predefined task capacity. The method [400] further comprises transmitting, by the transceiver unit [304] from the PSC service [1100] 15 to the CP [1090], an event acknowledgement message in an event the breach condition associated with the task is determined. In an exemplary aspect of the present disclosure, an instance of the PSC [1100] creates the task if the breach condition associated with the task is determined at the PSC [1100]. 20 [0080] The event acknowledgement message refers to a notification sent when the breach is detected where the task is being monitored by the CP [1090] for specific conditions. The breach condition associated with the task, based on a predefined task capacity, indicates that the network resources are overwhelmed or over utilised and the PSC service [1100] is not in a situation to handle additional capacity for the 25 tasks.
[0081] In an exemplary aspect of the present disclosure, the method [400] further comprises storing, by a storage unit [312], the created task in a database [3122]. The method [400] further comprises transmitting, by the transceiver unit [304], a 30 success response from the PSC service [1100] to the CP [1090]. It is to be noted that the success response comprises attributes such as but not limited to success 28 code, task name, task ID etc. The method [400] further comprises triggering, by the execution unit [310] at the PSC service [1100], the task based on the task schedule. And the method [400] further comprises transmitting, by the transceiver unit [304] from the PSC service [1100], a notification to the CP [1090] based on the triggering of the task. The notification here 5 comprises attributes such as but not limited to task ID, task name, task information i.e., resources that are assigned to the task and to be monitored.
[0082] In an exemplary aspect of the present disclosure, the CP [1090], determines 10 a usage of one or more resources, on receiving the notification based on triggering of the task. The CP [1090] is capable of monitoring usage of network resources such as but not limited to CPU utilization, RAM utilization and storage utilization across all the instances of the virtual infrastructure manager (VIM) or simply the NFV infrastructure monitoring manager [1082]. The CP [1090] is also capable of 15 monitoring said network resources for each instance of the VNF. The CP [1090] is responsible for constantly tracking the network resource utilization. The CP [1090] tags each resource with a threshold value, which is user-defined. It then creates a task at the PSC [1100]. When PSC [1100] triggers a response to the CP [1090] at a scheduled time, then the CP [1090] gathers current network resource usage level 20 and compares with threshold attached/ tagged to the network resource being used and takes appropriate action when the current usage of network resource exceeds the preset threshold value. Thus, the CP [1090] constantly tracks the network resource utilization. 25 [0083] In an exemplary aspect of the present disclosure, the scheduling for the task comprises at least a daily scheduling, a weekly scheduling and a monthly scheduling.
[0084] In an exemplary aspect of the present disclosure, a frequency of the 30 notification is configurable at run time of the task. It is pertinent to note that the 29 frequency of the notification is configurable by a user at the run time of the task via a graphical user interface (GUI) [604] (as shown in FIG.6) or a command line interface (CLI) [606] (as shown in FIG.6). Thus, the platform scheduler and cron jobs (PSC) service [1100] enables the user to create a task about which notification needs to be send periodically or 5 just one time, thereby giving notification of the task as per requirement of the user.
[0085] Thereafter, the method [400] terminates at step [412]. 10 [0086] Referring to FIG. 5, another exemplary flow chart depicting an interaction between a capacity and performance monitoring manager (CP) [1090] (also shown in FIG. 3), a platform scheduler and cron jobs (PSC) service [11001100] and an Elastic Search (ES) database [504] for scheduling a task, in a network environment
[500] is shown, in accordance with the exemplary embodiments of the present 15 disclosure. The present disclosure may be implemented by the system [300] (as shown in FIG. 3) and the system [600] (as shown in FIG. 6) having the computing device [200] (as shown in FIG. 2). In an implementation, the computing device
[200] may be connected to the system [300] to perform scheduling of the task by the PSC [11001100]. Further, the network environment [500] comprises various 20 components of MANO architecture [100] (as shown in FIG. 1) in implementation of the present disclosure. The network environment [500] comprises the capacity and performance monitoring manager (CP) [1090], the platform scheduler and cron jobs service (PSC) [1100] and the Elastic Search (ES) database [504]. In another implementation of the present disclosure, the capacity and performance monitoring 25 manager (CP) [1090] performs the functions appertain to the capacity monitoring manager [1090] (as shown in FIG. 1) of the MANO architecture [100]. Further, the Elastic Search (ES) [504] is a distributed search and analytics engine. Elasticsearch (ES) is used for data ingestion, enrichment, storage, analysis, and visualization. At its core, Elasticsearch (ES) acts as a server that can process JSON requests and 30 gives back JSON data. So, PSC service [1100] interacts with Elasticsearch (ES) 30 database [504] for fetching the data and provide the relevant information to other microservices. The interaction between the capacity and performance monitoring manager (CP) [1090], the PSC service [11001100] and the Elastic Search (ES) database [504] is performed in the following manner: Step 1 (5 S1): The CP [1090] sends an HTTP REQUEST for creation and scheduling of a task. This request is sent to the PSC [1100] for scheduling as a TASK REQUEST. It is sent to confirm if the task is already created and scheduled at the PSC [1100]. 10 Step 2 (S2): S2 is performed by the PSC [1100] for affirming that the requested task has not been created and scheduled. If the task has been created and scheduled, then the PSC [1100] sends back a FAILURE RESPONSE to the CP
[1090]. The FAILIRE RESPONSE is reflective of the fact that the requested task exists at the PSC [1100] and therefore the TASK REQUEST cannot be 15 performed. Step 3 (S3): If the requested task does not exist and the PSC [1100] identifies that the requested task has not been scheduled, then PSC [1100] checks if the task capacity has reached its maximum capacity or the task capacity has 20 breached. The task capacity breach is checked at step S3. If the task capacity is not breached, the PSC [1100] sends the event acknowledgement back to the CP
[1090]. Step 4 (S4): After sending the acknowledgement to the CP [1090] that the task 25 capacity is not breached, the PSC [1100] creates the requested task and stores the created task in the ES [504] at step S4. Step 5 (S5): Once the task is scheduled for execution at the PSC [1100], a notification is sent out by the PSC [1100] to the CP [1090] that the task is 30 successfully created and scheduled. Step S4 indicates that the task has been 31 successfully created and scheduled for execution at the PSC [1100]. The PSC
[1100] informs the CP [1090] about the task creation and scheduling via a notification. Step 6 (5 S6): Later, when the task is triggered based on the schedule, a notification via the HTTP request is sent to the CP [1090]. Step S5 is performed when the task is triggered at the scheduled time. Thereafter the PSC [1100] notifies the CP [1090] via the HTTP REQUEST that task is performed at the scheduled time. 10
[0087] Referring to FIG. 6, another exemplary block diagram of a system [600] for scheduling the task is shown, in accordance with the exemplary embodiments of the present disclosure. The system comprises an event routing manager (ERM)
[602]; a graphical user (GU) interface [604]; a CL interface [606]; an edge load 15 balancer (EDGE-LB/ ELB) [608]; a platform scheduler and cron jobs (PSC) service
[1100]; an elastic search database (ES-DB) client [612] connected to Elastic Search (ES) database [504] (also shown as ES [504] in FIG. 5); and a virtual network function (VNF) manager [614]. The VNF manager [614] further manages various virtual machines (VM). The ERM [602] is a microservice which is used to route the 20 request to and from the required microservices. The interface between the PSC
[1100] and the ERM [602] is used to route all the incoming requests to PSC [1100] and all the outgoing requests from PSC [1100]. This is achieved through Publisher and Subscriber policy. If any microservice wants to send request to PSC [1100] then that event should be registered in ERM [602] with publisher as PSC [1100] 25 and subscriber as other microservice, such as CP [1090] as shown in FIG. 1. Further, if PSC [1100] wants to send request to other microservice then that event should be registered in ERM [602] with subscriber as PSC [1100] and publisher as other microservice.. The ELB [608] is used to send the requests between the active instances of one microservice to another microservice. The PSC [1100] is a process 30 scheduler that allows one to execute commands, scripts, and programs following 32 specified schedules via input given through either the graphical user (GU) interface
[604] or the CL interface [606]. It is pertinent to note that the frequency of the notification is configurable by a user at the run time of the task via a graphical user interface (GUI) [604] or a command line interface (CLI) [606]. Thus, the PSC service [1100] enables the user to 5 create a task about which notification needs to be sent periodically or just one time, thereby giving notification of the task as per requirement of the user. The PSC [1100] carries out the following functions: 1. Cron Management [616] - It is used to manage all the active and inactive crons created at the platform core services module (or PSC) [108] (as shown 10 in FIG.1). 2. Task Management [618]- It is used to manage all the active and inactive tasks created at the PSC [108]. 3. FCAP Management [620]– A Fault, Configuration, Accounting, Performance and Security (FCAP) management is done for all the counters 15 and alarms created at the PSC [108]. 4. Event Handling [622]– PSC [108] manages all the events between microservices through the event handling function of the PSC [1100]. 5. High Availability (HA) and Fault Tolerance [624]– The PSC handles all the requests if one running instance goes down, then another active instance 20 will complete that request, through the HA and Fault Tolerance function of the PSC [1100].
[0088] The ES [504] stores the created and scheduled tasks or jobs The ES [504] interacts with the PSC [1100] via the ES-DB client [612]. The ES [504] keeps the 25 tasks in the stack data structure based upon the execution-priority of the tasks. The VNF manager [614] is a key component of the network functions virtualization (NFV) management and organization (MANO) architectural framework (as shown in FIG.1). The NFV defines standards for compute, storage, and networking resources that can be used to build virtualized network functions. The VNF manager 30 [614] works in tandem with the NFV to help standardize the functions of virtual 33 networking and increase the interoperability of software-defined networking elements.
[0089] Another aspect of the present disclosure may relate to a non-transitory computer-readable storage 5 medium storing instruction for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100], the storage medium comprising executable code which, when executed by one or more units of a system
[300], causes a transceiver unit [304] to receive, a create task request associated with the task, from a Capacity and Performance monitoring manager (CP) [1090]. 10 The create task request comprises a task schedule for the task. Further, the executable code which, when executed, causes an identification unit [308] to identify, a status associated with the create task request, wherein the status is at least one of a positive status and a negative status. Further, the executable code which, when executed, causes an execution unit [310] to create, the task based on the 15 positive status. Further, the executable code which, when executed, causes the execution unit [310] to schedule, the task based on the task schedule.
[0090] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be 20 implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative 25 arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0091] As is evident from the above, the present disclosure provides a technically 30 advanced solution for automatically scheduling the task by the platform scheduler 34 and cron jobs (PSC) service [1100] by delivering tangible benefits in terms of time, effort, and operational efficiency of operating the network systems. The present disclosure offers the notable technical advantages: 1. Addressing the problem of task scheduling on the CP manager/ CP [1090] as the present disclosure 5 leads to significant reduction in network development, network validation, network integration, and network testing efforts of the network personnel (primarily network administrators). 2. An efficient workflow for the network personnel by saving valuable time and network resources constrained by the time. 10 3. Centralization of the task management process for the CP [1090] as the tasks, including but not limited to creation, updates, and deletions of the task in the scheduler queue. The centralization given by the present disclosure absolves one the need of individual operations on each respective network systems. 15 4. Simplification of the task management by ensuring consistency and coherence across the platform, thereby enhancing overall network system efficiency and maintainability.
[0092] While considerable emphasis has been placed herein on the disclosed 20 implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative 25 and non-limiting. 35 We Claim: 1. A method [400] for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100], the method [400] comprising: - receiving, by a transceiver 5 unit [304] at the PSC service [1100] from a Capacity and Performance monitoring manager (CP) [306], a create task request associated with a task, wherein the create task request comprises a task schedule; - identifying, by an identification unit [308] at the PSC service [1100], a 10 status associated with the create task request, wherein the status is at least one of a positive status and a negative status; - creating, by an execution unit [310] at the PSC service [1100], the task based on the positive status; and - scheduling, by the execution unit [310] at the PSC service [1100], the task 15 based on the task schedule. 2. The method [400] as claimed in claim 1, wherein the positive status associated with the create task request indicates non-existence of the requested task at the PSC service [1100]. 20 3. The method [400] as claimed in claim 1, wherein the negative status associated with the create task request indicates pre-existence of the requested task at the PSC service [1100]. 25 4. The method [400] as claimed in claim 3, wherein the method [400] further comprises transmitting by the transceiver unit [304] from the PSC service
[1100] to the CP monitoring manager [1090], a failure response in an event the negative status associated with the create task request is identified by the identification unit [308] at the PSC service [1100]. 30 36 5. The method [400] as claimed in claim 1, wherein prior to creating the task based on the positive status, the method [400] comprises: - determining, by the identification unit [308] at the PSC service [1100], a breach condition associated with the task, based on a predefined task 5 capacity; and - transmitting, by the transceiver unit [304] from the PSC service [1100] to the CP monitoring manager [1090], an event acknowledgement message in an event the breach condition associated with the task is determined. 10 6. The method as claimed in claim 5, wherein, an instance of the PSC [1100] creates the task if the breach condition associated with the task is determined at the PSC [1100]. 7. The method [400] as claimed in claim 1, wherein the method [400] further 15 comprises: • storing, by a storage unit [312], the created task in a database [3122]; • transmitting, by the transceiver unit [304], a success response from the PSC service [1100] to the CP monitoring manager [1090]; • triggering, by the execution unit [310] at the PSC service [1100], the 20 task based on the created task; and • transmitting, by the transceiver unit [304] from the PSC service [1100], a notification to the CP monitoring manager [1090] based on the triggering of the task. 25 8. The method as claimed in claim 7, wherein, the CP [1090], determines a usage of one or more resources on receiving the notification based on triggering of the task. 37 9. The method [400] as claimed in claim 1, wherein the scheduling for the task comprises at least a daily scheduling, a weekly scheduling and a monthly scheduling. 10. The method [400] as 5 claimed in claim 7, wherein a frequency of the notification is configurable at run time of the task. 11. A system [300] for scheduling a task by a platform scheduler and cron jobs (PSC) service [1100], the system [300] comprises: 10 - a transceiver unit [304] at the PSC service [1100], wherein the transceiver unit [304] is configured to: • receive, a create task request associated with a task, from a Capacity and Performance monitoring manager (CP) [1090], wherein the create task request comprises a task schedule; 15 - an identification unit [308] at the PSC service [1100], connected at least with the transceiver unit [304], wherein the identification unit [308] is configured to: • identify, a status associated with the create task request, wherein the status is at least one of a positive status and a negative status; 20 - an execution unit [310], at the PSC service [1100], connected at least with the identification unit [308], wherein the execution unit [310] is configured to: • create, the task based on the positive status; and • schedule, the task based on the task schedule. 25 12. The system [300] as claimed in claim 11, wherein the positive status associated with the create task request indicates non-existence of the requested task at the PSC service [1100]. 38 13. The system [300] as claimed in claim 11, wherein the negative status associated with the create task request indicates pre-existence of the requested task at the PSC service [1100]. 5 14. The system [300] as claimed in claim 11, wherein the transceiver unit [304] is further configured to transmit, from the PSC service [1100] to the CP monitoring manager [1090], a failure response in an event the negative status associated with the create task request is identified by the identification unit 10 [308] at the PSC service [1100]. 15. The system [300] as claimed in claim 11, wherein prior to creating the task based on the positive status, the system [300] comprises: - the identification unit [308] further configured to determine a breach 15 condition associated with the task, based on a predefined task capacity; and - the transceiver unit [304] further configured to transmit, from the PSC service [1100] to the CP monitoring manager [1090], an event acknowledgement message in an event the breach condition associated with the task is determined. 20 16. The system [300] as claimed in claim 15, wherein an instance of the PSC [1100] is configured to create the task if the breach condition associated with the task is determined at the PSC [1100]. 25 17. The system [300] as claimed in claim 11, the system [300] further comprises: • a storage unit [312], configured to store the created task in a database
[3122]; • the transceiver unit [304], configured to transmit a success response from the PSC service [1100] to the CP monitoring manager [1090]; 39 • the execution unit [310] further configured to trigger the task based on the task schedule; and • the transceiver unit [304] further configured to transmit a notification to the CP monitoring manager [1090] based on the triggering of the task. 5 18. The system [300] as claimed in claim 17, wherein, the CP [1090] is configured to determine a usage of one or more resources on receiving the notification based on triggering of the task. 19. The system [300] 10 as claimed in claim 11, wherein the scheduling for the task comprises at least a daily scheduling, a weekly scheduling and a monthly scheduling. 20. The system as claimed in claim 17, wherein a frequency of the notification is 15 configurable at run time of the task.