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 ONE OR MORE
INSTANCES OF POLICY EXECUTION ENGINE (PEEGN)”
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 ONE OR MORE
INSTANCES OF POLICY EXECUTION ENGINE (PEEGN)
FIELD OF THE DISCLOSURE
5
[0001] Embodiments of the present disclosure generally relate to network
performance management systems. More particularly, embodiments of the present
disclosure relate to managing one or more instances of a policy execution engine
(PEEGN) unit in a network.
10
BACKGROUND
[0002] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may
15 include certain aspects of the art that may be related to various features of the
present disclosure. However, it should be appreciated that this section is used only
to enhance the understanding of the reader with respect to the present disclosure,
and not as admissions of the prior art.
20 [0003] Wireless communication technology has rapidly evolved over the past few
decades, with each generation bringing significant improvements and
advancements. The first generation of wireless communication technology was
based on analog technology and offered only voice services. However, with the
advent of the second generation (2G) technology, digital communication and data
25 services became possible, and text messaging was introduced. The third generation
(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, better network coverage,
and improved security. Currently, the fifth generation (5G) technology is being
30 deployed, promising even faster data, low latency, and the ability to connect
multiple devices simultaneously. With each generation, wireless communication
3
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
[0004] The 5G core networks are based on service‐based architecture (SBA) that is
5 centred around network function (NF) services. In the said Service‐Based
Architecture (SBA), a set of interconnected Network Functions (NFs) deliver the
control plane functionality and common data repositories of the 5G network, where
each NF is authorized to access services of other NFs. Particularly, each NF can
register itself and its supported services to a Network Repository Function (NRF),
10 which is used by other NFs for the discovery of NF instances and their services.
Further, the network functions may include, but not limited to, a containerized
network function (CNF) and a virtual network function (VNF).
[0005] The CNFs are a set of small, independent, and loosely coupled services such
15 as microservices. These microservices work independently, which may increase
flexibility while reducing deployment risk. In 5G communication, cloud-native 5G
network offers the fully digitized architecture necessary for deploying new cloud
services and taking full advantage of cloud-native 5G features such as edge
computing, as well as network slicing and other services. Whereas the VNFs may
20 run in virtual machines (VMs) on common virtualization infrastructure. The VNFs
may be created on top of network function virtualization infrastructure (NFVI)
which may allocate resources like compute, storage, and networking efficiently
among the VNFs. MANO which stands for Management and Orchestration is a key
NFV architectural framework that includes all the essential management modules.
25 It coordinates network resources in NFV framework. Further, due to such vast
usage and implementation of the CNFs and the VNFs, there is a need of maintaining
such microservices and applications data in a secure way, which may not be lost
and may be retained safely from any unwanted incidents such as network service
crash, outage, cyber-attacks and any other undesirable incidents.
30
4
[0006] A network function virtualization (NFV) and software defined network
(SDN) design function module (NFV SDN) platform provides the facility to act as
a single platform to manage all the Virtual Network Functions (VNFs) and CloudNative Network Functions (CNFs) being deployed in a telecom network. As the
5 platform is completely based on micro service architecture, it is highly scalable and
will be able to handle hundreds of NFVs. The platform is completely event driven
and is based on standard REST Application Program Interfaces (APIs). A Policy
Execution Engine (PEEGN) provides NFV SDN Platform functionality to support
dynamic requirements of resource management and network service orchestration
10 in the virtualized and containerized network.
[0007] PEEGN enriches the network function virtualization (NFV) software
defined networking (SDN) server with automatic scaling and healing functionality
of network components and services. PEEGN further provides policies for resource,
15 security, availability, and scalability for both virtualized and containerized
environment.
[0008] Other services can send request to PEEGN for different events in JSON
format supported by PEEGN. There is a Orchestration and Management (OAM)
20 service which manages all the PEEGN instances in order to perform smooth
interaction with other services.
[0009] Thus, there exists an imperative need in the art for a method and a system
for facilitating communication between OAM and policy execution engine
25 (PEEGN), which the present disclosure aims to address.
SUMMARY
[0010] This section is provided to introduce certain aspects of the present disclosure
30 in a simplified form that are further described below in the detailed description.
5
This summary is not intended to identify the key features or the scope of the claimed
subject matter.
[0011] An aspect of the present disclosure may relate to a method for managing
5 one or more instances of a policy execution engine (PEEGN) unit in a network. The
method comprises receiving, by a transceiver unit, at an operation and management
(OAM) unit via an interface, a request for an operation from at least a policy
execution engine (PEEGN) unit. The request comprises a set of details related to at
least the PEEGN unit. Further, the method comprises storing, by a storage unit via
10 the OAM unit, at a database, the set of details related to at least the PEEGN unit.
Furthermore, the method comprises broadcasting, by a broadcasting unit via the
OAM unit, the set of details related to at least the PEEGN unit to one or more
microservices connected to the OAM unit.
15 [0012] In an exemplary aspect of the present disclosure, the set of details comprises
at least one of an IP port path, component broadcast context, and a subscribe
component type corresponding to at least the PEEGN unit.
[0013] In an exemplary aspect of the present disclosure, the method further
20 comprises receiving, by the transceiver unit, via the OAM unit, from at least the
PEEGN unit, and the one or more microservices, a set of fault, configuration,
accounting, performance and security (FCAPS) data. Further, the method
comprises transmitting, by the transceiver unit, via the OAM unit, to an execution
management system (EMS) unit, the received set of FCAPS data from at least the
25 PEEGN unit, and the one or more microservices.
[0014] In an exemplary aspect of the present disclosure, the request comprises at
least one of a registration request, a re-registration request, and a de-registration
request. The de-registration request is received at least in an event an instance of
30 the PEEGN unit is identified as an inactive instance.
6
[0015] In an exemplary aspect of the present disclosure, in response to the request
being at least one of the registration request, and the re-registration request, the
method comprises storing, by the storage unit via the OAM unit, at the database,
and in a list of active PEEGN instances, the set of details related to at least the
5 PEEGN. Further, the method comprises broadcasting, by the broadcasting unit via
the OAM unit, the set of details related to at least the PEEGN unit to at least a load
balancer (LB) unit connected to the OAM unit.
[0016] In an exemplary aspect of the present disclosure, in response to the request
10 being the de-registration request, the method comprises storing, by the storage unit
via the OAM unit, at the database, and in a list of inactive PEEGN instances, the
set of details related to at least the PEEGN unit. Further, the method comprises
broadcasting, by the broadcasting unit via the OAM unit, the set of details related
to at least the PEEGN unit to at least a load balancer (LB) unit connected to the
15 OAM unit.
[0017] In an exemplary aspect of the present disclosure, the interface is an PE_OA
interface.
20 [0018] In an exemplary aspect of the present disclosure, the set of details related to
at least the PEEGN unit further comprises at least one of an information of at least
the PEEGN unit, one or more instances of at least the PEEGN unit, active instances
of at least the PEEGN unit, inactive instances of at least the PEEGN unit, and new
instances of at least the PEEGN unit.
25
[0019] Another aspect of the present disclosure may relate to a system for
managing one or more instances of a policy execution engine (PEEGN) unit in a
network. The system comprises a transceiver unit. The transceiver unit is
configured to receive, at an operation and management (OAM) unit via an interface,
30 a request for an operation from at least a policy execution engine (PEEGN) unit.
The request comprises a set of details related to at least the PEEGN unit. The system
7
further comprises a storage unit. The storage unit is configured to store, via the
OAM unit, at a database, the set of details related to at least the PEEGN. The system
further comprises a broadcasting unit is further configured to broadcast, via the
OAM unit, the set of details related to at least the PEEGN unit to one or more
5 microservices connected to the OAM unit.
[0020] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for managing one or more
instances of a policy execution engine (PEEGN) unit in a network, the instructions
10 include executable code which, when executed by one or more units of a system
cause a transceiver unit to receive, at an operation and management (OAM) unit via
an interface, a request for an operation from at least a policy execution engine
(PEEGN) unit. The request comprises a set of details related to at least the PEEGN
unit. The instructions when executed by the system further cause a storage unit to
15 store, via the OAM unit, at a database, the set of details related to at least the
PEEGN. The instructions when executed by the system further cause a broadcasting
unit to broadcast, via the OAM unit, the set of details related to at least the PEEGN
unit to one or more microservices connected to the OAM unit.
20 OBJECTS OF THE DISCLOSURE
[0021] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
25 [0022] It is an object of the present disclosure to provide a system and a method for
facilitating communication between OAM service and policy execution engine
(PEEGN) via PE_OA interface.
[0023] It is yet another object of the present disclosure to provide a solution that
30 enables instance management via the PE_OA interface.
8
[0024] It is yet another object of the present disclosure to provide a solution that
enables alarm management via the PE_OA interface.
[0025] It is yet another object of the present disclosure to provide a solution that
5 enables counter management via the PE_OA interface.
[0026] It is yet another object of the present disclosure to provide a solution that
enables high availability of PEEGN.
10 DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
15 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
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
20 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.
[0028] FIG. 1 illustrates an exemplary block diagram representation of
25 management and orchestration (MANO) architecture/platform, in accordance with
exemplary implementation of the present disclosure.
[0029] 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
30 exemplary implementation of the present disclosure.
9
[0030] FIG. 3 illustrates an exemplary architecture for managing one or more
instances of a policy execution engine (PEEGN) unit in a network, in accordance
with exemplary implementations of the present disclosure.
5 [0031] FIG. 4 illustrates an exemplary block diagram of a system for managing one
or more instances of a policy execution engine (PEEGN) unit in a network, in
accordance with exemplary implementations of the present disclosure.
[0032] FIG. 5 illustrates a method flow diagram for managing one or more
10 instances of a policy execution engine (PEEGN) unit in a network, in accordance
with exemplary implementations of the present disclosure.
[0033] FIG. 6 illustrates an implementation of the method for managing one or
more instances of a policy execution engine (PEEGN) unit in a network, in
15 accordance with exemplary implementations of the present disclosure.
[0034] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
20 DETAILED DESCRIPTION
[0035] 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
10
[0036] 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.
[0037] 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
[0038] 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.
[0039] 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
“includes,” “has,” “contains,” and other similar words are used in either the detailed
11
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 [0040] 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
of microprocessors, one or more microprocessors in association with a (Digital
10 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
the system according to the present disclosure. More specifically, the processor or
15 processing unit is a hardware processor.
[0041] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
20 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,
tablet computer, wearable device or any other computing device which is capable
25 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 [0042] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
12
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
5 that may be required by one or more units of the system to perform their respective
functions.
[0043] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information
10 or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be
called.
15 [0044] 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
microprocessors in association with a DSP core, a controller, a microcontroller,
20 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0045] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
25 information or a combination thereof between units/components within the system
and/or connected with the system.
[0046] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above30 mentioned and other existing problems in this field of technology by providing a
13
method and a system of managing one or more instances of a policy execution
engine (PEEGN) unit in a network.
[0047] FIG. 1 illustrates an exemplary block diagram representation of a
5 management and orchestration (MANO) architecture/ platform [100], in
accordance with exemplary implementation of the present disclosure. The MANO
architecture [100] is developed for managing telecom cloud infrastructure
automatically, managing design or deployment design, managing instantiation of
network node(s)/ service(s) etc. The MANO architecture [100] deploys the network
10 node(s) in the form of Virtual Network Function (VNF) and Cloud-native/
Container Network Function (CNF). The system may comprise one or more
components of the MANO architecture [100]. The MANO architecture [100] is
used to auto-instantiate the VNFs into the corresponding environment of the present
disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to
15 the platform.
[0048] As shown in FIG. 1, the MANO architecture [100] comprises a user
interface layer, a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platforms foundation services
20 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
implementing features of the present disclosure.
25 [0049] The NFV and SDN design function module [104] comprises a VNF
lifecycle manager (compute) [1042], a VNF catalogue [1044], a network services
catalogue [1046], a network slicing and service chaining manager [1048], a physical
and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF
lifecycle manager (compute) [1042] is responsible for deciding on which server of
30 the communication network, the microservice will be instantiated. The VNF
lifecycle manager (compute) [1042] may manage the overall flow of incoming/
14
outgoing requests during interaction with the user. The VNF lifecycle manager
(compute) [1042] is responsible for determining which sequence to be followed for
executing the process. For e.g. in an AMF network function of the communication
network (such as a 5G network), sequence for execution of processes P1 and P2
5 etc. The VNF catalogue [1044] stores the metadata of all the VNFs (also CNFs in
some cases). The network services catalogue [1046] stores the information of the
services that need to be run. The network slicing and service chaining manager
[1048] manages the slicing (an ordered and connected sequence of network service/
network functions (NFs)) that must be applied to a specific networked data packet.
10 The physical and virtual resource manager [1050] stores the logical and physical
inventory of the VNFs. Just like the VNF lifecycle manager (compute) [1042], the
CNF lifecycle manager [1052] is used for the CNFs lifecycle management.
[0050] The platforms foundation services module [106] comprises a microservices
15 elastic load balancer [1062], an identify & access manager [1064], a command line
interface (CLI) [1066], a central logging manager [1068], and an event routing
manager [1070]. The microservices elastic load balancer [1062] is used for
maintaining the load balancing of the request for the services. The identify & access
manager [1064] is used for logging purposes. The command line interface (CLI)
20 [1066] is used to provide commands to execute certain processes which requires
changes during the run time. The central logging manager [1068] is responsible for
keeping the logs of every service. These logs are generated by the MANO platform
[100]. These logs are used for debugging purposes. The event routing manager
[1070] is responsible for routing the events, i.e., the application programming
25 interface (API) hits to the corresponding services.
[0051] The platforms core services module [108] comprises NFV infrastructure
monitoring manager [1082], an assure manager [1084], a performance manager
[1086], a policy execution engine [1088], a capacity monitoring manager [1090], a
30 release management (mgmt.) repository [1092], a configuration manager & GCT
[1094], an NFV platform decision analytics [1096], a platform NoSQL DB [1098];
15
a platform schedulers and cron jobs [1100], a VNF backup & upgrade manager
[1102], a micro service auditor [1104], and a platform operations, administration
and maintenance manager [1106]. The NFV infrastructure monitoring manager
[1082] monitors the infrastructure part of the NFs. For e.g., any metrics such as
5 CPU utilization by the VNF. The assure manager [1084] is responsible for
supervising the alarms the vendor is generating. The performance manager
[1086] is responsible for managing the performance counters. The policy execution
engine (PEEGN) [1088] is responsible for managing all the policies. The capacity
monitoring manager (CMM) [1090] is responsible for sending the request to the
10 PEEGN [1088]. The release management (mgmt.) repository (RMR) [1092] is
responsible for managing the releases and the images of all the vendor network
node. The configuration manager & (GCT) [1094] manages the configuration and
GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps
in deciding the priority of using the network resources. It is further noted that the
15 policy execution engine (PEEGN) [1088], the configuration manager & GCT
[1094] and the NPDA [1096] work together. The platform NoSQL DB [1098] is a
database for storing all the inventory (both physical and logical) as well as the
metadata of the VNFs and CNF. The platform schedulers and cron jobs [1100]
schedules the task such as but not limited to triggering of an event, traverse the
20 network graph etc. The VNF backup & upgrade manager [1102] takes backup of
the images, binaries of the VNFs and the CNFs and produces the backup on demand
in case of server failure. The micro service auditor [1104] audits the microservices.
For e.g., in a hypothetical case, instances not being instantiated by the MANO
architecture [100] using the network resources then the micro service auditor [1104]
25 audits and informs the same so that resources can be released for services running
in the MANO architecture [100], thereby assuring the services only run on the
MANO platform [100]. The platform operations, administration and maintenance
manager [1106] is used for newer instances that are spawning.
30 [0052] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122]; a generic decoder and indexer
16
(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] is responsible for handling the external services (to the MANO platform
[100]) that requires the network resources. The generic decoder and indexer (XML,
5 CSV, JSON) [1124] gets directly the data of the vendor system in the XML, CSV,
JSON format. The docker service adaptor [1126] is the interface provided between
the telecom cloud and the MANO architecture [100] for communication. The API
adapter [1128] is used to connect with the virtual machines (VMs). The NFV
gateway [1130] is responsible for providing the path to each services going
10 to/incoming from the MANO architecture [100].
[0053] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
15 implementation, the computing device [200] may also implement a method for
managing one or more instances of a policy execution engine (PEEGN) unit in a
network utilising the system. In another implementation, the computing device
[200] itself implements the method for managing one or more instances of a policy
execution engine (PEEGN) unit in a network, using one or more units configured
20 within the computing device [200], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
[0054] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
25 processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
30 main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
17
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
5 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0055] 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
10 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
15 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]. This input device typically has two degrees
20 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.
[0056] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
25 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
sequences of one or more instructions contained in the main memory [206]. Such
30 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
18
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
5
[0057] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a twoway data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
10 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
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
15 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0058] The computing device [200] can send messages and receive data, including
20 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
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,
25 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0059] The present disclosure is implemented by a system [400] (as shown in FIG.
4). In an implementation, the system [400] may include the computing device [200]
30 (as shown in FIG. 2). It is further noted that the computing device [200] is able to
perform the steps of a method [500] (as shown in FIG. 5).
19
[0060] Referring to FIG. 3, an exemplary architecture [300] for managing one or
more instances of a policy execution engine (PEEGN) unit in a network, in
accordance with exemplary implementations of the present disclosure is shown.
5
[0061] The OAM unit [302] receives the request comprising the set of details which
includes but may not be limited to the IP port path, the component broadcast
context, the subscribe component type from the PEEGN unit [306]. The request
may be one of a registration request, a re-registration request and a de-registration
10 request with the OAM unit [302].
[0062] In one example, where the request is the registration request, a web socket
connection gets established between the OAM unit [302] and the PEEGN instance
[308] using the PE_OA interface [304]. The PE_OA interface [304] broadcasts the
15 registration information to the one or more microservice instances and provides the
broadcast data to the micro service. The broadcast allows all instances to have the
latest data to allow any of the instance of the one or more microservices to handle
requests if any other microservice instance fails. This allows microservices to have
high availability (HA). Since, the OAM unit [302] contains all active PEEGN
20 instance list, so using this interface, the OAM unit [302] broadcasts it to other
microservices so that other services can send any event/request to only active
instances of PEEGN unit [306]. With the broadcast functionality of the PE_OA
interface [304], the microservices will be services by any active PEEGN instance
[308], which ensures high availability of the platform.
25
[0063] Whenever a second PEEGN instance [308] comes up, the second PEEGN
instance registers itself with the OAM unit [302]. The registration may be
performed by a hypertext transfer protocol (HTTP) request. The OAM unit [302]
adds the second PEEGN instance [308] details in the list of active instances of the
30 PE. The list of active PEEGN instances [308] may be broadcasted to the load
20
balancer and the one or more microservices which requires the details of the active
PEEGN instances [308].
[0064] Further, the OAM unit [302] may continuously monitor to check the health
5 of one or more active PEEGN instances [308] based on the list of active PEEGN
instances [308] stored in the OAM unit [302]. In one example, when any of the
PEEGN instances [308] from the list of active PEEGN instances [308] goes down,
the OAM unit [302] deregisters the PEEGN instance [308]. Further, the OAM unit
[302] adds the registered PEEGN instance [308] details to the list of inactive
10 PEEGN instances [308]. The details of the deregistered PEEGN instance may be
broadcasted to a load balancer and other services which may require details of the
deregistered PEEGN instance [308].
[0065] Referring to FIG. 4, an exemplary block diagram of a system [400] for
15 managing one or more instances of a policy execution engine (PEEGN) unit in a
network is shown, in accordance with the exemplary implementations of the present
disclosure. The system [400] comprises at least one transceiver unit [402], at least
storage unit [404] and at least one broadcasting unit [406]. Also, all of the
components/ units of the system [400] are assumed to be connected to each other
20 unless otherwise indicated below. As shown in the figures all units shown within
the system should also be assumed to be connected to each other. Also, in FIG. 4
only a few units are shown, however, the system [400] may comprise multiple such
units or the system [400] may comprise any such numbers of said units, as required
to implement the features of the present disclosure. In an implementation, the
25 system [400] may reside in a server or a network entity. In yet another
implementation, the system [400] may reside partly in the server/ network entity.
[0066] The system [400] is configured for managing one or more instances of a
PEEGN unit [306] in a network, with the help of the interconnection between the
30 components/units of the system [400]. Further, FIG. 4 is intended to be read in
conjunction with FIG. 5.
21
[0067] The transceiver unit [402] is configured to receive a request for an operation
from at least a PEEGN unit [306]. The operation may be at least one of a registration
request, a re-registration request, and a de-registration request associated with an
5 orchestration and management (OAM) unit [302]. On the NFV SDN platform, all
pertinent microservice details are stored within a central repository managed by the
OAM microservice/OAM unit [302]. The OAM unit [302] is the central connecting
point for the microservices. When a PEEGN instance [308] starts, it registers itself
with the OAM unit [302]. Further, the OAM unit [302] stores data about the
10 initiated PEEGN instances [308]. The data may include an internet protocol (IP)
address, a port, a server disk location, and the like. The port is an endpoint in a
connection that allows a system to differentiate between multiple services or
applications running on the same IP address. The server disk location refers to a
specific path on a server’s storage where files, applications, or data are stored. The
15 OAM unit [302] maintains a ping-pong communication using http requests with the
PEEGN instances [308]. The ping-pong communication may check whether an
instance from the PEEGN instances [308] is running or down. So, on request, the
OAM Unit [302] broadcasts a message to all the instances registered to it. This
message may be in JSON format and contains information whether a PEEGN
20 instance [308] is running or down. Thus, with this process OAM unit [302] gets the
availability status of the PEEGN instances [308]. If the OAM unit [302] does not
receive a response from a PEEGN instance [308], then the OAM unit [302] gets the
information that the PEEGN instance [308] is down and is inactive. The deregistration request is received at least in an event one or more instances of the
25 PEEGN unit [306] are identified as an inactive instance.
[0068] The request comprises a set of details related to at least the PEEGN unit
[306]. The set of details comprises at least one of an IP port path, component
broadcast context, and a subscribe component type corresponding to at least the
30 PEEGN unit [306]. The IP port path refers to specific port on an Internet protocol
(IP) address used for communication. The IP port path helps to distinguish the types
22
of traffic. The subscribe component type refers to a type of component that
subscribes to receive certain data or messages.
[0069] The set of details related to at least the PEEGN unit [306] further comprises
5 at least one of an information of at least the PEEGN unit [306], one or more
instances of at least the PEEGN unit [306], active instances of at least the PEEGN
unit [306], inactive instances of at least the PEEGN unit [306], and new instances
of at least the PEEGN unit [306].
10 [0070] The request is received at an operation and management (OAM) unit via an
interface. The interface is an PE_OA interface [304]. The PE_OA interface [304]
is a central connecting point of the PEEGN unit [306] with the OAM unit [302].
The PEEGN unit [306] registers, deregisters or reregisters themselves with the
OAM unit using the PE_OA interface [304].
15
[0071] In response to the request being at least one of the registration request and
the re-registration request, the storage unit [404] is configured to further store, at
the database, and in a list of active PEEGN instances [308], the set of details related
to at least the PEEGN unit [306]. Further, the broadcasting unit [406] is configured
20 to further broadcast, via the OAM unit [302], the set of details related to at least the
PEEGN unit [306] to at least a load balancer (LB) unit connected to the OAM unit
[302]. Whenever a new PEEGN instance [308] comes up it registers itself with the
OAM unit [302] via http request. Thereafter, the OAM unit [302] adds that instance
details in active instances list of PEEGN and broadcasts details to load balancer and
25 other services which require the details of PEEGN instances [308].
[0072] In response to the request being the de-registration request, the storage unit
[404] is further configured to store, at the database, and in a list of inactive PEEGN
instances, the set of details related to at least the PEEGN unit [306]. Further, the
30 broadcasting unit [406] is configured to broadcast, the set of details related to at
least the PEEGN unit [306] to at least a load balancer (LB) unit connected to the
23
OAM unit [302]. The OAM unit [302] continuously checks the health of active
PEEGN instances [308] via http request. Whenever any PEEGN instance [308]
goes down, the OAM unit [302] deregisters that instance and adds that instance
details in inactive instances list of PEEGN unit [306] and broadcasts details to load
5 balancer and other services which require the details of PEEGN unit [306].
[0073] As described, the storage unit [404] is configured to store, at a database, the
set of details related to at least the PEEGN unit [306] received in the request.
10 [0074] The broadcasting unit [406] is configured to broadcast the set of details to
one or more microservices connected to the OAM unit [302] via the PE_OA
interface [304]. The broadcast of the set of details refers to sending a list of latest
active PEEGN instances [308] and a list of latest inactive PEEGN instances [308]
to each of the load balancer connected to each of the one or more microservices to
15 allow any of the load balancer to select an active PEEGN instance [308] to handle
the request. This allows the PEEGN instances [308] to have high availability (HA).
The PE_OA interface [304] works in a high availability mode and if one PEEGN
instance [308] goes down during request processing then next available instance
will take care of this request. The OAM unit [302] contains all active PEEGN
20 instance list and using this interface the OAM unit broadcasts the list to other
microservices so that other service can send any event/request to only active
instances of PEEGN unit [306]. This way with the functionality of the PE_OA
interface [304], the NFV SDN platform provides high availability to all
microservices.
25
[0075] The transceiver unit [402] is further configured to receive a set of fault,
configuration, accounting, performance and security (FCAPS) data. The set of fault,
configuration, accounting, performance and security (FCAPS) data may be received
from the one or more microservices. In one example, the FCAPS request refers to
30 detecting and managing faults at each of the PEEGN instance [308] or each of the
one or more microservices. Further the FCAPS request corresponds to monitoring
24
and managing changes in configuration of each of the PEEGN instance [308] and
each of the one or more microservices. Further, the FCAPS request may track usage
data and allocate costs to a user accordingly. The user may be one of a system
operator or a network operator. Furthermore, the FCAPS request corresponds to
5 monitoring performance metrics like one of a latency, bandwidth, etc. to ensure that
each of the PEEGN instance [308] or each of the microservice instance is
performing properly. Further, the FCAPS request may implement security policies
and monitor each of the PEEGN instances [308] and each of the one or more
microservices for any potential breach to ensure security of the PEEGN unit [306]
10 and the one or more microservices. The PE_OA interface [304] is used to send
FCAPS request to respective micro service instances and also consolidates all the
micro service FCAPS responses and sends the consolidated response to Element
Management System (EMS). The EMS is an application to monitor each of the
PEEGN instance [308] from the one or more PEE instances to gather the FCAPS
15 data from the PEEGN unit [306]. The fundamental functionality of the EMS is
divided into five classifications that are fault, configuration, accounting,
performance and security (FCAPS). The EMS is configured to gather, merge and
normalize the FCAPS data from the PEEGN unit [306] to be easily readable by the
user. Further, the EMS provides a powerful user interface for centralized
20 management. Some of the key features of EMS includes Performance Management,
Fault Management, Backup and Restore, Configuration Management, Management
Dashboard etc.
[0076] Further, the transceiver unit [402] is configured to transmit, to an element
25 management system (EMS) unit, the received set of FCAPS data from at least the
PEEGN unit [306] and the one or more microservices. The PE_OA interface [304]
is used to send FCAPS request from the one or more microservice instances or the
PEEGN unit [306], where the PE_OA interface [304] may consolidate all the micro
service FCAPS responses and send the consolidated response to the EMS unit.
30
25
[0077] Referring to FIG. 5, an exemplary method flow diagram [500] for managing
one or more instances of a policy execution engine (PEEGN) unit in a network, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [500] is performed by the system [400]. Further, in
5 an implementation, the system [400] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 5, the method [500]
starts at step [502].
[0078] At step [504], the method comprises receiving, by a transceiver unit [402],
10 at an operation and management (OAM) unit [302] via an interface, a request for
an operation from at least a PEEGN unit [306].
[0079] The operation may be at least one of a registration request, a re-registration
request, and a de-registration request associated with registration, re-registration or
15 de-registration of the PEEGN unit [306] with an orchestration and management
(OAM) unit [302]. The OAM unit [302] is a central connecting point for each of
one or more microservices. The de-registration request is received at least in an
event one or more instances of the PEEGN unit [306] are identified as an inactive
instance.
20
[0080] The request comprises a set of details related to at least the PEEGN unit
[306]. The set of details comprises at least one of an IP port path, component
broadcast context, and a subscribe component type corresponding to at least the
PEEGN unit [306]. The IP port path refers to specific port on an Internet protocol
25 (IP) address used for communication. The IP port path helps to distinguish the types
of traffic. The subscribe component type refers to a type of component that
subscribes to receive certain data or messages.
[0081] The set of details related to at least the PEEGN unit [306] further comprises
30 at least one of an information of at least the PEEGN unit [306], one or more
instances of at least the PEEGN unit [306], active instances of at least the PEEGN
26
unit [306], inactive instances of at least the PEEGN unit [306], and new instances
of at least the PEEGN unit [306].
[0082] The request is received at an operation and management (OAM) unit via the
5 interface. The interface is an PE_OA interface [304]. The PE_OA interface [304]
is a central connecting point of the PEEGN unit [306] with the OAM unit [302].
The PEEGN unit [306] registers, deregisters or reregisters themselves with the
OAM unit [302] using the PE_OA interface [304].
10 [0083] The set of details related to at least the PEEGN unit [306] further comprises
at least one of an information of at least the PEEGN unit [306], one or more
instances of at least the PEEGN unit [306] [410], active instances of at least the
PEEGN unit [306], inactive instances of at least the PEEGN unit [306], and new
instances of at least the PEEGN unit [306].
15
[0084] In response to the request being at least one of the registration request, and
the re-registration request, the method comprises storing, by the storage unit [404]
via the OAM unit [302], at the database, and in a list of active PEEGN instances
[308], the set of details related to at least the PEEGN [306]. The method further
20 comprises broadcasting, by the broadcasting unit [406] via the OAM unit [302], the
set of details related to at least the PEEGN unit [306] to at least a load balancer
(LB) unit connected to the OAM unit [302].
[0085] In response to the request being the de-registration request, the method
25 comprises storing, by the storage unit [404] via the OAM unit [302], at the database,
and in a list of inactive PEEGN instances [308], the set of details related to at least
the PEEGN unit. The method further comprises broadcasting, by the broadcasting
unit [406] via the OAM unit [302], the set of details related to at least the PEEGN
unit [306] to at least a load balancer (LB) unit connected to the OAM unit [302].
30
27
[0086] At step [506], the method comprises storing, by a storage unit [404] via the
OAM unit [302], at a database, the set of details related to at least the PEEGN unit
[306].
5 [0087] At step [508], the method comprises broadcasting, by a broadcasting unit
[406] via the OAM unit [302], the set of details related to at least the PEEGN unit
[306] to one or more microservices connected to the OAM unit [302] by the PE_OA
interface [304]. The broadcast of the set of details refers to sending a list latest active
PEEGN instances [308] and a list of latest inactive PEEGN instances [308] to each
10 of the load balancer connected to each of the one or more microservices to allow
any of the load balancer to select an active PEEGN instance [308] to handle the
request. This allows the PEEGN instances [308] to have high availability (HA).
[0088] The method comprises receiving, by the transceiver unit [402], via the OAM
15 unit [302], from at least the PEEGN unit [306] and the one or more microservices,
a set of fault, configuration, accounting, performance and security (FCAPS) data.
The set of fault, configuration, accounting, performance and security (FCAPS) data
may be received from the one or more microservices. In one example, the FCAPS
request refers to detecting and managing faults at each of the PEEGN instance [308]
20 or each of the one or more microservices. Further the FCAPS request corresponds
to monitoring and managing changes in configuration of each of the PEEGN
instance and each of the one or more microservices. Further, the FCAPS request
may track usage data and allocate costs to a user accordingly. The user may be one
of a system operator or a network operator. Furthermore, the FCAPS request
25 corresponds to monitoring performance metrics like one of a latency, bandwidth,
etc. to ensure that each of the PEEGN instance [308] or each of the microservice
instance is performing properly. Further, the FCAPS request may implement
security policies and monitor each of the PEEGN instances [308] and each of the
one or more microservices for any potential breach to ensure security of the PEEGN
30 unit [306] and the one or more microservices.
28
[0089] Further, the method comprises transmitting, by the transceiver unit [402],
via the OAM unit [302], to an execution management system (EMS) unit, the
received set of FCAPS data from at least the PEEGN unit, and the one or more
microservices. The PE_OA interface [304] is used to send FCAPS request from the
5 one or more microservice instances or the PEEGN unit [306], where the PE_OA
interface [304] may consolidate all the micro service FCAPS responses and send
the consolidated response to the EMS unit. The EMS is an application to monitor
each of the PEEGN instance [308] from the one or more PEE instances [308] to
gather the FCAPS data from the PEEGN unit [306]. The fundamental functionality
10 of the EMS is divided into five classifications that are fault, configuration,
accounting, performance and security (FCAPS). The EMS is configured to gather,
merge and normalize the FCAPS data from the PEEGN unit to be easily readable
by the user. Further, the EMS provides a powerful user interface for centralized
management. Some of the key features of EMS includes Performance Management,
15 Fault Management, Backup and Restore, Configuration Management, Management
Dashboard etc.
[0090] The method [500] terminates at step [510].
20 [0091] Referring to FIG. 6, an implementation of the method [600] for managing
FCAPS request at one or more instances of a policy execution engine (PEEGN) unit
in a network, in accordance with exemplary implementations of the present
disclosure is shown.
25 [0092] The PE_OA interface [304] is also used to fetch the FCAPS response from
the PEEGN unit [306] and the one or more microservices. The FCAPS response
helps to manage faults, configuration, accounting, performance and security related
functionality at the PEEGN unit [306] and the one or more microservices.
30 [0093] In one example, the FCAPS request refers to detecting and managing faults
at each of the PEEGN instance [308] or each of the one or more microservices.
29
Further the FCAPS request corresponds to monitoring and managing changes in
configuration of each of the PEEGN instance [308] and each of the one or more
microservices. Further, the FCAPS request may track usage data and allocate costs
to a user accordingly. The user may be one of a system operator or a network
5 operator. Furthermore, the FCAPS request corresponds to monitoring performance
metrics like one of a latency, bandwidth, etc. to ensure that each of the PEEGN
instance [308] or each of the microservice instance is performing properly. Further,
the FCAPS request may implement security policies and monitor each of the
PEEGN instances [308] and each of the one or more microservices for any potential
10 breach to ensure security of the PEEGN unit [306] and the one or more
microservices.
[0094] Further, based on the FCAPS response, a set of performance counter data
and a set of alarm data may be monitored to generate an alarm. The set of
15 performance counter data corresponds to collection and analysis of the performance
metrics and the set of alarm data refers to monitoring faults at each of the PEEGN
instances [308] or the one or more microservices. Based on detection of a fault, the
alarm may be generated to alert the load balancer. Based on the alarm, the load
balancer may not send the request to a faulty PEEGN instance [308] and direct the
20 request to a healthy or active PEEGN instance [308].
[0095] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for managing one or more instances of a policy
execution engine (PEEGN) unit [306] in a network, the instructions include
25 executable code which, when executed by one or more units of a system, cause a
transceiver unit [402] to receive, at an operation and management (OAM) unit [302]
via an interface, a request for an operation from at least a PEEGN unit [306]. The
request comprises a set of details related to at least the PEEGN unit [306]. The
instructions when executed by the system further cause a storage unit [404] to store,
30 via the OAM unit [302], at a database, the set of details related to at least the PEEGN
unit [306]. The instructions when executed by the system further cause a
30
broadcasting unit [406] to broadcast, via the OAM unit [302], the set of details
related to at least the PEEGN unit [306] to one or more microservices connected to
the OAM unit [302] via the interface.
5 [0096] As is evident from the above, the present disclosure provides a technically
advanced solution for managing one or more instances of a policy execution engine
(PEEGN) unit in a network. The present solution provides a system and a method
for facilitating communication between OAM server and policy execution engine
server. The present disclosure further provides a solution that enables instance
10 management. The present disclosure provides a solution to enable alarm and
counter management. The present disclosure further provides a solution that
enables high availability of PEEGN instances.
[0097] While considerable emphasis has been placed herein on the disclosed
15 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
20 and non-limiting.
[0098] 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
25 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
30 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
31
We Claim:
1. A method [500] for managing one or more instances of a policy execution
engine (PEEGN) unit [306] in a network, the method comprising:
5 - receiving, by a transceiver unit [402], at an operation and management
(OAM) unit via an interface, a request for an operation from at least a
PEEGN unit [306], wherein the request comprises a set of details related
to at least the PEEGN unit [306];
- storing, by a storage unit [404] via the OAM unit [302], at a database,
10 the set of details related to at least the PEEGN unit [306]; and
- broadcasting, by a broadcasting unit [406] via the OAM unit [302], the
set of details related to at least the PEEGN unit [306] to one or more
microservices connected to the OAM unit [302].
15 2. The method [500] as claimed in claim 1, wherein the set of details comprises
at least one of an IP port path, component broadcast context, and a subscribe
component type corresponding to at least the PEEGN unit [306].
3. The method [500] as claimed in claim 1, wherein the method comprises:
20 - receiving, by the transceiver unit [402], via the OAM unit [302], from
at least the PEEGN unit [306], and the one or more microservices, a set
of fault, configuration, accounting, performance and security (FCAPS)
data; and
- transmitting, by the transceiver unit [402], via the OAM unit [302], to
25 an element management system (EMS) unit, the received set of FCAPS
data from at least the PEEGN unit [306], and the one or more
microservices.
4. The method [500] as claimed in claim 1, wherein the request comprises at
30 least one of a registration request, a re-registration request, and a de-
32
registration request, wherein the de-registration request is received at least in
an event an instance of the PEEGN unit [306] is identified as an inactive
instance.
5 5. The method [500] as claimed in claim 4, wherein, in response to the request
being at least one of the registration request, and the re-registration request,
the method comprises:
- storing, by the storage unit [404] via the OAM unit [302], at the
database, and in a list of active PEEGN instances [308], the set of details
10 related to at least the PEEGN unit [306]; and
- broadcasting, by the broadcasting unit [406] via the OAM unit [302],
the set of details related to at least the PEEGN unit [306] to at least a
load balancer (LB) unit connected to the OAM unit [302].
15 6. The method [500] as claimed in claim 4, wherein, in response to the request
being the de-registration request, the method comprises:
- storing, by the storage unit [404] via the OAM unit [302], at the
database, and in a list of inactive PEEGN instances [308], the set of
details related to at least the PEEGN unit [306]; and
20 - broadcasting, by the broadcasting unit [406] via the OAM unit [302],
the set of details related to at least the PEEGN unit [306] to at least a
load balancer (LB) unit connected to the OAM unit [302].
7. The method [500] as claimed in claim 1, wherein the interface is an PE_OA
25 interface [304].
8. The method [500] as claimed in claim 1, wherein the set of details related to
at least the PEEGN unit [306] further comprises at least one of an information
of at least the PEEGN unit [306], one or more instances of at least the PEEGN
30 unit [306], active instances of at least the PEEGN unit [306], inactive
33
instances of at least the PEEGN unit [306], and new instances of at least the
PEEGN unit [306].
9. A system [400] for managing one or more instances of a policy execution
5 engine (PEEGN) unit in a network, the system comprising:
- a transceiver unit [402] configured to receive, at an operation and
management (OAM) unit [402] via an interface, a request for an
operation from at least PEEGN unit [306], wherein the request
comprises a set of details related to at least the PEEGN unit [306];
10 - a storage unit [404] configured to store, via the OAM unit [302], at a
database, the set of details related to at least the PEEGN unit [306]; and
- a broadcasting unit [406] configured to broadcast, via the OAM unit
[302], the set of details related to at least the PEEGN unit [306] to one
or more microservices connected to the OAM unit [302].
15
10. The system [400] as claimed in claim 9, wherein the set of details comprises
at least one of an IP port path, component broadcast context, and a subscribe
component type corresponding to at least the PEEGN unit [306].
20 11. The system [400] as claimed in claim 9, wherein
- the transceiver unit [402], further configured to receive, via the OAM
unit [302], from at least the PEEGN unit [306], and the one or more
microservices, a set of fault, configuration, accounting, performance and
security (FCAPS) data; and
25 - the transceiver unit [402] further configured to transmit, via the OAM
unit [302], to an element management system (EMS) unit, the received
set of FCAPS data from at least the PEEGN unit [306], and the one or
more microservices.
34
12. The system [400] as claimed in claim 9, wherein the request comprises at least
one of a registration request, a re-registration request, and a de-registration
request. wherein the de-registration request is received at least in an event an
instance of the PEEGN unit [306] is identified as an inactive instance.
5
13. The system [400] as claimed in claim 12, wherein, in response to the request
being at least one of the registration request, and the re-registration request,
the system comprises:
- the storage unit [404] configured to further store, via the OAM unit
10 [302], at the database, and in a list of active PEEGN instances [308], the
set of details related to at least the PEEGN unit [306]; and
- the broadcasting unit [406] configured to further broadcast, via the
OAM unit [302], the set of details related to at least the PEEGN unit
[306] to at least a load balancer (LB) unit connected to the OAM unit
15 [302].
14. The system [400] as claimed in claim 12, wherein, in response to the request
being the de-registration request, the system comprises:
- the storage unit [404] configured to further store, via the OAM unit
20 [302], at the database, and in a list of inactive PEEGN instances [308],
the set of details related to at least the PEEGN unit [306]; and
- the broadcasting unit [406] configured to further broadcast, via the
OAM unit [302], the set of details related to at least the PEEGN unit
[306] to at least a load balancer (LB) unit connected to the OAM unit
25 [302].
15. The system [400] as claimed in claim 9, wherein the interface is an PE_OA
interface [304].
35
16. The system [400] as claimed in claim 9, wherein the set of details related to at least the PEEGN unit [306] further comprises at least one of an information of at least the PEEGN unit [306], one or more instances of at least the PEEGN unit [306], active instances of at least the PEEGN unit [306], inactive instances of at least the PEEGN unit [306], and new instances of at least the PEEGN unit [306].