Cross-platform schedule synchronization implementation method and device

Abstract

The invention relates to the technical field of data synchronization, and discloses a cross-platform schedule synchronization implementation method and device.The method comprises the steps that schedule data corresponding to schedule operation executed by a target user on a first schedule program is obtained, program information of a second schedule program needing schedule synchronization is obtained, the method comprises the steps of acquiring program information of a first schedule program, performing data conversion on schedule data according to the program information to obtain target schedule data, establishing an interaction channel between the first schedule program and a second schedule program according to the program information, and transmitting the target schedule data to the second schedule program through the interaction channel, and executing schedule synchronization operation in the second schedule program based on the target schedule data. It can be seen that cross-platform schedule synchronization between different schedule programs can be achieved, second-level schedule synchronization can be achieved, schedule synchronization instantaneity is improved, information difference caused by delay is reduced, schedule management efficiency is improved, collaborative consistency of multi-platform schedule data is ensured, and user experience is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data synchronization, in particular to a cross-platform schedule synchronization implementation method and device. BACKGROUND

[0002] In the current digital office popularization, cross-platform schedule management has become a key requirement to improve work efficiency. Microsoft Outlook, as an office software with high global popularity, is commonly used in conjunction with local schedule systems (enterprise self-developed office system schedule modules, third-party schedule tools, etc.). However, the existing synchronization mechanism has significant delay, and after data synchronization, Outlook often has data residue or updates are not timely, and some operations need to be synchronized manually, resulting in low schedule management efficiency.

[0003] Currently, the existing technology mainly realizes cross-platform schedule synchronization through email pushing or intermediate database, but these methods still have the problem of long time consumption and inability to meet the real-time synchronization requirement. Therefore, it is particularly important to propose a technical solution that can improve the real-time performance of cross-platform schedule synchronization and thus improve schedule management efficiency. SUMMARY

[0004] The present application provides a cross-platform schedule synchronization implementation method and device, which can improve the real-time performance of cross-platform schedule synchronization and thus improve schedule management efficiency.

[0005] To solve the above technical problems, the first aspect of the present application discloses a cross-platform schedule synchronization implementation method, which comprises: When detecting that a target user performs a schedule operation on a first schedule program, obtaining schedule data corresponding to the schedule operation; Obtaining program information of a second schedule program that needs to perform schedule synchronization, and performing data conversion on the schedule data according to the program information to obtain target schedule data; Establishing an interaction channel between the first schedule program and the second schedule program according to the program information, and transmitting the target schedule data to the second schedule program through the interaction channel, and performing a schedule synchronization operation in the second schedule program based on the target schedule data.

[0006] As an optional implementation, in the first aspect of the present application, the program information includes a data target field of the second schedule program, and the data target field includes mandatory fields and optional fields; The data conversion on the schedule data according to the program information to obtain target schedule data comprises: Determining the data field corresponding to the schedule data, and establishing a mapping relationship between the data field and the data target field; Based on the mapping relationship and the field type requirements of the target data field, the data field is converted to obtain the converted data field; Based on the mapping relationship and the field formatting requirements of the target data field, the converted data field is subjected to format standardization processing to obtain the format-standardized data field; The data fields after format standardization are checked for integrity based on the required fields. When the data fields after format standardization pass the integrity check, the data fields after format standardization are encapsulated into target schedule data.

[0007] As an optional implementation, in the first aspect of the present invention, the program information further includes identity authentication platform information and basic address information corresponding to the second schedule program; Before establishing the interaction channel between the first schedule program and the second schedule program based on the program information, the method further includes: Register the registration application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program according to the identity authentication platform information, and receive the identity authentication parameters returned by the identity authentication platform. The identity authentication parameters include the client identifier, client password and tenant identifier corresponding to the first schedule program. The step of establishing an interaction channel between the first schedule program and the second schedule program based on the program information includes: The identity authentication information is encapsulated according to a preset target format to obtain a target request, and the target request is sent to the identity authentication platform to obtain an access token returned by the identity authentication platform. Determine whether the access token meets the preset verification conditions. When the access token meets the verification conditions, establish an interaction channel between the first scheduler and the second scheduler based on the access token and the base address information. The verification conditions include validity period verification conditions and permission verification conditions.

[0008] As an optional implementation, in a first aspect of the invention, transmitting the target schedule data to the second scheduler via the interaction channel includes: Obtain the interface document corresponding to the second schedule program, and determine the target interface corresponding to the schedule operation in the interface document; Based on the access token, the target schedule data, and the target interface, a target request is constructed and transmitted to the second scheduler through the interaction channel; Monitor whether a response is received from the second scheduler within a preset time period. If no response is received within the preset time period, retransmit the target request to the second scheduler.

[0009] As an optional implementation, in the first aspect of the present invention, the schedule operation includes a schedule creation operation, a schedule modification operation, or a schedule deletion operation, and the target interface includes a schedule creation interface, a schedule modification interface, or a schedule deletion interface. Constructing a target request based on the access token, the target schedule data, and the target interface includes: When the scheduling operation includes the scheduling creation operation, the scheduling creation interface is invoked to construct a scheduling creation request based on the access token and the target scheduling data; When the schedule operation includes the schedule modification operation, the first schedule identifier of the local schedule corresponding to the schedule modification operation is obtained from the mapping table preset in the first schedule program, and the schedule modification interface is called to construct a schedule modification request based on the access token, the target schedule data and the first schedule identifier. When the schedule operation includes the schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the preset mapping table in the first schedule program, and the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. And, the step of performing a schedule synchronization operation in the second scheduler based on the target schedule data includes: When the scheduling operation includes the scheduling creation operation, a target schedule corresponding to the target schedule data is created in the second scheduling program according to the scheduling creation request, and the schedule identifier corresponding to the target schedule returned by the second scheduling program is received; The schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in a preset mapping table in the first schedule program; When the scheduling operation includes the scheduling modification operation, the schedule corresponding to the first schedule identifier is modified in the second scheduling program according to the scheduling modification request; When the schedule operation includes the schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request, and after receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table.

[0010] As an optional implementation, in the first aspect of the present invention, when the scheduling operation includes the scheduling modification operation, the method further includes: Call the schedule query interface in the second schedule program to obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program according to the first schedule identifier; The original schedule data is compared with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, and the changed fields and redundant fields in the target schedule data are determined based on the difference data. The target schedule data is modified based on the changed fields and the redundant fields to obtain schedule change data; The step of invoking the schedule modification interface to construct a schedule modification request based on the access token, the target schedule data, and the first schedule identifier includes: The schedule modification interface is invoked to construct a schedule modification request based on the access token, the schedule change data, and the first schedule identifier.

[0011] As an optional implementation, in the first aspect of the present invention, the method further includes: After the schedule synchronization operation is performed in the second schedule program based on the target schedule data, a response result returned by the second schedule program is received, the response result including a response status code and a response body; The success of the schedule synchronization operation is determined based on the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body and stored in a preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and the target schedule data. When the response status code indicates that the schedule synchronization operation has failed, analyze the reason for the failure of the schedule synchronization operation based on the response status code; Based on the cause of failure, a failure solution is generated, and the user is redirected to the failure resolution page in the first schedule program. The failure solution guides the target user to perform the failure resolution operation. After the target user completes the failure resolution operation, the failure resolution operation result is obtained, and an error investigation record is generated based on the failure resolution operation result, the response status code, the failure reason and the failure solution, and the error investigation record is stored in the mapping table.

