Information processing, information interaction, label check, information display method and device

Abstract

The present disclosure provides a method and device for information processing, information interaction, label checking, and information display, in which a usage authority can be set in advance for a first label, and the usage authority of the first label can indicate whether a first user has the authority to use the first label. In response to a label adding operation triggered by a first user, a first device can obtain a first label indicated by the label adding operation and obtain the usage authority of the first label. After obtaining the first label and the usage authority of the first label, the first device can display usage authority information for indicating the usage authority of the first label and / or the first label. Thus, in an embodiment of the present application, the first label has usage authority, and the first user cannot add the first label according to his / her subjective will, and whether the first user can use the first label is determined by the usage authority of the first label. Therefore, the present solution is advantageous for information integration.

Description

[Technical Field]

[0001] This disclosure was filed on February 26, 2021 with the State Intellectual Property Office of the People's Republic of China, with application number 202110217494.9, entitled "Information Processing Method and Apparatus," and on February 26, 2021 with the State Intellectual Property Office of the People's Republic of China, with application number 202110217727.5, entitled "Information Interaction Method, Label Checking Method and Apparatus," and on February 26, 2021 with the State Intellectual Property Office of the People's Republic of China, with application number 202110217727.5, entitled "Information Interaction Method, Label Checking Method and Apparatus." This application claims priority to four Chinese patent applications filed with the State Intellectual Property Office on March 25, 2021, bearing application number 202110218477.7 and entitled "Information processing method and apparatus," all of which are incorporated by reference into this application.

[0002] The present invention belongs to the field of data processing technology, and specifically relates to an information processing method, an information interaction method, a label checking method, and an information display method and device. [Background technology]

[0003] For a certain project, the development of the project may need to be completed collaboratively by multiple organizations (e.g., multiple departments or multiple teams). During the development of the project, members participating in the project may generate some information related to the project, such as tasks, schedules, messages, documents, and chat groups. These pieces of information may belong to different information domains, for example, tasks, schedules, messages, documents, and chat groups belong to different information domains. Summary of the Invention [Problem to be solved by the invention]

[0004] Currently, how to integrate and manage information related to the project is an unsolved problem.

[0005] In order to solve the above technical problems or at least part of them, the embodiments of the present application provide an information processing method, an information interaction method, a label checking method, an information display method and an apparatus for realizing the integration and management of different information and performing collaborative work. [Means for solving the problem]

[0006] According to a first aspect, an embodiment of the present application provides an information processing method, the method comprising: In response to a label addition operation triggered by a first user, obtaining a first label indicated by the label addition operation; obtaining usage rights for the first label, the usage rights being used to indicate whether the first user has usage rights for the first label; and displaying the first label and / or usage rights information to indicate usage rights of the first label.

[0007] According to a second aspect, an embodiment of the present application provides an information processing device, the device comprising: a first acquiring unit for acquiring, in response to a label adding operation triggered by a first user, a first label indicated by the label adding operation; a second acquisition unit for acquiring usage rights for the first label, the usage rights being used to indicate whether the first user has usage rights for the first label; and a first display unit for displaying the first label and / or usage rights information for indicating usage rights of the first label.

[0008] According to a third aspect, an embodiment of the present application provides an apparatus, the apparatus including a processor and a memory; The processor executes instructions stored in the memory to cause the device to perform the method of any one of the first aspects above.

[0009] According to a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, the instructions directing a device to perform a method according to any one of the first aspects above.

[0010] According to a fifth aspect, an embodiment of the present application provides a computer program product, which when run on a computer causes the computer to perform the method according to any one of the first aspects above.

[0011] An embodiment of the present application provides an information processing method, which is executed by a first device. Specifically, for a first label, usage rights can be pre-set for the first label, and the usage rights for the first label can indicate whether a first user has the authority to use the first label. Using the first label means adding the first label to information. When the first user needs to add a label, the first user can trigger a label addition operation. After the first user triggers the label addition operation, the first device can obtain the first label and usage rights for the first label indicated by the label addition operation in response to the label addition operation triggered by the first user. After obtaining the first label and the usage rights for the first label, the first device can display usage rights information indicating the usage rights for the first label and / or the first label. Thus, in an embodiment of the present application, the first label has a usage authority, and the first user cannot add the first label simply according to his or her own subjective will. Whether the first user can use the first label is determined by the first user's usage authority for the first label. In one example, users within a certain team (e.g., a team for research and development project A) can be permitted to use the first label, while users outside the team are not permitted to use the first label. In this way, users outside the team can be prevented from adding the first label to information, which facilitates the integration of information for project A based on the first label. Therefore, this solution is advantageous for information integration.

[0012] In an embodiment of the present application, a user can add a label to a target object. Correspondingly, according to the label addition operation triggered by the user on the target object, the user can determine the label he or she wants to add to the target object, and further obtain the correspondence between the target label and the target object. In this way, when a user wants to check an object corresponding to a certain label, the object corresponding to the label (including the target object) can be searched and displayed based on the correspondence. In this way, according to the label addition operation, a label can be added to the target object, thereby distinguishing the target object from other objects, allowing the user to quickly find the required object and more flexibly manage the objects.

[0013] According to a sixth aspect, an embodiment of the present application provides a method of information interaction, comprising: accepting a label addition operation triggered by a user on a target object; generating a correspondence according to the label adding operation, the correspondence including a correspondence between a target label and the target object; Includes.

[0014] According to a seventh aspect, an embodiment of the present application provides a label checking method, comprising: accepting a label check operation triggered by a user on the label check control; displaying at least one label according to the label checking operation; Includes.

[0015] According to an eighth aspect, an embodiment of the present application provides an information interaction device, a receiving module for receiving a label adding operation triggered by a user on a target object; a generating module for generating a correspondence according to the label adding operation, the correspondence including a correspondence between a target label and the target object; Includes:

[0016] According to a ninth aspect, an embodiment of the present application provides a label checking device, a receiving module that accepts a label check operation triggered by a user on a label check control; a display module for displaying at least one label according to the label checking operation; Includes:

[0017] According to a tenth aspect, an embodiment of the present application provides an electronic device, the electronic device comprising: one or more processors; a memory for storing one or more programs; Including, When executed by the one or more processors, the one or more programs cause the one or more processors to implement the information interaction method or label checking method described in any one of the embodiments of the present application.

[0018] According to an eleventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, realizes a method of information interaction as described in any one of the embodiments of the present application, or a method of information interaction or a label checking method as described in any one of the embodiments of the present application.

[0019] In an embodiment of the present application, a user can add a label to a target object. Correspondingly, the user can determine the label they want to add to the target object according to the label addition operation triggered by the user for the target object, and further obtain the correspondence between the target label and the target object. In this way, when the user wants to check the object corresponding to a certain label, the object corresponding to the label (including the target object) can be searched and displayed based on the correspondence. In this way, a label can be added to the target object according to the label addition operation, thereby distinguishing the target object from other objects, allowing the user to quickly find the required object and more flexibly manage the objects.

[0020] According to a twelfth aspect, an embodiment of the present application provides an information processing method, the method comprising: determining a first user's authority to a first label and a check authority of the first user to first information, the first information comprising the first label; and determining display content for the first user based on the first user's authority for the first label and the first user's check authority for the first information.

[0021] According to a thirteenth aspect, an embodiment of the present application provides an information processing method, the method comprising: obtaining a check authority for a first label of a first user in response to a check operation triggered by the first user for the first label, the check authority being used to indicate whether the first user has the authority to check information related to the first label; and if it is determined that the first user has the authority to check the first label, displaying information related to the first label.

[0022] According to a fourteenth aspect, an embodiment of the present application provides an information processing device, the device comprising: a first determination unit for determining a first user's authority to a first label and a check authority of the first user to a first information, the first information comprising the first label; and a second determination unit for determining display content for the first user based on the first user's authority for the first label and the first user's check authority for the first information.

[0023] According to a fifteenth aspect, an embodiment of the present application provides an information processing device, the device comprising: an acquiring unit for acquiring a check authority of a first user for the first label in response to a check operation triggered by the first user for the first label, the check authority being used to indicate whether the first user has the authority to check related information of the first label; and a first display unit for displaying information related to the first label when it is determined that the first user has the authority to check the first label.

[0024] According to a sixteenth aspect, an embodiment of the present application provides an apparatus, the apparatus including a processor and a memory; The processor executes instructions stored in the memory to cause the device to perform the method of any one of the twelfth aspect above or the thirteenth aspect above.

[0025] According to a seventeenth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, the instructions instructing a device to perform a method according to any one of the twelfth aspect above or the thirteenth aspect above.

[0026] According to an eighteenth aspect, an embodiment of the present application provides a computer program product, which when run on a computer causes the computer to perform a method according to any one of the twelfth aspect above or at least one of the thirteenth aspect.

[0027] An embodiment of the present application further provides an information processing method, and in one example, the method is performed by a first device. For first information having a first label, the first device first determines a first user's authority for the first label and the first user's check authority for the first information, and then determines display content for the first user based on the first user's authority for the first label and the first user's check authority for the first information. Thus, according to this solution, the first user's authority for the first label and the first user's check authority for the first information can be combined to determine display content for the first user, and further manage information related to a project.

[0028] An embodiment of the present application further provides an information processing method. In one example, the method can be executed by a first device. A first user can trigger a check operation on a first label. After the first user triggers the check operation on the first label, the first device can obtain the first user's check authority for the first label in response to the check operation triggered by the first user on the first label. The first user's check authority for the first label is used to indicate whether the first user has the authority to check information related to the first label. If the first user has the authority to check the first label, the device displays information related to the first label. In one example, the first label may be a label corresponding to a project, and the information related to the first label may be information related to the project. According to this solution, a first user with the authority to check the first label can check the information related to the first label, thereby checking information related to the project and realizing management of information related to the project.

[0029] According to a nineteenth aspect, an embodiment of the present application provides an information processing method, the method comprising: accepting a new label creation operation triggered by a first user; displaying a label creation page, the label creation page including a label attribute component, the label attribute component being used to indicate authority scope attributes that a newly created label will have; and receiving a label name input by the first user and a selection operation on the label attribute component to generate a first label.

[0030] According to a twentieth aspect, an embodiment of the present application provides an information display method, the method comprising: accepting a label check operation triggered by a third user; and displaying the information block and the label in association with each other based on the authority range attribute of the label and the third user's access authority to the information block having the label.

[0031] According to a twenty-first aspect, an embodiment of the present application provides an electronic device, the electronic device comprising: one or more processors; a memory for storing one or more programs; When the one or more programs are executed by the one or more processors, they cause the one or more processors to realize an information interaction method described in any one of the 19th aspects or an information display method described in any one of the 20th aspects.

[0032] According to a 22nd aspect, an embodiment of the present application provides a computer-readable storage medium having instructions stored therein, which, when executed by a device, cause the device to perform the information processing method described in the 19th aspect or the information display method described in the 20th aspect.

[0033] According to a 23rd aspect, an embodiment of the present application provides a computer program product, which, when executed on an apparatus, causes the apparatus to perform the information processing method described in the 19th aspect or the information display method described in the 20th aspect.

[0034] An embodiment of the present application further provides an information processing method in which, when a first user creates a label, the first user determines an authority range attribute of the newly created label according to needs. For example, if the authority range attribute is a first attribute value, the newly created label is a public label, and if the authority range attribute is a second attribute value, the newly created label is a private label. Public labels can be searched, viewed, or edited by all members of the organization, while private labels can only be viewed or edited by collaborators, who are determined by the first user. That is, if the authority range attribute of the newly created label by the first user is a second attribute value, the first user can specify several members to view or edit the newly created label, thereby realizing private label sharing, which meets the needs of users in different scenarios and improves the user experience.

[0035] An embodiment of the present application further provides an information display method, in which when a third user wants to check an information block corresponding to a label, a client associates and displays the label with the information block based on an authority range attribute corresponding to the label and the third user's access authority to the information block. The authority range attribute may be a first attribute value or a second attribute value, where the first attribute value indicates that the label is a public label and the second attribute value indicates that the label is a private label. That is, the client can display different information based on the authority range attribute corresponding to the label and the third user's access authority to the information block, thereby reflecting the authority range attribute of the label and whether the third user has access authority to the information block in different displays. [Brief explanation of the drawings]

[0036] The drawings are used to provide a further understanding of the invention, constitute a part of the specification, and together with the examples of this application, interpret the invention and do not constitute a limitation of the invention. [Figure 1]1 is a flow diagram of an information processing method provided by an embodiment of the present application; [Figure 2a] FIG. 1 is a schematic diagram of an add label page provided by an embodiment of the present application. [Figure 2b] 1 is a schematic diagram of a label placement interface provided by an embodiment of the present application; [Figure 2c] 1 is a schematic diagram of a relevant page of a first label provided by an embodiment of the present application. [Figure 2d] 1 is a schematic diagram of a page provided by an embodiment of the present application. [Figure 2e] FIG. 2 is a schematic diagram of a label authorization setting interface provided by an embodiment of the present application; [Figure 3] 1 is a structural schematic diagram of an information processing device provided by an embodiment of the present application; [Figure 4] 1 is a flow diagram of a method for information interaction provided by an embodiment of the present application; [Figure 5a] 1 is a schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 5b] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 5c] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 6a] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 6b] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 7] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 8] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 9] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 10]FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 11] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 12] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 13] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 14] 1 is a flow diagram of a label checking method provided by an embodiment of the present application. [Figure 15a] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 15b] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 16] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 17] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 18] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 19] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 20] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 21a] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 21b] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 22a] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 22b]FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 23] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 24] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 25] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 26] FIG. 2 is another schematic diagram of a display interface of a client provided by an embodiment of the present application; [Figure 27] 1 is a structural schematic diagram of an information interactive device provided by an embodiment of the present application; [Figure 28] 1 is a structural schematic diagram of a label checking device provided by an embodiment of the present application; [Figure 29] 1 is a flow diagram of an information processing method provided by an embodiment of the present application; [Figure 30] FIG. 1 is a schematic diagram of an add label page provided by an embodiment of the present application. [Figure 31] 1 is a flow diagram of an information processing method provided by an embodiment of the present application; [Figure 32a] 1 is a schematic diagram of a relevant page of a first label provided by an embodiment of the present application. [Figure 32b] 1 is a schematic diagram of a page provided by an embodiment of the present application. [Figure 32c] FIG. 1 is a schematic diagram of an add label page provided by an embodiment of the present application. [Figure 32d] FIG. 2 is a schematic diagram of a label authorization setting interface provided by an embodiment of the present application; [Figure 32e] 1 is a schematic diagram of a label placement interface provided by an embodiment of the present application; [Figure 33] 1 is a structural schematic diagram of an information processing device provided by an embodiment of the present application; [Figure 34] 1 is a structural schematic diagram of an information processing device provided by an embodiment of the present application; [Figure 35]1 is a flowchart of an information processing method provided by an embodiment of the present application; [Figure 36a] FIG. 2 is a schematic diagram of a label creation page provided by an embodiment of the present application. [Figure 36b] FIG. 10 is a schematic diagram of another label creation page provided by an embodiment of the present application. [Figure 36c] FIG. 10 is a schematic diagram of a collaborator addition page provided by an embodiment of the present application. [Figure 36d] FIG. 10 is a schematic diagram of another add collaborator page provided by an embodiment of the present application. [Figure 37a] FIG. 1 is a schematic diagram of a label page display provided by an embodiment of the present application. [Figure 37b] FIG. 2 is a schematic diagram of a label correction page provided by an embodiment of the present application. [Figure 38] 1 is a flowchart of an information display method provided by an embodiment of the present application; [Figure 39a] FIG. 1 is a schematic diagram of a group display provided by an embodiment of the present application. [Figure 39b] FIG. 2 is a schematic diagram of a message display provided by an embodiment of the present application. [Figure 39c] FIG. 10 is a schematic diagram of another message display provided by an embodiment of the present application. [Figure 39d] FIG. 1 is a schematic diagram of a cloud document display provided by an embodiment of the present application. [Figure 39e] FIG. 2 is a schematic diagram of cloud document permission setting provided by an embodiment of the present application; [Figure 39f] FIG. 10 is a schematic diagram of another cloud document permission setting provided by an embodiment of the present application. [Figure 40] 1 is a structural schematic diagram of an information processing device provided by an embodiment of the present application; [Figure 41] 1 is a structural schematic diagram of an information display device provided by an embodiment of the present application; [Figure 42] 1 is a structural diagram of an electronic device provided by an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0037] In order to allow those skilled in the art to better understand the solutions of the present application, the following clearly and completely describes the technical solutions of the embodiments of the present application in combination with the drawings of the embodiments of the present application, and obviously, the described embodiments are not all embodiments but only some embodiments of the present application. Based on the embodiments of the present application, on the premise that those skilled in the art do not make efforts that amount to inventive steps, all other embodiments obtained fall within the protection scope of the present application.

[0038] It should be understood that the steps described in the method embodiments of the present application may be performed in different orders and / or in parallel, and that the method embodiments may include additional steps and / or omit performing steps that are shown, and the scope of the present application is not limited in this respect.

[0039] As used herein, the term "including" and variations thereof are open inclusions, i.e., meaning "including, but not limited to." The term "based on" means "based at least in part on." The term "in one embodiment" refers to "at least one embodiment," the term "in another embodiment" refers to "at least one other embodiment," and the term "in some embodiments" refers to "at least some embodiments." Relevant definitions of other terms are provided below.

[0040] It should be noted that the concepts of "first", "second", etc. mentioned in this application are merely intended to distinguish between different devices, modules or units, and do not limit the order or interdependence of the functions performed by these devices, modules or units.

[0041] Herein, the modifications "one" and "multiple" referred to in this application are general rather than limiting, and as will be understood by those skilled in the art, unless otherwise expressly indicated in the specification, they are to be understood as "one or more."

[0042] The inventors of the present application have discovered that in some scenarios, the development of a certain project may be completed jointly by multiple organizations (e.g., multiple departments or multiple teams). During the development of the project, members participating in the project may generate several pieces of information related to the project, such as tasks, schedules, messages, documents, and chat groups. These pieces of information may belong to different information domains. For example, tasks, schedules, messages, documents, and chat groups belong to different information domains. By integrating related information of the project, users (e.g., project managers, project participants) can determine information related to the project by labeling the information related to the project and then use the labels to integrate the information related to the project.

[0043] Currently, when users label information, there are no particular restrictions on the labels they can use. That is, for a given label, such as "Project A Research and Development," any user can use that label to label the content they want to mark. However, this is disadvantageous when integrating information about the projects mentioned above. For example, if Team A and Team B jointly research and develop Project A, Team A and Team B can label related information using the label "Project A Research and Development," and other users can also label related information using the label "Project A Research and Development." Therefore, when integrating information using the label "Project A Research and Development," other content marked by other users will also be integrated.

[0044] Therefore, the current label usage method is not favorable for information integration.

[0045] Various non-limiting embodiments of the present application will be described in detail below in conjunction with the drawings.

[0046] Exemplary Methods Referring to Figure 1, this figure is a schematic flow diagram of an information processing method provided by an embodiment of the present application. The method provided by the embodiment of the present application is executed by a first device, and the first device may be a client or a service terminal, which is not specifically limited in the embodiment of the present application.

[0047] In an embodiment of the present application, a target application program is installed on the first device, and the first user referred to in the embodiment of the present application is a user corresponding to an account that logs in to the target application program on the first device.

[0048] Unless otherwise stated, information referred to in the embodiments of the present application, such as first information, second information, third information or target information, may be one or more of a task, a schedule, a message, a document, a chat group, etc. In some scenarios, the terms "information unit" and "information" can be used interchangeably.

[0049] In the embodiments and drawings of the present application, "#" is a label identifier. Of course, the label identifier is not limited to "#" and may be other symbols.

[0050] All drawings in the embodiments of the present application, such as Figures 2a to 2e, do not limit the embodiments of the present application and are provided only to facilitate understanding of the contents of the embodiments of the present application. The pages shown in Figures 2a to 2e may include other contents, which are not specifically limited in the embodiments of the present application.

[0051] In this embodiment, the method may include, for example, the following steps S101 to S103. S101: In response to a label adding operation triggered by a first user, obtain a first label indicated by the label adding operation.

[0052] In an embodiment of the present application, a target application program is installed on the first device, and the target application program has a label adding function. In one example, a first user may trigger a label adding operation for certain information, or may trigger a label adding operation on a label management homepage. After the first user triggers the label adding operation, the first device can obtain a first label indicated by the label adding operation. In one example, after the first user triggers the label adding operation, the first device displays a label adding page. The label adding page includes a character input area, and the first user can input corresponding characters into the character input area. Correspondingly, after obtaining the characters input by the first user, the first device provides the first user with corresponding label candidates based on the characters input by the first user and displays the label candidates on the label adding page, so that the user can select a label to be added based on the label candidates. The first label may be a label candidate determined by the first device based on the characters input by the first user.

[0053] The characters referred to herein may include one or more of Chinese characters, English characters, Korean characters, numbers, etc., to which the embodiments of the present application are not specifically limited.

[0054] S102: Obtain a usage right for the first label, where the usage right indicates whether the first user has a usage right for the first label.

[0055] S103: Display the first label and / or usage rights information for indicating usage rights of the first label.

[0056] Considering that the traditional label usage method is disadvantageous to information integration, in an embodiment of the present application, for a first label, a usage authority can be pre-set for the first label, and the usage authority of the first label can indicate whether a first user has the authority to use the first label. Using the first label can be adding the first label, for example, creating the first label or adding the first label to information.

[0057] In view of this, after determining a first label, the first device may obtain usage rights for the first label and display the first label and the usage rights for the first label on the label addition page. In other words, usage rights information for indicating the first label and / or the usage rights for the first label is displayed on the label addition page.

[0058] In one example, if the first user does not have permission to use the first label, the first label and the permission information may be displayed to prompt the first user that the first user does not have permission to use the first label. If the first user has permission to use the first label, only the first label may be displayed. In other words, if the permission to use the first label is not displayed on the label addition page, the first user has permission to use the first label by default.

[0059] Thus, in an embodiment of the present application, a first user cannot add a first label according to his or her own subjective will, and whether the first user can use the first label is determined by the usage authority of the first label. In one example, users within a certain team (e.g., a team for research and development project A) are permitted to use the first label, while users outside the team are not permitted to use the first label. This prevents users outside the team from adding the first label to information, which is advantageous for integrating information for project A based on the first label. Therefore, this solution is advantageous for information integration.

[0060] The above steps S101 to S103 can be understood in conjunction with Fig. 2a, which is a schematic diagram of a label addition page provided in an embodiment of the present application. As shown in Fig. 2a, after a first user inputs the character "#Q" on the label addition page, label candidates such as "All-Day Test", "Light Service", and "Confirm" appear in Fig. 2a. For the label candidate "Light Service", it is further displayed that the first user does not have the authority to use the label "Light Service".

[0061] In one example, if a first user does not have the usage rights for the first label, the usage rights information is further used to instruct the first user to request the usage rights for the first label from the owner of the first label. The first user can request the usage rights for the first label from the owner of the first label by triggering a corresponding operation. For example, the first user can request the usage rights for the first label from the owner of the first label by clicking the usage rights information. After the owner of the first label agrees to the first user's request, the first user can use the first label.

