DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR DE-ESTABLISHING NETWORK PROTOCOL CONNECTIONS
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to a wireless communication system, and more particularly, relates to a method and system for de-establishing network protocol connections.
BACKGROUND OF THE INVENTION
[0002] In network applications, in a ‘race’ condition, when there is network failure or when the application/server is closing the connection, the actual number of HTTP/2.0 connections created at the client end is more than the configured number of connections. For example, when the configured number is 10, then, in the above cases, the actual number of connections created may be 12 or 13. This is one condition. Therefore, in certain conditions, such as a race condition, the actual number of HTTP/2.0 connections that are created is greater than the configured number of connections. Secondly, in the condition of dynamic management of HTTP/2.0 connections, the number of HTTP/2.0 connections is gracefully increased to handle higher traffic.
[0003] Therefore, in the above two conditions (i.e. firstly, in a condition associated with a race condition, during network failure or the connection getting closed from the server end, and secondly, in a condition of graceful creation of extra connections to handle the extra traffic), the actual number of HTTP/2.0 connections created is greater than the configured number of connections. The excess connection may be created due to traffic surge resulting in addition of extra connection to cater the surge traffic.
[0004] There is, therefore, a need for a solution for de-establishing excess concurrent connections (e.g. HTTP/2.0 connections) while avoiding request failures.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and system for de-establishing network protocol connections.
[0006] In one aspect of the present invention, a system for de-establishing network protocol connections is disclosed. The system includes a network protocol manager configured to determine an actual number of network protocol connections established at an endpoint and configured number of network protocol connections for the endpoint. Further, the network protocol manager is configured to check if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections. Further, the system includes an identification module configured to parse a list, to identify one or more excess network protocol connections when the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections. Further, the system includes a de-establishing module configured to de-establish the one or more excess network protocol connections from the list.
[0007] In an embodiment, once the one or more excess network protocol connections are de-established from the list, a transceiver of the system does not forward the request to the one or more excess network protocol connections. In an embodiment, upon de-establishment, the network protocol manager isolates the excess network protocol connections from the actual network protocol connections for a predefined time period, wherein the predefined time period is configured to be twice a response timeout time period of the one or more excess network protocol connections.
[0008] In an embodiment, upon isolation the request pertaining to the one or more excess network protocol connections are configured to one of successfully complete and timeout within the predefined time period. In an embodiment, the network protocol manager is further configured to perform a check to determine if a request is pending at, at least one of the de-established network protocol connections.
[0009] In an embodiment, the actual number of network protocol connections includes connections which are in effect between a client end and a server end. In an embodiment, the configured number of network protocol connections includes connections which are provided in excess to the actual number of network protocol connections in order to ease communication during surge in traffic between a client and a server end.
[0010] In an embodiment, the list is indicative of the configured number of network protocol connections for the endpoint. In an embodiment, the excess network protocol connections are the difference between the actual number of network protocol connections for the endpoint and the configured number of network protocol connections. The network protocol connection is at least one of, a Hypertext Transfer Protocol 2 (HTTP2).
[0011] In another aspect of the present invention, a method of de-establishing network protocol connections is disclosed. The method includes the steps of determining an actual number of network protocol connections established at an endpoint and configured number of network protocol connections for the endpoint. The method further includes the steps of checking if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections. The method further includes the steps of parsing a list, to identify one or more excess network protocol connections when the actual number of network protocol connections for the endpoint is greater than the configured number of network protocol connections. The method further includes the steps of de-establishing the one or more excess network protocol connections from the list.
[0012] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be 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.
[0014] FIG. 1 is an exemplary block diagram of an environment for de-establishing network protocol connections, according to one or more embodiments of the present invention;
[0015] FIG. 2 is an exemplary block diagram of the system for de-establishing the network protocol connections, according to one or more embodiments of the present invention;
[0016] FIG. 3 is an exemplary flow diagram of the system of FIG. 2, according to one or more embodiments of the present invention;
[0017] FIG. 4 is an exemplary architecture diagram for de-establishing the network protocol connections, according to one or more embodiments of the present invention; and
[0018] FIG. 5 is a flow diagram of a method of de-establishing the network protocol connections, according to one or more embodiments of the present invention.
[0019] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0020] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0021] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0022] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0023] As per various embodiments depicted, the present invention discloses the system and method of de-establishing network protocol connections.
[0024] FIG. 1 illustrates an exemplary block diagram of an environment 100 for de-establishing network protocol connections, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for de-establishing the at least one network protocol connection, hereinafter referred to as the network protocol connections.
[0025] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. Accordingly, in alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0026] In an embodiment, the UE 102 is not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0027] The environment 100 includes the server 104 accessible via the network 106. The server 104 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0028] The network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0029] The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0030] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to de-establish the network protocol connections in the network 106. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity. However, for the purpose of description, the system 108 is described as an integral part of the server 104, without deviating from the scope of the present disclosure.
[0031] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0032] FIG. 2 is an exemplary block diagram of the system 108 for de-establishing network protocol connections, according to one or more embodiments of the present invention.
[0033] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, a database 208 and a transceiver 216. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0034] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0035] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0036] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0037] In order for the system 108 to de-establish the network protocol connection, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a network protocol manager 210, an identification module 212, and a de-establishing module 214 communicably coupled to each other to de-establish the network protocol connections.
[0038] The network protocol manager 210, the identification module 212, the de-establishing module 214 and the transceiver 216, in an exemplary embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0039] In an embodiment, the network protocol connection is the establishment and management of communication between two or more UE 102 over the network 106 using a specific protocol or set of protocols. The network protocol connection includes, but not limited to, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Simple Network Management Protocol (SNMP), Internet Control Message Protocol (ICMP), Hypertext Transfer Protocol Secure (HTTPS) and Terminal Network (TELNET). The network protocol connection in the present disclosure is at least one of, a Hypertext Transfer Protocol 2 (HTTP2).
[0040] In an embodiment, an endpoint includes an actual number of network protocol connections. The endpoint is a specific connection point, such as URL in web services or an Internet Protocol (IP) address in internet communication. The actual number of network protocol connections include the defined number of connections between a server end 304 and a client end 302 to aid in communication therebetween. The example for the connection between the server end 304 and the client end 302 is as follows, the connection is established when a user visits https://www.example.com using a web browser. The browser (client) makes an HTTP/HTTPS request to the server at www.example.com (server), and the server responds with the requested web page. The actual number of network protocol connections are identified by determining the scope of the connections, capturing active connections by using network monitoring tools, system commands or programming libraries, identifying and filtering the connections and counting the number of connections that meets the filtering criteria. In scenarios where there exists a surge in network traffic, excess connections, or otherwise termed as a configured number of network protocol connections are provided between the server end 304 and the client end 302. The configured number of network protocol connections aids in easing communication during surge in traffic between the client end 302 (shown in FIG. 3) and the server end 304 (shown in FIG.3).
[0041] Referring to FIG. 2, in order to de-stablish the network protocol connection, in one embodiment, the network protocol manager 210 of the processor 202 is configured to determine the actual number of network protocol connections established at the endpoint and the configured number of network protocol connections for the endpoint. The network protocol manager 210 determines the actual number of network protocol connections established at the endpoint by monitoring active connections, collecting statistics from the network interface, and monitoring protocol- specific tools and libraries that provide information about active sessions and streams (for example, HTTP2 libraries). The network protocol manager 210 determines the configured number of network protocol connections for the endpoint by reading from the configuration files where the maximum allowed number of connections for each endpoint is specified, interfacing with a network policy management system that dynamically provides configuration parameters and accessing the database 208 that stores configuration parameters for different endpoints. On determination, the network protocol manager 210 is configured to check if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections. The network protocol manager 210 checks the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections by retrieving and comparing the actual number of connections and the configured number of connections. More specifically, the network protocol manager 210 compares the actual number of active connections with the configured number using a simple conditional check. The conditional check refers to the process where the network protocol manager 210 evaluates whether the actual number of network protocol connections at an endpoint meets the criteria defined by the configured number of network protocol connections.
[0042] Upon determining and checking the configured and the actual number of protocol connections of the endpoint by the network protocol manager 210, the identification module 212 is configured to parse a list to identify one or more excess network protocol connections. The list is the indicative of the configured number of network protocol connections for the endpoint. The list containing network protocol connection has a structured format with a set of headers and associated parameters for each connection entry. The headers and parameters represent specific attributes and details of each network protocol connection. The headers include, but are not limited to, connection Identifier (ID), source Internet Protocol (IP) address, destination IP address, source port, destination port, status, timestamp, protocol. The parameters are the values corresponding to each header for a specific network protocol connection. The list is parsed by retrieving the number of active connections and comparing the total number of active connections with configured number of network protocol connections. Further, if the actual number of active connections is greater than the configured number of network protocol connections, the number of excess connections is identified. On parsing of the list, the identification module 212 is configured to determine the one or more excess network protocol connections.
[0043] A connection is determined to be one or more excess network protocol connections if the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections. More specifically, the one or more excess network protocol connections is the difference between the actual number of network protocol connections for the endpoint and the configured number of network protocol connections for the endpoint as indicated in the list.
[0044] Upon determining the one or more excess network protocol connections by the identification module 212, the de-establishing module 214 is configured to de-establish the one or more excess network protocol connections from the list.
[0045] In one embodiment, the transceiver 216 of the system 108 receives the request from the client end 302 and forwards the same request to the network protocol connection. The request includes, but is not limited to, data, service, Hypertext Transfer Protocol (HTTP) requests and the like. Further, on de-establishing the network protocol connections from the list by the de-establishing module 214, the transceiver 216 of the system 108 does not forward the request to the one or more excess network protocol connections.
[0046] Further, upon de-establishment of the one or more excess network protocol connections by the de-establishing module 214, the network protocol manager 210 isolates the one or more excess network protocol connections from the actual network protocol connections for a predefined time period. The isolation refers to segregating or marking the excess network protocol connections such that the excess network protocol connections are prevented from participating in network communication processes. The predefined time period refers to a specific duration of time that has been predetermined or set in advance for one or more excess network protocol connections to either complete the request successfully or timeout. Further, the predefined time period is configured to be twice a response timeout of the one or more excess network protocol connections. For instance, a request whose response timeout is 10 seconds, that connection may be kept idle for 20 seconds.
[0047] After the predefined time period, the network protocol manager 210 is further configured to perform a check, to determine if the request is pending at, at least one of the de-established network protocol connections. Once it is determined that there is no pending request at the de-established network protocol connection, then the connection is closed.
[0048] FIG. 3 is an exemplary flow diagram of the system of FIG. 2, according to one or more embodiments of the present invention.
[0049] For the purpose of description of the exemplary embodiment as illustrated in FIG. 3, the client 302 is considered as a SCP proxy 302 and the server 304 is considered as an NF instance 304. The SCP proxy 302 is an application that uses one or more network protocol connections to communicate with the NF Instance 304.
[0050] As per the illustrated embodiment in FIG. 3a and FIG. 3b, the one or more network protocol connections are established between the SCP proxy 302 and the NF instance 304. As per FIG. 3a, the SCP proxy 302 includes two network protocol connections 306 and 308 to communicate with the NF instance 304. The two network protocol connections 306, 308 constitute the actual number of network protocol connections.
[0051] In certain scenarios, due to a surge in the network traffic, the actual network protocol connections 306 and 308 are burdened. In such scenarios, an excess or additional network protocol connection may be added in addition to the actual network protocol connections. Accordingly, as per the illustrated embodiment, the two network protocol connections 306, 308 and the excess network protocol connection 310 together constitute the configured number of network protocol connections to aid in easing the network traffic. In addition, the processor 202 of the system 108 updates the list with the excess network protocol connection.
[0052] When the network traffic surge between the server and the client end 304, 302 reduces, the actual number of network protocol connections are sufficient to handle the traffic therebetween. Accordingly, the excess network protocol connection 310 is required to be de-established. The processor 202 of the system 108 is configured to parse the list to identify the one or more excess network protocol connections, or in this case the excess network protocol connection 310.
[0053] The excess network protocol connection is the difference between the actual and the configured number of network protocol connections. Accordingly, the processor 202 of the system 108 is configured to de-establish the excess network protocol connection 310. On de-establishment, only the two network protocol connections 306, 308, i.e., the actual number of network protocol connections, exist between the sever end 304 and the client end 302, As is shown in FIG. 3b.
[0054] For example, three connections (HTTP/2.0) are configured between the client-end 302 and the server-end 304. When the traffic at the rate of 10,000 TPS is received between the client-end 302 and the server-end 304, one connection seems to be an extra connection. Hence the extra one connection needs to be removed to reduce mesh in the network.
[0055] FIG. 4 is an exemplary architecture diagram 400 for de-establishing network protocol connections, according to one or more embodiments of the present invention.
[0056] The architecture 400 includes a HTTP client scheduler module 402, HTTP client memory cache 404, a HTTP client connection module 406, connection management 408, a HTTP server 410. The HTTP server 410 includes, but not limited to, a HTTP server 410a, a HTTP server 410b, and a HTTP server 410c, and should nowhere be construed as limiting the scope of the present disclosure.
[0057] In an embodiment, the HTTP client scheduler module 402 interacts with the HTTP client memory cache 404 to fetch the configuration data (configured number of connections) and determines the actual number of connections and the fetched configured number of connections. The HTTP client scheduler module 402 is responsible for determining the number of connections to be established or maintained with each of the HTTP server 410. The HTTP client memory cache 404 stores configuration data such as the number of allowed connections for each of the HTTP server 410.
[0058] Upon determining the actual number of connections and the fetched configured number of connections, if the actual number of connections is greater than the configured number of connections, the HTTP client connection module 406 de-establishes the excess connections. For example, if the actual number of connections is 13 and the configured number of connections is 10, then the 3 excess connections are de-established.
[0059] In an embodiment, the HTTP client connection module 406 manages the connection between each of the HTTP server 410a, the HTTP server 410b, and the HTTP server 410c. The HTTP client connection module 406 is responsible for establishing, maintaining, and de-establishing connections based on the inputs from the HTTP client scheduler module 402 and the HTTP client memory cache 404.
[0060] FIG. 5 is a flow diagram of a method 500 for de-establishing network protocol connections, according to one or more embodiments of the present invention. For the purpose of description, the method is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0061] At step 502, the method 500 includes the step of determining the actual number of network protocol connections established at the endpoint and the configured number of network protocol connections for the endpoint. In one embodiment, the network protocol manager 210 of the processor 202 is configured to determine the actual number of network protocol connections established at the endpoint and the configured number of network protocol connections for the endpoint.
[0062] At step 504, the method 500 includes the step of checking if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections.
[0063] At 506, the method 500 includes the step of parsing the list to the network protocol connections when the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections. Upon determining the configured and the actual number of network protocol connections of the endpoint by the network protocol manager 210, the identification module 212 is configured to parse the list to identify one or more excess network protocol connections. The list is the indicative of the configured number of network protocol connections for the endpoint. On parsing of the list, the parsing module is configured to determine the one or more excess network connections. The connection is determined to be the one or more excess network connections if the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections.
[0064] At 508, the method 500 includes the step of de-establishing the one or more excess network protocol connections from the list. Upon determining one or more excess network protocol connections by the identification module 212, the de-establishing module 214 is configured to de-establish the one or more excess network protocol connections from the list.
[0065] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to determine the actual number of network protocol connections established at the endpoint and configured number of network protocol connections for the endpoint. The processor 202 is further configured to check if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections. The processor 202 is further configured to parse the list to identify one or more excess network protocol connections when the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections. The processor 202 is further configured to de-establish, the one or more excess network protocol connections from the list.
[0066] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-4) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0067] The present disclosure incorporates technical advancement of de-stablishing the network protocol connections by reducing the network mesh by decreasing excess connections in the network while avoiding request failures. Further it also reduces the CPU and RAM utilization at the client-end and server-end connections. Further, it also reduces the total PING frame in the network as excess connections are removed from network. The present disclosure incorporates various advantages including avoiding overall KPI degradation, adjusting number of channels per endpoint, thereby resulting in optimization of overall system resource.
[0068] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0069] Environment- 100
[0070] User Equipment (UE)- 102
[0071] Server- 104
[0072] Network- 106
[0073] System -108
[0074] Processor- 202
[0075] Memory- 204
[0076] User Interface- 206
[0077] Database- 208
[0078] Network Protocol Manager- 210
[0079] Identification module- 212
[0080] De-establishing module – 214
[0081] Transceiver- 216
[0082] SCP Proxy (Client)– 302
[0083] NF instance (Server)- 304
[0084] HTTP client scheduler module -402
[0085] HTTP client memory cache -404
[0086] HTTP client connection module -406
[0087] Connection management -408
[0088] HTTP server -410

