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 MANAGING LINK
FLUCTUATION IN A COMMUNICATION NETWORK”
15 We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre
Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
20
The following specification particularly describes the invention and the manner in
which it is to be performed.
25
2
METHOD AND SYSTEM FOR MANAGING LINK FLUCTUATION IN A
COMMUNICATION NETWORK
5
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to network
management systems. More particularly, embodiments of the present disclosure
10 relate to methods and systems for managing link fluctuation in a communication
network.
BACKGROUND
15 [0002] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may
include certain aspects of the art that may be related to various features of the
present disclosure. However, it should be appreciated that this section is used only
to enhance the understanding of the reader with respect to the present disclosure,
20 and not as admissions of the prior art.
[0003] Conventionally, in the wireless communication networks deploying the
5G technology, the network bonding (or link aggregation) is often used. The
multiple physical network interfaces of the network bonding help in creating the
25 one or more virtual network interfaces.
[0004] Additionally, often the network links that are aggregated together are
called slave links, and the bonded logical link is called the master (or primary) links.
Using network bonding, the multiple slave links act as if there is only one master
30 link that is working with more bandwidth and network redundancy. Thus, slave
3
network links often experience the problem of rapid link flapping for random or
asynchronous time intervals. The rapid link flapping refers to a condition where a
communication link alternates between up and down states. The rapid link flapping
is caused by end station reboots, power-saving features, incorrect duplex
5 configuration or marginal connections and signal integrity issues on the links.
[0005] Further, over the period various solutions have been developed to
address the problems relating to various network interruptions, reduced network
downtime and low network reliability and stability. In the link flapping, the master
10 network link toggles rapidly between connected and disconnected states which
further leads to network disruptions and instability. Furthermore, the TOR switch
is often required to deactivate the port when the slave link experiences link flapping.
[0006] Thus, there exists an imperative need in the art to automate the
15 configuration of the network interfaces by configuring primary reselection as
failure for the slave link so that the primary link does not regain active status until
the slave link goes offline, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
20
[0007] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a system and a method
25 for managing link fluctuation in a communication network for enhancing the
reliability and stability of network bonding by addressing the issue of active link
flapping in a systematic and controlled manner.
4
[0009] It is another object of the present disclosure to improve the performance
of a communication network where multiple network links are aggregated together,
forming a bonded device to increase bandwidth and fault tolerance.
5 SUMMARY
[0010] 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
10 of the claimed subject matter.
[0011] An aspect of the present disclosure may relate to a method for managing
link fluctuation in a communication network. The method comprises checking, by
a checking unit, a connectivity between an automation server and a plurality of
15 network functions connected to the automation server. Thereafter, the method
comprises receiving, by a transceiver unit, a list of one or more network functions
to be automated. Thereafter, the method comprises selecting, by a selecting unit,
the one or more network functions from the list. Thereafter, the method comprises
remotely executing, by a processing unit, an automation script at the one or more
20 network functions. Thereafter, the method comprises restarting, by the processing
unit, the one or more network functions.
[0012] In an exemplary aspect of the present disclosure, the method further
comprises determining, by a determining unit, whether execution of the automation
25 script is completed at the one or more network functions.
[0013] In an exemplary aspect of the present disclosure, the one or more
network functions are restarted upon completion of the execution of the automation
script at the one or more network functions.
30
5
[0014] In an exemplary aspect of the present disclosure, the method further
comprises fetching, by fetching unit, a list of interfaces associated with the one or
more network functions from a storage unit.
5 [0015] In an exemplary aspect of the present disclosure, the automation script
is executed for each interface from the list of interfaces associated with the one or
more network functions.
[0016] In an exemplary aspect of the present disclosure, the list of interfaces
10 comprises a master interface and one or more slave interfaces.
[0017] In an exemplary aspect of the present disclosure, the automation script
comprises a set of instructions to enable the one or more slave interfaces to work as
a promoted master interface in an event the master interface fails.
15
[0018] In an exemplary aspect of the present disclosure, the automation script
is remotely executed by remotely enabling the one or more slave interfaces to work
as a promoted master interface in an event the master interface fails.
20 [0019] In an exemplary aspect of the present disclosure, the link fluctuation
indicates a toggling between a connected state and a disconnected state within a
predefined time period.
[0020] In an exemplary aspect of the present disclosure, the list of one or more
25 network functions to be automated is received in a user input, and wherein the user
input is received from an input unit.
[0021] Another aspect of the present disclosure may relate to a system for
managing link fluctuation in a communication network. The system comprises a
30 checking unit configured to check a connectivity between an automation server and
6
a plurality of network functions connected to the automation server. The system
further comprises a transceiver unit configured to receive a list of one or more
network functions to be automated. The system further comprises a selecting unit
configured to select the one or more network functions from the list. The system
5 further comprises a processing unit configured to remotely execute an automation
script at the one or more network functions. The processing unit is further
configured to restart the one or more network functions.
[0022] Yet another aspect of the present disclosure may relate to a user
10 equipment (UE). Further, the UE comprises a memory, and a processor connected
to the memory. Herein, the processor is configured to check a connectivity between
an automation server and a plurality of network functions connected to the
automation server. Further, the processor is configured to receive a list of one or
more network functions to be automated. Further, the processor is configured to
15 select the one or more network functions from the list. Further, the processor is
configured to remotely execute an automation script at the one or more network
functions. Further, the processor is configured to restart the one or more network
functions.
20 [0023] Yet another aspect of the present disclosure may relate to a nontransitory computer-readable storage medium, storing instructions for managing
link fluctuation in a communication network, the storage medium comprising
executable code which, when executed by one or more units of a system, causes: a
checking unit to check a connectivity between an automation server and a plurality
25 of network functions connected to the automation server; a transceiver unit to
receive a list of one or more network functions to be automated; a selecting unit to
select the one or more network functions from the list; and a processing unit to:
remotely execute an automation script at the one or more network functions; and
restart the one or more network functions.
30
7
BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the
5 disclosed methods and systems in which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Also, the embodiments shown in the figures are
not to be construed as limiting the disclosure, but the possible variants of the method
10 and system according to the disclosure are illustrated herein to highlight the
advantages of the disclosure. It will be appreciated by those skilled in the art that
disclosure of such drawings includes disclosure of electrical components or
circuitry commonly used to implement such components.
[0025] FIG. 1 illustrates an exemplary block diagram representation of 5th 15
generation core (5GC) network architecture.
[0026] FIG. 2 illustrates an exemplary block diagram of a computing device
upon which the features of the present disclosure may be implemented in
20 accordance with exemplary implementation of the present disclosure.
[0027] FIG. 3 illustrates an exemplary block diagram of a system for managing
link fluctuation in a communication network, in accordance with exemplary
implementations of the present disclosure.
25
[0028] FIG. 4 illustrates a method flow diagram for managing link fluctuation
in a communication network in accordance with exemplary implementations of the
present disclosure.
8
[0029] FIG. 5 illustrates an exemplary flow diagram for a process managing
link fluctuation in a communication network in accordance with exemplary
implementations of the present disclosure.
5 [0030] FIG. 6 illustrates an exemplary block diagram of an architecture in
which features of the present disclosure may be implemented, in accordance with
exemplary implementations of the present disclosure.
[0031] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0032] In the following description, for the purposes of explanation, various
15 specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
20 address any of the problems discussed above or might address only some of the
problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is
not intended to limit the scope, applicability, or configuration of the disclosure.
25 Rather, the ensuing description of the exemplary embodiments will provide those
skilled in the art with an enabling description for implementing an exemplary
embodiment. It should be understood that various changes may be made in the
function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
30
9
[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 ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
5 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0035] It should be noted that the terms "first", "second", "primary",
"secondary", "target" and the like, herein do not denote any order, ranking, quantity,
10 or importance, but rather are used to distinguish one element from another.
[0036] 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
15 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.
20 [0037] 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 to be construed as preferred or advantageous over other aspects or
25 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
similar to the term “comprising” as an open transition word—without precluding
30 any additional or other elements.
10
[0038] As used herein, a “processing unit” or “processor” or “operating
processor” includes one or more processors, wherein processor refers to any logic
circuitry for processing instructions. A processor may be a general-purpose
5 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 integrated circuits, etc. The processor may
10 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.
15 [0039] As used herein, “a user equipment”, “a user device”, “a smart-userdevice”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld
device”, “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
20 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
contain at least one input means configured to receive an input from unit(s) which
25 are required to implement the features of the present disclosure.
[0040] 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
30 medium includes read-only memory (“ROM”), random access memory (“RAM”),
11
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.
5
[0041] 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 refer to a set of rules or protocols that
define communication or interaction of one or more modules or one or more units
10 with each other, which also includes the methods, functions, or procedures that may
be called.
[0042] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
15 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.
20
[0043] As used herein the transceiver unit includes at least one receiver and at
least one transmitter configured respectively for receiving and transmitting data,
signals, information or a combination thereof between units/components within the
system and/or connected with the system.
25
[0044] As discussed in the background section, the current known solutions
have several shortcomings such as for overcoming the link flapping is the use of
TOR switch that deactivates the port in the communication network when the slave
link experiences link flapping by upgrading the configuration which involves
12
automating the primary reselect as failure. This deactivates the status of the master
link till the time active slave link goes offline.
[0045] The present disclosure aims to overcome the above-mentioned and
5 other existing problems in this field of technology by providing a method and a
system of managing link fluctuation in a communication network.
[0046] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
10 implementation of the present disclosure. As shown in fig. 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],
an Authentication Server Function (AUSF) [112], a Network Slice Specific
15 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
User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
20 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
telecommunications system that connects user equipment (UE) [102] to the core
25 network (CN) and provides access to different types of networks (e.g., 5G network).
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
30 network function responsible for managing access and mobility aspects, such as UE
13
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
5 function 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
10 5G core network that facilitates communication between other network functions
by providing a secure and efficient messaging service. It acts as a mediator for
service-based interfaces.
[0051] Authentication Server Function (AUSF) [112] is a network function in
15 the 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
20 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
25 such as subscription, requested services, and network policies.
[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.
30
14
[0055] Network Repository Function (NRF) [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.
5 [0056] Policy Control Function (PCF) [122] is a network function responsible
for 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
10 centralizes the management of subscriber data, including authentication,
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
15 capabilities and services.
[0059] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
20
[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.
25 [0061] FIG. 2 illustrates an exemplary block diagram of a computing device
[200] upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [200] may also implement a method for
managing link fluctuation in a communication network utilising the system [300].
30 In another implementation, the computing device [200] itself implements the
15
method for managing link fluctuation in a communication network using one or
more units configured within the computing device [200], wherein said one or more
units are capable of implementing the features as disclosed in the present disclosure.
5 [0062] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a random10 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 media
15 accessible to the processor [204], render the computing device [200] into a specialpurpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
20
[0063] A storage device [210], such as a magnetic disk, optical disk, or solidstate drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as
30 a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
16
cursor movement on the display [212]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
5 [0064] 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
10 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
15 process steps described herein. In alternative implementations of the present
disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0065] The computing device [200] also may include a communication
20 interface [218] coupled to the bus [202]. The communication interface [218]
provides a two-way data communication coupling to a network link [220] that is
connected to a local network [222]. For example, the communication interface
[218] may be an integrated services digital network (ISDN) card, cable modem,
satellite modem, or a modem to provide a data communication connection to a
25 corresponding type of telephone line. As another example, the communication
interface [218] may be a local area network (LAN) card to provide a data
communication connection to a compatible LAN. Wireless links may also be
implemented. In any such implementation, the communication interface [218]
sends and receives electrical, electromagnetic or optical signals that carry digital
30 data streams representing various types of information.
17
[0066] 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
5 transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], a host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
10
[0067] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing link fluctuation in a communication network, is shown, in accordance
with the exemplary implementations of the present disclosure. The system [300]
comprises at least one checking unit [302], at least one transceiver unit [304], at
15 least one selecting unit [306], at least one processing unit [308], at least one
determining unit [310], at least one fetching unit [312], at least one input unit [314],
and at least one storage unit [316]. 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 the figures all units shown within the system [300] should also be
20 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 user equipment (UE) [102] to implement the features of the present
25 disclosure. The system [300] may be a part of the UE [102] or may be independent
of but in communication with the UE [102]. 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 server/ network entity and partly in the UE
[102]. Further, while the present system [300] is described using an implementation
30 in 5G, the present system [300] may also be implemented in 4G and/or 6G
networks.
18
[0068] The system [300] is configured for managing link fluctuation in a
communication network, with the help of the interconnection between the
components/units of the system [300].
5
[0069] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can
be implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
10 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended
functionality described herein, are considered to be encompassed within the scope
15 of the present disclosure.
[0070] The system [300] comprises the checking unit [302] configured to
check a connectivity between an automation server and a plurality of network
functions connected to the automation server. Herein, the automation server is
20 responsible for automating a plurality of tasks across the plurality of network
functions. In an example, the automation server may utilize one or more automation
frameworks in order to enhance an overall efficiency, scalability, and flexibility of
the plurality of network functions.
25 [0071] Further, in an implementation of the present disclosure, the checking
unit [302] may utilize one or more processes to check the connectivity between the
automation server and the plurality of network functions.
[0072] In an implementation, the checking unit [302] may send small data
30 packets (or signals) to each network function from the plurality of network
19
functions. Further, based on a response from said network function is received
within a pre-defined time, the checking unit [302] may determine the connectivity
of said network function with the automation server.
5 [0073] In another implementation, the checking unit [302] may utilize one or
more methods to identify one or more connectivity errors such as packet loss,
latency, or network congestion, that may hinder communication between the
automation server and the plurality of network functions.
10 [0074] In yet another implementation, the checking unit [302] may verify one
or more communication protocols (such as TCP/IP, HTTP, or proprietary protocols)
that are used for exchange of data between the automation server and the plurality
of network functions.
15 [0075] In yet another implementation, the checking unit [302] may check for
any redundancy, such as in an event, a plurality of network paths are available, then
in such event, the checking unit [302] may ensure that any alternate communication
links does exist to provide one or more failover options in the event of the primary
path failure.
20
[0076] It is to be noted that the mentioned one or more process are mentioned
for the ease of understanding of the present disclosure, and any other process that
would be known to a person skilled in the art can be implemented to check the
connectivity between the automation server and the plurality of network functions.
25
[0077] Further, the checking unit [302] utilizes a structured procedure to check
the connectivity between the automation server and the plurality of network
functions. Firstly, the checking unit [302] may utilize on or more process mentioned
above (suppose the checking unit [302] may send small data packets to a network
30 function) and based on the response of said one or more process, the checking unit
20
[302] may determine a connection status between the automation server and the
plurality of network functions.
[0078] The system [300] further comprises transceiver unit [304] configured
5 to receive a list of one or more network functions to be automated.
[0079] Further, the list of network functions may include at least one of a
virtualized network function (VNFs), a cloud native functions (CNFs) or any other
network functions that are already mentioned within the FIG. 1. Further, it is to be
10 noted that the list of network functions can include any other network functions that
are not mentioned herein, and would be known to a person skilled in the art.
[0080] Herein, the list of one or more network functions to be automated is
received in a user input, and the user input is received from an input unit [314]. The
15 input unit [314] may refer to an interface accessed by one or more users for
providing one or more inputs such as herein, the list of network functions that is to
be automated.
[0081] In an example, the input unit [314] can be a graphical user interface
20 (GUI), that allows the one or more users to select the one or more network functions
through one or more visual methods which may include at least one of a dropdown
menus, checkboxes, or by inputting specific parameters.
[0082] In another example, the input unit [314] can be a command line
25 interface (CLI) that allows the one or more users to input commands manually to
specify the list of network functions from the plurality of network functions that
are to be automated.
21
[0083] In yet another example, the input unit [314] can be an application
programming interface (API) for allowing an external system to send the list of
network functions that are to be automated.
5 [0084] It is to be noted that the input unit [314] mentioned herein may include
any other networking units or interfaces that are not mentioned above and would be
known to a person skilled in the art.
[0085] Further, it is to be noted that the user input by the one or more users
10 may occur due to one or more reasons.
[0086] In an example, the one or more reasons may include a specific
operational requirement for one or more network functions that may require the one
or more network functions to be automated.
15
[0087] In another example, the one or more reasons may include a different
automation script to be required for each network function, therefore manual user
input may facilitate an automation of a network function based on the role of said
network function.
20
[0088] In yet another example, the one or more reasons may include that
automating a wrong network function may lead to performance issues for said
network functions and their associated network entities, therefore manual user input
may prevent such type of events.
25
[0089] In yet another example, the one or more reasons may include that in an
event of change (such as adding, removing or modification of roles in the network
function) may also require a manual input to automate said network functions that
may have changed.
30
22
[0090] Further, the system [300] comprises the selecting unit [306] is
configured to select the one or more network functions from the list. Herein, the
primary purpose of the checking unit [302] is to separate the one or more network
functions that may have a proper connection with the automation server to the one
5 or more network functions having a disrupted connection with the automation
server. Further, in an implementation, when the transceiver unit [304] receives the
list of the one or more network functions that are to be automated, then in such case
the selection unit is able to easily separate the one or more network functions from
the list of received network functions.
10
[0091] Further, post receiving the list of the network functions from the
transceiver unit [304], the selecting unit [306] may identify a connectivity status of
said list of network functions from the checking unit [302].
15 [0092] In an implementation, the selecting unit [306] may further select the one
or more network functions based on of other one or more criteria, which may
include but not limited to a type of network function, a current operational status,
requirement of one or more resources to automate the network function and others
that would be known to a person skilled in the art.
20
[0093] Further, the system [300] comprises the fetching unit [312] configured
to fetch a list of interfaces associated with the one or more network functions from
the storage unit [316]. Post selection of the one or more network functions, the
fetching unit [312] is responsible for retrieving the list of interfaces associated with
25 each selected network function from the storage unit [316]. Herein, the storage unit
[316] can be at least one of a cloud-based unit, a local database, and a repository
architecture, which contains information on each network function and their
corresponding interfaces.
23
[0094] In an implementation, the fetching unit [312] retrieves details
associated with the interfaces that manage the at least one of a selected network
functions from the list of network functions. In another implementation, the
fetching unit [312] may identify a particular interface (preferably a master interface)
5 which is responsible to control the specific network function, and other backup
interfaces (preferably a slave interface) that may take over said particular interface
in a particular event.
[0095] It is to be noted that the list of interfaces comprises the master interface
10 and one or more slave interfaces.
[0096] In an example, the master interface may be associated with a master
server. The master server may be a primary server responsible for controlling and
managing a particular network function. The master server may handle a major
15 chunk of all operations, configuration changes, and automation tasks related to said
network function.
[0097] In another example, the slave interface may be associated with a slave
server. The slave server may be a server may act as a backup server for the master
20 server. The slave server is further to be promoted to act as a master server in an
event of failure of said master server or if one or more issues are faced by said
master server.
[0098] The system [300] further comprises a processing unit [308] configured
25 to remotely execute an automation script at the one or more network functions. Post
selection of the master interface and the one or more slave interface from the storage
unit [316], the processing unit [308] may execute the automation script at the one
or more network functions. Herein, the automation script comprises a set of
instructions to enable the one or more slave interfaces to work as a promoted master
30 interface in an event the master interface fails. The set of instructions mentioned in
24
the automation script comprise the steps to perform one or more tasks without any
manual intervention, in an event of failure of the master interface.
[0099] Further, the automation script may further contain one or more details
5 associated with the corresponding network function. In one example, the one or
more details may contain a detailed information of the master interface status
associated with said network function. In another example, the one or more details
may contain a specific or a group of slave interfaces that are to be promoted as the
master interface. In yet another example, the one or more details may contain an
10 information associated with the process to perform the promotion of the identified
said slave interface to the master interface. In yet another example, the one or more
details may contain an information associated with the process of undertaking the
one or more ongoing tasks of the master interface by the slave interface in the event
of promotion of the slave interface. In yet another example, the one or more details
15 may contain an information associated with the process of synchronizing data
between the existing master interface and the newly promoted master interface to
ensure minimal disruption during the promotion of said slave interface.
[0100] The automation script is designed to manage a plurality of roles in a
20 master-slave architecture for interfaces, particularly to promote the slave interface
to the role of master interface in an event of failure of the master interface. It may
be noted that the automation script is preferably written in a high-level language
which may include but not limited to a python language, a bash language, and a
PowerShell language.
25
[0101] In an implementation, the primary purpose of the execution of the
automation script is to maintain high availability of one or more network functions
and minimize downtime in the event of master interface failure. In another
implementation, the execution of the automation script may ensure a continuation
30 of the one or more ongoing operations performed by the existing master interface.
25
[0102] Further, the automation script is remotely executed by remotely
enabling the one or more slave interfaces to work as a promoted master interface in
an event the master interface fails. Herein, the remotely execution of the automation
5 script on the identified slave interface indicates that the automation script is
remotely executed by the processing unit [308] without any direct physical
interaction with said slave interface. The remote execution of said automation script
is achieved through at least one or a combination of network protocols.
10 [0103] In an example, the remote execution of said automation script is
achieved through a secure shell that may facilitate in securely executing one or more
commands on remote servers. In another example, the remote execution of said
automation script is achieved through API calls that may trigger the automation
script via network management platforms. In yet another example, the remote
15 execution of said automation script is achieved through cloud management
interfaces that may execute commands through a cloud service provider.
[0104] In an example, the remote execution of the automation script may
increase an overall efficiency of network function during the failure of their
20 corresponding master interface.
[0105] In another example, the remote execution of the automation script may
minimize the downtime to facilitate the promotion of the slave interface to the
master interface.
25
[0106] In yet another example, the remote execution of the automation script
may facilitate the management of large-scale networks, as manual intervention is
time-consuming.
26
[0107] Further, the automation script is executed for each interface from the
list of interfaces associated with the one or more network functions. Herein, the
execution of the automation script over each interface may facilitate the transfer of
the ongoing operations of the existing master interface to the newly promoted
5 interface. Further, the automation script is configured with respect to a particular
interface therefore, there is a requirement to configure said automation script to
their corresponding interface.
[0108] It is to be noted that the link fluctuation indicates a toggling between a
10 connected state and a disconnected state within a predefined time period. The time
period mentioned In an implementation, the link fluctuation may occur due to one
or more reasons which may include but not limited to a network congestion,
hardware failures, or unstable connectivity. Herein, the hardware failures may refer
to a malfunction in the physical components of the interface, such as the CPU,
15 memory, or network card may lead to such link fluctuation. Further, the unstable
connectivity may refer to an event, where the interface may lose connection to the
network due which may make the interface unable to communicate with other
interfaces.
20 [0109] It is to be noted that the reasons for the link fluctuation may be due to
the one or more mentioned reasons or any other reasons that may be known to a
person skilled in the art.
[0110] The system [300] further comprises the determining unit [310]
25 configured to determine whether execution of the automation script is completed at
the one or more network functions. The determination unit may perform one or
more processes to determine the execution of the automation script at the one or
more network functions.
27
[0111] In an implementation, the automation script may include exit codes or
result flags that indicate whether the automation script is executed at the one or
more network functions. Herein, the flags are indicators that may indicate a success
or failure of the execution of the autonomous script. Further, the determination unit
5 may monitor the mentioned exit codes or flags to confirm the execution of the
autonomous script.
[0112] In another implementation, the determining unit [310] may analyse logs
which are generated by the automation script. Herein, the generated logs may
10 contain detailed step-by-step records of the execution of the autonomous script.
[0113] In another implementation, the determining unit [310] may also receive
feedback from the network functions. For instance, the NFs may send a status
message back to the determining unit [310] after completion of the autonomous
15 script.
[0114] Further, the processing unit [308] is configured to restart the one or
more network functions. It is to be noted that the one or more network functions are
restarted upon completion of the execution of the automation script at the one or
20 more network functions. Herein, the restarting of the one or more network functions
is necessary for one or more reasons.
[0115] In an example, the restarting of the one or more network functions is
necessary for applying changes at the one or more network functions. For instance,
25 the automation script may modify the configuration, reallocate resources, or update
specific settings, respectively of the one or more network functions. Therefore, a
restart of the one or more network functions may further ensure that the mentioned
changes are applied correctly and that the one or more network functions may
operate under the new settings.
30
28
[0116] In another example, the restarting of the one or more network functions
is necessary for clearing any temporary files or resources that may be granted during
the automation of the one or more network functions. Further, restarting the one or
more network functions may clear any unnecessary data, and may further ensure
5 that the one or more network functions are in a clean state.
[0117] In yet another example, the restarting of the one or more network
functions is necessary for maintaining stability in the one or more network functions
as the automation of the one or more network functions may cause the one or more
10 network functions to behave unpredictably, which is further resolved by restarting
of the one or more network functions.
[0118] For restarting the one or more network functions, the processing unit
[308] may firstly send a command to the one or more network functions to initiate
15 the restart. Herein, the command is sent using a plurality of protocols, such as by
the SSH or API specific to the network management platform.
[0119] Referring to FIG. 4, an exemplary method flow diagram [400] for
managing link fluctuation in a communication network, in accordance with
20 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 interface device to implement
the features of the present disclosure.
25 [0120] Also, as shown in Fig. 4, the method [400] starts at step [402].
[0121] At step [404], the method [400] comprises checking, by the checking
unit [302], the connectivity between the automation server and the plurality of
network functions connected to the automation server. Further, the list of one or
29
more network functions to be automated is received in the user input, and the user
input is received from the input unit [314].
[0122] At step [406], the method [400] comprises receiving, by the transceiver
5 unit [304], the list of one or more network functions to be automated.
[0123] At step [408], the method [400] comprises selecting, by the selecting
unit [306], the one or more network functions from the list.
10 [0124] The method [400] [400] further comprises fetching, by fetching unit
[312], the list of interfaces associated with the one or more network functions from
the storage unit [316].
[0125] The method [400] [400] further explains that the list of interfaces
15 comprises the master interface and one or more slave interfaces.
[0126] At step [410], the method [400] comprises remotely executing, by the
processing unit [308], the automation script at the one or more network functions.
Further, the automation script comprises a set of instructions to enable the one or
20 more slave interfaces to work as a promoted master interface in an event the master
interface fails.
[0127] Further, the automation script is remotely executed by remotely
enabling the one or more slave interfaces to work as a promoted master interface in
25 an event the master interface fails.
[0128] The method [400] further explains that the automation script is executed
for each interface from the list of interfaces associated with the one or more network
functions.
30
[0129] The method [400] further explains that the link fluctuation indicates the
toggling between the connected state and the disconnected state within a predefined
time period.
5
[0130] The further comprises determining, by the determining unit [310],
whether execution of the automation script is completed at the one or more network
functions.
10 [0131] At step [412], the method [400] comprises restarting, by the processing
unit [308], the one or more network functions.
[0132] The method [400] further explains that the processing unit [308]
configured to restart the one or more network functions. It is to be noted that the
15 one or more network functions are restarted upon completion of the execution of
the automation script at the one or more network functions.
[0133] Thereafter, at step [414], the method [400] is terminated.
20 [0134] Referring to FIG. 5, an exemplary flow diagram [500] of a process for
managing link fluctuation in a communication network, in accordance with
exemplary implementations of the present disclosure is shown. In an
implementation the flow [500] is performed by the system [300].
25 [0135] At step 502, an automation interface receives a user input. Herein, the
user input may include specific instructions or requests from a user, for identifying
one or more network functions, where a configuration change or automation task is
required.
31
[0136] At step 504, the automation server may select the one or more network
functions over which a primary reselect configuration is required. Herein, the one
or more network functions can be a interface or a group of interfaces, where one of
the slave interfaces is to be promoted to the master interface, due to failure at the
5 master service. It is to be noted that based on the user input, the automation server
identifies the one or more network functions that require the primary interface to be
reselected (a slave interface is to be promoted), ensuing that only the necessary one
or more network functions are selection for the promotion of slave interfaces
associated with the selected one or more network functions.
10
[0137] At step 506, post selection of the necessary one or more network
functions the automation server may execute a predefined set of instructions that
facilitate the promotion of the slave interface to the master interface.
15 [0138] At step 508, post executing the predefined set of instructions, the
automation server may monitor the execution of the automation script and may wait
for completion of said automation script. During this period, the automation server
continuously checks whether the reselect process has been successfully executed
and all configurations have been updated.
20
[0139] At step 510, Post successful completion of the primary reselect task, the
automation server proceeds to restart the one or more network functions. The restart
of the one or more network functions is essential to apply the new configurations
and ensure that the changes made during the automation process are fully
25 implemented at the one or more network functions.
[0140] At step 512, the automation server may confirm that the primary
reselect configuration is successfully completed at the one or more network
functions, implying that the master interface is reassigned, and other network
30 operations at the one or more network functions are handled smoothly.
32
[0141] Referring to FIG. 6, an exemplary block diagram [600] of an
architecture in which features of the present disclosure may be implemented, in
accordance with exemplary implementations of the present disclosure, is shown.
5
[0142] The architecture [600] depicts the operation in the system (e.g., the
system [300]) that shows the system deciding to switch between a first interface
[604-1] (e.g., master interface), and a second interface [604-2] (e.g., slave
interface), and vice-versa, after a failure event, in which one of the first interface
10 [604-1], and the second interface [604-2] fails. Such an operation is relevant in
bonding modes like active-backup where you designate one interface as primary,
but may need to fall back to another if the primary fails. Further, the first interface
[604-1], and the second interface [604-2] may be operationally connected to a first
network switch [602-1], and a second network switch [602-2], respectively. The
15 first network switch [602-1] and the second network switch [602-2] function to
operatively select the first interface [604-1], and the second interface [604-2],
respectively.
[0143] In the exemplary implementation depicted by the architecture [600], the
20 first interface [604-1] is the primary interface. The first interface [604-1] may be an
ens1f0 interface. Further, the second interface [604-2] is the backup interface. The
second interface [604-2] may be an ens4f0 interface. The first interface [604-1], and
the second interface [604-2] are bonded in active-backup mode. In other words, the
ens1f0 interface and the ens4f0 interface are bonded in active-backup mode.
25
[0144] As long as the first interface [604-1] (i.e., ens1f0) is operational, the
system may use the first interface [604-1]. If the first interface [604-1] fails, the
system may be configured to switch to the backup second interface [604-2] (i.e.,
ens4f0).
30
33
[0145] The primary_reselect function may control how the system decides to
switch back to the first interface [604-1] after the failure event. The
primary_reselect setting may be one of always, better, and failure. Based on the
primary_reselect setting:
5
 always: If the first interface [604-] (i.e., ens1f0) comes back online, the bond
will immediately switch back to the first interface [604-1], even if the
second interface [604-2] (i.e., ens4f0) is working fine.
10  better: The bond will only switch back to the first interface [604-1] if it's in
a better state than the second interface [604-2].
 failure: The bond will stay on with the second interface [604-2] until it also
fails, at which point, the system may switch the bond back to the first
15 interface [604-1], or to another backup interface.
[0146] The present disclosure further provides a user equipment (UE). Further,
the UE comprises a memory, and a processor connected to the memory. Herein, the
processor is configured to check a connectivity between an automation server and
20 a plurality of network functions connected to the automation server. Further, the
processor is configured to receive a list of one or more network functions to be
automated. Further, the processor is configured to select the one or more network
functions from the list. Further, the processor is configured to remotely execute an
automation script at the one or more network functions. Further, the processor is
25 configured to restart the one or more network functions.
[0147] The present disclosure further provides a non-transitory computerreadable storage medium, storing instructions for managing link fluctuation in a
communication network, the storage medium comprising executable code which,
30 when executed by one or more units of a system, causes: a checking unit [302] to
34
check a connectivity between an automation server and a plurality of network
functions connected to the automation server; a transceiver unit [304] to receive a
list of one or more network functions to be automated; a selecting unit [306] to
select the one or more network functions from the list; and a processing unit [308]
5 to: remotely execute an automation script at the one or more network functions; and
restart the one or more network functions.
[0148] As is evident from the above, the present disclosure provides a
technically advanced solution for managing link fluctuation in a communication
10 network. The present solution provides enhanced stability and reliability of the
communication network by preventing rapid link flapping and controlled activation
of the master link which further leads to minimization of the network disruptions.
The implementation of "primary reselect" set to "failure" ensures a seamless and
smooth failover process as the master link doesn't regain control until the current
15 active slave is down thereby guaranteeing uninterrupted network operation. This
further reduced downtime of the network by preventing the primary slave link from
becoming active immediately after link restoration, even if it's up again. This
mitigation of the active link flapping contributed to a more stable and predictable
network environment.
20
[0149] 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
25 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.
35
We Claim:
1. A method [400] for managing link fluctuation in a communication network,
the method [400] comprising:
5 - checking, by a checking unit [302], a connectivity between an
automation server and a plurality of network functions connected to
the automation server;
- receiving, by a transceiver unit [304], a list of one or more network
functions to be automated;
10 - selecting, by a selecting unit [306], the one or more network functions
from the list;
- remotely executing, by a processing unit [308], an automation script
at the one or more network functions; and
- restarting, by the processing unit [308], the one or more network
15 functions.
2. The method [400] as claimed in claim 1, wherein the method [400] further
comprises determining, by a determining unit [310], whether execution of
the automation script is completed at the one or more network functions.
20
3. The method [400] as claimed in claim 2, wherein the one or more network
functions are restarted upon completion of execution of the automation
script at the one or more network functions.
25 4. The method [400] as claimed in claim 1, wherein the method further
comprises fetching, by fetching unit [312], a list of interfaces associated
with the one or more network functions from a storage unit [316].
5. The method [400] as claimed in claim 4, wherein the automation script is
30 executed for each interface from the list of interfaces associated with the
one or more network functions.
36
6. The method [400] as claimed in claim 4, wherein the list of interfaces
comprises a master interface and one or more slave interfaces.
5 7. The method [400] as claimed in claim 6, wherein the automation script
comprises a set of instructions to enable the one or more slave interfaces to
work as a promoted master interface in an event the master interface fails.
8. The method [400] as claimed in claim 6, wherein the automation script is
10 remotely executed by remotely enabling the one or more slave interfaces to
work as a promoted master interface in an event the master interface fails.
9. The method [400] as claimed in claim 1, wherein the link fluctuation
indicates a toggling between a connected state and a disconnected state
15 within a predefined time period.
10. The method [400] as claimed in claim 1, wherein the list of one or more
network functions to be automated is received in a user input, and wherein
the user input is received from an input unit [314].
20
11. A system [300] for managing link fluctuation in a communication network,
the system [300] comprising:
- a checking unit [302] configured to check a connectivity between an
automation server and a plurality of network functions connected to
25 the automation server;
- a transceiver unit [304] configured to receive a list of one or more
network functions to be automated;
- a selecting unit [306] configured to select the one or more network
functions from the list; and
30 - a processing unit [308] configured to:
37
- remotely execute an automation script at the one or more
network functions; and
- restart the one or more network functions.
5 12. The system [300] as claimed in claim 11, wherein the system [300]
comprises a determining unit [310] configured to determine whether
execution of the automation script is completed at the one or more network
functions.
10 13. The system [300] as claimed in claim 12, wherein the one or more network
functions are restarted upon completion of execution of the automation
script at the one or more network functions.
14. The system [300] as claimed in claim 11, wherein the system [300]
15 comprises a fetching unit [312] configured to fetch a list of servers
associated with the one or more network functions from a storage unit [316].
15. The system [300] as claimed in claim 14, wherein the automation script is
executed for each server from the list of servers associated with the one or
20 more network functions.
16. The system [300] as claimed in claim 14, wherein the list of interfaces
comprises a master interface and one or more slave interfaces.
25 17. The system [300] as claimed in claim 16, wherein the automation script
comprises a set of instructions to enable the one or more slave interfaces to
work as a promoted master interface in an event the master interface fails.
18. The system [300] as claimed in claim 16, wherein the automation script is
30 remotely executed by remotely enabling the one or more slave interfaces to
work as a promoted master interface in an event the master interface fails.
38
19. The system [300] as claimed in claim 11, wherein the link fluctuation
indicates a toggling between a connected state and a disconnected state
within a predefined time period.
5 20. The system [300] as claimed in claim 11, wherein the list of one or more
network functions to be automated is received in a user input, and wherein
the user input is received from an input unit [314].
21. A user equipment (UE) comprising:
10 - a memory; and
- a processor connected to the memory, wherein the processor is
configured to:
- check a connectivity between an automation server and a
plurality of network functions connected to the automation
15 server,
- receive a list of one or more network functions to be automated,
- select the one or more network functions from the list,
- remotely execute an automation script at the one or more network functions, and - restart the one or more network functions.