Systems and methods for identitybased encryption and related cryptographic techniques
Download PDFInfo
 Publication number
 US20090034714A9 US20090034714A9 US11431410 US43141006A US2009034714A9 US 20090034714 A9 US20090034714 A9 US 20090034714A9 US 11431410 US11431410 US 11431410 US 43141006 A US43141006 A US 43141006A US 2009034714 A9 US2009034714 A9 US 2009034714A9
 Authority
 US
 Grant status
 Application
 Patent type
 Prior art keywords
 key
 id
 system
 public
 receiver
 Prior art date
 Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
 Granted
Links
Images
Classifications

 H—ELECTRICITY
 H04—ELECTRIC COMMUNICATION TECHNIQUE
 H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
 H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
 H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
 H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
 H04L9/0838—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these
 H04L9/0847—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these involving identity based encryption [IBE] schemes

 H—ELECTRICITY
 H04—ELECTRIC COMMUNICATION TECHNIQUE
 H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
 H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
 H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
 H04L9/3066—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyperelliptic curves
 H04L9/3073—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyperelliptic curves involving pairings, e.g. identity based encryption [IBE], bilinear mappings or bilinear pairings, e.g. Weil or Tate pairing

 H—ELECTRICITY
 H04—ELECTRIC COMMUNICATION TECHNIQUE
 H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
 H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
 H04L2209/04—Masking or blinding
