Device control by multiple remote controls

Information

  • Patent Grant
  • 8659399
  • Patent Number
    8,659,399
  • Date Filed
    Wednesday, July 15, 2009
    15 years ago
  • Date Issued
    Tuesday, February 25, 2014
    10 years ago
Abstract
A method and system for remotely controlling a remote-controlled device (RCD) includes receiving an instruction from a remote control (RC). The instruction may include an RC code and a control code. The RC code may identify the RC and the control code may identify an operation to be performed on the RCD. RC codes matching an authorized set of RC codes may cause the control code to be accepted, since the RC is authorized. If a non-matching RC code is received, the control code may be rejected as coming from a prohibited RC. An authorization mode on the RCD may allow modification of the authorized set of RC codes.
Description
BACKGROUND

1. Field of the Disclosure


The present disclosure relates to remote-controlled devices and, more particularly, to authorizing remote controls to operate a remote-controlled device.


2. Description of the Related Art


Remote-controlled devices provide convenient operation of equipment from a distance. Many consumer electronic devices are equipped with remote control features. Universal remote-controlled devices, may be configured to control different pieces of equipment.





BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 a block diagram of selected elements of an embodiment of a universal remote control system;



FIG. 2 illustrates an embodiment of a method for programming a universal remote control; and



FIG. 3 illustrates an embodiment of a method for programming a universal remote control.





DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

In one aspect, a disclosed method for operating a remote-controlled device (RCD) includes receiving an instruction to operate the RCD from a remote control (RC), wherein the instruction includes an RC code corresponding to the RC and a control code, and responsive to determining that the RC code indicates authorization to control the RCD, performing an RCD operation corresponding to the control code. The method operation of determining that the RC code indicates authorization to control the RCD may further include comparing the RC code with a stored set of RC codes indicating a respective set of RCs that are authorized to control the RCD.


In certain embodiments, responsive to receiving user input, the method further includes initiating an authorization mode for determining which RC codes are included in the stored set of RC codes. The method may further include receiving a new RC code corresponding to a new RC, and adding the new RC code to the stored set of RC codes, wherein the new RC is authorized to control the RCD. The method may also include deleting an RC code from the stored set of RC codes, wherein an RC corresponding to the deleted RC code is no longer authorized to control the RCD. The method may still further include outputting a user indication that the authorization mode is active. The stored set of RC codes may be stored on a memory device included in the RCD. An empty set of RC codes may result in the RCD being non-responsive to instructions received from any RC.


In another aspect, an RCD includes a processor, a wireless receiver to receive wirelessly transmitted instructions, and memory media accessible to the processor. The memory media may include instructions executable by the processor to receive an instruction to operate the RCD from an RC, wherein the instruction includes an RC code unique to the RC and a control code. The memory media may further include instructions executable to compare the RC code with a stored set of RC codes indicating a respective set of RCs that are authorized to control the RCD, and responsive to finding a match for the RC code in the stored set of RC codes, execute an RCD operation corresponding to the control code.


In particular embodiments, the RC may be a universal remote control (URC), while the URC may be configured to send instructions to more than one RCD. The stored set of RC codes may indicate a set of RCs including the URC. The stored set of RC codes may be stored in the memory media. The instructions may further include processor executable instructions to receive a new RC code corresponding to a new RC device, and add the new RC code to the stored set of RC codes. The instructions may still further include processor executable instructions to delete one of the RC codes in the stored set of RC codes.


In a further aspect, a disclosed computer-readable memory media includes executable instructions for operating an RCD. The instructions may be executable to receive an instruction to operate the RCD from an RC, wherein the instruction includes an RC code corresponding to the RC and a control code and identify the RC code and the control code. Responsive to finding a match for the RC code in a stored set of RC codes indicating a respective set of RCs that are authorized to control the RCD, the instructions may also be executable to execute an RCD operation corresponding to the control code.


