FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR AUTOMATING UPGRADES
ON ONE OR MORE NETWORK FUNCTIONS (NFs) IN A
NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre
Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in
which it is to be performed.
2
METHOD AND SYSTEM FOR AUTOMATING UPGRADES ON ONE OR
MORE NETWORK FUNCTIONS (NFs) IN A NETWORK
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 automating upgrades on one or more
network functions (NFs) in a network.
10
BACKGROUND
[0002] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may
15 include certain aspects of the art that may be related to various features of the
present disclosure. However, it should be appreciated that this section is used only
to enhance the understanding of the reader with respect to the present disclosure,
and not as admissions of the prior art.
20 [0003] Wireless communication technology has rapidly evolved over the past few
decades, with each generation bringing significant improvements and
advancements. The first generation of wireless communication technology was
based on analog technology and offered only voice services. However, with the
advent of the second-generation (2G) technology, digital communication and data
25 services became possible, and text messaging was introduced. The third-generation
(3G) technology marked the introduction of high-speed internet access, mobile
video calling, and location-based services. The fourth-generation (4G) technology
revolutionized wireless communication with faster data speeds, better network
coverage, and improved security. Currently, the fifth-generation (5G) technology is
30 being deployed, promising even faster data speeds, low latency, and the ability to
connect multiple devices simultaneously. With each generation, wireless
3
communication technology has become more advanced, sophisticated, and capable
of delivering more services to its users.
[0004] In the 5G communication system, there is provided a plurality of network
functions (NFs), for example an Access 5 and Mobility Management Function
(AMF), session management function (SMF), Authentication Server function
(AUSF), a Network Slice Selection Function (NSSF), Policy control function
(PCF), a Network Repository Function (NRF), Network Exposure Function (NEF)
and the like. One or more of the aforementioned NFs communicate with each other,
10 to implement multiple activities on the 5G communication system. For example,
NEF is one of the key network functions, which supports for creating new services
in network domain, such as data and network services, easily available for
communication service providers and third-party domains.
15 [0005] In 5G communication system, installations, deployments and upgradations
such as, but not limited to, installing operating system, bios upgrade, security
patches, dockers and others of 5G Network Functions Infrastructure and Cloud
Native services are challenging and cumbersome tasks. For different Network
Function nodes and Cloud Native services, there is a need for different types of
20 interfaces and different tools for different phases such as from installation to any
required upgradation, and there is a need for specific, dedicated and multiple models
based on upgradation. Further, in a conventional system, each type of Cloud Native
upgradation and infrastructural patches to comply with the 5G standards happen at
each 5G network function level with manual approach, which takes more time and
25 gives scope to manual errors. For implementing any sort of new features and
upgradation such as dockers, containers, applications or operating system (OS), and
their versions in the network, there is a requirement for different manual procedures,
processes, interfaces and teams for deploying such upgradations in the network.
30 [0006] Thus, there exists an imperative need in the art to provide an efficient system
and method for core network automation adoption platform, which automates the
4
5G Network Function’s Infrastructural and Cloud native services. The present
system and method provide a single platform which has different interfaces which
point to different category of automation and thus helping in flawless and quick
upgrades. The present system and method provide a platform which automates the
Infrastructural and Cloud native installation 5 and upgrades for 5GCN containerized
stack at scale. Further, the present system and method provide a platform which
may reduce deployment time by executing any upgrades in multiple nodes
parallelly in the network.
10 SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.
This summary is not intended to identify the key features or the scope of the claimed
15 subject matter.
[0008] An aspect of the present disclosure may relate to a method for automating
upgrades on one or more network functions (NFs) in a network, the method
comprising receiving, by a transceiver unit at an automation node, a selection of
20 one or more network function (NFs). The method further comprises establishing,
by the transceiver unit at the automation node, a connection between the automation
node and the one or more selected NFs. The method further comprises identifying,
by a processing unit at the automation node, one or more interfaces associated with
the one or more selected NFs. The method further comprises triggering, by the
25 processing unit at the automation node, via the one or more interfaces, an
automation task for upgrading the one or more NFs.
[0009] In an exemplary aspect of the present disclosure, the selection of the one or
more NFs is received at the automation node based on a first user input at a user
30 interface of the automation node.
5
[0010] In an exemplary aspect of the present disclosure, the upgrades on the one or
more NFs are performed to comply with network standard.
[0011] In an exemplary aspect of the present disclosure, the automation task is
performed remotely on the one or more 5 interfaces associated with the one or more
NFs.
[0012] In an exemplary aspect of the present disclosure, the automation task
comprises an execution of at least one of one or more script(s), instruction(s),
10 command(s) and a set of code.
[0013] In an exemplary aspect of the present disclosure, the one or more interfaces
comprises at least a Cloud Native interface, a Security Enforcement interface, a
Deployment Prechecks interface, a health Check interface, an Infrastructure
15 Installation & Upgrades interface, and a Configuration and Operations interface.
[0014] In an exemplary aspect of the present disclosure, triggering the automation
task for upgrading the one or more NFs is based on a second user input at the user
interface of the automation node.
20
[0015] In an exemplary aspect of the present disclosure, the method further
comprises receiving, by the transceiver unit at the automation node, a task
completion acknowledgement from the automation task based on completion of the
automation task.
25
[0016] Another aspect of the present disclosure may relate to a system for
automating upgrades on one or more network functions (NFs) in a network, the
system comprising an automation node, wherein the automation node comprises: a
transceiver unit configured to receive, a selection of one or more Network Functions
30 (NFs). The transceiver unit is further configured to establish, a connection between
the automation node and the one or more selected NFs. A processing unit is
6
configured to identify, one or more interfaces associated with the one or more
selected NFs. The processing unit is further configured to trigger, via the one or
more interfaces, an automation task for upgrading the one or more NFs.
[0017] Yet another aspect of the present 5 disclosure may relate to a non-transitory
computer readable storage medium storing instruction for automating upgrades on
one or more network functions (NFs) in a network. The instructions include
executable code which, when executed by one or more units of a system, causes: a
transceiver unit, to receive, a selection of one or more Network Functions (NFs).
10 Further, the instructions include executable code which, when executed causes the
transceiver unit to establish, a connection between the automation node and the one
or more selected NFs. Further, the instructions include executable code which,
when executed causes a processing unit to identify, one or more interfaces
associated with the one or more selected NFs. Further, the instructions include
15 executable code which, when executed causes the processing unit to trigger, via the
one or more interfaces, an automation task for upgrading the one or more NFs.
OBJECTS OF THE DISCLOSURE
20 [0018] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for
automating upgrades on one or more network functions (NFs) in a network.
25
[0020] It is an object of the present disclosure to provide a system and a method for
automating upgrades on one or more network functions (NFs) in a network, which
automates the 5G Network Function’s Infrastructural and Cloud native services.
7
[0021] It is another object of the present disclosure to provide a system and a
method for providing automated Infrastructural and Cloud native installation and
upgrades for 5GCN containerized stack at scale.
[0022] It is another object 5 of the present disclosure to provide a system and a
method for enabling multi network function interfaces and Cloud Native service
installations and upgradation support with a single uniform platform in an
automated manner.
10 [0023] It is another object of the present disclosure to provide a system and a
method for providing platform which may reduce deployment time by executing
any upgrades on multiple nodes parallelly in the network.
DESCRIPTION OF THE DRAWINGS
15
[0024] 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,
20 emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the figures are not to be construed as
limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
25 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0025] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
30
8
[0026] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure.
[0027] FIG. 3 illustrates an exemplary 5 block diagram of a system comprising an
automation node [300] for automating upgrades on one or more network functions
(NFs) in a network, in accordance with exemplary implementations of the present
disclosure.
10 [0028] FIG. 4 illustrates a method flow diagram [400] for automating upgrades on
one or more network functions (NFs) in a network, in accordance with exemplary
implementations of the present disclosure.
[0029] FIG. 5 illustrates a flow diagram [500] of automating upgrades on one or
15 more network functions (NFs) in a network, in accordance with the exemplary
embodiments of the present invention.
[0030] FIG. 6 illustrates a system architecture [600] for automating upgrades on
one or more network functions (NFs) in a network, in accordance with the
20 exemplary embodiments of the present invention.
[0031] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
25 DETAILED DESCRIPTION
[0032] 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
30 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
9
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.
[0033] The ensuing description provides exemplary 5 embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
10 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0034] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
15 ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
20 [0035] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
25 is terminated when its operations are completed but could have additional steps not
included in a figure.
[0036] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the
30 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
10
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 5 are intended to be inclusive—in a manner
similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0037] As used herein, a “processing unit” or “processor” or “operating processor”
10 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 microcontroller, Application Specific
15 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 processor.
20
[0038] 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
25 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
of implementing the features of the present disclosure. Also, the user device may
30 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.
11
[0039] 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”), 5 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
that may be required by one or more units of the system to perform their respective
functions.
10
[0040] 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
15 each other, which also includes the methods, functions, or procedures that may be
called.
[0041] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
20 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,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
25
[0042] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
and/or connected with the system.
30
12
[0043] In an implementation, the network is the 5th generation core network. In
another implementation, the network may be a 4th generation network, 6th
generation network, or any other future generations of network.
[0044] As discussed in the background 5 section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the abovementioned
and other existing problems in this field of technology by providing
method and system of automating upgrades on one or more network functions
(NFs) in a network.
10
[0045] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0046] FIG. 1 illustrates an exemplary block diagram representation of 5th
15 generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in figure 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
20 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
25 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
components are assumed to be connected to each other in a manner as obvious to
the person skilled in the art for implementing features of the present disclosure.
[0047] Radio Access Network (RAN) [104] is the part of a mobile
30 telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
13
It consists of radio base stations and the radio access technologies that enable
wireless communication.
[0048] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access 5 and mobility aspects, such as UE
registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0049] Session Management Function (SMF) [108] is a 5G core network function
10 responsible for managing session-related aspects, such as establishing, modifying,
and releasing sessions. It coordinates with the User Plane Function (UPF) for data
forwarding and handles IP address allocation and QoS enforcement.
[0050] Service Communication Proxy (SCP) [110] is a network function in the 5G
15 core network that facilitates communication between other network functions by
providing a secure and efficient messaging service. It acts as a mediator for servicebased
interfaces.
[0051] Authentication Server Function (AUSF) [112] is a network function in the
20 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
[0052] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
25 authorization services specific to network slices. It ensures that UEs can access only
the slices for which they are authorized.
[0053] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
30 such as subscription, requested services, and network policies.
14
[0054] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling
integration with third-party services and applications.
[0055] Network Repository Function (NRF) 5 [120] is a network function that acts
as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0056] Policy Control Function (PCF) [122] is a network function responsible for
10 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0057] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
15 authorization, and subscription information.
[0058] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network
capabilities and services.
20
[0059] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
25 [0060] Data Network (DN) [130] refers to a network that provides data services to
user equipment (UE) in a telecommunications system. The data services may
include but are not limited to Internet services, private data network related services.
[0061] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
30 upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
15
implementation, the computing device [200] may also implement a method for
automating upgrades on one or more network functions (NFs) in a network utilising
the system. In another implementation, the computing device [200] itself
implements the method for automating upgrades on one or more network functions
(NFs) in a network using one 5 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.
[0062] The computing device [200] may include a bus [202] or other
10 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
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]
15 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 media
accessible to the processor [204], render the computing device [200] into a special20
purpose 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
information and instructions for the processor [204].
25 [0063] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
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
30 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
16
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
cursor movement on the display 5 [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.
[0064] The computing device [200] may implement the techniques described
10 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
15 sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
20 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0065] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two25
way data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] may be a
30 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
17
implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0066] The computing device [200] can 5 send messages and receive data, including
program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], the host [224] and the communication interface
10 [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.
[0067] Referring to FIG. 3, an exemplary block diagram of a system comprising an
15 automation node [300] for automating upgrades on one or more network functions
(NFs) in a network is shown, in accordance with the exemplary implementations of
the present disclosure. The automation node [300] represents a centralized node
responsible for implementing upgrades on the one or more NFs. The automation
node [300] comprises at least one transceiver unit [302], at least one processing unit
20 [304] an at least one user interface [306]. Also, all of the components/ units of the
automation node [300] are assumed to be connected to each other unless otherwise
indicated below. As shown in the FIG. 3 all units shown within the automation node
[300] should also be assumed to be connected to each other. Also, in FIG. 3 only a
few units are shown, however, the automation node [300] may comprise multiple
25 such units or the automation node [300] may comprise any such numbers of said
units, as required to implement the features of the present disclosure. In an
implementation, the automation node [300] may reside in a server or a network
entity.
30 [0068] The automation node [300] is configured for automating upgrades on one
or more network functions (NFs) in a network, with the help of the interconnection
18
between the components/units of the system [300]. The upgrades may be for
example, such as a software upgrade, configuration change, or any other
maintenance operation.
[0069] In order to perform automating 5 upgrades on one or more network functions
(NFs) in a network, the transceiver unit [302] at the automation node [300] is
configured to receive, a selection of one or more Network Functions (NFs).
[0070] In an implementation of the present disclosure, the Network Functions
10 (NFs) are defined for processing functions in a network, which have defined
functional behaviour and defined interfaces. Network Functions may offer different
capabilities and thus, different NF services to distinct consumers. Each of the NF
services offered by the NF shall be self-contained, reusable and use management
schemes independently of other NF services offered by the same Network Function
15 (e.g. for scaling, healing, etc). There can be dependencies between NF services
within the same Network Function due to sharing of some common resources, e.g.
context data. This does not preclude that NF services offered by a single NF are
managed independently of each other. In an exemplary implementation, some
examples of NFs in a 5G network are as shown in FIG. 1 like the PCF [122], the
20 AMF [106], the SMF [108], etc.
[0071] In an example, the selection of the one or more NFs is received at the
automation node [300] based on a first user input at a user interface [306] of the
automation node [300]. The user interface [306] may provide a list of NFs. The first
25 user input may select the one or more NFs from the provided list at the user interface
[306]. Further, the selection could be based on various criteria, like the need for
compliance or performance improvement. Also, the automation node [300] may be
a central system or device that manages the automation process.
30 [0072] Thereafter, the transceiver unit [302] is further configured to establish, a
connection between the automation node [300] and the one or more selected NFs.
19
In an implementation of the present disclosure, the connection may be established
based on network addresses, hostnames, or other unique identifiers associated with
the NFs. Once identified, the automation node [300] initiates a connection using a
suitable communication protocol. This may involve protocols like SSH, HTTPS, or
others, depending on the network environment 5 and the specific requirements of the
NFs. The automation node [300] must authenticate itself to the NFs using
credentials, such as passwords, keys, or certificates. This confirms that the
automation node [300] has the necessary permissions to interact with the NFs.
Finally, after successful authentication, a secure and stable communication channel
10 is established between the automation node [300] and the NFs.
[0073] Then, the processing unit [304] connected with at least the transceiver unit
[302], is configured to identify, one or more interfaces associated with the one or
more selected NFs. The interfaces are the points of interaction between the
15 automation node [300] and the NFs. These interfaces may include various APIs,
command-line interfaces (CLIs), or configuration management systems specific to
each NF. Network Functions offer different NF services to consumers and each NF
service is accessible by means of an interface. A list of interfaces is provided at the
user interface [306] of the automation node [300]. A user input at the user interface
20 [306] selects the one or more interfaces associated with the one or more selected
NFs. The selection based on the user input identifies the one or more interfaces,
which are used by the automation node [300] to communicate the necessary
instructions, which may include downloading and applying software updates,
adjusting configurations, or performing system checks on the one or more NFs.
25
[0074] In an exemplary implementation, the one or more interfaces comprise at
least a cloud native (CN) interface, a security enforcement (SE) interface, a
deployment prechecks (DP) interface, a health check (HC) interface, an
infrastructure installation & upgrades (IIU) interface, and a network function’s
30 configuration and operations (NCO) interface.
20
[0075] In other words, the cloud native (CN) interface may refer to an interface
designed for cloud-based environments for cloud native installation and
upgradation. The term cloud native refers to an application that was designed to
reside in the cloud from the start. Cloud native involves cloud technologies like
microservices, container orchestrators, and auto scaling. 5 The security enforcement
(SE) interface deals with ensuring that security protocols and policies are enforced
during upgrades. The deployment prechecks (DP) interface is used to verify that
conditions are suitable for deployment before proceeding with upgrades. The health
check (HC) interface monitors the status and functionality of the NFs to ensure they
10 are operational. The infrastructure installation & upgrades (IIU) interface is
specifically tailored for managing the installation and upgrade processes of
infrastructure components. And the network function’s configuration and
operations (NCO) interface manages configuration settings and operational aspects
of the NFs.
15
[0076] Further, the processing unit [304] is configured to trigger, via the one or
more interfaces, an automation task for upgrading the one or more NFs. In an
implementation of the present disclosure, triggering means sending specific
commands, executing scripts, or initiating processes that start the upgrade on the
20 selected NFs. The automation node [300] uses the identified interfaces to
communicate the necessary instructions, which may include downloading and
applying software updates, adjusting configurations, or performing system checks.
The triggering process may involve the automation node [300] executing
predefined workflows or scripts that have been designed to handle the upgrade
25 process. In an exemplary implementation, the automation task comprises an
execution of at least one of one or more script(s), instruction(s), command(s) and a
set of code. The automation task may execute one or more script(s), instruction(s),
command(s) or a set of code to implement the upgrades on the one or more NFs,
wherein the upgrades are implemented to comply with network standards.
30
21
[0077] In an exemplary implementation of the present disclosure, the upgrades on
the one or more NFs are performed to comply with network standards.
Standardization ensures interoperability, reliability, and efficiency in networking,
allowing devices from different manufacturers to work together seamlessly and
reducing costs by promoting the use 5 of common technologies. The automation task
is performed remotely on the one or more interfaces associated with the one or more
NFs, wherein triggering the automation task for upgrading the one or more NFs is
based on a second user input at the user interface [306] of the automation node
[300].
10
[0078] The automation task summarizes various actions that the automation node
[300] can perform, such as running scripts, executing commands, or deploying
code.
15 [0079] Thereafter, the transceiver unit [302] at the automation node [300], receives
a task completion acknowledgement from the automation task based on completion
of the automation task. This means a confirmation is received by the automation
node [300] indicating that the automation task has been successfully completed.
20 [0080] Referring to FIG. 4, an exemplary method flow diagram [400] for
automating upgrades on one or more network functions (NFs) in a network in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [400] is performed by the system [300]. Further, in
an implementation, the system [300] may be present in a server device to implement
25 the features of the present disclosure. Also, as shown in FIG. 4, the method [400]
starts at step [402].
[0081] At step 404, the method comprises, receiving, by a transceiver unit [302] at
an automation node [300], a selection of one or more network functions (NFs). The
30 automation node [300] represents a centralized node responsible for implementing
upgrades on the one or more NFs.
22
[0082] In an implementation of the present disclosure, the Network Functions
(NFs) are defined for processing functions in a network, which have defined
functional behaviour and defined interfaces. Network Functions may offer different
capabilities and thus, different NF services 5 to distinct consumers. Each of the NF
services offered by the NF shall be self-contained, reusable and use management
schemes independently of other NF services offered by the same Network Function
(e.g. for scaling, healing, etc). There can be dependencies between NF services
within the same Network Function due to sharing of some common resources, e.g.
10 context data. This does not preclude that NF services offered by a single NF are
managed independently of each other.
[0083] In an example, the selection of the one or more NFs is received at the
automation node [300] based on a first user input at a user interface [306] of the
15 automation node [300]. The user interface [306] may provide a list of NFs. The first
user input may select the one or more NFs from the provided list at the user interface
[306]. Further, the selection could be based on various criteria, like the need for
compliance or performance improvement to be performed on the one or more NFs.
Also, the automation node [300] may be a central system or device that manages
20 the automation process.
[0084] At step 406, the method comprises, establishing, by the transceiver unit
[302] at the automation node [300], a connection between the automation node
[300] and the one or more selected NFs. In an implementation of the present
25 disclosure, the connection may be established based on network addresses,
hostnames, or other unique identifiers associated with the NFs. Once identified, the
automation node [300] initiates a connection using a suitable communication
protocol. This may involve protocols like SSH, HTTPS, or others, depending on the
network environment and the specific requirements of the NFs. The automation
30 node [300] must authenticate itself to the NFs using credentials, such as passwords,
keys, or certificates. This confirms that the automation node [300] has the necessary
23
permissions to interact with the NFs. Finally, after successful authentication, a
secure and stable communication channel is established between the automation
node [300] and the NFs.
[0085] At step 408, the method comprises, identifying, 5 by a processing unit [304]
at the automation node [300], one or more interfaces associated with the one or
more selected NFs. A list of interfaces is provided at the user interface [306] of the
automation node [300]. A user input at the user interface [306] selects the one or
more interfaces associated with the one or more selected NFs. The selection based
10 on the user input identifies the one or more interfaces, which are used by the
automation node [300] to communicate the necessary instructions, which may
include downloading and applying software updates, adjusting configurations, or
performing system checks on the one or more NFs. The interfaces are the points of
interaction between the automation node [300] and the NFs. These interfaces may
15 include various APIs, command-line interfaces (CLIs), or configuration
management systems specific to each NF. Network Functions offer different NF
services to consumers and each NF service is accessible by means of an interface.
[0086] In an exemplary implementation, the one or more interfaces comprise at
20 least a cloud native (CN) interface, a security enforcement (SE) interface, a
deployment prechecks (DP) interface, a health check (HC) interface, an
infrastructure installation & upgrades (IIU) interface, and a network function’s
configuration and operations (NCO) interface.
25 [0087] In other words, the cloud native interface may refer to interfaces designed
for cloud-based environments, for cloud native installation and upgradation. The
security enforcement interface deals with ensuring that security protocols and
policies are enforced during upgrades. The deployment prechecks interface is used
to verify that conditions are suitable for deployment before proceeding with
30 upgrades. The health check interface monitors the status and functionality of the
NFs to ensure they are operational. The infrastructure installation & upgrades
24
interface is specifically tailored for managing the installation and upgrade processes
of infrastructure components. And the configuration and operations interface
manage configuration settings and operational aspects of the NFs.
[0088] At step 410, the me 5 thod comprises, triggering, by the processing unit [304]
at the automation node [300], via the one or more interfaces, an automation task for
upgrading the one or more NFs. In an implementation of the present disclosure, the
triggering means sending specific commands, executing scripts, or initiating
processes that start the upgrade on the selected NFs. The automation node [300]
10 uses the identified interfaces to communicate the necessary instructions, which may
include downloading and applying software updates, adjusting configurations, or
performing system checks. The triggering process may involve the automation node
[300] executing predefined workflows or scripts that have been designed to handle
the upgrade process. In an exemplary implementation, the automation task
15 comprises an execution of at least one of one or more script(s), instruction(s),
command(s) and a set of code. The automation task may execute one or more
script(s), instruction(s), command(s) or a set of code to implement the upgrades on
the one or more NFs, wherein the upgrades are implemented to comply with
network standards.
20
[0089] In an exemplary implementation of the present disclosure, the upgrades on
the one or more NFs are performed to comply with network standard.
Standardization ensures interoperability, reliability, and efficiency in networking,
allowing devices from different manufacturers to work together seamlessly and
25 reducing costs by promoting the use of common technologies. Further, the
automation task is performed remotely on the one or more interfaces associated
with the one or more NFs, wherein triggering the automation task for upgrading the
one or more NFs is based on a second user input at the user interface [306] of the
automation node [300].
30
25
[0090] The automation task summarizes various actions that the automation node
[300] can perform, such as running scripts, executing commands, or deploying
code.
[0091] Thereafter, the transceiver unit [302] 5 at the automation node [300], receives
a task completion acknowledgement from the automation task based on completion
of the automation task. This means a confirmation is received by the automation
node [300] indicating that the automation task has been successfully completed.
10 [0092] Thereafter, the method terminates at step (412).
[0093] FIG. 5 illustrates a flow diagram [500] of automating upgrades on one or
more network functions (NFs) in a network, in accordance with the exemplary
embodiments of the present invention.
15
[0094] The process begins at step [502] with a user input received at the Core
Network Automation Adoption Platform (CNAAP), where the user selects the
specific network function that requires upgrading as shown in step [504]. The
CNAAP performs the same function as the automation node [300] as shown in FIG.
20 3. This is the initial selection step where the CNAAP/automation node [300]
receives the selection of one or more network functions (NFs) for the upgrade
process.
[0095] Following the selection of the network function, the user provides further
25 input to choose the specific task for automation as shown in step [506]. This step
involves determining what type of automation task needs to be triggered, such as a
software upgrade, configuration change, or any other maintenance operation. The
choice of the task is critical as it directs the subsequent actions that the CNAAP
/automation node [300] will take to manage the upgrade of the selected network
30 function.
26
[0096] The FIG. 5 shows various interfaces [506] that the CNAAP/automation
node [300] use to interact with and to execute the selected tasks. These interfaces
include the Cloud Native (CN) Interface, Security Enforcement (SE) Interface,
Deployment Prechecks (DP) Interface, Health Check (HC) Interface, Infrastructure
Installation & Upgrades (IIU) Interface, 5 and NF’s Configuration and Operations
(NCO) Interface. Each interface represents a different aspect of the network
function’s operations and capabilities, and the automation code specific to each
interface is executed to carry out the desired task.
10 [0097] In an example, the cloud native (CN) interface is designed for interacting
with network functions that are built using cloud-native principles. These principles
typically include containerization, microservices, and dynamic orchestration. The
CN interface facilitates tasks such as deploying, scaling, and updating these cloudnative
components.
15
[0098] Further, the security enforcement (SE) interface is responsible for managing
and enforcing security protocols during the automation process. It may involve
tasks like validating authentication, applying security patches, ensuring encryption
standards, and enforcing access controls.
20
[0099] The deployment prechecks (DP) interface is used to perform a series of
checks before an upgrade or deployment task is executed. It may involve verifying
the current software version, checking available resources, ensuring compatibility,
and confirming that there are no conflicts or issues that could disrupt the upgrade
25 process.
[0100] The health check (HC) interface is responsible for monitoring the status and
health of the network functions before, during, and after the automation tasks. The
health checks may include monitoring system performance, validating service
30 availability, and checking the integrity of network functions.
27
[0101] The infrastructure installation & upgrades (IIU) interface focuses on the
tasks related to the physical or virtual infrastructure that supports the network
functions. This interface manages the installation of new hardware or software
components and oversees the upgrades to existing infrastructure elements.
5
[0102] The network function’s configuration and operations (NCO) interface deals
with the configuration management and operational tasks of the network functions.
This interface allows the automation platform to modify, apply, and verify
configuration settings across the network functions.
10
[0103] Finally, once the automation tasks are triggered and executed through the
respective interfaces as shown in step [508], the CNAAP/automation node [300]
receives task completion verification and acknowledgment as shown in step [510].
This step confirms that the CNAAP/automation node [300] is informed of the
15 successful completion of the upgrade or maintenance task, allowing it to confirm
that the network function has been properly updated or configured.
[0104] Referring to FIG. 6 illustrates a system architecture [600] for automating
upgrades on one or more network functions (NFs) in a network, in accordance with
20 the exemplary embodiments of the present invention, which automates the 5G
Network Function’s Infrastructural and Cloud native services is shown, in
accordance with the exemplary embodiments of the present invention. The system
[600] for automation adaption platform may have, such as, but not limited to, core
network automation adoption platform (CNAAP) [602], 5GCN NF Config and OPS
25 service [604], Cloud Native Installation and Upgrades service [606], Security
Enforcement service [608], Infrastructure Installation and Upgrade service [610],
NF Health Check service [612] and Deployment Precheck service [614]. The
CNAAP [602] uses NCO interface to connect with 5GCN NF Config and OPS
service [604] for such as, but not limited to, configuration and operational
30 upgradations, CN interface to connect with Cloud Native Installation and Upgrades
service [606] for such as, but not limited to, cloud and server upgradations, SE
28
interface to connect with Security Enforcement service [608] for such as, but not
limited to, applying patches and increasing the security, IIU interface to connect
with Infrastructure Installation and Upgrade service [610] for such as, but not
limited to, upgrading infrastructure OS, containers upgradation and others as per
requirement, HC interface to connect with NF 5 Health Check service [612] for such
as, but not limited to, monitoring such as server and components performance and
health and DP interface with Deployment Precheck service [614] for such as, but
not limited to, deploying such as operating system and other features. The system
[600] has different interfaces which point to different category of automation
10 service which helps flawless and quick upgrades, such as, CN Interface may use
Cloud native Installation & Upgrades for 5G network deployment, SE Interface
may use Security Enforcement as per 5G industry standards, DP Interface may use
Deployment Prechecks as per 5G NF requirement, HC Interface may use NF’s
Health Check for all 5GCN network functions, IIU Interface may use Infrastructure
15 Installation and Upgrades for all 5GCN network functions and NCO Interface may
use 5GCN NF’s Configuration and Operations.
[0105] The present disclosure further discloses a non-transitory computer readable
storage medium storing instruction for automating upgrades on one or more
20 network functions (NFs) in a network, the instructions include executable code
which, when executed by one or more units of a system, causes: a transceiver unit
[302], to receive, a selection of one or more Network Functions (NFs). Further, the
instructions include executable code which, when executed causes the transceiver
unit [302] to establish, a connection between the automation node [300] and the one
25 or more selected NFs. Further, the instructions include executable code which,
when executed causes a processing unit [304] to identify, one or more interfaces
associated with the one or more selected NFs. Further, the instructions include
executable code which, when executed causes the processing unit [304] to trigger,
via the one or more interfaces, an automation task for upgrading the one or more
30 NFs.
29
[0106] As is evident from the above, the present disclosure provides a technically
advanced solution of efficient system and method for automating upgrades on one
or more network functions (NFs) in a network, which automates the 5G Network
Function’s Infrastructural and Cloud native services. The present disclosure
provides a single platform which has different interfaces 5 which point to different
category of automation with helping flawless and quick upgrades. The present
disclosure provides a platform which automates the Infrastructural and Cloud native
installation and upgrades for 5GCN containerized stack at scale. The present
disclosure provides a platform which may reduce deployment time by executing
10 any upgrades in multiple nodes parallelly in the network. In another embodiment,
the present disclosure provides a system and method for a platform which may be
applicable for not only 5G, but also, for any other lower or higher network
communication technology.
15 [0107] 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
of the present disclosure will be apparent to those skilled in the art, whereby it is to
20 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0108] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can
25 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
as limiting the scope of the present disclosure. Consequently, alternative
30 arrangements and substitutions of units, provided they achieve the intended
30
functionality described herein, are considered to be encompassed within the scope
of the present disclosure.

