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 PROCESSING ONE OR MORE NETWORK REQUESTS
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 wireless communication system, more particularly relates to a method and system for processing one or more network requests.
BACKGROUND OF THE INVENTION
[0002] In communication networks, 4G or 5G nodes have storage which may include Home Subscriber Server (HSS) or Unified Data Management (UDM). The HSS and UDM may work together and may act as storage (or database) to different nodes and act as database of subscriber information.
[0003] The Diameter base protocol is intended to provide an Authentication, Authorization, and Accounting (AAA) framework for applications such as network access or IP mobility in both local and roaming situations. In case of any transaction between a peer node and HSS, the HSS communicates with its peer node on the interface.
[0004] In case of application component failure, the HSS will send an error. For example, diameter errors such as network not available, unable to comply, etc. depending upon the state. So, when the HSS fails, it will propagate to the end node and the retry can be either by end node or by peer node. For example, HSS is in communication with MME, and MME comes to know that HSS has failed, the MME can retry or send error message that the service is not available, or request not serviced, etc. In this case, a single node failure will cause a single message failure.
[0005] In case of application component failure, signaling message is either retried by Diameter Agent or directly by peer node. So, the application component failure could cause the whole message to be retransmitted over the network again.
[0006] Further, in case of repeated re-attempts from the peer nodes, it will involve multiple transactions, which in turn will add to the latency to servicing. There will be additional load on the processing and will require more time.
[0007] As a result, owing to the failure / error reported and a delay / latency in processing, the KPI of the network is affected / degraded and there is a service impact, and the service quality is also affected in case of failures.
[0008] There is therefore a need to overcome the above disadvantages in signal processing in case of a component failure.
SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a system and a method for processing one or more network requests.
[0010] In one aspect of the present invention, the system for processing one or more network requests is disclosed. The system includes an assigning unit configured to assign one or more Provider Layer (PL) and User Layer (UL) to a network interface. The system further includes a receiving unit configured to receive, the one or more network requests from at least one agent, the one or more network request is received at the one or more UL via the one or more PL. The system further includes a checking unit configured to check if a response is received from the one or more UL within a predefined time limit. The system further includes a re-transmitting unit configured to re-transmit, the one or more network requests to an alternative UL upon failure to receive the response from the UL within the predefined time limit.
[0011] In an embodiment, a count of the one or more PL and the UL assigned to the network interface is based on a network operator requirement. In an embodiment, a list of the one or more PL and the UL assigned to the network interface is stored in a database.
[0012] In an embodiment, the network interface is at least one of, a diameter stack interface. In an embodiment, the at least one agent includes at least one of, a peer node and a routing agent. In an embodiment, the alternative UL pertains to an available UL.
[0013] In another aspect of the present invention, the method for processing one or more network requests is disclosed. The method includes the step of assigning one or more Provider Layer (PL) and User Layer (UL) to a network interface. The method further includes the step of receiving the one or more network requests from at least one agent, the one or more network request is received at the one or more UL via the one or more PL. The method further includes the step of checking if a response is received from the one or more UL within a predefined time limit. The method further includes the step of re-transmitting the one or more network requests to an alternative UL upon failure to receive the response from the UL within the predefined time limit.
[0014] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to assign one or more Provider Layer (PL) and User Layer (UL) to a network interface. The processor is further configured to receive the one or more network requests from at least one agent, the one or more network request is received at the one or more UL via the one or more PL. The processor is further configured to check if a response is received from the one or more UL within a predefined time limit. The processor is further configured re-transmit the one or more network requests to an alternative UL upon failure to receive the response from the UL within the predefined time limit.
[0015] 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
[0016] 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.
[0017] FIG. 1 is an exemplary block diagram of an environment for processing one or more network requests, according to one or more embodiments of the present invention;
[0018] FIG. 2 is an exemplary block diagram of a system for processing the one or more network requests, according to one or more embodiments of the present invention;
[0019] FIG. 3 is an exemplary block diagram of an architecture of the system of the FIG. 2, according to one or more embodiments of the present invention;