In certain embodiments, the memory media may include instructions executable to receive first input for initiating an authorization mode on the RCD, and receive second input for terminating the authorization mode. The memory media may also include instructions executable to receive a new RC code corresponding to a new RC, and add the new RC code to the stored set of RC codes to authorize the new RC to control the RCD. The new RC code may be received from the new RC. The new RC code may be received from a programming device. The first input and the second input may both be user inputs. The first input and the second input may be received from a programming device. The memory media may still further include instructions executable to delete an RC code from the stored set of RC codes to prohibit an RC corresponding to the deleted RC code from controlling the RCD.


In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments.


Referring now to FIG. 1, a block diagram of selected elements of an embodiment of remote-controlled system 100 are depicted. System 100 illustrates devices, interfaces and information that may be processed to configure RCD 108 to use at least one RC. In system 100, RCD 108 represents any of a number of different types of devices that are remote-controlled, such as media players, televisions, or client-premises equipment (CPE) for multimedia content distribution networks (MCDNs), among others. System 100 is also shown including two particular RCs, original remote control (ORC) 114 and URC 110, along with programming device 113.


In FIG. 1, ORC 114 is depicted communicating with RCD 108 via communication link 104. Similarly, URC 110 is shown communicating with RCD 108 via communication link 102. Communication links 102 and 104 may be wireless or mechanically connected interfaces. Programming device 113 may communicate with RCD 108 via communication link 124, which may be removably coupled to RCD 108.


As shown in FIG. 1, RCD 108 includes numerous elements, and may include additional elements (not shown in FIG. 1) in various embodiments. RCD 108 is shown including processor system 106, RC interface 120, memory 112, and display/output elements 122. Memory 112 is depicted in FIG. 1 including authorized RC set 116 and RC program 118. Accordingly, RCD 108 may comprise elements configured to function as an embodiment of a computing device. RCD 108 may further include at least one shared bus (not shown in FIG. 1) for interconnectivity among internal elements, such as those depicted in FIG. 1.


The RCs shown in FIG. 1 include ORC 114 and URC 110 and represent devices that respond to user input to control operation of RCD 108. ORC 114 may represent original equipment associated with RCD 108 that may be provided by a manufacturer of RCD 108. Thus, ORC 114 may be configured for exclusive use with RCD 108. On the other hand, URC 110 may be provided by a third-party for use with a number of different RCDs, such as RCD 108. That is, different control elements (not shown in FIG. 1) on URC 110 may be programmable to generate instructions to control different RCDs. Although two RCs are shown in FIG. 1 for clarity, RCD 108 may be configured to respond to a number of different RCs.


Processor system 106 may represent at least one processing unit and may further include internal memory, such as a cache for storing processor executable instructions. In certain embodiments, processor system 106 serves as a main controller for RCD 108. In various embodiments, processor system 106 is operable to perform remote control operations, as described herein.


In FIG. 1, RC interface(s) 120 may represent a communications transceiver providing an interface for any of a number of communication links. In certain embodiments, RC interface(s) 120 supports wireless communication links, such as infrared (IR), radio-frequency (RF), and audio, among others. RC interface(s) 120 may further support mechanically connected communication links to RCs, such as galvanically wired connections, and may accordingly include a physical adapter or receptacle for receiving such connections. In one embodiment, RC interface(s) 120 transforms a received signal into an instruction for operating RCD 108, by which an RC may operate RCD 108.


Also in FIG. 1, memory 112 encompasses persistent and volatile media, fixed and removable media, magnetic and semiconductor media, or a combination thereof. Memory 112 is operable to store instructions, data, or both. Memory 112 as shown includes data, which may be in the form of sets or sequences of instructions, namely, authorized RC set 116 and RC program 118. Authorized RC set 116 may represent information indicating a set of RCs that are authorized to control the RCD. RC program 118 may include processor executable instructions to receive commands from RCs and execute the commands, as will be described in detail herein.


