Office schedule reminding method and device, equipment and storage medium

Abstract

The invention provides an office schedule reminding method and device, equipment and a storage medium. The method is applied to the technical field of computers, and comprises the steps of obtaining a schedule request sent by a first user, generating a corresponding schedule task according to the schedule request, determining receiving states of multiple invitees according to the schedule task when a target schedule corresponding to the schedule task is set to be required to be reminded, and displaying the receiving states of the invitees according to the receiving states of the invitees. And determining at least one to-be-reminded user from the plurality of invitees according to the receiving states of the plurality of invitees, and sending reminding information corresponding to the schedule task to the at least one to-be-reminded user. The reminding process is simplified, and the reminding efficiency is improved.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and particularly relates to an office schedule reminder method, device, equipment, and storage medium. Background Art

[0002] With the continuous development and popularization of information technology, in daily work, many schedule activities such as meeting invitations, questionnaire surveys, and itinerary arrangements from different people will be received or sent out. However, in modern society, the requirements for work efficiency and work quality are getting higher and higher. In this context, it is particularly important to simplify and optimize the work process.

[0003] In today's working environment, employees need to collaborate and cooperate with many people, including colleagues, customers, suppliers, partners, etc. It is necessary to timely understand and respond to each schedule activity. The existing office schedule reminder methods usually use traditional office schedule management methods such as memo records and calendar records to manage and remind office schedules.

[0004] The office schedule reminder methods in the prior art have the defects of being unable to automatically synchronize and record office schedules; it is inconvenient to synchronize after the office schedule information is updated; there is a lack of unified reminder for approaching deadlines and it is impossible to view everything at a glance. Summary of the Invention

[0005] This application provides an office schedule reminder method, device, equipment, and storage medium, which simplifies the reminder process, improves the reminder efficiency, and makes up for the deficiencies in office schedule reminders in the prior art.

[0006] In a first aspect, this application provides an office schedule reminder method, which includes:

[0007] Obtain a schedule request sent by a first user, and generate a corresponding schedule task according to the schedule request. The schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user;

[0008] When the target schedule corresponding to the schedule task is set to require a reminder, determine the receiving status of multiple invitees according to the schedule task;

[0009] Determine at least one user to be reminded from the multiple invitees according to the receiving status of the multiple invitees, and send reminder information corresponding to the schedule task to the at least one user to be reminded. The user to be reminded is an invitee whose acceptance status is the received status.

[0010] Optionally, the determining the receiving status of multiple invitees according to the schedule task includes:

[0011] Judge whether the invitee is the first user;

[0012] If the invited person is the first user, determine that the receiving status of the first user is the received status;

[0013] If the invited person is the second user, determine whether the first user exists in the blacklist of invitees of the second user;

[0014] If so, determine that the receiving status of the second user is the rejected status;

[0015] If not, determine whether the first user exists in the whitelist of invitees of the second user;

[0016] When the first user exists in the whitelist of invitees of the second user, determine that the receiving status of the second user is the received status;

[0017] When the first user does not exist in the whitelist of invitees of the second user, determine the receiving status of the second user according to the receiving identifier of the second user.

[0018] Optionally, determining the receiving status of the second user according to the receiving identifier of the second user includes:

[0019] If the receiving identifier of the second user is the first identifier, determine that the receiving status of the second user is the received status;

[0020] If the receiving identifier of the second user is the second identifier, determine that the receiving status of the second user is the rejected status.

[0021] Optionally, the schedule task further includes: a first reminder time, and sending reminder information corresponding to the schedule task to the at least one user to be reminded, including:

[0022] Obtain the reminder configuration information of the at least one user to be reminded, and judge whether there is personalized configuration information in the reminder configuration information according to the reminder configuration information;

[0023] When there is personalized configuration information in the reminder configuration information, determine a second reminder time according to the personalized configuration information, and update the reminder time of the personalized reminder user corresponding to the personalized configuration information to the second reminder time, where the personalized reminder user is any one of the at least one user to be reminded;

[0024] Send the reminder information to the personalized reminder user according to the second reminder time;

[0025] Send the reminder information to the users other than the personalized reminder user among the at least one user to be reminded according to the first reminder time.

