TW201926953A - Information acquisition method and device for group task - Google Patents

Abstract

Provided in one or more embodiments of the description are an information acquisition method and device for a group task. The method can comprise: sending a message through a session corresponding to a group, wherein the message contains identification content, and query content for a group task in the group, and the identification content is used for instructing a server to reply to the query content; and receiving reply content returned by the server for the query content, wherein the reply content comprises information of the group task.

Description

Group task information acquisition method and device

One or more embodiments of the present specification relate to the field of communications technologies, and in particular, to a method and apparatus for acquiring information of a group task.

In the related technology, the mobile group office platform is more and more widely used in the business processes of various groups such as enterprises, educational institutions, government agencies, etc., which can not only improve communication efficiency between users, reduce communication costs, but also be effective. Improve user event processing efficiency and office efficiency. For example, the mobile group office platform can implement the task function, and realize the reminding and tracking processing of related events by creating tasks. However, the communication function and the task function in the mobile group office platform are independent of each other. The user needs to perform task management in the task management interface corresponding to the task function, and then switch from the task management interface to the communication interface corresponding to the communication function to communicate, resulting in use. The operation is cumbersome and inefficient. Moreover, when the number of existing tasks is increasing, the user needs to carefully view and filter the tasks in the task management interface, and it is often difficult to efficiently and accurately obtain the task information that is desired to be understood.

