US20170372271A1 - Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data - Google Patents

Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data Download PDF

Info

Publication number
US20170372271A1
US20170372271A1 US15/694,649 US201715694649A US2017372271A1 US 20170372271 A1 US20170372271 A1 US 20170372271A1 US 201715694649 A US201715694649 A US 201715694649A US 2017372271 A1 US2017372271 A1 US 2017372271A1
Authority
US
United States
Prior art keywords
data
meeting
user
system
computing device
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.)
Abandoned
Application number
US15/694,649
Inventor
David Goldsmith
Gary Stephen Shuster
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.)
BUZD LLC
Original Assignee
BUZD LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201261747348P priority Critical
Priority to US201361790249P priority
Priority to US14/035,615 priority patent/US9754243B2/en
Application filed by BUZD LLC filed Critical BUZD LLC
Priority to US15/694,649 priority patent/US20170372271A1/en
Publication of US20170372271A1 publication Critical patent/US20170372271A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/109Time management, e.g. calendars, reminders, meetings, time accounting
    • G06Q10/1093Calendar-based scheduling for a person or group
    • G06Q10/1095Meeting or appointment
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • G06Q10/063Operations research or analysis
    • G06Q10/0635Risk analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/22Tracking the activity of the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/30Network-specific arrangements or communication protocols supporting networked applications involving profiles
    • H04L67/306User profiles

Abstract