,CLAIMS:CLAIMS:
We Claim
1. A method (500) of de-establishing network protocol connections, the method (500) comprising the steps of:
determining, by one or more processors (202), an actual number of network protocol connections established at an endpoint and configured number of network protocol connections for the endpoint;
checking, by the one or more processors (202), if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections;
parsing, by the one or more processors (202), a list to identify one or more excess network protocol connections when the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections; and
de-establishing, by the one or more processors (202), the one or more excess network protocol connections from the list.

2. The method (500) as claimed in claim 1, wherein once the one or more excess network protocol connections are de-established from the list, the one or more processors does not forward the request to the one or more excess network protocol connections.

3. The method (500) as claimed in claim 1, wherein upon de-establishment, the one or more excess network protocol connections are isolated from the actual network protocol connections for a predefined time period, wherein the predefined time period is configured to be twice a response timeout time period of the one or more excess network protocol connections.

4. The method (500) as claimed in claim 3, wherein upon isolation, the request pertaining to the one or more excess network protocol connections are configured to one of successfully complete and timeout within the predefined time period.

5. The method (500) as claimed in claim 1, wherein the method (400) further performs the step of performing, by the one or more processors (202), a check to determine if a request is pending at, at least one of the de-established network protocol connections.

6. The method (500) as claimed in claim 1, wherein the actual number of network protocol connections includes connections which are in effect between a client end and a server end.