Abstract
Description
 [0001]This application is a continuation of copending U.S. patent application Ser. No. 10/218,691 filed Aug. 13, 2002, which claims the benefit of U.S. provisional application No. 60/311,946, filed Aug. 13, 2001, both of which are incorporated herein by reference.
 [0002]The present invention was made with the support of DARPA contract F306029910530. The U.S. Government has certain rights in the invention.
 [0003]The field of the present invention relates generally to cryptographic systems.
 [0004]Publickey cryptographic systems allow two people to exchange private and authenticated messages without requiring that they first have a secure communication channel for sharing private keys. One of the most widely used publickey cryptosystem is the RSA cryptosystem disclosed in U.S. Pat. No. 4,405,829. The RSA cryptosystem is currently deployed in many commercial systems. It is used by web servers and browsers to secure web traffic, it is used to ensure privacy and authenticity of email, it is used to secure remote login sessions, and it is at the heart of electronic creditcard payment systems. In short, RSA is frequently used in applications where security of digital data is a concern.
 [0005]According to publickey cryptosystems such as the RSA cryptosystem, each person has a unique pair of keys: a private key that is a secret and a public key that is widely known. This pair of keys has two important properties: (1) the private key cannot be deduced from knowledge of the public key alone, and (2) the two keys are complementary, i.e., a message encrypted with one key of the pair can be decrypted only with the complementary key. In these systems, both the public key and the private key in a pair are generated together as the output of a key generation algorithm that takes as input a random seed. Consequently, in these cryptosystems, people cannot choose a desired public or private key, but must simply use the keys that are generated for them by a key generation algorithm. This has the disadvantage that others cannot encrypt messages to a person until that person generates and publishes a public key. Another problem with this type of cryptosystem is that an impostor can publish a public key and claim that it belongs to someone else. To address this issue, a trusted certificate authority (CA) is used to authenticate individuals and certify to others that the individual's public key is authentic. Unfortunately, this adds complexity to the cryptosystem since a sender must obtain a certificate for every receiver, and must obtain a new certificate every time an existing certificate expires. It also requires receivers to create public keys, publish them, register certificates with the CA, and renew such certificates when they expire.
 [0006]In 1984 Shamir envisioned a new type of public key encryption scheme (described in A. Shamir, “Identitybased cryptosystems and signature schemes”, in Advances in Cryptology—Crypto '84, Lecture Notes in Computer Science, Vol. 196, SpringerVerlag, pp. 4753, 1984). According to Shamir's scheme, a person's public key consists of a public identifier, which may be the person's name and network address, or combination of name and email address, social security number, street address, telephone number, or office address. Because the public key is the person's preexisting public identifier (ID) rather than a key produced from a random seed, this kind of public key cryptosystem is called an identitybased encryption (IBE) scheme. Shamir, however, did not provide a concrete, practical IBE cryptosystem. In fact, Shamir argued that existing cryptosystems (such as RSA) could not be adapted to realize a secure IBE cryptosystem.
 [0007]In the years since Shamir proposed his IBE scheme there have been several attempts to realize an identitybased cryptosystem. Some proposals require that users not collude. Other proposals require the private key generator (PKG) to spend an impractically long time for each private key generation request. Some proposals require tamper resistant hardware.
 [0008]In short, there remains a need for improved cryptographic methods and systems.
 [0009]According to one embodiment of the invention, a method of encrypting a first piece of information to be sent by a sender to a receiver uses an encryption key generated from a second piece of information. A bilinear map and the encryption key are used to encrypt at least a portion of the first piece of information to be sent from the sender to the receiver. The bilinear map may be symmetric or asymmetric. The bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve. More generally, the bilinear map may be based on a pairing defined on algebraic varieties.
 [0010]According to one embodiment of the invention, encrypting the portion of the first piece of information can be completed prior to generating a decryption key corresponding to the encryption key.
 [0011]According to another embodiment of the invention, the second piece of information is known to the receiver prior to the generation of a decryption key corresponding to the encryption key. The second piece of information may comprise a character string such as an email address, name or other identifier associated with the receiver, according to different embodiments of the invention. The second piece of information may also include, according to various embodiments, an attribute associated with the receiver or information corresponding to a time or times, such as a date or series of dates defining one or more time intervals. A decryption key may be provided based on a time that a request for the decryption key is received relative to the information corresponding to a time. According to other embodiments of the invention, the second piece of information may include a message identifier, a credential identifier or a message subject identifier.
 [0012]According to another embodiment of the invention, a message key is generated from the encryption key using a bilinear map, and a cryptographic hash function is applied to the message key.
 [0013]According to another embodiment of the invention, encrypting the portion of the first piece of information includes generating a mask from the second piece of information using a bilinear map. The mask is applied to the portion of the second piece of information.
 [0014]An embodiment of the invention is directed to a method of decrypting ciphertext which has been encrypted by a sender using an identitybased encryption key associated with a receiver. A decryption key derived from the encryption key is obtained. At least a portion of the ciphertext is decrypted using a bilinear map and the decryption key. The bilinear map may be symmetric or asymmetric. The bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve.
 [0015]According to another embodiment of the invention, the ciphertext is obtained prior to creating the decryption key. According to another embodiment of the invention, the first piece of information is known to the receiver prior to obtaining the ciphertext and prior to obtaining the decryption key. The decryption key may be obtained by sending a request to a private key generator, including information sent together with the ciphertext.
 [0016]An embodiment of the invention is directed to a method of generating a decryption key corresponding to an encryption key. An algebraic group, a group action, and a master key are provided. The encryption key is generated based on a first piece of information. The decryption key is generated based on the group action, the master key and the encryption key. According to one embodiment of the invention, the group action is capable of being calculated in polynomial time. According to another aspect of the invention, generation of the decryption key in the absence of the master key would require greater than polynomial time.
 [0017]Another embodiment of the invention is directed to a method of providing system parameters for a cryptographic system. Algebraic groups _{1 }and _{2 }having an order q are provided, together with associated group actions. In addition, a bilinear map is provided that maps pairs of points in _{1 }to points in _{2}. In another embodiment, a system parameter representing a member P of G_{1}, and a system parameter representing a member P_{pub }of G_{1 }are provided, where P_{pub }is based on the group action of a master key s applied to P. According to other embodiments of the invention, a system parameter representing a set of one or more hash functions H_{1}, H_{2}, H_{3}, or H_{4 }are provided. According to another embodiment of the invention, a system parameter representing a size n of a message space is provided.
 [0018]According to another embodiment of the invention, the bilinear map may be asymmetric or symmetric. In another embodiment the bilinear map is based on a Weil pairing or a Tate pairing defined on a portion of an elliptic curve.
 [0019]According to another embodiment of the invention, the algebraic group G_{1 }is defined by an elliptic curve defined over a field of order p and the order q is less than the order p. According to another aspect of the invention, the length of p is at least 1024 bits and the length of q is no greater than 160 bits.
 [0020]Another embodiment of the invention is directed to a method for managing cryptographic communication including generating shares of a master key. The shares are stored in separate systems. A request from a receiver to obtain a private key is responded to in the separate systems by generating from the respective shares of the master key, corresponding respective shares of the private key. The receiver constructs the private key from the shares of the private key, where the private key corresponds to identifying information of the receiver.
 [0021]Another embodiment of the invention is directed to a method for communicating between a sender and a receiver. A message to be sent from the sender to the receiver is encrypted, and the message is sent from the sender to the receiver. A request for a decryption key is received from the receiver of the message. After receiving the request for the decryption key, information indicating that the receiver has received the message is generated, and the decryption key is provided to the receiver. According to an embodiment of the invention, a return address of the sender is included in the message, and an acknowledgment that the message has been received is sent to the return address. According to another aspect of the invention, an identification of the message is included in an acknowledgment and the acknowledgment is sent to the sender. According to another aspect of the invention, the encryption key is derived based on a return address of the sender.
 [0022]Another embodiment of the invention is directed to a method for communicating between a sender and a receiver having a credential. Identifying information of the receiver is obtained. A credential required for the receiver to gain a decryption key is specified, and an encryption key is derived from the identifying information of the receiver and the credential. A message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map, and the message is sent from the sender to the receiver. A request for a decryption key is received from the receiver of the message. It is determined whether the receiver has the credential, and if the receiver has the credential, the decryption key is provided to the receiver. The receiver then may use the decryption key and the bilinear map to decrypt the message.
 [0023]Another embodiment of the invention is directed to a method of communicating between a sender and a receiver involving storing a decryption key on a target system. Sets of decryption keys associated with times messages may be decrypted are derived, and the decryption keys are stored on the target system. An encryption key is derived from a string associated with a time a message is to be decrypted. A message is encrypted using the encryption key. The message is received on the target system, and the message is decrypted using a bilinear map and the corresponding decryption key.
 [0024]Another embodiment of the invention is directed to a method of communicating between a sender and receiver involving entities having different responsibilities. A set of decryption keys is derived from a master key and a set of strings associated with different responsibilities. The decryption keys are provided to entities having the respective responsibilities. An encryption key is derived from a string associated with one of the different responsibilities. A message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map. An entity having a particular responsibility receives the message and decrypts the message using the respective decryption key and the bilinear map. According to one embodiment of the invention, the string corresponding to the particular responsibility comprises a subject line of an email.
 [0025]
FIG. 1 is a block diagram illustrating a cryptosystem according to an embodiment of the invention, showing steps taken by a sender, a receiver, and a private key generator (PKG), and information communicated between them.  [0026]
FIG. 2 is a block diagram illustrating steps performed by a PKG when generating a private key according to an embodiment of the invention.  [0027]
FIG. 3 is a block diagram illustrating steps performed by a sender when computing a secret message key and using it to encrypt a message intended for a receiver according to an embodiment of the invention.  [0028]
FIG. 4 is a block diagram illustrating steps performed by a receiver when computing a secret message key and using it to decrypt ciphertext received from a sender according to an embodiment of the invention.  [0029]
FIG. 5 is a block diagram illustrating a distributed PKG, according to an embodiment of the invention.  [0030]
FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention.  [0031]
FIG. 7 is a block diagram illustrating steps performed by a sender when encrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.  [0032]
FIG. 8 is a block diagram illustrating steps performed by a receiver when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.  [0033]
FIG. 9 is a block diagram illustrating steps performed by an escrow when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an alternate embodiment of the invention.  [0034]
FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention.  [0035]
FIG. 11 is a block diagram illustrating a system with key delegation according to an embodiment of the invention.  [0036]
FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention.  [0037]The following description provides details of several exemplary embodiments of the cryptographic techniques of the present invention, as well as a technical discussion of the security of the system.
 [0000]Overview
 [0038]As is normally the case with modern cryptosystems, the techniques of the present invention are generally implemented on computers connected by a communication medium. Although typically the computers are connected by the Internet or another computer network, any communication medium may be used.
 [0039]One embodiment of the invention comprises an identitybased encryption system that uses a secret message key derived from identitybased information. The message key may be used by a sender to encrypt a message, and by a receiver to decrypt the message. The secret message key is computed by the sender from an identitybased public key of the receiver. The same message key may be computed by the receiver from the receiver's private key, which is derived from the receiver's identitybased public key. Both sender and receiver compute the same secret key using a bilinear map. For example, in one embodiment, an asymmetric or symmetric bilinear map ê: _{0}× _{1}→ _{2 }is used where _{0}, _{1}, _{2 }are (not necessarily distinct) algebraic groups. In the case where _{0 }is equal to _{1}, we say the bilinear map is symmetric and often denote it as ê: _{1}× _{1}→ _{2}. A bilinear map ê that is nondegenerate and efficiently computable will be referred to as an admissible map. It is preferable in some embodiments of the invention that the bilinear map be admissible.
 [0040]The convention throughout this description will be to denote the group operations of _{0 }and _{1 }by addition, and the group operation of _{2 }by multiplication. For a group of prime order we use * to denote the set *=\{O} where O is the identity element in the group . The set of binary strings of arbitrary length is denoted by {0, 1}*. We use _{q }to denote the group {0, . . . , q−1} under addition modulo q, and we use ^{+} to denote the set of positive integers. We note that there is a natural group action of _{q }on given by repeated addition, and we denote the result of the action of an element αε _{q }on an element Pε by aP.
 [0041]According to another embodiment of the invention, a certain variant (involving the map ê) of the computational DiffieHellman problem is hard. In one implementation the map ê is admissible and the orders of _{0}, _{1}, _{2 }have a very large prime factor q. The orders of _{0}, _{1 }and _{2 }may be equal to each other. Without loss of generality, the following description assumes for simplicity that the orders of _{0}, _{1}, and _{2 }are all of prime order q.
 [0042]In an exemplary embodiment, an admissible map ê: _{0}× _{1}→ _{2 }is used to realize an identitybased cryptosystem, as follows. To encrypt a message, a sender uses a public key Q_{ID}ε _{1 }associated with a public identifier ID for the intended receiver. To decrypt the encrypted message, the receiver uses a complementary private key d_{ID}ε _{1}. The private key is computed from the public key Q_{ID}, a secret master key sε*_{q}, and a group action of *_{q }on _{1}. In one embodiment, for example, d_{ID}=sQ_{ID}. Since the secret master key s is known only by a trusted PKG, users normally cannot themselves compute private keys. To obtain a private key, an individual may obtain it from the PKG, preferably after being authenticated. At any time, however, anyone can compute the public key Q_{ID }associated with any public identifier ID even before the corresponding private key has been determined. For example, in one embodiment the public key Q_{ID }may be obtained by (1) using a conventional character encoding scheme to map the public identifier ID to a corresponding binary string in {0, 1}*, and (2) using a hash function H_{1}: {0, 1}*→*_{1 }to hash the binary string to the element Q_{ID }of *_{1}, where the order of Q_{ID }is q.
 [0043]In this embodiment, a message intended for a receiver with public identifier ID may be encrypted and decrypted as follows. The admissible map ê may be used by the sender to determine a secret message key. Although the sender and receiver do not share all the same information, using the fact that the map ê is bilinear, they can use different information to compute the same message key. Since each uses information that is private, the message key is a secret.
 [0044]To illustrate how this approach may be implemented, suppose that the sender has knowledge of elements P and sP in _{1}. In one embodiment, for example, elements P and P_{pub}=sP in _{1 }are published system parameters. Now further suppose the sender privately selects a random rε*_{q}, and uses the receiver's identitybased public key Q_{ID }to compute g_{ID} ^{r}=ê(rQ_{ID}, sP). The element g_{ID} ^{r }is an identitybased secret which the sender may use as a secret message key to perform identitybased encryption of a message to the receiver. The sender may then send an encrypted message together with rP to the receiver. The receiver then receives rP and uses it together with the private key sQ_{ID }to compute the secret message key g_{ID} ^{r}=ê(sQ_{ID}, rP). This secret message key is equal to the secret message key computed by the sender because of the bilinearity of the ê map. This computed element g_{ID} ^{r}ε _{2 }is thus an identitybased secret of the sender which the receiver may compute using the element rP and the private key sQ_{ID}. This secret may be used as a message key for cryptographic communication between the sender and receiver.
 [0045]Note that the PKG also knows the receiver's private key, so can also compute the secret message key and decrypt the message. The sender, receiver and PKG all have sufficient information to compute the secret message key. No other entity, however, normally has knowledge of the sender's secret r or the receiver's secret sQ_{ID}. The security of this embodiment is related to the difficulty of computing the secret message key, which is based upon a combination of r, s, and Q_{ID }using a bilinear map, without knowledge of r or knowledge of sQ_{ID}.
 [0046]In one embodiment, the message key g_{ID} ^{r }is used to determine a mask which is used to encrypt and decrypt the bits of the message using an XOR operation (denoted by ‘⊕’). Specifically, the ciphertext V of a message M is produced by computing V=M⊕H_{2}(g_{ID} ^{r}), where H_{2}: _{2}→{0, 1}^{n }is a hash function, and n is the bit length of the message. Conversely, the message M is recovered from the ciphertext V by computing M=V⊕H_{2}(g_{ID} ^{r}).
 [0047]In another embodiment, the oneway encryption scheme outlined above is made more secure by converting it into a chosen ciphertext secure system. In one embodiment of the invention, for example, a general technique of FujisakiOkamoto is used.
 [0048]In another embodiment, the master key is broken into components s_{i }distributed among several private key generators in a distributed PKG. For a given user with a public key Q_{ID }based on an identifier ID, each of these private key generators in the distributed PKG computes a private key portion d_{i }using Q and its portion s_{i }of the master key. These private key portions can be combined by the user and used as a single private key d_{ID }to decrypt messages encrypted with Q_{ID}.
 [0049]In another embodiment, an ElGamal encryption scheme is provided with builtin key escrow, i.e., where one global escrow key can decrypt ciphertexts encrypted under any public key. In this embodiment, the exemplary system described above is adapted as follows. Suppose that the receiver also has knowledge of elements P and sP. Rather than obtaining a private key from the PKG, the receiver generates a public/private key pair by selecting a random xε*_{q}, computing xP using a group action, and publishing a public key based on the result of the computation. In one embodiment, the public key is xP and the complementary private key is d=x(sP). (Thus, xP plays the role of Q_{ID}, and d=x(sP)=s(xP) plays the role of d_{ID}=sQ_{ID}.) To encrypt a message to the receiver, the sender as before selects a random r and sends rP to the receiver. Then the receiver knows the pair (rP, x(sP)), where x(sP)=d is a secret, while the sender knows the pair (sP, r(xP)), where r(xP) is a secret. Thus, the sender and receiver both can compute g=e(rP, x(sP))=e(sP, r(xP)), where the second equality follows from the bilinearity of ê. This secret, however, can also be determined from knowledge of the master key s. Using the element rP from the sender, the receiver's public key xP, and the master key s, the message key can be computed by evaluating g=ê(rP, s(xP)). It should be noted that this embodiment makes use of a symmetric bilinear map ê: _{1}× _{1}→ _{2}.
 [0050]In several embodiments of the invention, _{1 }is a subgroup of an elliptic curve, and an admissible map ê is constructed from the Weil pairing (or Tate pairing) on the elliptic curve. (Recall that, by definition, a subgroup is not necessarily smaller than the group, i.e., _{1 }may be the entire elliptic curve). More generally, _{1 }may be an abelian variety and ê an admissible pairing of its elements. In embodiments using a map ê: _{0}× _{1}→G_{2 }where _{0 }and _{1 }are distinct, _{0 }also may be a subgroup of an elliptic curve, or more generally, an abelian variety.
 [0051]In other embodiments, various novel applications of identitybased encryption are provided. New and useful applications of IBE systems are possible by using other types of public identifiers, or enhanced public identifiers. For example, the public identifier ID is not limited to an identifier associated with an individual person, but may be an identifier associated with any type of entity including not just individuals but also organizations, governmental agencies, corporations and the like. It should also be noted that individual identities forming a group may be naturally combined to produce a joint identity for the group with a corresponding group private key. The group's private key need not be issued by a PKG, but is simply the combination of the separate private keys of the entities composing the group. It should be noted that the basic ID specifying the identity of an entity is not limited to the name, email address, address, or social security number of an entity, but could also include other types of information such as domain names, URLs, 9digit zip codes, tax identification numbers, and so on. In many applications, the public identifier ID will contain some character string known to the public to be uniquely associated with a particular entity or collection of entities. In general, however, the public identifier ID can be any arbitrary character string or other arbitrary information.
 [0052]Various useful applications of IBE make use of enhanced public identifiers. An enhanced identifier may comprise a type of identifier that contains information not necessarily limited to information specifying the identity of a particular entity. For example, an ID can contain a credential descriptor such as a license number, official title, or security clearance associated with an entity. An agency can then manage the credentials by providing private keys only to entities it certifies. In one exemplary embodiment, an ID can contain a property descriptor such as a serial number, vehicle identification number, patent number, or the like. An agency responsible for registering property owners and authenticating owners can manage property registration by providing private keys only to entities that it registers as true owners. More generally, an association between two or more things can be managed by including identifiers for them in an ID. The PKG then acts as the management authority for the associations between things.
 [0053]Another type of enhanced ID is an identifier that includes a time, a time interval, or a set of time intervals. A private key for such an identifier can then be constructed to automatically expire at a certain time, to automatically activate only after a certain time, or to be valid only for one or more specified time intervals. This technique can be combined with the credential and ownership management to control the time of activation and/or expiration.
 [0054]From the above examples, it is evident that an identitybased encryption systems according to the present invention are not limited to any particular type of identifier. Thus, the term ‘identitybased’ should be understood in general terms as indicating that any arbitrary character string or other arbitrary information may be used as a basis.
 [0055]According to another embodiment, an IBE system allows the delegation of decryption capabilities. An entity can set up its own IBE system with its own secret master key, and assume the role of PKG for this IBE system. Because the entity has the master key, it can issue keys to delegate decryption capabilities to others. For example, if the entity is a corporation, the employees can obtain private keys from the corporate PKG. Individuals can be issued private keys matching their names, titles, duties, projects, cases, or any other taskrelated identifier. In another example, an individual can issue to a laptop private keys that are valid only for the duration of a business trip. If the laptop is lost or stolen, only the keys for that time period are compromised. The master key, which remained at home, is uncompromised.
 [0056]It should also be pointed out that the medium of communication need not be limited to email or the Internet, but could include any communication medium such as printed publications, digital storage media, radio broadcasting, wireless communications, and so on.
 [0000]Definitions
 [0000]IdentityBased Encryption. An exemplary embodiment of an identitybased encryption system and method E uses four randomized algorithms: Setup, Extract, Encrypt, Decrypt:
 [0000]
 Setup: Given a security parameter k, return params (system parameters) and masterkey. The system parameters include a description of a finite message space , and a description of a finite ciphertext space . Normally, the system parameters will be publicly known, while the masterkey will be known only to a Private Key Generator (PKG).
 Extract: takes as input params, masterkey, and an arbitrary IDε{0, 1}*, and returns a private key d. Here ID is an arbitrary string that will be used as a public key, and d is the corresponding private decryption key. The Extract algorithm extracts a private key from the given public key. Because the extraction requires the masterkey, it is normally performed by the PKG.
 Encrypt: takes as input params, ID, and Mε. It returns a ciphertext Cε.
 Decrypt: takes as input params, Cε, and a private key d. It return Mε.
According to an embodiment of the invention, these algorithms satisfy the standard consistency constraint that ensures decryption will faithfully recover any encrypted message. More specifically, when d is the private key generated by algorithm Extract when it is given ID as the public key, then
∀Mε: Decrypt(params, C, d)=M where C=Encrypt(params, ID, M).
 [0061]In an identitybased cryptosystem according to an embodiment of the invention, the above algorithms are used together as illustrated in
FIG. 1 . A sender 100 uses Encrypt, a receiver 110 uses Decrypt, and a PKG 120 uses Setup and Extract. To send a message M to receiver 110, the sender 100 obtains an ID of the receiver (e.g., the receiver's email address) and combines it with a randomly selected integer r to compute a secret message key g_{ID} ^{r}. The element rP is sent to receiver 110 who combines it with a private key d_{ID }to determine the same message key g_{ID} ^{r}. Because the sender and receiver share the secret message key, a message encrypted with the key by the sender can be decrypted by the receiver. In particular, the sender encrypts M with the message key to produce ciphertext V which is communicated with rP to the receiver. The receiver then uses the secret message key to decrypt the ciphertext to recover the original message. In order to decrypt messages, however, the receiver 110 must first obtain the private key d_{ID }from the PKG 120. After the PKG authenticates the identity of the receiver, it provides the receiver with the private key corresponding to the receiver's ID. (Note that, in this embodiment, the PKG can compute any private key in the system, and can thus decrypt any message to any user in the system.)  [0062]Chosen ciphertext security. Chosen ciphertext security (INDCCA) is the standard acceptable notion of security for a public key encryption scheme. An embodiment of an identitybased encryption system and method may be implemented to satisfy this strong notion of security. Additionally, the selected level of chosen ciphertext security may be strengthened a bit. The reason is that when an adversary attacks a public key ID in an identitybased system, the adversary might already possess the private keys of users ID_{1}, . . . , ID_{n }of her choice. In an embodiment of the invention, the system remains secure under such an attack. That is, the system remains secure even when the adversary can obtain the private key associated with any identity ID_{i }of her choice (other than the public key ID being attacked). We refer to such queries as private key extraction queries. The system of this embodiment also remains secure even though the adversary is challenged on a public key ID of her choice (as opposed to a random public key).
 [0063]We say that an embodiment of an identitybased encryption system or method is semantically secure against an adaptive chosen ciphertext attack (INDIDCCA) if no polynomially bounded adversary A has a nonnegligible advantage against the Challenger in the following INDIDCCA game:

 Setup: The challenger takes a security parameter k and runs the Setup algorithm. It gives the adversary the resulting system parameters params. It keeps the masterkey to itself.
 Phase 1: The adversary issues queries q_{1}, . . . , q_{m }where query q_{i }is one of:
 Extraction query <ID_{i}>. The challenger responds by running algorithm Extract to generate the private key d_{i }corresponding to the public key <ID_{i}>. It sends d_{i }to the adversary.
 Decryption query <ID_{i}, C_{i}>. The challenger responds by running algorithm Extract to generate the private key d_{i }corresponding to ID_{i}. It then runs algorithm Decrypt to decrypt the ciphertext C_{i }using the private key d_{i}. It sends the resulting plaintext to the adversary.
 These queries may be asked adaptively, that is, each query q_{i }may depend on the replies to q_{1}, . . . , q_{i−1}.
 Challenge: Once the adversary decides that Phase 1 is over it outputs two equal length plaintexts M_{0}, M_{1}ε and an identity ID on which it wishes to be challenged. The only constraint is that ID did not appear in any private key extraction query in Phase 1.
 The challenger picks a random bit bε{0, 1} and sets C=Encrypt(params, ID, M_{b}). It sends C as the challenge to the adversary.
 Phase 2: The adversary issues more queries q_{m+1}, . . . , q_{n }where query q_{i }is one of:
 Extraction query <ID_{i}> where ID_{i}≠ID. Challenger responds as in Phase 1.
 Decryption query <ID_{i}, C_{i}>≠<ID, C>. Challenger responds as in Phase 1.
 These queries may be asked adaptively as in Phase 1.
 Guess: Finally, the adversary outputs a guess b′ε{0, 1}. The adversary wins the game if b=b′.
 We refer to such an adversary as an INDIDCCA adversary. We define adversary 's advantage in attacking the scheme as the following function of the security parameter k (k is given as input to the challenger):
${\mathrm{Adv}}_{\varepsilon ,\mathcal{A}}\left(k\right)=\uf603\mathrm{Pr}\left[b={b}^{\prime}\right]\frac{1}{2}\uf604.$  The probability is over the random bits used by the challenger and the adversary.
Using the INDIDCCA game we can define chosen ciphertext security for IBE schemes. As usual, we say that a function g:→ is negligible if g(k) is smaller than 1/ƒ(k) for any polynomial ƒ.
Definition 1 We say that an IBE system is semantically secure against an adaptive chosen ciphertext attack if for any polynomial time INDIDCCA adversary the function Adv_{,}(k) is negligible. As shorthand, we say that is INDIDCCA secure.

 [0078]Note that the standard definition of chosen ciphertext security (INDCCA) is the same as above except that there are no private key extraction queries and the adversary is challenged on a random public key (rather than a public key of her choice). Private key extraction queries are related to the definition of chosen ciphertext security in the multiuser settings. After all, our definition involves multiple public keys belonging to multiple users. A multiuser INDCCA may be reducible to single user INDCCA using a standard hybrid argument. This does not hold in the identitybased settings, INDIDCCA, since the adversary gets to choose which public keys to corrupt during the attack. To emphasize the importance of private key extraction queries we note that one implementation of the disclosed IBE system can be modified (by removing one of the hash functions) into a system which has chosen ciphertext security when private extraction queries are disallowed. However, the implementation is insecure when extraction queries are allowed.
 [0079]Semantically secure identity based encryption. The proof of security for an implementation of our IBE system makes use of a weaker notion of security known as semantic security (also known as semantic security against a chosen plaintext attack). Semantic security is similar to chosen ciphertext security (INDIDCCA) except that the adversary is more limited; it cannot issue decryption queries while attacking the challenge public key. For a standard public key system (not an identity based system) semantic security is defined using the following game: (1) the adversary is given a random public key generated by the challenger, (2) the adversary outputs two equal length messages M_{0 }and M_{1 }and receives the encryption of M_{b }from the challenger where b is chosen at random in {0, 1}, (3) the adversary outputs b′ and wins the game if b=b′. The public key system is said to be semantically secure if no polynomial time adversary can win the game with a nonnegligible advantage. As shorthand we say that a semantically secure public key system is INDCPA secure. Semantic security captures our intuition that given a ciphertext the adversary learns nothing about the corresponding plaintext.
 [0080]To define semantic security for identity based systems (denoted INDIDCPA) we strengthen the standard definition by allowing the adversary to issue chosen private key extraction queries. Similarly, the adversary is challenged on a public key ID of her choice. We define semantic security for identity based encryption schemes using an INDIDCPA game. The game is identical to the INDIDCCA game defined above except that the adversary cannot make any decryption queries. The adversary can only make private key extraction queries. We say that an identitybased encryption scheme is semantically secure (INDIDCPA) if no polynomially bounded adversary has a nonnegligible advantage against the Challenger in the following INDIDCPA game:

 Setup: The challenger takes a security parameter k and runs the Setup algorithm. It gives the adversary the resulting system parameters params. It keeps the masterkey to itself.
 Phase 1: The adversary issues private key extraction queries ID_{1}, . . . , ID_{m}. The challenger responds by running algorithm Extract to generate the private key d_{i }corresponding to the public key ID_{i}. It sends d_{i }to the adversary. These queries may be asked adaptively.
 Challenge: Once the adversary decides that Phase 1 is over it outputs two equal length plaintexts M_{0}, M_{1}ε and a public key ID on which it wishes to be challenged. The only constraint is that ID did not appear in any private key extraction query in Phase 1. The challenger picks a random bit bε{0, 1} and sets C=Encrypt(params, ID, M_{b}). It sends C as the challenge to the adversary.
 Phase 2: The adversary issues more extraction queries ID_{m+1}, . . . , ID_{n}. The only constraint is that ID_{i}≠ID. The challenger responds as in Phase 1.
 Guess: Finally, the adversary outputs a guess b′ε{0, 1}. The adversary wins the game if b=b′.
 We refer to such an adversary as an INDIDCPA adversary. As we did above, the advantage of an INDIDCPA adversary against the scheme is the following function of the security parameter k:
${\mathrm{Adv}}_{\varepsilon ,\mathcal{A}}\left(k\right)=\uf603\mathrm{Pr}\left[b={b}^{\prime}\right]\frac{1}{2}\uf604.$  The probability is over the random bits used by the challenger and the adversary.
Definition 2 We say that the IBE system is semantically secure if for any polynomial time INDIDCPA adversary the function Adv_{,}(k) is negligible. As shorthand, we say that is INDIDCPA secure.
One way identitybased encryption. One can define an even weaker notion of security called oneway encryption (OWE). Roughly speaking, a public key encryption scheme is a oneway encryption if given the encryption of a random plaintext the adversary cannot produce the plaintext in its entirety. Oneway encryption is a weak notion of security since there is nothing preventing the adversary from, say, learning half the bits of the plaintext. Hence, oneway encryption schemes do not generally provide secure encryption. In the random oracle model oneway encryption schemes can be used for encrypting sessionkeys (the sessionkey is taken to be the hash of the plaintext). We note that one can extend the notion of oneway encryption to identity based systems by adding private key extraction queries to the definition. We do not give the full definition here since we use semantic security as the weakest notion of security.
Bilinear Maps and the Bilinear DiffieHellman Assumption

 [0088]One embodiment of the invention is directed to an IBE system that makes use of a map ê: _{1}× _{1}→ _{2 }between groups _{1 }and _{2 }of order q for some large prime q. A map ê may be called an admissible map if it satisfies the following properties:
 1. Bilinear: The map ê: _{1}× _{1}→ _{2 }satisfies ê(aP, bQ)=ê(P, Q)^{ab }for all (P, Q)ε _{1}× _{1 }and all a, bε.
 2. Nondegenerate: The map does not send all pairs in _{1}× _{1 }to the identity in _{2}. Observe that since _{1}, _{1}, _{2 }are groups of prime order this implies that if _{1}= _{1 }and P is a generator of _{1}= _{1 }then ê(P, P) is a generator of _{2}.
 3. Computable: There is an efficient algorithm to compute ê(P, Q) for any (P, Q)ε _{1}× _{1}.
Although many of the embodiments are described with reference to a map ê: _{1}× _{1}→ _{2}, this is only a specific case of bilinear maps used in embodiments of the invention. More generally, maps ê: _{0}× _{1}→ _{2 }may be used, where _{0 }and _{1 }may be distinct. For simplicity of description, however, the description of many of the embodiments focuses primarily on the case where _{1 }and _{1 }are the same, and both groups are then denoted _{1}. Below we present a detailed exemplary embodiment using groups _{1}, _{2 }and an admissible map between them. In this exemplary embodiment, the group _{1 }is a subgroup of the additive group of points of an elliptic curve E/ _{p}, and the group _{2 }is a subgroup of the multiplicative group of a finite field *_{p} _{ 2 }. As we will see below in the detailed example of an IBE system, the Weil pairing (which is not itself an admissible map) can be used to construct an admissible map between these two groups.
 [0092]The existence of the admissible map ê: _{1}× _{1}→ _{2 }as above has two direct implications to these groups.
 The MOV reduction: The discrete log problem in _{1 }is no harder than the discrete log problem in _{2}. To see this, let P, Qε _{1 }be an instance of the discrete log problem in _{1 }where both P, Q have order q. We wish to find an aε _{q }such that Q=aP. Let g=ê(P, P) and h=ê(Q, P). Then, by bilinearity of ê we know that h=g^{a}. By nondegeneracy of ê both g, h have order q in _{2}. Hence, we reduced the discrete log problem in _{1 }to a discrete log problem in _{2}. It follows that for discrete log to be hard in _{1 }we must choose our security parameter so that discrete log is hard in _{2}.
 Decision DiffieHellman is Easy: The Decision DiffieHellman problem (DDH) in _{1 }is the problem of distinguishing between the distributions <P, aP, bP, abP> and <P, aP, bP, cP> where a, b, c are random in _{q }and P is random in _{1}. To see that DDH in _{1 }is easy, observe that given P, aP, bP, cPε*_{1 }we have
c=ab mod q ê(P, cP)=ê(aP, bP).  The Computational DiffieHellman problem (CDH) in _{1 }can still be hard (CDH in _{1 }is to find abP given random <P, aP, bP>). Exemplary embodiments may use mappings ê: _{1}× _{1}→ _{2 }where CDH in _{1 }is believed to be hard even though DDH in _{1 }is easy.
The Bilinear DiffieHellman Assumption (BDH)
 [0096]Since the Decision DiffieHellman problem (DDH) in _{1 }is easy, embodiments of the invention do not use DDH to build cryptosystems in the group _{1}. Instead, the security in embodiments of our IBE system is based on a novel variant of the Computational DiffieHellman assumption called the Bilinear DiffieHellman Assumption (BDH).
 [0097]Bilinear DiffieHellman Problem. Let _{1}, _{2 }be two groups of prime order q. Let ê: _{1}× _{1}→ _{2 }be an admissible map and let P be a generator of _{1}. The BDH problem in ( _{1}, _{2}, ê> is as follows: Given <P, aP, bP, cP> for some a, b, cε*_{q }compute W=ê(P, p)^{abc}ε _{2}. An algorithm A has advantage ε in solving BDH in < _{1}, _{2}, ê if
Pr[(P,aP,bP,cP)=ê(P,P)^{abc}]≧ε
where the probability is over the random choice of a, b, c in *_{q}, the random choice of Pε*_{1}, and the random bits of .
BDH Parameter Generator. We say that a randomized algorithm is a BDH parameter generator if (1) takes a security parameter kε ^{+}, (2) runs in polynomial time in k, and (3) outputs a prime number q, the description of two groups _{1}, _{2 }of order q, and the description of an admissible map ê: _{1}× _{1}→ _{2}. We denote the output of G by (1^{k})=<q, _{1}, _{2}, ê>. The security parameter k is used to determine the size of q; for example, one could take q to be a random kbit prime. For i=1, 2 we assume that the description of the group _{i }contains polynomial time (in k) algorithms for computing the group action in _{i }and contains a generator of _{i}. The generator of _{i }enables us to generate uniformly random elements in _{i}. Similarly, we assume that the description of ê contains a polynomial time algorithm for computing ê. We give an example of a BDH parameter generator below in the detailed example of an IBE system using the Weil pairing.
Bilinear DiffieHellman Assumption. Let be a BDH parameter generator. We say that an algorithm has advantage ε(k) in solving the BDH problem for if for sufficiently large k:$\begin{array}{c}{\mathrm{Adv}}_{\mathcal{G},\mathcal{A}}\left(k\right)=\mathrm{Pr}[\mathcal{A}\left(q,{\mathbb{G}}_{1},{\mathbb{G}}_{2},\hat{e},P,\mathrm{aP},\mathrm{bP},\mathrm{cP}\right)\\ ={\hat{e}\left(P,P\right)}^{\mathrm{abc}}\begin{array}{c}\langle q,{\mathbb{G}}_{1},{\mathbb{G}}_{2},\hat{e}\rangle \leftarrow \mathcal{G}\left({1}^{k}\right),\\ P\leftarrow {\mathbb{G}}_{1}^{*},a,b,c\leftarrow {\mathbb{Z}}_{q}^{*}\end{array}]>\epsilon \text{\hspace{1em}}\left(k\right)\end{array}$
We say that satisfies the BDH assumption if for any randomized polynomial time (in k) algorithm and for any polynomial fε[x] algorithm solves the BDH problem with advantage at most 1/ƒ(k). When satisfies the BDH assumption we say that BDH is hard in groups generated by .  [0098]In the description below of a detailed example of an IBE system we give some examples of BDH parameter generators that are believed to satisfy the BDH assumption.
 [0099]Hardness of BDH. It is interesting to study the relationship of the BDH problem to other hard problems used in cryptography. Currently, all we can say is that the BDH problem in < _{1}, _{2}, ê> is no harder than the CDH problem in _{1 }or _{2}. In other words, an algorithm for CDH in _{1 }or _{2 }is sufficient for solving BDH in ( _{1}, _{2}, ê). The converse is currently an open problem: is an algorithm for BDH sufficient for solving CDH in _{1 }or in _{2}?
 [0100]We note that in a detailed example of an IBE system below, the isomorphisms from _{1 }to _{2 }induced by the admissible map are believed to be oneway functions. More specifically, for a point Qε*_{1 }define the isomorphism ƒ_{Q: } _{1}→ _{2 }by ƒ_{Q}(P)=ê(P, Q). If any one of these isomorphisms turns out to be invertible, then BDH is easy in ( _{1}, _{2}, ê>. Fortunately, an efficient algorithm for inverting ƒ_{Q }would imply an efficient algorithm for deciding DDH in the group _{2}. In the exemplary embodiments DDH is believed to be hard in the group _{2}. Hence, the isomorphisms ƒ_{Q}: _{1 }→ _{2 }induced by the admissible map are believed to be oneway functions.
 [0000]Exemplary IdentityBased Encryption Scheme
 [0101]We describe the following exemplary embodiments in stages. First we describe a basic identitybased encryption system and method which is not secure against an adaptive chosen ciphertext attack. Another embodiment described below extends the basic scheme to get security against an adaptive chosen ciphertext attack (INDIDCCA) in the random oracle model. We later relax some of the requirements on the hash functions to provide alternative embodiments. These embodiments are described with reference to a generic BDH parameter generator satisfying the BDH assumption. Later we describe a detailed example of an IBE system using the Weil pairing.
 [0000]BasicIdent
 [0102]The following describes a basic embodiment, called BasicIdent. We present the embodiment by describing the four algorithms: Setup, Extract, Encrypt, Decrypt. We let k be the security parameter given to the setup algorithm. We let be some BDH parameter generator.
 Setup: Given a security parameter kε ^{+}, the algorithm in the basic embodiment works as follows:
 Step 1: Run on input k to generate a prime q, two groups _{1}, _{2 }of order q, and an admissible map ê: _{1}× _{1}→ _{2}. Choose an arbitrary generator Pε _{1}.
 Step 2: Pick a random sε*_{q }and set P_{pub}=sP.
 Step 3: Choose a cryptographic hash function H_{1}: {0, 1}*→*_{1}. Choose a cryptographic hash function H_{2}: _{2}→{0, 1}^{n }for some n. The security analysis will view H_{1}, H_{2 }as random oracles.
 The message space is ={0, 1}^{n}. The ciphertext space is =*_{1}×{0, 1}^{n}. The system parameters are params=<q, _{1}, _{2}, ê, n, P, P_{pub}, H_{1}, H_{2}>. The masterkey is sε*_{q}. Embodiments of the IBE system may be used to encrypt a symmetric key, in which case one may take n to be, for example, 128 or 256. For k one may use, for example, 512 or 1024 or 2048.
 Extract: For a given string IDε{0, 1}* the algorithm in the basic embodiment does: (1) computes Q_{ID}=H_{1}(ID)ε*_{1}, and (2) sets the private key d_{ID }to be d_{ID}=sQ_{ID }where s is the master key.
 Extract may be performed by a PKG in various embodiments as illustrated in
FIG. 2 . The PKG obtains the master key in block 200, obtains the public identifier ID in block 210, computes the public key from the ID in block 220, then computes the private key from the master key and the public key in block 230. In block 240 the private key is then sent to an entity associated with the public identifier ID, normally after the entity's identity has been authenticated.
 Extract may be performed by a PKG in various embodiments as illustrated in
 Encrypt: To encrypt Mε under the public key ID do the following: (1) compute Q_{ID}=H_{1}(ID)ε*_{1}, (2) choose a random rε*_{q}, and (3) set the ciphertext to be
C=<rP,M⊕H _{2}(g _{ID} ^{r})> where g _{ID} =ê(Q _{ID} ,P _{pub})ε*_{2}. In the basic embodiment, the sender of a message may perform Encrypt as illustrated in
FIG. 3 . In block 300 the system parameters are obtained (from an external resource such as a PKG, or from a local storage medium if they were obtained previously). A receiver's ID is determined in block 310, and the corresponding public key is computed from the ID in block 320. Then the secret message key is computed in block 330, and the message key is used to encrypt the message in block 340.
 In the basic embodiment, the sender of a message may perform Encrypt as illustrated in
 Decrypt: Let C=<U, V>εC be a ciphertext encrypted using the public key ID. To decrypt C using the private key d_{ID}ε*_{1 }compute:
V⊕H _{2}(ê(d _{ID} ,U))=M. In the basic embodiment, the receiver may perform Decrypt as illustrated in
FIG. 4 . In block 400, the system parameters are obtained (from an external resource such as a PKG, or from a local storage medium if they were obtained previously). The ciphertext V and an element rP are obtained from the sender in block 410. The element rP may be considered a portion of the total ciphertext obtained from the sender. In block 420 the receiver obtains the private key d_{ID }corresponding to the public identifier ID used to encrypt the message. The private key is normally obtained from an external resource such as a PKG, or from a local storage medium if it was obtained previously. The secret message key is then computed in block 430, and used to decrypt the message in block 440.
This completes the description of BasicIdent for the basic embodiment. We first verify consistency. When everything is computed as above we have:
1. During encryption M is bitwise exclusiveored with the hash of: g_{ID} ^{r}.
2. During decryption V is bitwise exclusiveored with the hash of: ê(d_{ID}, U).
These masks used during encryption and decryption are the same since:
ê(d _{ID} ,U)=ê(sQ _{ID} ,rP)=ê(Q _{ID} ,p)^{st} =ê(Q _{ID} ,P _{pub})^{r} =g _{ID} ^{r }
Thus, applying decryption after encryption produces the original message M as required. Performance considerations of BasicIdent are discussed later.
 In the basic embodiment, the receiver may perform Decrypt as illustrated in
 Security. Next, we study the security of this basic embodiment.
 Setup: Given a security parameter kε ^{+}, the algorithm in the basic embodiment works as follows:
 [0115]The security of the exemplary system is based on the assumption that a variant of the Computational DiffieHellman problem in _{1 }is hard. The technical security details of the encryption scheme are discussed by the inventors in D. Boneh, M. Franklin, “Identity based encryption from the Weil pairing”, extended abstract in Advances in Cryptology—Crypto 2001, Lecture Notes in Computer Science, Vol. 2139, SpringerVerlag, pp. 231229, 2001, which is incorporated herein by reference.
 [0116]In an exemplary embodiment, the performance of the system is comparable to the performance of ElGamal encryption in *_{p}. The security of the exemplary system is based on a variant of the computational DiffieHellman assumption. Based on this assumption we show that the exemplary system has chosen ciphertext security in the random oracle model. In accordance with a distributed PKG embodiment, threshold cryptography techniques allow the PKG to be distributed so that the masterkey is never available in a single location. Unlike common threshold systems, we show that robustness for the distributed PKG embodiment is free.
 [0117]To argue about the security of the exemplary system, we define chosen ciphertext security for identitybased encryption. Our model gives the adversary more power than the standard model for chosen ciphertext security. First, we allow the attacker to attack an arbitrary public key ID of her choice. Second, while mounting a chosen ciphertext attack on ID we allow the attacker to obtain from the PKG the private key for any public key of her choice, other than the private key for ID. This models an attacker who obtains a number of private keys corresponding to some identities of her choice and then tries to attack some other public key ID of her choice. Even with the help of such queries, it is desirable that the attacker still have negligible advantage in defeating the semantic security of the system.
 [0118]The following theorem shows that BasicIdent is a semantically secure identity based encryption scheme (INDIDCPA) assuming BDH is hard in groups generated by .
Theorem 1 Suppose the hash functions H_{1}, H_{2 }are random oracles. Then BasicIdent is a semantically secure identity based encryption scheme (INDIDCPA) assuming BDH is hard in groups generated by . Concretely, suppose there is an INDIDCPA adversary that has advantage ε(k) against the scheme BasicIdent. Suppose makes at most q_{E}>0 private key extraction queries and q_{H} _{ 2 }>0 hash queries to H_{2}. Then there is an algorithm that solves BDH in groups generated by with advantage at least:${\mathrm{Adv}}_{\mathcal{G},\mathcal{B}}\left(k\right)\ge \frac{2\epsilon \left(k\right)}{e\left(1+{q}_{E}\right)\xb7{q}_{{H}_{2}}}$
Here e≈2.71 is the base of the natural logarithm. The running time of is O(time()).  [0119]To prove the theorem we first define a related Public Key Encryption scheme (not an identity based scheme), called BasicPub. BasicPub is described by three algorithms: keygen, encrypt, decrypt.
 keygen: Given a security parameter kε ^{+}, the algorithm works as follows:
 Step 1: Run on input k to generate two prime order groups _{1}, _{2 }and an admissible map ê: _{1}× _{1}→ _{2}. Let q be the order of _{1}, _{2}. Choose an arbitrary generator Pε _{1}.
 Step 2: Pick a random sε*_{q }and set P_{pub}=sP. Pick a random Q_{ID}ε*_{1}.
 Step 3: Choose a cryptographic hash function H_{2}: _{2}{0, 1}^{n }for some n.
 Step 4: The public key is <q, _{1}, _{2}, ê, n, P, P_{pub}, Q_{ID}, H_{2}>. The private key is d_{ID}=sQ_{ID}ε*_{1}.
 encrypt: To encrypt Mε{0, 1}^{n }choose a random rε*_{q }and set the ciphertext to be:
C=<rP,M⊕H _{2}(g ^{r})> where g=ê(Q _{ID} ,P _{pub})ε*_{2 }  decrypt: Let C=<U, V> be a ciphertext created using the public key <q, _{1}, _{2}, ê, n, P, P_{pub}, Q_{ID}, H_{2}>. To decrypt C using the private key d_{ID}ε*_{1 }compute:
V⊕H _{2}(ê(d _{ID} ,U))=M
This completes the description of BasicPub. We now prove Theorem 1 in two steps. We first show that an INDIDCPA attack on BasicIdent can be converted to a INDCPA attack on BasicPub. This step shows that private key extraction queries do not help the adversary. We then show that BasicPub is INDCPA secure if the BDH assumption holds. The proofs are omitted.
Lemma 2 Let H_{1 }be a random oracle from {0, 1}* to *_{1}. Let be an INDIDCPA adversary that has advantage ε(k) against BasicIdent. Suppose makes at most q_{E}>0 private key extraction queries. Then there is a INDCPA adversary that has advantage at least ε(k)/e(1+q_{E}) against BasicPub. Its running time is O(time()).
Lemma 3 Let H_{2 }be a random oracle from _{2 }to {0, 1}^{n}. Let be an INDCPA adversary that has advantage ε(k) against BasicPub. Suppose makes a total of q_{H} _{ 2 }>0 queries to H_{2}. Then there is an algorithm that solves the BDH problem for with advantage at least 2ε(k)/q_{H} _{ 2 }and a running time O(time()).
Proof of Theorem 1. The theorem follows directly from Lemma 2 and Lemma 3. Composing both reductions shows that an INDIDCPA adversary on BasicIdent with advantage ε(k) gives a BDH algorithm for G with advantage at least 2ε(k)/e(1+q_{E})q_{H} _{ 2 }, as required.
IdentityBased Encryption with Chosen Ciphertext Security
 keygen: Given a security parameter kε ^{+}, the algorithm works as follows:
 [0127]According to one embodiment of the invention, a technique of Fujisaki and Okamoto (described in E. Fujisaki and T. Okamoto, “Secure integration of asymmetric and symmetric encryption schemes”, in Advances in Cryptology—Crypto '99, Lecture Notes in Computer Science, Vol. 1666, SpringerVerlag, pp. 537554, 1999, which is incorporated herein by reference) may be appropriately adapted to convert the BasicIdent embodiment of the previous section into a chosen ciphertext secure embodiment of an IBE system (in the sense defined earlier) in the random oracle model. Let be a probabilistic public key encryption scheme. We denote by _{pk}(M; r) the encryption of M using the random bits r under the public key pk. FujisakiOkamoto define the hybrid scheme ^{hy }as:
_{pk} ^{hy}(M)=< _{pk}(σ;H _{3}(σ,M)),H _{4}(σ)⊕M>
Here σ is generated at random and H_{3}, H_{4 }are cryptographic hash functions. FujisakiOkamoto show that if is a oneway encryption scheme then ^{hy }is a chosen ciphertext secure system (INDCCA) in the random oracle model (assuming _{pk }satisfies some natural constraints). We note that semantic security implies oneway encryption and hence the FujisakiOkamoto result also applies if is semantically secure (INDCPA).  [0128]We apply the FujisakiOkamoto transformation to BasicIdent and show that the resulting embodiment of an IBE system is INDIDCCA secure. We obtain the following IBE embodiment which we call FullIdent. Recall that n is the length of the message to be encrypted.
 Setup: As in the BasicIdent scheme. In addition, we pick a hash function H_{3}: {0, 1}^{n}×{0, 1}^{n}→*_{q}, and a hash function H_{4}: {0, 1}^{n}→{0, 1}^{n}.
 Extract: As in the BasicIdent scheme.
 Encrypt: To encrypt Mε{, 1}^{n }under the public key ID do the following: (1) compute Q_{ID}=H_{1}(ID)ε*_{1}, (2) choose a random σε{0, 1}^{n}, (3) set r=H_{3}(σ, M), and (4) set the ciphertext to be
C=<rP,σ⊕H _{2}(g _{ID} ^{r}), M⊕(H_{4}(σ)> where g _{ID} =ê(Q _{ID} ,P _{pub})ε _{2 }  Decrypt: Let C=<U, V, W> be a ciphertext encrypted using the public key ID. If U≠*_{1 }reject the ciphertext. To decrypt C using the private key d_{ID}ε*_{1 }do:
 1. Compute V⊕H_{2}(ê(d_{ID}, U))=σ.
 2. Compute W⊕H_{4}(σ)=M.
 3. Set r=H_{3}(σ, M). Test that U=rP. If not, reject the ciphertext.
 4. Output M as the decryption of C.
This completes the description of FullIdent. Its implementation follows the same basic pattern as BasicIdent shown inFIGS. 2, 3 , 4. Note that M is encrypted as W=M⊕H_{4}(σ). This can be replaced by W=E_{H} _{ 4 } _{(σ)}(M) where E is a semantically secure symmetric encryption scheme.
 Security. The following theorem shows that FullIdent is a chosen ciphertext secure IBE (i.e. INDIDCCA), assuming BDH is hard in groups generated by .
Theorem 4 Let the hash functions H_{1}, H_{2}, H_{3}, H_{4 }be random oracles. Then FullIdent is a chosen ciphertext secure IBE (INDIDCCA) assuming BDH is hard in groups generated by .
Concretely, suppose there is an INDIDCCA adversary that has advantage ε(k) against the scheme FullIdent and runs in time at most t(k). Suppose makes at most q_{E }extraction queries, at most q_{D }decryption queries, and at most q_{H} _{ 2 }, q_{H} _{ 3 }, q_{H} _{ 4 }queries to the hash functions H_{2}, H_{3}, H_{4 }respectively. Then there is a BDH algorithm for with running time t_{1}(k) where:${\mathrm{Adv}}_{\mathcal{G},\mathcal{B}}\left(k\right)\ge 2\text{\hspace{1em}}{\mathrm{FO}}_{\mathrm{adv}}\left(\frac{\epsilon \left(k\right)}{e\left(1+{q}_{E}+{q}_{D}\right)},{q}_{{H}_{4}},{q}_{{H}_{3}},{q}_{D}\right)/{q}_{{H}_{2}}$ ${t}_{1}\left(k\right)\le {\mathrm{FO}}_{\mathrm{time}}\left(t\left(k\right),{q}_{{H}_{4}},{q}_{{H}_{3}}\right)$
where the functions FO_{time }and FO_{adv }are defined in Theorem 5.
 [0138]The proof of Theorem 4 is based on the following result of Fujisaki and Okamoto. Let BasicPub^{hy }be the result of applying the FujisakiOkamoto transformation to BasicPub.
Theorem 5 (FujisakiOkamoto) Suppose is an INDCCA adversary that achieves advantage ε(k) when attacking BasicPub^{hy}. Suppose has running time t(k), makes at most q_{D }decryption queries, and makes at most q_{H} _{ 3 }, q_{H} _{ 4 }queries to the hash functions H_{3}, H_{4 }respectively. Then there is an INDCPA adversary against BasicPub with running time t_{1}(k) and advantage ε_{1}(k) where$\begin{array}{c}{\epsilon}_{1}\left(k\right)\ge {\mathrm{FO}}_{\mathrm{adv}}\left(\epsilon \left(k\right),{q}_{{H}_{4}},{q}_{{H}_{3}},{q}_{D}\right)\\ =\frac{1}{2\left({q}_{{H}_{4}}+{q}_{{H}_{3}}\right)}\left[\left(\epsilon \left(k\right)+1\right){\left(12/q\right)}^{{q}_{D}}1\right]\end{array}$ $\begin{array}{c}{t}_{1}\left(k\right)\le {\mathrm{FO}}_{\mathrm{time}}\left(t\left(k\right),{q}_{{H}_{4}},{q}_{{H}_{3}}\right)\\ =t\left(k\right)+O\left(\left({q}_{{H}_{4}}+{q}_{{H}_{3}}\right)\xb7n\right),\end{array}$
Here q is the size of the groups _{1}, _{2 }and n is the length of σ.  [0139]In fact, FujisakiOkamoto prove a stronger result: Under the hypothesis of Theorem 5, BasicPub^{hy }would not even be a oneway encryption scheme. For our purposes the result in Theorem 5 is sufficient. To prove Theorem 4 we also need the following lemma to translate between an INDIDCCA chosen ciphertext attack on FullIdent and an INDCCA chosen ciphertext attack on BasicPub^{hy}.
Lemma 6 Let A be an INDIDCCA adversary that has advantage ε(k) against FullIdent. Suppose makes at most q_{E}>0 private key extraction queries and at most q_{D }decryption queries. Then there is an INDCCA adversary that has advantage at least$\frac{\epsilon \left(k\right)}{e\left(1+{q}_{E}+{q}_{D}\right)}$
against BasicPub^{hy}. Its running time is O(time()).
Proof of Theorem 4. By Lemma 6 an INDIDCCA adversary on FullIdent implies an INDCCA adversary on BasicPub^{hy}. By Theorem 5 an INDCCA adversary on BasicPub^{hy }implies an INDCPA adversary on BasicPub. By Lemma 3 an INDCPA adversary on BasicPub implies an algorithm for BDH. Composing all these reductions gives the required bounds. □  [0140]Relaxing the Hashing Requirements
 [0141]Recall that an IBE system of Section uses a hash function H_{1}: {0, 1}*→*_{1}. The detailed example of an IBE system presented in the next section uses _{1 }as a subgroup of the group of points on an elliptic curve. In practice, it sometimes can be difficult to build hash functions that hash directly onto such groups. In an exemplary embodiment, we therefore show how to relax the requirement of hashing directly onto *_{1}. Rather than hash onto *_{1 }we hash onto some set A⊂{0, 1}* and then use a deterministic encoding function to map A onto *_{1}.
 [0000]
 [0000]
 1. Computable: There is an efficient deterministic algorithm to compute L(z) for any xεA.
 2. lto1: For any yε*_{1 }the preimage of y under L has size exactly l. In other words, L^{−1}(y)=l for all yε*_{1}. Note that this implies that A=l·*_{1}.
 3. Samplable: There is an efficient randomized algorithm _{s }such that _{s}(y) induces a uniform distribution on L^{−1}(y) for any yε*_{1}. In other words, _{s}(y) is a uniform random element in L^{−1}(y).
We modify FullIdent to obtain an INDIDCCA secure embodiment of an IBE system where H_{1 }is replaced by a hash function into some set A. Since the change is relatively minor we refer to this new scheme as FullIdent:  Setup: As in the FullIdent embodiment. The only difference is that H_{1 }is replaced by a hash function H′_{1}: {0, 1}*→A. The system parameters also include a description of an admissible encoding function L: A→*_{1}.
 Extract, Encrypt: As in the FullIdent embodiment. The only difference is that in Step 1 these algorithms compute Q_{ID}=L(H′_{1}(ID))ε*_{1}.
 Decrypt: As in the FullIdent embodiment.
This completes the description of FullIdent′. The following theorem shows that FullIdent′ is a chosen ciphertext secure IBE (i.e. INDIDCCA), assuming FullIdent is.
Theorem 7 Let be an INDIDCCA adversary on FullIdent′ that achieves advantage ε(k). Suppose makes at most q_{H} _{ 1 }queries to the hash function H′_{1}. Then there is an INDIDCCA adversary on FullIdent that achieves the same advantage ε(k) and time()=time()+q_{H} _{ 1 }·time(L_{s})
Proof Sketch Algorithm attacks FullIdent by running algorithm . It relays all decryption queries, extraction queries, and hash queries from directly to the challenger and relays the challenger's response back to . It only behaves differently when issues a hash query to H′_{1}. Recall that only has access to a hash function H_{1}: {0, 1}*→*_{1}. To respond to H′_{1 }queries algorithm maintains a list of tuples <ID_{j}, y_{j}> as explained below. We refer to this list as the (H′_{1})^{list}. The list is initially empty. When queries the oracle H′_{1 }at a point ID_{i }algorithm responds as follows:  1. If the query ID_{i }already appears on the (H′_{1})^{list }in a tuple <ID_{i}, y_{i}> then respond with H′_{1}(ID_{i})=y_{i}εA.
 2. Otherwise, issues a query for H_{1}(ID_{i}). Say, H_{1}(ID_{i})=αε*_{1}.
 3. runs the sampling algorithm _{s}(α) to generate a random element yεL^{−1}(α).
 4. adds the tuple <ID_{i}, y> to the (H′_{1})^{list }and responds to with H′_{1}(ID_{i})=yεA. Note that y is uniformly distributed in A as required since α is uniformly distributed in *_{1 }and L is an lto1 map.
Algorithm 's responses to all of 's queries, including H′_{1 }queries, are identical to 's view in the real attack. Hence, will have the same advantage ε(k) in winning the game with the challenger.
A Detailed Example of an IBE System Using the Weil Pairing
 [0152]In this section we use FullIdent′ to describe a detailed example of an embodiment of an IBE system. This embodiment is based on the Weil pairing. Although in practice the Tate pairing has computational advantages and may be used instead of the Weil pairing in various embodiments, the implementation using the Weil pairing will be described first because it is simpler. Later, the Tate pairing will be discussed.
 [0000]Properties of the Weil Pairing
 [0153]Let p>3 be a prime satisfying p=2 mod 3 and let q be some prime factor of p+1. Let E be the elliptic curve defined by the equation y^{2}=x^{3}+1 over _{p}. We state a few elementary facts about this curve E. From here on we let E( _{p} _{ r }) denote the group of points on E defined over _{p} _{ r }.
 Fact 1: Since x^{3}+1 is a permutation on _{p }it follows that the group E( _{p}) contains p+1 points. We let O denote the point at infinity. Let PεE( _{p}) be a point of order q and let _{1 }be the subgroup of points generated by P.
 Fact 2: For any y_{0}ε _{p }there is a unique point (x_{0}, y_{0}) on E( _{p}), namely x_{0}=(y_{0} ^{2}−1)^{1/3}ε _{p}. Hence, if (x, y) is a random nonzero point on E( _{p}) then y is uniform in _{p}. We use this property to build a simple admissible encoding function.
 Fact 3: Let 1≠ζε _{p} _{ 2 }be a solution of x^{3}−1=0 mod p. Then the map φ(x, y)=(ζx, y) is an automorphism of the group of points on the curve E. Note that for any point Q=(x, y)εE( _{p}) we have that φ(Q)εE( _{p} _{ 2 }), but φ(Q)εE( _{p}). Hence, QεE( _{p}) is linearly independent of φ(Q)εE _{p} _{ 2 }).
 Fact 4: Since the points Pε _{1 }and φ(P) are linearly independent they generate a group isomorphic to _{q}× _{q}. We denote this group of points by E[q].
Let _{2 }be the subgroup of *_{p} _{ 2 }of order q. The Weil pairing on the curve E( _{p} _{ 2 }) is a mapping e: E[q]×E[q]→ _{2}. (This map is defined and discussed in the section below entitled Description of the Weil Pairing.) For any Q, RεE( _{p}) the Weil pairing satisfies e(Q, R)=1. In other words, the Weil pairing is degenerate on E( _{p}), and hence degenerate on the group _{1}. To get a nondegenerate map we define the modified Weil pairing ê: _{1}× _{1}→ _{2 }as follows:
ê(P,Q)=e(P,φ(Q))
The modified Weil pairing satisfies the following properties:  1. Bilinear: For all P, Qε _{1 }and for all a, bε we have ê(aP, bQ)=ê(P, Q)^{ab}.
 2. Nondegenerate: If P is a generator of _{1 }then ê(P, P)ε*_{p} _{ 2 }is a generator of _{2}.
 3. Computable: Given P, Qε _{1 }there is an efficient algorithm to compute ê(P, Q)ε _{2}. (This algorithm is described in the section below entitled Description of the Weil Pairing.) Its running time is comparable to exponentiation in _{p}.
Although the Computational DiffieHellman problem (CDH) appears to be hard in the group _{1}, the Decision DiffieHellman problem (DDH) is easy in _{1}.
BDH Parameter Generator _{1}: Given a security parameter 2<kεthe BDH parameter generator picks a random kbit prime q and finds the smallest prime p such that (1) p=2 mod 3, (2) q divides p+1, and (3) q^{2 }does not divide p+1. We write p=lq+1. The group _{1 }is the subgroup of order q of the group of points on the curve y^{2}=x^{3}+1 over _{p}. The group _{2 }is the subgroup of order q of *_{p} _{ 2 }. The bilinear map ê: _{1}× _{1}→ _{2 }is the modified Weil pairing defined above.
 [0161]The BDH parameter generator _{1 }is believed to satisfy the BDH assumption asymptotically. However, there is still the question of what values of p and q can be used in practice to make the BDH problem sufficiently hard. It is desirable that we can ensure, at the very least, that the discrete log problem in _{1 }is sufficiently hard. As pointed out earlier, the discrete log problem in _{1 }is efficiently reducible to discrete log in _{2}. Hence, computing discrete log in *_{p} _{ 2 }is sufficient for computing discrete log in _{1}. In practice, for proper security of discrete log in *_{p} _{ 2 }it is desirable to use primes p that are at least 512bits long (so that the group size is at least 1024 bits long). Consequently, in some embodiments, this BDH parameter generator is used with primes p that may be 512bits long or more.
 [0000]An Admissible Encoding Function: MapToPoint
 [0162]Let _{1}, _{2 }be two groups generated by _{1 }as defined above. Recall that an IBE system discussed earlier uses a hash function H_{1}: {0, 1}*→*_{1}. It suffices to have a hash function H_{1}: {0, 1}*→A for some set A, and an admissible encoding function L: A→*_{1}. In what follows the set A will be _{p}, and the admissible encoding function L will be called MapToPoint, which may be used in various embodiments of the present invention.
 [0163]In this example, let p be a prime satisfying p=2 mod 3 and p=lq−1 for some prime q>3. In this exemplary embodiment, q does not divide l (i.e. q^{2 }does not divide p+1). Let E be the elliptic curve y^{2}=x^{3}+1 over _{p}. Let _{1 }be the subgroup of points on E of order q. In addition, a hash function H_{1}: {0, 1}*→ _{p }is provided.
 [0000]
 [0000]
 [0000]
 [0000]3. Output MapToPoint (y_{0})=Q_{ID}.
 [0000]This completes the description of MapToPoint.
 [0164]We note that there are l−1 values of y_{0}ε _{p }for which lQ=l(x_{0}, y_{0})=O (these are the nonO points of order dividing l). Let B⊂ _{p }be the set of these y_{0}. When H_{1}(ID) is one of these l−1 values Q_{ID }is the identity element of _{1}. It is extremely unlikely for H_{1}(ID) to hit one of these points—the probability is 1/{dot over (q)}<½^{k}. Hence, for simplicity we say that H_{1}(ID) only outputs elements in _{p}\B, i.e. H_{1}: {0, 1}*→ _{p}\B. In other embodiments, algorithm MapToPoint can be easily extended to handle the values y_{0}εB by hashing ID multiple times using different hash functions.
 [0000]
 [0165]Proof The map is clearly computable and is a lto1 mapping. It remains to show that L is samplable. Let P be a generator of E( _{p}). Given a Qε*_{1 }the sampling algorithm _{s }does the following: (1) pick a random bε{0, . . . , l−1}, (2) compute Q′=l^{−1}·Q+bqP=(x, y), and (3) output _{s}(Q)=yε _{p}. Here l^{−1 }is the inverse of l in *_{q}. This algorithm outputs a random element from the l elements in MapToPoint^{−1}(Q) as required. □
 [0000]A Detailed Example of an IBE System
 [0166]Using the BDH parameter generator _{1 }and the admissible encoding function MapToPoint we obtain the following detailed example of an embodiment of an IBE system.
 Setup: Given a security parameter kε ^{+}, the algorithm works as follows:
 Step 1: Run _{1 }on input k to generate a kbit prime q and a prime p=2 mod 3 such that q divides p+1. Let E be the elliptic curve defined by y^{2}=x^{3}+1 over _{p}. Choose an arbitrary PεE( _{p}) of order q.
 Step 2: Pick a random sε*_{q }and set P_{pub}=sP.
 Step 3: Pick four hash functions: H_{1}: {0, 1}*→ _{p}; H_{2}: _{p} _{ 2 }→{0, 1}^{n }for some n H_{3}: {0, 1}^{n}×{0, 1}^{n}→*_{q}, and a hash function H_{4}: {0, 1}^{n}→{0, 1}^{n}.
 The message space is ={0, 1}^{n}. The ciphertext space is =E( _{p})×{0, 1}^{n}. The system parameters are params=<p, q, n, P, P_{pub}, H_{1}, . . . , H_{4}>. The masterkey is sε*_{q}.
 Extract: For a given string IDε{0, 1}* the algorithm builds a private key d as follows:
 Step 1: Compute MapToPoint(H_{1}(ID))=Q_{ID}εE( _{p}) of order q.
 Step 2: Set the private key d_{ID }to be d_{ID}=sQ_{ID }where s is the master key.
 Encrypt: To encrypt Mε{0, 1}^{n }under the public key ID do the following:
 Step 1: Compute MapToPoint(H_{1}(ID))=Q_{ID}εE( _{p}) of order q.
 Step 2: Choose a random σε{0, 1}^{n}.
 Step 3: Set r=H_{3}(σ, M).
 Step 4: Set the ciphertext to be
C=<rP,σ⊕H _{2}(g _{ID} ^{r}),M⊕H _{4}(σ)> where g _{ID} =ê(Q _{ID} ,P _{pub})ε _{p} _{ 2 }
 Decrypt: Let C=<U, V, W>ε be a ciphertext encrypted using the public key ID. If UεE( _{p}) is not a point of order q reject the ciphertext. To decrypt C using the private key d_{ID }do:
Step 1. Compute V⊕H_{2}(ê(d_{ID}, U))=σ.
Step 2. Compute W⊕(H_{4}(σ)=M.
Step 3. Set r=H_{3}(σ, M). Test that U=rP. If not, reject the ciphertext.
Step 4. Output M as the decryption of C.
Performance. In this embodiment, algorithms Setup and Extract are very simple. At the heart of both algorithms is a standard multiplication on the curve E( _{p}). Algorithm Encrypt requires that the encryptor compute the Weil pairing of Q_{ID }and P_{pub}. Note that this computation is independent of the message, and hence can be done once and for all. Once g_{ID }is computed the performance of this embodiment is almost identical to standard ElGamal encryption. We also note that the ciphertext length of the exemplary embodiment of BasicIdent is the same as in regular ElGamal encryption in _{p}. Decryption is a simple Weil pairing computation.
Security. The security of the detailed exemplary embodiment just described follows directly from Theorem 4 and Theorem 7.
Corollary 9 The detailed exemplary embodiment described above is a chosen ciphertext secure IBE system (i.e. INDIDCCA in the random oracle model) assuming the BDH parameter generator _{1 }satisfies the BDH assumption.
Extensions and Observations
Tate Pairing and Other Curves.
 Setup: Given a security parameter kε ^{+}, the algorithm works as follows:
 [0181]Embodiments of our IBE system work with efficiently computable bilinear maps ê: _{1}× _{1}→ _{2 }between two groups _{1}, _{2 }where the BDH assumption holds. Many different elliptic curves may give rise to such maps. For example, one could use the curve y^{2}=x^{3}+x over _{p }with p=3 mod 4 and its endomorphism φ: (x, y)→(−x, iy) where i^{2}=−1.
 [0182]In an alternative embodiment, one may use a family of nonsupersingular elliptic curves over _{p }discussed by Miyaji et al. (A. Miyaji, M. Nakabayashi, S. Takano, “New explicit condition of elliptic curve trace for FRreduction”, IEICE Trans. Fundamentals, Vol. E84 A, No. 5, May 2001). For example, to use a curve E/ _{p }in this family one can take _{1 }to be a cyclic subgroup of E( _{p} _{ 6 }) (that is not contained in E( _{p})) and then use the trace map on the curve E as the endomorphism φ used to define the pairing ê. We also note that both encryption and decryption in FullIdent can be made faster in alternate embodiments by using the Tate pairing on elliptic curves rather than the Weil pairing. In other embodiments, suitable bilinear maps may be derived from abelian varieties.
 [0000]Asymmetric Pairings
 [0183]As mentioned earlier, embodiments of our IBE system are not limited to symmetric maps, but may include asymmetric maps as well. In other words, embodiments generally may use maps of the form ê: _{0}× _{1}→ _{2 }where _{0}, _{1 }are groups of prime order q. When _{0 }and are equal we say the map is symmetric. When _{0 }and _{1 }are not equal we say the map is asymmetric.
 [0184]The elements Q_{ID }and P in the asymmetric case are members of _{0 }and _{1}, respectively (or vice versa), and the target group of the hash function H_{1 }is selected accordingly. However, to make the proof of security go through (Lemma 2 in particular) we use a slightly strange looking complexity assumption which we call the coBDH assumption: given random P, aP, bPε _{1 }and Q, aQ, cQε _{0 }no polynomial time algorithm can compute ê(P, Q)^{abc }with nonnegligible probability. If one is uses this assumption then for embodiments using a curve E/ _{p }from Miyaji et al. (as just described above) one can take _{1 }to be a cyclic subgroup of E( _{p}) of order q and _{0 }to be a different cyclic subgroup of E( _{p} _{ 6 }) of order q. This will result in a more efficient system than the method described in the preceding paragraph for using these curves.
 [0000]Distributed PKG
 [0185]In exemplary embodiments of an IBE system it is desirable that the masterkey stored at the PKG be protected. One way of protecting this key is by distributing it among different sites using techniques of threshold cryptography. Embodiments of our IBE system support this in a very efficient and robust way. Recall that in some embodiments discussed above, the masterkey may be some sε*_{q }and the PKG uses the group action to compute a private key from s and Q_{ID}, where Q_{ID }is derived from the user's public key ID. For example, d_{ID}=sQ_{ID}. A distributed PKG embodiment can be implemented in a toutofn fashion by giving each of the n PKGs one share s_{i }of a Shamir secret sharing of s mod q. Each of the n PKGs can use its share s_{i }of the master key to generate a corresponding share d_{i }of a private key d_{ID }by calculating d_{i}=s_{i}Q_{ID}. The user can then construct the entire private key d_{ID }by requesting from t of the n PKGs its share d_{i }of the private key, then combining the shares by calculating
${d}_{\mathrm{ID}}=\sum _{i}{\lambda}_{i}{d}_{i},$
where the λ_{i}'s are the appropriate Lagrange interpolation coefficients.  [0186]Furthermore, it is easy to make this embodiment robust against dishonest PKGs using the fact that DDH is easy in _{1}. During setup each of the n PKGs publishes P_{i}=s_{i}P. During a key generation request the user can verify that the response from the i'th PKG is valid by testing that:
ê(d _{i} ,P)=ê(Q _{ID} ,P _{i})
Thus, a misbehaving PKG will be immediately caught. There is no need for zeroknowledge proofs as in regular robust threshold schemes. The PKG's masterkey can be generated in a distributed fashion using the techniques of R. Gennaro et al. (R. Gennaro, S. Jarecki, H. Krawczyk, T. Rabin, “Secure Distributed Key Generation for DiscreteLog Based Cryptosystems”, Advances in Cryptology—Eurocrypt '99, Lecture Notes in Computer Science, Vol. 1592, SpringerVerlag, pp. 295310, 1999). Using this technique, the PKGs can execute a cooperative protocol that allows them to jointly generate their respective shares of the master key without the master key ever existing in any one place.  [0187]Note that a distributed masterkey embodiment also enables threshold decryption on a permessage basis, without any need to derive the corresponding decryption key. For example, threshold decryption of BasicIdent ciphertext (U, V) is straightforward if each PKG responds with ê(s_{i}Q_{ID}, U).
 [0188]
FIG. 5 is a block diagram illustrating a distributed PKG system, according to an embodiment of the invention.FIG. 5 includes a sender system 501, receiver system 502 and three PKGs (PKG A 503, PKG B 504 and PKG C 505). In one embodiment illustrating a 2outof3 sharing, each of three PKGs contains a different share of a master key, and any two of the three are able to derive the master key. As shown in the figure, PKG A 503, PKG B 504, and PKG C 505 include, respectively, master key share s_{1}, 511, master key share 52, 512, and master key share s_{3}, 513. In 2outof3 sharing, any two out of these three PKGs could combine their shares to determine the master key, although in this embodiment each PKG secretly holds its master key share.  [0189]Sender system 501 sends a message to receiver 502. The message 514 may be encrypted using a public key based on an identifier ID of the receiver. In order to obtain the corresponding private key, the receiver system queries two of the three PKGs using, for example, the receiver's identity or public key. As shown in the figure, receiver system 502 makes queries 506 and 507 to PKG A 503 and PKG B 504, respectively, in order to obtain two shares of the private key. In response to the queries, PKG A 503 and PKG B 504 return, respectively, share d_{1}, 508, and share d_{2}, 509, of private key d, 510. Receiver system 502 is then able to assemble the corresponding private key d_{ID}, which corresponds to the public key with which the message 514 was encrypted. More generally, the receiver could have selected to query any two of the three PKGs. For example, receiver system 502 alternatively could have queried PKGs B and C and combined private key shares d_{2 }and d_{3 }to produce the private key 510. These techniques easily generalize to provide similar embodiments using toutof n sharing.
 [0190]Sender system 501, receiver system 502 as well as PKGs 503, 504 and 505 may be each implemented as computer systems which include elements such as processors and computerreadable media such as memory and other storage devices. Communication between the respective elements may take place using data packets sent over data networks, or any of various other forms of electronic and data transmission and communication. The communication may transpire over various architectures of communication, such as a computer network, such as the Internet, with various wired, wireless and other communications media.
 [0000]Working in Subgroups
 [0191]In an alternative embodiment of the detailed IBE system described above, performance may be improved by working in a comparatively small subgroup of the curve. For example, choose a 1024bit prime p=2 mod 3 with p=aq−1 for some 160bit prime q. The point P is then chosen to be a point of order q. Each public key ID is converted to a group point by hashing ID to a point Q on the curve and then multiplying the point by a. The system is secure if the BDH assumption holds in the group generated by P. The advantage of this embodiment is that the Weil computation is done on points of small order, and hence is much faster.
 [0000]IBE Implies Signatures
 [0192]Various IBE techniques described above can be used to provide public key signature systems and methods. The intuition is as follows. The private key for the signature scheme is the master key for the IBE scheme. The public key for the signature scheme is the set of global system parameters for the IBE scheme. The signature on a message M is the IBE decryption key for ID=M. To verify a signature, choose a random message M′, encrypt M′ using the public key ID=M, and then attempt to decrypt using the given signature on M as the decryption key. If the IBE system is INDIDCCA, then the signature scheme is existentially unforgeable against a chosen message attack. Note that, unlike most signature schemes, this signature verification embodiment is randomized. This shows that the IBE techniques described herein may encompass both public key encryption and digital signatures. Signature schemes derived from these approaches can be used to provide interesting properties, as described by Boneh et al. (D. Boneh, B. Lynn, H. Shacham, “Short signatures from the Weil pairing”, in Advances in Cryptology—AsiaCrypt 2001, Lecture Notes in Computer Science, Vol. 2248, SpringerVerlag, pp. 514532, 2001, which is incorporated herein by reference).
 [0000]Escrow ElGamal Encryption
 [0193]In this section we show that various IBE techniques described above can be used to provide an ElGamal encryption system embodiment having global escrow capability. In this embodiment, a single escrow key enables the decryption of ciphertexts encrypted under any public key.
 [0194]In one exemplary embodiment, the ElGamal escrow system works as follows. The Setup is similar to that for BasicIdent. Unlike the identitybased BasicIdent, each user selects a secret random number and uses it to generate a public/private key pair. A sender and receiver can then use Encrypt and Decrypt to communicate an encrypted message. The message is secure except for an escrow who can use a master key s to decrypt the message.
 [0195]
FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention. The system includes a sender system 601 with encryption logic 610, receiver system 602 with decryption logic 611, escrow agent system 604 and broadcasting system 605. Broadcast system 605 sends system parameters to participants such as escrow agent system 604, receiver system 602 and sender system 601. The receiver system 602 selects a private key x, 607, and uses it to generate a public key P_{pub}=xP, 606, which is then published. The private key x and the public key P_{pub }form a complementary key pair. Using the public key P_{pub}=xP, 606, sender system 601 encrypts a message M with encryption logic 610. Sender system 601 sends a resulting encrypted message 603 to receiver 602. Receiver system 602 decrypts the message with decryption logic 611 using the private key x, 607. Escrow agent system 604 may intercept message 603 and, using the escrow agent key s, 609, public key P_{pub}=xP, 606, and decrypt message 603 with decryption logic 612. In an alternate embodiment, broadcast system 605 and escrow agent 604 may be a single entity. In yet another embodiment, the escrow agent key s may be shared in a manner such as in the distributed PKG embodiments described earlier.  [0196]In more detail, an exemplary embodiment of the technique involves the following procedures:
 Setup: Let be some BDH parameter generator. Given a security parameter kε ^{+}, the algorithm works as follows:
 Step 1: Run on input k to generate a prime q, two groups _{1}, _{2 }of order q, and an admissible map ê: _{1}× _{1}→ _{2}. Let P be some generator of _{1}.
 Step 2: Pick a random sε*_{q }and set Q=sP.
 Step 3: Choose a cryptographic hash function H: _{2}→{0, 1}^{n}.
 The message space is ={0, 1}^{n}. The ciphertext space is = _{1}×{0, 1}^{n}. The system parameters are params=<q, _{1}, _{2}, ê, n, P, Q, H>. The escrow key is sε*_{q}.
 keygen: A user generates a public/private key pair for herself by picking a random xε*_{q }and computing P_{pub}=xPε _{1}. Her private key is x (or xQ), her public key is P_{pub}.
 Encrypt: To encrypt Mε{0, 1}^{n }under the public key P_{pub }do the following: (1) pick a random rε*_{q}, and (2) set the ciphertext to be:
C=<rP,M⊕H(g ^{r})> where g=ê(P _{pub} ,Q)ε _{2}. This encryption technique is also illustrated in
FIG. 7 , where the sender obtains the system parameters and elements P and Q=sP in block 700, and obtains the recipient's public key P_{pub}=xP in block 710. The sender then selects a random r and computes a message key in block 720. The message key is then used to encrypt a message in block 730. The sender then transmits an encapsulated key rP and encrypted message V to the receiver.
 This encryption technique is also illustrated in
 Decrypt: Let C=<U, V> be a ciphertext encrypted using P_{pub}. Then Uε _{l}. To decrypt C using the private key x do:
V⊕H(ê(U,xQ))=M. As illustrated in
FIG. 8 , the receiver obtains the system parameters and elements P and Q=sP in block 800, then obtains the encrypted message V and encapsulated key rP from the sender in block 810. The receiver then computes the message key in block 820, and uses it to decrypt the message in block 830.  To see that the message keys computed by the sender and receiver are the same, note that the sender knows the secret r as well as the public Q=sP and P_{pub}=xP, and uses these to compute a key from ê(sP, xP)^{r}. The receiver, on the other hand, knows the secret x as well as the public Q=sP and rP, and uses these to compute a message key from ê(rP, x(sP)). The bilinearity of ê implies that ê(sP, xP)^{r}=ê(rP, x(sP)), so the sender and receiver compute the same message key.
 As illustrated in
 Escrowdecrypt: The purpose of this embodiment is to permit escrow decryption of otherwise secure communications. To decrypt C=<U, V> using the escrow key s, compute:
V⊕H(ê(U,sP _{pub}))=M. As shown in
FIG. 9 , the escrow obtains the system parameters and element P in block 900, then in block 910 obtains the recipient's public key xP, and obtains the encrypted message V and encapsulated key rP from the sender. The escrow then computes the message key in block 920, and uses it to decrypt the message in block 930. The escrow can compute the message key from the knowledge of s, rP, and xP.
A standard argument shows that assuming that BDH is hard for groups generated by the system of this embodiment has semantic security in the random oracle model (recall that since DDH is easy we cannot prove semantic security based on DDH). Yet, the escrow agent can decrypt any ciphertext encrypted using any user's public key. The decryption capability of the escrow agent can be distributed using the PKG distribution techniques described earlier.
 As shown in
 Setup: Let be some BDH parameter generator. Given a security parameter kε ^{+}, the algorithm works as follows:
 [0210]Another embodiment uses a similar hardness assumption, with an ElGamal encryption system with nonglobal escrow. In this embodiment, each user constructs a public key with two corresponding private keys, and gives one of the private keys to the trusted third party. The trusted third party maintains a database of all private keys given to it by the various users. Although both private keys can be used to decrypt, only the user's private key can be used simultaneously as the signing key for a discrete logarithm based signature scheme.
 [0211]Various other cryptographic systems can be devised based on the principles illustrated in the above embodiments. For example, three entities A, B, and C can communicate securely as a group by privately selecting random integers a, b, c and publishing public keys aP, bP, cP. One of them, such as A, could encrypt a message using the message key ê(bP, cP)^{r }and transmit it with rP. Then B could decrypt the message by calculating ê(cP, rP)^{b }and C could decrypt it by calculating ê(bP, rP)^{c}. Similarly, B could send a message to A and C, or C could send a message to A and B.
 [0212]In another possible embodiment, two of the three entities, say A and B, could publish a joint public key abP. Then C could encrypt a message using the message key ê(abP, cP)^{r }and transmit it with rP. Then neither A nor B alone could decrypt the message, but both A and B together could compute ê(cP, rP)^{ab }and jointly decrypt the message. This technique generalizes to any number of entities. For example, C could join A and B by using abP to compute and publish the threeway joint public key abcP. Then anyone could encrypt a message using the message key ê(abcP, xP)^{r }and transmit it with rP. Then only A and B and C together could compute ê(xP, rP)^{abc }and jointly decrypt the message.
 [0000]Threshold Decryption.
 [0213]Embodiments of the invention enable n entities to have shares of a private key d_{ID }corresponding to a given public key ID, so that messages encrypted using ID can only be decrypted if t of the n entities collaborate. The private key d_{ID }is never reconstructed in a single location. Embodiments of our IBE system may support this as follows.
 [0214]Recall that in other embodiments the private key d_{ID}=sQ_{ID }where sε*_{q }is the masterkey. Instead, let s_{1}, . . . s_{n}ε*_{q }be a toutofn Shamir secret sharing of the masterkey s. Each of the n users is given d_{i}=s_{i}Q_{ID}. To decrypt a ciphertext <U, V> encrypted using the key ID each user locally computes g_{i}=ê(U, d_{i}) and sends g_{i}ε _{2 }to the user managing the decryption process. That user then combines the decryption shares by computing g_{ID}=
$\prod _{i}{g}_{i}^{{\lambda}_{i}}$
where λ_{i }are the appropriate Lagrange interpolation coefficients used in Shamir secret sharing. The message is then obtained by computing H_{2}(g_{ID})⊕V=M.  [0215]Those skilled in the art of cryptography will be able to devise many other schemes that employ the basic principles of the present invention.
 [0000]Applications of IdentityBased Encryption
 [0216]One application for embodiments of identitybased encryption is to help the deployment of a public key infrastructure. In this section, we show several embodiments of this and other applications.
 [0000]Revocation of Public Keys
 [0217]In this embodiment, the sender may encrypt using a public key derived from a piece of information containing a time element, such as a year, date or other time, to help provide key expiration or other forms of temporal key management. For example, in one embodiment, key expiration can be done by having Alice encrypt email sent to Bob using the public key: “bob@company.com ∥ currentyear”. In doing so Bob can use his private key during the current year only. Once a year Bob needs to obtain a new private key from the PKG. Hence, we get the effect of annual private key expiration. Note that unlike the existing public key infrastructure, Alice does not need to obtain a new certificate from Bob every time Bob refreshes his private key.
 [0218]One may make this approach more granular in other embodiments by encrypting email for Bob using “bob@company.com ∥ currentdate”, or using another time stamp. This forces Bob to obtain a new private key every day. This embodiment may be used in a corporate context where the PKG is maintained by the corporation. With this approach key revocation is very simple: when Bob leaves the company and his key needs to be revoked, the corporate PKG is instructed to stop issuing private keys for Bob's email address. As a result, Bob can no longer read his email. The interesting property is that Alice does not need to communicate with any third party certificate directory to obtain Bob's daily public key. Hence, embodiments of identity based encryption can provide a very efficient mechanism for implementing ephemeral public keys. Also note that this embodiment can be used to enable Alice to send messages into the future: Bob will only be able to decrypt the email on the date specified by Alice.
 [0000]Managing User Credentials
 [0219]An embodiment of the invention enables the management of user credentials using an IBE system. The message is encrypted with a string containing a credential identifier. For example, suppose Alice encrypts mail to Bob using the public key: “bob@company.com ∥ currentyear ∥ clearance=secret”. Then Bob will only be able to read the email if on the specified date he has secret clearance. Consequently, it is very easy to grant and revoke user credentials using the PKG.
 [0220]
FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention. The system includes sender system 1001, receiver system 1002 and PKG 1003. Each such system may be implemented as a computer system such as a client or server connected to a computer network. Accordingly, sender 1001, receiver 1002 and PKG 1003 may each contain processors, such as processor 1014, processor 1013 and processor 1012. Additionally, these systems may include computerreadable storage media, such as computer memory, and may additionally include interfaces to a computer network, including technology allowing for communication with a wired, wireless or other network. Sender system 1001 may include a software plugin 1017. Such a plugin may comprise a software module which performs cryptographic functions. The plugin includes, according to an embodiment of the invention, items such as cryptographic logic 1004. Plugin 1017 may be distributed to various computers such as sender system 1001 and receiver system 1002 through a network in order to roll out functionality associated with identitybased encryption and other communication functionality. Parameters 1015 from a system such as PKG 1003 are also distributed over a computer network or other communications medium to senders and receivers, such as sender system 1001 and receiver system 1002, who may then use them in conjunction with plugin 1017 when encrypting or decrypting messages. In one embodiment, plugin 1017 is distributed together with parameters 1014. In an alternate embodiment, parameters 1015 may be distributed separately.  [0221]Sender system 1001 encrypts a message M using encryption logic 1004 in plugin 1017. Encryption logic 1004 encrypts the message using encryption key 1011, which is based on selected credential 1005 and an identification 1016 of the intended receiver of the message. In some embodiments, the key may be based on other information as well. The sender system 1001 sends the receiver system 1002 information 1006, e.g., in the form of a data packet transmitted over a network or other communication medium. The information 1006 sent to receiver system 1002 contains the encrypted message and may also contain information 1007 regarding the credential 1005 used as part of the basis for the encryption key.
 [0222]Either before or after receiving information 1006, receiver system 1002 sends a request 1009 to PKG 1003. In one embodiment, the request 1009 may include the receiver's identity 1016 and may also include information related to the selected credential 1005. In response, PKG 1003 verifies the credential of receiver 1002 using credential check logic 1008. Such logic may be implemented in software, hardware or a combination thereof. If the credential is verified as belonging to the receiver, then PKG 1003 provides a response 1010 to receiver 1002, which includes a private decryption key 1018 corresponding to the encryption key 1011. Using the private decryption key, the receiver then may decrypt the encrypted message contained in information 1006 to recover the original message M. Thus, by including a credential as part of an encryption key, embodiments such as this one allow a sender to encrypt a message intended for a receiver, where the decryption of the message by the receiver is contingent upon the validity of the receiver's credential.
 [0000]Delegation of Decryption Keys
 [0223]Another application for embodiments of IBE systems is delegation of decryption capabilities. We give two exemplary embodiments, described with reference to a user Bob who plays the role of the PKG. Bob runs the setup algorithm to generate his own IBE system parameters params and his own masterkey. Here we view params as Bob's public key. Bob obtains a certificate from a CA for his public key params. When Alice wishes to send mail to Bob she first obtains Bob's public key params from Bob's public key certificate. Note that Bob is the only one who knows his masterkey and hence there is no keyescrow with this setup.
 1. Delegation to a laptop. Suppose Alice encrypts mail to Bob using the current date as the IBE encryption key (she uses Bob's params as the IBE system parameters). Since Bob has the masterkey he can extract the private key corresponding to this IBE encryption key and then decrypt the message. Now, suppose Bob goes on a trip for seven days. Normally, Bob would put his private key on his laptop. If the laptop is stolen the private key is compromised. When using the IBE system Bob could simply install on his laptop the seven private keys corresponding to the seven days of the trip. If the laptop is stolen, only the private keys for those seven days are compromised. The masterkey is unharmed.
FIG. 11 is a block diagram illustrating a system with key delegation according to an embodiment of the invention. The system includes user system 1101 and target system 1102. The target system may comprise a computer such as a laptop computer. User system 1101 includes a master key 1103, which is used to generate decryption keys 1104. The decryption keys 1104 are downloaded to the target system 1102. Using the techniques of key revocation described above, these decryption keys may be valid only for a limited time, thus providing additional security in the event that target system 1101 is compromised. User system 1101 and target system 1102 may include elements of computer systems such as memory 1106 and 1107 as well as processor 1105 and 1108. User system 1101 includes key generator logic 1109, which uses master key 1103 and system parameters 1110 to generate private decryption keys 1104 based on information derived from a user ID 1113 and one or more dates 1114 or other time stamps. Target system 1102 includes decryption logic 1111, which uses the private decryption keys 1104 obtained from user system 1101 and system parameters 1110 to decrypt an incoming encrypted message 1112. If message 1112 is encrypted using public keys based on ID 1113 and one of the dates 1114, then private decryption keys may be used to decrypt it. Thus the decryption capabilities of target system 1102 may be limited to messages associated with selected dates 1114. In an alternate embodiment, the target system may be a data storage medium or portable data storage device which can be connected as desired to other computer systems, thereby enabling use of the decryption keys on those systems.  2. Delegation of duties. Suppose Alice encrypts mail to Bob using the subject line as the IBE encryption key. Bob can decrypt mail using his masterkey. Now, suppose Bob has several assistants each responsible for a different task (e.g. one is ‘purchasing’, another is ‘humanresources’, etc.). In this embodiment, Bob may give one private key to each of his assistants corresponding to the assistant's responsibility. Each assistant can then decrypt messages whose subject line falls within its responsibilities, but it cannot decrypt messages intended for other assistants. Note that Alice only obtains a single public key from Bob (params), and she uses that public key to send mail with any subject line of her choice. The mail can only be read by the assistant responsible for that subject.
 More generally, embodiments of IBE can simplify various systems that manage a large number of public keys. Rather than storing a big database of public keys the system can either derive these public keys from user names, or simply use the integers 1, . . . , n as distinct public keys. For example, in a corporation, each employee might have a unique employee number, and that number may serve also as the employee's public key.
Return Receipt
 More generally, embodiments of IBE can simplify various systems that manage a large number of public keys. Rather than storing a big database of public keys the system can either derive these public keys from user names, or simply use the integers 1, . . . , n as distinct public keys. For example, in a corporation, each employee might have a unique employee number, and that number may serve also as the employee's public key.
 1. Delegation to a laptop. Suppose Alice encrypts mail to Bob using the current date as the IBE encryption key (she uses Bob's params as the IBE system parameters). Since Bob has the masterkey he can extract the private key corresponding to this IBE encryption key and then decrypt the message. Now, suppose Bob goes on a trip for seven days. Normally, Bob would put his private key on his laptop. If the laptop is stolen the private key is compromised. When using the IBE system Bob could simply install on his laptop the seven private keys corresponding to the seven days of the trip. If the laptop is stolen, only the private keys for those seven days are compromised. The masterkey is unharmed.
 [0227]
FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention. According to one embodiment of the invention, a sender can receive an confirmation that the recipient has received an encrypted message. More generally, upon receipt of a request for a decryption key from a receiver, the PKG takes an action separate from providing a decryption key to the receiver. Such an action comprises providing an acknowledgement to the sender that indicates that the message was received, according to one embodiment.  [0228]An embodiment of a system having return receipt capability is illustrated in
FIG. 12 . The system includes sender system 1201, recipient system 1202 and PKG system 1203. The sender system 1201, receiver system 1202 and PKG system 1203 may be implemented as computer systems coupled to a computer network. For example, PKG 1203, sender system 1201 and receiver system 1202 may include processor 1212, processor 1213 and processor and 1214, respectively. These computer systems may include elements such as computer readable storage media, computer memory and other storage devices. Additionally, these systems may include interfaces to a computer network, including technology allowing for communication from a wired, wireless or other network. Further, according an embodiment of the invention, communication between the respective elements may take place using data packets sent over a computer network, or using any of various other forms of electronic and data transmission and communication.  [0229]The sender 1201 encrypts a message M and sends the resulting ciphertext to receiver 1202 in a data package 1204 that also may include return receipt request information 1209. The return receipt request information may contain, for example, a return address and a message identifier corresponding to the particular message 1204. The message M is encrypted by the sender using encryption logic 1211 and an encryption key 1215. Encryption key 1215 may be based on a receiver ID (such as an email address) 1216 and the return receipt request information 1209. Because the receiver ID and return receipt request information 1209 are used by the sender to determine the encryption key 1215, the receiver 1202 needs a corresponding decryption key that can be used to decrypt the message. Accordingly, recipient system 1202, in response to receiving message 1204, sends PKG 1203 a request 1206, which includes the return receipt request information 1209 and the receiver's ID, 1216. In response, PKG 1203 sends to receiver 1202 the private decryption key 1205, which receiver then uses with decryption logic 1217 to decrypt the ciphertext of message 1204 and recover the original message M. In addition to sending receiver 1202 the decryption key 1205, PKG 1203 also sends a return receipt 1207 to sender 1201. PKG 1203 may alternatively store the receipt on storage media as part of a log rather than send a return receipt. Return receipt 1207 may include information such as the message identifier. Thus, sender 1201 receives proof that recipient 1202 has received the message 1204. The system may be initialized by placing plugin software in various systems, such as sender system 1201 and receiver system 1202. Such plugin software may include system parameters, some of which may be derived from a system master key. Such parameters, stored in local devices such as sender 1201 and receiver 1202 are then used to generate encryption keys, perform encryption, perform decryption, and other functions, as appropriate.
 [0000]Description of the Weil Pairing
 [0230]In this section we describe the Weil pairing on elliptic curves and then show how to efficiently compute it using an algorithm. To be concrete we present an example using supersingular elliptic curves defined over a prime field _{p }with p>3 (the curve y^{2}=x^{3}+1 over _{p }with p=2 mod 3 is an example of such a curve). The following discussion easily generalizes to computing the Weil pairing over other elliptic curves.
 [0000]Elliptic Curves and the Weil Pairing
 [0231]We state a few elementary facts about supersingular elliptic curves defined over a prime field _{p }with p>3:
 Fact 1: A supersingular curve E/ _{p }(with p>3) contains p+1 points in _{p}. We let O denote the point at infinity. The group of points over _{p }forms a cyclic group of order p+1. For simplicity, let P be a generator of this group and set n=p+1.
 Fact 2: The group of points E( _{p} _{ 2 }) contains a point Q of order n which is linearly independent of the points in E( _{p}). Hence, E( _{p} _{ 2 }) contains a subgroup which is isomorphic to the group _{n} ^{2}. The group is generated by PεE( _{p}) and QεE( _{p} _{ 2 }). We denote this group by E[p+1]=E[n].
We will be working with the Weil pairing e which maps pairs of points in E[n] into *_{p} _{ 2 }, i.e. e: E[n]×E[n]→*_{p} _{ 2 }. To describe the pairing, we review the following concepts:  Divisors A divisor is a formal sum of points on the curve E( _{p} _{ 2 }). We write divisors as
$\mathcal{A}=\sum _{P}{a}_{p}\left(P\right)$  where a_{P}ε and PεE( _{p} _{ 2 }). For example, =3(P_{1})−2(P_{2})−(P_{3}) is a divisor. We will only consider divisors
$f\left(x,y\right)\in {\mathbb{F}}_{{p}^{2}}\left(x,y\right).$  where
$\sum _{P}{a}_{p}=0.$  Functions Roughly speaking, a function ƒ on the curve E( _{p} _{ 2 }) can be viewed as a rational function ƒ(x, y)ε _{p} _{ 2 }(x, y). For any point P=(x, y)εE( _{p} _{ 2 }) we define ƒ(P)=ƒ(x, y).
 Divisors of functions Let ƒ be a function on the curve E( _{p} _{ 2 }). We define its divisor, denoted by (ƒ), as
$\left(f\right)=\sum _{P}{\mathrm{ord}}_{P}\left(f\right)\xb7P.$  P. Here ord_{P}(ƒ) is the order of the zero that ƒ has at the point P. For example, let ax+by+c=0 be the line passing through the points P_{1}, P_{2}εE( _{p} _{ 2 }) with P_{1 }≠±P_{2}. This line intersects the curve at third point P_{3}εE( _{p} _{ 2 }). Then the function ƒ(x, y)=ax+by+c has three zeroes P_{1}, P_{2}, P_{3 }and a pole of order 3 at infinity. The divisor of ƒ is (ƒ)=(P_{1})+(P_{2})+(P_{3})−3(O).
 Principal divisors Let be a divisor. If there exists a function ƒ such that (ƒ)= then we say that is a principal divisor. We know that a divisor
$\mathcal{A}=\sum _{P}{a}_{p}\left(P\right)$  is principal if and only if
$\sum _{P}{a}_{p}=0$  and
$\sum _{P}{a}_{P}P=O.$  Note that the second summation is using the group action on the curve. Furthermore, given a principal divisor there exists a unique function ƒ (up to constant multiples) such that (A)=(ƒ).
 Equivalence of divisors We say that two divisors , are equivalent if their difference − is a principal divisor. We know that any divisor
$\mathcal{A}=\sum _{P}{a}_{p}\left(P\right)$  (with
$\left(\mathrm{with}\text{\hspace{1em}}\sum _{P}{a}_{P}=0\right)$  is equivalent to a divisor of the form ′=(Q)−(O) for some QεE. Observe that
$Q=\sum _{P}{a}_{P}P.$  Notation Given a function ƒ and a divisor
$\mathcal{A}=\sum _{P}{a}_{P}\left(P\right)$  we define ƒ() as ƒ()=Π_{P}ƒ(P)^{aP}. Note that since
$\sum _{P}{a}_{P}=0$  we have that ƒ() remains unchanged if instead of ƒ we use cƒ for any cε _{p} _{ 2 }.
We are now ready to describe the Weil pairing of two points P, QεE[n]. Let _{P }be some divisor equivalent to the divisor (P)−(O). We know that n _{P }is a principal divisor (it is equivalent to n(P)−n(O) which is clearly a principal divisor). Hence, there exists a function ƒ_{P }such that (ƒ_{P})=n _{P}. Define _{Q }and ƒ_{Q }analogously. The Weil pairing of P and Q is given by:$e\left(P,Q\right)=\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\mathcal{A}}_{P}\right)}$
This ratio provides the value of the Weil pairing of P and Q whenever it is well defined (i.e., whenever no division by zero has occurred). If this ratio is undefined we use different divisors _{P}, _{Q }to define e(P, Q). When P, QεE( _{p} _{ 2 }) we have that e(P, Q)ε _{p} _{ 2 }.
 [0250]We briefly show that the Weil pairing is well defined. That is, the value of e(P, Q) is independent of the choice of the divisor _{P }as long as _{P }is equivalent to (P)−(O) and _{P }leads to a well defined value. The same holds for _{Q}. Let {circumflex over ()}_{P }be a divisor equivalent to _{P }and let {circumflex over (ƒ)}_{P }be a function so that ({circumflex over (ƒ)}_{P})=n{circumflex over ()}_{P}. Then {circumflex over ()}_{P}= _{P}+(g) for some function g and {circumflex over (ƒ)}_{P}=ƒ_{P}·g^{n}. We have that:
$\begin{array}{c}e\left(P,Q\right)=\frac{{\hat{f}}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\hat{\mathcal{A}}}_{P}\right)}\\ =\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right){g\left({\mathcal{A}}_{Q}\right)}^{n}}{{f}_{Q}\left({\mathcal{A}}_{P}\right){f}_{Q}\left(\left(g\right)\right)}\\ =\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\mathcal{A}}_{P}\right)}\xb7\frac{g\left(n\text{\hspace{1em}}{\mathcal{A}}_{Q}\right)}{{f}_{Q}\left(\left(g\right)\right)}\\ =\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\mathcal{A}}_{P}\right)}\xb7\frac{g\left(\left({f}_{Q}\right)\right)}{{f}_{Q}\left(\left(g\right)\right)}\\ =\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\mathcal{A}}_{P}\right)}\end{array}$
The last equality follows from the following fact known as Weil reciprocity: for any two functions ƒ, g we have that ƒ((g))=g((ƒ)). Hence, the Weil pairing is well defined.
Fact 10 The Weil pairing has the following properties:
 For all PεE[n] we have: e(P, P)=1.
 Bilinear: e(P_{1}+P_{2}, Q)=e(P_{1}, Q)·e(P_{2}, Q) and e(P, Q_{1}+Q_{2})=e(P, Q_{1})·e(P, Q_{2})
 When P, QεE[n] are collinear then e(P, Q)=1. Similarly, e(P, Q)=e(Q, p)^{−1}.
 n'th root: for all P, QεE[n] we have e(P, Q)^{n}=1.
 Nondegenerate: if P satisfies e(P, Q)=1 for all QεE[n] then P=O.

 [0256]As discussed earlier, our detailed example of an embodiment of an IBE scheme uses the modified Weil pairing ê(P, Q)=e(P, φ(Q)), where φ is an automorphism on the group of points of E.
