Schedule data processing and display method and device, computer device and storage medium

Abstract

The application relates to a schedule data processing and display method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: when a first account in a first communication application and a second account in a second communication application have an association relationship, receiving external schedule data belonging to the second account and sent by a communication application server of the second communication application; based on the association relationship, fusing the external schedule data into a schedule data set associated with the first account; and in response to a schedule data synchronization event, synchronizing the latest schedule data set associated with the first account to a terminal in which the first communication application is logged in by the first account. By using the method, schedule data can be efficiently synchronized, and schedule arrangement conflicts can be reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer equipment, storage medium and computer program product for processing schedule data, as well as a method, apparatus, computer equipment, storage medium and computer program product for displaying schedule data. Background Technology

[0002] With the development of computer technology, using schedule management applications to manage time and achieve efficient work and life has become an increasingly popular choice. For example, people can manage their schedules through various types of applications such as social media apps, shopping apps, electronic calendars, and schedule management apps.

[0003] However, in current schedule management, it is difficult to effectively synchronize schedule data when multiple terminal devices under different application account systems are involved, which makes it easy for schedules to conflict. Summary of the Invention

[0004] Therefore, it is necessary to provide a schedule data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can efficiently synchronize schedule data and reduce schedule conflicts, as well as a schedule data display method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can efficiently synchronize schedule data and reduce schedule conflicts.

[0005] Firstly, this application provides a method for processing schedule data. The method includes:

[0006] When the first account in the first communication application is associated with the second account in the second communication application, it receives external schedule data belonging to the second account sent by the communication application server of the second communication application.

[0007] Based on the relationship, external schedule data is integrated into the schedule dataset associated with the first account;

[0008] In response to a calendar data synchronization event, the latest calendar dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account.

[0009] Secondly, this application also provides a schedule data processing apparatus. The apparatus includes:

[0010] The schedule data receiving module is used to receive external schedule data belonging to the second account sent by the communication application server of the second communication application when there is an association between the first account in the first communication application and the second account in the second communication application.

[0011] The schedule data fusion module is used to merge external schedule data into the schedule dataset associated with the first account based on the relationship between them.

[0012] The schedule data synchronization module is used to respond to schedule data synchronization events and synchronize the latest schedule dataset associated with the first account to the terminal logged into the first communication application with the first account.

[0013] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0014] When the first account in the first communication application is associated with the second account in the second communication application, it receives external schedule data belonging to the second account sent by the communication application server of the second communication application.

[0015] Based on the relationship, external schedule data is integrated into the schedule dataset associated with the first account;

[0016] In response to a calendar data synchronization event, the latest calendar dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account.

[0017] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0018] When the first account in the first communication application is associated with the second account in the second communication application, it receives external schedule data belonging to the second account sent by the communication application server of the second communication application.

[0019] Based on the relationship, external schedule data is integrated into the schedule dataset associated with the first account;

[0020] In response to a calendar data synchronization event, the latest calendar dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account.

[0021] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0022] When the first account in the first communication application is associated with the second account in the second communication application, it receives external schedule data belonging to the second account sent by the communication application server of the second communication application.

[0023] Based on the relationship, external schedule data is integrated into the schedule dataset associated with the first account;

[0024] In response to a calendar data synchronization event, the latest calendar dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account.

[0025] The aforementioned schedule data processing method, apparatus, computer equipment, storage medium, and computer program product, when a first account in a first communication application and a second account in a second communication application are associated, receive external schedule data belonging to the second account sent by the communication application server of the second communication application, and merge the external schedule data into the schedule dataset associated with the first account based on the association relationship. In response to a schedule data synchronization event, the latest schedule dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account. During schedule data processing, for first and second accounts that are associated under different account systems, external schedule data belonging to the second account can be merged into the schedule dataset associated with the first account based on the association relationship, thereby synchronizing schedule data from different account systems on the terminal logged into the first communication application with the first account. This achieves efficient schedule data synchronization and reduces schedule conflicts.

[0026] Sixthly, this application provides a method for displaying schedule data. The method includes:

[0027] In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed;

[0028] The schedule display area displays schedule data; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset incorporates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0029] Seventhly, this application also provides a schedule data display device. The device includes:

[0030] The schedule display trigger module is used to display the schedule display area in response to the schedule display trigger event in the first communication application logged in with the first account;

[0031] The schedule data display module is used to display schedule data in the schedule display area; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset integrates external schedule data belonging to the second account in the second communication application, and there is an association relationship between the first account and the second account.

[0032] Eighthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0033] In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed;

[0034] The schedule display area displays schedule data; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset incorporates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0035] Ninthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0036] In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed;

[0037] The schedule display area displays schedule data; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset incorporates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0038] Tenthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0039] In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed;

[0040] The schedule display area displays schedule data; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset incorporates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0041] The aforementioned schedule data display method, apparatus, computer equipment, storage medium, and computer program product, in a first communication application logged in with a first account, responds to a schedule display trigger event and displays schedule data from the latest schedule dataset associated with the first account in the displayed schedule display area. This schedule dataset incorporates external schedule data from a second account in a second communication application, and the first and second accounts are associated. During the schedule data display process, for the first and second accounts that are associated under different account systems, the external schedule data belonging to the second account is merged into the schedule dataset associated with the first account. This allows for the synchronized display of schedule data from different account systems within the first communication application logged in with the first account, achieving efficient synchronization of schedule data and reducing scheduling conflicts. Attached Figure Description

[0042] Figure 1 This is an application environment diagram of a schedule data processing and display method in one embodiment;

[0043] Figure 2 This is a flowchart illustrating a schedule data processing method in one embodiment;

[0044] Figure 3 This is a schematic diagram of the interface for synchronously displaying schedule data in one embodiment;

[0045] Figure 4 This is a schematic diagram of the schedule data fusion process in one embodiment;

[0046] Figure 5 This is a flowchart illustrating a method for displaying schedule data in one embodiment;

[0047] Figure 6 This is a schematic diagram illustrating the interface changes that trigger the synchronized display of schedule data in one embodiment.

[0048] Figure 7 This is a schematic diagram illustrating the interface changes that trigger email display in one embodiment;

[0049] Figure 8 This is a schematic diagram of an interface for displaying schedule data in a calendar, as shown in one embodiment.

[0050] Figure 9 This is a schematic diagram of the interface for displaying corporate emails in an enterprise communication application, as shown in one embodiment.

[0051] Figure 10 This is a schematic diagram of an interface that synchronously displays corporate email calendar data in an enterprise communication application, as shown in one embodiment.

[0052] Figure 11 This is a schematic diagram of the interface for external application control in one embodiment;

[0053] Figure 12 This is a schematic diagram of the interface for enterprise email activation management in one embodiment;

[0054] Figure 13 A sequence diagram illustrating the process of synchronizing schedule data in one embodiment;

[0055] Figure 14 This is a sequence diagram of the process for unbinding a local email address in one embodiment.

[0056] Figure 15 This is a structural block diagram of a schedule data processing device in one embodiment;

[0057] Figure 16 This is a structural block diagram of a schedule data display device in one embodiment;

[0058] Figure 17 This is an internal structural diagram of a computer device in one embodiment;

[0059] Figure 18 This is a diagram of the internal structure of a computer device in another embodiment. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0061] The schedule data processing method provided in this application embodiment can be applied to, for example... Figure 1In the application environment shown, the first terminal 102 communicates with the first communication application server 106 via a network, and the second terminal 104 communicates with the second communication application server 108 via a network. The first communication application server 106 and the second communication application server 108 also communicate via a network. The data storage system can store the data that the first and second communication application servers 106 and 108 need to process. The data storage system can be integrated on either the first or second communication application server 106, or it can be located in the cloud or on another server. Users log in to the first communication application on the first terminal 102 using a first account, and log in to the second communication application on the second terminal 104 using a second account. Users can establish a relationship between the first and second accounts in the first communication application on the first terminal 102, and in the second communication application on the second terminal 104, they can create schedule events using the second account, generate external schedule data, and send it from the second communication application server 108 to the first communication application server 106. When a first account in the first communication application is associated with a second account in the second communication application, the first communication application server 106 receives external schedule data belonging to the second account sent by the second communication application server 108 of the second communication application, and merges the external schedule data into the schedule dataset associated with the first account based on the association relationship. In response to the schedule data synchronization event, the first communication application server 106 synchronizes the latest schedule dataset associated with the first account to the first terminal 102.

[0062] The schedule data display method provided in this application embodiment can be applied to, for example... Figure 1In the application environment shown, the first terminal 102 communicates with the first communication application server 106 via a network, and the second terminal 104 communicates with the second communication application server 108 via a network. The first communication application server 106 and the second communication application server 108 also communicate via a network. The data storage system can store the data that the first and second communication application servers 106 and 108 need to process. The data storage system can be integrated on either the first or second communication application server 106, or it can be located in the cloud or on another server. Users log in to the first communication application on the first terminal 102 using a first account, and log in to the second communication application on the second terminal 104 using a second account. Users can establish a relationship between the first and second accounts in the first communication application on the first terminal 102, and in the second communication application on the second terminal 104, they can create schedule events using the second account, generate external schedule data, and send it from the second communication application server 108 to the first communication application server 106. In the first communication application logged in with the first account, the first terminal 102 responds to the calendar display trigger event and displays the latest calendar data in the calendar display area associated with the first account. The calendar dataset integrates external calendar data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0063] Furthermore, the first terminal 102 or the second terminal 104 can each install a first communication application and a second communication application, respectively, to simultaneously achieve communication with the first communication application server 106 and the second communication application server 108 on either the first terminal 102 or the second terminal 104. Additionally, the first communication application and the second communication application can each install corresponding clients on either the first terminal 102 or the second terminal 104. For example, clients for the first communication application and the second communication application can be installed on the first terminal 102. Alternatively, the first communication application and the second communication application can be implemented within the same client as plugins or sub-applications. For instance, a client for the first communication application can be installed on the first terminal 102, and the second communication application can be installed and run as a plugin or sub-application within that client.

[0064] The first terminal 102 and the second terminal 104 can be, but are not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. The first communication application server 106 and the second communication application server 108 can be implemented using independent servers or a server cluster composed of multiple servers.

[0065] In one embodiment, such as Figure 2 As shown, a method for processing schedule data is provided, which can be applied to... Figure 1 Taking the first communication application server in the example, the following steps are included:

[0066] Step 202: When there is an association between the first account in the first communication application and the second account in the second communication application, receive external schedule data belonging to the second account sent by the communication application server of the second communication application.

[0067] A schedule refers to the plan and arrangement of a specific time point or period, such as a day, week, or month. Schedule data is electronic data of the schedule when it is managed by computer. Depending on the content of the schedule, the schedule data can have different data formats, such as text, graphic symbols, numbers, images, audio, and video. Communication applications refer to applications that achieve data communication through networks based on computer technology, such as instant messaging applications, email applications, and other applications capable of communication. The first communication application and the second communication application are different types of communication applications with different account systems. For example, the first communication application can be an instant messaging application, and the second communication application can be an email application; or the first communication application can be a first instant messaging application, and the second communication application can be a second instant messaging application. The first account belongs to the first communication application, and the second account belongs to the second communication application. The first account and the second account belong to different account systems of the first communication application.

[0068] In practical applications, the first and second communication applications can be implemented using separate clients. For example, the first communication application can be implemented by installing a first client on a terminal, and the second communication application can be implemented by installing a second client on the terminal. Alternatively, the first and second communication applications can be implemented within the same client. For instance, the first client can be installed on the terminal, and the second communication application can be implemented within that first client as a plugin. This involves adding a plugin for the second communication application to the first client and running the plugin within it. In other implementations, the second communication application can also be implemented within the first client as a sub-application. Specifically, a sub-application of the second communication application can be added to the first client and run within it to implement the second communication application.

[0069] A connection refers to establishing a link between accounts belonging to different account systems, forming a mapping between accounts. This connection can be achieved through account binding. For example, a user can create a first account under the account system of a first communication application to communicate within that application; similarly, the same user can create a second account under the account system of a second communication application to communicate within that application. The user can then link the first and second accounts, such as by binding them, thus establishing a connection between the accounts in the first and second communication applications. By establishing this connection, interoperability between the two applications can be achieved. For instance, a user can receive communication messages from the second account in the second communication application through their first account in the first application. The connection between the first and second accounts can be pre-built according to actual needs.

[0070] The communication application server is the server that enables data communication for the corresponding communication application. External schedule data belongs to the second account and is generated within the application environment of the second communication application. Specifically, external schedule data can be schedule data associated with the second account. For example, external schedule data can include schedule data actively created by the user through the second account in the second communication application, and it can also include schedule data generated corresponding to schedule invitations received by the second account in the second communication application. Relative to the communication application server of the first communication application, external schedule data belongs to the second account in the second communication application and is not created or generated in the first communication application; it originates from schedule data from an external application.

[0071] Specifically, if a first account in the first communication application is associated with a second account in the second communication application, indicating that the first and second accounts have been linked, and if account binding is performed in advance, the server of the first communication application can receive external schedule data belonging to the second account sent by the communication application server of the second communication application. In practical applications, if a first account in the first communication application is associated with a second account in the second communication application, when external schedule data belonging to the second account is generated in the second communication application, the communication application server of the second communication application sends the external schedule data to the server of the first account to synchronize the external schedule data belonging to the second account in the first communication application, thereby achieving synchronized processing of schedule data under different account systems.

[0072] Step 204: Based on the association relationship, merge the external schedule data into the schedule dataset associated with the first account.

[0073] The schedule dataset is associated with the first account and includes various schedule data belonging to the first account; that is, the schedule dataset is used to store schedule data belonging to the first account. Specifically, after the server obtains external schedule data, it merges the external schedule data into the schedule dataset associated with the first account based on the association between the first and second accounts, thereby realizing the aggregation of schedule data of the first account and schedule data of the second account.

[0074] In practical implementation, after receiving external schedule data belonging to the second account, the server can query the first account associated with the second account based on the relationship. After identifying the first account, it can query the schedule dataset associated with the first account and merge the external schedule data belonging to the second account into the schedule dataset associated with the first account. For example, the server can aggregate and write the external schedule data into the schedule dataset associated with the first account according to the schedule data format of the schedule dataset associated with the first account, thereby realizing the fusion between the schedule data of the first account and the schedule data of the second account.

[0075] Step 206: In response to the calendar data synchronization event, synchronize the latest calendar dataset associated with the first account to the terminal that is logged into the first communication application with the first account.

[0076] The calendar data synchronization event refers to an event that triggers calendar data synchronization processing. Specifically, a calendar data synchronization event can be triggered when certain conditions are met. For example, when a user actively requests calendar data synchronization by sending a synchronization request message, or when the server detects an update to the calendar dataset associated with the first account, a calendar data synchronization event can be generated. The server then synchronizes the latest calendar dataset associated with the first account to the terminal logged into the first communication application with the first account. The calendar data synchronized on the terminal originates from the latest calendar dataset associated with the first account. This calendar dataset includes calendar data belonging to the second account in the second communication application, thus achieving the synchronization of the second account's calendar data to the terminal logged into the first communication application with the first account.

[0077] Specifically, the server can detect whether a calendar data synchronization event has occurred. If a calendar data synchronization event occurs, the server can respond to the event by determining the latest calendar dataset associated with the first account and sending the latest calendar dataset to the terminal logged into the first communication application with the first account. In a specific application, such as Figure 3As shown, on the terminal that logs into the first communication application with the first account, the schedule data belonging to the first account and the schedule data belonging to the second account are displayed simultaneously. Thus, the user can directly know the schedule data belonging to the first account and the second account in the first communication application that is logged in with the first account. This realizes the synchronization of schedule data under different account systems on the terminal that logs into the first communication application with the first account, which is conducive to the efficient synchronization of schedule data and reduces schedule conflicts.

[0078] In the aforementioned schedule data processing method, when a first account in a first communication application and a second account in a second communication application are associated, external schedule data belonging to the second account, sent by the communication application server of the second communication application, is received. Based on the association relationship, the external schedule data is merged into the schedule dataset associated with the first account. In response to a schedule data synchronization event, the latest schedule dataset associated with the first account is synchronized to the terminal logged into the first communication application with the first account. During schedule data processing, for first and second accounts with associated relationships under different account systems, external schedule data belonging to the second account can be merged into the schedule dataset associated with the first account based on the association relationship. This allows schedule data from different account systems to be synchronized on the terminal logged into the first communication application with the first account, achieving efficient schedule data synchronization and reducing schedule conflicts.

[0079] In one embodiment, such as Figure 4 As shown, the process of merging schedule data, that is, merging the external schedule data into the schedule dataset associated with the first account based on the aforementioned relationship, includes:

[0080] Step 402: Based on the association, determine the first account in the first communication application.

[0081] The first account and the second account are related, specifically through an account binding relationship where the user links the first account to the second account. After receiving external schedule data belonging to the second account, the server can, based on the relationship between the first and second accounts, retrieve the first account from the first communication application using the second account. Specifically, the server can query the relationship between each account in the first communication application, and, combined with the second account, determine the first account associated with the second account from among all the accounts in the first communication application.

[0082] Step 404: Determine the calendar dataset associated with the first account from the calendar dataset of the first communication application.

[0083] The schedule dataset is used to store schedule data, and the schedule dataset of the first communication application is used to store the schedule data of each account in the first communication application. Specifically, the server can query the schedule dataset of the first communication application, which can be obtained by combining the schedule datasets associated with each account. The server determines the schedule dataset associated with the first account from the schedule dataset of the first communication application, and the schedule dataset associated with the first account includes the schedule data belonging to the first account.

[0084] Step 406: Integrate the external schedule data into the schedule dataset associated with the first account.

[0085] Specifically, after the server determines the calendar dataset associated with the first account, it merges external calendar data belonging to the second account into the calendar dataset associated with the first account. For example, the server can add external calendar data to the calendar dataset associated with the first account to achieve the fusion of calendar data between the first account and the second account.

[0086] In its implementation, the calendar dataset associated with the first account can be divided into subsets, such as a synchronized subset and a subset to be synchronized. The server can merge external calendar data into the subset to be synchronized for the first account, facilitating subsequent calendar synchronization. Furthermore, the calendar dataset associated with the first account can be divided into a local subset and an external subset. The local subset stores calendar data generated directly within the first communication application, while the external subset stores calendar data generated in other communication applications. The server can also merge external calendar data belonging to the second account into the external subset.

[0087] In this embodiment, based on the association between the first account and the second account, the first account is determined from the first communication application, and the calendar dataset associated with the first account is determined, so as to merge the external calendar data belonging to the second account into the calendar dataset associated with the first account, thereby aggregating the external calendar data of the second account, which belongs to a different account system than the first account, into the calendar dataset associated with the first account, so as to achieve efficient synchronization of calendar data of different account systems in the first communication application account.

[0088] In one embodiment, in response to a calendar data synchronization event, synchronizing the latest calendar dataset associated with the first account to the terminal logged into the first communication application with the first account includes: when the calendar dataset associated with the first account triggers an update, determining the terminal logged into the first communication application with the first account; and synchronizing the latest calendar dataset associated with the first account to the terminal.

[0089] The calendar data synchronization event is an event that needs to be triggered to perform calendar data synchronization processing. Specifically, it is an event that triggers an update of the calendar dataset associated with the first account. When the calendar dataset associated with the first account is updated, it indicates that the state of the calendar dataset associated with the first account has changed. For example, when new calendar data is written or when calendar data is modified, a calendar data synchronization event is triggered.

[0090] Specifically, the server can detect the schedule dataset associated with the first account. Specifically, it can detect the status of the schedule dataset associated with the first account. When the schedule dataset associated with the first account triggers an update, that is, when the dataset status is updated, the server determines the terminal that is logged in to the first communication application with the first account and synchronizes the latest schedule dataset associated with the first account to the terminal. Thus, when the schedule dataset associated with the first account triggers an update, the server can promptly synchronize the update of the schedule data to the corresponding terminal to ensure the timeliness of the schedule data.

[0091] In this embodiment, when the schedule dataset associated with the first account is updated, a schedule data synchronization event is considered to be triggered. The server synchronizes the latest schedule dataset associated with the first account to the terminal, thereby ensuring the timeliness of the schedule data.

[0092] In one embodiment, synchronizing the latest schedule dataset associated with the first account to the terminal includes: generating a synchronization prompt message based on the schedule dataset associated with the first account; sending the synchronization prompt message to the terminal to instruct the terminal to send a schedule data synchronization request based on the synchronization prompt message; and sending the latest schedule dataset associated with the first account to the terminal based on the schedule data synchronization request sent by the terminal.

[0093] The synchronization notification message is used to notify the terminal that the schedule data has been updated, so that the user can update the displayed schedule data in a timely manner. The schedule data synchronization request is sent by the terminal to the server to request the server to perform synchronization update processing on the schedule data.

[0094] Specifically, when the server synchronizes the latest schedule dataset associated with the first account to the terminal, the server generates a synchronization notification message based on the schedule dataset associated with the first account and sends the generated synchronization notification message to the terminal logged into the first communication application with the first account, thereby notifying the terminal that the schedule data of the first account has been updated. After receiving the synchronization notification message, the user of the terminal can send a schedule data synchronization request to the server to request the server to synchronize the schedule data. When the server receives the schedule data synchronization request sent by the terminal, indicating that the terminal requests to update the schedule data, the server sends the latest schedule dataset associated with the first account to the terminal. In specific implementation, the server can determine the latest schedule dataset associated with the first account from the first communication application and send the latest schedule dataset to the terminal, so that the terminal can update and synchronize the schedule data of the first account based on the latest schedule dataset.