[0026] Optionally, after sending the reminder information corresponding to the schedule task to the at least one user to be reminded, the method further includes:

[0027] Determine whether there is an update to the target schedule corresponding to the schedule task. If there is an update, obtain the updated schedule task, and determine the user information of multiple invitees corresponding to the updated schedule task according to the updated schedule task;

[0028] Determine the receiving status of multiple updated invitees according to the updated user information;

[0029] And determine whether to send the reminder information to the multiple updated invitees according to the receiving status of the multiple updated invitees.

[0030] Optionally, the determining the receiving status of multiple updated invitees according to the updated user information includes:

[0031] Determine a removal group, a maintenance group, and a new addition group according to the user information of the multiple updated invitees and the user information of the multiple invitees before the update;

[0032] Modify the receiving status of at least one invitee in the removal group to the removed status;

[0033] Synchronize the acceptance status of at least one invitee in the maintenance group;

[0034] Determine the corresponding receiving status according to the user information of at least one invitee in the new addition group.

[0035] In a second aspect, the present application provides an office schedule reminder device, and the device includes:

[0036] An obtaining module, configured to obtain a schedule request sent by a first user;

[0037] A generating module, configured to generate a corresponding schedule task according to the schedule request, where the schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user;

[0038] A determining module, configured to determine the receiving status of multiple invitees according to the schedule task when the target schedule corresponding to the schedule task is set to require a reminder;

[0039] The determining module is further configured to determine at least one user to be reminded from the multiple invitees according to the receiving status of the multiple invitees;

[0040] A sending module, configured to send reminder information corresponding to the schedule task to the at least one user to be reminded, where the user to be reminded is an invitee whose acceptance status is the received status.

[0041] Optionally, the office schedule reminder device further includes: a judgment module;

[0042] The judgment module is configured to judge whether the invitee is the first user;

[0043] The determination module is configured to determine that the reception status of the first user is the received status when the invitee is the first user;

[0044] The judgment module is further configured to judge whether the first user exists in the invitee blacklist of the second user when the invitee is the second user;

[0045] The determination module is further configured to determine that the reception status of the second user is the rejected status when the first user exists in the invitee blacklist of the second user;

[0046] The judgment module is further configured to judge whether the first user exists in the invitee whitelist of the second user when the first user does not exist in the invitee blacklist of the second user;

[0047] The determination module is further configured to determine that the reception status of the second user is the received status when the first user exists in the invitee whitelist of the second user;

[0048] The determination module is further configured to determine the reception status of the second user according to the reception identifier of the second user when the first user does not exist in the invitee whitelist of the second user.

[0049] Optionally, the determination module is configured to determine that the reception status of the second user is the received status when the reception identifier of the second user is the first identifier;

[0050] The determination module is further configured to determine that the reception status of the second user is the rejected status when the reception identifier of the second user is the second identifier.

[0051] Optionally, the acquisition module is configured to acquire reminder configuration information of the at least one user to be reminded;

[0052] The judgment module is configured to judge whether there is personalized configuration information in the reminder configuration information according to the reminder configuration information;

[0053] The determining module is configured to, when the personalized configuration information exists in the reminder configuration information, determine a second reminder time according to the personalized configuration information, and update the reminder time for reminding the personalized reminder user corresponding to the personalized configuration information to the second reminder time;

[0054] The sending module is configured to send the reminder information to the personalized reminder user according to the second reminder time;

[0055] The sending module is further configured to send the reminder information to the users other than the personalized reminder user among the at least one user to be reminded according to the first reminder time.

[0056] Optionally, the judging module is configured to judge whether there is an update to the target schedule corresponding to the schedule task;

[0057] The obtaining module is configured to obtain the updated schedule task when there is an update to the target schedule corresponding to the schedule task;

[0058] The determining module is configured to determine the user information of multiple invitees corresponding to the updated schedule task according to the updated schedule task;

[0059] The determining module is further configured to determine the receiving status of multiple updated invitees according to the updated user information;

[0060] The determining module is further configured to determine whether to send the reminder information to the multiple updated invitees according to the receiving status of the multiple updated invitees.