In view of this, one or more embodiments of the present specification provide a method and apparatus for acquiring information of a group task. In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions: According to the first aspect of one or more embodiments of the present specification, a method for acquiring information of a group task is provided, including: The session sends a message, the message includes the content of the query and the content of the query for the group task in the group, the identifier content is used to instruct the server to reply to the query content; receiving the server for the The reply content returned by the content is inquired, and the reply content includes information of the group task. According to a second aspect of one or more embodiments of the present disclosure, an information acquiring apparatus for a group task is provided, including: a sending unit, which sends a message through a session corresponding to the group, the message including the identifier content and the group An inquiry content of the group task in the group, the identifier content is used to instruct the server to reply to the inquiry content; the reply content receiving unit receives the reply content returned by the server for the inquiry content, the reply The content includes information about the group task.

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of the specification. Instead, they are merely examples of devices and methods consistent with aspects of one or more embodiments of the present specification as detailed in the appended claims. It should be noted that the steps of the corresponding method are not necessarily performed in the order shown and described in the specification in other embodiments. In some other embodiments, the method may include more or fewer steps than those described herein. In addition, the individual steps described in this specification may be decomposed into multiple steps for description in other embodiments; while the multiple steps described in this specification may be combined into a single step in other embodiments. description. FIG. 1 is a schematic structural diagram of a group task system according to an exemplary embodiment. As shown in FIG. 1, the system may include a server 11, a network 12, and a number of electronic devices, such as a mobile phone 13, a mobile phone 14, and a mobile phone 15. The server 11 can be a physical server including a separate host, or the server 11 can be a virtual server hosted by the host cluster. During operation, the server 11 can run a program on the server side of an application to implement related business functions of the application, such as when the server 11 runs a program of the mobile group office platform. The server side of the group office platform. In the technical solution of one or more embodiments of the present specification, the server 11 can cooperate with the user end running on the mobile phone 13-15 to implement a group task-based information acquisition solution. In this embodiment, the mobile group office platform can not only realize the communication function, but also can be used as an integrated function platform for many other functions, such as approval events (such as leave, office item application, financial and other approval events), attendance events. The processing of internal events of the group, such as task events, log events, and the like, such as ordering, purchasing, and other external events of the group, one or more embodiments of the present specification are not limited thereto. More specifically, the mobile group office platform can be carried in instant messaging applications in related technologies, such as enterprise instant messaging (EIM) applications, such as Skype For Business. ^® , Microsoft Teams ^® Yammer ^® Workplace ^® Slack ^® Enterprise WeChat ^® Share customers ^® Corporate letter ^® Enterprise letter ^® Wait. of course, The instant messaging function is only one of the communication functions supported by the mobile group office platform. The mobile group office platform can also implement more features such as the above. I will not repeat them here. Mobile phones 13-15 are just one type of electronic device that a user can use. Actually, It is obvious that the user can also use an electronic device such as the following: Tablet device, Notebook computer, Palm computers (PDAs, Personal Digital Assistants), Wearable devices (such as smart glasses, Wisdom watches, etc.) One or more embodiments of the present specification do not limit this. During the operation, The electronic device can run a program on the client side of an application. To implement the relevant business functions of the application, For example, when the electronic device runs a program of a mobile group office platform, It can be implemented as the client of the mobile group office platform. It should be noted that: The client-side application of the mobile group office platform can be pre-installed on the electronic device. Enabling the client to be up and running on the electronic device; of course, When using an online "client" such as HTML5 technology, No need to install the appropriate application on the electronic device. You can get and run the client. And for the network 12 that interacts between the mobile phone 13-15 and the server 11, Multiple types of wired or wireless networks can be included. In an embodiment, The network 12 can include a Public Switched Telephone Network (Public Switched Telephone Network). PSTN) and the Internet. Simultaneously, Communication between the electronic devices such as the mobile phone 13-15 can also be performed through the network 12, For example, establishing a single chat session between any two electronic devices; or, Multiple users can participate in the same group. The multiple electronic devices they use can participate in the corresponding session of the same group. Enabling any user to send a communication message to all other users in the session through their own electronic devices. FIG. 2 is a flowchart of a method for acquiring information of a group task according to an exemplary embodiment. as shown in picture 2, The method is applied to an electronic device, The steps can be included: Step 202, Send a message through the session corresponding to the group. The message includes an identification content and an inquiry content for a group task within the group. The identifier content is used to instruct the server to reply to the inquiry content. In an embodiment, When the user input information is detected in the session interface corresponding to the session, Transmitting the user input information as a message content of the message, That is, the message can be manually input by the user. In an embodiment, According to the message content and sending period set by the user, Automatically send the message, For example, the sending cycle can include daily, weekly, Waiting every month, It can be set by the user according to actual needs. among them, The user can set one or more transmission cycles. And each cycle corresponds to the same or different message; E.g, Users can set the sending period to both daily and weekly. a message that automatically sends the first content every day, And the message of the second content is automatically sent every week. In an embodiment, The identification content can include any predefined content. This specification does not limit this. E.g, The identification content can be in the form of "special character + name". For example, the special character can be @, #等不字的字元, And the name can be a server, Robots, etc., pre-agreed to refer to the information of the server, Thus the identification content can be such as "@server", "#Robot#" and so on. For another example, The identification content can directly use the information pre-agreed to refer to the server. Such as "group secretary" and so on. In an embodiment, The user terminal of the mobile group office platform can be run on the electronic device. The client can provide group communication functions and task management functions. The group communication function realizes group creation and communication operations between group members. The task management function realizes the management of tasks. In an embodiment, Group tasks are different from other types of tasks. Group tasks are available for users to create within the functional interface associated with the group. View and other management operations, Easy to create the group task, Fast communication based on the group's session between the associated users such as the performer. In an embodiment, The creator of the group task, Associated users such as performers may be group members of the group. Enables these associated users to implement quick communication based on the group's sessions. In an embodiment, The group task may be created by a group member of the group in an associated function interface of the group. E.g, The associated function interface can include a task management interface. The task management interface allows group members to create new group tasks, View group tasks that have been created, etc. And the session interface of the group may include an entry of the task management interface. So that group members can quickly switch between the task management interface and the session interface. of course, The associated function interface can also include other forms of functional interfaces related to the group. This specification does not limit this. In an embodiment, An executor of the group task may be determined by a creator of the group task by performing a selection operation in a group member of the group. For example, the creator can select at least one group member, As the executor of the group task; among them, When the creator is creating a group task, The creator can only be provided with a list of group members for the group. Thus, both the creator and the performer are restricted to the group members of the group. In addition, If the creator of the group task does not implement the selection operation, All group members of the group are preset as performers of the group task. In an embodiment, When the creator is a member of a group within the group, The creator is able to enter the functional interface associated with the group. To complete the creation of the group task. In an embodiment, When the creation interface of any task is not related to the group, And the creator of any of the tasks described, When the performers are members of the group of the group, Any of the tasks may be determined as group tasks within the group. E.g, Although the creator did not create tasks in the functional interface associated with the group, But if both the creator and the selected performer belong to the same group, The task can be set to a group task related to the same group; among them, This setting operation can be automatic operation. Or you can initiate a reminder to the creator. And the setting operation is performed when the creator responds to the set reminder. In an embodiment, Group members of a group may have the same group attribution information (such as belonging to the same company). That is, the group is a group within the group. In an embodiment, The group members of the group may have different group attribution information (such as belonging to multiple enterprises respectively). That is, the group is a cross-group group. In an embodiment, Groups can be independent of groups. For example, groups created between relatives or friends. Step 204, Receiving a reply content returned by the server for the inquiry content, The reply content includes information of the group task. In an embodiment, News, The reply content can be of any type. This specification does not limit this. such as, The message can include at least one of the following: Text message or audio message, The reply content can include at least one of the following: Text message or audio message. In one case, Messages and answers can be of the same type. For example, when a message uses a text message, The reply content is also a text message. When the message is an audio message, The reply content is also an audio message. In another case, There can be no type association between the message and the reply content. For example, when a message uses a text message, The reply content can be a text message, It can also be an audio message. In an embodiment, When the message contains the identified content, The message and the reply content may be visible only to the sender of the message, Not visible to other group members in the group, Therefore, in the case of satisfying the inquiry request of the sender, Avoid unnecessary interference with other group members. In an embodiment, Receiving a notification message for the group task automatically sent by the server; E.g, The notification message may include at least one of the following: Periodic statistical information, Tips for group tasks that have not yet been completed, Tips for group tasks near completion deadlines, Completion prompt information for completed group tasks, etc. This specification does not limit this. In an embodiment, When a triggering operation for the notification message is detected, Switching to the information display interface of the group task related to the notification message, To view summary or detailed information about the group's tasks. In an embodiment, The group task can be generated by the creator by configuring the group task template. In other words, Several alternative group task templates can be created in advance. For example, these group task templates are applicable to different positions, Different scenes, Different industries or different purposes, etc. Allows the creator to select the appropriate group task template based on actual needs. By configuring the configurable variables in the group task template, You can quickly generate group tasks that meet your actual needs. Simplify the creator's actions. Simultaneously, In the process of creating a group task, The group task template can also play a certain teaching and guiding role for the creator. Especially for creators who create group tasks for the first time or less, Can assist the creator to complete the rapid creation of group tasks. Thereby reducing the creator's learning threshold. In an embodiment, Creators are free to use all of the group task templates. In another embodiment, The group task template is pre-bound to the group. That is, the creator can only configure the group task template bound to the group. Can't use other group task templates at will, Thereby, the use management of the group task template is realized. In an embodiment, Can be group owner, Management members such as administrators manage group task templates. For example, bind a group task template to a group. Or unbind the group task template from the group. Correspondingly, Group members can use the group task template that is bound to the group. To quickly create the corresponding group task. In an embodiment, The group task template can be provided by the above-mentioned communication application or developer of the mobile group office platform. Access and use by users of the communications application or mobile community office platform. In another embodiment, The group task template can be created by the above-mentioned communication application or user of the mobile group office platform. And share it with other users for use; E.g, The communication application or mobile group office platform can provide a common platform for group task templates. Users can share the group task templates created by themselves through the shared platform. You can also get a group task template shared by other users. In an embodiment, A task log file can be imported within the group. Descriptive information of at least one group task recorded in the task log file; then, According to the description information recorded in the task log file, Create group tasks related to the group in batches. among them, The task log file can include any of the following: Text file, Form file, etc. This specification does not limit this. By recording the description information of the group task in the task log file in advance, Enable group members to import the task log file into the group. fast, Create corresponding group tasks in batches. Without group members, Create each group task separately, Helps improve the efficiency of creating group tasks. In an embodiment, When a group member imports a task log file, You can specify a group task template to use. The created group tasks are generated based on the group task template. Helps ensure that generated group tasks are in style, The format and other aspects meet the actual needs of the members of the group. For ease of understanding, Take the enterprise instant messaging application "Enterprise WeChat" as an example. The technical solution of one or more embodiments of the present specification will be described. Assume that the mobile phone 13 and the mobile phone 14 are running an enterprise WeChat client, The server 11 runs an enterprise WeChat server. The registered account of user A is registered on the mobile phone 13, Making the mobile phone 13 configured as the enterprise WeChat client 1, The registered account of user B is registered on the mobile phone 14, The mobile phone 14 is configured as an enterprise WeChat client 2. among them, Assume user A, User B is a group member of group AA. The management operation of the group task can be implemented based on the group AA. FIG. 3 is a schematic diagram of a group session interface provided by an exemplary embodiment. Assume that on the enterprise WeChat client 1 running on the mobile phone 13, The user interface A can be presented with the conversation interface 300 as shown in FIG. The session interface 300 corresponds to the group AA in which the user A is located. The session interface 300 can include a group task diagram 301 as shown in FIG. The group task icon 301 can serve as an operation entry for the corresponding function interface. When the triggering operation for the group task icon 301 is detected, It is possible to switch to the group task management interface 400 as shown in FIG. FIG. 4 is a schematic diagram of a group task management interface provided by an exemplary embodiment. In an embodiment of the present specification, Group tasks and group tasks are different names for the same type of tasks. This specification does not limit this. In the group task management interface 400 as shown in FIG. 4, A group task creation area 401 may be included. The group task creation area 401 is available for the user A to create a new group task within the group AA. The group task management interface 400 can also display group tasks that have been created within the group AA. For example, the group task 402 shown in FIG. 4, Group task 403 and so on. In an embodiment, The task theme of group task 402 is "Complete the design plan before Tuesday", The creator is user A, The executor is user B, The task creation time is "10-18 15: 30", The deadline is "October 24, Tuesday 18: 00", The reply status is "no reply", The completion status is "B is not completed". Of course, in other embodiments, only a part of the above content may be included. Or you can include other types of task information. This specification does not limit this. Similarly, The task topic of group task 403 is "X project product plan", The creator is user C, The performer is 3 users, such as User A. The task creation time is "10-12 14: 20", The deadline is "10 October 20th Friday: 00", The reply status is "2 replies", The completion status is "1/3 completed". In an embodiment, Only group task 402 can be shown in FIG. 4, Part of the information of group task 403, etc. User A can trigger the group task 402 or the group task 403. To view task details. E.g, The specific reply content of "2 replies" in group task 403, Information on the three performers of "A and 3 people", Information on completed and unfinished people in "1/3 people completed", etc. They can all be presented in the task details. In an embodiment, The prompt information such as "add a group task..." may be displayed in the input box of the group task creation area 401. To assist user A to complete the creation of the group task. E.g, FIG. 5 is a schematic diagram of a task theme for setting a group task according to an exemplary embodiment; FIG. The input box of the area 401 is created by the trigger group task, User A can enter the task topic of the group task to be created in the input box. For example, the task theme may be the "Y project design draft" shown in FIG. 5 or any other content. In an embodiment, The group task creation area 401 may include an executor setting icon 501, Allows User A to set the performer for the group task that needs to be created. E.g, FIG. 6 is a schematic diagram of an executor of setting a group task according to an exemplary embodiment; After detecting the trigger operation for the executor setting icon 501, It is possible to switch to the performer setting interface 600 as shown in FIG. The performer setup interface 600 can include an alternate user list 601 on the right side and a selected user list 602 on the left side. among them, The alternate user list 601 can include all group members of the group AA. For example, user A, User B, User C, User D and user E, etc.; Assume that user A selects user B and user C as performers. In user B, The user C will display the check mark "√" in the corresponding selection box "○" in the candidate user list 601. User B and User C will be added to the selected user list 602 on the left. When User A wishes to cancel the selection of User B or User C, The corresponding selection box "○" can be retriggered; or, In the selected user list 602, User B, User C has a corresponding delete flag "X". The selection of the corresponding user can be cancelled by triggering the delete flag "X". FIG. 7 is a schematic diagram of a group task management interface of a set performer provided by an exemplary embodiment. After user A implements the selection of the performer, The executor setting icon 501 shown in FIG. 5 can be replaced. To prompt user A that the selection operation has been implemented, Avoid forgetting after performing other operations. E.g, When User A will User B, When user C is selected as the performer, The performer setting icon 501 shown in FIG. 5 can be replaced with the user B selected as the performer, User C's avatar icon, In order to enable user A to quickly determine at least a portion of the selected performers. of course, Since the group task creation area 401 is often limited, Therefore, there may be a limit to the number of avatars displayed. For example, the limit is no more than 3 avatars. The excess avatar may not be displayed or omitted by "...". In an embodiment, The group task creation area 401 can include a deadline setting icon 502, User A can set a deadline for the group task that needs to be created. E.g, FIG. 8 is a schematic diagram of a deadline for setting a group task according to an exemplary embodiment; FIG. When the triggering operation for the deadline setting icon 502 is detected, You can switch to the deadline setting interface 800 as shown in Figure 8. The deadline setting interface 600 can include a date selection area and a time setting area. The user can set the date and time as the deadline, respectively. For example, it can be set as shown in Figure 8 on October 30, 2017 16: 00. among them, The deadline setting interface 800 can provide the "no deadline" option as shown in FIG. Never set a deadline for the corresponding group task. Similar to the executor setting icon 501, After user A sets the deadline for the group task, It is also possible to replace the deadline setting icon 502. To prompt user A, I will not repeat them here. FIG. 9 is a schematic diagram of another population task management interface provided by an exemplary embodiment. Based on the above operation of user A, Creating a new group task can be displayed in the group task management interface 400 as shown in FIG. For example, the new group task can be the group task 404 shown in FIG. among them, The task theme of group task 404 is "Y project design draft", The creator is user A, The performer is 2 users such as User B. The task creation time is "10-18 17: 30", The deadline is "Monday, October 30th 16: 00", The reply status is "no reply", The completion status is "0/2 Completed". FIG. 10 is a schematic diagram of a creator-based session interface provided by an exemplary embodiment. Based on the group task created by the user A in the above embodiment, The enterprise WeChat client 1 can publish the group task in the session interface 300 of the group AA; For example, as shown in Figure 10, This group of tasks can be used as a message from user A. It is shown in the session interface 300. of course, User A can also trigger the group task icon 301 in the session interface 300. Switching to the group task management interface 400 as shown in FIG. To view the group task 404 corresponding to the message. FIG. 11 is a schematic diagram of an executor-based session interface provided by an exemplary embodiment. Assume that on the enterprise WeChat client 2 running on the mobile phone 14, The user interface B can be presented with a session interface 1100 as shown in FIG. The session interface 1100 displays a message 1101 issued by user A, The content of the message 1101 is the group task 404 as shown in FIG. of course, Since the display area of the message 1101 is small, Thus, only part of the information of the group task 404 can be shown. Such as the task theme, Executor, Deadline, etc. When the user B trigger message 1101 is detected, The task details of the corresponding group task can be presented to User B. E.g, FIG. 12 is a schematic diagram of a task details interface provided by an exemplary embodiment; FIG. Based on the triggering operation on the message 1101, You can switch to the task details interface 1200 as shown in Figure 12. To display the task details of the corresponding group task on the task details interface 1200, Including the task theme is "Y project design draft", The creator of this group task is user A, The creation time is "just (such as within 1 minute)", The deadline is "Monday, October 30th 16: 00", The remaining days are "12 days remaining", The performers are User B and User C, The completion status is "not completed", The related group is "Group AA" and the like. among them, The status setting option is included on the left side of the task topic "Y Project Design Draft". This status setting option is presented as "□" in Figure 12; When the status setting option is shown as shown in Figure 12, Indicates that the completion status of the corresponding group task is "unfinished"; When user B triggers the status setting option, You can add the tag "√" to "□". And the completion status of the corresponding group task is switched to "completed"; of course, User B can set the option by triggering the status of the "Completed" status. Make the mark "√" in "□" canceled. Thereby, the completion status of the corresponding group task is switched to "unfinished". In an embodiment, The task details interface 1200 shows "from the group: Group AA" can be set to trigger state. Enabling user B to trigger the display content. Quickly switch to the session interface corresponding to group AA (such as session interface 1100 above). In an embodiment, The task details interface 1200 can include a subtask creation option (ie, "+subtask") as shown in FIG. This allows User B to create one or more subtasks associated with the group task "Y Project Design Draft". In an embodiment, The session interface 1100 of the group AA may include a group task icon 1102, Similar to the group task icon 301 in the session interface 300 described above, User B can switch to the group task management interface 1300 as shown in FIG. 13 by triggering the group task icon 1102. To view and manage group tasks in group AA. In an embodiment, Corresponding to the message 1101 shown in FIG. 11, The group task management interface 1300 can show a corresponding group task 1301, And the group task management interface 1300 can also show other group tasks 1302. Group task 1303, etc. among them, The group task management interface 1300 can include a group task creation area 1304, User B can create group tasks in group AA. This process is similar to User A's above creation process. I will not repeat them here. In an embodiment, The group task management interface 1300 can show all group tasks in the group AA. Such as group task 1301 Group task 1302 is a group task in which user B acts as an executor. Group task 1303 is independent of user B (user B is neither a creator, Group tasks that are not performers or other roles, However, it can be displayed on the group task management interface 1300. among them, Since group task 1301-1302 is related to user B, It is thus possible to provide User B with status setting options for the respective group tasks. The status setting option is presented as the same "□" as in Figure 12; When the status setting option is shown as shown in Figure 13, Indicates that the completion status of the corresponding group task is "unfinished"; When user B triggers the status setting option, You can add the tag "√" to "□". And the completion status of the corresponding group task is switched to "completed"; of course, User B can set the option by triggering the status of the "Completed" status. Make the mark "√" in "□" canceled. Thereby, the completion status of the corresponding group task is switched to "unfinished". And since group task 1303 is not related to user B, It is thus not possible to provide User B with status setting options for the respective group tasks. Or provide user B with an inoperable status setting option "■" as shown in FIG. To avoid user B misuse. In an embodiment, The group tasks displayed by the group task management interface 1300 can include multiple types. For example, group tasks that have not been completed, Completed group tasks, Closed group tasks, etc. User B can choose to display all types of group tasks. You can also choose to show only some types of group tasks. This specification does not limit this. E.g, The selection in Figure 13 only shows the group tasks that have not yet been completed. Thus masking the completed group tasks, Other types of group tasks such as closed group tasks. For other group members in group AA, When acting as the creator of a group task, You can refer to the related description of User A above. As an executor or an unrelated person of a group task, You can refer to the related description of User B above. I will not repeat them here. When the number of group tasks in the group AA is large, If you only rely on the group task management interface for viewing group AA, It may be difficult to implement group task management operations efficiently, You need to manually view each group task. therefore, This manual provides an efficient management solution for group tasks. FIG. 14 is a schematic diagram of an implementation group task management according to an exemplary embodiment; FIG. As shown in Figure 14, Assume that in the session interface 1400 corresponding to user A, User A can issue an inquiry message 1401 for the group task within the session interface 1400. This process is the same as the process of sending a message. In an embodiment, The query message 1401 can include two parts: Identify the content and the content of the inquiry. among them, The identification content is used for identification by the enterprise WeChat client 1 or the enterprise WeChat server (sent by the enterprise WeChat client 1 to the enterprise WeChat server). To distinguish the inquiry message 1401 from the ordinary message, For example, the identifier content may include “@群任务”. Of course, this specification does not limit the specific form of the content of the logo. The content of the inquiry may include "How is the progress of the current group task as shown in FIG. 14? ", That is, user A actually wants to initiate an inquiry for the group task. In an embodiment, When the enterprise WeChat client 1 recognizes the identification content, The query message 1401 or the query content can be distinguished from the ordinary message (such as adding a specific message identifier, Using a specific transmission port, Use a specific transmission link, etc. This manual does not limit this) to the enterprise WeChat server. The enterprise WeChat server does not forward it to other group members. But to analyze the content of the inquiry, And return the corresponding inquiry result. In another embodiment, After receiving the inquiry message 1401 sent by the enterprise WeChat client 1, the enterprise WeChat server receives the inquiry message 1401. The identification content and the inquiry content can be automatically recognized. And by parsing the inquiry, Return the corresponding inquiry result. In an embodiment, The result of the inquiry can be presented to the user A in the form of a message. For example, as shown in Figure 14, The query result can be included in message 1402. Received by the enterprise WeChat client 1 and displayed in the session interface 1400, And the sender of the message 1402 can be set to be a special sender different from the group member of the group AA, Such as the "robot" or other forms shown in Figure 14, This specification does not limit this. In an embodiment, When User A initiates an inquiry to the Enterprise WeChat server, The inquiry message 1401 will not be sent to other group members of the group AA. And the message 1402 containing the inquiry result is only sent to the user A, Also will not be sent to other group members of group AA, This avoids interference with other group members. of course, In some embodiments, Both the query message 1401 and the message 1402 can be sent to all group members. This specification does not limit this. User A can ask for anything related to the group task. Enterprise WeChat server can make corresponding answers and feedback. For example, in addition to the more general overall progress in Figure 14, It is also possible to make inquiries for a particular group member or groups. For example, as shown in Figure 15, The inquiry message 1501 sent by the user A in the session interface 1500 may be "@群 Task B's group task progress". Including the identification content "@群任务" and the content of the group "question progress" of the content "B", So that the enterprise WeChat server can determine the corresponding processing progress information for the group B of the user B in the group AA. This information can be included in the message 1502 and returned to the enterprise WeChat client 1, Presented by the enterprise WeChat client 1 to user A. In an embodiment, You can ask for a specific type of group task. For example, as shown in Figure 16, The inquiry message 1601 sent by the user A in the session interface 1600 may be "@group task uncompleted group task". Including the identification content "@群任务" and the inquiry content "unfinished group task", So that the enterprise WeChat server can determine the outstanding group tasks in the group AA, And return relevant information to the enterprise WeChat client 1 based on the message 1602. Presented by the enterprise WeChat client 1 to user A. In an embodiment, You can ask for group tasks for a specific deadline. For example, as shown in Figure 17, The inquiry message 1701 sent by the user A in the session interface 1700 may be "uncomplete group task of the @group task deadline before November". Including the identification content "@群任务" and the inquiry content "unfinished group tasks with deadlines before November", So that the enterprise WeChat server can be based on the deadline and completion status of the group tasks in the group AA. Identify group tasks with a due date earlier than November 1 and in an incomplete state. And return relevant information to the enterprise WeChat client 1 based on the message 1702. Presented by the enterprise WeChat client 1 to user A. In addition to responding to active inquiries from group members, The enterprise WeChat server can also actively push notification messages related to group tasks to group members. So that group members can keep up to date with relevant information. E.g, FIG. 18 is a schematic diagram of an active push and group task related notification message according to an exemplary embodiment; FIG. As shown in Figure 18, When the enterprise WeChat server determines that user A has two uncompleted group tasks, The corresponding notification message 1801 may be sent to the enterprise WeChat client 1 corresponding to the user A. The notification message 1801 is shown in the session interface 1800 by the enterprise WeChat client 1, Thereby achieving an active reminder to user A. For another example, FIG. 19 is a schematic diagram of another active push and group task related notification message according to an exemplary embodiment; FIG. As shown in Figure 19, When the enterprise WeChat server determines that User B has a group task that is about to reach the deadline (for example, no more than 3 days from the deadline), The corresponding notification message 1901 can be sent to the enterprise WeChat client 2 corresponding to the user B, The notification message 1901 is shown in the session interface 1900 by the enterprise WeChat client 2, Thereby realizing the active reminder to user B. In the embodiment shown in Figure 18, The notification message 1801 can be sent only to the user A, Not sent to other group members in group AA; In the embodiment shown in FIG. 19, The notification message 1901 can be sent to all group members of the group AA. And by adding a separate notification prompt identifier (such as "@B") for user B in the notification message 1901, So that even if the group AA is masked (for example, the "Do Not Disturb" function is activated), Enterprise WeChat client 2 can still send a reminder to user B. Thus, User B is prevented from ignoring the notification message 1901 for some reason. FIG. 20 is a schematic diagram of still another active push and group task related notification message according to an exemplary embodiment; FIG. As shown in Figure 20, The enterprise WeChat server receives such as user B, When a group member such as user C manages a group task, The corresponding notification message may be sent to the related party of the related group task (such as the creator or other performer, etc.) or the enterprise WeChat client corresponding to all the group members of the group AA. For example, the enterprise WeChat client 1 can receive the corresponding notification message 2001-2002, The notification message 2001-2002 is shown in the session interface 2000 by the enterprise WeChat client 1, Thereby, an active reminder to a group member such as user A is realized. In an embodiment, When it is detected that the group member triggers the messages 1402~1702 or the notification messages 1801~2001 in the above embodiment, The following operations can be implemented: In one case, Switch to the group task management interface of group AA, Viewed by group members; In another case, Switch to the group task management interface of group AA, Mark the group tasks involved in the above message, For group members to view; In another case, Switch to the task information viewing interface, Only the information of the group task (summary information or detailed information) related to the above message is shown; or, Other options are also available. This specification does not limit this. In an embodiment, In addition to performing manual input directly in the group task creation area 401 as shown in FIG. To create a corresponding group task, Group tasks can also be provided to group members of group AA. So that it can be faster, Create group tasks easily. E.g, 21 is a schematic diagram of a template selection interface provided by an exemplary embodiment; Group members of group AA can pass through the corresponding enterprise WeChat client. Looking at the template selection interface 2100 shown in FIG. 21, The template selection interface 2100 can include a template content layout preview map corresponding to a plurality of candidate group task templates. further, You can also select the "More Templates" option in interface 2100 via the trigger template. To view other group task templates that are not currently shown. In an embodiment, The group task template can be provided by the developer of the enterprise WeChat. Or provided by a dedicated third-party manufacturer. In another embodiment, The group task template can be created by the user of the enterprise WeChat. Upload to the enterprise WeChat server, And displayed by the enterprise WeChat server in the template selection interface 2100, Viewed by group members of group AA or group members of other groups, use. FIG. 22 is a schematic diagram of a template binding interface provided by an exemplary embodiment. Assume that the group members of the group AA select the "XX industry group task template" in the template selection interface 2100. Can be in the template binding interface 2200 as shown in FIG. A corresponding template content layout preview map 2201 is shown, For viewing by members of this group. When the group member belongs to a management member in the group AA, That is, the group members have the group task template management permission for the group AA. The template binding interface 2200 can provide binding options 2202 to the group members, Enabling the group member to trigger the binding option 2202, Bind the above "XX Industry Group Task Template" to the group AA. All group members in the group AA can quickly create corresponding group tasks through the "XX industry group task template". FIG. 23 is a schematic diagram of another template binding interface provided by an exemplary embodiment. Similar to FIG. 22, When the group member of the group AA selects the "XX industry group task template" in the template selection interface 2100, Can be in the template binding interface 2300 as shown in FIG. A corresponding template content layout preview diagram 2301 is shown, For viewing by members of this group. When the group member is not a management member of the group AA, That is, the group members do not have the group task template management permission for the group AA. The template binding interface 2300 can provide a binding request option 2302 to the group member, Enabling the group member to trigger the binding option 2302, Send a binding request message to the management member in the group AA, The management member can trigger the binding request message. Bind the above "XX Industry Group Task Template" to the group AA. All group members in the group AA can quickly create corresponding group tasks through the "XX industry group task template". FIG. 24 is a schematic diagram of another population task management interface provided by an exemplary embodiment. When group AA has a bound group task template, In the group task management interface 2400 as shown in FIG. 24, In addition to providing the group A creation area 2401 to the user A (corresponding to the group task creation area 401 shown in FIG. 4), The user A can create a corresponding group task by manually inputting in the group task creation area 2401. The group task management interface 2400 can also include a group task template trigger option 2402. Assume that the above "XX Industry Group Task Template" is bound to the group AA. When the user A trigger group task template trigger option 2402 is detected, This "XX Industry Group Task Template" can be called. Thus, by configuring the variable parameters in the "XX Industry Group Task Template", Group tasks that meet the needs of the "XX industry" can be created quickly and easily. In an embodiment, The group task management interface 2400 can include a group task batch import option 2403, For user A to quickly, Import group tasks in batches, No need to create them one by one. among them, User A can be in Notepad, The description information of the group task is recorded in the table tool. Such as the task theme, Task deadline, Task performer, etc. And generate a file that records these descriptions, Such as text files, Form file, etc. then, Bulk import option 2403 through the trigger group task, And select the above text file or form file, The enterprise WeChat client 1 or the enterprise WeChat server can parse the description information of the group task recorded in the file. And create corresponding group tasks in batches accordingly. It can effectively improve the efficiency of user A's creation of group tasks. FIG. 25 is a schematic structural diagram of an apparatus provided by an exemplary embodiment. Please refer to Figure 25, On the hardware level, The device includes a processor 2502 Internal bus 2504, Network interface 2506, Memory 2508 and non-volatile memory 2510, Of course, it may also include the hardware required by other businesses. The processor 2502 reads the corresponding computer program from the non-volatile memory 2510 into the memory 2508 and then runs. An information acquisition device that forms a group task on a logical level. of course, In addition to the software implementation, One or more embodiments of the present specification do not exclude other implementations. Such as logic devices or the combination of software and hardware, etc. In other words, the execution body of the following processing flow is not limited to each logical unit. It can also be a hardware or logic device. Please refer to Figure 26, In a software implementation, The information obtaining device of the group task may include: Transmitting unit 2601, Send a message through the session corresponding to the group. The message includes an identification content and an inquiry content for a group task within the group. The identifier content is used to instruct the server to reply to the inquiry content; Answer content receiving unit 2602, Receiving a reply content returned by the server for the inquiry content, The reply content includes information of the group task. Optional, The sending unit 2601 is specifically configured to: When the session interface corresponding to the session detects user input information, Transmitting the user input information as a message content of the message; or, According to the message content and sending period set by the user, The message is sent automatically. Optional, The message includes at least one of the following: Text message or audio message; The reply content includes at least one of the following: Text message or audio message. Optional, The creator of the group task, The performers are all members of the group of the group. Optional, The group task is created by a group member of the group in an associated function interface of the group. Optional, An executor of the group task is determined by a creator of the group task by performing a selection operation in a group member of the group; among them, When the creator of the group task does not implement the selection operation, All group members of the group are preset as performers of the group task. Optional, When the creation interface of any task is not related to the group, And the creator of any of the tasks described, When the performers are members of the group of the group, Any of the tasks are determined to be group tasks within the group. Optional, When the message contains the identified content, The message and the reply content are only visible to the sender of the message, Not visible to other group members in the group. Optional, Also includes: Notification receiving unit 2603, Receiving a notification message for the group task automatically sent by the server; The notification message includes at least one of the following: Periodic statistical information, Tips for group tasks that have not yet been completed, Tips for group tasks near completion deadlines, Information about completion of completed group tasks. Optional, Also includes: Switching unit 2604, When a triggering operation for the notification message is detected, Switching to the information presentation interface of the group task associated with the notification message. Optional, The group task is generated by the creator by configuring the group task template. Optional, The group task template is pre-bound to the group. Optional, Also includes: Import unit 2605, Import a task log file in the group, Descriptive information of at least one group task recorded in the task log file; Creating unit 2606, According to the description information recorded in the task log file, Create group tasks related to the group in batches. Optional, The task log file includes any of the following: Text file, Form file. The system illustrated in the above embodiment, Device, Module or unit, Specifically, it can be implemented by a computer chip or an entity. Or it can be realized by a product with a certain function. A typical implementation device is a computer. The specific form of the computer can be a personal computer, Laptop, Cellular phone, Camera phone, Smart phone, Personal digital assistant, Media player, Navigation equipment, Email transceiver, Game console, tablet, A wearable device or a combination of any of these devices. In a typical configuration, The computer includes one or more processors (CPUs), Input/output interface, Network interface and memory. Memory may include non-permanent memory in computer readable media. In the form of random access memory (RAM) and/or non-volatile memory, Such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer readable medium. Computer readable media includes both permanent and non-permanent, Removable and non-removable media can be stored by any method or technique. Information can be computer readable instructions, Data structure, Program modules or other materials. Examples of computer storage media include, But not limited to phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic random access memory (DRAM), Other types of random access memory (RAM), Read only memory (ROM), Electrically erasable programmable read-only memory (EEPROM), Flash memory or other memory technology, CD-ROM only read-only memory (CD-ROM), Digital versatile disc (DVD) or other optical storage, Magnetic cassette tape, Disk storage, Quantum memory, Graphene-based storage media or other magnetic storage devices or any other non-transporting media, Can be used to store information that can be accessed by a computing device. As defined in this article, Computer readable media does not include temporary storage of computer readable media (transitory media). Such as modulated data signals and carrier waves. It should also be noted that The term "includes", "Include" or any other variation thereof is intended to cover a non-exclusive inclusion, Thus a process that includes a series of elements, method, Goods or equipment include not only those elements, It also includes other elements that are not explicitly listed. Or is it also included for this process, method, The elements inherent in the goods or equipment. Without more restrictions, An element defined by the statement "includes one..." Does not exclude the process of including the elements, method, There are additional identical elements in the item or device. The foregoing description of the specific embodiments of the specification has been described. Other embodiments are within the scope of the appended claims. In some cases, The actions or steps recited in the claims can be performed in a different order than in the embodiments and the desired results can still be achieved. In addition, The processes depicted in the figures are not necessarily required to be in a particular In certain embodiments, Multiplex processing and parallel processing are also possible or may be advantageous. The terms used in one or more embodiments of the specification are for the purpose of describing particular embodiments only. Rather than intending to limit one or more embodiments. The singular forms "a" or "an""The" and "the" are also intended to include the majority of forms, Unless the context clearly indicates other meanings. It should also be understood that The term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It should be understood that Although one or more embodiments of the present specification may adopt the term first, second, Third class to describe various information, However, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. E.g, Without departing from the scope of one or more embodiments of the specification, The first information can also be referred to as the second information. Similarly, The second information can also be referred to as the first information. Depending on the context, The word "if" as used herein may be interpreted to mean "when" or "when" or "in response to a determination." The above description is only a preferred embodiment of one or more embodiments of the present specification. It is not intended to limit one or more embodiments of the specification. Within the spirit and principles of one or more embodiments of the present specification, Any modifications made, Equivalent replacement, Improvement, etc. They are all included within the scope of protection of one or more embodiments of the specification.

