Collaborative task processing method, apparatus, device, and computer-readable storage medium

Abstract

Embodiments of the present specification provide a method, device and computer readable storage medium for processing a collaborative task, wherein the method comprises: obtaining at least one second user having a task collaboration relationship with a first user; obtaining an arrangement order of the at least one second user; and displaying an identity of the at least one second user in a collaborative task center interface of the first user according to the arrangement order. Through the embodiments, the identity of the second user having the task collaboration relationship with the first user can be displayed in the collaborative task center interface of the first user, thereby providing more information about the collaborative task for the user and improving the experience of the user in processing the collaborative task.

Description

Technical Field

[0001] This document relates to the field of communication technology, and in particular to a collaborative task processing method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] In the field of collaborative office work, task (also known as "to-do") systems are commonly used applications. Existing task systems provide users with a collaborative task center, through which users can create tasks and view all tasks related to them in the system. Currently, collaborative tasks related to a user are typically displayed in the user's collaborative task center in the order of their creation time. However, this task display method only allows users to browse related collaborative tasks, providing limited information and failing to offer users more comprehensive information about collaborative tasks. Summary of the Invention

[0003] This specification provides a collaborative task processing method, apparatus, device, and computer-readable storage medium, which can display the identifier of a second user with a task collaboration relationship with the first user in the collaborative task center interface of the first user, thereby providing the user with more information about the collaborative task and improving the user's experience in processing collaborative tasks.

[0004] Firstly, an embodiment of this specification provides a collaborative task processing method, including:

[0005] Obtain at least one second user who has a task collaboration relationship with the first user;

[0006] Obtain the arrangement order of the at least one second user;

[0007] The identifiers of at least one second user are displayed in the collaborative task center interface of the first user in the order stated.

[0008] Secondly, one embodiment of this specification provides a collaborative task processing device, comprising:

[0009] The first acquisition unit is used to acquire at least one second user who has a task collaboration relationship with the first user;

[0010] The second acquisition unit is used to acquire the arrangement order of the at least one second user;

[0011] The identifier display unit is used to display the identifiers of at least one second user in the collaborative task center interface of the first user according to the arranged order.

[0012] Thirdly, one embodiment of this specification provides an electronic device, including:

[0013] Processor; and,

[0014] A memory configured to store computer-executable instructions that, when executed by a processor, cause the processor to perform the steps of the method described in the first aspect above.

[0015] Fourthly, one embodiment of this specification provides a computer-readable storage medium for storing computer-executable instructions that, when executed by a processor, implement the steps of the method described in the first aspect above.

[0016] In this embodiment, firstly, at least one second user with a task collaboration relationship with the first user is obtained; then, the sorting order of the at least one second user is obtained; finally, the identifiers of the at least one second user are displayed in the first user's collaboration task center interface according to the sorting order. Therefore, this embodiment can display the identifiers of second users with a task collaboration relationship with the first user in the first user's collaboration task center interface, thereby providing the user with more information about the collaboration task and improving the user's experience in handling collaboration tasks. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a collaborative task processing method provided in one embodiment of this specification;

[0019] Figure 2a A schematic diagram illustrating the identifier of a second user provided for one embodiment of this specification;

[0020] Figure 2b A schematic diagram illustrating the identifier of a second user, provided for another embodiment of this specification;

[0021] Figure 2c A schematic diagram illustrating the identifier of a second user, provided for another embodiment of this specification;

[0022] Figure 3 A flowchart illustrating a collaborative task processing method provided in yet another embodiment of this specification;

[0023] Figure 4a This is a schematic diagram illustrating a display of a collaborative task provided in one embodiment of this specification;

[0024] Figure 4b A schematic diagram illustrating a collaborative task as provided in yet another embodiment of this specification;

[0025] Figure 5a A schematic diagram illustrating the creation of a source identifier for a demonstration task provided in one embodiment of this specification;

[0026] Figure 5b To and Figure 5a A diagram showing the corresponding task creation source interface;

[0027] Figure 6 This is a schematic diagram of the structure of a collaborative task processing device provided in one embodiment of this specification;

[0028] Figure 7 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this specification. Detailed Implementation

[0029] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0030] Considering that the current task system's collaborative task center can only display collaborative tasks related to the user, providing limited information and failing to offer more information about collaborative tasks, this specification provides a collaborative task processing method in one embodiment. This method can display the identifier of a second user with a task collaboration relationship with the first user in the first user's collaborative task center interface, thereby providing the user with more information about collaborative tasks and improving the user's experience in processing collaborative tasks.

[0031] It should be noted that the collaborative task center involved in the various embodiments of this specification is located in the task system. This task system can be an independent application or an application within collaborative office software. Specifically, collaborative office software is office software designed for internal personnel of an enterprise / organization. Collaborative office software generally integrates multiple applications such as instant messaging, cloud documents, audio and video conferencing, and task systems, greatly improving the efficiency of collaborative work among employees of large enterprises. Both the task system within collaborative office software and independent task systems can apply the collaborative task processing methods in the various embodiments of this specification and achieve the same results.

[0032] Figure 1 This is a flowchart illustrating a collaborative task processing method provided in one embodiment of this specification, as shown below. Figure 1 As shown, the method includes the following steps:

[0033] Step S102: Obtain at least one second user who has a task collaboration relationship with the first user;

[0034] Step S104: Obtain the arrangement order of the at least one second user;

[0035] Step S106: Display the identifiers of at least one second user in the first user's collaborative task center interface according to the arrangement order.

[0036] In this embodiment, firstly, at least one second user with a task collaboration relationship with the first user is obtained; then, the sorting order of the at least one second user is obtained; finally, the identifiers of the at least one second user are displayed in the first user's collaboration task center interface according to the sorting order. Therefore, this embodiment can display the identifiers of second users with a task collaboration relationship with the first user in the first user's collaboration task center interface, thereby providing the user with more information about the collaboration task and improving the user's experience in handling collaboration tasks.

[0037] The collaborative task processing methods in the various embodiments of this specification can be executed by a user terminal running a task system or by a background server running the system; no limitation is made here.

[0038] In step S102 above, at least one second user with a task collaboration relationship with the first user is obtained. Specifically, the first user is a registered user of the task system, and the second user may or may not be a registered user of the task system. Registered users of the task system have a corresponding collaborative task center interface in the task system, therefore the first user also has a corresponding collaborative task center interface in the task system.

[0039] In one specific embodiment, obtaining at least one second user who has a task collaboration relationship with the first user specifically involves:

[0040] (a1) Obtain at least one second user who has a task collaboration relationship with the first user within a preset time range;

[0041] or,

[0042] (a2) Based on the time information of the task collaboration relationship between the first user and the first user, obtain a preset number of second users who have a task collaboration relationship with the first user in chronological order.

