Web Interface Module for Mobile Broadband Device Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile broadband devices require separate clients for each operating system platform, leading to increased development complexity, cost, and storage requirements due to limited cross-platform support, and necessitate installation on host devices.

Innovation Solution

A mobile broadband device equipped with a Web protocol stack module, a Web interface module, and a Web service implementing module allows management through a Web interface, eliminating the need for platform-specific clients by using standard Web protocols and browsers, enabling management without installation and reducing development and hardware costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate clients are developed for each operating system platform, then platform-specific functionality can be optimized, but development complexity and cost increase significantly

Engineering Contradiction:
Improveplatform-specific functionalityVSAvoiddevelopment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal client architecture that can operate across multiple operating system platforms (Windows, Linux, macOS, etc.) through a single codebase. The framework provides platform-agnostic interfaces while using operating system-specific implementations only where absolutely necessary, allowing one client to serve multiple platforms without sacrificing core functionality.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an abstraction layer and standardized communication protocols between the client and mobile broadband device that mediate platform-specific differences. This intermediary layer handles operating system variations, allowing the core client logic to remain platform-independent while still accessing native capabilities when needed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate clients are developed for each operating system platform, then platform-specific optimization is possible, but development cost increases

Engineering Contradiction:
Improveplatform-specific optimizationVSAvoiddevelopment cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal client framework that reduces development cost by eliminating the need to hire and maintain separate development teams for each operating system platform. The single codebase approach significantly reduces development, testing, and maintenance costs while still providing optimized functionality through standardized interfaces.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent allows configuration parameters and behavior to be adjusted based on the detected operating system platform, enabling optimization for each platform without requiring separate codebases. The client automatically adapts its behavior, resource usage, and interface presentation based on the running platform while maintaining a unified code structure.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If platform-specific clients are required, then each platform can be optimized, but cross-platform support becomes limited

Engineering Contradiction:
Improveplatform optimizationVSAvoidcross-platform support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a client that natively supports multiple operating system platforms including Windows (various versions), Linux (various distributions), macOS, and embedded systems. The unified architecture provides consistent functionality across all platforms while adapting to platform-specific conventions and capabilities, achieving both optimization and broad support.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent makes the client dynamically adaptable to different operating system environments by detecting the runtime platform and adjusting its behavior, resource allocation, and interface presentation accordingly. This dynamic adaptation allows the same client binary or package to optimize its operation on each platform without requiring separate versions.

Inventive Principle:
Principle #15Dynamics

4Ease of operation

If a client is installed on the host device, then management functionality is available, but storage space is occupied and installation is required

Engineering Contradiction:
Improvemanagement functionalityVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts the client functionality from a traditional installed application model and implements it as a lightweight web-based interface or on-demand service. This extraction removes the need for permanent installation and associated storage occupation, while still providing full management functionality when needed through browser-based access or temporary runtime environments.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces the permanent installed client with a disposable, on-demand access model where management functionality is provided through web pages or temporary runtime environments that do not require persistent storage. The client functionality exists only when actively used, significantly reducing or eliminating storage requirements while maintaining full operational capability.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS8370461B2Mobile broadband device and method for managing mobile broadband device
Publication Date: 2013.02.05 HUAWEI DEVICE CO LTD
  • US8370461B2 patent drawing
  • US8370461B2 patent drawing
  • US8370461B2 patent drawing

AI summary

A method for managing a mobile broadband device includes receiving, by the Web interface module via the Web protocol stack module, a management command that is sent by a user on a Web management page of a host device, where the Web management page is provided by the Web interface module; sending, by the Web interface module via the Web protocol stack module, the management command to the Web service implementing module; and receiving, by the Web service implementing module, the management command, and invoking an application programming interface that corresponds to the management command to execute the management command.