US7555656B2

Exclusive encryption

Summary by NHIP

Exclusive Encryption System

The system generates encrypted directory names from plaintext names without decrypting them during verification. It encodes a mapped name, then encrypts the encoded result, while verifying syntax and uniqueness without decryption.

Claim Score by NHIP

Read claim 29, the broadest

Abstract

An exclusive encryption system is established using multiple computing devices. The exclusive encryption system allows for the exclusion of certain plaintext (e.g., by one of the computing devices) and ciphertext (e.g., by another of the computing devices) while at the same time maintaining the privacy created by the encryption (e.g., so the other computing device cannot see the plaintext). The exclusive encryption system may be implemented as part of a serverless distributed file system with directory entries (e.g., file names or folder names) being the plaintext, or alternatively as part of other systems.

US7555656B2, drawing sheet 1 — Sheet 1 of 15

Term

Term ended

Expired 13 January 2023, 3.7 years ago.

32 claims: 5 independent, 27 dependent

1
A system comprising:a source processor;a source memory;a source computing device component to generate an encrypted directory name based on a plaintext name that conforms to a syntax, wherein the source computing component generates the encrypted directory name by a method, the method comprising: receiving a plaintext name;generating, based on the plaintext name, a mapped name;encoding the mapped name;and encrypting the encoded name;and a recipient processor;a recipient memory;and a recipient computing component, electronically coupled to the source computing component, to perform a method, the method comprising: receiving the encrypted directory name;verifying that the encrypted directory name is an encryption of a plaintext name that conforms to the syntax without decrypting the encrypted directory name;verifying that the encrypted directory name is an encryption of a plaintext name that is not a duplicative name without decrypting the encrypted directory name;and processing the encrypted directory name based on the verifying, wherein the processing comprises storing the encrypted directory name, forwarding the encrypted directory name, or determining that the encrypted directory name is invalid.
19
A computing device comprising:a processor;a memory;a client component configured to encrypt only directory entries that are syntactically legal, and to encrypt the directory entries in a manner that allows another device to verify, without decrypting the encrypted entries, that the directory entries are not identical to any other directory entries maintained by the other device, wherein to encrypt the directory entries is to: receive a plaintext name of the directory entry;generate, based on the plaintext name, a mapped name;encode the mapped name;and encrypt the encoded name;and a server component configured to receive encrypted directory entries, to verify that the received encrypted directory entries are encryptions of syntactically legal directory entries, arid to verify that the received encrypted directory entries are not encryptions of directory entries identical to any other directory entries maintained by the device, and to process the encrypted directory entries based on the verifying.
22
One or more computer storage media having stored thereon a plurality of instructions that, when executed by one or more processors of a device, causes the one or more processors to perform a method, the method comprising:encrypting only directory entries that are syntactically legal in a manner that allows another device to verify, without decrypting the encrypted directory entries, that the directory entries are not identical to any other directory entries maintained by the other device, wherein encrypting one of the directory entries further comprises: receiving a plaintext name of the one directory entry;generating, based on the plaintext name, a mapped name;encoding the mapped name;and encrypting the encoded name;receiving additional encrypted directory entries;verifying that the received additional encrypted directory entries are encryptions of syntactically legal directory entries;verifying that the received additional encrypted directory entries are not encryptions of directory entries identical to any other directory entries maintained by the device;and processing each of the received additional encrypted directory entries based on the verifying.
25
A method, implemented in a device, the method comprising:encrypting only directory entries that are syntactically legal;in a manner that allows each of one or more other devices to verify, without decrypting the encrypted directory entries, that the directory entries are not identical to any other directory entries maintained by the other device, wherein encrypting the directory entries comprises, for each directory entry: receiving a plaintext name of the directory entry;generating, based on the plaintext name, a mapped name;encoding the mapped name;and encrypting the encoded name;receiving additional encrypted directory entries;verifying that the received additional encrypted directory entries are encryptions of syntactically legal directory entries;verifying that the received additional encrypted directory entries are not encryptions of directory entries identical to any other directory entries maintained by the device;and processing the received additional encrypted directory entries based on the verifying, wherein a device comprises a memory and a processor.
29
Broadest claimClaim Score 56, average(NHIP)A system comprising:a processor;a memory;means for encrypting only directory entries that are syntactically legal, and for encrypting the directory entries in a manner that allows each of one or more other systems to verify, without decrypting the encrypted directory entries, that the directory entries are not identical to any other directory entries maintained by the other system, wherein the means for encrypting comprises means for, for each directory entry: receiving a plaintext name of the directory entry;generating, based on the plaintext name, a mapped name;encoding the mapped name;and encrypting the encoded name;means for receiving additional encrypted directory entries;means for verifying that the received additional encrypted directory entries are encryptions of syntactically legal directory entries;and means for verifying that the received additional encrypted directory entries are not encryptions of directory entries identical to any other directory entries maintained by the system;and means for processing the received additional encrypted directory entries based of the verifying.

Independent claims5

114 paragraphs in 7 sections, as filed

This application is a continuation application of U.S. patent application Ser. No. 09/764,962, filed Jan. 17, 2001, entitled “Exclusive Encryption” to John R. Douceur, Atul Adya, Josh D. Benaloh, and Gideon A. Yuval, which is hereby incorporated by reference herein.

TECHNICAL FIELD

This invention relates to cryptography, and more particularly to cryptosystems that enable enforcement of syntactical and/or semantic requirements on encrypted data.

BACKGROUND OF THE INVENTION

As computer technology has advanced, so too has the need for computer security. One significant area of concern with computer security is the security of data stored by a user of the computer. Such security can include, for example, security against another user reading the data, another user modifying the data (either maliciously or unintentionally), etc. One manner in which such security is currently provided is through encryption. Using encryption, only those users who are supposed to have access to the data (e.g., those users with the decryption key) are able to decrypt and read (and/or modify) the data.

However, situations arise in which encryption creates additional problems. One such situation is in the case where the data is to be verified as being in accordance with a certain set of rules (e.g., a naming syntax), while at the same time maintaining the security/privacy of the data. Current systems typically cannot perform such verifications without reading the underlying data.

For example, in some situations where computers are networked together it would be desirable to have a distributed file system in which different files could be stored on different machines in the network. However, in order to maintain security of the data in the files, it would be beneficial to be able to render both the data and the filename itself unreadable at the computer on which the file is stored, thereby preventing another unauthorized user from gathering information about the data by either reading the data file or the filename. However, maintaining a directory of such encrypted/protected filenames can lead to difficulties, especially due to the fact that the user of the computer on which the data file or filename is stored may not be authorized to read the file. Care must be taken to ensure that the filename syntax is not violated and that duplicate filenames do not exist. Current systems do not have the ability to maintain such a directory of non-duplicate filenames that do not violate the naming syntax while at the same time can be verified by a component that is not authorized to read the filenames.

The invention described below addresses these disadvantages, providing methods and systems for encryption that excludes syntactically illegal plaintext from being encrypted and that enables a party without access to encryption keys to exclude more than one item of ciphertext that decrypts to the same plaintext. For this reason, the invention is referred to as “exclusive encryption.”

SUMMARY OF THE INVENTION

Methods and systems for exclusive encryption are described herein.

According to one aspect, an exclusive encryption system is established using multiple computing devices. The exclusive encryption system allows for the exclusion of certain plaintext (e.g., by one of the computing devices) and ciphertext (e.g., by another of the computing devices) while at the same time maintaining the privacy created by the encryption (e.g., so the other computing device cannot see the plaintext).

According to another aspect, an exclusive encryption system is established as part of a serverless distributed file system. The file system is distributed among multiple computing devices, and each directory entry (e.g., a file name or folder name) is encrypted by the device creating (or otherwise using) the entry. The encryption process used ensures that the directory entry is syntactically legal and cannot be read by the device on which the entry is stored. Additionally, the device on which the entry is stored is able to verify the legality of the directory entry, and ensures that duplicate entries are not stored in the same directory.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings. The same numbers are used throughout the figures to reference like components and/or features.

<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an exemplary system in which certain embodiments of the invention can be implemented.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary network environment in which certain embodiments of the invention may be practiced.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an exemplary computing device such as may be used in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating an exemplary process for decrypting a received directory entry in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating an exemplary process for mapping a plaintext name to a mapped name in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating an exemplary process for decasifying a mapped name in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating an exemplary process for encoding a decasified name in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart illustrating an exemplary process for verifying a received directory entry in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart illustrating an exemplary process for decoding an encoded name in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 11</figref> is a flowchart illustrating an exemplary recasifying procedure in accordance with certain embodiments of the invention.