[0043] In method (a1), the preset time range can be a time range preceding the current time with a preset duration up to the current time. For example, if the preset duration is 3 months, then the preset time range is the three months preceding the current time. At least one second user with a task collaboration relationship with the first user within the preset time range is obtained. The number of second users can be one or more, depending on the number of collaborative task-related operations performed by the first user in the task system within the preset time range.

[0044] In method (a2), based on the time information of the task collaboration relationship established with the first user, a preset number of second users with task collaboration relationships with the first user are obtained in chronological order. This time information can be a timestamp; for example, based on the timestamp of the task collaboration relationship established with the first user, a preset number, such as 10, of users with task collaboration relationships with the first user are obtained as second users, arranged in order of their timestamps being closest to the current time. This method can be simply understood as obtaining a preset number of users who most recently had a task collaboration relationship with the first user as second users.

[0045] As can be seen from this embodiment, a second user can be obtained from either the time range dimension or the user quantity dimension, and in specific implementation, a method can be selected to obtain the second user as needed.

[0046] In one embodiment, the arrangement order of at least one second user is obtained, which may specifically be a randomly sorted order.

[0047] In another embodiment, obtaining the arrangement order of at least one second user as described above specifically involves:

[0048] (b1) Determine the order of the at least one second user based on the user sorting elements of the at least one second user;

[0049] The user ranking elements include: the type of collaboration relationship between the second user and the first user and / or the time information of when the task collaboration relationship was established between the second user and the first user.

[0050] The collaborative relationship between a first user and a second user can be categorized into five main types, including but not limited to: task assignment, task sharing, task following, task liking, and task commenting. Each main type can be further divided into several subtypes. Specifically, the task assignment relationship includes, but is not limited to, the following subtypes: the second user is the task executor designated by the first user; the first user is the task executor designated by the second user. The task sharing relationship includes, but is not limited to, the following subtypes: the second user is the task sharing recipient designated by the first user; the first user is the task sharing recipient designated by the second user; the second user shares a task posted by the first user; the first user shares a task posted by the second user. The task following relationship includes, but is not limited to, the following subtypes: the second user follows a task posted by the first user; the first user follows a task posted by the second user. The task liking relationship includes, but is not limited to, the following subtypes: the second user likes a task posted by the first user; the first user likes a task posted by the second user. The task commenting relationship includes, but is not limited to, the following subtypes: the second user comments on a task posted by the first user; the first user comments on a task posted by the second user.

[0051] Specifically, "the second user is the task executor designated by the first user" means that the first user assigned the task to the second user. Similarly, "the first user is the task executor designated by the second user" means that the second user assigned the task to the first user. In either of these cases, a task assignment relationship exists between the first user and the second user.

[0052] The second user is the task-sharing recipient designated by the first user. This means the first user shares a task with the second user. The task can be posted by the first user themselves or by a user other than the first and second users. Similarly, the first user is the task-sharing recipient designated by the second user. This means the second user shares a task with the first user. The task can be posted by the second user themselves or by a user other than the first and second users. In either of these two scenarios, a task-sharing relationship exists between the first and second users.

[0053] When a second user shares a task posted by a first user, it means that the first user posted a task, and the second user shared that task with users other than the first and second users. Similarly, when a first user shares a task posted by a second user, it means that the second user posted a task, and the first user shared that task with users other than the first and second users. In either of these cases, a task-sharing relationship exists between the first and second users.

[0054] If a second user follows a task posted by a first user, it means that the first user posted a task, and the second user followed that task. Similarly, if a first user follows a task posted by a second user, it means that the second user posted a task, and the first user followed that task. In either of these cases, a task-following relationship exists between the first and second users.

[0055] When a second user likes a task posted by a first user, it means that the first user posted a task, and the second user liked that task. Similarly, when a first user likes a task posted by a second user, it means that the second user posted a task, and the first user liked that task. In either of these cases, a task-liking relationship exists between the first and second users.

[0056] When a second user comments on a task posted by a first user, it means that the first user posted a task, and the second user commented on that task. Similarly, when a first user comments on a task posted by a second user, it means that the second user posted a task, and the first user commented on that task. In either of these cases, a task comment relationship exists between the first and second users.

[0057] The task collaboration relationship between the first user and the second user can belong to one or more main types, such as task attention and task assignment. The task collaboration relationship between the first user and the second user can also belong to one or more sub-types, such as the first user assigning a task to the second user, and the second user liking the task posted by the first user.

[0058] In step (b1), the type of collaboration relationship between each second user and the first user can be determined. This type of collaboration relationship can be one of the five main types mentioned above: task assignment, task sharing, task following, task liking, and task commenting, or it can be any of the sub-types mentioned above. This step can also determine the time information of the task collaboration relationship between each second user and the first user. This time information can be in the form of a timestamp. For example, if a second user likes a task posted by a first user, the timestamp of the second user's liking action is obtained as the time information of the task collaboration relationship between the second user and the first user. Similarly, if a second user assigns a task to a first user, the timestamp of the second user's assignment action is obtained as the time information of the task collaboration relationship between the second user and the first user.

[0059] In a special case, if the collaboration relationship between a second user and a first user includes multiple types, such as both likes and comments, then the collaboration relationship type with the highest priority will be used as the user ranking factor for that second user. The priority of collaboration relationship types will be explained later.

[0060] In a special case, if a second user has multiple task collaboration relationships with a first user, the time information of the most recent task collaboration relationship between the second user and the first user is obtained as the user ranking factor for the second user. For example, if a second user liked two tasks posted by the first user, the time information of the most recent like of the first user's task is obtained.

[0061] In step (b1), the order of the second users is determined based on the type of collaboration relationship between each second user and the first user and / or the time information of the task collaboration relationship between each second user and the first user.

[0062] In one scenario, the user ranking elements include: time information of the task collaboration relationship between the second user and the first user. Accordingly, based on the user ranking elements of at least one second user, the order of at least one second user is determined. Specifically, based on the time information of the task collaboration relationship between each second user and the first user, the order of each second user is determined in chronological order.

[0063] Specifically, when the user ranking elements include the time information of the task collaboration relationship between each second user, the ranking order of each second user is determined according to the time information, from the closest to the current time. The second user corresponding to the time information closest to the current time is ranked first, and the second user corresponding to the time information farthest from the current time is ranked last.

[0064] As can be seen, in this embodiment, the second users can be sorted according to the time information of the task collaboration relationship between the second user and the first user, so that the second user who last established a task collaboration relationship with the first user is ranked first and the second user who first established a task collaboration relationship with the first user is ranked last, thereby improving the experience of the first user in browsing the icons of the second users.

[0065] In one scenario, the user ranking elements include: the type of collaboration relationship between the second user and the first user. Accordingly, the ranking order of at least one second user is determined based on the user ranking elements of at least one second user. Specifically, the ranking order of each second user is determined based on the type of collaboration relationship between each second user and the first user and the priority order of each preset type of collaboration relationship.