We Claim:

1. A method for automating upgrades on one or more network functions (NFs)
in a network, the method comprising:
- receiving, by a transceiver unit [302] at an automation node [300], a
5 selection of one or more network function (NFs);
- establishing, by the transceiver unit [302] at the automation node [300],
a connection between the automation node [300] and the one or more
selected NFs;
- identifying, by a processing unit [304] at the automation node [300], one
10 or more interfaces associated with the one or more selected NFs;
- triggering, by the processing unit [304] at the automation node [300],
via the one or more interfaces, an automation task for upgrading the one
or more NFs.

2. The method as claimed in claim 1, wherein the selection of the one or more
NFs is received at the automation node [300] based on a first user input at a
user interface [306] of the automation node [300].

3. The method as claimed in claim 1, wherein the upgrades on the one or more
NFs are performed to comply with network standards.

4. The method as claimed in claim 1, wherein the automation task is performed
remotely on the one or more interfaces associated with the one or more NFs.

5. The method as claimed in claim 1, wherein the automation task comprises
an execution of at least one of one or more script(s), instruction(s),
command(s) and a set of code.

6. The method as claimed in claim 1, wherein the one or more interfaces
comprises at least a Cloud Native interface, a Security Enforcement
interface, a Deployment Prechecks interface, a health Check interface, an
32
Infrastructure Installation & Upgrades interface, and a Configuration and
Operations interface.

