Protocol Version Compatibility Check for Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex systems with multiple software modules or bus participants face time-consuming compatibility checks due to varying protocol versions, making commissioning and ensuring data exchange compatibility challenging.

Innovation Solution

A method where participants exchange and compare protocol version information during initialization, using a list of previous versions to determine compatibility, with the latest version being compared, and automatically detecting interface changes for updates, ensuring secure data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If protocol version information is exchanged and compared during initialization, then compatibility checking is automated and commissioning is simplified, but additional data exchange and processing time are required during initialization

Engineering Contradiction:
Improvecommissioning simplicityVSAvoidinitialization time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The protocol version information is exchanged and compatibility checked during the initialization phase, before actual data exchange begins. This preliminary action ensures that compatibility issues are identified early, automating the commissioning process and simplifying system setup without requiring manual compatibility verification later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically performs compatibility checking by exchanging protocol version information between participants during initialization. Each participant independently compares its own protocol version with the other participant's version, automatically determining compatibility without external intervention or manual configuration.

Inventive Principle:
Principle #25Self-service

2Reliability

If protocol version information including development history is stored and exchanged, then compatibility determination is accurate, but storage requirements and data exchange volume increase

Engineering Contradiction:
Improvecompatibility determination accuracyVSAvoiddata exchange volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Only the essential protocol version information is extracted and exchanged during initialization, rather than transmitting complete development histories. The system stores and exchanges only the necessary version identifiers and compatibility metadata, reducing data exchange volume while maintaining accurate compatibility determination.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system exchanges partial protocol version information sufficient for compatibility checking during initialization, rather than all detailed development history. This partial action provides enough data to accurately determine compatibility while minimizing the quantity of data transmitted and stored.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If manual compatibility checking is performed, then compatibility can be verified, but commissioning time and development effort increase

Engineering Contradiction:
Improvecompatibility verificationVSAvoidcommissioning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically performs compatibility verification by exchanging protocol version information during initialization. Each participant independently compares protocol versions and determines compatibility without requiring manual intervention, thereby verifying reliability while reducing commissioning time and development effort.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Compatibility verification is performed automatically during the initialization phase before actual data exchange begins. This preliminary automated checking eliminates the need for manual compatibility verification later, reducing commissioning time while ensuring reliable compatibility through systematic version comparison.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2283630B1Compatibility method and system for data exchange
Publication Date: 2013.04.10 SEW EURODRIVE GMBH & CO KG
  • EP2283630B1 patent drawingFigure 1
  • EP2283630B1 patent drawingFigure 2
  • EP2283630B1 patent drawingFigure 3

AI summary

The invention relates to a system and a method fro operating a system comprising users, exchanging data by means of an interface, wherein each user stores information on protocol version or a list of all the information about previous protocol versions in particular those associated with previous development stages. During the initialisation phase the or a in particular the latest information on protocol version is exchanged and compared, in particular to determine the compatibility, in compatibility, implausibility or partial compatibility with the latest or an older protocol version.