Patent Grant
10930289
In published applications 20110212717, 20110161076 and 20120208592, the present assignee detailed a variety of smartphone arrangements that respond in accordance with context. The present specification expands these teachings in certain respects.
In accordance with one aspect, systems and methods according to the present technology use a smartphone to sense audio and/or visual information, and provide same to a first classifier module. The first classifier module characterizes the input audio-visual stimuli by type (e.g., music, speech, silence, video imagery, natural scene, face, etc.). A second classifier module processes other context information (which may include the output from the first classifier module), such as of day, day of week, location, calendar data, clock alarm status, motion sensors, Facebook status, etc., and outputs data characterizing a device state type, or scenario. A control rule module then issues control signals to one or more content recognition modules in accordance with the outputs from the two classifier modules.
The control signals can simply enable or disable the different recognition modules. Additionally, if a recognition module is enabled, the control signals can establish the frequency, or schedule, or other parameter(s), by which the module performs its recognition functions.
Such arrangements conserve battery power, by not attempting operations that are unneeded or inappropriate to the context. Moreover, they aid other smartphone operations, since processing resources are not diverted to the idle recognition operations.
The foregoing and other features and advantages of the present technology will be more readily apparent from the following detailed description, which proceeds with reference to the accompanying drawings.
Referring to
One suitable smartphone is the Apple iPhone 4 device, which includes two cameras (one front-facing and one rear-facing), and two microphones. Another is the HTC EVO 3D, which includes stereo cameras (both rear-facing).
The audio-visual classifier module(s) 16 processes the data captured by the microphone(s) and/or camera(s), and classifies such audio-visual content by type.
As is familiar to artisans (and as explained in the Wikipedia article “Statistical classification”), classification is the problem of identifying to which of a set of categories (sub-populations) a new observation belongs. The individual observations may be analyzed into a set of quantifiable properties, known variously as variables, features, etc. These properties may be categorical (e.g. “A”, “B”, “AB” or “O”, for blood type), ordinal (e.g. “large”, “medium” or “small”), etc. A familiar (although sometimes difficult) classification problem is identifying email as spam or not-spam. An algorithm or procedure that implements classification is known as a classifier.
Classically, classification is performed based on a training set of data comprising observations (or instances) whose category membership is known. Classification, in this sense, is regarded as an instance of supervised machine learning, i.e., learning where a training set of correctly-identified observations is available. The corresponding unsupervised procedure is known as clustering (or cluster analysis), and involves grouping data into categories based on some measure of inherent similarity (e.g. the distance between instances, considered as vectors in a multi-dimensional vector space). For purposes of the present application, classification is regarded as including clustering.
One illustrative classifier module 16 is an audio classifier, which categorizes input stimulus as speech, music, background/indeterminate, or silence. For the first three, the module also classifies the volume of the audio, as loud, mid-level, or quiet.
Illustrative audio classification technologies are detailed in a later section.
A simple embodiment activates different content recognition modules, in accordance with the output of the audio classifier, as follows:
That is, if the audio classifier module classifies the sensed audio as “silent” or “quiet background,” all three of the detailed content recognition modules are controlled to “off.” If the sensed audio is classified as music, the system activates the Nielsen audio watermark detector, and the Gracenote fingerprint engine, but leaves the Nuance speech recognition engine off.
If the sensed audio is classified as speech, the audio watermark detector is activated, as is the speech recognition engine, but no fingerprint calculations are performed.
If the audio classifier identifies a loud or mid-level acoustic background, but is unable to further classify its type, the audio watermark detector, the fingerprint engine, and the speech recognition engine are all activated.
It will thus be recognized that different combinations of recognition technologies are applied to the input content, based on the type of content indicated by the content classifier.
(The detailed recognition modules are all familiar to artisans. A brief review follows: Nielsen encodes nearly all of the television broadcasts in the United States with an audio watermark that encodes broadcast source and time data, to assist Nielsen in identifying programs for rating surveys, etc. Nielsen maintains a database that correlates source/time data decoded from broadcasts, with program names and other identifiers. Such watermark technology is detailed, e.g., in U.S. Pat. Nos. 6,968,564 and 7,006,555. Gracenote uses audio fingerprinting technology to enable music recognition. Characteristic feature data is derived from audio by a fingerprint engine, and used to query a database containing reference fingerprint data. If a match is found, associated song identification data is returned from the database. Gracenote uses fingerprint technology originally developed by Philips, detailed, e.g., in patent documents 20060075237 and 20060041753. Nuance offers popular speech recognition technology. Its SpeechMagic SDK and/or NaturallySpeaking SDK can be incorporated into embodiments of the present technology to provide speech recognition capability.)
Second classifier module 18 outputs device state type data, or scenario identification data, in accordance with context information. This context information may include the classification of the audio and/or visual environment (i.e., by the audio-visual classifier module(s) 16, as shown by the dashed line in
This other context information can include, but is not limited to, time of day, day of week, location, calendar data, clock alarm status, motion and orientation sensor data, social network information (e.g., from Facebook), etc.
Consider Table II, which expands the Table I information to include certain device state types as determined by the second classifier module (i.e., “away from office after work hours” and “at office during work hours”):
It will be recognized that the first five rows of Table II are identical to Table I. They detail how the different modules are controlled when the user is away from the office, after work hours, given the noted audio environments.
The final set of rows is different. These correspond to the device state type of being at the user's office, during work hours. As can be seen, only the speech recognition engine is ever activated in this context (i.e., when speech or loud background audio is sensed); the other modules are left idle regardless of the audio environment.
To determine whether the user is “at office during work hours,” or “away from office after work hours,” the second classifier module 18 uses inputs such as time of day data and GPS data, in connection with reference data. This reference data establishes—for the particular smartphone user—the times of day that should be classified as work hours (e.g., 8 am-5 pm, Monday-Friday), and the location that should be classified as the office location (e.g., 45.4518° lat, −122.7932° long, +/−0.0012 degrees).
It will be recognized that this arrangement conserves battery power, by not attempting to recognize songs or television programs while the user is at work. It also aids other tasks the smartphone may be instructed to perform at work, since processing resources are not diverted to the idle recognition operations.
More typically, the smartphone considers other factors beyond those of this simple example. Table IIIA shows a more detailed scenario, as classified by the second classifier module 18:
This confluence of circumstances is classed by the second classifier module as “Scenario 1.” It corresponds to the scenario in which the user is probably asleep (it is before 6:30 am on a weekday, and the alarm is set for 6:30; the smartphone is stationary in a quiet, dark environment). The control rules 20 associated with Scenario 1 cause all of the content recognition modules to be inactive.
The following tables show other scenarios, as classified by the second classifier module:
Scenario 2 (Table IIIB) corresponds to the user after waking up and before leaving home. The rules include instructions appropriate to this interval—while the user may be watching a morning news program on television, listening to the radio, or talking with a spouse. In particular, the Nielsen watermark detector is active, to allow the user to link to additional web content about something discussed on the television. The fingerprint engine is also active, so that the user might identify an appealing song that airs on the radio. Speech recognition may also be enabled, so that the spouse's verbal instructions to pick up ketchup, grapes, tin foil and postage stamps on the way home are transcribed for later reference.
The user's smartphone also includes various visual content recognition capabilities, including facial recognition. The control rules specify that, in Scenario 2, facial recognition is disabled—as the user isn't expected to need prompting to recall faces of anyone encountered at home this early.
Scenario 3 (Table IIIC) corresponds to the user's drive to work. No television audio is expected in this environment, so the Nielsen watermark detector is disabled. Song recognition and transcription of news from talk radio, however, may be helpful, so the fingerprint and speech recognition engines are enabled. Again, facial recognition is disabled.
A different user may take the bus to work, instead of drive a car. Second scenario control rules for this user may be different. Without a car radio, song recognition is unneeded, so the fingerprint engine is disabled. However, the user sometimes overhears amusing conversations on the bus, so speech recognition is enabled so that any humorous dialog may be shared with work-mates. Occasionally, the user sees someone she should recognize on the bus—a parent of a child's soccer teammate, for example—but be unable to recall the name in this different environment. To prepare for this eventuality, the smartphone's facial recognition capability is loaded into memory and ready for operation, but does not process a frame of camera imagery until signaled by the user. (The signal may comprise the user holding the phone in a predetermined pose and saying the word “who.”)
The confluence of sensor information detailed in Table IIID—which the second classifier module identifies as Scenario 4—corresponds to the circumstance of the user's morning work at her desk. The smartphone is apparently lying face-up on a surface in the quiet work environment. The corresponding control rules specify that all recognition modules are disabled. However, if the audio classifier indicates a change in audio environment—to mid-level or loud background sound, or speech, the rules cause the phone to enable the speech recognition module. This provides the user with a transcribed record of any request or information she is given, or any instruction she issues, so that it may be referred-to later.
Speech recognition can raise privacy concerns in some situations, including a work setting. Accordingly, the control rules cause the speech recognition module to issue an audible “beep” every thirty seconds when activated at work, to alert others that a recording is being made. In contrast, no “beep” alert is issued in the previously-discussed scenarios, because no recording of private third party speech is normally expected at home or in the car, and there is likely no expectation of privacy for speech overheard in a bus.
Another datum of context that is processed by the illustrated second classifier module 18 is the number and identity of people nearby. “Nearby” may be within the range of a Bluetooth signal issued by a person's cell phone—typically 30 feet or less. Relative distance within this range can be assessed by strength of the Bluetooth signal, with a strong signal indicating, e.g., location within ten feet or less (i.e., “close”). Identity can be discerned—at least for familiar people—by reference to Bluetooth IDs for their known devices. Bluetooth IDs for devices owned by the user, family members, workmates, and other acquaintances, may be stored with the control rules to help discriminate well known persons from others.
Returning briefly to the previous scenarios, the rules can provide that speech recognition—if enabled—is performed without alert beeps, if the user is apparently solitary (i.e., no strong Bluetooth signals sensed, or only transitory signals—such as from strangers in nearby vehicles), or if the user is in the presence only of family members. However, if an unfamiliar strong Bluetooth signal is sensed when speech recognition is enabled, the system can instruct issuance of periodic alert beeps.
(If the user's phone issues speech recognition alert beeps at home, because the user's child has a new device with an unrecognized Bluetooth identifier, the user's phone can present a user interface screen allowing the user to store this previously-unrecognized Bluetooth identifier. This UI allows the user to specify the identifier as corresponding to a family member, or to associate more particular identification information with the identifier (e.g., name and/or relationship). By such arrangement, beeping when not warranted is readily curtailed, and avoided when such circumstance recurs in the future.)
Scenario 5—a work meeting—is contextually similar to Scenario 4, except the audio classifier reports mid-level background audio, and the phone's location is in a meeting room. The speech recognition module is enabled, but corporate data retention policies require that transcripts of meetings be maintained only on corporate servers, so that they can be deleted after a retention period (e.g., 12 months) has elapsed. The control rules module 20 complies with this corporate policy, and immediately transmits the transcribed speech data to a corporate transcriptions database for storage—keeping no copy. Alert beeps are issued as a courtesy reminder of the recording. However, since all the close-by persons are recognized to be “friends” (i.e., their Bluetooth identifiers correspond to known workmates), the rules cause the phone to beep only once every five minutes, instead of once every 30 seconds, to reduce the beeps' intrusiveness. (Additionally or alternatively, the volume of the beeps can be reduced, based on a degree of social relationship between the user and the other sensed individual(s)—so that the beeps are louder when recording someone who is only distantly or not at all socially related to the user.)
Rules for face recognition in scenario 5 can vary depending on whether people sensed to be close-by are recognized by the user's phone. If all are recognized, the facial recognition module is not activated. However, if one or more close-by persons are not in the user's just-noted “friends” list (or within some more distant degree of relationship in a social network), then facial recognition is enabled as before—in an on-demand (rather than free-running) mode. (Alternatively, a different arrangement can be employed, e.g., with facial recognition activated if one or persons who have a certain type of social network linkage to the user, or absence thereof, are sensed to be present.)
Scenario 6 finds the user in a subway, during the noon hour. The rules may be like those noted above for the bus commute. However, radio reception underground is poor. Accordingly, any facial recognition operation consults only facial eigenface reference data stored on the phone—rather than consulting the user's larger collection of Facebook or Picasa facial data, which are stored on cloud servers.
Scenario 7 corresponds to a Friday evening birthday party. Lots of unfamiliar people are present, so the rules launch the facial recognition module in free-running mode—providing the user with the names of every recognized face within the field-of-view of any non-dark camera. This module relies on the user's Facebook and Picasa facial reference data stored in the cloud, as well as such data maintained in Facebook accounts of the user's Facebook friends. Speech recognition is disabled. Audio fingerprinting is enabled and—due to the party context—the phone has downloaded reference fingerprints for all the songs on Billboard's primary song lists (Hot 100, Billboard 200, and Hot 100 Airplay). Having this reference data cached on the phone allows much quicker operation of the song recognition application—at least for these 200+ songs.
Additional Information
Fingerprint computation, watermark detection, and speech/facial recognition are computationally relatively expensive (“computationally heavy”). So are many classification tasks (e.g., speech/music classification). It is desirable to prevent such processes from running at a 100% duty cycle.
One approach is to let the user decide when to run one or more heavy modules—with help from the output of one or more computationally light detectors. Adding additional steps to assess the signal quality prior to running one or more heavy detectors is another approach.
Reducing the duty cycle of a heavy module implies the possibility of missed detection, so the user should have some control over how much compromise she/he wants.
Consider a simple classifier (e.g., a quietness classifier), which simply checks the ambient audio energy within a one-second long audio frame, and compares this value to a pre-defined threshold. Such module may indicate that there is a sudden change in the environment from a quiet state. Rules may call for activation of one or more heavy classifiers to determine whether the new audio environment is music or speech. In this case, the system may present a display screen with a “Confirm to Proceed” button that the user taps to undertake the classification. (There can also be an “Ignore” button. The system can have a default behavior, e.g., “Ignore,” if the user makes no selection within a pre-defined interval, such as ten seconds.)
The user response to such prompts can be logged, and associated with different context information (including the sensitivity of the quietness classifier). Over time, this stored history data can be used to predict the circumstances in which the user instructs the heavy classifier to proceed. Action can then be taken based on such historical precedent, rather than always resorting to a user tap.
That is, the system can be self-learning, based on user interaction. For example, when a quietness classifier detects a change in loudness of amount “A,” it asks for the user's permission to enable a heavier classifier (for example, music versus speech classifier) or detector (e.g., watermark detector). If the user agrees, then this “A” level of loudness change is evidently at least sometimes of interest to the user. However, if over time, it becomes evident that the user uniformly refuses to activate the heavy classifier when the loudness changes by amount “A,” then the classifier can reset its threshold accordingly, and not ask the user for permission to activate the heavy module unless the loudness increases by “B” (where B>A). The quietness classifier thus learns to be less sensitive.
Conversely, if the user manually launches the heavy module when the quietness classifier has sensed a change in loudness too small to trigger a UI prompt to the user, this indicates that the threshold used by the quietness classifier is too high, and should be changed to a lower level. The quietness classifier thus learns to be more sensitive.
Shown in dashed lines are additional aspects of the method that may be included. For example, the user's response—entered through the UI—is logged and added to a user history, to guide future automated responses by the system. The current context is also stored in such history, as provided by a context classifier. In some cases, the user history, alone, may provide instructions as to how to respond in a given situation—without the need to ask the user.
(It will be recognized that instead of asking the user whether to invoke the complex processing module when the context changes, the system can instead ask whether the complex processing module should not be invoked. In this case the user's inaction results in the processing module being invoked.)
Another approach is to employ an additional classifier, to decide whether the current audio samples have a quality that merits further classification (i.e., with a heavy classifier). If the quality is judged to be insufficient, the heavy classifier is not activated (or is de-activated).
Information-bearing signals—such as speech and music—are commonly characterized by temporal variation, at least in spectral frequency content, and also generally in amplitude, when analyzed over brief time windows (e.g., 0.5 to 3 seconds). An additional classifier can listen for audio signals that are relatively uniform in spectral frequency content, and/or that are relatively uniform in average amplitude, over such a window interval. If such a classifier detects such a signal, and the amplitude of such signal is stronger by a threshold amount (e.g., 3 dB) than a long-term average amplitude of the sensed audio environment (e.g., over a previous interval of 3-30 seconds), the signal may be regarded as interfering noise that unacceptably impairs the signal-to-noise ratio of the desired audio. In response to such a determination, the system discontinues heavy module processing until the interfering signal ceases.
To cite an extreme case, consider a user riding a bus that passes a construction site where a loud jack-hammer is being used. The just-discussed classifier detects the interval during which the jack-hammer is operated, and interrupts heavy audio processing during such period.
Such classifier may similarly trigger when a loud train passes, or an air compressor operates, or even when a telephone rings—causing the system to change from its normal operation in these circumstances.
Another simple classifier relies on principles noted in Lu et al, SpeakerSense: Energy Efficient Unobtrusive Speaker Identification on Mobile Phones, Pervasive Computing Conf., 2011. Lu et al use a combination of signal energy (RMS) and zero crossing rate (ZCR) to distinguish human speech from other audio. While Lu et al use these parameters to identify speech, they can also be used to identify information-bearing signals more generally. (Or, stated otherwise, to flag audio passages that are likely lacking information, so that heavy processing modules can be disabled.)
As a further alternative, since the additional classifier works after the detection of “sound change,” audio samples prior to the “sound change” can be used as an approximation of the background noise, and the audio sample after the “sound change” can be used as the background noise plus the useful signal. This gives a crude signal-to-noise ratio. The additional classifier can keep heavy modules in an idle state until this ratio exceeds a threshold value (e.g., 10 dB).
Still another additional classifier—to indicate the likely absence of an information-bearing signal—simply looks at a ratio of frequency components. Generally, the presence of high frequency signal components above a threshold amplitude is an indication of audio information. A ratio of energy in high frequency components (e.g., above 2 KHz) compared to energy in low frequency components (e.g., below 500 Hz) can serve as another simple signal-to-noise ratio. If the classifier finds that such ratio is below 3 or 10 dB, it can suspend operation of heavy modules.
Such an arrangement is shown in
Also shown in
(While the
The above-discussed principles are likewise applicable to sensing visual information. Visual image classifiers (e.g., facial recognition systems) generally work on imagery having significant spatial variation in luminance (contrast/intensity) and/or hue (color/chrominance). If frames of imagery appear that are lacking in such variations, any heavy image processing module that would otherwise be operating should suspend its operation.
Accordingly, a classifier can look for a series of image frames characterized by luminance or hue variation below a threshold, and interrupt heavy visual processing when such scene is detected. Thus, for example, heavy visual processes are suspended when the user points a camera to a blank wall, or to the floor. (Such action may also be taken based on smartphone orientation, e.g., with facial recognition only operative when the smartphone is oriented with its camera axis within 20 degrees of horizontal. Other threshold values can, of course, be used.)
Similarly, facial recognition analysis is likely wasted effort if the frame is out of focus. Accordingly, a simple classifier can examine frame focus (e.g., by known metrics, such as high frequency content and contrast measures, or by a camera shake metric—provided by the phone's motion sensors), and disable facial recognition if the frame is likely blurred.
Facial recognition can also be disabled if the subject is too distant to likely allow a correct identification. Thus, for example, if the phone's autofocus system indicates a focal distance of ten meters or more, facial recognition needn't be engaged.
While Bluetooth is one way to sense other individuals nearby, there are others.
One technique relies on the smartphone's calendar app. When the user's calendar, and phone clock, indicate the user is at a meeting, other participants in the user's proximity can be identified from the meeting participant data in the calendar app.
Another approach relies on location data, which is short range-broadcast from the phone (or published from the phone to a common site), and used to indicate co-location with other phones. The location data can be derived from known techniques, including GPS, WiFi node identification, etc.
A related approach relies on acoustic emitters that introduce subtle or inaudible background audio signals into an environment, which can be indicative of location. Software in a microphone-equipped device (e.g., a smartphone app) can listen for such signal (e.g., above or below a range of human hearing, such as above 15-20 KHz), and broadcast or publish—to a public site—information about the sensed signal. The published information can include information conveyed by the sensed signal, e.g., identifying the emitting device or its owner, the device location and/or other context, etc.). The published information can also include information associated with the receiving device (e.g., identifying the device or its owner, the device location and/or other context, etc.). This allows a group of phones near each emitter to be identified. (Related technology is employed by the Shopkick service, and is detailed in patent publication US20110029370.)
Bluetooth is presently preferred because—in addition to identifying nearby people, it also provides a communication channel with nearby phones. This enables the phones to collaborate in various tasks, including speech recognition, music fingerprinting, facial recognition, etc. For example, plural phones can exchange information about their respective battery states and/or other on-going processing tasks. An algorithm is then employed to select one phone to perform a particular task (e.g., the one with the most battery life remaining is selected to perform watermark decoding or facial recognition). This phone then transmits the results of its task—or related information based thereon—to the other phones (by Bluetooth or otherwise).
Another form of collaboration is 3D image modeling, based on camera data from two or more different phones, each with a different view of a subject. A particular application is facial recognition, where two or more different views of a person allow a 3D facial model to be generated. Facial recognition can then be based on the 3D model information—yielding a more certain identification than 2D facial recognition affords.
Yet another form of collaboration is for multiple smartphones to undertake the same task, and then share results. Different phone processes may yield results with different confidence measures, in which case the result with the highest confidence measure can be used by all phones. (Such processing can be done by processes in the cloud, instead of using the phones' own processors.)
In some applications, a phone processes ambient audio/visual stimulus in connection with phone-specific information, allowing different phones to provide different results. For example, the face of an unknown person may be identified in a Facebook account accessible to one phone, but not to others. Thus, one phone may be able to complete a task that others cannot. (Other phone-specific information includes history, contacts, computing context, user context, physical context, etc. See, e.g., published application 20110161076 and application Ser. No. 13/174,258, filed Jun. 30, 2011 (now U.S. Pat. No. 8,831,279). For image processing, different phones may have better or worse views of the subject.)
Relatedly, collaborating phones can send the audio/imagery they captured to one or more other phones for processing. For example, a phone having Facebook access to useful facial recognition data may not be the phone with the best view of a person to be identified. If plural phones each captures data, and shares such data (or information based thereon, e.g., eigenface data) to the other phones, results may be achieved that are better than any phone—by itself—could manage.
Of course, devices may communicate other than by Bluetooth. NFC and WiFi are two such alternatives.
Bluetooth was also noted as a technique for determining that a user is in a vehicle. Again, other arrangements can be employed.
One is GPS. Even a sporadically-executing GPS module (e.g., once every minute) can collect enough trajectory information to determine whether a user is moving in a manner consistent with vehicular travel. For example, GPS can establish that the user is following established roads, and is moving at speeds above that associated with walking or biking. (When disambiguating biking from motorized vehicle travel, terrain elevation can be considered. If the terrain is generally flat, or if the traveler is going uphill, a sustained speed of more than 20 mph may distinguish motorized transport from bicycling. However, if the user is following a road down a steep downhill incline, then a sustained speed of more than 35 mph may be used to establish motorized travel with certainty.)
If two or more phones report, e.g., by a shared short-range context broadcast, that they are each following the same geo-location-track, at the same speed, then the users of the two phones can conclude that they are traveling on the same conveyance—whether car, bus, bike, etc.
Such conclusion can similarly be made without GPS, e.g., if two or more phones report similar data from their 3D accelerometers, gyroscopes, and/or magnetometers Still further, co-conveyance of multiple users can likewise be established if two or more phones capture the same audio (e.g., as indicated by a correlation metric exceeding a threshold value, e.g., 0.9), and share this information with other nearby devices.
Again, the cloud can serve as a recipient for such information reported by the smartphones, can make determinations, e.g., about correlation between devices.
Reference was made to a short-range context broadcast. This can be effected by phones broadcasting their sensed context information (which may include captured audio) by Bluetooth to nearby devices. The information shared may be of such a character (e.g., acceleration, captured audio) that privacy concerns do not arise—given the short range of transmission involved.
While this specification focuses on audio applications, and also considers facial recognition, there are unlimited classes that might be recognized and acted-on. A few other visual classes include optical character recognition (OCR) and barcode decoding.
The presence of multiple cameras on a smartphone enables other arrangements. For example, as noted in application Ser. No. 13/212,119, filed Aug. 17, 2011 (now U.S. Pat. No. 8,564,684), a user-facing camera can be used to assess emotions of a user (or user response to information presented on the smartphone screen), and tailor operation of the phone—including use of the other camera—accordingly.
A user-facing camera can also detect the user's eye position. Operation of the phone can thereby be controlled. For example, instead of switching between “portrait” and “landscape” display modes based on the phone's position sensors, this screen display mode can be controlled based on the orientation of the user's eyes. Thus, if the user is lying in bed on her side (i.e., with a line between the pupils extending vertically), and the phone is spatially oriented in a landscape direction (with its long axis extending horizontally, parallel to the axis of the user's body), the phone can operate its display in the “portrait” mode. If the user turns the phone ninety degrees (i.e., so that its long axis is parallel to the axis between the users' eyes), the phone switches its display mode to “landscape.”
Similarly, if the user is lying on her back, and holding the phone overhead, the screen mode switches to follow the relative orientation of the axis between the user's eyes, relative to the screen axis. (That is, if the long axis of the phone is parallel with the axis between the user's eyes, landscape mode is used; and vice versa.)
If the phone is equipped with stereo cameras (i.e., two cameras with fields of view that overlap), the two views can be used for distance determination to any point in the frame (i.e., range finding). For certain visual detection tasks (e.g., watermark and barcode decoding), the distance information can be used by the phone processor to guide the user to move the phone closer to, or further from, the intended subject in order to achieve best results.
A phone may seek to identify an audio scene by reference to sensed audio. For example, a meeting room scene may be acoustically characterized by a quiet background, with distinguishable human speech, and with occasional sound source transition (different people speaking alternatively). A home scene with the user and her husband may be acoustically characterized by a mid-level background audio (perhaps music or television), and by two different voices speaking alternately. A crowded convention center may be characterized by a high-level background sound, with many indistinguishable human voices, and occasionally the user's voice or another.
Once an audio scene has been identified, two or more smartphones can act and cooperate in different ways. For example, if the scene has been identified as a meeting, the user's phone can automatically check-in for the room, indicating that the meeting room is occupied. (Calendar programs are often used for this, but impromptu meetings may occupy rooms without advance scheduling. The smartphone can enter the meeting on the calendar—booking the room against competing reservations—after the meeting has started.)
The phone may communicate with a laptop or other device controlling a Powerpoint slide presentation, to learn the number of slides in the deck being reviewed, and the slide currently being displayed. The laptop or the phone can compute how quickly the slides are being advanced, and extrapolate when the meeting will conclude. (E.g., if a deck has 30 slides, and it has taken 20 minutes to get through 15 slides, a processor can figure it will take a further 20 minutes to get through the final 15 slides. Adding 10 minutes at the end for a wrap-up discussion, it can figure that the meeting will conclude in 30 minutes.) This information can be shared with participants, or posted to the calendar app to indicate when the room might become available.
If the auditory scene indicates a home setting in the presence of a spouse, the two phones can exchange domestic information (e.g., shopping list information, social calendar data, bills to be paid soon, etc.).
In a crowded convention center scene, a phone can initiate automatic electronic business card exchange (e.g., v-card), if it senses the user having a chat with another person, and the phone does not already have contact information for the other person (e.g., as identified by Bluetooth-indicated cell phone number, or otherwise).
In the convention scene, the user's phone might also check the public calendars of people with whom the user talks, to identify those with similar transportation requirements (e.g., a person whose flight departs from the same airport as the user's departing flight, with a flight time within 30 minutes of the user's flight). Such information can then be brought to the attention of the user, e.g., with an audible or tactile alert.
Reference was made to performing certain operations in the cloud. Tasks can be referred to the cloud based on various factors. An example is use cloud processing for “easy to transmit” data (i.e., small size) and “hard to calculate” tasks (i.e., computationally complex). Cloud processing is often best suited for tasks that don't require extensive local knowledge (e.g., device history and other information stored on the device).
Consider a traveler flying to San Francisco for a conference, who needs to commute to a conference center hotel downtown. On landing at the airport, the user's phone sends the address of the downtown hotel/conference center to a cloud server. The cloud server has knowledge of real-time traffic information, construction delays, etc. The server calculates the optimal route under various constraints, e.g., shortest-time route, shortest-distance route, most cost-effective route, etc. If the user arrives at the airport only 20 minutes before the conference begins, the phone suggests taking a taxi (perhaps suggesting sharing a taxi with others that it senses have the same destination—perhaps others who also have a third-party trustworthiness score exceeding “good”). In contrast, if the user arrives a day ahead of the conference, the phone suggests taking BART—provided the user traveled with one piece of checked baggage or less (determined by reference to airline check-in data stored on the smartphone). Such route selection task is an example of “little data, big computation.”
In addition to audio and imagery from its own sensors, the smartphone can rely on audio and imagery collected by public sensors, such as surveillance cameras in a parking garage, mall, convention center, or a home security system. This information can be part of the “big computation” provided by cloud processing. Or the data can be processed exclusively by the smartphone, such as helping the user find where she parked her yellow Nissan Leaf automobile in a crowded parking lot.
While the specification has focused on analysis of audio and image data, the same principles can be applied to other data types. One is haptic data. Another is gas and chemical analysis. Related is olfactory information. (Smell sensors can be used by smartphones as a diagnostic aid in medicine, e.g., detecting biomarkers that correlate to lung cancer in a user's breath.)
Naturally, information from the user's social networking accounts (Facebook, Twitter, Foursquare, Shopkick, LinkedIn, etc.) can be used as input to the arrangements detailed herein (e.g., as context information). Likewise with public information from the accounts of people that the user encounters, e.g., at work, home, conferences, etc. Moreover, information output from the detailed arrangements can be posted automatically to the user's social networking account(s).
It will be recognized that facial recognition has a number of uses. One, noted above, is as a memory aid—prompting the user with a name of an acquaintance. Another is for user identification and/or authorization. For example, the user's smartphone may broadcast certain private information only if it recognizes a nearby person as a friend (e.g., by reference to the user's list of Friends on Facebook). Facial recognition can also be used to tag images of a person with the person's name and other information.
In some embodiments a user's smartphone broadcasts one or more high quality facial portraits of the user, or associated eigenface data. Another smartphone user can snap a poor picture of the user. That smartphone compares the snapped image with high quality image data (or eigenface data) received over Bluetooth from the user, and can confirm that the poor picture and the received image data correspond to the same individual. The other smartphone then uses the received image data in lieu of the poor picture, e.g., for facial recognition, or to illustrate a Contacts list, or for any other purpose where the user's photo might be employed.
Note that that there is no classifier output for “image.” Everything is a candidate. Thus, the image watermark decoding module, and the image fingerprint module, are activated based on certain combinations of outputs from the classifier(s) (e.g., when none or all of the three types of classified images is identified).
Note, too, how no image recognition processing is undertaken when the system detects a dark scene, or the system detects that the imagery was captured under conditions of motion (“jerk”) that make image quality dubious.
Published application 20120208592 further details technology useful with the arrangements of
More on Audio Classification
Audio classification problem is often termed as content-based classification/retrieval, or audio segmentation. There are two basic issues in this work: feature selection and classifier selection.
One of the early works in this field was published in 1996 by Wold et al. [5]. He used various perceptual features (loudness, pitch, brightness, bandwidth and harmonicity) and the nearest neighbor classifier. In [6], Foote used the 13 Mel-Frequency Cepstral Coefficients (MFCCs) as audio features, and a vector quantization method for classification. In [7], Zhang and Kuo used hidden Markov models to characterize audio segments, and a hierarchical classifier is used for two-step classification. Scheirer, in [12], evaluated the properties of 13 features for classify speech and music, achieving very high accuracy (around 95% accuracy, but only for music/speech classification), especially integrating long segments of sound (2.4 seconds). Liu et al. [8] argued that “audio understanding can be based on features in three layers: low-level acoustic characteristics, intermediate-level audio signatures associated with different sounding objects, and high level semantic models of audio in different scene classes”; and “classification based on these low-level features alone may not be accurate, but the error can be addressed in a higher layer by examining the structure underlying a sequence of continuous audio clips.”
Meanwhile, in terms of calculating low-level features, [6,8] mentioned explicitly to firstly divide the audio samples into 1-second long clips and then further divide each clip into 40 non-overlapping 25-milisecond long sub-clips. The low-level features are calculated on each 25-millisecond long sub-clip and then merged through the 40 sub-clips to represent the 1-second long clip. The classification is based on the 1-second long clips. (In a 25-milisecond period, the sound signal shows a stationary property, whereas in a 1-second period, the sound signal exhibits characteristics corresponding to the categories that we want to distinguish. In these early references, and also in later years, these categories include silence, music, speech, environment sound, speech with environment sound, etc.
In the 2000s, Microsoft Research Asia worked actively on audio classification, as shown in [9,10]. Lu in [9] used low-level audio features, including 8 order MFCCs and several other perceptual features, as well as kernel SVM (support vector machine) as the classifier in a cascaded scheme. The work in [10] also included perceptual features and used different classifiers in a cascaded classification scheme, including k-NN, LSP VQ and rule based methods (for smoothing). In this paper they used dynamic feature sets (use different features) for classifying different classes.
More recently, work on audio classification has increased. Some people work on exploiting new audio features, like [2,3,4,17], or new classifiers [13]. Others work on high level classification framework beyond the low level features, like [1,18]. Still others work on the applications based on audio classification, for example, determination of emotional content of video clips [16].
Other researchers are comparing existing feature extraction methods, classifier, and parameter selection schemes, making audio classification implementation practical, and even have prototype implemented on a Nokia cellphone [14,15].
Arrangements particularly focused on speech/music discrimination include [19] and [20].
Exemplary classifiers also include those detailed in patent publications 20020080286 (British Telecomm), 20020080286 (NEC), 20020080286 (Philips), 20030009325 (Deutsche Telekom), 20040210436 (Microsoft), 20100257129 and 20120109643 (Google), and U.S. Pat. No. 5,712,953 (Hewlett-Packard).
Other Remarks
Having described and illustrated the principles of our inventive work with reference to illustrative examples, it will be recognized that the technology is not so limited.
For example, while reference has been made to smartphones, it will be recognized that this technology finds utility with all manner of devices—both portable and fixed. PDAs, organizers, portable music players, desktop computers, laptop computers, tablet computers, netbooks, wearable computers, servers, etc., can all make use of the principles detailed herein.
Similarly, it is expected that head-worn devices (e.g., Google Glass goggles), and other unobtrusive sensor platforms will eventually replace today's smartphones. Naturally, the present technology can be used with such other forms of devices.
The term “smartphone” should be construed to encompass all such devices, even those that are not strictly-speaking cellular, nor telephones.
(Details of the iPhone, including its touch interface, are provided in Apple's published patent application 20080174570.)
The design of smartphones and other computers used in embodiments of the present technology is familiar to the artisan. In general terms, each includes one or more processors, one or more memories (e.g. RAM), storage (e.g., a disk or flash memory), a user interface (which may include, e.g., a keypad, a TFT LCD or OLED display screen, touch or other gesture sensors, a camera or other optical sensor, a compass sensor, a 3D magnetometer, a 3-axis accelerometer, a microphone, etc., together with software instructions for providing a graphical user interface), interconnections between these elements (e.g., buses), and an interface for communicating with other devices (which may be wireless, such as GSM, CDMA, W-CDMA, CDMA2000, TDMA, EV-DO, HSDPA, WiFi, WiMax, or Bluetooth, and/or wired, such as through an Ethernet local area network, a T−1 internet connection, etc.).
While this specification earlier noted its relation to the assignee's previous patent filings, it bears repeating. These disclosures should be read in concert and construed as a whole. Applicants intend that features in each be combined with features in the others. That is, it should be understood that the methods, elements and concepts disclosed in the present application be combined with the methods, elements and concepts detailed in those related applications. While some have been particularly detailed in the present specification, many have not—due to the large number of permutations and combinations is large. However, implementation of all such combinations is straightforward to the artisan from the provided teachings.
The processes and system components detailed in this specification may be implemented as instructions for computing devices, including general purpose processor instructions for a variety of programmable processors, including microprocessors, graphics processing units (GPUs, such as the nVidia Tegra APX 2600), digital signal processors (e.g., the Texas Instruments TMS320 series devices), etc. These instructions may be implemented as software, firmware, etc. These instructions can also be implemented to various forms of processor circuitry, including programmable logic devices, FPGAs (e.g., the noted Xilinx Virtex series devices), FPOAs (e.g., the noted PicoChip devices), and application specific circuits—including digital, analog and mixed analog/digital circuitry. Execution of the instructions can be distributed among processors and/or made parallel across processors within a device or across a network of devices. Transformation of content signal data may also be distributed among different processor and memory devices. References to “processors” or “modules” should be understood to refer to functionality, rather than requiring a particular form of hardware and/or software implementation.
Software instructions for implementing the detailed functionality can be readily authored by artisans, from the descriptions provided herein, e.g., written in C, C++, Visual Basic, Java, Python, Tcl, Perl, Scheme, Ruby, etc. Smartphones and other devices according to certain implementations of the present technology can include software modules for performing the different functions and acts. Known artificial intelligence systems and techniques can be employed to make the inferences, conclusions, and other determinations noted above.
Commonly, each device includes operating system software that provides interfaces to hardware resources and general purpose functions, and also includes application software which can be selectively invoked to perform particular tasks desired by a user. Known browser software, communications software, and media processing software can be adapted for many of the uses detailed herein. Software and hardware configuration data/instructions are commonly stored as instructions in one or more data structures conveyed by tangible media, such as magnetic or optical discs, memory cards, ROM, etc., which may be accessed across a network. Some embodiments may be implemented as embedded systems—a special purpose computer system in which the operating system software and the application software is indistinguishable to the user (e.g., as is commonly the case in basic cell phones). The functionality detailed in this specification can be implemented in operating system software, application software and/or as embedded system software.
While this disclosure has detailed particular ordering of acts and particular combinations of elements in the illustrative embodiments, it will be recognized that other contemplated methods may re-order acts (possibly omitting some and adding others), and other contemplated combinations may omit some elements, add others, and configure the elements differently, etc.
Although disclosed as a complete system, sub-combinations of the detailed arrangements are also separately contemplated.
While detailed primarily in the context of systems that perform audio capture and processing, corresponding arrangements are equally applicable to systems that capture and process visual stimulus (imagery), or that capture and process both imagery and audio.
Similarly, while certain aspects of the technology have been described by reference to illustrative methods, it will be recognized that apparatus configured to perform the acts of such methods are also contemplated as part of applicant's inventive work. Likewise, other aspects have been described by reference to illustrative apparatus, and the methodology performed by such apparatus is likewise within the scope of the present technology. Still further, tangible computer readable media containing instructions for configuring a processor or other programmable system to perform such methods is also expressly contemplated.
The reference to Bluetooth technology to indicate proximity to, and identity of, nearby persons is illustrative only. Many alternative technologies are known to perform one or both of these functions, and can be readily substituted.
The illustrations should be understood as exemplary and not limiting.
It is impossible to expressly catalog the myriad variations and combinations of the technology described herein. Applicants recognize and intend that the concepts of this specification can be combined, substituted and interchanged—both among and between themselves, as well as with those known from the cited prior art. Moreover, it will be recognized that the detailed technology can be included with other technologies—current and upcoming—to advantageous effect.
The reader is presumed to be familiar with the documents (including patent documents) referenced herein. To provide a comprehensive disclosure without unduly lengthening this specification, applicants incorporate-by-reference these documents referenced above. (Such documents are incorporated in their entireties, even if cited above in connection with specific of their teachings.) These references disclose technologies and teachings that can be incorporated into the arrangements detailed herein, and into which the technologies and teachings detailed herein can be incorporated.
This application is a continuation of application Ser. No. 16/262,634, filed Jan. 30, 2019 (now U.S. Pat. No. 10,510,349), which is a continuation of application Ser. No. 15/711,357, filed Sep. 21, 2017 (now U.S. Pat. No. 10,199,042), which is a continuation of application Ser. No. 15/446,837, filed Mar. 1, 2017 (now abandoned), which is a continuation of application Ser. No. 14/947,008, filed Nov. 20, 2015 (now U.S. Pat. No. 9,595,258), which is a divisional of application Ser. No. 13/607,095, filed Sep. 7, 2012 (now U.S. Pat. No. 9,196,028), which is a non-provisional of applications 61/542,737, filed Oct. 3, 2011, and 61/538,578, filed Sep. 23, 2011. Application Ser. No. 15/711,357 is also a continuation in part of application Ser. No. 15/139,671, filed Apr. 26, 2016 (now U.S. Pat. No. 9,830,950), which is a continuation of application Ser. No. 14/157,108, filed Jan. 16, 2014 (now U.S. Pat. No. 9,330,427), which is a divisional of application Ser. No. 13/299,140, filed Nov. 17, 2011 (now U.S. Pat. No. 8,819,172), which is a continuation in part of application PCT/US11/59412, filed Nov. 4, 2011 (now published as WO2012061760). Application PCT/US11/59412 is a continuation-in-part of each of application Ser. No. 13/278,949, filed Oct. 21, 2011 (now U.S. Pat. No. 9,183,580); Ser. No. 13/207,841, filed Aug. 11, 2011 (now U.S. Pat. No. 9,218,530); and Ser. No. 13/174,258, filed Jun. 30, 2011 (now U.S. Pat. No. 8,831,279). Application PCT/US11/59412 is also a non-provisional of applications 61/501,602, filed Jun. 27, 2011; 61/485,888, filed May 13, 2011; 61/483,555, filed May 6, 2011; 61/479,323, filed Apr. 26, 2011; and 61/471,651, filed Apr. 4, 2011.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5799068 | Kikinis et al. | Aug 1998 | A |
| 6122403 | Rhoads | Sep 2000 | A |
| 6182218 | Saito | Jan 2001 | B1 |
| 6590996 | Reed | Jul 2003 | B1 |
| 6614914 | Rhoads | Sep 2003 | B1 |
| 6722569 | Ehrhart et al. | Apr 2004 | B2 |
| 6947571 | Rhoads | Sep 2005 | B1 |
| 6968564 | Srinivasan | Nov 2005 | B1 |
| 6990453 | Wang | Jan 2006 | B2 |
| 7003731 | Rhoads | Feb 2006 | B1 |
| 7006555 | Srinivasan | Feb 2006 | B1 |
| 7020304 | Alattar | Mar 2006 | B2 |
| 7076737 | Abbott et al. | Jul 2006 | B2 |
| 7185201 | Rhoads | Feb 2007 | B2 |
| 7359889 | Wang | Apr 2008 | B2 |
| 7370190 | Calhoon | May 2008 | B2 |
| 7512889 | Newell et al. | Mar 2009 | B2 |
| 7516074 | Bilobrov | Apr 2009 | B2 |
| 7565294 | Rhoads | Jul 2009 | B2 |
| 7676372 | Oba | Mar 2010 | B1 |
| 7760902 | Rhoads | Jul 2010 | B2 |
| 7774504 | Chene et al. | Aug 2010 | B2 |
| 9196028 | Rodriguez et al. | Nov 2015 | B2 |
| 9595258 | Rodriguez et al. | Mar 2017 | B2 |
| 20010031066 | Meyer | Oct 2001 | A1 |
| 20020055924 | Liming | May 2002 | A1 |
| 20020065063 | Uhlik | May 2002 | A1 |
| 20030062419 | Ehrhart et al. | Apr 2003 | A1 |
| 20040091111 | Levy | May 2004 | A1 |
| 20040138877 | Ariu | Jul 2004 | A1 |
| 20050198095 | Du et al. | Sep 2005 | A1 |
| 20060009702 | Iwaki et al. | Jan 2006 | A1 |
| 20060031684 | Sharma et al. | Feb 2006 | A1 |
| 20060047704 | Gopalakrishnan | Mar 2006 | A1 |
| 20060107219 | Ahya et al. | May 2006 | A1 |
| 20070100480 | Sinclair et al. | May 2007 | A1 |
| 20070112567 | Lau et al. | May 2007 | A1 |
| 20070174059 | Rhoads | Jul 2007 | A1 |
| 20070185840 | Rhoads | Aug 2007 | A1 |
| 20070187505 | Rhoads | Aug 2007 | A1 |
| 20070192352 | Levy | Aug 2007 | A1 |
| 20070250716 | Brunk | Oct 2007 | A1 |
| 20070286463 | Ritzau | Dec 2007 | A1 |
| 20080057911 | Lauper | Mar 2008 | A1 |
| 20080243806 | Dalal | Oct 2008 | A1 |
| 20080263046 | Kristensson | Oct 2008 | A1 |
| 20080267504 | Schloter et al. | Oct 2008 | A1 |
| 20080296392 | Connell et al. | Dec 2008 | A1 |
| 20080300011 | Rhoads | Dec 2008 | A1 |
| 20090002491 | Haler | Jan 2009 | A1 |
| 20090031814 | Takiguchi | Feb 2009 | A1 |
| 20090164896 | Thorn | Jun 2009 | A1 |
| 20090247184 | Sennett | Oct 2009 | A1 |
| 20090259936 | Tanskanen | Oct 2009 | A1 |
| 20100004926 | Neoran et al. | Jan 2010 | A1 |
| 20100036717 | Trest | Feb 2010 | A1 |
| 20100046842 | Conwell | Feb 2010 | A1 |
| 20100048242 | Rhoads et al. | Feb 2010 | A1 |
| 20100070272 | Lee et al. | Mar 2010 | A1 |
| 20100070284 | Oh | Mar 2010 | A1 |
| 20100119208 | Davis | May 2010 | A1 |
| 20100150434 | Reed | Jun 2010 | A1 |
| 20100158310 | McQueen et al. | Jun 2010 | A1 |
| 20100162105 | Beebe et al. | Jun 2010 | A1 |
| 20100205628 | Davis | Aug 2010 | A1 |
| 20100211693 | Master | Aug 2010 | A1 |
| 20100226526 | Modro et al. | Sep 2010 | A1 |
| 20100228632 | Rodriguez | Sep 2010 | A1 |
| 20100271365 | Smith et al. | Oct 2010 | A1 |
| 20100277611 | Holt et al. | Nov 2010 | A1 |
| 20100284617 | Ritzau et al. | Nov 2010 | A1 |
| 20100318470 | Meinel et al. | Dec 2010 | A1 |
| 20110043652 | King et al. | Feb 2011 | A1 |
| 20110058707 | Rhoads | Mar 2011 | A1 |
| 20110098056 | Rhoads | Apr 2011 | A1 |
| 20110125735 | Petrou et al. | May 2011 | A1 |
| 20110131040 | Huang et al. | Jun 2011 | A1 |
| 20110137895 | Petrou et al. | Jun 2011 | A1 |
| 20110143811 | Rodriguez | Jun 2011 | A1 |
| 20110150292 | Boncyk et al. | Jun 2011 | A1 |
| 20110153050 | Bauer et al. | Jun 2011 | A1 |
| 20110159921 | Davis et al. | Jun 2011 | A1 |
| 20110161076 | Davis et al. | Jun 2011 | A1 |
| 20110212717 | Rhoads et al. | Sep 2011 | A1 |
| 20110233278 | Patel et al. | Sep 2011 | A1 |
| 20110244919 | Aller et al. | Oct 2011 | A1 |
| 20110274310 | Rhoads | Nov 2011 | A1 |
| 20120013766 | Rothschild | Jan 2012 | A1 |
| 20120023060 | Rothkopf et al. | Jan 2012 | A1 |
| 20120034904 | LeBeau et al. | Feb 2012 | A1 |
| 20120046071 | Brandis | Feb 2012 | A1 |
| 20120059780 | Kononen et al. | Mar 2012 | A1 |
| 20120075168 | Osterhout et al. | Mar 2012 | A1 |
| 20120078397 | Lee et al. | Mar 2012 | A1 |
| 20120141660 | Fiedler | Jun 2012 | A1 |
| 20120143655 | Sunaoshi et al. | Jun 2012 | A1 |
| 20120224743 | Rodriguez et al. | Sep 2012 | A1 |
| 20120284012 | Rodriguez et al. | Nov 2012 | A1 |
| 20130007201 | Jeffrey et al. | Jan 2013 | A1 |
| 20130044233 | Bai et al. | Feb 2013 | A1 |
| 20130090926 | Grokop et al. | Apr 2013 | A1 |
| 20130097630 | Rodriguez | Apr 2013 | A1 |
| 20130254422 | Master et al. | Sep 2013 | A2 |
| 20140282051 | Cruz-Hernandez | Sep 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2000322078 | Nov 2000 | JP |
| 2008009120 | Jan 2008 | JP |
| 0200001 | Jan 2002 | WO |
| WO02011116309 | Sep 2011 | WO |
| 2012061760 | May 2012 | WO |
| 2012127439 | Sep 2012 | WO |
| WO2013043393 | Mar 2013 | WO |
| Entry |
|---|
| Alin, Object Tracking with Iphone 3G's, dated Feb. 16, 2010. |
| Chen, et al, “Listen-to-nose: a low-cost system to record nasal symptoms in daily life,” 14th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 590-591. |
| Larson, et al., “SpiroSmart: using a microphone to measure lung function on a mobile phone,” 14th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 280-289. |
| Lu, et al., “StressSense: Detecting stress in unconstrained acoustic environments using smartphones,” 14th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 351-360. |
| Miluzzo, “Sensing Meets Mobile Social Network: The Design, Implementation and Evaluation of the CenceMe Application”, dated Nov. 5, 2008. |
| Modro, et al, Digital Watermarking Opportunities Enabled by Mobile Media Proliferation, Proc. SPIE, vol. 7254, Jan. 2009. |
| Rodriguez, et al, Evolution of Middleware to Support Mobile Discovery, presented at MobiSense, Jun. 2011. |
| Tulusan, et al., “Lullaby: a capture & access systems for understanding the sleep environment,” 14th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 226-234. |
| Wang, et al, A Framework of Energy Efficient Mobile Sensing for Automatic User State Recognition, MOBISYS 2009, Jun. 2009, 14 pp. |
| Yatani et al, “BodyScope: a wearable acoustic sensor for activity recognition,” 14th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 341-350. |
| PCT International Search Report and PCT Written Opinion of the International Searching Authority, PCT/US12/54232, dated Nov. 14, 2012. |
| Miluzzo, “Smartphone Sensing”, dated Jun. 2011. |
| Alin, Object Tracing with Iphone 3G's, dated Feb. 16, 2010. |
| Wallach, “Smartphone Security: Trends and Predictions”, dated Feb. 17, 2011. |
| Emiliano Miluzzo, ‘Sensing Meets Mobile Social Networks: The Design, Implementation and Evaluation of the CenceMe Application’, (Nov. 7, 2008), URL: http://dl.acm.org/citation.cfm?id=1460445, (May 8, 2012), XP055026265. |
| Eagle, “Machine Perception and Learning of Complex Social Systems”, dated Jun. 27, 2005. |
| Chen, et al, ‘Listen-to-nose: a low-cost system to record nasal symptoms in daily life,’ 14.sup.th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 590-591. |
| Larson, et al., ‘SpiroSmart: using a microphone to measure lung function on a mobile phone,’ 14.sup.th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 280-289. |
| Lu, et al, SpeakerSense: Energy Efficient Unobtrusive Speaker Identification on Mobile Phones, Pervasive Computing Conference, Jun. 2011, pp. 188-205. |
| Lu, et al., ‘StressSense: Detecting stress in unconstrained acoustic environments using smartphones,’ 14.sup.th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 351-360. |
| Rodriguez et al., ‘Evolution of Middleware to Support Mobile Discovery,’ Presented at the MobiSense Workshop/Pervasive on Jun. 12, 2011. |
| Tulusan, et al., ‘Lullaby: a capture & access systems for understanding the sleep environment,’ 14.sup.th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 226-234. |
| Yatani et al, ‘BodyScope: a wearable acoustic sensor for activity recognition,’ 14.sup.th International Conference on Ubiquitous Computing, Sep. 5-8, 2012, pp. 341-350. |
| Benbasat, et al, A framework for the automated generation of power-efficient classifiers for embedded sensor nodes, Proc. Of the 5th Int'l Conf. on Embedded Networked Sensor Systems. ACM, 2007. |
| Brunette, et al., Some sensor network elements for ubiquitous computing, 4th Int'l. Symposium on Information Processing in Sensor Networks, pp. 388-392, 2005. |
| Csirik, et al, Sequential Classifier Combination for Pattern Recognition in Wireless Sensor Networks, 10th Int'l Workshop on Multiple Classifier Systems, Jun. 2011. |
| Kang et al, Orchestrator—An Active Resource Orchestration Framework for Mobile Context Monitoring in Sensor-Rich Mobile Environments, IEEE Conf. on Pervasive Computing and Communications, pp. 135-144, 2010. |
| Lane, et al., A Survey of Mobile Phone Sensing, IEEE Communications Magazine, 48.9, pp. 140-150, 2010. |
| Misra, et al, Optimizing Sensor Data Acquisition for Energy-Efficient Smartphone-based Continuous Event Processing, 12th IEEE International Conf. on Mobile Data Management, Jun. 2011. |
| Priyantha, et al, Eers—Energy Efficient Responsive Sleeping on Mobile Phones, Workshop on Sensing for App Phones, 2010. |
| Soria-Morillo et al, Mobile Architecture for Communication and Development of Applications Based on Context, 12th IEEE Int'l Conf. on Mobile Data Management, Jun. 2011. |
| Modro et al, Digital Watermarking Opportunities Enabled by Mobile Media Proliferation, Media Forensics and Security, SPIE Proceedings vol. 7254, Jan. 19, 2009. |
| Nishihara et al, Power Savings in Mobile Devices Using Context-Aware Resource Control, IEEE Conf. on Networking and Computing, 2010, pp. 220-226. |
| Wang, et al, A Framework of Energy Efficient Mobile Sensing for Automatic User State Recognition, Proc. 7th Int'l ACM Conf. on Mobile Systems, Applications, and Services, 2009. |
| Excerpts from prosecution of corresponding Chinese application 201280054460.1, including amended claims 1-46 on which prosecution is based, translated Text of the First Action dated Mar. 27, 2015, claims submitted in response, translated Text of the Second Action dated Dec. 10, 2015, claims filed in response, and Notice of Allowance dated Apr. 13, 2016. |
| Excerpts from prosecution of corresponding European application 12833294.7, including amended claims 1-11 on which prosecution is based, Supplemental European Search Report dated Apr. 1, 2015, and Written Opinion dated Apr. 10, 2015,a and claims filed in response in Oct. 2015. |
| Excerpts from prosecution of U.S. Appl. No. 14/189,236, including original claims, Action dated Aug. 20, 2014, Response dated Nov. 19, 2014, Final Action dated Feb. 5, 2015, Response after Final dated Apr. 6, 2015, Advisory Action dated Apr. 22, 2015, Pre-Brief Conference Request dated May 11, 2015, Pre-Appeal Conference Decision dated May 21, 2015, Applicant responses dated Jun. 2 and 19, 2015, Rejection dated Jun. 19, 2015, Interview summary dated Aug. 13, 2015, Applicant Response dated Aug. 19, 2015, and Notice of Allowance dated Nov. 20, 2015. |
| Excerpts from prosecution of Japanese patent application P2014-531853, namely originally-presented claims, English translation of Notice of Reasons for Rejection dated Oct. 25, 2016, amended claims of Jan. 2017, and English translation of Final Notice of Rejection dated Jun. 13, 2017. |
| WO2012/061760 (May 10, 2012), with International Search Report (dated Apr. 13, 2012) and International Preliminary Report on Patentability (dated May 7, 2013). |
| Number | Date | Country | |
|---|---|---|---|
| 20200227048 A1 | Jul 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61501602 | Jun 2011 | US | |
| 61485888 | May 2011 | US | |
| 61483555 | May 2011 | US | |
| 61479323 | Apr 2011 | US | |
| 61542737 | Oct 2011 | US | |
| 61538578 | Sep 2011 | US | |
| 61471651 | Apr 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13607095 | Sep 2012 | US |
| Child | 14947008 | US | |
| Parent | 13299140 | Nov 2011 | US |
| Child | 14157108 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16262634 | Jan 2019 | US |
| Child | 16709463 | US | |
| Parent | 15711357 | Sep 2017 | US |
| Child | 16262634 | US | |
| Parent | 15446837 | Mar 2017 | US |
| Child | 15711357 | US | |
| Parent | 14947008 | Nov 2015 | US |
| Child | 15446837 | US | |
| Parent | 14157108 | Jan 2014 | US |
| Child | 15139671 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15139671 | Apr 2016 | US |
| Child | 15446837 | US | |
| Parent | PCT/US2011/059412 | Nov 2011 | US |
| Child | 13299140 | US | |
| Parent | 13278949 | Oct 2011 | US |
| Child | PCT/US2011/059412 | US | |
| Parent | 13207841 | Aug 2011 | US |
| Child | 13278949 | US | |
| Parent | 13174258 | Jun 2011 | US |
| Child | 13207841 | US |