<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating an exemplary process for demapping a name in accordance with certain embodiments of the invention

<figref idref="DRAWINGS">FIG. 13</figref> shows a general example of a computer that can be used in accordance with the invention

DETAILED DESCRIPTION

Cryptographic methods and systems including exclusive encryption are described herein. Exclusive encryption is used herein to refer to encryption that allows for the exclusion of certain plaintext and ciphertext while at the same time maintaining the privacy created by the encryption. In certain embodiments, these exclusions include the exclusion of syntactically illegal plaintext (e.g., exclusion from being encrypted) and the exclusion of multiple ciphertexts that decrypt to the same plaintext.

The discussions herein assume a basic understanding of cryptography by the reader. For a basic introduction of cryptography, the reader is directed to a text written by Bruce Schneier and entitled “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published by John Wiley & Sons with copyright 1994 (or second edition with copyright 1996).

<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an exemplary system in which certain embodiments of the invention can be implemented. A computing device 102 is illustrated coupled to a computing device 104. Computing device 102 communicates ciphertext 106 to computing device 104. Ciphertext 106 can be communicated to computing device 104 for any of a wide variety of uses, such as storage of the ciphertext, verification of the ciphertext, forwarding of the ciphertext, etc. Ciphertext 106 is encrypted using an exclusive encryption cryptosystem that allows computing device 104 to exclude certain types of data (e.g., duplicates) from being processed (e.g., stored, forwarded, etc.) by device 104 without actually determining the underlying plaintext.

Another computing device 108 coupled to computing device 104 may also be able to access, and obtain the ciphertext 106 from, computing device 104. If computing device 108 is not authorized to access the plaintext corresponding to ciphertext 106, then computing device 108 would not be able to decrypt ciphertext 106 (e.g., device 108 would not have the appropriate cryptographic key(s)) and the corresponding plaintext would thus be secure from being viewed by device 108. However, if computing device 108 is authorized to access the plaintext corresponding to ciphertext 106 (e.g., computing device has the appropriate key(s) to decrypt ciphertext 106), then device 108 will be able to obtain the plaintext by decrypting ciphertext 106. Additionally, computing device 108 is assured that the decrypted plaintext will be syntactically legal, regardless of what encrypted bits it receives and regardless of what key(s) it uses.

The methods and systems of the exclusive encryption cryptosystem are discussed herein primarily with reference to a directory service that uses exclusive encryption. However, the invention is not limited to use with directory services and can be used in any of a wide variety of other situations. One example of such a situation is a secure courier service in which a courier guarantees to the message recipient that it will only deliver syntactically valid messages, and it will never deliver a duplicate message, even though the courier is not permitted access to the unencrypted contents of the messages it carries. Another example is a secret-ballot election, in which one wishes to transmit a vote in encrypted form while demonstrating that the vote is of a valid form. Yet another example is “secret sharing”, in which portions of a key are distributed; in such situations, one may want to encrypt the “shares” of the key for transmission while demonstrating that the shares are valid.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary network environment 118 in which certain embodiments of the invention may be practiced. Four client computing devices 120, 122, 124, and 126 are illustrated coupled together via a data communications network 128. Although four computing devices 120-126 are illustrated, different numbers (either greater or fewer than four) may be included in network environment 118.

Network 128 represents any of a wide variety of data communications networks. Network 128 can include public portions (e.g., the Internet) as well as private portions (e.g., an internal corporate Local Area Network (LAN)), as well as combinations of public and private portions. Network 128 can be implemented using any one or more of a wide variety of conventional communications media including both wired and wireless media. Any of a wide variety of communications protocols can be used to communicate data via network 128, including both public and proprietary protocols. Examples of such protocols include TCP/IP, IPX/SPX, NetBEUI, etc.

Computing devices 120-126 represent any of a wide range of computing devices, and each device 120-126 may be the same or different. By way of example, devices 120-126 may be desktop computers, laptop computers, handheld or pocket computers, personal digital assistants (PDAs), cellular phones, Internet appliances, consumer electronics devices, gaming consoles, etc.

Two or more of devices 120-126 operate to implement a serverless distributed file system 130. The actual devices included in the serverless distributed file system 130 can change over time, allowing new devices to be added to the system 130 and other devices to be removed from the system 130. Each device 120-126 that is part of the distributed file system 130 has different portions of its mass storage device(s) (e.g., hard disk drive) allocated for use as either local storage or distributed storage. The local storage is used for data that the user desires to store on his or her local machine and not in the distributed file system structure. The distributed storage portion is used for data that the user of the device (or another device) desires to store within the distributed file system structure. In the illustrated example of <figref idref="DRAWINGS">FIG. 2</figref>, each of devices 120-124 includes one or more mass storage devices that each includes a distributed portion and a local portion. This separation into multiple portions may occur on a per storage device basis (e.g., one hard drive is designated for use in the distributed system 130 while another is designated solely for local use), and/or within a single storage device (e.g., part of one hard drive may be designated for use in the distributed system 130 while another part is designated for local use). Another computing device, device 126, is coupled to network 128 but is not part of the distributed file system 130 and thus does not have any of its mass storage device(s) allocated for use by the distributed system. Device 126, which does not have storage space allocated for use as distributed storage, may be permitted to store files in the distributed portions of one or more of devices 120-124, or alternatively may be prohibited from doing so.

The distributed file system 130 operates to store one or more copies of files on different computing devices 120-124. When a new file is created by the user of a computer 120-126, he or she has the option of storing the file on the local portion of his or her computing device, or alternatively in the distributed file system 130. If the file is stored in the distributed file system 130, then the file will be stored in the distributed system portion of the mass storage device(s) of one or more of devices 120-124. The user creating the file typically has no ability to control which device 120-124 the file is stored on, nor any knowledge of which device 120-124 the file is stored on. Additionally, duplicate copies of the file will typically be saved, allowing the user to subsequently retrieve the file even if one of the computing devices 120-124 on which the file is saved is unavailable (e.g., is powered-down, is malfunctioning, etc.).

The distributed file system 130 is implemented by one or more components on each of the devices 120-124, thereby obviating the need for any centralized server to coordinate the file system. These components operate to determine where particular files are stored, how many copies of the files are created for storage on different devices, etc. Exactly which device will store which files depends on numerous factors, including the number of devices in the distributed file system 130, the storage space allocated to the file system from each of the devices, a number of copies of the file are to be saved, the number of files already stored on the devices, etc. Thus, the distributed file system 130 allows the user to create and access files (as well as folders or directories) without any knowledge of exactly which other computing device(s) the file is being stored on.

The files stored by the file system 130 are distributed among the various devices 120-124 and stored in encrypted form. When a new file is created, the device on which the file is being created encrypts the file prior to communicating the file to other device(s) for storage. The directory entry (e.g., the file name) for a new file is also communicated to the other device(s) for storage. Additionally, if a new folder or directory is created, the directory entry (e.g., folder name or directory name) is also communicated to the other device(s) for storage. As used herein, a directory entry refers to any entry that can be added to a file system directory, including both file names and directory (or folder) names.

The distributed file system 130 is designed to prevent unauthorized users from reading data stored on one of the devices 120-124. Thus, a file created by device 122 and stored on device 124 is not readable by the user of device 124 (unless he or she is authorized to do so). In order to implement such security, the contents of files as well as all directory entries are encrypted, and only authorized users are given the decryption key. Thus, although device 124 may store a file created by device 122, if a user of device 124 is not an authorized user of the file then the user of device 124 cannot decrypt (and thus cannot read) either the contents of the file or its directory name (e.g., filename).

The exclusive encryption described herein allows the directory entry to be stored in an encrypted form, thereby preventing unauthorized users from improperly gaining any information based on the filename. Additionally, the exclusive encryption assures that various properties are maintained. In the illustrated example, the following three properties are maintained: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0038">no two encrypted entries in a directory will decrypt to the same name</li><li id="ul0002-0002" num="0039">all encrypted entries in the directory decrypt to syntactically legal names</li><li id="ul0002-0003" num="0040">the service that maintains the directory does not have access to the plaintext names of the entries Thus, the system is able to ensure both that no two entries in a directory are encryptions of the same name and that all entries in a directory are encryptions of syntactically legal names, while at the same time ensuring that the device maintaining the directory does not have access to the plaintext names of the entries. </li></ul></li></ul>

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an exemplary computing device 150 such as may be used in accordance with certain embodiments of the invention. Computing device 150 can be, for example, a device 120-124 of <figref idref="DRAWINGS">FIG. 2</figref>. Computing device 150 includes a server component 152, a client component 154, a memory 156, and a mass storage device 158. Computing device 150 also typically includes additional components (e.g., a processor), however these additional components have not been shown in <figref idref="DRAWINGS">FIG. 3</figref> so as not to clutter the drawings. Memory 156 can be any of a wide variety of conventional volatile and/or nonvolatile memories, such as RAM, ROM, Flash memory, etc. Mass storage device 158 can be any of a wide variety of conventional nonvolatile storage devices, such as a magnetic disk, optical disk, Flash memory, etc.

