Systems and methods for wirelessly modifying detection characteristics of portable devices

Example systems, methods, apparatus and articles of manufacture for wirelessly modifying detection characteristics of portable devices are disclosed herein. Example portable devices disclosed here include a microphone and radio frequency circuitry to scan for a radio frequency beacon at a first scanning rate. Disclosed example apparatus also include a processor to trigger activation of audio monitoring, in the portable device, of an audio signal obtained via the microphone. In some disclosed examples, the audio monitoring is to be triggered in response to a first connection being made via the radio frequency circuitry with a first transmitter of the radio frequency beacon. In some disclosed examples, the audio monitoring is to collect research data from the audio signal.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
RELATED APPLICATION(S)

This patent arises from a continuation of U.S. patent application Ser. No. 13/657,380, which is entitled “SYSTEMS AND METHODS FOR WIRELESSLY MODIFYING DETECTION CHARACTERISTICS OF PORTABLE DEVICES,” and which was filed on Oct. 22, 2012. Priority to U.S. patent application Ser. No. 13/657,380 is claimed. U.S. patent application Ser. No. 13/657,380 is hereby incorporated by reference in its entirety

TECHNICAL FIELD

The present disclosure is directed to processor-based audience analytics. More specifically, the disclosure describes systems and methods for utilizing wireless data signals to control and/or regulate data scanning and retrieval, as well as audio monitoring.

BACKGROUND INFORMATION

Wireless technology such as Bluetooth and Wi-Fi has become an important part of data transfer for portable processing devices. Bluetooth is a proprietary open wireless technology standard for exchanging data over short distances from fixed and mobile devices, creating personal area networks (PANs) with high levels of security. Bluetooth uses a radio technology called frequency-hopping spread spectrum, which divides the data being sent and transmits portions of it on up to 79 bands (1 MHz each, preferably centered from 2402 to 2480 MHz) in the range 2,400-2,483.5 MHz (allowing for guard bands). This range is in the globally unlicensed Industrial, Scientific and Medical (ISM) 2.4 GHz short-range radio frequency band. Gaussian frequency-shift keying (GFSK) modulation may be used, however, more advanced techniques, such as π/4-DQPSK and 8DPSK modulation may also be used between compatible devices. Devices functioning with GFSK are said to be operating in “basic rate” (BR) mode where an instantaneous data rate of 1 Mbit/s is possible. “Enhanced Data Rate” (EDR) is used to describe π/4-DPSK and 8DPSK schemes, each giving 2 and 3 Mbit/s respectively. The combination of these (BR and EDR) modes in Bluetooth radio technology is classified as a “BR/EDR radio”.

Bluetooth is a packet-based protocol with a master-slave structure. One master may communicate with up to 7 slaves in a piconet, where all devices preferably share the master's clock. Packet exchange is based on the basic clock, defined by the master, which may tick at 312.5 μs intervals. In the simple example of single-slot packets, the master transmits in even slots and receives in odd slots; the slave, conversely, receives in even slots and transmits in odd slots. Packets may be 1, 3 or 5 slots long but in all cases the master transmit will begin in even slots and the slave transmit in odd slots.

Bluetooth provides a secure way to connect and exchange information between devices such as faxes, mobile phones, telephones, laptops, personal computers, printers, Global Positioning System (GPS) receivers, digital cameras, and video game consoles. At any given time, data can be transferred between the master and one other device. The master may choose which slave device to address and may switch rapidly from one device to another in a round-robin fashion. In the area of computer processors, Bluetooth is commonly used to operationally link devices to the computer processor. In other cases, Bluetooth signals are used to “unlock” a computer processor when an enabled device is within a certain proximity.

One area where improvements are needed is in the area of media exposure tracking and web analytics. To date, Bluetooth has been relatively underutilized in this area. What is needed are methods, systems and apparatuses for utilizing Bluetooth signal characteristics in conjunction with media exposure data to produce research data that accurately identifies and characterizes devices, and their accompanying users. Additionally, it has been found that Bluetooth and Wifi communications may be used to advantageously control functions of portable wireless devices to provide efficient operations for one or multiple devices.

SUMMARY

Accordingly, apparatuses, systems and methods are disclosed for computer-implemented techniques for modifying operation of a portable processing device configured to scan for wireless signals under a first scan rate. Under one exemplary embodiment, a first wireless signal is received in the portable processing device and a characteristic of the first wireless signal is determined. The characteristic is then processed to determine if it conforms with a predetermined characteristic. The operation of the portable processing device is then modified if the processing step determines that the characteristic conforms with the predetermined characteristic, wherein the modification comprises at least one of (i) modifying the first scan rate to a second scan rate, the second scan rate being different from the first, and (ii) activating monitoring capabilities in the portable processing device to collect research data on media data.

Under another exemplary embodiment, a portable processing device is configured to scan for wireless signals under a first scan rate, comprising: a memory; a microphone operatively coupled to the memory; an input operatively coupled to the memory, wherein the input is configured to receive a first wireless signal; and a processor, operatively coupled to the input, wherein the processor is configured to determine a characteristic of the first wireless signal and process the characteristic to determine if it conforms with a predetermined characteristic, and wherein the processor is further configured to modify the operation of the portable processing device if the characteristic conforms with the predetermined characteristic, wherein the modification comprises at least one of (i) modifying the first scan rate to a second scan rate, the second scan rate being different from the first, and (ii) activating monitoring capabilities in the portable processing device to collect research data on media data received via the microphone.

Under yet another embodiment, a computer-implemented method is disclosed for modifying operation of a portable processing device, where the method comprises the steps of configuring the device to execute a first scan rate for detecting wireless signals; receiving a first wireless signal in the portable processing device; determining a characteristic of the first wireless signal; processing the characteristic to determine if it conforms with a predetermined characteristic; detecting the presence of media data in the portable processing device; and modifying the operation of the portable processing device if the processing step determines that the characteristic conforms with the predetermined characteristic, wherein the modification comprises at least one of (i) modifying the first scan rate to a second scan rate, the second scan rate being different from the first, and (ii) activating monitoring capabilities in the portable processing device to collect research data on the media data.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 illustrates an exemplary system under one embodiment, where media data is provided from a network to a processing device in the vicinity of a plurality of portable devices;

FIG. 2 illustrates an exemplary Bluetooth protocol stack utilized for communication;

FIG. 3 illustrates an exemplary service discovery process;

FIG. 4 illustrates an exemplary authentication mechanism for connected devices;

FIG. 5 is an exemplary flowchart for monitoring an RSSI Bluetooth signal characteristic;

FIG. 6 illustrates an exemplary block diagram of a portable device utilized in the present disclosure;

FIG. 7 illustrates another exemplary embodiment of a portable device configured to monitor media data communicating with a plurality of wireless transmitters; and

FIG. 8 is an exemplary flow diagram of wireless transmitter communication for a portable device under one embodiment.

 DETAILED DESCRIPTION

The present disclosure generally deals with the collection of research data relating to media and media data from portable computing devices using wireless technologies, such as Bluetooth and Wi-Fi. Additionally, the present disclosure deals with configuring portable computing devices for the collection of research data using wireless technologies. Regarding collection of research data, FIG. 1 illustrates an exemplary system 100 that comprises a computer processing device 101 and a plurality of portable computing devices (102-104) that are in the vicinity of processing device 101. In this example, processing device 101 is illustrated as a personal computer, while portable computing devices 102-104 are illustrated as Bluetooth-enabled, Wi-Fi-enabled, or other wirelessly-enabled cell phones. One example of a portable computing device is illustrated below in connection with FIG. 6. It is understood by those skilled in the art that other similar devices may be used as well. For example, processing device 101 may also be a laptop, a computer tablet, a set-top box, a media player, a network-enabled television or DVD player, and the like. Portable computing devices 102-104 may also be laptops, PDAs, tablet computers, Personal People Meters™ (PPMs), wireless telephone, etc.

