Label processing method and apparatus

Abstract

This specification provides a tag processing method and apparatus. The method is applied to a first application, which is an instant messaging application or a suite application including an instant messaging application. A specific implementation of the method includes: receiving a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first range; in response to the first user successfully subscribing to the first tag, displaying the first tag in a target area of ​​the first user's client interface, wherein the target area is used to display the tags subscribed by the first user; in response to receiving a request triggered by the first user based on the first tag displayed in the target area, displaying a set of objects visible to the first user and tagged with the first tag in the first user's client interface; wherein the objects in the object set include instant messaging sessions.

Description

Technical Field

[0001] This specification relates to the field of Internet technology, and in particular to a tag processing method and apparatus. Background Technology

[0002] With the rapid development of computer and internet technologies, various applications have emerged. To meet user needs, these applications offer increasingly richer functionalities. For example, users can send text, images, and videos through instant messaging applications, upload files to cloud servers, set schedule reminders, and so on. These applications bring great convenience to users in both work and life. However, as users use these applications, the amount of data accumulated increases significantly. This large volume of data, mixed together, can make it difficult for users to find what they need. Summary of the Invention

[0003] The embodiments described in this specification illustrate a label processing method and apparatus.

[0004] According to a first aspect, a tag processing method is provided, applied to a first application, wherein the first application is an instant messaging application or a suite application containing an instant messaging application, the method comprising: receiving a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first scope; in response to the first user successfully subscribing to the first tag, displaying the first tag in a target area of ​​the first user's client interface, wherein the target area is used to display the tags subscribed by the first user; in response to receiving a request triggered by the first user based on the first tag displayed in the target area, displaying a set of objects visible to the first user and tagged with the first tag in the first user's client interface; wherein the objects in the set of objects include instant messaging sessions.

[0005] According to a second aspect, a tag processing apparatus is provided, disposed on a client of a first application, wherein the first application is an instant messaging application or a suite application including an instant messaging application, the apparatus comprising: a receiving unit configured to receive a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first range; a first display unit configured to, in response to the first user successfully subscribing to the first tag, display the first tag in a target area of ​​the first user's client interface, wherein the target area is used to display the tags subscribed by the first user; and a second display unit configured to, in response to receiving a request triggered by the first user based on the first tag displayed in the target area, display a set of objects visible to the first user and tagged with the first tag in the first user's client interface; wherein the objects in the set of objects include instant messaging sessions.

[0006] According to a third aspect, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method as described in any of the first aspects.

[0007] According to a fourth aspect, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed in a computer, causes the computer to perform any of the methods described in the first aspect.

[0008] According to a fifth aspect, an electronic device is provided, including a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, it implements the method described in any one of the first aspects.

[0009] The tag processing method and apparatus provided in the embodiments of this specification are applied to a first application, which is an instant messaging application or a suite application including an instant messaging application. The first application first receives a request from a first user to subscribe to a first tag, where the first tag is a shared tag within a first range. If the first user successfully subscribes to the first tag, the first tag is displayed in a target area of ​​the first user's client interface. This target area is used to display the tag subscribed by the first user. If a request triggered by the first user based on the first tag displayed in the target area is received, a set of objects visible to the first user and tagged with the first tag is displayed in the first user's client interface. The objects in the object set include instant messaging sessions. Therefore, by displaying successfully subscribed first tags in the target area, users can easily trigger requests based on the first tags displayed in the target area, and the set of objects visible to the first user and tagged with the first tag is displayed in response to the request. This provides convenience for the first user to find objects tagged with the first tag and improves the efficiency of the first user's information retrieval. Attached Figure Description

[0010] Figure 1 A schematic diagram is shown illustrating one application scenario in which the embodiments of this specification can be applied;

[0011] Figure 2 A flowchart illustrating a tag processing method according to one embodiment is shown;

[0012] Figure 3A A schematic diagram showing the subscription control for the first tag "Signal-to-Noise Ratio Special" is provided;

[0013] Figure 3B This diagram illustrates how subscribed tags are displayed in "Subscribed Tags" after a successful tag subscription.

[0014] Figure 3CA schematic diagram is shown showing a set of objects that are visible to the first user and are labeled with a first tag;

[0015] Figure 4 This diagram illustrates the interface labels for displaying group sessions on the group session information editing page.

