A multi-application real-time to-do reminder system and method

Abstract

The application discloses a kind of multi-application real-time to-be-done reminding system and method, the system includes: terminal to-be-done reminding client, server to-be-done reminding system;The terminal to-be-done reminding client includes configuration management component, to-be-done reminding component and identity authentication component;The server to-be-done reminding system includes terminal management service, message push service, identity authentication service and single sign-on service.The application realizes that user login-free operation accesses different application systems, realizes real-time reminding through long connection and server push, improves reminding efficiency, realizes to-be-done reminding real-time closed loop processing through new to-be-done and handling completion, supports the security control of application system login user and terminal to-be-done reminding client login user.

Description

Technical Field

[0001] This invention belongs to the field of information technology, specifically relating to a multi-application real-time to-do reminder system and method. Background Technology

[0002] Currently, the traditional method of to-do reminders in application systems involves displaying reminders on the homepage after the user logs in. Users cannot receive reminders when not logged in, and even after logging in, reminders are not available in real-time unless the page is refreshed. This prevents users from promptly handling tasks with high real-time requirements. With the development of the information technology industry, various application systems are proliferating, and users need to handle more and more business online. Frequent switching between application systems and refreshing pages to obtain to-do information in real time places a heavy workload on users.

[0003] Existing technology CN115412525A discloses a method for centralized reminders of messages from multiple application systems. This method involves centralizing messages from multiple application systems into a single client tool. The client tool uses a timer to send requests to a server at a certain frequency to retrieve to-do reminders for the current user account. A message prompt box pops up in the lower right corner of the Windows operating system desktop. Hovering over the lower right corner and clicking the prompt box invokes the Chrome browser and performs single sign-on to open the system, accessing the current user account's to-do task interface or homepage announcement interface. This achieves centralized reminders for to-do items from application systems under the same user account, enabling access to to-do items without logging in. However, this existing technology refreshes the application system's to-do list through a scheduled task in the client tool, failing to provide real-time reminders. Furthermore, the client tool only allows all application systems to use the same user account, making it unsuitable for scenarios where the same user uses different user accounts in different application systems. Additionally, this technology lacks security controls for switching users directly to log in to application systems.

[0004] Existing technology CN111200554A discloses a method and system for desktop to-do reminders based on MAC addresses. The method includes automatically obtaining the MAC address information of the current network device; retrieving an authorization verification file and verifying whether the file includes the MAC address information of the current network device; the authorization verification file includes the correspondence between the MAC address of the user's network device and the user's account; periodically obtaining to-do information corresponding to the user's account through a to-do query interface, and displaying the to-do information via a desktop floating icon, thus enabling different accounts on the same terminal to query to-do items without logging in. However, this existing technology requires a scheduled task to refresh the application system's to-do list, failing to provide real-time reminders. Reminders cannot be canceled immediately after completion of the to-do item. Furthermore, after receiving a to-do reminder, the user needs to log in to the application system to complete the to-do item.

[0005] Therefore, overcoming the shortcomings of existing technologies has become an urgent issue to be addressed in this field. Summary of the Invention

[0006] This invention provides a multi-application real-time to-do reminder system and method, specifically adopting the following technical solution: A multi-application real-time to-do reminder system, the system comprising: a terminal to-do reminder client and a server-side to-do reminder system; The terminal task reminder client includes a configuration management component, a task reminder component, and an identity authentication component; The server-side task reminder system includes terminal management service, message push service, identity authentication service, and single sign-on service.

[0007] This invention also relates to a multi-application real-time to-do reminder method, the method being used in the multi-application real-time to-do reminder system described above, the method comprising the following steps: S1. The server-side to-do reminder system collects user accounts from various application systems and binds user identifiers to the user accounts; S2. The terminal starts the to-do reminder client, establishes a long connection with the to-do reminder system, and displays the user's to-do information; S3. The to-do reminder system receives new to-do information and sends it to the to-do reminder client for real-time reminder; S4. Click on the to-do item in the to-do reminder client to open the to-do processing page and start processing; S5. Once the task to be completed is finished, the task reminder client cancels the task message. S6. Switch users to directly log in to the application system, and the to-do reminder client is subject to security management.