[0095] In this embodiment, a synchronization notification message is generated to notify the terminal of the update of the schedule dataset associated with the first account. Based on the schedule data synchronization request sent by the terminal, the latest schedule dataset associated with the first account is sent to the terminal, thereby prompting the terminal to synchronize the updated schedule data in a timely manner and ensuring the timeliness of the schedule data on the terminal.

[0096] In one embodiment, in response to a calendar data synchronization event, synchronizing the latest calendar dataset associated with a first account to a terminal logged into the first communication application with the first account includes: when a calendar data synchronization request is received from the terminal, determining the synchronization request account logged into the first communication application in the terminal based on the calendar data synchronization request; when the synchronization request account is the first account, obtaining the latest calendar dataset associated with the first account; and sending the latest calendar dataset associated with the first account to the terminal for calendar data synchronization processing on the terminal.

[0097] The calendar data synchronization request is sent from the terminal to the server to request the synchronization and updating of calendar data. This request can be generated by the user when initiating calendar synchronization on the terminal; for example, the user can trigger the request when accessing the calendar application on the terminal, or the user can actively trigger it after receiving a synchronization prompt message from the server. The synchronization request account is the application account used to trigger the calendar synchronization on the terminal, specifically the application account logged into the First Communication application.

[0098] Specifically, users can actively trigger calendar synchronization through their terminals. For example, a user can click on the calendar synchronization control on the terminal or enter the calendar application. The terminal then generates a calendar data synchronization request and sends it to the server. When the server receives the calendar data synchronization request from the terminal, it determines the synchronization request account logged into the first communication application on the terminal. For instance, the server can parse the calendar data synchronization request to obtain the synchronization request account logged into the first communication application on the terminal. This calendar data synchronization request is issued by the synchronization request account, meaning the calendar data of the synchronization request account needs to be synchronized and updated. The server matches the synchronization request account with the first account. If the synchronization request account is determined to be the first account (meaning the first account is logged into the first communication application on the terminal), the server obtains the latest calendar dataset associated with the first account and sends it to the terminal for calendar data synchronization. The terminal can then display the calendar data from the latest calendar dataset associated with the first account.

[0099] In this embodiment, the terminal actively triggers calendar synchronization by sending a calendar data synchronization request. When the server determines that the synchronization request account logged into the first communication application is the first account, it sends the latest calendar dataset associated with the first account to the terminal for calendar data synchronization processing. This achieves efficient synchronization of calendar data under different application account systems and reduces calendar conflicts.

[0100] In one embodiment, synchronizing the latest schedule dataset associated with the first account to the terminal logged into the first communication application with the first account includes: determining the latest schedule dataset associated with the first account; determining the schedule data to be synchronized for the first account from the latest schedule dataset; and synchronizing the schedule data to be synchronized to the terminal logged into the first communication application with the first account.

[0101] The schedule data to be synchronized refers to the schedule data in the latest schedule dataset associated with the first account that has not yet been synchronized. In practical applications, the server can periodically synchronize the schedule data of the first account, so the schedule data to be synchronized can be the incremental schedule data that needs to be synchronized to the terminal within the current synchronization period.

[0102] Specifically, in response to a calendar data synchronization event, the server determines the latest calendar dataset associated with the first account. In practical applications, the calendar dataset associated with the first account can continuously integrate external calendar data. For example, external calendar data can be integrated into the calendar dataset associated with the first account immediately upon receipt, thus continuously updating the calendar dataset associated with the first account. When calendar data synchronization is required, the server determines the latest calendar dataset associated with the first account and performs synchronization based on the latest calendar data. The server determines the incremental calendar data of the first account compared to the last synchronization from the latest calendar dataset. This incremental calendar data can be used as the calendar data to be synchronized, which is the calendar data that has not been synchronized on the terminal. In specific implementation, the server can determine the historical synchronization data of the first account on the terminal and determine the calendar data to be synchronized for the first account from the latest calendar dataset based on the historical synchronization data. The server synchronizes the calendar data to be synchronized to the terminal logged into the first communication application with the first account. Specifically, the server can send the calendar data to be synchronized to the terminal logged into the first communication application with the first account.

[0103] In this embodiment, the server synchronizes the calendar data to be synchronized from the latest calendar dataset associated with the first account to the terminal that logged into the first communication application with the first account, thereby synchronizing the incremental calendar data of the first account to the terminal, which can reduce the amount of data to be processed and ensure the processing efficiency of calendar data synchronization.

[0104] In one embodiment, determining the schedule data to be synchronized for the first account from the latest schedule dataset includes: determining the historical synchronization sequence number in the terminal logged into the first communication application with the first account; determining the synchronization sequence number based on the historical synchronization sequence number and the latest schedule dataset; and determining the schedule data to be synchronized for the first account from the latest schedule dataset according to the synchronization sequence number.

[0105] The historical synchronization sequence number refers to the sequence number of historically synchronized data that has already undergone synchronization processing in the terminal. For each piece of schedule data, a corresponding sequence number can be configured to effectively manage each schedule data. For example, the sequence number can be incremented, meaning earlier acquired schedule data will have a smaller sequence number, and later acquired schedule data will have a larger sequence number. The sequence number can be used to identify the schedule data of the first account in the schedule dataset. The sequence number to be synchronized refers to the sequence number of the schedule data in the schedule dataset that needs to be synchronized.

[0106] Specifically, when determining the schedule data to be synchronized for the first account, the server can use the schedule data to be synchronized for the first account, that is, the historical synchronization sequence number of the historical synchronization data that has already been synchronized on the terminal. Based on the historical synchronization sequence number and the latest schedule dataset, the server determines the sequence number to be synchronized, and then determines the schedule data to be synchronized for the first account from the latest schedule dataset according to the determined sequence number. For example, if the server determines that the historical synchronization sequence number in the terminal logged into the first communication application with the first account is N, it indicates that the sequence number of the schedule data that has already been synchronized on the terminal is N. The server can then determine the sequence number to be synchronized based on the historical synchronization sequence number and the latest schedule dataset, such as N+10, which indicates that there are 10 schedule data items that need to be updated, with sequence numbers N+1 to N+10. The server can then determine the schedule data to be synchronized for the first account from the latest schedule dataset as the schedule data corresponding to sequence numbers N+1 to N+10.

[0107] In this embodiment, incremental schedule data that needs to be synchronized is determined by comparing the sequence numbers of the schedule data. The schedule data to be synchronized is determined by incremental synchronization, which can reduce the amount of data to be synchronized and ensure the efficiency of schedule data synchronization.

[0108] In one embodiment, synchronizing the latest schedule dataset associated with the first account to a terminal logged into the first communication application with the first account includes: determining schedule data filtering conditions that match the first account; determining schedule data to be synchronized from the latest schedule dataset associated with the first account according to the schedule data filtering conditions; and synchronizing the schedule data to be synchronized to the terminal logged into the first communication application with the first account.

[0109] The schedule data filtering criteria are used to filter schedule data that needs to be synchronized. These criteria can include various options such as account, time, location, participants, topic, and type. By using these filtering criteria, the schedule data to be synchronized on the terminal can be flexibly configured to effectively categorize various types of schedule data, expanding the applicable scenarios for schedule synchronization processing.

[0110] Specifically, the server can determine the schedule data filtering criteria that match the first account. These criteria can be specified by the user through their logged-in first account; for example, the user can configure the filtering criteria in the terminal's first communication application using their logged-in first account. The schedule data filtering criteria can also be preset with default settings, such as setting them to all schedule data, schedule data for the next week, or schedule data for the next month. The server determines the schedule data to be synchronized from the latest schedule dataset associated with the first account according to the filtering criteria. In practice, the server can filter each schedule data in the latest schedule dataset associated with the first account based on the filtering criteria, thereby selecting the schedule data that meets the filtering criteria and identifying it as the schedule data to be synchronized. The server then synchronizes the schedule data to be synchronized to the terminal logged into the first communication application with the first account. Specifically, the server can send the schedule data to be synchronized to the terminal logged into the first communication application with the first account.

[0111] In this embodiment, the server can filter out the schedule data to be synchronized from the latest schedule data set associated with the first account based on the schedule data filtering conditions that match the first account, and synchronize the schedule data to be synchronized to the terminal that is logged into the first communication application with the first account. This allows for flexible configuration of the synchronized schedule data according to the user's actual needs, expands the applicable scenarios for schedule data processing, and ensures the efficiency of schedule data processing.

[0112] In one embodiment, the schedule data processing method further includes: determining a local associated account in a terminal that logs into the first communication application with a first account; when the local associated account is determined to include a second account, generating a schedule synchronization cancellation message for the second account; and sending the schedule synchronization cancellation message to the terminal to instruct the terminal to cancel the schedule data synchronization processing for the second account through the communication application server of the second communication application.

[0113] The locally associated account refers to the account that is associated with the first account on the terminal's local machine. This locally associated account can belong to a different application account system than the first account, such as an account belonging to a second communication application, or an account belonging to other communication applications. The terminal can receive and store the schedule data of the locally associated account, achieving local schedule data synchronization. In specific applications, the server of the locally associated account can directly send the schedule data to the terminal, allowing the terminal to receive and store the schedule data, thus achieving local schedule data synchronization on the terminal. The schedule synchronization cancellation message is used to cancel the synchronization of schedule data for the locally associated account on the terminal; that is, the terminal no longer directly receives and stores the schedule data of the locally associated account.

[0114] Specifically, the server determines the locally associated account in the terminal logged into the first communication application with the first account. Specifically, the server can query the account association information of the terminal logged into the first communication application with the first account and determine the locally associated account from the account association information. The server analyzes the locally associated account to determine whether it includes the second account in the second communication application. If the locally associated account includes the second account, it indicates that the terminal can directly perform schedule data synchronization processing on the external schedule data of the second account locally. To avoid duplicate schedule data synchronization, the server can generate a schedule synchronization cancellation message for the second account and send the schedule synchronization cancellation message to the terminal, instructing the terminal to cancel schedule data synchronization processing for the second account through the communication application server of the second communication application. In practical applications, after receiving the schedule synchronization cancellation message, the terminal no longer performs schedule data synchronization processing on the second account locally. That is, the terminal no longer obtains external schedule data belonging to the second account through the communication application server of the second communication application, but uniformly performs schedule data synchronization processing on external schedule data belonging to the second account through the server, thereby avoiding duplicate schedule data synchronization.

[0115] In this embodiment, when the local associated account of the terminal includes the second account, the terminal is instructed to disconnect the communication application server through the second communication application via the calendar synchronization cancellation message, and the calendar data synchronization processing is performed on the second account, thereby avoiding duplicate synchronization of calendar data and ensuring the accuracy of calendar data.

[0116] In one embodiment, external schedule data is obtained through a schedule data generation step, which includes: receiving a communication message associated with a second account through a second communication application; when the communication message is a schedule message type, performing schedule data analysis on the communication message to obtain a schedule data analysis result; and generating external schedule data belonging to the second account based on the schedule data analysis result.