[0062] The owner of the first label referred to herein may be the creator of the first label. For example, for a certain project, if a person in charge of the project creates the first label, the owner of the first label may be the person in charge of the project.

[0063] Furthermore, given that project personnel may change, it is not advisable for the previous personnel to assume the role of owner of the first label after the change. Therefore, in an embodiment of the present application, the owner status of the first label can be transferred. The historical owner of the first label performs an owner status transfer operation to transfer the owner of the first label to another user. In one example, the historical owner performs the label transfer operation in the first label installation interface to designate a user as the owner of the first label. Please refer to FIG. 2b, which is a schematic diagram of a label installation interface provided in an embodiment of the present application. As shown in FIG. 2b, the historical owner of the first label "QA," e.g., user A, clicks "Transfer" in FIG. 2b to trigger the owner status transfer operation and designate a user as the new owner.

[0064] In one example, a first label may have only one owner. If the first label has undergone multiple ownership transitions, the owner of the first label may be the user designated by the last ownership transition operation.

[0065] In another example, if a first user has permission to use the first label, the first user can trigger a label addition operation on the first label to add the first label. If the label addition page is a page displayed after the first user triggers a label addition operation on target information, the first device can add the first label to the target information after the first user triggers the label addition operation on the first label. If the label addition page is a page displayed after the first user triggers a label addition operation on a label management homepage, the first device can create the first label after the first user triggers the label addition operation on the first label. Triggering the label addition operation on the first label mentioned herein may be, for example, clicking the first label in label candidates.

[0066] In some embodiments, in addition to including a use right for a first label, the first label may further include a check right. The check right for a first label is used to indicate whether the first user has the right to check information related to the first label. In one example, the priority of the use right for the first label is higher than the priority of the check right for the first label. If the first user has the use right for the first label, the first user also has the check right for the first label.

[0067] In one example, the first user can trigger a check operation on the first label. If the first device determines in response to the check operation triggered by the first user on the first label that the first user has the check authority for the first label, the first device can display information related to the first label. Here, if the usage authority information in S103 indicates that the first user has the use authority for the first label, the first user necessarily has the check authority for the first label. In this case, after the first user triggers the check operation on the first label, the first device can display information related to the first label in response to the check operation triggered by the first user on the first label. If the usage authority information in S103 indicates that the first user does not have the use authority for the first label, the first user may or may not have the check authority for the first label. In this case, after the first user triggers a check operation on the first label, the first device can further determine whether the first user has the check authority for the first label in response to the check operation triggered by the first user on the first label, and display information related to the first label if it determines that the first user has the check authority for the first label.

[0068] In one example, the first user triggers a check operation for the first label on a page including label sharing information, where the label indicated by the label sharing information is the first label. As one example, the page including the label sharing information may be an instant messaging session interface, and the label sharing information may be information shared by a user in the instant messaging session interface to the instant messaging session interface. In another example, the first user searches for the first label in a label management interface, and after the first label is searched, the first user can further trigger a check operation for the first label.

[0069] After a first user triggers a check operation on the first label, the first device can obtain the first user's check authority for the first label in response to the check operation triggered by the first user on the first label, and determine display content for the first user based on the first user's check authority for the first label.

[0070] In one example, if the first user has the authority to check the first label, information related to the first label can be displayed to the first user.

[0071] In one implementation, the related information of the first label may be displayed on a related page of the first label. Thus, one implementation of "displaying a related page of the first label" is to display a related page of the label.

[0072] The related page may include, for example, summary information of an information unit that has the first label and that the first user has the authority to check. For example, if the first user has the authority to check a second piece of information and the second piece of information has a first label, the related page of the first label may include summary information of the information unit of the second piece of information. Correspondingly, if the first user does not have the authority to check a first piece of information, in one example, the related page of the first label may not include summary information of the first piece of information. In an embodiment of the present application, the summary information of an information unit may be some information in the information unit, such as some keywords in the information unit.

[0073] In an embodiment of the present application, information summaries of information units having the first label are categorized and displayed on the page associated with the first label according to the message domain from which each information unit originates. The information units having the first label include a first information unit. The message domain from which the first information unit originates is used to indicate the origin of the first information unit. In one example, the message domain from which the first information unit originates is used to indicate the service provider corresponding to the first information unit. The service provider referred to here may be, for example, an instant messaging session service provider, a file service provider, etc.

[0074] It can be understood by referring to Figure 2c, which is a schematic diagram of the related page of the first label provided by an embodiment of the present application, that the information summaries of the information units having the first label are categorized and displayed on the related page of the first label according to the message domain from which each information unit originates.

[0075] As shown in FIG. 2c, the related page includes five message domains: "Tasks," "Schedule," "Messages," "Documents," and "Chat Groups." In the related page shown in FIG. 2c, the message domain "Tasks" is selected, and the page displays information summaries corresponding to three tasks: "Project Seminar," "Complete R&D Task 1," and "Complete R&D Task 2." While the content corresponding to the message domain "Tasks" shown in FIG. 2c is displayed in a list format, FIG. 2c does not limit the scope of the present application and is shown for ease of understanding only. In one example, the content included in the related page of the first label may be displayed in a canvas format. A user may switch the display format of the content included in the related page, for example, using the controls labeled "List" and "Canvas" shown in FIG. 2c.

[0076] In one example, when the content included in the related page is displayed in the form of a canvas, the related page includes one or more label canvases, and each canvas is used to display summary information corresponding to one piece of information. For example, summary information corresponding to a second piece of information is displayed. Furthermore, when the content included in the related page is displayed in the form of a canvas, the first user may group the content included in the related page on the related page. Correspondingly, the first device may group the content included in the related page in response to a grouping operation triggered by the user. Specifically, the first user triggers a grouping operation, determines the content to be added to the group, and inputs a group name. The first device generates a correspondence between the group name and the content to be added to the group and displays the correspondence on the related page in the form of a canvas.

[0077] For example, if the first user divides task X and task Y in the message domain "Task" into one group on the related page, the first user sets the label group name of the group as "First Group", and the first device accordingly records the correspondence between the first group and task X and the correspondence between the first group and task Y, and reflects the correspondence between the first group and task X and the correspondence between the first group and task Y on the related page in the form of a canvas.

[0078] In one example, a first user classifies a plurality of pieces of information having a certain characteristic into one group, so that even if there is a large amount of information on the relevant page that has the first label, the first user can quickly find the desired information based on the set group.

[0079] In one example, after a first user groups the content included in the related page, other users who have the authority to check the first label can also check the group displayed in canvas format. Taking the above "first group" as an example, a second user who has the authority to check the first label can check the "first group" displayed in canvas format. Specifically, for information belonging to the "first group," if the second user has the authority to check the information, the second user can check, for example, summary information of the information displayed in canvas format. In other words, the canvas corresponding to the "first group" included in the related page displayed on the client corresponding to the second user includes summary information of the information. If the second user does not have the authority to check the information, the second user cannot check the summary information of the information displayed in canvas format. In other words, the canvas corresponding to the "first group" included in the related page displayed on the client corresponding to the second user does not include summary information of the information. Of course, if the second user does not have the authority to check the information, the canvas corresponding to the "first group" included in the related page displayed on the client corresponding to the second user may display summary information and / or prompt information for the information. The prompt information is used to prompt the second user to request the owner of the information for the authority to check the information. Example 1: The "first group" includes task X and task Y. If the second user has the authority to check task X but does not have the authority to check task Y, the related page displayed on the client corresponding to the second user includes a canvas corresponding to the "first group," and the canvas displays summary information for task X but does not display summary information for task Y.

[0080] Example 2: When the "first group" includes task X and task Y, and the second user has the authority to check task X but does not have the authority to check task Y, the related page displayed on the client of the second user includes a canvas corresponding to the "first group," which displays summary information of task X, summary information of task Y, and prompt information. The prompt information is used to prompt the second user to request the owner of task Y to check task Y.

[0081] In one example, a first user may check the second information by triggering a predetermined operation on the summary information of the second information displayed on the related page. The predetermined operation triggered by the first user on the summary information of the second information may be, for example, a click operation. In one example, when the first user triggers a predetermined operation on the summary information of the second information, the first device may display the second information in response to the predetermined operation triggered by the first user on the summary information of the second information. For example, the second information may be displayed by loading a separate page on the related page, or the second information may be displayed in a certain area on the related page, such as a sidebar. In another example, when the first user triggers a predetermined operation on the summary information of the second information, the first device may jump to a page including the second information in response to the predetermined operation triggered by the first user on the summary information of the second information. For example, if the second information is an instant messaging message, the first user can trigger a predetermined operation on the information summary of the second information and then jump to an instant messaging session interface where the instant messaging message is located. Also, for example, if the second information is a group, the first user can trigger a predetermined operation on the information summary of the second information and then jump to an instant messaging session interface corresponding to the group.

[0082] In another example, in addition to including summary information of the second information in the related page of the first label, summary information of third information having less stringent confidentiality requirements may also be included in the related page of the first label, even if the first user does not have access permissions to the third information. The related page referred to here is a page displayed on a client to which the first user has logged in.

[0083] In this case, the first user can request the owner of the third information to check the third information by triggering a predetermined operation on the information summary of the third information. In one example, after checking the summary of the third information, if the first user wants to further check the specific content of the third information, the first user can request the owner of the third information to check the third information by triggering a predetermined operation on the information summary of the third information (e.g., clicking on the information summary of the third information). If the owner of the third information agrees to the request, the first user can further check the third information. The owner of the third information referred to here may be, for example, the publisher or creator of the third information.

[0084] In one example, after a first user triggers a check operation on a first label, the first device may display first prompt information if it determines that the first user does not have the authority to check the first label. The first prompt information indicates that the first user does not have the authority to check the information related to the first label. In another example, the first prompt information, in addition to indicating that the first user does not have the authority to check the information related to the first label, is used to instruct the first user to request the owner of the first label for the authority to check the first label. In this case, the first user may trigger a predetermined operation on the first prompt information if they wish to check the information related to the first label. After the first user triggers a predetermined operation on the first prompt information, for example, after the first user clicks on the first prompt information, the first device may request the owner of the first label for the authority to check the first label in response to the predetermined operation triggered by the first user on the first prompt information. If the owner of the first label agrees to the request, the first user can check the related information of the first label, for example, the first device can display the related page of the first label.

[0085] 2d, which is a schematic diagram of a page provided by an embodiment of the present application. In FIG. 2d, if the first user does not have the check authority for the first label "QA", after the first user triggers a check operation for the first label, the first device may display a first prompt information saying "You do not have the check authority, click here to request the authority".

[0086] In an embodiment of the present application, the use authority and the check authority of the first label may be set by the owner of the first label. In one example, the owner of the first label can achieve the authority setting for the first label by triggering an authority setting operation on the authority setting interface of the first label. After the owner of the first label triggers the authority setting operation on the authority setting interface of the first label, the first device acquires the use authority of the first label and / or the check authority of the first label set by the owner of the first label in response to the authority setting operation. After acquiring the use authority of the first label and / or the check authority of the first label set by the owner of the first label, the first device can generate the authority setting information of the first label.

[0087] Here, the authority setting information of the first label includes the check authority of the first label and the use authority of the first label. In one example, the priority of the use authority of the first label is higher than the priority of the check authority of the first label. When the first user has the use authority of the first label, he or she also has the check authority of the first label.

[0088] Please refer to FIG. 2e, which is a schematic diagram of a label authorization setting interface provided in an embodiment of the present application. The owner of a first label "QA" uses three authorization setting options 201, 202, and 203 provided by FIG. 2e to set authorization for the first label. As described above, the priority of the use authorization is higher than the priority of the check authorization. Therefore, if the owner of the first label uses option 201 to set authorization for the first label, all members in the organization will have the use authorization for the first label and the check authorization for the first label. If the owner of the first label uses option 202 or 203 to set authorization for the first label, the owner of the first label can further set the designated users.

[0089] As the inventors of the present application have discovered, how to integrate and manage information related to a project is currently an unsolved problem. For a certain project, by integrating related information of the project, users (e.g., project managers, project participants) can determine information related to the project by labeling the information related to the project and integrating the information related to the project by the label.

[0090] To prevent project information from being leaked during the project development stage, permissions are set for project-related labels, and only users with label permissions can perform corresponding operations on the labels.

[0091] Currently, label authority is tightly coupled with the authority of the information bearing that label, but this approach does not meet practical needs. For example, if information 1 is assigned label 1 and user 1 has label authority for label 1, user 1 also has the corresponding authority to view information 1. However, this approach does not effectively protect information security. This is because, although multiple organizations participate in the development of the same project, the priorities of the different organizations may differ. Accordingly, information with high confidentiality requirements can, in principle, only be viewed by members of the organization that created the information. Also, for example, if information 1 is assigned label 1 and user 1 does not have label authority for label 1, user 1 cannot view information 1. However, if the authority settings for label 1 are strict and information 1 itself does not have special confidentiality needs, this approach is unfavorable for information sharing.

[0092] In view of this, in one implementation form of the embodiment of the present application, the first device can further perform the following steps A and B.

[0093] Step A: Determine a first user's authority to a first label and a check authority of the first user to first information, where the first information comprises the first label.

[0094] In the embodiment of the present application, the authority for the first user's first label and the check authority for the first user's first information may be stored in a client local corresponding to the first user, or may be stored in a service terminal of a target application program. The first device may obtain the authority for the first user's first label and the check authority for the first user's first information from a client local corresponding to the first user, or may obtain the authority for the first user's first label and the check authority for the first user's first information from a service terminal, which is not specifically limited in the embodiment of the present application. The target application program is installed in the client corresponding to the first user referred to herein.

[0095] Step B: Determine display content for the first user based on the authority of the first user to the first label and the check authority of the first user to the first information.

[0096] In the embodiment of the present application, for a first label, the first label itself has authority, and for information having the first label, such as first information, the first information also has corresponding check authority. The check authority of the first information and the authority of the first label are independent of each other, and the check authority of the first information mentioned here is used to indicate whether the first user has the check authority of the first information.

[0097] In an embodiment of the present application, content to be displayed to a first user is determined taking into consideration not only the first user's authority to check the first information but also the first user's authority to the first label. This avoids problems of information security and disadvantages to information sharing that may arise from determining content to be displayed to a first user based only on the first user's authority to the first label. The content to be displayed to a first user referred to herein may be displayed on a client corresponding to the first user. The client corresponding to the first user referred to herein is a client that logs in to an account corresponding to the first user.

[0098] In one example, the authority of the first user for the first label includes a check authority for the first user for the first label. The check authority for the first user for the first label is used to indicate whether the first user has the authority to check the related information of the first label. The related information of the first label referred to here may be information having an association relationship with the first label, for example, information that includes the first label.

[0099] In one example, the related information of the first label may be displayed on the related page of the first label. In this case, the first user's check authority for the first label is used to indicate whether the first user has the check authority for the related page of the first label. In this case, if the first user has the check authority for the first label, they can check the related page of the first label. If the first user does not have the check authority for the first label, they cannot check the related page of the first label.

[0100] In one example, for first information having a first label, if the first user has the authority to check the first label but does not have the authority to check the first information, it is determined that the first page displayed to the first user does not include the first information. The first page referred to here may be a related page of the first label or another page, such as an instant messaging session interface. In other words, if the first user has the authority to check the first label but does not have the authority to check the first information, the content displayed to the first user does not include the first information. For example, if the first page is a related page of the first label, the related page does not include the first information. This method can effectively protect the information security of the first information.

[0101] In one example, the first page may be, for example, an instant messaging session interface, and in this case, the first information may be a file posted by another user in the instant messaging session indicated by the instant messaging session interface. Here, the first user may be a user included in the instant messaging session indicated by the instant messaging session interface. In this case, if the first user does not have the corresponding permission to check a file posted by another user in the instant messaging session indicated by the instant messaging session interface, the first information is not included in the instant messaging session interface displayed on the client corresponding to the first user. For example, if the first user and the second user are both users in the instant messaging session interface, and the second user posts a document, but the first user does not have the permission to check the document, the document is not included in the instant messaging session interface displayed on the client corresponding to the first user. In one scenario, the instant messaging session indicated by the instant messaging session interface may include only the first user and the second user, or may include other users, although the embodiments of the present application are not specifically limited thereto.

[0102] In one example, when the first user has the authority to check a first label, a related page of the first label can be displayed to the first user, and the related page may include, for example, summary information of an information unit that has the first label and for which the first user has the authority to check. For example, when the first user has the authority to check a second piece of information and the second piece of information has a first label, the related page of the first label includes summary information of the information unit of the second piece of information. Correspondingly, when the first user does not have the authority to check a first piece of information, in one example, the related page of the first label does not include summary information of the first piece of information. In an embodiment of the present application, the summary information of an information unit is some information in the information unit, for example, some keywords in the information unit.

[0103] In another example, a first user has the authority to use a first label, and the first information is information in an instant messaging session. The first user does not necessarily have the authority to check the first information unless he or she is a user in the instant messaging session. However, if the first user subsequently joins an instant messaging session that includes the first information, he or she will have the authority to check the first information. In this case, the first information in the instant messaging session that has the first label is displayed in association with the first user. Displaying the first information that has the first label in association with the first information displays the association relationship between the first information and the first label while displaying the first information. The first user can determine that the first information has the first label based on the first information that has the first label and is displayed in association with the first information.

[0104] As described above, a first user's check authority for a first label is used to indicate whether the first user has the authority to check information related to the first label. The information related to the first label may be displayed on a page related to the first label. Thus, in some embodiments, if the first user does not have the authority to check the first label, the content displayed to the first user does not include the page related to the first label, regardless of whether the first user has the authority to check the first information.

[0105] In one example, if the first user does not have the authority to check the first label but has the authority to check the first information, the first device can determine that the content to be displayed to the first user includes a page containing the first information. Furthermore, because the first user does not have the authority to check the first label, the page containing the first information does not display the relationship between the first information and the first label. For convenience of explanation, the "page containing the first information" is referred to as a second page. The second page includes the first information, and the first user can check the first information on the second page, but the second page does not display the relationship between the first information and the first label. In other words, the first user can check the first information through the second page, but cannot determine that the first information has the first label through the second page. The second page referred to herein may be, for example, an instant messaging session interface including the first user. The first information may include, for example, session messages in the instant messaging session indicated by the instant messaging session interface and / or files posted by other users in the instant messaging session indicated by the instant messaging session interface. The instant messaging session interface referred to herein may be an instant messaging interface including two users, or an instant messaging session interface including two or more users, and the embodiments of the present application are not specifically limited thereto.

[0106] In one example, the first user triggers a label check operation on the label sharing information, thereby triggering a check operation on the label indicated by the label sharing information. After the first user triggers the label check operation on the label sharing information, the first device can determine display content on a label-related page displayed to the first user based on the first user's check authority for the label indicated by the label sharing information. The label sharing information may be, for example, a hyperlink or a label identifier, although the embodiments of the present application do not specifically limit this. The label check operation triggered on the label sharing information may be, for example, a click operation. For specific implementation of "determining display content on a label-related page displayed to the first user based on the first user's check authority for the label indicated by the label sharing information," please refer to the relevant descriptions above regarding "the first user's check authority for the first label" and "content to be displayed on the first label-related page displayed to the first user," and no further details will be provided here.

[0107] Exemplary Equipment Based on the method provided by the above embodiments, the embodiments of the present application further provide an apparatus, which will be introduced below in conjunction with the drawings.

[0108] Please refer to Figure 3, which is a structural schematic diagram of an information processing device provided by an embodiment of the present application. The device 300 specifically includes: a first obtaining unit 301 for obtaining a first label indicated by a label adding operation triggered by a first user in response to the label adding operation; a second obtaining unit 302 for obtaining a usage right of the first label, the usage right being used to indicate whether the first user has a usage right of the first label; and a first display unit 303 for displaying the first label and / or usage rights information for indicating usage rights of the first label.

[0109] Preferably, if the usage rights information indicates that the first user does not have the right to use the first label, the usage rights information further instructs the first user to request the right to use the first label from the owner of the first label.

[0110] Preferably, if the usage right information indicates that the first user has usage rights for the first label, the device: The device further includes a label adding unit that adds the first label in response to a label adding operation triggered by the first user on the first label.

[0111] Preferably, the label adding unit comprises: The first label is added to the target information.

[0112] Preferably, the device comprises: a third obtaining unit for obtaining a check authority of a first user for the first label in response to a check operation triggered by the first user for the first label, the check authority being used to indicate whether the first user has the authority to check related information of the first label; and a second display unit for displaying information related to the first label when it is determined that the first user has the authority to check the first label.

[0113] Preferably, the second display unit A related page of the first label is displayed, the related page of the first label including related information of the first label.

[0114] Preferably, the associated page of the first label is: The information unit includes summary information of the information unit having the first label, the information unit includes second information, and the first user has the authority to check the second information.

[0115] Preferably, information summaries of information units having said first label are displayed sorted on the associated page of said first label according to the message domain from which each information unit originates.

[0116] Preferably, each of the information units includes a first information unit, and a message domain from which the first information unit originates is used to indicate a service provider corresponding to the first information unit.

[0117] Preferably, the device comprises: a page jump unit that jumps to a page including the second information in response to a predetermined operation triggered by the first user on the summary information of the second information; and / or The display device further includes a third display unit for displaying the second information in response to a predetermined operation triggered by the first user on summary information of the second information.

[0118] Preferably, the associated page of the first label is: The information further includes summary information of third information having the first label, the first user does not have the authority to check the third information, and the associated page of the first label is a page displayed on a device to which the first user is logged in.

[0119] Preferably, the device comprises: The information processing device further includes a first requesting unit that requests the owner of the third information for the right to check the third information in response to a predetermined operation triggered by the first user on the information summary of the third information.

[0120] Preferably, the device comprises: The device further includes a fourth display unit for displaying first prompt information when it is determined that the first user does not have the authority to check the first label, the first prompt information being used to indicate that the first user does not have the authority to check the related information of the first label.

[0121] Preferably, the first prompt information further prompts the first user to request the owner of the first label for the authority to check the first label.

[0122] Preferably, the device comprises: The device further includes a second request unit for requesting the owner of the first label for the right to check the first label in response to a predetermined operation triggered by the first user in response to the first prompt information.

[0123] Preferably, the device comprises: The device further includes a generating unit for generating authority setting information of the first label in response to an authority setting operation triggered by an owner of the first label on an authority setting interface of the first label.

[0124] Preferably, the authority setting information of the first label includes the check authority of the first label and the use authority of the first label, the priority of the use authority of the first label is higher than the priority of the check authority of the first label, and when the first user has the use authority of the first label, he or she also has the check authority of the first label.

[0125] Preferably, the owner of the first label: the creator of the first label, or The historical owner of the first label is the user designated when performing the owner status transfer operation.

[0126] Preferably, the device comprises: a first determination unit for determining a first user's authority to a first label and a check authority of the first user to a first information, the first information comprising the first label; and a second determination unit for determining display content for the first user based on the first user's authority for the first label and the first user's check authority for the first information.

[0127] Preferably, the second determination unit If the first user has the authority to check the first label but does not have the authority to check the first information, it is determined that the first page displayed to the first user does not include the first information.