[0012] A second aspect of the present invention discloses a cross-platform calendar synchronization device, the device comprising: The acquisition module is used to acquire the schedule data corresponding to the schedule operation when it is detected that the target user performs a schedule operation on the first schedule program; The acquisition module is also used to acquire program information of the second schedule program that needs to be synchronized. The data conversion module is used to convert the schedule data according to the program information to obtain the target schedule data; The data transmission module is used to establish an interaction channel between the first schedule program and the second schedule program based on the program information, and to transmit the target schedule data to the second schedule program through the interaction channel. The schedule synchronization module is used to perform schedule synchronization operations in the second schedule program based on the target schedule data.

[0013] As an optional implementation, in a second aspect of the present invention, the program information includes a data target field of the second schedule program, the data target field including a required field and an optional field; The data conversion module performs data conversion on the schedule data according to the program information to obtain the target schedule data in the following specific ways: Determine the data fields corresponding to the schedule data, and establish a mapping relationship between the data fields and the target data fields; Based on the mapping relationship and the field type requirements of the target data field, the data field is converted to obtain the converted data field; Based on the mapping relationship and the field formatting requirements of the target data field, the converted data field is subjected to format standardization processing to obtain the format-standardized data field; The data fields after format standardization are checked for integrity based on the required fields. When the data fields after format standardization pass the integrity check, the data fields after format standardization are encapsulated into target schedule data.

[0014] As an optional implementation, in the second aspect of the present invention, the program information further includes identity authentication platform information and basic address information corresponding to the second schedule program; The device further includes: The registration module is used to register the registration application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program according to the identity authentication platform information before the data transmission module establishes an interaction channel between the first schedule program and the second schedule program according to the program information, and to receive the identity authentication parameters returned by the identity authentication platform, the identity authentication parameters including the client identifier, client password and tenant identifier corresponding to the first schedule program. The method by which the data transmission module establishes an interactive channel between the first schedule program and the second schedule program based on the program information specifically includes: The identity authentication information is encapsulated according to a preset target format to obtain a target request, and the target request is sent to the identity authentication platform to obtain an access token returned by the identity authentication platform. Determine whether the access token meets the preset verification conditions. When the access token meets the verification conditions, establish an interaction channel between the first scheduler and the second scheduler based on the access token and the base address information. The verification conditions include validity period verification conditions and permission verification conditions.

[0015] As an optional implementation, in a second aspect of the present invention, the method by which the data transmission module transmits the target schedule data to the second schedule program through the interaction channel specifically includes: Obtain the interface document corresponding to the second schedule program, and determine the target interface corresponding to the schedule operation in the interface document; Based on the access token, the target schedule data, and the target interface, a target request is constructed and transmitted to the second scheduler through the interaction channel; Monitor whether a response is received from the second scheduler within a preset time period. If no response is received within the preset time period, retransmit the target request to the second scheduler.

[0016] As an optional implementation, in the second aspect of the present invention, the schedule operation includes a schedule creation operation, a schedule modification operation, or a schedule deletion operation, and the target interface includes a schedule creation interface, a schedule modification interface, or a schedule deletion interface. The data transmission module constructs the target request based on the access token, the target schedule data, and the target interface in the following specific ways: When the scheduling operation includes the scheduling creation operation, the scheduling creation interface is invoked to construct a scheduling creation request based on the access token and the target scheduling data; When the schedule operation includes the schedule modification operation, the first schedule identifier of the local schedule corresponding to the schedule modification operation is obtained from the mapping table preset in the first schedule program, and the schedule modification interface is called to construct a schedule modification request based on the access token, the target schedule data and the first schedule identifier. When the schedule operation includes the schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the preset mapping table in the first schedule program, and the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. Furthermore, the method by which the schedule synchronization module performs schedule synchronization operations in the second schedule program based on the target schedule data specifically includes: When the scheduling operation includes the scheduling creation operation, a target schedule corresponding to the target schedule data is created in the second scheduling program according to the scheduling creation request, and the schedule identifier corresponding to the target schedule returned by the second scheduling program is received; The schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in a preset mapping table in the first schedule program; When the scheduling operation includes the scheduling modification operation, the schedule corresponding to the first schedule identifier is modified in the second scheduling program according to the scheduling modification request; When the schedule operation includes the schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request, and after receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table.

[0017] As an optional implementation, in a second aspect of the present invention, the acquisition module is further configured to, when the schedule operation includes the schedule modification operation, call the schedule query interface in the second schedule program to obtain the original schedule data stored in the second schedule program corresponding to the schedule modification operation according to the first schedule identifier; The device further includes: The comparison module is used to compare the original schedule data with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, and to determine the changed fields and redundant fields in the target schedule data based on the difference data. The modification module is used to modify the target schedule data according to the changed fields and the redundant fields to obtain schedule change data; The data transmission module invokes the schedule modification interface to construct a schedule modification request based on the access token, the target schedule data, and the first schedule identifier. Specifically, this includes the following methods: The schedule modification interface is invoked to construct a schedule modification request based on the access token, the schedule change data, and the first schedule identifier.

[0018] As an optional implementation, in a second aspect of the invention, the apparatus further includes: The receiving module is configured to receive a response result returned by the second schedule program after the schedule synchronization module performs a schedule synchronization operation based on the target schedule data. The response result includes a response status code and a response body. The judgment module is used to determine whether the schedule synchronization operation is successful based on the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body, and the schedule synchronization record is stored in a preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and the target schedule data. The analysis module is used to analyze the reason for the failure of the schedule synchronization operation based on the response status code when the response status code indicates that the schedule synchronization operation has failed. The generation module is used to generate a failure solution based on the failure reason and jump to the failure resolution page in the first schedule program to guide the target user to perform the failure resolution operation through the failure solution; The acquisition module is further configured to acquire the failure resolution operation result after the target user completes the failure resolution operation, generate an error investigation record based on the failure resolution operation result, the response status code, the failure reason and the failure solution, and store the error investigation record in the mapping table.

[0019] A third aspect of the present invention discloses another cross-platform calendar synchronization device, the device comprising: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute some or all of the steps in the cross-platform schedule synchronization implementation method according to any of the first aspects of the present invention.

[0020] The fourth aspect of the present invention discloses a computer storage medium storing computer instructions, which, when invoked, are used to execute some or all of the steps in the cross-platform schedule synchronization implementation method described in any of the first aspects of the present invention.

[0021] Compared with the prior art, the present invention has the following beneficial effects: In this embodiment of the invention, schedule data corresponding to the schedule operation performed by the target user on a first scheduler program is obtained; program information of a second scheduler program that needs to be synchronized is obtained; and the schedule data is transformed according to the program information to obtain the target schedule data. An interaction channel is established between the first and second scheduler programs based on the program information, and the target schedule data is transmitted to the second scheduler program through the interaction channel. Based on the target schedule data, a schedule synchronization operation is performed in the second scheduler program. Therefore, implementing this invention enables cross-platform schedule synchronization between different scheduler programs, achieving second-level schedule synchronization, improving the immediacy of schedule synchronization, reducing information gaps caused by delays, improving schedule management efficiency, ensuring the collaborative consistency of schedule data across multiple platforms, and enhancing the user experience. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a flowchart illustrating a cross-platform calendar synchronization method disclosed in an embodiment of the present invention; Figure 2 This is a flowchart illustrating another cross-platform calendar synchronization method disclosed in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a cross-platform schedule synchronization device disclosed in an embodiment of the present invention; Figure 4 This is a schematic diagram of another cross-platform calendar synchronization device disclosed in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of another cross-platform schedule synchronization device disclosed in an embodiment of the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.

