1
FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
5 THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
10 “METHOD AND SYSTEM FOR MONITORING OPERATIONS
RELATED TO NETWORK FUNCTIONS IN A NETWORK
ENVIRONMENT”
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
METHOD AND SYSTEM FOR MONITORING OPERATIONS RELATED
TO NETWORK FUNCTIONS IN A NETWORK ENVIRONMENT
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure relate generally to the field of
wireless communication systems. More particularly, embodiment of the present
disclosure relates to a method and system for monitoring operations related to
network functions in a network environment.
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. 3G technology
marked the introduction of high-speed internet access, mobile video calling, and
location-based services. The fourth-generation (4G) technology revolutionized
wireless communication with faster data speeds, better network coverage, and
improved security. Currently, the fifth-generation (5G) technology is being
30 deployed, promising even faster data speeds, low latency, and the ability to connect
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] With the development and evolution of wireless communication systems,
the number of 5 network functions implemented in a wireless communication
systems has also increased. Thus, with this increased number of the network
functions implemented in place, management of these network functions has also
become complex. In the existing solutions, the management of these network
functions, such as the container network functions (CNFs) and the virtual network
10 functions (VNFs), is performed manually. However, the manual management of the
network functions has several shortcomings such as the manual management is time
consuming, requires a lot of efforts, is prone to human errors, etc.
[0005] Thus, there exists an imperative need in the art to provide a method and a
15 system for managing network functions using a single platform, which the present
disclosure aims to address.
SUMMARY
20 [0006] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.
This summary is not intended to identify the key features or the scope of the claimed
subject matter.
25 [0007] An aspect of the present disclosure may relate to a method for monitoring
operations related to network functions in a network environment. The method
comprising receiving, by a transceiver unit via a user interface (UI), a request to
perform an operation on at least a network function (NF), wherein the request
comprises a set of details relating to the operation. The method further comprises
30 transmitting, by the transceiver unit, to the UI, a first acknowledgement indicative
of receipt of the request. The method further comprises storing, by a storage unit, a
4
record of the received request and the first acknowledgement in a database. The
method further comprises receiving, by the transceiver unit, from the database, a
second acknowledgement indicative of storing of the record in the database.
[0008] In an exemplary 5 aspect of the present disclosure, the request is in a hypertext
transfer protocol (HTTP) format.
[0009] In an exemplary aspect of the present disclosure, the first acknowledgement,
and the second acknowledgement are in one of a JavaScript Object Notation
10 (JSON) format and Extensible Markup Language (XML) format.
[0010] In an exemplary aspect of the present disclosure, the request corresponds to
at least one of instantiation of network functions, migration of network functions to
new hosts, and termination of the network functions.
15
[0011] In an exemplary aspect of the present disclosure, the set of details comprises
information related to at least one of instantiation of the network functions,
termination of the network functions, intermediate level termination of the network
functions, backup operations related to the network functions, restore operations
20 related to the network functions, and update operations related to the network
functions.
[0012] In an exemplary aspect of the present disclosure, the network functions
comprise at least one of cloud-native network functions (CNFs), and virtualised
25 network functions (VNFs).
[0013] In an exemplary aspect of the present disclosure, the UI and the transceiver
unit [304] are in communication over a SA_UI interface.
30 [0014] Another aspect of the present disclosure may relate to a system for
monitoring operations related to network functions in a network environment. The
5
system comprises a processing unit and a transceiver unit connected at least to the
processing unit. The transceiver unit is configured to receive, via a user interface
(UI), a request to perform an operation on at least a network function (NF), wherein
the request comprises a set of details relating to the operation. The transceiver unit
is further configured to 5 transmit, to the UI, a first acknowledgement indicative of
receipt of the request. The system further comprises a storage unit connected at least
to the transceiver unit. The storage unit is configured to store a record of the
received request and the first acknowledgement in a database. The transceiver unit
is further configured to receive, from the database, a second acknowledgement
10 indicative of storing of the record in the database.
[0015] Yet another aspect of the present disclosure may relate to a User Equipment
(UE). The UE comprises a memory and a processor connected to the memory. The
processor is configured to transmit, via a User Interface (UI), a request to a system.
15 The request is to perform an operation on at least a Network Function (NF). Further,
the request includes a set of details relating to the operation. The processor is further
configured to receive, at the UI, a first acknowledgement from the system. The first
acknowledgement is indicative of receipt of the request.
20 [0016] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for monitoring operations
related to network functions in a network environment. The instructions include
executable code which, when executed by one or more units of a system, causes a
transceiver unit of the system to receive, via a user interface (UI), a request to
25 perform an operation on at least a network function (NF), wherein the request
comprises a set of details relating to the operation. Further, the instructions include
executable code which, when executed, causes the transceiver unit to transmit, to
the UI, a first acknowledgement indicative of receipt of the request. Further, the
instructions include executable code which, when executed, causes a storage unit
30 to store a record of the received request and the first acknowledgement in a
database. Further, the instructions include executable code which, when executed,
6
causes the transceiver unit to receive, from the database, a second
acknowledgement indicative of storing of the record in the database.
OBJECTS OF THE DISCLOSURE
5
[0017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for
10 monitoring operations related to network functions in a network environment.
[0019] It is another object of the present disclosure to provide a separate interface
on an automation platform for instantiation, termination and other operations
related to the management of network functions.
15
[0020] It is yet another object of the present disclosure to provide a solution in
which all information related to the network functions is visible on the user interface
of the automation platform.
20 [0021] It is yet another object of the present disclosure to provide a solution that is
less prone to errors.
DESCRIPTION OF THE DRAWINGS
25 [0022] 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
different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
30 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
7
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.
5
[0023] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture.
[0024] FIG. 2 illustrates an exemplary block diagram of a computing device upon
10 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0025] FIG. 3 illustrates an exemplary block diagram of a system for monitoring
operations related to network functions in a network environment, in accordance
15 with exemplary implementations of the present disclosure.
[0026] FIG. 4 illustrates an exemplary flow diagram for monitoring operations
related to network functions in a network environment, in accordance with
exemplary implementations of the present disclosure.
20
[0027] FIG. 5 illustrates a method flow diagram for monitoring operations related
to network functions in a network environment, in accordance with exemplary
implementations of the present disclosure.
25 [0028] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
30 [0029] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
8
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
address any of the problems discussed 5 above or might address only some of the
problems discussed above.
[0030] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
10 the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
15
[0031] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
20 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0032] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
25 diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
included in a figure.
30
9
[0033] 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
necessarily 5 to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
10 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0034] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
15 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a Digital
Signal Processing (DSP) core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
20 integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
25 [0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
30 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
10
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from unit(s) which
are required to implement the features of the present disclosure.
5
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
10 magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
that may be required by one or more units of the system to perform their respective
functions.
15 [0037] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be
20 called.
[0038] 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
25 digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
30 [0039] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
11
information or a combination thereof between units/components within the system
and/or connected with the system.
[0040] As discussed in the background section, the current known solutions for
managing network 5 functions have several shortcomings such as those related to
time consumption, requirement of human efforts, being prone to errors. The present
disclosure aims to overcome the above-mentioned and other existing problems in
this field of technology by providing a method and a system monitoring operations
related to network functions in a network environment.
10
[0041] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0042] FIG. 1 illustrates an exemplary block diagram representation of a
15 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)
20 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
25 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.
[0043] As shown in FIG. 1, the MANO architecture [100] comprises a user
30 interface layer [102], a network function virtualization (NFV) and software defined
network (SDN) design function module [104], a platform foundation services
12
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
implementing features of the present disclosure.
5
[0044] The NFV and SDN design function module [104] comprises a VNF
lifecycle manager [1042], a VNF catalog [1044], a network services catalog [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
10 manager [1042] may be responsible for deciding on which server of the
communication network the microservice may be instantiated. The VNF lifecycle
manager [1042] may manage the overall flow of incoming/ outgoing requests
during interaction with the user. The VNF lifecycle manager [1042] may be
responsible for determining which sequence to be followed for executing the
15 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 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
20 slicing (an ordered and connected sequence of network service/ network functions
(NFs)) that must be applied to a specific networked data packet. The physical and
virtual resource manager [1050] stores the logical and physical inventory of the
VNFs. Just like the VNF lifecycle manager [1042], the CNF lifecycle manager
[1052] may be similarly used for the CNFs lifecycle management.
25
[0045] The platforms foundation services module [106] comprises a microservices
elastic load balancer [1062], an identity & access manager [1064], a command line
interface (CLI) [1066], a central logging manager [1068], and an event routing
manager [1070]. The microservices elastic load balancer [1062] may be used for
30 maintaining the load balancing of the request for the services. The identity & access
manager [1064] may be used for logging purposes. The command line interface
13
(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 5 [1070] may be responsible for routing the events i.e., the
application programming interface (API) hits to the corresponding services.
[0046] The platforms core services module [108] comprises NFV infrastructure
monitoring manager [1082], an assure manager [1084], a performance manager
10 [1086], a policy execution engine [1088], a capacity monitoring manager [1090], a
release management (mgmt.) repository [1092], a configuration manager & golden
configuration template (GCT) [1094], an NFV platform decision analytics [1096],
a platform NoSQL DB [1098], a platform schedulers and cron jobs [1100], a VNF
backup & upgrade manager [1102], a micro service auditor [1104], and a platform
15 operations, administration and 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
20 performance counters. The policy execution engine (PEE) [1088] may be
responsible for managing all the policies. The capacity monitoring manager (CMM)
[1090] may be responsible for sending the request to the PEE [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
25 manager & GCT [1094] manages the configuration and GCT of all the vendors. The
NFV platform decision analytics (NPDA) [1096] helps in deciding the priority of
using the network resources. It is further noted that the policy execution engine
(PEE) [1088], the configuration manager & (GCT) [1094] and the (NPDA) [1096]
work together. The platform NoSQL DB [1098] may be a platform database for
30 storing all the inventory (both 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
14
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 limited to triggering of an event, traverse the
network graph 5 etc. The VNF backup & upgrade manager [1102] takes backup of
the images, binaries of the VNFs and the CNFs and produces those backups on
demand in case 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,
10 the microservice auditor [1104] audits and 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.
15
[0047] The platform resource adapters and utilities module [112] further comprises
a platform external API adaptor and gateway [1122], a generic decoder and indexer
(XML, CSV, JSON) [1124], a docker service adaptor [1126], an OpenStack API
adapter [1128], and a NFV gateway [1130]. The platform external API adaptor and
20 gateway [1122] may be responsible for handling the external services (to the
MANO platform [100]) that requires the network resources. The generic decoder
and indexer (XML, CSV, JSON) [1124] may get directly the data of the vendor
system in the XML, CSV, JSON format. The docker service adaptor [1126] may be
the interface provided between the telecom cloud and the MANO architecture [100]
25 for communication. The Docker Service Adapter (DSA) is a microservices-based
system designed to deploy and manage Container Network Functions (CNFs) and
their components (CNFCs) across Docker nodes. It offers REST endpoints for key
operations, including uploading container images to a Docker registry, terminating
CNFC instances, and creating Docker volumes and networks. CNFs, which are
30 network functions packaged as containers, may consist of multiple CNFCs. The
DSA facilitates the deployment, configuration, and management of these
15
components by interacting with Docker's API, ensuring proper setup and scalability
within a containerized environment. This approach provides a modular and flexible
framework for handling network functions in a virtualized network setup.
5 [0048] The OpenStack API adapter [1128] may be used to connect with the virtual
machines (VMs). The NFV gateway [1130] may be responsible for providing the
path to each services going to/incoming from the MANO architecture [100].
[0049] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
10 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
monitoring operations related to network functions in a network environment
utilising the system. In another implementation, the computing device [200] itself
15 implements the method for monitoring operations related to network functions in a
network environment 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.
20 [0050] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with the 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
25 random-access 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 processor [204]. Such instructions, when stored in non-transitory storage
30 media accessible to the processor [204], render the computing device [200] into a
special-purpose machine that is customized to perform the operations specified in
16
the instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0051] A storage device [210], such 5 as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
10 displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
15 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. This 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.
20 [0052] 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.
According to one implementation, the techniques herein are performed by the
25 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
contained in the main memory [206] causes the processor [204] to perform the
30 process steps described herein. In alternative implementations of the present
17
disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0053] The computing device [200] also may include a communication interface
[218] coupled to the 5 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
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
10 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 data streams representing
15 various types of information.
[0054] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
20 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,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
25
[0055] Referring to FIG. 3, an exemplary block diagram of a system [300] for
monitoring operations related to network functions in a network environment, is
shown, in accordance with the exemplary implementations of the present
disclosure. In one example, the system [300] may be implemented as or within a
30 Docker Service Adaptor (DSA). Such Docker Service Adaptor (DSA) may be
understood as DSA [1126], as explained in conjunction with FIG. 1.
18
[0056] FIG. 4 illustrates an exemplary flow diagram for monitoring operations
related to network functions in a network environment, in accordance with
exemplary implementations of the present disclosure.
5
[0057] It may be noted that FIG. 3 and FIG. 4 have been explained simultaneously
and may be read in conjunction with each other.
[0058] In one example, the system [300] may be in communication with other
10 network entities/components as depicted in FIG. 4. It may be further noted that any
other network entities/components known to a person skilled in the art and not
depicted in FIG. 4, may also be in communication with the system [300]. Such
network entities/components have not been explained here for the sake of brevity.
15 [0059] As depicted in FIG. 3, the system [300] may include at least one processing
unit [302], at least one transceiver unit [304] and at least one storage unit [306].
[0060] Also, all of the components/ units of the system [300] are assumed to be
connected to each other unless otherwise indicated below. As shown in FIG.3, all
20 units shown within the system [300] should also be assumed to be connected to
each other. Also, in FIG. 3, only a few units are shown, however, the system [300]
may comprise multiple such units or the system [300] may comprise any such
numbers of said units, as required to implement the features of the present
disclosure. Further, in an implementation, the system [300] may be present in a user
25 device/ user equipment [102] to implement the features of the present disclosure.
The system [300] may be a part of the user device [102]/ or may be independent of
but in communication with the user device [102] (may also referred herein as a UE).
In another implementation, the system [300] may reside in a server or a network
entity. In yet another implementation, the system [300] may reside partly in the
30 server/ network entity and partly in the user device.
19
[0061] The system [300] is configured for monitoring operations related to network
functions in a network environment, with the help of the interconnection between
the components/units of the system [300].
[0062] In one embodiment, 5 the system [300] may deploy an event-driven
architecture, known to a person skilled in the art, to handle operations related to
network functions. In such cases, the system [300] may use standard REST APIs
for communication between various components over HTTP, similar to the way
clients and servers exchange data.
10
[0063] In one example, a user, such as a network operator or a network
administrator may initiate the process of monitoring operations related to Network
Functions (NFs) in the network environment. In one example, the user may be using
a User Equipment (UE) (not depicted in FIGS. 3-4), which may be in
15 communication with the system [300]. The UE may be utilising a User Interface
(UI) [410], The UI [410] may be a part of the UE and may allow the user to initiate
and manage the process of monitoring operations related to Network Functions
(NFs) in the network environment. The UI [410] may also allow the UE to
communicate with the system [300]. In one example, the UI [410] may be
20 implemented as a Graphical User Interface (GUI).
[0064] In an example, the UI [410] (of the UE) and the system [300] may be in
communication over a SA_UI interface, which may be used for monitoring
operations related to network functions in the network environment, using HTTP25
based communication.
[0065] In operation, the user, using the UI [410], may initiate a request to perform
an operation on at least a NF. The request may include a set of details relating to the
operation. The transceiver unit [304] of the system [300] may receive said request.
30 This has been depicted by Step [402] in FIG. 4.
20
[0066] In an embodiment of the present disclosure, the request is an instruction or
command to perform an operation on at least one network function (NF). The
network function may be a cloud native function (CNF) or a virtualized network
function (VNF), or any other network function.
5
[0067] In another example, the request corresponds to at least one of instantiation
of network functions, migration of network functions to new hosts, and termination
of the network functions.
10 [0068] The CNFs are network functions designed and optimized to run in cloud
environments using cloud native principles. These functions are built to leverage
the benefits of cloud computing, including scalability, flexibility, and resilience.
The CNFs are often packaged and deployed in containers (e.g., Docker containers)
which provide a lightweight, portable, and consistent environment across different
15 stages of development and deployment. Further, CNFs are managed and
orchestrated using cloud-based platforms (as depicted in FIG. 4) such as container
orchestration platforms like Kubernetes, which handle deployment, scaling, and
management of containerized applications.
20 [0069] The VNFs are network functions that are implemented as software and run
on virtual machines (VMs) in a virtualized environment. They are designed to
replace traditional hardware-based network appliances with software-based
solutions running on standard hardware.
25 [0070] In another example, the set of details comprises information related at least
one of instantiation of the network functions, termination of the network functions,
intermediate level termination the network functions, backup operations related to
the network functions, restore operations related to the network functions, and
update operations related to the network functions.
30
21
[0071] The set of details within the request encompasses various types of
information that define operations to be performed on the network functions (NFs).
These operations are essential for managing both Cloud Native Network Functions
(CNFs) and Virtualized Network Functions (VNFs) in a network environment.
5
[0072] For example, the instantiation of the network functions refers to the creation
and deployment of new instances of network functions. The request may contain
details such as the network function image (for CNF or VNF), resource allocation
(e.g., CPU, memory), and the target node or cloud environment where the network
10 function may be instantiated.
[0073] The migration of network functions to new hosts refers to relocating an
existing network function from one host or node to another. The migration may be
necessary for various reasons, such as load balancing, resource optimization, or
15 recovery from a host failure.
[0074] The termination of network functions involves stopping and removing an
existing network function. The request to terminate a function specifies which
function is to be removed and may include options for a graceful shutdown or an
20 immediate stop.
[0075] Continuing further, in yet another example, the request is in a hypertext
transfer protocol (HTTP) format. The HTTP is a widely used communication
protocol for sending requests and receiving responses between clients and servers
25 over a network. The use of HTTP format means that the request to perform an
operation on the network function (NF) is structured according to the HTTP
standards. This involves using standard HTTP methods such as POST may use
when creating or instantiating a new network function (e.g., CNF or VNF). The
DELETE may use when terminating or removing a network function. The PUT or
30 PATCH may use when updating or modifying an existing network function. The
GET may be used to retrieve information or status of the network function.
22
[0076] Each HTTP request is forwarded to an event routing manager, which routes
the event from the publisher (requesting entity) to the relevant subscribers (such as
network function orchestrators, storage units, and service adaptors).
5
[0077] In an example, each operation will be initiated using separate HTTP requests
differentiated by event names, such as "INSTANTIATE_CNFC_ON_SITES" for
instantiation or "TERMINATE_CNFC" for termination.
10 [0078] Continuing further, the system [300] may interface with a cloud-based
platform [412] for managing Cloud Native Network Functions (CNFs). The cloudbased
platform [412] may provide the underlying infrastructure where CNFs are
deployed and operated. The cloud-based platform [412] may further include a
Docker or Kubernetes environment, along with Docker Host.
15
[0079] The kubernetes is an open-source platform used to manage, automate, and
orchestrate the deployment, scaling, and operation of containerized applications
across clusters of hosts. Also, kubernetes enables the automated deployment and
scaling of CNFs in a distributed cloud environment.
20
[0080] In the context of the present invention, the system [300] is responsible for
managing different operations, such as, instantiating, migrating, and terminating
CNFs/CNFCs by using Docker REST APIs and XFTP (Extended File Transfer
Protocol) to issue commands to the docker host.
25
[0081] The REST APIs are a set of standardized rules and protocols used for
creating, reading, updating, and deleting resources over the web. The REST APIs
handle all communication between various components, such as the Service
Adaptor (SA), Docker Host, Kubernetes, and UI [410].
30
23
[0082] The XFTP is a file transfer protocol that is typically extended to include
custom functionalities not covered by standard protocols like FTP. The XFTP
provides a secure channel through which the system [300] may send commands to
configure specific network functions to terminate a container running a CNF in the
5 cloud-based platform.
[0083] For example, when a request is received to instantiate a CNF, the system
[300] pulls the relevant image from a private Docker registry (from the cloud-based
platform) [412], allocates resources (such as CPU and memory), and deploys the
10 CNF within the cloud-based platform [412]. This deployment involves configuring
the CNF on the available cloud resources.
[0084] The docker registry is a storage and distribution system for docker images.
It is used to store and retrieve container images, which may be used to instantiate
15 containers in a docker environment.
[0085] In one embodiment, an interface, referred to as ‘SA interface’ acts as an
intermediary between the system [300], Docker Host, and Docker Registry. The SA
interface is designed not only to pull images from the private Docker registry but
20 also to upload new or updated CNF images to the private registry.
[0086] The system [300] also supports the execution of custom commands to
manage network functions using the XFTP. For example, during the instantiation
of a CNF, custom commands may be sent to the Docker host to allocate additional
25 resources or to perform specific configurations required by the CNF.
[0087] Considering an example, the system [300] receives an HTTP request to
instantiate the NF. The system [300] interacts with the Docker host (or Kubernetes
environment) through the Docker REST API, pulling the specified CNF image from
30 a registry (e.g., a private Docker registry). The system [300] uses the XFTP protocol
24
to issue custom commands for instantiation, confirming the NF is launched on the
targeted cloud infrastructure.
[0088] Once the CNF is successfully deployed, the system [300] responds with an
acknowledgment t 5 o confirm that the instantiation was successful.
[0089] For another example, the termination of the Network Functions operation
involves removing or stopping a network function. The request may contain the
network function identifier (ID) and possibly a specification of the type of
10 termination (e.g., graceful shutdown).
[0090] Upon receiving the HTTP request for termination, the system communicates
with the Docker host to stop and delete the CNF container from the cloud-based
platform [412]. The system then interacts with the Docker repository to delete the
15 CNF image if required, and sends notifications to other microservices (such as
policy management engine or alarm management systems) to clear any associated
data or configurations. Once terminated, a response is sent back confirming the
operation.
20 [0091] For yet another example, instead of a complete termination, the system
[300] may perform an intermediate level termination. This may be useful for
temporary suspension of a network function (e.g., for maintenance or scaling down
resources) without fully removing it from the infrastructure.
25 [0092] The backup operations may be related to network functions. The request
may include commands to back up the network function's state, data, and
configurations.
[0093] This is important for confirming disaster recovery and maintaining the
30 ability to restore the network function in case of failure. The backup operations
involve creating a picture of the network function’s current state, which is then
25
stored in a secure location (e.g., a backup server). This picture can later be used for
restore operations.
[0094] The restore operations related to network functions which may restore a
network function from 5 a previously created backup. The request may specify the
backup identifier and the target environment for restoration. This operation is
typically used after a failure or data loss event.
[0095] In the event of a node failure, the cloud-based platform [412] may work in
10 conjunction with the system to automatically shift CNFs to other available
resources or sites. The cloud-based platform [412] supports this failover process by
reallocating resources and redeploying CNFs to continued service availability.
[0096] The update operations related to network functions are he set of details may
15 include commands to update a network function, such as applying patches, updating
configurations, or migrating to a newer version.
[0097] In addition to managing CNF instantiation, the system plays an important
role in managing the Docker images. When a CNF is terminated, the system
20 interacts with the Docker repository to delete the associated CNF images. After the
deletion of these images, the system [300] notifies other microservices to clear
related data, such as policies, images from the Resource Management Repository
(RMR), and alarm/config dictionaries.
25 [0098] Further, the system [300] supports a wide range of operations such as
migration, scaling, health monitoring, and logging.
[0099] Continuing further with the present example, once the request is received
(e.g., a request to instantiate, terminate, or migrate a network function), the
30 transceiver unit [304] may then transmit, to the UI, a first acknowledgement
indicative of receipt of the request. This has been depicted by Step [404] in FIG. 4.
26
This acknowledgment confirms that the request has been successfully received by
the system.
[0100] This first acknowledgment is part of a larger system to handle asynchronous
5 communication, which means that operations may proceed in the background after
the initial acknowledgment is sent, and final results or status updates may be
provided later.
[0101] For example, if the user sends a request to instantiate a CNF, the transceiver
10 unit [304] receives this request and immediately responds to the UI [410] with a
first acknowledgment to indicate that the system [300] is working on fulfilling the
request, even if the instantiation process itself will take more time. This keeps the
user informed while the operation progresses in the background.
15 [0102] After receiving the acknowledgement, a storage unit [306] may store, a
record of the received request, and the first acknowledgement in a database [414].
This has been depicted by Step [406] in FIG. 4. For example, the storage unit [306]
logs the request details (such as request type, parameters, and timestamp) and the
first acknowledgment into the database [414].
20
[0103] Continuing further, after the storage unit [306] has recorded the request and
the acknowledgment in the database [414], the transceiver unit [304] may receive,
from the database [414], a second acknowledgement indicative of storing of the
record in the database [414]. This has been depicted by Step [408] in FIG. 4. This
25 second acknowledgment indicates that the record has been successfully stored. This
acknowledgment indicates that the storage operation has been completed, and the
data is now safely stored in the database [414].
[0104] In an example, the first acknowledgement, and the second
30 acknowledgement are in one of a JavaScript Object Notation (JSON) format and
Extensible Markup Language (XML) format.
27
[0105] Both JSON and XML are standard formats for data interchange and are
widely supported by various systems and platforms. Using these formats confirm
compatibility and ease of integration with different technologies. JSON provides a
compact and easily 5 readable format, which is beneficial for web applications and
APIs. XML offers a more detailed and hierarchical structure, which can be useful
for more complex data representations.
[0106] However, it may be noted that the aforementioned formats of the first
10 acknowledgement request and the second acknowledgement request are only
exemplary, and in no manner is construed to limit the scope of the present subject
matter in any manner. Any other formats may also be used for generating the
acknowledgement message, and all such examples would also lie within the scope
of the present subject matter.
15
[0107] Referring to FIG. 5, an exemplary method flow diagram [500] for
monitoring operations related to network functions in a network environment in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [500] is performed by the system [300]. Further, in
20 an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 5, the method [500]
starts at step [502].
[0108] In one embodiment, the system [300] may deploy an event-driven
25 architecture, known to a person skilled in the art, to handle operations related to
network functions. In such cases, the system [300] may use standard REST APIs
for communication between various components over HTTP, similar to the way
clients and servers exchange data.
30 [0109] At step [504], the method [500] comprises receiving, by a transceiver unit
[304] via a user interface (UI) [410], a request to perform an operation on at least a
28
network function (NF), wherein the request comprises a set of details relating to the
operation.
[0110] In one example, a user, such as a network operator or a network
administrator may 5 initiate the process of monitoring operations related to Network
Functions (NFs) in the network environment. In one example, the user may be
utilising a User Interface (UI) [410], which may be in communication with the
system [300]. The UI [410] may allow the user to initiate and manage the process
of monitoring operations related to Network Functions (NFs) in the network
10 environment.
[0111] In an example, the UI [410] and the system [300] may be in communication
over a SA_UI interface, which may be used for monitoring operations related to
network functions in the network environment, using HTTP-based communication.
15
[0112] In operation, the user, using the UI [410], may initiate a request to perform
an operation on at least a NF. The request may include a set of details relating to the
operation. The transceiver unit [304] of the system [300] may receive said request.
20 [0113] In an embodiment of the present disclosure, the request is an instruction or
command to perform an operation on at least one network function (NF). The
network function may be a cloud native function (CNF) or a virtualized network
function (VNF), or any other network function.
25 [0114] In another example, the request corresponds to at least one of instantiation
of network functions, migration of network functions to new hosts, and termination
of the network functions.
[0115] In another example, the set of details comprises information related at least
30 one of instantiation of the network functions, termination of the network functions,
intermediate level termination the network functions, backup operations related to
29
the network functions, restore operations related to the network functions, and
update operations related to the network functions.
[0116] The set of details within the request encompasses various types of
information 5 that define operations to be performed on the network functions (NFs).
These operations are essential for managing both Cloud Native Network Functions
(CNFs) and Virtualized Network Functions (VNFs) in a network environment.
[0117] For example, the instantiation of the network functions refers to the creation
10 and deployment of new instances of network functions. The request may contain
details such as the network function image (for CNF or VNF), resource allocation
(e.g., CPU, memory), and the target node or cloud environment where the network
function may be instantiated.
15 [0118] The migration of network functions to new hosts refers to relocating an
existing network function from one host or node to another. The migration may be
necessary for various reasons, such as load balancing, resource optimization, or
recovery from a host failure.
20 [0119] The termination of network functions involves stopping and removing an
existing network function. The request to terminate a function specifies which
function is to be removed and may include options for a graceful shutdown or an
immediate stop.
25 [0120] Continuing further, in yet another example, the request is in a hypertext
transfer protocol (HTTP) format.
[0121] Continuing further, the system [300] may interface with a cloud-based
platform [412] for managing Cloud Native Network Functions (CNFs). The cloud30
based platform [412] may provide the underlying infrastructure where CNFs are
30
deployed and operated. The cloud-based platform [412] may further include a
Docker or Kubernetes environment, along with Docker Host.
[0122] In the context of the present invention, the system [300] is responsible for
managing different operations, 5 such as, instantiating, migrating, and terminating
CNFs by using Docker REST APIs and XFTP (SimpleX File Transfer Protocol) to
issue commands to the docker host.
[0123] For example, when a request is received to instantiate a CNF, the system
10 [300] pulls the relevant image from a private Docker registry (from the cloud-based
platform), allocates resources (such as CPU and memory), and deploys the CNF
within the cloud-based platform [412]. This deployment involves configuring the
CNF on the available cloud resources.
15 [0124] The system [300] also supports the execution of custom commands to
manage network functions using the XFTP. For example, during the instantiation
of a CNF, custom commands may be sent to the Docker host to allocate additional
resources or to perform specific configurations required by the CNF.
20 [0125] For another example, the termination of the Network Functions operation
involves removing or stopping a network function. The request may contain the
network function identifier (ID) and possibly a specification of the type of
termination (e.g., graceful shutdown).
25 [0126] For yet another example, instead of a complete termination, the system
[300] may perform an intermediate level termination. This may be useful for
temporary suspension of a network function (e.g., for maintenance or scaling down
resources) without fully removing it from the infrastructure.
31
[0127] The backup operations may be related to network functions. The request
may include commands to back up the network function's state, data, and
configurations.
[0128] 5 The restore operations related to network functions which may restore a
network function from a previously created backup. The request may specify the
backup identifier and the target environment for restoration. This operation is
typically used after a failure or data loss event.
10 [0129] In the event of a node failure, the cloud-based platform [412] may work in
conjunction with the system to automatically shift CNFs to other available
resources or sites. The cloud-based platform [412] supports this failover process by
reallocating resources and redeploying CNFs to continued service availability.
15 [0130] The update operations related to network functions are he set of details may
include commands to update a network function, such as applying patches, updating
configurations, or migrating to a newer version.
[0131] In addition to managing CNF instantiation, the system plays an important
20 role in managing the Docker images. When a CNF is terminated, the system
interacts with the Docker repository to delete the associated CNF images. After the
deletion of these images, the system [300] notifies other microservices to clear
related data, such as policies, images from the Resource Management Repository
(RMR), and alarm/config dictionaries.
25
[0132] Further, the system [300] supports a wide range of operations such as
migration, scaling, health monitoring, and logging.
[0133] At step [506], the method [500] comprises transmitting, by the transceiver
30 unit [304], to the UI, a first acknowledgement indicative of receipt of the request.
32
[0134] Continuing further with the present example, once the request is received
(e.g., a request to instantiate, terminate, or migrate a network function), the
transceiver unit [304] may then transmit, to the UI, a first acknowledgement
indicative of receipt of the request. This acknowledgment confirms that the request
5 has been successfully received by the system.
[0135] This first acknowledgment is part of a larger system to handle asynchronous
communication, which means that operations may proceed in the background after
the initial acknowledgment is sent, and final results or status updates may be
10 provided later.
[0136] For example, if the user sends a request to instantiate a CNF, the transceiver
unit [304] receives this request and immediately responds to the UI with a first
acknowledgment to indicate that the system [300] is working on fulfilling the
15 request, even if the instantiation process itself will take more time. This keeps the
user informed while the operation progresses in the background.
[0137] At step [508], the method [500] comprises storing, by a storage unit [306],
a record of the received request, and the first acknowledgement in a database [414].
20
[0138] After receiving the acknowledgement, a storage unit [306] may store, a
record of the received request, and the first acknowledgement in a database [414].
For example, the storage unit [306] logs the request details (such as request type,
parameters, and timestamp) and the first acknowledgment into the database [414].
25
[0139] At step [510], the method [500] comprises receiving, by the transceiver unit
[304], from the database [414], a second acknowledgement indicative of storing of
the record in the database [414].
30 [0140] Continuing further, after the storage unit [306] has recorded the request and
the acknowledgment in the database [414], the transceiver unit [304] may receive,
33
from the database [414], a second acknowledgement indicative of storing of the
record in the database [414]. This has been depicted by Step [408] in FIG. 4. This
second acknowledgment indicates that the record has been successfully stored. This
acknowledgment indicates that the storage operation has been completed, and the
5 data is now safely stored in the database [414].
[0141] In an example, the first acknowledgement, and the second
acknowledgement are in one of a JavaScript Object Notation (JSON) format and
Extensible Markup Language (XML) format.
10
[0142] Thereafter, the method terminates at step [512].
[0143] The present disclosure further discloses a User Equipment (UE). The UE
comprises a memory and a processor connected to the memory. The processor is
15 configured to transmit, via a User Interface (UI), a request to a system. The request
is to perform an operation on at least a Network Function (NF). Further, the request
includes a set of details relating to the operation. The processor is further configured
to receive, at the UI, a first acknowledgement from the system. The first
acknowledgement is indicative of receipt of the request.
20
[0144] The present disclosure furthermore discloses a non-transitory computer
readable storage medium storing instructions for monitoring operations related to
network functions in a network environment. The instructions include executable
code which, when executed by one or more units of a system, causes a transceiver
25 unit [304] of the system [300] to receive, via a user interface (UI), a request to
perform an operation on at least a network function (NF), wherein the request
comprises a set of details relating to the operation. Further, the instructions include
executable code which, when executed, causes the transceiver unit [304] to
transmit, to the UI [410], a first acknowledgement indicative of receipt of the
30 request. Further, the instructions include executable code which, when executed,
causes a storage unit [306] to store a record of the received request and the first
34
acknowledgement in a database [414]. Further, the instructions include executable
code which, when executed, causes the transceiver unit [304]to receive, from the
database, [414], a second acknowledgement indicative of storing of the record in
the database [414].
5
[0145] As is evident from the above, the present disclosure provides a technically
advanced solution for monitoring operations related to network functions in a
network environment. Implementing the features of the present solution, all
information related to the network functions is visible on the user interface of the
10 automation platform. Further, the present invention is less prone to errors as there
is no manual intervention.
[0146] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
15 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
and non-limiting.
20
[0147] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
25 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are considered to be encompassed within the scope
30 of the present disclosure.
35
We Claim:
1. A method [500] for monitoring operations related to network functions in a
network environment, the method [500] comprising:
- receiving [504], by a 5 transceiver unit [304] via a user interface (UI)
[410], a request to perform an operation on at least a network function
(NF), wherein the request comprises a set of details relating to the
operation;
- transmitting [506], by the transceiver unit [304], to the UI [410], a first
10 acknowledgement indicative of receipt of the request;
- storing [508], by a storage unit [306], a record of the received request
and the first acknowledgement in a database; and
- receiving [510], by the transceiver unit [304], from the database, a
second acknowledgement indicative of storing of the record in the
15 database.
2. The method [500] as claimed in claim 1, wherein the request is in a
hypertext transfer protocol (HTTP) format.
20 3. The method [500] as claimed in claim 1, wherein the first
acknowledgement, and the second acknowledgement are in one of a JavaScript
Object Notation (JSON) format and Extensible Markup Language (XML) format.
4. The method [500] as claimed in claim 1, wherein the request corresponds to
25 at least one of instantiation of network functions, migration of network functions to
new hosts, and termination of the network functions.
5. The method [500] as claimed in claim 1, wherein the set of details comprises
information related to at least one of instantiation of the network functions,
30 termination of the network functions, intermediate level termination of the network
36
functions, backup operations related to the network functions, restore operations
related to the network functions, and update operations related to the network
functions.
6. The method 5 [500] as claimed in claim 1, wherein the network functions
comprise at least one of cloud-native network functions (CNFs), and virtualised
network functions (VNFs).
7. The method [500] as claimed in claim 1, wherein the UI and the transceiver
10 unit [304] are in communication over a SA_UI interface.
8. A system [300] for monitoring operations related to network functions in a
network environment, the system comprising:
- a processing unit [302];
15 - a transceiver unit [304] connected at least to the processing unit [302],
wherein the transceiver unit [304] is configured to:
o receive, via a user interface (UI), a request to perform an
operation on at least a network function (NF), wherein the
request comprises a set of details relating to the operation;
20 o transmit, to the UI, a first acknowledgement indicative of receipt
of the request;
- a storage unit [306] connected at least to the transceiver unit [304],
wherein the storage unit [306] is configured to: store, a record of the
received request, and the first acknowledgement in a database; and
25 - the transceiver unit [304] is further configured to: receive, from the
database, a second acknowledgement indicative of storing of the record
in the database.
9. The system [300] as claimed in claim 8, wherein the request is in a hypertext
30 transfer protocol (HTTP) format.
37
10. The system [300] as claimed in claim 8, wherein the first acknowledgement,
and the second acknowledgement are in one of a JavaScript Object Notation
(JSON) format and Extensible Markup Language (XML) format.
5
11. The system [300] as claimed in claim 8, wherein the request corresponds to
at least one of instantiation of network functions, migration of network functions to
new hosts, and termination of the network functions.
10 12. The system [300] as claimed in claim 8, wherein the set of details comprises
information related at least one of instantiation of the network functions,
termination of the network functions, intermediate level termination the network
functions, backup operations related to the network functions, restore operations
related to the network functions, and update operations related to the network
15 functions.
13. The system [300] as claimed in claim 8, wherein the network functions
comprise at least one of cloud-native network functions (CNFs), and virtualised
network functions (VNFs).
20
14. The system [300] as claimed in claim 8, wherein the UI and the system [300]
are in communication over a SA_UI interface.
15. A User Equipment (UE) comprising:
25 - a memory; and
- a processor connected to the memory, wherein the processor is
configured to:
o transmit, via a User Interface (UI) [410], a request to a system
[300], wherein the request is to perform an operation on at least
38
a Network Function (NF), and wherein the request comprises a
set of details relating to the operation; and
o receive, at the UI [410], a first acknowledgement from the
system [300], wherein the first acknowledgement is indicative
5 of receipt of the request