Document updating reminding method and device, electronic equipment and storage medium

Abstract

The invention relates to a document updating reminding method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a document updating subscription request from a client, determining a target document subscribed by the client, and determining a subscription rule of the client for the target document; and sending an update reminding message of a document update event to the client in response to the occurrence of the document update event matched with the subscription rule in the target document. Therefore, the user can customize the subscription rule for document updating while the document updating reminding is realized, so that the diversified requirements of the user on the document updating reminding are met, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of computers, and in particular, to a method, device, electronic device, and storage medium for document update reminder. Background Art

[0002] Currently, when a user pays attention to a certain document, they expect to master the update dynamics of the document.

[0003] In this regard, although there are some ways in the prior art for users to master the update dynamics of documents, the document update reminder method is very simple and cannot meet the diverse needs of users. Summary of the Invention

[0004] This application provides a method, device, electronic device, and storage medium for document update reminder to solve the technical problem that the document update reminder method in the prior art is very simple and cannot meet the diverse needs of users.

[0005] In a first aspect, this application provides a method for document update reminder, and the method includes:

[0006] Receiving a document update subscription request from a client, determining the target document subscribed by the client, and determining the subscription rule of the client for the target document;

[0007] In response to a document update event that matches the subscription rule occurring for the target document, sending an update reminder message of the document update event to the client.

[0008] In a possible implementation manner, the determining the target document subscribed by the client includes:

[0009] Parsing a target keyword from the document update subscription request;

[0010] Determining the target document subscribed by the client according to the target keyword.

[0011] In a possible implementation manner, the determining the subscription rule of the client for the target document includes:

[0012] Parsing the subscription rule of the client for the target document from the document update subscription request.

[0013] In a possible implementation manner, the subscription rule for the target document includes:

[0014] When the client sets a collaborator as the reminder party, after a document update event that matches the subscription rule occurs for the target document, sending an update reminder message of the document update event to the collaborator.

[0015] In a possible implementation, the method further includes:

[0016] Receiving an unsubscribe request from the client, and unsetting the collaborator indicated by the unsubscribe request as the reminder party.

[0017] In a possible implementation, the subscription rule is used to indicate attention to document updates; the sending of an update reminder message of the document update event to the client in response to a document update event matching the subscription rule for the target document includes:

[0018] In response to any collaborator of the target document performing a document update event on the target document, sending an update reminder message of the document update event to the client.

[0019] In a possible implementation, the subscription rule is used to indicate attention to updates of a target collaborator to a document; the sending of an update reminder message of the document update event to the client in response to a document update event matching the subscription rule for the target document includes:

[0020] In response to the target collaborator performing a document update event on the target document, sending an update reminder message of the document update event to the client.

[0021] In a possible implementation, the subscription rule is used to indicate attention to document updates within a target time period; the sending of an update reminder message of the document update event to the client in response to a document update event matching the subscription rule for the target document includes:

[0022] In response to at least one collaborator of the target document performing a document update event on the target document within the target time period, sending an update reminder message of the document update event to the client.

[0023] In a possible implementation, the subscription rule is used to indicate attention to updates of a target area in a document; the sending of an update reminder message of the document update event to the client in response to a document update event matching the subscription rule for the target document includes:

[0024] In response to at least one collaborator of the target document performing a document update event on the target area in the target document, sending an update reminder message of the document update event to the client.

[0025] In a possible implementation, the method further includes:

[0026] In response to the triggering of a set event, cancel the client's subscription to the target document; wherein, the set event includes at least one of the following: the client's access permission to the target document is cancelled, and collaboration on the target document is cancelled.

[0027] In a possible implementation manner, sending the update reminder message of the document update event to the client includes:

[0028] Sending the update reminder message of the document update event to the message subscription queue of the client in the message center, so that the message center obtains the update reminder message from the message subscription queue and pushes it to the client.

[0029] In a second aspect, the present application provides a document update reminder device, and the device includes:

[0030] A subscription module, configured to receive a document update subscription request from a client, determine the target document subscribed by the client, and determine the subscription rule of the client for the target document;

[0031] A reminder module, configured to send an update reminder message of the document update event to the client in response to a document update event that matches the subscription rule for the target document.

[0032] In a possible implementation manner, the subscription module includes:

[0033] An analysis unit, configured to analyze a target keyword from the document update subscription request;

[0034] A determination unit, configured to determine the target document subscribed by the client according to the target keyword.

[0035] In a possible implementation manner, the subscription module is specifically configured to:

[0036] Analyze the subscription rule of the client for the target document from the document update subscription request.

[0037] In a possible implementation manner, the subscription rule for the target document includes:

[0038] In the case where the client sets a collaborator as the reminded party, after a document update event that matches the subscription rule occurs for the target document, send an update reminder message of the document update event to the collaborator.

[0039] In a possible implementation manner, the device further includes:

[0040] The first unsubscribe module is used to receive an unsubscribe request from the client and un-set the collaborator indicated by the unsubscribe request as the reminder recipient.

[0041] In a possible implementation, the subscription rule is used to indicate attention to document updates; specifically, the reminder module is configured to:

[0042] In response to any collaborator of the target document performing a document update event on the target document, send an update reminder message of the document update event to the client.

[0043] In a possible implementation, the subscription rule is used to indicate attention to the updates of a target collaborator to a document; specifically, the reminder module is configured to:

[0044] In response to the target collaborator performing a document update event on the target document, send an update reminder message of the document update event to the client.

[0045] In a possible implementation, the subscription rule is used to indicate attention to document updates within a target time period; specifically, the reminder module is configured to:

[0046] In response to at least one collaborator of the target document performing a document update event on the target document within the target time period, send an update reminder message of the document update event to the client.

[0047] In a possible implementation, the subscription rule is used to indicate attention to updates of a target area in a document; specifically, the reminder module is configured to:

[0048] In response to at least one collaborator of the target document performing a document update event on the target area in the target document, send an update reminder message of the document update event to the client.

