Single System Model Decouples Application Views

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The multiple system model approach in multi-function printers couples application views to system models, limiting functionality and expandability, and results in unnecessary communication of status and error messages to all user interfaces, disrupting user experience and functionality.

Innovation Solution

Implementing a single system model with a central database and a common software bus protocol decouples application views from the system model, allowing targeted status and error messaging and enabling the addition or modification of application views without affecting the system model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a multiple system model approach is used, then each user interface can access device functions, but application views are coupled to system models limiting functionality and expandability

Engineering Contradiction:

Improvefunctionality and expandabilityVSAvoidcoupling between application views and system models

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the system into separate components: a single system model and multiple independent application views. Each application view is decoupled from the system model, allowing independent development, modification, and removal of application views without affecting the system model or other application views. This segmentation resolves the contradiction by reducing coupling complexity while maintaining adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The single system model serves as a universal data source for all application views through a common software bus protocol. The system model maintains a centralized database that all application views can access, enabling multi-functionality without requiring separate system models for each user interface. This universality improves expandability while reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Loss of information

If a multiple system model approach is used, then all interfaces can access device status, but status and error messages are communicated to all interfaces regardless of active use

Engineering Contradiction:

Improverelevant status and error information deliveryVSAvoiduser experience disruption

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

The patent implements local quality by delivering status and error messages selectively to specific application views based on active user sessions. Each application view receives only the information relevant to its current operation, rather than broadcasting all system status to all interfaces. This resolves the contradiction by reducing information loss for active users while preventing disruption to inactive users.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

Instead of having the system model push status information to all application views simultaneously, the patent inverts the approach by having application views pull only the specific status information they need when required. This inversion of the information flow mechanism allows targeted message delivery that improves both information relevance and user experience.

Inventive Principle:

Principle #13The other way round (Inversion)

3Reliability

If a multiple system model approach is used, then device functions can be monitored at all interfaces, but error messages disrupt active users and block uninterrupted use of non-affected functions

Engineering Contradiction:

Improveuninterrupted use of non-affected functionsVSAvoiderror message disruption to active users

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments error message delivery by associating errors with specific application views rather than broadcasting to all interfaces. When an error occurs, only the application view handling the affected function receives the error message, allowing other active application views to continue uninterrupted. This segmentation resolves the contradiction by maintaining reliability for non-affected functions while reducing harmful disruption to active users.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The common software bus protocol acts as an intermediary between the system model and application views. It mediates error message delivery by filtering and routing errors only to the appropriate application views based on the current operational context, preventing erroneous interruptions to active functions while maintaining system reliability monitoring.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8701021B2Capability to build multiple application views from a single system model

Publication Date: 2014.04.15 HEWLETT PACKARD DEVELOPMENT COMPANY LP

AI summary

An embedded marker system includes a plurality of devices communicatively coupled to a single system model. The system further includes a plurality of application views configured to communicate with the system model to obtain status and configuration data associated with one of the plurality of devices.