[0026] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0027] This invention discloses a cross-platform calendar synchronization method and apparatus, which enables cross-platform calendar synchronization between different calendar programs, achieving second-level calendar synchronization, improving the immediacy of calendar synchronization, reducing information gaps caused by delays, improving calendar management efficiency, ensuring the collaborative consistency of calendar data across multiple platforms, and enhancing the user experience. Detailed descriptions follow.

[0028] Example 1 Please see Figure 1 , Figure 1 This is a flowchart illustrating a cross-platform calendar synchronization method disclosed in an embodiment of the present invention. Figure 1 The described cross-platform calendar synchronization method can be applied to a cross-platform calendar synchronization device, which may include a smart server or a smart platform. The smart server may include a local server or a cloud server, and this embodiment of the invention does not limit the scope. Figure 1 As shown, this cross-platform calendar synchronization implementation method can include the following operations: 101. When a target user is detected performing a schedule operation on the first schedule program, obtain the schedule data corresponding to the schedule operation.

[0029] In this embodiment of the invention, optionally, the first schedule program can represent the user's local schedule program, such as the built-in schedule module of an enterprise's self-developed office system, a third-party professional schedule tool, etc. A hook function-based listening mechanism can be set in the first schedule program to detect the schedule operations performed by the target user on the first schedule program. The schedule operations can include schedule creation operations, schedule modification operations, or schedule deletion operations. The schedule data corresponding to the schedule operation can include the schedule unique identifier of the schedule corresponding to the schedule operation, the operation time, the schedule core data, etc. The schedule core data can include the title, content description, start time, end time, reminder time, etc., which are not limited in this invention.

[0030] 102. Obtain the program information of the second schedule program that needs to be synchronized, and perform data transformation on the schedule data according to the program information to obtain the target schedule data.

[0031] In this embodiment of the invention, optionally, the second schedule program may include the Microsoft Outlook calendar program. The program information of the second schedule program may include the data target fields of the second schedule program, such as title field, content description field, start time field, end time field, reminder time field, location field, participant field, etc. Since the data formats of the first schedule program and the second schedule program are different, the schedule data is converted according to the program information to obtain the target schedule data.

[0032] 103. Establish an interaction channel between the first schedule program and the second schedule program based on the program information, and transmit the target schedule data to the second schedule program through the interaction channel. Perform schedule synchronization operation in the second schedule program based on the target schedule data.

[0033] In this embodiment of the invention, optionally, the program information may also include the identity authentication platform information and basic address information corresponding to the second schedule program, which are used to establish an interaction channel between the first schedule program and the second schedule program. The target schedule data can be transmitted to the second schedule program through the interaction channel, and then the corresponding API is called based on the target schedule data to perform a schedule synchronization operation in the second schedule program. For example, the schedule creation operation calls "POST / me / events", the schedule modification operation calls "PATCH / me / events / {id}", or the schedule deletion operation calls "DELETE / me / events / {id}". The entire process from the user completing the schedule operation in the first schedule program to the implementation of the schedule synchronization operation in the second schedule program is controlled within a second, reducing the information gap caused by delay.

[0034] It is evident that implementation Figure 1The described cross-platform schedule synchronization method can obtain schedule data corresponding to the schedule operations performed by the target user on the first schedule program, obtain program information of the second schedule program that needs to be synchronized, and perform data transformation on the schedule data according to the program information to obtain the target schedule data. Based on the program information, an interaction channel is established between the first and second schedule programs, and the target schedule data is transmitted to the second schedule program through the interaction channel. Based on the target schedule data, the schedule synchronization operation is performed on the second schedule program, realizing cross-platform schedule synchronization between different schedule programs, achieving second-level schedule synchronization, improving the immediacy of schedule synchronization, reducing information gaps caused by delays, improving schedule management efficiency, ensuring the collaborative consistency of schedule data across multiple platforms, and improving the user experience.

[0035] In an optional embodiment, the program information also includes the identity authentication platform information and basic address information corresponding to the second scheduling program; Before establishing an interaction channel between the first and second schedule programs based on the program information, this cross-platform schedule synchronization method may also include the following operations: Register the application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program based on the identity authentication platform information, and receive the identity authentication parameters returned by the identity authentication platform. The identity authentication parameters include the client identifier, client password and tenant identifier corresponding to the first schedule program. Establishing an interaction channel between the first and second schedule programs based on program information can include the following operations: The identity authentication information is encapsulated according to the preset target format to obtain the target request, and the target request is sent to the identity authentication platform to obtain the access token returned by the identity authentication platform. Determine whether the access token meets the preset verification conditions. When the access token meets the verification conditions, establish an interaction channel between the first scheduler and the second scheduler based on the access token and the base address information. The verification conditions include validity period verification conditions and permission verification conditions.

[0036] In this optional embodiment, the program information may also include identity authentication platform information and basic address information corresponding to the second schedule program. The identity authentication platform information may include the web address of the identity authentication platform. The identity authentication platform may be part of the second schedule program or a dedicated platform independent of the second schedule program. The basic address information is used to build an interaction channel, and this embodiment does not limit it.

[0037] In this optional embodiment, the first scheduler's corresponding application can be registered on the identity authentication platform corresponding to the second scheduler based on the identity authentication platform information, and the corresponding API call permissions can be granted. Then, the identity authentication parameters returned by the identity authentication platform can be received. The identity authentication parameters include the client identifier, client password, and tenant identifier corresponding to the first scheduler. The identity authentication information can be encapsulated according to a preset target format to obtain the target request. For example, the client identifier, client password, and tenant identifier can be encapsulated in a form format, and the target request can be sent to the identity authentication platform. Specifically, a POST request can be sent to the token acquisition address of the identity authentication platform to obtain the access token returned by the identity authentication platform. This embodiment does not limit this.

[0038] In this optional embodiment, it can be determined whether the access token meets the preset verification conditions. The verification conditions may include validity period verification conditions and permission verification conditions, that is, verifying whether the access token has expired and verifying whether the access token meets the schedule synchronization permission requirements of the second target program. When the access token meets the verification conditions, an interaction channel between the first schedule program and the second schedule program is established based on the access token and the base address information. This embodiment does not limit this.

[0039] As can be seen, implementing this optional embodiment can register the registration application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program based on the identity authentication platform information, receive the identity authentication parameters returned by the identity authentication platform, encapsulate the identity authentication information according to the preset target format to obtain the target request, and send the target request to the identity authentication platform to obtain the access token returned by the identity authentication platform. It then determines whether the access token meets the preset verification conditions. When the access token meets the verification conditions, it establishes an interaction channel between the first schedule program and the second schedule program based on the access token and the base address information. By establishing a reliable and secure interaction channel through the access token identity authentication mechanism, it prevents unauthorized access, ensures the security of data transmission, and ensures the legality and controllability of the channel by verifying the validity period and permissions of the token, thereby reducing the risk of data leakage or malicious tampering.

[0040] In another alternative embodiment, transmitting the target schedule data to the second scheduler via an interactive channel may include the following operations: Obtain the interface document corresponding to the second schedule procedure, and determine the target interface corresponding to the schedule operation in the interface document; Based on the access token, target schedule data, and target interface, construct the target request and transmit the target request to the second scheduler through the interaction channel; Listen for a response from the second scheduler within a preset time period. If no response is received within the preset time period, retransmit the target request to the second scheduler.

