Search

EP-4740418-A1 - METHOD AND SYSTEM OF HANDLING SESSION INITIATION PROTOCOL PACKETS DISTRIBUTION IN A NETWORK

EP4740418A1EP 4740418 A1EP4740418 A1EP 4740418A1EP-4740418-A1

Abstract

The present disclosure relates to a system (120) and a method (500) of handling Session Initiation Protocol (SIP) packets distribution in a network. The method includes the step of receiving one or more SIP packets addressed to at least one IP Multimedia Subsystem (IMS) node from a User Equipment (UE) (110). The method includes the step of retrieving a relevant fully qualified domain name (FQDN) associated with the at least one IMS node and one or more IP addresses. The method includes the step of determining a status of the at least one IMS node as one of, blacklisted and available, based on comparing a determined number of failures of the one or more IP addresses. The method includes the step of routing the received SIP packet to the at least one IMS node when the status of the at least one IMS node is determined as available or blacklisted.

Inventors

  • BHATNAGAR, AAYUSH
  • BISHT, BIRENDRA
  • Singh, Harbinder Pal
  • KUMAR, ABHAY
  • Kelkar, Priti
  • Eslavath, Mahendra
  • VERMA, HIMANSHU

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240627

Claims (20)

  1. 1. A method (500) of handling Session Initiation Protocol (SIP) packets distribution in a network (105), the method (500) comprises the steps of: receiving (505), by one or more processors (205), one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node (125) from a User Equipment (UE) (110); retrieving (510), by the one or more processors (205), from a node database (245), a relevant fully qualified domain name (FQDN) associated with the at least one IMS node (125); retrieving (515), by the one or more processors (205), one or more IP addresses pertaining to the retrieved FQDN associated with the at least one IMS node (125) from a Domain Name System (DNS) unit; determining (520), by the one or more processors (205), a status of the at least one IMS node (125) as one of, blacklisted and available, based on comparing a determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) with a pre-defined threshold; routing (525), by the one or more processors (205), the received SIP packet to the at least one IMS node (125) when the status of the at least one IMS node (125) is determined as available; and routing (530), by the one or more processors (205), the received SIP packet to a subsequent available IMS node, when the status of the at least one IMS node (125) is determined as blacklisted.
  2. 2. The method (500) as claimed in claim 1, wherein the node database (245) includes a list of FQDNs corresponding to a plurality of IMS nodes.
  3. 3. The method (500) as claimed in claim 1, wherein the status of the at least one IMS node (125) is determined as blacklisted, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) is equal to or above the pre-defined threshold within a pre-defined time interval.
  4. 4. The method (500) as claimed in claim 1, wherein the status of the at least one IMS node (125) is determined as available, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) is below the pre-defined threshold within a pre-defined time interval.
  5. 5. The method (500) as claimed in claim 1, wherein the one or more processors (205), determines a failure of the one or more IP addresses associated with the at least one IMS node (125) when a response is not received from the at least one IMS node (125) within a pre-defined time interval.
  6. 6. The method (500) as claimed in claim 1, wherein the pre-defined threshold corresponds to non-allowable number of failures for the one or more IP addresses associated with the at least one IMS node.
  7. 7. The method (500) as claimed in claim 1 , wherein the at least one blacklisted IMS node is whitelisted subsequent to a pre-determined time period based on a type of the at least one IMS node (125).
  8. 8. The method (500) as claimed in claim 7, wherein the type of the at least one IMS node (125) includes at least one of, an Application Server (AS) node (130) or a Media Gateway Control Function (MGCF) node (135).
  9. 9. The method (500) as claimed in claim 1, wherein the one or more processors (205) determines the subsequent available IMS node by: checking, at a pool including the at least one blacklisted IMS node and the plurality of IMS nodes that share similar characteristics and/or functionalities related to the at least one blacklisted IMS node; and identifying, the subsequent available IMS node present in the pool in response to determining that the number of failures of the one or more IP addresses associated with the said IMS node is below the pre-defined threshold within the pre-defined time interval.
  10. 10. A User Equipment (UE) (110), comprising: one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory unit (310), wherein said memory unit (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to: transmit, Session Initiation Protocol (SIP) packets to a network (105) in order to avail one or more services; and wherein the one or more processors (205) is further configured to perform the method as claimed in claim 1.
  11. 11. A system ( 120) of handling S ession Initiation Protocol (SIP) packets distribution in a network (105), the system (120) comprising: a transceiver (220), configured to, receive, one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node (125) from a User Equipment (UE) (110); a retrieving unit (225), configured to: retrieve, from a node database (245), a relevant fully qualified domain name (FQDN) associated with the at least one IMS node (125); retrieve, one or more IP addresses pertaining to the retrieved FQDN associated with the at least one IMS node (125) from a Domain Name System (DNS) unit; a determining unit (230), configured to, determine, a status of the at least one IMS node (125) as one of, blacklisted and available, based on comparing a determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) with a pre-defined threshold; and a routing unit (240), configured to: route, the received SIP packet to the at least one IMS node (125) when the status of the at least one IMS node (125) is determined as available; and route, the received SIP packet to a subsequent available IMS node, when the status of the at least one IMS node (125) is determined as blacklisted.
  12. 12. The system (120) as claimed in claim 11, wherein the node database (245) includes a list of FQDNs corresponding to a plurality of IMS nodes.
  13. 13. The system (120) as claimed in claim 11, wherein the status of the at least one IMS node (125) is determined as blacklisted, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) is equal to or above the pre-defined threshold within a pre-defined time interval.
  14. 14. The system (120) as claimed in claim 11, wherein the status of the at least one IMS node (125) is determined as available, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) is below the pre-defined threshold within a pre-defined time interval.
  15. 15. The system (120) as claimed in claim 11, wherein the determining unit (230), determines a failure of the one or more IP addresses associated with the at least one IMS node (125) when a response is not received from the at least one IMS node (125) within a pre-defined time interval.
  16. 16. The system (120) as claimed in claim 11, wherein the pre-defined threshold corresponds to non-allowable number of failures for the one or more IP addresses associated with the at least one IMS node (125).
  17. 17. The system (120) as claimed in claim 11, wherein a whitelisting unit (235) of the system, whitelists the at least one blacklisted IMS node subsequent to a predetermined time period based on a type of the at least one IMS node (125).
  18. 18. The system (120) as claimed in claim 11, wherein the type of the at least one IMS node (125) includes at least one of, an Application Server (AS) node (130) or a Media Gateway Control Function (MGCF) node (135).
  19. 19. The system (120) as claimed in claim 11, wherein the determining unit (230), determines the subsequent available IMS node by: checking, at a pool including the at least one blacklisted IMS node and the plurality of IMS nodes that share similar characteristics and/or functionalities related to the at least one blacklisted IMS node; and identifying, the subsequent available IMS node present in the pool in response to determining that the number of failures of the one or more IP addresses associated with the said IMS node is below the pre-defined threshold within the pre-defined time interval.
  20. 20. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (205), causes the processor (205) to: receive, one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node (125) from a User Equipment (UE) (110); retrieve, from a node database (245), a relevant fully qualified domain name (FQDN) associated with the at least one IMS node (125); retrieve, one or more IP addresses pertaining to the retrieved FQDN associated with the at least one IMS node (125) from a Domain Name System (DNS) unit; determine, a status of the at least one IMS node (125) as one of, blacklisted and available, based on comparing a determined number of failures of the one or more IP addresses associated with the at least one IMS node (125) with a predefined threshold; and route, the received SIP packet to the at least one IMS node (125) when the status of the at least one IMS node (125) is determined as available; and route, the received SIP packet to a subsequent available IMS node, when the status of the at least one IMS node (125) is determined as blacklisted.

