SYSTEM AND METHOD FOR BLOCKCHAIN-BASED NOTIFICATION

• US 20200145223A1
• Filed: 01/08/2020
• Published: 05/07/2020
• Est. Priority Date: 07/02/2019
• Status: Active Grant

• Current Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: YANG, Renhui, LIU, Jiawei, CHEN, Yuan, LIN, Yuqi
• Granted Patent: US 10,708,060 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/45 Structures or tools for the administration of authentication
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 9/0637 Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
• CPC Class Codes: H04L 9/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04L 9/0866 involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
• CPC Class Codes: H04L 9/0877 using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/3073 involving pairings, e.g. identity based encryption [IBE], bilinear mappings or bilinear pairings, e.g. Weil or Tate pairing
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/3271 using challenge-response
• CPC Class Codes: H04L 9/50 : using hash chains, e.g. blockchains or hash trees

Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for blockchain-based notification are provided. One of the methods includes: obtaining, from a computing device associated with a first decentralized identifier (DID), a query about event data; in response to the obtained query, searching a data store to obtain one or more notifications for event data associated with a second DID, wherein a DID document associated with the second DID comprises the first DID, and wherein the DID document is stored in a blockchain; and providing the one or more notifications for the computing device associated with the first DID.

Claims

1. A computer-implemented method for blockchain-based notification, comprising:

obtaining, from a computing device associated with a first decentralized identifier (DID), a query about event data;

in response to the obtained query, searching a data store to obtain one or more notifications for event data associated with a second DID, wherein a DID document associated with the second DID comprises the first DID, and wherein the DID document is stored in a blockchain; and

providing the one or more notifications for the computing device associated with the first DID.

2. The method of claim 1, wherein:

the DID document comprises a parameter indicating a creator of the second DID; and

the parameter comprises the first DID.

3. The method of claim 1, wherein:

the DID document comprises a parameter indicating a controller of the second DID; and

the parameter comprises the first DID.

4. The method of claim 1, wherein:

the event data is associated with a verifiable claim; and

a representation of the verifiable claim is stored in the blockchain.

5. The method of claim 1, wherein the event data associated with the second DID comprises one or more of the following:

a registration of the second DID in the blockchain;

an update to the DID document in the blockchain;

an issuance of a first verifiable claim associated with the second DID, wherein the second DID corresponds to an issuer of the first verifiable claim; and

an issuance of a second verifiable claim associated with the second DID, wherein the second DID corresponds to a subject of the second verifiable claim.

6. The method of claim 1, before obtaining the query, further comprising:

obtaining a plurality of notifications from one or more message queues; and

storing the plurality of notifications in the data store in association with information of corresponding DIDs and corresponding blockchain heights in the blockchain, wherein the plurality of notifications comprise the one or more notifications for the event data associated with the second DID.

7. The method of claim 6, after obtaining the plurality of notifications, further comprising:

filtering the plurality of notifications to remove one or more unauthorized notifications.

8. The method of claim 6, after obtaining the plurality of notifications, further comprising:

categorizing the plurality of notifications based on one or more of the following notification parameters;

event type, DID, DID creator, DID controller, notification recipient, verifiable claim issuer, and verifiable claim subject.

9. The method of claim 1, wherein searching the data store to obtain the one or more notifications for the event data associated with the second DID comprises:

searching the data store based on a current starting height of the blockchain to obtain the one or more notifications for the event data associated with the second DID.

10. The method of claim 9, wherein:

searching the data store based on the current starting height of the blockchain to obtain the one or more notifications for the event data associated with the second DID comprises;

searching from the current starting height of the blockchain to a current ending height of the blockchain for the one or more notifications associated with the event data; and

the method further comprises providing the current ending height of the blockchain for one or more of the following;

the computing device associated with the first DID and another computing device associated with the second DID.

11. The method of claim 9, wherein:

the query comprises the current starting height of the blockchain; and

the current starting height of the blockchain comprises an offset from a previous ending height of the blockchain of a previous search.

12. The method of claim 9, wherein:

the query comprises the current starting height of the blockchain; and

the current starting height of the blockchain is a previous ending height of the blockchain of a previous search.

13. A system for blockchain-based notification, the system comprising one or more processors and one or more non-transitory computer-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system to perform operations comprising:

obtaining, from a computing device associated with a first decentralized identifier (DID), a query about event data;

in response to the obtained query, searching a data store to obtain one or more notifications for event data associated with a second DID, wherein a DID document associated with the second DID comprises the first DID, and wherein the DID document is stored in a blockchain; and

providing the one or more notifications for the computing device associated with the first DID.

14. The system of claim 13, wherein:

the DID document comprises a parameter indicating a creator of the second DID; and

the parameter comprises the first DID.

15. The system of claim 13, wherein:

the DID document comprises a parameter indicating a controller of the second DID; and

the parameter comprises the first DID.

16. The system of claim 13, wherein:

the event data is associated with a verifiable claim; and

a representation of the verifiable claim is stored in the blockchain.

17. A non-transitory computer-readable storage medium for blockchain-based notification, the storage medium configured with instructions executable by one or more processors to cause the one or more processors to perform operations comprising:

obtaining, from a computing device associated with a first decentralized identifier (DID), a query about event data;

in response to the obtained query, searching a data store to obtain one or more notifications for event data associated with a second DID, wherein a DID document associated with the second DID comprises the first DID, and wherein the DID document is stored in a blockchain; and

providing the one or more notifications for the computing device associated with the first DID.

18. The storage medium of claim 17, wherein:

the DID document comprises a parameter indicating a creator of the second DID; and

the parameter comprises the first DID.

19. The storage medium of claim 17, wherein:

the DID document comprises a parameter indicating a controller of the second DID; and

the parameter comprises the first DID.

20. The storage medium of claim 17, wherein:

the event data is associated with a verifiable claim; and

a representation of the verifiable claim is stored in the blockchain.