7. The method as claimed in claim 2, wherein triggering the automation task
for upgrading the one or more NFs is a 5 based on a second user input at the
user interface [306] of the automation node [300].

8. The method as claimed in claim 1, further comprises:
receiving, by the transceiver unit [302] at the automation node [300], a task
10 completion acknowledgement from the automation task based on
completion of the automation task.

9. A system for automating upgrades on one or more network functions (NFs)
in a network, the system comprising:
15 an automation node [300], wherein the automation node [300] comprises:
- a transceiver unit [302], the transceiver unit [302] configured to:
o receive, a selection of one or more Network Functions (NFs);
o establish, a connection between the automation node [300] and
the one or more selected NFs;
20 - a processing unit [304], the processing unit [304] connected with at least
the transceiver unit [302], the processing unit configured to:
o identify, one or more interfaces associated with the one or more
selected NFs;
o trigger, via the one or more interfaces, an automation task for
25 upgrading the one or more NFs.

10. The system as claimed in claim 9, wherein the selection of the one or more
NFs is received at the automation node [300] based on a first user input at a
user interface [306] of the automation node [300].
30
33

11. The system as claimed in claim 9, wherein the upgrades on the one or more
NFs are performed to comply with network standards.

12. The system as claimed in claim 9, wherein the automation task is performed
remotely on the one or more interfaces 5 associated with the one or more NFs.

13. The system as claimed in claim 9, wherein the automation task comprises
an execution of at least one of one or more script(s), instruction(s),
command(s) and a set of code.

14. The system as claimed in claim 9, wherein the one or more interfaces
comprises at least a Cloud Native interface, a Security Enforcement
interface, a Deployment Prechecks interface, a health Check interface, an
Infrastructure Installation & Upgrades interface, and a Configuration and
15 Operations interface.

15. The system as claimed in claim 10, wherein triggering the automation task
for upgrading the one or more NFs is based on a second user input at the
user interface [306] of the automation node [300].

16. The system as claimed in claim 9, further comprises:
receiving, by the transceiver unit [302] at the automation node [300], a task
completion acknowledgement from the automation task based on
completion of the automation task.

Dated this the 8th Day of September, 2023