11‧‧‧Server

12‧‧‧Network

13‧‧‧Mobile

14‧‧‧Mobile

15‧‧‧Mobile

300‧‧‧session interface

301‧‧‧Group mission icon

400‧‧‧Group Task Management Interface

401‧‧‧Group task creation area

402‧‧‧Group Mission

403‧‧‧Group Mission

404‧‧‧Group Mission

501‧‧‧executor setting icon

502‧‧‧ deadline setting icon

600‧‧ deadline setting interface

601‧‧‧Optional User List

602‧‧‧Selected User List

800‧‧‧ deadline setting interface

1100‧‧‧session interface

1101‧‧ News

1102‧‧‧Group mission icon

1200‧‧‧Task details interface

1300‧‧‧Group Task Management Interface

1301‧‧‧Group Mission

1302‧‧‧Group Mission

1303‧‧‧Group Mission

1304‧‧‧Group task creation area

1400‧‧‧session interface

1401‧‧‧Inquiry

1402‧‧ News

1500‧‧‧session interface

1501‧‧‧Inquiry

1502‧‧ News

1600‧‧‧session interface

1601‧‧‧Inquiry

1602‧‧ News

1700‧‧‧session interface

1701‧‧‧Inquiry

1702‧‧ News

1800‧‧‧Session interface

