Label processing method, device, electronic device and storage medium

Abstract

The embodiments of this specification provide a tag processing method, device, electronic device and storage medium, wherein the method includes: in response to a user's edit request operation for a tag rule of a first tag, displaying an editing page of the tag rule; wherein the first tag is used to represent a grouping of user sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules; obtaining at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session meets some or all of the rule conditions, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag; according to each tag rule, determining and displaying the session group corresponding to the first tag. Through this embodiment, a large number of sessions can be managed, and the efficiency of users finding required sessions can be improved.

Description

Technical Field

[0001] This document relates to the field of instant messaging technology, and in particular to a tag processing method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of collaborative office scenarios, more and more employees in large enterprises are working together through collaborative office software. Most collaborative office software integrates multiple office applications such as instant messaging, cloud documents, audio and video conferencing, etc., which greatly improves the efficiency of collaborative office between employees.

[0003] In the instant messaging scenario of collaborative office, users usually create a large number of sessions to communicate with other users. How to manage a large number of sessions and improve the efficiency of users finding the required sessions has become a problem that urgently needs to be solved. Summary of the invention

[0004] The embodiments of this specification provide a tag processing method, device, electronic device and storage medium, which can manage a large number of conversations and improve the efficiency of users finding required conversations.

[0005] In a first aspect, an embodiment of the present specification provides a label processing method, including:

[0006] In response to a user's edit request operation for a tag rule of a first tag, an edit page of the tag rule is displayed; wherein the first tag is used to represent a grouping of the user's sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules;

[0007] Acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0008] According to the at least one tag rule, a conversation group corresponding to the first tag is determined and displayed.

[0009] In a second aspect, an embodiment of the present specification provides a label processing device, including:

[0010] A display unit, configured to display an editing page of a tag rule in response to a user's editing request operation for a tag rule of a first tag; wherein the first tag is used to represent a grouping of sessions of the user, the tag rule is used to filter the sessions of the user, and different tags correspond to different session groups based on different tag rules;

[0011] an acquisition unit, configured to acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0012] A determining unit is used to determine and display a conversation group corresponding to the first tag according to the at least one tag rule.

[0013] In a third aspect, an embodiment of the present specification provides an electronic device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein the computer-executable instructions, when executed, enable the processor to implement the steps of the method described in the first aspect above.

[0014] In a fourth aspect, an embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store computer-executable instructions, and the computer-executable instructions, when executed by a processor, implement the steps of the method described in the first aspect above.

[0015] In one or more embodiments of the present specification, according to the user's edit request operation on the tag rule of the first tag, the tag rule editing page is displayed, and at least one tag rule of the first tag edited by the user in the editing page is obtained. According to the at least one tag rule, the session group corresponding to the first tag is determined and displayed. Among them, the first tag is used to represent a grouping of the user's session, the tag rule is used to filter the user's session, different tags correspond to different session groups based on different tag rules, and a tag rule of the first tag includes a rule action and at least one rule condition. When the session meets part or all of at least one rule condition, the rule action is executed to filter the user's session to obtain the session corresponding to the first tag. It can be seen that through one or more embodiments of the present specification, the user can realize the grouping of the session by editing the tag rule of the first tag, thereby managing a large number of sessions and improving the efficiency of the user to find the required session. In addition, multiple tag rules can be edited under the first tag, and the precise grouping of the session can be further realized through multiple tag rules, which improves the efficiency of the user to find the required session. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor.

[0017] Figure 1 A flowchart of a label processing method provided in one embodiment of this specification;

[0018] Figure 2a A schematic diagram of an editing page for a tag rule provided in an embodiment of this specification;

[0019] Figure 2b A schematic diagram of an editing page for tag rules provided in another embodiment of the present specification;

[0020] Figure 3 A specific schematic diagram of a labeling rule provided in an embodiment of this specification;

[0021] Figure 4a A schematic diagram of an editing page for triggering display tag rules provided in an embodiment of this specification;

[0022] Figure 4b A schematic diagram of an editing page for triggering display tag rules provided by another embodiment of the present specification;

[0023] Figure 4c A schematic diagram of an editing page for triggering display tag rules provided by another embodiment of the present specification;

[0024] Figure 5a A schematic diagram of multiple label rules provided in an embodiment of this specification;

[0025] Figure 5b A schematic diagram of adjusting the arrangement order of each tag rule in an editing page provided in an embodiment of this specification;

[0026] Figure 6a A schematic diagram showing a session grouping provided in an embodiment of this specification;

[0027] Figure 6b A schematic diagram showing a session grouping provided in another embodiment of the present specification;

[0028] Figure 6c A schematic diagram showing a session grouping provided in another embodiment of the present specification;

[0029] Figure 6d A schematic diagram showing a session grouping provided in yet another embodiment of the present specification;

[0030] Figure 6e A schematic diagram showing a session grouping provided in yet another embodiment of the present specification;

[0031] Figure 7a A schematic diagram of a folding label rule provided in an embodiment of this specification;

[0032] Figure 7b A schematic diagram of an expansion tag rule provided in an embodiment of this specification;

[0033] Figure 8 A schematic diagram of processing a label rule in a folded state provided in an embodiment of this specification;

[0034] Fig. 9 A schematic diagram of prompting a user to fill in a blank field provided in an embodiment of this specification;

[0035] Fig.10a A schematic diagram of creating a first tag provided in an embodiment of this specification;

[0036] Fig.10b A schematic diagram of inputting a tag name provided in an embodiment of this specification;