Under a preferred embodiment, processing device 101 connects to content source 125 via network 110 to obtain media data. The terms “media data” and “media” as used herein mean data which is widely accessible, whether over-the-air, or via cable, satellite, network, internetwork (including the Internet), displayed, distributed on storage media, or by any other means or technique that is humanly perceptible, without regard to the form or content of such data, and including but not limited to audio, video, audio/video, text, images, animations, databases, broadcasts, displays (including but not limited to video displays), web pages and streaming media. As media is received on processing device 101, analytics software residing on processing device 101 collects information relating to media data received from content source 125, and additionally may collect data relating to network 110.

Data relating to the media data may include a “cookie”, also known as an HTTP cookie, which can provide state information (memory of previous events) from a user's browser and return the state information to a collecting site, which may be the content source 125 or collection site 121 (or both). The state information can be used for identification of a user session, authentication, user's preferences, shopping cart contents, or anything else that can be accomplished through storing text data on the user's computer.

Referring back to the example of FIG. 1, media data is received on processing device 101. At the time the media data is received, portable computing devices 102-104 are in the vicinity, and are configured to establish Bluetooth communication (“pair”) with processing device 101. After Bluetooth communications are established, processing device 101 collects the Bluetooth signal characteristics from each portable computing device. Under a preferred embodiment, Bluetooth signal characteristics relate to status parameters of a Bluetooth connection together with any other signal strength values made available in Bluetooth Core Specification. The Host Controller Interface (HCI) (discussed in greater detail below) provides access to three such connection status parameters, including Link Quality (LQ), Received Signal Strength Indicator (RSSI), and Transmit Power Level (TPL). All these status parameters require the establishment of an active Bluetooth connection in order to be measured. Another signal parameter, referred to as “Inquiry Result with RSSI”, alternately also be used, where the parameter perceives RSSI from the responses sent by its nearby devices.

Briefly, Link Quality (LQ) is an 8-bit unsigned integer that evaluates the perceived link quality at the receiver. It ranges from 0 to 255, where the larger the value, the better the link's state. For most Bluetooth modules, it is derived from the average bit error rate (BER) seen at the receiver, and is constantly updated as packets are received. Received Signal Strength Indicator (RSSI) is an 8-bit signed integer that denotes received (RX) power levels and may further denote if the level is within or above/below the Golden Receiver Power Range (GRPR), which is regarded as the ideal RX power range. As a simplified example, when multipath propagation is present, RSSI is generally based on a line-of-sight (LOS) field strength and a reflected signal strength, where the overall strength is proportional to the magnitude of the electromagnetic wave's E⋅field. Thus, when there is minimal reflective interference, RSSI may be determined by 20 log (LOS+RS), where LOS is the line-of-sight signal strength and RS is the reflected signal. When reflective interference is introduced RSSI becomes 20 log (LOS−RS).

Transmit Power Level (TPL) is an 8-bit signed integer which specifies the Bluetooth module's transmit power level (in dBm). Although there are instances when a transmitter will use its device-specific default power setting to instigate or answer inquiries, its TPL may vary during a connection due to possible power control. “Inquiry Result with RSSI” works in a similar manner as a typical inquiry. In addition to the other parameters (e.g., Bluetooth device address, clock offset) generally retrieved by a normal inquiry, it also provides the RSSI value. Since it requires no active connection, the radio layer simply monitors the RX power level of the current inquiry response from a nearby device, and infers the corresponding RSSI.

For system 100, transmission may occur from direct voltage controlled oscillator (VCO) modulation to IQ mixing at the final radio frequency (RF). In the receiver, a conventional frequency discriminator or IQ down-conversion combined with analog-to-digital conversion is used. The Bluetooth configuration for each of the portable computing devices 102-104 and processing device 101 include a radio unit, a baseband link control unit, and link management software. Higher-level software utilities focusing on interoperability features and functionality are included as well. Enhanced Data Rate (EDR) functionalities may also be used to incorporate phase shift keying (PSK) modulation scheme to achieve a data rate of 2 or 3 Mb/s. It allows greater possibilities for using multiple devices on the same connection because of the increased bandwidth. Due to EDR having a reduced duty cycle, there is lower power consumption compared to a standard Bluetooth link.

As mentioned above, processing device 101 collects the Bluetooth signal characteristics from each portable computing device (102-104). At the same time, processing device 101 is equipped with software and/or hardware allowing it to measure media data exposure for a given period of time (e.g., digital signage, QR scan, a web browsing session, etc.) to produce research data. The term “research data” as used herein means data comprising (1) data concerning usage of media data, (2) data concerning exposure to media data, and/or (3) market research data. Under a preferred embodiment, when processing device 101 detects media data activity, it triggers a timer task to run for a predetermined period of time (e.g., X minutes) until the activity is over. At this time, discovery of paired devices is performed to locate each of the paired devices. Preferably, the UIDs of each device is known in advance. For each device discovered and paired, processing device 101 records each Bluetooth signal characteristic for the connection until the end of the session. Afterwards, the signal characteristics collected for each device, and the resultant research data for the session is forwarded to collection server 121 for further processing and/or analysis. Collection server 121 may further be communicatively coupled to server 120 which may be configured to provide further processing and/or analysis, generate reports, provide content back to processing device 101, and other functions. Of course, these functions can readily be incorporated into collection server 121, depending on the needs and requirements of the designer.

FIG. 2 shows an exemplary Bluetooth protocol stack utilized for communication in the embodiment of FIG. 1. Generally, the transition from implementation in hardware and firmware (lower layers) to software (higher layers). If each of these groups of layers are separate entities, such as a PC card and laptop computer, then they can communicate with each other through Host Controller Interface 213 (HCI), which provides paths for data, audio, and control signals between the Bluetooth module and host.

Radio 210 completes the physical layer by providing a transmitter and receiver for two-way communication. Data packets are assembled and fed to the radio 210 by the baseband/link controller 211. The link controller of 211 provides more complex state operations, such as the standby, connect, and low-power modes. The baseband and link controller functions are combined into one layer to be consistent with their treatment in the Bluetooth Specification. Link manager 212 provides link control and configuration through a low-level language called the link manager protocol (LMP).

Logical link control and adaptation protocol (L2CAP) 214 establishes virtual channels between hosts that can keep track of several simultaneous sessions such as multiple file transfers. L2CAP 214 also takes application data and breaks it into Bluetooth-size portions for transmission, and reverses the process for received data. Radio Frequency Communication (RFCOMM) 215 is a Bluetooth serial port emulator, and its main purpose is to “trick” application 220 into thinking that a wired serial port exists instead of an RF link. Finally, various software programs that are needed for different Bluetooth usage models enable resident application 220 to use Bluetooth. These include service discovery protocol (SDP) 219, object exchange (OBEX), 216 telephony control protocol specification (TCS) 218, and Wireless Application Protocol (WAP) 217. Bluetooth radio 210 and baseband/link controller 211 consist of hardware that is typically available as one or two integrated circuits. Firmware-bast link manager 212 and one end of the host controller interface 213, perhaps with a bus driver for connection to the host, complete the Bluetooth module shown in FIG. 2. The remaining parts of tile protocol stack and the host end of HCI 213 can be implemented in software on the host itself.

FIG. 3 illustrates an exemplary Bluetooth discovery process utilizing “Device A” 310 and “Device B” 311 using each respective baseband layer (320, 321). Here, Device A 310 is initiating service discover while Device B 311 establishes communications in order to make it discoverable. The process may be assisted using a service discovery application from an access profile stored in each device.

