FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING A PERSISTENT
CONNECTION”
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.

METHOD AND SYSTEM FOR MANAGING A PERSISTENT
CONNECTION
FIELD OF INVENTION
[0001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for managing the persistent connection.
BACKGROUND
[0002] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 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 being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] The present disclosure solves the problem related to the connection management - when a radio frequency is acting as a client (Hyper Text Transfer Protocol (HTTP) client), it requires some connections to be initiated from its end and based on the type of connections, a decision has to be taken whether that connection has to be a persistent connection or a non-persistent connection. None of the prior known solutions provides a clear solution designed to resolve Hyper Text Transfer Protocol/ Secure (HTTP/S) connection overload at a Network Resource Function (NRF) for Notification endpoints and to monitor/audit persistent connections required by application for forwarding requests to the NRF and/or a Probe server and/or a Security Edge Protection Proxy (SEPP) and hence this particular problem is not solved by the existing technical solutions.
[0005] Thus, there exists an imperative need in the art to efficiently manage the persistent connection, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one implementation disclosed herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide a system and a method for managing a persistent connection, which bifurcate between requirement of persistent/non-persistent connections based on endpoint details and provide a solution to audit mechanism with real time monitoring of all HTTP2 connections.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description.

This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for managing a persistent connection. The method comprises receiving, by a transceiver unit at a Network Resource Function (NRF) unit via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end point configuration associated with the first end point. The method further comprises determining, by a determination unit at the NRF unit, a required connection type associated with the first connection request based on at least the first end point configuration, wherein the required connection type is at least one of the persistent connection and a non-persistent connection. The method further comprises establishing, by a connection manager at the NRF unit with the first end point, a first target connection in an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection. The method further comprises initiating, by the connection manager at the NRF unit, a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured for a pre¬defined time. The method further comprises detecting, by a detection unit at the NRF unit, a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection unavailable status. The method further comprises re-establishing, by the connection manager at the NRF unit with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.
[0010] In an exemplary aspect of the present disclosure, the method further comprises detecting, by the detection unit at the NRF unit, a target re-connection status associated with re-establishing of the first target connection from the NRF unit with the first end point, wherein the target re-connection status is one of a target

re-connection successful status and a target re-connection unsuccessful status, and wherein the target re-connection unsuccessful status at least comprises a target re-connection unsuccessful reason. The method further comprises initiating, by the connection manager at the NRF unit via a northbound interface (NBI), an alarm based on detecting the target re-connection unsuccessful status, wherein the alarm comprises at least the first end point configuration and the target re-connection unsuccessful reason.
[0011] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit at the NRF unit via the interface, a second connection request associated with a second end point based on the alarm, wherein the second connection request at least comprises a second end point configuration associated with the second end point. The method further comprises successfully establishing, by the connection manager at the NRF unit with the second end point, a second target connection based on the second connection request. The method further comprises automatically clearing, by the connection manager at the NRF unit via the NBI, the alarm based on successfully establishing the second target connection based on the second connection request.
[0012] In an exemplary aspect of the present disclosure, the required connection type is determined at the NRF unit based on a prestored connection data stack associated with the NRF unit, wherein the prestored connection data stack is associated with at least the first end point configuration.
[0013] In an exemplary aspect of the present disclosure, the connection monitoring timer associated with the first target connection is at least one of a predefined periodic timer and a dynamically configurable timer.
[0014] In an exemplary aspect of the present disclosure, the second target connection from the NRF unit with the second end point is at least one of the persistent connection and the non-persistent connection.

[0015] In an exemplary aspect of the present disclosure, the method further comprises establishing, by the connection manager, a non-persistent target connection in an event the required connection type is the non-persistent connection. The method further comprises detecting, by the detection unit, a successful transaction status associated with the non-persistent connection. The method further comprises terminating, by the connection manager, the non-persistent connection based on the detection of the successful transaction status.
[0016] Another aspect of the present disclosure may relate to a system for managing a persistent connection. The system comprises a Network Resource Function (NRF) unit. The NRF unit further comprising a transceiver unit, a determination unit, a connection manager, and a detection unit connected to each other. The transceiver unit is configured to receive, via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end point configuration associated with the first end point. Further, the determination unit is configured to determine a required connection type associated with the first connection request based on at least the first end point configuration, wherein the required connection type is at least one of the persistent connection and a non-persistent connection. Further, the connection manager is configured to establish with the first end point, a first target connection in an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection. Further, the connection manager is configured to initiate a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured for a pre-defined time. Further, the detection unit is configured to detect, a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection unavailable status. Further, the connection manager is configured to re-establish with the first end point, the first target connection based

