WO2017045557A1 - 通讯过程中的任务提示方法及装置 - Google Patents

通讯过程中的任务提示方法及装置 Download PDF

Info

Publication number
WO2017045557A1
WO2017045557A1 PCT/CN2016/098278 CN2016098278W WO2017045557A1 WO 2017045557 A1 WO2017045557 A1 WO 2017045557A1 CN 2016098278 W CN2016098278 W CN 2016098278W WO 2017045557 A1 WO2017045557 A1 WO 2017045557A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
communication
event
task
responding
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2016/098278
Other languages
English (en)
French (fr)
Inventor
任卿
陈航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
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
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Publication of WO2017045557A1 publication Critical patent/WO2017045557A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G06Q10/063114—Status monitoring or status determination for a person or group
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2457—Query processing with adaptation to user needs
    • G06F16/24575—Query processing with adaptation to user needs using context
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G06F16/288—Entity relationship models
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/9038—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/046—Interoperability with other network applications or services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a task prompting method and apparatus in a communication process.
  • the present application provides a task prompting method and device in a communication process, which can prompt a user for a task in a communication process, and help the user to timely understand and solve an unfinished task, thereby improving communication efficiency.
  • a task prompting method in a communication process including:
  • a task prompting device in a communication process including:
  • the detecting unit detects a communication event
  • Determining a unit determining an unfinished task related to the requestor user and the responder user of the communication event
  • Pushing unit pushing the unfinished task to at least one of the requesting user and the responding user, To be displayed on the associated device of the corresponding user.
  • the present application enables the uncompleted task to be pushed and displayed on the requesting user's associated device by determining an unfinished task related to the requesting user and the responding user during the processing of the communication event.
  • the requesting user can view and grasp all the unfinished tasks at any time, avoiding forgetting and causing multiple communication; meanwhile, when the unfinished task is pushed and displayed on the responding user's associated device, the responding user It can timely understand the communication intention of the requesting user and prepare it, and does not require the requesting user to describe and explain the unfinished task, which helps to shorten communication time and improve communication efficiency.
  • FIG. 1 is a schematic diagram of a terminal call interface in the related art
  • FIG. 2 is a flowchart of a task prompting method in a communication process in an exemplary embodiment of the present application
  • FIG. 3A is a schematic diagram of a communication process in an exemplary embodiment of the present application.
  • FIG. 3B is a schematic diagram of another communication process in an exemplary embodiment of the present application.
  • FIG. 4 is a schematic diagram of implementing a task prompt in a communication process according to an exemplary embodiment of the present application
  • FIG. 5 is a flowchart of a task prompting method in another communication process in an exemplary embodiment of the present application.
  • 6A is a schematic diagram of an interface of historical communication data in an exemplary embodiment of the present application.
  • 6B is a schematic diagram of an interface of another historical communication data in an exemplary embodiment of the present application.
  • FIG. 7 is a schematic diagram of a task prompt in a communication process in an exemplary embodiment of the present application.
  • FIG. 8A is a schematic diagram of a terminal call interface of a requesting user in an exemplary embodiment of the present application.
  • FIG. 8B is a schematic diagram of a terminal call interface of a responding user in an exemplary embodiment of the present application.
  • FIG. 9 is a schematic diagram of an instant messaging interface of a responding user in an exemplary embodiment of the present application.
  • FIG. 10 is a schematic diagram of task prompts in another communication process in an exemplary embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • FIG. 12 is a block diagram of a task prompting device in a communication process in an exemplary embodiment of the present application.
  • FIG. 1 is a schematic diagram of a terminal call interface in the related art. As shown in FIG. 1 , in the terminal call interface, only the initiator user of the call can be viewed as “white”, and at most, the user can be viewed as “small white”. “White” position "nailing business department - development” and other information, but can not understand the “black” the true intention of this call, can only wait for the call to be connected, "Little White” personally tells their own intention.
  • the initiator user must personally emphasize his communication intention, otherwise the responder user will not be able to know, and can not know the true intention of the initiator user in advance, resulting in a long and inefficient communication process. And other issues.
  • the present application can solve the above technical problems existing in the related art by implementing task prompts in the communication process.
  • the following examples are provided:
  • FIG. 2 is a flowchart of a task prompting method in a communication process according to an exemplary embodiment of the present application. As shown in FIG. 2, the method is applied to a server, and may include the following steps:
  • step 202 a communication event is detected.
  • the server carries a communication platform, and the user can initiate a communication event with other users through the communication platform, and the communication platform can detect the existing communication event according to the communication platform.
  • the communication event may be a real-time communication event, such as a call time, an instant messaging event, and the like.
  • the communication time can also be a non-real-time communication event.
  • the communication platform establishes a communication event at the set communication time, and transmits the set communication content to the response. Party user.
  • the "DING message” function provided by the enterprise instant messaging application "nail” is taken as an example: the requesting user can use the sent instant messaging message or any of the individually set messages as the "DING message".
  • the communication content and the set time point is the communication time of the "DING message”; then, the server corresponding to the "nail” can initiate a "DING message” to the responding user, which specifically includes: converting the set communication content For voice, and by initiating a telephone call to the responding user, after the responding user connects the calling call, the voice is played to the responding user, thereby completing the non-real-time communication event.
  • Step 204 Determine outstanding tasks related to the requestor user and the responder user of the communication event.
  • the user who initiates the communication is the requesting user, and the user who responds to the communication is the responding user; for example, when user A dials the telephone number of user B, it is considered that user A is the requesting user and user B is Responder user.
  • the unfinished task may be any unfinished event related to the requesting user and the responding user, such as a pre-agreed (such as shopping) between the requesting user and the responding user, such as a work content (such as The requesting user pre-authorizes the responding user to perform any test, such as software testing.
  • a pre-agreed such as shopping
  • a work content such as The requesting user pre-authorizes the responding user to perform any test, such as software testing.
  • Step 206 Push the unfinished task to at least one of the requesting user and the responding user to be displayed in an associated device of the corresponding user.
  • the present application enables the uncompleted task to be pushed and displayed on the requesting user's associated device by determining an unfinished task related to the requesting user and the responding user during the processing of the communication event.
  • the requesting user can view and grasp all the unfinished tasks at any time, avoiding forgetting and causing multiple communication; meanwhile, when the unfinished task is pushed and displayed on the responding user's associated device, the responding user It can timely understand the communication intention of the requesting user and prepare it, and does not require the requesting user to describe and explain the unfinished task, which helps to shorten communication time and improve communication efficiency.
  • the requesting user can establish a communication event with the responding user through the client platform carried in the server through the client application in the terminal.
  • the client application may have a one-to-one correspondence with the communication type. For example, when the communication type is call, instant messaging, email, etc., multiple client applications respectively corresponding to each of the above communication types may be installed in the terminal, respectively.
  • the corresponding type of communication event can be realized; or the client application can integrate multiple communication types, and only one client application can be installed in the terminal, so that multiple types of communication events can be realized.
  • the client application may be an instant messaging application, such as an enterprise instant messaging application (EIM), for example, a corporate instant messaging application (DingTalk);
  • EIM enterprise instant messaging application
  • DingTalk corporate instant messaging application
  • the combination of communication types, "nailing” can realize various types of communication events such as call, instant messaging, mail, and timing message push (such as "DING message"), then the platform carried by the above server can be called “nail” Unified Communications Platform to uniformly support multiple types of communication events.
  • the nail unified communication platform is based on the communication initiated by the user “Little White”.
  • the request directly establishes a corresponding communication event between the user “Xiaobai” and the user “Xiaohei”, wherein the user “Xiaobai” is the initiator user of the communication event, and the user “Xiaohei” is the responder of the communication event. user.
  • the nail unified communication platform directly sends the instant messaging message or mail to the user "small black”, and the user "black” "View and complete the communication event to establish an instant messaging or mail type between the two.
  • the nail unified communication platform is initiated based on the user "Little White”.
  • the communication request establishes a communication connection with the user "Xiaobai” and the user “Xiaohe” respectively, and then connects the two communication connections to realize the communication connection between the user "Xiaobai” and the user “Xiaohei", and establishes a communication connection.
  • the corresponding communication event assuming that the user "Xiaobai" initiates a communication request for the user "small black” to the nail unified communication platform, the nail unified communication platform is initiated based on the user "Little White”.
  • FIG. 4 is a schematic diagram of a task prompt in a communication process according to an exemplary embodiment of the present application
  • FIG. 5 is a flowchart of a task prompting method in another communication process in an exemplary embodiment of the present application.
  • the process of implementing the task prompt in the communication process may include the following steps:
  • Step 502 detecting a communication event.
  • the task prompting method shown in FIG. 5 is applied to a server, which carries a communication platform, such as the nail unified communication platform shown in FIG. 4, such as a user “Little White”, a user.
  • a communication platform such as the nail unified communication platform shown in FIG. 4, such as a user “Little White”, a user.
  • the communication event between "Little Black” is processed.
  • step 504A historical communication data is queried, and the historical communication data is related to the initiator user and the responder user.
  • Step 504B querying a process business event, the process business event being related to the initiator user and the responder user.
  • step 506 it is determined that the task is not completed.
  • the corresponding unfinished task may be determined in various manners, such as the two modes shown in step 504A and step 504B; the following is shown for step 504A and step 504B.
  • the two ways are illustrated separately:
  • Method 1 Based on historical communication data
  • an incomplete task may be determined based on historical communication data between the requesting user and the responding user.
  • the historical communication data may include historical data of any communication type.
  • the communication type may include: instant messaging, a call, an email, etc.
  • the corresponding historical communication data includes at least one of the following: an instant messaging message, a call log, and a phone message. ,mail.
  • the corresponding unfinished tasks can be determined by the following methods:
  • the incomplete task may be an instant messaging advisory request initiated by the requesting user to the responding user and not yet answered.
  • the number of the instant messaging requests that are not answered may be determined according to the number of the instant messaging messages (the historical total amount or the quantity in a certain period of time). For example, in FIG. 6A, the number of messages sent by the user “Little White” is 1. The number of messages sent by the user "small black” is 0, and thus it is determined that there is an unanswered instant messaging consultation request.
  • the content of the instant messaging message can be parsed to improve the accuracy of the judgment. For example, when the content of the instant messaging message sent by the user "Xiaobai” is “hi”, it is actually just saying hello, and should not be used as a "task”; when the content of the instant messaging message sent by the user “Xiaobai” is "small” Black, did you test your beta version yesterday?”, based on the "?", "?" or even semantic analysis contained in it, it is determined that the content is for "inquiry” purposes, and thus it is determined that there is an unanswered Instant messaging consultation request.
  • the unfinished task includes at least one of the following: the mail content of the preset importance related to the requesting user and the responding user, the communication between the requesting user and the responding user, and not yet completed. Matters.
  • the unfinished task is a missed call record initiated by the requesting user to the responding user and has not been processed; or, when the historical communication data is a telephone message, the unfinished task is the requesting user The phone message content initiated by the responding user and not yet processed.
  • the missed call record that is, the user “small black” calls back to the user “small white”, if the callback is not returned, the missed call record is considered to have not been processed; and for the processing of the telephone message, If the user "small black” listens to the specific content of the telephone message, if the user does not listen, the telephone message is considered to have not been processed.
  • a process business event related to a requestor user and a responder user may be acquired, and an unfinished process business event is taken as an incomplete task.
  • the process business event is actually a process business event involving both the requester user and the responder user, such as an application scenario for "enterprise management", and the process business event may include at least one of the following: approval Business events, collaborative business events, attendance management events.
  • the technical solution of the present application can also be applied to other scenarios, and the process service event will also be changed correspondingly.
  • the application does not limit this.
  • the process business event may include: Party invitations, group participation applications, etc.
  • Step 508 task sorting and marking.
  • the importance degree when there are multiple unfinished tasks, the importance degree may be sorted and marked for a plurality of outstanding tasks, and when the plurality of outstanding tasks are pushed to the association of the requesting user or the responding user When the device is in use, it can be displayed in the associated device according to the importance degree, so as to facilitate the viewing by the corresponding user.
  • step 510 the unfinished task is pushed.
  • the nail unified communication platform may push the unfinished task to at least one of the initiator user and the responder user to display the outstanding task in the associated device of the corresponding user.
  • the nail unified communication platform can send the unfinished task to the user “white”, so that the displayed in the associated device is not
  • the user "small white” can be prompted to avoid missing the task when the task is too much or during the chat, or the unifying task can also send the unfinished task to the user "small black”.
  • the user "small black” can understand the communication intention of the other party, which helps to shorten the communication duration and improve the communication efficiency.
  • the nailed unified communication platform can also push unfinished tasks to the user "Little White” and the user “Little Black” at the same time.
  • the associated device of the requesting user and the responding user may also be used to process the communication event and the prompt of the unfinished task.
  • FIG. 7 the user “Little White” is used as the initiator user, and only the mobile phone 1 is used as the associated device, and the mobile phone 1 is not only used for receiving and displaying unfinished tasks, but also used to initiate communication events to the user “Little Black”. .
  • FIG. 8A shows the mobile phone 1 during the call (Fig.
  • the interface diagram shows the unfinished tasks related to the user "Little White” and the user “Little Black”, including “1, beta version test results", “2, new version progress", two; of course, not
  • the number of completed tasks may be one or more, and this application does not limit this.
  • the two unfinished tasks shown in FIG. 8A may be arranged in any order, or may be sorted and marked based on the nail unified communication platform, and arranged according to importance.
  • the corresponding source may also be marked, for example, “1, beta version test result” is obtained from an instant messaging message in the instant messaging application “nail”. Thus marked as “from nail”; similarly, it is assumed that "2, new version progress” is obtained from the "nail mail” mail, and thus marked as "from nail mail”.
  • FIG. 8B may also be arranged in any order, or may be sorted and marked based on the nail unified communication platform, arranged according to importance; and, in FIG. 8B, the same may be performed. The source of each unfinished task is marked and will not be described here.
  • FIG. 9 is a schematic diagram of the interface of the user “small black” associated device, and the user “white” only In the case of sending a greeting of "Hi” to the user “Little Black”, the server can predict the communication intention of the user “Little White” without further description by the user "Little White”, and prompt the corresponding unfinished task.
  • the user's "small black” associated device's instant messaging interface allows users to view “small black” and improve subsequent communication efficiency.
  • the associated device of the requesting user and the responding user may be used only for the prompt of the unfinished task, and the communication event is processed by other devices, such as the requesting user initiating the communication event through the first device, A device is distinguished from an associated device of the requesting user, and the responding user responds to the communication event by the second device, and the second device is distinguished from the associated device of the responding user.
  • the user "Xiaobai” is used as the initiator user, and the mobile phone 1 is used as the first device for initiating a communication event to the user "small black”, and the user "small black” is used as the responding user, using the mobile phone 2
  • the second device it is used to respond to the communication event to the user "white”.
  • the user "small white” prompts the unfinished task by using the associated device different from the mobile phone 1, for example, the associated device can be another mobile phone 3 or computer 1 and other electronic devices, and the user "small black” is distinguished from the mobile phone 2
  • the associated device performs a prompt for an unfinished task, for example, the associated device may be another electronic device such as the mobile phone 4 or the computer 2.
  • the communication event of the type of the call is used as an example, and is similar to the terminal interface shown in FIG. 8A-8B, and details are not described herein again.
  • the communication event established by the initiator user may not be effectively responded or Communication can be solved by the following steps 5A to 5C.
  • Step 5A Obtain status information of the responding user.
  • the steps 5A to 5C only need to be satisfied after the step 502 and before the step 510, and there is no necessary sequence or dependency relationship with other steps.
  • the responding user is an enterprise employee
  • the state information thereof may be recorded in a “state management subsystem” or other similar subsystem in the enterprise management system, and then the nail is
  • the nail unified communication platform can obtain the status information of the responding user by accessing the enterprise management system or the corresponding subsystem.
  • the nail unified communication platform can also obtain the event status of the respondent user, such as attendance and vacation, or obtain the real-time geographic location information of the responding user, thereby estimating the state information of the responding user.
  • Step 5B find the proxy user.
  • the proxy user associated with the responding user is looked up. Since the prediction result is that the communication intention of the originating user is related to the unfinished task, when the actual responder user cannot process the unfinished task, the proxy user who can actually handle the unfinished task should respond to the communication event. Helps improve communication efficiency.
  • step 5C replace the responder.
  • the proxy user is replaced with a responder of the communication event, and the unfinished task is pushed to the proxy user for display in the associated device of the proxy user.
  • the nail unified communication platform can use the "service scheduling" function to display the communication event from the initiator user "Xiaobai" when the user "small black” status information indicates that it can handle the unfinished task.
  • the corresponding unfinished task is scheduled to the user "small black”; and when the status information of the user "small black” indicates that it can not handle the unfinished task, the communication event from the initiator user "white” and the corresponding un Complete the task scheduling to the user "white” of the user "small black” in order to improve communication efficiency.
  • FIG. 11 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may of course include hardware required for other services.
  • the processor reads the corresponding computer program from the non-volatile memory into the memory and then runs to form a task prompting device in the communication process at a logical level.
  • the present application does 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 logical unit, and may be Hardware or logic device.
  • the task prompting device in the communication process may include a detecting unit, Determine the unit and push unit. among them:
  • the detecting unit detects a communication event
  • Determining a unit determining an unfinished task related to the requestor user and the responder user of the communication event
  • the pushing unit pushes the unfinished task to at least one of the requesting user and the responding user to be displayed in an associated device of the corresponding user.
  • the determining unit is specifically configured to:
  • the unfinished task is determined according to historical communication data between the requesting user and the responding user.
  • the historical communication data includes at least one of the following:
  • the unfinished task is an instant messaging consultation request initiated by the requesting user to the responding user and has not been answered;
  • the unfinished task is a missed call record initiated by the requesting user to the responding user and has not been processed
  • the unfinished task is a phone message content initiated by the requesting user to the responding user and has not been processed;
  • the unfinished task includes at least one of the following: a mail content of a preset importance related to the requesting user and the responding user, the requesting user and the A matter that the responding user communicates by mail and has not completed.
  • the determining unit is specifically configured to:
  • the process business event includes at least one of the following: an approval business event, a collaborative business event, and an attendance management event.
  • it also includes:
  • a marking unit when there are a plurality of outstanding tasks, sorting and marking the importance of the plurality of outstanding tasks, so that the plurality of outstanding tasks are arranged and displayed in the associated device according to importance.
  • the associated device of the requesting user is further configured to initiate the communication event, and the associated device of the responding user is further configured to respond to the communication event;
  • the requesting user initiates the communication event by using the first device
  • the first device is different from the associated device of the requesting user
  • the responding user responds to the communication event by using the second device.
  • the second device is different from the associated device of the responding user.
  • the communication event is a call event initiated by the requesting user through the instant messaging application for the responding user.
  • the communication event is an instant messaging event initiated by the requesting user through the instant messaging application for the responding user.
  • the instant messaging application is an enterprise instant messaging application.
  • it also includes:
  • a searching unit when the status information indicates that the responding user cannot process the outstanding task, searching for a proxy user associated with the responding user;
  • a replacement unit that replaces the proxy user with a responder of the communication event and pushes the outstanding task to the proxy user for display in an associated device of the proxy user.
  • a computing device 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. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Computational Linguistics (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请提供一种通讯过程中的任务提示方法及装置，该方法可以包括：检测到通讯事件；确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。通过本申请的技术方案，可以在通讯过程中对用户进行任务提示，帮助用户及时了解和解决未完成任务，有助于提升沟通效率。

Description

通讯过程中的任务提示方法及装置
本申请要求2015年09月16日递交的申请号为201510590910.4、发明名称为“通讯过程中的任务提示方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通讯技术领域，尤其涉及通讯过程中的任务提示方法及装置。
背景技术
当用户A与用户B进行通讯时，往往带有相应的意图，比如解决与用户A和用户B相关且尚未完成的事件，即“未完成任务”。
然而，当用户A向用户B发起通讯事件时，用户B往往并不能够了解未完成任务的具体内容，需要由用户A在通讯过程中进行相应描述，而用户B也无法及时做好相应准备；而如果同时存在多项未完成任务，则用户A在通讯的过程中很可能会忘记其中的部分未完成任务，需要多次向用户B发起通讯事件。可见，相关技术中的通讯过程，存在沟通时间长、效率低的问题。
发明内容
有鉴于此，本申请提供一种通讯过程中的任务提示方法及装置，可以在通讯过程中对用户进行任务提示，帮助用户及时了解和解决未完成任务，有助于提升沟通效率。
为实现上述目的，本申请提供技术方案如下：
根据本申请的第一方面，提出了一种通讯过程中的任务提示方法，包括：
检测到通讯事件；
确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；
将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。
根据本申请的第二方面，提出了一种通讯过程中的任务提示装置，包括：
检测单元，检测到通讯事件；
确定单元，确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；
推送单元，将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一， 以展示于相应用户的关联设备中。
由以上技术方案可见，本申请通过在通讯事件的处理过程中，通过确定与请求方用户和响应方用户相关的未完成任务，使得当该未完成任务被推送并展示于请求方用户的关联设备时，该请求方用户可以随时查看并掌握所有未完成任务的情况，避免遗忘而导致多次沟通；同时，当该未完成任务被推送并展示于响应方用户的关联设备时，该响应方用户可以及时了解请求方用户的通讯意图并做好准备，且无需请求方用户对该未完成任务的情况进行描述和讲解，有助于缩短沟通时间、提升沟通效率。
附图说明
图1是相关技术中的终端通话界面的示意图；
图2是本申请一示例性实施例中的一种通讯过程中的任务提示方法的流程图；
图3A是本申请一示例性实施例中的一种通讯过程的示意图；
图3B是本申请一示例性实施例中的另一种通讯过程的示意图；
图4是本申请一示例性实施例中的一种在通讯过程中实现任务提示的示意图；
图5是本申请一示例性实施例中的另一种通讯过程中的任务提示方法的流程图；
图6A是本申请一示例性实施例中的一种历史通讯数据的界面示意图；
图6B是本申请一示例性实施例中的另一种历史通讯数据的界面示意图；
图7是本申请一示例性实施例中的一种通讯过程中的任务提示的示意图；
图8A是本申请一示例性实施例中的一种请求方用户的终端通话界面的示意图；
图8B是本申请一示例性实施例中的一种响应方用户的终端通话界面的示意图；
图9是本申请一示例性实施例中的一种响应方用户的即时通讯界面的示意图；
图10是本申请一示例性实施例中的另一种通讯过程中的任务提示的示意图；
图11是本申请一示例性实施例中的一种电子设备的结构示意图；
图12是本申请一示例性实施例中的一种通讯过程中的任务提示装置的框图。
具体实施方式
图1是相关技术中的终端通话界面的示意图，如图1所示，在该终端通话界面中，仅能够查看到通话的发起方用户为“小白”，并至多能够查看到该用户“小白”的职位“钉钉事业部-开发”等信息，而并不能够了解到“小白”本次来电的真正意图，只能够等待该通话接通后，由“小白”亲自讲述自己的意图。
类似地，在其他各种通讯过程中，诸如即时通讯、邮件等，在发起方用户首先发出诸如“Hi”等问候语时，响应方用户并不能够了解该发起方用户的真正意图，除非该发起方用户主动描述。
可见，在相关技术的通讯过程中，发起方用户必须亲自强调自己的通讯意图，否则响应方用户将无法得知、更无法提前了解发起方用户的真正意图，导致通讯过程存在耗时长、效率低等问题。
因此，本申请通过在通讯过程中实现任务提示，可以解决相关技术中存在的上述技术问题。为对本申请进行进一步说明，提供下列实施例：
图2是本申请一示例性实施例中的一种通讯过程中的任务提示方法的流程图，如图2所示，该方法应用于服务器中，可以包括以下步骤：
步骤202，检测到通讯事件。
在本实施例中，服务器上承载了通讯平台，用户可以通过该通讯平台发起与其他用户的通讯事件，则该通讯平台可以据此检测存在的通讯事件。
在本实施例中，通讯事件可以为实时的通讯事件，比如通话时间、即时通讯事件等。当然，通讯时间也可以为非实时的通讯事件，比如由请求方用户设定通讯内容和通讯时间后，由通讯平台在设定的通讯时间建立通讯事件，并将设定的通讯内容传达至响应方用户。
对于非实时的通讯事件，以企业即时通讯应用“钉钉”提供的“DING消息”功能为例：请求方用户可以将已发送的即时通讯消息或其单独设定的任意消息作为“DING消息”的通讯内容，并设定的任意时间点为“DING消息”的通讯时间；那么，“钉钉”对应的服务器可以向响应方用户发起“DING消息”，具体包括：将设定的通讯内容转换为语音，并通过向响应方用户发起电话呼叫，在响应方用户接通呼叫电话后，将语音播放给响应方用户，从而完成该非实时的通讯事件。
步骤204，确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务。
在本实施例中，发起通讯的用户为请求方用户、响应通讯的用户为响应方用户；举例而言，当用户A拨打用户B的电话号码时，认为用户A为请求方用户、用户B为响应方用户。
在本实施例中，未完成任务可以为与请求方用户与响应方用户相关的任何未完成事件，比如请求方用户与响应方用户之间的预先约定(比如逛街)、某项工作内容(比如请求方用户预先委托响应方用户进行软件测试)等任意事件。
步骤206，将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。
由以上技术方案可见，本申请通过在通讯事件的处理过程中，通过确定与请求方用户和响应方用户相关的未完成任务，使得当该未完成任务被推送并展示于请求方用户的关联设备时，该请求方用户可以随时查看并掌握所有未完成任务的情况，避免遗忘而导致多次沟通；同时，当该未完成任务被推送并展示于响应方用户的关联设备时，该响应方用户可以及时了解请求方用户的通讯意图并做好准备，且无需请求方用户对该未完成任务的情况进行描述和讲解，有助于缩短沟通时间、提升沟通效率。
1、客户端应用和通讯平台
在本申请中，请求方用户可以通过自身终端内的客户端应用，经由上述服务器承载的通讯平台，建立与响应方用户之间的通讯事件。其中，该客户端应用可以与通讯类型一一对应，比如当通讯类型为通话、即时通讯、邮件等时，终端内可以安装有分别对应于上述每一通讯类型的多个客户端应用，以分别实现相应类型的通讯事件；或者，客户端应用可以融合多种通讯类型，则终端内可以仅安装该一个客户端应用，即可实现多种类型的通讯事件。
作为一示例性实施例，上述的客户端应用可以为即时通讯应用，比如企业即时通讯应用(Enterprise Instant Messaging，EIM)，例如，企业即时通讯应用“钉钉”(DingTalk)；其中，通过对多种通讯类型的融合，“钉钉”可以实现通话、即时通讯、邮件、定时消息推送(如“DING消息”)等多种类型的通讯事件，则上述的服务器承载的平台可以称为“钉钉统一通信平台”，以统一支持多种类型的通讯事件。
为了便于描述，下面的实施例均以“钉钉”和“钉钉统一通信平台”为例，对本申请的技术方案做进一步的详细介绍。
2、创建通讯事件
在一种情况下，如图3A所示，假定用户“小白”向钉钉统一通讯平台发起针对用户“小黑”的通讯请求，则钉钉统一通讯平台基于用户“小白”发起的通讯请求，直接在用户“小白”与用户“小黑”之间建立相应的通讯事件，其中用户“小白”为该通讯事件的发起方用户、用户“小黑”为该通讯事件的响应方用户。
举例而言，假定用户“小白”拨打了用户“小黑”的电话号码，则钉钉统一通讯平台直接将用户“小白”的呼叫请求发送至用户“小黑”，并由用户“小黑”接听后，完成建立两者之间的通话类型的通讯事件。
或者，假定用户“小白”向用户“小黑”发送了即时通讯消息或邮件，则钉钉统一通讯平台直接将该即时通讯消息或邮件发送至用户“小黑”，并由用户“小黑”进行查看，完成建立两者之间的即时通讯或邮件类型的通讯事件。
在另一种情况下，如图3B所示，假定用户“小白”向钉钉统一通讯平台发起针对用户“小黑”的通讯请求，则钉钉统一通讯平台基于用户“小白”发起的通讯请求，分别与用户“小白”和用户“小黑”之间建立通讯连接，然后将两个通讯连接对接，实现用户“小白”与用户“小黑”之间的通讯连接，并建立相应的通讯事件。
举例而言，假定用户“小白”拨打(可以通过企业即时通讯应用“钉钉”提供的通话功能实现)了用户“小黑”的电话号码，则钉钉统一通讯平台将挂断该通话，并一方面回拨至用户“小白”、另一方面拨打至用户“小黑”，然后将用户“小白”与用户“小黑”的通话对接，完成建立两者之间的通话类型的通讯事件。
当然，基于通讯平台的处理逻辑的不同，可能存在包括上述情况在内的很多通讯事件的创建方式，本申请对相应的通讯事件均予以支持，并不对此进行限制。
3、通讯过程中的任务提示
图4是本申请一示例性实施例中的一种在通讯过程中实现任务提示的示意图；图5是本申请一示例性实施例中的另一种通讯过程中的任务提示方法的流程图。其中，如图5所示，在通讯过程中实现任务提示的过程可以包括以下步骤：
步骤502，检测到通讯事件。
在本实施例中，图5所示的任务提示方法应用于服务器中，该服务器承载了通讯平台，比如图4所示的钉钉统一通讯平台，该通讯平台对诸如用户“小白”、用户“小黑”之间的通讯事件进行处理。
步骤504A，查询历史通讯数据，该历史通讯数据与发起方用户和响应方用户相关。
步骤504B，查询流程业务事件，该流程业务事件与发起方用户和响应方用户相关。
步骤506，确定未完成任务。
在本申请的技术方案中，基于检测到的通讯事件，可以通过多种方式来确定相应的未完成任务，比如步骤504A和步骤504B所示的两种方式；下面针对步骤504A和步骤504B所示的两种方式，分别进行举例说明：
方式一：基于历史通讯数据
作为一示例性实施例，可以根据请求方用户与响应方用户之间的历史通讯数据，确定未完成任务。
其中，历史通讯数据可以包括任意通讯类型的历史数据，比如该通讯类型可以包括：即时通讯、通话、邮件等，则相应的历史通讯数据包括以下至少之一：即时通讯消息、通话记录、电话留言、邮件。相应地，针对不同类型的历史通讯数据，可以分别通过下述方式确定对应的未完成任务：
1)即时通讯消息
当历史通讯数据为即时通讯消息时，未完成任务可以为请求方用户向响应方用户发起且尚未被答复的即时通讯咨询请求。
比如图6A所示，假定用户“小白”在10:20时向用户“小黑”发送了即时通讯消息，内容为“小黑，昨天给你的beta版本测试完了吗？”，而在用户“小白”于10:45向用户“小黑”发起通讯事件时，该即时通讯消息仍未被回复，即用户“小白”向用户“小黑”发起的即时通讯咨询请求未被答复，因此，将该即时通讯咨询请求作为用户“小白”与用户“小黑”之间的未完成任务。
其中，可以根据即时通讯消息的收发数量(历史全量，或者一定时间内的数量)，确定是否存在未被答复的即时通讯咨询请求，比如图6A中，用户“小白”发出的消息数量为1、用户“小黑”发出的消息数量为0，因而判定存在未被答复的即时通讯咨询请求。
或者，还可以对即时通讯消息的内容进行解析，以提升判断的准确性。比如当用户“小白”发送的即时通讯消息的内容为“hi”时，实际上只是打招呼，并不应当作为“任务”；而当用户“小白”发送的即时通讯消息的内容为“小黑，昨天给你的beta版本测试完了吗？”时，可以根据其中包含的“吗”、“？”甚至语义分析，确定该内容是出于“询问”目的，从而判定为存在未被答复的即时通讯咨询请求。
2)邮件
当历史通讯数据为邮件时，未完成任务包括以下至少之一：与请求方用户和响应方用户相关的预设重要度的邮件内容、请求方用户与响应方用户之间通过邮件沟通且尚未完成的事项。
A.重要度。每封邮件都存在对应的重要度，用户可以根据自己的需求进行设置。如图6B所示，该邮件的重要度被用户“小黑”设置为“极高”，则可以不必分析该邮件的内容等方面，即可认定用户“小白”很可能希望与用户“小黑”讨论关于该邮件的事项，因而将该邮件作为未完成任务。
B.邮件沟通事项。如图6B所示，可以通过提取邮件内容“小黑：昨天给你的beta 版本测试完了吗？”，并通过与上述的“即时通讯消息”相类似的处理过程，即当双方的邮件数量不一致、或者根据邮件内容确定该邮件未被答复时，判定用户“小白”与用户“小黑”之间存在尚未完成的事项，可以作为两者之间的未完成任务。
3)通话记录或电话留言
当历史通讯数据为通话记录时，未完成任务为请求方用户向响应方用户发起且尚未被处理的未接通话记录；或者，当历史通讯数据为电话留言时，未完成任务为请求方用户向响应方用户发起且尚未被处理的电话留言内容。
上述两种形式的历史通讯数据类似，都是由用户“小白”向用户“小黑”发起后，用户“小黑”尚未处理的情况，且只需要确保与用户“小白”和用户“小黑”相关即可，而无需考虑具体的数据内容分析等，即可作为相应的未完成任务。
其中，对于未接通话记录的处理，即用户“小黑”回拨给用户“小白”，因而若未回拨，则认为该未接通话记录尚未被处理；而对于电话留言的处理，即用户“小黑”收听电话留言的具体内容，则若未收听，则认为该电话留言尚未被处理。
方式二：基于流程业务事件
作为另一示例性实施例，可以获取与请求方用户和响应方用户相关的流程业务事件，并将未完成的流程业务事件作为未完成任务。
在本实施例中，流程业务事件实际上就是同时涉及请求方用户与响应方用户的流程性的业务事件，比如针对“企业管理”的应用场景，该流程业务事件可以包括以下至少之一：审批业务事件、协作业务事件、考勤管理事件。当然，本申请的技术方案也可以应用于其他场景，则流程业务事件也将相应变化，本申请并不对此进行限制；举例而言，比如针对“社交”的应用场景，流程业务事件可以包括：聚会邀约、群组加入申请等。
以“审批业务事件”为例。假定用户“小白”预先向用户“小黑”发起了关于休假的审批事件，则如果在用户“小白”向用户“小黑”发起通讯事件时，该审批事件尚未被处理，即用户“小黑”尚未向用户“小白”反馈审批结果，则很可能用户“小白”是希望了解或催促该审批事件的处理情况，可以将该休假审批事件作为未完成任务。
以“协作业务事件”为例。假定用户“小白”属于开发人员、用户“小黑”属于测试人员，则两者之间存在工作上的协作关系。那么，只要该协作关系尚未被取消，就认定存在相应的协作业务事件，则用户“小白”向用户“小黑”发起通讯事件时，将很可能是讨论两者的协作内容，因而可以将该协作业务事件作为未完成任务。
以“考勤管理事件”为例。假定用户“小白”为部门主管、用户“小黑”为部门成 员，则如果用户“小黑”尚未打卡考勤，则用户“小白”向用户“小黑”发起通讯事件时，将很可能是询问关于考勤情况的问题，因而可以将该考勤管理事件作为未完成任务。
步骤508，任务排序和标记。
在本实施例中，当存在多个未完成任务时，可以对多个未完成任务进行重要度的排序和标记，则当该多个未完成任务被推送至请求方用户或响应方用户的关联设备时，可以按照重要度进行排列展示于关联设备中，以便于相应用户的查看。
步骤510，推送未完成任务。
在本实施例中，钉钉统一通讯平台可以将未完成任务推送至发起方用户和响应方用户中至少之一，以将该未完成任务展示于相应用户的关联设备中。比如当发起方用户为用户“小白”、响应方用户为用户“小黑”时，钉钉统一通讯平台可以将未完成任务发送至用户“小白”，使得展示于其关联设备中的未完成任务，可以对用户“小白”起到提示作用，避免当未完成任务过多或闲聊过程中造成遗漏，或者钉钉统一通讯平台也可以将未完成任务发送至用户“小黑”，则无需用户“小白”提示，用户“小黑”即可了解到对方的通讯意图，有助于缩短通讯时长、提升通讯效率。当然，钉钉统一通讯平台也可以将未完成任务同时推送至用户“小白”和用户“小黑”。
作为一示例性实施例，请求方用户和响应方用户的关联设备，也可以同时用于处理通讯事件和未完成任务的提示。
如图7所示，用户“小白”作为发起方用户，仅使用手机1为关联设备，则该手机1不仅用于接收和展示未完成任务，还用于向用户“小黑”发起通讯事件。以“通话”类型的通讯事件为例，图8A示出了手机1在通话过程中(图8A为电话接通前的界面，接通后的界面与之类似，同样可以示出未完成任务)的界面示意图，其中示出了与用户“小白”和用户“小黑”相关的未完成任务，包括“1、beta版本测试结果”、“2、新版本进度”共两条；当然，未完成任务的数量可以为1条或多条，本申请并不对此进行限制。其中，对于图8A所示的2条未完成任务，可以是按照任意顺序排列，也可以是基于钉钉统一通讯平台的排序和标记，按照重要度进行排列。
进一步的，如图8A所示，对于每条未完成任务，还可以标示出相应的出处，比如“1、beta版本测试结果”是从即时通讯应用“钉钉”中的即时通讯消息得到的，因而标记为“来自钉钉”；类似的，假定“2、新版本进度”是从“钉邮”的邮件得到的，因而标记为“来自钉邮”。
类似的，用户“小黑”作为响应方用户，仅使用手机2为关联设备，则该手机2不 仅用于接收和展示未完成任务，还用于向用户“小白”响应通讯事件。那么，对应于图8A，在图8B中示出了手机2在通话过程中(图8B为电话接通前的界面，接通后的界面与之类似，同样可以示出未完成任务)的界面示意图，其中示出了与用户“小白”和用户“小黑”相关的未完成任务，包括“1、beta版本测试结果”、“2、新版本进度”共两条，与图8A中示出的未完成任务相同。其中，对于图8B所示的2条未完成任务，同样可以是按照任意顺序排列，也可以是基于钉钉统一通讯平台的排序和标记，按照重要度进行排列；并且，图8B中同样可以对每条未完成任务的来源进行标记，此处不再赘述。
此外，而正如上文所述，由于本申请中的通讯事件可以存在多种类型，下面以“即时通讯”类型的通讯事件为例，做进一步说明。如图9所示，假定用户“小白”为发起方用户、用户“小黑”为响应方用户，则图9为用户“小黑”的关联设备的界面示意图，在用户“小白”仅向用户“小黑”发送了“Hi”的问候语的情况下，无需用户“小白”进一步描述，服务器即可预测出用户“小白”的通讯意图，并将相应的未完成任务提示于用户“小黑”的关联设备的即时通讯界面中，以便用户“小黑”的查看，并提升后续的沟通效率。
作为另一示例性实施例，请求方用户和响应方用户的关联设备可以分别仅用于未完成任务的提示，而通过其他设备处理通讯事件，比如请求方用户通过第一设备发起通讯事件，第一设备区别于请求方用户的关联设备，且响应方用户通过第二设备响应通讯事件，第二设备区别于响应方用户的关联设备。
如图10所示，用户“小白”作为发起方用户，使用手机1为第一设备，用于向用户“小黑”发起通讯事件，而用户“小黑”作为响应方用户，使用手机2为第二设备，用于向用户“小白”响应通讯事件。同时，用户“小白”通过区别于手机1的关联设备进行未完成任务的提示，比如该关联设备可以为另一手机3或电脑1等电子设备，而用户“小黑”通过区别于手机2的关联设备进行未完成任务的提示，比如该关联设备可以为另一手机4或电脑2等电子设备。
其中，各个关联设备对未完成任务进行展示时，以“通话”类型的通讯事件为例，与图8A-8B所示的终端界面类似，此处不再赘述。
此外，在图5所示的实施例中，除了发起方用户与响应方用户之间的正常通讯之外，基于响应方用户的不便，可能无法对发起方用户建立的通讯事件进行有效的响应或沟通，则可以通过下述的步骤5A～5C进行解决。
步骤5A，获取响应方用户的状态信息。
在本实施例中，步骤5A～5C只需要满足位于步骤502之后、步骤510之前即可，与其他步骤之间没有必然的先后顺序或依存关系。
在本实施例中，在“企业管理”的应用场景中，响应方用户作为企业员工，其状态信息可以记录在企业管理系统内的“状态管理子系统”或其他类似的子系统中，则钉钉统一通讯平台可以通过接入企业管理系统或相应的子系统中，获取响应方用户的状态信息。
在本实施例中，钉钉统一通讯平台也可以获取响应方用户的考勤、休假等事件状态，或者获取响应方用户的实时地理位置信息等，从而推测出响应方用户的状态信息。
步骤5B，查找代理用户。
在本实施例中，当状态信息表明响应方用户无法处理未完成任务时，查找与响应方用户相关联的代理用户。由于预测结果为发起方用户的通讯意图与未完成任务相关，因而在实际上的响应方用户无法处理未完成任务时，应当由实际上能够处理该未完成任务的代理用户对通讯事件进行响应，有助于提升沟通效率。
步骤5C，替换响应方。
在本实施例中，将代理用户替换为通讯事件的响应方，并将未完成任务推送至代理用户，以展示于代理用户的关联设备中。
结合图4可知，钉钉统一通讯平台可以通过“服务调度”功能，在用户“小黑”的状态信息表明其可以处理未完成任务时，可以将来自发起方用户“小白”的通讯事件以及对应的未完成任务调度至用户“小黑”；而在用户“小黑”的状态信息表明其可以无法处理未完成任务时，可以将来自发起方用户“小白”的通讯事件以及对应的未完成任务调度至用户“小黑”的代理用户“白白”，以便提升沟通效率。
图11示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图11，在硬件层面，该电子设备包括处理器、内部总线、网络接口、内存以及非易失性存储器，当然还可能包括其他业务所需要的硬件。处理器从非易失性存储器中读取对应的计算机程序到内存中然后运行，在逻辑层面上形成通讯过程中的任务提示装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图12，在软件实施方式中，该通讯过程中的任务提示装置可以包括检测单元、 确定单元和推送单元。其中：
检测单元，检测到通讯事件；
确定单元，确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；
推送单元，将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。
可选的，所述确定单元具体用于：
根据所述请求方用户与响应方用户之间的历史通讯数据，确定所述未完成任务。
可选的，所述历史通讯数据包括以下至少之一：
即时通讯消息、通话记录、电话留言、邮件。
可选的，
当所述历史通讯数据为即时通讯消息时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被答复的即时通讯咨询请求；
当所述历史通讯数据为通话记录时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的未接通话记录；
当所述历史通讯数据为电话留言时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的电话留言内容；
当所述历史通讯数据为邮件时，所述未完成任务包括以下至少之一：与所述请求方用户和所述响应方用户相关的预设重要度的邮件内容、所述请求方用户与所述响应方用户之间通过邮件沟通且尚未完成的事项。
可选的，所述确定单元具体用于：
获取与所述请求方用户和所述响应方用户相关的流程业务事件，并将未完成的流程业务事件作为所述未完成任务。
可选的，所述流程业务事件包括以下至少之一：审批业务事件、协作业务事件、考勤管理事件。
可选的，还包括：
标记单元，当存在多个未完成任务时，对所述多个未完成任务进行重要度的排序和标记，以使所述多个未完成任务按照重要度进行排列展示于所述关联设备中。
可选的，
所述请求方用户的关联设备还用于发起所述通讯事件，所述响应方用户的关联设备还用于响应所述通讯事件；
或者，所述请求方用户通过第一设备发起所述通讯事件，所述第一设备区别于所述请求方用户的关联设备，且所述响应方用户通过第二设备响应所述通讯事件，所述第二设备区别于所述响应方用户的关联设备。
可选的，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的通话事件。
可选的，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的即时通讯事件。
可选的，所述即时通讯应用为企业即时通讯应用。
可选的，还包括：
获取单元，获取所述响应方用户的状态信息；
查找单元，当所述状态信息表明所述响应方用户无法处理所述未完成任务时，查找与所述响应方用户相关联的代理用户；
替换单元，将所述代理用户替换为所述通讯事件的响应方，并将所述未完成任务推送至所述代理用户，以展示于所述代理用户的关联设备中。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而 且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (24)

  1. 一种通讯过程中的任务提示方法，其特征在于，包括：
    检测到通讯事件；
    确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；
    将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。
  2. 根据权利要求1所述的方法，其特征在于，所述确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务，包括：
    根据所述请求方用户与响应方用户之间的历史通讯数据，确定所述未完成任务。
  3. 根据权利要求2所述的方法，其特征在于，所述历史通讯数据包括以下至少之一：
    即时通讯消息、通话记录、电话留言、邮件。
  4. 根据权利要求3所述的方法，其特征在于，
    当所述历史通讯数据为即时通讯消息时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被答复的即时通讯咨询请求；
    当所述历史通讯数据为通话记录时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的未接通话记录；
    当所述历史通讯数据为电话留言时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的电话留言内容；
    当所述历史通讯数据为邮件时，所述未完成任务包括以下至少之一：与所述请求方用户和所述响应方用户相关的预设重要度的邮件内容、所述请求方用户与所述响应方用户之间通过邮件沟通且尚未完成的事项。
  5. 根据权利要求1所述的方法，其特征在于，所述确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务，包括：
    获取与所述请求方用户和所述响应方用户相关的流程业务事件，并将未完成的流程业务事件作为所述未完成任务。
  6. 根据权利要求5所述的方法，其特征在于，所述流程业务事件包括以下至少之一：审批业务事件、协作业务事件、考勤管理事件。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    当存在多个未完成任务时，对所述多个未完成任务进行重要度的排序和标记，以使 所述多个未完成任务按照重要度进行排列展示于所述关联设备中。
  8. 根据权利要求1所述的方法，其特征在于，
    所述请求方用户的关联设备还用于发起所述通讯事件，所述响应方用户的关联设备还用于响应所述通讯事件；
    或者，所述请求方用户通过第一设备发起所述通讯事件，所述第一设备区别于所述请求方用户的关联设备，且所述响应方用户通过第二设备响应所述通讯事件，所述第二设备区别于所述响应方用户的关联设备。
  9. 根据权利要求1所述的方法，其特征在于，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的通话事件。
  10. 根据权利要求1所述的方法，其特征在于，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的即时通讯事件。
  11. 根据权利要求9或10所述的方法，其特征在于，所述即时通讯应用为企业即时通讯应用。
  12. 根据权利要求1所述的方法，其特征在于，还包括：
    获取所述响应方用户的状态信息；
    当所述状态信息表明所述响应方用户无法处理所述未完成任务时，查找与所述响应方用户相关联的代理用户；
    将所述代理用户替换为所述通讯事件的响应方，并将所述未完成任务推送至所述代理用户，以展示于所述代理用户的关联设备中。
  13. 一种通讯过程中的任务提示装置，其特征在于，包括：
    检测单元，检测到通讯事件；
    确定单元，确定与所述通讯事件的请求方用户和响应方用户相关的未完成任务；
    推送单元，将所述未完成任务推送至所述请求方用户和所述响应方用户中至少之一，以展示于相应用户的关联设备中。
  14. 根据权利要求13所述的装置，其特征在于，所述确定单元具体用于：
    根据所述请求方用户与响应方用户之间的历史通讯数据，确定所述未完成任务。
  15. 根据权利要求14所述的装置，其特征在于，所述历史通讯数据包括以下至少之一：
    即时通讯消息、通话记录、电话留言、邮件。
  16. 根据权利要求15所述的装置，其特征在于，
    当所述历史通讯数据为即时通讯消息时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被答复的即时通讯咨询请求；
    当所述历史通讯数据为通话记录时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的未接通话记录；
    当所述历史通讯数据为电话留言时，所述未完成任务为所述请求方用户向所述响应方用户发起且尚未被处理的电话留言内容；
    当所述历史通讯数据为邮件时，所述未完成任务包括以下至少之一：与所述请求方用户和所述响应方用户相关的预设重要度的邮件内容、所述请求方用户与所述响应方用户之间通过邮件沟通且尚未完成的事项。
  17. 根据权利要求13所述的装置，其特征在于，所述确定单元具体用于：
    获取与所述请求方用户和所述响应方用户相关的流程业务事件，并将未完成的流程业务事件作为所述未完成任务。
  18. 根据权利要求17所述的装置，其特征在于，所述流程业务事件包括以下至少之一：审批业务事件、协作业务事件、考勤管理事件。
  19. 根据权利要求13所述的装置，其特征在于，还包括：
    标记单元，当存在多个未完成任务时，对所述多个未完成任务进行重要度的排序和标记，以使所述多个未完成任务按照重要度进行排列展示于所述关联设备中。
  20. 根据权利要求13所述的装置，其特征在于，
    所述请求方用户的关联设备还用于发起所述通讯事件，所述响应方用户的关联设备还用于响应所述通讯事件；
    或者，所述请求方用户通过第一设备发起所述通讯事件，所述第一设备区别于所述请求方用户的关联设备，且所述响应方用户通过第二设备响应所述通讯事件，所述第二设备区别于所述响应方用户的关联设备。
  21. 根据权利要求13所述的装置，其特征在于，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的通话事件。
  22. 根据权利要求13所述的装置，其特征在于，所述通讯事件为所述请求方用户通过即时通讯应用发起的针对所述响应方用户的即时通讯事件。
  23. 根据权利要求21所述的装置，其特征在于，所述即时通讯应用为企业即时通讯应用。
  24. 根据权利要求13所述的装置，其特征在于，还包括：
    获取单元，获取所述响应方用户的状态信息；
    查找单元，当所述状态信息表明所述响应方用户无法处理所述未完成任务时，查找与所述响应方用户相关联的代理用户；
    替换单元，将所述代理用户替换为所述通讯事件的响应方，并将所述未完成任务推送至所述代理用户，以展示于所述代理用户的关联设备中。