[0016] Figure 5 This diagram illustrates the display of labels on the session details page.

[0017] Figure 6 This diagram illustrates the display of labels on the conversation message preview page;

[0018] Figure 7 A schematic block diagram of a label processing apparatus according to one embodiment is shown;

[0019] Figure 8 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of this application is shown. Detailed Implementation

[0020] The technical solutions provided in this specification will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not intended to limit the invention. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in this specification can be combined with each other.

[0021] As mentioned earlier, the large amount of data accumulated in applications (such as conversations, documents, tasks, etc.) can make it difficult for users to find what they need. Therefore, this specification provides a tagging method to improve the efficiency of information retrieval for users. Figure 1 This diagram illustrates one application scenario to which the embodiments of this specification can be applied. Figure 1In the illustrated application scenario, user A's terminal device may have a first application installed. This first application can be an instant messaging application or a suite application that includes an instant messaging application. For example, it could be a collaborative office suite application that integrates one or more of the following: instant messaging application, cloud document application, audio / video conferencing application, and calendar application. Indicatively, this suite application can provide instant messaging services, calendar-related services, cloud document-related services, etc. The first application can receive a request from user A to subscribe to the first tag "XX Project Group," which is a shared tag within a first scope. After user A successfully subscribes to the first tag "XX Project Group," the first application can display the first tag "XX Project Group" in the target area 102 of user A's client interface 101. The target area 102 is used to display the tags subscribed to by user A. In this example, the tags subscribed to by user A include "XX Project Group," "Public Group," "External," "Version Group," etc. Upon receiving a request from user A triggered by the first tag "XX Project Group" displayed in target area 102, the system displays a collection of objects visible to user A and tagged with the first tag "XX Project Group" in user A's client interface 101. In this example, the object collection is displayed in area 103, and the objects in this collection include instant messaging sessions, such as one-on-one chats and group chats. This allows user A to quickly find visible objects tagged with the first tag through the first tag displayed in target area 102, thereby improving user A's efficiency in viewing information.

[0022] See also Figure 2 , Figure 2 A flowchart illustrating a tag processing method according to one embodiment is shown. This method can be executed via a first application installed on a user's terminal device. The first application can be an instant messaging application, or a suite of applications including an instant messaging application. For example, the suite of applications can provide various information services such as instant messaging services, calendar-related services, and cloud document-related services. Figure 2 As shown, this label processing method may include the following steps:

[0023] Step 201: Receive a request from the first user to subscribe to the first tag.

[0024] In this embodiment, the first application can receive a request from the first user to subscribe to a first tag. Here, the first tag can be a shared tag within a first scope. In practice, tags can be divided into personal tags and shared tags. Personal tags can be tags created and used by a user personally, tending towards personal organization and not shareable. Shared tags can be tags shared within a certain scope.

[0025] In some implementations, the first tag may include one or more of the following: system tag, interface tag, tenant tag, group sharing tag, etc.

[0026] System tags can be tags provided by the primary application itself. Taking an instant messaging application as an example, system tags could include "external," "bot," "public," "department," etc. System tags can also be tags shared by users of the instant messaging application.

[0027] Interface tags can be labels added by other business systems to newly created and / or existing sessions through interfaces provided by the first application. Here, the newly created and existing sessions can be sessions created by other business systems through interfaces provided by the first application. For example, the first application can provide an interface for business system "XX". When business system "XX" creates a new session through this interface, it can add tags such as "XX Project" or "XX Project Group" to the newly created session. Business system "XX" can also add tags such as "XX Project" or "XX Project Group" to existing sessions through this interface. Sessions can include one-on-one chats and group chats.

[0028] Tenant tags are tags created by the tenant within the first application and shared within a custom scope using the interface provided by the first application. Taking a company as an example, the first application can provide an interface for the tenant to create tags for groups or contacts within the company.

[0029] Shared tags within a group can be tags shared by members of the target group.

[0030] In some implementations, prior to step 201, in response to a first user's triggering operation on the first session, the first application can display the details page of the first session. The first session is tagged with a first tag, and the details page of the first session displays the first tag. Based on this, step 201 can be specifically performed as follows: in response to a first user's preset operation on the first tag in the details page of the first session, a request to subscribe to the first tag sent by the first user is received.

