WO2019109880A1 - 群组任务的信息获取方法及装置 - Google Patents

群组任务的信息获取方法及装置 Download PDF

Info

Publication number
WO2019109880A1
WO2019109880A1 PCT/CN2018/118870 CN2018118870W WO2019109880A1 WO 2019109880 A1 WO2019109880 A1 WO 2019109880A1 CN 2018118870 W CN2018118870 W CN 2018118870W WO 2019109880 A1 WO2019109880 A1 WO 2019109880A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
task
message
content
information
Prior art date
Application number
PCT/CN2018/118870
Other languages
English (en)
French (fr)
Inventor
杨博宇
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201810265592.8A external-priority patent/CN109905315B/zh
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019109880A1 publication Critical patent/WO2019109880A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • One or more embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method and an apparatus for acquiring information of a group task.
  • 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.
  • the mobile group office platform can implement the task function, and realize the reminding and tracking processing of related events by creating tasks.
  • 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 on the task management interface corresponding to the task function, and then switches from the task management interface to the session interface corresponding to the communication function to communicate, resulting in the user's
  • the operation is cumbersome and inefficient.
  • 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.
  • one or more embodiments of the present specification provide a method and an apparatus for acquiring information of a group task.
  • a method for acquiring information of a group task including:
  • 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 content of the query;
  • the reply content including information of the group task.
  • an information acquiring apparatus for a group task including:
  • the sending unit sends a message by using a session corresponding to the group, where the message includes the identifier content and the query content for the group task in the group, the identifier content is used to instruct the server to reply to the query content;
  • the reply content receiving unit receives the reply content returned by the server for the query content, and the reply content includes information of the group task.
  • 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 theme 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 according to 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 according to an exemplary embodiment
  • FIG. 13 is a schematic diagram of still another population task management interface provided by an exemplary embodiment
  • FIG. 14 is a schematic diagram of an implementation group task management according to an exemplary embodiment
  • FIG. 15 is a schematic diagram of another implementation group task management provided by an exemplary embodiment
  • FIG. 16 is a schematic diagram of still another implementation of group task management according to an exemplary embodiment
  • FIG. 17 is a schematic diagram of still another implementation of group task management according to an exemplary embodiment.
  • FIG. 18 is a schematic diagram of an active push and group task related notification message according to an exemplary embodiment
  • FIG. 19 is a schematic diagram of another active push and group task related notification message according to an exemplary embodiment.
  • FIG. 20 is a schematic diagram of still another active push and group task related notification message according to an exemplary embodiment
  • 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 according to an exemplary embodiment
  • FIG. 23 is a schematic diagram of another template binding interface provided by an exemplary embodiment
  • 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 acquiring apparatus for a group task according to an exemplary embodiment.
  • 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.
  • 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 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster.
  • the server 11 can run a server-side program of an application to implement related business functions of the application. For example, when the server 11 runs the program of the mobile group office platform, the mobile group can be implemented. The server side of the platform.
  • the server 11 can cooperate with the client running on the mobile phone 13-15 to implement a group task-based information acquisition scheme.
  • 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.
  • approval events such as leave, office item application, financial and other approval events
  • attendance events such as attendance events.
  • 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. Microsoft Wait.
  • EIM enterprise instant messaging
  • Skype For. Microsoft Wait a mobile group office platform
  • the instant messaging function is only one of the communication functions supported by the mobile group office platform, and the mobile group office platform can implement more functions such as the above, which will not be described here.
  • Mobile phones 13-15 are just one type of electronic device that a user can use. In fact, users obviously can also use electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. Various embodiments do not limit this.
  • the electronic device can run a client-side program of an application to implement related business functions of the application, for example, when the electronic device runs a program of the mobile group office platform, the mobile device can be implemented as the mobile device. The client of the group office platform.
  • the application of the client of the mobile group office platform can be pre-installed on the electronic device so that the client can be launched and run on the electronic device; of course, when adopting an online "customer such as HTML5 technology" At the end, the client can be obtained and run without installing the corresponding application on the electronic device.
  • the network 12 may include multiple types of wired or wireless networks.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • the electronic devices such as the mobile phone 13-15 can also communicate through the network 12, for example, to establish a single-chat session between any two electronic devices; or, multiple users can participate in the same group, and they use more
  • the electronic device can participate in the corresponding session of the same group, so that any user can send a communication message to all other users in the session through its own electronic device.
  • FIG. 2 is a flowchart of a method for acquiring information of a group task according to an exemplary embodiment. As shown in FIG. 2, the method is applied to an electronic device, and may include the following steps:
  • Step 202 Send a message by using a session corresponding to the group, where the message includes the identifier content and the query content for the group task in the group, where the identifier content is used to instruct the server to reply to the query content.
  • the user input information when the user input information is detected on the session interface corresponding to the session, the user input information is sent as the message content of the message, that is, the message can be manually input by the user.
  • the message may be automatically sent according to the message content and the sending period set by the user.
  • the sending period may include daily, weekly, monthly, etc., and may be set by the user according to actual needs.
  • the user may set one or more sending periods, and each period corresponds to the same or different message; for example, the user may simultaneously set the sending period to be daily and weekly, so that the message of the first content is automatically sent every day, and The message of the second content is automatically sent every week.
  • the identification content may include any predefined content, which is not limited in this specification.
  • the identifier content may be in the form of “special character + name”.
  • the special character may be an infrequently used character such as @, #
  • the name may be a server, a robot, etc., which is pre-agreed for referring to the server, and thus the content is identified. It can be such as "@server”, "#robot#", and the like.
  • the identification content may directly adopt information pre-agreed for referring to the server, such as “group secretary” and the like.
  • the client of the mobile group office platform can be run on the electronic device, and the client can provide a group communication function and a task management function, and the group communication function realizes group creation and group members.
  • the communication operation between the tasks is managed by the task management function.
  • the group task is different from other types of tasks, and the group task is available for the user to implement management operations such as creating and viewing in the function interface related to the group, facilitating the creation of the group task, the performer, and the like. Quick communication is achieved between related users based on the group's session.
  • the associated users such as the creator, the performer, and the like of the group task may be group members of the group, so that the associated users can implement quick communication based on the session of the group.
  • the group task may be created by a group member of the group in an associated function interface of the group.
  • the associated function interface may include a task management interface
  • the task management interface may be used by the group member to create a new group task, view the created group task, and the like
  • the session interface of the group may include the task management interface.
  • the portal so that group members can quickly switch between the task management interface and the session interface.
  • the associated function interface may also include other forms of functional interfaces related to the group, and this specification does not limit this.
  • the performer of the group task may be determined by the creator of the group task by performing a selection operation in a group member of the group, for example, the creator may select at least one group a member, as an executor of the group task; wherein, when the creator creates the group task, the creator may only be provided with the group member list of the group, so that both the creator and the performer are restricted In the group members of the group.
  • the creator of the group task does not implement the selection operation, all group members of the group are defaulted to the executor of the group task.
  • the creator when the creator is a group member within the group, the creator can enter the function interface related to the group to complete the creation operation of the group task.
  • the any task when the creation interface of any task is not related to the group, and the creator or performer of any of the tasks is a group member of the group, the any task may be It is determined to be a group task within the group. For example, although the creator does not create a task in the function interface associated with the group, if both the creator and the selected performer belong to the same group, the task can be set as a group related to the same group.
  • the task wherein the setting operation may be an automatic operation, or a setting reminder may be initiated to the creator, and the setting operation is performed when the creator responds to the setting reminder.
  • group members of the group may have the same group attribution information (such as belonging to the same enterprise), that is, the group is a group within the group.
  • the group members of the group may have different group attribution information (such as belonging to multiple enterprises respectively), that is, the group is an inter-group group.
  • the group may be independent of the group, such as a group created between relatives or friends.
  • Step 204 Receive reply content returned by the server for the query content, where the reply content includes information of the group task.
  • the message and the reply content may be of any type, and the specification does not limit this.
  • the message may include at least one of the following: a text message or an audio message
  • the reply content may include at least one of the following: a text message or an audio message.
  • the message and the reply content may be of the same type.
  • the reply content when the message adopts a text message, the reply content is also a text message, and when the message is an audio message, the reply content is also an audio message.
  • the message and the reply content may be associated with no type.
  • the reply content may be a text message or an audio message.
  • the message and the reply content may be visible only to the sender of the message and not to other group members in the group. Therefore, in the case of satisfying the inquiry request of the sender, unnecessary interference with other group members is avoided.
  • the notification message for the group task that is automatically sent by the server may be received; for example, the notification message may include at least one of: periodic statistical information, for a group task that has not been completed yet.
  • the prompt information, the prompt information for the group task near the completion deadline, the completion prompt information for the completed group task, and the like are not limited in this specification.
  • the information presentation interface of the group task related to the notification message may be switched to facilitate viewing the summary information or the detailed information of the group task.
  • the group task may be generated by a creator by configuring a group task template.
  • a plurality of candidate group task templates can be created in advance, for example, the group task templates are respectively applicable to different positions, different scenarios, different industries, or different purposes, so that the creator can select an appropriate group task template according to actual needs.
  • the group task template can also play a certain teaching and guiding role for the creator, especially for the creator of the first or less group task creation, the creator can be assisted. Complete the rapid creation of group tasks, reducing the creator's learning threshold.
  • the creator can use all of the group task templates at will.
  • 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, but cannot be to other groups. The task template is used at will, so that the use management of the group task template is realized.
  • the group task template may be managed by a group owner, an administrator, or the like, such as group task template to group, or group task template to group. . Accordingly, group members can use the group task template that is bound to the group to quickly create the corresponding group task.
  • the group task template may be provided by the above-mentioned communication application or developer of the mobile group office platform for acquisition and use by the user of the communication application or the mobile group office platform.
  • the group task template may be created by the user of the communication application or the mobile group office platform described above, and shared to other users for use; for example, the communication application or the mobile group office platform may provide the group.
  • a shared platform of the group task template the user can share the group task template created by the user through the sharing platform, and can also obtain the group task template shared by other users.
  • a task record file may be imported in the group, where the description information of at least one group task is recorded in the task record file; and then, according to the description information recorded in the task record file, Create group tasks related to the group in batches.
  • the task record file may include any one of the following: a text file, a form file, and the like, which is not limited in this specification.
  • the group task template can be specified, so that the created group task is generated based on the group task template, which helps ensure the generated group.
  • the task satisfies the actual needs of the members of the group in terms of style, format, and the like.
  • the technical solution of one or more embodiments of the present specification will be described by taking the enterprise instant messaging application "Enterprise WeChat" as an example. It is assumed that the mobile phone 13 and the mobile phone 14 are running the enterprise WeChat client, the server 11 is running the enterprise WeChat server, the mobile phone 13 is registered with the user A's registered account, and the mobile phone 13 is configured as the enterprise WeChat client 1, the mobile phone 14 The registered account of the user B is logged in, so that the mobile phone 14 is configured as the enterprise WeChat client 2. It is assumed that the user A and the user B are group members of the group AA, and 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. It is assumed that on the enterprise WeChat client 1 running on the mobile phone 13, the user interface A can be presented with the session interface 300 as shown in FIG. 3, which corresponds to the group AA in which the user A is located.
  • the session interface 300 may include a group task icon 301 as shown in FIG. 3, and the group task icon 301 may serve as an operation entry of a corresponding function interface, so that when a trigger operation for the group task icon 301 is detected, it may be switched to The group task management interface 400 shown in FIG.
  • FIG. 4 is a schematic diagram of a group task management interface provided by an exemplary embodiment.
  • the group task and the group task are different names of the same type of task, and the present specification does not limit this.
  • a group task creation area 401 can be included, which can be used by 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, such as the group task 402, the group task 403, and the like shown in FIG.
  • the task topic of the group task 402 is “Complete design plan before Tuesday”, the creator is user A, the performer is user B, the task creation time is “10-18 15:30”, and the deadline is “ On Tuesday, October 24th, 18:00”, the reply status is "no reply”, and the completion status is "B is not completed”.
  • the task topic of the group task 403 is “X project product plan”, the creator is user C, the performer is user A, and the like, the task creation time is “10-12 14:20”, and the deadline is “10”. On Friday, January 20th, 12:00”, the reply status is "2 replies", and the completion status is "1/3 completed”.
  • only partial information of the group task 402, the group task 403, and the like may be shown in FIG. 4, and the user A may trigger the group task 402 or the group task 403 to view the task details.
  • the specific reply content of "2 replies” in the group task 403, the information of 3 executors of "3 people such as A”, the completed person in the "1/3 person completed", and the unfinished person Information, etc. can be specifically presented in the task details.
  • prompt information such as "add a group task" may be displayed in the input box of the group task creation area 401 to assist the user A in completing the group task creation operation.
  • FIG. 5 is a schematic diagram of a task theme for setting a group task according to an exemplary embodiment; by triggering an input box of the group task creation area 401, the user A can input the group task to be created in the input box.
  • the task theme such as the task topic, may be the "Y project design draft" shown in Figure 5 or any other content.
  • the group task creation area 401 may include an executor setting icon 501 for the user A to set the executor for the group task to be created.
  • FIG. 6 is a schematic diagram of an executor of setting a group task according to an exemplary embodiment; after detecting a triggering operation for the executor setting icon 501, it may switch to an executor setting interface as shown in FIG. 6. 600.
  • the performer settings interface 600 can include an alternate user list 601 on the right side and a selected user list 602 on the left side.
  • the candidate user list 601 may include all group members of the group AA, such as user A, user B, user C, user D, and user E, etc.; assume that user A selects user B and user C as performers, and the user B.
  • the user C will display the check mark " ⁇ " in the corresponding selection box " ⁇ " in the candidate user list 601, and the user B and the user C will be added to the selected user list 602 on the left side.
  • the corresponding selection box “ ⁇ ” may be re-triggered; or, in the selected user list 602, both the user B and the user C have the corresponding deletion flag “ ⁇ ”. You can cancel the selection of the corresponding user 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.
  • the executor setting icon 501 as shown in FIG. 5 may be replaced to prompt the user A that the selection operation has been performed to avoid forgetting after performing other operations.
  • the executor setting icon 501 as shown in FIG. 5 may be replaced with the avatar icon of the user B and the user C selected as the performer, so that the user A can quickly determine at least a portion of the selected performers.
  • the group task creation area 401 is often limited, the number of avatars displayed may be limited, for example, to no more than 3 avatars, and the excess avatar may not be displayed or omitted by using "".
  • the group task creation area 401 may include a deadline setting icon 502 for the user A to set a deadline for the group task to be created.
  • FIG. 8 is a schematic diagram of a deadline for setting a group task according to an exemplary embodiment; after detecting a trigger operation for the deadline setting icon 502, it may switch to the deadline setting interface 800 as shown in FIG.
  • the deadline setting interface 600 may include a date selection area and a time setting area, respectively, for the user to set the date and time as the deadline, for example, may be set to 16:00 on October 30, 2017 as shown in FIG.
  • the deadline setting interface 800 can provide a "no deadline" option as shown in FIG. 8 so that the deadline is not set for the corresponding group task. Similar to the executor setting icon 501, after the user A sets the deadline for the group task, the deadline setting icon 502 can also be replaced to prompt the user A, and details are not described herein again.
  • FIG. 9 is a schematic diagram of another population task management interface provided by an exemplary embodiment.
  • the created new group task can be displayed in the group task management interface 400 as shown in FIG. 9, for example, the new group task can be the group task 404 shown in FIG.
  • the task theme of the group task 404 is “Y project design draft”, the creator is user A, the performer is user B, and the like, the task creation time is “10-18 17:30”, and the deadline is “10 months”. On Monday 30th, 16:00", the reply status is "no reply", and the completion status is "0/2 completed”.
  • FIG. 10 is a schematic diagram of a creator-based session interface provided by an exemplary 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 FIG. 10, the group task can be issued as the user A.
  • a message is displayed in the session interface 300.
  • the user A can also switch to the group task management interface 400 as shown in FIG. 9 by triggering the group task icon 301 in the session interface 300 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. It is assumed that on the enterprise WeChat client 2 running on the mobile phone 14, a conversation interface 1100 as shown in FIG. 11 can be presented to the user B, and the conversation interface 1100 displays a message 1101 issued by the user A, and the content of the message 1101 is Group task 404 as shown in FIG. Of course, since the display area of the message 1101 is small, only part of the information of the group task 404, such as the task topic, the performer, the deadline, and the like, may be shown.
  • FIG. 12 is a schematic diagram of a task details interface provided by an exemplary embodiment; based on the triggering operation on the message 1101, it may be switched to the task details interface 1200 as shown in FIG. 12 to be on the task details interface 1200.
  • the task details of the corresponding group task are displayed, including the task theme is “Y project design draft”, the creator of the group task is user A, the creation time is “just (such as within 1 minute)”, and the deadline is “10 months”. Monday, 16:00, 16:00, the remaining days are "12 days remaining", the performers are User B and User C, the completion status is "Unfinished", and the related group is "Group AA”.
  • the left side of the task theme "Y project design draft” includes a status setting option, which is presented as " ⁇ " in FIG. 12; when the status setting option is displayed as shown in FIG. 12, indicating corresponding The completion status of the group task is “unfinished”; when user B triggers the status setting option, the flag “ ⁇ ” can be added in “ ⁇ ”, and the completion status of the corresponding group task is switched to “completed”; User B can cause the flag “ ⁇ ” in “ ⁇ ” to be canceled by triggering the status setting option of the "Completed” status, thereby switching the completion status of the corresponding group task to "Incomplete".
  • the "from group: group AA" displayed by the task details interface 1200 can be set to a triggerable state, so that the user B can quickly switch to the session interface corresponding to the group AA by triggering the display content ( For example, the above session interface 1100).
  • the task details interface 1200 may include a subtask creation option (ie, "+subtask") as shown in FIG. 12, such that the user B may create a related one of the group tasks "Y project design draft” accordingly. Or multiple subtasks.
  • the session interface 1100 of the group AA may include a group task icon 1102, which is similar to the group task icon 301 in the session interface 300, and the user B may switch to the group view icon 1102 by triggering the group task icon 1102.
  • the group task management interface 1300 is shown to view and manage group tasks in group AA.
  • the group task management interface 1300 may show a corresponding group task 1301, and the group task management interface 1300 may also show other group tasks 1302 and group tasks 1303. Wait.
  • the group task management interface 1300 may include a group task creation area 1304, and the user group B may create a group task in the group AA. The process is similar to the above-mentioned creation process of the user A, and details are not described herein again.
  • the group task management interface 1300 can show all group tasks in the group AA, such as the group task 1301, the group task 1302 is the group task of the user B as the performer, and the group task 1303 is independent of the user B.
  • the group task (user B is neither a creator nor an executor or other role) can be displayed on the group task management interface 1300.
  • the user B can be provided with a status setting option for the corresponding group task, the status setting option being presented as the same " ⁇ " as in FIG. 12; when the status setting option is displayed As shown in Figure 13, it indicates that the completion status of the corresponding group task is "unfinished”; when user B triggers the status setting option, the flag " ⁇ ” can be added in “ ⁇ ", and the corresponding group task The completion status is switched to "Completed”; of course, User B can trigger the status setting option of the "Completed” status, so that the flag " ⁇ ” in " ⁇ ” is canceled, thereby switching the completion status of the corresponding group task to "undone".
  • the state setting option for the corresponding group task may not be provided to the user B, or the user may be provided with the inoperable state setting option " ⁇ " as shown in FIG. 13 to avoid the user. B misoperation.
  • the group task displayed by the group task management interface 1300 may include multiple types, such as a group task that has not been completed, a group task that has been completed, a group task that has been closed, and the like, and the user B may select to display all types of groups. Tasks, you can also choose to display only some types of group tasks, this specification does not limit this. For example, the selection in Figure 13 only shows group tasks that have not yet completed, thus masking other types of group tasks such as completed group tasks, closed group tasks, and the like.
  • the related description of the user A when the creator of the group task is used, the related description of the user A may be referred to, and when the executor or the unrelated person of the group task is used, the related description of the user B may be referred to. I will not repeat them here.
  • FIG. 14 is a schematic diagram of an implementation of group task management provided by an exemplary embodiment; as shown in FIG. 14, it is assumed that in the session interface 1400 corresponding to user A, user A can issue a group task in the session interface 1400.
  • the message 1401 is queried, the process being the same as the process of sending the message.
  • the query message 1401 can include two portions: identifying content and querying content.
  • the identifier content is used for discriminating between the enterprise WeChat client 1 or the enterprise WeChat server (transmitted by the enterprise WeChat client 1 to the enterprise WeChat server) to distinguish the query message 1401 from the ordinary message, such as the identifier content.
  • the "@ ⁇ task" may be included, although the specification does not limit the specific form of the identification content.
  • the inquiry content may include "How is the current group task progress?" as shown in FIG. 14, that is, the content that the user A actually desires to initiate an inquiry for the group task.
  • the inquiry message 1401 or the inquiry content may be distinguished from the ordinary message (such as adding a specific message identifier, adopting a specific transmission port, adopting The specific transmission link, etc., is not limited in this specification. It is sent to the enterprise WeChat server, so that the enterprise WeChat server does not forward it to other group members, but parses the content of the inquiry and returns the corresponding Ask for results.
  • the enterprise WeChat server can automatically identify the identification content and the inquiry content, and return the corresponding inquiry result by parsing the inquiry content.
  • the query result may be presented to User A in the form of a message.
  • the query result may be included in the message 1402, received by the enterprise WeChat client 1 and displayed in the session interface 1400, and the sender of the message 1402 may be set to be different from the group of the group AA.
  • the special sender of the member such as the "robot" or other forms shown in Figure 14, is not limited in this specification.
  • the inquiry message 1401 when user A initiates an inquiry to the enterprise WeChat server, the inquiry message 1401 is not sent to other group members of the group AA, and the message 1402 containing the inquiry result is only sent to the user A, the same Will not be sent to other group members of group AA, thus avoiding interference to other group members.
  • both the query message 1401 and the message 1402 can be sent to all group members, and this specification does not limit this.
  • the enterprise WeChat server can make corresponding answers and feedback.
  • the inquiry message 1501 sent by the user A in the session interface 1500 may be "@group task B's group task progress", including the identification content "@group task” and the inquiry content "B group task progress". 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, the 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.
  • an inquiry can be made for a particular type of group task.
  • 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 "@group task” and the inquiry content "unfinished group task”. So that the enterprise WeChat server can determine the outstanding group task in the group AA, and return the related information to the enterprise WeChat client 1 based on the message 1602, and the enterprise WeChat client 1 presents to the user A.
  • an inquiry can be made for a group task of a specific deadline.
  • the inquiry message 1701 sent by the user A in the session interface 1700 may be "uncomplete group task before the @group task deadline is 11 months", including the identification content "@group task” and the inquiry content "cut-off"
  • the unfinished group task with a deadline of 11 months so that the enterprise WeChat server can determine the group whose deadline is earlier than November 1 and is incomplete according to the deadline and completion status of the group task in the group AA.
  • the task, and the related information is returned to the enterprise WeChat client 1 based on the message 1702, and presented to the user A by the enterprise WeChat client 1.
  • FIG. 18 is a schematic diagram of an active push and group task related notification message provided by an exemplary embodiment; as shown in FIG. 18, when the enterprise WeChat server determines that user A has two uncompleted group tasks, The corresponding notification message 1801 is sent to the enterprise WeChat client 1 corresponding to the user A, so that the enterprise WeChat client 1 displays the notification message 1801 in the session interface 1800, thereby implementing an active reminder to the user A.
  • FIG. 19 is a schematic diagram of another active push and group task related notification message provided by an exemplary embodiment; as shown in FIG.
  • the enterprise WeChat server determines that user B has an upcoming deadline (for example, When the group task has a deadline of no more than 3 days, the corresponding notification message 1901 may be sent to the enterprise WeChat client 2 corresponding to the user B, so that the notification message 1901 is displayed by the enterprise WeChat client 2 in the session interface 1900. Thereby realizing the active reminder to user B.
  • the notification message 1801 may be sent only to the user A, but not to other group members in the group AA; and in the embodiment shown in FIG. 19, the notification message 1901 Can be sent to all group members of group AA, and by adding a separate notification prompt identifier (such as "@B") for user B in the notification message 1901, such that even if group AA is masked (such as being activated)
  • a separate notification prompt identifier such as "@B”
  • the Enterprise WeChat client 2 can still send a receiving reminder to User B, thereby preventing User B 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; as shown in FIG. 20, the enterprise WeChat server receives a group member group such as user B and user C.
  • the corresponding WeChat client corresponding to all the group members of the group AA, such as the creator or other performers, or the group Wean client of the group AA, may be sent a corresponding notification message, such as an enterprise WeChat client.
  • a corresponding notification message 2001-2002 can be received to display the notification message 2001-2002 in the session interface 2000 by the enterprise WeChat client 1, thereby realizing an active reminder to the group member such as the user A.
  • the following operations may be implemented: in one case, switching to the group task management of the group AA The interface is viewed by the group members; in another case, the group task management interface of the group AA is switched, and the group tasks involved in the above message are marked for group members to view; Then, switching to the task information viewing interface, only the information of the group task (summary information or detailed information) involved in the above message is shown; or other schemes may be used, and the present specification does not limit this.
  • FIG. 21 is a schematic diagram of a template selection interface provided by an exemplary embodiment; a group member of group AA can view a template selection interface 2100 as shown in FIG. 21 through a corresponding enterprise WeChat client.
  • the template selection interface 2100 may include a template content layout preview map corresponding to a plurality of candidate group task templates.
  • the "More Templates" option in the interface 2100 can be selected by triggering the template to view other group task templates that are not temporarily displayed.
  • the group task template may be provided by the developer of the enterprise WeChat or by a specialized third party.
  • the group task template may be created by the user of the enterprise WeChat, uploaded to the enterprise WeChat server, and displayed by the enterprise WeChat server in the template selection interface 2100 for group members of the group AA or Group members of other groups view and use them.
  • FIG. 22 is a schematic diagram of a template binding interface provided by an exemplary embodiment. It is assumed that the group member of the group AA selects the “XX industry group task template” in the template selection interface 2100. In the template binding interface 2200 shown in FIG. 22, the corresponding template content layout preview image 2201 is shown. For viewing by members of this group.
  • the template binding interface 2200 can provide the group member with the binding option 2202. So that the group member can bind the "XX industry group task template" to the group AA by triggering the binding option 2202, and all group members in the group AA can pass the "XX" Industry Group Task Templates quickly create corresponding group tasks.
  • 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, the corresponding template may be displayed in the template binding interface 2300 shown in FIG. 23 .
  • the template content layout preview map 2301 is for viewing by the group members.
  • the template binding interface 2300 can provide the group member with the binding.
  • the XX industry group task template is bound to the group AA, and 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.
  • the group task management interface 2400 shown in FIG. 24 in addition to the group A creation area 2401 (which is equivalent to the group task creation area shown in FIG. 4), the user A can be provided. 401), so that user A can create a corresponding group task by manual input in the group task creation area 2401, and the group task management interface 2400 can further include a group task template trigger option 2402. Assume that the above-mentioned "XX industry group task template" is bound to the group AA.
  • variable parameters in the group task template are configured to quickly create a group task that meets the requirements of the "XX industry".
  • the group task management interface 2400 may include a group task batch import option 2403 for the user A to quickly and batch import the group tasks without manually creating them one by one.
  • the user A can record the description information of the group task in the notebook and the form tool in advance, such as the task topic, the task deadline, the task executor, etc., and generate a file recording the description information, such as a text file, a form file, and the like.
  • 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 correspondingly according to this.
  • the group task can effectively improve the efficiency of user A's group task creation.
  • FIG. 25 is a schematic structural diagram of an apparatus provided by an exemplary embodiment.
  • the device includes a processor 2502, an internal bus 2504, a network interface 2506, a memory 2508, and a non-volatile memory 2510, and of course may also include hardware required for other services.
  • the processor 2502 reads the corresponding computer program from the non-volatile memory 2510 into the memory 2508 and then operates to form an information acquisition device of the group task on the logical level.
  • one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each.
  • a logical unit which can also be a hardware or logic device.
  • the information acquiring apparatus of the group task may include:
  • the sending unit 2601 is configured to send a message by using a session corresponding to the group, where the message includes the identifier content and the query content for the group task in the group, where the identifier content is used to instruct the server to reply to the query content;
  • the reply content receiving unit 2602 receives the reply content returned by the server for the query content, and the reply content includes information of the group task.
  • the sending unit 2601 is specifically configured to:
  • the message is automatically sent according to the message content and the transmission period set by the user.
  • the message includes at least one of the following: a text message or an audio message;
  • the reply content includes at least one of the following: a text message or an audio message.
  • the creator and the performer of the group task are all group members of the group.
  • the group task is created and generated by a group member of the group in an associated function interface of the group.
  • the performer of the group task is determined by the creator of the group task by performing a selecting operation in a group member of the group;
  • the task is determined to be Group tasks within the group.
  • the message and the reply content are only visible to a sender of the message, and are invisible to other group members in the group.
  • it also includes:
  • the notification receiving unit 2603 receives a notification message that is automatically sent by the server for the group task, and 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.
  • it also includes:
  • the switching unit 2604 when detecting the triggering operation for the notification message, switches to the information presentation interface of the group task related to the notification message.
  • the group task is generated by the creator by configuring the group task template.
  • the group task template is pre-bound to the group.
  • it also includes:
  • the importing unit 2605 is configured to import a task record file in the group, where the task record file records description information of at least one group task;
  • the creating unit 2606 creates a group task related to the group in batch according to the description information recorded in the task record file.
  • the task record file includes any one of the following: a text file and a form file.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are 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.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • flash memory or other memory technology
  • compact disk read only memory CD-ROM
  • DVD digital versatile disk
  • Magnetic cassette tape disk storage
  • quantum memory graphene-based storage media or other magnetic storage devices or any other non-transporting media
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used to describe various information in one or more embodiments of the specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first information may also be referred to as the second information without departing from the scope of one or more embodiments of the present disclosure.
  • the second information may also be referred to as the first information.
  • the word "if” as used herein may be interpreted as "when” or "when” or "in response to a determination.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本说明书一个或多个实施例提供一种群组任务的信息获取方法及装置，该方法可以包括：通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。

Description

群组任务的信息获取方法及装置
本申请要求2017年12月08日递交的申请号为201711294078.9、发明名称为“群组任务的信息获取方法及装置”以及2018年03月28日递交的申请号为201810265592.8、发明名称为“群组任务的信息获取方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本说明书一个或多个实施例涉及通讯技术领域，尤其涉及一种群组任务的信息获取方法及装置。
背景技术
在相关技术中，移动化团体办公平台被越来越广泛地应用于企业、教育机构、政府机关等各类团体的办公过程，不仅能够提升用户之间的沟通效率、降低沟通成本，而且能够有效提升用户的事件处理效率和办公效率。例如，移动化团体办公平台可以实现任务功能，通过创建任务实现对相关事件的提醒和跟踪处理。
但是，移动化团体办公平台中的通讯功能与任务功能相互独立，用户需要在任务功能对应的任务管理界面进行任务管理，再从任务管理界面切换至通讯功能对应的会话界面进行沟通，造成用户的操作繁琐、效率低下。并且，当已存在的任务数量越来越多时，用户需要对任务管理界面中的任务进行仔细查看和筛选，往往难以高效、准确地获知希望了解的任务信息。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种群组任务的信息获取方法及装置。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种群组任务的信息获取方法，包括：
通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；
接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
根据本说明书一个或多个实施例的第二方面，提出了一种群组任务的信息获取装置，包括：
发送单元，通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；
答复内容接收单元，接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
附图说明
图1是一示例性实施例提供的一种群组任务系统的架构示意图；
图2是一示例性实施例提供的一种群组任务的信息获取方法的流程图；
图3是一示例性实施例提供的一种群组的会话界面的示意图；
图4是一示例性实施例提供的一种群任务管理界面的示意图；
图5是一示例性实施例提供的一种设置群任务的任务主题的示意图；
图6是一示例性实施例提供的一种设置群任务的执行者的示意图；
图7是一示例性实施例提供的一种已设定执行者的群任务管理界面的示意图；
图8是一示例性实施例提供的一种设置群任务的截止时间的示意图；
图9是一示例性实施例提供的另一种群任务管理界面的示意图；
图10是一示例性实施例提供的一种基于创建者的会话界面的示意图；
图11是一示例性实施例提供的一种基于执行者的会话界面的示意图；
图12是一示例性实施例提供的一种任务详情界面的示意图；
图13是一示例性实施例提供的又一种群任务管理界面的示意图；
图14是一示例性实施例提供的一种实现群任务管理的示意图；
图15是一示例性实施例提供的另一种实现群任务管理的示意图；
图16是一示例性实施例提供的又一种实现群任务管理的示意图；
图17是一示例性实施例提供的又一种实现群任务管理的示意图；
图18是一示例性实施例提供的一种主动推送与群任务相关的通知消息的示意图；
图19是一示例性实施例提供的另一种主动推送与群任务相关的通知消息的示意图；
图20是一示例性实施例提供的又一种主动推送与群任务相关的通知消息的示意图；
图21是一示例性实施例提供的一种模板选择界面的示意图；
图22是一示例性实施例提供的一种模板绑定界面的示意图；
图23是一示例性实施例提供的另一种模板绑定界面的示意图；
图24是一示例性实施例提供的另一种群任务管理界面的示意图；
图25是一示例性实施例提供的一种设备的结构示意图；
图26是一示例性实施例提供的一种群组任务的信息获取装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
图1是一示例性实施例提供的一种群组任务系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14和手机15等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现该应用的相关业务功能，比如当该服务器11运行移动化团体办公平台的程序时，可以实现为该移动化团体办公平台的服务端。而在本说明书一个或多个实施例的技术方案中，可由服务器11通过与手机13-15上运行的客户端进行配合，以实现基于群组任务的信息获取方案。
在本实施例中，移动化团体办公平台不仅可以实现通讯功能，还可以作为诸多其他功能的集成化功能平台，比如对于审批事件(如请假、办公物品申领、财务等审批事件)、考勤事件、任务事件、日志事件等团体内部事件的处理，再比如订餐、采购等团体外部事件的处理，本说明书一个或多个实施例并不对此进行限制。
较为具体地，移动化团体办公平台可以承载于相关技术中的即时通讯应用，比如企业即时通讯(Enterprise Instant Messaging，EIM)应用，例如Skype For
Figure PCTCN2018118870-appb-000001
Microsoft
Figure PCTCN2018118870-appb-000002
Figure PCTCN2018118870-appb-000003
等。当然，即时通讯功能仅为移动化团体办公平台支持的通讯功能之一，该移动化团体办公平台还能够实现更多诸如上述的其他功能，此处不再赘述。
手机13-15只是用户可以使用的一种类型的电子设备。实际上，用户显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本说明书一个或多个实施例并不对此进行限制。在运行过程中，该电子设备可以运行某一应用的客户端侧的程序，以实现该应用的相关业务功能，比如当该电子设备运行移动化团体办公平台的程序时，可以实现为该移动化团体办公平台的客户端。
需要指出的是：移动化团体办公平台的客户端的应用程序可以被预先安装在电子设备上，使得该客户端可以在该电子设备上被启动并运行；当然，当采用诸如HTML5技术的在线“客户端”时，无需在电子设备上安装相应的应用程序，即可获得并运行该客户端。
而对于手机13-15与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。同时，手机13-15等电子设备之间也可以通过该网络12进行通讯交互，比如在任意两台电子设备之间建立单聊会话；或者，多个用户可以参与同一群组，他们使用的多台电子设备可以参与至该同一群组对应的会话，使得任一用户可以通过自身的电子设备向该会话中的其他所有用户发送通讯消息。
图2是一示例性实施例提供的一种群组任务的信息获取方法的流程图。如图2所示，该方法应用于电子设备，可以包括以下步骤：
步骤202，通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复。
在一实施例中，可以在所述会话对应的会话界面检测到用户输入信息时，将所述用户输入信息作为所述消息的消息内容进行发送，即消息可由用户手动输入得到。
在一实施例中，可以按照用户设定的消息内容和发送周期，自动发送所述消息，比如该发送周期可以包括每天、每周、每月等，可由用户根据实际需求进行设定。其中，用户可以设定一个或多个发送周期，且每一周期对应相同或不同的消息；例如，用户可以同时设定发送周期为每天和每周，使得每天自动发送第一内容的消息，且每周自动发送第二内容的消息。
在一实施例中，标识内容可以包括预定义的任意内容，本说明书并不对此进行限制。例如，标识内容可以采用“特殊字符+名称”的形式，比如特殊字符可以为@、#等不常用的字符，而名称可以为服务器、机器人等预先约定用于指代服务器的信息，因而标识内容可以为诸如“@服务器”、“#机器人#”等。再例如，标识内容可以直接采用预先约定用于指代服务器的信息，比如“群组秘书”等。
在一实施例中，电子设备上可以运行移动化团体办公平台的客户端，该客户端可以提供群组通讯功能和任务管理功能，由该群组通讯功能实现群组的创建以及群组成员之间的通讯操作，并由该任务管理功能实现任务的管理。
在一实施例中，群组任务区别于其他类型的任务，群组任务可供用户在与群组相关的功能界面内实现创建、查看等管理操作，便于群组任务的创建者、执行者等关联用户之间基于该群组的会话实现快捷沟通。
在一实施例中，群组任务的创建者、执行者等关联用户可以均为所述群组的群组成员，使得这些关联用户可以基于该群组的会话实现快捷沟通。
在一实施例中，所述群组任务可由所述群组的群组成员在所述群组的关联功能界面中创建生成。例如，该关联功能界面可以包括任务管理界面，该任务管理界面可供群组成员创建新的群组任务、查看已创建的群组任务等，且该群组的会话界面可以包括该任务管理界面的入口，以便群组成员在任务管理界面与会话界面之间实现快速切换。当然，关联功能界面还可以包括与群组相关的其他形式的功能界面，本说明书并不对此进行限制。
在一实施例中，所述群组任务的执行者可由所述群组任务的创建者通过在所述群组的群组成员中实施选取操作而确定，比如该创建者可以选取至少一个群组成员、以作为该群组任务的执行者；其中，当创建者在创建群组任务时，可以仅向该创建者提供该群组的群组成员列表，从而使得创建者与执行者均被限制于该群组的群组成员中。此外，所述群组任务的创建者如果未实施所述选取操作，所述群组的所有群组成员被默认为所述群组任务的执行者。
在一实施例中，当创建者为群组内的群组成员时，该创建者才能够进入与群组相关的功能界面，以完成对群组任务的创建操作。
在一实施例中，当任一任务的创建界面与所述群组无关，且所述任一任务的创建者、执行者均为所述群组的群组成员时，所述任一任务可以被确定为所述群组内的群组任务。例如，虽然创建者并未在与群组相关的功能界面创建任务，但是如果创建者和被选中的 执行者均属于同一群组，可以将该任务设定为与该同一群组相关的群组任务；其中，该设定操作可以为自动操作，或者可以向创建者发起设定提醒，并在创建者响应于该设定提醒时实施设定操作。
在一实施例中，群组的群组成员可以具有相同的团体归属信息(比如归属于同一企业)，即该群组为团体内群组。在一实施例中，群组的群组成员可以具有不完全相同的团体归属信息(比如分别归属于多个企业)，即该群组为跨团体群组。在一实施例中，群组可以与团体无关，比如亲戚或朋友之间创建的群组等。
步骤204，接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
在一实施例中，消息、答复内容可以采用任意类型，本说明书并不对此进行限制。比如，消息可以包括以下至少之一：文字消息或音频消息，答复内容可以包括以下至少之一：文字消息或音频消息。在一种情况下，消息与答复内容可以为相同类型，比如当消息采用文字消息时，答复内容也为文字消息，当消息为音频消息时，答复内容也为音频消息。在另一种情况下，消息与答复内容可以不存在类型关联，比如当消息采用文字消息时，答复内容可以为文字消息、也可以为音频消息。
在一实施例中，当所述消息包含所述标识内容时，所述消息和所述答复内容可以仅对所述消息的发送方可见、对所述群组中的其他群组成员不可见，从而在满足发送方的询问需求的情况下，避免对其他群组成员造成不必要的干扰。
在一实施例中，可以接收所述服务器自动发送的针对所述群组任务的通知消息；例如，所述通知消息可以包括以下至少之一：周期性统计信息、针对尚未完成的群组任务的提示信息、针对临近完成期限的群组任务的提示信息、针对已完成的群组任务的完成提示信息等，本说明书并不对此进行限制。
在一实施例中，当检测到针对所述通知消息的触发操作时，可以切换至与所述通知消息相关的群组任务的信息展示界面，以便于查看该群组任务的概要信息或详情信息。
在一实施例中，所述群组任务可由创建者通过对群组任务模板进行配置而生成。换言之，可以预先创建若干备选的群组任务模板，比如这些群组任务模板分别适用于不同职位、不同场景、不同行业或不同目的等，使得创建者可以根据实际需求选取恰当的群组任务模板后，通过配置该群组任务模板中的可配置变量，即可快速生成符合实际需求的群组任务，简化创建者的操作。同时，在创建群组任务的过程中，群组任务模板还可以对创建者起到一定的教学和引导作用，尤其是对于初次或较少创建群组任务的创建者 而言，可以协助创建者完成对群组任务的快速创建，从而降低创建者的学习门槛。
在一实施例中，创建者可以随意使用所有的群组任务模板。在另一实施例中，所述群组任务模板被预先绑定至所述群组，即创建者只能够对绑定至该群组的群组任务模板进行配置，而不能够对其他群组任务模板进行随意使用，从而实现了对群组任务模板的使用管理。
在一实施例中，可由群组的群主、管理员等管理成员对群组任务模板进行管理，比如将群组任务模板绑定至群组，或者将群组任务模板与群组解绑定。相应地，群组成员可以使用被绑定至该群组的群组任务模板，以快速创建相应的群组任务。
在一实施例中，群组任务模板可以由上述的通讯应用或移动化团体办公平台的开发方提供，以供该通讯应用或移动化团体办公平台的使用者进行获取和使用。在另一实施例中，群组任务模板可由上述的通讯应用或移动化团体办公平台的使用者创建，并分享至其他使用者进行使用；例如，该通讯应用或移动化团体办公平台可以提供群组任务模板的共享平台，使用者可以通过该共享平台对自己创建的群组任务模板进行共享，也可以获取其他使用者共享的群组任务模板。
在一实施例中，可以在所述群组内导入任务记录文件，所述任务记录文件中记录有至少一项群组任务的描述信息；然后，根据所述任务记录文件中记录的描述信息，批量创建与所述群组相关的群组任务。其中，所述任务记录文件可以包括下述任一：文本文件、表格文件等，本说明书并不对此进行限制。通过预先将群组任务的描述信息记录于任务记录文件中，使得群组成员可以通过向群组中导入该任务记录文件，快速、批量创建相应的群组任务，而无需群组成员分别、单独创建每个群组任务，有助于提升对群组任务的创建效率。
在一实施例中，群组成员在导入任务记录文件时，可以指定采用的群组任务模板，使得创建的群组任务均为基于该群组任务模板而生成，有助于确保生成的群组任务在样式、格式等方面满足该群组成员的实际需求。
为了便于理解，以企业即时通讯应用“企业微信”为例，对本说明书一个或多个实施例的技术方案进行说明。假定手机13和手机14上运行有企业微信客户端、服务器11上运行有企业微信服务端，手机13上登录有用户A的注册账号、使得手机13被配置为企业微信客户端1，手机14上登录有用户B的注册账号、使得手机14被配置为企业微信客户端2。其中，假定用户A、用户B均为群组AA的群组成员，可以基于该群组AA实现对群组任务的管理操作。
图3是一示例性实施例提供的一种群组的会话界面的示意图。假定在手机13运行的企业微信客户端1上，可以向用户A呈现出如图3所示的会话界面300，该会话界面300对应于用户A所处的群组AA。会话界面300可以包括如图3所示的群任务图标301，该群任务图标301可以作为相应的功能界面的操作入口，使得在检测到针对该群任务图标301的触发操作时，可以切换至如图4所示的群任务管理界面400。
图4是一示例性实施例提供的一种群任务管理界面的示意图。在本说明书的实施例中，群组任务与群任务均为同一类任务的不同叫法，本说明书并不对此进行限制。在如图4所示的群任务管理界面400中，可以包括群任务创建区域401，该群任务创建区域401可供用户A在该群组AA内创建新的群任务。群任务管理界面400还可以展示出群组AA内已创建的群任务，比如图4所示的群任务402、群任务403等。
在一实施例中，群任务402的任务主题为“周二前完成设计方案”、创建者为用户A、执行者为用户B、任务创建时间为“10-18 15:30”、截止时间为“10月24日周二18:00”、回复状态为“暂无回复”、完成状态为“B未完成”，当然在其他实施例中可以仅包含上述内容的一部分，或者还可以包含其他类型的任务信息，本说明书并不对此进行限制。类似地，群任务403的任务主题为“X项目产品方案”、创建者为用户C、执行者为用户A等3人、任务创建时间为“10-12 14:20”、截止时间为“10月20日周五12:00”、回复状态为“2条回复”、完成状态为“1/3已完成”。
在一实施例中，图4中可以仅示出群任务402、群任务403等的部分信息，而用户A可以通过触发该群任务402或群任务403，以查看任务详情。例如，在群任务403中的“2条回复”的具体回复内容、“A等3人”的3个执行者的信息、“1/3人已完成”中的已完成者和未完成者的信息等，均可以在任务详情中予以具体呈现。
在一实施例中，群任务创建区域401的输入框内可以示出诸如“添加一个群任务…”的提示信息，以协助用户A完成群任务的创建操作。例如，图5是一示例性实施例提供的一种设置群任务的任务主题的示意图；通过触发群任务创建区域401的输入框，用户A可以在该输入框内输入所需创建的群任务的任务主题，比如该任务主题可以为图5所示的“Y项目设计稿”或其他任意内容。
在一实施例中，群任务创建区域401可以包括执行者设置图标501，可供用户A为所需创建的群任务设置执行者。例如，图6是一示例性实施例提供的一种设置群任务的执行者的示意图；当检测到针对执行者设置图标501的触发操作后，可以切换至如图6所示的执行者设置界面600，该执行者设置界面600可以包括右侧的备选用户列表601 和左侧的已选用户列表602。其中，备选用户列表601可以包括群组AA的所有群组成员，比如用户A、用户B、用户C、用户D和用户E等；假定用户A选取用户B和用户C为执行者，在用户B、用户C在备选用户列表601中对应的选择框“○”中将出现选中标记“√”，且用户B和用户C将被添加至左侧的已选用户列表602中。当用户A希望取消对用户B或用户C的选择时，可以重新触发相应的选择框“○”；或者，在已选用户列表602中，用户B、用户C均存在对应的删除标记“×”，可以通过触发该删除标记“×”来取消对相应用户的选择。
图7是一示例性实施例提供的一种已设定执行者的群任务管理界面的示意图。在用户A实施了对执行者的选取后，可以对如图5所示的执行者设置图标501进行替换，以提示用户A已经实施了该选取操作，避免在实施其他操作后发生遗忘。例如，当用户A将用户B、用户C选取为执行者时，可以将如图5所示的执行者设置图标501替换为被选取为执行者的用户B、用户C的头像图标，以使得用户A能够快速确定已选取的至少一部分执行者。当然，由于群任务创建区域401往往有限，因而展示的头像数量可以存在一定限制，比如限制为不超过3个头像，而超出的头像可以不展示或采用“…”予以省略。
在一实施例中，群任务创建区域401可以包括期限设置图标502，可供用户A为所需创建的群任务设置截止时间。例如，图8是一示例性实施例提供的一种设置群任务的截止时间的示意图；当检测到针对期限设置图标502的触发操作后，可以切换至如图8所示的期限设置界面800，该期限设置界面600可以包括日期选择区域和时刻设定区域，可分别供用户设定作为截止时间的日期和时刻，比如可以设定为图8所示的2017年10月30日16:00。其中，期限设置界面800可以提供如图8所示的“无截止时间”选项，从而不为相应的群任务设定截止时间。与执行者设置图标501相类似的，在用户A设置了群任务的截止时间后，也可以对期限设置图标502进行替换，以对用户A进行提示，此处不再赘述。
图9是一示例性实施例提供的另一种群任务管理界面的示意图。基于用户A的上述操作，创建得到新的群任务可以被展示于如图9所示的群任务管理界面400中，比如该新的群任务可以为图9所示的群任务404。其中，群任务404的任务主题为“Y项目设计稿”、创建者为用户A、执行者为用户B等2人、任务创建时间为“10-18 17:30”、截止时间为“10月30日周一16:00”、回复状态为“暂无回复”、完成状态为“0/2已完成”。
图10是一示例性实施例提供的一种基于创建者的会话界面的示意图。基于用户A在上述实施例中创建的群任务，企业微信客户端1可以将该群任务发布在群组AA的会话界面300中；例如图10所示，该群任务可以被作为用户A发出的一条消息，被展示于会话界面300中。当然，用户A还可以通过触发会话界面300中的群任务图标301，切换至如图9所示的群任务管理界面400，以查看该消息对应的群任务404。
图11是一示例性实施例提供的一种基于执行者的会话界面的示意图。假定在手机14运行的企业微信客户端2上，可以向用户B呈现出如图11所示的会话界面1100，该会话界面1100展示出由用户A发出的消息1101，该消息1101的内容即为如图9所示的群任务404。当然，由于消息1101的展示区域较小，因而可以仅示出该群任务404的部分信息，比如任务主题、执行者、截止时间等。
当检测到用户B触发消息1101时，可以向用户B展示相应群任务的任务详情。例如，图12是一示例性实施例提供的一种任务详情界面的示意图；基于对消息1101的触发操作，可以切换至如图12所示的任务详情界面1200，以在该任务详情界面1200上展示出相应群任务的任务详情，包括任务主题为“Y项目设计稿”、该群任务的创建者为用户A、创建时刻为“刚刚(如1分钟之内)”、截止时间为“10月30日周一16:00”、剩余天数为“剩余12天”、执行者为用户B和用户C、完成状态为“未完成”、相关群组为“群组AA”等。
其中，在任务主题“Y项目设计稿”的左侧包括状态设置选项，该状态设置选项在图12中呈现为“□”；当该状态设置选项展示为如图12所示时，表明相应的群任务的完成状态为“未完成”；当用户B触发该状态设置选项时，可以在“□”内添加标记“√”，且相应的群任务的完成状态切换为“已完成”；当然，用户B可以通过触发“已完成”状态的状态设置选项，使得“□”内的标记“√”被取消，从而将相应的群任务的完成状态切换为“未完成”。
在一实施例中，任务详情界面1200展示的“来自群组：群组AA”可以被设置为可触发状态，使得用户B可以通过触发该显示内容，快速切换至群组AA对应的会话界面(比如上述的会话界面1100)。
在一实施例中，任务详情界面1200可以包括如图12所示的子任务创建选项(即“+子任务”)，使得用户B可以据此创建与群任务“Y项目设计稿”相关的一个或多个子任务。
在一实施例中，群组AA的会话界面1100可以包括群任务图标1102，与上述会话 界面300中的群任务图标301相类似的，用户B可以通过触发该群任务图标1102切换至如图13所示的群任务管理界面1300，以查看和管理群组AA中的群任务。
在一实施例中，对应于图11所示的消息1101，群任务管理界面1300可以示出相应的群任务1301，且该群任务管理界面1300还可以示出其他的群任务1302、群任务1303等。其中，群任务管理界面1300可以包括群任务创建区域1304，可供用户B创建群组AA内的群任务，该过程与用户A的上述创建过程类似，此处不再赘述。
在一实施例中，群任务管理界面1300可以示出群组AA中所有的群任务，比如群任务1301、群任务1302是用户B作为执行者的群任务，而群任务1303是与用户B无关(用户B既不是创建者，也不是执行者或其他角色)的群任务，但是都可以在该群任务管理界面1300上予以展示。
其中，由于群任务1301-1302与用户B相关，因而可以向用户B提供针对相应群任务的状态设置选项，该状态设置选项呈现为与图12中相同的“□”；当该状态设置选项展示为如图13所示时，表明相应的群任务的完成状态为“未完成”；当用户B触发该状态设置选项时，可以在“□”内添加标记“√”，且相应的群任务的完成状态切换为“已完成”；当然，用户B可以通过触发“已完成”状态的状态设置选项，使得“□”内的标记“√”被取消，从而将相应的群任务的完成状态切换为“未完成”。而由于群任务1303与用户B无关，因而可以不向用户B提供针对相应群任务的状态设置选项，或者向用户B提供如图13所示的不可操作的状态设置选项“■”，以避免用户B误操作。
在一实施例中，群任务管理界面1300展示的群任务可以包括多种类型，比如尚未完成的群任务、已完成的群任务、已关闭的群任务等，用户B可以选择展示所有类型的群任务，也可以选择仅展示部分类型的群任务，本说明书并不对此进行限制。例如，图13中选择仅展示出尚未完成的群任务，因而屏蔽了已完成的群任务、已关闭的群任务等其他类型的群任务。
对于群组AA中的其他群组成员，当作为群任务的创建者时，可以参考上述用户A的相关描述，而作为群任务的执行者或无关人员时，可以参考上述用户B的相关描述，此处不再一一赘述。
当群组AA中的群任务数量较多时，如果仅仅依靠查看群组AA的群任务管理界面，可能难以高效地实施群任务管理操作，需要手动翻看各个群任务。因此，本说明书提供了针对群任务的高效管理方案。图14是一示例性实施例提供的一种实现群任务管理的示 意图；如图14所示，假定在用户A对应的会话界面1400中，用户A可以在该会话界面1400内发出针对群任务的询问消息1401，该过程与发送消息的过程相同。
在一实施例中，询问消息1401可以包括两个部分：标识内容和询问内容。其中，标识内容用于由企业微信客户端1或企业微信服务端(由企业微信客户端1发送至企业微信服务端)进行辨别，以将询问消息1401与普通的消息予以区分，比如该标识内容可以包括“@群任务”，当然本说明书并不限制该标识内容的具体形式。询问内容可以包括如图14所示的“现在群任务进度怎么样？”，即用户A实际希望针对群任务发起询问的内容。
在一实施例中，当企业微信客户端1识别出标识内容时，可以将询问消息1401或询问内容通过区别于普通的消息的方式(比如添加特定的报文标识、采用特定的传输端口、采用特定的传输链路等，本说明书并不对此进行限制)发送至企业微信服务端，使得企业微信服务端并不将其转发至其他群组成员，而是针对询问内容予以解析，并返回相应的询问结果。在另一实施例中，企业微信服务端在接收到企业微信客户端1发送的询问消息1401后，可以自动识别出标识内容和询问内容，并通过解析该询问内容，返回相应的询问结果。
在一实施例中，询问结果可以被采用消息的形式呈现给用户A。例如图14所示，询问结果可以被包含于消息1402中，由企业微信客户端1接收并展示于会话界面1400中，而该消息1402的发送方可以被设置为区别于群组AA的群组成员的特殊发送方，比如图14所示的“机器人”或其他形式，本说明书并不对此进行限制。
在一实施例中，当用户A向企业微信服务端发起询问时，询问消息1401不会被发送至群组AA的其他群组成员，且包含询问结果的消息1402仅被发送至用户A、同样不会被发送至群组AA的其他群组成员，从而避免对其他群组成员造成干扰。当然，在一些实施例中，询问消息1401和消息1402均可以被发送至所有群组成员，本说明书并不对此进行限制。
用户A可以询问与群任务相关的任何内容，企业微信服务端均可以做出相应的解答与反馈。比如除了图14中较为笼统的总体进度之外，还可以针对特定的一个或多个群组成员进行询问。例如图15所示，用户A在会话界面1500中发出的询问消息1501可以为“@群任务B的群任务进度”，包括标识内容“@群任务”和询问内容“B的群任务进度”，以使得企业微信服务端可以针对用户B在群组AA中的群任务而确定相应的处理进度信息，这些信息可以被包含于消息1502而返回至企业微信客户端1，由企业微信 客户端1呈现至用户A。
在一实施例中，可以针对特定类型的群任务进行询问。例如图16所示，用户A在会话界面1600中发出的询问消息1601可以为“@群任务未完成的群任务”，包括标识内容“@群任务”和询问内容“未完成的群任务”，以使得企业微信服务端可以确定群组AA中的未完成群任务，并将相关信息基于消息1602而返回至企业微信客户端1，由企业微信客户端1呈现至用户A。
在一实施例中，可以针对特定截止期限的群任务进行询问。例如图17所示，用户A在会话界面1700中发出的询问消息1701可以为“@群任务截止期限在11月之前的未完成群任务”，包括标识内容“@群任务”和询问内容“截止期限在11月之前的未完成群任务”，以使得企业微信服务端可以根据群组AA中群任务的截止日期和完成状态，确定出截止日期早于11月1日且处于未完成状态的群任务，并将相关信息基于消息1702而返回至企业微信客户端1，由企业微信客户端1呈现至用户A。
除了对群组成员的主动询问进行响应之外，企业微信服务端还可以向群组成员主动推送与群任务相关的通知消息，以便于群组成员及时了解相关信息。例如，图18是一示例性实施例提供的一种主动推送与群任务相关的通知消息的示意图；如图18所示，企业微信服务端确定用户A存在两个未完成的群任务时，可以向用户A对应的企业微信客户端1发送相应的通知消息1801，以由企业微信客户端1在会话界面1800中示出该通知消息1801，从而实现对用户A的主动提醒。再例如，图19是一示例性实施例提供的另一种主动推送与群任务相关的通知消息的示意图；如图19所示，企业微信服务端确定用户B存在一个即将到达截止期限(比如与截止期限相隔不超过3天)的群任务时，可以向用户B对应的企业微信客户端2发送相应的通知消息1901，以由企业微信客户端2在会话界面1900中示出该通知消息1901，从而实现对用户B的主动提醒。
在如图18所示的实施例中，通知消息1801可以仅发送至用户A，而不发送至群组AA中的其他群组成员；而在如图19所示的实施例中，通知消息1901可以被发送至群组AA的所有群组成员，并通过在该通知消息1901中添加针对用户B的单独通知提示标识(如“@B”)，使得即便群组AA被屏蔽(比如被启动“免打扰”功能)，企业微信客户端2仍然可以向用户B发出接收提醒，从而避免用户B由于某些原因而忽略该通知消息1901。
图20是一示例性实施例提供的又一种主动推送与群任务相关的通知消息的示意图；如图20所示，企业微信服务端在接收到诸如用户B、用户C等群组成员对于群任务的管 理操作时，可以向相关群任务的关联者(如创建者或其他执行者等)或群组AA的所有群组成员对应的企业微信客户端发送相应的通知消息，比如企业微信客户端1可以收到相应的通知消息2001-2002，以由企业微信客户端1在会话界面2000中示出该通知消息2001-2002，从而实现对用户A等群组成员的主动提醒。
在一实施例中，当检测到群组成员触发上述实施例中的消息1402～1702或通知消息1801～2001时，可以实施下述操作：一种情况下，切换至群组AA的群任务管理界面，由群组成员进行查看；另一种情况下，切换至群组AA的群任务管理界面，并对上述消息中涉及的群任务进行标记，以便于群组成员进行查看；又一种情况下，切换至任务信息查看界面，仅示出上述消息涉及的群任务的信息(概要信息或者详情信息)；或者，还可以采用其他方案，本说明书并不对此进行限制。
在一实施例中，除了直接在如图4所示的群任务创建区域401中进行手动输入，以创建相应的群任务之外，还可以向群组AA的群组成员提供群任务模板，从而能够更为快速、便捷地创建群任务。例如，图21是一示例性实施例提供的一种模板选择界面的示意图；群组AA的群组成员可以通过对应的企业微信客户端，查看到如图21所示的模板选择界面2100，该模板选择界面2100可以包括若干备选的群任务模板对应的模板内容布局预览图。进一步地，还可以通过触发模板选择界面2100中的“更多模板”选项，以查看其他暂时未展示的群任务模板。
在一实施例中，群任务模板可以由企业微信的开发方提供，或者由专门的第三方提供。在另一实施例中，群任务模板可由企业微信的使用者创建后，上传至企业微信服务端，并由企业微信服务端展示于模板选择界面2100中，以供群组AA的群组成员或其他群组的群组成员进行查看、使用。
图22是一示例性实施例提供的一种模板绑定界面的示意图。假定群组AA的群组成员选取了模板选择界面2100中的“XX行业群任务模板”，可以在如图22所示的模板绑定界面2200中，示出相应的模板内容布局预览图2201，以供该群组成员进行查看。当该群组成员属于该群组AA中的管理成员时，即该群组成员具备针对该群组AA的群任务模板管理权限，模板绑定界面2200可以向该群组成员提供绑定选项2202，使得该群组成员可以通过触发该绑定选项2202，将上述的“XX行业群任务模板”绑定至该群组AA，则该群组AA中的所有群组成员均可以通过该“XX行业群任务模板”快捷地创建相应的群任务。
图23是一示例性实施例提供的另一种模板绑定界面的示意图。与图22类似地，当 群组AA的群组成员选取了模板选择界面2100中的“XX行业群任务模板”时，可以在如图23所示的模板绑定界面2300中，示出相应的模板内容布局预览图2301，以供该群组成员进行查看。当该群组成员并非该群组AA中的管理成员时，即该群组成员并不具备针对该群组AA的群任务模板管理权限，模板绑定界面2300可以向该群组成员提供绑定请求选项2302，使得该群组成员可以通过触发该绑定选项2302，向该群组AA中的管理成员发送绑定请求消息，而该管理成员可以通过触发该绑定请求消息，将上述的“XX行业群任务模板”绑定至该群组AA，则该群组AA中的所有群组成员均可以通过该“XX行业群任务模板”快捷地创建相应的群任务。
图24是一示例性实施例提供的另一种群任务管理界面的示意图。当群组AA存在绑定的群任务模板时，在如图24所示的群任务管理界面2400中，除了可以向用户A提供群任务创建区域2401(相当于图4所示的群任务创建区域401)，使得用户A可以在该群任务创建区域2401中通过手动输入而创建相应的群任务，该群任务管理界面2400还可以包括群任务模板触发选项2402。假定上述的“XX行业群任务模板”被绑定至群组AA，当检测到用户A触发群任务模板触发选项2402时，可以调用该“XX行业群任务模板”，从而通过对该“XX行业群任务模板”中的变量参数进行配置，即可快捷地创建符合“XX行业”需求的群任务。
在一实施例中，群任务管理界面2400可以包括群任务批量导入选项2403，以供用户A快速、批量导入群任务，而无需一一手动创建。其中，用户A可以事先在记事本、表格工具中记载群任务的描述信息，比如任务主题、任务截止时刻、任务执行者等，并生成记录有这些描述信息的文件，比如文本文件、表格文件等；然后，通过触发群任务批量导入选项2403，并选取上述的文本文件或表格文件，企业微信客户端1或企业微信服务端可以解析文件中记录的群任务的描述信息，并据此批量创建相应的群任务，能够有效地提升用户A对群任务的创建效率。
图25是一示例性实施例提供的一种设备的示意结构图。请参考图25，在硬件层面，该设备包括处理器2502、内部总线2504、网络接口2506、内存2508以及非易失性存储器2510，当然还可能包括其他业务所需要的硬件。处理器2502从非易失性存储器2510中读取对应的计算机程序到内存2508中然后运行，在逻辑层面上形成群组任务的信息获取装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图26，在软件实施方式中，该群组任务的信息获取装置可以包括：
发送单元2601，通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；
答复内容接收单元2602，接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
可选的，所述发送单元2601具体用于：
当所述会话对应的会话界面检测到用户输入信息时，将所述用户输入信息作为所述消息的消息内容进行发送；
或者，按照用户设定的消息内容和发送周期，自动发送所述消息。
可选的，
所述消息包括以下至少之一：文字消息或音频消息；
所述答复内容包括以下至少之一：文字消息或音频消息。
可选的，所述群组任务的创建者、执行者均为所述群组的群组成员。
可选的，所述群组任务由所述群组的群组成员在所述群组的关联功能界面中创建生成。
可选的，所述群组任务的执行者由所述群组任务的创建者通过在所述群组的群组成员中实施选取操作而确定；
其中，当所述群组任务的创建者未实施所述选取操作时，所述群组的所有群组成员被默认为所述群组任务的执行者。
可选的，当任一任务的创建界面与所述群组无关，且所述任一任务的创建者、执行者均为所述群组的群组成员时，所述任一任务被确定为所述群组内的群组任务。
可选的，当所述消息包含所述标识内容时，所述消息和所述答复内容仅对所述消息的发送方可见、对所述群组中的其他群组成员不可见。
可选的，还包括：
通知接收单元2603，接收所述服务器自动发送的针对所述群组任务的通知消息；所述通知消息包括以下至少之一：
周期性统计信息、针对尚未完成的群组任务的提示信息、针对临近完成期限的群组任务的提示信息、针对已完成的群组任务的完成提示信息。
可选的，还包括：
切换单元2604，当检测到针对所述通知消息的触发操作时，切换至与所述通知消息 相关的群组任务的信息展示界面。
可选的，所述群组任务由创建者通过对群组任务模板进行配置而生成。
可选的，所述群组任务模板被预先绑定至所述群组。
可选的，还包括：
导入单元2605，在所述群组内导入任务记录文件，所述任务记录文件中记录有至少一项群组任务的描述信息；
创建单元2606，根据所述任务记录文件中记录的描述信息，批量创建与所述群组相关的群组任务。
可选的，所述任务记录文件包括下述任一：文本文件、表格文件。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而 且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (28)

  1. 一种群组任务的信息获取方法，其特征在于，包括：
    通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；
    接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述通过群组对应的会话发送消息，包括：
    当所述会话对应的会话界面检测到用户输入信息时，将所述用户输入信息作为所述消息的消息内容进行发送；
    或者，按照用户设定的消息内容和发送周期，自动发送所述消息。
  3. 根据权利要求1所述的方法，其特征在于，
    所述消息包括以下至少之一：文字消息或音频消息；
    所述答复内容包括以下至少之一：文字消息或音频消息。
  4. 根据权利要求1所述的方法，其特征在于，所述群组任务的创建者、执行者均为所述群组的群组成员。
  5. 根据权利要求1所述的方法，其特征在于，所述群组任务由所述群组的群组成员在所述群组的关联功能界面中创建生成。
  6. 根据权利要求5所述的方法，其特征在于，所述群组任务的执行者由所述群组任务的创建者通过在所述群组的群组成员中实施选取操作而确定；
    其中，当所述群组任务的创建者未实施所述选取操作时，所述群组的所有群组成员被默认为所述群组任务的执行者。
  7. 根据权利要求1所述的方法，其特征在于，当任一任务的创建界面与所述群组无关，且所述任一任务的创建者、执行者均为所述群组的群组成员时，所述任一任务被确定为所述群组内的群组任务。
  8. 根据权利要求1所述的方法，其特征在于，当所述消息包含所述标识内容时，所述消息和所述答复内容仅对所述消息的发送方可见、对所述群组中的其他群组成员不可见。
  9. 根据权利要求1所述的方法，其特征在于，还包括：
    接收所述服务器自动发送的针对所述群组任务的通知消息；所述通知消息包括以下 至少之一：
    周期性统计信息、针对尚未完成的群组任务的提示信息、针对临近完成期限的群组任务的提示信息、针对已完成的群组任务的完成提示信息。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    当检测到针对所述通知消息的触发操作时，切换至与所述通知消息相关的群组任务的信息展示界面。
  11. 根据权利要求1所述的方法，其特征在于，所述群组任务由创建者通过对群组任务模板进行配置而生成。
  12. 根据权利要求11所述的方法，其特征在于，所述群组任务模板被预先绑定至所述群组。
  13. 根据权利要求1所述的方法，其特征在于，还包括：
    在所述群组内导入任务记录文件，所述任务记录文件中记录有至少一项群组任务的描述信息；
    根据所述任务记录文件中记录的描述信息，批量创建与所述群组相关的群组任务。
  14. 根据权利要求13所述的方法，其特征在于，所述任务记录文件包括下述任一：文本文件、表格文件。
  15. 一种群组任务的信息获取装置，其特征在于，包括：
    发送单元，通过群组对应的会话发送消息，所述消息包含标识内容和针对所述群组内的群组任务的询问内容，所述标识内容用于指示服务器对所述询问内容予以答复；
    答复内容接收单元，接收所述服务器针对所述询问内容返回的答复内容，所述答复内容包括所述群组任务的信息。
  16. 根据权利要求15所述的装置，其特征在于，所述发送单元具体用于：
    当所述会话对应的会话界面检测到用户输入信息时，将所述用户输入信息作为所述消息的消息内容进行发送；
    或者，按照用户设定的消息内容和发送周期，自动发送所述消息。
  17. 根据权利要求15所述的装置，其特征在于，
    所述消息包括以下至少之一：文字消息或音频消息；
    所述答复内容包括以下至少之一：文字消息或音频消息。
  18. 根据权利要求15所述的装置，其特征在于，所述群组任务的创建者、执行者均为所述群组的群组成员。
  19. 根据权利要求15所述的装置，其特征在于，所述群组任务由所述群组的群组成员在所述群组的关联功能界面中创建生成。
  20. 根据权利要求19所述的装置，其特征在于，所述群组任务的执行者由所述群组任务的创建者通过在所述群组的群组成员中实施选取操作而确定；
    其中，当所述群组任务的创建者未实施所述选取操作时，所述群组的所有群组成员被默认为所述群组任务的执行者。
  21. 根据权利要求15所述的装置，其特征在于，当任一任务的创建界面与所述群组无关，且所述任一任务的创建者、执行者均为所述群组的群组成员时，所述任一任务被确定为所述群组内的群组任务。
  22. 根据权利要求15所述的装置，其特征在于，当所述消息包含所述标识内容时，所述消息和所述答复内容仅对所述消息的发送方可见、对所述群组中的其他群组成员不可见。
  23. 根据权利要求15所述的装置，其特征在于，还包括：
    通知接收单元，接收所述服务器自动发送的针对所述群组任务的通知消息；所述通知消息包括以下至少之一：
    周期性统计信息、针对尚未完成的群组任务的提示信息、针对临近完成期限的群组任务的提示信息、针对已完成的群组任务的完成提示信息。
  24. 根据权利要求23所述的装置，其特征在于，还包括：
    切换单元，当检测到针对所述通知消息的触发操作时，切换至与所述通知消息相关的群组任务的信息展示界面。
  25. 根据权利要求15所述的装置，其特征在于，所述群组任务由创建者通过对群组任务模板进行配置而生成。
  26. 根据权利要求25所述的装置，其特征在于，所述群组任务模板被预先绑定至所述群组。
  27. 根据权利要求15所述的装置，其特征在于，还包括：
    导入单元，在所述群组内导入任务记录文件，所述任务记录文件中记录有至少一项群组任务的描述信息；
    创建单元，根据所述任务记录文件中记录的描述信息，批量创建与所述群组相关的群组任务。
  28. 根据权利要求27所述的装置，其特征在于，所述任务记录文件包括下述任一： 文本文件、表格文件。
PCT/CN2018/118870 2017-12-08 2018-12-03 群组任务的信息获取方法及装置 WO2019109880A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201711294078.9 2017-12-08
CN201711294078 2017-12-08
CN201810265592.8 2018-03-28
CN201810265592.8A CN109905315B (zh) 2017-12-08 2018-03-28 群组任务的信息获取方法及装置

Publications (1)

Publication Number Publication Date
WO2019109880A1 true WO2019109880A1 (zh) 2019-06-13

Family

ID=66750061

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/118870 WO2019109880A1 (zh) 2017-12-08 2018-12-03 群组任务的信息获取方法及装置

Country Status (1)

Country Link
WO (1) WO2019109880A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111934979A (zh) * 2020-07-10 2020-11-13 腾讯科技（深圳）有限公司 任务控制方法、装置、电子设备及存储介质
CN112261219A (zh) * 2019-07-22 2021-01-22 腾讯科技（深圳）有限公司 一种信息显示方法及智能终端
CN114827066A (zh) * 2021-01-18 2022-07-29 北京字跳网络技术有限公司 信息处理方法、装置、电子设备和存储介质
CN115248648A (zh) * 2022-08-12 2022-10-28 北京字跳网络技术有限公司 任务的处理方法、装置、电子设备和介质
CN116016413A (zh) * 2022-12-29 2023-04-25 维沃移动通信有限公司 信息处理方法、装置和电子设备
CN116226499A (zh) * 2023-03-22 2023-06-06 北京字跳网络技术有限公司 信息查询方法、装置及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222450A (zh) * 2008-01-31 2008-07-16 腾讯科技（深圳）有限公司 一种事件管理、事件通知的方法及系统
WO2013169586A2 (en) * 2012-05-10 2013-11-14 Qualcomm Incorporated Storing local session data at a user equipment and selectively transmitting group session data to group session targets based on dynamic playback relevance information
CN105791080A (zh) * 2014-12-24 2016-07-20 北京奇虎科技有限公司 群发消息处理方法和系统、电子设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222450A (zh) * 2008-01-31 2008-07-16 腾讯科技（深圳）有限公司 一种事件管理、事件通知的方法及系统
WO2013169586A2 (en) * 2012-05-10 2013-11-14 Qualcomm Incorporated Storing local session data at a user equipment and selectively transmitting group session data to group session targets based on dynamic playback relevance information
CN105791080A (zh) * 2014-12-24 2016-07-20 北京奇虎科技有限公司 群发消息处理方法和系统、电子设备

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112261219A (zh) * 2019-07-22 2021-01-22 腾讯科技（深圳）有限公司 一种信息显示方法及智能终端
CN111934979A (zh) * 2020-07-10 2020-11-13 腾讯科技（深圳）有限公司 任务控制方法、装置、电子设备及存储介质
CN111934979B (zh) * 2020-07-10 2023-09-12 腾讯科技（深圳）有限公司 任务控制方法、装置、电子设备及存储介质
CN114827066A (zh) * 2021-01-18 2022-07-29 北京字跳网络技术有限公司 信息处理方法、装置、电子设备和存储介质
CN114827066B (zh) * 2021-01-18 2024-02-20 北京字跳网络技术有限公司 信息处理方法、装置、电子设备和存储介质
CN115248648A (zh) * 2022-08-12 2022-10-28 北京字跳网络技术有限公司 任务的处理方法、装置、电子设备和介质
CN115248648B (zh) * 2022-08-12 2024-01-30 北京字跳网络技术有限公司 任务的处理方法、装置、电子设备和介质
CN116016413A (zh) * 2022-12-29 2023-04-25 维沃移动通信有限公司 信息处理方法、装置和电子设备
CN116226499A (zh) * 2023-03-22 2023-06-06 北京字跳网络技术有限公司 信息查询方法、装置及电子设备

Similar Documents

Publication Publication Date Title
CN109905315B (zh) 群组任务的信息获取方法及装置
WO2019109880A1 (zh) 群组任务的信息获取方法及装置
US20220383235A1 (en) Efficiency enhancements in task management applications
CN109005098B (zh) 任务提醒方法及装置、提醒消息的生成和展示方法及装置
JP7344386B2 (ja) グループセッションにおけるリマインダー方法、装置、デバイスおよびコンピュータプログラム
JP6204928B2 (ja) 時間管理される電子メール・メッセージ
WO2019062569A1 (zh) 消息展示方法及装置
US20150112749A1 (en) Method and system for processing actionable messages of an integrated communication and collaboration platform
US20080091782A1 (en) Method and system for delegating and managing tasks over instant messenger
TW201914263A (zh) 通訊方法、信息共享方法及裝置
WO2019062587A1 (zh) 任务生成方法及装置
US10122673B2 (en) Methods and systems for aggregating user generated content
WO2019139804A1 (en) Digital assistant task management
TW201836373A (zh) 通訊方法及裝置
US11294557B2 (en) Team configuration method, and method and apparatus for sharing team configuration solution
WO2019091323A1 (zh) 批量呼叫方法及装置
US20210019705A1 (en) Method and apparatus for sharing data across groups
WO2019019929A1 (zh) 签名档的生成方法、签名档模板的分享方法及装置
US20140358614A1 (en) Calendar-agnostic meeting scheduling
WO2020221195A1 (zh) 一种用于发布动态信息的方法与设备
US20180211227A1 (en) System and method for dynamic assistant prediction
KR102653486B1 (ko) 일정 관리 방법 및 시스템
TW202022724A (zh) 任務產生方法及裝置
WO2019184742A1 (zh) 任务提示方法及装置
US20180358011A1 (en) Providing event based activity service for conversational environment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18886607

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18886607

Country of ref document: EP

Kind code of ref document: A1