Matter reminder method, system, terminal device and storage medium

Abstract

The present application provides a matter reminder method, system, terminal device and storage medium, the method comprising: when an operation on a target file is monitored, obtaining a target operation type corresponding to the operation; if the obtained target operation type is the same as the preset operation type, querying the target reminder information of the monitored file under the obtained target operation type; and performing matter reminders according to the target reminder information. The present application is based on the judgment between the operation type of the operation and the preset operation type to judge whether a matter reminder is required for the monitored file. When it is judged that the operation type of the operation is the same as the preset operation type, the target reminder information under the corresponding operation type is queried according to the monitored file, and the queried target reminder information is used to remind the user of matters, so that when a specific operation is performed on the monitored file, it can effectively remind the user, thereby improving the user's experience.

Description

Technical Field

[0001] The present application relates to the field of computer applications, and in particular to a method, system, terminal device, and storage medium for reminding matters. Background Art

[0002] With the development of computer technology, more and more software applications are becoming increasingly widespread. Among them, the arrangement, setting and reminder of matters are particularly popular among users. Users can set up a variety of reminder services through terminal devices. For example, users can pre-set to-do items and time reminder points for when to process the to-do items in the terminal device. The terminal device reminds the user of the to-do items at the time point, thereby effectively preventing the user from forgetting the to-do items.

[0003] In the existing event reminder process, users can only set event reminders based on time or geographic location. However, in daily life, the events that users need to be reminded of may not be limited to time or geographic location. Therefore, the existing event reminder method is difficult to meet the needs of users, resulting in a low user experience. Summary of the Invention

[0004] The embodiments of the present application provide a matter reminder method, system, terminal device and storage medium, which aim to solve the problem that in the existing matter reminder process, file processing based on specific matters cannot serve as a matter reminder.

[0005] In a first aspect, an embodiment of the present application provides a method for reminding an event, the method comprising:

[0006] When an operation on a target file is detected, a target operation type corresponding to the operation is obtained;

[0007] If the acquired target operation type is the same as the preset operation type, querying the target reminder information of the monitored file under the acquired target operation type;

[0008] Issue reminders based on the target reminder information.

[0009] Compared with the prior art, the beneficial effects of the embodiments of the present application are: based on the judgment between the operation type of the operation and the preset operation type, it is determined whether a reminder is needed for the monitored file. When it is determined that the operation type of the operation is the same as the preset operation type, the target reminder information under the corresponding operation type is queried according to the monitored file, and the queried target reminder information is used to remind the user, so that when a specific operation is performed on the monitored file, it can effectively remind the user, thereby improving the user experience.

[0010] Furthermore, if the acquired target operation type is the same as the preset operation type, querying target reminder information of the monitored file under the acquired target operation type includes:

[0011] If the target operation type obtained is the same as the preset operation type, querying the event reminder data of the monitored file, wherein the event reminder data stores the correspondence between the preset operation type and the reminder list, and the reminder list stores the correspondence between different application identifiers and reminder information;

[0012] querying a target reminder list in the event reminder data according to the acquired target operation type;

[0013] Obtain the identifier of the source application of the operation. If the identifier of the source application matches any application identifier stored in the target reminder list, search for corresponding reminder information according to the matched application identifier, and set the found reminder information as the target reminder information.

[0014] Furthermore, after setting the found reminder information as the target reminder information, the method further includes:

[0015] Obtaining the application account of the source application;

[0016] If the application account is the same as the preset account, the account reminder information is queried according to the application account, and the account reminder information is added to the target reminder information. The account reminder information is the content to be reminded preset for the application account.

[0017] Furthermore, obtaining the identifier of the source application of the operation includes:

[0018] Obtaining an access record of the monitored file, wherein the access record stores a correspondence between an application identifier and an operation type;

[0019] In the access record, an identifier of an application corresponding to an operation type that is the same as the acquired target operation type is searched, and the searched identifier of the application is used as the identifier of the source application of the operation.

[0020] Furthermore, after querying the identifier of an application corresponding to an operation type that is the same as the acquired target operation type, and using the queried identifier of the application as the identifier of the source application of the operation, the method further includes:

[0021] Obtaining an operation record of the source application, and searching the operation record for an operation object corresponding to an operation time and an operation type of the operation;

[0022] If the queried operation object is not the monitored file, or the operation object is not queried, an error prompt is sent for the operation.

[0023] Furthermore, after the step of providing an event reminder according to the target reminder information, the method further includes:

[0024] If a confirmation instruction for the event reminder is received, no event reminder will be issued when the operation is performed again on the monitored file within the first preset time interval;

[0025] If a denial instruction for the matter reminder is received, canceling the operation and determining whether the operation is performed on the monitored file within a second preset time interval;

[0026] If the operation is performed on the monitored file within the second preset time interval, no event reminder is performed.

