Unified Call Log Generation via SIP Signal Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telephony systems fail to provide a unified call log across multiple devices and network connections, leading to incomplete and unsynchronized call histories for users who receive and transfer calls across different devices and network types.
Innovation Solution
A system and method that allow user devices in a device group to generate and store unified call logs independently, detecting and logging intervening events like call transfers and network handovers, without the need for a dedicated call log server, by using client applications to compile and derive consistent call log information through signals like SIP and SS7 protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dedicated call log server is used to maintain unified call logs across multiple devices, then call log consistency and completeness are improved, but system complexity and deployment costs increase
Solution Approach 1:
The patent extracts the call log maintenance function from a centralized server and distributes it to individual user devices. Each device independently generates and maintains its own unified call log by processing received signals (SIP INVITE, 200 OK, BYE, transfer notifications, handover messages), eliminating the need for a dedicated call log server while maintaining call log consistency across the device group.
Solution Approach 2:
Each user device autonomously generates its own unified call log by processing signaling messages it receives during call operations. The device independently detects call events (answer, transfer, handover, termination) and maintains complete call records without requiring external server assistance, enabling self-service call log management across the device group.
2Device complexity
If call logs are maintained independently on each device without synchronization, then network complexity is reduced, but call log completeness and accuracy deteriorate
Solution Approach 1:
The patent implements a universal call log generation approach where each user device in the device group performs the same multi-functional operations: receiving SIP INVITE messages, detecting call answers, processing transfer notifications, detecting network handovers, and generating unified call logs. This universal implementation across all devices ensures complete and accurate call records while maintaining simple peer-to-peer network architecture.
Solution Approach 2:
The system uses feedback from signaling messages (SIP protocols, transfer notifications, handover messages) received during call operations to continuously update and maintain accurate call logs. Each device monitors incoming signals and adjusts its call log records accordingly, ensuring completeness and accuracy through continuous feedback processing without requiring centralized coordination.
3Measurement precision
If call information is synchronized across all devices in real-time, then call log accuracy is improved, but network bandwidth consumption and processing overhead increase
Solution Approach 1:
The patent segments the call log maintenance function so that each user device independently processes and generates its own unified call log based on the specific signaling messages it receives. Instead of one device generating a complete log and distributing it to all others, each device segments the work and autonomously maintains accurate call records, eliminating redundant data transmission and reducing network bandwidth consumption while preserving call log accuracy.
Data Source
AI summary
Systems and methods provide a unified call log for user devices in a device group. A user device receives an invite message for an incoming call and stores first call log information including a caller identifier based on the invite message. The user device receives a status message indicating that another user device has answered the incoming call and stores second call log information including a timestamp for the status message. The user device receives a call information message for a new line between the user device and a device associated with the caller telephone number, determines that the new line is a handover call associated with the incoming call, and stores third call log information for the new line. The user device determines that the handover call on the new line is ended and generates a call log entry including information from the incoming call and the handover call.