1801‧‧‧Notice message

1900‧‧‧session interface

1901‧‧‧Notice message

2000‧‧‧Session interface

2001‧‧‧Notice

2002‧‧‧Notice

2100‧‧‧Template selection interface

2200‧‧‧Template Binding Interface

2201‧‧‧ Template Content Layout Preview

2202‧‧‧ Binding options

2300‧‧‧Template Binding Interface

2301‧‧‧ Template Content Layout Preview

2302‧‧‧ Binding options

2400‧‧‧Group Task Management Interface

2401‧‧‧Group task creation area

2402‧‧‧Group Task Template Trigger Options

2403‧‧‧Group Task Bulk Import Options

2502‧‧‧ processor

2504‧‧‧Internal busbar

2506‧‧‧Network interface

2508‧‧‧ memory

2510‧‧‧ Non-volatile memory

2601‧‧‧Send unit

2602‧‧‧Reply content receiving unit

2603‧‧‧Notice receiving unit

2604‧‧‧Switch unit

2605‧‧‧Importing unit

2606‧‧‧Create unit

FIG. 1 is a schematic structural diagram of a group task system according to an exemplary embodiment. FIG. 2 is a flowchart of a method for acquiring information of a group task according to an exemplary embodiment. FIG. 3 is a schematic diagram of a group session interface provided by an exemplary embodiment. FIG. 4 is a schematic diagram of a group task management interface provided by an exemplary embodiment. FIG. 5 is a schematic diagram of a task topic for setting a group task according to an exemplary embodiment. FIG. 6 is a schematic diagram of an executor of setting a group task according to an exemplary embodiment. FIG. 7 is a schematic diagram of a group task management interface of a set performer provided by an exemplary embodiment. FIG. 8 is a schematic diagram of a deadline for setting a group task according to an exemplary embodiment. FIG. 9 is a schematic diagram of another population task management interface provided by an exemplary embodiment. FIG. 10 is a schematic diagram of a creator-based session interface provided by an exemplary embodiment. FIG. 11 is a schematic diagram of an executor-based session interface provided by an exemplary embodiment. FIG. 12 is a schematic diagram of a task details interface provided by an exemplary embodiment. FIG. 13 is a schematic diagram of still another population task management interface provided by an exemplary embodiment. 14-17 are schematic diagrams of implementing group task management according to an exemplary embodiment. 18-20 are schematic diagrams of an active push and group task related notification message provided by an exemplary embodiment. FIG. 21 is a schematic diagram of a template selection interface provided by an exemplary embodiment. FIG. 22 is a schematic diagram of a template binding interface provided by an exemplary embodiment. FIG. 23 is a schematic diagram of another template binding interface provided by an exemplary embodiment. FIG. 24 is a schematic diagram of another population task management interface provided by an exemplary embodiment. FIG. 25 is a schematic structural diagram of an apparatus according to an exemplary embodiment. FIG. 26 is a block diagram of an information acquisition apparatus for a group task according to an exemplary embodiment.

