Call Log Synchronization Across Multiple Devices via Server Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communication devices with a single Address of Record (AoR) often fail to synchronize call logs effectively across multiple associated devices, leading to inconsistencies and incomplete call logging experiences for users.

Innovation Solution

A system and method that synchronizes call logs across multiple communication devices by receiving and updating call log entries based on events, such as call status changes or device bridging, using a communication processor to fork requests and send updated log entries to all associated devices, ensuring each device has a unified call log.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If call logs are maintained separately on each communication device, then each device has its own call log, but the call logs are not synchronized across devices using the same AoR

Engineering Contradiction:
Improvecall log synchronizationVSAvoidcall log consistency
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

A server acts as an intermediary between multiple communication devices sharing the same AoR. The server receives call log entries from one device, processes them, and distributes synchronized call log information to all other devices associated with that AoR, ensuring consistency across the network without requiring direct peer-to-peer synchronization between devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements a feedback mechanism where call log updates are propagated back to all devices associated with the same AoR. When a call log entry is created or modified on one device, the server sends notifications and updated call log data to all other devices, ensuring they receive real-time feedback about changes to maintain synchronization.

Inventive Principle:
Principle #23Feedback

2Loss of information

If call logs are synchronized across all devices, then all devices have consistent call log information, but the system complexity increases

Engineering Contradiction:
Improvecall log consistencyVSAvoidsynchronization system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

By introducing a server as an intermediary, the synchronization complexity is centralized rather than distributed across all devices. The server handles the complex logic of receiving, processing, and distributing call log entries, while individual devices only need to communicate with the server, significantly reducing the complexity burden on each device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent merges the synchronization functionality into a centralized server component rather than implementing it in each device. This consolidation combines the complex synchronization logic, event processing, and data distribution functions into a single system, reducing overall system complexity while maintaining synchronization capabilities.

Inventive Principle:
Principle #5Merging (Combining)

3Loss of information

If detailed call log events are tracked and updated, then comprehensive call information is available, but the data processing and communication overhead increases

Engineering Contradiction:
Improvecall log completenessVSAvoiddata processing overhead
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts only the essential call log event information that needs to be synchronized, rather than transmitting complete call detail records. By identifying and extracting key events (call initiation, answer, end, missed calls) and their essential attributes, the system reduces data processing overhead while maintaining sufficient call log completeness for user needs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by tracking different types of call log events with appropriate levels of detail based on their significance. Critical events like missed calls and answered calls receive full tracking and synchronization, while less critical information may be summarized or updated less frequently, optimizing the balance between completeness and processing overhead.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10320971B2Call log management for multiple communication devices using the same address of record
Publication Date: 2019.06.11 AVAYA INC
  • US10320971B2 patent drawing
  • US10320971B2 patent drawing
  • US10320971B2 patent drawing

AI summary

A request to establish a communication is received. For example a request to establish a voice communication is received. The request can be forked to a plurality of communication devices based on an address of record. The address of record is an address associated with multiple communication devices of the same user. The request to establish the communication is stored in a call log entry in a call log. An event associated with the call log entry is received. The event is based information associated with a calling device or a communication device that is not initially part of an established communication session. In response to receiving the event associated with the call log entry, the call log entry in the call log is updated based on the event. The updated call log or the updated call log entry is the sent to the plurality of communication devices.