Schedule synchronization method and apparatus, computer device, and storage medium

Abstract

The application relates to a schedule synchronization method and device, computer equipment and a storage medium. The method comprises the following steps: displaying a configuration interface of a first application, the first application being an application supporting a standard protocol; acquiring an open account based on the configuration interface, the open account being a virtual account corresponding to the standard protocol and created in a second application supporting a private protocol; and in response to a schedule display operation, displaying a first synchronized schedule through the first application, the first synchronized schedule being obtained by updating original schedules of the first application based on to-be-synchronized schedule data related to a private domain account corresponding to the open account in the second application, the private domain account being a real account corresponding to the private protocol in the second application. The method can synchronize schedules in different applications.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer device, and storage medium for synchronizing schedules. Background Technology

[0002] With the development of science and technology, more and more people are using mobile devices to manage their schedules. Schedule management involves arranging daily tasks and tasks on dates and keeping an effective record to facilitate the management of daily work and tasks, and to achieve the purpose of work reminders.

[0003] Therefore, schedule management is becoming increasingly important in modern society. Currently, many users typically use multiple different applications to record their schedules, such as the built-in calendar app on Android and the schedule recording function in group chat applications. Therefore, unifying the schedules across these applications is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, computer device, and storage medium that can uniformly synchronize schedules in various applications to address the aforementioned technical problems.

[0005] A schedule synchronization method, the method comprising:

[0006] The configuration interface of the first application is displayed. The first application is an application that supports standard protocols.

[0007] Obtain the open account collected based on the configuration interface. The open account is a virtual account created in the second application that supports the private protocol and corresponds to the standard protocol.

[0008] In response to the schedule display operation, the first synchronized schedule that has been synchronized is displayed through the first application. The first synchronized schedule is obtained by updating the original schedule of the first application based on the schedule data to be synchronized related to the private domain account corresponding to the open account in the second application. The private domain account is the real account in the second application corresponding to the private protocol.

[0009] A schedule synchronization device, the device comprising:

[0010] The configuration display module is used to display the configuration interface of the first application, which is an application that supports standard protocols;

[0011] The acquisition module is used to acquire open accounts based on the configuration interface. The open accounts are virtual accounts created in the second application that supports private protocols and correspond to the standard protocol.

[0012] The first synchronization module is used to respond to the schedule display operation and display the synchronized first synchronized schedule through the first application. The first synchronized schedule is obtained by updating the original schedule of the first application based on the schedule data to be synchronized related to the private domain account corresponding to the open account in the second application. The private domain account is the real account in the second application corresponding to the private protocol.

[0013] In one embodiment, the first synchronization module is further configured to, in response to a schedule display operation, generate a schedule synchronization request based on the open account; send the schedule synchronization request to the second application, wherein the schedule synchronization request is used to instruct the second application to return the schedule data to be synchronized related to the private domain account corresponding to the open account to the first application; receive the schedule data to be synchronized fed back by the second application, and update the original schedule of the first application based on the schedule data to be synchronized, thereby obtaining a first synchronized schedule and displaying it.

[0014] In one embodiment, the first synchronization module is further configured to generate an authentication request based on the open account and the authorization code, and send the authentication request to the second application via the domain name address; wherein the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; receive the verification result returned by the second application, and when the verification result indicates that the verification is successful, determine the account-related information, and generate a schedule synchronization request based on the account-related information.

[0015] In one embodiment, the first synchronization module is further configured to, in response to a schedule display operation, obtain the schedule data to be synchronized in the first application; generate a schedule synchronization request based on the open account and the schedule data to be synchronized in the first application; and use the schedule data to be synchronized in the first application to update the existing schedule of the second application.

[0016] In one embodiment, the schedule synchronization device is further configured to display the associated interface of the first application, wherein the associated interface displays the application identifier of the second application; in response to the selection operation of the application identifier of the second application, the open account is bound to the login account of the first application.

[0017] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0018] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0019] A computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in any of the schedule synchronization methods provided in the embodiments of this application.

[0020] The aforementioned schedule synchronization method, apparatus, computer equipment, storage medium, and computer program, by displaying the configuration interface of a first application, can collect open accounts based on the displayed configuration interface. The collected open accounts then respond to schedule display operations, displaying the synchronized first schedule through the first application. Since application configuration only requires entering the open account in the configuration interface, the configuration threshold is significantly lowered, improving user experience. Furthermore, by collecting the open account based on the configuration interface, the original schedule of the first application can be updated using the schedule data to be synchronized from the private domain account corresponding to the open account in the second application during the schedule display operation. This allows for the unified integration of schedules from various personal channels, facilitating users' time management through synchronized schedules.

[0021] Furthermore, this application can synchronize schedule data generated within a proprietary protocol system to various first-level applications that support the standard protocol via a standard protocol, thereby unifying schedule data across applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving the memory, processing, and other resources required by additional applications.

[0022] A schedule synchronization method, the method comprising:

[0023] In response to the information display operation of the second application, the configuration information display interface of the second application is displayed; the second application is an application that supports a private protocol;

[0024] The configuration information display interface displays an open account generated based on a private domain account; the private domain account is the real account in the second application corresponding to the private protocol; the open account is a virtual account created in the second application corresponding to the standard protocol, and the open account is used to be passed to the first application so that the first application can generate a schedule synchronization request based on the open account.

[0025] In response to the schedule synchronization request initiated by the first application, the second synchronized schedule is displayed through the second application. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application.

[0026] A schedule synchronization device, the device comprising:

[0027] The interface display module is used to respond to the information display operation of the second application and display the configuration information display interface of the second application; the second application is an application that supports a private protocol;

[0028] The information display module is used to display an open account generated based on a private domain account through the configuration information display interface; the private domain account is a real account in the second application corresponding to the private protocol; the open account is a virtual account created in the second application corresponding to the standard protocol, and the open account is used to be passed to the first application so that the first application can generate a schedule synchronization request based on the open account.

[0029] The second synchronization module is used to respond to the schedule synchronization request initiated by the first application and display the synchronized second synchronized schedule through the second application. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application.

[0030] In one embodiment, the information display module is further configured to determine the virtual account generation rules corresponding to the standard protocol; generate an open account corresponding to the private domain account according to the virtual account generation rules; and display the open account through the configuration information display interface.

[0031] In one embodiment, the schedule synchronization device is further configured to display an authorization code corresponding to the open account in response to a trigger operation on the configuration information display interface; the authorization code is used to transmit to the first application so that the first application can generate an authentication request based on the authorization code.

[0032] In one embodiment, the second synchronization module is further configured to, when receiving a schedule synchronization request sent by the first application, extract the schedule data to be synchronized and account-related information of the first application in the schedule synchronization request; determine the private domain account corresponding to the account-related information; update the original schedule in the second application related to the private domain account using the schedule data to be synchronized in the first application to obtain a second synchronized schedule; and display the second synchronized schedule through the second application.

[0033] In one embodiment, the schedule synchronization request includes a meeting identifier for a canceled meeting. The second synchronization module is further configured to respond to the schedule synchronization request initiated by the first application by canceling the display of meeting information corresponding to the meeting identifier of the canceled meeting through the second application; and triggering the display of message cards on the terminals of the participants in the canceled meeting; wherein the displayed message cards are used to indicate that the meeting has been canceled.

[0034] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0035] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0036] A computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in any of the schedule synchronization methods provided in the embodiments of this application.

[0037] The aforementioned schedule synchronization method, apparatus, computer equipment, storage medium, and computer program, in response to an information display operation, can display a configuration information display interface of a second application. This interface then displays an open account generated based on a private domain account. Users can then configure the first application using the displayed open account, enabling the configured first application to initiate schedule synchronization requests. In response to the schedule synchronization request initiated by the first application, the existing schedules related to the private domain account corresponding to the open account in the second application can be updated based on the schedule data to be synchronized in the first application, resulting in a second synchronized schedule. This second synchronized schedule can then be displayed through the second application, thereby achieving the goal of unifying and integrating personal schedules from various channels, facilitating users' time management through synchronized schedules.

[0038] Furthermore, this application can synchronize schedule data generated within the standard protocol system to various second applications that support proprietary protocols via the standard protocol, thereby unifying schedule data from applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving the memory, processing, and other resources occupied by additional applications.

[0039] A schedule synchronization method, the method comprising:

[0040] In response to a calendar synchronization request sent by a first application that supports the standard protocol, the open account pointed to by the account-related information carried in the calendar synchronization request is determined; wherein, the open account is a virtual account corresponding to the standard protocol created in a second application that supports the private protocol;

[0041] Determine the private domain account corresponding to the open account, wherein the private domain account is the real account in the second application that corresponds to the private protocol;

[0042] Obtain at least one of the schedule data to be synchronized from the first application and the schedule data to be synchronized related to the private domain account in the second application;

[0043] By acquiring the schedule data to be synchronized, the schedules in the first and second applications are synchronized.

[0044] A schedule synchronization device, the device comprising:

[0045] The request-response module is used to respond to a schedule synchronization request sent by a first application that supports the standard protocol, and to determine the open account pointed to by the account-related information carried in the schedule synchronization request; wherein, the open account is a virtual account corresponding to the standard protocol created in a second application that supports the private protocol;

[0046] The account conversion module is used to determine the private domain account corresponding to the open account, wherein the private domain account is the real account in the second application that corresponds to the private protocol;

