Search

EP-4740680-A1 - METHOD AND SYSTEM FOR MANAGING A PERSISTENT CONNECTION

EP4740680A1EP 4740680 A1EP4740680 A1EP 4740680A1EP-4740680-A1

Abstract

The present disclosure relates to methods and systems for managing a persistent connection The disclosure encompasses: receiving a first connection request comprising a first end point configuration; determining a required connection type based on the first end point configuration, wherein the required connection type is at least one of a persistent connection and a non-persistent connection; establishing with the first end point a first target connection if the required connection type is a persistent connection, wherein the first target connection is the persistent connection; initiating a connection monitoring timer configured for a pre-defined time; detecting a target connection status 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; re-establishing with the first end point, the first target connection based on detecting the target connection unavailable status.

Inventors

  • Shetty, Mukta
  • BHATNAGAR, AAYUSH
  • SINHA, ANURAG
  • AGARWAL, Ayush
  • GUPTA, ADITYA
  • Khamesra, Apoorva
  • Kalavadiya, Milankumar
  • Joshi, Yugandhara

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240703

Claims (15)

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
  15. 15. A non-transitory computer-readable storage medium storing instructions for managing a persistent connection, the instructions comprising executable code which, when executed by one or more units of a system [200], 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 point configuration associated with the first end point; a determination unit [206] of the system [200] 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] 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, 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] 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 unavailable status; and 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.

Description

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 fir