[0041] In this optional embodiment, optionally, the interface document corresponding to the second scheduler is obtained, i.e., the API document of Microsoft Outlook, and the target interface corresponding to the schedule operation is determined in the interface document, i.e., the target API interface corresponding to the schedule operation is determined, such as the schedule time interface of the Microsoft Graph API; optionally, the target interface information of the target interface can also be determined, which may include the request method, request header format and request body parameter requirements, etc., which are not limited in this embodiment.

[0042] In this optional embodiment, the target request can be constructed based on the access token, target schedule data, target interface, and target interface information. Specifically, the access token (access_token) is carried in the request header, with the format "Authorization: Bearer{access_token}", and the target schedule data is encapsulated in the request body, with the request body format satisfying the target interface information. Then, the target request is transmitted to the second scheduler through the interaction channel. This embodiment does not impose any limitations.

[0043] In this optional embodiment, it is possible to monitor whether a response result is received from the second scheduler within a preset time period, such as whether a response result is received from the second scheduler within 10 seconds. If no response result is received within the preset time period, the target request is retransmitted to the second scheduler. If a response result is received within the preset time period, the response result is stored. This embodiment does not impose any limitations on this.

[0044] As can be seen, implementing this optional embodiment can obtain the interface document corresponding to the second scheduler, determine the target interface corresponding to the schedule operation in the interface document, construct a target request based on the access token, target schedule data, and target interface, and transmit the target request to the second scheduler through the interaction channel. It listens for whether a response result is received from the second scheduler within a preset time. If no response result is received within the preset time, the target request is retransmitted to the second scheduler, which improves the stability and success rate of data transmission. The timeout retransmission mechanism can effectively cope with temporary network fluctuations or server response delays and reduce synchronization interruption problems caused by momentary failures.

[0045] In another optional embodiment, the schedule operation includes a schedule creation operation, a schedule modification operation, or a schedule deletion operation, and the target interface includes a schedule creation interface, a schedule modification interface, or a schedule deletion interface. Constructing a target request based on the access token, target schedule data, and target API can include the following operations: When a scheduling operation includes a schedule creation operation, the schedule creation interface is called to construct a schedule creation request based on the access token and the target schedule data. When a scheduling operation includes a scheduling modification operation, the first schedule identifier of the local schedule corresponding to the scheduling modification operation is obtained from the mapping table preset in the first scheduling program, and the scheduling modification interface is called to construct a scheduling modification request based on the access token, the target schedule data and the first schedule identifier. When the scheduling operation includes a schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the mapping table preset in the first scheduling program, and the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. Furthermore, performing schedule synchronization operations in the second scheduler based on the target schedule data may include the following operations: When the scheduling operation includes a schedule creation operation, the target schedule corresponding to the target schedule data is created in the second scheduling program according to the schedule creation request, and the schedule identifier corresponding to the target schedule returned by the second scheduling program is received. The schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in the preset mapping table in the first schedule program; When the scheduling operation includes a schedule modification operation, the schedule corresponding to the first schedule identifier is modified in the second scheduling program according to the schedule modification request; When a schedule operation includes a schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request. After receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table.

[0046] In this optional embodiment, the schedule operation may include a schedule creation operation, a schedule modification operation, or a schedule deletion operation. The target interface may include a schedule creation interface, a schedule modification interface, or a schedule deletion interface. The request method for the schedule creation interface is POST, the request method for the schedule modification interface is PATCH, and the request method for the schedule deletion interface is DELETE. This embodiment does not impose any limitations.

[0047] In this optional embodiment, when the scheduling operation includes a scheduling creation operation, a scheduling creation interface can be called to construct a scheduling creation request based on the access token and target scheduling data, i.e., calling the scheduling creation API, such as "POST / me / events", and writing the target scheduling data into the request body to construct the scheduling creation request; when the scheduling operation includes a scheduling modification operation, the first scheduling identifier of the local scheduling corresponding to the scheduling modification operation can be obtained from a pre-set mapping table in the first scheduling program. The first scheduling program has a pre-set mapping table, which can be used to store the scheduling information of all local scheduling in the first scheduling program. The scheduling information can include the first scheduling identifier and the status of the local scheduling, such as draft status, valid status, completed status, canceled status, expired status, deleted status, pending status, etc. At least one of the following states—synchronization status, synchronization success status, synchronization failure status, and partial synchronization status—can be used to construct a schedule modification request by calling the schedule modification interface based on the access token, target schedule data, and first schedule identifier. This involves calling the schedule modification API, for example, "PATCH / me / events / {id}", to write the target schedule data containing the modification content into the request body to construct a schedule creation request. When the schedule operation includes a schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the pre-set mapping table in the first schedule program. Then, the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. This involves calling the schedule deletion API "DELETE / me / events / {id}" to construct a deletion request without a request body. This embodiment does not impose limitations on this.

[0048] In this optional embodiment, when the schedule operation includes a schedule creation operation, a target schedule corresponding to the target schedule data is created in the second schedule program according to the schedule creation request, and the schedule identifier corresponding to the target schedule returned by the second schedule program is received. When creating the target schedule in the second schedule program, a unique schedule identifier corresponding to the target schedule is generated, and the schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in a preset mapping table in the first schedule program so as to achieve synchronization when operating on the schedule in the future. When the schedule operation includes a schedule modification operation, the schedule corresponding to the first schedule identifier is modified in the second schedule program according to the schedule modification request. Specifically, the corresponding schedule is determined in the second schedule program according to the first schedule identifier, and the schedule is modified according to the target schedule data. When the schedule operation includes a schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request. Specifically, the corresponding schedule is determined in the second schedule program according to the second schedule identifier, and the schedule is deleted. After receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table. This embodiment does not limit this.

[0049] As can be seen, implementing this optional embodiment can achieve different interface calls, data processing, and status recording for three types of schedule operations: creation, modification, and deletion. This improves the accurate synchronization of different types of schedule operations on both platforms. By associating local and remote identifiers through a mapping table, it solves the problem of chaotic correspondence between schedule operations across platforms and improves the consistency of data on both platforms.

[0050] In yet another optional embodiment, when the scheduling operation includes a schedule modification operation, the cross-platform schedule synchronization implementation method may further include the following operations: Call the schedule query interface in the second schedule program to obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program based on the first schedule identifier; The original schedule data is compared with the target schedule data to obtain the difference data between the original schedule data and the target schedule data. Based on the difference data, the changed fields and redundant fields in the target schedule data are determined. Modify the target schedule data based on the changed and redundant fields to obtain the schedule change data; The process of calling the schedule modification interface to construct a schedule modification request based on the access token, the target schedule data, and the first schedule identifier can include the following operations: The schedule modification interface is invoked to construct a schedule modification request based on the access token, schedule change data, and the first schedule identifier.

[0051] In this optional embodiment, when the scheduling operation includes a scheduling modification operation, the scheduling query interface in the second scheduling program can be called to obtain the original scheduling data corresponding to the scheduling modification operation stored in the second scheduling program according to the first scheduling identifier. Then, the original scheduling data is compared with the target scheduling data to obtain the difference data between the original scheduling data and the target scheduling data. Based on the difference data, the changed fields and redundant fields in the target scheduling data are determined. The changed fields may include the name and content of the changed fields, such as the "end time" field and the specific time content of the modified end time. The redundant fields may include unchanged fields, structured standard fields, etc., which are not limited in this embodiment.