[0049] In a possible implementation, the device further includes:

[0050] The second unsubscribe module is used to cancel the client's subscription to the target document in response to the triggering of a set event; wherein, the set event includes at least one of the following: the client is cancelled the access right to the target document, the target document is cancelled collaboration.

[0051] In a possible implementation, the reminder module is configured to:

[0052] Send the update reminder message of the document update event to the message subscription queue of the client in the message center, so that the message center obtains the update reminder message from the message subscription queue and pushes it to the client.

[0053] In a third aspect, the present application provides an electronic device, including: a processor and a memory, where the processor is configured to execute a document update reminder program stored in the memory to implement the document update reminder method according to any one of the first aspect.

[0054] In a fourth aspect, the present application provides a storage medium storing one or more programs, where the one or more programs can be executed by one or more processors to implement the document update reminder method according to any one of the first aspect.

[0055] The above technical solutions provided by the embodiments of the present application have the following advantages compared with the prior art: In the method provided by the embodiments of the present application, by receiving a document update subscription request from a client, determining the target document subscribed by the client and the subscription rule of the client for the target document, and in response to a document update event that matches the subscription rule occurring for the target document, sending an update reminder message of the document update event to the client, it is possible to implement document update reminder while enabling the user to customize the subscription rule for document update, thereby meeting the diverse needs of the user for document update reminder and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application and used together with the specification to explain the principles of the present application.

[0057] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0058] One or more embodiments are exemplarily illustrated by the pictures in the corresponding accompanying drawings. These exemplary illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements, unless otherwise stated, and the drawings in the figures do not constitute a proportional limitation.

[0059] Figure 1 It is a schematic diagram of a system architecture related to the embodiments of the present application;

[0060] Figure 2 It is a flowchart of an embodiment of a document update reminder method provided by the embodiments of the present application;

[0061] Figure 3 It is a flowchart of an embodiment of another document update reminder method provided by the embodiments of the present application;

[0062] Figure 4 This is a flowchart of an embodiment of another document update reminder method provided by an embodiment of the present application;

[0063] Figure 5 This is a schematic diagram of an interface operation for paying attention to the document update function;

[0064] Figure 6 This is a flowchart of an embodiment of yet another document update reminder method provided by an embodiment of the present application;

[0065] Figure 7 This is a flowchart of an embodiment of yet another document update reminder method provided by an embodiment of the present application;

[0066] Figure 8 This is an example of an update reminder message;

[0067] Figure 9 This is a block diagram of an embodiment of a document update reminder device provided by an embodiment of the present application;

[0068] Figure 10 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0069] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are some but not all of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0070] The following disclosure provides many different embodiments or examples for implementing different structures of the present application. To simplify the disclosure of the present application, components and settings of specific examples are described below. Of course, they are only examples and are not intended to limit the present application. In addition, the present application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplification and clarity and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0071] To solve the technical problem that the existing document update reminder method is very simple and cannot meet the diverse needs of users, the present application provides a document update reminder method, which can, while realizing the document update reminder, enable users to customize the subscription rules for document updates, thereby meeting the diverse needs of users for document update reminders and improving the user experience.

[0072] Figure 1Schematic diagram of a system architecture related to an embodiment of the present application.

[0073] As Figure 1 shown, the system architecture 100 may include devices 101 to 104, and a network 105. Among them, the network 105 is used to provide a communication link between devices 101 to 104, and may include a wireless link, a wired link, or an optical fiber cable, etc., which is not limited in the embodiments of the present application.

[0074] Devices 101 to 105 can be hardware devices or software that support network connections to provide various network services. When the device is hardware, it can be various electronic devices supporting a display screen, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, servers, etc. When the device is software, it can be installed in the above-listed electronic devices.

[0075] In practice, the device can provide corresponding network services by installing corresponding client applications or server applications. After the device installs the client application, it can be embodied as a user device in network communication. Correspondingly, after installing the server application, it can be embodied as a server in network communication. For example, in Figure 1 , device 101 can be referred to as a server (hereinafter referred to as server 101), and devices 102 to 104 can be referred to as user devices. In the embodiments of the present application, devices 101 to 104 can all install a document application so that users of devices 101 to 104 can enjoy document services.

[0076] In the embodiments of the present application, the above-mentioned document services include but are not limited to document editing services, document update reminder services, etc. Among them, the document update reminder service means that when one party updates the document content, the other party can receive a document update reminder message. Here, updating the document content includes but is not limited to deleting the document content, modifying the document content, adding new document content, saving the document content, etc. For example, when device 103 or device 104 updates a document that server 101 is concerned about, server 101 can send a document update reminder message to device 101. As for the specific implementation of the document update reminder service, it will be described in detail through the following embodiments and will not be elaborated here first.

[0077] It can be understood that Figure 1 the number of networks and devices in

[0078] Figure 2 Flowchart of an embodiment of a document update reminder method provided by an embodiment of the present application. In one embodiment, this method is applied to a cloud service, such as Figure 1on the server 101 shown in the example. As Figure 2 shown, the method includes the following steps:

[0079] Step 201, receive a document update subscription request from a client, determine the target document subscribed by the client, and determine the subscription rule of the client for the target document.

[0080] The above client can be a device installed with a corresponding client application (such as a document application), for example Figure 1 any one of the devices 102 to 104 shown in the example. The client application mentioned here refers to a program that provides services to users, which can be an application program running in an independent process, a sub-application program (mini-program) independent of the main page embedded in the client, a function running on a web browser (also known as a WebApp), a mini-program embedded in an email, etc. And the device here can be various electronic devices supporting a display screen, such as a smart phone, a desktop computer, a tablet computer, etc.

[0081] The above target document can be a collaborative document in formats such as.doc,.docx,.xlsx,.xls,.ppt,.txt, etc. Here, the collaborative document means that the document can be collaboratively edited by multiple users, and the collaborative document is stored on a cloud service.