[0020] FIG. 4 is a signal flow diagram for processing the one or more network requests, according to one or more embodiments of the present invention; and
[0021] FIG. 5 is a schematic representation of a method for processing the one or more network requests, according to one or more embodiments of the present invention.
[0022] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0023] 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.
[0024] 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.
[0025] 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.
[0026] The present disclosure is about redundancy at application level where multiple components will be available to a network interface. The network interface is aware of the applications which can serve the incoming request based on diameter-application-Ids. So, in case of any component failure, the network interface is able to serve the signaling traffic from another locally available application.
[0027] FIG. 1 illustrates an exemplary block diagram of an environment 100 for processing one or more network requests, 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 processing one or more network 106 requests.
[0028] 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. 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”.
[0029] In an embodiment, the UE 102 is one of, but 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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 for processing one or more network requests. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0034] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0035] FIG. 2 is an exemplary block diagram of the system 108 for uniform distribution of one or more data packets, according to one or more embodiments of the present invention.
[0036] 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 network interface 210. 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.
[0037] 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.
[0038] 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.
[0039] 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.
[0040] The network interface 210 is the point of interconnection between the UE 102 and the network 106. The network interface 210 is one of, but not limited to, ethernet cards or Network Interface Cards (NICs), Wireless Network Interface Cards (WNICs), fiber optic NICs, modems, loopback interfaces, Virtual LANs (VLANs), tunneling interfaces, bridge interfaces, InfiniBand interfaces, Bluetooth interface.
[0041] In order for the system 108 for processing one or more network 106 requests, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, an assigning unit 212, a receiving unit 214, a checking unit 216, and re-transmitting unit 218 communicably coupled to each other for processing one or more network requests.
[0042] The assigning unit 212, the receiving unit 214, the checking unit 216, and re-transmitting unit 218 in an 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. 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.
[0043] In one embodiment, the assigning unit 212 is configured to assign one or more Provider Layer (PL) 304 (as shown in FIG .3) and User Layer (UL) 306 (as shown in FIG. 3) to the network interface 210. The Diameter PL 304 is a network layer which interacts between the network and the UL 306. The UL 306 interacts between the PL 304 and the database 208. All business logics are implemented at the UL 306. In one embodiment, the PL and the UL are the instances of a Home Subscriber Server (HSS).
[0044] In one embodiment, a count of the one or more PL 304 and the UL 306 assigned to the network interface is based on a network operator requirement. The network operator requirement refers to the specific needs, policies, and criteria set by a network operator to ensure that the network 106 meets its operational goals, performance standards, and Service Level Agreements (SLAs). The network operator requirements guide the design, implementation, and management of network infrastructure and services to align with the operator's objectives and user expectations. The network operator requirements include, but not limited to bandwidth allocation, latency, securing protocols, redundancy plans, SLAs.
[0045] In one embodiment, a list of the one or more PL 304 and the UL 306 assigned to the network interface 210 is stored in the database 208. The network interface 210 is at least one of, a diameter stack interface. The diameter stack interface refers to a set of standardized protocols and interfaces used in telecommunication networks, particularly for Authentication, Authorization, and Accounting (AAA) purposes. The diameter stack interface includes, but not limited to diameter base protocol, diameter applications, diameter nodes.
[0046] Upon assigning the one or more PL 304 and UL 306 to the network interface 210 by the assigning unit 212, the one or more network requests is received from at least one agent by the receiving unit 214. The one or more network 106 requests is received at the one or more UL 306 via the one or more PL 304. The at least one agent includes at least one of, a peer node 302 (as shown in FIG. 3) and a routing agent.
[0047] The peer node 302 refers to any entity or endpoint that can directly communicate with another entity using the diameter protocol. The peer nodes 302 are typically involved in exchanging diameter messages directly without the need for intermediate nodes. Each peer node 302 is capable of both initiating and responding to diameter requests and can serve as a client, server, or both depending on the scenario. More specifically, the peer node 302 make requests to get subscriber related data to perform subscriber related function or service. The peer nodes 302 include, but not limited to Mobility Management Entity (MME), network functions, Access and Mobility Management Function (AMF), IP Short Message Gateway (IP-SM-GW), Gateway Mobile Location Centre (GMLC), and so forth. The routing agent refers to an intermediary node that facilitates the routing of messages between other nodes. Routing agents do not typically initiate requests themselves but rather ensure that messages are correctly forwarded to their intended destinations. The routing agent may also provide additional functionalities such as load balancing, policy enforcement, and failover handling. Thus, the network 106 is capable of handling requests originating directly from endpoints (peer nodes) as well as those forwarded or modified by intermediary nodes (routing agents). The handling requests ensures flexibility and robustness in handling various network 106 scenarios and managing the flow of diameter messages across different components of the network infrastructure.
[0048] After receiving the one or more network 106 requests from the at least one agent, the checking unit 216 is configured to check if a response is received from the one or more UL 306 within a predefined time limit. The predefined time limit refers to a specific duration of time that is set in advance within which the response from the UL 306 is expected. If the response is received within the predefined time, the response is sent to the network 106.
[0049] Alternatively, if the response from the one or more UL 306 is not received within the predefined time, the one or more network 106 requests is re-transmitted by the re-transmitting unit 218 to an alternative UL 306. The alternative UL 306 pertains to an available UL 306. For example, the predefined time is set at 2-3 seconds. If the response is received from the one or more UL 306 within 2 seconds, then the response is sent to the network 106. Alternatively, if the response is received after 5 seconds, then the response is not received within the predefined time. Thus, the one or more requests is re-transmitted to the next available UL 306.
[0050] In one embodiment, one or multiple application components (based on operator requirements) against Diameter Stack interface receive all network requests from peer nodes 302/ Routing Agents. Further, the list of the one or more UL 306 is maintained at diameter stack interface which serves the incoming application-Id request. The application-Id is specific to application or interfaces (having diameter protocol) between HSS and the peer nodes. For example, Sh interface (diameter protocol) between IP-SM-GW and the HSS has application-id 16777217. Thereafter the response from the list of the one or more UL 306 is received at the PL 304. If the response from the list of one or more UL 306 is not received within the predefined time, stack retries the same signaling request at another available UL 306. In particular, the PL 304 re-transmits the one or more network 106 requests to the available UL 306. As a result, the failure is avoided and saved, and no error is reported except for a delay in the order of a few milliseconds. So, the Key performance Indicator (KPI) of the network is not affected or degraded. Thus, there is no service impact, and the service quality is maintained even in case of failures.
[0051] FIG. 3 is an exemplary block diagram of an architecture 300 of the system of the FIG. 2, according to one or more embodiments of the present invention.
[0052] The architecture 300 includes peer node 302, PL 304, plurality of ULs 306 such as 1UL 306, 2UL 306, 3UL 306, 4UL 306 and database 208. In an embodiment, the one or more network 106 requests is received from at least one agent. The at least one agent includes at least one of, the peer node 302. The one or more network 106 request is received at the one or more UL 306 via the one or more PL 304. When one or more network 106 requests are received at PL 304, the PL 304 forwards the one or more network 106 request to any one of the ULs 306 (1UL 306, 2UL 306, 3UL 306, 4UL 306). If the response is received from any one of the ULs 306, the checking unit 216 (as shown in FIG. 2) checks if the response which was received has been received within a time limit. If the response is received within the time limit, the response is sent to the network 106. In one embodiment, when the time in which the response is received exceeds the time limit, the PL 304 tries other available UL 306 chosen from the rest of the ULs 306 (1UL 306, 2UL 306, 3UL 306, 4UL 306).
[0053] For instance, when the one or more network 106 requests is received at the PL 304 from the peer node 302, the PL 304 forwards the one or more network 106 request to 1UL 306. If the response is received from the 1UL 306, the checking unit 216 (as shown in FIG. 2) checks if the response is received from the 1UL 306 is received within the time limit. If the response from the 1UL 306 is received within the time limit, the response is sent to the network 106. If the response from the 1UL 306 is not received within the time limit, the PL 304 tries with 2UL 306 or 3UL 306 or 4UL 306 whichever is available.

