Facilitating user support of electronic devices using dynamic matrix code generation

Information

  • Patent Grant
  • 9792612
  • Patent Number
    9,792,612
  • Date Filed
    Tuesday, November 23, 2010
    14 years ago
  • Date Issued
    Tuesday, October 17, 2017
    7 years ago
Abstract
An electronic device may derive information specific to the device, dynamically generate a matrix code that includes the information as well as user support information, and transmit the dynamically generated code to a display. When a user captures the matrix code with a reader device, the reader device may decode (or use a back end server to decode) the specific information specific and the user support information and initiate a user support request. Thus, user support for electronic devices may be facilitated utilizing dynamically generated matrix codes, such as (but not limited to) QR codes. In response to the initiated user support request, user support may then be provided for the user. Problems may be automatically taken care of for the user, tutorials may be provided for the user, one or more notifications may be provided to the user, service calls may be scheduled for the user, and so on.
Description
FIELD OF THE INVENTION

This disclosure relates generally to user support of electronic devices, and more specifically to electronic devices dynamically generating matrix codes that include information specific to the electronic device as well as user support information which can then be displayed and scanned to initiate user support for a user of the electronic device.


SUMMARY

The present disclosure discloses systems and methods for helping provide user support for electronic devices utilizing dynamically generated matrix codes, such as (but not limited to) QR codes. An electronic device may derive information specific to the device (which may be related to the operation of the device), dynamically generate a matrix code that includes the information specific to the device and user support information, and transmit the dynamically generated matrix code to a display device. When a user captures the matrix code with a reader device, the reader device may decode (or use a back end server to decode) the information specific to the electronic device and the user support information and initiate a user support request.


In response to the initiated user support request, user support may then be provided for the user. Problems may be automatically taken care of for the user, tutorials may be provided for the user, service calls may be scheduled for the user, and so on. The user may also be provided notifications (via the electronic device, the reader device, and/or other communication devices) that the user support request has been received, notifications regarding the contents of the user support request, notifications regarding scheduled service calls, notifications regarding potential problem fixes, and various other notifications and/or other responses.


The information specific to the electronic device may include a variety of different information that is specific to the operation of the electronic device. such as electronic device identifiers, electronic device configuration, error codes for errors that have occurred during electronic device operation, account information for one or more customer accounts associated with the electronic device, a location of the electronic device, and so on. The user support information for the electronic device may include a variety of information that may be utilized to initiate user support requests such as a web site address to which to the information specific to the electronic device, a network address for a user support provider response system to which the information specific to the electronic device may be transmitted, an identifier for an application resident on the reader device to which the information specific to the electronic device may be passed, and so on.


In some implementations, the matrix code may be dynamically generated upon the occurrence of an error. However, in other implementations, the matrix code may be generated in response to receiving a user input. In various implementations, the electronic device may transmit the matrix code by themselves to a display device such that the matrix code will be the only element displayed on the display device at a particular time. In various other implementations, the electronic device may combine the matrix code with one or more images that are being transmitted to the display device and transmit the combination for simultaneous display.


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.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating a system for facilitating user support of an electronic device using dynamic matrix code generation.



FIG. 2 is a flow chart illustrating a method for facilitating user support of an electronic device using dynamic matrix code generation. This method may be performed by the system of FIG. 1.



FIGS. 3A-3B are diagrams illustrating a first example system that facilitates user support for a television receiver. The system may be the system of FIG. 1.



FIGS. 4A-4C are diagrams illustrating a second example system that facilitates user support for an automobile. The system may be the system of FIG. 1.



FIGS. 5A-5C are diagrams illustrating a third example system that facilitates user support for a security system. The system may be the system of FIG. 1.





DETAILED DESCRIPTION OF THE EMBODIMENTS

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. Users of electronic devices frequently utilize user support provided by manufacturers of the electronic devices, retailers of electronic devices, and so on in order to operate the electronic devices. This is particularly the case when errors occur during the operation of an electronic device. When an error does occur during the operation of an electronic device, a user of the electronic device may contact (such as by telephone, email, and so on) a user support provider in order to request user support from the provider. Such a user support provider may include the manufacturer or retailer of the electronic device, a third party contracted to provide user support for the electronic device, and so on.


