Non-networked Multi-function Device Local Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-function devices (MFDs) are expensive to purchase and maintain, and shared MFDs connected to networks pose security risks due to potential hacking, making it difficult for businesses to share costs and manage usage effectively in multi-tenant environments.
Innovation Solution
A non-networked multi-function device that uses a communication interface to establish a local connection with mobile endpoint devices for authentication and function execution, allowing each tenant to access and track usage independently, with usage rights and available functions controlled through a mobile application, and usage information tracked locally or remotely.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MFDs are connected to networks to enable authentication and usage tracking, then multi-tenant sharing and cost management become possible, but security risks increase due to potential hacking
Solution Approach 1:
The patent extracts the network connection component from the MFD system, creating a standalone offline device that maintains multi-tenant functionality through local authentication mechanisms. The MFD operates independently without requiring network connectivity, thereby eliminating security vulnerabilities associated with network hacking while preserving the ability to authenticate multiple users and track usage through local storage and processing capabilities.
2Reliability
If MFDs are placed in centralized locations for security monitoring, then security management improves, but placement flexibility decreases
Solution Approach 1:
The MFD performs self-authentication and self-monitoring through local authentication credentials stored on the device itself. Each MFD independently verifies user credentials and tracks usage without requiring centralized monitoring infrastructure. This self-service capability enables the device to be placed in diverse locations including remote or mobile settings while maintaining security management integrity.
3Ease of operation
If MFDs require network connectivity for authentication, then centralized control and tracking are achieved, but device complexity and maintenance costs increase
Solution Approach 1:
The authentication and control functionality is segmented from centralized network services and distributed to individual MFD units. Each device contains local authentication credentials and can independently verify users without requiring continuous network communication. This segmentation eliminates the need for complex network infrastructure while maintaining centralized-like control through locally stored authentication data and usage tracking capabilities.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A non-networked multi-function device (MFD) is disclosed. For example, the non-networked MFD includes a communication interface to establish a communication session with a mobile endpoint device, a memory to store authentication information, and a processor. The processor is to receive a connection request from a mobile endpoint device, establish a connection with the mobile endpoint device, authenticate the mobile endpoint device via authentication information received from the mobile endpoint device that matches authentication information stored in the memory, provide available functions to the mobile endpoint device, receive a request from the mobile endpoint device to execute a function from the available functions, and execute the function.