Message Access Layer Frame for Cloud Service Request Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud computing systems face issues with unbalanced access frequency among front ends, security threats due to independent authentication, and high development workload for the access layer, which requires repeated development for each front end.
Innovation Solution
A message access layer frame comprising a controller, receiver, account password checker, session processor, and repeater, which translates and handles requests across different protocols, manages login and rights, and provides single sign-on, while reducing the need for repeated development and enhancing security by centralizing access management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If independent access layer development is performed for each front end, then each front end can be customized according to specific requirements, but the development workload increases significantly and code repetition occurs
Solution Approach 1:
The patent implements a universal access layer framework that serves multiple front ends simultaneously. The framework includes reusable components such as the receiver module, account password checker, session processor, and repeater that can handle different protocols and front end types through configuration rather than code modification, thereby eliminating repeated development while maintaining adaptability
Solution Approach 2:
The access layer is segmented into independent functional modules (receiver, account password checker, session processor, repeater) that can be independently developed, configured, and reused across different front ends. This modular architecture allows the system to handle multiple front end requirements through configuration combinations rather than separate implementations
2Ease of operation
If all front ends connect to the back end independently, then each front end has direct access control, but the access frequency becomes unbalanced and excessive pressure is applied to the back end
Solution Approach 1:
The patent introduces an access layer framework as an intermediary between front ends and the back end. This intermediary layer includes a receiver that accepts requests from multiple front ends, a session processor that manages authentication and authorization, and a repeater that forwards validated requests to the back end. This mediation balances the load by centralizing access control logic and preventing direct unbalanced connections to the back end
Solution Approach 2:
The patent merges the access control functionality of multiple front ends into a single unified access layer framework. Instead of each front end having independent access control logic, the framework consolidates authentication, authorization, and request management in centralized components that serve all front ends, thereby balancing the access load on the back end
3Adaptability or versatility
If independent account authentication is implemented for each front end, then each front end has its own authentication logic, but security threats to the authentication database increase
Solution Approach 1:
The patent merges the authentication functionality of all front ends into a single centralized account password checker within the access layer framework. This unified authentication component validates credentials against the authentication database using standardized logic, reducing the security surface area compared to multiple distributed authentication implementations while maintaining the ability to support different front end requirements through configuration
Data Source
AI summary
A message access layer frame and an implementation method thereof are provided, relating to a technical field of software. After initiating a system, a controller parses a configuration file, initiates a database access service unit and initializes and initiates other components. After an application front end sends a request, a receiver receives the request of the application front end, translates the request into data in a consistent format and sends the data in the consistent format to a next handling module. An account password checker and a session processor, serving as main information handling modules of the frame, handle a client request and send the handled client request to the repeater. A repeater translates the handled data in the consistent format into data acceptable to an application back end and sends the data acceptable to the application back end to the application back end for a data handling by cloud.