A situational and global context aware calendar, communications, and/or relationship management method and system is disclosed. The system is configured to receive non-calendaring related context information, and, based on that context information, to automatically determine one or more parameters of a meeting request.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of and claims priority to U.S. application Ser. No. 14/035,615, filed Sep. 24, 2013, now U.S. Pat. No. 9,754,243, which claims priority pursuant to 35 U.S.C. §119(e) to U.S. provisional application Ser. No. 61/747,348, filed Dec. 30, 2012, and to U.S. provisional application Ser. No. 61/790,249, filed Mar. 15, 2013, which applications are hereby incorporated by reference in their entireties as though fully set forth herein.
  • TECHNICAL FIELD
  • The present disclosure relates to calendar management, and particularly to context aware calendar and relationship management.
  • BACKGROUND
  • Customer relationship management software (“CRM”) systems are frequently used to manage calendars, meetings, and even relationships. CRM is frequently described as a strategy for managing a company's interactions with customers, clients and sales prospects. CRM is frequently used to synchronize sales activities. While CRM is intended to accomplish such goals, the currently available technology fails to meet substantial scheduling, communications, and relationship management needs of individuals and businesses.
  • SUMMARY
  • The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
  • The systems, methods, and devices of the present disclosure provide, among other features, a situational and global context aware calendar, communications, and/or relationship management system (“the system”) configured to provide context aware enhanced calendaring, messaging, notification, and/or relationship management. In various embodiments, interactive visualizations and analyses provided by the system may be based on gathered social media, medical, immunization, insurance, financial, geographic, religious, cultural, weather, public record, traffic, venue, airline and/or other forms and types of data, whether text, graphic, multimedia or in other formats. This data, combined with environmental, contextual, and/or user input sensing allows for modifications to calendaring and messaging interactions that are more effective and efficient.
  • A situational and global context aware calendar, communications, and/or relationship management method and system is disclosed. In one embodiment, the system is configured to receive from at least one environmental data gathering device (such as a camera or microphone), data about at least one target participant at a gathering of a plurality of participants, analyze such data to determine at least one observed behavior (e.g. a potential observed behavior or cue) of said target participant, compare said at least one observed behavior against a dataset of at least one behavior; determine when said at least one behavior exceeds a threshold similarity to a behavior in said dataset; and communicate, to at least one notification device, said at least one observed behavior.
  • In one embodiment, a computing device comprises one or more processors, a memory, and a network interface. The memory may comprise instructions that, when executed by the processor, cause the device to query, via the network interface, a first database, the first database comprising non-calendaring-application context information. In response to the query, the device may receive, via the network interface, a first response comprising a first information, the first information comprising non-calendaring-application context information related to at least one or more persons. The device may receive, via the network interface, a second query regarding a meeting request from a user device, the meeting request comprising one or more invitees. The device may compare the second query to at least one attribute of a first invitee of the one or more invitees, and in response to the comparison, transmit, via the network interface, at least one parameter of the meeting request to the user device, the one parameter being calculated, at least in part, on the first information and the at least one attribute of the first invitee.
  • In an embodiment, the non-calendaring-application context information comprises religious, cultural, or demographic information, and the at least one attribute of the first invitee comprises a religious, cultural, or demographic attribute.
  • In an embodiment, the first information comprises timing information associated with the religious, cultural, or demographic information, and, wherein the parameter comprises at least one recommended scheduled meeting time based, at least in part, on the first information.
  • In an embodiment, the first information comprises dining information associated with religious, cultural, or demographic information, and, wherein the at least one parameter comprises at least one recommended dining location.
  • In an embodiment, the first information comprises location information, and the at least one attribute of the first invitee comprises preference information.
  • In an embodiment, the first information comprises weather information associated with the location information, and, wherein the at least one parameter comprises at least one recommended location based, at least in part, on the first information.
  • In an embodiment, the first information comprises travel information associated with the location information, and, wherein the at least one parameter comprises at least one recommended scheduled location based, at least in part, on the first information.
  • In an embodiment, the first information comprises a stored behavior, the at least one attribute of the first invitee comprises a potential observed behavior (e.g. a cue), and the at least one parameter comprises an observed behavior related to the potential observed behavior.
  • In an embodiment, the stored behavior comprises a travel related behavior, the potential observed behavior comprises a scheduled flight, and the observed behavior comprises a location. In an embodiment, the stored behavior comprises a geographic related behavior, the potential observed behavior comprises a geolocation of the first invitee, and the observed behavior comprises a location.
  • In an embodiment, the first information comprises dining location data comprising attribute values for a plurality of locations, and the at least one attribute of the first invitee comprises dining preferences of the first invitee, the at least one parameter comprising a recommended dining location.
  • In an embodiment, the first information comprises meeting preferences calculated based on a correlation of a population's preferences to the population's location.
  • In an embodiment, the non-calendaring-application context information does not comprise a calendar schedule of the first invitee.
  • In an embodiment, a computerized method may be executed, comprising accessing preference information, the preference information comprising non-schedule related preferences for a first participant, receiving, via a network interface, a query from a user device comprising a meeting request, the meeting request comprising one or more requested meeting parameters, determining the one or more requested meeting parameters based at least in part on the preference information, and transmitting, via the network interface, the determined one or more requested parameters.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the first participant's financial information.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the first participant's medical or immunization history.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the first participant's travel schedule.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the user device's environmental sensors.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the first participant's geolocation.
  • In an embodiment, the method may further comprise automatically generating the preference information on the first participant's religion.
  • In an embodiment, the method may further comprise automatically generating the preference information based on the first participant's demographics.
  • In an embodiment, the non-schedule related preferences comprise dining location preferences.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The following aspects of the disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings.
  • FIG. 1 is a block diagram illustrating an embodiment of the present disclosure that provides situational and global context aware calendar, communications, and/or relationship management.
  • FIG. 2 shows a flowchart depicting illustrative stored behavior creation operations of the system, according to an embodiment of the present disclosure.
  • FIG. 3 shows a flowchart depicting illustrative stored behavior comparison operations of the system, according to an embodiment of the present disclosure.
  • FIG. 4 shows a sample user interface of the system in which a smart calendaring meeting may be initiated, according to one embodiment.
  • FIG. 5 shows a flowchart depicting illustrative image analysis operations of the system, according to one embodiment.
  • FIG. 6 shows a sample user interface of the system in which a smart notice is received, according to one embodiment.
  • FIG. 7 shows a sample user interface of the system in which a smart prediction is received, according to one embodiment.
  • FIG. 8 shows a sample user interface of the system in which a smart warning is received, according to one embodiment.
  • FIG. 9 shows a sample user interface of the system in which tips are recommended, according to one embodiment.
  • FIG. 10 shows a flowchart depicting illustrative environmental sensing and reporting operations of the system, according to an embodiment of the present disclosure.
  • FIG. 11A illustrates sample tips and tip categories, according to an embodiment of the present disclosure.
  • FIG. 11B illustrates sample tips and tip categories, according to an embodiment of the present disclosure.
  • FIG. 11C illustrates sample tips and tip categories, according to an embodiment of the present disclosure.
  • DETAILED DESCRIPTION
  • Current calendaring, messaging, and CRM systems track and manipulate meetings, messages, and relationships between users. The present disclosure describes improvements to existing systems, such as improved methods of using the information collected by these systems, combining and comparing it with external context information (either from the environment, or recorded in a variety of public or private data sources) and outputting, in a variety of user interfaces, information to enable the user to act appropriately in an environment and to maximize usefulness of electronic meeting requests or other messages.
  • The present disclosure presents a variety of methods, systems, articles and apparatuses for calendar, communications, and relationship management and enhancement. In one embodiment, a computer obtains and/or generates a data set and performs analysis to automatically determine whether proposed or attempted meetings or communications are contraindicated by correlations between the proposed or likely participants (where the term “meeting” or “communication” is used alone herein, it should be understood that each term may include the other, and that a “meeting” may reference a desired or proposed meeting). Similarly, proposed or attempted meetings or communications (e.g., smart meetings), or alterations thereto, may be suggested by the intelligent assistant hub system, described with respect to FIG. 1 below, based on one or more correlations between the data set and the participants in the meeting or communication. In one aspect, the system may identify the likely acceptability of meeting times by ranges (such as 1 to 10), percentages, or groups (such as “clear”, “possible issues”, “likely conflict”, and “known conflict”).
  • Although meetings or communications may be between pluralities of people (participants), the term “Meeting Partner” (or primary participant), a broad term that encompasses its plain and ordinary meeting, may include the person with whom the system (or a user of the system or method) is attempting to communicate or set up a meeting with. While Meeting Partner is grammatically singular, it should be understood herein that even when used in the singular, it may include a reference to more than one person, as in the case of a meeting set up between a user of the system and ten other people (some, all, or none of which may also be users of the system).
  • The systems and method described herein may improve electronic meeting requests through the use of “smart meetings,” which are automatically generated and/or interactive meeting request (or management) tools that may make specific recommendations to a user based on detected context data, or may wholly create new meetings (or update existing meetings) based on detected context data. As an example, in one embodiment, a user (primary participant) who will be in Brazil from Apr. 20-24, 2011 may wish to set up a meeting with a participant who is an observant Jew and another participant who is a vegetarian. The system can obtain data pertinent to the potential participants, for example by being provided data, by analyzing public and private sources, by analyzing social media such as by analyzing the Twitter™ feed of participants, etc. When the user attempts to send a meeting invitation for April 21, the system informs him that it is Tiradentes' day, a public holiday in Brazil. When the user attempts to schedule for the evening of April 22, the system warns him that April 22 is a Friday and one of the participants has indicated on Twitter that he is an observant Jew, and for observant Jews, Shabbat prevents working after sundown on Fridays, which is 5:34 p.m. on that particular day. The system may then inform the user of the best meeting time or times, considering traffic patterns, likely times that participants will be tired due to jetlag (having calculated their prior time zone, if available how long they had been in that time zone, and how long they would have been in the meeting time zone prior to the proposed meeting time) or other factors (such as the length of time between the last flight together with the length of the flight, and even class of service, which together provide clues as to likely participant fatigue), the schedules of the participants, the conflicts with local holidays or traditions, the conflicts with participant holidays, traditions or observances, venue availability, cost of transportation to the proposed meeting place as it varies with date and time, and cost, availability, condition (such as how crowded a restaurant may be) of the meeting place, and/or any other data associated with the planned meeting that may be useful.
  • As the example depicts, the system may access and/or use a variety of databases or data stores in order to improve meeting requests (or other messaging or environmental awareness). These data stores may include databases and information stores that are unavailable to calendaring or scheduling applications. For example, Microsoft Outlook stores calendaring or scheduling information about its individual users (such as the times when they are available or unavailable), or may store calendaring or scheduling preferences for each user to assist in scheduling meetings (such as blocking out time on all Thursdays to prevent any meetings occurring for that user on those days). Microsoft outlook uses this information to assist in creating meeting requests. However, Microsoft Outlook does not have access to, and does not make any scheduling decisions on, non-calendaring-application information, non-scheduling information, and non-scheduling (or non-calendar) preferences. The current disclosure, however, does describe how to use context information (e.g. non-calendaring-application information, non-scheduling information, and non-scheduling (or non-calendar) preferences) to assist in formulating smart meeting requests, performing meeting scheduling, providing smart messaging, and making CRM decisions, among other computerized actions.
  • Referring to FIG. 1, this figure is a block diagram that shows how the system may be connected, according to one embodiment. The Intelligent Assistant Hub 110 (also referred to herein as “the system”) may comprise an Internet connected computer server, servers, or cloud system, and has access to many networked databases. For example, Intelligent Assistant Hub 110 may have access to behavior data 150. This behavior data may comprise stored behaviors, such as behavior rules. For example, a stored behavior may comprise an electronic rule indicating that “if a person has eaten at restaurant Y X times, then the person prefers restaurant Y.” The variable X may be a threshold for the comparison and can be set automatically based on observed information in comparison to user preferences, or set by a user or administrator. Stored behaviors may apply to many scenarios and are used, in the typical case, to make an educated guess based on observed or gathered data that may be used by the system to categorize a target, participant, item or location, among other things. A stored behavior need not require a threshold. A stored behavior, as used herein, is a broad term, and encompasses its plain and ordinary meaning, and may include rules about human behavior as described above, but may also include rules about behaviors or attributes of locations or items.
  • Behavior data 150 may also store other behavior information in addition to stored behaviors. For example, behavior data 150 may store locally, for the intelligent assistant hub 110, data gathered from one or more private databases 106, public databases 122, or participant systems 108. This data may be a copy of the data in those databases, or may be analyzed, summarized, or processed data from those databases. For example, data from geographic data store 164 may be gathered by intelligent assistant hub 110. This data may comprise data indicating that Brazil has an average humidity of 41%. This data may then be compared to a stored behavior when a user is attempting to initiate an electronic meeting request for a meeting in Brazil. The intelligent assistant hub may compare the 41% humidity value for Brazil to a stored behavior that indicates that all meetings should be held indoors if humidity exceeds 40% in any location. Such a behavior rule may be set by a system administrator, by the meeting coordinator, based on data associated with other planned meeting participants, etc. Behavior data 150 may also include a cache. This cache may allow for quick access to behavior data that is frequently accessed, or for outside database information that is frequently gathered.
  • Participant data 140 may also be accessed to either create a stored behavior, or to be compared to stored behaviors. Participant data may include data gathered from environmental sensors 128 across one or more participant devices 108. These sensors may be gathering health, location, temperature, image, audio, and/or other contextual information on a periodic, intermittent, or constant basis. For example, a participant system may record the temperature in its current location every 5 minutes, and send the current temperature and location value pair to the participant data database 140 for storage. Or it could record all images and associated metadata for the images (time taken, location taken, etc.) that were taken by the participant device 108 with camera 126. This information may then be sent to the Intelligent assistant hub 110 and stored (either analyzed, summarized or in raw form) in the participant data database 140, which may comprise a local database (or other data structure) and/or a cloud based system.
  • Participant data 140 may also store tracked participant users' actions within the system. For example, the intelligent assistant hub 110 may track explicit or implicit preferences of participants. As an explicit preference, a user may be able to state that they prefer to eat at Mexican food restaurants, or do not prefer coffee houses as meeting locations. Alternatively, or in combination, the system (such as the participant preference module 120) may track user interactions to implicitly determine these preferences. For example, if a user declines invitations for meetings at Italian restaurants three times, then the system may analyze this information and conclude that the user prefers not to eat at Italian restaurants. This preference detection could also be expressed in terms of a stored behavior. Like behavior data 150, participant data 140 may also include a cache. This cache may allow for quick access to participant data that is frequently accessed.
  • Intelligent Assistant Hub 110 itself may support and implement traditional calendaring and messaging features, or may work in conjunction with one or more other calendaring and/or messaging systems. In addition, the Intelligent Assistant Hub 110 may implement portions of the system that use a variety of modules or sub-components (which may be implemented in hardware and/or software, in a single computing device or across multiple computing devices).
  • The environment data analyzer module 112 may be configured to communicate with participant systems 108, public data systems 122, private data systems 106, behavior data 150, and/or participant data 140 (or other sub-components). The environment data analyzer module 112 may, among other functionality, analyze data to determine new stored behavior rules to store in behavior data 150, or analyze incoming environmental sensor data or meeting request data, and compare them to stored behaviors to make a behavior determination. These comparisons may trigger outputs helpful for setting up meetings or informing participants, as disclosed generally herein, or may be passed to the intelligent suggestion module 114 or participant preference module 120 for further analysis.
  • In some embodiments, the intelligent suggestion module 114 may itself be configured to analyze incoming environmental sensor data or meeting request data, and compare them to stored behaviors to make a behavior determination. Like the environment data analyzer module 112, the intelligent suggestion module may compare observed data to stored behaviors in order to provide suggestions, warnings, notifications, tips, etc. to participants when those participants are using the system (or possibly to non-users of the system, such as with an invitation to enroll in a service provided by the system to continue to receive similar notifications). When a stored behavior is met, the intelligent suggestion module 114 determines the appropriate suggestion(s), warning(s), notification(s), or tip(s) (or other information) to be sent to a participant system and to be displayed (and/or stored).
  • The participant preference module 120 may be configured to access (and store) participant data 140, receive and store explicit user preferences, and determine and store implicit user preferences based on tracked participant data.
  • The intelligent assistant hub 110 and its sub components, whether implemented in the cloud, across multiple servers, or in a single server, may comprise display 142 for displaying output to an administrator or user, non-transitory storage 144 such as memory, hard drive, or other permanent or semi-permanent storage (e.g., magnetic, optical, volatile and/or nonvolatile semiconductor memory), and processor(s) 136 that may execute programmatic instructions stored in storage 144 to execute and implement via software and/or hardware the systems and methods herein. The intelligent assistant hub 110 may also comprise other 1/0 component(s) 148 such as other input, audio and networking components.
  • A participant system 108, in general, may be used by the participant to initiate messages and calendaring requests, received warnings, tips, notifications and messages, and/or otherwise interact with the system. A participant system 108 may comprise a computer (such as a pc computer, mac, or laptop, running any operating system), mobile device, tablet, smartphone, smartwatch, smart glasses, or other networkable devices. The participant system 108 may comprise display 132 for displaying output to an administrator or participant, non-transitory storage 134 such as memory, hard drive, or other permanent or semi-permanent storage (e.g., magnetic, optical, volatile and/or nonvolatile semiconductor memory), and processor(s) 136 that may execute programmatic instructions stored in storage 134 to execute and implement via software and/or hardware the systems and methods herein. The participant systems 108 may also comprise other 1/0 component(s) 138 such as other input, audio and networking components. In some embodiments, certain functionality, modules, software and/or hardware, of one or more participant systems 108 and the intelligent assistant hub 110 may be combined into a single device. For example, in one embodiment a participant system 108 may include software functionality to perform methods discussed herein with reference to the modules 112, 114, and/or 120 of the intelligent assistant hub 110.
  • A participant system 108 may also include one or more data gathering device 124, such as a camera 126 and/or other environmental sensors 128. These components may be used to gather environmental data that is processed by the environment data analyzer module 112, the intelligent suggestion module 114, and/or the participant module 120. A participant system 108 may also comprise a user interface application 130, which may include a computer application or mobile application, that may implement CRM, calendaring, or messaging functions, in addition to providing smart meeting and contextual messaging user interface support. The user interface application 130 may communicate with the data gathering device 124 and the intelligent assistant hub 110 using traditional operating system communication or networking techniques.
  • The intelligent assistant hub 110 may access a variety of databases in order to determine triggerable stored behaviors or for comparison to stored behaviors, in addition to the stored behaviors already stored in the behavior data database 150 and the participant database 140. These databases may be used in order to make determinations about individuals, or groups of individuals, and may be received or analyzed, or reported with in an anonymous manner if necessary.
  • For example, the intelligent assistant hub 110 may access one or more private data systems 106 that each have data on one or more participants, or one or more contacts of participants, such as financial data 176 which may include banking data, investment data, spending habit data, credit card data, and/or other financial data. Airline data 174 (or other travel enterprise data) may be used to track an individual's flights, flight schedule, on time information, or to model stored behaviors across a general population with regard to travel. Venues data 172 may track availability of venues, as well as attributes of venues (such as the kind of food a venue serves, its average temperature, seating arrangements, etc.). Social media data (for example, Twitter, Google+, Facebook, lnstagram, Pinterest, etc.) may be accessed, including all of the related images and text associated with a user. Medical history and immunization history data 168 may also be accessed, for example, to determine whether it is safe for a user to travel to a foreign country for a meeting, or whether certain foods that are being eaten may conflict with a user's history of heart disease. Insurance data 166 may also be accessed to make a correlation with a participant's driving habits (such as whether they typically drive fast or slow based on number of speeding tickets received), or to determine how risk averse a participant is.
  • Public data systems 122 may also be accessed for similar purposes. For example, geographic data 164 (such as average temperature, national holidays, popular diseases, etc.) for an area may be accessed to inform meeting requests and make decisions about logistics for meetings that are occurring. Similarly cultural data 162 or religious data 161 may store religious or cultural holidays, traditions, or faux pas that may be used to smartly organize meetings or to warn a user of potential embarrassment when dealing with people of specific religions/cultures. Other public data may be accessed, such as weather data 156 (yearly weather patterns, 10 day weather report for an area, etc), public records (such as business or corporate registrations, criminal records, etc), and traffic data (such as average fastest ways to drive, or current traffic delays).
  • The above databases are only examples of the type of data that may be accessed by the system, but the system is not limited to accessing only these databases, or accessing them only for the reasons cited above. Each of these databases may be used to determine related behaviors for an individual, or general behaviors across a population for determining new stored behaviors.
  • Example Generation of Stored Behaviors
  • Referring to FIG. 2, a process is described for creating and storing stored behaviors used by the system to enhance CRM, calendaring, and messaging functionality, according to one embodiment. Depending on the embodiment, the method of FIG. 2 may include fewer or additional blocks and/or the blocks may be performed in an order that is different than illustrated.
  • In block 202, one or more data stores of the data stores described herein (but not limited to the data stores described herein) may be accessed for both underlying data and outcome data. Underlying data, is a broad term, and may include its plain and ordinary meeting, and also include any data that may be used to correlate, determine causation for, or model a stored behavior. Outcome data is a broad term, and may include its plain and ordinary meaning, but may also include any data that is dependent on underlying data. For example, traffic data may be accessed and transmitted from the traffic data database 152 to the intelligent assistant hub 110, including the volume of cars travelling a specific highway during certain time periods, and the speeding traffic tickets issued for that specific highway during the same time periods. In this example, the volume data may be considered the underlying data, and the traffic ticket data the outcome data (or vice versa depending on which direction the correlation is calculated).
  • In block 204, the intelligent assistant hub 110 and/or its subcomponents may then correlate (or otherwise model, or determine causation for) the underlying data and the outcome data. For example, a correlation may be calculated that states that if volume of cars increases, then speeding tickets decrease. In this case, the underlying data may be considered the volume of cars, and the outcome data the decrease in speeding tickets.
  • There are multiple embodiments for determining causation or correlation. For example, predictive modeling may be used including neural networks, heuristic models, statistical models, regression models, linear regression models, discrete choice models, logistic regression, multinomial logistic regression, probit regression, time series models, survival or duration analysis, classification and regression trees, machine learning, multivariate adaptive regression splines, multilayer perceptron, radial basis functions, support vector machines, and/or Bayesian modeling, among others.
  • Other correlation techniques do not require modeling. For example, if a religious database indicates that the Jewish faith requires their followers to not work on a high holiday, no additional analysis may be necessary for this stored behavior.
  • The system simply records that, if the date matches a high holiday and a particular participant or user is Jewish, this stored behavior may be triggered.
  • In block 206, after determining the causation or correlation, the system may store or record the analysis within the behavior data database 150 (e.g., a stored behavior). Various parameters may be included in the stored behavior, including the strength of the correlation or causation.
  • In block 208, optionally, the system may determine a threshold for the stored behavior. In one embodiment, this determination may include analyzing (for example, via various models described above), the strength of the correlation to determine a threshold at which an observed behavior (e.g. a potential observed behavior or cue) may match a stored behavior. Using the car volume and speeding ticket example, the system may determine that, if car volume increases to a certain amount, then the stored behavior will trigger an indication that the risk for a speeding ticket has been significantly reduced. The stronger the correlation, the less of an increase that may be required, and thus a lower threshold may be allocated to the stored behavior.
  • Example Comparison of Observed Behaviors to Stored Behaviors
  • Referring to FIG. 3, an example of how to use a stored behavior to enhance calendaring, messaging, or CRM functions is described according to one embodiment. Depending on the embodiment, the method of FIG. 3 may include fewer or additional blocks and/or the blocks may be performed in an order that is different than illustrated.
  • In block 201, the participant or user may select a calendar, messaging, or CRM task to be performed. This may include, by way of example, the user preparing a new meeting request to meet a potential customer, preparing an email to a supplier regarding new opportunities, or adding a new contact to a CRM system. User interaction is also not required. A user need not be the initiator for selecting a calendar, messaging, or CRM task. For example, a meeting or message task may be triggered automatically without user intervention, such as whether or not to send a message that notifies a participant that a meeting should be rescheduled due to an attendee's illness learned of through a social media context.
  • This may also include the participant device 108 or intelligent assistant hub 110 performing automated tasks. For example, the participant device 108 may be monitoring a user's location. The participant device 108 may also be aware of the user's calendar, including a meeting at 2 pm. The participant device 108, as a part of block 201, may automatically initiate a check to determine whether, based on their location and current traffic, the user will reach the destination before 2 pm without any interaction by the user.
  • In some embodiments, other data associated with the participant may be automatically monitored, such as in response to the participant device 108 (and/or one or more other public or private data sources) providing data to the intelligent assistant hub 110 and the intelligent assistant hub determining which stored behaviors to check based on the data received, which may include the current status of the participant, where he is located, the type of person he is meeting with, etc.
  • In block 202, the participant device 108, and/or the intelligent assistant hub 110 may receive, data about the target participant. Using the example above (but not limited to this example), the data transferred may include the stored behavior(s) to be checked (traffic speed I destination estimate), the potential observed behavior data (current location and speed, or any traffic cue), and any other parameters the stored behavior check may require. Alternatively, no stored behavior may be specified.
  • In block 204, the received data is analyzed to determine at least one observed behavior of the target participant. The intelligent assistant hub 110 and/or its sub-components may analyze the received potential observed behavior data to determine whether the data indicates an observed behavior. This may comprise selecting certain received data (including, but not limited to, using all received data without a selection) for use in checking against stored behaviors.
  • In block 206, the observed behavior may be compared with one or more stored behaviors. This may include whether the received data matches the one or more stored behaviors to be checked. In other words, is the data sufficient to match a possible stored behavior.
  • In block 208, optionally, the system may determine when the similarity between the observed behavior exceeds a threshold with one or more of the stored behaviors. As disclosed herein, a stored behavior may have a threshold. For example, some observed behaviors will not trigger (or cue) a stored behavior because the observed behavior data did not meet a threshold required to trigger the stored behavior (e.g. is the distance between the participant and another user sufficient to trigger a stored behavior that indicates that the participant is standing too close to another person in a given culture). Other stored behaviors may not have a threshold (e.g. an indicated holiday for a Jewish person), and are more binary checks.
  • In block 210, the intelligent assistant hub 110 may transmit, to the participant device 108, an output based on determining one or more triggered stored behaviors, where a “triggered” stored behavior is one that has been matched by the observed behavior of the participant. The participant device 108 may then display (or otherwise notify the participant, such as via audible signal), in the context of the current user's interaction (such as a meeting request, message, CRM interface, or in a notification, or warning, etc), information based on the triggered stored behavior. For example, if the stored behavior that was triggered corresponded to a notice that an invitee to a meeting request is Jewish and would not likely make a meeting on a Friday, that information may be displayed within the meeting request, or otherwise communicated to the user through the participant device 108.
  • Example Participant Notifications
  • By way of illustration, multiple embodiments of the context aware system described above will be discussed.
  • For example, in one embodiment, the system may use real time data. For example, if a participant's meeting is in downtown Los Angeles and the participant is in Santa Monica, the system, based on previously stored behaviors correlated and created based on the data disclosed above, can alert the participant to leave at a particular time, taking into account current traffic, predicted weather, participant's driving history and average speeds, the importance of being on time (more conservative v. less conservative departure time), and/or other factors. In some cases, as the participant is running late, the system could alert the participant to drive faster and/or notify the other participants of the participant's status, etc. The system can also be connected with GPS data and could inform the participant if she has taken a wrong turn or assist in directions to get to the meeting. The system can also alert the participant if the meeting time is modified by other factors, for example, if other participants are also running late. The system can balance meetings by priority, so if other participants of the meeting are running 30 minutes late, it may send a cancel notice to those participants or prompt to send a cancellation notice so that the participant is not late for another meeting. In one embodiment, if the meeting is cancelled, it should rearrange the participant's schedule and notify.
  • Among other factors, in addition to the data sources described under FIG. 1, the system may incorporate data (which can be understood as including both planned and predicted data) about national holidays, cultural holidays, exchange rates, climate forecasts, climate patterns, the statistical likelihood, for certain times and places, of climate extremes such as monsoons or hurricanes, actual predicted climate extremes, long-term climate trends, special events, strikes, civil unrest, travel restrictions, travel safety, reliability, nature, availability and cost of travel to a destination, reliability, nature, availability and cost of travel within a destination, political events, political stability, geopolitical threats, proposed or pending laws or regulations, legality of transport of required or desirable items, such as prescription medicines, to a proposed destination, cost, and availability of local talent, communications and infrastructure availability, nature, cost, and reliability, availability, nature, cost and reliability of translators, similarity between local language and participant languages, and frequency with which persons likely to be encountered during travel (such as cab drivers) speak the participant's language sufficiently to avoid errors or misunderstandings.
  • In one embodiment, the system may have access to a data set with public and/or private information about the participants in the meeting or communication. An embodiment of a method of populating the participant data 140, used to determine stored behaviors and/or observed behaviors (based on potential observed behaviors or cues), and/or update other databases, is described below. For example, public data systems/public data sources such as the Google™ search engine, Google+™, Facebook™, LinkedIn™, the Bing™ search engine, travel sites (sites herein may include databases), airline sites, sunrise/sunset calculation sites, Wikipedia™ or other general data sources, IP address geolocation sites, name analysis sites such as ones that provide an inference about age, religion, national origin or other characteristics based on name, genealogy sites, personal data compilation sites, traffic tracking sites, weather tracking sites, weather prediction sites, real-time and historical flight data sites, and Twitter™ may be sources of information. Some information may be input directly, such as a database of holidays for certain countries. Other information may be determined programmatically, such as sunrise or sunset times. A further aspect may include obtaining and/or sharing such data via at least one application programming interface (“API”). A further aspect may include obtaining data by impersonating a user of a service, such as by utilizing the Facebook™ or LinkedIn™ credentials for the user on whose behalf the system is operating. In one aspect, the terms of service for sites may be categorized, either programmatically, manually, or by a combination thereof to determine whether such impersonation or other access is acceptable. In one implementation, terms of service and applicable laws may be analyzed, and/or a database of pre-analyzed terms of service and/or applicable laws accessed, and a determination made as to whether a particular data source may be utilized. Additional data sources may be utilized. For example, Lexis/Nexis™ and other paid and/or private data systems/sources are available.
  • In one aspect, previous presentations, PowerPoint or similar presentations, speeches, and other data may be utilized. In one aspect, video and photographs may be identified using face recognition technology, and voice data may be identified using voice recognition technology. The content of the data may also be analyzed to identify the origin and relevant data within such content.
  • A further aspect may include caching some or all such data, such as in the behavior data cache 150 and participant data cache 140, and refreshing the cache after a certain amount of time (or in conjunction with the first use of the data after the passage of such amount of time), and/or after the occurrence of certain events, which amount or events may vary by data source and/or analysis target. A further aspect may include refreshing the cached data after different amounts of time depending on the type of meeting or communication or whether the cache contains sufficient data. Such caching policies may be combined in whole or part. A further aspect may include identifying the most recent geographic location from one or a plurality of data sources, where such data sources include geographical location of a user posting data (or associated with posted data). A further aspect may include identifying any people recently or currently with another person, which data may be obtained from data sources that record that one person is near or with another person. Proximity in time and place may be used to infer that people were at or near the same location at the same time. Uses of such data include an automated system to identify associations between people, identify witnesses to an event, allow emergency messages to be sent to persons who are near the person intended to receive the message, to detect improper contact (such as monitoring a parolee who is not permitted to be near children or a person who is subject to a restraining order), among other uses.
  • A further aspect, in addition to the data sources listed in FIG. 1, may include monitoring network traffic (including via techniques such as packet sniffing, proxy server monitoring, monitoring at a router or switch level, cached data analysis, screen scraping, a browser plug-in that accomplishes or assists in data capture, or other methods). In an aspect, monitoring may be limited to the capture of data meeting certain criteria, such as data useful for the systems and methods described herein.
  • A further aspect may be the establishment and/or use of a network of wireless MAC address detectors, wireless network detectors (in particular with reference to mobile hot spots), and other mechanisms capable of identifying a unique or likely unique wireless identifier or transmission. Such detectors would report such data and the data may be utilized to infer the location of a person, or of some number of persons within a group of persons with access to the device emitting the unique or likely unique identifier or transmission.
  • A further aspect is analysis of other available data, such as analysis of files stored locally or over a network and available to the user. In one implementation, files not generally available to the public, such as over a non-authenticated internet connection, but available to a user or organization, may be indexed or mined for data. In one aspect, only data useful for the systems and methods described herein would be obtained.
  • It should be understood that while various aspects describe access to, or analysis of, very large amounts of data, such as the data sources described under FIG. 1, a far smaller set of data may be utilized. Indeed, in one implementation only data manually input by a user may be utilized. Similarly, regardless of what data may be utilized to begin with, the system may be programmed to heuristically determine additional data and/or to determine the relevance of extent data. For example, a user who always rejects meeting invitations taking place after sunset on a Friday but before sunset on Saturday may be scored as likely to be an observant Jew (e.g., may have that indication added to a participant profile stored in the participant data 140, possibly with an indication of a score or confidence level that the determined attribute of the participant is accurate). While a more simple scoring mechanism (such as “unlikely to accept Friday night meetings”) may be useful as well, it does not provide the additional data associated with a determination of the cause of the scheduling pattern. Identifying the cause—in this case, that the user is likely an observant Jew—allows the system to provide additional guidance, such as arranging a meeting at a restaurant that has Kosher options available. Two or more individuals exhibiting similar patterns (or who are related) may be inferred to be more likely to share other patterns, particularly where there is insufficient data about at least one of the individuals with regard to such pattern.
  • Data from Facebook™, Twitter™ and certain other services feature status updates that include very current data, often including the geographic location where an update was posted from, the time and date of an update, and, in some cases, the people who are with the person posting the update. Indeed, services such as Foursquare™ and Facebook™ allow people to expressly “check in” to locations and post that information to publicly available databases (note that in some cases, data access may be restricted by user choice, privacy policy, or for other reasons). Where data about one person is not available, known associates of that person may be used as search keys to determine if they have indicated where the person is located or has been located. Even without an express indication, an inference may be made based on past activity. In one aspect, an application running on a (portable for the most part, although fixed may work when reporting when a user returns to a known location) device may be used to communicate with the intelligent assistant hub 110 to provide the location of the user and/or information usable by the intelligent assistant hub 110 in determine that location. Venues may report the presence of computers or devices hooking up to (or visible to) their networks via MAC address or other unique code.
  • With regard to caching policy, and with respect to FIG. 2, behavior data cache 150 and participant data cache 140, current status updates may be retrieved every time the system is utilized, for example. In another aspect, once a sufficiently current update (or other data point) is found, the system may be programmed to cease searching additional databases for the same data. For other data, such as a person's religion, caching policy may dictate that the information only be refreshed at lengthy intervals, only when the information is retrieved as part of another search, or by the sooner of the two to occur. Note that data collection or analysis via the analysis of cached data, such as in a user browser, in order to populate one or more of the data sets is normally a completely different cache than used by the system, although in certain cases there may be partial or full sharing of cache contents or space.
  • Cross-updating of records is an additional feature that may be present in some implementations. For example, if Joe's record was last updated ten days ago and is thus within the “use cached data” window, but updated data about Joe is retrieved in the course of obtaining data about his office-mate Fred, Joe's data may be updated as well.
  • In one aspect, data regarding associates of the primary person or persons with whom communication or a meeting is desired may be gathered by the intelligent assistant hub 110. Data on such associates may be tracked and correlated with the primary person or other associates. Similarly, data incidentally obtained pertaining to associates of a person may be stored in a cache or database in order to reduce the requisite data retrieval in the event that data about that associate or associates needs to be obtained in the future (such as if that associate accompanies the primary person to a meeting).
  • In one aspect, as another data source, heuristic, correlation, or other analysis of communications may be utilized to determine the characteristics of a communication that receives a desired type of response. For example, emails sent to a user that are under 100 characters long may receive a brief but fast response. Similarly, emails sent to a user after 3:00 p.m. on a Wednesday may never be returned before Thursday morning, and even then are returned with a brief response. The user may be asked to rate or categorize the type of response in order to populate such a database. Alternatively, or in addition, automated analysis or modeling may be done to rate or categorize the type of response. In one aspect, the utility of the response may be measured by the way the user utilizes or interacts with it. For example, responses that frequently elicit a meeting scheduling request, a lengthy response, or a long time spent reading the response may be scored accordingly.
  • Users may also “vote” or rank the quality of system performance in order to provide additional guidance for the system to adjust its rating system and behavior.
  • As another data source, the volume and type of inbound communications from a sender may be utilized to determine characteristics about the sender, which characteristics may additionally be used to further improve the predictive capabilities of the system. It should be understood that acceptance, type of acceptance, characteristics of acceptance, non-acceptance and characteristics of non-acceptance of outbound communications to the person being analyzed may be utilized in addition to, or in place of, inbound communications for these purposes. In one aspect, telephone records, SMS records, email records, Facebook™ communications records and other records may be analyzed to determine when communications take place, the type of communication, the modality, and other characteristics. For example, the intelligent assistant hub 110 may analyze such records and determine that on 95% of days, no communications come from user Joe between 3:00 p.m. and 3:50 p.m. on Wednesdays, and may infer that Joe has a recurring appointment during those times. Similarly, the system may determine that communications with Joe occur via work line 80% of the time before 5:00 p.m. on workdays, by cellular phone 80% of the time after 5:00 p.m., 50% of the time by cell and 50% of the time by home phone after 6:00 p.m., and 99% of the time from the home phone after 7:00 p.m. The system may also determine the normal commute time between Joe's work and home (and may even use traffic, weather or other data for specific days on which communications being analyzed took place) and may infer that Joe normally leaves work at or around 5:00 p.m., sometimes stops on the way home, and is almost always home by 7:00 p.m. Accordingly, the system may route communications in a manner that accommodates the travel schedule (for example, by not sending SMS messages during Joe's commute time if Joe lives in a state where it is illegal to text while driving, by holding the transmission of text or email messages until the normal commute time has expired, by routing a phone call to the most likely phone system to answer, by warning the sender of Joe's schedule or seeking sender permission before altering the communication, or otherwise).
  • As an additional data source, the content of social media may be gathered and analyzed to determine stored behaviors for specific individuals. Feedback provided by potential meeting request or communications recipients, either with regard to a message sent by the system or by another method or by another user may be analyzed to determine additional characteristics of optimal communications or scheduling with such recipient. For example, if a recipient posted on Twitter™ “Don't you hate idiots who schedule while the Dodgers are playing?”, future meeting requests may be correlated to not be sent requesting a meeting during a Dodgers game. If there was already a meeting request outstanding to such recipient in violation of the new preference, it may be withdrawn automatically, rescheduled automatically, or rescheduled with the consent of one or more participants.
  • Physical requirements may be compatible only in certain sequences. For example, when scheduling a meeting at a coffee shop, a networking basketball game, and a meeting in an office, the clothing required for the office meeting would be incompatible with that for the basketball game; if the basketball game preceded either of the other meetings, the person would need time to shower and care would need to be taken to make sure that the temperature in any immediately following meeting would not be so high as to trigger sweating as a result of the increased metabolism following exercise. In one implementation, the system would incorporate such requirements into the scheduling.
  • In scheduling meetings or even travel, the physical environment of the meeting participants (such as clothing) at each stage is of importance. In addition, desirable physical characteristics vary with cultural norms, cultural expectations, legal requirements, the physical characteristics of the person, the clothing worn or available to the person, and the preferences of the person. In one implementation, the likely temperature or temperature range in one or more potential meeting venues (or routes, hotel rooms, etc.) may be used to advise as to clothing to bring, to properly sequence events, to choose between a plurality of potential locations, etc. The system may utilize actual temperature or other data to replace projected data where actual data is available. For example, average hotel temperatures, the availability and types of hotel climate control, presence of patio heaters or misters at outdoor restaurants, average restaurant temperature may all be utilized to manage travel, meetings, and other events. Indeed, such information may be used to determine an appropriate place within a location, such as by reserving a table near the entrance in a restaurant that is overheated in the winter. Where meetings happen by audio or videoconference, the system may automatically correct errors or may augment features of the participants. For example, a man having a meeting with an orthodox Jew may offend that participant by not wearing head covering. The system may automatically add head covering to the transmitted digital image, such as a meeting invitation that is sent to that particular participant (various participants in a same meeting may receive different information in their corresponding meeting requests). Similarly, accents may be corrected, “pause words” such as “um” and “you know” may be eliminated, and other elements corrected. By maintaining a database of such information and/or gathering such information as needed, the system is able to better meet the needs of its users.
  • Example Smart Meeting Request
  • An example user interface for a “smart meeting” request produced by the system is depicted in FIG. 4, according to one embodiment. The meeting request user interface may comprise a plugin to a standard outlook (or other calendaring system) user interface. In other embodiments, the smart meeting user interface may be part of a stand-alone calendaring system provided by the system, or some combination thereof. For example, the user interface 400 shows a modified outlook meeting user interface that includes a smart meeting tab with additional features compared to a normal, non-context aware, meeting request.
  • The smart meeting user interface may automatically populate invitees based on context. For example, text input area 450 or subject text area 404 may contain information about the context of a meeting. Based on this information (and/or other information), the user interface may automatically select contacts from a participant's set of contacts (or contacts based on contacts known by the system) that would likely be invited to a meeting regarding the subject matter entered. This selection may be made based on information (such as individual stored behaviors) gathered about these contacts via the data sources listed in FIG. 1, or throughout this disclosure. This field population may be accomplished by local processing on the participant device 108, or by sending an electronic query containing the subject line 404 and/or text data 450 to the intelligent assistant hub 110 for processing. The intelligent assistant hub 110 may respond by transmitting to the participant device 108 a list of contacts (optionally including a likelihood indicator of attending, such as a list that is sorted to include the most likely participants first) that the participant device 108 or user may select from. The invitees field 402 may be populated with the results. This population may happen automatically, or via using suggest button 416 to initiate processing of recommendations. In general, any field that may automatically be populated with context aware information may be populated locally, or via a query/response process with the intelligent assistant hub 110.
  • For example, if a user entered “Meet to go over new kosher foods available to be distributed by Goldman's groceries” in field 450, and/or entered “Kosher Foods Sales Pitch” as subject 404, the system may analyze this information to recommend invitees in field 402. The contact Herbert Goldman may be in the meeting requestor's contacts. Intelligent assistant hub 110 may have stored behaviors about Herbert Goldman indicating that he is Jewish and runs a grocery store. Based on the subject matter text entered, the intelligent assistant hub 110 may search all of the contacts' stored behaviors for one that may match (as described in FIG. 3) the subject matter received. Based on this search, Herbert Goldman may be a contact that has a matched stored behavior based on his Jewish identify and/or grocery store. Once this information is transmitted back to the participant device 108, the user may select Herbert Goldman from a list of recommended contacts (or have it automatically populate the field without user interaction in other embodiments, for example, by meeting a likeliness threshold). In this way, the user may be alerted of possible participants to invite to a meeting that would not have otherwise been invited, but that may be valuable participants in the meeting.
  • Context aware information may also be used to populate the location in a meeting request. For example, like the invitees populated in invitees field 402, a location may be automatically populated in location field 406 or suggested (via suggestion button 418), based on context data known to the system. For example, using a similar process as described for invitees, the system may collect context aware information such as from the user, meeting subject 404, text data 450, invitees 402, and/or other relevant data, and determine one or more suitable locations for the particular meeting. For example, based on Herbert's past restaurant selections (and/or the requestor), it may be determined that Herbert Goldman (and/or the requestor) prefers bagels or deli sandwiches. Other factors may be used in determining a recommended location as described herein, such as opening/closing times, type of food, location, other preferences of the attendees, etc. Multiple locations may also be recommended, and/or ranked. For example, cursor 420 is located over (“mouseover”) the location header. In popup box 422, multiple locations are described as recommendations, each with a match percentage that may rank how closely aligned each location is with user preferences or context constraints. In one embodiment, the user can select a location in the popup box 422.
  • The time selected for the meeting may also be automatically suggested or informed by context aware information. For example, meeting request 400 contains suggested times for the meeting which may be based on analysis of both the participants' schedules, as well as other contextual information about the participants. For example, suggested time 408 does not list any suggested times on Friday because the system is aware that Herbert Goldman may not work on Fridays for religious purposes. Similarly, the Yom Kippur holiday may prevent any suggested times on certain dates. Suggested times 410 and 412 may be identified by the system as times that likely work for participants based on past observed meeting times or other observed data. For example, based on Herbert Goldman's potentially Jewish heritage, culture and/or religion, a suggested time 410 for Saturday may be after sunset. Suggested times may be highlighted, sorted, or otherwise distinguished from one another based on various factors such as times that are most convenient for the requester, times that are most convenient for the other participant(s), or some other factors.
  • In another example, the smart meeting may automatically make a reservation for the selected meeting location (“venue”). In this example, the Make Reservation button 426 may be selected by the user (or automatically performed in other embodiments or configurations) to make a reservation for the selected venue. The reservation may be made with contextual knowledge, such as the preference of users. For example, button 424 may be used to suggest certain tables for the reservation based on known restaurant seat maps and explicit or implicit observed preferences for temperatures (e.g., inside/outside tables), noise, etc.
  • In some embodiments, data may not be available in the form required for use by the intelligent assistant hub 110. For example, the temperature in a restaurant may not be available to the system. The system may pull images, video, audio, and text from various feeds such as Facebook™ and Twitter™, and/or from image search engines such as that provided by Google™. Such searches would, in one implementation, be limited to images bearing metadata indicating they were taken in the location at issue; to data that references the location at issue; or to posts or data meeting other search criteria. A data range or other limitations, such as matching a time of day or time of year, may also be implemented. The images and/or other data may then be analyzed to infer data in the form required for the system to analyze, to obtain direct data that the system or its users require, or to confirm the validity of extent data within the system. For example, if there were a meeting at “Joe's Steakhouse”, the system might examine images recently taken within Joe's Steakhouse and observe that diners close to the kitchen and along the wall opposite the door were 50% more likely to remove their sweaters or coats than were visitors proximate to the door or windows. Similarly, the system might observe that drinks with ice were more likely to see that ice melt quickly at tables close to the kitchen, and that diners close to the kitchen were more likely to order cold drinks. Such information may be correlated to infer that the area near the kitchen is warmer than the area near the door and such information may be used by the system to guide reservations, to recommend table placement requests, or for other reasons. In one implementation, the system analyzes the data to identify individuals similar in weight, height, age, body type, gender, place of residence, or other factors and determines how the similar cohort is dealing with the venue. If, for example, a potential dinner meeting participant with a body mass index (BMI) of 45 were considering multiple venues, it would be informative to know among people with a similar BMI in images taken at the potential venues, the amount of sweating was lowest at venue A.
  • Additional data that the system may analyze would include public records related to the potential venue. For example, building permits issued for locations at or near the venue may indicate potential disruption or noise near the venue. Business licenses, restaurant health inspections, critical reviews, reviews by laypeople, and other similar data related to the potential venue or places enroute to the potential venue (including conveyances) may all be used by the system.
  • Example Document Processing
  • In another aspect, referring to FIG. 5, photographs, purchasing records, videos, and other data about other participants in a potential meeting or event (or in some cases those associated with participants) may be analyzed to determine appropriate clothing or other factors. Such data may be correlated with a database about the user of the system, with data provided by the user of the system, or a combination thereof. In one example, Jill is going to attend a networking event. The system has some data about Jill's available clothing, and Jill takes a photograph of the potential clothes she is considering wearing to the event. The system then analyzes the available data, such as images, of other participants and determines whether any of them wore identical or substantially identical clothes. In so doing, the system may then provide Jill with an analysis of the likelihood that she will show up at the event and find somebody else wearing the same outfit. Similar analysis may be done for other things.
  • In one implementation, as depicted in a flowchart of one embodiment in FIG. 5, analysis of photographs, purchasing records, and other data may be utilized to determine whether a potential recipient of a gift already has something identical or similar to the potential gift; whether the potential recipient has a possession that can be used to identify a complimentary gift (such as shoes that match a certain outfit, or a game that works with a particular gaming system), and/or the preferences of the potential recipient. In one example, a business associate's child may have been photographed playing with various toy trains, but no photograph showed the hot new toy train, “Example Train”. In such a case, the system may identify “Example Train” as a potential gift. In addition, such a system may be utilized to pre-populate, add to, or otherwise enhance gift registries or similar lists. For example, using existing photographic data or photographs taken for that purpose, a couple may photograph their kitchen utensils, pots, and pans and the system would then identify the existing things in the kitchen, evaluate which of those items have aged, are of poor quality, or otherwise would be good candidates for replacements, and identify desirable items that are not present in the data set. Such items may then be added to the data set, presented to the user for approval prior to addition, or noted within the dataset as automatically generated.
  • FIG. 5 illustrates one possible embodiment of analyzing image context information in order to assist in selecting a gift (or determine Jill's clothes to wear). For example, in 500, a participant's device 108 is used to take a picture of a train engine that may be used as a desired gift (or a piece of clothing that may possibly be worn, etc.). The photo, along with the target criteria 501 may be transmitted to the intelligent assistant hub 110. The target criteria may contain the specific query from the user (or automatically generated by the device), such as data indicating a question about the likelihood of whether a particular train engine is owned by a toddler, or whether there is a significant chance that a user will show up at a party with the same outfit. A mobile device application may be configured to respond to a particular query, such as whether a social network friend owns a particular product, such that separate applications are usable to response to other queries. Alternatively, an application may include multiple queries that are selectable by the user and/or are parsed from natural language text provided by the user (whether typed or orally received). The query may include any configured question that may be determined based on multimedia information accessible to the intelligent assistant hub 110.
  • In block 502, the intelligent assistant hub 110 may then analyze relevant social media images, or other multimedia items, based on the target criteria. For example, if the target criteria indicated a gift for a particular individual, then that individual's images may be analyzed to determine whether that individual may or may not already own the gift. In another example, if the target criteria is based on whether anyone else at a social event will wear the same clothing as the clothing in the picture, the requestor's social friend's images may be searched for corresponding clothing.
  • In block 504, the results of the search are determined. This may include determining what the likelihood of a match is based on image matching heuristics or other models. The results (text results, or in some embodiments matching images), may then be transmitted back to participant's device 108 for display. The display may indicate the likelihood of an event occurring or not occurring, or a confidence level in the query result.
  • Other Multimedia Examples
  • Images, video data, and other data regarding events that are not yet readily available in the expected databases may be used to supplement the data available to the system, such as to determine stored behaviors and/or to determine observed behaviors that the system attempts to match to one or more stored behaviors. For example, a photograph with metadata indicating it is 8 hours old and showing a “street closed for street fair all weekend” sign may be used to supplement road closure data available from Garmin™.
  • Images, video and other data may also be utilized to identify people who are associated with each other, organizations, or activities (face recognition technology may be utilized among other things). Similarly, expected clothing and appearance elements, such as the presence and type of facial hair, whether all women at a certain location wear burkas, common clothing and head coverings, etc., may be utilized by the system to identify suitable participants and/or to provide information or guidance to participants.
  • Indeed, video and audio data may additionally be utilized to determine whether potential participants have accents, speak a certain language or dialect thereof, speak slowly or quickly, speak softly or loudly, etc. Similarly, venues may be identified as having good or bad acoustics and having loud or quiet ambient sound (including music or televisions). Such information may be used by the system to identify and/or prepare participants. For example, a person with slight hearing loss meeting with a person with an accent and who speaks softly may be advised to avoid certain venues with high levels of ambient noise. The system may also compare these factors and determine whether assistive devices and/or translators will be required, and if so, what type of devices or translators.
  • Additional information may be gathered from various data sources and incorporated into the system. For example, how people similar to meeting participants (body type, cultural background, educational background), or the meeting participants themselves, normally sit or participate at meetings. In one example, somebody who fidgets may be preferentially seated near the end of a table, while a person who typically speaks softly but contributes significantly to the process during meetings may be seated toward the center of a table. Cultural analysis may also be done as to how to arrange seating (for example, a person with the habit of crossing their legs in a manner that shows the bottom of their foot to the person on their right may be seated at a place where there is too little room to cross their legs should the meeting also include a participant (or likely include a participant) from a culture where showing the bottom of a foot is considered an insult. Actual table shape, or the expected table shape for a specified location, may be incorporated as an additional factor.
  • The system may also utilize various data sources, including real time traffic data, 30 models, data from drones, helicopters and other sources. For example, a sensor mounted on a drone may show poor air quality up to 1,000 in the Los Angeles basin. In such a case, a meeting set for downtown may be moved to a venue in the hills above the 1,000 foot line.
  • Similarly, as another data source, activity on a social networking system may be used as indicia of when a user is utilizing a computer (as may availability on an instant messaging program or when a user sends or receives emails). Such cues (e.g. potential observed behaviors, which may be matched to stored behaviors) may be utilized to determine when a message should be sent via email or when it is unlikely to be read by email so should be sent via another mode, such as SMS. Similarly, cues in the messages (such as email headers or notes in an email such as “sent from a mobile device” and other potential observed behaviors, which may be matched to stored behaviors) may be used to determine when email is likely to be read on a device other than a traditional computer (and optionally, what kind of device and device characteristics). Such information may be used to alter communication patterns with such user.
  • It should be noted that gathered information or cues, such as observed behaviors or potential observed behaviors, may be used automatically to determine information to be presented as soon as possible (e.g., in realtime) to a user, such as information that may be used in formulating messaging or meeting strategy or identifying undesired behaviors during a meeting, etc. In some embodiments, information to be presented to a user is formulated only when a proposed action or behavior appears to conflict with gathered information or cues, or according to other formulations.
  • In one embodiment, the system may be integrated into one or more social networking systems, may itself comprise one or more social networking systems, may incorporate data from one or more social networking systems, or any combination thereof.
  • In one aspect, an automated analysis may be made to determine and/or predict scheduling availability, schedule patterns, travel patterns, or other useful patterns. Among other data points, the system may analyze internet or network activity, email or meeting activity, indicia of real world activity (such as posts by a person or others describing a person's real world activity and/or schedules), and/or data gathered from real world sensors (for example, metadata contained in photographs may be utilized to determine where a person was at a given time and place; though it should be noted that metadata is defined herein to include the data itself where useful information may be gleaned from it such as may be obtained with facial recognition, identifying the person and/or others and/or objects and/or places in the photograph may be identified even if not identified in textual metadata). This analysis of a person's activity may be used for various purposes, including determination of appropriate advice, guidance, or programmatic activity with regard to scheduling and other communications.
  • The method may further include a communication to the user about the factors that were used to determine meeting or communication parameters. Such information may be useful to the user in determining additional factors, such as the content or nature of the meeting or communication. Such information may further be combined with additional information relevant to the meeting or communication.
  • When planning any interaction (whether in person, via live telecommunication, via message, or by other means) it may be useful to determine what the likelihood is that a person will show up and/or respond, and if so, what to expect in terms of timeliness. For example, the system may analyze available data to determine the likelihood that a meeting will be cancelled or that one or more participants will not show up. Similarly, it may score the likelihood that an email will be replied to, and if so, the type of reply (length, cursory, or otherwise) and the delay to expect before a reply.
  • In addition, the system may provide timing windows based on predictions, past performance, and/or cultural factors. If, for example, it is unacceptable to be more than 5 minutes late for a meeting in a particular culture, when scheduling such a meeting, the system may provide additional warnings prior to the meeting or may schedule the meeting at an earlier time. In addition, the system may utilize mobile devices and/or interaction with fixed location devices to determine if the user is at risk of missing a meeting. For example, if a user has a meeting in downtown Los Angeles at 4:00 p.m., the system may determine that the user is at risk if the user is sitting at a computer located in Santa Monica at 3:00 p.m. (location may be determined with geo-ip, GPS, or other mechanisms). Similarly, if the user is in Santa Monica at 3:00 p.m. but is in motion (such as if a user's cellular device GPS indicates the user is heading eastbound on the 10 freeway), the user may not receive a warning unless the user becomes at risk for being late (such as by exiting the freeway and heading toward the beach). In one aspect, the system may automatically (or according to a rule set) notify one or more participants (which may be limited to participants on the “same team” or meeting other criteria) that the user is likely to be late. The system may analyze cultural and/or situational needs to determine where notification is desirable.
  • In addition, the system may take into account extrinsic information, such as historic or extent traffic conditions, in making determinations. When scheduling events or at other times, the system may warn if events are set with insufficient time to transition between events. Such warning may be triggered by a change to extrinsic information, such as a change to traffic conditions. Where there are cultural and/or situational preferences or norms with regard to early or late arrival, the system may identify a time window and warn the user (or a third party) if the user risks arriving outside of that window. The system may additional utilize GPS data, such as by warning a user who has arrived at the destination that they are more than 10 minutes early, which falls outside of the 5 minute window for early arrival.
  • Example Outcome Predictions
  • It may also be desirable for the system to predict probabilities for particular outcomes. For example, as depicted in FIG. 7 according to one embodiment, based on the traffic conditions described above, predictions may be made based on a user's movements or locations. These predictions may appear as notifications in a user application, such as the one depicted in FIG. 7. This may comprise a mobile application (such as an app on an iPhone). Notification data may be sent from intelligent assistant hub 110 that is tracking traffic conditions and participant movement. Based on these factors, the notification data may indicate to a participant that a user is early or late, and suggest changes in calendaring as a result. For example, app screen 702 describes a user Ted as being predicted to be late to a meeting. The notification also presents an option to a participant to alter their behavior, such as by leaving 10 minutes later. Various user interface buttons may be presented to the easier to act on this information. For example, activating button 704 may confirm to the calendaring system and/or other users that the participant is still planning on arriving on time despite Ted being late. Activating button 706, on the other hand, may indicate to the system that the participant is altering their schedule based on Ted's delay.
  • For example, a meeting between Hamas representatives and Israeli citizens may be ranked as likely to be unsuccessful unless dealing in one or more particular areas where there has been past success. In one aspect, available data may be utilized to set up a probabilistic model, or any model described above, and/or simulations may then be run to determine the likely range of outcomes.
  • Example Consideration of Cultural Factors
  • Further, cultural factors are frequently overlooked in preparing for a meeting, in determining the appropriate content of a meeting or communication, in conduct within a meeting, in tone or other affect within a communication or meeting, or in other interactions. Similarly, cultural and other factors may significantly impact the ability of a person to arrive at a meeting in a timely manner and ready to work.
  • For example, cultures differ in expectations about personal space and proximity. In some cultures, standing too close to another person is viewed as rude, while in others it is viewed as proper. Standards for dress and appearance vary from culture to culture. Gifts and other tokens of greeting or appreciation may be interpreted very differently from culture to culture—such as where a person presents a rose when the particular flower is considered bad luck in that culture. The appropriateness of incorporating other activities into meetings, such as meals, varies significantly from culture to culture.
  • Indeed, in certain cultures there is an expectation that one participant will engage in activities that are illegal or highly inappropriate in the nation of another participant. In one example, a company from a country where women are not expected to be vested with decision-making authority may seek to hire a law firm in the United States, where such discrimination based on gender is illegal. Similarly, a businessman from one country may find his hosts from another country insulted when he refuses to socialize at a strip club. Indeed, even within a single nation, regional or religious differences may result in profound misunderstandings, such as where a Mormon businesswoman is invited to a business dinner with a heavy focus on alcohol.
  • Further, cultural attitudes toward working relationships may be analyzed or utilized. For example, a New Zealand company working with two allies, one from the United States and the other from Japan, would benefit from understanding that statistically, Americans are more likely to prefer a more individualistic working relationship, while Japanese are more likely to prefer a more collectivist working relationship. In one implementation, the system may take or give weight to such preferences in managing communications or meetings. Gender, religious, cultural, and national differences in such areas may be considered.
  • Where such factors are known to exist, the system would alter meeting parameters and communications content appropriately, and/or would warn the user that it has detected a potential conflict or a cultural, personal, or other nature. Where such factors are not known, the system described herein may make probabilistic assessments as to the likelihood that they exist. For example, a person with a history of travel to Israel and with a significant number of friends who keep kosher may be scored as likely to require kosher food.
  • Example Notification
  • Individual circumstances may make a meeting or characteristic of a meeting very uncomfortable for a participant. In one example, a vegetarian may find an invitation to dinner at a steakhouse uncomfortable. Similarly, a recovering alcoholic may have difficulty with an invitation to finalize negotiations over drinks. In FIG. 8, a user interface for receiving a warning is presented that may be used to inform the user of important information based on the context of a meeting or message. For example, as discussed above a vegetarian may find an invitation to dinner at a steakhouse uncomfortable. The system may present to the user such a warning automatically. In user interface 802, the system may present options for handling the warning. For example, the user interface may present button 804 that, if activated, may allow the user to suggest a new restaurant for the meeting (manually, or automatically based on their context aware preferences). Alternatively, the warning may be ignored with button 806.
  • Example Information Sharing
  • In one implementation, multiple implementations of the system (or even with regard to different users within the same system) may make information available to trusted users. In such an implementation, User 1 may seek to set up a meeting with User 2. Optionally after seeking validation from User 2, or after checking to see if the users are “friends” or otherwise linked within a social network context, work for “pre-cleared” companies, or other factors, the system (or systems after an exchange of data) would utilize self-reported factors from each user to create an appropriate communication or meeting.
  • In one aspect, the system may craft meeting parameters by exchanging proposed meeting times, places, or other elements from one user to the other, and having the system automatically reject meetings with parameters that conflict with user preferences, cultural or otherwise. Such rejection may be accompanied by an invitation to suggest another time or other parameters, or by a suggestion of another time or other parameters. In addition, or alternatively, the system may initially pick a meeting time or parameter that complies with known facts and/or probabilistically likely facts about the other user.
  • In one aspect, the health and vaccination history of the user may be compared to the situation and risks in the place of the meeting (and in places visited in transit to the meeting), and alternate meeting places or times suggested. In addition, the system may provide a list of necessary health measures, such as shots or preventative pills or bringing antibiotics, that may be desirable. The system may also use the amount of medical preparation and risk as factors in weighting whether a place is appropriate for a meeting and/or in determining which of a plurality of locations and/or times is desirable.
  • Example Pre-Meeting Tips
  • Once a meeting has been set (or in conjunction with other communications or in conjunction with negotiating the meeting), the system may provide cultural and behavioral guidelines based on information about participants. For example, in preparation for a meeting with people from a nation where showing the bottom of a person's foot is considered an insult, such information may warn against doing so. In one implementation, the guidelines may be presented in order of importance or significance, and/or may include an explanation of such guideline and/or a score as to the relative significance of such guideline. Such guideline may, in one implementation, be presented as a “tips” application or sheet.
  • While the “tips” app or sheet may be presented electronically, on paper, or via any other mode of communication, and while the specific factors that are significant enough to include will vary based upon the needs of the individual and their industry, it may include some or all of the factors depicted in FIGS. 11A, 11B, and 11C. In one embodiment, such a sheet or “checklist” may aggregate all of the data needed for a meeting. In another, different lists may be provided for different portions of the meeting or different participants.
  • Example “Tips” Application
  • FIG. 9 illustrates one example of an electronic context aware tips mobile device user interface, according to one embodiment. Interface 900 may present, for example, context aware tips to be used before, during, and/or after a meeting. The Before Meeting button 910 may display tips relevant for before the meeting, such as items that require some time to perform prior to the meeting. Selecting During Meeting button 914 may display the tips for during the meeting, and Post Meeting button 912 may display tips for after the meeting. In some embodiments, buttons are not required and the appropriate tips are displayed automatically based on the system being aware of what stage the meeting is in (e.g., by using time to determine whether the meeting is schedule, active, or over).
  • The system may provide a wide variety of tips, including all of those listed in FIG. 11. In this example, cultural tips 902 are presented. For instance, in some cultures a gift or invitation must be refused prior to acceptance. This information may be determined to be relevant based on the context (e.g., based on participant tracking, it is known that participants frequently go out to dinner after a meeting), and may be displayed to the user in case any invitation is extended post meeting. Location or area based context aware tips may be provided 904.
  • Example Travel Tips and Information
  • In one embodiment, a database of global guidance and travel is accessed by a portable device. The device incorporates some or all of real-time data, such as weather and traffic conditions and exchange rates with other data (real-time or otherwise), such as expected behavior, food, legal, and safety information. In one implementation, the database is updated in realtime utilizing GPS or other geolocation mechanisms. In a further implementation, where guidance is unclear (such as guidance as to language spoken when travelling near the border between the United States and Mexico), the one or more recommendations are presented and/or the best recommendation is presented and/or such recommendations are accompanied by scoring data, which data may be presented numerically or graphically (such as by color or intensity of the text display). In another implementation, current location data may be incorporated with calendaring information to provide recommendations, such as where a person is in Los Angeles but scheduled to fly to New York, where the system may include both warm and cold clothing on such list. In one embodiment, the system relies only upon schedule data and/or manually input data. In one embodiment, the system obtains schedule data from other sources, such as social network posts and emails. In one embodiment, the data is displayed as an “app” on a mobile device, which “app” may serve as the entire system, or may send some or all of the data to another system for analysis or use. In one embodiment, the system may also present (either as a “pop-up” from a background application, on demand, or otherwise) information useful to the traveler based on highly local data. For example, as depicted in FIG. 6, a traveler newly arrived in an airport from an international destination may be presented with a pop-up alert saying “If you are on a Y fare or higher, you are eligible for free use of the lounge”, or an alert 602 noting “You are eligible for free wifi and lounge with your business class fare” along with options 604 to be given directions to the lounge if required.
  • In addition, where elite or other travel memberships or status provide access, the system may direct users to such access (for example, first class lines or elite travel program security clearance). Where cellular phones or other mobile devices are utilized as payment systems, the database may be consulted (or a default value used) to determine a culturally or otherwise appropriate transaction parameter, such as a tip amount. Such parameter may be used to determine when the user is making a possible error (for example, “you are tipping 20%; traditional tipping here is 5%”) and/or to directly input the data (for example, by automatically calculating the tip based on cultural expectations). Where individualized data (such as quality of service) as a factor in determining the parameter (such as a tip), the system may accept a rating (such as “rank the service from 1, excellent, to 5, terrible”) and calculate an appropriate tip based on consideration of the individualized data in light of localized data for such parameter.
  • The system may also track travel documentation and restrictions. For example, if a person may only travel where dialysis is available, an attempt to travel to a nation where his insurance will not be honored, or where no dialysis is available, may be rejected or may result in a warning. Similarly, notification of the need for travel documents, such as a visa, may be made. Where the system has data about the user's extent travel documents, the system may automatically determine if the travel documents are adequate (for example, warning if a travel document will expire prior to the travel date). In addition, the system may track, plan about, and/or warn about acceptable payment systems. For example, if the user has only a Visa card and a Cirrus network ATM card, and is about to travel into a nation with a low level of Visa card acceptance and no Cirrus network ATMs will be near his planned travel route or destination, the user may be warned. In another variant, the user may be notified when he passes or nears the last facility for using a particular payment system and is not expected to be near another one for a set period of time (i.e. if the last compatible ATM machine is in the airport and the user is about to take a cab into the city, where no additional compatible ATM machines are found). Data about the relative comfort of various travel modalities may also be incorporated, such as by using data about in-flight humidity, seat pitch, or similar factors. Such factors may be further weighted by user characteristics, such as by reducing the weight attached to seat pitch for a very short user.
  • Example Environmental Sensors and Notification Devices
  • In one embodiment, such guidelines may be programmed into a computing system coupled to one or more environmental data gathering devices, such as a camera or microphone. In one aspect, one or more users may be provided with a display or communication device coupled to such computing system. The display or communication device may, but need not, be physically attached or virtually attached (such as by Bluetooth) to the environmental data gathering devices, although for near-real time operation of this embodiment, some form of connection is preferable. The display or communication device, the environmental sensors, and the computing system may all be incorporated into a single device, connected through a network, connected through a local connection, wired or wireless, or otherwise set to communication with each other whether in real time or with stored data. In the near real time implementation, the environmental sensors feed data to the computing device, the data is analyzed to determine what cultural or other guidelines are being violated or complied with, or appear close to being violated or complied with, and the user provided with such feedback via the display or communication device. In one implementation, such data is provided in order of importance. In another, only data of a set level of significance or higher is provided. In another, the required level of significance may be changed by the user, or, when the system determines (such as by analysis of voice tone or body language) that the meetings is not proceeding as expected or that there is a likelihood that some disruptive event likely related to compliance with cultural or other norms has occurred or is occurring.
  • For example, according to one embodiment, as illustrated in FIG. 10, a warning system minimally perceptible to other meeting participants, such as a vibrating watch, may be used to inform the user that the system has detected an issue. Additional information may be made available by the same device or another display or communications device. In one embodiment, a hidden warning system that is minimally perceptible to other participants may be used where a number of specific behaviors are tied to a certain warning pattern, for example a single buzz indicating that the user is standing too close to another participant, a dual buzz to indicate that the user is showing the bottom of his foot, a triple buzz to indicate that the user is using an incorrect form of address, such as “Mr.” when the correct term is “Your Honor”, and a quadruple buzz to indicate some other issue has been detected. In one aspect, when another issue has been detected, additional information may be made available on a display system. The display system may include a heads-up display in eyeglasses, an audio display such as an earpiece, a Braille or similar tactile display, a display on a computer, phone or tablet device, or a coded display whether via one of those modalities or another modality. In one implementation, the display is polarized in a manner that obscures the message unless the user is wearing glasses capable or interacting with the polarized light in a set manner. In another implementation, the display is shown only when the environmental sensors show that other participants (or certain other participants) are not looking in a direction that would allow them to read the message. In another aspect, the system may provide real time translation. In one aspect, real time translation would be provided only for words, terms, or phrases more complex than a set grade level. In another aspect, translation may be provided only where the speaker talks in a manner more likely to be difficult to understand (such as where there is a heavy regional dialect). In another aspect, the system would track the alcohol intake of one or more participants (including the user), optionally considering actual or estimated weight of the participant, optionally considering the gender of the participant, optionally considering the estimated metabolization rate for each participant, and make available to one or more participants or other persons real time or non-real time data on likely blood alcohol level and level of impairment of the one or more participants. In one implementation a warning may be issued where the level exceeds a certain point. Additional data, such as nystagmus or lack of coordination, may also be noted, utilized, or incorporated.
  • Such a warning system (which is not restricted to a watch, but may be in the form of any hidden messaging), is illustrated in FIG. 10, according to one embodiment. In block 1002, the participant device 108 may receive environmental data using an environmental sensor. For example, data may be received by camera, thermometer, gyro sensor, light meter, microphone, etc. The data is then transmitted to the Intelligent Assistant Hub 110 for analysis (if not being processed locally). In blocks 1004 and 1006, the environmental data is analyzed according to FIG. 3, for example. If an observed behavior is detected, an alarm may be triggered in 1008. For example, if it is detected that the participant is standing too close to another person, that detected observed behavior (or a message to step away, etc.) may be transmitted to participant device 108.
  • In block 1010, the participant device 108 may code an alarm signal to be transmitted to the hidden messaging device. For example, a watch may be programmed to buzz based on Bluetooth signals received from a participant device 108 such as a mobile phone. The mobile phone would configure the Bluetooth (or other wireless protocol) transmission to instruct the watch to emit the correct number of buzzes, or any other type of hidden signal, that corresponds to the observed behavior/recommendation. In block 1012, when the watch receives the signal instruction, the signal will be expressed to the participant and understood by the user without notifying other parties. Similarly, the hidden message may be provided via other devices, such as smart glasses (e.g., Google Glass) in order to provide a textual description of the observed behavior to the user (e.g., “You're standing too close—move back one step)”.
  • Example Business Predictions
  • In another aspect, the system may gather data about companies involved in a proposed communication, meeting or transaction, and utilize that data. In one aspect, the system may analyze data, such as public records data, to determine the frequency with which persons bearing certain characteristics have or succeeded at (or failed to succeed at), rising within a company, dealing with a company, entering into a profitable arrangement within a company, or otherwise productively dealing with the company. The nature of meetings or communications leading to such outcomes (or failing to lead to such outcomes) may similarly be analyzed. It should be understood that such analysis may also be done for individuals or groups of individuals as well as for companies. Data that leads to indirect inferences (such as data about shareholders) may be utilized as well.
  • For example, an analysis of public records may show that ExampleCo, a Florida corporation, has a fifteen member Board of Directors, twelve from the Southern states and three from Nevada. In such a case, a corporation trying to do business with ExampleCo might preferentially select to make contact through an agent with a Southern background or, failing that, an agent from Nevada. By contrast, if all members of ExampleTwoCo's board were from Japan, it would be scored as unlikely that approaching that company other than through a local Japanese agent would be successful. In certain cases, the system may (upon request or automatically) suggest similarly situated companies with a profile that makes a deal more likely (such as a company with a Board that is more diverse, or more similar to the user's company's board or the user's characteristics).
  • For further example, consider that ExampleCo may be a publicly traded U.S. corporation. An analysis of SEC filings may indicate that of the last 100 times ExampleCo filed a Form 8-K, 40% involved a deal with a company in China, 20% involved deals with a company in the United States, and the remaining 40% related to scattered events, none of which involved European markets. In such a case, a Dutch company looking to market ExampleCo's products in Europe may have an opportunity, but communications would need to be filtered through the lens of ExampleCo's experience. The system would account for such a need, for example, by giving additional weight to conflicts between Chinese and U.S. customs, on the one hand, and Dutch customs, on the other. In such an example, while behaviors that are normally discouraged in the United States but acceptable in China may be scored as less important to avoid than would be behaviors that are normally discouraged in both nations—even if the meeting is taking place in the United States and with only U.S. participants. In this case, because ExampleCo's agents are inferred to be used to dealing with Chinese companies, an inference may be made that engaging in a behavior that is normal during Chinese business meetings is less likely to be troublesome for ExampleCo than it would be for a company within a similar level of experience in China. In one aspect, such a weighting system may be additionally refined by looking to the personal experiences of the proposed meeting participants.
  • In a further aspect, elements common to deals with a target entity may be identified by the system and meetings or communications shaped to recreate or emulate some or all such elements. For example, if 80% of all of ExampleCo's recent press releases about big deals contained the term “significant European presence”, it may be inferred that an approach to ExampleCo utilizing that term (or a similar term) may be preferable. In one implementation, similar terms may be automatically altered to make them more similar or even identical, such as by altering “big EU footprint” to “significant European footprint”. Such alterations may also be made as suggestions to the user, optionally with an explanation and/or weighting providing to the user. In addition to press releases, other communications by or about a target company or person may be used. Language that is common to documents, web pages, and/or communications written by such target may also be automatically inserted into communications (or such insertion suggested to the user). If, for example, ExampleCo frequently uses the term “disruptive to the industry”, communications containing analogous or somewhat analogous phrases, such as “industry altering” may be changed to “disruptive to the industry”. Such changes may be made only where such change would not cause the phrase to appear within a selected proximity of the same phrase in the same document.
  • In should be understood that among other things, when the system gathers data about individuals (or groups, cultures, and nations), such data may include: customs, race, religion, beliefs, values, assumptions, attitude, family, generations, history, disease, geography, age, creed, color, rituals, height, weight, leisure, disabilities, genetics, arts, sex, ecosystems, modality, size, birthrate, language, accent, dialect, strength, adaptability, and life expectancy. When the system considers communications, meetings, and physical environments for meetings, additional factors may include whether the meeting is to take place on land, water, or in flight; traffic data, both real time and predicted; time zones; plants, including whether allergens, particularly where a participant is known to have allergies; geology, seasons, currents, amount and timing of sunlight; phase of the moon; wildlife, temperature; disease and epidemics and similar factors. The system may also consider business practices; supply chain issues; manufacturing capacity and expertise; financial issues; healthcare infrastructure; tools, models; fashion; housing; patents and patent system; trademark and trademark system; copyright and copyright system; research and development; food, education, energy, and similar factors.
  • Other Example Data Sources and Predictions
  • Terrorist watch lists, lists of nations with which commerce is banned, and similar datasets would also be utilized in one implementation. For individuals or groups involved in certain industries, additional calendars or data may be checked. For example, a COO might be scored as less likely to be available just prior to the end of the fiscal year, a CPA might be scored as less likely to be available just prior to the end of the tax year, and an attorney's availability may be scored by checking court calendars for trial or hearing dates.
  • In another aspect, safety and security assessments may be utilized. In one implementation, generalized crime data may be utilized. In addition, or instead of, such generalized data, more sophisticated measures may be utilized, such as analyzing crime data by demographics (i.e. the number of people with similar demographics to the user who were victims), by date (for example, Mardi Gras may correspond to higher crime rates), by location, or by a combination thereof Alterations may be made or suggested to travel plans, and/or advice given as to how to behave and/or appear, that mitigates such risk. Furthermore, measures of national, regional, and/or ethnic discrimination or otherwise disparate treatment may be utilized. For example, a Sunni Muslim visitor to a Shiite Muslim area may trigger additional risk scoring and/or changes to travel recommendations. In one implementation, communications by email or other electronic means may automatically be altered to reflect a name and profile that are more likely to obtain good results, whether by avoiding bias or otherwise. For example, if a woman named “Jane Smith” is communicating with a party who is likely to discriminate against women, the system may automatically alter her communications to reflect the name “John Smith”. Another response may be for the system to create, either automatically, with human approval and/or input, or with a combination thereof, a fictitious additional persona for the user. Such persona may additionally minimize risk of discrimination, as by having “Jane Smith” automatically communicate via an artificial persona such as “John Washington”. Where communications include voice and/or video, automated (in one implementation, real-time) alterations to the voice and/or appearance and/or mannerisms, and/or accents of one or more participants may be made. Such alterations may be made to make the artificial persona appear to be the one communicating. Such alterations may also be made to influence the likelihood that the communications will be received in a particular manner or understood or accepted. For example, a telecommunications device may alter a Boston accent to sound like a mid-west accent where it is determined or believed that such a change may be advantageous.
  • The system may also determine the reputation of the people and companies represented at (or present at, or proposed to be present at) a meeting. In one aspect, public data such as internet data reporting “scams” by companies may be utilized. An appropriate warning may be issued. In addition, where there is a risk (such as a company whose public records show a high level of litigation over contracts), additional participants (such as legal counsel) may be added or recommended.
  • In one aspect, the system may identify additional participants or communications recipients (either automatically or upon request). For example, if a meeting is being conducted with ExampleCo about bringing widgets to Europe, and a common contact for both parties is Jane Smith who has written a book about widgets, the system may suggest (or automatically include) Jane Smith.
  • In one aspect, records of charitable, political, and other giving may be utilized to generate data about political or charitable interests or preferences for people.
  • In one aspect, the system may utilize the available data to generate a scoring of likelihood of conflict, success, or other outcomes. For example, if a meeting is being set up between a businessman who is associated with Hamas and a businessman who regularly donated money only to Jewish politicians, even in the absence of any specific factors standing in the way of a meeting, the system may score the meeting as unlikely to succeed and provide the user with such information. Similarly, if a meeting to discuss sales of printer paper was being set up between ExampleCo and a Joe Smith of ExampleTwoCo, and public records show that Joe Smith has given the maximum amount legally possible to every Republican presidential candidate for the past 5 election cycles, as between ExampleCo's two possible representatives at the meeting—representatives who are otherwise equally well suited to the meeting but who differ in political orientation—the system would recommend, assign, and/or attach additional weight to the representative who was Republican. The significance attached to political differences, differences in hobbies, and similar differences that are colloquially seen as more likely to influence a friendship than a business relationship, may be increased when the meeting is between people from cultures where socialization is an expected or important part of a business deal. In cultures where participants “get right down to business”, the weighting of political or similar disagreements, or lack of common interests, would be reduced.
  • Example Conference Call Improvements
  • Another aspect of the invention addresses several long felt needs in the field, including the ability to hold meetings at factories, shipyards, clubs, and other locations where there is a significant amount of noise, as well as the ability to hold meetings where participants are free to leave the immediate area, such as to inspect an item being discussed, without leaving the conversation. Existing conference call technology as well as blue tooth ear piece technology is well known, but falls short in this regard. There is an unsettling delay in between hearing a live voice and hearing the voice as transmitted over a conference call. Thus, it is not desirable to hold a meeting where participants all have earpieces connected via a conference call so that ambient noise can be overcome or so that participants can move around during the meeting. In one embodiment, the system provides a method of communication whereby a plurality of participants have equipment capable of receiving transmissions from other units, sending transmissions to other units, and determining whether the proximity of the transmitting unit is such that the user is able to hear the participant with the transmitting unit without receiving and playing that transmission for the participant with the receiving unit. For example, imagine that Abe, Belle, and Carl are having a meeting at a factory. Abe is known to have some hearing loss and has set his unit up to play sounds transmitted from other units when the ambient voice of the person wearing the other unit has more than a set likelihood of being incomprehensible to him (or he can actuate the unit manually). Belle walks ten yards away during a conversation. Abe's unit and Carl's unit detect her distance (whether by reading a GPS signal or location signal sent by the unit, reading the strength of the unit's signal, or measuring the sound and qualities of her voice, potentially in combination with measurement of ambient noise levels). Carl's unit determines that Carl can hear Belle without assistance, and does not re transmit what Belle is saying. Abe's unit determines that Abe needs assistance and plays what Belle is saying in Abe's ear. In a variation, the unit may record and/or retain and/or transcribe part or all of the conversation from one or more participants. In one use of such a variation, a participant may indicate to the unit that he or she did not understand what another participant said, in which case the unit may replay the sound for the user, may show a transcript of the sound, may alert the speaker of the problem, or may take similar measures.
  • Example Computing Systems
  • A number of computing systems have been described throughout this disclosure. The descriptions of these systems are not intended to limit the teachings or applicability of this disclosure. For example, the systems described herein (e.g., the participant devices, the intelligent assistant hub, data sources, etc.) can generally include any computing device(s), such as servers, desktops, laptops, video game platforms, television set-top boxes, televisions (e.g., interne TVs), computerized appliances, and wireless mobile devices (e.g. smart phones, PDAs, tablets, or the like), to name a few. Further, it is possible for the systems described herein to be different types of devices, to include different applications, or to otherwise be configured differently. In addition, the systems described herein can include any type of operating system (“OS”). For example, the mobile computing systems described herein can implement an Android™ OS, a Windows® OS, a Mac® OS, a Linux or Unix-based OS, or the like.
  • Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be communicate via a variety of methods, including electronic communications such as: computer networking on a local area network or a wide area network, a POTS network, a cellular network, or any wireless-based and wired/cable-based mediums that may include analog communications or digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.
  • The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
  • Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
  • Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
  • All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the system and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CO-ROMs, magnetic tape, flash drives, and optical data storage devices.
  • It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the systems and methods. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the systems and methods can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the systems and methods should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the systems and methods with which that terminology is associated.

Claims (20)

What is claimed is:
1. A computing device comprising one or more processors, a network interface, and a memory, the memory comprising instructions, that when executed by the one or more processors, cause the computing device to:
receive, via the network interface, a meeting request from a user device, the meeting request indicating one or more invitees;
access, from at least one server having one or more data repositories, social media data related to the one or more invitees, wherein the social media data comprises one or more stored images generated by an imaging sensor and stored by the one or more data repositories;
perform face recognition on the stored image(s) to identify at least one invitee;
determine, based on content of textual data in or associated with the stored image(s), at least one attribute of the at least one invitee;
determine, in near real time, the locations of a user of the user device and the one or more invitees from geolocation sensors on the user device and respective user devices associated with the one or more invitees;
identify at least one recommended meeting parameter based, at least in part, on the at least one attribute of the at least one invitee and the locations of the user and the respective invitees; and
transmit, via the network interface, the at least one meeting recommended parameter to the user device.
2. The computing device of claim 1, wherein the social media data comprises religious information, and the at least one attribute comprises a religious attribute.
3. The computing device of claim 2, wherein the at least one recommended meeting parameter comprises at least one recommended meeting time based, at least in part, on the religious attribute.
4. The computing device of claim 1, wherein the at least one recommended meeting parameter comprises venue information based on preferences of the one or more of the invitees identified in the social media data.
5. The computing device of claim 1, wherein the at least one recommended meeting parameter is further based on travel information for at least one of the one or more invitees.
6. The computing device of claim 1, wherein the social media data comprises cultural information, and the at least one attribute comprises a cultural attribute.
7. The computing device of claim 1, wherein the social media data comprises demographic information and the at least one attribute comprises demographic attribute.
8. A computing device comprising one or more processors, a network interface, and a memory, the memory comprising instructions, that when executed by the one or more processors, cause the computing device to:
receive, via the network interface, a meeting request from a user device, the meeting request indicating one or more invitees and comprising one or more requested meeting parameters;
access, from at least one server having one or more data repositories (i) social media data related to the one or more invitees, wherein the social media data comprises one or more stored images generated by an imaging sensor and stored by the one or more data repositories, and (ii) at least one non-schedule related preference for the at least one invitee;
perform face recognition on the stored image(s) to identify at least one invitee;
determine, based on content of textual data in or associated with the stored image(s), at least one attribute of the at least one invitee;
determine, in near real time, the locations of a user of the user device and the one or more invitees from geolocation sensors on the user device and respective user devices associated with the one or more invitees;
identify at least one recommended meeting parameter based, at least in part, on the at least one attribute, the non-schedule related preferences for the at least one invitee, and the locations of the user and the respective invitees; and
transmit, via the network interface, the at least one meeting recommended parameter to the user device.
9. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's financial information.
10. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's immunization history.
11. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's medical history.
12. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's travel schedule.
13. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on one or more environmental sensors on the at least one invitee's user device.
14. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's religion.
15. The computing device of claim 8, wherein the at least one non-schedule related preference is automatically generated based on the at least one invitee's demographics.
16. The computing device of claim 8, wherein the at least one non-schedule related preference comprises a dining location preference.
17. A computing device comprising one or more processors, a network interface, and a memory, the memory comprising instructions, that when executed by the one or more processors, cause the computing device to:
receive, via the network interface, a meeting request from a user device, the meeting request indicating one or more invitees;
access, from at least one server having one or more data repositories, social media data related to the one or more invitees, wherein the social media data comprises one or more stored images generated by an imaging sensor and stored by the one or more data repositories;
perform face recognition on the stored image(s) to identify at least one invitee;
determine, based on content of textual data in or associated with the stored image(s), one or more religious or cultural attributes of the at least one invitee;
determine, in near real time, the locations of a user of the user device and the one or more invitees from geolocation sensors on the user device and respective user devices associated with the one or more invitees; and
identify at least one recommended meeting parameter based, at least in part, on the at least one attribute of the at least one invitee and the locations of the user and the respective invitees; and
transmit, via the network interface, the at least one recommended meeting parameter to the user device.
18. The computing device of claim 17, wherein the social media data comprises religious information, and the one or more religious, or cultural attributes comprises religious attributes.
19. The computing device of claim 17, wherein the at least one recommended meeting parameter comprises venue information based on preferences identified in the accessed social media data of the one or more of the invitees.
20. The computing device of claim 17, wherein the at least one recommended meeting parameter is further based on travel information for at least one of the one or more invitees.
US15/694,649 2012-12-30 2017-09-01 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data Abandoned US20170372271A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US201261747348P true 2012-12-30 2012-12-30
US201361790249P true 2013-03-15 2013-03-15
US14/035,615 US9754243B2 (en) 2012-12-30 2013-09-24 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data
US15/694,649 US20170372271A1 (en) 2012-12-30 2017-09-01 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/694,649 US20170372271A1 (en) 2012-12-30 2017-09-01 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/035,615 Continuation US9754243B2 (en) 2012-12-30 2013-09-24 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data

Publications (1)

Publication Number Publication Date
US20170372271A1 true US20170372271A1 (en) 2017-12-28

Family

ID=51018209

Family Applications (5)

Application Number Title Priority Date Filing Date
US14/032,621 Active 2034-02-03 US9953304B2 (en) 2012-12-30 2013-09-20 Situational and global context aware calendar, communications, and relationship management
US14/035,615 Active US9754243B2 (en) 2012-12-30 2013-09-24 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data
US14/733,872 Abandoned US20150278730A1 (en) 2012-12-30 2015-06-08 Situational and global context aware calendar, communications, and relationship management
US15/694,649 Abandoned US20170372271A1 (en) 2012-12-30 2017-09-01 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data
US15/960,437 Abandoned US20180240078A1 (en) 2012-12-30 2018-04-23 Situational Global Context Aware Calendar, Communications and Relationship Management

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US14/032,621 Active 2034-02-03 US9953304B2 (en) 2012-12-30 2013-09-20 Situational and global context aware calendar, communications, and relationship management
US14/035,615 Active US9754243B2 (en) 2012-12-30 2013-09-24 Providing recommended meeting parameters based on religious or cultural attributes of meeting invitees obtained from social media data
US14/733,872 Abandoned US20150278730A1 (en) 2012-12-30 2015-06-08 Situational and global context aware calendar, communications, and relationship management

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/960,437 Abandoned US20180240078A1 (en) 2012-12-30 2018-04-23 Situational Global Context Aware Calendar, Communications and Relationship Management

Country Status (1)

Country Link
US (5) US9953304B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10223673B2 (en) * 2017-05-16 2019-03-05 International Business Machines Corporation Cognitive adaptation to user behavior for personalized automatic processing of events

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9276884B2 (en) * 2007-06-29 2016-03-01 Aquila Vision Corporation Intelligent notification system and method
US9116513B2 (en) * 2008-03-28 2015-08-25 Securitypoint Holdings, Inc. Methods and systems for efficient security screening
US20130246221A1 (en) * 2012-03-15 2013-09-19 Aptitude, Llc Method, apparatus, and computer program product for contract compliance monitoring and enforcement
US10032233B2 (en) * 2012-10-17 2018-07-24 Facebook, Inc. Social context in augmented reality
US9773231B2 (en) 2013-05-29 2017-09-26 Evernote Corporation Content associations and sharing for scheduled events
US20140372162A1 (en) * 2013-06-14 2014-12-18 Avaya Inc. System and method for smart contextual calendaring based meeting scheduling
US9525743B2 (en) * 2013-07-16 2016-12-20 Interactive Intelligence Group, Inc. System and method for predictive live interaction offering and hosting
US20150046367A1 (en) * 2013-08-06 2015-02-12 Evernote Corporation Gathering meeting-related information
US9390607B2 (en) * 2013-12-06 2016-07-12 International Business Machines Corporation Smart device safety mechanism
CN104767652A (en) * 2014-01-08 2015-07-08 杜比实验室特许公司 Method for monitoring performance of digit transmission environment and system for determining potential service quality
US20160036923A1 (en) * 2014-08-03 2016-02-04 Microsoft Corporation Efficient Migration of Application State Information
US20160086104A1 (en) * 2014-09-19 2016-03-24 Rita Hanna Wouhaybi Facilitating intelligent gathering of data and dynamic setting of event expectations for event invitees on computing devices
US20160092040A1 (en) * 2014-09-26 2016-03-31 Ebay Inc. Communication device with contact information inference
US9727201B2 (en) 2015-04-01 2017-08-08 Microsoft Technology Licensing, Llc Contextual help
US10104023B2 (en) * 2015-04-16 2018-10-16 Oath Inc. Location sharing
US9934475B2 (en) 2015-05-13 2018-04-03 Bank Of America Corporation Managing enterprise data movement using a heuristic data movement detection engine
US9513867B1 (en) 2015-06-19 2016-12-06 Honda Motor Co., Ltd. System and method for managing communications on a mobile communication device based upon a user's behavior
US9628419B2 (en) * 2015-07-29 2017-04-18 Mimecast North America, Inc. System for annotation of electronic messages with contextual information
US10438172B2 (en) * 2015-08-06 2019-10-08 Clari Inc. Automatic ranking and scoring of meetings and its attendees within an organization
US9684652B2 (en) 2015-08-10 2017-06-20 International Business Machines Corporation Multicultural communication management
US20170061385A1 (en) * 2015-08-24 2017-03-02 International Business Machines Corporation Efficiency of scheduling of a meeting time
US20170109707A1 (en) * 2015-10-19 2017-04-20 International Business Machines Corporation Productivity through automated work balancing
US20170139918A1 (en) * 2015-11-13 2017-05-18 Salesforce.Com, Inc. Managing importance ratings related to event records in a database system
US10176463B2 (en) * 2015-12-17 2019-01-08 International Business Machines Corporation Machine learning system for intelligently identifying suitable time slots in a user's electronic calendar
US10423931B2 (en) * 2015-12-31 2019-09-24 International Business Machines Corporation Dynamic processing for collaborative events
US9773419B1 (en) 2016-03-24 2017-09-26 International Business Machines Corporation Pre-positioning aerial drones
US10148546B2 (en) 2016-06-09 2018-12-04 Apple Inc. Scheduling processing tasks based on predicted context
US20190087468A1 (en) * 2017-09-15 2019-03-21 PAG Financial International LLC Status streaming pop-up map

Family Cites Families (90)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6064975A (en) * 1997-10-22 2000-05-16 Ericsson Inc. Apparatus and method for highlighting holidays of a specified location in a calendar software application
US6141005A (en) * 1998-09-10 2000-10-31 International Business Machines Corporation Combined display of locale-sensitive calendars in a distributed computer enterprise environment
EP1071055B1 (en) 1999-07-23 2004-12-22 Matsushita Electric Industrial Co., Ltd. Home monitoring system for health conditions
US6886000B1 (en) * 1999-09-29 2005-04-26 International Business Machines Corporation On-line negotiations with dynamic profiling
US6581037B1 (en) * 1999-11-05 2003-06-17 Michael Pak System and method for analyzing human behavior
US7716077B1 (en) * 1999-11-22 2010-05-11 Accenture Global Services Gmbh Scheduling and planning maintenance and service in a network-based supply chain environment
US6842737B1 (en) * 2000-07-19 2005-01-11 Ijet Travel Intelligence, Inc. Travel information method and associated system
WO2002023442A1 (en) * 2000-09-13 2002-03-21 Infospace, Inc. System and method for providing an advanced personal information manager
AU7640300A (en) * 2000-09-30 2002-04-15 Intel Corp Method, apparatus, and system for distributed meeting scheduling based on autonomous multi-agent
US20020099592A1 (en) * 2001-01-22 2002-07-25 Donahue John J. Method and apparatus for providing best practice reports for real estate transactions using a computer network
US6767211B2 (en) * 2001-03-13 2004-07-27 Carolyn W. Hall Method and apparatus for behaviorally reinforced training with guided practice
US20030061087A1 (en) * 2002-07-15 2003-03-27 Paul Srimuang Calendar scheduling of multiple persons resources and consumables with group access view restriction
US8165640B2 (en) * 2003-03-14 2012-04-24 Jeffrey D Mullen Systems and methods for providing remote incoming call notification for cellular phones
US20120179981A1 (en) * 2011-01-07 2012-07-12 Meetup, Inc. Collaboration Meeting Management in a Web-Based Interactive Meeting Facility
US8359206B2 (en) * 2003-06-16 2013-01-22 Meetup, Inc. Web based interactive meeting facility
US7552393B2 (en) * 2003-08-14 2009-06-23 The Hayes-Roth Family Trust Hook-up assistant
US20050075096A1 (en) * 2003-10-03 2005-04-07 Aljuraid Nassir Abdulrahman GSM phone applet and method for controlling prayer timings
US8538768B2 (en) * 2005-02-16 2013-09-17 Ingenio Llc Methods and apparatuses for delivery of advice to mobile/wireless devices
US7716140B1 (en) * 2004-12-31 2010-05-11 Google Inc. Methods and systems for controlling access to relationship information in a social network
US20060212330A1 (en) * 2005-03-16 2006-09-21 Erkki Savilampi Network based processing of calendar meeting requests
US8374888B2 (en) * 2005-10-28 2013-02-12 Ace Ideas, Llc Behavior monitoring and reinforcement system and method
US20070106725A1 (en) * 2005-11-08 2007-05-10 Robert Starr Methods, systems, and computer program products for providing a scheduler for multiple parties
US8209181B2 (en) * 2006-02-14 2012-06-26 Microsoft Corporation Personal audio-video recorder for live meetings
US20060122903A1 (en) * 2006-02-25 2006-06-08 Medrano Guillermo A Cross-Cultural and Personality Support System and Method
US20070226034A1 (en) 2006-03-23 2007-09-27 Kyocera Wireless Corp. Wireless communication device meeting scheduler
WO2007117606A2 (en) * 2006-04-07 2007-10-18 Pelago, Inc. Proximity-based user interaction
WO2007140321A2 (en) * 2006-05-26 2007-12-06 Mix & Meet, Inc. System and method for scheduling meetings and user interface
US20140040371A1 (en) * 2009-12-01 2014-02-06 Topsy Labs, Inc. Systems and methods for identifying geographic locations of social media content collected over social networks
US8276081B2 (en) * 2006-09-02 2012-09-25 John Edward Boyd Computer-based methods for arranging meetings and systems for performing the same
US7707256B2 (en) * 2006-11-14 2010-04-27 Microsoft Corporation Suggesting meeting locations for conducting meetings
US20080153474A1 (en) 2006-12-22 2008-06-26 Research In Motion Limited Time and/or time-zone indicator for contacts
US8269834B2 (en) * 2007-01-12 2012-09-18 International Business Machines Corporation Warning a user about adverse behaviors of others within an environment based on a 3D captured image stream
US7895246B2 (en) * 2007-05-31 2011-02-22 Microsoft Corporation Collection bin for data management and transformation
US8243116B2 (en) * 2007-09-24 2012-08-14 Fuji Xerox Co., Ltd. Method and system for modifying non-verbal behavior for social appropriateness in video conferencing and other computer mediated communications
US8209310B1 (en) * 2007-09-26 2012-06-26 Empire Consulting, Inc. System and method of matching professionals for networking meetings
US20090100037A1 (en) * 2007-10-15 2009-04-16 Yahoo! Inc. Suggestive meeting points based on location of multiple users
US8990269B2 (en) * 2007-11-28 2015-03-24 International Business Machines Corporation Intelligent client cache mashup for the traveler
US20090150222A1 (en) * 2007-12-10 2009-06-11 Alexander Polonsky Method for increasing the accuracy of social network profiles
US8078677B2 (en) * 2008-03-11 2011-12-13 Voxp Pte. Ltd. Method for making recommendations in a social networking system based on personal communication information and a social networking system incorporating same
US7836140B2 (en) * 2008-06-02 2010-11-16 International Business Machines Corporation Team-based task invitations
US20100057562A1 (en) 2008-09-03 2010-03-04 Ronen Gabbay System and method for mobile match mapping
US20100076951A1 (en) * 2008-09-11 2010-03-25 International Business Machines Corporation Service for negotiating a meeting location given multiple user preferences and locations using social networking
US8560371B2 (en) * 2008-09-26 2013-10-15 Microsoft Corporation Suggesting things to do during time slots in a schedule
US8626552B2 (en) * 2009-03-26 2014-01-07 International Business Machines Corporation Quorum management of appointment scheduling
US20100274855A1 (en) * 2009-04-22 2010-10-28 Sony Ericsson Mobile Communications Ab Scheduling events with location management
US8150718B2 (en) * 2009-05-13 2012-04-03 Hugh Olliphant System and method for automatically scheduling appointments
US8407177B2 (en) * 2009-06-22 2013-03-26 Integrated Training Solutions, Inc. System and associated method for determining and applying sociocultural characteristics
US8620710B2 (en) * 2009-07-02 2013-12-31 International Business Machines Corporation Managing calendar events while preparing for time out-of-office
US8533175B2 (en) * 2009-08-13 2013-09-10 Gilbert Marquard ROSWELL Temporal and geographic presentation and navigation of linked cultural, artistic, and historic content
US8823527B2 (en) * 2009-09-03 2014-09-02 Koninklijke Philips N.V. Consciousness monitoring
US8639756B2 (en) * 2010-02-19 2014-01-28 Nokia Corporation Method and apparatus for generating a relevant social graph
WO2011106364A2 (en) * 2010-02-23 2011-09-01 Farmacia Electronica, Inc. Method and system for consumer-specific communication based on cultural normalization techniques
EP2549753B1 (en) * 2010-03-15 2019-04-10 Omron Corporation Surveillance camera terminal
US8468144B2 (en) * 2010-03-19 2013-06-18 Honeywell International Inc. Methods and apparatus for analyzing information to identify entities of significance
US8963987B2 (en) * 2010-05-27 2015-02-24 Microsoft Corporation Non-linguistic signal detection and feedback
US8670018B2 (en) * 2010-05-27 2014-03-11 Microsoft Corporation Detecting reactions and providing feedback to an interaction
US9292565B2 (en) * 2010-06-30 2016-03-22 International Business Machines Corporation Template-based recognition of food product information
KR101722687B1 (en) * 2010-08-10 2017-04-04 삼성전자주식회사 Method for providing information between objects or object and user, user device, and storage medium thereof
JP5559335B2 (en) * 2010-08-31 2014-07-23 オムロン株式会社 Behavior analysis device
US20130031475A1 (en) * 2010-10-18 2013-01-31 Scene 53 Inc. Social network based virtual assembly places
US8244277B1 (en) * 2011-02-16 2012-08-14 Sprint Communications Company L.P. Device experience adaptation based on schedules and events
US8667062B2 (en) * 2011-02-22 2014-03-04 Nokia Corporation Method and apparatus for preserving privacy for appointment scheduling
CN102739837A (en) 2011-04-02 2012-10-17 奇美通讯股份有限公司 Method and system for managing time zone of contact person
US8676937B2 (en) * 2011-05-12 2014-03-18 Jeffrey Alan Rapaport Social-topical adaptive networking (STAN) system allowing for group based contextual transaction offers and acceptances and hot topic watchdogging
US20120303415A1 (en) * 2011-05-25 2012-11-29 Ari Edelson System and method of providing recommendations
US20130024391A1 (en) * 2011-06-09 2013-01-24 Tripadvisor Llc Social travel recommendations
US20120316911A1 (en) * 2011-06-09 2012-12-13 Jacob Patrick Schwarz Smart scheduling system
US8783566B1 (en) * 2011-06-14 2014-07-22 Norman J. Drew Electronic registration kiosk for managing individual healthcare information and services
US20150193819A1 (en) * 2011-06-21 2015-07-09 Google Inc. Targeting Content to Meeting Location
US9781540B2 (en) * 2011-07-07 2017-10-03 Qualcomm Incorporated Application relevance determination based on social context
US8832301B2 (en) * 2011-07-21 2014-09-09 Parlant Technology System and method for enhanced event participation
US8743171B2 (en) * 2011-08-10 2014-06-03 Polycom, Inc. Automated calendared conference rescheduling and forwarding
JP5879877B2 (en) * 2011-09-28 2016-03-08 沖電気工業株式会社 Image processing apparatus, image processing method, program, and image processing system
US20130144672A1 (en) * 2011-12-05 2013-06-06 International Business Machines Corporation Analytics-Based Community Value Meetings
CN103957777B (en) * 2011-12-07 2018-01-09 捷通国际有限公司 Behavior tracking and update the system
JP5785869B2 (en) * 2011-12-22 2015-09-30 株式会社日立製作所 Behavior attribute analysis program and apparatus
AU2013217184A1 (en) * 2012-02-02 2014-08-21 Tata Consultancy Services Limited A system and method for identifying and analyzing personal context of a user
US8533266B2 (en) * 2012-02-14 2013-09-10 Google Inc. User presence detection and event discovery
US20130246116A1 (en) * 2012-03-16 2013-09-19 International Business Machines Corporation Assisting user to schedule a meeting with the best candidate from a list of individuals based on past communication history, calendar information and user's rules
US20130246526A1 (en) * 2012-03-18 2013-09-19 Nam Wu Consensus and preference event scheduling
US9692795B2 (en) * 2012-04-18 2017-06-27 Qualcomm Incorporated Dynamic group and event update method in phone based impromptu meet-up app
US9299027B2 (en) * 2012-05-07 2016-03-29 Runaway 20, Inc. System and method for providing intelligent location information
US20140006518A1 (en) * 2012-06-27 2014-01-02 Everote Corporation Instant meetings with calendar free scheduling
US20140049389A1 (en) * 2012-08-16 2014-02-20 Weezee Llc Devices for Facilitating Administration of a Personalized Sensory Experience and Systems and Methods Using Same
US20140058768A1 (en) * 2012-08-21 2014-02-27 Google Inc. System and method for trip planning suggestions
US20140081693A1 (en) * 2012-09-18 2014-03-20 International Business Machines Corporation System and method configured to automatically invite participants to a meeting based on relation to meeting materials
US20140129505A1 (en) * 2012-11-08 2014-05-08 Microsoft Corporation Social event recommendation system
US20140143352A1 (en) * 2012-11-20 2014-05-22 Linkedln Corporation User profile and geography-based meetings
CN105074742A (en) * 2012-12-30 2015-11-18 加里·斯蒂芬·舒斯特 Global contact synchronization
US20140278455A1 (en) * 2013-03-14 2014-09-18 Microsoft Corporation Providing Feedback Pertaining to Communication Style

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10223673B2 (en) * 2017-05-16 2019-03-05 International Business Machines Corporation Cognitive adaptation to user behavior for personalized automatic processing of events

Also Published As

Publication number Publication date
US20140189016A1 (en) 2014-07-03
US20150278730A1 (en) 2015-10-01
US9754243B2 (en) 2017-09-05
US20180240078A1 (en) 2018-08-23
US20140188541A1 (en) 2014-07-03
US9953304B2 (en) 2018-04-24

Similar Documents

Publication Publication Date Title
Kanter et al. The networked nonprofit: Connecting with social media to drive change
Gummesson Exit services marketing-enter service marketing
Gregg Work's intimacy
Heath et al. Human communication theory and research: Concepts, contexts, and challenges
US9622055B2 (en) System and method for managing mobile communications
US10102539B2 (en) Verification of redemption of an electronic offer
US8874679B2 (en) Location-based communications
US8019692B2 (en) System and method for location based social networking
US20140344386A1 (en) System and method for conditional delivery of messages
US9264462B2 (en) System and method for confirming attendance for in-person meetings or events
US20110238755A1 (en) Proximity-based social networking
US20140280292A1 (en) Refining a search based on schedule items
US8560515B2 (en) Automatic generation of markers based on social interaction
US20100205541A1 (en) social network driven indexing system for instantly clustering people with concurrent focus on same topic into on-topic chat rooms and/or for generating on-topic search results tailored to user preferences regarding topic
US20090177745A1 (en) System and method for delivery of augmented messages
US9117220B2 (en) Web-based interactive meeting facility with revenue generation through sponsorship
US20140052485A1 (en) System and method for on-line event promotion and group planning
US8904295B2 (en) Web-based interactive meeting facility with recommendations to users
CN105164663B (en) The system and method for accessing controllable interaction
US9501573B2 (en) Electronic personal companion
US20180032997A1 (en) System, method, and computer program product for determining whether to prompt an action by a platform in connection with a mobile device
US9654425B2 (en) System and method for communicating among members of meeting groups
US20080098313A1 (en) System and method for developing and managing group social networks
US20130282421A1 (en) System and method for enhanced event participation
Lee et al. To personalize or depersonalize? When and how politicians' personalized tweets affect the public's reactions

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION