Schedule label synchronization method and system, main client, electronic equipment and medium

Abstract

The invention relates to the technical field of communication, and particularly provides a schedule label synchronization method and system, a main client, electronic equipment and a medium, the schedule label synchronization method comprises the following steps: receiving a first main label set by a user for a target schedule, the first main label being one of a plurality of main labels; based on the mapping relation table, a first auxiliary label corresponding to the first main label is inquired and determined, and the first auxiliary label is one of the multiple auxiliary labels; and sending the target schedule for synchronization and the first auxiliary label associated with the target schedule to the mail server, so that the auxiliary client can synchronize the target schedule and the first auxiliary label associated with the target schedule from the mail server. In this way, the problem that schedule labels cannot be synchronized between different clients of a label system can be solved.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a schedule label synchronization method, system, main client, electronic device, and medium. Background Art

[0002] Currently, a mail server is a device responsible for the management of email sending and receiving, and it can be connected to multiple clients simultaneously. Each client can synchronize email information from the mail server, extract schedule information from the email information, and present it to the user.

[0003] However, there may be differences in the label systems used among different clients. Herein, "differences in the label system" can be understood as different label dimensions used for annotating schedules, or rather, different dimensions of schedule labels. For clients with different label systems, due to the incompatibility of the label dimensions used for schedule annotation, if a user annotates a schedule on a certain client, other clients cannot synchronize this schedule annotation, resulting in poor schedule synchronization between clients and affecting the user experience.

[0004] Therefore, how to solve the problem that schedule labels cannot be synchronized between clients with different label systems and improve the schedule synchronization between clients has become an urgent problem to be solved currently. Summary of the Invention

[0005] In view of this, the present invention provides a schedule label synchronization method, system, main client, electronic device, and medium, which can solve the problem that schedule labels cannot be synchronized between clients with different label systems.

[0006] To solve the above technical problems, on the one hand, the present invention provides a schedule label synchronization method, which is applied to a main client. The main client and a secondary client are connected to the same mail server. Among them, the main client uses a first label system, and the first label system includes multiple main labels; the secondary client uses a second label system, and the second label system includes multiple secondary labels; a mapping relationship table is stored in the main client, and the mapping relationship table contains the mapping relationship between the main labels used by the main client and the secondary labels used by the secondary client; the schedule label synchronization method includes:

[0007] Receiving a first main label set by the user for a target schedule, where the first main label is one of the multiple main labels; based on the mapping relationship table, querying and determining a first secondary label corresponding to the first main label, where the first secondary label is one of the multiple secondary labels; sending the target schedule for synchronization and the first secondary label associated with the target schedule to the mail server, so that the secondary client can synchronize the target schedule and the first secondary label associated with the target schedule from the mail server.

[0008] In this embodiment, by establishing a mapping relation table to associate different tag systems used by the primary client and the secondary client and storing the mapping relation table in the primary client, when receiving a first primary tag set by the user for a target schedule on the primary client, the first secondary tag corresponding to the first primary tag applicable to the secondary client can be obtained by querying using the mapping relation table, thereby overcoming the problem that schedule tags cannot be synchronized between clients due to differences between tag systems and improving the schedule synchronization between clients and the user experience.

[0009] According to some embodiments of the present invention, the mapping relation between the primary tag and the secondary tag includes at least one of one-to-one, one-to-many, many-to-one, and many-to-many mapping relations.

[0010] According to some embodiments of the present invention, the mapping relation table is generated based on the mapping relation between the primary tag of the primary client and the secondary tag of the secondary client input by the user through the configuration interface; wherein, all secondary tags set on the secondary client are obtained from the mail server in response to a configuration request input by the user.

[0011] This embodiment generates a mapping relation table through user-defined configuration, provides personalized settings for the user, and improves the user experience.

[0012] According to some embodiments of the present invention, the mapping relation table is stored in the schedule database in the primary client, and the schedule database also stores a schedule information table, which contains the schedule detailed information corresponding to each target schedule and the first primary tag associated with the target schedule.

[0013] In a second aspect, an embodiment of the present invention provides a schedule tag synchronization method, which is applied to a secondary client. The secondary client and the primary client are connected to the same mail server. Among them, the primary client uses a first tag system, and the first tag system includes multiple primary tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the primary client, and the mapping relation table contains the mapping relation between the primary tags used by the primary client and the secondary tags used by the secondary client; the schedule tag synchronization method includes:

[0014] Receiving a first secondary tag set by the user for a target schedule, where the first secondary tag is one of the multiple secondary tags; sending the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server, so that the primary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server, and based on the mapping relation table, query and determine the first primary tag corresponding to the first secondary tag, where the first primary tag is one of the multiple primary tags.

[0015] In a third aspect, an embodiment of the present invention provides a main client, which is connected to a secondary client to the same mail server. The main client uses a first tag system, and the first tag system includes a plurality of main tags; the secondary client uses a second tag system, and the second tag system includes a plurality of secondary tags; the main client includes:

[0016] A storage module for storing a mapping relation table, where the mapping relation table contains the mapping relation between the main tags used by the main client and the secondary tags used by the secondary client.

[0017] A calendar module, connected to the storage module, for receiving a first main tag set by a user for a target schedule, where the first main tag is one of the plurality of main tags; obtaining the mapping relation table from the storage module; based on the mapping relation table, querying and determining a first secondary tag corresponding to the first main tag, where the first secondary tag is one of the plurality of secondary tags; sending the first secondary tag associated with the target schedule to the storage module; where the storage module is further configured to, in response to receiving the first secondary tag associated with the target schedule, send the target schedule and the first secondary tag associated with the target schedule to the mail module.

[0018] A mail module, connected to the storage module and the mail server, for receiving the target schedule and the first secondary tag associated with the target schedule sent by the storage module; sending the target schedule and the first secondary tag associated with the target schedule for synchronization to the mail server, so that the secondary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

[0019] According to some embodiments of the present invention, the mapping relation table is generated by the storage module based on the mapping relation between the main tags of the main client and the secondary tags of the secondary client input by the user through a configuration interface; where all the secondary tags set on the secondary client are obtained by the calendar module from the mail server in response to a configuration request input by the user.

[0020] According to some embodiments of the present invention, the mapping relation table is stored in a schedule database in the storage module, and the schedule database also stores a schedule information table, where the schedule information table contains the schedule detailed information corresponding to each target schedule and the first main tag associated with the target schedule.

[0021] In a fourth aspect, an embodiment of the present invention provides a schedule tag synchronization system, including: a main client, a secondary client, and a mail server connected to the main client and the secondary client; where the main client uses a first tag system, and the first tag system includes a plurality of main tags; the secondary client uses a second tag system, and the second tag system includes a plurality of secondary tags; a mapping relation table is stored in the main client, and the mapping relation table contains the mapping relation between the main tags used by the main client and the secondary tags used by the secondary client.