[0066] Specifically, there is a priority order among the various collaboration relationship types. In one case, the priority order refers to the order among the five main types mentioned above—task assignment, task sharing, task following, task liking, and task commenting. For example, the priority of task assignment, task sharing, task following, task liking, and task commenting decreases in that order. In another case, the priority order refers to the order among the various subtypes mentioned above. For example, for the subtypes where the second user is the task executor designated by the first user, the first user is the task executor designated by the second user, the second user is the task sharing recipient designated by the first user, and the first user is the task sharing recipient designated by the second user, the priority of these four subtypes decreases in that order.

[0067] When the collaboration relationship type between the second user and the first user included in the user sorting elements refers to the five main types mentioned above, the order of the second users is determined according to the priority order of the five main types and the main type to which the task collaboration relationship between each second user and the first user belongs. In the determined order, the priority of the main type corresponding to each second user decreases sequentially according to the order of the second users from first to last.

[0068] When the collaboration relationship type between the second user and the first user included in the user sorting elements refers to the various subtypes mentioned above, the order of the second users is determined according to the priority order of the various subtypes and the subtype to which the task collaboration relationship between each second user and the first user belongs. In the determined order, the priority of the subtype corresponding to each second user decreases sequentially according to the order of the second users from first to last.

[0069] As can be seen, in this embodiment, the second users can be sorted according to the type of collaboration relationship between the second user and the first user, so that the second users with higher priority collaboration relationship types are ranked first and the second users with lower priority collaboration relationship types are ranked last, thereby improving the experience of the first user in browsing the identifiers of the second users.

[0070] In another scenario, user ranking elements include: the type of collaboration relationship between the second user and the first user, and the time information of the task collaboration relationship between the second user and the first user; based on the user ranking elements of at least one second user, the ranking order of at least one second user is determined, specifically as follows:

[0071] (b11) Classify each second user according to the type of collaboration relationship between each second user and the first user, and determine the order of second users in each category according to the priority order of each type of collaboration relationship; within each category, determine the order of second users according to the time information of the task collaboration relationship between each second user and the first user, in chronological order.

[0072] or,

[0073] (b12) Based on the time information of the task collaboration relationship between each second user and the first user and the preset first time range division rule, classify each second user into categories, and the categories of the second users correspond one-to-one with the first time ranges divided according to the first time range division rule; determine the order of the second users in each category according to the time sequence between the first time ranges; within each category, determine the order of the second users according to the collaboration relationship type between each second user and the first user and the preset priority order between the collaboration relationship types.

[0074] Regarding step (b11), firstly, each second user is categorized according to the type of collaboration relationship between each second user and the first user. The order of the second users in each category is determined based on the preset priority order of the collaboration relationship types. When categorizing and sorting, if the collaboration relationship type between the second user and the first user included in the user sorting elements refers to the five main types mentioned above, each second user can be categorized according to the main type of the task collaboration relationship between each second user and the first user. Each category corresponds to one main type. Furthermore, the order of the second users in each category is determined based on the priority order of the five main types mentioned above. In the order of the categories, the priority of the main type corresponding to each category decreases sequentially from first to last.

[0075] When classifying and sorting by category, if the collaboration relationship type between the second user and the first user included in the user sorting elements refers to the various subtypes mentioned above, each second user can be classified according to the subtype to which the task collaboration relationship between each second user and the first user belongs. Each category corresponds to one subtype. Furthermore, the order of the second users in each category is determined according to the priority order among the various subtypes mentioned above. In the order of each category, the priority of the subtypes corresponding to each category decreases sequentially from the first category to the last.

[0076] Then, within each category, based on the time information of the task collaboration relationship established between each second user and the first user within each category, the order of the second users within each category is determined according to the chronological order. Specifically, within any category, the second user who last established a task collaboration relationship with the first user in chronological order is ranked first, and the second user who first established a task collaboration relationship with the first user in chronological order is ranked last.

[0077] As can be seen, through step (b11), the order of each second user can be determined by dimension in the order of type first and then time. In the determined order, the second user who last generated the task collaboration relationship among the multiple second users with the highest priority of collaboration relationship type is ranked first, so as to improve the user's experience of browsing the identifiers of each second user.

[0078] Regarding step (b12), firstly, based on the time information of the task collaboration relationship between each second user and the first user, and the preset first time range division rule, each second user is classified. The categories of the second users correspond one-to-one with the various first time ranges obtained according to the first time range division rule. Specifically, according to the preset first time range division rule, multiple first time ranges are obtained. For example, if the first time range division rule divides the time between the current time into 7-day intervals, then according to this rule, the time between the current time is divided into multiple first time ranges. Based on the time information of the task collaboration relationship between each second user and the first user, and the various time ranges obtained, each second user is classified. The categories of the second users correspond one-to-one with the various first time ranges obtained according to the first time range division rule. For each category of second user, the time when the task collaboration relationship with the first user falls within the time range corresponding to its category.

[0079] Next, based on the chronological order of the various first time ranges, the order of the second users in each category is determined. In the determined order, the first time range of the earlier category is closer to the current time, and the first time range of the later category is farther from the current time.

[0080] Finally, within each category, the order of the second users within each category is determined based on the type of collaboration relationship between each second user and the first user, and the preset priority order among these collaboration relationship types. Specifically, if the collaboration relationship between each second user and the first user within each category refers to one of the five main types mentioned above, the order of the second users within each category is determined based on the priority order among these five main types and the main type to which the task collaboration relationship between each second user and the first user belongs. Within this determined order, the priority of the main type corresponding to each second user within each category decreases sequentially according to the order of the second users from first to last.

[0081] Within each category, when the collaboration relationship between each second user and the first user refers to the various subtypes mentioned above, the order of the second users within each category is determined according to the priority order of the various subtypes and the subtype to which the task collaboration relationship between each second user and the first user within each category belongs. In the determined order, the priority of the subtype corresponding to each second user within each category decreases sequentially according to the order of the second users from first to last.

[0082] As can be seen, through step (b12), the order of each second user can be determined by dimension in the order of time first and then type. In the determined order, the second user with the highest priority of the collaboration relationship type among the multiple second users who have recently generated task collaboration relationships is ranked first, so as to improve the user's experience of browsing the identifiers of each second user.

[0083] In step S106 above, at least one second user's identifier is displayed in the first user's collaborative task center interface according to the determined arrangement order. The second user's identifier can be the second user's avatar.

