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 CREATING BACKUP OF A
CONTAINER NETWORK FUNCTION COMPONENT (CNFC)”
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 CREATING BACKUP OF A CONTAINER
NETWORK FUNCTION COMPONENT (CNFC)
FIELD OF THE DISCLOSURE
5
[0001] Embodiments of the present disclosure generally relate to the field of
wireless communication. More particularly, embodiments of the present disclosure
relate to method and system for creating backup of a container network function
component (CNFC).
10
BACKGROUND
[0002] The following description of related art is intended to provide background
information pertaining to the field of the disclosure. This section may include
15 certain aspects of the art that may be related to various features of the present
disclosure. However, it should be appreciated that this section be used only to
enhance the understanding of the reader with respect to the present disclosure, and
not as admissions of prior art.
20 [0003] Container Network Function Components (CNFCs) are applications
operating on a cloud server that replaces the specialized hardware. CNFCs are built
using microservice architecture and operate natively over virtual machines hosted
on the cloud server. CNFCs are an alternative to monolithic model of computing
and utilize individual and interconnected microservices. These microservices are
25 run in software containers which provide a run-time environment including the
application code, binaries, and dependencies needed for microservices to operate.
[0004] There are situations where a CNFC configured and deployed on a virtual
machine may have to be migrated to another virtual machine. In situations such as
30 disasters, where the network infrastructure is badly disrupted. This sabotage of the
network deployment requires the CNFC to be reconfigured and redeployed on the
3
other virtual machine which further leads to extensive development efforts that are
computationally expensive.
[0005] Also backing up of the CNFC ensures data integrity, business continuity,
5 and the ability to recover from various disaster scenarios to the telecom service
providers. The backup helps in creating a protection strategy against unforeseen
events which are not limited to disaster but also migration of the CNFC to different
virtual machines. Their backups can thus be created and used when it is necessary.
10 [0006] Thus, there exists an imperative need in the art to provide systems and
methods for creating backups of the CNFC for facilitating migration of CNFCs
between different virtual machines, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
15
[0007] This section is provided to introduce certain objects and aspects of the
present disclosure in a simplified form that are further described below in the
description. To overcome at least a few problems associated with the known
solutions as provided in the previous section, an object of the present disclosure is
20 to substantially reduce the limitations and drawbacks of the prior arts as described
hereinabove.
[0008] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
25
[0009] It is an object of the present disclosure to provide a system and a method
that may reduce the complexity and excessive consumption of computational
resources involved in migration of container network function component (CNFC)
between different virtual machines.
30
4
[0010] It is another object of the present disclosure to provide a solution that
facilitates creating backup of the CNFCs.
[0011] It is yet another object of the present disclosure to provide a solution for
5 facilitating restoration of deployed CNFCs in event of failure of the virtual machine.
[0012] It is yet another object of the present disclosure to take backup of a running
CNFC for disaster recovery.
10 SUMMARY OF THE DISCLOSURE
[0013] 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
15 subject matter.
[0014] An aspect of the present disclosure may relate to a method for creating
backup of a container network function component (CNFC). The method comprises
receiving, by a transceiver unit, at a virtual backup manager (VBM) a backup
20 request for the CNFC from a user interface (UI). The method further comprises
transmitting, by the transceiver unit, from the VBM, the backup request for the
CNFC to a service adapter (SA). The method further comprises receiving, by a
transceiver unit, at the VBM, backup details provided by the SA. The method
further comprises processing, by a processing unit, at the VBM, the backup details
25 to create a backup response. The method further comprises transmitting, by the
transceiver unit, from the VBM, the backup response comprising the backup details
to the UI.
[0015] In an exemplary implementation of the present disclosure, the method of
30 providing backup details by the SA comprises identifying, by a backup unit, at the
SA, the CNFC running on a container host. The method further comprises creating,
5
by a backup unit, at the SA, a backup of the CNFC. The backup here comprises a
file. The method further comprises storing, by a storage unit, at the SA, the backup
at a storage location. The method further comprises providing, by the backup unit,
from the SA, the backup details to the VBM.
5
[0016] In an exemplary implementation of the present disclosure, the storage
location is provided by the VBM in the backup request.
[0017] In an exemplary implementation of the present disclosure, the backup
10 details comprise the file name and the storage location of the file.
[0018] In an exemplary implementation of the present disclosure, the file is in tape
archive (tar) format and comprises one or more files.
15 [0019] Another aspect of the present disclosure may relate to a system for creating
backup of a container network function component (CNFC). The system comprises
a transceiver unit configured to receive, at a virtual backup manager (VBM), a
backup request for the CNFC from a user interface (UI). The transceiver unit is
further configured to transmit, from the VBM, the backup request for the CNFC to
20 a service adapter (SA). The transceiver unit is further configured to receive, at the
VBM, backup details provided by the SA. The system further comprises a
processing unit configured to process, at the VBM, the backup details to create a
backup response. The transceiver unit is further configured to transmit, from the
VBM, the backup response comprising the backup details to the UI.
25
[0020] Another aspect of the present disclosure may relate to a User Equipment
(UE). The UE comprises a transceiver unit, configured to transmit, a backup request
for a container network function component (CNFC) to a system, from a user
interface (UI) of the UE. The transceiver unit is further configured to receive, at the
30 UI, a backup response from the system. The backup response is generated by the
6
system. The transceiver unit is configured to receive, at a virtual backup manager
(VBM), a backup request for the container network function component (CNFC)
from the UI. The transceiver unit is configured to transmit, from the VBM, the
backup request for the CNFC to a service adapter (SA). The transceiver unit is
5 configured to receive, at the VBM, backup details provided by the SA. The UE
comprises a processing unit, configured to process, at the VBM, the backup details
to create the backup response. The transceiver unit is further configured to transmit,
from the VBM, the backup response comprising the backup details to the user
interface (UI).
10
[0021] Yet another aspect of the present disclosure may relate to a non-transitory
computer-readable storage medium storing instruction for creating backup of a
container network function component (CNFC), the storage medium comprising
executable code which, when executed by one or more units of a system, causes a
15 transceiver unit, of the system, to receive, at a virtual backup manager (VBM), a
backup request for the CNFC from a user interface (UI). Further, the executable
code which, when executed, causes the transceiver unit to transmit, from the VBM,
the backup request for the CNFC to a service adapter (SA). Further, the executable
code which, when executed, causes the transceiver unit to receive, at the VBM,
20 backup details provided by the SA. Further, the executable code which, when
executed, causes a processing unit, of the system, to process, at the VBM, the
backup details to create a backup response. Further, the executable code which,
when executed, causes the transceiver unit to transmit, from the VBM, the backup
response comprising the backup details to the UI.
25
DESCRIPTION OF DRAWINGS
[0022] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
30 and systems in which like reference numerals refer to the same parts throughout the
7
different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Some drawings may indicate the components using block diagrams and
may not represent the internal circuitry of each component. It will be appreciated
5 by those skilled in the art that disclosure of such drawings includes disclosure of
electrical components, electronic components or circuitry commonly used to
implement such components.
[0023] FIG. 1 illustrates an exemplary block diagram representation of a
10 management and orchestration (MANO) architecture, in accordance with an
exemplary implementation of the present disclosure.
[0024] 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
15 an exemplary implementation of the present disclosure.
[0025] FIG. 3 illustrates an exemplary block diagram of a network environment
having a system for creating backup of a container network function component
(CNFC), in accordance with an exemplary implementation of the present
20 disclosure.
[0026] FIG. 4 illustrates an exemplary flow diagram of a method for creating
backup of the CNFC, in accordance with an exemplary implementation of the
present disclosure.
25
[0027] FIG. 5A illustrates an exemplary system architecture for creating backup of
the CNFC, in accordance with an exemplary implementation of the present
disclosure.
8
[0028] FIG. 5B illustrates another system architecture for creating backup of the
CNFC, in accordance with an exemplary implementation of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
5 description of the disclosure.
DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various
10 specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter can each be used independently of one
another or with any combination of other features. An individual feature may not
15 address any of the problems discussed above or might address only some of the
problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different
20 drawings.
[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
25 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.
9
[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, networks, processes, and other
5 components may be shown as components in block diagram form in order not to
obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the embodiments.
10 [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
a sequential process, many of the operations can be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
15 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
serving as an example, instance, or illustration. For the avoidance of doubt, the
20 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
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
25 “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.
10
[0035] Further, the user device and/or a system as described herein to implement
technical features as disclosed in the present disclosure may also comprise
a “processor” or “processing unit”, wherein processor refers to any logic circuitry
for processing instructions. The processor may be a general-purpose processor, a
5 special purpose processor, a conventional processor, a digital signal processor, a
plurality of microprocessors, one or more microprocessors in association with a
Digital Signal Processor (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
10 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 is a hardware processor.
[0036] As used herein “interface” or “user interface” refers to a shared boundary
15 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.
20
[0037] 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
25 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.
[0038] As used herein the transceiver unit includes at least one receiver and at least
30 one transmitter configured respectively for receiving and transmitting data, signals,
11
information or a combination thereof between units/components within the system
and/or connected with the system.
[0039] In a Service-Based Architecture (SBA), each of these network functions can
5 be configured as a single container or as multiple containers. This network function
in the form of a container is called a Container Network Function (CNF), and if a
service consists of multiple containers, each container is called a Container
Network Function Component (CNFC). As discussed in the background section,
the current known solutions for migrating container network function component
10 (CNFC) have several shortcomings. As already described, there are situations when
the configured CNFC is deployed on a virtual machine may have to be migrated to
another virtual machine. In such situations, existing solutions require the CNFC to
be reconfigured and redeployed on the other virtual machine. It is pertinent to note
that configuration and deployment of CNFCs onto virtual machines requires
15 extensive development efforts and is computationally expensive.
[0040] Accordingly, migration of the CNFCs from one virtual machine to other
virtual machines is rendered complex and computationally expensive. In order to
overcome the problems mentioned in the background section, the present disclosure
20 provides system and method for creating backup of the CNFCs deployed on a
virtual machine hosted on a cloud server.
[0041] The present disclosure thus aims to overcome the above-mentioned and
other existing problems in this field of technology by facilitating back up of the
25 CNFCs deployed on a virtual machine hosted on a cloud server and utilizing the
backup for migrating the CNFCs between virtual machines.
[0042] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
30
12
[0043] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture [100], in accordance with
exemplary implementation of the present disclosure. The MANO architecture [100]
may be developed for managing telecom cloud infrastructure automatically,
5 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 as provided by the present disclosure may comprise
one or more components of the MANO architecture [100]. The MANO architecture
10 [100] may be used to auto-instantiate the VNFs into the corresponding environment
of the present disclosure so that it could help in recovery of network function(s) to
the platform.
[0044] As shown in FIG. 1, the MANO architecture [100] comprises a user
15 interface layer [102], a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platform foundation services
module [106], a platform core services module [108] and a platform resource
adapters and utilities module [112]. All the components are assumed to be
connected to each other in a manner as obvious to the person skilled in the art for
20 implementing features of the present disclosure.
[0045] The NFV and SDN design function module [104] comprises a VNF
lifecycle manager (compute)/ LM module [1042], a VNF catalogue [1044], a
network services catalogue [1046], a network slicing and service chaining manager
25 [1048], a physical and virtual resource manager/ PVIM module [1050] and a CNF
lifecycle manager [1052]. The VNF lifecycle manager (compute)/ LM module
[1042] may be responsible for deciding on which server of the communication
network, the microservice will be instantiated. The VNF lifecycle manager
(compute) / LM module [1042] may manage the overall flow of incoming/ outgoing
30 requests during interaction with the user. The VNF lifecycle manager (compute) /
13
LM module [1042] may be responsible for determining which sequence to be
followed for executing the process. For e.g. in an AMF network function of the
communication network (such as a 5G network), sequence for execution of
processes P1 and P2 etc. The VNF catalogue [1044] stores the metadata of all the
5 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. The physical and virtual resource manager/ physical
10 virtual inventory manager (PVIM) module [1050] stores the logical and physical
inventory of the VNFs. Just like the VNF lifecycle manager (compute) / LM module
[1042], the CNF lifecycle manager [1052] may be used for the CNFs lifecycle
management.
15 [0046] The platforms foundation services module [106] comprises a
microservices elastic load balancer [1062], an identity & access manager [1064], a
command line interface (CLI) [1066], a central logging manager [1068], and an
event routing manager (ERM)/ ERM module [1070]. The microservices elastic
load balancer [1062] may be used for maintaining the load balancing of the request
20 for the services. The identity & access manager [1064] may be used for logging
purposes. The command line interface (CLI) [1066] may be used to provide
commands to execute certain processes which requires changes during the run time.
The central logging manager [1068] may be responsible for keeping the logs of
every service. These logs are generated by the MANO platform [100]. These logs
25 are used for debugging purposes. The event routing manager (ERM)/ event
routing manger (ERM) module [1070] may be responsible for routing the events
i.e., the application programming interface (API) hits to the corresponding services.
[0047] The platforms core services module [108] comprises NFV infrastructure
30 monitoring manager [1082], an assure manager [1084], a performance manager
14
[1086], a policy execution engine [1088], a capacity monitoring manager [1090], a
release management (mgmt.) repository [1092], a configuration manager & golden
configuration template (GCT) [1094], an NFV platform decision analytics/ NPDA
module [1096], a platform NoSQL DB [1098]; a platform schedulers and cron jobs
5 [1100], a VNF backup & restore manager [1102], a microservice auditor [1104],
and a platform operations, administration and maintenance manager [1106]. The
NFV infrastructure monitoring manager [1082] monitors the infrastructure part
of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure
manager [1084] may be responsible for supervising the alarms the vendor may be
10 generating. The performance manager [1086] may be responsible for managing
the performance counters. The policy execution engine (PEGN)/ PEGN module
[1088] may be responsible for managing all of the policies. The capacity
monitoring manager (CMM) [1090] may be responsible for sending the request
to the PEGN [1088]. The release management (mgmt.) repository (RMR) [1092]
15 may be responsible for managing the releases and the images of all of the vendor's
network nodes. The configuration manager & golden configuration template
(GCT) [1094] manages the configuration and GCT of all the vendors. The NFV
platform decision analytics (NPDA)/ NFV platform decision analytics (NPDA)
module [1096] helps in deciding the priority of using the network resources. It may
20 be further noted that the policy execution engine (PEGN) module [1088], the
configuration manager & GCT [1094] and the NPDA [1096] work together. The
platform NoSQL DB [1098] may be a database for storing all the 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
25 triggering of an event, traverse the network graph etc. The VNF backup & restore
manager [1102] takes backup of the images, binaries of the VNFs and the CNFs
and produces those backup on demand in case of server failure. The microservice
auditor [1104] audits the microservices. For e.g., in a hypothetical case, instances
not being instantiated by the MANO architecture [100] may be using the network
30 resources. In such case, the microservice auditor [1104] audits and informs the same
15
so that resources can be released for services running in the MANO architecture
[100]. The audit assures that the services only run on the MANO platform [100].
The platform operations, administration and maintenance manager [1106]
may be used for newer instances that are spawning.
5
[0048] 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 service adaptor [1126]; an API adapter
[1128]; and a NFV gateway [1130]. The platform external API adaptor and
10 gateway [1122] may be responsible for handling the external services (to the
MANO platform [100]) that requires the network resources. The generic decoder
and indexer (XML, CSV, JSON) [1124] gets directly the data of the vendor
system in the XML, CSV, JSON format. The service adaptor [1126] may be the
interface provided between the telecom cloud and the MANO architecture [100] for
15 communication. The API adapter [1128] may be used to connect with the virtual
machines (VMs). The NFV gateway [1130] may be responsible for providing the
path to each services going to/incoming from the MANO architecture [100].
[0049] The present disclosure can be implemented on a computing device [200] as
20 shown in FIG. 2. The computing device [200] implements the present disclosure in
accordance with the MANO architecture (as shown in FIG. 1). FIG. 2 illustrates
an exemplary block diagram of the 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
25 device [200] may also implement a method [400] (as shown in FIG. 4) for creating
backup of container network functions components (CNFCs) [316]. In another
implementation, the computing device [200] itself implements the method [400] for
creating backup of CNFC [316] in a communication network using one or more
units configured within the computing device [200], wherein said one or more units
30 can implement the features as disclosed in the present disclosure.
16
[0050] 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
5 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]
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
10 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 specialpurpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
15 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0051] 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
20 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
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
25 bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as
a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. The input device typically has two degrees
17
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.
[0052] The computing device [200] may implement the techniques described
5 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
10 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
15 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0053] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two20 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
25 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.
30
18
[0054] 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
5 ISP [226], the local network [222], a host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
10 [0055] The present disclosure is implemented by the system [300] (as shown in
FIG. 3). The system [300] may be implemented using the computing device [200]
(as shown in FIG. 2). In an implementation, the computing device [200] may be
connected to the system [300] to perform the present disclosure.
15 [0056] Referring to FIG. 3, an exemplary block diagram of a network environment
having a system [300] for creating backup of a container network function
component (CNFC) [316] on a container host [314], is shown, in accordance with
the exemplary implementations of the present disclosure. The system [300]
comprises a virtual backup manager (VBM) [302] and a service adapter (SA) [310].
20 The VBM [302] comprises at least one transceiver unit [304]; at least one
processing unit [306]; and at least one storage unit [308]. It is further important to
note that the VBM [302] here performs the functions of the VNF backup and restore
manager [1102] (as shown in FIG.1 showing MANO architecture [100]). The SA
[310] comprises at least one backup unit [312]. It is further important to note that
25 the SA [310] here performs the functions of the service adapter (SA) [1126] (as
shown in FIG.1 showing MANO architecture [100]. The system [300] is connected
to at least one container network function component (CNFC) [316] hosted by a
container host [314]. The container host [314] may include a physical or virtual
network infrastructure where a virtual network function (VNF) or a container
30 network function component (CNFC) [316] (as seen in the instant case) can be
19
deployed. The container host [314] details may comprise computation resources
(like CPU or memory), network connections, types of virtualization layers etc. The
system [300] is also connected to a user equipment (UE) [318]. It is pertinent to
note that the UE [318] is not to be confused with a user/ subscriber device of the
5 network. Rather, the UE [318] interacts with the system [300] via a user interface
(UI) [320] (as also shown in FIG.1 demonstrating MANO architecture [100]). The
UE [318] is operated by a network personnel such as but not limited to network
administrator or an authorized network executive. Further, the UI [320] may also
act as an interface for communication with the VBM [302]. Also, all the
10 components/ units of the system [300] are assumed to be connected to each other
unless otherwise indicated below. As shown in the FIG.3, all units shown within
the system [300] should also be assumed to be connected to each other. Also, in
FIG. 3 only a few units are shown, however, the system [300] may comprise
multiple such units or the system [300] may comprise any such numbers of said
15 units, as required to implement the features of the present disclosure. In an
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.
20 [0057] Further, as stated earlier and as known in the art, creating backup allows to
recover resources after an outage or cyber-attack. Also, environment replication can
be extremely useful when moving from a test environment to a production
environment and can help in migration of container clusters. However, replication
of the whole container environment after an outage requires several components:
25 the container image, the attached mass storage memory and databases, persistent
volumes, etc. Unfortunately, traditional software for backup and disaster recovery
are not effective in a container environment. This type of software usually focuses
on protection of individual servers and the applications running on them.
Meanwhile, in the container environment, applications are often widely dispersed
30 and sometimes include many clouds and data centers. In addition, containers are
20
usually highly temporary, which is a big challenge for applications in creating
backup copies. The present disclosure implemented by the system [300] provides a
solution for creating backup of a CNFC.
5 [0058] The system [300] is configured for creating backup of a container network
function component (CNFC) [316] in a network environment, with the help of the
interconnection between the components/units of the system [300].
[0059] For creating the backup, the transceiver unit [304] receives, at the virtual
10 backup manager (VBM) [302], a backup request for the container network function
component (CNFC) [316] from the user interface (UI) [320]. The backup request is
a command sent to trigger creation of the backup of the CNFC [316]. Thereafter,
the transceiver unit [304] transmits, from the VBM [302], the backup request for
the CNFC [316] to the service adapter (SA) [310]. Then, the transceiver unit [304]
15 receives, at the VBM [302], backup details provided by the SA [310].
[0060] Upon receiving the backup details, the processing unit [306] processes the
received backup details, at the VBM [302], to create a backup response. The backup
response refers to an acknowledgement or status signifying the response that
20 whether the backup request has been accepted or not and further whether the backup
has been successfully created or not.
[0061] Once, the backup response is created, the transceiver unit [304] transmits,
from the VBM [302], the backup response comprising the backup details to the user
25 interface (UI) [320].
[0062] In an implementation of the present disclosure, for providing the backup
details, the system [300] comprises a backup unit [312], at the SA [310], configured
to identify the CNFC [316] running on a container host [314]. The container host
30 [314] may include a physical or virtual network infrastructure where a virtual
21
network function (VNF) or a container network function (CNF) can be deployed.
The container host [314] details may comprise computation resources (like CPU or
memory), network connections, types of virtualization layers etc. The backup unit
[312], at the SA [310], is further configured to create a backup of the CNFC [316].
5 The backup of the CNFC [316] created comprises a file. The storage unit [308], at
the SA [310], is further configured to store the backup at a storage location. The
storage location may be a backup location server [504] (as shown in FIG. 5A). The
backup unit [312], is further configured to provide from the SA [310], the backup
details to the VBM [302].
10
[0063] In an implementation of the present disclosure, the storage location is
provided by the VBM [302] in the backup request.
[0064] In an implementation of the present disclosure, the backup details comprise
15 the file name and the storage location of the file. The backup details may also
specify other information such as backup type, status and the timestamp of the
backup done at the system [300].
[0065] In an implementation of the present disclosure, the file is in a tape archive
20 (tar) format and comprises one or more files. The file may contain the backed-up
data of the CNFC [316]. As known in the art, a tar (tape archive) file format is an
archive created by tar, a UNIX-based utility used to package files together for
backup or distribution purposes. The tar software utility collects many files into
one archive file.
25
[0066] Referring to FIG. 4, an exemplary method flow diagram [400] for creating
backup of a container network function component (CNFC) [316] in a network
environment, in accordance with exemplary implementations of the present
disclosure is shown. In an implementation the method [400] is performed by the
30 system [300] (as shown in FIG. 3). Further, in an implementation, the system [300]
22
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].
[0067] At step [404], the method [400] comprises receiving, by a transceiver unit
5 [304], at a virtual backup manager (VBM) [302] a backup request for the container
network function component (CNFC) [316] from a user interface (UI) [320] (a
shown in FIG. 1). The backup request is a command sent to trigger start of creation
of the backup of the CNFC [316].
10 [0068] At step [406], the method [400] further comprises transmitting, by the
transceiver unit [304], from the VBM [302], the backup request for the CNFC [316]
to a service adapter (SA) [310].
[0069] At step [408], the method [400] further comprises receiving, by the
15 transceiver unit [304], at the VBM [302], backup details provided by the SA [310].
[0070] At step [410], the method [400] further comprises receiving, by the
transceiver unit [304], at the VBM [302], backup details provided by the SA [310].
20 [0071] At step [412], the method [400] further comprises processing, by a
processing unit [306], at the VBM [302], the backup details to create a backup
response. The backup response refers to an acknowledgement or status signifying
the response that whether the backup request has been accepted or not and further
whether the backup has been successfully created or not.
25
[0072] At step [414], the method [400] further comprises transmitting, by the
transceiver unit [304], from the VBM [302], the backup response comprising the
backup details to the user interface (UI) [320].
30 [0073] In an implementation of the present disclosure, the method [400] of
providing backup details by the SA [310] comprises identifying, by a backup unit
23
[312], at the SA [310], the CNFC [316] running on a container host [314]. The
container host [314] may include a physical or virtual network infrastructure where
a virtual network function (VNF) or a container network function (CNF) can be
deployed. The container host [314] details may comprise computation resources
5 (like CPU or memory), network connections, types of virtualization layers etc. The
method [400] further comprises creating, by a backup unit [312], at the SA [310], a
backup of the CNFC [316]. The backup of the CNFC [316] created comprises a
file. The method [400] further comprises storing, by a storage unit [308], at the SA
[310], the backup at a storage location. The method [400] further comprises
10 providing, by the backup unit [312], from the SA [310], the backup details to the
VBM [302].
[0074] In an implementation of the present disclosure, the backup details comprise
the file name and the storage location of the file. The backup details may also
15 specify other information such as backup type, status and the timestamp of the
backup done at the system [300].
[0075] In an implementation of the present disclosure, the storage location is
provided by the VBM [302] in the backup request.
20
[0076] In an implementation of the present disclosure, the file is in tape archive
(tar) format and comprises one or more files. The file may contain the backed-up
data of the CNFC [316]. As known in the art, a tar (tape archive) file format is an
archive created by tar, a UNIX-based utility used to package files together for
25 backup or distribution purposes. The tar software utility collects many files into
one archive file.
[0077] Thereafter, the method [400] terminates at step [416].
24
[0078] Referring to FIG. 5A, an exemplary system architecture [500A] for creating
backup of the container network function component (CNFC) [316] is shown, in
accordance with exemplary embodiments of the present disclosure. Referring to
FIG. 5B, another exemplary system architecture [500B] for creating backup of the
5 CNFC [316], in accordance with exemplary embodiments of the present disclosure,
in accordance with exemplary embodiments of the present disclosure. FIG.5A and
FIG. 5B have been explained in conjunction with each other to understand the
scenario of creating backup of the CNFC [316] i.e., working of the present
disclosure.
10
[0079] The CNFC [316] is operating on a virtual machine/ a host [314] (as shown
in FIG.3) which is hosted on a cloud server such as a Telco cloud [506]. The Telco
cloud [506] can be used by a telecommunication service provider. The system
[500A] comprises the at least one User Interface (UI) [320] (as also shown in FIG.
15 3), at least one backup location server [504] and at least one telco cloud [506], in
addition to a virtual backup manager (VBM) [302] (as also shown in FIG. 3) and a
service adapter (SA) [310] (as also shown in FIG. 3). Further, FIG. 5B comprises
the service adapter [310] connected with the virtual backup manager (VBM) [302]
by a SA_BM interface [502]. Also, all the components/ units of the system [500A]
20 are assumed to be connected to each other unless otherwise indicated below. Also,
in FIG. 5A and FIG. 5B, only a few units are shown, however, the system [500A]
and system [500B], may comprise multiple such units or the system [500A] and
system [500B] may comprise any such numbers of said units, as required to
implement the features of the present disclosure.
25
[0080] For backing up the CNFC [316], a BACKUP REQUEST (as shown in FIG.
5A) is received at the user interface (UI) [320] from a network personnel such as
network administrator. Thereafter, the BACKUP REQUEST is transmitted to the
VBM [302].
30
25
[0081] The system [500A] then causes the BACKUP REQUEST to be transmitted
from the VBM [302] to the SA [310]. The SA [310] comprises the information
indicative of the virtual machine on which the CNFC is being executed.
Accordingly, the SA [310] calls the virtual machine and takes a backup of the
5 container on which the CNFC [316] is being executed. The SA [310] may take the
backup of the container running on the virtual machine in a compressed format.
[0082] The SA [310] subsequently stores the backed-up container in the backup
location server [504]. Once the backup of the container has been stored, a
10 RESPONSE indicative of successful backup of the CNFC [316] is transmitted to
the VBM [302]. In an example, the RESPONSE comprises a file name of the
backup and a location on the backup location server [504] where the backup of the
CNFC [316] has been stored.
15 [0083] The VBM [302] subsequently transmits the RESPONSE indicative of
successful backup to the UI [320] from where the BACKUP REQUEST was first
received.
[0084] As would be appreciated, the backup of the CNFC [316] can be utilized for
20 deployment of the CNFC [316] onto a different virtual machine, thereby reducing
the complexity and consumption of computational resources involved in migration
of CNFCs [316] between different virtual machines. Further, the backup of the
CNFC [316] can be used for facilitating restoration of deployed CNFCs [316] in
event of failure of the virtual machine as well.
25
[0085] Further, the communication between the service adapter (SA) [310] and the
VBM [302] takes place through the SA_BM interface [502] as shown in FIG. 5B.
This interface is used to take backup of CNFC [316] between the SA [310] and the
VBM [302].
30
26
[0086] Another aspect of the present disclosure may relate to a User Equipment
(UE) [318]. The UE [318] comprises a transceiver unit [304], configured to
transmit, a backup request for a container network function component (CNFC)
[316] to a system [300], from a user interface (UI) [320]] of the UE [318]. The
5 transceiver unit [304] of the UE [318] is further configured to receive, at the user
interface (UI) [320], a backup response from the system [300]. The backup response
is generated by the system [300] comprising the transceiver unit [304] configured
to receive, at a virtual backup manager (VBM) [302], a backup request for the
container network function component (CNFC) [316] from the user interface (UI)
10 [320]. The transceiver unit [304] is configured to transmit, from the VBM [302],
the backup request for the CNFC [316] to a service adapter (SA) [310]. The
transceiver unit [304] is configured to receive, at the VBM [302], backup details
provided by the SA [310]. The UE [318] comprises a processing unit [306],
configured to process, at the VBM [302], the backup details to create the backup
15 response. The transceiver unit [304] is further configured to transmit, from the
VBM [302], the backup response comprising the backup details to the user interface
(UI) [320].
[0087] Yet another aspect of the present disclosure may relate to a non-transitory
20 computer-readable storage medium storing instruction for creating backup of a
container network function component (CNFC) [316], the storage medium
comprising executable code which, when executed by one or more units of a system
[300], causes a transceiver unit [304] of the system [300] to receive, at a virtual
backup manager (VBM) [302], a backup request for the container network function
25 component (CNFC) [316] from a user interface (UI) [320]. Further, the executable
code which, when executed, causes the transceiver unit [304] to transmit, from the
VBM [302], the backup request for the CNFC [316] to a service adapter (SA) [310].
Further, the executable code which, when executed, causes the transceiver unit
[304] to receive, at the VBM [302], backup details provided by the SA [310].
30 Further, the executable code which, when executed, causes a processing unit [306],
27
of the system [300], to process, at the VBM [302], the backup details to create a
backup response. Further, the executable code which, when executed, causes the
transceiver unit [304] to transmit, from the VBM [302], the backup response
comprising the backup details to the user interface (UI) [320].
5
[0088] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
10 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are encompassed within the scope of the present
15 disclosure.
[0089] As is evident from the above, the present disclosure provides a technically
advanced solution for creating backup of container network function component
(CNFC), thereby also facilitating migration of the CNFC across various virtual
20 machines. The backup of the CNFC can be utilized for deployment of the CNFC
onto different virtual machines and provides the following advantages:
- Nonservice impacting: The backup taken do not impact the functioning on
any of the running microservices/ functions in the communication network.
- Time efficiency: Due to the backup, the consumption of network resources
25 involved takes faster time in execution of the redundant microservices.
- Backup availability: Because of the present disclosure, the CNFC are
readily available to deploy in cases of failure.
- Disaster recovery: The present disclosure can be phenomenal in the disaster
management situations when the network catering to a particular area is
30 disrupted which leads to network infrastructure being affected. The backup
28
can thus ensure faster deployment of the status-quo of the network
infrastructure.
[0090] While considerable emphasis has been placed herein on the disclosed
5 implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
of the present disclosure 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
10 and non-limiting.
We Claim:
1. A method [400] for creating backup of a container network function component
(CNFC) [316], the method [400] comprising:
5 - receiving, by a transceiver unit [304], at a virtual backup manager (VBM)
[302] a backup request for the container network function component
(CNFC) [316] from a user interface (UI) [320];
- transmitting, by the transceiver unit [304], from the VBM [302], the backup
request for the CNFC [316] to a service adapter (SA) [310];
10 - receiving, by the transceiver unit [304], at the VBM [302], backup details
provided by the SA [310];
- processing, by a processing unit [306], at the VBM [302], the backup details
to create a backup response;
- transmitting, by the transceiver unit [304], from the VBM [302], the backup
15 response comprising the backup details to the user interface (UI) [320].
2. The method [400] as claimed in claim 1, wherein the method [400] of providing
backup details by the SA [310] comprises:
- identifying, by a backup unit [312], at the SA [310], the CNFC [316] running
20 on a container host [314];
- creating, by a backup unit [312], at the SA [310], a backup of the CNFC
[316], wherein the backup comprises a file;
- storing, by a storage unit [308], at the SA [310], the backup at a storage
location;
25 - providing, by the backup unit [312], from the SA [310], the backup details to
the VBM [302].
3. The method [400] as claimed in claim 2, wherein the storage location is provided
by the VBM [302] in the backup request.
30
30
4. The method [400] as claimed in claim 2, wherein the backup details comprise the
file name and the storage location of the file.
5. The method [400] as claimed in claim 2, wherein the file is in tape archive (tar)
5 format and comprises one or more files.
6. A system [300] for creating backup of a container network function component
(CNFC) [316], the system [300] comprising:
- a transceiver unit [304], configured to:
10 o receive, at a virtual backup manager (VBM) [302], a backup request
for the container network function component (CNFC) [316] from a
user interface (UI) [320];
o transmit, from the VBM [302], the backup request for the CNFC
[316] to a service adapter (SA) [310];
15 o receive, at the VBM [302], backup details provided by the SA [310];
- a processing unit [306], configured to:
o process, at the VBM [302], the backup details to create a backup
response;
- the transceiver unit [304], further configured to:
20 o transmit, from the VBM [302], the backup response comprising the
backup details to the user interface (UI) [320].
7. The system [300] as claimed in claim 6, wherein for providing the backup
details, the system [300] comprises:
25 - a backup unit [312], at the SA [310], configured to identify the CNFC [316]
running on a container host [314];
- the backup unit [312], at the SA [310], configured to create a backup of the
CNFC [316], wherein the backup comprises a file;
- a storage unit [308], at the SA [310], configured to store the backup at a
30 storage location;
31
- the backup unit [312], configured to provide from the SA [310], the backup
details to the VBM [302].
8. The system [300] as claimed in claim 7, wherein the storage location is provided
5 by the VBM [302] in the backup request.
9. The system [300] as claimed in claim 7, wherein the backup details comprise the
file name and the storage location of the file.
10 10. The system [300] as claimed in claim 7, wherein the file is in a tape archive (tar)
format and comprises one or more files.
11. A User Equipment (UE) [318], comprising:
- a transceiver unit, configured to:
15 o transmit, a backup request for a container network function component
(CNFC) [316] to a system [300], from a user interface (UI) [320] of
the UE [318];
o receive, at the user interface (UI) [320], a backup response from the
system [300], wherein the backup response is generated by the system
20 [300] comprising:
o a transceiver unit [304] configured to:
▪ receive, at a virtual backup manager (VBM) [302], a
backup request for the container network function
component (CNFC) [316] from the user interface (UI)
25 [320];
▪ transmit, from the VBM [302], the backup request for
the CNFC [316] to a service adapter (SA) [310];
▪ receive, at the VBM [302], backup details provided by
the SA [310];
30 o a processing unit [306], configured to:
32
▪ process, at the VBM [302], the backup details to create
the backup response;
o the transceiver unit [304], further configured to:
▪ transmit, from the VBM [302], the backup response
5 comprising the backup details to the user interface (UI)
[320].