[0022] The main client is used to receive a first main tag set by the user for a target schedule, where the first main tag is one of multiple main tags; based on the mapping relation table, query and determine a first secondary tag corresponding to the first main tag, where the first secondary tag is one of multiple secondary tags; and send the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server. The secondary client is used to synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

[0023] According to some embodiments of the present invention, the mail server is used to, in response to receiving the target schedule and the first secondary tag associated with the target schedule, send a schedule update reminder to the secondary client, so that the secondary client synchronizes the target schedule and the first secondary tag associated with the target schedule from the mail server in response to the schedule update reminder.

[0024] In this embodiment, by using the mail server to send a schedule update reminder to the secondary client, real-time management and automatic update of the schedule can be achieved, thereby improving the timeliness of schedule tag synchronization.

[0025] In a fifth aspect, an embodiment of the present invention provides a schedule tag synchronization system, including: a main client, a secondary client, and a mail server connected to the main client and the secondary client; wherein, the main client uses a first tag system, and the first tag system includes multiple main tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the main client, and the mapping relation table includes the mapping relation between the main tags used by the main client and the secondary tags used by the secondary client.

[0026] The secondary client is used to receive a first secondary tag set by the user for a target schedule, where the first secondary tag is one of multiple secondary tags; and send the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server.

[0027] The main client is used to synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server, and based on the mapping relation table, query and determine a first main tag corresponding to the first secondary tag, where the first main tag is one of multiple main tags.

[0028] This embodiment can directly synchronize the first secondary tag to the main client through the mail server when receiving the first secondary tag set by the user for the target schedule on the secondary client. Then, through the mapping relation table stored in the main client, the different tag systems on the main client and the secondary client are associated, realizing the conversion and synchronization of schedule tags under different tag systems, overcoming the problem that schedule tags cannot be synchronized between different clients caused by differences in tag systems, and improving the schedule synchronization between different clients and the user experience.

[0029] According to some embodiments of the present invention, a mail server is configured to send a schedule update reminder to a primary client in response to receiving a target schedule and a first secondary tag associated with the target schedule, so that the primary client synchronizes the target schedule and the first secondary tag associated with the target schedule from the mail server in response to the schedule update reminder.

[0030] This embodiment uses the mail server to send a schedule update reminder to the primary client, which can realize real-time management and automatic update of the schedule, thereby improving the timeliness of schedule tag synchronization.

[0031] In a sixth aspect, an embodiment of the present invention provides an electronic device, including: a processor; and a memory in which computer program instructions are stored.

[0032] Wherein, when the computer program instructions are run by the processor, the processor is caused to execute the schedule tag synchronization method described in the above technical solution.

[0033] In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when run by a processor, causes the processor to execute the schedule tag synchronization method described in the above technical solution. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a schematic diagram of a schedule tag synchronization system according to an embodiment of the present invention;

[0035] Figure 2 It is a schematic diagram of an example of a schedule display interface of a computer;

[0036] Figure 3 It is a flow interaction diagram of a schedule tag synchronization method according to an embodiment of the present invention;

[0037] Figure 4 It is a flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

[0038] Figure 5 It is a schematic diagram of an example of a schedule display interface of a schedule app installed on a mobile phone and a schedule app installed on a computer;

[0039] Figure 6 It is a schematic diagram of an example of a schedule display interface of a schedule app installed on a mobile phone;

[0040] Figure 7 It is a schematic diagram of a primary client according to an embodiment of the present invention;

[0041] Figure 8 It is a flow interaction diagram of a schedule tag synchronization method according to an embodiment of the present invention;

[0042] Figure 9 Flow interaction diagram for configuring a mapping relationship table in the schedule label synchronization method according to an embodiment of the present invention;

[0043] Figure 10 Flow interaction diagram for the schedule label synchronization method according to an embodiment of the present invention;

[0044] Figure 11 Flowchart of the schedule label synchronization method according to an embodiment of the present invention;

[0045] Figure 12 Flow interaction diagram for the schedule label synchronization method according to an embodiment of the present invention;

[0046] Figure 13 Schematic diagram of an electronic device according to an embodiment of the present invention. Detailed implementation manners

[0047] The following will further describe in detail the specific implementation manners of the present invention in conjunction with the accompanying drawings and embodiments. The following embodiments are used to illustrate the present invention, but are not used to limit the scope of the present invention.

[0048] A mail server is a device responsible for the management of email sending and receiving, and it can be connected to multiple clients at the same time. Each client can synchronize email information from the mail server, extract schedule information from the email information, and present it to the user.

[0049] However, there may be differences in the label systems used between different clients, or rather, the label dimensions used for annotating schedules are different. Hereinafter, the "labels used for annotating schedules" will be simply referred to as schedule labels. Currently, for clients with different label systems, if a user makes a schedule annotation on a certain client, other clients cannot synchronize this schedule annotation. For example, the first client uses the first schedule label to annotate the schedule, and the second client uses the second schedule label to annotate the schedule; due to the different label dimensions of the first schedule label and the second schedule label, the first client cannot be compatible with the second schedule label, and the second client cannot be compatible with the first schedule label, resulting in the inability to synchronize the schedule labels between the first client and the second client, thereby affecting the user experience.

[0050] Therefore, how to solve the problem that schedule labels cannot be synchronized between clients with different label systems and improve the schedule synchronization between clients has become an urgent problem to be solved currently.

[0051] To solve the problem that schedule tags cannot be synchronized between clients with different tag systems, an embodiment of the present application proposes a schedule tag synchronization system, which includes: a main client, a secondary client, and a mail server connected to the main client and the secondary client. The main client uses a first tag system, and the first tag system includes multiple main tags. The secondary client uses a second tag system, and the second tag system includes multiple secondary tags. A mapping table is stored in the main client, and the mapping table contains the mapping relationship between the main tags used by the main client and the secondary tags used by the secondary client.

[0052] The main client receives the first main tag set by the user for the target schedule. Then, based on the mapping table, it queries and determines the first secondary tag corresponding to the first main tag. Finally, it sends the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server, so that the secondary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

[0053] The schedule tag synchronization system proposed in the embodiment of the present application can associate different tag systems used by the main client and the secondary client by establishing a mapping table and store it in the main client. When receiving the first main tag set by the user for the target schedule on the main client, it can use the mapping table to query and obtain the first secondary tag corresponding to the first main tag applicable to the secondary client, thereby overcoming the problem that schedule tags cannot be synchronized between clients caused by differences between tag systems, improving the schedule synchronization between clients and the user experience.

[0054] Before elaborating on the embodiments of the present application in detail, a brief introduction is given to the "schedule annotation", "schedule tag dimension", "mail communication protocol", and "client" involved in the embodiments of the present application.

[0055] First, by setting schedule tags for the target schedule, the schedule annotation operation can be completed. Among them, in specific application scenarios, "schedule annotation" can be used for schedule classification and / or schedule reminder, or in other words, "schedule tags" can be used for schedule classification and / or key identification. Through schedule annotation, personalized management of schedules can be realized, and the convenience and intelligence of schedule management can be improved.

