Trunk Share Server Authentication Logic for Secure Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the trunk share system, delivery articles requiring confirmation of delivery suitability, such as registered mail or cash-on-delivery items, face issues like unauthorized delivery and unsettled payments due to the lack of authentication assurance when authentication information is shared before suitability confirmation.

Innovation Solution

A server device acquires vehicle information and authentication details, ensuring that authentication information is only transmitted to the delivery terminal if proof of the recipient's rightful ownership and payment confirmation is obtained, preventing unauthorized access and ensuring payment settlement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If authentication information is issued to the delivery terminal before delivery suitability is confirmed, then delivery work can proceed efficiently, but unauthorized delivery and payment settlement issues may occur

Engineering Contradiction:
Improvedelivery work efficiencyVSAvoiddelivery authorization reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary confirmation of delivery suitability by communicating with the user terminal before issuing authentication information to the delivery terminal. This preliminary action ensures that authentication is only provided after verifying the delivery article requires no special confirmation, thus preventing unauthorized delivery while maintaining efficiency for standard deliveries.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback loop where the delivery management server communicates with the user terminal to confirm delivery suitability before authorizing the delivery terminal. This feedback mechanism ensures that authentication information is only issued after proper verification, resolving the contradiction between efficiency and reliability.

Inventive Principle:
Principle #23Feedback

2Reliability

If authentication information is withheld until delivery suitability is confirmed, then unauthorized delivery is prevented, but delivery work efficiency decreases

Engineering Contradiction:
Improvedelivery authorization reliabilityVSAvoiddelivery work efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary confirmation of delivery suitability through automated communication with the user terminal before the delivery terminal needs authentication. This preliminary action ensures reliability is maintained while avoiding delays during the actual delivery process, as authentication is ready when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The user terminal automatically responds to confirmation requests from the delivery management server, enabling self-service verification of delivery suitability. This automation eliminates manual intervention delays while ensuring reliable authentication, thus maintaining both reliability and efficiency.

Inventive Principle:
Principle #25Self-service

3Reliability

If the system communicates with the user terminal to confirm delivery suitability, then payment settlement and authorization reliability improve, but system complexity increases

Engineering Contradiction:
Improvepayment settlement reliabilityVSAvoidsystem communication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The user terminal serves multiple functions: it receives delivery requests, provides authentication information, and confirms delivery suitability. By making the terminal multi-functional, the system avoids adding separate verification devices, thus improving payment settlement reliability without significantly increasing system complexity.

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

Solution Approach 2:

The delivery management server acts as an intermediary that coordinates between the user terminal and delivery terminal. It handles the confirmation communication automatically, simplifying the interaction model while ensuring reliable payment settlement verification without requiring complex direct communication between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11321794B2Server device, trunk share system, information processing method, and non-transitory computer-readable medium storing information processing program
Publication Date: 2022.05.03 TOYOTA JIDOSHA KK
  • US11321794B2 patent drawing
  • US11321794B2 patent drawing
  • US11321794B2 patent drawing

AI summary

A server device includes a processor configured to i) acquire vehicle information when a delivery request is made; ii) acquire predetermined authentication information for unlocking and locking a door of a vehicle, based on the acquired vehicle information; iii) transmit the acquired predetermined authentication information to a delivery terminal; and iv) to acquire predetermined proof information for proving that a user of the vehicle is a rightful recipient of a delivery article, by communicating with a user terminal. The processor is configured to transmit the acquired predetermined authentication information to the delivery terminal, on a condition that the predetermined proof information is acquired.