CALCULATION ENGINE AND CALCULATION PROVIDERS

• US 20120078944A1
• Filed: 09/28/2010
• Published: 03/29/2012
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Schneider Electric USA, Inc. (Schneider Electric SE)
• Original Assignee: Schneider Electric USA, Inc. (Schneider Electric SE)
• Inventors: Yeo, Jeffrey W., Lloyd, Chad Andrew, McClanahan, Jason D., Dodson, John Jeffrey, Little, Marcus E., Zheng, Yixiong, Wall, Theresa K., Wimsatt, Coni Christine
• Granted Patent: US 8,984,034 B2
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G05B 23/027 Alarm generation, e.g. communication protocol; Forms of alarm

Abstract

A method of acquiring data and performing calculations on the data using a provider service. A provider ticket service (PTS) receives tickets from one or more clients. Each ticket includes a calculation identifier and a payload. The calculation identifier identifies a calculation to be performed using information in the payload. The PTS associates a unique ticket identifier with each ticket. A ticket manager submits a selected ticket from the PTS to a provider host service (PHS), which determines which provider is to perform the calculation identified by the selected ticket by inspecting provider identification information in the selected ticket. The PHS launches a provider host thread (PHT) that invokes the provider determined to perform the calculation identified by the calculation identifier of the selected ticket. The provider performs the calculation and returns its result to the PHS, which passes the result back to the PTS, which returns the result to the requesting client.

Claims

1. A method of acquiring data and performing calculations on the data using a provider service, comprising:

receiving, at a provider ticket service, a plurality of tickets from one or more clients, each of the tickets including a calculation identifier and a payload, the calculation identifier identifying a calculation to be performed using at least information indicated in the payload of the ticket;

for each of the tickets received at the provider ticket service, associating a unique ticket identifier with each of the corresponding tickets;

a ticket manager submitting the selected ticket from the provider ticket service to a provider host service;

determining which one or more of a plurality of providers is to perform the calculation identified by the calculation identifier of the selected ticket;

the provider host service launching at least one provider host thread that invokes or instantiates the one or more providers determined to perform the calculation identified by the calculation identifier of the selected ticket;

receiving at the provider ticket service from the provider host service a result of the calculation carried out by the invoked one or more providers; and

returning the result to the requesting client associated with the selected ticket.

2. The method of claim 1, further comprising, prior to performing the calculation requested by the selected ticket, determining whether the calculation requested by the selected ticket has been performed already, and, if so, retrieving the previously calculated result and returning the previously calculated result as the result to be returned to the requesting client associated with the selected ticket.

3. The method of claim 2, further comprising storing the previously calculated result in a data store of the provider ticket service.

4. The method of claim 1, further comprising, prior to performing the calculation requested by the selected ticket, determining whether another of the providers is in the process of performing the calculation requested by the selected ticket, and if so, waiting for the other provider to perform the calculation and provide the result and returning the result from the other provider as the result to be returned to the requesting client associated with the selected ticket.

5. The method of claim 1, further comprising:

determining whether to store the result based on at least one criterion; and

responsive to the at least one criterion being satisfied, storing the result in a data store of the provider ticket service.

6. The method of claim 5, wherein the at least one criterion includes whether the calculation requested by the selected ticket has been requested by at least one other of the clients.

7. The method of claim 5, wherein the at least one criterion includes a frequency with which the result is expected to be requested or has been requested.

8. The method of claim 5, wherein the at least one criterion is based on how frequently the calculation requested by the selected tickets is requested by other clients of the one or more clients.

9. The method of claim 5, wherein the at least one criterion includes whether data used to perform the calculation is within a predetermined time period.

10. The method of claim 1, further comprising:

receiving, from the client that provided the first ticket, a request for the result using the ticket identifier associated with the first ticket; and

responsive to receiving the request from the requesting client, querying the data store for the result.

11. The method of claim 1, further comprising inserting into the selected ticket a provider identification that identifies which of the one or more of providers is to be invoked for carrying out the calculation identified by the calculation identifier of the selected ticket.

12. The method of claim 1, further comprising communicating to the client that communicated the selected ticket the ticket identifier associated with the selected ticket.

13. The method of claim 12 further comprising:

receiving from the one or more clients a request for a status of the selected ticket;

responsive to receiving the request for the status of the selected ticket, the provider ticket service querying a ticket status table for the status of the selected ticket; and

the provider ticket service communicating, to the client that requested the status of the selected ticket, the status of the selected ticket, the status including an indication of whether processing of the selected ticket is pending or in-progress, and if the status of the selected ticket is in-progress, the ticket provider service further communicating an indication as to how much processing has been completed or remains to be completed to produce the result.

14. The method of claim 1, wherein the invoked provider carries out the calculation to be performed using input data hosted locally by the provider host service or externally to the provider host service based at least in further part on the local or external data.

15. The method of claim 1, further comprising:

the invoked provider requesting the information indicated in the payload of the ticket from a data store hosted by the provider ticket service or from a data service hosted external to the provider host service and to the provider ticket service; and

