Patent Description:
The approaches described in this section could be pursued but are not necessarily approaches that have previously been conceived or pursued.

A chat information system (CIS) is a computer-based agent having a human-centric interface for accessing and managing information. Traditionally, a CIS may interact with users in natural language to simulate an intelligent conversation and provide personalized assistance to the users. For example, the users may ask the CIS questions such as "Where is the nearest hotel?" or "What is the weather like today?" and receive corresponding answers. The users may also provide voice commands to the CIS so as to perform certain functions including, for example, generating emails, making phone calls, searching information, acquiring data, readdressing user requests, guiding users, providing notifications and reminders, and so forth. CIS and personal digital assistant (PDA) systems are widely used and are of great help for users of computers and are especially helpful for holders of portable electronic devices such as smart phones, cellular phones, tablet computers, gaming consoles, and so forth.

The term "chat information system," or CIS, may also be also known as "spoken dialog system," "dialog system," "conversational agent," "chatter robot," "chatterbot," "chatbot," "chat agent," "digital personal assistant/agent," "automated online assistant," and so forth. All these terms are within the scope of the present disclosure and referred to as "chat information system" or "CIS" for simplicity.

Essentially, the CIS users may ask a great number of various questions and request a wide range of information. The users typically request one and the same type of information on a daily basis, which may include, for example, weather reports, traffic reports, local or global news, information related to scheduled meetings or appointments, evening events in a target city, navigational information, and so forth. However, some users may find it difficult or annoying to generate a plurality of CIS requests over and over again and every day to get typically requested information. Moreover, the users, when required to gather information from multiple sources on a daily basis, may simply forget to request certain information items, which may lead to unwanted consequences including missed meetings or events, missed deadlines, ignorance of important information, and so forth. Therefore, there is still a need for development of CIS and, in particular, there is a need for improvement of human-CIS interaction interface.

United States patent application publication number <CIT> presents systems and methods for assisting a user with a variety of tasks. <CIT> presents a triggering mechanism for generating task reminders based on contextual information associated with the tasks. <CIT> presents techniques for processing task items. <CIT> presents a computer-implemented method for providing location-sensitive and time-sensitive calendaring to a wireless device, such as a cellphone, pager, PDA, etc. <CIT> presents a method and apparatus for processing instant messaging information.

This summary is provided to introduce a selection of concepts in a simplified form that are further described in the Detailed Description below.

The present disclosure approaches provide for the technology of intelligent and proactive generation of push notifications for the users of CIS based on multiple criteria. This technology overcomes at least some drawbacks of the prior art systems and improves the user-CIS interaction interface and overall user experience of using CIS.

Embodiments are illustrated byway of example, and not by limitation, in the figures of the accompanying drawings, in which like references indicate similar elements and in which:.

The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments, which are also referred to herein as "examples," are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical, and electrical changes can be made without departing from the scope of what is claimed. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims. In this document, the terms "a" and "an" are used, as is common in patent documents, to include one or more than one. In this document, the term "or" is used to refer to a nonexclusive "or," such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated.

The techniques of the embodiments disclosed herein may be implemented using a variety of technologies. For example, the methods described herein may be implemented in software executing on a computer system or in hardware utilizing either a combination of microprocessors or other specially designed application-specific integrated circuits (ASICs), programmable logic devices, or various combinations thereof. In particular, the methods described herein may be implemented by a series of computer- executable instructions residing on a storage medium such as a disk drive, or computer-readable medium. It should be noted that methods disclosed herein can be implemented by a computer (e.g., a desktop computer, tablet computer, laptop computer), game console, handheld gaming device, cellular phone, smart phone, smart television system, and so forth.

The embodiments of the present disclosure refer to a computer- based "Daily Brief" service, which implies methods and corresponding systems for proactively providing push notifications for users of CIS. In general, the push notifications may be dynamically and proactively generated and presented for attention of the users based on one or more criteria/rules, which are referred herein to as "triggering events. " As described in greater detail below, the CIS may monitor a current time/date associated with the user or his user device, current geographical location of the user, activity of peers and friends in social media associated with the user, social networking events, scheduled events, calendar events, appointments, email accounts, instant message service, dialogue context of user-CIS interaction, presence of one or more specific devices within a predetermined area from the user, presence of certain wireless networks within a predetermined area from the user, and so forth. All these activities, events and information items may constitute or relate to triggering events. Based on the monitoring and identifying of one or more of these triggering events, the CIS may proactively generate one or more push notifications and present them to the user in the form of text messages, image messages, video messages, audio messages, and actionable messages through the user device once at least some triggering events are identified. In some embodiments, the push notifications may include all requested information such as a text, image, video, and audio content. In other embodiments, however, the push notifications may include metadata or instruction for the user device to obtain information associated with a triggering event from a corresponding networked server.