[0008] The present invention also relates to a computer-readable storage medium for storing a computer program, which is executed by a processor to perform the above-described multi-application real-time to-do reminder method.

[0009] This invention provides a multi-application real-time to-do reminder system and method, enabling the same user to access different application systems using different accounts, thereby solving the problem of centralized reminders for to-do items in application systems that have not undergone single sign-on (SSO) modifications. Real-time reminders allow for cancellation of reminders immediately after completion, addressing the issue of untimely reminders in existing technologies. Furthermore, the technology supports security management for users whose terminals are not currently displaying to-do reminders to directly log in to application systems, ensuring consistency between to-do reminders and actual user tasks, thus resolving the problem of inaccurate to-do reminders caused by inconsistencies between the user logging into the application system and the user logging into the to-do system service. Attached Figure Description

[0010] Figure 1 This is a schematic diagram of the structure of a multi-application real-time to-do reminder system according to the present invention.

[0011] Figure 2 This is a flowchart of a multi-application real-time to-do reminder method according to the present invention.

[0012] Figure 3 This is a flowchart of step 2 in a multi-application real-time to-do reminder method of the present invention.

[0013] Figure 4 This is a flowchart of step 3 in a multi-application real-time to-do reminder method of the present invention.

[0014] Figure 5 This is a flowchart of step 4 in a multi-application real-time to-do reminder method of the present invention. Detailed Implementation

[0015] The present invention will now be further described with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solutions of the present invention and should not be construed as limiting the scope of protection of the present invention. It should be noted that the following detailed descriptions are exemplary and intended to provide further explanation of the present invention.

[0016] Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular forms are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms “comprising” and / or “including” are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0017] As attached Figure 1 As shown, Embodiment 1 of the present invention relates to a multi-application real-time to-do reminder system, including: a terminal to-do reminder client and a server-side to-do reminder system. The terminal to-do reminder client includes a configuration management component, a to-do reminder component, and an identity authentication component. The server-side to-do reminder system includes a terminal management service, a message push service, an identity authentication service, and a single sign-on service.

[0018] The configuration management component is used to configure prompt sounds and configure tray pop-up styles.

[0019] The to-do reminder component is used to connect to the server-side to-do reminder system, receive information from the server-side to-do reminder system, assemble the received information into to-do information or completed to-do information, display the to-do information in the tray pop-up box, and delete the completed to-do information.

[0020] The identity authentication component is used to receive the user identifier, verify the user identifier, and send the user identifier to the to-do reminder component after successful verification.

[0021] The terminal management service is used to manage the accessed terminals, receive the connection established by the terminal to-do reminder component, and verify the user's identity in conjunction with the identity authentication service to confirm the real identity of the terminal user; it is used to collect information on the various application systems that the user can access, and supports the user to quickly access multiple application systems without logging in through the single sign-on service; it is used to manage the long connection established between the terminal and the server.

[0022] The message push service is used to receive user to-do information and to-do completion information from the application system, and push the information to the terminal to-do reminder client through the long connection.

[0023] The identity authentication service is used by the terminal identity authentication component to verify user identity. The identity authentication service supports multiple authentication methods, including but not limited to: username / password, user digital certificate, and user fingerprint.

[0024] The single sign-on service provides authenticated users with quick access across multiple application systems without requiring login. Preferably, the single sign-on service is based on user identity tickets, generating identity tickets for authenticated users and managing the entire lifecycle of these tickets, including verification, updates, and expiration / destruction; based on these user identity tickets, it enables users to access multiple application systems without logging in.

[0025] As attached Figure 2 As shown, Embodiment 2 of the present invention relates to a multi-application real-time to-do reminder method, which specifically includes the following steps: S1. The server-side to-do reminder system collects user accounts from various application systems and binds user identifiers to the user accounts; S2. The terminal starts the to-do reminder client, establishes a long connection with the to-do reminder system, and displays the user's to-do information; S3. The to-do reminder system receives new to-do information and sends it to the to-do reminder client for real-time reminder; S4. Click on the to-do item in the to-do reminder client to open the to-do processing page and start processing; S5. Once the task to be completed is finished, the task reminder client cancels the task message. S6. Switch users to directly log in to the application system, and the to-do reminder client is subject to security management.

