Terminal Operation Processing Without Repeated Login
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users experience poor user experience due to frequent login requirements when using browsers on terminals, as session validity periods are short, leading to frequent account name and password re-entry, especially on mobile devices, and existing solutions like SMS verification can be inconvenient and costly.
Innovation Solution
A method and apparatus for processing user operations on a terminal and server, where a web page includes a first control element to acquire an account identifier and a second control element to correlate the identifier with an operation request, allowing the account identifier and request to be sent to the server without re-entering credentials, using stored identifiers or user input, and monitoring trigger actions to meet preset conditions for authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server sets a short validity period for session, then security is improved, but user experience deteriorates due to frequent re-login requirements
Solution Approach 1:
The patent applies preliminary action by pre-storing account identifiers in the terminal before the user needs to perform operations. When a user accesses a web page, the system checks whether an account identifier is stored in advance. If stored, the system automatically uses it to correlate with operation requests, eliminating the need for users to re-enter credentials during the session validity period.
Solution Approach 2:
The patent introduces an intermediary mechanism by using the account identifier as a mediator between the user and the server. Instead of directly transmitting passwords or requiring repeated authentication, the system uses the pre-stored account identifier to establish a correlation with operation requests, serving as an intermediary that enables seamless operations without direct credential re-entry.
2Reliability
If the browser uses traditional login methods, then security monitoring is improved, but operation efficiency deteriorates due to frequent page jumping and re-login
Solution Approach 1:
The patent merges the login authentication process with the operation request processing. By combining the account identifier storage, operation request correlation, and server verification into a unified flow, the system eliminates separate login pages and reduces page jumping. The account identifier serves as both authentication proof and operation correlation key, merging security verification with operational efficiency.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining the account identifier correlation throughout the session validity period. Once an account identifier is stored and correlated with operation requests, the system continuously uses this correlation to process subsequent operations without interruption or re-login, ensuring seamless and efficient user interactions throughout the session.
3Reliability
If SMS verification is used for authentication, then security is improved, but convenience and cost deteriorate due to additional steps and expenses
Solution Approach 1:
The patent extracts the essential authentication function from complex SMS verification processes. Instead of using SMS codes that require sending, receiving, and entering additional information, the system extracts and uses the account identifier directly stored in the terminal. This extraction simplifies the authentication process while maintaining security, eliminating the need for SMS verification steps and associated costs.
Data Source
AI summary
The present disclosure provides systems and methods for processing operation. An exemplary method for processing operation, implementable by a terminal, may comprise: displaying a target web page, wherein the target web page comprises a first control element and a second control element, the first control element is configured to acquire an account identifier for an account, and the second control element is configured to correlate the account identifier and an operation request for executing the operation request without logging in the account after the operation request is correlated with the account identifier; acquiring the account identifier in response to a trigger action on the second control element; and sending the account identifier and the operation request that is correlated by the second control element to a server corresponding to the target web page.