[0082] In the embodiment of the present application, when the client needs to pay attention to the target document and expects to receive a document update reminder message when the content of the target document is updated, it can send a document update subscription request to the cloud service, and the document update subscription request carries at least the document identifier of the target document that the client needs to pay attention to and the subscription rule of the client for the target document. Based on this, the cloud service can receive the document update subscription request from the client, and then parse out the document identifier of the target document and the subscription rule of the client for the target document from the document update subscription request, so as to determine the target document subscribed by the client and the subscription rule of the client for the target document. As for how the client pays attention to the target document and sets the subscription rule for the target document, exemplary descriptions are made through different embodiments in the following, and will not be elaborated here first.

[0083] Among them, the above document identifier is, for example, data such as a document name, a document serial number, etc. that can uniquely identify a document.

[0084] The above-mentioned subscription rules of the client for the target document are used to indicate the attention rules set by the client for the target document, which can also be said to be the document update reminder rules set by the client for the target document. Generally speaking, it is used to indicate in what kind of document update event of the target document, a document update reminder message is sent to the client. Here, document update events include but are not limited to deleting document content events, modifying document content events, adding document content events, saving document content events, etc. As for the specific content of the subscription rules, exemplary explanations are given through different embodiments in the following text, and will not be elaborated here for the time being.

[0085] One more point to add here: The number of the above-mentioned clients can be one or more, that is, multiple clients can separately send document update subscription requests to the cloud service. After the cloud service receives the document update subscription request, determines the target document subscribed by the client, and determines the subscription rules of the client for the target document, it can associate and store the identifier of the client with the identifier of the target document it subscribes to and the subscription rules, and then implement document update reminders for different clients using their associated subscription rules. Here, the target documents subscribed by different clients can be the same or different, and the embodiments of this application do not limit this. Further, in the case where different clients subscribe to the same target document, the subscription rules of different clients for the same target document can be the same or different, and the embodiments of this application do not limit this either.

[0086] For example, in Figure 1 the system architecture shown in the example, Device 102 and Device 103 subscribe to Document 1, and Device 104 subscribes to Document 2. Then, in the case where Device 103 or Device 104 updates the document content of Document 1, Server 101 can send a document update reminder message to Device 102; in the case where Device 102 or Device 104 updates the document content of Document 1, Server 101 can send a document update reminder message to Device 103; in the case where Device 102 or Device 103 updates the document content of Document 2, Server 101 can send a document update reminder message to Device 104.

[0087] Step 202: In response to a document update event that matches the subscription rules occurring for the target document, send an update reminder message for the document update event to the client.

[0088] As can be seen from the description in step 101 above, the subscription rule is used to indicate in what case of what document update event occurs in the target document, a document update reminder message is sent to the client. Based on this, when the cloud service responds to a document update event that matches the subscription rule for the target document, it can send a document update reminder message to the client. Here, the document update reminder message is the update reminder message for the document update event, which can indicate what document update event has occurred in the target document, and / or indicate the trigger of the document update event.

[0089] The technical solution provided by the embodiments of the present application, by receiving a document update subscription request from the client, determining the target document subscribed by the client and the subscription rule of the client for the target document, and sending an update reminder message for the document update event to the client in response to a document update event that matches the subscription rule, can, while implementing the document update reminder, enable the user to customize the subscription rule for the document update, so as to meet the diverse needs of the user for the document update reminder and improve the user experience.

[0090] The following makes an exemplary description of the specific content of the above subscription rule through different embodiments, and these examples do not constitute a limitation to the present application.

[0091] Specifically, in one embodiment, the subscription rule is used to indicate attention to document updates. That is to say, the client can simply pay attention to the target document, and does not care about who, at what time, and what kind of document update event has been triggered for the target document.

[0092] Based on this, the specific implementation of the cloud service sending an update reminder message for the document update event to the client in response to a document update event that matches the subscription rule includes: sending an update reminder message for the document update event to the client in response to any collaborator of the target document executing a document update event on the target document.

[0093] It can be seen from this that by applying the above embodiments, it can be realized that when any collaborator triggers any document update event for the target document at any time, the client can timely receive the update reminder message for the document update event, so that the client can comprehensively master the update dynamics of the target document.

[0094] In one embodiment, after the user logs in to the account on any device and sets the document update reminder, the user can receive the update reminder information on this device, and the user can open the document associated with the update reminder information through the update reminder information and switch to the area where the update reminder information occurs in the document.

[0095] In another embodiment, the subscription rule is used to indicate to follow the updates of a target collaborator to a document. That is to say, the client can follow the updates of the target collaborator to the target document, rather than the updates of other collaborators to the target document.

[0096] Based on this, the specific implementation of the cloud service sending an update reminder message of a document update event to the client in response to a document update event matching the subscription rule for the target document includes: sending an update reminder message of the document update event to the client in response to the target collaborator performing a document update event on the target document. Here, the target collaborator can be set by the client according to actual needs, and there can be one or more target collaborators.

[0097] For example, in Figure 1 the illustrated system architecture, devices 102 to 104 all have the collaboration permission for the target document. When device 102 wants to follow the updates of device 103 to the target document, it can set device 103 as the target collaborator. Then, when device 103 triggers any document update event on the target document at any time, server 101 can send an update reminder message of this document update event to device 102, while when device 104 triggers any document update event on the target document, server 101 will no longer send an update reminder message of this document update event to device 102.

[0098] It can be seen that by applying the above embodiment, the client can independently set the target collaborator to be followed. Only when the target collaborator triggers a document update event on the target document will the client receive an update reminder message of the document update event, while when other collaborators trigger a document update event on the target document, the client will not receive an update reminder message of the document update time. On the one hand, this can meet the user's customized document update reminder requirements, and on the other hand, it can also avoid resource waste caused by the cloud service pushing unnecessary update reminder messages externally and causing unnecessary disturbances to users.

