A set-top box (STB) is a device that connects a television to an external signal source. The set-top box decodes the signal into content which is then displayed on the television screen. Many improvements have been made recently in the functionality provided through a user's integrated set-top box. For example, many of today's set-top boxes are also digital video recorders (DVRs). A digital video recorder (DVR) is a device that records video in a digital format to a disk drive or other memory medium within a device.
Embodiments of the present invention include a set-top box that comprises a memory component for storing computer executable instructions, a data storage unit for storing recorded voice communications and recorded media content files; a line monitoring module for detecting a connected call on a communication line; and a processing unit for executing the computer executable instructions to record voice communications in response to detecting the connected call.
Further details and advantages of the present invention will be discussed in the following detailed description of the preferred embodiments.
The disclosed embodiments and advantages thereof are best understood by referring to
Embodiments of the present invention include an integrated set-top box for recording voice communications on the integrated set-top box. In addition, the integrated set-top box provides video signal decoding capabilities for displaying a television program on a display unit. As will be further described, in one embodiment, the integrated set-top box automatically detects, records, and stores communications associated with a monitored communication device in a data storage unit of the integrated set-top box. In another embodiment, the integrated set-top box may provide, in addition to other features, voicemail capabilities. With the advent of virtually unlimited data storage capacity, e.g., a terabyte hard drive, the disclosed embodiments may store year's worth of conversations and/or voicemails.
For example, in the depicted embodiment, set-top box 140 is communicatively coupled to a display unit 160, network 120, and communication device 170. Set-top box 140 is configured to receive television signals 181 from a cable service provider 180 for displaying television programming on display unit 160. In addition, in one embodiment, set-top box 140 is configured to monitor voice communications associated with communication line 171. Communication line 171 may be, but is not limited to, a standard telephone line, a fiber-optic line, and/or a coaxial cable. In one embodiment, communication line 171 is touted through set-top box 140 for enabling set-top box 140 to monitor and record voice communications associated with a communication device, such as, communication device 170, coupled to communication line 171.
For example, in one embodiment, set-top box 140 executes instructions associated with a set-top box voice communication recording application 150 for recording voice communications and/or voicemails associated with communication device 170. Communication device 170 may be, but is not limited to, an analog phone, voice over IP phone, or a data processing system, such as, a personal computer, capable of receiving and calling a plurality of communication devices 110 over network 120. Communication devices 110 include, but are not limited to, a regular landline phone, a mobile phone, a VOIP phone, and/or a data processing system.
In some embodiments, set-top box 140 may monitor the voice communications associated with more than one communication device connected to a single communication line. For example, in one embodiment, communication device 170 and communication device 172 may be connected to communication line 171. Additionally, in some embodiments, set-top box 140 may monitor voice communications associated with more than one communication device connected to a plurality of separate communication lines.
In one embodiment, network 120 may include one or more satellite and/or cable networks for transmitting media content. Additionally, in some embodiments, network 120 may also include a cellular network, the public switched telephone network (PSTN), and the Internet for connecting communication device 170 to the plurality of communication devices 110. In some embodiments, the cellular network may include a 3G network. 3G networks are wide-area cellular telephone networks that incorporate high-speed Internet access. In some embodiments, network 120 may also include a number of different types of data networks, such as, but not limited to, an intranet, a local area network (LAN), a wide area network (WAN), and wireless local area network (WLAN) networks.
Processing unit 200 may comprise of one or more microprocessors for executing computer usable program code/instructions for recording voice communications and voicemails. In one embodiment, processing unit 202 may execute computer executable instructions associated with set-top box voice communication recording application 150 stored in memory component 204 for recording voice communications and voicemails associated with communication device 170.
Memory component 204 is a data storage component of set-top box 140. In some embodiments, memory component 204 includes volatile memory. Volatile memory is memory that loses its contents when the computer or hardware device loses power. For example, in some embodiments, memory component 154 may be random access memory (RAM). Random access memory stores currently executing instructions and/or data utilized by an operating system, software program, hardware device, and/or a user.
Data storage unit 202 is a non-volatile memory component of set-top box 140, such as, but not limited to, a hard disk drive. Non-volatile memory retains stored data when power is loss. In some embodiments, data storage unit 202 may be an external hard drive and/or a network data storage unit. In one embodiment, data storage unit 202 stores voice communications 230. Voice communications 230 may include recorded voice communications and voicemails associated with communication device 170. In addition, in some embodiments, data storage unit 202 may store other data, such as, but not limited to, recorded media content files 232.
In some embodiments, line monitoring module 218 includes a line voltage detector used to monitor the voltage level traveling through communication line 171. For example, in one embodiment, line monitoring module 218 may determine whether communication device 170 is off the hook, whether an incoming call is being received, or whether communication device 170 is initiating an outbound call. For example, in some embodiments, line monitoring module 218 determines that the handheld receiver of communication device 170 is off the hook when it detects direct current (DC) flowing through communication line 171. Additionally, in some embodiments, line monitoring module 218 is configured to detect a dial tone frequency indicating that the receiving end is ready to receive dial pulses or DTMF signals. For example, in one embodiment, the dial tone frequency is a combination of 350-hertz tone and a 440-hertz tone held steady at −13 dBm0/frequency.
In addition, in some embodiments, line monitoring module 218 is also configured to interpret the dial pulses or DTMF signals to determine the caller ID information associated with an outbound call. Further, in some embodiments, line monitoring module 218 is also configured to detect the audible ring back frequency, i.e., the ringing sound that a caller hears when placing a call. Once the audible ring back frequency is no longer detected, line monitoring module 218 determines that a call has been answered. Moreover, in some embodiments, line monitoring module 218 is configured to detect a ring voltage for determining that an incoming call is being received. Likewise, in some embodiments, line monitoring module 218 is also configured to determine the caller id information associated with an incoming call over communication line 171.
In one embodiment, line monitoring module 218 may include an analogue terminal adapter (ATA). The analogue terminal adapter enables communication device 170 to communicate directly with a VoIP server using a VoIP protocol, such as, H.323, SIP, MGCP, or IAX, and encodes and decodes the voice signal using a voice codec, such as, ULAW, ALAW, GSM, ILBC and others.
Communication interface 220 provides connection ports for coupling set-top box 140 to one or more electronic devices. For example, in one embodiment, communication interface 220 includes a video output interface, such as, but not limited to, a coaxial cable connection for coupling set top box 140 to display unit 160. Additionally, in some embodiments, communication interface 220 includes, but is not limited to, a RJ45 Ethernet port and/or a RJ11 telephone line port for communicatively coupling set top box 140 to communication line 171 for monitoring voice communications associated with communication device 170. Further, in some embodiments, communication interface 220 may include other connector ports, such as, but not limited to, a 1394 port, a universal serial bus (USB) port, and/or a high-definition multimedia interface (HDMI).
Cable card 210 is a plug-in cable/smart card that enables viewing and/or recording of cable television programming. For example, in some embodiments, cable card 210 comprises instructions and/or a decryption key for decoding encrypted cable television signals transmitted by a cable provider.
Audio/video generator 212 may receive media signals through communication interface 220 and generate the appropriate audio and/or video output for transmission to display unit 160. In some embodiments, audio/video generator 212 uses a decryption key provided by cable card 210 to decode the received media signals.
Wireless transceiver 208 provides short-range exchange of data using, but not limited to, infrared light. For example, wireless transceiver 208 enables a user using a remote control device to operate and configure set top box 140. Additionally, in some embodiments, wireless transceiver 208 enables a user using a remote control device to record, playback, search, and/or send a recorded voice communication and/or voicemail associated with communication device 170.
Finally, power unit 206 converts the input power from an AC adaptor to run various components of set-top box 140. In some embodiments, power unit 202 may include an internal power source, such as, but not limited to, a battery component.
With reference now to
Process 300 begins, at step 302, by monitoring the communication line associated with one or more monitored communication devices. At step 304, the process determines whether a monitored communication device is off the hook. If the process determines that a monitored communication device is off the hook, the process captures the calling information at step 306. For example, in one embodiment, the process is able to determine the outbound call number by deciphering the dial pulses for a rotary telephone or DTMF signals for a touch-tone telephone.
At step 308, the process monitors for call connection. For example, in one embodiment, once the process no longer detects the audible ring back frequency, the process, at step 310, determines that the call is connected. At step 312, process begins recording of the voice communication associated with the monitored communication device. Additionally, in some embodiments, the process logs the beginning time and maintains a timer for monitoring the length of the call. Alternatively, in some embodiments, the process logs the ending time of the call and determines the difference between the ending time and the beginning time to determine the length of the call.
At step 314, the process monitors for the end of the call. If the call has not ended, the process continues to record the conversation at step 312. In some embodiments, the process may receive a request to playback some or a portion of the recorded conversation at step 316. In these embodiments, the process, at step 318, plays the recorded conversation starting from a user specified location. Once the process detects, at step 314, that a call has ended, the process stops recording at step 320. The process, at step 322, stores the recording along with the calling data, such as, but not limited to, the caller ID information, the time of the call, and the length of the call in data storage unit 202, with process 300 terminating thereafter.
Process 400 depicts an embodiment of a process for recording an inbound voice communication call and/or a voicemail on a set-top box in accordance with the disclosed embodiments. In one embodiment, process 400 is executed by a set-top box, such as, set-top box 140. In some embodiments, process 400 may be computer executable instructions associated with a software application, such as, but not limited to, set-top box voice communication recording application 150. Process 400 may be executed by one or more processors, such as, processing unit 200. Alternatively, in some embodiments, process 400 may be executed by a hardware embodiment or a combination of hardware and software.
Process 400 begins, at step 402, by monitoring the communication line associated with one or more monitored communication devices. At step 404, the process detects an incoming call over the monitored communication line. For example, in one embodiment, line monitoring module 218 is configured to detect a ring voltage for determining that an incoming call is being received. For instance, in one embodiment, the “ring” signal is a 90-volt AC wave at 20 hertz (Hz).
At step 406, the process captures the calling information, such as, but not limited to, the caller ID, and the time of the call. For instance, the phone company uses frequency shift keying technique to send ASCII character data over communication line 171 to communication device 170 for identifying the caller. In one embodiment, the process decodes the ASCII characters to determine the caller identification.
In some embodiments, the process determines whether the incoming call is answered within a specified time period at step 408. For example, in one embodiment, the process determines whether the call is answered within a specified number of rings. If the call is not answered within the specified time period, the process answers the incoming call and plays a recorded message at step 410. At step 412, process records a voicemail. The process, at step 414, stores the recorded voice mail and the respective calling information, such as, but not limited to, the caller ID, call time, and/or the length of the voicemail message in data storage unit 202.
However, if the call is answered within a specified time period at step 408, the process records the conversation at step 416. At step 418, the process monitors for the end of the call. If the call has not ended, the process continues to record the conversation at step 416. In some embodiments, the process may receive a request to playback some or a portion of the recorded conversation at step 424. In these embodiments, the process, at step 426, plays the recorded conversation starting from a user specified location. In some embodiments, the process continues to record the live conversation during playback of the recorded conversation at step 416. Additionally, in some embodiments, the process may play the recorded conversation using the audio output speakers of a coupled display unit, such as, but not limited to, a television. Alternatively, or in addition to, in one embodiment, the process may play a recorded conversation over communication line 171, thus, enabling both parties to directly hear the recorded conversation.
Once the process detects, at step 418, that a call has ended, the process, at step 420, stops recording of the voice communication. The process, at step 422, stores the recording along with the calling data, such as, but not limited to, the caller ID information, the time of the call, and the length of the call in data storage unit 202, with process 400 terminating thereafter.
In one embodiment, selecting recorded shows option 502 causes set-top box 140 to display a list of recorded television programs. Similarly, selecting recorded phone conversations option 504 or a voicemail option 506 causes set-top box 140 to respectively display a list of recorded phone conversations or voicemails.
User preferences option 508 may enable a user to select certain options associated with set-top box 140. For example, in one embodiment, a user may configure whether set-top box 140 automatically records every voice communication, automatically records every voice communications associated with a particular caller ID, automatically records voice communications only during a certain time of day, automatically not record voice communications associated with a particular call list (e.g., private conversations and calls from telemarketers), or only record voice communications that are manually initiated by a user. Additionally, in some embodiments, a user may configure set-top box voice communication recording application 150 to automatically notify a user of a new voicemail. For example, in some embodiments, set-top box voice communication recording application 150 may send the new voicemail to a user specified email address. In another embodiment, set-top box voice communication recording application 150 may call and/or send a text message to a user to provide notification of a new voicemail.
In some embodiments, a user may specify whether the latest or earliest voice communications/voicemails are displayed first on the list of recorded voice communications 512 and the list of recorded voicemails 532. For example, in one embodiment, by selecting the header row of date/time column 514, the list of recorded voice communications 512 alternates between displaying the earliest conversation first and displaying the latest conversation first.
In addition, in some embodiments, a user may specify that the list of recorded voice communications 512 and/or the list of recorded voicemails 532 group the recorded voice communications/voicemails by caller ID. Further, in some embodiments, a user may manually enter notes associated with a voice communication/voicemail in notes column 518. In some embodiments, text characters may be entered using character keys on a remote control device. Alternatively, or in addition to, in some embodiments, set-top box 140 may display a user selectable keyboard on display unit 160.
Additionally, in some embodiments, user interface 510 includes a search component 516 enabling a user to search for a particular voice communication and/or voicemail. For example, in some embodiments, a user may search for a particular term found in notes column 518 and/or a particular caller ID. Further, in some embodiments, set-top box voice communication recording application 150 may use speech recognition software to parse the recorded voice communications/voicemails to enable a user to search for specific terms spoken during a voice communication/voicemail.
In addition, in some embodiments, a user may transfer a recorded voice communication and/or voicemail via e-mail option 520, SMS option 522, and/or via a USB option 524. In some embodiments, a user pre-configures e-mail addresses and/or mobile identification numbers (mobile phone numbers) for sending recorded voice communications and/or voicemails. Additionally, in some embodiments, a user interface may be presented in which a user may specify an e-mail address and/or a mobile phone number for sending a particular recorded voice communication.
USB option 524 transfers a selected recorded voice communication to an attached USB memory device. In some embodiments, alternative memory devices and connector ports may be used, including, but not limited to, an external hard drive or a memory card.
In addition, in some embodiments, a user may use a standard set-top box remote control device to playback a selected recorded phone conversation or voicemail. For example, in some embodiments, similar buttons for controlling playback of a recorded media content file may be used for playing back a recorded voice communication or voicemail. In some embodiments, user interface 510 and user interface 530 may display a progress bar 526 depicting the progress of a voice communication or voicemail is being played.
Accordingly, embodiments of the present invention disclose a set-top box for recording a voice communication and/or a voicemail. In one embodiment, the set-top box comprises memory for storing computer executable instructions, a data storage unit for storing recorded voice communications and recorded media content files; a line monitoring module for detecting a connected call on a communication line; and a processing unit for executing the computer executable instructions to record a voice communication in response to detecting the connected call.
As will be appreciated by one skilled in the art, the disclosed embodiments may be embodied as a system, method, or computer program product. Accordingly, the disclosed embodiments may be implemented entirely with hardware or as a software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the disclosed embodiments may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.
Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language, such as Java, Smalltalk, C++, or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
The disclosed embodiments are described above with reference to flowchart illustrations, sequence diagrams, and/or block diagrams. Each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The terminology used herein is for describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprise” and/or “comprising,” when used in this specification and/or the claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described to explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
In addition, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which may include one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. One of skill in this art will immediately envisage the methods and variations used to implement this invention in other areas than those described in detail. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.
Number | Name | Date | Kind |
---|---|---|---|
5831664 | Wharton et al. | Nov 1998 | A |
6684240 | Goddard | Jan 2004 | B1 |
6810506 | Levy | Oct 2004 | B1 |
6810526 | Menard et al. | Oct 2004 | B1 |
7478414 | Glusker et al. | Jan 2009 | B1 |
7571458 | Eyal | Aug 2009 | B1 |
7643564 | Sheynman | Jan 2010 | B2 |
7870279 | Chuang et al. | Jan 2011 | B2 |
8253558 | Emerson et al. | Aug 2012 | B2 |
8260363 | Roberts et al. | Sep 2012 | B2 |
8286215 | Daniels | Oct 2012 | B2 |
8312500 | Emerson et al. | Nov 2012 | B2 |
8316399 | Nush | Nov 2012 | B1 |
8467275 | Emerson et al. | Jun 2013 | B2 |
8478598 | Burckart et al. | Jul 2013 | B2 |
8627377 | LaFreniere et al. | Jan 2014 | B2 |
8627399 | White et al. | Jan 2014 | B2 |
8731620 | Roberts et al. | May 2014 | B2 |
8756646 | LaFreniere et al. | Jun 2014 | B2 |
8789113 | Goergen et al. | Jul 2014 | B2 |
8856855 | Goergen et al. | Oct 2014 | B2 |
9106976 | Emerson et al. | Aug 2015 | B2 |
9167206 | Goergen et al. | Oct 2015 | B2 |
20010021994 | Nash | Sep 2001 | A1 |
20020083468 | Dudkiewicz | Jun 2002 | A1 |
20020100044 | Daniels | Jul 2002 | A1 |
20020124252 | Schaefer et al. | Sep 2002 | A1 |
20020129368 | Schlack et al. | Sep 2002 | A1 |
20020147986 | Michael et al. | Oct 2002 | A1 |
20020188944 | Noble | Dec 2002 | A1 |
20020188949 | Wang et al. | Dec 2002 | A1 |
20020188959 | Piotrowski | Dec 2002 | A1 |
20030005448 | Axelsson et al. | Jan 2003 | A1 |
20030018977 | McKenna | Jan 2003 | A1 |
20030066069 | Mankovich | Apr 2003 | A1 |
20030128820 | Hirschberg et al. | Jul 2003 | A1 |
20030194966 | Fellenstein et al. | Oct 2003 | A1 |
20030208777 | Danker et al. | Nov 2003 | A1 |
20040019807 | Freund | Jan 2004 | A1 |
20040049785 | Grzeczkowski et al. | Mar 2004 | A1 |
20040203651 | Qu et al. | Oct 2004 | A1 |
20060020993 | Hannum et al. | Jan 2006 | A1 |
20060184989 | Slothouber | Aug 2006 | A1 |
20060212894 | Knudson et al. | Sep 2006 | A1 |
20060253886 | Khurana et al. | Nov 2006 | A1 |
20070079345 | McEnroe | Apr 2007 | A1 |
20070079353 | Boortz | Apr 2007 | A1 |
20070121651 | Casey et al. | May 2007 | A1 |
20070150273 | Yamamoto et al. | Jun 2007 | A1 |
20070220554 | Barton et al. | Sep 2007 | A1 |
20070280445 | Shkedi | Dec 2007 | A1 |
20070280446 | Hsieh et al. | Dec 2007 | A1 |
20080059992 | Amidon et al. | Mar 2008 | A1 |
20080107244 | Setzer et al. | May 2008 | A1 |
20080115164 | Kiiskinen | May 2008 | A1 |
20080134043 | Georgis et al. | Jun 2008 | A1 |
20080301732 | Archer et al. | Dec 2008 | A1 |
20090069038 | Olague et al. | Mar 2009 | A1 |
20090133069 | Conness et al. | May 2009 | A1 |
20090133070 | Hamano et al. | May 2009 | A1 |
20090150925 | Henderson | Jun 2009 | A1 |
20090158382 | Shaffer et al. | Jun 2009 | A1 |
20090164559 | Johnson et al. | Jun 2009 | A1 |
20090217324 | Massimi | Aug 2009 | A1 |
20090228929 | Cass | Sep 2009 | A1 |
20090249387 | Magdy et al. | Oct 2009 | A1 |
20090249451 | Su et al. | Oct 2009 | A1 |
20090265737 | Issa et al. | Oct 2009 | A1 |
20090293079 | McKee et al. | Nov 2009 | A1 |
20090300695 | White et al. | Dec 2009 | A1 |
20100058395 | Goergen et al. | Mar 2010 | A1 |
20100058415 | Goergen et al. | Mar 2010 | A1 |
20100058417 | Rondeau et al. | Mar 2010 | A1 |
20100064325 | Fishman et al. | Mar 2010 | A1 |
20100125884 | Howcroft | May 2010 | A1 |
20100149302 | Malik | Jun 2010 | A1 |
20100251325 | Gupta | Sep 2010 | A1 |
20100261466 | Chang et al. | Oct 2010 | A1 |
20110126251 | LaFreniere et al. | May 2011 | A1 |
20110126257 | Goergen et al. | May 2011 | A1 |
20110131604 | Van Hoff et al. | Jun 2011 | A1 |
20110270952 | Ray et al. | Nov 2011 | A1 |
20120018510 | Gardner | Jan 2012 | A1 |
20120223134 | Smith et al. | Sep 2012 | A1 |
20120223135 | Meek et al. | Sep 2012 | A1 |
20120233638 | Slaney et al. | Sep 2012 | A1 |
20120317599 | Emerson et al. | Dec 2012 | A1 |
20120324003 | Armstrong et al. | Dec 2012 | A1 |
20130031590 | Ivanov et al. | Jan 2013 | A1 |
20130241726 | Hunter et al. | Sep 2013 | A1 |
20130305275 | Emerson et al. | Nov 2013 | A1 |
20140053190 | Sirpal | Feb 2014 | A1 |
20140074621 | Chai et al. | Mar 2014 | A1 |
20140130093 | Goergen et al. | May 2014 | A1 |
20140259081 | Chatterjee | Sep 2014 | A1 |
20140282705 | Chatterjee et al. | Sep 2014 | A1 |
Number | Date | Country |
---|---|---|
1650927 | Apr 2006 | EP |
Entry |
---|
US 9,083,851, 07/2015, Goergen et al. (withdrawn) |
Parchomovsky, Gideon et al., “Fair Use Harbors”; 93 Va. L. Rev. 1483 (2007). |
U.S. Appl. No. 12/201,249; Notice of Allowance dated Mar. 14, 2014; 31 pages. |
U.S. Appl. No. 12/201,313; NonFinal Office Action dated Mar. 26, 2014; 10 pages. |
U.S. Appl. No. 12/201,313; Final Office Action dated Oct. 23, 2014; 11 pages. |
U.S. Appl. No. 12/201,313; Final Office Action dated Feb. 27, 2015; 11 pages. |
U.S. Appl. No. 14/152,696; Notice of Publication dated May 8, 2014; 1 page. |
U.S. Appl. No. 12/201,273; NonFinal Office Action dated Apr. 10, 2014; 35 pages. |
U.S. Appl. No. 12/201,273; Final Office Action dated Oct. 27, 2014; 38 pages. |
U.S. Appl. No. 12/201,273; Notice of Allowance dated Mar. 16, 2015; 28 pages. |
U.S. Appl. No. 12/201,436; Final Office Action dated Apr. 25, 2014; 30 pages. |
U.S. Appl. No. 13/750,537; Notice of Allowance dated Jan. 10, 2014; 11 pages. |
U.S. Appl. No. 13/910,706; Notice of Allowance dated Mar. 26, 2015; 30 pages. |
U.S. Appl. No. 13/567,367; NonFinal Office Action dated Jan. 30, 2014; 17 pages. |
U.S. Appl. No. 13/567,367; Final Office Action dated Jul. 23, 2014; 14 pages. |
U.S. Appl. No. 12/625,744; Notice of Allowance dated Feb. 5, 2014; 26 pages. |
U.S. Appl. No. 12/625,762; Notice of Allowance dated Jun. 3, 2014; 18 pages. |
U.S. Appl. No. 13/787,371; NonFinal Office Action dated Apr. 9, 2014; 30 pages. |
U.S. Appl. No. 13/787,371; Final Office Action dated Aug. 22, 2014; 32 pages. |
U.S. Appl. No. 13/787,371; Notice of Publication dated Sep. 11, 2014; 1 page. |
U.S. Appl. No. 13/787,371; NonFinal Office Action dated Mar. 5, 2015; 40 pages. |
U.S. Appl. No. 13/962,531; Notice of Publication dated Sep. 19, 2014; 1 page. |
U.S. Appl. No. 13/962,531; NonFinal Office Action dated Dec. 18, 2014; 47 pages. |
U.S. Appl. No. 12/201,313; NonFinal Office Action dated Jul. 1, 2015; 19 pages. |
U.S. Appl. No. 14/152,696; NonFinal Office Action dated Aug. 21, 2015; 26 pages. |
U.S. Appl. No. 13/567,367; NonFinal Office Action dated Jun. 10, 2015; 21 pages. |
U.S. Appl. No. 13/787,371; Final Office Action dated Jul. 30, 2015; 50 pages. |
U.S. Appl. No. 13/962,531; Final Office Action dated Jun. 19, 2015; 30 pages. |
Number | Date | Country | |
---|---|---|---|
20100169944 A1 | Jul 2010 | US |