[0031] In this implementation, the first user can perform a preset operation on the first tab in the details page of the first session, such as clicking, double-clicking, or hovering, and send a request to subscribe to the first tab through the preset operation. For example, hovering the mouse over the first tab sends a request to subscribe to the first tab. With this implementation, the first user can directly send a request to subscribe to the first tab on the details page of the first session, thereby improving the efficiency of tab subscription.

[0032] In some implementations, prior to step 201, in response to the first user's triggering operation on the first session, the first application can display the details page of the first session. The first session is tagged with a first label, and the details page of the first session displays the first label. Based on this, step 201 can be specifically performed as follows:

[0033] (i) In response to a first user’s preset operation on the first tab in the details page of the first session, display a set of objects visible to the first user and marked with the first tab in a preset area, and display a subscription control for the first tab in the preset area.

[0034] In this implementation, a first user can perform a preset operation on the first tag in the details page of the first session, such as clicking. In response to this preset operation, the first application can display a collection of objects visible to the first user and tagged with the first tag in a preset area, and also display a subscription control for the first tag in the preset area. This subscription control can be used to send a tag subscription request; for example, the first user can send a subscription request by selecting the subscription control. As an example, the preset area can be a news feed display area. The news feed display area can display preview information for multiple messages.

[0035] (ii) In response to the first user's preset operation on the subscription control, receive the first user's request to subscribe to the first tag.

[0036] In this implementation, the first user can perform a preset operation on the subscription control (e.g., click, or display the subscription control after hovering the mouse and then clicking the subscription control), and send a request to subscribe to the first tag to the first application through this preset operation. With this implementation, the first user can send a request to subscribe to the first tag through the subscription control for the first tag.

[0037] Taking the first label as "signal-to-noise ratio project" as an example, such as Figure 3A As shown, Figure 3A A schematic diagram shows the subscription controls displayed for the first tab, "Signal-to-Noise Ratio Special". Figure 3A In the example shown, after the first user performs a preset operation (e.g., click operation) on the first tag "Signal-to-Noise Ratio Special" in the details page 301 of the first session, a collection of objects visible to the first user and tagged with the first tag "Signal-to-Noise Ratio Special" is displayed in the preset area 302, and a subscription control 303 for the first tag "Signal-to-Noise Ratio Special" is displayed in the preset area 302.

[0038] Step 202: In response to the first user successfully subscribing to the first tag, the first tag is displayed in the target area of ​​the first user's client interface.

[0039] In this embodiment, after the first user successfully subscribes to the first tag, the first tag can be displayed in a target area of ​​the first user's client interface. Here, the target area can be used to display all tags subscribed to by the first user.

[0040] Continue with Figure 3A For example, the first user, through... Figure 3A The display subscription control 303 performs a preset operation, such as a click operation, to send a tag subscription request. After successful subscription, the first tag "Signal-to-Noise Ratio Special" can be displayed in "Subscribed Tags". Figure 3B As shown, Figure 3B This diagram illustrates how subscribed tags are displayed in "Subscribed Tags" after a successful tag subscription. Figure 3B In the example shown, the “Subscribed Tags” are displayed in target area 102.

[0041] Step 203: In response to receiving a request triggered by the first user based on the first tag displayed in the target area, display the set of objects visible to the first user and marked with the first tag in the first user's client interface.

[0042] In this embodiment, for the first label displayed in the target area, the first user can trigger a request through the first label, for example, by performing an operation such as clicking, double-clicking, or hovering over the first label. After receiving the request, the first application can display a collection of objects visible to the first user and labeled with the first label in the client interface. As an example, the objects in the object collection may include instant messaging sessions, which may include one-on-one chats and group chats.

[0043] Continue with Figure 3B The example shown illustrates how, in response to a first user's click on the first label "Signal-to-Noise Ratio Specialized" displayed in target area 102, a set of objects labeled with the first label that are visible to the first user can be displayed on the first user's client interface. Figure 3C As shown, Figure 3C This diagram illustrates a set of objects visible to the first user and labeled with a first tag. Figure 3C In the example shown, the collection of objects is displayed in area 103.

[0044] In some implementations, objects visible to the first user may include objects in which the first user is a member or collaborator. Alternatively, objects visible to the first user, even if the first user is not a member or collaborator, may be objects in which the first user can apply to become a member or collaborator.