Computing device 150 is intended to be used in a serverless distributed file system, and as such includes both server component 152 and client component 154. Server component 152 handles requests when device 150 is responding to a request involving a file or directory entry stored (or to be stored) in storage device 158 (although files and corresponding directory entries need not be stored on the same device 150), while client component 154 handles the issuance of requests by device 150 for files stored (or to be stored) in the distributed file system. Client component 154 and server component 152 operate independent of one another. Thus, situations can arise where the serverless distributed file system causes files being stored by client component 154 to be stored in mass storage device 158 by server component 152.

Client component 154 includes a storage and retrieval control module 160, a mapping module 162, a decasifying module 164, an encoding module 166, an encryption module 168, a decryption module 170, a decoding module 172, a recasifying module 174, and a demapping module 176. Control module 160 (in combination with interface 200 discussed below) manages accesses to the serverless distributed file system for the creation, storage, retrieval, and any other modification of files and directories on behalf of computing device 150. Due to the distributed nature of the file system, directory information such as file names and directory names (plaintext names) are modified by computing device 150 prior to being stored in the file system so that the modified names themselves reveal very little information about the original plaintext name, while at the same time allowing the device at which the names will be stored to verify that they are syntactically legal names and are not duplicates. The modified names do leak information about the approximate length of the original plaintext name (although this leak can be avoided in an alternate embodiment discussed below). The modules 162-168 are used to modify plaintext names prior to communicating them to the serverless distributed file system, while modules 170-176 are used to reconstruct the plaintext name when a modified name is received from the serverless distributed file system. The use of these modules and their operation will be discussed with additional reference to <figref idref="DRAWINGS">FIGS. 4-12</figref>.

<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating an exemplary process for exclusively encrypting a directory entry prior to storage in accordance with certain embodiments of the invention. Initially, control module 160 receives a plaintext name that is the directory entry to be encrypted (act 180). The plaintext name is received from another component internal to device 150 (not shown), such as an application, operating system, etc. The received plaintext name is made available to mapper 162 which maps the plaintext name to a new mapped name (act 182). The mapped name is then made available to decasifier 164 which decasifies the mapped name into a decasified name (e.g., a name where the case of the characters has no importance) and corresponding case information (act 184).

The decasified name is then made available to encoder 166 which encodes the decasified name (act 186). The encoded name is then made available to encryptor 168 which encrypts both the encoded name from act 186 and the case information from act 184 (act 188). Control module 160 then communicates the encrypted name and encrypted case information to another device for verification and storage (act 190). This encrypted name and case information are also referred to as ciphertexts.

The process of <figref idref="DRAWINGS">FIG. 4</figref> is based on the directory entries being case-insensitive. That is, the serverless distributed file system does not distinguish between upper-case and lower-case letters. For example, the entries “MEMO” and “memo” would be the same entries as viewed by the serverless distributed file system. Alternatively, the serverless distributed file system may be case-sensitive. If the system is case-sensitive, then no decasifying is done, and neither decasifier 164 nor decasifying act 184 are needed (and act 188 would not encrypt case information).

After the directory entry is modified per the process of <figref idref="DRAWINGS">FIG. 4</figref>, the directory entry is communicated to another device via a distributed system interface 200. Distributed system interface 200 determines, optionally in collaboration with corresponding interfaces on other devices in the serverless distributed file system, where the directory entry and corresponding file (if any) are to be stored. Interface 200 selects one or more devices, which can include computing device 150, and communicates the directory entry to the selected device. The selection process can be accomplished in a variety of different manners, such as based on the storage space available in the various devices that are part of the serverless distributed file system, an anticipated likelihood that one or more of the various devices will be unavailable at any given moment, etc. Interface 200 also maintains a client storage record 202 that identifies the location of each directory entry (and corresponding file, if any) that is stored by client component 154. Thus, when client component 154 requests retrieval of a particular directory entry interface 200 knows where to locate the requested entry.

<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating an exemplary process for decrypting a received directory entry in accordance with certain embodiments of the invention. Initially, control module 160 receives an encrypted name and encrypted case information (ciphertexts) from another device via interface 200 (act 210). The encrypted name and encrypted case information are made available to decryptor 170 which decrypts both the name and the case information (act 212). The decrypted name is then made available to decoder 172 which decodes the decrypted name (act 214).

The decoded name and decrypted case information are then made available to recasifier 174 which uses the case information to recasify the decoded name (act 216). The recasified name is then made available to demapper 176 which demaps the recasified name into the plaintext name (act 218).

The process of <figref idref="DRAWINGS">FIG. 5</figref> is based on the directory entries being case-insensitive. Alternatively, if the serverless distributed file system is case-sensitive, then no recasifying is done, and neither recasifier 174 nor recasifying act 216 are needed (and no decryption of case information is performed in act 212).

An exemplary implementation of the modules 162-176 will now be discussed.

Mapping module (mapper) 162 maps a received plaintext name into a mapped name. <figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating an exemplary process for mapping the plaintext name to the mapped name in accordance with certain embodiments of the invention. Mapping module 162 initially receives the input plaintext name (act 240). Mapping module 162 may receive the actual name, or alternatively an indication of where the name can be found (e.g., a pointer to the name).

Mapping module 162 then checks whether the input plaintext name is an illegal name (act 242). Mapping module 162 includes a record of illegal names, which may be pre-programmed or defined in module 162 or alternatively provided to module 162 by some other component (e.g., module 160). In one implementation, the following strings (regardless of case) are illegal names: CONIN$, CONOUT$, CON, PRN, AUX, NUL, LPTn, COMn (where n represents any digit 0 through 9). Alternatively, the illegal names may include more or fewer (and/or different) strings. Additionally, the set of illegal names may be the empty set, which is equivalent to there being no illegal names. If there are no illegal names, then neither mapping module 162 (nor mapping act 242) need be included, and demapping module 176 and any demapping acts (discussed in more detail below) also need not be included.

If the plaintext name is equal to any one of these illegal names then an indication that no valid mapping exists is given to module 160 (act 244) and the modification process of <figref idref="DRAWINGS">FIG. 4</figref> fails. However, if the input plaintext name is not an illegal name, then module 162 checks whether the input plaintext name is an illegal name followed by one or more underscore characters, such as the name “CON_” or “PRN_”, (act 246). If the input name is not an illegal name followed by one or more underscore characters, then the input plaintext name is used as the mapped name (act 248). In other words, the input name maps to itself. However, if the input name is an illegal name followed by one or more underscore characters, then the mapped name is the input name with one trailing underscore removed (act 250). For example, the input name “CON_” would map to “CON”, and the input name “PRN_” (having two underscores) would map to “PRN_” (having one underscore).

Alternatively, other characters may be used by mapping module 162 other than an underscore. Any character (e.g., letter, number, other symbol, etc.) can be used in place of the underscore, so long as adding a string of zero or more such characters to an illegal name does not result in another illegal name.

Once mapped, the mapped name is decasified by decasifying module (decasifier) 164. <figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating an exemplary process for decasifying the mapped name in accordance with certain embodiments of the invention. Decasifying module 164 initially receives the input mapped name (act 270). Decasifying module 164 may receive the actual name, or alternatively an indication of where the name can be found (e.g., a pointer to the name), from module 160 or alternatively directly from mapping module 162.

Module 164 then initializes two strings, referred to as the L and the I strings, to null (act 272). At the end of the decasifying process, the L string will be the decasified version of the input name received in act 270, and the I string will be a set of bits that identify the appropriate case for each of the characters in the L string. Module 164 operates to decasify names based on the Unicode standard including current and future versions of the standard. Additionally information regarding the Unicode standard is available from The Unicode Consortium of Mountain View, Calif. The Unicode standard uses sixteen bits to identify each character, but it is an evolving standard, so not all 65,536 combinations are defined. However, the conventional ASCII character set (which includes the uppercase and lowercase English alphabet, numbers, and many symbols commonly used in English) is defined using the last seven bits of the sixteen Unicode bits (with the first nine bits being all zeroes). Thus, characters with Unicode values between 0 and 127 are equivalent to characters with identical ASCII values. Furthermore, characters with Unicode values between 128 and 255 have all been defined, and they include characters that, together with the first 128 Unicode characters, are sufficient to display text in most Latinate languages. These 256 characters are sometimes referred to as the “extended ASCII” character set. Due to the evolving nature of the Unicode standard, module 164 is implemented so as to decasify only those characters with Unicode values less than or equal to 255 (that is, the extended ASCII character set). Module 164 does not attempt to decasify any character in the input mapped name having a Unicode value greater than 255. Alternatively, additional characters may be decasified, such as any characters which are defined in the Unicode standard.