[0037] Fig.10c A schematic diagram of successful label creation provided in an embodiment of this specification;

[0038] Fig.10d A schematic diagram of successful label modification provided in an embodiment of this specification;

[0039] Fig.11 A schematic diagram of the structure of a label processing device provided in one embodiment of this specification;

[0040] Fig.12 A schematic diagram of the structure of an electronic device provided in one embodiment of this specification. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0042] An embodiment of the present specification provides a tag processing method, which can manage a large number of conversations and improve the efficiency of users finding required conversations.

[0043] Figure 1 A flowchart of a label processing method provided in an embodiment of this specification is shown as follows: Figure 1 As shown, the process includes:

[0044] Step S102, in response to a user's edit request operation for a tag rule of a first tag, displaying an edit page for the tag rule; wherein the first tag is used to represent a grouping of user sessions, the tag rule is used to filter the user sessions, and different tags correspond to different session groups based on different tag rules;

[0045] Step S104, obtaining at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0046] Step S106: Determine and display the conversation group corresponding to the first tag according to at least one tag rule.

[0047] In one or more embodiments of the present specification, according to the user's edit request operation on the tag rule of the first tag, the tag rule editing page is displayed, and at least one tag rule of the first tag edited by the user in the editing page is obtained. According to the at least one tag rule, the session group corresponding to the first tag is determined and displayed. Among them, the first tag is used to represent a grouping of the user's session, the tag rule is used to filter the user's session, different tags correspond to different session groups based on different tag rules, and a tag rule of the first tag includes a rule action and at least one rule condition. When the session meets part or all of at least one rule condition, the rule action is executed to filter the user's session to obtain the session corresponding to the first tag. It can be seen that through one or more embodiments of the present specification, the user can realize the grouping of the session by editing the tag rule of the first tag, thereby managing a large number of sessions and improving the efficiency of the user to find the required session. In addition, multiple tag rules can be edited under the first tag, and the precise grouping of the session can be further realized through multiple tag rules, which improves the efficiency of the user to find the required session.

[0048] The tag processing method in this embodiment can be applied to an instant messaging application, which can be a separate messaging application or an application integrated into collaborative office software, which is not limited here.

[0049] Figure 2a A schematic diagram of an editing page for a tag rule provided in an embodiment of this specification, such as Figure 2aAs shown in the figure, users can edit tag rules in the tag rule editing page, including creating tag rules and modifying existing tag rules. Figure 2a As shown, the tag name of the first tag can be displayed in the tag rule editing page, such as Figure 2a In the "Questions to be Followed Up" section, if the user has not entered the tag name of the first tag in advance, the identification name of the first tag will not be displayed in the editing page of the tag rule.

[0050] refer to Figure 2a For the first tag, a tag rule includes one or more rule conditions and a rule action. Figure 2a , add multiple rule conditions, and when a session satisfies some or all of the rule conditions, such as any one of the rule conditions or all of the rule conditions, execute the rule action corresponding to the rule condition to filter the user's session and obtain the session corresponding to the first tag.

[0051] Figure 2b A schematic diagram of an editing page for a tag rule provided in another embodiment of this specification, combined with Figure 2a and Figure 2b As shown in the figure, in addition to setting multiple rule conditions for a tag rule in the tag rule editing page, users can also Figure 2a , click the "+ Add New Rule" button in the dialog box to add multiple tag rules for the first tag. The structure of each tag rule is the same, and each tag rule may include one or more rule conditions and a rule action. In a tag rule, when a user's session meets some or all of the rule conditions in the tag rule, for example, when any one or all of the rule conditions in the tag rule are met, the rule action in the tag rule is executed to filter the user's session to obtain a session corresponding to the first tag.

[0052] from Figure 2a and Figure 2b It can be seen that in a tag rule, the user can select an option to execute the rule action when the user's session meets all rule conditions, or to execute the rule action when the user's session meets any rule condition. Of course, what is not shown in the figure is that the user can also specify to execute the rule action when the user's session meets two or more rule conditions, and the two or more rule conditions can be any rule conditions or user-specified rule conditions.

[0053] In one embodiment, for the first label, when it has one or more label rules, the name of each label rule is an automatically generated default name, such as starting from 1, and obtaining the names of each label rule such as "label rule 1", "label rule 2", and so on. In addition, it can be set that the user is not allowed to change the name of each label rule. In one embodiment, for the first label, it can have a maximum of 10 label rules, and for each label rule, it can set a maximum of 20 rule conditions.

[0054] In each tag rule of the first tag introduced above, the rule condition includes three parts: data source, operator and keyword. The data source includes at least one of session name, session member and session type. The keyword is set by the user. The operator is used to indicate the matching relationship between the data source and the keyword. The rule action includes moving the session into the session group corresponding to the first tag or moving the session out of the session group corresponding to the first tag.

[0055] Figure 3 A specific schematic diagram of a label rule provided in an embodiment of this specification is as follows: Figure 3 As shown, taking any tag rule of the first tag as an example, in the tag rule, the rule condition includes three parts: data source, operator and keyword. The data source includes at least one of the session name, session member (i.e., group member in the figure), and session type. The user can select one or more data sources by selecting options. Keywords can be set by the user and configured in the keyword box. Figure 3 As shown, the operator matches the data source. When the data source is the session name and group member, the operator is include and does not include. When the data source is the session type, the operator is belongs to and does not belong to. In addition, when the data source is the session type, keywords are provided on the page for users to select. The keywords include single chat, group chat, message do not disturb group, etc. Each keyword represents a session type.