Tate pairing. The Tate pairing is another bilinear pairing that has the required properties for embodiments of our system. In various embodiments, we slightly modify the original definition of the Tate pairing to fit our purpose. Define the Tate pairing of two points P, QεE[n] as$T\left(P,Q\right)={{f}_{P}\left({\mathcal{A}}_{Q}\right)}^{\uf603{\mathbb{F}}_{{p}^{2}}^{*}\uf604/n}$
where ƒ_{P }and _{Q }are defined as earlier. This definition gives a computable bilinear pairing T: E[n]×E[n]→ _{2}.
Computing the Weil Pairing  [0257]Given two points P, QεE[n] we show how to compute e(P, Q)ε*_{p} _{ 2 }using O(log p) arithmetic operations in _{p}. We assume P # Q. We proceed as follows: pick two random points R_{1}, R_{2}εE[n]. Consider the divisors _{P}=(P+R_{1})−(R_{1}) and _{Q}=(Q+R_{2})−(R_{2}). These divisors are equivalent to (P)−(O) and (O)−(O) respectively. Hence, we can use _{P }and _{Q }to compute the Weil pairing as:
$e\left(P,Q\right)=\frac{{f}_{P}\left({\mathcal{A}}_{Q}\right)}{{f}_{Q}\left({\mathcal{A}}_{P}\right)}=\frac{{f}_{P}\left(Q+{R}_{2}\right){f}_{Q}\left({R}_{1}\right)}{{f}_{P}\left({R}_{2}\right){f}_{Q}\left(P+{R}_{1}\right)}$
This expression is well defined with very high probability over the choice of R_{1}, R_{2 }(the probability of failure is at most$O\left(\frac{\mathrm{log}\text{\hspace{1em}}p}{p}\right)).$
In the rare event that a division by zero occurs during the computation of e(P, Q) we simply pick new random points R_{1}, R_{2 }and repeat the process.  [0258]To evaluate e(P, Q) it suffices to show how to evaluate the function ƒ_{P }at _{Q}. Evaluating ƒ_{Q}( _{P}) is done analogously. We evaluate ƒ_{P}( _{Q}) using repeated doubling. For a positive integer b define the divisor
_{b} =b(P+R _{1})−b(R _{1})−(bP)+(O)
It is a principal divisor and therefore there exists a function ƒ_{b }such that (ƒ_{b})= _{b}. Observe that (ƒ_{P})=(ƒ_{n}) and hence, ƒ_{P}( _{Q})=ƒ_{n}( _{Q}). It suffices to show how to evaluate ƒ_{n}( _{Q}).
Lemma 11 There is an algorithm that given ƒ_{b}( _{Q}), ƒ_{c}( _{Q}) and bP, cP, (b+c)P for some b, c>0 outputs ƒ_{b+c}( _{Q}). The algorithm only uses a (small) constant number of arithmetic operations in _{p} _{ 2 }.
Proof We first define two auxiliary linear functions g_{1}, g_{2}:
 1. Let a_{1}x+b_{1}y+c_{1}=0 be the line passing through the points bP and cP (if b=c then let a_{1}x+b_{1}y+c_{1}=0 be the line tangent to E at bP). Define g_{1}(x, y)=a_{1}x+b_{1}y+c_{1}.
 2. Let x+c_{2}=0 be the vertical line passing through the point (b+c)P. Define g_{2}(x, y)=x+c_{2 }