The user may interact with the CIS utilizing a user device selected from a wide range of electronic devices including, for example, a computer (desktop computer, laptop computer, tablet computer, PDA), smart phone, cellular phone, game console, game pad, remote controller, television device, smart (Internet) television device, audio system, in-vehicle computer system, infotainment system, or any other suitable electronic device. The interaction with the CIS may include speech commands, although key input commands, selection of actionable (clickable) messages, or gesture-based commands are also possible. As described below in greater detail, the CIS may refer to a software application installed on the user device, a server, or a remote device, or it may refer to a distributed application or a cloud-based service.

<FIG> shows a high level flow diagram <NUM> of user interaction with a CIS. As shown in this figure, the user may commence interaction at operation <NUM> with providing a speech-based (audio) user input via a user device (e.g., using one or more microphones). The user input may refer to an information request, such as "What is the weather like today?" or a speech command such as to send a text message or the like.

At operation <NUM>, an automatic speech recognizer (ASR) of the CIS may recognize the user input so as to translate spoken words, phrases, and sentences into text, which are referred to herein as a recognized input. The recognized input is then analyzed at operation <NUM> by a natural language processing (NLP) module (e.g., morphological analysis, part-of-speech tagging, or shallow parsing are performed). The NLP module may also map the recognized input or its parts to one or more meaning representations (e.g., semantic frame) from which the dialog act, user goal, and named entities are extracted by a semantic parser or statistical model.

At operation <NUM>, a dialog manager generates an output (response) based at least in part on the recognized input and located meaning representations. For example, the dialog manager may retrieve specific information from one or more resources (e.g., electronic calendar, database, website, etc.) or generate metadata or instruction for a user device to request corresponding information from a networked server. At operation <NUM>, the output is provided to the user (for example, as a text, image, audio, or video message). For these ends, an output renderer may be utilized, which may transform text into speech and provide the output as a machine-generated audio signal. Alternatively, the output may be presented as a text message and shown on a display of the user device.

The above given user interaction is further illustrated in <FIG>, which shows a high level architecture of a CIS <NUM>, according to an example embodiment. It should be noted that every module of the CIS <NUM> may include hardware components, software components, or a combination thereof. The CIS <NUM> may be embedded in the user device or server, or may be presented as a cloud computing module and/or a distributed computing module.

The CIS <NUM> may include an ASR <NUM> configured to receive and process speech-based user inputs into a sequence of parameter vectors. The ASR <NUM> further converts the sequence of parameter vectors into a recognized input (i.e., a textual input having one or more words, phrases, or sentences). The ASR <NUM> may include one or more speech recognizers such as a pattern-based speech recognizer, free-dictation recognizer, address book based recognizer, dynamically created recognizer, and so forth.

Further, the CIS <NUM> may include a NLP module <NUM> for understanding spoken language input. Specifically, the NLP module <NUM> may disassemble and parse the recognized input to produce utterances which are then analyzed utilizing, for example, morphological analysis, part-of-speech tagging, shallow parsing, and the like, and then map recognized input or its parts to meaning representations.

The CIS <NUM> may further include a dialog manager <NUM>, which coordinates the activity of all components, controls dialog flows, and communicates with external applications/devices. The dialog manager <NUM> may play many roles, which include discourse analysis, knowledge database query, and system action prediction based on the discourse context. In some embodiments, the dialog manager <NUM> may contact one or more task managers (not shown) that may have knowledge of specific task domains. In some embodiments, the dialog manager <NUM> may communicate with various computing, logic, or storage resources <NUM>, which may include, for example, a triggering criteria database, rules database, recommendation database, push notification database, electronic address book, email or text agents, dialog history database, various knowledge databases, map database, points of interest database, geographical location determiner, clock, wireless network detector, search engines, social networking websites, blogging websites, news feeds services, and so forth. The dialog manager <NUM> may employ multiple various approaches to generate output in response to the recognized input. Some approaches may include the use of statistical analysis, machine-learning algorithms (e.g., neural networks), heuristic analysis, and so forth. The dialog manager <NUM> is one of the central components of CIS <NUM>. The major role of the dialog manager <NUM> is to select the correct system actions based on observed evidences and inferred dialog states from the results of NLP (e.g., dialog act, user goal, and discourse history). In addition, the dialog manager <NUM> should be able to handle errors when the user input has ASR and NLP errors caused by noises or unexpected inputs.