[0027] Furthermore, after the step of providing an event reminder according to the target reminder information, the method further includes:

[0028] Determine whether the reminder mode of the target reminder information is a periodic reminder;

[0029] If the reminder mode of the target reminder information is not the periodic reminder, deleting the target reminder information;

[0030] If the reminder mode of the target reminder information is the periodic reminder, determine whether an information update instruction for the target reminder information is received; if the information update instruction for the target reminder information is received, update the target reminder information according to the information update instruction; if the information update instruction for the target reminder information is not received, update the target reminder information according to the preset default information.

[0031] Furthermore, after the step of determining that the target operation type is the same as the preset operation type, the method further includes:

[0032] Acquire operation status information of executing the operation, the operation status information including operation time and / or operation address, the operation address including physical address and network address;

[0033] If the operation status information satisfies the operation status condition, querying the target reminder information of the monitored file under the target operation type, wherein the operation status condition is that the operation time and / or operation address in the operation status information is a preset operation time and preset operation address;

[0034] Issue reminders based on the target reminder information.

[0035] In a second aspect, an embodiment of the present application provides an event reminder system, including:

[0036] An operation type acquisition module is used to acquire a target operation type corresponding to an operation on a target file when an operation on the target file is detected;

[0037] a reminder information query module, configured to query target reminder information of the monitored file under the acquired target operation type if the acquired target operation type is the same as a preset operation type;

[0038] The event reminder module is used to provide event reminders based on the target reminder information.

[0039] In a third aspect, an embodiment of the present application provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-described method when executing the computer program.

[0040] In a fourth aspect, an embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and the computer program implements the above-mentioned method when executed by a processor.

[0041] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a terminal device, enables the terminal device to execute the matter reminder method described in any one of the above-mentioned first aspects.

[0042] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art.

[0044] Figure 1 This is a flowchart of the event reminder method provided by the first embodiment of the present application;

[0045] Figure 2 is a schematic diagram of the target file provided by the first embodiment of the present application;

[0046] Figure 3 This is a flowchart of the event reminder method provided in the second embodiment of the present application;

[0047] Figure 4 This is a flowchart of the event reminder method provided in the third embodiment of the present application;

[0048] Figure 5This is a flowchart of the event reminder method provided in the fourth embodiment of the present application;

[0049] Figure 6 Schematic diagram of the structure of the event reminder system provided in the fifth embodiment of the present application;

[0050] Figure 7 This is a structural diagram of the terminal device provided in the sixth embodiment of the present application. DETAILED DESCRIPTION

[0051] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0052] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0053] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0054] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0055] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0056] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0057] Currently, there are many time-based reminder software and location-based reminder software. However, the things that users need to be reminded of during their daily work may not be limited to time or location. For example, the things that need to be reminded are dependent on a specific behavior. For example, when processing a certain file, a corresponding reminder is required. For example, the thing that needs to be reminded is: when the user sends a specified weekly report file, remind the user to add a test report. However, relying solely on time or location cannot achieve the above purpose. That is, the existing reminder method is difficult to meet the needs of users, resulting in a low user experience. In order to solve the above technical problems, the present application provides a reminder method, system, mobile terminal and storage medium that can provide corresponding reminders when performing specific operations on files.

[0058] An event reminder method based on file monitoring can achieve the effect of reminding users of events when any monitored file triggers a specific operation.

[0059] Example 1

[0060] See also Figure 1 , is a flowchart of the event reminder method provided in the first embodiment of the present application, comprising the steps of:

[0061] Step S10, when an operation on a target file is detected, obtaining a target operation type corresponding to the operation;

[0062] Among them, the matter reminder method can be applied to any operating system, for example, the operating system can be a Windows system, a Linux system, a Unix system, a MacOS system, an Android system, etc. The operating system can be installed on any terminal device, and the terminal device can be a mobile phone, a computer tablet or a wearable smart device, etc. Optionally, any file in the operating system can be set as a monitored file according to user needs. A monitoring list is pre-stored on the operating system, and the monitoring list stores the file names or file paths of all monitored files. When an operation is performed on a file corresponding to any file name or file path in the monitoring list, the operation type corresponding to the operation is obtained.

[0063] Optionally, the operation type is a description of any operation performed on the target file, for example, see Figure 2 The operation descriptions of the copy operation, delete operation, open operation, or send operation as an attachment for the target file weekly_report.doc can all be set to this operation type.

[0064] Specifically, the operation types corresponding to the operations on the monitored files include ACCESS (file is read), CLOSE_WRITE (modified and closed), CREATE (create), DELETE (delete), OPEN (opened), MODIFY (modified), etc. In this step, the correspondence between all operation types and corresponding operation instructions is pre-stored on the operating system. The operation instruction can be an operation code or an operation identifier, etc. Therefore, by obtaining the operation instruction of the operation, the operation type corresponding to the operation can be queried.