[0084] Figure 2a This is a schematic diagram illustrating the identification of a second user as provided in one embodiment of this specification, such as... Figure 2a As shown, taking the computer-based task system as an example, the left sidebar of the first user's collaborative task center interface displays the title "Recent Collaborators," under which the avatars of the aforementioned second users are displayed. Figure 2aIn the scenario shown, the five second users who have the most recent task collaboration relationships with the first user are displayed in chronological order. The order of these second users is determined based on the time information of when their task collaboration relationships with the first user were established. Figure 2a In the scenario shown, the second user represented by the first avatar among the displayed second users is the one who last established a task collaboration relationship with the first user in chronological order. Conversely, the second user represented by the last avatar among the displayed second users is the one who first established a task collaboration relationship with the first user in chronological order. Figure 2a In the scenario shown, the order of the second user's avatars from top to bottom corresponds to the order of the time that the task collaboration relationship between the second user and the first user occurred, from the most recent to the furthest from the current time.

[0085] Figure 2b A schematic diagram illustrating the identifier of a second user, provided for another embodiment of this specification, such as... Figure 2b As shown, taking the mobile task system as an example, a human-shaped control is displayed in the upper right corner of the first user's collaborative task center interface. Triggering this control will redirect to... Figure 2c The scene shown. Figure 2c A schematic diagram illustrating the identifier of a second user, provided for another embodiment of this specification, such as... Figure 2c As shown, after triggering the humanoid control on the mobile device, the "Recent Collaborators" interface can be displayed, which shows the avatars of the aforementioned second users. Figure 2c In the scenario shown, the five second users who have the most recent task collaboration relationships with the first user are displayed in chronological order, and the order of these second users is determined based on the type of collaboration relationship between them and the first user. Figure 2c In the scenario shown, the second user represented by the first avatar among the displayed second users is the one with the highest priority in terms of the collaboration relationship type between them and the first user. Conversely, the second user represented by the last avatar among the displayed second users is the one with the lowest priority in terms of the collaboration relationship type between them and the first user. Figure 2c In the scenario shown, the order of the second user's avatars from top to bottom corresponds to the order of priority of the collaboration relationship type between the second user and the first user, from high to low.

[0086] Figure 3 A flowchart illustrating another embodiment of the collaborative task processing method provided in this specification is shown below. Figure 3 As shown, this process is in Figure 1 Based on this, after displaying the identifiers of at least one second user in the collaborative task center interface of the first user in an ordered manner, the following steps are also included:

[0087] Step S108: In response to the first user triggering the identification of the target second user among at least one second user, at least one collaborative task between the target second user and the first user is obtained, and the at least one collaborative task is displayed in the first user's collaborative task center interface.

[0088] Specifically, refer to Figure 2a and Figure 2c As shown, in addition to displaying the identifiers of each second user on the first user's collaborative task center interface, the first user can also trigger an action on any second user's identifier, such as clicking on any second user's avatar. In response to the first user's trigger on the identifier of at least one target second user, at least one collaborative task between the target second user and the first user is retrieved. This can be done when there are few collaborative tasks between the target second user and the first user, retrieving all collaborative tasks; or when there are many collaborative tasks, retrieving a preset number of collaborative tasks between the target second user and the first user, and displaying each retrieved collaborative task on the first user's collaborative task center interface. It should be noted that if any second user, such as the target second user, establishes a collaborative task relationship with the first user based on a certain collaborative task, then that collaborative task is considered a collaborative task between the second user and the first user. For example, if the second user shares task A with the first user, thus establishing a collaborative task relationship between the second user and the first user, then task A is a collaborative task between the second user and the first user.

[0089] In one embodiment, the number of at least one collaborative task obtained is multiple, that is, multiple collaborative tasks between the target second user and the first user are obtained. Accordingly, at least one collaborative task is displayed in the first user's collaborative task center interface. Specifically, in each collaborative task, the target collaborative task corresponding to the most recent collaborative relationship between the target second user and the first user is determined, and the target collaborative task is determined to be the first in the arrangement of each collaborative task in the first user's collaborative task center interface; the arrangement of other collaborative tasks besides the target collaborative task in each collaborative task in the first user's collaborative task center interface is determined; based on the arrangement of the target collaborative task and other collaborative tasks in the first user's collaborative task center interface, each collaborative task is displayed in the first user's collaborative task center interface.

[0090] Specifically, after obtaining multiple collaborative tasks between the target second user and the first user, the target collaborative task is determined from among these tasks based on the most recent collaborative relationship between the second user and the first user. For example, if three collaborative tasks are obtained: one where the first user liked the second user's post two days ago, one where the first user shared something with the second user one day ago, and one where the first user assigned something to the second user one hour ago, then since the most recent collaborative relationship between the second user and the first user was one hour ago, the task assigned by the first user to the second user one hour ago is taken as the target collaborative task. Subsequently, the target collaborative task is determined to be the first item in the list of all the obtained collaborative tasks in the first user's collaborative task center interface.

[0091] Next, the arrangement of all collaborative tasks (excluding the target collaborative task) within each collaborative task in the first user's collaborative task center interface is determined. This can be done by randomly determining the arrangement of each other collaborative task within the acquired collaborative tasks in the first user's collaborative task center interface. Finally, based on the arrangement of the target collaborative task and each other collaborative task within the acquired collaborative tasks in the first user's collaborative task center interface, each collaborative task is displayed in the first user's collaborative task center interface.

[0092] As can be seen, in this embodiment, since the target collaborative task corresponding to the most recent task collaboration relationship between the target second user and the first user is arranged first, after the first user triggers the target second user's identifier, the first user can first see the target collaborative task corresponding to the most recent task collaboration relationship between the first user and the second user, which makes it easier for the first user to browse the most recent collaborative task between the first user and the second user and improves the first user's task browsing experience.

[0093] In one embodiment, the number of at least one collaborative task obtained is multiple, that is, multiple collaborative tasks between the target second user and the first user are obtained. Accordingly, at least one collaborative task is displayed in the first user's collaborative task center interface. Specifically, the order of the collaborative tasks is determined according to the task sorting elements of each collaborative task, and each collaborative task is displayed in the first user's collaborative task center interface according to the order of the collaborative tasks. The task sorting elements include: the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task and / or the time information of the time when the collaborative relationship between the target second user and the first user was established.

[0094] Understandably, each collaborative task obtained reflects the collaborative task relationship between the first user and the target second user. For example, if the obtained task is assigned by the first user to the target second user, the corresponding collaborative task relationship can be a task assignment relationship. Similarly, each collaborative task obtained reflects the time information of when the collaborative task relationship between the first user and the target second user was established. For example, if the obtained task was assigned by the first user to the target second user an hour ago, the corresponding time information is a timestamp from an hour ago.

[0095] Based on this, after obtaining multiple collaborative tasks between the target second user and the first user, in one scenario, the type of collaborative relationship between the target second user and the first user corresponding to each obtained collaborative task is determined as the task sorting element for each obtained task. In another scenario, the time information, such as a timestamp, of the establishment of the task collaboration relationship between the target second user and the first user corresponding to each obtained collaborative task is determined as the task sorting element for each obtained task. In yet another scenario, both the type of collaborative relationship between the target second user and the first user corresponding to each obtained collaborative task, and the time information, such as a timestamp, of the establishment of the task collaboration relationship between the target second user and the first user corresponding to each obtained collaborative task are determined as the task sorting element for each obtained task.

