Modular Service Configuration for Remote Data Processing Updates

Solution Overview

Problem

Conventional service configurations in data processing devices, such as franking machines, are rigid and inflexible, making it costly and difficult to update or modify services, as they require on-site technician intervention and involve transferring large software modules for minor changes.

Innovation Solution

Designing service configurations in a modular fashion, allowing individual components to be easily updated or exchanged, enabling centralized administration and transmission of updates without the need for on-site technicians, and using semantically-hierarchical coding formats like XML for flexible modification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service configurations are designed rigidly with static coding, then service stability is maintained, but service adaptability deteriorates

Engineering Contradiction:

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The service configuration is divided into multiple independent components (service identification, data field configuration, message configuration, protocol configuration) that can be individually modified. This segmentation allows specific parts to be updated without changing the entire configuration, maintaining stability while enabling adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The service configuration transitions from static coding to dynamic configurability through XML-based definitions. Configuration components can be modified, added, or removed without recompiling the entire service, allowing the system to adapt to changing requirements while maintaining operational stability.

Inventive Principle:

Principle #15Dynamics

2Reliability

If complete software modules are downloaded for function updates, then service completeness is ensured, but data transfer volume increases

Engineering Contradiction:

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

Individual configuration components are extracted from complete software modules. Instead of downloading entire service packages, only the specific XML configuration files that need updating are transferred. This extraction minimizes data transfer volume while ensuring that the necessary service updates are complete and functional.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The service configuration is segmented into independent XML files that can be selectively updated. Each configuration component (data fields, messages, protocols) is a separate downloadable unit, allowing the system to receive only the specific updates needed rather than complete software modules.

Inventive Principle:

Principle #1Segmentation

3Reliability

If on-site technicians are used for service updates, then service reliability is maintained, but administrative effort and cost increase

Engineering Contradiction:

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system enables automated service updates through configuration file transmission and automatic installation. The data processing device can update its own service configurations by receiving XML files and applying them without requiring on-site technician intervention, reducing administrative effort while maintaining reliability through structured update procedures.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Service configuration updates are prepared in advance as XML files at the data center. These pre-configured update packages can be automatically transmitted and installed, eliminating the need for on-site technicians and reducing administrative effort while ensuring reliable updates through pre-validation.

Inventive Principle:

Principle #10Preliminary action

4Ease of manufacture

If service configurations are statically coded, then development simplicity is maintained, but service flexibility deteriorates

Engineering Contradiction:

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

Service configurations are defined through XML templates that can be copied and reused. Standard configuration patterns can be replicated across different services and devices, maintaining development simplicity through template reuse while enabling flexibility through parameter customization and selective modification of configuration components.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS7606264B2Method and arrangement for providing services between data processing devices

Publication Date: 2009.10.20

AI summary

In a method and arrangement for providing services, a first data processing device provides a service for a remote second data processing device, the first service being implemented according to a service configuration and the first service configuration is modularly composed of a plurality of components, with at least one of the components of the service configuration being modifiable to update the service.