System and method for identifying vehicle by utilizing detected magnetic field

A device includes a field-detecting component, an input component, an accessing component, a comparing component and an identifying component. The field-detecting component can detect a field and generate a detected field signature based thereon. The input component can input the detected field signature into a database. The accessing component can access the detected field signature from the database. The comparing component can generate a comparison signal. The identifying component can identify item or location based on the comparison signal. The field-detecting component can further detect a second field and generate a second detected field signature based on the detected second field. The comparing component can generate the comparison signal based on a comparison of the detected field signature and the second detected field signature.

BACKGROUND

Vehicle telematics is the technology of sending, receiving and storing information to and from vehicles and is generally present (at least to a limited extent) in the automotive marketplace today. For example, both General Motors (through their OnStar offering) and Mercedes Benz (through their Tele-Aid and more recent embrace system offering) have long offered connected-vehicle functionality to their customers. Both of these offerings make use of the data available on a vehicle's CAN bus, which is specified in the OBD-II vehicle diagnostics standard. For example, the deployment of an airbag, which suggests that the vehicle has been involved in a crash, may be detected by monitoring the CAN bus. In this event, a digital wireless telephony module that is embedded in the vehicle and connected to the vehicle's audio system (i.e., having voice connectivity) can initiate a phone call to a telematics service provider (TSP) to “report” the crash. Vehicle location may also be provided to the TSP using the vehicle's GPS functionality. Once the call is established, the TSP representative may attempt to communicate with the vehicle driver, using the vehicle's audio system, to assess the severity of the situation. Assistance may thus be dispatched by the TSP representative to the vehicle as appropriate.

Historically, these services were focused entirely on driver and passenger safety. These types of services have expanded since their initial roll-out, however, and now offer additional features to the driver, such as concierge services. The services, however, remain mainly focused on voice based driver to call center communication, with data services being only slowly introduced, hindered by low bandwidth communication modules, high cost and only partial availability on some model lines.

As a result, while generally functional, vehicle telematics services have experienced only limited commercial acceptance in the marketplace. There are several reasons for this. In addition to low speeds and bandwidth, most vehicle drivers (perhaps excluding the premium automotive market niche) are reluctant to pay extra for vehicle telematics services, either in the form of an upfront payment (i.e., more expensive vehicle) or a recurring (monthly/yearly) service fee. Moreover, from the vehicle manufacturer's perspective, the services require additional hardware to be embedded into the vehicle, resulting in extra costs on the order of $250 to $350 or more per vehicle which cannot be recouped. Thus, manufacturers have been slow to fully commit to or invest in the provision of vehicle telematics equipment in all vehicles.

There have been rudimentary attempts in the past to determine when a smartphone is in a moving vehicle. Wireless service provider AT&T, Sprint and Verizon, for example, offer a smartphone application that reacts in a specific manner to incoming text messages and voice calls when a phone is in what AT&T calls DriveMode™. With the AT&T DriveMode™ application, a wireless telephone is considered to be in “drive mode” when one of two conditions are met. First, the smartphone operator can manually turn on the application, i.e., she “tells” the application to enter drive mode. Alternatively, when the DriveMode application is in automatic on/off mode and the smartphone GPS sensor senses that the smartphone is travelling at greater than 25 miles per hour, the GPS sensor so informs the DriveMode application, the DriveMode application concludes that the smartphone is in a moving vehicle, and drive mode is entered.

Both of these paths to engaging the AT&T DriveMode application—the “manual” approach to entering drive mode and the “automatic” approach to entering drive mode—are problematic. First, if the smartphone operator forgets or simply chooses not to launch the DriveMode application prior to driving the vehicle when the application is in manual mode then the application will not launch. Second, in automatic on/off mode AT&T's use of only the GPS sensor to determine when a smartphone is in a moving vehicle is problematic for a number of reasons. First, the speed threshold of the application is arbitrary, meaning that drive mode will not be detected/engaged at less than 25 mph. If the vehicle is stopped in traffic or at a traffic signal, for example, then the DriveMode application may inadvertently terminate. Second, and perhaps more importantly, AT&T's DriveMode application requires that the smartphone's GPS functionality be turned on at all times. Because the use of a smartphone's GPS sensor is extremely demanding to the battery resources of a smartphone, this requirement severely undermines the usefulness of AT&T's application. Thirdly this method does not differentiate between the type of vehicle that the phone is in, e.g. a bus, a taxi or a train and therefore allows no correlation between the owner of the phone and her driving situation. For the classic embedded telematics devices to be replaces by smartphones it is important to correlate the driver and smartphone owner with her personal vehicle. Only then the smartphone can truly take the functional role of an embedded telematics device in a vehicle.

Accordingly, for at least the foregoing reasons there exists a need and it is an object of the present invention to provide an improved method and apparatus of determining the specific identity and type of vehicle a smartphone is in.

SUMMARY

The present invention provides an improved method and apparatus of determining the specific identity and type of vehicle a smartphone is in.

Various embodiments described herein are drawn to a device, for use with a database. The device includes a field-detecting component, an input component, an accessing component, a comparing component and an identifying component. The field-detecting component can detect at least one of an electric field, a magnetic field and an electro-magnetic field and can generate a detected field signature based on the detected one of an electric field, a magnetic field and an electro-magnetic field. The input component can input the detected field signature into the database. The accessing component can access the detected field signature from the database. The comparing component can generate a comparison signal. The identifying component can identify one of an item and a location based on the comparison signal. The field-detecting component can further detect a second one of an electric field, a magnetic field and an electro-magnetic field and can generate a second detected field signature based on the detected second one of an electric field, a magnetic field and an electro-magnetic field. The comparing component can generate the comparison signal based on a comparison of the detected field signature and the second detected field signature.

