WO2025062434A1

WO2025062434A1 - Method and system for optimising operations of platform scheduler service

Info

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

Abstract

The present disclosure relates to a method and a system for optimising operations of platform scheduler (PS) service [1100] The disclosure encompasses receiving, at an operation and management (OAM) interface [304], a request from a first PS instance [312], related to performing registration/ deregistration of the first PS instance [312] with an OAM server [308]; detecting, at the OAM interface [304], a success status based on performing the registration/ deregistration of the first PS instance [312] with the OAM server [308]; and broadcasting at the OAM interface [304], to one or more other PS service instances [314], a broadcast notification based on the success status.

Description

METHOD AND SYSTEM FOR OPTIMISING OPERATIONS OF PLATFORM SCHEDULER SERVICE

FIELD OF THE DISCLOSURE

[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to optimising operations of platform scheduler service.

BACKGROUND OF THE DISCLOSURE

[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include 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 an admissions of prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on antilog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionised wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] In the wireless communication systems, there is a need for efficient resource allocation and management of different kinds of jobs for delivering high quality services. The jobs may refer to tasks which may involve simple processing task and complex workflow management. The tasks may be such as mobility management, network optimization, radio resource management, Fault management, performance management, etc. [0005] Platform scheduler (PS) microservice (alternatively referred to as platform schedulers and cron jobs (PS) microservice or service) acts as a centralised platform which helps to create and schedule jobs on behalf of other micro services. The PS microservice may be a service or a component responsible for managing and coordinating the execution of various jobs across a distributed computing environment. It should be noted that effective scheduling of the jobs is essential for optimum utilisation of resources, ensuring timely completion of the tasks, enabling automation of the repetitive tasks, reducing manual efforts and human errors. Further, the centralised platform would also enable dynamic scalability to enable adapting to the changing workloads. In the current existing solutions, individual PS microservice instances are not controlled and coordinated by centralised services, and are prone to dysfunction due to becoming down, thereby making such services unavailable during the downtime of the servers/instances. Further, it may be noted that due to low availability and increased downtime, the overall throughput of the PS microservice gets affected leading to lower performance throughput during its downtime.

[0006] Thus, there exists a need to provide a solution to achieve High Availability of PS service instances for better performance throughput.

OBJECTS OF THE DISCLOSURE

[0007] This section is provided to introduce certain objects 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 and drawbacks of the prior arts as described hereinabove.

[0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0009] It is an object of the present disclosure to provide a system and a method for ensuring seamless interaction between Platform Scheduler (PS) microservice instances and Operation and Management (0AM) microservice. [0010] It is another object of the present disclosure fault tolerance to achieve High Availability of PS service instances it interacts with operation and management (0AM) microservice interface.

[0011] It is yet another object of the present disclosure solving the problem of downtime and nonavailability for PS service to handle the request.

[0012] It is yet another object of the present disclosure to enable 0AM to consolidate FCAPS information of PS microservices and send it to Element Management Service (EMS) for operational purposes.

SUMMARY OF THE DISCLOSURE

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

[0014] An aspect of the present disclosure may relate to a method for optimising operations of platform scheduler (PS) service. The method comprises receiving, by a transceiver unit at an operation and management (0AM) interface, a request from at least a first PS instance. The request relates to performing one of: a registration and a deregistration of the at least a first PS instance with an 0AM server. The method further comprises detecting, by a processing unit at the 0AM interface, a success status. The success status is based on performing one of: a registration and a deregistration of the at least a first PS instance with the 0AM server. The method further comprises broadcasting, by the processing unit at the 0AM interface, to one or more other PS service instances connected with the 0AM server, a broadcast notification based on the success status.

[0015] In an exemplary aspect of the present disclosure, the one or more other PS service instances connected with the 0AM server are active service instances.

[0016] In an exemplary aspect of the present disclosure, the method comprises detecting, by the processing unit at the 0AM interface, the success status, comprises detecting, by the processing unit, a successful registration of the at least the first PS instance with the 0AM server in an event the received request is for performing the registration of the at least a first PS instance with the 0AM server. [0017] In an exemplary aspect of the present disclosure, the method comprises detecting, by the processing unit at the 0AM interface, the success status, comprises detecting, by the processing unit, a successful deregistration of the at least the first PS instance with the 0AM server in an event the received request is for performing the deregistration of the at least a first PS instance with the 0AM server.

[0018] In an exemplary aspect of the present disclosure, the broadcast notification is associated with providing registration details of the at least the first PS instance to the one or more other PS service instances, wherein the one or more other PS service instances are subscribed instances.

[0019] In an exemplary aspect of the present disclosure, the broadcast notification is associated with providing deregistration details of the at least the first PS instance to the one or more other PS service instances, wherein the one or more other PS service instances are subscribed instances.

[0020] In an exemplary aspect of the present disclosure, the request related to performing the deregistration of the at least the first PS instance with the 0AM server, is received in an event of an occurrence of a failure trigger at the at least the first PS instance.

[0021] In an exemplary aspect of the present disclosure, the request related to performing the registration of the at least the first PS instance with the 0AM server, is received in an event of an occurrence of a restore trigger at the at least the first PS instance.

[0022] In an exemplary aspect of the present disclosure, in an event of failure of one or more PS instances, the method further comprises managing, by one or more PS instances, wherein the one or more PS instance is healthy and registered PS instance at the 0AM among the one or more other PS service instances, a set of tasks of the one or more failed PS instances.

[0023] In an exemplary aspect of the present disclosure, the 0AM interface [304] is a PS OA interface.

[0024] Another aspect of the present disclosure may relate to a system for optimising operations of platform scheduler (PS) service. The system comprises an operation and management (0AM) interface. The 0AM interface further comprises a transceiver unit configured to receive a request from at least a first PS instance, related to performing one of: a registration and a deregistration of the at least a first PS instance with an 0AM server. The 0AM interface further comprises a processing unit configured to detect a success status, wherein the success status is based on performing one of: a registration and a deregistration of the at least a first PS instance with the OAM server. The processing unit of the 0AM interface is further configured to broadcast, to one or more other PS service instances connected with the OAM server, a broadcast notification based on the success status.

[0025] Another aspect of the present disclosure may relate to a non-transitory computer-readable storage medium storing instruction for optimising operations of platform scheduler (PS) 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 request from at least a first PS instance, related to performing one of a registration and a deregistration of the at least a first PS instance with an OAM server. Further, the executable code, when executed, causes a processing unit to detect a success status, wherein the success status is based on performing one of a registration and a deregistration of the at least a first PS instance with the OAM server. Further, the executable code, when executed, causes the processing unit to broadcast, to one or more other PS service instances connected with the OAM server, a broadcast notification based on the success status.

DESCRIPTION OF DRAWINGS

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

[0027] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture/ platform.

[0028] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. [0029] FIG. 3 illustrates an exemplary block diagram of a system for optimising operations of platform scheduler (PS) service, in accordance with exemplary implementations of the present disclosure.

[0030] FIG. 4 illustrates an exemplary method flow diagram for optimising operations of platform scheduler (PS) service, in accordance with the exemplary embodiments of the present disclosure.

[0031] FIG. 5 illustrates an exemplary block diagram of a system architecture [500] for optimising operations of platform scheduler (PS) service, in accordance with exemplary embodiments of the present disclosure.

[0032] The foregoing shall be more apparent from the following more detailed description of the disclosure.

DETAILED DESCRIPTION

[0033] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practised without these specific 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 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.

[0034] The ensuing description provides exemplary embodiments only, and is not 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 disclosure as set forth. [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 practised without these 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.

[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 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 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 known to those of ordinary skill in the art. Furthermore, to the extent that the terms “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.

[0038] 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 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 type of integrated circuits, etc. The processor may perform signal coding data 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. [0039] All modules, units, components used herein, unless explicitly excluded herein, may be software 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 circuits (FPGA), any other type of integrated circuits, etc.

[0040] 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 and/or connected with the system.

[0041] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0042] 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, managing design or deployment design, managing instantiation of network node(s)/ service(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 system may comprise one or more components of the MANO architecture [100], The MANO architecture [100] is used to auto-instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform.

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

[0044] 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 on 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 communication network (such as a 5G network), sequence for execution of processes Pl 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 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.

[0045] 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 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 requires changes during the run time. The central logging manager [1068] is responsible for keeping the logs of every service. The logs are generated by the MANO architecture [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.

[0046] The platforms core services module [108] further comprises NFV infrastructure monitoring manager [1082]; an assure manager [1084]; a performance manager [1086]; a policy execution engine (PEGN) [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 (NPDA) [1096]; a platform NoSQL DB [1098]; a platform schedulers and cron jobs (PSC/PS) [1100]; a VNF backup & upgrade manager [1102]; a micro service auditor [1104]; and a platform operations, administration and maintenance manager (0AM) [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 is generating. The performance manager [1086] is responsible for manging the performance counters. The policy execution engine (PEGN) [1088] is responsible for all the managing the policies. The capacity monitoring manager (CMM) [1090] is responsible for sending the request to the PEGN [1088], The release management (mgmt.) repository (RMR) [1092] is responsible for managing the releases and the images of all the vendor network node. The configuration manager & (GCT) [1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps in deciding the priority of using the network resources. It is further noted that the policy execution engine (PEGN) [1088], the configuration manager & (GCT) [1094] and the (NPDA) [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 (PSC/PS) [1100] schedules the task such as but not limited to triggering of an event, traverse 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] using the network resources then the micro service auditor [1104] audits and informs the same so that resources can be released for services running in the MANO architecture [100], thereby assuring the services only run on the MANO architecture [100], The platform operations, administration and maintenance manager (0AM) [1106] is used for managing between instances that are spawned.

[0047] 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 gateway [1122] is responsible for handling the external services (to the MANO architecture [100]) that requires 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. 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 service going to/incoming from the MANO architecture [100], [0048] The present disclosure can be implemented on a computing device [200] as shown in FIG. 2. The computing device [200] implements the present disclosure in accordance with the MANO architecture/ platform [100] (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 device [200] may also implement a method [400] (as shown in FIG. 4) for optimising operations of platform scheduler (PS) service [1100] (as shown in FIG. 3) utilising a system [300] (as shown in FIG. 3). In another implementation, the computing device [200] may also implement the method [400] for optimising operations of platform scheduler (PS) service [1100] utilising a system [500] (as shown in FIG. 5). In another implementation, the computing device [200] itself implements the method [400] for optimising operations of platform scheduler (PS) service [1100] in a communication network using one or more units configured within the computing device [200], wherein said one or more units can implement the features as disclosed in the present disclosure.

[0049] Referring to Fig. 2, the computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a processor [204] coupled with bus [202] for processing information. The processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] 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 special-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],

[0050] 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 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 information and command selections to the processor [204], and for controlling 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.

[0051] The computing device [200] may implement the techniques described herein using customised 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 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 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.

[0052] The computing device [200] also may include a communication interface [218] coupled to the bus [202], The communication interface [218] provides a two-way 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 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 various types of information.

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

[0054] Further, 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 implement the features of the present disclosure.

[0055] Referring to FIG. 3, an exemplary block diagram of the system [300] for optimising operations of platform scheduler (PS) 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 Operation and Management (0AM) interface [304] comprising at least one transceiver unit [306], at least one processing unit [310] and at least one database [316], The system is connected to at least one Operation and Management (0AM) server [308] and at least one platform scheduler (PS) service [1100] in a bilateral communication manner. The PS service [1100] further comprises at least a first PS instance [312] and one or more other PS service instances (or PS instances) [314], 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 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.

[0056] The system [300] is configured for optimising operations of the platform scheduler (PS) service [1100], with the help of the interconnection between the components/units of the system [300], The optimising here refers to improving the operations of the PS service [1100] through improved resource allocation and task scheduling for different network functions. The optimization ensures efficient management of network resources by way of automating the network functions in order to meet varying network traffic needs. The network resources may include processors, network links, memories etc.

[0057] The transceiver unit [306] is configured to receive a request from at least a first PS instance [312], related to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308], The at least a first PS instance [312] refers to a current PS instance which is first encountered by the OAM interface [304] for registration/ deregistration of the at least a first PS instance [312] so as to allow the OAM server [308] to coordinate and control one or more other PS instances [314] based upon the registration/ deregistration of the at least a first PS instance [312], The registration refers to the adding the at least a first instance [312] to manage network resources for the network functions. Thus, the PS instances (such as the at least a first PS instance [312] in the instant case) configure the details of the OAM server [308] and get registered with them so that they can act as a controller and coordinator to achieve high availability (HA). While the deregistration refers to removal of an existing PS instance (such as the at least a first PS instance [312] in the instant case) when it is no longer required.

[0058] In an exemplary aspect, registration involves addition of PS instance [312] details, in a database [316] associated with OAM server [308],

[0059] In an exemplary aspect, deregistration involves removal or changing status of PS instance [312] details, from the database [316], associated with OAM server [308],

[0060] In an exemplary aspect, the OAM interface [304] is at the OAM server [308], or at the PS instance [312] or both.

[0061] In an exemplary aspect, the OAM interface [304] is a PS OA interface.

[0062] Upon the receipt of the request, the processing unit [310] detects a success status. The success status is based on performing one of a registration and a deregistration of the at least a first PS instance [312] with the OAM server [308], The success status here refers to the completion of the process of registration or deregistration of the instance for which the request was received. Thereafter, the processing unit [310] broadcasts, to one or more other PS service instances [314] connected with the OAM server [308], a broadcast notification based on the success status. The broadcast notification refers to alert or update to the one or more other PS instances [314] like changes, resource updates, details of registered/unregistered instances etc.

[0063] In an exemplary aspect of the present disclosure, the one or more other PS service instances [314] connected with the OAM server [308] are active service instances. The active instances are those registered instances that are currently operational and used for performance of the functions of the PS services. As would be understood, there may be various instances of the PS services which may be responsible for its functioning. Some instances of PS services may be used for acting as a backup and some instances may be used for actively performing such services such as scheduling jobs for managing and allocating network resources.

[0064] In an exemplary aspect of the present disclosure, the broadcast notification is associated with providing registration details of the at least the first PS instance [312] to the one or more other PS service instances [314], The one or more other PS service instances [314] are subscribed instances. The subscribed PS instances [314] are those which are registered to receive specific notifications (such as broadcast notification in the instant case) from the 0AM server [308], The subscribed instances may not always be active, but they are registered to respond in certain situations such as but not limited to reconfigurations, network resource changes etc. It is further important to note that the broadcast notification is associated with providing deregistration details of the at least the first PS instance [312] to the one or more other PS service instances [314], The one or more other PS service instances [314] are subscribed instances in case of deregistration details also.

[0065] In an exemplary aspect, the registration details may include such as but not limited only to IP address, port, uniform resource identifier (URI), instance identifier, status etc.

[0066] In an exemplary aspect, deregistration details may include such as but not limited only to IP address, port, URI, instance identifier, status etc.

[0067] In an exemplary aspect, the broadcast notification may include such as but not limited only to IP address, port, URI, instance identifier, status etc.

[0068] In an exemplary aspect of the present disclosure, the request related to performing the deregistration of the at least a first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a failure trigger at the at least the first PS instance [312], The failure trigger refers to an automated mechanism that gets activated when the first PS instance [312] experiences an unexpected event, such as a system error or resource failure or network congestion. The failure trigger prompts failover procedures of the MANO architecture [100], such as reallocating task to other active PS instance or alerting the 0AM server [308] to take corrective action so that continuity and integrity of the network components can be ensured. It is further important to note that the request related to performing the registration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a restore trigger at the at least the first PS instance [312], The restore trigger refers to an automated mechanism that gets activated when the first PS instance [312] recovers after a downtime or upgrade in the network resources. The restore trigger initiates actions such as reassigning tasks, synchronising of network functions etc.

[0069] In an exemplary aspect of the present disclosure, in an event of failure of one or more PS service instances, one or more PS instances, wherein the one or more PS instance is healthy and registered PS instance at the 0AM that is, active and registered instances among the one or more other PS service instances [314], manage a set of tasks of the one or more malfunctioning PS instances. The one or more malfunctioning PS instances in such cases would be those instances of the PS service [1100] which are not able to function properly due to the downtime. In case of the event of failure of the one or more PS service instances, then the instance of the PS services [1100] which are healthy, i.e., the one or more healthy instances would take up the functions of the PS service and would be responsible for handling the requests and loads thereby reducing chances of any failure or any downtime of the PS service.

[0070] In an exemplary aspect, the 0AM interface [304] may also be used to transfer fault, configuration, accounting, performance and security (FCAP) from PS instances [312] to 0AM server [308], 0AM server [308] uses the fault & alarm data from FCAP to define which instances are healthy.

[0071] In an exemplary aspect, 0AM server [308] may also use FCAP to determine whether the first PS instance [312] has failed and sends the deregistration request to the first PS instance [312] and changing the status of other PS instance [312] to “active”.

[0072] Referring to FIG. 4, an exemplary method flow diagram [400] for optimising operations of platform scheduler (PS) service [1100], in accordance with exemplary implementations of the present disclosure is shown. The optimising here refers to improving the operations of the PS service [1100] through improved resource allocation and task scheduling for different network functions. The optimization ensures efficient management of network resources by way of automating the processes of the network functions in order to meet varying network traffic needs. The network resources may include processors, network links, memories etc., based on the optimization. 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 [500] (as shown in FIG. 5). Further, in an implementation, the system [300] may be present in a server device to 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], [0073] At step [404], the method [400] comprises receiving, by a transceiver unit [306] at an operation and management (0AM) interface [304], a request from at least a first PS instance [312], The request relates to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308], The at least a first PS instance [312] refers to a current PS instance which is first encountered by the 0AM interface [304] for registration/ deregistration of the at least a first PS instance [312] so as to allow the 0AM server [308] to coordinate and control one or more other PS instances [314] based upon the registration/ deregistration of the at least a first PS instance [312], The registration refers to the adding the at least a first instance [312] to manage network resources for the network functions. Thus, the PS instances (such as the at least a first PS instance [312] in the instant case) configure the details of the 0AM server [308] and get registered with them so that they can act as a controller and coordinator to achieve high availability (HA). While the deregistration refers to removal of an existing PS instance (such as the at least a first PS instance [312] in the instant case) when it is no longer required.

[0074] In an exemplary aspect, registration involves addition of PS instance [312] details, in a database [316] associated with 0AM server [308],

[0075] In an exemplary aspect, deregistration involves removal or changing status of PS instance [312] details, from the database [316], associated with 0AM server [308],

[0076] In an exemplary aspect, the 0AM interface [304] is a PS OA interface.

[0077] At step [406], the method [400] comprises detecting, by a processing unit [310] at the 0AM interface [304], a success status. The success status is based on performing one of: a registration and a deregistration of the at least a first PS instance [312] with the 0AM server [308], The success status here refers to the completion of the process of registration or deregistration of the instance for which the request was received.

[0078] In an exemplary aspect of the present disclosure, the detecting, by the processing unit [310] at the 0AM interface [304], the success status, comprises: detecting, by the processing unit [310], a successful registration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the registration of the at least a first PS instance [312] with the 0AM server [308], [0079] In an exemplary aspect of the present disclosure, the detecting, by the processing unit [310] at the 0AM interface [304], the success status, comprises: detecting, by the processing unit [310], a successful deregistration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the deregistration of the at least a first PS instance [312] with the 0AM server [308],

[0080] At step [408], the method [400] further comprises broadcasting, by the processing unit [310] at the 0AM interface [304], to one or more other PS service instances [314] connected with the 0AM server [308], a broadcast notification based on the success status. The broadcast notification refers to alert or update to the one or more other PS instances [314] like changes, resource updates, details of registered/unregistered instances etc.

[0081] In an exemplary aspect of the present disclosure, the broadcast notification is associated with providing registration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances. The subscribed PS instances [314] are those which are registered to receive specific notifications (such as broadcast notification in the instant case) from the 0AM server [308], The subscribed instances may not always be active, but they are registered to respond in certain situations such as but not limited to reconfigurations, network resource changes etc.

[0082] In an exemplary aspect of the present disclosure, the broadcast notification is associated with providing deregistration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances.

[0083] In an exemplary aspect of the present disclosure, the request related to performing the deregistration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a failure trigger at the at least the first PS instance [312], The failure trigger refers to an automated mechanism that gets activated when the at a first PS instance [312] experiences an unexpected event, such as a system error or resource failure or network congestion. The failure trigger prompts failover procedures of the MANO architecture [100], such as reallocating tasks to other active PS instance or alerting the 0AM server [308] to take corrective action so that continuity and integrity of the network components can be ensured. [0084] In an exemplary aspect of the present disclosure, the request related to performing the registration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a restore trigger at the at least the first PS instance [312], The restore trigger refers to an automated mechanism that gets activated when the first PS instance [312] recovers after a downtime or upgrade in the network resources. The restore trigger initiates actions such as reassigning tasks, synchronising of network functions etc.

[0085] In an exemplary aspect of the present disclosure, the method [400], in an event of failure of one or more PS instances, further comprises managing, by one or more PS instances, wherein the one or more PS instance is healthy and registered PS instance at the 0AM among the one or more other PS service instances [314], a set of tasks of the one or more failed PS instances.

[0086] Thereafter, the method [400] terminates at step [410],

[0087] Referring to FIG. 5, another exemplary block diagram of a system architecture [500] for optimising operations of platform scheduler (PS) service [1100] (as shown in FIG.3) is shown, in accordance with the exemplary embodiments of the present disclosure. The system [500] comprises an event routing manager (ERM) [502]; a graphical user (GU) interface [504]; a command line (CL) interface [506]; an edge/ element load balancer (EDGE-LB/ ELB) [508]; a cron and schedulers manager unit [510] (such as PS service); an elastic database (ES)/ (ES-DB) [512] having at least one elastic database client (ES-client) / (ES-DB client) [5122]; and a virtual network function (VNF) manager [514], The VNF manager [514] further manages various virtual machines (VM). In an implementation of the present disclosure, the cron and schedulers manager unit [510] and the ES [512] along with the ES-DB client [5122] are implemented in a platform schedulers and cron jobs (PSC/PS) [1100] (as shown in FIG. 1) of the MANO architecture [100] (as shown in FIG. 1) to perform the functions that appertain to the platform schedulers and cron jobs (PSC/PS) [1100], In another implementation of the present disclosure, the cron and schedulers manager unit [510] itself performs the functions that appertain to the platform schedulers and cron jobs (PSC/PS) [1100], The ERM [502] is used to send the requests between publisher microservice to subscriber microservice. The ELB [508] is used to send the requests between the active instances of one microservice to another microservice. The cron and schedulers manager unit [510] is a process scheduler that allows one to execute commands, scripts, and programs following specified schedules via input given through either the graphical user (GU) interface [504] or the CL interface [506], The cron and schedulers manager unit [510] carries out the following functions: 1. Cron Management [510a] - It is used to manage all the active and inactive crons created at the platform scheduler (or PS) service [1100],

2. Task Management [510b] - It is used to manage all the active and inactive tasks created at the PS service [1100],

3. FCAP Management [510c] - A Fault, Configuration, Accounting, Performance and Security (FCAP) management [510c] is done for all the counters and alarms created at the cron and schedulers manager unit [510],

4. Event Handling [5 lOd] - As the name suggests, it is performed by managing all the events between microservices.

5. High Availability (HA) and Fault Tolerance [510e] - The PSC handles all the requests if one running instance goes down, then another active instance will complete that request.

6. Data Modelling Framework [5 lOf - It is used to manage and check incoming and outgoing format data at PSC end. The Data Modelling Framework [51 Of] governs the structure and format of incoming and outgoing data so as to maintain consistency across all microservices when exchanging data. For example, when data is fetched from the Elasticsearch (ES) database (ES - DB) client [5122], it is transformed into the required format by this framework before being sent to the requesting microservice.

[0088] The ES [512] manages the scheduling and execution of events, that is, tasks that run according to a schedule. The ES [512] keeps the task in the stack data structure based upon the execution-priority of the task. The ES [512] interacts with the cron and schedulers manager unit [510] via the ES-DB client [5122], The VNF manager [514] is a key component of the network functions virtualization (NFV) management and orchestration (MANO) architectural framework (as shown in FIG.l). The NFV defines standards for compute, storage, and networking resources that can be used to build virtualized network functions. The VNF manager [514] works in tandem with the NFV to help standardise the functions of virtual 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 medium storing instruction for optimising operations of platform scheduler (PS) service [1100], the storage medium comprising executable code which, when executed by one or more units of a system [300], causes a transceiver unit [306] to receive a request from at least a first PS instance [312], related to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308], Further, the executable code which, when executed, causes a processing unit [310] to detect a success status, wherein the success status is based on performing one of: a registration and a deregistration of the at least a first PS instance [312] with the OAM server [308], Further, the executable code which, when executed, causes the processing unit [310] to broadcast, to one or more other PS service instances [314] connected with the OAM server [308], a broadcast notification based on the success status.

[0090] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be 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 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 advanced for ensuring seamless interaction between Platform Scheduler (PS) microservice instances and operation and management (OAM) microservice. The present disclosure provides a solution to achieve High Availability of PS service instances that interacts with operation and management (OAM) microservice interface. Further, the present disclosure solves the problem of downtime and non-availability for PS service to handle the request. The OAM microservice consolidates FCAPS information of PS micro services and sends it to Element Management Service (EMS) for Operational Purpose.

[0092] While considerable emphasis has been placed herein on the disclosed 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 and non-limiting.

Claims

We Claim:

1. A method [400] for optimising operations of platform scheduler (PS) service [1100], the method [400] comprising:

- receiving, by a transceiver unit [306] at an operation and management (0AM) interface [304], a request from at least a first PS instance [312], related to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308];

- detecting, by a processing unit [310] at the 0AM interface [304], a success status, wherein the success status is based on performing one of: a registration and a deregistration of the at least a first PS instance [312] with the 0AM server [308]; and

- broadcasting, by the processing unit [310] at the 0AM interface [304], to one or more other PS service instances [314] connected with the 0AM server [308], a broadcast notification based on the success status.

2. The method [400] as claimed in claim 1, wherein the one or more other PS service instances [314] connected with the 0AM server [308] are active service instances.

3. The method [400] as claimed in claim 1 , wherein the detecting, by the processing unit [310] at the 0AM interface [304], the success status, comprises: detecting, by the processing unit [310], a successful registration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the registration of the at least a first PS instance [312] with the 0AM server [308],

4. The method [400] as claimed in claim 1 , wherein the detecting, by the processing unit [310] at the 0AM interface [304], the success status, comprises: detecting, by the processing unit [310], a successful deregistration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the deregistration of the at least a first PS instance [312] with the 0AM server [308],

5. The method [400] as claimed in claim 1, wherein the broadcast notification is associated with providing registration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances.

6. The method [400] as claimed in claim 1, wherein the broadcast notification is associated with providing deregistration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances.

7. The method [400] as claimed in claim 1, wherein the request related to performing the deregistration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a failure trigger at the at least the first PS instance [312],

8. The method [400] as claimed in claim 1, wherein the request related to performing the registration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a restore trigger at the at least the first PS instance [312],

9. The method [400] as claimed in claim 7, the method [400], in an event of failure of one or more PS instances, further comprising: managing, by one or more PS instances, wherein the one or more PS instance is healthy and registered PS instance at the 0AM among the one or more other PS service instances [314], a set of tasks of the one or more failed PS instances.

10. The method [400] as claimed in claim 1, wherein the 0AM interface [304] is a PS OA interface.

11. A system [300] for optimising operations of platform scheduler (PS) service [1100], the system [300] comprising an operation and management (0AM) interface [304], the 0AM interface [304] further comprising:

- a transceiver unit [306] configured to receive a request from at least a first PS instance [312], related to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308]; and

- a processing unit [310] configured to: o detect a success status, wherein the success status is based on performing one of: a registration and a deregistration of the at least a first PS instance [312] with the 0AM server [308]; and o broadcast, to one or more other PS service instances [314] connected with the 0AM server [308], a broadcast notification based on the success status.

12. The system [300] as claimed in claim 11, wherein the one or more other PS service instances [314] connected with the 0AM server [308] are active service instances.

13. The system [300] as claimed in claim 11, wherein the processing unit [310] is configured to detect the success status, based on detecting a successful registration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the registration of the at least a first PS instance [312] with the 0AM server [308],

14. The system [300] as claimed in claim 11, wherein the processing unit [310] is configured to detect the success status, based on detecting a successful deregistration of the at least the first PS instance [312] with the 0AM server [308] in an event the received request is for performing the deregistration of the at least a first PS instance [312] with the 0AM server [308],

15. The system [300] as claimed in claim 11, wherein the broadcast notification is associated with providing registration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances.

16. The system [300] as claimed in claim 11, wherein the broadcast notification is associated with providing deregistration details of the at least the first PS instance [312] to the one or more other PS service instances [314], wherein the one or more other PS service instances [314] are subscribed instances.

17. The system [300] as claimed in claim 11, wherein the request related to performing the deregistration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a failure trigger at the at least the first PS instance [312],

18. The system [300] as claimed in claim 11, wherein the request related to performing the registration of the at least the first PS instance [312] with the 0AM server [308], is received in an event of an occurrence of a restore trigger at the at least the first PS instance [312],

19. The system [300] as claimed in claim 17, wherein in an event of failure of one or more PS instances, one or more PS instances, wherein the one or more PS instance is healthy and registered PS instance at the 0AM among the one or more other PS service instances [314], manage a set of tasks of the one or more failed PS instances.

20. The system as claimed in claim 11, the 0AM interface [304] is a PS OA interface.

21. A non-transitory computer-readable storage medium storing instruction for optimising operations of platform scheduler (PS) service [1100], the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [306] to: receive a request from at least a first PS instance [312], related to performing one of: a registration and a deregistration of the at least a first PS instance [312] with an 0AM server [308]; and a processing unit [310] to: detect a success status, wherein the success status is based on performing one of: a registration and a deregistration of the at least a first PS instance [312] with the 0AM server [308]; and broadcast, to one or more other PS service instances [314] connected with the 0AM server [308], a broadcast notification based on the success status.