[0128] Preferably, the second determination unit If the first user has a check authority for the first label and does not have a check authority for the first information, determine that the content displayed to the first user includes an associated page of the first label, and the associated page of the first label includes: The information unit includes summary information of the information unit having the first label, the information unit includes second information and does not include the first information, and the first user has the authority to check the second information.

[0129] Preferably, the second determination unit If the first user has check authority for the first label, in response to the first user joining the instant messaging session, the first information having the first label in the instant messaging session is displayed in association with the first user.

[0130] Preferably, the second determination unit If the first user does not have the authority to check the first label and has the authority to check the first information, it is determined that the content displayed to the first user does not include a related page of the first label.

[0131] Preferably, the second determination unit determining that the content to be displayed to the first user includes a second page if the first user does not have the authority to check the first label and has the authority to check the first information; The second page includes the first information, and the second page does not display an association between the first information and the first label.

[0132] Preferably, the second page comprises: an instant messaging session interface for the first user, the first information comprising: The instant messaging session includes session messages in the instant messaging session indicated by the instant messaging session interface and / or files posted by other users in the instant messaging session indicated by the instant messaging session interface.

[0133] Preferably, the device comprises: The information sharing device further includes a third determination unit that, in response to a label check operation triggered by the first user on the label sharing information, determines display content in a label-related page to be displayed to the first user based on the first user's check authority for the label indicated by the label sharing information.

[0134] Since the device 300 corresponds to the method provided by the above method embodiments, the specific implementation of each unit of the device 300 is the same as the concept of the above method embodiments. Therefore, for the specific implementation of each unit of the device 300, please refer to the description of the above method embodiments, and no further details will be given here.

[0135] An embodiment of the present application further provides an apparatus, the apparatus including a processor and a memory; The processor executes the instructions stored in the memory to cause the device to perform the methods described in the above method examples.

[0136] An embodiment of the present application further provides a computer-readable storage medium containing instructions, the instructions directing an apparatus to perform the method described in the above method embodiment.

[0137] An embodiment of the present application further provides a computer program product, which, when executed on a computer, causes the computer to perform the method described in the above method embodiments.

[0138] On the other hand, the amount of data generated by software increases with the duration of use. Therefore, when a user wants to select a desired object from the data, they must determine whether each piece of data is the desired object, making it difficult to quickly find the desired object. For example, if a user wants to search for chat history related to Project A from chat history, the user must browse a large amount of chat data to find the chat history related to Project A. As such, it can be seen that the speed at which a user searches for a target object in the conventional technology is slow.

[0139] To solve this problem, the related art provides a favorites function, allowing users to add data they need to use to favorites, which can improve the speed at which users can search for target objects to some extent. However, this method displays all objects added to favorites. When there are a large number of objects added to favorites, the problem of slow speed at which users can search for target objects still exists. To solve the problems of the prior art, the embodiments of the present application further provide an information interaction method and a label checking method, which will be described in detail below in conjunction with the drawings in the specification.

[0140] 4 is a flow diagram of an information interaction method provided by an embodiment of the present application, which is applied to a scenario of adding a label to a target object, and the method is executed by a processing device for adding a label, which is realized in the form of software and integrated into a user's client. The client may be a PC (Personal Computer) terminal or a mobile terminal. As shown in FIG. 4, the method specifically includes the following steps:

[0141] S201: The client accepts a label addition operation triggered by a user for a target object.

[0142] When a user adds a label to a target object, the user can trigger a label addition operation for the target object by performing an operation on the client. The client accepts the label addition operation triggered by the user.

[0143] In an embodiment of the present application, the target object may be any one of operational objects to which a label can be added, such as a cloud document, a schedule, a task, an instant messaging (IM) message, and an instant messaging group. A cloud document may be a document stored on a server or a file in another format. A user may download the cloud document locally from the server, or may open the cloud document by accessing the storage address stored on the server (e.g., opening it in a web page browser). An instant messaging message is a message sent or received by a user using instant messaging software. Instant messaging messages include group chat instant messaging messages and single chat instant messaging messages. A group chat instant messaging message is a message sent by an instant messaging user in an instant messaging group. A single chat instant messaging message is a message sent by one instant messaging user to another instant messaging user via single chat. An instant messaging group includes at least three instant messaging users, and a message sent in an instant messaging group can be viewed by any instant messaging user in the group. A single chat is a message sent between two instant messaging users that cannot be seen by a third instant messaging user.

[0144] The label addition operation may be a slide operation or any possible trigger operation on the label addition control, such as clicking on the label addition control. The slide operation is a slide trail on the screen triggered by the user, which is acquired by the client. If the client's screen is a non-touch screen, the slide operation is an operation in which the user uses an external device (e.g., a mouse, a writing board, etc.) to control a cursor or a mouse and move it on the screen to generate a slide trail. If the client's screen is a touch screen, the slide operation may be an operation in which the user moves a finger on the screen to generate a slide trail.

[0145] If the sliding path is a preset path, the client can determine that the user has triggered a label adding operation. For example, assuming that the screen of the client is a touch screen and the preset path is a circle, the client can record the sliding path of the user's finger. If the client detects that the sliding path is a circle, it can determine that the user has triggered a label adding operation.

[0146] The add label control is a control for triggering a label add operation. When a user triggers the add label control, for example, by clicking or long pressing the add label control, the client can determine that the user has triggered the add label operation.

[0147] In an embodiment of the present application, a user may trigger a label addition operation for a target object in an interface displaying the target object, or may trigger a label addition operation for a target object in a label display interface displaying the label, as will be described below.

[0148] First, we will introduce a situation in which a user triggers a label addition operation for a target object in an interface displaying the target object. Depending on the target object, the client may display the target object while simultaneously displaying the label addition control, or may hide the label addition control. If the client hides the label addition control, the user can control the client to display the label addition control through a triggered selection operation or display operation. The selection operation refers to the user selecting the target object, which may be, for example, clicking or long pressing the target object. The display operation may refer to the user clicking a display control displayed on the client. For an introduction to the display operation, please refer to the introductions of the embodiments in Figures 5, 6, and 10 below. For an introduction to the selection operation, please refer to the introductions of the embodiments in Figures 7, 8, and 9 below. No further details will be provided here.

[0149] After a user triggers a label addition operation, the client can obtain the target label. In an embodiment of the present application, the target label may be created by the user who triggered the label addition operation, or may be created by another user different from the user. Before obtaining the target label, the client can determine whether the user has the authority to add the target label to the target object. For example, assuming that user A creates label X and user B has the authority to add label X, when user B wants to add label X to the target object, the client can determine that user B has the authority to add label X and add label X to the target object.

[0150] To obtain a target label, the client may display multiple candidate labels that can be added, but the user may only want to add one or more candidate labels to the target object. After triggering a label addition operation, the user may then perform a selection operation on the target labels, i.e., select one or more labels from the candidate labels as target labels. Correspondingly, after accepting the label addition operation triggered by the user, the client may determine the target labels according to the user's needs in order to add the target labels to the target object by accepting the selection operation triggered by the user. For a detailed description of the selection operation, please refer to the description of the embodiments described below, and further details will not be provided here. The candidate labels may include labels created by the user or by other users.

[0151] In an embodiment of the present application, at least one candidate label displayed on the client is arranged according to a predetermined rule, which may include any one or more of the following: label creation time, label access time, and matching degree between the keyword.

[0152] In some possible implementations, one or more candidate labels displayed on the client may not include the target label, so the user can trigger a new label addition operation to create a new label as the target label. In this way, the number of labels displayed on the client is not limited, and the user can create labels independently. Preferably, for a detailed description of the selection operation, please refer to the description of the embodiment in Figures 12 and 13 below, and further description will not be given here.

[0153] Below, we introduce the situations in which a user triggers a label addition operation for a target object in the label display interface.

[0154] The label display interface displays one or more labels, and the one or more labels correspond to the same or different target objects, so that the user can easily manage the labels. For an introduction of the label display interface, please refer to the introduction of the embodiment in Figure 20, and further description will not be given here.

[0155] Because the label display interface can display multiple labels, before triggering the label addition operation, the user can first determine the target label corresponding to the label addition operation. For example, the user can select and click the target label from the multiple labels displayed in the label display interface. Correspondingly, the client can jump to the label details page corresponding to the target label according to the user's click operation.

[0156] In the label detail page corresponding to the target label, the user can select one or more target objects to which the target label needs to be added, and trigger the label adding operation for these target labels.

[0157] In one possible implementation, a user can trigger an add operation, control the client to display at least one candidate object through the add operation, and then select one or more candidate objects from the at least one candidate object as a target object. Correspondingly, the client can accept the add operation triggered by the user on the target label, and display at least one candidate object according to the add operation.

[0158] Specifically, as shown in Fig. 5a, if a user wants to add an object with a target label of "Meeting", the user can trigger the add operation by clicking the add control 210 in the display area. After accepting the add operation triggered by the user, the client can display the interface shown in Fig. 5b.

[0159] 5b includes an add operation area 220. The add operation area 220 includes a title display area 221, an add control 222, a search bar 223, a label domain display area 224, a candidate object display area 225, and a target object display area 226.

[0160] The title display area 221 is used to prompt the user that the purpose of the add operation area 220 is to select a target object to which the label "Meeting" needs to be added, and the add control 222 is used to trigger the label addition operation. The search bar 223 is used to receive keywords entered by the user and search for target objects corresponding to the keywords. The label domain display area 244 is used to display the label domain from which the object corresponding to the summary information originates. For a detailed introduction of the label domain and the label domain display area 244, please refer to the embodiment of FIG. 23 and will not be described here. In the embodiment shown in FIGS. 5b and 5c, the displayed label domain is instant messaging messages, i.e., the objects displayed in the candidate object display area 225 and the target object display area 226 belong to instant messaging messages.

[0161] The candidate object display area 225 is used to display at least one candidate object. In the embodiment shown in FIG. 5b, the candidate object is displayed in the form of a card. The candidate object display area 225 includes a first candidate object card 225-1, a second candidate object card 225-2, and a third candidate object card 225-3 that is not fully displayed. The candidate object card may include one or more of the following: basic information about the candidate object, the user to which the candidate object belongs, the time the candidate object was received, and an information block of the candidate object. For an introduction to the candidate object card, please refer to the introduction to the canvas card below; no further explanation will be given here.

[0162] The target object display area 226 displays at least one target object, and the display format may be the same as that of the candidate object display area 225. In the embodiment shown in Fig. 5b, the target object display area 226 further includes a statistics information display area 226-1. The statistics information display area 226-1 is used to display statistics information of the target objects, and may display, for example, the number of target objects selected by the user.

[0163] In an embodiment of the present application, a user may arbitrarily select one or more candidate objects as target objects. For example, in the interface shown in FIG. 5b, a user may arbitrarily select any one of the candidate objects displayed in the candidate object card as a target object. In an embodiment of the present application, a user can determine a candidate object as a target object by clicking a selection box in the candidate object card, for example, by clicking selection box 225-4. Preferably, the selection box corresponding to a candidate object may be white before being selected as a target object.

[0164] After the user selects the candidate object displayed in the candidate object card 225-1 as the target object, the client displays an interface as shown in FIG. 5c. According to the user's selection, the client determines that the instant messaging message "I have a meeting the morning after tomorrow" sent by Leader D belongs to the target object to which the "I have a meeting" label is to be added. The client then adds a target object card 226-2 to the target object selection area 226, displaying basic information about the target object, the instant messaging message "I have a meeting the morning after tomorrow," and adjusts the display content of the statistical information display area 226-1. The content displayed in the first candidate card 225-1 and the second candidate card 225-2 in the candidate object display area 225 is also changed accordingly. Preferably, the color of the target label selection box may be different from the color of the candidate label selection box. For example, in the embodiment shown in FIG. 5c, the target label selection box 226-3 is black.

[0165] After selecting one or more target objects from the candidate objects, the user can trigger a label addition operation by clicking the label addition control 222. Correspondingly, the client can continue to execute S202 after accepting the label addition operation triggered by the user. For the descriptions of other parts in Figures 5a, 5b, and 5c, please refer to the embodiment in Figure 23, and no further explanation will be given here. Furthermore, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment. A combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0166] S202: The client generates a correspondence according to the label addition operation.

[0167] After accepting the label adding operation triggered by the user on the target object, the client can generate a correspondence between the target object and the target label according to the label adding operation.

[0168] In an embodiment of the present application, the correspondence relationship includes a correspondence relationship between a target label and an information block of the target object. The information block is generated based on the target object. Specifically, the information block includes summary information of the target object to provide a general description of the target object. For example, if the target object is a cloud document, the information block of the target object includes summary information of the cloud document, which may include information such as the title, author, and publication time of the cloud document. If the target object is an instant messaging message, the summary information of the target object may be the sender of the instant messaging message and the first n characters of the instant messaging message, where n is an integer greater than or equal to 1.

[0169] The information block may further include display information of the target object, which is used to display the target object. For example, if the target object is a cloud document, the display information of the target object may include a link to the cloud document, through which all the contents of the cloud document can be displayed. If the target object is an instant messaging message, the display information of the target object may include all the contents of the instant messaging message corresponding to the target label (without opening an instant messaging software window), or may include the call chain of the instant messaging message. Through the call chain, all the contents of the instant messaging message corresponding to the target label can be displayed in the instant messaging software window.

[0170] In an embodiment of the present application, after receiving a label addition operation triggered by a user, and before generating a correspondence between an information block and a label, the client can first determine the information block of the target object based on the target object, for example, extract summary information of the target data and / or provide a unified structural packaging for the target object, etc. After converting the target object into an information block, the client can establish a correspondence between the information block and the label.

[0171] In some possible implementations, the correspondence may further include a correspondence between the target label, the information block of the target object, and information of the user who triggered the label addition operation. The user information may include one or more of the following information: user name, label addition time, etc. In this way, when displaying the target label or the target object, the user can not only see the target label and the target object, but also see which user added the target label to the target object and when the target label was added.

[0172] In the embodiment of the present application, the correspondence relationship may be generated by the client or may be generated by the client controlling the server. If the correspondence relationship is generated by the client, the client can execute S103-1 (not shown). If the correspondence relationship is generated by the client controlling the server, the client can execute S103-2 (not shown).

[0173] S103-1: The client generates a correspondence relationship.

[0174] When the correspondence is generated by the client, the client can store the correspondence between the target label and the information block of the target object. After generating the correspondence, the client can send the correspondence to the server, so that other clients or servers can know the correspondence between the target label and the information block of the target object in some application scenarios.

[0175] S103-2: The client sends the target object and the target label to the server.

[0176] After the correspondence is generated by the server, the client can send the target object and the target label to the server. After receiving the target object sent by the client, the server determines the information block of the target object based on the target object, and establishes the correspondence between the information block of the target object and the target label.

[0177] Here, the client sending the target object and the target label to the server is merely a possible implementation provided by the embodiments of the present application. In some other implementations, the client may obtain the target label and the information block of the target object and send them to the server, so that the server generates a correspondence between the target label and the information block of the target object. However, the embodiments of the present application are not limited thereto.

[0178] In some possible implementations, after determining the target label, the client can display prompt information, which is used to indicate that adding the target label to the target object is complete. After viewing the prompt information, the user can know that the client has already added the target label to the target object. Preferably, the prompt message can be an icon or a text message.

[0179] In some possible implementations, a user can trigger a label check operation after adding a target label to a target object. After the client accepts the user-triggered label check operation on the target object, the client can display the target label according to the check operation. In this way, the user can view the label added to the target object and determine whether the user added an incorrect label to the target object.

[0180] In some possible implementations, the client may display a content check control after generating the correspondence. When a user clicks on the content check control or triggers a check operation on the content check control in other ways, the client searches the correspondence according to the check operation to determine and display an information block corresponding to the target label. The information block may include, for example, an information block that may be the target object. If the information block includes summary information of the object, the summary information of the object corresponding to the target label may be displayed.

[0181] In response to a user's trigger operation on an information block of a target object, the client can jump to an interface including the target object or display the target object. In one possible implementation form, in response to a user's trigger operation on summary information of a target object, the client can jump to an interface of the target object or display the target object based on the above-mentioned exhibition information of the target object.

[0182] For other methods of displaying the label of the target object, please refer to the introduction of the embodiment shown in FIG. 14 below, and no further description will be given here.

[0183] In addition, in an embodiment of the present application, a user may delete a target label of a target object. Specifically, the user can trigger a delete operation on the target label of the target object. After accepting the delete operation, the client can delete the target label of the target object according to the delete operation, for example, delete the correspondence between the target label and the target object.

[0184] In an embodiment of the present application, a user can add a label to a target object. Correspondingly, the client can determine the label the user wants to add to the target object according to the label addition operation triggered by the user on the target object, and further obtain the correspondence between the target label and the information block of the target object. In this way, when a user wants to check an object corresponding to a certain label, the client can search for and display the object corresponding to the label (including the target object) based on the correspondence. In this way, the client can add a label to the target object according to the label addition operation, thereby distinguishing the target object from other objects, allowing the user to quickly find the required object and flexibly manage the objects.

[0185] In addition, in the embodiment of the present application, the correspondence relationship includes the correspondence relationship between the label and the information block of the target object. Thus, compared to the conventional favorite method, the client can display information such as summary information of the target object to the user based on the label and the information block of the target object. This increases the amount of information that the user can view, thereby allowing the user to find the desired object more quickly.

[0186] Furthermore, in the embodiments of the present application, the target object may be any one of the operation objects to which a label can be added, such as a cloud document, a schedule, a task, an instant messaging message, and an instant messaging group. That is, a user can add the same label to target objects in different label domains and check the target objects belonging to the different label domains of the label. In this way, cross-label domain assignment of labels is realized, and management flexibility is improved. For other introductions to label domains, please refer to the following and no further details will be given here.

[0187] In an embodiment of the present application, different target objects belonging to different label domains can be extracted as information blocks, and a correspondence between the information blocks and labels can be generated. Extracting target objects from different label domains as information blocks in this way can resolve homogenization modeling and labeling consistency issues when heterogeneous information entities circulate across business applications and business domains, thereby supporting cross-business information aggregation and double consumption scenarios. That is, information blocking provides uniform packaging for objects from different label domains (i.e., heterogeneous information entities), unifying the labeling operations required without paying attention to the different structures of the content in different domains during labeling operations. Without packaging, heterogeneous entities from different domains would require high aggregation costs without a homogenization solution.

[0188] As can be seen from the above introduction, the target object may be any one of the operation objects to which a label can be added, such as a cloud document, a schedule, a task, an instant messaging message, and an instant messaging group. In the embodiments of the present application, when the target object is different, the manner in which the user triggers the label addition control is also different. Below, the manner in which the user triggers the label addition operation will be introduced by taking the target objects as cloud documents, schedules, tasks, instant messaging messages, and instant messaging groups as examples.

[0189] First, we introduce how a user can trigger a label addition operation when the target object is a cloud document. When the cloud document is displayed by a client, the client can display the name, title, body, and operation controls of the cloud document on the screen.

[0190] In a first possible implementation, the operation controls displayed on the screen of the client may include an add label control, and when the user clicks on the add label control or performs another triggering action on the add label control, the client can determine that the user has triggered an add label operation on the displayed cloud document.

[0191] In a second possible realization, the label adding control is hidden on the screen, and the user controls the client to display the label adding control by triggering a display operation.

[0192] Specifically, as shown in Fig. 6a, when a client displays a cloud document, the display area includes a name display area 310, a title display area 320, a body display area 3230, and an operation control set 340. The name display area 310 is used to display the name of the cloud document, and the title display area 320 is used to display the body title of the cloud document. The body display area 330 is used to display the body of the cloud document. The operation control set 340 includes a view operation control 341, a minimize operation control 342, and a close operation control 343, but does not include an add label control.

[0193] The close operation control 343 is used to close a cloud document. For example, when a user single-clicks the close operation control 343, the client closes the cloud document. The minimize operation control 342 minimizes the cloud document. For example, when a user single-clicks the minimize operation control 3242, the client displays the cloud document as minimized. The show operation control 341 displays hidden operation controls. In an embodiment of the present application, the hidden operation controls include operation trigger controls.

[0194] If a user wants to add a label to a cloud document, they can click the view operation control 341 or perform other trigger actions on the view operation control 341. After the client detects that the view operation control 341 has been triggered, it displays hidden operation controls on the screen. As shown in FIG. 6b, after the user clicks the view operation control 341, the client displays a hidden control set 350. The hidden control set 350 includes an add label control 351, a copy control 352, a cut control 353, a delete control 354, and a jump control 355. The add label control 351 is used to trigger the add label operation. The copy control 352 is used to copy the cloud document. The cut control 353 is used to copy the cloud document and delete the original cloud document after the cloud document in the clipboard is overlaid. The delete control 354 is used to delete the cloud document. The jump control 355 is used to jump to other interfaces so that the user can perform other operations on the cloud document.

[0195] Preferably, the add label control can be provided with prompt information to prompt the user that the control is to be used to add a label. As shown in Fig. 6b, the prompt information of the add label control 351 is "add label", and the prompt information of the copy control 352 is "copy".

[0196] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0197] The following describes how a user can trigger a label addition operation when the target object is a schedule. When a calendar is displayed by a client, the client can prompt the user for schedule information corresponding to the time by adding a marking to the position on the calendar corresponding to the schedule based on the time information corresponding to the schedule, using the calendar as the background.

[0198] In a first possible implementation, the client can display an add label control on the screen, and when the user clicks on the add label control or performs some other triggering action on the add label control, the client can determine that the user has triggered an add label operation on the displayed schedule.

[0199] In a second possible implementation, the add label control is hidden on the screen and the user can control the client to display the add label control by triggering a select operation.

[0200] Specifically, as shown in Fig. 7, when the client displays a schedule, a display area 400 may include a display mode control 410, a calendar display area 420, and an operation control set 430. The display mode control 410 is used to switch the calendar division unit. For example, in the embodiment shown in Fig. 7, dates are divided into weeks, and the schedule for one week is displayed in the display area 400. When the user switches the display mode using the display mode control 410, the client may further display the corresponding schedule in days or months.

[0201] Specifically, when dates are divided into weeks, the calendar display area 420 includes multiple schedule display areas 421, date marking areas 422, and time marking areas 423. The schedule display area 421 includes at least one schedule display element. Each schedule display element corresponds to one date and one time period and is used to display the schedule for that time period on that date. Preferably, schedule display elements in the same column correspond to different time periods on the same date, and schedule display elements in the same row correspond to the same time period on different dates. The date marking area 422 is used to mark the dates corresponding to the schedule display elements in each column. The time marking area 423 is used to mark the time periods corresponding to the schedule display elements in each column.

[0202] As shown in FIG. 7, the schedule display area 421 includes seven columns of schedule display elements corresponding to the seven days from January 11, 2021 to January 17, 2021. The schedule display element in the first column and first row corresponds to the time period from 9:00 to 10:00 on January 11, 2021. This schedule display element includes a schedule called "Project A," indicating that the schedule from 9:00 to 10:00 on January 11, 2021 is Project A.

