Vehicular ECU Service Management for Dynamic Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicular electronic control units lack a mechanism to dynamically and interoperably use functions of multiple networked units, limiting application development and flexibility.

Innovation Solution

A vehicular electronic control unit (ECU) with a service interface, service bus, and service manager that enables dynamic and interoperable service usage by managing service positions and facilitating message transmission between ECUs, allowing applications to request and utilize functions from other ECUs without restarting the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional vehicular ECUs are used without a service management mechanism, then each ECU operates independently with fixed functions, but the system lacks flexibility and interoperability between different ECUs

Engineering Contradiction:
Improveinteroperability between ECUsVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is segmented into independent service providers and service users, where each ECU can function as either or both roles. Services are divided into discrete, manageable units that can be independently developed, deployed, and orchestrated across different ECUs without requiring system-wide redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service management mechanism provides universal interfaces and protocols that enable any ECU to provide or consume services regardless of its specific function. This multi-functionality allows engine ECUs, body ECUs, and navigation ECUs to interoperate through a common service framework, achieving system-wide versatility.

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

2Ease of operation

If applications directly access lower application layers, then specific functions can be accessed, but application developers must consider lower layer details which limits development flexibility

Engineering Contradiction:
Improveapplication development easeVSAvoidlayer interaction complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The service management mechanism acts as an intermediary layer between applications and lower application layers. Applications interact with services through standardized interfaces, and the service management mechanism handles the complexity of locating, invoking, and managing service instances, shielding developers from lower layer details.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Services automatically manage their own registration, discovery, and invocation through the service management mechanism. This self-service capability eliminates the need for applications to manually configure or manage service instances, reducing development complexity and improving ease of operation.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If the system uses static service configuration, then system structure is simple, but services cannot be dynamically added or removed without restarting the system

Engineering Contradiction:
Improvedynamic service usageVSAvoidservice continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The service management mechanism enables dynamic service configuration where services can be registered, updated, and removed at runtime without system restart. The orchestration mechanism dynamically adjusts service invocations based on current service availability, allowing the system to adapt to changing conditions while maintaining continuous operation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service management mechanism implements feedback loops that monitor service status, availability, and performance in real-time. This feedback enables automatic service discovery, load balancing, and failover, ensuring service continuity while allowing dynamic configuration changes without system restart.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10163272B2Vehicular electronic control unit and vehicular service management system
Publication Date: 2018.12.25 DENSO CORP
  • US10163272B2 patent drawing
  • US10163272B2 patent drawing
  • US10163272B2 patent drawing

AI summary

A vehicular ECU (electronic control unit) is any one of a plurality of vehicular ECUs connected to an in-vehicle network in a vehicle and includes: a service interface, a service bus, and a service manager. The service interface issues a request of service that uses a function installed in a different vehicular ECU based on a request from the application, and makes the application generate a service as a response to a request of service from the different vehicular ECU. The service bus transmits and receives a message corresponding to a request of service and a response by using a predetermined protocol between the service interfaces of the vehicular ECU and the different vehicular ECU. The service manager achieves the service to be dynamically and interoperably used by managing a position of the service.