[0117] The communication messages are those generated in the second communication application and associated with the second account. Specifically, they can include messages generated when other accounts communicate with the second account within the second communication application; for example, messages sent from other accounts to the second account, or messages sent from the second account to other accounts. The second communication application can be implemented as a standalone client, meaning a client application for the second communication application can be installed on a terminal to run it. Alternatively, the second communication application can be implemented as a plugin or sub-application within the same client; that is, a plugin or sub-application can be added to the client of the first communication application to run the second communication application. The schedule data analysis results refer to the analysis of communication messages to obtain schedule-related attribute information. This may include, but is not limited to, various schedule attribute information such as the account, time, location, participants, schedule topic, and schedule type. Based on the schedule data analysis results, external schedule data belonging to the second account can be generated.

[0118] Specifically, external schedule data belonging to the second account can be generated by the communication application server of the second communication application. Specifically, the communication application server of the second communication application can receive communication messages associated with the second account through the second communication application. For example, if the second communication application is an email application, the communication messages associated with the second account can be emails exchanged between the second account and the email application. The server determines the type of the communication message. When the communication message is a schedule message, it indicates that the communication message is related to a schedule and carries schedule information. The server can then perform schedule data analysis on the communication message, such as content recognition, to obtain the schedule data analysis results. Based on the obtained schedule data analysis results, the server generates external schedule data belonging to the second account. Specifically, the server can generate external schedule data belonging to the second account according to the schedule data analysis results and a preset schedule data format, such as a format including time, location, participants, and schedule content.

[0119] In this embodiment, when a communication message associated with a second account is received through a second communication application, if the communication message is a schedule message type, schedule data analysis is performed on the communication message, and external schedule data belonging to the second account is generated based on the obtained schedule data analysis results. This enables the generation of corresponding external schedule data based on the communication message associated with the second account, which is beneficial to improving the processing efficiency of schedule data synchronization.

[0120] In one embodiment, when the communication message is a schedule message type, schedule data analysis is performed on the communication message to obtain schedule data analysis results, including: determining the message type of the communication message; when the message type is a schedule message type, schedule events are extracted from the communication message to obtain schedule event extraction results.

[0121] The message type refers to the subject type of the communication message, such as notification, schedule, conversation, etc. For a schedule message type, it indicates that the communication message carries schedule event information, and schedule event extraction results related to the schedule event can be extracted from the communication message. The schedule data format is the expression format of the schedule data, specifically including items such as schedule time, location, participants, schedule topic, etc.

[0122] Specifically, after receiving the communication message associated with the second account, the server determines the message type. If the message type is a schedule message, it indicates that the message describes a schedule event. The server then extracts the schedule event from the message, such as through keyword recognition, to extract information related to the schedule event, thus obtaining the schedule event extraction result. The schedule event extraction result can include various schedule attribute information related to the schedule event, such as schedule time, location, participants, schedule topic, and other attribute information.

[0123] Furthermore, based on the results of the schedule data analysis, external schedule data belonging to the second account is generated, including: generating external schedule data belonging to the second account according to the schedule data format based on the schedule event extraction results.

[0124] Specifically, based on the extracted schedule events, the server generates external schedule data belonging to the second account according to a preset schedule data format. In practical applications, the server can obtain a preset schedule data format, which can be flexibly configured in advance according to actual needs. The server generates external schedule data belonging to the second account from the various schedule items included in the extracted schedule events, according to the schedule data format.

[0125] In this embodiment, when the message type of the communication message is a schedule message type, schedule events are extracted from the communication message, and according to the obtained schedule event extraction results, external schedule data belonging to the second account is generated according to the schedule data format. This enables the generation of corresponding external schedule data based on the communication messages associated with the second account, which is beneficial to improving the processing efficiency of schedule data synchronization.

[0126] In one embodiment, external schedule data is obtained through a schedule data generation step, which includes: in response to a schedule creation event in a second communication application, obtaining newly created schedule information based on the schedule creation event; and generating external schedule data belonging to the second account based on the newly created schedule information.

[0127] The "Schedule Creation Event" is the event that triggers the creation of a new schedule. This can be triggered by the user on the terminal, such as by clicking the schedule creation control. The "New Schedule Information" is the information about the newly created schedule. Based on this information, external schedule data belonging to the second account can be generated. Specifically, the user can trigger a schedule creation operation in the terminal's second communication application to send a schedule creation request to the server, thereby triggering the schedule creation event. The server responds to the schedule creation event in the second communication application by obtaining the new schedule information obtained based on the event, such as information that can be edited by the user. Based on the obtained new schedule information, the server generates external schedule data belonging to the second account. Specifically, the server can generate external schedule data belonging to the second account according to a preset schedule data format based on the new schedule information.

[0128] In this embodiment, the server can respond to a calendar creation event triggered by the user in the second communication application, and generate external calendar data belonging to the second account based on the newly created calendar information obtained from the calendar creation event. That is, it can generate corresponding external calendar data in a targeted manner, which is beneficial to improving the processing efficiency of calendar data synchronization.

[0129] In one embodiment, the schedule data processing method further includes: performing schedule conflict analysis on the schedule dataset associated with the first account to obtain schedule conflict analysis results; when the schedule conflict analysis results indicate that there is a schedule conflict, identifying abnormal schedule data with a schedule conflict; generating a schedule abnormality prompt message based on the abnormal schedule data, and sending the schedule abnormality prompt message to the terminal that logged into the first communication application with the first account.

[0130] Schedule conflict analysis refers to analyzing the scheduling of each schedule in a schedule dataset to determine whether there are any conflicts between them. For example, if the schedule dataset includes schedule A and schedule B, where schedule A is a meeting scheduled for 1:00 PM to 4:00 PM on March 2, 2022, and schedule B is a client visit scheduled for 2:00 PM to 3:00 PM on the same day, then schedule A and schedule B conflict. In other words, each schedule in the schedule dataset should not have any overlapping times. If there is overlap, the schedules cannot be completed simultaneously, and they conflict. Abnormal schedule data refers to schedules in the schedule dataset that have conflicts. Schedule exception messages are used to notify users of conflicting schedules in the dataset so that users can adjust their schedules in a timely manner to avoid conflicts.

[0131] Specifically, the server can perform schedule conflict analysis on the schedule dataset associated with the first account in real time or at regular intervals. Specifically, the server analyzes each schedule data in the schedule dataset associated with the first account to determine whether there are conflicts between the schedule data, including various types of conflicts such as time overlap conflicts and location cross-location conflicts. Time overlap conflicts occur when multiple schedule data overlap in time, making it impossible to execute all schedules simultaneously. Location cross-location conflicts occur when the locations of the schedules are significantly different, making it impossible to execute the corresponding schedule at the corresponding time. For example, if the schedule dataset includes schedule data C and schedule data D, where schedule data C is a schedule for attending an exhibition in Guangzhou from 13:00 to 16:00 on March 3, 2022, and schedule data B is a schedule for visiting a client in Shanghai from 16:00 to 18:00 on March 3, 2022, then after attending the exhibition in Guangzhou at 16:00, it is necessary to immediately visit the client in Shanghai. The large location difference prevents simultaneous execution, meaning that schedule data C and schedule data D have a location cross-location conflict.

[0132] The server performs a schedule conflict analysis on the schedule dataset associated with the first account. If a schedule conflict is detected, it indicates that there are schedules in the dataset that cannot be executed simultaneously. The server then identifies these conflicting schedules as abnormal. Based on this abnormal data, the server generates a schedule exception message and sends it to the terminal logged into the first communication application with the first account. This prompts the user to adjust the conflicting schedules to avoid further conflicts. In practice, after receiving the schedule exception message, users can adjust the conflicting schedules by changing details such as time and location. Users can also delete schedules to prevent scheduling conflicts. In addition, users can pre-set schedule priority conditions according to actual needs. The server can then adjust conflicting schedules based on their priorities, such as modifying schedule time or location or deleting them, thereby resolving conflicts between schedules. Users can confirm the schedules automatically adjusted by the server based on schedule priority conditions, thus improving the efficiency of schedule adjustment.

[0133] For example, users can pre-set the priorities of schedules from various sources and types based on their origin and type. When schedules with different priorities conflict, such as schedule data E (priority I) and schedule data F (priority II), where schedule data E has a higher priority than schedule data F, the server can adjust the schedule information of schedule data F, such as adjusting the trigger time of schedule data F, to avoid conflict with schedule data E. Users can confirm the adjusted schedule from the server. After user confirmation, the server then performs schedule data synchronization based on the adjusted schedule. Furthermore, users can also modify the server's adjustment results to adjust conflicting schedules according to their actual needs, thus avoiding conflicts between schedules.

[0134] In this embodiment, the server performs a schedule conflict analysis on the schedule dataset associated with the first account. When a schedule conflict exists in the schedule dataset, a schedule exception prompt message is generated based on the abnormal schedule data with the schedule conflict. By sending the schedule exception prompt message to the terminal, the user is notified of the conflict in the schedule data. This helps the user to adjust the conflicting schedule data in a timely manner, thereby avoiding conflicts between schedules.

[0135] In one embodiment, such as Figure 5 As shown, a method for displaying schedule data is provided, which can be applied to... Figure 1 Taking the first terminal as an example, the explanation includes the following steps:

[0136] Step 502: In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed.

[0137] The schedule data refers to the electronic data of schedules when using computers for schedule management. A schedule refers to the plan and arrangement of a specific time node or time period, such as a day, a week, or a month. Communication applications refer to applications that achieve data communication through networks based on computer technology, such as instant messaging applications, email applications, and various other applications capable of communication. The first account belongs to the first communication application and is an account registered under the account system of the first communication application. Schedule display trigger events are events that trigger the display of schedules. Specifically, these can be events generated by the user through schedule display trigger operations on the terminal, or trigger events generated when preset trigger conditions are met, such as automatically generating a schedule display trigger event when a preset time is reached, thereby triggering schedule display processing. The schedule display area is the area where schedule data is displayed; specifically, it can be an area designated within the application interface of the first communication application used to display the schedule data of the first account.

[0138] Specifically, the user logs into the first communication application on the terminal using the first account. The user can trigger a schedule display operation in the first communication application, thereby generating a schedule display trigger event. The terminal responds to the schedule display trigger event and displays a schedule display area for displaying schedule data.

[0139] Step 504: Display schedule data in the schedule display area; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset integrates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0140] External calendar data belongs to the second account and is generated within the application environment of the second communication application. Specifically, external calendar data can be calendar data associated with the second account. For example, external calendar data can include calendar data actively created by the user through the second account in the second communication application, as well as calendar data generated corresponding to calendar invitations received by the second account in the second communication application. Relative to the communication application server of the first communication application, external calendar data belongs to the second account in the second communication application and is not created or generated in the first communication application; it originates from an external application. The first and second communication applications are different types of communication applications with different account systems. The calendar dataset is associated with the first account and includes various calendar data belonging to the first account; that is, the calendar dataset is used to store calendar data belonging to the first account.

