Schedule tag synchronization method and system, main client, electronic device and medium

Abstract

The application relates to the technical field of communication, and particularly provides a schedule label synchronization method, a system, a main client, an electronic device 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 a mapping relationship table, a first auxiliary label corresponding to the first main label is inquired and determined, the first auxiliary label being one of a plurality of auxiliary labels; a target schedule and the first auxiliary label associated with the target schedule are sent to a mail server for synchronization, so that a secondary client can synchronize the target schedule and the first auxiliary label associated with the target schedule from the mail server. Through the above method, the application can solve the problem that the schedule labels cannot be synchronized between the clients with different label systems.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method, system, master client, electronic device, and medium for synchronizing schedule tags. Background Technology

[0002] Currently, a mail server is a device used to manage the sending and receiving of emails, and it can connect 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, different clients may use different tagging systems. This "difference in tagging systems" can be understood as different tag dimensions used to annotate schedules, or in other words, different dimensions for schedule tags. For clients with different tagging systems, the incompatibility of the tag dimensions used for schedule annotation means that if a user annotates a schedule on one client, other clients cannot synchronize that annotation, resulting in poor schedule synchronization between clients and negatively impacting the user experience.

[0004] Therefore, how to solve the problem of calendar tags not being synchronized between different clients with different tag systems and improve the calendar synchronization between clients has become an urgent problem to be solved. Summary of the Invention

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

[0006] To address the aforementioned technical problems, this invention provides a calendar tag synchronization method applied to a primary client and a secondary client connected to the same mail server. The primary client uses a first tagging system comprising multiple primary tags; the secondary client uses a second tagging system comprising multiple secondary tags. The primary client stores a mapping table containing the mapping relationships between the primary tags used by the primary client and the secondary tags used by the secondary client. The calendar tag synchronization method includes:

[0007] Receive the first primary label set by the user for the target schedule. The first primary label is one of multiple primary labels. Based on the mapping table, query and determine the first secondary label corresponding to the first primary label. The first secondary label is one of multiple secondary labels. Send the target schedule and the first secondary label associated with the target schedule to the mail server for synchronization, 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] This embodiment establishes a mapping table to associate the different tag systems used by the main client and the secondary client, and stores it in the main client. When the main client receives the first main tag set by the user for the target schedule, it can use the mapping table to query the first secondary tag applicable to the secondary client and corresponding to the first main tag. This overcomes the problem of schedule tags not being synchronized between clients due to differences in tag systems, and improves the schedule synchronization between clients and the user experience.

[0009] According to some embodiments of the present invention, the mapping relationship between the main tag and the sub-tag includes at least one of one-to-one, one-to-many, many-to-one, and many-to-many mapping relationships.

[0010] According to some embodiments of the present invention, the mapping table is generated based on the mapping relationship between the main label of the main client and the sub-label of the sub-client entered by the user through the configuration interface; wherein, all sub-labels set on the sub-client are obtained from the mail server in response to the configuration request entered by the user.

[0011] This embodiment generates a mapping table through user-defined configuration, providing users with personalized settings and improving the user experience.

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

[0013] Secondly, embodiments of the present invention provide a schedule tag synchronization method applied to a secondary client, wherein the secondary client and the primary client are connected to the same mail server, wherein the primary client uses a first tag system, the first tag system including multiple primary tags; the secondary client uses a second tag system, the second tag system including multiple secondary tags; the primary client stores a mapping table, the mapping table containing the mapping relationship 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] Receive the first sub-label set by the user for the target schedule. The first sub-label is one of multiple sub-labels. Send the target schedule and the first sub-label associated with the target schedule to the mail server for synchronization, so that the main client can synchronize the target schedule and the first sub-label associated with the target schedule from the mail server. Based on the mapping table, query and determine the first primary label corresponding to the first sub-label. The first primary label is one of multiple primary labels.

[0015] Thirdly, embodiments of the present invention provide a primary client connected to a secondary client on the same mail server, wherein the primary client uses a first tagging system, the first tagging system including multiple primary tags; the secondary client uses a second tagging system, the second tagging system including multiple secondary tags; the primary client includes:

[0016] The storage module stores the mapping relationship table, which contains the mapping relationship between the main tag used by the main client and the sub-tag used by the sub-client.

[0017] The calendar module, connected to the storage module, is used to receive the first primary label set by the user for the target schedule, where the first primary label is one of multiple primary labels; retrieve the mapping table from the storage module; based on the mapping table, query and determine the first secondary label corresponding to the first primary label, where the first secondary label is one of multiple secondary labels; and send the first secondary label associated with the target schedule to the storage module; wherein the storage module is also used to send the target schedule and the first secondary label associated with the target schedule to the email module in response to receiving the first secondary label associated with the target schedule.

[0018] The email module, connected to the storage module and the email server, is used to receive the target schedule and the first secondary label associated with the target schedule sent by the storage module; and to send the target schedule and the first secondary label associated with the target schedule to the email server for synchronization, so that the secondary client can synchronize the target schedule and the first secondary label associated with the target schedule from the email server.

[0019] According to some embodiments of the present invention, the mapping relationship table is generated by the storage module based on the mapping relationship between the main label of the main client and the sub-label of the sub-client entered by the user through the configuration interface; wherein, all sub-labels set on the sub-client are obtained by the calendar module from the mail server in response to the configuration request entered by the user.

[0020] According to some embodiments of the present invention, the mapping relationship table is stored in the schedule database in the storage module. The schedule database also stores a schedule information table, which contains detailed schedule information corresponding to each target schedule and a first primary label associated with the target schedule.

[0021] Fourthly, embodiments of the present invention provide 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, the first tag system including multiple main tags; the secondary client uses a second tag system, the second tag system including multiple secondary tags; the main client stores a mapping relationship table, the mapping relationship table containing the mapping relationship between the main tags used by the main client and the secondary tags used by the secondary client.

