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 EXECUTING AT LEAST ONE
SERVICE TASK”
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 EXECUTING AT LEAST ONE SERVICE
TASK
FIELD OF DISCLOSURE
5
[0001] The present disclosure generally relates to a methods and systems of
information technology and network performance management. More particularly,
embodiments of the present disclosure relate to a method and system for executing
at least one service task.
10
BACKGROUND
[0002] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may
15 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 is used only
to enhance the understanding of the reader with respect to the present disclosure,
and not as admissions of the prior art.
20 [0003] The problem at hand revolves around the efficient execution of periodic
tasks essential for the micro service such as Auditor (AU) micro service. These tasks
encompass various types, including API calls, FTP transfers, Events, and Queries.
The challenge lies in orchestrating and managing these tasks seamlessly within the
micro service such as the AU microservice, ensuring they are performed at their
25 designated intervals or at any preferred time. Further, the existing method and
system also fail to optimize task management within the microservices architecture.
[0004] Therefore, in view of limitations to the existing solutions and in order to
overcome these limitations, it is necessary to provide an efficient solution for
30 automatically scheduling a task within the microservice architecture.
3
SUMMARY
[0005] 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.
5 This summary is not intended to identify the key features or the scope of the claimed
subject matter.
[0006] An aspect of the present disclosure may relate to a method for executing at
least one service task. The method includes transmitting, by a transceiver unit from
10 at least one service unit, a request to schedule at least one service task to a core
operation unit. The method further includes receiving, by the transceiver unit at the
at least one service unit from the core operation unit, a response to the request
comprising a status on existence of the at least one service task. The method further
includes receiving, by the transceiver unit, a notification associated with scheduling
15 the at least one service task from the core operation unit upon receiving a negative
status on the existence of the at least one service task. The method further includes
executing, by a processing unit, the at least one scheduled task based on information
received in the notification.
20 [0007] In an exemplary aspect of the present disclosure, the notification comprises
scheduling information associated with the at least one service task.
[0008] In an exemplary aspect of the present disclosure, the existence of the at least
one service task is checked by determining the existence of the at least one service
25 task in a list of service tasks stored at one of the core operation unit, and an elastic
storage (ES).
[0009] In an exemplary aspect of the present disclosure, the negative status
indicates an absence of the existence of the at least one service task in the list of the
30 service tasks stored at the core operation unit and the elastic storage (ES).
4
[0010] In an exemplary aspect of the present disclosure, the at least one service unit
corresponds to an auditor microservice (AU), and the core operation unit
corresponds to a platform schedulers & cron job (PSC).
5 [0011] In an exemplary aspect of the present disclosure, the PSC and the AU
communicates using a PS_AU interface.
[0012] In an exemplary aspect of the present disclosure, the request to schedule the
at least one service task comprises at least a type of service task, time and frequency
10 of execution of the service task, format of the service task, conditions associated
with the service task, resource allocation required for the service task, corrective
actions required for at least one error identified during the execution of the service
task.
15 [0013] In an exemplary aspect of the present disclosure, scheduling the at least one
service task comprises creating, by the core operation unit, the at least one service
task based on at least the type of service task, the frequency of execution of the
service task, the format of the service task, conditions associated with the service
task, resource allocation required for the service task, corrective actions required
20 for at least one error identified during the execution of the service task; and
scheduling, by the core operation unit, the at least one service task after creating the
at least one service task.
[0014] In an exemplary aspect of the present disclosure, the corrective actions are
25 performed, by the processing unit, upon identification of the at least one error
during the execution of the at least one service task.
[0015] Another aspect of the present disclosure may relate to a system for executing
at least one service task. The system comprises a transceiver unit. The transceiver
30 unit is configured to transmit, from at least one service unit, a request to schedule
at least one service task to a core operation unit. The transceiver unit is configured
5
to receive, at the at least one service unit from the core operation unit, a response
to the request comprising a status on existence of the at least one service task. The
transceiver unit is configured to receive a notification associated with scheduling
the at least one service task from the core operation unit upon receiving a negative
5 status on the existence of the at least one service task. The system further comprises
a processing unit connected at least with the transceiver unit. The processing unit is
configured to execute the at least one scheduled task based on information received
in the notification.
10 [0016] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instruction for executing at least one
service task, the instructions include executable code which, when executed by one
or more units of a system, causes a transceiver unit to transmit, from at least one
service unit, a request to schedule at least one service task to a core operation unit.
15 The executable code when executed further causes the transceiver unit to receive,
at the at least one service unit from the core operation unit, a response to the request
comprising a status on existence of the at least one service task. The executable
code when executed further causes the transceiver unit to receive a notification
associated with scheduling the at least one service task from the core operation unit
20 upon receiving a negative status on the existence of the at least one service task.
The executable code when executed further causes a processing unit to execute the
at least one scheduled task based on information received in the notification.
OBJECTS OF THE DISCLOSURE
25
[0017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for
30 executing at least one service task.
6
[0019] Another object of the invention is to provide a system and a method to
receive an HTTP request comprising a request to create and schedule a task.
[0020] Yet another object of the present invention is to provide a solution that
5 enables efficient execution of at least one task.
BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute
10 a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems 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. Also, the embodiments shown in the figures are not to be construed as
15 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
20
[0022] FIG. 1 illustrates an exemplary block diagram representation of
management and orchestration (MANO) architecture/ platform [100].
[0023] FIG. 2 illustrates an exemplary block diagram of a computing device upon
25 which the features of the present disclosure may be implemented, in accordance
with exemplary implementation of the present disclosure.
[0024] FIG. 3 illustrates an exemplary block diagram of a system for executing at
least one service task, in accordance with exemplary implementations of the present
30 disclosure.
7
[0025] FIG. 4 illustrates a method flow diagram for executing at least one service
task, in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 5 illustrates an exemplary block diagram of a system architecture for
5 executing at least one service task, in accordance with exemplary embodiments of
the present disclosure.
[0027] FIG. 6 illustrates a process flow diagram for executing at least one service
task, in accordance with exemplary implementations of the present disclosure.
10
[0028] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
15
[0029] 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
20 details. Several features described hereafter may 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.
25 [0030] 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
30 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
8
[0031] 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
5 specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0032] Also, it is noted that individual embodiments may be described as a process
10 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 may 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
15 included in a figure.
[0033] 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
20 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
25 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.
[0034] As used herein, a “processing unit” or “processor” or “operating processor”
30 includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
9
purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a Digital
Signal Processing (DSP) core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
5 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 or
processing unit is a hardware processor.
10 [0035] As used herein, “a 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
15 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 unit(s) which
20 are required to implement the features of the present disclosure.
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
25 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
functions.
30
10
[0037] 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
communication or interaction of one or more modules or one or more units with
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0038] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
10 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.
15
[0039] 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.
20
[0040] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the abovementioned and other existing problems in this field of technology by providing a
method and system for executing at least one service task.
25
[0041] 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] may be developed for managing telecom cloud infrastructure
30 automatically, managing design or deployment design, managing instantiation of
network node(s)/ service(s) etc. The MANO architecture [100] deploys the network
11
node(s) in the form of Virtual Network Function (VNF) and Cloud-native/
Container Network Function (CNF). The system as provided by the present
disclosure may comprise one or more components of the MANO architecture [100].
The MANO architecture [100] may be used to auto-instantiate the VNFs into the
5 corresponding environment of the present disclosure so that it could help in
onboarding other vendor(s) CNFs and VNFs to the platform.
[0042] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer [102], a network function virtualization (NFV) and software defined
10 network (SDN) design function module [104], a platform foundation services
module [106], a platform core services module [108] and a platform resource
adapters and utilities module [112]. 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.
15
[0043] The NFV and SDN design function module [104] comprises a VNF
lifecycle manager (compute) [1042], a VNF catalog [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
20 lifecycle manager (compute) [1042] may be responsible for deciding on which
server of the communication network, the microservice will be instantiated. The
VNF lifecycle manager (compute) [1042] may manage the overall flow of
incoming/ outgoing requests during interaction with the user. The VNF lifecycle
manager (compute) [1042] may be responsible for determining which sequence to
25 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 P1 and P2 etc. The VNF catalog [1044] stores the metadata of all the
VNFs (also CNFs in some cases). The network services catalogue [1046] stores the
information on the services that need to be run. The network slicing and service
30 chaining manager [1048] manages the slicing (an ordered and connected sequence
of network service/ network functions (NFs) that must be applied to a specific
12
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] may be used for the CNFs
lifecycle management.
5
[0044] The platforms foundation services module [106] comprises a microservices
elastic load balancer [1062], an identity & 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] may be used for
10 maintaining the load balancing of the request for the services. The identity & access
manager [1064] may be used for logging purposes. The command line interface
(CLI) [1066] may be used to provide commands to execute certain processes which
require changes during the run time. The central logging manager [1068] may be
responsible for keeping the logs of every service. These logs are generated by the
15 MANO platform [100]. These logs are used for debugging purposes. The event
routing manager [1070] may be responsible for routing the events i.e., the
application programming interface (API) hits to the corresponding services.
[0045] The platforms core services module [108] comprises an NFV infrastructure
20 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 & GCT
[1094], an NFV platform decision analytics [1096], a platform NoSQL DB [1098];
a platform schedulers and cron jobs [1100], a VNF backup & upgrade manager
25 [1102], a microservice 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] may be responsible for
supervising the alarms the vendor may be generating. The performance manager
30 [1086] may be responsible for managing the performance counters. The policy
execution engine (PEGN) [1088] may be responsible for managing all of the
13
policies. The capacity monitoring manager (CMM) [1090] may be responsible for
sending the request to the PEGN [1090]. The release management (mgmt.)
repository (RMR) [1092] may be responsible for managing the releases and the
images of all of the vendor's network nodes. The configuration manager & (GCT)
5 [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 may be 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] may be a database for storing all the
10 inventory (both physical and logical) as well as the metadata of the VNFs and CNF.
The platform schedulers and cron jobs [1100] schedule the tasks such as but not
limited to triggering of an event, traversing the network graph etc. The VNF backup
& upgrade manager [1102] takes a backup of the images, and binaries of the VNFs
and the CNFs and produces that backup on demand in case of server failure. The
15 microservice auditor [1104] audits the microservices. For e.g., in a hypothetical
case, instances not being instantiated by the MANO architecture [100] may be using
the network resources. In such cases, the microservice auditor [1104] audits and
informs the same so that resources can be released for services running in the
MANO architecture [100]. The audit assures that the services only run on the
20 MANO platform [100]. The platform operations, administration, and maintenance
manager [1106] may be used for newer instances that are spawning.
[0046] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122]; a generic decoder and indexer
25 (XML, CSV, JSON) [1124]; a docker service adaptor [1126]; an OpenStack API
adapter [1128]; and a NFV gateway [1130]. The platform's external API adaptor
and gateway [1122] may be 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
30 in the XML, CSV, JSON format. The docker service adaptor [1126] may be the
interface provided between the telecom cloud and the MANO architecture [100] for
14
communication. The OpenStack API adapter [1128] may be used to connect with
the virtual machines (VMs). The NFV gateway [1130] may be responsible for
providing the path to each service going to/incoming from the MANO architecture
[100].
5
[0047] FIG. 2 illustrates an exemplary block diagram of a 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 for
10 executing at least one service task utilising the system [300]. In another
implementation, the computing device [200] itself implements the method for
executing at least one service task using one or more units configured within the
computing device [200], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
15
[0048] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with the bus [202] for processing information. The
hardware processor [204] may be, for example, a general-purpose microprocessor.
20 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 the execution of the instructions to be
25 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]
30 for storing static information and instructions for the processor [204].
15
[0049] 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),
5 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
10 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.
15
[0050] 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.
20 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
25 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.
30 [0051] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
16
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
5 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
10 various types of information.
[0052] 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
15 transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], a 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.
20
[0053] The computing device [200] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of
computing device [200] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may
25 operate independently or as part of a network and can perform a variety of tasks
such as data storage, retrieval, and analysis. Additionally, computing device [200]
may include peripheral devices, such as monitors, keyboards, and printers, as well
as integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
30
17
[0054] Referring to FIG. 3, an exemplary block diagram of a system [300] for
executing at least one service task, is shown, in accordance with the exemplary
implementations of the present disclosure. The system [300] comprises at least one
transceiver unit [302], at least one service unit [304], at least one core operation
5 unit [306], and at least one processing unit [308]. 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 figures 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
10 the system [300] may comprise any such numbers of said units, as required to
implement the features of the present disclosure. Further, in an implementation, the
system [300] may be present in a user device/ user equipment to implement the
features of the present disclosure. The system [300] may be a part of the user device
or may be independent of but in communication with the user device (may also
15 referred to herein as a UE). In another implementation, the system [300] may reside
in a server or a network entity. In yet another implementation, the system [300] may
reside partly in the server/ network entity and partly in the user device.
[0055] The system [300] is configured for executing at least one service task, with
20 the help of the interconnection between the components/units of the system [300].
[0056] The system [300] comprises a transceiver unit [302]. The transceiver unit
[302] is configured to transmit, from at least one service unit [304], a request to
schedule at least one service task to a core operation unit [306].
25
[0057] The transceiver unit [302] transmits the request to schedule at least one
service task to the core operation unit [306] from at least one service unit [304]. In
an exemplary aspect, the request includes details about the specific service task that
needs to be scheduled.
30
18
[0058] In an exemplary aspect, service tasks or types of service tasks may include
such as but are not limited to application programming interface (API), file transfer
protocol (FTP), event scheduling, query, etc.
5 [0059] In an exemplary aspect, the at least one service unit [304] corresponds to an
auditor microservice (AU), and the core operation unit [306] corresponds to a
platform schedulers & cron job (PSC) [1100].
[0060] In an exemplary aspect, the AU and PSC communicates using a PS_AU
10 interface.
[0061] In an exemplary aspect, the PS_AU interface may include at least one of
hypertext transfer protocol (HTTP) and web-socket based connection.
15 [0062] In an exemplary aspect, the PS_AU interface is configured to facilitate
exchange of information using hypertext transfer protocol (HTTP) rest application
programming interface (API). In an embodiment, the HTTP rest API is used in
conjunction with JSON and/or XML communication media.
20 [0063] In an exemplary aspect, the PS_AU interface is configured to facilitate
exchange of information by establishing a web-socket connection between the
inventory manager unit, and the container orchestrator unit. A web-socket
connection may involve establishing a persistent connectivity between the
inventory manager unit, and the container orchestrator unit. An example of the web25 socket based communication includes, without limitation, a transmission control
protocol (TCP) connection. In such a connection, information, such as operational
status, health, etc. of different components may be exchanged through the interface
using a ping-pong-based communication.
19
[0064] In an exemplary aspect, at least one service unit [304] refers to the auditor
microservice (AU) which is responsible for sending requests and scheduling tasks
such as periodic audits, that need to be performed.
5 [0065] In an exemplary aspect, core operation unit [306] or PSC [1100] receives
the service task request from the at least one service unit [304] and determines
whether the requested service task is already available or not and send an
appropriate response back to the auditor microservice in the form of positive and
negative response indicating availably and non-availability of the at least service
10 task respectively.
[0066] The transceiver unit [302] is further configured to receive, at the at least one
service unit [304] from the core operation unit [306], a response to the request
comprising a status on the existence of the at least one service task.
15
[0067] The transceiver unit [302] receives the response to the previously sent
request from the core operation unit [306] at the at least one service unit [304]. The
response or status response includes the status of existence of the at least one service
task indicating whether the requested service task already exists in the system [300].
20
[0068] In an exemplary aspect, the status may include a positive status indicating
that the requested service task already exists in the system [300]. Similarly, the
status may include a negative status indicating that the request service task does not
exist.
25
[0069] In an exemplary aspect, the existence of the at least one service task is
determined by checking the existence of the at least one service task in a list of
service tasks stored at one of the core operation unit and an elastic storage (also
referred to as elastic search database [512] as shown in FIG. 5).
30
20
[0070] In an exemplary aspect, the list of service tasks or scheduled service tasks
is also stored in the PSC [1100] to eliminate a delay in the scheduling the service
task.
5 [0071] In an exemplary aspect, the existence of the at least one service task is
determined by checking the existence of the at least one service task in a list of
service tasks stored in the PSC [1100].
[0072] In an exemplary aspect, at least one of the core operation unit [306] and the
10 Elastic Storage (or Elastic Search Database) includes a list of service tasks that are
already present or scheduled by the core operation unit [306]. In an event, the core
operation unit [306] fails to search for the already scheduled task then communicate
with the elastic storage (ES) to check existence of the requested service task in this
list or database associated with the ES.
15
[0073] The transceiver unit [302] is further configured to receive a notification
associated with scheduling the at least one service task from the core operation unit
[306] upon receiving a negative status on the existence of the at least one service
task.
20
[0074] Upon receiving the negative status on the existence of the at least one
service task, the transceiver unit [302] receives from the core operation unit [306]
the notification associated with scheduling the at least one service task. In an
exemplary aspect, the notification may include information about the specific
25 service task or requested service task that needs to be scheduled.
[0075] In an exemplary aspect, the negative status indicates an absence of the
existence of the at least one service task in the list of the service tasks stored one of
the core operation unit or at the elastic storage (ES).
30
21
[0076] In an exemplary aspect, the negative status indicates that the requested
service task does not exist in the list of service tasks stored in the core operations
unit and the elastic storage (ES). By sending the negative status, the elastic storage
or the core operation unit prevents service task duplication and ensures that the AU
5 can initiate necessary service tasks without conflicts and errors increasing the
overall efficiency of the system [300].
[0077] In an exemplary aspect, elastic storage (ES) may also send a positive status
to the AU indicating that the initially requested service task is already present in the
10 list of service tasks thereby indicating that there is no need to create new service
tasks.
[0078] In an exemplary aspect, the notification comprises scheduling information
associated with the at least one service task.
15
[0079] In an exemplary aspect, the notification sent from the PSC [1100] to the
auditor microservice (AU) contains scheduling information related to the requested
service task which may include such as but is not limited to the type of task to be
performed (like inventory audit tasks, API check tasks, file transfer protocol (FTP)
20 tasks, event scheduling tasks, etc). Furthermore, the scheduling information may
include the frequency at which a particular task needs to be performed i.e., whether
the service tasks need to run on an hourly, daily, or weekly basis.
[0080] For example, if the service unit [304] requests an API audit service task and
25 receives a negative status along with the notification from the core operation unit
[306], the notification may specify in the scheduled information that the API audit
service task should run every hour, or everyday etc. based on the overall
requirement of the system administrator.
22
[0081] The system [300] further comprises a processing unit [308] connected to at
least the transceiver unit [302]. The processing unit [308] is configured to execute
the at least one scheduled task based on information received in the notification.
5 [0082] Upon receiving the notification which indicates that the specific service task
has been scheduled, the processing unit [308] executes that specific service task
based on information received in the notification. In an exemplary aspect, the
scheduled specific service task may include tasks related to such as but not limited
to application programming interface (API), file transfer protocol (FTP), event
10 scheduling, query etc.
[0083] In an exemplary aspect, the request to schedule the at least one service task
comprises at least a type of service task, frequency of execution of the service task,
format of the service task, conditions associated with the service task, resource
15 allocation required for the service task, corrective actions required for at least one
error identified during the execution of the service task.
[0084] In an exemplary aspect, the request to schedule the at least one service task
comprises at least the type of service task which may include such as but not limited
20 to inventory audit tasks, API check tasks, event scheduling tasks, query tasks, etc.
[0085] Furthermore, the request to schedule the at least one service task may
include the frequency at which a particular service task needs to be performed i.e.,
whether the service tasks are to be run on an hourly, daily, or weekly basis. For
25 example, if the service unit [304] requests an API audit service task and receives a
negative status along with the notification from the core operation unit [306], the
request to schedule the at least one service task may specify in the request that the
API audit service task should run every hour, or everyday, etc. based on the request
of service task.
30
23
[0086] In an exemplary aspect, the request to schedule the at least one service task
may include the format of the service task such as but not limited only to JSON
format, XML format etc, in which the particular service task outcomes need to be
presented.
5
[0087] In an exemplary aspect, the request to schedule the at least one service task
may include conditions associated with the service task and may further include
predefined criteria or conditions set by the system administrator that must be
fulfilled for the execution of the service task.
10
[0088] In an exemplary aspect, the request to schedule the at least one service task
may include the resource allocation required for the particular service task i.e., the
resource requirement of the specific service type. In an exemplary aspect, the
resources may include physical memory, central processing unit (CPUs), and
15 random-access memory (RAM).
[0089] In an exemplary aspect, the request to schedule the at least one service task
may include corrective actions which may include such as but not limited to
deleting the resources; adding the resources; syncing the data, alerting/notifying the
20 system administrator/microservice for the result of the audit, and action required
for at least one identified error during the execution of the service task. In an
exemplary aspect, while receiving the notification from PSC [1100] for triggering
the audit activity, it may include information related to which resource/or in what
scenario the audit should be performed.
25
[0090] In an exemplary aspect, to schedule the at least one service task, the core
operation unit [306] is configured to create the at least one service task based on at
least the type of service task, the frequency of execution of the service task, the
format of the service task, conditions associated with the service task, resource
30 allocation required for the service task, corrective actions required for at least one
24
error identified during the execution of the service task; and schedule the at least
one service task after creating the at least one service task.
[0091] In order to schedule the at least one service task, the core operation unit
5 [306] creates the at least one service task based on the type of service task, the
frequency of execution of the service task, the format of the service task, conditions
associated with the service task, resource allocation required for the service task,
corrective actions required for at least one error identified during the execution of
the service task; and schedule the at least one service task after creating the at least
10 one service task.
[0092] The processing unit [308] is configured to perform corrective actions upon
identification of the at least one error during the execution of the at least one service
task.
15
[0093] Upon identification of the at least one error during the execution of the at
least one service task, the processing unit [308] performs corrective actions which
may include such as but not limited to deleting the resources; adding the resources;
syncing the data, alerting/notifying the system administrator/microservice for the
20 result of the audit, and action required for at least one identified error during the
execution of the service task.
[0094] In an example, the service tasks can be auditing inclusion of a new resource
(API or microservice or Virtualized Network Function (VNF) or Virtualized
25 Network Function Component (VNFC)). An audit task is initially created/defined
at PSC service about possible auditing and sent to PSC. For example, AU wants to
audit the reserved VNF/VNFC resources (in terms of physical memory, CPUs and
RAM) between the inventory maintained at MANO Platform and at the Openstack.
The differences in resource utilization is taken care to keep the resource utilization
30 in sync between the platform and the VIM sites. Here, syncing can be a corrective
action when audit results in a mismatch.
25
[0095] Based on the definition (service task request) provided by the AU
microservice to the PSC, PSC executes the trigger for example every hour and
notify the AU micro service to check the differences in resource utilization. The AU
5 service performs the audit and based on the definition of the audit trigger, it
performs the possible corrective actions. In an example, the possible corrective
actions can be syncing the data (on identifying mismatch) or abandoning the service
or pause the service.
10 [0096] Referring to FIG. 4, an exemplary method flow diagram [400] for executing
at least one service task, in accordance with exemplary implementations of the
present disclosure is shown. In an implementation the method [400] is performed
by the system [300]. Further, in an implementation, the system [300] may be present
in a server device to implement the features of the present disclosure. Also, as
15 shown in FIG. 4, the method [400] starts at step [402].
[0097] At step 404, the method [400] comprises transmitting, by a transceiver unit
[302] from at least one service unit [304], a request to schedule at least one service
task to a core operation unit [306].
20
[0098] The transceiver unit [302] transmits the request to schedule at least one
service task to the core operation unit [306] from at least one service unit [304]. In
an exemplary aspect, the request includes details about the specific service task that
needs to be scheduled.
25
[0099] In an exemplary aspect, service tasks may include tasks related to such as
but not limited only to application programming interface (API), file transfer
protocol (FTP), event scheduling, query, etc.
26
[0100] In an exemplary aspect, the at least one service unit [304] corresponds to an
auditor microservice (AU), and the core operation unit [306] corresponds to a PSC
[1100].
5 [0101] In an exemplary aspect, the AU and PSC [1100] communicates using a
PS_AU interface.
[0102] In an exemplary aspect, the PS_AU interface may include at least one of
hypertext transfer protocol HTTP and web-socket based connection.
10
[0103] In an exemplary aspect, the PS_AU interface is configured to facilitate
exchange of information using hypertext transfer protocol (HTTP) rest application
programming interface (API). In an embodiment, the HTTP rest API is used in
conjunction with JSON and/or XML communication media.
15
[0104] In an exemplary aspect, the PS_AU interface is configured to facilitate
exchange of information by establishing a web-socket connection between the
inventory manager unit, and the container orchestrator unit. A web-socket
connection may involve establishing a persistent connectivity between the
20 inventory manager unit, and the container orchestrator unit. An example of the websocket based communication includes, without limitation, a transmission control
protocol (TCP) connection. In such a connection, information, such as operational
status, health, etc. of different components may be exchanged through the interface
using a ping-pong based communication.
25
[0105] In an exemplary aspect, at least one service unit [304] refers to the auditor
microservice (AU) which is responsible for sending requests for scheduling tasks
such as periodic audits, that need to be performed.
30 [0106] In an exemplary aspect, core operation unit [306] refers to the platform
schedulers & cron Job (PSC) [1100] which on receiving the service task request
27
from the at least one service unit [304] determines whether the requested scheduled
request is already available or not and send an appropriate response back to the
auditor microservice in the form of positive and negative response indicating
availably and non-availability of the at least service task respectively.
5
[0107] At step 406, the method [400] comprises receiving, by the transceiver unit
[302] at the at least one service unit [304] from the core operation unit, a response
to the request comprising a status on existence of the at least one service task.
10 [0108] The transceiver unit [302] receives the response to the previously sent
request from the core operation unit [306] at the at least one service unit [304]. The
response includes the status of existence of the at least one service task indicating
whether the requested service task already exists in the system [300].
15 [0109] In an exemplary aspect, the status may include a positive status indicating
that the requested service task already exists in the system [300]. Similarly, the
status may include a negative status indicating that the request service task does not
exist.
20 [0110] In an exemplary aspect, the existence of the at least one service task is
determined by checking the existence of the at least one service task in a list of
service tasks stored at an elastic storage (ES).
[0111] In an exemplary aspect, the list of service task is also stored in the PSC
25 [1100].
[0112] In an exemplary aspect, the existence of the is the existence of the at least
one service task is determined by checking the existence of the at least one service
task in a list of service tasks stored in the PSC [1100].
30
28
[0113] In an exemplary aspect, the elastic storage (ES) includes the list of service
tasks that are already present. The elastic storage (ES) checks in this list of the
current service task the existence/presence of the requested service task in order to
determine whether the requested service task is present in the list thereby ensuring
5 that there are no duplications and conflicts, increasing the overall efficiency of the
system.
[0114] In an exemplary aspect, the elastic storage (ES) includes the list of service
tasks that are already present. The elastic storage (ES) checks in this list of the
10 current service task the existence/presence of the requested service task in order to
determine whether the requested service task is present in the list thereby ensuring
that there are no duplications and conflicts, increasing the overall efficiency of the
system [300].
15 [0115] At step 408, the method [400] comprises receiving, by the transceiver unit
[302], a notification associated with scheduling the at least one service task from
the core operation unit upon receiving a negative status on the existence of the at
least one service task.
20 [0116] Upon receiving the negative status on the existence of the at least one
service task, the transceiver unit [302] receives from the core operation unit [306]
the notification associated with scheduling the at least one service task. In an
exemplary aspect, the notification may include information about the specific
service task that needs to be scheduled.
25
[0117] In an exemplary aspect, the negative status indicates an absence of the
existence of the at least one service task in the list of the service tasks stored at the
elastic storage (ES) or core operation unit.
30 [0118] In an exemplary aspect, a negative status indicates that the requested service
task does not exist in the list of service tasks stored in the core operations unit i.e.,
29
elastic storage (ES). Furthermore, the elastic storage (ES) indicates to the at least
one service unit [304] i.e., Auditor Microservice (AU) via core operation unit [306]
that the task needs to be created and scheduled. By sending the negative status, the
elastic storage (ES) prevents service task duplication and ensures that the AU can
5 initiate necessary service tasks without conflicts and errors increasing the overall
efficiency of the system [300].
[0119] In an exemplary aspect, the elastic storage (ES) (ES) may also send a
positive status to the AU indicating that the initially requested service task is already
10 present in the list of service tasks thereby indicating that there is no need to create
new service tasks.
[0120] In an exemplary aspect, the notification comprises scheduling information
associated with the at least one service task.
15
[0121] In an exemplary aspect, the notification sent from the PSC [1100] to the
auditor microservice (AU) contains scheduling information related to the requested
service task which may include such as but not limited to details such as the type of
task to be performed, like inventory audit tasks, API check tasks, file transfer
20 protocol (FTP) tasks, event scheduling tasks, etc). Furthermore, the scheduling
information may include the frequency at which a particular task needs to be
performed i.e., whether the service tasks are to be run on an hourly, daily, or weekly
basis.
25 [0122] For example, if the service unit [304] requests an API audit service task and
receives a negative status notification from the core operation unit [306], the
notification may specify in the scheduled information that the API audit service task
should run every hour, or every day etc. based on the overall requirement of the
system administrator.
30
30
[0123] At step 410, the method [400] comprises executing, by a processing unit
[308], the at least one scheduled task based on information received in the
notification.
5 [0124] Upon receiving the notification which indicates that the specific service
task has been scheduled, the processing unit [308] executes that specific service
task based on information received in the notification. In an exemplary aspect, the
scheduled specific service task may include tasks related to such as but not limited
only to application programming interface (API), file transfer protocol (FTP), event
10 scheduling, query, etc.
[0125] In an exemplary aspect, the request to schedule the at least one service task
comprises at least a type of service task, frequency of execution of the service task,
format of the service task, conditions associated with the service task, resource
15 allocation required for the service task, corrective actions required for at least one
error identified during the execution of the service task.
[0126] In an exemplary aspect, the request to schedule the at least one service task
comprises at least a type of service task which may include such as but is not limited
20 only to inventory audit tasks, API check tasks, event scheduling tasks, query tasks,
etc.
[0127] Furthermore, the request to schedule the at least one service task may
include the frequency at which a particular service task needs to be performed i.e.,
25 whether the service task is to be run on an hourly, daily, or weekly basis. For
example, if the service unit [304] requests an API audit service task and receives a
negative status and notification from the core operation unit [306], the request to
schedule the at least one service task may specify in the request that the API audit
service task should run every hour, or everyday, etc. based on the overall
30 requirement of the system administrator.
31
[0128] In an exemplary aspect, the request to schedule the at least one service task
may include the format of the service task may include the data format, such as but
not limited only to JSON format, XML format etc., in which the particular service
task outcomes need to be presented.
5
[0129] In an exemplary aspect, the request to schedule the at least one service task
may include conditions associated with the service task and may further include
predefined criteria or conditions set by the system administrator that must be
fulfilled before the specific service task needs to be performed or executed.
10
[0130] In an exemplary aspect, the request to schedule the at least one service task
may include the resource allocation required for the particular service task i.e., the
resource requirement of the specific service type. In an exemplary aspect, the
resources may include physical memory, central processing unit (CPUs), and
15 random-access memory (RAM).
[0131] In an exemplary aspect, the request to schedule the at least one service task
may include corrective actions which may include such as but not limited to
deleting the resources; adding the resources; syncing the data, alerting/notifying the
20 system administrator/microservice for the result of the audit, and action required
for at least one identified error during the execution of the service task. In an
exemplary aspect, while sending the notification from PSC [1100] for triggering the
audit activity, it may include information related to which resource/or in what
scenario the audit should be performed.
25
[0132] In an exemplary aspect, scheduling the at least one service task comprises
creating, by the core operation unit [306], the at least one service task based on at
least the type of service task, the frequency of execution of the service task, the
format of the service task, conditions associated with the service task, resource
30 allocation required for the service task, corrective actions required for at least one
error identified during the execution of the service task; and scheduling, by the core
32
operation unit, the at least one service task after creating the at least one service
task.
[0133] In order to schedule the at least one service task, the core operation unit
5 [306] creates the at least one service task based on the type of service task, the
frequency of execution of the service task, the format of the service task, conditions
associated with the service task, resource allocation required for the service task,
corrective actions required for at least one error identified during the execution of
the service task; and schedule the at least one service task after creating the at least
10 one service task.
[0134] In an exemplary aspect, the corrective actions are performed, by the
processing unit [308], upon identification of the at least one error during the
execution of the at least one service task.
15
[0135] Upon identification of the at least one error during the execution of the at
least one service task, the processing unit [308] performs corrective actions which
may include deleting the resources; adding the resources; syncing the data,
alerting/notifying the system administrator/microservice for the result of the audit,
20 and action required for at least one identified error during the execution of the
service task.
[0136] Thereafter, at step [412], the method [400] is terminated.
25 [0137] Referring to FIG. 5, another exemplary block diagram of a system
architecture [500] for executing at least one service task (as shown in FIG.3) is
shown, in accordance with the exemplary embodiments of the present disclosure.
The system architecture [500] comprises an event routing manager (ERM) [502]; a
graphical user (GU) interface [504]; a command line (CL) interface [506]; an edge/
30 element load balancer (EDGE-LB/ ELB) [508]; a cron and schedulers manager unit
[510]; an elastic storage/ elastic search database (ES)/ (ES-DB) [512] having at least
33
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
5 client [5122] are implemented in a platform schedulers and cron jobs (PSC) [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)
[1100]. In another implementation of the present disclosure, the cron and schedulers
manager unit [510] itself performs the functions that appertain to the platform
10 schedulers and cron jobs (PSC) [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
15 schedules via input given through either the graphical user (GU) interface [504] or
the CL interface [506].
[0138] The cron and schedulers manager unit [510] carries out the following
functions:
20 1. Cron Management [510a] - It is used to manage all the active and inactive
crons created at the platform scheduler (or PS).
2. Task Management [510b] - It is used to manage all the active and inactive
tasks created at the PS [302].
3. FCAP Management [510c] – A Fault, Configuration, Accounting,
25 Performance and Security (FCAP) management [510c] is done for all the counters
and alarms created at the PS [502].
4. Event Handling [510d] – As the name suggests, it is performed by manging
all the events between microservices.
5. High Availability (HA) and Fault Tolerance [510e] – The PSC handles all
30 the requests if one running instance goes down, then another active instance will
complete that request.
34
6. Data Modelling Framework [510f] – It is used to manage and check
incoming and outgoing format data at PSC end. The Data Modelling Framework
[510f] governs the structure and format of incoming and outgoing data so as to
maintain consistency across all microservices when exchanging data. For example,
5 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.
[0139] The ES [512] manages the scheduling and execution of events, that is, tasks
10 that run according to a schedule. The ES [512] keeps the task in the stack data
structure based on 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
15 FIG.1). 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 standardize the functions of virtual
networking and increase the interoperability of software-defined networking
elements.
20
[0140] Referring to FIG. 6, an exemplary process flow diagram [600] for executing
at least one service task, in accordance with exemplary implementations of the
present disclosure is shown.
25 [0141] At step S1, the process [600] comprises transmitting, from the auditor
microservice [600a] (also referred to herein as service unit [304]), a request for
creating and scheduling service task at the platform scheduler and cron job (PSC)
[1100].
30 [0142] At step S2, the process [600] comprises checking, at the PSC [1100] whether
the requested service task already exists or not.
35
[0143] In an exemplary aspect, PSC [1100] may check the existence of the
requested service task by determining the existence of the at least one service task
in a list of service tasks stored at least one of the PSC (core operation unit [306])
5 and an elastic storage (ES). Thus, the PSC in one embodiment may directly check
the list of service tasks or list of the scheduled service task to check the existence
of the requested service task. In another embodiment, the PSC may communicate
with the elastic storage to check the existence of the requested service task. The
PSC may receive a confirmation from the elastic storage or elastic search database
10 related to the existence of the requested service task. In an exemplary aspect, the
elastic storage (ES) [512] includes the list of service tasks that are already available.
The elastic storage (ES) [512] checks in this list of the current service task the
existence/presence of the requested service task in order to determine whether the
requested service task is already present in the list thereby ensuring that there are
15 no duplications and conflicts, increasing the overall efficiency of the system.
[0144] At step S3, the PSC may determine the existence/presence of the requested
service task from the list stored at the PSC. In an exemplary implementation, the
PSC may receive a confirmation message from the ES about the presence of the
20 requested service task based on the presence of the requested service task in the list
stored at the ES.
[0145] At step S4, the process [600] comprises receiving, at the AU [600a] from
the PSC [1100], a response indicating that the requested service task is present in
25 the PSC [1100] or the ES [512] and hence does not require recreation of the
requested service task. The response may also be referred to as failure response due
to termination of the requested received from the AU.
[0146] At step S5, if the service task is not present in the list stored at one of the
30 PSC [1100] or the ES [512], then the PSC becomes aware of the non-existence of
the requested service task. In an embodiment, the PSC may check the list at its end
36
first and then may communicate with the ES to further confirm the existence of the
requested service task. If the requested service task is not found in the list of
scheduled tasks then the PSC may receive a confirmation from the ES about the
non-existence or absence of the requested service task in the list stored at the ES.
5
[0147] At step S6, the process [600] comprises creating, at the PSC [1100], the
requested service task. Furthermore, the process [600] comprises storing the newly
created service task in the ES [512] In another embodiment, the PSC may store the
scheduled task at one of the PSC database or the ES after creating the requested
10 service task.
[0148] It is to be noted that the steps S3 and S4 illustrates a scenario where the
requested service task is already present either at the PSC or at the ES. Further, the
steps S5 and S6 illustrates another scenario where the requested service task is not
15 present at the PSC or at the ES and therefore the PSC create and store the requested
service task at the PSC database or at the ES.
[0149] At step S7, once the task is already created at the PSC [1100], and stored at
the ES [512] or at the PSC database, the process [600] comprises sending, by the
20 PSC [1100] an acknowledgment back to the AU [600a], notifying that the requested
service task has been successfully created and scheduled.
[0150] At step S8, the process [600] comprises triggering, at the AU [600a] by the
PSC [1100], the scheduled service task (or requested service task) at a scheduled
25 time. In an exemplary aspect, the task is executed based on the trigger at the AU
[600a].
[0151] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for executing at least one service task, the
30 instructions include executable code which, when executed by one or more units of
a system, causes a transceiver unit to transmit, from at least one service unit, a
37
request to schedule at least one service task to a core operation unit. The executable
code when executed further causes the transceiver unit to receive, at the at least one
service unit from the core operation unit, a response to the request comprising a
status on existence of the at least one service task. The executable code when
5 executed further causes the transceiver unit to receive a notification associated with
scheduling the at least one service task from the core operation unit upon receiving
a negative status on the existence of the at least one service task. The executable
code when executed further causes a processing unit to execute the at least one
scheduled task based on information received in the notification.
10
[0152] As is evident from the above, the present disclosure provides a technically
advanced solution for executing at least one service task. The present solution offers
notable technical advantages, firstly, it effectively tackles the challenge of
scheduling tasks within the Microservice Auditor service (AU) micro service,
15 significantly diminishing the overhead associated with development, validation,
integration, and testing processes. This translates to a more streamlined and
efficient workflow. Secondly, it empowers the AU micro service by providing a
centralized platform for creating, updating, and deleting a diverse array of tasks.
This centralized approach simplifies task management, eliminating the need for
20 operations to be performed within individual systems. Lastly, the interface plays a
crucial role in creating tasks that prompt notifications to check the MANO
(Management and Orchestration) infrastructure details. This not only enhances the
monitoring capabilities but also contributes to the overall operational robustness of
the system. In essence, these technical advantages underscore the transformative
25 impact of this solution on task management and operational efficiency within the
microservices architecture.
[0153] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
30 implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
38
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
5 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
[0154] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
10 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.
39
We Claim:
1. A method for executing at least one service task, the method comprising:
transmitting, by a transceiver unit [302] from at least one service unit [304],
5 a request to schedule at least one service task to a core operation unit [306];
receiving, by the transceiver unit [302] at the at least one service unit [304]
from the core operation unit [306], a response to the request comprising a status
on existence of the at least one service task;
receiving, by the transceiver unit [302], a notification associated with
10 scheduling the at least one service task from the core operation unit [306] upon
receiving a negative status on the existence of the at least one service task; and
executing, by a processing unit [308], the at least one scheduled task based
on information received in the notification.
15 2. The method as claimed in claim 1, wherein the notification comprises
scheduling information associated with the at least one service task.
3. The method as claimed in claim 1, wherein the existence of the at least one
service task is checked by determining the existence of the at least one service
20 task in a list of service tasks stored at least one of the core operation unit [306]
and an elastic storage (ES).
4. The method as claimed in claim 3, wherein the negative status indicates an
absence of the existence of the at least one service task in the list of the service
25 tasks stored at least one of the core operation unit [306] and the elastic storage
(ES).
5. The method as claimed in claim 1, wherein the at least one service unit [304]
corresponds to an auditor microservice (AU), and the core operation unit [306]
30 corresponds to a platform scheduler and cron jobs (PSC) [1100].
40
6. The method as claimed in claim 5, wherein the PSC and the AU communicates
using a PS_AU interface.
7. The method as claimed in claim 1, wherein the request to schedule the at least
5 one service task comprises at least a type of service task, time and frequency of
execution of the service task, format of the service task, conditions associated
with the service task, resource allocation required for the service task, corrective
actions required for at least one error identified during the execution of the
service task.
10
8. The method as claimed in claim 7, wherein scheduling the at least one service
task comprises:
creating, by the core operation unit [306], the at least one service task based
on at least the type of service task, the frequency of execution of the service
15 task, the format of the service task, conditions associated with the service task,
resource allocation required for the service task, corrective actions required for
at least one error identified during the execution of the service task; and
scheduling, by the core operation unit [306], the at least one service task
after creating the at least one service task.
20
9. The method as claimed in claim 7, wherein the corrective actions are performed,
by the processing unit [308], upon identification of the at least one error during
the execution of the at least one service task.
25 10. A system for executing at least one service task, the system comprises:
a transceiver unit [302], wherein the transceiver unit [302] is configured to:
transmit, from at least one service unit [304], a request to schedule at least
one service task to a core operation unit [306];
receive, at the at least one service unit from the core operation unit [306], a
30 response to the request comprising a status on existence of the at least one
service task;
41
receive a notification associated with scheduling the at least one service task
from the core operation unit [306] upon receiving a negative status on the
existence of the at least one service task; and
a processing unit [308] connected at least with the transceiver unit [302],
5 the processing unit [308] is configured to:
execute the at least one scheduled task based on information received in the
notification.
11. The system as claimed in claim 10, wherein the notification comprises
10 scheduling information associated with the at least one service task.
12. The system as claimed in claim 10, wherein the existence of the at least one
service task is determined by checking the existence of the at least one service
task in a list of service tasks stored at one of the core operation unit and an
15 elastic storage (ES).
13. The system as claimed in claim 12, wherein the negative status indicates an
absence of the existence of the at least one service task in the list of the service
tasks stored at one of the core operation unit and in the elastic storage (ES).
20
14. The system as claimed in claim 10, wherein the at least one service unit [304]
corresponds to an auditor microservice (AU), and the core operation unit
corresponds to a platform scheduler and cron jobs (PSC) [1100].
25 15. The system as claimed in claim 14, wherein the PSC and the AU communicates
using a PS_AU interface.
16. The system as claimed in claim 10, wherein the request to schedule the at least
one service task comprises at least a type of service task, time and frequency of
30 execution of the service task, format of the service task, conditions associated
with the service task, resource allocation required for the service task, corrective
42
actions required for at least one error identified during the execution of the
service task.
17. The system as claimed in claim 16, wherein to schedule the at least one service
5 task, the core operation unit [306] is configured to:
create the at least one service task based on at least the type of service task,
time and frequency of execution of the service task, the format of the service
task, conditions associated with the service task, resource allocation required
for the service task, corrective actions required for at least one error identified
10 during the execution of the service task; and
schedule the at least one service task after creating the at least one service
task.
18. The system as claimed in claim 16, wherein the processing unit [308] is
15 configured to perform corrective actions upon identification of the at least one
error during the execution of the at least one service task.