[0026] Step S1 specifically includes the following sub-steps: S11. The server-side task reminder system provides an interface, and each application system pushes its own user account information to the task reminder system. S12. The to-do reminder system binds the user identifier and the user account information to generate binding information. One user identifier can be bound to multiple user accounts. The binding information includes the user identifier, the user account, and the application system identifier.

[0027] As attached Figure 3 As shown, step S2 specifically includes the following sub-steps: S21. The terminal launches the to-do reminder client; S22. The user logs into the to-do reminder client, which includes multiple login methods such as fingerprint login, UKey login, username / password login, and user card login. Furthermore, UKey login and user card login require no user interaction; the authentication component of the to-do reminder client can directly read the user's identifier. For fingerprint login, the authentication component obtains the user's identifier based on the user's fingerprint. For username / password login, the authentication component obtains the user's identifier using the username and password. S23. The to-do reminder client obtains the user identifier obtained in step S22 and initiates a request to the to-do reminder system for identity verification through the identity authentication component. If the verification fails, the to-do reminder client displays a failure message; if the verification succeeds, the to-do reminder system returns a user identity ticket and continues to step S24. S24. The to-do reminder client uses the user identity ticket mentioned in step S23 as the connection identifier to establish a long connection with the server-side to-do reminder system and generate a connection identifier. The to-do reminder system caches the long connection using the connection identifier. S25. The to-do reminder system obtains the user accounts of each application system through the binding information described in step S12, and then queries the user's to-do list through the user account. S26. The to-do reminder system assembles the user's to-do items, encapsulates them into to-do information, and combines the to-do information into a to-do information list for return. The to-do information includes the to-do title, the user, the page address for handling the to-do, a unique identifier for the task, the to-do generation time, and the application system identifier. Furthermore, if the to-do title contains sensitive data, this sensitive data is replaced with ****. S27. After receiving the list of to-do information, the client of the to-do reminder calls up the tray pop-up box, which is displayed in the lower right corner of the terminal desktop. The tray pop-up box contains the application system name, the number of to-dos, the title and sending time of the first to-do information in the to-do information list, and pagination information.

[0028] As attached Figure 4 As shown, step S3 specifically includes the following sub-steps: S31. The application system generates a new to-do item and sends it to the to-do reminder system. S32. After receiving the new task, the task reminder system assembles it into task information, and then finds the user identifier in the binding information in step S12 based on the user account in the new task and the user identity ticket in step S23. Then, it finds the long connection in step S24 and sends the task information to the task reminder client. S33. After receiving the message, the to-do reminder client determines that it is the to-do information and adds it to the last item of the to-do information list in step S26. The to-do reminder client calls the tray pop-up box and displays it in the lower left corner of the terminal desktop to provide a voice reminder.

[0029] As attached Figure 5 As shown, step S4 specifically includes the following sub-steps: S41. Click the title of the task in step S26. The task reminder client obtains the user account of the corresponding system from the task reminder system according to the user identity ticket in step S23. Then, the user account and the task processing page address in step S26 are sent to the corresponding application system. S42. The application system determines whether the user account corresponding to the user identity ticket in step S23 is logged in. If not logged in, the system performs internal login based on the user identity ticket and then enters the pending task page. If logged in, the system directly enters the pending task page. The pending task page can be a client-side processing page of a C / S architecture system or a browser-side processing page of a B / S architecture system. S43. Users can complete pending tasks on the pending task page.

[0030] Preferably, step S5 specifically includes the following sub-steps: S51. The task is completed. The application in step S41 sends the task completion information to the task reminder system. The task completion information includes the unique identifier of the task, the user identifier, the user identity ticket and the task completion information in step S26. S52. The to-do reminder system finds the long connection based on the user identity ticket in step S51 and sends the completion information to the to-do reminder client. S53. After receiving the completion information, the client deletes the pending information from the pending information list in step S26 according to the unique identifier of the matter to be handled.

[0031] Preferably, step S6 specifically includes the following sub-steps: S61. After switching user accounts on the terminal, use the user account to log in to the application system directly; S62. The application system sends the user account information described in step S61 to the to-do reminder client; S63. The to-do reminder client requests the to-do reminder system to obtain the user identifier based on the user account information described in step S61, and determines whether the user identifier is consistent with the user identifier described in step S22, and then returns the determination result. S64. After receiving the judgment result in step S61, if the result is inconsistent, the application system will prevent the user from logging in as described in step S61; if the result is consistent, the user will be allowed to log in as described in step S61.

[0032] Compared with existing technologies, this invention has the following advantages and positive effects: First, it enables users to access different application systems without logging in. Since application systems do not use single sign-on and user accounts are not unified, the server-side to-do reminder system can collect user accounts from various application systems, associate them with user identifiers, centrally remind users, and allow access to application systems without logging in. Second, it achieves real-time reminders and improves reminder efficiency through long connections and server-side push notifications. The client-side to-do reminder client establishes a long connection with the server-side to-do reminder system, and reminder messages are sent directly by the application system through the server-side to-do reminder system, corresponding to the polling mechanism of existing technologies, resulting in high real-time performance. Third, it achieves real-time closed-loop processing of to-do reminders through new to-dos and completed tasks. After the application system completes a task, it directly sends the task completion information to the server-side to-do reminder system. The to-do reminder system then sends the task completion information to the client-side to-do reminder client through the long connection established with the client-side to-do reminder client, deleting expired tasks in real time, thus completing the closed-loop to-do reminder process. Fourth, it supports security management of application system login users and terminal to-do reminder client login users. When a user logs into the application system directly using another account, the terminal to-do reminder client will intercept the login. If the two accounts are different, the user will not be allowed to log in to the application system, thus avoiding the situation where the to-do information in the terminal to-do reminder client is inconsistent with the to-do information in the application system.

[0033] The above description is merely a preferred embodiment of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A multi-application real-time to-do reminder system, characterized in that, The system includes: a terminal-based to-do reminder client and a server-based to-do reminder system; The terminal task reminder client includes a configuration management component, a task reminder component, and an identity authentication component; The server-side task reminder system includes terminal management service, message push service, identity authentication service and single sign-on service; The configuration management component is used to configure prompt sounds and configure tray pop-up styles; The to-do reminder component is used to connect to the server-side to-do reminder system, receive information from the server-side to-do reminder system, assemble the received information into to-do information or completed to-do information, display the to-do information in the tray pop-up box, and delete the completed to-do information. The identity authentication component is used to receive the user identifier, verify the user identifier, and send the user identifier to the to-do reminder component after successful verification. The terminal management service is used to manage the accessed terminals, receive the connection established by the terminal to-do reminder component, and verify the user's identity in conjunction with the identity authentication service to confirm the real identity of the terminal user; it is used to collect information on the various application systems that the user can access, and supports the user to quickly access multiple application systems without logging in through the single sign-on service; it is used to manage the long connection established between the terminal and the server. The message push service is used to receive user to-do information and to-do completion information from the application system, and push the information to the terminal to-do reminder client through the long connection. The identity authentication service is used by the terminal identity authentication component to verify the user's identity; the identity authentication service supports multiple identity authentication methods, including: username / password, user digital certificate, and user fingerprint; The single sign-on service is used to provide authenticated users with quick access to multiple application systems without logging in.

2. The multi-application real-time to-do reminder system according to claim 1, characterized in that, The single sign-on service is a single sign-on service based on user identity tickets. It generates identity tickets for users who have passed identity authentication and manages the entire lifecycle of identity ticket verification, updating, and expiration destruction. Based on user identity tickets, it enables users to access multiple application systems without logging in.

3. A method for real-time to-do reminders across multiple applications, the method being used in the real-time to-do reminder system for multiple applications as described in claim 1 or 2, characterized in that, The method includes the following steps: S1. The server-side to-do reminder system collects user accounts from various application systems and binds user identifiers to the user accounts; S2. The terminal starts the to-do reminder client, establishes a long connection with the to-do reminder system, and displays the user's to-do information; S3. The to-do reminder system receives new to-do information and sends it to the to-do reminder client for real-time reminder; S4. Click on the to-do item in the to-do reminder client to open the to-do processing page and start processing; S5. Once the task to be completed is finished, the task reminder client cancels the task information. S6. Switch users to directly log in to the application system, and the to-do reminder client is subject to security management.

