WO2025008968A1 - Procédé et système de gestion de distribution de paquets de protocole d'initiation de session dans un réseau - Google Patents

Procédé et système de gestion de distribution de paquets de protocole d'initiation de session dans un réseau Download PDF

Info

Publication number
WO2025008968A1
WO2025008968A1 PCT/IN2024/050955 IN2024050955W WO2025008968A1 WO 2025008968 A1 WO2025008968 A1 WO 2025008968A1 IN 2024050955 W IN2024050955 W IN 2024050955W WO 2025008968 A1 WO2025008968 A1 WO 2025008968A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
ims
ims node
status
blacklisted
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IN2024/050955
Other languages
English (en)
Inventor
Aayush Bhatnagar
Birendra Bisht
Harbinder Pal Singh
Abhay Kumar
Priti Kelkar
Mahendra Eslavath
Himanshu Verma
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025008968A1 publication Critical patent/WO2025008968A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • 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.
  • SIP Session Initiation Protocol
  • 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.
  • AS Application Server
  • MGCF Media Gateway Control Function
  • 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.
  • Another problem that can occur is a loss of network redundancy.
  • 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.
  • One or more embodiments of the present disclosure provide a method and system of handling Session Initiation Protocol (SIP) packets distribution in a network.
  • SIP Session Initiation Protocol
  • the method of handling Session Initiation Protocol (SIP) packets distribution in the network 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).
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • 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.
  • DNS Domain Name System
  • 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.
  • the node database includes a list of FQDNs corresponding to a plurality of IMS nodes.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the type of the at least one IMS node includes at least one of, an Application Server (AS) node or a Media Gateway Control Function (MGCF) node.
  • AS Application Server
  • MGCF Media Gateway Control Function
  • the one or more processors determines the subsequent available IMS node by checking, at a pool including the at least one blacklisted IMS node and a plurality of IMS nodes that share similar characteristics and/or functionalities related to the at least one blacklisted IMS node.
  • the one or more processors determines the subsequent available IMS node by 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.
  • SIP Session Initiation Protocol
  • the system includes a transceiver, configured to receive, one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node from a User Equipment (UE).
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the system includes a retrieving unit configured to retrieve, from a node database, a relevant fully qualified domain name (FQDN) associated with the at least one IMS node.
  • FQDN fully qualified domain name
  • the system further includes the retrieving unit configured to retrieve, 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.
  • DNS Domain Name System
  • the system includes a determining unit, configured to, determine, 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 system includes a routing unit, configured to route 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 system further includes a routing unit, configured to route the received SIP packet to a subsequent available IMS node, when the status of the at least one IMS node is determined as blacklisted.
  • a User Equipment includes one or more primary processors and a memory.
  • the one or more primary processors are coupled with one or more processors.
  • the memory stores instructions which when executed by the one or more primary processors causes the UE to transmit Session Initiation Protocol (SIP) packets to a network in order to avail one or more services.
  • SIP Session Initiation Protocol
  • FIG. 1 is an exemplary block diagram of an environment of handling Session Initiation Protocol (SIP) packets distribution in a network, according to one or more embodiments of the present disclosure
  • SIP Session Initiation Protocol
  • FIG. 2 is an exemplary block diagram of a system of handling the SIP packets distribution in the network, according to one or more embodiments of the present disclosure
  • FIG. 3 is a schematic representation of the present system of FIG. 1 workflow, according to one or more embodiments of the present disclosure
  • FIG. 4 illustrates an exemplary block diagram of workflow between one or more processors, and a first pool, according to one or more embodiments of the present disclosure
  • FIG. 5 is a flow diagram illustrating a method of handling SIP packets distribution in the network, according to one or more embodiments of the present disclosure.
  • the system and method are configured to obtain FQDN (Fully Qualified Domain Name) corresponding to the IP Multimedia Subsystem (IMS) nodes of the IP network. Based on the obtained FQDNs, the system determines IP addresses corresponding to the IMS nodes and subsequently, based on the IP addresses, determines the health of the IMS nodes as either available or blacklisted. Accordingly, when the system has to send one or more Session Initiation Protocol (SIP) packets to the IMS node in an IMS network, the system is able to efficiently handle the SIP packet as per the health of the destination IMS node.
  • SIP Session Initiation Protocol
  • FIG. 1 illustrates an exemplary block diagram of an environment 100 of handling Session Initiation Protocol (SIP) packets distribution in a network 105, according to one or more embodiments of the present disclosure.
  • the environment 100 includes the network 105, a User Equipment (UE) 110, a server 115, a system 120, and at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node 125.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the UE 110 aids a user to interact with the system 120 for transmitting Session Initiation Protocol (SIP) packets to the network 105 in order to avail one or more services.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • IMS node at least one IMS node and “plurality of IMS nodes” are used interchangeably hereinafter, without limiting the scope of the invention.
  • SIP packet could be referred to as “one or more SIP packets”, hereinafter, without limiting the scope of the invention.
  • Each of the UE 110 from the one or more UEs 110 is configured to connect to the server 115 via the network 105.
  • each of the first UE 110a, the second UE 110b, and the third UE 110c 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.
  • VR virtual reality
  • AR augmented reality
  • each of the first UE 110a, the second UE 110b, and the third UE 110c is configured to facilitate the transmission of a request via the network 105 for the purpose of availing a variety of services.
  • the scope of said services is inclusive of, but not limited to, engaging with the server 115 for the purpose of submitting a request thereto and transmitting SIP packets to the network 105, all aforementioned activities being conducted over the network 105.
  • This configuration enables a streamlined and efficient interaction between the UE 110 and the network resources, thereby enhancing the utility and performance of the network 105 in providing said services.
  • the network 105 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.
  • PSTN Public-Switched Telephone Network
  • the network 105 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.
  • 3G Third Generation
  • 4G Fourth Generation
  • 5G Fifth Generation
  • 6G Sixth Generation
  • NR New Radio
  • NB-IoT Narrow Band Internet of Things
  • OF-RAN Open Radio Access Network
  • the network 105 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 105 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.
  • PSTN Public- Switched Telephone Network
  • the environment 100 includes the server 115 accessible via the network 105.
  • the server 115 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.
  • 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 defence facility side, or any other facility that provides service.
  • the environment 100 further includes the at least one IMS node 125 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the network 105.
  • the at least one IMS node 125 in the context of telecommunications and networking, refers to an element within an IP Multimedia Subsystem (IMS) architecture.
  • IMS IP Multimedia Subsystem
  • the at least one IMS node 125 is a framework for delivering multimedia and communication services over IP networks, including voice, video, messaging, and data services.
  • the at least one IMS node 125 works together to provide these services in a standardized and interoperable manner.
  • the at least one IMS node 125 includes an Application Server (AS) node 130, and a Media Gateway Control Function (MGCF) node 135.
  • the AS node 130 refers to a component in a network architecture that is responsible for running and managing applications, services, and processes.
  • the AS node 130 typically provides a platform where applications can be deployed, executed, and accessed by clients or users over the network 105.
  • the MGCF node 135 is a key component in telecommunications networks, specifically in the context of Voice over Internet Protocol (VoIP) and the IMS architectures.
  • the MGCF node 135 is responsible for controlling the flow of media (voice, video, data) between circuit-switched networks (such as traditional telephone networks) and packet-switched networks (such as IP networks).
  • the environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the network 105.
  • the system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity. However, for the purpose of description, the system 120 is described as an integral part of the server 115, without deviating from the scope of the present disclosure.
  • FIG. 2 illustrates an exemplary block diagram of the system 120 of handling SIP packets distribution in the network 105, according to one or more embodiments of the present disclosure.
  • the system 120 includes one or more processors 205, a memory 210, a communication interface 215, and a node database 245.
  • the one or more processors 205 hereinafter referred to as the processor 205 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.
  • the system 120 includes one processor 205.
  • the system 120 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
  • the information related to the request pertaining to handling SIP packets distribution is provided or stored in the memory 210.
  • the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210.
  • the memory 210 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 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROMs, FLASH memory, unalterable memory, and the like.
  • the information related to the request pertaining to handling the SIP packets distribution is rendered on the communication interface 215.
  • the communication interface 215 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), and the like.
  • GUI Graphical User Interface
  • CLI Command Line Interface
  • the communication interface 215 facilitates communication of the system 120.
  • the communication interface 215 provides a communication pathway for one or more components of the system 120. Examples of the one or more components include, but are not limited to, the UE 110 and the node database 245.
  • the node database 245 is configured to store the request pertaining to handling the SIP packets distribution which is transmitted by the UE 110. Further, the node database 245 provides structured storage, support for complex queries, and enables efficient data retrieval and analysis.
  • the node database 245 is one of, but is not limited to, one of 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.
  • NoSQL No-Structured Query Language
  • the processor 205 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 205.
  • programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions.
  • the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205.
  • the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource.
  • the processor 205 may be implemented by electronic circuitry.
  • the processor 205 includes a transceiver 220, a retrieving unit 225, a determining unit 230, a whitelisting unit 235 and a routing unit 240 communicably coupled to each other for handling the SIP packets distribution in the network 105.
  • the transceiver 220, the retrieving unit 225, the determining unit 230, the whitelisting unit 235, and the routing unit 240 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205.
  • programming for the processor 205 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.
  • the memory 210 may store instructions that, when executed by the processing resource, implement the processor.
  • the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource.
  • the processor 205 may be implemented by electronic circuitry.
  • the transceiver 220 is configured to receive the one or more SIP packets addressed to the at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node 125 from the UE 110.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the one or more Session Initiation Protocol (SIP) is a signaling protocol that enables a Voice Over Internet Protocol (VoIP) by defining the messages sent between endpoints and managing the actual elements of a call.
  • VoIP Voice Over Internet Protocol
  • the SIP packets refer to the messages exchanged between the UE 110 or applications in a SIP- based communication system.
  • the one or more SIP packets are used to initiate, modify, and terminate communication sessions between users.
  • the at least one IMS node 125 is a network element that implements the IP Multimedia Subsystem architecture, which is a standardized framework for delivering multimedia services over IP networks.
  • the at least one IMS node 125 facilitates the integration of various communication services, including voice, video, messaging, and presence, over IPbased networks.
  • the retrieving unit 225 On receiving the one or more SIP packets addressed to the at least one IMS node 125 from the UE 110, the retrieving unit 225 is configured to retrieve from the node database 245, a relevant Fully Qualified Domain Name (FQDN) associated with the at least one IMS node 125.
  • the relevant FQDN is referred to as a complete and unique address that specifies the exact location of a specific node within an IMS network.
  • the node database 245 includes a list of FQDNs corresponding to the at least one IMS node 125.
  • the at least one IMS node 125 includes, but not limited to, a first IMS node, and a second IMS node.
  • each FQDN corresponds to the at least one IMS node 125, which is the Application Server (AS) node 130, the Media Gateway Control Function (MGCF) node 135, or any other node within the IMS system.
  • the FQDNs serve as identifiers for the nodes and are used for various purposes, such as routing, addressing, and establishing connections within the IMS network.
  • the retrieving unit 225 is configured to 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.
  • DNS Domain Name System
  • the DNS unit refers to a specific configuration related to DNS servers or services.
  • the DNS unit is a distributed system used to translate domain names into IP addresses to communicate over the network 105.
  • the DNS unit might indicate a certain capacity, performance level, or configuration aspect of the server 115 or the system 120.
  • the retrieving unit 225 when the retrieving unit 225 initiates the resolution process, it sends DNS queries to the server 115, providing the FQDNs of the at least one IMS node 125. The server 115 then looks up the IP addresses associated with each FQDN and returns them to the system 120. By obtaining the IP addresses through DNS resolution, the retrieving unit 225 establishes connections with the at least one IMS node 125 using the appropriate IP addresses. The retrieving unit 225 allows for communication and interaction between the system 120 and the at least one IMS node 125 within the system 120.
  • the retrieved one or more IP addresses are stored in the node database 245.
  • the retrieving unit 225 resolves the FQDNs of the IMS nodes, it obtains the one or more IP addresses for each node.
  • the one or more IP addresses are stored in the node database 245.
  • the retrieving unit 225 establishes connections with the IMS nodes using the stored IP addresses, enabling efficient communication and interaction within the system 120.
  • the determining unit 230 Upon storing the retrieved one or more IP addresses in the node database 245, the determining unit 230 is 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. [0056] Accordingly, in one embodiment, 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.
  • the predefined threshold refers to a specific value or criterion set in advance that serves as a boundary or limit for making decisions or taking actions.
  • the predefined threshold includes 100 SIP packets on the at least one IMS node 125.
  • the at least one IMS node 125 receives 101 SIP packets.
  • the system 120 is configured to blacklist the AS node 130 for the predetermined time interval.
  • 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 the pre-defined time interval.
  • the predetermined time interval may range from seconds to hours.
  • the system 120 categorizes the AS node 130 as available, without performing any status check.
  • the at least one IMS node 125 has more than one corresponding IP addresses and a first IP address is blacklisted, then all the remaining IP addresses for the at least one IMS node 125 are checked. Accordingly, the status of the at least one IMS node 125 is determined based on the availability of the corresponding IP addresses. In an example, if even one corresponding IP address is available, the status of the at least one IMS node 125 is stored as available. In case none of the IP addresses of the at least one IMS node 125 is available, the status of the at least one IMS node 125 is categorized as blacklisted.
  • the determining unit 230 is configured to determine 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 the pre-defined time interval. For instance, in case the at least one IMS node 125 is the AS node 130 the system 120 blacklists the AS node 130 for the predetermined time interval. In an exemplary embodiment, the predetermined time interval may range from seconds to hours. On completion of the predetermined time interval, the system 120 categorizes the AS node 130 as available, without performing any status check.
  • 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.
  • the pre-defined threshold includes 500 SIP packets on the AS node 130.
  • the system 120 is configured to blacklist the AS node 130 for the predetermined time interval. On completion of the predetermined time interval, the system 120 categorizes the AS node 130 as available, without performing any status check.
  • the determining unit 230 is configured to determine the subsequent available IMS node by checking at a pool including the at least one blacklisted IMS node.
  • the pool includes, but not limited to, a first pool, a second pool, and the like.
  • the pool refers to the plurality of IMS nodes that share similar characteristics or functionalities.
  • the determining unit 230 is configured to determine the subsequent available IMS node by 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 at least one IMS node 125 is below the pre-defined threshold within the pre-defined time interval.
  • the whitelisting unit 235 of the system 120 is configured to whitelist the at least one blacklisted IMS node subsequent to the predefined time interval based on the type of the at least one IMS node 125.
  • the type of the at least one IMS node 125 includes at least one of, a plurality of Application Server (AS) nodes 130 or a plurality of Media Gateway Control Function (MGCF) node 135.
  • the plurality of AS nodes 130 includes, but not limited to an AS node 130-1, and an AS node 130-2.
  • the blacklisted node When the blacklisted node starts responding to the at least one IMS node 125, it will be whitelisted again.
  • whitelisting unit 235 of the at least one IMS node 125 is done only after ensuring it is in an operational state. In this whitelisting of non-operational nodes is averted and accordingly related failures are avoided, resulting in network resource optimization and reduced overheads.
  • the routing unit 240 is configured to route the received SIP packets to the at least one IMS node 125 when the status of at least one IMS node 125 is determined as available. If the predefined threshold is not reached, the status of the at least one IMS node 125 is categorized as available.
  • the routing unit 240 is configured to route the received SIP packets to the subsequent available IMS node, when the status of the at least one IMS node 125 is determined as blacklisted. If the predefined threshold is reached, the status of the at least one IMS node 125 is categorized as blacklisted. In an example, the routing unit 240 is configured to route the received SIP packets to the second IMS node from the same pool as the first IMS node, when the first IMS node is determined to be not available. The system 120 selects the second IMS node from the same pool as the first IMS node and routes the SIP packets to the second IMS node for ensuring continuity of communication and exchange information to the UE 110.
  • a routing mechanism helps maintain the flow of communication and prevents disruptions caused by the unavailability of the first IMS node. It allows for efficient utilization of resources within the at least one IMS node 125 and ensures that the intended actions or requests are carried out by the alternative node from the same pool. By doing so, the system 120 receives any request sent to unreachable or errorresponding node, which can be easily routed to another node, which saves response time. When a failure response is received for a particular node, the particular node can retry the request with a different node under the same pool based on failure response and maintains flexibility in managing access control.
  • FIG. 3 is a schematic representation of the system 120 in which various entities operations are explained, according to one or more embodiments of the present
  • FIG. 3 describes the system 120 for handling SIP packets distribution in the network 105. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
  • the first UE 110a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, personal computers, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity.
  • the scope of the first UE 110a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications.
  • This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms.
  • the first UE 110a can be associated with multiple users. Each UE 110 is communicatively coupled with the processor 205 via the network 105.
  • the first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.
  • the one or more primary processors 305 are coupled with a memory unit 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to transmit the SIP packets to the network 105 in order to avail one or more services.
  • the one or more primary processors 305 within the UE 110 are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor’s capability to handle the SIP packets distribution.
  • the one or more processors 205 of the system 120 is configured to receive the one or more SIP packets addressed to at least one IMS node 125 from the UE 110, retrieve from the node database 245, the relevant 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 the DNS unit, determine the status of the at least one IMS node 125 as one of, blacklisted and available, 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 further route the received SIP packet to the subsequent available IMS node, when the status of the at least one IMS node 125 is determined as blacklisted.
  • the system 120 includes the one or more processors 205, the memory 210, and the communication interface 215.
  • the operations and functions of the one or more processors 205, the memory 210, and the communication interface 215 are already explained in FIG. 2.
  • a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
  • the processor 205 includes the transceiver 220, the retrieving unit 225, the determining unit 230, and the routing unit 240.
  • the operations and functions of the transceiver 220, the retrieving unit 225, the determining unit 230, and the routing unit 240 are already explained in FIG. 2.
  • a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
  • the limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
  • FIG. 3 should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
  • FIG. 4 illustrates an exemplary block diagram of workflow between the one or more processors 205 of the system 120, and the first pool, according to one or more embodiments of the present disclosure. It is to be noted that the embodiment with respect to FIG. 4 will be explained with respect to the first pool for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
  • the system 120 includes the UE 110.
  • the system 120 can monitor traffic and operations related to the first pool of at least one IMS node, for example, Application Server (AS) nodes 130.
  • AS Application Server
  • the system 120 is connected to the node database 245.
  • the IP addresses for all the AS nodes 130 are stored.
  • the node database 245 also includes the status of each of the AS node 130. The status may be either “available” if the AS node 130 is available or “blacklisted” in case the AS node 130 is not available.
  • the system 120 receives the one or more SIP packets from the UE 110 which is directed towards the AS node 130-1. On receiving the one or more SIP packets, the system 120 determines the availability of the AS node 130-1 based on the status of the AS node 130 as stored in the node database 245. In the event that the AS nodes 130-1 is blacklisted, the system 120 is configured to route the SIP packets to another AS node, for example, the AS node 130-2, from the same pool, i.e., Pool 1. Thus, efficient handling of the SIP packet is ensured.
  • the other AS or IMS node is selected from the same pool based on predefined process, such as weightage or priority-based process. In another embodiment, the selection of the other IMS nodes is based on logic or selection defined by an admin.
  • the system 120 is provisioned to allow the admin to selectively operate the IP addresses of the at least one IMS node 125. For instance, let’s consider that the AS nodes 130-1 of pool 1 have at least four (‘4’) IP addresses.
  • the system 120 provides the admin with an option of making one or more IP addresses act as non-functional.
  • the network traffic is directed to specific IP addresses, as desired by the admin.
  • FIG. 5 is a flow diagram illustrating a method 500 of handling SIP packets distribution in the network 105, 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.
  • the method 500 includes the step of receiving the one or more SIP packets addressed to the at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node 125 from the UE 110 by the transceiver 220.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the method 500 includes the step of retrieving from the node database 245, the relevant Fully Qualified Domain Name (FQDN) associated with the at least one IMS node 125 by the retrieving unit 225 based on receiving the one or more SIP packets addressed to the at least one IMS node 125 from the UE 110.
  • the FQDNs serve as identifiers for the nodes and are used for various purposes, such as routing, addressing, and establishing connections within the IMS network.
  • the method 500 includes the step of retrieving the one or more IP addresses pertaining to the retrieved FQDN associated with the at least one IMS node 125 from the DNS unit by the retrieving unit 225.
  • the method 500 includes the step of determining the status of the at least one IMS node 125 as one of, blacklisted and available, based on comparing the determined number of failures of the one or more IP addresses associated with the at least one IMS node 125 with the pre-defined threshold by the determining unit 230.
  • the method 500 includes the step of routing the received SIP packets to the at least one IMS node 125 when the status of at least one IMS node 125 is determined as available by the routing unit 240. If the threshold is not reached, the status of the at least one IMS node 125 is categorized as available.
  • the method 500 includes the step of routing the received SIP packet to the subsequent available IMS node by the routing unit 240, when the status of at least one IMS node 125 is determined as blacklisted. If the threshold is reached, the status of the at least one IMS node 125 is categorized as blacklisted.
  • the routing unit 240 is configured to route the received SIP packet to the second IMS node from the same pool as the first IMS node, when the first IMS node is determined to be not available.
  • the routing mechanism helps maintain the flow of communication and prevents disruptions caused by the unavailability of the first IMS node. It allows for efficient utilization of resources within the at least one IMS node 125 and ensures that the intended actions or requests are carried out by the alternative node from the same pool. By doing so, the method 500 receives any request sent to unreachable or errorresponding node can be easily routed to another node, which saves response time. When a failure response is received for a particular node, the particular node can retry the request with a different node under the same pool based on failure response and maintains flexibility in managing access control.
  • the present invention discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions.
  • the computer-readable instructions are executed by a processor 205.
  • the processor 205 is configured to receive the one or more SIP packets addressed to at least one Internet Protocol (IP) Multimedia Subsystem (IMS) node 125 from a User Equipment (UE) 110.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • UE User Equipment
  • the processor 205 is configured to retrieve from a node database 245, a relevant fully qualified domain name (FQDN) associated with the at least one IMS node 125.
  • the processor 205 is further configured to 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.
  • DNS Domain Name System
  • the processor 205 is further 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.
  • the processor 205 is configured to route the received SIP packet to the at least one IMS node 125 when the status of at least one IMS node 125 is determined as available.
  • the processor 205 is further configured to 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.
  • the present disclosure incorporates technical advancement of handling Session Initiation Protocol (SIP) packets distribution in the network for retrieving all IP addresses corresponding to the IMS node. This ensures that the system has a comprehensive understanding of the available IP addresses associated with each IMS node. By considering all IP addresses, the accuracy of status determination increases. This allows for more precise assessment of the availability of IMS nodes, enabling packets to be handled more appropriately based on their accurate health status.
  • SIP Session Initiation Protocol
  • the present invention offers significant advantages by retrieving all IP addresses corresponding to the IMS node.
  • This approach enhances the accuracy of health determination as the system considers the health status of all the IP addresses associated with the node, rather than relying on just one IP address.
  • the system gains a more comprehensive understanding of the node's availability and makes more informed decisions regarding packet handling.
  • This increased accuracy in health determination ensures that packets are handled appropriately based on the precise status of the IMS node. Consequently, the system can optimize resource allocation, improve network efficiency, and enhance overall performance.
  • Another advantage of the invention is the categorization of IMS node health as either "available” or “blacklisted”.
  • the status of the at least one node is determined based on predefined conditions, such as the number of failures within a given time interval.
  • This proactive monitoring and categorization of health status allows for efficient management of IMS nodes. It enables the system to make informed decisions regarding routing, load balancing, and resource allocation within the network.
  • 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.
  • At least one IMS node- 125 At least one IMS node- 125;
  • Routing unit- 240
  • One or more primary processors - 305 are provided.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation porte sur un système (120) et un procédé (500) de gestion de distribution de paquets de protocole d'ouverture de session (SIP) dans un réseau. Le procédé comprend l'étape consistant à recevoir un ou plusieurs paquets SIP adressés à au moins un nœud de sous-système multimédia sur IP (IMS) depuis un équipement utilisateur (UE) (110). Le procédé comprend l'étape consistant à récupérer un nom de domaine complet pertinent (FQDN) associé au ou aux nœuds IMS et à une ou plusieurs adresses IP. Le procédé comprend l'étape consistant à déterminer un état du ou des nœuds IMS parmi des nœuds noirs et disponibles, sur la base de la comparaison d'un nombre déterminé de défaillances de la ou des adresses IP. Le procédé comprend l'étape consistant à acheminer le paquet SIP reçu vers le ou les nœuds IMS lorsque l'état du ou des nœuds IMS est déterminé comme disponible ou sur liste noire.