[0056] The operator is used to indicate the matching relationship between the data source and the keyword. Specifically, when the data source is the session name, when the operator is contains, it means that the rule action is executed for the session whose session name contains the keyword set by the user. When the data source is the session name, when the operator is does not contain, it means that the rule action is executed for the session whose session name does not contain the keyword set by the user. The user can set two rule conditions to specify that the session name contains the first specified keyword and does not contain the first specified keyword respectively.

[0057] When the data source is a session member, when the operator is "contains", it means that the rule action is executed on the session that contains the member corresponding to the keyword set by the user. When the data source is a session member, when the operator is "does not contain", it means that the rule action is executed on the session that does not contain the member corresponding to the keyword set by the user. The user can set two rule conditions to specify that the session member contains the first specific member and does not contain the second specific member. Among them, when a chat robot, a self-service chat role, is provided in the instant messaging application, the user can specify whether the member session contains the chat robot or not.

[0058] When the data source is a session type, the operator is "belongs", which means that the rule action is executed on the session whose session type belongs to the type corresponding to the keyword. When the data source is a session type, the operator is "does not belong", which means that the rule action is executed on the session whose session type does not belong to the type corresponding to the keyword.

[0059] like Figure 3 As shown, taking any tag rule of the first tag as an example, in the tag rule, the rule actions include: adding to the current tag, which means moving the session into the session group corresponding to the first tag, and also include: moving out of the current tag, which means moving the session out of the session group corresponding to the first tag.

[0060] It can be seen that in this embodiment, the user can configure rule conditions from multiple dimensions such as session name, session members, session type, etc., and set rule actions that meet the needs, thereby enriching the session screening method and improving the accuracy and efficiency of session screening queries.

[0061] In step S102, in response to the user's edit request operation for the tag rule of the first tag, the tag rule editing page is displayed. The first tag is used to represent a grouping of user sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules.

[0062] In one embodiment, in response to a user's request to edit a tag rule of a first tag, an edit page of the tag rule is displayed, including:

[0063] In response to a user executing an edit request operation on a tag rule on a tag edit page when creating or editing a first tag, displaying an edit page for the tag rule;

[0064] or,

[0065] In response to a user's request to edit a tag rule on a first tag group displayed in the information flow area, an editing page for the tag rule is displayed.

[0066] Figure 4aA schematic diagram of an editing page for triggering display tag rules provided in an embodiment of this specification, such as Figure 4a As shown, the user can trigger the "add tag rule" control in the tag editing page for creating or editing the first tag to perform an edit request operation on the tag rule. In response to the edit request operation, the following may be displayed: Figure 2a The edit page for a tag rule is shown.

[0067] Figure 4b A schematic diagram of an editing page for triggering display tag rules provided in another embodiment of the present specification is as follows: Figure 4b As shown, the user can perform an edit request operation on the tag rule for the first tag group displayed in the information flow area by triggering the "add tag rule" control. In response to the edit request operation, the following may be displayed: Figure 2a The edit page for a tag rule is shown.

[0068] Figure 4c A schematic diagram of an editing page for triggering display tag rules provided in another embodiment of the present specification is as follows: Figure 4c As shown, the user can execute an edit request operation on the tag rules for the first tag group displayed in the information flow area by triggering the "Modify tag rules" control. In response to the edit request operation, the tag rule editing page can be displayed. Since the tag rules are modified here, the displayed tag rule editing page contains pre-edited tag rules.

[0069] It can be seen that through this embodiment, the user can trigger the entry into the tag rule editing page from different entrances, which enriches the user's operation mode and improves the user's experience in editing tag rules.

[0070] According to the above introduction, for the first tag, it can have multiple tag rules, each of which has a rule action and at least one rule condition. In a tag rule, when a session meets all or any one of the rule conditions, the rule action is executed to filter the session. Therefore, when there are multiple tag rules, each tag rule has its own rule action execution result. Based on this, in one embodiment, in the above step S106, when there are multiple tag rules edited by the user, according to at least one tag rule, the session group corresponding to the first tag is determined and displayed, including:

[0071] According to the arrangement order of each tag rule in the editing page, and according to the rule conditions in each tag rule, the rule actions in each tag rule are executed in turn, so as to move the user's session into the session group corresponding to the first tag or move the user's session out of the session group corresponding to the first tag;

[0072] After the rule action in the last tag rule is executed, the conversation group corresponding to the first tag is obtained and displayed.

[0073] Figure 5a A schematic diagram of multiple label rules provided in an embodiment of this specification, such as Figure 5a As shown, when the first tag has multiple tag rules, each tag rule is executed in turn according to the order in which each tag rule is arranged from top to bottom in the editing page. When any tag rule is executed, the rule action in the tag rule is executed according to the rule condition in the tag rule to move the user's session into the session group corresponding to the first tag or to move the user's session out of the session group corresponding to the first tag. After the last tag rule is executed according to the order in which it is arranged from top to bottom, the session group corresponding to the first tag is obtained, and the session group is displayed in the editing page, as shown in FIG. Figure 5a "Based on the current tag rules, the following conversations will be added to the tag."

[0074] In one embodiment, a user moves some sessions into a session group corresponding to a first tag through a partial tag rule, and then the user adds a tag rule, and the rule action of the added tag rule is to move the session out of the session group corresponding to the first tag. Then, through the added tag rule, some sessions can be filtered out of the session group corresponding to the first tag in the previously moved-in sessions.

