CN118214610B - Login state maintaining method and system - Google Patents

Abstract

The present invention relates to the field of the Internet, and provides a method and system for maintaining a login status, wherein the method for maintaining a login status comprises: interacting with a login terminal to generate a cookie matching the login terminal; receiving a cookie saving request from the login terminal, and placing the cookie saving request in an asynchronous queue; the login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie. The method is used to solve the defect in the prior art that it is difficult to ensure that users can successfully log in to an office system anytime and anywhere due to network fluctuations, and can maintain the login status of users, and realize intelligent office processing using limited server resources.

Description

Login status maintenance method and system

Technical Field

The present invention relates to the field of Internet technology, and in particular to a method and system for maintaining a login status.

Background Art

When users log in to the office system, it is difficult to ensure that they can log in smoothly anytime and anywhere due to network fluctuations. In addition, for the sake of service stability, the server side of some office systems usually limits the number of logins for the same user to avoid multiple frequent logins. Under such circumstances, it is very likely to affect the user's normal work.

Based on this, there is an urgent need for a solution that can maintain the user's login status and use limited server resources to achieve intelligent office processing.

Summary of the invention

The present invention provides a login status maintaining method and system, which are used to solve the defect in the prior art that it is difficult to ensure that users can successfully log in to the office system anytime and anywhere due to network fluctuations. The method and system can maintain the user's login status and realize intelligent office processing by using limited server resources.

The present invention provides a method for maintaining a login status, comprising:

Interact with the login terminal and generate a cookie that matches the login terminal;

Receive the cookie saving request from the login terminal and put the cookie saving request into the asynchronous queue;

The login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

According to the login status maintaining method provided by the present invention, after generating a cookie matching the login terminal, the method further includes:

Verify the cookie, and if the verification passes, store the cookie in the login terminal.

According to the login status maintaining method provided by the present invention, a cookie saving request from a login terminal is received, and the cookie saving request is placed in an asynchronous queue, including:

Receive the heartbeat request from the login terminal and send a reply instruction to the login terminal to maintain the heartbeat connection with the login terminal.

According to the login status maintaining method provided by the present invention, the cookie saving request is an API maintaining request, and the heartbeat request of the login terminal is a non-blocking request.

According to the login status maintaining method provided by the present invention, the cookie saving request is a driver maintaining request, and the login terminal sends a heartbeat request by continuously refreshing.

According to the login status maintaining method provided by the present invention, the login terminal sends a heartbeat request at random intervals of N minutes until no reply instruction is received.

The method for maintaining the login status according to the present invention further includes:

The login status is recorded through asynchronous logs.

The present invention also provides a login status maintaining system, comprising:

A generation module, used to interact with the login terminal and generate a cookie matching the login terminal;

The receiving module is used to receive the cookie saving request from the login terminal and put the cookie saving request into the asynchronous queue;

The maintenance module is used for the login terminal to save the cookie. The login terminal maintains the login status of the login terminal based on the cookie.

The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, any of the above-mentioned methods for maintaining a login status is implemented.

The present invention also provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any of the above-mentioned login status maintaining methods is implemented.

The present invention also provides a computer program product, including a computer program, and when the computer program is executed by a processor, any of the above-mentioned login status maintaining methods is implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the present invention or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a flow chart of a method for maintaining a login status according to an embodiment of the present invention;

2 is a schematic diagram of the structure of a login status maintaining system provided in an embodiment of the present invention;

3 is a second flow chart of a method for maintaining a login status according to an embodiment of the present invention;

4 is a third flow chart of a method for maintaining a login status according to an embodiment of the present invention;

5 is a fourth flow chart of a method for maintaining a login status according to an embodiment of the present invention;

6 is a flowchart of a method for maintaining a login status according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

FIG. 1 is a flow chart of a method for maintaining a login status according to an embodiment of the present invention.

As shown in FIG1 , this embodiment provides a method for maintaining a login status, including:

Step 101, interacting with a login terminal to generate a cookie matching the login terminal;

Step 102, receiving a cookie saving request from the login terminal, and placing the cookie saving request into an asynchronous queue;