To decasify the received name, module 164 selects the first character from the input name (act 274). Module 164 then checks whether the leading eight bits of the selected character are zero (act 276). If the leading eight bits are not all zero (that is, the character has a Unicode value greater than 255) then module 164 appends the selected character to the L string and a zero bit to the I string (act 278). Module 164 then checks whether there are any additional characters in the input name (act 280). If there are no additional characters, then module 164 outputs the decasified name as the L string and the corresponding case information as the I string (act 282). However, if there are additional characters, then module 164 selects the next character in the input name (act 284) and returns to check whether each of the leading eight bits of the selected character is zero (act 276).

Returning to act 276, if the leading eight bits of the selected character are all zeroes, then module 164 checks whether the selected character is not a lower-case character (act 286). It should be noted that the phrase “not a lower-case character” is not equivalent to the phrase “an upper-case character”. For example, the asterisk symbol (*) has no case distinction and thus would not be a lower-case character, but also would not be an upper-case character.

If the selected character is not a lower-case character, then the selected character is appended to the L string and a zero bit is appended to the I string (act 288), and the process continues to act 280 to check whether any additional characters are in the input name. However, if the selected character is a lower-case character, then the upper-case form of the selected character is appended to the L string and a one bit is appended to the I string (act 290), and the process continues to act 280 to check whether any additional characters are in the input name.

By way of example, following the process of <figref idref="DRAWINGS">FIG. 7</figref>, if the input name were “Memo.doc”, then module 164 would output as the decasified name (L string) “MEMO.DOC”, and as the case information (I string) “01110111”.

In the illustrated example of <figref idref="DRAWINGS">FIG. 7</figref>, a zero bit in case information string I is used to signify that a character is upper-case or has no case distinction, and the decasified name (L string) is all non-lower case characters. Various alterations can be made to this process, such as having upper-case characters signified by a one bit, having characters with no case distinction signified by a one bit, having the decasified name all non-upper case characters, etc.

Once decasified, the decasified name is encoded by encoding module (encoder) 166. <figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating an exemplary process for encoding the decasified name in accordance with certain embodiments of the invention. Encoding module 166 initially receives the input decasified name (act 302). Encoding module 166 may receive the actual name, or alternatively an indication of where the name can be found (e.g., a pointer to the name), from module 160 or alternatively directly from decasifying module 164 (or mapping module 162 if the system is case-sensitive).

The characters of the input name are then reversed (act 304) and the number of trailing underscores in the reversed name counted and removed (act 306). An encoded bit stream B (which will be the output encoded name at the end of the encoding process) is then initialized with a string of one bits equal to the number of underscores removed in act 306, followed by a zero (act 308). If there are no trailing underscores, then the encoded bit stream B is initialized with a single zero bit. Alternatively, rather than relying on underscores, different characters may be used. In one implementation, the character that is Huffman coded to zero is the character that is counted and removed from the end of the reversed name (Huffman coding is discussed in more detail below).

Module 166 then checks whether the leading eight bits of the first character in the reversed name are all zero (act 310). If the leading eight bits are not all zero, then the sixteen bits of the first character are appended to the encoded bit stream B (act 312). However, if the leading eight bits of the first character are all zero, then the character (based on the last eight bits) is encoded using a first coding table (act 314), and then eight zero bits followed by the bits from the coding table are appended to the encoded bit stream B (act 316).

The coding table in act 314 can be generated in any of a wide variety of conventional manners using any of a wide variety of prefix coding schemes. In one implementation, conventional Huffman coding is used, although other coding schemes could alternatively be used. In the illustrated example, the coding table in act 314 codes an underscore to all zeroes and has codes for all valid non-lower case characters with Unicode values less than 256 and greater than 31, except for the following: space, period, quotation mark, asterisk, forward slash, colon, greater than symbol, less than symbol, question mark, back slash, or vertical line. If module 166 is given an input name with a character that is the first character in act 308 and is not in the coding table, then the coding process fails, as does the modification process of <figref idref="DRAWINGS">FIG. 4</figref>.

Regardless of the bits added to encoded bit stream B in either act 312 or 316, module 166 proceeds to check whether there is an additional character in the reversed name (act 318). If there are no more characters in the reversed name, then module 166 removes any trailing zero bits and the one bit preceding the trailing zero bits from the encoded bit string B (act 320). Module 166 then outputs the encoded bit string B as the encoded name (act 322).

Returning to act 318, if there are additional characters in the reversed name, then the next character in the reversed name is selected (act 324) and a check made as to whether the leading eight bits of the selected character are all zero (act 326). If the leading eight bits are not all zero, then the sixteen bits of the selected character are appended to the encoded bit stream B (act 328). However, if the leading eight bits of the selected character are all zero, then the character (based on the last eight bits) is encoded using another coding table (act 330), and then eight zero bits followed by the bits from the coding table are appended to the encoded bit stream B (act 332).

Analogous to the coding table discussed in act 314 above, the coding table used in act 330 can be generated in any of a wide variety of conventional manners using any of a wide variety of prefix coding schemes. In one implementation, conventional Huffman coding is used, although other coding schemes could alternatively be used. In the illustrated example, the coding table in act 330 codes an underscore to all zeroes and has codes for all valid non-lower case characters with Unicode values less than 256 and greater than 31, except for the following: quotation mark, asterisk, forward slash, colon, greater than symbol, less than symbol, question mark, back slash, or vertical line. These codes may be the same as those in the table of act 314, or alternatively different. If module 166 is given an input name with a character that is the selected character in act 324 and is not in the coding table, then the coding process fails, as does the modification process of <figref idref="DRAWINGS">FIG. 4</figref>.

Regardless of the bits added to encoded bit stream B in either act 328 or 332, module 166 proceeds to check whether there is an additional character in the reversed name (act 318), and proceeds accordingly. In the illustrated example of <figref idref="DRAWINGS">FIG. 8</figref>, each additional character is encoded using the other coding table in act 330. Alternatively, the same coding table as was used in act 314 may be used in act 330. In another alternative, multiple additional coding tables are used in act 330 for encoding additional characters. For example, there may be a different coding table for each additional character or groups of characters.

Once encoded, the encoded name (encoded bit string B of <figref idref="DRAWINGS">FIG. 8</figref>) is encrypted by encryption module (encryptor) 168. Encryption module 168 initially receives the encoded name (or an indication of where the name can be found) from module 160 or alternatively directly from encoding module 166 (act 302). Encryption module 168 can use any of a wide variety of encryption schemes to encrypt the encoded name. The encryption scheme used, however, should be surjective so that any arbitrary string of bits will decrypt to a valid encoded name, and it should be deterministic so that identicality of names can be determined by examining only their encrypted forms. In the illustrated example, a conventional block cipher is used, although other types of ciphers could alternatively be used (e.g., a stream cipher).

Given that the encoded bit string B can be of varying length, additional bits are added to the bit string B as necessary to bring the bit string up to a length that is a multiple of the block size for the block cipher. In one implementation, this addition (also referred to as padding) to bit string B is accomplished by prepending to the bit string B (adding to the beginning of the bit string B) a one bit preceded by as many zero bits as necessary to bring the length of the bit string up to a multiple of the cipher block size. Encryption module 168 then encrypts the padded bit string B on a per-block (x) basis according to the following three rules: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0073">(1) if the block x of bit string B has the value of zero, then the encrypted block has a value of zero;</li><li id="ul0004-0002" num="0074">(2) otherwise, if the result of encrypting block x with a block cipher encryption E is zero, then the encrypted block has a value equal to the encryption E of the value zero; and</li><li id="ul0004-0003" num="0075">(3) if neither rule (1) nor (2) applies, then the encrypted block has a value equal to the encryption E of the block.</li></ul></li></ul>

Any of a wide variety of conventional block ciphers can be used as block cipher encryption E. In one implementation, block cipher encryption E is the well-known RC2 block cipher. Other conventional block ciphers can alternatively be used, such as DES, RC5, AES/Rijndael, and so forth.

