PATENT CLAIM ANALYSIS

Application Number: 16003214
Application Type: Utility
Filing Date: 2018-06
Publication Date: 2019-12
Patent Classification: ["719", "318000"]

Abstract:
Domain and/or event type-specific consensus processes for distributed ledger are provided. A consensus request is received by a core consensus engine. The consensus request corresponds to an event, the event (i) corresponds to a domain and (ii) has a type, and the consensus request comprises information corresponding to the event. Information corresponding to the event and the type are provided to the processing manager corresponding to the domain. The processing manager identifies a set of processing objects based on the type. The processing manager calls at least one processing object of the set via a corresponding interface and provides information corresponding to the event to the called processing object. The processing object is executed to generate a corresponding object result. The processing manager generates an aggregate result based on the object results. The core consensus engine determines a consensus response based at least in part on the aggregate result.

Claim (Index 19):
A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code portions stored therein, the computer-executable program code portions comprising program code instructions corresponding (a) a core consensus engine and (b) a domain specific engine, the program code instructions corresponding to the domain specific engine comprising (i) program code instructions corresponding to a processing manager and (ii) one or more pluggable modules corresponding to one or more processing objects, the computer program code instructions, when executed by a processor of a node computing entity storing a distributed ledger, are configured to:\n receive a consensus request by the core consensus engine, wherein (a) the consensus request corresponds to an event, (b) the event (i) corresponds to a domain and (ii) has a type, and (c) the consensus request comprises information corresponding to the event; provide at least a portion of the information corresponding to the event and the type to the at least one processing manager, the at least one processing manager corresponding to the domain; identify a set of one or more processing objects by the processing manager based on the type; call, by the processing manager, at least one processing object of the set of one or more processing objects via a corresponding interface and provide at least a portion of the information corresponding to the event to the at least one processing object; execute the at least one processing object to generate a corresponding at least one object result; aggregate the at least one object result by the processing manager to generate an aggregate result; determine, by the core consensus engine, a consensus response based at least in part on the aggregate result; and cause, by the core consensus engine, a communications interface of the node computing entity to provide the consensus response, to at least one of a plurality of node computing entities storing the distributed ledger.

Metadata:
- Claim Count in Document: 50.0
- Percentile: 94.0
- Lexical Diversity: 2.52308
- Patent Class: 719.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['15728934', '15899914', '14632499', '15139217', '15869752']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.4968592628627817
- 35 USC 102 Novelty (BERT): 0.4929646412410862
- Combined Prediction Score: 0.4964698007006122
- Mean Citation Score: 194.794428
- Max Citation Score: 234.12495
- Similarity Product: 176.17937319016457

Labels:
- Claim Label 101: 1
- Claim Label 102: 0
- Claim Label 103: 1
- Claim Label 112: 1
- Combined Label: 0
- Label 101 Adjusted: 1

Dataset: test