[0022] The primary client receives the first primary label set by the user for the target schedule (this primary label is one of multiple primary labels); based on a mapping table, it queries and determines the first secondary label corresponding to the first primary label (this secondary label is one of multiple secondary labels); and it sends the target schedule and the associated primary label to the mail server for synchronization. The secondary client synchronizes the target schedule and the associated primary label from the mail server.

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

[0024] This embodiment utilizes an email server to send schedule update reminders to a secondary client, enabling real-time management and automatic updates of schedules, thereby improving the timeliness of schedule tag synchronization.

[0025] Fifthly, embodiments of the present invention provide 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, the first tag system including multiple main tags; the secondary client uses a second tag system, the second tag system including multiple secondary tags; the main client stores a mapping relationship table, the mapping relationship table containing the mapping relationship 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 the first secondary label set by the user for the target schedule, which is one of multiple secondary labels; and to send the target schedule and the first secondary label associated with the target schedule to the mail server for synchronization.

[0027] The main client is used to synchronize the target schedule and the first sub-label associated with the target schedule from the mail server, and to query and determine the first main label corresponding to the first sub-label based on the mapping table. The first main label is one of multiple main labels.

[0028] This embodiment can directly synchronize the first secondary tag set by the user for the target schedule on the secondary client to the primary client via the mail server. Then, through the mapping table stored in the primary client, the different tag systems on the primary and secondary clients are associated, realizing the conversion and synchronization of schedule tags under different tag systems. This overcomes the problem of schedule tags not being synchronized between clients due to differences in tag systems, and improves the schedule synchronization between clients and the user experience.

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

[0030] This embodiment utilizes an email server to send schedule update reminders to the main client, enabling real-time management and automatic updates of schedules, thereby improving the timeliness of schedule tag synchronization.

[0031] Sixthly, embodiments of the present invention provide an electronic device, including: a processor; and a memory, wherein computer program instructions are stored in the memory.

[0032] When the computer program instructions are executed by the processor, the processor performs the schedule tag synchronization method described in the above technical solution.

[0033] In a seventh aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the schedule tag synchronization method described above. Attached Figure Description

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

[0035] Figure 2 This is a schematic diagram of an example of a computer's calendar display interface;

[0036] Figure 3 This is a flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

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

[0038] Figure 5 This is a schematic diagram illustrating an example of the schedule display interface of a schedule app installed on a mobile phone and a schedule app installed on a computer.

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

[0040] Figure 7 This is a schematic diagram of the main client in an embodiment of the present invention;

[0041] Figure 8 This is a flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

[0042] Figure 9 This is a flowchart illustrating the configuration of a mapping relationship table in a schedule tag synchronization method according to an embodiment of the present invention.

[0043] Figure 10 This is a flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

[0044] Figure 11 A flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

[0045] Figure 12 This is a flowchart of a schedule tag synchronization method according to an embodiment of the present invention;

[0046] Figure 13 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0047] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.

[0048] A mail server is a device used to manage the sending and receiving of emails, and it can connect 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.

[0049] However, different clients may use different tagging systems, or in other words, use different tag dimensions to annotate schedules. Hereinafter, "the tags used to annotate schedules" will be referred to as schedule tags. Currently, for clients with different tagging systems, if a user annotates a schedule on one client, other clients cannot synchronize that schedule annotation. For example, if client one uses the first schedule tag to annotate a schedule, and client two uses the second schedule tag to annotate a schedule; because the tag dimensions of the first and second schedule tags are different, client one is incompatible with the second schedule tag, and client two is incompatible with the first schedule tag, resulting in a lack of synchronization between schedule tags on client one and client two, thus affecting the user experience.

[0050] Therefore, how to solve the problem of calendar tags not being synchronized between different clients with different tag systems and improve the calendar synchronization between clients has become an urgent problem to be solved.

[0051] To address the issue of incompatibility in synchronizing calendar tags between clients using different tag systems, this application proposes a calendar tag synchronization system. This system includes a primary client, a secondary client, and a mail server connected to both the primary and secondary clients. The primary client uses a first tag system, which includes multiple primary tags. The secondary client uses a second tag system, which includes multiple secondary tags. The primary client stores a mapping table containing the mapping relationships between the primary tags used by the primary client and the secondary tags used by the secondary client.

[0052] The primary client receives the first primary label set by the user for the target schedule. Then, based on a mapping table, it queries and determines the first secondary label corresponding to the first primary label. Finally, it sends the target schedule and the associated first secondary label to the mail server for synchronization, enabling the secondary client to synchronize the target schedule and its associated first secondary label from the mail server.

[0053] The calendar tag synchronization system proposed in this application establishes a mapping table to associate the different tag systems used by the main client and the sub-client, and stores it in the main client. When the main client receives the first main tag set by the user for the target calendar, it can use the mapping table to query the first sub-tag applicable to the sub-client and corresponding to the first main tag. This overcomes the problem of calendar tags not being synchronized between clients due to differences in tag systems, and improves the calendar synchronization between clients and the user experience.

[0054] Before providing a detailed description of the embodiments of this application, a brief introduction will be given to the "schedule labeling", "schedule tag dimensions", "email communication protocol" and "client" involved in the embodiments of this application.

[0055] First, by setting schedule tags for target schedules, schedule annotation can be completed. In specific application scenarios, "schedule annotation" can be used for schedule categorization and / or schedule reminders, or in other words, "schedule tags" can be used for schedule categorization and / or highlighting. Schedule annotation enables personalized schedule management, improving the convenience and intelligence of schedule management.