RCD 108, as depicted in FIG. 1, further includes display/output element(s) 122, which may represent various types of components for interacting with a user of RCD 108. An output element included in display/output element(s) 122 may represent a device for providing signals or indications to the user, such as loudspeakers for generating audio signals. A display element included in display/output element(s) 122 may include a display device, which may be implemented as a liquid crystal display screen, a computer monitor, a television, a touch screen device, or the like. The display element may comply with a display standard for the corresponding type of display. Standards for computer monitors include analog standards such as video graphics array (VGA), extended graphics array (XGA), etc., or digital standards such as digital video interface (DVI), high definition multimedia interface (HDMI), among others. A television display may comply with standards such as National Television System Committee (NTSC), Phase Alternating Line (PAL), or another suitable standard.


In FIG. 1, programming device 113 may represent a special-purpose device configured to program memory 112. Programming device 113 may thus be configured to modify authorized RC set 116 and/or RC program 118, or to load these elements in memory 112. In certain embodiments, programming device 113 is configured to initiate an authorization mode in RCD 108, during which authorized RC set 116 may be edited. In some embodiments, programming device 113 may further be used to reset memory 112 to a default state. In one embodiment, programming device 113 is located at a remote location (not shown in FIG. 1) from RCD 108, while communication link 124 may be a network interface


In one embodiment, RCD 108 may receive an instruction from an RC, such as URC 110. The instruction may be received via communication link 102 by RC interface(s) 120. A method to process the instruction, as described herein, may be embodied in RC program 118, which may be executed by processor system 106. The instruction may include an RC code corresponding to URC 110 and a control code. The control code may represent a specific operation for RCD 108.


RC program 118 may compare the received RC code with a stored set of RC codes in authorized RC set 116. Authorized RC set 116 may store a set of RC codes indicating a respective set of RCs, such as URC 110, that are authorized to control RCD 108. If the received RC code does not match an RC code in authorized RC set 116, then RC program 118 may deny the instruction, or simply remain non-responsive.


If the received RC code does match an RC code in authorized RC set 116, then RC program 118 may interpret the control code as a specific operation for RCD 108 and cause RCD 108 to perform the specific operation. RCD 108 may further display or output an indication of the specific operation or whether the received RC code was authorized using display/output element(s) 122.


Further, RCD 108 may receive input for initiating an authorization mode. In certain embodiments, input may be user input from an RC, such as ORC 114 or URC 110. In other embodiments, the input may be received from programming device 113. During authorization mode, modifications to authorized RC set 116 may be allowed. The modifications may include deletion of an RC code stored in authorized RC set 116 and addition of a new RC code to authorized RC set 116. In one embodiment, authorized RC set 116 may be completely cleared of RC codes, such that no RC is authorized to control RCD 108. Authorized RC set 116 may be restored to a default state that authorizes ORC 114 to control RCD 108. If a particular RC code is deleted from authorized RC set 116, then the corresponding RC will be prohibited from controlling RCD 108. In particular embodiments, authorized RC set 116 may contain protected, i.e., read-only, entries for RC codes that cannot be deleted.


Turning now to FIG. 2, an embodiment of method 200 for remotely controlling an RCD is illustrated. In one embodiment, method 200 is performed by RC program 118 executing on RCD 108. It is noted that certain operations described in method 200 may be optional or may be rearranged in different embodiments. For example in certain embodiments, operations 210 through 220 may be executed as a separate authorization mode method in parallel with other operations.


Method 200 may begin by receiving an instruction to operate an RCD from an RC, including an RC code and a control code (operation 202). The instruction may be received in the form of digital codes. The RC code may uniquely correspond to the particular RC sending the instruction, while the control code may correspond to a particular operation on the RCD. In certain embodiments, the RC code may simply correspond to a particular type of RC, such that any instance of the RC type generates the same RC code. The RCD may be configured to receive and interpret the codes in the instruction, which may be further encoded or encrypted for security. The instruction may be wirelessly received at an RC interface of the RCD.


In operation 202, the RC may send the instruction in response to user input received at a control element of the RC, such as a physical or virtual button. The activation of the control element by the user may generate the control code, while the RC code may be solely associated with the RC itself. In various embodiments, the instruction may include additional information generated by the RC along with the RC code and the control code.