7. The method (500) as claimed in claim 1, wherein the configured number of network protocol connections includes connections which are provided in excess to the actual number of network protocol connections in order to ease communication during surge in traffic between a client and a server end.

8. The method (500) as claimed in claim 1, wherein the list is indicative of the configured number of network protocol connections for the endpoint.

9. The method (500) as claimed in claim 1, wherein the excess network protocol connections is the difference between the actual number of network protocol connections for the endpoint and the configured number of network protocol connections, wherein the network protocol connection is at least one of, a Hypertext Transfer Protocol 2 (HTTP2).

10. A system (108) for de-establishing network protocol connections, the system (108) comprising:
a network protocol manager (210) configured to:

determine, an actual number of network protocol connections established at an endpoint and configured number of network protocol connections for the endpoint;
check, if the configured number of network protocol connections for the endpoint is one of equal and greater than the actual number of network protocol connections;
an identification module (212) configured to, parse, a list to identify one or more excess network protocol connections when the configured number of network protocol connections for the endpoint is greater than the actual number of network protocol connections; and
a de-establishing module (214) configured to, de-establish, the one or more excess network protocol connections from the list.

11. The system (108) as claimed in claim 10, wherein once the one or more excess network protocol connections are de-established from the list, a transceiver (216) of the system (108) does not forward the request to the one or more excess network protocol connections.