[0056] The "schedule tag dimension" or "tag dimension used for schedule labeling" can be understood as the field type of the schedule tag. The field type of the schedule tag is related to the email communication protocol or the client's operating system used in actual application. Commonly used email communication protocols may include, but are not limited to, Exchange protocol, EAS (Exchange Active Sync) protocol, POP3 protocol, and IMAP protocol. Operating systems may include, but are not limited to, Windows, Android, Harmony, and EulerOS. Client device types may include, but are not limited to, mobile phones, tablets, and computers. This application embodiment does not limit the email communication protocol used by the client or the client's device type.

[0057] The following section uses the Exchange protocol, EAS (Exchange Active Sync) protocol, and Android operating system as examples to introduce the field types of calendar tags. For the Exchange protocol or EAS (Exchange Active Sync) protocol, the field type for calendar tags can be a Category field; that is, if a client (such as a computer) communicates using the Exchange protocol or EAS (Exchange Active Sync) protocol, it can generally use the Category field to mark calendar events. For clients using Android operating system mobile devices, the field type for calendar tags can be a Piroirty field; that is, clients using Android operating system mobile devices generally use the Piroirty field to mark calendar events. Because the Category field and Piroirty field have different field types, they belong to different tag dimensions and are not compatible with each other.

[0058] The embodiments proposed in this application will now be described in detail one by one. First, the schedule tag synchronization system proposed in the embodiments of this application will be introduced.

[0059] like Figure 1 As shown, the calendar tag synchronization system 100 of this embodiment includes: a main client 101, a secondary client 102, and a mail server 103 connected to the main client and the secondary client.

[0060] The primary client 101 uses a first tag system, which includes multiple primary tags. The secondary client 102 uses a second tag system, which includes multiple secondary tags. The primary client 101 stores a mapping table containing the mapping relationships between the primary tags used by the primary client 101 and the secondary tags used by the secondary client 102.

[0061] The following will first describe the “main client 101”, “secondary client 102”, “first tag system”, “secondary tag system”, “main tag” and “secondary tag” involved in the embodiments of this application.

[0062] First, a "client" refers to an application (app) or webpage that runs on a hardware device (computer, mobile phone, or tablet, etc.). Applications can be categorized into native apps based on the operating system and third-party downloaded apps. For a client running on a computer, it can be a native app running on a desktop operating system, a third-party downloaded app, or a webpage running in a desktop browser. For a client running on a mobile phone, it can be a native app running on a mobile device's operating system, a third-party downloaded app, or a webpage running in a mobile device's browser.

[0063] In this embodiment, "main client 101" and "secondary client 102" are used only to indicate clients connected to the same mail server 103 using different tag systems. Their device types can be the same or different; no limitation is made on the device type here. Main client 101 and secondary client 102 can belong to different hardware devices or the same hardware device. That is, main client 101 and secondary 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 mobile phone clients as an example, the native email app on the phone can log in to third-party email accounts. The native email app is one client, while the dedicated app or webpage for the third-party email account is another client.

[0065] The schedule tags (i.e., main tags) used by the main client 101 under the "first tag system" and the schedule tags (i.e., secondary tags) used by the secondary client 102 under the "second tag system" have different dimensions, or in other words, different field types.

[0066] The number and content of the main tags used by the main client 101 can be customized, and the number and content of the sub-tags used by the sub-client 102 can also be customized. The tag content of the main tags and the tag content of the sub-tags can be the same or different. The "tag content" can be understood as schedule labeling information.

[0067] In one example, three main labels can be set on the main client 101, with the label content being "Work Category," "Study Category," and "Social Category," respectively. These three main labels allow for the categorization of schedules into "Work," "Study," and "Social" types. However, six sub-labels can be set on the secondary client 102, with the label content being "Red Category," "Yellow Category," "Blue Category," "Green Category," "Orange Category," and "Purple Category," respectively. These six sub-labels allow for the categorization of schedules using color categories. In this example, the label content of the main labels and the label content of the sub-labels are different; in other words, the target categorization information is different.

[0068] In other examples, a secondary label with the same content as the primary label can be set on the secondary client 102, or a primary label with the same content as the secondary label can be set on the primary client 101. The specific settings can be customized according to the actual application requirements. Here, there is no limitation on the number and content of the primary and secondary labels.

[0069] In one embodiment, the main client 101 may be a calendar app installed on a mobile phone, and the main label may be the Piroirty field. The calendar app installed on the mobile phone may use the Piroirty field to classify schedule priorities, or in other words, classify them by importance. Specifically, the Piroirty field is used to divide schedules into "important category", "normal category" and "ignore category".

[0070] In one embodiment, the secondary client 102 can be a calendar app installed on a computer, and the secondary label can be a Category field. The calendar app installed on the computer can use the Category field to divide the schedule into eight color-related schedule labels, such as "blue category," "yellow category," "red category," "orange category," or "green category." In one embodiment, as... Figure 2 As shown, in the computer's schedule display interface 200, the user can right-click on the schedule box 21 containing the target schedule to open the settings menu 22. The settings menu 22 is generally used to display options related to schedule management. Figure 2 In one example of the settings menu 22 shown, settings menu 22 can be used to display "Quick Print," "Receive," "Temporary," "Reject," "Create New Time," "Reply," "Reply All," "Forward," "Show," "Category," and "Delete." Then, left-clicking "Category" in settings menu 22 opens category menu 23, which is generally used to display options related to schedule category settings. Figure 2In one example of the category menu 23 shown, category menu 23 can be used to display "Blue Category", "Yellow Category", "Red Category", "Orange Category", "Green Category", "All Categories", and "Set New Category". Then, in category menu 23, select the "Blue Category", "Yellow Category", "Red Category", "Orange Category", or "Green Category" you want to set for the target schedule. When you need to create a new custom category, you can left-click "Set New Category" in category menu 23 to enter the creation process for the new category, such as a label for a new color.