Then, a decision may be made whether the RC code is in an authorized set of RC codes (operation 204). Additional operations may be associated with the decision in operation 204 (see FIG. 3). If the result of the decision in operation 204 is NO, then a “prohibited RC code” indication may be output (operation 206). After operation 206, method 200 may return to operation 202 and wait for another received instruction.


If the result of the decision in operation 204 is YES, then an RCD operation corresponding to the control code may be executed (operation 208). The RCD operation may be executed by the RCD and may correspond to a device function of the RCD. The RCD may output or display an “authorized RC code” indication in association with performing the RCD operation.


Method 200 may continue by making a decision whether an authorization mode should be initiated (operation 210). The decision in operation 210 may be made in response to receiving an instruction to enter authorization mode. In certain embodiments, the decision in operation 210 is made in response to user input. If the result of the decision in operation 210 is NO, then method 200 may return to operation 202 and wait for another received instruction.


If the result of the decision in operation 210 is YES, then an indication of authorization mode “on” may be output (operation 212). If a new RC code is transmitted, then the new RC code may be received and the new RC code may be added to the authorized set of RC codes (operation 214). The new RC code may be transmitted from an RC or a programming device. An additional instruction to add the new RC code in authorization mode may be received. If the new RC code matches an existing RC code in the authorized set of RC codes, a message indicating a duplicate RC code may be returned. If a delete RC code is transmitted, an RC code may be deleted from the authorized set of RC codes (operation 216). The delete RC code may be transmitted from an RC or a programming device. An additional instruction to delete the delete RC code in authorization mode may be received. If the deleted RC code does not match an existing RC code in the authorized set of RC codes, a message indicating a delete RC code error may be returned.


Method 200 may proceed by making a decision whether the authorization mode should be terminated (operation 218). The termination of authorization mode may be in response to a received instruction or user input. If the result of the decision in operation 218 is NO, then method 200 may return to operation 202 and wait for additional operations in authorization mode. If the result of the decision in operation 218 is YES, then an indication of authorization mode “off” may be output (operation 220). The authorization mode may be terminated on the RCD and method 200 may return to operation 202 and wait for another received instruction.


Turning now to FIG. 3, an embodiment of method 204 for remotely controlling an RCD is illustrated. Method 204 corresponds to one exemplary embodiment of operation 204 (see FIG. 2). In one embodiment, method 204 is performed by RC program 118 executing on RCD 108. It is noted that certain operations described in method 204 may be optional or may be rearranged in different embodiments.


Method 204 may begin by comparing a received RC code with RC codes stored in an authorized set of RC codes (operation 222). Method 204 may proceed by making a decision whether the RC code matches any RC codes in the authorized set of RC codes (operation 224). If the result of the decision in operation 224 is NO, then method 204 may continue to operation 206 (see FIG. 2).


If the result of the decision in operation 224 is YES, then the matching RC code may be determined along with an RC identity (operation 226). The RC identity may correspond to the RC sending the instruction in operation 202 (see FIG. 2). Next, the RCD operation(s) corresponding to control code(s) for the RC identity may be determined (operation 228). The RCD operations may represent the operations executed by the RCD when a corresponding control code is received. Further, the RCD may output a “busy” or “authorized” indication (operation 230). The “busy” or “authorized” indication may persist until the RCD operation has been performed. Method 204 may then continue to operation 208 (see FIG. 2).


To the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited to the specific embodiments described in the foregoing detailed description.

