Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same

TECHNICAL FIELD

This invention relates to generally to the area of context-aware computing or ubiquitous computing.

BACKGROUND

The World Wide Web (WWW) was created to make content available from any source in any location around the world. Users of the Web are able to generally access a seemingly infinite number of resources via the Web. The Web has been highly successful in this regard. Yet, with the evolution of the Web, certain needs remain largely unmet. Specifically, people continue to have a need to access information that has a contextual aspect to it. That is, often times, individuals will find themselves in a computing environment that carries with it a certain context. Yet, the context of the environment cannot be easily incorporated into the present computing environment. As an example, consider the context of location. People generally have a need to access information, data, resources and the like, that have geographic dimensions to them. For example, individuals may desire to take advantage of services or products that are close in proximity to where they currently are located. In this regard, it is desirable to understand the individual's contextual location so that services, goods and the like can be made available to the individual. As “e-Commerce” continues to grow in importance, the necessity of bringing people, places, services and goods together in an efficient manner will become critically important.

To date, many attempts have been made to bring people, places, services and goods together. These various attempts have generally approached the problem from different directions in an often times incompatible manner. As an example, consider the context of location. Some services have attempted to bring people and services together by defining large databases that maintain information about the services. For example, a list of restaurants may be maintained in a web accessible database where each restaurant is associated with a zip code in which the restaurant is located. When a user desires to locate a particular restaurant, they might simply enter the zip code where they are located to see a list of corresponding restaurants in that zip code. From the list of restaurants, they might be able to select one or two restaurants of interest. This approach is undesirable for a number of reasons. First, the operation of the system is dependent upon a central server that is responsible for receiving user queries and executing the queries to return the information to the user. In the event the server fails, so too does the service. In addition, this particular service might be suited to finding restaurants, but possibly not other businesses. In addition, the granularity with which the results are returned to the user may foist some of the search burden on the user (i.e. the user gets a list of restaurants in a nearby zip code, but has to further explore the list to select which ones are of interest). Further, the list of restaurants may include some restaurants that are blocked by some type of a physical barrier (i.e. a river, mountain, etc.) that makes the distance, as the crow flies, unroutable.

Providers of services and products want to be connected to nearby end-users. End-users want to consume these services and goods at the closest and most convenient location. Acquiring the services of a dentist or a plumber that lives somewhere “out on the net” is not appropriate if you need them to fill a cavity or unclog a sink. Looking for the nearest hotdog while in a stadium requires you to stay in the stadium.

There is an unsolved need to be able to create context-aware computing in which computing devices can participate in their particular context. In specific circumstances, there are needs to provide relational position awareness among physical locations in both public and private views of the world. To date, however, there is no one standardized view of the world that would unlock the potential of context-aware computing. Context-aware computing is much more than just position awareness—although this is a very big field in and of itself.

This invention arose out of concerns associated with developing a standardized, context-aware infrastructure and related systems to unlock the potential of context-aware computing.

SUMMARY

Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same are described. In various embodiments, a context or location service module, implemented in software, determines a vehicle context or a vehicle location based upon information that it receives from various context providers or location providers respectively. Software executing on a vehicle's computer can then cause one or more applications that are associated with a vehicle computer to be modified in a manner that changes their behavior. The behavior modification is based on the current context or location of the vehicle and thus provides a context-specific or location-specific user experience. The context or location can be ascertained through the use of one or more hierarchical tree structures that comprises individual nodes. Each node is associated with a context or location. The nodes are traversable by the vehicle's software to ascertain a more complete context or location.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a diagram of an exemplary computing device that can be used in accordance with the described embodiments.

<figref idref="DRAWINGS">FIG. 2</figref> is a conceptual diagram of an exemplary Master World and an exemplary Secondary World in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 3</figref> is an exemplary specific view of a Master World and a Secondary World and their relation to one another.

<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 6</figref> is a high level diagram of an exemplary computing device architecture.

<figref idref="DRAWINGS">FIG. 7</figref> is a somewhat more specific view of an exemplary computing device architecture.

<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 10</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment.

<figref idref="DRAWINGS">FIG. 11</figref> is a side elevational view of an exemplary location beacon in accordance with one embodiment.

<figref idref="DRAWINGS">FIG. 12</figref> is a diagram of a vehicle computer in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 13</figref> is a more detailed view of portions of the <figref idref="DRAWINGS">FIG. 12</figref> vehicle computer.

<figref idref="DRAWINGS">FIG. 14</figref> is a block diagram of an exemplary context-aware system in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 15</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 16</figref> is a block diagram of an exemplary location-aware system in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 18</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 19</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 20</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 21</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment.

<figref idref="DRAWINGS">FIG. 22</figref> is a diagram of an exemplary system in accordance with one described embodiment.

DETAILED DESCRIPTION

Overview

To provide a standardized solution, embodiments described just below provide a uniform definition of the world. The uniform definition is defined in terms of a hierarchical tree of nodes, where each node represents some aspect of the world. Each node is connected to at least one other node by a branch. An exemplary classification of nodes takes place on a physical level (e.g. physical locations such as political entities, infrastructure entities and public places), as well as a non-physical level (e.g. military APOs). This hierarchical nodal structure is referred to as the Master World, and is a standardized view worldwide. Each node of the Master World has various attributes associated with it that assist in context-aware computing. Exemplary attributes include a unique ID, name, geographic entity class, latitude/longitude, relative importance, contextual parents to name just a few. The Master World is useful because it can be used to determine the relative location of a place anywhere in the world and at any definable granularity.

Once an individual's location or a place an individual is interested in is determined, various services that reference the location can be offered to the individual based on their location. That is, value is provided by the Master World model in the ability to tie services to nodal locations in the Master World.

Building on this concept, two additional concepts add value—the concept of so-called Secondary Worlds and a “geozone.”

A Secondary World is a powerful computing mechanism whereby individual entities (such as businesses or organizations) can define their own particular worlds that need not necessarily conform to the Master World view of the world. That is, while the Master World is essentially a physical hierarchical representation of the world, the Secondary Worlds can be physical and/or logical representations of each individual entities' world view. One particularly useful aspect of the Secondary World is that it links, at at least one point, into the Master World. Thus, within any Secondary World, a user's location not only within the Secondary World, but the Master World as well can be determined. Various services can be attached to the nodes of the Secondary World. Based upon a user's calculated position, these various services that are associated with Secondary World nodes can be offered to the user. In addition, because the user's context is determined relative to the Master World, other services that may not be associated with a particular Secondary World can be offered.

A geozone is essentially a spatial indexing mechanism by which the Master World is subdivided into individual zones. In the described embodiment, the zones are subdivided through the use of a quadtree algorithm that is dependent on a density function (although many other spatial index approaches can also be used). Once a desired density level is achieved (density might be defined in terms of points of interest per zone), each node on the Master World is assigned a particular geozone. Geozones enable proximity calculations to be computed in a fast and straight forward manner.

A useful aspect of the Master and Secondary Worlds are that they are “reachable” from various computing devices such as stationary (i.e. desktop devices) or mobile computing devices (i.e. cell phones, laptops etc.). That is, the Master World (or at least a portion of it) and one or more Secondary Worlds can be either locally maintained on the computing device, or accessed, e.g. via the Web or some other mechanism, so that a user can derive their context. For example, the Secondary World can be downloaded onto the computing device so that a user can derive their context within then Secondary World. One a user's context is determined from the Master World and one or more Secondary Worlds, a various robust collection of context-aware solutions become available to the user. For example, specific Secondary World services can be offered or Master World services can be offered. Additionally, services from other Secondary Worlds might also be offered since the user's location may be known (or made known) to these other Secondary Worlds. In this way, the Master World can link two or more Secondary Worlds together.

Another aspect is that the described embodiments harness the computing power of each computing device in determining the device's location. Here, by virtue of having the Master World and one or more Secondary Worlds reachable by the device (and possibly locally maintained on the device), the device itself determines its own context.

One embodiment provides a client side device that is configured to utilize the context-aware structures that are discussed above, i.e. the Master and one or more Secondary Worlds. The Master World or a portion thereof can be locally available on the device or can be accessible at another location, e.g. via the Web. In this embodiment, the client device has a location service embodied thereon. The described location service is a software module that can determine the location of the device and can answer queries from various applications (either executing on the device or off the device). The location service determines the location of the device by using the Master World and one or more Secondary Worlds. The applications query the location service through one or more Application Program Interfaces (APIs) or Events to get location information that is used by the applications to render a service.

The location service makes use of one or more location providers that convey information to the device. This information can be information that is specific to the location provider, or can be information that can be mapped directly into a node of the Master World or Secondary Worlds. Exemplary location providers can include Global Positioning Service (GPS) providers, cell phone providers (cell providers), Bluetooth providers, a user interface provider and the like. The location providers provide information that gives some aspect of a device's current location. This information is used by the location service to ascertain the location of the device.

One particularly advantageous feature of the client device is a standard or common location provider interface. The location provider interface enables the various location providers to provide information to the location service so that the location service can use the information to determine its location. Essentially, the multiple location provider interface is a common interface that enables multiple different location providers to provide location information (or hints) about location to a location service that is on a device. The location providers can provide the location information constantly, at intervals, or when polled by the device. The location information can be provided with confidence and accuracy estimates to enable the location service to evaluate the relative quality of the information before it is used. The various providers also have the ability to self-monitor themselves which assists in the providers' ability to intelligently convey information to the location service. By having a common interface, the collection of location providers is dynamically extensible—that is location providers can be added or removed from the collection of location providers without any interference of the functionality performed by the location service or device. The location providers can be added or removed while the device is operating. This is particularly useful in accommodating location providers that are developed in the future. In this particular embodiment, two levels of abstraction are provided i.e. (1) the provider interface that receives information from the location providers and (2) the API/events layer that enables applications to get at the various information.

One focus of this embodiment is a device that can collect context information (e.g. location information) from a variety of different sources, determine the device's current context from that information, and provide the current context at some level to one or more applications that can use the device's context to render a service or enable the device to participate in its context environment.

In the described embodiment, the device receives location information or hints about its location. This information is collated and mapped by the location service into a node in the Master World and/or Secondary World. The hierarchical trees can then be traversed to determine the device's accurate location in both the Secondary World and the Master World. At this point, the device has determined its context. The information that is collected can be subject to arbitration to ensure that only highly trusted information is used to determine context. The location information can be cached to provide “current location information” which, for a definable period of time will be accurate to some degree. Thus, if for some reason other location providers are unavailable, the cache can be used to ascertain location.

Once a device's location is determined, the device can apply a security policy to the information. Once this is done, the device can begin to answer queries from various applications.

One aspect of the described embodiment is a “favorite locations” aspect in which the device can be automatically configured, when it determines its context, so that it can adjust to the different locations.

Further, various types of location providers can convey different types of information. For example, a so-called “thin provider” provides location information that is translated by the location service into the appropriate node information. A so-called “thick provider” includes logic that takes location information and provides it in a form that can map directly into the Master World or Secondary World.

In another embodiment location translation services are provided that are directed to determining, as accurately as possible, the context or location of the device. In this embodiment, information is received from the various location providers. This information includes location, accuracy and confidence (all of which are provided by the location provider), trust (which is assigned to a location provider by the device or a user) and a timestamp (which helps to age the location information). The location translation processing involves determining which of the location providers are valid and active. The location providers can be ranked in accordance with the confidence and trust levels. This defines an ordered list of location providers. Provision is made for a situation in which all of the location providers may go inactive. If so, a “current location” is used as a location provider whose confidence decreases over time.