[0141] A connection refers to establishing a link between accounts belonging to different account systems, forming a mapping between accounts. This connection can be achieved through account binding. For example, a user can create a first account under the account system of a first communication application to communicate within that application; similarly, the same user can create a second account under the account system of a second communication application to communicate within that application. The user can then link the first and second accounts, such as by binding them, thus establishing a connection between the accounts in the first and second communication applications. By establishing this connection, interoperability between the two applications can be achieved. For instance, a user can receive communication messages from the second account in the second communication application through their first account in the first application. The connection between the first and second accounts can be pre-built according to actual needs.

[0142] Specifically, the terminal displays schedule data in the schedule display area. The displayed schedule data belongs to the latest schedule dataset associated with the first account. Specifically, the terminal can retrieve schedule data from the latest schedule dataset associated with the first account and display it in the schedule display area. The latest schedule dataset associated with the first account incorporates external schedule data belonging to a second account in a second communication application, and the first account and the second account are associated. Therefore, the schedule data displayed in the schedule display area integrates the schedule data of the first account and the schedule data of the second account, achieving efficient synchronization of schedule data and reducing scheduling conflicts.

[0143] In a specific application, such as Figure 6 As shown, in the first communication application logged in with the first account, the session interface of the first communication application is displayed, showing the session messages of the user's conversation through the first account. The user can click the schedule control in the side menu bar to generate a schedule display trigger event. The terminal responds to the schedule display trigger event, displays the schedule display area, and shows the schedule data in the latest schedule dataset associated with the first account in the schedule display area. Specifically, it includes schedule data from the first account and schedule data from the second account, thereby achieving efficient synchronous display of schedule data from the first account and schedule data from the second account in the first communication application.

[0144] In the aforementioned schedule data display method, in the first communication application logged in with the first account, in response to the schedule display trigger event, the latest schedule data belonging to the first account is displayed in the displayed schedule area. This schedule dataset incorporates external schedule data belonging to the second account in the second communication application, and the first and second accounts are associated. During the schedule data display process, for the first and second accounts that are associated under different account systems, the external schedule data belonging to the second account is merged into the schedule dataset associated with the first account. This allows schedule data from different account systems to be displayed synchronously in the first communication application logged in with the first account, achieving efficient synchronization of schedule data and reducing scheduling conflicts.

[0145] In one embodiment, in a first communication application logged in with a first account, in response to a schedule display trigger event, a schedule display area is displayed, including: displaying the communication application interface of the first communication application logged in with the first account, the communication application interface including a schedule entry; in response to a trigger operation on the schedule entry, entering the schedule display interface of the first account; and displaying the schedule display area in the schedule display interface.

[0146] The communication application interface is the interface for the first communication application. This interface provides access to various functions of the first communication application, such as conversations, schedules, and settings. The communication application interface includes a schedule entry point, which triggers entry to the schedule display interface, where the schedule data for the first account is displayed.

[0147] Specifically, after a user logs into the first communication application on the terminal using a first account, the terminal displays the communication application interface of the first communication application logged in with the first account. The communication application interface includes a schedule entry. The user can interact with the schedule entry; for example, if the user clicks on the schedule entry, the terminal responds to the user's triggered operation and enters the schedule display interface of the first account. The schedule display interface is used to display the schedule data associated with the first account. The terminal displays a schedule display area in the schedule display interface, which can display schedule data in various formats, such as displaying the schedule data for each day in a calendar format.

[0148] In this embodiment, the user can interact through the schedule entry in the communication application interface of the first communication application to trigger the entry into the schedule display interface to display the schedule display area. This enables efficient synchronization and display of schedule data between the first account and the second account in the first communication application, thereby reducing scheduling conflicts.

[0149] In one embodiment, the communication application interface includes an associated application message entry; the schedule data display method further includes: in response to a trigger operation on the associated application message entry, displaying an associated session area of ​​the second communication application; and in the associated session area, displaying communication messages generated by the second account in the second communication application.

[0150] The associated application message entry is used to trigger entry into the session area of ​​other communication applications associated with the first communication application. Users can interact with the associated application message entry; for example, clicking the associated application message entry will trigger entry into the session area of ​​other communication applications associated with the first communication application. The associated session area is used to display session messages of a second communication application associated with the first communication application.

[0151] Specifically, when a first account in the first communication application is associated with a second account in the second communication application, the second communication application can run as a plugin or sub-application within the first communication application. That is, the communication application interface displayed on the terminal also includes an associated application message entry. Users can trigger interactive operations on this entry, and the terminal responds by displaying the associated session area of ​​the second communication application. This associated session area displays communication messages generated by the second account in the second communication application. In specific applications, the type and display method of the communication messages displayed in the associated session area can be configured according to the second communication application to suit its usage. Users can communicate within the first communication application using their first account within the first communication application's interface, and they can also communicate within the second communication application using a second account associated with the first account in the associated session area.

[0152] In a specific application, such as Figure 7 As shown, in the first communication application logged in with the first account, the session interface of the first communication application is displayed, showing the session messages of the user's conversations through the first account. The user can click the associated application message entry control in the side menu bar. In response to this trigger event, the terminal displays the associated session area, which shows the communication messages generated by the second account in the second communication application. Here, the second communication application is an email application, the second account is an email account, and the associated session area displays the emails of the email account in the email application.

[0153] In this embodiment, the user can interact through the associated application message entry in the communication application interface of the first communication application to trigger entry into the associated session area of ​​the second communication application. The terminal displays the communication messages generated by the second account in the second communication application in the associated session area, thereby realizing the synchronization of communication messages of the second communication application in the first communication application, which is beneficial to improving the processing efficiency of communication messages.

[0154] In one embodiment, displaying schedule data in the schedule display area includes: arranging and displaying schedule data in the schedule display area according to the schedule trigger time of the schedule data associated with the first account; and displaying at least one of the schedule trigger time, schedule content, schedule participants, and schedule trigger location for each schedule data item.

[0155] The schedule trigger time refers to the time at which the schedule is triggered to execute, that is, the scheduled start time of the schedule. For example, if the schedule is a meeting, the schedule trigger time can be the meeting start time. The schedule content can be a description of the specific activities of the schedule. The schedule participants are the members who participate in the schedule. The schedule trigger location is the location where the schedule is triggered to execute, such as the location where the meeting is held.

[0156] Specifically, when displaying schedule data, the terminal arranges the schedule data in the schedule display area according to the schedule trigger time associated with the first account. In a specific application, a calendar can be displayed in the schedule display area, showing the schedule data for each day. For the displayed schedule data, at least one of the following can be shown: schedule trigger time, schedule content, schedule participants, and schedule trigger location. In a specific application, such as... Figure 8 As shown, the calendar is displayed in the schedule display area. For each day in the calendar, the schedule data included in that day is displayed, specifically showing the schedule trigger time and schedule content.

[0157] In this embodiment, the schedule data is arranged and displayed according to the schedule trigger time, and schedule information related to the schedule data is also displayed, which can fully display the synchronized schedule data and ensure the synchronization effect of schedule data.

[0158] In one embodiment, the schedule data display method further includes: displaying schedule filter items in a schedule display area; and, in response to a filter configuration operation triggered in the schedule filter items, displaying schedule data that meets the display conditions specified by the filter configuration operation in the schedule display area.

[0159] The schedule filter option is an interactive element used to filter the displayed schedule data based on conditions. Users can interact with the schedule filter option to trigger the filter configuration operation, so as to configure the display conditions of the schedule data displayed in the schedule display area, and thus flexibly set the displayed schedule data as needed.

[0160] Specifically, the terminal displays schedule filter items in the schedule display area. These filter items can include various filtering conditions such as account, time, location, participants, topic, and type. Users can trigger filter configuration operations within the schedule filter items to configure display conditions. In response to these operations, the terminal displays schedule data that meets the specified display conditions in the schedule display area. Specifically, the terminal determines the user-specified display conditions based on the filter configuration operation, filters the schedule data based on these conditions, selects schedule data that meets the display conditions from the schedule dataset associated with the first account, and displays this data in the schedule display area.

[0161] In this embodiment, the terminal displays schedule data that meets the display conditions in the schedule display area according to the filtering configuration operation triggered by the user in the schedule filter item. This allows for flexible configuration of the synchronized schedule data according to the user's actual needs, expands the applicable scenarios of schedule data processing, and ensures the efficiency of schedule data processing.

[0162] In one embodiment, the schedule data display method further includes: in a first communication application, in response to an association triggering operation for a second communication application, displaying an account association operation area; in response to an account editing operation in the account association operation area, displaying a second account edited by the account editing operation; and in response to an association confirmation operation for the second account, displaying an account association result that associates the first account and the second account.

[0163] The process includes several key elements: **Association Trigger Operation:** This is an operation triggered by the user in the first communication application to associate with the second communication application. For example, the user can interact through an application association entry point to trigger the association. **Account Association Operation Area:** This area is where accounts in the first and second communication applications are associated. **Account Editing Operation:** This is an operation triggered by the user to edit an account in the second communication application. **Association Confirmation Operation:** This is an operation where the user confirms the association between the first and second accounts. For example, this can be generated based on the user clicking a confirmation control. **Account Association Result:** This is the result of establishing the association between the first and second accounts.

[0164] Specifically, a user can associate a first account in a first communication application with a second account in a second communication application to establish an association between the two accounts. The user can trigger an association action in the first application targeting the second application; for example, by clicking the application association entry, the terminal responds by displaying an account association operation area. The user can also trigger an account editing action in the account association operation area to edit the account in the second communication application that they wish to associate. The terminal responds to the user's account editing action in the account association operation area, retrieves the edited second account, and displays it. The user can confirm the association of the edited second account. In response to the user's confirmation, the terminal associates the first and second accounts, establishing an association between them, and displays the account association result, such as a description of a successful association.

[0165] In this embodiment, the user can trigger the association between the second account in the second communication application and the first account in the first communication application. Based on the association between the first account and the second account, the schedule data under different account systems can be synchronously displayed when logging into the first communication application with the first account, thereby achieving efficient synchronization of schedule data and reducing schedule conflicts.

[0166] In one embodiment, in a first communication application, in response to an association triggering operation for a second communication application, displaying an account association operation area includes: in the first communication application, in response to an application control event, displaying an application control area including an application entry for the second communication application; in response to a triggering operation on the application entry in the application control area, displaying an association activation area for the second communication application; in response to an association activation operation triggered in the association activation area, displaying an account association entry for the second communication application; and in response to an association triggering operation on the account association entry, displaying an account association operation area.

[0167] Application control events are events within the first communication application that control various external applications; these events are generated by the user clicking application control controls. The application control area is the area where the user controls external applications within the first communication application. The application control area includes the application entry point for the second communication application, through which the user can access the associated activation area for the second communication application. In the associated activation area, the user can activate the second communication application, thereby activating account association processing between the first and second communication applications. After the user triggers the associated activation operation, the terminal can display the account association entry point for the second communication application. Through this entry point, the user can trigger access to the account association operation area for the second communication application, thus achieving the association processing between the first and second accounts.

