The present disclosure pertains to audience measurement and, more particularly, to portable audience measurement architectures and methods for portable audience measurement.
Determining a size and demographics of a television viewing audience helps television program producers improve their television programming and determine a price to be charged for advertising that is broadcasted during such programming. In addition, accurate television viewing demographics allow advertisers to target audiences of a desired size and/or audiences comprising members having a set of common, desired characteristics (e.g., income level, lifestyles, interests, etc.).
In order to collect these demographics, an audience measurement company may enlist a number of television viewers (e.g., panelists) to cooperate in an audience measurement study for a predefined length of time. The viewing habits of these enlisted viewers, as well as demographic data about these enlisted viewers, are collected using automated and/or manual collection methods. The collected data is subsequently used to generate a variety of informational statistics related to television viewing audiences including, for example, audience sizes, audience demographics, audience preferences, the total number of hours of television viewing per household and/or per region, etc.
The configurations of audience measurement systems vary depending on the equipment used to receive, process, and display television signals in each home being monitored. For example, homes that receive cable television signals and/or satellite television signals typically include a set top box (STB) to receive television signals from a cable and/or a satellite television provider. Television systems configured in this manner are typically monitored using hardware, firmware, and/or software to interface with the STB to extract or to generate signal information therefrom. Such hardware, firmware, and/or software may be adapted to perform a variety of monitoring tasks including, for example, detecting the channel tuning status of a tuning device disposed in the STB, extracting program identification codes embedded in television signals tuned by the STB, generating signatures characteristic of television signals tuned by the STB, etc. The collected viewing and demographic data may then be transmitted to a data collection facility for processing.
Traditional audience measurement systems have employed a client/server architecture with the client (e.g., a metering device) and server (e.g., a data collection unit to collect data from the metering device) being in fixed physical locations. For example, in a typical system, the client is located in a room in an enlisted viewer's residence and there may be a need for multiple clients if additional rooms in the enlisted viewer's residence are to be monitored. The server is typically located in an off-site location away from the enlisted viewer's residence. Also, each client is assigned to a specific data collection server so that, even in the case of a portable client (e.g., a metering device), data collected by the metering device is always exported to the same data collection server.
Typically, metering devices (e.g., a Peoplemeter) communicate with media devices (e.g., devices to be measured such as a TV, STB, etc.) to measure usage of the media devices. The metering devices accumulate the viewing and demographic data and typically use a proprietary data transfer protocol to communicate with a dedicated data collection unit. The proprietary data transfer protocol is non-extensible.
The media device 106 may be any device that is to be measured by the audience measurement architecture disclosed herein. As described above, the media device 106 may be a television and/or an audio system, but may also include a STB, a video game console or system, advertisements, and/or a personal computer.
The viewing area 102, as shown in
The portable measurement devices 108a and 108b are devices to collect audience measurement data from media devices 106. Preferably, the portable measurement devices 108a and 108b are designed to be worn or otherwise carried by the household members 104. The portable measurement devices 108a and 108b may use well known techniques to collect the audience measurement data such as audio code capture techniques and/or audio signature capture techniques. The portable metering devices 108a and 108b may also be configured to capture program identification code information or collect audience measurement data using any other method known to a person of ordinary skill in the art. The collected audience measuring data may be stored in any type of storage device 320 (
The portable measurement devices 108a and 108b are also configured to have wireless communication capabilities using an extensible data transport protocol 112 such as Extensible Markup Language (XML) and may also have the capabilities of discovering other portable measurement devices 108 and/or data collection servers 110a, 110b, and/or 110c that are within a predetermined distance of the portable measurement devices 108a and 108b (e.g., a communication range). The wireless communication may be implemented using any wireless protocol such as Bluetooth, 802.11b, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), etc.
The data collection servers 110a, 110b, and 110c may be any device configured to collect audience measurement data from any portable measurement device 108a or 108b from a plurality of portable measurement devices. The data collection servers 110a, 110b, and 110c are configured to communicate with any portable measurement device 108a or 108b from a plurality of portable measurement devices in a peer-to-peer manner using any wireless communication protocol and/or standard. The data collection servers 110a, 110b, and 110c may be located anywhere (e.g., in a viewing area 102, in a home, outside of a home, in a restaurant, in a bar, outside, on a telephone pole or a cellular phone tower, etc.) and are situated to receive and store the audience measurement data from the portable measuring devices 108a and 108b. The data collection servers 110a, 110b, and 110c are typically stationary servers configured to communicate with the central data processing server 116 and a plurality of portable measurement devices (e.g., portable measurement devices 108a and 108b). The geographical location and the communication range of each data collection server 110a, 110b, and 110c may be known by the central data processing server 116 and the geographical location/proximity of a portable measurement device 108a and/or 108b may be determined from the reporting data collection server's location. For example, if the central data processing server 116 receives data from data collection server 110a, it may determine that portable measurement device 108a has been in the geographical or network proximity of the data collection server 110a. When the portable measurement devices 108a and 108b are within the communication range of at least one of the data collection servers 110a, 110b, and 110c, a communication link (e.g., a network connection) is established via the communication protocol 112 and the portable measurement devices 108a and 108b may transmit audience measurement data to the data collection server 110a, 110b, and 110c. The data collection servers 110a, 110b, and 110c may process, store, and/or transmit the audience measurement data to the central data processing server 116 via the network connection 114. The data collection servers 110a, 110b, and 110c may also be configured to detect the portable measurement devices 108a and 108b and indicate the data collection servers' ability to receive audience measurement data.
The portable measurement devices 108a and 108b may detect the data collection servers 110 (e.g., the data collection servers 110a, 110b, 110c, and/or other data collection servers not shown in
The communication protocol 112 may be any extensible data transport protocol such as XML and/or XML Web Services. In the illustrated example, the communication protocol 112 is a non-proprietary protocol that allows devices such as the data collection servers 110a, 110b, and 110c and the portable measurement devices 108a and 108b to communicate with one another in a global or localized manner (e.g. a peer-to-peer network). The communication protocol 112 may be implemented via a wireless network protocol such as Bluetooth, 802.11b and/or an infrared (IR) connection.
The network connection 114 may be implemented using any type of public or private network such as, but not limited to, the Internet, an intranet, a telephone network, a local area network (LAN), a cable network, and/or a wireless peer-to-peer network. The network connection 114 allows for the data collection servers 110a, 110b, and 110c to communicate with one another, with the central data processing server 116 and/or with other devices which may be connected through the network connection 114 such as a personal computer.
The central data processing server 116 is a device that collects audience measurement data from the data collection servers 110a, 110b, and 110c via the network connection 114. The central data processing server 116 may store and/or process the data received from the data collection servers 110a, 110b, and 110c. Typically, the central data processing server 116 processes the received data into reports that may be sold to interested parties.
A typical scenario in which a portable measurement device 108a or 108b is used may be similar to the following example. In this example, it is assumed that the viewing area 102 is a room in a house, including a television 106, and the portable measurement device 108a is associated with the viewing area 102. It is also assumed the portable measurement device 108a is configured to collect audience measurement data from the television 106.
The household member 104 watching the television 106 places the portable measurement device 108a in the viewing area 102. The portable measurement device 108a collects signatures of television programs and/or advertisements shown on the television 106 and/or codes broadcast with the television program and/or advertisements. Subsequently, the household member 104, may move the portable measurement device 108a to a first location outside of the viewing area 102 such as a second room in the house containing a data collection server 110a. If so, the portable measurement device 108a may detect the data collection server 110a and may determine that enough audience measurement data has been collected. If so, it uploads the audience measurement data to the data collection server 110a. The data collection server 110a may communicate with the portable measurement device 108a when the portable measurement device 108a is present in the house (irrespective of which room) and within the communication range of the data collection server 110a. This may be implemented by a wireless network in the house which is well known to those of ordinary skill in the art. The data collection server 110a may be able to use a signal strength from the portable measurement device 108a to determine where in the house the portable measurement device 108a is located.
Subsequently, the household member 104 may carry the portable measurement device 108a back to the viewing area 102. The portable measurement device 108a then collects additional audience measurement data from the television 106. The household member 104 may then carry the portable measurement device 108a to a second location outside of the viewing area 102, such as a grocery store. If the second location (or a location between the first and second location (e.g., a telephone pole on the street or in a parking lot) contains a data collection server 110b, the portable measurement device 108a may detect the data collection server 110b and upload the audience measurement data to the data collection server 110b if a predetermined amount of audience measurement data has been collected.
In general, the example process 200 begins when a portable measurement device 108 (e.g., the portable measurement devices 108a and/or 108b of
More specifically, the process 200 of
After the audience measurement data has been collected by the portable measurement device 108a, a household member 104 may carry the portable measurement device 108a or the portable measurement device 108a may be otherwise moved to a new location (e.g., outside the home, into a separate room, etc.) (block 204). In the example of
Irrespective of the location of the server 110a, when the portable measurement device 108a detects the lost communication link 112, it attempts to establish a wireless communication link (e.g., discovered) with any available data collection server 110a by broadcasting a query message (block 206). The data collection server 110a may be discovered through commonly known protocols and/or the network identity of the collection servers 110a (e.g., a domain name and/or an Internet protocol address) may be stored in the portable measurement device 108a. The query message is transmitted using a communication protocol 112 as described above. The query message may be a message publishing the portable measurement device's capabilities (e.g., a wireless communication protocol, collecting audience measurement data, ability to transfer the collected audience measurement data, etc.) or a message searching for a network to join.
If a data collection server 110a, 110b, and 110c is in the communication range of the portable measurement device 108a and receives the query message, the data collection server 110a, 110b, and 110c responds and a wireless communication link is established between the data collection server 110a, 110b, and 110c and the portable measurement device 108a (block 208). The portable measurement device 108a then transfers the collected audience measurement data to the data collection server 110a, 110b, and 110c (block 210) using the communication protocol 112. Control then returns to block 210.
Although not shown in
Returning to block 208, if no data collection server 110 responds to the query message (block 208), the portable measurement device 108a waits a predetermined amount of time (block 212). The predetermined amount of time may be dynamically adjusted, set by a user, or determined in software. After the predetermined amount of time has elapsed (block 212), control returns to block 206 and the portable measurement device 108a again attempts to find a data collection server 110 by broadcasting the query message. This attempt may be successful if, for example, the device 108a has been moved to a location within the communication range of a data collection server 110a, 110b, and/or 110c.
More specifically, the process of
If a query message is detected (block 252), the data collection server 110a, 110b, or 110c responds to the query message (block 254) and creates a wireless communication link with the portable measurement device 108a or 108b (block 255). The data collection server 110a, 110b, or 110c may respond to the query message by sending an acknowledgement message or some other message to inform the portable measurement device 108a or 108b of the presence and capabilities of the data collection server 110a, 110b, or 110c. The acknowledgment message is transmitted using the communication protocol 112 as described above.
After the wireless communication link is established (block 255), the data collection server 110a, 110b, or 110c collects audience measurement data from the portable measurement device 108a or 108b (block 256). The audience measurement data is transmitted from the portable measurement device 108a or 108b using the communication protocol 112.
After the audience measurement data is received by the data collection server 110a, 110b, or 110c (block 256), the data collection server 110a, 110b, or 110c may transfer the collected audience measurement data to the central data processing server 116 (block 257). The collected audience measurement data may be transferred as it is received by the data collection server 110a, 110b, or 110c or may be stored and transferred at a later time. The data collection server 110a, 110b, or 110c then waits for another query message and/or additional audience measurement data from the portable measurement device 108a or 108b (block 258).
Although the above examples illustrate only two portable measurement devices 108a and 108b, persons of ordinary skill in the art will readily appreciate that any number of portable measurement devices may be employed. Similarly, although only portable measurement devices 108a and 108b are discussed above, persons of ordinary skill in the art will appreciated that the system 100 may employ fixed measurement devices (not shown) in addition to the portable measurement devices. Moreover, although only three data collection servers 110a, 110b, and 110c are shown in the above example, a person of ordinary skill in the art will appreciate that any number of such servers may be employed. For example, additional data collection servers may be used in areas with large data traffic loads. Similarly, although only data collection servers 110a, 110b, or 110c employing an extensible language are disclosed above, persons of ordinary skill in the art will appreciate that some of the servers may be traditional dedicated servers adapted to collect data from fixed or otherwise dedicated metering devices.
The processor 306 may be any type of well known processor, such as a processor from the Intel Pentium® family of microprocessors, the Intel Itanium® family of microprocessors, the Intel Centrino® family of microprocessors, and/or the Intel XScale® family of microprocessors. In addition, the processor 306 may include any type of well known cache memory, such as static random access memory (SRAM). The main memory device 310 may include dynamic random access memory (DRAM) and/or any other form of random access memory. For example, the main memory device 310 may include double data rate random access memory (DDRAM). The main memory device 310 may also include non-volatile memory. In an example, the main memory device 310 stores a software program which is executed by the processor 306 in a well known manner. The flash memory device 312 may be any type of flash memory device. The flash memory device 312 may store firmware used to boot the portable metering device 300.
The interface circuit(s) 314 may be implemented using any type of well known interface standard, such as an Ethernet interface and/or a Universal Serial Bus (USB) interface. One or more input devices 316 may be connected to the interface circuits 314 for entering data and commands into the main processing unit 302. For example, the input device 316 may be a keypad, mouse, touch screen, track pad, track ball, and/or a voice recognition system.
One or more displays, speakers, and/or other output devices 318 may also be connected to the main processing unit 302 via one or more of the interface circuits 314. The display 318 may be a liquid crystal displays (LCD), light emitting diode (LED) display, or any other type of display. The display 318 may generate visual indications of data generated during operation of the main processing unit 302. The visual indications may include prompts for human operator input, calculated values, detected data, etc.
The example processor system 300 may also include one or more storage devices 320. For example, the portable metering device 300 may include one or more hard drives, a compact disk (CD) drive, a digital versatile disk drive (DVD), and/or other computer media input/output (I/O) devices.
The example processor system 300 may also exchange data with other devices 322 via a connection to a network 324. The network connection may be any type of network connection, such as an Ethernet connection, a wireless network connection, a cellular data line, etc. The network 324 may be any type of network, such as the Internet, a cellular network, a cable network, and/or a wireless peer-to-peer network. Data may be exchanged using an extensible data transport such as XML and/or XML Web Services or may be exchanged using some other known communication protocol.
Because the hardware configuration of a server is well known, it is not separately shown. However, persons of ordinary skill in the art will appreciate that the data collection servers 110 may be implemented using hardware such as that shown in
Although the above discloses example systems including, among other components, software executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the disclosed hardware and software components could be embodied exclusively in dedicated hardware, exclusively in software, exclusively in firmware or in some combination of hardware, firmware and/or software.
In addition, although certain methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all apparatus, methods and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.
This patent arises from a continuation of U.S. patent application Ser. No. 11/457,666 (now U.S. Pat. No. 8,023,882), entitled “PORTABLE AUDIENCE MEASUREMENT ARCHITECTURES AND METHODS FOR PORTABLE AUDIENCE MEASUREMENT” which was filed on Jul. 14, 2006 and which is a continuation of International Patent Application No. PCT/US2004/000818, entitled “PORTABLE AUDIENCE MEASUREMENT ARCHITECTURES AND METHODS FOR PORTABLE AUDIENCE MEASUREMENT” which was filed on Jan. 14, 2004. U.S. patent application Ser. No. 11/457,666 and International Patent Application No. PCT/US2004/000818 are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4603232 | Kurland et al. | Jul 1986 | A |
4623230 | Weinblatt | Nov 1986 | A |
4695879 | Weinblatt | Sep 1987 | A |
4718106 | Weinblatt | Jan 1988 | A |
4930011 | Kiewit | May 1990 | A |
5014206 | Scribner et al. | May 1991 | A |
5068656 | Sutherland | Nov 1991 | A |
5072380 | Randelman et al. | Dec 1991 | A |
5097981 | Degasperi et al. | Mar 1992 | A |
5133081 | Mayo | Jul 1992 | A |
5142278 | Moallemi et al. | Aug 1992 | A |
5309174 | Minkus | May 1994 | A |
5331544 | Lu et al. | Jul 1994 | A |
5382970 | Kiefl | Jan 1995 | A |
5394461 | Garland | Feb 1995 | A |
5398190 | Wortham | Mar 1995 | A |
5406271 | Sonnendorfer et al. | Apr 1995 | A |
5410724 | Worthy | Apr 1995 | A |
5432841 | Rimer | Jul 1995 | A |
5481294 | Thomas et al. | Jan 1996 | A |
5483276 | Brooks et al. | Jan 1996 | A |
5490060 | Malec et al. | Feb 1996 | A |
5510828 | Lutterbach et al. | Apr 1996 | A |
5557268 | Hughes et al. | Sep 1996 | A |
5557524 | Maki | Sep 1996 | A |
5592181 | Cai et al. | Jan 1997 | A |
5636245 | Ernst et al. | Jun 1997 | A |
5638077 | Martin | Jun 1997 | A |
5644723 | Deaton et al. | Jul 1997 | A |
5691980 | Welles et al. | Nov 1997 | A |
5699244 | Clark, Jr. et al. | Dec 1997 | A |
5710884 | Dedrick | Jan 1998 | A |
5737026 | Lu et al. | Apr 1998 | A |
5748104 | Argyroudis et al. | May 1998 | A |
5812959 | Froeburg et al. | Sep 1998 | A |
5815114 | Speasl et al. | Sep 1998 | A |
5825283 | Camhi | Oct 1998 | A |
5826164 | Weinblatt | Oct 1998 | A |
5848129 | Baker | Dec 1998 | A |
5872588 | Aras et al. | Feb 1999 | A |
5890068 | Fattouche et al. | Mar 1999 | A |
5898384 | Alt et al. | Apr 1999 | A |
5901171 | Kohli et al. | May 1999 | A |
5923252 | Sizer et al. | Jul 1999 | A |
5952958 | Speasl et al. | Sep 1999 | A |
5974396 | Anderson et al. | Oct 1999 | A |
5984182 | Murrah et al. | Nov 1999 | A |
5995015 | DeTemple et al. | Nov 1999 | A |
6006148 | Strong | Dec 1999 | A |
6035177 | Moses et al. | Mar 2000 | A |
6041280 | Kohli et al. | Mar 2000 | A |
6091956 | Hollenberg | Jul 2000 | A |
6098048 | Dashefsky et al. | Aug 2000 | A |
6125325 | Kohli | Sep 2000 | A |
6236937 | Kohli | May 2001 | B1 |
6246948 | Thakker | Jun 2001 | B1 |
6252522 | Hampton et al. | Jun 2001 | B1 |
6353929 | Houston | Mar 2002 | B1 |
6393046 | Kohli et al. | May 2002 | B1 |
6397041 | Ballard et al. | May 2002 | B1 |
6400753 | Kohli et al. | Jun 2002 | B1 |
6421609 | Kohli | Jul 2002 | B2 |
6466971 | Humpleman et al. | Oct 2002 | B1 |
6467089 | Aust et al. | Oct 2002 | B1 |
6530082 | Del Sesto et al. | Mar 2003 | B1 |
6531982 | White et al. | Mar 2003 | B1 |
6546419 | Humpleman et al. | Apr 2003 | B1 |
6574558 | Kohli | Jun 2003 | B2 |
6615130 | Myr | Sep 2003 | B2 |
6647548 | Lu et al. | Nov 2003 | B1 |
6741684 | Kaars | May 2004 | B2 |
6745011 | Hendrickson et al. | Jun 2004 | B1 |
6934508 | Ceresoli et al. | Aug 2005 | B2 |
6970131 | Percy et al. | Nov 2005 | B2 |
7181159 | Breen | Feb 2007 | B2 |
7277692 | Jones et al. | Oct 2007 | B1 |
7460827 | Schuster et al. | Dec 2008 | B2 |
7471987 | Crystal et al. | Dec 2008 | B2 |
8023882 | Croy et al. | Sep 2011 | B2 |
8185351 | Crystal et al. | May 2012 | B2 |
20010037232 | Miller | Nov 2001 | A1 |
20010049620 | Blasko | Dec 2001 | A1 |
20020010919 | Lu et al. | Jan 2002 | A1 |
20020056087 | Berezowski et al. | May 2002 | A1 |
20020059218 | August et al. | May 2002 | A1 |
20020129360 | Lee | Sep 2002 | A1 |
20020133393 | Tatsumi et al. | Sep 2002 | A1 |
20020133412 | Oliver et al. | Sep 2002 | A1 |
20020138830 | Nagaoka et al. | Sep 2002 | A1 |
20020178220 | Smith et al. | Nov 2002 | A1 |
20020178441 | Hashimoto | Nov 2002 | A1 |
20030005433 | Janik et al. | Jan 2003 | A1 |
20030018977 | McKenna | Jan 2003 | A1 |
20030037333 | Ghashghai et al. | Feb 2003 | A1 |
20030041141 | Abdelaziz et al. | Feb 2003 | A1 |
20030074224 | Tanabe et al. | Apr 2003 | A1 |
20030115586 | Lejouan et al. | Jun 2003 | A1 |
20030122708 | Percy et al. | Jul 2003 | A1 |
20030163831 | Gall et al. | Aug 2003 | A1 |
20030177488 | Smith et al. | Sep 2003 | A1 |
20040004737 | Kahn et al. | Jan 2004 | A1 |
20040111738 | Gunzinger | Jun 2004 | A1 |
20050035857 | Zhang et al. | Feb 2005 | A1 |
20050039206 | Opdycke | Feb 2005 | A1 |
20050054285 | Mears et al. | Mar 2005 | A1 |
20050144632 | Mears et al. | Jun 2005 | A1 |
20050204379 | Yamamori | Sep 2005 | A1 |
20060168613 | Wood et al. | Jul 2006 | A1 |
20060242325 | Ramaswamy et al. | Oct 2006 | A1 |
20070288277 | Neuhauser et al. | Dec 2007 | A1 |
20070288476 | Flanagan, III et al. | Dec 2007 | A1 |
20070294705 | Gopalakrishnan et al. | Dec 2007 | A1 |
20080005308 | Ochiai et al. | Jan 2008 | A1 |
20080109295 | McConochie et al. | May 2008 | A1 |
20090037575 | Crystal et al. | Feb 2009 | A1 |
20090169024 | Krug et al. | Jul 2009 | A1 |
20090171767 | Kolessar | Jul 2009 | A1 |
20100269127 | Krug | Oct 2010 | A1 |
20110099142 | Karjalainen et al. | Apr 2011 | A1 |
20110106587 | Lynch et al. | May 2011 | A1 |
20110153391 | Tenbrock | Jun 2011 | A1 |
20120245978 | Jain et al. | Sep 2012 | A1 |
Number | Date | Country |
---|---|---|
199731160 | Dec 1997 | AU |
2003253598 | Nov 2003 | AU |
2252903 | Apr 1997 | CA |
2229238 | Aug 1999 | CA |
0231427 | Aug 1986 | EP |
0 731 339 | Mar 1996 | EP |
1 209 483 | Apr 1997 | EP |
1 271 102 | Apr 1997 | EP |
1 026 847 | Aug 2000 | EP |
1133090 | Sep 2001 | EP |
1 209 483 | May 2002 | EP |
1213860 | Jun 2002 | EP |
0 895 599 | Aug 2002 | EP |
0 731 339 | Nov 2002 | EP |
1 271 102 | Jan 2003 | EP |
7007483 | Jan 1995 | JP |
7327017 | Dec 1995 | JP |
8249307 | Sep 1996 | JP |
9081638 | Sep 1997 | JP |
10163992 | Jun 1998 | JP |
10308711 | Nov 1998 | JP |
11308185 | Nov 1999 | JP |
11345388 | Dec 1999 | JP |
2000020548 | Jan 2000 | JP |
2000020555 | Jan 2000 | JP |
2000048070 | Feb 2000 | JP |
200068956 | Mar 2000 | JP |
2000307530 | Nov 2000 | JP |
2000517141 | Dec 2000 | JP |
2001502130 | Feb 2001 | JP |
2001524776 | Dec 2001 | JP |
2001527320 | Dec 2001 | JP |
200251274 | Feb 2002 | JP |
2002051274 | Feb 2002 | JP |
2002135810 | May 2002 | JP |
2002344933 | Nov 2002 | JP |
9504430 | Feb 1995 | WO |
9904350 | Jan 1999 | WO |
9933206 | Jul 1999 | WO |
0003364 | Jan 2000 | WO |
03095945 | Nov 2003 | WO |
2005057956 | Jun 2005 | WO |
2005071961 | Aug 2005 | WO |
Entry |
---|
Japanese Patent Office, “Notice of Grounds for Rejection,” issued in connection with Japanese Patent Serial No. 2001-579179, mailed on Oct. 20, 2009, with its English language translation (5 pages). |
Canadian Intellectual Property Office, “Notification of a Requisition by the Examiner,” issued in connection with Canadian Patent Serial No. 2,407,474, on Sep. 8, 2009 (4 pages). |
Robinson, Phillip, Global positioning helps keeps travelers on course, Knight Ridder/Tribune News Service, Jun. 1997, 3 pages. |
International Trade Administration, Office of Telecommunications, Global Positioning System: Market Projections and Trends in the Newest Global Information Utility, Sep. 1998, 95 pages. |
Definition of “advertise”, 1998, Webster's II—New Riverside University Dictionary, 1988. |
“Nielsen to Test Electronic Ratings for Outdoor Advertizind”, BIZCOMMUNITY.COM, Oct. 9, 2002, 4 pgs, www.biz-community.com/Article/198/19/1181.html. |
Battelle Transportation Division, “Lexington Area Travel Date Collection Test”, Final Report to Federal Highway Administration, Sep. 15, 1997, http://www.thwa.dot.gov/ohi. |
Australian Patent Office, Search Report, Jul. 12, 2005, 4 pages. |
Euopean Patent Office, a Written Opinion of the International Searching Authority for the international application No. PCT/US04/000818, dated Mar. 25, 2005, 9 pages. |
European Patent Office, International Search Report of the International Searching Authority for the international application No. PCT/US04/000818, dated Mar. 25, 2005, 4 pages. |
European Patent Office, International Preliminary Report on Patentability and Written Opinion for international application No. PCT/US04/000818, dated Aug. 3, 2006, 11 pages. |
United States Patent and Trademark Office, Office Action issued in connection with U.S. Appl. No. 11/457,666, dated Feb. 23, 2009, 16 pages. |
United State Patent and Trademark Office, Notice of Allowance issued in connection with U.S. Appl. No. 11/457,666, dated Mar. 4, 2011, 7 pages. |
Intellectual Property Corporation of Malaysia, “Substantive Examination Adverse Report and Search Report,” issued in connection with Malaysian Application No. PI20050135, mailed on May 13, 2008 (3 pages). |
Mexican Patent Office, “Official Action,” issued in connection with Mexican Patent Application No. PA/a/2006/008054, on Apr. 7, 2009 (4 pages).—with redacted summary in English, issued in connection with Mexican Patent Application No. PA/a/2006/008054, on Jun. 2, 2009. |
United States Patent and Trademark Office, “Office Action,” issued in connection with U.S. Appl. No. 11/457,666, dated Dec. 14, 2009, (20 pages). |
United States Patent and Trademark Office, “Office Action,” issued in connection with U.S. Appl. No. 11/457,666, dated Mar. 9, 2010, (24 pages). |
Intellectual Property Corporation of Malaysia, “Substantive Examination Adverse Report and Search Report,” issued in connection with Malaysian Application No. PI20080006, on Dec. 31, 2008 (3 pages). |
Intellectual Property Corporation of Malaysia, “Substantive Examination Adverse Report and Search Report,” issued in connection with Malaysian Application No. PI20031501, on Aug. 14, 2009 (3 pages). |
European Patent Office, “Supplementary European Search Report,” issued in connection with application No. 03750041.0, on Oct. 19, 2010 (3 pages). |
European Patent Office, “Communication and Examination,” issued in connection with application No. 03750041.0, on Apr. 11, 2011 (7 pages). |
Number | Date | Country | |
---|---|---|---|
20110239245 A1 | Sep 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11457666 | Jul 2006 | US |
Child | 13159243 | US | |
Parent | PCT/US2004/000818 | Jan 2004 | US |
Child | 11457666 | US |