Schedule management method, server and client

Abstract

The embodiment of the present application provides a schedule management method, a server and a client, the server acquires N schedule events to be completed in a target time period, N is a positive integer; when the completion deadline of the N schedule events is reached, the completion state of each schedule event in the N schedule events is checked; according to the completion state of each schedule event, M schedule events which are not completed are selected from the N schedule events, M is a positive integer less than or equal to N; the M schedule events which are not completed are sent to the client, and the client displays the M schedule events which are not completed to the user. That is, the embodiment of the present application checks the completion state of each schedule event which needs to be completed by the user in the target time period when the completion deadline of the schedule event is reached, selects the schedule event which is not completed, and reminds the user of the schedule event which is not completed, so as to urge the user to complete the schedule event which is not completed, and improve the management reliability of the schedule event.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a schedule management method, server, and client. Background Technology

[0002] With the increasing sophistication of electronic devices, many devices are equipped with schedule management systems. These systems allow users to plan and schedule events that need to be performed at a specific time or within a given timeframe. Typically, schedule management systems include functions such as displaying the time, creating, modifying, deleting, or displaying events, as well as providing reminders and sharing schedules (scheduling appointments or viewing others' schedules) after the event's appointed time.

[0003] Using a schedule management system flexibly can help cultivate self-learning ability, but currently, schedule management systems have limited functionality and cannot meet user needs. Summary of the Invention

[0004] This application provides a schedule management method, server, and client. By displaying unfinished schedule events to users, the method encourages users to complete the unfinished schedule events, thereby enriching the functionality of the schedule management system and improving the user experience.

[0005] In a first aspect, embodiments of this application provide a schedule management method applied to a server, comprising:

[0006] Obtain N scheduled events to be completed within a target time period, where N is a positive integer;

[0007] When the completion deadlines of the N schedule events arrive, check the completion status of each of the N schedule events;

[0008] Based on the completion status of each schedule event, select M incomplete schedule events from the N schedule events, where M is a positive integer less than or equal to N;

[0009] The M unfinished schedule events are sent to the client so that the client can display the M unfinished schedule events to the user.

[0010] Secondly, embodiments of this application provide a schedule management method applied to a client, the method comprising:

[0011] The server receives N schedule events, of which M are incomplete, M being a positive integer less than or equal to N. The completion status of the N schedule events is checked when their completion deadlines are reached.

[0012] Display the M unfinished schedule events to the user.

[0013] In some embodiments, the above method further includes:

[0014] Add the M unfinished schedule events to the schedule event list of the next time period after the target time period.

[0015] Thirdly, embodiments of this application provide a server, including:

[0016] The acquisition unit is used to acquire N scheduled events to be completed within a target time period, where N is a positive integer;

[0017] The first processing unit is used to check the completion status of each of the N schedule events when the completion deadline of the N schedule events arrives.

[0018] The selection unit is used to select M incomplete schedule events from the N schedule events based on the completion status of each schedule event, where M is a positive integer less than or equal to N;

[0019] The first transceiver unit is used to send the M unfinished schedule events to the client so that the client can display the M unfinished schedule events to the user.

[0020] Fourthly, embodiments of this application provide a client, including:

[0021] The second transceiver unit is used to receive M schedule events with an incomplete status out of N schedule events sent by the server, where M is a positive integer less than or equal to N, and the completion status of the N schedule events is checked when the completion deadline of the N schedule events arrives.

[0022] The display unit is used to display the M unfinished schedule events to the user.

[0023] Fifthly, embodiments of this application provide an electronic device, including a processor and a memory;

[0024] The memory is used to store computer programs;

[0025] The processor is configured to execute the computer program to implement the methods described in the first and / or second aspects above.

[0026] In a sixth aspect, embodiments of this application provide a schedule management system, including: a client and a server, wherein the server is used to implement the method described in the first aspect above, and the client implements the method described in the third aspect above.

[0027] In a seventh aspect, embodiments of this application provide a computer-readable storage medium including computer instructions that, when executed by a computer, cause the computer to perform the method as described in the first aspect and / or the second aspect.

[0028] Eighthly, embodiments of this application provide a computer program product comprising a computer program stored in a readable storage medium, wherein at least one processor of a computer can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the computer to perform the methods described in the first aspect and / or the second aspect.

[0029] Based on the technical solution provided in this application, the server obtains N scheduled events to be completed within a preset target time period, where N is a positive integer; when the completion deadline of the N scheduled events arrives, it checks the completion status of each of the N scheduled events; based on the completion status of each scheduled event, it selects M uncompleted scheduled events from the N scheduled events, where M is a positive integer less than or equal to N; and sends the M uncompleted scheduled events to the client, which then displays the M uncompleted scheduled events to the user. In other words, this embodiment of the application checks the completion status of each scheduled event that the user needs to complete within the target time period when the completion deadline arrives, selects the uncompleted scheduled events, and reminds the user of the uncompleted scheduled events, thereby urging the user to complete the uncompleted scheduled events and improving the reliability of scheduled event management. Attached Figure Description

[0030] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0031] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application;

[0032] Figure 2 This is a schematic diagram of the structure of the client device involved in an embodiment of this application;

[0033] Figure 3 A flowchart illustrating a schedule management method provided in an embodiment of this application;

[0034] Figure 4 A flowchart illustrating a schedule management method provided in an embodiment of this application;

[0035] Figure 5 A flowchart illustrating a schedule management method provided in an embodiment of this application;

[0036] Figure 6A schematic diagram of the structure of a server provided in an embodiment of this application;

[0037] Figure 7 A schematic diagram of the structure of a client provided in an embodiment of this application;

[0038] Figure 8 This is a block diagram of an electronic device involved in an embodiment of this application;

[0039] Figure 9 This is a schedule management system involved in the embodiments of this application. Detailed Implementation

[0040] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0041] It should be understood that, in the embodiments of the present invention, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0042] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0043] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0044] This solution can be applied to service platforms in areas including but not limited to social networking, e-commerce, multimedia, transportation (such as autonomous driving, mapping, vehicle networking, etc.), and healthcare.

[0045] The schedule management system described in this application can be understood as an application. The schedule management system includes a client and a server. The client can be installed on a client device and is used for data interaction with the user. The server resides on a backend server and is used for data interaction with the client.

[0046] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application, such as... Figure 1 As shown, it includes a client device and a server, wherein the client device has a client of the schedule management system installed, and the server of the schedule management system is located on the server.