[0047] The target synchronization module is used to acquire at least one of the schedule data to be synchronized in the first application and the schedule data to be synchronized in the second application related to the private domain account; and to synchronize the schedules in the first application and the second application using the acquired schedule data to be synchronized.

[0048] In one embodiment, the target synchronization module is further configured to, if the schedule synchronization request carries schedule data, use the schedule data carried in the schedule synchronization request as the schedule data to be synchronized in the first application; and update the original schedule related to the private domain account corresponding to the open account in the second application using the schedule data to be synchronized in the first application.

[0049] In one embodiment, the target synchronization module is further configured to, if the schedule synchronization request does not carry schedule data, search for changed schedule data corresponding to the private domain account in the schedule data repository corresponding to the second application; use the found changed schedule data as the schedule data to be synchronized in the second application related to the private domain account; and update the original schedule in the first application using the schedule data to be synchronized in the second application related to the private domain account.

[0050] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0051] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the schedule synchronization methods provided in the embodiments of this application.

[0052] A computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in any of the schedule synchronization methods provided in the embodiments of this application.

[0053] The aforementioned schedule synchronization method, apparatus, computer device, storage medium, and computer program, in response to a schedule synchronization request sent by a first application supporting a standard protocol, can determine the open account pointed to by the account-related information carried in the schedule synchronization request, thereby determining the private domain account corresponding to that open account. By obtaining the private domain account and the schedule synchronization request, at least one type of schedule data to be synchronized can be obtained from the private domain account-related schedule data in the second application and the schedule data to be synchronized from the first application carried in the schedule synchronization request. Based on the obtained schedule data to be synchronized, the schedules in the first and second applications are synchronized, achieving the purpose of integrating personal schedules from various channels together, making it convenient for users to schedule their personal time plans through the synchronized schedules.

[0054] Furthermore, this application can synchronize schedule data generated within a proprietary protocol system to various first applications supporting the standard protocol via a standard protocol, and can also synchronize schedule data generated within a standard protocol system to various second applications supporting the proprietary protocol via a standard protocol, thereby unifying schedule data across applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving memory, processing, and other resources consumed by additional applications. Attached Figure Description

[0055] Figure 1 This is a diagram illustrating the application environment of a schedule synchronization method in one embodiment;

[0056] Figure 2 This is a flowchart illustrating a schedule synchronization method in one embodiment;

[0057] Figure 3 This is a schematic diagram of the configuration interface in one embodiment;

[0058] Figure 4 This is a schematic diagram of a synchronized schedule in one embodiment;

[0059] Figure 5 This is a schematic diagram illustrating the generation of an open account and authorization code in one embodiment;

[0060] Figure 6 This is a schematic diagram illustrating the interaction between the first application and the second application in one embodiment;

[0061] Figure 7 This is a schematic diagram of the associated interface in one embodiment;

[0062] Figure 8 This is a flowchart illustrating the schedule synchronization method in another embodiment;

[0063] Figure 9 This is a schematic diagram of a configuration information display interface in one embodiment;

[0064] Figure 10 This is a schematic diagram illustrating the interaction between the first application and the second application in another embodiment;

[0065] Figure 11 This is a flowchart illustrating the schedule synchronization method in yet another embodiment;

[0066] Figure 12 This is a schematic diagram of the architecture of a schedule synchronization method in one embodiment;

[0067] Figure 13 This is a flowchart illustrating the steps of a schedule synchronization method in a specific embodiment.

[0068] Figure 14 This is a structural block diagram of a schedule synchronization device in one embodiment;

[0069] Figure 15 This is a structural block diagram of the schedule synchronization device in another embodiment;

[0070] Figure 16 This is a structural block diagram of the schedule synchronization device in yet another embodiment;

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

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

[0073] 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.

[0074] Figure 1 This is a diagram illustrating the application environment of a schedule synchronization method in one embodiment. (Refer to...) Figure 1 This schedule synchronization method is applied to a schedule synchronization system 100. The schedule synchronization system 100 includes a terminal 102 and a server 104. The terminal 102 runs a first application supporting a standard protocol and a second application supporting a proprietary protocol. When the first application wants to synchronize its schedule with that of the second application, the first application can generate a schedule synchronization request based on the standard protocol and account-related information associated with the open account, and send the request to the server 104. The server 104 then parses the schedule synchronization request based on the standard protocol to obtain the open account pointed to by the account-related information, and determines the private domain account corresponding to the open account based on the proprietary protocol. The server 104 uses the private domain account to find the schedule data to be synchronized in the second application and returns this data to the first application, allowing the first application to update its existing schedule based on the received data, thereby synchronizing the schedules in both the first and second applications.

[0075] The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal 102 can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, in-vehicle terminal, smart TV, etc., but is not limited to these. The terminal 102 and the server 104 can be directly or indirectly connected via wired or wireless communication. The first application and the second application can run on the same terminal 102 or on different terminals 102. This application does not impose any restrictions.

[0076] 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 the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0077] In one embodiment, such as Figure 2 As shown, a schedule synchronization method is provided, which can be applied to... Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0078] Step S202: Display the configuration interface of the first application, which is an application that supports standard protocols.

[0079] In this context, a standard protocol refers to a standard specification for transmitting and managing information within a network. This protocol is typically recognized or widely accepted within the industry. In this embodiment, the standard protocol may specifically be the Exchange ActiveSync protocol (a Microsoft Exchange synchronization protocol) or the CalDAV protocol (an Internet standard protocol), or other standard protocols. The Exchange ActiveSync protocol allows mobile device users to access their emails, calendars, contacts, and tasks, and this access continues even when working offline. The CalDAV protocol allows clients to access scheduling information on a remote server. A proprietary protocol refers to a specification for transmitting and managing information within a network. This protocol is typically used only within a small scope, such as within a single company.

[0080] Because applications support different protocols, schedule data in applications supporting different protocols can only be updated within their respective applications and cannot be effectively integrated with other applications, making schedule synchronization difficult. For example, when the first application supports a standard protocol and the second application supports a proprietary protocol, the different protocols create a protocol barrier between them. This prevents schedule data in the first application from being updated within the first application, and vice versa, making synchronization impossible. This application addresses this issue by configuring the first application supporting the standard protocol to enable schedule synchronization between the configured application and the second application supporting the proprietary protocol, thus breaking down the protocol barrier.

[0081] The first application supporting the standard protocol can be the calendar built into the terminal system, such as the calendar built into Android or iOS. The second application supporting the proprietary protocol can be an application with scheduling functions, such as a group chat application, a live streaming application, or a meeting room booking application with calendar functionality.

[0082] Specifically, before synchronizing the schedule data of the first application with the schedule data of the second application, the first application needs to be configured accordingly. When configuring the first application, the terminal responds to the user's trigger operation by displaying the configuration interface of the first application. For example, when the first application is the terminal's built-in calendar application, the user can trigger the terminal to display, as shown below. Figure 3 The configuration interface shown includes an open account input box (301), a domain name address input box (302), and an authorization code input box (303). The open account refers to a virtual account created in the second application that supports the proprietary protocol, corresponding to the standard protocol. The domain name address refers to the address of the second application's server; a domain name is the name of a computer or group of computers on the Internet, consisting of a string of names separated by dots, used to locate the computer during data transmission. The authorization code refers to a password created in the second application that matches the open account. Figure 3 A schematic diagram of the configuration interface in one embodiment is shown.

[0083] Step S204: Obtain the open account collected based on the configuration interface. The open account is a virtual account created in the second application that supports the private protocol and corresponds to the standard protocol.

[0084] Specifically, users can enter their open account in the configuration interface of the first application, so that the terminal can obtain the open account collected based on the configuration interface, and then the schedule can be synchronized based on the open account.

[0085] In one embodiment, to bridge the gap between protocols, the second application can obtain a private domain account and generate an open account matching the private domain account according to the virtual account generation rules corresponding to the standard protocol. The user can then input the open account generated by the second application into the configuration interface to complete the information configuration. It is easy to understand that when the second application generates an open account matching the private domain account, it can also bind and store the private domain account and the open account, enabling subsequent schedule synchronization based on the open account and the bound private domain account. Here, the private domain account refers to an account that the second application can recognize. For example, when the second application is a group chat application that supports a private protocol, the private domain account can be the login account used to log in to the group chat application. The virtual account generation rules can vary depending on the standard protocol, and therefore the account format of the open account generated based on different virtual account generation rules can also be different.

[0086] For example, when the standard protocol is based on an email account system, and the information flow in the first application supporting the standard protocol relies entirely on email-formatted accounts, while the private protocol is not based on an email account system, and the information flow in the second application supporting the private protocol relies entirely on login accounts that are not in email format, the second application can convert the login account into an open account in email format. This allows the first application to transmit the schedule data to be synchronized to the second application through the open account in email format. The second application can then identify the private domain account corresponding to the open account and perform schedule synchronization based on the private domain account and the received schedule data to be synchronized. As another example, when the standard protocol is based on a mobile phone number system, and the information flow in the first application supporting the standard protocol relies entirely on accounts in mobile phone number format, the second application can convert the private domain account into an open account in mobile phone number format.

[0087] Step S206: In response to the schedule display operation, the first synchronized schedule that has been synchronized is displayed through the first application. The first synchronized schedule is obtained by updating the original schedule of the first application based on the schedule data to be synchronized related to the private domain account corresponding to the open account in the second application. The private domain account is the real account corresponding to the private protocol in the second application.