However, requesting user support for an electronic device may be as complex for a user as operation of the electronic device itself. Often, a user may be required to locate contact information for a user support provider and wait on hold for extensive periods of time or wait extensive periods of time for a response. Further, the user support provider may need the user to provide extensive amounts of information regarding the electronic device (such as customer account information, electronic device identifiers, electronic device configuration information, detailed descriptions of errors, and so on) which may be burdensome for the user or beyond their level of understanding. As such, the user's ability to obtain desired user support and/or ability to operate the electronic device may be frustrated.


The present disclosure discloses systems and methods for facilitating user support of electronic devices using dynamic matrix code generation. An electronic device may derive information specific to the electronic device. The information specific to the electronic device may be related to the operation of the electronic device. The electronic device may then dynamically generate one or more matrix codes, such as (but not limited to) QR codes, that include the information specific to the electronic device. Further, the dynamically generated matrix code may include user support information for the electronic device. The electronic device may then transmit the dynamically generated matrix code to a display device (which may be integrated into the electronic device). When the user of the electronic device utilizes a reader device (such as a smart phone, a mobile computing device, and so on) to detect the matrix code, the reader device may decode (or use a back end server to decode) the information specific to the electronic device and the user support information and may initiate a user support request based on the decoded information.



FIG. 1 is a block diagram illustrating a system 100 for facilitating user support of an electronic device using dynamic matrix code generation. The system 100 may include a electronic device 101 (which may be any kind of electronic device such as a television, a television receiver, a digital video recorder, a digital video disc player, an automobile, a computing device, a telephone, a kitchen appliance, a video game system, a security system, and so on), at least one display device 102 (which may be any kind of display device such as a cathode ray tube display, a liquid crystal display, a television, a computer monitor, and so on), and a reader device 103 (which may be any kind of device capable of detecting and decoding a matrix code such as a telephone equipped with a camera, a mobile computing device that includes a camera, and so on). The system may also include a user support provider 104.


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.



FIG. 2 illustrates a method 200 for facilitating user support of an electronic device using dynamic matrix code generation. The method 200 may be performed by the system 100 of FIG. 1. The flow begins at block 201 and proceeds to block 202 where the processing unit 105 of the electronic device 101 derives the information specific to the electronic device. The flow then proceeds to block 203 where the processing unit dynamically generates a matrix code (such as a QR code) that includes the information specific to the electronic device and the user support information. Then, the flow proceeds to block 204 where the processing unit transmits the dynamically generated matrix code to the display device 102 via the output component 107 before the flow proceeds to block 205.


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.



FIGS. 3A-3B illustrate a first example system 300A-300B that facilitates user 301A-301B support for a television receiver. As illustrated in FIG. 3A, the system 300A includes a television 302A (which incorporates a television receiver for receiving television programming from a programming provider for the television 302A) and a user 301A. In this example, the television detects an error condition because the television receiver is not receiving a signal from the programming provider. As such, the television dynamically determines information specific to the television which includes a physical address associated with the television receiver, a network address for the television receiver, an identifier for the television receiver, an account number for the programming provider account associated with the television receiver, and an error code corresponding to the error condition of no signal. The television dynamically generates a QR code 306A that includes the dynamically determined information specific to the television. Further, the television includes user support information in the QR code specifying to transmit the information specific to the television to a customer support system of the programming provider (such as via a web interface). The television then displays the QR code on the screen 303A of the television. In order to request user support, the user takes a picture of the QR code on the screen of the television with a cellular phone 304A that is executing a QR code reader program. The QR code reader program detects and decodes the QR code. Based on the decoded user support information, the cellular phone then transmits the decoded information specific to the television to the customer support system of the programming provider.


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. FIG. 3B depicts a response from the programming provider received by the cellular phone 304B and displayed on a display screen 305B of the cellular phone.



