The present disclosure pertains to mixing digital data and, more particularly, to methods and apparatus for mixing encrypted data with unencrypted data.
The importance of digital audio content protection has increased significantly in recent years, particularly in the personal computing domain. For example, distributors of audio compact discs (CDs), artists creating the audio content, and software companies are concerned about the unauthorized copying of copyrighted digital audio content. Personal computer users wishing to capture and distribute copyrighted digital audio content can use a software application to capture raw digital audio data as it travels through the audio layers of an operating system to the hardware associated with the playback of the audio content.
One known method of preventing the copying of the copyrighted digital audio content encrypts a stream of digital audio data (i.e., an audio stream) at the source (e.g., an audio player application such as Windows Media Player™) and decrypts the audio stream at the destination (e.g., the hardware used to playback the audio and/or a software driver). This method is suitable if the encrypted audio content is not manipulated or mixed with any other audio source(s) as it travels from the source to the destination. However, if another sound (e.g., a system sound or any other unencrypted media source) is played back simultaneously, the operating system audio mixer will attempt to mix the encrypted audio stream with the unencrypted audio stream, rendering the resulting audio stream unintelligible at the destination.
Another known method of preventing copying of digital audio content encrypts the audio content at the source and decrypts the audio content at the operating system audio mixer before mixing in the second audio source. This method requires a significant amount of computational power because the audio content must be decrypted before any processing is performed on the encrypted audio content and, as a result, may cause noticeable delays in audio playback. Also, this method is not secure because each software component in the operating system audio layer is required to be aware of the encryption and the encryption key.
Although the following discloses example systems, including software or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware or in some combination of hardware, firmware and/or software. Accordingly, while the following describes example systems, persons of ordinary skill in the art will readily appreciate that the examples are not the only way to implement such systems.
The CD player application 102 may be any software application configured to receive CD audio data from a CD drive 620 (
The OS multimedia component 104 is configured to receive the PCM data from the CD player application 102 and also provides the interface between the CD player application 102 and the OS audio layers 106. The OS multimedia component 104 may be a plurality of software instructions used to, but not limited to, transfer digital audio data to audio buffers and/or audio stacks within the OS and/or scale the gain applied to the audio data.
The OS audio layers 106 are configured to process audio sources, including the PCM data, system sounds, and/or sounds generated by other applications. The OS audio layers 106 may process audio sources (e.g., audio streams) by mixing audio sources together, filtering the audio sources, and/or conveying the audio sources to the hardware driver 108. A person of ordinary skill in the art will readily appreciate that the OS audio layers 106 are not limited to the above-described functionality.
The audio data paths 110, 112, 114, 116, and 118 are used to convey the digital audio data or audio streams to the blocks of the example prior art system 100. The audio data paths 110, 112, 114, 116, and 118 may be any combination of an input/output bus, a data bus, a wire, a cable, a memory location, or any other device used to transport data. The audio data paths 110, 112, 114, 116, and 118 are example points at which copyrighted audio content is vulnerable to copying, either in a digital form or an analog form. For example, a software application may attempt to access the data directly from the CD drive 620 or a software application may intercept the PCM data from the CD player application 102. A person of ordinary skill in the art will readily appreciate that there are additional points at which the copyrighted audio content may be copied and that the audio data paths 110, 112, 114, 116, and 118 are merely example points.
The first media source 202 may provide an unencrypted audio source including a stream of digital data samples. Each digital data sample has a predetermined size (e.g., a number or a maximum number of bits used to represent the sample). Example digital data samples include 8 bits, 16 bits, 20 bits, and 24 bits. The first media source 202 may provide, but is not limited to providing, audio content from a CD and/or digital versatile disc audio (DVD-A). In addition, the first media source 202 may provide copyrighted digital media but is not restricted to providing copyrighted digital media. In one example, the first media source 202 provides digital content in a raw digital format and/or digital content in the form of a PCM signal.
The second media source 204 may be configured to provide digital audio content in a manner similar to that of the first media source 202. The second media source 204 also includes a stream of unencrypted digital data samples where each sample has the same size or data width as a sample from the first media source 202. An example second media source 204 is a sound generated by an operating system (e.g., a tone) to indicate an error and/or sounds generated by a software application that is not concerned about protecting its audio content from copying.
The symmetric key stream generator 205 is configured to generate the symmetric key stream 206. The symmetric key stream generator 205 may use a key stream block cipher algorithm to generate the symmetric key stream 206. The key stream block cipher algorithm is well known to those of ordinary skill in the art and, thus, is not described in greater detail. The symmetric key stream generator 205 may use an encryption key known by the encryption module 208 and the hardware driver 212 to generate the symmetric key stream 206. Each key in the symmetric key stream 206 is of the same size or data width as the digital data samples associated with the first and second media sources 202 and 204. An example symmetric key stream 206 is a key stream produced by the symmetric key stream generator 205 using the well-known RC4 stream cipher algorithm. A person of ordinary skill in the art will readily appreciate that there are various other methods that may be used to generate the symmetric key stream 206.
The encryption module 208 is configured to receive unencrypted digital data from the first media source 202 and a symmetric key stream 206 and to encrypt the digital data (e.g., digital audio data) received from the first media source 202 using any known symmetric key stream encryption algorithm such as Triple Data Encryption Standard (DES). Symmetric key stream encryption algorithms are well known to those of ordinary skill in the art and, thus, are not described in further detail. In addition to encrypting digital data from the first media source 202, the encryption module 208 may also be configured to separate the encrypted data into at least two encrypted data streams or sources. If so, the encrypted data stream is separated so that the sum of the encrypted data streams (e.g., encrypted audio streams) is equal to the digital data stream provided by the encrypted digital content received from the first media source 202. The encryption module 208 may also be further configured to determine the least significant bit (LSB) of data provided by a media source such as, for example, an audio source.
The mixer 210 is configured to receive data from at least one encrypted media source (e.g., encrypted audio data) and an unencrypted media source (e.g., unencrypted audio data) and combine the data received from the media sources into a mixed media data stream. The mixer 210 is configured to combine the encrypted data (e.g., audio data) with unencrypted data (e.g., audio data) without knowledge of the encryption key used by the encryption module 208. The mixer 210 may combine the encrypted and the unencrypted data by calculating an average or by combining the data using some other statistical or mathematical method. In addition, the mixer 210 may also be configured to determine the LSB of data received from a media source, such as data received from the unencrypted media source 204.
The hardware driver 212 is configured to receive the mixed media data stream and decrypt the mixed media data stream using the encryption key used by the encryption module 208. The hardware driver 212 may decrypt the mixed media data stream (e.g., mixed audio) using a decryption algorithm that is complimentary to the encryption algorithm used by the encryption module 208 or may use some other decryption algorithm that is compatible with the encryption algorithm employed by the encryption module 208. The hardware driver 212 may also be configured to process the decrypted data by normalizing the decrypted data and/or correcting overflow of the decrypted data. The decrypted data (e.g., mixed audio data) is transmitted to the hardware associated with one or both of the media sources 202 and 204. Example hardware associated with one or both of the media sources 202 and 204 includes a soundcard or a device configured to generate sounds.
In general, the example process 300 receives data from the first media source 202 and the symmetric key stream 206. The encryption module 208 is configured to encrypt the data from the first media source 202 using the symmetric key stream 206 and to separate the encrypted data into a plurality (e.g., two) of encrypted data streams. The encrypted media data is separated so that the sum of the data from the encrypted data streams is equal to the encrypted data from the first media source 202. The encrypted data is transmitted to the mixer 210, which also receives unencrypted data from the second media source 204. The mixer 210 combines the encrypted data with the unencrypted data and transmits the mixed data to a hardware driver 212. The hardware driver 212 decrypts the mixed data and outputs the decrypted data (e.g., audio data) to a soundcard or other similar device.
Now turning in detail to
The encryption module 208 also receives a symmetric key stream 206 from the symmetric key stream generator 205 (block 304). For ease of discussion, the symmetric key stream 206 is represented as k=k1, k2, k3 . . . , where k is the symmetric key stream 206 and k1, k2, and k3 represent the first, second, and third keys in the symmetric key stream 206, respectively. Each key in the symmetric key stream 206 is the same size (i.e., has the same width or number of bits) as the samples or data received from the first media source 202 (e.g., n bits). The symmetric key stream generator 205 may generate the symmetric key stream 206 using a key stream block cipher algorithm. Example key stream cipher algorithms are well known to those of ordinary skill in the art.
The encryption module 208 uses the symmetric key stream 206 to encrypt the audio data from the first media source 202 to form an encrypted audio data stream e (block 306). The encrypted audio data stream e may be represented as e=e1, e2, e3 . . . , where e1, e2, and e3 represent the first, second, and third samples or data portions associated with the encrypted audio data stream e, respectively. An example implementation of the encryption algorithm used at block 306 may be similar to Equation 1 shown below.
e1=a1+k1, e2=a2+k2, . . . Equation 1
As shown above in Equation 1, a sample of the encrypted audio data stream e (e.g., e1) is calculated or determined by adding a sample of the audio data from the first media source 202 (e.g., a1) and a key from the symmetric key stream 206 (e.g., k1). A person of ordinary skill in the art will readily appreciate that the encryption process is not limited to Equation 1 and, thus, Equation 1 is merely an example.
After the audio data from the first media source 202 has been encrypted (block 306), the encryption module 208 separates the encrypted audio data stream e, into an encrypted data stream x and an encrypted data stream y (block 308). The encrypted audio data stream e may be separated into the encrypted data stream x and the encrypted data stream y so that each sample of the two encrypted data streams x and y is equal to half the corresponding sample of the encrypted audio data stream e (e.g., xi=yi=ei/2). The encrypted audio data stream e is separated into the two encrypted audio data streams x and y to facilitate prevention of data overflow during the example process 300.
The encrypted audio data streams x and y are transmitted to the mixer 210 (block 310). The mixer 210 also receives audio data from the second media source 204 (block 312). For ease of discussion, the audio data received from the second media source 204 will be represented as b=b1, b2, b3 . . . , where b is associated with the second media source 204 and b1, b2, and b3 represent the first, second and third samples or data portions received from the second media source 204, respectively. The samples or audio data received from the second media source 204, as well as the audio data received from the first media source 202 and the symmetric key stream 206, are n bits wide. The second media source 204 may provide unencrypted audio data associated with a system sound or some other sound that is generated by a software application.
After the encrypted audio data streams x and y and the unencrypted audio data from the second media source 204 are received by the mixer 210 (block 312), the mixer 210 combines the received audio data to form a mixed audio data stream m (block 314). The mixer 210 combines the received audio data without decrypting the encrypted audio data streams x and y and without knowledge of the encryption key used by the encryption module 208. The encrypted audio data streams x and y and the unencrypted audio data from the second media source 204 may be combined using Equation 2 shown below.
As shown above in Equation 2, a sample of the mixed audio data stream (e.g., m1) may be formed by calculating an average of data values from each of the two encrypted audio data streams x and y (e.g., x1 and y1) and audio data from the second media source 204 (e.g., b1). However, a person of ordinary skill in the art will readily appreciate that the manner in which the encrypted audio data associated with the data streams x and y may be mixed or combined with the unencrypted audio associated with the audio data (e.g., b1, b2, . . . ) from the second media source 204 is not limited to Equation 2.
After the mixed audio data stream m is formed (block 314), the mixed audio data stream m is transmitted to the hardware driver 212. The hardware driver 212 receives the mixed audio data stream m and decrypts the mixed audio data stream m to form a decrypted audio data stream s (block 316). The hardware driver 212 is aware of the encryption key used by the encryption module 208 and is configured to decrypt the mixed audio data stream m. An example method to decrypt the mixed audio data stream m is to use Equation 3 shown below.
As shown above in Equation 3, a sample of the decrypted audio data stream s (e.g., s1) may be formed by subtracting one third of the key value
from a sample of the mixed audio data stream m (e.g., m1).
After the decrypted audio data stream s is formed (block 316), the hardware driver 212 normalizes the decrypted audio data stream s to form a final signal f (block 318). An example method of normalizing the decrypted audio data stream s is illustrated in Equation 4 below.
As shown above in Equation 4, a sample of the final signal f (e.g., f1) is normalized by multiplying a sample of the decrypted audio data stream s (e.g., s1) by three-halves. This is equivalent to adding a sample or data from the first media source 202 (e.g., a1) and a sample or data from the second media source 204 (e.g., b1) and then dividing the sum by 2. The final signal f is then transmitted to hardware associated with the media source.
A second example process 400 by which the system of
Blocks 402 and 404 of the example process 400 of
Equation 5 as shown above is similar to Equation 1, but the samples or audio data from the first media source 202 (e.g., a1) and the keys from the symmetric key stream 206 (e.g., k) are divided by 2. A person of ordinary skill in the art will readily appreciate that other implementations exist and that Equation 5 is merely an example.
After the encrypted audio data stream e is formed (block 406), the encrypted audio data stream e is transmitted to the mixer 210 (block 408). The mixer 210 also receives unencrypted audio data from the second media source 204 (block 410) as described above. The mixer 210 mixes the encrypted audio data stream e and the audio data from the second media source 204 to form a mixed audio data stream m (block 412). As in the example process 300, the mixer 210 forms the mixed audio data stream m (block 412) without decrypting the encrypted audio data stream e and without knowledge of the encryption key used by the encryption module 208. The encrypted audio data stream e and the unencrypted audio from the second media source 204 may be combined or mixed by using Equation 6 shown below.
As shown above in Equation 6, a first sample of the mixed audio data stream (e.g., m1) is formed by calculating an average of the encrypted audio data stream e (e.g., e1) and a sample of the audio data from the second media source 204 divided by 2
Of course, a person of ordinary skill in the art will readily appreciate that mixing the data streams associated with the media sources 202 and 204 is not limited to Equation 6 and that other implementations exist.
After the mixed audio data stream m is formed (block 412), the mixed audio data stream m is transmitted to a hardware driver 212. The hardware driver 212 receives the mixed audio data stream m and decrypts the mixed audio data stream m to form a decrypted audio data stream s (block 414). Similar to process 300, the hardware driver 212 is aware of the encryption key used by the encryption module 208 and is configured to decrypt the mixed audio data stream m. An example method to decrypt the mixed audio data stream m is to use Equation 7 shown below.
As shown above in Equation 7, the decryption process is similar to the decryption process in Equation 3. Instead of dividing the key value by 3 as in Equation 3
the key value is divided by 4
because the key value was divided by 2 in Equations 5 and 6.
After the decrypted audio data stream s is formed (block 414), the hardware driver 212 normalizes the decrypted audio data stream s to form a final signal f (block 416). An example method to normalize the decrypted audio data stream s is to use Equation 8 below.
As shown above in Equation 8, a sample of the final signal f (e.g., f1) is normalized by multiplying a sample of the decrypted audio data stream s (e.g., s1) by 2. This is equivalent to adding a sample or data from the first media source 202 (e.g., a1) and a sample or data from the second media source 204 (e.g., b1) and then dividing the sum by 2. The final signal f is transmitted to hardware associated with one or both of the audio data streams 202 and 204 as in the case with the example process 300.
A third example process 500 by which the system of
(block 506). The first scaled audio data stream a′ may be used to prevent overflow errors in the encryption process. The mixer 210 analyzes the first scaled audio data stream a′ to find samples or data equal to a predetermined maximum value (e.g., 2n−1−1, where n is the bit depth or width of the sample) (block 506). If a sample is equal to the predetermined maximum value (e.g., a1′=2n−1−1), the encryption module 208 may subtract a number from the sample, such as 1 (e.g., a1′=a1′−1), to prevent a sample from the first scaled audio data stream a′ to facilitate the encryption process of Equation 9 below.
After the audio data received from the first media source 202 is scaled, the encryption module 208 uses the symmetric key stream 206 to encrypt the scaled audio data stream a1′ to form the encrypted audio data stream e (block 508). However, Equation 1 shown above is not used to encrypt the audio data received from the first media source 202 (e.g., block 306) and the encrypted audio data stream e is not separated into encrypted audio data streams x and y (e.g., block 308). Instead, the audio data received from the first media source 202 may be encrypted using an equation similar to Equation 9 below (block 508).
e1=(a1′+k1)mod(2n−1−1), e2=(a2′+k1)mod(2n−1−1), . . . Equation 9
As shown above in Equation 9, a sample of the encrypted audio data stream e (e.g., e1) is calculated by adding a sample or data from the first scaled audio data stream a′ (e.g., a1′) and the key of the symmetric key stream 206 (e.g., k1) and performing a modulo operation with a divisor equal to 2n−1−1. The encrypted audio data stream e may also be scaled. For example, each sample may be scaled by 2 (e.g., e1=2*e1).
After the encrypted audio data stream e is generated (block 508), a least significant bit (LSB) of the each sample of the scaled audio data stream a′ is determined (e.g., LSB(a1′)) (block 510). A person of ordinary skill in the art will readily appreciate that there are many methods to determine the LSB of each sample of the scaled audio data stream a′. For example, a logical AND operation may be used to determine the value of the last bit of the sample (e.g., LSB(a1′)=a1′ AND 1). The encryption module 208 transmits the LSB of the first scaled audio data stream a′ and the encrypted audio data stream e to the mixer 210.
The mixer 210 receives audio data from the second media source 204 (block 512). The mixer 210 scales the audio data received from the second media source 204 in a manner similar to the manner in which the encryption module 208 scaled the audio data received from the first media source 202 to form a second scaled audio data stream b′
(block 514). The mixer 210 also computes the LSB of the samples of the second scaled audio data stream b′ (block 514). The LSB of the second scaled audio data stream b′ may be determined in a manner similar to the manner in which the encryption module 208 determines the LSB of the first scaled audio data stream a′.
After the audio data received from the second media source 204 is scaled and the LSB of the second scaled audio data stream b′ is determined (block 514), the encrypted audio data stream e and the second scaled audio data stream b′ are combined (block 516). The encrypted audio data stream e may be multiplied by a predetermined number before the encrypted audio data stream e is combined with the second scaled audio data stream b′ (block 516). For example, if the first scaled audio data stream a′ was divided by 2 in block 506, the encrypted audio data stream e is multiplied by 2 in block 516. The mixer 210 may combine the encrypted audio data stream e with the second scaled audio data stream b′ by using Equation 10 below or an equation similar to Equation 10.
m1=e1+b1′, m2=e2+b2′, . . . Equation 10
As shown above in Equation 10, a sample of the mixed audio data stream m (e.g., m1) is calculated by adding a sample of the encrypted audio data stream (e.g., e1) and a sample of the scaled second audio data stream (e.g., b1′).
The mixer 210 then determines the LSB of the final signal f (block 518). The LSB of the final signal f may be determined by applying an XOR (exclusive OR) operation to each sample of the LSB of the first scaled audio data stream and the LSB of the second scaled audio data stream (e.g., LSB(a1′) XOR LSB(b1′)) (block 518). The mixed audio data stream m and the LSB of the final signal f are then transmitted to the hardware driver 212 (block 520).
The hardware driver 212 receives the mixed audio data stream m and the LSB of the final signal f (block 520). The hardware driver 212 decrypts the mixed audio data stream m to form the decrypted audio data stream s by using Equation 11 below.
s1=(m1−k1)mod(2n−1−1), s2=(m2−k2)mod(2n−1−1), . . . Equation 11
After the decrypted audio data stream s is generated, the hardware driver 212 corrects the decrypted audio data stream s for overflow errors to create the final signal f (block 524). Overflow errors in each sample of the final signal f may be corrected by using the determined LSB of the final signal f and the LSB of the decrypted audio data stream s. For example, if the LSB(s1) is equal to LSB(f1), then the sample of the final signal f is equal to the sample of the decrypted audio data stream s. Otherwise, the sample of the final signal f is equal to the sample of the decrypted audio data stream s added to the predetermined maximum value (e.g., f1=s1+2n−−1).
The processor 606 may be any type of processor, such as a processor from the Intel Pentium® family of microprocessors, the Intel Itanium® family of microprocessors, the Intel Centirino® family of microprocessors, and/or the Intel XScale® family of microprocessors. In addition, the processor 606 may include any type of cache memory, such as static random access memory (SRAM). The main memory device 610 may include dynamic random access memory (DRAM) and/or any other form of random access memory. For example, the main memory device 610 may include double data rate random access memory (DDRAM). The main memory device 610 may also include non-volatile memory. In an example, the main memory device 610 stores a software program which is executed by the processor 606. The flash memory device 612 may be any type of flash memory device. The flash memory device 612 may store firmware used to boot the computer system 600.
The interface circuit(s) 614 may be implemented using any type of interface standard, such as an Ethernet interface and/or a Universal Serial Bus (USB) interface. One or more input devices 616 may be connected to the interface circuits 614 for entering data and commands into the main processing unit 602. For example, an input device 616 may be a keyboard, mouse, touch screen, track pad, track ball, isopoint, and/or a voice recognition system.
One or more displays, printers, speakers, and/or other output devices 618 may also be connected to the main processing unit 602 via one or more of the interface circuits 614. The display 618 may be a cathode ray tube (CRT), a liquid crystal display (LCD), or any other type of display. The display 618 may generate visual indications of data generated during operation of the main processing unit 602. The visual indications may include prompts for human operator input, calculated values, detected data, etc.
The computer system 600 may also include one or more storage devices 620. For example, the computer system 600 may include one or more hard drives, a compact disk (CD) drive, a digital versatile disk drive (DVD), and/or other computer audio input/output (I/O) devices. In addition to the text strings stored in the flash memory device 612 (if any), one or more storage devices 620 (e.g., a hard disk) may store text strings in one or more languages.
The computer system 600 may also exchange data with other devices 622 via a connection to a network 624. The network connection may be any type of network connection, such as an Ethernet connection, digital subscriber line (DSL), telephone line, coaxial cable, etc. The network 624 may be any type of network, such as the Internet, a telephone network, a cable network, and/or a wireless network. The network devices 622 may be any type of network devices 622. For example, the network device 622 may be a client, a server, a hard drive, etc.
Although the above discloses example systems including, among other components, software executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the disclosed hardware and software components could be embodied exclusively in dedicated hardware, exclusively in software, exclusively in firmware or in some combination of hardware, firmware and/or software.
In addition, although certain methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all apparatus, methods and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.
Number | Name | Date | Kind |
---|---|---|---|
4591660 | Scordo | May 1986 | A |
4845749 | Brickell et al. | Jul 1989 | A |
4920565 | Strawczynski et al. | Apr 1990 | A |
5040138 | Maher, III | Aug 1991 | A |
5548648 | Yorke-Smith | Aug 1996 | A |
5751617 | Wong | May 1998 | A |
5768126 | Frederick | Jun 1998 | A |
5906880 | Chiba et al. | May 1999 | A |
5986588 | Kim | Nov 1999 | A |
5995623 | Kawano et al. | Nov 1999 | A |
6236727 | Ciacelli et al. | May 2001 | B1 |
6408076 | Bewick | Jun 2002 | B1 |
6690307 | Karczewicz | Feb 2004 | B2 |
6813355 | Hakaste | Nov 2004 | B1 |
6865747 | Mercier | Mar 2005 | B1 |
6931551 | Weng et al. | Aug 2005 | B2 |
7023991 | Nakamura et al. | Apr 2006 | B1 |
7027982 | Chen et al. | Apr 2006 | B2 |
7151831 | Candelore et al. | Dec 2006 | B2 |
7191342 | New et al. | Mar 2007 | B1 |
7194192 | Ko et al. | Mar 2007 | B2 |
7197768 | Cole et al. | Mar 2007 | B2 |
7242773 | Candelore | Jul 2007 | B2 |
7280956 | Cross et al. | Oct 2007 | B2 |
7286667 | Ryal | Oct 2007 | B1 |
7751556 | Sato et al. | Jul 2010 | B2 |
20020023120 | Gentric | Feb 2002 | A1 |
20020044655 | Applebaum | Apr 2002 | A1 |
20020049580 | Kutaragi et al. | Apr 2002 | A1 |
20020053030 | Weng et al. | May 2002 | A1 |
20020108049 | Xu et al. | Aug 2002 | A1 |
20020121999 | Akune et al. | Sep 2002 | A1 |
20020164017 | Wee et al. | Nov 2002 | A1 |
20020164018 | Wee et al. | Nov 2002 | A1 |
20020164153 | Tanaka et al. | Nov 2002 | A1 |
20030190054 | Troyansky et al. | Oct 2003 | A1 |
20040028227 | Yu | Feb 2004 | A1 |
20040049688 | Candelore et al. | Mar 2004 | A1 |
20040073917 | Pedlow et al. | Apr 2004 | A1 |
20050094808 | Pedlow et al. | May 2005 | A1 |
20050135618 | Aslam et al. | Jun 2005 | A1 |
20050141713 | Genevois | Jun 2005 | A1 |
20050259813 | Wasilewski et al. | Nov 2005 | A1 |
Number | Date | Country | |
---|---|---|---|
20050135618 A1 | Jun 2005 | US |