[0088] Specifically, when the open account is entered into the configuration interface, the user can trigger the first application on the terminal to display the schedule. The schedule displayed at this time is the first synchronized schedule. For example, refer to... Figure 4The terminal can respond to a user's calendar display operation for a first application by displaying a first calendar display interface 401 in the first application, wherein the first calendar display interface shows the synchronized first calendar. Furthermore, the terminal can also respond to a calendar display operation for a second application by displaying a second calendar display interface 402 in the second application, wherein the second calendar display interface shows the synchronized second calendar, and the first synchronized calendar displayed in the first calendar display interface and the second synchronized calendar displayed in the second calendar display interface may be the same. Figure 4 A schematic diagram of a synchronized schedule is shown in one embodiment.

[0089] In one embodiment, a user can trigger the schedule display operation by exiting the configuration interface. The first application will then display a first schedule display interface after the user exits the configuration interface, showing the synchronized first schedule. Alternatively, the user can trigger the schedule display operation by re-entering the first application. Upon re-entering the first application, the terminal will then display the first schedule display interface, showing the synchronized first schedule.

[0090] In one embodiment, in response to a schedule display operation, displaying a synchronized first schedule through a first application includes: in response to a schedule display operation, generating a schedule synchronization request based on an open account; sending the schedule synchronization request to a second application, wherein the schedule synchronization request instructs the second application to return schedule data to be synchronized related to a private domain account corresponding to the open account to the first application; receiving the schedule data to be synchronized from the second application, and updating the original schedule of the first application based on the schedule data to be synchronized, thereby obtaining and displaying the first synchronized schedule.

[0091] Specifically, the second application may include a client for the second application and a server for the second application. The client for the second application can be used to display schedule data, and the server for the second application can be used to locate the corresponding schedule data to be synchronized in response to the schedule display operation. The first application in the terminal can generate a schedule synchronization request based on an open account in response to the schedule display operation. For example, the first application can generate a schedule synchronization request carrying an open account and send the generated schedule synchronization request to the server of the second application. When the server of the second application receives the schedule synchronization request, it can determine the open account corresponding to the schedule synchronization request and determine the private domain account corresponding to the open account. For example, the server of the second application can extract the open account from the schedule synchronization request and search in the storage space whether there is a stored private domain account corresponding to the open account, and use the found stored private domain account as the private domain account corresponding to the open account. Furthermore, the server of the second application searches for the schedule data to be synchronized corresponding to the private domain account in the schedule data repository, and returns the found schedule synchronization data to the first application. Thus, the first application can receive the schedule data to be synchronized fed back by the second application, and update the original schedule of the first application based on the schedule data to be synchronized of the second application to obtain the first synchronized schedule, which is then displayed through the first schedule display interface.

[0092] In one embodiment, the schedule data repository may pre-store the schedule data corresponding to different private domain accounts. When the server of the second application obtains the private domain account corresponding to the open account, it can search for the schedule data corresponding to the obtained private domain account in the schedule data repository, that is, search for the original schedule corresponding to the obtained private domain account, and determine the schedule data to be synchronized from the original schedule to obtain the schedule data to be synchronized for the second application.

[0093] In one embodiment, when synchronizing a schedule for the first time, the schedule data to be synchronized can be all schedule data corresponding to the private domain account at the current moment. When synchronizing a schedule for subsequent times, the schedule data to be synchronized can be schedule data updated within a preset time period prior to the current moment.

[0094] In the above embodiments, by generating a schedule synchronization request, the schedule data to be synchronized fed back by the second application can be obtained through the schedule synchronization request, thereby realizing the synchronization of the schedule based on the schedule data to be synchronized fed back by the second application, which makes it easier for users to arrange schedule tasks based on the synchronized schedule.

[0095] In one embodiment, when the second application displays schedule data while the first application has no schedule data, the first application, upon receiving the open account, can respond to the schedule display operation by generating a schedule synchronization request and sending it to the second application. The second application retrieves existing schedules related to the private domain account corresponding to the open account from the schedule data repository, uses these existing schedules as the schedule data to be synchronized in the second application, and returns the schedule data to be synchronized in the second application to the first application. Thus, the first application can use the received schedule data to be synchronized as the first synchronized schedule and display it, thereby achieving one-click synchronization of the schedules of the first and second applications.

[0096] In the aforementioned schedule synchronization method, by displaying the configuration interface of the first application, an open account can be collected based on the displayed configuration interface. The collected open account then responds to the schedule display operation, displaying the synchronized first schedule through the first application. Since application configuration only requires entering the open account in the configuration interface, the configuration threshold is greatly reduced, improving the user experience. Furthermore, by collecting the open account based on the configuration interface, the original schedule of the first application can be updated using the schedule data to be synchronized from the private domain account corresponding to the open account in the second application during the schedule display operation. This allows for the unified integration of schedules from various personal channels, making it easier for users to schedule their personal time through the synchronized schedule.

[0097] Furthermore, this application can synchronize schedule data generated within a proprietary protocol system to various first-level applications that support the standard protocol via a standard protocol, thereby unifying schedule data across applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving the memory, processing, and other resources required by additional applications.

[0098] In one embodiment, the configuration interface also configures a domain name address and an authorization code. In response to the calendar display operation, a calendar synchronization request is generated based on the open account, including: generating an authentication request based on the open account and the authorization code, and sending the authentication request to the second application through the domain name address; wherein the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; receiving the verification result returned by the second application, and when the verification result indicates that the verification is successful, determining the account-related information, and generating a calendar synchronization request based on the account-related information.

[0099] Specifically, when entering an open account in the configuration interface of the first application, users can also enter a domain name address and an authorization code. The domain name address is used to navigate the calendar synchronization request to the server of the second application, and the authorization code is used to verify the legitimacy of the calendar synchronization request.

[0100] When a user triggers a schedule display operation, the first application responds by obtaining a pre-configured open account, authorization code, and domain address. It then generates an authentication request carrying the open account and authorization code and sends it to the second application's server via the domain address. The second application's server stores the mapping between open accounts and authorization codes. Upon receiving the authentication request, the second application's server extracts the authorization code and open account from the request and determines whether they match based on the mapping. If they match, it returns a verification result to the first application. Further, when the first application receives the verification result from the second application, and this result indicates successful verification, the first application determines the account-related information and generates a schedule synchronization request based on this information. Specifically, the account-related information can be an open account or a Session ID (time domain identifier). The Session ID refers to the identifier of the session object. A Session can be referred to as "session control." The Session object stores the attributes and configuration information required for a specific user session, and the server can distinguish different users using the Session ID.

[0101] In one embodiment, when the server of the second application determines that the authorization code in the authentication request matches the open account, the server of the second application can generate a Session ID, store the generated Session ID in memory, and return the Session ID to the first application as a verification result. The first application can store the Session ID via a cookie, and subsequently generate a schedule synchronization request based on the Session ID.

[0102] In one embodiment, before responding to the schedule display operation, the first application needs to be configured. Before configuring the first application, the second application can also generate the authorization code and open account required for configuration. (See reference) Figure 5The second application may include a second application front-end, an access layer, a schedule logic module, and an account storage module. For example, the client of the second application includes a second application front-end, an access layer, a schedule logic module, and an account storage module. When it is necessary to generate an open account and authorization code, the user can generate a configuration information generation request through the second application front-end and send the configuration information generation request to the access layer. The access layer sends the configuration information generation request to the schedule logic module, so that the schedule logic module can obtain a private domain account, generate an open account corresponding to the private domain account, and bind the generated open account with the obtained private domain account. Further, the schedule logic module sends the binding relationship to the account storage module, so that the account storage module stores the binding relationship, obtains the storage result, and returns the storage result to the schedule logic module. When the schedule logic module receives the storage result, the schedule logic module generates an authorization code that matches the open account and returns the open account and authorization code to the second application front-end, so that the second application front-end can display the generated open account and authorization code, so that the user can configure the first application through the displayed open account and authorization code. Figure 5 A schematic diagram illustrating the generation of an open account and authorization code is shown in one embodiment.

[0103] In one embodiment, reference Figure 6 The server of the second application may include an access layer service, an account authentication service, a schedule logic service, and a schedule storage service. In response to a schedule display operation, the first application generates an authentication request including an open account, an authorization code, and a domain name address. This authentication request can be in the form of an HTTPS link, allowing the first application to send the HTTPS link to the access layer service of the second application. The access layer service then extracts the open account and authorization code from the HTTPS link and sends them to the account authentication service. The account authentication service verifies the matching between the received open account and authorization code, obtains a verification result, and returns the verification result to the access layer service, which then feeds back the verification result to the first application. Upon receiving the verification result from the second application and confirming successful verification, the first application determines the account-related information, generates a schedule synchronization request based on the account-related information, and sends the schedule synchronization request to the access layer service.

[0104] Furthermore, the access layer service triggers the account authentication service to determine the private domain account corresponding to the account-related information. For example, when the account-related information is an open account, the access layer service determines the private domain account bound to that open account; when the account-related information is a Session ID, the access layer service identifies the open account corresponding to that Session ID and determines the private domain account bound to that open account. The access layer service generates a data retrieval request based on the determined private domain account and sends this request to the schedule logic service. This causes the schedule logic service to trigger the schedule storage service to search for the schedule data to be synchronized corresponding to the private domain account and returns the found schedule data to the access layer service. The access layer service then transforms the schedule data to be synchronized according to the standard protocol, obtaining the transformed schedule data for the second application. This transformed schedule data for the second application is then returned to the first application, enabling the first application to parse the transformed schedule data using the standard protocol, obtain the parsing result, and update its original schedule based on the parsing result. Figure 6 A schematic diagram illustrating the interaction between a first application and a second application in one embodiment is shown.