[0045] In some implementations, the objects in the object collection may also include one or more of the following: contacts, cloud documents, calendars, tasks, audio conferencing, video conferencing, etc.

[0046] In some implementations, the first tag may include an interface tag, which can be a tag added by other business systems to a newly created session and / or an existing session through an interface provided by the first application. Furthermore, the above tag processing method may also include the following:

[0047] S1 receives interface tag deletion requests sent by other business systems through the interface of the first application.

[0048] In this implementation, the first application can receive interface tag deletion requests sent by other business systems through interfaces provided by the first application. Here, the interface tag deletion request can be used to delete interface tags. The interface tag deletion request can include the interface tag to be deleted and the object identifier of the object already tagged with the interface tag to be deleted.

[0049] S2, based on the object identifier and the interface tag to be deleted in the interface tag deletion request, remove the interface tag to be deleted from the corresponding object.

[0050] In this implementation, the first application can first determine the object whose interface tag needs to be deleted based on the object identifier in the interface tag deletion request. Then, it deletes the interface tag of the determined object. Using this implementation, other business systems can delete interface tags through the interface provided by the first application.

[0051] In some implementations, the first tag may include an interface tag, and the above tag processing method may also include the following:

[0052] 1) Receive tag update requests sent by other business systems through the interface of the first application.

[0053] In this implementation, the first application can receive tag update requests sent by other business systems through an interface provided by the first application. Here, the tag update request can be used to update interface tags. The tag update request may include the interface tag to be updated, the object identifier of the object already tagged with the interface tag to be updated, and the updated interface tag.

[0054] 2) Based on the object identifier, the interface tag to be updated, and the updated interface tag in the tag update request, update the interface tag to be updated in the corresponding object to the updated interface tag.

[0055] In this implementation, the first application can first determine the object whose interface label needs to be updated based on the object identifier in the label update request. Then, it replaces the interface label to be updated for the determined object with the updated interface label. Through this implementation, other business systems can update interface labels using the interface provided by the first application.

[0056] In some implementations, the first tag may include an interface tag, and the above tag processing method may also include the following:

[0057] a) Receive the interface label display position sent by other business systems through the interface of the first application.

[0058] In this implementation, the first application can receive the interface label display location sent by other business systems through the interface provided by the first application. Here, the interface label display location can be used to indicate the position where the interface label is displayed. As an example, the interface label display location may include one or more of the following: group session information editing page, session details page, session message browsing page, etc.

[0059] In practice, group information (or group chats) can be edited on the group chat information editing page. This includes editing group avatars, group names, and group descriptions. For user convenience, interface labels can also be displayed on the group chat information editing page. Figure 4 As shown, Figure 4 This diagram illustrates the interface labels for displaying group sessions on the group session information editing page. Figure 4 In the example shown, users can edit the group avatar, enter the group name, and enter the group description on the group conversation information editing page 401. The interface tag can be displayed below the group description as a group tag. Figure 4 The interface labels displayed include "Signal-to-Noise Ratio Special Project" and "YY Issue Feedback". Optionally, the group conversation information editing page can also provide group label editing options to allow authorized users (e.g., group administrators) to add / remove group labels.

[0060] Various tags can also be displayed on the conversation details page, such as system tags, interface tags, personal tags, etc. Figure 5 As shown, Figure 5 This illustrates the display of labels on the session details page. Figure 5 In the example shown, a label can be displayed below the session name "L group". Figure 5 The tags displayed can include "Signal-to-Noise Ratio Special Project," "YY Issue Feedback," and so on. As an example, when a session has multiple tags, they can be displayed in the order of "System Tags > Interface Tags > Personal Tags." If there are multiple system tags, multiple interface tags, etc., they can be displayed in the order they were added.

[0061] Various tags can also be displayed on the conversation message preview page, such as system tags, interface tags, personal tags, etc. Figure 6 As shown, Figure 6 This illustrates the display of labels on the conversation message preview page. Figure 6 In the example shown, the session preview information displayed on the session message preview page 601 may include session name, tags, etc.

[0062] b) Display the interface label according to its display position.

[0063] In this implementation, the first application can display the interface label at the corresponding position based on the display position of the interface label sent by other business systems. Through this implementation, other business systems can control the display position of the interface label through the interface provided by the first application.

