EVVM Server Notification for Multi-Device Message Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional multimedia content retrieval systems, such as Enhanced Visual Voice Mail (EVVM) technology, face issues in multi-device environments, including message duplication, flag information loss, and attachment failure due to inconsistent message IDs across devices.
Innovation Solution
Implementing a notification system where the server sends a message with an old identification value (UID) and a new identification value (UID) to devices, along with optional additional information, to synchronize and update message states, ensuring seamless content retrieval and processing across multiple devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If message synchronization is implemented across multiple devices using conventional methods, then message retrieval is enabled on multiple devices, but message duplication and flag information loss occur due to inconsistent message IDs
Solution Approach 1:
The server sends a notification to all devices before performing message transformation operations such as transcription or deletion. This preliminary action includes providing old and new message IDs, allowing devices to proactively update their local state and avoid inconsistencies like message duplication or flag information loss when subsequent operations are performed.
Solution Approach 2:
The system implements a feedback mechanism where the server notifies all user devices about message state changes by sending notifications containing old and new message identification values. This feedback loop ensures that all devices remain synchronized with the server's message state, resolving the contradiction between multi-device accessibility and message consistency.
2Productivity
If message transformation operations are performed on the server, then message content is updated or converted, but flag information is lost due to lack of device awareness
Solution Approach 1:
Before the server performs message transformation operations such as transcription or deletion, it sends a notification to all devices with the old and new message IDs. This preliminary notification allows devices to preserve and transfer flag information from the old message to the new message, preventing information loss while maintaining processing efficiency.
Solution Approach 2:
The notification message acts as an intermediary carrier that transmits critical information (old message ID, new message ID) from the server to all devices. This intermediary mechanism ensures that flag information is properly associated with transformed messages across multiple devices without being lost during server-side operations.
3Ease of operation
If attachment operations reference old message IDs, then attachments can be sent, but attachment failures occur when message IDs have changed
Solution Approach 1:
The server sends a notification to all devices before performing message transformation operations. This notification includes the old and new message IDs, allowing devices to update their local message databases proactively. As a result, when users subsequently perform attachment operations, the correct new message IDs are already available, preventing attachment failures.
Solution Approach 2:
The notification mechanism provides feedback to all devices about message ID changes before they occur. This feedback ensures that devices have up-to-date message identification values, allowing attachment operations to reference correct message IDs and succeed reliably across multiple devices.
Data Source
AI summary
In order to support Enhanced Visual Voice Mail (EVVM) technology in OMA standards that allow for voicemail retrieval via a plurality of devices for a single user, a method and apparatus for generating a notification that includes an old identification value (UID) for an old message, a new identification value (UID) for a new message, and optional additional information related to the notification; and transmitting, independent of an IMAP synchronization procedure with a first device, said notification to at least one other device that is different from the first device, has been conceived.