Remote Server Communication History Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of mobile communication devices face challenges in accessing and viewing comprehensive communication history information, including events from other users and devices, leading to a lack of awareness about prior interactions with other parties.

Innovation Solution

A system and method that allow information about communication events from one mobile device to be stored and shared with another, enabling retrieval and transmission of prior communication events between users and devices through a remote server, thereby providing an integrated view of communication history across multiple users and devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If communication history is stored only on individual mobile devices, then each device can access its own communication events, but users cannot view communication events from other users and devices

Engineering Contradiction:
Improvecommunication history informationVSAvoidsystem architecture
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges communication history data from multiple mobile devices into a centralized remote server database. The server aggregates communication events from various users and devices, allowing any user to query and view comprehensive communication history that spans across the entire system, not just their own device.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The remote server acts as an intermediary between mobile devices and communication history data. Instead of devices directly sharing data with each other, they communicate through the server which stores, manages, and distributes communication history information, simplifying the data sharing architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a centralized system stores all communication history, then users can access comprehensive communication events, but system complexity and data management burden increase

Engineering Contradiction:
Improveaccess to communication historyVSAvoiddata management system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The remote server provides universal access to communication history for all users and devices in the system. A single database infrastructure serves multiple functions: storing communication events, enabling queries from any device, supporting multiple users, and providing a unified interface for data retrieval across the entire network.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If communication events are distributed across multiple devices, then data can be stored locally, but users lack awareness of prior interactions with other parties

Engineering Contradiction:
Improvedata availabilityVSAvoidprior communication events
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary action by pre-storing communication history data on the remote server as events occur. This proactive data collection and centralization ensures that when users need to query communication history, the information is already available and organized, eliminating the need for real-time data gathering or complex distributed queries.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8712387B2Systems and methods to provide communication history for communication devices
Publication Date: 2014.04.29 SAP SE
  • US8712387B2 patent drawing
  • US8712387B2 patent drawing
  • US8712387B2 patent drawing

AI summary

According to some embodiments, a remote server may receive, from a first communication device associated with a first user, information about a first communication event between the first user and another party. The remote server may store the information about the first communication event. The remote server may also receive, from a second communication device associated with a second user, a request associated with the other party. Responsive to the request, the remote server may retrieve and transmit information about the first communication event to the second communication device.