on detecting the target connection unavailable status associated with the first target connection.
[0017] Another aspect of the present disclosure may relate to a non-transitory computer readable medium storing one or more instructions, the one or more instructions comprising executable code, which when executed by one or more units of a system, causes, the one or more units of the system to perform certain functions. The one or more instructions when executed causes a transceiver unit of the system to receive, via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end point configuration associated with the first end point. The one or more instructions when executed further causes a determination unit of the system to determine a required connection type associated with the first connection request based on at least the first end point configuration, wherein the required connection type is at least one of the persistent connection and a non-persistent connection. The one or more instructions when executed further causes a connection manager of the system to establish with the first end point, a first target connection in an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection. The one or more instructions when executed further causes initiate a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured for a pre¬defined time. The one or more instructions when executed further causes a detection unit of the system to detect, a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection unavailable status. The one or more instructions when executed further causes the connection manager of the system to re-establish with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.

BRIEF DESCRIPTION OF DRAWINGS
[0018] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary implementations of the disclosed
5 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. Some drawings may indicate the components using block
diagrams and may not represent the internal circuitry of each component. It will be
10 appreciated by those skilled in the art that disclosure of such drawings includes
disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0019] FIG. 1 illustrates an exemplary block diagram representation of 5th
15 generation core (5GC) network architecture.
[0020] FIG. 2 illustrates an exemplary block diagram of a system for managing a persistent connection, in accordance with exemplary implementations of the present disclosure. 20
[0021] FIG. 3 illustrates an exemplary method flow diagram indicating the process for managing a persistent connection, in accordance with exemplary implementations of the present disclosure.
25 [0022] FIG. 4 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0023] The foregoing shall be more apparent from the following more detailed
30 description of the disclosure.
8

DETAILED DESCRIPTION
[0024] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
5 implementations of the present disclosure. It will be apparent, however, that
implementations of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the
10 problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Example implementations of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
15
[0025] The ensuing description provides exemplary implementations only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary implementations will provide those skilled in the art with an enabling description for implementing an exemplary
20 implementation. 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.
[0026] It should be noted that the terms "mobile device", "user equipment", "user
25 device", “communication device”, “device” and similar terms are used
interchangeably for the purpose of describing the disclosure. These terms are not
intended to limit the scope of the disclosure or imply any specific functionality or
limitations on the described implementations. The use of these terms is solely for
convenience and clarity of description. The disclosure is not limited to any
30 particular type of device or equipment, and it should be understood that other
9

equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein.
[0027] Specific details are given in the following description to provide a thorough
5 understanding of the implementations. However, it will be understood by one of
ordinary skill in the art that the implementations may be practiced without these
specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the implementations in unnecessary detail. In other instances, well-known
10 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the implementations.
[0028] Also, it is noted that individual implementations may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
15 structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can 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
[0029] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
25 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner
30 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
10

[0030] As used herein, an “electronic device”, or “portable electronic device”, or
“user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical and computing device. The user
5 device is capable of receiving and/or transmitting one or parameters, performing
function/s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including
10 but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
Energy, Near Field Communication, Z-Wave, Wireless Fidelity (Wi-Fi), Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant,
15 tablet computer, mainframe computer, or any other device as may be obvious to a
person skilled in the art for implementation of the features of the present disclosure.
[0031] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for
20 processing instructions. The 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 DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
25 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 is a hardware processor.
[0032] All modules, units, components used herein, unless explicitly excluded
30 herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor, a
11

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. 5
[0033] 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.
10
[0034] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic
15 advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
20 [0035] Radio Access Technology (RAT) refers to the technology used by mobile
devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define
25 the frequency bands, modulation techniques, and other parameters used for
transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network
30 infrastructure, the available spectrum, and the mobile device's/device's capabilities.
Mobile devices often support multiple RATs, allowing them to connect to different
12

types of networks and provide optimal performance based on the available network resources.
[0036] As discussed in the background section, the current known solutions for
5 connection management and auditing for persistent Hyper Text Transfer Protocol
Secure (HTTP/S) connections have several shortcomings such as resolving a
HTTP/S connection overload at a Network Resource Function (NRF) for
Notification endpoints and to monitor/audit persistent connections required by
application for forwarding requests to a the NRF and/or a Probe server and/or a
10 Security Edge Protection Proxy (SEPP).
[0037] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a solution for managing Network Resource Function (NRF), wherein the client bifurcates between
15 requirement of a persistent and a non-persistent connection based on endpoint
details. The non-persistent connection is teared down to free system resources and audit the persistent connections in interval of configurable timer. The present solution restores the persistent connections, once found not available in audit. If restoring is unsuccessful, then it will raise corresponding alarm at a North-Bound
20 Interface (NBI) for manual intervention. The Alarms maybe auto cleared once
connection is re-established with remote host.
[0038] Hereinafter, exemplary implementations of the present disclosure will be described with reference to the accompanying drawings.
25
[0039] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary 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
30 (RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
13

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],
5 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 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.
10 [0040] The User Equipment (UE) [102] interfaces with the network via the Radio
Access Network (RAN) [104]; the Access and Mobility Management Function (AMF) [106] manages connectivity and mobility, while the Session Management Function (SMF) [108] administers session control; the service communication proxy (SCP) [110] routes and manages communication between network services,
15 enhancing efficiency and security, and the Authentication Server Function (AUSF)
[112] handles user authentication; the Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] for integrating the 5G core network with existing 4G LTE networks i.e., to enable Non-Standalone (NSA) 5G deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function
20 (NEF) [118], and Network Repository Function (NRF) [120] enable network
customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function (PCF) [122] develops operational policies, and the Unified Data Management (UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application
25 interaction, the User Plane Function (UPF) [128] processes and forwards user data,
and the Data Network (DN) [130] connects to external internet resources; collectively, these components are designed to enhance mobile broadband, ensure low-latency communication, and support massive machine-type communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
30
14

[0041] Radio Access Network (RAN) [104] is the part of a mobile
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).
It consists of radio base stations and the radio access technologies that enable
5 wireless communication.
[0042] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
registration, connection, and reachability. It also handles mobility management
10 procedures like handovers and paging.
[0043] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
and releasing sessions. It coordinates with the User Plane Function (UPF) for data
15 forwarding and handles IP address allocation and QoS enforcement.
[0044] Service Communication Proxy (SCP) [110] is a network function in the 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-
20 based interfaces.
[0045] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
25
[0046] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
30
15