[0071] like Figure 3 As shown, the schedule tag synchronization system 100 proposed in the above embodiments will be further described below.

[0072] The primary client 101 receives a first primary tag set by the user for a target schedule. The first primary tag is one of multiple primary tags. Based on a mapping table, it queries and determines the first secondary tag corresponding to the first primary tag. The first secondary tag is one of multiple secondary tags. It then sends the target schedule and the associated first secondary tag to the mail server 103 for synchronization. The secondary client 102 synchronizes the target schedule and the associated first secondary tag from the mail server 103. When the primary client 101 receives the first primary tag set by the user for the target schedule, it uses the mapping table to query the corresponding first secondary tag, thereby establishing the association between the first tag system and the second tag system, providing a foundation for schedule tag 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 secondary tag associated with the target schedule, so that the secondary client 102 can synchronize the target schedule and the first secondary tag associated with the target schedule from the mail server 103 in response to the schedule update reminder, thereby realizing real-time management and automatic updates of the schedule and improving the timeliness of schedule tag synchronization.

[0074] The above embodiments associate the different tag systems used by the main client 101 and the secondary client 102 by establishing a mapping relationship table and storing it in the main client 101. When the main client 101 receives the first primary tag set by the user for the target schedule, it can use the mapping relationship table to query the first secondary tag applicable to the secondary client 102 corresponding to the first primary tag. This overcomes the problem of schedule tags not being synchronized between clients due to differences in tag systems, and improves the schedule synchronization between clients and the user experience.

[0075] In one embodiment, the mapping relationship table includes at least one of the following mapping relationships: one-to-one, one-to-many, many-to-one, and many-to-many. "One-to-one" refers to a mapping relationship between one main tag and one sub-tag; "one-to-many" refers to a mapping relationship between one main tag and multiple sub-tags; "many-to-one" refers to a mapping relationship between multiple main tags and one sub-tag; and "many-to-many" refers to a mapping relationship between multiple main tags and multiple sub-tags.

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

[0077] Table 1 Mapping Relationship Table

[0078] Main client - Piority field Secondary Client - Category Field Important-2 String (red category) Ignore-0 String (Yellow Category) Normal-1 String (blue category)

[0079] In the mapping table shown in Table 1 above, there is a one-to-one mapping relationship between the main label and the sub-label. The main client 101 uses the "Piority" field as the schedule label, and the "Important-2", "Ignore-0", and "Normal-1" fields are used to indicate the priority of the schedule. Schedules labeled "Important-2" have the highest priority (these are called important schedules), schedules labeled "Normal-1" have the next highest priority (these are called ordinary schedules), and schedules labeled "Ignore-0" have the lowest priority (these are called ignored schedules). The sub-client 102 uses the "Category" field as the schedule label, and the "String (Red Category)", "String (Yellow Category)", and "String (Blue Category)" fields are used to indicate the category of the schedule. As shown in Table 1 above, important schedules correspond to the red category, ignored schedules correspond to the yellow category, and ordinary schedules correspond to the blue category.

[0080] like Figure 4 As shown in Table 1 above, an example of the schedule tag synchronization method proposed in this application embodiment will be described in detail below with reference to the mapping relationship table. This schedule tag synchronization method is applied to the main client 101 in the schedule tag synchronization system 100 in the above embodiment. 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 label "Important-2" set by the user for the target schedule.

[0082] Step 120: Based on the mapping table, query and determine the sub-label "String (Red Category)" corresponding to the main label "Important-2".

[0083] The main client 101 can receive the user's setting of the main label "Important-2" for the target schedule, and then, based on the mapping relationship table shown in Table 1 above, query the sub-label corresponding to the main label "Important-2" in the mapping relationship table, thereby determining the sub-label as "String (red category)".

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

[0085] After determining that the sub-tag is "String (Red Category)", the target schedule and the sub-tag "String (Red Category)" associated with the target schedule are sent to the mail server 103 for synchronization, so that the secondary client 102 can synchronize the target schedule and the sub-tag "String (Red Category)" associated with the target schedule from the mail server 103.

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

[0087] Generally, the secondary client 102 can use the same email communication protocol as the mail server 103, achieving compatibility between the secondary client 102 and the mail server 103. Sub-labels set on the secondary client 102 can be directly synchronized to the mail server 103 and other clients using the same email communication protocol. For example, if the secondary client 102 uses a Category field as a sub-label, and the sub-label includes "String (Red Category)", "String (Yellow Category)", and "String (Blue Category)" fields, then the same sub-labels will also be synchronously set in other clients using the same email communication protocol. Furthermore, during the calendar label synchronization process, in response to receiving the target calendar and the first sub-label associated with the target calendar for synchronization, the mail server 103 can also send calendar update reminders to other clients using the same email communication protocol, excluding the secondary client 102, so that other clients can synchronize the target calendar and the first sub-label associated with the target calendar from the mail server 103. For example, in response to receiving the target schedule and the first sub-label "String (blue category)" associated with the target schedule for synchronization, mail server 103 sends a schedule update reminder to other clients using the same mail communication protocol, except for sub-client 102, so that other clients can synchronize the target schedule and the first sub-label "String (blue category)" associated with the target schedule from mail server 103.

[0088] In one embodiment, in step 130 above, only the name of the target schedule for synchronization and the associated sub-tag "String (Red Category)" can be sent to the mail server 103, without sending the detailed schedule information of the target schedule. The secondary client 102 can find the corresponding target schedule based on the schedule name and associate the sub-tag "String (Red Category)" with it. This method can reduce the amount of data transmission and further improve synchronization efficiency.

