Speech Data Sequence Identifier Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing speech output systems face compatibility issues when software updates require different or additional speech data, leading to potential incompatibility between speech data and application versions, especially when speech data is provided separately from the main application.
Innovation Solution
The solution involves using sequence identifiers, such as RSDI and ASDI, to determine compatibility between speech data and application versions, ensuring that speech data can be updated or replaced while maintaining compatibility by adding or removing speech segments, and using composition lists to handle changes in speech output requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If speech data are provided separately from the main application, then users can update speech data without repurchasing the entire application, but compatibility problems arise when the main application software changes and requires different or additional speech data
Solution Approach 1:
The patent applies preliminary action by embedding a sequence identifier in the speech data that indicates the application version or speech data version for which it is compatible. This allows the system to pre-determine compatibility before attempting to use the speech data, preventing version mismatch issues. The sequence identifier is checked in advance to ensure the speech data matches the required application version.
Solution Approach 2:
The patent implements feedback by checking the sequence identifier of the speech data against the sequence identifier of the required speech data for the current application version. This feedback mechanism determines whether the speech data is compatible and should be used, or if updated speech data needs to be loaded. The system uses this comparison result to automatically select the appropriate speech data set.
2Reliability
If speech data are bundled with the application, then compatibility is ensured, but users cannot update speech data independently to improve sound quality or use different voices
Solution Approach 1:
The patent applies segmentation by separating speech data from the main application executable, storing them as distinct files. The speech data are stored as separate files with their own sequence identifiers, allowing independent updating. This segmentation enables users to update only the speech data files without needing to update or repurchase the entire application package.
Solution Approach 2:
The patent implements universality by creating a universal interface mechanism (sequence identifier comparison) that works across different application versions and speech data sets. This universal compatibility check allows any speech data set to be used with any application version that supports the same identifier format, enabling both backward compatibility and forward compatibility simultaneously.
3Reliability
If speech data are provided as a complete package with the application, then no compatibility issues occur, but the data size and software complexity increase
Solution Approach 1:
The patent extracts the speech data from the application executable and stores them as separate files. This extraction reduces the size of the main application and allows speech data to be managed independently. The sequence identifier mechanism is extracted as a simple comparison function that checks compatibility without requiring complex integration logic within the application code.
Data Source
AI summary
A system for outputting speech from speech data that may include an application, an internal speech data module, and an external speech data module is provided. The internal speech module stores default speech data that defines which speech data is compatible with the application. The external speech module, which may include a data carrier, may provide optional speech data, including a sequence identifier, separately from the application. To determine whether optional speech data fits the application, the application generates a sequence of one or more segment designators designating speech segments, and associating with them a sequence identifier. The application may also compare the sequence identifier generated by the application with that of the optional speech data. If a predetermined result occurs, the optional speech data may be used. Otherwise, the default speech data may be used. This method may be used to update default speech data with optional speech data.