[0203] If a user wants to add a label to a schedule, the user can select a schedule display element corresponding to the schedule and control the client to display a label addition control. For example, if the user wants to add a label to a schedule that reads, "I have a meeting on January 13, 2021, from 1:00 PM to 2:00 PM," the user can select schedule display element 421-1. For example, the user can trigger the selection operation by clicking schedule display element 421-1 on the client screen. After receiving the user's selection operation of the label addition control, the client can display a hidden interface, which includes the label addition control. As shown in FIG. 8, after the user selects schedule display element 421-1, the client displays hidden interface 500, which includes an operation control set 510, a schedule information display area 520, a presentation time display area 530, and a label addition area 540.

[0204] The schedule information display area is used to display basic information about the schedule. For example, in the embodiment shown in FIG. 8, the schedule information display area 520 displays that the theme of the schedule is a meeting and the time is January 13, 2021, from 1:00 PM to 2:00 PM. The presentation time display area is used to display the presentation time of the schedule, which indicates how long before the start of the schedule the client will present it to the user. For example, in the embodiment shown in FIG. 8, the presentation time display area 520 indicates that the client will present it to the user 5 minutes before the start of the schedule. The label addition area 540 includes a label display area 541 and an add label control 542. The label display area 541 displays existing labels for the schedule, and the add label control 542 is used to trigger a label addition operation.

[0205] For the embodiment shown in Figures 7 and 8, if a user wants to add a label to the schedule "I have a meeting" corresponding to schedule display element 421-1, he or she can select schedule display element 421-1 and then click label addition control 542 in the hidden interface.

[0206] Of course, in some other implementations, the user may control the client to display the control-add control by triggering a display operation, which is not mentioned here.

[0207] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0208] Below, we will introduce how a user can trigger a label addition operation when the target object is an instant messaging message.

[0209] As can be seen from the above introduction, the instant messaging message includes one or more of: a group chat instant messaging message and a single chat instant messaging message. Hereinafter, the instant messaging message will be taken as an example to be a group chat instant messaging message.

[0210] In a first possible implementation, the client can display an add label control on the screen, and when the user clicks on the add label control or performs some other triggering action on the add label control, the client can determine that the user has triggered an add label operation on the displayed communication group message.

[0211] In the second possible implementation, the label adding control is hidden on the screen, and the user can control the client to display the label adding control by triggering a selection operation.

[0212] When a user checks group chat instant messaging messages on a client, the client can display the group chat instant messaging messages and related information about the instant messaging group. Specifically, as shown in FIG. 9 , when a client displays group chat instant messaging messages, a display area 600 includes a title display area 610, a message display area 620, and an operation area 640. The title display area 610 is used to display basic information about the instant messaging group. For example, in the embodiment shown in FIG. 9 , the title display area 610 displays the group name of the instant messaging group, "Workplace Communication Group," and the group's avatar. Preferably, the title display area 610 may further include a jump control 611 for jumping to another interface. For a detailed introduction to the jump control 611, please refer to the description of the embodiment below, and further explanation will not be given here.

[0213] The message display area 620 is used to display a group chat instant messaging message. Preferably, when displaying a group chat instant messaging message, the client can jointly display the message body and corresponding user information. For example, in the embodiment shown in FIG. 9, the group chat instant messaging message 62 includes an avatar display area 621-1, an identifier display area 621-2, and a body display area 621-3. The avatar display area 621-1 is used to display the avatar of the user who sent the group chat instant messaging message. The identifier display area 621-2 is used to display the identifier of the user who sent the group chat instant messaging message. For example, this may be the user's ID or nickname. The body display area 621-3 displays the body of the group chat instant messaging message sent by the user. In the embodiment shown in FIG. 9, the body of the group message 621 is "Hey everyone, please be careful."

[0214] The operation area 640 may include an input box 641 and a send control 642. The input box 641 is used to input a group chat instant messaging message, and the send control 642 is used to send the group chat instant messaging message in the input box 641 to be sent.

[0215] When a user needs to add a label to a group chat instant messaging message, the user can select the group chat instant messaging message. After accepting the selection operation for the instant messaging message, the client can display a control set. In some possible implementations, the control set includes an add label control. Correspondingly, the user can add a label to the selected group chat instant messaging message by triggering the add label control. Of course, the user may select multiple instant messaging messages at once to add labels to the multiple instant messaging messages. In this case, the client displays the control set after accepting the user's selection operation for the multiple instant messaging messages.

[0216] In some other implementations, the control set does not include the add label control, and the user controls the client to display the add label control by triggering a show operation. More details are provided below.

[0217] As shown in FIG. 9 , when a user wants to add a label to a group chat instant messaging message 630, the user can first select the group chat instant messaging message 630. For example, the user can click a corresponding position on the screen of the group chat instant messaging message 630. In response to the user's selection operation, the client can display a control set 640. The control set 640 includes a reply control 641, a like control 642, and a view control 643. The reply control 641 is used to reply to a message. If the user clicks the reply control 641, the user can reply to the group chat instant messaging message 630. The like control 642 is used to add a like identifier to the group chat instant messaging message 630. If the user clicks the like control 642, the client can add a like identifier to the group chat instant messaging message 630. The view operation control 643 is used to display hidden operation controls. If the user clicks the view operation control 643, the client can display a hidden control set 650 to the user.

[0218] The hidden control set 650 includes an add label control 651, a delete control 652, a multiple selection control 653, and a jump control 654. The add label control 651 is used to trigger a label addition operation. The delete control 652 is used to delete the client's local chat history of the group chat instant messaging message 630. The multiple selection control 653 is used to select the instant messaging group information 630 and to select other group chat instant messaging messages. The jump control 654 is used to jump to other interfaces so that the user can perform other operations on the group chat instant messaging message 630.

[0219] Preferably, the add label control includes prompt information for prompting a user that the add label control will trigger a label addition operation. As shown in Figure 9, the prompt information of the add label control 651 is "add label," and the prompt information of the delete control 652 is "delete."

[0220] If the instant messaging message is a single-chat instant messaging message, the user adopts the same or similar flow to control the client to display the label adding control and trigger the label adding operation, which is not detailed here.

[0221] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0222] Below, we will introduce how a user can trigger a label addition operation when the target object is an instant messaging group.

[0223] In a first possible implementation, the client displays an add label control in an interface including an instant messaging group, allowing a user to trigger a label addition operation using the add label control, where the interface including the instant messaging group may be, for example, an interface displaying group chat instant messaging messages, or an information stream interface including the instant messaging group, and is not limited thereto.

[0224] In a second possible implementation, the chat interface for the instant messaging group does not include an add label control. In this way, the user can control the client to display the add label interface by triggering a display operation. For example, in the embodiment shown in FIG. 9, the chat interface 600 for the instant messaging chat group does not include an add label control for adding a label to the group. The user can control the client to display the setup interface for the instant messaging group by clicking on the jump control 611, which includes an add label control for triggering the add label operation.

[0225] As shown in FIG. 10, when displaying the instant messaging group setup interface, the client display area 700 includes a title display area 710, a position adjustment control 720, an avatar adjustment control 730, a name adjustment control 740, and a label addition control 750.

[0226] The title display area 710 is used to display basic information and basic operation controls of the setup interface. For example, in the embodiment shown in Figure 10, the title display area 710 displays that the name of the setup interface is "Setup - Workplace Communication Group", and the setup interface is used to set up information related to the instant messaging group whose group name is "Workplace Communication Group".

[0227] The position adjustment control 720 is used to adjust the relative position of the currently located interface and the display area 700. As shown in Fig. 10, the position adjustment control 720 includes a chute 721 and a slider control 722. The slider control 722 can be moved up and down in the chute 721 to adjust the relative position of the installed interface and the display area 700.

[0228] The avatar adjustment control 730 may display an avatar for the instant messaging group or may be used to adjust the avatar for the instant messaging group. For example, when a user wants to modify the group avatar for the instant messaging group "Workplace Communication Group," the user can click on the corresponding position of the avatar adjustment control 730 on the client screen to trigger an avatar change operation and adjust the group avatar for the instant messaging group.

[0229] The name adjustment control 740 may be used to display the group name of the instant messaging group or to adjust the name of the instant messaging group. As shown in FIG. 10 , the name adjustment control 740 includes marking information 741, a name display area 742, and an edit control 743. The marking information 741 is used to prompt the user that the content displayed in the name display area 742 is the name of the instant messaging group. The name display area 742 is used to display the name of the instant messaging group, and the edit control 743 is used to trigger a name change operation. For example, if a user wants to modify the group name of the instant messaging group "Workplace Communication Group," the user can click the edit control 743 in the name adjustment control 740 on the client screen to trigger a name change operation and adjust the group name of the instant messaging group.

[0230] The label addition control 750 may be used to add a label to an instant messaging group, display a label corresponding to the instant messaging group, or adjust the label corresponding to the instant messaging group. As shown in FIG. 10 , the label addition control 750 includes marking information 751, a label display area 752, and an edit control 753. The marking information 751 is used to prompt the user that the content displayed in the label display area 752 is a label corresponding to the instant messaging group. The label display area 752 is used to display a label corresponding to the instant messaging group. Preferably, if the instant messaging group does not have a label, the label display area 742 can display "No label yet." The edit control 753 is used to trigger a label addition operation. Preferably, if the instant messaging group has a label, the edit control 753 is further used to trigger a label deletion operation or a label change operation.

[0231] In some possible implementations, edit control 753 may include an instruction message to prompt the user that edit control 753 is being used to trigger a label add operation, or a label remove operation, or a label change operation. For example, if the instant messaging group does not have a label, the instruction message of edit control 753 may be "ADD" and used to prompt the user that edit control 753 is being used to trigger a label add operation. If the instant messaging group has a label, the instruction message of edit control 753 may be "ADD" and used to prompt the user that edit control 753 is being used to trigger a label add operation, a label change operation, or a label remove operation.

[0232] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0233] The above introduces a method in which a user triggers a label addition operation on a target object. In an embodiment of the present application, after accepting the label addition operation triggered by the user, the client may further accept a selection operation triggered by the user, and determine a target label according to the selection operation.

[0234] Before accepting the selection operation triggered by the user, the client displays at least one candidate label in accordance with the label addition operation, allowing the user to view these candidate labels on the client screen and select a target label from the candidate labels. For example, the user can click on a position corresponding to a target label on the client screen. After detecting that a position corresponding to one of the candidate labels has been clicked, the client can determine that the candidate label is the target label selected by the user. The client can display at least one candidate label in a list format. The user can view the list displayed on the client and select one or more candidate labels from the list as target labels according to actual needs. In this way, the client can determine a target label corresponding to a target object in accordance with the user's click operation and add the target label to the target object.

[0235] In a practical application scenario, the number of candidate labels may be large, which may result in a long time for the user to select a target label from the candidate labels. To solve this problem, the client can display a label input box and determine the target label based on the user's input.

[0236] Specifically, as shown in FIG. 11 , when the client displays the label input box, the display area 800 includes a title display area 810, an operation control set 820, a label input box 830, a label addition control 840, and a candidate label display area 850. The title display area 810 is used to display basic information of the interface. For example, in the embodiment shown in FIG. 11 , the title display area 810 displays "Determine Target Label," and the interface is used to determine the target label from the candidate labels. The operation control set 820 may be similar to the operation control set 240 of FIG. 2 and is not described here. The label input box 830 is used to receive keywords entered by the user. The label addition control 840 is used to select the target label.

[0237] The candidate label display area 850 is used to display at least one candidate label that matches the keyword entered by the user in the label input box 830. If there are multiple candidate labels, the multiple candidate labels are sorted in descending order of their matching degree with the keyword. As shown in FIG. 11 , the candidate label display area 850 displays four candidate labels, namely, Label 1, Label 2, Label 3, and Label 4. In this case, Label 1 is the candidate label that matches the keyword most, and the matching degree between Label 2 and the keyword is lower than Label 1 and higher than Label 3 and Label 4. Of course, in some other implementations, the client may sort the candidate labels according to the label creation time or label access time of the candidate labels, which is not limited to the embodiments of the present application.

[0238] Preferably, the label addition control 840 may be located in the candidate label display area. In this way, when the user clicks on any one of the candidate labels in the candidate label display area, the label addition control 840 is triggered and the client accepts the user's selection operation for the target label.

[0239] If the number of candidate labels is small, the client may display all candidate labels, and the user can select the label that he / she wants to add to the target object from the labels displayed on the client, and add the label to the target object by a selection operation.

[0240] Specifically, the client can display the candidate labels in the form of cards. When the client displays all candidate labels, the candidate label display area 850 includes label card, label card, label card, label card, label card, and label card. Each label card has an independent boundary and includes name information. The name information is used to display the name of the label corresponding to the label card. For example, the name of the label corresponding to the label card is "Workplace."

[0241] The user can determine which label cards they want to add based on the name information of the label cards and select these label cards. After selecting the labels, the user can trigger the label addition control 840, which allows the client to determine which labels the user wants to add to the target object.

[0242] In an embodiment of the present application, after a user selects a label card, the client can change the background color of the label card, for example, changing the background color of the label card indicates that the user wants to add the label to the target object.

[0243] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0244] The above embodiment introduces an information interaction method, in which a user can add a label to a target object. Below, we will introduce a label acquisition method, that is, the above label is obtained from the label creation method introduced below.

[0245] In an embodiment of the present application, a user may create a label using label creation controls in a label creation interface, or may create a label when adding a label.

[0246] First, a user is introduced to creating a label using the label creation controls in the label creation interface.

[0247] When a user creates a label using the label creation interface, the user first triggers the client to jump to the label creation interface. For example, the user can click a jump control or input a homepage address to jump to the label creation interface. After jumping to the label creation interface, the user inputs a label name into the interface to trigger the label creation control, thereby controlling the client or server to create a label.

[0248] Specifically, as shown in FIG. 12 , the label creation interface 900 includes a title display area 910, a label name input box 920, a label details input box 930, and a label creation control 940. The title display area 910 is used to display basic information about the interface. For example, in the embodiment shown in FIG. 12 , the title display area 910 may display "Create New Label," indicating that the interface is used to create a label. The label name input box 920 is used to receive a label name entered by a user. The label details input box 930 is used to receive label details entered by a user, and the label creation control 940 is used to trigger a label creation operation.

[0249] After inputting a label name in the label name input box 920, the user can trigger a label creation operation by triggering the label creation control 940. After accepting the label creation operation triggered by the user, the client can obtain the content input by the user in the label name input box 920 as the name of the newly created label. Preferably, the user may further obtain the content input by the user in the label description input box 930 as the detailed description of the newly created label.

[0250] Preferably, as shown in FIG. 12, before the user inputs data, the label name input box 920 and the label details input box 930 can display prompt information to prompt the user as to what information to input into the input box.

[0251] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0252] Below, we will show you how to create a label if you want to add one.

[0253] As can be seen from the above introduction, when a user selects a target label from the candidate labels, the user can input a keyword into the label input box and find the target label in the candidate label display area. However, if the candidate labels do not include the target label, the target label cannot be found in the candidate label display area. Therefore, the user can create a new label during the label addition process. Preferably, the user can jump to another interface using the jump control to create a label, or can create a label in the current interface. A detailed explanation is provided below.

[0254] In a first possible implementation, the display interface of the label input box displayed on the client includes a jump control, which is used to jump to a label creation interface, so that after a user finds that the candidate labels do not include the target label, the user can trigger the jump control to create a new label in the label creation interface.

[0255] In a second possible implementation, the candidate label display area includes a label creation control, which the user can use to create a new label.

[0256] 13, when the client displays a label input box, a display area 1000 includes a title display area 1010, an operation control set 1020, a label input box 1030, a selection control 1040, and a candidate label display area 1050. The title display area 1010, the operation control set 1020, the label input box 1030, and the selection control 1040 are similar to the corresponding areas or controls in FIG. 11, and therefore will not be described here in detail.

[0257] The candidate label display area 1050 includes a first prompt information display area 1051, a first candidate label display area 1052, a second candidate label display area 1053, a first prompt information display area 1054, and a label creation control 1055. The first prompt information display area 1051 is used to prompt the user that the content displayed in the first candidate label display area 1052 and the second candidate label display area 1053 is a candidate label. The first candidate label display area 1052 displays the candidate label that most closely matches the keyword entered by the user, and the second candidate label display area 1053 displays the candidate label that second most closely matches the keyword entered by the user. The second prompt information display area 1053 is used to prompt the user that the label creation control 1055 is used to create a new label. The label creation control 1055 is used to trigger a label creation operation. Preferably, the label creation control 1055 includes label preview information. The label preview information is the name of the newly created label, which matches the keyword entered by the user in the label input box 1030 .

[0258] When a user inputs a keyword into the label input box 1030 and there is no candidate label that perfectly matches the keyword, the client can display a first prompt information display area 1054 and a label creation control 1055 in the candidate label display area 1050. If the user thinks that a new label needs to be created to meet the needs of the existing candidate labels and target label, the user can click the label creation control 1055 to trigger a label creation operation and control the client or server to create a new label. The name of the label is the keyword input by the user into the label input box 1030.

[0259] Preferably, in some possible implementations, the user may create a new label using the label addition control 1040 rather than the label creation control 1055. Specifically, the client receives a keyword entered by the user through the label input box 1030. The client can display labels that match the keyword as candidate labels. When the label addition control 1040 is triggered, the client can add a label that matches the keyword to the target object and store the label as a label created by the user.

[0260] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0261] In an embodiment of the present application, the creator of the target label further sets operation permissions for the target label, so that users with different operation permissions can perform different operations on the target object with the target label. The operation permissions can include edit permission and / or check permission. The edit permission includes one or more of the following: modify permission for the target label, modify permission for the target object with the target label, and modify permission for the association relationship between the target label and the target object. When checking the target object, the check permission includes one or more of the following: permission to see the target label, permission to check the target object, and permission to check all target objects with the target label.

[0262] Specifically, a user can trigger a permission setting operation for a target label in a label checking interface, or can trigger a permission setting operation for the target label after adding the target label to a target object, and the client can accept the permission setting operation and determine the operating user with the target label according to the permission setting operation.

[0263] The operation permissions include three permissions: all members of the organization can edit, can add, collaborators can edit and other members of the organization can view, and only collaborators can edit or check. An organization is a team to which a user belongs. For example, it may be a company, department, or project team to which a user belongs, and a collaborator may be one or more other users added by the user, for example, selected by the user in the organization.

[0264] The three operating permissions are explained in detail below. When a user sets the operation authority of the target label so that all members in the organization can edit it, the client can accept the editing operation of any one member in the organization and make editing modifications to the target label or the target object having the target label according to the editing operation of the member. Optionally, the editing operation may further include deleting the label of the target object or adding the target label to the target object. If a user sets the operation permissions for a target label so that only collaborators can edit it and other members can check it, the client can obtain the information of the collaborators selected by the user. When receiving an edit request from another user, the client compares the information of the other user with the information of the collaborator to see if they are the same. If the two pieces of information are the same, the client can edit and modify the target label or target object according to the user's editing operation. If the two pieces of information are different and the other user is a member of the organization, the client can display the target label or target object and prohibit the user from editing it. When a user sets the operation authority of a target label so that only collaborators can edit or check it, the client assumes that the user is not the creator of the target label or a collaborator set by the creator, and does not display the target object or target label. For example, when displaying a target object, the client can hide the target label that the target object has.

[0265] In addition, in the embodiment of the present application, the creator of the target label may also delete the target label. Specifically, the user can trigger a delete operation on the target label. After accepting the delete operation, the client can delete the target label according to the delete operation, for example, delete the correspondence between the target label and any one of the objects. For a detailed description of the delete operation, please refer to the description of the label checking method below, and no further details will be given here.

[0266] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0267] The above is an introduction of the information interaction method provided by the embodiment of the present application. Correspondingly, the embodiment of the present application further provides a corresponding label checking method, which will be introduced in detail below.

[0268] Please refer to FIG. 14, which is a flow diagram of a label checking method provided in an embodiment of the present application, and the method specifically includes the following steps: S1101: The client accepts the label check operation triggered by the user for the label check control.

[0269] When a user wants to check a label, the client can trigger a label check operation on the label check control. Correspondingly, the client can accept the label check operation triggered by the user. In the embodiment of this application, the label check control may be related to a target object or may be unrelated to the target object. The following introduces these two situations respectively.

[0270] In the first possible implementation, the label check control is related to the target object, that is, the label check operation is used to check the label corresponding to the target object. After the label check control is triggered, the label check operation accepted by the client is the label check operation for the target object, and the displayed label is also the label possessed by the target object. In this way, the user can see the label possessed by the target object.

[0271] Preferably, the label check control for the target object may be located in the interface where the target object is located. The client displays the target object and also displays the label check control. In this way, when the user checks the target object, the corresponding label check operation can be triggered. Correspondingly, when the client accepts the label check operation for the target object, the client displays the label that the target object has to the user. In this way, when the user checks the target object, the client controls the label check control to display the label that the target object has.

[0272] Of course, the client can display the label of the target object in the interface that displays the target object, i.e., display the target object and the label of the target object simultaneously. In this way, the label check control can also be a control for jumping to the interface that displays the target object. That is, after the user clicks the label check control in another interface (which does not include the target object), the client can jump to the interface corresponding to the target object and check the label of the target object. In this way, the user can check the target object and the label of the target object simultaneously in one interface.

[0273] As can be seen from the above introduction, in the embodiment of the present application, the target object may be any one of the operation objects to which a label can be added, such as a cloud document, a schedule, a task, an instant messaging message, and an instant messaging group. In the embodiment of the present application, when the target object is different, the manner in which the user triggers the label check control is also different. For the introduction of this part, please refer to the introduction of the embodiment corresponding to Figures 15 to 20 below, and no further explanation will be given here.

[0274] In a second possible implementation, the label check control is not directly related to a target object, but to a label. Correspondingly, the label check operation is used to check the label itself, not the label that a target object has. That is, after the label check control is triggered by the user, the client jumps to a label display interface. The label display interface displays one or more labels, and the one or more labels can correspond to the same or different target objects. This allows the user to manage the labels.

[0275] For an explanation of the contents of this part, please refer to the explanation of the embodiment corresponding to the following FIGS. 21 to 24, and no further explanation will be given here.

[0276] S1102: The client displays at least one label according to the label check operation.

[0277] After receiving the label check operation, the client can display at least one label for the user to check according to the label check operation. Preferably, the client can display information about the creator of the label along with the label display. The information about the creator includes the creator's name, contact information, team, job title, etc.

[0278] Preferably, when displaying multiple labels, the client can first sort the labels according to a predetermined rule and then display the multiple labels in order. The predetermined rule includes any one or more of sorting according to label access time, sorting according to label creation time, and label priority. For example, if the predetermined rule is sorting according to label creation time, the client obtains the creation time of each label among the at least one label and sorts the labels in order of most recent creation time. The priority of a label is determined based on whether the label is added to favorites.

[0279] As can be seen from the above introduction, the label check operation is used to check a label corresponding to a target object or all labels. When the label check operation is used to check a label corresponding to a target object, the client can display at least one label corresponding to the target object. When the label check operation is used to check all labels, the client can display all labels visible to the user. Preferably, when the label check operation is used to check all labels, the client can modify at least one displayed label, for example, perform operations such as detailed check, deletion, and grouping on the labels. For specific details of this part, please refer to the following introduction and no further details will be given here.