[0056] The "schedule label dimension", or the "label dimension used for schedule annotation", can be understood as the field type of schedule labels. The field type of schedule labels is related to the mail communication protocol used by the client in actual applications or the operating system of the client. Commonly used mail communication protocols may include, but are not limited to, the Exchange protocol, the EAS (Exchange ActiveSync) protocol, the POP3 protocol, and the IMAP protocol. The operating systems may include, but are not limited to, Windows, Android, Harmony, and EulerOS. The device types of the client may include, but are not limited to, mobile phones, tablets, and computers, etc. The embodiments of the present application do not limit the mail communication protocol adopted by the client and the device type of the client.

[0057] The following takes the Exchange protocol, the EAS (Exchange Active Sync) protocol, and the Android operating system as examples to introduce the field type of schedule labels. Corresponding to the Exchange protocol or the EAS (Exchange Active Sync) protocol, the field type of schedule labels can be the Category field; that is to say, if the client (such as a computer) uses the Exchange protocol or the EAS (Exchange Active Sync) protocol for communication, it can generally perform schedule annotation by defining the Category field. Corresponding to the client on a mobile phone device using the Android operating system, the field type of the schedule labels it uses can be the Piroirty field; that is to say, the client on a mobile phone device using the Android operating system generally uses the Piroirty field for schedule annotation. Since the field types of the above Category field and Piroirty field are different, the two belong to different label dimensions and cannot be compatible with each other.

[0058] The following begins to introduce the embodiments proposed in the present application in detail one by one. First, the schedule label synchronization system proposed in the embodiments of the present application will be introduced.

[0059] As Figure 1 shown, the schedule label synchronization system 100 of the embodiment of the present invention includes: a primary client 101, a secondary client 102, and a mail server 103 connected to the primary client and the secondary client.

[0060] Among them, the primary client 101 uses a first label system, and the first label system includes multiple primary labels. The secondary client 102 uses a second label system, and the second label system includes multiple secondary labels. A mapping relation table is stored in the primary client 101, and the mapping relation table includes the mapping relation between the primary labels used by the primary client 101 and the secondary labels used by the secondary client 102.

[0061] First, the "main client 101", "sub-client 102", "first label system", "second label system", "main label", and "sub-label" involved in the embodiments of the present application will be described.

[0062] First, a "client" refers to an application (app) or a web page installed on a hardware device (such as a computer, a mobile phone, or a tablet). Among them, the application can be divided into a native app based on an operating system and an app downloaded from a third party. Corresponding to the client installed on a computer, it can be a native app running on a desktop operating system, an app downloaded from a third party, or a web page running in a desktop browser; corresponding to the client installed on a mobile phone, it can be a native app running on a mobile device operating system, an app downloaded from a third party, or a web page running in a mobile device browser.

[0063] In the embodiments of the present application, the "main client 101" and the "sub-client 102" are only used to represent clients with different label systems connected to the same mail server 103. The device types of the two can be the same or different, and the device type is not limited here. The main client 101 and the sub-client 102 can belong to different hardware devices or the same hardware device. That is to say, the main client 101 and the sub-client 102 can be applications or web pages on different hardware devices, or different applications or web pages on the same hardware device.

[0064] Taking the client installed on a mobile phone as an example, the native email app on the mobile phone can log in to a third-party email. Among them, the native email app is one client, and the dedicated app or dedicated web page of the third-party email is another client.

[0065] The dimensions of the schedule labels (i.e., main labels) used by the main client 101 under the "first label system" and the schedule labels (i.e., sub-labels) used by the sub-client 102 under the "second label system" are different, or rather, the field types are different.

[0066] The number and label content of the main labels used by the main client 101 can be set customarily, and the number and label content of the sub-labels used by the sub-client 102 can also be set customarily. The label content of the main labels and the label content of the sub-labels can be the same or different, where the "label content" can be understood as schedule annotation information.

[0067] In one example, three main tags can be set on the main client 101, and the tag contents of the three main tags are "Work Category", "Study Category", and "Social Category" respectively. Thus, the above three main tags can be used to classify schedules into three types: "Work", "Study", and "Social". However, six secondary tags are set on the secondary client 102, and the tag contents of the six secondary tags can be "Red Category", "Yellow Category", "Blue Category", "Green Category", "Orange Category", and "Purple Category" respectively. Through the above six secondary tags, the schedule can be classified using color categories. In this example, the tag contents of the main tags and the secondary tags are different, or rather, the target classification information is different.

[0068] In other examples, secondary tags with the same tag contents as the above main tags can also be set on the secondary client 102, or main tags with the same tag contents as the above secondary tags can be set on the main client 101. Specifically, it can be customized according to actual application requirements. Here, the number and tag contents of the main tags and secondary tags are not limited.

[0069] In one embodiment, the main client 101 can be a schedule app installed on a mobile phone, and the main tag can be a Piroirty field. The schedule app installed on the mobile phone can use the Piroirty field to classify the schedule priority, or rather, the importance level. Specifically, the schedule is divided into: "Important Category", "Ordinary Category", and "Ignored Category" using the Piroirty field.

[0070] In one embodiment, the secondary client 102 can be a schedule app installed on a computer, and the secondary tag can be a Category field. The schedule app installed on the computer can use the Category field to divide the schedule into 8 schedule tags related to colors, such as "Blue Category", "Yellow Category", "Red Category", "Orange Category", or "Green Category". In one embodiment, as Figure 2 shown, in the schedule display interface 200 of the computer, the user can right-click on the schedule box 21 where the target schedule is located to open the settings menu 22. The settings menu 22 is generally used to display options related to schedule management. In Figure 2 an example of the shown settings menu 22, the settings menu 22 can be used to display "Quick Print", "Receive", "Tentative", "Reject", "Set New Time", "Reply", "Reply All", "Forward", "Display", "Classify", and "Delete". Then left-click on "Classify" in the settings menu 22 to open the classification menu 23. The classification menu 23 is generally used to display options related to schedule category settings. In Figure 2In an example of the classification menu 23 shown, the classification menu 23 can be used to display "Blue Category", "Yellow Category", "Red Category", "Orange Category", "Green Category", "All Categories", and "Set New Category". Then, check the "Blue Category", "Yellow Category", "Red Category", "Orange Category", or "Green Category" to be set for the target schedule in the classification menu 23. When a new custom category needs to be created, left-click on "Set New Category" in the classification menu 23 to enter a new category, such as the creation process of a label for a new color.

[0071] As Figure 3 shown, the schedule label synchronization system 100 proposed in the above embodiment will be further introduced below.