FIGS. 4A-4C illustrate a second example system 400A-400C that facilitates user 401A-401C support for an automobile 402A-402C. As illustrated in FIG. 4A, the system 400A includes an automobile 402A and a user 401A. In this example, the automobile detects an error condition because the engine of the automobile has locked up. As such, the automobile dynamically determines information specific to the automobile which includes a global position system location for the automobile, name information for the owner of the automobile, account information for a roadside assistance account associated with the automobile, and an error code corresponding to the error condition of locked engine. The automobile dynamically generates a QR code 406A that includes the dynamically determined information specific to the automobile. Further, the automobile includes user support information in the QR code specifying to transmit the information specific to the automobile to a roadside assistance system (such as via a web interface). The automobile then displays the QR code on a dashboard display screen 503A of the automobile. In order to request user support, the user takes a picture of the QR code on the dashboard display screen with a personal digital assistant 404A that is executing a QR code reader program. The QR code reader program detects and decodes the QR code. Based on the decoded user support information, the personal digital assistant then transmits the decoded information specific to the automobile to the roadside assistance system.


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. FIG. 4B depicts a response from the roadside assistance system received by the personal digital assistant 404B and displayed on a display screen 405B of the personal digital assistant. As the response indicates, a telephone service representative from roadside assistance will call the user 401B within ten minutes to either help the user troubleshoot the problem, send out a mechanic, call a tow truck, and so on. FIG. 4C depicts the user 401C speaking to the telephone service representative when the telephone service representative makes the scheduled telephone service call to the personal digital assistant 404C.



FIGS. 5A-5C illustrate a third example system 500A-500C that facilitates user support for a security system 502A-502C. As illustrated in FIG. 5A, the system 500A includes a security system 502A and a user 501A. In this example, the user may have forgotten a password stored by the security system and may have pressed a button for recovering the password. As such, the security system dynamically determines information specific to the security system which includes the password to recover, one or more passkey questions, and answers to the one or more passkey questions (any of which may be encrypted). The security system dynamically generates a QR code 506A that includes the dynamically determined information specific to the security system. Further, the security system includes user support information in the QR code identifying a password recovery program to initiate and supply with the information specific to the security system. The security system then displays the QR code on a control panel display screen 503A of the security system. In order to request user support, the user takes a picture of the QR code on the control panel display screen with a mobile computing device 504A that is executing a QR code reader program. The QR code reader program detects and decodes the QR code. Based on the decoded user support information, the mobile computing device initiates the password recovery program and passes the program the decoded information specific to the security system.


As illustrated in FIG. 5B, the password recovery program presents the user 501B with one or more of the passkey questions from the decoded information specific to the security system via a display screen 505B of the mobile computing device 504B, receives responses to the one or more passkey questions from the user, and compares the received answers to the decoded information specific to the security system. If the responses match the answers, the password recovery program presents the password to the user via the display screen 505C of the mobile computing device 504C, as illustrated in FIG. 5C.


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.