[0064] In some embodiments of this disclosure, a user can unsubscribe from an already subscribed first tab, for example, in Figure 3B In the target area 102, if a user right-clicks on the first tab (e.g., XX project group), a control to unsubscribe will pop up. Clicking the unsubscribe control will cancel the user's subscription to the first tab.

[0065] Reviewing the above process, in the embodiments described in this specification, the first application can first receive a request from a first user to subscribe to a first tag, which is a shared tag within a first range. If the first user successfully subscribes to the first tag, the first tag is displayed in a target area of ​​the first user's client interface, where the target area is used to display the tag subscribed by the first user. If a request triggered by the first user based on the first tag displayed in the target area is received, a set of objects visible to the first user and tagged with the first tag is displayed in the first user's client interface, wherein the objects in the object set include instant messaging sessions. Thus, by displaying successfully subscribed first tags in the target area, users can easily trigger requests based on the first tags displayed in the target area, and the set of objects visible to the first user and tagged with the first tag is displayed in response to the request, thereby facilitating the first user's search for objects tagged with the first tag and improving the efficiency of the first user's information search.

[0066] According to another embodiment, a tag processing apparatus is provided. This tag processing apparatus can be configured on a client of a first application, which is an instant messaging application or a suite application including an instant messaging application.

[0067] Figure 7 A schematic block diagram of a label processing apparatus according to one embodiment is shown. Figure 7 The device shown is used to perform Figure 2 The method shown. (As illustrated) Figure 7 As shown, the tag processing device 700 includes: a receiving unit 701 configured to receive a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first range; a first display unit 702 configured to display the first tag in a target area of ​​the first user's client interface in response to the first user successfully subscribing to the first tag, wherein the target area is used to display the tag subscribed by the first user; and a second display unit 703 configured to display a set of objects visible to the first user and tagged with the first tag in the first user's client interface in response to receiving a request triggered by the first user based on the first tag displayed in the target area; wherein the objects in the set of objects include instant messaging sessions.

[0068] In some optional implementations of this embodiment, the objects in the object set may also include one or more of the following: contacts, cloud documents, calendars, tasks, and audio / video conferencing.

[0069] In some optional implementations of this embodiment, the objects visible to the first user include: objects in which the first user is a member or collaborator; or objects in which the first user is not a member or collaborator, but which are visible to the first user and which the first user can apply to become a member or collaborator.

[0070] In some optional implementations of this embodiment, the first tag includes one or more of the following: a system tag, which is a tag provided by the first application itself; an interface tag, which is a tag added by other business systems to newly created sessions and / or existing sessions through the interface provided by the first application; a tenant tag, which is a tag created by the tenant of the first application through the interface provided by the first application and shared within a custom scope; and a group-shared tag, which is a tag shared by members of the target group.

[0071] In some optional implementations of this embodiment, the first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to a newly created session and / or an existing session through an interface provided by the first application; the device 700 further includes: a deletion request receiving unit (not shown in the figure), configured to receive an interface tag deletion request sent by the other business system through the interface of the first application, wherein the interface tag deletion request includes an interface tag to be deleted and an object identifier of an object that has been tagged with the interface tag to be deleted; and a deletion unit (not shown in the figure), configured to remove the interface tag to be deleted from the corresponding object according to the object identifier and the interface tag to be deleted in the interface tag deletion request.

[0072] In some optional implementations of this embodiment, the first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to a newly created session and / or an existing session through an interface provided by the first application; and the device 700 further includes: an update request receiving unit (not shown in the figure), configured to receive a tag update request sent by the other business system through the interface of the first application, wherein the tag update request includes an interface tag to be updated, an object identifier of an object that has been tagged with the interface tag to be updated, and an updated interface tag; and an update unit (not shown in the figure), configured to update the interface tag to be updated in the corresponding object to the updated interface tag according to the object identifier, the interface tag to be updated, and the updated interface tag in the tag update request.

[0073] In some optional implementations of this embodiment, the first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to a newly created session and / or an existing session through an interface provided by the first application; and the device 700 further includes: a location receiving unit (not shown in the figure), configured to receive the interface tag display location sent by the other business systems through the interface of the first application, wherein the interface tag display location includes one or more of the following: a group session information editing page, a session details page, and a session message preview page; and an interface tag display unit (not shown in the figure), configured to display the interface tag according to the interface tag display location.