[0065] Step S20, determining whether the acquired target operation type is the same as the preset operation type;

[0066] Among them, by judging whether the obtained target operation type is the same as the preset operation type, it is determined whether a reminder is needed for the operation. The preset operation type can be set according to user needs. The preset operation type can be an operation description for any execution operation of the target file. The preset operation types registered by different monitored files can be the same or different, and a monitored file can register multiple different preset operation types. Optionally, the operating system can use a function to perform monitoring registration between the monitored file and the preset operation type.

[0067] Specifically, the operating system pre-stores the correspondence between all monitored files and preset operation types. For example, for monitored file A, the user sets ACCESS and MODIFY as the preset operation types of monitored file A on the operating system. That is, in this step, it is determined whether the target operation type obtained is ACCESS or MODIFY.

[0068] If the target operation type obtained is different from the preset operation type, that is, for the monitored file A, when the target operation type obtained is not ACCESS or MODIFY, the steps of the event reminder method are stopped and no event reminder is performed for the operation.

[0069] If the target operation type obtained is the same as the preset operation type, that is, for the monitored file A, when the target operation type obtained is ACCESS or MODIFY, step S30 is executed;

[0070] Step S30, querying target reminder information of the monitored file under the acquired target operation type;

[0071] The target reminder information is information of the type of text, numbers, images or voice preset by the user. The target reminder information is used to remind the user when the target operation type is executed on the monitored file, so as to remind the user of matters that need to be paid attention to when performing the operation. The operating system stores reminder information corresponding to all monitored files when performing different operation types. For example, the reminder information set for the monitored file A includes: ACCESS-first reminder information, MODIFY-second reminder information. Optionally, the information content in the first reminder information and the second reminder information can be set according to the user's needs. The message content can be text, numbers, images or voice, and the reminder information corresponding to different operation types can be the same or different.

[0072] Therefore, in this step, the corresponding reminder information can be effectively queried based on the obtained target operation type, and the queried reminder information is used as the target reminder information corresponding to the operation type, so that the reminder information corresponding to different preset operation types can be set to different contents according to the user's needs. When the obtained operation types are different, the queried reminder information can be different, which effectively improves the diversity of the reminder information setting.

[0073] Step S40, performing an event reminder according to the target reminder information;

[0074] Among them, the reminder method of the matter reminder corresponding to each target reminder information can be fixed according to the user's needs, or the matter reminder can be made based on the information type of the target reminder information. The optional reminder method of the matter reminder can be text reminder, image reminder, vibration reminder or sound and light reminder.

[0075] Specifically, when the reminder method of the matter reminder adopts a fixed method for reminder, the user's pre-set method is used for reminders for different target reminder information. For example, when the reminder method of the matter reminder is set to use text or image to remind, the reminder text or image corresponding to different target reminder information is different; when the reminder method of the matter reminder is set to use vibration reminder method for reminder, the vibration amplitude or frequency corresponding to different target reminder information is different; when the reminder method of the matter reminder is set to use sound and light reminder method for reminder, the voice volume, voice content, light brightness or light display time corresponding to different target reminder information is different.

[0076] Optionally, when using the information type based on the target reminder information to perform a corresponding reminder, the information type of the target reminder information is obtained and matched with the reminder method table pre-stored in the operating system to query the reminder method, and the target reminder information is executed according to the queried reminder method. For example, when the information type of the target reminder information is audio information, the queried reminder method is a voice reminder, and when the information type of the target reminder information is text information, the queried reminder method is a text reminder.

[0077] In this embodiment, a judgment is made based on the operation type of the operation and the preset operation type to determine whether a reminder is required for the monitored file. When it is determined that the operation type of the operation is the same as the preset operation type, the target reminder information under the corresponding operation type is queried according to the monitored file, and the queried target reminder information is used to remind the user, so that when a specific operation is performed on the monitored file, the user can be effectively reminded, thereby improving the user's usage experience.

[0078] Example 2

[0079] See also Figure 3 , is a flowchart of a matter reminder method provided by a second embodiment of the present application. The second embodiment is used to refine step S30 in the first embodiment to further describe how to query the target reminder information of the monitored file under the acquired target operation type. The matter reminder method includes the steps of:

[0080] Step S11, when an operation on a target file is detected, obtaining a target operation type corresponding to the operation;

[0081] Please refer to the explanation of step S10 in the first embodiment, and the explanation of this step will not be repeated.

[0082] Step S21, determining whether the acquired target operation type is the same as the preset operation type;

[0083] Please refer to the explanation of step S20 in the first embodiment, and the explanation of this step will not be repeated.

[0084] If the acquired target operation type is the same as the preset operation type, executing step S31;

[0085] Step S31, querying the event reminder data of the monitored file, and querying the target reminder list in the event reminder data according to the acquired target operation type;

