1. Technical Field
The present disclosure generally relates to digital media devices, and more specifically, to managing media content associated with digital media devices.
2. Description of the Related Art
Digital media recording devices can be used for recording media signals, such as audio and/or video signals, in a digital format. Such devices may also be used for the storage and playback of such signals. Specific examples of such digital media recording devices are a Digital Video Recorder (DVR) and a Personal Video Recorder (PVR).
In general, a DVR may be used to schedule and record future television programs, for buffering live television programs in a time-shift buffer, and/or playback of the digitally recorded media. The incoming media signals may be received, potentially decrypted and/or encoded, and digitally stored on a storage medium. The storage medium is commonly a non-volatile storage device such as a hard disk drive (HDD) (i.e., hard drive), among other acceptable mediums. Such an HDD can write the digital media data on a magnetic surface of the HDD disk platters and read the media data at later times for playback.
From time-to-time, users of a DVR may wish to upgrade or replace their current DVR with a replacement DVR. For example, the replacement DVRs may include new features not supported by the current DVR. However, in some cases, users balk at upgrading the DVR because media content stored to the current DVR is unable to be transferred to the replacement DVR. Thus, many users choose to refrain from upgrading their DVR, losing out on many exciting features in new models. Additionally, producers of DVRs and others who benefit from their sale or rental, potentially lose revenue over the lost sales.
Accordingly, the present disclosure includes a number of potential embodiments for resolving the aforementioned deficiencies of conventional media recording devices.
The components in the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding parts throughout the several views.
According to some embodiments, DVR 102 is also embedded within, or otherwise associated with, other electronic devices such as a cable television set-top box (STB), a tuner, a television, and/or a satellite-television receiver, or a playback device, such as a television, among others.
Media content is also referred to herein as media programs or media programming. Some examples of media programming used herein include, but are not intended to be limited to, television programs and radio programs. An instance of media programming or media content could be, for example, a recording of a television show (e.g., an episode of Smallville). A series of media programming could be, for example, a number of episodes of a television show (e.g., the last five recordings of Smallville).
The media content is recorded by the digital media recorder and stored as media data. In some instances, such media data is encoded audio and/or video signals, among other representations of the media content that is in a form suitable for processing by DVR 102. Such media signals could be analog and/or digital signals.
DVR 102 is configured to receive media signals from a media signal source 104, and is also in communication with a playback device, such as television 106. According to some embodiments, the playback device is a computer display, portable device, or audio receiver, among other devices capable of emitting or displaying media.
Media signal source 104 is any of a number of sources of analog and/or digital media signals, such as video and/or audio signals. According to some embodiments, media signal source 104 is, for example, among others, a satellite television source, an over-the-air broadcast source, a cable-television (CATV) system, or a server configured to stream, or otherwise provide, media signals over a network (i.e., LAN., WAN, Internet, etc.).
In some instances, media signal source 104 also transmits additional network data, including Internet traffic, teletext, closed-captioning, and/or programming information, among others. Media signal source 104 transmits such signals to DVR 102, which is located in one implementation, among others, remotely at a customer premises 108. Although only one media signal source is depicted, in some embodiments DVR 102 receives media signals from more than one media signal source. For example, in one such embodiment, DVR 102 receives signals from a CATV system as well as an over-the-air antenna.
Television 106 receives and emits signals from DVR 102 that represent the recorded (and unrecorded) media signals. For example, television 106 emits, among others, recorded audio and/or video signals. According to some embodiments, television 106 also displays any windows associated with a graphical user interface generated by DVR 102.
DVR 102 also includes a tuner system 204 for receiving and selecting one or more selected channels or streams of media content. For example, according to some instances, tuner system 204 can tune to a particular television channel or stream, and the media signals associated with this channel or stream are recorded by the DVR 102.
DVR 102 further includes at least one processor 206 for controlling the operations of the DVR 102 and an output system 208 for driving a playback device (e.g., television 106). An input system 210 receives user inputs provided via a wired or wireless input device such as, for example, a hand-held remote control, a transmitter with buttons or keys located on the exterior of the DVR, and/or a keyboard, among other potential input devices.
Network interface 212 transmits and/or receives data over a network such as a LAN, WAN, or the Internet. For example, data is transferred to/from another DVR, a media signal source, or a centralized server through network interface 212, among others. Memory 214, which can include volatile and/or non-volatile memory, stores one or more programmed software applications, routines, drivers, or other functional elements (herein broadly referred to as applications), which contain instructions that are executed by processor 206 under the direction of operating system 216. Input data used by an application is stored in memory 214 and read by processor 206 as needed during the course of the execution of the application. In some instances, this input data is data stored in memory 214 by a secondary application or other source, either internal or external to DVR 102. In other stances, data is created with the application at the time it was generated as a software application program. According to some embodiments, other logic is stored in memory 212 for operation of the DVR 102.
Internal storage 218 comprises a recordable medium and may be any of a number of devices available for non-volatile data storage, such as, among others, a hard disk drive (HDD), optical drive, or flash memory, for example. Although depicted as separate components, internal storage 218 and memory 214 are the same device in some embodiments. Among other uses, internal storage 218 is used for storing media content (i.e. in the form of media data) received through communication interface 202 and/or network interface 212. In some embodiments, before being stored on the recordable medium, the media content is digitally encoded by the DVR itself or by means external from the DVR, such as the media signal source or a cable set-top box. Media content is stored on the recordable medium in an encrypted or unencrypted state.
According to some embodiments, DVR 102 does not include an external device for storing media content and/or a communication interface for being communicatively coupled to such an external storage device. However, according to some embodiments, DVR 102 includes, or is otherwise configured for attachment to, external storage 220 over a communication interface. Like internal storage 218, external storage 220 also comprises a recordable medium for non-volatile data storage, such as, among others, a hard disk drive (HDD), optical drive, or flash memory, for example. However, unlike internal storage 218, which is located within the DVR enclosure (i.e., housing) 219, external storage 220 can be removably attached to DVR 102 through a communications interface 222. According to some embodiments, external storage 220 is located remotely from the DVR, such as in other rooms or locations within a house.
Although only one external storage medium is used in some embodiments, it is contemplated that other embodiments may comprise a plurality of external storage mediums 220a-220n. In some instances, for example, external storage mediums 220a-220n comprise a plurality of HDDs. It can be appreciated that the one or more HDDs can be combined to communicate with DVR 102 over one or more communication interfaces using a hub or other similar device. According to some embodiments, the external storage 220 is provided in a self-supporting, external housing. Some embodiments also include an integrated power supply for powering to the external storage and/or cooling devices, such as fans and/or heat dissipating devices.
According to some embodiments, communication interface 222 can be a high-speed communication bus, such as, among others, a bus operating under the Advanced Technology Attachment (ATA) standard, and more specifically, the Serial-ATA (i.e., SATA) standard version 2.5, which is available from the Serial ATA International Organization and is hereby incorporated by reference in its entirety. According to such an embodiment, DVR 102 includes a communications interface comprising an attachment port on the housing 219 of the DVR that cooperatively mates with the plug of external storage 220. A cable complying with the high-speed bus (i.e., a cable complying with the SATA standards, for example) provides the transmission medium between external storage 220 and DVR 102. It should be understood that other controllers for moving data across communications interface 222, that are not presently shown in
According to some embodiments, the communication interface 222 (and any related controllers and/or other circuitry) is a bus complying with wired infrastructure and protocols, such as, for example, the IEEE 1394 (Firewire) standard or the Universal Serial Bus (USB) standard, among others. However, in some instances, the communication interface 222 is a wireless medium. According to one such a wireless embodiment, the external storage device 220 communicates with DVR 102 using a wireless protocol such as the IEEE 802.11 protocol, among others.
Some embodiments of DVR 102 include a communications interface comprising a slot or port for readily removable media. The readily removable media is, for example, flash memory, an HDD, optical media, and/or magnetic media, among others.
User input received during the course of execution of any processes implemented by DVR 102 are received from an input device (not shown) via input system 210, transmitted through the bus 200, at least temporarily stored within memory 214, and communicated to processor 206. Data generated by an application is stored in memory 214 by processor 206 during the course of the execution of the application. Availability, location, and amount of data generated by one application for consumption by another application is communicated by messages through the services of operating system 224, among others. Hence, preferences for the operation of the DVR functions is input by, among others, a subscriber using a remote and/or remotely under the control of an entity other than the user (e.g., by a command or other configuration change transmitted from the cable head-end). Changes to decision-making logic associated with the applications described herein are made by, among others, a variety of mechanisms under software control.
A navigator application 226 provides a navigation framework for services provided by DVR 102. Navigator 226 registers for, and in some cases reserves, certain user inputs related to navigational keys such as channel increment/decrement, last channel, favorite channel, etc. Navigator 226 also provides users with television (or other programming) related menu options that correspond to DVR functions such as, for example, providing an interactive program guide, blocking a channel or a group of channels from being displayed in a channel menu, recording particular channels, playback of recorded shows, etc.
Under user instruction, DVR application 228 performs the general tasks of recording and/or playing back received media content. Among other functions, DVR application 228 manages media content and related information. For example, according to some embodiments, DVR application 228 determines when and to which device the media content and related information will be stored to respective available storage devices. As well, as communication with storage devices is established or broken (e.g., by, among other possibilities, attaching and detaching external storage devices to the DVR), DVR application 228 performs a number of tasks to ensure that respective information associated with media content stored to the storage devices is managed accordingly. These aspects of DVR application 228, and others, will be described in more detail below.
Applications, such as navigator 226 and DVR application 228, among others, utilize services provided by window manager 232 and/or other graphics utilities provided by operating system 224 to draw dialog boxes, menus, graphics, etc., for display on playback device 106. Window manager 232, which in one embodiment is part of operating system 224, contains functionality for allocating screen areas and managing screen use among the various applications. Accordingly, window manager 232 provides the user interface for the DVR.
The applications executed by DVR 102 comprise executable instructions for implementing logical functions. In some instances, the applications are embodied in any computer-readable medium for use by, or in connection with, an instruction execution system. Some embodiments of the instruction execution system are, for example, a computer-based system, a processor-containing system, or any other system capable of executing or interpreting instructions. In the context of this document, a “computer-readable medium” is any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
Some embodiments of the computer-readable medium are, for example, among others, an electronic, solid-state, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium, either internal to DVR 102 or externally connected to the DVR 102 via one or more communication ports or network interfaces. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a hard drive storage device (magnetic), a random access memory (RAM) (solid-state device), a read-only memory (ROM) (solid-state device), an erasable programmable read-only memory (EPROM or Flash memory) (multiple devices), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
As described in more detail below, DVR application 228 and/or other applications associated with DVR 102 can be used for facilitating the transfer of media content from a first digital media device to a second digital media device. For example, the first and second digital media devices could be, among other digital media devices, DVRs (i.e. DVR set-tops) configured according to the embodiment of DVR 102 depicted in
At block 302, instances of media content are recorded to a first storage medium associated with the first DVR. For example, a user may select an episode of the television show Smallville for recording, the DVR receives the episode of Smallville from media signal source 104 and stores the episode as an instance of media content on internal storage 218. Over time, the user may store several instances of media content to internal storage 218. The first DVR may also store catalog information related to the media content stored to the storage medium. The catalog information may include information about associated media content, such as guide information (i.e., title, actors, genre, program description, channel, time, etc.), recording date, and/or trip play information. The catalog information may also include logical rules for determining which of the media data stored to the storage device can be deleted at a particular opportunity.
At block 304, depending on the specific embodiment, either the first or second DVR may receive an indication that instances of media content are to be made available to the second DVR. Exemplary embodiments of this step will be described in later portions of this document.
At block 306, the instances of media content recorded to the first storage medium are provided to a second DVR. For example, the instances of media content can be provided to the second DVR over its communication interface 222, which could be a high-speed communication bus.
Now that a general overview of the concepts of an embodiment of a media content transfer process have been described,
Specifically,
According to some embodiments, the media content 406 that is stored to internal storage and/or transferred to storage medium 410 could be encrypted by the first DVR. Embodiments directed to enabling such encrypted media content to be decrypted by other media devices, such as a second DVR, will be described in portions of the detailed description below.
At block 704, first DVR 402 may receive an indication that the instances of media content recorded to the storage medium associated with the DVR 402 are to be made available to second DVR 412.
For example, according to some embodiments, the first DVR 402 may receive input from a user requesting that the instances of media content recorded to the storage medium associated with the DVR 402 be made available to second DVR 412. Such a user selection can be made, for example, through a remote control or other input device communicating to DVR 402 through input system 210 (
According to some embodiments, the indication that the instances of media content recorded to the storage medium associated with the first DVR 402 are to be made available to the second DVR 412 is an event triggered by the detection of a connection of the external storage 408 to the first DVR (i.e., as may be performed in block 706). That is, the attachment of external storage 408 to first DVR 402 can serve to automatically imply that the media content is to be copied from internal storage 404 to the storage medium 410 of external storage 408. Such an implication could also be conditional, based on whether the external storage includes files and/or logic, readable by the first DVR 402, that indicates that the storage is to be used for the purpose of transferring files.
According to yet another embodiment, the indication that the first DVR is to transfer media content to the external storage 408 could come from a remote server (i.e. from a cable-head end or other remote server in communication with the first DVR). Specifically, the remote server could send the indication, which could include instructions and/or other logic, for performing the transfer process. Such an indication could be transmitted to the first DVR 402 at the request of a user. According to one embodiment, the service-provider's customer service representative or automated system (i.e. telephone response system and/or Internet server), could initiate such an indication. Although such indications could be received by a DVR at the user premises, according to some embodiments, a service provider staging or unit swap-out area (i.e. at the service provider's facility) can be provided for such service.
According to some embodiments, providing a DVR with the ability to transfer media content can be used as an income stream by the service provider. For example, the service provider can charge extra to initiate, or otherwise facilitate, the media transfer process and/or charge to use their facility to do so. Such an income stream can be enabled, in part, because the indication that the first DVR is to transfer media content can be authorized and/or entitled under the control the service provider (i.e. an MSO, etc.). Whether the invocation of the transfer is performed by a remote server or by the user, according to some embodiments, the service provider can provide the authorization to perform the transfer.
At block 706, external storage 408 is communicatively coupled to the first DVR 402. For example, the external storage 408 can be connected to the external port of the first DVR that is associated with the communication interface 222. At block 708, the instances of media content are transferred to storage medium 410 associated with external storage 408. At block 710, the external storage 408 can be disassociated with first DVR. For example, the external storage 408 can be detached or otherwise removed from communication with the first DVR 402.
At block 712 external storage 408 can be communicatively coupled to the second DVR 412. For example, the external storage 408 can be attached to the external port of the second DVR 412 to provide communication over the communication interface 222. At block 714, according to some embodiments, access to the instances of media content stored to the second storage medium 410 of external storage 408 is provided to second DVR 412 over the communication interface 222 of the second DVR.
According to some embodiments, access to the media content may further include providing access to the media content using a key transfer scheme, transencryption scheme, password, remote authorization from a cable head end and/or other verification that ensures the media content is viewable by second DVR 412.
For example, according to some embodiments, access to the instances of media content 406 is provided to second DVR 412 using a key transfer scheme and/or a re-encryption process. For example, the instances of media content 406 may be initially encrypted by first DVR 402 using a content key for each instances of media content. According to some embodiments, these content keys are further encrypted by a secure element of the first DVR 402 with a second key and then stored to memory or non-volatile storage. Since the content keys are encrypted, other DVRs that do not have access to the second key are not able to decrypt the content keys in order to access the media content 406 for playback. Thus, if the instances of media content 406 are not useful for playback on second DVR 412 unless second DVR 412 is provided access.
Accordingly, in one embodiment, content keys can be provided from the first DVR 402 to the second DVR 412 by re-encrypting the content keys using an encryption key that is capable of being decrypted by the second DVR set top. For example, the first DVR 402 can be configured to decrypt the content keys associated with instances of media content stored to internal storage 404. The content keys associated with the instances of media content can then be encrypted by the first DVR 402 into encrypted content keys that are capable of being decrypted by the second DVR 412. For example, among other possibilities, the first DVR 402 could encrypt the content keys with a public key of a secure element of the second DVR 412. The encrypted content keys can then be transferred and stored to the second storage medium 410 associated with external storage 408. For example, when media content 406 is transferred to storage medium 410, the re-encrypted content keys can be transferred to storage medium 410 as well. Once external storage 408 is communicatively coupled to second DVR 412, the second DVR 412 accesses the re-encrypted content keys and decrypts them. For example, second DVR 412 can decrypt them with its private key, which could be stored securely within a secure element of second DVR 412. Accordingly, the content keys can then be accessed in order to decrypt the associated media content 406.
According to yet another example of providing access to the media content stored to the second storage medium 410, the encrypted content keys, as encrypted by first DVR 402, can be stored to storage medium 410 along with the instances of media content 406. A key capable of decrypting the encrypted content keys can then be provided to second DVR 412. Once the external storage 408 is placed in communication with second DVR 412, the second DVR 412 can decrypt the encrypted content keys associated with the media content using the key provided to second DVR 412. Finally, the media content 406 can be decrypted with the content keys to provide access to the media content stored to the second storage medium. One skilled in the art will understand that other keying and/or trans-encryption schemes, among other access methods, could be used to access the media content.
At block 1104, the first storage medium (i.e. internal storage 804) is removed from the housing of the first DVR 802. At block 1106 the first storage medium is associated with an external storage device, such as external storage 808. According to some embodiments, internal storage 804 is installed within the housing of external storage 808, for example.
At block 1108, the external storage 808 is communicatively coupled to the second DVR. Specifically, according to one embodiment, external storage 808 is coupled to an external port of second DVR 810 using communication interface 222.
At block 1110, an indication that the instances of media content are to be made available to the second DVR 810 is received. For example, a user selection can be received on the second DVR 810 (e.g through a graphical user interface) requesting that instances of media content be made available to the second DVR or an indication could be received from a remote server. In another embodiment, the attachment of external storage 808, containing a pre-formatted storage element containing the media content 806 causes the DVR 810 to automatically access the stored material. According to the latter embodiment, the process of making the first storage element available to the second DVR is initiated simply by attaching the external storage, and no specific user input is needed.
At block 1112, the second DVR 810 provides access to the instances of media content stored to the second storage medium over, in one embodiment, the communication bus 222 of the second DVR. According to some embodiments, such access is facilitated through using a key mechanism or trans-encryption scheme, among other possibilities, similar to that described above.
Specifically, according to one embodiment, first DVR 1202 is connected to second DVR 1208 over communication interface 222, which could be a high-speed communication bus. According to such an embodiment, the media content 1206 stored to internal storage 1204 can be transferred to internal storage 1210 of second DVR 1208 over communication interface 222.
Once the media content 1206 has been transferred to internal storage 1210, according to some embodiments, the media content 1206 is deleted from internal storage 1204. However, in other embodiments, media content 1206 can remain on internal storage 1204.
At block 1406, an indication can be received at either the first DVR or the second DVR that requests instances of media content are to be made available to the second DVR.
For example, as described in embodiments above, such indication could be from a user through a graphical user interface or received by either DVR from a remote server. In some embodiments, the attachment of the first DVR 1202 to the second DVR 1208 triggers an event that provides the indication that the media content is to be made available to the second DVR. That is, the attachment of first DVR 1202 to second DVR 1208 can serve to automatically imply that the media content is to be copied from internal storage 1204 to internal storage 1210 of second DVR 1208.
At block 1408, access is provided to the instances of media content stored to internal storage 1204. According to some embodiments, such access is facilitated through using a key mechanism or trans-encryption scheme similar to that described above. At block 1410, the instances of media content 1206 and/or other information, can be transferred from the internal storage 1204 to the internal storage 1210 of the second DVR over the communication interface 222.
Conditional language, such as, among others, “can,” “could,” “might”, or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, steps, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the preferred embodiments of the systems and methods described herein in which steps or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5742677 | Pinder et al. | Apr 1998 | A |
5742686 | Finley | Apr 1998 | A |
5796829 | Newby et al. | Aug 1998 | A |
5856975 | Rostoker et al. | Jan 1999 | A |
5870474 | Wasilewski et al. | Feb 1999 | A |
5872846 | Ichikawa | Feb 1999 | A |
5905522 | Lawler | May 1999 | A |
5915068 | Levine | Jun 1999 | A |
5917822 | Lyles et al. | Jun 1999 | A |
5933503 | Schell et al. | Aug 1999 | A |
5940391 | Malkin et al. | Aug 1999 | A |
5943047 | Suzuki | Aug 1999 | A |
5961603 | Kunkel et al. | Oct 1999 | A |
5987572 | Weidner et al. | Nov 1999 | A |
5990881 | Inoue et al. | Nov 1999 | A |
5990927 | Hendricks et al. | Nov 1999 | A |
5999970 | Krisbergh et al. | Dec 1999 | A |
6005938 | Banker et al. | Dec 1999 | A |
6006257 | Slezak | Dec 1999 | A |
6020982 | Yamauchi et al. | Feb 2000 | A |
6035281 | Crosskey et al. | Mar 2000 | A |
6057872 | Candelore | May 2000 | A |
6088455 | Logan et al. | Jul 2000 | A |
6098056 | Rusnak et al. | Aug 2000 | A |
6105134 | Pinder et al. | Aug 2000 | A |
6108002 | Ishizaki | Aug 2000 | A |
6118976 | Arias et al. | Sep 2000 | A |
6157377 | Shah-Nazaroff et al. | Dec 2000 | A |
6157719 | Wasilewski et al. | Dec 2000 | A |
6173400 | Perlman et al. | Jan 2001 | B1 |
6185625 | Tso et al. | Feb 2001 | B1 |
6229895 | Son et al. | May 2001 | B1 |
6230269 | Spies et al. | May 2001 | B1 |
6246767 | Akins, III et al. | Jun 2001 | B1 |
6252964 | Wasilewski et al. | Jun 2001 | B1 |
6253375 | Gordon et al. | Jun 2001 | B1 |
6292568 | Akins, III et al. | Sep 2001 | B1 |
6305020 | Hoarty et al. | Oct 2001 | B1 |
6345307 | Booth | Feb 2002 | B1 |
6356971 | Katz et al. | Mar 2002 | B1 |
6366987 | Tzelnic et al. | Apr 2002 | B1 |
6378130 | Adams | Apr 2002 | B1 |
6401243 | Suzuki | Jun 2002 | B1 |
6424714 | Wasilewski et al. | Jul 2002 | B1 |
6424717 | Pinder et al. | Jul 2002 | B1 |
6459427 | Mao et al. | Oct 2002 | B1 |
6484318 | Shioda et al. | Nov 2002 | B1 |
6510519 | Wasilewski et al. | Jan 2003 | B2 |
6516412 | Wasilewski et al. | Feb 2003 | B2 |
6526508 | Akins, III et al. | Feb 2003 | B2 |
6532593 | Moroney | Mar 2003 | B1 |
6543053 | Li et al. | Apr 2003 | B1 |
6549577 | Florencio et al. | Apr 2003 | B2 |
6550008 | Zhang et al. | Apr 2003 | B1 |
6560340 | Akins, III et al. | May 2003 | B1 |
6574609 | Downs et al. | Jun 2003 | B1 |
6636953 | Yuasa et al. | Oct 2003 | B2 |
6727944 | Adachi | Apr 2004 | B1 |
6744892 | Akins, III et al. | Jun 2004 | B2 |
6748080 | Russ et al. | Jun 2004 | B2 |
6804357 | Ikonen et al. | Oct 2004 | B1 |
6937729 | Akins, III et al. | Aug 2005 | B2 |
6963972 | Chang et al. | Nov 2005 | B1 |
6971008 | Wasilewski et al. | Nov 2005 | B2 |
7062658 | Cheriton et al. | Jun 2006 | B1 |
7065216 | Benaloh et al. | Jun 2006 | B1 |
7089579 | Mao et al. | Aug 2006 | B1 |
7107416 | Stuart et al. | Sep 2006 | B2 |
7146388 | Stakutis et al. | Dec 2006 | B2 |
7155609 | Chan et al. | Dec 2006 | B2 |
7181010 | Russ et al. | Feb 2007 | B2 |
7200868 | Mattox et al. | Apr 2007 | B2 |
7212725 | Gunji et al. | May 2007 | B2 |
7233959 | Kanellos et al. | Jun 2007 | B2 |
7363326 | Margolus | Apr 2008 | B2 |
7505592 | Russ et al. | Mar 2009 | B2 |
7602913 | Wasilewski | Oct 2009 | B2 |
7602914 | Wasilewski | Oct 2009 | B2 |
7630499 | Wasilewski | Dec 2009 | B2 |
7650442 | Ashley et al. | Jan 2010 | B2 |
7860250 | Russ et al. | Dec 2010 | B2 |
7861082 | Pinder et al. | Dec 2010 | B2 |
20010006400 | Kubo et al. | Jul 2001 | A1 |
20010049824 | Baker et al. | Dec 2001 | A1 |
20020013772 | Peinado | Jan 2002 | A1 |
20020018130 | Suemoto et al. | Feb 2002 | A1 |
20020026582 | Futamura et al. | Feb 2002 | A1 |
20020044658 | Wasilewski et al. | Apr 2002 | A1 |
20020094084 | Wasilewski et al. | Jul 2002 | A1 |
20020099663 | Yoshino et al. | Jul 2002 | A1 |
20020116708 | Morris et al. | Aug 2002 | A1 |
20020144067 | Jeong | Oct 2002 | A1 |
20020146237 | Safadi | Oct 2002 | A1 |
20020184457 | Yuasa et al. | Dec 2002 | A1 |
20020199190 | Su | Dec 2002 | A1 |
20030005446 | Jaff et al. | Jan 2003 | A1 |
20030005454 | Rodriguez et al. | Jan 2003 | A1 |
20030009668 | Chan | Jan 2003 | A1 |
20030028890 | Swart | Feb 2003 | A1 |
20030093680 | Astley et al. | May 2003 | A1 |
20030110234 | Egli et al. | Jun 2003 | A1 |
20030161617 | Um et al. | Aug 2003 | A1 |
20030188164 | Okimoto et al. | Oct 2003 | A1 |
20030200337 | Jabri et al. | Oct 2003 | A1 |
20040039911 | Oka et al. | Feb 2004 | A1 |
20040045030 | Reynolds et al. | Mar 2004 | A1 |
20040052377 | Mattox et al. | Mar 2004 | A1 |
20040068739 | Russ et al. | Apr 2004 | A1 |
20040117831 | Ellis et al. | Jun 2004 | A1 |
20040128499 | Peterka et al. | Jul 2004 | A1 |
20040187014 | Molaro | Sep 2004 | A1 |
20040193921 | Byrne | Sep 2004 | A1 |
20040236804 | Bots et al. | Nov 2004 | A1 |
20040237100 | Pinder | Nov 2004 | A1 |
20050076066 | Stakutis et al. | Apr 2005 | A1 |
20050080497 | Rao | Apr 2005 | A1 |
20050091173 | Alve | Apr 2005 | A1 |
20050100162 | Alve et al. | May 2005 | A1 |
20050102513 | Alve | May 2005 | A1 |
20050111835 | Friel et al. | May 2005 | A1 |
20050223414 | Kenrich et al. | Oct 2005 | A1 |
20050232593 | Kanai | Oct 2005 | A1 |
20050237396 | Hagiwara et al. | Oct 2005 | A1 |
20050240708 | Shaver et al. | Oct 2005 | A1 |
20060013566 | Nakamura | Jan 2006 | A1 |
20060020786 | Helms et al. | Jan 2006 | A1 |
20060039256 | Nakamura et al. | Feb 2006 | A1 |
20060039559 | Wasilewski | Feb 2006 | A1 |
20060039560 | Wasilewski | Feb 2006 | A1 |
20060041905 | Wasilewski | Feb 2006 | A1 |
20060072752 | Nakano et al. | Apr 2006 | A1 |
20060074807 | Gauba et al. | Apr 2006 | A1 |
20060109854 | Cancel | May 2006 | A1 |
20060156382 | Motoyama | Jul 2006 | A1 |
20060179478 | Han et al. | Aug 2006 | A1 |
20060184733 | Yamamoto et al. | Aug 2006 | A1 |
20060200865 | Leake et al. | Sep 2006 | A1 |
20070055390 | Simon et al. | Mar 2007 | A1 |
20070130254 | Russ et al. | Jun 2007 | A1 |
20070277205 | Grannan | Nov 2007 | A1 |
20090089369 | Russ et al. | Apr 2009 | A1 |
Number | Date | Country |
---|---|---|
0 782 296 | Jul 1997 | EP |
1 014 715 | Jun 2000 | EP |
1 213 919 | Dec 2002 | EP |
2 779 599 | Dec 1999 | FR |
2 403 586 | Jan 2005 | GB |
10-2003-0037098 | May 2003 | KR |
10-2004-0062662 | Jul 2004 | KR |
WO 0011840 | Mar 2000 | WO |
WO 0051041 | Aug 2000 | WO |
WO 0118807 | Mar 2001 | WO |
WO 0175876 | Oct 2001 | WO |
WO 0182588 | Nov 2001 | WO |
WO 02097997 | Dec 2002 | WO |
WO 2004098190 | Nov 2004 | WO |
WO 2005029843 | Mar 2005 | WO |
WO 2005029852 | Mar 2005 | WO |
WO 2005091626 | Sep 2005 | WO |
WO 2005101411 | Oct 2005 | WO |
WO 2006038204 | Apr 2006 | WO |
2006066052 | Jun 2006 | WO |
WO 2008005699 | Jan 2008 | WO |
WO 2008005700 | Jan 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20080002951 A1 | Jan 2008 | US |