Modular Vehicle Frame and Software Update Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional electric and hybrid-electric vehicles are limited by standard frame sizes, shapes, and materials, failing to leverage new technologies and infrastructure, and lack adaptability to changing demands and safety advancements.

Innovation Solution

The vehicle system incorporates a modular frame with interchangeable subsystems and advanced power management, including redundant power distribution and energy recovery systems, enabling quick component exchange, enhanced safety, and efficient energy sharing between vehicles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard frame sizes and shapes are used in traditional vehicles, then manufacturing is simplified, but adaptability to new technologies and changing demands is reduced

Engineering Contradiction:
Improveadaptability to technological advancementsVSAvoidframe structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The vehicle frame is divided into modular sections with standardized interfaces, allowing independent replacement and reconfiguration of subsystems. This segmentation enables the frame to adapt to different technologies while maintaining a manageable overall structure through modular design principles.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The frame structure incorporates universal mounting points and standardized connection interfaces that can accommodate multiple types of subsystems and power sources. This multi-functionality allows the same frame to support different configurations for various technological advancements without requiring complete redesign.

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

2Reliability

If software updates are performed by overwriting existing code, then storage space is optimized, but system reliability is reduced due to loss of backup versions

Engineering Contradiction:
Improvesystem reliability during updatesVSAvoidmemory storage requirement
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system maintains backup copies of previous software versions in memory before performing updates. This beforehand cushioning ensures that if an update fails or introduces errors, the system can revert to the previous working version, thereby protecting system reliability at the cost of additional temporary storage requirements.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

Instead of directly overwriting existing software code, the system creates copies of update packages and maintains multiple version copies in memory. This copying approach allows for safe testing and verification of updates before full deployment, improving reliability while managing storage through selective retention of critical backup versions.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If a pointer is set to point to the first image of operating system code, then system startup is simplified, but flexibility to switch between versions is reduced

Engineering Contradiction:
Improveflexibility to switch software versionsVSAvoidpointer management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The pointer managing software versions is made dynamic rather than fixed, allowing it to be reconfigured to point to different software images as needed. This dynamic pointer can be updated through standardized interfaces to switch between different operating system versions, providing flexibility while maintaining relatively simple pointer management through centralized control mechanisms.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10209981B2Structure for updating software in remote device
Publication Date: 2019.02.19 NIO TECH ANHUI CO LTD
  • US10209981B2 patent drawing
  • US10209981B2 patent drawing
  • US10209981B2 patent drawing

AI summary

According to one embodiment, updating software in a remote device comprises operating on a first image of an operating system code, updating to a second image of the operating system code, wherein updating to the second image comprises operating on the second image while maintaining the first image in memory, and in response to detecting an error in operating on the second image, operating on the first image of the operating system code maintained in the memory accessible by the ECU. Operating on the first image of the operating system code can comprise saving the first image in the memory and executing the first image based on a pointer to the first image. Updating can comprise saving the second image without overwriting or erasing the first image and executing the second image based on a pointer to the second image.