[0086] Among them, the operating system stores the event reminder data of all monitored files, and the event reminder data stores the correspondence between multiple groups of different preset operation types and reminder lists. The reminder list stores the correspondence between different application identifiers and reminder information, and the reminder information corresponding to different application identifiers can be the same or different. In this step, the obtained target operation type is matched with the event reminder data, and the matched reminder list is set as the target reminder list.

[0087] For example, for the monitored file B, the event reminder data b corresponding to the monitored file B in the operating system includes a corresponding relationship: ACCESS-first reminder list, OPEN-second reminder list;

[0088] Optionally, the first reminder list includes a correspondence relationship: application identifier c-third reminder information, application identifier d-fourth reminder information, wherein the application identifier c is used to point to application C, and the application identifier d is used to point to application D.

[0089] Specifically, when the operation type acquired in step S11 is ACCESS, the target reminder list queried in this step is the first reminder list.

[0090] Step S41, obtaining the identifier of the source application of the operation;

[0091] The source application is an application that performs the operation on the monitoring file, and the identifier of the source application may be an application name or an application image of the source application.

[0092] Specifically, in this step, obtaining the identifier of the source application of the operation includes:

[0093] Step S411, obtaining access records of the monitored file;

[0094] The access record stores the correspondence between the identifier of the application that accessed the monitored file and the operation type at different time points;

[0095] For example, for the monitored file B, the access record C obtained includes: application identifier c-ACCESS and application identifier d-OPEN, then it is determined that at this time point, application C executed ACCESS on the monitored file B, and at the same time, application D executed OPEN on the monitored file B.

[0096] Step S412: In the access record, query the identifier of the application corresponding to the same operation type as the acquired target operation type, and use the identifier of the application obtained as the identifier of the source application of the operation;

[0097] When the operation type acquired in step S11 is ACCESS, the identifier of the application found is used as application identifier c, and application identifier c is used as the identifier of the source application of the operation, that is, the source application is application C.

[0098] Optionally, in this step, after using the queried application identifier as the identifier of the source application of the operation, the method further includes:

[0099] Step S413: Obtain the operation record of the source application, and search the operation record for an operation object corresponding to the operation time and operation type of the operation;

[0100] Among them, the operation record stores the operation information of the source application within a preset time. The preset time can be set according to the time value as needed. For example, the preset time can be set to 1 day, 1 hour or 10 minutes, etc. Each operation information stores the corresponding operation time, operation type and operation object. Therefore, in this step, the operation information in the operation record is matched based on the operation time and operation object corresponding to the operation type.

[0101] Step S414: If the queried operation object is not the monitored file, or the operation object is not queried, an error prompt is sent for the operation;

[0102] Among them, when the operation object queried is not the monitored file, or the operation object is not queried, it is determined that the source application did not perform the preset operation type on the monitored file within the operation time of the operation. Therefore, through the design of sending an error prompt for the operation, the user is reminded that an error has occurred regarding the operation, and the user is promptly reminded to troubleshoot.

[0103] Step S51, determining whether the identifier of the source application of the operation matches the application identifier stored in the target reminder list;

[0104] When the identifier of the source application of the operation is application identifier c, the application identifier c is matched with all application identifiers stored in the first reminder list, that is, it is determined whether the application identifier c has corresponding reminder information in the first reminder list.

[0105] Specifically, in this step, by determining whether the identifier of the source application of the operation matches the application identifier stored in the target reminder list, it is determined whether the source application is a preset application that requires a reminder when the preset operation type is executed on the monitored file. For example, if ACCESS is the preset operation type of the monitored file B, and it is found that the source application of the ACCESS executed on the monitored file B is application C, then it is determined whether reminder information is set for application C according to the target reminder list queried in step S31;

[0106] Further, when it is determined that the target reminder list queried in step S31 has reminder information set for application C, it is determined that when application C executes ACCESS on the monitored file B, an event reminder is required. When it is determined that the target reminder list queried in step S31 has no reminder information set for application C, it is determined that when application C executes ACCESS on the monitored file B, no event reminder is required. Therefore, when executing ACCESS on the monitored file B, event reminders can be set for different applications according to user needs.

[0107] If the source application identifier matches any application identifier stored in the target reminder list, executing step S61;

[0108] Step S61, searching for corresponding reminder information according to the matched application identifier, and setting the found reminder information as the target reminder information;

[0109] Among them, when the target reminder list queried in step S31 is the first reminder list, and the identifier of the source application of the operation obtained in step S41 is application identifier c, the corresponding relationship queried in the first reminder list is: application identifier c-third reminder information, therefore, the third reminder information is set as the target reminder information.

[0110] Optionally, in this step, after the step of setting the found reminder information as the target reminder information, the method further includes:

[0111] Step S610, obtaining the application account of the source application;