[0105] In the above embodiments, since the calendar is synchronized after authentication, the security of calendar synchronization can be improved, thereby reducing the probability of unauthorized synchronization.

[0106] In one embodiment, in response to a schedule display operation, a schedule synchronization request is generated based on an open account, including: in response to a schedule display operation, obtaining schedule data to be synchronized in a first application; generating a schedule synchronization request based on the open account and the schedule data to be synchronized in the first application; the schedule data to be synchronized in the first application is used to update the existing schedule of a second application.

[0107] Specifically, the terminal can also synchronize the schedule of the second application through the schedule data in the first application. For example, when the first application is successfully configured, the first application can send its own schedule data to the second application so that the second application can update the original schedule by synchronizing the received schedule data.

[0108] When a user requests a calendar display, the first application responds by obtaining the calendar data to be synchronized from its own application. Based on this data and the configured open account, it generates a calendar synchronization request and sends it to the server of the second application. The server of the second application extracts the calendar data from the first application carried in the calendar synchronization request, finds the private domain account corresponding to the open account in the request, updates the existing calendar in the second application corresponding to the private domain account using the calendar data from the first application, obtains the second synchronized calendar, and triggers the second application client to display the second synchronized calendar.

[0109] In one embodiment, when the first application synchronizes its schedule with the second application for the first time, the schedule data to be synchronized in the first application can be all the schedule data of the first application. When the first application synchronizes its schedule with the second application for the second time, the schedule data to be synchronized in the first application can be the recently updated schedule data.

[0110] In one embodiment, after configuring the first application based on the open account, authorization code, and domain name address, the first application can respond to the calendar display operation by generating a calendar synchronization request based on the open account, authorization code, and the calendar data to be synchronized in the first application, and sending the calendar synchronization request to the server of the second application via the domain name address. The server of the second application extracts the open account and authorization code from the calendar synchronization request and determines whether the open account and authorization code match. If they do not match, the calendar synchronization request is considered an illegal synchronization request, and the server of the second application does not process the calendar synchronization request. If they match, the server of the second application converts the open account into a private domain account, finds the calendar data corresponding to the private domain account, extracts the calendar data to be synchronized from the calendar synchronization data corresponding to the private domain account, that is, extracts the calendar data to be synchronized in the second application, and returns the calendar data to be synchronized in the second application to the first application, so that the first application can perform calendar synchronization using the received calendar data to be synchronized in the second application. The server of the second application also updates the calendar data corresponding to the private domain account using the calendar data to be synchronized in the first application, so that the second application can perform calendar synchronization using the calendar data to be synchronized in the first application. By sending the schedule data to be synchronized from the first application to the second application, and feeding back the schedule data to be synchronized from the second application to the first application, the first application can perform schedule synchronization processing in a timely manner using the schedule data to be synchronized from the second application, and the second application can perform schedule synchronization processing in a timely manner using the schedule data to be synchronized from the first application, thereby ensuring that the schedules displayed by the first application and the schedules displayed by the second application are consistent.

[0111] In the above embodiments, by sending the schedule data to be synchronized from the first application to the second application based on the open account, the second application can update the original schedule using the received schedule data to be synchronized, thereby achieving schedule synchronization.

[0112] In one embodiment, the method further includes: displaying an association interface of the first application, wherein the association interface displays an application identifier of the second application; and in response to the selection operation of the application identifier of the second application, binding the open account with the login account of the first application.

[0113] Specifically, when the open account, domain name address, and authorization code are entered into the configuration interface displayed by the first application, the first application can display related interfaces, such as... Figure 7 The associated interface is shown. The associated interface displays the application identifier 701 of the second application. When the user selects the application identifier 701 of the second application, the first application responds to the selection operation by binding its open account to its login account. This allows the first application to use the schedule data to be synchronized stored corresponding to the login account as its own schedule data to be synchronized. The login account of the first application refers to the account used to log in to the first application. Figure 7 A schematic diagram of the associated interface in one embodiment is shown.

[0114] In one embodiment, when the first application receives the schedule data to be synchronized returned by the second application, the first application can determine the original schedule of the login account bound to the open account, and update the original schedule through the schedule data to be synchronized of the second application to obtain the first synchronized schedule.

[0115] In this embodiment, by displaying the association interface, the open account and the login account can be bound through the association interface, so that the schedule can be synchronized based on the association result in the future.

[0116] In one embodiment, such as Figure 8 As shown, a schedule synchronization method is provided, which can be applied to... Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0117] Step S802: In response to the information display operation of the second application, the configuration information display interface of the second application is displayed; the second application is an application that supports private protocols.

[0118] Specifically, when a user wants to synchronize the schedules of the first application and the second application, the user can trigger an information display operation. This causes the second application to respond to the user's information display operation and display a configuration information display interface. For example, the second application may display an information display control. When the second application determines that the user has clicked this control, it can display the configuration information display interface. The configuration information display interface refers to the interface used to display configuration information. This configuration information can be used to configure the first application so that the configured first application can synchronize its schedule with the second application. The configuration information includes at least one of the following: an open account, a domain name address, and an authorization code.

[0119] Step S804: Display the open account generated based on the private domain account through the configuration information display interface; the private domain account is the real account corresponding to the private protocol in the second application; the open account is the virtual account created in the second application corresponding to the standard protocol, and the open account is used to pass to the first application so that the first application can generate a schedule synchronization request based on the open account.

[0120] Specifically, the terminal can display the open account through the configuration information display interface of the second application. This open account is a virtual account created in the second application based on a standard protocol, corresponding to the private domain account. The private domain account is the real account in the second application corresponding to the private protocol.

[0121] In one embodiment, when a user triggers an information display operation, the second application can obtain the currently logged-in account and use the obtained login account as a private domain account. The second application obtains virtual account generation rules corresponding to the standard protocol, generates a corresponding open account using the virtual account generation rules and the private domain account, and then... Figure 9 The configuration information display interface shown presents the open account. For example, the open account is displayed via 901. Users can then input the displayed open account into the configuration interface of the first application to configure it. Figure 9 A schematic diagram of a configuration information display interface in one embodiment is shown.

[0122] In one embodiment, when the second application displays a configuration information display interface, the user can input the corresponding private domain account through the interface. For example, by inputting the private domain account at 901, the second application generates an open account corresponding to the input private domain account and displays the generated open account at 901. It is easy to understand that the private domain account is the real account corresponding to the private protocol in the second application; that is, the second application uses the private domain account for information flow and updates.

[0123] Step S806: In response to the schedule synchronization request initiated by the first application, the synchronized second schedule is displayed through the second application. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application.

[0124] Specifically, once the open account is entered into the configuration interface of the first application, the first application can synchronize the schedule. For example, the first application can obtain the schedule to be synchronized, generate a schedule synchronization request based on the schedule to be synchronized in the first application, and send the schedule synchronization request to the second application. This allows the second application to update the original schedule related to the private domain account corresponding to the open account using the schedule to be synchronized in the first application, obtain the synchronized second schedule, and display the synchronized second schedule through the second application.

[0125] In one embodiment, when a first application generates a schedule synchronization request carrying schedule data to be synchronized, the first application can send the schedule synchronization request to the server of a second application. The server of the second application can then determine the open account carried in the schedule synchronization request, find the private domain account corresponding to the open account, update the original schedule related to the private domain account using the schedule data to be synchronized carried in the schedule synchronization request, obtain the second synchronized schedule, and trigger the client of the second application logged in with the private domain account to display the second synchronized schedule.

[0126] In one embodiment, when the first application displays schedule data while the second application has no schedule data, the first application, upon receiving an open account, can send its locally stored schedule data as the schedule data to be synchronized to the second application. This allows the second application to use the schedule data to be synchronized from the first application as the second synchronized schedule. The second application, in response to the user's operation to display the schedule in the second application, displays this second synchronized schedule, thus achieving one-click synchronization of the schedules of the first and second applications.

[0127] In the aforementioned schedule synchronization method, in response to an information display operation, the configuration information display interface of the second application can be shown. This interface then displays an open account generated based on the private domain account. Users can then configure the first application using this displayed open account, enabling the configured first application to initiate a schedule synchronization request. Responding to the schedule synchronization request initiated by the first application, the existing schedules related to the private domain account corresponding to the open account in the second application can be updated based on the schedule data to be synchronized in the first application, resulting in a second synchronized schedule. This second synchronized schedule can then be displayed through the second application, thereby achieving the goal of unifying and integrating personal schedules from various channels, facilitating users' time management through synchronized schedules.

[0128] Furthermore, this application can synchronize schedule data generated within the standard protocol system to various second applications that support proprietary protocols via the standard protocol, thereby unifying schedule data from applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving the memory, processing, and other resources occupied by additional applications.

[0129] In one embodiment, displaying an open account generated based on a private domain account through a configuration information display interface includes: determining virtual account generation rules corresponding to a standard protocol; generating an open account corresponding to the private domain account according to the virtual account generation rules; and displaying the open account through the configuration information display interface.