In the event that information from two or more of the location providers conflicts, then measures can be taken to use information for which there is a higher level of trust. The information that is provided by all of the location providers (assuming no conflict) can then be used to determine a tree structure and a node's entity ID (EID). The tree might be the Master World and the EID is a node on the Master World. The tree might also be a Secondary World and the EID (or location unique indentifier or “LUID”) is a node on the Secondary World. Once this information is collected, complete location information can be determined by simply traversing the tree(s). Once a device's location is determined, a cache can be updated with the current location (including a time stamp).

In another embodiment, privacy issues in the context-aware computing environment are addressed. In this embodiment, the location service has acquired location information that pertains to the location of a particular device. A privacy manager determines what level of information to provide to applications that might request the information. The privacy manager can reside on the computing device itself, or can be proxied by a trusted third party.

According to this embodiment, a scale of privacy levels are defined. Each level is defined to include more or less specific information about the location of a particular device. A user is able to assign a privacy level to entities that might request location information. Additionally, each node of the Master World and a Secondary World can have a privacy level associated with it. When a query from an application is received, the privacy manager first determines who the query is from and the privacy level associated with the application or entity. The privacy manager then evaluates one or more of the Master World and the Secondary World to find a node that has a corresponding privacy level. When a corresponding node is found, information at that particular granularity is provided to the requesting application or entity.

In another embodiment systems and methods of providing a location provider in the form of a location beacon are described. In this embodiment, a location beacon is provided that can be mounted in various areas (public/private areas) to beacon the location to any computing devices within transmission range. The information that is transmitted enables a device to determine its location or context. The location beacon can transmit information that is specific to the location service that uses the information. Transmitted information can include an EID/URL pair, and a LUID/URL pair. The EID gives the node identification of a node in the Master World; and, the associated URL gives a protocol to communicate with the Master World. The URL might, for instance, link to a server that can provide additional context information that uses the EID. The LUID indicates a node on a Secondary World that corresponds to a current location; and the URL gives a protocol to communicate with the Secondary World. For example, the URL can link with a server that is hosting the Secondary World. This server can then be queried to discover more information about the Secondary World (i.e. Secondary World tree structure, location of associated resources, etc.) With the EID and LUID (along with the URLs), a device can now traverse the Master World or Secondary World to determine its location. Various technologies can be used to implement the beacon (wireless, RF, IR). The beacon can be a “program once” device to deter tampering. Programmable beacons can, however, be provided. Security can also be provided in the form of a verifiable signature that is provided with the beacon information to assure the veracity of the transmitted information.

A useful context-aware computing aspect of the beacon is the concept of “location-enabled access”. That is, in addition to (or separately from) receiving location information, a beacon can transmit code download pointers that enable smart devices to access software code that allows the device to participate in its current context.

Exemplary Computing System

In the context of this document, the term “computing device” is used to refer generally to any type of computing device. Characteristics of exemplary computing devices are that they typically include one or more processors, computer-readable media (such as storage devices and memory), and software executing on the one or more processors that cause the processors to implement a programmed functionality. In particular embodiments, implementation takes place in the context of mobile computing devices (e.g. laptop computers and the like), and/or hand-held computing devices (e.g. palm PCs, wireless telephones and the like).

<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram that constitutes but one example of a computing device that is suitable for use in connection with the described embodiments. It is to be understood that portions of the illustrated computing device can be incorporated in one or more of the computing devices (e.g. palm PCs, wireless telephones, etc.) with which particular embodiments are envisioned for use.

Computer <b>130</b> includes one or more processors or processing units <b>132</b>, a system memory <b>134</b>, and a bus <b>136</b> that couples various system components including the system memory <b>134</b> to processors <b>132</b>. The bus <b>136</b> represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The system memory <b>134</b> includes read only memory (ROM) <b>138</b> and random access memory (RAM) <b>140</b>. A basic input/output system (BIOS) <b>142</b>, containing the basic routines that help to transfer information between elements within computer <b>130</b>, such as during start-up, is stored in ROM <b>138</b>.

Computer <b>130</b> further includes a hard disk drive <b>144</b> for reading from and writing to a hard disk (not shown), a magnetic disk drive <b>146</b> for reading from and writing to a removable magnetic disk <b>148</b>, and an optical disk drive <b>150</b> for reading from or writing to a removable optical disk <b>152</b> such as a CD ROM or other optical media. The hard disk drive <b>144</b>, magnetic disk drive <b>146</b>, and optical disk drive <b>150</b> are connected to the bus <b>136</b> by an SCSI interface <b>154</b> or some other appropriate interface. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for computer <b>130</b>. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk <b>148</b> and a removable optical disk <b>152</b>, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk <b>144</b>, magnetic disk <b>148</b>, optical disk <b>152</b>, ROM <b>138</b>, or RAM <b>140</b>, including an operating system <b>158</b>, one or more application programs <b>160</b>, other program modules <b>162</b>, and program data <b>164</b>. A user may enter commands and information into computer <b>130</b> through input devices such as a keyboard <b>166</b> and a pointing device <b>168</b>. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit <b>132</b> through an interface <b>170</b> that is coupled to the bus <b>136</b>. A monitor <b>172</b> or other type of display device is also connected to the bus <b>136</b> via an interface, such as a video adapter <b>174</b>. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers.

Computer <b>130</b> commonly operates in a networked environment using logical connections to one or more remote computers, such as a remote computer <b>176</b>. The remote computer <b>176</b> may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer <b>130</b>, although only a memory storage device <b>178</b> has been illustrated in FIG. <b>1</b>. The logical connections depicted in <figref idref="DRAWINGS">FIG. 1</figref> include a local area network (LAN) <b>180</b> and a wide area network (WAN) <b>182</b>. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN networking environment, computer <b>130</b> is connected to the local network <b>180</b> through a network interface or adapter <b>184</b>. When used in a WAN networking environment, computer <b>130</b> typically includes a modem <b>186</b> or other means for establishing communications over the wide area network <b>182</b>, such as the Internet. The modem <b>186</b>, which may be internal or external, is connected to the bus <b>136</b> via a serial port interface <b>156</b>. In a networked environment, program modules depicted relative to the personal computer <b>130</b>, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

Generally, the data processors of computer <b>130</b> are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. The invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the steps described below in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described below.

For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.

Defining the World

One of the problems to date with attempting to solve the context-aware computing problem is that every proposed solution has its own approach, data structures, processes and the like. There is little if any standardization between the various approaches. In the described embodiment, standardization is achieved at the foundational level by defining a universal view of the Earth. That is, a universally acceptable definition of the Earth is proposed and is useable in various computing scenarios to enable context-dependent computing. In this document, a specific example of context-dependent computing is given in the form of location dependent computing. It is to be understood that this constitutes but one example of a context in which the various embodiments discussed below can be employed. Other “contexts” can include, any information that can fit into a hierarchical structure including, without limitation, role/personnel in an organization, device categorizations, current activity, current environment, active devices and the like.

The Master World

A Master World is defined as a politically correct and publicly accepted hierarchical tree structure that catalogs physical location or geographic divisions of the Earth. The Master World is defined in such a way that many different classes of political, administrative and geographic entities across the entire Earth are included. Areas of political contention are accounted for by presenting a view of the world based on the language/locale of the computing device.

<figref idref="DRAWINGS">FIG. 2</figref> shows an exemplary hierarchical tree structure <b>200</b> that represents a portion of the Master World. The Master World contains multiple nodes <b>202</b>, with each node representing some type of geographic division (e.g. political or natural entity) of the Earth. In the illustrated example, the nodes of the Master World are arranged in the following groups: (1) political or natural entities (e.g. continents, countries, oceans, states, counties, cities and the like); (2) infrastructure entities (e.g. postal codes, area codes, time zones and the like); (3) public place entities (e.g. parks, malls, airports, stadiums, and the like); and (4) non-physical entities (military postal code regions, vacation regions, affiliate coverage areas of television networks that can be geographically discontinuous, and the like).

In the <figref idref="DRAWINGS">FIG. 2</figref> example, the top node of the tree structure represents the Earth. Each node underneath the top node represents a geographical division of the Earth. In this example, none of the nodes have an association with any businesses or services. That is, there is a distinction between node entities that are part of the Master World and non-geographic places where activities take place. Though the Master World includes nodes for public places (i.e. airports, malls, etc), it does not include individual listings of businesses or service providers. Each node is uniquely identified by an ID (EID or entity ID). In addition to the unique EIDs, a URL is associated with the tree structure and provides a context for the tree structure as will become apparent below.

As an example, consider the following: Seattle-Tacoma International Airport (SeaTac) will be included in the Master World, but references to individual airline business locations at SeaTac might be “leaves” on the tree that are tagged by the SeaTac Airport EID (see “Secondary World” section and the Table below). Similarly, the Seattle Center might be a node on the Master World, while the Seattle Arts Festival, Bumpershoot, the Seattle Sonics NBA Team, and the Seattle Center Starbucks Coffee Shop might be tagged with the Seattle Center EID. As another example, the Master World also contains nodes for all Interstate (motorway) exits. For example, the I-90, Exit 109, Washington is a node in the Master World. The Best Western Inn located at 1700 Canyon Road in Ellensburg, Wash. might be tagged with the EID of this Exit.

Thus, the Master World provides a uniform way of defining locations. The uniform location definitions can then be universally used to assign attributes to goods or services. Whenever a computing device determines its location to correspond to a particular uniform location definition, it can take advantage of the location-dependent goods or services that share the uniform location definition. The Master World is useful because it is a standardized view of the world. Its accurate standardized geographic dimension attribution can be easily accessed by both providers and consumers. Services and product providers (or third parties such as search engines, network and yellow-page database directories) can use the nodes of the Master World by assigning a standardized persistent geographic reference to all commerce locations or points of interest. These commerce locations or points of interest can be considered as “leaves” on the tree structure.

In the illustrated example, the nodes of the Master World have one or more attributes that facilitate its use. Exemplary attributes are described in the table immediately below:

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="63pt" align="left" /><colspec colname="2" colwidth="154pt" align="left" /><thead><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Attribute</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Entity ID (EID)</entry><entry>The EID is a unique ID for each node. No two</entry></row><row><entry /><entry>nodes have the same EID.</entry></row><row><entry>Name</entry><entry>The name is defined in terms of the neutral ground</entry></row><row><entry /><entry>truth (NGT) name. The NGT name supports various</entry></row><row><entry /><entry>language translations for entity names as appropriate</entry></row><row><entry /><entry>(e.g. Pacific Ocean, Pazifischer Ozean, Oceano</entry></row><row><entry /><entry>Pacifico, etc.)</entry></row><row><entry>Geographical Entity</entry><entry>The GEC is a geographical classification of each</entry></row><row><entry>Class (GEC)</entry><entry>node. An exemplary GEC is discussed below in the</entry></row><row><entry /><entry>“Geozone” section.</entry></row><row><entry>Latitude</entry><entry>The horizontal coordinate position on the globe (i.e.</entry></row><row><entry /><entry>the coordinate position of the node's centroid)</entry></row><row><entry>Longitude</entry><entry>The vertical coordinate position on the globe (i.e.</entry></row><row><entry /><entry>the coordinate position of the node's centroid)</entry></row><row><entry>Relative Importance</entry><entry>The geographic importance of an entity in reference</entry></row><row><entry /><entry>to other entities in the same region. Value from 1 to</entry></row><row><entry /><entry>256 (e.g. New York City = 3, Los Angeles = 4, and</entry></row><row><entry /><entry>Omaha = 5 even though Omaha is much smaller but</entry></row><row><entry /><entry>almost as important in relation to surrounding</entry></row><row><entry /><entry>populated places)</entry></row><row><entry>Contextual Parent(s)</entry><entry>The parents of the parent/child relationship for each</entry></row><row><entry /><entry>node. Multiple parents are supported (e.g. Redmond</entry></row><row><entry /><entry>is a child of King County, Area Code 425, the</entry></row><row><entry /><entry>Pacific Time Zone, and the MSNBC affiliate</entry></row><row><entry /><entry>KING TV).</entry></row><row><entry>Source</entry><entry>The source of origin for the record (e.g. Microsoft</entry></row><row><entry /><entry>or a specified data vendor)</entry></row><row><entry>Start Date</entry><entry>Date when the node information was first valid</entry></row><row><entry>End Date</entry><entry>Date when the node information was last valid</entry></row><row><entry /><entry>(retired zip codes, breakup of countries)</entry></row><row><entry>Modification Date</entry><entry>Records date changes that are made to the record</entry></row><row><entry /><entry>relating to retirement or updates to any fields</entry></row><row><entry>Status</entry><entry>Active, lashed (links duplicate nodes together),</entry></row><row><entry /><entry>pending or retired</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