[0072] The main client 101 is used to receive the first main label set by the user for the target schedule, and the first main label is one of multiple main labels. Based on the mapping relationship table, query and determine the first sub-label corresponding to the first main label, and the first sub-label is one of multiple sub-labels. Send the target schedule for synchronization and the first sub-label associated with the target schedule to the mail server 103. The secondary client 102 is used to synchronize the target schedule and the first sub-label associated with the target schedule from the mail server 103. When the main client 101 receives the first main label set by the user for the target schedule, it uses the mapping relationship table to query the first sub-label corresponding to the first main label, thereby realizing the association between the first label system and the second label system and providing a basis for schedule label synchronization.

[0073] In one embodiment, the mail server 103 is used to send a schedule update reminder to the secondary client 102 in response to receiving the target schedule and the first sub-label associated with the target schedule, so that the secondary client 102 synchronizes the target schedule and the first sub-label associated with the target schedule from the mail server 103 in response to the schedule update reminder, thereby realizing real-time management and automatic update of the schedule and improving the timeliness of schedule label synchronization.

[0074] The above embodiment associates the different label systems used by the main client 101 and the secondary client 102 by establishing a mapping relationship table and stores it in the main client 101. When receiving the first main label set by the user for the target schedule on the main client 101, it can use the mapping relationship table to query the first sub-label corresponding to the first main label applicable to the secondary client 102, thereby overcoming the problem that schedule labels cannot be synchronized between clients caused by differences between label systems and improving the schedule synchronization between clients and the user experience.

[0075] In one embodiment, the mapping relationship between the main tag and the secondary tag included in the mapping relationship table may include at least one of one-to-one, one-to-many, many-to-one, and many-to-many mapping relationships. Among them, "one-to-one" means that there is a mapping relationship between one main tag and one secondary tag; "one-to-many" means that there is a mapping relationship between one main tag and multiple secondary tags; "many-to-one" means that there is a mapping relationship between multiple main tags and one secondary tag; "many-to-many" means that there is a mapping relationship between multiple main tags and multiple secondary tags.

[0076] As shown in Table 1 below, Table 1 is an example of the mapping relationship table.

[0077] Table 1 Mapping Relationship Table

[0078] Primary Client - Priority Field Secondary Client - Category Field Important - 2 String (Red Classification) Ignore - 0 String (Yellow Classification) Normal - 1 String (Blue Classification)

[0079] In the mapping relationship table shown in Table 1 above, there is a one-to-one mapping relationship between the main tag and the secondary tag. The main client 101 uses the Piority field as the schedule tag, and the "Important-2" field, "Ignore-0" field, and "Normal-1" field are used to mark the priority of the schedule. Among them, the schedule marked with the "Important-2" field has the highest priority (this schedule is called an important schedule), the schedule marked with the "Normal-1" field has a lower priority than the important schedule (this schedule is called a normal schedule), and the schedule marked with the "Ignore-0" field has the lowest priority (this schedule is called an ignored schedule). The secondary client 102 uses the Category field as the schedule tag, and the "String (red classification)" field, "String (yellow classification)" field, and "String (blue classification)" field are used to mark the category of the schedule. As can be seen from Table 1 above, the important schedule corresponds to the red classification, the ignored schedule corresponds to the yellow classification, and the normal schedule corresponds to the blue classification.

[0080] As Figure 4 shown, the following combines the mapping relationship table shown in Table 1 above to introduce in detail an example of the schedule tag synchronization method proposed in the embodiment of the present application. This schedule tag synchronization method is applied to the main client 101 in the schedule tag synchronization system 100 in the above embodiment, and the schedule tag synchronization system 100 will not be described in detail here. The schedule tag synchronization method includes:

[0081] Step 110: Receive the main tag "Important-2" set by the user for the target schedule.

[0082] Step 120: Based on the mapping relationship table, query and determine the secondary tag "String (red classification)" corresponding to the main tag "Important-2".

[0083] The main client 101 may receive that the user sets the main label "Important-2" for the target schedule, and then query the secondary label corresponding to the main label "Important-2" in the mapping relation table based on the mapping relation table shown in Table 1 above, so as to determine that the secondary label is "String (Red Classification)".

[0084] Step 130: Send the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule to the mail server, so that the secondary client can synchronize the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server.

[0085] After determining that the secondary label is "String (Red Classification)", send the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule to the mail server 103, so that the secondary client 102 can synchronize the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server 103.

[0086] In an embodiment, the mail server 103 may, in response to receiving the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule, send a schedule update reminder to the secondary client 102, so that the secondary client 102 synchronizes the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server 103.

[0087] Generally speaking, the secondary client 102 can use the same mail communication protocol as the mail server 103 to achieve compatibility between the secondary client 102 and the mail server 103. The secondary tags set on the secondary client 102 can be directly synchronized to the mail server 103 and other clients using the same mail communication protocol. For example, if the secondary client 102 uses the Category field as the secondary tag, and the secondary tag includes fields such as "String (red classification)", "String (yellow classification)", and "String (blue classification)", then the same secondary tags are also synchronously set in other clients using the same mail communication protocol. In addition, during the process of synchronizing the schedule tags, when the mail server 103 receives the target schedule for synchronization and the first secondary tag associated with the target schedule, it can also send a schedule update reminder to other clients using the same mail communication protocol except the secondary client 102, so that other clients can all synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server 103. For example, when the mail server 103 receives the target schedule for synchronization and the first secondary tag "String (blue classification)" associated with the target schedule, it sends a schedule update reminder to other clients using the same mail communication protocol except the secondary client 102, so that other clients can all synchronize the target schedule and the first secondary tag "String (blue classification)" associated with the target schedule from the mail server 103.

[0088] In one embodiment, in the above step 130, only the schedule name of the target schedule for synchronization and the secondary tag "String (red classification)" associated with the target schedule may be sent to the mail server 103, without sending the schedule details of the target schedule. The secondary client 102 can find the corresponding target schedule based on the schedule name and associate the secondary tag "String (red classification)" with it. In this way, the amount of data transmission can be reduced, and the synchronization efficiency can be further improved.

[0089] The primary client 101 of the embodiment of the present application stores a mapping relationship table that associates different tag systems on the primary client 101 and the secondary client 102. Then, when receiving the primary tag "Important-2" set by the user for the target schedule, by referring to the mapping relationship table, the secondary tag "String (red classification)" corresponding to the primary tag "Important-2" applicable to the secondary client 102 is obtained, thereby overcoming the problem that the schedule tags between different clients cannot be synchronized due to differences in tag systems, realizing the synchronization of schedule tags between the secondary client 102 and the primary client 101, and improving the schedule synchronization between different clients and the user experience.

[0090] In one embodiment, the mapping relation table can be stored in the schedule database in the main client 101. The schedule database also stores a schedule information table, which may include the detailed schedule information corresponding to each target schedule and the first main label associated with the target schedule. It can be understood that when the main client 101 receives the first main label set by the user for the target schedule, the main client 101 can store the first main label in the schedule information table and associate it with the corresponding target schedule in the schedule information table to update the schedule information table in real time.