[0047] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
5 [0048] 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.
[0049] Network Repository Function (NRF) [120] is a network function that acts
10 as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0050] Policy Control Function (PCF) [122] is a network function responsible for
policy control decisions, such as QoS, charging, and access control, based on
15 subscriber information and network policies.
[0051] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 20
[0052] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
25 [0053] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0054] Data Network (DN) [130] refers to a network that provides data services to
30 user equipment (UE) in a telecommunications system. The data services may
include but are not limited to Internet services, private data network related services.
16

[0055] The 5GC network architecture also comprises a plurality of interfaces for
connecting the network functions with a network entity for performing the network
functions. The NSSF [116] is connected with the network entity via the interface
5 denoted as (Nnssf) interface. The NEF [118] is connected with the network entity via
the interface denoted as (Nnef) interface. The NRF [120] is connected with the network entity via the interface denoted as (Nnrf) interface. The PCF [122] is connected with the network entity via the interface denoted as (Npcf) interface. The UDM [124] is connected with the network entity via the interface denoted as (Nudm)
10 interface. The AF [126] is connected with the network entity via the interface
denoted as (Naf) interface. The NSSAAF [114] is connected with the network entity via the interface denoted as (Nnssaaf) interface. The AUSF [112] is connected with the network entity via the interface denoted as (Nausf) interface. The AMF [106] is connected with the network entity via the interface denoted as (Namf) interface. The
15 SMF [108] is connected with the network entity via the interface denoted as (Nsmf)
interface. The SMF [108] is connected with the UPF [128] via the interface denoted as (N4) interface. The UPF [128] is connected with the RAN [104] via the interface denoted as (N3) interface. The UPF [128] is connected with the DN [130] via the interface denoted as (N6) interface. The RAN [104] is connected with the AMF
20 [106] via the interface denoted as (N2). The AMF [106] is connected with the RAN
[104] via the interface denoted as (N1). The UPF [128] is connected with other UPF [128] via the interface denoted as (N9). The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication channel between one or more functions or modules for
25 enabling exchange of data or information between such functions or modules, and
network entities.
[0056] Referring to FIG. 2, an exemplary block diagram of a system [200] for
managing a persistent connection, is shown, in accordance with the exemplary
30 implementations of the present disclosure. The system [200] comprises a Network
Resource Function (NRF) unit [202], the NRF unit [202] of the system [200] further
17

comprises at least one transceiver unit [204], at least one determination unit [206],
at least one connection manager [208], and at least one detection unit [210]. Also,
all of the components/ units of the system [200] are assumed to be connected to
each other unless otherwise indicated below. Also, in FIG. 2 only a few units are
5 shown, however, the system [200] may comprise multiple such units or the system
[200] may comprise any such numbers of said units, as required to implement the
features of the present disclosure. The system [200] may be independent system in
communication with a user device (may also referred herein as a UE). In another
implementation, the system [200] may reside in a server or a network entity. In yet
10 another implementation, the system [200] may reside partly in the server/ network
entity.
[0057] The persistent connection may refer to a network connection between different network elements such as a user device(s) and a network server(s), which
15 remains open for multiple requests and responses instead of being closed after each
individual transaction. The transceiver unit [204] may be a device capable of reception and transmission of data and/or signals. The determination unit [206] may be a processor or a processing unit configured to perform one or more operation to implement the solution as disclosed by the present disclosure. The connection
20 manager [208] may be a processor or a processing unit configured to perform one
or more operation to implement the solution as disclosed by the present disclosure. The detection unit [210] may be a processor or a processing unit configured to perform one or more operation to implement the solution as disclosed by the present disclosure.
25
[0058] The system [200] is configured for managing the persistent connection, with the help of the interconnection between the components/units of the system [200].
[0059] In order to manage the persistent connection, the transceiver unit [204] of
30 the system [200] is configured to receive via an interface, a first connection request
associated with a first end point, wherein the first connection request at least
18