[0280] In an embodiment of the present application, all labels displayed on the client may include labels created by the user, or may include labels created by other users for which the user has the authority to check. An example is shown in which the client displays labels created by the user and labels created by other users for which the user has the authority to check. After receiving a label check operation, the client triggers the server to sort the labels created by the user and labels created by other users from all stored labels. The client then determines one by one whether the user has the authority to check the corresponding labels created by other users, selects the labels for which the user has the corresponding authority to check, and sends the labels created by the user and the labels created by other users for which the user has the authority to check to the client.

[0281] In some possible implementations, if a user does not have the check authority for a label they want to check, they can request the check authority for that label from the user who created the label. Specifically, assuming that user X does not have the check authority for label A, they can trigger an authority request operation for label A. After receiving the operation triggered by the user, the client can generate an authority request request according to the authority request operation and send it to user Y, who created label A. The authority request request is used to request the check authority for label A. After viewing the authority request request, user Y can approve the authority request request so that user X has the check authority for label A and can view label A in the client. Of course, user Y can also reject the authority request so that user X cannot view label A.

[0282] In some possible implementations, a user can select a label. Specifically, the user can trigger a selection trigger operation on the selection control. The client accepts the selection trigger operation triggered by the user, triggers a selection operation according to the selection trigger operation, and displays the selection result.

[0283] Preferably, the sorting operation can include a sorting condition. Correspondingly, the sorting operation triggered by the sorting trigger operation can sort labels based on the sorting condition. Specifically, the sorting condition includes an attribute value condition of at least one attribute. In this way, the sorting operation can sort labels displayed on the target interface according to the attribute value of the at least one attribute.

[0284] In an embodiment of the present application, the at least one attribute may include any one of user-owned, other-user-owned, and ownership-unrestricted. A label with the attribute user-owned is a label created by the user himself / herself. A label with the attribute other-user-owned is a label created by other users themselves. A label with the attribute ownership-unrestricted includes both a label created by the user and a label created by other users.

[0285] Below we will introduce in detail how a user can trigger a label check operation based on whether the label check control is related to the target object.

[0286] First, we introduce the situation where the label check control is related to the target object, that is, the label check control is used to check the label that the target object has.

[0287] As can be seen from the above introduction, the target object is any one of the operation objects to which a label can be added, such as a cloud document, a schedule, a task, an instant messaging message, and an instant messaging group. In the embodiments of the present application, when the target object is different, the manner in which the user triggers the label check operation may be different. Below, taking the target objects as cloud documents, schedules, instant messaging messages, and instant messaging groups as examples, the manner in which the user triggers the label check operation will be respectively introduced.

[0288] Here, after receiving the label check operation, the client may display all labels that the target object has, or may display, among all labels that the target object has, labels created by the user and / or labels created by other users that the user has permission to check. Hereinafter, an example will be described in which the client displays all labels that the target object has.

[0289] First, we introduce how users can trigger the label check operation when the target object is a cloud document.

[0290] In a first possible implementation, a client can display a cloud document and the labels that the cloud document has. Correspondingly, the label check control is a control for checking the label of the cloud document. After the control is triggered, the client can jump to an interface that displays the cloud document and display the cloud document and the labels that the cloud document has.

[0291] As shown in Fig. 15a, when a client displays a cloud document, the display area includes a name display area 1210, a title display area 1220, a body display area 1230, and an operation control set 1240. The title display area 1220 includes a label display area 1221 for displaying labels that the cloud document has.

[0292] Preferably, when displaying labels, the client can display identifier information to prompt the user that the displayed content is a label. For example, in the embodiment shown in FIG. 15a, a hash symbol "#" can be displayed before each label. In this way, when a user views a cloud document, the user can determine that the labels corresponding to the cloud document include two labels: "Software Project" and "Feature Update Description."

[0293] For the other parts of FIG. 15a, please refer to the introduction of the embodiment in FIG. 2 and FIG. 3, and no further description will be given here.

[0294] In a second possible implementation, the client can display a cloud document and a label check control interface corresponding to the cloud document. For example, in the embodiment shown in FIG. 15b, the title display area 1220 includes a label check control 1222. The user can trigger the label display operation by triggering the label check control 1222. Correspondingly, after receiving the label display operation, the client can display the labels of the cloud document. Preferably, in some other implementations, the client can hide the label check control and display the label check control according to the display operation and selection operation triggered by the user. The display operation and selection operation can be introduced above, and will not be described further here.

[0295] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0296] Below, we will introduce how a user can trigger a label check operation when the target object is a schedule.

[0297] In a first possible implementation, the client can display a schedule and also display the labels that the schedule has. Correspondingly, the label check control is a control for checking the schedule. After the control is triggered, the client can jump to an interface that displays the schedule and display the schedule and the labels that the schedule has.

[0298] In a second possible implementation, the client may display a schedule and also display a label check control corresponding to the schedule, and / or may display a label check control corresponding to the schedule according to a display operation or a selection operation triggered by a user on an interface displaying the schedule. Hereinafter, an example will be described in which the client displays a label check control corresponding to the schedule according to a selection operation triggered by a user.

[0299] As shown in Fig. 16, a user can trigger a selection operation by clicking a schedule display element 1310. After the user triggers the selection operation, the client can display a hidden interface 1320, which includes an operation control set 1321, a schedule information display area 1322, a presentation time display area 1323, and a label display area 1324. The label display area 1324 can display labels corresponding to the schedule. In the embodiment shown in Fig. 16, the labels corresponding to the schedule include two labels, "Project A" and "Feature Update Description."

[0300] For the other parts of FIG. 16, please refer to the introduction of the embodiments in FIG. 8 and FIG. 9, and no further explanation will be given here.

[0301] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0302] Below, we will introduce how a user can trigger a label check operation when the target object is an instant messaging message.

[0303] In a first possible implementation, the client can display an instant messaging message and a label included in the instant messaging message. Correspondingly, the label check control can be a control for checking the instant messaging message. After the control is triggered, the client can jump to an interface displaying the instant messaging message and display the instant messaging message and the label included in the instant messaging message.

[0304] In a second possible implementation, the client may display an instant messaging message and display a label display control corresponding to the instant messaging message, and / or display a label display control corresponding to the instant messaging message according to a display operation or a selection operation triggered by a user on an interface displaying the instant messaging message. Hereinafter, an example will be described in which the client displays a label display control corresponding to the instant messaging message according to a selection operation and a display operation triggered by a user.

[0305] 17 , when a user wants to check the label of a group chat IM message 1410, the user can select the group chat IM message 1410. The client can display a control set 1420 according to the user's selection operation, and the control set 1420 includes a display operation control 1421. The user triggers a display operation using the display operation control 1421 to control the client to display a hide control set 1430, and the hide control set 1430 includes a label check control 1431.

[0306] After triggering the label check control 1431, the client can display a label check interface, which includes the label of the group chat IM message 1410. Preferably, the label check interface can be a pop-up dialog box, so that the client can display the label check interface in the interface displaying the group chat IM message. Preferably, the label check interface can be a separate interface, so that the client can jump to another interface to view the label of the group chat IM message.

[0307] Here, the label check control 1431 shown in FIG. 17 and the label addition control 651 shown in FIG. 9 may be the same control.

[0308] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0309] Below, we will introduce how a user can trigger a label check operation when the target object is an instant messaging group.

[0310] In a first possible implementation, the client can display an instant messaging group and display a label that the instant messaging group has. Correspondingly, the label check control can be a control that checks the instant messaging group. After the control is triggered, the client can jump to an interface that displays the instant messaging group and display the instant messaging group and the label that the instant messaging group has.

[0311] As shown in Figure 18, when a client displays an instant messaging group, a title display area 1510 may include a label display area 1511. The label display area 1511 is used to display labels corresponding to the instant messaging group. In the embodiment shown in Figure 18, the labels of an instant messaging group called "Workplace Communication Group" include two labels: "Project A" and "Workplace Group."

[0312] In a second possible implementation, the client may display an instant messaging group and display a label check control corresponding to the instant messaging group, and / or may display a label check control corresponding to the instant messaging group according to a display operation or a selection operation triggered by a user on an interface displaying the instant messaging group. Hereinafter, an example will be described in which the client displays an instant messaging group and displays a label check control corresponding to the instant messaging group.

[0313] 19, when the client displays an instant messaging group, a title display area 1610 may include a jump control 1611, which may function as a label check control. After a user triggers the jump control 1611, the client may accept a label check operation and display the label of the instant messaging group "Workplace Communication Group." Preferably, the client may display the label of the instant messaging group in the current interface, or may jump to another interface and display the label of the instant messaging group.

[0314] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0315] Above we have introduced a scenario in which the label checking control is used to check the label of a target object. Below we will introduce a scenario in which the label checking control is not directly related to the target object, i.e., the label checking control is used to check the label itself.

[0316] If the label check control is not directly used to check the labels of a target object, it can be used to jump to a label display interface. In the label display interface, the client can display at least one label that the user can check (e.g., has the authority to check). By operating any of the at least one label, the user can check the related information of the object corresponding to the label, adjust the related information of the label, and even adjust the correspondence between the label and the object.

[0317] In the embodiment of the present application, the label check control may be located in the initial interface of the client or in any other interface, and accordingly, the user can trigger the label check operation in the initial interface of the client or in any other interface.

[0318] Take for example a user triggering a label check operation in a group chat IM message interface. As shown in FIG. 20 , when a client displays a group chat IM message interface, the display area includes a title display area 1710, a message display area 1720, and a control display area 1730. The title display area 1710 is used to display basic information about the client. For example, in FIG. 20 , the title display area 1710 displays that the name of the software running on the client is “Software X.” The message display area 1720 displays the instant messaging group chat message. A detailed description of the message display area 1720 can be found above, and will not be repeated here.

[0319] The control display area 1730 displays at least one operation control, and in the embodiment shown in FIG. 20 , the control display area 1730 includes a message check control 1731, an address book check control 1732, and a label check control 1733. The message check control 1731, after being triggered, is used to cause the client to display instant messaging group chat messages. In the embodiment shown in FIG. 20 , the message check control 1731 is in a triggered state. The address book check control 1732, after being triggered, is used to cause the client to display an address book. In the embodiment shown in FIG. 20 , the address book check control 1732 is in an untriggered state. The label check control 1733, after being triggered, is used to cause the client to display at least one label. In the embodiment shown in FIG. 20 , the label check control 1732 is in an untriggered state.

[0320] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0321] After the user triggers the label check control, the client can accept the label check operation and jump to a label display interface according to the label check operation. In the label display interface, the client can display at least one label. As can be seen from the above introduction, the at least one label can include labels created by the user and labels created by other users that the user has the authority to check. The user can be a user who is logged in to the client or a user who is operating the client.

[0322] As shown in FIG. 21a, when the client displays the label display interface, the display area may include a title display area 1810, a control display area 1820, a search control 1830, a sorting information display area 1840, and a label display area 1850.

[0323] The title display area 1810 is used to display basic information about the client, and the control display area 1820 includes a label check control 1821. In the embodiment shown in FIG. 21a, the label check control 1821 is in a triggered state. The search control 1830 is used to receive keywords entered by the user and search for labels matching the keywords. The sorting information display area 1840 is used to display the sorting rules for each label card in the label display area 1850. In the embodiment shown in FIG. 21a, the content displayed in the sorting information display area 1840 is "Last," indicating that the sorting rule for labels in the label display area 1850 is sorted according to label access time, with the most recently accessed label being located at the front.

[0324] The label display area 1850 is used to display one or more label cards, each of which can display information related to one label. In the embodiment shown in FIG. 21a, the label display area 1850 includes a first label card 1851, a second label card 1852, a third label card 1853, and a fourth label card 1854 that is not fully displayed. The first label card 1851 includes a color identifier area 1851-1 and a label name display area 1851-2. The color displayed in the color identifier area 1851-1 is used to indicate the creator of the first label 1851, and the label name display area 1851-2 is used to display the name of the first label 1851. In the embodiment shown in FIG. 21a, the color corresponding to the first label card 1851 is black, and the label "I have a meeting" displayed on the first label card 1851 indicates that it was created by the user logged in to the client. In another example, the color displayed in color identifier field 1851-1 may indicate other content, to which the embodiments of the present application are not specifically limited.

[0325] As can be seen from the above introduction, a user can select at least one label to be displayed on a client. In an embodiment of the present application, the label display interface includes a selection control, and the user can control the client to select a label by triggering a selection trigger operation on the selection control.

[0326] As shown in Fig. 21b, the label display interface further includes a filtering control 1860, which includes a current attribute display area 1861 and an attribute change control 1862. The current attribute display area 1861 is used to display the current filtering conditions. In the embodiment shown in Fig. 21b, if the label filtering condition by the client is "no ownership restrictions," the labels displayed on the client include labels created by the user and labels created by other users. The attribute change control 1862 is used to change the filtering conditions of the client.

[0327] When a user wants to select labels with other attributes from the labels, the user can trigger the attribute change control 1862. The client can display an attribute display area 1863 in response to the user's operation. The attribute display area 1863 includes a first attribute selection control 1863-1 and a second attribute selection control 1863-2. When the first attribute selection control 1863-1 is triggered, the client can select labels created by the user from the labels. When the second attribute selection control 1863-2 is triggered, the client can select labels created by other users from the labels.

[0328] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0329] When there are a large number of labels, it may take a long time for a user to find a desired label from the label display interface. Therefore, the user can add one or more labels to favorites by triggering a favorite operation in the label display interface. In this way, when checking the labels added to a certain favorite, the user can quickly find the labels added to favorites from the favorite interface.

[0330] In some possible implementations, a user can trigger a favorites operation through a favorites control. Specifically, as shown in FIG. 22a, label cards displayed in the label display interface can include a favorites control. For example, a first label card 1851 includes a first favorites control 1851-3, a second label card 1852 includes a second favorites control 1852-3, and a third label card 1853 includes a second favorites control 1852-3.

[0331] When a user wants to add a label to their favorites, they click a favorites control on the label card that displays that label. For example, if a user wants to add the label "I have a meeting" to their favorites, they can click the first favorites control 1851-3 on the first label card 1851. In response to the first favorites control 1851-3 being clicked, the client can determine that the user has triggered a favorites operation on the label "I have a meeting" and add the label "I have a meeting" to their favorites.

[0332] Preferably, after adding a target label to favorites, the client can adjust the color of the favorites control in the label card where the target label is located. As shown in Figure 22b, after adding the label "I have a meeting" to favorites, the client can adjust the color of the first favorites control 1851-3 from white to black to prompt the user that the label "I have a meeting" displayed in the first label card 1851 has already been added to favorites.

[0333] After adding any one or more labels to the favorites, the user can trigger a check operation for the favorited labels. For example, the check operation for the favorited labels can be triggered by a check control on the client's homepage, or the check operation for the favorited labels can be triggered in the client's interface that displays the objects added to the favorites. After receiving the check operation, the client can display the favorited labels.

[0334] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0335] In the label checking interface, the client displays one or more labels for the user to view. When the user wants to further check the objects corresponding to a label and other information about these objects, the user triggers a check operation for any one of the labels. Correspondingly, as can be seen from the above introduction, after a label is added to a target object, the client or server can generate a correspondence between the information block of the target object and the label. Then, after accepting the label checking operation, the client can display the information block of the object that has the label.

[0336] In the embodiments of the present application, the information block can include summary information. For ease of explanation, the following embodiments will be described taking the client displaying the summary as an example. Here, if the target object information block includes other information of the target object, the client can also display this information.

[0337] When the information block of the target object includes summary information of the target object, the client can display the summary information of at least one object having the label. For example, when a user triggers a check operation on a first label, the client can jump to a label details interface corresponding to the first label according to the check operation. The label details interface includes summary information of at least one object.

[0338] In order to allow users to easily distinguish between different types of objects, in an embodiment of the present application, the client first classifies at least one object based on a label domain, and then displays the summary information in a classified manner based on the label domain. The label domain represents the origin or type of the object. Preferably, the label domain may be the type of the object. For example, if object A is a cloud document, the label domain corresponding to object A is cloud document. As can be seen from the above discussion, the target object to which the label is added may be an operation object, such as a cloud document, a schedule, a task, an instant messaging message, or an instant messaging group. Correspondingly, the label domain may include one or more of cloud documents, schedules, tasks, instant messaging messages, and instant messaging groups.

[0339] In an embodiment of the present application, when the client displays summary information of at least one object with the same label, the client can display the summary information in the form of a list or a canvas card, which will be introduced in detail below.

[0340] First, we introduce the situation where a client displays summary information in the form of a list.

[0341] When displaying summary information in the form of a list, the client can display summary information of at least one object having a label in order. Specifically, as shown in Fig. 23, when the client displays summary information in the form of a list, the display area includes a title display area 2010, a control display area 2020, a display mode switching control 2030, and a label display area 2040. The title display area 2010 and the control display area 2020 can be described above, and will not be described in detail here.

[0342] The display mode switching control 2030 is used to switch the display mode of the summary information by the client. For example, the display mode may be switched from a list type to a canvas card type, or from a canvas card type to a list type. In the embodiment shown in FIG. 23 , the display mode switching control 2030 includes a canvas card type display control 2031 and a list type display control 2032. The canvas card type display control 2031 is in an untriggered state, and the list type display control 2032 is in a triggered state, indicating that the client is currently displaying the summary information in a list type.

[0343] The label display area 2040 includes a label switching control 2041, a label name display area 2042, a label domain display area 2043, and at least one summary information display area.

[0344] The label switching control 2041 is used to switch to another label. When the user wants to check another label, the user can trigger the label switching control 2041, and the label name display area 2042 is used to display the name of the label. For example, in the embodiment shown in Fig. 23, the user can determine based on the label name display area 2042 that the currently displayed summary information belongs to the label "I have a meeting."

[0345] The label domain display area 2043 may display the label domain from which the object corresponding to the summary information originates, or may switch between displaying summary information of objects originating from other label domains. As shown in FIG. 23 , the label domain display area 2043 includes a first label domain name 2043-1, a second label domain name 2043-2, and marking information 2043-3. The first label domain name 2043-1, which is “message,” indicates that the object originating from the label domain is an instant messaging message. The second label domain name 2043-2, which is “group,” indicates that the object originating from the label domain is an instant messaging group. The marking information 2043-3 is used to mark the label domain to which the summary information currently displayed on the client belongs. In the example shown in FIG. 23 , the marking information 2043-3 indicates, for the first label domain name 2043-1, that the object corresponding to the summary information currently displayed on the client originates from the label domain “instant messaging message.”

[0346] Of course, in some possible implementations, the client does not sort the summary information based on label domains, and accordingly, label display area 2040 does not include label domain display area 2043.

[0347] In the embodiment of the present application, the label display area 2040 may include one or more summary display areas. Each summary display area is used to display summary information of one object. Hereinafter, an example will be described in which the label display area 2040 includes a summary display area 2044.

[0348] As shown in FIG. 23 , when the summary information displayed on the client is summary information of an instant messaging message, the summary display area 2044 may include at least one of a summary avatar display area 2044-1, a summary content display area 2044-2, and an object information display area 2044-3. The summary avatar display area 2044-1 is used to display the avatar of the user who sent the instant messaging message. The summary content display area 2044-2 may display the specific content of the instant messaging message. Preferably, if the specific content of the instant messaging message is extensive, the summary content display area 2044-2 may display a portion of the instant messaging message, such as the first 10 characters of the message. The object information display area 2044-3 may display other information of the instant messaging message. For example, in the embodiment shown in FIG. 23 , the object information display area 2044-3 may display the sending time of the instant messaging message. Of course, the object information display area 2044-3 may also display other information, such as the instant messaging group to which the instant messaging message belongs.

[0349] Preferably, the label display area may further include instruction information for prompting the user about the content displayed in each display area in the summary display area. For example, in the embodiment shown in FIG. 23 , the label display area 2040 includes two instruction information items, "Message Content" and "Last Sent." The prompt information "Message Content" is used to prompt the user that the corresponding position in the lower summary display area displays the content of the instant messaging message. The prompt information "Last Sent" is used to prompt the user that the summary information displayed in each lower summary display area is arranged in order of the sending time of the corresponding instant messaging message.

[0350] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0351] The following describes a situation in which a client displays summary information in the form of a canvas card. When the client displays summary information in the form of a canvas card, the client sets up a canvas view display area in the display area. Specifically, as shown in FIG. 24, when the client displays summary information in the form of a canvas card, the display area includes a display scale adjustment control 2110, a display mode switching control 2120, a search control 2130, a label domain display area 2140, a canvas view 2150, and at least one canvas card. For the description of other parts of FIG. 24, please refer to the above embodiment and no further explanation will be given here.

[0352] The display scale adjustment control 2110 is used to adjust the display scale of the canvas view 2150, and includes a zoom out control 2111, a zoom in control 2112, and a scale display area 2113. The zoom out control 2111 is used to decrease the display scale of the canvas view 2150, the zoom in control 2112 is used to increase the display scale of the canvas view 2150, and the scale display area 2113 is used to display the current display scale of the canvas view 2150.

[0353] The display mode switching control 2120 is used to switch the display mode of the summary information by the client. In the embodiment shown in Fig. 24, the display mode switching control 2120 includes a canvas card display control 2121 and a list display control 2122. When the canvas card display control 2121 is in a triggered state and the list display control 2122 is in an untriggered state, the client is currently displaying the summary information in a canvas card format.

[0354] The search control 2130 is used to search for corresponding objects and / or abstract information based on keywords entered by the user. When a user wants to obtain certain abstract information or objects that have a keyword, the user can enter the keyword in the search control 2130. Correspondingly, the client can search for objects and / or abstract information that match the keyword.

[0355] For a detailed explanation of the label domain display area 2140, please refer to the above, and no further explanation will be given here.

[0356] The canvas view 2150 can group information blocks displayed on the canvas card according to user operations. For a detailed description of the canvas view 2150, please refer to the examples in Figures 25 and 26 below, and further details will not be provided here.

[0357] In an embodiment of the present application, the display area of ​​the client may include one or more label canvas cards, and each canvas card is used to display corresponding summary information of an object. Hereinafter, the display area will be described as including a canvas card 2160 as an example.

[0358] As shown in FIG. 24 , the canvas card 2160 includes a summary avatar display area 2161, a summary content display area 2162, and an object information display area 2163. The summary avatar display area 2161 is used to display the avatar of the user who sent the instant messaging message. The summary content display area 2162 displays the specific content of the instant messaging message. The object information display area 2163 displays other information of the instant messaging message. For example, in the embodiment of FIG. 24 , the object information display area 2163 displays the sending time of the instant messaging message. Here, FIG. 24 is merely an example to make the canvas card easier to understand and is not intended to limit the specific aspects of the canvas card.

[0359] In the embodiment of the present application, there is a partition area between different canvas cards to distinguish the corresponding summary information of different objects. As shown in Fig. 24, the background color of the canvas card 2160 is different from that of other parts. In this way, the user can determine that the card display area 2160 is used to display summary information based on the color information of the card display area.

