The present invention relates to delivering restricted media content, and in particular to providing an interconnect device that allows a source device to deliver media content to a destination device when the source device does not have a compliant rights management interface.
Copyright owners are in a constant battle against piracy of their media content. In the current digital world, high quality copies of digital content can be readily made and distributed without permission by the copyright owners. With the increasing availability of high definition video content and no or low compression audio content, the need to prevent unauthorized copies of audio and video content is greater than ever. In response to these needs, various digital rights management (DRM) techniques have evolved. DRM is a broad term that is used for various techniques used by copyright owners and authorized publishers to control access and restrict use of media content on associated electronic devices.
High-Bandwidth Digital Content Protection (HDCP) is a form of DRM that was developed by Intel Corporation and is widely used to control the delivery of audio and video media content from one electronic device to another. For HDCP, a source device is able to restrict the playback quality of otherwise high definition media content to DVD (Digital Video Disk) quality, or standard definition, when a destination device does not have an HDCP compliant media interface. Two common HDCP compliant media interfaces include the HDCP compliant High Definition Multimedia Interface (HDMI) and the HDCP compliant Digital Video Interface (DVI). When the destination device does have an HDCP compliant media interface, the high definition media content is generally encrypted by the source device and delivered to the destination device in a secure fashion.
For HDCP, the media interfaces of the respective source and destination devices are able to communicate with each other and play pivotal roles to ensure that the media content is protected. The media interface of the source device will authenticate the media interface of the destination device, and the respective media interfaces will exchange any necessary encryption information to facilitate encryption of the media content by the media interface of the source device and decryption of the encrypted media content by the media interface of the destination device. Notably, this functionality is generally provided in the hardware at the media interfaces and not in the higher level control systems of the respective electronic devices. Other DRM techniques, such as the Advanced Access Content System (AACS), operate in a similar fashion.
Unfortunately, many audio and video processing and interface cards, which often provide the actual media interfaces for various types of electronic devices, such as personal computers, DVD players, set-top boxes, digital video recorders, audio processors and receivers, and video processors, do not comply with HDCP or other DRM techniques. The manufacturers of these processing and interface cards often do not want to incorporate DRM techniques due to increased processing overhead, increased complexity, licensing costs, liability, and the like. Even though the control systems of the electronic devices in which the processing and interface cards are located generally have the processing capability to provide the functionality of compliant media interfaces, the use of non-HDCP compliant processing and interface cards results in non-HDCP compliant electronic devices. Further, legacy products may not have interfaces that are compliant with current DRM requirements. As such, users of non-compliant electronic devices are unable to enjoy the higher resolution audio and video that would otherwise be available to them, if the processing and interface cards were HDCP compliant.
Accordingly, there is a need for a technique to allow a source device that does not have a DRM compliant media interface to securely deliver media content to a destination device that does have a DRM compliant media interface without compromising the security of the media content.
The present invention provides an interconnect device that connects a source device to a destination device, and allows the source device's non-compliant rights management (RM) interface to deliver media content with little or no restriction to the destination device's compliant RM interface. Without the interconnect device, the media content could not be delivered at all or without significant restriction to the compliant RM interface of the destination device. The interconnect device is coupled to the non-compliant RM interface and an alternate communication interface of the source device, as well as to the compliant RM interface of the destination device. In operation, the source device will determine whether media content to be delivered to the destination device is associated with rights management restrictions and deliver a corresponding notification to the interconnect device via the alternate communication interface.
If the media content is associated with rights management, the interconnect device is able to determine whether the destination device has a compliant RM interface. Via the alternate communication interface, the interconnect device may notify the source device of the presence of the compliant RM interface at the destination device. The interconnect device may also interact with the destination device's compliant RM interface to obtain RM encryption information, which is used for encrypting any media content that is associated with rights management prior to being delivered to the compliant RM interface. Assuming the compliant RM interface is available at the destination device, the source device will encrypt the media content using compliance encryption information, which may be different than the RM encryption information, and deliver the encrypted media content to the interconnect device via the source device's non-compliant RM interface.
The interconnect device may have previously obtained the compliance encryption information via the alternate communication interface of the source device or from another entity. Upon receiving the encrypted media content, the interconnect device will decrypt the encrypted media content using the compliance encryption information. Since the media content must be encrypted using RM encryption information before being delivered to the destination device's RM compliant media interface, the interconnect device will re-encrypt the media content using the RM encryption information. The re-encrypted media content is then delivered to the RM compliant interface of the destination device. As such, media content associated with digital or other rights management may be provided from a non-compliant RM interface at a source device to a compliant RM interface at a destination device in a substantially unrestricted and secure fashion.
Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the invention, and together with the description serve to explain the principles of the invention.
The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
The present invention provides an interconnect device that connects a source device to a destination device and allows the source device's non-compliant rights management (RM) interface to deliver media content with little or no restriction to the destination device's compliant RM interface. Without the interconnect device, the media content could not be delivered at all or without significant restriction to the compliant RM interface of the destination device. Prior to delving into the operation details of the interconnect device, an overview of the interaction and basic architecture of a source device, interconnect device, and destination device are provided according to one embodiment of the present invention in
As illustrated, a source device 12 is coupled to a destination device 14 by an interconnect device 16. The source device 12 may take the form of a personal computer, DVD player, set-top box, digital video recorder, audio processor or receiver, video processor, or the like. The source device 12 has a control system 18 that is associated with a media source 20, a non-compliant RM interface (I/F) 22, and a communication interface 24. The media source 20 is the receiver or storage mechanism from which media content is obtained for delivery by the source device 12. The communication interface 24 is any type of communication interface, such as a personal area network (PAN) interface, local area network (LAN) interface, wireless LAN (WLAN) interface, or wide area network (WAN) interface. In general, the communication interface 24 is an alternate interface to the non-compliant RM interface 22, and is used to allow the source device 12 and the interconnect device 16 to communicate with each other to facilitate certain aspects of the present invention, which will be described below in further detail.
The non-compliant RM interface 22 is primarily a digital media interface from which media content is presented by the source device 12. The non-compliant RM interface 22 may be a digital visual interface (DVI), high-definition multimedia interface (HDMI), or the like. For the present invention, the non-compliant RM interface 22 is not compliant with a desired rights management mechanism that is used to detect the media content as it is delivered from the source device 12 to the destination device 14. Normally, the non-compliant RM interface 22 would not allow certain media content to be delivered to the destination device 14, or would impose significant quality-related restrictions on any media content being delivered to the destination device 14 due to the inability to comply with the rights management associated with the media content. The interconnect device 16 is able to cooperate with the source device 12 to allow the media content to be delivered from the source device 12 to the interconnect device 16 with little or no restriction, and then present the media content to the destination device 14 according to the rights management required for delivering the media content from one device to another.
The control system 18 of the source device 12 will provide or be associated with a media control function 26, a compliance encryption function 28, and a device driver 30. In general, the media control function 26 operates to control delivery and playback of the media content provided by the media source 20. The compliance encryption function 28 is employed to encrypt the media content in a secure fashion, such that the encrypted media content can be safely and securely delivered to the interconnect device 16 via the non-compliant RM interface 22 of the source device 12. The device driver 30 is configured to communicate with the interconnect device 16 through the communication interface 24 to allow the source device 12 and the interconnect device 16 to coordinate with each other in a manner allowing the media content to be encrypted by the source device 12 and decrypted at the interconnect device 16.
The interconnect device 16 will have a communication interface 32, which is coupled to the communication interface 24 of the source device 12. Through the communication interface 32, an RM control function 34 of the interconnect device 16 can effectively communicate with the device driver 30 of the source device 12. The RM control function 34 effectively coordinates operation of the interconnect device 16 with both the source device 12 and the destination device 14. In general, the RM control function 34 of the interconnect device 16 and the device driver 30 of the source device 12 will coordinate with one another to ensure that the media content is encrypted by the source device 12 in a fashion to enable decryption of the encrypted media content by the interconnect device 16. The exchange of this encryption related information, referred to hereinafter as “compliance encryption information,” is necessary to facilitate encryption and decryption of the media content. The compliance encryption information is provided or exchanged through the communication interfaces 24, 32 of the source and interconnect devices 12, 16, respectively, and not through the non-compliant RM interface 22 of the source device 12.
When the media control function 26 cooperates with the media source 20 to have media content delivered toward the destination device 14, the media content may be encrypted based on the compliance encryption information by the compliance encryption function 28, wherein the encrypted media content is output through the non-compliant RM interface 22 to a source interface 36 of the interconnect device 16. The encrypted media content is passed through a compliance decryption function 38 to provide the unencrypted media content, which is subsequently re-encrypted by an RM encryption function 40 using RM encryption information. The RM encrypted media content is then passed through a destination interface 42 to a compliant RM interface 44 of the destination device 14. Notably, the media content is encrypted according to the appropriate rights management requirements when delivered from the interconnect device 16 to the compliant RM interface 44 of the destination device 14. Assuming the encrypted media content is decrypted based on the RM encryption information in the compliant RM interface 44, the unencrypted media content may be delivered to any number of sub-systems, such as an audio system 46, video system 48, processing system 50, or the like, depending on the type of media represented by the media content and the type of functionality provided by the destination device 14. Notably, all of the sub-systems as well as the compliant RM interface 44 may be under the control of a control system 52.
The destination device 14 may be the final destination of the media content before being presented to a user, or the destination device 14 may represent an intermediate node, which may act as a source device for delivering the media content to yet another destination device 14. As such, the destination device 14 may take various forms, such as a digital video recorder, set-top box, media server, television, display, or video monitor.
If the media content provided by the source device 12 is not subject to rights management, the compliance encryption function 28 may be bypassed, wherein the media content is delivered from the non-compliant RM interface 22 of the source device 12 to the source interface 36 of the interconnect device 16. At this point, the source interface 36 may deliver the media content to the destination interface 42, directly or through an intermediate processing function (not shown), wherein the unencrypted media content may be delivered to the compliant RM interface 44 and then processed accordingly.
Continuing with
Turning now to
The interconnect device 16 will receive the media content via the source interface 36, and deliver the media content to the destination device's compliant RM interface 44 via the destination interface 42 (step 110). The destination device 14 can then process the media content as desired. Notably, media content that is not associated with rights management restrictions may not be encrypted for transmission, and thus the compliant RM interface 44 will not need to decrypt the media content prior to initiating any requisite processing of the media content.
If the device driver 30 analyzes the media content and determines that there are rights management restrictions associated with the media content (step 104), the device driver 30 will notify the RM control function 34 of the interconnect device 16 that the media content has associated rights management restrictions (step 112). If it has not already done so, the RM control function 34 will determine the presence of a compliant RM interface 44 at the destination device 14 via the destination interface 42 (step 114). In operation, the destination interface 42 may interrogate the compliant RM interface 44 to determine its compliance with the requisite rights management requirements, and then report back to the RM control function 34. Alternatively, the RM control function 34 may interact with the compliant RM interface 44 via the destination interface 42 to determine the compliance of the compliant RM interface 44 with the requisite rights management requirements. If there is no compliant rights management interface at the destination device 14 (step 116), the rights management control function 34 will notify the device driver 30 via the communication interfaces 24, 32 that there is no compliant RM interface available at the destination device 14 (step 118). The device driver 30 will notify the media control function 26 that no compliant RM interface is available at the destination device 14 (step 120).
In response, the media control function 26 may take various actions, including preventing delivery of the media content, restricting the quality of the media content that is delivered, and the like (step 122). If the media content may be delivered to the destination device 14 at a restricted quality level, the media control function 26 may operate to downconvert the media content to a lower resolution, re-encode the media content at a higher compression rate, or the like, and then facilitate delivery of the media content to the interconnect device 16 via the non-compliant RM interface 22. The interconnect device 16 will treat the incoming media content as media content that is not associated with rights management, and effect delivery of the poorer quality media content to the compliant RM interface 44 of the destination device 14.
If the media content is associated with rights management restrictions, and the destination device 14 has a compliant RM interface 44 (step 116), the RM control function 34 will notify the device driver 30 via the communication interfaces 24, 32 that a compliant RM interface 44 is available at the destination device 14 (step 124). The device driver 30 will notify the media control function 26 that a compliant RM interface 44 is available at the destination device 14 (step 126). The device driver 30 will also provide compliance encryption information via the communication interfaces 24, 32 to the RM control function 34 of the interconnect device 16 (step 128). Notably, the compliance encryption information is information sufficient to allow the RM control function 34 to instruct the compliance decryption function 38 to decrypt any encrypted media content to be delivered to the interconnect device 16 by the source device 12.
To ensure that the media content is delivered to the destination device 14 according to the rights management requirements, the RM control function 34 may receive rights management encryption information from the compliant RM interface 44 of the destination device 14 via the destination interface 42 (step 130). At this point, the RM control function 34 has compliance encryption information to assist with decrypting encrypted media content provided by the source device 12, and RM encryption information to assist in re-encrypting the unencrypted media content prior to delivering it to the compliant RM interface 44 of the destination device 14.
The media control function 26 of the source device 12 will initiate delivery of the media content (step 132), and as such, the media source 20 will begin delivery of the media content. The compliance encryption function 28 of the source device 12 uses the compliance encryption information to encrypt the media content. The encrypted media content is delivered via the non-compliant RM interface 22 of the source device 12 to the source interface 36 of the interconnect device 16 (step 134). The encrypted media content from the source device 12 is passed through the compliance decryption function 38, which will decrypt the encrypted media content using the compliance encryption information (step 136). Based on the RM control function 34, the unencrypted media content from the compliance decryption function 38 is re-encryption by the RM encryption function 40 using the RM encryption information, and the re-encrypted media content is then delivered through the destination interface 42 of the interconnect device 16 to the compliant RM interface 44 of the destination device 14 (step 138).
At this point, the compliant RM interface 44 may decrypt the re-encrypted media content and deliver the unencrypted media content to the appropriate sub-system for further processing, presentation, or display (step not shown). As indicated above, the destination device 14 may be an intermediate device that acts as a destination device when receiving media content from a source device 12, and then acts as a source device for sending the media information to another destination device.
In one embodiment, the rights management mechanism is an HDCP, AACS, or like digital rights management system. Accordingly, the compliant RM interface 44 and the destination interface 42 may be a DVI or HDMI. Those skilled in the art will recognize other types of digital media interfaces that will benefit from the present invention. In a digital rights management embodiment, the compliant RM interface 44 may be an HDCP-compliant media interface, and the interconnect device 16 may cooperate with the source device 12 via the communication interface 24 and the non-compliant RM interface 22 to allow the media content to be delivered to the destination device 14 with little or no restrictions. By allowing the RM control function 34 of the interconnect device 16 to communicate with the device driver 30 of the source device 12 via a communication interface 24 other than the non-compliant RM interface 22, the source device 12 and the interconnect device 16 can cooperate to securely transfer the media content to the interconnect device 16, which will process the media content as necessary to subsequently provide the media content in an appropriate fashion to the compliant RM interface 44. As such, the destination device 14 does not need to be aware of the presence of the interconnect device 16 or the functionality provided by the interconnect device 16.
However, the source device 12 and the interconnect device 16 must coordinate with each other or be coordinated by another device, such as a remote RM server 54 as illustrated in
Regardless of the embodiment, a source device 12 that has a non-compliant RM interface 22 and an alternate communication interface 24 may coordinate with the interconnect device 16 to effectively and securely deliver the media content to the interconnect device 16, which will take the necessary steps to interact with the destination device 14 to deliver the media content in an appropriate fashion to a compliant RM interface 44. Thus, a non-HDCP-compliant source device 12 may take advantage of the interconnect device 16 to be able to deliver full resolution media content at its highest quality to an HDCP-compliant RM interface 44, without risking the integrity of the media content.
Further, the encryption and decryption provided by the source device 12, interconnect device 16, and destination device 14 may take various forms and will include traditional encryption and decryption using appropriate keys and algorithms, and may be provided in a full or limited fashion. Further, such encryption will include frequency-based distortion as well as time-based distortion of audio and video content. Thus, the encryption or decryption associated with the present invention includes but is not limited to full encryption of audio and video content, limited encryption of all or a portion of audio or video content, frequency-based distortion of all or part of audio or video content, and time-based distortion of all or part of audio or video content. Aspects of the present invention may be extended to media content other than audio or video content, such as digital images, data, and the like.
In one embodiment of the present invention, the interconnect device 16 is provided in the form of a cable that is used to connect a source device 12 to a destination device 14. The electronics necessary to provide the various interfaces and functions may have a separate power supply, or power may be derived from the non-compliant RM interface 22 of the source device 12 or from the compliant RM interface 44 of the destination device 14.
With reference to
Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
The present application is a continuation of U.S. application Ser. No. 11/689,059, filed Mar. 21, 2007, the disclosure of which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5613004 | Cooperman et al. | Mar 1997 | A |
5687236 | Moskowitz et al. | Nov 1997 | A |
6141753 | Zhao et al. | Oct 2000 | A |
6389541 | Patterson | May 2002 | B1 |
6735699 | Sasaki et al. | May 2004 | B1 |
6751670 | Patterson | Jun 2004 | B1 |
6804779 | Carroni et al. | Oct 2004 | B1 |
6980204 | Hawkins et al. | Dec 2005 | B1 |
6987985 | Purkayastha et al. | Jan 2006 | B2 |
7003131 | Watson et al. | Feb 2006 | B2 |
7016668 | Vaidyanathan et al. | Mar 2006 | B2 |
7036024 | Watson | Apr 2006 | B2 |
7065607 | England et al. | Jun 2006 | B2 |
7069580 | Deitz et al. | Jun 2006 | B1 |
7242766 | Lyle | Jul 2007 | B1 |
7369677 | Petrovic et al. | May 2008 | B2 |
7415617 | Ginter et al. | Aug 2008 | B2 |
7562397 | Mithal et al. | Jul 2009 | B1 |
7840489 | Candelore | Nov 2010 | B2 |
7895442 | Adams et al. | Feb 2011 | B1 |
20010051996 | Cooper et al. | Dec 2001 | A1 |
20020010759 | Hitson et al. | Jan 2002 | A1 |
20020049580 | Kutaragi et al. | Apr 2002 | A1 |
20020054578 | Zhang et al. | May 2002 | A1 |
20020061029 | Dillon | May 2002 | A1 |
20020104003 | Iwamura | Aug 2002 | A1 |
20020104099 | Novak | Aug 2002 | A1 |
20020122141 | Lee | Sep 2002 | A1 |
20020129367 | Devara | Sep 2002 | A1 |
20020141578 | Ripley et al. | Oct 2002 | A1 |
20020144267 | Gutta et al. | Oct 2002 | A1 |
20020156842 | Signes et al. | Oct 2002 | A1 |
20020168082 | Razdan | Nov 2002 | A1 |
20030009769 | Hensgen et al. | Jan 2003 | A1 |
20030050055 | Ting et al. | Mar 2003 | A1 |
20030081580 | Vaidyanathan et al. | May 2003 | A1 |
20030084294 | Aoshima et al. | May 2003 | A1 |
20030093665 | Cooper et al. | May 2003 | A1 |
20030161268 | Larsson et al. | Aug 2003 | A1 |
20030191850 | Thornton | Oct 2003 | A1 |
20030221100 | Russ et al. | Nov 2003 | A1 |
20040008864 | Watson et al. | Jan 2004 | A1 |
20040010692 | Watson | Jan 2004 | A1 |
20040010694 | Collens et al. | Jan 2004 | A1 |
20040030798 | Andersson et al. | Feb 2004 | A1 |
20040042421 | Mahany | Mar 2004 | A1 |
20040070593 | Neely et al. | Apr 2004 | A1 |
20040073916 | Petrovic et al. | Apr 2004 | A1 |
20040083487 | Collens et al. | Apr 2004 | A1 |
20040086122 | Watson | May 2004 | A1 |
20040088557 | Malcolm et al. | May 2004 | A1 |
20040117824 | Karaoguz et al. | Jun 2004 | A1 |
20040139047 | Rechsteiner et al. | Jul 2004 | A1 |
20040156528 | Joo et al. | Aug 2004 | A1 |
20040187005 | Molaro | Sep 2004 | A1 |
20040248615 | Purkayastha et al. | Dec 2004 | A1 |
20040263941 | Chen et al. | Dec 2004 | A1 |
20040264372 | Huang | Dec 2004 | A1 |
20050008017 | Datta et al. | Jan 2005 | A1 |
20050034001 | Pontarelli | Feb 2005 | A1 |
20050050103 | Kesteloot et al. | Mar 2005 | A1 |
20050081042 | Venkatesan et al. | Apr 2005 | A1 |
20050086069 | Watson et al. | Apr 2005 | A1 |
20050097331 | Majidimehr et al. | May 2005 | A1 |
20050108769 | Arnold et al. | May 2005 | A1 |
20050120127 | Bradley et al. | Jun 2005 | A1 |
20050123135 | Hunt et al. | Jun 2005 | A1 |
20050125405 | Watson et al. | Jun 2005 | A1 |
20050144468 | Northcutt et al. | Jun 2005 | A1 |
20050182876 | Kim et al. | Aug 2005 | A1 |
20050182989 | Zarnke et al. | Aug 2005 | A1 |
20050183120 | Jain et al. | Aug 2005 | A1 |
20050192987 | Marsh | Sep 2005 | A1 |
20050201726 | Malcolm et al. | Sep 2005 | A1 |
20050204391 | Hunleth et al. | Sep 2005 | A1 |
20050216942 | Barton | Sep 2005 | A1 |
20050220321 | Langelaar | Oct 2005 | A1 |
20050239497 | Bahl et al. | Oct 2005 | A1 |
20050251486 | Nair | Nov 2005 | A1 |
20050286438 | Rajkotia | Dec 2005 | A1 |
20060010274 | Olson | Jan 2006 | A1 |
20060015735 | Kudo et al. | Jan 2006 | A1 |
20060048185 | Alterman | Mar 2006 | A1 |
20060048186 | Alterman | Mar 2006 | A1 |
20060050880 | Taylor et al. | Mar 2006 | A1 |
20060053452 | Lee et al. | Mar 2006 | A1 |
20060053472 | Goto et al. | Mar 2006 | A1 |
20060056349 | Nakatugawa et al. | Mar 2006 | A1 |
20060059560 | Montulli | Mar 2006 | A1 |
20060072786 | Watson et al. | Apr 2006 | A1 |
20060075243 | Lakamp et al. | Apr 2006 | A1 |
20060085534 | Ralston et al. | Apr 2006 | A1 |
20060085830 | Bruck et al. | Apr 2006 | A1 |
20060095401 | Krikorian et al. | May 2006 | A1 |
20060095471 | Krikorian et al. | May 2006 | A1 |
20060095472 | Krikorian et al. | May 2006 | A1 |
20060095792 | Hurtado et al. | May 2006 | A1 |
20060123235 | Vanstone | Jun 2006 | A1 |
20060126888 | Talstra et al. | Jun 2006 | A1 |
20060127037 | Van Hoff et al. | Jun 2006 | A1 |
20060133644 | Wells et al. | Jun 2006 | A1 |
20060156003 | Zhang et al. | Jul 2006 | A1 |
20060156416 | Huotari et al. | Jul 2006 | A1 |
20060158968 | Vanman et al. | Jul 2006 | A1 |
20060161776 | Van Der Veen et al. | Jul 2006 | A1 |
20060173794 | Sellars et al. | Aug 2006 | A1 |
20060174128 | Yuval | Aug 2006 | A1 |
20060193492 | Kuzmich et al. | Aug 2006 | A1 |
20060200416 | White et al. | Sep 2006 | A1 |
20060282676 | Serret-Avila et al. | Dec 2006 | A1 |
20070056046 | Claudatos et al. | Mar 2007 | A1 |
20070100771 | Eckleder et al. | May 2007 | A1 |
20070124474 | Margulis | May 2007 | A1 |
20070130585 | Perret et al. | Jun 2007 | A1 |
20070133673 | Imaizumi | Jun 2007 | A1 |
20070269044 | Bruestle | Nov 2007 | A1 |
20070294738 | Kuo et al. | Dec 2007 | A1 |
20080005676 | Evans et al. | Jan 2008 | A1 |
20080044087 | Levy et al. | Feb 2008 | A1 |
20080148063 | Hanko et al. | Jun 2008 | A1 |
20090037388 | Cooper et al. | Feb 2009 | A1 |
20090287837 | Felsher | Nov 2009 | A1 |
20090287940 | Carr | Nov 2009 | A1 |
Number | Date | Country |
---|---|---|
2306869 | May 1997 | GB |
2005045647 | May 2005 | WO |
2006046099 | May 2006 | WO |
Entry |
---|
Author Unknown, “Double 108Mbps Wireless PC Card (WG511U), Netgear, Inc.,” PC Connection, 2006, http://http://www.pcconnection.com/ProductDetail?sku=5373172&SourceID=k40132, accessed on Apr. 5, 2006, 2 pages. |
Author Unknown, “DVI Extender via CAT5: Extend a single link digital DVI display up to 150 feet,” Network Technologies Incorporated, http://www.networktechinc.com/cat5-dvi.html, accessed on Jul. 13, 2007, 2 pages. |
Author Unknown, “Gefen—HDMI CAT-5 Extreme,” User Manual, Gefen Inc., 2006, 16 pages. |
Author Unknown, “Global-Link Product Manual,” Logical Solutions Inc., Copyright 2003, Revision C, Jan. 2005, 68 pages. |
Author Unknown, “HDTV Extender: Extend a HDTV display and speakers up to 600 feet from a YPbPr component video source,” Network Technologies Incorporated, 2005, www.nti1.com/hdtv-extend.html, 2 pages. |
Author Unkown, “High-bandwidth Digital Content Protection System,” Digital Content Production LLC, Revision 1.3, Dec. 21, 2006, pp. 1-20. |
Author Unknown, “Introducing The World's First ‘Legal’ HDMI Distribution Amp with HDCP on Every Port!”, PureLink Digital Extender, Dtrovision LLC, http://www.dtrovision.com, accessed Jul. 13, 2007, 2 pages. |
Author Unknown, “Kaleidescape Home Page”, Kaleidescape, Inc., http://www.kaleidescape.com, accessed Jul. 13, 2007, 1 page. |
Author Unknown, “KVMPro—KVM Switch,” http://www.kvmpro.com/dvi-extender-c-38.html, accessed Nov. 11, 2006, 4 pages. |
Author Unknown, “KVM over IP Extender—Logical Solutions,” http://www.kvmpro.com/thinklogical-kvm-extnders-dvi-global-link-p-202.html, accessed Nov. 1, 2006, 3 pages. |
Author Unknown, “MediaMax Overview”, Axonix Corporation, http://www.axonix.com/mediamax/, accessed Jul. 13, 2007, 2 pages. |
Author Unknown, “PureLink Digital Extender User Manual,” Dtrovision LLC, 2006, 6 pages. |
Author Unknown, “Remote Access to USB Devices,” Network Technologies Incorporated, http://www.networktechinc.com/usb-ip-extender.html, accessed Nov. 1, 2006, 2 pages. |
Author Unknown, “Secure KVM over IP: Global-link—Thinklogical”, http://www.thinklogical.com/products/globalLink.php, accessed Jul. 13, 2007, 1 page. |
Author Unknown, “ST-C5DVI-150:150 foot DVI Video Extender,”Installation and Operation Manual,Software Version 1.2, Network Technologies Inc., 2006, Manual 063 Revision, Oct. 16, 2006, 11 pages. |
Author Unknown, “The DVI 1000 HD (EXT-DVI-1000),” http://www.kvmpro.com/gefen-kvm-extenders-dvi-the-dvi-1000-hd-p-213.html, accessed Nov. 1, 2006, 2 pages. |
Author Unknown, “The DVI CAT5 Extender, (EXT-DVI-CAT5),” http://www.kvmpro.com/gefen-kvm-extenders-dvi-the-dvi-cat5-extender-p-214.html, acessed Nov. 1, 2006, 3 pages. |
Author Unknown, “USB KVM Extender copper CAT5 RJ45,” Network Technologies Incorporated, http://www.networktechinc.com/extenders.html, accessed Nov. 1, 2006, 3 pages. |
Dittmann, J. et al., “Robust MPEG Video Watermarking Technologies,” ACM Multimedia, Bristol, UK, Aug. 1998, pp. 71-80. |
Fridrich, J., “Applications of Data Hiding in Digital Images,” Tutorial for the ISPACS '98 Conference in Melbourne, Australia, Nov. 4-6, 1998, 33 pages. |
Judge, P. et al., “WHIM: Watermarking Multicast Video with a Hierarchy of Intermediaries,” Computer Networks: The International Journal of Computer and Telecommunications Networking, Aug. 21, 2002, vol. 39, Issue 6, pp. 699-712. |
Koch, E. et al., “Towards Robust and Hidden Image Copyright Labeling,” IEEE Workshop on Nonlinear Signal and Image Processing, presented Jun. 20-22, 1995, pp. 452-455. |
Lyle, “HDCP: what it is and how to use it,” Apr. 18, 2002, www.ednmag.com, http://www.edn.com/article/ca209091.html?q=&q=HDCP, 6 pages. |
Raisinghani, V., “ECLAIR: An Efficient Cross Layer Architecture for Wireless Protocol Stacks,” 5th World Wireless Congress, San Francisco, California, May 25-28, 2004, 6 pages. |
Setton, E. et al., “Cross-Layer Design of Ad Hoc Networks for Real-Time Video Streaming,” IEEE Wireless Communications, Aug. 2005, vol. 12, Issue 4, pp. 59-65. |
Srivastava, V. et al., “Cross-Layer Design: A Survey and the Road Ahead,” IEEE Communications Magazine, Dec. 2005, vol. 43, Issue 12, pp. 112-119. |
Non-final Office Action for U.S. Appl. No. 11/689,059 mailed Apr. 15, 2010, 25 pages. |
Final Office Action for U.S. Appl. No. 11/689,059 mailed Dec. 8, 2010, 25 pages. |
Non-final Office Action for U.S. Appl. No. 11/689,059 mailed Mar. 17, 2011, 24 pages. |
Notice of Allowance for U.S. Appl. No. 11/689,059 mailed Sep. 15, 2011, 8 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 11689059 | Mar 2007 | US |
Child | 13350961 | US |