[0168] Specifically, a user can trigger application control events within the first communication application. For example, a user can click on an application control control in the first communication application, and the terminal displays an application control area including an entry point for the second communication application. The user can interact with the entry point of the second communication application. In response to the user's triggering operation on the application entry point in the application control area, the terminal displays an associated activation area for the second communication application, where the user can activate the second communication application. In response to the user's associated activation operation in the associated activation area, the terminal displays an account association entry point for the second communication application. The user can interact with this account association entry point, such as clicking on it. In response to the user's association triggering operation on the account association entry point, the terminal displays an account association operation area, where the user can associate a second account in the second application with a first account in the first application.

[0169] In this embodiment, after the user triggers the activation of the account association entry of the second communication application in the first communication application, the user can trigger the association of the second account in the second communication application with the first account in the first communication application. Based on the association relationship between the first account and the second account, the schedule data under different account systems can be synchronously displayed in the first communication application when logged in with the first account, thereby achieving efficient synchronization of schedule data and reducing schedule conflicts.

[0170] This application also provides an application scenario in which the above-described schedule data processing method and schedule data display method are applied. Specifically, the application of the schedule data processing method and schedule data display method in this application scenario is as follows:

[0171] Currently, in the field of calendar applications, the common practice is to bind email accounts to clients for data retrieval, and then write received schedules to the local terminal via EAS (Exchange ActiveSync) or CalDAV protocol email servers. In application calendars or calendar applications across various systems, email accounts from different email service providers can be added. The terminal then selects the appropriate synchronization method through the chosen calendar service provider to synchronize schedule data with the email service provider's server, and the synchronized schedule data is stored locally on the terminal. However, in scenarios where users have multiple devices, especially when there are differences between devices with different account systems (e.g., PCs and mobile devices, or different operating systems), users need to authorize and bind accounts on each different platform, making it impossible to achieve synchronized roaming of schedule data. Furthermore, the inability to unify synchronized schedule data from multiple email services to a single cloud makes it difficult to accurately determine the availability of participants when scheduling meeting invitations, easily leading to scheduling conflicts. Based on this, this embodiment provides a technical solution for synchronizing schedules between a first communication application and a second communication application. Specifically, it automatically synchronizes meeting schedules received via email or event schedules created in the email application to various terminals of the first communication application, such as to various terminals of an enterprise communication application. After the enterprise communication application is automatically bound to the email application, the schedule data in the email application is automatically associated with the backend of the enterprise communication application, thereby providing comprehensive data support for calculating user availability.

[0172] Specifically, in this embodiment, the first communication application can be an enterprise communication application, and the second communication application can be an enterprise email application. The enterprise email application can run as a plugin within the enterprise communication application, thereby enabling the communication application functions of the enterprise email application, such as sending and receiving emails, within the enterprise communication application. Figure 9 As shown, linking the enterprise communication application and the enterprise email application can be achieved by binding a first account in the enterprise communication application to a second account in the enterprise email application. This allows the enterprise communication application to display email messages from the enterprise email application. Figure 10 As shown, calendar data belonging to the second account in the enterprise email application can also be synchronized and displayed in the calendar of the enterprise communication application. That is, the enterprise communication application can display calendar data from both the first and second accounts. Furthermore, as... Figure 11 As shown, in enterprise communication applications, enterprise application management can be triggered to manage and control external applications. The external application management interface includes entry points for various external applications, specifically the enterprise email application entry point. Users can manage the enterprise email application by clicking on this entry point. Figure 12As shown, after entering the management interface of the enterprise email application, authorized users can activate the association of the enterprise email application in the management interface. This allows users to associate the first account with the second account in the email application in the enterprise communication application, thereby enabling the synchronization of schedule data in the email application through the enterprise communication application.

[0173] Furthermore, when automatically binding enterprise communication applications and enterprise email applications to schedules, the enterprise communication application can be linked. Specifically, after an enterprise activates its enterprise email application, the schedule in the enterprise communication application will be associated with the enterprise email application by default. After a user enters their email account and password in the enterprise communication application client, the client can then receive the schedule and emails from the enterprise email. When a user's enterprise email receives a schedule invitation email, the enterprise email application's backend extracts the corresponding schedule event and writes the obtained schedule data to the user's schedule storage in the enterprise communication application. When a user replies to a schedule invitation email in the enterprise email application client, the client requests a reply from the enterprise email application's backend. The backend then sends a response email to the corresponding organizer and updates the user's own schedule storage status. When a user creates a single schedule event in the enterprise email application client, the client initiates a write operation to the enterprise email application's backend. After logical processing, the backend writes the schedule data to the enterprise communication application's backend storage, thus achieving the integration of schedule data from the enterprise email application.

[0174] Furthermore, such as Figure 13 As shown, when synchronizing calendar data from the enterprise email application within the enterprise communication application, other email services can send calendar invitation emails to the enterprise email application's backend. The enterprise email application's backend performs email logic processing on these invitation emails, such as calendar analysis, to obtain calendar data, which is then written to the enterprise communication application's backend. For the enterprise communication application's backend, when a new calendar event is written or its status changes, the backend pushes a control message to the enterprise communication application's client to activate the client and proactively synchronize calendar data. Additionally, the enterprise communication application's client can also trigger proactive calendar data synchronization when a user actively accesses the calendar application. The enterprise communication application's client and backend use a private protocol to incrementally retrieve the user's calendar and calendar data by comparing sequence numbers (seq), enabling calendar data synchronization on the enterprise communication application's client. The calendar data from the enterprise email application and the enterprise communication application are integrated in the same storage. When the enterprise communication application's client retrieves data, it will simultaneously retrieve all calendar data that meets the specified conditions, thus achieving calendar data synchronization across different account systems.

[0175] In addition, such as Figure 14 As shown, after the enterprise email application's calendar is automatically bound, to avoid duplicate calendars, it's necessary to unbind calendars from locally linked accounts with the same name. When the enterprise communication application client actively binds an email address, it sends a list of locally bound email addresses to the enterprise communication application's backend, periodically querying the backend. The backend determines if the email address is already bound to the enterprise account and issues an unbinding command accordingly. The enterprise communication application's backend retrieves the list of email addresses bound to the current account from the enterprise email application's backend, identifies the email addresses that need to be unbound, and then issues an unbinding command to unbind the locally linked email addresses. To handle situations where an enterprise email account is later activated after an already bound email address, the enterprise communication application client can also include the locally bound email address at specific times to query the backend for unbinding. Upon receiving the unbinding command, the enterprise communication application client stops calendar collection and synchronizes calendar data through the enterprise communication application's calendar synchronization process, ensuring the uniqueness of the calendar data.

[0176] In this embodiment, taking enterprise communication applications as an example, a feasible approach is explored for the automatic binding of office applications and email. This effectively unifies office products and email products onto the same calendar client, providing users with effective assistance in managing personal affairs and work schedules, facilitating efficient synchronization of schedule data, and reducing scheduling conflicts.

[0177] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0178] Based on the same inventive concept, this application also provides a schedule data processing apparatus for implementing the schedule data processing method described above, and a schedule data display apparatus for implementing the schedule data display method described above. The solution provided by this apparatus is similar to the solution described in the above method; therefore, the specific limitations of one or more schedule data processing apparatus or schedule data display apparatus embodiments provided below can be found in the limitations of the schedule data processing method or schedule data display method described above, and will not be repeated here.

[0179] In one embodiment, such as Figure 15 As shown, a schedule data processing device 1500 is provided, including: a schedule data receiving module 1502, a schedule data fusion module 1504, and a schedule data synchronization module 1506, wherein:

[0180] The schedule data receiving module 1502 is used to receive external schedule data belonging to the second account sent by the communication application server of the second communication application when there is an association between the first account in the first communication application and the second account in the second communication application.

[0181] The schedule data fusion module 1504 is used to merge external schedule data into the schedule dataset associated with the first account based on the association relationship.

[0182] The schedule data synchronization module 1506 is used to synchronize the latest schedule dataset associated with the first account to the terminal logged into the first communication application with the first account in response to the schedule data synchronization event.

[0183] In one embodiment, the schedule data fusion module 1504 includes a first account determination module, a dataset determination module, and a data fusion module; wherein: the first account determination module is used to determine a first account in a first communication application based on the association relationship; the dataset determination module is used to determine the schedule dataset associated with the first account from the schedule dataset of the first communication application; and the data fusion module is used to fuse external schedule data into the schedule dataset associated with the first account.

[0184] In one embodiment, the schedule data fusion module 1504 includes a login terminal determination module and a latest dataset synchronization module; wherein: the login terminal determination module is used to determine the terminal that logs into the first communication application with the first account when the schedule dataset associated with the first account triggers an update; the latest dataset synchronization module is used to synchronize the latest schedule dataset associated with the first account to the terminal.

[0185] In one embodiment, the latest dataset synchronization module includes a prompt message generation module, a prompt message distribution module, and a synchronization request response module; wherein: the prompt message generation module is used to generate a synchronization prompt message based on the calendar dataset associated with the first account; the prompt message distribution module is used to send the synchronization prompt message to the terminal to instruct the terminal to send a calendar data synchronization request based on the synchronization prompt message; and the synchronization request response module is used to send the latest calendar dataset associated with the first account to the terminal based on the calendar data synchronization request sent by the terminal.

[0186] In one embodiment, the schedule data synchronization module 1506 includes a synchronization request account determination module, a synchronization request account matching module, and a schedule dataset distribution module; wherein: the synchronization request account determination module is used to determine the synchronization request account logged into the first communication application in the terminal according to the schedule data synchronization request when a schedule data synchronization request is received from the terminal; the synchronization request account matching module is used to obtain the latest schedule dataset associated with the first account when the synchronization request account is the first account; and the schedule dataset distribution module is used to send the latest schedule dataset associated with the first account to the terminal for schedule data synchronization processing on the terminal.

[0187] In one embodiment, the schedule data synchronization module 1506 is further configured to determine the latest schedule dataset associated with the first account; determine the schedule data to be synchronized for the first account from the latest schedule dataset; and synchronize the schedule data to be synchronized to the terminal logged into the first communication application with the first account.

[0188] In one embodiment, the schedule data synchronization module 1506 is further configured to determine the historical synchronization sequence number in the terminal logged into the first communication application with the first account; determine the sequence number to be synchronized based on the historical synchronization sequence number and the latest schedule dataset; and determine the schedule data to be synchronized for the first account from the latest schedule dataset according to the sequence number to be synchronized.