[0047] The client devices involved in the embodiments of this application may include various handheld devices, vehicle-mounted devices, wireless headsets, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of user equipment (UE), mobile station (MS), terminal device, etc. The client devices may be, for example, smartphones, tablets, headphone boxes, smart desk lamps, etc.

[0048] In some embodiments, such as Figure 2 As shown, the client device also includes a control circuit and an input-output circuit, with the input-output circuit connected to the control circuit.

[0049] The control circuit may include storage and processing circuitry. The storage circuitry within this circuitry may be a memory, such as a hard disk drive, non-volatile memory (e.g., flash memory or other electronically programmable read-only memory used to form a solid-state drive), or volatile memory (e.g., static or dynamic random access memory), etc., without limitation in the embodiments of this application. The processing circuitry within the storage and processing circuitry can be used to control the operation of the client device. This processing circuitry may be implemented based on one or more microprocessors, microcontrollers, digital signal processors, baseband processors, power management units, audio codec chips, application-specific integrated circuits (ASICs), display driver integrated circuits, etc.

[0050] The storage and processing circuitry can be used to run software in the client device, such as applications for playing incoming call alerts, playing text message alerts, playing alarm clock alerts, playing media files, making voice calls (VoIP), and operating system functions. This software can be used to perform control operations, such as playing incoming call alerts, playing text message alerts, playing alarm clock alerts, playing media files, making voice calls, and other functions in the client device; this application's embodiments do not impose limitations on these functions.

[0051] The input-output circuit can be used to enable the client device to input and output data, that is, to allow the client device to receive data from external devices and to allow the client device to output data from the client device to external devices.

[0052] The input-output circuitry may further include sensors. Sensors may include ambient light sensors, light- and capacitance-based infrared proximity sensors, ultrasonic sensors, touch sensors (e.g., light-based touch sensors and / or capacitive touch sensors, where the touch sensor may be part of a touchscreen display or used independently as a touch sensor structure), accelerometers, gravity sensors, and other sensors. The input-output circuitry may also further include audio components that can provide audio input and output functionality to client devices. The audio components may also include tone generators and other components for generating and detecting sound.

[0053] The input-output circuit may also include one or more displays. The displays may include one or more of the following: liquid crystal displays, organic light-emitting diode displays, electronic ink displays, plasma displays, and displays using other display technologies. The displays may include a touch sensor array (i.e., the displays may be touch-sensitive displays). The touch sensors may be capacitive touch sensors formed by an array of transparent touch sensor electrodes (e.g., indium tin oxide (ITO) electrodes), or they may be touch sensors formed using other touch technologies, such as acoustic touch, pressure-sensitive touch, resistive touch, optical touch, etc., and this application does not impose limitations.

[0054] The input-output circuitry may further include communication circuitry that can provide the client device with the ability to communicate with external devices. The communication circuitry may include analog and digital input-output interface circuitry, and wireless communication circuitry based on radio frequency signals and / or optical signals. The wireless communication circuitry within the communication circuitry may include radio frequency transceiver circuitry, power amplifier circuitry, low-noise amplifiers, switches, filters, and antennas. For example, the wireless communication circuitry within the communication circuitry may include circuitry for supporting near-field communication (NFC) by transmitting and receiving near-field coupled electromagnetic signals. For instance, the communication circuitry may include a near-field communication antenna and a near-field communication transceiver. The communication circuitry may also include cellular telephone transceivers and antennas, wireless LAN transceiver circuitry and antennas, etc.

[0055] The input-output circuit may further include other input-output units. These units may include buttons, joysticks, click wheels, scroll wheels, touchpads, keypads, keyboards, cameras, LEDs, and other status indicators.

[0056] The client device may further include a battery (not shown) for providing power to the client device.

[0057] Current schedule management systems have limited functionality, such as reminding users to complete scheduled events when their appointed time arrives. However, they lack the ability to track and remind users of incomplete events, thus failing to meet user needs.

[0058] To address the aforementioned technical issues, this application embodiment checks the completion status of each scheduled event that the user needs to complete within the target time period when the deadline for completing a scheduled event arrives, selects incomplete scheduled events, and reminds the user of the incomplete scheduled events, thereby urging the user to complete the incomplete scheduled events and improving the reliability of scheduled event management.

[0059] The technical solutions of the embodiments of this application will be described in detail below through some examples. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0060] Figure 3 A flowchart illustrating a schedule management method provided in an embodiment of this application is shown below. Figure 3 As shown, it includes:

[0061] S301. The server obtains N scheduled events that are scheduled to be completed within the target time period.

[0062] Where N is a positive integer.

[0063] The target time period can be any time period set by the user, such as half a day, one day, two days, or one week. This application embodiment does not limit the specific length of the target time period.

[0064] Scheduled events are tasks that users set to be completed within a target time period.

[0065] Schedule events are created by users in the schedule management system. For example, a user can create N schedule events that need to be completed on the same day in the schedule management system.

[0066] For example, the process of a user creating a schedule event in the schedule management system is as follows: the user opens the schedule management system client on the client device, enters the key information of the schedule event to be created on the schedule creation interface of the client, the client sends the key information of the schedule event to the server, the server saves the key information of the schedule event, and returns a message to the client that the schedule event has been created successfully.

[0067] Key information for a schedule event includes time, location, and event (or task or business).

[0068] Optionally, the time of the aforementioned scheduled event may include the start and end times of the scheduled event. Optionally, it may also include the expiration period of the scheduled event, etc.

[0069] Optional items can include work, meetings, business trips, medical checkups, etc.

[0070] As can be seen from the above, the server stores key information for each created schedule event. Therefore, the server can obtain the preset N schedule events to be completed within the target time period based on the time in the key information of the schedule events.

[0071] It should be noted that the embodiments of this application do not limit the specific time for obtaining the N schedule events to be completed within the target time period; for example, it can be any time within the target time period. For instance, taking a target time period of one day, the N schedule events to be completed that day can be obtained at the last time of the day.

[0072] S302. When the completion deadline of N schedule events arrives, the server checks the completion status of each of the N schedule events.

[0073] In one example, the completion deadline for the above N schedule events can be the end time of the last schedule event among the N schedule events.

[0074] In another example, the completion deadline for the above N schedule events is any time between the end time of the last schedule event among the N schedule events and the last moment of the target time period. For example, if the target time period is one day and the end time of the last schedule event among the above N schedule events is 10 PM, then any time between 10 PM and midnight can be used as the completion deadline for the N schedule events.

[0075] In another example, the deadline for completing the above N schedule events is the last moment of the target time period.

[0076] In this embodiment, the completion status of a schedule event includes, but is not limited to: completed, incomplete, and expired.