The divisors of these functions are:
(g _{1})=(bP)+(cP)+(−(b+c)P)−3(O)
(g _{2})=((b+c)P)+(−(b+c)P)−2(O)
By definition we have that:
_{b} =b(P+R _{1})−b(R _{1})−(bP)+(O)
_{c} =c(P+R _{1})−c(R _{1})−(cP)+(O)
_{b} +c=(b+c)(P+R _{1})−(b+c)(R _{1})−((b+c)P)+(O)
It now follows that: _{b+c}= _{b}+ _{c}+(g_{1})−(g_{2}). Hence:$\begin{array}{cc}{f}_{b+c}\left({\mathcal{A}}_{Q}\right)={f}_{b}\left({\mathcal{A}}_{Q}\right)\xb7{f}_{c}\left({\mathcal{A}}_{Q}\right)\xb7\frac{{g}_{1}\left({\mathcal{A}}_{Q}\right)}{{g}_{2}\left({\mathcal{A}}_{Q}\right)}& \left(1\right)\end{array}$
This shows that to evaluate ƒ_{b+c}( _{Q}) it suffices to evaluate g_{i}( _{Q}) for all i=1, 2 and plug the results into equation 1. Hence, given ƒ_{b}( _{Q}), ƒ_{c}( _{Q}) and bP, cP, (b+c)P one can compute ƒ_{b+c}( _{Q}) using a constant number of arithmetic operations.

 [0261]Denote the output of Algorithm of Lemma 11 by (ƒ_{b}( _{Q}), ƒ_{c}( _{Q}), bP, cP, (b+c)P)=ƒ_{b+c}( _{Q}). Then one can compute ƒ_{P}( _{Q})=ƒ_{n}( _{Q}) using the following standard repeated doubling procedure. Let n=b_{m}b_{m1 }. . . b_{1}b_{0 }be the binary representation of n, i.e.
