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 OPERATIONS
IN A HIGH AVAILABILITY 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 MANAGING OPERATIONS IN A HIGH
AVAILABILITY NETWORK
FIELD OF DISCLOSURE
5
[0001] Embodiments of the present disclosure generally relate to network
performance management systems. More particularly, embodiments of the present
disclosure relate to managing operations in a high availability 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
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] A network function virtualization (NFV) and software defined network
20 (SDN) platform has been designed and developed to be the common platform of
network for offering emerging new technologies and differentiating on-demand
services. The platform overcomes the need of manual changes required in the
network to launch new services by exploiting the NFV and SDN features. The NFV
and SDN platform provides Management and Orchestration (MANO) functionality
25 across multi-site and multi-Virtual Infrastructure Manager (VIM) environment for
life cycle management (LCM) operation of VNFs provided by different vendors.
The platform has UI/UX interface which helps the user to on-board VNF, design
Network Service Chain, define VNF auto scaling and healing policies, instantiate
Network Service and VNFs as well as manage the VIM site. It also allows the user
30 to create storage volume pools, availability zones and define host aggregates.
3
[0004] The NFV SDN Platform is based on microservice (MS) architecture. The
microservices have specific task and functionality to perform. The MSs work
collectively to achieve the overall functionality of the NFV SDN platform. Each
MS has exposed certain APIs which are called by other micro services. A VNF
5 generally has the following stages:
• Design
• Deployment Planning
• Instantiation
• Operation
10 • Maintenance and DevOps.
[0005] Further, inventory management service (IM) maintains the virtual inventory
and limited physical inventory. It maintains relation between physical and virtual
resources (w.r.t overlay). Also, it describes physical and virtual resources w.r.t
15 different attributes using updates from external micro-service. Thus, its data
accuracy depends on the micro-services which create, update, delete these resources
and at the same time update these events with inventory manager IM). Other
services can query IM relations, attributes etc. using Query APIs provided by IM.
The Inventory Management Service stores data in Doc based NoSQL database (DB)
20 and Graph database (DB), where NoSQL DB is running in cluster mode which is
also used by other services. However, the Graph database in cluster mode requires
more number of servers to host database. Also, the Graph database in cluster mode
makes the system slow. Also. any changes in graph of one inventory instance does
not reflect in other instances of the inventory.
25
[0006] Thus, there exists an imperative need in the art for syncing a chaining
information of CNF/VNF and corresponding data between multiple instances.
SUMMARY
30
4
[0007] 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.
5
[0008] An aspect of the present disclosure may relate to a method for managing
operations in a high availability network. The method comprises receiving, by a
transceiver unit, a request to perform an operation on at least a database associated
with a node. Further, the method comprises performing, by a processing unit, a
10 validity check of the received request. Furthermore, the method comprises
performing, by the processing unit, in response to a positive validity check of the
received request, the operation on at least the database associated with the node.
Hereinafter the method comprises transmitting, by the transceiver unit, to at least a
cluster database, a set of details relating to the operation on at least the database
15 associated with the node. The method further comprises transmitting, by the
transceiver unit, to one or more nodes in a cluster, communicably coupled with at
least the database, a broadcast request relating to the operation on at least a database
associated with the one or more nodes in the cluster, and a request to update
respective databases associated with the one or more nodes. The method further
20 comprises receiving, by the transceiver unit, from the one or more nodes, an
acknowledgement message related to receipt, by the one or more nodes, of the
broadcast request.
[0009] In an exemplary aspect of the present disclosure, the request to perform the
25 operation is received from one or more network functions.
[0010] In an exemplary aspect of the present disclosure, the database associated
with the node corresponds to a graph. The operation on at least the graph comprises
at least one of additions to at least the graph, deletions in at least the graph,
30 modifications to at least the graph, and combinations thereof.
5
[0011] In an exemplary aspect of the present disclosure, the method comprises
storing, by the processing unit, in a cluster database, and in response to the positive
validity check of the received request, a received message associated with the
request. The received message is stored in the cluster database in a predefined
5 format and with a label associating the received message with at least the database
associated with the node.
[0012] In an exemplary aspect of the present disclosure, the predefined format
comprises Java Script Object Notation (JSON).
10
[0013] In an exemplary aspect of the present disclosure, the method comprises
storing, by the processing unit, on databases associated with the one or more nodes,
the received broadcast request.
15 [0014] In an exemplary aspect of the present disclosure, the method comprises
performing, by the processing unit, the operation on at least the database associated
with the node, based on the received broadcast request.
[0015] In an exemplary aspect of the present disclosure, the operation on at least
20 the database associated with the node, as received in the broadcast request, is
performed on the cluster database.
[0016] In an exemplary aspect of the present disclosure, the method further
comprises updating, by the processing unit, the cluster database to reflect that one
25 or more node associated with the graphs are updated.
[0017] In an exemplary aspect of the present disclosure, the cluster database is a
NoSQL database.
30 [0018] Another aspect of the present disclosure may relate to a system for
managing operations in a high availability network. The system comprises a
6
transceiver unit configured to receive a request to perform an operation on at least
a database associated with a node. Further, a processing unit is further configured
to perform a validity check of the received request. The processing unit is further
configured to perform, in response to a positive validity check of the received
5 request, the operation on at least the database associated with the node. Further, the
transceiver unit is configured to transmit, to one or more nodes in a cluster,
communicably coupled with at least the database, a broadcast request relating to the
operation on at least the database associated with the node, and a request to update
respective databases associated with the one or more nodes. Furthermore, the
10 transceiver unit is configured to receive, from the one or more nodes, an
acknowledgement message related to receipt, by the one or more nodes, of the
broadcast request.
[0019] Yet another aspect of the present disclosure may relate to a non-transitory
15 computer readable storage medium, storing instructions for managing operations in
a high availability network, the instructions include executable code which, when
executed by one or more units of a system cause a transceiver unit to receive a
request to perform an operation on at least a database associated with a node. The
instructions when executed by the system further cause a processing unit to perform
20 a validity check of the received request. The instructions when executed by the
system further cause the processing unit to perform, in response to a positive
validity check of the received request, the operation on at least the database
associated with the node. The instructions when executed by the system further
cause the transceiver unit to transmit, to one or more nodes in a cluster,
25 communicably coupled with at least the database, a broadcast request relating to the
operation on at least the database associated with the node, and a request to update
respective databases associated with the one or more nodes. The instructions when
executed by the system further cause the transceiver unit to receive, from the one
or more nodes, an acknowledgement message related to receipt, by the one or more
30 nodes, of the broadcast request.
7
OBJECTS OF THE INVENTION
[0020] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
5
[0021] It is an object of the present disclosure to provide a system and a method for
syncing a chaining information of CNF/VNF and corresponding data between
multiple instances using broadcasting services.
10 [0022] It is another object of the present disclosure to provide a solution to
eliminate the need of extra servers required for running Graph database, the present
solution runs with the application itself.
[0023] It is yet another object of the present disclosure to provide a Graph database
15 in embedded mode to enhance the performance and make the system faster.
DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute
20 a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the figures are not to be construed as
25 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
30
8
[0025] 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 [0026] 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.
[0027] FIG. 3 illustrates an exemplary block diagram of a system for managing
10 operations in a high availability network, in accordance with exemplary
implementations of the present disclosure.
[0028] FIG. 4 illustrates an implementation of the system for managing operations
in a high availability network, in accordance with exemplary implementations of
15 the present disclosure.
[0029] FIG. 5 illustrates a method flow diagram for managing operations in a high
availability network, in accordance with exemplary implementations of the present
disclosure.
20
[0030] FIG. 6 illustrates an implementation of the method for managing operations
in a high availability network, in accordance with exemplary implementations of
the present disclosure.
25 [0031] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
30 [0032] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
9
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
5 address any of the problems discussed above or might address only some of the
problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
10 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.
15
[0034] 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
20 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0035] 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
25 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.
30
10
[0036] 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
5 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
10 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0037] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
15 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
20 integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
25 [0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
30 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
11
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 at least one of
a transceiver unit, a processing unit, a storage unit, a detection unit and any other
5 such unit(s) which are required to implement the features of the present disclosure.
[0039] 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
10 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
that may be required by one or more units of the system to perform their respective
functions.
15
[0040] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
20 each other, which also includes the methods, functions, or procedures that may be
called.
[0041] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
25 general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
30
12
[0042] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
and/or connected with the system.
5
[0043] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the abovementioned and other existing problems in this field of technology by providing
method and system of managing operations in a high availability network.
10
[0044] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture/ platform [100], in
accordance with exemplary implementation of the present disclosure. The MANO
architecture [100] is developed for managing telecom cloud infrastructure
15 automatically, managing design or deployment design, managing instantiation of
network node(s)/ service(s) etc. The MANO architecture [100] deploys the network
node(s) in the form of Virtual Network Function (VNF) and Cloud-native/
Container Network Function (CNF). The system may comprise one or more
components of the MANO architecture [100]. The MANO architecture [100] is
20 used to auto-instantiate the VNFs into the corresponding environment of the present
disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to
the platform.
[0045] As shown in FIG. 1, the MANO architecture [100] comprises a user
25 interface layer, a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platforms foundation services
module [106], a platform core services module [108] and a platform resource
adapters and utilities module [112]. All the components are assumed to be
connected to each other in a manner as obvious to the person skilled in the art for
30 implementing features of the present disclosure.
13
[0046] The NFV and SDN design function module [104] comprises a VNF
lifecycle manager (compute) [1042], a VNF catalogue [1044], a network services
catalogue [1046], a network slicing and service chaining manager [1048], a physical
and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF
5 lifecycle manager (compute) [1042] is responsible for deciding on which server of
the communication network, the microservice will be instantiated. The VNF
lifecycle manager (compute) [1042] may manage the overall flow of incoming/
outgoing requests during interaction with the user. The VNF lifecycle manager
(compute) [1042] is responsible for determining which sequence to be followed for
10 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 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
15 [1048] manages the slicing (an ordered and connected sequence of network service/
network functions (NFs)) that must be applied to a specific networked data packet.
The physical and virtual resource manager [1050] stores the logical and physical
inventory of the VNFs. Just like the VNF lifecycle manager (compute) [1042], the
CNF lifecycle manager [1052] is used for the CNFs lifecycle management.
20
[0047] The platforms foundation services module [106] comprises a microservices
elastic load balancer [1062], an identify & access manager [1064], a command line
interface (CLI) [1066], a central logging manager [1068], and an event routing
manager [1070]. The microservices elastic load balancer [1062] is used for
25 maintaining the load balancing of the request for the services. The identify & access
manager [1064] is used for logging purposes. The command line interface (CLI)
[1066] is used to provide commands to execute certain processes which requires
changes during the run time. The central logging manager [1068] is responsible for
keeping the logs of every service. These logs are generated by the MANO platform
30 [100]. These logs are used for debugging purposes. The event routing manager
14
[1070] is responsible for routing the events i.e., the application programming
interface (API) hits to the corresponding services.
[0048] The platforms core services module [108] comprises NFV infrastructure
5 monitoring manager [1082], an assure manager [1084], a performance manager
[1086], a policy execution engine [1088], a capacity monitoring manager [1090], a
release management (mgmt.) repository [1092], a configuration manager & GCT
[1094], an NFV platform decision analytics [1096], a platform NoSQL DB [1098];
a platform schedulers and cron jobs [1100], a VNF backup & upgrade manager
10 [1102], a micro service auditor [1104], and a platform operations, administration
and maintenance manager [1106]. The NFV infrastructure monitoring manager
[1082] monitors the infrastructure part of the NFs. For e.g., any metrics such as
CPU utilization by the VNF. The assure manager [1084] is responsible for
supervising the alarms the vendor is generating. The performance manager [1086]
15 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
PEGN [1090]. The release management (mgmt.) repository (RMR) [1092] is
responsible for managing the releases and the images of all the vendor network
20 node. The configuration manager & (GCT) [1094] manages the configuration and
GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps
in deciding the priority of using the network resources. It is further noted that the
policy execution engine (PEGN) [1088], the configuration manager & GCT [1094]
and the NPDA [1096] work together. The platform NoSQL DB [1098] is a database
25 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
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
30 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
15
architecture [100] using the network resources then the micro service auditor [1104]
audits and informs the same so that resources can be released for services running
in the MANO architecture [100], thereby assuring the services only run on the
MANO platform [100]. The platform operations, administration and maintenance
5 manager [1106] is used for newer instances that are spawning.
[0049] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122]; a generic decoder and indexer
(XML, CSV, JSON) [1124]; a docker service adaptor [1126]; an OpenStack API
10 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
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
15 provided between the telecom cloud and the MANO architecture [100] for
communication. The OpenStack API adapter [1128] is used to connect with the
virtual machines (VMs). The NFV gateway [1130] is responsible for providing the
path to each service going to/incoming from the MANO architecture [100].
20 [0050] 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
managing operations in a high availability network, utilising the system. In another
25 implementation, the computing device [200] itself implements the method using
one or for managing operations in a high availability network, 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 [0051] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
16
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
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]
5 for storing information and instructions to be executed by the processor [204]. The
main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special10 purpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
15 [0052] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
20 displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as
a mouse, a trackball, or cursor direction keys, for communicating direction
25 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
30 [0053] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
17
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
5 sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
10 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0054] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two15 way data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] may be a
20 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
25
[0055] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
30 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,
18
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0056] The present disclosure is implemented by a system [300] (as shown in FIG.
5 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).
[0057] Referring to FIG. 3, an exemplary block diagram of a system [300] for
10 managing operations in a high availability network is shown, in accordance with
the exemplary implementations of the present disclosure. The system [300]
comprises at least one transceiver unit [302] and at least one processing unit [304].
Also, all 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
15 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 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
20 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 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
25 device.
[0058] The system [300] is configured for managing operations in a high
availability network, with the help of the interconnection between the
components/units of the system [300].
30
19
[0059] The transceiver unit [302] is configured to receive a request to perform an
operation on at least a database [306] associated with a node. The database [306]
associated with the node corresponds to a graph. The graph database is based on
graph theory. The data is stored in the nodes of the graph and the relationship
5 between the data are represented by the edges between the nodes. In one example,
a user may be able to select the node from a dropdown via a user interface (UI).
The user may be one of a system operator and a network operator. In an example,
on selecting the node, the node becomes the central node, and first level relationship
associated with the selected node may be displayed to the user by the system [300].
10
[0060] The request to perform the operation is received from one or more
microservices. In one example, the one or more microservices includes but may not
be limited to the NFV SDN design function module [104], the platforms foundation
module [106], the platform core services module [108] and the platform resource
15 adapters and utilities module [112] (as depicted in FIG. 1). The request may be for
performing the operation comprising at least one of additions to at least the graph,
deletions in at least the graph, modifications to at least the graph, and combinations
thereof. In one example, the request may be for a node identifier (for instance, the
node identifier is “11097”) to identify the node. In addition, the request may be an
20 operation, for instance, update the graph), and the like.
[0061] The processing unit [304] is configured to perform a validity check of the
received request. The validity check refers to ensuring that the message in received
request is complete and adhere to the predefined format and the label. To perform
25 the validity check, the processing unit [304] may check if the received message
associated with the request includes the node identifier, the operation, and other
required fields. Further, the processing unit [304] may determine if the received
message is in the predefined format. The validity check may be one of a positive
validity check and a negative validity check. The positive validity check refers to
30 when the received message associated with the request is complete and adheres to
20
predefined format rules. The negative validity check refers to when the received
request may not be complete and may not adhere to predefined format rules.
[0062] Further, based on the positive validity check of the received request, the
5 processing unit [304] is configured to perform the operation on at least the database
[306] associated with the node. In an exemplary embodiment, the user may view a
first database from a dropdown on the user interface (UI) to visualize a cluster
database [308]. The cluster database [308] may be implemented as a NoSQL
database. On selecting a first node of the database, the first node becomes a central
10 node of the system [300]. In one example, the user may be able to view any of the
database to see the properties associated with the each of the database [306]. For
instance, if the operation to be performed is the addition to the graph, the processing
unit [304] may add data to the graph. In one example, the transceiver unit [302]
may update or inform a cluster database [308] on completion of the addition in the
15 graph at the database.
[0063] The transceiver unit [302] is further configured to transmit to at least the
cluster database, a set of details relating to the operation on at least the database
[306] associated with the node. The database [306] may be an embedded database.
20 The set of details includes but may not be limited a label associated with a message
in the received request, in a predefined format. The predefined format comprises
Java Script Object Notation (JSON). The JSON refers to a data interchange format
easy to read and write, and easy for the system [300] to parse and generate. The
label refers to a type of the request- if it is the addition to the graph, the deletion to
25 the graph or the modification request.
[0064] The processing unit [304] is configured to store the received message
associated with the request, in response to the positive validity check of the received
request. The received message is stored in the cluster database [308]. The cluster
30 database [308] is the NoSQL database. The NoSQL database refers to a non-
21
relational database. The non-relational database stores data in a non-tabular form
and is more flexible than a traditional, SQL-based database structure.
[0065] The transceiver unit [302] is further configured to transmit, to one or more
5 nodes in a cluster, a broadcast request relating to the operation on at least the
database associated with the node, and a request to update respective databases
associated with the one or more nodes. The broadcast request refers to a request
sent to all nodes in the cluster. The broadcast request includes but may not be
limited to the set of data that need to be processed by each node of the one or more
10 nodes. The broadcast request ensures that all nodes in the cluster database [308]
perform a specific operation or update their respective databases based on the
operation in the request.
[0066] The one or more nodes in a cluster are communicably coupled with at least
15 the database [306]. Each of the one or more nodes in the cluster are configured to
handle the broadcast request to ensure that the system remains [300] operational
even if one of the one or more nodes fails. The processing unit [304] is configured
to store, on the database [306] associated with the one or more nodes, the received
broadcast request.
20
[0067] The transceiver unit [302] is further configured to receive, from the one or
more nodes, an acknowledgement message by the one or more nodes of the
broadcast request. The acknowledgment message may be related to the related to
confirmation or receipt of the broadcast message. The processing unit [304] is
25 configured to perform the operation on at least the database [306] associated with
the node, based on the received broadcast request. The operation on at least the
database [302] associated with the node, as received in the broadcast request, is
performed on the cluster database [308]. The transceiver unit [302] is configured to
update the cluster database [308] to reflect that one or more databases associated
30 with the graphs are updated.
22
[0068] Further, the node may send back a response to the one or more microservices
based on the request to inform of the update to the one or more nodes.
[0069] Referring to FIG. 4, an implementation of the system [400] for managing
5 operations in a high availability network, in accordance with exemplary
implementations of the present disclosure is shown.
[0070] The system [400] comprises one or more network functions [402], a cluster
database [404], a first physical and virtual infrastructure manager (first PVIM)
10 [406], a second PVIM [408], a third PVIM [410], a first graph database [412], a
second graph database [414] and a third graph database [416]. The PVIM is
exemplary – It can be any node as mentioned in FIG. 1, for syncing data between
instances of the node. Also, all of the components/ units of the implementation
system [400] are assumed to be connected to each other unless otherwise indicated
15 below. As shown in the FIG., all units shown within the system should also be
assumed to be connected to each other. Also, in FIG. 4 only a few units are shown,
however, the implementation system [400] may comprise multiple such units or the
system [400] may comprise any such numbers of said units, as required to
implement the features of the present disclosure. The implementation of the system
20 [400] is further explained in one or more steps.
[0071] At step 1, the one or more network functions [402] send the request to the
first PVIM [406]. The one or more network functions [402] may be any
microservice. The cluster database [404] is similar to the cluster database [308] of
25 FIG. 3.
[0072] The request is to perform an operation on the database [306] associated with
a node. The operation includes but may not be limited to make additions to at least
the graph, deletions in at least the graph, modifications to at least the graph, and
30 combinations thereof.
23
[0073] The first PVIM [406] is communicably coupled to at least the first graph
database [412]. Based on the received request, the first PVIM [406] performs the
operation of addition, modification or deletion to the graph. The updated graph may
be stored in the first graph database [412].
5
[0074] Further, at step 2, the first PVIM [406] may send the update in the graph
that is stored in the first graph database [412], to a cluster database (NoSQL) [404].
[0075] Further, at step 3, the first PVIM [406] is configured to send the broadcast
10 request to the second PVIM [408] and the third PVIM [410]. Based on the received
broadcast request, the second PVIM [408] and the third PVIM [410], at step 4,
updates the respective databases, i.e., the second graph database [414] and the third
graph database [416].
15 [0076] The second PVIM [408] and the third PVIM [410] are configured to send
the update in the graph to the cluster database [404].
[0077] At step 5, based on the update in the first PVIM [406], the second PVIM
[408] and the third PVIM [410], the first PVIM [406] may send a response of update
20 or execution of the request to the one or more network functions [402].
[0078] Referring to FIG. 5, an exemplary method flow diagram [500] for managing
operations in a high availability network, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
25 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] starts at step [502].
[0079] At step [504], the method comprises receiving, by a transceiver unit [302],
30 a request to perform an operation on at least a database associated with a node. The
database associated with the node corresponds to a graph. In one example, the node
24
refers to an instance of the database. In an implementation of the present disclosure,
the nodes combine to form the database.
[0080] The request to perform the operation is received from one or more
5 microservices. In one example, the one or more microservices includes but may not
be limited to the NFV SDN design function module [104], the platforms foundation
module [106], the platform core services module [108] and the platform resource
adapters and utilities module [112]. The request may be for performing the
operation comprising at least one of additions to at least the graph, deletions in at
10 least the graph, modifications to at least the graph, and combinations thereof. In one
example, the request includes but may not be limited to a node identifier (for
instance, the node identifier is “11097”) to identify the node, an operation (for
instance- update the graph), and the like.
15 [0081] At step [506], the method comprises performing, by a processing unit [304],
a validity check of the received request. The validity check refers to ensuring that
the message in received request is complete and adhere to the predefined format
and the label. The process of performing the validity check includes checking, the
processing unit [304], if the received message associated with the request includes
20 the node identifier, the operation, and other required fields. Further, the processing
unit [304] may determine if the received message is in the predefined format. The
validity check may be one of a positive validity check and a negative validity check.
The positive validity check refers to when the received message associated with the
request is complete and adheres to predefined format rules. The negative validity
25 check refers to when the received request may not be complete and may not adhere
to predefined format rules.
[0082] Next at step [508], the method comprises performing, by the processing unit
[304], in response to a positive validity check of the received request, the operation
30 on at least the database associated with the node. For instance, if the operation to
be performed is the addition to the graph, data may be added to the graph by the
25
processing unit [304]. In one example, the transceiver unit [302] may update or
inform the cluster database on completion of the addition in the graph at the
database.
5 [0083] Further at step [510], the method comprises transmitting, by the transceiver
unit [302], to at least a cluster database, a set of details relating to the operation on
at least the database associated with the node. The set of details includes but may
not be limited a predefined format and a label associated with a message in the
received request. The predefined format comprises Java Script Object Notation
10 (JSON). The JSON refers to a data interchange format easy to read and write, and
easy for the system [300] to parse and generate. The label refers to a type of the
request- if it is the addition to the graph, the deletion to the graph or the modification
request.
15 [0084] The method [500] further comprises storing, by the processing unit [304],
in the cluster database, and in response to the positive validity check of the received
request, a received message associated with the request, wherein the received
message is stored in the cluster database in a predefined format and with a label
associating the received message with at least the database associated with the node.
20
[0085] Further at step [512], the method comprises transmitting, by the transceiver
unit [302], to one or more nodes in a cluster, communicably coupled with at least
the database, a broadcast request relating to the operation on at least a database
associated with the one or more nodes in the cluster, and a request to update
25 respective databases associated with the one or more nodes. Each of the one or more
nodes in the cluster are configured to handle the broadcast request to ensure that the
system remains [300] operational even if one of the one or more nodes fails. The
processing unit [304] is configured to store, on databases associated with the one or
more nodes, the received broadcast request.
30
26
[0086] Further at step [514], the method comprises receiving, by the transceiver
unit [302], from the one or more nodes, an acknowledgement message related to
receipt by the one or more nodes of the broadcast request. The processing unit [304]
is configured to perform the operation on at least the database associated with the
5 node, based on the received broadcast request. The operation on at least the database
associated with the node, as received in the broadcast request, is performed on the
cluster database. The transceiver unit [302] is configured to update the cluster
database to reflect that one or more databases associated with the graphs are
updated.
10
[0087] Further, the selected node may send back a response to the one or more
microservices based on the request to inform of the update to the one or more nodes.
[0088] The method terminates at step [516].
15
[0089] Referring to FIG. 6, an implementation of the method [600] for managing
operations in a high availability network, in accordance with exemplary
implementations of the present disclosure, is shown. The method [600] starts at step
[602].
20
[0090] At step [604], the request to perform an operation on the first PVIM [406]
associated with a node is received. The request may be sent from the one or more
microservices [402]. The operation includes but may not be limited to make
additions to at least the graph, deletions in at least the graph, modifications to at
25 least the graph, and combinations thereof.
[0091] At step [606], the validity check may be performed on the request. The
validity check may be one of the positive validity checks and the negative validity
check. If the validity check is the positive validity check, the request may be stored
30 in the cluster database [404].
27
[0092] Further, at step [608], based on the received request, the first PVIM [406]
performs the operation of addition, modification or deletion to the graph.
[0093] At step [610], the updated graph may be stored in the graph database
5 corresponding to the first PVIM [406].
[0094] Further, at step [612], the cluster database [404] may be updated by the first
PVIM [406] of the update in the graph. The cluster database [404] may be
implemented as a NoSQL database.
10
[0095] At step [614], the broadcast request may be sent to the second PVIM [408]
and the third PVIM [410] by the first PVIM [406] to update the graph based on the
graph to ensure that other PVIM remains operational in case the first PVIM [406]
fails. Based on the update, the corresponding databases of the second PVIM [408]
15 and the third PVIM [410] may be updated.
[0096] At step [616], the update may be sent to the cluster database [404] by the
second PVIM [408] and the third PVIM [410] to inform the cluster database [404]
of the update.
20
[0097] Further, at step [618], the response to the request by the one or more
microservices [402] may be sent by the first PVIM [406].
[0098] The method terminates at step [620].
25
[0099] The present disclosure further discloses a non-transitory computer readable
storage medium, storing instructions for managing operations in a high availability
network, 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 to perform
30 an operation on at least a database associated with a node. The instructions when
executed by the system further cause a processing unit [304] to perform a validity
28
check of the received request. The instructions when executed by the system further
cause the processing unit [304] to perform, in response to a positive validity check
of the received request, the operation on at least the database associated with the
node. The instructions when executed by the system further cause the transceiver
5 unit [302] to transmit, to one or more nodes in a cluster, communicably coupled
with at least the database, a broadcast request relating to the operation on at least
the database associated with the node, and a request to update respective databases
associated with the one or more nodes. The instructions when executed by the
system further cause the transceiver unit [302] to receive, from the one or more
10 nodes, an acknowledgement message related to receipt by the one or more nodes of
the broadcast request.
[0100] As is evident from the above, the present disclosure provides a technically
advanced solution for managing operations in a high availability network. The
15 present solution provides a system and a method for syncing a chaining information
of CNF/VNF and corresponding data between multiple instances using
broadcasting services. The present disclosure further provides a solution that
eliminates the need of extra servers required for running Graph database, the present
solution runs with the application itself. The present disclosure provides Graph
20 database in embedded mode to enhance the performance and makes system faster.
[0101] 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
25 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.
30 [0102] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
29
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
5 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
10
30
We Claim:
1. A method for managing operations in a high availability network, the
method comprising:
5
- receiving, by a transceiver unit [302], a request to perform an
operation on at least a database [306] associated with a node;
- performing, by a processing unit [304], a validity check of the
received request;
10 - performing, by the processing unit [304], in response to a positive
validity check of the received request, the operation on at least the
database [306] associated with the node;
- transmitting, by the transceiver unit [302], to at least a cluster database
[308], a set of details relating to the operation on at least the database
15 associated with the node;
- transmitting, by the transceiver unit [302], to one or more nodes in a
cluster, communicably coupled with at least the database [306], a
broadcast request relating to the operation on at least a database
associated with the one or more nodes in the cluster database [308],
20 and a request to update respective databases associated with the one
or more nodes; and
- receiving, by the transceiver unit [302], from the one or more nodes,
an acknowledgement message related to receipt, by the one or more
nodes, of the broadcast request.
25
2. The method as claimed in claim 1, wherein the request to perform the
operation is received from one or more network functions [402].
3. The method as claimed in claim 1, wherein the database [306] associated
30 with the node corresponds to a graph, wherein the operation on at least the
31
graph comprises at least one of additions to at least the graph, deletions in
at least the graph, modifications to at least the graph, and combinations
thereof.
5 4. The method as claimed in claim 1, wherein the method comprises storing,
by the processing unit [304], in the cluster database [308], and in response
to the positive validity check of the received request, a received message
associated with the request, wherein the received message is stored in the
cluster database [308] in a predefined format and with a label associating
10 the received message with at least the database [306] associated with the
node.
5. The method as claimed in claim 4, wherein the predefined format comprises
Java Script Object Notation (JSON).
15
6. The method as claimed in claim 1, wherein the method comprises storing,
by the processing unit [304], on databases associated with the one or more
nodes, the received broadcast request.
20 7. The method as claimed in claim 1, wherein the method comprises
performing, by the processing unit [304], the operation on at least the
database [306] associated with the node, based on the received broadcast
request.
25 8. The method as claimed in claim 1, wherein the operation on at least the
database [306] associated with the node, as received in the broadcast
request, is performed on the cluster database [308].
32
9. The method as claimed in claim 8, wherein the method further comprises
updating, by the processing unit [304], the cluster database [308] to reflect
that one or more node associated with the graphs are updated.
5 10. The method as claimed in claim 8, wherein the cluster database [404] is a
NoSQL database.
11. A system for managing operations in a high availability network
environment, the system comprising:
10
- a transceiver unit [302] configured to receive a request to perform an
operation on at least a database [306] associated with a node;
- a processing unit [304] configured to:
- perform a validity check of the received request;
15 - perform, in response to a positive validity check of the received
request, the operation on at least the database [306] associated
with the node;
- the transceiver unit [302] further configured to transmit to at least a
cluster database [308], a set of details relating to the operation on at least
20 the database [306] associated with the node
- the transceiver unit [302] further configured to transmit, to one or more
nodes in a cluster, communicably coupled with at least the database
[306], a broadcast request relating to the operation on at least the
database associated with the node, and a request to update respective
25 databases associated with the one or more nodes; and
- the transceiver unit [302] further configured to receive, from the one or
more nodes, an acknowledgement message related to receipt, by the one
or more nodes of the broadcast request.
33
12. The system as claimed in claim 11, wherein the request to perform the
operation is received from one or more network functions [402].
13. The system as claimed in claim 11, wherein the database associated with the
5 node corresponds to a graph, wherein the operation on at least the graph
comprises at least one of additions to at least the graph, deletions in at least
the graph, modifications to at least the graph, and combinations thereof.
10 14. The system as claimed in claim 11, wherein the processing unit [304] is
configured to store, in a cluster database, and in response to the positive
validity check of the received request, a received message associated with
the request, wherein the received message is stored in the cluster database
in a predefined format and with a label associating the received message
15 with at least the database associated with the node.
15. The system as claimed in claim 14, wherein the predefined format
comprises Java Script Object Notation (JSON).
20 16. The system as claimed in claim 11, wherein the processing unit [304] is
configured to store, on databases associated with the one or more nodes, the
received broadcast request.
17. The system as claimed in claim 11, wherein the processing unit [304] is
25 configured to perform the operation on at least the database associated with
the node, based on the received broadcast request.
18. The system as claimed in claim 11, wherein the operation on at least the
database associated with the node, as received in the broadcast request, is
30 performed on a cluster database.
34
19. The system as claimed in claim 18, wherein the method further comprises
updating, by the processing unit [304], the cluster database to reflect that
one or more inventory instances associated with the graphs are updated.
20. The system as claimed in claim 18, wherein the cluster database [404] is a NoSQL database.