[0077] Optionally, users are not allowed to complete expired schedule events.

[0078] In this application embodiment, the server obtains the completion status of schedule events in the following ways, including but not limited to:

[0079] In Method 1, when a user completes a scheduled event, they click on the corresponding completion option in the client. After detecting the user's click, the client sends the scheduled event completion information to the server. This information includes the identifier of the completed scheduled event. Based on this information, the server marks the scheduled event as completed.

[0080] Method 2: When the client device detects that the user has completed the scheduled event, such as when the user watches a learning video on the client device, the client device sends the scheduled event completion information to the server after the user finishes watching the learning video. The scheduled event completion information includes the identification information of the completed scheduled event. Based on the scheduled event completion information, the server marks the completion status of the scheduled event as completed.

[0081] Based on this, when the completion deadline of N schedule events arrives, the server checks the completion status of each of the N schedule events.

[0082] In some embodiments, for each of the N schedule events, if the server detects that the schedule event is completed within the target time period, then the completion status of the schedule event is determined to be completed; or,

[0083] If the server detects that a scheduled event is not completed within the target event segment and the event's expiration date has not yet arrived, then the server determines the event's completion status as incomplete; or...

[0084] If the server detects that a scheduled event has not been completed within the target event segment and the event's expiration date has been reached, then the server determines that the event's completion status is expired.

[0085] In some embodiments, the server further includes generating an instance for each of the N schedule events and recording the completion status of the schedule event in the instance information corresponding to the schedule event.

[0086] Based on this, the above S302 includes the following steps S302-A1 and S302-A2:

[0087] S302-A1: When the completion deadline of N schedule events arrives, scan the instance information corresponding to each of the N schedule events;

[0088] S302-A2. Determine the completion status of each schedule event based on the instance information corresponding to each schedule event.

[0089] It should be noted that for recurring schedule events, the server generates an instance of the schedule event each time it is executed. For example, for an event that repeats every day for a month, the server will generate an instance of the event each time it is executed, such as generating an instance of the event every day, and recording the completion status of the event each day in the instance information corresponding to the event.

[0090] S303. Based on the completion status of each schedule event, the server selects M incomplete schedule events from N schedule events.

[0091] Where M is a positive integer less than or equal to N.

[0092] Based on the above steps, the server obtains the completion status of each of the N schedule events. Then, based on the completion status of each schedule event, it selects the M incomplete schedule events from the N schedule events.

[0093] In one example, the server identifies M incomplete schedule events out of N schedule events that are incomplete.

[0094] S304. The server sends the M unfinished schedule events to the client.

[0095] S305. The client displays M unfinished schedule events to the user.

[0096] In some embodiments, if the target task associated with an unfinished schedule event is a network resource, to facilitate the user's completion of the unfinished schedule event, the client can display a link to the target task associated with the unfinished schedule event in addition to showing the user the unfinished schedule event. The user can click the link to jump to the interface containing the target task, thereby facilitating the completion of the unfinished schedule event. In other words, this application embodiment also provides users with an "eliminate procrastination" entry point, further improving the reliability of schedule management and enhancing the user experience.

[0097] In some embodiments, to facilitate users in completing unfinished schedule events in a timely manner, the client of this application embodiment can also add the M unfinished schedule events within the target time period to the schedule event list of the next time period. For example, unfinished schedule events from the previous day can be added to the schedule event list of the next day, making it easier for users to complete the unfinished schedule events of the previous day on the second day. Optionally, the M unfinished schedule events can be pinned to the top of the schedule event list of the next time period to remind users to prioritize completing the unfinished schedule events from the previous period, effectively helping users eliminate backlogged schedules.

[0098] In some embodiments, to facilitate users in understanding the completion status of scheduled events within a target time period, the embodiments of this application further include: the server counting the number of scheduled events in different completion states among the N scheduled events based on the completion status of each scheduled event; and sending the counted number of scheduled events in different completion states among the N scheduled events to the client and / or terminal device for display by the client and / or terminal device.

[0099] For example, based on the completion status of each of the N schedule events, the server counts the number of completed, incomplete, and expired schedule events, and sends these counts to the client for display to the user. Alternatively, the server may send these counts to an associated terminal device, such as the user's mobile phone, allowing the user to stay informed about the schedule's progress.

[0100] In some embodiments, this application further includes: when the client detects that a user has triggered a voice playback option for a target schedule event, it plays key information about the target schedule event to the user via voice. This reduces the cognitive burden and ease of use for the user.

[0101] The schedule management method provided in this application involves a server acquiring N scheduled events to be completed within a preset target time period, where N is a positive integer. When the deadline for each of the N scheduled events arrives, the server checks the completion status of each of the N scheduled events. Based on the completion status of each scheduled event, the server selects M incomplete scheduled events from the N scheduled events, where M is a positive integer less than or equal to N. The server then sends the M incomplete scheduled events to the client, which displays them to the user. In other words, this application improves the reliability of schedule management by checking the completion status of each scheduled event that the user needs to complete within the target time period when the deadline arrives, selecting incomplete scheduled events, and reminding the user of the incomplete events.

[0102] In some embodiments, the schedule events created in this application include jump links to target tasks, as described below. Figure 4 The process of creating schedule events involved in the embodiments of this application is described.

[0103] Figure 4 A flowchart illustrating a schedule management method provided in an embodiment of this application is shown below. Figure 4 As shown, the embodiments of this application include:

[0104] S401. The client receives a first schedule creation request sent by the user, which includes a jump link to the target task associated with the first schedule event.

[0105] Optionally, the first schedule creation request may also include other key information about the first schedule event, such as time, location, target task name, etc.

[0106] Optionally, the target task can be understood as the matters mentioned above.

[0107] S402, The client sends the first schedule creation request to the server.

[0108] S403. The server creates a first schedule event based on the first schedule creation request. The key information of the first schedule event includes the jump link of the target task.

[0109] Optionally, key information for this first schedule event may also include time, location, and target task name.

[0110] Optionally, the server may save key information about the first scheduled event.

[0111] S404. The server sends key information about the first scheduled event to the client.

[0112] S405. The client displays the redirect link for the target task.

[0113] Among them, the jump link is used to jump to the interface where the target task is located when the user triggers the jump link.

[0114] In this embodiment of the application, in order to facilitate users in executing target tasks associated with schedule events, a jump link for the target task is added to the key information of the target event. In this way, users can jump to the interface where the target task is located simply by clicking the jump link, which makes it convenient for users to complete the target task, further enriches the functions of the schedule management system, improves the management reliability of the schedule management system, and enhances the user experience.

