Companion Device Emergency Alert Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies for enabling second screen applications, such as those defined by ATSC 2.0 and HbbTV 2.0, are limited in providing efficient content information and message formats between primary and companion devices, leading to synchronization issues and inadequate interaction with audiovisual content.
Innovation Solution
A method for companion devices to receive and primary devices to provide emergency alert messages, including identifiers, dates, content formats, URLs, phone numbers, and email addresses, facilitating synchronized interaction and enhanced viewing experiences across devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If ATSC 2.0 trigger delivery service is used to pass triggers to second screen devices, then basic trigger information can be delivered, but the amount of information that may be included in a trigger is limited
Solution Approach 1:
The trigger message is segmented into multiple distinct fields including trigger_id, program_id, component_id, trigger_type, trigger_data, and timestamp. Each field carries specific information, allowing comprehensive data transmission while maintaining structured organization that reduces overall complexity.
Solution Approach 2:
The trigger delivery service is designed with a universal message format that can accommodate multiple types of triggers and information categories. The standardized structure allows the same service framework to handle diverse trigger types (program information, advertising, interactive content) without requiring separate complex protocols for each type.
2Adaptability or versatility
If two-way communications service provides TCP/IP connection for primary and second screen devices, then devices can communicate, but devices from different manufacturers are incompatible due to proprietary formats
Solution Approach 1:
A homogeneous communication protocol is implemented across all devices, using standardized TCP/IP based messaging with consistent data formats. This ensures that devices from different manufacturers can interoperate seamlessly, as the same message structure and communication rules apply universally to all primary and companion devices in the system.
Solution Approach 2:
The communication service acts as an intermediary layer between diverse devices, providing a standardized interface that translates between different device types while maintaining compatibility. The service handles message routing, format standardization, and protocol management, allowing devices to communicate without requiring manufacturer-specific implementations.
3Reliability
If current second screen application techniques are used, then basic interaction is possible, but synchronization issues occur between primary and companion devices
Solution Approach 1:
The system implements feedback mechanisms where the primary device sends trigger messages to companion devices, and companion devices can send status or response messages back. This bidirectional feedback ensures that both devices remain synchronized, as the primary device can monitor and adjust content delivery based on companion device status, and vice versa.
Solution Approach 2:
The primary device performs preliminary actions by sending trigger messages with complete information (program_id, component_id, trigger_data) before the companion device needs to act. This preliminary delivery of synchronized information allows the companion device to prepare and execute actions in sync with the primary device without requiring complex real-time coordination.
4Productivity
If ATSC 2.0 services are implemented, then second screen application support is provided, but content information is not provided to companion device applications in an efficient manner
Solution Approach 1:
Content information is segmented into structured trigger messages with distinct fields for trigger_id, program_id, component_id, trigger_type, trigger_data, and timestamp. This segmentation allows efficient processing and delivery of specific content information to companion devices while maintaining complete and organized data structures that prevent information loss.
Data Source
AI summary
The present invention relates to a method for a companion device to receive current service information from a primary device comprising: (a) said companion device receiving from said primary device an emergency alert message including at least one of: (i) an identifier of said emergency alert message that uniquely identifies said emergency alert message; (ii) a date when said emergency alert message was generated together with a time when said emergency alert message was generated; (iii) a content format defining a content type of an initial said emergency alert message; (iv) a content of said emergency alert message received given by initial content element; (v) a URL which provides initial emergency alert message content for accessibility; (vi) an additional URL which provides additional information about said emergency alert message; (vii) a phone number for obtaining additional information about said emergency alert message; (viii) an e-mail address for obtaining additional information about said emergency alert message; (ix) a received additional emergency alert containing a continuation of another said emergency alert message; (x) a received one of a new or a repeat said emergency alert message; (xi) a received said emergency alert message that is not repeated; (xii) an identifier of said primary device; (xiii) a version of said primary device.