[0089] In this embodiment, the main client 101 stores a mapping table that associates different tag systems on the main client 101 and the secondary client 102. When it receives the main tag "Important-2" set by the user for the target schedule, it obtains the secondary tag "String (Red Category)" corresponding to the main tag "Important-2" for the secondary client 102 by referring to the mapping table. This overcomes the problem of schedule tags not being synchronized between clients due to differences in tag systems, realizes the synchronization of schedule tags between the secondary client 102 and the main client 101, and improves the schedule synchronization between clients and the user experience.

[0090] In one embodiment, the mapping table can be stored in a schedule database in the main client 101. The schedule database also stores a schedule information table, which may contain detailed schedule information corresponding to each target schedule and a first primary tag associated with the target schedule. Understandably, when the main client 101 receives the first primary tag set by the user for the target schedule, it can also store the first primary tag 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 main label is displayed differently on the schedule display interface of the main client 101 and the secondary label is displayed differently on the schedule display interface of the secondary client 102. The "display method" 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, weight and italics. The specific settings can be made according to actual needs and are not limited here.

[0092] In one embodiment, each main label can be displayed in the same way on the schedule display interface of the main client 101, wherein different main labels have different specific appearances on the schedule display interface of the main client 101; each sub-label can be displayed in the same way on the schedule display interface of the sub-client 102, wherein different sub-labels have different specific appearances on the schedule display interface of the sub-client 102. By using the same type of display method, it is convenient to ensure the uniformity and intuitiveness of the display of main labels and sub-labels on their respective schedule display interfaces. For example, different main labels or sub-labels can be displayed using different symbols, or using different colors for text highlighting, or using different degrees of text folding, or using different font styles, etc., without limitation.

[0093] The following example illustrates the display interface (hereinafter referred to as the "scheduling display interface") of the scheduling apps on the main client 101 and the secondary client 102, using the mapping relationship table shown in Table 1 above, the main client 101 as a scheduling app installed on a mobile phone, and the secondary client 102 as a scheduling app installed on a computer as examples. Figure 5As shown, there are 6 events scheduled for December 14, 2023, at 10:30, 15:00, 16:00, 19:00, 19:10, and 19:30. The events at 10:30, 15:00, and 16:00 are marked as regular events on the mobile calendar app (marked in blue on the desktop calendar app); the events at 19:00 and 19:30 are marked as ignored events on the mobile calendar app (marked in yellow on the desktop calendar app); and the event at 19:10 is marked as important events on the mobile calendar app (marked in red on the desktop calendar app).

[0094] In the calendar display interface 500b of the calendar app installed on the computer in this example, each calendar box displays all the calendar data for each event. The calendar data may include the event name and detailed event information, which may include time, location, and other event details. In the calendar display interface 500b, different colored text highlights distinguish between blue, yellow, and red categories. Understandably, in... Figure 5 In the calendar display interface 500b, blue, yellow and red are only represented by different shades of gray, which is not the actual display effect during application.

[0095] In the calendar display interface 500a of the calendar app installed on the phone in this example, the ignored events at 19:00 and 19:30 are displayed in thinner font, and the event data is partially collapsed, showing only the event name and hiding the detailed event information. Compared to the font of the ignored events at 19:00 and 19:30, the regular events at 10:30, 15:00, and 16:00 and the important event at 19:10 are displayed in thicker font, making them more eye-catching. The event data for the regular events at 10:30, 15:00, and 16:00 and the important event at 19:10 are not collapsed, displaying the event name and at least some of the event details. The important event at 19:10 is marked with a flag to emphasize its importance. By highlighting important events and collapsing ignored events, the importance of events is made more intuitive, improving the user experience.

[0096] Generally, when schedule data is partially collapsed, only the schedule name is displayed; when schedule data does not need to be collapsed, the full schedule name and details are displayed. However, in practical applications, the schedule data displayed in the schedule box is also limited by the maximum space of the schedule box and the character length of the schedule name and details. For example, when schedule data needs to be partially collapsed, if the schedule name exceeds the maximum number of characters that the schedule box can display, only part of the schedule name can be displayed. Similarly, when schedule data does not need to be collapsed, if the total number of characters in the schedule name and details exceeds the maximum number of characters that the schedule box can display, as much schedule data as possible should be displayed. For example, depending on the actual situation, the schedule name and some details can be displayed, or only the schedule name can be displayed, or only part of the schedule name can be displayed.

[0097] The above embodiments display target schedules in different ways based on the content of the main tag in the schedule display interface of the main client, and in different ways based on the content of the sub-tag in the schedule display interface of the secondary client. Using different display methods to distinguish different schedule tags allows the underlying tag content to be displayed intuitively, making schedule categorization clearer and thus improving the user experience.

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

[0099] The configuration process for the mapping table can specifically include: responding to a 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 returns all the sub-labels set on the secondary client 102. Receiving all the sub-labels set on the secondary client 102, and generating and displaying a configuration interface based on all the primary labels and all the sub-labels set on the primary client 101. Receiving the mapping relationship between the primary labels of the primary client 101 and the sub-labels of the secondary client 102 input by the user through the configuration interface, and generating a mapping table.

[0100] like Figure 6As shown, the configuration process of the mapping relationship table is introduced by taking the main client 101 as a calendar app installed on a mobile phone, and using the Piroirty field to divide the calendar into "Important Category" and "Ignore Category"; and the secondary client 102 as a calendar app installed on a computer, and using the Category field to divide the calendar into "Blue Category", "Yellow Category", "Red Category", "Orange Category" and "Green Category".

