202321065838
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 OPERATION OF
CONTAINER NETWORK FUNCTION COMPONENTS
(CNFCs)”
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 OPERATION OF
CONTAINER NETWORK FUNCTION COMPONENTS (CNFCs)
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure generally relate to the field of
wireless communication systems. More particularly, embodiments of the present
disclosure relate to methods and systems for managing operation of container
network function components (CNFCs).
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] Wireless communication technology has rapidly evolved over the past few
decades, with each generation bringing significant improvements and
advancements. The first generation of wireless communication technology was
based on analog technology and offered only voice services. However, with the
advent of the second-generation (2G) technology, digital communication and data
25 services became possible, and text messaging was introduced. 3G technology
marked the introduction of high-speed internet access, mobile video calling, and
location-based services. The fourth generation (4G) technology revolutionized
wireless communication with faster data speeds, better network coverage, and
improved security. Currently, the fifth generation (5G) technology is being
30 deployed, promising even faster data speeds, low latency, and the ability to connect
3
multiple devices simultaneously. With each generation, wireless communication
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
5 [0004] A network function is generally packaged in a container to make it
consistent, portable, and easily distributable and modifiable with little labor and few
dependencies. The host operating system's kernel is then used by containers as they
operate. Either a real server or a virtual machine houses the host operating system.
A clustering and scheduling tool for Docker containers is called Docker Swarm. IT
10 managers and developers may set up and control a cluster of Docker nodes as a
single virtual system using Swarm. Swarm mode is a built-in feature of Docker
Engine, which acts as a bridge between operating systems and container images.
The function of fetching CNFC metrics and host metrics for execution of new
CNFC in case of any policy breach or any host down is required to be handled by
15 an efficient and error free system.
[0005] Thus, there exists an imperative need in the art for a system and method for
managing operation of Container Network Function Components (CNFCs), which
the present disclosure aims to address.
20
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.
25 This summary is not intended to identify the key features or the scope of the claimed
subject matter.
[0007] An aspect of the present disclosure may relate to a method for managing
operation of Container Network Function Components (CNFCs). The method
30 includes receiving, by a docker service adapter (DSA) unit, CNFC metrics related
4
to a plurality of CNFCs hosted on a host network, and host metrics related to the
host network. The CNFC metrics and the host metrics are received in response to
executing one or more jobs scheduled for the plurality of CNFCs. Next, the method
includes receiving, by the DSA unit, from the host network, a status of the plurality
5 of CNFCs running on the host network. Thereafter, the method includes updating,
by the DSA unit, to a database coupled to the DSA unit, the CNFC metrics, the host
metrics, and the status of the plurality of CNFCs and the host network to facilitate
the management of CNFCs.
10 [0008] In an exemplary aspect of the present disclosure, the method comprises
transmitting, by the DSA unit, to the host network, a request for details associated
with the status of the plurality of CNFCs running on the host network; and
receiving, by the DSA unit, the status of the plurality of CNFCs in response to the
transmitted request.
15
[0009] In an exemplary aspect of the present disclosure, the method comprises
modifying, by the DSA unit, execution parameters of one or more CNFCs from the
plurality of CNFCs based on at least one of the CNFC metrics, the host metrics, or
the status of the plurality of CNFCs. The execution parameters comprise at least
20 one of a timing parameter associated with the one or more jobs, or an interval
parameter associated with the execution of the one or more jobs.
[0010] In an exemplary aspect of the present disclosure, the method further
comprises retrieving, by the DSA unit, from the database, the updated CNFC
25 metrics, the host metrics, or the status of the plurality of CNFCs in response to an
error event. The error event is selected from a group consisting of a policy breach,
a host error, and a combination thereof.
5
[0011] In an exemplary aspect of the present disclosure, the management operation
of CNFCs is performed in at least one of: an event of a policy breach or
malfunctioning of host.
5 [0012] Another aspect of the present disclosure may relate to a system for
managing operation of Container Network Function Components (CNFCs) via an
interface. The system comprises a docker service adapter (DSA) unit. The DSA unit
is configured to receive CNFC metrics related to a plurality of CNFCs hosted on a
host network, and host metrics related to the host network, wherein the CNFC
10 metrics and the host metrics are received in response to executing one or more jobs
scheduled for the plurality of CNFCs; receive, from the host network, a status of
the plurality of CNFCs running on the host network; and update, to a database
coupled to the DSA unit, the CNFC metrics, the host metrics, and the status of the
plurality of CNFCs and the host network to facilitate the management of CNFCs.
15
[0013] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for managing operation of
Container Network Function Components (CNFCs) via an interface, the
instructions include executable code which, when executed by one or more units of
20 a system, causes: a docker service adapter (DSA) unit of the system to receive
CNFC metrics related to a plurality of CNFCs hosted on a host network, and host
metrics related to the host network, wherein the CNFC metrics and the host metrics
are received in response to executing one or more jobs scheduled for the plurality
of CNFCs; receive, from the host network, a status of the plurality of CNFCs
25 running on the host network; and update, to a database coupled to the DSA unit, the
CNFC metrics, the host metrics, and the status of the plurality of CNFCs and the
host network to facilitate the management of CNFCs.
OBJECTS OF THE INVENTION
30
6
[0014] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for
5 managing an execution of new CNFC in the event of any policy breach or any
malfunctioning host using the updated and stored metrics.
[0016] It is another object of the present disclosure to provide a solution to utilize
an interface efficiently by employing an async event-based implementation and
10 using Jobs to fetch the metrics periodically.
DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated herein, and constitute
15 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
20 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
25
[0018] FIG. 1 illustrates an exemplary block diagram of a management and
orchestration (MANO) architecture, in accordance with exemplary
implementations of the present disclosure.
7
[0019] FIG. 2 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
5 [0020] FIG. 3 illustrates an exemplary block diagram of a system for managing
operation of Container Network Function Components (CNFCs), in accordance
with exemplary implementations of the present disclosure.
[0021] FIG. 4 illustrates a method flow diagram for managing operation of
10 Container Network Function Components (CNFCs), in accordance with exemplary
implementations of the present disclosure.
[0022] FIG. 5 illustrates an exemplary system architecture for managing operation
of Container Network Function Components (CNFCs), in accordance with
15 exemplary implementations of the present disclosure.
[0023] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
20 DETAILED DESCRIPTION
[0024] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
25 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
address any of the problems discussed above or might address only some of the
problems discussed above.
30
8
[0025] 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
the art with an enabling description for implementing an exemplary embodiment.
5 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.
[0026] Specific details are given in the following description to provide a thorough
10 understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
15
[0027] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
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
20 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.
[0028] The word “exemplary” and/or “demonstrative” is used herein to mean
25 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
9
“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.
5
[0029] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
10 of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
15 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0030] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
20 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
25 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
such unit(s) which are required to implement the features of the present disclosure.
30
10
[0031] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
5 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.
10 [0032] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
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
15 called.
[0033] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
20 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.
25 [0034] As used herein, the transceiver unit includes at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
and/or connected with the system.
11
[0035] As used herein, Physical and Virtual Inventory Manager (PVIM) module
maintains the inventory and its resources. After getting a request to reserve
resources from PEEGN, PVIM adds up the resources consumed by particular
network function as used resources and removes them from free resources. Further,
5 the PVIM updates this in NoSQL database.
[0036] As used herein, Docker Service Adapter (DSA) directly connects to docker
host of swarm manager to deploy the docker image to docker host nodes. DSA may
create docker swarm manager and may add docker hosts as swarm worker node.
10
[0037] As used herein, IM_SA interface is present between the PVIM and the DSA.
IM_SA interface may assist the managing operation of the CNFCs.
[0038] As used herein, Policy Execution Engine (PEEGN) module provides a
15 network function virtualisation (NFV) software defined network (SDN) platform
functionality to support dynamic requirements of resource management and
network service orchestration in the virtualized network. Further, the PEEGN is
involved during CNF instantiation flow to check for CNF policy and to reserve
resources required to instantiate CNF at PVIM. PEEGN supports scaling policy for
20 CNFC.
[0039] 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 a
25 method and system for managing operation of Container Network Function
Components (CNFCs). The present disclosure employs an async event-based
implementation to utilize interface efficiently. Further, one or more jobs or cron
jobs run at scheduled time for the plurality of CNFCs to get CNFC metrics and host
metrics periodically which are configured in DSA unit. The present solution
30 facilitates for changing the time-schedule of the cron jobs and time interval of
running the cron jobs in the DSA unit.
12
[0040] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
5 [0041] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0042] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture/ platform [100], in
10 accordance with exemplary implementation of the present disclosure. The MANO
architecture [100] may be developed for managing telecom cloud infrastructure
automatically, managing design or deployment design, managing instantiation of
network node(s)/ service(s) etc. The MANO architecture [100] deploys the network
node(s) in the form of Virtual Network Function (VNF) and Cloud-native/
15 Container Network Function (CNF). The system as provided by the present
disclosure may comprise one or more components of the MANO architecture [100].
The MANO architecture [100] may be used to 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.
20
[0043] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer [102], a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platform foundation services
module [106], a Platform Schedulers & Cron Jobs module [108] and a platform
25 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
implementing features of the present disclosure.
[0044] The NFV and SDN design function module [104] comprises a VNF
30 lifecycle manager (compute) [1042], a VNF catalogue [1044], a network services
13
catalogue [1046], a network slicing and service chaining manager [1048], a physical
and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF
lifecycle manager (compute) [1042] may be responsible for deciding on which
server of the communication network, the microservice will be instantiated. The
5 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] 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
10 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 [1048] manages the slicing (an ordered and connected sequence
of network service/ network functions (NFs)) that must be applied to a specific
15 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] may be used for the CNFs
lifecycle management.
20 [0045] 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 [1070]. The microservices elastic load balancer [1062] may be used for
maintaining the load balancing of the request for the services. The identity & access
25 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 are used for debugging purposes. The event
14
routing manager [1070] may be responsible for routing the events i.e., the
application programming interface (API) hits to the corresponding services.
[0046] 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 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 generating. The performance manager
15 [1086] may be responsible for managing the performance counters. The policy
execution engine (PEGN) [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] may be responsible for managing the releases and the
20 images of all of the vendor's network nodes. The configuration manager & (GCT)
[1094] manages the configuration and GCT of all the vendors. The NFV platform
decision analytics (NPDA) [1096] helps in deciding the priority of using the
network resources. It may be further noted that the policy execution engine (PEGN)
[1088], the configuration manager & GCT [1094] and the NPDA [1096] work
25 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 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
30 the CNFs and produces those backups on demand in case of server failure. The
15
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 resources. In such case, the microservice auditor [1104] audits and
informs the same so that resources can be released for services running in the
5 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.
[0047] The platform resource adapters and utilities module [112] further comprises
10 a platform external API adaptor and gateway [1122]; a generic decoder and indexer
(XML, CSV, JSON) [1124]; a docker service adaptor [1126]; an API adapter
[1128]; and a NFV gateway [1130]. The platform external API adaptor and gateway
[1122] may be responsible for handling the external services (to the MANO
platform [100]) that requires the network resources. The generic decoder and
15 indexer (XML, CSV, JSON) [1124] gets directly the data of the vendor system in
the XML, CSV, JSON format. The docker service adaptor [1126] may be the
interface provided between the telecom cloud and the MANO architecture [100] for
communication. The API adapter [1128] may be used to connect with the virtual
machines (VMs). The NFV gateway [1130] may be responsible for providing the
20 path to each services going to/incoming from the MANO architecture [100].
[0048] Referring to FIG. 2, 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, is shown. In
25 an implementation, the computing device [200] may also implement a method for
managing operation of container network function components (CNFCs) utilising
the system. In another implementation, the computing device [200] itself
implements the method for managing operation of container network function
components (CNFCs) using one or more units configured within the computing
30 device [200], wherein said one or more units are capable of implementing the
features as disclosed in the present disclosure.
16
[0049] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
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].
[0050] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
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.
[0051] 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.
[0052] 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
[0053] 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], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
10 [0054] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing operation of container network function components (CNFCs) is shown,
in accordance with the exemplary implementations of the present disclosure. The
system [300] comprises at least one docker service adapter (DSA) unit [1126], at
least one container network function component (CNFC) [302], and at least one
15 database (DB) [304]. Also, all of the components/ units of the system [300] are
assumed to be connected to each other unless otherwise indicated below. 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. In an
20 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.
[0055] The system [300] is configured for managing operation of container
25 network function components (CNFCs) via an interface, with the help of the
interconnection between the components/units of the system [300].
[0056] The system [300] comprises the docker service adapter (DSA) unit [1126].
The DSA unit [1126] is configured to receive CNFC metrics related to a plurality
30 of CNFCs [302] hosted on a host network, and host metrics related to the host
19
network. The CNFC metrics and the host metrics are received in response to
executing one or more jobs scheduled for the plurality of CNFCs [302]. In an
exemplary implementation, the host network may have one or more servers or
computing devices. The host network may host the plurality of CNFCs [302]
5 performing preconfigured services in the host network. The DSA unit [1126] is
configured to execute one or more jobs or run cron jobs at schedule time for the
plurality of CNFCs [302] to get CNFC metrics and host metrics. The one or more
jobs or cron jobs are scheduled at a predefined time or interval for fetching metrics
details associated with the CNFCs and the host. In an exemplary implementation,
10 the metrics (i.e., CNFC metrics and host metrics) may be associated with server
load, storage, status of tasks and number of active/inactive CNFCs.
[0057] The DSA unit [1126] is further configured to receive, from the host network,
a status of the plurality of CNFCs [302] running on the host network. The DSA unit
15 [1126] is configured to transmit, to the host network, a request for details associated
with the status of the plurality of CNFCs [302] running on the host network. The
DSA unit [1126] is further configured to receive, from the host network, the status
of the plurality of CNFCs [302] in response to the transmitted request. For example,
the DSA unit [1126] may receive the status of the plurality of CNFCs [302] running
20 on the host network. For example, the status of the plurality of CNFCs may include,
but not limited to, storage usage of CNFC1, status of ‘task A’ of CNFC2, and ‘not
in service’ status of CNFC3. In an exemplary implementation, the DSA unit [1126]
is configured to send request and receive response periodically from the host
network.
25
[0058] The DSA unit [1126] is further configured to update, to the database [304]
coupled to the DSA unit [1126], the CNFC metrics, the host metrics, and the status
of the plurality of CNFCs [302] and the host network to facilitate the management
of CNFCs [302]. After receiving the CNFCs metrics, host metrics and the status of
30 the plurality of the CNFCs [302] from the host network, the DSA unit [1126] is
configured to store and update it in the database [304]. In an exemplary
20
implementation, the management of operation of the CNFCs [302] is performed in
at least one of: an event of a policy breach or malfunctioning of host. The managing
operation of the CNFCs [302] is performed via an interface, such as IM_SA
interface.
5
[0059] For example, IM may relate to an inventory manager (e.g., physical &
virtual resource manager (PVIM) in the MANO architecture [100]) and SA may
relate to the service adaptor (e.g., DSA unit [1126] in the MANO architecture
[100]). The IM_SA interface may be a communication link between the IM and the
10 SA, which enables the communication between the components.
[0060] In an exemplary implementation, the DSA unit [1126] is configured to
modify execution parameters of one or more CNFCs from the plurality of CNFCs
[302] based on at least one of the CNFC metrics, the host metrics, or the status of
15 the plurality of CNFCs [302]. The execution parameters may comprise at least one
of a timing parameter associated with the one or more jobs, or an interval parameter
associated with the execution of the one or more jobs. For example, the DSA unit
[1126] is configured to modify time interval from 15 mins to 10 mins, if one or
more CNFC from the plurality of the CNFCs [302] such as, CNFC1’s load metrics
20 is getting closer to the predefined limit and CNFC1’s status is about to breach the
predefined CNFC policy for the operation management. The DSA unit [1126] is
configured to change job fire time and interval of request to the host network.
[0061] In an exemplary implementation, the DSA unit [1126] is further configured
25 to retrieve, from the database [304], the updated CNFC metrics, the host metrics,
or the status of the plurality of CNFCs [302] in response to an error event. The error
event is selected from a group consisting of the policy breach, a host error, and a
combination thereof. The network administrator or service provider may define
policy for the plurality of the CNFCs [302] for the operation. In an event of breach
30 of the policy for the operation of the plurality of the CNFCs [302] or any host
malfunctioning or host error, the DSA unit [1126] is configured to retrieve the
21
updated CNFC metrics, the host metrics, or the status of the plurality of CNFCs
[302] from the database [304]. After retrieving the updated CNFC metrics, the host
metrics, or the status of the plurality of CNFCs, the DSA unit [1126] is configured
to create and execute new CNFC for managing the operation of the CNFCs.
5
[0062] 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 considered to be encompassed within the scope
15 of the present disclosure.
[0063] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
operation of container network function components (CNFCs), in accordance with
exemplary implementations of the present disclosure is shown. In an
20 implementation, the method [400] is performed by the system [300]. As shown in
FIG. 4, the method [400] starts at step [402].
[0064] At step [404], the method [400] comprises receiving, by the docker service
adapter (DSA) unit [1126], CNFC metrics related to the plurality of CNFCs [302]
25 hosted on the host network, and host metrics related to the host network. The CNFC
metrics and the host metrics are received in response to executing one or more jobs
scheduled for the plurality of CNFCs [302]. In an exemplary implementation, the
host network may have one or more servers or computing devices.
30 [0065] The host network may host the plurality of CNFCs [302] performing
preconfigured services in the host network. The DSA unit [1126] may execute one
22
or more jobs or run cron jobs at schedule time for the plurality of CNFCs [302] to
get CNFC metrics and host metrics. The one or more jobs or cron jobs are scheduled
at a predefined time or interval for fetching metrics details associated with the
CNFCs and the host. In an exemplary implementation, the metrics may be
5 associated with vendor details, server load, storage, status of tasks and number of
active/inactive CNFCs.
[0066] Next, at step [406], the method [400] comprises receiving, by the DSA unit
[1126], from the host network, the status of the plurality of CNFCs [302] running
10 on the host network. The DSA unit [1126] may transmit, to the host network, a
request for details associated with the status of the plurality of CNFCs [302] running
on the host network. The DSA unit [1126] may receive, from the host network, the
status of the plurality of CNFCs [302] in response to the transmitted request.
15 [0067] For example, the DSA unit [1126] may receive the status of the plurality of
CNFCs [302] running on the host network. In an exemplary implementation, the
DSA unit [1126] may send request and receive response periodically from the host
network.
20 [0068] Next, at step [408], the method [400] comprises updating, by the DSA unit
[1126], to the database [304] coupled to the DSA unit [1126], the CNFC metrics,
the host metrics, and the status of the plurality of CNFCs and the host network to
facilitate the management of CNFCs [302]. After receiving the CNFCs metrics, host
metrics, and the status of the plurality of the CNFCs [302] from the host network,
25 the DSA unit [1126] may store and update it in the database [304]. In an exemplary
implementation, the management of operation of the CNFCs [302] is performed in
at least one of: an event of a policy breach or malfunctioning of host. The managing
operation of the CNFCs is performed via an interface, such as IM_SA interface
using closed loop action.
30
23
[0069] In an exemplary implementation, the DSA unit [1126] may modify
execution parameters of one or more CNFCs from the plurality of CNFCs [302]
based on at least one of the CNFC metrics, the host metrics, or the status of the
plurality of CNFCs [302]. The execution parameters may comprise at least one of
5 a timing parameter associated with the one or more jobs, or an interval parameter
associated with the execution of the one or more jobs. For example, if one or more
CNFC from the plurality of the CNFCs [302] such as, CNFC1’s load metrics is
getting closer to the predefined limit and/or CNFC1’s status is about to breach the
predefined CNFC policy for the operation management, the DSA unit [1126] may
10 modify time interval from 15 mins to 10 mins. The DSA unit [1126] may change
job fire time and interval of request to the host network.
[0070] In an exemplary implementation, the DSA unit [1126] may retrieve, from
the database [304], the updated CNFC metrics, the host metrics, or the status of the
15 plurality of CNFCs [302] in response to an error event. The error event is selected
from a group consisting of the policy breach, a host error, and a combination
thereof.
[0071] The network administrator or service provider may define policy for the
20 plurality of the CNFCs [302] for the operation. In an event of breach of the policy
for the operation of the plurality of the CNFCs [302] or any host malfunctioning or
host error, the DSA unit [1126] is configured to retrieve the updated CNFC metrics,
the host metrics, or the status of the plurality of CNFCs [302] from the database
[304]. After retrieving the updated CNFC metrics, the host metrics, or the status of
25 the plurality of CNFCs, the DSA unit [1126] is configured to create and execute
new CNFC for managing the operation of the CNFCs.
[0072] Thereafter, the method [400] terminates at step [410].
30 [0073] FIG. 5 illustrates an exemplary system architecture [500] for managing
operation of Container Network Function Components (CNFCs), in accordance
24
with exemplary implementations of the present disclosure. As shown in FIG. 5, the
system [500] comprises a database (DB) [504], a host [506] having a CNFC1(502a)
and CNFC2 (502b), a DSA unit [1126] comprising Cron Job for container metric
of host [508] and Cron Job for host metric [510].
5
[0074] As shown in FIG, 5, DSA [1126] sends a request via cron Job for container
metric of host [508] to the host [506] for getting CNFCs metrics and status. In
response to this, the host sends CNFCs metrics and status of the CNFCs, such as
CFC1 [502a] and CNFC2 [502b]. After receiving the metrics and status of the
10 CNFCs, the DSA [1126] stores and updates the CNFCs metrics and status in a
database (DS) [504]. The DSA [1126] may sends this request periodically or at
predefined time interval for getting details of the plurality of CNFCs running on the
host.
15 [0075] Further, DSA [1126] sends a request via cron Job for host metric [510] to
the host [506] for getting host metrics and status. In response to this, the host sends
host metrics and status of the host. After receiving the metrics and status of the host,
the DSA [1126] stores and updates the host metrics and status in a database (DS)
[504]. The DSA [1126] may send this request periodically or at predefined time
20 interval for getting details of the host.
[0076] In an implementation, for any policy breach for the CNFCs (CNFC [502a]
and CNFC [502b]) or any host malfunctioning, the DSA [1126] may fetch the stored
and updated details (e.g., metrics and status) from the database [504] and creates a
25 new CNFC based on the fetched details.
[0077] In a non-limiting implementation of the present solution in other words, the
method [400] may be configured to perform as depicted in FIG. 4 via at one or more
components as depicted in FIG. 1 to FIG. 5 as follows: When DSA unit come up,
30 it will connect and run jobs to get CNFC metrics and host metrics. The DSA unit
25
will send request to host and get container metrics for the container, which is
running on host. The DSA unit will save these metrics on database for taking closed
loop action. The DSA unit can change job fire time and interval of requests to host.
5 [0078] The present disclosure may relate to a non-transitory computer readable
storage medium storing instructions for managing operation of Container Network
Function Components (CNFCs) via an interface, the instructions include executable
code which, when executed by one or more units of a system, causes: a docker
service adapter (DSA) unit [1126] of the system to receive CNFC metrics related
10 to a plurality of CNFCs [302] hosted on a host network, and host metrics related to
the host network, wherein the CNFC metrics and the host metrics are received in
response to executing one or more jobs scheduled for the plurality of CNFCs [302];
receive, from the host network, a status of the plurality of CNFCs running on the
host network; and update, to a database [304] coupled to the DSA unit [1126], the
15 CNFC metrics, the host metrics, and the status of the plurality of CNFCs [302] and
the host network to facilitate the management of CNFCs.
[0079] As is evident from the above, the present disclosure provides a technically
advanced solution for managing via the IM_SA interface an execution of new
20 CNFC in the event of any policy breach or any malfunctioning host using the
updated and stored metrics. The present solution encompasses many advantages
such as DSA have cron jobs inside to get CNFC metric and host metric details. This
job uses rest end points to fetch the CNFC and host metrics and save to database
for taking closed loop actions.
25
[0080] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made to the embodiments without departing from the
principles of the present disclosure. These and other changes in the embodiments
30 of the present disclosure will be apparent to those skilled in the art, whereby it is to
26
be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
27
We Claim:
1. A method for managing operation of Container Network Function
Components (CNFCs), the method comprising:
- receiving, by a docker service adapter (DSA) unit [1126], CNFC
5 metrics related to a plurality of CNFCs [302] hosted on a host network,
and host metrics related to the host network, wherein the CNFC metrics
and the host metrics are received in response to executing one or more
jobs scheduled for the plurality of CNFCs [302];
- receiving, by the DSA unit [1126], from the host network, a status of
10 the plurality of CNFCs [302] running on the host network; and
- updating, by the DSA unit [1126], to a database [304] coupled to the
DSA unit [1126], the CNFC metrics, the host metrics, and the status of
the plurality of CNFCs and the host network to facilitate the
management of CNFCs [302].
15
2. The method as claimed in claim 1, wherein the method comprises:
- transmitting, by the DSA unit [1126], to the host network, a request for
details associated with the status of the plurality of CNFCs [302]
running on the host network; and
20 - receiving, by the DSA unit [1126], the status of the plurality of CNFCs
in response to the transmitted request.
3. The method as claimed in claim 1, comprising modifying, by the DSA unit
[1126], execution parameters of one or more CNFCs from the plurality of
25 CNFCs [302] based on at least one of the CNFC metrics, the host metrics, or
the status of the plurality of CNFCs [302], wherein the execution parameters
comprise at least one of a timing parameter associated with the one or more
jobs, or an interval parameter associated with the execution of the one or more
jobs.
28
4. The method as claimed in claim 1, wherein the method comprises retrieving,
by the DSA unit [1126], from the database [304], the updated CNFC metrics,
the host metrics, or the status of the plurality of CNFCs [302] in response to
5 an error event, wherein the error event is selected from a group consisting of
a policy breach, a host error, and a combination thereof.
5. The method as claimed in claim 1, wherein the management operation of
CNFCs [302] is performed in at least one of: an event of a policy breach or
10 malfunctioning of host.
6. A system for managing operation of Container Network Function
Components (CNFCs) via an interface, the system comprising:
- a docker service adapter (DSA) unit [1126] configured to:
15 - receive CNFC metrics related to a plurality of CNFCs [302]
hosted on a host network, and host metrics related to the host
network, wherein the CNFC metrics and the host metrics are
received in response to executing one or more jobs scheduled for
the plurality of CNFCs [302];
20 - receive, from the host network, a status of the plurality of CNFCs
[302] running on the host network; and
- update, to a database [304] coupled to the DSA unit [1126], the
CNFC metrics, the host metrics, and the status of the plurality of
CNFCs [302] and the host network to facilitate the management
25 of CNFCs [302].
7. The system as claimed in claim 6, wherein the DSA unit [1126] is configured
to:
29
- transmit, to the host network, a request for details associated with the
status of the plurality of CNFCs [302] running on the host network; and
- receive, from the host network, the status of the plurality of CNFCs
[302] in response to the transmitted request.
5
8. The system as claimed in claim 6, wherein the DSA unit [1126] is configured
to modify execution parameters of one or more CNFCs from the plurality of
CNFCs [302] based on at least one of the CNFC metrics, the host metrics, or
the status of the plurality of CNFCs [302], wherein the execution parameters
10 comprise at least one of a timing parameter associated with the one or more
jobs, or an interval parameter associated with the execution of the one or more
jobs.
9. The system as claimed in claim 6, wherein the DSA unit [1126] is configured
15 to retrieve, from the database [304], the updated CNFC metrics, the host
metrics, or the status of the plurality of CNFCs [302] in response to an error
event, wherein the error event is selected from a group consisting of a policy
breach, a host error, and a combination thereof.
20 10. The system as claimed in claim 6, wherein the management operation of
CNFCs [302] is performed in at least one of: an event of a policy breach or
malfunctioning of host.