comprises a first end point configuration associated with the first end point. The
first connection request may be request for connecting with the NRF unit [202], and
may be sent by the first end point. The first end point may be a server or a user
device and/or a network node. The first endpoint configuration may be a
5 configuration associated with the first end point. The interface may refer to the
connection between the NRF unit [202] and the first end point.
[0060] Further, the determination unit [206] of the system [200] is configured to determine a required connection type associated with the first connection request
10 based on at least the first end point configuration, wherein the required connection
type is at least one of the persistent connection and a non-persistent connection. The required connection type associated with the first connection request may refer to the type of connection which is required by the NRF unit [202]. The required connection type may be the persistent connection or the non-persistent connection.
15 The non-persistent connection may be the type of connection which is not persistent
connection i.e., a network connection between different network elements such as user devices and network servers, which closes after each individual network transaction or a bunch of network transactions or network requests or network responses instead of remaining open after each individual network transaction.
20
[0061] The present disclosure further discloses that the required connection type is determined at the NRF unit [202] based on a prestored connection data stack associated with the NRF unit [202], wherein the prestored connection data stack is associated with at least the first end point configuration. The prestored connection
25 data stack is a predetermined configuration of specific end points for determination
of the required connection type. The prestored connection data stack uses the predefined configuration at NRF unit [202] for determining whether the required connection type is persistent connection or non-persistent connection with end point.
30
19

[0062] The present disclosure further discloses that the connection manager [208]
is further configured to establish a non-persistent target connection in an event the
required connection type is the non-persistent connection. The detection unit [210]
is further configured to detect a successful transaction status associated with the
5 non-persistent connection. The connection manager [208] is configured to
terminate the non-persistent connection based on the detection of the successful
transaction status. The non-persistent target connection may refer to the non-
persistent connection between the NRF unit [202] and the first end point in an event
the required connection type is the non-persistent connection, i.e., the situation
10 where the required connection type is the non-persistent connection. The successful
transaction status may refer to a successful completion of an ongoing transaction between the NRF unit [202] and the first end point.
[0063] Further, the connection manager [208] of the system [200] is configured to
15 establish with the first end point, a first target connection in an event the required
connection type is the persistent connection, wherein the first target connection is
at least the persistent connection. The first target connection may refer to a required
connection type between the NRF unit [202] and the first end point. In the event the
required connection type is the persistent connection it may refer to the instance
20 when the required connection type between the NRF unit [202] and the first end is
determined as the persistent connection.
[0064] Further, the connection manager [208] of the system [200] is configured to initiate, at the NRF unit [202], a connection monitoring timer associated with the
25 first target connection, wherein the connection monitoring timer is configured for a
pre-defined time. The connection monitoring timer may be a timer which monitors the first target connection and the second target connection for detecting a connection status associated with the first target connection and the connection monitoring timer may run for the pre-defined time. The pre-defined time may refer
30 to the time period which may be specifically set based on a need(s) and
requirements of a network service provider of the NRF unit [202].
20

[0065] In an implementation of the present disclosure, the connection monitoring
timer associated with the first target connection is at least one of a predefined
periodic timer and a dynamically configurable timer. The predefined periodic timer
5 may be a timer which may be pre-fixed with a timer, and the dynamically
configurable timer may be a timer which may be dynamically changed based on the needs and requirements of the network service provider.
[0066] Further, the detection unit [210] of the system [200] is configured to detect
10 a target connection status associated with the first target connection via monitoring
periodically the first target connection based on the connection monitoring timer,
wherein the target connection status is one of a target connection available status
and a target connection unavailable status. The target connection status may refer
to the availability status of the first target connection. The target connection
15 available status may refer to an event that the first target connection is now available
for connecting to the NRF unit [202]. The target connection unavailable status may refer to an event that the first target connection is not available for connecting to the NRF unit [202].
20 [0067] Further, the connection manager [208] of the system [200] is configured to
re-establish, from the NRF unit [202] with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.
25 [0068] The present disclosure further discloses that the detection unit [210] of the
system [200] is further configured to detect a target re-connection status associated with re-establishing of the first target connection from the NRF unit [202] with the first end point, wherein the target re-connection status is one of a target re-connection successful status and a target re-connection unsuccessful status, and
30 wherein the target re-connection unsuccessful status at least comprises a target re-
connection unsuccessful reason. The target re-connection status may refer to the
21

status of the first target connection after the re-establishment of the first target
connection with the first end point based on detecting the target connection
unavailable status associated with the first target connection. The target re-
connection successful status may refer to the event where the re-establishment of
5 the first target connection with the first end point based on detecting the target
connection unavailable status associated with the first target connection is
successful. The target re-connection unsuccessful status may refer to the event
where the re-establishment of the first target connection with the first end point
based on detecting the target connection unavailable status associated with the first
10 target connection is not successful. The target re-connection unsuccessful reason
may refer to the reason for the target re-connection unsuccessful status.
[0069] The present disclosure further discloses that the connection manager unit [208] of the system [200] is configured to initiate, via a northbound interface (NBI),
15 an alarm based on detecting the target re-connection unsuccessful status, wherein
the alarm comprises at least the first end point configuration and the target re-connection unsuccessful reason. The alarm may refer to an indication regarding the target re-connection unsuccessful status of the first target connection. The alarm helps for escalating the situation and receive a new connection request (also referred
20 as second connection request or a subsequent connection request) containing
information of the second end point when available with it. The Northbound Interface (NBI) is a network interface used for communicating via the interface between the NRF unit [202] and the external management systems such as alarms management systems, counter management systems, etc.
25
[0070] The present disclosure further discloses that the transceiver unit [204] of the system [200] is configured to receive via the interface, a second connection request associated with a second end point based on the alarm, wherein the second connection request at least comprises a second end point configuration associated
30 with the second end point. The second connection request may refer to a request by
the second end point for connecting with the NRF unit [202]. The second end point
22