It should also be noted that encryption module 168, using these rules, will not result in an encrypted name with a first block equaling zero. This is true even if the encryption uses a feedback mechanism such as cipher block chaining (CBC) to increase the security of the encrypted data. In CBC mode, the plaintext of each block is exclusively ORed (XORed) with the ciphertext of the previous block before it is encrypted, thereby making each ciphertext block dependent not only on the corresponding plaintext block but also on all previous plaintext blocks.

The resulting encrypted blocks are the encrypted name to be communicated to another device (act 190 of <figref idref="DRAWINGS">FIG. 4</figref>).

In addition to encrypting the name, the case information I is also encrypted. The case information I is encrypted using any of a wide variety of conventional block ciphers. The block cipher may be the same as used for encrypting the encoded name, or alternatively a different block cipher. Additionally, the case information may be prepended with a one bit preceded by as many zero bits as necessary to bring the length of the case information up to a multiple of the size of the block cipher, analogous to the padding of the encoded bit string B discussed above. Alternatively, additional random padding may be added to the end of the case information I to bring it up to a multiple (not necessarily the next closest multiple) of the block cipher size. Any such additional information is ignored when recasifying the decoded name as discussed in more detail below.

Once generated, the encrypted directory entry is communicated to one or more other computing devices 150. As discussed above, this is typically a different device 150 than the device that generated the encrypted directory entry, although it could be the same device. Regardless of the source of the encrypted directory entry, the distributed system interface 200 at the receiving device 150 communicates the directory entry to server component 152.

Server component 152 includes a distributed system control module 350, a syntax verifier 352, and a duplication identifier 354. Distributed system control module 350 receives the encrypted directory entry and communicates the entry to syntax verifier 352 to verify that the entry is syntactically legal, and duplication identifier 354 to verify that the entry is not a duplicate of another entry in the distributed file system. Distributed system control module 350 maintains a record 356 of the encrypted directory entries that are stored at computing device 150 (or alternatively that are stored in all of the serverless distributed file system). In addition to having record 356 available in memory 156, if memory 156 is a volatile memory then record 356 is also stored in a nonvolatile memory (such as mass storage device 158) in order to preserve record 356 if computing device 150 is powered-down. Additionally, distributed system control module 350 communicates with mass storage device 158 to store and retrieve encrypted files corresponding to encrypted directory entries in record 356.

Syntax verifier 352 verifies that the syntax of a received directory entry is valid. In the illustrated example, syntax verifier 352 checks whether the first block of the encrypted directory entry is zero. If the first block is zero, then the directory entry is not syntactically legal; otherwise, the directory entry is syntactically legal.

Duplication identifier 354 compares the received encrypted directory entry to the other encrypted directory entries stored in record 356. If the received encrypted entry matches any of the encrypted entries stored in record 356 in the same folder as the received encrypted entry will be placed in, then the received entry is a duplicate; otherwise the received entry is not a duplicate. Note that the serverless distributed file system prevents multiple files or folders within the same directory or folder from having the same name, but does not prevent different files in different folders from having the same name. For example, two files in the same directory could not be named “memo.doc”, but two files in two different directories could be named “memo.doc”. Record 356 maintains an indication, for each entry, of which folder or directory the entry is in.

<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart illustrating an exemplary process for verifying a received directory entry in accordance with certain embodiments of the invention. Initially, the encrypted name is received by distributed system control module 350 (act 370). Syntax verifier 352 then checks whether the first block of the encrypted name is zero (act 372). If the first block is zero, then the encrypted name is invalid (act 374). However, if the first block is not zero, then duplication identifier 354 checks whether the encrypted name is identical to any other encrypted name in the directory (act 376). If the encrypted name is identical to another encrypted name in the directory, then the encrypted name is invalid (act 374); otherwise, the encrypted name is valid (act 380).

As mentioned above, the exclusive encryption described herein maintains the following three properties: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0086">no two encrypted entries in a directory will decrypt to the same name</li><li id="ul0006-0002" num="0087">all encrypted entries in the directory will decrypt to syntactically legal names</li><li id="ul0006-0003" num="0088">the service that maintains the directory does not have access to the plaintext names of the entries Distributed system control module 350 ensures that no two entries in a directory can be duplicates (based on the comparison performed by duplication identifier 354). Encryption of the directory entry using the block or other cipher ensures that the service that maintains the directory does not have access to the plaintext names of the entries. </li></ul></li></ul>

The encryption process does not result in an encrypted name having a first block that equals zero. Thus, any encrypted name having a first blocker equal to zero is an illegal entry and is detected by syntax verifier 352. Additionally, in one implementation a directory entry must satisfy the following criteria in order to be syntactically legal: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0090">the directory entry name cannot be null (the encoding process discussed above with reference to <figref idref="DRAWINGS">FIG. 8</figref> admits no null name)</li><li id="ul0008-0002" num="0091">the directory entry name cannot include any character with an ASCII or Unicode value less than 32 (the encoding process discussed above with reference to <figref idref="DRAWINGS">FIG. 8</figref> admits no such characters)</li><li id="ul0008-0003" num="0092">the directory entry name may not include any of the following characters: “* / : < > ? \ | (the encoding process discussed above with reference to <figref idref="DRAWINGS">FIG. 8</figref> can be configured to admit no such characters)</li><li id="ul0008-0004" num="0093">the final character of a directory entry name may not be a space or a period (the encoding process discussed above with reference to <figref idref="DRAWINGS">FIG. 8</figref> can be configured to admit no such final characters)</li><li id="ul0008-0005" num="0094">the following names are illegal (where n is any digit): CONIN$, CONOUT$, CON, PRN, AUX, NUL, LPTn COMn (the mapping process discussed above with reference to <figref idref="DRAWINGS">FIG. 6</figref> can be configured to admit no such names)</li><li id="ul0008-0006" num="0095">for purposes of determining duplication, character case is ignored (the decasifying process discussed above with reference to <figref idref="DRAWINGS">FIG. 7</figref> decasifies the entry names)</li></ul></li></ul>

Given that the directory entries are stored in an encrypted manner, when a computing device 150 retrieves the entries from another device in the serverless distributed file system, the entries need to be converted to plaintext to be useable by other components in the device. The general process for converting the received encrypted name and case information into a plaintext name is discussed above with reference to <figref idref="DRAWINGS">FIG. 5</figref>. One implementation of the process will be described in more detail below.

Initially, the encrypted name (bit string B discussed above) and the encrypted case information are decrypted by decryption module (decryptor) 170. The decryption process is the reverse of the encryption process discussed above. Initially, the prepended encoded name B is decrypted on a per-block (x) basis according to the following rules: <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0098">(1) if the block x of bit string B has the value of zero, then the decrypted block has a value of zero;</li><li id="ul0010-0002" num="0099">(2) otherwise, if the result of decrypting block x with a block cipher decryption E−1 is zero, then the decrypted block has a value equal to the decryption E−1 of the value zero; and</li><li id="ul0010-0003" num="0100">(3) if neither rule (1) nor (2) applies, then the decrypted block has a value equal to the decryption E−1 of the block. The block cipher decryption E−1 is the decryption that corresponds to block cipher encryption E.</li></ul></li></ul>

The result of this decryption process is the prepended encoded name B, from which decryption module 170 discards all leading bits up to and including the first one bit.

Decryption module 170 decrypts case information analogous to the decryption of prepended encoded name B. However, if any additional random padding was added to the end of the case information prior to encryption, this additional padding remains part of the decrypted case information and is simply ignored during the recasification process discussed below.

Once decrypted, decoding module (decoder) 172 decodes the encoded name B. <figref idref="DRAWINGS">FIG. 10</figref> is a flowchart illustrating an exemplary process for decoding an encoded name in accordance with certain embodiments of the invention. Initially, decoding module 172 receives the encoded name (act 400), either from control module 160 or directly from decryption module 170. Decoding module 172 then initializes a name string L to null (act 402). The name string L will be the decoded name output by module 172 upon completion of the process of <figref idref="DRAWINGS">FIG. 10</figref>. The encoded name is also extended, if necessary, by appending a one bit followed by as many zero bits as needed to complete the process described in <figref idref="DRAWINGS">FIG. 10</figref>.

The number of leading one bits that precede the first zero bit in the encoded name B are then counted (act 404) and a pointer initialized to point to the first bit of the encoded name following the zero bit that follows the leading one bit (act 406). Decoding module 172 then checks whether the leading eight bits pointed to by the pointer are all zeroes (act 408). If the leading eight bits are not all zeroes, then module 172 appends the leading sixteen bits pointed to by the pointer to the name string L (act 410), updates the pointer to point to the first bit after the leading sixteen bits (act 412), and proceeds to check whether the leading eight bits pointed to by the pointer are all zeroes (act 414).