[0052] In this optional embodiment, the target schedule data can be modified based on the changed fields and redundant fields to obtain schedule change data. That is, only the changed fields and necessary fields such as the identification-related fields are retained, and the redundant fields that have not been changed are deleted. Then, the schedule modification interface is called to construct a schedule modification request based on the access token, the schedule change data and the first schedule identifier, thereby reducing the amount of data transmission and improving efficiency.

[0053] As can be seen, implementing this optional embodiment can call the schedule query interface in the second schedule program, obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program according to the first schedule identifier, compare the original schedule data with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, determine the changed fields and redundant fields in the target schedule data according to the difference data, modify the target schedule data according to the changed fields and redundant fields to obtain the schedule changed data, call the schedule modification interface to construct a schedule modification request according to the access token, schedule changed data and the first schedule identifier. In the modification operation, the differential data is updated, which reduces the amount of data transmission, reduces network bandwidth occupation and transmission latency, improves synchronization efficiency, and avoids conflicts or errors that may be caused by redundant data transmission, further improving the accuracy and stability of the schedule modification operation.

[0054] In yet another optional embodiment, the cross-platform calendar synchronization implementation method may further include the following operations: After the second schedule program performs a schedule synchronization operation based on the target schedule data, the response result returned by the second schedule program is received. The response result includes a response status code and a response body. The success of the schedule synchronization operation is determined by the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body and stored in the preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and target schedule data. When the response status code indicates that the schedule synchronization operation has failed, analyze the reason for the failure based on the response status code; Generate a failure solution based on the cause of failure, and redirect the user to the failure resolution page in the first schedule program to guide the target user to perform the failure resolution operation through the failure solution; After the target user completes the failure resolution operation, the failure resolution operation result is obtained, and an error investigation record is generated based on the failure resolution operation result, response status code, failure reason and failure solution, and the error investigation record is stored in the mapping table.

[0055] In this optional embodiment, after performing a schedule synchronization operation based on the target schedule data in the second schedule program, a response result returned by the second schedule program can be received. The response result may include a response status code and a response body. The response status code may be used to indicate whether the synchronization operation was successful, and to indicate the specific reason for failure when the corresponding operation fails. The response body may carry relevant data of the returned synchronization operation, such as the identifier of the schedule corresponding to the synchronization operation in the second schedule program, the synchronization operation time, and the error description when the synchronization operation fails. This embodiment does not limit this.

[0056] In this optional embodiment, the success of the schedule synchronization operation can be determined based on the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body and stored in a preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and target schedule data. The schedule identification information includes the local schedule identification corresponding to the schedule operation in the first schedule program and the schedule identification corresponding to the schedule operation in the second schedule program. This embodiment does not limit this.

[0057] In this optional embodiment, when the response status code indicates that the schedule synchronization operation has failed, the failure reason can be analyzed based on the response status code. The failure reason may include one or more of the following: authentication error, data format error, and network / service error. A failure solution can be generated based on the failure reason, and the user can be redirected to the failure resolution page in the first schedule program to guide the target user to perform the failure resolution operation. For example, when the failure reason includes an authentication error, the user can be redirected to the API configuration page, prompting them to check whether the tenant identifier, client identifier, and client password are entered accurately, and providing an option to re-verify so that the user can obtain the access token again. When the failure reason includes a data format error, a data verification tool can be invoked to compare the target schedule data with the field specifications of the second schedule program, generate a format difference report, and mark the mismatched fields and the error reasons. When the failure reason includes a network / service error, network connectivity detection can be initiated to detect the network link between the API server of the first schedule program and the second schedule program, generate a link detection report, including packet loss rate, latency, etc. If a network anomaly is detected, an alarm notification is issued. This embodiment does not limit this.

[0058] In this optional embodiment, after the target user completes the failure resolution operation, the failure resolution operation result can be obtained, and an error investigation record can be generated based on the failure resolution operation result, response status code, failure reason and failure solution. The error investigation record is stored in a mapping table for reference in the event of a similar error in the future to generate a solution. This embodiment does not limit this.

[0059] As can be seen, implementing this optional embodiment can achieve traceability of the synchronization process and rapid problem location by recording synchronization results, analyzing the causes of failure, providing solutions, and generating troubleshooting records. This allows users to intuitively understand the synchronization status, efficiently troubleshoot synchronization failures to solve problems, improve user experience, and enhance system maintainability.

[0060] In yet another alternative embodiment, constructing a target request based on the access token, target schedule data, and target interface may include the following operations: Determine the single request data volume threshold corresponding to the target interface and the data volume of the target schedule data, and determine whether the data volume of the target schedule data is greater than the single request data volume threshold; When the data volume of the target schedule data exceeds the single request data volume threshold, the target schedule data is compressed according to the preset compression algorithm and the single request data volume threshold to obtain the compressed target schedule data. Generate a data verification code for the compressed target schedule data. Generate a request header based on the data verification code and the access token. Construct a target request based on the request header, the compressed target schedule data, and the target interface. The data verification code is used to verify the integrity of the target schedule data in the second schedule program.

[0061] In this optional embodiment, when the data volume of the target schedule data is greater than the single request data volume threshold, the target schedule data can be compressed according to a preset compression algorithm and the single request data volume threshold, such as a lightweight compression algorithm, to control the compressed data volume within the single request data volume limit specified by the API of the second schedule program, such as within 4MB. This embodiment does not impose any limitations.

[0062] As can be seen, implementing this optional embodiment can reduce the amount of data transmitted over the network through data compression, reduce bandwidth usage and transmission latency, and ensure that data is not tampered with or damaged during transmission through a data verification mechanism, thereby improving the reliability of data transmission.

[0063] Example 2 Please see Figure 2 , Figure 2 This is a flowchart illustrating a cross-platform calendar synchronization method disclosed in an embodiment of the present invention. Figure 2 The described cross-platform calendar synchronization method can be applied to a cross-platform calendar synchronization device, which may include a smart server or a smart platform. The smart server may include a local server or a cloud server, and this embodiment of the invention does not limit the scope. Figure 2 As shown, this cross-platform calendar synchronization implementation method can include the following operations: 201. When a target user is detected performing a schedule operation on the first schedule program, obtain the schedule data corresponding to the schedule operation.

[0064] 202. Obtain the program information of the second schedule program that needs to be synchronized.

[0065] 203. Determine the data fields corresponding to the schedule data and establish the mapping relationship between the data fields and the target data fields.

[0066] In this embodiment of the invention, optionally, the program information includes data target fields of the second schedule program. The data target fields may include required fields and optional fields. For example, required fields may include a title field, a start time field, an end time field, a reminder time field, etc. Optional fields may include a content description field, a location field, a participant field, etc. The mapping relationship between data fields and data target fields may include a one-to-one correspondence between the field name of each data field corresponding to the schedule data and the field name of each data target field of the second schedule program, and / or, a one-to-one correspondence between the unique identifier of each data field corresponding to the schedule data and the unique identifier of each data target field of the second schedule program. This invention does not impose any limitations.

[0067] 204. Based on the mapping relationship and the field type requirements of the target data field, perform data type conversion on the data field to obtain the converted data field.

[0068] Optionally, in this embodiment of the invention, the data field can be converted according to the mapping relationship and the field type requirements of the target data field to obtain the converted data field. The field type requirements of the target data field may include the attribute name requirements and data type requirements of each field. Taking the reminder time field as an example, the attribute name of the field can be converted from "noticeTime" in the first schedule program to "ReminderMinutesStart" as required by the second schedule program, and the data type of the field can be converted from "2025-07-08 16:00:00 +0800" in the first schedule program to "2025-07-08T14:00:00+08:00" as required by the second schedule program, thereby obtaining the converted reminder time field. This invention does not impose any limitations.