[0130] Specifically, upon obtaining a private domain account, the second application can also acquire virtual account generation rules corresponding to the standard protocol, generate a corresponding open account using these rules, bind the generated open account to the acquired private domain account, and display the open account through a configuration information display interface. For example, when the standard protocol is a protocol under the email account system, the second application can convert the private domain account "gooper1000" into an open account in email format, "gooper1000.cslq.wecccm.wook".

[0131] It is easy to understand that since the second application may include a client of the second application and a server of the second application, configuration information can be generated either through the client of the second application or through the server of the second application, and the client of the second application can be triggered to display the configuration information through the configuration information display interface.

[0132] In this embodiment, since the virtual account generation rule corresponds to the standard protocol, the open account generated based on the virtual account generation rule that matches the private domain account can also correspond to the standard protocol. In this way, the first application that supports the standard protocol can synchronize its schedule with the second application that supports the private protocol through the open account.

[0133] In one embodiment, the method further includes: in response to a trigger operation on the configuration information display interface, displaying an authorization code corresponding to the open account; the authorization code is used to transmit to the first application so that the first application can generate an authentication request based on the authorization code.

[0134] Specifically, while generating an open account, the second application can also generate an authorization code that matches the open account, and associate and store the generated open account and authorization code together. Thus, when a user triggers the configuration information display interface, the second application can respond to the user's trigger operation by displaying the authorization code in the configuration information display interface. In one embodiment, refer to... Figure 9 The configuration information display interface can show the authorization code acquisition control 902. Users can click the authorization code acquisition control to trigger the second application to display the authorization code that matches the open account.

[0135] In one embodiment, the configuration information display interface also displays a password acquisition record control. Users can click on this control to trigger a second application to display the authorization code obtained at a historical moment.

[0136] In one embodiment, when a user triggers an information display operation, the second application can display a configuration information display interface, showing the open account and domain name address. The domain name address can be an address pre-configured by the developers. The configuration information display interface may also display an authorization code retrieval control. When the second application determines that the user clicks the authorization code retrieval control, it can determine the authorization code matching the open account and display that authorization code on the configuration information display interface. Thus, the user can configure the first application through the configuration information displayed on the configuration information display interface.

[0137] In the above embodiments, by generating and displaying an authorization code, the first application can generate an authentication request through the authorization code. Then, when the second application determines that the first application is a legitimate application based on the authentication request, it can synchronize the schedule with the first application. This greatly improves the security of schedule synchronization.

[0138] In one embodiment, in response to a schedule synchronization request initiated by a first application, displaying the synchronized second synchronized schedule through a second application includes: when a schedule synchronization request is received from the first application, extracting the schedule data to be synchronized and account-related information of the first application from the schedule synchronization request; determining the private domain account corresponding to the account-related information; updating the original schedule related to the private domain account in the second application using the schedule data to be synchronized from the first application to obtain the second synchronized schedule; and displaying the second synchronized schedule through the second application.

[0139] Specifically, when the server of the second application receives a calendar synchronization request from the first application, the server of the second application can extract the calendar data to be synchronized from the calendar synchronization request, that is, extract the calendar data to be synchronized from the first application, as well as extract account-related information. This account-related information can be an open account or a Session ID. Further, the server of the second application determines the private domain account corresponding to this account-related information and determines the original calendar corresponding to this private domain account. It then updates this original calendar using the calendar data to be synchronized from the first application to obtain the second synchronized calendar, thereby triggering the client of the second application to display the second synchronized calendar.

[0140] In the above embodiments, simply generating a schedule synchronization request that includes the schedule data to be synchronized and account-related information is sufficient to trigger the second application to synchronize and update the original schedule through the schedule synchronization request, thereby greatly improving the convenience of schedule synchronization.

[0141] In one embodiment, the schedule synchronization request includes a meeting identifier of a canceled meeting. In response to the schedule synchronization request initiated by the first application, the second application displays the synchronized second schedule, including: in response to the schedule synchronization request initiated by the first application, the second application cancels the display of meeting information corresponding to the meeting identifier of the canceled meeting; the method further includes: triggering the display of a message card on the terminals of participants in the canceled meeting; wherein the displayed message card is used to indicate that the meeting has been canceled.

[0142] Specifically, when a user cancels a meeting in the first application, the first application obtains the meeting identifier of the canceled meeting and uses this identifier as schedule data to be synchronized. Using this schedule data and account-related information, the first application generates a schedule synchronization request and sends it to the server of the second application. The server of the second application responds to the schedule synchronization request, determines the original schedule of the private domain account corresponding to the account-related information, deletes the meeting information related to the canceled meeting identifier from the original schedule corresponding to the private domain account, and triggers the client of the second application to cancel the display of the meeting information corresponding to the canceled meeting identifier.

[0143] Furthermore, when the server of the second application deletes the meeting information associated with the meeting identifier of the canceled meeting, the server of the second application can also identify the participants in the canceled meeting and trigger the display of a message card on the participants' terminals. For example, it can trigger the display of a message card on the second application client in the participants' terminals, where the message card is used to notify the participants that the meeting has been canceled.

[0144] In one embodiment, reference Figure 10The server for the second application may include a standard protocol access layer, an account authentication service, a schedule logic service, and an online meeting service. When a user cancels a meeting in the first application, the first application can automatically generate a schedule synchronization request and send it to the standard protocol access layer. The standard protocol access layer triggers the account authentication service to verify the matching of the open account and the authorization code, and determines the private domain account corresponding to the open account upon successful verification. Further, the standard protocol access layer sends the private domain account to the schedule logic service, so that the schedule logic service can execute the deletion logic to remove the meeting information associated with the canceled meeting from the original schedule corresponding to the private domain account, obtain the deletion result, and return the deletion result to the standard protocol access layer, which then returns the deletion result to the first application. Further, when the schedule logic service executes the deletion logic, it can also trigger the online meeting service to generate a message card and send the message card to the participants' terminals. The schedule logic service is used for logical processing such as pulling, updating, and deleting schedule data. Figure 10 A schematic diagram illustrating the interaction between a first application and a second application in one embodiment is shown.

[0145] It is easy to understand that when the first application adds a meeting schedule, adds other schedules besides the meeting schedule, or cancels other schedules besides the meeting schedule, the first application can automatically generate a schedule synchronization request in the manner described above, so that the second application can also perform schedule synchronization in the manner described above.

[0146] In the above embodiments, since the canceled meeting can be automatically synchronized to the second application when the first application cancels the meeting, the schedule can be synchronized without the user's awareness, thereby greatly improving the user experience.

[0147] In one embodiment, such as Figure 11 As shown, a schedule synchronization method is provided, which can be applied to... Figure 1 Taking the server in the example of the second application, the calendar synchronization method includes the following steps:

[0148] Step S1102: In response to the calendar synchronization request sent by the first application supporting the standard protocol, determine the open account to which the account-related information carried in the calendar synchronization request points; wherein, the open account is a virtual account corresponding to the standard protocol created in the second application supporting the private protocol.

[0149] Specifically, the first application can generate a schedule synchronization request and send it to the server, i.e., to the server of the second application. For example, when a user changes the schedule in the first application, the first application can generate a schedule synchronization request; or, the first application can generate schedule synchronization requests at a preset request frequency. Furthermore, when the server of the second application receives the schedule synchronization request sent by the first application, the server of the second application can determine the open account pointed to by the account-related information carried in the schedule synchronization request. For example, when the account-related information is an open account, the server of the second application can directly identify the account-related information as an open account; when the account-related information is a Session ID, the server of the second application can identify the open account corresponding to that Session ID.

[0150] Step S1104: Determine the private domain account corresponding to the open account. The private domain account is the real account corresponding to the private protocol in the second application.

[0151] Specifically, the server of the second application stores the correspondence between open accounts and private domain accounts. When an open account is obtained, the server of the second application can use this correspondence to determine the private domain account corresponding to the open account pointed to by the account-related information.

[0152] Step S1106: Obtain at least one type of schedule data to be synchronized from the schedule data to be synchronized in the first application and the schedule data to be synchronized related to the private domain account in the second application.

[0153] Specifically, when the schedule data in the first application is updated, the second application can update its existing schedule to match that of the first application, and vice versa. Therefore, when a private domain account is obtained, the server of the second application can acquire at least one of the following: the schedule data to be synchronized related to the private domain account in the second application, and the schedule data to be synchronized in the first application. For example, when the schedule data in the first application is updated, the first application can use the updated schedule data as the schedule data to be synchronized and include it in the schedule synchronization request, so that the server of the second application can extract the schedule data to be synchronized from the schedule synchronization request. Alternatively, whenever the schedule data in the second application is updated, when the server of the second application receives a schedule synchronization request, it can search for the existing schedule corresponding to the private domain account in memory, extract the recently updated schedule data from the existing schedule corresponding to the private domain account, and use the recently updated schedule data as the schedule data to be synchronized in the second application.

[0154] Step S1108: Synchronize the schedules in the first and second applications using the acquired schedule data to be synchronized.

[0155] Specifically, when the schedule data to be synchronized is the schedule data of the first application, the server of the second application updates the original schedule corresponding to the private domain account using the schedule data to be synchronized in the first application to obtain the second synchronized schedule, and displays the second synchronized schedule through the client of the second application. When the schedule data to be synchronized is the schedule data of the second application, the server of the second application returns the schedule data to be synchronized in the second application to the first application, so that the first application updates the original schedule using the schedule data to obtain the first synchronized schedule, and displays the first synchronized schedule.

