EP-4740345-A1 - METHOD AND SYSTEM FOR PROCESSING ONE OR MORE NETWORK REQUESTS
Abstract
The present disclosure relates to a system (108) and a method (500) for processing one or more network (106) requests The system (108) includes an assigning unit (212) configured to assign one or more Provider Layer (PL) (304) and User Layer (UL) (306) to a network interface (210). The system (108) further includes a receiving unit (214) configured to receive the one or more network (106) requests from at least one agent. The system (108) further includes a checking unit (216) configured to check if a response is received from the one or more UL (306) within a predefined time limit. The system (108) further includes 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.
Inventors
- BHATNAGAR, AAYUSH
- JHA, ADITYAKAR
- Priyadarshi, Ajay
- KUMAR, DINESH
- Murmu, Raghunath
- Padhan, Sanjeeb
Assignees
- Jio Platforms Limited
Dates
- Publication Date
- 20260513
- Application Date
- 20240629
Claims (13)
- 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.
- 13. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (202), causes the processor (202) to: assign one or more Provider Layer (PL) (304) and User Layer (UL) (306) to a network interface (210); 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); check if a response is received from the one or more UL (306) within a predefined time limit; and 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.
Description
METHOD AND SYSTEM FOR PROCESSING ONE OR MORE NETWORK REQUESTS 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