[0074] In some optional implementations of this embodiment, the device 700 further includes: a first details page display unit (not shown in the figure), configured to display the details page of the first session in response to a triggering operation of the first user on the first session; wherein the first session is tagged with the first tag, and the details page of the first session displays the first tag; and the receiving unit 701 is further configured to receive a request from the first user to subscribe to the first tag in response to a preset operation of the first user on the first tag in the details page of the first session.

[0075] In some optional implementations of this embodiment, the device 700 further includes: a second details page display unit (not shown in the figure), configured to display the details page of the first session in response to a triggering operation by the first user on the first session; wherein the first session is tagged with the first tag, and the details page of the first session displays the first tag; and the receiving unit 701 is further configured to: in response to a preset operation by the first user on the first tag in the details page of the first session, display a set of objects visible to the first user and tagged with the first tag in a preset area, and display a subscription control for the first tag in the preset area, wherein the subscription control is used to send a tag subscription request; and in response to a preset operation by the first user on the subscription control, receive a request from the first user to subscribe to the first tag.

[0076] In some optional implementations of this embodiment, the preset area is an information flow display area.

[0077] The above-described apparatus embodiments correspond to the method embodiments, and detailed descriptions can be found in the description of the method embodiments section, which will not be repeated here. The apparatus embodiments are derived based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments; detailed descriptions can be found in the corresponding method embodiments.

[0078] According to another embodiment, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed in a computer, causes the computer to perform... Figure 2 The method described.

[0079] According to another embodiment, an electronic device is also provided, including a memory and a processor, characterized in that the memory stores executable code, and when the processor executes the executable code, it implements... Figure 2 The method described.

[0080] The foregoing description describes specific embodiments of this specification; other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than those shown in the embodiments, and the desired result may still be achieved. Furthermore, the processes depicted in the drawings do not necessarily need to follow the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0081] The following is for reference. Figure 8 It shows a structural schematic diagram of an electronic device 800 suitable for implementing embodiments of the present application. Figure 8The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0082] like Figure 8 As shown, the electronic device 800 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the electronic device 800. The processing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0083] Typically, the following devices can be connected to I / O interface 805: input devices 806 including, for example, touchscreens, touchpads, keyboards, mice, etc.; output devices 807 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 808 including, for example, magnetic tapes, hard disks, etc.; and communication devices 809. Communication device 809 allows electronic device 800 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8 An electronic device 800 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 8 Each box shown can represent a device or multiple devices as needed.

[0084] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by a processing device 801, it performs the functions defined in the methods of embodiments of this application.

[0085] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the methods described in this specification.

[0086] It should be noted that the computer-readable medium described in the embodiments of this specification may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the embodiments of this specification, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the embodiments of this specification, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (Radio Frequency), etc., or any suitable combination thereof.

[0087] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: receive a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first scope; in response to the first user successfully subscribing to the first tag, display the first tag in a target area of ​​the first user's client interface, wherein the target area is used to display the tag subscribed by the first user; in response to receiving a request triggered by the first user based on the first tag displayed in the target area, display a set of objects visible to the first user and tagged with the first tag in the first user's client interface; wherein the objects in the set of objects include instant messaging sessions.

[0088] Computer program code for performing the operations of the embodiments of this specification can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or electronic device. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0089] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for storage media and computing devices are basically similar to the method embodiments, so they are described more simply; relevant parts can be referred to the descriptions of the method embodiments.

[0090] Those skilled in the art will recognize that the functions described in the embodiments of the present invention in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium.

[0091] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, or improvements made based on the technical solutions of the present invention should be included within the scope of protection of the present invention.

Claims

1. A tag processing method, the method being applied to a first application, the first application being an instant messaging application or a suite application containing an instant messaging application, the method comprising: Receive a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first scope; In response to the first user successfully subscribing to the first tag, the first tag is displayed in a target area of ​​the first user's client interface, wherein the target area is used to display the tag subscribed by the first user, and wherein the client interface is the interface of the client of the first application; In response to receiving a request triggered by the first tag displayed by the first user based on the target area, a set of objects visible to the first user and tagged with the first tag is displayed in the client interface of the first user; wherein, the objects in the set of objects include instant messaging sessions, and the objects visible to the first user include: objects in which the first user is a member or collaborator; or, objects in which the first user is not a member or collaborator but is visible to the first user and the first user can apply to become a member or collaborator.