The attributes listed above constitute exemplary attributes only. Other attributes that are different from and/or additional to those referenced above could be used. A few exemplary entity or node records that employ the above attributes are shown below:

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="119pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>Entity ID</entry><entry>24948</entry></row><row><entry /><entry>(EID)</entry></row><row><entry /><entry>Name</entry><entry>Pacific Ocean, Pazifischer</entry></row><row><entry /><entry /><entry>Ozean, Oceano Pacifico, etc.</entry></row><row><entry /><entry>Geographical</entry><entry>138/Ocean</entry></row><row><entry /><entry>Entity Class</entry></row><row><entry /><entry>(GEC)</entry></row><row><entry /><entry>Latitude</entry><entry>0 (+000° 00′ 00″)</entry></row><row><entry /><entry>Longitude</entry><entry>−170 (−170° 00′ 00″)</entry></row><row><entry /><entry>Relative</entry><entry>1</entry></row><row><entry /><entry>Importance</entry></row><row><entry /><entry>Contextual</entry><entry>World</entry></row><row><entry /><entry>Parent(s)</entry></row><row><entry /><entry>Source</entry><entry>MSFT GeoUnit</entry></row><row><entry /><entry>Start Date</entry><entry>0/0/00</entry></row><row><entry /><entry>End Date</entry><entry>0/0/00</entry></row><row><entry /><entry>Modification</entry><entry>01/18/00</entry></row><row><entry /><entry>Date</entry></row><row><entry /><entry>Status</entry><entry>Active</entry></row><row><entry /><entry>Entity ID</entry><entry>27490</entry></row><row><entry /><entry>(EID)</entry></row><row><entry /><entry>Name</entry><entry>Redmond</entry></row><row><entry /><entry>Geographical</entry><entry>78/non-capital town</entry></row><row><entry /><entry>Entity Class</entry></row><row><entry /><entry>(GEC)</entry></row><row><entry /><entry>Latitude</entry><entry>47.6768303 (+047° 40′ 36″)</entry></row><row><entry /><entry>Longitude</entry><entry>−122.1099625 (−122° 06′ 35″)</entry></row><row><entry /><entry>Relative</entry><entry>107</entry></row><row><entry /><entry>Importance</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="14pt" align="left" /><colspec colname="3" colwidth="105pt" align="left" /><tbody valign="top"><row><entry /><entry>Contextual</entry><entry>1.</entry><entry>King, second level</entry></row><row><entry /><entry>Parent(s)</entry><entry /><entry>[Washington, United</entry></row><row><entry /><entry /><entry /><entry>States]</entry></row><row><entry /><entry /><entry>2.</entry><entry>Puget Sound-Seattle,</entry></row><row><entry /><entry /><entry /><entry>travel region</entry></row><row><entry /><entry /><entry /><entry>[Washington, United</entry></row><row><entry /><entry /><entry /><entry>States]</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="119pt" align="left" /><tbody valign="top"><row><entry /><entry>Source</entry><entry>MSFT GeoUnit</entry></row><row><entry /><entry>Start Date</entry><entry>0/0/00</entry></row><row><entry /><entry>End Date</entry><entry>0/0/00</entry></row><row><entry /><entry>Modification</entry><entry>01/18/00</entry></row><row><entry /><entry>Date</entry></row><row><entry /><entry>Status</entry><entry>Active</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

The Master World also serves as a repository of common denominator links between itself and various “Secondary Worlds” and as a conduit that connects Secondary Worlds to other Secondary Worlds. Content, service and device providers can use the Master World to associate their publicly available offerings with a geographic location and the corresponding multiple branch hierarchical structure. This location will be associated with a single entity within the tree structure thereby allowing geographic and time/distance calculations and the necessary parent/child relationship navigation.

The Master World Index (Geozones)

By definition, the Master World provides a hierarchical structure of entities (nodes) that cover the entire globe. Upward navigation within the hierarchy is quite natural. Efficient navigation downward requires geographic proximity awareness. Additionally, there are possible scenarios that will require jumping from branch to branch in order to successfully return values in a query, or for more accurate calculations of distances to close “leaves” attached to nodes other than the original source node. The Master World makes use of an index scheme that can identify peer level nodes by virtue of the geographical proximity. This indexing scheme makes use of a quad tree algorithm to define so-called “geozones.”

A quadtree is essentially a spatial index that breaks coverage into homogeneous cells of regularly decreasing size. Each quadrant of the tree has up to four children. The quadtree segmentation process can continue until the entire map is partitioned based on many different end result criteria including the density of the number of items (e.g. points of interest) in each quad. The approach provides a form of spatial index that accelerates spatial selection and content identification.

To complete the spatial indexing scheme to provide each node with a defined geozone, a quadtree algorithm is applied to the nodes and can be based upon a desired density of, for example, points of interest that are to occur in any one zone. Once all of the zones have been defined, each zone is given a unique ID (e.g. top/left and bottom/right Latitude and Longitude pairs). Each of the nodes of the Master World is then assigned a zone in which it is located. Quadtree algorithms are known and will be appreciated by those of skill in the art.

The Master World Location

As can be appreciated, having a uniform standardized representation of the world in the form of a hierarchical traversable tree structure can greatly facilitate the manner to which context-dependent, and more specifically, location-dependent goods and services can be linked.

In the described embodiment, a computing device has access to at least a portion of the Master World. For example, the computing device can have the Master World saved in an internal storage device, it can comprise part of the computing device's operating system, or the device might access the Master World via a network medium such as the Internet. With the Master World tree structure being accessible to each computing device, each device has the power to determine its own context or node-referenced location. That is, the computing device can determine, through software it is executing, its particular location, i.e. node. Once the computing device determines an associated node, it can simply traverse the tree to ascertain its complete location.

For example, if a computing device determines that it is currently located at a node that corresponds to the City of Redmond, it can traverse the Master World tree structure to ascertain that it is in the State of Washington, Country of The United States, on the continent of North America. By ascertaining its precise location, the computing device (or its user) is now in a position to take advantage of location-dependent services that might be offered. This particular model is a tremendous improvement over current models that utilize a central server to ascertain location for a number of different devices. In that model, each device (or user) provides information about its location (e.g. perhaps the user enters the zip code or city that the device is currently in) and might enter a query to find, for example, a McDonald's restaurant in his zip code. The server then takes this information and might, for example, tell the user about the location of all of the McDonald's restaurants within that zip code or city. If the servers fails in this model, then none of the computing devices can take advantage of its services. In the present model, each computing device is self-sustaining. Each can determine its own location, and accordingly, each device can take advantage of location-dependent services. For example, if the computing device understands that it is located on a particular node of the Master World, then it can execute queries to find a McDonald's that has an EID that corresponds to the particular node in which the computing device is located. Particular robustness is provided through the use of the above-described geo-zones. The geo-zones enable proximate geographic divisions to be quickly searched in an efficient manner. For example, if an individual is looking for the nearest Kinko's to make copies and none are located in the geo-zone that corresponds to the node in which the computing device is located, then adjacent geo-zones can be quickly searched.

Secondary Worlds

In the described embodiment, the concept of a Secondary World is used to provide support for additional context. A secondary world might be defined by a third party organization or company and contains nodes that comprise physical and/or logical entities that are unique to that organization. The nodes of the Secondary World may or may not have much context outside of the particular organization that defined the Secondary World, since a secondary world could be made either public or private. The Secondary Worlds do not duplicate the Master World, but rather supplement it in a unique, organization specific manner. While the Master World is defined to be a widely accepted standard, each Secondary World can be a widely variant representation of an organization's proprietary view of the world. In the described embodiment, each Secondary World has at least one node that is linked with a node of the Master World. This gives the Secondary World a context or location in the Master World. Also note that in some context applications, several secondary worlds may be accessed, each providing additional context specific pieces of location data.

<figref idref="DRAWINGS">FIG. 2</figref> shows an exemplary Secondary World <b>204</b> that comprises a plurality of nodes <b>206</b>. Each of the nodes <b>206</b> constitutes a physical or logical entity. For example, the nodes can constitute a company, its divisions, regions campuses, buildings, floors in various buildings and rooms on various floors. At least one of the nodes is linked with a node of the Master World. The nodes of the Secondary World can have the same attributes as the nodes of the Master World.

