1
FORM 2
THE PATENTS ACT, 1970 (39 OF
1970)
&
5 THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
10 “METHOD AND SYSTEM FOR MANAGING NETWORK RESOURCES”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point,
Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
15
20 The following specification particularly describes the invention and the manner in which it is
to be performed.
25
30
2
METHOD AND SYSTEM FOR MANAGING NETWORK RESOURCES
TECHNICAL FIELD
5 [0001] Embodiments of the present disclosure generally relate to network management
systems. More particularly, embodiments of the present disclosure relate to methods and
systems for managing network resources.
BACKGROUND
10
[0002] The following description of the 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 is used only to enhance the understanding of the reader with
15 respect to the present disclosure, and not as admissions of the prior art.
[0003] With rapidly evolving communication technology, a requirement for efficient task
scheduling is crucial for the optimal functioning of microservices, especially with
microservices like Inventory Management (IM). Further, to address the issue, the Platform
20 Scheduler and Cron Jobs (PSC) are introduced to act as a centralized unit for managing and
executing periodic tasks on behalf of a plurality of microservices. The PSC is designed to
handle multiple tasks, such as API calls, FTP transfers, event triggers, and database queries.
The innovation of this system directly addresses the challenge of orchestrating these tasks,
alleviating the overhead on the IM micro service and ensuring seamless, timely execution of
25 essential functions.
[0004] Therefore, there are a number of limitations to the existing solutions and in order
to overcome these and such other limitations of the known solutions it is necessary to provide
an efficient solution for automatically scheduling a task by platform core services to a reserve
30 resource and an unreserved resource associated with the task.
OBJECTS OF THE DISCLOSURE
3
[0005] Some of the objects of the present disclosure, which at least one embodiment
disclosed herein satisfies are listed herein below.
5 [0006] It is an object of the present disclosure to provide a system and a method for
managing network resources.
[0007] Another object of the invention is to provide a system and a method that allows for
the receipt of a http request to create and schedule a task request.
10
[0008] Yet another object of the present invention is to provide a solution that transmits
from the PSC to the IM at least one of a task successfully created and scheduled message to at
least one of the one of one or more reserve resources and the one or more unreserved resources
associated with the task request.
15
SUMMARY
[0009] 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
20 not intended to identify the key features or the scope of the claimed subject matter.
[0010] An aspect of the present disclosure may relate to a method for managing network
resources. The method comprises transmitting, by a transceiver unit at an Inventory Manager
(IM) to a Platform scheduler and cron jobs (PSC), a create task request comprising one or more
25 task parameters. Next, the method comprises receiving, by the transceiver unit, over an
interface, at the Inventory Manager (IM) from the PSC, a notification associated with the create
task request. Next, the method comprises performing, by a performance unit at the IM, the
target action on a set of resources based on the notification, wherein the target action is at least
one of a reserve resources action and an unreserve resources action.
30
[0011] In an exemplary aspect of the present disclosure, post transmitting the create task
request, and prior to receiving the notification over the interface, the method further comprises
4
creating, by a processing unit at the PSC, a task based on the create task request. Further the
method comprises scheduling, by the processing unit at the PSC, the task based on the one or
more task parameters.
5 [0012] In an exemplary aspect of the present disclosure, the method further comprises
reserving, by the processing unit, one or more resources for the scheduled task based on
performing the reserve resources action.
[0013] In an exemplary aspect of the present disclosure, the method further comprises
10 unreserving, by the processing unit, one or more resources for the scheduled task based on
performing the unreserve resources action.
[0014] In an exemplary aspect of the present disclosure, post receiving the notification
over the interface, and prior to performing the target action, the method further comprises
15 identifying, by an identification unit at the IM, one or more resources associated with the create
task request, wherein the one or more resources are at least one of a physical resource and a
virtual resource.
[0015] In an exemplary aspect of the present disclosure, the interface is an PSC_IM
20 interface.
[0016] Another aspect of the present disclosure may relate to a system for managing
network resources. The system comprises a transceiver unit configured to transmit, at an
Inventory Manager (IM), a create task request comprising one or more task parameters to a
25 Platform scheduler and cron jobs (PSC). Further, the transceiver unit is configured to receive,
over an interface, at the IM from the PSC, a notification associated with the create task request.
Further, the system comprises a performance unit connected at least to the transceiver unit,
wherein the performance unit is configured to perform a target action on a set of resources
based on the received notification, wherein the target action is at least one of a reserve resources
30 action and an unreserve resources action.
5
[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for managing network resources, the instructions
comprising executable code which, when executed by one or more units of a system, causes: a
transceiver unit to transmit, at an Inventory Manager (IM), a create task request comprising
5 one or more task parameters to a Platform scheduler and cron jobs (PSC). The executable code
which, when executed by one or more units of a system, causes the transceiver unit to receive,
over an interface, at the IM from the PSC, a notification associated with the create task request.
Further, the executable code which, when executed by one or more units of a system, causes a
performance unit to perform a target action on a set of resources based on the received
10 notification, wherein the target action is at least one of a reserve resources action and an
unreserve resources action.
DESCRIPTION OF THE DRAWINGS
15 [0018] 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. Also, the embodiments shown in the
20 figures are not to be construed as 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.
25
[0019] FIG.1 illustrates an exemplary block diagram of a manifestation and orchestration
(MANO) architecture.
[0020] FIG. 2 illustrates an exemplary block diagram of a computing device upon which
30 the features of the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure.
6
[0021] FIG. 3 illustrates an exemplary block diagram of a system for managing network
resources, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 4 illustrates a method flow diagram for managing network resources in
5 accordance with exemplary implementations of the present disclosure.
[0023] FIG. 5 illustrates an exemplary block diagram of a system architecture for
managing network resources, in accordance with the exemplary implementations of the present
disclosure.
10
[0024] The foregoing shall be more apparent from the following more detailed description
of the disclosure.
DETAILED DESCRIPTION
15
[0025] 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 details. Several features described hereafter may each be used
20 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.
[0026] The ensuing description provides exemplary embodiments only, and is not
25 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.
30
[0027] 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
7
the art that the embodiments may be practiced without these 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.
5 [0028] 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 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
10 could have additional steps not included in a figure.
[0029] 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
15 “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
20 to the term “comprising” as an open transition word—without precluding any additional or
other elements.
[0030] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing
25 instructions. A 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 Processing (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
30 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.
8
[0031] 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
5 the features of the present disclosure. The 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 are required to implement
10 the features of the present disclosure.
[0032] As used herein, “storage unit” or “memory unit” refers to a machine or computerreadable medium including any mechanism for storing information in a form readable by a
computer or similar machine. For example, a computer-readable medium includes read-only
15 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.
20 [0033] 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 refer to a set of rules or protocols that define communication or interaction
of one or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
25
[0034] 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
30 controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field
Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
9
[0035] 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.
5
[0036] As discussed in the background section, the current known solutions have several
shortcomings. The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing a method and a system of managing
network resources. The present disclosure relates to a novel method and for automatically
10 scheduling one or more tasks using Platform Scheduler and Cron Jobs (PSC) microservice. The
present disclosure efficiently manages a plurality of tasks such as API calls, FTP operations,
event triggers, and queries. A key feature is its ability to dynamically reserve and unreserve
resources, both physical and virtual, for task execution. Further, the present disclosure
facilitates dynamic allocation and deallocation of both physical and virtual resources, which
15 further optimizes the overall efficiency of microservices like Inventory Management (IM).
[0037] FIG. 1 illustrates an exemplary block diagram representation of a management and
orchestration (MANO) architecture [100], in accordance with exemplary implementations of
the present disclosure. The MANO architecture [100] is developed for managing telecom cloud
20 infrastructure automatically, managing design or deployment design, managing instantiation
of a network node(s) etc. The MANO architecture [100] deploys the network node(s) in the
form of Virtual Network Function (VNF) and Cloud-native/ Container Network Function
(CNF). The system may comprise one or more components of the MANO architecture. The
MANO architecture [100] is used to auto-instantiate the VNFs into the corresponding
25 environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs
and VNFs to the platform. In an implementation, the system comprises a NFV Platform
Decision Analytics (NPDA) [1096] component.
[0038] As shown in FIG. 1, the MANO architecture [100] comprises a user interface layer
30 [102], 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
10
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.
[0039] The NFV and SDN design function module [104] further comprises a VNF
5 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 network the microservice will be instantiated.
The VNF lifecycle manager (compute) [1042] will manage the overall flow of incoming/
10 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 network (such as a 5G network), sequence for
execution of processes P1 and P2 etc. The VNF catalogue [1044] stores the metadata of all the
VNFs (also CNFs in some cases). The network services catalogue [1046] stores the information
15 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
20 for the CNFs lifecycle management.
[0040] The platforms foundation services module [106] further comprises a microservices
elastic load balancer [1062], an identify and access manager [1064], a command line interface
(CLI) [1066], a central logging manager [1068], and an event routing manager [1070]. The
25 microservices elastic load balancer [1062] is used for maintaining the load balancing of the
request for the services. The identify and access manager [1064] is used for logging purposes.
The command line interface (CLI) [1066] is used to provide commands to execute certain
processes which require changes during the run time. The central logging manager [1068] is
responsible for keeping the logs of every service. These logs are generated by the MANO
30 platform [100]. These logs are used for debugging purposes. The event routing manager [1070]
is responsible for routing the events i.e., the application programming interface (API) hits to
the corresponding services.
11
[0041] 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 [1088], a capacity monitoring manager [1090], a release management
(mgmt.) repository [1092], a configuration manager and GCT [1094], an NFV platform
5 decision analytics [1096], a platform NoSQL DB [1098], a platform schedulers and cron jobs
[1100], a VNF backup and upgrade manager [1102], a micro service auditor [1104], and a
platform operations, administration and maintenance manager [1106]. The NFV infrastructure
monitoring manager [1082] monitors the infrastructure part of the NFs. For e.g., any metrics
such as CPU utilization by the VNF. The assure manager [1084] is responsible for supervising
10 the alarms the vendor is generating. The performance manager [1086] is responsible for
manging the performance counters. The policy execution engine (PEEGN) [1088] is
responsible for all the managing the policies. The capacity monitoring manager (CPM) [1090]
is responsible for sending the request to the PEEGN [1088]. The release management (mgmt.)
repository (RMR) [1092] is responsible for managing the releases and the images of all the
15 vendor network node. The configuration manager and 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 (PEEGN) [1088], the configuration manager and GCT [1094] and the (NPDA) [1096]
work together. The platform NoSQL DB [1098] is a platform database for storing all the
20 inventory (both physical and logical) as well as the metadata of the VNFs and CNF. It may be
noted that the platform NoSQL DB [1098] may be just a narrow implementation of the present
disclosure, and any other kind of structure for the database may be implemented for the
platform database such as relational or non-relational database. The platform schedulers and
cron jobs [1100] schedules the task such as but not limited to triggering of an event, traversing
25 the network graph etc. The VNF backup and 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
30 resources can be released for services running in the MANO architecture [100], thereby
assuring the services only run on the MANO platform [100]. The platform operations,
administration and maintenance manager [1106] is used for newer instances that are spawning.
12
[0042] The platform resource adapters and utilities module [112] further comprises a
platform external API adapter and gateway [1122], a generic decoder and indexer (XML, CSV,
JSON) [1124], a docker service adapter [1126], an API adapter [1128], and a NFV gateway
[1130]. The platform external API adapter and gateway [1122] may be responsible for handling
5 the external services (to the MANO platform [100]) that require the network resources. The
generic decoder and indexer (XML, CSV, JSON) [1124] gets directly the data of the vendor
system in the XML, CSV, JSON format. The docker service adapter [1126] may be the
interface provided between the telecom cloud and the MANO architecture [100] for
communication. The API adapter [1128] may be used to connect with the virtual machines
10 (VMs). The NFV gateway [1130] may be responsible for providing the path to each service
going to/incoming from the MANO architecture [100].
[0043] The docker service adapter (DSA) [1126] is a microservices-based system designed
to deploy and manage Container Network Functions (CNFs) and their components (CNFCs)
15 across Docker nodes. The DSA [1126] offers REST endpoints for key operations, including
uploading container images to a Docker registry, terminating CNFC instances, and creating
Docker volumes and networks. CNFs, which are network functions packaged as containers,
may consist of multiple CNFCs. The DSA [1126] facilitates the deployment, configuration,
and management of these components by interacting with Docker's API, ensuring proper setup
20 and scalability within a containerized environment. This approach provides a modular and
flexible framework for handling network functions in a virtualized network setup.
[0044] FIG. 2 illustrates an exemplary block diagram of a computing device [200] (herein,
also referred to as a computer system [200]) upon which one or more features of the present
25 disclosure may be implemented in accordance with an exemplary implementation of the
present disclosure. 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 (as shown in FIG. 1). In an implementation, the computing device
[200] may also implement a method for managing network resources, utilising a system, or one
30 or more sub-systems, provided in the network. In another implementation, the computing
device [200] itself implements the method for managing network resources, 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.
13
[0045] The computing device [200] may include a bus [202] or other communication
mechanism(s) for communicating information, and a hardware processor [204] coupled with
bus [202] for processing said information. The hardware processor [204] may be, for example,
5 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
10 processor [204]. Such instructions, when stored in a non-transitory storage media accessible to
the processor [204], render the computing device [200] into a special purpose device that is
customized to perform operations according to 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].
15
[0046] 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
20 (OLED) display, etc., for displaying information to a user of the computing device [200]. 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
25 command selections to the processor [204], and for controlling cursor movement on the display
[212]. The cursor controller [216] typically has two degrees of freedom in two axes, a first axis
(e.g., x) and a second axis (e.g., y), that allows the cursor controller [216] to specify positions
in a plane.
30 [0047] 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 device. According to one implementation, the techniques
14
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]. The one or more instructions may be read into the main memory [206] from another
storage medium, such as the storage device [210]. Execution of the one or more sequences of
5 the one or more 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.
10 [0048] The computing device [200] also may include a communication interface [218]
coupled to the bus [202]. The communication interface [218] provides 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
15 connection to a corresponding type of telecommunication line. In 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 different types of
20 information.
[0049] The computing device [200] can send and receive data, including program code,
messages, etc. through the network(s), the network link [220] and the communication interface
[218]. In an example, a server [230] might transmit a requested code for an application program
25 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.
30 [0050] Referring to FIG. 3, an exemplary block diagram of a system [300] for managing
network resources, 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
performance unit [304], at least one identification unit [306], and at least one processing unit
15
[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 the system
5 [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 a user equipment (UE) (e.g., a user device) or may be independent of but in
communication with the UE. In another implementation, the system [300] may reside in a
10 server or a network entity. In yet another implementation, the system [300] may reside partly
in the server/ network entity and partly in the UE.
[0051] The system [300] is configured for managing network resources, with the help of
the interconnection between the components/units of the system [300].
15
[0052] 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
20 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.
25 [0053] In an embodiment, the system [300] is implementable in a communication system.
The system [300] comprises the transceiver unit [302] connected to an Inventory Manager (IM)
[310]. Further, the transceiver unit [302] is configured to transmit a create task request
comprising one or more task parameters to a Platform scheduler and cron jobs (PSC) [1100].
30 [0054] In one aspect, the IM [310] is configured to maintain an up-to-date inventory of
one or more network resources that are present within the communication network. The one or
more network resources mentioned herein may include one or more physical resources, such
as servers, routers, switches, and alike. Furthermore, the one or more network resources
16
mentioned herein may include one or more virtual resources, such as virtual network functions
(VNFs), containerized network functions (CNFs), network slices and alike. It is to be noted
that the one or more network resources may contain any other network resources that is not
mentioned herein but would be known to a person skilled in the art.
5
[0055] In another aspect, the IM [310] is configured to update the inventory based on
addition, removal or reallocation of the one or more network resources, for ensuring real-time
tracking of the one or more network resources which may further define an availability and
status of the one or more network resources.
10
[0056] Further, the PSC [1100] mentioned herein are utilized for scheduling one or more
tasks (preferably periodic tasks) and further executing said one or more tasks, according to a
respective time interval of said one or more tasks. The one or more tasks herein may include
API calls, FTP transfers, event-triggered actions, database queries, and alike that would be
15 known to a person skilled in the art. Furthermore, the one or more tasks mentioned herein may
be a recurring task or a trigger-based task that are based on one or more events or conditions,
respectively. It is to be noted that the corn jobs within the PSC [1100] is responsible for
handling the periodic execution of the aforementioned one or more tasks, ensuring that one or
more microservice may perform the one or more tasks within a designated time allotted with
20 the one or more tasks.
[0057] Further, in an implementation of the present disclosure, the create task request may
contain one or more task parameters that may further define a scheduling and execution of said
respective task.
25
[0058] In one example, the one or more task parameters may include a task type that may
further specify that whether a task from the one or more task is an application programming
interface (API) call, a file transfer protocol (FTP) transfer, an event-driven action, or a database
query.
30
[0059] In another example, the one or more task parameters may include an execution time
interval that may further specify a periodic interval (if applicable) at which a specific task from
the one or more task is to be executed (i.e., daily, weekly, or hourly).
17
[0060] In yet another example, the one or more task parameters may include a priority
level that may further specify an urgency or prioritization of a specific task from the one or
more tasks.
5
[0061] In yet another example, the one or more task parameters may include a resource
requirement that may further specify one or more resources that are required to execute the
specific task from the one or more tasks.
10 [0062] It is to be noted that the one or more task parameters associated with the create task
request may contain any other task parameters that is not mentioned herein but would be known
to a person skilled in the art.
[0063] The transceiver unit [302] is further configured to receive, over the interface, at the
15 IM [310] from the PSC [1100], a notification associated with the create task request. Post
sending the create task request to the PSC [1100], the transceiver unit [302] may wait for a
response such as the notification mentioned herein, associated with said create task request
from the PSC [1100].
20 [0064] In an example, the notification received at the transceiver unit [302] may include
an acknowledgement message indicating that the create task request is received or the task to
be created by the PSC [1100] is created or scheduled.
[0065] In another example, the notification received at the transceiver unit [302] may
25 include an update in a status for said create task request informing that whether the task is
currently running, delayed, completed, encountered errors or alike.
[0066] In yet another example, the notification received at the transceiver unit [302] may
include an error or failure message which may be delivered in an event, the task mentioned in
30 the create task request may fail to execute, encounter an error, or may be delayed due to one or
more issues.
18
[0067] In yet another example, the notification received at the transceiver unit [302] may
include a task completion message which may indicate the task mentioned in the create task
request is successfully executed.
5 [0068] It is to be noted that the notification associated with the create task request
mentioned herein are just exemplary and, in any order, may not limit the scope of the present
disclosure.
[0069] Further, the interface is a PSC_IM interface. The interface mentioned above is
10 utilized to facilitate a communication channel between the IM [310] and the PSC [1100].
Further, the PSC_IM interface is based on hypertext transfer protocol (HTTP) communication,
which may require the IM [310] to send one or more create task requests in a standardized
format. In an implementation, the HTTP communication is essential for creation of one or more
tasks that may involve API calls or FTP transfers, as the mentioned one or more tasks may
15 involve an interaction with external systems that are connected with the communication
network.
[0070] The system [300] further comprises the processing unit [308] at the PSC [1100].
Herein, the PSC [1100] is configured to create, at the PSC [1100], a task based on the create
20 task request. In an implementation of the present disclosure, post receiving the create task
request at the PSC [1100], the processing unit [308] at the PSC [1100] may parse one or more
task parameters mentioned in said create task request. Thereafter, the processing unit [308]
may create a task entry within the PSC [1100]. The task entry may include one or more
information required to create the task mentioned in said create task request.
25
[0071] Thereafter, the processing unit [308] is configured to schedule, at the PSC
[1100], the task based on the one or more task parameters. In an implementation of the present
disclosure, post creating the task entry of said task, the processing unit [308] may interact with
the corn jobs within the PSC [1100] to schedule the task for execution. Herein, the scheduling
30 of the task is done based on the one or more task parameters (such as priority and execution
time interval) that are mentioned within the create task request.
19
[0072] Post scheduling of the task at the PSC [1100], the processing unit [308] may send
a corresponding notification (mentioned above) back to the transceiver unit [302] in order to
notify the IM [310] regarding scheduling said task mentioned in said create task request.
5 [0073] The system [300] further comprises the identification unit [306] connected at least
to the transceiver unit [302], Herein, the identification unit [306] is configured to identify, at
the IM [310], one or more resources associated with the create task request. Post creating the
create task request, the identification unit [306] may identify the one or more resources that
constitute at least one of a physical resource and a virtual resource.
10
[0074] In an implementation of the present disclosure, the identification unit [306] may
analyse the one or more task parameters mentioned in the create task request (such as task type,
execution time interval and other details) or the notification received from the PSC [1100] and
may accordingly determine the one or more resources that is required in the execution of the
15 task.
[0075] In one example, for identifying at least one of a physical resource, the identification
unit [306] may parse the one or more task parameters mentioned in the create task request, to
identify one or more servers, routers, switches, or any other physical resources that may be
20 required in execution of the task mentioned in said create task request, and post identification
of said one or more physical resources, the identification unit [306] may detect the availability
of said one or more physical resources for executing said task.
[0076] In one example, for identifying at least one of a virtual resource the identification
25 unit [306] may parse the one or more task parameters mentioned in the create task request, to
identify any involvement of one or more VNFs, CNFs, network slices or any other virtual
resources that may be required in execution of the task mentioned in said create task request,
and post identification of said one or more virtual resources, the identification unit [306] may
detect the availability of said one or more virtual resources for executing said task.
30
[0077] Further, the system [300] comprises the performance unit [304] connected at least
to the transceiver unit [302]. Herein, the performance unit [304] is configured to perform a
20
target action on a set of resources based on the received notification. Further, the target action
is at least one of a reserve resources action and an unreserve resources action.
[0078] In an implementation of the present disclosure, in case the target action is the
5 reserve resources action, then the target action may ensure that the one or more network
resources (at least one a physical and virtual network resources) are reserved for execution of
said scheduled task. The performance unit [304] may monitor the notification and may
accordingly reserve the one or more network resources, accordingly.
10 [0079] In another implementation of the present disclosure, in case the target action is the
unreserve resources action, which may further indicate that the task mentioned in said create
task request is either executed or may face any error during the execution, then the target action
may further ensure that the reserved one or more network resources are then unreserved for
execution of other tasks at the PSC [1100].
15
[0080] In an event, the target action is a reserve resources action, the processing unit [308]
is further configured to reserve one or more resources at the PSC [1100], for the scheduled task
based on performing the reserve resources action. Further, in an implementation of the present
disclosure, in an event, the create task request is processed, and the task is scheduled, then the
20 processing unit [308] at the PSC [1100] may then reserves the required one or more network
resources as mentioned in the target action, to ensure that the one or more network resources
are available at the time of execution of said task. This reservation prevents other processes or
tasks from using the same one or more resources, which may further ensure said one or more
network resources are dedicated to said scheduled task.
25
[0081] In another event, the target action is an unreserve resources action, the processing
unit [308] is further configured to unreserve one or more resources at the PSC [1100], for the
scheduled task based on performing the unreserve resources action. Furthermore, in another
implementation of the present disclosure, in another event, once the task is successfully
30 executed or failed, then in such events, the processing unit [308] unreserves the reserved one
or more network resources.
21
[0082] For ease of understanding, the present disclosure is explained with an exemplary
scenario. In an event the create task request may correspond to an FTP data backup task for the
IM [310], and is sent to the PSC [1100]. Further, the one or more task parameters may include
a task type (which is FTP transfer), an execution time interval (suppose at 3:00 PM of the
5 following day), a priority level (suppose a high priority level), and the resource requirements
(suppose a file path, credentials to access the FTP server and alike). Thereafter, post receiving
the create task request, the PSC [1100] may process the create task request and accordingly
schedule the task at the mentioned execution time interval. Further, the identification unit [306]
may identify that the task me require a physical resource (such as a database) and a virtual
10 resource (such as a CNF) and another one or more network resource for executing the FTP data
backup task. Thereafter, the performance unit [304] may send the following one or more
resource to the processing unit [308] at the PSC [1100] to reserve the one or more mentioned
network resources at the execution time interval to execute the FTP data backup task as per
requirement. Further, post completion of said FTP data backup task, the processing unit [308]
15 may then again unreserve the one or more mentioned network resources, enabling the one or
more mentioned network resources to be available for other tasks.
[0083] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
network resources, in accordance with exemplary implementations of the present disclosure is
20 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.
[0084] Also, as shown in FIG.4, the method [400] initially starts at step [402].
25
[0085] At step [404], the method [400] comprises transmitting, by the transceiver unit
[302] at the Inventory Manager (IM) [310] to the Platform scheduler and cron jobs (PSC)
[1100], the create task request comprising one or more task parameters.
30 [0086] At step [406], the method [400] comprises receiving over the interface, by the
transceiver unit [302] at the Inventory Manager (IM) [310] from the PSC [1100], the
notification associated with the create task request. Herein, the interface is the PSC_IM
interface.
22
[0087] The method [400] further explains that prior to receiving the notification over the
interface, the method [400] comprises creating, by the processing unit [308] at the PSC [1100],
the task based on the create task request.
5
[0088] Thereafter, scheduling, by the processing unit [308] at the PSC [1100], the task
based on the one or more task parameters.
[0089] The method [400] further explains that post receiving the notification over the
10 interface the method [400] comprises identifying, by the identification unit [306] at the IM
[310], one or more resources associated with the create task request. Further, the one or more
resources are at least one of a physical resource and a virtual resource.
[0090] At step [408], the method [400] comprises performing, by the performance unit
15 [304] at the IM [310], the target action on the set of resources based on the notification. Herein,
the target action is at least one of the reserve resources action and the unreserve resources
action.
[0091] The method [400] further explains that in an event the target action is the reserve
20 resources action, the method [400] comprises reserving, by the processing unit [308], one or
more resources for the scheduled task based on performing the reserve resources action.
[0092] The method [400] further explains that in another event the target action is the
unreserve resources action, the method [400] comprises unreserving, by the processing unit
25 [308], one or more resources for the scheduled task based on performing the unreserve
resources action.
[0093] The method [400] herein terminates at step [410].
30 [0094] Referring to FIG. 5, an exemplary block diagram of a system architecture [500]
for managing network resources, is shown, in accordance with the exemplary implementations
of the present disclosure. The system [500] comprises at least one edge resource manager
23
(ERM) [502], at least one edge load balancer (ELB) [504], at least one virtual network function
(VNF) manager [506], at least one cron and schedulers management unit [508], at least one
Elasticsearch- database (ES-DB) client [510], at least one Elasticsearch (ES) [512], at least one
graphical user interface (GUI) interface [514], and at least one command-line interface (CLI)
5 [516]. As shown in the figures all units shown within the system [500] should also be assumed
to be connected to each other. Also, in FIG. 5 only a few units are shown, however, the system
[500] may comprise multiple such units or the system [500] may comprise any such numbers
of said units, as required to implement the features of the present disclosure.
10 [0095] As shown in FIG. 5, the ERM [502] is connected directly to the ELB [504], which
further indicates that the ERM [502] manages one or more network resources at the edge of the
network. The ERM [502] communicates with the ELB [504] and other management units to
ensure one or more tasks are executed efficiently.
15 [0096] Further, the ELB [504] may ensures that one or more resource requests and the one
or more tasks are balanced across the available one or more network resources, such as one or
more instances of VNF manager [506] that are represented as (VM [506a], VM [506b] …VM
[506n]).
20 [0097] Further, the VNF manager [506] manages the one or more virtual network
functions that are running on the VMs (VM [506a], VM [506b] …VM [506n]).
[0098] Further, the cron and schedulers management unit [508] further comprises one or
more sub-units such as a corn management [508a] for handling scheduled one or more tasks
25 and ensuring that the one or more tasks are executed at their respective time intervals.
[0099] The one or more sub-units further include a task management [508b] for managing
the lifecycle of the one or more tasks, such as the creation of the task, scheduling of the task,
execution of the task, and similar.
30
24
[0100] The one or more sub-units further include an event handling [508c] that is
responsible for handling real-time events or may be utilized for executing one or more tasks
that are not scheduled in a certain time period.
5 [0101] The one or more sub-units further include a high availability and fault tolerance
[508d], that may ensure that the system may continue one or more ongoing operation, even at
a failure of one or more components, in order to manage redundancy of the one or more tasks.
[0102] The one or more sub-units further include a FCAPS management [508e] for
10 handling one or more security measures.
[0103] The one or more sub-units further include a data modelling framework [508f] for
managing one or more task and their associated one or more network resource management by
structuring and modelling one or more data associated with the one or more tasks, one or more
15 network resources, and one or more events.
[0104] The cron & schedulers management unit [508] is further connected to the ES-DB
client [510], for interacting with the ES [512] (a database for storing logs, task states, or
historical data).
20
[0105] Further, the ES-DB client [510] may handle large volumes of data with quick
search and retrieval capabilities. Herein, the ES [512] may store task scheduling, resource
allocations, events, and their corresponding statuses.
25 [0106] Further the GUI interface [514] and CLI interface [516] interact with the cron &
schedulers management unit [508] via the ELB [504]. The GUI interface [514] facilities a userfriendly interface for users to interact with the system, monitor tasks, and manage resources.
Similarly, the CLI interface [516] may facilitate command-line access for users for providing
direct control over task management, event handling, and resource allocation.
30
[0107] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for managing network resources, the instructions comprising
25
executable code which, when executed by one or more units of a system [300], causes: a
transceiver unit [302] to transmit, at an inventory manager (IM) [310], a create task request
comprising one or more task parameters to a Platform scheduler and cron jobs (PSC) [1100].
The executable code which, when executed by one or more units of a system [300], causes the
5 transceiver unit [302] to receive, over an interface, at the IM [310] from the PSC [1100], a
notification associated with the create task request. Further, the executable code which, when
executed by one or more units of a system [300], causes a performance unit [304] to perform a
target action on a set of resources based on the received notification, wherein the target action
is at least one of a reserve resources action and an unreserve resources action.
10
[0108] As is evident from the above, the present disclosure provides a technically
advanced solution for managing network resources. The present disclosure solves the challenge
of job scheduling in the Inventory Management (IM) microservice, which further reduces
overhead such as testing, and integration efforts in order to provide a more efficient and cost15 effective operational model. Further, the present disclosure simplifies operations compared to
traditional methods where tasks are managed separately in individual units. The approach of
the present disclosure improves efficiency, lowers costs, and makes task management more
agile and responsive, offering significant improvements in the functions performed by the one
or more microservices.
20
[0109] 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
25 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.
26
We Claim:
1. A method [400] for managing network resources, the method [400] comprising:
5 - transmitting, by a transceiver unit [302] at an Inventory Manager (IM) [310] to a
Platform scheduler and cron jobs (PSC) [1100], a create task request comprising one or
more task parameters;
- receiving, by the transceiver unit [302], over an interface, at the Inventory Manager
(IM) [310] from the PSC [1100], a notification associated with the create task request;
10 and
- performing, by a performance unit [304] at the IM [310], a target action on a set of
resources based on the notification, wherein the target action is at least one of a reserve
resources action and an unreserve resources action.
15 2. The method [400] as claimed in claim 1, wherein, post transmitting the create task request,
and prior to receiving the notification over the interface, the method [400] further
comprises:
- creating, by a processing unit [308] at the PSC [1100], a task based on the create task
request; and
20 - scheduling, by the processing unit [308] at the PSC [1100], the task based on the one
or more task parameters.
3. The method [400] as claimed in claim 2, wherein the method [400] further comprises
reserving, by the processing unit [308], one or more resources for the scheduled task based
25 on performing the reserve resources action.
4. The method [400] as claimed in claim 2, wherein the method [400] further comprises
unreserving, by the processing unit [308], one or more resources for the scheduled task
based on performing the unreserve resources action.
30
5. The method [400] as claimed in claim 1, wherein post receiving the notification over the
interface, and prior to performing the target action, the method [400] further comprises
27
identifying, by an identification unit [306] at the IM [310], one or more resources
associated with the create task request, wherein the one or more resources are at least one
of a physical resource and a virtual resource.
5 6. The method [400] as claimed in claim 1, wherein the interface is an PSC_IM interface.
7. A system [300] for managing network resources, the system [300] comprises:
- a transceiver unit [302] configured to:
 transmit, from an inventory manager (IM) [310], a create task request
10 comprising one or more task parameters to a Platform scheduler and cron jobs
(PSC) [1100]; and
 receive, over an interface, at the IM [310] from the PSC [1100], a notification
associated with the create task request; and
- a performance unit [304] connected at least to the transceiver unit [302], wherein the
15 performance unit [304] is configured to perform a target action on a set of resources
based on the received notification, wherein the target action is at least one of a reserve
resources action and an unreserve resources action.
8. The system [300] as claimed in claim 7, wherein the PSC [1100] comprises a processing
20 unit [308], and wherein post transmitting the create task request, and prior to receiving
the notification over the interface, the processing unit [308] is configured to:
- create, at the PSC [1100], a task based on the create task request; and
- schedule, at the PSC [1100], the task based on the one or more task parameters.
25 9. The system [300] as claimed in claim 8, wherein the processing unit [308] is further
configured to reserve one or more resources at the PSC [1100], for the scheduled task
based on performing the reserve resources action.
10. The system [300] as claimed in claim 8, wherein the processing unit [308] is further
30 configured to unreserve one or more resources at the PSC [1100], for the scheduled task
based on performing the unreserve resources action.
28
11. The system [300] as claimed in claim 7, wherein the system [300] comprises an
identification unit [306] connected at least to the transceiver unit [302], and wherein, post
receiving the notification over the interface, and prior to performing the target action, the
identification unit [306] is configured to identify, at the IM [310], one or more resources
5 associated with the create task request, wherein the one or more resources are at least one
of a physical resource and a virtual resource.
12. The system [300] as claimed in claim 7, wherein the interface is an PSC_IM interface.