Claims (28)

A method for acquiring information of a group task, comprising: sending a message through a session corresponding to the group, the message comprising the identifier content and the content of the query for the group task in the group, the identifier content is used to indicate the servo The device responds to the inquiry content; receives the reply content returned by the server for the inquiry content, and the reply content includes information of the group task. The method of claim 1, wherein the transmitting the message through the session corresponding to the group includes: when the session interface corresponding to the session detects the user input information, the user input information is used as the The message content of the message is sent; or, the message is automatically sent according to the message content and the sending period set by the user. The method of claim 1, wherein the message comprises at least one of: a text message or an audio message; the reply content comprises at least one of the following: a text message or an audio message. The method of claim 1, wherein the creator and the performer of the group task are group members of the group. The method of claim 1, wherein the group task is created by a group member of the group in an associated function interface of the group. The method of claim 5, wherein the performer of the group task is determined by a creator of the group task by performing a selection operation in a group member of the group; wherein, the group When the creator of the group task does not implement the selection operation, all group members of the group are preset as the performers of the group task. The method of claim 1, wherein when the creation interface of any task is not related to the group, and the creator or performer of the task is a group member of the group, the Any task is determined to be a group task within the group. The method of claim 1, wherein when the message includes the identification content, the message and the reply content are only visible to the sender of the message, and are invisible to other group members in the group. . The method of claim 1, further comprising: receiving a notification message automatically sent by the server for the group task; the notification message includes at least one of the following: periodic statistical information, for not yet completed The prompt information of the group task, the prompt information for the group task near the completion deadline, and the completion prompt information for the completed group task. The method of claim 9, wherein the method further comprises: switching to an information presentation interface of the group task associated with the notification message when a triggering operation for the notification message is detected. The method of claim 1, wherein the group task is generated by the creator by configuring the group task template. The method of claim 11, wherein the group task template is pre-bound to the group. The method of claim 1, further comprising: importing a task log file in the group, wherein the task log file records description information of at least one group task; according to the task log file Record description information, create group tasks related to the group in batches. The method of claim 13, wherein the task log file comprises any one of the following: a text file, a form file. An information acquisition device for a group task, comprising: a sending unit, configured to send a message through a session corresponding to the group, the message comprising the identifier content and the query content for the group task in the group, the identifier content is used by the identifier The instruction server is responsive to the inquiry content; the reply content receiving unit receives the reply content returned by the server for the inquiry content, and the reply content includes information of the group task. The device of claim 15, wherein the sending unit is specifically configured to: when the session interface corresponding to the session detects that the user inputs information, send the user input information as the message content of the message. Or, the message is automatically sent according to the message content and sending period set by the user. The device of claim 15, wherein the message comprises at least one of: a text message or an audio message; the reply content comprises at least one of the following: a text message or an audio message. The device of claim 15, wherein the creator and the performer of the group task are group members of the group. The device of claim 15, wherein the group task is created by a group member of the group in an associated function interface of the group. The device of claim 19, wherein the executor of the group task is determined by a creator of the group task by performing a selection operation in a group member of the group; wherein, the group When the creator of the group task does not implement the selection operation, all group members of the group are preset as the performers of the group task. The device of claim 15, wherein when the creation interface of any task is not related to the group, and the creator or performer of the task is a group member of the group, the Any task is determined to be a group task within the group. The device of claim 15, wherein when the message includes the identification content, the message and the reply content are only visible to the sender of the message, and are invisible to other group members in the group. . The device according to claim 15 , further comprising: a notification receiving unit, receiving a notification message automatically sent by the server for the group task; the notification message includes at least one of the following: periodic statistical information Prompt information for group tasks that have not been completed, prompt information for group tasks that are near completion deadlines, and completion prompt information for completed group tasks. The device of claim 23, further comprising: a switching unit that switches to an information presentation interface of the group task associated with the notification message when a triggering operation for the notification message is detected. The device of claim 15, wherein the group task is generated by the creator by configuring the group task template. The device of claim 25, wherein the group task template is pre-bound to the group. The device according to claim 15 , further comprising: an import unit, wherein a task log file is recorded in the group, and the task log file records description information of at least one group task; Create group tasks related to the group in batches according to the description information recorded in the task log file. The device of claim 27, wherein the task log file comprises any one of the following: a text file, a form file.