This disclosure relates generally to user support of electronic devices, and more specifically to electronic devices providing error messages that include matrix codes which can then be displayed and scanned to access information regarding resolution of error conditions related to the error messages.
The present disclosure discloses systems, apparatuses, and methods for facilitating user support of an electronic device using matrix codes. An electronic device may detect that an error condition has occurred and may select a matrix code based on the error condition. The electronic device may include the selected matrix code in an error message. After the electronic device transmits the error message to a display device, a reader device may detect the displayed matrix code. The reader device may decode the matrix code to access and present information regarding resolution of the error condition.
In one or more implementations, the electronic device may select the matrix code by looking up the error condition in a table that lists correspondences between error conditions and matrix codes. In one or more other implementations, the electronic device may dynamically generate the matrix code and may include information specific to the electronic device in the generated matrix code.
In various implementations, the electronic device may determine that the information regarding resolution of the error condition has been utilized to unsuccessfully resolve the error condition. The electronic device may determine such by monitoring operations performed by the electronic device, by receiving indications of such from the reader device and/or one or more user interfaces of the electronic devices, and so on. In some cases, if the electronic device determines that the information regarding resolution of the error condition has been utilized to unsuccessfully resolve the error condition, the electronic device may select and transmit and additional matrix code that may be decoded by the reader device to access and present an additional set of information regarding resolution of the error condition. In other cases, if the electronic device determines that the information regarding resolution of the error condition has been utilized to unsuccessfully resolve the error condition, the electronic device may select and transmit and additional matrix code that may be decoded by the reader device to initiate an electronic device support request. Whether the additional matrix code selected by the electronic device can be decoded to access and present an additional set of information regarding resolution of the error condition or to initiate an electronic device support request may be dependent on received user input, the fact that a threshold number of sets of information regarding resolution of the error condition have been unsuccessfully utilized, the fact that additional sets of information regarding resolution of the error condition do not exist or are not available, and so on.
In some implementations, the reader device may prompt for login information before presenting the information regarding resolution of the error condition. The reader device may require login information prior to presenting the information related to resolution of the error condition in order to restrict access to technical support personnel, users who have subscribed to a support service, registered users, and so on.
It is to be understood that both the foregoing general description and the following detailed description are for purposes of example and explanation and do not necessarily limit the present disclosure. The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate subject matter of the disclosure. Together, the descriptions and the drawings serve to explain the principles of the disclosure.
The description that follows includes sample systems, methods, and computer program products that embody various elements of the present disclosure. However, it should be understood that the described disclosure may be practiced in a variety of forms in addition to those described herein.
Electronic devices (such as televisions, television receivers, digital video recorders, digital video disc players, automobiles, computing devices, telephones, kitchen appliances, video game systems, security systems, and so on) are often complex to operate. When an electronic device encounters an error condition during operation, the electronic device may present an error message (such as a pop-up error message) indicating that the error condition has been encountered. However, error messages may be cryptic or difficult for users to understand. Even when users are able to understand from error messages exactly what error condition has occurred, they may be uncertain or unaware exactly what they should do in order to resolve the error condition.
The present disclosure discloses systems, apparatuses, and methods for facilitating user support of an electronic device using matrix codes. An electronic device may detect that an error condition has occurred. In response to detecting that the error condition has occurred, the electronic device may select a matrix code. The electronic device may include the selected matrix code in an error message and transmit the error message to a display device. A reader device may detect the matrix code displayed on the display device, decode the matrix code, and utilize information decoded from the detected matrix code to access and present information regarding resolution of the error condition.
The electronic device 101 may include one or more processing units 105, one or more one or more non-transitory storage media 106 (which may take the form of, but is not limited to, a magnetic storage medium; optical storage medium; magneto-optical storage medium; read only memory; random access memory; erasable programmable memory; flash memory; and so on), and one or more output components 107. Additionally, although the display device 102 is illustrated as separate from the electronic device, it is understood that in various implementations the display device may be incorporated into the electronic device. The processing unit of the electronic device may execute instructions stored in the non-transitory storage medium to derive information specific to the electronic device that relates to operation of the electronic device, dynamically generate one or more matrix codes (such as one or more QR codes) that include the information specific to the electronic device as well as user support information for the electronic device, and transmit the dynamically generated matrix code to the display device utilizing the output component.
Subsequently, the reader device 103 may detect the matrix code displayed by the display device 102, decode the information specific to the electronic device 101 and the user support information, and initiate one or more user support requests based on the decoded information. As part of initiating the user support request, the reader device may transmit the information specific to the electronic device to the user support provider 104. The user support information may include information regarding how the reader device will transmit the information specific to the electronic device to the user support provider (such as including a web address whether the user support provider may be contacted, an email address for a user support representative of the user support provider, a telephone number for the user support provider and so on. The reader device may include one or more processing units 109 which execute instructions stored in one or more non-transitory storage media 111 in order to perform the above described functions. The reader device may also include an optical input device 110 (such as a camera, a barcode scanner, and so on) for detecting the matrix code displayed by the display device as well as a communication component 112 for communicating with the user support provider.
The information specific to the electronic device 101 may include a variety of different information that is specific to the operation of the electronic device. For example, the information may include electronic device identifiers (such as network addresses, serial numbers, media access control numbers, and so on), electronic device configuration information (such as the individual hardware components included in the electronic device and/or identifiers for such components, drivers utilized on the electronic device, options set for the electronic device, a current status of the electronic device, and so on), error codes for errors that have occurred during electronic device operation (such as an error number associated with an error that has occurred, debug information, a core dump, and so on), account information for one or more customer accounts (such as subscription service accounts, warrantee accounts, support agreement accounts, and so on) associated with the electronic device, a location of the electronic device (such as a global positioning system location, a mailing address, and so on), and so on. For instance, in implementations where the electronic device includes a television receiver, the information specific to the television receiver may include a serial number for the receiver, a media access control number for the receiver, current settings for the receiver, current channel information for the receiver, account information for a programming subscription related to the television receiver, information on hardware included in the television receiver, a mailing address associated with the television receiver, and so on.
The user support information for the electronic device 101 may include a variety of information that may be utilized to initiate user support requests based on the information specific to the electronic device. For example, the user support information may include a web site address to which to transmit error codes and the web site may provide a user tutorials regarding operation of the electronic device related to the error code. By way of another example, the user support information may include a network address for a user support provider 104 response system to which user contact information, electronic device identifiers, error codes, and so on may be transmitted such that the response system may automatically correct a problem with the electronic device, schedule a service call (which may be performed via telephone, email, an onsite visit, and so on) and inform the user of the scheduled service call, and so on. By way of still another example, user support information may include an identifier for an application resident on the reader device 103 such as an electronic device password recovery application which may be passed an encrypted version of the password, one or more password recovery verification questions, and one or more encrypted password recovery verification answers. As such, the electronic device password recovery application may prompt a user with the one or more password recovery verification questions, compare the user's answers with the encrypted answers, and present the user with a decrypted version of the password if the answers are correct.
In some implementations, the electronic device 101 may dynamically generate the matrix codes upon the occurrence of an error during operation of the electronic device. For example, a refrigerator may dynamically generate a matrix code that includes an error code and transmit the matrix code to an associated display device when a cooling component ceases cooling. In other implementations, the electronic device 101 may dynamically generate the matrix codes in response to receiving a user input. For example, a user may call a user support line to obtain user support for a software product on a computer. A user support representative assisting the user may need to know configuration information about the computer in order to provide user support. The user support representative may include the user to launch a program on the computer for dynamically generating and displaying a matrix code that, when the user scans it with their smart phone, decodes the configuration information and transmits it to the user support representative.
In various implementations, the electronic device 101 may transmit the one or more matrix codes by themselves to the display device 102 via the output component 107 for the display device to display only the one or more matrix codes at a particular time. However, in various other implementations (such as implementations where the electronic device is a television receiver, digital video recorder, or other such device that provides images to a display), the electronic device may transmit one or more images (such as a video stream) to the display device via the output component. In such implementations, the electronic device may combine the one or more matrix codes with the one or more images and transmit the combination to the display device via the output component.
At block 205, the display device 102 displays the matrix code that was transmitted by the processing unit 105 of the electronic device 101 via the output component 107. The flow then proceeds to block 206.
At block 206, the reader device 103 detects the matrix code displayed on the display device 102. The flow then proceeds to block 207 where the reader device decodes the detected matrix code. Decoding the detected matrix code may include decoding the information specific to the electronic device and the user support information that is included in the matrix code. The flow then proceeds to block 208 where the reader device determines from the decoded user support information whether or not the reader device will provide user support. If so, the flow proceeds to block 215 where the reader device provides the user support before the flow proceeds to block 214 and ends. Otherwise, the flow proceeds to block 209.
At block 209, after the reader device 103 determines that the reader device will not provide user support, the reader device 103 determines from the decoded user support information whether or not to transmit a user support request to the user support provider 104. If not, the flow proceeds to block 214 and ends. Otherwise, the flow proceeds to block 210 where the reader device transmits a user support request including the decoded information specific including the electronic device to the user support provider 104 as specified by the decoded user support information.
The flow then proceeds to block 211 where the user support provider 104 provides the requested user support and the flow proceeds to block 212. At block 212, the user support provider determines whether or not to transmit a response to the user support request. The user support provider may not submit a response to the user support request if the user support request can be fulfilled without additional user involvement. However, the user support provider may submit a response for a variety of reasons such as if the user support request cannot be fulfilled without additional involvement (i.e., if the user support provider needs to schedule a telephone call with the user to provider the requested user support), if the user support provider provides a confirmation (i.e., an acknowledgement that the user support request was received, a notification as to the contents of the user support request that was received, and so on), if the user support provider will provide tutorials concerning the user support request, and so on.
If the user support provider 104 determines not to transmit a response to the user support request, the flow proceeds to block 214 and ends. Otherwise, the flow proceeds from block 212 to block 213 where the user support provider transmits the response. The user support provider may transmit the response to the reader device 103, the electronic device 101, another communication device utilized by the user (such as a telephone, an in person visit, an email address, and so on), and so on. The flow then proceeds to block 214 and ends.
It should be understood that the specific steps as well as the specific order or hierarchy of steps described in method 200 is an example of a sample approach. In other implementations, some of the specific steps as well as the specific order or hierarchy of steps in the method may be rearranged while remaining within the disclosed subject matter.
In this example, the television receiver is not receiving a signal from the programming provider because of a network outage that the programming provider is already aware of and is already attempting to fix. As such, the programming provider may transmit a response to the user indicating that the problem is related to a service outage that the programming provider is working to correct.
In this example, the automobile 402A may require an on site mechanic visit in order to repair the locked engine. As such, the roadside assistance system may determine when a telephone support representative will be able to call the user 401A and transmit a notification regarding when the telephone support representative will call the user.
As illustrated in
The electronic device 601 may include one or more processing units 605, one or more one or more non-transitory storage media 606, and one or more communication components 607. Additionally, although the display device 102 is illustrated as separate from the electronic device, it is understood that in various implementations the display device may be incorporated into the electronic device. The processing unit of the electronic device may execute instructions stored in the non-transitory storage medium to detect that at least one error condition has occurred during the operation of the electronic device, select at least one matrix code to include in at least one error message based on the error condition, and transmit the error message (including the matrix code) to the display device utilizing the communication component.
Subsequently, the reader device 603 may detect and decode the matrix code displayed by the display device 602 and utilize information decoded from the matrix code to access and present one or more sets of information related to resolution of the error condition. For example, in cases where the electronic device 601 is a computer and the error condition relates to a failure to detect a hard drive, the information related to resolution of the error condition may be a video that demonstrates how to replace the hard drive of the computer. The reader device may include one or more processing units 609 which execute instructions stored in one or more non-transitory storage media 611 in order to perform the above described functions. As part of accessing the information related to resolution of the error condition, the reader device may retrieve the information from the non-transitory storage medium 611, retrieve the information from where it is stored and provided by the information server 604, and/or retrieve the information from another location where the information is stored. The reader device may also include an optical input device 610 (such as a camera, a barcode scanner, and so on) for detecting the matrix code displayed by the display device as well as a communication component 612 for communicating with the user support provider.
The information related to resolution the error condition may be a variety of different kind of information presented via a variety of different media. In some implementations the information related to resolution the error condition may be video (such as a YouTube™ video), audio, text, and/or other media step by step presentation of a procedure to resolve the error condition.
In various implementations, the reader device 603 may prompt for a set of login information (such as one or more login identifiers, passwords, security certificates, security tokens, and/or other information utilized to authenticate a login) prior to presenting the set of information related to resolution of the error condition. The reader device may prompt for such login information based on information decoded from the matrix code. In such cases, the reader device may require login information prior to presenting the set of information related to resolution of the error condition to restrict access to technical support personnel, users who have subscribed to a support service, registered users, and so on.
In some implementations, the electronic device 601 may select the matrix code to include in the error message by dynamically generating the matrix code upon the detection of the error condition. For example, in situations where the electronic device is a set top box and a failure to connect to a programming source is detected, the electronic device may generate a matrix code utilizing one or more references to information related to resolution of failure to detect programming sources. In such cases, the reference may have been obtained from the information server 604, which may be maintained by a programming provider associated with the set top box, and stored in the non-transitory storage medium 606.
Further, in such implementations, the electronic device may include various information specific to the electronic device in the generated matrix code. For example, the electronic device may include: electronic device identifiers (such as network addresses, serial numbers, media access control numbers, and so on), electronic device configuration information (such as the individual hardware components included in the electronic device and/or identifiers for such components, drivers utilized on the electronic device, options set for the electronic device, a current status of the electronic device, and so on), error codes for errors that have occurred during electronic device operation (such as an error number associated with an error that has occurred, debug information, a core dump, and so on), account information for one or more customer accounts (such as subscription service accounts, warrantee accounts, support agreement accounts, and so on) associated with the electronic device, a location of the electronic device (such as a global positioning system location, a mailing address, and so on), and so on. The reader device 603 may utilize the information specific to the electronic device to select among one or more sets of information related to resolution of the error condition, confirm authorization to present the information, and so on.
In other implementations, the electronic device 601 may store a number of matrix codes related to different error conditions in the non-transitory storage medium 606. Such matrix codes may have been obtained from the information server 604, which may be maintained by a support provider associated with the electronic device (such as a service provider associated with the electronic device). When the processing unit 605 detects an error condition, the processing unit 605 may select a matrix code that corresponds to the error condition (such as utilizing a lookup table that maintains correspondences between error conditions and matrix codes). For example, in cases where the electronic device is an electric range and the electric range detects that a heating element has failed to heat, the electronic range may consult a lookup table of correspondences between error conditions and matrix codes to select a matrix code related to failed heating elements.
In various implementations, after the processing unit 605 transmits the error message (including the matrix code) to the display device 602 utilizing the communication component 607, the processing unit may determine that the information regarding the resolution of the error condition has been utilized to unsuccessfully attempt to resolve the error condition. The processing unit may determine that the information regarding the resolution of the error condition has been utilized to unsuccessfully attempt to resolve the error condition by: monitoring the operation of the electronic device 601 to ascertain whether operations included in the information have been performed, receiving one or more indications that one or more resolution attempts utilizing the information have been unsuccessful from the reader device 603, receiving one or more indications that one or more resolution attempts utilizing the information have been unsuccessful from one or more user interfaces (not shown) of the electronic device (such as one or more remotes, buttons, touch screens, and/or other user interface components), and/or other such ways of determining that the information regarding the resolution of the error condition has been utilized to unsuccessfully attempt to resolve the error condition. If the processing unit 605 determines that the information regarding the resolution of the error condition has been utilized to unsuccessfully attempt to resolve the error condition, the processing unit may select one or more additional matrix codes to transmit to the display device 602 via the communication component 607.
In some cases, the reader device 603 may detect and decode the additional matrix code displayed by the display device and utilize information decoded from the matrix code to access and present one or more sets of additional information related to resolution of the error condition. For example, in situations where the electronic device is an automobile that has detected a low power error condition, the automobile may display a matrix code that may be scanned by a smart phone to present a video demonstrating how to verify that battery cables are properly secured. The video may include a prompt for a user to indicate whether the user has successfully or unsuccessfully resolved the low power error condition utilizing the video. If the user indicates that he has unsuccessfully resolved the low power error condition utilizing the video, the smart phone may transmit such to the automobile which may then display an additional matrix code. The additional matrix code may be scanned by the smart phone to present a different video that demonstrates how to replace the battery.
In such cases, the reader device 603 may prompt for a set of login information (such as one or more login identifiers, passwords, security certificates, security tokens, and/or other information utilized to authenticate a login) prior to presenting the additional set of information related to resolution of the error condition. The reader device may prompt for such login information based on information decoded from the additional matrix code. In such cases, the reader device may require login information prior to presenting the set of additional information related to resolution of the error condition to restrict access to technical support personnel, users who have subscribed to a support service, registered users, and so on.
In other cases, the reader device 603 may detect and decode the additional matrix code displayed by the display device and utilize information decoded from the additional matrix code to initiate one or more electronic device support requests. In some implementations, the electronic device 601 may have selected the additional matrix code that is decodable to initiate the electronic device support request as opposed to a different matrix code decodable to access and/or present a set additional information related to resolution of the error condition. The electronic device may have performed this selection in response to: receiving an input from a user (such as via the reader device, an input component associated with the electronic device, and so on) indicating that the user does not wish to perform additional attempts to resolve the error condition, determining that a threshold number (such as three) of attempts to resolve the error condition have been performed, determining that a set of additional information regarding resolution of the error condition is not available, and/or similar conditions.
At block 704, after the electronic device 601 determines that an error condition has been detected, the electronic device selects a matrix code based on the detected error condition. In some cases, the electronic device may select the matrix code based on the error condition by selecting an error code stored by the electronic device, such as by utilizing a table of correspondences between error conditions and stored matrix codes. In other cases, the electronic device may generate the matrix code dynamically. In these other cases the electronic device may include information specific to the electronic device in the dynamically generated matrix code. The flow then proceeds to block 705 where the electronic device includes the matrix code in an error message. Next, the flow proceeds to block 706 where the electronic device transmits the error message to a display device 602 before the flow proceeds to block 707. The matrix code included in the error message displayed on the display device may be scanned and decoded by the reader device 603 in order to access and present information related to resolution of the error condition.
At block 707, the electronic device 601 waits for resolution of the error condition and the flow proceeds to block 708. At block 708, the electronic device determines whether or not the error condition is resolved. If so, the flow returns to block 702 and the electronic device continues to operate. Otherwise, the flow proceeds to block 709.
At block 709, after the electronic device 601 determines that the error condition is not resolved, the electronic device determines whether or not to transmit an additional matrix code. In some cases, the electronic device may determine to transmit an additional matrix code if the electronic device determines that an attempt to resolve the error condition utilizing information presented in association with a previously transmitted matrix code is unsuccessful. If not, the flow returns to block 707 and the electronic device continues to wait for resolution of the error condition. Otherwise, the flow proceeds to block 710.
At block 710, after the electronic device 601 determines to transmit an additional matrix code, the electronic device selects and transmits the additional matrix code to the display device 602. The additional matrix code displayed on the display device may be scanned and decoded by the reader device 603 in order to access and present additional information related to resolution of the error condition, to initiate an electronic device support request, and/or perform similar operations. The flow then returns to block 707 and the electronic device continues to wait for resolution of the error condition.
As shown in
As also shown, the window 814c may include selection elements prompting the user 804 to indicate whether the error condition is resolved 809c, whether the error condition is not resolved and to provide another matrix code related to another set of information regarding resolution of the “no input detected” error condition 810c, or whether the error condition is not resolved and to initiate a technical support request 811c.
If the user 804 selects the selection element indicating that the error condition is resolved 809c, the smart phone 805 may close the window 814c and may transmit a message to the set top box 801 to stop displaying the error message 807a displayed on the television screen 803.
However, if the user 804 selects the selection element indicating that the error condition is not resolved and to provide another matrix code related to another set of information regarding resolution of the “no input detected” error condition 810c, the smart phone 805 may transmit a message to the set top box 801 (as illustrated in
As shown in
If the user 804 selects the selection element indicating to initiate a technical support request 811f, the smart phone 805 may (as illustrated in
In the present disclosure, the methods disclosed may be implemented as sets of instructions or software readable by a device. Further, it is understood that the specific order or hierarchy of steps in the methods disclosed are examples of sample approaches. In other embodiments, the specific order or hierarchy of steps in the method can be rearranged while remaining within the disclosed subject matter. The accompanying method claims present elements of the various steps in a sample order, and are not necessarily meant to be limited to the specific order or hierarchy presented.
The described disclosure may be provided as a computer program product, or software, that may include a non-transitory machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to the present disclosure. A non-transitory machine-readable medium includes any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The non-transitory machine-readable medium may take the form of, but is not limited to, a magnetic storage medium (e.g., floppy diskette, video cassette, and so on); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; and so on.
It is believed that the present disclosure and many of its attendant advantages will be understood by the foregoing description, and it will be apparent that various changes may be made in the form, construction and arrangement of the components without departing from the disclosed subject matter or without sacrificing all of its material advantages. The form described is merely explanatory, and it is the intention of the following claims to encompass and include such changes.
While the present disclosure has been described with reference to various embodiments, it will be understood that these embodiments are illustrative and that the scope of the disclosure is not limited to them. Many variations, modifications, additions, and improvements are possible. More generally, embodiments in accordance with the present disclosure have been described in the context or particular embodiments. Functionality may be separated or combined in blocks differently in various embodiments of the disclosure or described with different terminology. These and other variations, modifications, additions, and improvements may fall within the scope of the disclosure as defined in the claims that follow.
This application is a continuation-in-part application of U.S. patent application Ser. No. 12/953,227, entitled “Facilitating User Support of Electronic Devices Utilizing Dynamic Matrix Code Generation,” filed on Nov. 23, 2010, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4809325 | Hayashi et al. | Feb 1989 | A |
4837414 | Edamula | Jun 1989 | A |
5500681 | Jones | Mar 1996 | A |
5510603 | Hess et al. | Apr 1996 | A |
5581636 | Skinger | Dec 1996 | A |
5602377 | Beller et al. | Feb 1997 | A |
5703349 | Meyerson et al. | Dec 1997 | A |
5959285 | Schuessler | Sep 1999 | A |
5963265 | Bae et al. | Oct 1999 | A |
5978855 | Metz et al. | Nov 1999 | A |
6006990 | Ye et al. | Dec 1999 | A |
6058238 | Ng | May 2000 | A |
6263502 | Morrison et al. | Jul 2001 | B1 |
6438751 | Voyticky et al. | Aug 2002 | B1 |
6512919 | Ogasawara | Jan 2003 | B2 |
6556273 | Wheeler et al. | Apr 2003 | B1 |
6704929 | Ozer et al. | Mar 2004 | B1 |
6766956 | Boylan et al. | Jul 2004 | B1 |
6983304 | Sato | Jan 2006 | B2 |
7046161 | Hayes | May 2006 | B2 |
7206029 | Cohen-Solal | Apr 2007 | B2 |
7206409 | Antonellis et al. | Apr 2007 | B2 |
7221405 | Basson et al. | May 2007 | B2 |
7244404 | Rosenberg et al. | Jul 2007 | B2 |
7328848 | Xia et al. | Feb 2008 | B2 |
7349668 | Ilan et al. | Mar 2008 | B2 |
7369180 | May 2008 | B2 | |
7373652 | Bayrakeri et al. | May 2008 | B1 |
7387250 | Muni | Jun 2008 | B2 |
7394519 | Mossman et al. | Jul 2008 | B1 |
7424976 | Muramatsu | Sep 2008 | B2 |
7443449 | Momosaki et al. | Oct 2008 | B2 |
7487527 | Ellis et al. | Feb 2009 | B2 |
7587601 | Levy et al. | Sep 2009 | B2 |
7604172 | Onogi | Oct 2009 | B2 |
7612748 | Tateuchi | Nov 2009 | B2 |
7624417 | Dua | Nov 2009 | B2 |
7624916 | Sato et al. | Dec 2009 | B2 |
7673297 | Arsenault et al. | Mar 2010 | B1 |
7797430 | Ichieda | Sep 2010 | B2 |
7818675 | Maruyama et al. | Oct 2010 | B2 |
7841531 | Onogi | Nov 2010 | B2 |
8010977 | Hogyoku | Aug 2011 | B2 |
8045054 | Bishop et al. | Oct 2011 | B2 |
8186572 | Herzig | May 2012 | B2 |
8292166 | Gomez et al. | Oct 2012 | B2 |
8364018 | McArdle | Jan 2013 | B2 |
8380993 | Chen et al. | Feb 2013 | B2 |
8386339 | Minnick et al. | Feb 2013 | B2 |
8408466 | Gratton | Apr 2013 | B2 |
8427455 | Matsuda | Apr 2013 | B2 |
8430302 | Minnick et al. | Apr 2013 | B2 |
8439257 | Beals et al. | May 2013 | B2 |
8443407 | Gaede et al. | May 2013 | B2 |
8468610 | Beals et al. | Jun 2013 | B2 |
8511540 | Anguiano | Aug 2013 | B2 |
8534540 | Gratton et al. | Sep 2013 | B2 |
8550334 | Gratton et al. | Oct 2013 | B2 |
8553146 | Kennedy | Oct 2013 | B2 |
8746554 | Gomez et al. | Jun 2014 | B2 |
8786410 | Beals et al. | Jul 2014 | B2 |
8827150 | Gratton et al. | Sep 2014 | B2 |
8833640 | Martch et al. | Sep 2014 | B2 |
8856853 | Casagrande et al. | Oct 2014 | B2 |
8875173 | Kilaru et al. | Oct 2014 | B2 |
8886172 | Gomez | Nov 2014 | B2 |
8931031 | Schaefer | Jan 2015 | B2 |
9092830 | Gomez et al. | Jul 2015 | B2 |
9148686 | Gerhards et al. | Sep 2015 | B2 |
20010037297 | McNair | Nov 2001 | A1 |
20010052133 | Pack et al. | Dec 2001 | A1 |
20020027612 | Brill et al. | Mar 2002 | A1 |
20020049980 | Hoang | Apr 2002 | A1 |
20020112250 | Koplar et al. | Aug 2002 | A1 |
20030018711 | Imanishi | Jan 2003 | A1 |
20030050854 | Showghi et al. | Mar 2003 | A1 |
20030077065 | Scholten et al. | Apr 2003 | A1 |
20030112974 | Levy | Jun 2003 | A1 |
20030121978 | Rubin et al. | Jul 2003 | A1 |
20030151562 | Kulas | Aug 2003 | A1 |
20030172374 | Vinson et al. | Sep 2003 | A1 |
20040005900 | Zilliacus | Jan 2004 | A1 |
20040019691 | Daymond et al. | Jan 2004 | A1 |
20040026508 | Nakajima et al. | Feb 2004 | A1 |
20040044532 | Karstens | Mar 2004 | A1 |
20040046790 | Agarwal et al. | Mar 2004 | A1 |
20050009564 | Hayaashi et al. | Jan 2005 | A1 |
20050011958 | Fukasawa et al. | Jan 2005 | A1 |
20050015800 | Holcomb | Jan 2005 | A1 |
20050015815 | Shoff et al. | Jan 2005 | A1 |
20050055281 | Williams | Mar 2005 | A1 |
20050059339 | Honda et al. | Mar 2005 | A1 |
20050097618 | Arling et al. | May 2005 | A1 |
20050107135 | Deeds et al. | May 2005 | A1 |
20050125301 | Muni | Jun 2005 | A1 |
20050149967 | Hanley et al. | Jul 2005 | A1 |
20050163483 | Rassool | Jul 2005 | A1 |
20050180804 | Andrew et al. | Aug 2005 | A1 |
20050203854 | Das | Sep 2005 | A1 |
20050262548 | Shimojo et al. | Nov 2005 | A1 |
20050264694 | Ilan et al. | Dec 2005 | A1 |
20060064700 | Ludvig et al. | Mar 2006 | A1 |
20060065733 | Lee et al. | Mar 2006 | A1 |
20060071076 | Tamayama | Apr 2006 | A1 |
20060079247 | Ritter | Apr 2006 | A1 |
20060086796 | Onogi | Apr 2006 | A1 |
20060095286 | Kimura | May 2006 | A1 |
20060124742 | Rines et al. | Jun 2006 | A1 |
20060196950 | Kiliccote | Sep 2006 | A1 |
20060203339 | Kleinberger et al. | Sep 2006 | A1 |
20060208088 | Sekiguchi | Sep 2006 | A1 |
20060265731 | Matsuda | Nov 2006 | A1 |
20070008344 | Medina | Jan 2007 | A1 |
20070011709 | Katz et al. | Jan 2007 | A1 |
20070016934 | Okada et al. | Jan 2007 | A1 |
20070016936 | Okada et al. | Jan 2007 | A1 |
20070017350 | Uehara | Jan 2007 | A1 |
20070019215 | Yu | Jan 2007 | A1 |
20070063050 | Attia et al. | Mar 2007 | A1 |
20070073585 | Apple et al. | Mar 2007 | A1 |
20070143788 | Abernethy et al. | Jun 2007 | A1 |
20070174198 | Kasahara | Jul 2007 | A1 |
20070192723 | Anzelde et al. | Aug 2007 | A1 |
20070200335 | Tushcel | Aug 2007 | A1 |
20070206020 | Duffield et al. | Sep 2007 | A1 |
20070256118 | Nomura et al. | Nov 2007 | A1 |
20070288594 | Philyaw et al. | Dec 2007 | A1 |
20080022323 | Koo | Jan 2008 | A1 |
20080059998 | McClenny et al. | Mar 2008 | A1 |
20080062164 | Bassi et al. | Mar 2008 | A1 |
20080073434 | Epshteyn et al. | Mar 2008 | A1 |
20080077324 | Hatano et al. | Mar 2008 | A1 |
20080082684 | Gaos et al. | Apr 2008 | A1 |
20080092154 | Hogyoku | Apr 2008 | A1 |
20080112615 | Obrea et al. | May 2008 | A1 |
20080156879 | Melick et al. | Jul 2008 | A1 |
20080182561 | Kim et al. | Jul 2008 | A1 |
20080189185 | Matsuo et al. | Aug 2008 | A1 |
20080200153 | Fitzpatrick et al. | Aug 2008 | A1 |
20080200160 | Fitzpatrick et al. | Aug 2008 | A1 |
20080201078 | Fitzpatrick et al. | Aug 2008 | A1 |
20080244675 | Sako et al. | Oct 2008 | A1 |
20080263621 | Austerlitz et al. | Oct 2008 | A1 |
20080267537 | Thuries | Oct 2008 | A1 |
20080281624 | Shibata | Nov 2008 | A1 |
20080288460 | Poniatowski et al. | Nov 2008 | A1 |
20080288600 | Clark | Nov 2008 | A1 |
20080307348 | Jones et al. | Dec 2008 | A1 |
20090029725 | Kindberg | Jan 2009 | A1 |
20090031071 | Chiu | Jan 2009 | A1 |
20090031373 | Hogyoku | Jan 2009 | A1 |
20090070699 | Birkill et al. | Mar 2009 | A1 |
20090083808 | Morrison | Mar 2009 | A1 |
20090088213 | Rofougaran | Apr 2009 | A1 |
20090094546 | Anzelde et al. | Apr 2009 | A1 |
20090108057 | Mu et al. | Apr 2009 | A1 |
20090113334 | Chakra et al. | Apr 2009 | A1 |
20090116074 | Wilsher | May 2009 | A1 |
20090154759 | Koskinen et al. | Jun 2009 | A1 |
20090157511 | Spinnell et al. | Jun 2009 | A1 |
20090157530 | Nagamoto et al. | Jun 2009 | A1 |
20090172780 | Sukeda et al. | Jul 2009 | A1 |
20090179852 | Refai et al. | Jul 2009 | A1 |
20090180025 | Dawson | Jul 2009 | A1 |
20090212112 | Li et al. | Aug 2009 | A1 |
20090212113 | Chiu et al. | Aug 2009 | A1 |
20090234570 | Sever | Sep 2009 | A1 |
20090254954 | Jeong | Oct 2009 | A1 |
20090293110 | Koga | Nov 2009 | A1 |
20090294538 | Wihlborg et al. | Dec 2009 | A1 |
20090303036 | Sahuguet | Dec 2009 | A1 |
20090307232 | Hall | Dec 2009 | A1 |
20090307719 | Clark et al. | Dec 2009 | A1 |
20090312105 | Koplar | Dec 2009 | A1 |
20090320066 | Soldan et al. | Dec 2009 | A1 |
20100001072 | Nobuyoshi | Jan 2010 | A1 |
20100017457 | Jumpertz et al. | Jan 2010 | A1 |
20100020970 | Liu et al. | Jan 2010 | A1 |
20100026721 | Park et al. | Feb 2010 | A1 |
20100031162 | Wiser et al. | Feb 2010 | A1 |
20100036936 | Cox et al. | Feb 2010 | A1 |
20100053339 | Aaron et al. | Mar 2010 | A1 |
20100081375 | Rosenblatt et al. | Apr 2010 | A1 |
20100089996 | Koplar | Apr 2010 | A1 |
20100096448 | Melick et al. | Apr 2010 | A1 |
20100103018 | Yoon et al. | Apr 2010 | A1 |
20100114715 | Schuster et al. | May 2010 | A1 |
20100129057 | Kulkarni | May 2010 | A1 |
20100131900 | Spetalnick | May 2010 | A1 |
20100131970 | Falcon | May 2010 | A1 |
20100131983 | Shannon et al. | May 2010 | A1 |
20100138344 | Wong | Jun 2010 | A1 |
20100149187 | Slavin et al. | Jun 2010 | A1 |
20100154035 | Damola et al. | Jun 2010 | A1 |
20100161437 | Pandey | Jun 2010 | A1 |
20100163613 | Bucher et al. | Jul 2010 | A1 |
20100169935 | Abbruzzese | Jul 2010 | A1 |
20100188514 | Sato et al. | Jul 2010 | A1 |
20100201894 | Nakayama et al. | Aug 2010 | A1 |
20100205628 | Davis et al. | Aug 2010 | A1 |
20100217663 | Ramer et al. | Aug 2010 | A1 |
20100225653 | Sao et al. | Sep 2010 | A1 |
20100261454 | Shenfield et al. | Oct 2010 | A1 |
20100262924 | Kalu | Oct 2010 | A1 |
20100262992 | Casagrande | Oct 2010 | A1 |
20100272193 | Khan et al. | Oct 2010 | A1 |
20100272420 | Soohoo et al. | Oct 2010 | A1 |
20100275010 | Ghirardi | Oct 2010 | A1 |
20100279710 | Dicke et al. | Nov 2010 | A1 |
20100295868 | Zahnert et al. | Nov 2010 | A1 |
20100301115 | Berkun | Dec 2010 | A1 |
20100313231 | Okamoto et al. | Dec 2010 | A1 |
20100319041 | Ellis | Dec 2010 | A1 |
20100327060 | Moran et al. | Dec 2010 | A1 |
20110000958 | Herzig | Jan 2011 | A1 |
20110007630 | Almhana et al. | Jan 2011 | A1 |
20110030068 | Imai | Feb 2011 | A1 |
20110039573 | Hardie | Feb 2011 | A1 |
20110058516 | Small et al. | Mar 2011 | A1 |
20110061003 | Miyazawa et al. | Mar 2011 | A1 |
20110065451 | Danado et al. | Mar 2011 | A1 |
20110087539 | Rubinstein et al. | Apr 2011 | A1 |
20110107374 | Roberts et al. | May 2011 | A1 |
20110107386 | De Los Reyes et al. | May 2011 | A1 |
20110138408 | Adimatyam et al. | Jun 2011 | A1 |
20110208710 | Lesavich | Aug 2011 | A1 |
20110258058 | Carroll et al. | Oct 2011 | A1 |
20110264527 | Fitzpatrick et al. | Oct 2011 | A1 |
20110264530 | Santangelo et al. | Oct 2011 | A1 |
20110282727 | Phan et al. | Nov 2011 | A1 |
20110314485 | Abed | Dec 2011 | A1 |
20120075529 | Wong et al. | Mar 2012 | A1 |
20120084206 | Mehew et al. | Apr 2012 | A1 |
20120096499 | Dasher et al. | Apr 2012 | A1 |
20120117232 | Brown et al. | May 2012 | A1 |
20120127110 | Amm et al. | May 2012 | A1 |
20120128267 | Dugan et al. | May 2012 | A1 |
20120130835 | Fan et al. | May 2012 | A1 |
20120130851 | Minnick et al. | May 2012 | A1 |
20120137318 | Kilaru et al. | May 2012 | A1 |
20120138671 | Gaede et al. | Jun 2012 | A1 |
20120139826 | Beals et al. | Jun 2012 | A1 |
20120139835 | Morrison et al. | Jun 2012 | A1 |
20120142322 | Gomez | Jun 2012 | A1 |
20120151293 | Beals | Jun 2012 | A1 |
20120151524 | Kilaru et al. | Jun 2012 | A1 |
20120153015 | Gomez et al. | Jun 2012 | A1 |
20120153017 | Bracalente et al. | Jun 2012 | A1 |
20120155838 | Gerhards et al. | Jun 2012 | A1 |
20120158919 | Aggarwal et al. | Jun 2012 | A1 |
20120159563 | Gomez et al. | Jun 2012 | A1 |
20120168493 | Worms | Jul 2012 | A1 |
20120168510 | Gratton | Jul 2012 | A1 |
20120169928 | Casagrande et al. | Jul 2012 | A1 |
20120175416 | Gomez et al. | Jul 2012 | A1 |
20120181329 | Gratton et al. | Jul 2012 | A1 |
20120182320 | Beals et al. | Jul 2012 | A1 |
20120188112 | Beals et al. | Jul 2012 | A1 |
20120188442 | Kennedy | Jul 2012 | A1 |
20120198572 | Beals et al. | Aug 2012 | A1 |
20120199643 | Minnick et al. | Aug 2012 | A1 |
20120206648 | Casagrande et al. | Aug 2012 | A1 |
20120215830 | Anguiano | Aug 2012 | A1 |
20120217292 | Gratton et al. | Aug 2012 | A1 |
20120217293 | Martch et al. | Aug 2012 | A1 |
20120218470 | Schaefer | Aug 2012 | A1 |
20120218471 | Gratton | Aug 2012 | A1 |
20120222055 | Schaefer et al. | Aug 2012 | A1 |
20120222071 | Gaede et al. | Aug 2012 | A1 |
20120222081 | Schaefer et al. | Aug 2012 | A1 |
20120293327 | Mountain | Nov 2012 | A1 |
20120311623 | Davis et al. | Dec 2012 | A1 |
20130068838 | Gomez et al. | Mar 2013 | A1 |
20130239157 | Gaede et al. | Sep 2013 | A1 |
20140046661 | Bruner | Feb 2014 | A1 |
20140076963 | Gratton et al. | Mar 2014 | A1 |
20140158762 | Gomez et al. | Jun 2014 | A1 |
Number | Date | Country |
---|---|---|
2 634 951 | Jan 2010 | CA |
1352765 | Jun 2002 | CN |
1571503 | Jan 2005 | CN |
1636371 | Jul 2005 | CN |
1675930 | Sep 2005 | CN |
101 227 581 | Jul 2008 | CN |
101253504 | Aug 2008 | CN |
10 2007 038 810 | Feb 2009 | DE |
1 021 035 | Jul 2000 | EP |
1 383 071 | Jan 2004 | EP |
1 724 695 | Nov 2006 | EP |
1 757 222 | Feb 2007 | EP |
1 768 400 | Mar 2007 | EP |
2 079 051 | Jul 2009 | EP |
2 131 289 | Dec 2009 | EP |
2 439 936 | Apr 2012 | EP |
2 565 748 | Dec 1985 | FR |
2 044 446 | Oct 1980 | GB |
2 165 129 | Apr 1986 | GB |
2 311 451 | Sep 1997 | GB |
2 325 765 | Dec 1998 | GB |
2 471 567 | Jan 2011 | GB |
2002-215768 | Aug 2002 | JP |
2007-213548 | Aug 2007 | JP |
2008 244556 | Oct 2008 | JP |
2004 0087776 | Oct 2004 | KR |
299433 | Mar 1997 | TW |
200915193 | Apr 2009 | TW |
200926075 | Jun 2009 | TW |
201032139 | Jan 2010 | TW |
201038061 | Oct 2010 | TW |
201043039 | Dec 2010 | TW |
9527275 | Oct 1995 | WO |
9741690 | Nov 1997 | WO |
0106593 | Jan 2001 | WO |
0118589 | Mar 2001 | WO |
0158146 | Aug 2001 | WO |
2005109338 | Nov 2005 | WO |
2007009005 | Jan 2007 | WO |
2009057651 | May 2009 | WO |
2009116954 | Sep 2009 | WO |
2009144536 | Dec 2009 | WO |
2010149161 | Dec 2010 | WO |
2011009055 | Jan 2011 | WO |
Entry |
---|
“Android App Reviews & Showcase Just a Tapp Away,” Android Tapp, 10pp. Found online at http://www.androidtapp.com/download-the-weather-channel-android-app-from-your-tv/, Oct. 22, 2010. |
“Can Mobile Barcodes Work on TV?,” India and Asia Pacific Mobile Industry Reports, Sep. 2009, 4 pp. Found online at http://gomonews.com/can-mobile-barcodes-work-on-tv/, Oct. 22, 2010. |
“Fox TV Uses QR Codes,” 2D Barcode Strategy, Sep. 2010, 6 pp. Found online at http://www.2dbarcodestrategy.com/2010/09/fox-tv-uses-qr-codes.html, Oct. 22, 2010. |
“Fox's Fringe Uses QR Code,” 2D Barcode Strategy, Oct. 2010, 4 pp. Found on the Internet at http://www.2dbarcodestrategy.com/2010/10/foxs-fringe-uses-qr-code.html, Oct. 22, 2010. |
“Mobile Paths: QR Codes Come to TV,” Mobile Behavior: An Omnicom Group Company, Sep. 2010, 8 pp. Found online at http://www.mobilebehavior.com/2010/09/27/mobile-paths-qr-codes-come-to-tv, Oct. 22, 2010. |
“What Can I Do with the QR Barcode,” Search Magnet Local-QR Barcode Technology, 2 pp. Found online at http://www.searchmagnetlocal.com/qr—barcode—technology.html, Oct. 22, 2010. |
Byford, D., “Universal Interactive Device,” International Business Machines Corporation, Jun. 1998, 1 page. |
Costedio, K., “Bluefly QR Codes Debut on TV,” 2 pp. Found online at http://www.barcode.com/Mobile-Barcode-news/bluefly-qr-codes-debut-on-tv.html, Oct. 22, 2010. |
Gao, J., et al., “A 2D Barcode-Based Mobile Payment System,” Multimedia and Ubiquitous Engineering, 2009, 10 pp. Found online at http://ieeexplore.ieee.org/Xplore/login.jsp?url=http%3A%2F%2Fieeexplore.ieee.org%2Fie . . . , Oct. 22, 2010. |
International Search Report and Written Opinion of PCT/US11/59977 mailed on Mar. 19, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/60002 mailed on Feb. 15, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/60094 mailed on Mar. 30, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/60104 mailed on Mar. 29, 2012, 9 pages. |
International Search Report of PCT/US11/60109 mailed on Feb. 14, 2012, 3 pages. |
International Search Report and Written Opinion of PCT/US11/60121 mailed on Feb. 14, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/61074 mailed on Jan. 6, 2012, 11 pages. |
International Search Report and Written Opinion of PCT/US11/61211 mailed on Mar. 29, 2012, 8 pages. |
International Search Report and Written Opinion of PCT/US11/61773 mailed on Feb. 21, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/61778 mailed on Mar. 2, 2012, 7 pages. |
International Search Report and Written Opinion of PCT/US11/63111 mailed on Apr. 4, 2012, 9 pages. |
International Search Report and Written Opinion of PCT/US11/64709 mailed on Apr. 10, 2012, 8 pages. |
International Search Report and Written Opinion of PCT/US2011/060098 mailed on Mar. 29, 2012, 10 pages. |
International Search Report and Written Opinion of PCT/US2011/063308 mailed on Mar. 29, 2012, 10 pages. |
International Search Report and Written Opinion of PCT/US2011/068161 mailed on Jun. 14, 2012, 19 pages. |
International Search Report and Written Opinion of PCT/US2011/068176 mailed on Mar. 29, 2012, 15 pages. |
International Search Report and Written Opinion of PCT/US2012/021657 mailed on May 23, 2012, 12 pages. |
International Search Report and Written Opinion of PCT/US2012/022405 mailed on Apr. 19, 2012, 11 pages. |
International Search Report and Written Opinion of PCT/US2012/024923 mailed on May 22, 2012, 12 pages. |
International Search Report and Written Opinion of PCT/US2012/024956 mailed on Jun. 11, 2012, 10 pages. |
International Search Report and Written Opinion of PCT/US2012/025502 mailed Jun. 8, 2012, 13 pages. |
International Search Report and Written Opinion of PCT/US2012/025607 mailed Jun. 8, 2012, 13 pages. |
International Search Report and Written Opinion of PCT/US2012/025634 mailed on May 7, 2012, 8 pages. |
International Search Report and Written Opinion of PCT/US2012/026373 mailed Jun. 13, 2012, 14 pages. |
International Search Report and Written Opinion of PCT/US2012/026722 mailed Jun. 28, 2012, 11 pages. |
Ngee, S., “Data Transmission Between PDA and PC Using WiFi for Pocket Barcode Application,” Thesis, University Teknologi Malaysia, May 2007, 126 pp. Found online at http://eprints.utm.my/6421/1/SeahYeowNgeeMFKE20007TTT.pdf, Oct. 22, 2010. |
Olson, E., “Bar Codes add Detail on Items in TV Ads,” New York Times, Sep. 2010, 3 pp. Found online at http:www.nytimes.com/2010/09/27/business/media/27bluefly.html?src=busin, Oct. 22, 2010. |
Rekimoto, J., et al., “Augment-able Reality: Situated Communication Through Physical and Digital Spaces,” Sony Computer Science Laboratory, 2002, 8 pp. Found online at Citeseer: 10.1.1.20.34[1].pdf, Oct. 22, 2010. |
Schmitz, A., et al., “ Ad-Hoc Multi-Displays for Mobile Interactive Applications,” 31st Annual Conference of the European Association for Computer Graphics (Eurographics 2010), May 2010, vol. 29, No. 2, 8 pages. |
Silverstein, B., “QR Codes and TV Campaigns Connect,” ReveNews, Sep. 2010, 5 pp. Found online at http://www.revenews.com/barrysilverstein/qr-codes-and-tv-campaigns-connect/, Oct. 22, 2010. |
Smith, L., “QR Barcodes Make History on Global TV,” 3 pp. Found online at http://lindsaysmith.com/worlds-first-mobio-mini-telethon/, Oct. 22, 2010. |
Yamanari, T., et al., “Electronic Invisible Code Display Unit for Group Work on Reminiscence Therapy,” Proceedings of the International MultiConference of Engineers and Computer Scientists 2009, vol. 1, IMECS 2009, Mar. 2009, 6 pp. Retrieved from the Internet: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.6904&rep1&type=pdf. |
Yang, C., et al., “Embedded Digital Information Integrated by Video-on-Demand System,” Proceedings of the Fourth International Conference on Networked Computing and Advanced Information Management, IEEE Computer Society, 2008, 6 pages. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Office Action mailed Mar. 9, 2012, 17 pages. |
U.S. Appl. No. 12/971,349, filed Dec. 17, 2010, Office Action mailed Nov. 10, 2011, 9 pages. |
U.S. Appl. No. 12/971,349, filed Dec. 17, 2010, Final Office Action mailed Jan. 20, 2012, 10 pages. |
U.S. Appl. No. 12/971,349, filed Dec. 17, 2010, Office Action mailed Jul. 16, 2012, 11 pages. |
U.S. Appl. No. 12/984,385, filed Jan. 4, 2011, Office Action mailed Jul. 12, 2012, 16 pages. |
U.S. Appl. No. 12/986,721, filed Jan. 7, 2011, Office Action mailed Mar. 16, 2012, 6 pages. |
U.S. Appl. No. 12/986,721, filed Jan. 7, 2011, Notice of Allowance mailed Jun. 21, 2012, 7 pages. |
U.S. Appl. No. 13/020,678, filed Feb. 3, 2011, Office Action mailed Jul. 30, 2012, 15 pages. |
U.S. Appl. No. 13/035,525, filed Feb. 25, 2011, Office Action mailed Jul. 18, 2012, 15 pages. |
Extended European Search Report for EP 12152690.9 dated Jun. 19, 2012, 9 pages. |
International Search Report and Written Opinion of PCT/US2012/026624 mailed Aug. 29, 2012, 14 pages. |
U.S. Appl. No. 12/958,073, filed Dec. 1, 2010, Office Action mailed Aug. 31, 2012, 12 pages. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Final Rejection mailed Oct. 30, 2012, 17 pages. |
U.S. Appl. No. 12/971,349, filed Dec. 7, 2010, Final Rejection mailed Oct. 24, 2012, 11 pages. |
U.S. Appl. No. 12/953,227, filed Nov. 23, 2010, Office Action mailed Nov. 7, 2012, 31 pages. |
U.S. Appl. No. 13/015,382, filed Jan. 27, 2011, Office Action Mailed Nov. 13, 2012, 7 pages. |
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011, Office Action mailed Nov. 2, 2012, 18 pages. |
U.S. Appl. No. 12/953,273, filed Nov. 23, 2010, Notice of Allowance, mailed Oct. 18, 2012, 11 pages. |
U.S. Appl. No. 13/034,482, filed Feb. 24, 2011, Office Action mailed Oct. 19, 2012, 11 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011, Office Action mailed Oct. 30, 2012, 11 pages. |
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010, Final Office Action mailed Dec. 6, 2012, 17 pages. |
U.S. Appl. No. 12/984,385, filed Jan. 4, 2011, Notice of Allowance mailed Nov. 28, 2012, 11 pages. |
U.S. Appl. No. 13/037,312, filed Feb. 28, 2011, Office Action mailed Aug. 15, 2012, 9 pages. |
International Search Report of PCT/US2012/022581 mailed on Oct. 8, 2012, 18 pages. |
International Search Report and Written Opinion of PCT/US2012/048032, mailed Oct. 16, 2012, 14 pages. |
O'Sullivan, “Can Mobile Barcodes Work on TV?,” India and Asia Pacific Mobile Industry Reports, Sep. 2009, 4 pp. Found online at http://gomonews.com/can-mobile-barcodes-work-on-tv/, Feb. 5, 2013. |
U.S. Appl. No. 12/958,073, filed Dec. 1, 2010, Notice of Allowance mailed Jan. 17, 2013, 17 pages. |
U.S. Appl. No. 12/981,244, filed December 29, 2010, Office Action mailed Dec. 21, 2012, 23 pages. |
U.S. Appl. No. 12/984,244, filed Jan. 4, 2011, Notice of Allowance mailed Nov. 28, 2012, 11 pages. |
U.S. Appl. No. 13/015,382, filed Jan. 27, 2011, Notice of Allowance mailed Feb. 22, 2013, 12 pages. |
U.S. Appl. No. 13/007,317, filed Jan. 14, 2011, Office action mailed Dec. 19, 2012, 29 pages. |
U.S. Appl. No. 13/020,678, filed Feb. 3, 2011, Notice of Allowance mailed Jan. 3, 2013, 13 pages. |
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011, Office Action mailed Jan. 11, 2013, 14 pages. |
U.S. Appl. No. 13/035,525, filed Feb. 25, 2011, Final Office Action mailed Jan. 31, 2013, 26 pages. |
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011 Office Action mailed Mar. 1, 2013, 20 pages. |
U.S. Appl. No. 13/037,312, filed Feb. 28, 2011, Final Office Action mailed Feb. 28, 2013, 18 pages. |
U.S. Appl. No. 13/037,316, filed Feb. 28, 2011, Office Action mailed Jan. 30, 2013, 21 pages. |
U.S. Appl. No. 13/037,333, filed Feb. 28, 2011 Notice of Allowance mailed Jan. 18, 2013, 27 pages. |
U.S. Appl. No. 13/673,480, filed Nov. 9, 2012 Office Action mailed Jan. 16, 2013, 27 pages. |
U.S. Appl. No. 12/964,478, filed Dec. 9, 2010, Final Office Action mailed Sep. 16, 2013, 12 pages. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Non-Final Office Action mailed Jul. 12, 2013, 22 pages. |
U.S. Appl. No. 12/965,645, filed Dec. 10, 2010, Non-Final Office Action, mailed Jul. 19, 2013, 20 pages. |
International Preliminary Report on Patentability of PCT/US2011/059977 mailed on Jun. 6, 2013, 6 pages. |
International Preliminary Report on Patentability of PCT/US2011/068161 mailed on Jul. 25, 2013, 13 pages. |
International Preliminary Report on Patentability of PCT/US2012/025502 mailed Sep. 6, 2013, 9 pages. |
Liu, Yue et al., “Recognition of QR code with mobile phones,” Control and Decision Conference, 2008. CCDC 2008. Jul. 2-4, 2008, pp. 203, 206. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Non-Final Office Action mailed Mar. 25, 2013, 17 pages. |
U.S. Appl. No. 12/981,244, filed Dec. 29, 2010, Final Office Action mailed Oct. 30, 2013, 10 pages. |
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011 Final Office Action mailed Jun. 27, 2013, 13 pages. |
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010, Final Office Action mailed Jun. 27, 2013, 11 pages. |
U.S. Appl. No. 13/006,270, filed Jan. 13, 2011, Non-Final Office Action mailed Oct. 8, 2013, 20 pages. |
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011, Non-Final Office Action mailed Dec. 17, 2013, 60 pages. |
U.S. Appl. No. 13/035,525, filed Feb. 25, 2011, Final Office Action mailed Sep. 12, 2013, 21 pages. |
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011 Final Office Action mailed Oct. 16, 2013, 28 pages. |
U.S. Appl. No. 13/037,316, filed Feb. 28, 2011, Final Office Action mailed Aug. 28, 2013, 13 pages. |
U.S. Appl. No. 13/673,480, filed Nov. 9, 2012 Final Office Action mailed Sep. 9, 2013, 10 pages. |
U.S. Appl. No. 13/673,480, filed Nov. 9, 2012 Notice of Allowance mailed Nov. 12, 2013, 16 pages. |
U.S. Appl. No. 13/475,794, filed May 18, 2012 Non-Final Office Action mailed Sep. 18, 2013, 19 pages. |
U.S. Appl. No. 12/964,478, filed Dec. 9, 2010, Non-Final Office Action mailed Mar. 26, 2013, 19 pages. |
U.S. Appl. No. 12/953,227, filed Nov. 23, 2010, Final Office Action mailed May 24, 2013, 17 pages. |
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010, Non-Final Rejection mailed May 15, 2013, 30 pages. |
U.S. Appl. No. 13/014,591, Notice of Allowance mailed May 24, 2013, 32 pages. |
U.S. Appl. No. 13/007,317, Notice of Allowance mailed May 13, 2013, 16 pages. |
U.S. Appl. No. 13/031,115, Notice of Allowance mailed Apr. 16, 2013, 24 pages. |
U.S. Appl. No. 13/034,482, filed Feb. 24, 2011, Final Office Action mailed Apr. 25, 2013, 19 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011, Final Rejection mailed Mar. 29, 2013, 20 pages. |
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010, Final Office Action mailed Apr. 18, 2013, 14 pages. |
U.S. Appl. No. 13/035,525, filed Feb. 25, 2011, Non-Final Office Action mailed May 15, 2013, 15 pages. |
First Examination Report from European Patent Office dated Feb. 4, 2015 for EP 12716751.8, 4 pages. |
Office Action dated Nov. 12, 2014 for Mexican Patent Application No. MX/a/2013/009794 is not translated into English, 2 pages. |
Office Action dated Jan. 28, 2015 for Mexican Patent Application No. MX/a/2013/006973 is not translated into English, 3 pages. |
Office Action from European Patent Office for Application No. 12716728.6 dated Feb. 26, 2015, 4 pages. |
European Search Report for EP 11844504 dated Feb. 24, 2015, 10 pages. |
U.S. Appl. No. 14/179,336, filed Feb. 12, 2014 Notice of Allowance mailed Feb. 18, 2015, 15 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011 Non Final Rejection mailed Feb. 17, 2015, 57 pages. |
Office Action dated Feb. 18, 2015 for Mexican Patent Application No. MX/a/2013/009794, 1 page. |
Office Action dated Feb. 10, 2015 for Mexican Patent Application No. MX/a/2013/006770, 2 pages. |
Office Action dated Feb. 6, 2015 for Mexican Patent Application No. MX/a/2013/006520, 2 pages. |
Office Action and Search Report for ROC (Taiwan) Patent Application No. 100149344 issued Jan. 23, 2015, 8 pages. |
Office Action for European Patent Application No. 12707435.9 dated Mar. 12, 2015, 6 pages. |
U.S. Appl. No. 12/953,227, filed Nov. 23, 2010, Non Final Office action mailed Mar. 24, 2015, 39 pages. |
U.S. Appl. No. 13/006,270, filed Jan. 13, 2011, Final Office Action mailed Mar. 23, 2014, 51 pages. |
Extended European Search Report for EP 11850819 dated Mar. 17, 2014, 2 pages. |
International Preliminary Report on Patentability of PCT/US2012/048032 mailed on Apr. 3, 2014, 6 pages. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Non-Final Office Action mailed Feb. 13, 2014, 21 pages. |
U.S. Appl. No. 12/971,349, filed Dec. 7, 2010, Notice of Allowance mailed Oct. 02, 2013, 24 pages. |
U.S. Appl. No. 12/965,645, filed Dec. 10, 2010, Final Office Action, mailed Mar. 18, 2014, 24 pages. |
U.S. Appl. No. 13/010,557, filed Jan. 20, 2011, Final Rejection mailed Jan. 16, 2014, 17 pages. |
U.S. Appl. No. 13/010,557, filed Jan. 20, 2011, Non-Final Rejection mailed Aug. 5, 2013, 17 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011, Non Final Rejection mailed Mar. 6, 2014, 20 pages. |
U.S. Appl. No. 13/037,312, filed Feb. 28, 2011, Notice of Allowance mailed Jun. 13, 2013, 10 pages. |
U.S. Appl. No. 13/968,611, filed Aug. 16, 2013, Non-Final Office Action mailed Jan. 17, 2014, 21 pages. |
Extended European Search Report for EP 11842890.3 dated Mar. 26, 2014, 8 pages. |
Extended European Search Report for EP 11846486 dated Mar. 26, 2014, 5 pages. |
Extended European Search Report for EP 11852630 dated Jun. 30, 2014, 7 pages. |
International Preliminary Report on Patentability of PCT/US2011/063111 mailed Jun. 13, 2013, 8 pages. |
International Preliminary Report on Patentability of PCT/US2012/048032 mailed Apr. 3, 2014, 6 pages. |
Kato et al, “2D barcodes for mobile phones”, Mobile Technology, Applications and Systems, 2005 2nd International Conference on Guangzhou, China Nov. 15-17, 2005, Piscataway, NJ, USA, IEEE, Piscataway, NJ, USA, Nov. 15, 2005, pp. 8pp. 8, XP031887368, DOI: 10.1109/MTAS.2005.207166; ISBN: 978-981-05-4573-4, 8 pages. |
Office Action and Search Report for ROC (Taiwan) Patent Application No. 10014870 dated May 7, 2014, issued in the corresponding foreign application, 9 pages. |
Office Action and Search Report for ROC (Taiwan) Patent Application No. 100142966 dated May 27, 2014, 6 pages. |
Office Action for European Patent Application No. 12719817.4 dated Jun. 23, 2014 issued in the corresponding foreign application, 5 pages. |
U.S. Appl. No. 14/179,336, filed Feb. 12, 2014, Non-Final Office Action mailed May 22, 2014, 14 pages. |
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010, Notice of Allowance mailed Jul. 16, 2014, 15 pages. |
U.S. Appl. No. 12/981,244, filed Dec. 29, 2010, Notice of Allowance mailed Mar. 25, 2014, 17 pages. |
U.S. Appl. No. 12/965,645, filed Dec. 10, 2010, Notice of Allowance, mailed Jun. 20, 2014, 35 pages. |
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011, Final Office Action mailed Jul. 11, 2014, 43 pages. |
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010, Non-Final Office Action mailed Jun. 6, 2014, 19 pages. |
U.S. Appl. No. 13/006,270, filed Jan. 13, 2011, Final Office Action mailed May 9, 2014, 41 pages. |
U.S. Appl. No. 13/968,611, filed Aug. 16, 2013, Notice of Allowance mailed May 2, 2014, 40 pages. |
Jung, Eui-Hyun et al., “A Robust Digital Watermarking System Adopting 2D Barcode against Digital Piracy on P2P Network,” IJCSNS International Journal of Computer Science and Network Security, vol. 6, No. 10, Oct. 2006, 6 pages. |
First Office Action by the Mexican Institute of Industrial Property for Mexican Patent Application No. MX/a/2013/00988 dated Aug. 14, 2014, 3 pages. |
International Preliminary Report on Patentability for PCT/US2011/060002 mailed Jun. 6, 2013, 6 pages. |
International Preliminary Report on Patentability for PCT/US2011/060094 mailed Jun. 20, 2013, 6 pages. |
International Preliminary Report on Patentability for PCT/US2011/060121 mailed Jun. 20, 2013, 6 pages. |
International Preliminary Report on Patentability for PCT/US2011/061211 mailed Jul. 4, 2013, 7 pages. |
International Preliminary Report on Patentability for PCT/US2011/061773 mailed Jun. 6, 2013, 6 pages. |
International Preliminary Report on Patentability for PCT/US2011/061778 mailed Jul. 11, 2013, 6 pages. |
International Preliminary Report on Patentability for PCT/US2011/060098 mailed Jun. 13, 2013, 9 pages. |
International Preliminary Report on Patentability for PCT/US2011/063308 mailed Jul. 18, 2013, 9 pages. |
International Preliminary Report on Patentability for PCT/US2012/022581 mailed Aug. 8, 2013, 12 pages. |
International Preliminary Report on Patentability for PCT/US2012/022405 mailed Aug. 8, 2013, 7 pages. |
International Preliminary Report on Patentability for PCT/US2012/024923 mailed Aug. 29, 2013, 8 pages. |
International Preliminary Report on Patentability for PCT/US2012/024956 mailed Aug. 29, 2013, 7 pages. |
International Preliminary Report on Patentability for PCT/US2012/025607 mailed Sep. 12, 2013, 8 pages. |
International Preliminary Report on Patentability for PCT/US2012/025634 mailed Sep. 6, 2013, 5 pages. |
International Preliminary Report on Patentability for PCT/US2012/026373 mailed Sep. 12, 2013, 10 pages. |
International Preliminary Report on Patentability for PCT/US2012/026624 mailed Sep. 12, 2013, 12 pages. |
International Preliminary Report on Patentability for PCT/US2011/060109 mailed Jun. 20, 2013, 7 pages. |
Office Action of the Intellectual Property Office for ROC Patent App. No. 101101486 dated Aug. 5, 2014, 4 pages. |
The First Office Action for Mexican Patent Application No. MX/a/2013/006262 is not translated into English. This document is from prosecution of the corresponding foreign matter for which we do not have a translation. Dated Aug. 7, 2014, 2 pages. |
Publication of PCT/US2011/059977 by the India Controller General of Patents Designs and Trademarks as India Patent Publication No. 4694/CHENP/2013 A on Sep. 5, 2014, 1 page. |
Publication of PCT/US2012/025634 by the India General Patents Designs and Trademarks as India Patent Publication No. 6967/CHENP/2013 A on Aug. 1, 2014, 1 page. |
U.S. Appl. No. 13/034,482, filed Feb. 24, 2011 Notice of Allowance mailed Aug. 29, 2014, 45 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011 Final Rejection mailed Aug. 27, 2014, 38 pages. |
U.S. Appl. No. 13/006,270, filed Jan. 13, 2011 Non-Final Office Action mailed Sep. 12, 2014, 41 pages. |
Office Action of the Intellectual Property Office for ROC Patent App. No. 100143194 dated Sep. 23, 2014, 10 pages. |
Office Action of the Intellectual Property Office for ROC Patent App. No. 100142978 dated Sep. 23, 2014, 9 pages. |
The First Office Action dated Sep. 11, 2014 for Mexican Patent Application No. MX/a/2013/007672 is not translated into English, 2 pages. |
The Notice of Allowance for Mexican Patent Application No. MX/a/2013/009882 is not translated into English, 1 page. |
U.S. Appl. No. 14/179,336, filed Feb. 12, 2014 Final Office Action mailed Dec. 1, 2014, 30 pages. |
U.S. Appl. No. 13/475,794, filed May 18, 2012 Non-Final Office Action mailed Nov. 21, 2014, 33 pages. |
U.S. Appl. No. 13/302,717, filed Nov. 22, 2011 Non-Final Rejection mailed Dec. 18, 2014, 71 pages. |
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011, Non-Final Office Action mailed Feb. 6, 2015, 56 pages. |
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011 Non-Final Office Action mailed Nov. 3, 2014, 33 pages. |
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010 Non-Final Rejection mailed Dec. 19, 2014, 30 pages. |
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010 Final Office Action mailed Dec. 3, 2014, 19 pages. |
First Examination Report from European Patent Office dated May 18, 2015 for EP 11849496.2, 7 pages. |
European Office Action for EP 11842890.3 dated Mar. 13, 2015, 8 pages. |
European Search Report for EP 11855065 dated Mar. 6, 2014, 6 pages. |
Office Action for EP 11855065 dated Mar. 13, 2015, 6 pages. |
Notice of Allowance by the Mexican Institute of Industrial Property for Mexican Patent Application No. MX/a/2013/009881 dated Jan. 12, 2015, 1 page. |
First Office Action for CN 201180065044.7 issued Feb. 13, 2015 by the State Intellectual Property Office, 4 pages. |
U.S. Appl. No. 13/475,794, filed May 18, 2012 Final Office Action mailed Jun. 1, 2015, 45 pages. |
U.S. Appl. No. 13/302,717, filed Nov. 22, 2011 Final Rejection mailed May 8, 2015, 44 pages. |
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011 Final Office Action mailed May 4, 2015, 54 pages. |
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011 Final Office Action mailed May 13, 2015, 34 pages. |
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010 Notice of Allowance mailed May 28, 2015, 20 pages. |
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010 Non-Final Office Action mailed May 14, 2015, 21 pages. |
Office Action from European Patent Office for Application No. 11852630.0 dated May 12, 2015, 7 pages. |
Office Action from State Intellectual Property Office for CN Appln. No. 201180056242.7 received Jun. 17, 2015, 10 pages. |
Office Action dated Apr. 22, 2015 for Mexican Patent Application No. MX/a/2013/009883, 2 pages. |
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011, Final Office Action mailed Jul. 17, 2015, 63 pages. |
Notice of Allowance and search report for ROC (Taiwan) Patent Application No. 101106288 received May 29, 2015, 9 pages. |
The Second Office Action dated Jun. 1, 2015 for Mexican Patent Application No. MX/a/2013/007672 is not translated into English, 2 pages. |
The First Office Action dated Jul. 13, 2015 for Mexican Patent Application No. MX/a/2013/009791 is not translated into English, 2 pages. |
Office Action and Search Report from the State Intellectual Property Office for CN Pat. Appln. No. 201180066584.7 issued on Jul. 10, 2015, 12 pages. |
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011 Non Final Rejection mailed Sep. 11, 2015, 65 pages. |
U.S. Appl. No. 13/864,474, filed Apr. 17, 2013 Non Final Office Action mailed Aug. 11, 2015, 59 pages. |
Number | Date | Country | |
---|---|---|---|
20120131416 A1 | May 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12953227 | Nov 2010 | US |
Child | 13192287 | US |