Beacon Authentication API for Secure Resource Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack a secure mechanism for API authentication and authorization that can restrict the range and number of resources available based on beacon area information, particularly for mobile terminals using Bluetooth Low Energy.
Innovation Solution
An information processing system employing OAuth 2.0 standards, with an authentication unit verifying terminal identification and issuing authorization tokens, allowing resource access based on beacon-specific conditions, thereby controlling resource availability and usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a secure mechanism for API authentication and authorization is implemented to restrict resource access based on beacon area information, then security and control over resource availability are improved, but system complexity increases
Solution Approach 1:
The patent introduces a server as an intermediary component that handles authentication and authorization between mobile terminals and resources. The server receives beacon information from terminals, validates it against stored beacon data, and controls resource access accordingly. This mediator approach improves security by centralizing authentication logic while keeping the terminal system relatively simple.
Solution Approach 2:
The system segments authentication and authorization functions into distinct modules: beacon information reception, beacon validation, authorization token issuance, and resource access control. This segmentation allows each component to be independently implemented and maintained, improving overall system reliability while managing complexity through functional decomposition.
2Adaptability or versatility
If resource access is restricted based on beacon area information and authorization tokens, then control over resource usage range and number is improved, but ease of operation deteriorates
Solution Approach 1:
The system implements self-service authentication where mobile terminals automatically perform beacon scanning and present beacon information to the server for validation. Users don't need to manually configure access rights or remember credentials - the system automatically handles authentication based on the beacon signal, improving ease of operation while maintaining strict access control.
Solution Approach 2:
Beacon information and authorization rules are pre-configured on the server before actual resource access occurs. The server stores beacon data, area information, and resource access policies in advance. When a terminal presents a beacon, the server quickly matches it against pre-configured rules, enabling fast authorization decisions without complex real-time computations.
3Reliability
If authorization tokens are issued and verified for each resource request, then security and authorization control are improved, but processing time increases
Solution Approach 1:
Instead of repeatedly validating the entire beacon information and authorization rules for each resource request, the system creates authorization tokens that copy and encapsulate the essential authorization data. These tokens are issued once after initial beacon validation and then quickly verified for subsequent resource requests, dramatically reducing processing time while maintaining security.
Solution Approach 2:
The system performs the complex beacon validation and authorization decision-making in advance, before the actual resource request occurs. Authorization tokens are issued preliminarily based on pre-configured rules, so that subsequent resource access only requires simple token verification rather than full re-validation, reducing processing time for each request.
Data Source
AI summary
There are provided a beacon authentication API that obtains identification information of a terminal and performs authentication if a resource is provided to an application of a terminal via network and if the terminal receives a beacon transmitted from a beacon transmitter, and an authorization API that issues an authorization token if the authentication is performed by the beacon authentication API, wherein the authorization API verifies whether or not the authorization token is valid if there is a call request of the resource by using the authorization token from the terminal, and wherein the beacon authentication API permits the application to use the resource in accordance with the content of an event based on the beacon if the authorization token is verified to be valid.