Description

METHOD AND SYSTEM OF HANDLING SESSION INITIATION PROTOCOL PACKETS DISTRIBUTION IN A NETWORK FIELD OF THE INVENTION [0001] The present invention generally relates to wireless communication networks, and more particularly relates to a method and system for handling Session Initiation Protocol (SIP) packets distribution in the networks. BACKGROUND OF THE INVENTION [0002] The IP Multimedia Subsystem (IMS) network is a framework for delivering multimedia services over IP networks. It provides a standardized architecture for integrating various communication services, such as voice, video, and messaging, into a single network. The IMS network consists of several nodes, including Application Server (AS) nodes and Media Gateway Control Function (MGCF) nodes, which play crucial roles in the system. [0003] When a node in the IMS system goes down, such as the AS node or the MGCF node, it can lead to several problems. One of the main issues is service disruption. The affected node may be responsible for handling specific services or functionalities, and its failure can result in the loss of those services. For example, if an AS node responsible for handling voice calls goes down, users may experience call failures or an inability to initiate new calls. [0004] Another problem that can occur is a loss of network redundancy. In an IMS network, redundancy is often built into the system to ensure high availability and fault tolerance. When a node fails, it can disrupt the redundancy mechanisms, potentially leading to a single point of failure. This can make the network more vulnerable to further failures and increase the risk of service outages. [0005] Therefore, there is a need for an advancement of a system and method that can overcome at least one of the above shortcomings, particularly for handling session initiation protocol packets distribution in the network. BRIEF SUMMARY OF THE INVENTION [0006] One or more embodiments of the present disclosure provide a method and system of handling Session Initiation Protocol (SIP) packets distribution in a network. [0007] In one aspect of the present invention, the method of handling Session Initiation Protocol (SIP) packets distribution in the network is disclosed. The method includes the step of receiving, by one or more processors, one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node from a User Equipment (UE). The method includes the step of retrieving, by the one or more processors, from a node database, a relevant fully qualified domain name (FQDN) associated with the at least one IMS node. The method further includes the step of retrieving, by the one or more processors, one or more IP addresses pertaining to the retrieved FQDN associated with the at least one IMS node from a Domain Name System (DNS) unit. The method includes the step of determining, by the one or more processors, a status of the at least one IMS node as one of, blacklisted and available, based on comparing a determined number of failures of the one or more IP addresses associated with the at least one IMS node with a pre-defined threshold. The method includes the step of routing, by the one or more processors, the received SIP packet to the at least one IMS node when the status of the at least one IMS node is determined as available. The method further includes the step of routing, by the one or more processors, the received SIP packet to a subsequent available IMS node, when the status of the at least one IMS node is determined as blacklisted. [0008] In one embodiment, the node database includes a list of FQDNs corresponding to a plurality of IMS nodes. [0009] In another embodiment, the status of the at least one IMS node is determined as blacklisted, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node is equal to or above the pre-defined threshold within a pre-defined time interval. [0010] In yet another embodiment, the status of the at least one IMS node is determined as available, when the determined number of failures of the one or more IP addresses associated with the at least one IMS node is below the pre-defined threshold within a pre-defined time interval. [0011] In yet another embodiment, the one or more processors, determines a failure of the one or more IP addresses associated with the at least one IMS node when a response is not received from the at least one IMS node within a pre-defined time interval. [0012] In yet another embodiment, the pre-defined threshold corresponds to nonallowable number of failures for the one or more IP addresses associated with the at least one IMS node. [0013] In yet another embodiment, the at least one blacklisted IMS node is whitelisted subsequent to a pre-determined time period based on a type of the at least one IMS node. [0014] In yet another embodiment, the type of the at least one IMS node includes at least one of, an Application Server (AS