DETAILED DESCRIPTION

Aspects of the present invention are drawn to a system and method for determining a specific item and/or location by utilizing field properties within and/or near the specific item and or location.

As used herein, the term “smartphone” includes cellular and/or satellite radiotelephone(s) with or without a display (text/graphical); Personal Communications System (PCS) terminal(s) that may combine a radiotelephone with data processing, facsimile and/or data communications capabilities; Personal Digital Assistant(s) (PDA) or other devices that can include a radio frequency transceiver and a pager, Internet/Intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and/or conventional laptop (notebook) and/or palmtop (netbook) computer(s), tablet(s), or other appliance(s), which include a radio frequency transceiver. As used herein, the term “smartphone” also includes any other radiating user device that may have time-varying or fixed geographic coordinates and/or may be portable, transportable, installed in a vehicle (aeronautical, maritime, or land-based) and/or situated and/or configured to operate locally and/or in a distributed fashion over one or more location(s).

In one non-limiting example embodiment, a smartphone is used to measure a magnetic field associated with a vehicle to identify the vehicle. In another non-limiting example embodiment, a smartphone is used to measure a magnetic field associated with a house to identify the location of the user of the smartphone. These aspects will now be described in more detail with reference toFIGS. 1A-2B.

As shown inFIG. 1A, at time t1, a magnetic field106is located near vehicle102. For purposes of discussion, person104is holding a device (not shown) in accordance with an aspect of the present invention. In this specific example, the device in accordance with an aspect of the present invention is embodied in a smartphone. In this specific example, the smartphone is able to detect magnetic field106.

As shown inFIG. 1B, at time t3, the opening of door108affects the magnetic field located near vehicle102, as shown by filed lines110. Again the smartphone is able to detect magnetic field shown by field lines110.

As shown inFIG. 1C, at time t3, the smartphone is not detecting the magnetic field outside of vehicle102.

In accordance with example aspects of the present invention, a smartphone carried by person104may identify vehicle102by aspects of magnetic field102or magnetic field108. Non-limiting detectable aspects of the magnetic fields include an instantaneous magnitude, an instantaneous field vector, a magnitude as a function over a period of time, a field vector as a function over a period of time and combinations thereof.

In accordance with other example aspects of the present invention, a smartphone carried by person104may identify vehicle102by aspects of a change of magnetic field102to magnetic field108. Non-limiting detectable aspects of the change magnetic fields include an instantaneous change in magnitude, an instantaneous change in field vector, a change in magnitude as a function over a period of time, a change in field vector as a function over a period of time and combinations thereof.

In addition to identifying an item, as discussed above with reference toFIGS. 1A-1C, aspects of the present invention may be used to identify a location.

As shown inFIG. 2A, at time t4, a person204is entering a house202. A magnetic field206is located near house202. For purposes of discussion, person204is holding a device (not shown) in accordance with an aspect of the present invention. In this specific example, the device in accordance with an aspect of the present invention is embodied in a smartphone. In this specific example, the smartphone is able to detect magnetic field106.

As shown inFIG. 2B, at time t5, person204is entering a building208. A magnetic field210is located near building208. Again the smartphone is able to detect magnetic field210.

In accordance with example aspects of the present invention, a smartphone carried by person104may identify whether person204is entering house202or building208by aspects of magnetic field206or magnetic field210.

A more detailed discussion of example working embodiment will now be discussed with additional reference toFIGS. 3-13.

FIG. 3illustrates an example method300of identifying an item or a location in accordance with aspects of the present invention.

Method300starts (S302) and an item or location is registered (S304). For example, if a person would like to be able to identify their vehicle, the vehicle would be registered based on a field associated with the vehicle, whereas if a person would like to be able to identify a location such as their place of work, then the location would be registered based on a field associated with the vehicle. A more detailed discussion of registration will now be provided with additional reference toFIGS. 4-11.

FIG. 4illustrates an example device402for identifying an item or a location in accordance with aspects of the present invention.

FIG. 4includes a device402, a database404, a field406and a network408. In this example embodiment, device402and database404are distinct elements. However, in some embodiments, device402and database404may be a unitary device as indicated by dotted line410.

Device402includes a field-detecting component412, an input component414, an accessing component416, a comparing component418, an identifying component420, a parameter-detecting component422, a communication component424, a verification component426and a controlling component428.

In this example, field-detecting component412, input component414, accessing component416, comparing component418, identifying component420, parameter-detecting component422, communication component424, verification component426and controlling component428are illustrated as individual devices. However, in some embodiments, at least two of field-detecting component412, input component414, accessing component416, comparing component418, identifying component420, parameter-detecting component422, communication component424, verification component426and controlling component428may be combined as a unitary device. Further, in some embodiments, at least one of field-detecting component412, input component414, accessing component416, comparing component418, identifying component420, parameter-detecting component422, communication component424, verification component426and controlling component428may be implemented as a computer having tangible computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such tangible computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. Non-limiting examples of tangible computer-readable media include physical storage and/or memory media such as RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. For information transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer may properly view the connection as a computer-readable medium. Thus, any such connection may be properly termed a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media.