[0112] Wherein, when the source application is an application with a message sending function, the application account is the account logged in to the source application or the target user account of the source application to receive the message;

[0113] For example, when the source application is a mail application, the application account may be the sender's email address in the mail application (i.e., the logged-in account), or the application account may be the recipient's email address of the mail to be received (i.e., the target user account);

[0114] Step S611: If the application account is the same as the preset account, query the account reminder information according to the application account, and add the account reminder information to the target reminder information;

[0115] Among them, the operating system pre-stores the correspondence between multiple groups of different application accounts and corresponding account reminder information. The account reminder information is the content to be reminded preset for the application account. In the operating system, by setting the correspondence between the preset account and the account reminder information, further reminders of matters can be made based on different application accounts.

[0116] The account reminder information in this step is used to provide targeted information reminders to the corresponding preset account. For example, when the application account is the sender's mailbox, and the sender's mailbox is the preset first mailbox, the account reminder information corresponding to the preset first mailbox can be "The email carrying this file needs to carry today's work plan", and when the sender's mailbox is the preset second mailbox, the account reminder information corresponding to the preset second mailbox can be "The email carrying this file needs to carry tax returns", so that further reminders can be made based on different application accounts.

[0117] For example, when the mail application is performing a copy operation on a monitored file, and the copy operation is a preset operation type for the monitored file, the target reminder list corresponding to the copy operation stores the application identifier of the mail application. Then, the target reminder information corresponding to the target reminder list is queried according to the application identifier of the mail application, and the application account of the mail application is obtained to obtain account K. When it is determined that the account K is a preset account, the account reminder information is queried according to the account K to obtain account reminder information N, and the account reminder information N is added to the queried target reminder information, so that the effect of reminding different matters again can be achieved based on different application accounts.

[0118] Step S71, performing an event reminder according to the target reminder information;

[0119] In this embodiment, the operation types of all monitored files can be effectively monitored to determine whether it is necessary to query the corresponding event reminder data. By obtaining the identifier of the source application of the operation, it is queried whether there is corresponding target reminder information in the event reminder data, and event reminders are performed according to the queried target reminder information. When the monitored file performs a specific operation, it is also necessary to determine whether the source application for the specific operation is a preset application. Only when it is determined that the source application is a preset application, the user is reminded of the event, thereby making the event reminder more targeted and greatly improving the user experience.

[0120] Example 3

[0121] See also Figure 4 , is a flowchart of the event reminder method provided by the third embodiment of the present application. The third embodiment is used to refine the steps after step S40 in the first embodiment to further describe the subsequent operation steps of the event reminder method after the step of performing the event reminder according to the target reminder information. The event reminder method includes the steps of:

[0122] Step S12: when an operation on a target file is detected, obtaining a target operation type corresponding to the operation;

[0123] Please refer to the explanation of step S10 in the first embodiment, and the explanation of this step will not be repeated.

[0124] Step S22, determining whether the acquired target operation type is the same as the preset operation type;

[0125] Please refer to the explanation of step S20 in the first embodiment, and the explanation of this step will not be repeated.

[0126] If the acquired target operation type is the same as the preset operation type, executing step S30;

[0127] Step S32, querying target reminder information of the monitored file under the acquired target operation type;

[0128] Please refer to the explanation of step S30 in the first embodiment, and the explanation of this step will not be repeated.

[0129] Step S42, performing an event reminder according to the target reminder information;

[0130] Please refer to the explanation of step S40 in the first embodiment, and the explanation of this step will not be repeated.

[0131] Step S52: If a confirmation instruction for the event reminder is received, no event reminder is performed when the operation is performed again on the monitored file within the first preset time interval;

[0132] Among them, when a confirmation instruction for the matter reminder is received, it is determined that the user has viewed the target reminder information. Therefore, by performing the operation on the monitored file again within the first preset time interval, no matter reminder is issued, so as to prevent the interference caused by the target reminder information repeatedly reminding the user of the matter within the first preset time interval.

[0133] Optionally, the first preset time interval can be set according to needs. The first preset time interval can be set to 1 day, 1 hour or 10 minutes, etc. For example, if a confirmation instruction for the matter reminder is received, and when the first preset time interval is 10 minutes, no matter reminder will be issued when the operation is performed again on the monitored file within 10 minutes.

[0134] Step S62, if a denial instruction for the event reminder is received, cancel the operation;

[0135] If a denial instruction for the event reminder is received, it is determined that the user realizes that the operation on the monitored file needs to be modified after receiving the event reminder. Therefore, the operation is revoked to prevent erroneous operation on the monitored file.

[0136] For example, when the operation performed on the monitored file is DELETE, and DELETE is the preset operation type of the monitored file, and the target reminder information corresponding to the preset operation type is "the file needs to be sent to the mailbox before 7 o'clock", then when it is determined that DELETE is performed on the monitored file, the user is reminded of the matter based on "the file needs to be sent to the mailbox before 7 o'clock", and when a denial instruction for the matter reminder is received, the DELETE of the monitored file is revoked, thereby preventing the erroneous deletion of the monitored file.

[0137] Step S72, determining whether the operation is performed on the monitored file within a second preset time interval;

[0138] The second preset time interval can be set according to needs. For example, the second preset time interval can be set to 1 day, 1 hour, or 10 minutes.

[0139] Step S82: If the operation is performed on the monitored file within the second preset time interval, no event reminder is performed;

[0140] Among them, if the operation is performed on the monitored file within the second preset time interval, it is determined that the user has viewed the target reminder information. At this time, when the monitored file performs the same operation again, there is no need to remind the user again.

[0141] In this embodiment, the design determines whether a confirmation instruction for the matter reminder is received to determine whether the user has viewed the target reminder information. When it is determined that the user has viewed the target reminder information, no matter reminder will be given when the operation is performed again on the monitored file within the first preset time interval, which effectively prevents the interference caused by the target reminder information repeatedly reminding the user within the first preset time interval. When it is determined that a denial instruction for the matter reminder is received, it is determined that the user realizes that the operation on the monitored file needs to be modified after receiving the matter reminder, and the operation is revoked to prevent erroneous operation on the monitored file.

[0142] Example 4

[0143] See also Figure 5 , is a flowchart of a matter reminder method provided by a fourth embodiment of the present application. The fourth embodiment is used to refine step S30 in the first embodiment to further describe how to query the target reminder information of the monitored file under the acquired target operation type, including the steps of:

[0144] Step S13, when an operation on the target file is detected, obtaining a target operation type corresponding to the operation;

[0145] Please refer to the explanation of step S10 in the first embodiment, and the explanation of this step will not be repeated.

[0146] Step S23, determining whether the acquired target operation type is the same as the preset operation type;

[0147] Please refer to the explanation of step S20 in the first embodiment, and the explanation of this step will not be repeated.

[0148] If the acquired target operation type is the same as the preset operation type, executing step S33;

[0149] Step S33, obtaining operation status information of executing the operation;

[0150] The operation status information includes operation time and / or operation address, and the operation address includes a physical address and a network address.

[0151] Step S43, determining whether the operating state meets the operating state condition;

[0152] The operation status condition is that the operation time and / or operation address in the operation status information is a preset operation time and preset operation address. That is, by judging whether the operation status satisfies the design of the operation status condition, it is judged whether the operation time or operation address of the operation is the time or address preset by the user. For example, the preset time may be set to 9 am to 5 pm. When the operation time for performing the operation is not within the time range of 9 am to 5 pm, there is no need to issue a reminder for the operation;

[0153] For example, the preset address can be set to the network port address or routing IP address in the user's home address or office address to determine whether the operation address of the operation is within the user's preset home address or office address. When it is determined that the operation address of the operation is not the user's preset home address or office address, there is no need to issue a reminder for the operation.

[0154] If the operation status information satisfies the operation status condition, that is, when it is determined that the operation time of the operation is within the time preset by the user and / or the operation address of the operation is the home address or office address preset by the user, step S53 is executed;

[0155] Step S53, querying the target reminder information of the monitored file under the target operation type;

[0156] Step S63, performing an event reminder according to the target reminder information;

[0157] Among them, please refer to the explanation of step S40 in the first embodiment, and this step will not be repeated for the explanation.

[0158] Optionally, in this step, after the step of providing an event reminder according to the target reminder information, the method further includes:

[0159] Step S631, determining whether the reminder mode of the target reminder information is a periodic reminder;

[0160] Among them, by judging whether the target reminder information is set with a cycle parameter, it is judged whether the reminder method of the target reminder information is a periodic reminder. The periodic reminder is a periodic information reminder based on the cycle parameter. Optionally, the cycle parameter can be the remaining number of reminders or the cycle time. For example, the cycle time can be set to Monday to Friday, that is, from Monday to Friday of each week, event reminders can be made for the target reminder information. The cycle time can be set to Friday, that is, on Friday of each week, event reminders can be made for the target reminder information.

[0161] Step S632: If the reminder mode of the target reminder information is not the periodic reminder, delete the target reminder information;

[0162] When it is determined that the target reminder information is not set with a loop parameter, it is determined that the reminder mode of the target reminder information is a one-time reminder, that is, after the matter reminder is made according to the target reminder information, the target reminder information is directly deleted.

[0163] Step S633: If the reminder mode of the target reminder information is the periodic reminder, determining whether an information update instruction for the target reminder information is received;

[0164] The information update instruction is used to update the reminder parameters corresponding to the target reminder information.

[0165] Step S634: if the information update instruction for the target reminder information is received, the target reminder information is updated according to the information update instruction; if the information update instruction for the target reminder information is not received, the target reminder information is updated according to preset default information.

[0166] Step S73: If the operation status information does not meet the operation status condition, the steps of the event reminder method are ended.

[0167] In this embodiment, it is determined whether the reminder mode of the target reminder information is a periodic reminder to determine whether the target reminder information is deleted, and when it is determined that the reminder mode of the target reminder information is a periodic reminder, the target reminder information is updated according to the received information update instruction or the preset default information, so that after the target reminder information reminds the user of a matter, the content can be reset based on the user's needs or the default information.

[0168] Example 5

[0169] Corresponding to the matter reminder method described in the above embodiment, Figure 6 A structural diagram of the event reminder system 100 provided in the fifth embodiment of the present application is shown. For the sake of convenience, only the parts related to the embodiment of the present application are shown.

[0170] Reference Figure 6 The system includes: an operation type acquisition module 10, a reminder information query module 11 and an event reminder module 12, wherein:

[0171] The operation type acquisition module 10 is configured to acquire a target operation type corresponding to an operation on a target file when an operation on the target file is detected.

[0172] The reminder information query module 11 is configured to query the target reminder information of the monitored file under the obtained target operation type if the obtained target operation type is the same as the preset operation type.

[0173] Among them, the reminder information query module 11 is also used for: if the target operation type obtained is the same as the preset operation type, then querying the matter reminder data of the monitored file, the matter reminder data stores the correspondence between multiple groups of different preset operation types and reminder lists, and the reminder list stores the correspondence between different application identifiers and reminder information; querying the target reminder list in the matter reminder data according to the obtained target operation type; obtaining the identifier of the source application of the operation, if the identifier of the source application matches any application identifier stored in the target reminder list, then searching for the corresponding reminder information according to the matched application identifier, and setting the found reminder information as the target reminder information.

[0174] Furthermore, the reminder information query module 11 is also used to: obtain the application account in the source application; if the application account is the same as the preset account, query the account reminder information based on the application account, and add the account reminder information to the target reminder information, wherein the account reminder information is the preset reminder content for the application account. Optionally, the reminder information query module 11 is also used to: obtain the access record of the monitored file, wherein the access record stores the correspondence between the application identifier and the operation type; in the access record, query the identifier of the application corresponding to the operation type that is the same as the obtained target operation type, and use the queried application identifier as the identifier of the source application of the operation.

[0175] Furthermore, the reminder information query module 11 is further used to: obtain the operation record of the source application, and query the operation object corresponding to the operation time and operation type of the operation in the operation record; if the operation object queried is not the monitored file, or the operation object is not queried, an error prompt is sent for the operation,

[0176] The event reminder module 12 is used to make event reminders according to the target reminder information.

[0177] The event reminder module 12 is further configured to: if a confirmation instruction for the event reminder is received, not to issue an event reminder when the operation is performed again on the monitored file within a first preset time interval;

[0178] If a denial instruction for the matter reminder is received, canceling the operation and determining whether the operation is performed on the monitored file within a second preset time interval;

[0179] If the operation is performed on the monitored file within the second preset time interval, no event reminder is performed.

[0180] In addition, the event reminder system 100 further includes:

[0181] The reminder information management module 13 is used to determine whether the reminder mode of the target reminder information is a periodic reminder; if the reminder mode of the target reminder information is not the periodic reminder, delete the target reminder information; if the reminder mode of the target reminder information is the periodic reminder, determine whether an information update instruction for the target reminder information is received; if the information update instruction for the target reminder information is received, update the target reminder information according to the information update instruction; if the information update instruction for the target reminder information is not received, update the target reminder information according to the preset default information.

[0182] An operation status detection module 14 is configured to obtain operation status information of executing the operation, wherein the operation status information includes operation time and / or operation address, wherein the operation address includes a physical address and a network address;

[0183] If the operation status information satisfies the operation status condition, the reminder information query module 11 is prompted to query the target reminder information of the monitored file under the target operation type, so that the event reminder module 12 performs event reminders according to the target reminder information.

[0184] In this embodiment, a judgment is made based on the operation type of the operation and the preset operation type to determine whether a reminder is required for the monitored file. When it is determined that the operation type of the operation is the same as the preset operation type, the target reminder information under the corresponding operation type is queried according to the monitored file, and the queried target reminder information is used to remind the user, so that when a specific operation is performed on the monitored file, the user can be effectively reminded, thereby improving the user's usage experience.

[0185] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / modules are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment section and will not be repeated here.

[0186] Figure 7 This is a schematic diagram of the structure of the terminal device 2 provided in the sixth embodiment of the present application. Figure 7 As shown, the terminal device 2 of this embodiment includes: at least one processor 20 ( Figure 7 Only one processor is shown in the figure), a memory 21, and a computer program 22 stored in the memory 21 and executable on the at least one processor 20, wherein the processor 20 implements the steps of any of the above-mentioned method embodiments when executing the computer program 22.

