Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20030028664 A1
Publication typeApplication
Application numberUS 09/920,919
Publication dateFeb 6, 2003
Filing dateAug 2, 2001
Priority dateAug 2, 2001
Also published asUS8055769, US8078725, US20080092220, US20080092221, US20080098223
Publication number09920919, 920919, US 2003/0028664 A1, US 2003/028664 A1, US 20030028664 A1, US 20030028664A1, US 2003028664 A1, US 2003028664A1, US-A1-20030028664, US-A1-2003028664, US2003/0028664A1, US2003/028664A1, US20030028664 A1, US20030028664A1, US2003028664 A1, US2003028664A1
InventorsKaijun Tan, Michael Cochran, Logan Badia
Original AssigneeKaijun Tan, Cochran Michael Lloyd, Logan Badia
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Method and system for secure distribution and utilization of data over a network
US 20030028664 A1
Abstract
A method and system for the secure distribution and utilization of data over a network. A server computer may issue a certificate and a private key to a client for identifying the client in a transaction. The certificate and the private key may be stored in a token used by the client during a transaction. The server may verify a digital signature using the certificate stored in the token before distributing data to the client. The server may also generate a message associated with the data being downloaded to the client and associated with the token used by the client during a transaction.
Images(8)
Previous page
Next page
Claims(32)
What is claimed is:
1. A method for distributing data over a network comprising:
issuing a certificate and a private key to a client for identifying the client in a transaction;
storing the certificate and the private key in a token used by the client during a transaction;
verifying a digital signature using the certificate stored in the token before distributing data to the client;
generating a message associated with the data being downloaded to the client and associated with the token used by the client during a transaction; and
distributing the data and the associated message to the client.
2. The method of claim 1, further comprising providing the client with information necessary for establishing an account.
3. The method of claim 2, further comprising providing the client with the token.
4. A method for distributing data over a network comprising:
establishing a secure connection between a client and a server;
issuing a certificate and a private key to the client for identifying the client in a transaction; and
storing the certificate and the private key in a token used by the client during a transaction.
5. The method of claim 4, further comprising distributing data to the client.
6. The method of claim 5, further comprising requesting information from the client for establishing an account.
7. The method of claim 4, wherein establishing a secure connection comprises establishing a secure connection using a security protocol.
8. The method of claim 7, wherein the security protocol is the secure socket layer protocol.
9. The method of claim 6, wherein requesting information comprises requesting a credit card number.
10. The method of claim 6, wherein requesting information comprises requesting a password.
11. The method of claim 4, wherein storing the certificate comprises:
interfacing the token to a client computer; and
writing the certificate and the private key to the token across the network.
12. The method of claim 4, wherein storing the certificate comprises:
interfacing the token to a server computer; and
writing the certificate to the token at the server computer.
13. The method of claim 5, wherein distributing data to the client comprises distributing a media player.
14. A method for distributing data over a network comprising:
establishing a secure connection between a client and a server;
receiving a request from the client for data to be downloaded;
generating a message associated with the data being downloaded to the client and associated with a token used by the client; and
distributing the data and the associated message to the client.
15. The method of claim 14, wherein establishing a secure connection comprises establishing a secure connection using a security protocol.
16. The method of claim 15, wherein the security protocol is the secure socket layer protocol.
17. The method of claim 14, wherein establishing a secure connection comprises
requesting authentication information from the client; and
sending authentication information from the server.
18. The method of claim 17, wherein requesting authentication information from the client comprises
requesting a certificate from the client; and
requesting a digital signature from the client.
19. The method of claim 17, wherein sending authentication information from the server comprises
sending a certificate from the server; and
sending a digital signature from the server.
20. The method of claim 18, wherein requesting a certificate comprises reading the certificate from the token used by the client.
21. The method of claim 14, wherein generating a message further comprises:
including in the message a data identification number;
including in the message a period of time for which the data may be used by the client;
including in the message a distinguishing number of the token used by the client when requesting data;
including in the message a symmetrical key used to encrypt the data when distributing data from the server to the client over the network.
22. The method of claim 14, wherein generating a message further comprises generating a message using a public key (asymmetric) cryptographic algorithm.
23. A method of securely utilizing downloaded data comprising:
opening a media player;
opening a data file;
requesting a token from a client;
reading a distinguishing number from the token;
verifying a digital message associated with the data file and the token using the media player, the distinguishing number, and a private key in the token.
24. The method of claim 23, wherein in verifying a digital message, the media player reads the private key from the token to decrypt the digital message.
25. The method of claim 23, wherein in verifying a digital message, the media player sends the digital message to the token.
26. The method of claim 25, wherein the token decrypts an encrypted symmetric key using the private key.
27. The method of claim 22, wherein verifying a digital message comprises
verifying the distinguishing number read from the token;
verifying a time period associated with the data file;
decrypting an encrypted symmetrical key using the private key from the token;
decrypting the data file using the symmetrical key.
28. A system for distributing data over a network comprising:
a client computer for requesting data over a network, the client computer being interfaced to the network;
a server computer for distributing requested data over a network, the server computer being interfaced to the network; and
a token interfaced to the client computer,
wherein the server computer stores a certificate and a private key in the token.
29. The system of claim 28, wherein the server computer verifies an identity of the client with the certificate in the token before distributing data to the client.
30. The system of claim 28, further comprising
a firewall interfaced to the network; and
a cryptographic processor interfaced to the server computer and the firewall.
31. A system for distributing data over a network comprising:
a client computer for requesting data over a network, the client computer interfaced to the network;
a server computer for distributing requested data over a network, the server computer interfaced to the network;
a token interfaced to the client computer; and
a third party computer system interfaced to the network,
wherein the third party computer system issues a certificate and stores the certificate in the token.
32. The method of claim 31, wherein the third party computer system issues a private key and stores the private key in the token.
Description
    BACKGROUND
  • [0001]
    1. Field of the Invention
  • [0002]
    The present invention relates to the field of data distribution and, in particular, to the secure distribution and utilization of data, such as, for example, confidential or proprietary documents or audio, video, multimedia or other entertainment content, over a network.
  • [0003]
    2. Description of Related Art
  • [0004]
    The ease with which data may be copied and distributed over public and private networks has been a major impediment to the widespread use of networks as a medium for the sale and distribution of data. In particular, the inability to prevent the illegal copying and/or distribution of copyrighted material or the pilfering of proprietary documents has thwarted the commercial use of networks as a viable sales and distribution channel.
  • [0005]
    In the area of entertainment content, copyright violations have been particularly egregious. The illegal copying and distribution of copyrighted material has gone virtually unchecked, with little recourse to the copyright owners. The recent decision of a federal court to issue an injunction shutting down the song-swapping web site NAPSTER is further indication that, up to the present time, little has be done to prevent illegal copying and distributing over public networks except to prevent use of the network for transmission of copyrighted material altogether. Thus, content owners are still not able to tap the massive markets that exist for online sale and distribution of audio, video, multimedia and other entertainment content.
  • [0006]
    In addition, the exchange of confidential or proprietary data over public networks such as the Internet, although being tremendously convenient and offering tremendous savings in time and money, has still not been fully embraced by businesses and other networking communities due to concerns over privacy and confidentiality. The ever-present threat of pilfering of such data has prompted many businesses and organizations to recommend that such data be exchanged by means other than an electronic network.
  • [0007]
    The security, privacy and confidentiality issues associated with data or content distribution over a network have been addressed by several techniques, all with limited success. For example, one of the first techniques to address the distribution of data and content over public networks involved encryption/decryption. In an effort to prevent unauthorized access to data being sent over a network, data may be encrypted in such a manner that it can be decrypted only by the recipient. While this technique may be effective to prevent hacking during transmission of the data, encryption/decryption techniques do nothing to prevent illegal copying and redistribution of the data once the data has been decrypted by the recipient.
  • [0008]
    Other techniques have sought to prevent illegal copying and distribution of data over networks by identifying the owner of the data within the data itself. For example, certain identifying data, commonly known as a “digital watermark” and deriving its name from a traditional watermark seen on checks and other documents, may be added to data so that the owner, creator, distributor or other interested party may be identified within the data. In addition, a digital watermark may communicate copyright information, such as the owner of the copyright to the data, when the data was first copyrighted, whom the recipient may contact in order to inquire about licensing rights, and the like.
  • [0009]
    Unfortunately, digital watermarking alone has been insufficient to prevent widespread illegal copying and distributing of copyrighted material. Many in the networking community simply ignore digital watermarks. Moreover, enforcement by copyright owners using digital watermarks alone is tremendously difficult. Even if an unscrupulous user of copyrighted material is aware of a digital watermark, the user can copy and redistribute the data hundreds and even thousands of times without knowledge by the copyright owner. There is little the copyright owner can do to prevent this.
  • [0010]
    One technique for monitoring the distribution of information that is accessible through a public network is disclosed in U.S. Pat. No. 5,889,860, Encryption System With Transaction Coded Decryption Key. According to the '860 patent, a client who has chosen to purchase online data, such as a song, enters payment information and is assigned a password that is specific to the client and the transaction. The password functions as a decryption key to enable use of the data by the client. Should the client improperly copy and redistribute the data and the decryption password, the copies can be traced back to the client based on client identifying information encoded in the password.
  • [0011]
    Although possibly effective for identifying clients who have copied and redistributed data, the technique of U.S. Pat. No. 5,889,860 offers no method of enforcement. Similar to the case of digital watermarking, many clients are unconcerned that information identifying them is passed along with the data to unauthorized third parties. As far as the copyright owner is concerned, it is tremendously difficult to determine that data is being copied and redistributed over a public network and, even if it were not difficult, the volume typically associated with the illegal copying and redistributing of popular data is so great that any practical attempts to enforce copyrights would currently be futile.
  • SUMMARY OF THE DISCLOSURE
  • [0012]
    Embodiments of the present invention relate to methods and systems for the secure distribution and utilization of data over a network. Methods according to embodiments of the present invention may include issuing a certificate and a private key to a client for identifying the client in a transaction. The certificate and private key may be stored in a token used by the client during the transaction. Before distributing data to the client, the client's identity may be verified using the certificate and a digital signature signed using the private key.
  • [0013]
    A message may be generated by a server and associated with the data being downloaded to the client and further associated with the token used by the client during the transaction. Once the client's identity has been verified and a message generated, data may be distributed to the client.
  • [0014]
    A client and a server may communicate over a secure network connection. Using the secure network connection, the server may issue the certificate and private key to the client. The secure network connection may use a secure socket layer protocol or other secure protocol. Prior to issuing a certificate and private key and storing them in the client's token, the server may ask the client to establish a password for the token. The server may also ask the client to establish a password for a client account.
  • [0015]
    The token may interface to the client's computer. The certificate and private key may be stored in the token by writing them to the token across the network. Alternatively, the certificate and private key may be stored in the token by writing them to the token at the server computer.
  • [0016]
    A client may request data to be distributed from a server. Prior to distributing the data, the server may request that the client send the server the client's certificate. The server may also request that the client send the server a digital signature. The server may also request a distinguishing number of the token. Once the server has verified the client's identity, the server may generate a message associated with the data and the token and distribute the data to the client over a network.
  • [0017]
    A system for distributing data over a network according to embodiments of the present invention may include a client computer for requesting data over a network, the client computer being interfaced to the network, a server computer for distributing requested data over a network, the server computer being interfaced to the network, and a token interfaced to the client computer. The server computer may store the certificate and private key in the token. Furthermore, the server computer may verify the identity of the client with the client's certificate in the token before distributing data to the client.
  • [0018]
    A system for distributing data over a network according to embodiments of the present invention may further include a firewall interfaced to the network and a cryptographic processor interfaced to the server computer and the firewall.
  • [0019]
    According to embodiments of the present invention, a third party computer system may interface to the network. The third party computer system may issue a certificate and a private key and stores them in the token.
  • [0020]
    These and other objects, features, and advantages of embodiments of the invention will be apparent to those skilled in the art from the following detailed description of embodiments of the invention when read with the drawings and appended claims.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0021]
    [0021]FIG. 1 is a general system for the secure distribution and utilization of data over a network according to an embodiment of the present invention.
  • [0022]
    [0022]FIG. 2 is a flowchart of a general method for the secure distribution of data over a network according to an embodiment of the present invention.
  • [0023]
    [0023]FIG. 3 is a flowchart of a method for issuing a certificate and private key and storing them in a token according to an embodiment of the present invention.
  • [0024]
    [0024]FIG. 4 is a flowchart of a method for verifying the client's identity with the client's certificate, generating a message, and distributing data according to an embodiment of the present invention.
  • [0025]
    [0025]FIG. 5A is a flowchart of a method for utilizing data that has been downloaded to a client according to an embodiment of the present invention.
  • [0026]
    [0026]FIG. 5B is a flowchart of a method for verifying a digital message according to an embodiment of the present invention.
  • [0027]
    [0027]FIG. 6 is an alternative system for the secure distribution of data over a network according to an embodiment of the present invention.
  • [0028]
    [0028]FIG. 7 is an alternative system for the secure distribution of data over a network according to an embodiment of the present invention.
  • DETAILED DESCRIPTION
  • [0029]
    In the following description of preferred embodiments, reference is made to the accompanying drawings which form a part hereof, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the preferred embodiments of the present invention.
  • [0030]
    Embodiments of the invention are directed toward a method and system for the secure distribution and utilization of data over a network. Embodiments of the present invention allow data, including, without limitation, data in the form of entertainment content such as audio and video, to be distributed over a network to consumers, companies or other individuals or entities while reducing the risk that such data is subsequently copied illegally or redistributed without authorization. Embodiments of the invention may be implemented by individuals or large organizations. For example, embodiments of the invention may be implemented by entertainment content owners desirous of distributing music, movies, games, videos and other multimedia over networks such as the Internet.
  • [0031]
    Embodiments of the present invention may be implemented in a variety of ways. FIG. 1 shows a general system configuration on which embodiments of the present invention may be implemented. A client computer or other computing device 10 has a connection to a network 14. The client computer or other computing device 10 may contain, without limitation, a processor or processors, memory and other components as are common in the industry.
  • [0032]
    The network 14 may be a public network, a private network, or a combination thereof. For example, in a typical workplace environment, a client computer 10 may be connected via an Ethernet connection to a local area network (LAN), which, in turn, is connected to a larger public network, such as the Internet. Alternatively, if the client computer 10 is a stand alone PC in the client's home and the network 14 is the Internet, the client may connect to the network 14 through an Internet Service Provider (ISP) using a standard modem connection.
  • [0033]
    A server 16 also connects to the network 14 such that the client computer 10 and the server 16 may communicate with each other over the network 14. The server 16 may contain, without limitation, a processor or processors, memory and other components as are common in the industry.
  • [0034]
    Interfaced to the client computer or other computing device 10 is a token 12. The token may be a discreet piece of hardware that interfaces in some manner to the computer or other computing device 10. For example, the token 12 may be in the form of a smart card, a floppy disk, a CD-R, or a removable hard drive. Alternatively, the token may be an IKEY™ hardware token, made by RAINBOW TECHNOLOGIES, Irvine, Calif. In one embodiment of the invention, the information in the token is difficult for a general user to read. In addition, the token may be sealed within a security boundary, i.e., a physical boundary or border, outside of which it may be relatively easy to write information into the token but relatively difficult to read information from the token. Thus, the token may physically protect information, such as private keys, such that the information never exits the token. Cryptographic operations associated with protected keys may be performed within the token itself.
  • [0035]
    The token 12 may interface to the computer 10 in a variety of ways. For example, the token 12 may interface to the computer 10 via a cable. Alternatively, the token 12 may interface to the computer 10 via wireless link, such as, for example, an RF, optical or infrared link. If, for example, the token 12 is an IKEY™ hardware token, the token 12 may plug into a Universal Serial Bus (USB) port on the computer 10.
  • [0036]
    The token 12 may come in a variety of sizes and form factors. For example, if the token 12 is an IKEY™ hardware token, the token 12 may be small enough and lightweight enough to placed on a key ring or other type of key holder. The token may be kept and guarded by the client, much in the same way the client would keep and guard credit cards, house keys, car keys and other valuables.
  • [0037]
    [0037]FIG. 2 shows a generalized method for secure data distribution according to an embodiment of the present invention. At step 20, an individual, a company, a distributor or some other entity in control of data and intending to distribute the data in a secure manner issues a certificate and a private key to a client requesting the data. The certificate and private key are used to authenticate the client during a transaction in which the client requests data. The data may consist of confidential or proprietary documents or, alternatively, may be entertainment content, such as, for example, music, a movie, multimedia or some other type of audio or video content.
  • [0038]
    Once a certificate and private key has been issued to a client at step 20, they may be stored in a token used by the client at step 22. As stated previously, the token may be a discreet piece of hardware that interfaces in some manner to a computer or other computing device.
  • [0039]
    Once a certificate and private key identifying a client have been stored in the token at step 22, the client is then ready to download data. The client may download data during the session in which the client's certificate and private key was stored in the token or during another session at a later time. Whenever the client is ready to download data, the client's identity may be verified by a server operated by the individual, company, distributor, or other entity using the client's certificate before distributing data at step 24. For example, assume a client, at some time after receiving a certificate and private key, interfaces the token containing the certificate and private key to a computer and visits a music distribution company's web site. After perusing the music available for download, the client may request a download of a particular song in digital form. Prior to distributing the song to the client, the client's identity is authenticated with the client's certificate stored in the token, thereby ensuring that the downloading of data to the client is authorized.
  • [0040]
    Once the client's identity is verified with the certificate, at step 26 a message may be generated by the server which is associated with the data requested by the client and the token used by the client when making the request. As will be explained in greater detail below, the message, in conjunction with the token in which a certificate has been stored, may be used to prevent illegal copying, theft, and/or subsequent distribution of the data downloaded by the client.
  • [0041]
    After the message is generated at step 26, the encrypted data and the associated message are distributed to the client at step 28. The client is then free to use the data. For example, if a song in digital form has been distributed to the client, the client may listen to the song at any time, using an appropriate media player, by interfacing the token used during the session in which the distribution was made to the computer on which the song resides.
  • [0042]
    A certificate and private key may be issued in a variety of contexts. For example, a certificate and private key may be issued in the course of establishing an account between a content distributor and a consumer. Such would be the case, for example, if a consumer wanted to establish an account with a music distribution company. According to an embodiment of the present invention, the music distribution company would issue a certificate and a private key to the consumer and store them in a token used by the consumer. FIG. 3 shows a detailed method of issuing a certificate and private key and storing them in a token according to an embodiment of the present invention in the general context of a content distribution company.
  • [0043]
    At step 30, a content distribution company or other company provides a client, i.e., a consumer, with enough information necessary to establish an account between the company and the client. The information may include, but is not limited to, providing a client with a company name and a web site address.
  • [0044]
    The company may provide this information in a variety of ways. For example, such information may be made available through a retail store. If a client is interested, for example, in purchasing music, movies or the like over a network such as the Internet and visits a retail store where the company's music, movie or other distribution services are advertised, the client may obtain a package at the retail store containing company information and instructions that direct the user to the company's web site. The client may then go to a computer or other device to access the company's web site, logon to the web site and begin the process of establishing an account with the company.
  • [0045]
    Once the client has logged on to the company web site, a secure connection may be established between the company server and the client. The secure connection may be established in a variety of ways. For example, the widely-implemented Secure Socket Layer (SSL) protocol may be used in establishing a secure connection between the server and the client. Alternatively, other protocols may be used in establishing a secure connection between the server and the client. When establishing a secure connection between the server and the client using SSL, the client may send the server a protocol version number, a session identifier, cipher settings, random numbers, and other information necessary for communicating with the server. In turn, the server may send the client a protocol version number, a session identifier, cipher settings, random numbers, and other information necessary for communicating with the client.
  • [0046]
    Regardless of any protocol used for the connection between the client and the server, at step 32, the server sends the client its certificate and key exchange information. In turn, the client sends the server verification of the server's certificate and key exchange information at step 34. Subsequently, the server and the client may compute a session key for the session at step 36. After the session key has been computed, a secure connection between the server and the client will have been established.
  • [0047]
    Once the session key has been computed and a secure connection established, at step 38 the server may request and the client may send to the server a variety of information, such as, for example, a user name, a password for an account, a credit card number and any other information, such as, for example, addresses, telephone numbers and the like, which may be necessary for the client to establish an account with the company as determined by the company, all of which will have been encrypted with the session key. Once the server has obtained the requisite information from the client, the server may verify the client's credit card number and establish an account for the client at step 40.
  • [0048]
    During this time, terms of the account may also be established. For example, if the company distributes music over a network, the client may choose a variety of payment methods. The client may choose to have his credit card charged a monthly fee for a predetermined number of downloads. Alternatively, the client may choose to have his credit card charged per download. The client and the company may establish any payment method suitable to both parties.
  • [0049]
    Other terms of the account may also be established at this time. For example, in the case of a music distribution company, the duration for which a song may be enabled for listening may depend on the amount of money a client has paid for the song. A small fee charged to the client's credit card may enable the client to listen to the song for a predetermined period of time. A larger fee charged to the client's credit card may enable the client to listen to the song for an unlimited period of time. As with the payment methods, the client and the company may establish any terms suitable to both parties.
  • [0050]
    Subsequent to the establishment of the account, the server may generate a private key for the client, issue a certificate for the client, encrypt both of them with the session key, and store the private key and the client certificate in the client's token at step 42. The server may store the private key and the client certificate in the client's token in a variety of ways. For example, if the chosen token is an IKEY™ hardware token, the token is lightweight and portable, and may be easily included in the package obtained by the client at a retail store. Thus, subsequent to account establishment, the server may direct the client to insert the token into a port on the computer or other device used for the session. The port may connect to a serial bus such as the USB. Thus, with the token connected to a USB port of the device being used by the client, the server may store the private key and the client certificate directly into the token by sending the private key and the client certificate in encrypted form to the token over the network.
  • [0051]
    Alternatively, the server may store the private key and the client certificate into the token at the server location. The token may then be sent to the client using regular mail or delivery services.
  • [0052]
    Once a private key and client certificate have been stored in the client's token, the client may download a media player or other enabling player into the client computer or other device used by the client to utilize downloaded data at step 44. The client is then ready to purchase data over a network and listen to, watch, play, read or utilize in any way, as the case may be, the data downloaded from the server.
  • [0053]
    [0053]FIG. 4 shows a detailed method according to an embodiment of the present invention of verifying a client's identity with a certificate stored in a token; generating a message associated with data requested by the client and the token used by the client; and distributing the data and the associated message to the client in response to a request by the client to purchase data.
  • [0054]
    Once a client has decided to purchase or lease data over a network, whether such data be in the form of entertainment content or otherwise, and has logged on to a company web site, the client and the server may authenticate each other. The authentication between the client and the server may be accomplished in a variety of ways. A variety of protocols may be used for the authentication process. As before, for example, the SSL protocol may be used for authentication between the server and the client. The client may send the server a protocol version number, a session identifier, cipher settings, random numbers, and other information necessary for communicating with the server. In turn, the server may send the client a protocol version number, a session identifier, cipher settings, random numbers, and other information necessary for communicating with the client.
  • [0055]
    The server may send a client a server certificate so that the client may verify the identity of the server at step 50. Additionally, the server may request that the client send the client's certificate to the server so that the server may verify the identity of the client.
  • [0056]
    At step 52, the client sends the server the client certificate that was issued to the client when the client first established an account with the content distribution company. The client may also send the server a verification of the server identity with the server's certificate, thereby notifying the server that the client recognizes the identity of the server.
  • [0057]
    Also, the token used by the client during the transaction may be marked with a distinguishing number. The distinguishing number may be a permanent marking on the token to identify the token. The distinguishing number may be assigned by the token manufacturer at the time of token fabrication. Thus, the token distinguishing number may not be modified or removed from the token and serves to identify the token during its lifetime. At step 52, the client may also send the token distinguishing number to the server. If desired, the server may verify the token distinguishing number sent by the client during the current session with the token distinguishing number sent by the client when the account was established, thereby giving the server a heightened sense of security in identifying and verifying the client requesting the download.
  • [0058]
    Once the client sends the server the client certificate, server certificate verification and token distinguishing number, the server verifies identity of the client with the client certificate at step 54. Once the client's identity has been verified, a symmetrical key may be generated by the server at step 56, thereby establishing a secure connection and allowing data to be transferred from server to client in a secure, encrypted manner. The symmetrical key may be generated randomly.
  • [0059]
    Once the symmetrical key has been generated, the server computes a digital message for the data requested by the client and the client token at step 58. The digital message is, thereafter, associated with the data requested by the client and the token used during the session and serves to permanently link the data requested by the client with the token used during the session. The digital message may take a variety of forms. For example, the digital message may be computed using a public key (asymmetric) cryptographic algorithm and may contain a variety of information, including, without limitation, an identification number of the data the period of time for which the data may be used by the client, the distinguishing number of the token used during the session in which the data was requested or downloaded, and the symmetrical key used to encrypt the data when sent from the server to the client over a network. In notation form, the digital message according to an embodiment of the present invention may be in the form of:
  • D(DID+T+DN+E(S)pukc)prkd
  • [0060]
    where D is the asymmetric cryptography decryption process using a private key, E is the asymmetric cryptography encryption process using a public key, DID is the identification number of the data, T is the period of time for which the data may be used by the client, DN is the distinguishing number of the token used during the session in which the data was requested or downloaded, S is the symmetrical key used to encrypt the data when sent from the server to the client over a network, pukc is the public key of the client and prkd is the private key of the server.
  • [0061]
    Once the digital message has been computed, the server encrypts the data using the symmetrical key and sends it and the digital message to the client at step 60. The client then may use the data in a desired manner or store the data for use at a subsequent time.
  • [0062]
    [0062]FIG. 5A shows a method of using data that has been downloaded from a server according to an embodiment of the present invention. If, for example, the client has downloaded a song in digital form, the client may wish to listen to the song at some point. Thus, at step 64 the client may open the requisite media player and the file containing the song data and the digital message that was downloaded in digital form from the music distributor's server. At step 66, the media player resident in the client computer may ask the client for a token. Thus, the client would then interface his token to the computer or other device currently being used. If, for example, the client is using an IKEY™ hardware token, the token may be inserted directly into a USB port of the computer or other device being used by the client.
  • [0063]
    At step 68, the media player reads the distinguishing number (DN) of the token. Next, at step 70, the media player verifies the digital message that was sent with the downloaded data, the details of which are explained below, with the public key of the distributor's server. Once the digital message has been verified, the media player plays the downloaded data.
  • [0064]
    Details of the digital message verification of step 70 may be seen in FIG. 5B. According to an embodiment of the present invention, at step 72, the media player verifies the DN of the token with the DN that is part of the digital message. If the DN of the token matches the DN of the digital message, the media player then checks the time period associated with the data at step 74 to determine if the client is permitted to play the file according to the terms of the purchase agreement. If the client is within the allowable time period, the media player uses the private key from the token to decrypt the encrypted symmetrical key that was used to transfer data over the network between the server and the client at step 76. The media player may read the private key from the token. Alternatively, if the token is equipped with cryptographic processing capabilities, the media player may send the encrypted symmetrical key to the token so that it may be decrypted with the private key. Armed with the symmetrical key, the media player then decrypts the data that was downloaded at step 78.
  • [0065]
    If steps 72 through 78 are successful, i.e., if all compared values are equal and the encrypted symmetrical key and data can be properly decrypted, the media player may then play the file for the enjoyment of the client at step 80.
  • [0066]
    Thus, the methods and systems according to embodiments of the present invention may deter illegal copying or redistribution of data in a variety of ways. If the DN of the token does not match the DN of the data, which may occur if a token has been stolen or the data has been copied and sent to another client having another token, the media player will not play the file. In addition, if the time period for which the file may be played has expired, or if the time period for which the file may be played has not yet started, such as in the case where a file is downloaded at a particular time for use at a future time, the media player will not play the file.
  • [0067]
    If the data has been modified in any way, which may be the result of unscrupulous users attempting to circumvent the system by tampering with the data, the client generally will be aware of such modification because the data, in its modified form, will not be usable to the client. The client may then have the option of sending the digital message back to the server and ask the server to re-send the data to the client. The server can determine what data to send back to the client by using the DID in the digital message.
  • [0068]
    Furthermore, if downloaded data and the associated digital message is stolen from a client by an unscrupulous client having his own token, the file will still not play because only the private key from the original client's token can decrypt the encrypted symmetrical key when the symmetrical key is decrypted by the media player. In addition, the digital message cannot be forged by a third party since it was encrypted using the private key of the server.
  • [0069]
    According to further embodiments of the invention, if a client should lose the token or have the token stolen, the client may so notify the server that the token has been lost or stolen. The server may then revoke the client's certificate. Thus, should a third party attempt to use the token after the server has revoked the client's certificate, the token, which stores the client's certificate, will be rejected by the server. Thus, after a certificate has been revoked, the token storing the certificate will be essentially useless, thereby adding yet another layer of protection afforded by the methods and systems according to embodiments of the present invention.
  • [0070]
    In addition, use of the token by a third party who has stolen or otherwise illegally obtained the token may be further prevented by utilizing a password protection system with the token. As explained previously, when a client establishes an account with a server, the client may be required to furnish to the server a password for the account. The client may also be require to enter a password for the token. If a token has been stolen by a third party, the third party will not have knowledge of the password, thereby making it difficult for the third party to use the stolen token to purchase data.
  • [0071]
    The method of verifying a digital message and playing a downloaded file shown in FIGS. 5A and 5B are representative embodiments of the present invention. Other information may be included in the digital message and other methods according to embodiments of the present invention may be used to verify the digital message and utilize downloaded data.
  • [0072]
    Systems implementing embodiments of the present invention need not be limited to the system shown in FIG. 1. For example, FIG. 6 shows an alternative system according to embodiments of the present invention. A client computer or other computing device 10 connects to a network 14. Connected to the client computer or other computing device 10 is a token 12. A firewall 18 connects to the network 14 as an added layer of protection for the server 16. In addition, a cryptographic processor 15 may be connected between the firewall 18 and the server 16. The cryptographic processor 15 may handle some or all of the cryptographic and other functions performed by embodiments of the invention. For example, the cryptographic processor 15 may function as a certificate authority. In addition, the cryptographic processor 15 may perform all of the functions necessary when establishing a secure connection between a server and a client, may generate digital messages and may encrypt data.
  • [0073]
    The server 16 may also be supplemented by a data base 17. The data base 17 may store account numbers, passwords, and any other of a variety of information required by a distributor to implement the particular embodiment of the present invention.
  • [0074]
    [0074]FIG. 7 shows an alternative system according to embodiments of the present invention. A client computer or other computing device 10 connects to a network 14. Connected to the client computer or other computing device 10 is a token 12. Also connected to the network is a third party certificate authority 13. The third party certificate authority 13 may provide a variety of functions, including, without limitation, verifying clients, issuing client certificates, preliminarily establishing client accounts, and the like. The performance of such functions by the third party certificate authority may relieve the burden of these functions from the distributor's server, thereby allowing the server to focus its activities on downloading data requests made by clients.
  • [0075]
    The computer or other computing device 10 may be implemented in a variety of ways. For example, the computer or other computing device 10 may be a portable device such as a PALM™ handheld or other portable device. The portable device or other handheld may have a wireless connection to a network. For example, embodiments of the present invention may by implemented on a handheld device with a wireless connection to the Internet. Clients who are interested in, for example, downloading music from the Internet could interface their tokens to the handheld device and download music to the handheld device. If the handheld device is equipped with audio processing hardware, cryptographic capabilities, and an interface for the token, a media player on the handheld device could play the downloaded music file, thereby allowing the client to listen to music virtually anywhere.
  • [0076]
    Moreover, downloaded data is not limited to entertainment content. A variety of data may be downloaded according to embodiments of the present invention, including, without limitation, software, consumer information, account information, or other data.
  • [0077]
    While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that the invention is not limited to the particular embodiments shown and described and that changes and modifications may be made without departing from the spirit and scope of the appended claims.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US5590197 *Apr 4, 1995Dec 31, 1996V-One CorporationElectronic payment system and method
