Logging and analyzing computer user's context data

Abstract
A facility for logging context attributes is described. For each of a set of selected context attributes, the facility, determines a target frequency with which values of the selected context attribute are to be logged. For each of the set of selected context attributes, the facility obtains values of the selected context attribute at a frequency approximating the target frequency determined for the selected context attribute. Then, for each obtained context attribute value, the facility writes the obtained value to a storage device in a manner that identifies its context attribute.
Description
TECHNICAL FIELD

The present invention is directed to the field of data storage and analysis, and more particularly, to the field of storage and analysis of user context data, such as in a wearable personal computer.


BACKGROUND

Most general-purpose computer systems are designed to operate by processing commands as they are inputted. As a result, the only information such a computer system typically possesses about the condition of its user is the commands issued by the user. In particular, such a computer system generally only possesses this very limited type of information about the user's condition for the short time during which the computer system is processing the command.


A few special-purpose application programs that execute on general-purpose computer systems maintain a record of the commands issued by the user. For example, the Microsoft Internet Explorer and Netscape Navigator web browser applications accept commands, to display particular web pages, and have a “history” feature that maintains and displays a list of web page requests made by the user. The history feature enables the user to review his or her web page requests, and to resubmit a web page request by selecting it from the list.


While such application history features can be useful, they are not extensively configurable with respect to either the identity of the information that they record, the manner in which they record it, the manner in which they maintain it once recorded, or the nature of any later-performed analysis on the recorded information. Further, such history features are inherently limited to recording information in the possession of their host applications, and thus do not record other information such as the state of other applications, the operating system, or the computer system hardware. Such history features also fail to record information about the user, or about the environment surrounding the computer system and/or the user.


Accordingly, a facility in a general-purpose computer system for selectively recording, maintaining, and analyzing information about the computer system, a user, and/or their environment would have significant utility.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates an embodiment of the facility which executes on a general-purpose body-mounted wearable computer worn by a user.



FIG. 2 illustrates an exemplary computer system on which an embodiment of the facility is executing.



FIG. 3 is a data flow diagram showing a sample exchange of attributes performed by the characterization module.



FIG. 4 is a data structure diagram showing an attribute instance table in which the characterization module caches attribute instance values.



FIG. 5 is a data structure diagram showing a logging configuration table used by the facility to determine which attribute instances to log and when.



FIG. 6 is a flow diagram showing the steps preferably performed by the facility in order to log attribute instances.



FIG. 7 is a data structure diagram showing an attribute log table produced by the facility.



FIG. 8 is a flow diagram showing the steps preferably performed by the facility in order to maintain an attribute log.



FIG. 9 is a flow diagram showing the steps preferably performed by the facility to analyze log records for attribute instances.



FIG. 10 is a flow diagram showing the steps preferably performed by the facility in order to conduct a context simulation.



FIG. 11 is a data flow diagram showing the operation of the facility without a characterization module.





DETAILED DESCRIPTION

A software facility for recording, maintaining, and analyzing data regarding user context (“the facility”) is provided. In a preferred embodiment, a characterization module operating in a computer system such as a wearable general-purpose computer system obtains context information, in the form of values for individual attributes each modeling an aspect of the wearable computer system, its user, or the surrounding environment, from one or more context servers, and provide it to one or more context clients that consume the context information. The facility, preferably implemented as part of the characterization module, periodically stores values of selected attributes obtained from context servers in a time-indexed log.


The log may be stored in a database, a sparse matrix, or a file of another type, on a storage device that is either local or remote with respect to the computer system. The identity of the logged attributes, as well as the frequency at which each is logged, is preferably configurable, either manually by the user, or by other programs executing on the computer system. The logged attributes are data gathered or derived to characterize the state of the computer system, its user, and the surrounding environment. The logged attributes may be very compact, such as a boolean value, or very voluminous, such as a color image.


The facility preferably further provides configurable pre-logging processing of logged attributes, such as determining whether data specified for logging should actually be logged, transforming data into a new form for logging, and/or combining data from different sources before logging it.


The facility preferably further provides configurable, selective maintenance of logged attribute data, enabling logged data to be compacted, abstracted, or otherwise further processed based on a variety of factors. This enables the facility to retain detailed, voluminous information for a short time, then process the information to reduce the volume of information that is retained for a longer time. In cases where the detailed information is interesting, such processing can be skipped or deferred to retain the detailed information.


The facility preferably further provides analysis of logged attribute data using later-defined analysis techniques. For example, after data has been logged indicating that (1) a user was present in a particular location for a period of time, and that (2) the user thereafter moved away from that location at a particular direction and speed, an analysis technique could be defined and applied to this data to determine that the user waited for and embarked on a mode of transportation that takes on passengers at the logged location and moves in the logged direction at the logged speed.


Additional embodiments of the facility provide retrospective simulation of events represented in logged attribute data by substituting logged values of selected attributes for real-time attribute values in the attribute values provided to context clients by the characterization module. Such simulations may be conducted for a variety of purposes, including for training, to demonstrate how context clients perform in a particular situation, for usability texting, for debugging, or to repeat an experience represented by logged data. By modifying the logged data used in a simulation beforehand, the user can modify the represented experience. Indeed, completely new experiences may be presented to the user by manufacturing logged data that represent such new experiences.


In this way, the facility makes it possible to preserve, review, and analyze, and simulate historical context data. This enables programs executing on the computer system to make observations, and even judgments, in the present that are predicated on an understanding of events that occurred in the past, and to take initiative to assist the user on this basis. It also enables programs executing on the computer system to evaluate and understand in a retrospective context, rather than merely in an instantaneous context.



FIG. 1 illustrates an embodiment of the facility 100 which executes on a general-purpose body-mounted wearable computer 120 worn by a 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 logged. Indeed, the computer system may have no identifiable user, but rather operate as an independent probe, logging and/or reporting on the context in an arbitrary location.


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, such as from context servers that process the input information and generate attribute values, and can present information to the user on the various output devices accessible to the computer.