[0069] 205. Based on the mapping relationship and the field formatting requirements of the target data field, perform format standardization processing on the converted data fields to obtain the format-standardized data fields.

[0070] In this embodiment of the invention, optionally, the converted data fields can be formatted according to the mapping relationship and the field formatting requirements of the target data fields to obtain formatted data fields. For example, JSON formatting can be performed, special characters not supported by the second schedule program in the data fields can be replaced or removed, and structured data (such as attendee information) can be reorganized according to the target format. This invention does not limit the scope of the invention.

[0071] 206. Perform integrity checks on the standardized data fields based on the required fields. When the standardized data fields pass the integrity check, encapsulate them into the target schedule data.

[0072] Optionally, in this embodiment of the invention, the data fields after format standardization can be checked for completeness based on the required fields, that is, it can be determined whether the content of the required fields is missing. When the required fields are missing, they can be filled according to the default value of the required fields or an error message can be returned to the user to supplement them. When the data fields after format standardization pass the completeness check, the data fields after format standardization are encapsulated into the target schedule data. This invention does not impose any limitations.

[0073] 207. Establish an interaction channel between the first schedule program and the second schedule program based on the program information, and transmit the target schedule data to the second schedule program through the interaction channel. Perform schedule synchronization operation in the second schedule program based on the target schedule data.

[0074] In this embodiment of the invention, for other descriptions of steps 201, 202 and 207, please refer to the detailed description of steps 101-103 in Embodiment 1 of the invention. These descriptions will not be repeated in this embodiment of the invention.

[0075] It is evident that implementation Figure 2 The described cross-platform schedule synchronization method can obtain schedule data corresponding to the schedule operations performed by the target user on the first schedule program, obtain program information of the second schedule program that needs to be synchronized, determine the data fields corresponding to the schedule data, establish a mapping relationship between the data fields and the target data fields, perform data type conversion, format standardization processing, and integrity verification, and then encapsulate the format-standardized data fields into target schedule data. This ensures that the original schedule data of the first schedule program can accurately adapt to the field requirements of the second schedule program, reducing synchronization failures caused by data format incompatibility, improving the accuracy and reliability of data conversion, and thus laying the data foundation for subsequent data synchronization operations. An interaction channel is established between the first and second schedule programs based on the program information, and the target schedule data is transmitted to the second schedule program through the interaction channel. Based on the target schedule data, the second schedule program performs schedule synchronization operations, realizing cross-platform schedule synchronization between different schedule programs, achieving second-level schedule synchronization, improving the immediacy of schedule synchronization, reducing information gaps caused by delays, improving schedule management efficiency, ensuring the collaborative consistency of schedule data across multiple platforms, and improving the user experience.

[0076] Example 3 Please see Figure 3 , Figure 3 This is a schematic diagram of a cross-platform schedule synchronization device disclosed in an embodiment of the present invention. Figure 3The described cross-platform schedule synchronization device may include a smart server or a smart platform, where the smart server may be a local server or a cloud server; this embodiment of the invention does not limit the scope. Figure 3 As shown, the cross-platform calendar synchronization device may include: The acquisition module 301 is used to acquire the schedule data corresponding to the schedule operation when it is detected that the target user performs a schedule operation on the first schedule program; The acquisition module 301 is also used to acquire program information of the second schedule program that needs to be synchronized. Data conversion module 302 is used to convert schedule data according to program information to obtain target schedule data; Data transmission module 303 is used to establish an interaction channel between the first schedule program and the second schedule program based on program information, and to transmit the target schedule data to the second schedule program through the interaction channel. The schedule synchronization module 304 is used to perform schedule synchronization operations in the second schedule program based on the target schedule data.

[0077] It is evident that implementation Figure 3 The described cross-platform schedule synchronization device can acquire schedule data corresponding to the schedule operation performed by the target user on a first schedule program, acquire program information of a second schedule program that needs to be synchronized, and perform data transformation on the schedule data according to the program information to obtain target schedule data. It establishes an interaction channel between the first and second schedule programs based on the program information, and transmits the target schedule data to the second schedule program through the interaction channel. Based on the target schedule data, it performs schedule synchronization operations on the second schedule program, achieving cross-platform schedule synchronization between different schedule programs. This achieves second-level schedule synchronization, improves the immediacy of schedule synchronization, reduces information gaps caused by delays, improves schedule management efficiency, ensures the collaborative consistency of schedule data across multiple platforms, and enhances the user experience.

[0078] In an optional embodiment, such as Figure 4 As shown, the program information includes the data target fields of the second schedule program, which include required fields and optional fields; The data conversion module 302 performs data conversion on the schedule data according to the program information, and the specific methods for obtaining the target schedule data include: Identify the data fields corresponding to the schedule data and establish a mapping relationship between the data fields and the target data fields; Based on the mapping relationship and the field type requirements of the target data field, the data field is converted to obtain the converted data field; Based on the mapping relationship and the field formatting requirements of the target data field, the converted data fields are standardized to obtain the standardized data fields. The data fields after format standardization are validated for integrity based on the required fields. When the data fields after format standardization pass the integrity validation, they are encapsulated into the target schedule data.

[0079] It is evident that implementation Figure 4 The described cross-platform schedule synchronization device can acquire schedule data corresponding to the schedule operations performed by the target user on a first schedule program, acquire program information of a second schedule program that needs to be synchronized, determine the data fields corresponding to the schedule data, establish a mapping relationship between the data fields and the target data fields, perform data type conversion, format standardization processing, and integrity verification, and then encapsulate the format-standardized data fields into target schedule data. This ensures that the original schedule data of the first schedule program can accurately adapt to the field requirements of the second schedule program, reducing synchronization failures caused by data format incompatibility, improving the accuracy and reliability of data conversion, and laying the data foundation for subsequent data synchronization operations. An interaction channel is established between the first and second schedule programs based on the program information, and the target schedule data is transmitted to the second schedule program through this interaction channel. Based on the target schedule data, the second schedule program performs schedule synchronization operations, achieving cross-platform schedule synchronization between different schedule programs. This achieves second-level schedule synchronization, improves the immediacy of schedule synchronization, reduces information gaps caused by delays, improves schedule management efficiency, ensures the collaborative consistency of schedule data across multiple platforms, and enhances the user experience.

[0080] In another alternative embodiment, such as Figure 4 As shown, the program information also includes the identity authentication platform information and basic address information corresponding to the second schedule program; This cross-platform calendar synchronization device may also include: The registration module 305 is used to register the registration application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program according to the identity authentication platform information before the data transmission module 303 establishes the interaction channel between the first schedule program and the second schedule program according to the program information, and to receive the identity authentication parameters returned by the identity authentication platform. The identity authentication parameters include the client identifier, client password and tenant identifier corresponding to the first schedule program. The specific methods by which the data transmission module 303 establishes an interaction channel between the first schedule program and the second schedule program based on program information include: The identity authentication information is encapsulated according to the preset target format to obtain the target request, and the target request is sent to the identity authentication platform to obtain the access token returned by the identity authentication platform. Determine whether the access token meets the preset verification conditions. When the access token meets the verification conditions, establish an interaction channel between the first scheduler and the second scheduler based on the access token and the base address information. The verification conditions include validity period verification conditions and permission verification conditions.