Step 103: The login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

In practical applications, the login status maintenance method provided in this embodiment can be applied to the field of tax reporting. Specifically, in the prior art, facing the complex and changeable network environment and the limitations of tax reporting login at the bureau end, it is difficult to ensure that users can log in to the tax office system anytime and anywhere to perform remote tax reporting operations. Based on this, the solution provided in this embodiment can enable users to maintain the login status after logging in once, and realize intelligent tax processing with limited resources.

The use of an asynchronous queue in step 102 has the benefits of improving concurrency and throughput, as follows:

In multi-threaded programming, it may take a long time for a thread to complete a task. If the next thread starts working after waiting for the thread to complete the task, the concurrency of the program will be greatly reduced. Asynchronous queues can store pending tasks and allow multiple threads to take tasks from the queue for processing at the same time, which improves concurrency and fully utilizes the computing power of multi-core processors.

Since asynchronous queues allow multiple threads to process tasks simultaneously, the throughput of the program can be significantly improved. This is very important for applications that need to process a large number of requests.

In an exemplary embodiment, after generating a cookie matching the login terminal, the method further includes:

Verify the cookie, and if the verification passes, store the cookie in the login terminal.

In an exemplary embodiment, receiving a cookie saving request from a login terminal and placing the cookie saving request in an asynchronous queue includes:

Receive the heartbeat request from the login terminal and send a reply instruction to the login terminal to maintain the heartbeat connection with the login terminal.

In an exemplary embodiment, the cookie preservation request is an API retention request, and the heartbeat request of the login terminal is a non-blocking request.

In an exemplary embodiment, the cookie saving request is a driver retention request, and the login terminal sends a heartbeat request by continuously refreshing.

In an exemplary embodiment, the login terminal sends a heartbeat request at random intervals of N minutes until no reply instruction is received.

In an exemplary embodiment, it further includes:

The login status is recorded through asynchronous logs.

The login status maintaining system provided by the present invention is described below. The login status maintaining system described below and the login status maintaining method described above can be referenced to each other.

FIG. 2 is a schematic diagram of the structure of a login status maintaining system provided in an embodiment of the present invention.

As shown in FIG2 , the login status maintaining system provided in this embodiment includes:

A generation module 201 is used to interact with a login terminal and generate a cookie matching the login terminal;

The receiving module 202 is used to receive a cookie saving request from a login terminal and place the cookie saving request into an asynchronous queue;

The maintaining module 203 is used for the login terminal to save the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

In an exemplary embodiment, a verification module is also included, and the verification module is specifically used to: verify the cookie, and after the verification passes, store the cookie in the login terminal.

In an exemplary embodiment, the receiving module 202 is further used to: receive a heartbeat request from the login terminal, and send a reply instruction to the login terminal to maintain a heartbeat connection with the login terminal.

In an exemplary embodiment, the cookie saving request is an API holding request, and the heartbeat request of the login terminal is a non-blocking request.

In an exemplary embodiment, the cookie saving request is a driver retention request, and the login terminal sends a heartbeat request by continuously refreshing.

In an exemplary embodiment, the login terminal sends a heartbeat request at random intervals of N minutes until no reply instruction is received.

In an exemplary embodiment, a recording module is also included, and the recording module is specifically used for:

The login status is recorded through asynchronous logs.

The specific implementation method of the login status maintaining system provided in this embodiment can be implemented with reference to the above embodiment and will not be described in detail here.

The following provides a specific embodiment to illustrate the login status maintenance method provided by the present application.

FIG. 3 is a second flow chart of the method for maintaining the login status provided in an embodiment of the present invention.

FIG. 4 is a third flow chart of the method for maintaining the login status provided in an embodiment of the present invention.

FIG. 5 is a fourth flow chart of the method for maintaining the login status provided in an embodiment of the present invention.

FIG. 6 is a fifth flowchart of the method for maintaining a login status provided in an embodiment of the present invention.

FIG. 3 is a schematic diagram of a specific flow chart of a method for maintaining a login status according to an embodiment of the present invention, and FIGS. 4 to 6 are timing diagrams of three different login modes according to an embodiment of the present invention.

