Mobile Broadband Device Web Management Decoupling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of software version customization and device terminal customization for mobile broadband devices is overly complex due to the close coupling with hardware production, and the local Web mode lacks the efficiency in releasing Web versions, with numerous customized versions of Web application software requiring separate production and slow deployment to end-users.

Innovation Solution

A method and system where a mobile broadband device sends a local device identifier to a server, updates customized parameters, and requests a Web management page, allowing the server to return the page and execute management commands through an API, decoupling hardware production from Web application software customization and enabling remote API invocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If local Web mode is used to manage mobile broadband device, then Web application software can be customized, but software version customization and device terminal customization management becomes too complicated

Engineering Contradiction:
ImproveWeb application software customizationVSAvoidcustomization management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the customization management into two independent parts: device terminal customization handled at the hardware production level, and software version customization handled at the Web application level. This separation allows each to be managed independently through their respective configuration files, reducing the overall complexity of customization management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration files as intermediaries between the device terminal and Web application software. The device terminal configuration file stores terminal-specific parameters, while the Web application configuration file stores software-specific parameters. These configuration files act as mediators that decouple the customization requirements, allowing independent management without direct coupling between software and hardware customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If Web App is burnt into data card during production, then customization can be implemented, but close coupling with hardware production occurs

Engineering Contradiction:
Improvesoftware customizationVSAvoidhardware production coupling
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the software delivery into two parts: a minimal core system burned into the data card during hardware production, and the full Web application software delivered separately through Web deployment. This segmentation allows the hardware production process to remain simple while enabling comprehensive software customization through external configuration files and Web-based delivery mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary configuration by pre-configuring the device terminal configuration file with terminal-specific parameters during hardware production, but delays the Web application software configuration until after deployment. This allows the hardware to be manufactured with minimal software requirements, while the full software customization occurs as a preliminary step before actual use, decoupling hardware production from complete software customization.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If customized versions are produced separately, then specific requirements can be met, but version management complexity increases

Engineering Contradiction:
Improvespecific requirement fulfillmentVSAvoidversion management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal configuration management system that can handle multiple customized versions through a common framework. Both device terminal configuration files and Web application configuration files use standardized formats and structures, allowing the system to manage diverse customized versions universally. This multi-functionality enables the same management mechanism to handle different versions without increasing complexity.

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

Solution Approach 2:

The patent manages version customization through parameter changes in configuration files rather than creating fundamentally different software structures. By using configuration files that store adjustable parameters for different versions, the system can adapt to specific requirements by changing parameters while maintaining the same underlying software architecture, thereby reducing version management complexity.

Inventive Principle:
Principle #35Parameter changes

4Ease of operation

If Web App software is delivered with data card, then local Web mode works, but Web version releasing efficiency cannot be fully used

Engineering Contradiction:
Improvelocal Web mode functionalityVSAvoidWeb version releasing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent makes the Web application software delivery dynamic rather than static. Instead of permanently binding the Web App to the data card, the system allows the Web application configuration file to be updated and reconfigured at any time through Web deployment. This dynamic approach enables rapid version releases and updates without requiring physical data card redistribution, fully utilizing Web releasing efficiency while maintaining local Web mode functionality.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses configuration files as lightweight copies that contain the essential customization parameters. Rather than distributing complete software installations with each data card, the system distributes configuration files that can be quickly copied and applied to multiple devices. This copying mechanism enables efficient Web version releasing while maintaining the local Web mode operation through the configuration parameters stored in these portable files.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2704358B1Method and device for managing mobile broadband device
Publication Date: 2017.02.15 HUAWEI DEVICE CO LTD
  • EP2704358B1 patent drawingFigure 1
  • EP2704358B1 patent drawingFigure 2
  • EP2704358B1 patent drawingFigure 3

AI summary

The present invention relates to the field of communication technologies, and provides a method, a device, and a system for managing a mobile broadband device. The method includes the following steps: sending a local device identifier to a server; updating a customized parameter of the mobile broadband device according to a customized parameter returned by the server; sending a request for opening a Web management page to the server, so that the server returns the Web management page; receiving a management command sent by a host-side device on the Web management page; and executing the management command through an application programming interface corresponding to the management command on the mobile broadband device. The present invention implements decoupling between hardware production of the mobile broadband device and customization of Web application software. Therefore, the complexity of managing the software version customization and device terminal customization is reduced, the high efficiency of Web version releasing is improved, and the mobile broadband device has a capability of allowing the server to remotely invoke an application programming interface to execute a corresponding management command.