Smart Synchronization for IMS Device Event Awareness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IP Multimedia Subsystem (IMS) environments, related devices sharing the same communication address are not aware of communications received by each other, leading to duplication and missed communication events due to the lack of access to communication notifications across network identities within an implicit registration set.
Innovation Solution
Implementing a system where related devices compare data items from communication notifications with their local activity databases to determine if a communication event has already been logged, allowing them to avoid duplications and synchronize missed events by updating their databases with notifications received while offline.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If communication notifications are sent to all network identities in a registration set, then all devices receive communication events, but devices cannot distinguish which communications are received by which specific network identity, leading to duplication and lack of awareness
Solution Approach 1:
The patent segments communication notifications by including specific network identity identifiers within each notification. This allows devices to distinguish which communications are received by which network identity, enabling precise tracking and awareness without requiring complex centralized management. Each notification is divided into identifiable components including the network identity that received the communication.
Solution Approach 2:
The patent implements a feedback mechanism where devices compare received communication notifications against their local activity databases. This feedback loop enables devices to determine whether they have already logged a communication event, preventing duplication while maintaining awareness across all network identities. The comparison process provides continuous feedback about the state of communication event logging.
2Reliability
If devices independently log communication events in their local activity databases, then each device maintains its own record, but devices miss communication events that occur when they are offline or unavailable
Solution Approach 1:
The patent prepares communication notifications in advance and stores them in the activity database before devices need to access them. When devices come online after being offline, the notifications are already prepared and waiting, eliminating synchronization delays. This preliminary action ensures that communication events are not lost during offline periods.
Solution Approach 2:
The patent enables devices to autonomously synchronize their local activity databases by comparing received communication notifications with their existing records. Devices independently determine what events they have missed and log them without requiring manual intervention or complex centralized coordination. This self-service approach maintains reliability while minimizing synchronization delays.
3Loss of information
If devices synchronize their activity databases frequently, then communication events are kept up-to-date, but network bandwidth and device energy are consumed
Solution Approach 1:
The patent implements periodic synchronization where devices compare their activity databases at scheduled intervals rather than continuously. This periodic action maintains database synchronization while significantly reducing network bandwidth consumption and device energy usage compared to continuous synchronization approaches.
Solution Approach 2:
The patent changes the synchronization parameter from continuous to event-triggered or interval-based comparison. Devices compare their activity databases based on changes in communication patterns or at predetermined intervals, optimizing the balance between maintaining information accuracy and conserving energy and network resources.
Data Source
AI summary
Device and/or line event awareness and smart synchronization is described. In at least one example, a related device of a group of related devices may receive a communication notification representative of a communication event. Such communication notifications may enable event awareness for each of the devices in the group of related devices. In an example, the related device may compare data items (e.g., participants, timestamps, etc.) associated with the communication notification with data items associated with entries stored in a local data store. The entries may correspond to communication events associated with at least the related device. Based at least in part on comparing the data items, the related device may determine whether a new entry associated with the communication notification should be added to a local data store or the communication notification should be disregarded as a duplication.