Claims
  • 1. A remote control method comprising: receiving, from a first remote control, an instruction to operate a remote-controlled media player, wherein the instruction includes a first remote control code identifying the first remote control and an operation code corresponding to a first operation associated with the remote controlled media player;comparing the first remote control code with a stored set of remote control codes indicating a respective set of remote controls that are authorized to control the remote-controlled media player;responsive to determining that the first remote control code indicates that the first remote control is authorized to control the remote-controlled media player, sending the operation code to the remote controlled media player for execution;after sending the operation code, determining whether to initiate an authorization mode; andresponsive to initiating the authorization mode, adding a new remote control code to the stored set of remote control codes responsive to detecting the new remote control code;responsive to receiving a delete remote code instruction identifying a remote control code, removing the identified remote control code from the stored set of remote control codes;wherein the remote control corresponding to a deleted remote control code is no longer authorized to control the remote-controlled media player and wherein a number of remote control codes in the stored set of remote control codes after execution of the delete remote code instruction is less than a number of remote control codes in the stored set of remote control codes before execution of the delete remote code instruction.
  • 2. The method of claim 1, further comprising: responsive to receiving a reset instruction, restoring the stored set of remote control codes to an original state including a single authorized remote control code corresponding to an original remote control.
  • 3. The method of claim 1, further comprising: outputting a user indication that the authorization mode is active.
  • 4. The method of claim 1, wherein the stored set of remote control codes is stored on a memory device included in the remote-controlled media player.
  • 5. The method of claim 1, wherein an empty set of remote control codes results in the remote-controlled media player being non-responsive to instructions received from any remote control.
  • 6. A remote-controlled media player, comprising: a processor;a wireless receiver to receive wirelessly transmitted instructions; andmemory storage media accessible to the processor, including processor executable instructions that, when executed by the processor, cause the processor to perform operations comprising:receiving a wirelessly transmitted instruction to operate the remote-controlled media player from a first remote control, wherein the wirelessly transmitted instruction includes a first remote control code unique to the first remote control and an operation code corresponding to an operation executable by the remote-controlled media player;comparing the first remote control code with a stored set of remote control codes indicating a respective set of remote controls that are authorized to control the remote-controlled media player; andresponsive to finding a match for the first remote control code in the stored set of remote control codes: performing the operation indicated by the operation code;after performing the operation, determining whether an authorization mode has been initiated;responsive to detecting initiation of the authorization mode:adding a second remote control code to the stored set of remote control codes responsive to detecting the second remote control code; andterminating the authorization model; andresponsive to receiving a delete remote code instruction identifying a remote control code, removing the identified remote control code from the stored set of remote control codes;wherein the remote control corresponding to a deleted remote control code is no longer authorized to control the remote-controlled media player and wherein a number of recognized remote control codes in the stored set of remote control codes after execution of the delete remote code instruction is less than a number of recognized remote control codes in the stored set of remote control codes before execution of the delete remote code instruction.
  • 7. The remote-controlled media player of claim 6, wherein the first remote control is a universal remote control, and wherein the universal remote control is configured to send the wirelessly transmitted instructions to more than one remote-controlled media player.
  • 8. The remote-controlled media player of claim 7, wherein the stored set of remote control codes are stored in the memory media.
  • 9. A computer-readable memory device, including processor executable instructions that, when executed by a processor, cause the processor to perform processor operations comprising: receiving a wirelessly transmitted instruction to operate a remote-controlled media player from a first remote control, wherein the wirelessly transmitted instruction includes a first remote control code unique to the first remote control and an operation code corresponding to an operation executable by the remote-controlled media player;comparing the first remote control code with a stored set of remote control codes indicating a respective set of remote controls that are authorized to control the remote-controlled media player; andresponsive to finding a match for the first remote control code in the stored set of remote control codes: performing the operation corresponding to the operation code;after performing the operation, determining whether an authorization mode has been initiated;responsive to detecting initiation of the authorization mode, adding a second remote control code to the stored set of remote control codes responsive to detecting the second remote control code; andresponsive to receiving a delete remote code instruction identifying a remote control code, removing the identified remote control code from the stored set of remote control codes;wherein the remote control corresponding to a deleted remote control code is no longer authorized to control the remote-controlled media player and wherein a number of remote control codes in the stored set of remote control codes after execution of the delete remote code instruction is less than a number of remote control codes in the stored set of remote control codes before execution of the delete remote code instruction.
  • 10. The memory device of claim 9, wherein the second remote control code is received from a new second remote control.
  • 11. The memory device of claim 9, wherein the second remote control code is received from a programming device.
  • 12. The memory device of claim 9, wherein the authorization mode is initiated in response to user input.
  • 13. The memory device of claim 9, wherein the instruction is received from a programming device.
  • 14. The memory device of claim 9, wherein the processor operations include: deleting a remote control code from the stored set of remote control codes to prohibit an remote control corresponding to the deleted remote control code from controlling the remote-controlled media player.