Controlling component428is arranged to communicate with: field-detecting component412via a communication line430; input component414via a communication line432; accessing component416via a communication line434; comparing component418via a communication line436; identifying component420via a communication line438; parameter-detecting component422via a communication line440; communication component424via a communication line442; and verification component426via a communication line444. Controlling component428is operable to control each of field-detecting component412, input component414, accessing component416, comparing component418, identifying component420, parameter-detecting component422, communication component424and verification component426.

Field-detecting component412is additionally arranged to detect field406, to communicate with input component414via a communication line446, to communicate with comparing component418via a communication line448and to communicate with parameter-detecting component422via a communication line445. Field-detecting component412may be any known device or system that is operable to detect a field, non-limiting examples of which include an electric field, a magnetic field, and electro-magnetic field and combinations thereof. In some non-limiting example embodiments, field-detecting component412may detect the amplitude of a field at an instant of time. In some non-limiting example embodiments, field-detecting component412may detect a field vector at an instant of time. In some non-limiting example embodiments, field-detecting component412may detect the amplitude of a field as a function over a period of time. In some non-limiting example embodiments, field-detecting component412may detect a field vector as a function over a period of time. In some non-limiting example embodiments, field-detecting component412may detect a change in the amplitude of a field as a function over a period of time. In some non-limiting example embodiments, field-detecting component412may detect a change in a field vector as a function over a period of time.

Input component414is additionally arranged to communicate with database404via a communication line450and to communicate with verification component426via a communication line452. Input component414may be any known device or system that is operable to input data into database404. Non-limiting examples of input component414include a graphic user interface (GUI) having a user interactive touch screen or keypad.

Accessing component416is additionally arranged to communicate with database404via a communication line454and to communicate with comparing component418via a communication line456. Accessing component416may be any known device or system that access data from database404.

Comparing component418is additionally arranged to communicate with identifying component420via a communication line458. Comparing component418may be any known device or system that is operable to compare two inputs.

Parameter-detecting component422is additionally arranged to communicate with identifying component422via a communication line460. Parameter-detecting component422may be any known device or system that is operable to detect a parameter, non-limiting examples of which include velocity, acceleration, angular velocity, angular acceleration, geodetic position, sound, temperature, vibrations, pressure, biometrics, contents of surrounding atmosphere and combinations thereof. In some non-limiting example embodiments, parameter-detecting component422may detect the amplitude of a parameter at an instant of time. In some non-limiting example embodiments, parameter-detecting component422may detect a parameter vector at an instant of time. In some non-limiting example embodiments, parameter-detecting component422may detect the amplitude of a parameter as a function over a period of time. In some non-limiting example embodiments, parameter-detecting component422may detect a parameter vector as a function over a period of time. In some non-limiting example embodiments, parameter-detecting component422may detect a change in the amplitude of a parameter as a function over a period of time. In some non-limiting example embodiments, parameter-detecting component422may detect a change in a parameter vector as a function over a period of time.

Communication component424is additionally arranged to communicate with network408via a communication line462. Communication component424may be any known device or system that is operable to communicate with network408. Non-limiting examples of communication component include a wired and a wireless transmitter/receiver.

Verification component426may be any known device or system that is operable to provide a request for verification. Non-limiting examples of verification component426include a graphic user interface having a user interactive touch screen or keypad.

Communication lines430,432,434,436,438,440,442,444,445,446,448,450,452,454,456,458,460and462may be any known wired or wireless communication line.

Database404may be any known device or system that is operable to receive, store, organize and provide (upon a request) data, wherein the “database” refers to the data itself and supporting data structures. Non-limiting examples of database404include a memory hard-drive and a semiconductor memory.

Network408may be any known linkage of two or more communication devices. Non-limiting examples of database408include a wide-area network, a local-area network and the Internet.

For purposes of discussion, consider the example where a person is registering their vehicle. In some example embodiments, the vehicle may be registered based on an approach and entry into the vehicle as discussed above with reference toFIGS. 1A-C. In some example embodiments, the vehicle may be registered based upon fields detected while the person using the device is within the vehicle. For purposes of discussion, consider the example where a person is registering their vehicle while sitting in the vehicle. In some example embodiments, the registration may be performed based upon fields detected while the vehicle is in a specific mode of operation, non-limiting examples of which include starting up, driving forward, driving in reverse, stopped, accelerating, decelerating and combinations thereof. For purposes of discussion, consider the following example where a person is registering their vehicle based on the starting up of the vehicle. This example will now be described with additional reference toFIG. 5.

FIG. 5illustrates an example method500of registering an item or a location in accordance with aspects of the present invention.

Method500starts (S502) and a field is detected (S504). For example, returning toFIG. 4, field-detecting component412detects field406. For purposes of discussion, let field406be a magnetic field corresponding to the superposition of magnetic fields generated by all electronic and mechanical systems involved with the ignition of the vehicle. Some example detected field will now be described with greater detail with reference toFIGS. 6-8.

FIG. 6illustrates an example of measured magnetic fields associated with a specific vehicle in accordance with aspects of the present invention.