[0075] It can be seen that, through this embodiment, the rule actions in each tag rule can be executed in sequence according to the arrangement order of each tag rule in the editing page, so as to obtain the conversation group corresponding to the first tag.

[0076] In one embodiment, executing rule actions in each tag rule to move the user's session into a session group corresponding to the first tag or to move the user's session out of the session group corresponding to the first tag includes:

[0077] If it is determined that there is a first session of the user that hits multiple rule actions, the first session is moved into the session group corresponding to the first tag or out of the session group corresponding to the first tag according to the last rule action hit by the first session in the arrangement order.

[0078] Specifically, in the process of executing each tag rule in sequence according to the arrangement order of each tag rule from top to bottom in the editing page, if there is a first session that hits rule actions in multiple tag rules, the rule action of the last tag rule hit by the first session is determined according to the arrangement order of each tag rule from top to bottom in the editing page, and according to the rule action, it is determined to move the first session into the session group corresponding to the first tag or to move the first session out of the session group corresponding to the first tag.

[0079] For example, there is a first session A that hits two rule actions, namely moving into the session group corresponding to the first tag or moving out of the session group corresponding to the first tag. Since the order of arrangement from top to bottom in the editing page for each tag rule is determined, and the rule action last hit by the first session A is moving out of the session group corresponding to the first tag, it is determined that the first session A is moved out of the session group corresponding to the first tag.

[0080] It can be seen that through this embodiment, when the first session hits multiple rule actions, the rule action hit last by the first session can be determined according to the arrangement order of each tag rule in the editing page, so as to determine whether to move the first session into the session group corresponding to the first tag or to move the first session out of the session group corresponding to the first tag, thereby solving the problem of conflicting rule actions hit by the first session.

[0081] Considering that the rule actions in the various tag rules can be executed in sequence according to the arrangement order of the various tag rules in the editing page to move the user's session into the session group corresponding to the first tag or move the user's session out of the session group corresponding to the first tag, in one embodiment, in step S106, after determining and displaying the session group corresponding to the first tag according to at least one tag rule, the method further includes:

[0082] In response to the user's adjustment operation on the arrangement order of each tag rule in the editing page, the arrangement order is adjusted, and each tag rule after the order adjustment is displayed;

[0083] According to the label rules after the order adjustment, the conversation group corresponding to the first label is re-determined and displayed.

[0084] Figure 5b A schematic diagram of adjusting the arrangement order of each tag rule in an editing page provided in an embodiment of this specification, such as Figure 5b As shown, the user can adjust the arrangement order of each tag rule in the editing page by dragging the tag rule. After the user adjusts the arrangement order of each tag rule in the editing page, the editing page displays the tag rules after the order adjustment, and based on the tag rules after the order adjustment, the conversation group corresponding to the first tag is re-determined and displayed.

[0085] It can be seen that through this embodiment, the user can also adjust the arrangement order of each tag rule in the editing page, thereby adjusting the execution order of each rule action to achieve re-screening of the session.

[0086] In the process of determining the conversation group corresponding to the first tag according to each tag rule of the first tag, before the result is determined, text information can be displayed on the tag rule editing page to indicate that all qualifying conversations are being searched for the user.

[0087] Figure 6a A schematic diagram showing a session grouping provided in an embodiment of this specification, such as Figure 6a As shown, after determining the conversation group corresponding to the first tag according to each tag rule of the first tag, if there is a rule action in each tag rule that is to move the conversation into the conversation group corresponding to the first tag (including the case where the rule action in each tag rule only contains a move-in action and the case where it contains both a move-in action and a move-out action), then text information can be displayed on the editing page of the tag rule to indicate that according to the current tag rule, the following conversation is moved into the conversation group corresponding to the tag.

[0088] Figure 6b A schematic diagram showing a session grouping provided in another embodiment of the present specification is shown in FIG. Figure 6b As shown, after determining to obtain the session group corresponding to the first tag according to each tag rule of the first tag, if there is a rule action in each tag rule to move the session into the session group corresponding to the first tag (including the case where the rule action in each tag rule contains only a move-in action and the case where it contains both a move-in action and a move-out action), but it is determined that the number of sessions that can be moved into is 0, then text information can be displayed on the editing page of the tag rule to indicate that there are currently no sessions that meet the rules.

[0089] Figure 6c A schematic diagram showing a session grouping provided in another embodiment of the present specification is shown in FIG. Figure 6c As shown, after determining to obtain a session group corresponding to the first tag according to each tag rule of the first tag, if there is a rule action in each tag rule to move the session into the session group corresponding to the first tag (including the case where the rule action in each tag rule contains only a move-in action and the case where it contains both a move-in action and a move-out action), but it is determined that the number of sessions that can be moved in exceeds a preset value, then text information can be displayed on the editing page of the tag rule to indicate that there are too many sessions that meet the rule, and only a part of the most recently generated sessions are moved into the session group corresponding to the tag.

[0090] Figure 6d A schematic diagram showing a session grouping provided in another embodiment of the present specification is shown in FIG. Figure 6dAs shown, after determining the session group corresponding to the first tag according to the various tag rules of the first tag, if all rule actions in the various tag rules are to move the session out of the session group corresponding to the first tag, then after determining the session that can be moved out, text information can be displayed on the editing page of the tag rule to indicate that according to the current tag rule, the following session will be moved out of the session group corresponding to the tag.