[0096] In a special case, if the target second user and the first user have multiple task collaboration relationships based on the same collaborative task, then the time information of the most recent task collaboration relationship between the target second user and the first user based on the collaborative task is obtained as the task ranking element of the collaborative task.

[0097] In a special case, if a certain collaborative task corresponds to multiple collaborative relationship types between the target second user and the first user, such as both like and comment relationships, then the collaborative relationship type with the highest priority is taken as the task ranking factor for that task.

[0098] Then, based on the task sorting elements of each collaborative task, the order of arrangement of each collaborative task is determined, and each collaborative task is displayed in the collaborative task center interface of the first user according to the order of arrangement of each collaborative task.

[0099] In one embodiment, the task sorting elements include: the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task. Accordingly, the order of arrangement of each collaborative task is determined according to the task sorting elements of each collaborative task in at least one collaborative task. Specifically, the order of arrangement of each collaborative task is determined according to the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task, in chronological order.

[0100] Specifically, when the task sorting elements include the time information of the task collaboration relationship between the target second user and the first user corresponding to each acquired collaborative task, the order of the acquired collaborative tasks is determined according to the time information, from the closest to the current time. Among the acquired collaborative tasks, the collaborative task whose time information is closest to the current time is sorted first, and the collaborative task whose time information is farthest from the current time is sorted last.

[0101] As can be seen, in this embodiment, the acquired collaborative tasks can be sorted according to the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task. The collaborative task whose time information is closest to the current time is placed at the top, and the collaborative task whose time information is furthest from the current time is placed at the bottom, thereby improving the experience of the first user in browsing the acquired collaborative tasks.

[0102] In one embodiment, the task sorting elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task. Accordingly, the order of arrangement of each collaborative task is determined according to the task sorting elements of each collaborative task in at least one collaborative task. Specifically, the order of arrangement of each collaborative task is determined according to the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and the priority order of each preset type of collaboration relationship.

[0103] Specifically, there is a priority order among the various collaboration relationship types. In one case, the priority order refers to the priority order among the five main types mentioned above—task assignment, task sharing, task following, task liking, and task commenting. In another case, the priority order refers to the priority order among the various subtypes mentioned above.

[0104] When the collaboration relationship type between the target second user and the first user corresponding to each collaboration task included in the task sorting elements refers to the above five main types, the order of the obtained collaboration tasks is determined according to the priority order among the above five main types and the main type to which the task collaboration relationship between the target second user and the first user corresponding to each collaboration task belongs. In the determined order, the priority of the main type corresponding to each collaboration task decreases sequentially according to the order of the collaboration tasks from first to last.

[0105] When the collaboration relationship between the target second user and the first user corresponding to each collaboration task is one of the aforementioned subtypes, the order of the acquired collaboration tasks is determined according to the priority order of the aforementioned subtypes and the subtype to which the collaboration relationship between the target second user and the first user corresponding to each collaboration task belongs. In the determined order, the priority of the subtypes corresponding to each collaboration task decreases sequentially according to the order of the collaboration tasks from first to last.

[0106] As can be seen, in this embodiment, the collaborative tasks can be sorted according to the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task, so that the collaborative tasks with higher priority of the collaborative relationship type are placed first, and the collaborative tasks with lower priority of the collaborative relationship type are placed last, thereby improving the experience of the first user in browsing each collaborative task.

[0107] In another scenario, the task ranking elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task, and the time information of the time when the task collaboration relationship was established between the target second user and the first user corresponding to each collaborative task. Accordingly, based on the task ranking elements of each collaborative task in at least one collaborative task, the order of arrangement among the collaborative tasks is determined, specifically as follows:

[0108] (c11) Classify each collaborative task according to the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task, and determine the order of collaborative tasks in each category according to the priority order of each type of collaborative relationship; within each category, determine the order of collaborative tasks according to the time information of the time when the collaborative relationship between the target second user and the first user corresponding to each collaborative task is generated, in chronological order.

[0109] or,

[0110] (c12) Based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset second time range division rule, classify each collaborative task, and the categories of collaborative tasks correspond one-to-one with each second time range divided according to the second time range division rule; determine the arrangement order of collaborative tasks in each category according to the time sequence between each second time range; within each category, determine the arrangement order of collaborative tasks according to the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset priority order between each type of collaboration relationship.

[0111] Regarding step (c11), firstly, each collaborative task is categorized according to the type of collaborative relationship between the target second user and the first user. The order of collaborative tasks within each category is determined based on a preset priority order among the various collaborative relationship types. When categorizing and sorting by category, if the collaborative relationship type between the target second user and the first user for each collaborative task is one of the five main types mentioned above, the collaborative tasks can be categorized according to the main type of the collaborative relationship corresponding to each task. Each category corresponds to one main type. Furthermore, the order of collaborative tasks within each category is determined based on the priority order among the five main types. In the order of categories, the priority of the main type corresponding to each category decreases sequentially from the first category to the last.

[0112] When classifying and sorting by category, if the collaborative relationship type between the target second user and the first user corresponding to each collaborative task is one of the aforementioned subtypes, the collaborative tasks can be classified according to the subtype to which the collaborative relationship belongs. Each category corresponds to one subtype. Furthermore, the order of collaborative tasks in each category is determined according to the priority order among the aforementioned subtypes. In the order of each category, the priority of the subtypes corresponding to each category decreases sequentially from the first category to the last.

[0113] Then, within each category, based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task within each category, the order of the collaborative tasks within each category is determined according to chronological order. Specifically, within any category, the collaborative task whose time information is closest to the current time is ranked first, and the collaborative task whose time information is furthest from the current time is ranked last.

[0114] As can be seen, through step (c11), the order of various collaborative tasks can be determined by dimension, following the order of type first and then time. In the determined order, the collaborative task with the highest priority of the collaborative relationship type and the one whose time information is closest to the current time is placed first, so as to improve the user's experience of browsing various collaborative tasks.

[0115] Regarding step (c12), firstly, based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset second time range division rule, each collaborative task is classified. The categories of collaborative tasks correspond one-to-one with the various second time ranges obtained according to the second time range division rule. Specifically, multiple second time ranges are obtained according to the preset second time range division rule. For example, if the second time range division rule divides the time between the current time into 7-day intervals, then multiple second time ranges are obtained by dividing the time between the current time into 7-day intervals according to this rule. Based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task and the various time ranges obtained, each collaborative task is classified. The categories of collaborative tasks correspond one-to-one with the various second time ranges obtained according to the second time range division rule. For each category of collaborative task, the time information of the task collaboration relationship between the target second user and the first user falls within the time range corresponding to its category.