[0101] In the schedule display interface 600a of the schedule app installed on the mobile phone, the user can left-click 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. Figure 6 In one example shown, settings menu 62 includes "Jump to a specified date," "Account Management," "Print," and "Settings." Then, left-clicking "Account Management" in settings menu 62 will navigate to account management page 600b. On account management page 600b, right-clicking "Schedule" will open schedule menu 63, which displays options related to schedule settings. Figure 6 In one example shown, the schedule menu 63 includes "Sync Now," "Hide All," and "Priority Settings." Left-clicking "Priority Settings" in the schedule menu 63 accesses the priority settings page 600c. On the priority settings page 600c, users can configure "Important Categories" and "Ignore Categories" according to their needs. Figure 6 This section describes the mapping relationships between various "Exchange Categories," which are categorized as "Blue Category," "Yellow Category," "Red Category," "Orange Category," and "Green Category." For example, you can select both "Important" and "Red Category" to establish a mapping between them, meaning events marked as "Red Category" correspond to important events. Similarly, you can select "Ignore," "Blue Category," and "Yellow Category" to establish a mapping between them, meaning events marked as "Blue Category" or "Yellow Category" correspond to ignored events.

[0102] The structure of the main client 101 described above will be explained in detail below.

[0103] like Figure 7As shown, in this embodiment of the invention, the main client 101 and the secondary client 102 are connected to the same mail server 103. The main client 101 uses a first tag system, which includes multiple primary tags; the secondary client 102 uses a second tag system, which includes multiple secondary tags. The main client 101 includes a calendar module 1011, a storage module 1012, and an email module 1013. The storage module 1012 is connected to the calendar module 1011, and the email module 1013 is connected to both the storage module 1012 and the mail server 103.

[0104] The storage module 1012 stores a mapping relationship table, which contains the mapping relationship between the primary tag used by the main client 101 and the secondary tag used by the secondary client 102. The calendar module 1011 receives a first primary tag set by the user for a target schedule, where the first primary tag is one of multiple primary tags. In one embodiment, the mapping relationship table may be stored in a schedule database in the storage module 1012. The schedule database also stores a schedule information table, which contains detailed schedule information corresponding to each target schedule and a first primary 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 email module 1013 can be implemented by system software integrated into the processor. It should be noted that the main client 101, in implementing its functions, is only illustrating the division of the above-described functional modules. The functions can also be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the apparatus and corresponding method embodiments provided in the above embodiments belong to the same concept, and their specific implementation processes are detailed in the corresponding method embodiments, and will not be repeated here.

[0106] like Figure 8 As shown in Table 1 above, the following is a detailed introduction to an example of the calendar tag synchronization method implemented by the various functional modules in the main client 101.

[0107] In response to receiving the primary label "Important-2" set by the user for the target schedule, the calendar module 1011 retrieves the mapping table from the storage module 1012. Then, based on the mapping table, it queries and determines the sub-label "String (Red Category)" corresponding to the primary label "Important-2". Finally, it sends the sub-label "String (Red Category)" associated with the target schedule to the storage module 1012.

[0108] In response to receiving the sub-label "String (Red Category)" associated with the target schedule, the storage module 1012 sends the target schedule and the sub-label "String (Red Category)" associated with the target schedule to the email module 1013.

[0109] The email module 1013 receives the target schedule and the associated sub-tag "String (Red Category)" sent by the storage module 1012, and then sends the target schedule and the associated sub-tag "String (Red Category)" for synchronization to the email server 103, so that the secondary client 102 can synchronize the target schedule and the associated sub-tag "String (Red Category)" from the email server 103. In response to receiving the target schedule and the associated sub-tag "String (Red Category)", the email server 103 sends a schedule update reminder to the secondary client 102, so that the secondary client 102 synchronizes the target schedule and the associated sub-tag "String (Red Category)" from the email server 103 in response to the schedule update reminder.

[0110] In one embodiment, the mapping table is generated by the storage module 1012 based on the mapping relationship between the main label of the main client 101 and the sub-label of the sub-client 102, which is entered by the user through the configuration interface. All sub-labels set on the sub-client 102 are obtained by the calendar module 1011 from the mail server 103 in response to the user's configuration request.

[0111] like Figure 9 As shown below, the process of configuring the mapping relationship table for the main client 101 will be described in detail.

[0112] When a user first logs into their account on the mail server 103 on the main client 101, or when the main client 101 first connects to the mail server 103, they can send a configuration request to the calendar module 1011 to initiate the configuration process for the mapping table. The calendar module 1011 receives the configuration request from the user and, in response, sends a configuration request instruction to the mail module 1013. The mail module 1013, in response to the configuration request instruction, sends a configuration request to the mail server 103. The mail server 103, in response to the configuration request, sends all sub-tags set on the secondary client 102 back to the mail module 1013. The mail module 1013 sends all the received sub-tags set on the secondary client 102 to the storage module 1012. The storage module 1012 writes all the received sub-tags set on the secondary client 102 into the calendar database. Calendar module 1011 retrieves all sub-tags set on sub-client 102 from storage module 1012, and generates and displays a configuration interface based on all primary and secondary tags set on primary client 101. The user inputs the mapping relationship between primary tags on primary client 101 and sub-tags on sub-client 102 through the configuration interface. Calendar module 1011 generates a mapping table based on the mapping relationship input by the user through the configuration interface and sends the mapping table to storage module 1012. Storage module 1012 writes the mapping table into the schedule database.

[0113] The following describes another embodiment of the calendar tag synchronization system 100 of the present invention. The calendar tag 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. The main client 101 uses a first tag system, which includes multiple main tags. The secondary client 102 uses a second tag system, which includes multiple secondary tags. The main client 101 stores a mapping table containing the mapping relationships between the main tags used by the main client 101 and the secondary tags used by the secondary client 102. Understandably, the structure of this calendar tag synchronization system 100 is similar to that of the embodiments described above (e.g., ...). Figure 1 The schedule tag synchronization system 100 shown is the same as that in the system shown, so it will not be described in detail here.

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