As shown in FIG3 , the method for maintaining the login status provided in this embodiment includes:

1. Obtain cookie task. In this step, there are different ways to obtain cookies depending on the login terminal. Specifically, when the login terminal is an ordinary mobile terminal, after the first login is successful, the mobile terminal interacts with the server and saves cookies, and maintains a heartbeat connection with the server to maintain the session state; when the login terminal is a fixed device, a larger driver pool can be managed by a group of machines. When logging in, each driver can open the login interface and send the QR code to the middle station for scanning and verification. Once the QR code is scanned by the user and the login is successful, it will interact with the server to obtain and save cookies, and maintain a heartbeat connection with the server.

2. Receive a cookie saving request from the login terminal and verify some fields of the cookie. For example, when the login status maintenance method provided in this embodiment is applied to tax declaration services, it can be verified whether the tax number length is 18 digits;

3. After the verification is passed, the cookie is stored in redis, and the task of keeping the cookie is placed in the asynchronous queue. The asynchronous queue will distribute the task to the machine group used to keep the cookie heartbeat;

4. After receiving the cookie save request, the machines in the machine group that maintains the cookie heartbeat are divided into two modes: API request preservation and driver preservation according to the different cookie types in the cookie save request. For API request preservation, aiohttp can be used to send non-blocking requests to maintain the heartbeat of the server; for driver preservation, a driver object can be randomly obtained from the pre-established asynchronous driver pool, and the driver object will be continuously refreshed to maintain the heartbeat;

5. Maintain the heartbeat connection at random intervals of N minutes until the heartbeat connection reaches the maximum duration or the heartbeat fails, then you need to log in again. Once it is determined that the heartbeat connection has reached the maximum duration or the heartbeat fails, the resources will be released, and you can close the API request or release the driver.

6. After the resources are released, the invalid cookies in redis can be deleted;

7. The entire process mentioned above can be recorded through asynchronous logs.

The Playwright head in Figure 3 refers to Playwright running the browser's automated operation with a UI interface;

Playwright headless means that Playwright runs the browser's automated operations without a UI interface.

As shown in FIG. 4 , this embodiment illustrates a login process for maintaining the login status through an API, including:

The first time a client logs in through RPA, after successful login, it sends a request to the server with the cookie and specifies the refresh mode as API. After receiving the cookie, the server saves the cookie to redis and inserts a cookie task into the MQ message queue.

The MQ message queue distributes tasks to the refresh robot, and the robot executes API requests to refresh the cookie regularly until the cookie expires or reaches the maximum retention time and deletes the cookie from redis.

The second time, the client directly requests the server to obtain the cookie. If the cookie is valid, it will directly jump to the system to be logged in. If the cookie is invalid, it will continue to repeat the first login process.

As shown in FIG. 5 , this embodiment also illustrates a login process for maintaining the login status through a driver, including:

The first time a client logs in through RPA, after successful login, it sends a request to the server with the cookie and specifies the refresh mode as driver. After receiving the cookie, the server saves the cookie to redis and inserts a cookie task into the MQ message queue.

The MQ message queue distributes tasks to the refresh robot. The robot executes the RPA tool and refreshes the cookie regularly until the cookie expires or reaches the maximum retention time and deletes the cookie from redis.

The second time, the client directly requests the server to obtain the cookie. If the cookie is valid, it will directly jump to the system to be logged in. If the cookie is invalid, it will continue to repeat the first login process.

As shown in FIG. 6 , this embodiment also illustrates a login process for maintaining the login status through QR code login, including:

The customer opens the RPA tool on the client and passes the QR code information to the middle platform. The middle platform saves the QR code and waits for the customer to scan it.

The client periodically checks its own login status. When it detects that the status has changed to successful login, it sends a request with cookies to the server and specifies the refresh mode as api.

The server receives the cookie, saves it to redis, and inserts a cookie task into the MQ message queue.

The MQ queue distributes tasks to the refresh robot, and the robot executes API requests to refresh the cookie regularly until the cookie expires or reaches the maximum retention time and deletes the cookie from redis.