The initial linking process 312 begins with an inquiry and page among devices in order to establish a piconet. In FIG. 3, Device A 310 is configured as a prospective slave (p-slave) and Device B 311 is a prospective master (p-master). As a p-master, Device B 311 must send its frequency hop synchronization (FHS) packet to a Device A 310 so the latter can use the same hop sequence and phase used by the master. Preferably, a predetermined hop sequence or set of sequences, are used for paging and inquiries. For inquiries, the p-master may not know about nearby devices, so a single common hop sequence (one sequence for sending an inquiry and another for responding to the inquiry) is used by all devices for initial device discovery. A p-slave responding to an inquiry sends its FHS packet, within which is its Bluetooth device address (BD_ADDR) which may be used for further piconet and scatternet identification. Now the p-master can create a new hopping sequence based the BD_ADDR for transmitting a subsequent page for establishing a piconet with that p-slave.

Inquiries that are sent and replied by a device are typically transmitted at a device-specific default power setting. As a result, signal characteristics, such RSSI collected through an inquiry is relatively free from the side-effect of power control. Accordingly, a inquiry fetched RSSI may provide finer measurements than the connection-based RSSI.

For establishing channel 313, a hop channel set and the sequence of hops through the channel set may be determined by the lower 28 bits of a device's BD_ADDR, and the hop phase may be determined by the 27 most significant bits of CLK. These two values are sent to a hop generator, and the output of this generator goes to the Bluetooth radio's frequency synthesizer. In order to establish communications, Devices A and B should use the same hop channels, the same hop sequence from channel to channel, and the same phase so that they hop together. Also, one device should transmit while the other receives on the same frequency and vice versa. Multiple hop sequences and periods are configured to cover inquiry, page, and connect activity. These include channel hop sequence (used for normal piconet communications between master and slave(s)), page hop sequence (used by a p-master to send a page to a specific p-slave and to respond to the slave's reply), page response sequence (used by a p-slave to respond to a p-master's page), inquiry hop sequence (used by a p-master to send an inquiry to find Bluetooth devices in range), and inquiry response sequence (used by a p-slave to respond to a p-master's inquiry).

Service discovery 314 is used for retrieving information required to set up a transport service or usage scenario, and may also be used to access a device and retrieve its capabilities or to access a specific application and find devices that support that application. Retrieving capabilities requires paging a device and forming an Asynchronous Connectionless Link (ACL) to retrieve the desired information, accessing applications involves connecting to and retrieving information from several devices that are discovered via an inquiry. Thus, service discovery may be used for browsing for services on a particular device, searching for and discovering services based upon desired attributes, and/or incrementally searching a device's service list to limit the amount of data to be exchanged. An L2CAP channel with a protocol service multiplexer (PSM) is used for the exchange of service-related information. Service discovery can have both client and server implementations, with at most one service discovery server on any one device. However, if a device is client only, then it need not have a service discovery server. Each service is preferably listed in the device's SOP database as a service record having a unique ServiceRecordHandle, and each attribute of the service record is given an attribute ID and an attribute value. Attributes include the various classes, descriptors, and names associated with the service record. After service discovery is completed, the channel is released 315.

FIG. 4 illustrates an exemplary authentication configuration 400, where Bluetooth Pairing Service 415 sends API calls to Bluetooth Stack 410 and receives back pairing events. Bluetooth Stack 410 transmits API calls to Bluetooth helper service/function 411, which receives discovery enable signals (inquiry, page scan) from Bluetooth Pairing Service 415. Bluetooth pairing information for Pairing Service 415 is communicated from persistence/settings manager 413 and paired device list 412, which preferably retries information from system registry 414. Bluetooth Pairing Service 415 forwards information to device application 417, and may further retrieve and communicate profile services 416 to application 417 as well.

The authentication process verifies the identity of the device at the other end of a link. The verifier queries the claimant and checks its response; if correct, then authentication is successful. Authorization can be used to grant access to all services, a subset of services, or to some services when authentication is successful, but requires additional authentication based on some user input at the client device for further services. The last item is usually implemented at the application layer. For Bluetooth Pairing Services 415, two devices become paired when they start with the same PIN and generate the same link key, and then use this key for authenticating at least a current communication session. The session can exist for the life of a L2CAP link (for Mode 2 security) or the life of the ACL link (for Mode 3 security). Pairing can occur through an automatic authentication process if both devices already have the same stored PIN from which they can derive the same link keys for authentication. Alternatively, either or both applications can ask their respective users for manual PIN entry. Once devices are paired they can either store their link keys for use in subsequent authentications or discard them and repeat the pairing process each time they connect. If the link keys are stored, then the devices are “bonded,” enabling future authentications to occur using the same link keys and without requiring the user to input the PIN again. The concept of “trust” applies to a device's authorization to access certain services on another device. A trusted device is previously authenticated and, based upon that authentication, has authorization to access various services. An untrusted device may be authenticated, but further action is needed, such as user intervention with a password, before authorization is granted to access services. Also, encryption may be used to further enhance security of connections.

FIG. 5 discloses one exemplary process for linking exposure to media data utilizing Bluetooth signal characteristics described above. In the beginning, a web session 520 starts, which triggers Bluetooth pairing of nearby devices 510. Once paired, the Bluetooth signal characteristics 511 (“BSig”) are initially received. In the event that devices are already paired and/or bonded, the process starts by acquiring Bluetooth signal characteristics 511. Afterwards, a discovery process is run 512 for retrieving information for transport service or usage scenario, and may also be used to access a device and retrieve its capabilities or to access a specific application and find devices that support that application. Under one embodiment, a timer is used for media data exposure, wherein the timer can be set for specific time periods, or may alternately be set and used to correspond with web sessions or other events. When the timer 513 runs out, the process ends in 517. Otherwise, the process moves to 514, where the pairing is validated to ensure that a Bluetooth device is not moving out of range or otherwise compromising the connection. If the pairing validation produces a negative result, the process continues to look for the device via 512 for the time period 513. If the pairing validation is affirmative, the Bluetooth signal characteristics are logged 515 and stored 516 for the duration of the measurement (513). It should be understood that BSig block 515 may include Received Signal Strength Indicator (RSSI) value, a Transmit Power Level (TPL) value and/or a Link Quality (LQ) value

It is understood that the examples above are provided as examples, and are not intended to be limiting in any way. Under an alternate embodiment, Bluetooth signal strengths may be approximated to determine distance. As explained above, an RSSI value provides the distance between the received signal strength and an optimal receiver power rank referred to as the “golden receiver power rank.” The golden receiver power rank is limited by two thresholds. The lower threshold may be defined by an offset of 6 dB to the actual sensitivity of the receiver. The maximum of this value is predefined by −56 dBm. The upper threshold may be 20 dB over the lower one, where the accuracy of the upper threshold is about ±6 dB. Where S is assigned as the received signal strength, the value of S is determined by: (1) S=RSSI+TU, for RSSI>0 and (2) S=RSSI−TL, for RSSI<0, where TU=TL+20 DdB. Here, TU refers to the upper threshold, and TL refers to the lower threshold. The definition of the Bluetooth golden receiver limits the measurement of the RSSI to a distance. In order to measure the most unique characteristics of the signal, only measurements that result in a positive range of the RSSI should be considered for a functional approximation. The approximation may be calculated by choosing the best fitted function given by determining and minimizing the parameters of a least square sum of the signal strength measurements.

With regard to media data exposure measurement, the preferred embodiment collects research data on a computer processing device, associates it with the collected Bluetooth signal characteristics, and (a) transmits the research data and Bluetooth signal characteristics to a remote server(s) (e.g., collection server 121) for processing, (b) performs processing of the research data and Bluetooth signal characteristics in the computer processing device itself and communicates the results to the remote server(s), or (c) distributes association/processing of the research data and Bluetooth signal characteristics between the computer processing device and the remote server(s).

Under another embodiment, one or more remote servers are responsible for collecting research data on media data exposure. When Bluetooth signal characteristics are received from a computer processing device, the signal characteristics are associated with the research data (e.g., using time stamps) and processed. This embodiment is particularly advantageous when remote media data exposure techniques are used to produce research data. One technique, referred to as “logfile analysis,” reads the logfiles in which a web server records all its transactions. A second technique, referred to as “page tagging,” uses JavaScript on each page to notify a third-party server when a page is rendered by a web browser. Both collect data that can be processed to produce web traffic reports together with the Bluetooth signal characteristics. In certain cases, collecting web site data using a third-party data collection server (or even an in-house data collection server) requires an additional DNS look-up by the user's computer to determine the IP address of the collection server. As an alternative to logfile analysis and page tagging, “call backs” to the server from the rendered page may be used to produce research data. In this case, when the page is rendered on the web browser, a piece of Ajax code calls to the server (XMLHttpRequest) and passes information about the client that can then be aggregated.

FIG. 6 is an exemplary embodiment of a portable computing device 700 which may function as a mobile terminal (e.g., see FIGS. 1 and 8, below), and may be a smart phone, tablet computer, or the like. Device 700 may include a central processing unit (CPU) 701 (which may include one or more computer readable storage mediums), a memory controller 702, one or more processors 703, a peripherals interface 704, RF circuitry 705, audio circuitry 706, a speaker 720, a microphone 721, and an input/output (I/O) subsystem 711 having display controller 712, control circuitry for one or more sensors 713 and input device control 714. These components may communicate over one or more communication buses or signal lines in device 700. It should be appreciated that device 700 is only one example of a portable multifunction device 700, and that device 700 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in FIG. 6 may be implemented in hardware or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

In one embodiment, decoder 710 serves to decode ancillary data embedded in audio signals in order to detect exposure to media. Examples of techniques for encoding and decoding such ancillary data are disclosed in U.S. Pat. No. 6,871,180, titled “Decoding of Information in Audio Signals,” issued Mar. 22, 2005, and is incorporated by reference in its entirety herein. Other suitable techniques for encoding data in audio data are disclosed in U.S. Pat. No. 7,640,141 to Ronald S. Kolessar and U.S. Pat. No. 5,764,763 to James M. Jensen, et al., which are incorporated by reference in their entirety herein. Other appropriate encoding techniques are disclosed in U.S. Pat. No. 5,579,124 to Aijala, et al., U.S. Pat. Nos. 5,574,962, 5,581,800 and 5,787,334 to Fardeau, et al., and U.S. Pat. No. 5,450,490 to Jensen, et al., each of which is assigned to the assignee of the present application and all of which are incorporated herein by reference in their entirety.

An audio signal which may be encoded with a plurality of code symbols is received at microphone 721, or via a direct link through audio circuitry 706. The received audio signal may be from streaming media, broadcast, otherwise communicated signal, or a signal reproduced from storage in a device. It may be a direct coupled or an acoustically coupled signal. From the following description in connection with the accompanying drawings, it will be appreciated that decoder 710 is capable of detecting codes in addition to those arranged in the formats disclosed hereinabove.

Alternately or in addition, processor(s) 703 can processes the frequency-domain audio data to extract a signature therefrom, i.e., data expressing information inherent to an audio signal, for use in identifying the audio signal or obtaining other information concerning the audio signal (such as a source or distribution path thereof). Suitable techniques for extracting signatures include those disclosed in U.S. Pat. No. 5,612,729 to Ellis, et al. and in U.S. Pat. No. 4,739,398 to Thomas, et al., both of which are incorporated herein by reference in their entireties. Still other suitable techniques are the subject of U.S. Pat. No. 2,662,168 to Scherbatskoy, U.S. Pat. No. 3,919,479 to Moon, et al., U.S. Pat. No. 4,697,209 to Kiewit, et al., U.S. Pat. No. 4,677,466 to Lert, et al., U.S. Pat. No. 5,512,933 to Wheatley, et al., U.S. Pat. No. 4,955,070 to Welsh, et al., U.S. Pat. No. 4,918,730 to Schulze, U.S. Pat. No. 4,843,562 to Kenyon, et al., U.S. Pat. No. 4,450,551 to Kenyon, et al., U.S. Pat. No. 4,230,990 to Lert, et al., U.S. Pat. No. 5,594,934 to Lu, et al., European Published Patent Application EP 0887958 to Bichsel, PCT Publication WO02/11123 to Wang, et al. and PCT publication WO91/11062 to Young, et al., all of which are incorporated herein by reference in their entireties. As discussed above, the code detection and/or signature extraction serve to identify and determine media exposure for the user of device 700.

Memory 708 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 708 by other components of the device 700, such as processor 703, decoder 710 and peripherals interface 704, may be controlled by the memory controller 702. Peripherals interface 704 couples the input and output peripherals of the device to the processor 703 and memory 708. The one or more processors 703 run or execute various software programs and/or sets of instructions stored in memory 708 to perform various functions for the device 700 and to process data. In some embodiments, the peripherals interface 704, processor(s) 703, decoder 710 and memory controller 702 may be implemented on a single chip, such as a chip 701. In some other embodiments, they may be implemented on separate chips.

The RF (radio frequency) circuitry 705 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 705 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 705 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 705 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and/or Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS)), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 706, speaker 720, and microphone 721 provide an audio interface between a user and the device 700. Audio circuitry 706 may receive audio data from the peripherals interface 704, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 720. The speaker 720 converts the electrical signal to human-audible sound waves. Audio circuitry 706 also receives electrical signals converted by the microphone 721 from sound waves, which may include encoded audio, described above. The audio circuitry 706 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 704 for processing. Audio data may be retrieved from and/or transmitted to memory 708 and/or the RF circuitry 705 by peripherals interface 704. In some embodiments, audio circuitry 706 also includes a headset jack for providing an interface between the audio circuitry 706 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 711 couples input/output peripherals on the device 700, such as touch screen 715 and other input/control devices 717, to the peripherals interface 704. The I/O subsystem 711 may include a display controller 712 and one or more input controllers 714 for other input or control devices. The one or more input controllers 714 receive/send electrical signals from/to other input or control devices 717. The other input/control devices 717 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 714 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse, an up/down button for volume control of the speaker 720 and/or the microphone 721. Touch screen 715 may also be used to implement virtual or soft buttons and one or more soft keyboards.

