US20070266318A1 - Managing interactions between computer users' context models - Google Patents

Managing interactions between computer users' context models Download PDF

Info

Publication number
US20070266318A1
US20070266318A1 US11622954 US62295407A US2007266318A1 US 20070266318 A1 US20070266318 A1 US 20070266318A1 US 11622954 US11622954 US 11622954 US 62295407 A US62295407 A US 62295407A US 2007266318 A1 US2007266318 A1 US 2007266318A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
attribute
step
information
value
continues
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
US11622954
Inventor
Kenneth Abbott
Dan Newell
James Robarts
Joshua Freedman
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.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/033Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
    • G06F3/038Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 – G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/163Wearable computers, e.g. on a belt
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30017Multimedia data retrieval; Retrieval of more than one type of audiovisual media
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/011Arrangements for interaction with the human body, e.g. for user immersion in virtual reality
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/016Input arrangements with force or tactile feedback as computer generated output to the user
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06NCOMPUTER SYSTEMS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N99/00Subject matter not provided for in other groups of this subclass
    • G06N99/005Learning machines, i.e. computer in which a programme is changed according to experience gained by the machine itself during a complete run
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149Restricted operating environment
    • GPHYSICS
    • G09EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09GARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2358/00Arrangements for display data security
    • GPHYSICS
    • G09EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09GARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2360/00Aspects of the architecture of display systems
    • G09G2360/12Frame memory handling
    • G09G2360/121Frame memory handling using a cache memory
    • GPHYSICS
    • G09EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09GARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2370/00Aspects of data communication
    • G09G2370/02Networking aspects
    • G09G2370/022Centralised management of display operation, e.g. in a server instead of locally
    • GPHYSICS
    • G09EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09GARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2370/00Aspects of data communication
    • G09G2370/04Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller
    • G09G2370/042Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller for monitor identification
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99943Generating database or data structure, e.g. via user interface

Abstract