The CIS <NUM> may further include an output renderer <NUM> for transforming the output of the dialog manager <NUM> into a form suitable for providing to the user. For example, the output renderer <NUM> may employ a text-to-speech engine or may contact a prerecorded audio database to generate an audio message corresponding to the output of the dialog manager <NUM>. In certain embodiments, the output renderer <NUM> may present the output of the dialog manager <NUM> as a text message, an image, or a video message for further displaying on a display screen of the user device.

<FIG> shows a high-level block diagram of an example system <NUM> suitable for practicing the present technologies for proactively delivering push notifications. It should be understood by those skilled in the art that all components of the system <NUM> may include logic elements, hardware components, software (firmware) components, virtual components, or a combination thereof. The modules of system <NUM> may be present in one device (e.g., a user device), multiple devices (e.g., in client-server environment), or may be distributed computing modules or cloud computing modules. Further, all modules shown in <FIG> may be operatively coupled using any suitable wired, wireless, radio, electrical, or optical standards.

As shown in <FIG>, the system <NUM> may include one or more input modules <NUM> such as a microphone, touchscreen, keypad, keyboard, touchpad, trackball, video camera (e.g., for gesture recognition), motion sensors, and the like. The system <NUM> may also include one or more output modules <NUM> such as speakers or a display.

The system <NUM> further includes a CIS <NUM> for providing a human-centric interface for accessing and managing information as discussed herein. The CIS <NUM> may be represented by an example implementation shown above with reference to <FIG>.

The system <NUM> further includes an event manager <NUM> for monitoring activities and identifying one or more triggering events. The triggering events may relate to a wide range of various activities or events. Some examples of triggering events may include:.

The event manager <NUM> may refer to a triggering criteria database <NUM>, which may store various criteria, rules, reference triggering events, and so forth. For example, the triggering criteria database <NUM> may store a list of triggering words (e.g., "weather," "email," "where," "schedule," "when," etc.), a list of predetermined geographical locations, a list of wireless networks, a list of peripheral devices, a list of user-CIS interaction types, dialog histories, and many other rules or criteria. The event manager <NUM> may refer to local or remote storage resources <NUM> (e.g., social media sites) for identifying triggering events or refer to any other modules of the system <NUM>.

The system <NUM> may include a push notification manager <NUM> for generating push notifications for the user based at least in part on triggering events identified by the event manager <NUM>, rules stored in rule database <NUM> and/or push notification templates stored in a push notification database <NUM>. More specifically, once the event manager <NUM> identifies a specific triggering event, the push notification manager <NUM> refers to the rule database <NUM> and/or push notification database <NUM> to locate data and/or rules associated with the identified triggering event. Based on the located data/rule and the triggering event itself, the push notification manager <NUM> produces one or more push notifications for the user, which may be then presented to the user via the output module <NUM>.

Notably, there are two types of push notifications. First, push notifications can contain all information to be presented to the user in the form of text, image, video, and/or audio content. Second, push notifications can contain a special instruction to a user device. The special instruction includes text or meta-data that the user device needs to submit to a particular networked server, web storage resources, or web services. The second option can be especially helpful for those CISs that have limitations for push notification messages. Accordingly, in the second option, when a user receives a push notification with such an instruction and opens it to review, the user device can generate a request to a server. The request includes metadata for the instruction and other data (e.g., a current location of the user). In response to the request, the server can create an answer and send the answer back to the user that includes the requested information (e.g., a current weather). When received by the user device, the user device can generate the push notification message "on the fly" and deliver the push notification to the user.

The push notification manager <NUM> may also generate recommendations for the user based on one of more triggering events. For this purpose, the push notification manager <NUM> may refer to the rule database <NUM> and/or recommendation database <NUM>.