4. The multi-application real-time to-do reminder method according to claim 3, characterized in that, Step S2 specifically includes: S21. The terminal launches the to-do reminder client; S22. The user logs into the to-do reminder client, where the login methods include fingerprint login, UKey login, username / password login, and user card login; furthermore, UKey login and user card login do not require user operation, and the identity authentication component of the to-do reminder client can directly read the user identifier; when using fingerprint login, the identity authentication component can obtain the user identifier based on the user's fingerprint; when using username / password login, the identity authentication component can obtain the user identifier through the username and password; S23. The to-do reminder client obtains the user identifier obtained in step S22, and sends a request to the to-do reminder system for identity verification through the identity authentication component; if the verification fails, the to-do reminder client displays a failure message; if the verification succeeds, the to-do reminder system returns a user identity ticket, and continues to step S24; S24. The to-do reminder client uses the user identity ticket mentioned in step S23 as the connection identifier to establish a long connection with the server-side to-do reminder system and generate a connection identifier. The to-do reminder system caches the long connection using the connection identifier. S25. The to-do reminder system obtains the user accounts of each application system through the information generated by binding the user identifier and the user account in step S1, and then queries the user's to-do list through the user account. S26. The to-do reminder system assembles the user's to-do items, encapsulates them into to-do information, and combines the to-do information into a to-do information list and returns it. The to-do information includes the to-do title, the user, the page address for handling the to-do, the unique identifier of the item to be handled, the to-do generation time, and the application system identifier. Furthermore, if the to-do title contains sensitive data, the sensitive data is replaced with ****. S27. After receiving the list of to-do information, the client of the to-do reminder calls up the tray pop-up box, which is displayed in the lower right corner of the terminal desktop. The tray pop-up box contains the application system name, the number of to-dos, the title and sending time of the first to-do information in the to-do information list, and pagination information.

5. The multi-application real-time to-do reminder method according to claim 4, characterized in that, Step S3 specifically includes: S31. The application system generates a new to-do item and sends it to the to-do reminder system. S32. After receiving the new task, the task reminder system assembles it into task information. Then, based on the user account in the new task and the user identity ticket in step S23, it finds the user identifier in the information generated by binding the user identifier and the user account in step S1, and then finds the long connection in step S24, and sends the task information to the task reminder client. S33. After receiving the message, the to-do reminder client determines that it is the to-do information and adds it to the last item of the to-do information list in step S26. The to-do reminder client calls the tray pop-up box and displays it in the lower left corner of the terminal desktop to provide a voice reminder.

6. The multi-application real-time to-do reminder method according to claim 5, characterized in that, Step S4 specifically includes: S41. Click the title of the task in step S26. The task reminder client obtains the user account of the corresponding system from the task reminder system according to the user identity ticket in step S23. Then, the user account and the task processing page address in step S26 are sent to the corresponding application system. S42. The application system determines whether the user account corresponding to the user identity ticket in step S23 is logged in. If not logged in, the system performs internal login based on the user identity ticket and then enters the pending processing page. If logged in, the system directly enters the pending processing page. The pending processing page can be the client processing page of a C / S architecture system or the browser processing page of a B / S architecture system. S43. Users can complete pending tasks on the pending task page.

7. A multi-application real-time to-do reminder method according to claim 6, characterized in that, Step S5 specifically includes: S51. The task is completed. The application in step S41 sends the task completion information to the task reminder system. The task completion information includes the unique identifier of the task, the user identifier, the user identity ticket and the task completion information in step S26. S52. The to-do reminder system finds the long connection based on the user identity ticket in step S51 and sends the completion information to the to-do reminder client. S53. After receiving the completion information, the client deletes the pending information from the pending information list in step S26 according to the unique identifier of the matter to be handled.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which is executed by a processor to perform a multi-application real-time to-do reminder method according to any one of claims 3-7.

Images