Returning to act 408, if the leading eight bits pointed to by the pointer are all zeroes, then module 172 decodes the next eight bits after the leading eight bits using a coding table (act 416). The coding table used in act 416 is the same as the coding table used in act 314 of <figref idref="DRAWINGS">FIG. 8</figref>. Decoding module 172 then checks whether the decoded character is an underscore (act 418). If the decoded character is an underscore, then module 172 checks whether any more one bits remain in the encoded name B (act 420). If no more one bits remain, then decoding module 172 appends a string of underscore characters to L equal in number to the number of leading one bits that preceded the first zero bit as counted in act 404 above (act 422). The order of the characters in L is then reversed (act 424) and L is output as the decoded name (act 426).

Returning to acts 414 and 418, if the decoded character is not an underscore (act 418) or more one bits remain in the encoded name (act 420), then the decoded character is appended to L (act 428). Decoding module 172 then updates the pointer to point to the next bit after the decoded character (act 430), and then checks whether the leading eight bits pointed to by the pointer are all zeroes (act 414). If the leading eight bits pointed to by the pointer are not all zeroes, then module 172 returns to act 410. However, if the leading eight bits pointed to by the pointer are all zeroes, then module 172 decodes the next eight bits after the leading eight bits using another coding table (act 432) and returns to act 418. The coding table used in act 432 is the same as the coding table used in act 330 of <figref idref="DRAWINGS">FIG. 8</figref> above.

Upon completion of the decoding process, a decoded and decasified name remains, along with corresponding case information. Recasifying module (recasifier) 174 uses the decoded name and the corresponding case information to recasify the name. <figref idref="DRAWINGS">FIG. 11</figref> is a flowchart illustrating an exemplary recasifying procedure in accordance with certain embodiments of the invention. Initially, recasifying module 174 receives an input name and corresponding case information (act 450). The input name and/or case information can be received from control module 160, or alternatively directly from decoding module 172.

Recasifying module 174 then initializes a decoded name string M to be a null bit string (act 452). Recasifying module 174 outputs string M as the recasified name upon completing the process of <figref idref="DRAWINGS">FIG. 11</figref>. Recasifying module 174 then selects the first character of the input name and the first bit of case information (act 454) and checks whether the selected case information bit is zero (act 456).

If the selected case information bit is zero, then the selected character is appended to string M (act 458). However, if the selected case information is not zero, then module 174 checks whether the leading eight bits of the selected character are all zeroes (act 460). If the leading eight bits of the selected character are not all zero, then the selected character is appended to string M (act 458); otherwise, module 174 checks whether the selected character has case distinction (act 462). If the selected character does not have case distinction then the selected character is appended to string M (act 458); otherwise, the lower-case form of the selected character is appended to string M (act 464).

After acts 458 and 464, module 174 checks whether any additional characters are in the input name (act 466). If there are no more characters in the input name then the value of string M is output as the recasified name (act 468). Any bits remaining in the case information are simply ignored. However, if there are additional characters in the input name, then module 174 selects the next character in the input name (act 470) and checks whether there is case information corresponding to the selected character (act 472). If there is case information corresponding to the selected character, then the corresponding case information is selected (act 474) and module 174 returns to act 456; otherwise, the value zero is used as the selected case information corresponding to the selected character (act 476) and module 174 returns to act 456.

After recasifying module 174 recasifies the decode name, demapping module (demapper) 176 demaps the recasified name. <figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating an exemplary process for demapping a name in accordance with certain embodiments of the invention. Initially, an input name is received by demapping module 176 (act 500). The input name can be received from control module 160, or alternatively directly from recasifying module 174 (or alternatively directly from decoding module 172 if the serverless distributed file system is case sensitive).

Demapping module 176 then checks whether the input name is equal to an illegal name followed by zero or more underscores (act 502). If the input name is equal to an illegal name followed by zero or more underscores, then the demapped name is formed by appending one underscore to the input name (act 504). However, if the input name is not equal to an illegal name followed by zero or more underscores, then the input name is used as the demapped name (act 506). Thus, if the input name is not equal to an illegal name followed by zero or more underscores, then the input name demaps to itself.

The system and process described above with reference to <figref idref="DRAWINGS">FIGS. 3-12</figref> discusses generation and storage of modified names that reveal very little information about the original plaintext name (the approximate length of the original plaintext name and possibly some case information). In an alternate embodiment, the system and process described above are altered so that less information is revealed about the original plaintext name. These alterations are to the encoding/decoding, encryption/decryption, and validation processes as follows.

The decoding and encoding processes (discussed above with reference to <figref idref="DRAWINGS">FIGS. 8 and 10</figref>) and corresponding modules 166 and 172 of <figref idref="DRAWINGS">FIG. 3</figref> are altered so that in act 320 of <figref idref="DRAWINGS">FIG. 8</figref>, only the trailing zero bits (if any) are removed (the one bit preceding the trailing zero bits is not removed). Then, during the decoding process of <figref idref="DRAWINGS">FIG. 10</figref>, the encoded name is extended by appending as many zero bits as necessary to complete the process described in <figref idref="DRAWINGS">FIG. 10</figref>.

Encryption module 168 of <figref idref="DRAWINGS">FIG. 3</figref> is altered to the following encryption scheme. A fixed value W is established for the count of blocks in an encrypted name. This imposes some restrictions on the plaintext name (a plaintext name that would result in ciphertext having more than W blocks cannot be encrypted using this scheme). The encryption scheme can use any conventional block cipher encryption E (as discussed above) having a block size of Q bits. Encryption module 168 encrypts the encoded bit string according to the following three rules: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0116">(1) if the encoded bit string B equals W×Q zero bits followed by a single one bit, then remove the trailing one bit from string B and encrypt the remaining bits of string B with block cipher E;</li><li id="ul0012-0002" num="0117">(2) if rule (1) does not apply and if the length of the encoded bit string B is greater than W×Q, then the procedure is aborted (the bit string is too long to be encrypted); and</li><li id="ul0012-0003" num="0118">(3) if neither rule (1) nor (2) applies, then append as many zero bits as necessary to the end of encoded bit string B so that bit string B has a length of W×Q bits, and encrypt the bit string B with block cipher E.</li></ul></li></ul>

Encryption module 168 is also altered to encrypt the case information I as follows. The case information I is extended to include as many bits as necessary to bring the total length of the case information string I up to a fixed value V. The value V can vary, and in one implementation is equal to the largest number of characters that can be in a valid name (optionally plus additional space for additional random padding). The case information I can be extended using any bit values (e.g., random values). The case information I is then encrypted with block cipher E (or alternatively a different block cipher).

Decryption module 170 is similarly modified so that the decryption is performed as follows. Decryption module 170 sets the encoded name B equal to the decryption E−1 of the encrypted name. If the encoded name thus decrypted is all zero bits, then a one bit is appended to encoded name B. The encrypted case information is similarly decrypted using the decryption corresponding to the block cipher encryption used to encrypt the case information I.

The validation process (discussed above with reference to <figref idref="DRAWINGS">FIG. 9</figref> and modules 350 and 352 of <figref idref="DRAWINGS">FIG. 3</figref>) is similarly altered to eliminate the checking of whether the first block of an encrypted name equals zero (block 372 of <figref idref="DRAWINGS">FIG. 9</figref>). The encryption process described here with a fixed block count W can result in valid encrypted names with a first block having a value of zero, so this checking is removed from the validation process.

The system and process described above with reference to <figref idref="DRAWINGS">FIGS. 3-12</figref> allows multiple properties to be maintained (no two entries in a directory can be encryptions of identical names, all entries in the directory are encryptions of syntactically legal names, and the service that maintains the directory does not have access to the plaintext names of the entries). Alternative systems and processes may also be used that involve fewer acts and/or components, but do not necessarily maintain all of the properties discussed above. One such alternative is to simply encode a plaintext name using a fixed-bit-width encoding scheme, and then encrypt the encoded name using an encryption key. This alternative, however, can have problems when used with some encryption ciphers if the number of characters that are to be encoded is not a power of two (so there is no fixed bit width that can exactly encode all legal characters). Another such alternative also uses a fixed-bit-width encoding scheme, but with some characters encoded multiple times. This alternative, however, under circumstances cannot ensure that two directory entries are not the same.

Another such alternative is to encode each plaintext character using Huffman coding (or other prefix coding) and then encrypt the encoded name. However, due to variances in lengths of encoded names, it is not always possible to determine whether an encrypted name represents a legally complete encoded name. Another alternative that solves part of this problem is to discard any final partial character during decryption or to treat all missing bits as zeroes for the final character when running out of characters during decryption. However, both of these can also result in multiple directory entries that are the same.