[0061] Optionally, the office schedule reminder device further includes: a processing module;

[0062] The determining module is configured to determine a removal group, a maintenance group, and a new group according to the user information of the multiple updated invitees and the user information of the multiple invitees before the update;

[0063] The processing module is configured to modify the receiving status of at least one invitee in the removal group to the removed status;

[0064] The processing module is further configured to synchronize the acceptance status of at least one invitee in the maintenance group;

[0065] The processing module is further configured to determine the corresponding receiving status according to the user information of at least one invitee in the new group.

[0066] In a third aspect, the present application provides an office schedule reminder device, including:

[0067] A memory;

[0068] Processor;

[0069] Wherein, the memory stores computer-executable instructions;

[0070] The processor executes the computer-executable instructions stored in the memory to implement the office schedule reminder method as described in the first aspect and various possible implementation manners of the first aspect.

[0071] In a fourth aspect, the present application provides a computer storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the office schedule reminder method as described in the first aspect and various possible implementation manners of the first aspect.

[0072] The present application provides an office schedule reminder method, device, equipment and storage medium. The method simplifies the reminder process and improves the reminder efficiency by obtaining a schedule request sent by a first user, generating a corresponding schedule task according to the schedule request, determining the receiving statuses of multiple invitees according to the schedule task when the target schedule corresponding to the schedule task is set to require reminder, determining at least one user to be reminded from the multiple invitees according to the receiving statuses of the multiple invitees, and sending reminder information corresponding to the schedule task to the at least one user to be reminded. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0074] Figure 1 Flow diagram of the office schedule reminder method provided by the present application Figure 1 ;

[0075] Figure 2 Flow diagram of the office schedule reminder method provided by the present application Figure 2 ;

[0076] Figure 3 Flow diagram of the office schedule reminder method provided by the present application Figure 3 ;

[0077] Figure 4 Structural diagram of the office schedule reminder device provided by the present application;

[0078] Figure 5 Structural diagram of the office schedule reminder equipment provided by the present application.

[0079] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and will be described in more detail hereinafter. These drawings and written descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Description of the Invention

[0080] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application. Obviously, 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 in the present application without creative efforts shall fall within the protection scope of the present application.

[0081] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that such data may be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein.

[0082] In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0083] With the continuous development and popularization of information technology, in daily work, many schedule activities such as meeting invitations, questionnaire surveys, and itinerary arrangements from different personnel will be received or sent. However, in today's era of the continuous development and popularization of information technology, it has become particularly important to simplify and timely remind work schedules.

[0084] In today's work environment, employees need to collaborate and cooperate with many people, including colleagues, customers, suppliers, partners, etc. It is necessary to timely understand and respond to each schedule activity. Existing office schedule reminder methods usually use traditional office schedule management methods such as memo records and calendar records to manage and remind office schedules.

[0085] However, the existing office schedule reminder methods have the following defects:

[0086] 1) Schedule activities such as meeting invitations, questionnaire surveys, and itinerary arrangements from different organizations, applications, systems, and personnel cannot be automatically recorded in the memo or schedule.

[0087] 2) When changing information such as meeting invitations and itinerary arrangements that have been sent out, it is time-consuming and laborious to notify each participant one by one, and it is not easy to count the receipt status of information changes when sending group messages.

[0088] 3) The method of recording schedules in a memo or calendar requires setting reminder times and reminder contents one by one, and it is impossible to uniformly configure a general reminder method and time.

[0089] 4) The method of recording schedules in a memo or calendar lacks the function of viewing everything at a glance, and it is not convenient to perform relevant statistics and report export functions for types such as itinerary and meetings.

[0090] In view of the above problems, the present application proposes an office schedule reminder method. This method synchronizes the target schedule tasks to multiple invitees in a timely manner, determines the receipt status of multiple invitees in the target schedule, and then determines the target schedule reminder time of the invitees with the receipt status of received, and sends reminder information to the at least one user to be reminded at the corresponding reminder time, improving the reminder efficiency and avoiding the defects of being unable to synchronize in time and being error-prone.

[0091] The following uses specific embodiments to detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0092] Figure 1 Flow chart of the office schedule reminder method provided for the embodiments of the application Figure 1 As Figure 1 shown, the office schedule reminder method provided in this embodiment includes:

[0093] S101. Obtain the schedule request sent by the first user, and generate a corresponding schedule task according to the schedule request. The schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user.

[0094] Among them, to obtain the schedule request sent by the first user, when receiving the schedule request sent by the first user, use an automated tool or programming to parse and process the schedule request, and generate a schedule task corresponding to the parsed and processed schedule request.

[0095] The schedule task includes user information of multiple invitees. The invitees include the first user of the schedule task, that is, the creator, and at least one second user, that is, the schedule task participant.

[0096] S102. When the target schedule corresponding to the schedule task is set to require reminder, determine the receipt status of multiple invitees according to the schedule task.

[0097] Among them, in the schedule task, when the target schedule is set by the creator to require reminder at the time of creation, the receiving status of multiple invitees is determined according to the information of the schedule task, so as to know whether all invitees have received the schedule, which is convenient for further necessary follow-up and adjustment.

[0098] S103. Determine at least one user to be reminded from multiple invitees according to the receiving status of multiple invitees, and send reminder information corresponding to the schedule task to at least one user to be reminded.

[0099] Among them, after determining the receiving status of multiple invitees according to the schedule task, at least one user to be reminded is determined from multiple invitees according to the receiving status of multiple invitees. The user to be reminded is an invitee whose receiving status is the received status. The received status indicates that the invitee has received the schedule task and is willing to participate in the schedule task on time; and send reminder information corresponding to the schedule task to at least one user to be reminded to ensure the smooth progress of the schedule task.

[0100] This embodiment proposes an office schedule reminder method. This method obtains the schedule request sent by the first user and generates a corresponding schedule task. When the target schedule needs to be reminded, the receiving status of multiple invitees is determined, and then at least one user to be reminded is determined from multiple invitees, and reminder information corresponding to the target schedule task is sent to the user to be reminded, reducing the degree of manual participation and improving the efficiency of office schedule reminder.

[0101] Figure 2 It is a flowchart of the office schedule reminder method provided by the embodiment of the present application Figure 2 . This embodiment is based on Figure 1 the embodiment, and details the office schedule reminder method. As Figure 2 shown, the office schedule reminder method provided by this embodiment includes:

[0102] S201. Obtain the schedule request sent by the first user, and generate a corresponding schedule task according to the schedule request. The schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user.

[0103] Step S201 is the same as the above step S101 and will not be elaborated here.

[0104] S202. When the target schedule corresponding to the schedule task is set to require reminder, determine whether the invitee is the first user. If so, execute step S203; if not, execute step S204.

[0105] Among them, when the target schedule corresponding to the schedule task is set to require reminder, it is determined whether the current invitee is the first user according to the invitee list of the schedule task, that is: the creator of the schedule task. If so, step S203 is executed; if not, step S204 is executed. This step is to distinguish the creator of the schedule task from other invitees in order to better coordinate the schedule arrangement.

[0106] S203. Determine that the receiving status of the first user is the received status.

[0107] Among them, for each invitee, it is necessary to first determine whether the invitee is the first user, that is, to determine whether it is the inviter. Since the schedule task is initiated by the first user (inviter), when the invitee is the first user, it is determined that the receiving status of the first user is the accepted status.

[0108] S204. Determine whether the first user exists in the invitee blacklist of the second user. If so, step S205 is executed; if not, step S206 is executed.

[0109] Among them, to determine whether the first user exists in the invitee blacklist of the second user, that is, to determine whether the second user refuses to participate in the schedule task initiated by the first user by determining whether the first user is in the invitee blacklist of the second user. If so, step S205 is executed; if not, step S206 is executed.

[0110] S205. Determine that the receiving status of the second user is the rejected status.

[0111] Among them, if the first user exists in the invitee blacklist of the second user, that is: the second user among the invitees of the schedule task blacklists the first user, that is, the creator of the schedule task, then it is directly determined that the receiving status of the second user is the rejected status.

[0112] S206. Determine whether the first user exists in the invitee whitelist of the second user. If so, step S207 is executed; if not, step S208 is executed.

[0113] Among them, to determine whether the first user exists in the invitee whitelist of the second user, that is, to determine whether the second user defaults to participate in the schedule task initiated by the first user by determining whether the first user is in the invitee whitelist of the second user. If so, step S207 is executed; if not, step S208 is executed.

[0114] S207. Determine that the receiving status of the second user is the received status.

[0115] Among them, the second user defaults to receiving schedule tasks initiated by users in the whitelist. Therefore, when the first user exists in the invitee whitelist of the second user, it is determined that the receiving status of the second user is the received status.

[0116] S208. Determine the receiving status of the second user according to the receiving identifier of the second user.

[0117] Among them, the detailed information of the second user is confirmed according to the receiving identifier of the second user, and the receiving status of the second user is confirmed according to the receiving identifier indicating whether the second user accepts or rejects.

[0118] Exemplarily, a possible implementation manner is given here. The determining the receiving status of the second user according to the receiving identifier of the second user includes:

[0119] If the receiving identifier of the second user is the first identifier, it is determined that the receiving status of the second user is the received status;

[0120] If the receiving identifier of the second user is the second identifier, it is determined that the receiving status of the second user is the rejected status.

[0121] S209. Determine at least one user to be reminded from multiple invitees according to the receiving statuses of the multiple invitees, and obtain the reminder configuration information of the at least one user to be reminded.

[0122] Among them, collect the receiving statuses of multiple invitees, and according to the receiving statuses of the multiple invitees, determine at least one user to be reminded with a received status, and obtain the configuration information of the at least one user to be reminded.

[0123] S210. Determine whether there is personalized configuration information in the reminder configuration information. If there is personalized configuration information, execute step S211; if there is no personalized configuration information, execute step S213.

[0124] Among them, according to the identifier of the user to be reminded, obtain its reminder configuration information from the reminder configuration database or service. The configuration information may include: reminder time, reminder frequency, etc.; check whether the reminder configuration information contains a personalized configuration field. If there is personalized configuration information, execute step S211; if there is no personalized configuration information, execute step S213.

[0125] In this way, personalized reminder processing can be performed on the user to be reminded, and default configurations or general strategies are used to handle reminder operations when personalized configuration information is lacking.

[0126] S211. Determine the second reminder moment according to the personalized configuration information, and update the reminder moment of the personalized reminder user corresponding to the personalized configuration information to the second reminder moment.

[0127] Among them, personalized configuration information is obtained from a reminder configuration database or service, and the reminder time for a personalized reminder to a user is updated to a second reminder time, where the personalized reminder user is any one of the at least one user to be reminded.

[0128] S212. Send a reminder message to the personalized reminder user according to the second reminder time.

[0129] S213. Send a reminder message to the users among the at least one user to be reminded except the personalized reminder user according to the first reminder time.

[0130] This embodiment proposes an office schedule reminder method. This method provides an application schedule management capability externally; users can configure a unified reminder method or a personalized reminder method according to their own needs, and configure an application list or a personnel list for automatic acceptance, manual acceptance, and automatic rejection. It realizes the automatic recording, automatic change, approaching reminder, and comprehensive view at a glance functions of the user schedule.

[0131] Figure 3 It is a flowchart of the office schedule reminder method provided by the embodiments of the present application Figure 3 . In this embodiment, when the target schedule corresponding to the schedule task has an update, both the invitees and the users to be reminded who send the reminder message will change. This embodiment supplements the description of the office schedule reminder method when the target schedule corresponding to the schedule task has an update on the basis of Embodiment 1 and Embodiment 2. As Figure 3 shown, the office schedule reminder method provided by this embodiment includes:

[0132] S301. Obtain the updated schedule task, and determine the user information of multiple invitees corresponding to the updated schedule task according to the updated schedule task.

[0133] Among them, when there is an update of the invitee for the target schedule corresponding to the schedule task, find the corresponding schedule task in the schedule management system, obtain the invitee list from the updated schedule task according to the updated schedule task, and the list contains information such as the user identifiers of multiple invitees. According to each user identifier in each invitee list, obtain the user information of the corresponding invitee from the user management system or the user database.

[0134] S302. Determine a removal group, a maintenance group, and a new addition group according to the user information of multiple updated invitees and the user information of multiple invitees before the update.