[0091] Figure 6e A schematic diagram showing a session grouping provided in another embodiment of the present specification is shown in FIG. Figure 6e As shown, after determining the session grouping corresponding to the first tag according to the tag rules of the first tag, if all rule actions in the tag rules are to move the session out of the session grouping corresponding to the first tag, but it is determined that the number of sessions that can be moved out is 0, then text information can be displayed on the editing page of the tag rule to indicate that there are currently no sessions that meet the rules.

[0092] It can be seen that, through this embodiment, different text information can be displayed according to different situations to inform the user which conversations are about to be moved into or out of the conversation group corresponding to the first label.

[0093] Considering that there may be a situation where the user manually moves the conversation into the conversation group corresponding to the first label, in one embodiment, in step S106, after determining and displaying the conversation group corresponding to the first label according to at least one label rule, the method further includes:

[0094] In response to a user's operation of moving a second session into a session group corresponding to a first tag, determining whether the second session satisfies a specific tag rule of the first tag; the specific tag rule is used to move the session out of the session group corresponding to the first tag;

[0095] If the conditions are met, a first prompt message is displayed, where the first prompt message is used to indicate that the second conversation cannot be moved into the conversation group corresponding to the first tag.

[0096] Specifically, after determining the conversation group corresponding to the first label, if the user manually moves the second conversation into the conversation group corresponding to the first label, then in response to the user's move-in operation, it is determined whether the second conversation satisfies the specific label rule of the first label, and the specific label rule is used to move the conversation out of the conversation group corresponding to the first label. If so, it indicates that the second conversation should be moved out of the conversation group corresponding to the first label, and a first prompt message is displayed, and the first prompt message is used to indicate that the second conversation cannot be moved into the conversation group corresponding to the first label.

[0097] If not, check whether the second session is located in the session group corresponding to the first label. If it is, display a second prompt message to indicate that the second session is already in the session group corresponding to the first label. If not, move the second session into the session group corresponding to the first label.

[0098] It can be seen that through this embodiment, when the user manually moves a session into the session group corresponding to the first label, it can be determined whether the session satisfies the session removal logic of the first label. If so, the user is informed that the session cannot be moved into the session group corresponding to the first label, thereby avoiding the user from moving a non-compliant session into the session group corresponding to the first label when forgetting the label rule.

[0099] Furthermore, in one embodiment, after obtaining at least one tag rule of the first tag edited by the user in the editing page, it is also possible to:

[0100] In response to a user's folding operation on any one of at least one tag rule, the tag rule is folded and thumbnail information of the folded tag rule is displayed; the thumbnail information of the tag rule includes each rule condition in the thumbnail display state of the tag rule and the rule action in the thumbnail display state of the tag rule.

[0101] Figure 7a A schematic diagram of a folding label rule provided in an embodiment of this specification, such as Figure 7a As shown in the figure, by clicking the folding control on the editing page, you can fold any tag rule. The folded tag rule is displayed in the form of thumbnail information. The thumbnail information of the tag rule includes the rule conditions and rule actions in the thumbnail display state. The rule conditions in the thumbnail display state are Figure 7a The rule action in the thumbnail display state is Figure 7a "Action: Add to current tab" in the Figure 7a As shown, the abbreviated information of the tag rule also includes the name of the tag rule, such as Figure 7a It should be noted that the folding control changes in form as the user clicks, and the folding control has different forms when the label rule is in the abbreviated state and when the label rule is in the expanded state.

[0102] When a tag rule includes multiple rule conditions, in the rule conditions in the thumbnail display state, each rule condition can be connected by "and" or "or". The "and" connection method means that the rule action is executed when all rule conditions are met, and the "or" connection method means that the rule action is executed when any one of the rule conditions is met. For example, the rule condition in the thumbnail display state is "Condition: Group name includes XXX or group members include YYY".

[0103] In one embodiment, when a user adds a subsequent tag rule on the edit page, the previous tag rule is automatically folded and the abbreviated information of the tag rule is displayed. For example, when a user adds a second tag rule on the edit page, the first tag rule is automatically folded and the abbreviated information of the tag rule is displayed.

[0104] Figure 7b A schematic diagram of an expansion tag rule provided in an embodiment of this specification, such as Figure 7b As shown, by clicking the collapse control on the editing page, the collapsed label rules can be expanded and displayed. The expanded label rules are in an editable state, and the collapsed label rules are in a non-editable state.

[0105] It can be seen that, through this embodiment, the folding and unfolding of tag rules can also be realized, thereby improving the user experience of editing tag rules and facilitating the user to preview each tag rule in a folded state.

[0106] Based on the folding label rule, in an implementation example, after the folding label rule, you can also:

[0107] Displaying operation controls associated with the collapsed label rule, the operation controls including an edit control and a delete control;

[0108] In response to the user's triggering operation on the operation control, the folded label rules are processed accordingly.

[0109] Figure 8 A schematic diagram of processing a label rule in a folded state provided in an embodiment of this specification, such as Figure 8 As shown, after the label rule is folded, the associated operation controls are displayed near the folded label rule, and the operation controls include an edit control and a delete control. If the user clicks the edit control, the folded label rule is expanded on the editing page of the label rule, and the user is allowed to edit the expanded label rule. The expanded label rule is in an editable state. If the user clicks the delete control, the label rule is deleted with or without user confirmation. The label rule can be expanded or not before deletion.

[0110] Figure 8In the example, the folded tag rules are displayed on the tag editing page when creating or editing the first tag. The folded tag rules are the abbreviated tag rules. In other embodiments, the folded tag rules can also be displayed on the tag rule editing page, which is not limited in this embodiment. When the folded tag rules are displayed on the tag editing page, they can be displayed as follows: Figure 8 As shown in the figure, there are edit controls and delete controls. When the collapsed tag rule is displayed on the tag rule editing page, you can also Figure 8 The display shown has edit controls and delete controls.