2. The method according to claim 1, wherein, The objects in the object set also include one or more of the following: contacts, cloud documents, calendars, tasks, and audio / video conferencing.

3. The method according to claim 1, wherein, The first tag includes one or more of the following: System tags, which are tags provided by the first application itself; Interface tags, which are tags added by other business systems to newly created sessions and / or existing sessions through the interfaces provided by the first application; Tenant tags, which are tags created within a tenant using the interface provided by the first application and shared within a custom scope; Shared tags within a group are tags shared by members of the target group.

4. The method according to claim 1, wherein, The first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to a newly created session and / or an existing session through the interface provided by the first application; The method further includes: Receive an interface tag deletion request sent by the other business systems through the interface of the first application, wherein the interface tag deletion request includes an interface tag to be deleted and an object identifier of the object that has been tagged with the interface tag to be deleted; Based on the object identifier and the interface tag to be deleted in the interface tag deletion request, remove the interface tag to be deleted from the corresponding object.

5. The method according to claim 1, wherein, The first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to newly created sessions and / or existing sessions through the interface provided by the first application; and The method further includes: Receive a tag update request sent by the other business systems through the interface of the first application, wherein the tag update request includes the interface tag to be updated, the object identifier of the object that has been tagged with the interface tag to be updated, and the updated interface tag; Based on the object identifier, the interface label to be updated, and the updated interface label in the label update request, update the interface label to be updated in the corresponding object to the updated interface label.

6. The method according to claim 1, wherein, The first tag includes an interface tag; wherein, the interface tag is a tag added by other business systems to newly created sessions and / or existing sessions through the interface provided by the first application; and The method further includes: The system receives interface tag display locations sent by other business systems through the interface of the first application, wherein the interface tag display locations include one or more of the following: group session information editing page, session details page, and session message preview page; Display the interface label according to its location.

7. The method according to claim 1, wherein, Before receiving a request from a first user to subscribe to the first tag, the method further includes: in response to a triggering operation by the first user on the first session, displaying a details page of the first session; wherein the first session is tagged with the first tag, and the details page of the first session displays the first tag; and, The process of receiving a request from the first user to subscribe to the first tag includes: In response to the first user's preset operation on the first tab in the details page of the first session, a request to subscribe to the first tab is received from the first user.

8. The method according to claim 1, wherein, Before receiving a request from a first user to subscribe to the first tag, the method further includes: in response to a triggering operation by the first user on the first session, displaying a details page of the first session; wherein the first session is tagged with the first tag, and the details page of the first session displays the first tag; and, The process of receiving a request from the first user to subscribe to the first tag includes: In response to a preset operation by the first user on a first tag in the details page of the first session, a set of objects visible to the first user and marked with the first tag is displayed in a preset area, and a subscription control for the first tag is displayed in the preset area, wherein the subscription control is used to send a tag subscription request; In response to the first user's preset operation on the subscription control, a request to subscribe to the first tag is received from the first user.

9. The method according to claim 8, wherein, The preset area is an information flow display area.

10. A tag processing apparatus, the apparatus being disposed on a client of a first application, the first application being an instant messaging application or a suite application including an instant messaging application, the apparatus comprising: The receiving unit is configured to receive a request from a first user to subscribe to a first tag; wherein the first tag is a shared tag within a first range; The first display unit is configured to display the first tag in a target area of ​​the first user's client interface in response to the first user successfully subscribing to the first tag, wherein the target area is used to display the tag subscribed by the first user, and the client interface is the interface of the client of the first application; The second display unit is configured to, in response to receiving a request triggered by the first tag displayed by the first user based on the target area, display a set of objects visible to the first user and tagged with the first tag in the client interface of the first user; wherein, the objects in the set of objects include instant messaging sessions, and the objects visible to the first user include: objects in which the first user is a member or collaborator; or, objects in which the first user is not a member or collaborator but is visible to the first user and the first user can apply to become a member or collaborator.

11. A computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method of any one of claims 1-9.

12. An electronic device comprising a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method of any one of claims 1-9.

Images