[0115] In current technology, after a schedule management system creates a schedule event related to a business system, it sends the event's identifier information to the business system, which then saves this identifier. Later, when the business system needs to delete and / or modify the schedule event, it sends a deletion and / or modification request to the schedule management system's server. However, in this technology, the schedule management system needs to send the event's identifier information to the business system so that it can delete and / or modify the target event based on this identifier. As can be seen, current technology increases the workload of the schedule management system by requiring it to send the event's identifier information to the business system. Furthermore, the business system needs to allocate separate storage space to store the event's identifier information, increasing its storage burden.

[0116] To address the aforementioned technical problems, in some embodiments, the schedule events created in this application include a business type and a business identifier, which are described below in conjunction with... Figure 5 The process of creating schedule events involved in the embodiments of this application is described.

[0117] Figure 5 A flowchart illustrating a schedule management method provided in an embodiment of this application is shown below. Figure 5 As shown, the embodiments of this application include:

[0118] S501, The client receives a second schedule creation request sent by the user. The second schedule creation request includes the business type and business identifier associated with the second schedule event.

[0119] In some embodiments, a service can be understood as a task or matter that a user needs to complete.

[0120] The business identifier can be a business ID.

[0121] S502, The client sends the second schedule creation request to the server.

[0122] S503. The server creates a second schedule event based on the second schedule creation request. The key information of the second schedule event includes the business type and business identifier associated with the second schedule event.

[0123] S504, The server sends the key information of the second schedule event to the client.

[0124] S505: The client displays the business type and business identifier associated with the second schedule event.

[0125] In other words, the second schedule event in this application embodiment includes not only the time and the name of the task to be executed, but also the business type and business identifier, thereby enriching the display content of the second schedule event and making it easier for users to grasp more detailed information about the second schedule event in order to determine its urgency, etc.

[0126] In some embodiments, this application further includes operations for modifying and / or deleting created schedule events, as shown in S506 and S507 below:

[0127] S506. The server receives a schedule operation request sent by the business system. The schedule operation request includes the business type and business identifier associated with the second schedule event.

[0128] S507. The server queries the second schedule event based on the business type and business identifier associated with the second schedule event.

[0129] In some embodiments, when a service type and a service identifier are associated with multiple schedule events, the above S507 includes S507-A:

[0130] S507-A: If multiple schedule events matching the business type and business identifier are found based on the business type and business identifier associated with the second schedule event, the schedule event with the earliest creation time among the multiple schedule events shall be determined as the second schedule event.

[0131] S508: The server performs the target operation on the second schedule event based on the schedule operation request.

[0132] In some embodiments, a schedule operation request includes a schedule deletion request or a schedule modification request. If the schedule operation request is a schedule deletion request, the target operation is a deletion operation. If the schedule operation request is a schedule modification request, the target operation is a modification operation.

[0133] In this embodiment, when creating a schedule event, the schedule management system includes a business type and a business identifier in the key information of the event. When a business system needs to delete or modify the schedule event, it only needs to send the business type and business identifier to the schedule management system. The schedule management system then determines the schedule event to be deleted or modified based on the business type and business identifier, and modifies or deletes the event accordingly. As can be seen from the above, in this embodiment, the schedule management system does not need to send the schedule event's identifier information to the business system, thus reducing the workload of the schedule management system. Furthermore, the business system does not need to allocate separate storage space to store the schedule event's identifier information, thereby reducing the storage burden on the business system.

[0134] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application.

[0135] It should also be understood that, in the various method embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0136] The above text combined Figures 3 to 5 The method embodiments of this application are described in detail below, in conjunction with... Figures 6 to 8 The following describes in detail the device embodiments of this application.

[0137] Figure 6 This is a schematic diagram of a server structure provided in an embodiment of this application.

[0138] like Figure 6 As shown, server 30 includes:

[0139] The acquisition unit 31 is used to acquire N scheduled events to be completed within a target time period, where N is a positive integer;

[0140] The first processing unit 32 is used to check the completion status of each of the N schedule events when the completion deadline of the N schedule events arrives.

[0141] Selection unit 33 is used to select M incomplete schedule events from the N schedule events according to the completion status of each schedule event, where M is a positive integer less than or equal to N;

[0142] The first transceiver unit 34 is used to send the M unfinished schedule events to the client so that the client can display the M unfinished schedule events to the user.

[0143] In some embodiments, the first processing unit 32 is further configured to count the number of schedule events in different completion states among the N schedule events based on the completion status of each schedule event;

[0144] The first transceiver unit 34 is further configured to send the number of schedule events in different completion states among the N schedule events to the client and / or terminal device so that the client and / or terminal device can display it.

[0145] In some embodiments, the first processing unit 32 is specifically configured to determine the completion status of the schedule event as completed if it is detected that the schedule event is completed within the target time period; or,

[0146] If it is found that the scheduled event has not been completed within the target event segment, and the validity period of the scheduled event has not expired, then the completion status of the scheduled event is determined to be incomplete; or,

[0147] If it is found that the scheduled event has not been completed within the target event segment, and the validity period of the scheduled event has expired, then the completion status of the scheduled event is determined to be expired.

[0148] In some embodiments, the selection unit 33 is specifically used to determine the schedule events with an incomplete status among the N schedule events as the M incomplete schedule events.

[0149] In some embodiments, the first processing unit 32 is further configured to generate an instance for each of the N schedule events; record the completion status of the schedule event in the instance information corresponding to the schedule event; scan the instance information corresponding to each of the N schedule events when the completion deadline of the N schedule events arrives; and determine the completion status of each schedule event based on the instance information corresponding to each schedule event.

[0150] In some embodiments, the first transceiver unit 34 is further configured to receive a first schedule creation request sent by the client, the first schedule creation request including a jump link to a target task associated with a first schedule event;

[0151] The first processing unit 32 is further configured to create a first schedule event according to the first schedule creation request, wherein the key information of the first schedule event includes the jump link of the target task;

[0152] The first transceiver unit 34 is also used to send key information of the first schedule event to the client so that the client displays a jump link for the target task, the jump link being used to jump to the interface where the target task is located when the user triggers the jump link.

[0153] In some embodiments, the first transceiver unit 34 is further configured to receive a second schedule creation request sent by the client, the second schedule creation request including the service type and service identifier associated with the second schedule event;

[0154] The first processing unit 32 is further configured to create the second schedule event according to the second schedule creation request, wherein the key information of the second schedule event includes the business type and business identifier associated with the second schedule event;

