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 MONITORING RESOURCE
ALLOCATION IN A NETWORK”
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 MONITORING RESOURCE
ALLOCATION IN A NETWORK
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure relate generally to the field of
wireless communication systems. More particularly, embodiments of the present
disclosure relate to a method and system for monitoring resource allocation in a
network.
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] Wireless communication technology has rapidly evolved over the past few
decades, with each generation bringing significant improvements and
advancements. The first generation of wireless communication technology was
based on analog technology and offered only voice services. However, with the
advent of the second-generation (2G) technology, digital communication and data
25 services became possible, and text messaging was introduced. 3G technology
marked the introduction of high-speed internet access, mobile video calling, and
location-based services. The fourth generation (4G) technology revolutionized
wireless communication with faster data speeds, better network coverage, and
improved security. Currently, the fifth generation (5G) technology is being
30 deployed, promising even faster data speeds, low latency, and the ability to connect
multiple devices simultaneously. With each generation, wireless communication
3
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
[0004] Network Functions Virtualization Software-Defined Networking (NFV
SDN) platform acts as a single 5 platform to manage all the Virtual Network
Functions (VNFs) and Cloud-native Network Functions (CNFs) deployed in a
telecom network. As the platform is completely based on microservice architecture,
it is highly scalable and is able to handle hundreds of NFV. The platform is
completely event driven and is based on standard REST APIs. However, existing
10 platforms face a lot of limitations in scalability, real-time resource synchronization,
and efficient inventory management. The existing solutions suffer from resource
mismatches between actual hardware usage and inventory records.
[0005] Thus, there exists an imperative need in the art for providing a method and
15 system for efficiently monitoring resource allocation in a network, which the
present disclosure aims to address.
SUMMARY
20 [0006] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.
This summary is not intended to identify the key features or the scope of the claimed
subject matter.
25 [0007] An aspect of the present disclosure may relate to a method for monitoring
resource allocation in a network at an auditor node, the method comprising:
receiving, by a transceiver unit from a physical virtual inventory manager (PVIM)
unit, a set of details associated with a plurality of container network function
components (CNFCs). The method further comprises transmitting, by the
30 transceiver unit to a Service Adaptor (SA), the set of details associated with the
plurality of CNFCs over an interface. The method comprises receiving, by the
4
transceiver unit from the SA, an attribute message related to one or more CNFCs
among the plurality of CNFCs, based on the set of details associated with each
CNFC among the plurality of CNFCs. The attribute message comprises a real-time
information related to resources utilized by each CNFC among the plurality of
5 CNFCs.
[0008] In an exemplary aspect of the present disclosure, the set of details comprises
details of a set of servers and a set of nodes associated with each CNFC of the
plurality of CNFCs.
10
[0009] In an exemplary aspect of the present disclosure, prior to receiving the
attribute message based on the set of details associated with the plurality of CNFCs
from the SA, the method comprises: receiving, by the SA, a query related to
providing the real-time information associated with the one or more CNFCs among
15 the plurality of CNFCs. The method further comprises fetching, by the SA, the realtime
information associated with the one or more CNFCs among the plurality of
CNFCs.
[0010] In an exemplary aspect of the present disclosure, the interface is AU_SA.
20
[0011] Another aspect of the present disclosure may relate to a system for
monitoring resource allocation in a network at an auditor node, the system
comprising a transceiver unit configured to receive, from a physical virtual
inventory manager (PVIM) unit, a set of details associated with a plurality of
25 container network function components (CNFCs). The transceiver unit is
configured to transmit, to a Service Adaptor (SA), the set of details associated with
the plurality of CNFCs over an interface. The transceiver unit is configured to
receive, from the SA, an attribute message related to one or more CNFCs among
the plurality of CNFCs, based on the set of details associated with each CNFC
30 among the plurality of CNFCs. The attribute message comprises a real-time
5
information related to resources utilized by each CNFC among the plurality of
CNFCs.
[0012] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable 5 storage medium storing instructions for monitoring resource
allocation in a network at an auditor node, the instructions include executable code
which, when executed by one or more units of a system, causes: a transceiver unit
of the system to receive, from a physical virtual inventory manager (PVIM) unit, a
set of details associated with a plurality of container network function components
10 (CNFCs). Further, the executable code when executed causes, the transceiver unit
to transmit, to a Service Adaptor (SA), the set of details associated with the plurality
of CNFCs over an interface. Furthermore, the executable code when executed
causes, the transceiver unit to receive, from the SA, an attribute message related to
one or more CNFCs among the plurality of CNFCs, based on the set of details
15 associated with each CNFC among the plurality of CNFCs. The attribute message
comprises a real-time information related to resources utilized by each CNFC
among the plurality of CNFCs.
OBJECTS OF THE DISCLOSURE
20
[0013] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0014] It is an object of the present disclosure to provide a system and method for
25 monitoring resource allocation in a network.
[0015] It is another object of the present disclosure to provide a solution for
optimizing the network operations by increasing availability and efficient
utilization of the resources.
30
6
[0016] It is yet another object of the present disclosure to provide a solution that
provides data of actual resources used by CNFCs running on servers of a site.
DESCRIPTION OF THE DRAWINGS
5
[0017] 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,
10 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
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
15 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0018] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture, in accordance with
20 exemplary implementations of the present disclosure.
[0019] FIG. 2 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented, in accordance
with exemplary implementations of the present disclosure.
25
[0020] FIG. 3 illustrates an exemplary block diagram of a system for monitoring
resource allocation in a network, in accordance with exemplary implementations of
the present disclosure.
7
[0021] FIG. 4 illustrates an exemplary flow diagram for monitoring resource
allocation in the network, in accordance with exemplary implementations of the
present disclosure.
[0022] FIG. 5 illustrates a method flow 5 diagram for monitoring resource allocation
in the network, in accordance with exemplary implementations of the present
disclosure.
[0023] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0024] In the following description, for the purposes of explanation, various
15 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 independently of one
another or with any combination of other features. An individual feature may not
20 address any of the problems discussed above or might address only some of the
problems discussed above.
[0025] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
25 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
8
[0026] 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
specific details. For example, circuits, systems, processes, and other components
may be shown as components 5 in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0027] 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
10 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
included in a figure.
15
[0028] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
20 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
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0029] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
30 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
9
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 data processing,
input/output processing, and/or any 5 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.
[0030] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
10 “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
user equipment/device may include, but is not limited to, a mobile phone, smart
15 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 the features of the present disclosure.
20
[0031] 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
medium includes read-only memory (“ROM”), random access memory (“RAM”),
25 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 [0032] As used herein, “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
10
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
each other, which also includes the methods, functions, or procedures that may be
called.
5
[0033] 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
10 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.
[0034] As used herein, the transceiver unit include at least one receiver and at least
15 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.
[0035] The present disclosure aims to overcome the limitations discussed in the
20 background section and other existing problems in this field of technology by
providing data of actual resources used by CNFCs running on servers of a site.
[0036] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
25
[0037] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture/platform [100], in accordance
with exemplary implementations of the present disclosure. The MANO architecture
[100] may be developed for managing telecom cloud infrastructure automatically,
30 managing design or deployment design, managing instantiation of a network
node(s) etc/service(s). The MANO architecture [100] deploys the network node(s)
11
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 automatically instantiate the VNFs into the
corresponding environment 5 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 may comprise a NFV Platform Decision Analytics (NPDA) [1096]
component.
10 [0038] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer [102], a network function virtualization (NFV) and software defined
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 may be assumed to be
15 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] comprises a VNF
lifecycle manager [1042], a VNF catalog [1044], a network services catalog [1046],
20 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 [1042] may be responsible for deciding on which server of the
communication network the microservice may be instantiated. The VNF lifecycle
manager [1042] may manage the overall flow of incoming/ outgoing requests
25 during interaction with the user. The VNF lifecycle manager [1042] may be
responsible for determining which sequence to be followed for executing the
process. For e.g. in an AMF network function of the communication network (such
as a 5G network), sequence for execution of processes P1 and P2 etc. The VNF
catalog [1044] stores the metadata of all the VNFs (also CNFs in some cases). The
30 network services catalog [1046] stores the information of the services that need to
be run. The network slicing and service chaining manager [1048] manages the
12
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 [1042], the CNF lifecycle manager
[1052] ma 5 y be similarly used for the CNFs lifecycle management.
[0040] 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
10 manager [1070]. The microservices elastic load balancer [1062] may be used for
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
requires changes during the run time. The central logging manager [1068] may be
15 responsible for keeping the logs of every service. These logs are generated by the
MANO platform [100]. These logs may be 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.
20 [0041] The platforms core services module [108] comprises NFV infrastructure
monitoring manager [1082], an assure manager [1084], a performance manager
[1086], a policy execution engine (PEEGN) [1088], a capacity monitoring manager
(CMM) [1090], a release management (mgmt.) repository [1092], a configuration
manager & golden configuration template (GCT) [1094], an NFV platform decision
25 analytics [1096], a platform NoSQL DB [1098], a platform schedulers and cron jobs
[1100], a VNF backup & upgrade manager [1102], a micro service auditor [1104],
and a platform operations, administration and maintenance manager [1106]. The
NFV infrastructure monitoring manager [1082] may monitor the infrastructure part
of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure
30 manager [1084] may be responsible for supervising the alarms the vendor may be
generating. The performance manager [1086] may be responsible for managing the
13
performance counters. The policy execution engine (PEEGN) [1088] may be
responsible for managing all the policies. The capacity monitoring manager (CMM)
[1090] may be responsible for sending the request to the PEEGN [1088]. The
release management repository (RMR) [1092] may be responsible for managing the
releases and the images of all 5 of the vendor’s network nodes. The configuration
manager & GCT [1094] manages the configuration and GCT of all the vendors. The
NFV platform decision analytics (NPDA) [1096] helps in deciding the priority of
using the network resources. It is further noted that the policy execution engine
(PEEGN) [1088], the configuration manager & (GCT) [1094] and the (NPDA)
10 [1096] work together. The platform NoSQL DB [1098] may be a platform database
for storing all the 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 narrower implementation of the present disclosure, and any other kind of
structure for the database may be implemented for the platform database such as
15 relational or non-relational database. The platform schedulers and cron jobs [1100]
may schedule the task such as but not limited to triggering of an event, traverse the
network graph etc. The VNF backup & upgrade manager [1102] takes backup of
the images, binaries of the VNFs and the CNFs and produces those backups on
demand in case of server failure. The microservice auditor [1104] audits the
20 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 case,
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 MANO platform [100]. The platform operations,
25 administration and maintenance manager [1106] may be used for newer instances
that are spawning.
[0042] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122], a generic decoder and indexer
30 (XML, CSV, JSON) [1124], a service adaptor [1126], an API adapter [1128], and a
NFV gateway [1130]. The platform external API adaptor and gateway [1122] may
14
be responsible for handling the external services (to the MANO platform [100]) that
requires the network resources. The generic decoder and indexer (XML, CSV,
JSON) [1124] may get directly the data of the vendor system in the XML, CSV,
JSON format. The service adaptor [1126] may be the interface provided between
the telecom cloud and the MANO architecture 5 [100] for communication. The
Service Adapter (SA) is a microservices-based system designed to deploy and
manage Container Network Functions (CNFs) and their components (CNFCs)
across nodes. It offers REST endpoints for key operations, including uploading
container images to a registry, terminating CNFC instances, and creating volumes
10 and networks. CNFs, which are network functions packaged as containers, may
consist of multiple CNFCs. The SA facilitates the deployment, configuration, and
management of these components by interacting with API, ensuring proper setup
and scalability within a containerized environment. This approach provides a
modular and flexible framework for handling network functions in a virtualized
15 network setup.
[0043] The 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
services going to/incoming from the MANO architecture [100].
20
[0044] 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
25 monitoring resource allocation in a network, utilising the system. In another
implementation, the computing device [200] itself implements the method for
monitoring resource allocation in the network, 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.
30
15
[0045] 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.
The computing device [200] 5 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
10 by the processor [204]. Such instructions, when stored in non-transitory storage
media accessible to the processor [204], render the computing device [200] into a
special-purpose machine that is customized to perform the operations specified in
the instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
15 information and instructions for the processor [204].
[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
20 display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
25 [204]. Another type of user input device may be a cursor controller [216], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. This 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
30 the device to specify positions in a plane.
16
[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 machine.
According to one implementation, 5 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
10 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.
15 [0048] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a twoway
data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
20 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] may be a
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [218] sends and receives electrical,
25 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0049] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the
30 communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
17
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.
5
[0050] Referring to FIG. 3, an exemplary block diagram of a system [300] for
monitoring resource allocation in the network, is shown, in accordance with
exemplary implementations of the present disclosure. In an example, the system
[300] may be implemented as or within an auditor node [415] (as shown in FIG. 4).
10 In the context of the present invention, the auditor node [415] may be understood
as the processing entity responsible for overseeing, managing, and auditing network
components within the system [300].
[0051] The system [300] comprises at least one transceiver unit [302] and at least
15 one storage unit [304]. All of the components/ units of the system [300] are assumed
to be connected to each other unless otherwise indicated below.
[0052] As shown in FIG. 3, all units shown within the system [300] should be
assumed to be connected to each other. Also, in FIG. 3, only a few units are shown,
20 however, the system [300] may comprise multiple such units or 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 (UE) (i.e., computing device [200]) to
implement the features of the present disclosure. The system [300] may be a part of
25 the user device [200]/ or may be independent of but in communication with the user
device [200]. 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 [200].
18
[0053] The system [300] is configured for monitoring resource allocation in the
network at the auditor node [415], with the help of the interconnection between the
components/units of the system [300].
[0054] FIG. 4 illustrates an exemplary 5 flow diagram [400] for monitoring resource
allocation in the network at the auditor node [415], in accordance with exemplary
implementations of the present disclosure. It may be noted that FIG. 3 and FIG. 4
have been explained simultaneously and may be read in conjunction with each
other.
10
[0055] In one implementation, the auditor node [415] may be in communication
with other network entities/components. It is noted that FIG. 4 may also include
other network entities/components known to a person skilled in the art and may also
be in communication with the auditor node [415]. Such network
15 entities/components have not been explained here for the sake of brevity. In one
implementation, the auditor node [415] refers to a component within the system
[300] responsible for handling auditing functions.
[0056] In one implementation, the transceiver unit [302] is configured to receive,
20 from a physical virtual inventory manager (PVIM) unit [405], a set of details
associated with a plurality of container network function components (CNFCs).
(i.e., Step [402] in FIG. 4) For example, the set of details include data about servers,
nodes, resource allocation, configuration parameters, and other attributes of each
CNFC.
25
[0057] In one implementation, the auditor node [415] is configured to perform
auditing and management processes by retrieving detailed information about the
CNFCs from the PVIM unit [405]. The PVIM unit [405] is a management entity
responsible for maintaining an inventory in the network.
30
19
[0058] When the auditor node [415] receives the set of details from the PVIM unit
[405], the auditor node [415] is configured to generate an event. In general, CNFCs
are individual components of network functions that are deployed and managed
within containerized environments. Further, this transmission occurs
asynchronously, meaning the 5 auditor node [415] does not require a synchronous
acknowledgment by a Service Adaptor (SA) [410].
[0059] In one implementation, the set of details comprises details of a set of servers
and a set of nodes associated with each CNFC of the plurality of CNFCs.
10
[0060] The set of servers refer to servers on which CNFCs are deployed and
executed. Each server is a host that provides the necessary computing resources,
such as CPU, memory, and storage, required for the operation of CNFCs. The
attributes of each server may include server ID or name for identification, storage
15 resources and availability and network interfaces and bandwidth.
[0061] In general, the set of nodes refer to individual entities within the network
that are associated with each CNFC. The node is a connection point where the
CNFC operates within the network. Each CNFC operates on one or more servers
20 and interacts with one or more nodes in the network. Therefore, the set of details
provides the auditor node [415] with a complete assessment of the each CNFC.
[0062] After receiving the set of details from the PVIM unit [405], the transceiver
unit [302] is configured to transmit, to the Service Adaptor (SA) [410], the set of
25 details associated with the plurality of CNFCs over an interface. In an
implementation, the interface is AU_SA (i.e., Step [404] in FIG. 4).
[0063] The set of details include data associated with the plurality of CNFCs, data
related to the servers and nodes associated with each CNFC. In one embodiment,
30 the interface is AU_SA.
20
[0064] In one implementation, AU_SA interface represents the interaction between
the auditor node [415] and the SA [410]. In particular, AU_SA interface supports
REST API communication over Hyper Text Transfer Protocol (HTTP).
[0065] Prior to receiving the attribute message 5 from the SA [410] based on the set
of details associated with the plurality of CNFCs, the SA [410] is configured to
receive a query related to providing the real-time information associated with the
one or more CNFCs among the plurality of CNFCs. The query herein refers to a
request made by a network entity or system component that requires specific real
10 time information about the one or more CNFCs. The SA [410] is responsible for
handling, processing, and storing information regarding the plurality of CNFCs.
[0066] The query may originate from multiple sources, such as network
management platforms, auditing systems, or external monitoring tools. The query
15 may further be transmitted as a request to the SA [410]. Upon receiving the query
for real-time information regarding the one or more CNFCs, the SA [410] is
configured to fetch the real-time information associated with the one or more
CNFCs among the plurality of CNFCs. Next, the SA [410] is configured to transmit
the real-time information associated with the one or more CNFCs among the
20 plurality of CNFCs back to the auditor node [415] via the AU_SA interface (i.e.,
Step [406] in FIG. 4).
[0067] In particular, the SA [410] is a microservice based system designed to
deploy and manage Container Network Functions (CNFs) and their components
25 (CNFCs) across nodes. The SA [410] offers REST endpoints for key operations,
including uploading container images to a Docker registry, terminating CNFC
instances, and creating volumes and networks, and fetching operation.
[0068] The SA [410] facilitates the deployment, configuration, and management of
30 these components by interacting with API, ensuring proper setup and scalability
21
within a containerized environment. This approach provides a modular and flexible
framework for handling network functions in a virtualized network setup.
[0069] Upon receiving the query, the SA [410] initiates a process to fetch the
requested real time information. The term fetch herein 5 refers to an operation where
the SA [410] accesses the real-time information associated with the one or more
CNFCs from a host.
[0070] Next, the transceiver unit [302] receives, from the SA [410], the attribute
10 message related to the one or more CNFCs from the plurality of CNFCs. The
attribute message is based on the set of details associated with each CNFC and
includes real-time information related to resources utilized by each CNFC.
[0071] In one implementation, the storage unit [304] is configured to store the real15
time information associated with the one or more CNFCs from the plurality of
CNFCs. In one example, the storage unit [304] is configured to store the real-time
information in a database.
[0072] Referring to FIG. 5, an exemplary method flow diagram [500] for
20 monitoring resource allocation in the network at the auditor node [415], in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation, the method [500] 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 shown in FIG. 5, the method [500]
25 starts at step [502].
[0073] At step [504], the method [500] comprises receiving, by the transceiver unit
[302] from the physical virtual inventory manager (PVIM) unit [405], the set of
details associated with the plurality of container network function components
30 (CNFCs). The set of details comprises details of a set of servers and a set of nodes
associated with each CNFC of the plurality of CNFCs.
22
[0074] At step [506], the method [500] comprises transmitting, by the transceiver
unit [302] to the Service Adaptor (SA) [410], the set of details associated with the
plurality of CNFCs over the interface. In an implementation, the interface is
5 AU_SA.
[0075] Prior to receiving the attribute message based on the set of details associated
with the plurality of CNFCs from the SA [410], the method [500] comprises
receiving, by the SA [410], the query related to providing the real-time information
10 associated with the one or more CNFCs among the plurality of CNFCs. The method
[500] also comprises fetching, by the SA [410], the real-time information associated
with the one or more CNFCs among the plurality of CNFCs.
[0076] At step [508], the method [500] comprises receiving, by the transceiver unit
15 [302], from the SA [410], the attribute message related to the one or more CNFCs
among the plurality of CNFCs, based on the set of details associated with each
CNFC among the plurality of CNFCs. The attribute message comprises the realtime
information related to resources utilized by each CNFC among the plurality of
CNFCs.
20
[0077] Thereafter, the method [500] terminates at step [510].
[0078] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for monitoring resource allocation in a network
25 at the auditor node [415], the instructions include executable code which, when
executed by one or more units of a system, causes: a transceiver unit [302] of the
system [300] to retrieve, from a physical virtual inventory manager (PVIM) unit
[405], a set of details associated with a plurality of container network function
components (CNFCs). Further, the executable code when executed causes, the
30 transceiver unit [302] to transmit to the Service Adaptor (SA) [410], the set of
details associated with the plurality of CNFCs over an interface. Furthermore, the
23
executable code when executed causes, the transceiver unit [302] to receive, from
the SA [410], an attribute message related to one or more CNFCs among the
plurality of CNFCs, based on the set of details associated with each CNFC among
the plurality of CNFCs, wherein the attribute message comprises a real-time
information related to resources utilized 5 by each CNFC among the plurality of
CNFCs.
[0079] As is evident from the above, the present disclosure provides a technically
advanced solution for monitoring resource allocation in a network. The present
10 solution provides data of actual resources used by CNFCs running on servers of a
site. The present solution fetches the CNFC instances list for a node.
[0080] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
15 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.
20
[0081] 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
25 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are considered to be encompassed within the scope
30 of the present disclosure.
24
We Claim:
1. A method for monitoring resource allocation in a network at an auditor node
[415], the method comprising:
- receiving, by a transceiver unit [302] from a physical virtual inventory
manager (PVIM) unit 5 [405], a set of details associated with a plurality
of container network function components (CNFCs);
- transmitting, by the transceiver unit [302] to a Service Adaptor (SA)
[410], the set of details associated with the plurality of CNFCs over an
interface; and
10 - receiving, by the transceiver unit [302] from the SA [410], an attribute
message related to one or more CNFCs among the plurality of CNFCs,
based on the set of details associated with each CNFC among the
plurality of CNFCs, wherein the attribute message comprises a real-time
information related to resources utilized by each CNFC among the
15 plurality of CNFCs.
2. The method as claimed in claim 1, wherein the set of details comprises
details of a set of servers and a set of nodes associated with each CNFC of
the plurality of CNFCs.
20
3. The method as claimed in claim 1, wherein prior to receiving the attribute
message based on the set of details associated with the plurality of CNFCs
from the SA [410], the method comprises:
- receiving, by the SA [410], a query related to providing the real-time
25 information associated with the one or more CNFCs among the plurality
of CNFCs; and
- fetching, by the SA [410], the real-time information associated with the
one or more CNFCs among the plurality of CNFCs.
30 4. The method as claimed in claim 1, wherein the interface is AU_SA.
25
5. A system [300] for monitoring resource allocation in a network at an auditor
node [415], the system comprises a transceiver unit [302] configured to:
- receive, from a physical virtual inventory manager (PVIM) unit [405],
a set of details associated with a plurality of container network function
5 components (CNFCs);
- transmit, to a Service Adaptor (SA) [410], the set of details associated
with the plurality of CNFCs over an interface; and
- receive, from the SA [410], an attribute message related to one or more
CNFCs among the plurality of CNFCs, based on the set of details
10 associated with each CNFC among the plurality of CNFCs, wherein the
attribute message comprises a real-time information related to resources
utilized by each CNFC among the plurality of CNFCs.
6. The system [300] as claimed in claim 5, wherein the set of details comprises
15 details of a set of servers and a set of nodes associated with each CNFC of
the plurality of CNFCs.
7. The system [300] as claimed in claim 5, wherein prior to receiving the
attribute message based on the set of details associated with the plurality of
20 CNFCs from the SA [410], the SA [410] is configured to:
- receive a query related to providing the real-time information associated
with the one or more CNFCs among the plurality of CNFCs; and
- fetch the real-time information associated with the one or more CNFCs
among the plurality of CNFCs.
25
8. The system [300] as claimed in claim 5, wherein the interface is AU_SA.