FIG. 6includes a graph602, a graph604, a graph606and a graph608, each of which share a common x-axis610in units of seconds. Graph602has a y-axis in units of μT and includes a function612. Graph604has a y-axis in units of μT and includes a function614. Graph606has a y-axis in units of μT and includes a function616. Graph608has a y-axis in units of μT and includes a function618.

Function612corresponds to the absolute value of the magnitude of a magnetic field vector (B) of the vehicle. Function614corresponds to the magnitude of B in a z-direction relative to field-detecting component412. Function616corresponds to the magnitude of B in a y-direction relative to field-detecting component412. Function618corresponds to the magnitude of B in an x-direction relative to field-detecting component412.

A sudden change in the magnetic field manifests as spike620in function612, as spike622in function614, as spike624in function616and as spike626in function618. This spike may be indicative of an event. For purposes of discussion, let this sudden change in the magnetic field correspond to the ignition of a particular vehicle. In this example therefore, the vehicle may have a signature based on functions612,614,616and618, having tell-tail spikes620,622,624and626, respectively. These functions may be easily distinguished from signatures based on different events, as will now be described with reference toFIG. 7.

FIG. 7illustrates another example of measured magnetic fields associated with a second vehicle in accordance with aspects of the present invention.

FIG. 7includes a graph702, a graph704, a graph706and a graph708, each of which share a common x-axis710in units of seconds. Graph702has a y-axis in units of μT and includes a function712. Graph704has a y-axis in units of μT and includes a function714. Graph706has a y-axis in units of μT and includes a function716. Graph708has a y-axis in units of μT and includes a function718.

Function712corresponds to the absolute value of the magnitude of a B of the second vehicle. Function714corresponds to the magnitude of B in a z-direction relative to field-detecting component412. Function716corresponds to the magnitude of B in a y-direction relative to field-detecting component412. Function718corresponds to the magnitude of B in an x-direction relative to field-detecting component412.

By comparing the overall magnitudes of the detected magnetic fields betweenFIG. 6andFIG. 7it is clear that the fields are associated with two different vehicles. However, there are additional differences between the detected fields worth noting. A change in the magnetic field ofFIG. 7manifests as a curve720in function712, as a curve722in function714, as a curve724in function716and as a spike726in function718. A commonality of each of these features is a rotation of the magnetic field, which may be indicative of an event. In this example, the relatively smooth transition of the magnetic field in more than one axis as shown in functions714and716, is indicative of a smooth movement of the detecting device within the detected magnetic field. For purposes of discussion, let this smooth change in the magnetic field correspond to the person, holding the device, entering a vehicle. Also noteworthy is a sudden change728in function718. This change which is detected in only one axis may be indicative of another event. For purposes of discussion, let this sudden change correspond to ignition of the vehicle. Therefore, in this example, the action of entering a specific vehicle and starting that specific vehicle may have a signature based on functions712,714,716and718.

FIG. 8illustrates another example of measured magnetic fields associated with a third vehicle in accordance with aspects of the present invention.

FIG. 8includes a graph802, a graph804, a graph806and a graph808, each of which share a common x-axis810in units of seconds. Graph802has a y-axis in units of μT and includes a function812. Graph804has a y-axis in units of μT and includes a function814. Graph806has a y-axis in units of μT and includes a function816. Graph808has a y-axis in units of μT and includes a function818.

Function812corresponds to the absolute value of the magnitude of a B of the third vehicle. Function814corresponds to the magnitude of B in a z-direction relative to field-detecting component412. Function816corresponds to the magnitude of B in a y-direction relative to field-detecting component412. Function818corresponds to the magnitude of B in an x-direction relative to field-detecting component412.

A sudden change in the magnetic field manifests as a curve820in function812, as a spike822in function814, as a spike824in function816and as a spike826in function818. A commonality of each of these features is a brief rotation of the magnetic field, which may be indicative of an event. In this example, the very brief rotation of the magnetic field in more than one axis, is indicative of a rotation the detecting device within the detected magnetic field. For purposes of discussion, let this quick change in the magnetic field correspond to the person, holding the device, entering a vehicle. Also noteworthy is a small bump828in function812, a small bump830in function814and a small bump832in function816. This small bump, which is detected in only two axes may be indicative of another event. For purposes of discussion, let this change correspond to ignition of the vehicle. Therefore, in this example, the action of entering a specific vehicle and starting that specific vehicle may have a signature based on functions812,814,816and818.

Returning toFIG. 5, once the field is detected (S504), a signature is generated (S506). In some embodiments, for example as shown inFIG. 4, field-detecting component412may generate a signature of the vehicle based any of functions612,614,616,618ofFIG. 6, and combinations thereof. In some embodiments, field-detecting component412may additionally process any of functions612,614,616,618and combinations thereof to generate such a signature. Non-limiting examples of further processes include averaging, adding, subtracting, and transforming any of functions612,614,616,618and combinations thereof.

Returning toFIG. 5, once the signature is generated (S506), the signature in input into memory (S508). For example, as shown inFIG. 4, field-detecting component412provides the signature to input component414via communication line446.

In an example embodiment, input component414includes a GUI that informs a user of device402that a signature has been generated. Input component414may additionally enable the user to input an association between and item or location and the generated signature. For example, input component414may display on a GUI a message such as “A signature was generated. To what item/location is the signature associated?” Input component414may then display an input prompt for the user to input, via the GUI, an item/location to be associated with the generated signature.

Input component414may then provide the signature, and the association to a specific item or location, to database404via communication line450.