may be a server or a user device or a network node. The second endpoint configuration may be a configuration associated with the second end point.
[0071] Further, the connection manager [208] of the system [200] is configured to
5 successfully establish, with the second end point, a second target connection based
on the second connection request. The present disclosure further discloses that the
second target connection from the NRF unit [202] with the second end point is at
least one of the persistent connection and the non-persistent connection. The second
target connection may refer to the connection between the NRF unit [202] and the
10 second end point based on the second connection request.
[0072] The present disclosure further discloses that, the connection manager [208]
of the system [200] is configured to automatically clear via the NBI, the alarm based
on successfully establishing the second target connection based on the second
15 connection request.
[0073] The present disclosure further discloses that the NRF unit [202] keeps
checking for the reachability with the first end point, and when the first end points
are re-established with the NRF unit [202], the connection with the second end point
20 may be terminated. This helps in graceful tearing down of the second target
connection established with the second end point, once connections with the first end point are re-established with the NRF unit [202] as the NRF unit [202] keeps checking for reachability with the first end point as well.
25 [0074] Referring to FIG. 3, an exemplary method flow diagram [300], for
managing the persistent connection, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. As shown in FIG. 3, the method [300] starts at step [302]. The persistent connection may refer to a network
30 connection between different network elements such as user device(s) and network
server(s), which remains open for multiple requests and responses instead of being
23

closed after each individual transaction. The NRF unit [202] may be a unit/device
capable of performing a Network Resource Function. The transceiver unit [204]
may be a device capable of reception and transmission of data and/or signals. The
determination unit [206] may be a processor or a processing unit. The connection
5 manager [208] may be a processor or a processing unit. detection unit [210] may be
a processor or a processing unit.
[0075] At step [304], the method [300] comprises receiving, by the transceiver unit [204], at the NRF unit [202] via an interface, a first connection request associated
10 with a first end point, wherein the first connection request at least comprises a first
end point configuration associated with the first end point. The first connection request may be request for connecting with the NRF unit [202], and may be sent by the first end point. The first end point may be a server or a user/device and/or a network node. The first endpoint configuration may be a configuration associated
15 with the first end point. The interface may refer to the connection between the NRF
unit [202] and the first end point.
[0076] At step [306], the method [300] comprises determining, by the determination unit [206] at the NRF unit [202], a required connection type
20 associated with the first connection request based on at least the first end point
configuration, wherein the required connection type is at least one of a persistent connection and a non-persistent connection. The required connection type associated with the first connection request may refer to the type of connection which is required by the NRF unit [202]. The required connection type may be the
25 persistent connection or the non-persistent connection. The non-persistent
connection may be the type of connection which is not persistent connection i.e., a network connection between different network elements such as user devices and network servers, which closes after each individual network transaction or a bunch of network transactions or network requests/responses instead of remaining open
30 after each individual transaction.
24

[0077] The present disclosure further discloses that the required connection type is
determined at the NRF unit [202] based on a prestored connection data stack
associated with the NRF unit [202], wherein the prestored connection data stack is
associated with at least the first end point configuration. The prestored connection
5 data stack is a predetermined configuration of specific end points for determination
of the required connection type. The prestored connection data stack uses the predefined configuration at NRF unit [202] for determining whether the required connection type is persistent connection or non-persistent connection with end point.
10
[0078] The present disclosure further discloses establishing, by the connection manager [208], a non-persistent target connection in an event the required connection type is the non-persistent connection. The present disclosure further discloses, detecting, by the detection unit [210], a successful transaction status
15 associated with the non-persistent connection. The present disclosure further
discloses terminating, by the connection manager [208], the non-persistent connection based on the detection of the successful transaction status. The non-persistent target connection may refer to the non-persistent connection between the NRF unit [202] and the first end point, in an event the required connection type is
20 the non-persistent connection, i.e., the situation where the required connection type
is the non-persistent connection. The successful transaction status may refer to a successful completion of an ongoing transaction between the NRF unit [202] and the first end point.
25 [0079] Next, at step [308], the method [300] comprises establishing, by the
connection manager [208] at the NRF unit [202] with the first end point, a first target connection based on the required connection type, wherein the first target connection is at least the persistent connection. The first target connection may refer to the connection between the NRF unit [202] and the first end point. The event the
30 required connection type is the persistent connection it may refer to the instance
when the required connection type is determined to be a persistent connection.
25