$n=\sum _{i=0}^{m}{b}_{i}{2}^{i}.$
Init: Set Z=O, V=ƒ_{0}( _{Q})=1, and k=0.
Iterate: For i=m, m−1, . . . , 1, 0 do:
 1: If b_{i}=1 then do: Set V=(V, ƒ_{1}( _{Q}), Z, P, Z+P), set Z=Z+P, and set k=k+1.
 2: If i>0 set V=(V, V, Z, Z, 2Z), set Z=2Z, and set k=2k.
 3: Observe that at the end of each iteration we have z=kP and V=ƒ_{k}( _{Q}).
Output: After the last iteration we have k=n and therefore V=ƒ_{n}( _{Q}) as required.
To evaluate the Weil pairing e(P, Q) we run the above algorithm once to compute ƒ_{P}( _{Q}) and once to compute ƒ_{Q}( _{P}). Note that the repeated squaring algorithm needs to evaluate ƒ_{1}(3 _{Q}). This is easily done since the function ƒ_{1}(x, y) (whose divisor is (ƒ_{1})=(P+R_{1})−(R_{1})−(P)+(O)) can be written out explicitly as follows:  1. Let a_{1}x+b_{1}y+c_{1}=0 be the line passing through the points P and R_{1}. Define the function: g_{1}(x, y)=a_{1}x+b_{1}y+c_{1}.
 2. Let x+c_{2}=0 be the vertical line passing through the point P+R_{1}. Define the function: g_{2}(x, y)=x+c_{2}.
 3. The function ƒ_{1}(x, y) is simply ƒ_{1}(x, y)=g_{2}(x, y)/g_{1}(x, y) which is easy to evaluate in _{p} _{ 2 }.