As discussed above, in some embodiments, database404is part of device402, whereas in other embodiments, database404is separate from device402. Data input and retrieval from database404may be faster when database404part of device402, as opposed to cases where database404is distinct from device402. However, size may be a concern when designing device402, particularly when device402is intended to be a handheld device such as a smartphone. As such, device402may be much smaller when database404is distinct from device402, as opposed to cases where database404is part of device402.

Consider an example embodiment, where database404is part of device402. In such cases, input component414may enable a user to input signatures and the item/location associations, for a predetermined number of items/locations. In this manner, database404will only be used for device402.

Now consider an example embodiment, where database404is separate from device402. Further, let database404be much larger than the ease where database404is part of device402. Still further, let database404be accessible to other devices in accordance with aspects of the present invention. In such cases, input component414may enable a user to input signatures and the item/location associations, for a much larger predetermined number of items/locations. Further, in such cases, input component414may enable other users of similar devices to input signatures and the item/location associations, for even more items/locations.

An example embodiment may use the differentiating magnetic field properties between different vehicle types and makes to identify the different vehicle types and makes. Today's vehicles are fully equipped with electronic and mechanical actuators and switches, engine subsystems. All these subsystems are generating their own electromagnetic and magnetic fields and therefore will alter the overall three-dimensional properties and field strength fluctuations of the vehicle interior. Particularly the ignition of a vehicle generates a characteristic magnetic flux for every vehicle. Aspects of the present invention include a storing these field properties as signatures within database404through measurements in the near field within the vehicle interior for a reference group of make and models. As such, any user of a device may be able to identify a registered vehicle within database404. Thus, through previously stored signatures and additional measurements, the present invention enables a library of vehicular electromagnetic signatures. This library may be augmented with additional measurements describing the electromagnetic signatures of different vehicles. This will be described in greater detail later with reference toFIG. 13.

In the examples discussed above with respect toFIGS. 6-8, field-detecting component412is detecting magnetic fields as field vectors as functions over a period of time. The detected signals illustrated inFIGS. 6-8are easily distinguishable from one another. Accordingly, the vehicles associated therewith, respectively, may additionally be easily distinguishable from one another.

Returning toFIG. 5, method500may involve the detection of additional parameters to associate with an item or location. Specifically, additional aspects of the present invention are drawn to a system and method for determining a specific item and/or location by utilizing: 1) field properties within and/or near the specific item and or location; and 2) additionally detected parameters. In one non-limiting example embodiment, a smartphone is used to measure a magnetic field associated with a vehicle, and to measure velocity and/acceleration whether the user of the smartphone is in an identified vehicle.

FIG. 9illustrates an example of measured magnetic fields and of measured acceleration associated with the device being carried in accordance with aspects of the present invention.

FIG. 9includes graph602, graph604, graph606and graph608, in addition to a graph902, a graph904, a graph906, a graph908, a graph910and a graph912, each of which share a common x-axis914in units of seconds.FIG. 9additionally includes a line916. Graph902has a y-axis in units of m/s2and includes a function918. Graph904has a y-axis in units of m/s2and includes a function920. Graph906has a y-axis in units of m/s2and includes a function922. Graph908has a y-axis in units of degrees and includes a function924. Graph910has a y-axis in units of degrees and includes a function926. Graph912has a y-axis in units of degrees and includes a function928.

Function918corresponds to the acceleration in a z-direction relative to parameter-detecting component422. Function920corresponds to the acceleration in a y-direction relative to parameter-detecting component422. Function922corresponds to the acceleration in an x-direction relative to parameter-detecting component422. Function924corresponds to the angular acceleration in a yaw direction relative to parameter-detecting component422. Function926corresponds to the angular acceleration in a pitch direction relative to parameter-detecting component422. Function928corresponds to the angular acceleration in a roll direction relative to parameter-detecting component422.

As noted, function920, the acceleration in the y-direction, changes dramatically. This corresponds to the up and down motion of a person walking. Further, a spike930corresponds to motion of the person sitting into the vehicle. A second spike932corresponds to the large vibration coincident with starting of the vehicle. As discussed above, spikes620,622,624and626correspond to the detected magnetic field associated with ignition of the vehicle. Now these two separate parameters may be analyzed together to more clearly identify an event. In this example, a person is walking to, entering and starting a vehicle. As shown in each of functions918,920and922, the dramatic variations in detected acceleration in each axis (after the vehicle has been started as evidenced by the spikes in the detected magnetic fields of functions612,614,616and618) may be explained by way of the vibrations of the vehicle now that it is running. This is particularly telling by function918, or the acceleration in the z-axis (toward the vehicle). As the person is walking toward the vehicle, the constant walking velocity registers as no change in acceleration in this axis. However, after the vehicle is started, which shows as spike934in function918, acceleration changes in the z-axis as a result of the vehicle vibrating from the engine.

Functions924,926and928are shown here as further non-limiting examples of additional parameters that may be detected for use to identify a vehicle or location. In this example however, it should be noted that functions928includes a spike936. This spike in the “roll” rotational axis is indicative that the device is being rolled, which may correspond to the phone being in the user's hand when entering the vehicle. This further supports the notion that a person is entering a vehicle. This, evidence in conjunction with the magnetic and acceleration signatures may be used to accurately identify the vehicle.