For example, when the user travels from Washington, D. to Sunnyvale, CA, the event manager <NUM> may identify the new location of the user (user device) and consider it as a triggering event. Further, based on predetermined rules, the push notification manager <NUM> may generate push notifications to the user with a "Daily Brief" including, for example, weather information in Sunnyvale, traffic information, information regarding local restaurants, new emails, text messages and voice messages received while the user was offline (e.g., in a plane), and most recent information items from subscribed news feeds. The user may further interact with the CIS, for example, to get details of the new emails, messages, and navigation information to selected restaurants and so forth. Some other examples of user-CIS interaction will be given below.

Still referring to <FIG>, the system <NUM> may include a clock <NUM> for providing current time or current time and date for the requesting module. The clock <NUM> may be either internal or remote module. The system <NUM> may further include a geo location determiner <NUM> for determining a current geographical location of the user device. The geo location determiner <NUM> may utilize a number of different methods for determining geographical location including, for example, receiving and processing signals of global positioning systems (GPS), GLONASS satellite navigation systems, or Galileo satellite navigation systems; utilizing multilateration of radio signals between radio towers (base stations); or utilizing geolocation methods associated with Internet Protocol (IP) addresses, Media Access Control (MAC) addresses, Radio-Frequency Identification (RFID), or other technologies.

The system <NUM> may include one or more local or remote storage or computing resources <NUM> including, for example, web resources, web sites, social networking websites, blogging websites, news feeds, email servers, web calendars, event databases, ticket aggregators, map databases, points of interest databases, and so forth. It should be clear that the event manager <NUM> and the recommendation manager <NUM> may also refer to these resources <NUM> for identifying triggering events or producing dialog recommendations.

<FIG> shows a high-level block diagram of an example system environment <NUM> suitable for practicing the present technologies for proactively delivering push notifications. The system environment <NUM> may include a user device <NUM>, distributed modules including a CIS <NUM>, an event manager <NUM>, a push notification manager <NUM>, one or more databases (e.g., a triggering criteria database <NUM>, rules database <NUM>, recommendation database <NUM>, push notification database <NUM>), one or more web resources and/or one or more web services <NUM>, and a communications network <NUM>.

According to various embodiments, the user device <NUM> may refer to a client in a "client-server environment. " In general, the user device <NUM> may include a computer (e.g., a desktop computer, laptop computer, tablet computer), smart phone, wireless telephone, cellular phone, television system, remote controller, gaming console, gaming pad, in-vehicle computer, infotainment system, smart-home computer, and any other electronic device having at least one processing or computational unit. The user device <NUM> should be configured to receive or capture user audio inputs (e.g., via one or more microphones). Furthermore, the user device <NUM> may run dedicated software allowing it to practice the principles of the present disclosure. In an example, the user device <NUM> may run a browser allowing the user to visit a dedicated webpage or access a specific web service which employs at least some functionality of the CIS <NUM> and other modules. In another example, the user device <NUM> may run a dedicated mobile application enabling communication with the CIS <NUM> and other modules. It should be understood that the CIS <NUM>, event manager <NUM>, push notification manager <NUM> and/or other modules or databases <NUM>, <NUM>, <NUM>, <NUM> may be run on the user device <NUM> or a networked server, or they may constitute distributed software application(s) running on both the user device <NUM> and a network server (not shown) or on a plurality of networked servers (e.g., be cloud-based embodiment).

The communications network <NUM> can be a wireless or wire network, or a combination thereof. For example, the network may include one or more of the following: the Internet, local intranet, PAN (Personal Area Network), LAN (Local Area Network), WAN (Wide Area Network), MAN (Metropolitan Area Network), virtual private network (VPN), storage area network (SAN), frame relay connection, Advanced Intelligent Network (AIN) connection, synchronous optical network (SONET) connection, digital T1, T3, E1 or E3 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, Ethernet connection, ISDN (Integrated Services Digital Network) line, cable modem, ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications may also include links to any of a variety of wireless networks including, GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access), cellular phone networks, GPS, CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE <NUM>-based radio frequency network.