[0155] The first transceiver unit 34 is also configured to send key information of the second schedule event to the client so that the client can display the business type and business identifier associated with the second schedule event.

[0156] In some embodiments, the first processing unit 32 is further configured to receive a schedule operation request sent by the business system, the schedule operation request including the business type and business identifier associated with the second schedule event;

[0157] The first processing unit 32 is further configured to query the second schedule event based on the business type and business identifier associated with the second schedule event; and to perform a target operation on the second schedule event based on the schedule operation request.

[0158] In some embodiments, the first processing unit 32 is further configured to determine the schedule event with the earliest creation time among the multiple schedule events as the second schedule event if multiple schedule events matching the business type and business identifier are found based on the business type and business identifier associated with the second schedule event.

[0159] In some embodiments, the schedule operation request includes a schedule deletion request or a schedule modification request. If the schedule operation request is a schedule deletion request, the target operation is a deletion operation; if the schedule operation request is a schedule modification request, the target operation is a modification operation.

[0160] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be found in the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 6 The server shown can correspond to the corresponding subject in the method of the embodiments of this application, and the foregoing and other operations and / or functions of each module in the server are respectively to implement the corresponding processes in the above methods. For the sake of brevity, they will not be described in detail here.

[0161] Figure 7 This is a schematic diagram of a client architecture provided in an embodiment of this application. Figure 7 As shown, client 40 includes:

[0162] The second transceiver unit 41 is used to receive M schedule events with an incomplete status out of N schedule events sent by the server, where M is a positive integer less than or equal to N, and the completion status of the N schedule events is checked when the completion deadline of the N schedule events arrives.

[0163] Display unit 42 is used to display the M unfinished schedule events to the user.

[0164] In some embodiments, the transceiver unit 41 is further configured to receive the number of schedule events in different completion states among N schedule events sent by the server, wherein the number of schedule events in different completion states among the N schedule events is obtained by statistically analyzing the completion state of each schedule event among the N schedule events.

[0165] The display unit 42 is also used to display the number of schedule events in different completion states among the N schedule events.

[0166] In some embodiments, the second transceiver unit 41 is further configured to receive a first schedule creation request sent by a user, the first schedule creation request including a jump link to a target task associated with a first schedule event; send the first schedule creation request to the server; and receive key information of the first schedule event sent by the server, the first schedule event being created by the server according to the first schedule creation request, the key information of the first schedule event including the jump link to the target task.

[0167] The display unit 42 is also used to display a jump link for the target task to the user, wherein the jump link is used to jump to the interface where the target task is located when the user triggers the jump link.

[0168] In some embodiments, the second transceiver unit 41 is further configured to receive a second schedule creation request sent by the user, the second schedule creation request including a service type and service identifier associated with a second schedule event; send the second schedule creation request to the server; and receive key information of the second schedule event sent by the server, the second schedule event being created by the server according to the second schedule creation request, the key information of the second schedule event including a service type and service identifier associated with the second schedule event.

[0169] The display unit 42 is also used to display to the user the business type and business identifier associated with the second schedule event.

[0170] In some embodiments, the client 40 further includes a second processing unit 43, configured to play key information of the target schedule event to the user via voice when the user triggers a voice playback option for the target schedule event.

[0171] In some embodiments, the second processing unit 43 is further configured to add the M unfinished schedule events to the schedule event list of the next time period of the target time period.

[0172] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be found in the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 7 The client shown can correspond to the corresponding subject in the method of the embodiment of this application, and the foregoing and other operations and / or functions of each module in the client 40 are respectively to implement the corresponding processes in the above methods. For the sake of brevity, they will not be described in detail here.

[0173] The apparatus of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by the hardware processor, or executed by a combination of hardware and software modules in the processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0174] Figure 8 This is a block diagram of an electronic device involved in an embodiment of this application. The device may be a server or a client device.

[0175] Figure 8 The illustrated electronic device 50 includes a memory 51, a processor 52, and a communication interface 53. The memory 51, processor 52, and communication interface 53 are communicatively connected to each other. For example, the memory 51, processor 52, and communication interface 53 can be connected via a network. Alternatively, the electronic device 50 may also include a bus 54. The memory 51, processor 52, and communication interface 53 are communicatively connected to each other via the bus 54. Figure 8 It is an electronic device 50 in which the memory 51, processor 52, and communication interface 53 are connected to each other via bus 54.

[0176] The memory 51 can be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 51 can store programs, and when the program stored in the memory 51 is executed by the processor 52, the processor 52 and the communication interface 53 are used to execute the above methods.

[0177] The processor 52 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), or one or more integrated circuits.

[0178] Processor 52 can also be an integrated circuit chip with signal processing capabilities. In implementation, the method of this application can be completed through integrated logic circuits in the hardware of processor 52 or through software instructions. The processor 52 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. The software module can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 51, and processor 52 reads information from memory 51 and, in conjunction with its hardware, completes the method of this application embodiment.

[0179] Communication interface 53 uses transceiver modules, such as, but not limited to, transceivers, to enable communication between electronic device 50 and other devices or communication networks. For example, data sets can be acquired through communication interface 53.

[0180] When the aforementioned electronic device 50 includes a bus 54, the bus 54 may include a path for transmitting information between various components of the electronic device 50 (e.g., memory 51, processor 52, communication interface 53).

[0181] According to this application, a computer storage medium is also provided, on which a computer program is stored, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0182] Figure 9 The schedule management system involved in the embodiments of this application, such as Figure 9 As shown, the schedule management system 60 includes Figure 6 The server 61 shown and Figure 7 The client shown is 62.

[0183] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method described in the above-described method embodiments.

[0184] In other words, when implemented using software, it can be implemented wholly or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0185] According to one or more embodiments of this disclosure, a schedule management method is provided, applied to a server, comprising: acquiring N scheduled events to be completed within a preset target time period, wherein N is a positive integer; when the completion deadline of the N scheduled events arrives, checking the completion status of each of the N scheduled events; selecting M uncompleted scheduled events from the N scheduled events based on the completion status of each scheduled event, wherein M is a positive integer less than or equal to N; and sending the M uncompleted scheduled events to a client so that the client displays the M uncompleted scheduled events to a user.

[0186] According to one or more embodiments of this disclosure, the method further includes: counting the number of schedule events in different completion states among the N schedule events based on the completion status of each schedule event; and sending the counted number of schedule events in different completion states among the N schedule events to a client and / or a terminal device so that the client and / or the terminal device can display it.

