Common Trace Data Format for Multi-System Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional trace tools are limited in integrating and analyzing tracing data from various systems with different structures, leading to delays, misreading, or loss of data, especially in large development projects involving multiple systems, applications, and interfaces.

Innovation Solution

A method for generating a common trace data format is introduced, where trace data is generated, identified, compared to a common format, and modified to ensure compliance, allowing for integration and analysis across different systems through a central administration system and common performance trace architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional trace tools are used to trace execution flows in various systems, then tracing capability is provided for individual systems, but integration and analysis of tracing data from various systems with different structures cannot be performed

Engineering Contradiction:
Improvetracing capabilityVSAvoiddata integration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a universal trace data structure that can accommodate multiple trace data formats from different systems. The structure includes fields such as trace event identifier, trace timestamp, trace level, and trace message that can represent various types of trace events across different systems, making the tracing tool universally applicable while maintaining data integrity

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

Solution Approach 2:

The patent introduces an intermediary conversion process that translates trace data from various system-specific formats into a common standardized format. This intermediary layer handles the format differences between systems, allowing trace data from heterogeneous sources to be integrated and analyzed together without losing accuracy

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If manual reading of trace data is performed to handle format differences, then data can be read, but delays occur and errors may be misread or lost

Engineering Contradiction:
Improvedata readabilityVSAvoiderror detection time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements automated format identification and conversion mechanisms that enable the trace analysis system to automatically adapt to different trace data formats without requiring manual intervention. The system self-adjusts by detecting the source system and applying appropriate conversion rules, eliminating manual reading delays and reducing human error

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If trace data from multiple systems with different structures is integrated, then comprehensive tracing is achieved, but data loss or misreading occurs without a common format

Engineering Contradiction:
Improvemulti-system integrationVSAvoidtrace data完整性
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent transforms trace data from various systems by changing its structural parameters to fit a common format. Key parameters such as event identification, timestamp format, severity levels, and message structure are standardized while preserving the essential information content, enabling comprehensive multi-system tracing without data loss

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7979850B2Method and system for generating a common trace data format
Publication Date: 2011.07.12 SAP SE
  • US7979850B2 patent drawing
  • US7979850B2 patent drawing
  • US7979850B2 patent drawing

AI summary

A method for generating a common trace data format is disclosed. In one embodiment, the method includes generating trace data at a provider, identifying a format of the trace data, comparing the format of the trace data with a common format to determine if the format is in compliance with the common format, and modifying the format to comply with the common format, if the format is not in compliance with the common format.