The additionally detected parameter, in the above example ofFIG. 9, reduces the likelihood of false positive identification of a vehicle with only a magnetic signature. In accordance with aspects of the present invention, the use of additional parameter signatures may provide evidence to correctly identify a vehicle—or if the case may be—correctly identify a location.

In some embodiments, parameter-detecting component422may generate an output associated with the vehicle based any of functions918,920,922,924,926,928and combinations thereof. In some embodiments, parameter-detecting component422may additionally process any of functions918,920,922,924,926,928and combinations thereof to generate such an output. Non-limiting examples of further processes include averaging, adding, subtracting, and transforming any of functions918,920,922,924,926,928and combinations thereof. In any of these embodiments, field-detecting component412may then generate a signature of the vehicle based any of functions612,614,616,618and combinations thereof and based on the output generated by parameter-detecting component422.

FIG. 10illustrates another example of measured magnetic fields and of measured acceleration associated with a vehicle in accordance with aspects of the present invention.

FIG. 10includes graph702, graph704, graph706and graph708, in addition to a graph1002, a graph1004, a graph1006, a graph1.008, a graph1010and a graph1012, each of which share a common x-axis1014in units of seconds.FIG. 10additionally includes a line1016. Graph1002has a y-axis in units of m/s2and includes a function1018. Graph1004has a y-axis in units of m/s2and includes a function1020. Graph1006has a y-axis in units of m/s2and includes a function1022. Graph1008has a y-axis in units of degrees and includes a function1024. Graph1010has a y-axis in units of degrees and includes a function1026. Graph1012has a y-axis in units of degrees and includes a function1028.

Function1018corresponds to the acceleration in a z-direction relative to parameter-detecting component422. Function1020corresponds to the acceleration in a y-direction relative to parameter-detecting component422. Function1022corresponds to the acceleration in an x-direction relative to parameter-detecting component422. Function1024corresponds to the angular acceleration in a yaw direction relative to parameter-detecting component422. Function1026corresponds to the angular acceleration in a pitch direction relative to parameter-detecting component422. Function1028corresponds to the angular acceleration in a roll direction relative to parameter-detecting component422.

As discussed above with reference toFIGS. 6-7, by comparing the overall magnitudes of the detected magnetic fields betweenFIG. 9andFIG. 10, it is clear that the fields are associated with two different vehicles. However, there are additional differences between the detected parameters worth noting. As noted by functions1018,1020and1022, the acceleration changes very little until changes in the detected magnetic field as noted by720,724,728and732. At this point in time, as evidenced by variations1030,1032and1034, the acceleration-detecting component is “jostled” in all three axes. This corresponds to the relatively constant motion of a person walking, followed by the person entering the vehicle. Furthermore, as noted by function1024,1026and1028there is a generally constant yaw pitch and roll until the changes in the detected magnetic field as noted by720,724,728and732. At this point in time, as evidenced by double variations1036,1038and1040, the rotation-detecting component is “spun” in all three axes. These signatures, in conjunction with the relatively low acceleration as noted in functions1018,1020and1022, may be explained by the device being carried in a purse, for example. In such a case, being carried in a purse would buffer changes in acceleration, which is reflected in the relatively calm functions1018,1020and1022. When the person enters the vehicle and the purse is spun around and place in a seat, double variations1036,1038and1040may result. This is further evidenced by the lack of acceleration or movement detected in any of functions1018,1020,1022,1024,1026and1028after entering the vehicle.

In some embodiments, parameter-detecting component422may generate an output associated with the vehicle based any of functions1018,1020,1022,1024,1026,1028and combinations thereof. In some embodiments, parameter-detecting component422may additionally process any of functions1018,1020,1022,1024,1026,1028and combinations thereof to generate such an output. Non-limiting examples of further processes include averaging, adding, subtracting, and transforming any of functions1018,1020,1022,1024,1026,1028and combinations thereof. In any of these embodiments, field-detecting component412may then generate a signature of the vehicle based any of functions612,614,616,618and combinations thereof and based on the output generated by parameter-detecting component422.

FIG. 11illustrates another example of measured magnetic fields and of measured acceleration associated with a vehicle in accordance with aspects of the present invention.

FIG. 11includes graph802, graph804, graph806and graph808, in addition to a graph1102, a graph1104, a graph1106, a graph1108, a graph1110and a graph1112, each of which share a common x-axis1114in units of seconds.FIG. 11additionally includes a line1116. Graph1102has a y-axis in units of m/s2and includes a function1118. Graph1104has a y-axis in units of m/s2and includes a function1120. Graph1106has a y-axis in units of m/s2and includes a function1122. Graph1108has a y-axis in units of degrees and includes a function1124. Graph1110has a y-axis in units of degrees and includes a function1126. Graph1112has a y-axis in units of degrees and includes a function1128.

Function1118corresponds to the acceleration in a z-direction relative to parameter-detecting component422. Function1120corresponds to the acceleration in a y-direction relative to parameter-detecting component422. Function1122corresponds to the acceleration in an x-direction relative to parameter-detecting component422. Function1124corresponds to the angular acceleration in a yaw direction relative to parameter-detecting component422. Function1126corresponds to the angular acceleration in a pitch direction relative to parameter-detecting component422. Function1128corresponds to the angular acceleration in a roll direction relative to parameter-detecting component422.