[0080] Next, at step [310], the method [300] further comprises initiating by the
connection manager [208] at the NRF unit [202], a connection monitoring timer
associated with the first target connection, wherein the connection monitoring timer
5 is configured for a pre-defined time. The connection monitoring timer may be a
timer which monitors the first target connection and the second target connection
for detecting a connection status associated with the first target connection and the
connection monitoring timer may run for a pre-defined time. The pre-defined time
may refer to the time period which may be specifically set based on the needs and
10 requirements of the network service provider of the NRF unit [202].
[0081] In an implementation of the present disclosure, the connection monitoring
timer associated with the first target connection is at least one of a predefined
periodic timer and a dynamically configurable timer. The predefined periodic timer
15 may be a timer which may be pre-fixed with a timer, and the dynamically
configurable timer may be a timer which may be dynamically changed based on the needs and requirements of the network service provider.
[0082] Next, at step [312], the method [300] further comprises detecting, by the
20 detection unit [210] at the NRF unit [202], a target connection status associated with
the first target connection via monitoring periodically the first target connection
based on the connection monitoring timer, wherein the target connection status is
one of a target connection available status and a target connection unavailable
status. The target connection status may refer to the availability status of the first
25 target connection. The target connection available status may refer to an event that
the first target connection is now available for connecting to the NRF unit [202]. The target connection unavailable status may refer to an event that the first target connection is not available for connecting to the NRF unit [202].
30 [0083] Next, at step [314], the method [300] comprises re-establishing, by the
connection manager [208] at the NRF unit [202] with the first end point, the first
26

target connection based on detecting the target connection unavailable status associated with the first target connection.
[0084] The present disclosure further discloses detecting, by the detection unit
5 [210] at the NRF unit [202], a target re-connection status associated with re-
establishing of the first target connection from the NRF unit [202] with the first end point, wherein the target re-connection status is one of a target re-connection successful status and a target re-connection unsuccessful status, and wherein the target re-connection unsuccessful status at least comprises a target re-connection
10 unsuccessful reason. The present disclosure further discloses that the target re-
connection status may refer to the status of the first target connection after the re-establishment of the first target connection with the first end point based on detecting the target connection unavailable status associated with the first target connection. The target re-connection successful status may refer to the event where
15 the re-establishment of the first target connection with the first end point based on
detecting the target connection unavailable status associated with the first target connection is now successful. The target re-connection unsuccessful status may refer to the event where the re-establishment of the first target connection with the first end point based on detecting the target connection unavailable status associated
20 with the first target connection is not successful. The target re-connection
unsuccessful reason may refer to the reason for the target re-connection unsuccessful status.
[0085] The present disclosure further discloses initiating, by the connection
25 manager [208] at the NRF unit [202] via a northbound interface (NBI), an alarm
based on detecting the target re-connection unsuccessful status, wherein the alarm
comprises at least the first end point configuration and the target re-connection
unsuccessful reason. The alarm may refer to an indication regarding the target re-
connection unsuccessful status of the first target connection. The alarm helps for
30 escalating the situation and receive a new connection request (also referred as
second connection request or a subsequent connection request) containing
27

information of the second end point when available with it. The Northbound Interface (NBI) is a network interface used for communicating via the interface between the NRF unit [202] and the external management systems such as alarms management systems, counter management systems, etc. 5
[0086] The present disclosure further discloses receiving, by the transceiver unit
[204] at the NRF unit [202] via the interface, a second connection request associated
with a second end point based on the alarm, wherein the second connection request
at least comprises a second end point configuration associated with the second end
10 point. The second connection request may refer to a request by the second end point
for connecting with the NRF unit [202]. The second end point may be server or a user/device or a network node. The second endpoint configuration may be a configuration associated with the second end point.
15 [0087] The present disclosure further discloses successfully establishing, by the
connection manager [208] at the NRF unit [202] with the second end point, a second target connection based on the second connection request. The present disclosure further discloses that the second target connection from the NRF unit [202] with the second end point is at least one of the persistent connection and the non-persistent
20 connection. The second target connection may refer to the connection between the
NRF unit [202] and the second end point based on the second connection request.
[0088] The present disclosure further discloses automatically clearing, by the
connection manager [208] at the NRF unit [202] via the NBI, the alarm based on
25 successfully establishing the second target connection based on the second
connection request.
[0089] The present disclosure further discloses that the NRF unit [202] keeps
checking for the reachability with the first end point, and when the first end points
30 are re-established with the NRF unit [202], the connection with the second end point
may be terminated. This helps in graceful tearing down of the second target
28

