US9009491B2 - Distributed storage network and method for encrypting and decrypting data using hash functions - Google Patents
Distributed storage network and method for encrypting and decrypting data using hash functions Download PDFInfo
- Publication number
- US9009491B2 US9009491B2 US13/736,848 US201313736848A US9009491B2 US 9009491 B2 US9009491 B2 US 9009491B2 US 201313736848 A US201313736848 A US 201313736848A US 9009491 B2 US9009491 B2 US 9009491B2
- Authority
- US
- United States
- Prior art keywords
- encrypted
- portions
- data
- pluralities
- multitude
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1004—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's to protect a block of data words, e.g. CRC or checksum
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/14—Protection against unauthorised use of memory or access to memory
- G06F12/1408—Protection against unauthorised use of memory or access to memory by using cryptography
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/04—Protocols for data compression, e.g. ROHC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0863—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving passwords or one-time passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2107—File encryption
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2151—Time stamp
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/34—Encoding or coding, e.g. Huffman coding or error correction
Definitions
- This invention relates generally to computing and more particularly to storage of information.
- Computing systems are known to communicate, process, and store data. Such computing systems range from wireless smart phones to data centers that support millions of web searches, stock trades, or on-line purchases every day.
- Computing processing is known to manipulate data from one form into another. For instance, raw picture data from an image sensor may be compressed, or manipulated, in accordance with a picture compression standard to produce a standardized compressed picture that can be saved or shared with others.
- Computer processing capability continues to advance as processing speed advances and software applications that perform the manipulation become more sophisticated.
- computers may manipulate real time media from voice to streaming high definition (HD) video.
- Purpose-built communications devices like the cell phone, are being replaced or augmented by more general-purpose information appliances.
- smart phones can support telephony communications but they are also capable of text messaging, and accessing the internet to perform functions including email, web browsing, remote applications access, and media communications.
- Media communications may include telephony voice, image transfer, music files, video files, real time video streaming, and more.
- Each type of computing system is constructed, and hence operates, in accordance with one or more communication, processing, and storage standards.
- communication, processing, and storage standards With such standards, and with advances in technology, more and more of the global information content is being successfully converted into electronic formats and consumed by users in these electronic formats. For example, more digital cameras are now being sold than film cameras, thus producing more digital pictures that are shared and viewed electronically.
- High growth rates have consistently been observed for web-based programming.
- Web-based programming is electronically distributing among billions of users a large amount of content over the Internet and this content was, until recently, all broadcast by just a few entities over the air television stations and cable television providers.
- Digital content standards such as used in pictures, papers, books, video entertainment, home video, all enable this global transformation to a digital format. Electronic content pervasiveness is producing increasing demands on the storage function of computing systems.
- a typical computer storage function includes one or more memory devices that match the needs of the various operational aspects of the processing and communication functions.
- a memory device may include solid-state NAND flash, random access memory (RAM), read only memory (ROM), a mechanical hard disk drive, or other types of storage.
- RAM random access memory
- ROM read only memory
- Each type of memory device has a particular performance range, use case, operational environment, and normalized cost.
- the computing system architecture optimizes the use of one or more types of memory devices to achieve the desired functional, cost, reliability, performance goals, etc. of the computing system.
- the immediacy of access dictates what type of memory device is used.
- RAM memory can be accessed in any random order, all with a constant response time.
- memory device technologies that require physical movement such as magnetic discs, tapes, and optical discs, have a variable response times as the physical movement can take longer than the data transfer, but often these devices can store larger volumes of data in a reliable manner, long-term manner.
- Each type of computer storage system is constructed, and hence operates, in accordance with one or more storage standards.
- computer storage systems may operate in accordance with one or more standards including, but not limited to network file system (NFS), flash file system (FFS), disk file system (DFS), small computer system interface (SCSI), internet small computer system interface (iSCSI), file transfer protocol (FTP), and web-based distributed authoring and versioning (WebDAV).
- An operating systems (OS) and storage standard may specify the data storage format and interface between the processing subsystem and the memory devices.
- the interface may specify a structure, such as directories and files.
- a memory controller provides an interface function between the processing function and memory devices. As new storage systems are developed, the memory controller functional requirements may change to adapt to new standards.
- Memory devices are subject to failure and will eventually fail, especially those memory devices that utilize technologies that require physical movement, like a disc drive. For example, it is not uncommon for a disc drive to suffer from bit level corruption on a regular basis, or suffer from a complete drive failure after an average of three years of use.
- One common solution is to utilize more costly disc drives that have higher quality internal components.
- Another solution is to utilize multiple levels of redundant disc drives to abate these issues by replicating the data into two or more copies.
- One such redundant drive approach is called redundant array of independent discs (RAID).
- RAID redundant array of independent discs
- Multiple physical discs comprise an array where parity data is added to the original data before storing the data across the array. The parity is calculated such that the failure of one or more discs will not result in the loss of the original data.
- RAID 5 uses three or more discs to protect data from the failure of any one disc.
- RAID 6 can recover from a loss of two discs and requires a minimum of four discs with an efficiency of n ⁇ 2.
- Typical RAID systems utilize a RAID control to encode and decode the data across the array.
- the drawbacks of the RAID approach include effectiveness, efficiency, and security. As more discs are added, the probability of one or two discs failing rises and is not negligible, especially if the more-desirable and less-costly discs are used. When one disc fails, it should be immediately replaced and the data reconstructed before a second drive fails, whereby data full recover is no longer an option. To provide high reliability over a long time period, it is also common to mirror RAID arrays at different physical locations, especially if the RAID array is part of a national level computing system with occasional site outages. Unauthorized file access becomes a more acute problem when whole copies of the same file are replicated in many locations/geographies, either on just one storage system site or at two or more sites. In light of the effectiveness, the efficiency of dedicating 1 to 2 discs per array for the RAID data-recovery overhead is an issue.
- FIG. 1 is a schematic block diagram of an embodiment of a computing system in accordance with the invention.
- FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the invention.
- FIG. 3 is a schematic block diagram of an embodiment of a distributed storage processing unit in accordance with the invention.
- FIG. 4 is a schematic block diagram of an embodiment of a grid module in accordance with the invention.
- FIG. 5 is a diagram of an example embodiment of error coded data slice creation in accordance with the invention.
- FIG. 6 is a flowchart illustrating the segmentation of data in the system(s) taught herein;
- FIG. 7 is a flowchart illustrating the encryption of data in the system(s) taught herein;
- FIG. 8 is a flowchart illustrating the decryption of data in the system(s) taught herein;
- FIG. 9 is a flowchart illustrating the storing of an encryption key in the system(s) taught herein;
- FIG. 10 is a flowchart illustrating the retrieval of an encryption key in the system(s) taught herein;
- FIG. 11 is a schematic block diagram of another embodiment of a computing system in accordance with the invention.
- FIG. 12 is a schematic block diagram of another embodiment of a computing system in accordance with the invention.
- FIG. 1 is a schematic block diagram of a computing system 10 that includes one or more of a first type of user device(s) 12 , one or more of a second type of user device(s) 14 , at least one distributed storage (DS) processing unit 16 , at least one DS managing unit 18 , at least one storage integrity processing unit 20 , and a distributed storage network (DSN) memory 22 coupled via a network 24 .
- the network 24 may include one or more wireless and/or wire-lined communication systems, including one or more private intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).
- LAN local area network
- WAN wide area networks
- the DSN memory 22 includes a plurality of distributed storage (DS) units 36 for storing data for the system.
- Each of the DS units 36 includes a processing module and memory and may be located at a geographically different site than the other DS units (e.g., one in Chicago, one in Milwaukee, one in Tokyo, one in Paris, etc.).
- the processing module may be a single processing device or a plurality of processing devices.
- Such a processing device may be a microprocessor, micro-controller, graphics processing unit, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions.
- the processing module may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module.
- Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital or computer information.
- the processing module includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be located in a distributed fashion (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network, peer-to-peer, etc.).
- the processing module implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry
- the memory and/or memory element(s) storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.
- the memory element stores, and the processing module executes, hard-coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 1-12 .
- Each of the user devices 12 - 14 , the DS processing unit 16 , the DS managing unit 18 , and the storage integrity processing unit 20 may be a portable computing device (e.g., one or more of a social networking device, a gaming device, a cell phone, a tablet, a netbook, a smart phone, a personal digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a video game controller, and/or any other portable device that includes a computing core) and/or a fixed computing device (e.g., one or more of a personal computer, a workstation, a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, automotive entertainment device, industrial controls, a video game console, and/or any type of home or office computing equipment).
- a portable or fixed computing device includes a computing core 26 and one or more interfaces 30 , 32 , and/or 33 .
- each of the interfaces 30 - 33 includes software and/or hardware to support one or more communication links via the network 24 and/or directly.
- interfaces 30 support a communication link (wired, wireless, direct, via a LAN, via the network 24 , etc.) between the first type of user device 14 and the DS processing unit 16 .
- DSN interface 32 supports a plurality of communication links via the network 24 between the DSN memory 22 and the DS processing unit 16 , the first type of user device 12 , and/or the storage integrity processing unit 20 .
- interface 33 supports a communication link between the DS managing unit 18 and any one of the other devices and/or units 12 , 14 , 16 , 20 , and/or 22 via the network 24 .
- the system 10 supports three primary functions: distributed network data storage management, distributed data storage and retrieval, and data storage integrity verification.
- data can be stored in a distributed manner in a plurality of physically different locations and subsequently retrieved in a reliable and secure manner regardless of failures of individual storage devices, failures of network equipment, the duration of storage, the amount of data being stored, attempts at hacking the data, etc.
- the DS managing unit 18 performs distributed network data storage management functions, which include establishing distributed data storage parameters, performing network operations, performing network administration, and/or performing network maintenance.
- the DS managing unit 18 establishes the distributed data storage parameters (e.g., allocation of virtual DSN memory space, distributed storage parameters, security parameters, billing information, user profile information, etc.) for one or more of the user devices 12 - 14 (e.g., established for individual devices, established for a user group of devices, established for public access by the user devices, etc.).
- the DS managing unit 18 coordinates the creation of a vault (e.g., a virtual memory block) within the DSN memory 22 for a user device (for a group of devices, or for public access).
- a vault e.g., a virtual memory block
- the DS managing unit 18 also determines the distributed data storage parameters for the vault. In particular, the DS managing unit 18 determines a number of slices (e.g., the number that a data segment of a data file and/or data block is partitioned into for distributed storage) and a read threshold value (e.g., the minimum number of valid slices required to reconstruct the full and originally-stored data segment).
- a number of slices e.g., the number that a data segment of a data file and/or data block is partitioned into for distributed storage
- a read threshold value e.g., the minimum number of valid slices required to reconstruct the full and originally-stored data segment.
- the DS managing module 18 creates and stores, locally or within the DSN memory 22 , user profile information.
- the user profile information includes one or more of authentication information, permissions, and/or the security parameters.
- the security parameters may include one or more of encryption/decryption scheme, one or more encryption keys, key generation scheme, and data encoding/decoding scheme.
- the DS managing unit 18 creates billing information for a particular user, user group, vault access, public vault access, etc. For instance, the DS managing unit 18 tracks the number of times a user accesses a private vault and/or public vaults, which can be used to generate a per-access bill. In another instance, the DS managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate a per-data-amount bill.
- the DS managing unit 18 also performs network operations, network administration, and/or network maintenance. As at least part of performing the network operations and/or administration, the DS managing unit 18 monitors performance of the devices and/or units of the system 10 for potential failures, determines the devices and/or unit's activation status, determines the devices' and/or units' loading, and any other system level operation that affects the performance level of the system 10 . For example, the DS managing unit 18 receives and aggregates network management alarms, alerts, errors, status information, performance information, and messages from the devices 12 - 14 and/or the units 16 , 20 , 22 . For example, the DS managing unit 18 receives a simple network management protocol (SNMP) message regarding the status of the DS processing unit 16 .
- SNMP simple network management protocol
- the DS managing unit 18 performs the network maintenance by identifying equipment within the system 10 that needs replacing, upgrading, repairing, and/or expanding. For example, the DS managing unit 18 determines that the DSN memory 22 needs more DS units 36 or that one or more of the DS units 36 needs updating, software upgrades, more memory, etc.
- the second primary function begins and ends with a user device 12 - 14 .
- a second type of user device 14 has a data file 38 and/or data block 40 to store in the DSN memory 22 , it send the data file 38 and/or data block 40 to the DS processing unit 16 via its interface 30 .
- a second type of user device 14 has a data file 38 and/or data block 40 to store in the DSN memory 22 , it send the data file 38 and/or data block 40 to the DS processing unit 16 via its interface 30 .
- the interface 30 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.).
- OS operating system
- NFS network file system
- FFS flash file system
- DFS disk file system
- FTP file transfer protocol
- WebDAV web-based distributed authoring and versioning
- the interface 30 may attach a user identification code (ID) to the data file 38 and/or data block 40 .
- ID user identification code
- the DS processing unit 16 receives the data file 38 and/or data block 40 via its interface 30 and performs a distributed storage (DS) process 34 thereon (e.g., an error-coding dispersal storage function).
- the DS processing 34 begins by partitioning the data file 38 and/or data block 40 into one or more data segments, which is represented as Y data segments.
- the DS processing 34 error encodes (e.g., forward error correction (FEC), information dispersal algorithm, or error correction coding) and slices (or slices then error encodes) the data segment into a plurality of error coded (EC) data slices 42 - 48 , which is represented as X slices per data segment in the Y data segments.
- FEC forward error correction
- EC error coded
- n/k For example, if a Reed-Solomon (or other FEC scheme) is used in an n/k system, then a data segment is divided into n slices, where k number of slices is needed to reconstruct the original data (i.e., k is the threshold).
- k is the threshold
- the n/k factor may be 5/3; 6/4; 8/6; 8/5; 16/10.
- the DS processing unit 16 For each slice 42 - 48 , the DS processing unit 16 creates a unique slice name and appends it to the corresponding slice 42 - 48 .
- the slice name includes universal DSN memory addressing routing information (e.g., virtual memory addresses in the DSN memory 22 ) and user-specific information (e.g., user ID, file name, data block identifier, etc.).
- the DS processing unit 16 transmits the plurality of EC slices 42 - 48 to a plurality of DS units 36 of the DSN memory 22 via the DSN interface 32 and the network 24 .
- the DSN interface 32 formats each of the slices for transmission via the network 24 .
- the DSN interface 32 may utilize an internet protocol (e.g., TCP/IP, etc.) to packetize the slices 42 - 48 for transmission via the network 24 .
- the number of DS units 36 receiving the slices 42 - 48 is dependent on the distributed data storage parameters established by the DS managing unit 18 .
- the DS managing unit 18 may indicate that each slice is to be stored in a different DS unit 36 .
- the DS managing unit 18 may indicate that like slice numbers of different data segments are to be stored in the same DS unit 36 .
- the first slice of each of the data segments is to be stored in a first DS unit 36
- the second slice of each of the data segments is to be stored in a second DS unit 36 , etc.
- the data is encoded and stored in a distributed manner at physically diverse locations to improved data storage integrity and security. Further examples of encoding the data segments will be provided with reference to one or more of FIGS. 2-12 .
- Each DS unit 36 that receives a slice 42 - 48 for storage translates the virtual DSN memory address of the slice into a local physical address for storage. Accordingly, each DS unit 36 maintains a virtual-to-physical memory mapping to assist in the storage and retrieval of data.
- the first type of user device 12 performs a similar function to store data in the DSN memory 22 with the exception that it includes the DS processing. As such, the device 12 encodes and slices the data file and/or data block it has to store. The device then transmits the slices 35 to the DSN memory via its DSN interface 32 and the network 24 .
- a second type of user device 14 For a second type of user device 14 to retrieve a data file or data block from memory, it issues a read command via its interface 30 to the DS processing unit 16 .
- the DS processing unit 16 performs the DS processing 34 to identify the DS units 36 storing the slices of the data file and/or data block based on the read command.
- the DS processing unit 16 may also communicate with the DS managing unit 18 to verify that the user device 14 is authorized to access the requested data.
- the DS processing unit 16 issues slice read commands to at least a threshold number of the DS units 36 storing the requested data (e.g., to at least 10 DS units for a 16/10 error coding scheme).
- Each of the DS units 36 receiving the slice read command verifies the command, accesses its virtual to physical memory mapping, retrieves the requested slice, or slices, and transmits it to the DS processing unit 16 .
- the DS processing unit 16 After the DS processing unit 16 has received a read threshold number of slices for a data segment, it performs an error decoding function and de-slicing to reconstruct the data segment. When Y number of data segments has been reconstructed, the DS processing unit 16 provides the data file 38 and/or data block 40 to the user device 14 . Note that the first type of user device 12 performs a similar process to retrieve a data file and/or data block.
- the storage integrity processing unit 20 performs the third primary function of data storage integrity verification.
- the storage integrity processing unit 20 periodically retrieves slices 45 , and/or slice names, of a data file or data block of a user device to verify that one or more slices have not been corrupted or lost (e.g., the DS unit failed).
- the retrieval process mimics the read process previously described.
- the storage integrity processing unit 20 determines that one or more slices is corrupted or lost, it rebuilds the corrupted or lost slice(s) in accordance with the error-coding scheme.
- the storage integrity processing unit 20 stores the rebuild slice, or slices, in the appropriate DS unit(s) 36 in a manner that mimics the write process previously described.
- FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50 , a memory controller 52 , main memory 54 , a video graphics processing unit 55 , an input/output (IO) controller 56 , a peripheral component interconnect (PCI) interface (or another type of interface) 58 , at least one IO device interface module 62 , a read only memory (ROM) basic input output system (BIOS) 64 , and one or more memory interface modules.
- IO input/output
- PCI peripheral component interconnect
- IO device interface module 62 or another type of interface
- ROM read only memory
- BIOS basic input output system
- the memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66 , a host bus adapter (HBA) interface module 68 , a network interface module 70 , a flash interface module 72 , a hard drive interface module 74 , and a DSN interface module 76 .
- USB universal serial bus
- HBA host bus adapter
- network interface module 70 may function as the interface 30 of the user device 14 of FIG. 1 .
- the IO device interface module 62 and/or the memory interface modules may be collectively or individually referred to as IO ports.
- the processing module 50 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions.
- the processing module 50 may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module 50 .
- Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information.
- the processing module 50 includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be located in a distributed manner (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network).
- the processing module 50 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry
- the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.
- the memory element stores, and the processing module 50 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 1-12 .
- FIG. 3 is a schematic block diagram of an embodiment of a dispersed storage (DS) processing module 34 of user device 12 and/or of the DS processing unit 16 .
- the DS processing module 34 includes a gateway module 78 , an access module 80 , a grid module 82 , and a storage module 84 .
- the DS processing module 34 may also include an interface 30 and the DSnet interface 32 and/or the interfaces may be part of user 12 or of the DS processing unit 14 .
- the DS processing module 34 may further include a bypass/feedback path between the storage module 84 and the gateway module 78 .
- the gateway module 78 receives an incoming data object (e.g., a data file, a data block, an EC data slice, etc.) that includes a user ID field 86 , an object name field 88 , and the data field/object 40 .
- the gateway module 78 authenticates the user associated with the data object by verifying the user ID 86 with the managing unit 18 and/or another authenticating unit.
- the gateway module 78 obtains user information from the management unit 18 , the user device, and/or the other authenticating unit.
- the user information includes a vault identifier, operational parameters, and user attributes (e.g., user data, billing information, etc.) as shown in FIG. 3 .
- a vault identifier identifies a vault, which is a virtual memory space that maps to a set of DS storage units 36 .
- vault 1 i.e., user 1's DSN memory space
- vault 2 i.e., user 2's DSN memory space
- the operational parameters may include an error coding algorithm, the width n (number of pillars X or slices per segment for this vault), a read threshold T, an encryption algorithm, a slicing parameter, a compression algorithm, an integrity check method, caching settings, parallelism settings, and/or other parameters that may be used to access the DSN memory layer.
- the gateway module uses the user information to assign a source name to the data. For instance, the gateway module 60 determines the source name of the data object 40 based on the vault identifier and the data object. For example, the source name may contain a data name (block number or a file number), the vault generation (gen) number, the reserved field (resv), an optional file ID, and the vault identifier (ID). The data name may be randomly assigned but is associated with the user data object 40 .
- the access module 80 receives the data object 40 and creates a series of data segments 1 through Y 90 - 92 therefrom.
- the grid module 82 may pre-manipulate (e.g., compression, encryption, cyclic redundancy check (CRC), etc.) each of the data segments before performing an error coding function of the error coding dispersal storage function to produce a pre-manipulated data segment.
- the grid module 82 then error encodes (e.g., Reed-Solomon, Convolution encoding, Trellis encoding, etc.) the data segment or pre-manipulated data segment into X error coded data slices 42 - 44 .
- the grid module 82 determines a unique slice name for each error coded data slice and attaches it to the data slice.
- the value X is chosen as a parameter of the error coding dispersal storage function.
- Other parameters of the error coding dispersal function include a read threshold T, a write threshold W, etc.
- the write threshold W corresponds to a minimum number of DS storage units that acknowledge proper storage of their respective data slices before the DS processing module indicates proper storage of the encoded data segment. Note that in some embodiments the write threshold is greater than or equal to the read threshold for a given number of pillars (X).
- the grid module 82 also determines which of the DS storage units 36 will store the EC data slices based on a dispersed storage memory mapping associated with the user's vault and/or DS storage unit 36 attributes.
- the DS storage unit attributes includes availability, self-selection, performance history, link speed, link latency, ownership, available DSN memory, domain, cost, a prioritization scheme, a centralized selection message from another source, a lookup table, data ownership, and/or any other factor to optimize the operation of the computing system.
- the number of DS storage units 36 is equal to or greater than the number of pillars (e.g., X) so that no more than one error coded data slice of the same data segment is stored on the same DS storage unit 36 .
- EC data slices of the same pillar number but of different segments may be stored on the same or different DS storage units 36 .
- the storage module 84 performs an integrity check on the EC data slices and, when successful, transmits the EC data slices 1 through X of each segment 1 through Y to the DS Storage units.
- Each of the DS storage units 36 stores its EC data slice and keeps a table to convert the virtual DSN address of the EC data slice into physical storage addresses.
- the user device 12 and/or 14 sends a read request to the DS processing unit 34 , which authenticates the request.
- the DS processing unit 34 sends a read message to each of the DS storage units 36 storing slices of the data object being read.
- the slices are received via the DSnet interface 32 and processed by the storage module 84 , which performs a parity check and provides the slices to the grid module 82 when the parity check was successful.
- the grid module 82 decodes the slices in accordance with the error coding dispersal storage function to reconstruct the data segment.
- the access module 80 reconstructs the data object from the data segments and the gateway module 78 formats the data object for transmission to the user device.
- FIG. 4 is a schematic block diagram of an embodiment of a grid module 82 that includes a control unit 73 , a pre-data manipulator 75 , an encoder 77 , a slicer 79 , a post-data manipulator 81 , a pre-data de-manipulator 83 , a decoder 85 , a de-slicer 87 , and/or a post-data de-manipulator 89 .
- the control unit 73 may be partially or completely external to the grid module 82 .
- the control unit 73 may be part of the computing core at a remote location, part of a user device, part of the DS managing unit 18 , or distributed amongst one or more DS storage units.
- the pre-data manipulator 75 receives a data segment 90 - 92 and a write instruction from an authorized user device.
- the pre-data manipulator 75 determines if pre-manipulation of the data segment 90 - 92 is required and, if so, what type.
- the pre-data manipulator 75 may make the determination independently or based on instructions from the control unit 73 , where the determination is based a computing system-wide predetermination, a table lookup, vault parameters associated with the user identification, the type of data, security requirements, available DSN memory, performance requirements, and/or other metadata.
- the pre-data manipulator 75 manipulates the data segment 90 - 92 in accordance with the type of manipulation.
- the type of manipulation may be compression (e.g., Lempel-Ziv-Welch, Huffman, Golomb, fractal, wavelet, etc.), signatures (e.g., Digital Signature Algorithm (DSA), Elliptic Curve DSA, Secure Hash Algorithm, etc.), watermarking, tagging, encryption (e.g., Data Encryption Standard, Advanced
- Encryption Standard etc.
- metadata e.g., time/date stamping, user information, file type, etc.
- cyclic redundancy check e.g., CRC32
- the encoder 77 encodes the pre-manipulated data segment 92 using a forward error correction (FEC) encoder (and/or other type of erasure coding and/or error coding) to produce an encoded data segment 94 .
- FEC forward error correction
- the encoder 77 determines which forward error correction algorithm to use based on a predetermination associated with the user's vault, a time based algorithm, user direction, DS managing unit direction, control unit direction, as a function of the data type, as a function of the data segment 92 metadata, and/or any other factor to determine algorithm type.
- the forward error correction algorithm may be Golay, Multidimensional parity, Reed-Solomon, Hamming, Bose Ray Chauduri Hocquenghem (BCH), Cauchy-Reed-Solomon, or any other FEC encoder.
- the encoder 77 may use a different encoding algorithm for each data segment 92 , the same encoding algorithm for the data segments 92 of a data object, or a combination thereof.
- the encoded data segment 94 is of greater size than the data segment 92 by the overhead rate of the encoding algorithm by a factor of d*(X/T), where d is size of the data segment 92 , X is the width or number of slices, and T is the read threshold.
- d size of the data segment 92
- X is the width or number of slices
- T is the read threshold.
- the post-data manipulator 81 performs, if enabled, post-manipulation on the encoded slices to produce the EC data slices. If enabled, the post-data manipulator 81 determines the type of post-manipulation, which may be based on a computing system-wide predetermination, parameters in the vault for this user, a table lookup, the user identification, the type of data, security requirements, available DSN memory, performance requirements, control unit directed, and/or other metadata. Note that the type of post-data manipulation may include slice level compression, signatures, encryption, CRC, addressing, watermarking, tagging, adding metadata, and/or other manipulation to improve the effectiveness of the computing system.
- the post-data de-manipulator 89 receives at least a read threshold number of EC data slices and performs the inverse function of the post-data manipulator 81 to produce a plurality of encoded slices.
- the de-slicer 87 de-slices the encoded slices to produce an encoded data segment 94 .
- the decoder 85 performs the inverse function of the encoder 77 to recapture the data segment 90 - 92 .
- the pre-data de-manipulator 83 performs the inverse function of the pre-data manipulator 75 to recapture the data segment.
- FIG. 5 is a diagram of an example of slicing an encoded data segment 94 by the slicer 79 .
- the encoded data segment includes thirty-two bits, but may include more or less bits.
- the slicer 79 disperses the bits of the encoded data segment 94 across the EC data slices in a pattern as shown. As such, each EC data slice does not include consecutive bits of the data segment 94 reducing the impact of consecutive bit failures on data recovery.
- EC data slice 2 which includes bits 1 , 5 , 9 , 13 , 17 , 25 , and 29 ) is unavailable (e.g., lost, inaccessible, or corrupted)
- the data segment can be reconstructed from the other EC data slices (e.g., 1, 3 and 4 for a read threshold of 3 and a width of 4).
- FIG. 6 is a flowchart illustrating the segmentation of data where the access module 80 of the DS processing system may receive a data object 40 , determine how to perform segmentation, and segment the data object 40 into data segments in accordance with the segmentation determination made by the access module 80 .
- the method begins with the step 100 where the access module 80 of FIG. 3 receives a data object 40 (also shown in FIG. 3 ) and associated source name from the gateway module 78 or any other module of the system.
- the access module 80 determines the size in bytes (or some other quanta) of the data object 40 where the determination is based on incoming metadata, counting the data object bytes when all the data object bytes have been received, and/or some other algorithmic method, via a step 102 .
- the size determination can be made dynamically as the data object is received by the access module 80 , or the size determination can be made after the full receipt of the data object 40 is complete within (or associated with) access module 60
- the access module 80 may determine or associate metadata for the data object where the metadata may include one or more of the data object size, a data type indicator, a priority indicator, a security indicator, and/or a user ID, via a step 104 . This determination may be based on one or more of received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the access module 80 determines a segmentation approach where the approach may include segmenting the data object 40 into equally sized fixed data segments 90 - 92 or segmenting the data object into variable sized data segments 90 - 92 via steps 106 , 108 , 110 , and/or 116 .
- the determination may be based on one or more of the metadata, a system loading indicator, received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the access module 80 may choose the fixed-segment-size approach when the system loading indicator indicates light system loading or if the loading history indicates relatively steady loading.
- the access module 80 may choose the variable approach when the system loading indicator indicates currently heavy system loading such that the incremental load (e.g., of storing the data object) may not adversely affect the system loading.
- the incremental load e.g., of storing the data object
- fixed data segments may be substantially close in size but not identical in size. For example, if a 102 unit object was determined to be split into 4 fixed or equal parts, the parts would likely be of sizes 25, 25, 26, and 26 units. This is the case because the whole does not divide into equal fixed segments. Also, some segments may be appended with header or other metadata that leads one segment to be slightly larger than others. Therefore, when using the term “fixed” herein, the size may be slightly carrying from segment to segment.
- the access module 80 determines a fixed segment size when the access module 80 determines the segmentation approach of segmenting the data object into equally-sized fixed data segments, via steps 106 , 108 , and 110 in FIG. 6 .
- the determination may be based on one or more of the metadata, a system loading indicator, received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the access module 80 may choose a smaller fixed segment size when the system loading indicator indicates the system is loading is heavier than average and choosing smaller segment size will create less incremental loading than larger segments.
- the access module 80 creates a header and appends the header to the data object 40 per a step 112 . In another embodiment, the access module 80 appends the header to two or more (e.g., as many as all) of the data segments 90 - 92 per the step 112 .
- the header may include one or more of the data object size, the metadata, the fixed data segment size, and/or the data segmentation approach.
- the access module 80 segments the data object 40 in accordance with the data segmentation approach and the determined data segment sizes in the step 114 and sends the segments for further processing by the grid module 82 of FIG. 3 .
- the access module 80 determines or selects a variable pattern when the access module 80 determines the segmentation approach of segmenting the data object into variable sized data segments, via steps 106 , 108 , and 116 in FIG. 6 .
- the variable pattern may be static, random, pseudo-random, cyclical, or dynamic (e.g., the pattern may change to another pattern over time or as a function of instantaneous system loading).
- the variable pattern may start with smaller segment sizes and ramp upwards in size over time.
- the variable pattern may start with larger segment sizes and ramp downwards in size over time.
- the variable pattern may alternate between larger segment sizes and smaller segment sizes over time.
- the variable pattern may vary sinusoidally or via some other function over time or size.
- the variable pattern determination may be based on one or more of the metadata, a system loading indicator, received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the access module 80 may choose a smaller fixed segment size to start with and ramp upwards over time when the system loading indicator indicates the system is loading is heavier than average and choosing smaller segment size when that choice will create less incremental loading than larger segments.
- the access module 80 creates a header and appends the header to the data object in the step 118 . In another embodiment, the access module 80 appends the header to two or more (e.g., as many as all) data segments in the step 118 .
- the header may include one or more of the data object size, the metadata, the data segmentation approach, and/or the variable pattern.
- the access module segments the data object in accordance with the data segmentation approach and the determined variable pattern in the step 120 and sends the segments for further processing by the grid module 82 of FIG. 3 .
- the same general computing structure taught herein for enabling functions and modules via input and output interface circuitry coupled to a central processing unit or like one or more processing modules may be used to enable operation of the access module 80 in whole or in part.
- these teachings herein can be used to enable the entire DS processing unit 34 , of which the access module may only use a portion of the overall compute and memory capability of the larger unit 34 .
- the central processing unit or one or more processing modules are coupled to one or more forms of memory devices such as static random access memory, dynamic random access memory, non-volatile memory, cache memory, hard drives, optical storage, or other memory.
- FIG. 7 is a flowchart illustrating the encryption of data where the grid module 82 (see FIG. 3 ) of the DS processing system receives a data segment 90 - 92 and encrypts the data segment 90 - 92 prior to encoding and slicing each data segment to produce EC data slices 42 - 48 with improved security.
- the grid module 82 may contain a pre-data manipulator that may encrypt the data segment as taught herein.
- the method begins with the step 122 where the grid module 82 receives one or more data segments 90 - 92 from the access module 80 or any other module within the system.
- the grid module 82 partitions the data segment 90 or 92 into a first portion and second portion where the portions may be the same or different sizes via a step 124 .
- the grid module may partition the data segment 90 or 92 into more than two portions to obtain N portions where N is a finite integer greater than two. These N portions may be of equal sizes (or nearly equal if the segment does not divide evenly) or different sizes.
- the grid module 82 partitions the data segment 90 or 92 into two or more portions with equal or non-equal sizes based on a partitioning determination.
- the grid module 82 may determine the partitioning based on a security procedure, a security indicator, data object metadata, a system loading indicator, received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the security procedure may indicate that the portion sizes will change with every data segment by 5%.
- the first portion may grow by 5% and the second portion may shrink by 5% for the next data segment, until the first portion is 100% and the second portion is 0% in which case the security procedure may reverse the process.
- even numbered data segments may be partitioned into a 75% first portion and a 25% second portion while odd numbered data segments may be partitioned into a 15% first portion and an 85% second portion.
- any function over time or any other variable may be applied to the partitioning scheme so long as the sending and receiving end are aware of the scheme so that encryption and decryption may commence accurately.
- the function applied may also appear random.
- the sending and receiving end may each contain signature analyzers that are synced to each other, whereby the value of the signature analyzer determines the size or fractional size of first and second segments. For example, if a signature analyzer sequence with a max value of 100 cycles through the following sequence: 74, 12, 32, 89, 54, then the first segment may be set to contain 74% of the total data, 12% of the data, 32% of the data and so on whereby the second segment contains the remainder of the data.
- the grid module calculates a first portion hash value for the first portion in a step 126 .
- the hash function type may be stored in the user vault taught herein and associated with the data segment, slice, or file being processed.
- the grid module 82 may determine a first encryption algorithm based on one or more of a user vault entry, a predetermination, a command, and/or a table lookup utilizing the first portion hash as an index. In a step 128 , the grid module 82 then produces an encrypted second portion by encrypting the second portion utilizing the first encryption algorithm and an encryption key where the encryption key is based in whole or in part on the hash value of the first portion.
- the encryption key may be equal to the first portion hash.
- the encryption key may be a combination of the first portion hash and a second number (e.g. a stored value from the user vault, a calculated value) or may be the first portion hash placed through further processing.
- the grid module then calculates a hash of the encrypted second portion via a step 130 .
- the hash function type may be stored in the user vault associated with the data segment.
- the hash operations for the two segments may be the same or different.
- the grid module 82 may determine a second encryption algorithm based on one or more of a user vault entry, a predetermination, a command, and/or a table lookup utilizing the hash of the encrypted second portion as an index per a step 132 .
- the second encryption algorithm may be the same or different than the first encryption algorithm.
- the grid module 82 then produces an encrypted first portion by encrypting the first portion utilizing the second encryption algorithm and an encryption key where the encryption key is based in whole or in part on the hash of the encrypted second portion.
- the encryption key may be equal to the hash of the encrypted second portion.
- the encryption key may be a combination of the hash of the encrypted second portion and a second number (e.g. a stored value from the user vault, a calculated value) or post-processed in a similar manner to the first portion hash.
- the grid module 82 then combines the encrypted first portion and the encrypted second portion to produce an encrypted data segment in a step 134 .
- an improvement of the method includes providing security with efficiency where the size of the encrypted data segment is equal to the size of the encrypted first portion summed with the size of the encrypted second portion (e.g., no extra bits). Note that security is provided since the decryption method must be known to decrypt the encrypted data segment. The method of decryption is discussed in greater detail with reference to FIG. 8 below.
- segmentation and encryption algorithms taught herein can be applied to the segments through repeated application. Specifically, if there are N partitions or portions, then the algorithm may be run through the partitions or portion up to N times to ensure an all or nothing property (AONT) for the decryption operation. Without this process, if a hacker gains half the data, and part of the other partitioning (e.g., in a two way split) then some data can be yielded.
- AONT all or nothing property
- the cipher mode taught with respect to FIGS. 7-8 may in one embodiment not cause any additional expansion or padding of the message/data.
- Such methods include Counter Mode (CTR), Output Feedback Mode (OFB), Cipher Feedback Mode (CFB), or a stream cipher.
- FIG. 8 is a flowchart illustrating the decryption of data where the grid module 82 of the DS processing system recreates an encrypted data segment (e.g. by retrieving EC data slices, de-slicing the slices, and decoding the slices) and decrypts the encrypted data segment to produce a recreated decrypted data segment.
- the grid module's pre-data de-manipulator may decrypt the data segment.
- the method begins with the step 136 wherein the grid module's pre-data de-manipulator receives an encrypted data segment from the grid module decoder or any other module within the distributed network storage system.
- the grid module 82 partitions the encrypted data segment into an encrypted first portion and an encrypted second portion in a step 138 where the portions may be the same or different sizes.
- the grid module partitions the encrypted data segment into more than two portions.
- the grid module partitions the encrypted data segment into two or more portions with equal or non-equal sizes based on a partitioning determination (e.g., the same as the encryption portioning determination) that results in N partitions where N is a finite integer greater than two.
- the grid module may determine the partitioning based on a security procedure, a security indicator, data object metadata, a system loading indicator, received information appended to the data object, a lookup, a command, a predetermination, data object inspection, and/or a user vault entry.
- the security procedure may indicate that the portion sizes will change with every data segment by 5%.
- the first portion may grow by 5% and the second portion may shrink by 5% for the next data segment, until the first portion is 100% and the second portion is 0% in which case the security procedure may reverse the process.
- even numbered encrypted data segments may be partitioned into a 75% encrypted first portion and a 25% encrypted second portion while odd numbered data segments may be partitioned into a 15% encrypted first portion and a 85% encrypted second portion.
- the partitioning performed by the decryptor is a function of (or is identical to) the encryption partitioning used when encrypting this data segment or data object.
- the encryption and decryption segmentation parameters may be set by data segment, data object, data file, user, geographic location, address space, or some other parameter.
- the grid module 82 then calculates a hash of the encrypted second portion in a step 140 .
- the hash function type may be stored in the user vault associated with the data segment.
- the grid module 82 may then determine a second decryption algorithm based on one or more of a user vault entry, a predetermination, a command, and/or a table lookup utilizing the hash of the encrypted second portion as an index.
- the decryption algorithm must be compatible with the original encryption operation (see FIG. 7 ).
- the grid module 82 produces a decrypted first portion by decrypting the encrypted first portion utilizing the second decryption algorithm and an encryption key where the encryption key is based in whole or in part on the hash of the encrypted second portion via a step 142 .
- the encryption key may be equal to the hash of the encrypted second portion.
- the encryption key may be a combination of the hash of the encrypted second portion and a second number (e.g. a stored value from the user vault, a calculated value).
- the hash value is placed through algorithmic processing of some sort to derive the encryption key used herein.
- the grid module 82 then calculates a decrypted first portion hash by performing a hash on the decrypted first portion via a step 144 .
- the hash function type may be stored in the user vault associated with the data segment.
- the grid module 82 may determine a first decryption algorithm based on one or more of a user vault entry, a predetermination, a command, and/or a table lookup utilizing the decrypted first portion hash as an index. Again, the encryption and decryption operations should be compatible. However, the first decryption algorithm may be the same or different than the second decryption algorithm.
- the grid module 82 produces a decrypted second portion by decrypting the second portion utilizing the first encryption algorithm and an encryption key where the encryption key is based in part on the decrypted first portion hash, as shown in step 146 .
- the encryption key may be equal to the decrypted first portion hash.
- the encryption key may be a combination of the decrypted first portion hash and a second number (e.g. a stored value from the user vault, a calculated value).
- the grid module 82 combines the decrypted first portion and the decrypted second portion to produce a decrypted data segment in a step 148 of FIG. 8 .
- an improvement of this method includes providing security with efficiency where the size of the encrypted data segment is equal to the size of the encrypted first portion summed with the size of the encrypted second portion (e.g., no extra bits). Note that security is provided where the decryption method must be known to decrypt the encrypted data segment.
- FIG. 9 is a flowchart illustrating the storing of an encryption key where the DS managing unit may encrypt the encryption key prior to storing the encryption key.
- keys may be utilized to encrypt and/or decode control information and/or data content.
- a public key may be utilized to encrypt a message from any source to a target destination while a private key may be utilized just by a key owner to decrypt the message for the destination when the message is encrypted utilizing the public key.
- the system may utilize such public/private key pairs for signing integrity to authenticate units, modules, users, devices, and transactions.
- a secret key may be utilized to encrypt and/or decode data content associated with a secret key owner.
- a secret key may be utilized to encrypt a series of data object data segments prior to encoding, slicing, and storing EC data slices in the DSN memory.
- the key owner may utilize the same secret key to subsequently decrypt retrieved, de-sliced, and decoded encrypted data segments.
- the DS managing unit may enforce permissions such that retrieving and storing keys is controlled based on the user ID, the system element ID, and a permissions list lookup. For example, users may have permissions to retrieve and store their own private, public, and secret keys. In another example, users may have permissions to retrieve public keys. In yet another example, The DS managing unit may have permissions to retrieve and store all keys.
- the method begins with the step 150 where the DS managing unit receives a key to store from any other system element.
- the DS managing unit determines an encryption method to encrypt the key to produce an encrypted key.
- the key may be stored in the DSN memory as EC data slices of the encrypted key to provide improved security.
- the encryption methods include a public key method and a password method (the methods will be described below) in step 154 .
- the DS managing unit determines the method to encrypt the key based on one or more of user device connectivity type (e.g., iSCI), a user vault setting, a command, an operational parameter, availability of a public key, and/or availability of a password. For example, the DS managing unit may choose the public key method when the device connectivity type is iSCI (e.g., no password with iSCI).
- the DS managing unit retrieves a public key for the user (or unit) when the DS managing unit determines the method to encrypt the key to be the public key method.
- the DS managing unit may retrieve the public key from the user vault or it may be included with the key to be stored.
- the DS managing unit encrypts the key to be stored to produce an encrypted key utilizing the public key and an encryption algorithm based on the operational parameters (e.g., stored in the user vault).
- the DS managing unit stores the encrypted key in the user vault.
- the DS managing unit may encode and slice the encrypted key and store the EC data slices in the DSN memory.
- the DS managing unit retrieves a password for the user (or unit) in step 156 when the DS managing unit determines the method to encrypt the key to be the password method.
- the DS managing unit may retrieve the password from the user vault or it may be included with the key to be stored.
- the DS managing unit encrypts the key to be stored in step 158 to produce an encrypted key utilizing the public key and an encryption algorithm based on the operational parameters (e.g., stored in the user vault).
- the DS managing unit stores the encrypted key in the user vault in step 160 .
- the DS managing unit may encode and slice the encrypted key and store the EC data slices in the DSN memory.
- the DS managing unit retrieves a password for the user (or unit) in step 162 when the DS managing unit determines the method to encrypt the key to be the password method.
- the DS managing unit may retrieve the password from the user vault or it may be included with the key to be stored.
- the DS managing unit may retrieve a hash algorithm from the user vault.
- the DS managing unit calculates a hash of the password in step 164 to produce a storage key utilizing the hash algorithm.
- the DS managing unit encrypts the key to be stored in step 166 to produce an encrypted key utilizing the storage key and an encryption algorithm based on the operational parameters (e.g., stored in the user vault).
- the DS managing unit stores the encrypted key in the user vault in step 168 .
- the DS managing unit may encode and slice the encrypted key and store the EC data slices in the DSN memory.
- FIG. 10 is a flowchart illustrating the retrieval of an encryption key where the DS managing unit may retrieve an encrypted key and decrypt the encrypted key to provide a key to a requester.
- the method begins with the step 170 where the DS managing unit receives a retrieve key request from a requester (e.g., any system element).
- a requester e.g., any system element.
- the key may be previously stored in the user vault and or DSN memory as an encrypted key as was previously discussed.
- the DS managing unit determines the DSN memory and/or user vault location for the associated encrypted key based on one or more of a user ID, the requester ID, a key use indicator, a lookup, a command, a predetermination, and/or an identifier associated with the key.
- the DS managing unit retrieves the encrypted key based on the location determination in step 172 .
- the DS managing unit determines a decryption method to decrypt the encrypted key to produce a decrypted key in step 174 .
- the encrypted key may be stored in the DSN memory as EC data slices to provide improved security.
- the decryption methods include a public key method and a password method in step 176 (the methods will be described below).
- the DS managing unit determines the method to decrypt the key based on one or more of user device connectivity type (e.g., iSCI), a user vault setting, a command, an operational parameter, availability of a public key, and/or availability of a password. For example, the DS managing unit may choose the password method when a password is available.
- user device connectivity type e.g., iSCI
- a user vault setting e.g., a command, an operational parameter, availability of a public key, and/or availability of a password.
- the DS managing unit may choose the password method when a password is available.
- the DS managing unit retrieves a private key for the user (or unit) in step 178 when the DS managing unit determines the method to decrypt the key to be the public key method.
- the DS managing unit may retrieve the private key from the user vault or it may be included with the key request.
- the DS managing unit decrypts the encrypted key in step 180 to produce the decrypted key utilizing the private key and an encryption algorithm based on the operational parameters (e.g., stored in the user vault).
- the DS managing unit sends the decrypted key to the requester in step 182 .
- the DS managing unit retrieves a password for the user (or unit) in step 184 when the DS managing unit determines the method to decrypt the key to be the password method.
- the DS managing unit may retrieve the password from the user vault or it may be included with the key request.
- the DS managing unit may retrieve a hash algorithm from the user vault.
- the DS managing unit calculates a hash of the password in step 186 to produce a storage key utilizing the hash algorithm.
- the DS managing unit decrypts the encrypted key in step 188 to produce the decrypted key utilizing the storage key and an encryption algorithm based on the operational parameters (e.g., stored in the user vault).
- the DS managing unit sends the decrypted key to the requester in step 190 .
- FIG. 11 is a schematic block diagram of another embodiment of a computing system where a user device 12 may utilize two or more simultaneous wireless connections thru one or a plurality of modules 192 to store and/or retrieve EC data slices to/from the DSN memory associated with DS storage unit(s) 36 .
- a user device 12 may utilize two or more simultaneous wireless connections thru one or a plurality of modules 192 to store and/or retrieve EC data slices to/from the DSN memory associated with DS storage unit(s) 36 .
- Such a system may provide improved performance and security.
- the system includes a user device 12 , a network 24 , and the DSN memory which contains one or more DS units 36 .
- the network 24 may include one or more wireless networks 1 through n to accommodate wireless connections between the user device and the DSN memory. While FIG. 11 shows n wireless signals and n DS units 36 , it should be understood that in another embodiment one wireless signal can serve a plurality of DS units 36 or one wireless module may time multiplex or frequency multiplex process multiple of the wireless signals shown in FIG. 11 . Therefore, the value of n across all of the modules 192 , wireless signals, and DS units 36 need not be equal.
- the user device 12 includes the DS processing unit/function 34 (see FIG. 1 ), the DSN interface 32 (see FIG. 1 ), and one or more wireless modules 192 (1-n modules where n is a finite positive integer).
- the wireless modules 192 may be implemented as n hardware transceivers or fewer than n frequency multiplexed, time multiplexed, or the like.
- the wireless modules 1-n may be implemented as n software modules operating on one hardware transceiver (e.g., a software defined radio (SDR)).
- the wireless modules 1-n may be implemented as n software modules operating on two or more hardware transceivers (e.g., software defined radios).
- the wireless module 192 communicates wireless signals with the network 24 and may operate in accordance with one or more wireless industry standards including but not limited to universal mobile telecommunications system (UMTS), global system for mobile communications (GSM), long term evolution (LTE), wideband code division multiplexing (WCDMA), IEEE 802.11, IEEE 802.16, WiMax, Bluetooth, or any other LAN, WAN, PAN or like wireless protocol. Therefore any two, four, or any number of wireless modules in FIG. 12 may be powered by one or more different wireless protocols.
- UMTS universal mobile telecommunications system
- GSM global system for mobile communications
- LTE long term evolution
- WCDMA wideband code division multiplexing
- IEEE 802.11, IEEE 802.16, WiMax Bluetooth
- any other LAN, WAN, PAN or like wireless protocol any two, four, or any number of wireless modules in FIG. 12 may be powered by one or more different wireless protocols.
- wireless module 1 communicates (e.g., transmits and receives) wireless signals 1 with the network.
- wireless module 2 communicates (e.g., transmits and receives) wireless signals 2 with the network.
- wireless modules 1-n communicate (e.g., transmits and receives) wireless signals 1 -n with the network in this embodiment.
- Wireless modules 1-n may utilize the same or different wireless industry standards.
- wireless module 1 may utilize GSM and wireless module 2 may simultaneously utilize IEEE802.16.
- Wireless modules 1-n may utilize similar or different performance levels (e.g., speed in bits per second) of the wireless signals 1 -n.
- wireless module 1 may communicate at 100 kilobits per second (Kbps) via wireless signals 1 in accordance with the WCDMA standard and wireless module 2 may simultaneously communicate at 3.3 megabits per second (Mbps) via wireless signals 2 in accordance with IEEE 802.11 standard.
- wireless module 1 and wireless module 2 may both utilize the same portion of the network in accordance with the IEEE802.16 standard but operate at different performance levels.
- wireless module 1 may communicate at 350 kilobits per second via wireless signals 1 in accordance with the IEEE 802.16 standard and wireless module 2 may simultaneously communicate at 675 kilobits per second via wireless signals 2 in accordance with IEEE 802.16 standard. Since SDR's are possible in some embodiments, such protocols may be changed over time according to a predetermined security algorithm whereby the protocol on one or more wireless channels is changing over time.
- the DS processing unit/function 34 determines which of the wireless modules 1-n to utilize to transfer slices to and from the DSN memory.
- the DS processing unit/function 34 may determine or select two or more simultaneous wireless paths. For example, the DS processing unit/function 34 may determine to utilize wireless module 1 to communicate slice 1 over wireless signal 1 , wireless module 2 to communicate slice 2 over wireless signal 2 , wireless module 3 to communicate slice 3 over wireless signal 3 , etc. and wireless module n to communicate slice n over wireless signal n.
- the DS processing may determine to utilize wireless module 1 to communicate slice 1 through slice 10 over wireless signal 1 and wireless module 2 to communicate slice 11 through slice n over wireless signal 2 , etc. Therefore, the various wireless channels may communicate different quantities of data over different times or bandwidth availability and may change protocols or encryption techniques in order to improve security.
- the DS processing unit/function 34 creates n slices for storage in the DS units 36 of the DSN memory by creating a data segment, encoding the segment, and slicing the encoded segment into data slices.
- the DS processing unit/function 34 determines performance requirements (e.g., storage and retrieval latencies) and security requirements (e.g., higher or lower level of security) based on user vault information and/or metadata associated with the processed data object 40 .
- the DS processing unit/function 34 determines which wireless modules 192 to utilize to communicate the n slices to the DSN memory.
- the determination may be based on one or more of the performance requirements, the security requirements, and performance indicators for each or some of the wireless modules 192 , and/or security indicators for each of the wireless modules 192 .
- the DS processing unit/function 34 determines a mapping of the n slices to the determined wireless modules 192 where the determination may be based on one or more of the performance requirements, the security requirements, performance indicators for each of the wireless modules 192 , and/or security indicators for each of the wireless modules 192 .
- the DS processing unit/function 34 sends the slices with a store command to the DSN memory via the determined wireless modules 192 and the determined mapping of the n slices to the determined wireless modules 192 .
- the DS processing unit/function 34 retrieves n slices from the various DS unit(s) 36 of the DSN memory in FIG. 11 .
- the DS processing unit/function 34 determines performance requirements (e.g., storage and retrieval latencies) and security requirements (e.g., higher or lower level of security) based on user vault information and/or metadata associated with the data object, or some other method.
- the DS processing unit/function 34 determines the wireless modules 192 to utilize to retrieve the n slices from the DS unit(s) 36 if the DSN memory.
- the determination may be based on one or more of the performance requirements, the security requirements, and performance indicators for each of the wireless modules 192 , and/or security indicators for each of the wireless modules 192 .
- the DS processing unit/function 34 determines a mapping of the n slices to the determined wireless modules 192 where the determination may be based on one or more of the performance requirements, the security requirements, performance indicators for each of the wireless modules 192 n, and/or security indicators for each of the wireless modules 192 .
- the DS processing unit/function 34 sends 192 slice retrieval commands to the DSN memory or individual DS units 26 via the determined wireless modules 192 and the determined mapping of the n slices to the determined wireless modules.
- FIG. 12 is a schematic block diagram of another embodiment of a computing system where error coded (EC) data slices are created and distributed to the DS unit(s) 36 within the DSN memory by one or more user device(s) 12 .
- the EC data slices are video from a video surveillance camera, a television event, stadium camera coverage at a live event (e.g., football or boxing match) or some other stream of video information.
- the system includes user devices 1 -D, the network 24 , the storage integrity processing unit 20 , the DSN memory, and a player.
- user device 1 includes the computing core 26 (containing or connected to the DS processing unit/function 34 ) and the DSN interface 32 .
- An external video camera 194 interfaces with the computing core via one of the interfaces discussed with reference to FIG. 2 , such as USB, firewire, PCI, wireless connections, or like interfaces.
- user device D includes an integrated camera 196 , the computing core 22 (along with the associated DS processing unit/function 34 ), and the DSN interface 32 .
- the internal/integrated video camera also may interface with the computing core 22 via one of the interfaces discussed with reference to FIG. 2 .
- the computing core 22 includes the camera 196 (this configuration is not specifically shown in FIG. 12 ).
- Either or both cameras 194 - 196 may output standard definition (SD) and/or high definition (HD) video utilizing one of a plurality of video codec or video compression algorithms and may interface with the computing core 22 via an analog and/or digital interface that is wired and/or wireline.
- the computing core 22 may communicate control and metadata information with their respective cameras 194 - 196 .
- the control information may include operational instructions including but not limited to the video compression algorithm to utilize, a camera position schedule, pan left, pan right, zoom in, zoom out, change from visible mode to infrared mode, match a pattern, new software load, etc.
- the metadata information may include a timestamp, location information, pattern recognition information, camera setting information, camera direction, camera type, camera software version, 3D rendering data, depth data, facial recognition flags/alerts or information, internet protocol address, camera ID, etc.
- the camera 196 may operate in accordance with the control information and send video and metadata to the computing core 22 .
- the computing core 22 includes the DS processing unit/function 34 .
- the DS processing unit/function 34 may receive the video and metadata from a corresponding one or more cameras 196 .
- the DS processing unit/function 34 determines DSN operational parameters (e.g., number of pillars, encoding method, slicing method, encryption information, and DSN destinations) that are used for transferring and storing camera video. The determination may be based on one or more of an assignment by the DS managing unit, a predetermination, network performance, DSN memory availability, and/or information from the player.
- the DS processing unit/function 34 creates EC data slices of the video and metadata based on the DSN operational parameters.
- the DS processing unit/function 34 sends the EC data slices with a store command via the network to the DSN destinations (e.g., the DSN memory 22 , the player 198 for live viewing a local caching, other camera-equipped user devices for caching and processing).
- the DS processing unit/function 34 may append the operational parameters to the EC data slices such that the player can readily decode the slices and play back the video.
- the player 198 includes a DS processing unit/function 34 that is equipped or associated with the computing core 26 , the DSN interface 32 , and may include an internal or external display(s) 200 to display video.
- the player DS processing unit/function 34 may receive slices from one or more cameras 196 or DSN memory 22 , de-slice and decode the slices in accordance with the operational parameters as taught herein, and route the resulting video to the display(s) 200 .
- the player 198 may further process the video based in part on the metadata to analyze the video (e.g., look for patterns, detect faces, detect objects, detect events, time stamp certain events, etc.).
- the player 198 may send control information to the camera via the network to improve or change/program the operation of the camera 194 and/or 196 .
- the storage integrity processing unit 20 may determine when and how slices stored in the DSN memory are to be deleted, where the determination may be based on one or more of video storage age requirements (e.g., evidence/records retention policy), a current timestamp, a stored video timestamp, the metadata, a command, a command from the player, a command from the camera, a predetermination, and/or a DSN memory availability indicator. For example, the storage integrity processing unit 20 may identify slices of video that are greater than seven years old and the video storage requirements specify seven years. Or, usage data of the video may show that nobody has accessed the video in a threshold amount of time or at a rate that warrants retention. In these events, the storage integrity processing unit 20 sends a delete command to the DSN memory for the determined slices to be deleted, or at least removed from functional memory and sent to backup storage (like tape files or archival disks).
- video storage age requirements e.g., evidence/records retention policy
- a current timestamp e.g.,
- the storage integrity processing unit 20 may determine slices representing video stored in the DSN memory that are to be retrieved, decoded, recompressed, etc., with different video compression algorithms or encodes and may store those new files to the DSN memory 22 .
- the determination for this processing may be based on one or more of video storage age requirements (e.g., evidence/records retention policy), a current timestamp, a stored video timestamp, type of usage, frequency of usage, the metadata, a command, a command from the player, a command from the camera, a predetermination, and/or a DSN memory availability indicator.
- video storage age requirements e.g., evidence/records retention policy
- a current timestamp e.g., evidence/records retention policy
- type of usage e.g., type of usage, frequency of usage
- the metadata e.g., a command, a command from the player, a command from the camera, a predetermination, and/or a DSN memory availability
- the storage integrity processing unit 20 sends a retrieve command to the DSN memory 22 for the determined slices to be recompressed.
- the storage integrity processing unit 20 receives the slices, de-slices and decodes the slices to produce the video in accordance with the operational parameters.
- the storage integrity processing unit 20 also determines a new video compression algorithm based on the metadata, a command, a command from the player, a vault lookup, usage patterns, usage frequency, usage quantity, time accessed, a command from the camera, a predetermination, and/or a DSN memory availability indicator.
- the storage integrity processing unit 20 recompresses the video with a new video compression algorithm that will provide an improvement in memory availability or utilization (e.g., utilize less DSN memory space or free up more accessible or faster space for content that can be processed or delivered faster).
- the storage integrity processing unit 20 determines the new DSN operational parameters to create slices from the recompressed video based on the metadata, a command, a command from the player, a vault lookup, a command from the camera, a predetermination, and/or a DSN memory availability indicator or other parameters taught herein.
- the storage integrity processing unit 20 encodes and slices the recompressed video in accordance with the new DSN operational parameters to produce new slices.
- the storage integrity processing unit sends the new slices with a store command to the DSN memory to store the new data slices.
- the cameras taught in FIG. 12 may be any camera that captures any kind of image in any kind of format or spectrum. So, cameras 196 may be any sensing device, such as video cameras, professional film cameras.
- 3D cameras embedded low cost laptop cameras, security cameras, scientific cameras that capture other spectrums (infrared, gamma ray, ultraviolet, microwave, etc.), night spectrum cameras, heat sensors, simple motion detectors, thermometers, microphones, or any other camera or combination of devices that track audio and/or visual data, spectrum data, or changes in such data over time.
- the system taught in FIG. 12 allows real time or near real time information to be processed and sent using the segment and slice storage and security methodology taught herein. Near real time generally means any processing done within a few seconds to a few minutes of the capture of the real time data. However, if the case of scientific data, as in transmission from satellite or space bound objects, the time may take longer.
- Audio/visual information as used herein means any data or information that contains one or both of audio or visual information.
- the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences.
- the term(s) “coupled to” and/or “coupling” and/or includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level.
- an intervening item e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module
- inferred coupling i.e., where one element is coupled to another element by inference
- the term “operable to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform one or more its corresponding functions and may further include inferred coupling to one or more other items.
- the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.
- the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2 , a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
- Detection And Correction Of Errors (AREA)
Abstract
Description
Claims (17)
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/736,848 US9009491B2 (en) | 2009-10-30 | 2013-01-08 | Distributed storage network and method for encrypting and decrypting data using hash functions |
US14/292,727 US9413529B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
US14/292,772 US9088407B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
US15/230,145 US9819484B2 (en) | 2009-10-30 | 2016-08-05 | Distributed storage network and method for storing and retrieving encryption keys |
US15/442,273 US9772904B2 (en) | 2009-10-30 | 2017-02-24 | Robust reception of data utilizing encoded data slices |
US15/688,030 US10073737B2 (en) | 2009-10-30 | 2017-08-28 | Slice location identification |
US16/002,638 US10496480B2 (en) | 2009-10-30 | 2018-06-07 | Slice location identification |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US25641109P | 2009-10-30 | 2009-10-30 | |
US12/814,467 US8351600B2 (en) | 2009-10-30 | 2010-06-13 | Distributed storage network and method for encrypting and decrypting data using hash functions |
US13/736,848 US9009491B2 (en) | 2009-10-30 | 2013-01-08 | Distributed storage network and method for encrypting and decrypting data using hash functions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/814,467 Continuation US8351600B2 (en) | 2009-10-30 | 2010-06-13 | Distributed storage network and method for encrypting and decrypting data using hash functions |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/292,727 Continuation-In-Part US9413529B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
US14/292,772 Continuation US9088407B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130124875A1 US20130124875A1 (en) | 2013-05-16 |
US9009491B2 true US9009491B2 (en) | 2015-04-14 |
Family
ID=43925003
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/814,474 Active 2033-05-14 US9900150B2 (en) | 2009-10-30 | 2010-06-13 | Dispersed storage camera device and method of operation |
US12/814,467 Active 2031-07-12 US8351600B2 (en) | 2009-10-30 | 2010-06-13 | Distributed storage network and method for encrypting and decrypting data using hash functions |
US12/816,126 Expired - Fee Related US9692593B2 (en) | 2009-10-30 | 2010-06-15 | Distributed storage network and method for communicating data across a plurality of parallel wireless data streams |
US12/818,137 Expired - Fee Related US8468137B2 (en) | 2009-10-30 | 2010-06-17 | Distributed storage network that processes data in either fixed or variable sizes |
US13/736,848 Expired - Fee Related US9009491B2 (en) | 2009-10-30 | 2013-01-08 | Distributed storage network and method for encrypting and decrypting data using hash functions |
US14/292,772 Active US9088407B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/814,474 Active 2033-05-14 US9900150B2 (en) | 2009-10-30 | 2010-06-13 | Dispersed storage camera device and method of operation |
US12/814,467 Active 2031-07-12 US8351600B2 (en) | 2009-10-30 | 2010-06-13 | Distributed storage network and method for encrypting and decrypting data using hash functions |
US12/816,126 Expired - Fee Related US9692593B2 (en) | 2009-10-30 | 2010-06-15 | Distributed storage network and method for communicating data across a plurality of parallel wireless data streams |
US12/818,137 Expired - Fee Related US8468137B2 (en) | 2009-10-30 | 2010-06-17 | Distributed storage network that processes data in either fixed or variable sizes |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/292,772 Active US9088407B2 (en) | 2009-10-30 | 2014-05-30 | Distributed storage network and method for storing and retrieving encryption keys |
Country Status (1)
Country | Link |
---|---|
US (6) | US9900150B2 (en) |
Cited By (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106612328A (en) * | 2016-12-20 | 2017-05-03 | 杭州联众医疗科技股份有限公司 | Mobile radiograph reading system |
US9785495B1 (en) | 2015-12-14 | 2017-10-10 | Amazon Technologies, Inc. | Techniques and systems for detecting anomalous operational data |
US9904589B1 (en) | 2015-07-01 | 2018-02-27 | Amazon Technologies, Inc. | Incremental media size extension for grid encoded data storage systems |
US9928141B1 (en) | 2015-09-21 | 2018-03-27 | Amazon Technologies, Inc. | Exploiting variable media size in grid encoded data storage systems |
US9940474B1 (en) | 2015-09-29 | 2018-04-10 | Amazon Technologies, Inc. | Techniques and systems for data segregation in data storage systems |
US9959167B1 (en) * | 2015-07-01 | 2018-05-01 | Amazon Technologies, Inc. | Rebundling grid encoded data storage systems |
US9998150B1 (en) | 2015-06-16 | 2018-06-12 | Amazon Technologies, Inc. | Layered data redundancy coding techniques for layer-local data recovery |
US9998539B1 (en) | 2015-07-01 | 2018-06-12 | Amazon Technologies, Inc. | Non-parity in grid encoded data storage systems |
US10061668B1 (en) | 2016-03-28 | 2018-08-28 | Amazon Technologies, Inc. | Local storage clustering for redundancy coded data storage system |
US10089176B1 (en) | 2015-07-01 | 2018-10-02 | Amazon Technologies, Inc. | Incremental updates of grid encoded data storage systems |
US10102065B1 (en) | 2015-12-17 | 2018-10-16 | Amazon Technologies, Inc. | Localized failure mode decorrelation in redundancy encoded data storage systems |
US10108819B1 (en) | 2015-07-01 | 2018-10-23 | Amazon Technologies, Inc. | Cross-datacenter extension of grid encoded data storage systems |
US10127105B1 (en) | 2015-12-17 | 2018-11-13 | Amazon Technologies, Inc. | Techniques for extending grids in data storage systems |
US10162704B1 (en) | 2015-07-01 | 2018-12-25 | Amazon Technologies, Inc. | Grid encoded data storage systems for efficient data repair |
US10180912B1 (en) | 2015-12-17 | 2019-01-15 | Amazon Technologies, Inc. | Techniques and systems for data segregation in redundancy coded data storage systems |
US10198311B1 (en) | 2015-07-01 | 2019-02-05 | Amazon Technologies, Inc. | Cross-datacenter validation of grid encoded data storage systems |
US10235402B1 (en) | 2015-12-17 | 2019-03-19 | Amazon Technologies, Inc. | Techniques for combining grid-encoded data storage systems |
US10248793B1 (en) | 2015-12-16 | 2019-04-02 | Amazon Technologies, Inc. | Techniques and systems for durable encryption and deletion in data storage systems |
US10270475B1 (en) | 2015-06-16 | 2019-04-23 | Amazon Technologies, Inc. | Layered redundancy coding for encoded parity data |
US10270476B1 (en) | 2015-06-16 | 2019-04-23 | Amazon Technologies, Inc. | Failure mode-sensitive layered redundancy coding techniques |
US10296764B1 (en) | 2016-11-18 | 2019-05-21 | Amazon Technologies, Inc. | Verifiable cryptographically secured ledgers for human resource systems |
US10298259B1 (en) | 2015-06-16 | 2019-05-21 | Amazon Technologies, Inc. | Multi-layered data redundancy coding techniques |
US10324790B1 (en) | 2015-12-17 | 2019-06-18 | Amazon Technologies, Inc. | Flexible data storage device mapping for data storage systems |
US10360391B2 (en) | 2017-04-03 | 2019-07-23 | International Business Machines Corporation | Verifiable keyed all-or-nothing transform |
US10366062B1 (en) | 2016-03-28 | 2019-07-30 | Amazon Technologies, Inc. | Cycled clustering for redundancy coded data storage systems |
US10394762B1 (en) | 2015-07-01 | 2019-08-27 | Amazon Technologies, Inc. | Determining data redundancy in grid encoded data storage systems |
US10394789B1 (en) | 2015-12-07 | 2019-08-27 | Amazon Technologies, Inc. | Techniques and systems for scalable request handling in data processing systems |
US10437790B1 (en) | 2016-09-28 | 2019-10-08 | Amazon Technologies, Inc. | Contextual optimization for data storage systems |
US10496327B1 (en) | 2016-09-28 | 2019-12-03 | Amazon Technologies, Inc. | Command parallelization for data storage systems |
US10592336B1 (en) | 2016-03-24 | 2020-03-17 | Amazon Technologies, Inc. | Layered indexing for asynchronous retrieval of redundancy coded data |
US20200106820A1 (en) * | 2011-08-31 | 2020-04-02 | Divx, Llc | Systems and Methods for Automatically Generating Top Level Index Files |
US10614239B2 (en) | 2016-09-30 | 2020-04-07 | Amazon Technologies, Inc. | Immutable cryptographically secured ledger-backed databases |
US10642813B1 (en) | 2015-12-14 | 2020-05-05 | Amazon Technologies, Inc. | Techniques and systems for storage and processing of operational data |
US10657097B1 (en) | 2016-09-28 | 2020-05-19 | Amazon Technologies, Inc. | Data payload aggregation for data storage systems |
US10678664B1 (en) | 2016-03-28 | 2020-06-09 | Amazon Technologies, Inc. | Hybridized storage operation for redundancy coded data storage systems |
US10810157B1 (en) | 2016-09-28 | 2020-10-20 | Amazon Technologies, Inc. | Command aggregation for data storage operations |
US10977128B1 (en) | 2015-06-16 | 2021-04-13 | Amazon Technologies, Inc. | Adaptive data loss mitigation for redundancy coding systems |
US11137980B1 (en) | 2016-09-27 | 2021-10-05 | Amazon Technologies, Inc. | Monotonic time-based data storage |
US11204895B1 (en) | 2016-09-28 | 2021-12-21 | Amazon Technologies, Inc. | Data payload clustering for data storage systems |
US11269888B1 (en) | 2016-11-28 | 2022-03-08 | Amazon Technologies, Inc. | Archival data storage for structured data |
US11281624B1 (en) | 2016-09-28 | 2022-03-22 | Amazon Technologies, Inc. | Client-based batching of data payload |
US11349892B2 (en) | 2015-01-06 | 2022-05-31 | Divx, Llc | Systems and methods for encoding and sharing content between devices |
US11386060B1 (en) | 2015-09-23 | 2022-07-12 | Amazon Technologies, Inc. | Techniques for verifiably processing data in distributed computing systems |
Families Citing this family (125)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AUPS169002A0 (en) * | 2002-04-11 | 2002-05-16 | Tune, Andrew Dominic | An information storage system |
US20060167838A1 (en) * | 2005-01-21 | 2006-07-27 | Z-Force Communications, Inc. | File-based hybrid file storage scheme supporting multiple file switches |
US10289688B2 (en) * | 2010-06-22 | 2019-05-14 | International Business Machines Corporation | Metadata access in a dispersed storage network |
US8682916B2 (en) | 2007-05-25 | 2014-03-25 | F5 Networks, Inc. | Remote file virtualization in a switched file system |
US8548953B2 (en) | 2007-11-12 | 2013-10-01 | F5 Networks, Inc. | File deduplication using storage tiers |
US8549582B1 (en) | 2008-07-11 | 2013-10-01 | F5 Networks, Inc. | Methods for handling a multi-protocol content name and systems thereof |
US9495194B1 (en) * | 2008-10-17 | 2016-11-15 | Dispersive Networks, Inc. | Dispersive storage area networks |
US8713661B2 (en) | 2009-02-05 | 2014-04-29 | Wwpass Corporation | Authentication service |
JP5802137B2 (en) | 2009-02-05 | 2015-10-28 | ダブリューダブリューパス コーポレイションWwpass Corporation | Centralized authentication system and method with secure private data storage |
US8752153B2 (en) | 2009-02-05 | 2014-06-10 | Wwpass Corporation | Accessing data based on authenticated user, provider and system |
US8751829B2 (en) | 2009-02-05 | 2014-06-10 | Wwpass Corporation | Dispersed secure data storage and retrieval |
US8839391B2 (en) | 2009-02-05 | 2014-09-16 | Wwpass Corporation | Single token authentication |
US9317717B2 (en) * | 2012-12-28 | 2016-04-19 | Open Invention Network, Llc | Separate cryptographic keys for protecting different operations on data |
US8473677B2 (en) * | 2009-09-29 | 2013-06-25 | Cleversafe, Inc. | Distributed storage network memory access based on memory state |
US10757187B2 (en) * | 2009-10-29 | 2020-08-25 | Pure Storage, Inc. | Streaming all-or-nothing encoding with random offset support |
US10073737B2 (en) | 2009-10-30 | 2018-09-11 | International Business Machines Corporation | Slice location identification |
US9195500B1 (en) | 2010-02-09 | 2015-11-24 | F5 Networks, Inc. | Methods for seamless storage importing and devices thereof |
US9262643B2 (en) * | 2010-02-22 | 2016-02-16 | Sookasa Inc. | Encrypting files within a cloud computing environment |
US10324791B2 (en) * | 2010-11-01 | 2019-06-18 | International Business Machines Corporation | Selectable parallel processing of dispersed storage error encoding |
US11429486B1 (en) | 2010-02-27 | 2022-08-30 | Pure Storage, Inc. | Rebuilding data via locally decodable redundancy in a vast storage network |
US8625635B2 (en) * | 2010-04-26 | 2014-01-07 | Cleversafe, Inc. | Dispersed storage network frame protocol header |
US9235585B1 (en) | 2010-06-30 | 2016-01-12 | Emc Corporation | Dynamic prioritized recovery |
US9697086B2 (en) | 2010-06-30 | 2017-07-04 | EMC IP Holding Company LLC | Data access during data recovery |
US9367561B1 (en) | 2010-06-30 | 2016-06-14 | Emc Corporation | Prioritized backup segmenting |
US9286298B1 (en) | 2010-10-14 | 2016-03-15 | F5 Networks, Inc. | Methods for enhancing management of backup data sets and devices thereof |
US8266110B1 (en) * | 2010-10-22 | 2012-09-11 | Symantec Corporation | Integrated archival and backup |
US9007961B2 (en) | 2010-11-22 | 2015-04-14 | May Patents Ltd. | Apparatus and method for using and solving linear programming problem and applications thereof |
TW201224773A (en) * | 2010-12-10 | 2012-06-16 | Inst Information Industry | System and method for playing advertisement |
US8583911B1 (en) | 2010-12-29 | 2013-11-12 | Amazon Technologies, Inc. | Network application encryption with server-side key management |
US9094379B1 (en) | 2010-12-29 | 2015-07-28 | Amazon Technologies, Inc. | Transparent client-side cryptography for network applications |
US8538020B1 (en) * | 2010-12-29 | 2013-09-17 | Amazon Technologies, Inc. | Hybrid client-server cryptography for network applications |
KR101544483B1 (en) * | 2011-04-13 | 2015-08-17 | 주식회사 케이티 | Replication server apparatus and method for creating replica in distribution storage system |
US8930320B2 (en) * | 2011-09-30 | 2015-01-06 | Accenture Global Services Limited | Distributed computing backup and recovery system |
US9166953B2 (en) | 2011-10-31 | 2015-10-20 | Nokia Technologies Oy | Method and apparatus for providing identity based encryption in distributed computations |
US8656180B2 (en) | 2011-12-06 | 2014-02-18 | Wwpass Corporation | Token activation |
US8972719B2 (en) | 2011-12-06 | 2015-03-03 | Wwpass Corporation | Passcode restoration |
US8555079B2 (en) | 2011-12-06 | 2013-10-08 | Wwpass Corporation | Token management |
US8966021B1 (en) * | 2011-12-20 | 2015-02-24 | Amazon Technologies, Inc. | Composable machine image |
US20130169816A1 (en) * | 2011-12-28 | 2013-07-04 | Jhen-Jia Hu | Monitoring and managing device, monitoring and managing system and method of data center |
US9020912B1 (en) * | 2012-02-20 | 2015-04-28 | F5 Networks, Inc. | Methods for accessing data in a compressed file system and devices thereof |
EP2817917B1 (en) | 2012-02-20 | 2018-04-11 | KL Data Security Pty Ltd | Cryptographic method and system |
WO2013131273A1 (en) * | 2012-03-09 | 2013-09-12 | Empire Technology Development Llc | Cloud computing secure data storage |
WO2013138587A1 (en) * | 2012-03-14 | 2013-09-19 | Convergent .Io Technologies Inc. | Systems, methods and devices for management of virtual memory systems |
US20150046482A1 (en) * | 2012-03-15 | 2015-02-12 | Lei Wang | Two-level chunking for data analytics |
US10795766B2 (en) * | 2012-04-25 | 2020-10-06 | Pure Storage, Inc. | Mapping slice groupings in a dispersed storage network |
US9015106B2 (en) * | 2012-04-30 | 2015-04-21 | Dell Products, Lp | Cloud based master data management system and method therefor |
US9390055B2 (en) | 2012-07-17 | 2016-07-12 | Coho Data, Inc. | Systems, methods and devices for integrating end-host and network resources in distributed memory |
US9519501B1 (en) | 2012-09-30 | 2016-12-13 | F5 Networks, Inc. | Hardware assisted flow acceleration and L2 SMAC management in a heterogeneous distributed multi-tenant virtualized clustered system |
US9503513B2 (en) * | 2012-10-08 | 2016-11-22 | International Business Machines Corporation | Robust transmission of data utilizing encoded data slices |
KR20140052243A (en) * | 2012-10-23 | 2014-05-07 | 한국전자통신연구원 | Apparatus and method for providing network data service, client device for network data service |
GB2556743B (en) * | 2012-12-21 | 2018-12-05 | Displaylink Uk Ltd | Management of memory for storing display data |
US9373001B2 (en) | 2012-12-26 | 2016-06-21 | Barracuda Networks, Inc. | Distributed encryption and access control scheme in a cloud environment |
US9817728B2 (en) | 2013-02-01 | 2017-11-14 | Symbolic Io Corporation | Fast system state cloning |
US9628108B2 (en) | 2013-02-01 | 2017-04-18 | Symbolic Io Corporation | Method and apparatus for dense hyper IO digital retention |
US10133636B2 (en) | 2013-03-12 | 2018-11-20 | Formulus Black Corporation | Data storage and retrieval mediation system and methods for using same |
US9304703B1 (en) | 2015-04-15 | 2016-04-05 | Symbolic Io Corporation | Method and apparatus for dense hyper IO digital retention |
US9467294B2 (en) | 2013-02-01 | 2016-10-11 | Symbolic Io Corporation | Methods and systems for storing and retrieving data |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US9554418B1 (en) | 2013-02-28 | 2017-01-24 | F5 Networks, Inc. | Device for topology hiding of a visited network |
US10057250B2 (en) | 2013-05-14 | 2018-08-21 | Kara Partners Llc | Technologies for enhancing computer security |
US12028333B2 (en) | 2013-05-14 | 2024-07-02 | Kara Partners Llc | Systems and methods for variable-length encoding and decoding for enhancing computer systems |
US10594687B2 (en) | 2013-05-14 | 2020-03-17 | Kara Partners Llc | Technologies for enhancing computer security |
EP2863566B1 (en) | 2013-10-18 | 2020-09-02 | Université de Nantes | Method and apparatus for reconstructing a data block |
JP6305110B2 (en) * | 2014-02-28 | 2018-04-04 | キヤノン株式会社 | Imaging apparatus and imaging system |
US9367253B2 (en) | 2014-03-13 | 2016-06-14 | Vmware, Inc. | Catastrophic data loss avoidance |
US9606769B2 (en) * | 2014-04-05 | 2017-03-28 | Qualcomm Incorporated | System and method for adaptive compression mode selection for buffers in a portable computing device |
US9811677B2 (en) * | 2014-07-03 | 2017-11-07 | Pure Storage, Inc. | Secure data replication in a storage grid |
US9397832B2 (en) | 2014-08-27 | 2016-07-19 | International Business Machines Corporation | Shared data encryption and confidentiality |
US9397833B2 (en) | 2014-08-27 | 2016-07-19 | International Business Machines Corporation | Receipt, data reduction, and storage of encrypted data |
WO2016050287A1 (en) | 2014-09-30 | 2016-04-07 | Nec Europe Ltd. | Method and system for at least partially updating data encrypted with an all-or-nothing encryption scheme |
WO2016115174A1 (en) * | 2015-01-13 | 2016-07-21 | Reflexion Health, Inc. | System and method for storing and transmitting confidential medical information on vulnerable devices and networks |
JP6488221B2 (en) * | 2015-03-30 | 2019-03-20 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Reproduction method and reproduction apparatus |
US10097345B2 (en) * | 2015-04-14 | 2018-10-09 | PeerNova, Inc. | Secure hash algorithm in digital hardware for cryptographic applications |
US10061514B2 (en) | 2015-04-15 | 2018-08-28 | Formulus Black Corporation | Method and apparatus for dense hyper IO digital retention |
US11580125B2 (en) | 2015-05-08 | 2023-02-14 | Adp, Inc. | Information system with temporal data |
US10075386B2 (en) | 2015-05-08 | 2018-09-11 | Adp, Llc | Subscription-based information system |
US11144520B2 (en) | 2015-05-08 | 2021-10-12 | Adp, Llc | Information system with versioning descending node snapshot |
US10169125B2 (en) * | 2015-05-29 | 2019-01-01 | International Business Machines Corporation | Re-encoding data in a dispersed storage network |
US10838664B2 (en) * | 2015-05-29 | 2020-11-17 | Pure Storage, Inc. | Determining a storage location according to legal requirements |
US10108557B2 (en) * | 2015-06-25 | 2018-10-23 | Intel Corporation | Technologies for memory confidentiality, integrity, and replay protection |
US9703789B2 (en) | 2015-07-27 | 2017-07-11 | Sas Institute Inc. | Distributed data set storage and retrieval |
US9946719B2 (en) | 2015-07-27 | 2018-04-17 | Sas Institute Inc. | Distributed data set encryption and decryption |
WO2017079359A1 (en) * | 2015-11-02 | 2017-05-11 | Dispersive Networks, Inc. | Virtual dispersive networking systems and methods |
CN105511809B (en) * | 2015-12-07 | 2019-11-15 | 中国建设银行股份有限公司 | A kind of date storage method and device |
US10572460B2 (en) | 2016-02-11 | 2020-02-25 | Pure Storage, Inc. | Compressing data in dependence upon characteristics of a storage system |
KR102558002B1 (en) * | 2016-02-17 | 2023-07-20 | 삼성전자주식회사 | Filter and device including the filter |
US10331362B1 (en) * | 2016-09-30 | 2019-06-25 | EMC IP Holding Company LLC | Adaptive replication for segmentation anchoring type |
CN109791591B (en) * | 2016-10-06 | 2023-07-07 | 万事达卡国际公司 | Method and system for identity and credential protection and verification via blockchain |
US10412198B1 (en) | 2016-10-27 | 2019-09-10 | F5 Networks, Inc. | Methods for improved transmission control protocol (TCP) performance visibility and devices thereof |
US10567492B1 (en) | 2017-05-11 | 2020-02-18 | F5 Networks, Inc. | Methods for load balancing in a federated identity environment and devices thereof |
CA3213857A1 (en) * | 2017-06-14 | 2018-12-20 | Sas Institute Inc. | Distributed data set encryption and decryption |
CN107277141B (en) * | 2017-06-21 | 2020-03-31 | 京东方科技集团股份有限公司 | Data judgment method applied to distributed storage system and distributed storage system |
US10540198B2 (en) * | 2017-07-01 | 2020-01-21 | Intel Corporation | Technologies for memory replay prevention using compressive encryption |
US11238164B2 (en) * | 2017-07-10 | 2022-02-01 | Burstiq, Inc. | Secure adaptive data storage platform |
JP2019029761A (en) * | 2017-07-27 | 2019-02-21 | 京セラドキュメントソリューションズ株式会社 | Information processing apparatus and method for controlling information processing apparatus |
US10572186B2 (en) | 2017-12-18 | 2020-02-25 | Formulus Black Corporation | Random access memory (RAM)-based computer systems, devices, and methods |
US11223689B1 (en) | 2018-01-05 | 2022-01-11 | F5 Networks, Inc. | Methods for multipath transmission control protocol (MPTCP) based session migration and devices thereof |
US11483739B2 (en) | 2018-02-25 | 2022-10-25 | Nokia Solutions And Networks Oy | Method and system for automated dynamic network slice deployment using artificial intelligence |
US10833943B1 (en) | 2018-03-01 | 2020-11-10 | F5 Networks, Inc. | Methods for service chaining and devices thereof |
US11516013B2 (en) * | 2018-06-28 | 2022-11-29 | Intel Corporation | Accelerator for encrypting or decrypting confidential data with additional authentication data |
US10593152B1 (en) | 2018-08-22 | 2020-03-17 | Aristocrat Technologies Australia Pty Limited | Gaming machine and method for evaluating player reactions |
US11983990B2 (en) | 2018-08-22 | 2024-05-14 | Aristocrat Technologies Australia Pty Limited | Gaming machine and method for evaluating player reactions |
US11409892B2 (en) * | 2018-08-30 | 2022-08-09 | International Business Machines Corporation | Enhancing security during access and retrieval of data with multi-cloud storage |
US12003422B1 (en) | 2018-09-28 | 2024-06-04 | F5, Inc. | Methods for switching network packets based on packet data and devices |
CN109450623A (en) * | 2018-10-16 | 2019-03-08 | 如般量子科技有限公司 | Anti- quantum calculation cryptographic key negotiation method based on unsymmetrical key pond |
US10761932B2 (en) * | 2018-10-25 | 2020-09-01 | Hewlett Packard Enterprise Development Lp | Data and metadata storage in storage devices |
US10949388B2 (en) * | 2018-11-16 | 2021-03-16 | Advanced Messaging Technologies, Inc. | Systems and methods for distributed data storage and delivery using blockchain |
KR102019362B1 (en) * | 2018-11-26 | 2019-09-09 | 제주대학교 산학협력단 | CCTV video data distribution processing device and method thereof |
CN109740371A (en) * | 2018-12-12 | 2019-05-10 | 武汉掌游科技有限公司 | One kind being used for the easy encryption method of Android SDK resource and device |
US10725853B2 (en) | 2019-01-02 | 2020-07-28 | Formulus Black Corporation | Systems and methods for memory failure prevention, management, and mitigation |
US11189130B2 (en) | 2019-01-23 | 2021-11-30 | Aristocrat Technologies Australia Pty Limited | Gaming machine security devices and methods |
CN116232582A (en) | 2019-05-22 | 2023-06-06 | 妙泰公司 | Distributed data storage method and system with enhanced security, resilience and control |
US11263866B2 (en) | 2019-05-31 | 2022-03-01 | Aristocrat Technologies, Inc. | Securely storing machine data on a non-volatile memory device |
US11308761B2 (en) | 2019-05-31 | 2022-04-19 | Aristocrat Technologies, Inc. | Ticketing systems on a distributed ledger |
US11373480B2 (en) | 2019-05-31 | 2022-06-28 | Aristocrat Technologies, Inc. | Progressive systems on a distributed ledger |
US11100236B2 (en) * | 2019-06-26 | 2021-08-24 | Seagate Technology Llc | Distributed data security |
CN110968265B (en) * | 2019-11-05 | 2023-08-08 | 北京字节跳动网络技术有限公司 | Method and device for expanding capacity by fragments and electronic equipment |
US11195371B2 (en) | 2019-12-04 | 2021-12-07 | Aristocrat Technologies, Inc. | Preparation and installation of gaming devices using blockchain |
WO2021138426A1 (en) * | 2019-12-30 | 2021-07-08 | Dogwood Logic, Inc. | Secure decentralized control of network access to ai models and data |
US11418333B2 (en) * | 2020-01-10 | 2022-08-16 | Dell Products L.P. | System and method for trusted control flow enforcement using derived encryption keys |
CN113473645A (en) * | 2020-03-12 | 2021-10-01 | 华为技术有限公司 | Data transmission method and device |
US11636726B2 (en) | 2020-05-08 | 2023-04-25 | Aristocrat Technologies, Inc. | Systems and methods for gaming machine diagnostic analysis |
US11651096B2 (en) | 2020-08-24 | 2023-05-16 | Burstiq, Inc. | Systems and methods for accessing digital assets in a blockchain using global consent contracts |
US11727733B2 (en) | 2021-05-11 | 2023-08-15 | Ford Global Technologies, Llc | Enabling operator controls for machine operation |
CN114338943B (en) * | 2021-11-19 | 2023-03-21 | 中国科学院长春光学精密机械与物理研究所 | Encryption and ECC (error correction code) checking method and system for on-orbit image of space camera |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030084020A1 (en) * | 2000-12-22 | 2003-05-01 | Li Shu | Distributed fault tolerant and secure storage |
US20040049700A1 (en) * | 2002-09-11 | 2004-03-11 | Fuji Xerox Co., Ltd. | Distributive storage controller and method |
US20060034453A1 (en) * | 2004-08-13 | 2006-02-16 | Yen-Fu Liu | System and method for secure encryption |
US7636724B2 (en) | 2001-08-31 | 2009-12-22 | Peerify Technologies LLC | Data storage system and method by shredding and deshredding |
Family Cites Families (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4092732A (en) * | 1977-05-31 | 1978-05-30 | International Business Machines Corporation | System for recovering data stored in failed memory unit |
US4841150A (en) * | 1987-12-28 | 1989-06-20 | The United States Of America As Represented By The Secretary Of The Air Force | Reflection technique for thermal mapping of semiconductors |
US5485474A (en) * | 1988-02-25 | 1996-01-16 | The President And Fellows Of Harvard College | Scheme for information dispersal and reconstruction |
US5454101A (en) * | 1992-09-15 | 1995-09-26 | Universal Firmware Industries, Ltd. | Data storage system with set lists which contain elements associated with parents for defining a logical hierarchy and general record pointers identifying specific data sets |
US5987622A (en) * | 1993-12-10 | 1999-11-16 | Tm Patents, Lp | Parallel computer system including parallel storage subsystem including facility for correction of data in the event of failure of a storage device in parallel storage subsystem |
US5960344A (en) * | 1993-12-20 | 1999-09-28 | Norand Corporation | Local area network having multiple channel wireless access |
US6175571B1 (en) * | 1994-07-22 | 2001-01-16 | Network Peripherals, Inc. | Distributed memory switching hub |
US5892900A (en) * | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US7124302B2 (en) * | 1995-02-13 | 2006-10-17 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5848230A (en) * | 1995-05-25 | 1998-12-08 | Tandem Computers Incorporated | Continuously available computer memory systems |
US6418324B1 (en) * | 1995-06-01 | 2002-07-09 | Padcom, Incorporated | Apparatus and method for transparent wireless communication between a remote device and host system |
US7734061B2 (en) * | 1995-06-07 | 2010-06-08 | Automotive Technologies International, Inc. | Optical occupant sensing techniques |
US5774643A (en) * | 1995-10-13 | 1998-06-30 | Digital Equipment Corporation | Enhanced raid write hole protection and recovery |
US5809285A (en) * | 1995-12-21 | 1998-09-15 | Compaq Computer Corporation | Computer system having a virtual drive array controller |
US6012159A (en) * | 1996-01-17 | 2000-01-04 | Kencast, Inc. | Method and system for error-free data transfer |
US5802364A (en) * | 1996-04-15 | 1998-09-01 | Sun Microsystems, Inc. | Metadevice driver rename/exchange technique for a computer system incorporating a plurality of independent device drivers |
US5890156A (en) * | 1996-05-02 | 1999-03-30 | Alcatel Usa, Inc. | Distributed redundant database |
US6058454A (en) * | 1997-06-09 | 2000-05-02 | International Business Machines Corporation | Method and system for automatically configuring redundant arrays of disk memory devices |
US6088330A (en) * | 1997-09-09 | 2000-07-11 | Bruck; Joshua | Reliable array of distributed computing nodes |
US5991414A (en) * | 1997-09-12 | 1999-11-23 | International Business Machines Corporation | Method and apparatus for the secure distributed storage and retrieval of information |
US6272658B1 (en) * | 1997-10-27 | 2001-08-07 | Kencast, Inc. | Method and system for reliable broadcasting of data files and streams |
JPH11161505A (en) * | 1997-12-01 | 1999-06-18 | Matsushita Electric Ind Co Ltd | Media send-out device |
JPH11167443A (en) * | 1997-12-02 | 1999-06-22 | Casio Comput Co Ltd | Interface device |
US6374336B1 (en) * | 1997-12-24 | 2002-04-16 | Avid Technology, Inc. | Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner |
US6415373B1 (en) * | 1997-12-24 | 2002-07-02 | Avid Technology, Inc. | Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner |
CA2341014A1 (en) * | 1998-08-19 | 2000-03-02 | Alexander Roger Deas | A system and method for defining transforms of memory device addresses |
US6356949B1 (en) * | 1999-01-29 | 2002-03-12 | Intermec Ip Corp. | Automatic data collection device that receives data output instruction from data consumer |
US7966078B2 (en) * | 1999-02-01 | 2011-06-21 | Steven Hoffberg | Network media appliance system and method |
US6609223B1 (en) * | 1999-04-06 | 2003-08-19 | Kencast, Inc. | Method for packet-level fec encoding, in which on a source packet-by-source packet basis, the error correction contributions of a source packet to a plurality of wildcard packets are computed, and the source packet is transmitted thereafter |
US6571282B1 (en) * | 1999-08-31 | 2003-05-27 | Accenture Llp | Block-based communication in a communication services patterns environment |
US6826711B2 (en) * | 2000-02-18 | 2004-11-30 | Avamar Technologies, Inc. | System and method for data protection with multidimensional parity |
CA2304433A1 (en) * | 2000-04-05 | 2001-10-05 | Cloakware Corporation | General purpose access recovery scheme |
US6718361B1 (en) * | 2000-04-07 | 2004-04-06 | Network Appliance Inc. | Method and apparatus for reliable and scalable distribution of data files in distributed networks |
US6973130B1 (en) * | 2000-04-25 | 2005-12-06 | Wee Susie J | Compressed video signal including information for independently coded regions |
US7225191B1 (en) * | 2000-06-27 | 2007-05-29 | Emc Corporation | Method and apparatus for verifying storage access requests in a computer storage system with multiple storage elements |
EP1364510B1 (en) * | 2000-10-26 | 2007-12-12 | Prismedia Networks, Inc. | Method and system for managing distributed content and related metadata |
US6567387B1 (en) * | 2000-11-07 | 2003-05-20 | Intel Corporation | System and method for data transmission from multiple wireless base transceiver stations to a subscriber unit |
US7146644B2 (en) * | 2000-11-13 | 2006-12-05 | Digital Doors, Inc. | Data security system and method responsive to electronic attacks |
US7140044B2 (en) * | 2000-11-13 | 2006-11-21 | Digital Doors, Inc. | Data security system and method for separation of user communities |
US8176563B2 (en) * | 2000-11-13 | 2012-05-08 | DigitalDoors, Inc. | Data security system and method with editor |
US7103915B2 (en) * | 2000-11-13 | 2006-09-05 | Digital Doors, Inc. | Data security system and method |
GB2369206B (en) * | 2000-11-18 | 2004-11-03 | Ibm | Method for rebuilding meta-data in a data storage system and a data storage system |
US6785783B2 (en) * | 2000-11-30 | 2004-08-31 | International Business Machines Corporation | NUMA system with redundant main memory architecture |
US7080101B1 (en) * | 2000-12-01 | 2006-07-18 | Ncr Corp. | Method and apparatus for partitioning data for storage in a database |
WO2002065275A1 (en) * | 2001-01-11 | 2002-08-22 | Yottayotta, Inc. | Storage virtualization system and methods |
US20020174295A1 (en) * | 2001-01-29 | 2002-11-21 | Ulrich Thomas R. | Enhanced file system failure tolerance |
US20030037261A1 (en) * | 2001-03-26 | 2003-02-20 | Ilumin Corporation | Secured content delivery system and method |
US6879596B1 (en) * | 2001-04-11 | 2005-04-12 | Applied Micro Circuits Corporation | System and method for systolic array sorting of information segments |
US7024609B2 (en) * | 2001-04-20 | 2006-04-04 | Kencast, Inc. | System for protecting the transmission of live data streams, and upon reception, for reconstructing the live data streams and recording them into files |
GB2377049A (en) * | 2001-06-30 | 2002-12-31 | Hewlett Packard Co | Billing for utilisation of a data storage array |
US6944785B2 (en) * | 2001-07-23 | 2005-09-13 | Network Appliance, Inc. | High-availability cluster virtual server system |
US7685126B2 (en) * | 2001-08-03 | 2010-03-23 | Isilon Systems, Inc. | System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system |
US7024451B2 (en) * | 2001-11-05 | 2006-04-04 | Hewlett-Packard Development Company, L.P. | System and method for maintaining consistent independent server-side state among collaborating servers |
US7003688B1 (en) * | 2001-11-15 | 2006-02-21 | Xiotech Corporation | System and method for a reserved memory area shared by all redundant storage controllers |
US7171493B2 (en) * | 2001-12-19 | 2007-01-30 | The Charles Stark Draper Laboratory | Camouflage of network traffic to resist attack |
US20030191856A1 (en) * | 2002-04-08 | 2003-10-09 | Paul Lewis | Wireless networking with dynamic load sharing and balancing |
EP1547252A4 (en) * | 2002-07-29 | 2011-04-20 | Robert Halford | Multi-dimensional data protection and mirroring method for micro level data |
US7051155B2 (en) * | 2002-08-05 | 2006-05-23 | Sun Microsystems, Inc. | Method and system for striping data to accommodate integrity metadata |
US20040122917A1 (en) * | 2002-12-18 | 2004-06-24 | Menon Jaishankar Moothedath | Distributed storage system for data-sharing among client computers running defferent operating system types |
US7251832B2 (en) * | 2003-03-13 | 2007-07-31 | Drm Technologies, Llc | Secure streaming container |
US7185144B2 (en) * | 2003-11-24 | 2007-02-27 | Network Appliance, Inc. | Semi-static distribution technique |
GB0308264D0 (en) * | 2003-04-10 | 2003-05-14 | Ibm | Recovery from failures within data processing systems |
GB0308262D0 (en) * | 2003-04-10 | 2003-05-14 | Ibm | Recovery from failures within data processing systems |
US7415115B2 (en) * | 2003-05-14 | 2008-08-19 | Broadcom Corporation | Method and system for disaster recovery of data from a storage device |
JP4262014B2 (en) * | 2003-07-31 | 2009-05-13 | キヤノン株式会社 | Image photographing apparatus and image processing method |
EP1668486A2 (en) * | 2003-08-14 | 2006-06-14 | Compellent Technologies | Virtual disk drive system and method |
US20050157674A1 (en) * | 2003-10-31 | 2005-07-21 | Globespanvirata Incorporated | Time-scheduled multichannel direct link |
US7899059B2 (en) * | 2003-11-12 | 2011-03-01 | Agere Systems Inc. | Media delivery using quality of service differentiation within a media stream |
US8332483B2 (en) * | 2003-12-15 | 2012-12-11 | International Business Machines Corporation | Apparatus, system, and method for autonomic control of grid system resources |
US7206899B2 (en) * | 2003-12-29 | 2007-04-17 | Intel Corporation | Method, system, and program for managing data transfer and construction |
US7222133B1 (en) * | 2004-02-05 | 2007-05-22 | Unisys Corporation | Method for reducing database recovery time |
US7240236B2 (en) * | 2004-03-23 | 2007-07-03 | Archivas, Inc. | Fixed content distributed data storage using permutation ring encoding |
US7231578B2 (en) * | 2004-04-02 | 2007-06-12 | Hitachi Global Storage Technologies Netherlands B.V. | Techniques for detecting and correcting errors using multiple interleave erasure pointers |
US7552356B1 (en) * | 2004-06-30 | 2009-06-23 | Sun Microsystems, Inc. | Distributed data storage system for fixed content |
JP4446839B2 (en) * | 2004-08-30 | 2010-04-07 | 株式会社日立製作所 | Storage device and storage management device |
IL165190A (en) * | 2004-11-14 | 2012-05-31 | Elbit Systems Ltd | System and method for stabilizing an image |
US7680771B2 (en) * | 2004-12-20 | 2010-03-16 | International Business Machines Corporation | Apparatus, system, and method for database provisioning |
US7386758B2 (en) * | 2005-01-13 | 2008-06-10 | Hitachi, Ltd. | Method and apparatus for reconstructing data in object-based storage arrays |
AU2006223287C1 (en) * | 2005-03-10 | 2010-10-21 | Qualcomm Incorporated | A decoder architecture for optimized error management in streaming multimedia |
US7672930B2 (en) * | 2005-04-05 | 2010-03-02 | Wal-Mart Stores, Inc. | System and methods for facilitating a linear grid database with data organization by dimension |
US7546427B2 (en) * | 2005-09-30 | 2009-06-09 | Cleversafe, Inc. | System for rebuilding dispersed data |
US7953937B2 (en) * | 2005-09-30 | 2011-05-31 | Cleversafe, Inc. | Systems, methods, and apparatus for subdividing data for storage in a dispersed data storage grid |
US7574570B2 (en) * | 2005-09-30 | 2009-08-11 | Cleversafe Inc | Billing system for information dispersal system |
US8171101B2 (en) * | 2005-09-30 | 2012-05-01 | Cleversafe, Inc. | Smart access to a dispersed data storage network |
US7904475B2 (en) * | 2007-10-09 | 2011-03-08 | Cleversafe, Inc. | Virtualized data storage vaults on a dispersed data storage network |
US7574579B2 (en) * | 2005-09-30 | 2009-08-11 | Cleversafe, Inc. | Metadata management system for an information dispersed storage system |
US8285878B2 (en) * | 2007-10-09 | 2012-10-09 | Cleversafe, Inc. | Block based access to a dispersed data storage network |
EP1969857B1 (en) * | 2006-01-05 | 2012-03-28 | Telefonaktiebolaget LM Ericsson (publ) | Media container file management |
US20070214285A1 (en) * | 2006-03-08 | 2007-09-13 | Omneon Video Networks | Gateway server |
US7551486B2 (en) * | 2006-05-15 | 2009-06-23 | Apple Inc. | Iterative memory cell charging based on reference cell value |
US7844215B2 (en) * | 2006-08-08 | 2010-11-30 | Accenture Global Services Gmbh | Mobile audio content delivery system |
US7697053B2 (en) * | 2006-11-02 | 2010-04-13 | Eastman Kodak Company | Integrated display having multiple capture devices |
US8031875B1 (en) * | 2007-08-09 | 2011-10-04 | Emc Corporation | Key distribution in unidirectional channels with applications to RFID |
US8364892B2 (en) * | 2008-01-11 | 2013-01-29 | Verivue, Inc. | Asynchronous and distributed storage of data |
JP4958807B2 (en) * | 2008-01-24 | 2012-06-20 | 株式会社キーエンス | Image processing device |
JP2009284309A (en) * | 2008-05-23 | 2009-12-03 | Casio Comput Co Ltd | Imaging device, display control program, and display control method |
-
2010
- 2010-06-13 US US12/814,474 patent/US9900150B2/en active Active
- 2010-06-13 US US12/814,467 patent/US8351600B2/en active Active
- 2010-06-15 US US12/816,126 patent/US9692593B2/en not_active Expired - Fee Related
- 2010-06-17 US US12/818,137 patent/US8468137B2/en not_active Expired - Fee Related
-
2013
- 2013-01-08 US US13/736,848 patent/US9009491B2/en not_active Expired - Fee Related
-
2014
- 2014-05-30 US US14/292,772 patent/US9088407B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030084020A1 (en) * | 2000-12-22 | 2003-05-01 | Li Shu | Distributed fault tolerant and secure storage |
US7636724B2 (en) | 2001-08-31 | 2009-12-22 | Peerify Technologies LLC | Data storage system and method by shredding and deshredding |
US20040049700A1 (en) * | 2002-09-11 | 2004-03-11 | Fuji Xerox Co., Ltd. | Distributive storage controller and method |
US20060034453A1 (en) * | 2004-08-13 | 2006-02-16 | Yen-Fu Liu | System and method for secure encryption |
Non-Patent Citations (1)
Title |
---|
Kubiatowicz, et al.; OceanStore: An Architecture for Global-Scale Persistent Storage; Proceedings of the Ninth International Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS 2000); Nov. 2000; pp. 1-12. |
Cited By (49)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11716371B2 (en) | 2011-08-31 | 2023-08-01 | Divx, Llc | Systems and methods for automatically generating top level index files |
US20200106820A1 (en) * | 2011-08-31 | 2020-04-02 | Divx, Llc | Systems and Methods for Automatically Generating Top Level Index Files |
US11115450B2 (en) * | 2011-08-31 | 2021-09-07 | Divx, Llc | Systems, methods, and media for playing back protected video content by using top level index file |
US11349892B2 (en) | 2015-01-06 | 2022-05-31 | Divx, Llc | Systems and methods for encoding and sharing content between devices |
US11711410B2 (en) | 2015-01-06 | 2023-07-25 | Divx, Llc | Systems and methods for encoding and sharing content between devices |
US10270475B1 (en) | 2015-06-16 | 2019-04-23 | Amazon Technologies, Inc. | Layered redundancy coding for encoded parity data |
US9998150B1 (en) | 2015-06-16 | 2018-06-12 | Amazon Technologies, Inc. | Layered data redundancy coding techniques for layer-local data recovery |
US10977128B1 (en) | 2015-06-16 | 2021-04-13 | Amazon Technologies, Inc. | Adaptive data loss mitigation for redundancy coding systems |
US10298259B1 (en) | 2015-06-16 | 2019-05-21 | Amazon Technologies, Inc. | Multi-layered data redundancy coding techniques |
US10270476B1 (en) | 2015-06-16 | 2019-04-23 | Amazon Technologies, Inc. | Failure mode-sensitive layered redundancy coding techniques |
US10108819B1 (en) | 2015-07-01 | 2018-10-23 | Amazon Technologies, Inc. | Cross-datacenter extension of grid encoded data storage systems |
US10089176B1 (en) | 2015-07-01 | 2018-10-02 | Amazon Technologies, Inc. | Incremental updates of grid encoded data storage systems |
US10394762B1 (en) | 2015-07-01 | 2019-08-27 | Amazon Technologies, Inc. | Determining data redundancy in grid encoded data storage systems |
US10162704B1 (en) | 2015-07-01 | 2018-12-25 | Amazon Technologies, Inc. | Grid encoded data storage systems for efficient data repair |
US9998539B1 (en) | 2015-07-01 | 2018-06-12 | Amazon Technologies, Inc. | Non-parity in grid encoded data storage systems |
US10198311B1 (en) | 2015-07-01 | 2019-02-05 | Amazon Technologies, Inc. | Cross-datacenter validation of grid encoded data storage systems |
US9959167B1 (en) * | 2015-07-01 | 2018-05-01 | Amazon Technologies, Inc. | Rebundling grid encoded data storage systems |
US9904589B1 (en) | 2015-07-01 | 2018-02-27 | Amazon Technologies, Inc. | Incremental media size extension for grid encoded data storage systems |
US9928141B1 (en) | 2015-09-21 | 2018-03-27 | Amazon Technologies, Inc. | Exploiting variable media size in grid encoded data storage systems |
US11386060B1 (en) | 2015-09-23 | 2022-07-12 | Amazon Technologies, Inc. | Techniques for verifiably processing data in distributed computing systems |
US9940474B1 (en) | 2015-09-29 | 2018-04-10 | Amazon Technologies, Inc. | Techniques and systems for data segregation in data storage systems |
US10394789B1 (en) | 2015-12-07 | 2019-08-27 | Amazon Technologies, Inc. | Techniques and systems for scalable request handling in data processing systems |
US10642813B1 (en) | 2015-12-14 | 2020-05-05 | Amazon Technologies, Inc. | Techniques and systems for storage and processing of operational data |
US9785495B1 (en) | 2015-12-14 | 2017-10-10 | Amazon Technologies, Inc. | Techniques and systems for detecting anomalous operational data |
US11537587B2 (en) | 2015-12-14 | 2022-12-27 | Amazon Technologies, Inc. | Techniques and systems for storage and processing of operational data |
US10248793B1 (en) | 2015-12-16 | 2019-04-02 | Amazon Technologies, Inc. | Techniques and systems for durable encryption and deletion in data storage systems |
US10127105B1 (en) | 2015-12-17 | 2018-11-13 | Amazon Technologies, Inc. | Techniques for extending grids in data storage systems |
US10180912B1 (en) | 2015-12-17 | 2019-01-15 | Amazon Technologies, Inc. | Techniques and systems for data segregation in redundancy coded data storage systems |
US10235402B1 (en) | 2015-12-17 | 2019-03-19 | Amazon Technologies, Inc. | Techniques for combining grid-encoded data storage systems |
US10102065B1 (en) | 2015-12-17 | 2018-10-16 | Amazon Technologies, Inc. | Localized failure mode decorrelation in redundancy encoded data storage systems |
US10324790B1 (en) | 2015-12-17 | 2019-06-18 | Amazon Technologies, Inc. | Flexible data storage device mapping for data storage systems |
US10592336B1 (en) | 2016-03-24 | 2020-03-17 | Amazon Technologies, Inc. | Layered indexing for asynchronous retrieval of redundancy coded data |
US11113161B2 (en) | 2016-03-28 | 2021-09-07 | Amazon Technologies, Inc. | Local storage clustering for redundancy coded data storage system |
US10366062B1 (en) | 2016-03-28 | 2019-07-30 | Amazon Technologies, Inc. | Cycled clustering for redundancy coded data storage systems |
US10061668B1 (en) | 2016-03-28 | 2018-08-28 | Amazon Technologies, Inc. | Local storage clustering for redundancy coded data storage system |
US10678664B1 (en) | 2016-03-28 | 2020-06-09 | Amazon Technologies, Inc. | Hybridized storage operation for redundancy coded data storage systems |
US11137980B1 (en) | 2016-09-27 | 2021-10-05 | Amazon Technologies, Inc. | Monotonic time-based data storage |
US10810157B1 (en) | 2016-09-28 | 2020-10-20 | Amazon Technologies, Inc. | Command aggregation for data storage operations |
US10437790B1 (en) | 2016-09-28 | 2019-10-08 | Amazon Technologies, Inc. | Contextual optimization for data storage systems |
US10657097B1 (en) | 2016-09-28 | 2020-05-19 | Amazon Technologies, Inc. | Data payload aggregation for data storage systems |
US11204895B1 (en) | 2016-09-28 | 2021-12-21 | Amazon Technologies, Inc. | Data payload clustering for data storage systems |
US11281624B1 (en) | 2016-09-28 | 2022-03-22 | Amazon Technologies, Inc. | Client-based batching of data payload |
US10496327B1 (en) | 2016-09-28 | 2019-12-03 | Amazon Technologies, Inc. | Command parallelization for data storage systems |
US10614239B2 (en) | 2016-09-30 | 2020-04-07 | Amazon Technologies, Inc. | Immutable cryptographically secured ledger-backed databases |
US10296764B1 (en) | 2016-11-18 | 2019-05-21 | Amazon Technologies, Inc. | Verifiable cryptographically secured ledgers for human resource systems |
US11269888B1 (en) | 2016-11-28 | 2022-03-08 | Amazon Technologies, Inc. | Archival data storage for structured data |
CN106612328B (en) * | 2016-12-20 | 2021-07-23 | 杭州联众医疗科技股份有限公司 | Mobile film reading system |
CN106612328A (en) * | 2016-12-20 | 2017-05-03 | 杭州联众医疗科技股份有限公司 | Mobile radiograph reading system |
US10360391B2 (en) | 2017-04-03 | 2019-07-23 | International Business Machines Corporation | Verifiable keyed all-or-nothing transform |
Also Published As
Publication number | Publication date |
---|---|
US20140270180A1 (en) | 2014-09-18 |
US9900150B2 (en) | 2018-02-20 |
US8468137B2 (en) | 2013-06-18 |
US20130124875A1 (en) | 2013-05-16 |
US9692593B2 (en) | 2017-06-27 |
US9088407B2 (en) | 2015-07-21 |
US20110102546A1 (en) | 2011-05-05 |
US20110106769A1 (en) | 2011-05-05 |
US20110106909A1 (en) | 2011-05-05 |
US20110107112A1 (en) | 2011-05-05 |
US8351600B2 (en) | 2013-01-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9819484B2 (en) | Distributed storage network and method for storing and retrieving encryption keys | |
US12079380B2 (en) | Recovering data from encoded data slices interspersed with auxiliary data | |
US9088407B2 (en) | Distributed storage network and method for storing and retrieving encryption keys | |
US11301592B2 (en) | Distributed storage with data obfuscation and method for use therewith | |
US9842063B2 (en) | Encrypting data for storage in a dispersed storage network | |
US20190081781A1 (en) | Storing access information in a dispersed storage network | |
US9128870B2 (en) | Sending a zero information gain formatted encoded data slice | |
US9679153B2 (en) | Data deduplication in a dispersed storage system | |
US8522022B2 (en) | Distributed storage network employing multiple encoding layers in data routing | |
US9454431B2 (en) | Memory selection for slice storage in a dispersed storage network | |
US20120137095A1 (en) | Partitioning data for storage in a dispersed storage network | |
US20120054500A1 (en) | Secure rebuilding of an encoded data slice in a dispersed storage network | |
US20110289565A1 (en) | Retrieving access information in a dispersed storage network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: CLEVERSAFE, INC., ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESCH, JASON K.;REEL/FRAME:038276/0018 Effective date: 20100609 |
|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CLEVERSAFE, INC.;REEL/FRAME:038687/0596 Effective date: 20160405 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.) |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551) Year of fee payment: 4 |
|
AS | Assignment |
Owner name: PURE STORAGE, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:049556/0012 Effective date: 20190611 |
|
AS | Assignment |
Owner name: PURE STORAGE, INC., CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE 9992063 AND 10334045 LISTED IN ERROR PREVIOUSLY RECORDED ON REEL 049556 FRAME 0012. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNOR HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:052205/0705 Effective date: 20190611 |
|
AS | Assignment |
Owner name: BARCLAYS BANK PLC AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:PURE STORAGE, INC.;REEL/FRAME:053867/0581 Effective date: 20200824 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230414 |