<figref idref="DRAWINGS">FIG. 13</figref> illustrates an example of a suitable operating environment in which the invention may be implemented. The illustrated operating environment is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Other well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics (e.g., digital video recorders), gaming consoles, cellular telephones, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

<figref idref="DRAWINGS">FIG. 13</figref> shows a general example of a computer 542 that can be used in accordance with the invention. Computer 542 is shown as an example of a computer in which various embodiments of the invention can be practiced, and can be, for example, a computing device 150 of <figref idref="DRAWINGS">FIG. 3</figref>, a computing device 120-126 of <figref idref="DRAWINGS">FIG. 2</figref>, a computing device 102 or 104 of <figref idref="DRAWINGS">FIG. 1</figref>, etc. Computer 542 includes one or more processors or processing units 544, a system memory 546, and a bus 548 that couples various system components including the system memory 546 to processors 544.

The bus 548 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The system memory 546 includes read only memory (ROM) 550 and random access memory (RAM) 552. A basic input/output system (BIOS) 554, containing the basic routines that help to transfer information between elements within computer 542, such as during start-up, is stored in ROM 550. Computer 542 further includes a hard disk drive 556 for reading from and writing to a hard disk, not shown, connected to bus 548 via a hard disk drive interface 557 (e.g., a SCSI, ATA, or other type of interface); a magnetic disk drive 558 for reading from and writing to a removable magnetic disk 560, connected to bus 548 via a magnetic disk drive interface 561; and an optical disk drive 562 for reading from and/or writing to a removable optical disk 564 such as a CD ROM, DVD, or other optical media, connected to bus 548 via an optical drive interface 565. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for computer 542. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk 560, and a removable optical disk 564, it will be appreciated by those skilled in the art that other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, random access memories (RAMs), read only memories (ROM), and the like, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk, magnetic disk 560, optical disk 564, ROM 550, or RAM 552, including an operating system 570, one or more application programs 572, other program modules 574, and program data 576. A user may enter commands and information into computer 542 through input devices such as keyboard 578 and pointing device 580. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit 544 through an interface 568 that is coupled to the system bus (e.g., a serial port interface, a parallel port interface, a universal serial bus (USB) interface, etc.). A monitor 584 or other type of display device is also connected to the system bus 548 via an interface, such as a video adapter 586. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers.

Computer 542 operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 588. The remote computer 588 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 542, although only a memory storage device 590 has been illustrated in <figref idref="DRAWINGS">FIG. 13</figref>. The logical connections depicted in <figref idref="DRAWINGS">FIG. 13</figref> include a local area network (LAN) 592 and a wide area network (WAN) 594. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. In certain embodiments of the invention, computer 542 executes an Internet Web browser program (which may optionally be integrated into the operating system 570) such as the “Internet Explorer” Web browser manufactured and distributed by Microsoft Corporation of Redmond, Wash.

When used in a LAN networking environment, computer 542 is connected to the local network 592 through a network interface or adapter 596. When used in a WAN networking environment, computer 542 typically includes a modem 598 or other means for establishing communications over the wide area network 594, such as the Internet. The modem 598, which may be internal or external, is connected to the system bus 548 via a serial port interface 568. In a networked environment, program modules depicted relative to the personal computer 542, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

Computer 542 also includes a broadcast tuner 600. Broadcast tuner 600 receives broadcast signals either directly (e.g., analog or digital cable transmissions fed directly into tuner 600) or via a reception device (e.g., via antenna or satellite dish).

Computer 542 typically includes at least some form of computer readable media. Computer readable media can be any available media that can be accessed by computer 542. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology; CD-ROM, digital versatile disks (DVD), or other optical storage; magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices; or any other media which can be used to store the desired information and which can be accessed by computer 542. Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

The invention has been described in part in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.

For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.

Alternatively, the invention may be implemented in hardware or a combination of hardware, software, and/or firmware. For example, one or more application specific integrated circuits (ASICs) could be designed or programmed to carry out the invention.

CONCLUSIONS

Although the description above uses language that is specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the invention.

Contents7

Every citation, both waysCites: the store holds 146 of 147

Citations
Document	Relation	Office	Cited during
US9679146B2	Cited by	United States of America	Applicant
US12248597B2	Cited by	United States of America	Applicant
US10581804B2	Cited by	United States of America	Applicant
US10671761B2	Cited by	United States of America	Applicant
US2002066022A1	Cites	United States of America	Search report
US2003070071A1	Cites	United States of America	Search report
US2005131961A1	Cites	United States of America	Search report
US5202982A	Cites	United States of America	Applicant
US5317728A	Cites	United States of America	Applicant
US5371794A	Cites	United States of America	Applicant
US5452447A	Cites	United States of America	Applicant
US5483652A	Cites	United States of America	Applicant
US5553235A	Cites	United States of America	Applicant
US5586330A	Cites	United States of America	Search report
US5588147A	Cites	United States of America	Applicant
US5680611A	Cites	United States of America	Applicant
US5692178A	Cites	United States of America	Applicant
US5745902A	Cites	United States of America	Applicant
US5758359A	Cites	United States of America	Applicant
US5778395A	Cites	United States of America	Applicant
US5794042A	Cites	United States of America	Applicant
US5812776A	Cites	United States of America	Applicant
US5873085A	Cites	United States of America	Applicant
US5901227A	Cites	United States of America	Applicant
US5907673A	Cites	United States of America	Applicant
US5909540A	Cites	United States of America	Applicant
US5913217A	Cites	United States of America	Applicant
US5915096A	Cites	United States of America	Applicant
US5940841A	Cites	United States of America	Applicant
US5950198A	Cites	United States of America	Applicant
US5950209A	Cites	United States of America	Applicant
US5953729A	Cites	United States of America	Applicant
US5960446A	Cites	United States of America	Applicant
US5963963A	Cites	United States of America	Applicant
US5968121A	Cites	United States of America	Applicant
US5974141A	Cites	United States of America	Search report
US5978805A	Cites	United States of America	Applicant
US5987477A	Cites	United States of America	Applicant
US5991414A	Cites	United States of America	Applicant
US5991771A	Cites	United States of America	Applicant
US6023506A	Cites	United States of America	Search report
US6026474A	Cites	United States of America	Applicant
US6029168A	Cites	United States of America	Applicant
US6032151A	Cites	United States of America	Applicant
US6032216A	Cites	United States of America	Applicant
US6047283A	Cites	United States of America	Applicant
US6067545A	Cites	United States of America	Applicant
US6098079A	Cites	United States of America	Applicant
US6122378A	Cites	United States of America	Applicant
US6122631A	Cites	United States of America	Applicant
US6125372A	Cites	United States of America	Applicant
US6145094A	Cites	United States of America	Applicant
US6160552A	Cites	United States of America	Applicant
US6167449A	Cites	United States of America	Applicant
US6173293B1	Cites	United States of America	Applicant
US6185569B1	Cites	United States of America	Applicant
US6185574B1	Cites	United States of America	Applicant
US6208659B1	Cites	United States of America	Applicant
US6233606B1	Cites	United States of America	Applicant
US6240416B1	Cites	United States of America	Applicant
US6259723B1	Cites	United States of America	Applicant
US6260040B1	Cites	United States of America	Applicant
US6263348B1	Cites	United States of America	Applicant
US6269080B1	Cites	United States of America	Applicant
US6295538B1	Cites	United States of America	Applicant
US6324544B1	Cites	United States of America	Applicant
US6338057B1	Cites	United States of America	Applicant
US6345288B1	Cites	United States of America	Applicant
US6370547B1	Cites	United States of America	Applicant
US6389433B1	Cites	United States of America	Applicant
US6405315B1	Cites	United States of America	Applicant
US6415280B1	Cites	United States of America	Applicant
US6415372B1	Cites	United States of America	Applicant
US6463535B1	Cites	United States of America	Applicant
US6466978B1	Cites	United States of America	Applicant
US6477544B1	Cites	United States of America	Applicant
US6484186B1	Cites	United States of America	Applicant
US6484204B1	Cites	United States of America	Applicant
US6493804B1	Cites	United States of America	Applicant
US6510426B1	Cites	United States of America	Applicant
US6516350B1	Cites	United States of America	Applicant
US6522423B2	Cites	United States of America	Applicant
US6535894B1	Cites	United States of America	Applicant
US6556998B1	Cites	United States of America	Applicant
US6560706B1	Cites	United States of America	Applicant
US6577734B1	Cites	United States of America	Applicant
US6671821B1	Cites	United States of America	Applicant
US6704730B2	Cites	United States of America	Applicant
US6711559B1	Cites	United States of America	Applicant
US6718360B1	Cites	United States of America	Applicant
US6721880B1	Cites	United States of America	Applicant
US6725373B2	Cites	United States of America	Applicant
US6738797B1	Cites	United States of America	Applicant
US6742114B1	Cites	United States of America	Applicant
US6748538B1	Cites	United States of America	Applicant
US6751627B2	Cites	United States of America	Applicant
US6766367B1	Cites	United States of America	Applicant
US6775703B1	Cites	United States of America	Applicant
US6788769B1	Cites	United States of America	Applicant
US6928426B2	Cites	United States of America	Applicant

