Game Button Event Conversion for Mobile Control Layouts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile gamers using Chromebooks face inconvenient control settings, as Android games are preset to the right side of the keyboard or touch screen, differing from the customary left-hand direction control used on desktops with keys like 'A', 'W', 'S', 'D'.

Innovation Solution

A game operation optimization method and mobile device that reads a button configuration file to convert button events from one set of keys (e.g., 'A', 'W', 'S', 'D') to another (e.g., arrow keys) based on predefined relationships, allowing the processor to control game applications in a more familiar manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If Android games are preset to the right side of the keyboard or touch screen for mobile device control, then the games can be controlled on mobile devices, but the control is inconvenient for users accustomed to desktop keyboard layout (A, W, S, D keys on the left side)

Engineering Contradiction:
Improvecontrol convenienceVSAvoidcross-platform compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic button configuration that can be adjusted based on user preferences and game requirements. The system allows real-time switching between different control layouts (desktop-style left-side controls and mobile-style right-side controls), making the control scheme adaptable rather than fixed. This resolves the contradiction by enabling the same game to provide both mobile-optimized and desktop-familiar control experiences.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of button position and mapping configuration to resolve the control layout conflict. By allowing users to modify button assignment parameters and mapping relationships between physical keys and in-game actions, the system can transform the default mobile layout into a desktop-style layout, thus maintaining cross-platform compatibility while improving ease of operation for desktop users.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If button events are converted from one set of keys to another based on configuration files, then user experience is improved, but additional processing steps are required

Engineering Contradiction:
Improveuser experienceVSAvoidevent processing complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring button mapping relationships in configuration files before the game runs. The mapping between different key sets (A/W/S/D and arrow keys) is established in advance, so when a user presses a key, the system simply looks up the pre-defined mapping rather than performing complex real-time conversions. This reduces processing complexity while maintaining improved user experience.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer (the button configuration file and event conversion module) between the physical keyboard and the game application. This intermediary handles the translation and mapping of button events, isolating the complexity from both the user and the core game logic. The configuration file acts as a mediator that defines relationships without requiring complex processing during game execution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11253777B2Game operation optimization method and mobile device
Publication Date: 2022.02.22 ACER INC
  • US11253777B2 patent drawing
  • US11253777B2 patent drawing
  • US11253777B2 patent drawing

AI summary

The present disclosure provides a game operation optimization method and a mobile device. The method includes: in response to detecting that a game application is operating on the mobile device, reading a button configuration file corresponding to the game application; in response to detecting a first button event corresponding to the first button, converting the first button event into a second button event corresponding to the second button according to the button configuration file; and controlling a first content of the game application according to the second button event.