[0116] Next, based on the chronological order of the various second time ranges, the order of collaborative tasks in each category is determined. In the determined order, the category at the beginning has a second time range that is closer to the current time, while the category at the end has a second time range that is farther from the current time.

[0117] Finally, within each category, the order of collaborative tasks within each category is determined based on the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task, and the preset priority order among these collaborative relationship types. Within each category, if the collaborative relationship type between the target second user and the first user corresponding to each collaborative task, as included in the task sorting elements, refers to the five main types mentioned above, the order of collaborative tasks within each category is determined based on the priority order among these five main types and the main type to which the collaborative relationship between the target second user and the first user belongs. In this determined order, the priority of the main type corresponding to each collaborative task within each category decreases sequentially according to the order of the collaborative tasks.

[0118] Within each category, if the collaboration relationship type between the target second user and the first user corresponding to each collaborative task included in the task sorting elements refers to the various subtypes mentioned above, the order of each collaborative task within each category is determined according to the priority order among the various subtypes and the subtype to which the task collaboration relationship between the target second user and the first user corresponding to each collaborative task within each category belongs. In the determined order, the priority of the subtypes corresponding to each collaborative task within each category decreases sequentially according to the order of the collaborative tasks from first to last.

[0119] As can be seen, through step (c12), the order of each collaborative task can be determined by dimension in the order of time first and then type. In the determined order, the time information of the task collaboration relationship between the target second user and the first user is closer to the current time, and the collaborative task with the highest priority of the collaboration relationship type between the target second user and the first user is placed first, so as to improve the user's experience of browsing each collaborative task.

[0120] Figure 4a This is a schematic diagram illustrating a display of a collaborative task provided in one embodiment of this specification, such as... Figure 4a As shown, taking the task system on the computer as an example, the first user triggers the avatar of a second user under the title "Recent Collaborators" (e.g., ...). Figure 4a After "Xiao Wang" (in the context of the first user), the collaborative task center interface of the first user can display all the collaborative tasks between the triggered second user and the first user. Figure 4a In the scenario shown, the various collaborative tasks between the triggered second user and the first user are classified according to the collaborative relationship type corresponding to each collaborative task. Within each category, they are sorted according to the time information of the time when the collaborative relationship was generated.

[0121] Figure 4b This is a schematic diagram illustrating a collaborative task as provided in another embodiment of this specification, such as... Figure 4b As shown, taking the mobile task system as an example, the first user triggers the avatar of a second user under the title "Recent Collaborators" (e.g., ...). Figure 4b After "VIVIAN" in the name, the collaborative task center interface of the first user can display the various collaborative tasks between the triggered second user and the first user. Figure 4b In the scenario shown, the first collaborative task is the one that most recently created a collaborative relationship between the second user and the first user. The order of the remaining collaborative tasks is determined by the priority of their respective collaborative relationship types.

[0122] Furthermore, in one embodiment, the collaborative task center interface of the first user also displays collaborative tasks related to the first user, such as collaborative tasks assigned to the first user by other users, or collaborative tasks assigned by the first user to other users. Accordingly, the method in this embodiment further includes: obtaining the task creation source identifier corresponding to the displayed collaborative task, displaying the collaborative task creation source identifier in the collaborative task center interface of the first user, and, in response to the first user's triggering operation on the task creation source identifier, displaying the task creation source interface of the collaborative task to the first user.

[0123] Specifically, the displayed collaborative tasks can be either collaborations between any of the aforementioned second users (such as the target second user) and the first user, or any collaborative task related to the first user. In addition to displaying collaborative tasks related to the first user in the first user's collaborative task center interface, the interface can also retrieve the task creation source identifier corresponding to the displayed collaborative task. For example, if the collaborative task is created based on a session, a shared document, or a third-party external system, then the session identifier is retrieved as the task creation source identifier; or the shared document identifier is retrieved as the task creation source identifier; or the third-party external system identifier is retrieved as the task creation source identifier. Furthermore, this collaborative task creation source identifier is displayed in the first user's collaborative task center interface. The task creation source identifier can be displayed near the corresponding collaborative task.

[0124] Next, if the first user triggers the task creation source identifier, such as by clicking the task creation source identifier, the task creation source interface for the collaborative task will be displayed to the first user in response to this triggering action. As mentioned above, the task creation source can be a session, a shared document, or a third-party external system, etc., and the task creation source interface can be the associated interface of a session, the content interface of a shared document, the system interface of a third-party external system, etc.

[0125] Figure 5a This is a schematic diagram illustrating the creation of a source identifier for a demonstration task provided in one embodiment of this specification, such as... Figure 5a As shown, the collaborative task center interface for the first user displays collaborative tasks related to the first user, such as collaborative tasks between the first user and the target second user. Below the collaborative tasks, the task creation source identifier is also displayed. In the figure, the task creation source is represented by a session, and the task creation source identifier is used as the session identifier for illustration.

[0126] Figure 5b To and Figure 5a A diagram showing the corresponding task creation source interface, such as... Figure 5b As shown, if the first user triggers Figure 5a The session identifier in the middle can then display the associated interface of the session used to create the collaborative task corresponding to the source identifier of the triggered task to the first user. Figure 5b In the context of the displayed session, there is a session message that says "We need to have a meeting to discuss this tomorrow." The collaborative task corresponding to the triggered task creation source identifier is created based on this session message. Therefore, in the displayed session, this session message is displayed after being processed with a specific format, such as being bolded.

[0127] As can be seen, this embodiment also enables users to jump to the source of task creation, making it convenient for them to trace the source of collaborative task creation.

[0128] Figure 6 This is a schematic diagram of the structure of a collaborative task processing device provided in one embodiment of this specification, as shown below. Figure 6 As shown, the device includes:

[0129] The first acquisition unit 61 is used to acquire at least one second user who has a task collaboration relationship with the first user;

[0130] The second acquisition unit 62 is used to acquire the arrangement order of the at least one second user;

[0131] The identifier display unit 63 is used to display the identifiers of at least one second user in the collaborative task center interface of the first user according to the arrangement order.

[0132] Optionally, the first acquisition unit 61 is specifically used for:

[0133] Obtain at least one second user who has a task collaboration relationship with the first user within a preset time range;

[0134] or,

[0135] Based on the time information of the task collaboration relationship established with the first user, a preset number of second users who have a task collaboration relationship with the first user are obtained in chronological order.

[0136] Optionally, the second acquisition unit 62 is specifically used for:

[0137] The order of the at least one second user is determined based on the user sorting elements of the at least one second user;

[0138] The user ranking elements include: the type of collaboration relationship between the second user and the first user and / or the time information of the task collaboration relationship between the second user and the first user.

[0139] Optionally, the user ranking elements include: time information on the time when the task collaboration relationship was established between the second user and the first user;