[0111] It can be seen that, through this embodiment, an operation control associated with the folded label rule can also be provided, so that the user can process the folded label rule through the operation control.

[0112] Based on the folding label rule, in an implementation example, after the folding label rule, you can also:

[0113] In response to a tag rule saving operation by a user, checking whether there is a blank field in a rule action or a rule condition of the collapsed tag rule;

[0114] If it exists, the collapsed label rule is unfolded and the third prompt information is displayed, and the third prompt information is used to prompt the user to fill in the blank field;

[0115] If it does not exist, each label rule edited by the user is saved, each label rule edited by the user is changed to a folded state, and the abbreviated information of each folded label rule is displayed.

[0116] exist Figure 7a On the basis of, when some tag rules are folded and other tag rules are not folded, if the user clicks the Save button in the editing page to save the tag rules, it will automatically check whether there are blank fields in the rule actions or rule conditions of the folded tag rules. The blank fields include but are not limited to the data source, operator and keyword in the rule conditions, and the content of the rule action. If there are blank fields, the folded tag rules will be automatically expanded and the third prompt information will be displayed to prompt the user to fill in the blank fields. If there are no blank fields, the tag rules edited by the user will be saved, and the tag rules edited by the user will be changed to the folded state, and the abbreviated information of the folded tag rules will be displayed.

[0117] Fig. 9 A schematic diagram of prompting a user to fill in a blank field provided in an embodiment of this specification, such as Fig. 9 As shown, if there is a blank field in the rule action or rule condition of the collapsed tag rule after the user executes the tag rule save operation, the collapsed tag rule is automatically expanded and the third prompt information is displayed, such as Fig. 9 "Please enter keywords" in the form to prompt the user to fill in the blank fields. It can be understood that if there are also blank fields in the tag rule in the expanded state edited by the user, the third prompt information is also displayed to prompt the user to fill in the blank fields.

[0118] In the case that there are no blank fields in the collapsed label rules and the expanded label rules, in response to the user's label rule saving operation, the label rules edited by the user are saved, and the page jumps to Figure 8 The label editing interface, such as Figure 8 As shown, each label rule edited by the user is changed to a folded state, and the abbreviated information and associated operation controls of each folded label rule are displayed, so that the user can preview each label rule in a abbreviated state.

[0119] exist Figure 8 In , if the user clicks the edit control associated with a tag rule, they can jump back to the tag rule editing page for editing. Figure 8 As shown in the figure, if the user confirms that the label rules in the thumbnail state are correct, he can click Figure 8 In one embodiment, when a user creates a tag for the first time, the user's tag rule saving operation, such as clicking Figure 7a The Save button in the operation is used to save the tag rules locally. Figure 8 After clicking the Create button in the Create First Tag dialog box, the tag rules are uploaded to the server to store the tag rules. After the first tag is successfully stored, the tag rules are determined to be created. Before the first tag is successfully created, the tag rules are not effective. When the user modifies an existing tag, the user's tag rule saving operation, such as clicking Figure 7a The operation of the Save button in is used to save the label rule to the server. The server determines that the label modification is successful based on the save operation.

[0120] It can be seen that, through this embodiment, it is also possible to check the blank fields of the folded label rules when saving the label rules, so as to avoid saving invalid label rules.

[0121] Fig.10a A schematic diagram of creating a first tag provided in an embodiment of this specification is as follows: Fig.10a As shown, after the user edits the tag rule and executes the tag rule saving operation, the tag creation page will be displayed and the user will be prompted to enter the tag name of the first tag. Fig.10b A schematic diagram of inputting a tag name provided in an embodiment of this specification, such as Fig.10b As shown, the user can enter the tag name in the tag creation page and click the Create button. Fig.10cThis is a schematic diagram of successful label creation provided in an embodiment of this specification, such as Fig.10c As shown, after the user enters the tag name and clicks the create button, a text may be displayed to prompt the user that the first tag is created successfully. Fig.10d This is a schematic diagram of successful label modification provided in an embodiment of this specification, such as Fig.10d As shown, if the user modifies a pre-existing label rule, the modified label rule can be saved after the modification is completed. In response to the user's saving operation, the user can be prompted that the first label modification is successful.

[0122] In a specific embodiment, when a user first creates a first tag, the user can Figure 4a The interface shown triggers an edit request for the tag rule and jumps to Figure 2a and Figure 2b Create a label rule in the interface shown. After the creation is completed, click Figure 2a or Figure 2b to save the label rule and jump to Fig.10a The page for creating the first label is shown. In this page, add the name of the first label and click the Create button to create the first label.

[0123] In another specific embodiment, when a first label is available but the label rule needs to be modified, the label rule can be modified as follows: Figure 4c The edit request operation for the tag rule is triggered in the interface and jumps to Figure 7a and Figure 7b Modify the label rules in the interface shown. After the modification is completed, click Figure 7a or Figure 7b to save the label rule and jump to Fig.10b , click the Create button to modify the first label, or, Figure 7a or Figure 7b After you save the label rules by clicking the Save button in Fig.10b The interface directly displays the text to prompt the user that the first tag has been modified successfully.

[0124] In summary, through the above method flow, the user can group the conversations by editing the tag rules of the first tag, thereby managing a large number of conversations and improving the efficiency of users finding the desired conversations. In addition, multiple tag rules can be edited under the first tag, and multiple tag rules can further achieve accurate grouping of conversations, thereby improving the efficiency of users finding the desired conversations.

