Terminal Device Trap Management Object for Autonomous Fault Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing device management systems, such as OMA DM, are limited to reporting diagnostic results and fault reports from terminals, lacking the ability to execute predetermined operations for recovery or backup when failures occur, thus restricting their application and fault tolerance.

Innovation Solution

A method and apparatus that allow a device management server to send and execute predetermined operations on a terminal device based on trigger conditions, enabling maintenance processing like failure repair and data backup, beyond mere reporting, by storing and executing these operations within a Trap management object.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the existing event trigger mechanism is used for reporting diagnostic results or fault reports, then the terminal can send collected data back to the server, but the terminal cannot carry out any other operations such as recovery or backup

Engineering Contradiction:
Improveterminal operation capabilityVSAvoidfault recovery capability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The Trap MO is extended to perform multiple functions: it not only reports diagnostic results and fault reports to the server, but also executes predetermined operations locally on the terminal. This multi-functional design allows the same trigger mechanism to handle both reporting and recovery/backup operations, resolving the contradiction between versatility and reliability.

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

Solution Approach 2:

The system stores predetermined operations (such as backup procedures or recovery commands) in advance within the Trap MO. When a trigger condition occurs, these pre-stored operations are automatically executed without requiring real-time decision-making or manual intervention, enabling reliable fault recovery while maintaining terminal versatility.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the terminal only performs reporting operations when trigger conditions are satisfied, then the system structure remains simple, but the application scope and fault tolerance are greatly limited

Engineering Contradiction:
Improveapplication scopeVSAvoidterminal function complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The predetermined operations are nested within the Trap MO structure itself. The Trap MO contains both the trigger condition definition and the predetermined operations to be executed, creating a self-contained unit. This nesting approach expands application scope by allowing complex operations while keeping the overall system structure manageable through hierarchical organization.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The terminal device autonomously executes the predetermined operations stored in the Trap MO without requiring external intervention. The system serves itself by automatically performing recovery or backup operations when trigger conditions are met, thereby expanding application scope while avoiding the complexity of requiring continuous external control.

Inventive Principle:
Principle #25Self-service

3Reliability

If automatic recovery or backup operations are added to the terminal, then fault tolerance is improved, but the device complexity and operation management become more complex

Engineering Contradiction:
Improvefault toleranceVSAvoidoperation management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

By pre-storing recovery and backup operations within the Trap MO before faults occur, the system eliminates the need for complex real-time decision-making during fault conditions. The predetermined operations are ready to execute immediately when trigger conditions are satisfied, improving fault tolerance while keeping operation management simple through advance preparation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback loop where the terminal monitors trigger conditions, executes predetermined operations from the Trap MO, and can report results back to the server. This feedback mechanism enables reliable fault tolerance while managing complexity through structured information flow and automated execution based on predefined conditions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8434094B2Method and apparatus for implementing a predetermined operation in device management
Publication Date: 2013.04.30 HUAWEI TECH CO LTD
  • US8434094B2 patent drawing
  • US8434094B2 patent drawing
  • US8434094B2 patent drawing

AI summary

A method for implementing a predetermined operation in device management, being based on a DM system defined by OMA, includes: sending by the device management system a second predetermined operation based on a trigger condition to a terminal device and storing by the terminal device the received predetermined operation; and obtaining by the terminal device from itself the second predetermined operation and executing the second predetermined operation when the trigger condition is satisfied. The present invention also discloses an apparatus for implementing a predetermined operation in device management.