PCT/IN2024/050955 2023-07-03 2024-06-27 Procédé et système de gestion de distribution de paquets de protocole d'initiation de session dans un réseau Ceased WO2025008968A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321044343 2023-07-03
IN202321044343 2023-07-03

Publications (1)

Publication Number Publication Date
WO2025008968A1 true WO2025008968A1 (fr) 2025-01-09

Family

ID=94171820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050955 Ceased WO2025008968A1 (fr) 2023-07-03 2024-06-27 Procédé et système de gestion de distribution de paquets de protocole d'initiation de session dans un réseau

Country Status (1)

Country Link
WO (1) WO2025008968A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014134220A1 (fr) * 2013-03-01 2014-09-04 T-Mobile Usa, Inc. Systèmes et procédés de commutation pour acheminer des appels d'urgence
US20210044629A1 (en) * 2018-03-12 2021-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Quick Determination of the availability of a communication path between UEs and IMS

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014134220A1 (fr) * 2013-03-01 2014-09-04 T-Mobile Usa, Inc. Systèmes et procédés de commutation pour acheminer des appels d'urgence
US20210044629A1 (en) * 2018-03-12 2021-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Quick Determination of the availability of a communication path between UEs and IMS

Similar Documents

Publication Publication Date Title
US10063599B2 (en) Controlling registration floods in VOIP networks via DNS
US10257115B2 (en) Cloud-based service resource provisioning based on network characteristics
CN108696581B (zh) 分布式信息的缓存方法、装置、计算机设备以及存储介质
CN111357257B (zh) 用于对媒体服务器实例进行负载均衡的系统和方法
CN112437006B (zh) 基于api网关的请求控制方法、装置、电子设备和存储介质
US12316716B2 (en) Network coordination between proxy servers
US10715608B2 (en) Automatic server cluster discovery
US20220255813A1 (en) System and method to correlate end user experience with location
CN118118556B (zh) 基于用户请求的云手机调度方法、装置、设备及存储介质
US9191359B2 (en) Techniques for VoIP provider interconnection over the internet using a shared subscriber contact identifier translation service
US9813317B2 (en) Self-localizing data distribution network
CN116107760A (zh) 一种负载均衡方法、装置、设备及介质
WO2025008968A1 (fr) Procédé et système de gestion de distribution de paquets de protocole d'initiation de session dans un réseau
US11595471B1 (en) Method and system for electing a master in a cloud based distributed system using a serverless framework
US10958580B2 (en) System and method of performing load balancing over an overlay network
US10277421B2 (en) Route lookup resolution
US8743688B2 (en) Method and apparatus for dynamically controlling internet protocol packet handling in a voice over internet protocol network
WO2025013022A1 (fr) Procédé et système de surveillance d'une ou de plusieurs alarmes dans un réseau
WO2025052482A1 (fr) Procédé et système de gestion de trafic d'interface de programmation d'application (api) dans un réseau de communication
WO2025017654A1 (fr) Procédé et système de configuration d'un ou de plusieurs attributs de nœuds dans un réseau
WO2025013003A1 (fr) Système et procédé d'enrichissement d'alarmes de réseau
WO2025008970A1 (fr) Système et procédé de mise en cache de réponses dns pour une détection d'application
WO2025012949A1 (fr) Système et procédé de routage de message basé sur un supi dans des réseaux de télécommunication
WO2025022436A1 (fr) Procédé et système de surveillance de fonctions de réseau dans un réseau
WO2025017662A1 (fr) Procédé et système de gestion de défaillance dans réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24835689

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024835689

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024835689

Country of ref document: EP

Effective date: 20260203