Claims (20)
Priority Applications (3)
Application Number  Priority Date  Filing Date  Title 

US31194601 true  20010813  20010813  
US10218697 US7113594B2 (en)  20010813  20020813  Systems and methods for identitybased encryption and related cryptographic techniques 
US11431410 US7634087B2 (en)  20010813  20060509  Systems and methods for identitybased encryption and related cryptographic techniques 
Applications Claiming Priority (3)
Application Number  Priority Date  Filing Date  Title 

US11431410 US7634087B2 (en)  20010813  20060509  Systems and methods for identitybased encryption and related cryptographic techniques 
US12589880 US8130964B2 (en)  20010813  20091028  Systems and methods for identitybased encryption and related cryptographic techniques 
US13369165 US9356779B2 (en)  20010813  20120208  Systems and methods for identitybased encryption and related cryptographic techniques 
Related Parent Applications (1)
Application Number  Title  Priority Date  Filing Date  

US10218697 Continuation US7113594B2 (en)  20010813  20020813  Systems and methods for identitybased encryption and related cryptographic techniques 
Related Child Applications (1)
Application Number  Title  Priority Date  Filing Date 

US12589880 Continuation US8130964B2 (en)  20010813  20091028  Systems and methods for identitybased encryption and related cryptographic techniques 
Publications (3)
Publication Number  Publication Date 

US20070041583A1 true US20070041583A1 (en)  20070222 
US20090034714A9 true true US20090034714A9 (en)  20090205 
US7634087B2 US7634087B2 (en)  20091215 
Family
ID=23209176
Family Applications (4)
Application Number  Title  Priority Date  Filing Date 

US10218697 Active 20241223 US7113594B2 (en)  20010813  20020813  Systems and methods for identitybased encryption and related cryptographic techniques 
US11431410 Active 20230625 US7634087B2 (en)  20010813  20060509  Systems and methods for identitybased encryption and related cryptographic techniques 
US12589880 Active 20220923 US8130964B2 (en)  20010813  20091028  Systems and methods for identitybased encryption and related cryptographic techniques 
US13369165 Active 20231118 US9356779B2 (en)  20010813  20120208  Systems and methods for identitybased encryption and related cryptographic techniques 
Family Applications Before (1)
Application Number  Title  Priority Date  Filing Date 

US10218697 Active 20241223 US7113594B2 (en)  20010813  20020813  Systems and methods for identitybased encryption and related cryptographic techniques 
Family Applications After (2)
Application Number  Title  Priority Date  Filing Date 

US12589880 Active 20220923 US8130964B2 (en)  20010813  20091028  Systems and methods for identitybased encryption and related cryptographic techniques 
US13369165 Active 20231118 US9356779B2 (en)  20010813  20120208  Systems and methods for identitybased encryption and related cryptographic techniques 
Country Status (5)
Country  Link 

US (4)  US7113594B2 (en) 
JP (3)  JP2005500740A (en) 
DE (1)  DE60236094D1 (en) 
EP (3)  EP2224637B1 (en) 
WO (1)  WO2003017559A3 (en) 
Cited By (13)
Publication number  Priority date  Publication date  Assignee  Title 

US20080091947A1 (en) *  20061017  20080417  Andrew John Dancer  Software registration system 
US20090006851A1 (en) *  20070629  20090101  Microsoft Corporation  Confidential mail with tracking and authentication 
US20090030778A1 (en) *  20070723  20090129  Motivepath, Inc.  System, method and apparatus for secure multiparty location based services 
US20090257594A1 (en) *  20080415  20091015  Amjad Qureshi  Secure debug interface and memory of a media security circuit and method 
US20090319769A1 (en) *  20080521  20091224  Apple Inc.  Discrete key generation method and apparatus 
US20100104094A1 (en) *  20070119  20100429  Mitsubishi Electric Corporation  Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus 
US20100119058A1 (en) *  20081111  20100513  Seiichi Matsuda  Information processing apparatus, information processing method, and program 
US8166203B1 (en) *  20090529  20120424  Google Inc.  Server selection based upon time and query dependent hashing 
US20120233465A1 (en) *  20070405  20120913  International Business Machines Corporation  Distribution of Credentials 
US20120254616A1 (en) *  20110401  20121004  Certicom Corporation  IdentityBased Decryption 
US20130322620A1 (en) *  20120531  20131205  Samsung Sds Co., Ltd.  Apparatus and method for generating secret key for idbased encryption system and recording medium having program recorded thereon for causing computer to execute the method 
US20150120650A1 (en) *  20131030  20150430  Gordon E. Seay  Methods and Systems for Utilizing Global Entities In Software Applications 
US20160301531A1 (en) *  20150409  20161013  Qualcomm Incorporated  Proof of work based user identification system 
Families Citing this family (298)
Publication number  Priority date  Publication date  Assignee  Title 

