1
FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
5 THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
10 “METHODS AND SYSTEMS FOR MANAGING DYNAMIC RESOURCE
MANAGEMENT AND ORCHESTRATION IN A NETWORK”
15 We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre
Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
20
The following specification particularly describes the invention and the manner in
which it is to be performed.
25
2
METHODS AND SYSTEMS FOR MANAGING DYNAMIC RESOURCE
MANAGEMENT AND ORCHESTRATION IN A NETWORK
5
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to network
resource management systems. More particularly, embodiments of the present
10 disclosure relate to methods and systems for managing dynamic resource
management and orchestration in a network.
BACKGROUND
15 [0002] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may
include certain aspects of the art that may be related to various features of the
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,
20 and not as admissions of the prior art.
[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
25 based on analog technology and offered only voice services. However, with the
advent of the second-generation (2G) technology, digital communication and data
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
30 wireless communication with faster data speeds, better network coverage, and
3
improved security. Currently, the fifth generation (5G) technology is being
deployed, promising even faster data speeds, low latency, and the ability to connect
multiple devices simultaneously. With each generation, wireless communication
technology has become more advanced, sophisticated, and capable of delivering
5 more services to its users.
[0004] The evolution of telecommunications and networking technologies has
led to the development of Network Function Virtualization (NFV) and SoftwareDefined Networking (SDN) platforms, which offer greater flexibility, scalability,
10 and efficiency in managing network services. These platforms enable the
virtualization of network functions (VNFs) and containerized network functions
(CNFs), allowing for the efficient allocation and management of resources.
[0005] In NFV and SDN environments, effective management of policies
15 governing resource allocation, security, availability, and scalability is critical for
optimizing network performance and ensuring service reliability. These policies
define the rules and configurations that govern how network resources are
allocated, how security measures are applied, and how the network responds to
changes in demand or failures.
20
[0006] However, making configuration changes in the policies may impact
services. If a user wishes to change the configuration parameter, the user has to
change in a configuration sheet which a Policy Execution Engine (PE) used during
startup, and then restart the application.
25
[0007] Further, over the period of time various solutions have been developed
to effectively manage the policies. However, the existing solution does not allow a
user to change the parameters of the policies without restarting the application. For
example, the existing solutions do not allow on demand fault, configuration,
30 accounting, performance, and security (FCAPS) management. In addition, the
4
existing solutions do not allow on demand registration/deregistration with
Orchestration and Management (OAM) service.
[0008] Thus, there exists an imperative need in the art to provide a method and
5 system to effectively configure the parameters of the policies after the startup of the
application, which the present disclosure aims to address.
SUMMARY
10 [0009] This section is provided to introduce certain aspects of the present
disclosure in a simplified form that are further described below in the detailed
description. This summary is not intended to identify the key features or the scope
of the claimed subject matter.
15 [0010] An aspect of the present disclosure may relate to a method for managing
dynamic resource management and orchestration in a network. The method
comprises receiving, at a transceiver unit by a user interface (UI), an access request
from one or more user devices to access a policy execution engine (PEEGN) unit.
The method further comprises loading, by a loading unit, one or more commands
20 associated with the policy execution engine (PEEGN) unit. The method further
comprises receiving, by the transceiver unit via the UI, a selection of a command
from the one or more user devices, wherein the selection further comprises a user
input for the command. The method further comprises transmitting by the
transceiver unit, a service request to the policy execution engine (PEEGN) unit
25 based on the received selection. The method further comprises receiving, by the
transceiver unit, a service response from the policy execution engine (PEEGN) unit.
The method further comprises displaying, by a display unit, the service response
received from the policy execution engine (PEEGN) unit.
5
[0011] In an exemplary aspect of the present disclosure, the network comprises
one or more Virtual Network Functions (VNFs) and one or more Containerized
Network Functions (CNFs).
5 [0012] In another exemplary aspect of the present disclosure, the one or more
commands associated with the policy execution engine (PEEGN) unit comprises of
a command for change in configuration parameter, a command for monitoring one
or more performance counter, a command for monitoring severity alarm, and a
command for one of a registration and a deregistration of one or more instances of
10 the policy execution engine (PEEGN) unit associated with an orchestration
manager unit.
[0013] In another exemplary aspect of the present disclosure, the method
further comprises extracting, by the policy execution engine (PEEGN) unit, a
15 compute size information from a physical - virtual inventory management unit. The
method then comprises managing, by the policy execution engine (PEEGN) unit,
an instantiation and a scaling functionality for one or more virtual network
functions based on the compute size information.
20 [0014] In another exemplary aspect of the present disclosure, the user interface
is a command line interface.
[0015] In another exemplary aspect of the present disclosure, the command line
interface prompts the user to provide login credentials.
25
[0016] In another exemplary aspect of the present disclosure, the command line
interface enables the user to select a command from a list of commands associated
with the policy execution engine (PEEGN) unit.
6
[0017] In another exemplary aspect of the present disclosure, the method
further comprises receiving, by the transceiver unit via the UI, the selection of
commands to retrieve information of one or more connected components from the
policy execution engine (PEEGN) unit. Then the method comprises transmitting,
5 by the transceiver unit, a service request to the policy execution engine (PEEGN)
unit based on the received selection. Thereafter, the method comprises receiving,
by the transceiver unit via the UI, a service response from the policy execution
engine (PEEGN) unit. The service response comprises information regarding one
or more connected components. The method comprises displaying, by the display
10 unit, the service response received from the policy execution engine (PEEGN) unit.
[0018] In another exemplary aspect of the present disclosure, the UI works in
a high availability mode, and wherein in the high availability mode if an instance
of the policy execution engine (PEEGN) unit went down during processing of a
15 request, then a next available instance of the policy execution engine (PEEGN) unit
processes the request.
[0019] Another aspect of the present disclosure may relate to a system for
managing dynamic resource management and orchestration in a network. The
20 system comprises a transceiver unit, a loading unit, and a display unit connected to
each other. The transceiver unit is configured to receive via a user interface (UI), an
access request from one or more user devices to access a policy execution engine
(PEEGN) unit. The loading unit is configured to load one or more commands
associated with the policy execution engine (PEEGN) unit. The transceiver unit is
25 further configured to receive via the UI, a selection of a command from the one or
more user devices, wherein the selection further comprises a user input for the
command. The transceiver unit is further configured to transmit a service request to
the policy execution engine (PEEGN) unit based on the received selection. The
transceiver unit is further configured to receive a service response from the policy
30 execution engine (PEEGN) unit. The display unit is configured to display the
service response received from the policy execution engine (PEEGN) unit.
7
[0020] Yet another aspect of the present disclosure may relate to a User
Equipment (UE) comprising a memory, and a processor connected to the memory.
The processor is configured to receive via a user interface (UI), an access request
5 from one or more user devices to access a policy execution engine (PEEGN) unit.
The processor is further configured to load one or more commands associated with
the policy execution engine (PEEGN) unit. The processor is further configured to
receive via the UI, a selection of a command from the one or more user devices,
wherein the selection further comprises a user input for the command. The
10 processor is further configured to transmit a service request to the policy execution
engine (PEEGN) unit based on the received selection. The processor is further
configured to receive a service response from the policy execution engine (PEEGN)
unit. The processor is further configured to enable a display of the service response
received from the policy execution engine (PEEGN) unit.
15
[0021] Yet another aspect of the present disclosure may relate to a nontransitory computer readable storage medium storing one or more instructions for
managing dynamic resource management and orchestration in a network, the one
or more instructions include executable code which, when executed by one or more
20 units of a system, causes the one or more units to perform certain functions. The
one or more instructions when executed causes a transceiver unit to receive via a
user interface (UI), an access request from one or more user devices to access a
policy execution engine (PEEGN) unit. The one or more instructions when executed
further causes a loading unit to load one or more commands associated with the
25 policy execution engine (PEEGN) unit. The one or more instructions when executed
further causes the transceiver unit to receive via the UI, a selection of a command
from the one or more user devices. The selection further comprises a user input for
the command. The one or more instructions when executed further causes the
transceiver unit to transmit a service request to the policy execution engine
30 (PEEGN) unit based on the received selection. The one or more instructions when
executed further causes the transceiver unit to receive a service response from the
8
policy execution engine (PEEGN) unit. The one or more instructions when executed
further causes a display unit to display the service response received from the policy
execution engine (PEEGN) unit.
5 OBJECTS OF THE DISCLOSURE
[0022] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
10 [0023] It is an object of the present disclosure to provide a system and a method
for managing dynamic resource management and orchestration in a network.
[0024] It is another object of the present disclosure to provide a system and a
method to provide an interface to configure the policies in a non-service impacting
15 manner.
[0025] It is another object of the present disclosure to provide a system and
method to provide the interface that enables configuration of policies in a less timeconsuming manner.
20
[0026] It is yet another object of the present disclosure to provide a solution
for easier monitoring of FCAPS for all policy instances.
[0027] It is yet another object of the present invention to provide a solution to
25 update restricted information at Policy Execution Engine (PEEGN).
[0028] It is yet another object of the present invention to provide a solution for
on demand registration/deregistration with Orchestration and Management (OAM)
service.
9
BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The accompanying drawings, which are incorporated herein, and
5 constitute a part of this disclosure, illustrate exemplary embodiments of the
disclosed methods and systems in which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Also, the embodiments shown in the figures are
10 not to be construed as limiting the disclosure, but the possible variants of the method
and system according to the disclosure are illustrated herein to highlight the
advantages of the disclosure. It will be appreciated by those skilled in the art that
disclosure of such drawings includes disclosure of electrical components or
circuitry commonly used to implement such components.
15
[0030] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture/platform in accordance with
exemplary implementation of the present disclosure.
20 [0031] 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.
[0032] FIG. 3 illustrates an exemplary block diagram of an environment used
25 for managing dynamic resource management and orchestration in a network, in
accordance with exemplary implementations of the present disclosure.
[0033] FIG. 4 illustrates an exemplary block diagram of a system for managing
dynamic resource management and orchestration in the network, in accordance with
30 exemplary implementations of the present disclosure.
10
[0034] FIG. 5 illustrates a method flow diagram for managing dynamic
resource management and orchestration in the network, in accordance with
exemplary implementations of the present disclosure.
5
[0035] FIG. 6 illustrates a call flow diagram for managing dynamic resource
management and orchestration in the network, in accordance with exemplary
implementations of the present disclosure.
10 [0036] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
15 [0037] 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
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
20 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.
[0038] The ensuing description provides exemplary embodiments only, and is
25 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. It should be understood that various changes may be made in the
function and arrangement of elements without departing from the spirit and scope
30 of the disclosure as set forth.
11
[0039] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one
of ordinary skill in the art that the embodiments may be practiced without these
5 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.
[0040] It should be noted that the terms "first", "second", "primary",
10 "secondary", "target" and the like, herein do not denote any order, ranking, quantity,
or importance, but rather are used to distinguish one element from another.
[0041] 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
15 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 concurrently. In addition, the order of the operations may be re-arranged.
A process may be terminated when its operations are completed but could also have
additional steps that may not be included in the figures.
20
[0042] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
25 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
12
similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0043] As used herein, a “processing unit” or “processor” or “operating
5 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 Signal Processing (DSP) core, a controller, a
10 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 processing unit is a hardware
15 processor.
[0044] As used herein, “a user equipment”, “a user device”, “a smart-userdevice”, “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 unit(s) which
are required to implement the features of the present disclosure.
[0045] As used herein, “storage unit” or “memory unit” refers to a machine or
30 computer-readable medium including any mechanism for storing information in a
13
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.
[0046] As used herein “interface” or “user interface” refers to a shared
boundary across which two or more separate components of a system exchange
10 information or data. The interface may also refer 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 [0047] 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.
[0048] As used herein the transceiver unit includes at least one receiver and at
least one transmitter configured respectively for receiving and transmitting data,
25 signals, information or a combination thereof between units/components within the
system and/or connected with the system.
[0049] 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
14
method and a system of managing dynamic resource management and orchestration
in the network.
[0050] 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] may be developed for managing telecom cloud infrastructure automatically,
managing design or deployment design, managing instantiation of a network
node(s) etc/service(s). The MANO architecture [100] deploys the network node(s)
10 in the form of Virtual Network Function (VNF) and Cloud-native/ Container
Network Function (CNF). The system as provided by the present disclosure may
comprise one or more components of the MANO architecture [100]. The MANO
architecture [100] may be used to automatically instantiate the VNFs into the
corresponding environment of the present disclosure so that it could help in
15 onboarding other vendor(s) CNFs and VNFs to the platform. In an implementation,
the system may comprise a NFV Platform Decision Analytics (NPDA) [1096]
component.
[0051] As shown in FIG. 1, the MANO architecture [100] comprises a user
20 interface layer [102], a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platform foundation services
module [106], a platform core services module [108] and a platform resource
adapters and utilities module [112] All the components may be assumed to be
connected to each other in a manner as obvious to the person skilled in the art for
25 implementing features of the present disclosure.
[0052] The NFV and SDN design function module [104] comprises a network
manager [1042], a VNF catalog [1044], a network services catalog [1046], a
network slicing and service chaining manager [1048], a physical and virtual
30 resource manager [1050] and a CNF lifecycle manager [1052]. The network
15
manager [1042] may be responsible for deciding on which server of the
communication network the microservice may be instantiated. The network
manager [1042] may manage the overall flow of incoming/ outgoing requests
during interaction with the user. The network manager may have a VNF lifecycle
5 manager and the CNF lifecycle manager in case the network is working utilising
the VNF and CNF. The network manager [1042] may be responsible for
determining which sequence to be followed for executing the process. For e.g. in
an AMF network function of the communication network (such as a 5G network),
sequence for execution of processes P1 and P2 etc. The VNF catalog [1044] stores
10 the metadata of all the VNFs (also CNFs in some cases). The network services
catalog [1046] stores the information of the services that need to be run. The
network slicing and service chaining manager [1048] manages the slicing (an
ordered and connected sequence of network service/ network functions (NFs)) that
must be applied to a specific networked data packet. The physical and virtual
15 resource manager [1050] stores the logical and physical inventory of the VNFs. Just
like the network manager [1042], the CNF lifecycle manager [1052] may be
similarly used for the CNFs lifecycle management.
[0053] The platforms foundation services module [106] comprises a
20 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 manager [1064] may be used for logging purposes. The command
25 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 may be used for debugging
purposes. The event routing manager [1070] may be responsible for routing the
30 events i.e., the application programming interface (API) hits to the corresponding
services.
16
[0054] 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
5 monitoring manager [1090], a release management (mgmt.) repository [1092], a
configuration manager & golden configuration template (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 [1102], a
microservice auditor [1104], and a platform operations, administration and
10 maintenance manager [1106]. The NFV infrastructure monitoring manager [1082]
may monitor 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
[1086] may be responsible for managing the performance counters. The policy
15 execution engine (PEEGN) [1088] may be responsible for managing all the
policies. The capacity monitoring manager (CMM) [1090] may be responsible for
sending the request to the PEEGN [1088]. The release management repository
(RMR) [1092] may be responsible for managing the releases and the images of all
of the vendor’s network nodes. The configuration manager & GCT [1094] manages
20 the configuration and GCT of all the vendors. The NFV platform decision analytics
(NPDA) [1096] helps in deciding the priority of using the network resources. It is
further noted that the policy execution engine (PEEGN) [1088], the configuration
manager & (GCT) [1094] and the (NPDA) [1096] work together. The platform
NoSQL DB [1098] may be a platform database for storing all the inventory (both
25 physical and logical) as well as the metadata of the VNFs and CNF. It may be noted
that the platform NoSQL DB [1098] may be just a narrower implementation of the
present disclosure, and any other kind of structure for the database may be
implemented for the platform database such as relational or non-relational database.
The platform schedulers and cron jobs [1100] may schedule the task such as but not
30 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
17
the CNFs and produces those backups on demand in case of server failure. The
microservice auditor [1104] audits the microservices. For e.g., in a hypothetical
case, instances not being instantiated by the MANO architecture [100] may be using
the network resources. In such case, the microservice auditor [1104] audits and
5 informs the same so that resources can be released for services running in the
MANO architecture [100]. The audit assures that the services only run on the
MANO platform [100]. The platform operations, administration and maintenance
manager [1106] may be used for newer instances that are spawning.
10 [0055] The platform resource adapters and utilities module [112] further
comprises a platform external API adapter and gateway [1122], a generic decoder
and indexer (XML, CSV, JSON) [1124], a docker service adapter [1126], an API
adapter [1128], and a NFV gateway [1130]. The platform external API adapter and
gateway [1122] may be responsible for handling the external services (to the
15 MANO platform [100]) that requires the network resources. The generic decoder
and indexer (XML, CSV, JSON) [1124] may get directly the data of the vendor
system in the XML, CSV, JSON format. The docker service adapter [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
20 machines (VMs). The NFV gateway [1130] may be responsible for providing the
path to each service going to/incoming from the MANO architecture [100].
[0056] The Docker Service Adapter (DSA) [1126] may be a microservicesbased component that may be designed to deploy and manage Container Network
25 Functions (CNFs) and their components (CNFCs) across Docker nodes. The DSA
[1126] may offer REST endpoints for key operations, such as uploading container
images to a Docker registry, terminating CNFC instances, and creating Docker
volumes and networks. The CNFs, that may be network functions packaged as
containers, may consist of multiple CNFCs. The DSA [1126] facilitates the
30 deployment, configuration, and management of these components by interacting
with Docker's API, ensuring proper setup and scalability within a containerized
18
environment. The DSA provides a modular and flexible framework for handling
network functions in a virtualized network setup.
[0057] FIG. 2 illustrates an exemplary block diagram of a computing device
5 [200] (hereinafter also referred to as a computing system [200]) upon which the
features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure. In an implementation, the
computing device [200] may also implement a method for managing dynamic
resource management and orchestration in a network utilising the system [400]. In
10 another implementation, the computing device [200] itself implements the method
for managing dynamic resource management and orchestration in the network using
one or more units configured within the computing device [200], wherein said one
or more units are capable of implementing the features as disclosed in the present
disclosure.
15
[0058] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
20 computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
25 processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a specialpurpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
30 information and instructions for the processor [204].
19
[0059] A storage device [210], such as a magnetic disk, optical disk, or solidstate drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
5 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a
10 mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
15
[0060] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
20 According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
25 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.
30 [0061] The computing device [200] also may include a communication
interface [218] coupled to the bus [202]. The communication interface [218]
20
provides a two-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
5 corresponding type of telephone line. As another example, the communication
interface [218] may be a local area network (LAN) card to provide a data
communication connection to a compatible LAN. Wireless links may also be
implemented. In any such implementation, the communication interface [218]
sends and receives electrical, electromagnetic or optical signals that carry digital
10 data streams representing various types of information.
[0062] 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
15 transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], a host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
20
[0063] Referring to FIG. 3, an exemplary block diagram of an environment
[300] used for managing dynamic resource management and orchestration in the
network, in accordance with exemplary implementations of the present disclosure,
is shown.
25
[0064] As shown in the FIG. 3, the environment [300] may comprise at least
one user interface [302], at least one policy execution engine (PEEGN) unit [304],
and one or more databases [306]. The at least one PEEGN unit [304] may be
connected with the user interface [302] via an interface referred to as the PE_CL
30 interface [308] in the figure. The user interface [302] may refer to an interface used
21
for communication with the user and the PEEGN unit [304]. The PE_CL interface
[308] may in different examples use either HTTP based connection or web-socket
based connection for communication. In another example, PE_CL interface [308]
may use a REST Application Programming Interface (API) over the HTTP based
5 connection acting as a medium of communication. In another example, the PE_CL
interface may utilise a JavaScript Object Notation (JSON) format for
communication between the PEEGN unit [304] and the user interface [302]. The
PEEGN unit [304] may be construed to be similar to the policy execution engine
[1088] as provided in the FIG. 1. As would be understood, the one or more databases
10 [306] may refer to one or more repositories which comprises a structured/organized
collection of data. In an example, the one or more databases [306] may also be
connected to the one or more databases [306] via another interface which may also
utilise the web-socket connection or the HTTP based connections for
communication between the components. It may be noted that the environment
15 [300] may also include additional components, which have not been depicted in
FIG. 3, and would be understood to a person skilled in the art.
[0065] Referring to FIG. 4, an exemplary block diagram of a system [400] for
managing dynamic resource management and orchestration in the network, is
20 shown, in accordance with the exemplary implementations of the present
disclosure. In an implementation, the network may be, such as but not limited to,
4G, 5G or 6G network.
[0066] In an exemplary implementation of the present disclosure, the system
25 [400] may be in communication with the PEEGN unit [304] for implementation of
the solutions provided by the present disclosure. In another exemplary
implementation of the present disclosure, the system [400] may be implemented as
or within the PEEGN unit [304] for implementation of the present disclosure. Also,
in another implementation of the present disclosure, the system [400] may comprise
30 the PEEGN unit [304] for implementing the solutions of the present disclosure.
22
[0067] The system [400] may comprise at least one transceiver unit [402], at
least one loading unit [404], and at least one display unit. As would be understood,
the system [400] when implemented as the PEEGN unit [304], then in such case,
the above-mentioned units may reside within the PEEGN unit [304]. In another
5 example, when the system [400] comprises the PEEGN unit [304], then in such
cases, the above-mentioned units may reside within the PEEGN unit [304].
[0068] Also, all of the components/ units of the system [400] are assumed to
be connected to each other unless otherwise indicated below. As shown in the
10 figures all units shown within the system [400] 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. Further, in an implementation, the system [400] may be present in a user
15 device/ user equipment to implement the features of the present disclosure. The
system [400] may be a part of the user device/ or may be independent of but in
communication with the user device (may also referred herein as a UE). In another
implementation, the system [400] may reside in a server or a network entity. In yet
another implementation, the system [400] may reside partly in the server/ network
20 entity and partly in the user device.
[0069] The figures namely FIG. 3 and FIG. 4 may be referred to in conjunction
with each other in the foregoing description for explanation of the solutions
provided by the present disclosure.
25
[0070] In an example, the system [400] may be configured for managing
dynamic resource management and orchestration in the network, with the help of
the interconnection between the components/units of the system [400]. In another
example, the system [400] may be configured for managing dynamic resource
23
management and orchestration in the network, with the help of the interconnection
between the components/units of the environment [300].
[0071] As would be understood, resource management and orchestration in the
5 network may refer to coordination and management of multiple resources in the
network for example, by stringing together multiple tasks in order to execute a
larger workflow or process. Also, as would be understood, the network may refer
to a set of devices or components such as network nodes which are linked for
sharing resources, exchange information, and/or allow electronic communications
10 between each other. In an implementation of the present disclosure, the network
may comprise one or more Virtual Network Functions (VNFs) and one or more
Containerized Network Functions (CNFs). As used herein, the VNF may refer to
software applications that deliver network functions such as directory services,
routers, firewalls, load balancers, etc. The CNF may be a component or a software
15 service that fulfils certain network functionalities while adhering to cloud-native
design principles without requiring any hardware or appliance to house it.
[0072] Now, for managing dynamic resource management and orchestration in
the network, the transceiver unit [402] may be configured to receive via the user
20 interface (UI) [302], an access request from one or more user devices to access the
PEEGN unit [304]. The access request may refer to a request, which may be in the
form of a message or a command, for accessing the PEEGN unit [304]. The one or
more user devices may refer to the devices or components which are used as the
user interface [302] for providing interaction with the user interface [302]. The
25 access request may be received by the UI [302] when the user interacts with the UI
[302] and enters certain commands and requests, the same may be transmitted to
the transceiver unit [302] in the form of access request. In another example, the
access request after receiving at the user interface [302] may be transmitted to the
PEEGN unit [304] such as for loading one or more commands.
30
24
[0073] In an exemplary aspect of the present disclosure, the UI [302] may work
in a high availability mode. In the high availability mode, if an instance of the policy
execution engine (PEEGN) unit [304] went down during processing of a request,
then a next available instance of the PEEGN unit [304] processes the request. The
5 high availability mode may refer to a mode in which the PEEGN unit [304] may be
available at most times, ensuring high reliability of the communication between the
UI [302] and the PEEGN [304]. For implementation of the high availability mode,
the PEEGN unit [304] may be implemented in a cluster configuration in which there
may be various instances of the PEEGN unit [304]. In the cluster configuration, in
10 case of failure/error of one instance of the PEEGN unit [304], another instance of
the PEEGN unit [304] may be utilized from the cluster of PEEGN units [304], in
order to process the received request. As would be understood, in case of multiple
components acting as the PEEGN unit [304] in the cluster configuration, a
component used as the PEEGN unit [304] may be referred to as an instance of the
15 PEEGN unit [304]. Similarly, the next available instance may be referred to another
component used as the PEEGN unit [304], in case of any error/failure of the former
instances of the PEEGN unit [304]. In an example, the request may be similar to
the access request received by the transceiver unit [402].
20 [0074] In another exemplary implementation of the present disclosure, the user
interface [302] may be a command line interface (CLI) [602] (referred to in FIG.
6). As would be understood, the CLI [602] may refer to a text-based user interface
(UI) that may be utilised for running programs, managing files and interacting with
other components in the network. In such exemplary implementations of the present
25 disclosure, the CLI [602] may utilise the PE_CL interface for executing any
operation on the PEEGN unit [304]. In such examples, the permitted operations for
the user may be predefined at the PEEGN unit [304].
[0075] In a further exemplary implementation of the present disclosure, the
30 command line interface (CLI) [602] may be used to prompt the user to provide login
credentials. In an example, the login credentials may refer to a set of credentials
25
involving a username and a password which may be used for verification of an
identity of the user. For example, the prompt may be to enter the credentials into
the CLI [602]. Further, it may be noted that the above-mentioned example is not
limiting in nature, and may utilize different types of authentication methods which
5 may be considered to be obvious to a person skilled in the art.
[0076] After receiving the access request, the loading unit [404] may be
configured to load one or more commands associated with the policy execution
engine (PEEGN) unit [304]. The commands may refer to a set of instructions which
10 may be processed by a device associated with one or more objects and one or more
attributes of a program/file/data, etc. The one or more commands may be pre-stored
in a storage unit which may be loaded and may also be further presented. The
loading of the one or more commands may, in an example, be fetching the prestored one or more commands. In an example, the one or more commands after
15 being loaded may be sent to the user interface [302] in response to the forwarded
access request.
[0077] After loading the one or more commands, the transceiver unit [402]
may be configured to receive via the UI [302], a selection of the command from the
20 one or more user devices, wherein the selection further comprises a user input for
the command. The selection of the command may refer to a command selected from
the one or more commands. The user input for the command may refer to the input
received from the user interface [302] regarding the selection of the command from
the one or more user devices. In an example, the one or more commands may be
25 presented on the user interface [302] using the display unit [306]. The user interface
[302] may be then used for selecting a particular command from the one or more
commands that are displayed over the interface and may be selected by the user.
This selection of the particular command through the user interface [302] may be
then received by the transceiver unit [302] of the system [400].
30
26
[0078] In another exemplary implementation of the present disclosure, the
command line interface (CLI) [602] may enable the user to select a command from
a list of commands associated with the policy execution engine (PEEGN) unit
[304]. Further, the list of commands may refer to a list specifying recommended
5 instructions associated with the received request.
[0079] In exemplary implementations of the present disclosure, the one or
more commands may comprise a command for change in configuration parameter,
a command for monitoring one or more performance counter, a command for
10 monitoring severity alarm, and a command for one of a registration and
deregistration of one or more instances of the policy execution engine (PEEGN)
unit [304] associated with an orchestration manager unit.
[0080] In another example, the list of commands and/or the one or more
15 commands may comprise a get parameter command, a get parameters command, a
set parameters command, a get alarms command, a clear alarm command, a get
counters command, a get PEEGN information command a reregister to OAM
command, a deregister to OAM command, a do forceful reregistration command, a
get OAM information command, a get ELB information command, a get ERM
20 information command, a send event to fetch flavor details command, etc.
[0081] In an example, the get parameter command may be a “getParam”
command that may result in getting a specific configuration parameter of the
PEEGN unit [304]. In another example, the get parameters command may be a
25 “getParams” command that may result in getting all configuration parameters of the
PEEGN unit [304]. In another example, the set parameters command or the
command for change in configuration parameter may be a “setParam” command
that may result in changing the value of a specific configuration parameter. In
another example, the get alarms command or the command for monitoring severity
30 alarm may be a “getAlarms” command that may result in getting all the alarms. In
27
another example, the clear alarm command may be a “clearAlarm” command that
may result in clearing the alarm. In another example, the get counters command or
the command for monitoring one or more performance counters may be a
“getCounters” command that may result in getting performance counters. In another
5 example, the get PEEGN information command may be a “getPeegnInfo”
command that may result in getting PEEGN information. In another example, the
reregister to OAM command may be a “reregisterToOam” command that may result
in re-registration to OAM. In another example, the deregister to OAM command
may be a “deregisterToOam” command that may result in de-registration from
10 OAM. In another example, the do forceful reregistration command may be a
“doForcefulReregistration” command that may result in forceful registration to
OAM. In another example, the get OAM information command may be a
“getOamInfo” command that may result in getting OAM information. In another
example, the get ELB information command may be a “getElbInfo” command that
15 may result in getting ELB information. In another example, the get ERM
information command may be a “getErmInfo” command that may result in getting
ERM information. In another example, the send event to fetch flavor details
command may be a “sendEventTofetchFlavorDetails” command that may result in
fetching all the Compute size from the PVIM during run time.
20
[0082] As would be understood, the ERM may be considered to be similar to
the event routing manager (ERM) [1070] as may be understood in conjunction with
FIG. 1. Similarly, the PVIM may be considered to be similar to the physical &
virtual resource manager [1050] as may be understood in conjunction with FIG. 1.
25 Also, the ELB may refer to elastic load balancers which may be used for balancing
load/traffic between the components. Further, the OAM and the orchestration
manager unit may be considered to be similar to the platform operations,
administration, and maintenance manager [1106] as may be understood in
conjunction with FIG. 1.
30
28
[0083] Continuing further after the selection of the command, the transceiver
unit [402] may be configured to transmit a service request to the policy execution
engine (PEEGN) unit [304] based on the received selection. The service request
may refer to a request for execution of the command selected by the user interface
5 [302]. In an example, for transmitting the service request to the PEEGN unit [304],
the service request comprising the selected command may be forwarded to the
PEEGN unit [304]. In the implementations where the system [400] may function as
or within the PEEGN unit [304], the service request may be exchanged internally
between the certain units or modules and then may be used for processing the
10 request.
[0084] Then, in an example, in response to the service request, the policy
execution engine (PEEGN) unit [304] may be further configured to extract a
compute size information from a physical - virtual inventory management unit. The
15 PVIM unit may be similar to the physical and virtual resource manager as may be
understood in conjunction with FIG. 1. The compute size information may refer to
an information associated with compute capabilities of the network nodes within
the network. As would be understood, the compute capabilities may be associated
with processing capabilities of the network nodes. As provided above, the PVIM
20 unit may store information associated with network resources allocated to a
particular network node. For extracting the compute size information, such
information may be fetched by the system [400] and an information associated with
the compute resources associated with a particular network node in the network
may be parsed. Thereafter, the PEEGN unit [304] may manage an instantiation and
25 a scaling functionality for one or more virtual network functions (VNFs) based on
the compute size. The management of the instantiation and scaling functionality for
the one or more VNF may refer to performing actions such as scaling in/out or
performing no changes for a particular instance of the VNF within the network in
order to manage the functionalities of the VNF and/or other network nodes.
30
29
[0085] Continuing further, the transceiver unit [402] may be configured to
receive a service response from the policy execution engine (PEEGN) unit [304].
After, the management of the instantiation and the scaling functionality for the one
or more virtual network functions (VNFs) based on the compute size has been
5 performed by the PEEGN unit [304], the PEEGN unit [304] may generate the
service response and then transmit the same to the transceiver unit [402] of the
system [400]. The service response may refer to the response generated by the
PEEGN unit [304] and may, in an example, comprise certain policies required to be
executed for managing the instantiation and the scaling functionality for the one or
10 more virtual network functions (VNFs) based on the compute size. In an example,
the service response may comprise the requirements of performing scaling
operations, information associated with the scaling operations, suggestive actions
etc.
15 [0086] After the service response has been received, the display unit [406] may
be configured to display the service response received from the policy execution
engine (PEEGN) unit [304]. As would be understood, for displaying the service
response, the display unit [406] may present the information in the service response
over the user interface [302] which may be then provided to the user interface by a
20 visual representation of the information in the service response.
[0087] In an exemplary aspect of the present disclosure, the transceiver unit
[402] may receive, via the UI [302], the selection of commands to retrieve
information of one or more connected components from the policy execution engine
25 (PEEGN) unit [304]. The command for retrieving information as provided above
may be a get information command. In exemplary cases, the one or more connected
components may be the OAM, the ELB, the ERM, the PVIM, etc. Then, the
transceiver unit [402] may transmit the service request to the policy execution
engine (PEEGN) unit [304] based on the received selection. The service request, in
30 such an exemplary aspect, may be related to the request for performing the selected
30
operations associated with getting information of the one or more connected
components.
[0088] Continuing further to the exemplary aspect of the present disclosure,
5 the transceiver unit [302] may further receive, via the UI [302], a service response
from the policy execution engine (PEEGN) unit [304]. The service response may
comprise information regarding one or more connected components. In an example,
the service response may comprise a success indication or a failure indication in
response to the service request. The information regarding the one or more
10 connected components may be generated based on the performance of the service
request. Then, the display unit [406] may further display the service response
received from the policy execution engine (PEEGN) unit [304]. For example, the
display unit [406] may present the information regarding the one or more connected
components over the user interface [302].
15
[0089] Referring to FIG. 5, an exemplary method flow diagram [500] for
managing dynamic resource management and orchestration in the network, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [500] is performed by the system [400]. In another
20 implementation, the method [500] may be performed utilizing the environment
[300]. Further, in 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].
25 [0090] Referring to FIG. 6, an exemplary call flow diagram [600] for
managing dynamic resource management and orchestration in the network, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [600] is performed by the system [400]. In another
implementation, the method [600] may be performed utilizing the environment
31
[300]. Further, in an implementation, the system [400] may be present in a server
device to implement the features of the present disclosure.
[0091] The figures namely FIG. 5 and FIG. 6 may be referred to in conjunction
5 with each other in the foregoing description for explanation of the solutions
provided by the present disclosure.
[0092] For managing dynamic resource management and orchestration in a
network, at step [504], the method [500] involves receiving, at a transceiver unit
10 [402] by a user interface (UI) [302], an access request from one or more user devices
to access a policy execution engine (PEEGN) unit [304]. In an example, the access
request after receiving at the command line interface [602] may be transmitted to
the PEEGN unit [304] such as for loading one or more commands. This
transmission of the access request to the PEEGN unit [304] has been depicted by
15 Step 1 in the FIG. 6.
[0093] In an implementation of the present disclosure, the network may
comprise one or more Virtual Network Functions (VNFs) and one or more
Containerized Network Functions (CNFs).
20
[0094] In an exemplary aspect of the present disclosure, the UI [302] may work
in a high availability mode. In the high availability mode, if an instance of the policy
execution engine (PEEGN) unit [304] went down during processing of a request,
then a next available instance of the policy execution engine (PEEGN) unit [304]
25 processes the request.
[0095] In another exemplary implementation of the present disclosure, the user
interface [302] may be a command line interface (CLI) [602].
32
[0096] In a further exemplary implementation of the present disclosure, the
command line interface (CLI) [602] may be used to prompt the user to provide login
credentials.
5 [0097] Continuing further, after receiving the access request, at step [506], the
method [500] involves loading, by a loading unit [404], one or more commands
associated with the policy execution engine (PEEGN) unit [304]. The one or more
commands after being loaded may be sent to the command line interface [602] in
response to the access request. The step of sending by the PEEGN unit [304] and
10 receiving at the command line interface [602], the one or more commands have
been depicted by Step 2 in the FIG. 6.
[0098] After loading the one or more commands, then at step [508], the method
[500] involves receiving, by the transceiver unit [402] via the UI [302], a selection
15 of a command from the one or more user devices. The selection further comprises
a user input for the command.
[0099] In another exemplary implementation of the present disclosure, the
command line interface (CLI) [602] may enable the user to select a command from
20 a list of commands associated with the policy execution engine (PEEGN) unit
[304].
[0100] In an exemplary implementation of the present disclosure, the one or
more commands associated with the policy execution engine (PEEGN) unit [304]
25 comprises of a command for change in configuration parameter, a command for
monitoring one or more performance counter, a command for monitoring severity
alarm, and a command for one of a registration and a deregistration of one or more
instances of the policy execution engine (PEEGN) unit [304] associated with an
orchestration manager unit.
30
33
[0101] Continuing further after the selection of the command, then at step
[510], the method [500] involves transmitting by the transceiver unit [402], a
service request to the policy execution engine (PEEGN) unit [304] based on the
received selection. This step of transmitting the service request has also been
5 depicted by Step 3 in the FIG. 6.
[0102] Then, in an example, in response to the service request, the method
[500] may also involve extracting, by the policy execution engine (PEEGN) unit
[304], a compute size information from a physical - virtual inventory management
10 unit. Then the method [500] may lead to managing, by the policy execution engine
(PEEGN) unit [304], an instantiation and a scaling functionality for one or more
virtual network functions based on the compute size information.
[0103] Continuing further, then at step [512], the method [500] involves
15 receiving, by the transceiver unit [402], a service response from the policy
execution engine (PEEGN) unit [304]. This step of receiving the service response
has also been depicted by Step 4 in the FIG. 6.
[0104] Then after the service response has been received, at step [514], the
20 method [500] involves displaying, by a display unit [406], the service response
received from the policy execution engine (PEEGN) unit [304].
[0105] In an exemplary aspect of the present disclosure, the method [500]
involves receiving, by the transceiver unit [402] via the UI [302], the selection of
25 commands to retrieve information of one or more connected components from the
policy execution engine (PEEGN) unit [304]. Then the method [500] may lead to
transmitting, by the transceiver unit [402], a service request to the policy execution
engine (PEEGN) unit [304] based on the received selection.
34
[0106] Continuing further to the exemplary aspect of the present disclosure,
the method [500] involves receiving, by the transceiver unit [402] via the UI [302],
a service response from the policy execution engine (PEEGN) unit [304]. In such
an exemplary aspect of the present disclosure, the service response comprises
5 information regarding one or more connected components. Thereafter, the method
[500] leads to displaying, by the display unit [406], the service response received
from the policy execution engine (PEEGN) unit [304].
[0107] Thereafter, at step [516], the method [500] may be terminated.
10
[0108] In another aspect of the present disclosure, a User Equipment (UE)
comprising a memory, and a processor connected to the memory is disclosed. The
processor is configured to receive via a user interface (UI) [302], an access request
from one or more user devices to access a policy execution engine (PEEGN) unit
15 [304]. Then the processor is configured to load one or more commands associated
with the policy execution engine (PEEGN) unit [304]. The processor is also
configured to receive via the UI [302], a selection of a command from the one or
more user devices, wherein the selection further comprises a user input for the
command. Then the processor transmits a service request to the policy execution
20 engine (PEEGN) unit [304] based on the received selection. Further, the processor
receives a service response from the policy execution engine (PEEGN) unit [304].
Also, the processor enables a display of the service response received from the
policy execution engine (PEEGN) unit [304].
25 [0109] The present disclosure further discloses a non-transitory computer
readable storage medium storing one or more instructions for managing dynamic
resource management and orchestration in the network, the one or more instructions
include executable code which, when executed by one or more units of a system,
causes the one or more units to perform certain functions. The one or more
30 instructions when executed causes a transceiver unit [402] to receive via a user
35
interface (UI) [302], an access request from one or more user devices to access a
policy execution engine (PEEGN) unit [304]. The one or more instructions when
executed further causes a loading unit [404] to load one or more commands
associated with the policy execution engine (PEEGN) unit [304]. The one or more
5 instructions when executed further causes the transceiver unit [402] to receive via
the UI [302], a selection of a command from the one or more user devices. The
selection further comprises a user input for the command. The one or more
instructions when executed further causes the transceiver unit [402] to transmit a
service request to the policy execution engine (PEEGN) unit [304] based on the
10 received selection. The one or more instructions when executed further causes the
transceiver unit [402] to receive a service response from the policy execution engine
(PEEGN) unit [304]. The one or more instructions when executed further causes a
display unit [406] to display the service response received from the policy execution
engine (PEEGN) unit [304].
15
[0110] As is evident from the above, the present disclosure provides a
technically advanced solution for managing dynamic resource management and
orchestration in a network. The present solution provides an async event-based
implementation to utilize the interface efficiently. In addition, the present invention
20 provides fault tolerance for any event failure. The interface provided by the present
disclosure works in a high availability mode and if one inventory instance goes
down during request processing, then the next available instance takes care of the
request. The present solution provides a high-availability mode that provides a nonservice impacting solution. Further, the present solution provides less-time
25 consuming process for monitoring the instance of the policy execution engine
(PEEGN) and other instances. The present solution also provides updating of
restricted information at the PEEGN itself by authenticating at the user interface.
Also, the present solution provides on-demand registration and deregistration with
the Orchestration and Management components within the network.
30
36
[0111] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
5 of the present disclosure will be apparent to those skilled in the art, whereby it is to
be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0112] Further, in accordance with the present disclosure, it is to be
10 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
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
15 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
37
We Claim:
1. A method [500] for managing dynamic resource management and
orchestration in a network, the [500] method comprising:
5 - receiving, at a transceiver unit [402] by a user interface (UI) [302], an
access request from one or more user devices to access a policy
execution engine (PEEGN) unit [304];
- loading, by a loading unit [404], one or more commands associated
with the policy execution engine (PEEGN) unit [304];
10 - receiving, by the transceiver unit [402] via the UI [302], a selection of
a command from the one or more user devices, wherein the selection
further comprises of a user input for the command;
- transmitting by the transceiver unit [402], a service request to the
policy execution engine (PEEGN) unit [304] based on the received
15 selection;
- receiving, by the transceiver unit [402], a service response from the
policy execution engine (PEEGN) unit [304]; and
- displaying, by a display unit [406], the service response received from
the policy execution engine (PEEGN) unit [304].
20
2. The method [500] as claimed in claim 1, wherein the network comprises
one or more Virtual Network Functions (VNFs) and one or more
Containerized Network Functions (CNFs).
25 3. The method [500] as claimed in claim 1, wherein the one or more commands
associated with the policy execution engine (PEEGN) unit [304] comprises
of a command for change in configuration parameter, a command for
monitoring one or more performance counter, a command for monitoring
severity alarm, and a command for one of a registration and a deregistration
38
of one or more instances of the policy execution engine (PEEGN) unit [304]
associated with an orchestration manager unit.
4. The method [500] as claimed in claim 1, wherein the method [500] further
5 comprises:
- extracting, by the policy execution engine (PEEGN) unit [304], a
compute size information from a physical - virtual inventory
management unit; and
- managing, by the policy execution engine (PEEGN) unit [304], an
10 instantiation and a scaling functionality for one or more virtual
network functions based on the compute size information.
5. The method [500] as claimed in claim 1, wherein the user interface [302] is
a command line interface [602].
15
6. The method [500] as claimed in claim 5, wherein the command line
interface [602] prompts the user to provide login credentials.
7. The method [500] as claimed in claim 5, wherein the command line
20 interface [602] enables the user to select a command from a list of
commands associated with the policy execution engine (PEEGN) unit [304].
8. The method [400] as claimed in claim 1, wherein the method [500] further
comprises:
25 - receiving, by the transceiver unit [402] via the UI [302], the selection
of commands to retrieve information of one or more connected
components from the policy execution engine (PEEGN) unit [304],
- transmitting, by the transceiver unit [402], a service request to the
policy execution engine (PEEGN) unit [304] based on the received
30 selection,
39
- receiving, by the transceiver unit [402] via the UI [302], a service
response from the policy execution engine (PEEGN) unit [304], where
the service response comprises information regarding one or more
connected components, and
5 - displaying, by the display unit [406], the service response received
from the policy execution engine (PEEGN) unit [304].
9. The method [500] as claimed in claim 1, wherein the UI [302] works in a
high availability mode, and wherein in the high availability mode if an
10 instance of the policy execution engine (PEEGN) unit [304] went down
during processing of a request, then a next available instance of the policy
execution engine (PEEGN) unit [304] processes the request.
10. A system [400] for managing dynamic resource management and
15 orchestration in a network, the system [400] comprising:
- a transceiver unit [402] configured to receive via a user interface (UI)
[302], an access request from one or more user devices to access a
policy execution engine (PEEGN) unit [304];
- a loading unit [404] configured to load one or more commands
20 associated with the policy execution engine (PEEGN) unit [304];
- the transceiver unit [402] configured to:
- receive via the UI [302], a selection of a command from the one
or more user devices, wherein the selection further comprises of
a user input for the command;
25 - transmit a service request to the policy execution engine
(PEEGN) unit [304] based on the received selection; and
- receive a service response from the policy execution engine
(PEEGN) unit [304]; and
- a display unit [406] configured to display the service response
30 received from the policy execution engine (PEEGN) unit [304].
40
11. The system [400] as claimed in claim 10, wherein the network comprises
one or more Virtual Network Functions (VNFs) and one or more
Containerized Network Functions (CNFs).
5
12. The system [400] as claimed in claim 10, wherein the one or more
commands associated with the policy execution engine (PEEGN) unit [304]
comprises of a command for change in configuration parameter, a command
for monitoring one or more performance counter, a command for
10 monitoring severity alarm, and a command for one of a registration and
deregistration of one or more instances of the policy execution engine
(PEEGN) unit [304] associated with an orchestration manager unit.
13. The system [400] as claimed in claim 10, wherein the policy execution
15 engine (PEEGN) unit [304] is further configured to:
- extract a compute size information from a physical - virtual inventory
management unit; and
- manage an instantiation and a scaling functionality for one or more
virtual network functions based on the compute size.
20
14. The system [400] as claimed in claim 10, wherein the user interface [302]
is a command line interface [602].
15. The system [400] as claimed in claim 14, wherein the command line
25 interface [602] prompts the user to provide login credentials.
16. The system [400] as claimed in claim 14, wherein the command line
interface [602] enables the user to select a command from a list of
commands associated with the policy execution engine (PEEGN) unit [304].
30
41
17. The system [400] as claimed in claim 10, wherein:
- the transceiver unit [402] is configured to:
- receive via the UI [302], the selection of commands to retrieve
information of one or more connected components from the
5 policy execution engine (PEEGN) unit [304];
- transmit a service request to the policy execution engine
(PEEGN) unit [304] based on the received selection;
- receive via the UI [302], a service response from the policy
execution engine (PEEGN) unit [304], where the service response
10 comprises information regarding one or more connected
components; and
- the display unit [406] is further configured to display the service
response received from the policy execution engine (PEEGN) unit
[304].
15
18. The system [400] as claimed in claim 10, wherein the UI [302] works in a
high availability mode, and wherein in the high availability mode if an
instance of the policy execution engine (PEEGN) unit [304] went down
during processing of a request, then a next available instance of the policy
20 execution engine (PEEGN) unit [304] processes the request.
19. A User Equipment (UE) comprising:
- a memory; and
- a processor connected to the memory, wherein the processor is
25 configured to:
- receive via a user interface (UI) [302], an access request from one
or more user devices to access a policy execution engine
(PEEGN) unit [304];
- load one or more commands associated with the policy execution
30 engine (PEEGN) unit [304];
42
- receive via the UI [302], a selection of a command from the one
or more user devices, wherein the selection further comprises of
a user input for the command;
- transmit a service request to the policy execution engine
5 (PEEGN) unit [304] based on the received selection;
- receive a service response from the policy execution engine
(PEEGN) unit [304]; and
- enable a display of the service response received from the policy
execution engine (PEEGN) unit [304].