[0360] As can be seen from the above introduction, a label creator can set the view permission and / or edit permission for a label. Correspondingly, after receiving a label view operation, the client can determine whether the logged-in user has the view permission for the label. If the user does not have the view permission for the label, the client may not display the information block of the object that has the label. If the user has the view permission for the label, the client may not respond to the user's edit operation. For example, in the embodiment shown in FIG. 24, if the user does not have the edit permission for the label "Having a meeting" but only has the view permission, the client may display the canvas view shown in FIG. 24 and prohibit the user from performing operations such as grouping on the information block in the canvas view.

[0361] Herein, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment, and the combined solution also falls within the protection scope of the embodiments of the present disclosure.

[0362] The above describes a method in which a client displays a label and summary information of at least one object having the label to a user. Correspondingly, in the interface displaying the summary information, the user can operate the label or the summary information. In the embodiment of the present application, the user's operations on the label or the summary information may include a detailed check operation, a delete operation, and a grouping operation. The following provides a detailed description.

[0363] First, the detailed check operation will be introduced.

[0364] In actual application scenarios, the client is limited by the size of the display area and cannot display all the information or all the summary information of the object, so the user cannot find the content he or she wants to see from the information displayed on the client.

[0365] Therefore, the client can associate the summary information of the object with the object, or associate the summary information with the interface corresponding to the object. In this way, when a user wants to check detailed information of an object, the client can display the object or the interface corresponding to the object according to the detailed check operation triggered by the user.

[0366] For example, assuming that the objects displayed on the client include a first object, the client can pre-record a correspondence between the summary information of the first object and the first object, or a correspondence between the summary information of the first object and an associated interface of the first object. When a user wants to check detailed information of the first object, the user can trigger an operation on the summary information of the first object. In response to the user's trigger operation, the client can jump to an interface associated with the first object or display the first object.

[0367] The deletion operation is explained below.

[0368] When a user wants to delete a label for an object, the user can trigger a delete operation on the label. Correspondingly, the client can delete the association relationship between the object and the label according to the accepted delete operation. Preferably, when the user triggers the delete operation on the label detail page of the first label, the client accepts the user's delete operation on the first object. Because the current interface corresponds to the first label, the client can determine that the delete operation targets the first object and the first label, and delete the association relationship between the first object and the first label.

[0369] In an embodiment of the present application, a user may control a client to delete the correspondence between the label and all objects by triggering a delete operation on the label. For example, in the label display interface shown in FIG. 18 , a user can trigger a delete operation on a first label. After accepting the delete operation, the client can delete the first label and clear the correspondence between the first label and all objects. Preferably, the user can control the client to display a label delete control by clicking or long-pressing the first label 1851 with the right key, and can trigger the delete operation using the label delete control.

[0370] The grouping operation will be explained below.

[0371] In a practical application scenario, different objects may have the same label. If there are a large number of these objects, it may be difficult for the user to directly find the desired object. To solve this problem, the user can trigger a grouping operation. Correspondingly, the client groups one or more of one or more objects having the same label according to the grouping operation. In this way, objects having the same characteristics are grouped together, allowing the user to find the desired object more quickly.

[0372] Preferably, when creating a group, the client obtains a label group name. Based on the label group name, the client (or server) can create a correspondence between the label, the grouping object, and the label group name. In this way, based on the label group name, the user or client can determine the group to which the object belongs. For example, assuming that the user divides object X and object Y under label A into one group, the user can set the label group name of the group to "first group." Correspondingly, the client or server can record the correspondence between label A, first group, and object X, as well as the correspondence between label A, first group, and object Y.

[0373] For details on how clients obtain label group names, please refer to the following, and we will not go into detail here.

[0374] Below, we will introduce the grouping process for objects using an example where a client displays summary information in a canvas card format.

[0375] When a user wants to group objects, the user drags a canvas card containing the corresponding summary information of the objects to the canvas view. The client can determine a group to which the object corresponding to the summary information on the canvas card belongs based on the position of the canvas card in the canvas view. For example, the client can determine a group to which the object corresponding to the summary information on the canvas card belongs based on the distance between the canvas card and other canvas cards.

[0376] For example, if a user wants to add an object to a group, for example, if the user wants to add canvas card 2160 in FIG. 24 to a group called "Meeting X," the user can select canvas card 2160 and drag canvas card 2160 to canvas view 2150. If the client detects that canvas card 2160 has been newly added to canvas view 2150 and that the boundary of canvas view 2160 does not overlap with the boundary of an existing group area, the client can determine that the user has created a new group for canvas card 2160 and displays a new canvas card corresponding to canvas card 2160 in canvas view 2150. In this way, the display area of ​​the client, as shown in FIG. 25, includes canvas view 2150, which includes a first group display area 2151. The boundary of first group display area 2151 is 2151-1 and includes a name display area 2151-2 and a canvas card 2151-3.

[0377] The name display area 2151-2 is used to display a group name corresponding to the first group display area 2151. In the example shown in FIG. 25, the group name of the first group display area 2151 is "Meeting X." Preferably, when a new group X is created, the client displays a name input box, and the data entered by the user in the name input box can be used as the group label name. The canvas card 2151-3 is a new canvas card corresponding to the canvas card 216, and displays the same or similar summary information as the canvas card 2160. Thus, in the example shown in FIG. 25, the canvas card 2151-3 indicates that the instant messaging message "I have a meeting today at 1 PM" sent by leader A belongs to a group called "Meeting X" with a label "I have a meeting."

[0378] In an embodiment of the present application, the client can determine the group of the dragged canvas view based on whether the dragged canvas card overlaps with a group display area in the canvas view. For example, if the user drags the canvas card to a position where it overlaps with the first group display area 2151, it indicates that the user will add the new canvas card to a group called "Group X." If the user drags the canvas card to a position in the canvas view 2150 where it does not overlap with the first group display area 2151, it indicates that the user will not add the new canvas card to a group called "Group X."

[0379] Preferably, the client can determine whether a canvas card overlaps with a group display area by determining whether a boundary of the canvas card intersects with a boundary of the group display area. For example, if the boundary of a canvas card dragged to the canvas view 2150 intersects with the boundary 2151-1, the client can determine that the canvas card overlaps with the first group display area 2151. If the boundary of the canvas card dragged to the canvas view 2150 does not intersect with the boundary 2151-1, the client can determine that the canvas card does not overlap with the first group display area 2151.

[0380] Correspondingly, after the canvas card 2160 is moved to the canvas view 2150, the client can display the canvas card 2220 at the position where the canvas card 2160 was displayed. The sending time of the instant messaging message corresponding to the canvas card 2220 is next to the sending time of the instant messaging message corresponding to the canvas card 2160.

[0381] After the user operates multiple times, the display interface of the client includes a group symbol 2310, a canvas card 2320, a canvas card 2330, and a canvas 2340, as shown in Fig. 26. The group symbol 2310 is used to prompt the user that the canvas card 2320 and the canvas card 2330 on the right side of the display area are ungrouped canvas cards. The canvas card 2320 and the canvas card 2330 are used to display summary information of an object with a label "I have a meeting."

[0382] In the example shown in FIG. 26, the canvas view 2340 includes a first group 2341 and a second group 2342, and the boundary of the first group is 2341-1 in the drawing, and the boundary of the second group 2342 is 2342-1. The boundary of a group is the outer border of the group in the canvas view, and labels within the border belong to the same group. As can be seen from FIG. 26, the label "I have a meeting" includes at least two groups, one group's label group name is "Meeting X" and the other group's label group name is "Meeting Y". The group "Meeting X" includes an instant messaging message sent by leader A saying "I have a meeting today at 1 PM" and an instant messaging message sent by leader A saying "The topic of the meeting is..." A group called Meeting Y includes an instant messaging message sent by Leader B saying, "There is a meeting tomorrow at 10:00 AM," an instant messaging message sent by Colleague C saying, "The topic of tomorrow morning's meeting is...," and an instant messaging message sent by Colleague D saying, "The location of tomorrow morning's meeting is...."

[0383] Of course, in some possible implementations, a user may divide a group into multiple subgroups, each containing one or more objects. The specific division method is similar to the above method, and is not detailed here. However, if there is no contradiction, the method described in this embodiment may be combined with the method described in the above embodiment. The combined solution also falls within the scope of protection of the embodiments of the present disclosure.

[0384] 27 is a structural diagram of an information interaction device provided by an embodiment of the present application. This embodiment is applied to the situation of adding a target label to a target object in a client. The device specifically includes: a receiving module 2410 and a generating module 2420.

[0385] The receiving module 2410 receives a label adding operation triggered by a user for a target object, and the generating module 2420 generates a correspondence according to the label adding operation, where the correspondence includes a correspondence between a target label and the target object.

[0386] The information interaction device provided by the embodiments of the present disclosure can implement the information interaction method provided by any embodiment of the present disclosure, and can have corresponding functional modules and beneficial effects for implementing the information interaction method. Here, in the above-mentioned embodiments of the information interaction device, the included units and modules are only divided according to functional logic and are not limited to the above divisions, as long as they achieve corresponding functions, and the specific names of the functional units are only used to distinguish them from each other and do not limit the protection scope of the present disclosure.

[0387] FIG. 28 is a structural schematic diagram of a label checking device provided by an embodiment of the present application. This embodiment is applied to the situation of checking labels at a client. The device specifically includes a receiving module 2510 and a display module 2520.

[0388] The receiving module 2510 receives a label check operation triggered by a user on a label check control, and the display module 2520 displays at least one label according to the label check operation.

[0389] The label checking device provided by the embodiments of the present disclosure can perform the label checking method provided by any embodiment of the present disclosure and can be equipped with corresponding functional modules and beneficial effects for performing the label checking method.

[0390] Here, in the above-mentioned embodiment of the label checking device, each unit and module included is simply divided according to functional logic and is not limited to the above division, as long as it achieves the corresponding function, and the specific names of each functional unit are used only for the purpose of distinguishing each other, and do not limit the scope of protection of the present disclosure.

[0391] For details of the electronic device provided by the embodiments of the present disclosure, please refer to the relevant content of the following Figure 42. The electronic device belongs to the same inventive concept as the information interaction method and label checking method provided by the above embodiments, and for technical details not described in detail in the embodiments of the present disclosure, please refer to the above embodiments, and the embodiments of the present disclosure have the same beneficial effects as the above embodiments.

[0392] An embodiment of the present disclosure provides a computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the information interaction method or label checking method provided by the above embodiment.

[0393] According to one or more embodiments of the present disclosure, [Example 1] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user on a target object; and generating a correspondence relationship according to the label addition operation, the correspondence relationship including a correspondence relationship between a target label and the target object.

[0394] According to one or more embodiments of the present disclosure, [Example 2] provides a method of information interaction, and optionally, the target label is created by another user different from the user.

[0395] According to one or more embodiments of the present disclosure, [Example 3] provides a method for information interaction, and optionally, the step of accepting a label addition operation triggered by the user on a target object includes a step of accepting a label addition operation triggered by the user on a label addition control of the target object.

[0396] According to one or more embodiments of the present disclosure, [Example 4] provides a method for information interaction, and optionally, before accepting a label addition operation triggered by a user on a label addition control of a target object, the method further includes a step of accepting a selection operation triggered by the user on the target object, and a step of displaying the label addition control according to the selection operation of the target object.

[0397] According to one or more embodiments of the present disclosure, [Example 5] provides a method for information interaction, and optionally, before accepting a label addition operation triggered by a user on a label addition control of a target object, the method further includes a step of accepting a display operation of the label addition control triggered by the user, and a step of displaying the label addition control according to the display operation.

[0398] According to one or more embodiments of the present disclosure, [Example 6] provides a method for information interaction, and optionally, the step of obtaining a target label determined by the user according to the label adding operation includes the steps of displaying at least one candidate label according to the label adding operation, wherein the at least one candidate label includes the target label; accepting a user's selection operation for the target label; and determining the target label according to the selection operation.

[0399] According to one or more embodiments of the present disclosure, [Example 7] provides a method for information interaction, and optionally, the step of displaying at least one candidate label in accordance with the label addition operation includes the steps of displaying a label input box in accordance with the label addition operation, receiving keywords entered by a user in the label input box, and displaying at least one candidate label matching the keywords.

[0400] According to one or more embodiments of the present disclosure, [EXAMPLE 8] provides a method of information interaction, wherein optionally, the at least one candidate label is arranged according to a predetermined rule.

[0401] According to one or more embodiments of the present disclosure, [Example 9] provides a method for information interaction, and optionally, the predetermined rules include one or more of a label creation time, a label access time, and a matching degree between the keywords.

[0402] According to one or more embodiments of the present disclosure, [Example 10] provides a method for information interaction, and optionally, after obtaining a target label determined by the user according to the label adding operation, the method further includes a step of displaying prompt information, wherein the prompt information is used to indicate that the addition of the target label to the target object has been completed.

[0403] According to one or more embodiments of the present disclosure, [Example 11] provides a method for information interaction, and optionally, after obtaining a target label determined by the user according to the label adding operation, the method further includes a step of accepting a label checking operation on the target object triggered by the user, and a step of displaying the target label according to the checking operation.

[0404] According to one or more embodiments of the present disclosure, [Example 12] provides a method for information interaction, and optionally, after obtaining a target label determined by the user according to the label adding operation, the method further includes the steps of: displaying a content check control; accepting a check operation triggered by the user on the content check control; and displaying an object corresponding to the target label according to the check operation.

[0405] According to one or more embodiments of the present disclosure, [Example 13] provides a method for information interaction, optionally wherein the correspondence between the target label and the target object includes a correspondence between the target label and an information block of the target object, and the information block is generated based on the target object.

[0406] According to one or more embodiments of the present disclosure, [Example 14] a method of information interaction is provided, optionally further comprising a step of jumping to an interface including the target object in response to a trigger operation on the information block, and / or a step of displaying the target object in response to a trigger operation on the information block.

[0407] According to one or more embodiments of the present disclosure, [Example 15] provides a method for information interaction, optionally including the steps of: before accepting a label addition operation triggered by a user on a target object, accepting an addition operation triggered by the user on the target label and displaying at least one candidate object according to the addition operation; and determining a candidate object selected by the user from the at least one candidate object as the target object.

[0408] According to one or more embodiments of the present disclosure, [Example 16] a method of information interaction is provided, and optionally, the at least one candidate object is categorized and displayed according to a label domain from which the candidate object originates.

[0409] According to one or more embodiments of the present disclosure, [Example 17] provides a method for information interaction, optionally including a step of accepting a user's authority setting operation for the target label and determining a user who has operation authority to operate the target label according to the authority setting operation, wherein the operation authority includes editing authority and / or checking authority.

[0410] According to one or more embodiments of the present disclosure, [Example 18] provides a method for information interaction, and optionally, the editing authority and / or checking authority of the target label includes: All members within the organization can edit, or added collaborators can edit, other members can check, or only added collaborators can edit or check, where the collaborators are users who jointly edit the information block of the target label.

[0411] According to one or more embodiments of the present disclosure, [Example 19] provides a method of information interaction, optionally comprising, in response to the user setting permissions for the target label so that the added collaborator can edit it and other members can check it, the method: The method further includes a step of acquiring information about the collaborator determined by the user.

[0412] According to one or more embodiments of the present disclosure, [Example 20] provides a method for information interaction, optionally further including a step of accepting a delete operation by the user on the target label, and a step of deleting the target label according to the delete operation.

[0413] According to one or more embodiments of the present disclosure, [Example 21] provides a method for information interaction, and optionally, the correspondence includes a correspondence between the target label, an information block of the target object, and information of the user.

[0414] According to one or more embodiments of the present disclosure, [Example 22] provides a method of information interaction, and optionally, the target object includes at least one of a cloud document, a schedule, a task, an instant messaging message, and a group chat IM message.

[0415] According to one or more embodiments of the present disclosure, [Example 23] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user on a target cloud document; obtaining a target label determined by the user according to the label addition operation; and generating a correspondence between the target cloud document and the target label.

[0416] For the relevant content of this embodiment, please refer to the above.

[0417] According to one or more embodiments of the present disclosure, [Example 24] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user for a target schedule; obtaining a target label determined by the user according to the label addition operation; and generating a correspondence relationship between the target label and the target schedule.

[0418] For the relevant content of this embodiment, please refer to the above.

[0419] According to one or more embodiments of the present disclosure, [Example 25] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user for a target instant messaging (IM) message; obtaining a target label determined by the user according to the label addition operation; and generating a correspondence between the target label and the target IM message.

[0420] For the relevant content of this embodiment, please refer to the above.

[0421] According to one or more embodiments of the present disclosure, [EXAMPLE 26] a method of information interaction is provided, optionally wherein the targeted IM message comprises a single chat IM message or a group chat IM message.

[0422] According to one or more embodiments of the present disclosure, [Example 27] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user for a target instant messaging IM group; obtaining a target label determined by the user according to the label addition operation; and generating a correspondence between the target label and the target IM group.

[0423] For the relevant content of this embodiment, please refer to the above.

[0424] According to one or more embodiments of the present disclosure, [Example 28] provides a method for information interaction, the method including: accepting a label addition operation triggered by a user for a target task; obtaining a target label determined by the user according to the label addition operation; and generating a correspondence between the target label and the target task.

[0425] For the relevant content of this embodiment, please refer to the above.

[0426] According to one or more embodiments of the present disclosure, [Example 29] a label check method is provided, the method including: accepting a label check operation triggered by a user on a label check control; and displaying at least one label according to the label check operation.

[0427] According to one or more embodiments of the present disclosure, [Example 30] a label checking method is provided, and optionally, the at least one label includes one or more of a label created by the user, a label created by another user different from the user, and for which the user has check authority.

[0428] According to one or more embodiments of the present disclosure, [Example 31] a label check method is provided, optionally further comprising: accepting a sorting trigger operation by the user on a sorting control; and displaying a sorting result corresponding to the sorting operation triggered by the sorting trigger operation.

[0429] According to one or more embodiments of the present disclosure, [Example 32] a label checking method is provided, and optionally, the sorting operation is used to sort labels displayed on a target interface according to an attribute value of at least one attribute.

[0430] According to one or more embodiments of the present disclosure, [Example 33] provides a label checking method, and optionally, the at least one attribute includes one or more of user-owned, other-user-owned, and ownership-unrestricted.

[0431] According to one or more embodiments of the present disclosure, [Example 34] provides a label checking method, and optionally, the step of accepting a label checking operation triggered by the user on a label checking control further includes a step of accepting a label checking operation triggered by the user on a label checking control associated with and displayed on a target object, and the step of displaying at least one label in accordance with the label checking operation includes a step of displaying at least one label of the target object in accordance with the label checking operation.

[0432] According to one or more embodiments of the present disclosure, [Example 35] provides a label check method, optionally wherein the at least one label includes a first label, and the method further includes accepting a check operation on the first label triggered by the user, and displaying an information block of at least one object having the first label.

[0433] According to one or more embodiments of the present disclosure, [Example 36] a label checking method is provided, wherein, optionally, information blocks of at least one object having the first label are classified and displayed according to the label domain from which the object originates.

[0434] According to one or more embodiments of the present disclosure, [Example 37] a label checking method is provided, and optionally, the label domain includes one or more of a task, a schedule, a cloud document, an instant messaging message, and an instant messaging group.

[0435] According to one or more embodiments of the present disclosure, [EXAMPLE 38] a label checking method is provided, wherein optionally, each information block of the at least one object is displayed in the form of a list or a canvas card.

[0436] According to one or more embodiments of the present disclosure, [Example 39] a label checking method is provided, optionally further comprising: accepting a grouping operation triggered by the user for at least one object having the first label; and grouping one or more objects of the at least one object according to the grouping operation.

[0437] According to one or more embodiments of the present disclosure, [Example 40] provides a label checking method, optionally further comprising: obtaining a label group name, wherein the label group name is used to generate a correspondence relationship, the correspondence relationship being a correspondence relationship between the first label, an object of the grouping, and the label group name.

[0438] According to one or more embodiments of the present disclosure, [Example 41] provides a label checking method, optionally, wherein the at least one object includes a first object, an information block of the first object is displayed in a first canvas card, and the step of accepting a grouping operation triggered by the user for at least one object of the first label includes a step of accepting a drag operation in which the user drags the first canvas card into a first group in a canvas view.

[0439] According to one or more embodiments of the present disclosure, [Example 42] provides a label checking method, optionally wherein the at least one object includes a first object, and the method further includes, in response to a trigger operation on an information block of the first object, jumping to an interface of the first object associated with the information block, and / or displaying the first object in response to a trigger operation on the information block of the first object.

[0440] According to one or more embodiments of the present disclosure, [Example 43] provides a label checking method, optionally, wherein at least one object of the first label includes a first object, and the method further includes a step of deleting a correspondence between the first object and the first label in response to receiving a label deletion operation from the user for the first object.

[0441] According to one or more embodiments of the present disclosure, [Example 44] a label checking method is provided, and optionally, the step of displaying at least one label according to the label checking operation includes the step of displaying the at least one label and creator information of each of the at least one label according to the label checking operation.

[0442] According to one or more embodiments of the present disclosure, [Example 45] provides a label checking method, optionally wherein the at least one label includes a second label, the second label being created by a user different from the user and the user does not have the authority to check, and the method further includes: accepting an authority claiming operation for the second label triggered by the user; and sending an authority claiming request to a user corresponding to the second label according to the authority claiming operation, wherein the authority claiming request requests the authority to check the second label.

[0443] According to one or more embodiments of the present disclosure, [Example 46] provides a label checking method, optionally further including: accepting a favorite operation triggered by the user on a target label among the at least one label; and adding the target label to favorites according to the favorite operation.

[0444] According to one or more embodiments of the present disclosure, [Example 47] a label check method is provided, optionally further comprising: accepting a check operation triggered by the user on a favorited label control; and displaying favorited labels among the at least one label according to the check operation.

[0445] According to one or more embodiments of the present disclosure, there is provided a label checking method, wherein, optionally, the at least one label is sorted according to a predetermined rule.

[0446] According to one or more embodiments of the present disclosure, [Example 49] a label checking method is provided, and optionally, the predetermined rules include one or more of a label access time, a label creation time, and a label priority.

[0447] According to one or more embodiments of the present disclosure, [Example 50] a label checking method is provided, the method including: accepting a label checking operation triggered by a target user on a label checking control of a target cloud document; and displaying at least one label of the target cloud document according to the label checking operation.

[0448] For the relevant content of this embodiment, please refer to the above.

[0449] According to one or more embodiments of the present disclosure, [Example 51] provides a label checking method, the method including: accepting a label checking operation triggered by a target user on a label checking control of a target schedule; and displaying at least one label of the target schedule according to the label checking operation.

[0450] For the relevant content of this embodiment, please refer to the above.

[0451] According to one or more embodiments of the present disclosure, [Example 52] a label checking method is provided, the method including: accepting a label checking operation triggered by a target user on a label checking control of a target task; and displaying at least one label of the target task according to the label checking operation.

[0452] For the relevant content of this embodiment, please refer to the above.

[0453] According to one or more embodiments of the present disclosure, [Example 53] a label checking method is provided, the method including: accepting a label checking operation triggered by a target user on a label checking control of a target instant messaging (IM) message; and displaying at least one label of the target IM message according to the label checking operation.

[0454] For the relevant content of this embodiment, please refer to the above.

[0455] According to one or more embodiments of the present disclosure, [Example 54] a label checking method is provided, the method including: accepting a label checking operation triggered by a target user on a label checking control of a target instant messaging IM group; and displaying at least one label of the target IM group according to the label checking operation.

