Automated Mobile Driver Installation via Server Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of loading driver software onto mobile devices, such as mobile phones, is high and often requires manual intervention, making it difficult for users to successfully transfer game software, as it involves determining vendor and product identities and matching driver software, which can be cumbersome and error-prone.

Innovation Solution

A method where a second terminal connects to a first terminal, obtains its identification information, sends a driving request to a back-end server, receives a driving data address, and then sends the corresponding driving data to the first terminal to load the necessary software, simplifying the process by automating the matching and transfer of driver software based on identification information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual driver software installation is used, then driver software can be installed on mobile devices, but the operation becomes complicated with high complexity

Engineering Contradiction:
Improvedriver software installation successVSAvoidoperation complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically identifies the mobile device through USB connection, retrieves device information (vendor ID, product ID), queries the server for matching driver software, and completes the installation process without requiring manual user intervention. The device and system serve themselves by automatically matching and installing the correct driver software based on device identification.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A server acts as an intermediary between the computer and mobile device. The server receives device identification information, stores and processes driver software matching logic, and returns appropriate driver software addresses. This intermediary handles the complex matching logic centrally, simplifying the client-side operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual driver software installation is used, then driver software can be installed on mobile devices, but the process becomes error-prone

Engineering Contradiction:
Improvedriver software installation successVSAvoidprocess complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where the computer reads device identification information from the mobile device via USB, sends this information to the server, and receives back matching driver software addresses. This feedback loop ensures that the correct driver software is automatically selected and installed, reducing errors.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Driver software and matching logic are pre-stored on the server before the installation process begins. The server is pre-configured with vendor ID, product ID, and corresponding driver software mappings. This preliminary preparation eliminates the need for real-time complex calculations and reduces installation errors.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If automated driver software installation is implemented, then operation complexity is reduced, but system complexity increases

Engineering Contradiction:
Improveoperation simplicityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The server serves as an intermediary that handles all complex operations including device identification, driver software storage, matching logic, and transmission. This centralizes system complexity in the server while keeping the client-side operation simple, as the complexity is shifted rather than reduced.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The manual mechanical process of identifying devices, selecting drivers, and installing software is replaced with an automated electronic system. USB connection automatically triggers information exchange between devices and server, substituting manual operations with automated data communication and processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If driver software matching based on vendor and product identity is performed, then correct driver software can be installed, but the process becomes cumbersome

Engineering Contradiction:
Improvedriver software compatibilityVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Driver software and matching information are pre-stored on the server before installation is needed. The server is pre-configured with vendor ID, product ID, and corresponding driver software mappings. This preliminary preparation enables instant retrieval and installation without time-consuming real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of analyzing device hardware in real-time to match drivers, the system uses pre-stored copies of device identification information (vendor ID, product ID) and pre-matched driver software copies on the server. This copying approach enables rapid retrieval and installation without repeated analysis.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9442741B2Method, terminal, server, and system for data processing
Publication Date: 2016.09.13 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US9442741B2 patent drawing
  • US9442741B2 patent drawing
  • US9442741B2 patent drawing

AI summary

Methods, terminals, servers, and systems for data processing are provided. After establishing a connection with a first terminal, a second terminal obtains identification information of the first terminal and sends a driving request containing the identification information of the first terminal to a back-end server, such that the back-end server determines for the first terminal a driving data address matched with the identification information of the first terminal according to the identification information. The second terminal receives the driving data address sent from the back-end server, and obtains driving data corresponding to the driving data address. The second terminal sends the driving data to the first terminal for the first terminal to load the driving data.