[0187] According to one or more embodiments of this disclosure, checking the completion status of each of the N schedule events includes: if the schedule event is found to be completed within the target time period, then determining the completion status of the schedule event as completed; or, if the schedule event is found to be not completed within the target event period and the validity period of the schedule event has not been reached, then determining the completion status of the schedule event as incomplete; or, if the schedule event is found to be not completed within the target event period and the validity period of the schedule event has been reached, then determining the completion status of the schedule event as expired.

[0188] According to one or more embodiments of this disclosure, selecting M incomplete schedule events from the N schedule events based on the completion status of each schedule event includes: determining the schedule events with an incomplete completion status among the N schedule events as the M incomplete schedule events.

[0189] According to one or more embodiments of this disclosure, the method further includes: generating an instance for each of the N schedule events; recording the completion status of the schedule event in the instance information corresponding to the schedule event; the step of checking the completion status of each of the N schedule events when the completion deadline of the N schedule events arrives includes: scanning the instance information corresponding to each of the N schedule events when the completion deadline of the N schedule events arrives; and determining the completion status of each schedule event based on the instance information corresponding to each schedule event.

[0190] According to one or more embodiments of this disclosure, the method further includes: receiving a first schedule creation request sent by the client, the first schedule creation request including a jump link to a target task associated with a first schedule event; creating a first schedule event according to the first schedule creation request, the key information of the first schedule event including the jump link to the target task; sending the key information of the first schedule event to the client so that the client displays the jump link to the target task, the jump link being used to jump to the interface where the target task is located when the user triggers the jump link.

[0191] According to one or more embodiments of this disclosure, the method further includes: receiving a second schedule creation request sent by the client, the second schedule creation request including a business type and business identifier associated with a second schedule event; creating a second schedule event according to the second schedule creation request, the key information of the second schedule event including the business type and business identifier associated with the second schedule event; and sending the key information of the second schedule event to the client so that the client displays the business type and business identifier associated with the second schedule event.

[0192] According to one or more embodiments of this disclosure, the method further includes: receiving a schedule operation request sent by a business system, the schedule operation request including a business type and a business identifier associated with the second schedule event; querying the second schedule event according to the business type and the business identifier associated with the second schedule event; and performing a target operation on the second schedule event according to the schedule operation request.

[0193] According to one or more embodiments of this disclosure, querying the second schedule event based on the business type and business identifier associated with the second schedule event includes: if multiple schedule events matching the business type and business identifier are found based on the business type and business identifier associated with the second schedule event, the schedule event with the earliest creation time among the multiple schedule events is determined as the second schedule event.

[0194] According to one or more embodiments of this disclosure, the schedule operation request includes a schedule deletion request or a schedule modification request. If the schedule operation request is a schedule deletion request, the target operation is a deletion operation; if the schedule operation request is a schedule modification request, the target operation is a modification operation.

[0195] According to one or more embodiments of this disclosure, a schedule management method is provided, applied to a client, comprising: receiving M schedule events out of N schedule events sent by a server, wherein the completion status is incomplete, M is a positive integer less than or equal to N, and the completion status of the N schedule events is checked when the completion deadline of the N schedule events arrives; and displaying the M incomplete schedule events to the user.

[0196] According to one or more embodiments of this disclosure, the method further includes: receiving the number of schedule events in different completion states among N schedule events sent by the server, wherein the number of schedule events in different completion states among the N schedule events is obtained by statistical analysis based on the completion state of each schedule event among the N schedule events; and displaying the number of schedule events in different completion states among the N schedule events.

[0197] According to one or more embodiments of this disclosure, the method further includes: receiving a first schedule creation request sent by a user, the first schedule creation request including a jump link to a target task associated with a first schedule event; sending the first schedule creation request to the server; receiving key information of the first schedule event sent by the server, the first schedule event being created by the server according to the first schedule creation request, the key information of the first schedule event including the jump link to the target task; and displaying the jump link to the user, the jump link being used to jump to the interface where the target task is located when the user triggers the jump link.

[0198] According to one or more embodiments of this disclosure, the method further includes: receiving a second schedule creation request sent by the user, the second schedule creation request including a business type and business identifier associated with a second schedule event; sending the second schedule creation request to the server; receiving key information of the second schedule event sent by the server, the second schedule event being created by the server according to the second schedule creation request, the key information of the second schedule event including a business type and business identifier associated with the second schedule event; and displaying the business type and business identifier associated with the second schedule event to the user.

[0199] According to one or more embodiments of this disclosure, the method further includes: when a voice playback option for a target schedule event triggered by the user is detected, playing key information of the target schedule event to the user via voice.

[0200] According to one or more embodiments of this disclosure, the method further includes: adding the M unfinished schedule events to the schedule event list of the next time period of the target time period.

[0201] According to one or more embodiments of this disclosure, a server is provided, comprising: an acquisition unit, configured to acquire N scheduled events to be completed within a preset target time period, wherein N is a positive integer; a first processing unit, configured to check the completion status of each of the N scheduled events when the completion deadline of the N scheduled events arrives; a selection unit, configured to select M uncompleted scheduled events from the N scheduled events according to the completion status of each scheduled event, wherein M is a positive integer less than or equal to N; and a first transceiver unit, configured to send the M uncompleted scheduled events to a client, so that the client displays the M uncompleted scheduled events to a user.

[0202] According to one or more embodiments of this disclosure, the first processing unit is further configured to count the number of schedule events in different completion states among the N schedule events based on the completion status of each schedule event; the first transceiver unit is further configured to send the counted number of schedule events in different completion states among the N schedule events to a client and / or a terminal device, so that the client and / or the terminal device can display it.

[0203] According to one or more embodiments of this disclosure, a first processing unit is specifically configured to: if it is detected that the scheduled event is completed within the target time period, determine that the completion status of the scheduled event is "completed"; or, if it is detected that the scheduled event is not completed within the target event period and the validity period of the scheduled event has not been reached, determine that the completion status of the scheduled event is "incomplete"; or, if it is detected that the scheduled event is not completed within the target event period and the validity period of the scheduled event has been reached, determine that the completion status of the scheduled event is "expired".

[0204] According to one or more embodiments of this disclosure, the selection unit is specifically used to determine the schedule events with an incomplete completion status among the N schedule events as the M incomplete schedule events.

[0205] According to one or more embodiments of this disclosure, the first processing unit is further configured to generate an instance for each of the N schedule events; record the completion status of the schedule event in the instance information corresponding to the schedule event; scan the instance information corresponding to each of the N schedule events when the completion deadline of the N schedule events arrives; and determine the completion status of each schedule event based on the instance information corresponding to each schedule event.

