NFC Authentication ID Management in Communication Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods using NFC tags and terminal devices face inefficiencies in managing and verifying authentication IDs, particularly in establishing and maintaining secure communication sessions for function permissions.
Innovation Solution
A communication system comprising a multi-function peripheral (MFP) and mobile terminals that utilize NFC for short-distance wireless communication, where the MFP supplies identification and authentication information to the mobile terminals, allowing for registration and authentication processes to be executed securely and efficiently, with the MFP updating authentication IDs and managing permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If authentication ID is stored in NFC tag for authentication, then authentication function is provided, but processing load on communication device increases and efficiency decreases
Solution Approach 1:
The patent extracts the authentication ID storage function from the communication device and relocates it to the terminal device's non-volatile memory. The communication device only maintains authentication ID lists, while individual terminal devices store their own authentication IDs locally, thereby reducing the processing load on the communication device and improving authentication efficiency.
Solution Approach 2:
The terminal device performs self-authentication by using its stored authentication ID to verify itself against the authentication ID list on the communication device. This eliminates the need for the communication device to manage and verify authentication IDs for multiple terminals, significantly reducing its processing load and improving overall system efficiency.
2Reliability
If authentication ID is stored in volatile memory area of terminal device, then authentication information can be sent, but data loss occurs when communication session is disconnected
Solution Approach 1:
The patent implements preliminary action by storing the authentication ID in the terminal device's non-volatile memory area before any communication session occurs. This ensures that the authentication information is persistently saved and will not be lost when the communication session is disconnected or the device is restarted, thereby improving data reliability.
3Ease of operation
If authentication ID is pre-registered in communication device, then authentication can be executed, but management and verification of authentication IDs becomes complex
Solution Approach 1:
The patent extracts the authentication ID storage responsibility from the communication device and assigns it to individual terminal devices. The communication device only maintains a list of valid authentication IDs for verification, while each terminal device stores its own authentication ID locally. This division of responsibilities simplifies the management and verification processes.
Solution Approach 2:
Each terminal device performs self-management of its authentication ID by storing it in its own non-volatile memory. This eliminates the need for the communication device to manage authentication IDs for multiple terminals, significantly simplifying the overall authentication ID management and verification processes.
Data Source
AI summary
A communication device may supply both identification information for identifying a specific application program and first authentication information to a wireless interface so as to store both the identification information and the first authentication information in an interface memory. The wireless interface may be configured to send both the identification information and the first authentication information in the interface memory to a first terminal device by using a first communication session. The communication device may receive the first authentication information from the first terminal device by using a second communication session in a case where the second communication session with the first terminal device in which a specific application program has been installed is established via the wireless interface, and execute an authentication using the first authentication information in a case where the first authentication information is received.