RF Tag Authentication for Secondary User Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authentication systems lack efficient methods for secondary users to access resources controlled by primary users without direct intervention, especially in scenarios requiring varying levels of authentication based on transaction types and locations.
Innovation Solution
A system utilizing radio frequency tags (RF tags) that allow secondary users to authenticate and access resources by communicating unique identifiers to a mobile application and a back-end server, which determines approval based on pre-set permissions and primary user authorization, with the ability to differentiate between routine and non-routine transactions and track locations using a network of RF sensors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a secondary user directly accesses a resource controlled by a primary user, then access speed is improved, but security and authorization control deteriorate
Solution Approach 1:
The patent introduces a back-end server as an intermediary between the secondary user and the resource. The mobile application communicates with the back-end server, which verifies the unique identifier from the RF tag against stored authorization data and determines whether to approve the requested operation. This mediator enables automated authorization decisions without requiring direct primary user intervention for routine operations, thus maintaining security while improving access speed.
2Reliability
If the back-end contacts the primary user for every requested operation, then authorization accuracy is improved, but system complexity and response time worsen
Solution Approach 1:
The patent implements preliminary action by pre-storing authorization data in the back-end server before operations are requested. The system determines in advance which operations are routine and can be automatically approved based on pre-configured parameters. This allows the back-end server to make immediate authorization decisions for routine operations without contacting the primary user, reducing system complexity and response time while maintaining authorization accuracy through pre-established rules.
3Measurement precision
If the back-end determines each requested operation type, then authorization precision is improved, but processing time worsens
Solution Approach 1:
The system performs preliminary classification of operations by pre-determining which operations are routine and can be automatically approved versus those requiring primary user review. This pre-categorization enables the back-end server to quickly identify the authorization path for each requested operation type without extensive real-time analysis, thus maintaining high authorization precision while minimizing processing time through efficient decision routing.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
Enables secure and efficient access control for secondary users by leveraging RF tags to authenticate and authorize transactions and location tracking, reducing the need for constant primary user intervention while ensuring appropriate authentication levels for different transaction types and locations.
Implementation Method 1
Radio frequency identification uses wireless electromagnetic fields to transmit data to identify and track objects
Data Source
AI summary
Systems and methods for authentication using radio frequency tags are disclosed. In one embodiment, a method for approving a requested operation from a secondary user of a resource that is controlled by a primary user may include (1) a back end comprising at least one computer processor receiving, from a mobile application that is executed by a mobile device associated with a secondary user, a requested operation involving a resource that is controlled by a primary user; (2) the back end receiving a unique identifier from the secondary user mobile application, the unique identifier being read by the mobile application from a tag associated with the secondary user; (3) the back end determining that the received unique identifier matches a stored unique identifier that is associated with the secondary user; and (4) the back end approving the requested operation and communicating the approval to the secondary user mobile application.