U.S. patent application number 15/336300 was filed with the patent office on 2017-07-06 for determining byte-hours usage of a vault or by users.
The applicant listed for this patent is International Business Machines Corporation. Invention is credited to Bart R. Cilfone, Adam M. Gray, Scott M. Horan, Wesley B. Leggette, Jason K. Resch, Shikha Shree, Ilya Volvovski.
Application Number | 20170192698 15/336300 |
Document ID | / |
Family ID | 59226383 |
Filed Date | 2017-07-06 |
United States Patent
Application |
20170192698 |
Kind Code |
A1 |
Cilfone; Bart R. ; et
al. |
July 6, 2017 |
DETERMINING BYTE-HOURS USAGE OF A VAULT OR BY USERS
Abstract
Systems and methods for determining utilization levels of
storage within a dispersed storage network (DSN). The methods
include obtaining transaction records, updating a cumulative data
storage byte-hour count for storage of corresponding bytes of
encoded data slices in the storage units of the DSN, and issuing
byte-hour usage information based on the updated cumulative data
storage byte-hour counts. Each transaction record can include one
or more of an operation count, an operation type (e.g., read,
write, delete), number of slice bytes transferred, number of slice
bytes deleted, a timestamp, a user identifier, and a vault
identifier. The updating can include one or more of identifying the
one or more affiliated entities, determining a byte-hour adjustment
(i.e., up or down) based on a transaction record, and updating a
byte-hour record for affiliated entities based on the byte-hour
adjustment.
Inventors: |
Cilfone; Bart R.; (Marina
del Rey, CA) ; Gray; Adam M.; (Chicago, IL) ;
Horan; Scott M.; (Clarendon Hills, IL) ; Leggette;
Wesley B.; (Chicago, IL) ; Resch; Jason K.;
(Chicago, IL) ; Shree; Shikha; (Chicago, IL)
; Volvovski; Ilya; (Chicago, IL) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
International Business Machines Corporation |
Armonk |
NY |
US |
|
|
Family ID: |
59226383 |
Appl. No.: |
15/336300 |
Filed: |
October 27, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
62272848 |
Dec 30, 2015 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 11/1076 20130101;
G06F 3/0604 20130101; G06F 3/0616 20130101; G06F 2212/263 20130101;
H04L 43/16 20130101; G06F 3/0659 20130101; H04L 43/0888 20130101;
G06F 3/064 20130101; G06F 3/0647 20130101; H03M 13/3761 20130101;
G06F 3/0653 20130101; G06F 11/1092 20130101; G06F 16/2246 20190101;
G06F 3/0665 20130101; H04L 67/1097 20130101; G06F 3/0631 20130101;
G06F 12/1408 20130101; H04L 43/0852 20130101; G06F 3/0619 20130101;
G06F 16/182 20190101; H04L 43/0876 20130101; G06F 3/067 20130101;
H03M 13/1515 20130101; G06F 3/0652 20130101; G06F 12/0888 20130101;
G06F 12/0684 20130101; G06F 3/0661 20130101; G06F 2212/154
20130101; G06F 3/0608 20130101; G06F 3/0623 20130101; G06F 3/0644
20130101; G06F 3/0611 20130101; G06F 12/0813 20130101 |
International
Class: |
G06F 3/06 20060101
G06F003/06; H04L 12/26 20060101 H04L012/26; H04L 29/08 20060101
H04L029/08 |
Claims
1. A method of determining utilization levels of storage in a
dispersed storage network, the dispersed storage network including
a plurality of dispersed storage units, wherein the plurality of
dispersed storage units storing encoded data slices of a set of
encoded data slices, the method comprising: obtaining a transaction
record associated with one or more affiliated entities accessing
one or more of the encoded data slices of the set of encoded data
slices; updating a cumulative data storage byte-hour count for the
one or more affiliated entities based on the transaction record;
and issuing byte-hour usage information for the one or more
affiliated entities based on the cumulative data storage byte-hour
count.
2. The method of claim 1, wherein the transaction record associated
with one or more affiliated entities accessing one or more of the
encoded data slices of the set of encoded data slices comprises an
operation count, an operation type, a number of slice bytes
transferred, a number of slice bytes deleted, a timestamp, a user
identifier and a vault identifier.
3. The method of claim 2, wherein the operation type comprises
read, write and delete.
4. The method of claim 1, wherein the step of obtaining a
transaction record associated with one or more affiliated entities
accessing one or more of the encoded data slices of the set of
encoded data slices comprises one or more of receiving the
transaction record, issuing a request for the transaction record
and retrieving the transaction record from at least one of the
plurality of dispersed storage units.
5. The method of claim 1, wherein the one or more affiliated
entities comprises one or more of one or more users, a group of
users, and a vault.
6. The method of claim 1, wherein the step of updating a cumulative
data storage byte-hour count for the one or more affiliated
entities based on the transaction record comprises identifying the
one or more affiliated entities, determining a byte-hour adjustment
based on the transaction record, and updating a byte-hour record
for the one or more affiliated entities based on the byte-hour
adjustment.
7. The method of claim 1, wherein the step of issuing byte-hour
usage information for the one or more affiliated entities based on
the cumulative data storage byte-hour count comprises identifying
receiving entities.
8. The method of claim 7, wherein the step of identifying receiving
entities comprises interpreting a request, utilizing a
predetermination and selecting all entities.
9. A dispersed storage network managing unit for use in a dispersed
storage network, the dispersed storage network including a
plurality of dispersed storage units, wherein the plurality of
dispersed storage units storing encoded data slices of a set of
encoded data slices, the dispersed storage network managing unit
comprising: a communications interface; a memory; a computer
processor; where the memory includes instructions for causing the
computer processor to: obtain a transaction record associated with
one or more affiliated entities accessing one or more of the
encoded data slices of the set of encoded data slices; update a
cumulative data storage byte-hour count for the one or more
affiliated entities based on the transaction record; and issue
byte-hour usage information for the one or more affiliated entities
based on the cumulative data storage byte-hour count.
10. The dispersed storage network managing unit of claim 9, wherein
the transaction record associated with one or more affiliated
entities accessing one or more of the encoded data slices of the
set of encoded data slices comprises an operation count, an
operation type, a number of slice bytes transferred, a number of
slice bytes deleted, a timestamp, a user identifier and a vault
identifier.
11. The dispersed storage network managing unit of claim 10,
wherein the operation type comprises read, write and delete.
12. The dispersed storage network managing unit of claim 9, wherein
the memory further includes instructions for causing the computer
processor to receive the transaction record, issue a request for
the transaction record and retrieve the transaction record from at
least one of the plurality of dispersed storage units.
13. The dispersed storage network managing unit of claim 9, wherein
the one or more affiliated entities comprises one or more of one or
more users, a group of users and a vault.
14. The dispersed storage network managing unit of claim 9, wherein
the memory further includes instructions for causing the computer
processor to identify the one or more affiliated entities,
determine a byte-hour adjustment based on the transaction record,
and update a byte-hour record for the one or more affiliated
entities based on the byte-hour adjustment.
15. The dispersed storage network managing unit of claim 9, wherein
the memory further includes instructions for causing the computer
processor to identify receiving entities.
16. The dispersed storage network managing unit of claim 15,
wherein the memory further includes instructions for causing the
computer processor to interpret a request, utilize a
predetermination and select all entities.
17. A dispersed storage network comprising: a plurality of
dispersed storage units, wherein the plurality of dispersed storage
units storing encoded data slices of a set of encoded data slices;
a dispersed storage processing unit; at least one affiliated
entity; and a dispersed storage network management unit including:
a communications interface; a memory; a computer processor; where
the memory includes instructions for causing the computer processor
to: obtain from the dispersed storage processing unit a transaction
record associated with one or more of the at least one affiliated
entity accessing one or more of the encoded data slices of the set
of encoded data slices; update a cumulative data storage byte-hour
count for the one or more affiliated entities based on the
transaction record; and issue byte-hour usage information to the at
least one affiliated entity based on the cumulative data storage
byte-hour count.
18. The dispersed storage network of claim 17, wherein the
transaction record associated with one or more affiliated entities
accessing one or more of the encoded data slices of the set of
encoded data slices comprises an operation count, an operation
type, a number of slice bytes transferred, a number of slice bytes
deleted, a timestamp, a user identifier and a vault identifier.
19. The dispersed storage network of claim 18, wherein the
operation type comprises read, write and delete.
20. The dispersed storage network of claim 17, wherein the one or
more affiliated entities comprises one or more of one or more
users, a group of users and a vault.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present U.S. Utility patent application claims priority
pursuant to 35 U.S.C. .sctn.119(e) to U.S. Provisional Application
No. 62/272,848 filed 30 Dec. 2015, entitled "Optimizing Utilization
of Storage Memory in a Dispersed Storage Network," which is hereby
incorporated herein by reference in its entirety and made part of
the present U.S. Utility patent application for all purposes.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
[0002] Not Applicable.
INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT
DISC
[0003] Not Applicable.
BACKGROUND OF THE INVENTION
[0004] Technical Field of the Invention
[0005] This invention relates generally to computer networks, and
more particularly to dispersed or cloud storage.
[0006] Description of Related Art
[0007] Computing devices are known to communicate data, process
data, and/or store data. Such computing devices range from wireless
smart phones, laptops, tablets, personal computers (PC), work
stations, and video game devices, to data centers that support
millions of web searches, stock trades, or on-line purchases every
day. In general, a computing device includes a central processing
unit (CPU), a memory system, user input/output interfaces,
peripheral device interfaces, and an interconnecting bus
structure.
[0008] As is further known, a computer may effectively extend its
CPU by using "cloud computing" to perform one or more computing
functions (e.g., a service, an application, an algorithm, an
arithmetic logic function, etc.) on behalf of the computer.
Further, for large services, applications, and/or functions, cloud
computing may be performed by multiple cloud computing resources in
a distributed manner to improve the response time for completion of
the service, application, and/or function. For example, Hadoop is
an open source software framework that supports distributed
applications enabling application execution by thousands of
computers.
[0009] In addition to cloud computing, a computer may use "cloud
storage" as part of its memory system. As is known, cloud storage
enables a user, via its computer, to store files, applications,
etc. on a remote or Internet storage system. The remote or Internet
storage system may include a RAID (redundant array of independent
disks) system and/or a dispersed storage system that uses an error
correction scheme to encode data for storage.
[0010] In a RAID system, a RAID controller adds parity data to the
original data before storing it across an array of disks. The
parity data is calculated from the original data such that the
failure of a single disk typically will not result in the loss of
the original data. While RAID systems can address certain memory
device failures, these systems may suffer from effectiveness,
efficiency and security issues. For instance, as more disks are
added to the array, the probability of a disk failure rises, which
may increase maintenance costs. When a disk fails, for example, it
needs to be manually replaced before another disk(s) fails and the
data stored in the RAID system is lost. To reduce the risk of data
loss, data on a RAID device is often copied to one or more other
RAID devices. While this may reduce the possibility of data loss,
it also raises security issues since multiple copies of data may be
available, thereby increasing the chances of unauthorized access.
In addition, co-location of some RAID devices may result in a risk
of a complete data loss in the event of a natural disaster, fire,
power surge/outage, etc.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)
[0011] FIG. 1 is a schematic block diagram of an embodiment of a
dispersed, or distributed, storage network (DSN) in accordance with
the present disclosure;
[0012] FIG. 2 is a schematic block diagram of an embodiment of a
computing core in accordance with the present disclosure;
[0013] FIG. 3 is a schematic block diagram of an example of
dispersed storage error encoding of data in accordance with the
present disclosure;
[0014] FIG. 4 is a schematic block diagram of a generic example of
an error encoding function in accordance with the present
disclosure;
[0015] FIG. 5 is a schematic block diagram of a specific example of
an error encoding function in accordance with the present
disclosure;
[0016] FIG. 6 is a schematic block diagram of an example of slice
naming information for an encoded data slice (EDS) in accordance
with the present disclosure;
[0017] FIG. 7 is a schematic block diagram of an example of
dispersed storage error decoding of data in accordance with the
present disclosure;
[0018] FIG. 8 is a schematic block diagram of a generic example of
an error decoding function in accordance with the present
disclosure;
[0019] FIG. 9 is a schematic block diagram of an example of a
dispersed storage network in accordance with the present
disclosure;
[0020] FIG. 10A is a schematic block diagram of an embodiment of a
decentralized agreement module in accordance with the present
invention;
[0021] FIG. 10B is a flowchart illustrating an example of selecting
the resource in accordance with the present invention;
[0022] FIG. 10C is a schematic block diagram of an embodiment of a
dispersed storage network (DSN) in accordance with the present
invention;
[0023] FIG. 10D is a flowchart illustrating an example of accessing
a dispersed storage network (DSN) memory in accordance with the
present invention;
[0024] FIG. 11A is a schematic block diagram of another embodiment
of a dispersed storage network (DSN) in accordance with the present
invention; and
[0025] FIG. 11B is a flowchart illustrating an example of
determining byte-hour usage in a dispersed storage network
(DSN).
DETAILED DESCRIPTION OF THE INVENTION
[0026] FIG. 1 is a schematic block diagram of an embodiment of a
dispersed, or distributed, storage network (DSN) 10 that includes a
plurality of dispersed storage (DS) computing devices or processing
units 12-16, a DS managing unit 18, a DS integrity processing unit
20, and a DSN memory 22. The components of the DSN 10 are coupled
to a network 24, which may include one or more wireless and/or wire
lined communication systems; one or more non-public intranet
systems and/or public internet systems; and/or one or more local
area networks (LAN) and/or wide area networks (WAN).
[0027] The DSN memory 22 includes a plurality of dispersed storage
units 36 (DS units) that may be located at geographically different
sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common
site, or a combination thereof. For example, if the DSN memory 22
includes eight dispersed storage units 36, each storage unit is
located at a different site. As another example, if the DSN memory
22 includes eight storage units 36, all eight storage units are
located at the same site. As yet another example, if the DSN memory
22 includes eight storage units 36, a first pair of storage units
are at a first common site, a second pair of storage units are at a
second common site, a third pair of storage units are at a third
common site, and a fourth pair of storage units are at a fourth
common site. Note that a DSN memory 22 may include more or less
than eight storage units 36.
[0028] DS computing devices 12-16, the managing unit 18, and the
integrity processing unit 20 include a computing core 26, and
network or communications interfaces 30-33 which can be part of or
external to computing core 26. DS computing devices 12-16 may each
be a portable computing device and/or a fixed computing device. A
portable computing device may be a social networking device, a
gaming device, a cell phone, a smart phone, a digital assistant, a
digital music player, a digital video player, a laptop computer, a
handheld computer, a tablet, a video game controller, and/or any
other portable device that includes a computing core. A fixed
computing device may be a computer (PC), a computer server, a cable
set-top box, a satellite receiver, a television set, a printer, a
fax machine, home entertainment equipment, a video game console,
and/or any type of home or office computing equipment. Note that
each of the managing unit 18 and the integrity processing unit 20
may be separate computing devices, may be a common computing
device, and/or may be integrated into one or more of the computing
devices 12-16 and/or into one or more of the dispersed storage
units 36.
[0029] Each interface 30, 32, and 33 includes software and/or
hardware to support one or more communication links via the network
24 indirectly and/or directly. For example, interface 30 supports a
communication link (e.g., wired, wireless, direct, via a LAN, via
the network 24, etc.) between computing devices 14 and 16. As
another example, interface 32 supports communication links (e.g., a
wired connection, a wireless connection, a LAN connection, and/or
any other type of connection to/from the network 24) between
computing devices 12 and 16 and the DSN memory 22. As yet another
example, interface 33 supports a communication link for each of the
managing unit 18 and the integrity processing unit 20 to the
network 24.
[0030] In general, and with respect to DS error encoded data
storage and retrieval, the DSN 10 supports three primary
operations: storage management, data storage and retrieval. More
specifically computing devices 12 and 16 include a dispersed
storage (DS) client module 34, which enables the computing device
to dispersed storage error encode and decode data (e.g., data
object 40) as subsequently described with reference to one or more
of FIGS. 3-8. In this example embodiment, computing device 16
functions as a dispersed storage processing agent for computing
device 14. In this role, computing device 16 dispersed storage
error encodes and decodes data on behalf of computing device 14.
With the use of dispersed storage error encoding and decoding, the
DSN 10 is tolerant of a significant number of storage unit failures
(the number of failures is based on parameters of the dispersed
storage error encoding function) without loss of data and without
the need for a redundant or backup copies of the data. Further, the
DSN 10 stores data for an indefinite period of time without data
loss and in a secure manner (e.g., the system is very resistant to
unauthorized attempts at accessing or hacking the data).
[0031] The second primary function (i.e., distributed data storage
and retrieval) begins and ends with a DS computing devices 12-14.
For instance, if a second type of computing device 14 has data 40
to store in the DSN memory 22, it sends the data 40 to the DS
computing device 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.).
[0032] In operation, the managing unit 18 performs DS management
services. For example, the managing unit 18 establishes distributed
data storage parameters (e.g., vault creation, distributed storage
parameters, security parameters, billing information, user profile
information, etc.) for computing devices 12-16 individually or as
part of a group of user devices. As a specific example, the
managing unit 18 coordinates creation of a vault (e.g., a virtual
memory block associated with a portion of an overall namespace of
the DSN) within the DSN memory 22 for a user device, a group of
devices, or for public access and establishes per vault dispersed
storage (DS) error encoding parameters for a vault. The managing
unit 18 facilitates storage of DS error encoding parameters for
each vault by updating registry information of the DSN 10, where
the registry information may be stored in the DSN memory 22, a
computing device 12-16, the managing unit 18, and/or the integrity
processing unit 20.
[0033] The DS error encoding parameters (e.g., or dispersed storage
error coding parameters) include data segmenting information (e.g.,
how many segments data (e.g., a file, a group of files, a data
block, etc.) is divided into), segment security information (e.g.,
per segment encryption, compression, integrity checksum, etc.),
error coding information (e.g., pillar width, decode threshold,
read threshold, write threshold, etc.), slicing information (e.g.,
the number of encoded data slices that will be created for each
data segment); and slice security information (e.g., per encoded
data slice encryption, compression, integrity checksum, etc.).
[0034] The managing unit 18 creates and stores user profile
information (e.g., an access control list (ACL)) in local memory
and/or within memory of the DSN memory 22. The user profile
information includes authentication information, permissions,
and/or the security parameters. The security parameters may include
encryption/decryption scheme, one or more encryption keys, key
generation scheme, and/or data encoding/decoding scheme.
[0035] The managing unit 18 creates billing information for a
particular user, a user group, a vault access, public vault access,
etc. For instance, the managing unit 18 tracks the number of times
a user accesses a non-public vault and/or public vaults, which can
be used to generate per-access billing information. In another
instance, the 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 per-data-amount billing information. As will be
described in more detail in conjunction with FIGS. 11A and 11B,
usage can be determined by a managing unit 18 on a byte-hour
basis.
[0036] As another example, the managing unit 18 performs network
operations, network administration, and/or network maintenance.
Network operations includes authenticating user data allocation
requests (e.g., read and/or write requests), managing creation of
vaults, establishing authentication credentials for user devices,
adding/deleting components (e.g., user devices, storage units,
and/or computing devices with a DS client module 34) to/from the
DSN 10, and/or establishing authentication credentials for the
storage units 36. Network operations can further include monitoring
read, write and/or delete communications attempts, which attempts
could be in the form of requests. Network administration includes
monitoring devices and/or units for failures, maintaining vault
information, determining device and/or unit activation status,
determining device and/or unit loading, and/or determining any
other system level operation that affects the performance level of
the DSN 10. Network maintenance includes facilitating replacing,
upgrading, repairing, and/or expanding a device and/or unit of the
DSN 10.
[0037] To support data storage integrity verification within the
DSN 10, the integrity processing unit 20 (and/or other devices in
the DSN 10 such as managing unit 18) may assess and perform
rebuilding of `bad` or missing encoded data slices. At a high
level, the integrity processing unit 20 performs rebuilding by
periodically attempting to retrieve/list encoded data slices,
and/or slice names of the encoded data slices, from the DSN memory
22. Retrieved encoded slices are assessed and checked for errors
due to data corruption, outdated versioning, etc. If a slice
includes an error, it is flagged as a `bad` or `corrupt` slice.
Encoded data slices that are not received and/or not listed may be
flagged as missing slices. Bad and/or missing slices may be
subsequently rebuilt using other retrieved encoded data slices that
are deemed to be good slices in order to produce rebuilt slices. A
multi-stage decoding process may be employed in certain
circumstances to recover data even when the number of valid encoded
data slices of a set of encoded data slices is less than a relevant
decode threshold number. The rebuilt slices may then be written to
DSN memory 22. Note that the integrity processing unit 20 may be a
separate unit as shown, included in DSN memory 22, included in the
computing device 16, managing unit 18, stored on a DS unit 36,
and/or distributed among multiple storage units 36.
[0038] 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 (TO) controller 56, a peripheral component
interconnect (PCI) interface 58, an IO interface module 60, 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. The one or more 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.
[0039] The DSN interface module 76 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.). The DSN interface
module 76 and/or the network interface module 70 may function as
one or more of the interface 30-33 of FIG. 1. Note that the IO
device interface module 62 and/or the memory interface modules
66-76 may be collectively or individually referred to as IO
ports.
[0040] FIG. 3 is a schematic block diagram of an example of
dispersed storage error encoding of data. When a computing device
12 or 16 has data to store it disperse storage error encodes the
data in accordance with a dispersed storage error encoding process
based on dispersed storage error encoding parameters. The dispersed
storage error encoding parameters include an encoding function
(e.g., information dispersal algorithm, Reed-Solomon, Cauchy
Reed-Solomon, systematic encoding, non-systematic encoding, on-line
codes, etc.), a data segmenting protocol (e.g., data segment size,
fixed, variable, etc.), and per data segment encoding values. The
per data segment encoding values include a total, or pillar width,
number (T) of encoded data slices per encoding of a data segment
(i.e., in a set of encoded data slices); a decode threshold number
(D) of encoded data slices of a set of encoded data slices that are
needed to recover the data segment; a read threshold number (R) of
encoded data slices to indicate a number of encoded data slices per
set to be read from storage for decoding of the data segment;
and/or a write threshold number (W) to indicate a number of encoded
data slices per set that must be accurately stored before the
encoded data segment is deemed to have been properly stored. The
dispersed storage error encoding parameters may further include
slicing information (e.g., the number of encoded data slices that
will be created for each data segment) and/or slice security
information (e.g., per encoded data slice encryption, compression,
integrity checksum, etc.).
[0041] In the present example, Cauchy Reed-Solomon has been
selected as the encoding function (a generic example is shown in
FIG. 4 and a specific example is shown in FIG. 5); the data
segmenting protocol is to divide the data object into fixed sized
data segments; and the per data segment encoding values include: a
pillar width of 5, a decode threshold of 3, a read threshold of 4,
and a write threshold of 4. In accordance with the data segmenting
protocol, the computing device 12 or 16 divides the data (e.g., a
file (e.g., text, video, audio, etc.), a data object, or other data
arrangement) into a plurality of fixed sized data segments (e.g., 1
through Y of a fixed size in range of Kilo-bytes to Tera-bytes or
more). The number of data segments created is dependent of the size
of the data and the data segmenting protocol.
[0042] The computing device 12 or 16 then disperse storage error
encodes a data segment using the selected encoding function (e.g.,
Cauchy Reed-Solomon) to produce a set of encoded data slices. FIG.
4 illustrates a generic Cauchy Reed-Solomon encoding function,
which includes an encoding matrix (EM), a data matrix (DM), and a
coded matrix (CM). The size of the encoding matrix (EM) is
dependent on the pillar width number (T) and the decode threshold
number (D) of selected per data segment encoding values. To produce
the data matrix (DM), the data segment is divided into a plurality
of data blocks and the data blocks are arranged into D number of
rows with Z data blocks per row. Note that Z is a function of the
number of data blocks created from the data segment and the decode
threshold number (D). The coded matrix is produced by matrix
multiplying the data matrix by the encoding matrix.
[0043] FIG. 5 illustrates a specific example of Cauchy Reed-Solomon
encoding with a pillar number (T) of five and decode threshold
number of three. In this example, a first data segment is divided
into twelve data blocks (D1-D12). The coded matrix includes five
rows of coded data blocks, where the first row of X11-X14
corresponds to a first encoded data slice (EDS 1_1), the second row
of X21-X24 corresponds to a second encoded data slice (EDS 2_1),
the third row of X31-X34 corresponds to a third encoded data slice
(EDS 3_1), the fourth row of X41-X44 corresponds to a fourth
encoded data slice (EDS 4_1), and the fifth row of X51-X54
corresponds to a fifth encoded data slice (EDS 5_1). Note that the
second number of the EDS designation corresponds to the data
segment number. In the illustrated example, the value
X11=aD1+bD5+cD9, X12=aD2+bD6+cD10, . . . X53=mD3+nD7+oD11, and
X54=mD4+nD8+oD12.
[0044] Returning to the discussion of FIG. 3, the computing device
also creates a slice name (SN) for each encoded data slice (EDS) in
the set of encoded data slices. A typical format for a slice name
80 is shown in FIG. 6. As shown, the slice name (SN) 80 includes a
pillar number of the encoded data slice (e.g., one of 1-T), a data
segment number (e.g., one of 1-Y), a vault identifier (ID), a data
object identifier (ID), and may further include revision level
information of the encoded data slices. The slice name functions as
at least part of a DSN address for the encoded data slice for
storage and retrieval from the DSN memory 22.
[0045] As a result of encoding, the computing device 12 or 16
produces a plurality of sets of encoded data slices, which are
provided with their respective slice names to the storage units for
storage. As shown, the first set of encoded data slices includes
EDS 1_1 through EDS 5_1 and the first set of slice names includes
SN 1_1 through SN 5_1 and the last set of encoded data slices
includes EDS 1_Y through EDS 5_Y and the last set of slice names
includes SN 1_Y through SN 5_Y.
[0046] FIG. 7 is a schematic block diagram of an example of
dispersed storage error decoding of a data object that was
dispersed storage error encoded and stored in the example of FIG.
4. In this example, the computing device 12 or 16 retrieves from
the storage units at least the decode threshold number of encoded
data slices per data segment. As a specific example, the computing
device retrieves a read threshold number of encoded data
slices.
[0047] In order to recover a data segment from a decode threshold
number of encoded data slices, the computing device uses a decoding
function as shown in FIG. 8. As shown, the decoding function is
essentially an inverse of the encoding function of FIG. 4. The
coded matrix includes a decode threshold number of rows (e.g.,
three in this example) and the decoding matrix in an inversion of
the encoding matrix that includes the corresponding rows of the
coded matrix. For example, if the coded matrix includes rows 1, 2,
and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then
inverted to produce the decoding matrix.
[0048] FIG. 9 is a diagram of an example of a dispersed storage
network. The dispersed storage network includes a DS (dispersed
storage) client module 34 (which may be in DS computing devices 12
and/or 16 of FIG. 1), a network 24, and a plurality of DS units
36-1 . . . 36-n (which may be storage units 36 of FIG. 1 and which
form at least a portion of DS memory 22 of FIG. 1), a DSN managing
unit 18, and a DS integrity verification module (not shown). The DS
client module 34 includes an outbound DS processing section 81 and
an inbound DS processing section 82. Each of the DS units 36-1 . .
. 36-n includes a controller 86, a processing module 84 (e.g.
computer processor) including a communications interface for
communicating over network 24 (not shown), memory 88, a DT
(distributed task) execution module 90, and a DS client module
34.
[0049] In an example of operation, the DS client module 34 receives
data 92. The data 92 may be of any size and of any content, where,
due to the size (e.g., greater than a few Terabytes), the content
(e.g., secure data, etc.), and/or concerns over security and loss
of data, distributed storage of the data is desired. For example,
the data 92 may be one or more digital books, a copy of a company's
emails, a large-scale Internet search, a video security file, one
or more entertainment video files (e.g., television programs,
movies, etc.), data files, and/or any other large amount of data
(e.g., greater than a few Terabytes).
[0050] Within the DS client module 34, the outbound DS processing
section 81 receives the data 92. The outbound DS processing section
81 processes the data 92 to produce slice groupings 96. As an
example of such processing, the outbound DS processing section 81
partitions the data 92 into a plurality of data partitions. For
each data partition, the outbound DS processing section 81
dispersed storage (DS) error encodes the data partition to produce
encoded data slices and groups the encoded data slices into a slice
grouping 96.
[0051] The outbound DS processing section 81 then sends, via the
network 24, the slice groupings 96 to the DS units 36-1 . . . 36-n
of the DSN memory 22 of FIG. 1. For example, the outbound DS
processing section 81 sends slice group 1 to DS storage unit 36-1.
As another example, the outbound DS processing section 81 sends
slice group #n to DS unit #n.
[0052] In one example of operation, the DS client module 34
requests retrieval of stored data within the memory of the DS units
36. In this example, the task 94 is retrieve data stored in the DSN
memory 22. Accordingly, and according to one embodiment, the
outbound DS processing section 81 converts the task 94 into a
plurality of partial tasks 98 and sends the partial tasks 98 to the
respective DS storage units 36-1 . . . 36-n.
[0053] In response to the partial task 98 of retrieving stored
data, a DS storage unit 36 identifies the corresponding encoded
data slices 99 and retrieves them. For example, DS unit #1 receives
partial task #1 and retrieves, in response thereto, retrieved
slices #1. The DS units 36 send their respective retrieved slices
99 to the inbound DS processing section 82 via the network 24.
[0054] The inbound DS processing section 82 converts the retrieved
slices 99 into data 92. For example, the inbound DS processing
section 82 de-groups the retrieved slices 99 to produce encoded
slices per data partition. The inbound DS processing section 82
then DS error decodes the encoded slices per data partition to
produce data partitions. The inbound DS processing section 82
de-partitions the data partitions to recapture the data 92.
[0055] FIG. 10A is a schematic block diagram of an embodiment of a
decentralized agreement module 350 that includes a set of
deterministic functions 340-1 . . . 340-N, a set of normalizing
functions 342-1 . . . 342-N, a set of scoring functions 344-1 . . .
344-N, and a ranking function 352. Each of the deterministic
function, the normalizing function, the scoring function, and the
ranking function 352, may be implemented utilizing the processing
module 84 of FIG. 9. The decentralized agreement module 350 may be
implemented utilizing any module and/or unit of a dispersed storage
network (DSN). For example, the decentralized agreement module is
implemented utilizing the distributed storage (DS) client module 34
of FIG. 1.
[0056] The decentralized agreement module 350 functions to receive
a ranked scoring information request 354 and to generate ranked
scoring information 358 based on the ranked scoring information
request 354 and other information. The ranked scoring information
request 354 includes one or more of an asset identifier (ID) 356 of
an asset associated with the request, an asset type indicator, one
or more location identifiers of locations associated with the DSN,
one or more corresponding location weights, and a requesting entity
ID. The asset includes any portion of data associated with the DSN
including one or more asset types including a data object, a data
record, an encoded data slice, a data segment, a set of encoded
data slices, and a plurality of sets of encoded data slices. As
such, the asset ID 356 of the asset includes one or more of a data
name, a data record identifier, a source name, a slice name, and a
plurality of sets of slice names.
[0057] Each location of the DSN includes an aspect of a DSN
resource. Examples of locations include one or more of a storage
unit, a memory device of the storage unit, a site, a storage pool
of storage units, a pillar index associated with each encoded data
slice of a set of encoded data slices generated by an information
dispersal algorithm (IDA), a DS client module 34 of FIG. 1, a DS
processing unit (computing device) 16 of FIG. 1, a DS integrity
processing unit 20 of FIG. 1, a DSN managing unit 18 of FIG. 1, a
user device (computing device) 12 of FIG. 1, and a user device
(computing device) 14 of FIG. 1.
[0058] Each location is associated with a location weight based on
one or more of a resource prioritization of utilization scheme and
physical configuration of the DSN. The location weight includes an
arbitrary bias which adjusts a proportion of selections to an
associated location such that a probability that an asset will be
mapped to that location is equal to the location weight divided by
a sum of all location weights for all locations of comparison. For
example, each storage pool of a plurality of storage pools is
associated with a location weight based on storage capacity. For
instance, storage pools with more storage capacity are associated
with higher location weights than others. The other information may
include a set of location identifiers and a set of location weights
associated with the set of location identifiers. For example, the
other information includes location identifiers and location
weights associated with a set of memory devices of a storage unit
when the requesting entity utilizes the decentralized agreement
module 350 to produce ranked scoring information 358 with regards
to selection of a memory device of the set of memory devices for
accessing a particular encoded data slice (e.g., where the asset ID
includes a slice name of the particular encoded data slice).
[0059] The decentralized agreement module 350 outputs substantially
identical ranked scoring information for each ranked scoring
information request that includes substantially identical content
of the ranked scoring information request. For example, a first
requesting entity issues a first ranked scoring information request
to the decentralized agreement module 350 and receives first ranked
scoring information. A second requesting entity issues a second
ranked scoring information request to the decentralized agreement
module and receives second ranked scoring information. The second
ranked scoring information is substantially the same as the first
ranked scoring information when the second ranked scoring
information request is substantially the same as the first ranked
scoring information request.
[0060] As such, two or more requesting entities may utilize the
decentralized agreement module 350 to determine substantially
identical ranked scoring information. As a specific example, the
first requesting entity selects a first storage pool of a plurality
of storage pools for storing a set of encoded data slices utilizing
the decentralized agreement module 350 and the second requesting
entity identifies the first storage pool of the plurality of
storage pools for retrieving the set of encoded data slices
utilizing the decentralized agreement module 350.
[0061] In an example of operation, the decentralized agreement
module 350 receives the ranked scoring information request 354.
Each deterministic function performs a deterministic function on a
combination and/or concatenation (e.g., add, append, interleave) of
the asset ID 356 of the ranked scoring information request 354 and
an associated location ID of the set of location IDs to produce an
interim result 341-1 . . . 341-N. The deterministic function
includes at least one of a hashing function, a hash-based message
authentication code function, a mask generating function, a cyclic
redundancy code function, hashing module of a number of locations,
consistent hashing, rendezvous hashing, and a sponge function. As a
specific example, deterministic function 340-2 appends a location
ID 339-2 of a storage pool to a source name as the asset ID to
produce a combined value and performs the mask generating function
on the combined value to produce interim result 341-2.
[0062] With a set of interim results 341-1 . . . 341-N, each
normalizing function 342-1 . . . 342N performs a normalizing
function on a corresponding interim result to produce a
corresponding normalized interim result. The performing of the
normalizing function includes dividing the interim result by a
number of possible permutations of the output of the deterministic
function to produce the normalized interim result. For example,
normalizing function 342-2 performs the normalizing function on the
interim result 341-2 to produce a normalized interim result
343-2.
[0063] With a set of normalized interim results 343-1 . . . 343-N,
each scoring function performs a scoring function on a
corresponding normalized interim result to produce a corresponding
score. The performing of the scoring function includes dividing an
associated location weight by a negative log of the normalized
interim result. For example, scoring function 344-2 divides
location weight 345-2 of the storage pool (e.g., associated with
location ID 339-2) by a negative log of the normalized interim
result 343-2 to produce a score 346-2.
[0064] With a set of scores 346-1 . . . 346-N, the ranking function
352 performs a ranking function on the set of scores 346-1 . . .
346-N to generate the ranked scoring information 358. The ranking
function includes rank ordering each score with other scores of the
set of scores 346-1 . . . 346-N, where a highest score is ranked
first. As such, a location associated with the highest score may be
considered a highest priority location for resource utilization
(e.g., accessing, storing, retrieving, etc., the given asset of the
request). Having generated the ranked scoring information 358, the
decentralized agreement module 350 outputs the ranked scoring
information 358 to the requesting entity.
[0065] FIG. 10B is a flowchart illustrating an example of selecting
a resource. The method begins or continues at step 360 where a
processing module (e.g., of a decentralized agreement module)
receives a ranked scoring information request from a requesting
entity with regards to a set of candidate resources. For each
candidate resource, the method continues at step 362 where the
processing module performs a deterministic function on a location
identifier (ID) of the candidate resource and an asset ID of the
ranked scoring information request to produce an interim result. As
a specific example, the processing module combines the asset ID and
the location ID of the candidate resource to produce a combined
value and performs a hashing function on the combined value to
produce the interim result.
[0066] For each interim result, the method continues at step 364
where the processing module performs a normalizing function on the
interim result to produce a normalized interim result. As a
specific example, the processing module obtains a permutation value
associated with the deterministic function (e.g., maximum number of
permutations of output of the deterministic function) and divides
the interim result by the permutation value to produce the
normalized interim result (e.g., with a value between 0 and 1).
[0067] For each normalized interim result, the method continues at
step 366 where the processing module performs a scoring function on
the normalized interim result utilizing a location weight
associated with the candidate resource associated with the interim
result to produce a score of a set of scores. As a specific
example, the processing module divides the location weight by a
negative log of the normalized interim result to produce the
score.
[0068] The method continues at step 368 where the processing module
rank orders the set of scores to produce ranked scoring information
(e.g., ranking a highest value first). The method continues at step
370 where the processing module outputs the ranked scoring
information to the requesting entity. The requesting entity may
utilize the ranked scoring information to select one location of a
plurality of locations.
[0069] FIG. 10C is a schematic block diagram of an embodiment of a
dispersed storage network (DSN) that includes the distributed
storage (DS) processing unit (computing device) 16 of FIG. 1, the
network 24 of FIG. 1, and the distributed storage network (DSN)
module 22 of FIG. 1. Hereafter, the DSN module 22 may be
interchangeably referred to as a DSN memory. The DS processing unit
16 includes a decentralized agreement module 380 and the DS client
module 34 of FIG. 1. The decentralized agreement module 380 being
implemented utilizing the decentralized agreement module 350 of
FIG. 40A. The DSN module 22 includes a plurality of DS unit pools
400-1 . . . 400-N. Each DS unit pool includes one or more sites
402-1 . . . 402-N. Each site includes one or more DS units 404-1-1
. . . 404-1-N. Each DS unit may be associated with at least one
pillar of N pillars associated with an information dispersal
algorithm (IDA) (406-1 . . . 406-N), where a data segment is
dispersed storage error encoded using the IDA to produce one or
more sets of encoded data slices, and where each set includes N
encoded data slices and like encoded data slices (e.g., slice 3's)
of two or more sets of encoded data slices are included in a common
pillar (e.g., pillar 406-3). Each site may not include every pillar
and a given pillar may be implemented at more than one site. Each
DS unit includes a plurality of memories (e.g. DS unit 404-1-1
includes memories 408-1-1-1 . . . 408-1-1-N. Each DS unit may be
implemented utilizing the DS unit 36 of FIG. 1 and the memories 408
of DS units can be implemented utilizing memory 88 of DS unit 36 in
FIG. 9. Hereafter, a DS unit may be referred to interchangeably as
a storage unit and a set of DS units may be interchangeably
referred to as a set of storage units and/or as a storage unit
set.
[0070] The DSN functions to receive data access requests 382,
select resources of at least one DS unit pool for data access,
utilize the selected DS unit pool for the data access, and issue a
data access response 392 based on the data access. The selecting of
the resources includes utilizing a decentralized agreement function
of the decentralized agreement module 380, where a plurality of
locations are ranked against each other. The selecting may include
selecting one storage pool of the plurality of storage pools,
selecting DS units at various sites of the plurality of sites,
selecting a memory of the plurality of memories for each DS unit,
and selecting combinations of memories, DS units, sites, pillars,
and storage pools.
[0071] In an example of operation, the DS client module 34 receives
the data access request 382 from a requesting entity, where the
data access request 382 includes at least one of a store data
request, a retrieve data request, a delete data request, a data
name, and a requesting entity identifier (ID). Having received the
data access request 382, the DS client module 34 determines a DSN
address associated with the data access request. The DSN address
includes at least one of a source name (e.g., including a vault ID
and an object number associated with the data name), a data segment
ID, a set of slice names, a plurality of sets of slice names. The
determining includes at least one of generating (e.g., for the
store data request) and retrieving (e.g., from a DSN directory,
from a dispersed hierarchical index) based on the data name (e.g.,
for the retrieve data request).
[0072] Having determined the DSN address, the DS client module 34
selects a plurality of resource levels (e.g., DS unit pool, site,
DS unit, pillar, memory) associated with the DSN module 22. The
determining may be based on one or more of the data name, the
requesting entity ID, a predetermination, a lookup, a DSN
performance indicator, and interpreting an error message. For
example, the DS client module 34 selects the DS unit pool as a
first resource level and a set of memory devices of a plurality of
memory devices as a second resource level based on a system
registry lookup for a vault associated with the requesting
entity.
[0073] Having selected the plurality of resource levels, the DS
client module 34, for each resource level, issues a ranked scoring
information request 384 to the decentralized agreement module 380
utilizing the DSN address as an asset ID. The decentralized
agreement module 380 performs the decentralized agreement function
based on the asset ID (e.g., the DSN address), identifiers of
locations of the selected resource levels, and location weights of
the locations to generate ranked scoring information 386.
[0074] For each resource level, the DS client module 34 receives
corresponding ranked scoring information 386. Having received the
ranked scoring information 386, the DS client module 34 identifies
one or more resources associated with the resource level based on
the rank scoring information 386. For example, the DS client module
34 identifies a DS unit pool associated with a highest score and
identifies a set of memory devices within DS units of the
identified DS unit pool with a highest score.
[0075] Having identified the one or more resources, the DS client
module 34 accesses the DSN module 22 based on the identified one or
more resources associated with each resource level. For example,
the DS client module 34 issues resource access requests 388 (e.g.,
write slice requests when storing data, read slice requests when
recovering data) to the identified DS unit pool, where the resource
access requests 388 further identify the identified set of memory
devices. Having accessed the DSN module 22, the DS client module 34
receives resource access responses 390 (e.g., write slice
responses, read slice responses). The DS client module 34 issues
the data access response 392 based on the received resource access
responses 390. For example, the DS client module 34 decodes
received encoded data slices to reproduce data and generates the
data access response 392 to include the reproduced data.
[0076] FIG. 10D is a flowchart illustrating an example of accessing
a dispersed storage network (DSN) memory. The method begins or
continues at step 410 where a processing module (e.g., of a
distributed storage (DS) client module) receives a data access
request from a requesting entity. The data access request includes
one or more of a storage request, a retrieval request, a requesting
entity identifier, and a data identifier (ID). The method continues
at step 412 where the processing module determines a DSN address
associated with the data access request. For example, the
processing module generates the DSN address for the storage
request. As another example, the processing module performs a
lookup for the retrieval request based on the data identifier.
[0077] The method continues at step 414 where the processing module
selects a plurality of resource levels associated with the DSN
memory. The selecting may be based on one or more of a
predetermination, a range of weights associated with available
resources, a resource performance level, and a resource performance
requirement level. For each resource level, the method continues at
step 416 where the processing module determines ranked scoring
information. For example, the processing module issues a ranked
scoring information request to a decentralized agreement module
based on the DSN address and receives corresponding ranked scoring
information for the resource level, where the decentralized
agreement module performs a decentralized agreement protocol
function on the DSN address using the associated resource
identifiers and resource weights for the resource level to produce
the ranked scoring information for the resource level.
[0078] For each resource level, the method continues at step 418
where the processing module selects one or more resources
associated with the resource level based on the ranked scoring
information. For example, the processing module selects a resource
associated with a highest score when one resource is required. As
another example, the processing module selects a plurality of
resources associated with highest scores when a plurality of
resources are required.
[0079] The method continues at step 420 where the processing module
accesses the DSN memory utilizing the selected one or more
resources for each of the plurality of resource levels. For
example, the processing module identifies network addressing
information based on the selected resources including one or more
of a storage unit Internet protocol address and a memory device
identifier, generates a set of encoded data slice access requests
based on the data access request and the DSN address, and sends the
set of encoded data slice access requests to the DSN memory
utilizing the identified network addressing information.
[0080] The method continues at step 422 where the processing module
issues a data access response to the requesting entity based on one
or more resource access responses from the DSN memory. For example,
the processing module issues a data storage status indicator when
storing data. As another example, the processing module generates
the data access response to include recovered data when retrieving
data.
[0081] In one example of operation, the DSN of FIG. 1 is used to
determine byte-hour usage of a vault or by users of the DSN.
Explanations of this process are set out below in conjunction with
FIGS. 11A and 11B.
[0082] A byte-hour is defined as storing one byte for one hour. The
related kilobyte-hour, megabyte-hour, etc. refer to storing a
kilobyte for an hour, and a megabyte per hour respectively. In a
DSN memory billing system, knowing the usage only at the end of a
billing cycle may not accurately reflect the costs of that usage.
The data might have been added at the end of the billing cycle, and
the vault may have been empty for most of that time, or conversely,
the vault might have been storing a lot of data for the majority of
the billing cycle, and all or most of it is deleted right before
the end of the billing cycle. To address this limitation, a fairer
way to meter usage is by some unit that quantifies the quantity of
storage, along with the amount of time that storage capacity was
used. To recover this information and produce an accurate bill, the
billing system must have a way of identifying increases in
utilizations, as well as decreases in utilization, and at what
times those increases and decreases occurred. To achieve this, in
one example of operation, DS processing units maintain a log whose
record entries may include one or more of the following: Operation
Count (may be broken down by type, such as counts for read, write,
and delete operations);
Throughput Used (always positive, may break down input and output
throughput separately); Storage Delta (number of bytes added, or a
negative number indicating bytes removed);
Vault/User Identifier; and
[0083] Time stamp
[0084] The collection of these records, aggregated for one vault
(storage container) or for one user, across the duration of the
billing cycle (and basing the starting point for the total capacity
of the vault at the time of the end for the previous billing
cycle), a billing system can compute the byte-hours utilization.
The billing system may also bill separately for each operation (and
at different rates for each) or for throughput utilization. The log
for each DS processing unit must be stored reliably, such that the
failure of the DS processing unit does not result in an incomplete
picture of the current vault's utilization. Therefore, a dispersed
data structure, such as a queue, or tree may be utilized. After the
billing cycle has completed, the DS processing unit may archive or
delete these individual records. However, the billing system must
maintain the current utilization at the time of the last billing
cycle, which when all deltas are added at the end of the billing
cycle, will yield the current utilization for that vault.
[0085] FIG. 11A is a schematic block diagram of another embodiment
of a dispersed storage network that includes a plurality of
distributed storage (DS) processing units 16-1 to 16-D, the
distributed storage network (DSN) managing unit 18 of FIG. 1, the
network 24 of FIG. 1, and a plurality of storage sets 500-1 to
500-S. Each DS processing unit may be implemented utilizing the DST
processing unit 16 of FIG. 1. Each storage set includes a set of
storage units 36-1 to 36-n. Each storage unit may be implemented
utilizing the DS unit 36 of FIG. 1. The DSN functions to determine
utilization levels of storage within the DSN. The managing unit 18
may include a computing core 26, which can include one or more
computer processors, and a communications interface 33.
[0086] In an example of operation of the determining of the
utilization levels of the storage within the DSN, the DSN managing
unit 18 obtains, from each DS processing unit, transaction records
502-1 to 502-D, where the transaction includes the DS processing
units 16-1 to 16-D accessing, via the network 24, encoded data
slices 504-1 to 504-S, which could be part of a set of encoded data
slices, stored in one or more of the plurality of storage sets, and
where each transaction record includes one or more of an operation
count, an operation type (e.g., read, write, delete), number of
slice bytes transferred, number of slice bytes deleted, a
timestamp, a user identifier, and a vault identifier. The obtaining
includes one or more of receiving the transaction records from the
DS processing units 16-1 to 16-D, where the DS processing units
generate the transaction records, issuing a transaction record
request, and retrieving a transaction record from a set of storage
units, where the transaction record is stored as one or more sets
of encoded transaction record slices.
[0087] Having obtained the transaction records, the DSN managing
unit 18, for each received transaction record 502-1 to 502-D,
updates a cumulative data storage byte-hour count for storage of
corresponding bytes of encoded data slices in the plurality of
storage sets for one or more affiliated entities of a plurality of
entities utilizing the DSN (e.g., one or more users, a group or
users, a vault). The updating includes one or more of identifying
the one or more affiliated entities, determining a byte-hour
adjustment (i.e., up or down) based on the received transaction
record, and updating a byte-hour record for each of the one or more
affiliated entities based on the byte-hour adjustment.
[0088] Having updated the cumulative data storage byte-hour count,
the DSN managing unit 18 issues byte-hour usage information for
each of the one or more of the plurality of entities utilizing the
DSN based on the updated cumulative data storage byte-hour count
for storage. For example, the DSN managing unit 18 identifies the
one or more entities (e.g., interprets a request, utilizes a
predetermination, and/or selects all from time to time), for each
entity, generates the byte-hour usage information based on the
updated cumulative data storage byte-hour count, and outputs the
generated byte-hour usage information (e.g., byte-hour usage
information for users 1-U).
[0089] FIG. 11B is a flowchart illustrating an example of
determining utilization levels of storage within a dispersed
storage network (DSN). The method includes a step 600 where a
processing module (e.g., of a distributed storage network (DSN)
managing unit) obtains, from a plurality of DS processing units 16,
transaction records, where the plurality of DS processing units
transact encoded data slice access with DS storage units 36 of the
DSN on behalf of a plurality of DSN users. The obtaining includes
at least one of receiving from the processing unit, where the
processing unit generates a transaction record, issuing a
transaction record request to a processing unit, and retrieving a
transaction record from a set of storage units, where the
transaction record is dispersed storage error encoded to produce a
set of encoded transaction slices that are stored in the set of
storage units.
[0090] For each transaction record, the method continues at the
step 602 where the processing module updates a cumulative data
storage byte-hour count for storage of corresponding bytes of
encoded data slices in the storage units of the DSN for one or more
of the DSN users. The updating includes one or more of identifying
the one or more affiliated entities, determining a byte-hour
adjustment (e.g., up or down) based on the received transaction
record, and updating a byte-hour record for each of the one or more
affiliated entities based on the byte-hour adjustment.
[0091] The method continues at the step 604 where the processing
module issues byte-hour usage information for at least some of the
DSN users based on the updated cumulative data storage byte-hour
counts. For example, the processing module identifies the one or
more entities (e.g., interpret a request, utilize a
predetermination, select all entities from time to time), for each
entity, generate the byte-hour usage information based on the
updated cumulative data storage byte-hour count, and output the
generated byte-hour usage information.
[0092] As may be used herein, 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. As may also be used herein, the term(s)
"configured to", "operably coupled to", "coupled to", and/or
"coupling" 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 an example of 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. As may further be used herein, inferred coupling
(i.e., where one element is coupled to another element by
inference) includes direct and indirect coupling between two items
in the same manner as "coupled to". As may even further be used
herein, the term "configured to", "operable to", "coupled to", or
"operably coupled to" indicates that an item includes one or more
of power connections, input(s), output(s), etc., to perform, when
activated, one or more its corresponding functions and may further
include inferred coupling to one or more other items. As may still
further be used herein, the term "associated with", includes direct
and/or indirect coupling of separate items and/or one item being
embedded within another item.
[0093] As may be used herein, 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 A has a greater magnitude than
signal B, a favorable comparison may be achieved when the magnitude
of signal A is greater than that of signal B or when the magnitude
of signal B is less than that of signal A. As may be used herein,
the term "compares unfavorably", indicates that a comparison
between two or more items, signals, etc., fails to provide the
desired relationship.
[0094] As may also be used herein, the terms "processing module",
"processing circuit", "processor", and/or "processing unit" 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, module, processing circuit,
and/or processing unit may be, or further include, memory and/or an
integrated memory element, which may be a single memory device, a
plurality of memory devices, and/or embedded circuitry of another
processing module, module, processing circuit, and/or processing
unit. 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. Note that if the processing module,
module, processing circuit, and/or processing unit 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 distributedly located (e.g.,
cloud computing via indirect coupling via a local area network
and/or a wide area network). Further note that if the processing
module, module, processing circuit, and/or processing unit
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. Still further note that, the memory element
may store, and the processing module, module, processing circuit,
and/or processing unit executes, hard coded and/or operational
instructions corresponding to at least some of the steps and/or
functions illustrated in one or more of the Figures. Such a memory
device or memory element can be included in an article of
manufacture.
[0095] One or more embodiments have been described above with the
aid of method steps illustrating the performance of specified
functions and relationships thereof. The boundaries and sequence of
these functional building blocks and method steps have been
arbitrarily defined herein for convenience of description.
Alternate boundaries and sequences can be defined so long as the
specified functions and relationships are appropriately performed.
Any such alternate boundaries or sequences are thus within the
scope and spirit of the claims. Further, the boundaries of these
functional building blocks have been arbitrarily defined for
convenience of description. Alternate boundaries could be defined
as long as the certain significant functions are appropriately
performed. Similarly, flow diagram blocks may also have been
arbitrarily defined herein to illustrate certain significant
functionality.
[0096] To the extent used, the flow diagram block boundaries and
sequence could have been defined otherwise and still perform the
certain significant functionality. Such alternate definitions of
both functional building blocks and flow diagram blocks and
sequences are thus within the scope and spirit of the claims. One
of average skill in the art will also recognize that the functional
building blocks, and other illustrative blocks, modules and
components herein, can be implemented as illustrated or by discrete
components, application specific integrated circuits, processors
executing appropriate software and the like or any combination
thereof.
[0097] In addition, a flow diagram may include a "start" and/or
"continue" indication. The "start" and "continue" indications
reflect that the steps presented can optionally be incorporated in
or otherwise used in conjunction with other routines. In this
context, "start" indicates the beginning of the first step
presented and may be preceded by other activities not specifically
shown. Further, the "continue" indication reflects that the steps
presented may be performed multiple times and/or may be succeeded
by other activities not specifically shown. Further, while a flow
diagram indicates a particular ordering of steps, other orderings
are likewise possible provided that the principles of causality are
maintained.
[0098] The one or more embodiments are used herein to illustrate
one or more aspects, one or more features, one or more concepts,
and/or one or more examples. A physical embodiment of an apparatus,
an article of manufacture, a machine, and/or of a process may
include one or more of the aspects, features, concepts, examples,
etc. described with reference to one or more of the embodiments
discussed herein. Further, from Figure to Figure, the embodiments
may incorporate the same or similarly named functions, steps,
modules, etc. that may use the same or different reference numbers
and, as such, the functions, steps, modules, etc. may be the same
or similar functions, steps, modules, etc. or different ones.
[0099] Unless specifically stated to the contra, signals to, from,
and/or between elements in a figure of any of the figures presented
herein may be analog or digital, continuous time or discrete time,
and single-ended or differential. For instance, if a signal path is
shown as a single-ended path, it also represents a differential
signal path. Similarly, if a signal path is shown as a differential
path, it also represents a single-ended signal path. While one or
more particular architectures are described herein, other
architectures can likewise be implemented that use one or more data
buses not expressly shown, direct connectivity between elements,
and/or indirect coupling between other elements as recognized by
one of average skill in the art.
[0100] The term "module" is used in the description of one or more
of the embodiments. A module implements one or more functions via a
device such as a processor or other processing device or other
hardware that may include or operate in association with a memory
that stores operational instructions. A module may operate
independently and/or in conjunction with software and/or firmware.
As also used herein, a module may contain one or more sub-modules,
each of which may be one or more modules.
[0101] As may further be used herein, a computer readable memory
includes one or more memory elements. A memory element may be a
separate memory device, multiple memory devices, or a set of memory
locations within a memory device. 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 memory device may be in a form a solid state memory, a hard
drive memory, cloud memory, thumb drive, server memory, computing
device memory, and/or other physical medium for storing digital
information. A computer readable memory/storage medium, as used
herein, is not to be construed as being transitory signals per se,
such as radio waves or other freely propagating electromagnetic
waves, electromagnetic waves propagating through a waveguide or
other transmission media (e.g., light pulses passing through a
fiber-optic cable), or electrical signals transmitted through a
wire.
[0102] While particular combinations of various functions and
features of the one or more embodiments have been expressly
described herein, other combinations of these features and
functions are likewise possible. The present disclosure is not
limited by the particular examples disclosed herein and expressly
incorporates these other combinations.
* * * * *