[0187] The terminal device 2 can be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will understand that Figure 7 It is only an example of the terminal device 2 and does not constitute a limitation on the terminal device 2. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0188] The processor 20 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

[0189] In some embodiments, the memory 21 may be an internal storage unit of the terminal device 2, such as a hard disk or memory of the terminal device 2. In other embodiments, the memory 21 may also be an external storage device of the terminal device 2, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 2. Furthermore, the memory 21 may also include both an internal storage unit and an external storage device of the terminal device 2. The memory 21 is used to store an operating system, an application program, a boot loader, data, and other programs, such as the program code of the computer program. The memory 21 may also be used to temporarily store data that has been output or is to be output.

[0190] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0191] An embodiment of the present application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps of any of the above-mentioned method embodiments when executing the computer program.

[0192] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned various method embodiments can be implemented.

[0193] An embodiment of the present application provides a computer program product. When the computer program product is run on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned various method embodiments when executing the computer program product.

[0194] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process of the above-mentioned method embodiment by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium can at least include: any entity or device capable of carrying computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, mobile hard drive, magnetic disk, or optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals or telecommunication signals.

[0195] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0196] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0197] In the embodiments provided in this application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0198] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0199] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A method for reminding an event, characterized in that: The method comprises: When an operation on a target file is detected, a target operation type corresponding to the operation is obtained; If the acquired target operation type is the same as the preset operation type, querying the target reminder information of the monitored file under the acquired target operation type; Providing reminders based on the target reminder information; If the acquired target operation type is the same as the preset operation type, querying target reminder information of the monitored file under the acquired target operation type includes: If the target operation type obtained is the same as the preset operation type, querying the event reminder data of the monitored file, wherein the event reminder data stores the correspondence between the preset operation type and the reminder list, and the reminder list stores the correspondence between different application identifiers and reminder information; querying a target reminder list in the event reminder data according to the acquired target operation type; Obtain the identifier of the source application of the operation. If the identifier of the source application matches any application identifier stored in the target reminder list, search for the corresponding reminder information based on the matching application identifier, and set the found reminder information as the target reminder information; the source application is the application that performs the operation on the monitored file.

2. The method for reminding an event according to claim 1, wherein: After setting the found reminder information as the target reminder information, the method further includes: Obtaining the application account of the source application; If the application account is the same as the preset account, the account reminder information is queried according to the application account, and the account reminder information is added to the target reminder information. The account reminder information is the content to be reminded preset for the application account.

3. The method for reminding an event according to claim 1, wherein: The obtaining of the identifier of the source application of the operation includes: Obtaining an access record of the monitored file, wherein the access record stores a correspondence between an application identifier and an operation type; In the access record, an identifier of an application corresponding to an operation type that is the same as the acquired target operation type is searched, and the searched identifier of the application is used as the identifier of the source application of the operation.

4. The method for reminding an event according to claim 3, wherein: After querying the identifier of an application corresponding to an operation type identical to the acquired target operation type and using the queried identifier of the application as the identifier of the source application of the operation, the method further includes: Obtaining an operation record of the source application, and searching the operation record for an operation object corresponding to an operation time and an operation type of the operation; If the queried operation object is not the monitored file, or the operation object is not queried, an error prompt is sent for the operation.

5. The event reminder method according to claim 1, wherein: After the step of providing an event reminder according to the target reminder information, the method further includes: If a confirmation instruction for the event reminder is received, no event reminder will be issued when the operation is performed again on the monitored file within the first preset time interval; If a denial instruction for the matter reminder is received, canceling the operation and determining whether the operation is performed on the monitored file within a second preset time interval; If the operation is performed on the monitored file within the second preset time interval, no event reminder is performed.

6. The event reminder method according to claim 1, wherein: After the step of providing an event reminder according to the target reminder information, the method further includes: Determine whether the reminder mode of the target reminder information is a periodic reminder; If the reminder mode of the target reminder information is not the periodic reminder, deleting the target reminder information; If the reminder mode of the target reminder information is the periodic reminder, determine whether an information update instruction for the target reminder information is received; if the information update instruction for the target reminder information is received, update the target reminder information according to the information update instruction; if the information update instruction for the target reminder information is not received, update the target reminder information according to the preset default information.

7. The event reminder method according to claim 1, wherein: After the step of if the target operation type is the same as the preset operation type, the method further includes: Acquire operation status information of executing the operation, the operation status information including operation time and / or operation address, the operation address including physical address and network address; If the operation status information satisfies the operation status condition, querying the target reminder information of the monitored file under the target operation type, wherein the operation status condition is that the operation time and / or operation address in the operation status information is a preset operation time and preset operation address; Issue reminders based on the target reminder information.

8. A terminal device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

9. A storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images