connection established with the second end point, once connections with the first end point are re-established with the NRF unit [202] as the NRF unit [202] keeps checking for reachability with the first end point as well.
5 [0090] Thereafter, the method terminates at step (320).
[0091] FIG. 4 illustrates an exemplary block diagram of a computing device [400] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an
10 implementation, the computing device [400] may also implement a method [300]
for managing a persistent connection by utilising the system [200]. In another implementation, the computing device [400] itself implements the method [300] for managing the persistent connection using one or more units configured within the computing device [400], wherein said one or more units are capable of
15 implementing the features as disclosed in the present disclosure.
[0092] The computing device [400] may include a bus [402] or other communication mechanism for communicating information, and a hardware processor [404] coupled with bus [402] for processing information. The hardware
20 processor [404] may be, for example, a general-purpose microprocessor. The
computing device [400] may also include a main memory [406], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [402] for storing information and instructions to be executed by the processor [404]. The main memory [406] also may be used for storing temporary variables or other
25 intermediate information during execution of the instructions to be executed by the
processor [404]. Such instructions, when stored in non-transitory storage media accessible to the processor [404], render the computing device [400] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [400] further includes a read only memory
30 (ROM) [408] or other static storage device coupled to the bus [402] for storing static
information and instructions for the processor [404].
29

[0093] A storage device [410], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [402] for storing information and
instructions. The computing device [400] may be coupled via the bus [402] to a
5 display [412], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [414], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [402] for communicating information and command selections to the processor
10 [404]. Another type of user input device may be a cursor controller [416], such as a
mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [404], and for controlling cursor movement on the display [412]. 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
15 the device to specify positions in a plane.
[0094] The computing device [400] 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 [400] causes
20 or programs the computing device [400] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [400] in response to the processor [404] executing one or more sequences of one or more instructions contained in the main memory [406]. Such instructions may be read into the main memory [406] from another storage medium,
25 such as the storage device [410]. Execution of the sequences of instructions
contained in the main memory [406] causes the processor [404] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
30
30

[0095] The computing device [400] also may include a communication interface
[418] coupled to the bus [402]. The communication interface [418] provides a two-
way data communication coupling to a network link [420] that is connected to a
local network [422]. For example, the communication interface [418] may be an
5 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 [418] 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
10 implementation, the communication interface [418] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0096] The computing device [400] can send messages and receive data, including
15 program code, through the network(s), the network link [420] and the
communication interface [418]. In the Internet example, a server [430] might
transmit a requested code for an application program through the Internet [428], the
ISP [426], the host [424], the local network [422] and the communication interface
[418]. The received code may be executed by the processor [404] as it is received,
20 and/or stored in the storage device [410], or other non-volatile storage for later
execution.
[0097] The present disclosure further discloses a non-transitory computer readable medium storing one or more instructions, the one or more instructions comprising
25 executable code, which when executed by one or more units of a system [200],
causes, the one or more units of the system [200] to perform certain functions. The one or more instructions when executed causes a transceiver unit [204] of the system [200] to receive, via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end
30 point configuration associated with the first end point. The one or more instructions
when executed further causes a determination unit [206] of the system [200] to
31

determine a required connection type associated with the first connection request
based on at least the first end point configuration, wherein the required connection
type is at least one of the persistent connection and a non-persistent connection. The
one or more instructions when executed further causes a connection manager [208]
5 of the system [200] to establish with the first end point, a first target connection in
an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection. The one or more instructions when executed further causes initiate a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured
10 for a pre-defined time. The one or more instructions when executed further causes
a detection unit [210] of the system [200] to detect, a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection
15 unavailable status. The one or more instructions when executed further causes the
connection manager [208] of the system [200] to re-establish with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.
20 [0098] As is evident from the above, the present disclosure provides a technically
advanced solution for connection management and auditing for a persistent Hypertext Transfer Protocol secure (HTTP/S) connection. The present disclosure introduces a connection management and an auditing system for the persistent HTTP/S connection initiated by a Network Resource Function (NRF) client. Based
25 on configurable parameters, the NRF establishes “n” number of connections with
the server where persistent connections are required. The NRF stack conducts periodic auditing of these connection i.e., the persistent HTTP/S connection and sends notifications or generates alarms to an application via a user interface when a status of a connection is detected as down. The system then attempts to recreate
30 the connection with same server endpoint to restore the connection. While sending
a subscription Notification data, the NRF instantiates temporary connection with
32

Notification Endpoint which may be terminated automatically after “n” seconds which is configurable at the application.
[0099] While considerable emphasis has been placed herein on the disclosed
5 implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
of the present disclosure will be apparent to those skilled in the art, whereby it is to
be understood that the foregoing descriptive matter to be implemented is illustrative
10 and non-limiting.
[0100] 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
15 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
20 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
33

We Claim:
1. A method for managing a persistent connection, the method comprising:
• receiving, by a transceiver unit [204], at a Network Resource Function (NRF) unit [202] via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end point configuration associated with the first end point;
• determining, by a determination unit [206] at the NRF unit [202], a required connection type associated with the first connection request based on at least the first end point configuration, wherein the required connection type is at least one of the persistent connection and a non-persistent connection;
• establishing, by a connection manager [208] at the NRF unit [202] with the first end point, a first target connection in an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection;
• initiating, by the connection manager [208] at the NRF unit [202], a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured for a pre-defined time;
• detecting, by a detection unit [210] at the NRF unit [202], a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection unavailable status; and
• re-establishing, by the connection manager [208] at the NRF unit [202] with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.
2. The method as claimed in claim 1 further comprising:

• detecting, by the detection unit [210] at the NRF unit [202], a target re-connection status associated with re-establishing of the first target connection from the NRF unit [202] with the first end point, wherein the target re-connection status is one of a target re-connection successful status and a target re-connection unsuccessful status, and wherein the target re-connection unsuccessful status at least comprises a target re-connection unsuccessful reason; and
• initiating, by the connection manager [208] at the NRF unit [202] via a northbound interface (NBI), an alarm based on detecting the target re-connection unsuccessful status, wherein the alarm comprises at least the first end point configuration and the target re-connection unsuccessful reason.
3. The method as claimed in claim 2 further comprising:
• receiving, by the transceiver unit [204] at the NRF unit [202] via the interface, a second connection request associated with a second end point based on the alarm, wherein the second connection request at least comprises a second end point configuration associated with the second end point;
• successfully establishing, by the connection manager [208] at the NRF unit [202] with the second end point, a second target connection based on the second connection request; and
• automatically clearing, by the connection manager [208] at the NRF unit [202] via the NBI, the alarm based on successfully establishing the second target connection based on the second connection request.
4. The method as claimed in claim 1, wherein the required connection type is
determined at the NRF unit [202] based on a prestored connection data stack
associated with the NRF unit [202], wherein the prestored connection data
stack is associated with at least the first end point configuration.

5. The method as claimed in claim 1, wherein the connection monitoring timer associated with the first target connection is at least one of a predefined periodic timer and a dynamically configurable timer.
6. The method as claimed in claim 3, wherein the second target connection from the NRF unit [202] with the second end point is at least one of the persistent connection and the non-persistent connection.
7. The method as claimed in claim 1 further comprising:

- establishing, by the connection manager [208], a non-persistent target connection in an event the required connection type is the non-persistent connection;
- detecting, by the detection unit [210], a successful transaction status associated with the non-persistent connection; and
- terminating, by the connection manager [208], the non-persistent connection based on the detection of the successful transaction status.
8. A system [200] for managing a persistent connection, the system [200]
comprising a Network Resource Function (NRF) unit [202], the Network
Resource Function (NRF) unit [202] further comprising:
- a transceiver unit [204] configured to receive, via an interface, a first connection request associated with a first end point, wherein the first connection request at least comprises a first end point configuration associated with the first end point;
- a determination unit [206] connected at least to the transceiver unit [204], the determination unit [206] configured to determine a required connection type associated with the first connection request based on at least the first end point configuration, wherein the required connection type is at least one of the persistent connection and a non-persistent connection;
- a connection manager [208] connected at least to the determination unit [206], the connection manager [208] configured to:

• establish with the first end point, a first target connection in an event the required connection type is the persistent connection, wherein the first target connection is at least the persistent connection, and
• initiate a connection monitoring timer associated with the first target connection, wherein the connection monitoring timer is configured for a pre-defined time; and
- a detection unit [210] connected to at least the connection manager [208], the detection unit [210] configured to detect, a target connection status associated with the first target connection via monitoring periodically the first target connection based on the connection monitoring timer, wherein the target connection status is one of a target connection available status and a target connection unavailable status;
the connection manager [208] is further configured to re-establish with the first end point, the first target connection based on detecting the target connection unavailable status associated with the first target connection.
9. The system [200] as claimed in claim 8, wherein
• the detection unit [210] is further configured to detect a target re-connection status associated with re-establishing of the first target connection from the NRF unit [202] with the first end point, wherein the target re-connection status is one of a target re-connection successful status and a target re-connection unsuccessful status, and wherein the target re-connection unsuccessful status at least comprises a target re-connection unsuccessful reason; and
• the connection manager [208] is further configured to initiate, via a northbound interface (NBI), an alarm based on detecting the target re-connection unsuccessful status, wherein the alarm comprises at least the first end point configuration and the target re-connection unsuccessful reason.
10. The system [200] as claimed in claim 9, further comprising:

• the transceiver unit [204] is further configured to receive a second connection request associated with a second end point based on the alarm, wherein the second connection request at least comprises a second end point configuration associated with the second end point; and
• the connection manager [208] is further configured to:
o successfully establish with the second end point, a second target connection based on the second connection request, and
o automatically clear via the NBI, the alarm based on successfully establishing the second target connection based on the second connection request.
11. The system [200] as claimed in claim 8, wherein the required connection type is determined at the NRF unit [202] based on a prestored connection data stack associated with the NRF unit [202], wherein the prestored connection data stack is associated with at least the first end point configuration.
12. The system [200] as claimed in claim 8, wherein the connection monitoring timer associated with the first target connection is at least one of a predefined periodic timer and a dynamically configurable timer.
13. The system [200] as claimed in claim 10, wherein the second target connection from the NRF unit [202] with the second end point is at least one of the persistent connection and the non-persistent connection.
14. The system [200] as claimed in claim 8 wherein:

- the connection manager [208] is further configured to establish a non-persistent target connection in an event the required connection type is the non-persistent connection;
- the detection unit [210] is further configured to detect a successful transaction status associated with the non-persistent connection; and

- the connection manager [208] is further configured to terminate the non-persistent connection based on the detection of the successful transaction status.