CN103533043B - A kind of charging method of the cloud stores service based on REST - Google Patents
A kind of charging method of the cloud stores service based on REST Download PDFInfo
- Publication number
- CN103533043B CN103533043B CN201310472390.8A CN201310472390A CN103533043B CN 103533043 B CN103533043 B CN 103533043B CN 201310472390 A CN201310472390 A CN 201310472390A CN 103533043 B CN103533043 B CN 103533043B
- Authority
- CN
- China
- Prior art keywords
- perform
- user
- record
- data file
- request
- 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
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a kind of charging method of cloud stores service.This method is directed to the cloud stores service based on REST access interface, and in conjunction with the charging index of user, from real-time storage space, data transfer throughput and HTTP request number of times three aspect carry out charging.Charging method is based on quantifiable objective data, completely transparent to user, improves charging accuracy.
Description
(1) technical field
What the present invention relates to is a kind of charging method of the cloud stores service based on REST.
(2) background technology
Along with the development of cloud computing technology, the utilization that cloud stores is more and more extensive.Cloud storage is a cloud computing system being core with data store and management, from the definition of service angle: used as required for multi-user provides by network, the stores service of charging as required; Define from technical standpoint: by technology such as cluster application, grid or distributed file systems, various dissimilar memory device a large amount of network is gathered collaborative work, jointly externally provide data to store and Operational Visit function.
Http protocol (HyperTextTransferProtocol, HTML (Hypertext Markup Language)) is the agreement for the webserver and local client transmission hypertext.User end to server sends request message, and server then sends response message to client, and two kinds of messages are formed by begin column, stem row, entity body.It is request message or response message that begin column is used for differentiation, the begin column of request message is called request line, specify the path of institute's request resource, i.e. URI (universal resource identifier), and method of operation, that wherein uses herein has: GET (sending request to allocated resource), POST (submitting to data to carry out process request to allocated resource), PUT (uploading its what be new to allocated resource position), DELETE (request server deletion allocated resource).The begin column of response message is called statusline, contains the state of server response.Stem row is used for some information of client, server or main body of the packet are described.Entity body is the text of message.
REST (RepresentationalStateTransfer, declarative state transitions) be a kind of network service based on http protocol realize framework, REST specifies that the resource in service identifies by URI, acquisition, establishment, amendment are comprised to the operation of resource and deletes, corresponding to GET, POST, PUT and DELETE method that http protocol provides.
At present, the charge mode of cloud stores service is also in the middle of exploration, a kind of scheme is the memory space rented according to user is fixed size, rental period length is that the mode in monthly, season or year carries out charging, do not consider the instream factor of user under this pattern, cause the waste of the inaccurate of charging and resource.Another kind of scheme be to user stores take space, transfer of data generation flow, the successful pay of HTTP request, this pattern meets the situation of user's reality, for user has saved cost, for service provider improves resource utilization.And this charge mode carried out according to the actual service condition of user at present, only considered the information such as the time used of user, flow, consider the actual concrete dynamic change factor such as to take up room of the busy-idle condition in network system running, information, for this reason, a kind of method that this patent devises busy-idle condition charging according to server, the billing parameter etc. that provides plurality of optional to select carries out dynamic charging, makes cloud billing model more precisely and meets the multiple demand of user.
(3) summary of the invention
Object of the present invention is providing a kind of rational charging method of cloud stores service.The method is directed to the cloud stores service based on REST access interface, substantially increases the accuracy of charging.
The present invention is achieved in that
If cloud storage system has x user (U
1, U
2..., U
x), the storage resources that all users have is by URI unique identification, and be divided into data file and container two type comprising data file, data file takies certain memory space, and the type of resource can judge from URI; All access to cloud stores service are all based on HTTP request, and user passes through the information of GET method Gains resources or resource, and PUT method creates or replacement resource, the information of POST method amendment resource, and DELETE method deletes resource;
If cloud storage system can obtain the owning user of each HTTP request, requesting method, request resource, the request moment (adopt timestamp mode to represent, namely when 1 day 00 January of 1970 Greenwich mean time 00 point 00 second to present total number of seconds) and data transfer throughput (unit is byte); Ask to be the establishment to data file or deletion if current, user also at the memory space (unit is byte) in this request moment can increase accordingly or reduce; Based on above information, system is set up and is safeguarded following three records:
A) HTTP request record RH: the finite aggregate of four-tuple (u, m, t, b), wherein u ∈ (U
1, U
2..., U
x), be request owning user, { GET, PUT, DELETE, POST} are requesting method to m ∈, and t is the request moment, and b is data transfer throughput;
B) data file RD: the finite aggregate of tlv triple (u, r, s), wherein u is data file owning user, and r is the URI mark of data file, and s is taking up room of data file, identical with data file produces flow value when transmitting;
C) real-time storage spatial variations record RS: the finite aggregate of tlv triple (u, c, t), wherein u is the owning user of each memory space change, and c is the memory space after change, and t is the moment (timestamp form) changed;
Cloud storage system, when carrying out charging, gets information from above-mentioned record, then from real-time storage space, data transfer throughput and HTTP request number of times three aspect carry out charging, the billing parameter related separately to is as follows:
A) real-time storage space charge stores the room and time generation taken according to user, and user has C
fthe free space of byte-sized, exceedes the part in free space, and the storage price of interior every byte per second is P
s(unit);
B) flow added up when data transfer throughput expense uploads downloading data according to user produces, and the price uploading flow and downloading flow is respectively every byte P
uand P
d(unit);
C) HTTP request number of times expense produces according to user's HTTP request number of success, due to intraday HTTP request each period distribution and uneven, generally the number of request at night is far smaller than daytime, so just there is peak hours/period and idle period in the response of server, setting cloud storage system server had λ peak hours/period, ([T within one day
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ]), wherein T
α i, T
β i, (i ∈ [1, λ]) all shows with tabulation in 24 of standard hours, and other periods are idle period; Single GET, POST, PUT in peak hours/period and the successful price of DELETE request P respectively
g1, P
o1, P
p1and P
l1(unit), and time at one's leisure in section, single GET, POST, PUT and the successful price of DELETE request are respectively P
g2, P
o2, P
p2and P
l2(unit);
N billing parameter set (P is comprised in setting cloud storage system
1, P
2..., P
n), wherein arbitrary P
i(i ∈ [1, n]) is by parameter
form; Set all use and specify unique billing parameter set per family;
Its concrete grammar step is:
(1) cloud storage system arranges n billing parameter set (P
1, P
2..., P
n);
(2) cloud storage system sets up HTTP request record RH, data file RD and real-time storage spatial variations record RS;
(3) cloud storage system gets the owning user u of the HTTP request of each access cloud stores service, requesting method m, request resource r, request moment t and data transfer throughput b, will record (u, m, t, b) and increase newly in RH;
(4) if m=PUT and r is data file, then illustrate that user creates data file, will record (u, r, b) and increase newly in RD, execution (5);
Otherwise perform (7);
(5) if there is record in RS, then obtaining owning user is u, and the change moment is closest to the record (u, c ', t ') of t, will record that (u, c '+b, t) increases newly in RS, execution (7);
Otherwise, perform (6);
(6) will record (u, b, t) increases newly in RS;
(7) if m=DELETE and r is data file, then illustrate that user deletes data file, the owning user obtained in RD is u and data file URI is the record (u of r, r, s), then obtain owning user in RS and be u and change the record (u of moment closest to t, c "; t "), will record (u, c "-s; t) increase newly in RS; delete record (u, r, s) in RD;
(8) input needs the user U of charging, and charging start time T
1with finish time T
n;
(9) the billing parameter set P of user U is obtained
w;
(10) obtaining owning user in RS is U, and is engraved in T during change
1to T
nbetween all records, be designated as { (U, C
2, T
2), (U, C
3, T
3) ..., (U, C
h, T
h), wherein T
1<T
2< ... <T
h<T
n;
(11) if there is owning user in RS is U, and T is engraved in during change
1record before, obtains and wherein changes the moment closest to T
1record (U, C
0, T
0), make C
1=C
0, perform (13);
Otherwise, perform (12);
(12) C is made
1=0;
(13) real-time storage space charge F is tried to achieve
1:
(14) obtaining owning user in RH is U, and is engraved in T during request
1to T
nbetween all records, be designated as { (U, M
1, T
1, B
1), (U, M
2, T
2, B
2) ..., (U, M
y, T
y, B
y), wherein T
1<T
2< ... <T
y<T
n;
(15) initialization B
u=0, B
d=0, H
g1=0, H
o1=0, H
p1=0, H
l1=0, H
g2=0, H
o2=0, H
p2=0, H
l2=0, make i=0;
(16) record (U, M is obtained
i, T
i, B
i), by the T represented with timestamp form
ibe converted to the T that Greenwich mean time, form represented
i';
(17) if M
i=PUT, then B
u=B
u+ B
i, perform (18);
Otherwise, perform (20);
(18) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within,
H
p1=H
p1+ 1, perform (28);
Otherwise, perform (19);
(19) H
p2=H
p2+ 1, perform (28);
(20) if M
i=GET, then B
d=B
d+ B
i, perform (21);
Otherwise, perform (23);
(21) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
g1=H
g1+ 1, perform (28);
Otherwise, perform (22);
(22) H
g2=H
g2+ 1, perform (28);
(23) if M
i=POST, then perform (24);
Otherwise, perform (26);
(24) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
o1=H
o1+ 1, perform (28);
Otherwise, perform (25);
(25) H
o2=H
o2+ 1, perform (28);
(26) now M
i=DELETE, if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, then H
l1=H
l1+ 1, perform (28);
Otherwise, perform (27);
(27)H
l2＝H
l2+1；
(28) i=i+1, if i≤n, performs (16);
Otherwise, perform (29);
(29) data transfer throughput expense is tried to achieve
(30) HTTP request number of times expense is tried to achieve
(31) total cost F=F
1+ F
2+ F
3;
(32) calculated, returned the charging result of user U.
The charging method of cloud stores service set forth in the present invention, based on the real-time storage space of user, data transfer throughput and these three kinds of quantifiable objective datas of HTTP request number of times, completely transparent to user, set different billing parameter set simultaneously, agree with mutually with user's diversified cloud stores service demand.User takies oneself memory space as required, and select billing parameter as required, saved cost, service provider also improves the utilance of equipment.
The novelty of this method is:
1. pair user's real-time storage takes up room accurate charging.The change in the real-time storage space of cloud storage system recording user, carries out charging according to memory space actual in each time period.
2. can set multiple billing parameter set allows user select, like this service condition is stored for identical cloud, different billing parameter set is different with the charging result of HTTP request number of times to real-time storage space, data transfer throughput, meet different user's requests, such as certain user only uses cloud storage platform backup file, and infrequently access these files, so select the expense of real-time storage space calculating lower, to the billing parameter set costly that data transfer throughput and HTTP request number of times calculate, total cost can be lower.
3., when calculating HTTP request number of times expense, consider that cloud storage system exists peak hours/period and idle period (if 1:00 AM is to 6 points) one day server, section provides the cost of service lower at one's leisure.Period residing for request, more realistic situation, also attracted user more to HTTP request number of times price.
(4) accompanying drawing explanation
Fig. 1, cloud storage system schematic diagram
(5) embodiment
Below in conjunction with accompanying drawing citing, the present invention is described in more detail:
The feature of the method for the invention is:
If cloud storage system has x user (U
1, U
2..., U
x), the storage resources that all users have is by URI unique identification, and be divided into data file and container two type comprising data file, data file takies certain memory space, and the type of resource can judge from URI; All access to cloud stores service are all based on HTTP request, and user passes through the information of GET method Gains resources or resource, and PUT method creates or replacement resource, the information of POST method amendment resource, and DELETE method deletes resource;
If cloud storage system can obtain the owning user of each HTTP request, requesting method, request resource, the request moment (adopt timestamp mode to represent, namely when 1 day 00 January of 1970 Greenwich mean time 00 point 00 second to present total number of seconds) and data transfer throughput (unit is byte); Ask to be the establishment to data file or deletion if current, user also at the memory space (unit is byte) in this request moment can increase accordingly or reduce; Based on above information, system is set up and is safeguarded following three records:
D) HTTP request record RH: the finite aggregate of four-tuple (u, m, t, b), wherein u ∈ (U
1, U
2..., U
x), be request owning user, { GET, PUT, DELETE, POST} are requesting method to m ∈, and t is the request moment, and b is data transfer throughput;
E) data file RD: the finite aggregate of tlv triple (u, r, s), wherein u is data file owning user, and r is the URI mark of data file, and s is taking up room of data file, identical with data file produces flow value when transmitting;
F) real-time storage spatial variations record RS: the finite aggregate of tlv triple (u, c, t), wherein u is the owning user of each memory space change, and c is the memory space after change, and t is the moment (timestamp form) changed;
Cloud storage system, when carrying out charging, gets information from above-mentioned record, then from real-time storage space, data transfer throughput and HTTP request number of times three aspect carry out charging, the billing parameter related separately to is as follows:
D) real-time storage space charge stores the room and time generation taken according to user, and user has C
fthe free space of byte-sized, exceedes the part in free space, and the storage price of interior every byte per second is P
s(unit);
E) flow added up when data transfer throughput expense uploads downloading data according to user produces, and the price uploading flow and downloading flow is respectively every byte P
uand P
d(unit); P3
F) HTTP request number of times expense produces according to user's HTTP request number of success, due to intraday HTTP request each period distribution and uneven, generally the number of request at night is far smaller than daytime, so just there is peak hours/period and idle period in the response of server, setting cloud storage system server had m peak hours/period, ([T within one day
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ]), wherein T
α i, T
β i, (i ∈ [1, λ]) all shows with tabulation in 24 of standard hours, and other periods are idle period; Single GET, POST, PUT in peak hours/period and the successful price of DELETE request P respectively
g1, P
o1, P
p1and P
l1(unit), and time at one's leisure in section, single GET, POST, PUT and the successful price of DELETE request are respectively P
g2, P
o2, P
p2and P
l2(unit);
N billing parameter set (P is comprised in setting cloud storage system
1, P
2..., P
n), wherein arbitrary P
i(i ∈ [1, n]) is by parameter
form; Set all use and specify unique billing parameter set per family;
Its concrete grammar step is:
(1) cloud storage system arranges n billing parameter set (P
1, P
2..., P
n);
(2) cloud storage system sets up HTTP request record RH, data file RD and real-time storage spatial variations record RS;
(3) cloud storage system gets the owning user u of the HTTP request of each access cloud stores service, requesting method m, request resource r, request moment t and data transfer throughput b, will record (u, m, t, b) and increase newly in RH;
(4) if m=PUT and r is data file, then illustrate that user creates data file, will record (u, r, b) and increase newly in RD, execution (5);
Otherwise perform (7);
(5) if there is record in RS, then obtaining owning user is u, and the change moment is closest to the record (u, c ', t ') of t, will record that (u, c '+b, t) increases newly in RS, execution (7);
Otherwise, perform (6);
(6) will record (u, b, t) increases newly in RS;
(7) if m=DELETE and r is data file, then illustrate that user deletes data file, the owning user obtained in RD is u and data file URI is the record (u of r, r, s), then obtain owning user in RS and be u and change the record (u of moment closest to t, c "; t "), will record (u, c "-s; t) increase newly in RS; delete record (u, r, s) in RD;
(8) input needs the user U of charging, and charging start time T
1with finish time T
n;
(9) the billing parameter set P of user U is obtained
w;
(10) obtaining owning user in RS is U, and is engraved in T during change
1to T
nbetween all records, be designated as { (U, C
2, T
2), (U, C
3, T
3) ..., (U, C
h, T
h), wherein T
1<T
2< ... <T
h<T
n;
(11) if there is owning user in RS is U, and T is engraved in during change
1record before, obtains and wherein changes the moment closest to T
1record (U, C
0, T
0), make C
1=C
0, perform (13);
Otherwise, perform (12);
(12) C is made
1=0;
(13) real-time storage space charge F is tried to achieve
1:
(14) obtaining owning user in RH is U, and is engraved in T during request
1to T
nbetween all records, be designated as { (U, M
1, T
1, B
1), (U, M
2, T
2, B
2) ..., (U, M
y, T
y, B
y), wherein T
1<T
2< ... <T
y<T
n;
(15) initialization B
u=0, B
d=0, H
g1=0, H
o1=0, H
p1=0, H
l1=0, H
g2=0, H
o2=0, H
p2=0, H
l2=0, make i=0;
(16) record (U, M is obtained
i, T
i, B
i), by the T represented with timestamp form
ibe converted to the T that Greenwich mean time, form represented
i';
(17) if M
i=PUT, then B
u=B
u+ B
i, perform (18);
Otherwise, perform (20);
(18) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
p1=H
p1+ 1, perform (28);
Otherwise, perform (19);
(19) H
p2=H
p2+ 1, perform (28);
(20) if M
i=GET, then B
d=B
d+ B
i, perform (21);
Otherwise, perform (23);
(21) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
g1=H
g1+ 1, perform (28);
Otherwise, perform (22);
(22) H
g2=H
g2+ 1, perform (28);
(23) if M
i=POST, then perform (24);
Otherwise, perform (26);
(24) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
o1=H
o1+ 1, perform (28);
Otherwise, perform (25);
(25) H
o2=H
o2+ 1, perform (28);
(26) now M
i=DELETE, if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, then H
l1=H
l1+ 1, perform (28);
Otherwise, perform (27);
(27)H
l2＝H
l2+1；
(28) i=i+1, if i≤n, performs (16);
Otherwise, perform (29);
(29) data transfer throughput expense is tried to achieve
(30) HTTP request number of times expense is tried to achieve
(31) total cost F=F
1+ F
2+ F
3;
(32) calculated, returned the charging result of user U.
Wherein, step (1) completes the setting of billing parameter set, step (2) constructs HTTP request record, data file and the real-time storage spatial variations record needed for charging to step (7), system, after the HTTP request getting each access cloud stores service, all will perform step (3) completes record renewal to step (7); Be the process of computational costs after step (8), first input need charging user, start time and finish time, then from above-mentioned record, obtain data, complete calculating according to charging formula.
Claims (1)
1., based on a charging method for the cloud stores service of REST, it is characterized in that:
If cloud storage system has x user (U
1, U
2..., U
x), the storage resources that all users have is by URI unique identification, and be divided into data file and container two type comprising data file, data file takies certain memory space, and the type of resource can judge from URI; All access to cloud stores service are all based on HTTP request, and user passes through the information of GET method Gains resources or resource, and PUT method creates or replacement resource, the information of POST method amendment resource, and DELETE method deletes resource;
If cloud storage system can obtain the owning user of each HTTP request, requesting method, request resource, the request moment (adopt timestamp mode to represent, namely when 1 day 00 January of 1970 Greenwich mean time 00 point 00 second to present total number of seconds) and data transfer throughput (unit is byte); Ask to be the establishment to data file or deletion if current, user also at the memory space (unit is byte) in this request moment can increase accordingly or reduce; Based on above information, system is set up and is safeguarded following three records:
A) HTTP request record RH: the finite aggregate of four-tuple (u, m, t, b), wherein u ∈ (U
1, U
2..., U
x), be request owning user, { GET, PUT, DELETE, POST} are requesting method to m ∈, and t is the request moment, and b is data transfer throughput;
B) data file RD: the finite aggregate of tlv triple (u, r, s), wherein u is data file owning user, and r is the URI mark of data file, and s is taking up room of data file, identical with data file produces flow value when transmitting;
C) real-time storage spatial variations record RS: the finite aggregate of tlv triple (u, c, t), wherein u is the owning user of each memory space change, and c is the memory space after change, and t is the moment (timestamp form) changed;
Cloud storage system, when carrying out charging, gets information from above-mentioned record, then from real-time storage space, data transfer throughput and HTTP request number of times three aspect carry out charging, the billing parameter related separately to is as follows:
A) real-time storage space charge stores the room and time generation taken according to user, and user has C
fthe free space of byte-sized, exceedes the part in free space, and the storage price of interior every byte per second is P
s(unit);
B) flow added up when data transfer throughput expense uploads downloading data according to user produces, and the price uploading flow and downloading flow is respectively every byte P
uand P
d(unit);
C) HTTP request number of times expense produces according to user's HTTP request number of success, due to intraday HTTP request each period distribution and uneven, generally the number of request at night is far smaller than daytime, so just there is peak hours/period and idle period in the response of server, setting cloud storage system server had λ peak hours/period, ([T within one day
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ]), wherein T
α i, T
β i, (i ∈ [1, λ]) all shows with tabulation in 24 of standard hours, and other periods are idle period; Single GET, POST, PUT in peak hours/period and the successful price of DELETE request P respectively
g1, P
o1, P
p1and P
l1(unit), and time at one's leisure in section single GET, POST, PUT and
The successful price of DELETE request is respectively P
g2, P
o2, P
p2and P
l2(unit);
N billing parameter set (P is comprised in setting cloud storage system
1, P
2..., P
n), wherein arbitrary P
i(i ∈ [1, n]) is by parameter
form; Set all use and specify unique billing parameter set per family;
Its concrete grammar step is:
(1) cloud storage system arranges n billing parameter set (P
1, P
2..., P
n);
(2) cloud storage system sets up HTTP request record RH, data file RD and real-time storage spatial variations record RS;
(3) cloud storage system gets the owning user u of the HTTP request of each access cloud stores service, requesting method m, request resource r, request moment t and data transfer throughput b, will record (u, m, t, b) and increase newly in RH;
(4) if m=PUT and r is data file, then illustrate that user creates data file, will record (u, r, b) and increase newly in RD, execution (5);
Otherwise perform (7);
(5) if there is record in RS, then obtaining owning user is u, and the change moment is closest to the record (u, c ', t ') of t, will record that (u, c '+b, t) increases newly in RS, execution (7); Otherwise, perform (6);
(6) will record (u, b, t) increases newly in RS;
(7) if m=DELETE and r is data file, then illustrate that user deletes data file, the owning user obtained in RD is u and data file URI is the record (u of r, r, s), then obtain owning user in RS and be u and change the record (u of moment closest to t, c "; t "), will record (u, c "-s; t) increase newly in RS; delete record (u, r, s) in RD;
(8) input needs the user U of charging, and charging start time T
1with finish time T
n;
(9) the billing parameter set P of user U is obtained
w;
(10) obtaining owning user in RS is U, and is engraved in T during change
1to T
nbetween all records, be designated as { (U, C
2, T
2), (U, C
3, T
3) ..., (U, C
h, T
h), wherein T
1<T
2< ... <T
h<T
n;
(11) if there is owning user in RS is U, and T is engraved in during change
1record before, obtains and wherein changes the moment closest to T
1record (U, C
0, T
0), make C
1=C
0, perform (13);
Otherwise, perform (12);
(12) C is made
1=0;
(13) real-time storage space charge F is tried to achieve
1:
wherein
(14) obtaining owning user in RH is U, and is engraved in T during request
1to T
nbetween all records, be designated as { (U, M
1, T
1, B
1), (U, M
2, T
2, B
2) ..., (U, M
y, T
y, B
y), wherein T
1<T
2< ... <T
y<T
n;
(15) initialization B
u=0, B
d=0, H
g1=0, H
o1=0, H
p1=0, H
l1=0, H
g2=0, H
o2=0, H
p2=0, H
l2=0, make i=0;
(16) record (U, M is obtained
i, T
i, B
i), by the T represented with timestamp form
ibe converted to the T that Greenwich mean time, form represented
i';
(17) if M
i=PUT, then B
u=B
u+ B
i, perform (18);
Otherwise, perform (20);
(18) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
p1=H
p1+ 1, perform (28);
Otherwise, perform (19);
(19) H
p2=H
p2+ 1, perform (28);
(20) if M
i=GET, then B
d=B
d+ B
i, perform (21);
Otherwise, perform (23);
(21) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
g1=H
g1+ 1, perform (28);
Otherwise, perform (22);
(22) H
g2=H
g2+ 1, perform (28);
(23) if M
i=POST, then perform (24);
Otherwise, perform (26);
(24) if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, H
o1=H
o1+ 1, perform (28);
Otherwise, perform (25);
(25) H
o2=H
o2+ 1, perform (28);
(26) now M
i=DELETE, if T
i' represented time be engraved in one day server peak hours/period [T
α 1, T
β 1], [T
α 2, T
β 2] ..., [T
α λ, T
β λ] within, then H
l1=H
l1+ 1, perform (28);
Otherwise, perform (27);
(27)H
l2＝H
l2+1；
(28) i=i+1, if i≤n, performs (16);
Otherwise, perform (29);
(29) data transfer throughput expense is tried to achieve
(30) HTTP request number of times expense is tried to achieve
(31) total cost F=F
1+ F
2+ F
3;
(32) calculated, returned the charging result of user U.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310472390.8A CN103533043B (en) | 2013-10-11 | 2013-10-11 | A kind of charging method of the cloud stores service based on REST |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310472390.8A CN103533043B (en) | 2013-10-11 | 2013-10-11 | A kind of charging method of the cloud stores service based on REST |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103533043A CN103533043A (en) | 2014-01-22 |
| CN103533043B true CN103533043B (en) | 2016-04-06 |
Family
ID=49934708
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310472390.8A Expired - Fee Related CN103533043B (en) | 2013-10-11 | 2013-10-11 | A kind of charging method of the cloud stores service based on REST |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103533043B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104113424A (en) * | 2014-06-23 | 2014-10-22 | 汉柏科技有限公司 | Resource authorization method and system |
| JP6372187B2 (en) * | 2014-06-23 | 2018-08-15 | 富士通株式会社 | History information management method, history information management apparatus, and history information management program |
| CN104113595B (en) * | 2014-07-09 | 2018-01-02 | 武汉邮电科学研究院 | A kind of mixing cloud storage system and method based on safety status classification |
| US20170116217A1 (en) * | 2015-03-24 | 2017-04-27 | Intellectual Ventures Hong Kong Limited | High bit rate covert channel in cloud storage systems |
| US10636065B2 (en) | 2016-03-09 | 2020-04-28 | Western Digital Technologies, Inc. | Data storage device, method and system, and control of data storage device based on writing operations and lifetime |
| CN108268313A (en) * | 2016-12-30 | 2018-07-10 | 杭州华为数字技术有限公司 | The method and apparatus of data processing |
| CN108900386B (en) * | 2018-08-10 | 2020-07-31 | 北京金山云网络技术有限公司 | Method and device for generating alarm information and electronic equipment |
| CN117369720B (en) * | 2023-09-11 | 2024-05-14 | 广州德久信息科技有限公司 | Data storage management method and device, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101374174A (en) * | 2007-08-20 | 2009-02-25 | 华为技术有限公司 | Method, apparatus and system for real time charging value added business |
| CN102694661A (en) * | 2012-06-26 | 2012-09-26 | 重庆昇通科技有限公司 | On-time charging service monitoring method based on charging server |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050104666A (en) * | 2004-04-29 | 2005-11-03 | 삼성전자주식회사 | Ethernet mac adaptation apparatus for real time service and its data transmitting method |
-
2013
- 2013-10-11 CN CN201310472390.8A patent/CN103533043B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101374174A (en) * | 2007-08-20 | 2009-02-25 | 华为技术有限公司 | Method, apparatus and system for real time charging value added business |
| CN102694661A (en) * | 2012-06-26 | 2012-09-26 | 重庆昇通科技有限公司 | On-time charging service monitoring method based on charging server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103533043A (en) | 2014-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103533043B (en) | A kind of charging method of the cloud stores service based on REST | |
| CN103064778B (en) | A kind of server performance method of testing, Apparatus and system | |
| US20190207869A1 (en) | Intelligent Placement within a Data Center | |
| CN102193832B (en) | Cloud computing resource scheduling method and applied system | |
| CN108322548A (en) | A kind of industrial process data analyzing platform based on cloud computing | |
| CN105893628A (en) | Real-time data collection system and method | |
| CN102281290A (en) | Emulation system and method for a PaaS (Platform-as-a-service) cloud platform | |
| US11423358B2 (en) | Electric power software development platform | |
| CN110110002A (en) | Big data virtual interactive interface system | |
| CN105528248A (en) | Crowd sensing incentive mechanisms for multitask cooperative application | |
| CN103795697A (en) | Network medium information release effect simulation method and system | |
| CN105760449A (en) | Multi-source heterogeneous data cloud pushing method | |
| CN103258248A (en) | Method, device and system for predicting microblog fashion trend | |
| CN109977273A (en) | A kind of topology drawing generating method, device, equipment and readable storage medium storing program for executing | |
| CN105335800A (en) | Method for forecasting electricity consumption of power consumers based on joint learning | |
| CN105894326A (en) | Sign-in reward distribution method and system | |
| CN104301354B (en) | A kind of method and system of the spatial class business datum GISization service based on cloud computing | |
| CN110532319A (en) | A kind of distribution meteorological data timing processing system | |
| CN105335537A (en) | Estimation method and system of network media information exposure in video album | |
| Santhanavanich et al. | Integration and visualization of heterogeneous sensor data and geospatial information | |
| Jang et al. | Interpolating spatial interaction data1 | |
| CN104283934A (en) | WEB service pushing method and device based on reliability prediction and server | |
| CN108804781A (en) | The geographical process near real-time analogy method that stream calculation is integrated with Sensor Network | |
| Barry et al. | Web services for water systems: The iWIDGET REST API | |
| CN106354433B (en) | The hot spot data method for digging and device of distributed memory storage system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160406 Termination date: 20161011 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |