Device Management System for Rental Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of user authentication in rental device services, particularly for high-priced devices like notebook computers, tablets, and smartphones, requires both user and device identification, leading to unnecessary login requirements.

Innovation Solution

A device management system that includes a terminal for user authentication and a server managing rental devices, where the terminal transmits user and device information to the server, allowing the server to acquire a unique device code and unlock the device, enabling automatic login upon device removal from the storage box.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user authentication is performed before rental device usage, then user identification is ensured, but user authentication complexity increases due to requiring login again

Engineering Contradiction:
Improveuser identificationVSAvoidauthentication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs user authentication in advance during the rental process, and stores the authentication result. When the rental device is later used, the system automatically logs in using the pre-stored authentication information, eliminating the need for users to authenticate again. This applies preliminary action by completing authentication before the device usage phase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the user authentication information obtained during rental and uses this copy for automatic login during device usage. Instead of requiring fresh authentication, the system replicates the authentication credentials and applies them automatically, reducing complexity while maintaining security.

Inventive Principle:
Principle #26Copying

2Ease of operation

If automatic login is implemented upon device removal, then authentication complexity is reduced, but device and user identification accuracy must be ensured

Engineering Contradiction:
Improveauthentication processVSAvoididentification accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The system uses feedback from multiple identification points: the terminal provides user authentication information, the box provides box unique code, and the rental device provides device unique code. This multi-source feedback mechanism ensures accurate matching of user, device, and storage location, enabling automatic login while maintaining high identification accuracy.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The server performs multiple functions: it manages rental information, stores authentication data, identifies users, and enables automatic login. By consolidating these functions in a centralized system that processes information from multiple sources (terminal, box, device), the system achieves both ease of operation and identification accuracy through a universal management approach.

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

Data Source

PatentUS20230260014A1Device management system
Publication Date: 2023.08.17 NTT DOCOMO INC
  • US20230260014A1 patent drawing
  • US20230260014A1 patent drawing
  • US20230260014A1 patent drawing

AI summary

In a device management system 1 including a terminal 20 and a server 10 for managing a device 50 stored in a box 40, the terminal 20 includes: a transmission unit 23 that transmits information associated 5 with the device 50 and user authentication information to the server 10, and the server 10 includes: a unique device code acquisition unit 12 that acquires a unique device code from information associated with the device 50; a lock control unit 13 that instructs the box 40 to unlock; and a login control unit 14 that identifies a user based on the user 10 authentication information and allows the identified user to log in to the device 50 when the box 40 or the device 50 notifies that the device 50 has been taken out with an event indicating that the device 50 has been taken out of the box 40 as a trigger.