[0091] In one embodiment, the display manner of the main label on the schedule display interface of the main client 101 is different from that of the secondary label on the schedule display interface of the secondary client 102. The "display manner" may include but is not limited to text highlighting color, font style change, text folding, and symbol identification. The "font style" includes but is not limited to font, color, thickness, and italic. Specifically, it can be set according to actual requirements and is not limited herein.

[0092] In one embodiment, each main label can adopt the same type of display manner on the schedule display interface of the main client 101, where the specific manifestations of different main labels on the schedule display interface of the main client 101 are different; each secondary label can adopt the same type of display manner on the schedule display interface of the secondary client 102, where the specific manifestations of different secondary labels on the schedule display interface of the secondary client 102 are different. The same type of display manner can facilitate the unity and intuitiveness of the display of the main label and the secondary label on their respective schedule display interfaces. For example, different main labels or secondary labels can be displayed using different symbol identifications, or text can be highlighted with different colors, or different degrees of text folding can be adopted, or different font styles can be used, which is not limited herein.

[0093] Taking the mapping relation table shown in Table 1 above, the schedule app of the main client 101 installed on a mobile phone, and the schedule app of the secondary client 102 installed on a computer as examples, an example of the display interface (hereinafter briefly referred to as the "schedule display interface") of the schedule apps of the main client 101 and the secondary client 102 will be introduced. As Figure 5As shown, on December 14, 2023, there are 6 schedules set, and the times of the 6 schedules are 10:30, 15:00, 16:00, 19:00, 19:10, and 19:30 respectively. Among them, the schedules with times of 10:30, 15:00, and 16:00 are marked as ordinary schedules on the schedule app of the mobile phone (marked as blue classification on the schedule app of the computer); the schedules with times of 19:00 and 19:30 are marked as ignored schedules on the schedule app of the mobile phone (marked as yellow classification on the schedule app of the computer); the schedule with a time of 19:10 is marked as an important schedule on the schedule app of the mobile phone (marked as red classification on the schedule app of the computer).

[0094] In the schedule display interface 500b of the schedule app installed on the computer in this example, each schedule box shows all the schedule data of each schedule. Among them, the schedule data can include the schedule name and the schedule details. The schedule details can include time, location, and other schedule details. In the schedule display interface 500b, different colors of text highlighting are used to distinguish the blue classification, yellow classification, and red category. It can be understood that in the Figure 5 schedule display interface 500b in, only different shades of gray are used to indicate blue, yellow, and red, which is not the actual display effect during the application process.

[0095] In the schedule display interface 500a of the schedule app installed on the mobile phone in this example, the fonts of the ignored schedules with times of 19:00 and 19:30 are thinner, and the schedule data is partially folded, only showing the schedule name and hiding the schedule details. Compared with the fonts of the ignored schedules with times of 19:00 and 19:30, the fonts of the ordinary schedules with times of 10:30, 15:00, and 16:00 and the important schedule with a time of 19:10 are thicker and more prominent. The schedule data of the ordinary schedules with times of 10:30, 15:00, and 16:00 and the important schedule with a time of 19:10 is not folded, showing the schedule name and at least part of the schedule details. The important schedule with a time of 19:10 is marked with a flag to highlight the importance of the important schedule. By highlighting the important schedule and folding the ignored schedule, the importance of the schedule can be made more intuitive and the user experience can be improved.

[0096] Generally, when the schedule data is partially collapsed, only the schedule name can be displayed; when there is no need to collapse the schedule data, the schedule name and the detailed schedule information can be displayed completely. However, in actual application scenarios, the schedule data displayed in the schedule box is also limited by the maximum space of the schedule box, the character lengths of the schedule name and the detailed schedule information. For example, when it is necessary to partially collapse the schedule data, if the schedule name exceeds the maximum number of characters that can be displayed within the maximum space of the schedule box, only a part of the schedule name can be displayed. Similarly, when there is no need to collapse the schedule data, if the sum of the characters of the schedule name and the detailed schedule information exceeds the maximum number of characters that can be displayed within the maximum space of the schedule box, as much schedule data as possible can be displayed. For example, according to the actual situation, the schedule name and part of the detailed schedule information can be displayed, or only the schedule name can be displayed, or a part of the schedule name can be displayed.

[0097] In the above embodiments, different display methods are used to display the target schedule according to the content of the main label in the schedule display interface of the main client, and different display methods are used to display the target schedule according to the content of the secondary label in the schedule display interface of the secondary client. By using different display methods to distinguish different schedule labels, the underlying label content can be intuitively presented, making the schedule classification clearer, and thus improving the user experience.

[0098] In one embodiment, the mapping relationship table is generated based on the mapping relationship between the main label of the main client 101 and the secondary label of the secondary client 102 input by the user through the configuration interface. Among them, all the secondary labels set on the secondary client 102 are obtained from the mail server 103 in response to the configuration request input by the user. Generating the mapping relationship table through user-defined configuration provides personalized settings for the user and improves the user experience.

[0099] The configuration process of the mapping relationship table may specifically include: in response to the configuration request input by the user, sending a configuration application to the mail server 103 so that the mail server 103 responds to the configuration application and feedbacks all the secondary labels set on the secondary client 102. Receiving all the secondary labels set on the secondary client 102, and generating and displaying a configuration interface based on all the main labels and all the secondary labels set on the main client 101. Receiving the mapping relationship between the main label of the main client 101 and the secondary label of the secondary client 102 input by the user through the configuration interface, and generating the mapping relationship table.

[0100] Such as Figure 6As shown, take the main client 101 as the schedule app installed on the mobile phone, and use the Piroirty field to divide the schedule into: "important category" and "ignored category"; the secondary client 102 is the schedule app installed on the computer, and use the Category field to divide the schedule into: "blue category", "yellow category", "red category", "orange category" and "green category" as an example to introduce the configuration process of the mapping relationship table.

[0101] In the schedule display interface 600a of the schedule app installed on the mobile phone, the user can left-click on the settings button 651 in the upper right corner to open the settings menu 62. The settings menu 62 is used to display options related to schedule management. In Figure 6 In an example shown, the settings menu 62 includes "Jump to Specified Date", "Account Management", "Print" and "Settings". Then left-click on "Account Management" in the settings menu 62 to jump to the account management page 600b. In the account management page 600b, right-click on "Schedule" to open the schedule menu 63. The schedule menu 63 is used to display options related to schedule settings. In Figure 6 In an example shown, the schedule menu 63 includes "Synchronize Immediately", "Hide All" and "Priority Settings". Left-click on "Priority Settings" in the schedule menu 63 to enter the priority settings page 600c. In the priority settings page 600c, the user can configure the mapping relationship between the "important category" and "ignored category" and Figure 6 each "Exchange category" according to the needs, where the "Exchange category" refers to the "blue category", "yellow category", "red category", "orange category" and "green category". For example, "Important" and "Red Category" can be selected at the same time to establish the mapping relationship between the "important category" and the "red category", and the schedule marked as the "red category" corresponds to an important schedule. Select "Ignore", "Blue Category" and "Yellow Category" at the same time to establish the mapping relationship between the "ignored category" and the "blue category" and "yellow category", and the schedule marked as the "blue category" or "yellow category" corresponds to an ignored schedule.