[0115] The main client 101 is used to synchronize the target schedule and the first sub-label associated with the target schedule from the mail server 103, and to query and determine the first primary label corresponding to the first sub-label based on the mapping relationship table. 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 configured to send a schedule update reminder to the main client 101 in response to receiving the target schedule and the first sub-tag associated with the target schedule, so that the main client 101 synchronizes the target schedule and the first sub-tag 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 sub-tag set by the user for the target schedule on the secondary client 102 to the primary client 101 via the mail server 103 when the primary client 102 receives the first sub-tag. Then, through the mapping table stored in the primary client 101, the different tag systems on the primary client 101 and the secondary client 102 are associated, realizing the conversion and synchronization of schedule tags under different tag systems. This overcomes the problem of schedule tags not being synchronized between clients due to differences between tag systems, and improves the schedule synchronization between clients and the user experience.

[0118] like Figure 11 As shown in Table 1 above, an example of a schedule tag synchronization method proposed in another embodiment of this application will be described in detail below. This schedule tag synchronization method is applied to the secondary client 102 in the schedule tag synchronization system 100 in the above embodiment. The schedule tag synchronization system 100 will not be described in detail here. The schedule tag synchronization method includes:

[0119] Step 210: Receive the sub-label "String (red category)" set by the user for the target schedule.

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

[0121] Secondary client 102 receives the sub-tag "String (Red Category)" set by the user for the target schedule. It then sends the target schedule and the associated sub-tag "String (Red Category)" to mail server 103 for synchronization, enabling primary client 101 to synchronize the target schedule and the associated sub-tag "String (Red Category)" from mail server 103. Primary client 101, based on the mapping table shown in Table 1 above, queries the mapping table for the primary tag corresponding to the sub-tag "String (Red Category)", thus determining the primary tag to be "Important-2".

[0122] like Figure 12 As shown below, in conjunction with Figure 7 The main client 101 in the illustrated embodiment provides a detailed description of an example of the above-described schedule tag synchronization method. The main client 101 includes a calendar module 1011, a storage module 1012, and an email module 1013. The storage module 1012 is connected to the calendar module 1011, and the email module 1013 is connected to the storage module 1012 and the email server 103. For details, please refer to the detailed description of the main client 101 in the above embodiment, which will not be repeated here.

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

[0124] In response to receiving the target schedule and the associated sub-label "String (red category)", mail server 103 sends a schedule update reminder to mail module 1013 of main client 101.

[0125] In response to the schedule update reminder, the email module 1013 of the main client 101 synchronizes the target schedule and the sub-label "String (Red Category)" associated with the target schedule from the email server 103, and sends the target schedule and the sub-label "String (Red Category)" associated with the target schedule to the storage module 1012.

[0126] The storage module 1012 writes the received target schedule and the associated sub-label "String (red category)" 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 retrieves the mapping table from the storage module 1012, and based on the mapping table, queries and determines the main label "Important-2" corresponding to the sub-label "String (Red Category)".

[0128] This embodiment of the application can directly synchronize the sub-tag "String (Red Category)" set by the user for the target schedule on the secondary client 102 to the primary client 101 via the mail server 103. Then, through the mapping relationship table stored in the primary client 101, the different tag systems on the primary client 101 and the secondary client 102 are associated, realizing the conversion and synchronization of schedule tags under different tag systems. This overcomes the problem of schedule tags not being synchronized between clients due to differences between tag systems, and improves the schedule synchronization between clients and the user experience.

[0129] One embodiment of the present invention also provides an electronic device including a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the schedule tag synchronization method as provided in the above method embodiments.

[0130] Memory is used to store software programs and modules. The processor executes these stored software programs and modules to perform various functional applications and data processing. Memory can primarily consist of a program storage area and a data storage area. The program storage area stores the operating system, application programs required for functionality, etc.; the data storage area stores data created based on device usage, etc. Furthermore, memory can include high-speed random access memory (RAM) and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.

[0131] In one specific embodiment Figure 13 A schematic diagram of the structure of an electronic device for implementing the embodiments of the present invention is shown. The electronic device 1300 can be a computer terminal, a mobile terminal or other devices. The electronic device 1300 can also participate in the formation or include the main client 101 or the sub-client 102 provided in the embodiments of the present invention.

[0132] like Figure 13 As shown, an embodiment of the present invention provides an electronic device 1300, including a processor 1301 and a memory 1302. The memory 1302 stores computer program instructions, wherein when the computer program instructions are executed by the processor, the processor 1301 performs the schedule tag synchronization method as described in the above embodiment.

[0133] Furthermore, such as Figure 13As shown, the electronic device 1300 also 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 via a bus architecture. The bus architecture can include any number of interconnecting buses and bridges. Specifically, various circuits representing one or more central processing units (CPUs) as represented by processor 1301 and one or more memories as represented by 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 is understood that the bus architecture is used to implement 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 therefore will not be described in detail herein.

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

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

[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 intermediate results and other data during the calculation process of the processor 1301.

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

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

[0141] The operating system 13021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 13022 includes various applications, such as a browser, used to implement various application functions. The program implementing the method of this embodiment can be included in the application program 13022.

[0142] When the processor 1301 calls and executes the application program and data stored in the memory 1302, specifically the program or instructions stored in the application program 13022, it executes the schedule tag synchronization method as described in the above embodiments.

[0143] The methods disclosed in the above embodiments of the present invention can be applied to processor 1301, or implemented by processor 1301. Processor 1301 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 1301 or by instructions in the form of software. The processor 1301 may be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 1302. Processor 1301 reads the information in memory 1302 and completes the steps of the above method in conjunction with its hardware.

[0144] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can 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 herein, or combinations thereof.

[0145] For software implementation, the techniques described herein can be achieved through modules (e.g., procedures, functions, etc.) that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented within the processor or externally.

[0146] In addition, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the schedule tag synchronization method as described in the above embodiments.

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

[0148] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.

[0149] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the transmission and reception methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0150] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for synchronizing schedule tags, characterized in that, This applies to the primary client, where both the primary and secondary clients are connected to the same mail server. The main client uses a first tagging system, which includes multiple main tags; the secondary client uses a second tagging system, which includes multiple secondary tags; the tag dimensions of the first tagging system and the second tagging system are different. The main client stores a mapping table, which contains the mapping relationship between the main tags used by the main client and the sub-tags used by the sub-client; the method includes the following steps: Receive the first primary label set by the user for the target schedule, where the first primary label is one of multiple primary labels; Based on the mapping table, the first sub-label corresponding to the first main label is queried and determined, and the first sub-label is one of multiple sub-labels; The target schedule and the first sub-label associated with the target schedule are sent to the mail server for synchronization, so that the sub-client can synchronize the target schedule and the first sub-label associated with the target schedule from the mail server.