[0099] In yet another embodiment, the subscription rule is used to indicate to follow the document updates within a target time period. That is to say, the client can follow the updates to the target document that occur within the target time period, rather than the updates to the target document that occur in other time periods.

[0100] Based on this, the specific implementation of the cloud service sending an update reminder message of the document update event to the client in response to the document update event that matches the subscription rule for the target document includes: in response to at least one collaborator of the target document performing a document update event on the target document within the target time period, sending an update reminder message of the document update event to the client. Here, the target time period can be a continuous time period, such as within the next week, or can include multiple discrete time periods, such as every Monday, every Wednesday, and every Friday, or from 9 am to 11 am every day. In the application, the user can flexibly set the target time period according to actual needs, and the embodiments of the present application do not limit this.

[0101] For example, in Figure 1 the system architecture shown in the example, devices 102 to 104 all have the collaboration permission for the target document, and device 102 wants to pay attention to the updates of the target document that occur from 9 am to 11 am every day. Then, when device 103 triggers a document update event for the target document at 10 am, server 101 can send an update reminder message of this document update event to device 102, and when device 104 triggers a document update event for the target document at 2 pm, server 101 will no longer send an update reminder message of this document update event to device 102.

[0102] It can be seen that by applying the above embodiments, the client can independently set the document update time it pays attention to. Only when a document update event is triggered for the target document within the target time period that the user pays attention to, will the client receive an update reminder message of the document update event, while when a document update event is triggered for the target document in other time periods, the client will not receive an update reminder message of the document update event. On the one hand, this can meet the user's customized document update reminder requirements, and on the other hand, it can also avoid resource waste caused by the cloud service pushing unnecessary update reminder messages externally and causing unnecessary disturbances to users.

[0103] It can be seen that by applying the above embodiments, the client can independently set the target collaborator it pays attention to. Only when the target collaborator triggers a document update event for the target document, will the client receive an update reminder message of the document update event, while when other collaborators trigger a document update event for the target document, the client will not receive an update reminder message of the document update event. On the one hand, this can meet the user's customized document update reminder requirements, and on the other hand, it can also avoid resource waste caused by the cloud service pushing unnecessary update reminder messages externally and causing unnecessary disturbances to users.

[0104] In another embodiment, the subscription rule is used to indicate to pay attention to the updates of the target area in the document. That is to say, the client can pay attention to the updates that occur in the target area of the target document, rather than the updates that occur in other areas of the target document.

[0105] Based on this, the specific implementation of the cloud service sending an update reminder message of the document update event to the client in response to a document update event that matches the subscription rule in the target document includes: in response to at least one collaborator of the target document performing a document update event on the target area in the target document, sending an update reminder message of the document update event to the client. Here, the target area can be one or several paragraphs (which can be consecutive paragraphs or non-consecutive paragraphs) in the target document, or one or several chapters (which can be consecutive chapters or non-consecutive chapters) in the target document, or a document area composed of any document content in the target document. In applications, users can flexibly set the target area in the target document according to actual needs, and the embodiments of the present application do not limit this.

[0106] For example, in Figure 1 the illustrated system architecture, devices 102 to 104 all have the collaboration permission for the target document, and device 102 wants to pay attention to the updates in the target area of the target document. Then, when device 103 triggers a document update event for the target area, server 101 can send an update reminder message of this document update event to device 102, and when device 104 triggers a document update event for the document content outside the target area, server 101 will no longer send an update reminder message of this document update event to device 102.

[0107] It can be seen that by applying the above embodiments, the client can independently set the document area to be concerned. Only when a document update event is triggered in the document area concerned by the user, the client will receive an update reminder message of the document update event, and when a document update event is triggered in other areas of the target document, the client will not receive an update reminder message of the document update event. On the one hand, this can meet the user's customized document update reminder requirements, and on the other hand, it can also avoid resource waste caused by the cloud service pushing unnecessary update reminder messages externally and causing unnecessary disturbances to users.

[0108] In another embodiment, the subscription rule is used to indicate to pay attention to the updates of any number of documents, and any number of documents can also be set as documents to be particularly concerned about. For the documents to be particularly concerned about, the information of their update reminders can be set as the update reminder message ranked first, or the update reminder message with a special flag.

[0109] In another embodiment, the subscription rule is used to indicate to pay attention to a specified type of document update event occurring in the concerned document. That is to say, the client can pay attention to the specified type of document update event occurring in the target document, rather than other types of document update events occurring in the target document.

[0110] Based on this, the specific implementation of the cloud service sending an update reminder message of the document update event to the client in response to a document update event matching the subscription rule in the target document includes: in response to at least one collaborator of the target document performing a specified type of document update event on the target document, sending an update reminder message of the document update event to the client. Here, the specified type of document update event may be one or several of the events of modifying the document content, deleting the document content, and adding the document content.

[0111] For example, in Figure 1 the illustrated system architecture, devices 102 to 104 all have the collaboration permission for the target document, and device 102 wants to pay attention to the deletion operation in the target document. Then, when device 103 triggers a document content deletion event on the target document, server 101 can send an update reminder message of this document update event to device 102, and when device 104 triggers a document content addition event on the target document, server 101 no longer sends an update reminder message of this document update event to device 102.

[0112] It can be seen that by applying the above embodiments, the client can independently set the type of document update event to be concerned. Only when a specified type of document update event is triggered, the client will receive an update reminder message of the document update event, and when other types of document update events are triggered, the client will not receive an update reminder message of the document update event. On the one hand, this can meet the user's customized document update reminder requirements, and on the other hand, it can also avoid the waste of resources caused by the cloud service pushing unnecessary update reminder messages externally and the unnecessary disturbance to the user.

[0113] In another embodiment, the subscription rule may include a combination of two or more of the above subscription rules. For example, the subscription rule is used to indicate to pay attention to the update of the target document by the target collaborator within the target time period, and for another example, the subscription rule is used to indicate to pay attention to the update of the target area in the target document within the target time period, and for another example, the subscription rule is used to indicate to pay attention to the update of the target area in the target document by the target collaborator, and so on. The embodiments of the present application do not limit the specific subscription rules.

