US 11,716,201 B2
System and method for maintaining usage records in a shared computing environment
Krzysztof Fabjański, Bielsko-Biala (PL)
Assigned to ASSA ABLOY AB, Stockholm (SE)
Appl. No. 17/57,442
Filed by ASSA ABLOY AB, Stockholm (SE)
PCT Filed May 17, 2019, PCT No. PCT/EP2019/062811
§ 371(c)(1), (2) Date Nov. 20, 2020,
PCT Pub. No. WO2019/224118, PCT Pub. Date Nov. 28, 2019.
Claims priority of provisional application 62/674,393, filed on May 21, 2018.
Prior Publication US 2021/0314163 A1, Oct. 7, 2021
Int. Cl. H04L 29/06 (2006.01); H04L 9/32 (2006.01); G06F 16/23 (2019.01); G06F 9/54 (2006.01); G06F 21/64 (2013.01); H04L 9/40 (2022.01); H04L 9/00 (2022.01)
CPC H04L 9/3239 (2013.01) [G06F 9/547 (2013.01); G06F 16/2379 (2019.01); G06F 21/64 (2013.01); H04L 9/3247 (2013.01); H04L 63/0457 (2013.01); H04L 9/50 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A method for maintaining a log of events in a shared computing environment, the method comprising:
receiving, at an audit trail adapter provided on an audit server, one or more raw data streams from the shared computing environment that include transactions conducted in the shared computing environment by a first entity, a second entity that is different from the first entity, and a third entity that is different from the first entity and the second entity;
creating, by the audit trail adapter, based on the received one or more raw data streams, a first blockchain entry for a first transaction conducted in the shared computing environment for the first entity;
creating, by the audit trail adapter, based on the received one or more raw data streams, a second blockchain entry for a second transaction conducted in the shared computing environment for the second entity, wherein the second blockchain entry includes a signature that points to the first blockchain entry;
creating, by the audit trail adapter, based on the received one or more raw data streams, a third blockchain entry for a third transaction conducted in the shared computing environment for the third entity, wherein the third blockchain entry includes a signature that points to the second blockchain entry; and
causing the first, second, and third blockchain entries to be written to a common blockchain data structure in a database that is made accessible to the first entity, the second entity, and the third entity;
wherein the third entity is capable of determining that the second blockchain entry exists in the common blockchain data structure but is unable to access any payload in the second blockchain entry, and wherein the third entity is incapable of determining that the first blockchain entry exists in the common blockchain data structure because the third blockchain entry does not point to the first blockchain entry.