Showing 100 of 232

12 members in 1 office

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
76496201	United States of America	A	2001-01-17
76496201	United States of America	A	2001-01-17
98520204	United States of America	A	2004-11-10
09764962	–	–	–
US20010764962	–	–	–
US20040985202	–	–	–

Members12

Family members, oldest first
Document	Office	Kind
US2002095590A1	United States of America	A1	2002-07-18
US2005066183A1	United States of America	A1	2005-03-24
US2005066184A1	United States of America	A1	2005-03-24
US2005066185A1	United States of America	A1	2005-03-24
US7047420B2	United States of America	B2	2006-05-16
US2006107048A1	United States of America	A1	2006-05-18
US2007076881A1	United States of America	A1	2007-04-05
US7475258B2	United States of America	B2	2009-01-06
US7555656B2This record	United States of America	B2	2009-06-30
US7571327B2	United States of America	B2	2009-08-04
US7685415B2	United States of America	B2	2010-03-23
US7770023B2	United States of America	B2	2010-08-03

119 transactions on the USPTO file

Allowed after 1 non-final rejection and 1 RCE.

Non-final rejections: 1
Final rejections: 0
RCEs: 1
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2021-08-02	Expire PatentEXP.	EXP.
2021-02-15	Maintenance Fee Reminder MailedREM.	REM.
2009-06-30	Recordation of Patent Grant MailedPGM/	PGM/
2009-06-30	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2009-06-30	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2009-06-10	Issue Notification MailedAllowedWPIR	WPIR
2009-05-29	Dispatch to FDCD1935	D1935
2009-05-27	Issue Fee Payment VerifiedN084	N084
2009-05-27	Issue Fee Payment ReceivedIFEE	IFEE
2009-04-30	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2009-04-20	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2009-02-26	Information Disclosure Statement consideredIDSC	IDSC
2009-02-26	Reference capture on IDSRCAP	RCAP
2009-02-26	Information Disclosure Statement (IDS) FiledM844	M844
2009-02-26	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2009-02-10	Date Forwarded to ExaminerFWDX	FWDX
2009-02-10	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2009-02-02	Mail-Record Petition Decision of Granted to Withdraw from Issue - with assigned Patent NO.MP015	MP015
2009-02-02	Record Petition Decision of Granted to Withdraw from Issue - with assigned Patent NO.P015	P015
2009-02-02	Withdrawal Patent Case from IssueWFIS	WFIS
2009-01-30	Information Disclosure Statement consideredIDSC	IDSC
2009-01-30	Reference capture on IDSRCAP	RCAP
2009-01-30	Electronic Information Disclosure StatementEIDS.	EIDS.
2009-01-30	Request for Continued Examination (RCE)RCEX	RCEX
2009-01-30	Petition EnteredPET.	PET.
2009-01-30	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2009-01-30	Workflow - Request for RCE - BeginBRCE	BRCE
2009-01-21	Issue Notification MailedAllowedWPIR	WPIR
2009-01-12	Dispatch to FDCD1935	D1935
2009-01-09	Application Is Considered Ready for IssuePILS	PILS
2009-01-06	Issue Fee Payment VerifiedN084	N084
2009-01-06	Issue Fee Payment ReceivedIFEE	IFEE
2008-11-26	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2008-11-18	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2008-10-07	Information Disclosure Statement consideredIDSC	IDSC
2008-10-07	Reference capture on IDSRCAP	RCAP
2008-10-07	Information Disclosure Statement (IDS) FiledM844	M844
2008-10-07	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-10-06	Case Docketed to Examiner in GAUDOCK	DOCK
2008-09-11	Paralegal or electronic terminal disclaimer approvedP574	P574
2008-09-11	Paralegal or electronic terminal disclaimer approvedP574	P574
2008-09-11	Paralegal or electronic terminal disclaimer approvedP574	P574
2008-09-11	Paralegal or electronic terminal disclaimer approvedP574	P574
2008-09-11	Date Forwarded to ExaminerFWDX	FWDX
2008-08-11	Mail Examiner Interview Summary (PTOL - 413)MEXIN	MEXIN
2008-08-06	Information Disclosure Statement consideredIDSC	IDSC
2008-08-06	Terminal Disclaimer FiledDIST	DIST
2008-08-06	Terminal Disclaimer FiledDIST	DIST
2008-08-06	Terminal Disclaimer FiledDIST	DIST
2008-08-06	Terminal Disclaimer FiledDIST	DIST
2008-08-06	Response after Non-Final ActionA...	A...
2008-08-06	Request for Extension of Time - GrantedXT/G	XT/G
2008-08-06	Electronic Information Disclosure StatementEIDS.	EIDS.
2008-08-06	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-08-05	Examiner Interview Summary Record (PTOL - 413)EXIN	EXIN
2008-05-20	Information Disclosure Statement consideredIDSC	IDSC
2008-05-20	Electronic Information Disclosure StatementEIDS.	EIDS.
2008-05-20	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-04-07	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2008-04-03	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-02-26	Electronic Information Disclosure StatementEIDS.	EIDS.
2008-02-26	Information Disclosure Statement consideredIDSC	IDSC
2008-02-26	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-12-17	Information Disclosure Statement consideredIDSC	IDSC
2007-12-17	Miscellaneous Incoming LetterLET.	LET.
2007-12-17	Information Disclosure Statement (IDS) FiledM844	M844
2007-12-17	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-12-11	Case Docketed to Examiner in GAUDOCK	DOCK
2007-12-10	Transfer Inquiry to GAUTI1050	TI1050
2007-12-04	Case Docketed to Examiner in GAUDOCK	DOCK
2007-11-07	Case Docketed to Examiner in GAUDOCK	DOCK
2007-10-17	Withdraw Flagged for 5/25W525	W525
2007-10-15	Flagged for 5/25F525	F525
2007-04-24	Case Docketed to Examiner in GAUDOCK	DOCK
2006-12-11	Information Disclosure Statement consideredIDSC	IDSC
2006-12-11	Reference capture on IDSRCAP	RCAP
2006-12-11	Information Disclosure Statement (IDS) FiledM844	M844
2006-12-11	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-08-30	Information Disclosure Statement consideredIDSC	IDSC
2006-08-30	Information Disclosure Statement consideredIDSC	IDSC
2006-08-30	Information Disclosure Statement (IDS) FiledM844	M844
2006-08-30	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-08-30	Information Disclosure Statement (IDS) FiledM844	M844
2006-08-30	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-08-30	Reference capture on IDSRCAP	RCAP
2006-06-16	Information Disclosure Statement consideredIDSC	IDSC
2006-06-16	Reference capture on IDSRCAP	RCAP
2006-06-16	Information Disclosure Statement (IDS) FiledM844	M844
2006-06-16	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-02-10	Case Docketed to Examiner in GAUDOCK	DOCK
2005-12-20	Information Disclosure Statement consideredIDSC	IDSC
2005-12-20	Reference capture on IDSRCAP	RCAP
2005-12-20	Information Disclosure Statement (IDS) FiledM844	M844
2005-12-20	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-10-05	Information Disclosure Statement consideredIDSC	IDSC
2005-10-05	Reference capture on IDSRCAP	RCAP
2005-10-05	Information Disclosure Statement (IDS) FiledM844	M844
2005-10-05	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-05-10	Case Docketed to Examiner in GAUDOCK	DOCK
2005-05-06	Information Disclosure Statement consideredIDSC	IDSC

Showing 100 of 119

9 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2021-08-24	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2021-08-02	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2021-08-02	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2021-02-15	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2016-12-15	Fee paymentFPAY	FPAY
2014-12-09	AssignmentAS	AS
2012-10-04	Fee paymentFPAY	FPAY
2009-06-10	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2008-10-31	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP

Exclusive encryption

Summary by NHIP

Claim Score by NHIP

Abstract