In various embodiments, the one or more web resources and/or one or more web services <NUM> may include one or more of the following: webpages, websites, Internet search engines, databases, data storage resources, data aggregators (e.g., ticket aggregators), file sharing websites, email servers, email services, instant messaging services, social networking websites, blogging websites, micro-blogging websites, news services, news Rich Site Summaries (RSS), map services, online banking services, online calendar services, online appointment scheduling services, location determining services, weather services, time services, application programming interfaces (APIs), and so forth. The CIS <NUM>, event manager <NUM>, push notification manager <NUM>, and the user device <NUM> may be configured to operatively communicate with these or similar web resources/web services <NUM> to exchange data depending on an application. For example, the CIS <NUM> may communicate with the at least one web resource/service <NUM> so as to generate responses to user inputs (e.g., to retrieve/download weather information). In another example, the event manager <NUM> may communicate with the at least one web resource/service <NUM> so as to identify triggering events (e.g., identifying a new status of the user's peers via at least one social networking site). In yet another embodiment, the push notification manager <NUM> may communicate with the at least one web resource/web service <NUM> so as to generate one or more dialog recommendations for the user (e.g., communicating with a map service to identify points of interests located near a current location of the user).

<FIG> shows a high-level block diagram of another example system environment <NUM> suitable for practicing the present technologies for dynamic generation of dialog recommendations. In particular, in this embodiment, the CIS <NUM>, event manager <NUM>, push notification manager <NUM> and/or a plurality of databases <NUM>, <NUM>, <NUM>, <NUM> may reside in one or more networked servers <NUM>. It should also be clear that these modules may run in a plurality of networked servers or within a computing cloud.

<FIG> shows a high-level block diagram of yet another example system environment <NUM> suitable for practicing the present technologies. In particular, in this embodiment, the CIS <NUM>, event manager <NUM>, push notification manager <NUM> and, optionally, a plurality of databases <NUM>, <NUM>, <NUM>, <NUM> may reside in the user device <NUM>.

<FIG> illustrates a schematic diagram of a graphical user interface <NUM> for a user device <NUM>, in accordance with an example embodiment. Although the user device <NUM> is a smartphone in the example shown, the same or similar graphical user interface <NUM> may be provided for a desktop or laptop computer, tablet computer, or any other suitable device. In the example shown, the user device <NUM> includes a touchscreen which displays the user interface <NUM>. In the example embodiment, the user interface <NUM> includes a tray (output box) <NUM> where one or more push notification messages <NUM> may be dynamically displayed. Push notification messages <NUM> may be presented as text messages, still or animated image messages, or a combination thereof. In certain embodiments, the push notification messages <NUM> may include some kind of information (e.g., news feeds, weather information, emails, etc.) or just a summary of the information to be provided.

Optionally, the push notifications <NUM> may be presented as actionable messages (buttons) or hyperlinks. The user may have an option to click or select one of the displayed push notifications, which would be equivalent to spoken commands. It should be also understood that the user may speak commands corresponding to the shown push notifications and that the CIS will provide a corresponding response. It should be also noted that the push notification messages <NUM> may also include dialog recommendation messages (or dialog recommendation data).

<FIG> illustrates a schematic diagram of a graphical user interface <NUM> with chat features for a user device <NUM>, in accordance with an example embodiment. Although the user device <NUM> is a smartphone in the example shown, the same or similar graphical user interface <NUM> may be provided for a desktop or laptop computer, tablet computer, or any other suitable device. In the example shown, the user device <NUM> includes a touchscreen which displays the user interface <NUM>. In the example embodiment, the user interface <NUM> includes a tray (output box) <NUM> where an avatar <NUM> is displayed. Optionally, the user can select a different avatar, or construct it from various elements (e.g., select clothes, eyes, hair, etc.). Optionally, multiple trays for multiple topics can be employed. The user interface <NUM> also includes a tray <NUM> for displaying a message (text, image, or video) generated by the system (i.e., a CIS response). The user interface <NUM> may also include a tray <NUM> for displaying user input (e.g., a recognized audio input or manual text input). The user interface <NUM> also includes a tray <NUM> for displaying one or more dialog recommendations generated by the push notification manager <NUM>. The dialog recommendations may be presented as a text, image, video, or a combination thereof. Furthermore, the dialog recommendations may be displayed in separate actionable messages (buttons) or hyperlinks. The user may have an option to click or select one of the displayed dialog recommendations, which would be equivalent to spoken dialog recommendations.

According to certain embodiments, the user may interact with the user interface <NUM> by making a contact or by touching the trays. The user interface <NUM> may also include one or more control buttons <NUM>. The control buttons <NUM> may be used for selecting or changing specific settings, displaying characteristics, or controlling other options. The contact can be a gesture, such as, for example, one or more taps or one or more swipes (from left to right, from right to left, upward and/or downward).

<FIG> is a process flow diagram showing a method <NUM> for proactive delivering push notifications in a CIS, according to an example embodiment. The method <NUM> may be performed by processing logic that may comprise hardware (e.g., decision making logic, dedicated logic, programmable logic, and microcode), software (such as software run on a general-purpose computer system or a dedicated machine), or a combination of both. In one example embodiment, the processing logic resides at the CIS <NUM>, event manager <NUM> and/or the push notification manager <NUM>. In other words, the method <NUM> can be performed by various components discussed above with reference to <FIG>.

As shown in <FIG>, the method <NUM> may commence at operation <NUM> with the event manager <NUM> identifying at least one triggering event. For these ends, the event manager <NUM> may communicate with one or more of the following: the clock <NUM>, the geo location determiner <NUM>, local or remote storage resources <NUM>, and web resources or web services <NUM>. The triggering events may refer to a specific time, presence in a specific location, new message posted on a blogging site, and many other events as described herein.

At operation <NUM>, the push notification manager <NUM> generates one or more push notifications based, at least in part, on the at least one triggering event. In particular, the push notification manager <NUM> may refer to one or more databases <NUM>, <NUM>, <NUM>, <NUM> so as to generate the push notifications following certain rules, criteria or principles. In certain embodiments, some push notifications may include dialog recommendations for the user with suggestions on how user-CIS interaction can be continued.

At operation <NUM>, the push notification manager <NUM> (and/or the output renderer <NUM> of the CIS <NUM> and/or the output module <NUM>) provides the push notifications generated to the user as text messages, image messages, actionable messages, or audio messages.

At operation <NUM>, the CIS <NUM> may receive a speech-based (audio) input from the user. The user input may be made, for example, via a microphone of the user device <NUM>. At operation <NUM>, the CIS <NUM> recognizes at least a part of the user input and generates a recognized input. At operation <NUM>, the CIS <NUM> generates at least one response to the recognized input and provides it to the user as a machine generated audio message and/or displayable text, image, or video message. The output renderer <NUM> and/or output module <NUM> may be utilized for these actions.

In one example implementation, the user may configure CIS <NUM> so that "daily brief" push notifications are generated daily at <NUM> a. The event manager <NUM> may monitor current time through the clock <NUM>, and once it is determined that the current time meets certain predetermined settings, the push notification manager <NUM> generates push notifications following predetermined rules stored in the rule database <NUM>. The push notifications may be presented as audio messages and summarized text messages on a display screen of the user device <NUM>. In an example, the push notifications may include:.

The user may then select one of delivered push notifications or just provide a voice command, such as "Show my emails" or "Show details of scheduled events," so as to get more information regarding desired items. If the user interrupted the sequence of delivering push notifications, he may resume the delivering of remaining push notifications by providing a voice command such as "Back to brief.

In another example implementation, the user may travel from Washington, D. to San Francisco, CA. Once the user arrives to the airport of San Francisco, the event manager <NUM> may identify a triggering event associated with a new and predetermined location. Further, based on this triggering event, the push notification manager <NUM> may generate and provide to the user one or more of the following push notifications:.

In yet another example implementation, the event manager <NUM> may access a web service <NUM> associated with a social network (or the event manager <NUM> may receive a communication from this web service <NUM>) and identify that one of the user's peers in the social network has a birthday in the given day. The push notification manager <NUM> may provide push notifications (reminders) to the user. Optionally, the push notification manager <NUM> may provide dialog recommendations for the user suggesting possible user-CIS interaction with respect to the identified triggering event. For example, the dialog recommendations may include suggestions to call the peer, write an instant message or email, schedule a visit, and so forth.

In yet another example implementation, the event manager <NUM> may identify the presence of the user by monitoring whether or not the user device <NUM> is within a predetermined wireless network. Once, the event manager <NUM> identifies that the user arrives at work (e.g., when a work related wireless network is identified), the push notification manager <NUM> may provide a list of errands or scheduled meetings for the given day. Alternatively, once it is identified that the user arrives at home, the push notification manager <NUM> may provide a Television (TV) guide, or a recommendations for cooking specific dishes or other information relevant to the user.

In yet other example embodiment, push notifications may be generated in response to a user voice command such as "Show me Daily Brief" or simply "Daily Brief. " Alternatively, push notifications may be proactively generated once the user activates a CIS application on the user device <NUM>.

<FIG> shows a diagrammatic representation of a computing device for a machine in the example electronic form of a computer system <NUM>, within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein can be executed. In various example embodiments, the machine operates as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine can operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine can be a personal computer (PC), a tablet PC, a set-top box (STB), a PDA , a cellular telephone, a portable music player (e.g., a portable hard drive audio device, such as an Moving Picture Experts Group Audio Layer <NUM> (MP3) player), gaming pad, portable gaming console, in-vehicle computer, smart-home computer, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system <NUM> includes a processor or multiple processors <NUM> (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), and a main memory <NUM> and a static memory <NUM>, which communicate with each other via a bus <NUM>. The computer system <NUM> can further include a video display unit <NUM> (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system <NUM> also includes at least one input device <NUM>, such as an alphanumeric input device (e.g., a keyboard), a cursor control device (e.g., a mouse), a microphone, a digital camera, a video camera, and so forth. The computer system <NUM> also includes a disk drive unit <NUM>, a signal generation device <NUM> (e.g., a speaker), and a network interface device <NUM>.

The disk drive unit <NUM> includes a computer-readable medium <NUM>, which stores one or more sets of instructions and data structures (e.g., instructions <NUM>) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions <NUM> can also reside, completely or at least partially, within the main memory <NUM> and/or within the processors <NUM> during execution thereof by the computer system <NUM>. The main memory <NUM> and the processors <NUM> also constitute machine-readable media.

The instructions <NUM> can further be transmitted or received over the network <NUM> via the network interface device <NUM> utilizing any one of a number of well-known transfer protocols (e.g., Hyper Text Transfer Protocol (HTTP), CAN, Serial, and Modbus).

While the computer-readable medium <NUM> is shown in an example embodiment to be a single medium, the term "computer-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "computer-readable medium" shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present application, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such a set of instructions. The term "computer-readable medium" shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media. Such media can also include, without limitation, hard disks, floppy disks, flash memory cards, digital video disks (DVDs), random access memory (RAM), read only memory (ROM), and the like.

The example embodiments described herein can be implemented in an operating environment comprising computer-executable instructions (e.g., software) installed on a computer, in hardware, or in a combination of software and hardware. The computer-executable instructions can be written in a computer programming language or can be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interfaces to a variety of operating systems. Although not limited thereto, computer software programs for implementing the present method can be written in any number of suitable programming languages such as, for example, Hypertext Markup Language (HTML), Dynamic HTML, Extensible Markup Language (XML), Extensible Stylesheet Language (XSL), Document Style Semantics and Specification Language (DSSSL), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), Wireless Markup Language (WML), JavaTM, JiniTM, C, C++, Perl, UNIX Shell, Visual Basic or Visual Basic Script, Virtual Reality Markup Language (VRML), ColdFusionTM or other compilers, assemblers, interpreters or other computer languages or platforms.

Claim 1:
A method for proactively delivering push notifications in a chat information system (CIS) (<NUM>), the method comprising:
identifying, by a processor (<NUM>) of the CIS operatively coupled to a memory (<NUM>), at least one triggering event;
providing, by the processor of the CIS, a push notification to a user device using at least in part the CIS (<NUM>), the push notification being based on the at least one triggering event;
receiving, by the user device, the push notification comprising metadata for the user device (<NUM>) to submit to a networked server;
in response to the push notification being opened by a user of the user device, generating, by the user device (<NUM>), a request to obtain information associated with the at least one triggering event from the networked server, wherein the request comprises the metadata;
receiving, by the user device, from the networked server, the requested information in response to the request;
generating, by the user device, a push notification message (<NUM>) on the fly for the user, wherein the push notification message (<NUM>) contains the information received from the networked server and is associated, at least in part, with the at least one triggering event; and
providing, by the user device, the push notification message to the user.