Techniques are described for providing information about a current state that is represented with multiple attributes. In some situations, the providing includes a first computer receiving indications of multiple characterization modules, each characterization module executing on a computer to model an aspect of a current state related to that computer; receiving an indication of one of the multiple attributes of the represented current state; determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute; and gathering information about the modeled aspects related to the indicated one attribute from the determined characterization modules so that a value for the indicated one attribute can be generated based on the gathered information.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • [0001]
    This application is a continuation-in-part of U.S. patent application Ser. No. 09/216,193, entitled “METHOD AND SYSTEM FOR CONTROLLING PRESENTATION OF INFORMATION TO A USER BASED ON THE USER'S CONDITION” and filed Dec. 18, 1998, and a continuation-in-part of U.S. patent application Ser. No. 09/464,659, entitled “STORING AND RECALLING INFORMATION TO AUGMENT HUMAN MEMORIES” and filed Dec. 15, 1999. Both of these applications are hereby incorporated by reference in their entirety.
  • [0002]
    This application also claims the benefit of provisional U.S. Patent Application No. 60/194,004 (Attorney Docket No. 294438020US), entitled “MANAGING INTERACTIONS BETWEEN COMPUTER USERS' CONTEXT MODELS” and filed Apr. 2, 2000, and of provisional U.S. Patent Application No. 60/193,999 (Attorney Docket No. 294438008US entitled “OBTAINING AND USING CONTEXTUAL DATA FOR SELECTED TASKS OR SCENARIOS, SUCH AS FOR A WEARABLE PERSONAL COMPUTER” and filed Apr. 2, 2000. These applications are both hereby incorporated by reference in their entirety.
  • TECHNICAL FIELD
  • [0003]
    The following disclosure relates generally to computer-based modeling of information, and more particularly to modeling and exchanging context data, such as for a wearable personal computer.
  • BACKGROUND
  • [0004]
    Computer systems increasingly have access to a profusion of input information. For example, a computer may be able to receive instructions and other input from a user via a variety of input devices, such as a keyboard, various pointing devices, or an audio microphone. A computer may also be able to receive information about its surroundings using a variety of sensors, such as temperature sensors. In addition, computers can also receive information and communicate with other devices using various types of network connections and communication schemes (e.g., wire-based, infrared or radio communication).
  • [0005]
    Wearable personal computers (or “wearables”) can have even greater access to current input information. Wearables are devices that commonly serve as electronic companions and intelligent assistants to their users, and are typically strapped to their users' bodies or carried by their user in a holster. Like other computers, wearables may have access to a wide variety of input devices. Moreover, in addition to more conventional input devices, a wearable may have a variety of other input devices such as chording keyboards or a digitizer tablet. Similarly, a wearable computer may have access to a wide variety of sensors, such as barometric pressure sensors, global positioning system devices, or a heart rate monitor for determining the heart rate of its user. Wearables also may have access to a wide variety of non-conventional output devices, such as display eyeglasses and tactile output devices.
  • [0006]
    Many applications executing on computers utilize data received by the computer from sensors or other input sources. For example, a position mapping application for a wearable computer may utilize data received from a global positioning system device in order to plot its user's physical location and to determine whether that position is within a specified region. In this example, the global positioning system device produces data that is consumed by the position mapping application.
  • [0007]
    In conventional wearable computer systems, the position mapping application would be designed to interact directly with the global positioning system device sensor to obtain the needed data. For example, the application may be required to instruct the device to obtain position information, retrieve the information obtained by the device, convert it to conventional latitude and longitude representation, and determine whether the represented location is within the special region.
  • [0008]
    The need for such direct interaction between applications and sensors in order to obtain and process data has several significant disadvantages. First, developing an application to interact directly with a particular sensor can introduce sensor-specific dependencies into the application. Accordingly, the application may need to be subsequently modified to be able to interact successfully with alternatives to that sensor provided by other manufacturers, or even to interact successfully with future versions of the same sensor. Alternately, the sensor could be developed to explicitly support a particular type of application (e.g., via a device driver provided with the sensor), which would analogously introduce application-specific dependencies into the sensor.
  • [0009]
    Second, direct interaction between the application and the sensor can give rise to conflicts between multiple applications that consume the same data. For example, if the position mapping application was executing on the same wearable computer as a second application for determining the user's distance from home, and the second application also used the global positioning system device, the two applications' interactions with the device could interfere with one another.
  • [0010]
    Third, direct interaction between the application and the sensor can give rise to conflicts between multiple sensors that produce the same data. For example, if the position mapping application was executing on a wearable computer that had access to both the global positioning system device and an indoor positioning system, the application might well have trouble determining which device to use to determine the user's current position, and/or have trouble reconciling data produced by both devices.
  • [0011]
    Fourth, rather than an application having to directly process observable data from the sensors and derive more abstract information itself, it would be advantageous for the application to be able to rely on a separate programmatic entity that derives such abstract information and provides it to the application. For example, it would be more convenient for the position mapping application to be able rely on a separate programmatic entity that determines the user's location, and to then use that information to determine whether the user is in a special region.
  • [0012]
    Accordingly, a facility for exchanging information between sensors and applications in a wearable computer system would have significant utility.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0013]
    FIG. 1 illustrates an embodiment of the characterization module executing on a general-purpose body-mounted wearable computer.
  • [0014]
    FIG. 2 is a block diagram illustrating an embodiment of the characterization module executing on an exemplary computer system.
  • [0015]
    FIG. 3 is a data flow diagram showing a sample exchange of attributes performed by the characterization module.
  • [0016]
    FIG. 4 is a data structure diagram showing an example context server table used to maintain a portion of the state of the characterization module.
  • [0017]
    FIG. 5 is a data structure diagram showing an example attribute instance table used to maintain a portion of the state of the characterization module.
  • [0018]
    FIG. 6 is a data structure diagram showing an example context client table used to maintain a portion of the state of the characterization module.
  • [0019]
    FIG. 7 is a data structure diagram showing updated contents of the attribute instance table.
  • [0020]
    FIG. 8 is a flow diagram of an embodiment of the GetAttribute function.
  • [0021]
    FIG. 9 is a data structure diagram showing updated contents of the attribute instance table.
  • [0022]
    FIG. 10 is a data structure diagram showing an example condition table that contains a portion of the state of the characterization module.
  • [0023]
    FIG. 11 is a data structure diagram showing an example condition monitor table that maintains a portion of the state of the characterization module.
  • [0024]
    FIG. 12 is a data structure diagram showing updated contents of the condition monitor table.
  • [0025]
    FIG. 13 is a data flow diagram showing the operation of the facility without a characterization module.
  • [0026]
    FIG. 14 is a data structure diagram showing an example attribute request table used to maintain a portion of the state of the characterization module.
  • [0027]
    FIG. 15 illustrates an example of a plain-language, hierarchical, taxonometric attribute nomenclature.
  • [0028]
    FIG. 16 illustrates an example of an alternate hierarchical taxonomy related to context.
  • [0029]
    FIG. 17 is a flow diagram of an embodiment of the Characterization Module routine.
  • [0030]
    FIG. 18 is a flow diagram of an embodiment of the Notification Processing subroutine.
  • [0031]
    FIG. 19 is a flow diagram of an embodiment of the Dynamically Specify Available Clients, Servers, and Attributes subroutine.
  • [0032]
    FIG. 20 is a flow diagram of an embodiment of the Process Distributed Characterization Module Message subroutine.
  • [0033]
    FIG. 21 is a flow diagram of an embodiment of the Process Attribute Value Or Value Request Message subroutine.
  • [0034]
    FIG. 22 is a flow diagram of an embodiment of the Process Received Attribute Value subroutine.
  • [0035]
    FIG. 23 is a flow diagram of an embodiment of the Process Additional Information About Received Value subroutine.
  • [0036]
    FIG. 24 is a flow diagram of an embodiment of the Mediate Available Values subroutine.
  • [0037]
    FIG. 25 is a flow diagram of an embodiment of the Pull Attribute Value From Server subroutine.
  • [0038]
    FIG. 26 is a flow diagram of an embodiment of the Push Attribute Value To Client subroutine.
  • [0039]
    FIG. 27 is a flow diagram of an embodiment of the Context Client routine.
  • [0040]
    FIG. 28 is a flow diagram of an embodiment of the Context Server routine.
  • DETAILED DESCRIPTION
  • [0041]
    A software facility is described below that exchanges information between sources of context data and consumers of context data. In particular, in a preferred embodiment, a characterization module operating in a wearable computer system receives context information from one or more context servers (or “suppliers”), and provides that information to one or more context clients (or “consumers”). This context information represents a particular context (or “state” or “condition”) of the wearable, the user of the wearable, the surrounding physical environment and/or the available electronic data environment (or “cyber-environment”). In some embodiments the context is represented (or “modeled”) with a variety of attributes (or “variables”) each modeling a single aspect of the context. By facilitating the exchange of context information, the facility reduces dependencies of context client applications on specific sensors and other input sources, resolves conflicts between context client applications that consume the same context data, resolves conflicts between multiple sensors or other input sources that produce the same data, and isolates the generation of derived attributes from context client applications.
  • [0042]
    A context is modeled or represented with multiple attributes that each correspond to a specific element of the context (e.g., ambient temperature, location or a current user activity), and the value of an attribute represents a specific measure of that element. Thus, for example, for an attribute that represents the temperature of the surrounding air, an 80° Fahrenheit value represents a specific measurement of that temperature. Each attribute preferably has the following properties: a name, a value, an uncertainty level, units, and a timestamp. Thus, for example, the name of the air temperature attribute may be “ambient-temperature,” its units may be degrees Fahrenheit, and its value at a particular time may by 80. Associated with the current value may be a timestamp of Feb. 27, 1999 13:07 PST that indicates when the value was generated, and an uncertainty level of +/−1 degrees.
  • [0043]
    Context servers supply values for attributes by receiving and processing input information from sensors or other sources. Attribute values provided by a context server may either be “measured” (or “observed”) in that they are directly received from an input source, or may instead be “derived” in that they are the result of performing processing on one or more measured attribute values. Indeed, a derived attribute value may be produced by performing additional processing on one or more other derived attribute values. Context attributes (or “condition variables”) are discussed in greater detail in both U.S. patent application Ser. No. 09/216,193, filed Dec. 18, 1998 and entitled “METHOD AND SYSTEM FOR CONTROLLING PRESENTATION OF INFORMATION TO A USER BASED ON THE USER'S CONDITION”, and provisional U.S. Patent Application No. 60/193,999 (Attorney Docket # 29443.8008), filed Apr. 2, 2000 and entitled “OBTAINING AND USING CONTEXTUAL DATA FOR SELECTED TASKS OR SCENARIOS, SUCH AS FOR A WEARABLE PERSONAL COMPUTER,” which are both hereby incorporated by reference.
  • [0044]
    When the characterization module obtains an attribute value from a context server, it caches the value for use when responding to future requests from context clients for a value of the attribute. Thus, when the characterization module receives a request from a context client for the value of an attribute, the characterization module determines whether it has a cached value for the attribute and, if so, whether the value is sufficiently accurate (e.g., the value does not have too high of an uncertainty) and/or sufficiently recent (e.g., the value is not too old). If the value is not sufficiently accurate or recent, the characterization module requests and receives an updated value for the attribute from the context server that supplied the value. When the characterization module has a sufficiently accurate and recent value, it supplies the value to the context client. The determination of whether a value is sufficiently accurate and recent can be made in a variety of ways, such as by using thresholds for recency or uncertainty that can be specified by the context client during the request, by a context server for all values of an attribute or for a specific attribute value, or by the characterization module.
  • [0045]
    In some embodiments, two or more different context servers may supply to the characterization module their own distinct values for a single attribute. For example, a first context server can supply a value for a user.location attribute based on data received from a global positioning system device, while a second context server can supply a value for the user.location attribute based on data received from an indoor positioning device. Alternately, the first and second context servers could use the same input information when determining the value for a single attribute, but could use different methods to perform the determining and could thus arrive at different values. When multiple content servers supply values for the same attribute, each of the context servers is said to supply values for a separate “instance” of the attribute. The characterization module preferably provides a variety of different approaches, called “mediators,” for determining what attribute value to provide when a context client requests a value for an attribute that has more than one instance.
  • [0046]
    For attributes with multiple instances, the characterization module performs similar processing to that described above. In particular, the characterization module can maintain a unique cached value for each attribute instance. If the characterization module receives a request for a value of a particular attribute instance, the request is handled as discussed above. If the characterization module instead receives a attribute value request for an attribute with multiple instances and the request does not specify a particular instance, the characterization module checks the accuracy of each cached attribute instance and requests an updated value for any instance with a value that is not sufficiently accurate. If multiple sufficiently accurate values are available, the characterization module produces a mediated value that is returned to the context client. The mediator to be used for the mediation can be selected in a variety of ways, such as being a default mediator of the characterization module, being requested by a context client, being specified by one or more of the context servers, or being chosen by the characterization module.
  • [0047]
    The manner in which data (e.g., sensor data and attribute values) flows to and from the characterization module can vary. In some embodiments, a context client may receive an attribute value only after an explicit request, while in other embodiments a context client may be forwarded attribute values without a request (e.g., if the client had previously expressed an interest in receiving values for the attribute and a value has just become available). Similarly, in some embodiments context servers may supply attribute values only when requested, while in other embodiments the context servers may supply attribute values without a request (e.g., if sensor input information is received from which a new value is produced). Request-based processing is a type of “pull” data flow model, and some forms of processing that occur without explicit requests are referred to as a “push” or “event-driven” data flow model.
  • [0048]
    The manner in which the characterization module communicates with the context clients and context servers can also vary. In some embodiments, context servers and context clients perform various interactions with the characterization module (e.g., supplying attribute values and requests) by calling functions provided by the characterization module (e.g., via Component Object Module interfaces). These functions are said to collectively comprise an “application programming interface” (or “API”) to the characterization module. In alternate embodiments, such interactions can be performed using other mechanisms, such as passing messages or objects. Those skilled in the art will appreciate that an API can be created to support a pull data model, a push data model, or a hybrid system including both push and pull functionality.
  • [0049]
    As one example of an API, each executing context server may register with the characterization module by calling a RegisterContextServer function and supplying parameters to identify itself If a particular context server is not executing, a context client that desires a value of an attribute or attribute instance supplied by the context server may cause the context server to be launched by using a LaunchContextServer function. After registration, a context server may indicate an ability to supply values for an attribute to the characterization module by using a CreateAttributeInstance function. A particular context server can provide values for a number of different attributes by calling the CreateAttributeInstance function multiple times. In order to consume values of an attribute, a context client may call a RegisterContextClient function in order to identify itself and one or more attributes whose values it seeks to consume. To assist in selecting one or more attributes, a context client may also call a EnumerateAttributes function to obtain a list of the attributes available from the characterization module. In order to actually retrieve an attribute value, a context client may call a GetAttribute function and use parameters to identify the attribute and any attribute processing that should be applied, such as a specific mediator to be used if values are available for multiple instances of the attribute. For attributes that have multiple instances in the characterization module, a context client may also call a GetAllAttributeInstances function to obtain a value for each instance of the attribute. To force a particular context server to reevaluate all of its attribute instances, a context client may call a CompleteContextServerEvaluation function. Also, to retrieve values for attributes that model aspects of the configuration of the characterization module, a context client or other program may call a GetCharacterizationModuleAttribute function. A context client that consumes a particular attribute value may also create a condition in the characterization module (not to be confused with the current modeled condition of the user or the environment that is represented by various attribute values) for testing that attribute by calling a CreateCondition function. Once a context client has created a condition, it can evaluate the condition by calling an EvaluateCondition function using parameters to identify the condition, and may also proceed to create a condition monitor that monitors the condition and notifies the context server when the condition is satisfied by calling a CreateConditionMonitor function. To suspend operation of a created condition monitor, a context server may call a StopConditionMonitor function, and to resume its operation, may call a StartConditionMonitor function. The context server may remove a condition monitor that it created by calling a RemoveConditionMonitor function and, correspondingly, may remove a condition that it created by calling a RemoveCondition function. A context client may unregister with the characterization module by calling an UnregisterContextClient function. A context server may similarly remove attribute instances that it has registered by calling a RemoveAttributeInstance function. Before it does, however, it may first call a CheckAttributeInstanceDependencies function to determine whether any context clients currently depend upon that attribute instance. A context server may unregister with the characterization module by calling an UnregisterContextServer function. A set of API functions are discussed in greater detail in both U.S. patent application Ser. No. 09/541,328, filed Apr. 2, 2000 and entitled “INTERFACE FOR EXCHANGING CONTEXT DATA,” and provisional U.S. Patent Application No. 60/194,123, filed Apr. 2, 2000 and entitled “SUPPLYING AND CONSUMING USER CONTEXT DATA,” which are both hereby incorporated by reference.
  • [0050]
    In some embodiments, it may also be useful to store attribute value information in a more permanent fashion than a temporary cache. For example, it may be useful for the characterization module to keep a log of all attribute values received and sent, or of all interactions with context clients and context servers. Alternately, it may be useful to record the current values of some or all of the attributes and attribute instances at the same time, such as to capture a complete model of the current context. Storing attribute value information is discussed in greater detail in both U.S. patent application Ser. No. 09/464,659, filed Dec. 15, 1999 and entitled “STORING AND RECALLING INFORMATION TO AUGMENT HUMAN MEMORIES”, and U.S. patent application Ser. No. 09/541,326, filed Apr. 2, 2000 and entitled “LOGGING AND ANALYZING COMPUTER USER'S DATA,” which are both hereby incorporated by reference. Other uses of attribute value information are described in provisional U.S. Patent Application No. 60/194,000, filed Apr. 2, 2000 and entitled “SOLICITING PRODUCT INFORMATION BASED ON THE USER'S CONTEXT,” in provisional U.S. Patent Application No. 60/194,002, filed Apr. 2, 2000 and entitled “AUTOMATED SELECTION OF UNSOLICITED INFORMATION BASED ON A USER'S CONTEXT,” and in provisional U.S. Patent Application No. 60/194,758, filed Apr. 2, 2000 and entitled “CREATING PORTALS BASED ON THE USER'S CONTEXT,” each of which are hereby incorporated by reference.
  • [0051]
    FIG. 1 illustrates an embodiment of the characterization module which executes on a general-purpose body-mounted wearable computer 120 worn by user 110. Many wearable computers are designed to act as constant companions and intelligent assistants to a user, and are often strapped to a user's body or mounted in a holster. The computer system may also be incorporated in the user's clothing, be implanted in the user, follow the user, or otherwise remain in the user's presence. In one preferred embodiment the user is human, but in additional preferred embodiments, the user may be an animal, a robot, a car, a bus, or another entity whose context is to be modeled. Indeed, the computer system may have no identifiable user, but rather operate as an independent probe, modeling and/or reporting on the context in an arbitrary location.
  • [0052]
    The wearable computer 120 has a variety of user-worn user input devices including a microphone 124, a hand-held flat panel display 130 with character recognition capabilities, and various other user input devices 122. Similarly, the computer has a variety of user-worn output devices that include the hand-held flat panel display, an earpiece speaker 132, an eyeglass-mounted display 134, and a tactile display 136. In addition to the various user-worn user input devices, the computer can also receive information from various user sensor input devices 116 and from environment sensor input devices 128, including video camera 121. The characterization module can receive and process the various input information received by the computer, either directly or from context servers that process the input information and generate attribute values, and can supply the received information to context clients or directly to the user by presenting the information on the various output devices accessible to the computer.
  • [0053]
    In the current environment, computer 120 is accessible to a computer 150 (e.g., by being in line-of-sight wireless proximity or by being reachable via a long-distance communication device such as a cellular phone) which also has a variety of input and output devices. In the illustrated embodiment the computer 150 is non-portable, although the body-mounted computer of the user can similarly communicate with a variety of other types of computers, including body-mounted computers of other users. The devices from which the non-portable computer can directly receive information include various user input devices 152 and various user sensor input devices 156. The non-portable computer can output information directly to a display 160, a speaker 162, an olfactory device 164, and a printer 166. In the illustrated embodiment, the body-mounted computer can communicate with the non-portable computer via a wireless transmission medium. In this manner, the characterization module can receive information from the user input devices 152 and the user sensor devices 156 after the information has been transmitted to the non-portable computer and then to the body-mounted computer. Alternately, the body-mounted computer may be able to directly communicate with the user input devices 152 and the user sensor devices 156, as well as with other various remote environment sensor input devices 158, without the intervention of the non-portable computer 150. Similarly, the body-mounted computer may be able to supply output information to the display 160, the speaker 162, the olfactory device 164, and the printer 166, either directly or via the non-portable computer, and directly to the telephone 168. As the user moves out of range of the remote input and output devices, attribute values of the characterization module can be updated to reflect that the remote devices are not currently available.
  • [0054]
    Information that is received from the various input devices allows the characterization module or an application such as a context server (not shown) executing on the computer 120 to monitor the user and the environment, and to maintain a model (not shown) of the current context. In some embodiments, the model may be represented in a single location (e.g., the current cached values of all of the context attributes and attribute instances), while in other embodiments the model may be distributed. Such a model can be used by various applications, such as context clients, for a variety of purposes. A model of the current context can include a variety of context attributes that represent information about the user, the computer, and the user's environment at varying levels of abstraction. For example, information about the user at a low level of abstraction can include raw physiological data (e.g., heart rate and EKG) and geographic information (e.g., location and speed), while higher levels of abstraction may attempt to characterize or predict the user's physical activity (e.g., jogging or talking on a phone), emotional state (e.g., angry or puzzled), desired output behavior for different types of information (e.g., to present private family information so that it is perceivable only to myself and my family members), and cognitive load (i.e., the amount of attention required for the user's current activities). Background information which changes rarely or not at all can also be included, such as the user's age, gender and visual acuity. The model can similarly hold environment information at a low level of abstraction, such as air temperature or raw data from a motion sensor, or at higher levels of abstraction, such as the number and identities of nearby people, objects, user mood, and locations. The model of the current context can include information added explicitly from other sources (e.g., application programs), as well as user-specified or system-learned defaults and preference information.
  • [0055]
    Those skilled in the art will appreciate that computer systems 120 and 150. as well as their various input and output devices, are merely illustrative and are not intended to limit the scope of the present invention. The computer systems may contain additional components or may lack some illustrated components. For example, the characterization module could be implemented on the non-portable computer, with the body-mounted computer replaced by a thin computer client such as a transmitter/receiver for relaying information between the body-mounted input and output devices and the non-portable computer. Alternately, the user may not wear any devices or computers.
  • [0056]
    In addition, the body-mounted computer may be connected to one or more networks of other devices through wired or wireless communication means (e.g., wireless RF, a cellular phone or modem, infrared, physical cable, a docking station, etc.), either with or without support from other computers such as the computer 150. For example, the body-mounted computer of a user can make use of output devices in a smart room, such as a television and stereo when the user is at home, if the body-mounted computer is able to transmit information to those devices via a wireless medium or if a cabled or docking mechanism is available. Alternately, kiosks or other information devices can be installed at various locations (e.g., in airports or at tourist spots) to transmit relevant information to body-mounted computers within the range of the information device. Those skilled in the art will also appreciate that specialized versions of the body-mounted computer, characterization module, context clients and/or context servers can be created for a variety of purposes.
  • [0057]
    FIG. 2 illustrates an exemplary computer system 200 on which an embodiment of the characterization module is executing. The computer includes a memory 230, a CPU 210, a persistent storage device 250 such as a hard drive, and input/output devices including a microphone 222, a video camera 223, a computer-readable media drive 224 (e.g., a CD-ROM drive), a visual display 225, a speaker 226, and other devices 228. The memory preferably includes the characterization module 231, as well as information reflecting the current state of the characterization module (characterization module state) 232. The memory further contains software modules 233. 234, and 237 that consume attribute values and are therefore context clients, and software modules 235, 236, and 237 which provide attribute values and are therefore context servers. While items 231-237 are preferably stored in memory while being used, those skilled in the art will appreciate that these items, or portions of them, can be transferred between memory and the persistent storage device for purposes of memory management and data integrity. Alternately, in other embodiments some or all of the software modules may execute in memory on another device, and communicate with the characterization module via inter-computer communication.
  • [0058]
    In addition, in some embodiments a pre-defined set of attributes are available for use by context servers and context clients. This allows a common meaning to be shared between context clients and context servers as to those attributes and their values, and can also allow a context client to request a pre-defined attribute without having to determine whether the attribute has been created by a context server supplying values for the attribute. In one embodiment a plain-language, hierarchical, taxonometric attribute nomenclature is used to name attributes, such as the example attribute nomenclature illustrated in FIG. 15. The names within the nomenclature are preferably specific so that there is no ambiguity as to what they represent, and the ability to extend the nomenclature by adding new attribute names that conform to the hierarchical taxonomy of the nomenclature is preferably supported. The nomenclature preferably has attribute names relating to a variety of aspects of the user.
  • [0059]
    For example, as is illustrated in FIG. 15, the nomenclature preferably has a variety of types of attribute names, including: attribute names relating to the user's location, such as user.location.latitude, user.location.building, and user.location.street; attribute names relating to the user's movement, such as user.speed and user.direction; attribute names for various user moods, such as user.mood.happiness, user.mood.anger, and user.mood.confusion; attribute names for user activities, such as user.activity.driving, user.activity.eating, and user.activity.sleeping; attribute names for user physiology values, such as user.physiology.body_temperature and user.physiology.blood_pressure; attribute names for similar attributes of people other than the user, such as person.John_Smith.mood.happiness; attribute names for aspects of the computer system or “platform,” such as for aspects of the platform's user interface (“UI”) capabilities (e.g., platform.UI.oral_input_device_availability and platform.UI.visual_output_device_availability) and central processing unit (“CPU”) (e.g., platform.cpu.load and platform.cpu.speed); attribute names for aspects of the local environment, such as environment.local.temperature and environment.local.ambient_noise_level; attribute names for remote environments, such as environment.place.chicago.time and environment.place.san_diego.temperature; attribute names relating to a future context, such as those that predict or estimate a situation (e.g., environment.local.next_week.temperature); attribute names relating to specific applications, such as an email application (e.g., application.mail.available, application.mail.new_messages_waiting, and application.mail.messages_waiting_to_be_sent); etc. In this manner, the attribute nomenclature used by the facility provides effective names for attributes relating to the user, the computer system, and the environment. Additional attributes are illustrated in FIG. 15, and FIG. 16 illustrates an alternate hierarchical taxonomy related to context, such that various attributes could be added for each of the illustrated categories. Those skilled in the art will appreciate that for both FIG. 15 and FIG. 16, other categories and attributes could be added and existing categories and attributes could be removed or could have alternate names.
  • [0060]
    FIG. 3 is a data flow diagram showing a sample exchange of attributes performed by the characterization module. The diagram shows characterization module 300, as well as five other software modules, 310, 320, 330, 340, and 350. Software modules 310, 320, and 330 are said to be context servers, in that they provide attribute values to the characterization module. For example, context server 330 provides values for a user.in_region attribute 331. It can be seen that context servers may provide values for more than one attribute. For example, context server 320 provides values for a user.location attribute 321 and an user.elevation attribute 322. It can further be seen that values for a single attribute may be provided by more than one context server. For example, context server 310 provides values for user.location attribute 311, while context server 320 provides values for user.location attribute 321. Attributes 311 and 321 will be represented by the characterization module as multiple instances of a single user.location attribute. The characterization module preferably provides functionality for mediating between these two separate instances when the value of the user.location attribute is requested by a context client.
  • [0061]
    Software modules 330, 340, and 350 are said to be context clients because they consume attribute values. For example, context client 340 consumes user.location attribute 341 values. It can be seen that certain software modules may act both as a context server and as a context client. For example, software module 330 is both a context server and a context client, as it provides values for the user.in_region attribute 331 and consumes values for user.location attribute 332. It can also be seen that a context client can consume values for more than one attribute. For example, context client 350 consumes values for both user.in_region attribute 351 and user.elevation attribute 352. To determine which attributes are currently available, any of the context clients may request that the characterization module enumerate the available attributes. In response to such a request, the characterization module would enumerate the user.location attribute, the user.elevation attribute, and the user.in_region attribute.
  • [0062]
    FIG. 4 is a data structure diagram showing an example context server table used to maintain a portion of the state of the characterization module. Each row of the table corresponds to a registered context server. Each row contains a context server name field 411 containing the name of the context server, a version field 412 identifying the version of the context server, an installation date 413 identifying the date on which the context server was installed on the computer system, a filename 414 identifying a primary file in the file system representing the context server, and a request handler field 415 containing a reference to a request handler function on the context server that may be called by the characterization module to send messages to the context server (e.g., a request evaluation of one or all of the attributes provided by the context server). Other versions of the context server table may lack some of the illustrated fields (e.g., the version field), or may contain additional fields (e.g., a registered attributes field that contains the names of all of the attributes for which the context server is currently registered to supply values).
  • [0063]
    FIG. 5 is a data structure diagram showing an example attribute instance table used to maintain a portion of the state of the characterization module. The attribute instance table contains a row for each attribute or attribute instance for which a context server is currently registered to supply values. Each of these rows contains the following fields: an attribute name field 511 containing the name of the attribute, a context server name field 512 identifying the context server that created the attribute instance, a value field 513 containing the value of the attribute last provided by the context server and uncertainty field 514 identifying the level of uncertainty of the value, a timestamp 515 indicating the time at which the value is effective, a units field 516 identifying the units for the value and the uncertainty, and an indication 517 of the number of context clients consuming values for the attribute instance. While row 501 indicates that an instance of the user.location attribute from the gps context server has a multi-part value of 47° 36.73′ N and 122° 18.43′ W degrees and minutes, in alternate embodiments multi-part values may not be used, such as instead having two attributes to represent this context element (e.g., user.location.latitude and user.location.longitude). Similarly, while field 517 indicates the number of context clients consuming values for an attribute, in alternate embodiments this number could be dynamically calculated rather than being stored (e.g., by using the attribute request table discussed below), or an identifier for each context client could instead be stored rather than merely a number. Other versions of the attribute instance table may lack some of the illustrated fields, such as the units field if all the instances of an attribute are restricted to having the same units and if such common information about all the attribute instances is stored elsewhere. Alternately, some versions of the attribute instance table could include additional information, such as a separate row for each attribute with multiple instances that contains common information about all of instances, and additional fields such as a context client field that contains the name of each context client registered to receive values for the attribute or instance of that row. Other versions of the attribute instance table could include other additional fields such as an optional specified context client field so that the context server can indicate one or more context clients that are able to receive values for the attribute (e.g., a list of authorized clients).
  • [0064]
    FIG. 6 is a data structure diagram showing an example context client table used to maintain a portion of the state of the characterization module. Each row corresponds to a registered context client, and contains a context client name field 611 identifying the name of the registered context client as well as a message handler field 612 containing the reference to a message handler provided by the context client for processing messages from the characterization module. Other versions of the context client table may lack some of the illustrated fields, or may contain additional fields (e.g., a registered attributes field that contains the names of all of the attributes for which the context server is currently registered to receive values).
  • [0065]
    FIG. 7 is a data structure diagram showing updated contents of the attribute instance table illustrated in FIG. 5. It can be seen that, in response to registration of a location_map context client consuming values for the user.in_region attribute, the characterization module has incremented the number of context clients consuming the user.in_region attribute from 0 to 1.
  • [0066]
    FIG. 14 is a data structure diagram showing an example attribute request table used to maintain a portion of the state of the characterization module. The attribute request table contains a row for each attribute for which a context client is currently registered to receive values. Each of these rows contains the following fields: an attribute name field 1411 containing the name of the attribute, and a context client name field 1412 identifying the context client that registered a request to receive values for the attribute. Note that a context client can request values for an attribute without specifying a particular instance, as in row 1401, or can instead request values for a specific attribute instance, as in row 1403. Other versions of the attribute request table may lack some of the illustrated fields, or may contain additional fields such as an optional field to specify one or more particular context servers that can supply the values for the attribute (e.g., a list of authorized context servers).
  • [0067]
    FIG. 8 is a flow diagram of one embodiment of the GetAttribute function. In step 801, if the requested attribute exists, then the facility continues in step 803, else the facility continues in step 802 to return an “attribute not found” error. In step 803, if a single instance of the attribute was requested, then the facility continues in step 804, else the facility continues in step 811. In step 804, if the requested instance exists, then the facility continues in step 806, else the facility continues in step 805 to return an “attribute instance not found” error. In step 806, if the age criterion specified for the attribute request is satisfied, then the facility continues in step 807 to return the requested attribute instance, else the facility continues in step 808 to “freshen” the attribute instance by calling the appropriate context server's request handler to request evaluation of the attribute instance. In step 809, if the age criterion is satisfied by the freshened attribute instance, then the facility continues in step 807 to return the freshened attribute instance, else the facility continues in step 810 to return the freshened attribute instance with an “age not satisfied” error. In step 811, where a single attribute instance was not requested, if any registered instances of the attribute satisfy the age criterion, then the facility continues in step 816, else the facility continues in step 812. In step 812, the facility freshens all registered instances of the requested attribute. In step 813, if any of the attributes freshened in step 812 satisfy the age criterion, then the facility continues in step 816, else the facility continues in step 814. In step 814, the facility applies the requested attribute mediator to select one instance, or otherwise derive a value from the registered instances. In step 815, the facility returns the instance with an “age not satisfied” error. In step 816, where one or more instances satisfy the age criterion, if more than one instance satisfies the age criterion, then the facility continues in step 817, else the facility continues in step 807 to return the attribute instance that satisfies the age criterion. In step 817, the facility applies the requested attribute mediator to select one instance from among the instances that satisfy the age criterion, or to otherwise derive a value from the instances that satisfy the age criterion. After step 817, the facility continues in step 807 to return the value produced by the mediator.
  • [0068]
    FIG. 9 is a data structure diagram showing updated contents of the attribute instance table illustrated in FIG. 7. It can be seen in attribute instance table 900 that, upon reevaluation by the ips context server of its instance of the user.elevation attribute, the characterization module replaced the former contents of the value, uncertainty and timestamp fields of row 903 with the values resulting from the reevaluation.
  • [0069]
    FIG. 10 is a data structure diagram showing an example condition table that contains a portion of the state of the characterization module. Condition table 1000 has a row for each condition created by a context client. Row 1001 contains a condition name field 1011 containing the name of the condition, a context client name 1012 identifying the context client that created the condition, a first logical parameter field 1013 and a second logical parameter field 1014 identifying attributes or conditions that are to be compared, a comparison value 1015 that specifies a value to which an attribute listed in the first logical parameter is compared if no second logical parameter is listed, and a logical operator 1016 identifying the logical operator to be applied in the comparison.
  • [0070]
    FIG. 11 is a data structure diagram showing an example condition monitor table that maintains a portion of the state of the characterization module. Condition monitor table 1100 has a row 1101 corresponding to a condition and containing each of the following fields: a condition monitor name field 1111 containing the name of the condition monitor; a context client name field 1112 containing the name of the context client that created the condition monitor; a condition name field 1113 that contains the name of the condition monitored by the condition monitor; a behavior field 1114 that indicates whether the condition monitor is triggered when the condition becomes true, when it becomes false, or when it changes value in either direction; a frequency field 1115 showing the frequency with which the condition monitor evaluates the condition; a condition last evaluated field 1116 showing the time at which the condition monitor last evaluated the condition; a trigger handler reference 1117 that identifies a trigger handler function of the context client that is to be called when the condition monitor is triggered; and a stop field 1118 that indicates whether the context client has suspended operation of the condition monitor. Such condition monitors can be used in a variety of ways. For example, when a context client is notified via the triggering of the trigger handler function that the value has changed, the context client can then retrieve the new value.
  • [0071]
    FIG. 12 is a data structure diagram showing updated contents of the condition monitor table illustrated in FIG. 11. It can be seen from stop field 1218 of row 1201 in condition monitor table 1200 that the region analysis context client has stopped, or suspended the operation of, the region boundary_cross condition monitor, perhaps in response to the observation that the user is now asleep and his or her location will remain constant.
  • [0072]
    In the foregoing, the facility is described as being implemented using a characterization module that is called by context servers and context clients, that caches attribute values, and that maintains status information about the operation of context servers and context clients. In an alternative preferred embodiment, however, the facility operates without the use of such a characterization module. In this embodiment, context servers communicate directly with context clients.
  • [0073]
    FIG. 13 is a data flow diagram showing the operation of the facility without a characterization module. It can be seen in FIG. 13 that context servers 1310, 1320, and 1330 provide attributes directly to context clients 1330, 1340, and 1350. For example, it can be seen that context server 1320 provides a user.elevation attribute 1322 directly to context client 1350. In this embodiment, the context client may itself cache attribute values recently obtained from a context server. Further, in this embodiment, context clients may themselves interrogate context servers for an enumeration of their attributes, and mediate between attribute instances provided by different context servers. For example, context client 1340 may mediate between the instance 1311 of the user.location attribute provided by context server 1310 and the instance 1321 of the user.location attribute provided by context server 1320.
  • [0074]
    In additional preferred embodiments, the facility may operate with a partial characterization module. Such a partial characterization module may include various combinations of the functionalities of routing communication between context servers and the context clients that consume their attribute values, caching attribute values, enumerating available attributes, and providing attribute mediation.
  • [0075]
    In additional preferred embodiments, the facility may provide a characterization module that implements a “push” information flow model in which, each time an attribute value provided by a context server changes, the new value is automatically provided to context clients. In further preferred embodiments, the facility provides a characterization module that implements a “pull” information flow model, in which attribute values are only obtained by the characterization module from the context servers when they are requested by a context client. In additional preferred embodiments, characterization modules are provided that support a variety of other information flow models.
  • [0076]
    FIG. 17 is a flow diagram of an embodiment of the Characterization Module routine 1700. The routine receives messages from context clients (CCs) and from context servers (CSes), as well as instructions from users, and processes the messages or instructions. In some embodiments, a CM could wait to execute code that would provide functionality until the functionality was requested, such as by dynamically loading code to provide a requested mediator. The routine begins in step 1705, where the characterization module (CM) performs various startup operations (e.g., setting up tables in which to temporarily cache state information, retrieving previous state information, launching CSes or CCs that have previously registered with the CM, etc.). The routine then continues to step 1710 to determine if the newly started CM is to take the place of another previously executing CM (e.g., based on a user indication when the new CM was started). If so, the routine continues to step 1715 to swap places with the other executing CM. One method of executing a swap that would be transparent to the CCs and CSes interacting with the other CM would be to request the other CM to transfer all of its current state information to the new CM (e.g., registrations of CCs, CSes, and attributes, conditions and notification requests, cached values for attributes and attribute properties, etc.), to then update the other CCs and CSes so that the messages they previously sent to the other CM will now be sent to the new CM, and to then have the other CM shutdown.
  • [0077]
    After step 1715, or if it was determined in step 1710 that another CM is not being swapped out, the routine continues to step 1720 to receive an indication from a user or a message from a CC or CS. The routine then continues to step 1725 where it performs the Notification Processing subroutine to notify any CCs or CSes about the received message or user indication if appropriate. As is explained in greater detail below, CCs and CSes can submit notification requests so that they will be notified by the CM upon a particular type of occurrence. Such notification requests could include occurrences such as when an attribute value changes, when a particular CC or CS registers or unregisters, when values for an attribute become available or unavailable (e.g., due to registration or unregistration), when a CC registers or unregisters to receive values for an attribute, when the availability of particular input/output devices changes or other computer system features change, when a package of related themed attributes becomes available or unavailable, for changes in CM internal status (e.g., a change in the default mediator), etc. In addition, the notification requests can be created based not only on explicit requests, but also after the occurrence of a particular type of event (e.g., if a CC requests a value for an attribute for which no CSes are currently supplying values, a notification request could be automatically created to alert the CC if a CS later registers to supply values for the attribute). Moreover, additional information about the notification requests can be supplied (e.g., a number of times that the submitter wants to receive notifications for the request, or an expiration date after which the notification will be removed or become inactive).
  • [0078]
    After step 1725, the routine continues to step 1730 to determine if a registration or unregistration message was received. If so, the routine continues to step 1735 to execute the Dynamically Specify Available Clients, Servers, and Attributes subroutine. Thus, CCs and CSes can register and unregister dynamically as they become available or unavailable, and can similarly modify the status of the attributes that they have registered with the CM. If a registration or unregistration message was not received in step 1730, the routine instead continues to step 1740 to determine if an attribute value or a request for an attribute value has been received from a CC or CS. If so, the routine continues to step 1745 to execute the Process Attribute Value Or Value Request Message subroutine. This subroutine will satisfy requests for attribute values if possible (e.g., by supplying a cached value or requesting one or more CSes to supply the value) and will return the requested value or an error message. Similarly, when attribute values are pushed to the CM from a CS, the CM will send the values if appropriate to CCs that have registered an interest in receiving values for the attribute.
  • [0079]
    If an attribute value or an attribute value request has not been received from a CC or CS in step 1740, the routine instead continues to step 1750 to determine if a request has been received to establish or modify a condition that monitors attribute values or other conditions, or to establish or modify a condition monitor. If so, the routine continues to step 1755 to process the request. As described previously, conditions and condition monitors can be created, removed, and have their operation suspended (e.g., by deactivating them) or resumed (e.g., by activating them).
  • [0080]
    If a condition-related request was not received in step 1750, the routine continues instead to step 1760 to determine if a message related to one or more other executing CMs has been received, and if so continues to step 1765 to process the message by executing the Process Distributed Characterization Module Message subroutine. Characterization modules can interact for a variety of reasons, as explained in greater detail below. If a message related to another CM has not been received, the routine continues instead to step 1770 to determine if a request has been received to establish or modify a notification request. If so, the routine continues to step 1775 to process the notification-related request. If a notification-related request was not received, the routine continues instead to step 1780 to determine if a shutdown message was received (e.g., from a user). If so, the routine continues to step 1790 to perform shutdown operations (e.g., notifying all registered CCs and CSes to unregister, or saving current state information), and then continues to step 1795 and ends. If it was instead determined that a shutdown message was not received, the routine continues to step 1782 to determine if another supported operation has been requested. If so, the routine continues to step 1784 to perform the other operation, and if not the routine continues to step 1786 to send an error message to the requester. For example, other types of operations may be a request to receive information about all available attributes, about all attributes available from a particular CS, about which CCs are receiving values for a particular attribute, about properties and property values associated with attributes and attribute instances, to launch or shutdown a CC or CS, to receive information about an attribute taxonomy, to force a CS to reevaluate the values for all its registered attributes, to change internal CM information (e.g., the default mediator), to provide information about available packages of related themed attributes, to provide information about available computer resources such as input/output devices, etc. After steps 1735, 1745, 1755, 1765, 1775, 1784, or 1786, the routine returns to step 1720. In other embodiments, additional types of functionality may be available or illustrated functionality may not be available. For example, in some embodiments any CC or CS may need to satisfy security requirements (e.g., by verifying their identity as an authorized module) before being allowed to request information or functionality from the CM or to provide information to the CM.
  • [0081]
    FIG. 18 is a flow diagram of an embodiment of the Notification Processing subroutine 1725. The subroutine examines the message or user indication received by the CM, determines whether any active notification requests are satisfied by the type of message or indication or by information contained in the message or indication, and notifies the submitters of any such requests when the requests are satisfied. The subroutine begins in step 1805 where it receives an indication of the message or user indication received by the CM. The subroutine continues to step 1810 to compare the received message or user indication to the notification requests that are currently stored and active. The subroutine then continues to step 1815 to retrieve any additional information that may be needed to determine if a notification request has been satisfied (e.g., a previous value for an attribute to determine how the attribute value has changed).
  • [0082]
    The subroutine then continues to step 1820 where it determines if any of the notification requests have been satisfied. If not, the subroutine continues to step 1895 and returns, but if so the subroutine continues to step 1825 to select the next satisfied notification request, beginning with the first. The subroutine then continues to step 1830 to send a notification to the supplier of the request that the request was satisfied, and can include additional information about the occurrence that satisfied the request. The subroutine then continues step 1835 to determine whether the notification request should be removed (e.g., if it was defined as a one-time request, or has expired). If so, the subroutine continues to step 1840 to remove the request, and if not the subroutine continues to step 1845 to determine if the notification request should be deactivated for the current time (e.g., so that a similar occurrence can be monitored at a later time). After steps 1840 or 1850; or if the notification request was not deactivated, the subroutine continues to step 1855 to determine if there are more satisfied notification requests. If so, the subroutine returns to step 1825, and if not the subroutine continues to step 1895 and returns. In addition, the subroutine could periodically check the various stored notification requests (e.g., as a background process) to determine if their status should be modified (e.g., activated, deactivated, or removed).
  • [0083]
    FIG. 19 is a flow diagram of an embodiment of the Dynamically Specify Available Clients, Servers, and Attributes subroutine 1735. The subroutine receives registration or unregistration requests for CCs, CSes, and/or attributes, and satisfies the requests as appropriate. The subroutine begins in step 1905 where it receives a registration or unregistration message. The subroutine continues to step 1910 to determine if security authorization is needed (e.g., for any CC or CS, or for CCs and CSes executing on a different computer from the CM). If so, the subroutine continues to step 1915 to determine if the security authorization has been satisfied (e.g., by the submitter of the message supplying a password or a verified digital signature). It is determined in step 1920 that the security authorization has not been satisfied, the subroutine continues to step 1925 where it sends an error message to the submitter. However, if it is instead determined that the security standard has been satisfied, or if security authorization was not needed in step 1910, the subroutine continues to step 1930 to determine the type of the registration or unregistration message.
  • [0084]
    If the message is determined to be related to a CC, the subroutine continues to step 1940 to determine if the message is to register the CC. If so, the subroutine continues to step 1941 to register the new client if possible (e.g., if all necessary information has been provided and there is not another registered CC with the same unique identifier). If it is determined in step 1942 that an error occurred during the registration attempt, the subroutine continues to step 1944 to send an error message to the submitter. If no error occurred, the subroutine instead continues to step 1946 to determine if the registration request includes one or more attributes of interest to be registered for the client. If so, the subroutine continues to step 1982 to register those attributes. If it was instead determined in step 1940 that the received message was not to register the client, the subroutine continues to step 1948 to determine if the message was to unregister the client. If so, the subroutine continues to step 1950 to unregister the client, and then continues to step 1952 to determine if any registered attributes remain for the client. If so, the subroutine continues to step 1994 to unregister each of those attributes.
  • [0085]
    If it was instead determined in step 1930 that the received message was related to a CS, the subroutine continues to step 1960 to determine whether the message is to register the CS. If so, the subroutine continues to step 1961 to register the new server if possible. It is determined in step 1962 that an error occurred during the registration attempt, the subroutine continues to step 1964 to send an error message to the submitter. If no error occurred, however, the subroutine instead continues to step 1966 to determine if the registration request includes one or more attributes to register for which the server is available to supply values. If so, the subroutine continues to step 1982 to register those attributes. If it was instead determined in step 1960 that the received message was not to register the CS, the subroutine continues to step 1968 to determine if the message was to unregister the server. If so, the subroutine continues to step 1970 to unregister the server, and then continues to step 1972 to determine if any registered attributes remain for the server. If so, the subroutine continues to step 1994 to unregister those attributes.
  • [0086]
    If it was instead determined in step 1930 that the received message was related only to one or more attributes and not to a CC or CS, the subroutine continues to step 1980 to determine whether the message is to register those attributes. If so, the subroutine continues to step 1982 to select the next attribute, beginning with the first. The subroutine then continues to step 1984 to determine if at least one instance of the attribute is currently registered. If so, the subroutine continues to step 1986 to register a new instance of the attribute, and if not the subroutine continues to step 1988 to register the first instance for the attribute. After steps 1986 or 1988, the subroutine continues to step 1990 to determine if there are more attributes to be registered, and if so returns to step 1982. If it is instead determined in step 1980 that the received message was not to register the attributes, the subroutine continues to step 1992 to determine if the message was to unregister the attributes, and if so continues to step 1994 to unregister each attribute. After steps 1925, 1964, 1944, or 1994, or if the determination was made in the negative for one of steps 1946, 1948, 1952, 1966, 1972, 1990, or 1992, the subroutine continues to step 1995 and returns. As discussed previously, a variety of other types of optional information can additionally be supplied when registering CCs, CSes or attributes (e.g., various properties for the attribute).
  • [0087]
    FIG. 20 is a flow diagram of an embodiment of the Process Distributed Characterization Module Message subroutine 1765. The subroutine receives information from another CM or an instruction about another CM, and processes the information or instruction as appropriate. The subroutine begins in step 2005 where it receives an indication of the received information or instruction. The subroutine then continues to step 2010 to determine if security authorization is needed. If so, the subroutine continues to step 2012 to determine if the security has satisfied. It is determined at step 2014 that the security authorization has not been satisfied, the subroutine continues to step 2016 to send an error message to the submitter. If it is instead determined that the security authorization has been satisfied or was not needed in step 2010, the subroutine continues to step 2018 to determine whether information from another CM has been received.
  • [0088]
    If it is determined in step 2018 that an instruction about another CM has been received, the subroutine continues to step 2020 to determine if the instruction is to register or unregister as a CC or CS of the other CM. If so, the subroutine continues to step 2022 to rename any attributes in the request if necessary. For example, if a current CM 1 wants information about an attribute user.mood.happiness for its own user from another CM 2, CM 1 will have to modify the name of the attribute (e.g., to CM1.user.mood.happiness) it requests since CM 2's attribute user.mood.happiness will refer to the user of CM 2. The same will be true for a variety of other attributes that specify attributes relative to the CM, but not to attributes with absolute specifications (e.g., person.ABC.mood.happiness). After step 2022, the subroutine then continues to step 2024 to send a request to the other CM to reflect the request using the renamed attributes, with the other CM to perform the registration or unregistration.
  • [0089]
    If it is instead determined in step 2020 that the instruction was not to register or unregister, the subroutine continues to step 2026 to determine whether the instruction is to send an attribute value or an attribute value request to the other CM. If so, the subroutine continues to step 2028 to rename any attributes in the request if necessary, and then continues to step 2030 to determine whether a request or an attribute value is being sent. If an attribute value is being sent, the subroutine sends the value to the other CM in step 2032, and if a request is being sent the subroutine sends the request in step 2034. After step 2034, the subroutine continues to step 2036 to receive the requested value or an error message, and if the value is received rather than an error message, the subroutine sends the received value to the requester at step 2038.
  • [0090]
    If it is instead determined in step 2026 that the received instruction is not to send an attribute value or an attribute value request, the subroutine continues to step 2040 to determine if a group-wide attribute is to be modeled (e.g., troop morale for a group of soldiers that would require information for many or all of the soldiers). If so, the subroutine continues to step 2042 to request attribute values from the other CMs that are needed for the modeling, and then continues to step 2044 to receive the requested values or error messages. If the necessary values are received to perform the modeling, in step 2046 the subroutine determines the value of the group-wide attribute and in step 2048 sends the value to the requester. In alternate embodiments, any such modeling of attributes may be performed only by CSes, with the CM merely requesting values from other CMs as instructed and supplying the received values to the appropriate CS.
  • [0091]
    If it is instead determined in step 2040 that the received instruction is not to model a group-wide attribute, the subroutine continues to step 2050 to determine if the instruction is to aggregate information from subordinate CMs (e.g., in a hierarchical organization such as a business or the military, the hierarchy of users can be reflected in a hierarchy of their CMs) or specialized CMs (e.g., a CM specialized to monitor a user's health and to detect health problems). If so, the subroutine continues to step 2052 to request the information from the other CMs as needed, and continues to step 2054 to receive the requested information or error messages. If the necessary information is received, in step 2056 the subroutine aggregates the information, and in step 2058 sends the aggregated information to the requester. In alternate embodiments, any such aggregating of information may be performed only by CSes, with the CM merely requesting information from other CMs as instructed and supplying the received values to the appropriate CS.
  • [0092]
    If it is instead determined in step 2050 that the received instruction is not to aggregate information, the subroutine continues to step 2060 to determine if the received instruction is to use the processing capabilities of another computer or CM. If so, the subroutine continues to step 2062 to request the other computer or CM to perform an indicated task. The subroutine then continues to step 2064 where it receives the results of the task, and uses those results as if the task have been performed locally. If it is instead determined in step 2060 that the received instruction is not to use the processing abilities of another computer, the subroutine continues to step 2065 to determine if the received instruction is to send information to a module such as a thin client. If so, the subroutine continues to step 2067 to send the indicated information (e.g., from a CC), and if not the subroutine continues to step 2069 to perform another task as indicated. For example, other types of tasks could be to instruct another CM to swap itself out or to modify its internal state (e.g., to change a default mediator or to add a new mediator).
  • [0093]
    If it was instead determined at step 2018 that information from another CM has been received, the subroutine continues to step 2070 to determine if a registration or unregistration request has been received. If so, the subroutine continues to step 2071 to rename any attributes if necessary, and then continues to step 2072 to resubmit the request as if from a CC or a CS using the renamed attributes. If the information was not a registration or unregistration request, the subroutine continues to step 2073 to determine if an attribute value or an attribute value request has been received. If so, the subroutine continues to step 2074 to rename the attributes if necessary, and then continues to step 2075 to determine whether an attribute value or an attribute value request has been received. If an attribute value has been received, the subroutine continues to step 2076 where it resubmits the value as being from a CS, and if not the subroutine continues to step 2077 where it resubmits the attribute value request as being from a CC. After step 2077, the subroutine continues to step 2078 where it receives the requested value or an error message, and in step 2079 sends the received value to the requesting CM if an error message was not received.
  • [0094]
    If it was instead determined in step 2073 that an attribute value or attribute value request was not received, the subroutine continues to step 2080 to determine if the received information was an indication to modify the internal state of the CM. If so, the subroutine continues to step 2081 where it modifies the state as indicated. If the received instruction was not to modify the internal state, the subroutine continues to step 2082 to determine if the request is to swap the CM out to be replaced by the other requesting CM. If so, the subroutine continues to step 2084 to send the current state information from the CM to the requesting CM. In addition, the CM could perform other tasks if necessary such as updating the currently registered CCs and CSes so that they now will communicate with the other CM. The subroutine then continues to step 2086 to wait for an indication from the other CM to exit, and after receiving the indication, submits a shutdown request in step 2088. If the received instruction was not to swap out, the subroutine continues to step 2090 to perform the other task as indicated if appropriate. After steps 2016, 2024, 2032, 2038, 2048, 2058, 2064, 2067, 2069, 2072, 2076, 2079, 2081, 2088, or 2090, the subroutine continues to step 2095 and returns.
  • [0095]
    FIG. 21 is a flow diagram of an embodiment of the Process Attribute Value Or Value Request Message subroutine 1745, as illustrated in the accompanying figure and described elsewhere. In particular, the subroutine receives an indication of an attribute value or a request for an attribute value, and processes the value or request as appropriate (e.g., pulling values from servers when needed to satisfy requests and pushing received values to clients when appropriate). Those skilled in the art will appreciate that in other embodiments only one of the push and pull data flow models may be supported. The subroutine begins at step 2105 where it receives an indication of an attribute value or a request for an attribute value. The subroutine then continues to step 2110 to determine if an attribute value or a request was received.
  • [0096]
    If a value was received, the subroutine continues to step 2120 to execute the Process Received Attribute Value subroutine, such as to store the value and to process additional associated information received about the value. The subroutine next continues in the illustrated embodiment to push the received value or a related value to clients as appropriate. Those skilled in the art will appreciate that in other embodiments such values may merely be cached or otherwise stored until requested by a client. Alternately, even if received values are not generally pushed to clients, in other embodiments such values could be pushed to clients in limited circumstances, such as an update to a related value that had previously been sent to a client when the newly received value is more accurate.
  • [0097]
    In the illustrated embodiment, the subroutine continues to step 2122 to determine whether there are any previously specified requests or indications of interest related to the received value that would cause the received value or a related value to be pushed to one or more clients. If it is determined in step 2125 that there are any such requests or indications, the subroutine continues to step 2130 to determine if there are multiple attribute instance values available that meet the appropriate criteria (if any are specified) to satisfy the requests or indications. For example, a default or specified threshold for the freshness of values could be used as a criteria. If there are multiple values, the subroutine continues to step 2132 to execute the Mediate Available Values subroutine and produce a mediated value from the multiple available values, and in step 2134 selects the mediated value produced by the subroutine. If it was instead determined in step 2130 that there are not multiple attribute instance values available for the received value, the subroutine continues to step 2136 to select the received value. After steps 2134 or 2136, the subroutine continues to step 2138 to select the next request of the identified requests, beginning with the first request. The subroutine then continues to step 2140 to execute the Push Selected Attribute Value To Client subroutine for the selected request, and then continues to step 2142 to determine if there are more identified requests. If so, the subroutine returns to step 2138 to select the next request.
  • [0098]
    If it was instead determined in step 2110 that a request for a value was received, the subroutine continues to step 2150 to identify all attribute instances that match the request (e.g., that satisfy one or more criteria for the value that are specified with the request). The subroutine then continues to step 2152 to determine if there are any such instances, and if not continues to step 2154 to send an error message to the requester. In the illustrated embodiment, the subroutine next pulls current values for the identified attribute instances from servers as appropriate. Those skilled in the art will appreciate that in other embodiments only those values that have previously been received and stored may be supplied to clients. Alternately, even if current values are not generally pulled from servers, in other embodiments such values could be pulled from servers in limited circumstances, such as when explicitly requested by a client.
  • [0099]
    In the illustrated embodiment, if it is determined in step 2152 that at least one attribute instance is identified, the subroutine continues to step 2156 to select the next such instance, beginning with the first. The subroutine in step 2158 then determines if a new value is needed for the selected instance (e.g., the available value does not meet some specified criteria, such as an accuracy threshold specified by the requesting client). If so, the subroutine continues to step 2160 to execute the Pull Attribute Value From Server subroutine. The subroutine in step 2162 next waits for a value or error message response from the server, and determines if a value is received. If a value is received, the subroutine then continues to step 2164 to execute the Process Received Attribute Value subroutine. After step 2164, or if it was determined in step 2158 that the instance does not need a new value or in step 2162 that a new value was received, the subroutine continues to step 2166 to determine if there are more instances identified. If so, the subroutine returns to step 2156 to select the next such instance, and if not continues to step 2168 to determine if there are multiple values now available for the request that meet any relevant criteria. While all identified attribute instance values that match the request are used in the illustrated embodiment, in other embodiments a different or additional selection process for the values could be used. For example, information about the various servers that can supply the attribute instance values may be available (e.g., dynamically), and if so only certain of the servers could be selected based on the information with only the values from those servers being used.
  • [0100]
    If it is determined in step 2168 that there are multiple values available, the subroutine continues to step 2170 to execute the Mediate Available Values subroutine to produce a mediated value from the multiple available values, and in step 2172 sends the produced mediated value and any additional information about the value (e.g., properties, an associated uncertainty value, an indication of the server that produced the value, an indication of the mediator used to produce the value, etc.) to the requester. If it was instead determined in step 2168 that there are not multiple values available, the subroutine continues to step 2174 to determine if a single value is available, and if not continues to step 2178 to send an error message to the requester. If it is instead determined that there is a single value available, the subroutine continues to step 2176 and sends the value and any additional information to the requester. After steps 2154, 2172, 2176 or 2178, or if it was determined in step 2125 that there were no requests identified or in step 2142 that there were no more requests, the subroutine continues to step 2195 and returns.
  • [0101]
    FIG. 22 is a flow diagram of an embodiment of the Process Received Attribute Value subroutine 2200, as illustrated in the accompanying figure and described elsewhere. In particular, the subroutine receives an attribute value from a server, stores the value if appropriate (e.g., in a cache or long-term storage), processes additional received information associated with the value if appropriate, and processes any conditions related to the received value. The subroutine begins in step 2205 where it receives an indication of a received attribute value. The subroutine then continues to step 2210 to determine if the attribute for which the value is received is registered, and if not continues to step 2215 to send an error message to the server. If it is instead determined in step 2210 that the attribute is registered, the subroutine continues to step 2220 to determine if additional information about the value was received from the server. If so, the subroutine continues to step 2225 to execute the Process Additional Information About-Received Value subroutine.
  • [0102]
    After step 2225, or if it was instead determined that additional information about the value was not received from the server,-the subroutine continues to step 2230 to determine whether values for the attribute are being cached or otherwise temporarily stored. If so, the subroutine continues to step 2235 to cache the received value as well as any additional information received. Those skilled in the art will appreciate that the length of time used for caching can vary in a variety of ways, such as based on the type of information or for a particular attribute. After step 2235, or if it was instead determined that values are not being cached for the attribute, the subroutine continues to step 2240 to determine if values for the attribute are being stored in a long-term manner (e.g., being logged). If so, the subroutine continues to step 2245 to store the received value as well as any additional information received.
  • [0103]
    After step 2245, or if it was instead determined in step 2240 that values are not being stored for the attribute, the subroutine continues to step 2250 to determine if the value and/or any additional information about the value triggers any active stored conditions. In step 2255, if there are any such conditions, the subroutine continues to step 2260 to select the next such condition, beginning with the first. After step 2260, the subroutine continues to step 2265 to send a message to the entity associated with the condition (e.g., a client that created the condition) to indicate that the condition is satisfied. After step 2265, the subroutine continues to step 2270 to determine if the condition should now be removed. If so, the subroutine continues to step 2275 to remove the condition, and if not the subroutine continues to step 2280 to determine if the condition should now be deactivated. If so, the subroutine continues to step 2285 to deactivate the condition. After steps 2275 or 2285, or if it was instead determined in step 2280 that the condition is not to be deactivated, the subroutine continues to step 2290 to determine if there are more triggered conditions. If so, the subroutine returns to step 2260 to select the next such condition. After step 2215, or if it was instead determined in step 2255 that there were not any triggered conditions or in step 2290 that there were no more triggered conditions, the subroutine continues to step 2295 and returns.
  • [0104]
    In the illustrated embodiment, attribute values are received by the characterization module from servers either when the characterization module requests a new value from the server or when the server pushes a new value to the characterization module. In some embodiments in which a server has previously sent an attribute value to the characterization module in response to a request, the server may later send updated values for the attribute to the characterization module without a later request from the characterization module, such as if a more accurate or updated value is obtained by the server. In addition, in other embodiments servers could provide other types of information that could be received and processed by the characterization module. In particular, a server could provide a variety of types of meta-information about attribute values to the characterization module, such as information about a technique used to generate a value or an indication that a new value is available without sending the value until requested.
  • [0105]
    FIG. 23 is a flow diagram of an embodiment of the Process Additional Information About Received Value subroutine 2225, as illustrated in the accompanying figure and described elsewhere. As illustrated and discussed elsewhere, a variety of types of information related to attribute values (e.g., uncertainty or accuracy information, a timestamp of when the value was created or supplied or was most accurate, an indication that the value is a constant, indications of restrictions on whether the availability of the attribute instance or of the particular value should be available to any or to specified CCs, data type, units, a format version, a name, any generic attribute property supplied by the CS, etc.) can be received from CSes, can be used by the CM to determine whether and how to supply the values to CCs, can be supplied to CCs, and can be used by CCs when processing the received attribute values. For example, units as indicated below could be specified.
    Quantity Measured Unit
    Distance Meter
    Mass/Weight Kilogram
    Temperature Centigrade
    Time Second
    Speed Meters per second
    Acceleration Meters per second2
    Arc Radians
    Data size Bytes
    Data Throughput Bytes per second
    Force Newtons
    Power Watts
    Energy Joules
  • [0106]
    In addition, uncertainty of an attribute value can be indicated in a variety of ways. An example of an uncertainty specification is as follows. For each attribute instance there is a finite likelihood that the real quantity being measured is not the same as the value being expressed. For example, the speedometer of a car may show 30 mph when the “true” instantaneous speed is 32.56 mph. There are numerous factors that may give rise to these discrepancies, including the following: precision of measuring apparatus, conversion of continuous quantities to discrete values in the measurement process, random fluctuations, temporal variation, systematic errors, and measurement latency. Since different measured quantities have different sources of uncertainty, it is impossible to foresee and account for each individually. It is therefore helpful to express the overall effects with a general characterization of uncertainty. One type of uncertainty values represent the cumulative effects of all possible discrepancy sources. These uncertainty values may conform to a single, universal definition so that attribute mediators and clients can make effective use of them. Thus, the following definition of uncertainty, which is based upon the definition of standard deviation for random fluctuations about a mean value, could be used for numeric values:
  • [0107]
    For an attribute instance value, μ, the associated uncertainty, σ, shall represent the likelihood that the following condition has a 68% probability of being true:
    μtrue−σ≦μ≦μtrue
  • [0108]
    Where μtrue represents the “true” value that the attribute represents.
  • [0109]
    As with uncertainty, a value timestamp can be indicated in a variety of ways. An example of a timestamp specification is as follows. Attribute values may be thought of as representations of a particular quantity at a point in time. Often this time is not proximate to that of use, so it can be useful to provide the proper timestamp along with the value. One version of a timestamp is defined as follows:
  • [0110]
    The timestamp represents the moment at which the associated value would have been valid had it been measured directly at that moment. This definition results in some attributes having timestamps that do not correspond to the time at which their values were calculated. For instance, an attribute that represents the acceleration of the user can be calculated by looking at the change in velocity over a period of time. The necessary computations may further delay the availability of the acceleration value. This timestamp is thus specified to represent the time at which the acceleration was “most” valid, which in this case could be the middle of the time period during which the velocity was measured.
  • [0111]
    Other types of additional information related to an attribute value can include history information (e.g., frequency of past use and past popularity information), an indication of the supplier of the attribute, indications of equivalent attributes (e.g. for mediation purposes or if a value for this attribute is not available at a later time), indications of clients that have registered for this attribute or consumed values for the attribute, descriptions of clients in order to track statistics, information to be used to evaluate characterization module efficiency and/or to facilitate process optimization, and indication of a verification of accuracy (e.g., from a third-party, or of the value generation technique that was used), a consumer rating or reputation based on input from other clients (e.g., efficiency or reliability), a cost to use the value (e.g., an actual price, or an amount of time needed to retrieve or process the value), future availability of the attribute value (e.g., how intermittent additional values may be), a version of the attribute, etc.
  • [0112]
    The subroutine illustrated in FIG. 23 begins in step 2305 where additional information about an attribute value is received. The subroutine continues to step 2310 to determine if a timestamp is received, and if so continues to step 2315 to associate the timestamp information with the received value. After step 2315, or if it was instead determined that a timestamp is not received, the subroutine continues to step 2320 to determine if uncertainty or other accuracy information is received, and if so continues to step 2325 to associate that information with the received value. After step 2325, or if it was instead determined that uncertainty or other accuracy information is not received, the subroutine continues to step 2330 to determine if accuracy decay information (e.g., the rate at which the accuracy of the value changes over time) is received, and if so continues to step 2335 to associate that information with the received value. After step 2335, or if it was instead determined that accuracy decay information is not received, the subroutine continues to step 2340 to determine if information indicating that the value is a constant is received, and if so continues to step 2345 to associate that information with the received value. After step 2345, or if it was instead determined that constant-related information is not received, the subroutine continues to step 2350 to determine if information about which clients are to have access to the supplied value is received, and if so continues to step 2355 to associate that information with the received value so that client access to the attribute value is so restricted. After step 2355, or if it was instead determined that client access information is not received, the subroutine continues to step 2360 to associate any other received additional information with the received value, and then continues to step 2360 and returns. Those skilled in the art will appreciate that the various types of additional information can be associated with the received value in a variety of ways, such as by using a data structure to represent a received value that includes elements for the various types of associated information.
  • [0113]
    FIG. 24 is a flow diagram of an embodiment of the Mediate Available Values subroutine 2400, as illustrated in the accompanying figure and described elsewhere. As illustrated and discussed elsewhere, a variety of different types of mediators can be defined and specified. For example, some mediators include the following.
    Mediator Name Description
    First The first attribute instance that was created.
    Last The last attribute instance that was created.
    Fast The first attribute instance to respond to a request
    for evaluation.
    Confidence The attribute instance with the lowest
    uncertainty.
    Freshness The attribute instance with the newest data value.
    Average The attribute instances are averaged and the
    result returned.
    Vote Two or more attributes that agree overrule ones
    that do not.
    User Choice The user is presented with a choice of which
    instance to use.
    Fast Decay The instances' confidence is attenuated quickly
    over time based upon the age of the data. The
    attenuated confidence is used to select the instance.
    Slow Decay The instances' confidence is attenuated slowly
    over time based upon the age of the data. The
    attenuated confidence is used to select the instance.

    Those skilled in the art will appreciate that a variety of other mediators could similarly be used, including using the previously used value or a default value. In addition, other techniques could also be used, such as indicating that no value is available, asking a user to choose between available values or to provide additional instructions, repeatedly trying to obtain an appropriate value, attempt to identify new possible sources or a new mediation mechanism or technique, etc.
  • [0114]
    The subroutine begins at step 2405 where an indication of the values available for the mediation are received. The subroutine then continues to step 2410 to determine if a requester of the mediated value indicated a mediator to be used, and if so continues to step 2415 to select that mediator. If it is instead determined that the requester did not indicate a mediator to be used, the subroutine continues to step 2420 to determine if a supplier of one or more of values being mediated indicated a mediator to be used, and if so continues to step 2425 to select that mediator. If it is instead determined that a supplier did not indicate a mediator to be used, the subroutine continues to step 2430 to determine if a default mediator is available, and if so continues to step 2435 to select that mediator. If it is instead determined that a default mediator is not available, the subroutine continues to step 2440 to determine the mediators that are available to be used and then in step 2445 selects one of the available mediators. After steps 2415, 2425, 2435 or 2445, the subroutine continues to step 2450 to apply the selected mediator to the available values in order to select one or the available values or to generate a related value based on the available values. The subroutine then continues to step 2455 to return the mediated value, and returns. Those skilled in the art will appreciate that in other embodiments mediators could be identified and/or obtained in other manners, such as by being specified by third-parties that are not acting as a client, server, or characterization module.
  • [0115]
    FIG. 25 is a flow diagram of an embodiment of the Pull Attribute Value From Server subroutine 2160, as illustrated in the accompanying figure and described elsewhere. In particular, the subroutine begins in step 2505 where an indication of a request for an attribute instance value is received. The subroutine then continues to step 2510 to determine if an ID for the request has been received. If not, the subroutine continues to step 2515 to generate a unique request ID. After step 2515, or if it was instead determined that an ID for the request has been received, the subroutine continues to step 2520 to request an attribute value from the server registered for the attribute instance, including the unique ID with the request. The unique ID is included so that any circular references during the requests can be detected, as explained in greater detail below. The subroutine next continues to step 2525 to receive in response an attribute value and optionally additional information, or to instead receive an error message. In step 2530, the received information or error message is sent to the requester of the value, and in step 2595 the subroutine returns.
  • [0116]
    FIG. 26 is a flow diagram of an embodiment of the Push Attribute Value To Client subroutine 2140, as illustrated in the accompanying figure and described elsewhere. In particular, in the first step the subroutine receives an indication of an attribute instance value and of a client to receive that value. The subroutine then continues to the second step to determine if additional information is associated with the indicated value, and if so retrieves that additional information. After retrieving the additional information, or if it was instead determined that there is no associated additional information, the subroutine next sends the value and any available additional information to the indicated client. The subroutine then returns.
  • [0117]
    FIG. 27 is a flow diagram of an embodiment of the Context Client routine 2700. The routine receives messages from the CM as well as instructions from users, sends messages to the CM, and processes received messages and instructions. In some embodiments, a CC could indicate to the CM an interest in receiving values for one or more attributes, but not begin to otherwise execute (e.g., by dynamically loading code) until a value for one of the attributes is supplied by the CM. The routine begins in step 2702 where the CC registers with the CM. The routine then continues to step 2704 where the CC optionally registers for one or more attributes of interest with the CM. The routine continues to step 2706 where it receives an indication of an instruction or of information received. The routine continues to step 2708 where it determines whether information or an instruction has been received.
  • [0118]
    If information has been received, the routine continues to step 2710 to determine if information about the satisfaction of a notification request has been received, and if so continues to step 2712 to process the notification satisfaction information and to take appropriate action. If notification information has not been received, the routine continues to step 2714 to determine if information about the satisfaction of a condition has been received, and if so continues to step 2716 to process the condition satisfaction information and to take appropriate action. If condition information has not been received, the routine continues to step 2718 to determine if a status message from the CM has been received (e.g., that a particular CS or a particular attribute has been unregistered), and if so continues to step 2720 to process the status information and to take appropriate action. If a status message has not been received, the routine continues to step 2722 to determine if an attribute value has been pushed to the CC. If not, the routine continues to step 2724 to process the other information that has been received, and if so continues to step 2726 to determine if additional information related to the value has also been received. If additional information has been received, the subroutine continues to step 2730 to process the value and the additional information, and if not the routine continues to step 2728 to process the value.
  • [0119]
    If it was instead determined in step 2708 that an instruction was received, the routine continues to step 2740 to determine if the instruction is to send a notification-related request (e.g., to establish a request) to the CM, and if so the routine continues to step 2742 to send the request. If the instruction is not to send a notification-related request, the routine continues to step 2744 to determine if the instruction is to send a condition-related request (e.g., to temporarily suspend an existing condition), and if so the routine continues to step 2746 to send the request to the CM. If a condition-related request was not received, the routine continues to step 2748 to determine if an instruction to send an attribute value request was received, and if so continues to step 2750 to request the attribute value from the CM. In addition, other information could also be specified with the request, such as a mediator to be used if there are multiple available values or an indication of a particular supplier from whom to receive the value. After step 2750, the routine then continues to step 2752 to wait for the requested value or an error message. If it is determined in step 2754 that a value was received, the routine continues to step 2726, and if not the routine continues to step 2756 to process the error message.
  • [0120]
    If it was instead determined in step 2748 that the instruction was not to send an attribute value request, the routine continues to step 2758 to determine if the instrument was to send another type of request. If so, the routine continues to step 2760 to send the request, and if not the routine continues to step 2762 to perform another instruction as indicated. A variety of other types of requests could be sent to the CM, such as to shutdown the CM or a CS, to launch a CS, to specify a default mediator for the CM, etc. After steps 2712, 2716, 2720, 2724, 2728, 2730, 2742, 2746, 2756, 2760, or 2762, the routine continues to step 2770 to determine whether to continue. If not, the routine continues to step 2772 to unregister the registered attributes for the CC, next to step 2774 to unregister the client with the CM, and then to step 2795 to end. If it is instead determined to continue, the routine continues to step 2776 to determine whether any currently registered attributes should be unregistered, and if so continues to step 2778 to unregister the attributes with the CM. After step 2778, or if it was determined not to unregister any attributes, the routine continues to step 2780 to determine whether to register any additional attributes. If so, the routine continues to step 2782 to register for one or more attributes of interest. After step 2782, or if it was determined not to register any additional attributes, the routine returns to step 2706.
  • [0121]
    FIG. 28 is a flow diagram of an embodiment of the Context Server routine 2800. The routine receives messages from the CM as well as instructions from users, sends messages to the CM, and processes received messages and instructions. In some embodiments, a CS could indicate to the CM an ability to supply values for one or more attributes, but not begin to otherwise execute (e.g., by dynamically loading code) until a value is requested. The routine begins in step 2802 where the CS registers with the CM. The routine then continues to step 2804 where it registers with the CM for one or more attributes for which the CS has the ability to supply values. The routine continues to step 2806 where it receives an indication of an instruction or of information received. The routine continues to step 2808 where it determines whether information or an instruction has been received.
  • [0122]
    If an instruction was received, the routine continues to step 2810 to determine if the instruction is to send a notification-related request (e.g., to establish a request) to the CM, and if so the routine continues to step 2812 to send the request. If the instruction is not to send a notification-related request, the routine continues to step 2814 to determine if the instruction is to send a condition-related request (e.g., to temporarily suspend an existing condition), and if so the routine continues to step 2816 to send a request to the CM. If a condition-related request was not received, the routine continues to step 2818 to determine if the instruction was to send another type of request. If so, the routine continues to step 2820 to send the request, and if not the routine continues to step 2822 to perform another instruction as indicated.
  • [0123]
    If it was instead determined in step 2808 that information has been received, the routine continues to step 2830 to determine if information about the satisfaction of a notification request has been received, and if so continues to step 2832 to process the notification information and to take appropriate action. If notification information has not been received, the routine continues to step 2834 to determine if information about the satisfaction of a condition has been received, and if so continues to step 2836 to process the condition information and to take appropriate action. If condition information has not been received, the routine continues to step 2838 to determine if a status message from the CM has been received (e.g., that a particular CC has registered), and if so continues to step 2840 to process the status information and to take appropriate action.
  • [0124]
    If a status message has not been received, the routine continues to step 2850 to determine if a pull attribute value request has been received by the CS, along with an ID that uniquely identifies the request. The unique ID in this example embodiment is used to allow the context server to determine if a circular reference exists when determining the requested attribute value. For example, consider the situation in which CS 1 is registered to supply values for attribute 1, and CS 2 is registered to supply values for attribute 2. In addition, imagine that the calculation of the value for attribute I depends on the value for attribute 2. Thus, when CS 1 receives a pull request to supply the value for attribute 1, it requests the value for attribute 2 from the CM, which in turn request the value from CS 2. After receiving the value for attribute 2 from CS 2 via the CM, CS 1 can then calculate the value for attribute 1 and satisfy the initial request by supplying the value to the CM. If, however, CS 2 also depends on the value for attribute 1 in order to calculate the value for attribute 2, a circular reference may exist. In that situation, after CS 1 requests the value of the attribute 2 in order to calculate the value for attribute 1, CS 2 may in turn request the value of attribute 1 from CS 1 (via the CM), thus creating a loop such that neither attribute value can be calculated. In order to detect such circular references, the example routine uses a unique ID passed along with attribute value requests. Alternate equivalent ways of identifying circular references could instead be used, or no such processing could be performed.
  • [0125]
    In the illustrated embodiment, if it is determined that a pull attribute value request has been received by the CS, the routine continues to step 2852 to determine if the received request ID matches a temporarily stored ID for the same attribute value. If so, a circular reference exists, and the routine continues to step 2853 to return an error message. If the ID does not match, the routine continues to step 2854 to determine the input information needed (if any) to calculate the requested value. The routine then continues to step 2856 to determine if the value of another attribute is needed. If so, the routine in step 2858 temporarily stores an indication of the attribute whose value is being calculated and of the ID. The routine then continues to step 2860 to request the attribute value needed, including the received ID. In step 2862, the routine waits for the requested value or error message. After receiving the value or error message, the routine continues to step 2864 to determine if more attribute values are needed, and if so to return to step 2860. After all of the needed attribute values have been received, the routine continues to step 2866 to remove the temporarily stored attribute value and ID, and then continues to step 2868 to determine if any errors were received for needed attribute values such that sufficient information to calculate the value requested of the CS is not available. If so, the routine continues to step 2853 to signal an error.
  • [0126]
    If there are no such errors, or if it was instead determined in step 2856 that no attribute values were needed, the routine continues to step 2870 to determine if any sensor values or other input information is needed to calculate the value requested of the CS. If so, the routine continues in steps 2872 through 2876 to request and receive the sensor or other input information that is needed. The routine then continues to step 2878 to determine if any errors were received for needed sensor values or other input information such that sufficient information to calculate the value request of the CS is not available. If so, the routine continues to step 2853. If no such errors occurred, or if it was instead determined in step 2870 that no sensor or other input information was needed, the routine continues to step 2887 to calculate the requested attribute value based on the received information. The routine then continues to step 2888 to optionally calculate additional information about the value that characterizes it (e.g., a timestamp or uncertainty information), and then continues to step 2889 to send the value and any additional information to the CM to satisfy the request.
  • [0127]
    If it was instead determined in step 2850 that an attribute value request was not received, the routine continues to step 2880 to determine if sensor or other input information has been pushed to the CS. If not, the routine continues to step 2882 to process the other information received, and if so continues to step 2884 to determine if the CS has sufficient information to calculate one or more attribute values based on the received input information and other stored information. If so, the routine continues to step 2887 to calculate those values and to push them to the CM, and if not the routine continues to step 2886 to store the sensor information for later use. In alternate embodiments, the CS could request other information that is needed to calculate an attribute value when sensor or other input information is received, rather than waiting until all necessary information has been received.
  • [0128]
    After steps 2812, 2816, 2820, 2822, 2832, 2836, 2840, 2853, 2882, 2886 or 2889, the routine continues to step 2890 to determine whether to continue. If not, the routine continues to step 2891 to unregister the registered attributes for the CS, next to step 2892 to unregister the server with the CM, and then to step 2899 to end. If it was instead determined to continue, the routine continues to step 2893 to determine whether any currently registered attributes should be unregistered, and if so continues to step 2894 to unregister the attributes with the CM. After step 2894, or if it was determined not to unregister any attributes, the routine continues to step 2896 to determine whether to register any additional attributes. If so, the routine continues to step 2897 to register for one or more attributes of interest. After step 2897, or if it was determined not to register any additional attributes, the routine returns to step 2806.
  • [0129]
    As discussed previously, a variety of error messages can be used by the CS, CM, and CC. Example error messages include the following.
      • Attribute already exists—Occurs when a CS attempts to create an attribute instance that already exists.
      • Attribute does not exist—Occurs when the CM receives a request for an attribute that does not exist.
      • Attribute instance does not exist—Occurs when the CM receives a request for a specific instance of an attribute which is not registered.
      • Attribute mediator does not exist—Occurs when a request for an attribute mediator could not be fulfilled because the name does not correspond to an existing attribute mediator.
      • Attribute unavailable—Occurs when a CS determines that it cannot satisfy a request for reasons other than when an attribute upon which it depends returns an error.
      • CS already running—A request to launch a CS could not be completed because the CS was already running.
      • CS does not exist—A request has been made for a CS that has not registered.
      • CS not found—A request to launch a CS could not be completed because the CS was not found.
      • CS unavailable—A request was made to a CS that cannot respond.
      • Condition already exists—Occurs when a client attempts to create a condition with a name that is already in use.
      • Condition does not exist—A request has been made for a non-existent condition.
      • Event already exists—Occurs when a client attempts to create an event with a name that is already in use.
      • Event does not exist—A request has been made for a non-existent event.
      • Inconsistent attribute data type—Occurs when a CS registers or provides an attribute instance for an attribute that already exists that has a different data type.
      • Request timed out—Occurs when the timeout has been exceeded and the request cannot be satisfied.
        When error messages are received in some embodiments, the module receiving the error may make the request again but specify that diagnostic information is to be received, thus assisting in identifying the source of the error.
  • [0145]
    From the foregoing it will be appreciated that, although specific embodiments have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims. In addition, while certain aspects of the invention are presented below in certain claim forms, the inventors contemplate the various aspects of the invention in any available claim form. For example, while only one some aspects of the invention may currently be recited as being embodied in a computer-readable medium, other aspects may likewise be so embodied. Accordingly, the inventors reserve the right to add additional claims after filing the application to purse such additional claim forms for other aspects of the invention.

Claims (65)

  1. 1. A method in a wearable computer for an executing user characterization system to provide information about a current state of a user of the wearable computer, the user characterization system modeling the current state with multiple state attributes and including state server modules (SSMs) to supply values for the state attributes, state client modules (SCMs) to process values for the state attributes, and an intermediary module to facilitate exchange of state attribute values, comprising:
    under control of each SSM, generating values for at least one of the state attributes and sending the generated values to the intermediary module;
    under control of each SCM, receiving values for at least one state attribute from the intermediary module and performing processing based on the received values;
    under control of the intermediary module, facilitating exchange of values by,
    receiving values for the state attributes from SSMs and from a first of multiple other characterization systems, each of the other characterization systems executing on another computer to model a current state related to the another computer;
    for each state attribute, storing the received values for the attribute; and
    receiving requests for values of indicated state attributes from SCMs and from a second of the other characterization systems, and sending stored values of the indicated state attributes to the SCMs and the second other characterization system; and
    modeling an aspect of a current state using distributed state information by,
    identifying multiple portions of the distributed state information needed for the modeling of the aspect, and identifying multiple of the other characterization systems each having access to one of the identified multiple portions;
    gathering the identified portions of the distributed state information from the identified other characterization systems; and
    generating at least one value for the modeled aspect based on the gathered portions of the distributed state information, so that the user characterization system can interact with other characterization systems in order to exchange and use distributed state information of interest.
  2. 2. The method of claim 1 including:
    determining a need for access to a resource available to one of the other characterization systems executing on another computer;
    requesting the one other characterization system to provide access to the resource; and
    accessing the resource after the one other characterization system provides access to the resource.
  3. 3. The method of claim 2 wherein the resource is processing capabilities of the another computer, wherein the accessing of the resource includes use of the processing capabilities on behalf of the user characterization system, and including receiving an indication of results of the use of the processing capabilities.
  4. 4. The method of claim 2 wherein the resource is an input device of the another computer, and wherein the accessing of the resource includes receiving input information from the input device.
  5. 5. The method of claim 2 wherein the resource is information used during the executing of the one other characterization system, and wherein the accessing of the resource includes retrieving the information.
  6. 6. The method of claim 2 wherein the resource has access to a first portion of the distributed state information, wherein the determined need for access to the resource is to retrieve the first portion, and wherein the accessing of the resource results in the retrieving of the first portion.
  7. 7. The method of claim 1 wherein the distributed state information relates to a current state of a group of users, wherein the identified other characterization systems are user characterization systems each modeling a current state of one of the users in the group, and wherein the modeled aspect is of the current state of the group of users.
  8. 8. The method of claim 1 wherein the other characterization systems are hierarchically organized such that the identified other characterization systems are supervisors each having an associated group of other subordinate characterization systems, wherein the portion of the distributed state information gathered from each of the supervisors includes pieces of distributed state information obtained from the subordinate characterization systems associated with that supervisor, and wherein the modeled aspect is of the current state of the hierarchical organization.
  9. 9. The method of claim 1 wherein each of the other characterization systems is specialized to model a distinct facet of the current state of the user, wherein the aspect of the current state to be modeled includes information about multiple of the facets, and wherein the identified other characterization systems are the specialized characterization systems that model the multiple facets.
  10. 10. The method of claim 1 wherein the user characterization system executes on a computer remote from the wearable computer, and wherein the wearable computer is a thin client device to communicate with the executing user characterization system.
  11. 11. The method of claim 10 wherein the wearable computer includes at least one sensor to supply input information to the SSMs.
  12. 12. The method of claim 10 wherein the wearable computer includes at least one output device to present information to the user.
  13. 13. The method of claim 1 wherein the first other characterization system executes on another computer having a sensor receiving information about the user of the wearable computer, and wherein the received values from the first other characterization system for a state attribute of the modeled current state of the user are based on the received information from the sensor.
  14. 14. The method of claim 1 wherein the second other characterization system executes on another computer with an output device that is perceivable by the user of the wearable computer, and including presenting information to the user on the output device based on the state attribute values sent to the second other characterization system from the intermediary module.
  15. 15. The method of claim 1 wherein each of the state attributes has a local name used by the user characterization system, wherein the receiving of each value for a state attribute from the first other characterization system includes an indication of a first state attribute using a reference for the first state attribute other than the local name of the first state attribute, wherein the receiving of each request for a value of a state attribute from the second other characterization system includes an indication of a second state attribute using a reference for the second state attribute other than the local name of the second state attribute, and including translating the references for the first and second state attributes into the local names of the first and second state attributes before responding.
  16. 16. The method of claim 1 wherein at least some of the SSMs are available to supply values for additional state attributes of a current state other than for the user, and wherein the intermediary module additionally sends values for the additional state attributes to SCMs based on indications from those SCMs of a current desire to receive values for at least one of the additional state attributes.
  17. 17. A method in a first computer for providing information about a current state that is represented with multiple attributes, the method comprising:
    receiving indications of multiple characterization modules, each characterization module executing on a computer to model an aspect of a current state related to that computer;
    receiving an indication of one of the multiple attributes of the represented current state;
    determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute; and
    gathering information about the modeled aspects related to the indicated one attribute from the determined characterization modules so that a value for the indicated one attribute can be generated based on the gathered information.
  18. 18. The method of claim 17 including:
    determining a need for access to a resource available on another computer on which one of the other characterization systems is executing; and
    using the one other characterization system to access the resource.
  19. 19. The method of claim 18 wherein the resource is processing capabilities of the another computer, and wherein accessing of the resource includes use of the processing capabilities.
  20. 20. The method of claim 18 wherein the resource is an input device of the another computer, and wherein accessing of the resource includes receiving input information from the input device.
  21. 21. The method of claim 18 wherein the resource is information used during the executing of the one other characterization system, and wherein accessing of the resource includes retrieving the information.
  22. 22. The method of claim 17 wherein the determined characterization modules each model a current state of a user of the computer on which the characterization module is executing, and wherein the one attribute is related to the current state of the group of the users of the determined characterization modules.
  23. 23. The method of claim 17 wherein the determined characterization modules are hierarchically organized such that some of the characterization modules are supervisors each having an associated group of other subordinate characterization modules, and wherein the one attribute is related to the current state of the hierarchical organization.
  24. 24. The method of claim 17 wherein each of the determined characterization modules is specialized to model a portion of the current state of a single user, and wherein the one attribute is related to information about the user including information for multiple of the portions of the current state.
  25. 25. The method of claim 17 wherein the gathered information from two of the determined characterization modules includes information about a first of the multiple attributes, wherein the two determined characterization modules specify the first attribute with distinct names in their gathered information, and wherein the gathering of the information includes translating the specified names for the first attribute in the gathered information into a common name.
  26. 26. The method of claim 17 wherein the received indication of the one attribute additionally includes an indication of characterization modules, and wherein the determining of the characterization modules include selecting the indicated characterization modules.
  27. 27. The method of claim 17 including:
    determining whether the information gathered from one of the determined characterization modules satisfies a criteria; and
    when it is determined that the gathered information does not satisfy the criteria, obtaining additional information from the one determined characterization module that satisfies the criteria and replacing the gathered information from the one determined characterization module with the obtained additional information.
  28. 28. The method of claim 17 wherein the one attribute represents information about a user of the first computer.
  29. 29. The method of claim 28 wherein the represented information reflects a modeled mental state of the user.
  30. 30. The method of claim 17 wherein the one attribute represents information about the first computer.
  31. 31. The method of claim 17 wherein the one attribute represents information about a physical environment of a user of the first computer.
  32. 32. The method of claim 17 wherein the one attribute represents information about a cyber-environment of a user of the first computer.
  33. 33. The method of claim 17 wherein the one attribute represents a current prediction about a future state.
  34. 34. The method of claim 17 wherein the one attribute represents information about a group of users such that each of the users is a user of a computer on which one of the multiple characterization modules is executing.
  35. 35. The method of claim 17 wherein the one attribute represents information about the group of computers on which the multiple characterization modules are executing.
  36. 36. The method of claim 17 wherein the one attribute represents information about a physical environment common to the computers on which the multiple characterization modules are executing.
  37. 37. The method of claim 17 wherein the one attribute represents information about a cyber-environment common to the computers on which the multiple characterization modules are executing.
  38. 38. The method of claim 17 including, after receiving a request from a client for a value of a second indicated attribute, obtaining information from multiple characterization modules about modeled aspects related to the second attribute and supplying the obtained information to the client.
  39. 39. The method of claim 17 wherein the received indication is from a client, and including generating the value for the indicated one attribute and supplying the generated value to the client.
  40. 40. The method of claim 39 wherein receiving of the supplied value by the client prompts the client to present information to a user.
  41. 41. The method of claim 17 wherein the determining of the multiple characterization modules is based on previously received registration modules from each of the multiple characterization modules that indicate the modeled aspects.
  42. 42. The method of claim 17 wherein security information must be received for a characterization module before any information is accepted from the characterization module.
  43. 43. The method of claim 17 wherein security information must be received for a characterization module before information is supplied to the characterization module.
  44. 44. The method of claim 17 wherein the providing of the information about the represented current state is performed by one of the multiple characterization modules executing on the first computer.
  45. 45. The method of claim 17 wherein the generating of the value is performed by a client after the gathered information is supplied to the client.
  46. 46. A computer-readable medium whose contents cause a computing device to provide information about a current state that is represented with multiple attributes, by:
    receiving indications of multiple characterization modules, each characterization module executing on a computer to model an aspect of a current state related to that computer;
    receiving an indication of one of the multiple attributes of the represented current state;
    determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute;
    obtaining information about the modeled aspects related to the indicated one attribute from the determined characterization modules; and
    supplying the obtained information to a client able to generate a value for the indicated one attribute based on the supplied obtained information.
  47. 47. The computer-readable medium of claim 46 wherein the computer-readable medium is a memory of the computing device.
  48. 48. A computer-readable generated data signal transmitted via a transmission medium, the generated data signal having encoded contents that cause a computer system to provide information about a current state that is represented with multiple attributes, by:
    receiving indications of multiple characterization modules, each characterization module executing on a computer to model an aspect of a current state related to that computer;
    receiving an indication of one of the multiple attributes of the represented current state;
    determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute; and
    gathering information about the modeled aspects related to the indicated one attribute from the determined characterization modules so that a value for the indicated one attribute can be generated based on the gathered information.
  49. 49. A computing device for providing information about a current state that is represented with multiple attributes, comprising:
    an input module that is capable of receiving indications of multiple characterization modules each executing on a computer to model an aspect of a current state related to that computer, and of receiving an indication of one of the multiple attributes of the represented current state;
    an information gatherer module that is capable of determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute and of obtaining information about the modeled aspects related to the indicated one attribute from each of the determined characterization modules; and
    an output module capable of supplying the obtained information from the determined characterization modules to a client able to determine a value for the indicated one attribute based on the obtained information.
  50. 50. A computing device for providing information about a current state that is represented with multiple attributes, comprising:
    means for receiving indications of multiple characterization modules, each characterization module executing on a computer to model an aspect of a current state related to that computer;
    means for receiving an indication of one of the multiple attributes of the represented current state;
    means for determining multiple of the characterization modules whose modeled aspects are related to the indicated one attribute;
    means for obtaining information about the modeled aspects related to the indicated one attribute from each of the determined characterization modules; and
    means for supplying the obtained information from the determined characterization modules to a client able to determine a value for the indicated one attribute based on the obtained information.
  51. 51. A method in a portable computer for providing information about a context that is modeled with multiple context attributes, the method comprising:
    receiving from each of multiple sources an indication of an ability to supply values for at least one of the context attributes of the modeled context; and
    for each of multiple clients,
    receiving an indication of a desire to receive information of interest;
    when at least one source is determined to have the ability to supply the indicated information, retrieving the indicated information from at least one of those sources and sending the retrieved information to the client; and
    when none of the sources have the ability to supply the indicated information,
    determining one or more executing characterization modules from which the indicated information can be obtained and/or one or more resources of other accessible computers with which the indicated information can be obtained;
    obtaining the indicated information from the determined characterization modules and/or with the determined resources; and
    sending the obtained indicated information to the client.
  52. 52. The method of claim 51 wherein the determined resource is processing capabilities of at least one other computer, and wherein the obtaining of the indicated information with the determined resource includes use of the processing capabilities.
  53. 53. The method of claim 51 wherein the determined resource is an input device of at least one other computer, and wherein the obtaining of the indicated information with the determined resource includes receiving input information from the input device.
  54. 54. The method of claim 51 wherein the information obtained from the at least one determined executing characterization module is information used during the executing of the characterization module.
  55. 55. The method of claim 51 wherein at least one of the clients indicating a desire to receive indicated information is a characterization module.
  56. 56. The method of claim 51 wherein the information obtained from the at least one determined executing characterization module is information retrieved by that characterization module from at least one source.
  57. 57. The method of claim 51 wherein the context that is represented is a current context.
  58. 58. The method of claim 51 wherein the context attributes represent information about a user of the portable computer.
  59. 59. The method of claim 51 wherein the context attributes represent information about the first computer.
  60. 60. The method of claim 51 wherein the context attributes represent information about a group of users such that each of the users is a user of a computer on which one of the multiple determined characterization modules is executing.
  61. 61. The method of claim 51 wherein the context attributes represent information about the group of computers on which the multiple determined characterization modules are executing.
  62. 62. The method of claim 51 wherein receiving of the sent obtained information by the client prompts the client to present information to a user.
  63. 63. A computer-readable medium containing instructions that when executed cause a computing device to provide information about a context that is modeled with multiple context attributes, by:
    receiving from each of multiple sources an indication of an ability to supply values for at least one of the context attributes of the modeled context; and
    for each of multiple clients,
    receiving an indication of a desire to receive information of interest;
    when at least one source is determined to have the ability to supply the indicated information, retrieving the indicated information from at least one of those sources and sending the retrieved information to the client; and
    when none of the sources have the ability to supply the indicated information,
    determining one or more executing characterization modules from which the indicated information can be obtained and/or one or more resources of other accessible computers with which the indicated information can be obtained;
    obtaining the indicated information from the determined characterization modules and/or with the determined resources; and
    sending the obtained indicated information to the client.
  64. 64. A portable computer for providing information about a context that is represented with multiple modeled attributes, comprising:
    an attribute mapping module that is capable of receiving from each of multiple sources an indication of a current ability to supply values for at least one of the context attributes of the modeled context; and
    an information supplier module that is capable of receiving an indication of a desire to receive information of interest from a client, of retrieving the indicated information of interest from a source and sending the retrieved information to the client when at least one source has the ability to supply the indicated information of interest, and of, when none of the sources have the ability to supply the indicated information of interest, determining one or more executing characterization modules from which the indicated information of interest can be obtained and/or one or more resources of other accessible computers with which the indicated information of interest can be obtained, obtaining the indicated information of interest from the determined characterization modules and/or with the determined resources, and sending the obtained indicated information of interest to the client.
  65. 65. A computer-implemented method for providing information about a state that is modeled with multiple state attributes, the method comprising:
    receiving an indication of one of the multiple state attributes;
    determining multiple executing characterization modules that each model at least one piece of information related to the indicated one state attribute;
    gathering the modeled pieces of information from the determined characterization modules;
    generating a value for the indicated one attribute based on the gathered information; and
    providing an indication of the generated value of the one state attribute.
US11622954 1998-12-18 2007-01-12 Managing interactions between computer users' context models Abandoned US20070266318A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US09216193 US6466232B1 (en) 1998-12-18 1998-12-18 Method and system for controlling presentation of information to a user based on the user's condition
US09464659 US6513046B1 (en) 1999-12-15 1999-12-15 Storing and recalling information to augment human memories
US19400400 true 2000-04-02 2000-04-02
US19399900 true 2000-04-02 2000-04-02
US09724894 US6801223B1 (en) 1998-12-18 2000-11-28 Managing interactions between computer users' context models
US09894642 US9372555B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US11622954 US20070266318A1 (en) 1998-12-18 2007-01-12 Managing interactions between computer users' context models

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11622954 US20070266318A1 (en) 1998-12-18 2007-01-12 Managing interactions between computer users' context models

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09894642 Continuation US9372555B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models

Publications (1)

Publication Number Publication Date
US20070266318A1 true true US20070266318A1 (en) 2007-11-15

Family

ID=33033286

Family Applications (6)

Application Number Title Priority Date Filing Date
US09724894 Active 2020-05-15 US6801223B1 (en) 1998-12-18 2000-11-28 Managing interactions between computer users' context models
US09894615 Active 2019-10-21 US7058894B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894642 Active 2024-01-24 US9372555B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894281 Active 2019-12-11 US7058893B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894641 Active 2020-07-15 US7089497B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US11622954 Abandoned US20070266318A1 (en) 1998-12-18 2007-01-12 Managing interactions between computer users' context models

Family Applications Before (5)

Application Number Title Priority Date Filing Date
US09724894 Active 2020-05-15 US6801223B1 (en) 1998-12-18 2000-11-28 Managing interactions between computer users' context models
US09894615 Active 2019-10-21 US7058894B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894642 Active 2024-01-24 US9372555B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894281 Active 2019-12-11 US7058893B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models
US09894641 Active 2020-07-15 US7089497B2 (en) 1998-12-18 2001-06-27 Managing interactions between computer users' context models

Country Status (1)

Country Link
US (6) US6801223B1 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070168502A1 (en) * 2000-04-02 2007-07-19 Tangis Corporation Dynamically exchanging computer user's context
US20080313271A1 (en) * 1998-12-18 2008-12-18 Microsoft Corporation Automated reponse to computer users context
US20090320143A1 (en) * 2008-06-24 2009-12-24 Microsoft Corporation Sensor interface
US20090319569A1 (en) * 2008-06-24 2009-12-24 Microsoft Corporation Context platform
US7689919B2 (en) 1998-12-18 2010-03-30 Microsoft Corporation Requesting computer user's context data
US7739607B2 (en) 1998-12-18 2010-06-15 Microsoft Corporation Supplying notifications related to supply and consumption of user context data
US7779015B2 (en) 1998-12-18 2010-08-17 Microsoft Corporation Logging and analyzing context attributes
US7877686B2 (en) 2000-10-16 2011-01-25 Microsoft Corporation Dynamically displaying current status of tasks
US7945859B2 (en) 1998-12-18 2011-05-17 Microsoft Corporation Interface for exchanging context data
US8020104B2 (en) 1998-12-18 2011-09-13 Microsoft Corporation Contextual responses based on automated learning techniques
US8103665B2 (en) 2000-04-02 2012-01-24 Microsoft Corporation Soliciting information based on a computer user's context
US8181113B2 (en) 1998-12-18 2012-05-15 Microsoft Corporation Mediating conflicts in computer users context data
US8225214B2 (en) 1998-12-18 2012-07-17 Microsoft Corporation Supplying enhanced computer user's context data
US8346724B2 (en) 2000-04-02 2013-01-01 Microsoft Corporation Generating and supplying user context data
US9183306B2 (en) 1998-12-18 2015-11-10 Microsoft Technology Licensing, Llc Automated selection of appropriate information based on a computer user's context
US9372555B2 (en) 1998-12-18 2016-06-21 Microsoft Technology Licensing, Llc Managing interactions between computer users' context models
US9443037B2 (en) 1999-12-15 2016-09-13 Microsoft Technology Licensing, Llc Storing and recalling information to augment human memories

Families Citing this family (242)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7080322B2 (en) 1998-12-18 2006-07-18 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7055101B2 (en) * 1998-12-18 2006-05-30 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7107539B2 (en) * 1998-12-18 2006-09-12 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7073129B1 (en) 1998-12-18 2006-07-04 Tangis Corporation Automated selection of appropriate information based on a computer user's context
US6812937B1 (en) * 1998-12-18 2004-11-02 Tangis Corporation Supplying enhanced computer user's context data
US7076737B2 (en) * 1998-12-18 2006-07-11 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US6999955B1 (en) 1999-04-20 2006-02-14 Microsoft Corporation Systems and methods for estimating and integrating measures of human cognitive load into the behavior of computational applications and services
US6434527B1 (en) * 1999-05-17 2002-08-13 Microsoft Corporation Signalling and controlling the status of an automatic speech recognition system for use in handsfree conversational dialogue
CN1159654C (en) * 1999-05-26 2004-07-28 富士通株式会社 Network element management system and method
US7103806B1 (en) 1999-06-04 2006-09-05 Microsoft Corporation System for performing context-sensitive decisions about ideal communication modalities considering information about channel reliability
US6931384B1 (en) 1999-06-04 2005-08-16 Microsoft Corporation System and method providing utility-based decision making about clarification dialog given communicative uncertainty
US6714967B1 (en) 1999-07-30 2004-03-30 Microsoft Corporation Integration of a computer-based message priority system with mobile electronic devices
US7194681B1 (en) * 1999-07-30 2007-03-20 Microsoft Corporation Method for automatically assigning priorities to documents and messages
US6622160B1 (en) * 1999-07-30 2003-09-16 Microsoft Corporation Methods for routing items for communications based on a measure of criticality
US7444383B2 (en) 2000-06-17 2008-10-28 Microsoft Corporation Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information
US7634528B2 (en) 2000-03-16 2009-12-15 Microsoft Corporation Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services
US7243130B2 (en) * 2000-03-16 2007-07-10 Microsoft Corporation Notification platform architecture
US8024415B2 (en) 2001-03-16 2011-09-20 Microsoft Corporation Priorities generation and management
US8086672B2 (en) 2000-06-17 2011-12-27 Microsoft Corporation When-free messaging
US7743340B2 (en) * 2000-03-16 2010-06-22 Microsoft Corporation Positioning and rendering notification heralds based on user's focus of attention and activity
US7249159B1 (en) 2000-03-16 2007-07-24 Microsoft Corporation Notification platform architecture
US8701027B2 (en) 2000-03-16 2014-04-15 Microsoft Corporation Scope user interface for displaying the priorities and properties of multiple informational items
US7565403B2 (en) * 2000-03-16 2009-07-21 Microsoft Corporation Use of a bulk-email filter within a system for classifying messages for urgency or importance
US7457879B2 (en) * 2003-04-01 2008-11-25 Microsoft Corporation Notification platform architecture
US6938024B1 (en) * 2000-05-04 2005-08-30 Microsoft Corporation Transmitting information given constrained resources
US6847924B1 (en) * 2000-06-19 2005-01-25 Ncr Corporation Method and system for aggregating data distribution models
US7844666B2 (en) 2000-12-12 2010-11-30 Microsoft Corporation Controls and displays for acquiring preferences, inspecting behavior, and guiding the learning and decision policies of an adaptive communications prioritization and routing system
DE10100568A1 (en) * 2001-01-09 2002-07-11 Philips Corp Intellectual Pty Business contacts via the Internet
US6745193B1 (en) 2001-01-25 2004-06-01 Microsoft Corporation System and method for defining, refining, and personalizing communications policies in a notification platform
US7581230B2 (en) * 2001-02-06 2009-08-25 Siebel Systems, Inc. Adaptive communication application programming interface
US6901398B1 (en) 2001-02-12 2005-05-31 Microsoft Corporation System and method for constructing and personalizing a universal information classifier
EP1373143A1 (en) * 2001-02-27 2004-01-02 Peder Holmbom An apparatus and a method for the disinfection of water for water consumption units designed for health or dental care purposes
US7194428B2 (en) * 2001-03-02 2007-03-20 Accenture Global Services Gmbh Online wardrobe
US7302634B2 (en) 2001-03-14 2007-11-27 Microsoft Corporation Schema-based services for identity-based data access
US7024662B2 (en) 2001-03-14 2006-04-04 Microsoft Corporation Executing dynamically assigned functions while providing services
US6988132B2 (en) * 2001-03-15 2006-01-17 Microsoft Corporation System and method for identifying and establishing preferred modalities or channels for communications based on participants' preferences and contexts
US7389351B2 (en) * 2001-03-15 2008-06-17 Microsoft Corporation System and method for identifying and establishing preferred modalities or channels for communications based on participants' preferences and contexts
US7330895B1 (en) 2001-03-15 2008-02-12 Microsoft Corporation Representation, decision models, and user interface for encoding managing preferences, and performing automated decision making about the timing and modalities of interpersonal communications
US7251696B1 (en) 2001-03-15 2007-07-31 Microsoft Corporation System and methods enabling a mix of human and automated initiatives in the control of communication policies
US7512940B2 (en) * 2001-03-29 2009-03-31 Microsoft Corporation Methods and apparatus for downloading and/or distributing information and/or software resources based on expected utility
US7315616B2 (en) * 2001-03-31 2008-01-01 Siebel Systems, Inc. System and method for maintaining real-time agent information for multi-channel communication queuing
US8601492B2 (en) * 2001-03-31 2013-12-03 Siebel Systems, Inc. User interface for multi-channel communication
US20030206192A1 (en) * 2001-03-31 2003-11-06 Mingte Chen Asynchronous message push to web browser
US7757250B1 (en) 2001-04-04 2010-07-13 Microsoft Corporation Time-centric training, inference and user interface for personalized media program guides
US6947935B1 (en) * 2001-04-04 2005-09-20 Microsoft Corporation Training, inference and user interface for guiding the caching of media content on local stores
US7017152B2 (en) * 2001-04-06 2006-03-21 Appmind Software Ab Method of detecting lost objects in a software system
US7039642B1 (en) 2001-05-04 2006-05-02 Microsoft Corporation Decision-theoretic methods for identifying relevant substructures of a hierarchical file structure to enhance the efficiency of document access, browsing, and storage
US7107254B1 (en) 2001-05-07 2006-09-12 Microsoft Corporation Probablistic models and methods for combining multiple content classifiers
US7089226B1 (en) 2001-06-28 2006-08-08 Microsoft Corporation System, representation, and method providing multilevel information retrieval with clarification dialog
US7409423B2 (en) * 2001-06-28 2008-08-05 Horvitz Eric J Methods for and applications of learning and inferring the periods of time until people are available or unavailable for different forms of communication, collaboration, and information access
US7043506B1 (en) * 2001-06-28 2006-05-09 Microsoft Corporation Utility-based archiving
US7233933B2 (en) * 2001-06-28 2007-06-19 Microsoft Corporation Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability
US7689521B2 (en) * 2001-06-28 2010-03-30 Microsoft Corporation Continuous time bayesian network models for predicting users' presence, activities, and component usage
US7493369B2 (en) * 2001-06-28 2009-02-17 Microsoft Corporation Composable presence and availability services
US7519529B1 (en) 2001-06-29 2009-04-14 Microsoft Corporation System and methods for inferring informational goals and preferred level of detail of results in response to questions posed to an automated information-retrieval or question-answering service
US7409335B1 (en) 2001-06-29 2008-08-05 Microsoft Corporation Inferring informational goals and preferred level of detail of answers based on application being employed by the user
US8091042B2 (en) 2001-11-15 2012-01-03 Siebel Systems, Inc. Apparatus and method for displaying selectable icons in a toolbar for a user interface
FR2832577B1 (en) * 2001-11-16 2005-03-18 Cit Alcatel Adaptive Acquisition of data for networks and services management system
US7644144B1 (en) 2001-12-21 2010-01-05 Microsoft Corporation Methods, tools, and interfaces for the dynamic assignment of people to groups to enable enhanced communication and collaboration
US7203909B1 (en) 2002-04-04 2007-04-10 Microsoft Corporation System and methods for constructing personalized context-sensitive portal pages or views by analyzing patterns of users' information access activities
US20030212761A1 (en) * 2002-05-10 2003-11-13 Microsoft Corporation Process kernel
US20030217142A1 (en) 2002-05-15 2003-11-20 Microsoft Corporation Method and system for supporting the communication of presence information regarding one or more telephony devices
US20030217098A1 (en) 2002-05-15 2003-11-20 Microsoft Corporation Method and system for supporting the communication of presence information regarding one or more telephony devices
US7203635B2 (en) * 2002-06-27 2007-04-10 Microsoft Corporation Layered models for context awareness
US9886309B2 (en) 2002-06-28 2018-02-06 Microsoft Technology Licensing, Llc Identity-based distributed computing for device resources
US7870240B1 (en) 2002-06-28 2011-01-11 Microsoft Corporation Metadata schema for interpersonal communications management systems
US7069259B2 (en) * 2002-06-28 2006-06-27 Microsoft Corporation Multi-attribute specification of preferences about people, priorities and privacy for guiding messaging and communications
JP4298407B2 (en) * 2002-09-30 2009-07-22 キヤノン株式会社 How the video synthesizing apparatus and a video synthesis
US20040153445A1 (en) * 2003-02-04 2004-08-05 Horvitz Eric J. Systems and methods for constructing and using models of memorability in computing and communications applications
US8225224B1 (en) 2003-02-25 2012-07-17 Microsoft Corporation Computer desktop use via scaling of displayed objects with shifts to the periphery
US8230359B2 (en) * 2003-02-25 2012-07-24 Microsoft Corporation System and method that facilitates computer desktop use via scaling of displayed objects with shifts to the periphery
US7536650B1 (en) 2003-02-25 2009-05-19 Robertson George G System and method that facilitates computer desktop use via scaling of displayed objects with shifts to the periphery
US7793233B1 (en) * 2003-03-12 2010-09-07 Microsoft Corporation System and method for customizing note flags
US7774799B1 (en) 2003-03-26 2010-08-10 Microsoft Corporation System and method for linking page content with a media file and displaying the links
WO2004088514A1 (en) * 2003-03-28 2004-10-14 Sony Corporation Information providing device, method, and information providing system
US6992625B1 (en) * 2003-04-25 2006-01-31 Microsoft Corporation Calibration of a device location measurement system that utilizes wireless signal strengths
EP1618480A2 (en) * 2003-04-29 2006-01-25 University Of Strathclyde Monitoring software
US7225187B2 (en) * 2003-06-26 2007-05-29 Microsoft Corporation Systems and methods for performing background queries from content and activity
US7162473B2 (en) * 2003-06-26 2007-01-09 Microsoft Corporation Method and system for usage analyzer that determines user accessed sources, indexes data subsets, and associated metadata, processing implicit queries based on potential interest to users
US20040267746A1 (en) * 2003-06-26 2004-12-30 Cezary Marcjan User interface for controlling access to computer objects
US8346587B2 (en) * 2003-06-30 2013-01-01 Microsoft Corporation Models and methods for reducing visual complexity and search effort via ideal information abstraction, hiding, and sequencing
US20040264677A1 (en) * 2003-06-30 2004-12-30 Horvitz Eric J. Ideal transfer of call handling from automated systems to human operators based on forecasts of automation efficacy and operator load
US7444598B2 (en) * 2003-06-30 2008-10-28 Microsoft Corporation Exploded views for providing rich regularized geometric transformations and interaction models on content for viewing, previewing, and interacting with documents, projects, and tasks
US7250907B2 (en) * 2003-06-30 2007-07-31 Microsoft Corporation System and methods for determining the location dynamics of a portable computing device
US20050108366A1 (en) * 2003-07-02 2005-05-19 International Business Machines Corporation Administering devices with domain state objects
US7202816B2 (en) * 2003-07-22 2007-04-10 Microsoft Corporation Utilization of the approximate location of a device determined from ambient signals
US7319877B2 (en) * 2003-07-22 2008-01-15 Microsoft Corporation Methods for determining the approximate location of a device from ambient signals
US7738881B2 (en) * 2003-07-22 2010-06-15 Microsoft Corporation Systems for determining the approximate location of a device from ambient signals
US7454393B2 (en) * 2003-08-06 2008-11-18 Microsoft Corporation Cost-benefit approach to automatically composing answers to questions by extracting information from large unstructured corpora
US20050084082A1 (en) * 2003-10-15 2005-04-21 Microsoft Corporation Designs, interfaces, and policies for systems that enhance communication and minimize disruption by encoding preferences and situations
US7831679B2 (en) * 2003-10-15 2010-11-09 Microsoft Corporation Guiding sensing and preferences for context-sensitive services
US7774349B2 (en) 2003-12-11 2010-08-10 Microsoft Corporation Statistical models and methods to support the personalization of applications and services via consideration of preference encodings of a community of users
US20050165631A1 (en) * 2004-01-28 2005-07-28 Microsoft Corporation Time management representations and automation for allocating time to projects and meetings within an online calendaring system
US7293019B2 (en) * 2004-03-02 2007-11-06 Microsoft Corporation Principles and methods for personalizing newsfeeds via an analysis of information novelty and dynamics
US7327349B2 (en) * 2004-03-02 2008-02-05 Microsoft Corporation Advanced navigation techniques for portable devices
US7908663B2 (en) 2004-04-20 2011-03-15 Microsoft Corporation Abstractions and automation for enhanced sharing and collaboration
US7664249B2 (en) * 2004-06-30 2010-02-16 Microsoft Corporation Methods and interfaces for probing and understanding behaviors of alerting and filtering systems based on models and simulation from logs
US20060012183A1 (en) * 2004-07-19 2006-01-19 David Marchiori Rail car door opener
US7788589B2 (en) 2004-09-30 2010-08-31 Microsoft Corporation Method and system for improved electronic task flagging and management
US7712049B2 (en) 2004-09-30 2010-05-04 Microsoft Corporation Two-dimensional radial user interface for computer software applications
US20060074883A1 (en) * 2004-10-05 2006-04-06 Microsoft Corporation Systems, methods, and interfaces for providing personalized search and information access
US7831532B2 (en) * 2004-11-16 2010-11-09 Microsoft Corporation Precomputation and transmission of time-dependent information for varying or uncertain receipt times
US7698055B2 (en) * 2004-11-16 2010-04-13 Microsoft Corporation Traffic forecasting employing modeling and analysis of probabilistic interdependencies and contextual data
US7519564B2 (en) 2004-11-16 2009-04-14 Microsoft Corporation Building and using predictive models of current and future surprises
US7327245B2 (en) * 2004-11-22 2008-02-05 Microsoft Corporation Sensing and analysis of ambient contextual signals for discriminating between indoor and outdoor locations
US7809569B2 (en) * 2004-12-22 2010-10-05 Enterprise Integration Group, Inc. Turn-taking confidence
WO2006072052A3 (en) * 2004-12-31 2006-12-28 Gene Anderson System for protecting identity in a network environment
US7689615B2 (en) * 2005-02-25 2010-03-30 Microsoft Corporation Ranking results using multiple nested ranking
US7885817B2 (en) 2005-03-08 2011-02-08 Microsoft Corporation Easy generation and automatic training of spoken dialog systems using text-to-speech
US20060206333A1 (en) * 2005-03-08 2006-09-14 Microsoft Corporation Speaker-dependent dialog adaptation
US7734471B2 (en) * 2005-03-08 2010-06-08 Microsoft Corporation Online learning for dialog systems
US7707131B2 (en) * 2005-03-08 2010-04-27 Microsoft Corporation Thompson strategy based online reinforcement learning system for action selection
US20070011109A1 (en) * 2005-06-23 2007-01-11 Microsoft Corporation Immortal information storage and access platform
US7991607B2 (en) * 2005-06-27 2011-08-02 Microsoft Corporation Translation and capture architecture for output of conversational utterances
US7643985B2 (en) * 2005-06-27 2010-01-05 Microsoft Corporation Context-sensitive communication and translation methods for enhanced interactions and understanding among speakers of different languages
US7391427B2 (en) * 2005-06-28 2008-06-24 Zink Imaging, Llc Parametric programmable thermal printer
US7460884B2 (en) * 2005-06-29 2008-12-02 Microsoft Corporation Data buddy
US8079079B2 (en) * 2005-06-29 2011-12-13 Microsoft Corporation Multimodal authentication
US7694214B2 (en) * 2005-06-29 2010-04-06 Microsoft Corporation Multimodal note taking, annotation, and gaming
US20070004969A1 (en) * 2005-06-29 2007-01-04 Microsoft Corporation Health monitor
US7647171B2 (en) * 2005-06-29 2010-01-12 Microsoft Corporation Learning, storing, analyzing, and reasoning about the loss of location-identifying signals
US7428521B2 (en) * 2005-06-29 2008-09-23 Microsoft Corporation Precomputation of context-sensitive policies for automated inquiry and action under uncertainty
US7693817B2 (en) * 2005-06-29 2010-04-06 Microsoft Corporation Sensing, storing, indexing, and retrieving data leveraging measures of user activity, attention, and interest
US20070005363A1 (en) * 2005-06-29 2007-01-04 Microsoft Corporation Location aware multi-modal multi-lingual device
US7529683B2 (en) * 2005-06-29 2009-05-05 Microsoft Corporation Principals and methods for balancing the timeliness of communications and information delivery with the expected cost of interruption via deferral policies
US20070005754A1 (en) * 2005-06-30 2007-01-04 Microsoft Corporation Systems and methods for triaging attention for providing awareness of communications session activity
US7925995B2 (en) * 2005-06-30 2011-04-12 Microsoft Corporation Integration of location logs, GPS signals, and spatial resources for identifying user activities, goals, and context
US7646755B2 (en) * 2005-06-30 2010-01-12 Microsoft Corporation Seamless integration of portable computing devices and desktop computers
US20070005646A1 (en) * 2005-06-30 2007-01-04 Microsoft Corporation Analysis of topic dynamics of web search
US20070050252A1 (en) * 2005-08-29 2007-03-01 Microsoft Corporation Preview pane for ads
US20070050253A1 (en) * 2005-08-29 2007-03-01 Microsoft Corporation Automatically generating content for presenting in a preview pane for ADS
US20070050251A1 (en) * 2005-08-29 2007-03-01 Microsoft Corporation Monetizing a preview pane for ads
US8024112B2 (en) * 2005-09-29 2011-09-20 Microsoft Corporation Methods for predicting destinations from partial trajectories employing open-and closed-world modeling methods
US7319908B2 (en) * 2005-10-28 2008-01-15 Microsoft Corporation Multi-modal device power/mode management
US7467353B2 (en) * 2005-10-28 2008-12-16 Microsoft Corporation Aggregation of multi-modal devices
US7778632B2 (en) * 2005-10-28 2010-08-17 Microsoft Corporation Multi-modal device capable of automated actions
US20070100704A1 (en) * 2005-10-28 2007-05-03 Microsoft Corporation Shopping assistant
US20070112906A1 (en) * 2005-11-15 2007-05-17 Microsoft Corporation Infrastructure for multi-modal multilingual communications devices
US20070117557A1 (en) * 2005-11-21 2007-05-24 Conopco Inc, D/B/A Unilever Parametric user profiling
US20070136222A1 (en) * 2005-12-09 2007-06-14 Microsoft Corporation Question and answer architecture for reasoning and clarifying intentions, goals, and needs from contextual clues and content
US20070136068A1 (en) * 2005-12-09 2007-06-14 Microsoft Corporation Multimodal multilingual devices and applications for enhanced goal-interpretation and translation for service providers
US20070150512A1 (en) * 2005-12-15 2007-06-28 Microsoft Corporation Collaborative meeting assistant
US7797638B2 (en) 2006-01-05 2010-09-14 Microsoft Corporation Application of metadata to documents and document objects via a software application user interface
US7747557B2 (en) 2006-01-05 2010-06-29 Microsoft Corporation Application of metadata to documents and document objects via an operating system user interface
US7617164B2 (en) * 2006-03-17 2009-11-10 Microsoft Corporation Efficiency of training for ranking systems based on pairwise training with aggregated gradients
US20070245223A1 (en) * 2006-04-17 2007-10-18 Microsoft Corporation Synchronizing multimedia mobile notes
US20070245229A1 (en) * 2006-04-17 2007-10-18 Microsoft Corporation User experience for multimedia mobile note taking
US7761464B2 (en) * 2006-06-19 2010-07-20 Microsoft Corporation Diversifying search results for improved search and personalization
US7610151B2 (en) * 2006-06-27 2009-10-27 Microsoft Corporation Collaborative route planning for generating personalized and context-sensitive routing recommendations
US20080005095A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Validation of computer responses
US7739221B2 (en) * 2006-06-28 2010-06-15 Microsoft Corporation Visual and multi-dimensional search
US9396269B2 (en) * 2006-06-28 2016-07-19 Microsoft Technology Licensing, Llc Search engine that identifies and uses social networks in communications, retrieval, and electronic commerce
US20080005223A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Reputation data for entities and data processing
US20080005074A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Search over designated content
US20080005068A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Context-based search, retrieval, and awareness
US20080005108A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Message mining to enhance ranking of documents for retrieval
US20080004948A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Auctioning for video and audio advertising
US9141704B2 (en) * 2006-06-28 2015-09-22 Microsoft Technology Licensing, Llc Data management in social networks
US8788517B2 (en) * 2006-06-28 2014-07-22 Microsoft Corporation Intelligently guiding search based on user dialog
US20080005104A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Localized marketing
US20080005069A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Entity-specific search model
US7984169B2 (en) * 2006-06-28 2011-07-19 Microsoft Corporation Anonymous and secure network-based interaction
US20080005067A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Context-based search, retrieval, and awareness
US8874592B2 (en) 2006-06-28 2014-10-28 Microsoft Corporation Search guided by location and context
US7822762B2 (en) * 2006-06-28 2010-10-26 Microsoft Corporation Entity-specific search model
US20080004990A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Virtual spot market for advertisements
US7917514B2 (en) * 2006-06-28 2011-03-29 Microsoft Corporation Visual and multi-dimensional search
US20080004884A1 (en) * 2006-06-29 2008-01-03 Microsoft Corporation Employment of offline behavior to display online content
US20080004951A1 (en) * 2006-06-29 2008-01-03 Microsoft Corporation Web-based targeted advertising in a brick-and-mortar retail establishment using online customer information
US20080005079A1 (en) * 2006-06-29 2008-01-03 Microsoft Corporation Scenario-based search
US7552862B2 (en) * 2006-06-29 2009-06-30 Microsoft Corporation User-controlled profile sharing
US20080005313A1 (en) * 2006-06-29 2008-01-03 Microsoft Corporation Using offline activity to enhance online searching
US20080005047A1 (en) * 2006-06-29 2008-01-03 Microsoft Corporation Scenario-based search
US8244240B2 (en) * 2006-06-29 2012-08-14 Microsoft Corporation Queries as data for revising and extending a sensor-based location service
US7997485B2 (en) 2006-06-29 2011-08-16 Microsoft Corporation Content presentation based on user preferences
US8725567B2 (en) * 2006-06-29 2014-05-13 Microsoft Corporation Targeted advertising in brick-and-mortar establishments
US8626136B2 (en) * 2006-06-29 2014-01-07 Microsoft Corporation Architecture for user- and context-specific prefetching and caching of information on portable devices
US7873620B2 (en) * 2006-06-29 2011-01-18 Microsoft Corporation Desktop search from mobile device
US8126641B2 (en) 2006-06-30 2012-02-28 Microsoft Corporation Route planning with contingencies
US7706964B2 (en) * 2006-06-30 2010-04-27 Microsoft Corporation Inferring road speeds for context-sensitive routing
US7617042B2 (en) 2006-06-30 2009-11-10 Microsoft Corporation Computing and harnessing inferences about the timing, duration, and nature of motion and cessation of motion with applications to mobile computing and communications
US20080004954A1 (en) * 2006-06-30 2008-01-03 Microsoft Corporation Methods and architecture for performing client-side directed marketing with caching and local analytics for enhanced privacy and minimal disruption
US8112755B2 (en) * 2006-06-30 2012-02-07 Microsoft Corporation Reducing latencies in computing systems using probabilistic and/or decision-theoretic reasoning under scarce memory resources
US7739040B2 (en) 2006-06-30 2010-06-15 Microsoft Corporation Computation of travel routes, durations, and plans over multiple contexts
US7797267B2 (en) * 2006-06-30 2010-09-14 Microsoft Corporation Methods and architecture for learning and reasoning in support of context-sensitive reminding, informing, and service facilitation
US20100220613A1 (en) * 2006-09-05 2010-09-02 Jozef Henricus Petrus Hendriks Network node optimization with triggered expressions
JP4963129B2 (en) * 2006-09-11 2012-06-27 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Maschines Corporation Method of recommending a shortcut in order to fix to facilitate navigation in the navigation topology
US7707518B2 (en) 2006-11-13 2010-04-27 Microsoft Corporation Linking information
US7761785B2 (en) 2006-11-13 2010-07-20 Microsoft Corporation Providing resilient links
US8949769B2 (en) * 2007-02-23 2015-02-03 Microsoft Corporation Spatial layout of hierarchical shared resources
US7711716B2 (en) * 2007-03-06 2010-05-04 Microsoft Corporation Optimizations for a background database consistency check
US20080249667A1 (en) * 2007-04-09 2008-10-09 Microsoft Corporation Learning and reasoning to enhance energy efficiency in transportation systems
US7970721B2 (en) * 2007-06-15 2011-06-28 Microsoft Corporation Learning and reasoning from web projections
US7539659B2 (en) * 2007-06-15 2009-05-26 Microsoft Corporation Multidimensional timeline browsers for broadcast media
US8984133B2 (en) 2007-06-19 2015-03-17 The Invention Science Fund I, Llc Providing treatment-indicative feedback dependent on putative content treatment
US8682982B2 (en) 2007-06-19 2014-03-25 The Invention Science Fund I, Llc Preliminary destination-dependent evaluation of message content
US7979252B2 (en) * 2007-06-21 2011-07-12 Microsoft Corporation Selective sampling of user state based on expected utility
US20080320087A1 (en) * 2007-06-22 2008-12-25 Microsoft Corporation Swarm sensing and actuating
US7912637B2 (en) * 2007-06-25 2011-03-22 Microsoft Corporation Landmark-based routing
US20080319658A1 (en) * 2007-06-25 2008-12-25 Microsoft Corporation Landmark-based routing
US20080319660A1 (en) * 2007-06-25 2008-12-25 Microsoft Corporation Landmark-based routing
US7991718B2 (en) * 2007-06-28 2011-08-02 Microsoft Corporation Method and apparatus for generating an inference about a destination of a trip using a combination of open-world modeling and closed world modeling
US7696866B2 (en) * 2007-06-28 2010-04-13 Microsoft Corporation Learning and reasoning about the context-sensitive reliability of sensors
US8244660B2 (en) 2007-06-28 2012-08-14 Microsoft Corporation Open-world modeling
US7673088B2 (en) * 2007-06-29 2010-03-02 Microsoft Corporation Multi-tasking interference model
US7948400B2 (en) * 2007-06-29 2011-05-24 Microsoft Corporation Predictive models of road reliability for traffic sensor configuration and routing
US8254393B2 (en) * 2007-06-29 2012-08-28 Microsoft Corporation Harnessing predictive models of durations of channel availability for enhanced opportunistic allocation of radio spectrum
US8082225B2 (en) 2007-08-31 2011-12-20 The Invention Science Fund I, Llc Using destination-dependent criteria to guide data transmission decisions
US8065404B2 (en) 2007-08-31 2011-11-22 The Invention Science Fund I, Llc Layering destination-dependent content handling guidance
US8088004B2 (en) * 2007-10-16 2012-01-03 International Business Machines Corporation System and method for implementing environmentally-sensitive simulations on a data processing system
US9374242B2 (en) 2007-11-08 2016-06-21 Invention Science Fund I, Llc Using evaluations of tentative message content
US7930389B2 (en) 2007-11-20 2011-04-19 The Invention Science Fund I, Llc Adaptive filtering of annotated messages or the like
US8140335B2 (en) * 2007-12-11 2012-03-20 Voicebox Technologies, Inc. System and method for providing a natural language voice user interface in an integrated voice navigation services environment
US8799814B1 (en) * 2008-02-22 2014-08-05 Amazon Technologies, Inc. Automated targeting of content components
EP3249893A1 (en) * 2008-06-03 2017-11-29 Whirlpool Corporation Appliance development toolkit
US9704161B1 (en) 2008-06-27 2017-07-11 Amazon Technologies, Inc. Providing information without authentication
US8788945B1 (en) 2008-06-30 2014-07-22 Amazon Technologies, Inc. Automatic approval
US9449319B1 (en) 2008-06-30 2016-09-20 Amazon Technologies, Inc. Conducting transactions with dynamic passwords
US9846049B2 (en) * 2008-07-09 2017-12-19 Microsoft Technology Licensing, Llc Route prediction
US20100088143A1 (en) * 2008-10-07 2010-04-08 Microsoft Corporation Calendar event scheduling
US8346800B2 (en) * 2009-04-02 2013-01-01 Microsoft Corporation Content-based information retrieval
US8661030B2 (en) 2009-04-09 2014-02-25 Microsoft Corporation Re-ranking top search results
US8073993B2 (en) * 2009-04-20 2011-12-06 International Business Machines Corporation Management of redundant physical data paths in a computing system
US8122166B2 (en) 2009-04-20 2012-02-21 International Business Machines Corporation Management of redundant physical data paths in a computing system
US9305263B2 (en) 2010-06-30 2016-04-05 Microsoft Technology Licensing, Llc Combining human and machine intelligence to solve tasks with crowd sourcing
US8565783B2 (en) 2010-11-24 2013-10-22 Microsoft Corporation Path progression matching for indoor positioning systems
US9589254B2 (en) 2010-12-08 2017-03-07 Microsoft Technology Licensing, Llc Using e-mail message characteristics for prioritization
US20120198323A1 (en) * 2011-01-28 2012-08-02 Sap Ag Flexible dual data attribute
US8781452B2 (en) 2011-02-21 2014-07-15 Motorola Mobility Llc Wireless devices and methods of operating wireless devices based on the presence of another person
US9163952B2 (en) 2011-04-15 2015-10-20 Microsoft Technology Licensing, Llc Suggestive mapping
US8938403B2 (en) * 2011-05-11 2015-01-20 Ari M. Frank Computing token-dependent affective response baseline levels utilizing a database storing affective responses
US8981995B2 (en) 2011-06-03 2015-03-17 Microsoft Technology Licensing, Llc. Low accuracy positional data by detecting improbable samples
US9470529B2 (en) 2011-07-14 2016-10-18 Microsoft Technology Licensing, Llc Activating and deactivating sensors for dead reckoning
US9464903B2 (en) 2011-07-14 2016-10-11 Microsoft Technology Licensing, Llc Crowd sourcing based on dead reckoning
US8538686B2 (en) 2011-09-09 2013-09-17 Microsoft Corporation Transport-dependent prediction of destinations
US9429657B2 (en) 2011-12-14 2016-08-30 Microsoft Technology Licensing, Llc Power efficient activation of a device movement sensor module
US8775337B2 (en) 2011-12-19 2014-07-08 Microsoft Corporation Virtual sensor development
US9756571B2 (en) 2012-02-28 2017-09-05 Microsoft Technology Licensing, Llc Energy efficient maximization of network connectivity
US9817125B2 (en) 2012-09-07 2017-11-14 Microsoft Technology Licensing, Llc Estimating and predicting structures proximate to a mobile device
US8856948B1 (en) * 2013-12-23 2014-10-07 Google Inc. Displaying private information on personal devices
KR20150080868A (en) * 2014-01-02 2015-07-10 삼성전자주식회사 method and apparatus for controlling electronic devices in proximity
US8811951B1 (en) 2014-01-07 2014-08-19 Google Inc. Managing display of private information

Citations (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5133075A (en) * 1988-12-19 1992-07-21 Hewlett-Packard Company Method of monitoring changes in attribute values of object in an object-oriented database
US5237684A (en) * 1991-08-12 1993-08-17 International Business Machines Corporation Customized and versatile event monitor within event management services of a computer system
US5339395A (en) * 1992-09-17 1994-08-16 Delco Electronics Corporation Interface circuit for interfacing a peripheral device with a microprocessor operating in either a synchronous or an asynchronous mode
US5398021A (en) * 1993-07-19 1995-03-14 Motorola, Inc. Reliable information service message delivery system
US5513646A (en) * 1992-11-09 1996-05-07 I Am Fine, Inc. Personal security monitoring system and method
US5522024A (en) * 1990-03-30 1996-05-28 International Business Machines Corporation Programming environment system for customizing a program application based upon user input
US5592664A (en) * 1991-07-29 1997-01-07 Borland International Inc. Database server system with methods for alerting clients of occurrence of database server events of interest to the clients
US5738102A (en) * 1994-03-31 1998-04-14 Lemelson; Jerome H. Patient monitoring system
US5742279A (en) * 1993-11-08 1998-04-21 Matsushita Electrical Co., Ltd. Input/display integrated information processing device
US5754938A (en) * 1994-11-29 1998-05-19 Herz; Frederick S. M. Pseudonymous server for system for customized electronic identification of desirable objects
US5769085A (en) * 1993-01-06 1998-06-23 Mitsubishi Jidosha Kogyo Kabushiki Kaisha Apparatus for detecting awareness of a vehicle driver and method thereof
US5787234A (en) * 1994-06-22 1998-07-28 Molloy; Bruce G. System and method for representing and retrieving knowledge in an adaptive cognitive network
US5796952A (en) * 1997-03-21 1998-08-18 Dot Com Development, Inc. Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database
US5867171A (en) * 1993-05-25 1999-02-02 Casio Computer Co., Ltd. Face image data processing devices
US5930501A (en) * 1996-09-20 1999-07-27 Neil; John M. Pictorial user interface for establishing time of day and geographical or environmental context on a computer display or other monitor
US5942986A (en) * 1995-08-09 1999-08-24 Cedars-Sinai Medical Center System and method for automatic critical event notification
US5945988A (en) * 1996-06-06 1999-08-31 Intel Corporation Method and apparatus for automatically determining and dynamically updating user preferences in an entertainment system
US6031455A (en) * 1998-02-09 2000-02-29 Motorola, Inc. Method and apparatus for monitoring environmental conditions in a communication system
US6035264A (en) * 1996-11-26 2000-03-07 Global Maintech, Inc. Electronic control system and method for externally controlling process in a computer system with a script language
US6041365A (en) * 1985-10-29 2000-03-21 Kleinerman; Aurel Apparatus and method for high performance remote application gateway servers
US6044415A (en) * 1998-02-27 2000-03-28 Intel Corporation System for transferring I/O data between an I/O device and an application program's memory in accordance with a request directly over a virtual connection
US6061610A (en) * 1997-10-31 2000-05-09 Nissan Technical Center North America, Inc. Method and apparatus for determining workload of motor vehicle driver
US6061660A (en) * 1997-10-20 2000-05-09 York Eggleston System and method for incentive programs and award fulfillment
US6085086A (en) * 1995-08-22 2000-07-04 Lucent Technologies Inc. Network-based migrating user agent for personal communication services
US6105063A (en) * 1998-05-05 2000-08-15 International Business Machines Corp. Client-server system for maintaining application preferences in a hierarchical data structure according to user and user group or terminal and terminal group contexts
US6112246A (en) * 1998-10-22 2000-08-29 Horbal; Mark T. System and method for accessing information from a remote device and providing the information to a client workstation
US6198394B1 (en) * 1996-12-05 2001-03-06 Stephen C. Jacobsen System for remote monitoring of personnel
US6199102B1 (en) * 1997-08-26 2001-03-06 Christopher Alan Cobb Method and system for filtering electronic messages
US6199099B1 (en) * 1999-03-05 2001-03-06 Ac Properties B.V. System, method and article of manufacture for a mobile communication network utilizing a distributed communication network
US6263268B1 (en) * 1997-08-26 2001-07-17 Transcontech Corporation System and method for providing mobile automotive telemetry
US6282537B1 (en) * 1996-05-30 2001-08-28 Massachusetts Institute Of Technology Query and retrieving semi-structured data from heterogeneous sources by translating structured queries
US6353398B1 (en) * 1999-10-22 2002-03-05 Himanshu S. Amin System for dynamically pushing information to a user utilizing global positioning system
US6353823B1 (en) * 1999-03-08 2002-03-05 Intel Corporation Method and system for using associative metadata
US6356905B1 (en) * 1999-03-05 2002-03-12 Accenture Llp System, method and article of manufacture for mobile communication utilizing an interface support framework
US6385589B1 (en) * 1998-12-30 2002-05-07 Pharmacia Corporation System for monitoring and managing the health care of a patient population
US6401085B1 (en) * 1999-03-05 2002-06-04 Accenture Llp Mobile communication and computing system and method
US6421700B1 (en) * 1995-12-22 2002-07-16 Xerox Corporation Method and system for work process support using independent system and user states
US6438618B1 (en) * 1998-12-16 2002-08-20 Intel Corporation Method and device for filtering events in an event notification service
US6529723B1 (en) * 1999-07-06 2003-03-04 Televoke, Inc. Automated user notification system
US6546425B1 (en) * 1998-10-09 2003-04-08 Netmotion Wireless, Inc. Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US6546005B1 (en) * 1997-03-25 2003-04-08 At&T Corp. Active user registry
US6553336B1 (en) * 1999-06-25 2003-04-22 Telemonitor, Inc. Smart remote monitoring system and method
US6672506B2 (en) * 1996-01-25 2004-01-06 Symbol Technologies, Inc. Statistical sampling security methodology for self-scanning checkout system
US6704722B2 (en) * 1999-11-17 2004-03-09 Xerox Corporation Systems and methods for performing crawl searches and index searches
US6704785B1 (en) * 1997-03-17 2004-03-09 Vitria Technology, Inc. Event driven communication system
US6712615B2 (en) * 2000-05-22 2004-03-30 Rolf John Martin High-precision cognitive performance test battery suitable for internet and non-internet use
US6718332B1 (en) * 1999-01-04 2004-04-06 Cisco Technology, Inc. Seamless importation of data
US6738975B1 (en) * 1998-11-18 2004-05-18 Software Ag, Inc. Extensible distributed enterprise application integration system
USD494584S1 (en) * 2002-12-05 2004-08-17 Symbol Technologies, Inc. Mobile companion
US6837436B2 (en) * 1996-09-05 2005-01-04 Symbol Technologies, Inc. Consumer interactive shopping system
US6850252B1 (en) * 1999-10-05 2005-02-01 Steven M. Hoffberg Intelligent electronic appliance system and method
US20050066282A1 (en) * 1998-12-18 2005-03-24 Tangis Corporation Requesting computer user's context data
US20050086243A1 (en) * 1998-12-18 2005-04-21 Tangis Corporation Logging and analyzing computer user's context data
US6899539B1 (en) * 2000-02-17 2005-05-31 Exponent, Inc. Infantry wearable information and weapon system
US20060004680A1 (en) * 1998-12-18 2006-01-05 Robarts James O Contextual responses based on automated learning techniques
US7010501B1 (en) * 1998-05-29 2006-03-07 Symbol Technologies, Inc. Personal shopping system
US7010603B2 (en) * 1998-08-17 2006-03-07 Openwave Systems Inc. Method and apparatus for controlling network connections based on destination locations
US7040541B2 (en) * 1996-09-05 2006-05-09 Symbol Technologies, Inc. Portable shopping and order fulfillment system
US7055101B2 (en) * 1998-12-18 2006-05-30 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7058893B2 (en) * 1998-12-18 2006-06-06 Tangis Corporation Managing interactions between computer users' context models
US7062715B2 (en) * 1998-12-18 2006-06-13 Tangis Corporation Supplying notifications related to supply and consumption of user context data
US7063265B2 (en) * 2001-09-03 2006-06-20 Oji Paper Co., Ltd. Baggage tag and method for using baggage tag
US20060136393A1 (en) * 2000-04-02 2006-06-22 Tangis Corporation Soliciting information based on a computer user's context
US7076737B2 (en) * 1998-12-18 2006-07-11 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7080322B2 (en) * 1998-12-18 2006-07-18 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7162473B2 (en) * 2003-06-26 2007-01-09 Microsoft Corporation Method and system for usage analyzer that determines user accessed sources, indexes data subsets, and associated metadata, processing implicit queries based on potential interest to users
US20070022384A1 (en) * 1998-12-18 2007-01-25 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7171378B2 (en) * 1998-05-29 2007-01-30 Symbol Technologies, Inc. Portable electronic terminal and data processing system
US20070043459A1 (en) * 1999-12-15 2007-02-22 Tangis Corporation Storing and recalling information to augment human memories
US20070168502A1 (en) * 2000-04-02 2007-07-19 Tangis Corporation Dynamically exchanging computer user's context
US7349894B2 (en) * 2000-03-22 2008-03-25 Sidestep, Inc. Method and apparatus for dynamic information connection search engine
US7360152B2 (en) * 2000-12-21 2008-04-15 Microsoft Corporation Universal media player
US7386477B2 (en) * 1999-02-26 2008-06-10 Accenture Llp Location-based filtering for a shopping agent in the physical world
US7395221B2 (en) * 2002-05-09 2008-07-01 International Business Machines Corporation Intelligent free-time search
US20090013052A1 (en) * 1998-12-18 2009-01-08 Microsoft Corporation Automated selection of appropriate information based on a computer user's context
US20090055752A1 (en) * 1998-12-18 2009-02-26 Microsoft Corporation Mediating conflicts in computer users context data
US7512889B2 (en) * 1998-12-18 2009-03-31 Microsoft Corporation Method and system for controlling presentation of information to a user based on the user's condition
US20090094524A1 (en) * 1998-12-18 2009-04-09 Microsoft Corporation Interface for exchanging context data
US7533052B2 (en) * 2000-02-07 2009-05-12 Om Technology Ab Trading system
US20090150535A1 (en) * 2000-04-02 2009-06-11 Microsoft Corporation Generating and supplying user context data
US7561200B2 (en) * 2004-07-26 2009-07-14 Csi Technology, Inc. Apparatus and method for automation of imaging and dynamic signal analyses
US7571218B2 (en) * 2000-05-16 2009-08-04 Fujifilm Corporation Information intermediary apparatus, information management apparatus, and information communication system
US7734780B2 (en) * 1998-12-18 2010-06-08 Microsoft Corporation Automated response to computer users context
US7877686B2 (en) * 2000-10-16 2011-01-25 Microsoft Corporation Dynamically displaying current status of tasks

Family Cites Families (259)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3973251A (en) 1975-04-25 1976-08-03 Stephans J Larry Timing device for exercise program with signalling means
US4283712A (en) 1976-12-22 1981-08-11 Goody Roy W Portable exercise totalizer
US4569026A (en) 1979-02-05 1986-02-04 Best Robert M TV Movies that talk back
US4458331A (en) 1981-10-09 1984-07-03 International Business Machines Corporation Interactive display terminal with alternating data processing and text processing sessions with text processing status line operable during data processing session
US5227614A (en) 1986-08-15 1993-07-13 Norand Corporation Core computer processor module, and peripheral shell module assembled to form a pocket size data capture unit
US4970683A (en) 1986-08-26 1990-11-13 Heads Up Technologies, Inc. Computerized checklist with predetermined sequences of sublists which automatically returns to skipped checklists
US4815030A (en) 1986-09-03 1989-03-21 Wang Laboratories, Inc. Multitask subscription data retrieval system
GB8719572D0 (en) 1987-08-19 1987-09-23 Krebs M S Sigscan text retrieval system
US4916441A (en) 1988-09-19 1990-04-10 Clinicom Incorporated Portable handheld terminal
US5201034A (en) 1988-09-30 1993-04-06 Hitachi Ltd. Interactive intelligent interface
US4905163A (en) 1988-10-03 1990-02-27 Minnesota Mining & Manufacturing Company Intelligent optical navigator dynamic information presentation and navigation system
EP0404932A4 (en) 1989-01-13 1993-01-27 The Scott Fetzer Company Apparatus and method for controlling and monitoring the exercise session for remotely located patients
US5146221A (en) 1989-01-13 1992-09-08 Stac, Inc. Data compression apparatus and method
JP2938104B2 (en) 1989-11-08 1999-08-23 株式会社日立製作所 Shared Resource Management Act lateral and information processing system
JPH05502130A (en) 1989-11-22 1993-04-15
US5278946A (en) 1989-12-04 1994-01-11 Hitachi, Ltd. Method of presenting multimedia data in a desired form by comparing and replacing a user template model with analogous portions of a system
US5032083A (en) 1989-12-08 1991-07-16 Augmentech, Inc. Computerized vocational task guidance system
US5251294A (en) 1990-02-07 1993-10-05 Abelow Daniel H Accessing, assembling, and using bodies of information
US5214757A (en) 1990-08-07 1993-05-25 Georesearch, Inc. Interactive automated mapping system
US6568595B1 (en) 1994-08-17 2003-05-27 Metrologic Instruments, Inc. System and method for carrying out electronic-commerce transactions using web documents embodying electronic-commerce enabling applets automatically launched and executed in response to reading url-encoded symbols pointing thereto
US5327529A (en) 1990-09-24 1994-07-05 Geoworks Process of designing user's interfaces for application programs
US5267147A (en) 1990-10-19 1993-11-30 Heads Up Technologies, Inc. Portable checklist system
US5586218A (en) 1991-03-04 1996-12-17 Inference Corporation Autonomous learning and reasoning agent
US5317568A (en) 1991-04-11 1994-05-31 Galileo International Partnership Method and apparatus for managing and facilitating communications in a distributed hetergeneous network
US5630157A (en) * 1991-06-13 1997-05-13 International Business Machines Corporation Computer organization for multiple and out-of-order execution of condition code testing and setting instructions
US5781913A (en) 1991-07-18 1998-07-14 Felsenstein; Lee Wearable hypermedium system
US5349678A (en) 1991-08-21 1994-09-20 Norand Corporation Versatile RF data capture system
US5208449A (en) 1991-09-09 1993-05-04 Psc, Inc. Portable transaction terminal
US5454074A (en) 1991-09-18 1995-09-26 The Boeing Company Electronic checklist system
US6418424B1 (en) * 1991-12-23 2002-07-09 Steven M. Hoffberg Ergonomic man-machine interface incorporating adaptive pattern recognition based control system
WO1993014454A1 (en) 1992-01-10 1993-07-22 Foster-Miller, Inc. A sensory integrated data interface
US5481667A (en) 1992-02-13 1996-01-02 Microsoft Corporation Method and system for instructing a user of a computer system how to perform application program tasks
US5349654A (en) 1992-02-20 1994-09-20 The Boeing Company Fault tolerant data exchange unit
JPH05260188A (en) 1992-03-13 1993-10-08 Matsushita Electric Ind Co Ltd Telephone equipment with incoming control function
US5388198A (en) * 1992-04-16 1995-02-07 Symantec Corporation Proactive presentation of automating features to a computer user
US5285398A (en) 1992-05-15 1994-02-08 Mobila Technology Inc. Flexible wearable computer
US5491651A (en) 1992-05-15 1996-02-13 Key, Idea Development Flexible wearable computer
US5535323A (en) 1992-06-29 1996-07-09 Digital Equipment Corporation Method of and system for displaying context sensitive and application independent help information
JP2597802B2 (en) 1992-08-04 1997-04-09 インターナショナル・ビジネス・マシーンズ・コーポレイション The method for controlling an image capture device, an image capture device and the user interface
US5335276A (en) 1992-12-16 1994-08-02 Texas Instruments Incorporated Communication system and methods for enhanced information transfer
US5720001A (en) 1993-04-16 1998-02-17 Compaq Computer Corporation Questionless case-based knowledge base and a method for constructing the same
JPH06332786A (en) 1993-05-25 1994-12-02 Fujitsu Ltd Data processing system with composite object
GB9315448D0 (en) * 1993-07-26 1993-09-08 Rank Xerox Ltd Recording and retrieval of information relevant to the activities of a user
US5806079A (en) 1993-11-19 1998-09-08 Smartpatents, Inc. System, method, and computer program product for using intelligent notes to organize, link, and manipulate disparate data objects
US5416730A (en) 1993-11-19 1995-05-16 Appcon Technologies, Inc. Arm mounted computer
US5812865A (en) 1993-12-03 1998-09-22 Xerox Corporation Specifying and establishing communication data paths between particular media devices in multiple media device computing systems based on context of a user or users
US5493692A (en) 1993-12-03 1996-02-20 Xerox Corporation Selective delivery of electronic messages in a multiple computer system based on context and environment of a user
US5555376A (en) 1993-12-03 1996-09-10 Xerox Corporation Method for granting a user request having locational and contextual attributes consistent with user policies for devices having locational attributes consistent with the user request
US5572401A (en) * 1993-12-13 1996-11-05 Key Idea Development L.L.C. Wearable personal computer system having flexible battery forming casing of the system
EP0736203A1 (en) 1993-12-23 1996-10-09 Diacom Technologies, Inc. Method and apparatus for implementing user feedback
US5513342A (en) 1993-12-28 1996-04-30 International Business Machines Corporation Display window layout system that automatically accommodates changes in display resolution, font size and national language
US5566069A (en) 1994-03-07 1996-10-15 Monsanto Company Computer network for collecting and analyzing agronomic data
US5470233A (en) 1994-03-17 1995-11-28 Arkenstone, Inc. System and method for tracking a pedestrian
US5522026A (en) 1994-03-18 1996-05-28 The Boeing Company System for creating a single electronic checklist in response to multiple faults
US5642129A (en) 1994-03-23 1997-06-24 Kopin Corporation Color sequential display panels
US5566337A (en) 1994-05-13 1996-10-15 Apple Computer, Inc. Method and apparatus for distributing events in an operating system
US5646629A (en) 1994-05-16 1997-07-08 Trimble Navigation Limited Memory cartridge for a handheld electronic video game
EP0760122B1 (en) 1994-05-16 2002-01-30 Apple Computer, Inc. Switching between appearance/behavior themes in graphical user interfaces
US5704366A (en) 1994-05-23 1998-01-06 Enact Health Management Systems System for monitoring and reporting medical measurements
US6321158B1 (en) 1994-06-24 2001-11-20 Delorme Publishing Company Integrated routing/mapping information
US6023683A (en) 1994-08-10 2000-02-08 Fisher Scientific Company Electronic sourcing system and method
US5559520A (en) 1994-09-26 1996-09-24 Lucent Technologies Inc. Wireless information system for acquiring location related information
US5601435A (en) 1994-11-04 1997-02-11 Intercare Method and apparatus for interactively monitoring a physiological condition and for interactively providing health related information
EP0712075A3 (en) 1994-11-08 1997-10-22 Canon Kk Information processing system which understands information and acts accordingly and method therefor
US6539336B1 (en) 1996-12-12 2003-03-25 Phatrat Technologies, Inc. Sport monitoring system for determining airtime, speed, power absorbed and other factors such as drop distance
US6460036B1 (en) 1994-11-29 2002-10-01 Pinpoint Incorporated System and method for providing customized electronic newspapers and target advertisements
US6571279B1 (en) 1997-12-05 2003-05-27 Pinpoint Incorporated Location enhanced information delivery system
DE69531599T2 (en) 1994-12-20 2004-06-24 Sun Microsystems, Inc., Mountain View Method and apparatus for locating and obtaining personalized information
US5659746A (en) 1994-12-30 1997-08-19 Aegis Star Corporation Method for storing and retrieving digital data transmissions
US5553609A (en) 1995-02-09 1996-09-10 Visiting Nurse Service, Inc. Intelligent remote visual monitoring system for home health care service
US6157982A (en) 1995-02-22 2000-12-05 Deo; Vinay System and method for remotely managing memory in a portable information device from an external computer
US5959611A (en) 1995-03-06 1999-09-28 Carnegie Mellon University Portable computer system with ergonomic input device
JP4309480B2 (en) 1995-03-07 2009-08-05 株式会社東芝 The information processing apparatus
US5745110A (en) 1995-03-10 1998-04-28 Microsoft Corporation Method and apparatus for arranging and displaying task schedule information in a calendar view format
US5710884A (en) 1995-03-29 1998-01-20 Intel Corporation System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use
US5689708A (en) 1995-03-31 1997-11-18 Showcase Corporation Client/server computer systems having control of client-based application programs, and application-program control means therefor
US5963914A (en) 1995-04-17 1999-10-05 Skinner; Gary R. Network time and work tracker
US5911132A (en) 1995-04-26 1999-06-08 Lucent Technologies Inc. Method using central epidemiological database
US5832296A (en) 1995-04-26 1998-11-03 Interval Research Corp. Wearable context sensitive user interface for interacting with plurality of electronic devices of interest to the user
US5642303A (en) 1995-05-05 1997-06-24 Apple Computer, Inc. Time and location based computing
US5873070A (en) 1995-06-07 1999-02-16 Norand Corporation Data collection system
JP3756954B2 (en) * 1995-07-11 2006-03-22 株式会社 日立製作所 Service providing system
WO1997003434A1 (en) 1995-07-12 1997-01-30 Virtual I/O, Inc. Ultra portable computer
JP3729918B2 (en) 1995-07-19 2005-12-21 株式会社東芝 Multi-modal dialogue system and how they interact
US5715451A (en) 1995-07-20 1998-02-03 Spacelabs Medical, Inc. Method and system for constructing formulae for processing medical data
US5826253A (en) 1995-07-26 1998-10-20 Borland International, Inc. Database system with methodology for notifying clients of any additions, deletions, or modifications occurring at the database server which affect validity of a range of data records cached in local memory buffers of clients
DE69625652D1 (en) 1995-08-18 2003-02-13 Ibm Event Management Services
US5726688A (en) 1995-09-29 1998-03-10 Ncr Corporation Predictive, adaptive computer interface
US6131067A (en) 1995-10-09 2000-10-10 Snaptrack, Inc. Client-server based remote locator device
US5701894A (en) 1995-11-09 1997-12-30 Del Mar Avionics Modular physiological computer-recorder
US6127990A (en) 1995-11-28 2000-10-03 Vega Vista, Inc. Wearable display and methods for controlling same
US6088689A (en) 1995-11-29 2000-07-11 Hynomics Corporation Multiple-agent hybrid control architecture for intelligent real-time control of distributed nonlinear processes
US5726660A (en) 1995-12-01 1998-03-10 Purdy; Peter K. Personal data collection and reporting system
US6122960A (en) 1995-12-12 2000-09-26 Acceleron Technologies, Llc. System and method for measuring movement of objects
US5899963A (en) 1995-12-12 1999-05-04 Acceleron Technologies, Llc System and method for measuring movement of objects
US5787279A (en) 1995-12-22 1998-07-28 International Business Machines Corporation System and method for conformationally-flexible molecular recognition
US5752019A (en) 1995-12-22 1998-05-12 International Business Machines Corporation System and method for confirmationally-flexible molecular identification
US5740037A (en) 1996-01-22 1998-04-14 Hughes Aircraft Company Graphical user interface system for manportable applications
JP3216514B2 (en) 1996-01-31 2001-10-09 株式会社デンソー Information service device
US6047327A (en) 1996-02-16 2000-04-04 Intel Corporation System for distributing electronic information to a targeted group of users
WO1997034388A3 (en) 1996-03-12 1997-12-18 Compuserve Inc System for developing user interface themes
US5910799A (en) 1996-04-09 1999-06-08 International Business Machines Corporation Location motion sensitive user interface
US5971580A (en) 1996-04-17 1999-10-26 Raytheon Company Tactical awareness monitoring and direct response system
US5848396A (en) 1996-04-26 1998-12-08 Freedom Of Information, Inc. Method and apparatus for determining behavioral profile of a computer user
US5790974A (en) 1996-04-29 1998-08-04 Sun Microsystems, Inc. Portable calendaring device having perceptual agent managing calendar entries
US6047301A (en) 1996-05-24 2000-04-04 International Business Machines Corporation Wearable computer
US6014638A (en) 1996-05-29 2000-01-11 America Online, Inc. System for customizing computer displays in accordance with user preferences
US5717747A (en) 1996-05-31 1998-02-10 Lucent Technologies Inc. Arrangement for facilitating plug-and-play call features
JPH09330336A (en) 1996-06-11 1997-12-22 Sony Corp Information processor
US5966533A (en) * 1996-06-11 1999-10-12 Excite, Inc. Method and system for dynamically synthesizing a computer program by differentially resolving atoms based on user context data
US5879163A (en) 1996-06-24 1999-03-09 Health Hero Network, Inc. On-line health education and feedback system using motivational driver profile coding and automated content fulfillment
US5831594A (en) 1996-06-25 1998-11-03 Sun Microsystems, Inc. Method and apparatus for eyetrack derived backtrack
US6035104A (en) 1996-06-28 2000-03-07 Data Link Systems Corp. Method and apparatus for managing electronic documents by alerting a subscriber at a destination other than the primary destination
US6442549B1 (en) 1997-07-25 2002-08-27 Eric Schneider Method, product, and apparatus for processing reusable information
FI102923B1 (en) 1996-08-08 1999-03-15 Nokia Mobile Phones Ltd Information print-out system, process for printing out information and terminals for printing out information
US5832500A (en) 1996-08-09 1998-11-03 Digital Equipment Corporation Method for searching an index
US5689619A (en) 1996-08-09 1997-11-18 The United States Of America As Represented By The Secretary Of The Army Eyetracker control of heads-up displays
US5719743A (en) 1996-08-15 1998-02-17 Xybernaut Corporation Torso worn computer which can stand alone
JP3688822B2 (en) 1996-09-03 2005-08-31 株式会社東芝 Electronic medical record system
US5924074A (en) 1996-09-27 1999-07-13 Azron Incorporated Electronic medical records system
US5974572A (en) 1996-10-15 1999-10-26 Mercury Interactive Corporation Software system and methods for generating a load test using a server access log
US5938721A (en) 1996-10-24 1999-08-17 Trimble Navigation Limited Position based personal digital assistant
US5818446A (en) 1996-11-18 1998-10-06 International Business Machines Corporation System for changing user interfaces based on display data content
US5902347A (en) 1996-11-19 1999-05-11 American Navigation Systems, Inc. Hand-held GPS-mapping device
US6012152A (en) 1996-11-27 2000-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Software fault management system
US5905492A (en) 1996-12-06 1999-05-18 Microsoft Corporation Dynamically updating themes for an operating system shell
US5966126A (en) 1996-12-23 1999-10-12 Szabo; Andrew J. Graphic user interface for database system
FI106990B (en) 1996-12-31 2001-05-15 Nokia Mobile Phones Ltd A method for transmitting information to the user
US6076166A (en) 1997-01-17 2000-06-13 Philips Electronics North America Corporation Personalizing hospital intranet web sites
US5798733A (en) 1997-01-21 1998-08-25 Northrop Grumman Corporation Interactive position guidance apparatus and method for guiding a user to reach a predetermined target position
US6122657A (en) 1997-02-04 2000-09-19 Networks Associates, Inc. Internet computer system with methods for dynamic filtering of hypertext tags and content
US6128663A (en) 1997-02-11 2000-10-03 Invention Depot, Inc. Method and apparatus for customization of information content provided to a requestor over a network using demographic information yet the user remains anonymous to the server
US6098065A (en) 1997-02-13 2000-08-01 Nortel Networks Corporation Associative search engine
US5977968A (en) 1997-03-14 1999-11-02 Mindmeld Multimedia Inc. Graphical user interface to communicate attitude or emotion to a computer program
US5913030A (en) 1997-03-18 1999-06-15 International Business Machines Corporation Method and system for client/server communications with user information revealed as a function of willingness to reveal and whether the information is required
US6289316B1 (en) 1997-03-25 2001-09-11 International Business Machines Corporation Progress notes model in a clinical information system
JPH10326289A (en) 1997-03-28 1998-12-08 Nippon Telegr & Teleph Corp <Ntt> Method for providing information and system therefor and storage medium for storing the same program
US6041331A (en) 1997-04-01 2000-03-21 Manning And Napier Information Services, Llc Automatic extraction and graphic visualization system and method
US6272507B1 (en) 1997-04-09 2001-08-07 Xerox Corporation System for ranking search results from a collection of documents using spreading activation techniques
KR100536134B1 (en) 1997-04-14 2005-12-14 톰슨 콘슈머 일렉트로닉스, 인코포레이티드 A system and method for processing and decoding mpeg compatible data and internet information
WO1998047084A1 (en) 1997-04-17 1998-10-22 Sharp Kabushiki Kaisha A method and system for object-based video description and linking
US5937160A (en) 1997-05-01 1999-08-10 Reedy Creek Technologies, Inc. Systems, methods and computer program products for updating hypertext documents via electronic mail
US6023729A (en) 1997-05-05 2000-02-08 Mpath Interactive, Inc. Method and apparatus for match making
US6453334B1 (en) 1997-06-16 2002-09-17 Streamtheory, Inc. Method and apparatus to allow remotely located computer programs and/or data to be accessed on a local computer in a secure, time-limited manner, with persistent caching
US6092101A (en) 1997-06-16 2000-07-18 Digital Equipment Corporation Method for filtering mail messages for a plurality of client computers connected to a mail service system
US5991687A (en) 1997-07-02 1999-11-23 Case Corporation System and method for communicating information related to a geographical area
US6108665A (en) 1997-07-03 2000-08-22 The Psychological Corporation System and method for optimizing behaviorial health care collection
US6094625A (en) 1997-07-03 2000-07-25 Trimble Navigation Limited Augmented vision for survey work and machine control
US6081814A (en) 1997-07-07 2000-06-27 Novell, Inc. Document reference environment manager
JP3714378B2 (en) 1997-07-31 2005-11-09 セイコーエプソン株式会社 Equipment Setup support apparatus, equipment set up support method and apparatus setup support program recorded medium
US6111893A (en) 1997-07-31 2000-08-29 Cisco Technology, Inc. Universal protocol conversion
US6409086B1 (en) 1997-08-08 2002-06-25 Symbol Technolgies, Inc. Terminal locking system
US5974262A (en) 1997-08-15 1999-10-26 Fuller Research Corporation System for generating output based on involuntary and voluntary user input without providing output information to induce user to alter involuntary input
JPH1196099A (en) 1997-09-19 1999-04-09 Hitachi Ltd Service providing system
US6070167A (en) 1997-09-29 2000-05-30 Sharp Laboratories Of America, Inc. Hierarchical method and system for object-based audiovisual descriptive tagging of images for information retrieval, editing, and manipulation
WO1999019823A3 (en) 1997-10-10 1999-08-19 Allen Philip A Van Methods and systems for providing human/computer interfaces
JP3922482B2 (en) 1997-10-14 2007-05-30 ソニー株式会社 Information processing apparatus and method
US6236768B1 (en) 1997-10-14 2001-05-22 Massachusetts Institute Of Technology Method and apparatus for automated, context-dependent retrieval of information
US6067084A (en) 1997-10-29 2000-05-23 International Business Machines Corporation Configuring microphones in an audio interface
US5999943A (en) 1997-10-31 1999-12-07 Oracle Corporation Lob locators
EP1029282A2 (en) * 1997-11-07 2000-08-23 ViA, Inc. Interactive devices and methods
US5953718A (en) 1997-11-12 1999-09-14 Oracle Corporation Research mode for a knowledge base search and retrieval system
US6134532A (en) 1997-11-14 2000-10-17 Aptex Software, Inc. System and method for optimal adaptive matching of users to most relevant entity and information in real-time
US6236978B1 (en) 1997-11-14 2001-05-22 New York University System and method for dynamic profiling of users in one-to-one applications
US6405264B1 (en) 1997-12-18 2002-06-11 Sun Microsystems, Inc. Marshaling and unmarshaling framework for supporting filters in a distributed object system
US6122348A (en) 1997-12-22 2000-09-19 Nortel Networks Corporation System and method for managing incoming communication events using multiple media options
US6427142B1 (en) 1998-01-06 2002-07-30 Chi Systems, Inc. Intelligent agent workbench
US5999932A (en) 1998-01-13 1999-12-07 Bright Light Technologies, Inc. System and method for filtering unsolicited electronic mail messages using data matching and heuristic processing
US6195622B1 (en) 1998-01-15 2001-02-27 Microsoft Corporation Methods and apparatus for building attribute transition probability models for use in pre-fetching resources
US6314384B1 (en) 1998-03-04 2001-11-06 Gerald E. Goetz Medication management apparatus
JPH11272689A (en) 1998-03-19 1999-10-08 Seiko Epson Corp Method and device for information retrieval processing and recording medium where information retrieval processing program is recorded
US6185534B1 (en) 1998-03-23 2001-02-06 Microsoft Corporation Modeling emotion and personality in a computer user interface
US6003082A (en) 1998-04-22 1999-12-14 International Business Machines Corporation Selective internet request caching and execution system
US6215405B1 (en) 1998-04-23 2001-04-10 Digital Security Controls Ltd. Programmable temperature sensor for security system
JPH11306002A (en) 1998-04-23 1999-11-05 Fujitsu Ltd Editing device and editing method for gui environment
US6155960A (en) 1998-05-01 2000-12-05 Roberts; Donald Training dummy assembly in human form
US6188399B1 (en) 1998-05-08 2001-02-13 Apple Computer, Inc. Multiple theme engine graphical user interface architecture
US6625135B1 (en) * 1998-05-11 2003-09-23 Cargenie Mellon University Method and apparatus for incorporating environmental information for mobile communications
US6405159B2 (en) 1998-06-03 2002-06-11 Sbc Technology Resources, Inc. Method for categorizing, describing and modeling types of system users
US6526035B1 (en) 1998-06-09 2003-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for identifying the source of a digital signal
WO1999066394B1 (en) 1998-06-17 2000-02-10 Microsoft Corp Method for adapting user interface elements based on historical usage
US6256633B1 (en) 1998-06-25 2001-07-03 U.S. Philips Corporation Context-based and user-profile driven information retrieval
US6446109B2 (en) 1998-06-29 2002-09-03 Sun Microsystems, Inc. Application computing environment
US6169976B1 (en) 1998-07-02 2001-01-02 Encommerce, Inc. Method and apparatus for regulating the use of licensed products
US6490579B1 (en) 1998-07-16 2002-12-03 Perot Systems Corporation Search engine system and method utilizing context of heterogeneous information resources
US6305007B1 (en) 1998-07-24 2001-10-16 Computer Associates Think, Inc. Object property meta model emulator for legacy data structures
US6262720B1 (en) 1998-07-24 2001-07-17 The Boeing Company Electronic checklist system with checklist inhibiting
US6311162B1 (en) 1998-07-25 2001-10-30 Ernst F. Reichwein Interactive symptomatic recording system and methods
US6363377B1 (en) 1998-07-30 2002-03-26 Sarnoff Corporation Search data processor
US6230111B1 (en) 1998-08-06 2001-05-08 Yamaha Hatsudoki Kabushiki Kaisha Control system for controlling object using pseudo-emotions and pseudo-personality generated in the object
US6442620B1 (en) 1998-08-17 2002-08-27 Microsoft Corporation Environment extensibility and automatic services for component applications using contexts, policies and activators
US7769620B1 (en) 1998-09-01 2010-08-03 Dennis Fernandez Adaptive direct transaction for networked client group
US6629133B1 (en) 1998-09-11 2003-09-30 Lv Partners, L.P. Interactive doll
US6507845B1 (en) 1998-09-14 2003-01-14 International Business Machines Corporation Method and software for supporting improved awareness of and collaboration among users involved in a task
US6321279B1 (en) 1998-09-14 2001-11-20 Compaq Computer Corporation System for implementing intelligent I/O processing in a multi-processor system by redirecting I/O messages to a target central processor selected from the multi-processor system
US6324569B1 (en) 1998-09-23 2001-11-27 John W. L. Ogilvie Self-removing email verified or designated as such by a message distributor for the convenience of a recipient
US6487552B1 (en) 1998-10-05 2002-11-26 Oracle Corporation Database fine-grained access control
US6218958B1 (en) 1998-10-08 2001-04-17 International Business Machines Corporation Integrated touch-skin notification system for wearable computing devices
US6643684B1 (en) 1998-10-08 2003-11-04 International Business Machines Corporation Sender- specified delivery customization
US6446076B1 (en) 1998-11-12 2002-09-03 Accenture Llp. Voice interactive web-based agent system responsive to a user location for prioritizing and formatting information
US6263317B1 (en) 1998-12-01 2001-07-17 Fogdog, Inc. Web sales channel conflict resolution system
US6563430B1 (en) 1998-12-11 2003-05-13 Koninklijke Philips Electronics N.V. Remote control device with location dependent interface
US6812937B1 (en) 1998-12-18 2004-11-02 Tangis Corporation Supplying enhanced computer user's context data
US6747675B1 (en) 1998-12-18 2004-06-08 Tangis Corporation Mediating conflicts in computer user's context data
US6349307B1 (en) 1998-12-28 2002-02-19 U.S. Philips Corporation Cooperative topical servers with automatic prefiltering and routing
US6442589B1 (en) 1999-01-14 2002-08-27 Fujitsu Limited Method and system for sorting and forwarding electronic messages and other data
US6282517B1 (en) 1999-01-14 2001-08-28 Autobytel.Com, Inc. Real time communication of purchase requests
US6430531B1 (en) 1999-02-04 2002-08-06 Soliloquy, Inc. Bilateral speech system
US6292796B1 (en) 1999-02-23 2001-09-18 Clinical Focus, Inc. Method and apparatus for improving access to literature
US6462759B1 (en) 1999-02-25 2002-10-08 International Business Machines Corporation Adaptive computer display screen window
US6294953B1 (en) * 1999-02-26 2001-09-25 Axcess, Inc. High sensitivity demodulator for a radio tag and method
JP4299911B2 (en) 1999-03-24 2009-07-22 株式会社東芝 Information transfer system
US6636831B1 (en) * 1999-04-09 2003-10-21 Inroad, Inc. System and process for voice-controlled information retrieval
US6507567B1 (en) 1999-04-09 2003-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Efficient handling of connections in a mobile communications network
US6289513B1 (en) 1999-06-01 2001-09-11 Isaac Bentwich Interactive application generation and text processing
US7103806B1 (en) 1999-06-04 2006-09-05 Microsoft Corporation System for performing context-sensitive decisions about ideal communication modalities considering information about channel reliability
US6484200B1 (en) 1999-06-11 2002-11-19 Sun Microsystems, Inc. Distinguished name scoping system for event filtering
US7000187B2 (en) 1999-07-01 2006-02-14 Cisco Technology, Inc. Method and apparatus for software technical support and training
US6301609B1 (en) 1999-07-07 2001-10-09 Lucent Technologies Inc. Assignable associate priorities for user-definable instant messaging buddy groups
US20010030664A1 (en) 1999-08-16 2001-10-18 Shulman Leo A. Method and apparatus for configuring icon interactivity
US6483485B1 (en) 1999-08-18 2002-11-19 Jung-Tang Huang Method and device for protecting eyes through screen displaying setting
US6885734B1 (en) 1999-09-13 2005-04-26 Microstrategy, Incorporated System and method for the creation and automatic deployment of personalized, dynamic and interactive inbound and outbound voice services, with real-time interactive voice database queries
US6519552B1 (en) 1999-09-15 2003-02-11 Xerox Corporation Systems and methods for a hybrid diagnostic approach of real time diagnosis of electronic systems
US6714977B1 (en) 1999-10-27 2004-03-30 Netbotz, Inc. Method and system for monitoring computer networks and equipment
US6829639B1 (en) 1999-11-15 2004-12-07 Netvision, Inc. Method and system for intelligent global event notification and control within a distributed computing environment
US6834195B2 (en) 2000-04-04 2004-12-21 Carl Brock Brandenberg Method and apparatus for scheduling presentation of digital content on a personal communication device
US6652283B1 (en) 1999-12-30 2003-11-25 Cerego, Llc System apparatus and method for maximizing effectiveness and efficiency of learning retaining and retrieving knowledge and skills
US6834208B2 (en) 1999-12-30 2004-12-21 Microsoft Corporation Method and apparatus for providing distributed control of a home automation and control system
US6546554B1 (en) 2000-01-21 2003-04-08 Sun Microsystems, Inc. Browser-independent and automatic apparatus and method for receiving, installing and launching applications from a browser on a client computer
US6542889B1 (en) 2000-01-28 2003-04-01 International Business Machines Corporation Methods and apparatus for similarity text search based on conceptual indexing
US6868525B1 (en) 2000-02-01 2005-03-15 Alberti Anemometer Llc Computer graphic display visualization system and method
US20020075331A1 (en) 2000-02-14 2002-06-20 Julian Orbanes Method and apparatus for addressing data objects in virtual space
US6615197B1 (en) 2000-03-13 2003-09-02 Songhai Chai Brain programmer for increasing human information processing capacity
US6327535B1 (en) 2000-04-05 2001-12-04 Microsoft Corporation Location beaconing methods and systems
US20020191034A1 (en) 2000-06-28 2002-12-19 Sowizral Henry A. Size conditioned visibility search system and method
US6477117B1 (en) * 2000-06-30 2002-11-05 International Business Machines Corporation Alarm interface for a smart watch
US6707476B1 (en) 2000-07-05 2004-03-16 Ge Medical Systems Information Technologies, Inc. Automatic layout selection for information monitoring system
US6738759B1 (en) 2000-07-07 2004-05-18 Infoglide Corporation, Inc. System and method for performing similarity searching using pointer optimization
EP1182541A3 (en) 2000-08-22 2005-11-30 Siemens Aktiengesellschaft System and method for combined use of different display/apparatus types with system controlled context dependant information representation
US7392486B1 (en) 2000-09-19 2008-06-24 Honeywell International Inc. Method and apparatus for automatic display and removal of required synoptic pages in a checklist context
US6795806B1 (en) 2000-09-20 2004-09-21 International Business Machines Corporation Method for enhancing dictation and command discrimination
US20020044152A1 (en) 2000-10-16 2002-04-18 Abbott Kenneth H. Dynamic integration of computer generated and real world images
WO2002033541A3 (en) 2000-10-16 2003-12-31 Kenneth Abbott Dynamically determining appropriate computer interfaces
US6704812B2 (en) * 2000-11-30 2004-03-09 International Business Machines Corporation Transparent and dynamic management of redundant physical paths to peripheral devices
US7110764B1 (en) 2000-12-21 2006-09-19 Cisco Technology, Inc. Mobility manager in a wireless IP core network
EP1410228B1 (en) 2001-06-22 2016-03-23 Wonderware Corporation Remotely monitoring / diagnosing distributed components of a supervisory process control and manufacturing information application from a central location
US20040133600A1 (en) 2002-07-19 2004-07-08 Homer Gregg S. Rechargeable media distribution and play system
US20050160113A1 (en) 2001-08-31 2005-07-21 Kent Ridge Digital Labs Time-based media navigation system
US7283992B2 (en) 2001-11-30 2007-10-16 Microsoft Corporation Media agent to suggest contextually related media content
US6766245B2 (en) * 2002-03-14 2004-07-20 Microsoft Corporation Landmark-based location of users
WO2003096669A3 (en) 2002-05-10 2004-07-01 Richard R Reisman Method and apparatus for browsing using multiple coordinated device
US7124125B2 (en) 2002-11-01 2006-10-17 Loudeye Corp. System and method for providing media samples on-line in response to media related searches on the internet
KR100493891B1 (en) 2003-01-28 2005-06-10 삼성전자주식회사 Method and system for managing a database of media files
US20040267812A1 (en) 2003-06-26 2004-12-30 Microsoft Corporation Media platform
US7836010B2 (en) 2003-07-30 2010-11-16 Northwestern University Method and system for assessing relevant properties of work contexts for use by information services
US20050193017A1 (en) 2004-02-19 2005-09-01 Han-Gyoo Kim Portable multimedia player/recorder that accesses data contents from and writes to networked device
US7260453B2 (en) 2005-01-06 2007-08-21 The Boeing Company Checklist error mitigation system
US20060259494A1 (en) 2005-05-13 2006-11-16 Microsoft Corporation System and method for simultaneous search service and email search
WO2007130716A3 (en) 2006-01-31 2008-07-10 Intellext Inc Methods and apparatus for computerized searching

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041365A (en) * 1985-10-29 2000-03-21 Kleinerman; Aurel Apparatus and method for high performance remote application gateway servers
US5133075A (en) * 1988-12-19 1992-07-21 Hewlett-Packard Company Method of monitoring changes in attribute values of object in an object-oriented database
US5522024A (en) * 1990-03-30 1996-05-28 International Business Machines Corporation Programming environment system for customizing a program application based upon user input
US5592664A (en) * 1991-07-29 1997-01-07 Borland International Inc. Database server system with methods for alerting clients of occurrence of database server events of interest to the clients
US5237684A (en) * 1991-08-12 1993-08-17 International Business Machines Corporation Customized and versatile event monitor within event management services of a computer system
US5339395A (en) * 1992-09-17 1994-08-16 Delco Electronics Corporation Interface circuit for interfacing a peripheral device with a microprocessor operating in either a synchronous or an asynchronous mode
US5513646A (en) * 1992-11-09 1996-05-07 I Am Fine, Inc. Personal security monitoring system and method
US5769085A (en) * 1993-01-06 1998-06-23 Mitsubishi Jidosha Kogyo Kabushiki Kaisha Apparatus for detecting awareness of a vehicle driver and method thereof
US5867171A (en) * 1993-05-25 1999-02-02 Casio Computer Co., Ltd. Face image data processing devices
US5398021A (en) * 1993-07-19 1995-03-14 Motorola, Inc. Reliable information service message delivery system
US5742279A (en) * 1993-11-08 1998-04-21 Matsushita Electrical Co., Ltd. Input/display integrated information processing device
US5738102A (en) * 1994-03-31 1998-04-14 Lemelson; Jerome H. Patient monitoring system
US5787234A (en) * 1994-06-22 1998-07-28 Molloy; Bruce G. System and method for representing and retrieving knowledge in an adaptive cognitive network
US5754938A (en) * 1994-11-29 1998-05-19 Herz; Frederick S. M. Pseudonymous server for system for customized electronic identification of desirable objects
US5942986A (en) * 1995-08-09 1999-08-24 Cedars-Sinai Medical Center System and method for automatic critical event notification
US6085086A (en) * 1995-08-22 2000-07-04 Lucent Technologies Inc. Network-based migrating user agent for personal communication services
US6421700B1 (en) * 1995-12-22 2002-07-16 Xerox Corporation Method and system for work process support using independent system and user states
US6672506B2 (en) * 1996-01-25 2004-01-06 Symbol Technologies, Inc. Statistical sampling security methodology for self-scanning checkout system
US6282537B1 (en) * 1996-05-30 2001-08-28 Massachusetts Institute Of Technology Query and retrieving semi-structured data from heterogeneous sources by translating structured queries
US5945988A (en) * 1996-06-06 1999-08-31 Intel Corporation Method and apparatus for automatically determining and dynamically updating user preferences in an entertainment system
US7040541B2 (en) * 1996-09-05 2006-05-09 Symbol Technologies, Inc. Portable shopping and order fulfillment system
US6837436B2 (en) * 1996-09-05 2005-01-04 Symbol Technologies, Inc. Consumer interactive shopping system
US7195157B2 (en) * 1996-09-05 2007-03-27 Symbol Technologies, Inc. Consumer interactive shopping system
US5930501A (en) * 1996-09-20 1999-07-27 Neil; John M. Pictorial user interface for establishing time of day and geographical or environmental context on a computer display or other monitor
US6035264A (en) * 1996-11-26 2000-03-07 Global Maintech, Inc. Electronic control system and method for externally controlling process in a computer system with a script language
US6198394B1 (en) * 1996-12-05 2001-03-06 Stephen C. Jacobsen System for remote monitoring of personnel
US6704785B1 (en) * 1997-03-17 2004-03-09 Vitria Technology, Inc. Event driven communication system
US5796952A (en) * 1997-03-21 1998-08-18 Dot Com Development, Inc. Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database
US6546005B1 (en) * 1997-03-25 2003-04-08 At&T Corp. Active user registry
US6199102B1 (en) * 1997-08-26 2001-03-06 Christopher Alan Cobb Method and system for filtering electronic messages
US6263268B1 (en) * 1997-08-26 2001-07-17 Transcontech Corporation System and method for providing mobile automotive telemetry
US6061660A (en) * 1997-10-20 2000-05-09 York Eggleston System and method for incentive programs and award fulfillment
US6061610A (en) * 1997-10-31 2000-05-09 Nissan Technical Center North America, Inc. Method and apparatus for determining workload of motor vehicle driver
US6031455A (en) * 1998-02-09 2000-02-29 Motorola, Inc. Method and apparatus for monitoring environmental conditions in a communication system
US6044415A (en) * 1998-02-27 2000-03-28 Intel Corporation System for transferring I/O data between an I/O device and an application program's memory in accordance with a request directly over a virtual connection
US6105063A (en) * 1998-05-05 2000-08-15 International Business Machines Corp. Client-server system for maintaining application preferences in a hierarchical data structure according to user and user group or terminal and terminal group contexts
US7171378B2 (en) * 1998-05-29 2007-01-30 Symbol Technologies, Inc. Portable electronic terminal and data processing system
US7010501B1 (en) * 1998-05-29 2006-03-07 Symbol Technologies, Inc. Personal shopping system
US7010603B2 (en) * 1998-08-17 2006-03-07 Openwave Systems Inc. Method and apparatus for controlling network connections based on destination locations
US6546425B1 (en) * 1998-10-09 2003-04-08 Netmotion Wireless, Inc. Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US6112246A (en) * 1998-10-22 2000-08-29 Horbal; Mark T. System and method for accessing information from a remote device and providing the information to a client workstation
US6738975B1 (en) * 1998-11-18 2004-05-18 Software Ag, Inc. Extensible distributed enterprise application integration system
US6438618B1 (en) * 1998-12-16 2002-08-20 Intel Corporation Method and device for filtering events in an event notification service
US20100217862A1 (en) * 1998-12-18 2010-08-26 Microsoft Corporation Supplying notifications related to supply and consumption of user context data
US20090013052A1 (en) * 1998-12-18 2009-01-08 Microsoft Corporation Automated selection of appropriate information based on a computer user's context
US20070130524A1 (en) * 1998-12-18 2007-06-07 Tangis Corporation Supplying notifications related to supply and consumption of user context data
US20090055752A1 (en) * 1998-12-18 2009-02-26 Microsoft Corporation Mediating conflicts in computer users context data
US7076737B2 (en) * 1998-12-18 2006-07-11 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7512889B2 (en) * 1998-12-18 2009-03-31 Microsoft Corporation Method and system for controlling presentation of information to a user based on the user's condition
US20090094524A1 (en) * 1998-12-18 2009-04-09 Microsoft Corporation Interface for exchanging context data
US7734780B2 (en) * 1998-12-18 2010-06-08 Microsoft Corporation Automated response to computer users context
US20070022384A1 (en) * 1998-12-18 2007-01-25 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US20050066282A1 (en) * 1998-12-18 2005-03-24 Tangis Corporation Requesting computer user's context data
US20050086243A1 (en) * 1998-12-18 2005-04-21 Tangis Corporation Logging and analyzing computer user's context data
US7739607B2 (en) * 1998-12-18 2010-06-15 Microsoft Corporation Supplying notifications related to supply and consumption of user context data
US20060004680A1 (en) * 1998-12-18 2006-01-05 Robarts James O Contextual responses based on automated learning techniques
US7080322B2 (en) * 1998-12-18 2006-07-18 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7779015B2 (en) * 1998-12-18 2010-08-17 Microsoft Corporation Logging and analyzing context attributes
US7945859B2 (en) * 1998-12-18 2011-05-17 Microsoft Corporation Interface for exchanging context data
US7062715B2 (en) * 1998-12-18 2006-06-13 Tangis Corporation Supplying notifications related to supply and consumption of user context data
US7055101B2 (en) * 1998-12-18 2006-05-30 Tangis Corporation Thematic response to a computer user's context, such as by a wearable personal computer
US7089497B2 (en) * 1998-12-18 2006-08-08 Tangis Corporation Managing interactions between computer users' context models
US7058893B2 (en) * 1998-12-18 2006-06-06 Tangis Corporation Managing interactions between computer users' context models
US6385589B1 (en) * 1998-12-30 2002-05-07 Pharmacia Corporation System for monitoring and managing the health care of a patient population
US6718332B1 (en) * 1999-01-04 2004-04-06 Cisco Technology, Inc. Seamless importation of data
US7386477B2 (en) * 1999-02-26 2008-06-10 Accenture Llp Location-based filtering for a shopping agent in the physical world
US6401085B1 (en) * 1999-03-05 2002-06-04 Accenture Llp Mobile communication and computing system and method
US6356905B1 (en) * 1999-03-05 2002-03-12 Accenture Llp System, method and article of manufacture for mobile communication utilizing an interface support framework
US6199099B1 (en) * 1999-03-05 2001-03-06 Ac Properties B.V. System, method and article of manufacture for a mobile communication network utilizing a distributed communication network
US6353823B1 (en) * 1999-03-08 2002-03-05 Intel Corporation Method and system for using associative metadata
US6553336B1 (en) * 1999-06-25 2003-04-22 Telemonitor, Inc. Smart remote monitoring system and method
US6529723B1 (en) * 1999-07-06 2003-03-04 Televoke, Inc. Automated user notification system
US6850252B1 (en) * 1999-10-05 2005-02-01 Steven M. Hoffberg Intelligent electronic appliance system and method
US20080090591A1 (en) * 1999-10-22 2008-04-17 Miller John M computer-implemented method to perform location-based searching
US6353398B1 (en) * 1999-10-22 2002-03-05 Himanshu S. Amin System for dynamically pushing information to a user utilizing global positioning system
US20080161018A1 (en) * 1999-10-22 2008-07-03 Miller John M System for dynamically pushing information to a user utilizing global positioning system
US6741188B1 (en) * 1999-10-22 2004-05-25 John M. Miller System for dynamically pushing information to a user utilizing global positioning system
US20080091537A1 (en) * 1999-10-22 2008-04-17 Miller John M Computer-implemented method for pushing targeted advertisements to a user
US7385501B2 (en) * 1999-10-22 2008-06-10 Himanshu S. Amin System for dynamically pushing information to a user utilizing global positioning system
US20060019676A1 (en) * 1999-10-22 2006-01-26 Miller John M System for dynamically pushing information to a user utilizing global positioning system
US6704722B2 (en) * 1999-11-17 2004-03-09 Xerox Corporation Systems and methods for performing crawl searches and index searches
US20070043459A1 (en) * 1999-12-15 2007-02-22 Tangis Corporation Storing and recalling information to augment human memories
US7533052B2 (en) * 2000-02-07 2009-05-12 Om Technology Ab Trading system
US6899539B1 (en) * 2000-02-17 2005-05-31 Exponent, Inc. Infantry wearable information and weapon system
US7349894B2 (en) * 2000-03-22 2008-03-25 Sidestep, Inc. Method and apparatus for dynamic information connection search engine
US20080147775A1 (en) * 2000-04-02 2008-06-19 Microsoft Corporation Dynamically swapping modules for determing a computer user's context
US20070168502A1 (en) * 2000-04-02 2007-07-19 Tangis Corporation Dynamically exchanging computer user's context
US20060136393A1 (en) * 2000-04-02 2006-06-22 Tangis Corporation Soliciting information based on a computer user's context
US20090150535A1 (en) * 2000-04-02 2009-06-11 Microsoft Corporation Generating and supplying user context data
US8103665B2 (en) * 2000-04-02 2012-01-24 Microsoft Corporation Soliciting information based on a computer user's context
US7571218B2 (en) * 2000-05-16 2009-08-04 Fujifilm Corporation Information intermediary apparatus, information management apparatus, and information communication system
US6712615B2 (en) * 2000-05-22 2004-03-30 Rolf John Martin High-precision cognitive performance test battery suitable for internet and non-internet use
US7877686B2 (en) * 2000-10-16 2011-01-25 Microsoft Corporation Dynamically displaying current status of tasks
US7360152B2 (en) * 2000-12-21 2008-04-15 Microsoft Corporation Universal media player
US7063265B2 (en) * 2001-09-03 2006-06-20 Oji Paper Co., Ltd. Baggage tag and method for using baggage tag
US7395221B2 (en) * 2002-05-09 2008-07-01 International Business Machines Corporation Intelligent free-time search
USD494584S1 (en) * 2002-12-05 2004-08-17 Symbol Technologies, Inc. Mobile companion
US7162473B2 (en) * 2003-06-26 2007-01-09 Microsoft Corporation Method and system for usage analyzer that determines user accessed sources, indexes data subsets, and associated metadata, processing implicit queries based on potential interest to users
US7561200B2 (en) * 2004-07-26 2009-07-14 Csi Technology, Inc. Apparatus and method for automation of imaging and dynamic signal analyses

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Russinovich, Mark. "Inside the Windows NT Registry". downloaded from . March 31, 1997. *

Cited By (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8181113B2 (en) 1998-12-18 2012-05-15 Microsoft Corporation Mediating conflicts in computer users context data
US20080313271A1 (en) * 1998-12-18 2008-12-18 Microsoft Corporation Automated reponse to computer users context
US9559917B2 (en) 1998-12-18 2017-01-31 Microsoft Technology Licensing, Llc Supplying notifications related to supply and consumption of user context data
US9183306B2 (en) 1998-12-18 2015-11-10 Microsoft Technology Licensing, Llc Automated selection of appropriate information based on a computer user's context
US8489997B2 (en) 1998-12-18 2013-07-16 Microsoft Corporation Supplying notifications related to supply and consumption of user context data
US7689919B2 (en) 1998-12-18 2010-03-30 Microsoft Corporation Requesting computer user's context data
US7734780B2 (en) 1998-12-18 2010-06-08 Microsoft Corporation Automated response to computer users context
US7739607B2 (en) 1998-12-18 2010-06-15 Microsoft Corporation Supplying notifications related to supply and consumption of user context data
US7779015B2 (en) 1998-12-18 2010-08-17 Microsoft Corporation Logging and analyzing context attributes
US8225214B2 (en) 1998-12-18 2012-07-17 Microsoft Corporation Supplying enhanced computer user's context data
US9372555B2 (en) 1998-12-18 2016-06-21 Microsoft Technology Licensing, Llc Managing interactions between computer users' context models
US7945859B2 (en) 1998-12-18 2011-05-17 Microsoft Corporation Interface for exchanging context data
US8020104B2 (en) 1998-12-18 2011-09-13 Microsoft Corporation Contextual responses based on automated learning techniques
US9906474B2 (en) 1998-12-18 2018-02-27 Microsoft Technology Licensing, Llc Automated selection of appropriate information based on a computer user's context
US8126979B2 (en) 1998-12-18 2012-02-28 Microsoft Corporation Automated response to computer users context
US8677248B2 (en) 1998-12-18 2014-03-18 Microsoft Corporation Requesting computer user's context data
US8626712B2 (en) 1998-12-18 2014-01-07 Microsoft Corporation Logging and analyzing computer user's context data
US9443037B2 (en) 1999-12-15 2016-09-13 Microsoft Technology Licensing, Llc Storing and recalling information to augment human memories
US7827281B2 (en) 2000-04-02 2010-11-02 Microsoft Corporation Dynamically determining a computer user's context
US8346724B2 (en) 2000-04-02 2013-01-01 Microsoft Corporation Generating and supplying user context data
US7647400B2 (en) 2000-04-02 2010-01-12 Microsoft Corporation Dynamically exchanging computer user's context
US8103665B2 (en) 2000-04-02 2012-01-24 Microsoft Corporation Soliciting information based on a computer user's context
US20070168502A1 (en) * 2000-04-02 2007-07-19 Tangis Corporation Dynamically exchanging computer user's context
US7877686B2 (en) 2000-10-16 2011-01-25 Microsoft Corporation Dynamically displaying current status of tasks
US20090319569A1 (en) * 2008-06-24 2009-12-24 Microsoft Corporation Context platform
US20090320143A1 (en) * 2008-06-24 2009-12-24 Microsoft Corporation Sensor interface
US8516001B2 (en) 2008-06-24 2013-08-20 Microsoft Corporation Context platform

Also Published As

Publication number Publication date Type
US6801223B1 (en) 2004-10-05 grant
US20020052930A1 (en) 2002-05-02 application
US20020099817A1 (en) 2002-07-25 application
US7089497B2 (en) 2006-08-08 grant
US9372555B2 (en) 2016-06-21 grant
US20020083158A1 (en) 2002-06-27 application
US7058893B2 (en) 2006-06-06 grant
US7058894B2 (en) 2006-06-06 grant
US20020052963A1 (en) 2002-05-02 application

Similar Documents

Publication Publication Date Title
Korpipaa et al. Managing context information in mobile devices
US5493692A (en) Selective delivery of electronic messages in a multiple computer system based on context and environment of a user
Castro et al. Managing context data for smart spaces
US7661088B2 (en) Systems and methods to efficiently and automatically effect population of custom controls onto a visual designer toolbox
US20090165022A1 (en) System and method for scheduling electronic events
US7162494B2 (en) Method and system for distributed user profiling
US20130103212A1 (en) Method and apparatus for providing context-based power consumption control
US20050246304A1 (en) End-user application customization using rules
Ranganathan et al. An infrastructure for context-awareness based on first order logic
Anhalt et al. Toward context-aware computing: experiences and lessons
US20070100480A1 (en) Multi-modal device power/mode management
US20030074253A1 (en) System and method for matching consumers with products
US20050267770A1 (en) Methods and apparatus for performing task management based on user context
US7512889B2 (en) Method and system for controlling presentation of information to a user based on the user&#39;s condition
Garlan et al. Project aura: Toward distraction-free pervasive computing
US20100229082A1 (en) Dynamic context-data tag cloud
Henricksen et al. Modelling and using imperfect context information
Muhlenbrock et al. Learning to detect user activity and availability from a variety of sensor data
US7536695B2 (en) Architecture and system for location awareness
US20040143659A1 (en) System and method for a scalable notification server providing
US7433960B1 (en) Systems, methods and computer products for profile based identity verification over the internet
Huebscher et al. Adaptive middleware for context-aware applications in smart-homes
US20070299631A1 (en) Logging user actions within activity context
Nelson Context-aware and location systems
US7738884B2 (en) Positioning service utilizing existing radio base stations

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TANGIS CORPORATION;REEL/FRAME:019265/0368

Effective date: 20070306

Owner name: MICROSOFT CORPORATION,WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TANGIS CORPORATION;REEL/FRAME:019265/0368

Effective date: 20070306

AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ABBOTT, KENNETH H.;NEWELL, DAN;ROBARTS, JAMES O.;AND OTHERS;REEL/FRAME:019639/0001;SIGNING DATES FROM 20070521 TO 20070720

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034542/0001

Effective date: 20141014