Front-End Content Authorization via Back-End Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Back-end systems face bottlenecks and inefficient bandwidth usage when handling voluminous data for content requests, leading to slowed data transfer and increased network resource utilization, as they often need to transmit content between systems and then to user devices.
Innovation Solution
Implementing a system where a front-end system dynamically authorizes access to content stored on separate locations based on operation logic from a remote back-end system, allowing direct content transmission from the front-end to user devices, reducing the need for back-end to front-end data transfer and optimizing network resource use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If back-end systems transmit and process voluminous data for content requests, then content can be securely distributed, but network bandwidth is unnecessarily consumed and data transfer speed decreases
Solution Approach 1:
The system segments the content distribution function by separating the back-end system (which stores operation logic) from the front-end system (which stores content and handles transmission). This segmentation allows the back-end to authorize access without transmitting the actual content, improving both security and speed.
Solution Approach 2:
The invention extracts the content transmission function from the back-end system and relocates it to the front-end system. The back-end system retains only the authorization function, while the front-end system handles content storage and direct transmission to user devices, eliminating unnecessary data movement through the back-end.
2Reliability
If back-end systems process voluminous data for multiple content requests, then authorization can be centrally managed, but system bottlenecks occur and productivity decreases
Solution Approach 1:
The invention extracts the content processing and transmission functions from the back-end system, leaving only the lightweight authorization logic. This extraction eliminates the bottleneck by allowing the front-end system to handle content requests directly without back-end intervention in the data transmission path.
Solution Approach 2:
The front-end system acts as an intermediary between the back-end authorization system and user devices. It receives authorization tokens from the back-end and uses them to directly serve content requests, improving system throughput while maintaining centralized authorization control.
3Reliability
If back-end systems transmit content to front-end systems for every request, then content access can be controlled, but network resource consumption increases
Solution Approach 1:
The system performs preliminary authorization action by issuing tokens before content requests. The back-end system authorizes the front-end system in advance with tokens that contain authorization information, eliminating the need for repeated content transmission through the back-end for each request.
Solution Approach 2:
The invention uses authorization tokens as copies of authorization information. Instead of transmitting actual content through the back-end system, the front-end system receives token copies containing authorization data and uses these to directly serve content, dramatically reducing network bandwidth consumption.
Data Source
AI summary
Systems and methods are provided for dynamically authorizing access to content stored on a front-end system by one or more applications hosted on a remote back-end system. The content stored on the front-end system may be static files. The front-end system may store content in distinct content storage locations. Each content storage location may correspond to a respective application hosted by the back-end system. In one embodiment, there may be multiple back-end systems each hosting one or more applications. Each application on the back-end system may employ operation logic to determine authorization to a content storage location associated with the application.