DE10114157A1 (en) *  20010322  20020926  Deutsche Telekom Ag  Computeraided encryption key generation method provides public encryption key with common first part and second part specific to each receiver 
EP2224637B1 (en) *  20010813  20141008  The Board Of Trustees Of The Leland Stanford Junior University  Systems and methods for identitybased encryption 
JP3901484B2 (en) *  20011005  20070404  株式会社ジェイテクト  Electric power steering system 
GB0124681D0 (en) *  20011015  20011205  Hewlett Packard Co  Method and apparatus for encrypting data 
US8065713B1 (en)  20011212  20111122  Klimenty Vainstein  System and method for providing multilocation access management to secured items 
US7921284B1 (en)  20011212  20110405  Gary Mark Kinghorn  Method and system for protecting electronic data in enterprise environment 
US7260555B2 (en)  20011212  20070821  Guardian Data Storage, Llc  Method and architecture for providing pervasive security to digital assets 
US7921450B1 (en) *  20011212  20110405  Klimenty Vainstein  Security system using indirect key generation from access rules and methods therefor 
US7380120B1 (en)  20011212  20080527  Guardian Data Storage, Llc  Secured data format for access control 
USRE43906E1 (en)  20011212  20130101  Guardian Data Storage Llc  Method and apparatus for securing digital assets 
US7930756B1 (en)  20011212  20110419  Crocker Steven Toye  Multilevel cryptographic transformations for securing digital assets 
US8006280B1 (en)  20011212  20110823  Hildebrand Hal S  Security system for generating keys from access rules in a decentralized manner and methods therefor 
US7565683B1 (en)  20011212  20090721  Weiqing Huang  Method and system for implementing changes to security policies in a distributed security system 
US7921288B1 (en)  20011212  20110405  Hildebrand Hal S  System and method for providing different levels of key security for controlling access to secured items 
US7950066B1 (en)  20011221  20110524  Guardian Data Storage, Llc  Method and system for restricting use of a clipboard application 
US7349538B2 (en) *  20020321  20080325  Ntt Docomo Inc.  Hierarchical identitybased encryption and signature schemes 
JP4547158B2 (en) *  20020415  20100922  株式会社エヌ・ティ・ティ・ドコモ  Signature scheme using bilinear mapping 
GB0208858D0 (en) *  20020418  20020529  Hewlett Packard Co  Method and apparatus for encrypting/decrypting data 
GB0215334D0 (en)  20020702  20020814  Ascent Group The Ltd  Storage and authentication of data transactions 
US20050089173A1 (en) *  20020705  20050428  Harrison Keith A.  Trusted authority for identifierbased cryptography 
GB2401763B (en) *  20020705  20050810  Hewlett Packard Development Co  Trusted authority for identiferbased cryptography 
GB0215590D0 (en) *  20020705  20020814  Hewlett Packard Co  Method and apparatus for generating a cryptographic key 
GB0215524D0 (en)  20020705  20020814  Hewlett Packard Co  Method and apparatus for generating a cryptographic key 
DE60313087D1 (en) *  20020807  20070524  Mobilastic Technologies Pte Lt  Secure transmission of digital tokens 
US20040044734A1 (en) *  20020827  20040304  Mark Beck  Enhanced services electronic mail 
US7657748B2 (en) *  20020828  20100202  Ntt Docomo, Inc.  Certificatebased encryption and public key infrastructure 
KR100489327B1 (en) *  20020918  20050512  학교법인 한국정보통신학원  Identification scheme based on the bilinear diffiehellman problem 
US7486795B2 (en) *  20020920  20090203  University Of Maryland  Method and apparatus for key management in distributed sensor networks 
US8176334B2 (en)  20020930  20120508  Guardian Data Storage, Llc  Document security system that permits external users to gain access to secured files 
US7412059B1 (en)  20021127  20080812  Voltage Security, Inc.  Publickey encryption system 
KR20030008182A (en) *  20021224  20030124  학교법인 한국정보통신학원  Method of idbased blind signature by using bilinear parings 
KR20030008183A (en) *  20021224  20030124  학교법인 한국정보통신학원  Method of idbased ring signature by using bilinear parings 
DE60329530D1 (en) *  20030107  20091112  Qualcomm Inc  System, apparatus and method for replacing a cryptographic key 
US7003117B2 (en) *  20030205  20060221  Voltage Security, Inc.  Identitybased encryption system for secure data distribution 
US8108678B1 (en) *  20030210  20120131  Voltage Security, Inc.  Identitybased signcryption system 
US7480384B2 (en) *  20030210  20090120  International Business Machines Corporation  Method for distributing and authenticating public keys using random numbers and DiffieHellman public keys 
US7783044B2 (en) *  20030220  20100824  Proofpoint, Inc.  System for online and offline decryption 
GB2398713B (en) *  20030222  20051130  Hewlett Packard Development Co  Limiting service provision to group members 
US7571321B2 (en) *  20030314  20090804  Voltage Security, Inc.  Identitybasedencryption messaging system 
KR100507809B1 (en) *  20030319  20050817  학교법인 한국정보통신학원  Anonymous fingerprinting scheme based on the bilinear pairings diffiehellman problem 
US7921292B1 (en)  20030404  20110405  Voltage Security, Inc.  Secure messaging systems 
GB2400699B (en) *  20030417  20060705  Hewlett Packard Development Co  Security data provision method and apparatus and data recovery method and system 
GB2401013B (en) *  20030423  20050928  Hewlett Packard Development Co  Cryptographic method and apparatus 
GB0309157D0 (en) *  20030423  20030528  Hewlett Packard Development Co  Cryptographic method and apparatus 
GB0309182D0 (en) *  20030423  20030528  Hewlett Packard Development Co  Security method and apparatus using biometric data 
GB0309161D0 (en) *  20030423  20030528  Hewlett Packard Development Co  Cryptographic method and apparatus 
JP2006524352A (en) *  20030423  20061026  ヒューレット−パッカード デベロップメント カンパニー エル．ピー．  Identitybased encryption method and apparatus based on biometrics 
US20050005100A1 (en) *  20030423  20050106  Liqun Chen  Cryptographic method and system 
EP1471680B1 (en) *  20030423  20060621  HewlettPackard Development Company, L.P.  IdentifierBased Encryption method and apparatus 
EP1478121A3 (en) *  20030509  20041124  Abu, Nor Azman bin  Method and apparatus for IDbased public key generation 
US8707034B1 (en)  20030530  20140422  Intellectual Ventures I Llc  Method and system for using remote headers to secure electronic files 
GB0313666D0 (en)  20030613  20030716  Hewlett Packard Development Co  RSA cryptographic method and system 
GB0313663D0 (en) *  20030613  20030716  Hewlett Packard Development Co  Mediated rsa cryptographic method and system 
US7580521B1 (en)  20030625  20090825  Voltage Security, Inc.  Identitybasedencryption system with hidden public key attributes 
US7017181B2 (en) *  20030625  20060321  Voltage Security, Inc.  Identitybasedencryption messaging system with public parameter host servers 
DE10330089B4 (en) *  20030703  20140227  Bt Ignite Gmbh & Co.  Method and apparatus for transmitting decryption codes for freely transmitted encrypted program contents to uniquely identifiable receiver 
KR20030062401A (en) *  20030704  20030725  학교법인 한국정보통신학원  Apparatus and method for generating and verifying idbased blind signature by using bilinear parings 
US7769167B2 (en) *  20030725  20100803  Microsoft Corporation  Weil and Tate pairing techniques using parabolas 
US7298839B2 (en) *  20030725  20071120  Microsoft Corporation  Squared Weil and Tate pairing techniques for use with elliptic curves 
US7440569B2 (en) *  20030728  20081021  Microsoft Corporation  Tate pairing techniques for use with hyperelliptic curves 
US7266847B2 (en) *  20030925  20070904  Voltage Security, Inc.  Secure message system with remote decryption service 
EP1519530A1 (en) *  20030929  20050330  SGSTHOMSON MICROELECTRONICS S.r.l.  Method for establishing an encrypted communication by means of keys 
US7703140B2 (en)  20030930  20100420  Guardian Data Storage, Llc  Method and system for securing digital assets using processdriven security policies 
US8127366B2 (en)  20030930  20120228  Guardian Data Storage, Llc  Method and apparatus for transitioning between states of security policies used to secure electronic documents 
US8103592B2 (en) *  20031008  20120124  Microsoft Corporation  First computer process and second computer process proxyexecuting code on behalf of first process 
US7788496B2 (en) *  20031008  20100831  Microsoft Corporation  First computer process and second computer process proxyexecuting code on behalf thereof 
US7979911B2 (en) *  20031008  20110712  Microsoft Corporation  First computer process and second computer process proxyexecuting code from third computer process on behalf of first process 
US7596704B2 (en) *  20031010  20090929  JingJang Hwang  Partition and recovery of a verifiable digital secret 
US7487537B2 (en) *  20031014  20090203  International Business Machines Corporation  Method and apparatus for pervasive authentication domains 
US7103911B2 (en)  20031017  20060905  Voltage Security, Inc.  Identitybasedencryption system with district policy information 
JP4741503B2 (en)  20031028  20110803  サーティコム コーポレーション  To verify possible to generate a public key and a device 
US20050135610A1 (en) *  20031101  20050623  Liqun Chen  Identifierbased signcryption 
GB0325527D0 (en) *  20031101  20031203  Hewlett Packard Development Co  Identifierbased signcryption 
US7499544B2 (en)  20031103  20090303  Microsoft Corporation  Use of isogenies for design of cryptosystems 
US7523314B2 (en)  20031222  20090421  Voltage Security, Inc.  Identitybasedencryption message management system 
US20050187863A1 (en) *  20040220  20050825  Whinery Christopher S.  Method and system for protecting real estate from fraudulent transactions 
EP1730881B1 (en) *  20040330  20101013  Dublin City University  Verification of identity based signatures 
US8285996B2 (en)  20050330  20121009  Dublin City University  Verification of identity based signatures 
US8050409B2 (en) *  20040402  20111101  University Of Cincinnati  Threshold and identitybased key management and authentication for wireless ad hoc networks 
US7646872B2 (en) *  20040402  20100112  Research In Motion Limited  Systems and methods to securely generate shared keys 
US7590236B1 (en) *  20040604  20090915  Voltage Security, Inc.  Identitybasedencryption system 
GB2415112B (en)  20040611  20070425  Hewlett Packard Development Co  Cryptographic method and apparatus 
GB2415579B (en)  20040623  20061220  Hewlett Packard Development Co  Cryptographic method and apparatus 
KR100657265B1 (en)  20040623  20061214  삼성전자주식회사  Selfenforcing method and method for transmitting and receiving contents using the same 
US20060013397A1 (en) *  20040713  20060119  International Business Machines Corporation  Channel adapter managed trusted queue pairs 
GB2416282B (en)  20040715  20070516  Hewlett Packard Development Co  Identifierbased signcryption with two trusted authorities 
US7920050B2 (en) *  20040729  20110405  Emc Corporation  Proxy device for enhanced privacy in an RFID system 
EP1621956B1 (en) *  20040730  20170531  Irdeto B.V.  Method of providing rights data objects 
US7564970B2 (en) *  20040812  20090721  Cmla, Llc  Exponential data transform to enhance security 
US8077861B2 (en) *  20040812  20111213  Cmla, Llc  Permutation data transform to enhance security 
JP4820821B2 (en) *  20040812  20111124  シー エム エル エー， リミテッド ライアビリティ カンパニーＣｍｌａ， Ｌｌｃ．  Transpose data conversion for enhanced security 
US7577250B2 (en) *  20040812  20090818  Cmla, Llc  Key derivation functions to enhance security 
US7742596B2 (en) *  20040824  20100622  General Dynamics C4 Systems, Inc.  Reliable elliptic curve cryptography computation 
WO2006034428A3 (en) *  20040920  20070802  Pgp Corp  Apparatus and method for identitybased encryption within a conventional publickey infrastructure 
JP4752313B2 (en) *  20040930  20110817  ソニー株式会社  Cryptographic processing operation method, and a cryptographic processing apparatus, and computer program 
US20060078790A1 (en) *  20041005  20060413  Polyplus Battery Company  Solid electrolytes based on lithium hafnium phosphate for active metal anode protection 
KR100601706B1 (en) *  20041015  20060718  삼성전자주식회사  Method and apparatus for sharing and generating system key in DRM 
US7418100B2 (en) *  20041020  20080826  Cisco Technology, Inc.  Enciphering method 
GB2419787B (en) *  20041028  20070704  Hewlett Packard Development Co  Method and apparatus for providing shortterm private keys in publickey cryptographic systems 
US7660987B2 (en) *  20041029  20100209  Baylis Stephen W  Method of establishing a secure email transmission link 
US7370202B2 (en) *  20041102  20080506  Voltage Security, Inc.  Security device for cryptographic communications 
FR2877453A1 (en) *  20041104  20060505  France Telecom  Method for secure delegation of calculating a bilinear mapping 
EP1815636B1 (en)  20041111  20120222  Certicom Corp.  New trapdoor oneway function on elliptic curves and its application to asymmetric encryption and shorter signatures 
EP1813051B1 (en) *  20041112  20170913  Dublin City University  Identity based encryption 
JP4546231B2 (en) *  20041209  20100915  株式会社日立製作所  Id based signature and encryption systems and methods 
GB2421097B (en) *  20041210  20090701  Hewlett Packard Development Co  Methods, devices and computer programs for creating ciphertext, plaintext and a cryptographic key 
US7639799B2 (en) *  20041214  20091229  Microsoft Corporation  Cryptographically processing data based on a CasselsTate pairing 
DE602005010039D1 (en) *  20041223  20081113  Hewlett Packard Development Co  Improvements in the application of bilinear mappings in cryptographic applications 
JP4528114B2 (en) *  20041228  20100818  日本電信電話株式会社  The key generation device, encryption device, testing device, decoding device and the key generation program, an encryption program, test program, the decryption program 
US8099598B1 (en) *  20050103  20120117  Gary Gang Liu  Secure messaging system with automatic recipient enrollment 
US7869593B2 (en) *  20050107  20110111  First Data Corporation  Software for providing based on shared knowledge public keys having same private key 
CN1262087C (en) *  20050114  20060628  南相浩  Method for cipher key generation based on identification 
US20060159269A1 (en) *  20050120  20060720  Matsushita Electric Industrial Co., Ltd.  Cryptographic system for resource starved CE device secure upgrade and reconfiguration 
US8396213B2 (en)  20050121  20130312  Certicom Corp.  Elliptic curve random number generation 
US7860802B2 (en) *  20050201  20101228  Microsoft Corporation  Flexible licensing architecture in content rights management systems 
US7594261B2 (en) *  20050208  20090922  Microsoft Corporation  Cryptographic applications of the Cartier pairing 
KR20070104939A (en)  20050225  20071029  콸콤 인코포레이티드  Small publickey based digital signatures for authentication 
US7822200B2 (en) *  20050307  20101026  Microsoft Corporation  Method and system for asymmetric key security 
US7739500B2 (en) *  20050307  20100615  Microsoft Corporation  Method and system for consistent recognition of ongoing digital relationships 
US7680268B2 (en)  20050315  20100316  Microsoft Corporation  Elliptic curve point octupling using single instruction multiple data processing 
US7702098B2 (en) *  20050315  20100420  Microsoft Corporation  Elliptic curve point octupling for weighted projective coordinates 
US7657456B2 (en) *  20050318  20100202  Pitney Bowes Inc.  Method and system for electronic voting using identity based encryption 
US7634085B1 (en) *  20050325  20091215  Voltage Security, Inc.  Identitybasedencryption system with partial attribute matching 
US20060238304A1 (en) *  20050421  20061026  Sean Loving  System and method for adapting an FRID tag reader to its environment 
US7659819B2 (en)  20050421  20100209  Skyetek, Inc.  RFID reader operating system and associated architecture 
US20060253415A1 (en) *  20050421  20061109  Sayan Chakraborty  Datadefined communication device 
US20060238305A1 (en) *  20050421  20061026  Sean Loving  Configurable RFID reader 
US20060238303A1 (en) *  20050421  20061026  Sean Loving  Adaptable RFID reader 
US20060238302A1 (en) *  20050421  20061026  Sean Loving  System and method for configuring an RFID reader 
US8091142B2 (en) *  20050426  20120103  Microsoft Corporation  Supplementary trust model for software licensing/commercial digital distribution policy 
KR100635280B1 (en) *  20050427  20061011  삼성전자주식회사  Security method using electronic signature 
JP4646691B2 (en) *  20050510  20110309  株式会社エヌ・ティ・ティ・データ  Encryption communication system, the secret key issuing device, and, programs 
US7720221B2 (en) *  20050520  20100518  Certicom Corp.  Privacyenhanced epassport authentication protocol 
JP4723909B2 (en) *  20050527  20110713  株式会社日立製作所  Data exchange method, data exchange management apparatus and a data exchange management program 
US7649999B2 (en) *  20050608  20100119  Iris Anshel  Method and apparatus for establishing a key agreement protocol 
US8356175B2 (en) *  20050629  20130115  Intel Corporation  Methods and apparatus to perform associated security protocol extensions 
US8477940B2 (en) *  20050715  20130702  Tyfone, Inc.  Symmetric cryptography with user authentication 
US8189788B2 (en) *  20050715  20120529  Tyfone, Inc.  Hybrid symmetric/asymmetric cryptography with user authentication 
US7627760B2 (en) *  20050721  20091201  Microsoft Corporation  Extended authenticated key exchange 
JP2007036364A (en) *  20050722  20070208  Nec Corp  Time device, encrypting device, decrypting device, and encrypting/decrypting system 
US7694141B2 (en)  20050726  20100406  Microsoft Corporation  Extended authenticated key exchange with key confirmation 
US8190895B2 (en) *  20050818  20120529  Microsoft Corporation  Authenticated key exchange with derived ephemeral keys 
US7908482B2 (en) *  20050818  20110315  Microsoft Corporation  Key confirmed authenticated key exchange with derived ephemeral keys 
US20070046431A1 (en) *  20050831  20070301  Skyetek, Inc.  System and method for combining RFID tag memory 
US20070046467A1 (en) *  20050831  20070301  Sayan Chakraborty  System and method for RFID reader to reader communication 
FR2890201A1 (en) *  20050831  20070302  Proton World Internatinal Nv  Digital data e.g. music files, storing method for e.g. digital floppy disk, involves encrypting digital data using symmetric algorithm with encryption key independent to recorder, and transferring key onto physical medium or microcircuit 
US20070206786A1 (en) *  20050831  20070906  Skyetek, Inc.  Rfid security system 
FR2892251A1 (en) *  20051014  20070420  Gemplus Sa  Cryptographic method using a basic encryption system on the identity 
US20070104323A1 (en) *  20051104  20070510  Pitney Bowes Incorporated  Method and system for providing privacy to sender of a mail piece 
US20090083190A1 (en) *  20051201  20090326  Toshiyuki Isshiki  System and Method for Electronic Bidding 
US9165411B2 (en) *  20051216  20151020  Pitney Bowes Inc.  Method and system for embedding mailer specified mailing instructions on a mail piece to automate mail processing 
US20080022160A1 (en) *  20051230  20080124  Skyetek, Inc.  Malware scanner for rfid tags 
US7570164B2 (en) *  20051230  20090804  Skyetek, Inc.  System and method for implementing virtual RFID tags 
JP4688886B2 (en) *  20060111  20110525  三菱電機株式会社  Elliptic curve cryptosystem parameter generator and elliptic curve cryptosystems, and elliptic curve encryption parameter generating program 
US8180047B2 (en)  20060113  20120515  Microsoft Corporation  Trapdoor pairings 
US9137012B2 (en) *  20060203  20150915  Emc Corporation  Wireless authentication methods and apparatus 
US8094810B2 (en) *  20060203  20120110  Massachusetts Institute Of Technology  Unidirectional proxy reencryption 
US20070206797A1 (en) *  20060301  20070906  Skyetek, Inc.  Seamless rfid tag security system 
GB2436910B (en) *  20060403  20110216  Identum Ltd  Electronic Data Communication System 
US8311214B2 (en) *  20060424  20121113  Motorola Mobility Llc  Method for elliptic curve public key cryptographic validation 
US9002018B2 (en) *  20060509  20150407  Sync Up Technologies Corporation  Encryption key exchange system and method 
US7434726B2 (en) *  20060515  20081014  Pitney Bowes Inc.  Method and system for postdating of financial transactions 
US8121289B2 (en) *  20060531  20120221  France Telecom  Cryptographic method with integrated encryption and revocation, system, device and programs for implementing this method 
FR2901940B1 (en) *  20060531  20121214  Oberthur Card Syst Sa  Method for generation of a private key and processes encryption and deciphering a message 
US9769158B2 (en) *  20060607  20170919  Red Hat, Inc.  Guided enrollment and login for token users 
JP4868131B2 (en) *  20060615  20120201  ネッツエスアイ東洋株式会社  Electronic tally verification system 
JP4556917B2 (en) *  20060622  20101006  日本電気株式会社  Determination system, the determination method, determination apparatus and program 
US8670564B1 (en)  20060814  20140311  Key Holdings, LLC  Data encryption system and method 
US8548167B2 (en) *  20060817  20131001  Nagravision S.A.  System for traceable decryption of bandwidthefficient broadcast of encrypted messages and security module revocation method used for securing broadcasted messages 
US20080170701A1 (en) *  20060822  20080717  Ntt Data Corporation  Delegation system for decryption rights 
US20080065729A1 (en) *  20060908  20080313  Pitney Bowes Incorporated  Method and system for service provider to be compensated for delivering email messages while reducing amount of unsolicited email messages 
US7885406B2 (en) *  20061010  20110208  Microsoft Corporation  Computing endomorphism rings of Abelian surfaces over finite fields 
US20080137859A1 (en) *  20061206  20080612  Ramanathan Jagadeesan  Public key passing 
JP2008152737A (en) *  20061220  20080703  Nippon Telegr & Teleph Corp <Ntt>  Service provision server, authentication server, and authentication system 
GB0705494D0 (en) *  20070322  20070502  Ibm  A method and system for a subscription to a symmetric key 
US7859411B2 (en)  20070330  20101228  Skyetek, Inc.  RFID tagged item trajectory and location estimation system and method 
US8669845B1 (en)  20070330  20140311  Vail Resorts, Inc.  RFID skier monitoring systems and methods 
US20080297326A1 (en) *  20070330  20081204  Skyetek, Inc.  Low Cost RFID Tag Security And Privacy System And Method 
US20080290995A1 (en) *  20070330  20081127  Skyetek, Inc.  System and method for optimizing communication between an rfid reader and an rfid tag 
US8705744B2 (en) *  20070405  20140422  Koninklijke Philips N.V.  Wireless sensor network key distribution 
JP2008301391A (en) *  20070604  20081211  Murata Mach Ltd  Broadcasting encryption system, encryption communication method, decoder and decoding program 
US8676715B2 (en)  20070606  20140318  Pitney Bowes Inc.  System and method for authenticating indicia using identitybased signature scheme 
US8631419B2 (en) *  20070629  20140114  Microsoft Corporation  System and methods for disruption detection, management, and recovery 
DE102007033848A1 (en)  20070718  20090122  Freisleben, Bernd, Prof. Dr.  Method for verification of ownership of terminal address of communications device in network, involves verifying ownership of terminal address by communications device belonging to it, by private cryptographic key 
DE102007033847A1 (en)  20070718  20090122  Bernd Prof. Dr. Freisleben  Method for cryptographic key agreement between two communication devices in Internet protocol communications networks, involves arranging one or multiple Network address translation routers between two communication devices 
DE102007033846A1 (en)  20070718  20090122  Freisleben, Bernd, Prof. Dr.  Cryptographic key generating method for encrypted digital communication between communication devices, involves converting end product address of communication device into part of key, and utilizing address for key agreement 
DE102007033845A1 (en)  20070718  20090122  Bernd Prof. Dr. Freisleben  Public/private cryptographic key producing method for executing key agreement in digital data carrier, involves converting terminal end point address into key portion by applying inverse function of trap door oneway function for agreement 
KR101490687B1 (en)  20070820  20150206  삼성전자주식회사  Method and apparatus for sharing secret information between devices in home network 
US7890763B1 (en) *  20070914  20110215  The United States Of America As Represented By The Director, National Security Agency  Method of identifying invalid digital signatures involving batch verification 
US8700894B2 (en) *  20071017  20140415  Pitney Bowes Inc.  Method and system for securing routing information of a communication using identitybased encryption scheme 
EP2217995A4 (en) *  20071026  20121121  Telcordia Tech Inc  Method and system for secure session establishment using identitybased encryption (vdtls) 
JP5286748B2 (en) *  20071109  20130911  ソニー株式会社  The information processing apparatus, a key setting method, and program 
CN101179380A (en) *  20071119  20080514  上海交通大学;华为技术有限公司  Bidirectional authentication method, system and network terminal 
KR20090052199A (en) *  20071120  20090525  삼성전자주식회사  Storage device, terminal device using the storage device, and, method thereof 
JP4907502B2 (en) *  20071120  20120328  日本電信電話株式会社  Behavior certificate issuing method, behavior certificate issuing device, action certificate issuance program and behavioral certificate issuance and verification system 
JP5365072B2 (en) *  20071211  20131211  ソニー株式会社  The key generation device, encryption device, reception device, key generation method, encryption method, key processing method, and program 
US20090153290A1 (en) *  20071214  20090618  Farpointe Data, Inc., A California Corporation  Secure interface for access control systems 
US8806207B2 (en) *  20071221  20140812  Cocoon Data Holdings Limited  System and method for securing data 
CN101521569B (en) *  20080228  20130424  华为技术有限公司  Method, equipment and system for realizing service access 
KR101484110B1 (en) *  20080229  20150128  삼성전자주식회사  Memory controller and memory device thereof 
RU2505855C2 (en) *  20080523  20140127  Конинклейке Филипс Электроникс Н.В.  Identificationbased data entity encryption for safe access thereof 
US8259949B2 (en)  20080527  20120904  Intel Corporation  Methods and apparatus for protecting digital content 
JP5118556B2 (en) *  20080604  20130116  日本電信電話株式会社  Key delivery method, key distribution system, a client device, a key server device, those programs 
JP5027742B2 (en) *  20080619  20120919  日本電信電話株式会社  Secret information transmission system, secret information transmission method, the secret information management server, the cryptographic device, the secret information transmission program 
US8656177B2 (en) *  20080623  20140218  Voltage Security, Inc.  Identitybasedencryption system 
US8761390B2 (en) *  20080630  20140624  Gm Global Technology Operations  Production of cryptographic keys for an embedded processing device 
US8737614B1 (en) *  20080707  20140527  Voltage Security, Inc.  Document imaging system with identitybased encryption 
CN101350060B (en) *  20080723  20110601  西安西电捷通无线网络通信股份有限公司  Data safety access method being suitable for electronic label 
US8358783B2 (en) *  20080811  20130122  Assa Abloy Ab  Secure wiegand communications 
EP2157526B1 (en) *  20080814  20140430  Assa Abloy Ab  RFID reader with embedded attack detection heuristics 
US7995765B2 (en) *  20080828  20110809  Red Hat, Inc.  Sharing a secret using hyperplanes over GF(q) 
US7995764B2 (en) *  20080828  20110809  Red Hat, Inc.  Sharing a secret using hyperplanes over GF(2m) 
US8520854B2 (en) *  20080828  20130827  Red Hat, Inc.  Sharing a secret using polynomials over polynomials 
US8675877B2 (en) *  20080829  20140318  Red Hat, Inc.  Sharing a secret via linear interpolation 
US8559637B2 (en)  20080910  20131015  Verizon Patent And Licensing Inc.  Securing information exchanged via a network 
JP5491015B2 (en) *  20080925  20140514  Ｋｄｄｉ株式会社  Mediation device and program for setting the radio communication channel 
EP2359524B1 (en) *  20081014  20160831  Koninklijke Philips N.V.  Method and apparatus for pseudonym generation and authentication 
CN101420303B (en)  20081212  20110202  广州杰赛科技股份有限公司  Communication method for audio data and apparatus thereof 
JP5097102B2 (en) *  20081225  20121212  日本電信電話株式会社  Hierarchical id based encryption device and decryption device, the methods, program, and recording medium 
JP5134555B2 (en) *  20090107  20130130  日本電信電話株式会社  The key generation device, encryption device, a decryption device, an encryption system, key generation method, encryption method, decryption method, a program, and a recording medium 
JP5268066B2 (en) *  20090116  20130821  日本電信電話株式会社  Conversion computing device, the method, program and recording medium 
US9165154B2 (en) *  20090216  20151020  Microsoft Technology Licensing, Llc  Trusted cloud computing and services framework 
US8341427B2 (en) *  20090216  20121225  Microsoft Corporation  Trusted cloud computing and services framework 
US8510558B2 (en)  20090217  20130813  Alcatel Lucent  Identity based authenticated key agreement protocol 
EP2222015A1 (en) *  20090219  20100825  Thomson Licensing  Method and device for hashing onto points of an elliptic curve 
US8837718B2 (en) *  20090327  20140916  Microsoft Corporation  Userspecified sharing of data via policy and/or inference from a hierarchical cryptographic store 
US9704159B2 (en) *  20090515  20170711  Entit Software Llc  Purchase transaction system with encrypted transaction information 
US8571995B2 (en) *  20090602  20131029  Voltage Security, Inc.  Purchase transaction system with encrypted payment card data 
KR101377352B1 (en) *  20090717  20140325  알까뗄 루슨트  Digital rights management (drm) method and equipment in small and medium enterprise (sme) and method for providing drm service 
US8850203B2 (en) *  20090828  20140930  Alcatel Lucent  Secure key management in multimedia communication system 
US8301883B2 (en) *  20090828  20121030  Alcatel Lucent  Secure key management in conferencing system 
US8510835B1 (en)  20090918  20130813  Trend Micro Incorporated  Techniques for protecting data in cloud computing environments 
US8826013B1 (en)  20090923  20140902  Trend Micro Incorporated  Protection of customer data in cloud virtual machines using a central management server 
US8219792B2 (en) *  20091006  20120710  Dell Products L.P.  System and method for safe information handling system boot 
JP4802274B2 (en) *  20091030  20111026  インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｓｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ  Message transmission and reception method 
US8666812B1 (en) *  20091110  20140304  Google Inc.  Distributing content based on transaction information 
US8219810B2 (en) *  20091113  20120710  Palo Alto Research Center Incorporated  Method and system for facilitating throttling of interpolationbased authentication 
JP5325755B2 (en) *  20091211  20131023  株式会社エヌ・ティ・ティ・データ  The ciphertext decryption authority transfer system, the ciphertext decryption authority transfer method, the ciphertext conversion device, the decryption authority holder for apparatus and ciphertext conversion program 
EP2348450B1 (en) *  20091218  20131106  CompuGroup Medical AG  Database system, computer system, and computerreadable storage medium for decrypting a data record 
EP2348452B1 (en)  20091218  20140702  CompuGroup Medical AG  A computer implemented method for sending a message to a recipient user, receiving a message by a recipient user, a computer readable storage medium and a computer system 
EP2365456B1 (en)  20100311  20160720  CompuGroup Medical SE  Data structure, method and system for predicting medical conditions 
EP2348447B1 (en)  20091218  20140716  CompuGroup Medical AG  A computer implemented method for generating a set of identifiers from a private key, computer implemented method and computing device 
EP2525339A4 (en) *  20100113  20130911  Mitsubishi Electric Corp  Secret retrieval system, public parameter generation device, encryption device, user secret key generation device, query issue device, retrieval device, computer program, secret retrieval method, public parameter generation method, encryption method, user secret key generation method, query issue method, and retrieval method 
CN102713995B (en)  20100115  20150624  三菱电机株式会社  Confidential search system and encryption processing system 
US8488783B2 (en) *  20100219  20130716  Nokia  Method and apparatus for applying recipient criteria in identitybased encryption 
ES2524075T3 (en) *  20100303  20141204  Nagravision S.A.  A method for managing a group of revocation terminals 
US9025767B2 (en) *  20100324  20150505  Nokia Corporation  Method and apparatus for querying content protected by identitybased encryption 
US8553878B2 (en) *  20100414  20131008  Apple Inc.  Data transformation system using cyclic groups 
US9772834B2 (en) *  20100427  20170926  Red Hat, Inc.  Exportable encoded identifications of networked machines 
JP5424974B2 (en) *  20100427  20140226  三菱電機株式会社  Cryptographic processing system, the key generation device, encryption device, a decryption device, the signature processing system, the signature device and the verification device 
US8423764B2 (en)  20100623  20130416  Motorola Solutions, Inc.  Method and apparatus for key revocation in an attributebased encryption scheme 
RU2452111C1 (en) *  20101117  20120527  ЗАО Институт инфокоммуникационных технологий  Method for threshold key generating for protection system based on identity data 
US8656484B2 (en)  20101228  20140218  Authernative, Inc.  System and method for mutually authenticated cryptographic key exchange using matrices 
US8621227B2 (en)  20101228  20131231  Authernative, Inc.  System and method for cryptographic key exchange using matrices 
JP5612494B2 (en) *  20110121  20141022  日本電信電話株式会社  Timed cryptosystem, timed encryption method using the function code, device, program 
US20130042112A1 (en) *  20110212  20130214  CertiVox Ltd.  Use of noninteractive identity based key agreement derived secret keys with authenticated encryption 
US8661240B2 (en)  20110429  20140225  International Business Machines Corporation  Joint encryption of data 
US9544144B2 (en) *  20110429  20170110  International Business Machines Corporation  Data encryption 
US8644510B2 (en) *  20110511  20140204  Alcatel Lucent  Discovery of security associations for key management relying on public keys 
WO2012165889A3 (en) *  20110531  20130328  삼성에스디에스 주식회사  Idbased encryption and signature method and terminal 
US8891772B2 (en) *  20110617  20141118  Microsoft Corporation  Cloud key escrow system 
US9203621B2 (en) *  20110711  20151201  HewlettPackard Development Company, L.P.  Policybased data management 
WO2013012734A1 (en) *  20110715  20130124  AlcatelLucent Usa Inc.  Secure group messaging 
US8619986B2 (en) *  20110721  20131231  Patton Protection Systems LLC  Systems and methods for secure communication using a communication encryption bios based upon a message specific identifier 
US8892875B1 (en)  20110729  20141118  Trend Micro Incorporated  Methods and apparatus for controlling access to encrypted computer files 
JP2013042315A (en) *  20110812  20130228  Sony Corp  Information processing device and information processing method 
US8948381B2 (en) *  20110909  20150203  Fujitsu Limited  Conditional key generation based on expiration date of data 
EP2748963A4 (en) *  20110930  20150617  Ranganath C Abeyweera  Method, system and apparatus for a communications client program and an associated transfer server for onymous and secure communications 
US9154302B2 (en)  20120125  20151006  CertiVox Ltd.  System and method for secure twofactor authenticated IDbased key exchange and remote login using an insecure token and simple secondfactor such as a PIN number 
US9065637B2 (en) *  20120125  20150623  CertiVox Ltd.  System and method for securing private keys issued from distributed private key generator (DPKG) nodes 
US20140372752A1 (en) *  20120203  20141218  David Sallis  Method and database system for secure storage and communication of information 
US8694771B2 (en)  20120210  20140408  Connect In Private Panama Corp.  Method and system for a certificateless authenticated encryption scheme using identitybased encryption 
DK2648170T3 (en) *  20120406  20150223  Kapsch Trafficcom Ag  A method for detecting a vehicle speed violation 
JP5990406B2 (en) *  20120606  20160914  株式会社東海理化電機製作所  Electronic key registration method 
JP5985894B2 (en) *  20120606  20160906  株式会社東海理化電機製作所  Electronic key registration method 
FR2992509B1 (en) *  20120621  20170526  Commissariat Energie Atomique  Device and method for generating a session key 
JP6057150B2 (en) *  20120730  20170111  雅浩 満保  Public key encryption system, the receiving device, the public key encryption method, a program, and a recording medium 
US20140122900A1 (en) *  20121026  20140501  Infosys Limited  Providing searching over encrypted keywords in a database 
KR101493212B1 (en) *  20121031  20150223  삼성에스디에스 주식회사  Method and system for idbased encryption and decryption 
US9230072B1 (en) *  20121217  20160105  Creative Information Technology, Inc.  Dynamic identity program templates 
US8763085B1 (en)  20121219  20140624  Trend Micro Incorporated  Protection of remotely managed virtual machines 
US9197422B2 (en) *  20130124  20151124  Raytheon Company  System and method for differential encryption 
US9020151B1 (en)  20130304  20150428  Trend Micro Incorporated  Secure realtime data replication with disk encryption and key management system 
GB201309702D0 (en)  20130530  20130717  Certivox Ltd  Security 
US8971540B2 (en)  20130530  20150303  CertiVox Ltd.  Authentication 
US9106644B2 (en)  20130530  20150811  CertiVox Ltd.  Authentication 
CN104219047B (en) *  20130531  20171215  华为技术有限公司  A method and apparatus for signature verification 
KR101460541B1 (en) *  20130715  20141111  고려대학교 산학협력단  Public encryption method based on user ID 
US9197419B1 (en)  20131014  20151124  Trend Micro Incorporated  Security system for data stored in the cloud 
US9275242B1 (en)  20131014  20160301  Trend Micro Incorporated  Security system for cloudbased emails 
JP5915629B2 (en) *  20131128  20160511  トヨタ自動車株式会社  Communication method in a data sharing system, data sharing system, and the communication node 
US9219722B2 (en)  20131211  20151222  Globalfoundries Inc.  Unclonable ID based chiptochip communication 
US9628516B2 (en)  20131212  20170418  Hewlett Packard Enterprise Development Lp  Policybased data management 
US9515994B2 (en)  20140213  20161206  Infosys Limited  Keyword ordered storage, search and retrieval on encrypted data for multiuser scenario 
US20160269186A1 (en) *  20140505  20160915  Sypris Electronics, LLC.  Authentication system and device including physical unclonable function and threshold cryptography 
US9703979B1 (en) *  20140613  20170711  BicDroid Inc.  Methods and computer program products for encryption key generation and management 
US9619667B2 (en)  20140613  20170411  BicDroid Inc.  Methods, systems and computer program product for providing encryption on a plurality of devices 
GB201509499D0 (en) *  20150602  20150715  Certivox Ltd  Zkd 
Citations (13)
Publication number  Priority date  Publication date  Assignee  Title 