Claims
  • 1. A method for facilitating user support of electronic devices using dynamic matrix code generation, the method comprising: detecting, by an electronic device comprising a television receiver, an error condition experienced by the television receiver, the error condition corresponding to an error in an operation of the television receiver, where the electronic device detects the error condition without receiving an indication of the error condition from a remote provider that is remote from the electronic device;consequent to the detecting of the error condition, deriving, by the electronic device without receiving a signal from the remote provider, information specific to the television receiver, the information derived to specify i) an error code corresponding to the error in the operation of the television receiver, ii) a television receiver identifier of the television receiver, and iii) a customer identifier related to the electronic device;dynamically generating, utilizing the electronic device, at least one matrix code wherein the at least one matrix code includes the information specific to the television receiver and electronic device user support information; andtransmitting, utilizing the electronic device, the at least one matrix code to at least one display device wherein the at least one matrix code is decodable by at least one reader device that optically detects the at least one matrix code displayed on the at least one display device to initiate an electronic device user support request.
  • 2. The method of claim 1, wherein the at least one matrix code comprises at least one QR code.
  • 3. The method of claim 1, wherein the electronic device user support information includes information for transmitting the information specific to the television receiver to a user support provider from the at least one reader device.
  • 4. The method of claim 3, further comprising receiving a user support response from the user support provider that was transmitted in response to the transmitted information specific to the television receiver.
  • 5. The method of claim 4, wherein the user support response includes scheduling information regarding a service call for the user support provider to provide user support for the electronic device.
  • 6. The method of claim 1, wherein said operation of transmitting, utilizing the electronic device, the at least one matrix code to the at least one display device further comprises: combining the at least one matrix code with at least one image; andtransmitting the combination of the at least one matrix code and the at least one image to the at least one display device.
  • 7. The method of claim 1, wherein the electronic device performs said operation of dynamically generating the at least one matrix code upon occurrence of at least one electronic device malfunction.
  • 8. The method of claim 1, wherein the information specific to the television receiver includes at least one encoded password related to usage of the electronic device and the electronic device user support information includes information for recovering the at least one encoded password.
  • 9. An electronic device comprising a television receiver, the electronic device including: at least one processing unit that: detects an error condition experienced by the television receiver, the error condition corresponding to an error in an operation of the television receiver, where the electronic device detects the error condition without receiving an indication of the error condition from a remote provider that is remote from the electronic device;consequent to the detecting of the error condition, derives, without receiving a signal from the remote provider, information specific to the television receiver, the information derived to specify i) an error code corresponding to the error in the operation of the television receiver, ii) a television receiver identifier of the television receiver, and iii) a customer identifier related to the electronic device; andat least one output component, communicably coupled to the at least one processing unit and at least one display device;wherein the at least one processing unit dynamically generates at least one matrix code and transmits the at least one matrix code to at least one display device via the at least one output component wherein the at least one matrix code includes the information specific to the television receiver and electronic device support information and the at least one matrix code is decodable by at least one reader device that optically detects the at least one matrix code displayed on the at least one display device to initiate an electronic device user support request.
  • 10. The electronic device of claim 9, wherein the electronic device support information includes information for transmitting the information specific to the television receiver to a user support provider from the at least one reader device.
  • 11. The electronic device of claim 9, wherein the at least one matrix code comprises at least one QR code.
  • 12. The electronic device of claim 9, wherein the at least one processing unit transmits the at least one matrix code to the at least one display device via the at least one output component by combining the at least one matrix code with at least one image transmitting the combination of the at least one matrix code and the at least one image to the at least one display device via the at least one output component.
  • 13. The electronic device of claim 9, wherein the at least one processing unit dynamically generates the at least one matrix code upon occurrence of at least one electronic device operational error.
  • 14. The electronic device of claim 9, wherein the information specific to the television receiver includes at least one encoded password related to usage of the electronic device and the electronic device support information includes information for recovering the at least one encoded password.
  • 15. A system for facilitating user support of electronic devices using dynamic matrix code generation, comprising: an electronic device comprising a television receiver, the electronic device including: at least one processing unit that: detects an error condition experienced by the television receiver, the error condition corresponding to an error in an operation of the television receiver, where the electronic device detects the error condition without receiving an indication of the error condition from a remote provider that is remote from the electronic device;consequent to the detecting of the error condition, derives, without receiving a signal from the remote provider, information specific to the television receiver, the information derived to specify i) an error code corresponding to the error in the operation of the television receiver, ii) a television receiver identifier of the television receiver, and iii) a customer identifier related to the electronic device; andat least one output component;wherein the at least one processing unit dynamically generates at least one matrix code and transmits the at least one matrix code to the at least one display device via the at least one output component wherein the at least one matrix code includes the information specific to the television receiver and electronic device support information; andat least one reader device, comprising: at least one optical input device that detects the at least one matrix code displayed on the at least one display device;at least one processing unit that decodes the information specific to the television receiver and the electronic device support information from the detected at least one matrix code;wherein the at least one processing unit initiates an electronic device user support request based on the decoded information specific to the television receiver and the electronic device support information.
  • 16. The system of claim 15, further comprising at least one user support provider wherein the at least one reader device initiates the electronic device user support request by transmitting the information specific to the television receiver to the at least one user support provider based on the electronic device support information.
  • 17. The system of claim 16, wherein the at least one user support provider transmits a user support response to a user of the electronic device in response to receiving the information specific to the television receiver from the at least one reader device.
  • 18. The system of claim 17, wherein the user support response includes scheduling information regarding a service call for the user support provider to provide user support for the electronic device.
  • 19. The system of claim 15, wherein the information specific to the television receiver includes at least one encoded password related to usage of the electronic device and the electronic device support information includes information for recovering the at least one encoded password.