2. The schedule tag synchronization method according to claim 1, characterized in that, The mapping relationship between the main tag and the sub-tag includes at least one of the following: one-to-one, one-to-many, many-to-one, and many-to-many mapping relationships.

3. The schedule tag synchronization method according to claim 1, characterized in that, The mapping table is generated based on the mapping relationship between the main label of the main client and the sub-label of the sub-client, which is entered by the user through the configuration interface. All sub-labels set on the secondary client are obtained from the mail server in response to configuration requests input by the user.

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

5. A method for synchronizing schedule tags, characterized in that, This is applied to a secondary client, which connects to the same mail server as the primary client. The main client uses a first tagging system, which includes multiple main tags; the secondary client uses a second tagging system, which includes multiple secondary tags; the tag dimensions of the first tagging system and the second tagging system are different. The main client stores a mapping table, which contains the mapping relationship between the main tags used by the main client and the sub-tags used by the sub-client; the method includes the following steps: Receive the first sub-label set by the user for the target schedule, where the first sub-label is one of multiple sub-labels; The target schedule and the first sub-label associated with the target schedule are sent to the mail server for synchronization, so that the main client can synchronize the target schedule and the first sub-label associated with the target schedule from the mail server, and query and determine the first main label corresponding to the first sub-label based on the mapping table, wherein the first main label is one of a plurality of main labels.

6. A main client, characterized in that, The primary client and the secondary client are connected to the same mail server. The primary client uses a first tagging system, which includes multiple primary tags. The secondary client uses a second tagging system, which includes multiple secondary tags. The tag dimensions of the first tagging system and the second tagging system are different. The main client includes: The storage module is used to store a mapping relationship table, which contains the mapping relationship between the main tag used by the main client and the sub-tag used by the sub-client; A calendar module, connected to the storage module, is configured to receive a first primary tag set by the user for a target schedule, wherein the first primary tag is one of multiple primary tags; retrieve the mapping table from the storage module; based on the mapping table, query and determine a first secondary tag corresponding to the first primary tag, wherein the first secondary tag is one of multiple secondary tags; and send the first secondary tag associated with the target schedule to the storage module; wherein 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 email module; The email module, connected to the storage module and the email server, is configured to receive the target schedule and the first sub-tag associated with the target schedule sent by the storage module; and to send the target schedule and the first sub-tag associated with the target schedule to the email server for synchronization, so that the secondary client can synchronize the target schedule and the first sub-tag associated with the target schedule from the email server.

7. The main client according to claim 6, characterized in that, The mapping table is generated by the storage module based on the mapping relationship between the main label of the main client and the sub-label of the sub-client, which is entered by the user through the configuration interface. The sub-tabs set on the sub-client are obtained by the calendar module from the mail server in response to the user's configuration request.

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

9. A schedule tag synchronization system, characterized in that, include: A primary client, a secondary client, and a mail server connected to the primary client and the secondary client; The main client uses a first tagging system, which includes multiple main tags; the secondary client uses a second tagging system, which includes multiple secondary tags; the tag dimensions of the first tagging system and the second tagging system are different; the main client stores a mapping table, which contains the mapping relationship between the main tags used by the main client and the secondary tags used by the secondary client; The main client is used to receive a first primary tag set by the user for a target schedule, where the first primary tag is one of multiple primary tags; based on the mapping table, it queries and determines a first secondary tag corresponding to the first primary tag, where the first secondary tag is one of multiple secondary tags; and sends the target schedule and the first secondary tag associated with the target schedule to the mail server for synchronization. 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, characterized in that, The mail server is configured to send a schedule update reminder to the secondary client in response to receiving the target schedule and the first sub-tag associated with the target schedule, so that the secondary client, in response to the schedule update reminder, synchronizes the target schedule and the first sub-tag associated with the target schedule from the mail server.

11. A schedule tag synchronization system, characterized in that, include: A primary client, a secondary client, and a mail server connected to the primary client and the secondary client; The main client uses a first tagging system, which includes multiple main tags; the secondary client uses a second tagging system, which includes multiple secondary tags; the tag dimensions of the first tagging system and the second tagging system are different; the main client stores a mapping table, which contains the mapping relationship 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 label set by the user for the target schedule, the first secondary label being one of multiple secondary labels; and to send the target schedule and the first secondary label associated with the target schedule to the mail server for synchronization. The main client is used to synchronize the target schedule and the first sub-label associated with the target schedule from the mail server, and to query and determine the first main label corresponding to the first sub-label based on the mapping table. The first main label is one of multiple main labels.

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

13. An electronic device, characterized in that, include: processor; and a memory, in which computer program instructions are stored. When the computer program instructions are executed by the processor, the processor performs the schedule tag synchronization method as described in any one of claims 1-5.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, cause the processor to perform the schedule tag synchronization method as described in any one of claims 1-5.

Images