Residential Gateway SIP Call Setup via Identity Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current residential gateways face inefficiencies in managing multiline connections and call setup processes for SIP terminals, leading to excessive signaling, complex network operations, and performance issues due to the need for extensive topology storage and unnecessary message exchanges.
Innovation Solution
A method and system for a residential gateway that simplifies call setup by registering public identities with the gateway's network address, allowing a single call setup request to be sent to the gateway, which then filters and forwards messages to connected IP communication entities, reducing network complexity and processing overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the gateway performs translation between SIP signaling and terminal signaling for non-IP terminals, then compatibility with various terminal types is improved, but device complexity increases
Solution Approach 1:
The patent introduces an IP terminal as an intermediary component that bridges non-IP terminals and the SIP network. The IP terminal performs the signaling translation and protocol conversion, while the gateway itself remains relatively simple. This mediator approach allows the system to support multiple terminal types without significantly increasing gateway complexity.
Solution Approach 2:
The patent segments the call handling functionality by introducing separate IP terminals that manage specific terminal types. Instead of concentrating all translation and adaptation functions in the gateway, the system divides responsibilities: the gateway handles core SIP routing, while IP terminals handle terminal-specific protocol translation. This segmentation reduces gateway complexity while maintaining versatility.
2Device complexity
If the gateway acts as a simple router for IP terminals, then device complexity is reduced, but adaptability to handle different terminal configurations decreases
Solution Approach 1:
The patent implements self-service mechanisms where IP terminals automatically register their capabilities and supported terminal types with the gateway. The gateway maintains a registration database that stores information about each IP terminal's functionality. This allows the simple gateway to adapt to different terminal configurations without requiring complex built-in translation capabilities, as the adaptation information is provided autonomously by the IP terminals themselves.
3Ease of operation
If multiple terminals share the same public identity, then ease of operation is improved, but network load increases due to forking and multiple message exchanges
Solution Approach 1:
The patent implements preliminary action by having IP terminals pre-register their capabilities, supported terminal types, and associated public identities with the gateway before any call attempts. The gateway stores this information in a registration database in advance. When a call is initiated to a shared public identity, the gateway can efficiently query the pre-stored registration information and forward the call directly to the appropriate IP terminal, avoiding the need for real-time forking and multiple message exchanges that would otherwise increase network load.
Data Source
AI summary
The invention concerns a method for connection to IP communication entities (Ex,pu,, Ey,pu) via a residential gateway (PZ). It consists in registering (A) the public identity (pu) of each connected terminal associated with the network address (z) of the residential gateway, so that any message should be addressed to said residential gateway (Pz) and in transferring (B) said message to all the IP communication entities connected to the residential gateway (Pz), thus permitting each of the latter to filter (C) the message and to determine whether the message is addressed to a public identity which is assigned thereto. The invention is applicable to IP terminals managed in accordance with SIP or H323 protocol.