[0189] In one embodiment, the schedule data synchronization module 1506 includes a filtering condition determination module, a filtering processing module, and a schedule data synchronization module; wherein: the filtering condition determination module is used to determine the schedule data filtering conditions that match the first account; the filtering processing module is used to determine the schedule data to be synchronized from the latest schedule data set associated with the first account according to the schedule data filtering conditions; and the schedule data synchronization module is used to synchronize the schedule data to be synchronized to the terminal that logs in to the first communication application with the first account.

[0190] In one embodiment, the system further includes a local associated account determination module, a local associated account analysis module, and a local synchronization cancellation module; wherein: the local associated account determination module is used to determine the local associated account in the terminal that logs into the first communication application with the first account; the local associated account analysis module is used to generate a schedule synchronization cancellation message for the second account when it is determined that the local associated account includes the second account; and the local synchronization cancellation module is used to send the schedule synchronization cancellation message to the terminal to instruct the terminal to cancel the schedule data synchronization processing for the second account through the communication application server of the second communication application.

[0191] In one embodiment, the system further includes a communication message receiving module, a schedule data analysis module, and a schedule data generation module; wherein: the communication message receiving module is used to receive communication messages associated with the second account through the second communication application; the schedule data analysis module is used to perform schedule data analysis on the communication message when the communication message is a schedule message type, and obtain the schedule data analysis result; the schedule data generation module is used to generate external schedule data belonging to the second account based on the schedule data analysis result.

[0192] In one embodiment, the schedule data analysis module includes a message type determination module and a schedule event extraction module; wherein: the message type determination module is used to determine the message type of the communication message; the schedule event extraction module is used to extract schedule events from the communication message when the message type is a schedule message type, and obtain the schedule event extraction result; the schedule data generation module is also used to generate external schedule data belonging to the second account according to the schedule event extraction result and in accordance with the schedule data format.

[0193] In one embodiment, the system further includes a new schedule module, configured to, in response to a schedule creation event in the second communication application, obtain new schedule information obtained based on the schedule creation event; and generate external schedule data belonging to the second account based on the new schedule information.

[0194] In one embodiment, the system further includes a conflict analysis module, an abnormal data determination module, and an abnormal notification module; wherein: the conflict analysis module is used to perform a schedule conflict analysis on the schedule dataset associated with the first account and obtain a schedule conflict analysis result; the abnormal data determination module is used to determine the abnormal schedule data with a schedule conflict when the schedule conflict analysis result indicates that a schedule conflict exists; and the abnormal notification module is used to generate a schedule abnormal notification message based on the abnormal schedule data and send the schedule abnormal notification message to the terminal that logs into the first communication application with the first account.

[0195] In one embodiment, such as Figure 16 As shown, a schedule data display device 1600 is provided, including: a schedule display trigger module 1602 and a schedule data display module 1604, wherein:

[0196] The schedule display trigger module 1602 is used to display the schedule display area in response to the schedule display trigger event in the first communication application logged in with the first account;

[0197] The schedule data display module 1604 is used to display schedule data in the schedule display area; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset integrates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated.

[0198] In one embodiment, the schedule display trigger module 1602 includes an application interface display module, a schedule entry trigger module, and a schedule display interface display module; wherein: the application interface display module is used to display the communication application interface of the first communication application logged in with the first account, the communication application interface including a schedule entry; the schedule entry trigger module is used to enter the schedule display interface of the first account in response to the trigger operation of the schedule entry; the schedule display interface display module is used to display the schedule display area in the schedule display interface.

[0199] In one embodiment, the communication application interface includes an associated application message entry; it also includes an associated session area display module, which displays the associated session area of ​​the second communication application in response to a trigger operation on the associated application message entry; and displays communication messages generated by the second account in the second communication application in the associated session area.

[0200] In one embodiment, the schedule data display module 1604 is further configured to arrange and display schedule data in the schedule display area according to the schedule trigger time of the schedule data associated with the first account; and to display at least one of the schedule trigger time, schedule content, schedule participants, and schedule trigger location for each schedule data.

[0201] In one embodiment, the system further includes a schedule filter item display module and a filter result display module; wherein: the schedule filter item display module is used to display schedule filter items in the schedule display area; the filter result display module is used to display schedule data that meets the display conditions specified by the filter configuration operation in the schedule display area in response to a filter configuration operation triggered in the schedule filter item.

[0202] In one embodiment, the system further includes an association trigger operation response module, an account editing response module, and an association confirmation module; wherein: the association trigger operation response module is used to display an account association operation area in response to an association trigger operation for a second communication application in a first communication application; the account editing response module is used to display a second account edited by the account editing operation in response to an account editing operation in the account association operation area; and the association confirmation module is used to display the account association result of associating the first account and the second account in response to an association confirmation operation for the second account.

[0203] In one embodiment, the association trigger operation response module includes an application control event response module, an application entry trigger response module, an association activation response module, and an association trigger response module; wherein: the application control event response module is used to display an application control area including an application entry of a second communication application in response to an application control event in the first communication application; the application entry trigger response module is used to display an association activation area of ​​the second communication application in response to a trigger operation on the application entry in the application control area; the association activation response module is used to display an account association entry of the second communication application in response to an association activation operation triggered in the association activation area; and the association trigger response module is used to display an account association operation area in response to an association trigger operation on the account association entry.

[0204] Each module in the aforementioned schedule data processing device and schedule data display device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0205] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 17As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores schedule data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a schedule data processing method.

[0206] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 18 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a schedule data display method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0207] Those skilled in the art will understand that Figure 17 and Figure 18The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0208] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0209] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0210] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including 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 steps in the above method embodiments.

[0211] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0212] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, etc., and are not limited to these.

[0213] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification. The above embodiments only illustrate several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of this application. It should be noted that for those skilled in the art, several modifications and improvements can be made without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing schedule data, characterized in that, The method, applied to a first communication application server corresponding to a first communication application, includes: When a first account in the first communication application is associated with a second account in the second communication application, external schedule data belonging to the second account is received from the communication application server of the second communication application. The first communication application and the second communication application are different types of communication applications and have different account systems. The association between the first account and the second account indicates that the first account can receive communication messages from the second account in the second communication application through the first account. The external schedule data includes schedule data actively created by the second account in the second communication application and / or schedule data generated corresponding to schedule invitations received by the second account in the second communication application. Based on the aforementioned association, the first account is obtained by querying the first communication application using the second account; From the calendar dataset of the first communication application, determine the calendar dataset belonging to the first account; The external schedule data is merged into the schedule dataset belonging to the first account according to the schedule data format of the schedule dataset belonging to the first account; the schedule dataset is used to store the schedule data belonging to the first account. In response to a schedule data synchronization event, determine the schedule data filtering conditions configured by the first account that match the first account, wherein the schedule data filtering conditions are for the schedule data that needs to be synchronized. According to the aforementioned schedule data filtering criteria, the schedule data to be synchronized is obtained from the latest schedule dataset associated with the first account. The schedule data to be synchronized is synchronized to the terminal that is logged into the first communication application with the first account; The local associated account in the terminal that logs into the first communication application with the first account is determined. The local associated account is an account that belongs to a different application account system than the first account. The schedule data belonging to the local associated account can be collected by the terminal. When it is determined that the local associated account includes the second account, a schedule synchronization cancellation message is generated for the second account; The schedule synchronization cancellation message is sent to the terminal to instruct the terminal to cancel the communication application server through the second communication application, perform schedule data synchronization processing for the second account, and perform schedule data synchronization processing on the external schedule data of the second account locally.

2. The method according to claim 1, characterized in that, The method further includes: When the calendar dataset associated with the first account is updated, it is determined that the terminal logged into the first communication application with the first account is used. The latest schedule dataset associated with the first account is synchronized to the terminal.

3. The method according to claim 2, characterized in that, The step of synchronizing the latest schedule dataset associated with the first account to the terminal includes: Generate a synchronization notification message based on the schedule dataset associated with the first account; The synchronization prompt message is sent to the terminal to instruct the terminal to send a schedule data synchronization request based on the synchronization prompt message; Based on the schedule data synchronization request sent by the terminal, the latest schedule dataset associated with the first account is sent to the terminal.

4. The method according to claim 1, characterized in that, The method further includes: When a calendar data synchronization request is received from a terminal, the synchronization request account logged into the first communication application in the terminal is determined based on the calendar data synchronization request. When the synchronization request account is the first account, obtain the latest schedule dataset associated with the first account; The latest schedule dataset associated with the first account is sent to the terminal for schedule data synchronization processing on the terminal.

5. The method according to claim 1, characterized in that, The method further includes: Determine the latest schedule dataset associated with the first account; From the latest schedule dataset, determine the schedule data to be synchronized for the first account; The schedule data to be synchronized is synchronized to the terminal logged into the first communication application with the first account.

6. The method according to claim 5, characterized in that, The step of determining the schedule data to be synchronized for the first account from the latest schedule dataset includes: Determine the historical synchronization sequence number in the terminal that logged into the first communication application with the first account; Based on the historical synchronization sequence number and the latest schedule dataset, determine the sequence number to be synchronized; Based on the synchronization sequence number, determine the synchronization schedule data for the first account from the latest schedule dataset.

7. The method according to any one of claims 1 to 6, characterized in that, The external schedule data is obtained through a schedule data generation step, which includes: Receive communication messages associated with the second account through the second communication application; When the communication message is a schedule message type, schedule data analysis is performed on the communication message to obtain schedule data analysis results; Based on the analysis results of the schedule data, external schedule data belonging to the second account is generated.

8. The method according to claim 7, characterized in that, When the communication message is a schedule message type, schedule data analysis is performed on the communication message to obtain schedule data analysis results, including: Determine the message type of the communication message; When the message type is a schedule message type, schedule events are extracted from the communication message to obtain the schedule event extraction result; The step of generating external schedule data belonging to the second account based on the schedule data analysis results includes: Based on the extracted schedule events, external schedule data belonging to the second account is generated according to the schedule data format.

9. The method according to any one of claims 1 to 6, characterized in that, The external schedule data is obtained through a schedule data generation step, which includes: In response to a schedule creation event in the second communication application, obtain newly created schedule information based on the schedule creation event; Based on the newly created schedule information, external schedule data belonging to the second account is generated.

10. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Perform a schedule conflict analysis on the schedule dataset associated with the first account to obtain the schedule conflict analysis results; When the schedule conflict analysis result indicates that a schedule conflict exists, abnormal schedule data with a schedule conflict is identified. A schedule error message is generated based on the abnormal schedule data, and the schedule error message is sent to the terminal that is logged into the first communication application with the first account.