[0135] Among them, an invitee list is extracted from the user information of the invitees before and after the update. By comparing the invitee lists before and after the update, the removed users, the users remaining unchanged, and the newly added users are identified.

[0136] According to the comparison result, identify the users who are in the invitee list before the update but not in the invitee list after the update, and classify these users into the removal group.

[0137] According to the comparison result, identify the users who are in the invitee list before the update and also in the invitee list after the update, and classify these users into the maintenance group.

[0138] According to the comparison result, identify the users who are not in the invitee list before the update but are in the invitee list after the update, and classify these users into the new addition group.

[0139] S303. Modify the receiving status of at least one invitee in the removal group to the removed status.

[0140] Among them, determine the invitees whose receiving status needs to be modified to the removed status according to the removal group. For each invitee whose status needs to be modified, modify its receiving status to the removed status, and remove the invitee from the schedule task, and the invitee will no longer receive notifications of the target schedule subsequently.

[0141] S304. Synchronize the acceptance status of at least one invitee in the maintenance group.

[0142] Among them, determine the invitees who are in the invitee list both before and after the update according to the maintenance group. For these invitees, synchronize the receiving status of the invitees for the target schedule before the update, and use the receiving status of the target schedule before the update as the receiving status of the updated target schedule.

[0143] S305. Determine the corresponding receiving status according to the user information of at least one invitee in the new addition group.

[0144] Among them, determine the newly added invitees after the schedule task update according to the new addition group. For the newly added invitees, determine whether they are in the blacklist or whitelist of the first user, and determine the receiving status of the newly added invitees.

[0145] S306. Determine whether to send reminder messages to multiple updated invitees according to the receiving status of the multiple updated invitees.

[0146] Among them, an invitee list is extracted from the updated schedule tasks. According to each user identifier in the invitee list, the receiving status of the corresponding invitee is obtained from the user management system or the user database. According to the receiving status of multiple updated invitees, it is determined whether to send a reminder message to the invitee. If the receiving status is received, a reminder message is sent to the invitee; if the receiving status is rejected, no reminder message is sent to the invitee.

[0147] This embodiment proposes an office schedule reminder method. This method obtains multiple invitee information corresponding to the updated schedule tasks, compares the user information of the updated invitees with that of the invitees before the update, determines the receiving status of multiple updated invitees, and then determines whether to send a reminder message to multiple updated invitees based on the receiving status of the updated invitees. The method of this application avoids the defect of low efficiency caused by notifying participants one by one when the office schedule changes.

[0148] Figure 4 It is a schematic structural diagram of the office schedule reminder device provided by this application, as Figure 4 shown. The device 400 for automatically generating a test report provided in this embodiment includes:

[0149] An obtaining module 401, configured to obtain a schedule request sent by a first user;

[0150] A generating module 402, configured to generate a corresponding schedule task according to the schedule request. The schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user;

[0151] A determining module 403, configured to determine the receiving status of multiple invitees according to the schedule task when the target schedule corresponding to the schedule task is set to require a reminder;

[0152] The determining module 403 is further configured to determine at least one user to be reminded from the multiple invitees according to the receiving status of the multiple invitees;

[0153] A sending module 404, configured to send a reminder message corresponding to the schedule task to the at least one user to be reminded, and the user to be reminded is an invitee whose acceptance status is the received status.

[0154] Optionally, the office schedule reminder device further includes: a judging module 405;

[0155] The judging module 405 is configured to judge whether the invitee is the first user;

[0156] The determining module 403 is configured to determine that the receiving status of the first user is the received status when the invited person is the first user;

[0157] The determining module 405 is further configured to, when the invited person is the second user, determine whether the first user exists in the blacklist of invitees of the second user;

[0158] The determining module 403 is further configured to determine that the receiving status of the second user is the rejected status when the first user exists in the blacklist of invitees of the second user;

[0159] The determining module 405 is further configured to, when the first user does not exist in the blacklist of invitees of the second user, determine whether the first user exists in the whitelist of invitees of the second user;

[0160] The determining module 403 is further configured to determine that the receiving status of the second user is the received status when the first user exists in the whitelist of invitees of the second user;