PCT/CN2016/098278 2015-09-16 2016-09-07 通讯过程中的任务提示方法及装置 Ceased WO2017045557A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510590910.4 2015-09-16
CN201510590910.4A CN105282328A (zh) 2015-09-16 2015-09-16 通讯过程中的任务提示方法及装置

Publications (1)

Publication Number Publication Date
WO2017045557A1 true WO2017045557A1 (zh) 2017-03-23

Family

ID=55150619

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2016/098278 Ceased WO2017045557A1 (zh) 2015-09-16 2016-09-07 通讯过程中的任务提示方法及装置
PCT/CN2017/070357 Ceased WO2017121286A1 (zh) 2015-09-16 2017-01-06 通讯过程中的关系及任务提示方法、装置

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070357 Ceased WO2017121286A1 (zh) 2015-09-16 2017-01-06 通讯过程中的关系及任务提示方法、装置

Country Status (5)

Country Link
US (1) US20180322440A1 (zh)
CN (2) CN105282328A (zh)
HK (1) HK1215908A1 (zh)
TW (1) TW201731313A (zh)
WO (2) WO2017045557A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112152908A (zh) 2015-02-16 2020-12-29 钉钉控股（开曼）有限公司 通讯方法
KR101769423B1 (ko) * 2016-11-08 2017-08-22 최재호 대화방 기반의 리마인더 방법 및 장치
CN105282328A (zh) * 2015-09-16 2016-01-27 阿里巴巴集团控股有限公司 通讯过程中的任务提示方法及装置
CN105681056B (zh) 2016-01-13 2019-03-19 阿里巴巴集团控股有限公司 对象分配方法及装置
CN107305459A (zh) 2016-04-25 2017-10-31 阿里巴巴集团控股有限公司 语音和多媒体消息的发送方法及装置
CN107368995A (zh) 2016-05-13 2017-11-21 阿里巴巴集团控股有限公司 任务处理方法及装置
CN106375429A (zh) * 2016-08-31 2017-02-01 宁波金唐软件有限公司 一种任务推送系统
CN107636551B (zh) * 2016-09-22 2021-11-30 深圳市大疆创新科技有限公司 一种飞行控制方法、装置及智能终端
CN106411718B (zh) * 2016-11-04 2020-02-21 宇龙计算机通信科技(深圳)有限公司 一种基于即时通信应用的数据同步方法及装置
CN106682222B (zh) * 2017-01-04 2019-06-14 上海智臻智能网络科技股份有限公司 用于问答系统的多服务响应方法、装置及问答系统
CN109120654B (zh) * 2017-06-23 2021-01-19 腾讯科技（深圳）有限公司 一种服务器的信息提示方法、装置及存储介质
CN109286553A (zh) * 2017-07-21 2019-01-29 钉钉控股（开曼）有限公司 通讯方法及装置
CN107527306A (zh) * 2017-08-18 2017-12-29 深圳市华第时代科技有限公司 在线教学系统的任务提示方法、装置、服务器及存储介质
CN107579908A (zh) * 2017-09-06 2018-01-12 叶进蓉 一种通讯过程中的任务记录方法及装置
US11048383B2 (en) 2019-08-16 2021-06-29 Dropbox, Inc. Contact cards with dynamic interaction information
CN111163234B (zh) * 2019-12-31 2021-01-22 北京金山安全软件有限公司 业务通话处理方法、装置、电子设备及存储介质
CN112104734B (zh) * 2020-09-15 2022-09-02 北京百度网讯科技有限公司 用于推送信息的方法、装置、设备以及存储介质
CN114169868A (zh) * 2021-12-16 2022-03-11 建信金融科技有限责任公司 流程审批方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102130999A (zh) * 2011-03-16 2011-07-20 宇龙计算机通信科技(深圳)有限公司 待处理信息的提示方法及终端
US20110314375A1 (en) * 2010-06-22 2011-12-22 Microsoft Corporation Personal Assistant for Task Utilization
CN104796327A (zh) * 2015-04-30 2015-07-22 北京奇艺世纪科技有限公司 消息接收方法及装置、消息传输方法及系统
CN104899722A (zh) * 2015-04-30 2015-09-09 北京奇艺世纪科技有限公司 任务进度设置方法、装置及系统
CN104899034A (zh) * 2015-06-05 2015-09-09 郭睿 在im沟通界面生成沟通事项的待办任务和结论的方法
CN105282328A (zh) * 2015-09-16 2016-01-27 阿里巴巴集团控股有限公司 通讯过程中的任务提示方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101277329A (zh) * 2007-03-28 2008-10-01 华为技术有限公司 一种推送主叫信息的方法、话机、呼叫服务器和通信系统
CN101170605A (zh) * 2007-10-26 2008-04-30 华为技术有限公司 一种发起方信息的显示方法和设备
US9338286B2 (en) * 2009-11-30 2016-05-10 Intel Corporation Methods and systems for real time display of caller location, profile, and trust relationship
KR20120027775A (ko) * 2010-09-13 2012-03-22 주식회사 케이티 통화 연결 알림을 제공하는 방법 및 장치
CN103092870A (zh) * 2011-11-04 2013-05-08 腾讯科技（深圳）有限公司 网络通信系统中的联系人关系数据的建立方法和装置
CN106791229A (zh) * 2012-04-13 2017-05-31 北京搜狗科技发展有限公司 号码的标识方法和装置
CN104202237A (zh) * 2014-08-30 2014-12-10 北京光年无限科技有限公司 一种通讯的方法、装置及系统
CN105072018A (zh) * 2015-07-10 2015-11-18 阿里巴巴集团控股有限公司 工作状态的提示方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110314375A1 (en) * 2010-06-22 2011-12-22 Microsoft Corporation Personal Assistant for Task Utilization
CN102130999A (zh) * 2011-03-16 2011-07-20 宇龙计算机通信科技(深圳)有限公司 待处理信息的提示方法及终端
CN104796327A (zh) * 2015-04-30 2015-07-22 北京奇艺世纪科技有限公司 消息接收方法及装置、消息传输方法及系统
CN104899722A (zh) * 2015-04-30 2015-09-09 北京奇艺世纪科技有限公司 任务进度设置方法、装置及系统
CN104899034A (zh) * 2015-06-05 2015-09-09 郭睿 在im沟通界面生成沟通事项的待办任务和结论的方法
CN105282328A (zh) * 2015-09-16 2016-01-27 阿里巴巴集团控股有限公司 通讯过程中的任务提示方法及装置
CN105681165A (zh) * 2015-09-16 2016-06-15 阿里巴巴集团控股有限公司 通讯过程中的关系及任务提示方法、装置