[0102] The structure of the above-mentioned main client 101 will be introduced in detail below.

[0103] As Figure 7As shown in the figure, the main client 101 of the embodiment of the present invention is connected to the secondary client 102 to the same mail server 103. Among them, the main client 101 uses a first tag system, and the first tag system includes a plurality of main tags; the secondary client 102 uses a second tag system, and the second tag system includes a plurality of secondary tags. The main client 101 includes: a calendar module 1011, a storage module 1012, and a mail module 1013. Among them, the storage module 1012 is connected to the calendar module 1011, and the mail module 1013 is connected to the storage module 1012 and the mail server 103.

[0104] Among them, the storage module 1012 is used to store a mapping relation table, and the mapping relation table contains the mapping relation between the main tags used by the main client 101 and the secondary tags used by the secondary client 102. The calendar module 1011 is used to receive the first main tag set by the user for the target schedule, and the first main tag is one of the plurality of main tags. In one embodiment, the mapping relation table can be stored in the schedule database in the storage module 1012, and the schedule database also stores a schedule information table, and the schedule information table contains the schedule detailed information corresponding to each target schedule and the first main tag associated with the target schedule.

[0105] In one embodiment, the storage module 1012 can be implemented by a memory, and the calendar module 1011 and the mail module 1013 can be implemented by system software integrated in a processor. It should be noted that when the main client 101 implements its functions, only the above-mentioned division of each functional module is used as an example for illustration, and the above functions can also be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device provided in the above embodiment and the corresponding method embodiment belong to the same concept, and the specific implementation process can be seen in the corresponding method embodiment, which will not be elaborated here.

[0106] As Figure 8 shown, taking the mapping relation table shown in Table 1 above as an example, a detailed introduction will be given to an example of the schedule tag synchronization method implemented by the cooperation of each functional module in the main client 101.

[0107] In response to receiving the main tag "Important-2" set by the user for the target schedule, the calendar module 1011 obtains the mapping relation table from the storage module 1012. Then, based on the mapping relation table, it queries and determines the secondary tag "String (red classification)" corresponding to the main tag "Important-2". Then it sends the secondary tag "String (red classification)" associated with the target schedule to the storage module 1012.

[0108] The storage module 1012 sends the target schedule and the secondary label "String (red classification)" associated with the target schedule to the mail module 1013 in response to receiving the secondary label "String (red classification)" associated with the target schedule.

[0109] The mail module 1013 receives the target schedule and the secondary label "String (red classification)" associated with the target schedule sent by the storage module 1012, and then sends the target schedule and the secondary label "String (red classification)" associated with the target schedule for synchronization to the mail server 103, so that the secondary client 102 can synchronize the target schedule and the secondary label "String (red classification)" associated with the target schedule from the mail server 103. Among them, in response to receiving the target schedule and the secondary label "String (red classification)" associated with the target schedule, the mail server 103 sends a schedule update reminder to the secondary client 102, so that the secondary client 102 synchronizes the target schedule and the secondary label "String (red classification)" associated with the target schedule from the mail server 103 in response to the schedule update reminder.

[0110] In one embodiment, the mapping relation table is generated by the storage module 1012 based on the mapping relation between the primary label of the primary client 101 and the secondary label of the secondary client 102 input by the user through the configuration interface. Among them, all the secondary labels set on the secondary client 102 are obtained by the calendar module 1011 from the mail server 103 in response to the configuration request input by the user.

[0111] As Figure 9 shown, the process of configuring the mapping relation table by the above primary client 101 will be introduced in detail below.

[0112] When the user logs in to the account on the mail server 103 for the first time on the main client 101, or when the main client 101 accesses the mail server 103 for the first time, a configuration request can be sent to the calendar module 1011 to enter the configuration process of the mapping relationship table. The calendar module 1011 is used to receive the configuration request input by the user, and in response to the configuration request, send a configuration application instruction to the mail module 1013. The mail module 1013, in response to the configuration application instruction, sends a configuration application to the mail server 103. The mail server 103, in response to the configuration application, feeds back all the secondary labels set on the secondary client 102 to the mail module 1013. The mail module 1013 sends all the secondary labels set on the received secondary client 102 to the storage module 1012. The storage module 1012 writes all the secondary labels set on the received secondary client 102 into the schedule database. The calendar module 1011 obtains all the secondary labels set on the secondary client 102 from the storage module 1012, and generates and displays a configuration interface based on all the primary labels and all the secondary labels set on the main client 101. The user inputs the mapping relationship between the primary labels of the main client 101 and the secondary labels of the secondary client 102 through the configuration interface. The calendar module 1011 generates a mapping relationship table based on the mapping relationship between the primary labels of the main client 101 and the secondary labels of the secondary client 102 input by the user through the configuration interface, and sends the mapping relationship table to the storage module 1012. The storage module 1012 writes the mapping relationship table into the schedule database.

[0113] The schedule label synchronization system 100 of another embodiment of the present invention will be introduced below. The schedule label synchronization system 100 includes: a main client 101, a secondary client 102, and a mail server 103 connected to the main client 101 and the secondary client 102. Among them, the main client 101 uses a first label system, and the first label system includes multiple primary labels. The secondary client 102 uses a second label system, and the second label system includes multiple secondary labels. A mapping relationship table is stored in the main client 101, and the mapping relationship table contains the mapping relationship between the primary labels used by the main client 101 and the secondary labels used by the secondary client 102. It can be understood that the structure of the schedule label synchronization system 100 is the same as that of the schedule label synchronization system 100 in the above embodiment (such as Figure 1 shown), and will not be elaborated here.

[0114] As Figure 10 shown, in the schedule label synchronization system 100 of this embodiment, the secondary client 102 is used to receive the first secondary label set by the user for the target schedule, where the first secondary label is one of the multiple secondary labels, and then sends the target schedule for synchronization and the first secondary label associated with the target schedule to the mail server 103.

[0115] The main client 101 is used to synchronize the target schedule and the first secondary label associated with the target schedule from the mail server 103, and query and determine the first primary label corresponding to the first secondary label based on the mapping relationship table, where the first primary label is one of multiple primary labels, so as to complete the conversion and synchronization of schedule labels under different label systems.

[0116] In one embodiment, the mail server 103 is used to send a schedule update reminder to the main client 101 in response to receiving the target schedule and the first secondary label associated with the target schedule, so that the main client 101 synchronizes the target schedule and the first secondary label associated with the target schedule from the mail server 103 in response to the schedule update reminder.

[0117] The above embodiment can directly synchronize the first secondary label to the main client 101 through the mail server 103 when receiving the first secondary label set by the user for the target schedule on the secondary client 102. Then, through the mapping relationship table stored in the main client 101, the different label systems on the main client 101 and the secondary client 102 are associated to realize the conversion and synchronization of schedule labels under different label systems, overcome the problem that schedule labels cannot be synchronized between clients caused by differences between label systems, and improve the schedule synchronization between clients and the user experience.