Touch screen 715 provides an input interface and an output interface between the device and a user. The display controller 712 receives and/or sends electrical signals from/to the touch screen 715. Touch screen 715 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects. Touch screen 715 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 715 and display controller 712 (along with any associated modules and/or sets of instructions in memory 708) detect contact (and any movement or breaking of the contact) on the touch screen 715 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 715 and the user corresponds to a finger of the user. Touch screen 715 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. Touch screen 715 and display controller 712 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen 712.

Device 700 may also include one or more sensors 716 such as optical sensors that comprise charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensor may capture still images or video, where the sensor is operated in conjunction with touch screen display 715. Device 700 may also include one or more accelerometers 707, which may be operatively coupled to peripherals interface 704. Alternately, the accelerometer 707 may be coupled to an input controller 714 in the I/O subsystem 711. The accelerometer is preferably configured to output accelerometer data in the x, y, and z axes.

In some embodiments, the software components stored in memory 708 may include an operating system 709, a communication module 710, a contact/motion module 713, a text/graphics module 711, a Global Positioning System (GPS) module 712, and applications 714. Operating system 709 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. Communication module 710 facilitates communication with other devices over one or more external ports and also includes various software components for handling data received by the RF circuitry 705. An external port (e.g., Universal Serial Bus (USB), Firewire, etc.) may be provided and adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.

Contact/motion module 713 may detect contact with the touch screen 715 (in conjunction with the display controller 712) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 713 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred, determining if there is movement of the contact and tracking the movement across the touch screen 715, and determining if the contact has been broken (i.e., if the contact has ceased). Text/graphics module 711 includes various known software components for rendering and displaying graphics on the touch screen 715, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like. Additionally, soft keyboards may be provided for entering text in various applications requiring text input. GPS module 712 determines the location of the device and provides this information for use in various applications. Applications 714 may include various modules, including address books/contact list, email, instant messaging, video conferencing, media player, widgets, instant messaging, camera/image management, and the like. Examples of other applications include word processing applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