[0114] As can be seen from the above several embodiments, in the technical solution provided by the embodiments of the present application, the client is supported to customize the subscription rules for the target document from multiple dimensions such as the trigger time of the document update event, the collaborator who triggers the document update event, and the document area, so as to meet the document update reminder requirements in various scenarios, enabling the user to customize and master the update dynamics of the target document from multiple dimensions and improving the user experience.

[0115] Figure 3 This is a flowchart of an embodiment of another document update reminder method provided by the embodiments of the present application. Figure 3 The process shown is Figure 2 Based on the process shown, it includes the following steps:

[0116] Step 301, receive a document update subscription request from the client, and parse out the target document subscribed by the client and the subscription rules for the target document from the document update subscription request.

[0117] As can be seen from the description of step 301, the client can determine a local document as the target document it subscribes to. Here, it should be noted that when the client determines a local document as the target document it subscribes to, it also means that the client sets the local document as an online collaborative document and grants collaboration permissions for the local document to one or several other clients. The collaboration permissions here include at least the viewing permission and may also include the editing permission.

[0118] Among them, as an optional implementation method, when the user wants to enable the update reminder for the client's local document, the user can trigger the corresponding icon in the client toolbar to trigger the document update subscription operation. At this time, the client responds to the document update subscription operation and calls the document selector, enabling the user to select the target document to be subscribed from the local documents of the client through the document selector. After the user completes the selection of the target document, the client sends the target document in the document update subscription request to the cloud service, thus realizing the cloud processing of the target document on the client side.

[0119] Further, when the user has completed the selection of the target document, the client can also present a human-computer interaction interface, enabling the user to select the collaborators of the target document and the collaboration permissions of each collaborator through this interface, and set the subscription rules for the target document on the client. Then, when the client sends the above-mentioned document update subscription request to the cloud service, it can carry the collaborators, collaboration permissions, and subscription rules set by the user for the target document in the document update subscription request. This enables the cloud service to, in response to the document update subscription request, set the target document on the client side as a collaborative document, set the corresponding collaborators and collaboration permissions, and parse the subscription rules for the target document by the client from the document update subscription request.

[0120] As another alternative implementation, when the user wants to enable the update reminder for the local document on the client, the user can trigger the client to open the local folder. Then, the user can select the target document to be subscribed from this local folder. At this time, in response to the selection operation of the target document, the client presents a menu list, and this menu list includes an icon for indicating triggering the document update subscription operation. Based on this, the user can trigger this icon to trigger the document update subscription operation. At this time, in response to this document update subscription operation, the client sends the target document carried in the document update subscription request to the cloud service, thus achieving the cloud processing of the target document on the client side.

[0121] Further, the client can also present a human-computer interaction interface, enabling the user to select the collaborators of the target document and the collaboration permissions of each collaborator through this interface, and set the subscription rules for the target document on the client. Then, when the client sends the above-mentioned document update subscription request to the cloud service, it can carry the collaborators, collaboration permissions, and subscription rules set by the user for the target document in the document update subscription request. This enables the cloud service to, in response to the document update subscription request, set the target document on the client side as a collaborative document, set the corresponding collaborators and collaboration permissions, and parse the subscription rules for the target document by the client from the document update subscription request.

[0122] Step 302: In response to the occurrence of a document update event that matches the subscription rules for the target document, send an update reminder message for the document update event to the client.

[0123] For the detailed description of this step, reference can be made to the relevant description in the above Figure 2 illustrated embodiment, which will not be elaborated here.

[0124] Figure 3The process shown can set the local document of the client as an online collaborative document and enable the document update reminder function for the local document to meet the user's needs by receiving a document update subscription request from the client, parsing the target document subscribed by the client and the subscription rules for the target document from the document update subscription request, and sending an update reminder message of the document update event to the client in response to a document update event that matches the subscription rules for the target document.

[0125] Figure 4 This is a flowchart of an embodiment of another document update reminder method provided by an embodiment of the present application. Figure 4 The process shown in Figure 2 On the basis of the process shown, includes the following steps:

[0126] Step 401, receive a document update subscription request from the client, parse the cloud document identifier and the client's subscription rules from the document update subscription request, and determine the cloud document corresponding to the cloud document identifier as the target document subscribed by the client.

[0127] As can be seen from the description of step 401, the client can determine the cloud document as the target document it subscribes to. In addition, it should be noted here that when the client sets the cloud document as the target document it subscribes to, the client should have the collaboration permission for the target document. Based on this, after the cloud service parses the cloud document identifier from the document update subscription request, when it determines that the client has the access permission to the cloud document corresponding to the cloud document identifier, it determines the cloud document corresponding to the cloud document identifier as the target document subscribed by the client.

[0128] Among them, as an optional implementation method, as Figure 5 shown, when the user wants to enable the update reminder for the cloud document, the user can trigger the client to present a document list, such as Figure 5 the document list presented in shows the documents that have been recently opened on the client, and the document list can include cloud documents or local documents. Then, the user can select the cloud document identifier of the target document to be subscribed from the document list (such as Figure 5 the document name in). At this time, in response to the selection operation of the cloud document identifier, the client presents a menu list, and the menu list includes an icon for indicating triggering the document update subscription operation, such as Figure 5In the middle is the "Follow Document Updates" icon. Based on this, the user can trigger this icon or set the switch control corresponding to this icon to the on state to trigger the document update subscription operation. At this time, in response to this document update subscription operation, the client sends the selected cloud document identifier in the document update subscription request to the cloud service, so that the cloud server can parse out the cloud document identifier from it and determine the cloud document corresponding to this cloud document identifier as the target document subscribed by the client.