[0125] Fig.11 A schematic diagram of the structure of a label processing device provided in an embodiment of this specification is shown in FIG. Fig.11 As shown, the device comprises:

[0126] A display unit 11 is used to display an editing page of a tag rule in response to a user's editing request operation for a tag rule of a first tag; wherein the first tag is used to represent a grouping of the user's sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules;

[0127] an acquisition unit 12, configured to acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0128] The determining unit 13 is configured to determine and display a conversation group corresponding to the first tag according to the at least one tag rule.

[0129] Optionally, the display unit 11 is specifically used for:

[0130] In response to a user executing an edit request operation on a tag rule on a tag edit page when creating or editing a first tag, displaying an edit page for the tag rule;

[0131] or,

[0132] In response to a user's request to edit a tag rule on a first tag group displayed in an information flow area, an editing page for the tag rule is displayed.

[0133] Optionally, the rule condition includes a data source, an operator and a keyword; the data source includes at least one of a session name, a session member, and a session type; the keyword is set by the user; the operator is used to represent a matching relationship between the data source and the keyword; the rule action includes moving the session into a session group corresponding to the first tag or moving the session out of the session group corresponding to the first tag.

[0134] Optionally, the determining unit 13 is specifically configured to:

[0135] When there are multiple tag rules edited by the user, the rule actions in each tag rule are executed in sequence according to the arrangement order of each tag rule in the editing page and the rule conditions in each tag rule, so as to move the user's session into the session group corresponding to the first tag or move the user's session out of the session group corresponding to the first tag;

[0136] After the rule action in the last tag rule is executed, a conversation group corresponding to the first tag is obtained and displayed.

[0137] Optionally, the determining unit 13 is further specifically configured to:

[0138] If it is determined that there is a first session of the user that hits multiple rule actions, the first session is moved into the session group corresponding to the first tag or out of the session group corresponding to the first tag according to the last rule action hit by the first session in the arrangement order.

[0139] Optionally, an adjustment unit is further included, configured to:

[0140] After determining and displaying the conversation group corresponding to the first tag according to the at least one tag rule, in response to the user's adjustment operation on the arrangement order of each tag rule in the editing page, adjusting the arrangement order and displaying each tag rule after the order adjustment;

[0141] According to the label rules after the order adjustment, the conversation group corresponding to the first label is re-determined and displayed.

[0142] Optionally, a prompting unit is further included, for:

[0143] After determining and displaying the conversation group corresponding to the first tag according to the at least one tag rule, in response to the user's operation of moving a second conversation into the conversation group corresponding to the first tag, determining whether the second conversation satisfies a specific tag rule of the first tag; the specific tag rule is used to move the conversation out of the conversation group corresponding to the first tag;

[0144] If the conditions are met, a first prompt message is displayed, where the first prompt message is used to indicate that the second conversation cannot be moved into the conversation group corresponding to the first tag.

[0145] Optionally, a folding unit is further included, for:

[0146] After obtaining at least one tag rule of the first tag edited by the user in the editing page, in response to the user's folding operation on any one of the at least one tag rule, the tag rule is folded and thumbnail information of the folded tag rule is displayed; the thumbnail information of the tag rule includes each rule condition in the thumbnail display state of the tag rule and the rule action in the thumbnail display state of the tag rule.

[0147] Optionally, the method further comprises a processing unit, configured to:

[0148] After folding the label rule, displaying operation controls associated with the folded label rule, the operation controls including an edit control and a delete control;

[0149] In response to the user's triggering operation on the operation control, the folded label is processed accordingly.

[0150] Optionally, a storage unit is further included, configured to:

[0151] After folding the label rule, in response to the user's label rule saving operation, checking whether there is a blank field in the rule action or the rule condition of the folded label rule;

[0152] If so, unfold the folded label rule and display third prompt information, where the third prompt information is used to prompt the user to fill in the blank field;

[0153] If not, each of the label rules edited by the user is saved, each of the label rules edited by the user is changed to a folded state, and the abbreviated information of each of the folded label rules is displayed.

[0154] The label processing device in the embodiment of this specification can implement each process of the above-mentioned label processing method embodiment and achieve the same effect and function, which will not be repeated here.

[0155] An embodiment of the present specification also provides an electronic device, Fig.12 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification, such as Fig.12 As shown, the electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and one or more applications or data may be stored in the memory 802. Among them, the memory 802 may be a temporary storage or a permanent storage. The application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the electronic device. Furthermore, the processor 801 can be configured to communicate with the memory 802 to execute a series of computer executable instructions in the memory 802 on the electronic device. The electronic device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input or output interfaces 805, one or more keyboards 806, etc.

[0156] In a specific embodiment, the electronic device is a label processing device, comprising a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor implements the following process:

[0157] In response to a user's edit request operation for a tag rule of a first tag, an edit page of the tag rule is displayed; wherein the first tag is used to represent a grouping of the user's sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules;

[0158] Acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0159] According to the at least one tag rule, a conversation group corresponding to the first tag is determined and displayed.

[0160] The label processing device in the embodiment of this specification can implement each process of the above-mentioned label processing method embodiment and achieve the same effect and function, which will not be repeated here.

[0161] Another embodiment of the present specification further provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, the following process is implemented:

[0162] In response to a user's edit request operation for a tag rule of a first tag, an edit page of the tag rule is displayed; wherein the first tag is used to represent a grouping of the user's sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules;