US5754656 *Aug 1, 1996May 19, 1998Hitachi, Ltd.Electronic shopping method, electronic shopping system and document authenticating method relating thereto
US5809144 *Aug 24, 1995Sep 15, 1998Carnegie Mellon UniversityMethod and apparatus for purchasing and delivering digital goods over a network
US5889860 *Nov 8, 1996Mar 30, 1999Sunhawk Corporation, Inc.Encryption system with transaction coded decryption key
US5983273 *Sep 16, 1997Nov 9, 1999Webtv Networks, Inc.Method and apparatus for providing physical security for a user account and providing access to the user's environment and preferences
US5987140 *Apr 26, 1996Nov 16, 1999Verifone, Inc.System, method and article of manufacture for secure network electronic payment and credit collection
US5995626 *Apr 2, 1998Nov 30, 1999Hitachi, Ltd.Electronic shopping method, electronic shopping system and document authenticating method relating thereto
US6111956 *Feb 3, 1998Aug 29, 2000Signals, Inc.Method for secure key distribution over a nonsecure communications network
US6233682 *Jan 18, 2000May 15, 2001Bernhard FritschDistribution of musical products by a web site vendor over the internet
US6246996 *May 7, 1998Jun 12, 2001Messagemedia, Inc.Computerized system for facilitating transactions between parties on the internet using e-mail
US6385596 *Feb 6, 1998May 7, 2002Liquid Audio, Inc.Secure online music distribution system
US6742023 *Apr 28, 2000May 25, 2004Roxio, Inc.Use-sensitive distribution of data files between users
US6779115 *Feb 18, 2000Aug 17, 2004Digital5, Inc.Portable device using a smart card to receive and decrypt digital data
US20010051996 *Feb 20, 2001Dec 13, 2001Cooper Robin RossNetwork-based content distribution system
US20020002541 *Jun 29, 2001Jan 3, 2002Williams Eddie H.Online digital content library
US20020004902 *Jun 21, 2001Jan 10, 2002Eng-Whatt TohSecure and reliable document delivery
US20020029350 *Feb 12, 2001Mar 7, 2002Cooper Robin RossWeb based human services conferencing network
US20030163787 *Dec 20, 2000Aug 28, 2003Hay Brian RobertVirtual token
US20050149759 *Feb 25, 2005Jul 7, 2005Movemoney, Inc.User/product authentication and piracy management system
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7464089Aug 19, 2005Dec 9, 2008Connect Technologies CorporationSystem and method for processing a data stream to determine presence of search terms
US7486673Aug 29, 2005Feb 3, 2009Connect Technologies CorporationMethod and system for reassembling packets prior to searching
US7540788Jan 5, 2007Jun 2, 2009Apple Inc.Backward compatible connector system
US7548620Feb 23, 2004Jun 16, 2009Verisign, Inc.Token provisioning
US7627343Dec 1, 2009Apple Inc.Media player system
US7632114Dec 15, 2009Apple Inc.Interface connecter between media player and other electronic devices
US7632146May 1, 2009Dec 15, 2009Apple Inc.Backward compatible connector system
US7640577Dec 29, 2009Sony CorporationSystem and method for authenticating components in wireless home entertainment system
US7660929Feb 9, 2010Apple Inc.Connector interface system for a multi-communication device
US7673083Sep 11, 2006Mar 2, 2010Apple Inc.Method and system for controlling video selection and playback in a portable media player
US7702833Sep 12, 2008Apr 20, 2010Apple Inc.Techniques for transferring information between an accessory and a multi-communication device
US7751853Apr 3, 2009Jul 6, 2010Apple Inc.Female receptacle data pin connector
US7757026Jul 13, 2010Apple Inc.Techniques for transferring status information between an accessory and a multi-communication device
US7779185Apr 15, 2009Aug 17, 2010Apple Inc.Communication between a media player and an accessory using a protocol with multiple lingoes
US7783070Sep 25, 2008Aug 24, 2010Apple Inc.Cable adapter for a media player system
US7784087Aug 4, 2005Aug 24, 2010Toshiba CorporationSystem and method for securely sharing electronic documents
US7797471Jun 27, 2006Sep 14, 2010Apple Inc.Method and system for transferring album artwork between a media player and an accessory
US7822209Oct 26, 2010Red Hat, Inc.Methods and systems for key recovery for a token
US7823214Oct 26, 2010Apple Inc.Accessory authentication for electronic devices
US7826318Nov 2, 2010Apple Inc.Method and system for allowing a media player to transfer digital audio to an accessory
US7853746Dec 14, 2010Apple Inc.Interface system for enabling data communication between a multi-communication device and other devices
US7877532Jan 25, 2011Apple Inc.Communication between an accessory and a media player with multiple lingoes and lingo version information
US7895378Feb 22, 2011Apple Inc.Method and system for allowing a media player to transfer digital audio to an accessory
US7921464Jun 20, 2005Apr 5, 2011Lg Electronics Inc.Method of downloading contents and system thereof
US7949810May 24, 2011Apple Inc.Techniques for transferring data between a media player and an accessory having a tuner
US7992203Aug 2, 2011Red Hat, Inc.Methods and systems for secure shared smartcard access
US8006019Nov 2, 2009Aug 23, 2011Apple, Inc.Method and system for transferring stored data between a media player and an accessory
US8015599Sep 6, 2011Symantec CorporationToken provisioning
US8047966Nov 1, 2011Apple Inc.Interfacing portable media devices and sports equipment
US8050714Nov 1, 2011Apple Inc.Docking station for media player system
US8074265Dec 6, 2011Red Hat, Inc.Methods and systems for verifying a location factor associated with a token
US8078224Dec 13, 2011Apple Inc.Male plug connector
US8078776Dec 14, 2010Dec 13, 2011Apple Inc.Electronic device having a dual key connector
US8082376Dec 20, 2011Apple Inc.Communication between an accessory and a media player with multiple protocol versions
US8095716Jul 21, 2008Jan 10, 2012Apple Inc.Method and system for communicating capability information from an accessory to a media player
US8098829Jan 17, 2012Red Hat, Inc.Methods and systems for secure key delivery
US8099536Jan 17, 2012Apple Inc.Communication between an accessory and a media player with general and accessory lingoes
US8099765Jun 7, 2006Jan 17, 2012Red Hat, Inc.Methods and systems for remote password reset using an authentication credential managed by a third party
US8112567Feb 7, 2012Apple, Inc.Method and system for controlling power provided to an accessory
US8117651 *Jun 27, 2006Feb 14, 2012Apple Inc.Method and system for authenticating an accessory
US8135891Aug 7, 2009Mar 13, 2012Apple Inc.Method and system for transferring button status information between a media player and an accessory
US8145898Dec 23, 2003Mar 27, 2012Hewlett-Packard Development Company, L.P.Encryption/decryption pay per use web service
US8161567Apr 17, 2012Apple Inc.Accessory authentication for electronic devices
US8165634Apr 24, 2012Apple Inc.Female receptacle connector
US8171194Aug 16, 2010May 1, 2012Apple Inc.Accessory communication with a media player using a display remote lingo
US8171195Aug 16, 2010May 1, 2012Apple Inc.Media player communication with an accessory using a display remote lingo
US8180741May 15, 2012Red Hat, Inc.Methods and systems for providing data objects on a token
US8190205May 29, 2012Apple Inc.Male plug connector
US8208853Jun 26, 2012Apple Inc.Accessory device authentication
US8238811Jan 7, 2009Aug 7, 2012Apple Inc.Cross-transport authentication
US8239595Aug 7, 2012Apple Inc.Communication between a media player and an accessory with an extended interface mode
US8271038Oct 19, 2007Sep 18, 2012Apple Inc.Wireless adapter for media player system
US8271705Sep 18, 2012Apple Inc.Dual key electronic connector
US8285901Oct 9, 2012Apple Inc.Communication between an accessory and a media player using an extended interface lingo
US8317658Oct 12, 2011Nov 27, 2012Apple Inc.Interfacing portable media devices and sports equipment
US8332637Jun 6, 2006Dec 11, 2012Red Hat, Inc.Methods and systems for nonce generation in a token
US8347076 *Jan 1, 2013Samsung Electronics Co., Ltd.System and method for building home domain using smart card which contains information of home network member device
US8356342Aug 31, 2006Jan 15, 2013Red Hat, Inc.Method and system for issuing a kill sequence for a token
US8364952Jun 6, 2006Jan 29, 2013Red Hat, Inc.Methods and system for a key recovery plan
US8370555Feb 5, 2013Apple Inc.Method and system for allowing a media player to determine if it supports the capabilities of an accessory
US8386680Nov 15, 2011Feb 26, 2013Apple Inc.Communication between an accessory and a media player with multiple protocol versions and extended interface lingo
US8402187Mar 19, 2013Apple Inc.Method and system for transferring button status information between a media player and an accessory
US8412927Jun 7, 2006Apr 2, 2013Red Hat, Inc.Profile framework for token processing system
US8417967Apr 2, 2008Apr 9, 2013Hewlett-Packard Development Company, L.P.Storage device data encryption using a binary large object (BLOB)
US8424099 *Apr 16, 2013Comcast Cable Communications, LlcPC secure video path
US8467829Jun 18, 2013Apple Inc.Wireless adapter for media player system
US8495380 *Jun 6, 2006Jul 23, 2013Red Hat, Inc.Methods and systems for server-side key generation
US8509691May 17, 2012Aug 13, 2013Apple Inc.Accessory device authentication
US8572403 *Dec 24, 2009Oct 29, 2013The Commonwealth Of AustraliaDigital video guard
US8581449Sep 9, 2010Nov 12, 2013Apple Inc.Portable power source to provide power to an electronic device via an interface
US8589695 *Jun 7, 2006Nov 19, 2013Red Hat, Inc.Methods and systems for entropy collection for server-side key generation
US8590036Jan 10, 2012Nov 19, 2013Apple Inc.Method and system for authenticating an accessory
US8634761Jun 29, 2012Jan 21, 2014Apple Inc.Cross-transport authentication
US8639940Feb 28, 2007Jan 28, 2014Red Hat, Inc.Methods and systems for assigning roles on a token
US8661557 *Dec 21, 2011Feb 25, 2014Valve CorporationMethod and system for granting access to system and content
US8693690Dec 4, 2006Apr 8, 2014Red Hat, Inc.Organizing an extensible table for storing cryptographic objects
US8707024Aug 4, 2006Apr 22, 2014Red Hat, Inc.Methods and systems for managing identity management security domains
US8713685 *Feb 18, 2013Apr 29, 2014Comcast Cable Communications, LlcPC secure video path
US8739300Dec 30, 2010May 27, 2014Intergraph CorporationSystem and method for transmission of files within a secured network
US8762350Mar 13, 2012Jun 24, 2014Red Hat, Inc.Methods and systems for providing data objects on a token
US8763079Dec 4, 2008Jun 24, 2014Apple Inc.Accessory authentication for electronic devices
US8769614 *Dec 29, 2010Jul 1, 2014Akamai Technologies, Inc.Security framework for HTTP streaming architecture
US8787566Aug 23, 2006Jul 22, 2014Red Hat, Inc.Strong encryption
US8793492 *Jan 13, 2011Jul 29, 2014Adobe Systems IncorporatedMethods and systems for scalable distribution of protected content
US8806219Aug 23, 2006Aug 12, 2014Red Hat, Inc.Time-based function back-off
US8813243Feb 2, 2007Aug 19, 2014Red Hat, Inc.Reducing a size of a security-related data object stored on a token
US8817043Apr 24, 2009Aug 26, 2014Disney Enterprises, Inc.System and method for selective viewing of a hidden presentation within a displayed presentation
US8832453Feb 28, 2007Sep 9, 2014Red Hat, Inc.Token recycling
US8890892 *Nov 12, 2009Nov 18, 2014PixarSystem and method for steganographic image display
US8977844Aug 31, 2006Mar 10, 2015Red Hat, Inc.Smartcard formation with authentication keys
US9038154Aug 31, 2006May 19, 2015Red Hat, Inc.Token Registration
US9081948Mar 13, 2007Jul 14, 2015Red Hat, Inc.Configurable smartcard
US9160541 *Nov 19, 2013Oct 13, 2015Apple Inc.Method and system for authenticating an accessory
US9208284 *Jun 27, 2014Dec 8, 2015Practice Fusion, Inc.Medical professional application integration into electronic health record system
US9223958Jun 23, 2014Dec 29, 2015Apple Inc.Accessory authentication for electronic devices
US9332320Mar 10, 2014May 3, 2016Comcast Cable Communications, LlcPC secure video path
US20040250076 *Jan 2, 2004Dec 9, 2004Hsiang-Tsung KungPersonal authentication device and system and method thereof
US20050102652 *Oct 13, 2004May 12, 2005Sony CorporationSystem and method for building software suite
US20050120216 *Dec 1, 2004Jun 2, 2005Samsung Electronics Co., Ltd.System and method for building home domain using smart card which contains information of home network member device
US20050135628 *Feb 19, 2004Jun 23, 2005Sony CorporationSystem and method for authenticating components in wireless home entertainment system
US20050138360 *Dec 23, 2003Jun 23, 2005Kamalakantha Chandra H.Encryption/decryption pay per use web service
US20050188202 *Feb 23, 2004Aug 25, 2005Nicolas PoppToken provisioning
US20050240705 *Apr 27, 2004Oct 27, 2005Novotney Donald JConnector interface system for a multi-communication device
US20060021062 *Jun 20, 2005Jan 26, 2006Jang Hyun SMethod of downloading contents and system thereof
US20060156415 *Feb 3, 2005Jul 13, 2006Rubinstein Jonathan JAccessory authentication for electronic devices
US20070192488 *Feb 14, 2006Aug 16, 2007Dacosta Behram MSystem and method for authenticating components in wireless home entertainment system
US20070232098 *Mar 30, 2006Oct 4, 2007Apple Computer, Inc.Interface connector between media player and computer
US20070234420 *Jun 27, 2006Oct 4, 2007Novotney Donald JMethod and system for authenticating an accessory
US20070288747 *Aug 4, 2006Dec 13, 2007Nang Kon KwanMethods and systems for managing identity management security domains
US20070300155 *Sep 11, 2006Dec 27, 2007Laefer Jay SMethod and system for controlling video selection and playback in a portable media player
US20080005339 *Jun 7, 2006Jan 3, 2008Nang Kon KwanGuided enrollment and login for token users
US20080022086 *Jun 6, 2006Jan 24, 2008Red. Hat, Inc.Methods and system for a key recovery plan
US20080022121 *Jun 6, 2006Jan 24, 2008Red Hat, Inc.Methods and systems for server-side key generation
US20080022122 *Jun 7, 2006Jan 24, 2008Steven William ParkinsonMethods and systems for entropy collection for server-side key generation
US20080025172 *Jun 26, 2007Jan 31, 2008Apple Inc.Method and System For Allowing A Media Player To Transfer Digital Audio To An Accessory
US20080034129 *Aug 15, 2007Feb 7, 2008Apple Inc.Method And System For Transferring Status Information Between A Media Player And An Accessory
US20080056496 *Aug 31, 2006Mar 6, 2008Parkinson Steven WMethod and system for issuing a kill sequence for a token
US20080059790 *Aug 31, 2006Mar 6, 2008Steven William ParkinsonMethods, apparatus and systems for smartcard factory
US20080059793 *Aug 31, 2006Mar 6, 2008Lord Robert BMethods and systems for phone home token registration
US20080069338 *Aug 31, 2006Mar 20, 2008Robert RelyeaMethods and systems for verifying a location factor associated with a token
US20080069341 *Aug 23, 2006Mar 20, 2008Robert RelyeaMethods and systems for strong encryption
US20080123285 *Oct 19, 2007May 29, 2008Apple, Inc.Media player system
US20080125031 *Oct 19, 2007May 29, 2008Apple Inc.Media Player System
US20080133514 *Dec 4, 2006Jun 5, 2008Robert RelyeaMethod and Apparatus for Organizing an Extensible Table for Storing Cryptographic Objects
US20080189543 *Feb 2, 2007Aug 7, 2008Steven William ParkinsonMethod and system for reducing a size of a security-related data object stored on a token
US20080209225 *Feb 28, 2007Aug 28, 2008Robert LordMethods and systems for assigning roles on a token
US20080229401 *Mar 13, 2007Sep 18, 2008John MagneMethods and systems for configurable smartcard
US20080270578 *Jul 9, 2008Oct 30, 2008Huawei Technologies Co., Ltd.Method, Device And Data Download System For Controlling Effectiveness Of A Download Transaction
US20090006700 *Sep 12, 2008Jan 1, 2009Apple Inc.Connector interface system for a multi-communication device
US20090006701 *Sep 12, 2008Jan 1, 2009Apple Inc.Techniques for transferring status information between an accessory and a multi-communication device
US20090013096 *Sep 12, 2008Jan 8, 2009Apple Inc.Techniques for transferring information between an accessory and a multi-communication device
US20090013110 *Sep 12, 2008Jan 8, 2009Apple Inc.Connector interface system for enabling data communication with a multi-communication device
US20090125134 *Sep 11, 2008May 14, 2009Apple Inc.Method and system for controlling an accessory having a tuner
US20090191732 *Apr 3, 2009Jul 30, 2009Apple Inc.Female receptacle data pin connector
US20090198361 *Apr 15, 2009Aug 6, 2009Apple Inc.Communication between an accessory and a media player with multiple lingoes
US20090204244 *Apr 15, 2009Aug 13, 2009Apple Inc.Communication between an accessory and a media player with multiple protocol versions
US20090204738 *Apr 15, 2009Aug 13, 2009Apple Inc.Communication between an accessory and a media player with multiple protocol versions
US20090221404 *Sep 26, 2008Sep 3, 2009Apple Inc.Interfacing portable media devices and sports equipment
US20090249101 *Jun 4, 2009Oct 1, 2009Apple Inc.Method and system for controlling power provided to an accessory
US20090274303 *May 19, 2009Nov 5, 2009Nicolas PoppToken provisioning
US20090292835 *Nov 26, 2009Apple Inc.Techniques for transferring status information between an accessory and a multi-communication device
US20100075604 *Sep 9, 2009Mar 25, 2010Apple Inc.Accessory device authentication
US20100087099 *Apr 8, 2010Apple Inc.Male plug connector
US20100173673 *Jul 8, 2010Apple Inc.Cross-transport authentication
US20100271396 *Oct 28, 2010Disney Enterprises, Inc.System and method for selective viewing of a hidden presentation within a displayed presentation
US20100312931 *Aug 16, 2010Dec 9, 2010Apple Inc.Accessory communication with a media player using a display remote lingo
US20100312932 *Dec 9, 2010Apple Inc.Media player communication with an accessory using a display remote lingo
US20100327664 *Sep 9, 2010Dec 30, 2010Apple Inc.Portable power source to provide power to an electronic device via an interface
US20110029785 *Apr 2, 2008Feb 3, 2011Foster Joseph EDisk drive data encryption
US20110061113 *Sep 30, 2010Mar 10, 2011Apple Inc.Accessory authentication for electronic devices
US20110066775 *Nov 23, 2010Mar 17, 2011Apple Inc.Communication Between a Media Player and an Accessory with an Extended Interface Mode
US20110066776 *Nov 23, 2010Mar 17, 2011Apple Inc.Communication Between a Media Player and an Accessory with an Extended Interface Mode
US20110086551 *Apr 14, 2011Apple Inc.Electronic device and connector
US20110122152 *May 26, 2011Pixar Animation StudiosSystem and method for steganographic image display
US20110151724 *Jun 23, 2011Apple Inc.Female receptacle connector
US20110151725 *Jun 23, 2011Apple Inc.Male plug connector
US20110162050 *Jun 30, 2011Intergraph Technologies CompanySystem and Method for Transmission of Files Within a Secured Network
US20110219239 *Sep 8, 2011Comcast Cable Communications, LlcPC Secure Video Path
US20110264922 *Dec 24, 2009Oct 27, 2011The Commonwealth Of AustraliaDigital video guard
US20120095816 *Apr 19, 2012Valve CorporationMethod and system for granting access to system and content
US20120185695 *Jul 19, 2012Adobe Systems IncorporatedMethods and Systems for Scalable Distribution of Protected Content
US20130163763 *Feb 18, 2013Jun 27, 2013Comcast Cable Communications, LlcPC Secure Video Path
US20140101782 *Sep 30, 2013Apr 10, 2014The Commonwealth Of AustraliaDigital video guard
US20140181251 *Jan 3, 2014Jun 26, 2014Sony Dadc Austria AgMethod for downloading content from a server onto a recording medium as well as recording medium being suitable therefor
US20140223184 *Nov 19, 2013Aug 7, 2014Apple Inc.Method and system for authenticating an accessory
US20140337958 *Jun 4, 2014Nov 13, 2014Akamai Technologies, Inc.Security framework for http streaming architecture
USRE43780Oct 30, 2012Apple Inc.Plug connector
USRE43796Nov 5, 2009Nov 6, 2012Apple Inc.Receptacle connector
CN101479737BJun 26, 2007Jun 13, 2012苹果公司Method and system for authenticating an accessory
EP1610200A3 *Jun 20, 2005Jan 11, 2006Lg Electronics Inc.Method of downloading contents and system thereof
EP1719284A1 *Feb 23, 2005Nov 8, 2006Verisign, Inc.Token provisioning
EP1719284A4 *Feb 23, 2005Dec 17, 2008Verisign IncToken provisioning
EP2363822A2 *Mar 1, 2011Sep 7, 2011Comcast Cable Communications, LLCPC secure video path
EP2363822A3 *Mar 1, 2011Mar 14, 2012Comcast Cable Communications, LLCPC secure video path
WO2004098079A1 *Mar 18, 2004Nov 11, 2004Apple Computer Inc.Media player system
WO2005067202A1 *Nov 19, 2004Jul 21, 2005Electronic Data Systems CorporationSecure file transfer for web service
WO2009123630A1 *Apr 2, 2008Oct 8, 2009Hewlett-Packard Development Company, L.P.Disk drive data encryption
WO2011082322A2 *Dec 30, 2010Jul 7, 2011Intergraph Technologies CompanyA system and method for transmission of files within a secured network
WO2011082322A3 *Dec 30, 2010Dec 8, 2011Intergraph Technologies CompanyA system and method for transmission of files within a secured network
Classifications
U.S. Classification709/237, 726/3, 726/26, 709/229
International ClassificationH04L29/06, G06F21/00
Cooperative ClassificationH04L63/126, G06F21/6218, G06F2221/2137, H04L63/04, G06F21/10, G06F2221/0737, H04L63/0823, G06F2221/0797
European ClassificationH04L63/08C, G06F21/62B, H04L63/12B, G06F21/10
Legal Events
DateCodeEventDescription
Jan 8, 2002ASAssignment
Owner name: RAINBOW TECHNOLOGIES, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TAN, KAIJUN;COCHRAN, MICHAEL LLOYD;BADIA, LOGAN;REEL/FRAME:012458/0392
Effective date: 20011019
Nov 14, 2005ASAssignment
Owner name: SAFENET, INC., MARYLAND
Free format text: MERGER;ASSIGNOR:RAINBOW TECHNOLOGIES, INC.;REEL/FRAME:017227/0781
Effective date: 20040315
Apr 16, 2007ASAssignment
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERA
Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:SAFENET, INC.;REEL/FRAME:019161/0506
Effective date: 20070412
Apr 19, 2007ASAssignment
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERA
Free format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:SAFENET, INC.;REEL/FRAME:019181/0012
Effective date: 20070412