Vehicle Graphic Code Conversion With Embedded Configuration Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle development processes face challenges in managing and comparing differences between graphic codes due to the difficulty of using version management software like Git, which primarily handles text-based codes, and the lack of one-to-one correspondence between graphic and text codes, leading to discrepancies and repeated conversion cycles.

Innovation Solution

A method and system for converting graphic codes to text codes by inserting configuration information into annotation regions, ensuring one-to-one correspondence by using serialization encoding and decoding, and displaying positioning information to maintain code integrity during conversions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If graphic codes are converted to text codes without embedding configuration information, then the text codes can be executed in vehicle controllers, but the conversion cannot be reversed accurately leading to loss of information

Engineering Contradiction:
Improvecode conversion accuracyVSAvoidconfiguration information loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent embeds configuration information within annotation regions of the text code, creating a nested structure where graphic code metadata is contained within the text code representation. This allows the text code to carry embedded configuration data that enables accurate reverse conversion back to graphic code format.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent performs preliminary encoding of configuration information into the text code during the forward conversion process. By pre-embedding the configuration data in annotation regions before execution, the system ensures that all necessary information is preserved for future reverse conversion operations.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If version management software like Git is used to manage graphic codes, then text-based version control capabilities are available, but graphic codes cannot be properly managed due to format incompatibility

Engineering Contradiction:
Improveversion management capabilityVSAvoidcode format compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent transforms graphic code into text code representation by changing the format parameter, making it compatible with text-based version control systems like Git. The configuration information is encoded in a text-friendly format within annotation regions, enabling standard version management operations on graphic code assets.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a text-based copy of the graphic code that preserves all essential information through embedded configuration data. This text copy can be managed by version control systems while maintaining the ability to reconstruct the original graphic code when needed.

Inventive Principle:
Principle #26Copying

3Productivity

If graphic codes are repeatedly converted to text codes and back without preserving configuration information, then execution in vehicle controllers is enabled, but discrepancies accumulate requiring repeated conversion cycles

Engineering Contradiction:
Improveconversion efficiencyVSAvoidrepetitive conversion time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary embedding of configuration information during the first conversion, so that all subsequent conversions can use this preserved information to maintain accuracy. This eliminates the need for repeated manual corrections and re-conversions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The embedded configuration information acts as feedback that enables verification and correction during conversion processes. By having the original configuration data available in the text code, the system can detect and prevent discrepancy accumulation across multiple conversion cycles.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250390285A1Conversion method and conversion apparatus of text codes and graphic codes for vehicle development
Publication Date: 2025.12.25 SHANGHAI TOSUN TECH LTD
  • US20250390285A1 patent drawing
  • US20250390285A1 patent drawing
  • US20250390285A1 patent drawing

AI summary

A conversion method and conversion system of text codes and graphic codes for vehicle development. The conversion method of text codes and graphic codes for vehicle development includes: converting the graphic codes into the text codes, and while generating target text codes, inserting configuration information of each execution unit in current graphic codes into an annotation region of the target text codes; and, when converting the target text codes back to graphic codes, extracting the configuration information of the annotation region of the target text codes and loading the configuration information to restore the graphic codes.