[0161] The determining module 403 is further configured to determine the receiving status of the second user according to the receiving identifier of the second user when the first user does not exist in the whitelist of invitees of the second user.

[0162] Optionally, the determining module 403 is configured to determine that the receiving status of the second user is the received status when the receiving identifier of the second user is the first identifier;

[0163] The determining module 403 is further configured to determine that the receiving status of the second user is the rejected status when the receiving identifier of the second user is the second identifier.

[0164] Optionally, the obtaining module 401 is configured to obtain reminder configuration information of the at least one user to be reminded;

[0165] The determining module 405 is configured to determine whether personalized configuration information exists in the reminder configuration information according to the reminder configuration information;

[0166] The determining module 403 is configured to, when the personalized configuration information exists in the reminder configuration information, determine a second reminder time according to the personalized configuration information, and update the reminder time of the personalized reminder user corresponding to the personalized configuration information to the second reminder time;

[0167] The sending module 404 is configured to send the reminder information to the personalized reminder user according to the second reminder time;

[0168] The sending module 404 is further configured to send the reminder information to users among the at least one user to be reminded except the personalized reminder user at the first reminder time.

[0169] Optionally, the judging module 405 is configured to judge whether there is an update to the target schedule corresponding to the schedule task;

[0170] The obtaining module 401 is configured to obtain the updated schedule task when there is an update to the target schedule corresponding to the schedule task;

[0171] The determining module 403 is configured to determine user information of multiple invitees corresponding to the updated schedule task according to the updated schedule task;

[0172] The determining module 403 is further configured to determine the receiving status of multiple updated invitees according to the updated user information;

[0173] The determining module 403 is further configured to determine whether to send the reminder information to the multiple updated invitees according to the receiving status of the multiple updated invitees.

[0174] Optionally, the office schedule reminder device further includes: a processing module 406;

[0175] The determining module 403 is configured to determine a removal group, a maintenance group, and a new addition group according to the user information of the multiple updated invitees and the user information of the multiple invitees before the update;

[0176] The processing module 406 is configured to modify the receiving status of at least one invitee in the removal group to the removed status;

[0177] The processing module 406 is further configured to synchronize the acceptance status of at least one invitee in the maintenance group;

[0178] The processing module 406 is further configured to determine the corresponding receiving status according to the user information of at least one invitee in the new addition group.

[0179] Figure 5 It is a schematic structural diagram of an office schedule reminder device provided by the present application. As Figure 5 shown, the present application provides an office schedule reminder device. The office schedule reminder device 500 includes: a receiver 501, a transmitter 502, a processor 503, and a memory 504.

[0180] The receiver 501 is configured to receive instructions and data;

[0181] The transmitter 502 is configured to send instructions and data;

[0182] A memory 504 for storing computer-executable instructions;

[0183] A processor 503 for executing the computer-executable instructions stored in the memory 504 to implement each step performed by the office schedule reminder method in the above embodiments. Specifically, reference may be made to the relevant descriptions in the foregoing embodiments of the office schedule reminder method.

[0184] Optionally, the above-mentioned memory 504 may be either independent or integrated with the processor 503.

[0185] When the memory 504 is independently provided, the electronic device further includes a bus for connecting the memory 504 and the processor 503.

[0186] This application also provides a computer storage medium, in which computer-executable instructions are stored. When the processor executes the computer-executable instructions, the office schedule reminder method performed by the above-mentioned office schedule reminder device is implemented.

[0187] Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations. In the hardware implementation, the division between the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be executed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium.

[0188] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include well-known common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0189] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. An office schedule reminder method, characterized in that, The method includes: Obtaining a schedule request sent by a first user, and generating a corresponding schedule task according to the schedule request, where the schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user; When the target schedule corresponding to the schedule task is set to require a reminder, determining the receiving statuses of multiple invitees according to the schedule task; Determining at least one user to be reminded from the multiple invitees according to the receiving statuses of the multiple invitees, and sending reminder information corresponding to the schedule task to the at least one user to be reminded, where the user to be reminded is an invitee whose acceptance status is the received status.