11. A method for displaying schedule data, characterized in that, The method, applied to a first terminal having a first communication application installed, includes: In the first communication application logged in with the first account, in response to the calendar display trigger event, the calendar display area is displayed; The schedule display area displays schedule data; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset integrates external schedule data belonging to the second account in the second communication application, and the first account and the second account are associated; the first communication application and the second communication application are different types of communication applications and have different account systems; the association between the first account and the second account indicates that the first account can receive communication messages from the second account in the second communication application through the first account; the schedule dataset is used to store schedule data belonging to the first account; the external schedule data includes schedule data actively created by the second account in the second communication application, and / or schedule data generated corresponding to schedule invitations received by the second account in the second communication application; the external schedule data is integrated into the schedule dataset according to the schedule data format belonging to the schedule dataset; Schedule filter options are displayed in the schedule display area; In response to a filter configuration operation triggered in the schedule filter item, schedule data that meets the display conditions specified by the filter configuration operation is displayed in the schedule display area. The schedule data is obtained by filtering the schedule dataset according to the display conditions specified by the filter configuration operation. Identify the local associated account in the first terminal. The local associated account is an account that belongs to a different application account system than the first account. The schedule data belonging to the local associated account can be collected by the first terminal. When it is determined that the local associated account includes the second account, the communication application server through the second communication application is disconnected, the schedule data synchronization processing is performed for the second account, and the schedule data synchronization processing of the external schedule data of the second account is performed locally.

12. The method according to claim 11, characterized in that, In the first communication application logged in with the first account, in response to a calendar display trigger event, a calendar display area is displayed, including: Displays the communication application interface of the first communication application logged in with the first account, the communication application interface including a schedule entry; In response to the triggering operation of the schedule entry, the schedule display interface of the first account is entered; The schedule display interface shows the schedule display area.

13. The method according to claim 12, characterized in that, The communication application interface includes an entry point for associated application messages; the method further includes: In response to a trigger operation on the associated application message entry, the associated session area of ​​the second communication application is displayed; In the associated session area, communication messages generated by the second account in the second communication application are displayed.

14. The method according to claim 13, characterized in that, The display of schedule data in the schedule display area includes: In the schedule display area, the schedule data is arranged and displayed according to the schedule trigger time of the schedule data associated with the first account; For each of the aforementioned schedule data entries, at least one of the following is displayed: schedule trigger time, schedule content, schedule participants, and schedule trigger location.

15. The method according to any one of claims 11 to 14, characterized in that, The method further includes: In the first communication application, in response to the associated trigger operation for the second communication application, the account association operation area is displayed; In response to an account editing operation in the account association operation area, the second account edited by the account editing operation is displayed; In response to the confirmation operation for the association of the second account, the account association result of associating the first account and the second account is displayed.

16. The method according to claim 15, characterized in that, In the first communication application, in response to an association trigger operation for the second communication application, an account association operation area is displayed, including: In the first communication application, in response to an application control event, an application control area including the application entry of the second communication application is displayed; In response to a trigger operation on the application entry in the application control area, the associated activation area of ​​the second communication application is displayed; In response to an association activation operation triggered in the association activation area, the account association entry for the second communication application is displayed; In response to the associated trigger operation for the account association entry, the account association operation area is displayed.

17. A schedule data processing device, characterized in that, The device includes: The schedule data receiving module is used to receive external schedule data belonging to the second account sent by the communication application server of the second communication application when there is an association between a first account in the first communication application and a second account in the second communication application. The first communication application and the second communication application are different types of communication applications and have different account systems. The association between the first account and the second account indicates that the first account can receive communication messages from the second account in the second communication application through the first account in the first communication application. The external schedule data includes schedule data actively created by the second account in the second communication application and / or schedule data generated corresponding to schedule invitations received by the second account in the second communication application. The schedule data fusion module is used to query the first account from the first communication application based on the association relationship and through the second account; determine the schedule dataset belonging to the first account from the schedule dataset of the first communication application; and fuse the external schedule data into the schedule dataset belonging to the first account according to the schedule data format of the schedule dataset belonging to the first account; the schedule dataset is used to store the schedule data belonging to the first account. The schedule data synchronization module is used to respond to a schedule data synchronization event, determine the schedule data filtering conditions configured by the first account that match the first account, wherein the schedule data filtering conditions are for the schedule data that needs to be synchronized; according to the schedule data filtering conditions, filter the latest schedule data associated with the first account to obtain the schedule data to be synchronized; and synchronize the schedule data to be synchronized to the terminal logged in to the first communication application with the first account. The local associated account determination module is used to determine the local associated account in the terminal that logs in to the first communication application with the first account. The local associated account is an account that belongs to a different application account system than the first account. The schedule data belonging to the local associated account can be collected by the terminal. The local associated account analysis module is used to generate a schedule synchronization cancellation message for the second account when it is determined that the local associated account includes the second account. The local synchronization cancellation module is used to send the schedule synchronization cancellation message to the terminal to instruct the terminal to cancel the schedule data synchronization processing for the second account through the communication application server of the second communication application, and to directly perform schedule data synchronization processing on the external schedule data of the second account locally.

18. The apparatus according to claim 17, characterized in that, The schedule data synchronization module is further configured to determine the terminal logged into the first communication application with the first account when the schedule dataset associated with the first account is updated; and synchronize the latest schedule dataset associated with the first account to the terminal.

19. The apparatus according to claim 18, characterized in that, The schedule data synchronization module is further configured to generate a synchronization prompt message based on the schedule dataset associated with the first account; send the synchronization prompt message to the terminal to instruct the terminal to send a schedule data synchronization request based on the synchronization prompt message; and send the latest schedule dataset associated with the first account to the terminal based on the schedule data synchronization request sent by the terminal.

20. The apparatus according to claim 17, characterized in that, The schedule data synchronization module is further configured to, when receiving a schedule data synchronization request sent by a terminal, determine the synchronization request account logged into the first communication application in the terminal according to the schedule data synchronization request; when the synchronization request account is the first account, obtain the latest schedule dataset associated with the first account; The latest schedule dataset associated with the first account is sent to the terminal for schedule data synchronization processing on the terminal.

21. The apparatus according to claim 17, characterized in that, The schedule data synchronization module is further configured to determine the latest schedule dataset associated with the first account; and determine the schedule data to be synchronized for the first account from the latest schedule dataset. The schedule data to be synchronized is synchronized to the terminal logged into the first communication application with the first account.

22. The apparatus according to claim 21, characterized in that, The schedule data synchronization module is further configured to determine the historical synchronization sequence number in the terminal logged into the first communication application with the first account; and determine the sequence number to be synchronized based on the historical synchronization sequence number and the latest schedule dataset. Based on the synchronization sequence number, determine the synchronization schedule data for the first account from the latest schedule dataset.

23. The apparatus according to any one of claims 17 to 22, characterized in that, The device further includes: A communication message receiving module is used to receive communication messages associated with the second account through the second communication application; The schedule data analysis module is used to perform schedule data analysis on the communication message when the communication message is a schedule message type, and obtain the schedule data analysis results; The schedule data generation module is used to generate external schedule data belonging to the second account based on the schedule data analysis results.

24. The apparatus according to claim 23, characterized in that, The schedule data analysis module is also used to determine the message type of the communication message; when the message type is a schedule message type, the communication message is used to extract schedule events to obtain the schedule event extraction result. The schedule data generation module is also used to generate external schedule data belonging to the second account according to the schedule event extraction results and in accordance with the schedule data format.

25. The apparatus according to any one of claims 17 to 22, characterized in that, The device further includes: A new schedule module is used to respond to a schedule creation event in the second communication application, obtain new schedule information based on the schedule creation event, and generate external schedule data belonging to the second account based on the new schedule information.

26. The apparatus according to any one of claims 17 to 22, characterized in that, The device further includes: The conflict analysis module is used to perform schedule conflict analysis on the schedule dataset associated with the first account and obtain the schedule conflict analysis results. An abnormal data determination module is used to determine abnormal schedule data with schedule conflicts when the schedule conflict analysis result indicates that there are schedule conflicts. An error notification module is used to generate an error notification message based on the error schedule data and send the error notification message to the terminal that is logged into the first communication application with the first account.

27. A schedule data display device, characterized in that, The device includes: The schedule display trigger module is used to display the schedule display area in response to the schedule display trigger event in the first communication application logged in with the first account; A schedule data display module is used to display schedule data in the schedule display area; the displayed schedule data belongs to the latest schedule dataset associated with the first account; the schedule dataset integrates external schedule data belonging to a second account in a second communication application, and the first account and the second account are associated; the first communication application and the second communication application are different types of communication applications and have different account systems; the association between the first account and the second account indicates that the first account can receive communication messages from the second account in the second communication application through the first account; the schedule dataset is used to store schedule data belonging to the first account; the external schedule data includes schedule data actively created by the second account in the second communication application, and / or schedule data generated corresponding to schedule invitations received by the second account in the second communication application; the external schedule data is integrated into the schedule dataset according to the schedule data format belonging to the schedule dataset; A schedule filter display module is used to display schedule filter items in the schedule display area; The filtering result display module is used to respond to a filtering configuration operation triggered in the schedule filtering item, and to display schedule data that meets the display conditions specified by the filtering configuration operation in the schedule display area. The schedule data is obtained by filtering the schedule dataset according to the display conditions specified by the filtering configuration operation. The device is also used to determine the local associated account in the first terminal. The local associated account is an account that belongs to a different application account system than the first account. The schedule data belonging to the local associated account can be collected by the first terminal. When it is determined that the local associated account includes the second account, the communication application server through the second communication application is disconnected, the schedule data synchronization processing is performed for the second account, and the schedule data synchronization processing of the external schedule data of the second account is performed locally.

28. The apparatus according to claim 27, characterized in that, The schedule data display module is also used to display the communication application interface of the first communication application logged in with the first account, the communication application interface including a schedule entry; in response to a trigger operation on the schedule entry, the schedule display interface of the first account is entered. The schedule display interface shows the schedule display area.

29. The apparatus according to claim 28, characterized in that, The communication application interface includes an entry point for associated application messages; the device further includes: The associated session area display module is used to display the associated session area of ​​the second communication application in response to a trigger operation on the associated application message entry; in the associated session area, communication messages generated by the second account in the second communication application are displayed.

30. The apparatus according to claim 27, characterized in that, The schedule data display module is also used to arrange and display the schedule data in the schedule display area according to the schedule trigger time of the schedule data associated with the first account; For each of the aforementioned schedule data entries, at least one of the following is displayed: schedule trigger time, schedule content, schedule participants, and schedule trigger location.

31. The apparatus according to any one of claims 27 to 30, characterized in that, The device further includes: The association trigger operation response module is used to display the account association operation area in the first communication application in response to the association trigger operation for the second communication application. The account editing response module is used to respond to the account editing operation in the account association operation area and display the second account edited by the account editing operation; The association confirmation module is used to respond to the association confirmation operation of the second account and display the account association result of associating the first account and the second account.

32. The apparatus according to claim 31, characterized in that, The associated trigger operation response module is also used to display an application control area including the application entry of the second communication application in response to an application control event in the first communication application. In response to a trigger operation on the application entry in the application control area, the associated activation area of ​​the second communication application is displayed; In response to an association activation operation triggered in the association activation area, the account association entry for the second communication application is displayed; In response to the associated trigger operation for the account association entry, the account association operation area is displayed.

33. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 16.

34. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 16.

35. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 16.

Images