US4405829A (en) *  19771214  19830920  Massachusetts Institute Of Technology  Cryptographic communications system and method 
US4748668A (en) *  19860709  19880531  Yeda Research And Development Company Limited  Method, apparatus and article for identification and signature 
US5016276A (en) *  19860731  19910514  Kabushiki Kaisha Advance  Common cryptokey generation system and communication system using common cryptokeys 
US5146500A (en) *  19910314  19920908  Omnisec A.G.  Public key cryptographic system using elliptic curves over rings 
US5150411A (en) *  19901024  19920922  Omnisec  Cryptographic system allowing encrypted communication between users with a secure mutual cipher key determined without user interaction 
US5159632A (en) *  19910917  19921027  Next Computer, Inc.  Method and apparatus for public key exchange in a cryptographic system 
US5179301A (en) *  19890906  19930112  U.S. Philips Corporation  Switched current differentiator circuit for differentiating an input signal in the form of a sampled analog current 
US5271061A (en) *  19910917  19931214  Next Computer, Inc.  Method and apparatus for public key exchange in a cryptographic system 
US5272755A (en) *  19910628  19931221  Matsushita Electric Industrial Co., Ltd.  Public key cryptosystem with an elliptic curve 
US6061448A (en) *  19970401  20000509  Tumbleweed Communications Corp.  Method and system for dynamic server document encryption 
US6307935B1 (en) *  19910917  20011023  Apple Computer, Inc.  Method and apparatus for fast elliptic encryption with direct embedding 
US20020076042A1 (en) *  20001219  20020620  Ravi Sandhu  System and method for cryptokey generation and use in cryptosystem 
US6886096B2 (en) *  20021114  20050426  Voltage Security, Inc.  Identitybased encryption system 
Family Cites Families (14)
Publication number  Priority date  Publication date  Assignee  Title 

US5202921A (en)  19910401  19930413  International Business Machines Corporation  Method and apparatus for authenticating users of a communication system to each other 
JP2000515649A (en) *  19960807  20001121  バンカーズ・トラスト・コーポレーション  Concurrency electronic transaction by a trusted party can be seen 
US5982898A (en) *  19970307  19991109  At&T Corp.  Certification process 
JP3542895B2 (en) *  19970822  20040714  インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｓｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ  Time constraints encryption system 
JP3275812B2 (en) *  19971212  20020422  日本電気株式会社  Id authenticated key delivery method and apparatus as well as a machinereadable recording medium recording a program 
WO1999035783A1 (en) *  19980109  19990715  Cybersafe Corporation  Client side public key authentication method and apparatus with shortlived certificates 
US6446205B1 (en)  19981210  20020903  Citibank, N.A.  Cryptosystems with elliptic curves chosen by users 
JP4450969B2 (en)  20000502  20100414  隆一 境  Key sharing system, secret key generation device, the common key generation system, the cryptographic communication method, cryptographic communication system, and a recording medium 
US7239701B1 (en) *  20000502  20070703  Murata Machinery Ltd.  Key sharing method, secret key generating method, common key generating method and cryptographic communication method in IDNIKS cryptosystem 
JP2002164877A (en) *  20000914  20020607  Advanced Mobile Telecommunications Security Technology Research Lab Co Ltd  Key escrow and group communication method 
GB2370471B (en)  20001220  20040623  Director Government Comm Headq  Directoryless Public Key Cryptographic System and Method 
EP2224637B1 (en) *  20010813  20141008  The Board Of Trustees Of The Leland Stanford Junior University  Systems and methods for identitybased encryption 
FR2892251A1 (en) *  20051014  20070420  Gemplus Sa  Cryptographic method using a basic encryption system on the identity 
US8694771B2 (en) *  20120210  20140408  Connect In Private Panama Corp.  Method and system for a certificateless authenticated encryption scheme using identitybased encryption 
Patent Citations (14)
Publication number  Priority date  Publication date  Assignee  Title 

US4405829A (en) *  19771214  19830920  Massachusetts Institute Of Technology  Cryptographic communications system and method 
US4748668A (en) *  19860709  19880531  Yeda Research And Development Company Limited  Method, apparatus and article for identification and signature 
US5016276A (en) *  19860731  19910514  Kabushiki Kaisha Advance  Common cryptokey generation system and communication system using common cryptokeys 
US5179301A (en) *  19890906  19930112  U.S. Philips Corporation  Switched current differentiator circuit for differentiating an input signal in the form of a sampled analog current 
US5150411A (en) *  19901024  19920922  Omnisec  Cryptographic system allowing encrypted communication between users with a secure mutual cipher key determined without user interaction 
US5146500A (en) *  19910314  19920908  Omnisec A.G.  Public key cryptographic system using elliptic curves over rings 
US5272755A (en) *  19910628  19931221  Matsushita Electric Industrial Co., Ltd.  Public key cryptosystem with an elliptic curve 
US5271061A (en) *  19910917  19931214  Next Computer, Inc.  Method and apparatus for public key exchange in a cryptographic system 
US5159632A (en) *  19910917  19921027  Next Computer, Inc.  Method and apparatus for public key exchange in a cryptographic system 
US5581616A (en) *  19910917  19961203  Next Software, Inc.  Method and apparatus for digital signature authentication 
US6307935B1 (en) *  19910917  20011023  Apple Computer, Inc.  Method and apparatus for fast elliptic encryption with direct embedding 
US6061448A (en) *  19970401  20000509  Tumbleweed Communications Corp.  Method and system for dynamic server document encryption 
US20020076042A1 (en) *  20001219  20020620  Ravi Sandhu  System and method for cryptokey generation and use in cryptosystem 
US6886096B2 (en) *  20021114  20050426  Voltage Security, Inc.  Identitybased encryption system 
Cited By (23)
Publication number  Priority date  Publication date  Assignee  Title 

US8271788B2 (en) *  20061017  20120918  Trend Micro Incorporated  Software registration system 
US20080091947A1 (en) *  20061017  20080417  Andrew John Dancer  Software registration system 
US8290146B2 (en) *  20070119  20121016  Mitsubishi Electric Corporation  Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus 
US20100104094A1 (en) *  20070119  20100429  Mitsubishi Electric Corporation  Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus 
US20120233465A1 (en) *  20070405  20120913  International Business Machines Corporation  Distribution of Credentials 
US9112680B2 (en) *  20070405  20150818  International Business Machines Corporation  Distribution of credentials 
US9847977B2 (en) *  20070629  20171219  Microsoft Technology Licensing, Llc  Confidential mail with tracking and authentication 
US20090006851A1 (en) *  20070629  20090101  Microsoft Corporation  Confidential mail with tracking and authentication 
US20090030778A1 (en) *  20070723  20090129  Motivepath, Inc.  System, method and apparatus for secure multiparty location based services 
US20090257594A1 (en) *  20080415  20091015  Amjad Qureshi  Secure debug interface and memory of a media security circuit and method 
US8090108B2 (en) *  20080415  20120103  Adaptive Chips, Inc.  Secure debug interface and memory of a media security circuit and method 
US8045708B2 (en) *  20080521  20111025  Apple Inc.  Discrete key generation method and apparatus 
US20090319769A1 (en) *  20080521  20091224  Apple Inc.  Discrete key generation method and apparatus 
US20100119058A1 (en) *  20081111  20100513  Seiichi Matsuda  Information processing apparatus, information processing method, and program 
US8166203B1 (en) *  20090529  20120424  Google Inc.  Server selection based upon time and query dependent hashing 
WO2012129640A3 (en) *  20110401  20121206  Certicom Corp.  Identitybased decryption 
US9490974B2 (en) *  20110401  20161108  Certicom Corp.  Identitybased decryption 
EP2700189A4 (en) *  20110401  20150318  Certicom Corp  Identitybased decryption 
US20120254616A1 (en) *  20110401  20121004  Certicom Corporation  IdentityBased Decryption 
US9172530B2 (en) *  20120531  20151027  Samsung Sds Co., Ltd.  Apparatus and method for generating secret key for IDbased encryption system and recording medium having program recorded thereon for causing computer to execute the method 
US20130322620A1 (en) *  20120531  20131205  Samsung Sds Co., Ltd.  Apparatus and method for generating secret key for idbased encryption system and recording medium having program recorded thereon for causing computer to execute the method 
US20150120650A1 (en) *  20131030  20150430  Gordon E. Seay  Methods and Systems for Utilizing Global Entities In Software Applications 
US20160301531A1 (en) *  20150409  20161013  Qualcomm Incorporated  Proof of work based user identification system 
Also Published As
Publication number  Publication date  Type 

DE60236094D1 (en)  20100602  grant 
EP1425874A4 (en)  20090415  application 
JP2005500740A (en)  20050106  application 
EP1425874A2 (en)  20040609  application 
EP2429116A2 (en)  20120314  application 
US20100208895A1 (en)  20100819  application 
US7634087B2 (en)  20091215  grant 
US20070041583A1 (en)  20070222  application 
JP5933786B2 (en)  20160615  grant 
US20030081785A1 (en)  20030501  application 
EP2429116B1 (en)  20130710  grant 
EP2224637A3 (en)  20120523  application 
US9356779B2 (en)  20160531  grant 
JP2012032843A (en)  20120216  application 
US20120159188A1 (en)  20120621  application 
WO2003017559A2 (en)  20030227  application 
US8130964B2 (en)  20120306  grant 
WO2003017559A3 (en)  20030710  application 
EP2224637B1 (en)  20141008  grant 
EP1425874B1 (en)  20100421  grant 
US7113594B2 (en)  20060926  grant 
EP2429116A3 (en)  20120530  application 
EP2224637A2 (en)  20100901  application 
JP2015144495A (en)  20150806  application 
JP2011151866A (en)  20110804  application 
Similar Documents
Publication  Publication Date  Title 

Balfanz et al.  Secret handshakes from pairingbased key agreements  
Horwitz et al.  Toward hierarchical identitybased encryption  
Desmedt  Some recent research aspects of threshold cryptography  
Chen et al.  A New IDbased Group Signature Scheme from Bilinear Pairings.  
Boldyreva et al.  Identitybased encryption with efficient revocation  
Chen et al.  Improved identitybased signcryption  
Liu et al.  Certificateless signcryption scheme in the standard model  
Baek et al.  Formal proofs for the security of signcryption  
Baek et al.  Certificateless public key encryption without pairing  
Baek et al.  Efficient multireceiver identitybased encryption and its application to broadcast encryption  
Libert et al.  Efficient revocation and threshold pairing based cryptosystems  
US6473508B1 (en)  Autorecoverable autocertifiable cryptosystems with unescrowed signatureonly keys  
US6490352B1 (en)  Cryptographic elliptic curve apparatus and method  
Bentahar et al.  Generic constructions of identitybased and certificateless KEMs  
Zhang et al.  New Proxy Signature, Proxy Blind Signature and Proxy Ring Signature Schemes from Bilinear Pairing.  
Baek et al.  Identitybased threshold signature scheme from the bilinear pairings  
Liu et al.  Selfgeneratedcertificate public key cryptography and certificateless signature/encryption scheme in the standard model  
Goyal  Reducing trust in the PKG in identity based cryptosystems  
US6389136B1 (en)  AutoRecoverable and Autocertifiable cryptosystems with RSA or factoring based keys  
US6122742A (en)  Autorecoverable and autocertifiable cryptosystem with unescrowed signing keys  
Li et al.  Certificateless signature and proxy signature schemes from bilinear pairings  
Au et al.  Malicious KGC attacks in certificateless cryptography  
Ivan et al.  Proxy Cryptography Revisited.  
Baek et al.  A survey of identitybased cryptography  
Han et al.  Privacypreserving decentralized keypolicy attributebased encryption 
Legal Events
Date  Code  Title  Description 

AS  Assignment 
Owner name: UNIVERSITY OF CALIFORNIA DAVIS, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FRANKLIN, MATTHEW;REEL/FRAME:018145/0644 Effective date: 20060712 Owner name: BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BONEH, DAN;REEL/FRAME:018121/0027 Effective date: 20060719 

FPAY  Fee payment 
Year of fee payment: 4 

AS  Assignment 
Owner name: VENTURE LENDING & LEASING VII, INC., CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:VOLTAGE SECURITY, INC.;REEL/FRAME:032170/0273 Effective date: 20140131 Owner name: VENTURE LENDING & LEASING VI, INC., CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:VOLTAGE SECURITY, INC.;REEL/FRAME:032170/0273 Effective date: 20140131 

AS  Assignment 
Owner name: VOLTAGE SECURITY, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:VENTURE LENDING & LEASING VI, INC.;VENTURE LENDING & LEASING VII, INC.;REEL/FRAME:035110/0726 Effective date: 20150227 

FPAY  Fee payment 
Year of fee payment: 8 

AS  Assignment 
Owner name: JPMORGAN CHASE BANK, N.A., DELAWARE Free format text: SECURITY INTEREST;ASSIGNORS:ATTACHMATE CORPORATION;BORLAND SOFTWARE CORPORATION;NETIQ CORPORATION;AND OTHERS;REEL/FRAME:044183/0718 Effective date: 20170901 Owner name: JPMORGAN CHASE BANK, N.A., DELAWARE Free format text: SECURITY INTEREST;ASSIGNORS:ENTIT SOFTWARE LLC;ARCSIGHT, LLC;REEL/FRAME:044183/0577 Effective date: 20170901 