[0456] For the relevant content of this embodiment, please refer to the above.

[0457] According to one or more embodiments of the present disclosure, [Example 55] an information interaction device is provided, the device including: a receiving module that accepts a label addition operation triggered by a user on a target object; and a generating module that generates a correspondence relationship according to the label addition operation, the correspondence relationship including a correspondence relationship between a target label and the target object.

[0458] According to one or more embodiments of the present disclosure, [Example 56] a label check device is provided, the device including: a receiving module that accepts a label check operation triggered by a user on a label check control; and a display module that displays at least one label according to the label check operation.

[0459] According to one or more embodiments of the present disclosure, [Example 57] an electronic device is provided, the electronic device including one or more processors and a memory storing one or more programs, the one or more programs, when executed by the one or more processors, causing the one or more processors to realize an information interaction method or a label checking method described in any one of the embodiments of the present application.

[0460] According to one or more embodiments of the present disclosure, [Example 58] a computer-readable storage medium having a computer program stored thereon is provided, which, when executed by a processor, realizes the information interaction method or label checking method described in any one of the embodiments of the present application.

[0461] How to integrate and manage information related to a project is currently an unsolved problem. The inventors of the present application have discovered that for a certain project, by integrating related information of the project, users (e.g., project managers, project participants) can determine information related to the project by labeling the information related to the project and integrating the information related to the project by the labels.

[0462] To prevent project information from being leaked during the project development stage, permissions can be set for labels related to the project, and only users with label permissions can perform corresponding operations on the labels.

[0463] Currently, label authority is tightly coupled with the authority of the information bearing that label, but this approach does not meet practical needs. For example, if information 1 is assigned label 1 and user 1 has label authority for label 1, user 1 also has the corresponding authority to view information 1. However, this approach does not effectively protect information security. This is because, although multiple organizations participate in the development of the same project, the priorities of the different organizations may differ. Accordingly, information with high confidentiality requirements can, in principle, only be viewed by members of the organization that created the information. Also, for example, if information 1 is assigned label 1 and user 1 does not have label authority for label 1, user 1 cannot view information 1. However, if the authority settings for label 1 are strict and information 1 itself does not have special confidentiality needs, this approach is unfavorable for information sharing.

[0464] In view of this, the embodiments of the present application further provide an information processing method that can realize the management of information related to a project. Various non-limiting embodiments of the present application will be described in detail below in conjunction with the drawings.

[0465] Exemplary Methods Please refer to FIG. 29, which is a flow diagram of an information processing method provided by an embodiment of the present application.

[0466] The method provided by the embodiments of the present application can be performed by a first device, and the first device may be a client or a service terminal, which is not specifically limited in the embodiments of the present application.

[0467] In an embodiment of the present application, a target application program is installed on the first device, and the first user referred to in the embodiment of the present application is a user corresponding to an account that logs in to the target application program on the first device.

[0468] Unless otherwise stated, information referred to in the embodiments of the present application, such as first information, second information, third information, or target information, may be one of a task, a schedule, a message, a document, a chat group, etc. An information unit referred to in the embodiments of the present application may be one of a task, a schedule, a message, a document, a chat group, etc. In some scenarios, "information unit" and "information" may be used interchangeably.

[0469] In the embodiments and drawings of the present application, "#" is a label identifier, and of course, the label identifier is not limited to "#" and may be other symbols.

[0470] If there is no conflict, the method shown in FIG. 29 and the method shown in FIG. 31 below may be referenced in combination with each other.

[0471] All drawings in the embodiments of the present application, such as Figure 30, 32a to 32e, are shown only to facilitate understanding of the contents of the embodiments of the present application and do not constitute limitations on the embodiments of the present application. The pages of Figure 30, 32a to 32e may include other content, which the embodiments of the present application do not specifically limit.

[0472] In this embodiment, the method includes, for example, the following steps S301 to S302. S301: Determine a first user's authority to a first label and a check authority of the first user to first information, where the first information comprises the first label.

[0473] In the embodiment of the present application, the authority for the first user's first label and the check authority for the first user's first information may be stored in a client local corresponding to the first user, or may be stored in a service terminal of a target application program. The first device may obtain the authority for the first user's first label and the check authority for the first user's first information from a client local corresponding to the first user, or may obtain the authority for the first user's first label and the check authority for the first user's first information from a service terminal, which is not specifically limited in the embodiment of the present application. The target application program is installed in the client corresponding to the first user referred to herein.

[0474] S302: Determine display content for the first user based on the authority of the first user to a first label and the check authority of the first user to a first information.

[0475] In the embodiment of the present application, for a first label, the first label itself has an authority, and for information having the first label, for example, first information, the first information also has a corresponding check authority. The check authority of the first information and the authority of the first label are independent of each other, and the check authority of the first information referred to herein is used to indicate whether the first user has the check authority of the first information. For example, based on the check authority of the first information, it can be determined whether the first user can check the content of the first information and / or which content of the first information the first user can check.

[0476] In an embodiment of the present application, the display content for the first user takes into consideration not only the first user's check authority for the first information but also the first user's authority for the first label. This can avoid information security issues and problems that are detrimental to information sharing, which are caused by determining the display content for the first user by considering only the first user's authority for the first label. The display content for the first user mentioned herein may be displayed on a client corresponding to the first user.

[0477] In one example, the authority of the first user for the first label includes a check authority for the first user for the first label. The check authority for the first user for the first label is used to indicate whether the first user has the authority to check the related information of the first label. The related information of the first label referred to here is information having an association relationship with the first label. Correspondingly, the check authority for the related information of the first label of the first user includes, for example, but is not limited to, whether the client used by the first user can display the first label. In some application scenarios, assuming that a user has the check authority for certain information but does not have the check authority for a certain label A, when the user checks the information in the client used by the user, the information will not be displayed in association with label A.

[0478] In one example, the related information of the first label may be displayed on the related page of the first label. In this case, the first user's check authority for the first label is used to indicate whether the first user has the check authority for the related page of the first label. In this case, if the first user has the check authority for the first label, they can check the related page of the first label. If the first user does not have the check authority for the first label, they cannot check the related page of the first label.

[0479] In one example, for first information having a first label, if the first user has the authority to check the first label but does not have the authority to check the first information, it is determined that the first page displayed to the first user does not include the first information. The first page referred to here may be a page associated with the first label or another page, such as an instant messaging session interface. In other words, if the first user has the authority to check the first label but does not have the authority to check the first information, the content displayed to the first user will not include the first information. For example, if the first page is a page associated with the first label, the associated page will not include the first information. This method can effectively protect the information security of the first information.

[0480] In one example, the first page may be, for example, an instant messaging session interface, and the first information may be a file posted by another user in the instant messaging session indicated by the instant messaging session interface. Here, the first user is a user included in the instant messaging session indicated by the instant messaging session interface. In this case, if the first user does not have the corresponding permission to check a file posted by another user in the instant messaging session indicated by the instant messaging session interface, the first information is not included in the instant messaging session interface displayed on the client corresponding to the first user. For example, if the first user and a second user are both users in the instant messaging session interface, and the second user posts a document, but the first user does not have the permission to check the document, the document is not included in the instant messaging session interface displayed on the client corresponding to the first user. In one scenario, the instant messaging session indicated by the instant messaging session interface may include only the first user and the second user, or may include other users, although the embodiments of the present application are not specifically limited thereto.

[0481] In one example, when the first user has the authority to check a first label, a related page for the first label can be displayed to the first user, and the related page may include, for example, summary information for an information unit that has the first label and for which the first user has the authority to check. For example, when the first user has the authority to check a second piece of information and the second piece of information has a first label, the related page for the first label may include summary information for the information unit of the second piece of information. Correspondingly, when the first user does not have the authority to check a first piece of information, in one example, the related page for the first label displayed to the first user does not include summary information for the first piece of information. In an embodiment of the present application, the summary information for an information unit may be some information in the information unit, such as some keywords in the information unit. In another example, the related page for the first label displayed to the first user may include summary information and prompt information for the first piece of information. The prompt information is used to prompt the first user that he / she does not have the authority to check the first information, and to prompt the first user to request the authority to check the first information from the owner of the first information. In this case, in one example, the first user can request the authority to check the first information from the owner of the first information by triggering a predetermined operation on the summary information of the first information. The predetermined operation referred to here may be, for example, a click operation.

[0482] In one example, a first user may check the second information by triggering a predetermined operation on the summary information of the second information displayed on the related page. The predetermined operation triggered by the first user on the summary information of the second information may be, for example, a click operation. In one example, when the first user triggers a predetermined operation on the summary information of the second information, the first device may display the second information in response to the predetermined operation triggered by the first user on the summary information of the second information. For example, the second information may be displayed by loading a separate page on the related page. Alternatively, the second information may be displayed in a certain area on the related page, such as a sidebar. In another example, when the first user triggers a predetermined operation on the summary information of the second information, the first device may jump to a page including the second information in response to the predetermined operation triggered by the first user on the summary information of the second information. For example, if the second information is an instant messaging message, the first user can trigger a predetermined operation on the information summary of the second information and then jump to an instant messaging session interface where the instant messaging message is located. Also, for example, if the second information is a group, the first user can trigger a predetermined operation on the information summary of the second information and then jump to an instant messaging session interface corresponding to the group.

[0483] In another example, a first user has the authority to use a first label, and the first information is information in an instant messaging session. If the first user is not a user in the instant messaging session, the first user does not necessarily have the authority to check the first information. However, if the first user subsequently joins an instant messaging session that includes the first information, in some application scenarios, the first user has the authority to check the first information. In this case, the first information in the instant messaging session that has the first label is displayed in association with the first user. Displaying the first information in association with the first label means displaying the first information and displaying the association relationship between the first information and the first label. The first user can determine that the first information has the first label based on the first information that has the first label and is displayed in association with it.

[0484] As described above, a first user's check authority for a first label is used to indicate whether the first user has the authority to check information related to the first label. The information related to the first label may be displayed on a page related to the first label. Thus, in some embodiments, if the first user does not have the authority to check the first label, the content displayed to the first user does not include the page related to the first label, regardless of whether the first user has the authority to check the first information.

[0485] In one example, if the first user does not have the authority to check the first label but has the authority to check the first information, the first device can determine that the content to be displayed to the first user includes a page containing the first information. Furthermore, because the first user does not have the authority to check the first label, the page containing the first information does not display the relationship between the first information and the first label. For convenience of explanation, the "page containing the first information" is referred to as a second page. The second page includes the first information, and the first user can check the first information on the second page. However, the second page does not display the relationship between the first information and the first label. In other words, the first user can check the first information through the second page, but cannot determine that the first information includes the first label through the second page. The second page referred to herein may be, for example, an instant messaging session interface including the first user. The first information may include, for example, session messages in the instant messaging session indicated by the instant messaging session interface and / or files posted by other users in the instant messaging session indicated by the instant messaging session interface. The instant messaging session interface referred to herein may be an instant messaging interface including two users, or an instant messaging session interface including two or more users, and the embodiments of the present application are not specifically limited thereto.

[0486] The inventors of the present application have discovered that currently, when users label information, there are no particular restrictions on the labels they use. That is, for a given label, e.g., "Project A Research and Development," any user can use that label to label content they want to mark. However, this is disadvantageous for integrating related information for the project mentioned above. For example, if Team A and Team B jointly research and develop Project A, Team A and Team B may use the label "Project A Research and Development" to label related information (e.g., shared information that requires collaborative processing), and other users may also use the label "Project A Research and Development" to label related information. Therefore, when integrating information using the label "Project A Research and Development," there is a risk that other content marked by other users will also be integrated (e.g., another user may add the label "Project A Research and Development" to some information and not set access permissions for that information, or may set access permissions for that information, allowing members of Team A and / or Team B to view that information).

[0487] In view of this, in an embodiment of the present application, the authority of the first user to the first label may include, in addition to the first user's check authority to the first label, the first user's use authority to the first label, which is used to indicate whether the first user has the authority to add the first label to information.

[0488] Regarding the use authority and check authority of the first label, in one example, the use authority has a higher priority than the check authority. In other words, if the first user has the use authority of the first label, the first user necessarily has the check authority of the first label. Also, if the first user has the check authority of the first label, the first user does not necessarily have the use authority of the first label.

[0489] For the first label, the first user cannot add the first label according to his / her own subjective will, and whether the first user can use the first label is determined by the usage authority of the first label.

[0490] In one example, when a first user has the usage authority for a first label, the first user can add the first label to the target information. The following describes an implementation of adding a first label to the target information by a first user.

[0491] In one example, a first user can trigger a label addition operation on target information. After the first user triggers the label addition operation on target information, the first device can display a label addition page. The label addition page includes a character input area, and the first user inputs at least some characters included in a first label into the character input area. Correspondingly, after obtaining the characters input by the first user, the first device can provide the first user with corresponding label candidates based on the characters input by the first user and display the label candidates on the label addition page for the user to select a label to be added based on the label candidates. In one example, the label candidates include a first label. Thus, the first user can trigger a selection operation on the first label. After the first user triggers the selection operation on the first label, the first device generates a correspondence between the first label and the target information to add the first label to the target information.

[0492] In one example, a first user adds a first label to target information on a page associated with a first label. Specifically, the first user triggers an information block addition operation on the page associated with the first label, and the first device can display at least one candidate information block in response to the first user's triggered information block addition operation. The first user can select target information from the at least one displayed information block and then trigger a label addition operation for the target information. After the first user triggers the label addition operation for the target information, the first device responsively generates a correspondence between the first label and the target information, thereby realizing the addition of the first label to the target information. The first user's triggering of an information block addition operation on a page associated with the first label may be, for example, the first user entering some characters included in the target information into a character input area on the associated page.

[0493] Thus, in an embodiment of the present application, a first user can add a first label to information only if he or she has the usage authority for the first label. In one example, users within a certain team (e.g., a team for research and development project A) are permitted to use the first label, and users outside the team are not permitted to use the first label. This prevents users outside the team from adding the first label to information, which is advantageous for integrating information for project A based on the first label. Therefore, this solution is advantageous for information integration.

[0494] In one example, the first user can trigger a check operation on the first label. In one example, the first user can trigger a label check operation on label sharing information, thereby triggering a check operation on the label indicated by the label sharing information. After the first user triggers the label check operation on the label sharing information, the first device determines display content on a label-related page displayed to the first user based on the first user's check authority for the label indicated by the label sharing information. The label sharing information may be, for example, a hyperlink or a label identifier, although the embodiments of the present application do not specifically limit this. The label check operation triggered on the label sharing information may be, for example, a click operation. For specific implementations of "determining display content on a label-related page displayed to the first user based on the first user's check authority for the label indicated by the label sharing information," please refer to the relevant descriptions above regarding "the first user's check authority for the first label" and "content displayed on the first label-related page displayed to the first user," and no further details will be provided here.

[0495] The above-described label addition page can be understood in conjunction with FIG. 30, which is a schematic diagram of a label addition page provided in an embodiment of the present application. As shown in FIG. 30, after a first user inputs the character "#Q" on the label addition page, label candidates such as "All-Day Test," "Light Service," and "Confirm" as shown in FIG. 30 appear. The first label is "Light Service," and the first user can trigger a selection operation on the first label "Light Service." For example, the first user can click the first label "Light Service" to add the first label to the target information.

[0496] The embodiments of the present application further provide an information processing method, which will be introduced below in conjunction with the accompanying drawings.

[0497] Please refer to Figure 31, which is a flow diagram of an information processing method provided by an embodiment of the present application. The method of Figure 31 is executed by a first device, and the first device can be referred to the relevant description above and will not be described in detail here. The method of Figure 31 includes, for example, the following steps S401 to S402.

[0498] S401: In response to a check operation triggered by a first user on a first label, obtain a check authority of the first user on the first label, and the check authority is used to indicate whether the first user has the authority to check related information of the first label.

[0499] In one example, the first user triggers a check operation on the first label. In one example, the first user may trigger a check operation on the first label on a page including label sharing information. The label sharing information may indicate an access point to information related to the first label. In one example, the page including the label sharing information may be an instant messaging session interface. The label sharing information may be information shared by a user in the instant messaging session interface to the instant messaging session interface. In another example, the first user may search for the first label in a label management interface, and after searching for the first label, further trigger a check operation on the first label.

[0500] After a first user triggers a check operation on the first label, the first device obtains the first user's check authority on the first label in response to the check operation triggered by the first user on the first label, and determines display content for the first user based on the first user's check authority on the first label.

[0501] S402: If it is determined that the first user has the authority to check the first label, display the related information of the first label.

[0502] In one example, if the first user has the authority to check the first label, information related to the first label is displayed to the first user.

[0503] In one implementation, the related information of the first label may be displayed on the related page of the first label, so that when S402 is specifically implemented, the related page of the label is displayed.

[0504] The related page may include, for example, summary information of an information unit that has the first label and that the first user has the authority to check. For example, if the first user has the authority to check second information and the second information has a first label, the related page of the first label may include summary information of the information unit of the second information. Correspondingly, if the first user does not have the authority to check first information, in one example, the related page of the first label does not include summary information of the first information. In an embodiment of the present application, the summary information of an information unit is some information in the information unit, for example, some keywords in the information unit.

[0505] In an embodiment of the present application, information summaries of information units having the first label are categorized and displayed on the page associated with the first label according to the message domain from which each information unit originates. When the information units having the first label include a first information unit, the message domain from which the first information unit originates is used to indicate the origin of the first information unit. In one example, the message domain from which the first information unit originates is used to indicate the service provider corresponding to the first information unit. The service provider referred to here may be, for example, an instant messaging session service provider, a file service provider, etc.

[0506] The information summaries of the information units having the first label are categorized and displayed on the related page of the first label according to the message domain from which each information unit originates, which can be understood by referring to Figure 32a, which is a schematic diagram of the related page of the first label provided by an embodiment of the present application.

[0507] As shown in FIG. 32a, the relevant page includes five message domains: "Tasks," "Schedule," "Messages," "Documents," and "Chat Groups." In the relevant page shown in FIG. 32a, the message domain "Tasks" is in a selected state, and the page displays information summaries corresponding to three tasks: "Project Seminar," "Complete R&D Task 1," and "Complete R&D Task 2." Here, the content corresponding to the message domain "Tasks" shown in FIG. 32a is displayed in the form of a list. However, FIG. 32a does not limit the embodiments of the present application and is shown for ease of understanding only. In one example, the content corresponding to the message domain "Tasks" may be displayed in the form of a canvas. The user may switch the display form of the content corresponding to the option card using, for example, the controls labeled "List" and "Canvas" shown in FIG. 4a, which will not be described in detail here.

[0508] In one example, the first user may check the second information by triggering a predetermined operation on the summary information of the second information displayed on the related page. Regarding the related description portion in which the first user triggers a predetermined operation on the summary information of the second information, the related description portion of the method shown in FIG. 29 may be referred to, and will not be described in detail here.

[0509] In another example, the associated page of the first label may include summary information of the second information, as well as summary information of a third information, even if the first user does not have access permissions for the third information.

[0510] In this case, the first user can request the owner of the third information to check the third information by triggering a predetermined operation on the information summary of the third information. In one example, after checking the summary of the third information, if the first user wants to further check the specific content of the third information, the first user can request the owner of the third information to check the third information by triggering a predetermined operation on the information summary of the third information (e.g., clicking on the information summary of the third information). If the owner of the third information agrees to the request, the first user can further check the third information. The owner of the third information referred to here may be, for example, the publisher or creator of the third information.

[0511] By adopting this method, for third information, for example, third information with less strict confidentiality requirements, summary information of the third information can be displayed on the relevant page of the first label, providing the first user with an entry point for checking and requesting the third information, thereby facilitating information sharing.

[0512] As described above, the first device can determine display content for the first user based on the first user's authority to check the first label. In one example, if the first device determines that the first user does not have the authority to check the first label, it can display first prompt information. The first prompt information is used to indicate that the first user does not have the authority to check the information related to the first label. In another example, the first prompt information, in addition to indicating that the first user does not have the authority to check the information related to the first label, instructs the first user to request the owner of the first label for the authority to check the first label. In this case, if the first user wants to check the information related to the first label, they can trigger a predetermined operation on the first prompt information. The first user triggers a predetermined operation on the first prompt information. For example, after a first user clicks on the first prompt information, the first device can request the owner of the first label for permission to check the first label in response to a predetermined operation triggered by the first user on the first prompt information. If the owner of the first label agrees to the request, the first user can check information related to the first label, for example, the first device can display a page related to the first label.

[0513] 32b, which is a schematic diagram of a page provided by an embodiment of the present application. In FIG. 32b, if the first user does not have the check authority for the first label "QA", after the first user triggers a check operation for the first label, the first device may display a first prompt information saying "You do not have the check authority, click here to request the authority".

[0514] As described above, the authority of the first user to the first label includes the authority to check the first label of the first user as well as the authority to use the first label of the first user.

[0515] In one implementation, if the first user has the usage rights for the first label, the first user can add the first label to the target information. For the implementation of the first user adding the first label to the target information, please refer to the relevant description of the method shown in Figure 29 above, and no further description will be given here.

[0516] In another implementation, if the first user does not have permission to use the first label, the first device may display second prompt information on the label addition page, where the second prompt information is used to indicate that the first user does not have permission to use the first label. For example, the first user enters at least some characters included in the first label on the label addition page, and the first device displays corresponding label candidates on the label addition page, with the first label being one of the label candidates. In this case, if the first user does not have permission to use the first label, the second prompt information is displayed on the label addition page. In another example, the second prompt information can indicate that the first user does not have permission to use the first label, and can also instruct the first user to request permission to use the first label from the owner of the first label. In this case, if the first user wants to use the first label, the first user triggers a predetermined operation in response to the second prompt information. The first user triggers a predetermined operation in response to the second prompt information. For example, after a first user clicks on the second prompt information, the first device may request the owner of the first label for permission to use the first label in response to a predetermined operation triggered by the first user on the second prompt information, and if the owner of the first label agrees to the request, the first user can add the first label to target information.

[0517] 32c, which is a schematic diagram of a label adding page provided in an embodiment of the present application. As shown in Fig. 32c, after a first user inputs the character "#Q" on the label adding page, label candidates such as "All-Day Test", "Light Service", and "Confirm" in Fig. 32c appear, and for the first label candidate "Light Service", a second prompt information is further displayed saying "No authorization, click here to request authorization".

[0518] In an embodiment of the present application, the use authority and the check authority of the first label may be set by the owner of the first label. In one example, the owner of the first label can realize the authority setting for the first label by triggering an authority setting operation on the authority setting interface of the first label. After the owner of the first label triggers the authority setting operation on the authority setting interface of the first label, the first device can obtain the use authority of the first label and / or the check authority of the first label set by the owner of the first label in response to the authority setting operation. After obtaining the use authority of the first label and / or the check authority of the first label set by the owner of the first label, the first device can generate the authority setting information of the first label.

[0519] Please refer to Figure 32d, which is a schematic diagram of a label authority setting interface provided by an embodiment of the present application. The owner of the first label "QA" can set authorities for the first label using three authority setting options 401, 402, and 403 provided in Figure 32d. As described above, the priority of the use authority is higher than the priority of the check authority. Therefore, if the owner of the first label sets the authority for the first label using option 401, it indicates that all members in the organization have the use authority for the first label and the check authority for the first label. If the owner of the first label sets the authority for the first label using option 402 or 403, the owner of the first label can further set the designated user.

