Telephony Server Call Management via Relative Location Indication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current VoIP systems face challenges in managing service requests from nomadic softphone terminals, particularly in determining their location for call management, which affects service logic and licensing costs, and lacks dynamic location provision capabilities, leading to inefficiencies in call authorization and billing.
Innovation Solution
A method for managing service requests in a telephony application server that analyzes relative location indications within SIP protocol messages to authorize or reject calls, using a shared public identity for terminals connected via a connection box or in nomadic situations, allowing for dynamic call management and reduced licensing costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If softphone terminals share a common public identity with traditional terminals, then service provider resources are reduced and billing is simplified, but call management becomes complex due to inability to distinguish terminal locations
Solution Approach 1:
The patent introduces a location indication field as an intermediary element within SIP signaling messages. This field acts as a mediator that carries terminal location information (home or nomadic) through the existing SIP protocol infrastructure, enabling the application server to distinguish terminal locations without requiring new complex identification systems. The location indication serves as a simple yet effective mediator that resolves the conflict between using shared public identities and maintaining call management control.
2Ease of manufacture
If static location information is provisioned in the application server, then implementation is simple, but dynamic location updates are impossible leading to inefficiencies in call authorization
Solution Approach 1:
The patent transforms the static location information model into a dynamic one by having the terminal actively provide its current location indication through SIP signaling messages. Instead of relying on pre-provisioned static data that cannot be updated, the system now receives real-time location information from the terminal itself, allowing the application server to dynamically adjust call authorization and service logic based on the terminal's current state (home or nomadic).
Solution Approach 2:
The terminal provides feedback about its location status by including the location indication field in its SIP signaling messages to the application server. This feedback mechanism allows the server to continuously know the terminal's location state without requiring complex tracking infrastructure, enabling dynamic call management decisions based on current terminal conditions.
3Measurement precision
If the application server analyzes service requests to determine terminal location, then call management accuracy improves, but processing time and complexity increase
Solution Approach 1:
The terminal prepares the location indication information in advance and includes it proactively in its SIP signaling messages before the application server needs to make call management decisions. This preliminary action eliminates the need for the server to perform additional queries or analysis to determine terminal location, as the information is already available when the service request is received, thus maintaining high processing speed while ensuring accurate call management.
Data Source
Figure 1~6
Figure 2
Figure 3
AI summary
The invention relates in particular to the management of services in a telephony application server connected to a communication network, a connection box being connected to said network, a mobile terminal being connected to said network directly or via said connection box, said terminal comprising a public identity linked to said connection box and shared with at least one other terminal linked to said connection box, distinct from said terminal, referred to as the first terminal. After receiving a service request from said first terminal, including a relative location indication of said first terminal, said request is analyzed according to a predetermined logic based on a relative location indication. In response to the analysis step, said requested service is either rejected (504) or implemented (520).