[0156] In one embodiment, when a user updates the schedule in both the first and second applications, the first application can generate a schedule synchronization request carrying the schedule data to be synchronized and send the request to the server of the second application. The server of the second application can then perform schedule synchronization based on the schedule data to be synchronized from the first application. Simultaneously, the server of the second application can also determine the schedule data to be synchronized corresponding to a private domain account and return this data to the first application, enabling the first application to perform schedule synchronization using the received schedule data.

[0157] In one embodiment, reference Figure 12 The second application supporting the private protocol can specifically be a meeting room booking application, a live streaming application, or a group chat application. Users can modify schedules in the client of the second application, which triggers the schedule application service to store the modified schedule data in the schedule data repository. Users can also modify schedules in the first application, which sends an authentication request to the server of the second application via a standard protocol. This allows the server of the second application to authenticate the open account. Upon successful authentication, in response to the schedule synchronization request sent by the first application, the server updates the original schedule corresponding to the private domain account in the schedule data repository and sends the update result back to the client of the second application, so that the client of the second application can display the updated schedule data. Figure 12 A schematic diagram of the architecture of a schedule synchronization method in one embodiment is shown.

[0158] In the aforementioned schedule synchronization method, by responding to a schedule synchronization request sent by a first application supporting the standard protocol, the open account pointed to by the account-related information carried in the schedule synchronization request can be determined, thereby identifying the private domain account corresponding to that open account. By obtaining the private domain account and the schedule synchronization request, at least one type of schedule data to be synchronized can be obtained from the private domain account-related schedule data in the second application and the schedule data to be synchronized from the first application carried in the schedule synchronization request. Based on the obtained schedule data to be synchronized, the schedules in the first and second applications are synchronized, achieving the goal of integrating personal schedules from various channels together, making it convenient for users to schedule their personal time plans through the synchronized schedules.

[0159] Furthermore, this application can synchronize schedule data generated within a proprietary protocol system to various first applications supporting the standard protocol via a standard protocol, and can also synchronize schedule data generated within a standard protocol system to various second applications supporting the proprietary protocol via a standard protocol, thereby unifying schedule data across applications supporting different protocols. Moreover, compared to synchronizing schedules by installing applications providing calendar read / write interfaces on various terminals, this application eliminates the need for additional applications, thus saving memory, processing, and other resources consumed by additional applications.

[0160] In one embodiment, obtaining at least one type of schedule data to be synchronized, namely, schedule data to be synchronized in a first application and schedule data to be synchronized in a second application related to a private domain account, includes: if the schedule synchronization request carries schedule data, then using the schedule data carried in the schedule synchronization request as the schedule data to be synchronized in the first application; synchronizing the schedules in the first application and the second application using the obtained schedule data to be synchronized includes: updating the original schedules related to the private domain account corresponding to the open account in the second application using the schedule data to be synchronized in the first application.

[0161] Specifically, upon receiving a schedule synchronization request, the server of the second application can determine whether the request carries schedule data. If it does, the schedule data carried in the request is used as the schedule data to be synchronized in the first application. The server then uses this schedule data to update the existing schedules in the second application related to the private domain account corresponding to the open account, thus obtaining the second synchronized schedule. Furthermore, the server of the second application can also trigger clients logged into the second application with a private domain account to display this second synchronized schedule.

[0162] In this embodiment, by generating a schedule synchronization request carrying schedule data, the schedules of the first application and the second application can be synchronized based on the schedule synchronization request, thereby achieving the goal of unifying the schedule data in applications that support different protocols.

[0163] In one embodiment, obtaining at least one type of schedule data to be synchronized, namely, schedule data to be synchronized in a first application and schedule data to be synchronized in a second application related to a private domain account, includes: if the schedule synchronization request does not carry schedule data, searching for changed schedule data corresponding to the private domain account in the schedule data repository corresponding to the second application; using the found changed schedule data as the schedule data to be synchronized in the second application related to the private domain account; and synchronizing the schedules in the first application and the second application using the schedule data to be synchronized, including: updating the original schedule in the first application using the schedule data to be synchronized in the second application related to the private domain account.

[0164] Specifically, when the schedule synchronization request does not carry schedule data, the server of the second application can search for the original schedule corresponding to the private domain account in the schedule data repository and extract the changed schedule data from the original schedule. The changed schedule data refers to schedule data that has changed within the update time period, which is a period of time prior to the current moment. The end point of the update time period is the current moment, and the duration of the update time period can be a preset value. Further, the server of the second application uses the retrieved changed schedule data as the schedule data to be synchronized in the second application related to the private domain account, i.e., as the schedule data to be synchronized in the second application, and returns the schedule data to be synchronized in the second application to the first application. This allows the first application to update its original schedule using the received schedule data, obtain the first synchronized schedule, and display the first synchronized schedule.

[0165] In this embodiment, by generating a schedule synchronization request, the schedules of the first application and the second application can be synchronized based on the schedule synchronization request, thereby achieving the goal of unifying the schedule data in applications that support different protocols.

[0166] This application also provides an application scenario in which the above-described schedule synchronization method is applied. Specifically, the schedule synchronization method is applied in this scenario as follows:

[0167] The first application is the calendar application built into the terminal system, and the second application is a meeting room reservation application. When a user cancels a meeting room reservation through the first application, the first application generates cancellation information and uses this cancellation information and the open account to generate a schedule synchronization request, which is then sent to the server of the second application. The server of the second application receives the schedule synchronization request, extracts the open account from it, determines the original meeting reservation information of the private domain account corresponding to the extracted open account, updates the original meeting reservation information using the cancellation information in the schedule synchronization request, obtains the updated meeting reservation information, and triggers the client of the second application to cancel the display of the meeting room reservation information that has been canceled in the first application.

[0168] This application also provides another application scenario where the above-described schedule synchronization method is applied. Specifically, the schedule synchronization method is applied in this scenario as follows:

[0169] The first application is the calendar application built into the terminal system, and the second application is the live streaming application. When a user updates the live streaming schedule in the client of the second application, the client of the second application can trigger the server of the second application to update the original live streaming schedule related to the private domain account in the schedule data repository, thus obtaining the changed schedule data. When the server of the second application receives a schedule synchronization request sent by the first application, it can return the changed schedule data corresponding to the private domain account stored in the schedule data repository to the first application, so that the first application can perform schedule synchronization processing based on the received changed schedule data.

[0170] The above application scenarios are merely illustrative. It is understood that the application of the schedule synchronization method provided in the embodiments of this application is not limited to the above scenarios.

[0171] In one specific embodiment, reference Figure 13 The schedule synchronization method includes the following steps:

[0172] S1302, in response to the information display operation of the second application, display the configuration information display interface of the second application; the second application is an application that supports a private protocol.

[0173] S1304, determine the virtual account generation rules corresponding to the standard protocol; generate open accounts corresponding to private domain accounts according to the virtual account generation rules, and display the open accounts through the configuration information display interface; the open accounts are virtual accounts corresponding to the standard protocol.

[0174] S1306, the first application responds to the triggered operation of the configuration information display interface by displaying the authorization code corresponding to the open account.

[0175] S1308, the first application displays the configuration interface and obtains the open account collected based on the configuration interface; the first application is an application that supports standard protocols.

[0176] S1310, the first application responds to the schedule display operation by generating an authentication request based on the open account and authorization code, and sends the authentication request to the second application via the domain name address; wherein, the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code.

[0177] S1312, the first application receives the verification result returned by the second application, and when the verification result indicates that the verification is successful, it determines the account-related information and generates a schedule synchronization request based on the account-related information and the schedule data to be synchronized by the first application.

[0178] S1314, the first application sends a calendar synchronization request to the second application. The second application extracts the calendar data to be synchronized and account-related information of the first application from the calendar synchronization request, and determines the private domain account corresponding to the account-related information.

[0179] S1316, the second application updates the original schedule related to the private domain account in the second application using the schedule data to be synchronized in the first application, and obtains the second synchronized schedule; the second synchronized schedule is displayed through the second application.

[0180] S1318, the second application determines the schedule data to be synchronized related to the private domain account corresponding to the open account, and returns the determined schedule data to be synchronized to the first application.

[0181] S1320, the first application receives the schedule data to be synchronized from the second application, and updates the original schedule of the first application based on the schedule data to be synchronized from the second application to obtain the first synchronized schedule and display it.

[0182] The aforementioned schedule synchronization method, in response to an information display operation, can show the configuration information display interface of a second application. This interface then displays an open account generated from a private domain account. Users can then configure the first application using this displayed open account, enabling the configured first application to initiate schedule synchronization requests. Responding to the schedule synchronization request initiated by the first application, the existing schedules related to the private domain account corresponding to the open account in the second application are updated based on the schedule data to be synchronized in the first application, resulting in a second synchronized schedule. This second synchronized schedule can then be displayed through the second application, achieving the goal of unifying and integrating personal schedules from various channels, making it easier for users to schedule their time using the synchronized schedule.

[0183] 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.

[0184] In one embodiment, such as Figure 14 As shown, a schedule synchronization device 1400 is provided. This device can be a software module, a hardware module, or a combination of both as part of a computer device. Specifically, the device includes: a configuration display module 1402, a data acquisition module 1404, and a first synchronization module 1406, wherein:

[0185] The configuration display module 1402 is used to display the configuration interface of the first application, which is an application that supports standard protocols;

