Server Webpage Data Routing for Client Hardware Functions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing webpage technologies require separate modifications and upgrades for server and client sides to add hardware functions, making the process complex and time-consuming, especially when changing content or hardware-related functions.

Innovation Solution

The server sends different webpage data for browser and non-browser client applications, including hardware function information, allowing changes to be made at the server end without requiring client upgrades, simplifying the upgrading process and enabling users to access websites with enhanced hardware functions without additional changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hardware functions are added to the phone client, then hardware functionality is improved, but device complexity increases and client upgrades are required

Engineering Contradiction:

Improvehardware functionalityVSAvoidclient complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary that manages hardware function configurations. Instead of embedding hardware access logic directly in the client, the server acts as a mediator that receives client requests, determines appropriate hardware functions based on client capabilities, and returns corresponding webpage data with hardware function definitions. This separates hardware function management from client complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the hardware function management into separate components: the client sends capability information and requests, the server processes and determines hardware functions, and the server returns structured webpage data. This segmentation allows hardware functionality to be added without increasing client complexity, as the management logic resides on the server side.

Inventive Principle:

Principle #1Segmentation

2Productivity

If webpage content or hardware functions are modified, then functionality is improved, but separate server and client modifications are required causing time loss

Engineering Contradiction:

Improveupgrade efficiencyVSAvoidupgrade time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the server pre-determine and configure hardware function definitions in the webpage data before client execution. When hardware functions need to be modified or added, only the server-side webpage data needs to be updated in advance. The client simply receives and executes the pre-configured hardware function definitions, eliminating the need for separate client modification and upgrade processes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent inverts the traditional approach by making the server the active party that pushes hardware function definitions to the client, rather than the client actively seeking and implementing hardware functions. The server determines hardware functions based on client capability information and actively provides the corresponding webpage data with embedded hardware function definitions. This inversion allows centralized control and eliminates the need for separate client upgrades.

Inventive Principle:

Principle #13The other way round (Inversion)

3Adaptability or versatility

If the client is upgraded to add hardware functions, then hardware functionality is improved, but the upgrade process is complex and time-consuming for both developers and users

Engineering Contradiction:

Improvehardware functionalityVSAvoidupgrade process simplicity

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The server acts as an intermediary that handles the complexity of hardware function configuration and client capability matching. Instead of requiring developers to modify and upgrade client applications to add hardware functions, the server manages this complexity by receiving client capability information, determining appropriate hardware functions, and returning corresponding webpage data. This intermediary approach simplifies the upgrade process for both developers and users.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements self-service by enabling the client to automatically send its capability information to the server and receive appropriately configured webpage data with hardware function definitions. The client无需 manual upgrade or configuration - it automatically adapts to available hardware functions based on server-provided webpage data, making the process simple for users while maintaining full hardware functionality.

Inventive Principle:

Principle #25Self-service

Data Source

PatentEP2909998B1Webpages with onboard hardware functions

Publication Date: 2018.12.05 ALIBABA GROUP HOLDING LTD

Figure 1A
Figure 1B
Figure 2

AI summary

Sending webpage data to a client application includes: receiving a webpage request sent by the client application; detecting a marking parameter in the webpage request; determining a client type of the client application based at least in part on the marking parameter; in the event that the client type is determined to be a browser client application, sending to the client application first webpage data comprising webpage information; in the event that the client type is determined to be a non-browser client application, sending to the client application second webpage data comprising webpage information and code to execute an onboard hardware function.