In the current environment, computer 120 is accessible to a computer 150 (e.g., by being in 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, the characterization module will be updated to reflect that the remote devices are not currently available.


The various input devices allow the characterization module or an application such as a context server (not shown) executing on the computer system 120 to monitor the user and the environment and to model their current condition. Such a model can be used by various applications, such as context clients, for various purposes. A model of the current conditions can include a variety of condition variables 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, and locations. The model of the current conditions can additionally include information added explicitly from other sources (e.g., application programs), as well as user-specified or system-learned defaults and preference information.


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, it is possible that the characterization module can be implemented on the non-portable computer, with the body-mounted computer replaced by a thin context 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.


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 can transmit information to those devices via a wireless or wired 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 and characterization module can be created for a variety of purposes.



FIG. 2 illustrates an exemplary computer system 200 on which an embodiment of the facility 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, such as a CD-ROM drive, a visual display 225, a speaker 226, and other devices 228. The memory preferably contains the facility 231, as well as information reflecting the current state of the facility (facility state) 232. The memory further contains characterization module 233, software modules 234, 235, and 238 that consume attributes and are therefore context clients, and software modules 236, 237, and 238 which provide attributes and are therefore context servers. While items 231-238 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.


Attributes represent measures of specific context elements such as ambient temperature, location and current user task. Each attribute preferably has the following properties: a name, a value, an uncertainty level, units, and a time stamp. Attributes provided through the characterization module by a context server may either be “measured,” in that they are directly received from an input device, or “derived,” in that they are the result of performing processing on values directly obtained from input devices other attributes. Indeed, a derived attribute may be produced by performing additional processing on other derived attributes. Context servers, in addition to providing attributes through the characterization module, may also provide other functions. For example, an application, such as an electronic mail application, may serve as a context server by providing attributes through the characterization module. In addition to the source of attributes described above, such an “expanded” context server may provide attributes relating to the other functions of the expanded context server. For example, an electronic mail application context server could provide an attribute indicating other new messages are waiting. Indeed, the same program module may operate both as a context client and a context server.


Two or more different context servers may preferably supply to the characterization module their own 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. These alternate values for the same attribute provided by different context servers are referred to as separate “instances” of the attribute. Separate instances of an attribute provided by different context servers may be based on data obtained from the same sensor, or may be based on data obtained from different sensors. The characterization module preferably provides a variety of different approaches, called “mediators,” for determining, when an attribute requested by a context client has more than one instance, what attribute value to provide in response to the attribute request.


When the characterization module obtains an attribute value from a context server, it preferably caches it for responding to future requests for the attribute from context clients. Such attribute requests may specify a specific instance of the attribute—that is, a specific context server from which the attribute is to be obtained—or may specify that the attribute is to be obtained by applying a particular mediator to whatever instances of the attribute are available, or may utilize a default mediator to mediate between available instances of the attribute. When the characterization module receives an attribute request from a context client, it identifies the attribute instances available to satisfy the request, and, for each, determines whether the value for the attribute instance cached by the characterization module was obtained sufficiently recently from the corresponding context server. If not, the characterization module requests an updated value for the attribute instance from the corresponding context server before performing any necessary mediation and returning a value to the context client.


The facility preferably supports the collaborative logging, in which attribute values produced in multiple computer systems are logged in a single consolidating computer system and there analyzed, or in which values logged in multiple computer systems are maintained, analyzed, or simulationed in a single consolidating computer system. Such collaborative logging is valuable where multiple computer systems are collecting and processing information about the same general subject. For example, information about a military battle collected and processed by separate computer systems carried by each of a number of soldiers may preferably by consolidated and analyzed by the facility in a strategist's computer system.


The characterization module preferably utilizes a plain-language, hierarchical, taxonometric attribute nomenclature to name attributes. The attribute names within the nomenclature are preferably specific so that there is no ambiguity as to what they represent. The characterization module preferably supports the extension of the nomenclature by adding new attribute names that conform to the hierarchical taxonomy of the nomenclature. The nomenclature preferably has attribute names relating to the user, such as user.position, user.speed, and user.direction, providing information about the user's position, speed, and direction, respectively. The nomenclature preferably contains attribute names for various user moods, or “affect,” such as user.mood.happiness, user.mood.anger, and user.mood.confusion. The nomenclature preferably includes attribute names for user activities, such as user.activity.driving, user.activity.eating, and user.activity.sleeping. The nomenclature preferably includes attribute names for user physiology values, such as user.physiology.pulse, user.physiology.body_temperature, and user.physiology.blood_pressure. The nomenclature preferably includes attribute names for similar attributes of people other than the user, such as person.John_Smith.mood.happiness. The nomenclature preferably includes attribute names for aspects of the computer system or “platform.” For example, the nomenclature preferably includes attribute names for aspects of the platform's user interface, such as platform.user_interface.oral_input_device_availability and platform.user_interface.visual_output_device_availability. The nomenclature preferably includes attribute names for attributes relating to the central processing unit, or “CPU,” of the platform, such as platform.cpu_load and platform.clock_speed. The nomenclature preferably also provides attribute names for aspects of the local environment, such as environment.local.time, environment.local.temperature, and environment.local.ambient_noise_level. The nomenclature preferably also includes attribute names for remote environments, such as environment.place.chicago.time and environment.place.san_diego.temperature. The nomenclature preferably further provides attribute names relating to specific applications. For example, the nomenclature preferably provides attribute names for aspects of an electronic mail application, such as application.mail.available, application.mail.new_messages_waiting, and application.mail.messages_waiting_to_be_sent. The nomenclature preferably further provides attribute names relating to data stored in or accessible to the computer system. The nomenclature preferably further provides attribute names relating to the connectivity of the computer system to other computer systems and similar devices, such as such as connectivity.Internet.available and connectivity.Internet.speed.


A single attribute may preferably be referred to by two or more names in the nomenclature. For example, the attribute names person.John_Smith.mood.happiness and user.mood.happiness may refer to the same attributes in a computer system whose user is John Smith.


In this manner, the attribute nomenclature used by the characterization module provides effective names for attributes relating to the user, the computer system, and the environment. Additional detail on the attribute nomenclature utilized by the facility is provided in U.S. patent application Ser. No. 09/724,902, entitled “Dynamically Exchanging Computer User's Context,” which is hereby incorporated by reference in its entirety.


Additional embodiments of the facility preferably identify attributes in a variety of ways other than the plain-language, hierarchical, taxonometric attribute nomenclature discussed above. For example, attributes may be identified by arbitrary identifiers, or by the identity of associated events or messages.


Additional details of the operation of the characterization module to obtain attribute values from context servers is provided by U.S. patent application Ser. No. 09/692,507, entitled “Interface for Exchanging Context Data”, which' is hereby incorporated by reference in its entirety.



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 attributes to the characterization module. For example, context server 330 provides an user.in_region attribute 331. It can be seen that context servers may provide more than one attribute. For example, context server 320 provides a user.location attribute 321 and an user.elevation attribute 322. It can further be seen that a single attribute may be provided by more than one context server. For example, context server 310 provides user.location attribute 311, while context server 320 provides user.location attribute 321.


The diagram further shows the facility storing attribute instance values obtained from context servers by the characterization modules in a logging database 360 that is comprised of one or more attribute instance logs.



FIG. 4 is a data structure diagram showing an attribute instance table in which the characterization module caches attribute instance values. The attribute instance table contains a row for each attribute instance created by a context server. The attribute instance table 400 contains rows 401-404, each corresponding to a different attribute instance. Each of these rows contains the following fields: an attribute name field 411 containing the name of the attribute, a context server name field 412 identifying the context server that created the attribute instance, a value field 413 containing the value of the attribute last provided by the context server, and uncertainty field 414 identifying the level of uncertainty of the value, a timestamp 415 indicating the time at which the value is effective, a units field 416 identifying the units for the value and the uncertainty, and an indication 417 of the number of context clients consuming the attribute instance. For example, row 401 indicates that an instance of the user.location attribute from the gps context server has the effective time of 13:11:04.023 on Feb. 22, 2000. Its value is 47° 36.73′ N, 122° 18.43′ W degrees and minutes, with an uncertainty of 0° 0.09′. It further indicates that two context clients are presently consuming this attribute instance. It should be noted, as shown, the user's location, expressed in terms of latitude and longitude, is maintained in a single attribute. In alternative embodiments, such a location could be maintained in a larger number of attributes. For example, rather than being maintained in a single user.location attribute, such a location could be distributed across four separate attributes: user.location.latitude.degrees, user.location.latitude.minutes, user.location.longitude.degrees, and user.location.longitude.minutes. The characterization module preferably adds row 404 to the attribute instance table when the location_region_analysis context server calls the CreateAttributeInstance function for the user.in_region attribute.



FIG. 5 is a data structure diagram showing a logging configuration table used by the facility to determine which attribute instances to log and when. The information stored in the logging configuration table may be provided by a variety of sources, including the user, the facility, applications, and other programs running on the computer system. In particular, the facility or another program may dynamically determine that a particular attribute instance should be logged, and accordingly add a logging configuration record to the logging configuration table. For example, a program may determine that an altitude parameter should be logged when it observes that the user's location corresponds to the location of a helipad.


The logging configuration table 500 has two rows 501 and 502. Each row corresponds to a particular attribute instance and specifies details of how that attribute instance is to be logged. Each row preferably contains a log name field 511 naming the logging which values of the attribute instance are to be stored; an attribute name field identifying the attribute name of the attribute instance to be logged; a context server name field 513 identifying the context server that is the source of the attribute instance to be logged; a logging frequency field 514 indicating the interval at which the attribute instance is to be logged; a maximum attribute value age field 515 indicating the maximum age of a cache value of the attribute instance that may be logged; an importance level field 516 indicating the importance of maintaining logged data for the attribute instance; a pre-logging processing field 517 indicating any processing to be performed on the attribute instance before storing in the log; a maintenance processing field 518 indicating any maintenance processing to be performed on log values of the attribute instance while they are stored in the log; and a last logged field 519 indicating the time at which the attribute instance was most recently logged.


For instance, row 502 indicates that the instance of the user.in_region attribute supplied by the location_region_analysis context server is to be logged in the user_log log. While only one unique log name is shown in the logging configuration table, the use of the log name field enables the facility to log different attribute instances in different logs, for instance, when the attribute instances relate to different subjects, or where the information contained in the attribute instances belongs to different entities. Row 502 further indicates that this attribute instance is to be logged every ten minutes, and that a cached value for this attribute instance may be logged, rather than obtaining a fresh value from the context server, if the effective time of the cached value is less than 30 seconds before the logging time. Row 502 further indicates that the importance level of maintaining log data for this attribute instance is six, an intermediate importance level. A high importance level may preferably be attributed to a particular attribute based on such factors as whether logging the attribute is legally required or required by a business policy, or whether the attribute has implications for the user's safety. Row 502 further indicates that logging of this attribute instance should be omitted where the current value of the attribute instance matches the last-logged value of the attribute instance. In contrast, because row 501 specifies a maximum attribute value age of 00:00:00.000, the facility must request a fresh value for the instance of the user.location attribute obtained from the GPS context server each time the attribute instance is to be logged. Row 502 indicates that the logged information for this attribute instance is to be summarized weekly, for example, by removing the rows from the log that indicate that the value of this attribute instance has changed during the previous week, and replacing them with a single row indicating the total number of times that the value of this attribute instance changed during the week. Other summarization techniques may summarize the number of times that the user was at each of a number of common locations, such as work, home, and health club. Row 502 further indicates that this attribute instance was last logged at 14:04:36.121 on Feb. 22, 2000. Based on the contents of fields 514 and 519, this attribute instance is scheduled to be next logged at 14:14:36.121 on Feb. 22, 2000.



FIG. 6 is a flow diagram showing the steps preferably performed by the facility in order to log attribute instances. In step 601, the facility identifies the logging configuration record specifying the next logging time. By examining FIG. 5, it can be determined that the logging configuration record shown in row 501 has the next logging time, which is 14:07:10.011 on Feb. 22, 2000. In step 601, the facility further waits until this next logging time arrives. In step 602, if the value cached in the characterization module for the attribute instance specified by the logging configuration record identified in step 601 satisfies the maximum attribute value age limit specified by this logging configuration record, then the facility continues in step 604, else the facility continues in step 603. In step 603, the facility uses the characterization module to obtain a fresh value of the specified attribute instance from the specified context server. For example, the facility uses the characterization module to obtain a fresh value of the user.location attribute from the GPS context server. In a further preferred embodiment, the facility in steps 602-603 may use a characterization module operating in a different computer system to obtain a value for the logged attribute instance. That is, the facility may log attributes obtained in computer systems other than the one in which the facility is executing.


After step 603, the facility continues in step 604. In step 604, the facility perform any pre-logging processing specified by the identified logging configuration record. Examples of pre-logging processing techniques preferably supported by the facility include summarization, in which several values of one attribute instance, or values of a number of different attribute instances are summarized in a single log record; abstraction, in which the value of one or more attribute instances, are abstracted into a higher-level conceptualization; and compression, in which information to be stored in the log record is modified to fit in a smaller space.


In step 605, if the pre-logging processing performed in step 604 obviates the current logging iteration, then the facility continues in step 607 to abort the current logging iteration, else the facility continues in step 606. In step 606, the facility stores a record for the specified attribute instance in the specified log. Those skilled in the art will appreciate that the facility may be straightforwardly adapted to support additional techniques of a similar nature. To maximize the accessibility of the data stored in the log, the log record is preferably stored as tab-delimited ASCII text or another widely-supported format. The contents of a stored log record are discussed further in conjunction with FIG. 7 below. After step 606, the facility continues in step 607. In step 607, the facility updates the last logged field of the logging configuration record with the current time. After step 607, the facility continues in step 601 to identify the logging configuration record specifying the next logging time.



FIG. 7 is a data structure diagram showing an attribute log table produced by the facility. The attribute log table 700 contains rows 701-704, each corresponding to a single logged value of an attribute instance. Each row contains an attribute name field 711 indicating the attribute name of the logged attribute instance; a context field server field 712 identifying the context server from which the attribute instance is obtained; a value field 713 containing the logged value for the attribute instance; an uncertainty field 714 indicating the level of uncertainty of the logged value; a time-stamp field 715 indicating the effective time at which the logged value was most accurate; a units field 716 indicating the units in which the value and uncertainty are expressed; a format version field 717 indicating the version of the format in which the value and uncertainty are expressed; a flags field 718 containing additional information about the logged attribute instance; and a logged time field 719 indicating the time at which the value of the attribute instance was logged.


For example, it can be seen from row 704 that the most recently-logged attribute instance is the instance of the user.location attribute provided by the GPS context server. The logged value of this attribute instance is 47° 38.72′ N, 122° 18.22′ W, with an uncertainty of 0° 0.10′. This attribute instance value has an effective time of 14:05:10.008 on Feb. 22, 2000. The value and uncertainty are expressed in the units of degrees and minutes, the format version is 1.01, and there are no flags stored for attribute instance value. This attribute log record was generated at 14:05:10.011 on Feb. 22, 2000.



FIG. 8 is a flow diagram showing the steps preferably performed by the facility in order to maintain an attribute log. In steps 801-805, the facility loops through each attribute log maintenance cycle. Those skilled in the art will appreciate that the facility could be configured to perform attribute log maintenance cycles at a variety of frequencies, such as every hour, every day, or every month. In steps 802-804, the facility loops through each log configuration record that specifies a maintenance technique in the maintenance processing field 518. In step 803, the facility applies the specified maintenance technique to the log records corresponding to the logging configuration record, which may include log records stored in multiple logs and/or in multiple locations. Examples of maintenance techniques preferably supported by the facility include compression, summarization and abstraction, discussed above; thinning, in which some log records for an attribute instance are deleted from the log, while others are retained in the log; discarding, in which all values of an attribute instance during a particular time period are deleted from the log; and archiving, in which log records for a particular attribute instance are removed from the log and stored in another location, such as on a back-up storage device. Those skilled in the art will appreciate that the facility may be straightforwardly adapted to support additional techniques of a similar nature.


The facility preferably makes decisions regarding when and to which attribute instances to apply maintenance techniques based on a variety of factors, including the relative importance level specified for various attribute instances, as well as other indications of the need to retain the logged information, such as an indication that logging information for a particular attribute instance has become available from another source, such as a database accessible via the Internet.


In step 804, if additional logging Configuration records remain, then the facility continues in step 802 to process the next logging configuration record. In step 805, the facility continues in step 801 to process the next context log maintenance cycle.



FIG. 9 is a flow diagram showing the steps preferably performed by the facility to analyze log records for attribute instances. In step 901, the facility receives an analysis specification specifying an attribute instance, including the attribute name of the attribute instance and the context server from which the attribute instance is obtained, the time period in which to analyze the logged attribute instance, and an analysis technique. Such a specification may be received from the user via the user interface, or from an application or other program whose functionality includes logged attribute analysis.


Examples of analysis techniques preferably supported by the facility include the following: summarization, discussed above; combination, in which values of several different attribute instances from the same time period are combined; generating a new value of the context attribute that is made available via the characterization module; retrospective application of rules, in which a rule designed to be applied to real-time values of an attribute is applied to logged values of that attribute; and pattern analysis, where recurring patterns are identified in the logged attribute values, or where a pattern is identified in the logged attribute data that matches a pattern specified outside the logged attribute data—for example, matching a series of logged electrocardiogram attribute values to an external electrocardiogram model indicating a high likelihood of heart disease; and ongoing analysis, wherein interim results produced during earlier analysis are retrieved, employed in current processing, augmented, and stored, in some cases separately from the log. Those skilled in the art will appreciate that the facility may be straightforwardly adapted to support additional techniques of a similar nature.


In step 902, the facility applies the specified analysis technique to logged values of the specified attribute instance having effective times during the specified period. After step 902, the facility continues in 901 to receive the next analysis specification.



FIG. 10 is a flow diagram showing the steps preferably performed by the facility in order to conduct a context simulation. In step 1001, the facility receives a simulation specification specifying one or more attribute instances, a time period, and a speed for a new simulation. Such a specification may be received from the user via the user interface, or from an application or other program whose functionality includes logged attribute analysis. In simulation step 1002, the facility performs the simulation by causing the characterization module to, when it receives a request for one of the specified attribute instances, return a logged value for the attribute instance rather than returning a value for the attribute instance generated in real-time by the corresponding context server. (The characterization module preferably continues to respond to attribute instance requests for other attribute instances with a value for the attribute instance generated in real-time by the corresponding context server. The facility is preferably configurable, however, to disable provision of real-time, values for some or all of the other attribute instances.) As the simulation advances in time, the logged times of the logged values that are returned are also advanced in accordance with the specified simulation speed. Simulations may preferably be used for compliance testing or other testing, to repeat an experience, or for other purposes. In one preferred embodiment, scheduled logging is suspended during performance of the simulation in step 1002. After step 1002, the facility continues in step 1001 to receive the next simulation specification.



FIG. 11 is a data flow diagram showing the operation of the facility without a characterization module. It can be seen in FIG. 11 that context sewers 1110, 1120, and 1130 provide attributes directly to context clients 1130, 1140, and 1150. For example, it can be seen that context server 1120 provides a user.elevation attribute 1122 directly to context client 1150. In this embodiment, the context client may itself cache attribute values recently obtained from a context sewer. 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 1140 may mediate between the instance 1111 of the user.location attribute provided by context server 1110 and the instance 1121 of the user.location attribute provided by context server 1120.


In this embodiment, the facility preferably uses a logging context client 1160 to obtain attribute instance values from a context server and store them in a logging database 1161. For example, the diagram shows that the logging context client obtains values of the instance of the user.location attribute supplied by the gps context sewer and the instance of the in_region attribute supplied by the region_analysis context server and stores them in the logging database.


It will be understood by those skilled in the art that the above-described facility could be adapted or extended in various ways. For example, the facility may be implemented in computing devices other than wearable computers, including other types of mobile computing devices, such as personal digital assistants. The facility may further be implemented on various types of stationary and/or distributed computing devices, as well as non-traditional computing devices, such as smart appliances. Further, the facility may use attribute instance tables, logging configuration tables, and attribute log tables of various forms other than those shown above or may maintain its state in ways that do not involve the use of such tables. The facility may also utilize various additional pre-logging processing, log maintenance, and log analysis techniques beyond those described above. In addition to the information discussed above, additional information may be included in a log record, including the values of other attributes. Log records may preferably be ordered and/or indexed based upon any, all, or of the information contained in them.


While the foregoing description makes reference to preferred embodiments, the scope of the invention is defined solely by the claims that follow and the elements recited therein.

Claims
  • 1. A method for retroactively analyzing a log of context attribute values associated with a user, each context attribute value contained by the log is stored with an indication of a corresponding data item and an indexing value, the method comprising: receiving from at least one application a specification for analyzing values among the stored values, the specification specifying one or more context attributes, a range of indexing values that are effective times associated with data items, and an analysis technique applicable to the data items, the analysis technique includes at least one of summarization, combination, new value generation, ongoing analysis, pattern analysis, or retrospective application of rules, the retrospective application of rules includes a determination of a result that would have been produced had a rule been applied to analyze the specified context attribute values at the time the values were generated, the rule configured for analyzing context attribute values in real-time to produce a result and is adoptable for future real-time application when it is determined that a successful result would have been produced had the rule been applied to analyze the specified context attribute values at the time the values were generated;retrieving stored values for the specified context attributes associated with the user of a computing device within the specified range of indexing values, a first subset of the stored values for one of the specified context attributes being associated with a first source device, and a second subset for the stored values for the one of the specified context attributes being associated with a second source device;applying the specified analysis technique to the retrieved values to produce an analysis of the context attributes that infers information representing at least one of the user's physical activity, emotional state, or cognitive load; andoperating the at least one application to receive and use the inferred information.
  • 2. The method of claim 1, wherein: the specified analysis technique is a summarization technique that summarizes values of one context attribute instance or values of a plurality of context attribute instances in a single log record.
  • 3. The method of claim 1, wherein the first source device is a source of geographic information, and the second source device is a source of physiological information relating to the user of the computing device.
  • 4. The method of claim 1, wherein: the specified analysis technique identifies a recurring pattern in the retrieved context attribute values; andthe method further comprises: determining that a most recent pattern recurrence is identified in context attribute values having effective times only shortly preceding the present time;determining that the retrieved context values include context values reflecting an action taken by a user subsequent and proximal to at least one earlier occurrence of the pattern; andbased upon both determinations, making preparations in anticipation of repetition of the action by the user.
  • 5. A computing device comprising: a memory; anda processor that retroactively analyzes a log of context attribute values, each context attribute value contained by the log being stored with an indication of a corresponding data item, a specification specifying one or more context attributes associated with the context attribute values of the log, a range of effective times associated with the data items, and an analysis technique applicable to the data items, the analysis technique includes an identification of a recurring pattern in the one or more context attribute values, a first determination that a most recent pattern recurrence is identified in the one or more context attribute values having effective times only shortly before a present time, a second determination that the one or more context attribute values include context attribute values reflecting an action taken by a user subsequent and proximal to at least one earlier occurrence of the pattern, and a making of preparations in anticipation of repetition of the action by the user based on the first and the second determinations, the processor configured to act as: a value retrieval subsystem that, based on the specification, retrieves stored values from the memory for one or more specified context attributes, wherein a first subset of the retrieved values associated with one of the specified context attributes is associated with a first data source providing geographic information, and a second subset of the retrieved values associated with a second data source providing physiological information about a user; andan analysis subsystem that applies the specified analysis technique to the retrieved values to determine a status of the user based on the geographic information and the physiological information.
  • 6. The computing device of claim 5, wherein the computing device is a mobile computer system.
  • 7. The computing device of claim 5, wherein the computing device in which the method is performed is a body-supported computer system.
  • 8. The computing device of claim 5, wherein the analysis subsystem determines that the status of the user relates to embarking on a mode of transportation.
  • 9. The computing device of claim 5, wherein: the value retrieval subsystem retrieves stored values from the memory for the one or more specified context attributes based on the specification; andthe analysis subsystem applies the analysis technique selected based on the specification.
  • 10. The computing device of claim 5, wherein the analysis subsystem determines a cognitive load of the user.
  • 11. The computing device of claim 5, wherein the analysis technique further includes at least one of summarization, combination, retrospective application of rules, or ongoing analysis.
  • 12. A computer-readable storage device having computer-executable instructions stored thereon, which when executed perform acts, comprising: for each of a set of data items relating to experiences of a human user of a computing device, enabling at least one processor to iteratively obtain and store values of a selected subset of the set of data items, each stored value of a data item being stored with an indication of the data item and an indication of an effective time of the stored value, at least one data item obtaining values from a plurality of data sources, the data sources comprising at least one of a source of geographic information and physiological information;enabling the at least one processor to receive, from at least one application that performs logged context attribute analysis, a specification for analyzing values among the stored values that specifies one or more data items, a range of effective times, and an analysis technique applicable to the data items, the analysis technique includes determining a result that would have been produced had a rule been applied to analyze the specified context attribute values at the time the values were generated, the rule configured for analyzing context attribute values in real-time to produce a result, the rule adopted for future real-time application when it is determined that a successful result would have been produced had the rule been applied to analyze the specified context attribute values at the time the values were generated;enabling the at least one processor to retrieve stored values for the specified data items within the specified range of effective times and retrieving the real time values for the remaining non-specified data items;enabling the at least one processor to apply the specified analysis technique to the retrieved values using the specified one or more context attributes to produce an analysis of experiences of the human user; andenabling the at least one processor to select an operating characteristic of the computing device based on inferring a current or future status of the human user based on the analysis of experiences of the human user.
  • 13. The computer-readable storage device of claim 12, wherein said enabling the at least one processor to select the operating characteristic of the computing device comprises enabling the at least one processor to select an output behavior for the computing device.
  • 14. The computer-readable storage device of claim 13, wherein said enabling the at least one processor to select the output behavior comprises presenting information in a format that restricts access to the information.
  • 15. The computer-readable storage device of claim 12, further comprising: enabling the at least one processor to receive a specification of a user-selected mediation technique.
  • 16. The computer-readable storage device of claim 12, wherein said enabling the at least one processor to store values of the selected subset of the set of data items comprises: enabling the at least one processor to store the values in a sparse matrix.
  • 17. The computer-readable storage device of claim 12, further comprising, enabling the at least one processor to: receive a user specification of a user-selected mediation technique; andemploy the user-selected mediation technique to select which one of the plurality of data sources will supply values for the analysis.
  • 18. The computer-readable storage device of claim 12, wherein the computing device is a general-purpose mobile computer system.
  • 19. The computer-readable storage device of claim 12, wherein the analysis technique further includes at least one of summarization, combination, pattern analysis, or ongoing analysis.
  • 20. The computer-readable storage device of claim 12, wherein the experiences of the human user include a physical activity, an emotional state, or a cognitive load of the human user.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No. 10/984,511, filed Nov. 9, 2004, which is a continuation of Ser. No. 09/541,326, filed Apr. 2, 2000, which 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” filed Dec. 18, 1998 (now U.S. Pat. No. 6,466,232) and a Continuation-In-Part of U.S. patent application Ser. No. 09/464,659, entitled “STORING AND RECALLING INFORMATION TO AUGMENT HUMAN MEMORIES” filed Dec. 15, 1999 (now U.S. Pat. No. 6,513,046). These applications are hereby incorporated by reference in their entirety.

US Referenced Citations (420)
Number Name Date Kind
3973251 Stephans Aug 1976 A
4283712 Goody Aug 1981 A
4458331 Amezcua et al. Jul 1984 A
4569026 Best Feb 1986 A
4815030 Cross et al. Mar 1989 A
4905163 Garber et al. Feb 1990 A
4916441 Gombrich Apr 1990 A
4970683 Harshaw et al. Nov 1990 A
4991087 Burkowski et al. Feb 1991 A
5032083 Friedman Jul 1991 A
5133075 Risch Jul 1992 A
5201034 Matsuura et al. Apr 1993 A
5208449 Eastman et al. May 1993 A
5214757 Mauney et al. May 1993 A
5227614 Danielson et al. Jul 1993 A
5237684 Record et al. Aug 1993 A
5251294 Abelow Oct 1993 A
5267147 Harshaw et al. Nov 1993 A
5278946 Shimada et al. Jan 1994 A
5285398 Janik Feb 1994 A
5317568 Bixby et al. May 1994 A
5327529 Fults et al. Jul 1994 A
5335276 Thompson et al. Aug 1994 A
5339395 Pickett et al. Aug 1994 A
5349654 Bond et al. Sep 1994 A
5353399 Kuwamoto et al. Oct 1994 A
5388198 Layman et al. Feb 1995 A
5398021 Moore Mar 1995 A
5416730 Lookofsky May 1995 A
5454074 Hartel et al. Sep 1995 A
5470233 Fruchterman et al. Nov 1995 A
5471629 Risch Nov 1995 A
5481667 Bieniek et al. Jan 1996 A
5493692 Theimer et al. Feb 1996 A
5506580 Whiting et al. Apr 1996 A
5513646 Lehrman et al. May 1996 A
5522024 Hiraga et al. May 1996 A
5522026 Records et al. May 1996 A
5535323 Miller et al. Jul 1996 A
5537618 Boulton et al. Jul 1996 A
5539665 Lamming et al. Jul 1996 A
5544321 Theimer et al. Aug 1996 A
5553609 Chen et al. Sep 1996 A
5555376 Theimer et al. Sep 1996 A
5559520 Barzegar et al. Sep 1996 A
5560012 Ryu et al. Sep 1996 A
5566337 Szymanski et al. Oct 1996 A
5568645 Morris et al. Oct 1996 A
5572401 Carroll Nov 1996 A
5592664 Starkey Jan 1997 A
5601435 Quy Feb 1997 A
5603054 Theimer et al. Feb 1997 A
5611050 Theimer et al. Mar 1997 A
5636146 Flentov et al. Jun 1997 A
5642303 Small et al. Jun 1997 A
5646629 Loomis et al. Jul 1997 A
5659746 Bankert et al. Aug 1997 A
5675358 Bullock et al. Oct 1997 A
5689619 Smyth Nov 1997 A
5689708 Regnier et al. Nov 1997 A
5701894 Cherry et al. Dec 1997 A
5704366 Tacklind et al. Jan 1998 A
5710884 Dedrick Jan 1998 A
5715451 Marlin Feb 1998 A
5717747 Boyle, III et al. Feb 1998 A
5719744 Jenkins et al. Feb 1998 A
5726660 Purdy et al. Mar 1998 A
5726688 Siefert et al. Mar 1998 A
5738102 Lemelson Apr 1998 A
5740037 McCann et al. Apr 1998 A
5742279 Yamamoto et al. Apr 1998 A
5745110 Ertemalp Apr 1998 A
5751260 Nappi et al. May 1998 A
5752019 Rigoutsos et al. May 1998 A
5754938 Herz et al. May 1998 A
5761662 Dasan Jun 1998 A
5769085 Kawakami et al. Jun 1998 A
5781913 Felsenstein et al. Jul 1998 A
5787234 Molloy Jul 1998 A
5787279 Rigoutsos Jul 1998 A
5790974 Tognazzini Aug 1998 A
5796952 Davis et al. Aug 1998 A
5798733 Ethridge Aug 1998 A
5806079 Rivette et al. Sep 1998 A
5812865 Theimer et al. Sep 1998 A
5818446 Bertram et al. Oct 1998 A
5826253 Bredenberg Oct 1998 A
5831594 Tognazzini et al. Nov 1998 A
5832296 Wang et al. Nov 1998 A
5835087 Herz et al. Nov 1998 A
5842223 Bristor Nov 1998 A
5852814 Allen Dec 1998 A
5867171 Murata et al. Feb 1999 A
5873070 Bunte et al. Feb 1999 A
5878274 Kono et al. Mar 1999 A
5879163 Brown et al. Mar 1999 A
5881231 Takagi et al. Mar 1999 A
5899963 Hutchings May 1999 A
5902347 Backman et al. May 1999 A
5905492 Straub et al. May 1999 A
5910799 Carpenter et al. Jun 1999 A
5911132 Sloane Jun 1999 A
5913030 Lotspiech et al. Jun 1999 A
5924074 Evans Jul 1999 A
5930501 Neil Jul 1999 A
5937160 Davis et al. Aug 1999 A
5938721 Dussell et al. Aug 1999 A
5942986 Shabot et al. Aug 1999 A
5945988 Williams et al. Aug 1999 A
5948041 Abo et al. Sep 1999 A
5953718 Wical Sep 1999 A
5959611 Smailagic et al. Sep 1999 A
5963914 Skinner et al. Oct 1999 A
5966126 Szabo Oct 1999 A
5966533 Moody Oct 1999 A
5966710 Burrows Oct 1999 A
5971580 Hall et al. Oct 1999 A
5974262 Fuller et al. Oct 1999 A
5977968 Le Blanc Nov 1999 A
5980096 Thalhammer-Reyero Nov 1999 A
5983335 Dwyer, III Nov 1999 A
5991687 Hale et al. Nov 1999 A
5991735 Gerace Nov 1999 A
5995956 Nguyen Nov 1999 A
5999932 Paul Dec 1999 A
5999943 Nori et al. Dec 1999 A
5999975 Kittaka et al. Dec 1999 A
6002982 Fry Dec 1999 A
6003082 Gampper et al. Dec 1999 A
6006251 Toyouchi et al. Dec 1999 A
6012152 Douik et al. Jan 2000 A
6014638 Burge et al. Jan 2000 A
6023729 Samuel et al. Feb 2000 A
6031455 Grube et al. Feb 2000 A
6035264 Donaldson et al. Mar 2000 A
6041331 Weiner et al. Mar 2000 A
6041365 Kleinerman Mar 2000 A
6044415 Futral et al. Mar 2000 A
6047301 Bjorklund et al. Apr 2000 A
6047327 Tso et al. Apr 2000 A
6055516 Johnson et al. Apr 2000 A
6061610 Boer May 2000 A
6061660 Eggleston et al. May 2000 A
6064943 Clark, Jr. et al. May 2000 A
6067084 Fado et al. May 2000 A
6081814 Mangat et al. Jun 2000 A
6085086 La Porta et al. Jul 2000 A
6088689 Kohn et al. Jul 2000 A
6091411 Straub et al. Jul 2000 A
6092101 Birrell et al. Jul 2000 A
6094625 Ralston Jul 2000 A
6098065 Skillen et al. Aug 2000 A
6105063 Hayes, Jr. Aug 2000 A
6108197 Janik Aug 2000 A
6108665 Bair et al. Aug 2000 A
6112246 Horbal et al. Aug 2000 A
6122348 French-St. George et al. Sep 2000 A
6122657 Hoffman, Jr. et al. Sep 2000 A
6122960 Hutchings et al. Sep 2000 A
6127990 Zwern Oct 2000 A
6128663 Thomas Oct 2000 A
6131067 Girerd et al. Oct 2000 A
6134532 Lazarus et al. Oct 2000 A
6154745 Kari et al. Nov 2000 A
6155960 Roberts et al. Dec 2000 A
6164541 Dougherty et al. Dec 2000 A
6169976 Colosso Jan 2001 B1
6185534 Breese et al. Feb 2001 B1
6188399 Voas et al. Feb 2001 B1
6195622 Altschuler et al. Feb 2001 B1
6198394 Jacobsen et al. Mar 2001 B1
6199099 Gershman et al. Mar 2001 B1
6199102 Cobb Mar 2001 B1
6215405 Handley et al. Apr 2001 B1
6218958 Eichstaedt et al. Apr 2001 B1
6230111 Mizokawa May 2001 B1
6236768 Rhodes et al. May 2001 B1
6256633 Dharap Jul 2001 B1
6262720 Jeffrey et al. Jul 2001 B1
6263268 Nathanson Jul 2001 B1
6263317 Sharp et al. Jul 2001 B1
6272470 Teshima Aug 2001 B1
6272507 Pirolli et al. Aug 2001 B1
6282517 Wolfe et al. Aug 2001 B1
6282537 Madnick et al. Aug 2001 B1
6285757 Carroll et al. Sep 2001 B1
6285889 Nykanen et al. Sep 2001 B1
6289316 Aghili et al. Sep 2001 B1
6289513 Bentwich Sep 2001 B1
6292796 Drucker et al. Sep 2001 B1
6294953 Steeves Sep 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6305007 Mintz Oct 2001 B1
6305221 Hutchings Oct 2001 B1
6308203 Itabashi et al. Oct 2001 B1
6311162 Reichwein et al. Oct 2001 B1
6314384 Goetz Nov 2001 B1
6317718 Fano Nov 2001 B1
6321158 DeLorme et al. Nov 2001 B1
6321279 Bonola Nov 2001 B1
6324569 Ogilvie et al. Nov 2001 B1
6327535 Evans et al. Dec 2001 B1
6349307 Chen Feb 2002 B1
6353398 Amin et al. Mar 2002 B1
6353823 Kumar Mar 2002 B1
6356905 Gershman et al. Mar 2002 B1
6363377 Kravets et al. Mar 2002 B1
6385589 Trusheim et al. May 2002 B1
6392670 Takeuchi et al. May 2002 B1
6401085 Gershman et al. Jun 2002 B1
6405159 Bushey et al. Jun 2002 B2
6405206 Kayahara Jun 2002 B1
6418424 Hoffberg et al. Jul 2002 B1
6421700 Holmes et al. Jul 2002 B1
6427142 Zachary et al. Jul 2002 B1
6430531 Polish Aug 2002 B1
6438618 Lortz et al. Aug 2002 B1
6442549 Schneider Aug 2002 B1
6442589 Takahashi et al. Aug 2002 B1
6442620 Thatte et al. Aug 2002 B1
6446076 Burkey et al. Sep 2002 B1
6446109 Gupta Sep 2002 B2
6460036 Herz Oct 2002 B1
6462759 Kurtzberg et al. Oct 2002 B1
6466232 Newell et al. Oct 2002 B1
6477117 Narayanaswami et al. Nov 2002 B1
6483485 Huang et al. Nov 2002 B1
6484200 Angal et al. Nov 2002 B1
6487552 Lei et al. Nov 2002 B1
6490579 Gao et al. Dec 2002 B1
6505196 Drucker et al. Jan 2003 B2
6507567 Willars Jan 2003 B1
6507845 Cohen et al. Jan 2003 B1
6513046 Abbott, III et al. Jan 2003 B1
6519552 Sampath et al. Feb 2003 B1
6526035 Atarius et al. Feb 2003 B1
6529723 Bentley Mar 2003 B1
6539336 Vock et al. Mar 2003 B1
6542889 Aggarwal et al. Apr 2003 B1
6546005 Berkley et al. Apr 2003 B1
6546425 Hanson et al. Apr 2003 B1
6546554 Schmidt et al. Apr 2003 B1
6549915 Abbott, III et al. Apr 2003 B2
6549944 Weinberg et al. Apr 2003 B1
6553336 Johnson et al. Apr 2003 B1
6563430 Kemink et al. May 2003 B1
6568595 Russell et al. May 2003 B1
6571279 Herz et al. May 2003 B1
6578019 Suda et al. Jun 2003 B1
6615197 Chai Sep 2003 B1
6625135 Johnson et al. Sep 2003 B1
6636831 Profit, Jr. et al. Oct 2003 B1
6643682 Todd et al. Nov 2003 B1
6643684 Malkin et al. Nov 2003 B1
6652283 Van Schaack et al. Nov 2003 B1
6661437 Miller et al. Dec 2003 B1
6672506 Swartz et al. Jan 2004 B2
6697836 Kawano et al. Feb 2004 B1
6704722 Wang Baldonado Mar 2004 B2
6704785 Koo et al. Mar 2004 B1
6704812 Bakke et al. Mar 2004 B2
6707476 Hochstedler Mar 2004 B1
6712615 Martin Mar 2004 B2
6714977 Fowler et al. Mar 2004 B1
6718332 Sitaraman et al. Apr 2004 B1
6738040 Jahn et al. May 2004 B2
6738759 Wheeler et al. May 2004 B1
6738975 Yee et al. May 2004 B1
6741188 Miller et al. May 2004 B1
6741610 Volftsun et al. May 2004 B1
6747675 Abbott et al. Jun 2004 B1
6751620 Orbanes et al. Jun 2004 B2
6766245 Padmanabhan Jul 2004 B2
D494584 Schlieffers et al. Aug 2004 S
6791580 Abbott et al. Sep 2004 B1
6795806 Lewis et al. Sep 2004 B1
6796505 Pellaumail et al. Sep 2004 B2
6801223 Abbott et al. Oct 2004 B1
6812937 Abbott et al. Nov 2004 B1
6829639 Lawson et al. Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6834208 Gonzales et al. Dec 2004 B2
6837436 Swartz et al. Jan 2005 B2
6842877 Robarts et al. Jan 2005 B2
6850252 Hoffberg Feb 2005 B1
6853966 Bushey et al. Feb 2005 B2
6868525 Szabo Mar 2005 B1
6874017 Inoue et al. Mar 2005 B1
6874127 Newell et al. Mar 2005 B2
6885734 Eberle et al. Apr 2005 B1
6899539 Stallman et al. May 2005 B1
6920616 Abbott et al. Jul 2005 B1
6963899 Fernandez et al. Nov 2005 B1
6968333 Abbott et al. Nov 2005 B2
7000187 Messinger et al. Feb 2006 B2
7010501 Roslak et al. Mar 2006 B1
7010603 Martin, Jr. et al. Mar 2006 B2
7040541 Swartz et al. May 2006 B2
7046263 Abbott et al. May 2006 B1
7055101 Abbott et al. May 2006 B2
7058893 Abbott et al. Jun 2006 B2
7058894 Abbott et al. Jun 2006 B2
7062715 Abbott et al. Jun 2006 B2
7063263 Swartz et al. Jun 2006 B2
7076737 Abbott et al. Jul 2006 B2
7080322 Abbott et al. Jul 2006 B2
7089497 Abbott et al. Aug 2006 B2
7096253 Vinson et al. Aug 2006 B2
7103806 Horvitz Sep 2006 B1
7107539 Abbott et al. Sep 2006 B2
7110764 Blair et al. Sep 2006 B1
7120558 McIntyre et al. Oct 2006 B2
7124125 Cook et al. Oct 2006 B2
7137069 Abbott et al. Nov 2006 B2
7143093 Bracho et al. Nov 2006 B1
7155456 Abbott, III et al. Dec 2006 B2
7162473 Dumais et al. Jan 2007 B2
7171378 Petrovich et al. Jan 2007 B2
7195157 Swartz et al. Mar 2007 B2
7203906 Abbott et al. Apr 2007 B2
7225229 Abbott et al. May 2007 B1
7231439 Abbott et al. Jun 2007 B1
7260453 Poier et al. Aug 2007 B2
7349894 Barth et al. Mar 2008 B2
7360152 Capps et al. Apr 2008 B2
7385501 Miller et al. Jun 2008 B2
7386477 Fano Jun 2008 B2
7392486 Gyde et al. Jun 2008 B1
7395221 Doss et al. Jul 2008 B2
7444594 Abbott et al. Oct 2008 B2
7464153 Abbott et al. Dec 2008 B1
7478331 Abbott et al. Jan 2009 B2
7512889 Newell et al. Mar 2009 B2
7533052 Tilfors et al. May 2009 B2
7533082 Abbott et al. May 2009 B2
7561200 Garvey, III et al. Jul 2009 B2
7571218 Tanaka et al. Aug 2009 B2
7614001 Abbott et al. Nov 2009 B2
7647400 Abbott et al. Jan 2010 B2
7689919 Abbott et al. Mar 2010 B2
7734780 Abbott et al. Jun 2010 B2
7739210 Horvitz et al. Jun 2010 B2
7739607 Abbott et al. Jun 2010 B2
7779015 Abbott et al. Aug 2010 B2
7827281 Abbott et al. Nov 2010 B2
7831679 Apacible et al. Nov 2010 B2
7877686 Abbott et al. Jan 2011 B2
7925995 Krumm et al. Apr 2011 B2
7945859 Abbott et al. May 2011 B2
7979252 Horvitz et al. Jul 2011 B2
7991718 Horvitz et al. Aug 2011 B2
8020104 Robarts et al. Sep 2011 B2
8103665 Abbott et al. Jan 2012 B2
20010030664 Shulman et al. Oct 2001 A1
20010040590 Abbott et al. Nov 2001 A1
20010040591 Abbott et al. Nov 2001 A1
20010043231 Abbott et al. Nov 2001 A1
20010043232 Abbott et al. Nov 2001 A1
20020032689 Abbott et al. Mar 2002 A1
20020044152 Abbott et al. Apr 2002 A1
20020052930 Abbott et al. May 2002 A1
20020052963 Abbott et al. May 2002 A1
20020054130 Abbott et al. May 2002 A1
20020054174 Abbott et al. May 2002 A1
20020078204 Newell et al. Jun 2002 A1
20020080155 Abbott et al. Jun 2002 A1
20020080156 Abbott et al. Jun 2002 A1
20020083025 Robarts et al. Jun 2002 A1
20020083158 Abbott et al. Jun 2002 A1
20020087525 Abbott et al. Jul 2002 A1
20020099817 Abbott et al. Jul 2002 A1
20020147880 Wang Baldonado Oct 2002 A1
20020191034 Sowizral et al. Dec 2002 A1
20030046401 Abbott et al. Mar 2003 A1
20030154476 Abbott et al. Aug 2003 A1
20030186201 Martin Oct 2003 A1
20030229900 Reisman Dec 2003 A1
20040088328 Cook et al. May 2004 A1
20040133600 Homer Jul 2004 A1
20040186854 Choi Sep 2004 A1
20040201500 Miller et al. Oct 2004 A1
20040215663 Liu et al. Oct 2004 A1
20040267700 Dumais et al. Dec 2004 A1
20040267812 Harris et al. Dec 2004 A1
20050027704 Hammond et al. Feb 2005 A1
20050034078 Abbott et al. Feb 2005 A1
20050066282 Abbott et al. Mar 2005 A1
20050086243 Abbott et al. Apr 2005 A1
20050160113 Sipusic et al. Jul 2005 A1
20050165843 Capps et al. Jul 2005 A1
20050193017 Kim Sep 2005 A1
20050266858 Miller et al. Dec 2005 A1
20050272442 Miller et al. Dec 2005 A1
20060004680 Robarts et al. Jan 2006 A1
20060019676 Miller et al. Jan 2006 A1
20060136393 Abbott et al. Jun 2006 A1
20060259494 Watson et al. Nov 2006 A1
20070022384 Abbott et al. Jan 2007 A1
20070043459 Abbott et al. Feb 2007 A1
20070089067 Abbott et al. Apr 2007 A1
20070130524 Abbott et al. Jun 2007 A1
20070168502 Abbott et al. Jul 2007 A1
20070185864 Budzik et al. Aug 2007 A1
20070266318 Abbott et al. Nov 2007 A1
20080090591 Miller et al. Apr 2008 A1
20080091537 Miller et al. Apr 2008 A1
20080147775 Abbott et al. Jun 2008 A1
20080161018 Miller et al. Jul 2008 A1
20080313271 Abbott et al. Dec 2008 A1
20090013052 Robarts et al. Jan 2009 A1
20090055752 Abbott et al. Feb 2009 A1
20090094524 Abbott et al. Apr 2009 A1
20090150535 Abbott et al. Jun 2009 A1
20090228552 Abbott et al. Sep 2009 A1
20090234878 Herz et al. Sep 2009 A1
20090282030 Abbott et al. Nov 2009 A1
20100217862 Abbott et al. Aug 2010 A1
20100257235 Abbott et al. Oct 2010 A1
20110161276 Krumm et al. Jun 2011 A1
20110288839 Horvitz et al. Nov 2011 A1
Foreign Referenced Citations (20)
Number Date Country
0 661 627 Jul 1995 EP
0 759 591 Feb 1997 EP
0 801 342 Oct 1997 EP
0 823 813 Feb 1998 EP
0 846 440 Jun 1998 EP
0 924 615 Jun 1999 EP
05260188 Oct 1993 JP
09091112 Apr 1997 JP
11306002 Nov 1999 JP
WO-9008361 Jul 1990 WO
WO-9531773 Nov 1995 WO
WO-9703434 Jan 1997 WO
WO-9734388 Sep 1997 WO
WO-9800787 Jan 1998 WO
WO-9847084 Oct 1998 WO
WO 9917228 Apr 1999 WO
WO-9926180 May 1999 WO
WO-9966394 Dec 1999 WO
WO-9967698 Dec 1999 WO
WO-0036493 Jun 2000 WO
Non-Patent Literature Citations (129)
Entry
[No Author Listed] “Affective Understanding,” Modeling and Responding to User Affect, http://www.media.mit.edu/affect/AC—research/understanding.html, pp. 1-3 (Accessed Oct. 2, 1998).
[No Author Listed] “Alps GlidePoint,” http://www.alps.com/p17.html, p. 1 (Accessed Oct. 2, 1998).
[No Author Listed] “BridgeVIEW and LabVIEW G Programming Reference Manual,” Jan. 1998, National Instruments Corporation, http://www.ni.com/pdf/manuals/321296b.pdf. Last accessed Dec. 7, 2008, 667 pages.
[No Author Listed] “Context Recognition by User Situation Data Analysis (Context)”. Http://www.cs.helsinki.fi/group/context/. Last accessed Dec. 9, 2008, 7 pages.
[No Author Listed] “Context-Awareness in Wearable and Ubiquitous Computing.” Future Computing Environments, 1997. GVU Technical Report GIT-GVU-97-11.
[No Author Listed] “GyroPoint Technology,” http://www.gyration.com/html/gyropoint.html, pp. 1-3 (Accessed Oct. 2, 1998).
[No Author Listed] “Haptics,” http://www.ai.mit.edu/projects/handarm-haptics/haptics.html, pp. 1-2 (Accessed Oct. 2, 1998).
[No Author Listed] “Intelligent User Interface Prompt level,”IBM Technical Decision Bulletin, IBM Corp, New York, vol. 35, No. 1A, Jun. 1992, pp. 25-26.
[No Author Listed] “LabVIEW User Manual,” Jan. 1998 Edition, National Instruments. Http://claymore.engineer.gvsu.edu/eod/courses/egr450/media1/320999b.pef. Last accessed Dec. 7, 2008, 514 pages.
[No Author Listed] “Research Areas in Affective Computing” http://www.media.mit.edu/affect/ (Accessed Oct. 2, 1998).
[No Author Listed] “Research on Affective Pattern Recognition and Modeling,” http://www.mdeia.mit.edu/affect/AC—research/recognizing.html, pp. 1-4 (Accessed Oct. 2, 1998).
[No Author Listed] “Research on Sensing Human Affect,” http://www.mdeia.mit.edu/affect/AC—research/sensing.html, pp. 1-5 (Accessed Oct. 2, 1998).
[No Author Listed] “Smart Rooms,” http://vismod.www.media.mit.edu/vismod/demos.smartdesk/, pp. 1-4 (Accessed Oct. 2, 1998).
[No Author Listed] “SmartDesk Homepage,” http://vismod.www.media.mit.edu/vismod/demos/smartdesk/, pp. 1-4 (Accessed Oct. 2, 1998).
[No Author Listed] “The MIT Wearable Computing Web Page,” http://wearables.www.mdeia.mit.edu/projects.wearables/, pp. 1-3 (Accessed Oct. 2, 1998).
[No Author Listed] “Wearable Computer Systems for Affective Computer,” http://www.media.mit.edu/affect/AC—research/wearables.html, pp. 1-5 (Accessed Oct. 2, 1998).
[No Author Listed] “Workshop on Wearable Computing Systems,” Aug. 19-21, 1996.
Amon et al. “Integration of Design Education, Research and Practice at Carnegie Mellon University: A Multi-Disciplinary Course in Wearable Computer Design,” Proceedings of The Frontiers in Education Conference, Nov. 1-4, 1995, pp. 4a1.14-4a1.22, vol. 2.
Aoki et al., “Realtime Personal Positioning System for a Wearable Computer,” 3rd Int'l Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Bacon et al. “Using Events to Build Distributed Applications,” University of Cambridge, 1996. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.11.34.4545. Last accessed Dec. 9, 2008, 8 pages.
Bates et al., Middleware Support for Mobile Multimedia Applications, ICL System Journal, Nov. 1997, 20 pages.
Bauer et al., “A Collaborative Wearable System with Remote Sensing,” University of Oregon, Feb. 1996.
Bier et al. “Toolglass and Magic Lenses: The See-Through Interface,” Proceedings of SIGGRAPH'93, Computer Graphics and Annual Conference Series, ACM, pp. 73-80, Anaheim, California, 1993. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.36.9741. Last accessed Dec. 9, 2008, 8 pages.
Billinghurst et al., An Evaluation of Wearable Information Spaces, Proceedings of the Virtual Reality Annual International Symposium, 1998, 8 pages.
Billinghurst et al., Wearable Devices: New Ways to Manage Information, IEEE Computer Society, Jan. 1999, pp. 57-64.
Billinghurst, Research Directions in Wearable Computing, University of Washington, May 1998, 48 pages.
Bishop, “Hard Ware,” Jul. 28, 2000, Puget Sound Business Journal, print edition, pp. 1-4.
Biskup, et al, “Towards Secure Mediation”, Oct. 1989.
Bowskill, et al., “Wearable Location Mediated Telecommunications; A First Step Towards Contextual Communication,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Brown et al., “Using Explicit Requirements and Metrics for Interface Agent User Model Correction,” Autonomous Agents '98.
Brown et al. “Utility Theory-Based User Models for Intelligent Interface Agents,” Proceedings of the Twelfth Canadian Conference on Artificial Intelligence (AI'98), Jun. 1998.
Budzik et al., Watson: Anticipating and Contextualizing Information Needs, May 1, 1999, Proceedings of the 62nd Annual Meeting of the American Society for Information Science, pp. 1-14.
Chen et al., A Survey of Context-Aware Mobile Computing Research, Dartmouth Computer Science Technical Report, 2000, 16 pages.
Cochran, “The Development of Wearable Clothing,” Dr. Dobb's, online edition, pp. 1-2.
Crabtree et al. “Wearable Computing and the Remembrance Agent,” BT Technology Journal, vol. 16, No. 3, Jul. 1998, pp. 118-124. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.31.8514. Last accessed Dec. 9, 2008, 7 pages.
Cugola et al., Exploiting an Event-Based Infrastructure to Develop Complex Distributed Systems, 20th International Conference on Software Engineering (ICSE'98) Apr. 1998, p. 261-270, 10 pages.
D'Orazio et al. Mobile Robot Position Determination Using Visual Landmarks. IEEE Transactions on Industrial Electronics, vol. 41, issue 6, Dec. 1994, pp. 654-662. Last accessed Dec. 9, 2008, 9 pages.
Dechamboux et al., Using a Distributed Shared Memory for Implementing Efficient Information Mediators, Proceedings of the International Conference and Exhibition on High-Performance Computing and Networking, Apr. 1996, 5 pages.
Dey et al., CyberDesk: A Framework for Providing Self-Integrating Context-Aware Services, Knowledge-Based Systems, 11:3-13, 1998, 10 pages.
Dey et al., “The Conference Assistant: Combining Context-Awareness with Wearable Computing,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Doorenbos et al. “A Scalable Comparison-Shopping Agent for the World-Wide-Web,” Proceedings of the First International Conference on Autonomous Agents, Marina Del Rey, California, Feb. 5-8, 1997 pp. 39-48. http://www.cs.washington.edu/homes/etzioni/papers/agents97.pdf. Last accessed Dec. 9, 2008, 10 pages.
European Office Action dated Feb. 13, 2009 for EP Application No. 01964695.9, 4 pages.
Fickas et al., “Software Organization for Dynamic and Adaptable Wearable Systems,” University of Oregon, 8 pages, 1997.
Finger et al., “Rapid Design and Manufacture of Wearable Computer,” Communications of the ACM 39(2): 63-68, Feb. 1996.
Gabbard et al., A Taxonomy of Usability Characteristics in Virtual Environments, Nov. 1997, can be retrieved from http://csgrad.cs.vt.edu/˜jgabbard/ve/taxonomy/, 191 pages.
Gavrilova, “An Approach to Mapping of User Model to Corresponding Interface Parameters”, 1997, pp. 24-29, can be retrieved from http://citiseer.nj.nec.com/context/109679/352175>.
Goh et al., “Content Interchange: New Features and Formalisms for the Intelligent Integration of Information.” ACM transactions on Information Systems, 1997. http://dspace.mit.edu/bitstream/handle/1721.1/2642/SWP-3941-36987967.pdf?sequence=1. Last accessed Dec. 10, 2008. 25 pages.
Goharian et al., Enterprise Text Processing: A Sparse Matrix Approach, 2001, IEEE, pp. 71-75.
Golding et al., “Indoor Navigation Using a Diverse Set of Cheap, Wearable Sensors,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Goodridge, “The Environment Understanding Interface: Detecting and Tracking Human Activity Through Multimedia Sensors.” 1995.
Han, et al., “DBMiner: A System for Mining Knowledge in Large Relational Database, ”Proceedings 1996 International Conference on Data Mining and Knowledge Discovery, Portland, OR, Aug. 1996. http://www.cs.ualberta.ca/'zaiane/postscript/kdd96.pdf. Last accessed Dec. 9, 2008, 6 pages.
Harter et al. “A Distributed Location System for the Active Office”, IEEE Network, 1994 pp. 62-70.
Horvitz et al., Attention-Sensitive Alerting in Computing Systems, Microsoft Research, Aug. 1999.
Horvitz et al., In Pursuit of Effective Handsfree Decision Support: Coupling Bayesian Interference, Speech Understanding, and Understanding, and User Models, 1995, 8 pages.
Hull et al., “Towards Situated Computing,” Hewlett-Packard Laboratories, HPL-97-66 (1997).
International Search Report dated Sep. 29, 2003 for PCT Application Serial No. 00/20685, 3 pages.
International Search Report for PCT Application No. PCT/US01/10394, Mailed Jun. 13, 2002, 5 pages.
International Search Report PCT/US01/32543, Oct. 27, 2003, 3 pages.
International Search Report, Application No. PCT/US01/10599, Nov. 28, 2002.
International Search Report, PCT/US01/10538, Aug. 14, 2002, 2 pages.
Jakobovits, “Integrating Autonomous Heterogeneous Information Sources.” University of Washington, Technical Report UV-CSE-971205, Jul. 15, 1997, 29 pages.
Joachims, Text categorization with support vector machines: learning with many relevant features, Machine Learning, European Conference on Machine Learning, Apr. 21, 1998 pp. 137-142.
Kirsch, “The Sentic Mouse: A Tool for Measuring Emotional Valence,” http://www.media.mit.edu/affect/AC—research/projects/sentic—mouse.html, pp. 1-2 (Accessed Oct. 2, 1998).
Kortuem et al., “Context-Aware, Adaptive Wearable Computers as Remote Interfaces to ‘Intelligent’ Environments,” University of Oregon, Oct. 1998.
Kortuem, “When Cyborgs Meet: Building Communities of Cooperating Wearable Agents,”3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Lashkari et al., “Collaborative Interface Agents,” Proceedings of AAAI '94 Conference, Seattle, WA, Aug. 1994.
Lehikoinen et al. “MEX: A Distributed Software Architecture for Wearable Computers,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Leonhardi et al., “Virtual Information Towers—A Metaphor for Intuitive, Location-Aware Information Access in a Mobile Environment,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Leonhardt et al., Multi-Sensor Location Tracking, Department of Computing, London UK Oct. 1998.
Losee, Jr., Minimizing Information Overload: the ranking of electronic messages, Journal of Information Science 15, Elsevier Science Publishers B.V. 1989, pp. 179-189.
Lunt et al., “Knowledge-Based Intrusion Detection,” Proceedings of the Annual Artificial Intelligence Systems in Government Conference, IEEE Comp. Soc. Press, vol. Conf. 4, 1989, pp. 102-107.
Maes, “Agents that Reduce Work and Information Overload,” Communications of the ACM 37(7), Jul. 1994.
Mann, “Smart Clothing: Wearable Multimedia Computing and Personal Imaging to Restore the Technological Balance between People and Their Environments,” ACM Multimedia, pp. 163-174, Nov. 1996.
Metz, “MIT: Wearable PC's, Electronic Ink, and Smart Rooms,” PC Magazine, pp. 192-193, Jun. 1998.
Mott et al., A Formalism for Context Mediation based on Feature Logic, Feb. 1998. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.4473. Last accessed Dec. 10, 2008, 11 pages.
Ni, Attribute Name Evaluation and its Implementation, School of Computing and mathematics, Deakin University, Geelong, Victoria, May 16, 1994. http://www.deakin.edu.au/scitech/sit/dsapp/archive/techreport/TR-C94-10.pdf. Last accessed Dec. 9, 2008, 32 pages.
OA Dated Aug. 1, 2008 for U.S. Appl. No. 11/179,822.
OA Dated Nov. 28, 2008 for U.S. Appl. No. 11/761,210, 11pages.
OA Dated Dec. 3, 2008 for U.S. Appl. No. 09/981,320, 40 pages.
OA Dated Jul. 29, 2008 for U.S. Appl. No. 10/984,511, 28 pages.
OA Dated Sep. 17, 2008 for U.S. Appl. No. 09/894,642, 28 pages.
OA Dated Aug. 14, 2008 for U.S. Appl. No. 10/981,941, 14 pages.
OA dated Dec. 4, 2008 for U.S. Appl. No. 11/567,902.
OA dated Jan. 2, 2009 for U.S. Appl. No. 11/559,854, 23 pages.
OA Dated Oct. 30, 2008 for U.S. Appl. No. 11/490,540, 37 pages.
OA Dated Sep. 15, 2008 for U.S. Appl. No. 11/033,974, 17 pages.
Oakes, “The Truman Show Realized?,” http://www.wired.com/news/news/technology/story/15745.html, pp. 1-4 (Accessed Oct. 21, 1998).
Ockerbloom, Mediating Among Diverse Data Formats: Thesis Summary, PhD Thesis, Technical Report CMU-CS-98-102, Department of Computer Sciences, Carnegie Mellon University, Pittsburgh, PA, Jan. 14, 1998, 15 pages.
Ockerman et al. Wearable Computer for Performance Support: Initial Feasibility Study:, International Symposium in Wearable Computers, Oct. 1997, pp. 10-17.
Papakonstantinou et al., “MedMaker: A Mediation System Based on Declarative Specification.” 1995 http://citeseerx.ist.psu.edu/viewsoc/summary?di=10.1.1.35,735. Last accessed Nov. 25, 2008, 10 pages.
Pascoe, Adding Generic Contextual Capabilities to Wearable Computers, Proceedings of the 2nd International Symposium on Wearable Computers (ISWC '98), Pittsburgh, PA, Oct. 19-20, 1998, 8 pages.
Picard et al., “Affective Wearables,” Personal Technologies 1:231-240, MIT Media Laboratory, 1997.
Rekimoto et al., “The World Through the Computer: Computer Augmented Interaction with Real World Environments,” ACM, pp. 29-36, Nov. 1995.
Rhodes, “The Wearable Remembrance Agent: A System for Augmented Memory,” Proceedings of the First International Symposium on Wearable Computers (ISW '97), Cambridge, MA, Oct. 13-14, 1997.
Rhodes, “WIMP Interface Considered Fatal,” http:/rhodes.www.media.mit.edu/people/rhodes/Papers/no-wimp.html, pp. 1-3 (Accessed Oct. 2, 1998).
Rhodes, Remembrance Agent: A continuously running automated information retrieval system, The Proceedings of the First International Conference on the Practical Application of Intelligent Agents and Multi Agent Technology, 1996, pp. 487-495.
Rhodes, The Wearable Remembrance Agent: A System for Augmented Memory. Personal Technologies Journal Special Issue on Wearable Computing, 1997, 12 pages.
Rogers et al., Outbreak Agent: Intelligent Wearable Technology for Hazardous Environments. IEEE International Conference, Orlando, Florida, Oct. 12-15, 1997, pp. 3198-3203. http://citeseerx.ist.psu.edue/viewdoc/summary?doi+10.1.1.468827. Last accessed Nov. 25, 2008, 6 pages.
Rosis et al. “Adaptive Interaction with Knowledge-Based System,” ACM 1994.
Salber et al., The Design and Use of a Generic Context Server. Technical Report GIT-GVU-98-32. GVU Center, College of Computing, Georgia Institute of Technology. 1998. Available at ftp://ftp.cc.gatech.edu/pub/gvu/tr/1998/98-32.pdf. Last accessed Mar. 12, 2010.
Sato et al., “Autonomous Behavior Control of Virtual Actors Based on the AIR Model,” Proceedings Computer Animation, Jun. 5, 1997.
Sawhney, Contextual awareness, messaging and communication in nomadic audio environments, Massachusetts Institute of Technology, Jun. 1998 pp. 80-105, 25 pages.
Schilit et al, Disseminating Active Map Information to Mobile Hosts, IEEE Network, 1994, pp. 22-32, vol. 8—No. 5.
Schilit et al., Context-Aware Computing Applications, In Proceedings of the Workshop on Mobile Computing Systems and Applications, Dec. 1994, pp. 85-90.
Schilit et al., Customizing Mobile Applications, Proceedings USENIX Symposium on Mobile and Location Independent Computing, Aug. 1993, 9 pages.
Schilit et al. The ParcTab Mobile Computer System, IEEE WWOS-IV, 1993, 4 pages.
Schilit, A System Architecture for Context-Aware Mobile Computer, Columbia University, 1995, 153 pages.
Schmidt et al., “There's More to Context Than Location: Environment Sensing Technologies for Adaptive Mobile User Interfaces.” Nov. 1998.
Schneider et al., “Modeling Wearable Negotiation in an Opportunistic Task Oriented Domain,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Smailagic et al., “Matching Interface Design with User Task: Modalities of Interaction with CMU Wearable Computers,” IEEE Personal Communications, pp. 14-25, Feb. 1996.
Smailagic et al., “MoCCA: A Mobile Communications and Computer Architecture,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Spreitzer et al., “Providing Location Information in a Ubiquitous Computing Environment,” Xerox Palo Alto Research Center, ACM, 1993, pp. 270-283. http://www.computing/staff/kc/Lecturing/MSc/wk10/p270-spreitzer.pdf. Last access Dec. 9, 2008, 14 pages.
Spreitzer et al., Architectural Considerations for Scalable, Secure, Mobile Computing with Location Information, In The 14th International Conference on Distributed Computing Systems, Jun. 1994, pp. 29-38.
Spreitzer et al., Scalable, Secure, Mobile Computing with Location Information Communications of the ACM, Jul. 1993, 1 page, vol. 36—No. 7.
Starner et al., “Visual Contextual Awareness in Wearable Computing,” Proceedings 2nd International Symposium on Wearable Computers (ISWC '98), Oct. 1998, 8 pages.
Starner, Wearable Computing and Contextual Awareness, Massachusetts Institute of Technology, Jun. 1999, 248 pages.
Starovic, An Event Based Object Model for Distributed Programming, Technical Report TCD-CS-95-28, Dept. of Computer Science, Trinity College Dublin, Ireland, 1995, retrieved from http://citeseer.ist.psu.edu/starovic95event.html, 15 pages.
Tan et al., “Tactual Displays for Wearable Computing,” IEEE, Massachusetts Institute of Technology Media Laboratory, pp. 84-88, 1997.
Theimer et al., Operating System Issue for PDAs, In Fourth Workshop on Workstation Operating Systems, 1993, 7 pages.
Wachowicz et al., “Combining Location and Data Management in an Environment for Total Mobility.” University of Cambridge, England 1996.
Want, Active Badges and Personal Interactive Computing Objects, IEEE Transactions on Consumer Electronics, 1992, 11 pages, vol. 38—No. 1.
Want et al., The Active Badge Location System, ACM Transactions on Information Systems, Jan. 1992, pp. 91-102, vol. 10—No. 1.
Wardell, “Stardock.net Releases WindowBlinds.” Stardock.net, Inc. Oct. 4, 1999. http://stardock.net/media/pr—wb10.html. Last accessed Dec. 9, 2008, 2 pages.
Weiser, Some Computer Science Issues in Ubiquitous Computing, Communications of the ACM, Jul. 1993, pp. 75-84, vol. 36—No. 7.
Weiser, The Computer for the 21st Century, Scientific American, Sep. 1991, 8 pages.
Yang et al., “Smart Sight: A Tourist Assistant System,” 3rd International Symposium on Wearable Computers, San Francisco, CA, Oct. 18-19, 1999.
Zenel et al. “A General Purpose Proxy Filtering Mechanism Applied to the Mobile Environment,” Proceedings of the 3rd Annual ACM/IEEE International conference on Mobile computing and networking, MOBICOM'97. Budapest, Hungary, pp. 248-259. http://portal.acm.org/citation.cfm?id=262153. Last accessed Dec. 9, 2008, 12 pages.
European Search Report for EP 02017656.6 mailed Mar. 18, 2009.
Pending, unpublished U.S. Appl. No. 13/194,184, filed Jul. 29, 2011.
Related Publications (1)
Number Date Country
20100262573 A1 Oct 2010 US
Continuations (2)
Number Date Country
Parent 10984511 Nov 2004 US
Child 12824508 US
Parent 09541326 Apr 2000 US
Child 10984511 US
Continuation in Parts (2)
Number Date Country
Parent 09464659 Dec 1999 US
Child 09541326 US
Parent 09216193 Dec 1998 US
Child 09464659 US