2. The method according to claim 1, wherein The determining the receiving statuses of multiple invitees according to the schedule task includes: Judging whether the invitee is the first user; If the invitee is the first user, determining the receiving status of the first user as the received status; If the invitee is a second user, judging whether the first user exists in the invitee blacklist of the second user; If so, determining the receiving status of the second user as the rejected status; If not, judging whether the first user exists in the invitee whitelist of the second user; When the first user exists in the invitee whitelist of the second user, determining the receiving status of the second user as the received status; When the first user does not exist in the invitee whitelist of the second user, determining the receiving status of the second user according to the receiving identifier of the second user.

3. The method according to claim 2, characterized in that The determining the receiving status of the second user according to the receiving identifier of the second user includes: If the receiving identifier of the second user is the first identifier, determining the receiving status of the second user as the received status; If the receiving identifier of the second user is the second identifier, determining the receiving status of the second user as the rejected status.

4. The method according to claim 1, wherein The schedule task further includes: a first reminder time, and the sending reminder information corresponding to the schedule task to the at least one user to be reminded includes: Obtaining the reminder configuration information of the at least one user to be reminded, and judging whether there is personalized configuration information in the reminder configuration information according to the reminder configuration information; When there is personalized configuration information in the reminder configuration information, determining a second reminder time according to the personalized configuration information, and updating the reminder time of the personalized reminder user corresponding to the personalized configuration information to the second reminder time, where the personalized reminder user is any one of the at least one user to be reminded; Sending the reminder information to the personalized reminder user according to the second reminder time; Sending the reminder information to the users other than the personalized reminder user among the at least one user to be reminded according to the first reminder time.

5. The method according to claim 1, characterized in that After the sending reminder information corresponding to the schedule task to the at least one user to be reminded, the method further includes: Determine whether there is an update to the target schedule corresponding to the schedule task. If there is an update, obtain the updated schedule task, and based on the updated schedule task, determine the user information of multiple invitees corresponding to the updated schedule task; Based on the updated user information, determine the receiving status of multiple updated invitees; And based on the receiving status of the multiple updated invitees, determine whether to send the reminder information to the multiple updated invitees.

6. The method according to claim 5, characterized in that, The determining the receiving status of multiple updated invitees based on the updated user information includes: Based on the user information of the multiple updated invitees and the user information of multiple invitees before the update, determine a removal group, a maintenance group, and an addition group; Modify the receiving status of at least one invitee in the removal group to the removed status; Synchronize the acceptance status of at least one invitee in the maintenance group; Based on the user information of at least one invitee in the addition group, determine the corresponding receiving status.

7. An office schedule reminder device, characterized in that, The device includes: An obtaining module, configured to obtain a schedule request sent by a first user; A generating module, configured to generate a corresponding schedule task according to the schedule request, where the schedule task includes: user information of multiple invitees, and the invitees include the first user and at least one second user; A determining module, configured to, when the target schedule corresponding to the schedule task is set to require a reminder, determine the receiving status of multiple invitees according to the schedule task; The determining module is further configured to determine at least one user to be reminded from the multiple invitees according to the receiving status of the multiple invitees; A sending module, configured to send reminder information corresponding to the schedule task to the at least one user to be reminded, where the user to be reminded is an invitee whose acceptance status is the received status.

8. The device according to claim 7, characterized in that The device further includes: a judging module; The judging module is configured to judge whether there is an update to the target schedule corresponding to the schedule task; The determining module is configured to, when there is an update to the target schedule corresponding to the schedule task, obtain the updated schedule task, and based on the updated schedule task, determine the user information of multiple invitees corresponding to the updated schedule task; The determining module is further configured to determine the receiving status of multiple updated invitees according to the updated user information; The determining module is further configured to determine whether to send the reminder information to the multiple updated invitees according to the receiving status of the multiple updated invitees.

9. An office schedule reminder device, characterized in that, Includes: A memory; A processor; Wherein, the memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the office schedule reminder method according to any one of claims 1-6.

10. A computer storage medium, characterized in that, Computer execution instructions are stored in the computer storage medium, and when the computer execution instructions are executed by a processor, they are used to implement the office schedule reminder method according to any one of claims 1-6.

Images