[0054] FIG. 4 is a signal flow diagram for processing one or more network requests, according to one or more embodiments of the present invention.
[0055] At step 402, the one or more PL 304 and the one or more UL 306 are assigned to the network interface 210. The count of the one or more PL 304 and the UL 306 assigned to the network interface 210 is based on the network operator requirement. The network interface 210 is at least one of the diameter stack interface.
[0056] At step 404, the list of the one or more PL 304 and the UL 306 assigned to the network interface 210 is stored in the database 208.
[0057] At step 406, the one or more network 106 requests is received from the at least one agent. The at least one agent includes at least one of, the peer node 302 and the routing agent. The one or more network request is received at the PL 304.
[0058] At step 408, the one or more network 106 request is received at the PL 304 and the same one or more network 106 requests is transmitted to the at least one UL 306.
[0059] At step 410, upon receiving the one or more network requests from the PL 304, the at least one UL 306 fetches the data from the database 208.
[0060] At step 412, upon fetching the data from the database 208, the UL 306 responds to the one or more network 106 requests received from the PL 304. Subsequently, the received response from the at least one UL 306 is checked by the checking unit 216, if the response received from the at least one UL 306 is within the predefined time limit and a success response (identified using status codes). If the response from the at least one UL 306 is received within the predefined time limit, the response is transmitted to the network 106 or agent (at step 414). Alternatively, if the response from the at least one UL 306 is not received within the predefined time limit, the PL 304 re-transmits the one or more network request to the alternative UL 306. The alternative UL 306 pertains to the available UL 306.
[0061] FIG. 5 is a flow diagram of a method 500 for processing one or more network requests, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0062] At step 502, the method 500 includes the step of assigning the one or more PL 304 and the UL 306 to the network interface 210 by the assigning unit 212. The count of the one or more PL 304 and the UL 306 assigned to the network interface 210 is based on the network operator requirement. The list of the one or more PL 304 and the UL 306 assigned to the network interface 210 is stored in the database 208. The network interface 210 is at least one of the diameter stack interface.
[0063] At step 504, the method 500 includes the step of receiving the one or more network 106 requests from the at least one agent by the receiving unit 214. The at least one agent includes at least one of the peer node 302 and the routing agent. The one or more network 106 request is received at the one or more UL 306 via the one or more PL 304.
[0064] At step 506, the method 500 includes the step of checking if the response is received from the one or more UL 306 within the predefined time limit by the checking unit 216.
[0065] At step 508, the method 500 includes the step of re-transmitting the one or more network requests to the alternative UL 306 upon failure to receive the response from the UL 306 within the predefined time limit by the re-transmitting unit 218.
[0066] 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 assign the one or more PL 304 and UL 306 to the network interface 210. The processor 202 is further configured to receive the one or more network 106 requests from the at least one agent. The one or more network 106 request is received at the one or more UL 306 via the one or more PL 304. The processor 202 is further configured to check if the response is received from the one or more UL 306 within the predefined time limit. The processor 202 is further configured to re-transmit the one or more network requests to the alternative UL 306 upon failure to receive the response from the UL 306 within the predefined time limit.
[0067] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) 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.
[0068] The present disclosure incorporates technical advancement that the transparency to the network peer nodes in case of component failure. As the one or more network requests are re-transmitted to the available UL, the failure is avoided and saved, and no error is reported except for a delay in the order of a few milliseconds. Thus, the KPI of the network is not affected / degraded and there is no service impact, and the service quality is maintained even in case of failures.
[0069] 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