[0206] According to one or more embodiments of this disclosure, the first transceiver unit is further configured to receive a first schedule creation request sent by the client, the first schedule creation request including a jump link to a target task associated with a first schedule event; the first processing unit is further configured to create a first schedule event according to the first schedule creation request, the key information of the first schedule event including the jump link to the target task; the first transceiver unit is further configured to send the key information of the first schedule event to the client, so that the client displays the jump link to the target task, the jump link being used to jump to the interface where the target task is located when the user triggers the jump link.

[0207] According to one or more embodiments of this disclosure, the first transceiver unit is further configured to receive a second schedule creation request sent by the client, the second schedule creation request including a service type and service identifier associated with the second schedule event; the first processing unit is further configured to create the second schedule event according to the second schedule creation request, the key information of the second schedule event including the service type and service identifier associated with the second schedule event; the first transceiver unit is further configured to send the key information of the second schedule event to the client, so that the client displays the service type and service identifier associated with the second schedule event.

[0208] According to one or more embodiments of this disclosure, the first processing unit is further configured to receive a schedule operation request sent by a business system, the schedule operation request including a business type and a business identifier associated with the second schedule event; the first processing unit is further configured to query the second schedule event according to the business type and the business identifier associated with the second schedule event; and perform a target operation on the second schedule event according to the schedule operation request.

[0209] According to one or more embodiments of this disclosure, the first processing unit is further configured to determine the schedule event with the earliest creation time among the multiple schedule events as the second schedule event when multiple schedule events matching the business type and business identifier are found based on the business type and business identifier associated with the second schedule event.

[0210] According to one or more embodiments of this disclosure, the schedule operation request includes a schedule deletion request or a schedule modification request. If the schedule operation request is a schedule deletion request, the target operation is a deletion operation; if the schedule operation request is a schedule modification request, the target operation is a modification operation.

[0211] According to one or more embodiments of this disclosure, a client is provided, comprising: a second transceiver unit, configured to receive M schedule events with an incomplete status out of N schedule events sent by a server, wherein M is a positive integer less than or equal to N, and the completion status of the N schedule events is checked when the completion deadline of the N schedule events arrives; and a display unit, configured to display the M incomplete schedule events to a user.

[0212] According to one or more embodiments of this disclosure, the second transceiver unit is further configured to receive the number of schedule events in different completion states among N schedule events sent by the server, wherein the number of schedule events in different completion states among the N schedule events is obtained by statistical analysis based on the completion state of each schedule event among the N schedule events; the display unit is further configured to display the number of schedule events in different completion states among the N schedule events.

[0213] According to one or more embodiments of this disclosure, the second transceiver unit is further configured to receive a first schedule creation request sent by a user, the first schedule creation request including a jump link to a target task associated with a first schedule event; send the first schedule creation request to the server; receive key information of the first schedule event sent by the server, the first schedule event being created by the server according to the first schedule creation request, the key information of the first schedule event including the jump link to the target task; and the display unit is further configured to display the jump link to the user, the jump link being used to jump to the interface where the target task is located when the user triggers the jump link.

[0214] According to one or more embodiments of this disclosure, the second transceiver unit is further configured to receive a second schedule creation request sent by the user, the second schedule creation request including a service type and service identifier associated with the second schedule event; send the second schedule creation request to the server; receive key information of the second schedule event sent by the server, the second schedule event being created by the server according to the second schedule creation request, the key information of the second schedule event including a service type and service identifier associated with the second schedule event; and the display unit is further configured to display the service type and service identifier associated with the second schedule event to the user.

[0215] According to one or more embodiments of this disclosure, the client further includes: a second processing unit, configured to play key information of the target schedule event to the user via voice when a voice playback option for the user triggering the target schedule event is detected.

[0216] According to one or more embodiments of this disclosure, the second processing unit is further configured to add the M unfinished schedule events to the schedule event list of the next time period of the target time period.

[0217] According to one or more embodiments of this disclosure, a schedule management system is provided, including a client and a server, the server and client being used to implement the above-described method.

[0218] According to one or more embodiments of this disclosure, an electronic device is provided, comprising: a processor and a memory; the memory for storing a computer program; and the processor for implementing the method described above.

[0219] According to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, the storage medium including computer instructions that, when executed by a computer, cause the computer to perform the above-described method.

[0220] Those skilled in the art will recognize that the modules and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0221] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0222] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0223] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. Furthermore, reference can be made between the various method embodiments and between the various device embodiments; identical or corresponding content in different embodiments can be mutually referenced, without further elaboration.

Claims

1. A schedule management method, characterized in that, Applied to servers, including: Obtain N scheduled events to be completed within a target time period, where N is a positive integer; Generate one instance for each of the N schedule events; The completion status of the scheduled event is recorded in the instance information corresponding to the scheduled event; When the completion deadlines of the N schedule events arrive, check the completion status of each of the N schedule events, including: when the completion deadlines of the N schedule events arrive, scan the instance information corresponding to each of the N schedule events; determine the completion status of each schedule event based on the instance information corresponding to each schedule event, wherein the completion deadline is the end time of the last schedule event among the N schedule events, any time between the end time of the last schedule event among the N schedule events and the last moment of the target time period, or the last moment of the target time period; Based on the completion status of each schedule event, select M incomplete schedule events from the N schedule events, where M is a positive integer less than or equal to N; The M unfinished schedule events are sent to the client so that the client can display the M unfinished schedule events to the user.

2. The method according to claim 1, characterized in that, The method further includes: Based on the completion status of each schedule event, count the number of schedule events in different completion statuses among the N schedule events; The number of calendar events in different completion states among the N calendar events is sent to the client and / or terminal device so that the client and / or terminal device can display it.

3. The method according to claim 1, characterized in that, The step of checking the completion status of each of the N schedule events includes: If the scheduled event is found to be completed within the target time period, then the completion status of the scheduled event is determined to be "completed"; or, If it is found that the scheduled event is not completed within the target time period and the validity period of the scheduled event has not expired, then the completion status of the scheduled event is determined to be incomplete; or, If it is found that the scheduled event has not been completed within the target time period and the validity period of the scheduled event has expired, then the completion status of the scheduled event is determined to be expired.