[0081] It is evident that implementation Figure 4 The described cross-platform schedule synchronization device can register the application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program based on the identity authentication platform information, and receive the identity authentication parameters returned by the identity authentication platform. It encapsulates the identity authentication information according to the preset target format to obtain the target request, and sends the target request to the identity authentication platform to obtain the access token returned by the identity authentication platform. It determines whether the access token meets the preset verification conditions. When the access token meets the verification conditions, it establishes an interaction channel between the first schedule program and the second schedule program based on the access token and the base address information. It establishes a reliable and secure interaction channel through the access token identity authentication mechanism to prevent unauthorized access, ensure the security of data transmission, and ensure the legality and controllability of the channel by verifying the validity period and permissions of the token, thereby reducing the risk of data leakage or malicious tampering.

[0082] In yet another alternative embodiment, such as Figure 4 As shown, the specific method by which the data transmission module 303 transmits the target schedule data to the second schedule program through the interactive channel includes: Obtain the interface document corresponding to the second schedule procedure, and determine the target interface corresponding to the schedule operation in the interface document; Based on the access token, target schedule data, and target interface, construct the target request and transmit the target request to the second scheduler through the interaction channel; Listen for a response from the second scheduler within a preset time period. If no response is received within the preset time period, retransmit the target request to the second scheduler.

[0083] It is evident that implementation Figure 4 The described cross-platform calendar synchronization device can obtain the interface document corresponding to the second calendar program, determine the target interface corresponding to the calendar operation in the interface document, construct the target request based on the access token, target calendar data and target interface, and transmit the target request to the second calendar program through the interaction channel. It listens for whether the response result returned by the second calendar program is received within a preset time. If no response result is received within the preset time, the target request is retransmitted to the second calendar program, which improves the stability and success rate of data transmission. The timeout retransmission mechanism can effectively cope with temporary network fluctuations or server response delays and reduce synchronization interruption problems caused by momentary failures.

[0084] In yet another alternative embodiment, such as Figure 4 As shown, schedule operations include schedule creation, schedule modification, or schedule deletion, and the target interfaces include schedule creation, schedule modification, or schedule deletion interfaces. The data transmission module 303 constructs the target request based on the access token, target schedule data, and target interface in the following specific ways: When a scheduling operation includes a schedule creation operation, the schedule creation interface is called to construct a schedule creation request based on the access token and the target schedule data. When a scheduling operation includes a scheduling modification operation, the first schedule identifier of the local schedule corresponding to the scheduling modification operation is obtained from the mapping table preset in the first scheduling program, and the scheduling modification interface is called to construct a scheduling modification request based on the access token, the target schedule data and the first schedule identifier. When the scheduling operation includes a schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the mapping table preset in the first scheduling program, and the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. Furthermore, the specific methods by which the schedule synchronization module 304 performs schedule synchronization operations in the second schedule program based on the target schedule data include: When the scheduling operation includes a schedule creation operation, the target schedule corresponding to the target schedule data is created in the second scheduling program according to the schedule creation request, and the schedule identifier corresponding to the target schedule returned by the second scheduling program is received. The schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in the preset mapping table in the first schedule program; When the scheduling operation includes a schedule modification operation, the schedule corresponding to the first schedule identifier is modified in the second scheduling program according to the schedule modification request; When a schedule operation includes a schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request. After receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table.

[0085] It is evident that implementation Figure 4 The described cross-platform schedule synchronization device can implement different interface calls, data processing, and status recording for three types of schedule operations: creation, modification, and deletion. This improves the accurate synchronization of different types of schedule operations on both platforms. By associating local and remote identifiers through a mapping table, it solves the problem of chaotic correspondence between cross-platform schedule operations and improves the consistency of data on both platforms.

[0086] In yet another alternative embodiment, such asFigure 4 As shown, the acquisition module 301 is also used to call the schedule query interface in the second schedule program when the schedule operation includes a schedule modification operation, and obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program according to the first schedule identifier. This cross-platform calendar synchronization device may also include: The comparison module 306 is used to compare the original schedule data with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, and to determine the changed fields and redundant fields in the target schedule data based on the difference data. Modification module 307 is used to modify the target schedule data based on the changed fields and redundant fields to obtain the schedule change data; The specific methods by which the data transmission module 303 constructs a schedule modification request based on the access token, target schedule data, and first schedule identifier when calling the schedule modification interface include: The schedule modification interface is invoked to construct a schedule modification request based on the access token, schedule change data, and the first schedule identifier.

[0087] It is evident that implementation Figure 4 The described cross-platform schedule synchronization device can call the schedule query interface in the second schedule program, obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program according to the first schedule identifier, compare the original schedule data with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, determine the changed fields and redundant fields in the target schedule data according to the difference data, modify the target schedule data according to the changed fields and redundant fields to obtain the schedule changed data, call the schedule modification interface to construct a schedule modification request according to the access token, schedule changed data and the first schedule identifier. In the modification operation, the differential data is updated, which reduces the amount of data transmission, reduces network bandwidth occupation and transmission latency, improves synchronization efficiency, and avoids conflicts or errors that may be caused by redundant data transmission, further improving the accuracy and stability of the schedule modification operation.

[0088] In yet another alternative embodiment, such as Figure 4 As shown, the cross-platform calendar synchronization device may further include: The receiving module 308 is used to receive the response result returned by the second schedule program after the schedule synchronization module 304 performs the schedule synchronization operation based on the target schedule data. The response result includes a response status code and a response body. The judgment module 309 is used to determine whether the schedule synchronization operation is successful based on the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body and stored in the preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and target schedule data. Analysis module 310 is used to analyze the reason for the failure of the schedule synchronization operation based on the response status code when the response status code indicates that the schedule synchronization operation has failed. The generation module 311 is used to generate a failure solution based on the cause of failure and jump to the failure resolution page in the first schedule program to guide the target user to perform the failure resolution operation through the failure solution; The acquisition module 301 is also used to acquire the failure resolution operation result after the target user completes the failure resolution operation, and generate an error investigation record based on the failure resolution operation result, response status code, failure reason and failure solution, and store the error investigation record in the mapping table.

[0089] It is evident that implementation Figure 5 The described cross-platform calendar synchronization device enables traceability of the synchronization process and rapid problem location by recording synchronization results, analyzing failure causes, providing solutions, and generating troubleshooting records. This allows users to intuitively understand the synchronization status, efficiently troubleshoot synchronization failures to resolve issues, improve user experience, and enhance system maintainability.

[0090] Example 4 Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of another cross-platform calendar synchronization device disclosed in an embodiment of the present invention. ​ As shown, the cross-platform calendar synchronization device may include: Memory 401 storing executable program code; Processor 402 coupled to memory 401; The processor 402 calls the executable program code stored in the memory 401 to execute the steps in the cross-platform schedule synchronization implementation method described in Embodiment 1 or Embodiment 2 of the present invention.

[0091] Example 5 This invention discloses a computer storage medium storing computer instructions. When these computer instructions are invoked, they are used to execute some or all of the steps in any of the cross-platform calendar synchronization implementation methods disclosed in Embodiment 1 of this invention.

[0092] Example 6 This invention discloses a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform the steps in the cross-platform schedule synchronization implementation method described in Embodiment 1 or Embodiment 2.