responsive to the invoked provider requesting the information, the invoked provider receiving input data from the data store or external data service and using the received input data to perform the calculation requested by the selected ticket.

16. The method of claim 1, further comprising:

storing, using a ticket manager, the tickets in a ticket store according to a queue;

identifying a status of each of the tickets and storing an indication of the status of each of the tickets, including the selected ticket, in a ticket status table;

increasing a pending ticket counter each time the status of selected ones of the tickets is identified as pending;

querying the ticket store for a first one of the tickets at the front of the queue; and

identifying from the first ticket at least a provider to be invoked from the plurality of providers for carrying out the calculation indicated by the calculation identifier of the first ticket.

17. The method of claim 16, further comprising, responsive to receiving the selected ticket at the provider ticket service, updating the status of the selected ticket in the ticket status table from pending to in-progress.

18. The method of claim 17, further comprising:

storing the result in a data store of the provider ticket service; and

responsive to storing the result in the data store of the provider ticket service, updating the status of the selected ticket in the ticket status table from in-progress to completed.

19. The method of claim 16, wherein each of at least some of the tickets further includes a priority field indicating a priority order of invocation relative to the other tickets, the first ticket including a higher priority order in the corresponding priority field compared to at least some of the other tickets.

20. The method of claim 16, further comprising, responsive to returning the result to the client associated with the selected ticket, deleting the selected ticket from the ticket store and deleting the status of the selected ticket from the ticket status table.

21. The method of claim 1, further comprising:

receiving, at the provider ticket service, a request to cancel one of the tickets;

the provider ticket service determining which of the providers to notify based on provider identification information in the ticket to be canceled;

notifying the provider determined to be associated with the ticket to be canceled that the ticket to be canceled has received the request to cancel; and

canceling the ticket to be canceled.

22. The method of claim 1, further comprising, responsive to receiving the plurality of tickets at the provider ticket service, formatting each of the tickets by an extensible markup language (XML) or into a JavaScript Object Notation (JSON) format.

23. The method of claim 1, wherein the payload includes a set of inputs or parameters needed to perform the calculation associated with the calculation identifier.

24. The method of claim 23, wherein the set of inputs or parameters includes a source identification indicating a source of at least some of the data needed to perform the calculation associated with the calculation identifier.

25. The method of claim 1, further comprising:

the invoked provider associated with the selected ticket carrying out the calculation to be performed as indicated by the calculation identifier of the selected ticket based at least in part on the payload of the selected ticket; and

responsive to the carrying out the calculation, the invoked provider outputting the result of the calculation associated with the selected ticket.

26. The method of claim 1, further comprising the provider host service further hosting the one or more providers determined to perform the calculation identified by the calculation identifier of the selected ticket.

27. The method of claim 1, further comprising the provider host service notifying the provider ticket service how many provider host threads are available to perform calculations requested by the tickets.

28. The method of claim 1, wherein the launching the at least one provider host thread includes invoking a plurality of providers and chaining the plurality of providers together, some of the chained providers performing an intermediate calculation and producing an intermediate result to produce the result as the result to be returned to the requesting client associated with the selected ticket.

29. The method of claim 28, further comprising reading a configuration file to determine how to chain together the chained providers, the configuration file indicating at least a sequence order of processing each of the chained providers.

30. The method of claim 28, further comprising storing the intermediate result on a data store that is hosted local to the provider ticket service.

31. The method of claim 1, wherein the selected ticket includes a source identification, a topic identification, and a date or a date range, the source identification identifying a source of data used to perform the calculation identified by the calculation identifier of the selected ticket, the topic information identifying topical information about the data from the source identification, and the date or date range corresponding to a date or date range of the topical data from the source of the data.

32. The method of claim 31, wherein the selected ticket further includes a dependency identification associated with the source identification and the topic identification, the dependency identification having a unique value relative to dependency identifications associated with every other one of the tickets to permit multiple instances of the same source-topic combinations having the same source identification and the same topic identification.

33. The method of claim 32, wherein the dependency identification identifies one of a plurality of time-of-use (TOU) schedules, each of the TOU schedules being associated with the same source identification and the same topic identification, the calculation determining a time-of-use (TOU) pricing or an energy usage based on the TOU schedule identified by the dependency identification.

34. The method of claim 1, wherein the information includes values indicative of or calculated from a characteristic of a utility that is measured by one or more intelligent electronic devices in a utility system.

35. The method of claim 34, wherein the utility is water, air, gas, electricity, or steam.

36. The method of claim 34, wherein the utility is electricity and the characteristic includes current or voltage.

37. The method of claim 36, wherein the values calculated from the current or voltage include energy.

38. The method of claim 1, wherein the provider ticket service is hosted on a computing machine and the provider host service is hosted on the computing machine.

39. The method of claim 1, wherein the provider host service includes a plurality of provider host services, the provider ticket service being hosted on a computing machine and at least some of the plurality of provider host services being hosted on other computing machines communicatively coupled to the computing machine that hosts the provider ticket service.

40. The method of claim 1, further comprising associating a Uniform Resource Identifier with the provider host service.