4. The method according to claim 3, characterized in that, The step of selecting M incomplete schedule events from the N schedule events based on the completion status of each schedule event includes: The schedule events with an incomplete status among the N schedule events are identified as the M incomplete schedule events.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive a first schedule creation request sent by the client, the first schedule creation request including a jump link to the target task associated with the first schedule event; Based on the first schedule creation request, a first schedule event is created, and the key information of the first schedule event includes the jump link of the target task; The key information of the first schedule event is sent to the client so that the client displays a jump link for the target task. The jump link is used to jump to the interface where the target task is located when the user triggers the jump link.

6. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive a second schedule creation request sent by the client, the second schedule creation request including the business type and business identifier associated with the second schedule event; Based on the second schedule creation request, a second schedule event is created. The key information of the second schedule event includes the business type and business identifier associated with the second schedule event. The key information of the second schedule event is sent to the client so that the client can display the business type and business identifier associated with the second schedule event.

7. The method according to claim 6, characterized in that, The method further includes: Receive a schedule operation request sent by the business system, wherein the schedule operation request includes the business type and business identifier associated with the second schedule event; Query the second schedule event based on the business type and business identifier associated with the second schedule event; Perform the target operation on the second schedule event according to the schedule operation request.

8. The method according to claim 7, characterized in that, The step of querying the second schedule event based on the business type and business identifier associated with the second schedule event includes: If multiple schedule events matching the business type and business identifier are found based on the business type and business identifier associated with the second schedule event, the schedule event with the earliest creation time among the multiple schedule events is determined as the second schedule event.

9. The method according to claim 7, characterized in that, The schedule operation request includes a schedule deletion request or a schedule modification request. If the schedule operation request is a schedule deletion request, then the target operation is a deletion operation. If the schedule operation request is a schedule modification request, then the target operation is a modification operation.

10. A schedule management method, characterized in that, Applied to the client side, including: The system receives M schedule events from N schedule events sent by the server, where M is a positive integer less than or equal to N. The completion status of these N schedule events is checked when their completion deadlines arrive. The M schedule events with an incomplete completion status are N schedule events that the server has pre-selected and are scheduled to be completed within a target time period, where N is a positive integer. An instance is generated for each of the N schedule events. The completion status of each schedule event is recorded in the instance information corresponding to that event. When the completion deadline of each of the N schedule events arrives, the system checks the completion status of the N schedule events. The completion status of each scheduled event in the event includes: when the completion deadline of the N scheduled events arrives, scanning the instance information corresponding to each of the N scheduled events; determining the completion status of each scheduled event based on the instance information corresponding to each scheduled event, wherein the completion deadline is any time between the end time of the last scheduled event among the N scheduled events, the end time of the last scheduled event among the N scheduled events and the last moment of the target time period, or the last moment of the target time period; and selecting M uncompleted scheduled events from the N scheduled events based on the completion status of each scheduled event. Display the M unfinished schedule events to the user.

11. The method according to claim 10, characterized in that, The method further includes: The number of schedule events in different completion states among N schedule events sent by the receiving server, wherein the number of schedule events in different completion states among the N schedule events is obtained by counting the completion status of each schedule event among the N schedule events; This displays the number of schedule events in different completion states among the N schedule events.

12. The method according to claim 10, characterized in that, The method further includes: Receive a first schedule creation request sent by the user, the first schedule creation request including a jump link to the target task associated with the first schedule event; Send the first schedule creation request to the server; The server receives key information about the first schedule event, which is created by the server based on the first schedule creation request. The key information about the first schedule event includes the jump link of the target task. The user is shown a jump link to the target task, which is used to jump to the interface where the target task is located when the user triggers the jump link.

13. The method according to claim 10, characterized in that, The method further includes: Receive a second schedule creation request sent by the user, the second schedule creation request including the business type and business identifier associated with the second schedule event; Send the second schedule creation request to the server; The server receives key information about the second schedule event, which is created by the server based on the second schedule creation request. The key information about the second schedule event includes the business type and business identifier associated with the second schedule event. The user is shown the business type and business identifier associated with the second schedule event.

14. The method according to claim 10, characterized in that, The method further includes: When the system detects that the user has triggered a voice playback option for a target schedule event, it plays key information about the target schedule event to the user via voice.

15. A server, characterized in that, include: The acquisition unit is used to acquire N scheduled events to be completed within a target time period, where N is a positive integer; The processing unit is configured to generate an instance for each of the N schedule events; The completion status of the scheduled event is recorded in the instance information corresponding to the scheduled event; When the completion deadlines of the N schedule events arrive, check the completion status of each of the N schedule events, including: when the completion deadlines of the N schedule events arrive, scan the instance information corresponding to each of the N schedule events; determine the completion status of each schedule event based on the instance information corresponding to each schedule event, wherein the completion deadline is the end time of the last schedule event among the N schedule events, any time between the end time of the last schedule event among the N schedule events and the last moment of the target time period, or the last moment of the target time period; The selection unit is used to select M incomplete schedule events from the N schedule events based on the completion status of each schedule event, where M is a positive integer less than or equal to N; The first transceiver unit is used to send the M unfinished schedule events to the client so that the client can display the M unfinished schedule events to the user.

16. A client, characterized in that, include: The second transceiver unit is used to receive M schedule events with an incomplete status out of N schedule events sent by the server, where M is a positive integer less than or equal to N. The completion status of the N schedule events is checked when the completion deadline of the N schedule events arrives. The M schedule events with an incomplete status are N schedule events to be completed within a preset target time period obtained by the server, where N is a positive integer. An instance is generated for each of the N schedule events. The completion status of the scheduled event is recorded in the instance information corresponding to the scheduled event; When the completion deadlines of the N scheduled events arrive, check the completion status of each of the N scheduled events, including: scanning the instance information corresponding to each of the N scheduled events when the completion deadlines of the N scheduled events arrive; determining the completion status of each scheduled event based on the instance information corresponding to each scheduled event, wherein the completion deadline is any time between the end time of the last scheduled event in the N scheduled events, the end time of the last scheduled event in the N scheduled events and the last moment of the target time period, or the last moment of the target time period; and selecting M uncompleted scheduled events from the N scheduled events based on the completion status of each scheduled event. The display unit is used to display the M unfinished schedule events to the user.

17. A schedule management system, characterized in that, include: A client and a server, wherein the server is configured to implement the method as claimed in any one of claims 1 to 9, and the client is configured to implement the method as claimed in any one of claims 10 to 14.

18. An electronic device, characterized in that, include: Processor and memory; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method as claimed in any one of claims 1 to 9 or 10 to 14.

19. A computer-readable storage medium, characterized in that, The storage medium includes computer instructions that, when executed by a computer, cause the computer to perform the method as described in any one of claims 1 to 9 or 10 to 14.

Images