Turning to FIG. 7, embodiments are disclosed for utilizing wireless signals to configure wireless devices, preferably in the area of public places, such as shopping malls, stores, public events, and the like, for gathering research data. In one embodiment, public area 860 comprises at least one higher-range antenna 853 (e.g., class 1, up to 100 meters), together with a plurality of lower-range antennas 854, 855 (e.g., class 2, up to 30 meters) that are communicatively coupled to processor 852. Processor 852 may be a dedicated server, a terminal coupled to one or servers in network 855, or any other suitable device. Processor 852 is capable of sending/receiving data through any or all antennas 853-855. Preferably, processor 852 is configured to independently send and/or receive data through all connected antennas. Processor 852 may further send and/or receive data from network 855 via a dedicated connection such as TCP/IP.

Preferably, each antenna (transmitter/transceiver) in FIG. 7 supplies its own piconet for connecting devices, and the antennas may be operatively coupled together to form one or more scatternets in area 860. Each device initiates its own entry into an existing piconet by forming a scatternet with the master. Cross-piconet communication can take place without requiring devices to periodically disconnect from one piconet and reconnect to the other. Devices can also participate in store-and-forward messaging, effectively removing any Bluetooth range limits if enough devices are available to relay data. When operating in a scatternet, devices may multiplex between piconets to prevent timeouts. If a device is involved only in ACL traffic across piconets, it can use sniff, hold and park low-power modes to divide its attention between different piconets. If a slave device is a member of two or more piconets, an offsetting sniff interval (e.g., every X slots) may be used to multiplex traffic between piconets. This sniff interval would enable symmetric switching to allow a device to divide its time between different piconets. Additionally a predetermined hold time may be implemented for active piconet connections so that the device could sniff and connect with other piconets.

Instead of using sniff intervals to multiplex between piconets, devices may use the hold and park modes between piconets, although the hold mode may slow switching rates between piconets as this would require a device to hold an active piconet and renegotiate a hold in another piconet before returning to exchange more ACL packets. Preferably, a park mode is used for scatternet members, as this mode provides greater versatility for monitoring piconets for unpark commands and other broadcast packets, and may skip several beacon trains by utilizing a sleep time interval (NBsleep) that is a multiple of beacon interval lengths. This effectively allows a device to offset beacon monitoring times, similar to the sniff mode discussed above. Alternately, a device (acting as a slave in the scatternet), can simply ignore each piconet in turn without informing the respective masters of its temporary exit; as long as the timeout periods are not exceeded, the links should be maintained under normal operating conditions

During a set-up process, each of antennas 853-855 are provided a unique identification or hash that is communicated each time a wireless connection is made with a device (e.g., via module 705 illustrated in FIG. 6). Device 851A preferably stores a list of antenna ID's 856, that may be supplied via a wireless global “push,” or alternately provided by a local wireless source, such as long-range antenna 853. ID information 856 may be used by device 851A to identify specific antennas for adjusting operational characteristics. For the purposes of clarification, FIG. 7 illustrates an example of a device (851) being carried through an area 860 at four discreet locations, involving four different events; each of these locations/events for the device are designated as 851A-851D, respectively. It is understood that, in addition to receiving a wireless signal and ID, additional information may be provided in the wireless signal, such as messages or commands. Each antenna may have specific messages or commands that may be sent to the device and processed within the device to modify the operational characteristics described herein.

In the embodiment of FIG. 7, device 851A is physically carried by a user through public area 860. Prior to entering area 860, device 851A is arranged to have a default configuration where, in one embodiment, a predetermined wireless scan rate is set (e.g., once every 5 minutes) and an audio capture capabilities are set to “OFF.” As device 851A approaches area 860, it comes into communication range with long-range antenna 853. In the case of Bluetooth communication, antenna 853 is configured to be the master. Once initial communication is established, antenna 853 transmits its ID to device 851A, and the ID is compared to a stored ID to determine if there is a match. Once the ID is matched, this triggers device 851A to update scanning intervals to a higher frequency (e.g., once every 30 seconds) as device 851A enters area 860. Once inside area 860, the device moves to 851B, where it now establishes communication with antenna 854, where it may now form a scatternet together with antenna 853. Again, if the ID for antenna 854 is matched, a new operation may be triggered or an existing operation may be further updated. In this example, the ID received from antenna 854 causes device 851B to activate processes on the device via software and/or hardware. In one embodiment, audio processing is activated (e.g., via DSP/decoder 710 and microphone 721 of FIG. 6) to activate audio processing on the device to detect ancillary code in audio and/or extract audio signatures. Such a configuration is particularly advantageous in an area where detection of audio media exposure is important; once the activation is completed, device 851B is able to collect research data pertaining to audio 856 or an audio component of other media in the vicinity of 854. Additionally, environmental audio signatures may be extracted to establish and/or confirm the location of device 851B. Techniques for collecting and processing environmental audio signatures is described in U.S. patent application Ser. No. 13/341,453, titled “System and Method for Determining Contextual Characteristics of Media Exposure Data” filed Dec. 30, 2011, which is assigned to the assignee of the present application and is incorporated by reference in its entirety herein.

As device approaches 851C, it next establishes communication with antenna 855 and receives the antenna ID. If the ID matches, device 851C further updates the operating characteristics. In this example, the ID match may trigger device 851C to turn off audio monitoring. Additionally, the ID match from 855 may further update the scanning mode of device 851C to scan for wireless connections more or less frequently. As device 851D moves outside area 860, it eventually loses its wireless connection to the antennas and as a result, reverts back to a default mode of operation.

Turning to FIG. 8, an exemplary flowchart is provided, where, after a portable device powers up, the process begins at 900. At this point, the portable device is preferably set to a default configuration, where a wireless network scan rate is set to a default rate 901. The device periodically monitors to see if the device has receives a beacon or signal in 902, where, if no beacon or signal is received, the device retains its default scan rate 901. However, once a beacon or signal is detected, the scan rate is updated in 903 to a more or less frequent rate. Additionally or alternately, the detection of a beacon or signal in 902 may activate the devices DSP and/or microphone capabilities in 907, where the device would begin an audio monitoring process utilizing codes and/or signatures, described above.

As the scan rate is updated in 903, the device continues to monitor if a new beacon or signal is received in 904. If a new beacon or signal is not received, the device checks to see if the original beacon is being received in 905. If the original beacon or signal is not being received, the device reverts back to a default scan rate in 901. However, if the original beacon or signal is still being received, the device maintains the updated scan rate (903) and continues to monitor for new beacons or signals. As an example, device 851A of FIG. 7 may establish a connection with long-range antenna 853 while moving past area 860, but the device does not enter area 860. As a result, no further connections will be made with antennas 854-855. Once device 851A moves outside the communication range of 853, the beacon or signal will be lost and device 851A simply reverts back to its default mode of operation. However, as device 851A enters area 860, it is possible for device 851A to be in a section of area 860 that does not contain shorter-range antennas, or is not yet within range of antennas 854 or 855. In such a case, the device will maintain the updated scan rate until a new beacon or signal is received. Once a new beacon or signal is received in 904 (e.g., from antenna 854), the scan rate is updated again in 906 and further data may be collected. This process may repeat for each new beacon or signal (e.g. 855) until the device exits the area and no beacons or signals are detected.