[0129] In addition, in one embodiment, as Figure 5 shown, after the user hovers the mouse over the "Follow Document Updates" icon, the client can also present the description information of the document update reminder function, so that the user can understand the document update reminder function.

[0130] Furthermore, the client can also present a human-computer interaction interface, so that the user can set the subscription rules of the client for the target document through this human-computer interaction interface. Then, when the client sends the above-mentioned document update subscription request to the cloud service, it can carry the subscription rules set by the user for the target document in the document update subscription request together, which enables the cloud service to parse out the subscription rules of the client for the target document from the document update subscription request.

[0131] In addition, in one embodiment, when the client enables the document update reminder function for the target document, the client side can present a reminder message 51 as exemplified in Figure 5 so that the user can know the on state of the document update reminder function and improve the user experience.

[0132] Similarly, when the client fails to enable the document update reminder function for the target document, such as when the client does not have the collaboration permission for the target document, the client side can present a reminder message 52 as exemplified in Figure 5 so that the user can know the reason for the failure to successfully enable the document update reminder function, assist the user in solving the problem, and improve the user experience.

[0133] Step 402: In response to a document update event that matches the subscription rules for the target document, send an update reminder message for the document update event to the client.

[0134] For a detailed description of this step, reference can be made to the relevant description in the above Figure 2 illustrated embodiment, which will not be elaborated here.

[0135] Figure 4The process shown, by receiving a document update subscription request from a client, parsing out the cloud document identifier and the client's subscription rules from the document update subscription request, determining the cloud document corresponding to the cloud document identifier as the target document subscribed by the client, and in response to a document update event matching the subscription rules occurring for the target document, sending an update reminder message of the document update event to the client, can implement the function of enabling document update reminders for cloud documents and meet user needs.

[0136] Figure 6 This is a flowchart of an embodiment of another document update reminder method provided by an embodiment of the present application. Figure 6 The process shown in Figure 2 Based on the process shown, includes the following steps:

[0137] Step 601, receive a document update subscription request from a client, parse out the target keyword and the client's subscription rules from the document update subscription request, and determine the target document subscribed by the client according to the target keyword.

[0138] As can be seen from the description of step 601, the technical solution provided by the embodiment of the present application supports users to specify the target documents that need to pay attention to document updates in the way of specifying keywords. Here, the target document can be a local document or a cloud document. When the cloud service determines the target document subscribed by the client according to the target keyword, it can determine the document whose document title or document content contains the target keyword as the target document subscribed by the client. In this way, the flexibility of the client to specify the target document is further improved, and the user experience is improved.

[0139] Among them, as an optional implementation method, when the user wants to enable the document update reminder function, the user can trigger the client to present a search input box, so that the user can enter the above target keyword in the search input box. Further, the user can also specify the search scope, such as local documents, cloud documents, and the documents recently opened by the client (which can include cloud documents and local documents).

[0140] Among them, when the search scope specified by the user is cloud documents, the client can carry the target keyword entered by the user in the document update subscription request and send it to the cloud service, so that the cloud service parses out the target keyword from the document update subscription request and determines the target document subscribed by the client by finding the matching cloud document according to the target keyword.

[0141] When the search scope specified by the user is local documents, the client can find the matching local document according to the target keyword, and then apply the above Figure 3 The process shown to set the local document as the target document subscribed by the client.

[0142] Further, the client can also present a human-computer interaction interface, enabling the user to set the subscription rules for the target document through this human-computer interaction interface. Then, when the client sends the above-mentioned document update subscription request to the cloud service, it can carry the subscription rules set by the user for the target document in the document update subscription request, enabling the cloud service to parse the subscription rules of the client for the target document from the document update subscription request.

[0143] Step 602: In response to a document update event that matches the subscription rules for the target document, send an update reminder message for the document update event to the client.

[0144] For a detailed description of this step, reference can be made to the relevant description in the above Figure 2 illustrated embodiment, which will not be elaborated here.

[0145] Figure 6 In the illustrated process, by receiving a document update subscription request from the client, parsing the target keyword and the client's subscription rules from the document update subscription request, determining the target document subscribed by the client based on the target keyword, and in response to a document update event that matches the subscription rules for the target document, sending an update reminder message for the document update event to the client, it is possible to enable the user to specify the target document for which they need to pay attention to document updates in the form of a specified keyword, which further enhances the flexibility of the client when specifying the target document and improves the user experience.

[0146] Based on the above Figure 2 、 Figure 3 、 Figure 5 and Figure 6 illustrated processes, one more point is supplemented as follows:

[0147] The above-mentioned subscription rules can be the subscription rules described in any of the above embodiments, or can be used to indicate the reminder party specified by the client. That is to say, the client can, according to actual needs, set the collaborator of the target document as the reminder party. Then, after a document update event that matches the subscription rules for the target document occurs, the cloud service can send an update reminder message for the document update event to the collaborator of the target document. Here, the client can set all or part of the collaborators of the target document as the reminder party, and the embodiments of the present application do not limit this.

[0148] For example, in the Figure 1 illustrated system architecture, the user creates document A on device 102, sets document A as a collaborative document, and sets devices 103 and 104 as collaborators of document A. Subsequently, the user can choose to set device 103 as the reminder party, or set device 104 as the reminder party, or set both devices 103 and 104 as the reminder party.

[0149] As can be seen, by applying the above embodiments, it is possible to implement the reminder party for document updates to be set independently by the user, improving the user experience.

[0150] Furthermore, the user can also independently cancel the set reminder party, which further meets the user's usage requirements and improves the user experience.

[0151] To achieve this, in one embodiment, the cloud service receives an unsubscribe request from the client and cancels the setting of the collaborator indicated by the unsubscribe request as the reminder party. The user mentioned here is usually the creator of the document.

[0152] Among them, as an optional implementation method, the user can complete the above-mentioned setting of the reminder party for document updates and canceling the set reminder party through the human-computer interaction interface provided by the client he owns. As for the specific human-computer interaction interface and user operation method, this application does not make specific limitations.

