Blockchain micro-services framework

Patent metadata

Field	Value
Publication number	US-10447770-B2
Application number	US-201715607754-A
Country	US
Kind code	B2
Filing date	May 30, 2017
Priority date	May 30, 2017
Publication date	Oct 15, 2019
Grant date	Oct 15, 2019

Abstract

A network device receives a first application programming interface (API) call from an application. The first API call requests a micro-service of a blockchain-based technology. The blockchain-based technology includes use of a shared ledger among participating nodes in a distributed consensus network. The micro-service provides a function for the application. The network device sends, in response to the first API call, a second API call to one of the participating nodes. The second API call initiates a framework module of a multiple of framework modules in the participating nodes. The network device receives, from the one of the participating nodes, a response to the second API call, the response indicating consensus of the participating nodes. The network device generates, based on the response to the second API call, a reply to the first API call.

First claim

What is claimed is:

1. A method, comprising:
receiving, by a network device, a first application programming interface (API) call from an application, wherein the first API call requests a micro-service of a blockchain-based technology, wherein the blockchain-based technology includes use of a shared ledger among participating nodes in a distributed consensus network, and wherein the micro-service provides a function for the application;
identifying, by the network device, multiple different framework modules of a plurality of framework modules in the participating nodes, to accomplish different aspects of the micro-service;
sending, by the network device and in response to the first API call, second API calls to at least one of the participating nodes, wherein the second API calls initiate the multiple different framework modules to accomplish aspects of the micro-service;
receiving, by the network device and from the at least one of the participating nodes, responses to the second API calls, the responses indicating a consensus of the participating nodes; and
generating, by the network device and based on the responses to the second API calls, a reply to the first API call.

2. The method of claim 1 , further comprising:
sending, by the network device and to the application the reply to the first API call.

3. The method of claim 1 , further comprising:
receiving, by the network device, a third API call from the application, wherein the third API call requests a different micro-service of the blockchain-based technology.

4. The method of claim 1 , wherein the network device is one of the participating nodes in the distributed consensus network.

5. The method of claim 1 , further comprising:
sending, by the network device and in response to the first API call, a third API call to initiate a different micro-service.

6. The method of claim 1 , further comprising:
receiving, by the network device, a third API call from the application, wherein the third API call requests another instance of the micro-service.

7. The method of claim 1 , wherein the participating nodes in the distributed consensus network include nodes in a private domain and other nodes in a different private domain.

8. The method of claim 1 , wherein the framework module is a smart contract module that includes a read-only application binary interface (ABI) for use by the network device.

9. The method of claim 1 , further comprising:
storing, by the network device, an index of micro-services, including the micro-service.

10. The method of claim 1 , wherein the micro-service includes a collection of framework modules of the plurality of framework modules.

11. A network device in a distributed consensus network, comprising:
one or more memory devices for storing instructions; and
one or more processors configured to execute the instructions to:
receive a first application programming interface (API) call from an application, wherein the first API call requests a micro-service of a blockchain-based technology, wherein the blockchain-based technology includes use of a shared ledger among participating nodes in a distributed consensus network, and wherein the micro-service provides a function for the application;
identify, multiple different framework modules of a plurality of framework modules in the participating nodes, to accomplish different aspects of the micro-service;
send, in response to the first API call, second API calls to at least one of the participating nodes, wherein the second API calls initiate the multiple different framework modules to accomplish aspects of the micro-service;
receive, from the at least one of the participating nodes, responses to the second API calls, the responses indicating a consensus of the participating nodes; and
generate, based on the responses to the second API calls, a reply to the first API call.

12. The network device of claim 11 , wherein the one or more processors are further configured to execute the instructions to:
send to the application the reply to the first API call.

13. The network device of claim 11 , wherein the one or more processors are further configured to execute the instructions to:
receive a third API call from the application, wherein the third API call requests a different micro-service of the blockchain-based technology.

14. The network device of claim 11 , wherein the network device is one of the participating nodes in the distributed consensus network.

15. The network device of claim 11 , wherein the network device is not one of the participating nodes in the distributed consensus network.

16. The network device of claim 15 , wherein the one or more processors are further configured to execute the instructions to:
send, by the network device and in response to the first API call, a third API call to initiate a different micro-service.

17. A non-transitory computer-readable medium containing instructions executable by at least one processor, the computer-readable medium comprising one or more instructions to:
receive a first application programming interface (API) call from an application, wherein the first API call requests a micro-service of a blockchain-based technology, wherein the blockchain-based technology includes use of a shared ledger among participating nodes in a distributed consensus network, and wherein the micro-service provides a function for the application;
identify multiple different framework modules of a plurality of framework modules in the participating nodes, to accomplish different aspects of the micro-service;
send, in response to the first API call, second API calls to at least one of the participating nodes, wherein the second API calls initiate the multiple different framework modules to accomplish aspects of the micro-service;
receive, from the at least one of the participating nodes, responses to the second API calls, the responses indicating a consensus of the participating nodes; and
generate, based on the responses to the second API calls, a reply to the first API call.

18. The non-transitory computer-readable medium of claim 17 , further comprising one or more instructions to:
store an index of available micro-services, including the micro-service.

19. The non-transitory computer-readable medium of claim 17 , further comprising one or more instructions to:
receive a third API call from the application, wherein the third API call requests a different micro-service of the blockchain-based technology.

20. The non-transitory computer-readable medium of claim 17 , further comprising one or more instructions to:
sending, in response to the first API call, a third API call to initiate a different micro-service.

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Pacella Dante J
• Sardesai Ashish
• Tadayon Mani
• Mallesan Saravanan
• Mahey Sonit
• Sattler Lee E
• Josyula Venkata
• Mcmanus Jean M

Classifications

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• H04L67/10 Primary

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L2209/38

  Electricity · mapped topic

• H04L67/2838

  Electricity · mapped topic

• H04L67/567

  Integrating service provisioning from a plurality of service providers · CPC title