[0186] The acquisition module 1404 is used to acquire open accounts based on the configuration interface. The open account is a virtual account corresponding to the standard protocol created in the second application that supports the private protocol.

[0187] The first synchronization module 1406 is used to respond to the schedule display operation and display the synchronized first synchronized schedule through the first application. The first synchronized schedule is obtained by updating the original schedule of the first application based on the schedule data to be synchronized related to the private domain account corresponding to the open account in the second application. The private domain account is the real account corresponding to the private protocol in the second application.

[0188] In one embodiment, the first synchronization module 1406 is further configured to, in response to the schedule display operation, generate a schedule synchronization request based on the open account; send the schedule synchronization request to the second application, the schedule synchronization request being used to instruct the second application to return the schedule data to be synchronized related to the private domain account corresponding to the open account to the first application; receive the schedule data to be synchronized fed back by the second application, and update the original schedule of the first application based on the schedule data to be synchronized, thereby obtaining the first synchronized schedule and displaying it.

[0189] In one embodiment, the first synchronization module 1406 is further configured to generate an authentication request based on the open account and the authorization code, and send the authentication request to the second application via a domain name address; wherein the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; receive the verification result returned by the second application, and when the verification result indicates that the verification is successful, determine the account-related information and generate a schedule synchronization request based on the account-related information.

[0190] In one embodiment, the first synchronization module 1406 is used to respond to the schedule display operation, obtain the schedule data to be synchronized in the first application; generate a schedule synchronization request based on the open account and the schedule data to be synchronized in the first application; and use the schedule data to be synchronized in the first application to update the original schedule of the second application.

[0191] In one embodiment, the schedule synchronization device 1400 is further configured to display an associated interface of the first application, in which an application identifier of the second application is displayed; in response to the selection operation of the application identifier of the second application, the open account is bound to the login account of the first application.

[0192] In one embodiment, such as Figure 15 As shown, a schedule synchronization device 1500 is provided. This device can be a software module, a hardware module, or a combination of both as part of a computer device. Specifically, the device includes: an interface display module 1502, an information display module 1504, and a second synchronization module 1506, wherein:

[0193] The interface display module 1502 is used to respond to the information display operation of the second application and display the configuration information display interface of the second application; the second application is an application that supports private protocols.

[0194] The information display module 1504 is used to display the open account generated based on the private domain account through the configured information display interface; the private domain account is the real account corresponding to the private protocol in the second application; the open account is the virtual account created in the second application corresponding to the standard protocol, and the open account is used to pass to the first application so that the first application can generate a schedule synchronization request based on the open account.

[0195] The second synchronization module 1506 is used to respond to the schedule synchronization request initiated by the first application and display the synchronized second synchronized schedule through the second application. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application.

[0196] In one embodiment, the information display module 1504 is further configured to determine the virtual account generation rules corresponding to the standard protocol; generate an open account corresponding to the private domain account according to the virtual account generation rules; and display the open account through the configuration information display interface.

[0197] In one embodiment, the schedule synchronization device 1500 is further configured to display an authorization code corresponding to the open account in response to a trigger operation on the configuration information display interface; the authorization code is used to transmit to the first application so that the first application can generate an authentication request based on the authorization code.

[0198] In one embodiment, the second synchronization module 1506 is further configured to, when receiving a schedule synchronization request sent by the first application, extract the schedule data to be synchronized and account-related information of the first application in the schedule synchronization request; determine the private domain account corresponding to the account-related information; update the original schedule related to the private domain account in the second application using the schedule data to be synchronized in the first application to obtain the second synchronized schedule; and display the second synchronized schedule through the second application.

[0199] In one embodiment, the schedule synchronization request includes a meeting identifier for a canceled meeting. The second synchronization module 1506 is further configured to respond to the schedule synchronization request initiated by the first application by canceling the display of meeting information corresponding to the meeting identifier of the canceled meeting through the second application; and triggering the display of message cards on the terminals of the participants in the canceled meeting; wherein the displayed message cards are used to indicate that the meeting has been canceled.

[0200] In one embodiment, such as Figure 16 As shown, a schedule synchronization device 1600 is provided. This device can be a software module, a hardware module, or a combination of both as part of a computer device. Specifically, the device includes: a request-response module 1602, an account conversion module 1604, and a target synchronization module 1606, wherein:

[0201] The request-response module 1602 is used to respond to a schedule synchronization request sent by a first application that supports the standard protocol and determine the open account pointed to by the account-related information carried in the schedule synchronization request; wherein, the open account is a virtual account corresponding to the standard protocol created in a second application that supports the private protocol;

[0202] Account conversion module 1604 is used to determine the private domain account corresponding to the open account. The private domain account is the real account corresponding to the private protocol in the second application.

[0203] The target synchronization module 1606 is used to obtain at least one of the schedule data to be synchronized in the first application and the schedule data to be synchronized related to the private domain account in the second application; and to synchronize the schedules in the first application and the second application by obtaining the schedule data to be synchronized.

[0204] In one embodiment, the target synchronization module 1606 is further configured to, if the schedule synchronization request carries schedule data, use the schedule data carried in the schedule synchronization request as the schedule data to be synchronized in the first application; and update the original schedule related to the private domain account corresponding to the open account in the second application using the schedule data to be synchronized in the first application.

[0205] In one embodiment, the target synchronization module 1606 is further configured to, if the schedule synchronization request does not carry schedule data, search for changed schedule data corresponding to the private domain account in the schedule data repository corresponding to the second application; use the found changed schedule data as the schedule data to be synchronized related to the private domain account in the second application; and update the original schedule in the first application using the schedule data to be synchronized related to the private domain account in the second application.

[0206] For specific limitations regarding the schedule synchronization device, please refer to the limitations of the schedule synchronization method above, which will not be repeated here. Each module in the aforementioned schedule synchronization 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 the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0207] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 17 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. 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, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores schedule synchronization data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a schedule synchronization method.

[0208] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 18As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. 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 communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a schedule synchronization method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0209] Those skilled in the art will understand that Figures 17-18 The 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.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] Those skilled in the art will understand that all or part of the processes in the methods of 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, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, 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, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0214] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0215] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements 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 patent application should be determined by the appended claims.

Claims

1. A method for synchronizing schedules, characterized in that, The method includes: The configuration interface of the first application is displayed. The first application is an application that supports standard protocols. Obtain the open account and authorization code collected based on the configuration interface. The authorization code refers to the password created in the second application that supports the private protocol and matches the open account. The open account is a virtual account created by the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol, and is a virtual account corresponding to the standard protocol. The second application is an application that supports the private protocol and uses the private domain account to transfer and update information. The private domain account is the real account in the second application that corresponds to the private protocol. In response to the schedule display operation, an authentication request is generated based on the open account and the authorization code; wherein, the authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; When the verification result returned by the second application indicates that the verification is successful, a schedule synchronization request is generated based on the account-related information. The schedule synchronization request is used to instruct the second application to determine the corresponding private domain account based on the open account pointed to by the account-related information, and return the schedule data to be synchronized related to the private domain account to the first application. The first application displays the first synchronized schedule, which is obtained by updating the original schedule of the first application based on the schedule data to be synchronized fed back by the second application.

2. The method according to claim 1, characterized in that, There is a protocol barrier between the first application and the second application.

3. The method according to claim 1, characterized in that, The configuration interface also includes a domain name address and an authorization code. The response to the schedule display operation generates an authentication request based on the open account and the authorization code, including: An authentication request is generated based on the open account and the authorization code, and the authentication request is sent to the second application via the domain name address; wherein, the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; When the verification result returned by the second application indicates that the verification is successful, a schedule synchronization request is generated based on the account-related information, including: Receive the verification result returned by the second application, and when the verification result indicates that the verification is successful, determine the account-related information and generate a schedule synchronization request based on the account-related information.

4. The method according to claim 1, characterized in that, The method further includes: In response to the calendar display operation, obtain the calendar data to be synchronized from the first application; Based on the open account and the schedule data to be synchronized in the first application, a schedule synchronization request is generated; the schedule data to be synchronized in the first application is used to update the original schedule of the second application.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Display the associated interface of the first application, in which the application identifier of the second application is displayed; In response to the selection operation of the application identifier of the second application, the open account is bound to the login account of the first application.

6. A method for synchronizing schedules, characterized in that, The method includes: In response to the information display operation of the second application, the configuration information display interface of the second application is displayed; the second application is an application that supports private protocols and uses private domain accounts for information flow and updates; The configuration information display interface displays an authorization code and an open account generated based on a private domain account. The authorization code is a password created in a second application that supports the private protocol and matches the open account. The private domain account is a real account in the second application that corresponds to the private protocol. The open account is a virtual account created in the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol, and it corresponds to the standard protocol. The open account and the authorization code are used to transmit to the first application so that the first application can generate an authentication request based on the open account and the authorization code in response to the schedule display operation. The first application is an application that supports the standard protocol. In response to the authentication request initiated by the first application, the matching between the open account and the authorization code is verified, and the verification result is returned to the first application; the returned verification result is used to trigger the first application to generate a schedule synchronization request based on account-related information when the verification result indicates that the verification is successful; the account-related information includes the open account; In response to the schedule synchronization request initiated by the first application, the synchronized second schedule is displayed through the second application. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application in the schedule synchronization request. The private domain account in the second application is determined based on the open account pointed to by the account-related information.

7. The method according to claim 6, characterized in that, The private domain account is the login account currently logged into the second application.