Also Published As

Publication number Publication date
CN105681165A (zh) 2016-06-15
CN105681165B (zh) 2020-07-21
WO2017121286A1 (zh) 2017-07-20
US20180322440A1 (en) 2018-11-08
CN105282328A (zh) 2016-01-27
TW201731313A (zh) 2017-09-01
HK1225872A1 (zh) 2017-09-15
HK1215908A1 (zh) 2016-09-23

Similar Documents

Publication Publication Date Title
WO2017045557A1 (zh) 通讯过程中的任务提示方法及装置
JP6723340B2 (ja) 業務状態をプロンプトする方法及び装置
US20130297442A1 (en) System and method for routing and tracking real estate leads
US20110125826A1 (en) Stalking social media users to maximize the likelihood of immediate engagement
CN108074104A (zh) 一种客服处理方法及服务端和客户端
US11483430B2 (en) System and method for mobile device active callback prioritization
US20100088302A1 (en) Associating system requests with sms user responses
US11210633B2 (en) Collaborative event processing method and apparatus
US20250168280A1 (en) Geography-Based Voice Message Assignment And Management
US20230291836A1 (en) System and method for mobile device active callback integration
US20230291837A1 (en) System and method for mobile device active callback integration utlizing callback triggers
US20230095073A1 (en) System and method for mobile device active callback prioritization
US20200084286A1 (en) Method, apparatus and system for call prompting
CN110097327A (zh) 考勤方法及装置
US11770478B2 (en) System and method for mobile device active callback prioritization with predictive outcome scoring
CN106161358B (zh) 联络信息的管理方法及装置
HK1225872B (zh) 通讯过程中的关系及任务提示方法、装置
WO2020205962A1 (en) A system and method for mobile device active callback integration
CN121116578A (zh) 任务处理方法、电子设备和存储介质
HK40066964B (zh) 通讯会话的管理方法及装置
CN118890337A (zh) 一种删除企业微信目标客户的方法及设备
CN112330263A (zh) 数据处理方法、装置、设备、系统和存储介质
HK40000728B (zh) 通话提示方法及装置、系统

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: 16845671

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: 16845671

Country of ref document: EP

Kind code of ref document: A1