In step 902, a detected beacon or signal may also activate the device's DSP and/or microphone 907 whereupon the device begins reading ancillary code or extracting signatures from audio 908. If a new beacon or signal is detected in 909 (note: the beacon or signal in 909 may be the same beacon or signal as 904), the audio monitoring configuration is updated in 910. In one embodiment, the audio monitoring update may involve such actions as (1) modifying the characteristics of code detection (e.g., frequencies used, timing, etc.), (2) switching the monitoring from detecting code to extracting signatures and vice versa, (3) switching the method of code detection from one type to another (e.g., from CBET decoding to spread-spectrum, from echo-hiding to wavelet, etc.), (4) switching the method of signature extraction from one type to another (e.g., frequency-based, time-based, a combination of time and frequency), and/or (5) providing supplementary data that is correlated to the audio monitoring (e.g., location, other related media in the location, etc.). Similar to the scanning portion described above, if no additional beacons are detected in 909, the device looks to see if the original beacon or signal is being received. If not, the device reverts back to its original configuration and may turn off audio monitoring. If the original beacon is signal is still being detected, the device maintains its current (updated) audio monitoring configuration and continues to monitor for new beacons or signals. Also, the process for audio monitoring repeats for each new beacon or signal no beacons or signals are detected.

It is understood that the embodiments described above are mere examples, and that the disclosed configurations allow for a multitude of variations. For example, the ID detection may be combines with signal strength measurements described above to allow additional modifications, where scan rates may be incrementally increased or decreased as the signal strength becomes stronger or weaker. Also, scan rates and/or audio monitoring may be triggered only when signal strength exceeds a predetermined threshold. Furthermore, device triggers may be made dependent upon combinations of antenna connections. Thus, connections to a 1st and 2nd beacon would produce one modification on the device, while a connection to a 1st, 2nd and 3rd beacon would produce a new, alternate or additional modification. If the connection to the 2nd beacon is lost (leaving a connection only with the 1st and 3rd beacon), yet another new, alternate or additional modification could be produced. Many such variations may be made under the present disclosure, depending on the needs of the system.

Furthermore, while the exemplary embodiments provided above were discussed in the context of Bluetooth, one skilled in the art would understand that the configurations could be adapted to other wireless technologies as well. For example, Wi-Fi or other technologies compatible with the IEEE 802.11 standard may be used as well. While at least one example embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the example embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient and edifying road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope of the invention and the legal equivalents thereof.

Claims

1. A portable device comprising:

a microphone;
radio frequency circuitry to scan for a first radio frequency beacon at a first scanning rate, the radio frequency circuitry to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon; and
a processor to trigger activation of audio monitoring, in the portable device, of an audio signal obtained via the microphone, the processor to trigger the audio monitoring in response to the first connection being made via the radio frequency circuitry with the first transmitter of the first radio frequency beacon, the audio monitoring to collect research data from the audio signal, the processor to update the audio monitoring in response to a second connection being made via the radio frequency circuitry with a second transmitter of a second radio frequency beacon.

2. The portable device of claim 1, wherein the processor is to update the audio monitoring to have a first configuration in response to the second connection being made with the second transmitter of the second radio frequency beacon without the first connection with the first transmitter of the first radio frequency beacon being lost, and the processor is to update the audio monitoring to have a second configuration different from the first configuration in response to the first connection with the first transmitter of the first radio frequency beacon being lost and the second connection with the second transmitter of the second radio frequency beacon being present.

3. The portable device of claim 2, wherein the audio monitoring includes at least one of detection of codes in the audio signal or generation of signatures from the audio signal, the first configuration is to specify at least one of a first type of code detection method or a first type of signature generation method to be performed on the audio signal, and the second configuration is to specify at least one of a second type of code detection method or a second type of signature generation method to be performed on the audio signal.

4. The portable device of claim 1, wherein the radio frequency circuitry is to scan at a second scanning rate different from the first scanning rate after the first connection is made with the first transmitter of the first radio frequency beacon.

5. A portable device comprising:

a microphone;
radio frequency circuitry to scan for a first radio frequency beacon at a first scanning rate, the radio frequency circuitry to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon; and
a processor to trigger activation of audio monitoring, in the portable device, of an audio signal obtained via the microphone, the processor to trigger the audio monitoring in response to the first connection being made via the radio frequency circuitry with the first transmitter of the first radio frequency beacon, the audio monitoring to collect research data from the audio signal, the processor to turn off the audio monitoring in response to a second connection being made via the radio frequency circuitry with a second transmitter of a second radio frequency beacon.

6. A portable device comprising:

a microphone;
radio frequency circuitry to scan for a first radio frequency beacon at a first scanning rate, the radio frequency circuitry to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon; and
a processor to trigger activation of audio monitoring, in the portable device, of an audio signal obtained via the microphone, the processor to trigger the audio monitoring in response to the first connection being made via the radio frequency circuitry with the first transmitter of the first radio frequency beacon, the audio monitoring to collect research data from the audio signal, the processor to turn off the audio monitoring in response to the first connection with the first transmitter of the first radio frequency beacon being lost.

7. A portable apparatus comprising:

means for sensing an audio signal;
means for scanning for a first radio frequency beacon at a first scanning rate, the means for scanning to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon; and
means for performing audio monitoring of the audio signal, the means for performing audio monitoring to trigger activation of the audio monitoring of the audio signal in response to the first connection being made with the first transmitter of the first radio frequency beacon, the audio monitoring to collect research data from the audio signal, the audio monitoring including at least one of detection of codes in the audio signal or generation of signatures from the audio signal, the means for performing audio monitoring to update the audio monitoring to have a first configuration in response to a second connection being made with a second transmitter of a second radio frequency beacon without the first connection with the first transmitter of the first radio frequency beacon being lost, the means for performing audio monitoring to update the audio monitoring to have a second configuration different from the first configuration in response to the first connection with the first transmitter of the first radio frequency beacon being lost and the second connection with the second transmitter of the second radio frequency beacon being present, the first configuration to specify at least one of a first type of code detection method or a first type of signature generation method to be performed on the audio signal, and the second configuration to specify at least one of a second type of code detection method or a second type of signature generation method to be performed on the audio signal.

8. The apparatus of claim 7, wherein the means for scanning is to scan at a second scanning rate different from the first scanning rate after the first connection is made with the first transmitter of the first radio frequency beacon.

9. A portable apparatus comprising:

means for sensing an audio signal;
means for scanning for a first radio frequency beacon at a first scanning rate, the means for scanning to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon; and
means for performing audio monitoring of the audio signal, the means for performing audio monitoring to triggering activation of the audio monitoring of the audio signal in response to the first connection being made with the first transmitter of the first radio frequency beacon, the audio monitoring to collect research data from the audio signal, the means for performing audio monitoring to turn off the audio monitoring in response to the first connection with the first transmitter of the first radio frequency beacon being lost.

10. The apparatus of claim 9, wherein the means for performing audio monitoring is to turn off the audio monitoring in response to a second connection being made with a second transmitter of a second radio frequency beacon.

11. A computer readable storage device or storage disk comprising computer readable instructions which, when executed, cause a processor of a portable device to at least:

configure radio frequency circuitry of the portable device to scan for a first radio frequency beacon at a first scanning rate;
configure the radio frequency circuitry to continue to scan at a second scanning rate different from the first scanning rate after a first connection is made with a first transmitter of the first radio frequency beacon;
trigger activation of audio monitoring of an audio signal in response to the first connection being made with the first transmitter of the radio frequency beacon, the audio signal obtained by the portable device;
perform the audio monitoring of the audio signal obtained by the portable device, the audio monitoring to collect research data from the audio signal, the audio monitoring including at least one of detection of codes in the audio signal or generation of signatures from the audio signal;
update the audio monitoring to have a first configuration in response to a second connection being made with a second transmitter of a second radio frequency beacon without the first connection with the first transmitter of the first radio frequency beacon being lost, the first configuration to specify at least one of a first type of code detection method or a first type of signature generation method to be performed on the audio signal; and
update the audio monitoring to have a second configuration different from the first configuration in response to the first connection with the first transmitter of the first radio frequency beacon being lost and the second connection with the second transmitter of the second radio frequency beacon being present, the second configuration to specify at least one of a second type of code detection method or a second type of signature generation method to be performed on the audio signal.

12. The computer readable storage device or storage disk of claim 11, wherein the instructions, when executed, cause the processor to configure the radio frequency circuitry to scan at a second scanning rate different from the first scanning rate after the first connection is made with the first transmitter of the first radio frequency beacon.