[0153] Figure 7 FIG. is a flowchart of an embodiment of another document update reminder method provided by an embodiment of this application. Figure 7 The shown process is based on Figure 2 the shown process and includes the following steps:

[0154] Step 701, receive a document update subscription request from the client, and determine the target document subscribed by the client and the subscription rule of the client for the target document.

[0155] Step 702, in response to a document update event that matches the subscription rule occurring for the target document, send an update reminder message of the document update event to the client.

[0156] For the detailed descriptions of steps 701 and 702, reference can be made to the relevant descriptions in any of the above embodiments, and details will not be repeated here.

[0157] Step 703, in response to the triggering of a set event, cancel the subscription of the client to the target document.

[0158] In one embodiment, the above set event includes at least one of the following: the client is canceled the access right to the target document, the target document is canceled for collaboration, and the client triggers an unsubscribe operation.

[0159] Among them, from the relevant descriptions in the above Figure 4 shown process, when the client has the collaboration permission for the target document, the client can enable the document update reminder function for the target document. Based on this, when the client is canceled the access right to the target document, it means canceling the subscription of the client to the target document.

[0160] For example, user A creates document B, sets document B as a collaborative document, and grants user B the collaborative permission for document B. Then, user B can enable the document update reminder function for document B based on the technical solution provided in the embodiments of the present application, so that when user A triggers a document update event for document B, user B can receive the corresponding update reminder message in a timely manner.

[0161] After that, assume that user A cancels user B's access permission to document B. Then, the subscription of user B to the target document is also cancelled accordingly. When user A triggers a document update event for document B, user B can no longer receive the corresponding update reminder message.

[0162] For another example, user A creates document C, sets document C as a collaborative document, and grants user B and user C the collaborative permission for document C. Then, user B and user C can respectively enable the document update reminder function for document C based on the technical solution provided in the embodiments of the present application, so that when user A or user B triggers a document update event for document C, user C can receive the corresponding update reminder message in a timely manner, and when user A or user C triggers a document update event for document C, user B can receive the corresponding update reminder message in a timely manner.

[0163] After that, assume that user A closes the collaboration for document C, that is, document C is cancelled from collaboration. Then, the subscriptions of user B and user C to the target document are also cancelled accordingly. When user A triggers a document update event for document B, neither user B nor user C can receive the corresponding update reminder message.

[0164] For another example, user A creates document D, sets document D as a collaborative document, and grants user B the collaborative permission for document D. Then, user B can enable the document update reminder function for document D based on the technical solution provided in the embodiments of the present application, so that when user A triggers a document update event for document D, user B can receive the corresponding update reminder message in a timely manner. When user B no longer needs to pay attention to the update dynamics of document D, the user can trigger an unsubscribe operation for document D, so that the cloud service cancels the subscription of user B to document D. After that, when user A triggers a document update event for document D, user B will no longer receive the corresponding update reminder message. Here, referring to Figure 5 the example of, when the client successfully cancels the subscription for the target document, a reminder message 53 can be presented on the client side to remind the user that no update reminder message for the target document will be received again, improving the user experience.

[0165] Figure 7In the process shown, by canceling the client's subscription to the target document in response to the triggering of a set event, it is possible to control the enabling status of the document update reminder function of the client for the document through the collaboration status of the document and the client's collaboration permissions for the document. This enables the automatic closing of the document update reminder function of the client for the document when the collaboration status of the document and the client's collaboration permissions for the document change, without the need for the user to perform additional operations, thus enhancing the user experience. Additionally, it allows the user to independently choose to subscribe to or cancel the subscription to the update dynamics of the document, further enhancing the user experience.

[0166] In any of the above embodiments, the specific implementation of the cloud service sending an update reminder message for a document update event to the client includes: sending the update reminder message for the document update event to the message subscription queue of the client in the message center, so that the message center can obtain the update reminder message from the message subscription queue and push it to the client.

[0167] By using the message center architecture to push the update reminder message, the push efficiency can be improved and the user experience can be enhanced.

[0168] Finally, in one embodiment, different update message reminder methods can also be set for different remindees. The differences in the update message reminder methods mentioned here can include differences in form or differences in reminder timing.

[0169] Specifically, referring to Figure 8 , it is an example of an update reminder message. Figure 8 It is an update reminder message in text form. In practical applications, there can also be update reminder messages in other forms such as voice and pictures. Referring to the example in Figure 8 , the user can further trigger to view the specific document update content. For example, the user can click on the "View" icon. At this time, the client can automatically open the target document in response to the user's triggering operation on the "View" icon and can also locate to the position where the update occurred in the target document, which further enhances the user experience.

[0170] In terms of reminder timing, immediate reminders can be set for important remindees, while delayed reminders can be set for unimportant remindees, so as to preferentially ensure that the update reminder message is notified to important remindees when resources are limited.

[0171] Figure 9 This is a block diagram of an embodiment of a document update reminder device provided by an embodiment of the present application. As shown in Figure 9 , the device includes:

[0172] A subscription module 901, configured to receive a document update subscription request from a client, determine a target document subscribed by the client, and determine a subscription rule of the client for the target document;

[0173] A reminder module 902, configured to send an update reminder message of the document update event to the client in response to a document update event that matches the subscription rule occurring for the target document.

[0174] In a possible implementation, the subscription module 901 includes:

[0175] A parsing unit, configured to parse a target keyword from the document update subscription request;

[0176] A determination unit, configured to determine the target document subscribed by the client according to the target keyword.

[0177] In a possible implementation, the subscription module 901 is specifically configured to:

[0178] Parse the subscription rule of the client for the target document from the document update subscription request.

[0179] In a possible implementation, the subscription rule for the target document includes:

[0180] When the client sets a collaborator as a reminder recipient, after a document update event that matches the subscription rule occurs for the target document, send an update reminder message of the document update event to the collaborator.