By comparing the overall magnitudes of the detected magnetic fields betweenFIGS. 9-11, it is clear that the fields are associated with different vehicles. However, there are additional differences between the detected parameters worth noting. As noted by fluctuations1130,1132and1134of functions1118,1120and1122, respectively, the acceleration changes drastically in correspondence with changes in the detected magnetic field as noted by820,822,824and826. As discussed above, with reference toFIG. 8, this corresponds to entry into the vehicle. Further, as noted by spikes1136,1138and1140of functions1118,1120and1122, respectively, the acceleration changes drastically in correspondence with changes in the detected magnetic field as noted by828,830and832. As discussed above, with reference toFIG. 8, this ignition of the vehicle. At this point in time, as evidenced by spikes1136,1138and1140, the acceleration detecting component is “jostled” in all three axes.

Furthermore, as noted by function1124,1126and1128there is a generally constant yaw pitch and roll until the changes in the detected magnetic field as noted by820,822,824and826. At this point in time, as evidenced by changes1142,1144and1146, the rotation-detecting component is “spun” in all three axes as a result of the person entering the vehicle. Then the yaw pitch and roll remain constant for a period indicated by portions1148,1150and1152of functions1124,1126and1128, respectively. These signatures may be explained by the user setting the device down into one position after the entering the vehicle. At this point in time, as evidenced by changes1142,1144and1146, the rotation-detecting component is “spun” in all three axes as a result of the person entering the vehicle. Then the yaw pitch and roll again change as indicated by portions1154,1156and1158of functions1124,1126and1128, respectively. These signatures may be explained by the person moving the device.

In some embodiments, parameter-detecting component422may generate an output associated with the vehicle based any of functions1118,1120,1122,1124,1126,1128and combinations thereof. In some embodiments, parameter-detecting component422may additionally process any of functions1118,1120,1122,1124,1126,1128and combinations thereof to generate such an output. Non-limiting examples of further processes include averaging, adding, subtracting, and transforming any of functions1118,1120,1122,1124,1126,1128and combinations thereof. In any of these embodiments, field-detecting component412may then generate a signature of the vehicle based any of functions612,614,616,618and combinations thereof and based on the output generated by parameter-detecting component422.

In the examples discussed above with respect toFIGS. 9-11, just as with the examples discussed above with respect toFIGS. 6-8, the detected magnetic signals are easily distinguishable from one another. Accordingly, the vehicles associated therewith, respectively, may additionally be easily distinguishable from one another. However, in situations where the magnetic field signatures may be somewhat similar, it may be more difficult for a device in accordance with aspects of the present invention to distinguish vehicles—solely on the detected magnetic (or electric or electro-magnetic) fields. As such, the use of further distinguishing with at least a second detected parameter may help distinguish the vehicles.

In the examples discussed above with respect toFIGS. 9-11, parameter-detecting component422is detecting acceleration vectors as functions over a period of time. The detected acceleration signals illustrated inFIGS. 9-11are easily distinguishable from one another. Accordingly, even if such vehicles had similar magnetic signatures, the vehicles associated with the detected acceleration signals, respectively, may additionally be easily distinguishable from one another.

The above discussed examples ofFIGS. 9-11are merely provided for purposes of explanation and are not limiting. Clearly, any other type of detectable parameter may be used to additionally distinguish an item or location in accordance with aspects of the present invention.

It should be noted that the detected fields and parameters in the examples discussed above with reference toFIGS. 6-11are non-limiting examples. Each vehicle may have a distinct signature, just as each person may have a unique gait that will register a unique acceleration signature. An aspect of the present invention is the recording of a field signature, and in some cases an additional parameter signature, for future use to detect a vehicle or location.

In an example embodiment, field-detecting component412may detect magnetic field vectors associated with the approach and entry into vehicle102, for example as discussed above with reference toFIGS. 1A-C, whereas parameter-detecting component422may detect three dimensional acceleration associated with the gait of person104, the motion of person104opening door108and the motion of person104sitting in vehicle102. An overall signature may be generated based on the signatures generated from each of field-detecting component412and parameter-detecting component422.

In another example embodiment, field-detecting component412may detect magnetic field vectors associated the inside of vehicle102while it is operating, whereas parameter-detecting component422may detect ambient noise associated with the running engine and road noise associated with vehicle102while it is operating. An overall signature may be generated based on the signatures generated from each of field-detecting component412and parameter-detecting component422.

Returning toFIG. 3, after the item or location has been registered (S304), an item or location is detected (S306). For example, the next time the person approaches a vehicle, a device in accordance with aspects of the present invention would detect a field associated with the vehicle. Similarly, for example, the next time the person approaches a location, a device in accordance with aspects of the present invention would detect a field associated with the location. A more detailed discussion of registration will now be provided with additional reference toFIG. 12.

FIG. 12illustrates an example method1200of detecting an item or a location in accordance with aspects of the present invention.

Method1200starts (S1202) and a field is detected (S1204). This is the same as the field being detected (S504) as discussed above with reference to method500. For example, returning toFIG. 4, field-detecting component412detects a new field. For purposes of discussion, let the new field be a magnetic field corresponding to the superposition of magnetic fields generated by all electronic and mechanical systems involved with the ignition of a vehicle.