US Referenced Citations (304)
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
5929849 Kikinis Jul 1999 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 Xing 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
9280515 Gaede et al. Mar 2016 B2
9329966 Dugan et al. May 2016 B2
9367669 Gratton Jun 2016 B2
9596500 Gomez et al. Mar 2017 B2
20010037297 McNair Nov 2001 A1
20010052133 Pack et al. Dec 2001 A1
20020011521 Lahey et al. Jan 2002 A1
20020027612 Brill et al. Mar 2002 A1
20020049980 Hoang Apr 2002 A1
20020065728 Ogasawara May 2002 A1
20020112250 Koplar et al. Aug 2002 A1
20020195495 Melick et al. Dec 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
20030125092 Burnhouse 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
20040049672 Nollet et al. Mar 2004 A1
20040260850 Yu et al. Dec 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
20050258250 Melick et al. Nov 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
20060090179 Hsu et al. Apr 2006 A1
20060095286 Kimura May 2006 A1
20060124742 Rines et al. Jun 2006 A1
20060174317 Onomatsu et al. Aug 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 Abernathy et al. Jun 2007 A1
20070159522 Neven Jul 2007 A1
20070174198 Kasahara Jul 2007 A1
20070192723 Anzelde et al. Aug 2007 A1
20070200335 Tuschel Aug 2007 A1
20070205596 Mizuno et al. Sep 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
20090196456 Bisti et al. Aug 2009 A1
20090200367 Arnouse Aug 2009 A1
20090212112 Li Aug 2009 A1
20090212113 Chiu et al. Aug 2009 A1
20090234570 Sever Sep 2009 A1
20090250512 Deck et al. Oct 2009 A1
20090254954 Jeong Oct 2009 A1
20090293088 Mukerji et al. Nov 2009 A1
20090293110 Koga Nov 2009 A1
20090294538 Wihlborg et al. Dec 2009 A1
20090300673 Bachet 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 Onogi Jan 2010 A1
20100004984 Beyabani 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
20100131373 Kubasov 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
20110007218 Moran et al. 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
20110296046 Arya et al. Dec 2011 A1
20110314485 Abed Dec 2011 A1
20110321114 Newell 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
20120130835 Fan et al. May 2012 A1
20120130851 Minnick et al. May 2012 A1
20120131416 Dugan 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
20160066050 Gerhards et al. Mar 2016 A1
Foreign Referenced Citations (58)
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
1839398 Sep 2006 CN
101 227 581 Jul 2008 CN
101253504 Aug 2008 CN
101 355 685 Jan 2009 CN
101 409 027 Apr 2009 CN
101 873 467 Oct 2010 CN
101 894 113 Nov 2010 CN
101 895 722 Nov 2010 CN
23 36 711 Feb 1975 DE
10 2007 038 810 Feb 2009 DE
1 021 035 Jul 2000 EP
1 383 071 Jan 2004 EP
1 555 808 Jul 2005 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
4698CHENP2013 Jun 2016 IN
7734CHENP2013 Jun 2016 IN
2002-215768 Aug 2002 JP
3929450 Jun 2007 JP
2007-213548 Aug 2007 JP
2008 244556 Oct 2008 JP
2009-140204 Jun 2009 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
2004019442 Mar 2004 WO
2005109338 Nov 2005 WO
2007009005 Jan 2007 WO
2009056897 May 2009 WO
2009057651 May 2009 WO
2009116954 Sep 2009 WO
2009144536 Dec 2009 WO
2010149161 Dec 2010 WO
2011009055 Jan 2011 WO
0158146 Aug 2011 WO
Non-Patent Literature Citations (298)
Entry
U.S. Appl. No. 13/037,316, filed Feb. 28, 2011.
U.S. Appl. No. 13/037,333, filed Feb. 28, 2011.
U.S. Appl. No. 13/037,312, filed Feb. 28, 2011.
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011.
U.S. Appl. No. 13/302,717, filed Nov. 22, 2011.
U.S. Appl. No. 13/192,287, filed Jul. 27, 2011.
U.S. Appl. No. 12/961,369, filed Mar. 9, 2012, Non Final Office Action.
U.S. Appl. No. 12/971,349, filed Nov. 10, 2011, Non-Final Office Action.
U.S. Appl. No. 12/971,349, filed Jan. 20, 2012, Final Office Action.
U.S. Appl. No. 12/971,349, filed Jul. 16, 2012, Non-Final Office Action.
U.S. Appl. No. 12/984,385, filed Jul. 12, 2012, Non-Final Office Action.
U.S. Appl. No. 12/986,721, filed Mar. 16, 2012, Non-Final Office Action.
U.S. Appl. No. 12/986,721, filed Jun. 21, 2012, Notice of Allowance.
U.S. Appl. No. 13/020,678, filed Jul. 30, 2012, Non-Final Office Action.
U.S. Appl. No. 13/035,525, filed Jul. 18, 2012, Non-Final Office Action.
U.S. Appl. No. 12/953,273, filed Nov. 23, 2010.
U.S. Appl. No. 12/958,073, filed Dec. 1, 2010.
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010.
U.S. Appl. No. 12/961,369, filed Dec. 6, 2010.
U.S. Appl. No. 12/964,478, filed Dec. 9, 2010.
U.S. Appl. No. 12/965,645, filed Dec. 10, 2010.
U.S. Appl. No. 12/971,349, filed Dec. 17, 2010.
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010.
U.S. Appl. No. 12/981,244, filed Dec. 29, 2010.
U.S. Appl. No. 12/984,385, filed Jan. 4, 2011.
U.S. Appl. No. 12/986,721, filed Jan. 7, 2011.
U.S. Appl. No. 13/006,270, filed Jan. 13, 2011.
U.S. Appl. No. 13/007,317, filed Jan. 14, 2011.
U.S. Appl. No. 13/010,557, filed Jan. 20, 2011.
U.S. Appl. No. 13/014,591, filed Jan. 26, 2011.
U.S. Appl. No. 13/015,382, filed Jan. 27, 2011.
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011.
U.S. Appl. No. 13/020,678, filed Feb. 3, 2011.
U.S. Appl. No. 13/028,030, filed Feb. 15, 2011.
U.S. Appl. No. 13/031,115, filed Feb. 18, 2011.
U.S. Appl. No. 13/034,482, filed Feb. 24, 2011.
U.S. Appl. No. 13/035,525, filed Feb. 25, 2011.
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011.
U.S. Appl. No. 12/961,369, filed Mar. 9, 2012, Non-Final Office Action.
“Android App Reviews & Showcase Just a Tapp Away,” Android Tapp, 10 pp. 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://www.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.
Kartina Costedio, “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.
Smith, Lindsay, “Barcodes Make History on Global TV”, 3 pp. Found online at http://www.lindsaysmith.com/worlds-first-mobio-mini-telethon/, Oct. 22, 2010.
Nghee, Seah Y. , “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, Elizabeth, “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=busln, Oct. 22, 2010.
Rekimoto, Jun 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.
Silverstein, Barry, “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.
Yamanari, Tomofumi 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. I, IMECS 2009, Mar. 2009, 6 pp. Retrieved from Internet: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.148.6904&rep1&type=pdf.
Byford, D., “Universal Interactive Device,” International Business Machines Corporation, Jun. 1998, 1 page.
International Search Report and Written Opinion of PCT/US11/60094 mailed on Mar. 30, 2012, 7 pages.
International Search Report of PCT/US11/60109 mailed on Feb. 14, 2012, 3 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/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.
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.
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/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, 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.
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/60104 mailed on Mar. 29, 2012, 9 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/068176 mailed on Mar. 29, 2012, 15 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.
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/986,721, filed Jan. 7, 2011, Office Action mailed Mar. 16, 2012, 6 pages.
International Search Report of PCT/US2012/022581 mailed on Oct. 8, 2012, 18 pages.
International Search Report and Written Opinion of PCT/US2012/026624 mailed Aug. 29, 2012, 14 pages.
Extended European Search Report for EP 12152690.9 dated Jun. 19, 2012, 9 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, Office Action mailed Aug. 31, 2012, 12 pages.
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/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/981,244, filed Dec. 29, 2010, Office Action mailed Dec. 21, 2012, 23 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/015,382, filed Jan. 27, 2011, Office Action Mailed Nov. 13, 2012, 7 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/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/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/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. 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, Office Action mailed Aug. 15, 2012, 9 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/1037,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.
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 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 for Mexican Patent Application No. MX/a/2013/007672 is not translated into English. This document is from prosecution of the corresponding foreign matter for which we do not have a translation. Dated Sep. 11, 2014, 2 pages.
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/016,483, filed Jan. 28, 2011, Non-Final Office Action mailed Nov. 3, 2014, 33 pages.
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010, Final Office Action mailed Dec. 3, 2014, 19 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. 12/961,369, filed Dec. 6, 2010, Non-Final Office Action mailed Feb. 13, 2014, 21 pages.
U.S. Appl. No. 13/010,557, filed Jan. 20, 2011, Final Rejection mailed Jan. 15, 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/192,287, filed Jul. 27, 2011, Final Office Action mailed Jan. 28, 2014, 18 pages.
U.S. Appl. No. 13/035,474, filed Feb. 25, 2011, Non Final Rejection mailed Mar. 6, 2014, 20 pages.
Extended European Search Report for EP 11842890.3 dated Mar. 26, 2014, 8 pages.
Extended European Search Report for EP 11850819.1 dated Mar. 17, 2014, 5 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/US2012/048032 mailed on Apr. 3, 2014, 6 pages.
International Preliminary Report on Patentability of PCT/US2011/063111 mailed Jun. 13, 2013, 8 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, Final Office Action mailed Mar. 18, 2014, 24 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/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, Notice of Allowance mailed May 2, 2014, 40 pages.
U.S. Appl. No. 13/968,611, filed Aug. 16, 2013, Non-Final Office Action mailed Jan. 17, 2014, 21 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 of 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/SU2012/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 (94567-886650), 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. 13/006,270, filed Jan. 13, 2011, Non-Final Office Action mailed Sep. 12, 2014, 41 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. 12/973,431, filed Dec. 20, 2010 Non-Final Rejection mailed Dec. 19, 2014, 30 pages.
The Notice of Allowance received Dec. 16, 2014 for Mexican Patent Application No. MX/a/2013/009882 is not translated into English, 1 page.
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/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/971,349, filed Dec. 7, 2010, Notice of Allowance mailed Oct. 2, 2013, 24 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/965,645, filed Dec. 10, 2010, Non-Final Office Action, mailed Jul. 19, 2013, 20 pages.
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010, Final Office Action mailed Aug. 27, 2013, 11 pages.
U.S. Appl. 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/192,287, filed Jul. 27, 2011 Non Final Office Action mailed Jun. 13, 2013, 22 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/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.
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.
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 dated Feb. 18, 2015 for Mexican Patent Application No. MX/a/2013/009794, 1 page.
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. 13/006,270, filed Jan. 13, 2011, Final Office Action mailed Mar. 23, 2014, 51 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/960,285, filed Dec. 3, 2010 Non-Final Office Action mailed May 14, 2015, 21 pages.
U.S. Appl. No. 12/973,431, filed Dec. 20, 2010 Notice of Allowance mailed May 28, 2015, 20 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.
U.S. Appl. No. 13/302,717, filed Nov. 22, 2011 Non Final Rejection mailed Jun. 16, 2016, all pages.
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011 Final Office Action mailed Jul. 5, 2016, all pages.
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011, Final Office Action mailed Jul. 12, 2016, all pages.
U.S. Appl. No. 13/475,794, filed May 18, 2012 Non Final Office Action mailed Jul. 29, 2016, all pages.
U.S. Appl. No. 13/864,474, filed Apr. 17, 2013 Non Final Office Action mailed Mar. 23, 2016, all pages.
U.S. Appl. No. 12/960,285, filed Dec. 3, 2010, Notice of Allowance mailed Nov. 18, 2015, 31 pages.
Second Office Action for CN 201180065044.7 issued Sep. 9, 2015 by the State Intellectual Property Office (SIPO), 20 pages.
European Office Action for EP 11842890.3 dated May 9, 2016, all pages.
Office Action for European Patent App. 12704473.3 mailed Apr. 29, 2016, all pages.
Supplementary European Search Report for EP 11843423 completed Mar. 23, 2016, 8 pages.
Supplementary European Search Report for EP 11843045 completed Mar. 31, 2016, all pages.
First Office Action including Search Report from the State Intellectual Property Office for CN Patent Appln. No. 201280014034.5 issued on Apr. 5, 2016, all pages.
Office Action and Search Report for ROC (Taiwan) Pat. Appln. No. 101106313 received May 12, 2016, all pages.
Notice of Decision to Grant for CN 201280010873 on Mar. 25, 2016, all pages.
Examination Search Report from the European Patent Office dated Dec. 4, 2015 for EP 12707418.5, 8 pages.
European Office Action for EP 12716751.8 mailed Nov. 11, 2015, 4 pages.
Office Action for EP 11850819.1 dated Nov. 12, 2015, 4 pages.
First Office Action with Search Report for CN 201280013891.3 issued Jan. 15, 2016, 13 pages.
First Office Action and Search Report from State Intellectual Property Office for CN Appln. No. 201180064527.5 issued Oct. 23, 2015, 10 pages.
Notice of Allowance mailed Nov. 10, 2015 for Mexican Patent Application No. MX/a/2013/007672, 1 page.
Notice of Allowance for Mexican Patent Application No. MX/a/2013/006973 dated Sep. 4, 2015, 1 page.
Second Office Action issued by State Intellectual Property Office for CN Pat. Appln. No. 201180066584.7 issued on Jan. 11, 2016, 5 pages.
Search Report for Patent Application ROC (Taiwan) Patent Application No. 100149344 mailed Oct. 28, 2015, 1 page.
U.S. Appl. No. 13/302,717, filed Nov. 22, 2011 Non Final Rejection mailed Dec. 2, 2015, 27 pages.
U.S. Appl. No. 13/016,483, filed Jan. 28, 2011 Non-Final Office Action mailed Dec. 14, 2015, 27 pages.
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011, Non-Final Office Action mailed Jan. 12, 2016, 62 pages.
U.S. Appl. No. 13/192,287, filed Jul. 27, 2011, Notice of Allowance mailed Dec. 14, 2015, 14 pages.
U.S. Appl. No. 13/864,474, filed Apr. 17, 2013 Final Office Action mailed Nov. 20, 2015, all pages.
Second Office Action from State Intellectual Property Office for CN Appln. No. 201180056242.7 issued Jan. 26, 2016, all pages.
First Office Action and Search Report from the State Intellectual Property Office (SIPO) for CN 201180056249.9 issued on Feb. 3, 2016, all pages.
First Office Action for CN 201280010873 issued Mar. 2, 2016, all pages.
U.S. Appl. No. 13/037,302, filed Feb. 28, 2011, Notice of Allowance mailed Feb. 16, 2017, all pages.
U.S. Appl. No. 13/864,474, filed Apr. 17, 2013 Notice of Allowance mailed Feb. 16, 2017, all pages.
Office Action for EP 12705768.5 mailed May 25, 2016, all pages.
Office Action for Korean Patent Application No. 10-2013-7015610 mailed Oct. 21, 2016, all pages. (no English translation available).
Office Action for EP 11811502.1 mailed Aug. 29, 2016, all pages.
Publication of Brazil appln No. BR 11 2013 012218-8 on Aug. 9, 2016, 1 page.
Second Office Action CN 201280013891.3 issued Aug. 12, 2016, all pages.
Third Office Action from State Intellectual Property Office for CN Appln. No. 201180056242.7 issued Jul. 28, 2016, all pages.
Second Office Action from State Intellectual Property Office for CN Appln. No. 201180064527.5 issued Jun. 12, 2016, all pages.
Rejection Decision for CN Appln. No. 201180064527.5 issued Oct. 9, 2016, all pages. (Translation).
Notice of Allowance for Mexican Patent Application No. MX/a/2013/009791 dated Mar. 15, 2016, 1 page.
Office Action dated Oct. 17, 2016 for European Patent Appln. No. 12701638.4, all pages.
Second Office Action issued by State Intellectual Property Office (SIPO) for CN 201180056249.9 issued on Feb. 4, 2017, all pages.
Office Action for Korean Patent Application No. 10-2013-7020207 mailed Dec. 21, 2016, all pages.
Office Action and Search Report for ROC (Taiwan) Pat. Appln. No. 101106313 received Nov. 4, 2016, all pages.
Notice of Allowance for Canadian Application 2,822,214 dated Nov. 28, 2016, 1 page.
U.S. Appl. No. 13/475,794, filed May 18, 2012 Notice of Allowance mailed Jan. 5, 2017, all pages.
U.S. Appl. No. 14/852,787, filed Sep. 14, 2015, Non-Final Office Action mailed Sep. 14, 2016, all pages.
U.S. Appl. No. 14/852,787, filed Sep. 14, 2015, Final Office Action mailed Jan. 13, 2017, all pages.
Decision to Grant for Korean Patent Application No. 10-2013-7020207 on Mar. 9, 2017, all pages.
Office Action for Korean Patent Application No. 10-2013-7015610 mailed Feb. 21, 2017, all pages.
Related Publications (1)
Number Date Country
20120128267 A1 May 2012 US