[0181] In a possible implementation, the apparatus further includes:

[0182] A first unsubscribe module, configured to receive an unsubscribe request from the client and cancel the collaborator indicated by the unsubscribe request as a reminder recipient.

[0183] In a possible implementation, the subscription rule is used to indicate attention to document updates; the reminder module is specifically configured to:

[0184] In response to any collaborator of the target document performing a document update event on the target document, send an update reminder message of the document update event to the client.

[0185] In a possible implementation, the subscription rule is used to indicate attention to updates of a target collaborator to a document; the reminder module 902 is specifically configured to:

[0186] In response to the target collaborator performing a document update event on the target document, send an update reminder message of the document update event to the client.

[0187] In a possible implementation manner, the subscription rule is used to indicate attention to document updates within a target time period; the reminder module 902 is specifically configured to:

[0188] In response to at least one collaborator of the target document performing a document update event on the target document within the target time period, send an update reminder message of the document update event to the client.

[0189] In a possible implementation manner, the subscription rule is used to indicate attention to updates of a target area in a document; the reminder module 902 is specifically configured to:

[0190] In response to at least one collaborator of the target document performing a document update event on the target area in the target document, send an update reminder message of the document update event to the client.

[0191] In a possible implementation manner, the device further includes:

[0192] A second unsubscribe module, configured to cancel the client's subscription to the target document in response to the triggering of a set event; wherein, the set event includes at least one of the following: the client is cancelled the access right to the target document, the target document is cancelled collaboration.

[0193] In a possible implementation manner, the reminder module 902 is specifically configured to:

[0194] Send the update reminder message of the document update event to the message subscription queue of the client in the message center, so that the message center obtains the update reminder message from the message subscription queue and pushes it to the client.

[0195] As Figure 10 shown, an embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0196] The memory 113 is used to store a computer program.

[0197] In an embodiment of the present application, when the processor 111 is used to execute the program stored on the memory 113, it implements the document update reminder method provided by any one of the foregoing method embodiments, including:

[0198] Receive a document update subscription request from a client, determine the target document subscribed by the client, and determine the subscription rules of the client for the target document;

[0199] In response to a document update event that matches the subscription rules occurring in the target document, send an update reminder message of the document update event to the client.

[0200] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the document update reminder method provided in any one of the foregoing method embodiments are implemented.

[0201] The device embodiments described above are merely illustrative. 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, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0202] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the related technology, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0203] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless otherwise clearly specified in the context, the singular forms "a", "an", and "the" as used herein may also include the plural form. The terms "include", "comprise", "contain", and "have" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be executed in the specific order described or illustrated, unless the execution order is clearly stated. It should also be understood that alternative or additional steps may be used.

[0204] The above are only specific embodiments of the present application, enabling those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to these embodiments shown herein, but rather to the broadest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for reminding of document update, characterized in that, The method includes: Receiving a document update subscription request from a client, determining the target document subscribed by the client, and determining the subscription rule of the client for the target document; In response to a document update event matching the subscription rule occurring for the target document, sending an update reminder message of the document update event to the client.

2. The method according to claim 1, characterized in that, The determining the target document subscribed by the client includes: Parsing out a target keyword from the document update subscription request; Determining the target document subscribed by the client according to the target keyword.

3. The method according to claim 1 or 2, characterized in that, The determining the subscription rule of the client for the target document includes: Parsing out the subscription rule of the client for the target document from the document update subscription request.

4. The method according to claim 1, characterized in that, The method further includes: Receiving an unsubscribe request from the client, and canceling the setting of the collaborator indicated by the unsubscribe request as the reminder recipient.

5. The method according to claim 1, characterized in that, The subscription rule is used to indicate attention to document updates; The sending the update reminder message of the document update event to the client in response to a document update event matching the subscription rule occurring for the target document includes: In response to any collaborator of the target document performing a document update event on the target document, sending an update reminder message of the document update event to the client.

6. The method according to claim 1, characterized in that, The subscription rule is used to indicate attention to the update of the document by a target collaborator; the sending the update reminder message of the document update event to the client in response to a document update event matching the subscription rule occurring for the target document includes: In response to the target collaborator performing a document update event on the target document, sending an update reminder message of the document update event to the client.

7. The method according to claim 1, characterized in that, The subscription rule is used to indicate attention to document updates within a target time period; the sending the update reminder message of the document update event to the client in response to a document update event matching the subscription rule occurring for the target document includes: In response to at least one collaborator of the target document performing a document update event on the target document within the target time period, sending an update reminder message of the document update event to the client.

8. The method according to claim 1, characterized in that, The subscription rule is used to indicate attention to the update of a target area in the document; the sending the update reminder message of the document update event to the client in response to a document update event matching the subscription rule occurring for the target document includes: In response to at least one collaborator of the target document performing a document update event on the target area in the target document, sending an update reminder message of the document update event to the client.

9. The method according to claim 1, characterized in that, The method further includes: In response to the triggering of a set event, canceling the subscription of the client to the target document; wherein, the set event includes at least one of the following: the client is canceled the access right to the target document, the target document is canceled collaboration.

10. The method according to claim 1, characterized in that, The sending the update reminder message of the document update event to the client includes: Send the update reminder message of the document update event to the message subscription queue of the client in the message center, so that the message center can obtain the update reminder message from the message subscription queue and push it to the client.

11. A device for reminding of document update, characterized in that, The device includes: A subscription module, configured to receive a document update subscription request from a client, determine the target document subscribed by the client, and determine the subscription rule of the client for the target document; A reminder module, configured to send an update reminder message of the document update event to the client in response to a document update event that matches the subscription rule for the target document.

12. An electronic device, characterized in that, It includes: A processor and a memory, where the processor is configured to execute a document update reminder program stored in the memory to implement the document update reminder method according to any one of claims 1 to 10.

13. A storage medium, characterized in that, The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the document update reminder method according to any one of claims 1 to 10.

Images