8. The method according to claim 6, characterized in that, The standard protocol is a protocol under the email account system.

9. The method according to claim 6, characterized in that, The step of responding to a schedule synchronization request initiated by the first application and displaying the synchronized second schedule through the second application includes: When a calendar synchronization request is received from the first application, the calendar data to be synchronized and account-related information of the first application in the calendar synchronization request are extracted. Identify the private domain account corresponding to the aforementioned account information; Using the schedule data to be synchronized in the first application, the original schedule related to the private domain account in the second application is updated to obtain the second synchronized schedule; The second synchronized schedule is displayed through the second application.

10. The method according to any one of claims 6 to 9, characterized in that, The schedule synchronization request includes a meeting identifier indicating a canceled meeting. The step of responding to the schedule synchronization request initiated by the first application and displaying the synchronized second schedule through the second application includes: In response to the schedule synchronization request initiated by the first application, the second application cancels the display of meeting information corresponding to the meeting identifier of the canceled meeting; The method further includes: The terminal of the participant in the cancelled meeting is triggered to display a message card; wherein the displayed message card is used to indicate that the meeting has been cancelled.

11. A method for synchronizing schedules, characterized in that, The method includes: In response to a calendar synchronization request sent by a first application that supports the standard protocol, the open account to which the account-related information carried in the calendar synchronization request points is determined; wherein, the open account is a virtual account corresponding to the standard protocol created in the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol; the second application is an application that supports the private protocol and uses the private domain account for information flow and updates; Determine the private domain account corresponding to the open account, wherein the private domain account is the real account in the second application that corresponds to the private protocol; Obtain at least one of the schedule data to be synchronized from the first application and the schedule data to be synchronized related to the private domain account in the second application; By acquiring the schedule data to be synchronized, synchronize the schedules in the first and second applications; The method further includes: In response to the calendar display operation, the first application generates an authentication request based on the open account and the authorization code, and sends the authentication request to the second application; wherein, the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; the authorization code refers to a password created in the second application that supports private protocols and matches the open account; The first application receives the verification result returned by the second application, and when the verification result indicates that the verification is successful, it generates a schedule synchronization request based on the account-related information.

12. The method according to claim 11, characterized in that, The step of obtaining at least one type of schedule data to be synchronized from the schedule data to be synchronized in the first application and the schedule data to be synchronized related to the private domain account in the second application includes: If the schedule synchronization request carries schedule data, then the schedule data carried in the schedule synchronization request shall be used as the schedule data to be synchronized by the first application. The step of synchronizing the schedules in the first and second applications by acquiring the schedule data to be synchronized includes: Using the schedule data to be synchronized in the first application, the original schedules related to the private domain accounts corresponding to the open accounts in the second application are updated.

13. The method according to claim 11, characterized in that, The step of obtaining at least one type of schedule data to be synchronized from the schedule data to be synchronized in the first application and the schedule data to be synchronized related to the private domain account in the second application includes: If the schedule synchronization request does not carry schedule data, then search for the change schedule data corresponding to the private domain account in the schedule data repository corresponding to the second application. The obtained change schedule data will be used as the schedule data to be synchronized in the second application related to the private domain account. The step of synchronizing the schedules in the first and second applications using the schedule data to be synchronized includes: The existing schedule in the first application is updated using the schedule data to be synchronized related to the private domain account in the second application.

14. A schedule synchronization device, characterized in that, The device includes: The configuration display module is used to display the configuration interface of the first application, which is an application that supports standard protocols; The data acquisition module is used to obtain the open account and authorization code collected based on the configuration interface. The authorization code refers to the password created in the second application that supports the private protocol and matches the open account. The open account is a virtual account created by the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol, and is a virtual account corresponding to the standard protocol. The second application is an application that supports the private protocol and uses the private domain account to transfer and update information. The private domain account is the real account in the second application that corresponds to the private protocol. The first synchronization module is used to respond to the schedule display operation by generating an authentication request based on the open account and the authorization code. The authentication request instructs the second application to verify the matching between the open account and the authorization code. When the verification result returned by the second application indicates successful verification, a schedule synchronization request is generated based on account-related information. The schedule synchronization request instructs the second application to determine the corresponding private domain account based on the open account pointed to by the account-related information and return the schedule data to be synchronized related to the private domain account to the first application. The first application displays the synchronized first synchronized schedule, which is obtained by updating the original schedule of the first application based on the schedule data to be synchronized returned by the second application.

15. The apparatus according to claim 14, characterized in that, The configuration interface also includes a domain name address. The first synchronization module is further configured to generate an authentication request based on the open account and the authorization code, and send the authentication request to the second application through the domain name address. The sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code. The module receives the verification result returned by the second application, and when the verification result indicates that the verification is successful, determines the account-related information and generates a schedule synchronization request based on the account-related information.

16. The apparatus according to claim 14, characterized in that, The schedule synchronization device is also used to respond to the schedule display operation, obtain the schedule data to be synchronized in the first application, and generate a schedule synchronization request based on the open account and the schedule data to be synchronized in the first application. The schedule data to be synchronized in the first application is used to update the existing schedule in the second application.

17. The apparatus according to claim 14, characterized in that, The schedule synchronization device is also used to display the associated interface of the first application, in which the application identifier of the second application is displayed; in response to the selection operation of the application identifier of the second application, the open account is bound to the login account of the first application.

18. A schedule synchronization device, characterized in that, The device includes: The interface display module is used to respond to the information display operation of the second application and display the configuration information display interface of the second application; the second application is an application that supports private protocols and uses private domain accounts for information flow and updates; The information display module is used to display the authorization code and the open account generated based on the private domain account through the configuration information display interface; the authorization code refers to the password created in the second application that supports the private protocol and matches the open account; the private domain account is the real account in the second application that corresponds to the private protocol; the open account is a virtual account created in the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol, and the open account and the authorization code are used to transmit to the first application so that the first application responds to the schedule display operation and generates an authentication request based on the open account and the authorization code; the first application is an application that supports the standard protocol; the second synchronization module is used to respond to the... The authentication request initiated by the first application verifies the matching between the open account and the authorization code, and returns the verification result to the first application. The returned verification result is used to trigger the first application to generate a schedule synchronization request based on account-related information when the verification result indicates that the verification is successful. The account-related information includes the open account. In response to the schedule synchronization request initiated by the first application, the second application displays the synchronized second synchronized schedule. The second synchronized schedule is obtained by updating the original schedule related to the private domain account in the second application based on the schedule data to be synchronized in the first application in the schedule synchronization request. The private domain account in the second application is determined based on the open account pointed to by the account-related information.

19. The apparatus according to claim 18, characterized in that, The second synchronization module is also used to extract the schedule data to be synchronized and account-related information of the first application from the schedule synchronization request when it receives a schedule synchronization request sent by the first application. Identify the private domain account corresponding to the account information; update the original schedule related to the private domain account in the second application using the schedule data to be synchronized in the first application to obtain the second synchronized schedule; display the second synchronized schedule through the second application.

20. The apparatus according to claim 18, characterized in that, The schedule synchronization request includes a meeting identifier for a cancelled meeting. The second synchronization module is also used to respond to the schedule synchronization request initiated by the first application by cancelling the display of meeting information corresponding to the meeting identifier of the cancelled meeting through the second application; and triggering the display of message cards on the terminals of the participants in the cancelled meeting; wherein the displayed message card is used to indicate that the meeting has been cancelled.

21. A schedule synchronization device, characterized in that, The device includes: The request-response module is used to respond to a schedule synchronization request sent by a first application that supports the standard protocol, and to determine the open account to which the account-related information carried in the schedule synchronization request points; wherein, the open account is a virtual account corresponding to the standard protocol created in the second application according to the private domain account and the virtual account generation rules corresponding to the standard protocol; the second application is an application that supports the private protocol and uses the private domain account for information flow and updates; The account conversion module is used to determine the private domain account corresponding to the open account, wherein the private domain account is the real account in the second application that corresponds to the private protocol; The target synchronization module is used to acquire at least one of the schedule data to be synchronized in the first application and the schedule data to be synchronized in the second application related to the private domain account; and synchronize the schedules in the first application and the second application using the acquired schedule data to be synchronized. The schedule synchronization module is further configured to: respond to the schedule display operation, generate an authentication request based on the open account and authorization code, and send the authentication request to the second application; wherein the sent authentication request is used to instruct the second application to verify the matching between the open account and the authorization code; the authorization code refers to a password created in the second application that matches the open account; the first application receives the verification result returned by the second application, and when the verification result indicates that the verification is successful, generates a schedule synchronization request based on the account-related information.

22. The apparatus according to claim 21, characterized in that, The target synchronization module is further configured to, if the schedule synchronization request carries schedule data, use the schedule data carried in the schedule synchronization request as the schedule data to be synchronized in the first application; and update the original schedule related to the private domain account corresponding to the open account in the second application using the schedule data to be synchronized in the first application.

23. The apparatus according to claim 21, characterized in that, The target synchronization module is also used to search for change schedule data corresponding to the private domain account in the schedule data repository corresponding to the second application if the schedule synchronization request does not carry schedule data. The obtained changed schedule data is used as the schedule data to be synchronized with the private domain account in the second application; the original schedule in the first application is updated using the schedule data to be synchronized with the private domain account in the second application.

24. 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 13.

25. A computer-readable storage medium storing a computer program, 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 13.

26. A computer program product, comprising a computer program, 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 13.

Images