[0140] The second acquisition unit 62 is further specifically used to: determine the order of arrangement of each second user according to the time information of the time when the task collaboration relationship is generated between each second user and the first user, in chronological order.

[0141] Optionally, the user ranking element includes: the type of collaborative relationship between the second user and the first user;

[0142] The second acquisition unit 62 is further specifically used to: determine the arrangement order of each second user according to the type of collaboration relationship between each second user and the first user and the priority order of each preset type of collaboration relationship.

[0143] Optionally, the user ranking elements include: the type of collaboration relationship between the second user and the first user and the time information of the task collaboration relationship between the second user and the first user;

[0144] The second acquisition unit 62 is also specifically used for:

[0145] Based on the type of collaboration relationship between each second user and the first user, each second user is classified. The order of the second users in each category is determined according to the priority order of each preset collaboration relationship type. Within each category, the order of the second users is determined according to the time information of the task collaboration relationship between each second user and the first user, in chronological order.

[0146] or,

[0147] Based on the time information of the task collaboration relationship between each second user and the first user and the preset first time range division rule, each second user is classified, and the categories of the second users correspond one-to-one with each first time range divided according to the first time range division rule; the order of the second users in each category is determined according to the time sequence between each first time range; within each category, the order of the second users is determined according to the collaboration relationship type between each second user and the first user and the preset priority order between each collaboration relationship type.

[0148] Optionally, the device further includes: a task display unit, used for:

[0149] After displaying the identifiers of at least one second user in the first user's collaborative task center interface according to the arranged order, in response to the first user's triggering of the identifier of the target second user among the at least one second user, at least one collaborative task between the target second user and the first user is obtained, and the at least one collaborative task is displayed in the first user's collaborative task center interface.

[0150] Optionally, the number of the at least one collaborative task can be multiple; the task display unit is specifically used for:

[0151] In each of the collaborative tasks, the target collaborative task corresponding to the most recent collaborative relationship between the target second user and the first user is determined, and the target collaborative task is determined to be the first in the arrangement of the collaborative tasks in the first user's collaborative task center interface; the arrangement of other collaborative tasks besides the target collaborative task in the collaborative task center interface of the first user is determined; based on the arrangement of the target collaborative task and the other collaborative tasks in the collaborative task center interface of the first user, each collaborative task is displayed in the collaborative task center interface of the first user.

[0152] Optionally, the number of the at least one collaborative task can be multiple; the task display unit is specifically used for:

[0153] Based on the task sorting elements of each collaborative task in the at least one collaborative task, the arrangement order of each collaborative task is determined, and based on the arrangement order of each collaborative task, each collaborative task is displayed in the collaborative task center interface of the first user.

[0154] The task sorting elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and / or the time information of the time when the task collaboration relationship was generated between the target second user and the first user corresponding to each collaborative task.

[0155] Optionally, the task sorting elements include: time information on the time when the task collaboration relationship was established between the target second user and the first user corresponding to each collaborative task;

[0156] The task display unit is also specifically used for:

[0157] Based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task, the order of arrangement of each collaborative task is determined in chronological order.

[0158] Optionally, the task sorting elements include: the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task;

[0159] The task display unit is also specifically used for:

[0160] The order of the collaborative tasks is determined based on the collaborative relationship type between the target second user and the first user corresponding to each collaborative task and the priority order of each preset collaborative relationship type.

[0161] Optionally, the task sorting elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and the time information of the time when the task collaboration relationship was generated between the target second user and the first user corresponding to each collaborative task;

[0162] The task display unit is also specifically used for:

[0163] Based on the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task, the collaborative tasks are classified. The order of collaborative tasks in each category is determined according to the priority order of each preset collaborative relationship type. Within each category, the order of collaborative tasks is determined according to the time information of the time when the collaborative relationship between the target second user and the first user corresponding to each collaborative task is generated, in chronological order.

[0164] or,

[0165] Based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset second time range division rule, the collaborative tasks are classified, and the categories of the collaborative tasks correspond one-to-one with the various second time ranges obtained according to the second time range division rule; the order of collaborative tasks in each category is determined according to the chronological order between the various second time ranges; within each category, the order of collaborative tasks is determined according to the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset priority order between various collaboration relationship types.

[0166] Optionally, collaborative tasks related to the first user are also displayed in the first user's collaborative task center interface;

[0167] The device further includes an interface display unit, configured to: obtain the task creation source identifier corresponding to the collaborative task, and display the task creation source identifier in the collaborative task center interface of the first user; and, in response to the first user's trigger operation on the task creation source identifier, display the task creation source interface of the collaborative task to the first user.

[0168] It should be noted that the collaborative task processing device in this embodiment can implement the various processes of the aforementioned collaborative task processing method embodiments and achieve the same effects and functions, which will not be repeated here.

[0169] This specification also provides an electronic device according to one embodiment. Figure 7 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this specification, such as... Figure 7 As shown, electronic devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memories 802, with the memory 802 storing one or more application programs or data. The memory 802 can be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions within the electronic device. Furthermore, the processor 801 may be configured to communicate with the memory 802, executing the series of computer-executable instructions stored in the memory 802 on the electronic device. The electronic device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input or output interfaces 805, one or more keyboards 806, etc.

[0170] In one specific embodiment, the electronic device may be a server or terminal device for an instant messaging application, including a processor; and a memory configured to store computer-executable instructions, which, when executed by the processor, cause the processor to perform the following process:

[0171] Obtain at least one second user who has a task collaboration relationship with the first user;

[0172] Obtain the arrangement order of the at least one second user;

[0173] The identifiers of at least one second user are displayed in the collaborative task center interface of the first user in the order stated.

[0174] It should be noted that the electronic device in this embodiment can implement the various processes of the aforementioned collaborative task processing method embodiment and achieve the same effect and function, which will not be repeated here.

[0175] Another embodiment of this specification provides a computer-readable storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process:

[0176] Obtain at least one second user who has a task collaboration relationship with the first user;

[0177] Obtain the arrangement order of the at least one second user;

[0178] The identifiers of at least one second user are displayed in the collaborative task center interface of the first user in the order stated.

[0179] It should be noted that the storage medium in this embodiment can implement the various processes of the aforementioned collaborative task processing method embodiment and achieve the same effect and function, which will not be repeated here.

[0180] The computer-readable storage medium includes read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc.

