Patent Grant
8245046
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 that does not have a compliant rights management interface, when the source device has 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 of 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 prevent or at least 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, video processors, televisions, monitors, projectors, and the like, do not comply with HDCP or other DRM techniques. The manufacturers of these processing and interface cards often do not 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 has a DRM compliant media interface to securely deliver media content to a destination device that does not have a DRM compliant media interface without compromising the integrity of the media content.
For the present invention, a watermarking process is employed as a supplement or alternative to a primary rights management (RM) technique for media content. In general, an interconnect device is used to connect a source device to a destination device, and allows the source device's compliant rights management (RM) interface to deliver media content that is associated with certain RM restrictions with little or no restriction to the destination device's non-compliant RM interface. Without the interconnect device, the media content could not be delivered at all or would be delivered with significant quality reductions or like restrictions to any non-compliant RM interface of any destination device. To help ensure that only authorized media content that is associated with RM restrictions is delivered to the non-compliant RM interface of the destination device, the interconnect device provides a compliant RM interface to connect to the source device, and monitors media content received from the source device to detect an embedded digital watermark. The interconnect device will take the necessary steps to determine if the watermark is authentic and control delivery of the media content to the destination device accordingly. The interconnect device may go back to the source device or a remote service to authenticate the watermark. If the watermark is authentic, the media content is passed by the interconnect device to the non-compliant interface of the destination device outside of the normal RM restrictions. Otherwise, delivery of the media content to the non-compliant interface is prevented or restricted in some manner by the interconnect device.
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.
Digital watermarking is an adaptation of traditional paper-based watermarking for digital media. In particular, digital watermarking is a process of embedding information into digital media content in a manner in which the information can be subsequently detected for use in a variety of applications. Embedding the watermark information for a watermark into media content actually modifies the data representing the media content. With image, audio, and video media content, such modifications are substantially imperceptible, and thus have little or no effect on the media content from a viewing or listening standpoint. Although applying a watermark has little impact on the quality of the media content, removing a watermark from the media content will degrade the media content.
Certain watermarking applications employ watermarks to prevent unauthorized copying or distribution of the media content. A digital watermark is generally used to identify the media content; a particular copy of the media content; an authorized owner, user, recipient, or distributor of the media content; or any combination thereof. Further, digital watermarks may be the same for all copies of certain content, or may be effectively unique to each copy of certain content to enable differentiation between copies of the same content.
A system that uses watermarks to prevent unauthorized copying or distribution of media content is generally able to process the media content and detect an embedded watermark. Detection of the embedded watermark results in identification of the embedded watermark information that was previously embedded in the media content when the watermark was originally applied. To authenticate a detected watermark, and thus the media content from which the watermark was extracted, the system may compare the watermark information with authentication information that is stored outside of the media content, or send the watermark information to another entity that has access to the authentication information and is able to compare the watermark information with the authentication information. Authentication of a given watermark may require comparing both the watermark information and content information with the authentication information. The content information may identify the media content itself or provide information related to the media content or a party associated therewith.
For the present invention, a watermarking process is employed as a supplement or alternative to a primary rights management (RM) technique for media content. In general, an interconnect device is used to connect a source device to a destination device, and allows the source device's compliant rights management (RM) interface to deliver media content that is associated with certain RM restrictions with little or no restriction to the destination device's non-compliant RM interface. Without the interconnect device, the media content could not be delivered at all or without significant quality or like restrictions to any non-compliant RM interface of any destination device. To help ensure that only authorized media content that is associated with RM restrictions is delivered to the non-compliant RM interface of the destination device, the interconnect device provides a compliant RM interface to connect to the source device, and monitors media content received from the source device to detect an embedded digital watermark. The interconnect device will take the necessary steps to determine if the watermark is authentic and control delivery of the media content to the destination device accordingly. The interconnect device may go back to the source device or a remote service to authenticate the watermark. If the watermark is authentic, the media content is passed by the interconnect device to the non-compliant interface of the destination device outside of the normal RM restrictions. Otherwise, the delivery of the media content to the non-compliant interface is prevented or restricted in some manner by the interconnect 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 illustrated in
The compliant RM interface 22 is primarily a digital media interface from which media content is presented by the source device 12. The compliant RM interface 22 may be a digital visual interface (DVI), high-definition multimedia interface (HDMI), or the like. For the present invention, the compliant RM interface 22 is compliant with a desired rights management mechanism that is used to protect the media content as it is delivered from the source device 12 to the destination device 14. Normally, the compliant RM interface 22 would not allow certain media content to be delivered to a destination device that does not have a compliant RM interface, or would impose significant quality-related restrictions on any media content being delivered to a destination device that does not have a compliant RM interface due to the destination device's 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 within RM restrictions, and then present the media content to the destination device 14 outside of the RM restrictions. As is described in detail further below, the present invention employs a watermark authentication scheme to ensure that only media content including an authentic watermark is delivered with little or no quality restrictions to the interconnect device 16.
In one embodiment, the control system 18 of the source device 12 will provide or be associated with a media control function 26, a watermarking 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 watermarking function 28 is used to authenticate watermarks based on watermark information associated with the watermarks, and perhaps based on content information related to or identifying the media content. In certain embodiments, the watermarking function 28 may be configured to apply digital watermarks to the media content using appropriate watermark information.
Notably, the compliant RM interface 22 or associated function 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. 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 cooperate with each other in a manner to facilitate coordinated control of media content delivery and authentication of watermarks that are recovered by 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 may coordinate with one another to ensure that the media content having an authentic watermark can be delivered to the destination device 14 outside of the RM restrictions, yet in a secure fashion.
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 compliant RM interface 22, wherein the encrypted media content is delivered by the compliant RM interface 22 to a source interface 36 of the interconnect device 16. Notably, the source interface 36 is preferably a compliant RM interface, which may cooperate with the compliant RM interface 22 of the source device 12 to ensure that media content having RM restrictions is delivered between these interfaces in an appropriate fashion. The encrypted media content is passed through a decryption function 38, which decrypts the encrypted media content to provide unencrypted media content, which is passed through a watermark detection function 40 to an encryption function 42. The watermark detection function 40 may process the unencrypted media content to detect watermarks that were applied to the media content and provide watermark information associated with any detected watermarks, and perhaps provide content information to the RM control function 34. The RM control function 34 may take action to determine whether the watermark recovered from the unencrypted media content is authentic.
Under control of the RM control function 34, the unencrypted media content is either re-encrypted by an encryption function 42 to provide encrypted media content and then passed to a destination interface 44, or passed to the destination interface 44 without re-encryption. Whether unencrypted or re-encrypted, the resulting media content is then delivered by the destination interface 44 to a non-compliant RM interface 46 of the destination device 14. If re-encrypted, the media content is preferably re-encrypted according to the appropriate RM requirements associated with the media content. As the unencrypted media content is delivered to the non-compliant RM interface 46, the unencrypted media content may be delivered to any number of sub-systems, such as an audio system 48, video system 50, processing system 52, 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 non-compliant RM interface 44 may be under the control of a control system 54.
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 restrictions, the media content may be delivered from the 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 44, directly or through an intermediate processing function (not shown), and the destination interface 44 will deliver the media content to the non-compliant RM interface 46.
Turning now to
The interconnect device 16 will then receive the media content via the source interface 36 (step 108), and deliver the media content to the destination device's non-compliant RM interface 46 via the destination interface 44 (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 non-compliant RM interface 46 or other function of the destination device 14 may 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 source device 12 will query the interconnect device 16 to determine if the destination device 14 is compliant with the RM restrictions via the source device's compliant RM interface 22 (step 112). In response, the interconnect device 16 will determine the presence of a compliant RM interface at the destination device 14 via the destination interface 44 (step 114). In operation, the destination interface 44 may attempt to interrogate the non-compliant RM interface 46 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 non-compliant RM interface 46 via the destination interface 44 to determine the compliance of the non-compliant RM interface 46 with the requisite rights management requirements. If there is no compliant rights management interface at the destination device 14 (step 116), as is the case in this example, the rights management control function 34 will notify the device driver 30 via the compliant RM interface 22 of the source device 12 or 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 may notify the media control function 26 that no compliant RM interface is available at the destination device 14 (step 120) and cooperate with the media control function 26 to determine if the media content has a watermark (step 122).
If the media content has a watermark (step 124), the device driver 30 will determine whether the watermark can be authenticated (step 126). If the watermark cannot be authenticated (step 128), the device driver 30 will notify the RM control function 34 of the interconnect device 16 via the communication interfaces 24, 32 that the watermark cannot be authenticated (step 130). Accordingly, the RM control function 34 of the interconnect device 16 will prevent the media content from being delivered to the destination device 14 outside of the RM restrictions (step 132). In other words, the RM control function 34 will allow a reduced quality version of the media content to be passed to the destination device 14 via the destination device's non-compliant RM interface 46, if the RM restrictions allow the reduced quality version of the media content to be delivered to devices with non-compliant RM interfaces. Any version of the media content that is restricted according to the RM restrictions either will not be delivered to the destination device 14, or will be delivered to the destination device 14 without certain encryption required by the RM restrictions.
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 compliant RM interface 22. The interconnect device 16 will treat the incoming media content as media content that is not associated with rights management restrictions, and effect delivery of the poorer quality media content to the non-compliant RM interface 46 of the destination device 14.
If the media content does not have a watermark (step 124), the device driver 30 of the source device 12 may employ the watermarking function 28 to apply a watermark to the media content, and provide authentication information for the watermark (step 134). The authentication information will be maintained at the source device 12, such that watermark information provided back to the source device 12 from the interconnect device 16 may be used to authenticate the watermark. After a watermark has been applied to media content (step 134), or after it has been determined that an existing watermark can be authenticated (step 128), the device driver 30 will notify the RM control function 34 of the interconnect device 16 via the communication interfaces 24, 32 that the watermark can be authenticated (step 136). The device driver 30 will then instruct the media control function 26 to initiate delivery of the watermarked media content to the interconnect device 16 (step 138). The media control function 26 will then initiate delivery of the watermarked media content via the source device's compliant RM interface 22 (step 140).
Next, the compliant RM interface 22 of the source device 12 will use compliance encryption information to encrypt the watermarked media content and deliver the watermarked media content to the source interface 36 of the interconnect device 16 (step 142). Although encryption is provided by the compliant RM interface 22 in this example, those skilled in the art will recognize that such encryption is essentially under the control of the control system 18, and may be provided by a separate encryption function (not shown). The decryption function 38 of the interconnect device 16 will decrypt the encrypted media content using appropriate compliance encryption information (step 144).
Notably, the watermark detection function 40 will process the decrypted media content in an effort to detect an embedded watermark, and if a watermark is detected, report its findings to the RM control function 34 (step 146). If a watermark was not detected (step 148), the RM control function 34 of the interconnect device 16 will take the necessary steps to prevent the media content from being delivered to the destination device 14 outside of the RM restrictions (step 150). Again, this may mean preventing any delivery of the media content to the destination device 14, or allowing a lower quality version of the media content to be delivered to the destination device 14 while preventing delivery of high quality media content to the destination device 14. If a high quality version of the media content is to be delivered to the destination device 14 under these conditions, the RM control function 44 may require the decrypted media content to be re-encrypted by the encryption function 42 according to certain RM restrictions.
If a watermark was detected in the unencrypted media content (step 148), the RM control function 34 of the interconnect device 16 will send corresponding watermark information, and optionally any necessary content information associated with the media content, to the device driver 30 of the source device 12 via the communication interfaces 24, 32 (step 152). Notably, the watermark information represents all or a portion of the information that is embedded in the media content to create the watermark. In response to receiving the watermark information, and perhaps the associated content information, the device driver 30 will attempt to authenticate the watermark in light of the watermark information and any associated content information (step 154). Notably, authentication of a watermark will not necessarily require associated content information. Those skilled in the art will recognize that different authentication schemes may or may not require additional information bearing on the media content itself in addition to the watermark information that was extracted from the media content to facilitate authentication. Further, authentication of the watermark will often involve comparing the watermark information, and perhaps the associated content information, with the authentication information that was created or otherwise stored in association with the watermark or media content in the source device 12.
If the watermark cannot be authenticated (step 156), the device driver 30 will notify the RM control function 34 of the interconnect device 16 via the communication interfaces 24, 32 that the watermark is not authentic (step 158), and the RM control function 34 of the interconnect device 16 will prevent the media content from being delivered to the destination device 14 outside of the RM restrictions, as described above (step 160).
If the device driver 30 determines that the watermark is authentic (step 156), the device driver 30 will notify the RM control function 34 of the interconnect device 16 via the communication interfaces 24, 32 that the watermark is authentic (step 162). The RM control function 34 of the interconnect device 16 will allow delivery of the media content to the non-compliant RM interface 46 of the destination device 14 outside of the normal RM restrictions (step 164). Accordingly, the decrypted media content is passed to the non-compliant RM interface 46 outside of the RM restrictions, and generally without being re-encrypted by the encryption function 42 (step 166). Thus, a high quality version of the media content may be passed to the destination device 14 in an unencrypted form.
If the media content is associated with rights management restrictions, and the destination device 14 has a compliant RM interface (not shown in
At this point, the compliant RM interface of the destination device 14 may decrypt the encrypted media content and deliver the unencrypted media content to the appropriate sub-system for further processing, presentation, or display (step not shown). 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 22 of the source device and the source interface 36, which is also a compliant RM interface, may be a DVI, HDMI, or like interface. 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 22 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 compliant RM interface 22 to allow the media content that is associated with RM restrictions and properly watermarked to be delivered to the non-compliant RM interface 46 of the destination device 14 with little or no restrictions.
In
With reference to
If RM restrictions are required for the media content (step 204), the source device 12 will query the interconnect device 16 to determine if the destination device 14 is RM compliant via the compliant RM interface 22 (step 212). The interconnect device 16 will check for the presence of a compliant RM interface at the destination device 14 (step 214), and if the destination device 14 does not have a compliant RM interface available (step 216), the RM control function 34 of the interconnect device 16 will notify the source device 12 via the compliant RM interface that a compliant RM interface is available at the destination device 14 (step 218). The reason that the RM control function 34 will tell the source device 12 that a compliant RM interface is available at the destination device 14 is to effectively trick the source device 12 into delivering the media content that is associated with RM restrictions to the interconnect device 16. As such, the interconnect device 16 can make the decision to deliver the media content on to the destination device 14 after analyzing any watermarks provided in the media content.
Accordingly, the source device 12 will effect delivery of the media content via the compliant RM interface 22 (step 220). The compliant RM interface 22 of the source device 12 will use compliance encryption information to encrypt the media content according to the RM restrictions, and then deliver the encrypted media content to the source interface 36 of the interconnect device 16 (step 222). The decryption function 38 of the interconnect device 16 will decrypt the encrypted media content using the compliance encryption information (step 224). Next, the watermark detection function 40 will process the decrypted media content to detect any watermarks embedded within the media content, and report any recovered watermark information to the RM control function 34 of the interconnect device 16 (step 226). Notably, content information may be provided along with the watermark information to the RM control function 34.
If a watermark was not detected (step 228), the RM control function 34 of the interconnect device 16 will prevent the media content from being delivered to the destination device 14 outside of the RM restrictions (step 230). If a watermark was detected (step 228), the RM control function 34 of the interconnect device 16 will send the watermark information and any necessary content information associated with the media content to the remote watermark server 56 via the communication interface 32 (step 232). The remote watermark server 56 will attempt to authenticate the watermark in light of the watermark information and any necessary content information (step 234).
If the watermark is not authentic (step 236), the remote watermark server 56 will notify the RM control function 34 of the interconnect device 16 via the communication interface 32 that the watermark is not authentic (step 238). The RM control function 34 of the interconnect device 16 will then prevent the media content from being delivered to the destination device 14 outside of the RM restrictions (step 240). If the watermark is authentic (step 236), the remote watermark server 56 will notify the RM control function 34 of the interconnect device 16 via the communication interface 32 that the watermark is authentic (step 242). As such, the RM control function 34 of the interconnect device 16 will allow delivery of the media content to the destination device 14 outside of the RM restrictions (step 244). Accordingly, the decrypted media content is passed to the non-compliant RM interface 46 of the destination device 14 via the destination interface 44 outside of the RM restrictions, and generally without being re-encrypted (step 246). Accordingly, high quality media content that is associated with RM restrictions, if watermarked, may be delivered to a destination device 14 without a compliant RM interface outside of the RM restrictions in a relatively secure fashion.
If the destination device 14 has a compliant RM interface (not shown in
In certain embodiments, the source device 12 and the remote watermark server 56 are available to authenticate watermarks in response to requests by the interconnect device 16. In other embodiments, one of the source device 12 or the remote watermark server 56 will not be available to authenticate watermarks. For instance, the source device 12 may not have such capabilities in certain embodiments. Regardless of the embodiment, an interconnect device 16 is able to coordinate with either a source device 12 that has a compliant RM interface 22 and perhaps an alternate communication interface 24 or a remote watermark server 56 to effectively and securely deliver watermarked media content that is associated with RM restrictions to a destination device 14 with a non-compliant interface 46. In one embodiment, an HDCP-compliant source device 12 may take advantage of the interconnect device 16 to be able to deliver authentic, full resolution media content at its highest quality to a non-HDCP-compliant destination device 14.
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 compliant RM interface 22 of the source device 12 or from the non-compliant RM interface 46 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. patent application Ser. No. 11/764,460, filed on Jun. 18, 2007, the disclosure of which is hereby incorporated by reference 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 |
| 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 |
| 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 |
| 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 |
| 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 | Nov 1995 | GB |
| 2005045647 | May 2005 | WO |
| 2006046099 | May 2006 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20110145935 A1 | Jun 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11764460 | Jun 2007 | US |
| Child | 13029577 | US |