As an example of a Secondary World, consider that Boeing might define a Secondary World that includes a list of entities that are important to its employees. The root entity would be “Boeing Corp.” and its children might be company divisions (St. Louis Military Division, Everett Plant, Corporate HQ, etc.). Further down the tree structure, individual nodes might be defined to represent individual buildings (Hanger <b>12</b> , offices within this building (Office 1001), building areas (Southwestern quadrant of hanger <b>12</b>), etc. Each entity or node has a unique identifier (Local Unique ID or “LUID”) and a URL that is associated with the tree on which the node occurs. The URL uniquely identifies the Secondary World tree structure so that a user within that world can determine how to interact with the world. This aspect is discussed below in more detail. Boeing can then use the LUIDs to associate equipment, services, departments or even personnel to a physical or logical location.

As a more concrete example, consider <figref idref="DRAWINGS">FIG. 3</figref> which shows an exemplary portion of the Master World <b>300</b> and a Secondary World <b>302</b>. Master World <b>300</b> includes the following nodes: World, United States, Washington, Redmond, and Zip=98052. The exemplary Secondary World <b>302</b> is a hierarchical tree structure that has been defined by Microsoft Corporation and includes the following nodes: Microsoft, Redmond Campus, 1 Microsoft Way, Building 26, 3^rdfloor, Conference Room 3173, Building 24, 2^ndfloor, Conference Room 1342. In this example, the Secondary World <b>302</b> “touch points” into the Master World from the Redmond node. In this example, a video projector is shown as being associated with the node “Conference room 1342”. Here, the video projector is not a node in the secondary world. Rather, the video projector is an item in some other resource discovery service (e.g. the active directory) and includes a location attribute that is a pointer to “Conference room 1342.” There may be times, however, when nodes can be created in the worlds to represent the location of key services—the node themselves, however, would not represent the services.

Like the Master World, the Secondary World is advantageously accessible to a user's computing device. It could, for example, be downloaded—completely or partially—and stored on a storage device and accessed when needed. It might be downloaded for a one time use only. The Secondary World enables the computing device to ascertain its context within the Secondary World. In this example, the computing device would, by using the Secondary World, compute its location within the Secondary World. The computing device can do this by traversing the tree structure from the node in which it is currently located to the root node. This would, for example, give the computing device (and hence the user) a complete Secondary World context. Once the Secondary World location is known, the user is in a position to take advantage of goods or services that are associated with the nodes of the Secondary World. That is, once the computing device determines its Secondary World context, it is ready to become an active participant in the Secondary World.

Tremendous value can be achieved by associating goods or services with the individual nodes of the Secondary World. For example, Conference Room 1342 has a video projector associated with it. That is, the location of the video projector is in Conference Room 1342. Assume that an individual in Conference Room 3173 has a presentation that requires the use of the video projector such as the one located in Conference Room 1342. Normally, an individual would have no way of ascertaining the location of the video projector other than perhaps physically calling over to the building to check whether there is a video projector available. In this example, because the user's computing device is able to ascertain its location within the Secondary World, it is able to locate the video projector in Conference Room 1342. It would do this by simply executing software that traverses the Secondary World tree structure to find the resource of interest.

Note also that because there is a link into the Master World, the computing device is able to derive it context (location) within both worlds. This enables the computing device, and hence the user, to take advantage of goods and services that are associated with the Secondary World, as well as participate in location-dependent services that are consumable based upon the user's location in the Master World.

<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment. The steps described just below are implemented by a computing device which, in the illustrated example, is a hand-held mobile computing device.

Step <b>400</b> accesses first and second hierarchical tree structures that are resident on a computer-readable media. In this example, the tree structures might be stored on the device or might be accessible via a network such as the Internet. An exemplary first tree structure is the Master World and an exemplary second tree structure is a Secondary World. Alternately, the tree structures could both be Secondary Worlds. Once the tree structures have been accessed by the device, step <b>402</b> traverses multiple nodes of the tree structures to derive the context of the computing device. In this example, the computing device receives information that informs it as to its location at a node of one of the trees. This information can come to the computing device in any suitable way, e.g. a user can enter the information through a User Interface (UI) or the location might be broadcast to the computing device by another computing device (e.g. through the use of Bluetooth technology or Universal Plug and Play (UpnP). Specific examples of how this information can be conveyed to the computing device are given below in more detail. Regardless of how this information is conveyed to the computing device, once the computing device has the information, it executes software that traverses one or both of the tree structures to derive its context which, in this example, is the device's location.

Defining Secondary Worlds

As was mentioned above, one particularly valuable aspect of the described embodiment is that individual organizations can define their own Secondary Worlds. This gives the organization a great deal of flexibility in providing goods and services and, more broadly, increasing the efficiency of their organization. In one embodiment, a software tool is provided that enables individual organizations to define and maintain their own Secondary Worlds.

In one embodiment, each secondary world can be uniquely identified as a name space (e.g. an XML namespace). This ensures that any overlap in names between the Secondary World and the Master World will not result in a collision. As an example, consider the following: the Master World might contain an entity identified as “Chicago” referring the city. A Secondary World that is established by the National Basketball Association (NBA) and a different Secondary World that is established by the Caterpillar Corporation might also have entities named “Chicago” that refer to completely different entities than the Master World's “Chicago.” For example, the NBA's “Chicago” might refer to an NBA market area while Caterpillar's “Chicago” might refer to a sales district. Having the namespace separation between the Master and Secondary Worlds can ensure that there not a collision between identically named entities because each name space is uniquely different from every other namespace.

<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram that describes steps in a method of building a context-aware data structure. These steps are implemented by a software tool that is executing on a computing device.

Step <b>500</b> receives input from a source that specifies information that pertains to physical and/or logical entities. In this example, a system administrator might physically enter information about the structure of the Secondary World that they desire to define. This information can include information about buildings, divisions, conference rooms and the like. Step <b>502</b> then processes the information to define a hierarchical tree structure that has a context. In this example, the context is location. It will be appreciated, however, that other contexts could be employed. Each of the nodes in the hierarchical tree structure represents a separate physical or logical entity. Step <b>504</b> then links at least one of the nodes of the hierarchical tree structure with another tree structure having a context. In this example, this other tree structure can comprise the Master World. Once the tree structures have been built and linked, they are ready for traversal in a manner that enables context to be derived from one or more of the nodes.

Location as a Service

In the above examples, the computing device is able to determine its own location. In the embodiment about to be described, the computing device determines its location by using location information that is provided to it from a number of different sources of information. The device is able to take the information that is provided to it and process the information to determine a particular node on one or more hierarchical trees. Once the device has done this, it can determine its complete location which is a useful thing to know particularly when there are location-dependent services that can be consumed by the device's user.

<figref idref="DRAWINGS">FIG. 6</figref> shows a high level diagram of an exemplary computing device <b>600</b> that comprises, among other components, a context service module <b>602</b> and one or more context providers <b>604</b>. The context service module <b>602</b> can be implemented in any suitable hardware, software, firmware or combination thereof. In this particular example, the context service module is implemented in software that is executed by one or more device processors. The context service module <b>602</b> receives context information from one or more context providers <b>604</b> and processes the information to determine a current device context. In this particular example, the device context is the device's location. Accordingly, the context providers are location providers that provide location information, in various forms, to the context service module <b>602</b> for processing. The location providers <b>604</b> receive information from various sources of context information (location information) <b>606</b>.

In the context of this document, a context provider comprises a software component that can either be implemented on the device or off the device. The context provider can also include any suitable hardware, firmware or combination thereof. The role of the context providers are to receive information from sources <b>606</b> and convey the information to the context service module <b>602</b> so that the context service module can use the information to determine a current device context.

In the case where the context of the device is the device's location, sources <b>606</b> provide various information to the location providers <b>604</b> that pertains to the device's current location. As an example, the sources of the information can include various information transmitters such as a GPS system, cell phone or cell ID, wireless transmitters that transmit location information, location beacons, 802.11 transmitters and various other sources of information. The sources of information can also include other computing devices that might, for example, provide location information through Bluetooth technology. In addition, a source of information <b>606</b> might include a person who, for example, physically enters location information into the device <b>600</b> so that the device can process the information to determine its location.

When the device <b>600</b> receives the location information from the sources <b>606</b>, it processes the information with the location providers <b>604</b> and provides the information to the location service module <b>602</b>. The location service module <b>602</b> processes the location information and determines a particular node on one or more of the hierarchical tree structures to which it has access which corresponds to its current location. The location service module <b>602</b> can then traverse the tree structures to determine a complete location for the device. Once the complete location is determined, the device <b>600</b> can begin to interact with one or more applications <b>608</b> that can query the device about its particular location so that one or more location-dependent services can be rendered to the device. In this example, the applications <b>608</b> are illustrated as being separate from the device. It is to be understood, however, that the applications could be executing on the device, e.g. a browser application.

As shown, the applications <b>608</b> can make calls to the device to ask the device where it is located. The device is configured to receive the calls and respond in an appropriate manner to the application. Once the application has the device's location information, it can then render location specific services to the device.

Consider the following example: You are a traveler and have a hand-held mobile computing device that contains a Master World tree and a Secondary World tree for SeaTac International Airport. You are scheduled to depart on a plane for China from Concourse C. SeaTac International Airport has designed its Secondary World to have the following nodes: “Arrivals”, “Departures”, “Concourses”, “Airlines”, “Gates assigned to Airlines”, and “Gate Location”. When you arrive at the airport, as you enter the airport your computing device receives location information from different sources and with that information your device determines that your location is in the Arrivals node. SeaTac International has bank of servers that are executing applications to assist you while you are in the airport. There are applications that can help you find services, locate facilities (e.g. coffee shops, restaurants), give directions (e.g. how to get to your departure gate), update you on the status of your flight, and even check you in automatically for your flight. Consider also that as you walk through the airport your location changes. Your computing device, however, can receive continuous location information updates so that it can continue to determine its location as you move through the airport. At one point, as you pass a Starbucks coffee shop, your hand held device notifies you that if you purchase a latte at Starbucks and present your hand held device, you will receive a 50 cent discount on your latte. In this example, the utility of the Secondary World is demonstrated. By knowing where its particular customers are in its facility, SeaTac International is able to provide a host of services that were not possible before.

Assume further that you are in the airport and your flight is canceled. You must find a place to stay for the night. Accordingly, you wish to determine the closest Double Tree hotel because you really like the warm chocolate chip cookies they give you when you check in. You execute a search engine on your computing device to find the nearest Double Tree hotel. The search engine application first determines your current location in the Master World as indicated by the EID of the Master World node that corresponds to your location. Executing a search, the search engine application looks for a Double Tree hotel that has an attribute that includes an EID that matches your EID. If it finds one, it simply indicates for you the result. If it does not find one with the corresponding EID, it can use an adjacent geozone to search for a Double Tree hotel. It may also provide driving directions to the hotel. The search engine application was able to do this because it was able to ascertain your location in the Master World. It did this quickly and automatically with little or no effort from you.

Consider further that as you are driving from the airport to the hotel you decide that you want to find the nearest Kinko's so that you can print 100 copies of a presentation that you are to give in the morning. Consider that your hand-held computing device is a cellular phone and that Sprint is the carrier. Sprint has defined its own Secondary World that might, for example, be designated in terms of cell nets. By virtue of having Sprint's Secondary World on your computing device, you are able to ascertain your location in Sprint's Secondary World and, accordingly, your location in the Master World. Consider that Kinko's also has a Secondary World that links with the Master World. By executing a search application on your device, you are able to ascertain the location of the nearest Kinko's as well as driving directions thereto. All of this is possible because your device has access to the Master World and one or more Secondary Worlds. In this example, the Master World provides a mechanism to daisy chain two or more Secondary Worlds together. This is possible because the Secondary Worlds have at least one reference or link into the Master World.

Exemplary Device Architecture

<figref idref="DRAWINGS">FIG. 7</figref> shows computing device <b>600</b> in somewhat more detail. In this particular embodiment, device <b>600</b> comprises an architecture that includes the following components: a location service module <b>602</b>, a location provider interface <b>700</b>, an application program interface (API)/Events module <b>702</b>, a privacy manager <b>704</b> a location conversion module <b>706</b>, one or more applications <b>608</b> and one or more location providers <b>606</b>. Also included in the architecture is an active directory <b>708</b>, Web service <b>710</b>, location database <b>712</b>, and personal places <b>714</b>. The architecture can be implemented in any suitable hardware, software, firmware or combination thereof. The architecture mentioned above is advantageous in that it enables each computing device to determine its own context or location.

Common Location Provider Interface

One particularly advantageous aspect of the described embodiment is that it employs a common interface <b>700</b> that provides a standard interface through which the location providers <b>606</b> communicate. By having a common interface, the location providers are extensible (to support future providers) in that they can be dynamically added or removed from the collection of location providers. All that is required of a particular location provider <b>606</b> is that it be written to support the common interface.

In this example, there are several location providers <b>606</b>. These location providers provide location information in different forms. For example, a GPS location provider might provide location information that is GPS specific. Similarly, an IP/Subnet location provider might provide information that is specific to an Internet Protocol. A mobile phone location provider might provide location information in the form of a cell ID. In addition, a location User Interface (UI) might provide location information in the form of a user entry that specifies a city, street or building. All of the location information that is provided by the various location providers is processed by the location service module <b>602</b> so that a current device location can be determined. To determine the current device location, the location service module <b>602</b> may have to consult with an active directory <b>708</b>, a Web service <b>710</b>, or a location database <b>712</b>. In the illustrated example, the active directory <b>708</b> might, for example, maintain a secondary world and other networking metadata such as subnet and “site” information that can help determine location based on networking connectivity. Web service <b>710</b> can hold the master or secondary worlds, the attributes of which can be used to find location. For example, if a cell phone knows its cell tower ID, then the location provider can query the secondary world to ascertain the nodes that match that cell tower ID. Location database <b>712</b> is basically a version of the web service that is hosted or cached locally.

Location Providers

As indicate above, the architecture contemplates multiple different location providers that can provide location information to the location service module <b>602</b>. This information can come in many different forms and quality levels. The information is then processed by the location service module <b>602</b> to determine a current device location. To do this, the service module <b>602</b> ascertains from the location information a particular node ID (EID and/or LUID) and a URL that is associated with the tree structure with which the node is associated. Once the location service module ascertains a node ID, it can then query the tree structure (or more accurately a server that manages the tree structure) using the URL to ascertain more information about the tree structure. For example, if the location service module <b>602</b> ascertains a LUID from a particular Secondary World, it might then query an active directory <b>708</b> (or an Intranet server—which is another location database) to discover the parents and the children of the node. This would then enable the location service module to build the Secondary World.

The location providers <b>606</b> can provide the location information to the location service module <b>602</b> in many different ways. For example, some location providers <b>606</b> may continuously provide information (e.g. the GPS provider may continuously provide GPS coordinates). Alternately, the location providers can periodically provide location information such as at specific times or on the occurrence of definable events. For example, a user may define specific times when the location information should be updated. Alternately, the location information might be updated only when a device's location changes (i.e. a location change event). Additionally, the location providers might provide location information when polled by the location service module <b>602</b>. For example, the location service module <b>602</b> can call the location provider interface <b>700</b> and request location information from one or more of the location providers.

One specific location provider <b>606</b> is shown as a cache. The cache provider essentially maintains a current device context or location. That is, once the location service module <b>602</b> has ascertained its current location, it writes this location to a cache. This enables the device <b>600</b> to ascertain its location with a degree of confidence in the event all of the other location providers are not able to provide location information (e.g. the GPS provider may not receive GPS information because the GPS transmitter that supplies it with the information is unable to contact a requisite number of satellites).

Confidence and Accuracy Parameters

One important and useful feature of the described embodiment is that one or more of the location providers are configured to assign confidence parameters and/or accuracy parameters to the information that they provide to the location service module <b>602</b>. Confidence parameters provide a measure of a provider's confidence in the information that it provides to the location service module <b>602</b>. For example, assume that a GPS transmitter must receive information from five or more satellites in order to provide highly confident information. Assume that only three satellites are available at the time. The GPS transmitter would then transmit its information based only on the three satellites. The GPS provider would then know that the information it receives from the GPS transmitter was based only on three satellites rather than the desired five or more. In this case, the GPS provider can set a confidence parameter on the location information that indicates that it has a lower confidence level than if the information were based on the desired five or more satellites. In this case, the location service module <b>602</b> can take the confidence parameters for all of the location providers into account when determining the location of the device. This is discussed in more detail below.

With respect to the accuracy parameters, consider that the location information that is received from the location providers is accurate to varying degrees. Some information may be accurate to within one mile, while other information may be accurate to within 100 feet. The location providers are desirably configured to assign accuracy parameters to the location information that they provide to the location service module <b>602</b>. The accuracy parameters give the location service module an indication of the accuracy of the information.

When the confidence and accuracy parameters are used by the location service module <b>602</b>, the module can make decisions on how to use the location information it receives from each provider. For example, the location service module <b>602</b> might disregard completely any information that has a low confidence parameter. It might, on the other hand, strike a balance between the accuracy of the information and its confidence. For example, the module <b>602</b> might be programmed to use information with lower levels of accuracy only when there is a high level of confidence in the information. The module <b>602</b> might utilize the parameters to assign weights to the information so that the location is calculated as a weighted function of the confidence and accuracy of the information.

Another use of the confidence parameters is as follows: Assume that the location service module has determined a device location and has written that location to a cache. At the time when the location is written to a cache, it is assigned perhaps a high confidence level. Assume further that all of the other location providers are unavailable to provide location information. For a period of time, the location service module <b>602</b> can use the cache location as a current location and be fairly confident that its information is generally accurate. In this case, the location service module might assign a linearly decreasing confidence level to the information over time so that at some point, it ceases to use the information or informs the user that the information cannot be guaranteed.

Location, Trust, and Timestamp

When the location providers provide their information to the location service module <b>602</b>, the information can include, in addition to the confidence and accuracy parameters, the actual location information in a known format, a trust parameter and a timestamp. The trust parameter is a metric that is assigned by the location service module <b>602</b> to one or more of the location providers and defines the trust that the location service module has for the particular location provider. The timestamp is a metric that defines the time when the location information was provided by the location provider. This assists the location service module <b>602</b> in ascertaining whether information is stale and might need refreshed.

Once the location service module <b>602</b> has all of the location information, it can then set about determining the location of the device.

<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram that describes steps in a method of determining a device context which, in this example, is the device location. These steps are implemented by the location service module <b>602</b>.

Step <b>800</b> gets the current device context. The current context can be the last calculated device context that is stored in the cache. Step <b>802</b> determines whether any of a number of context providers are available to provide context information. The location service module might do this by polling the context providers to ascertain which of the providers are active and valid. Step <b>804</b> determines whether all of the providers are inactive. If all of the providers are inactive, step <b>806</b> decreases the confidence in the current context over time and uses the current context as the device context. Step <b>802</b> then continues to monitor for current active and valid providers. If step <b>804</b> determines that one or more of the context providers are active, then step <b>808</b> orders the active and valid context providers. When the location service module <b>602</b> orders or sorts the context providers, it does so as a function of the confidence of the provider's information and/or the trust that the location service module has in the location provider. This provides a ranked list of the location providers. Step <b>810</b> checks to ascertain whether the context information appears to be correct. For example, where the context is the location of the device, the location service module <b>602</b> might know that five seconds ago the current location was Redmond, Wash. Accordingly, location information that indicates that the current location is Beijing, China would be incorrect. Step <b>812</b> then determines whether any of the context information conflicts with either the device's current context or the context information from other providers. For example, the location service module <b>602</b> can compare the context information from each of the context providers with the information in the cache. If any of the information conflicts with the cached information, then the information from that context provider can be discarded. Similarly, if context information varies inordinately as between the context providers, then step <b>814</b> can select the context providers having a predefined level of trust and perhaps use just their information (Step <b>816</b>). If there are no conflicts, then step <b>816</b> determines the current context based upon the information that is provided by all of the context providers. In the described embodiment, this step is implemented by using the information to map to a particular node in one or more of the hierarchical tree structures mentioned above. For example, the location of the device can be ascertained by mapping the information to a particular node, and then completely traversing the tree structure until the root node is reached. Step <b>818</b> then updates the current context by perhaps writing it to the cache and returns to step <b>802</b> to determine the active and valid context providers.

The method described above provides a way for the location service module to receive location information and use only the location information that appears mostly likely to represent a current location. Conflicting information can be discounted or disregarded thereby assuring that only the most trusted, accurate and confident information is utilized to determine the device's current location.

Self Monitoring

In addition to the confidence and accuracy parameters, one or more of the location providers are advantageously programmed to self monitor their own operation for various irregularities that can occur. On the occurrence of an irregularity, the location providers are configured to notify the location service module <b>602</b>. For example, the source from which the location provider receives its information may go off line for a period of time so that the location provider is unable to receive any additional information. In this case, the location provider might generate a “provider out” message and send it to the location service module <b>602</b>. When the location service module <b>602</b> receives the “provider out” message, it can then take steps to exclude the location information from that provider from any location calculations that it performs. When the location provider's source comes back on line, it can generate a “provider on” message that informs the location service module <b>602</b> that it is able to transmit location information to the module. Of course, the location service module can be notified by the location providers on the occurrence of other operational irregularities, with the above example constituting but one specific case.

Applications

Once the location service module <b>602</b> has determined the device's location, it can receive queries from one or more applications <b>608</b>. In the <figref idref="DRAWINGS">FIG. 7</figref> example, the applications include a web site application, an Outlook application, and a service discovery application. In the present example, the web site application can be any web site application that is capable of rendering location-specific services. For example, the user of the device <b>602</b> might access Amazon.com's web site to buy a favorite book. When the user purchases their book, Amazon.com must now compute the taxes that the user must pay. In this example, a script executing on Amazon.com's web site might query device <b>602</b> to learn of the user's location. In this particular example, the device might respond to the query by returning the state in which the user is making the purchase. Amazon.com can then assess the tax automatically. Amazon.com might also desire to know where the individual is located so that they can select an optimal shipping method (UPS or Express Mail). Depending on where the individual is located, one method may be preferred over the other. The Outlook application might query the location service module to ascertain the location because it (or the operating system, e.g. Windows) may change device settings based on the location of the computing device. For example, the user may print on one particular printer while at work, and another particular printer when at home. When the Outlook application determines that the user has gone home for the day, it can automatically change the device settings for the printer at the user's home. It might acquire the print settings from a personal places data store <b>714</b>. Thus, the device is automatically configured for use depending on the user's location. The service discovery application might query the device to determine its location so that it can render a particular service depending on where the device is located. For example, if the user asks the application to locate the nearest color printer, the service discovery application might query the location service module to ascertain the device's current location so that it can use this information and find the nearest color printer. Consider also that the Outlook application could configure itself email to a work location (when an individual is at work) or to a home location (when an individual is at home). In addition, the Outlook calendar can become location aware, e.g. when you change time zones, your appointments would show up in the proper time slots.

As one can imagine, the possibilities are seemingly endless. This functionality is made possible through the use of the Master World and one or more Secondary Worlds.

Application Program Interface/Events

In the described embodiment, the applications <b>608</b> communicate with the location service module <b>602</b> through one or more application program interfaces (APIs) and/or events. The applications can make function calls on the API to query the location service module as to its current location. Similarly, the applications can register for location notifications by using an events registration process. For example, an application may register for a notification when the user changes their location. Consider the case where an application requests to be notified when the user arrives at work or at home so that the application can change the device's configuration (such as printer configuration).

<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment. The steps that are described are implemented by device <b>600</b>. Step <b>900</b> receives information that pertains to the current context of the device. In this particular example, a portion of the information is received from one or more context providers which, in this case, are location providers. Step <b>902</b> processes the information on and with the device to ascertain the current context of the device. In the illustrated example, the device maintains (or has access to) one or more of the Master World and one or more Secondary Worlds. When the device receives all of the location information, it maps the information to a particular node in the hierarchical tree structure that defines the Worlds. It then traverses the tree structures to ascertain the complete context (i.e. location) of the device. Step <b>904</b> receives calls from one or more applications that request information that pertains to the device's current context or location. In the illustrated example, the applications can call one or more APIs to request the information or the applications can register for event notifications. Step <b>906</b> then supplies the applications with at least some information that pertains to the current device location. As will be discussed below, a security policy or privacy policy can be applied to the information before it is returned to the applications.

Privacy Manager

In one embodiment, a privacy manager <b>704</b> (<figref idref="DRAWINGS">FIG. 7</figref>) is provided. Although the privacy manager is illustrated as being incorporated on the device, it could be implemented by a trusted entity such as a trusted server that is not part of the mobile computing device. The privacy manager can be implemented in any suitable hardware, software, firmware or combination thereof. In the illustrated example, the privacy manager comprises a software module that is incorporated in the mobile computing device.

The privacy manager <b>704</b> addresses privacy concerns that are associated with the information that is collected by the computing device. Specifically, the location service module can calculate detailed information regarding the location of the computing device. It may be desirable, in some instances, to filter the information that is provided to various applications. That is, it is entirely likely that a user may not want their specific location information provided to untrusted applications. In these instances a user might just desire for location service module <b>602</b> to inform such applications that the user is in the State of Washington.

<figref idref="DRAWINGS">FIG. 10</figref> shows a flow diagram that describes steps in a privacy protection method in accordance with the described embodiment. These steps can be implemented by the privacy manager <b>704</b>.

Step <b>1000</b> defines a plurality of privacy levels. Exemplary privacy levels are set forth in the table immediately below:

<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="49pt" align="center" /><colspec colname="2" colwidth="63pt" align="center" /><colspec colname="3" colwidth="91pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Privacy Level</entry><entry>Approximate Scale</entry><entry>Level of Revelation</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="49pt" align="char" char="." /><colspec colname="2" colwidth="63pt" align="center" /><colspec colname="3" colwidth="91pt" align="left" /><tbody valign="top"><row><entry /><entry>0</entry><entry>—</entry><entry>No location information</entry></row><row><entry /><entry /><entry /><entry>is returned</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="49pt" align="char" char="." /><colspec colname="2" colwidth="35pt" align="right" /><colspec colname="3" colwidth="28pt" align="left" /><colspec colname="4" colwidth="91pt" align="left" /><tbody valign="top"><row><entry /><entry>10</entry><entry>100,000</entry><entry>Km</entry><entry>Planet/Continent</entry></row><row><entry /><entry>20</entry><entry>1,000</entry><entry>Km</entry><entry>Country</entry></row><row><entry /><entry>30</entry><entry>100</entry><entry>Km</entry><entry>State</entry></row><row><entry /><entry>40</entry><entry>10-100</entry><entry>Km</entry><entry>City &amp; County or Region</entry></row><row><entry /><entry>50</entry><entry>10</entry><entry>Km</entry><entry>Postal Code &amp; Phone</entry></row><row><entry /><entry /><entry /><entry /><entry>Area Code</entry></row><row><entry /><entry>60</entry><entry>1</entry><entry>Km</entry><entry>Full Postal Code (Zip + 4)</entry></row><row><entry /><entry /><entry /><entry /><entry>&amp; Area Code and Exchange</entry></row><row><entry /><entry>70</entry><entry>100</entry><entry>m</entry><entry>Phone Number &amp;</entry></row><row><entry /><entry /><entry /><entry /><entry>Building/Floor</entry></row><row><entry /><entry>80</entry><entry>10</entry><entry>m</entry><entry>Room #</entry></row><row><entry /><entry>90</entry><entry>1</entry><entry>m</entry><entry>Exact Coordinates</entry></row><row><entry /><entry namest="offset" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In the illustrated table, <b>10</b> different privacy levels are defined and each has an associated approximate scale. For example, a privacy level of 0 means that no location information is returned. A privacy level of 90 means that very detailed location information is returned.

Step <b>1002</b> assigns various privacy levels to the individual nodes in one or more hierarchical tree structures. For example, each node of the Master World and the Secondary Worlds can have a privacy level associated with it. The root node of the Master World tree structure might have a privacy level of 10, while the node that represents a current location in a Secondary World might have a privacy level of 90. Step <b>1004</b> determines the context of the computing device. In the present example, the context is the device location and examples of how this is done are given above. Individual applications that call the location service module can have privacy levels associated with them. These privacy levels can be assigned by individual users. For example, a trusted application might have a privacy level of 90, while an untrusted application might have a privacy level of 30. Step <b>1006</b> receives context queries from one or more applications. Here, an application calls the location service module <b>602</b> (<figref idref="DRAWINGS">FIG. 7</figref>) to ascertain the location of the device. Step <b>1008</b> determines the privacy level associated with the application or applications. For example, if a untrusted application calls to request location information, the privacy manager <b>704</b> would determine that the application has a privacy level of 30. The privacy manager then traverses (step <b>1010</b>) one or more hierarchical tree structures to find a node with a corresponding privacy level so that it can select the information that is associated with that node. In this example, the traversal might involve jumping from the Secondary World to the Master World to find the node that corresponds to the state in which the user is located. Once the corresponding node is found, step <b>1012</b> returns the context information (e.g. location information) associated with the node. In this case, the location service module would inform the application that the user's location is the State of Washington.

As an example, consider the following: There is a web site that gives up to the minute weather of various locations. Accordingly, you might assign this web site a privacy level of 60 so that you can receive weather information for the geographical area that corresponds to your present full postal code. Another web site might be a corporation intranet web site that is a trusted web site. Thus, any applications associated with this web site can be assigned a privacy level of 90 so that you can give them precise location information as to your whereabouts.

Thus, in the present example, the computing device is able to determine the source (i.e. application) of its queries and modulate the information that is returned to the application as a function of the application's identity. The computing device is able to do this because it has access to the Master World and one or more Secondary Worlds. The above description constitutes but one exemplary way of accomplishing this feat.

Location Beacons as a Location Provider

In one embodiment, one of the location providers comprises a location beacon that beacons or transmits information to enable a computing device to actively participate in its current context. Location beacons can comprise standalone devices that can be retrofitted onto existing infrastructures, e.g. a smoke detector or wall outlet in order for the device to have a power source.

<figref idref="DRAWINGS">FIG. 11</figref> shows an exemplary beacon <b>1100</b> that is mounted on a structure <b>1102</b>. Structure <b>1102</b> can be any suitable structure such as a wall in a conference room or public place, a smoke detector, an electrical socket and the like. In the described embodiment, the location beacons are small inexpensive devices that can be permanently mounted in special locations such as conference rooms, building lobbies, airport gates, public places and the like. The beacons announce the physical location in the form of an EID and/or LUID to all mobile devices that are within range, such as laptops, tablet PCs, hand held computers, mobile phones, wearable computers and the like.

In the described embodiment, the location beacon can identify the particular locations by beaconing standard information that will be understood by the mobile computing devices. In the present example, the beacons can transmit one or two location identifier pairs comprising an EID/URL pair and a LUID/URL pair. The beacon might also transmit multiple LUIDs. The EID and LUID give the present node location in the Master World and Secondary World respectively. The URLs provide a reachable location for the Master and Secondary Worlds. For example, the URL associated with the Secondary World can give a service location that the device can use to query information about the Secondary World so that it can derive its context and take advantage of resources or services that are associated with the nodes in the Secondary World.

The beacons can also transmit a digital signature that can be used by the device to ascertain that the beacon is valid and legitimate. Any suitable signature or verification method could be used. In addition, and of particular use in the context-aware environment, the beacon can be programmed to transmit code download pointers to devices within range. The code download pointers can enable the computing device to access software code that permits them to interact with their environment. Consider the following example: You walk into a conference room with your cell phone computing device and immediately a beacon in the conference room transmits your location in the form of an EID/URL pair and a LUID/URL pair. Your device uses the information pairs to ascertain its location in the Master and Secondary Worlds as described above. The beacon also transmits a code download pointer that points to software code that enables you to operate the video projector in the conference room using your hand-held cellular phone. In this manner, the beacon serves as more than just a location beacon—it permits you, through your computing device, to actively participate in your surroundings.

The beacons can transmit the information in any suitable way, e.g. wireless methods including infrared and radio frequencies. In one embodiment, Bluetooth short range radio frequency communication can be used to provide a low cost, low power alternative.

Context-Aware Vehicle

<figref idref="DRAWINGS">FIG. 12</figref> shows an exemplary vehicle (e.g., automobile) computer system <b>1200</b> that can be used in connection with the context-aware systems and methods described above and below. System <b>1200</b> is configured for use in a vehicle such as a car, truck or other similar conveyance. When in place in a vehicle, computer system <b>1200</b> can provide a multitude of context-aware services as will become apparent below.

Vehicle computer system <b>1200</b> has a centralized computer <b>1202</b> coupled to various external peripheral devices, including a display device <b>1204</b>, security sensors <b>1206</b>, a vehicle diagnostic interface <b>1208</b>, speakers <b>1210</b>, a vehicle battery <b>1212</b>, a backup battery <b>1214</b>, and antenna(s) <b>1216</b>. The computer <b>1202</b> is assembled in a housing <b>1218</b> that is sized to be mounted in a vehicle dashboard, similar to a conventional automobile stereo. In the illustrated example, the housing <b>1218</b> has a form factor of a single DIN (Deutsche Industry Normen). Alternatively, it could be housed in a 2 DIN unit or other special form factor for an OEM.

The computer <b>1202</b> runs an open platform operating system which supports multiple applications. Using an open platform operating system and an open computer system architecture, various software applications and hardware peripherals can be produced by independent vendors and subsequently installed by the vehicle user after purchase of the vehicle. This is advantageous in that the software applications do not need to be specially configured for uniquely designed embedded systems. In the illustrated example the open hardware architecture runs a multitasking operating system that employs a graphical user interface. A multitasking operating system allows simultaneous execution of multiple applications. One such operating system is the “Windows” brand of operating systems (e.g., the “Windows CE” operating system) sold by Microsoft Corporation of Redmond, Wash.

The computer <b>1202</b> can include at least one storage drive which permits the vehicle user to download programs and data from a storage medium. In the illustrated implementation, the computer <b>1202</b> has a CD ROM (or other optical) drive <b>1220</b> which reads application-related CDs, as well as musical, video, game, or other types of entertainment CDs. The computer <b>1202</b> may also include other storage devices, such as a magnetic disk drive, smart card reader, PCMCIA card sockets, a hard disk drive, or a DVD (“digital video disk” or “digital versatile disk”) drive.

The storage drives are mounted in a base unit <b>1228</b> of the housing <b>1218</b>. The base unit <b>1228</b> is constructed and sized to be mounted in the dashboard. Optionally, this base unit may be removable in the same fashion as a laptop computer and its associated docking station. This option allows the user to take the vehicle computer to his/her home or office to serve as his/her portable PC. The housing <b>1218</b> also has a faceplate <b>1230</b> which is pivotally mounted to the front of the base unit <b>1228</b> and may optionally be detachable. The faceplate can be rotated to permit easy and convenient access to the storage drives.

The computer <b>1202</b> has a keypad <b>1232</b> and a display <b>1234</b> on the faceplate <b>1230</b>. The operating system executing on the computer <b>1202</b> controls the faceplate peripheral, which, through the faceplate processor, can control the faceplate keys <b>1232</b> and the faceplate display <b>1234</b> as peripheral devices when the faceplate is attached to the base unit. Additionally, the computer <b>1202</b> has a voice recognition device to permit the user to verbally enter commands in a hands-free, eyes-free environment. These voice commands can be used for controlling most operating modes of the vehicle computing platform. The computer <b>1202</b> is also equipped with an IrDA (infrared developers association) transceiver port <b>1236</b> mounted on the faceplate <b>1230</b> to transmit and receive data and programs using infrared signals. The entire faceplate unit <b>1230</b> behaves as a multifunction peripheral to the computing platform.

The computer <b>1202</b> can output visual data to the LCD <b>1234</b> at the faceplate, or to the display device <b>1204</b>. In the exemplary illustration, display <b>1234</b> is a back lit LCD and display <b>1204</b> is a small flat panel display (e.g., 6.4″ screen) that is movably mounted on a stand or yoke and remotely located from the computer. Additional display devices may also be added that are similar to display <b>1204</b> or <b>1234</b>. Different types of display devices may also be added, such as a Heads Up Display (HUD).

The display <b>1204</b> is fully adjustable to different viewing positions that can be seen by the driver or other passengers in the vehicle. The type of data displayed can range widely from word instructions concerning the vehicle's performance, to diagrammatic directions from a navigation system, to video movies for in-car entertainment. The display <b>1204</b> can be equipped with an automatic override switch <b>1238</b> which automatically disables the display of any non-driving related data when positioned to be viewed by the driver. When facing the driver, only information supportive and helpful to driving (e.g., diagnostics, navigation directions) is displayed on the monitor, while distracting information (e.g., video movies, games) is blocked from display. In one implementation, the switch is an electrical cylindrical switch which closes when the display is capable of being viewed by the driver; thus, the software can sense the display position and only allow permitted information to be displayed.

In general, the vehicle computer system <b>1200</b> can be used to integrate multiple vehicle-related systems onto one open platform hardware and software architecture. For instance, the vehicle computer system <b>1200</b> can serve as a multimedia entertainment system, a navigation system, a communications system, a security system, and a diagnostics system. Moreover, the vehicle computer system <b>1200</b> provides additional functionality traditionally associated with desk-top and laptop personal computers. For instance, vehicle computer system <b>1200</b> can support word processing applications, spreadsheet applications, database applications, web browser applications, and appointment/schedule applications. Furthermore, the vehicle computer system <b>1200</b> can be configured to operate as a server to other computing units in the vehicle to distribute games, video movies, and the like to passengers. Furthermore, the system includes an internet connectivity engine <b>1240</b> that is configured to establish connectivity with the Internet. This can be done in any suitable way. For example, the internet connectivity engine <b>1240</b> can wirelessly establish connectivity with the Internet through known wireless techniques.

In accordance with the described embodiment, information can be displayed on either display device <b>1204</b> or display <b>1234</b>. The information can be provided by an application running on computer <b>1202</b>, or by a device external to computer <b>1202</b>, such as sensors <b>1206</b> or via diagnostic interface <b>1208</b>, antenna <b>1216</b>, IrDA port <b>1236</b>, etc. Such information can also be provided to the computer via the internet connectivity engine <b>1240</b>. Information that can be displayed includes any type of data or control information. Additionally, information to be displayed can include a “caption” or “label” that describes the data. Examples of data that can be displayed include street addresses, phone numbers, and directions (e.g., “Turn Left At Light On Main Street”). Such data can be displayed either including a caption describing the data (e.g., “Address: 12345 Washington Street”, where “Address:” is the caption portion of the information) or without a caption (e.g., “12345 Washington Street”). Examples of control information include toolbars, menu options, and user-selectable on-screen regions (such as buttons), as well as instructions, headings, and other descriptive information.

In the discussion herein, the various embodiments are described in the general context of computer-executable instructions, such as program modules, being executed by one or more conventional personal computers. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the described embodiments can be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. In a distributed computer environment, program modules may be located in both local and remote memory storage devices.

<figref idref="DRAWINGS">FIG. 13</figref> shows exemplary components of computer <b>1202</b> of <figref idref="DRAWINGS">FIG. 12</figref> in more detail. Computer <b>1202</b> includes one or more processors or processing units <b>1352</b>, a system memory <b>1354</b>, and a bus <b>1356</b> that couples various system components including the system memory <b>1354</b> to processors <b>1352</b>.

The bus <b>1356</b> represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The system memory <b>1354</b> includes read only memory (ROM) <b>1358</b> and random access memory (RAM) <b>1360</b>. A portion of the operating system, such as kernel <b>1362</b>, contains the basic routines that help to transfer information between elements within computer <b>1202</b>, such as during start-up, is stored in ROM <b>1358</b>.

A number of program modules can be stored in ROM <b>1358</b> or RAM <b>1360</b>, including an operating system <b>1364</b> and one or more application programs <b>1366</b>. A user may enter commands and information into computer <b>1202</b> through various input devices, such as a keyboard (e.g., keypad <b>1232</b> of FIG. <b>12</b>), touchscreen, pointing device, microphone, joystick, game pad, satellite dish, scanner, or the like (not shown in FIG. <b>13</b>). These and other input devices are coupled to the processing unit <b>1352</b> through an input/output (I/O) interface <b>1368</b> that is coupled to the bus <b>1356</b>. A display <b>1204</b> or <b>1234</b>, or other type of display device, is also connected to the bus <b>1356</b> via an interface, such as a video adapter(s) <b>1370</b>. Data to be displayed on display <b>1204</b> or <b>1234</b> is provided to adapter <b>1370</b> by a display generator <b>1372</b> of operating system <b>1364</b>. In addition to the display, computers can include other peripheral output devices (not shown in <figref idref="DRAWINGS">FIG. 13</figref>) such as speakers and printers that are coupled to the processing unit <b>1352</b> through I/O interface <b>1368</b>.

Generally, the processors of computer <b>1202</b> are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. For example, the above-described context and location service can be stored in this manner so as to permit the computer to make full use of the context-aware (location-aware) applications described above and below.

The embodiments described herein include these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the steps described below in conjunction with a microprocessor or other data processor. The described embodiments also include the computer itself when programmed according to the methods and techniques described below. Furthermore, certain sub-components of the computer may be programmed to perform the functions and steps described below. The described embodiments include such sub-components when they are programmed as described. In addition, the described embodiments include data structures, described below, as embodied on various types of memory media.

For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.

Exemplary Context-based Architecture

<figref idref="DRAWINGS">FIG. 14</figref> shows an exemplary architecture <b>1400</b> that can be utilized to implement a context-aware vehicle. Some of the components of the architecture are similar to or the same as components that have already been discussed above. To this extent, these components are not described in additional detail here. These components include an application program interface/events component <b>1402</b>, context service module <b>1404</b>, context provider interface <b>1406</b>, and privacy manager <b>1408</b>.

Additional components that are germane to this discussion include one or more applications <b>1410</b> that are executable on the vehicle's computer, one or more context providers <b>1412</b>, a context data store <b>1414</b>, and a behavior engine <b>1418</b>.

Applications <b>1410</b> can include any suitable applications that are capable of being executed in connection with a vehicle such as an automobile. Exemplary applications can include those that are used to implement or be used in connection with audio/visual equipment or peripheral devices such as the radio, entertainment devices, visual displays, temperature regulation devices, and various controllers that can be associated with equipment on the vehicle, to name just a few.

The context providers <b>1412</b> can be any suitable context providers that are capable of providing context information, via the context provider interface <b>1406</b> and context service module <b>1404</b>, to the behavior engine <b>1418</b>. Context providers can include such things as environmental sensors (e.g. light, heat, smog and the like). It will be appreciated that although the context providers are shown as being on the computing device itself (i.e. located on the vehicle), the context providers can be located off of the vehicle. For example, context providers can broadcast wireless context information for receipt by the computing device.

Context store <b>1414</b> can store per-user context preferences that are available locally and/or it can cache per-user context preferences that are present somewhere outside the vehicle. This store can also be used to store context preference information that is common to all users (per-vehicle). This store can also be used to temporarily store all the context data that is being provided by the various context providers. This way, the behavior engine can act on this data at a later time, rather than instantaneously. In addition, the store can hold per-vehicle data. User-specific context information can pertain to any suitable type of context information. As an example, the user might provide their preferences for seat settings, vehicle temperature, vehicle interior lighting, radio volume and the like. These preferences can be maintained on the vehicle in a vehicle store, or externally of the vehicle in, for example, a network accessible data store (e.g. a data store accessible via a Web server).

Behavior engine <b>1418</b> comprises a software module that receives context information from one or more sources and manipulates in some way or causes the behavior of the vehicle to be manipulated. Manipulation of the vehicle's behavior can manifest itself, in the illustrated example, through settings or other parameters that are passed from the behavior engine <b>1418</b> to one or more applications <b>1410</b> and that affect the behavior of the vehicle. The settings or parameters thus cause the application to function, in some way, in a manner that is unique to the context in which the vehicle is determined to be.

As an example consider the following: A vehicle is traveling on a long trip that started early in the morning. As dusk approaches, a context provider <b>1412</b> in the form of a light sensor provides information to the context service module <b>1404</b> which, in turn, ascertains that outside lighting conditions are sufficient to require the headlights to be turned on. Accordingly, the behavior engine <b>1418</b> causes the application associated with the headlights to turn the headlights on. In this specific example, the behavior engine can also cause the application associated with the driver's display to change the light contrast setting so that the driver can more easily view the display. This solution, as well as the other solutions described below, can be advantageously implemented in software so that the necessity of building any hardwired hardware solutions is eliminated.

As another example, consider the following: While traveling in a context-aware vehicle, the vehicle enters an area where there is a large amount of smog. A context provider in the form of a smog sensor provides information to the context service modules which, in turn, determines that smoggy conditions exist. As a result, the behavior engine <b>1418</b> causes the application <b>1410</b> associated with the vehicle's ventilation system to automatically shut off the outside supply of air.

<figref idref="DRAWINGS">FIG. 15</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the illustrated example, the method is implemented in software. In a specific implementation, this method can be implemented in connection with the architecture shown in FIG. <b>14</b>.

Step <b>1500</b> receives context information. This information can comprise any suitable type of information and can be received in any suitable way. For example, the context information can comprise user-specific information. This user-specific information can be received from a user who physically enters the information into the vehicle's computer. Alternately, the user-specific information can be retrieved from a data store, either onboard or remote from the vehicle. If the information is onboard the vehicle, the information can simply be retrieved from whatever data store holds the information. If the information is maintained remote from the vehicle (e.g. in a Web-accessible data store), the information can then be retrieved in any suitable way such as via a wireless connection with the Web that is then used to access the remote data store and retrieve the information.

The context information can also comprise information associated with the vehicle's operating environment and can be gleaned from various different sensors that can be provided on the vehicle. Examples of this are given above.

Step <b>1502</b> determines, from the context information, a current vehicle context. This step can be implemented by a context service module such as module <b>1404</b> in FIG. <b>14</b>. The current context can be determined by ascertaining the current vehicle user. The current context can also be determined by making a decision, based upon the context information, about the likely context of the vehicle. For example, if the context information suggests that it is likely dark outside of the vehicle, a decision concerning the current context can be made with an ascertainable degree of certainty. Based on the current vehicle context, the behavior of the vehicle can then be modified in some way or manner that is consistent with the vehicle's current context (step <b>1504</b>). This step can be implemented by a behavior engine such as engine <b>1418</b> in FIG. <b>14</b>. The behavior engine receives information from the context service module <b>1404</b> indicating the current vehicle context. Based on this, the behavior engine can cause settings or other parameters to be passed to applications associated with the context so that the applications can modify the behavior of the vehicle in some way.

Exemplary Location-Based Architecture

<figref idref="DRAWINGS">FIG. 16</figref> shows an exemplary architecture <b>1600</b> that can be utilized to implement a location-aware vehicle. Some of the components of the architecture are similar to or the same as components that have already been discussed above. To this extent, these components are not described in additional detail here. These components include an application program interface/events component <b>1602</b>, location service module <b>1604</b>, location provider interface <b>1606</b>, and privacy manager <b>1608</b>.

Additional components that are germane to this discussion include one or more applications <b>1610</b> that are executable on the vehicle's computer or on the vehicle itself, one or more location providers <b>1612</b>, a context store <b>1614</b>, and a behavior engine <b>1618</b>.

Applications <b>1610</b> can include any suitable applications that are capable of being executed in connection with a vehicle such as an automobile. Exemplary applications can include those that are used to implement or be used in connection with a location-sensitive service. For example, one application can comprise an Internet connectivity application that establishes an Internet connection via a local ISP. For example, the Internet connectivity engine <b>1240</b> (<figref idref="DRAWINGS">FIG. 12</figref>) can call a toll free telephone number to get a list of affiliated ISPs and a set of &lt;location, phone number&gt; pairs. This list can also be pre-installed in the vehicle's computer, or downloaded periodically via that Internet. When the user tries to access the Internet, the Internet connectivity engine <b>1240</b> calls the location service module <b>1604</b> to ascertain the current location. Based on the current location, the Internet connectivity engine <b>1240</b> selects an access number that is local to the area in which the vehicle is located. As the vehicle moves between locations, the Internet connectivity engine <b>1240</b> can get location updates and update its local access number. Another application can control the radio and its various settings, as will be discussed in more detail below in the section entitled “Radio Station Settings”.

The location providers <b>1612</b> can be any suitable location providers that are capable of providing location information, via the location provider interface <b>1606</b> and location service module <b>1604</b>, to the behavior engine <b>1618</b>. Exemplary location providers are discussed above. In vehicle-based applications, however, one source of location information comprises a GPS source that provides GPS information to an onboard location provider.

Context store <b>1614</b> can store per-user location preferences that are available locally and/or it can cache per-user location preferences that are present somewhere outside the vehicle. This store can also be used to store location preference information that is common to all users (per-vehicle). This store can also be used to temporarily store all the location data that is being provided by the various location providers. This way, the behavior engine can act on this data at a later time, rather than instantaneously. In accordance with the described embodiment, users can provide user-specific location information that is maintained in store <b>1614</b>. This user-specific location information can pertain to any suitable type of location information. As an example, and one that is explored in more detail below, a user might enter their favorite radio stations for several different cities that they travel to often. These preferences can be maintained and, when the location service determines the location of the user's vehicle to be one of the subject cities, the behavior engine <b>1618</b> causes the application that is associated with the station controller to automatically program the radio stations for the new city.

Behavioral engine <b>1618</b> comprises a software module that receives location information from one or more sources and manipulates in some way the behavior of the vehicle. Manipulation of the vehicle's behavior can manifest itself, in the illustrated example, through settings or other parameters that are passed from the behavior engine to one or more applications <b>1610</b>. The settings or parameters thus cause the application to function, in some way, in a manner that is unique to the location in which the vehicle is determined to be.

<figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram that describes steps in a method in accordance with the described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the illustrated example, the method is implemented in software. In a specific implementation, this method can be implemented in connection with the architecture shown in FIG. <b>16</b>.

Step <b>1700</b> receives location information. This information can comprise any suitable type of information and can be received in any suitable way. For is example, the location information can comprise user-specific information. This user-specific information can be received from a user who physically enters the information. Alternately, the user-specific information can be retrieved from a data store, either onboard or remote from the vehicle. If the information is onboard the vehicle, the information can simply be retrieved from whatever data store holds the information. If the information is maintained remote from the vehicle (e.g. in a Web-accessible data store), the information can then be retrieved in any suitable way such as via a wireless connection with the Web.

Step <b>1702</b> determines, from the location information, a current vehicle location. This step can be implemented by a location service module such as module <b>1604</b> in FIG. <b>16</b>. Based on the current vehicle location, the behavior of the vehicle is modified in some way (step <b>1704</b>). This step can be implemented by a behavior engine such as engine <b>1618</b> in FIG. <b>16</b>. The behavior engine receives information from the location service module <b>1604</b> indicating the current vehicle location. Based on this, the behavior engine can cause settings or other parameters to be passed to applications associated with the location so that the applications can modify the behavior of the vehicle in some way.

Radio Station Settings

In one embodiment, a user can specify radio stations and locations associated with those radio stations. Based on the location of the vehicle, the user-specified radio stations for the particular radio stations are mapped automatically to the buttons of the radio when the vehicle's location coincides with a location specified by the user. As an example, consider the following: Assume that 950 AM is the all-sports radio channel in Seattle and 880 AM is the all-sports radio channel in Portland. Further assume that the user has specified that button #1 of the radio is to be associated with 950 AM when his vehicle is located in Seattle and 880 AM when his vehicle is located in Portland. These user specifications are referred to as the user's preferences. The user's preferences are stored in an accessible location such as a per-user location store <b>1614</b>. Assume now that the user has to travel from Portland to Seattle on business. When the location service on board the user's vehicle ascertains that the vehicle's location is Seattle, the behavior engine <b>1618</b> causes the application associated with the radio station controller to map Seattle station 950 to button #1 of the radio. This happens automatically without the need for any user intervention.

<figref idref="DRAWINGS">FIG. 18</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the described embodiment, the method is implemented in software. Suitable software is described above in connection with <figref idref="DRAWINGS">FIGS. 16 and 17</figref>.

Step <b>1800</b> associates one or more radio stations with one or more locations. This step can be implemented by a user establishing such an association by inputting their preferences into the vehicle's computer. This step can also be implemented by a user storing their preferences in some other location that is accessible by the vehicle's computer (e.g. a Web-accessible location). The preferences are then stored in a per-user location store such as the one described above. The store can either be onboard a vehicle or remote from the vehicle. If the store is remote from the vehicle, then the vehicle's computer can establish a suitable connection, for example via the Internet, and fetch the user's preferences. Step <b>1802</b> determines the location of the vehicle. Any suitable method or technique can be used to determine the vehicle's location. In this specific example, a location service, implemented in software, can be used. Recall that the location service discussed in this document makes use of hierarchical tree structures in the form of Primary and Secondary Worlds that permit the location service to ascertain its location based upon input from one or more location providers. Once the location is determined, radio stations that are associated with that location are mapped (step <b>1804</b>) to radio station buttons on the vehicle's radio. This step is implemented, in the present example, through the interaction between the behavior engine <b>1618</b> and an appropriate application <b>1610</b> that manages the mapping of the radio stations. Once the mapping has taken place, the user is free to select from among the station that they previously specified. Step <b>1806</b> then determines whether the vehicle is at a new location. If so, the method determines the new location through the use of the location service and then branches to step <b>1804</b> to map any new stations associated with the new location to the radio's buttons. If there is no new location, the method does nothing and simply returns to step <b>1806</b>.

The embodiment described immediately above provides a system and methodology by which a user can make radio station preferences for different locations known to the user. These known preferences are then enforced automatically as a function of a vehicle's location.

In certain circumstances, however, individuals may be unaware of the specific radio stations in all of the potential locations to which they may travel that play the type of music or content to which they desire to listen. For example, an individual may not know the specific radio stations in Fresno, San Francisco, Sacramento, and San Diego that play the type of music that they prefer. Accordingly, one embodiment allows the user to associate each of the radio buttons with a radio station type. Exemplary radio station types include, without limitation, those that play light rock, heavy metal, all-news, all-sports, classical, talk shows and the like. The vehicle's computer maintains or has access to a list that associates radio station types, location, and radio station frequency (i.e. station number). This list can be resident on the vehicle's computer, or can be periodically downloaded from the Internet. Now, when a user travels from location to location, the location service determines the vehicle's location as described above, and notifies the vehicle's behavior engine. The behavior engine then causes the appropriate application that manages the radio station selections to map the new radio station frequencies (or settings) to appropriate buttons on the vehicle's radio. In this way, a user need simply specify radio station types and need not know specific radio station settings.

<figref idref="DRAWINGS">FIG. 19</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the described embodiment, the method is implemented in software. Suitable software is described above in connection with <figref idref="DRAWINGS">FIGS. 16 and 17</figref>.

Step <b>1900</b> associates at least one radio station type with a radio button. This step can be implemented by a user specifying their associations or preferences. For example, hard rock can be associated with button #1, soft rock with button #2, and so on. These associations or preferences are then either maintained by or accessible to the vehicle's computer. Step <b>1902</b> determines the vehicle's location. This step can be implemented as described above. Step <b>1904</b> maps, for a given location, each radio station frequency for a radio station type to a radio station button. So, for example, as a user drives from San Francisco to San Diego, their preferences for radio station types (i.e. classical, rock, sports and the like) are automatically and seamlessly made available to the user via the radio buttons.

Location-based Information

In another embodiment, the location of a vehicle is utilized as the basis to provide the driver with information that can be of interest to them. Specifically, the location service onboard the vehicle determines the vehicle's location as set forth above. Once the location of the vehicle is ascertained, various information associated with or pertaining to that location or locations nearby can be presented to the driver. This information can be any information that might be of interest to the driver. For example, such information can include, without limitation, upcoming weather, traffic reports, rest stops, suggestions regarding food, gas stations, scenic viewpoints and the like. As an example, consider the following: A user indicates in their preferences that they prefer to fill their car with gas from Texaco stations only. While traveling on a trip, the location service determines the vehicle's location. In conjunction with determining the vehicle's location, an application executing on the vehicle's computer informs the driver that there are 3 Texaco stations within the next 100 miles, and the distance to each of the stations. The location service can ascertain this through the use of Primary and Secondary World structures as well as IDs that are associated with each of the Texaco stations, as described above in detail. It will be appreciated that the information that is provided to the user is different from and, in some cases independent of known navigation information (i.e. street maps and directional information and the like). The information that is provided to the users can be associated with one or more user-specified preferences. For example, the user might have specified that they only like to eat at Denny's, Stuckeys, and McDonald's while on the road. Accordingly, once the location service determines the location of the user's vehicle, the user can be advised of the nearest Denny's, Stuckeys, and McDonald's.

<figref idref="DRAWINGS">FIG. 20</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the described embodiment, the method is implemented in software.

Step <b>2000</b> determines a vehicle location. Location can be determined as described above. Step <b>2002</b> provides location-specific information for the user or driver of the vehicle. This information can be provided in any suitable way. In one particularly useful implementation, the location-specific information can be provided via a display that the user can view. The location-specific information can be information that is generally provided to all drivers (i.e. upcoming viewpoints, rest stops etc.). Alternately, the information can be user-specific and can be based on user-provided preferences.

User as a Context

In one embodiment, one context of a vehicle comprises the user or driver, as was mentioned above. That is, each user or driver is presumed to have preferences that are associated with a user-specific experience that they desire when they use the vehicle. For example, one user might have desired seat settings, while another driver might have different seat settings. When the context is location, different drivers might have different preferences that indicate where they desire to eat, points of interest, radio station types, and the like.

Consider the case when the vehicle is a rental car. In this instance, the vehicle is subject to use by a large number of users. Each user most assuredly will have different preferences that govern their user experience.

<figref idref="DRAWINGS">FIG. 21</figref> is a flow diagram that describes steps in a method in accordance with one described embodiment. The method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the described embodiment, the method is implemented in software.

In accordance with one embodiment, user preferences are collected (step <b>2100</b>) and stored (step <b>2102</b>) or otherwise maintained in a vehicle-accessible location. For example, if the vehicle is a family car, the preferences of family drivers might be stored in a locally maintained store. If the vehicle is a rental car, the preferences might be stored in a large preference store remote from the vehicle. One example of a remote store is one that is accessible via the Internet through, for example, a Web server. For example, <figref idref="DRAWINGS">FIG. 22</figref> shows a system generally at <b>2200</b> that comprises multiple vehicles <b>2202</b>. Each vehicle is equipped with a vehicle computer <b>2204</b> such as that described above. A central server <b>2206</b> is accessible via the Internet and has access to a data store <b>2208</b> in which user preferences are stored. Each vehicle's computer can wirelessly access the Internet, as described above, so that the computer can gain access to various user preferences.

In this embodiment, a user of the vehicle first authenticates or identifies themselves to the vehicle (step <b>2104</b>) at which point their preferences are retrieved (step <b>2106</b>). As noted above, the preferences can be retrieved from a local storage location, or from a remote storage location. A user can authenticate themselves in any suitable way. For example, a password might be used. Alternately, an authentication service like Microsoft's Passport service might be used which authenticates the user via the Internet. Further, alternately, authentication can be implemented through fingerprinting techniques, voice recognition, or any other suitable biometrics techniques. Consider also the following example. A user is a rental car customer and is issued a “Preferred” card. This preferred card uniquely identifies the user. When the user rents a car, the attendant at the rental car counter swipes their card through a card reader which identifies the customer. Based on the customer's identity, a computer retrieves the customer's preferences from a store and communicates the preferences to a car that is waiting for the customer.

Once the user is authenticated and the user's preferences are retrieved, the behavior engine (<b>1418</b> or <b>1618</b>) causes applications executing on the vehicle's computer and which are associated with the subject of the user's preference, to provide a user-specific experience (step <b>2108</b>). This user-specific experience can involve everything from adjusting the seat settings, to automatically mapping radio station types to radio buttons, to providing location-specific information that may likely be of interest to the user. In the rental car example above, when the customer arrives at their car, their preferences have already been implemented and a user-friendly car is waiting.

Accordingly, by maintaining or having access to user-specified preferences, the user's vehicle experience can be automatically tailored to a user's likes, while avoiding a user's dislikes. User convenience is enhanced in that once their preferences are established, they need not worry about configuring a vehicle to suit their preferences. This can all be done automatically for them.

Conclusion

The embodiments described above provide a uniform, standardized way to enhance the world of context aware computing. The embodiments provide a way for individuals to uniquely experience the world around them by ascertaining their location in the world in a standard way. The embodiments also provide a way for service providers to uniquely position their goods and services in a manner that is sensitive to and appreciates the contexts, e.g. locations, of various consumers of the goods and services. Unique and useful architectures and data structures are employed to facilitate the user's computing experience and provide for an individual-centric experience.

Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.