[0181] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0182] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0184] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0185] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0186] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0187] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0188] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0189] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0190] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0191] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0192] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method of cooperative task processing, characterized by, include: Obtain at least one second user who has a task collaboration relationship with the first user; The types of task collaboration relationships include at least one of the following: task assignment relationship, task sharing relationship, task following relationship, task liking relationship, and task commenting relationship; Obtain the arrangement order of the at least one second user; The identifiers of at least one second user are displayed in the collaborative task center interface of the first user in the order described above. In response to the first user's triggering of the identifier of the target second user among the at least one second user, at least one collaborative task between the target second user and the first user is obtained, and the at least one collaborative task is displayed in the first user's collaborative task center interface; The step of obtaining the arrangement order of the at least one second user includes: The order of the at least one second user is determined based on the user ranking factors of the at least one second user; the user ranking factors include: the type of collaboration relationship between the second user and the first user and / or the time information of the task collaboration relationship between the second user and the first user.

2. The method according to claim 1, characterized in that, The acquisition of at least one second user who has a task collaboration relationship with the first user includes: Obtain at least one second user who has a task collaboration relationship with the first user within a preset time range; or, Based on the time information of the task collaboration relationship established with the first user, a preset number of second users who have a task collaboration relationship with the first user are obtained in chronological order.

3. The method according to claim 1, characterized in that, The user ranking elements include: time information of the time when the task collaboration relationship was established between the second user and the first user; Determining the order of the at least one second user based on the user sorting elements of the at least one second user includes: determining the order of the second users according to the time information of the task collaboration relationship between each second user and the first user, in chronological order.

4. The method according to claim 1, characterized in that, The user ranking elements include: the type of collaborative relationship between the second user and the first user; Determining the order of the at least one second user based on the user sorting elements of the at least one second user includes: determining the order of the second users based on the type of collaboration relationship between each second user and the first user and the priority order of each preset type of collaboration relationship.

5. The method according to claim 1, characterized in that, The user ranking elements include: the type of collaboration relationship between the second user and the first user, and the time information of when the task collaboration relationship between the second user and the first user was established; Determining the order of the at least one second user based on the user sorting elements of the at least one second user includes: Based on the type of collaboration relationship between each second user and the first user, each second user is classified. The order of the second users in each category is determined according to the priority order of each preset collaboration relationship type. Within each category, the order of the second users is determined according to the time information of the task collaboration relationship between each second user and the first user, in chronological order. or, Based on the time information of the task collaboration relationship between each second user and the first user and the preset first time range division rule, each second user is classified, and the categories of the second users correspond one-to-one with each first time range divided according to the first time range division rule; the order of the second users in each category is determined according to the time sequence between each first time range; within each category, the order of the second users is determined according to the collaboration relationship type between each second user and the first user and the preset priority order between each collaboration relationship type.

6. The method according to claim 1, characterized in that, The number of the at least one collaborative task is multiple; Displaying the at least one collaborative task in the collaborative task center interface of the first user includes: in each collaborative task, determining the target collaborative task corresponding to the most recent collaborative relationship between the target second user and the first user; determining the target collaborative task as the first position in the arrangement of the collaborative tasks in the collaborative task center interface of the first user; determining the arrangement of other collaborative tasks besides the target collaborative task in the collaborative task center interface of the first user; and displaying each collaborative task in the collaborative task center interface of the first user based on the arrangement of the target collaborative task and the other collaborative tasks in the collaborative task center interface of the first user.

7. The method according to claim 1, characterized in that, The number of the at least one collaborative task is multiple; The step of displaying the at least one collaborative task in the collaborative task center interface of the first user includes: determining the arrangement order of the collaborative tasks according to the task sorting elements of each collaborative task in the at least one collaborative task, and displaying the collaborative tasks in the collaborative task center interface of the first user according to the arrangement order of the collaborative tasks. The task sorting elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and / or the time information of the time when the task collaboration relationship was generated between the target second user and the first user corresponding to each collaborative task.

8. The method according to claim 7, characterized in that, The task sorting elements include: the time information of the time when the task collaboration relationship was established between the target second user and the first user corresponding to each collaborative task; Determining the order of the collaborative tasks based on the task sorting elements of each collaborative task in the at least one collaborative task includes: determining the order of the collaborative tasks according to the time information of the time when the task collaboration relationship is established between the target second user and the first user corresponding to each collaborative task, in chronological order.

9. The method according to claim 7, characterized in that, The task sorting elements include: the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task; Determining the order of the collaborative tasks based on the task sorting elements of each collaborative task in the at least one collaborative task includes: determining the order of the collaborative tasks based on the collaborative relationship type between the target second user and the first user corresponding to each collaborative task and the priority order of each preset collaborative relationship type.

10. The method according to claim 7, characterized in that, The task sorting elements include: the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task, and the time information of the time when the task collaboration relationship was generated between the target second user and the first user corresponding to each collaborative task; Determining the order of the collaborative tasks based on the task sorting elements of each collaborative task in the at least one collaborative task includes: Based on the type of collaborative relationship between the target second user and the first user corresponding to each collaborative task, the collaborative tasks are classified. The order of collaborative tasks in each category is determined according to the priority order of each preset collaborative relationship type. Within each category, the order of collaborative tasks is determined according to the time information of the time when the collaborative relationship between the target second user and the first user corresponding to each collaborative task is generated, in chronological order. or, Based on the time information of the task collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset second time range division rule, the collaborative tasks are classified, and the categories of the collaborative tasks correspond one-to-one with the various second time ranges obtained according to the second time range division rule; the order of collaborative tasks in each category is determined according to the chronological order between the various second time ranges; within each category, the order of collaborative tasks is determined according to the type of collaboration relationship between the target second user and the first user corresponding to each collaborative task and the preset priority order between various collaboration relationship types.

11. The method according to claim 1, characterized in that, The first user's collaborative task center interface also displays collaborative tasks related to the first user; The method further includes: obtaining the task creation source identifier corresponding to the collaborative task, displaying the task creation source identifier in the collaborative task center interface of the first user; and, in response to the first user's trigger operation on the task creation source identifier, displaying the task creation source interface of the collaborative task to the first user.

12. A collaborative task processing device, characterized in that, include: The first acquisition unit is used to acquire at least one second user who has a task collaboration relationship with the first user; The types of task collaboration relationships include at least one of the following: task assignment relationship, task sharing relationship, task following relationship, task liking relationship, and task commenting relationship; The second acquisition unit is used to acquire the arrangement order of the at least one second user; An identifier display unit is used to display the identifiers of at least one second user in the collaborative task center interface of the first user according to the arranged order; The task display unit is used to respond to the first user's triggering of the identifier of the target second user among the at least one second user, to obtain at least one collaborative task between the target second user and the first user, and to display the at least one collaborative task in the first user's collaborative task center interface. Specifically, the second acquisition unit is used to: determine the order of the at least one second user based on the user sorting elements of the at least one second user; the user sorting elements include: the type of collaboration relationship between the second user and the first user and / or the time information of the task collaboration relationship between the second user and the first user.

13. An electronic device, characterized in that, include: processor; as well as, A memory configured to store computer-executable instructions, which, when executed by a processor, cause the processor to perform the steps of the method described in any one of claims 1-11.

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

Images