Timing Disruption Testing for Legacy Software Backward Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computer systems face issues with backward compatibility due to differences in performance characteristics between legacy and new devices, leading to errors in legacy applications when executed on newer systems with higher or lower performance.

Innovation Solution

Implement a timing testing mode that simulates different hardware configurations and operating frequencies to identify and fix synchronization errors between hardware and software components, allowing applications to run smoothly on devices with varying timing characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the new device operates at higher performance speed, then processing capability is improved, but synchronization errors occur in legacy applications

Engineering Contradiction:
Improveprocessing capabilityVSAvoidsynchronization accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by implementing a timing testing mode before legacy applications are deployed to the new device. This mode proactively identifies synchronization errors by simulating various timing scenarios and performance characteristics, allowing developers to detect and fix potential issues before they manifest in production environments. The timing testing mode performs advance validation of timing-critical code paths, preventing synchronization errors from occurring when the application runs at full performance speed.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the new device uses different hardware architecture, then performance is improved, but backward compatibility is compromised

Engineering Contradiction:
ImproveperformanceVSAvoidbackward compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent applies parameter changes by introducing a timing testing mode that dynamically adjusts hardware parameters such as operating frequency, cache timing, and processor speed to match legacy device characteristics. This allows the new device to simulate the timing behavior of older hardware architectures, enabling legacy applications to be tested under conditions that replicate their original execution environment. By changing these parameters, the system maintains backward compatibility while preserving the ability to run at full performance when needed.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If timing testing mode is implemented, then synchronization errors are detected, but additional testing time is required

Engineering Contradiction:
Improveerror detection capabilityVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies the skipping principle by implementing automated timing testing procedures that可以快速ly execute through various timing scenarios without requiring manual intervention for each test case. The system automatically skips through different frequency settings, cache configurations, and processor speed variations, rapidly identifying synchronization errors that would otherwise require extensive manual testing. This automated approach reduces the time loss associated with comprehensive timing validation.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentEP3920032B1Backward compatibility testing of software in a mode that disrupts timing
Publication Date: 2025.09.03 SONY INTERACTIVE ENTERTAINMENT LLC
  • EP3920032B1 patent drawingFigure 1
  • EP3920032B1 patent drawingFigure 2
  • EP3920032B1 patent drawingFigure 3

AI summary

A device may be run in a timing testing mode in which the device is configured to disrupt timing of processing that takes place on the one or more processors while running an application with the one or more processors. The application may be tested for errors while the device is running in the timing testing mode