Appliance Command Taxonomy for Interoperable Component Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of household appliance components and diverse implementation choices make it difficult to design, develop, test, diagnose, control, and debug appliances, hindering the creation of interoperable and reusable components.

Innovation Solution

A software architecture that enables communication between appliance components through a message protocol with a packet structure, allowing for dynamic and virtual data aggregation, and includes features like message binding, data processing only upon complete transactions, and support for external diagnostics and configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If diverse componentry and implementation choices are used in appliances, then functionality and adaptability are improved, but design, development, testing, diagnosis, control, and debug complexity increase

Engineering Contradiction:
ImprovefunctionalityVSAvoiddesign complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the appliance control system into discrete, addressable components that communicate through a standardized message bus. Each component (heating element, motor, sensor, etc.) is divided into independent functional units with unique addresses, allowing them to be designed, tested, and controlled separately while maintaining overall system functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal message protocol and control architecture that can interface with diverse component types through a common standardized interface. The message bus system provides multi-functional capability to communicate with various components (thermal, mechanical, electrical) using the same communication framework, reducing the need for component-specific control logic.

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

2Reliability

If discrete circuits are used for individual communication between components, then communication reliability is improved, but device complexity and wiring requirements increase

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidwiring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple discrete communication circuits into a single message bus system. All components share a common communication medium (bus) with standardized protocols, eliminating the need for separate dedicated circuits between each component pair. This reduces wiring complexity while maintaining communication reliability through protocol-level error handling and acknowledgment mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If components are enabled with software within microprocessors to achieve network participation, then interoperability and reusability are improved, but development and debugging difficulty increase

Engineering Contradiction:
ImproveinteroperabilityVSAvoiddebugging difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enforces homogeneity in the software architecture by requiring all components to implement a standardized message protocol and control interface. Each component uses the same basic software structure for receiving commands, reporting status, and handling events, making debugging and development more systematic and less prone to edge-case errors despite the diversity of physical components.

Inventive Principle:
Principle #33Homogeneity

4Productivity

If a message protocol with packet structure is implemented, then data aggregation and communication efficiency are improved, but processing complexity increases

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-defining message packet structures, protocols, and communication rules during system design. Message formats, address schemes, and control sequences are established beforehand, allowing components to process communications efficiently without complex runtime decision-making. This reduces processing complexity during operation while maintaining high communication efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7908019B2Taxonomy engine and dataset for operating an appliance
Publication Date: 2011.03.15 WHIRLPOOL CORP
  • US7908019B2 patent drawing
  • US7908019B2 patent drawing
  • US7908019B2 patent drawing

AI summary

A taxonomy engine in a software architecture generates a taxonomy dataset establishing the group of well formed commands, and at least one command generator of the system is adapted to generate a well formed command using the taxonomy dataset. The taxonomy engine is configured to deliver the taxonomy dataset to the command generator, and the command generator is configured to deliver the well formed command to the controller.