13. A computer readable storage device or storage disk comprising instructions which, when executed, cause a processor of a portable device to at least:

configure radio frequency circuitry of the portable device to scan for a first radio frequency beacon at a first scanning rate;
configure the radio frequency circuitry to continue to scan after a first connection is made with a first transmitter of the first radio frequency beacon;
trigger activation of audio monitoring of an audio signal in response to the first connection being made with the first transmitter of the radio frequency beacon, the audio signal obtained by the portable device;
perform the audio monitoring of the audio signal obtained by the portable device, the audio monitoring to collect research data from the audio signal; and
turn off the audio monitoring in response to the first connection with the first transmitter of the first radio frequency beacon being lost.

14. The computer readable storage device or storage disk of claim 13, wherein the instructions, when executed, further cause the processor to:

turn off the audio monitoring in response to a second connection being made with a second transmitter of a second radio frequency beacon.
Referenced Cited
U.S. Patent Documents
3919479 November 1975 Moon et al.
4230990 October 28, 1980 Lert, Jr. et al.
4626904 December 2, 1986 Lurie
4677466 June 30, 1987 Lert, Jr. et al.
4695879 September 22, 1987 Weinblatt
4697209 September 29, 1987 Kiewit et al.
4739398 April 19, 1988 Thomas et al.
4843562 June 27, 1989 Kenyon et al.
4918730 April 17, 1990 Schulze
4930011 May 29, 1990 Kiewit
4931865 June 5, 1990 Scarampi
4955070 September 4, 1990 Welsh et al.
4973952 November 27, 1990 Malec et al.
5218641 June 8, 1993 Abe et al.
5289526 February 22, 1994 Chymyck et al.
5382970 January 17, 1995 Kiefl
5406269 April 11, 1995 Baran
5450490 September 12, 1995 Jensen et al.
5451839 September 19, 1995 Rappaport et al.
5457807 October 10, 1995 Weinblatt
5481294 January 2, 1996 Thomas et al.
5483276 January 9, 1996 Brooks et al.
5490204 February 6, 1996 Gulledge
5512933 April 30, 1996 Wheatley et al.
5546444 August 13, 1996 Roach, Jr. et al.
5561835 October 1, 1996 Worthy
5574962 November 12, 1996 Fardeau et al.
5579124 November 26, 1996 Aijala et al.
5581800 December 3, 1996 Fardeau et al.
5612729 March 18, 1997 Ellis et al.
5623535 April 22, 1997 Leung et al.
5644623 July 1, 1997 Gulledge
5754956 May 19, 1998 Abreu et al.
5764763 June 9, 1998 Jensen et al.
5768680 June 16, 1998 Thomas
5781865 July 14, 1998 Gammon
5784442 July 21, 1998 Foti
5787334 July 28, 1998 Fardeau et al.
5794146 August 11, 1998 Sevcik
5822410 October 13, 1998 McCausland et al.
5826164 October 20, 1998 Weinblatt
5826186 October 20, 1998 Mitchell et al.
5839050 November 17, 1998 Baehr et al.
5896554 April 20, 1999 Itoh et al.
6006085 December 21, 1999 Balachandran
6049713 April 11, 2000 Tran et al.
6101175 August 8, 2000 Schorman et al.
6108637 August 22, 2000 Blumenau
6134544 October 17, 2000 Glitho et al.
6138020 October 24, 2000 Galyas et al.
6169896 January 2, 2001 Sant et al.
6212386 April 3, 2001 Briere et al.
6223031 April 24, 2001 Näslund
6329908 December 11, 2001 Frecksa
6421434 July 16, 2002 Rosu
6459371 October 1, 2002 Pike
6466783 October 15, 2002 Dahm et al.
6516189 February 4, 2003 Frangione et al.
6597671 July 22, 2003 Ahmadi et al.
6628953 September 30, 2003 Dillon et al.
6647548 November 11, 2003 Lu et al.
6717547 April 6, 2004 Spilker, Jr. et al.
6788926 September 7, 2004 Frangione et al.
6871180 March 22, 2005 Neuhauser
6934508 August 23, 2005 Ceresoli et al.
6999715 February 14, 2006 Hayter
6999766 February 14, 2006 Padovani
7013136 March 14, 2006 Frangione et al.
7130622 October 31, 2006 Vänskä et al.
7154398 December 26, 2006 Chen
7181159 February 20, 2007 Breen
7194281 March 20, 2007 Peng et al.
7203510 April 10, 2007 Tanoue
7340214 March 4, 2008 Hamberg
7395062 July 1, 2008 Tuccio
7409214 August 5, 2008 Lee
7471987 December 30, 2008 Crystal et al.
7486925 February 3, 2009 Breen
7505765 March 17, 2009 Frangione et al.
7627872 December 1, 2009 Hebeler et al.
7640141 December 29, 2009 Kolessar et al.
7734309 June 8, 2010 Chi et al.
7885239 February 8, 2011 Oroskar et al.
8175567 May 8, 2012 Hoefel
8275413 September 25, 2012 Fraden
8326290 December 4, 2012 Mortti
8417296 April 9, 2013 Caballero
8447293 May 21, 2013 Stapleton et al.
9502750 November 22, 2016 Yarga
9992729 June 5, 2018 Jain et al.
20020055924 May 9, 2002 Liming
20020087974 July 4, 2002 Sprague
20020102993 August 1, 2002 Hendrey et al.
20020129138 September 12, 2002 Carter
20020155831 October 24, 2002 Fodor et al.
20020174222 November 21, 2002 Cox
20030064722 April 3, 2003 Frangione et al.
20030065805 April 3, 2003 Barnes, Jr.
20030101451 May 29, 2003 Bentolila et al.
20030136827 July 24, 2003 Kaneko et al.
20030170001 September 11, 2003 Breen
20030235180 December 25, 2003 Oprescu-Surcobe et al.
20040019675 January 29, 2004 Hebeler, Jr. et al.
20040122727 June 24, 2004 Zhang et al.
20040142693 July 22, 2004 Feder et al.
20040202131 October 14, 2004 An et al.
20050043046 February 24, 2005 Lee
20050200476 September 15, 2005 Forr et al.
20050203798 September 15, 2005 Jensen et al.
20050243784 November 3, 2005 Fitzgerald et al.
20050287954 December 29, 2005 Lim et al.
20060023642 February 2, 2006 Roskowski
20060089153 April 27, 2006 Sheynblat
20060107195 May 18, 2006 Ramaswamy et al.
20060270401 November 30, 2006 Frangione et al.
20060284981 December 21, 2006 Erol et al.
20070011268 January 11, 2007 Banga et al.
20070041344 February 22, 2007 Yaqub et al.
20070058678 March 15, 2007 Thompson, III et al.
20070060084 March 15, 2007 Thompson, III et al.
20070193438 August 23, 2007 Asukai
20070243864 October 18, 2007 Jaquet
20080109295 May 8, 2008 McConochie et al.
20080262901 October 23, 2008 Banga et al.
20080299910 December 4, 2008 Petersen et al.
20090169024 July 2, 2009 Krug et al.
20090171767 July 2, 2009 Kolessar
20090187463 July 23, 2009 DaCosta
20090187593 July 23, 2009 Chen et al.
20090197582 August 6, 2009 Lewis et al.
20090254975 October 8, 2009 Turnbull et al.
20090258669 October 15, 2009 Nie
20090298514 December 3, 2009 Ullah
20090311966 December 17, 2009 Stapleton et al.
20100169904 July 1, 2010 Nielsen et al.
20100195837 August 5, 2010 Srinivasan et al.
20100222687 September 2, 2010 Thijs
20100228677 September 9, 2010 Houston
20100268540 October 21, 2010 Arshi et al.
20100291880 November 18, 2010 Feldstein
20100317371 December 16, 2010 Westerinen et al.
20110099142 April 28, 2011 Karjalainen et al.
20110126222 May 26, 2011 Wright et al.
20110261257 October 27, 2011 Terry et al.
20110264663 October 27, 2011 Verkasalo
20110286632 November 24, 2011 Tuxen
20110312308 December 22, 2011 Willey
20120003933 January 5, 2012 Baker
20120029345 February 2, 2012 Mahfouz
20120045994 February 23, 2012 Koh
20120047011 February 23, 2012 Rippetoe et al.
20120144076 June 7, 2012 Yang
20120245978 September 27, 2012 Jain et al.
20120290360 November 15, 2012 Zhang et al.
20120321101 December 20, 2012 Lee
20130035979 February 7, 2013 Tenbrock
20130103810 April 25, 2013 Papakipos
20130107732 May 2, 2013 O'Donnell et al.
20130125183 May 16, 2013 Gomez et al.
20130183926 July 18, 2013 Lindberg et al.
20130204999 August 8, 2013 Lindberg
20130205311 August 8, 2013 Ramaswamy et al.
20130262184 October 3, 2013 Jain et al.
20130290234 October 31, 2013 Harris
20130308506 November 21, 2013 Kim
20140018034 January 16, 2014 Lindberg
20140111698 April 24, 2014 Jain et al.
20140113557 April 24, 2014 Jain et al.
20140187268 July 3, 2014 Browne et al.
20140289611 September 25, 2014 Norwood
20140355588 December 4, 2014 Cho
20160191619 June 30, 2016 Wang
20160292461 October 6, 2016 Yan
20160374608 December 29, 2016 Dugan
Foreign Patent Documents
1629870 June 2005 CN
1965335 May 2007 CN
231427 December 1987 EP
895435 February 1999 EP
1011283 June 2000 EP
1026847 August 2000 EP
1133090 September 2001 EP
1892638 February 2008 EP
2426153 November 2006 GB
9312870 December 1997 JP
101071540 October 2011 KR
9111062 July 1991 WO
9533352 December 1995 WO
9641492 December 1996 WO
9833344 July 1998 WO
9837724 August 1998 WO
9853621 November 1998 WO
0072289 November 2000 WO
0072309 November 2000 WO
0205577 January 2002 WO
0211123 February 2002 WO
03077455 September 2003 WO
2007044356 April 2007 WO
2008008899 January 2008 WO
2008118119 October 2008 WO
2009046430 April 2009 WO
2011103660 September 2011 WO
2011161303 December 2011 WO
2014065903 May 2014 WO
Other references
  • International Searching Authority, “International Search Report and Written Opinion”, mailed in connection with International Application No. PCT/US2013/049120, dated Dec. 5, 2013 (16 pages).
  • Dolcera Wiki, “CDMA Basics,” Jul. 29, 2007, retrieved from <http://www.dolcera.com/wiki/index.php?title-CDMA_Basics>, on Feb. 21, 2008 (9 pages).
  • Geckobeach, “How to Interpret the Cellular/Mobile Equipment Maps,” Feb. 21, 2008, retrieved from <http://www.geckobeach.com/cellular/maps/mapfaqs.php>, on Feb. 21, 2008 (4 pages).
  • Google, “Google Announces Launch of Google Maps for Mobile with ‘My Location’ Technology,” Nov. 28, 2007, retrieved from <http://www.google.com/intl/en/press/annc/20081128_maps_mobile_my_loca-tion_technology> on Feb. 28, 2008 (1 page).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/731,882, dated Aug. 10, 2015 (32 pages).
  • Canadian Intellectual Property Office, “Office Action”, mailed in connection with Canadian Patent Application No. 2,875,286, dated Dec. 17, 2015 (4 pages).
  • International Searching Authority, “International Preliminary Report on Patentability”, mailed in connection with International Patent Application No. PCT/US2013/049120, dated Jun. 2, 2015 (10 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action,” mailed in connection with U.S. Appl. No. 13/729,889, dated Jan. 14, 2015 (25 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Jul. 25, 2014 (14 pages).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Dec. 29, 2014 (18 pages).
  • Kolessar et al., “Portable People Meters, A Report On The Large Scale Field Test of Portable People Meters In Manchester, England,” 2000 (18 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action”, mailed in connection with U.S. Appl. No. 13/731,882, dated Jan. 14, 2015 (31 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action”, mailed in connection with U.S. Appl. No. 13/729,889, dated Jan. 23, 2015 (27 pages).
  • United States Patent and Trademark Office, “Final Office Action”, mailed in connection with U.S. Appl. No. 13/729,889, dated Jul. 14, 2015 (50 pages).
  • European Patent Office, “European Search Report”, mailed in connection with European Patent Application No. 13848606.3, dated Jun. 13, 2016 (14 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action”, mailed in connection with U.S. Appl. No. 13/731,882, dated Sep. 15, 2016 (46 pages).
  • Canadian Patent Office, “Office Action”, mailed in connection with Canadian Patent Application No. 2,875,286, dated Nov. 23, 2016 (3 pages).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/731,882, dated Feb. 24, 2017 (42 pages).
  • United States Patent and Trademark Office, “Non-Final Office Action,” mailed in connection with U.S. Appl. No. 13/729,889, dated May 19, 2016 (43 pages).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/729,889, dated Nov. 14, 2016 (34 pages).
  • The State Intellectual Property Office of China, “First Notification of Office Action,” mailed in connection with Chinese Patent Application No. 201380029274.7, dated Feb. 14, 2018 (12 pages).
  • European Patent Office, “Communication under Rule 71(3) EPC,” mailed in connection with European Patent Application No. 13848606.3, dated Aug. 7, 2018 (42 pages).
  • United States Patent and Trademark Office, “Notice of Allowance,” mailed in connection with U.S. Appl. No. 13/657,380, dated Jan. 26, 2018 (8 pages).
  • United States Patent and Trademark Office, “Notice of Allowance,” mailed in connection with U.S. Appl. No. 13/657,380, dated Sep. 29, 2017 (9 pages).
  • United States Patent and Trademark Office, “Notice of Allowance,” mailed in connection with U.S. Appl. No. 13/657,380, dated Apr. 6, 2017 (8 pages).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Apr. 21, 2016 (21 pages).
  • United States Patent and Trademark Office, “Non-final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Aug. 27, 2015 (20 pages).
  • United States Patent and Trademark Office, “Final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Dec. 29, 2014 (19 pages).
  • United States Patent and Trademark Office, “Non-final Office Action,” mailed in connection with U.S. Appl. No. 13/657,380, dated Jul. 25, 2014 (15 pages).
  • State Intellectual Property Office of China, “Second Notification of Office Action,” mailed in connection with Chinese Patent Application No. 201380029274.7, dated Nov. 2, 2018, 7 pages.
  • State Intellectual Property Office of China, “Notice of Decision of Granting Patent Right for Invention,” issued in connection with Chinese Patent Application No. 201380029274.7, dated Feb. 20, 2019, 5 pages.
Patent History
Patent number: 10631231
Type: Grant
Filed: Jun 4, 2018
Date of Patent: Apr 21, 2020
Patent Publication Number: 20180288677
Assignee: The Nielsen Company (US), LLC (New York, NY)
Inventors: Anand Jain (Ellicott City, MD), John Stavropoulos (Edison, NJ), Alan Neuhauser (Silver Spring, MD), Wendell Lynch (East Lansing, MI), Vladimir Kuznetsov (Ellicott City, MD), Jack Crystal (Owings Mills, MD), David Gish (Riverdale, NJ)
Primary Examiner: Edward F Urban
Assistant Examiner: Max Mathew
Application Number: 15/997,391
Classifications
Current U.S. Class: Control Or Access Channel Scanning (455/434)
International Classification: H04B 7/00 (20060101); H04W 48/04 (20090101); H04N 21/00 (20110101); H04M 1/725 (20060101); H04M 1/60 (20060101); G06Q 30/02 (20120101);