Unified Keyboard Input Engine for Cross-Keyboard Lexicon Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices with dual keyboards (physical and virtual) require two input method kernel engines, leading to resource inefficiency and poor user experience due to the inability to share user entries between keyboard types.
Innovation Solution
Implement a unified input method kernel engine that manages both keyboards, loading only partial information specific to the current keyboard type and sharing a user lexicon across types, reducing resource usage and switching time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If two input method kernel engines are used for dual keyboards, then each keyboard can function independently, but resource occupation increases significantly
Solution Approach 1:
The patent merges two separate input method kernel engines into a single unified engine that can serve both physical and virtual keyboards. The unified engine loads only the necessary vocabulary and conversion algorithm models for the currently active keyboard type, avoiding the need to maintain two complete engine instances simultaneously. This reduces memory occupation and resource usage while preserving independent functionality for both keyboard types.
Solution Approach 2:
The unified input method engine is designed to be universal, supporting multiple keyboard types (physical and virtual) through a single instance. The engine dynamically adapts its behavior and loaded resources based on the active keyboard type, making one engine perform the functions previously requiring two separate engines. This multi-functionality approach reduces overall resource consumption while maintaining full keyboard functionality.
2Reliability
If two separate input method kernel engines are used, then each keyboard has dedicated processing, but user entries cannot be shared between keyboards
Solution Approach 1:
By merging the vocabulary storage and user entry databases into a single shared repository within the unified engine, user entries learned from one keyboard type become immediately available for the other keyboard type. The unified engine maintains a common user lexicon that both physical and virtual keyboards can access, eliminating the isolation between separate engine instances and enabling seamless entry sharing.
Solution Approach 2:
The unified input method engine acts as an intermediary that manages a shared user entry database accessible by both keyboard types. When a user enters new terms using one keyboard, the unified engine captures and stores these entries in the shared database, making them available for future use with either keyboard type. This intermediary role enables cross-keyboard knowledge transfer while maintaining reliable input processing.
3Reliability
If complete engine data is reloaded when switching keyboard types, then the new keyboard type is fully initialized, but switching time increases
Solution Approach 1:
The unified engine extracts and loads only the specific vocabulary subsets and conversion algorithm models necessary for the currently active keyboard type, rather than loading complete engine data for each keyboard type. When switching between physical and virtual keyboards, only the relevant portion of the vocabulary and models is loaded into memory, significantly reducing the time required for keyboard switching while ensuring proper initialization of the active keyboard type.
Solution Approach 2:
The engine implements dynamic resource loading that adapts to the active keyboard type. Instead of static complete loading, the system dynamically determines which vocabulary subsets and models are needed based on the current keyboard state, loads only those resources, and switches efficiently. This dynamic approach minimizes switching time while maintaining reliable initialization of the active keyboard type's specific requirements.
Data Source
AI summary
A keyboard input method includes determining a first type of a current input keyboard used by the electronic device; initializing an input method kernel engine and setting the first type corresponding to the current input keyboard for the input method kernel engine including loading a conversion algorithm model corresponding to the first type of the current input keyboard; loading a system word vocabulary corresponding to the first type of the current input keyboard; loading a user lexicon, the user lexicon comprising a user entry used based on an input keyboard of any type; obtaining inputted information of the current input keyboard using the input method kernel engine; obtaining user entry information corresponding to the inputted information from the user lexicon; obtaining system entry information corresponding to the inputted information from the system word vocabulary; and determining a list of to-be-selected entries corresponding to the inputted information.