Returning toFIG. 12, once the field is detected (S1204), a signature is generated (S1206). This is similar to the signature being generated (S506) as discussed above with reference to method500. In some embodiments, for example as shown inFIG. 4, field-detecting component412may generate a signature of the vehicle based any of functions612,614,616,618ofFIG. 6, and combinations thereof. In some embodiments, field-detecting component412may additionally process any of functions612,614,616,618and combinations thereof to generate such a signature. Non-limiting examples of further processes include averaging, adding, subtracting, and transforming any of functions612,614,616,618and combinations thereof.

This second signature is provided to comparing component418via communication line448.

Returning toFIG. 3, after the item or location has been detected (S306), it is verified (S308). For example, a device in accordance with aspects of the present invention would determine whether the newly detected vehicle is the vehicle that was previously registered. Similarly, a device in accordance with aspects of the present invention would determine whether the newly detected location is the location that was previously registered. A more detailed discussion of registration will now be provided with additional reference toFIG. 13.

FIG. 13illustrates an example method1300of verifying an item or a location in accordance with aspects of the present invention.

Method1300starts (S1302) and the previously stored signature is accessed (S1304). For example, as shown inFIG. 4, access component416retrieves the previously-stored signature from database404via communication line454. Access component416then provides the retrieved, previously-stored signature to comparator418via communication line456.

Returning toFIG. 13, now that the previously stored signature has been accessed (S1304), the signatures are compared (S1306). For example, as shown inFIG. 4, comparator418compares the retrieved, previously stored signature as provided by access component416with the newly generated signature as provided by field-detecting component412.

Returning toFIG. 13, now that the signatures have been compared (S1306), the item/location may be identified (S1308). For example, as shown inFIG. 4, comparator418provides an output to identifying component420via communication line458. If the retrieved, previously stored signature as provided by access component416matches the newly generated signature as provided by field-detecting component412, then the newly detected item/location is the same item/location that was previously registered. In such a case, identifying component420may indicate that the newly detected item/location is the same item/location that was previously registered. If the retrieved, previously stored signature as provided by access component416does not match the newly generated signature as provided by field-detecting component412, then the newly detected item/location is not the same item/location that was previously registered. In such a case, identifying component420may indicate that the newly detected item/location is the same item/location that was previously registered.

Returning toFIG. 3, after the item or location has been verified, the data is updated (S310). For example, in some embodiments, as shown inFIG. 4, comparator418may determine that the previously stored signature as provided by access component416does not exactly match the newly generated signature as provided by field-detecting component412, but the difference between the previously stored signature as provided by access component416does not exactly match the newly generated signature as provided by field-detecting component412is within a predetermined acceptable limit. In such cases, identifying component420may indicate that the newly detected item/location is still the same item/location that was previously registered. Further, comparator418may provide the newly generated signature as provided by field-detecting component41.2to access component416via communication line456. Access component416may then provide the newly generated signature to database404via communication line454.

In this manner, database404may be “taught” to accept variations of previously registered signatures. In some embodiments, an average of recognized signatures may be stored for future use. In some embodiments, a plurality of each recognized signature may be stored for future use.

Returning toFIG. 3, device402waits to detect a new field (S306).

The example embodiments discussed above are drawn to identifying an item or location using fields associated therewith. Once identified, other functions may be available. For example, consider the situation wherein a device in accordance with aspects of the present invention is embodied in a smartphone. In such an example, once an item (e.g., a vehicle) or a location (e.g., a house) is identified, the smartphone may institute a suite of applications and turn off other applications. In a specific example embodiment, the identification of a vehicle may be used to place a smartphone in a “Vehicle Mode,” wherein the smartphone will operate in a particular manner because it is determined to be in a vehicle.

In accordance with aspects of the present invention discussed above, the sensors and functionalities of smartphones can be used to supplement or even replace the known vehicle-based techniques of vehicle telematics. More specifically, smartphone-to-smartphone (when both phones are in Vehicle Mode), smartphone-to-infrastructure and infrastructure-to-smartphone communications (again, when the smartphone is in Vehicle Mode) can provide drivers with a wide range of telematics services and features, while resulting in little or no additional cost to the vehicle driver (because she likely already has a smartphone) or the vehicle manufacturer (because it doesn't have to provide the purchaser of the vehicle with a smartphone and also doesn't have to embed costly vehicle telematics equipment in the vehicle). To be able to do so, however, the smartphone again has to be able to “know” that it is in Vehicle Mode and be able to determine in what vehicle it is. Ideally for various applications it is necessary to be able to determine if the smartphone is in the vehicle that is owned by the smartphone user. Aspects of the present invention enable a smartphone to know that it is in Vehicle Mode based on detected magnetic, electric, magneto-electric fields and combinations thereof.

Further in accordance with the present invention, a smartphone may utilize its magnetometer function to periodically measure the electromagnetic levels sensed at the smartphone's current location. The smartphone uses its processing capabilities to try to map the periodic electromagnetic levels sensed by the smartphone with the vehicular electromagnetic signatures stored in library. If the periodic electromagnetic levels sensed by the smartphone match any of the specific vehicle signatures stored in the library, then the processor of the smartphone may generate and/or otherwise output a signal indicating that the smartphone is located in the specific vehicle, which in turn will be used by the Vehicle Mode detection method to trigger certain functions.

The Vehicle Mode relevant sensor suite may be monitored at intervals depending on detected speed and location, for example, up to several times per second. The magneto metric sensor output may be monitored dependent on the accelerometer output as this will indicate a movement of the phone either within the vehicle environment or of the vehicle itself.