[0093] The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0094] Through the detailed description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-Erasable Programmable Read-Only Memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0095] Finally, it should be noted that the cross-platform calendar synchronization method and apparatus disclosed in the embodiments of the present invention are merely preferred embodiments of the present invention and are only used to illustrate the technical solutions of the present invention, not to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A cross-platform method for implementing schedule synchronization, characterized in that, The method includes: When a target user is detected performing a schedule operation on the first schedule program, the schedule data corresponding to the schedule operation is obtained; Obtain the program information of the second schedule program that needs to be synchronized, and perform data transformation on the schedule data according to the program information to obtain the target schedule data; An interaction channel is established between the first schedule program and the second schedule program based on the program information, and the target schedule data is transmitted to the second schedule program through the interaction channel. A schedule synchronization operation is then performed in the second schedule program based on the target schedule data.

2. The cross-platform calendar synchronization method according to claim 1, characterized in that, The program information includes the data target fields of the second schedule program, and the data target fields include required fields and optional fields; The step of converting the schedule data according to the program information to obtain the target schedule data includes: Determine the data fields corresponding to the schedule data, and establish a mapping relationship between the data fields and the target data fields; Based on the mapping relationship and the field type requirements of the target data field, the data field is converted to obtain the converted data field; Based on the mapping relationship and the field formatting requirements of the target data field, the converted data field is subjected to format standardization processing to obtain the format-standardized data field; The data fields after format standardization are checked for integrity based on the required fields. When the data fields after format standardization pass the integrity check, the data fields after format standardization are encapsulated into target schedule data.

3. The cross-platform calendar synchronization method according to claim 1 or 2, characterized in that, The program information also includes the identity authentication platform information and basic address information corresponding to the second schedule program; Before establishing the interaction channel between the first schedule program and the second schedule program based on the program information, the method further includes: Register the registration application corresponding to the first schedule program on the identity authentication platform corresponding to the second schedule program according to the identity authentication platform information, and receive the identity authentication parameters returned by the identity authentication platform. The identity authentication parameters include the client identifier, client password and tenant identifier corresponding to the first schedule program. The step of establishing an interaction channel between the first schedule program and the second schedule program based on the program information includes: The identity authentication information is encapsulated according to a preset target format to obtain a target request, and the target request is sent to the identity authentication platform to obtain an access token returned by the identity authentication platform. Determine whether the access token meets the preset verification conditions. When the access token meets the verification conditions, establish an interaction channel between the first scheduler and the second scheduler based on the access token and the base address information. The verification conditions include validity period verification conditions and permission verification conditions.

4. The cross-platform calendar synchronization method according to claim 3, characterized in that, The step of transmitting the target schedule data to the second schedule program through the interaction channel includes: Obtain the interface document corresponding to the second schedule program, and determine the target interface corresponding to the schedule operation in the interface document; Based on the access token, the target schedule data, and the target interface, a target request is constructed and transmitted to the second scheduler through the interaction channel; Monitor whether a response is received from the second scheduler within a preset time period. If no response is received within the preset time period, retransmit the target request to the second scheduler.

5. The cross-platform calendar synchronization method according to claim 4, characterized in that, The schedule operations include schedule creation, schedule modification, or schedule deletion, and the target interfaces include schedule creation interfaces, schedule modification interfaces, or schedule deletion interfaces. Constructing a target request based on the access token, the target schedule data, and the target interface includes: When the scheduling operation includes the scheduling creation operation, the scheduling creation interface is invoked to construct a scheduling creation request based on the access token and the target scheduling data; When the schedule operation includes the schedule modification operation, the first schedule identifier of the local schedule corresponding to the schedule modification operation is obtained from the mapping table preset in the first schedule program, and the schedule modification interface is called to construct a schedule modification request based on the access token, the target schedule data and the first schedule identifier. When the schedule operation includes the schedule deletion operation, the second schedule identifier of the local schedule corresponding to the schedule deletion operation is obtained from the preset mapping table in the first schedule program, and the schedule deletion interface is called to construct a schedule deletion request based on the access token and the second schedule identifier. And, the step of performing a schedule synchronization operation in the second scheduler based on the target schedule data includes: When the scheduling operation includes the scheduling creation operation, a target schedule corresponding to the target schedule data is created in the second scheduling program according to the scheduling creation request, and the schedule identifier corresponding to the target schedule returned by the second scheduling program is received; The schedule identifier is associated with the third schedule identifier of the local schedule corresponding to the schedule creation operation and stored in a preset mapping table in the first schedule program; When the scheduling operation includes the scheduling modification operation, the schedule corresponding to the first schedule identifier is modified in the second scheduling program according to the scheduling modification request; When the schedule operation includes the schedule deletion operation, the schedule corresponding to the second schedule identifier is deleted in the second schedule program according to the schedule deletion request, and after receiving the deletion success instruction returned by the second schedule program, the local schedule corresponding to the schedule deletion operation is marked as deleted in the mapping table.

6. The cross-platform calendar synchronization method according to claim 5, characterized in that, When the scheduling operation includes the scheduling modification operation, the method further includes: Call the schedule query interface in the second schedule program to obtain the original schedule data corresponding to the schedule modification operation stored in the second schedule program according to the first schedule identifier; The original schedule data is compared with the target schedule data to obtain the difference data between the original schedule data and the target schedule data, and the changed fields and redundant fields in the target schedule data are determined based on the difference data. The target schedule data is modified based on the changed fields and the redundant fields to obtain schedule change data; The step of invoking the schedule modification interface to construct a schedule modification request based on the access token, the target schedule data, and the first schedule identifier includes: The schedule modification interface is invoked to construct a schedule modification request based on the access token, the schedule change data, and the first schedule identifier.

7. The cross-platform calendar synchronization method according to any one of claims 1, 2, 4-6, characterized in that, The method further includes: After the schedule synchronization operation is performed in the second schedule program based on the target schedule data, a response result returned by the second schedule program is received, the response result including a response status code and a response body; The success of the schedule synchronization operation is determined based on the response status code. When the response status code indicates that the schedule synchronization operation is successful, a schedule synchronization record is generated based on the response body and stored in a preset mapping table in the first schedule program. The response body includes the synchronization time, schedule operation type, schedule identification information corresponding to the schedule operation, and the target schedule data. When the response status code indicates that the schedule synchronization operation has failed, analyze the reason for the failure of the schedule synchronization operation based on the response status code; Based on the cause of failure, a failure solution is generated, and the user is redirected to the failure resolution page in the first schedule program. The failure solution guides the target user to perform the failure resolution operation. After the target user completes the failure resolution operation, the failure resolution operation result is obtained, and an error investigation record is generated based on the failure resolution operation result, the response status code, the failure reason and the failure solution, and the error investigation record is stored in the mapping table.

8. A cross-platform calendar synchronization device, characterized in that, The device includes: The acquisition module is used to acquire the schedule data corresponding to the schedule operation when it is detected that the target user performs a schedule operation on the first schedule program; The acquisition module is also used to acquire program information of the second schedule program that needs to be synchronized. The data conversion module is used to convert the schedule data according to the program information to obtain the target schedule data; The data transmission module is used to establish an interaction channel between the first schedule program and the second schedule program based on the program information, and to transmit the target schedule data to the second schedule program through the interaction channel. The schedule synchronization module is used to perform schedule synchronization operations in the second schedule program based on the target schedule data.

9. A cross-platform schedule synchronization device, characterized in that, The device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the cross-platform schedule synchronization implementation method as described in any one of claims 1-7.

10. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, which, when invoked, are used to execute the cross-platform schedule synchronization method as described in any one of claims 1-7.

Images