12. The system (108) as claimed in claim 10, wherein upon de-establishment, the network protocol manager isolates the excess network protocol connections from the actual network protocol connections for a predefined time period, wherein the predefined time period is configured to be twice a response timeout time period of the one or more excess network protocol connections.

13. The system (108) as claimed in claim 12, wherein upon isolation, the request pertaining to the one or more excess network protocol connections are configured to one of successfully complete and timeout within the predefined time period.

14. The system (108) as claimed in claim 10, wherein the network protocol manager is further configured to perform, a check to determine if a request is pending at, at least one of the de-established network protocol connections.

15. The system (108) as claimed in claim 10, wherein the actual number of network protocol connections includes connections which are in effect between a client end (302) and a server end (304).

16. The system (108) as claimed in claim 10, wherein the configured number of network protocol connections includes connections which are provided in excess to the actual number of network protocol connections in order to ease communication during surge in traffic between a client (302) and a server end (304).

17. The system (108) as claimed in claim 10, wherein the list is indicative of the configured number of network protocol connections for the endpoint.

18. The system (108) as claimed in claim 10, wherein the excess network protocol connections are the difference between the actual number of network protocol connections for the endpoint and the configured number of network protocol connections, wherein the network protocol connection is at least one of, a Hypertext Transfer Protocol 2 (HTTP2).