[0520] The owner of the first label referred to in the embodiments of the present application may be the creator of the first label. For example, if a person in charge of a certain project creates the first label for that project, the owner of the first label may be the person in charge of that project.

[0521] Furthermore, considering that project personnel may change, it is inappropriate for the previous personnel to assume the role of owner of the first label after the change. Therefore, in an embodiment of the present application, the owner status of the first label can be transferred. The historical owner of the first label can transfer the ownership of the first label to another user by performing an owner status transfer operation. In one example, the historical owner can perform the label transfer operation in the first label installation interface to designate a user as the owner of the first label. Please refer to FIG. 32e, which is a schematic diagram of a label installation interface provided in an embodiment of the present application. As shown in FIG. 32e, the historical owner of the first label "QA," e.g., user A, clicks "Transfer" in FIG. 32e to trigger the owner status transfer operation and designate a user as the new owner.

[0522] Exemplary Equipment Based on the method provided by the above embodiments, the embodiments of the present application further provide an apparatus, which will be introduced below in conjunction with the drawings.

[0523] 33, which is a structural schematic diagram of an information processing device provided in an embodiment of the present application. The device 500 specifically includes: A first determination unit 501 for determining a first user's authority to a first label and a check authority of the first user to a first information, the first information comprising the first label; and a second determination unit 502 for determining display content for the first user based on the first user's authority for the first label and the first user's check authority for the first information.

[0524] Preferably, the authority of the first user to the first label is: The first user's check authority for the first label is included, and the check authority for the first label of the first user is used to indicate whether the first user has the authority to check related information of the first label.

[0525] Preferably, the first user's check authority for the first label is used to indicate whether the first user has check authority for the related page of the first label, and the related page of the first label is used to display related information for the first label.

[0526] Preferably, the second determining unit 502: If the first user has the authority to check the first label but does not have the authority to check the first information, it is determined that the first page displayed to the first user does not include the first information.

[0527] Preferably, the second determining unit 502 determines that when the first user has the check authority for the first label and does not have the check authority for the first information, the content displayed to the first user includes a related page of the first label, and the related page of the first label is: The information unit includes summary information of the information unit having the first label, the information unit includes second information, and the first user has the authority to check the second information.

[0528] Preferably, the device comprises: a jump unit that jumps to a page including the second information in response to a predetermined operation triggered by the first user on the summary information of the second information; or The display unit further includes a display unit configured to display the second information in response to a predetermined operation triggered by the first user on summary information of the second information.

[0529] Preferably, the first page is an instant messaging session interface, and the first information is a file posted by another user in an instant messaging session indicated by the instant messaging session interface.

[0530] Preferably, the second determining unit 502: If the first user has check authority for the first label, in response to the first user joining the instant messaging session, the first information having the first label in the instant messaging session is displayed in association with the first user.

[0531] Preferably, the second determination unit 502 determines that if the first user does not have the authority to check the first label and has the authority to check the first information, the content displayed to the first user does not include the related page of the first label.

[0532] Preferably, the second determining unit 502: determining that the content to be displayed to the first user includes a second page if the first user does not have the authority to check the first label and has the authority to check the first information; The second page includes the first information, and the second page does not display an association between the first information and the first label.

[0533] Preferably, the second page comprises: an instant messaging session interface for the first user; The first information is The instant messaging session includes session messages in the instant messaging session indicated by the instant messaging session interface and / or files posted by other users in the instant messaging session indicated by the instant messaging session interface.

[0534] Preferably, the device comprises: The information sharing device further includes a third determination unit that, in response to a label check operation triggered by the first user on the label sharing information, determines display content in a label-related page to be displayed to the first user based on the first user's check authority for the label indicated by the label sharing information.

[0535] Preferably, the authority of the first user to the first label is: The first user's usage rights for the first label are included, and the first user's usage rights for the first label are used to indicate whether the first user has the authority to add the first label to information.

[0536] Preferably, the priority of the first user's use authority for the first label is higher than the priority of the first user's check authority for the first label, and when the first user has the use authority for the first label, the first user also has the check authority for the first label.

[0537] Preferably, the device comprises: In response to the first user being authorized to use the first label, and an adding unit that accepts a label adding operation triggered by the first user to target information, and adds the first label to the target information by generating a correspondence between the first label and the target information according to the label adding operation.

[0538] The above-mentioned device 500 is a device corresponding to the corresponding method in FIG. 29 provided by the above-mentioned method embodiment, so for the specific content of the device 500, please refer to the description of the method in FIG. 29 above, and no further details will be given here.

[0539] Please refer to Figure 34, which is a structural schematic diagram of an information processing device provided by an embodiment of the present application. The device 600 specifically includes, for example: an obtaining unit 601 for obtaining a check authority of a first user for the first label in response to a check operation triggered by the first user for the first label, the check authority being used to indicate whether the first user has the authority to check related information of the first label; a first display unit 602 for displaying information related to the first label if it is determined that the first user has the authority to check the first label.

[0540] Preferably, the first display unit 602 is A related page for the first label containing related information for the first label is displayed.

[0541] Preferably, the associated page of the first label is: The information unit includes summary information of the information unit having the first label, the information unit includes second information, and the first user has the authority to check the second information.

[0542] Preferably, information summaries of information units having said first label are displayed sorted on the associated page of said first label according to the message domain from which each information unit originates.

[0543] Preferably, each of the information units includes a first information unit, and a message domain from which the first information unit originates is used to indicate a service provider corresponding to the first information unit.

[0544] Preferably, the device comprises: a jump unit that jumps to a page including the second information in response to a predetermined operation triggered by the first user on the summary information of the second information; and / or The display device further includes a second display unit for displaying the second information in response to a predetermined operation triggered by the first user on summary information of the second information.

[0545] Preferably, the associated page of said first label is The information further includes summary information of a third piece of information having the first label, wherein the first user does not have the authority to check the third piece of information, and the associated page of the first label is a page displayed on a device corresponding to the first user.

[0546] Preferably, the device comprises: The information processing device further includes a first requesting unit that requests the owner of the third information for the right to check the third information in response to a predetermined operation triggered by the first user on the information summary of the third information.

[0547] Preferably, the device comprises: The display device further includes a third display unit for displaying first prompt information when it is determined that the first user does not have the authority to check the first label, the first prompt information being used to indicate that the first user does not have the authority to check the information related to the first label.

[0548] Preferably, the first prompt information is further used to prompt the first user to request the owner of the first label for the authority to check the first label.

[0549] Preferably, the device comprises: The device further includes a second request unit for requesting the owner of the first label for the right to check the first label in response to a predetermined operation triggered by the first user in response to the first prompt information.

[0550] Preferably, the device comprises: In response to the first user being authorized to use the first label, and an adding unit that accepts a label adding operation triggered by the first user to target information, and adds the first label to the target information by generating a correspondence between the first label and the target information according to the label adding operation.

[0551] Preferably, the device comprises: The fourth display unit further includes: a fourth display unit for displaying second prompt information on a label adding page if the first user does not have the authority to use the first label, the second prompt information being used to indicate that the first user does not have the authority to use the first label.

[0552] Preferably, the second prompt information is further used to prompt the first user to request the right to use the first label from the owner of the first label.

[0553] Preferably, the device comprises: The device further includes a third billing unit that bills an owner of the first label for the right to use the first label in response to a predetermined operation triggered by the first user in response to the second prompt information.

[0554] Preferably, the device comprises: The device further includes a generating unit for generating authority setting information of the first label in response to an authority setting operation triggered by an owner of the first label on an authority setting interface of the first label.

[0555] Preferably, the owner of the first label: the creator of the first label, or The first label includes at least one of the users designated by the previous owner of the first label when the owner status transfer operation is performed.

[0556] The above-mentioned device 600 is a device corresponding to the corresponding method in Figure 31 provided by the above method embodiment, so for the specific content of the device 600, please refer to the description of the method in Figure 31 above, and no further details will be given here.

[0557] An embodiment of the present application further provides an apparatus, the apparatus including a processor and a memory, the processor executing instructions stored in the memory to cause the apparatus to perform the method provided by the above method embodiment.

[0558] An embodiment of the present application further provides a computer-readable storage medium containing instructions, the instructions directing an apparatus to perform the method provided by the above method embodiment.

[0559] An embodiment of the present application further provides a computer program product, which, when executed on a computer, causes the computer to perform the method provided by the above method embodiment.

[0560] Those skilled in the art can easily conceive of other implementation solutions of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or suitable modifications of the present application, which variations, uses, or suitable modifications include common general knowledge or ordinary technical means in the art that are not disclosed in this disclosure, in accordance with the general principles of the present application. The specification and examples are exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0561] This application is not limited to the structures described above and illustrated in the drawings, and various modifications and variations can be made therein without departing from the scope thereof, which is limited only by the appended claims.

[0562] The above description does not limit the present application, but is merely a preferred embodiment of the present application, and any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should fall within the protection scope of the present application.

[0563] With the emergence of different application programs, related technologies provide a labeling function to realize information integration between different information domains. That is, by labeling information from different information domains, the labeled information can be integrated into the label page, and users can share labels to allow other users to check the information bearing the label. For example, for a certain project, the development of the project may be completed collaboratively by multiple organizations (e.g., multiple departments or multiple teams). During the development of the project, members participating in the project may generate several pieces of information related to the project, such as tasks, schedules, messages, documents, and chat groups. This information may belong to different information domains. For example, tasks, schedules, messages, documents, and chat groups belong to different information domains. Users label information from different information domains to realize information sharing between different organizations through labels. Different information domains may correspond to different service terminals or the same service terminal.

[0564] However, currently, when users create new labels or display information blocks on labels, the processing policy is relatively simple, which cannot meet the needs of users in different application scenarios. Based on this, the embodiments of the present application further provide information processing methods and information display methods, which will be described in detail below in conjunction with the drawings in the specification.

[0565] Referring to Figure 35, this figure is a schematic flow diagram of an information processing method provided by an embodiment of the present application, which is applied to a label new production scenario, and the method is executed by a processing device for new label production, which is realized in the form of software and integrated into a user's client. The client is integrated into a PC (Personal Computer) terminal or a mobile terminal. As shown in Figure 35, the method specifically includes the following steps: S501: A new label creation operation triggered by a first user is accepted.

[0566] In this embodiment, a first user creates a new label based on his / her needs, and the first user can trigger the new label creation operation through the client.

[0567] Specifically, the first user triggers a new label creation operation on the labeling page through the client. That is, when the first user just needs to create a new label, the client can trigger the new label creation operation on the label page to enter the label creation page. Alternatively, the first user triggers the new label creation operation through the labeling component. That is, when the first user needs to add a label to a target object, i.e., a certain information block, the first user can trigger the labeling component to enter the label creation page.

[0568] S502: Display a label creation page, the label creation page including a label attribute component.

[0569] After receiving the new label creation operation triggered by the first user, the client jumps to a label creation page so that the first user can create a label based on the information displayed on the label creation page. The label creation page may include a label attribute component, which is used to indicate the authority range attribute of the newly created label. Labels with different authority range attributes correspond to different authority ranges. For example, the authority range attribute may be a first attribute value or a second attribute value, where the first attribute value indicates that the label is a public label and the second attribute value indicates that the label is a private label. That is, the authority range corresponding to the first attribute value is greater than the authority range corresponding to the second attribute value. Public labels can generally be edited by all members belonging to the same organization as the first user. Private labels can only be viewed or edited by collaborators, who are added and designated by the label creator. The organization indicates the team to which the user belongs, and may be, for example, the company, department, or project team to which the user belongs.

[0570] Here, for ease of description below, this embodiment will be described using an example in which the authority range attribute is a first attribute value and a second attribute value, the first attribute value indicating that the label is a public label, and the second attribute value indicating that the label is a private label, and the above correspondence does not constitute a limitation on the specific application of the authority range attribute.

[0571] For example, as shown in FIG. 36a, the label creation page may include a label name input box 701, a label description addition component 702, a label attribute component 703, and a creation component 704. A prompt area 705 may also be included below the label attribute component 703, prompting the first user to select whether to turn on the public attribute indicated by the label attribute component 703. If the first user selects "on," the label creation page is updated, and the prompt area 705 includes a first prompt area 705-1 and a second prompt area 705-2, as shown in FIG. 36b. The first prompt area 705-1 prompts the user for the corresponding configuration of the public label. For example, "After turning on the public attribute, everyone in your organization can use it to mark and aggregate content, but everyone can only see content for which they have access permissions in the label, and the display will be different for each person." The second prompt area 705-2 informs the user that once the label is set to public, it cannot be changed, to encourage the user to make a careful selection. That is, when the first user selects the label attribute component 703 to be public, prompt information is displayed, which is used to indicate that the first label cannot be changed after being set public. Prompt information can be displayed in the label name input box 701 to prompt the user as to what information can be input in the input box. Preferably, the first user also triggers the label description component 702 to add a detailed description about the label.

[0572] Preferably, in response to the authority range attribute of the first label being a first attribute value, the system grants editing privileges for the first label to all users belonging to the same organization as the user creating the first label. The organization may refer to a team to which the user belongs, such as a company, department, or project team to which the user belongs. Alternatively, in response to the authority range attribute of the first label being a first attribute value, the system grants editing privileges for the first label to other users who have a predetermined association relationship with the user creating the first label. The other users who have a predetermined association relationship with the user creating the first label may be collaborators added by the user creating the first label. For example, if the first label is a public label, all members in the organization can edit the first label. Furthermore, to meet user needs, a collaborator addition component is added to the label creation page when the first label is a public label. A first user designates some members as collaborators through the component, and only the added collaborators have edit authority for the first label, while other members in the organization have only check authority for the first label. The edit authority means that the user can perform edit operations on the first label or the information block having the first label. Optionally, the edit operation can include deleting the label from the information block or adding the first label to the information block. The check authority means that the client can display the first label or information block to the user, but prohibits the user from editing.

[0573] If the first user does not turn on the public attribute indicated by the label attribute component 703 on the label creation page shown in FIG. 36a, the first user triggers the creation component 704 and then jumps to the add shared member page shown in FIG. 36c. This page may include a label name entered by the first user, an add shared member input box 706 (add collaborator component), a skip component 708, and a save component 707. The first user can decide whether to add a collaborator based on their own needs. If not, they can trigger the skip component 708 to directly save the label name entered by the first user. If necessary, they can add it in the input box 706. Specifically, the client receives the target user information entered by the first user in the add collaborator component and determines the target user corresponding to the target user information as a collaborator. The client accepts the first user's permission setting operation for the collaborator and determines the collaborator's operation permission for the first label according to the permission setting operation. Collaborators that can be added include, but are not limited to, a single user, a group, or a department; that is, the target user information can be a user name, a group name, or a department name. At the same time, operation permissions corresponding to the collaborator are set, including the added collaborator being able to edit and other members being able to check. Other members refer to users who belong to the same organization as the user creating the first label but are not collaborators, or only the added collaborator being able to check or edit. Here, if the added collaborator is a group, all members of the group can check or edit the label. If the added collaborator is a department, all members of the department can check or edit the label.

[0574] When the first user adds a collaborator, the shared member addition page includes a member display area 709, which displays Zhang San, the label owner, Li Si, who has review authority, Wang Wu, who has edit authority, and the group - Hangzhou Design Group, which has review authority, as shown in FIG. 36d. As can be seen from FIG. 36d, the permissions of each added collaborator can be set, for example, by prompting the user to select the corresponding permission using a pull-down menu, and the added collaborator can also be deleted. After determining the added collaborators, the first user triggers the save component 707 to save the created label and the added collaborator information.

[0575] Preferably, in general, whether the first user creates a new label on the label page or by using the labeling component, the default value of the authority scope attribute of the newly created label is the second attribute value, i.e., a private label, to ensure the user's privacy if the user forgets to make a selection.

[0576] S503: A selection operation on the label name and label attribute components input by the first user is accepted, and a first label is generated.

[0577] After the first user inputs a label name and selects a label attribute component, the client generates a first label according to the first user's operation. Preferably, to prevent the created label from overlapping with the name of an existing label, the client first performs a validity check after receiving the label name input by the first user. If there is no duplicate name for the label name input by the first user, the client generates the first label. For example, when the first user inputs a label name in the label name input box 701, the client verifies the validity of the input label name to prevent the newly created label from overlapping with the name of an existing label. If the label name input by the first user is valid, the client receives the first user's trigger for the creation component 704 to create a first label corresponding to the label name.

[0578] Preferably, to allow users to intuitively distinguish between labels with different authority range attributes, the client can determine the display format of the first label based on the authority range attribute of the first label. Specifically, if the authority range attribute of the first label is a first attribute value, i.e., if the first label is a public label, the client displays the first label on the label page in a first display format. If the authority range attribute of the first label is a second attribute value, i.e., if the first label is a private label, the client displays the second label on the label page in a second display format. The representations of the first and second display formats may be in different colors. For example, the symbol "#" of a public label may be displayed in red, and the symbol "#" of a private label may be displayed in black. Alternatively, the first and second display formats may be displayed with different display icons. For example, as shown in FIG. 37a, a public label corresponds to a first display icon 801, and a private label corresponds to a second display icon 802. Preferably, a prompt for public labels will be displayed on the label page, prompting the user that "this label is a public label, everyone can only see content they have access rights to, and the display will be different for each person," as shown in Figure 37a. Here, labels with different permission scope attributes can be displayed differently in various scenarios, such as the label page, labeling component, search, and mention.

[0579] Preferably, if the first label is a private label, the label attribute of the first label may be modified to change it to a public label. Specifically, if the authority range attribute of the first label is a second attribute value, a label attribute modification operation triggered by a first user for the first label is accepted. A label attribute modification component is displayed, and the label attribute modification component is used to instruct the modification of the authority range attribute of the first label from the second attribute value to the first attribute value. The first user's trigger operation on the label attribute modification component is accepted, and the authority range attribute of the first label is determined to be the first attribute value.

[0580] For example, as shown in FIG. 37b, a first user triggers a setup component on a label page corresponding to a first label to enter the setup page. The setup page includes a label attribute modification component 801, which the first user triggers to modify the label attributes of the first label to a public label. The setup page also includes two prompt areas, 802-1 and 802-2. Prompt area 802-1 prompts the user that once the label is modified to a public label, it cannot be changed again. That is, the user is prompted to proceed with caution because a public label cannot be changed to a private label. Prompt area 802-2 is used to prompt the user to enter a default configuration corresponding to the public label, that is, all members of the organization can check and use the label to label information blocks and add content to the label page corresponding to the label. After the first user triggers a save component 803 on the setup page, the modification takes effect, i.e., the first label is changed to a public label. At the same time, the collaborator information originally added is invalidated. Specifically, the authority range of the first label is updated in response to the authority range attribute of the first label being updated from the second attribute value to the first attribute value. For example, when the authority range attribute of the first label is the second attribute value, only collaborators have the authority to edit it. After the authority range attribute of the first label is updated to the first attribute value, all users belonging to the same organization as the user who created the first label have the authority to edit it. Furthermore, the display form of the first label also changes and is displayed in the first display form. Furthermore, if the first user does n...

Claims

1. 1. A method of information interaction performed by an electronic device, comprising: accepting a label addition operation triggered by a user on a target object; generating a correspondence according to the label adding operation, the correspondence including a correspondence between a target label and the target object; Including, the target label is used to distinguish between multiple objects having the target label according to different label domains, the label domain indicating the origin of the multiple objects; The target label has a corresponding check authority, and the check authority includes any one or more of the following when checking the target object: an authority to see the target label; an authority to check the target object; and an authority to check all target objects having the target label; A method characterized by:

2. The method of claim 1 , wherein the target label is created by a user other than the user.

3. The step of accepting a label addition operation triggered by the user on the target object includes: receiving a label addition operation triggered by a user on a label addition control of the target object; Before accepting the label addition operation triggered by the user on the label addition control of the target object, the method includes: receiving a selection operation triggered by the user on the target object, and displaying the label addition control according to the selection operation of the target object; or receiving a display operation of the label addition control triggered by the user, and displaying the label addition control according to the display operation; The method of claim 1 further comprising:

4. After receiving the label adding operation triggered by the user for the target object, the method further includes: obtaining a target label determined by the user according to the label adding operation; The step of obtaining a target label determined by the user according to the label adding operation includes: displaying at least one candidate label according to the label adding operation, wherein the at least one candidate label includes the target label; receiving a user's selection operation for the target label; determining the target label according to the selection operation; 2. The method of claim 1, comprising:

5. After receiving the label adding operation triggered by the user for the target object, the method further includes: obtaining a target label determined by the user according to the label adding operation; After obtaining the target label determined by the user according to the label adding operation, the method includes: displaying prompt information, the prompt information being used to indicate that adding the target label to the target object is complete; The method of claim 1 further comprising:

6. After receiving the label adding operation triggered by the user for the target object, the method further includes: obtaining a target label determined by the user according to the label adding operation; After obtaining the target label determined by the user according to the label adding operation, the method includes: accepting a label check operation triggered by the user on the target object; displaying the target label according to the label checking operation; The method of claim 1 further comprising:

7. After receiving the label adding operation triggered by the user for the target object, the method further includes: obtaining a target label determined by the user according to the label adding operation; After obtaining the target label determined by the user according to the label adding operation, the method includes: displaying a content checking control; accepting a check operation triggered by the user on the content check control; displaying an object corresponding to the target label according to the checking operation; The method of claim 1 further comprising:

8. The correspondence between the target label and the target object is: The method of claim 1 , further comprising: a correspondence between the target label and an information block of the target object, the information block being generated based on the target object.

9. In response to a trigger operation on the information block, jumping to an interface containing the target object; and / or displaying the target object in response to a trigger operation on the information block; 9. The method of claim 8, further comprising:

10. Before accepting the label addition operation triggered by the user on the target object, accepting an add operation triggered by the user on the target label, and displaying at least one candidate object according to the add operation; determining a candidate object selected by the user from the at least one candidate object as the target object; 2. The method of claim 1, comprising:

11. The method of claim 10 , wherein the at least one candidate object is categorized and displayed according to a label domain from which the candidate object originates.

12. receiving an authority setting operation of the user for the target label, and determining a user who has operation authority to operate the target label according to the authority setting operation; The method of claim 1 further comprising:

13. receiving a delete operation by the user for the target label; deleting the target label according to the deletion operation; The method of claim 1 further comprising:

14. The method of claim 1 , wherein the correspondence includes a correspondence between the target label, an information block of the target object, and information of the user.

15. The target object comprises at least:

10. The method of claim 1, comprising one of a cloud document, a schedule, a task, an instant messaging message, and a group chat IM message.

16. An electronic device, one or more processors; a memory for storing one or more programs; Including, An electronic device, characterized in that, when the one or more programs are executed by the one or more processors, the one or more programs cause the one or more processors to implement the method according to any one of claims 1 to 15.

17. A computer-readable storage medium having stored thereon a computer program, the computer program being adapted to implement the method of any one of claims 1 to 15 when executed by a processor.

Images