Telematics Control Unit Authentication Rejection Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing control systems for vehicles fail to effectively manage attachment to mobile communications networks, particularly in cases where user authentication is rejected, leading to inefficient communication modes and potential degradation of the radio-wave environment.

Innovation Solution

A control system that includes a telematics control unit (TCU) and electronic control units (ECUs) that request position registration, handle authentication rejections by switching to alternative communication modes like wireless LAN or Bluetooth, and mask sensitive data when attachment is rejected, thereby preventing useless communications and conserving power.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the control system continues to attempt attachment to the mobile communications network after authentication rejection, then the system maintains persistent communication capability, but power consumption increases and radio-wave environment degrades

Engineering Contradiction:
Improvecommunication capabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of continuously attempting mobile network attachment after authentication rejection, the system inverts the approach by switching to alternative communication modes (wireless LAN or Bluetooth). This inversion maintains communication capability while eliminating wasteful power consumption from persistent failed attachment attempts.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The control system autonomously detects authentication rejection from the base station and automatically switches to alternative communication modes without requiring external intervention. This self-service mechanism prevents continued power-wasting attempts by the system itself.

Inventive Principle:
Principle #25Self-service

2Reliability

If the control system continues to attempt attachment to the mobile communications network after authentication rejection, then the system maintains persistent communication capability, but radio-wave environment degrades

Engineering Contradiction:
Improvecommunication capabilityVSAvoidradio-wave environment degradation
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system inverts the persistent attachment approach by switching to alternative communication modes after detecting authentication rejection. This maintains communication reliability while eliminating the harmful effect of continuous radio wave transmission from failed attachment attempts.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The system converts the harmful effect of authentication rejection (which would normally lead to persistent failed attempts) into a beneficial switch to alternative communication modes. The rejection signal triggers a mode change that eliminates radio-wave environment degradation while maintaining communication functionality.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

3Use of energy by moving object

If the control system switches to alternative communication modes upon authentication rejection, then power consumption is reduced and radio-wave environment is protected, but communication capability may be limited

Engineering Contradiction:
Improvepower consumptionVSAvoidcommunication capability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The system dynamically adapts communication modes based on authentication status. When mobile network authentication succeeds, it uses mobile communication; when rejected, it switches to wireless LAN or Bluetooth. This dynamic approach reduces power consumption while maintaining communication capability through mode flexibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The control system implements multi-functionality by supporting multiple communication modes (mobile network, wireless LAN, Bluetooth). This universality ensures that when one mode is unavailable due to authentication rejection, alternative modes can maintain communication capability without sacrificing power efficiency.

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

4Reliability

If the control system attempts continuous attachment to the mobile communications network, then communication availability is maintained, but device complexity increases

Engineering Contradiction:
Improvecommunication availabilityVSAvoidcontrol system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The control system uses dynamic mode switching based on authentication outcomes. Instead of implementing complex continuous attachment logic, it simply transitions between mobile network mode and alternative modes (wireless LAN/Bluetooth) based on whether authentication succeeds or fails, reducing control complexity while maintaining communication availability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11832327B2Control system, mobile object, control method, and computer-readable storage medium
Publication Date: 2023.11.28 HONDA MOTOR CO LTD
  • US11832327B2 patent drawing
  • US11832327B2 patent drawing
  • US11832327B2 patent drawing

AI summary

A control system includes: a mobile object controller configured to control a mobile object; and a communications controller configured to control mobile communications via a mobile communications network. When the communications controller requests attachment to the mobile communications network and acquires rejection information of the attachment to the mobile communications network having been rejected, the communications controller is configured to notify the mobile object controller that the attachment has been rejected. A control method includes: requesting attachment to a mobile communications network; and when rejection information of the attachment to the mobile communications network having been rejected is acquired, notifying a mobile object controller connected to a network inside a mobile object and configured to control the mobile object that the attachment has been rejected.