[0118] As Figure 11 shown, a detailed introduction to an example of the schedule label synchronization method proposed in another embodiment of the present application is given below in combination with the mapping relationship table shown in Table 1 above. The schedule label synchronization method is applied to the secondary client 102 in the schedule label synchronization system 100 in the above embodiment, and the schedule label synchronization system 100 will not be described in detail here. The schedule label synchronization method includes:

[0119] Step 210: Receive the secondary label "String (Red Classification)" set by the user for the target schedule.

[0120] Step 220: Send the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule to the mail server, so that the main client can synchronize the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server, and query and determine the primary label "Important-2" corresponding to the secondary label "String (Red Classification)" based on the mapping relationship table.

[0121] The secondary client 102 can receive the secondary label "String (Red Classification)" set by the user for the target schedule. Then, it sends the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule to the mail server 103, so that the primary client 101 can synchronize the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server 103. Based on the mapping table shown in Table 1 above, the primary client 101 queries the mapping table for the primary label corresponding to the secondary label "String (Red Classification)", and thus determines that the primary label is "Important-2".

[0122] As Figure 12 shown, the following takes a primary client 101 in the embodiment shown Figure 7 as an example to introduce in detail the above schedule label synchronization method. Among them, the primary client 101 includes a calendar module 1011, a storage module 1012, and a mail module 1013. The storage module 1012 is connected to the calendar module 1011, and the mail module 1013 is connected to the storage module 1012 and the mail server 103. For the detailed introduction of the primary client 101, please refer to the above embodiment, which will not be elaborated here.

[0123] The secondary client 102 receives the secondary label "String (Red Classification)" set by the user for the target schedule, and then sends the target schedule for synchronization and the secondary label "String (Red Classification)" associated with the target schedule to the mail server 103.

[0124] In response to receiving the target schedule and the secondary label "String (Red Classification)" associated with the target schedule, the mail server 103 sends a schedule update reminder to the mail module 1013 of the primary client 101.

[0125] In response to the schedule update reminder, the mail module 1013 of the primary client 101 synchronizes the target schedule and the secondary label "String (Red Classification)" associated with the target schedule from the mail server 103, and sends the target schedule and the secondary label "String (Red Classification)" associated with the target schedule to the storage module 1012.

[0126] The storage module 1012 writes the received target schedule and the secondary label "String (Red Classification)" associated with the target schedule into the schedule database, and sends a schedule update reminder to the calendar module 1011.

[0127] In response to the schedule update reminder, the calendar module 1011 obtains the mapping table from the storage module 1012, and based on the mapping table, queries and determines the primary label "Important-2" corresponding to the secondary label "String (Red Classification)".

[0128] When the embodiment of the present application receives the secondary label "String (red classification)" set for the target schedule on the secondary client 102 by the user, it can directly synchronize the secondary label "String (red classification)" to the primary client 101 through the mail server 103. Then, through the mapping relation table stored in the primary client 101, the different label systems on the primary client 101 and the secondary client 102 are associated to achieve the conversion and synchronization of schedule labels under different label systems, overcoming the problem that schedule labels cannot be synchronized between clients caused by differences in label systems, and improving the schedule synchronization between clients and the user experience.

[0129] An embodiment of the present invention further provides an electronic device, which includes a processor and a memory. At least one instruction or at least one program segment is stored in the memory, and the at least one instruction or the at least one program segment is loaded and executed by the processor to implement the schedule label synchronization method provided by the above method embodiment.

[0130] The memory can be used to store software programs and modules. The processor runs the software programs and modules stored in the memory to execute various functional applications and data processing. The memory mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for functions, etc.; the data storage area can store data created according to the use of the device, etc. In addition, the memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory can also include a memory controller to provide the processor with access to the memory.

[0131] In a specific embodiment, Figure 13 The figure shows a schematic structural diagram of an electronic device for implementing the embodiment of the present invention. The electronic device 1300 can be a computer terminal, a mobile terminal or other devices. The electronic device 1300 can also participate in forming or include the primary client 101 or the secondary client 102 provided by the embodiment of the present invention.

[0132] As Figure 13 shown, an embodiment of the present invention provides an electronic device 1300, including: a processor 1301 and a memory 1302. Computer program instructions are stored in the memory 1302. When the computer program instructions are run by the processor, the processor 1301 executes the schedule label synchronization method described in the above embodiment.

[0133] Further, as Figure 13As shown, the electronic device 1300 further includes a network interface 1303, an input device 1304, a hard disk 1305, and a display device 1306.

[0134] The various interfaces and devices described above can be interconnected through a bus architecture. The bus architecture can include any number of interconnected buses and bridges. Specifically, one or more central processing units (CPUs) represented by the processor 1301 and various circuits of one or more memories represented by the memory 1302 are connected together. The bus architecture can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. It can be understood that the bus architecture is used to implement the connection and communication between these components. In addition to the data bus, the bus architecture also includes a power bus, a control bus, and a status signal bus, which are well known in the art and will not be described in detail herein.

[0135] The network interface 1303 can be connected to a network (such as the Internet, a local area network, etc.), obtain relevant data from the network, and can be stored in the hard disk 1305.

[0136] The input device 1304 can receive various instructions input by an operator and send them to the processor 1301 for execution. The input device 1304 can include a keyboard or a pointing device, for example, a mouse, a trackball, a touchpad, or a touch screen, etc.

[0137] The display device 1306 can display the results obtained by the processor 1301 executing instructions.

[0138] The memory 1302 is used to store programs and data necessary for the operation of the operating system, as well as data such as intermediate results during the calculation of the processor 1301.

[0139] It can be understood that the memory 1302 in the embodiments of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. The memory 1302 of the devices and methods described herein is intended to include, but is not limited to, these and any other suitable types of memories.

[0140] In some embodiments, the memory 1302 stores the following elements, executable modules, or data structures, or subsets thereof, or extended sets thereof: an operating system 13021 and an application program 13022.

[0141] Among them, the operating system 13021 includes various system programs, such as the framework layer, the core library layer, the driver layer, etc., which are used to implement various basic services and handle hardware-based tasks. The application program 13022 includes various application programs, such as the Browser, etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present invention may be included in the application program 13022.

[0142] When the above-mentioned processor 1301 calls and executes the application programs and data stored in the memory 1302, specifically, when it is the program or instruction stored in the application program 13022, it executes the schedule label synchronization method as described in the above embodiment.

[0143] The method disclosed in the above embodiment of the present invention can be applied to or implemented by the processor 1301. The processor 1301 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 1301 or the instructions in the form of software. The above-mentioned processor 1301 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by the hardware decoding processor, or executed by the combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. This storage medium is located in the memory 1302, and the processor 1301 reads the information in the memory 1302 and combines its hardware to complete the steps of the above method.