US Referenced Citations (211)
Number Name Date Kind
4638433 Schindler Jan 1987 A
5937065 Simon et al. Aug 1999 A
6163271 Yoshizawa et al. Dec 2000 A
6484027 Mauney et al. Nov 2002 B1
6486795 Sobel et al. Nov 2002 B1
6865372 Mauney et al. Mar 2005 B2
6903650 Murray Jun 2005 B2
7010169 Kortum et al. Mar 2006 B2
7016709 Kortum et al. Mar 2006 B2
7180260 Murphy et al. Feb 2007 B2
7206614 Kortum et al. Apr 2007 B2
7251373 Kortum et al. Jul 2007 B2
D550696 Kortum et al. Sep 2007 S
7307574 Kortum et al. Dec 2007 B2
D562806 Bruce et al. Feb 2008 S
7337220 Kortum et al. Feb 2008 B2
7353018 Mauney et al. Apr 2008 B2
7366337 Kortum et al. Apr 2008 B2
7403793 Mauney et al. Jul 2008 B2
7406207 Kortum et al. Jul 2008 B2
7474359 Sullivan et al. Jan 2009 B2
7499594 Kortum et al. Mar 2009 B2
7512228 Kortum et al. Mar 2009 B2
7518991 Sullivan et al. Apr 2009 B2
7551973 Cansler, Jr. et al. Jun 2009 B2
7565430 Kortum et al. Jul 2009 B2
7602898 Klein et al. Oct 2009 B2
D603842 Bruce et al. Nov 2009 S
7636933 Kortum et al. Dec 2009 B2
7693542 Mauney et al. Apr 2010 B2
7716714 Kortum et al. May 2010 B2
7720255 Rhoads May 2010 B2
7734788 Karaoguz et al. Jun 2010 B2
7774384 Kortum et al. Aug 2010 B2
7783120 Kortum et al. Aug 2010 B2
7793317 Sullivan et al. Sep 2010 B2
7836196 Karaoguz et al. Nov 2010 B2
7873102 Van Vleck et al. Jan 2011 B2
7876232 Sullivan et al. Jan 2011 B2
7876775 Jones et al. Jan 2011 B2
7885684 Mauney et al. Feb 2011 B2
7894682 Kortum et al. Feb 2011 B2
7949305 Sullivan et al. May 2011 B2
7966310 Sullivan et al. Jun 2011 B2
20020037715 Mauney et al. Mar 2002 A1
20020137460 Sun et al. Sep 2002 A1
20030016119 Teich Jan 2003 A1
20030016139 Teich Jan 2003 A1
20030023881 Fitzgibbon et al. Jan 2003 A1
20030079028 Kortum et al. Apr 2003 A1
20030194141 Kortum et al. Oct 2003 A1
20030194142 Kortum et al. Oct 2003 A1
20040116073 Mauney et al. Jun 2004 A1
20040177279 Domenz et al. Sep 2004 A1
20050020236 Mauney et al. Jan 2005 A1
20050032475 Mauney et al. Feb 2005 A1
20050076121 Kortum et al. Apr 2005 A1
20050159107 Mauney et al. Jul 2005 A1
20050166261 Kortum et al. Jul 2005 A1
20050175230 Kortum et al. Aug 2005 A1
20050180463 Jones et al. Aug 2005 A1
20050180560 Kortum et al. Aug 2005 A1
20050202854 Kortum et al. Sep 2005 A1
20050216589 Kortum et al. Sep 2005 A1
20060015924 Kortum et al. Jan 2006 A1
20060026663 Kortum et al. Feb 2006 A1
20060037043 Kortum et al. Feb 2006 A1
20060037083 Kortum et al. Feb 2006 A1
20060039547 Klein et al. Feb 2006 A1
20060048178 Kortum et al. Mar 2006 A1
20060048179 Kortum et al. Mar 2006 A1
20060050865 Kortum et al. Mar 2006 A1
20060087978 Sullivan et al. Apr 2006 A1
20060098882 Kortum et al. May 2006 A1
20060112094 Sullivan et al. May 2006 A1
20060114360 Kortum et al. Jun 2006 A1
20060116177 Kortum et al. Jun 2006 A1
20060117374 Kortum et al. Jun 2006 A1
20060123445 Sullivan et al. Jun 2006 A1
20060126808 Dallassendaro et al. Jun 2006 A1
20060156372 Cansler, Jr. et al. Jul 2006 A1
20060159119 Kortum et al. Jul 2006 A1
20060168610 Noil Williams et al. Jul 2006 A1
20060170582 Kortum et al. Aug 2006 A1
20060174279 Sullivan et al. Aug 2006 A1
20060184992 Kortum et al. Aug 2006 A1
20060187071 Kortum et al. Aug 2006 A1
20060271516 Kortum et al. Nov 2006 A1
20070011250 Kortum et al. Jan 2007 A1
20070025449 Van Vleck et al. Feb 2007 A1
20070039031 Cansler, Jr. et al. Feb 2007 A1
20070039036 Sullivan et al. Feb 2007 A1
20070044119 Sullivan et al. Feb 2007 A1
20070056015 Kortum et al. Mar 2007 A1
20070130588 Edwards et al. Jun 2007 A1
20070143790 Williams et al. Jun 2007 A1
20070169155 Pasquale et al. Jul 2007 A1
20070174276 Sullivan et al. Jul 2007 A1
20070177188 Wollmershauser et al. Aug 2007 A1
20070180382 Kortum et al. Aug 2007 A1
20070180489 Joseph et al. Aug 2007 A1
20070192791 Sullivan et al. Aug 2007 A1
20070248273 Kortum et al. Oct 2007 A1
20070271342 Brandt et al. Nov 2007 A1
20070294737 Edwards et al. Dec 2007 A1
20080098308 Kortum et al. Apr 2008 A1
20080100492 Kortum et al. May 2008 A1
20080101338 Reynolds et al. May 2008 A1
20080101588 Bruce et al. May 2008 A1
20080104630 Bruce et al. May 2008 A1
20080109839 Bruce et al. May 2008 A1
20080125098 Bruce et al. May 2008 A1
20080165283 Brandt et al. Jul 2008 A1
20080187210 Kortum et al. Aug 2008 A1
20080189736 Edwards et al. Aug 2008 A1
20080235745 Edwards et al. Sep 2008 A1
20080250468 Sullivan et al. Oct 2008 A1
20080261514 Pratt et al. Oct 2008 A1
20090010555 Kortum et al. Jan 2009 A1
20090021651 Pratt et al. Jan 2009 A1
20090031375 Sullivan et al. Jan 2009 A1
20090044233 Brandt et al. Feb 2009 A1
20090067591 Belz et al. Mar 2009 A1
20090070696 Belz et al. Mar 2009 A1
20090073321 Sullivan et al. Mar 2009 A1
20090094654 Sullivan et al. Apr 2009 A1
20090109050 Sullivan et al. Apr 2009 A1
20090111656 Sullivan et al. Apr 2009 A1
20090115904 Sullivan et al. May 2009 A1
20090119181 Pratt et al. May 2009 A1
20090125971 Belz et al. May 2009 A1
20090157473 Belz et al. Jun 2009 A1
20090157808 Karaoguz et al. Jun 2009 A1
20090158369 Van Vleck et al. Jun 2009 A1
20090158373 Belz et al. Jun 2009 A1
20090161532 Sullivan et al. Jun 2009 A1
20090180377 Sullivan et al. Jul 2009 A1
20090180596 Reynolds et al. Jul 2009 A1
20090185748 Kortum et al. Jul 2009 A1
20090187955 Sullivan et al. Jul 2009 A1
20090193143 Karaoguz et al. Jul 2009 A1
20090210948 Borghetti et al. Aug 2009 A1
20090222868 Reynolds et al. Sep 2009 A1
20090245494 Sullivan et al. Oct 2009 A1
20090249429 Sullivan et al. Oct 2009 A1
20090254778 Huang et al. Oct 2009 A1
20090284346 Hormann Nov 2009 A1
20090288115 Belz et al. Nov 2009 A1
20090312059 Pratt et al. Dec 2009 A1
20090319607 Belz et al. Dec 2009 A1
20100015999 Belz et al. Jan 2010 A1
20100039214 Pratt et al. Feb 2010 A1
20100039392 Pratt et al. Feb 2010 A1
20100039393 Pratt et al. Feb 2010 A1
20100040152 Kortum et al. Feb 2010 A1
20100042827 Pratt et al. Feb 2010 A1
20100050270 Pratt et al. Feb 2010 A1
20100069012 Sullivan et al. Mar 2010 A1
20100082712 Pratt et al. Apr 2010 A1
20100088149 Sullivan et al. Apr 2010 A1
20100104024 Sullivan et al. Apr 2010 A1
20100113160 Belz et al. May 2010 A1
20100115592 Belz et al. May 2010 A1
20100115607 Pratt et al. May 2010 A1
20100118748 Pratt et al. May 2010 A1
20100119051 Belz et al. May 2010 A1
20100121744 Belz et al. May 2010 A1
20100122306 Pratt et al. May 2010 A1
20100124905 Pratt et al. May 2010 A1
20100134338 Belz et al. Jun 2010 A1
20100138499 Belz et al. Jun 2010 A1
20100138876 Sullivan Jun 2010 A1
20100144368 Sullivan et al. Jun 2010 A1
20100149982 Pratt et al. Jun 2010 A1
20100150327 Belz et al. Jun 2010 A1
20100153764 Pratt et al. Jun 2010 A1
20100153995 Belz et al. Jun 2010 A1
20100158533 Belz et al. Jun 2010 A1
20100161801 Belz et al. Jun 2010 A1
20100162331 Belz et al. Jun 2010 A1
20100174572 Joseph et al. Jul 2010 A1
20100178869 Mauney et al. Jul 2010 A1
20100222031 Carolan et al. Sep 2010 A1
20100235872 Sullivan et al. Sep 2010 A1
20100275236 Kortum et al. Oct 2010 A1
20100275237 Pratt et al. Oct 2010 A1
20100289685 Pratt et al. Nov 2010 A1
20100289954 Sullivan et al. Nov 2010 A1
20100299693 Sullivan et al. Nov 2010 A1
20100302057 Pratt et al. Dec 2010 A1
20100302058 Belz et al. Dec 2010 A1
20110003587 Belz et al. Jan 2011 A1
20110010745 Belz et al. Jan 2011 A1
20110010746 Howarter et al. Jan 2011 A1
20110029887 Pearson et al. Feb 2011 A1
20110037574 Pratt et al. Feb 2011 A1
20110037611 Van Vleck et al. Feb 2011 A1
20110037637 Van Vleck et al. Feb 2011 A1
20110075727 Van Vleck et al. Mar 2011 A1
20110090085 Belz et al. Apr 2011 A1
20110093876 Belz et al. Apr 2011 A1
20110093908 Van Vleck et al. Apr 2011 A1
20110095873 Pratt et al. Apr 2011 A1
20110109490 Belz et al. May 2011 A1
20110113459 Crowe et al. May 2011 A1
20110114716 Pratt May 2011 A1
20110115664 Belz et al. May 2011 A1
20110124316 Mauney et al. May 2011 A1
20110131605 Pratt Jun 2011 A1
20110159861 Pratt et al. Jun 2011 A1
20110161423 Pratt et al. Jun 2011 A1
Related Publications (1)
Number Date Country
20110012710 A1 Jan 2011 US