FIG7 illustrates a schematic diagram of the physical structure of an electronic device. As shown in FIG7 , the electronic device may include: a processor 710, a communications interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communications interface 720, and the memory 730 communicate with each other through the communication bus 740. The processor 710 may call the logic instructions in the memory 730 to execute the login status maintenance method, which includes:

Interact with the login terminal and generate a cookie that matches the login terminal;

Receive the cookie saving request from the login terminal and put the cookie saving request into the asynchronous queue;

The login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

In addition, the logic instructions in the above-mentioned memory 730 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

On the other hand, the present invention further provides a computer program product, the computer program product includes a computer program, the computer program can be stored in a non-transitory computer-readable storage medium, when the computer program is executed by a processor, the computer can execute the login status maintenance method provided by the above methods, the method includes:

Interact with the login terminal and generate a cookie that matches the login terminal;

Receive the cookie saving request from the login terminal and put the cookie saving request into the asynchronous queue;

The login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to perform the login status maintaining method provided by the above methods, the method comprising:

Interact with the login terminal and generate a cookie that matches the login terminal;

Receive the cookie saving request from the login terminal and put the cookie saving request into the asynchronous queue;

The login terminal saves the cookie, and the login terminal maintains the login status of the login terminal based on the cookie.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.

Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiment.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (4)

1. A method for maintaining a logged-in status, characterized in that it comprises: Obtain cookie task. When the login terminal is an ordinary mobile terminal, after the first login is successful, the mobile terminal interacts with the server and saves cookies, and maintains a heartbeat connection with the server to maintain the session state. When the login terminal is a fixed device, a driver pool is managed by a group of machines. When logging in, each driver can open the login interface and send the QR code to the middle station for scanning and verification. Once the QR code is scanned by the user and the login is successful, it will interact with the server to obtain and save cookies, and maintain a heartbeat connection with the server. Receive the cookie saving request from the login terminal and verify some fields of the cookie. When applied to tax declaration services, verify whether the tax number length is 18 digits; After the verification is passed, the cookie is stored in redis, and the task of keeping the cookie is put into the asynchronous queue. The asynchronous queue will distribute the task to the machine group used to keep the cookie heartbeat; After receiving a cookie save request, the machines in the machine group that keeps the cookie heartbeat are divided into two modes: API request preservation and driver preservation according to the different cookie types in the cookie save request. For API request preservation, aiohttp is used to send non-blocking requests to keep the heartbeat on the server side; for driver preservation, a driver object is randomly obtained from the pre-established asynchronous driver pool, and the driver object will be continuously refreshed to keep the heartbeat; The heartbeat connection is maintained at random intervals of N minutes until the heartbeat connection reaches the maximum duration or the heartbeat fails, in which case you need to log in again. Once it is determined that the heartbeat connection has reached the maximum duration or the heartbeat fails, resources will be released, and the API request will be closed or the driver will be released. After the resources are released, delete the invalid cookies in redis; Record the process through asynchronous logging; The login process of maintaining the login status through API includes: The first time a client logs in through RPA, after successful login, it sends a request to the server with the cookie and specifies the refresh mode as API. After receiving the cookie, the server saves the cookie to redis and inserts a cookie task into the MQ message queue. The MQ message queue distributes tasks to the refresh robot, which executes API requests to refresh the cookie regularly until the cookie expires or reaches the maximum retention time, and then deletes the cookie from redis. The second time, the client directly requests the server to obtain the cookie. If the cookie is valid, it will directly jump to the system to be logged in. If the cookie is invalid, it will continue to repeat the first login process. 2. A login status maintaining system, applied to the login status maintaining method according to claim 1, characterized in that it comprises: A generation module, used to interact with the login terminal and generate a cookie matching the login terminal; A receiving module, used for receiving a cookie saving request from the login terminal, and placing the cookie saving request into an asynchronous queue; The maintaining module is used for the login terminal to save the cookie, and the login terminal maintains the login status of the login terminal based on the cookie. 3. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the login status maintaining method as claimed in claim 1 when executing the program. 4. A computer program product, comprising a computer program, which implements the login status maintaining method as claimed in claim 1 when the computer program is executed by a processor.