[0070] Environment- 100
[0071] User Equipment (UE)- 102
[0072] Server- 104
[0073] Network- 106
[0074] System -108
[0075] Processor- 202
[0076] Memory- 204
[0077] User Interface- 206
[0078] Database- 208
[0079] Network Interface- 210
[0080] Assigning Unit- 212
[0081] Receiving Unit- 214
[0082] Checking unit- 216
[0083] Re-transmitting Unit – 218
[0084] Peer Node- 302
[0085] Provider Layer (PL)- 304
[0086] User Layer- 306

,CLAIMS:CLAIMS:

We Claim:
1. A method (500) for processing one or more network (106) requests, the method (500) comprising the steps of:
assigning, by one or more processors (202), one or more Provider Layer (PL) (304) and User Layer (UL) (306) to a network interface (210);
receiving, by the one or more processors (202), the one or more network (106) requests from at least one agent, the one or more network (106) request is received at the one or more UL (306) via the one or more PL (304);
checking, by the one or more processors (202), if a response is received from the one or more UL (306) within a predefined time limit; and
re-transmitting, by the one or more processors (202), the one or more network (106) requests to an alternative UL (306) upon failure to receive the response from the UL (306) within the predefined time limit.

2. The method (500) as claimed in claim 1, wherein a count of the one or more PL (304) and the UL (306) assigned to the network interface (210) is based on a network operator requirement.

3. The method (500) as claimed in claim 1, wherein a list of the one or more PL (304) and the UL (306) assigned to the network interface (210) is stored in a database (208).

4. The method (500) as claimed in claim 1, wherein the network interface (210) is at least one of, a diameter stack interface.

5. The method (500) as claimed in claim 1, wherein the at least one agent includes at least one of, a peer node (302) and a routing agent.

6. The method (500) as claimed in claim 1, wherein the alternative UL (306) pertains to an available UL (306).

7. A system (108) of processing one or more network (106) requests, the system (108) comprising:
an assigning unit (212) configured to assign one or more Provider Layer (PL) (304) and User Layer (UL) (306) to a network interface (210);
a receiving unit (214) configured to receive, the one or more network (106) requests from at least one agent, the one or more network (106) request is received at the one or more UL (306) via the one or more PL (304);
a checking unit (216) configured to check if a response is received from the one or more UL (306) within a predefined time limit; and
a re-transmitting unit (218) configured to re-transmit, the one or more network (106) requests to an alternative UL (306) upon failure to receive the response from the UL (306) within the predefined time limit.

8. The system (108) as claimed in claim 7, wherein a count of the one or more PL (304) and the UL (306) assigned to the network interface (210) is based on a network operator requirement.

9. The system (108) as claimed in claim 7, wherein a list of the one or more PL (304) and the UL (306) assigned to the network interface (210) is stored in a database (208).

10. The system (108) as claimed in claim 7, wherein the network interface (210) is at least one of, a diameter stack interface.

11. The system (108) as claimed in claim 7, wherein the at least one agent includes at least one of, a peer node (302) and a routing agent.

12. The system (108) as claimed in claim 7, wherein the alternative UL pertains to an available UL.