[0144] It can be understood that these embodiments described herein can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or a combination thereof.

[0145] For software implementation, the techniques described herein can be implemented by modules (such as procedures, functions, etc.) that execute the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented within the processor or external to the processor.

[0146] In addition, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which, when run by a processor, causes the processor to execute the schedule label synchronization method as described in the above embodiment.

[0147] In several embodiments provided in the present application, it should be understood that the disclosed methods and apparatuses can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical or other forms.

[0148] In addition, each functional unit in various embodiments of the present invention can be integrated in a processing unit, or each unit can be physically included separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a hardware plus software functional unit.

[0149] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit stored in a storage medium includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute some steps of the transceiver methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc that can store program codes.

[0150] The above is the preferred implementation manner of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle described herein, several improvements and refinements can still be made, and these improvements and refinements should also be regarded as the protection scope of the present invention.

Claims

1. A schedule label synchronization method, characterized in that, Applied to the primary client, where the primary client and the secondary client are connected to the same mail server, wherein, the primary client uses a first tag system, and the first tag system includes multiple primary tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the primary client, and the mapping relation table contains the mapping relation between the primary tags used by the primary client and the secondary tags used by the secondary client; the method includes the following steps: Receiving a first primary tag set by the user for the target schedule, and the first primary tag is one of the multiple primary tags; Based on the mapping relation table, querying and determining a first secondary tag corresponding to the first primary tag, and the first secondary tag is one of the multiple secondary tags; Sending the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server, so that the secondary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

2. The schedule tag synchronization method according to claim 1, wherein the mapping relation between the primary tag and the secondary tag includes at least one of one-to-one, one-to-many, many-to-one, and many-to-many mapping relations.

3. The schedule tag synchronization method according to claim 1, wherein the mapping relation table is generated based on the mapping relation between the primary tags of the primary client and the secondary tags of the secondary client input by the user through the configuration interface; wherein, all the secondary tags set on the secondary client are obtained from the mail server in response to a configuration request input by the user.

4. The schedule label synchronization method according to claim 1, wherein The mapping relation table is stored in the schedule database in the primary client, and the schedule database also stores a schedule information table, and the schedule information table contains the schedule detailed information corresponding to each target schedule and the first primary tag associated with the target schedule.

5. A schedule label synchronization method, characterized in that, Applied to the secondary client, where the secondary client and the primary client are connected to the same mail server, wherein, the primary client uses a first tag system, and the first tag system includes multiple primary tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the primary client, and the mapping relation table contains the mapping relation between the primary tags used by the primary client and the secondary tags used by the secondary client; the method includes the following steps: Receiving a first secondary tag set by the user for the target schedule, and the first secondary tag is one of the multiple secondary tags; Sending the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server, so that the primary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server, and based on the mapping relation table, querying and determining a first primary tag corresponding to the first secondary tag, and the first primary tag is one of the multiple primary tags.

6. A main client, characterized in that, Connected to the same mail server as the secondary client. The primary client uses a first tag system, and the first tag system includes multiple primary tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; the primary client includes: A storage module for storing a mapping relation table, where the mapping relation table contains the mapping relation between the primary tags used by the primary client and the secondary tags used by the secondary client; A calendar module connected to the storage module, for receiving a first primary tag set by the user for a target schedule, where the first primary tag is one of the multiple primary tags; obtaining the mapping relation table from the storage module; based on the mapping relation table, querying and determining a first secondary tag corresponding to the first primary tag, where the first secondary tag is one of the multiple secondary tags; sending the first secondary tag associated with the target schedule to the storage module; where the storage module is further configured to, in response to receiving the first secondary tag associated with the target schedule, send the target schedule and the first secondary tag associated with the target schedule to the mail module; A mail module connected to the storage module and the mail server, for receiving the target schedule and the first secondary tag associated with the target schedule sent by the storage module; sending the target schedule and the first secondary tag associated with the target schedule for synchronization to the mail server, so that the secondary client can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

7. The primary client according to claim 6, wherein: The mapping relation table is generated by the storage module based on the mapping relation between the primary tags of the primary client and the secondary tags of the secondary client input by the user through a configuration interface; Wherein, all the secondary tags set on the secondary client are obtained by the calendar module from the mail server in response to a configuration request input by the user.

8. The main client according to claim 6, characterized in that, The mapping relation table is stored in a schedule database in the storage module, and the schedule database also stores a schedule information table, where the schedule information table contains the schedule detailed information corresponding to each target schedule and the first primary tag associated with the target schedule.

9. A schedule label synchronization system, characterized in that, Including: A primary client, a secondary client, and a mail server connected to the primary client and the secondary client; Wherein, the primary client uses a first tag system, and the first tag system includes multiple primary tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the primary client, and the mapping relation table contains the mapping relation between the primary tags used by the primary client and the secondary tags used by the secondary client; The main client is used to receive a first main tag set by a user for a target schedule, where the first main tag is one of multiple main tags; based on the mapping relation table, query and determine a first secondary tag corresponding to the first main tag, where the first secondary tag is one of multiple secondary tags; and send the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server. The secondary client is used to synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server.

10. The schedule tag synchronization system according to claim 9, wherein The mail server is used to, in response to receiving the target schedule and the first secondary tag associated with the target schedule, send a schedule update reminder to the secondary client, so that the secondary client synchronizes the target schedule and the first secondary tag associated with the target schedule from the mail server in response to the schedule update reminder.

11. A schedule label synchronization system, characterized in that, Comprising: A main client, a secondary client, and a mail server connected to the main client and the secondary client; Wherein, the main client uses a first tag system, and the first tag system includes multiple main tags; the secondary client uses a second tag system, and the second tag system includes multiple secondary tags; a mapping relation table is stored in the main client, and the mapping relation table contains the mapping relation between the main tags used by the main client and the secondary tags used by the secondary client; The secondary client is used to receive a first secondary tag set by a user for a target schedule, where the first secondary tag is one of multiple secondary tags; and send the target schedule for synchronization and the first secondary tag associated with the target schedule to the mail server. The main client is used to synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server, and based on the mapping relation table, query and determine a first main tag corresponding to the first secondary tag, where the first main tag is one of multiple main tags.

12. The schedule tag synchronization system according to claim 11, wherein The mail server is used to, in response to receiving the target schedule and the first secondary tag associated with the target schedule, send a schedule update reminder to the main client, so that the main client synchronizes the target schedule and the first secondary tag associated with the target schedule from the mail server in response to the schedule update reminder.

13. An electronic device, characterized in that, Comprising: A processor; And a memory, in which computer program instructions are stored, Wherein, when the computer program instructions are run by the processor, the processor is caused to execute the schedule tag synchronization method according to any one of claims 1-5.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, and when the computer program instructions are run by the processor, the processor is caused to execute the schedule tag synchronization method according to any one of claims 1-5.

Images