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 MANAGING VIRTUAL
NETWORK FUNCTION (VNF) RESOURCES”
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 MANAGING VIRTUAL NETWORK
FUNCTION (VNF) 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 managing virtual network function (VNF) resources.
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
include certain aspects of the art that may be related to various features of the
15 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.
[0003] In communication networks, different microservices perform different
20 services, jobs and tasks in the network. Different microservices have to perform
their jobs in such a way based on operational parameters and policies, that it does
not affect microservices’ own operation and service network operations. Virtual
Network Function (VNF) replaces network hardware with software that can be
changed and scaled to meet increasing demands. However, the current traditional
25 methods are not efficient for managing the VNF instantiations, maintaining the
relationship between physical and virtual resources with respect to different
attributes as per requirements of different microservices. Further, to manage the
data accuracy for VNF instantiations, VNF pools based on microservices with
create, update, delete resources tasks are cumbersome and challenging tasks.
30
3
[0004] Thus, there exists an imperative need in the art to provide an efficient system
and method for creating and managing VNF resources via IM_OS interface in the
network.
5 SUMMARY
[0005] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.
This summary is not intended to identify the key features or the scope of the claimed
10 subject matter.
[0006] An aspect of the present disclosure may relate to a method for managing
virtual network function (VNF) resources. The method comprises receiving, by a
transceiver unit, a request for managing one or more resources, through a
15 management platform (MP) from a user interface. The method further comprises
transmitting, by the transceiver unit, a request for performing action on the received
resource managing request, to a network function through the MP. Further, the
method comprises validating, by an authentication unit, the received request for
performing action by the network function. Furthermore, the method comprises
20 receiving, by the transceiver unit, a success response, through the MP, from the
network function after performing the action based on the request. Hereinafter, the
method comprises sending, by the transceiver unit, a notification related to a
resource managing action response, over an interface through the MP, to a physical
and virtual inventory manager (PVIM). The method further comprises storing, by a
25 storage unit, the resource managing status, at the PVIM.
[0007] In an exemplary aspect of the present disclosure, the resource managing
request involves at least one of: creating and configuring one or more resources.
4
[0008] In an exemplary aspect of the present disclosure, network function is at least
one of: a virtualized infrastructure manager (VIM) and network function virtualized
infrastructure monitoring manager (NFVIM).
5 [0009] In an exemplary aspect of the present disclosure, the one or more resources
comprises physical or virtual of compute, RAM, storage, network resource.
[0010] In an exemplary aspect of the present disclosure, the at least one of: the
sending of the request and the receiving of the response between the MP and the
10 PVIM is via an IM_OS interface.
[0011] In an exemplary aspect of the present disclosure, the method further
comprises sending, by the transceiver unit, a request for creating or deleting a
virtual IP (VIP) pool to the physical and virtual inventory manager (PVIM) through
15 the MP.
[0012] In an exemplary aspect of the present disclosure, the resource managing
request comprises performing create, read, update, or delete (CRUD) operations on
host aggregate through an interface designed for host aggregate management.
20
[0013] In an exemplary aspect of the present disclosure, sending the notification
related to the resource managing action response is performed by the transceiver
unit, through the OSA [304], for the performed action to the PVIM.
25 [0014] In an exemplary aspect of the present disclosure, the storing, by the storage
unit, the resource managing status, with resources attributes, at the PVIM.
[0015] Another aspect of the present disclosure may relate to a system for
managing virtual network function (VNF) resources. The system comprises a
30 transceiver unit. The transceiver unit configured to receive a request for managing
one or more resources, through a management platform (MP), from a user interface.
5
The transceiver unit is further configured to transmit a request for performing action
on the received resource managing request, to a network function, through the MP.
The system further comprises an authentication unit connected to at least the
transceiver unit. The authentication unit is configured to validate the received
5 request for performing action by the network function. Further, the transceiver unit
is configured to receive, a response, through the MP, from the network function
after performing the action based on the request. The transceiver unit is further
configured to send a resource managing action response, through the MP, to a
physical and virtual inventory manager (PVIM). The system further comprises a
10 storage unit connected to at least the authentication unit. The storage unit is
configured to store the resource managing status, at the PVIM.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium, storing instructions for managing virtual
15 network function (VNF) resources, the instructions include executable code which,
when executed by one or more units of a system cause a transceiver unit to receive
a request for managing one or more resources, through a management platform
(MP), from a user interface. The instructions when executed by the system further
cause the transceiver unit to transmit a request for performing action on the received
20 resource managing request, to a network function, through the MP. The instructions
when executed by the system further cause an authentication unit to validate the
received request for performing action by the network function. The instructions
when executed by the system further cause the transceiver unit to receive, a
response, through the MP, from the network function after performing the action
25 based on the request. The instructions when executed by the system further cause
the transceiver unit to send a resource managing action response, through the MP,
to a physical and virtual inventory manager (PVIM). The instructions when
executed by the system further cause a storage unit to store the resource managing
status, at the PVIM.
30
6
OBJECTS OF THE INVENTION
[0017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
5
[0018] It is an object of the present disclosure to provide a system and a method for
creating and managing VNF resources via IM_OS interface.
[0019] It is another object of the present disclosure to provide a system and a
10 method for performing fault tolerance for any event failure, IM_OS interface works
in a high availability mode and if one inventory instance went down during request
processing, then next available instance may take care of this request.
[0020] It is another object of the present disclosure to provide a system and a
15 method for performing auto sync inventory with VNF resources creation, deletion
and updating via IM_OS interface.
DESCRIPTION OF THE DRAWINGS
20 [0021] 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
25 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
drawings includes disclosure of electrical components or circuitry commonly used
30 to implement such components.
7
[0022] FIG. 1 illustrates an exemplary block diagram representation of
management and orchestration (MANO) architecture/ platform, in accordance with
exemplary implementation of the present disclosure.
5 [0023] FIG. 2 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0024] FIG. 3 illustrates an exemplary block diagram of a system for managing
10 virtual network function (VNF) resources, in accordance with exemplary
implementations of the present disclosure.
[0025] FIG. 4 illustrates a method flow diagram for managing virtual network
function (VNF) resources, in accordance with exemplary implementations of the
15 present disclosure.
[0026] FIG. 5 illustrates an implementation of system diagram for managing virtual
network function (VNF) resources, in accordance with exemplary implementations
of the present disclosure.
20
[0027] FIG. 6 illustrates an implementation of the method flow for storage pool
creation for managing virtual network function (VNF) resources, in accordance
with exemplary implementations of the present disclosure.
25 [0028] FIG. 7 illustrates an implementation of the method flow for volume creation
for managing virtual network function (VNF) resources, in accordance with
exemplary implementations of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
30 description of the disclosure.
8
DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
5 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
address any of the problems discussed above or might address only some of the
10 problems discussed above.
[0031] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
15 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.
20 [0032] 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 in block diagram form in order not to obscure the
25 embodiments in unnecessary detail.
[0033] 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
30 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
9
is terminated when its operations are completed but could have additional steps not
included in a figure.
[0034] The word “exemplary” and/or “demonstrative” is used herein to mean
5 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
10 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
15
[0035] 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 instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
20 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 other functionality that enables the working of
25 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0036] 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”,
30 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
10
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
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
5 of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of
a transceiver unit, a processing unit, a storage unit, a detection unit and any other
such unit(s) which are required to implement the features of the present disclosure.
10 [0037] 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”),
magnetic disk storage media, optical storage media, flash memory devices or other
15 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.
[0038] As used herein “interface” or “user interface” refers to a shared boundary
20 across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be
called.
25
[0039] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
30 microprocessors in association with a DSP core, a controller, a microcontroller,
11
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0040] As used herein the transceiver unit include at least one receiver and at least
5 one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
and/or connected with the system.
[0041] As discussed in the background section, the current known solutions have
10 several shortcomings. The present disclosure aims to overcome the abovementioned and other existing problems in this field of technology by providing
method and system of managing virtual network function (VNF) resources.
[0042] FIG. 1 illustrates an exemplary block diagram representation of a
15 management and orchestration (MANO) architecture/ platform [100], in
accordance with exemplary implementation of the present disclosure. The MANO
architecture [100] is developed for managing telecom cloud infrastructure
automatically, managing design or deployment design, managing instantiation of
network node(s)/ service(s) etc. The MANO architecture [100] deploys the network
20 node(s) in the form of Virtual Network Function (VNF) and Cloud-native/
Container Network Function (CNF). The system may comprise one or more
components of the MANO architecture [100]. The MANO architecture [100] is
used to auto-instantiate the VNFs into the corresponding environment of the present
disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to
25 the platform.
[0043] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer, a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platforms foundation services
30 module [106], a platform core services module [108] and a platform resource
adapters and utilities module [112]. All the components are assumed to be
12
connected to each other in a manner as obvious to the person skilled in the art for
implementing features of the present disclosure.
[0044] The NFV and SDN design function module [104] 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 deciding on which server of
the communication network, the microservice will be instantiated. The VNF
10 lifecycle manager (compute) [1042] may manage the overall flow of incoming/
outgoing requests during interaction with the user. The VNF lifecycle manager
(compute) [1042] is responsible for determining which sequence to be followed for
executing the process. For e.g. in an AMF network function of the communication
network (such as a 5G network), sequence for execution of processes P1 and P2
15 etc. The VNF catalogue [1044] stores the metadata of all the VNFs (also CNFs in
some cases). The network services catalogue [1046] stores the information of the
services that need to be run. The network slicing and service chaining manager
[1048] manages the slicing (an ordered and connected sequence of network service/
network functions (NFs)) that must be applied to a specific networked data packet.
20 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 used for the CNFs lifecycle management.
[0045] The platforms foundation services module [106] comprises a microservices
25 elastic load balancer [1062], an identity & access manager [1064], a command line
interface (CLI) [1066], a central logging manager [1068], and an event routing
manager [1070]. The microservices elastic load balancer [1062] is used for
maintaining the load balancing of the request for the services. The identity & access
manager [1064] is used for logging purposes. The command line interface (CLI)
30 [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
13
keeping the logs of every service. These logs are generated by the MANO platform
[100]. These logs are used for debugging purposes. The event routing manager
[1070] is responsible for routing the events i.e., the application programming
interface (API) hits to the corresponding services.
5
[0046] The platforms core services module [108] 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 & GCT
10 [1094], an NFV platform decision 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] monitors the infrastructure part of the NFs. For e.g., any metrics such as
15 CPU utilization by the VNF. The assure manager [1084] is responsible for
supervising the alarms the vendor is generating. The performance manager [1086]
is responsible for managing the performance counters. The policy execution engine
(PEGN) [1088] is responsible for all the managing the policies. The capacity
monitoring manager (CMM) [1090] is responsible for sending the request to the
20 PEGN [1088]. The release management (mgmt.) repository (RMR) [1092] is
responsible for managing the releases and the images of all the vendor network
node. The configuration manager & (GCT) [1094] manages the configuration and
GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps
in deciding the priority of using the network resources. It is further noted that the
25 policy execution engine (PEGN) [1088], the configuration manager & GCT [1094]
and the NPDA [1096] work together. The platform NoSQL DB [1098] is a database
for storing all the inventory (both physical and logical) as well as the metadata of
the VNFs and CNF. The platform schedulers and cron jobs [1100] schedules the
task such as but not limited to triggering of an event, traverse the network graph
30 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
14
of server failure. The micro service auditor [1104] audits the microservices. For
e.g., in a hypothetical case, instances not being instantiated by the MANO
architecture [100] using the network resources then the micro service auditor [1104]
audits and informs the same so that resources can be released for services running
5 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.
[0047] The platform resource adapters and utilities module [112] further comprises
10 a platform external API adaptor and gateway [1122]; a generic decoder and indexer
(XML, CSV, JSON) [1124]; a docker service adaptor [1126]; an OpenStack API
adapter [1128]; and a NFV gateway [1130]. The platform external API adaptor and
gateway [1122] is responsible for handling the external services (to the MANO
platform [100]) that requires the network resources. The generic decoder and
15 indexer (XML, CSV, JSON) [1124] gets directly the data of the vendor system in
the XML, CSV, JSON format. The docker service adaptor [1126] is the interface
provided between the telecom cloud and the MANO architecture [100] for
communication. The OpenStack API adapter [1128] is used to connect with virtual
machines (VMs). The NFV gateway [1130] is responsible for providing the path to
20 each services going to/incoming from the MANO architecture [100].
[0048] 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
25 implementation, the computing device [200] may also implement a method for
managing virtual network function (VNF) resources utilising the system. In another
implementation, the computing device [200] itself implements the method for
managing virtual network function (VNF) resources, using one or more units
configured within the computing device [200], wherein said one or more units are
30 capable of implementing the features as disclosed in the present disclosure.
15
[0049] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
5 computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202]
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 non-transitory storage media
accessible to the processor [204], render the computing device [200] into a specialpurpose 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].
[0050] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
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]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
30 the device to specify positions in a plane.
16
[0051] 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.
5 According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
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 [0052] 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.
[0053] 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], 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.
5
[0054] The present disclosure is implemented by a system [300] (as shown in FIG.
3). In an implementation, the system [300] may include the computing device [200]
(as shown in FIG. 2). It is further noted that the computing device [200] is able to
perform the steps of a method [400] (as shown in FIG. 4).
10
[0055] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing virtual network function (VNF) 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 authentication unit [304],
15 at least one storage unit [306]. 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 should also be assumed to
be connected to each other. Also, in FIG. 3 only a few units are shown, however,
the system [300] may comprise multiple such units or the system [300] may
20 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 to implement the features of the present disclosure. The
system [300] may be a part of the user device / or may be independent of but in
communication with the user device (may also referred herein as a UE). In another
25 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.
[0056] The system [300] is configured for managing virtual network function
30 (VNF) resources, with the help of the interconnection between the
components/units of the system [300].
18
[0057] The transceiver unit [302] is configured to receive a request, through a
management platform (MP), from a user interface. The request may be for
managing one or more resources. The request may be for managing one or more
5 resources including but may not be limited to a physical or virtual of compute, a
random-access memory (RAM), a storage and a network resource.
[0058] The MP corresponds to a microservice to facilitate deployment and
management of virtual machines (VMs) between microservices. In an exemplary
10 embodiment, the MP may be an open stack adapter (OSA). The adaptor in the OSA
corresponds to an application programming interface (API) between OpenStack and
other systems. The adaptor enables OpenStack to work with others.
[0059] The transceiver unit [302] is further configured to transmit a request for
15 performing action on the received resource managing request, to a network
function. The request to perform the action is transmitted via the MP. In one
example, the action refers to a specific operation requested in context of managing
virtual network function (VNF) resources. The action comprises performing a
create, read, update, or delete (CRUD) operations on host aggregate, volume
20 storage, storage pool or network through an interface. The host aggregate
corresponds to a grouping of the physical and virtual compute nodes into a logical
unit based on attributes such as the hardware or performance characteristics.
[0060] The network function [308] is at least one of a virtualized infrastructure
25 manager (VIM) and network function virtualized infrastructure monitoring
manager (NFVIM). The VIM operates within the MANO (Management and
Orchestration) architecture [100] as shown in FIG. 1. The VIM is responsible for
controlling and managing the compute, storage and network resources. The NFVIM
distributes all alerts or events to specific microservices. The NFVIM monitors the
30 infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the
VNF.
19
[0061] The authentication unit [304] is configured to validate the received request
for performing action by the network function [308]. To validate, the NFVIM or
the VIM may check the request against a predefined criteria to ensure the incoming
5 request is correct and complete. In one implementation, the criteria is related to
check validity of incoming data in the request. In one example, after validation, the
NFVIM or the VIM triggers an ansible script to validate the request. The ansible
script refers to a mode of execution to validate the request.
10 [0062] The transceiver unit [302] is further configured to receive, a success
response, through the MP [504], from the network function after performing the
action. The success response includes but may not be limited to an
acknowledgement of a successful validation. The response may be one of a success
response or an unsuccess response. The success response refers to the request
15 matching with the predefined criteria, and the unsuccess response refers to the
request not matching with the predefined criteria.
[0063] The transceiver unit [302] is further configured to send a notification related
to a resource managing action response, through the MP, to a physical and virtual
20 inventory manager (PVIM). The PVIM refers to a system to map virtual resources
to corresponding physical resources in real-time. Based on the request and the
success response for the validation, the PVIM may create, read, update or delete the
resources map. In another example, the virtualised inventory manager may create,
read, update or delete the resource map. The transceiver unit [302] facilitates the
25 sending of the request and receiving of the response between the MP and the PVIM
through an IM_OS interface. In one example, the IM_OS interface may further be
used for PVIM management, host aggregate management, VIP pool operations,
volume operation, network list operation and storage pool operation.
30 [0064] The storage unit [306] is configured to store the resource managing status
associated with the resource map, at the PVIM. The storage unit [306] is configured
20
to store the resource managing status, with resource attributes, at the PVIM [508].
The resource managing status may be one of a positive or negative resource
managing status. The positive resource managing status refers to completion of the
request and creation, update or deletion of the one or more resources. If the request
5 is not completed, the negative resource managing status may be stored at the storage
unit [306].
[0065] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
virtual network function (VNF) resources, in accordance with exemplary
10 implementations of the present disclosure is shown. In an implementation the
method [400] is performed by the system [300]. Further, in an implementation, the
system [300] may be present in a server device to implement the features of the
present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
15 [0066] At step [404], the method [400] comprises receiving, by a transceiver unit
[302], a request for managing one or more resources, via a management platform
(MP) from a user interface. The request may be for managing one or more
resources. The request may be for managing one or more resources including but
may not be limited to a physical or virtual of compute, a random-access memory
20 (RAM), a storage and a network resource.
[0067] The MP corresponds to a microservice to facilitate deployment and
management of virtual machines (VMs) between microservices. In an exemplary
embodiment, the MP may be an open stack adapter (OSA). The adaptor in the OSA
25 corresponds to an application programming interface (API) between OpenStack and
other systems. The adaptor enables OpenStack to work with others.
[0068] At step [406], the method [400] comprises transmitting, by the transceiver
unit [302], the request for performing action on the received resource managing
30 request, to a network function. The request to perform the action is transmitted
through the MP. In one example, the action refers to a specific operation requested
21
in context of managing virtual network function (VNF) resources. The action
comprises performing a create, read, update, or delete (CRUD) operations on host
aggregate, volume storage, storage pool or network through an interface designed
for host aggregate management. The host aggregate corresponds to a grouping of
5 the physical and virtual compute nodes into a logical unit based on attributes such
as the hardware or performance characteristics.
[0069] The network function [308] is at least one of a virtualized infrastructure
manager (VIM) and network function virtualized infrastructure monitoring
10 manager (NFVIM). The VIM operates within the MANO (Management and
Orchestration) architecture [100] as shown in FIG. 1. The VIM handles activities
associated with the NFV, including resource management and operations
management. The NFVIM performs functions similar to the VIM, which is
configured to manage resources and operations in the VNF.
15
[0070] Further at step [408], the method [400] comprises validating, by an
authentication unit [304], the received request for performing action by the network
function. To validate, the NFVIM or the VIM may check the request against a
predefined criteria to ensure the incoming request is correct and complete. In one
20 implementation, the criteria may be related to check validity of incoming data in
the request. In one example, for validation, the NFVIM or the VIM triggers an
ansible script to validate the request. The ansible script refers to a mode of execution
to validate the request.
25 [0071] Further, at step [410], the method [400] comprises receiving, by the
transceiver unit [302], a success response, through the MP, from the network
function after performing the action based on the request. The success response
includes but may not be limited to an acknowledgement of a successful validation.
The response may be one of a success response or an unsuccess response. The
30 success response refers to the request matching with the predefined criteria, and the
unsuccess response refers to the request not matching with the predefined criteria.
22
[0072] Next at step [412], if the response is the success response, the method [400]
comprises sending, by the transceiver unit [302], a notification related to a resource
managing action response, over an interface through the MP [504], to a physical
5 and virtual inventory manager (PVIM). Based on the request and the success
response for the validation, the PVIM may create, read, update or delete the
resources. The transceiver unit [302] facilitates the sending of the request and
receiving of the response between the PM and the PVIM through an IM_OS
interface. In one example, the IM_OS interface may further be used for PVIM
10 management, host aggregate management, VIP pool operations, volume operation,
network list operation and storage pool operation.
[0073] Next at step [414], the method [400] comprises storing, by a storage unit
[306], the resource managing status, at the PVIM.
15
[0074] The method [400] terminates at step [416].
[0075] Referring to FIG. 5, an implementation of system [500] for managing virtual
network function (VNF) resources, in accordance with exemplary implementations
20 of the present disclosure is shown.
[0076] The implementation system [500] comprises a network function [502], a
management platform (MP) [504], a user interface (UI) [506], an inventory
manager_open stack (IM_OS) interface [512], a physical and virtual inventory
25 manager (PVIM) server [508] and a database (DB) [510].
[0077] The UI [506] refers to a system to interact with the implementation system
[500] by a user. The user may be a system operator, a network consumer, and the
like. The UI [506] may be one of a graphical user interface (GUI), a command line
30 interface, and the like. The GUI refers to an interface to interact with the
implementation system [500] by the user by visual or graphical representation of
23
icons, menu, etc. The GUI is an interface that may be used within a smartphone,
laptop, computer, etc. The CLI refers to a text-based interface to interact with the
implementation system [500] as by the user. The user may input text lines called as
command lines in the CLI to access the data in the implementation system [500].
5 The UI [506] sends the request for managing the one or more resources to the MP
[504].
[0078] The MP [504] refers to a component to facilitate interaction between the
VNF and the PVIM server [508]. In one implementation of the present disclosure,
10 the MP [504] may be an open stack adapter (OSA). The OSA allows to manage
deployment, scaling, monitoring, and termination of service at the VNF. The MP
[504] is configured to forward the request received from the UI [506] to the network
function [502] to validate the request. Once the MP [504] receives a success
response for validation, the MP [504] is configured to send the request for creation,
15 updating or deletion of the status or information associated with at least one of
storage pool, volume or Virtual IP pool to the PVIM [508].
[0079] The network function [502] refers to a system to perform a specific function.
In one example, the network function [502] may be a microservice (MS). The one
20 or more microservice handles requests related to a specific function. In an
implementation of the present disclosure, the network function [502] is configured
to validate the request. To validate, the network function [502] may check the
request against a predefined criteria to ensure the incoming request is correct and
complete. In one example, for validation, the network function [502] triggers an
25 ansible script to validate the request. The ansible script refers to a mode of execution
to validate the request. Based on the validation, a response is sent to the MP [504].
The response may be one of a success response or an unsuccess response. The
success response refers to the request matching with the predefined criteria, and the
unsuccess response refers to the request not matching with the predefined criteria.
30
24
[0080] The IM_OS interface [512] is a communication link between the MP [504]
and the PVIM [508]. The IM_OS interface [512] facilitates sending of the request
and receiving of the response between the MP [504] and the PVIM [508] through
the IM_OS interface [512]. In one example, the IM_OS interface [512] may further
5 be used for management of the PVIM [508], host aggregate management, VIP pool
operations, volume operation, network list operation and storage pool operation.
[0081] The PVIM [508] refers to a system to maintain real-time mapping of virtual
resources to a physical resource corresponding to the virtual resource. The PVIM
10 [508] maintains state and attributes. The states may be one of a resource allocation
by monitoring the one or more resources, health monitoring of one or more physical
and virtual of resources, and the like. The attributes may be one of maintaining
configuration details, monitoring performance metrics of the one or more physical
and virtual of resources, enforcing security policies, and the like. Further, the PVIM
15 [508] uses a graph database model. The graph database model refers to a model to
analyse or visualize the VNF. In an implementation of the present disclosure, the
PVIM [508] may perform one of a create/read/update/delete based on the request
on the one or more resources.
20 [0082] The database [510] is configured to interact with the PVIM [508]. The
PVIM [508] stores the status of the create/read/update/delete of the one or more
resources at the database [510]. In an implementation of the present disclosure, the
database [510] stores the status in real-time.
25 [0083] FIG. 6 illustrates an implementation of the method flow [600] for storage
pool creation for managing virtual network function (VNF) resources, in
accordance with exemplary implementations of the present disclosure.
[0084] At step [602], the UI [506] may send the request for storage pool creation
30 to the MP [504]. In an implementation of the present disclosure, the MP [504] may
25
be the OSA. The storage pool creation refers to setting up a group of storage
resources to be allocated to manage storage in the VNF.
[0085] At step [604], the MP [504] forwards the request to the network function
5 (microservice) [502]. In an implementation of the present disclosure, the
microservice (MS) [502] is the network function virtualization infrastructure
monitoring manager (NFVIM).
[0086] At step [606], the MS [502] validates the incoming request and executes
10 ansible script and sends an acknowledgment to the MP [504]. To validate, the MS
[502] may check the incoming request against a predefined criteria to ensure the
incoming request is correct and complete. The predefined criteria may be defined
by a user, where the user may be a system operator or a network operator. In one
example, after validation, the MS [502] triggers the ansible script. The ansible script
15 refers to a mode of execution to validate the request.
[0087] Further at step [608], the MP [504] notifies the PVIM [508] regarding
successful creation of the storage pool based on the request from the UI [506]. The
MP [504] sends the notification via the IM_OS interface [512]. The PVIM [508]
20 stores the status corresponding to successful creation of the storage pool based on
the information in the request.
[0088] At step [610], the PVIM [508] updates the status of the created storage pool
in the database (DB) [510].
25
[0089] FIG. 7 illustrates an implementation of the method flow [700] for volume
creation for managing virtual network function (VNF) resources, in accordance
with exemplary implementations of the present disclosure.
30 [0090] At step [702], the UI [506] may send the request for volume creation to the
MP [504]. In an implementation of the present disclosure, the MP [504] may be the
26
OSA. The volume creation refers to allocating storage resources to the VNF to
ensure it has the necessary capacity to perform its functions.
[0091] At step [704], the MP [504] forwards the request to the MS [502]. In an
5 implementation of the present disclosure, the MS [502] is the VIM.
[0092] At step [706], the VIM creates the volume storage and sends a success
response to the MP [504]. The success response corresponds to successful creation
of the volume at the VIM.
10
[0093] Further at step [708], the OSA [504] notifies the PVIM [508] about creation
of the volume storage based on the request from the UI [506]. The MP [504] sends
the notification via the IM_OS interface [512].
15 [0094] At step [710], the PVIM [508] updates the status of the created volume
storage in the database (DB) [510].
[0095] The present disclosure further discloses a non-transitory computer readable
storage medium, storing instructions for managing virtual network function (VNF)
20 resources, the instructions include executable code which, when executed by one
or more units of a system, cause a transceiver unit [302] to receive a request for
managing one or more resources, through a management platform (MP) [504], from
a user interface [506]. The instructions when executed by the system further cause
the transceiver unit [302] to transmit a request for performing action on the received
25 resource managing request, to a network function [502], through the MP [504]. The
instructions when executed by the system further cause an authentication unit [304]
to validate the received request for performing action by the network function [502].
The instructions when executed by the system further cause the transceiver unit
[302] to receive, a response, through the MP [504], from the network function [502]
30 after performing the action. The instructions when executed by the system further
cause the transceiver unit [302] to send a resource managing action response,
27
through the MP [504], to a physical and virtual inventory manager (PVIM) [508].
The instructions when executed by the system further cause a storage unit [306] to
store the resource managing status, at the PVIM [508].
5 [0096] As is evident from the above, the present disclosure provides a technically
advanced solution for managing virtual network function (VNF) resources. The
present solution provides a system and method for creating and managing VNF
resources via IM_OS interface. Further, the invention provides, Notification for
Addition of new VIM Site to Inventory sends via the interface only. The present
10 disclosure further helps in VNF instantiation process by getting volume, storage
pool, Network and Host Aggregate information. Further, the present disclosure
enables the MP to mount drives to VNF servers to scale storage. The present
disclosure further provides VIP Pool creation and deletion request to IM by the
IM_OS interface.
15
[0097] 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
20 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.
[0098] Further, in accordance with the present disclosure, it is to be acknowledged
25 that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
30 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
28
functionality described herein, are considered to be encompassed within the scope
of the present disclosure
29
We Claim:
1. A method [400] for managing virtual network function (VNF) resource(s),
the method [400] comprising:
5 - receiving, by a transceiver unit [302], a request for managing one or
more resources, via a management platform (MP) [504] from a user
interface [506];
- transmitting, by the transceiver unit [302], a request for performing
action on the received resource managing request, to a network function
10 [502] through the MP [504];
- validating, by an authentication unit [304], the received request for
performing action by the network function [502];
- receiving, by the transceiver unit [302], a success response, through the
MP, from the network function [308] after performing the action based
15 on the request;
- sending, by the transceiver unit [302], a notification related to a resource
managing action response, over an interface through the MP [504], to a
physical and virtual inventory manager (PVIM) [508]; and
- storing, by a storage unit [306], the resource managing status, at the
20 PVIM [508].
2. The method [400] as claimed in claim 1, wherein the resource managing
request involves at least one of: creating and configuring the one or more
resources.
25
3. The method [400] as claimed in claim 1, wherein the network function [308]
is at least one of: a virtualized infrastructure manager (VIM) and network
function virtualized infrastructure monitoring manager (NFVIM).
30 4. The method [400] as claimed in claim 1, wherein the one or more resources
comprises physical or virtual of compute, RAM, storage, network resource.
30
5. The method [400] as claimed in claim 1, wherein at least one of: the sending
of the request and the receiving of the response between the MP [504] and
the PVIM [508] is via an IM_OS interface [602].
5
6. The method [400] as claimed in claim 1, wherein sending the notification
related to the resource managing action response is performed by the
transceiver unit [302], through the MP [504], for the performed action to the
PVIM [508].
10
7. The method [400] as claimed in claim 1, further comprising: sending, by the
transceiver unit [302], a request for creating or deleting a virtual IP (VIP)
pool to the physical and virtual inventory manager (PVIM) [508] through
the MP [504].
15
8. The method [400] as claimed in claim 1, wherein the resource managing
request comprises performing create, read, update, or delete (CRUD)
operations on host aggregate through the interface designed for host
aggregate management.
20
9. The method [400] as claimed in claim 1, wherein storing, by the storage unit
[306], the resource managing status, with resources attributes, at the PVIM
[508].
25 10. A system [300] for managing virtual network function (VNF) resource(s),
the system [300] comprising:
o a transceiver unit [302] configured to receive a request for managing
one or more resources, through an open stack adaptor (MP) [504],
30 from a user interface [506];
31
o the transceiver unit [302] is further configured to transmit a request
for performing action on the received resource managing request, to
a network function [308], through the MP [504];
o an authentication unit [304] connected to at least the transceiver unit
5 [302], the authentication unit [304] configured to validate the
received request for performing action by the network function
[308];
o the transceiver unit [302] is further configured to receive, a response,
through the MP [504], from the network function [308] after
10 performing the action based on the request;
o the transceiver unit [302] is further configured to send a notification
related to resource managing action response, through the MP [504],
to a physical and virtual inventory manager (PVIM) [508]; and
o a storage unit [306] connected to at least the authentication unit
15 [304], the storage unit [306] configured to store the resource
managing status, at the PVIM [508].
11. The system [300] as claimed in claim 10, wherein the resource managing
request involves at least one of: creating and configuring the one or more
20 resources.
12. The system [300] as claimed in claim 10, wherein the network function
[308] is at least one of: a virtualized infrastructure manager (VIM) and
network function virtualized infrastructure monitoring manager (NFVIM).
25
13. The system [300] as claimed in claim 10, wherein the one or more resources
comprises physical or virtual of compute, RAM, storage, network resource.
14. The system [300] as claimed in claim 10, wherein the transceiver unit [302]
30 facilitates the sending of the request and receiving of the response between
the MP [504] and the PVIM [508] through an IM_OS interface [512].
32
15. The system [430] as claimed in claim 10, wherein the transceiver unit [301]
is configured to send a request for creating or deleting a virtual IP (VIP)
pool to the physical and virtual inventory manager (PVIM) [508] through
5 the MP [504].
16. The system [300] as claimed in claim 10, wherein the resource managing
request comprises performing create, read, update, or delete (CRUD)
operations on host aggregate through the interface designed for host
10 aggregate management.
17. The system [300] as claimed in claim 10, wherein the transceiver unit [302]
is configured to send the notification related to the resource managing action
response is performed, through the MP [504], for the performed action to
15 the PVIM [508].
18. The system [300] as claimed in claim 10, wherein the storage unit [306] is
configured to store the resource managing status, with resources attributes,
at the PVIM [508].