[0163] Acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag;

[0164] According to the at least one tag rule, a conversation group corresponding to the first tag is determined and displayed.

[0165] The storage medium in the embodiments of this specification can implement each process of the above-mentioned label processing method embodiment and achieve the same effect and function, which will not be repeated here.

[0166] In various embodiments of this specification, the computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0167] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0168] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0169] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0170] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0171] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0172] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0173] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0174] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0175] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0176] One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0177] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0178] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A label processing method, characterized in that: include: In response to a user's edit request operation for a tag rule of a first tag, an edit page of the tag rule is displayed; wherein the first tag is used to represent a grouping of the user's sessions, the tag rule is used to filter the user's sessions, and different tags correspond to different session groups based on different tag rules; Acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag; Determine and display a conversation group corresponding to the first tag according to the at least one tag rule; The user edits a plurality of tag rules, and determining and displaying a conversation group corresponding to the first tag according to the at least one tag rule, includes: According to the arrangement order of each tag rule in the editing page, and in accordance with the rule conditions in each tag rule, execute the rule actions in each tag rule; After the rule action in the last tag rule is executed, text information is displayed, where the text information is used to indicate that the user's session is moved into or out of the session group corresponding to the first tag.

2. The method according to claim 1, characterized in that: The step of displaying an editing page for the tag rule in response to a user's editing request for the tag rule of the first tag includes: In response to a user's editing request operation for a tag rule on a tag editing page when creating or editing a first tag, displaying an editing page for the tag rule; or, In response to a user's request to edit a tag rule on a first tag group displayed in an information flow area, an editing page for the tag rule is displayed.

3. The method according to claim 1, characterized in that The rule conditions include a data source, an operator and a keyword; the data source includes at least one of a session name, a session member, and a session type; the keyword is set by the user; the operator is used to represent a matching relationship between the data source and the keyword; the rule action includes moving the session into a session group corresponding to a first tag or moving the session out of a session group corresponding to the first tag.

4. The method according to claim 1, characterized in that: The executing the rule action in each of the tag rules includes: If it is determined that there is a first session of the user that hits multiple rule actions, the first session is moved into the session group corresponding to the first tag or out of the session group corresponding to the first tag according to the last rule action hit by the first session in the arrangement order.

5. The method according to claim 1, characterized in that After determining and displaying the conversation group corresponding to the first tag according to the at least one tag rule, the method further includes: In response to the user's operation of adjusting the arrangement order of each tag rule in the editing page, the arrangement order is adjusted, and each tag rule after the order adjustment is displayed; According to the label rules after the order adjustment, the conversation group corresponding to the first label is re-determined and displayed.

6. The method according to claim 1, characterized in that After determining and displaying the conversation group corresponding to the first tag according to the at least one tag rule, the method further includes: In response to the user's operation of moving a second session into the session group corresponding to the first tag, determining whether the second session satisfies a specific tag rule of the first tag; the specific tag rule is used to move the session out of the session group corresponding to the first tag; If the conditions are met, a first prompt message is displayed, where the first prompt message is used to indicate that the second conversation cannot be moved into the conversation group corresponding to the first tag.

7. The method according to claim 1, characterized in that After acquiring at least one tag rule of the first tag edited by the user in the editing page, the method further includes: In response to the user's folding operation on any one of the at least one label rule, the label rule is folded and thumbnail information of the folded label rule is displayed; the thumbnail information of the label rule includes each of the rule conditions in the thumbnail display state of the label rule and the rule action in the thumbnail display state of the label rule.

8. The method according to claim 7, characterized in that After folding the label rule, the method further includes: Displaying operation controls associated with the collapsed label rule, wherein the operation controls include an edit control and a delete control; In response to the user's triggering operation on the operation control, the folded label is processed accordingly.

9. The method according to claim 7, characterized in that: After folding the label rule, the method further includes: In response to the user's tag rule saving operation, checking whether there is a blank field in the rule action or the rule condition of the folded tag rule; If so, unfold the folded label rule and display third prompt information, where the third prompt information is used to prompt the user to fill in the blank field; If not, each of the label rules edited by the user is saved, each of the label rules edited by the user is changed to a folded state, and the abbreviated information of each of the folded label rules is displayed.

10. A label processing device, characterized in that: include: A display unit, configured to display an editing page of a tag rule in response to a user's editing request operation for a tag rule of a first tag; wherein the first tag is used to represent a grouping of sessions of the user, the tag rule is used to filter the sessions of the user, and different tags correspond to different session groups based on different tag rules; an acquisition unit, configured to acquire at least one tag rule of the first tag edited by the user in the editing page; wherein a tag rule includes a rule action and at least one rule condition, and when a session satisfies part or all of the at least one rule condition, the rule action is executed to filter the user's session to obtain a session corresponding to the first tag; a determining unit, configured to determine and display a conversation group corresponding to the first tag according to the at least one tag rule; There are multiple tag rules edited by the user, and the determination unit is specifically used to: execute the rule actions in each tag rule according to the rule conditions in the tag rules in the order in which the tag rules are arranged in the editing page; after the rule action in the last tag rule is executed, display text information, where the text information is used to indicate that the user's session is moved into or out of the session group corresponding to the first tag.

11. An electronic device, characterized in that: include: processor; as well as, A memory configured to store computer executable instructions, which, when executed, cause the processor to implement the steps of the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store computer-executable instructions, and the computer-executable instructions, when executed by a processor, implement the steps of the method described in any one of claims 1 to 9.

Images