DEMAND RESPONSE EVENT DISSEMINATION SYSTEM AND METHOD

• US 20150052188A1
• Filed: 08/16/2013
• Published: 02/19/2015
• Est. Priority Date: 08/16/2013
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: HERBERG, Ulrich, JETCHEVA, Jorjeta G., MASHIMA, Daisuke
• Granted Patent: US 10,432,753 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 50/06 Energy or water supply
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks

Abstract

A method may include receiving peer data describing a set of peer clients associated with a demand response application server and describing how the peer clients communicate with one another. The peer data may be configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients. The method may also include receiving announcement data describing an event specified by the demand response application server and determining event response data responsive to the announcement data. The method may also include identifying, from the set of peer clients specified by the demand response application server, a set of recipient peer clients to receive the event response data.

Claims

1. A method comprising:

determining peer data configured to reduce bandwidth requirements for a demand response application server, the peer data describing a set of peer clients associated with the demand response application server and how the peer clients communicate with one another, the peer data configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients in the set;

generating announcement data describing an event for the set of peer clients; and

receiving, from the subset of peer clients specified by the peer data, event response data associated with one or more of the peer clients and responsive to the event described by the announcement data.

2. The method of claim 1, wherein the peer data is encrypted using a public key infrastructure to allow only the demand response application server to define peers.

3. The method of claim 1, wherein the announcement data is encrypted using a public key infrastructure to allow only the demand response application server to create a new event.

4. The method of claim 3, wherein the announcement data is encrypted using symmetric-key cryptography.

5. The method of claim 1, wherein a response described in the event response data includes one of:

an acknowledgement of the event indicating that a client from the set of peer clients is scheduled to participate in the event; and

an opt-out indicating that the client from the set of peer clients is not scheduled to participate in the event.

6. The method of claim 1, wherein the event response data includes a report describing telemetry and historical load for a client from the set of peer clients.

7. The method of claim 1 further comprising generating server beacon data to be transmitted by the demand response application server, the server beacon data encrypted using a public key so that the peer clients only acts on server beacon data generated by the demand response application server, the server beacon parameters configured to perform one of specifying how frequently the peer clients transmit beacon data to one another and changing how the peer clients are associated with one another.

8. The method of claim 1 further comprising:

determining whether a timeout period has elapsed since the announcement data was transmitted;

determining that event response data has not been received from a client included in the set of peer clients; and

directly communicating with the client to request event response data for the client.

9. The method of claim 8, further comprising receiving, from the client, a request for a different timeout period.

10. A method comprising:

receiving peer data describing a set of peer clients associated with a demand response application server and describing how the peer clients communicate with one another, the peer data configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients;

receiving announcement data describing an event specified by the demand response application server;

determining event response data responsive to the announcement data; and

identifying, from the set of peer clients specified by the demand response application server, a set of recipient peer clients to receive the event response data.

11. The method of claim 10, wherein the set of recipient peer clients includes at least two clients from the set of peer clients so that a redundancy of the event response data exists among the set of peer clients.

12. The method of claim 10, wherein the set of recipient peer clients is determined based on which of the peer clients included in the set of peer clients has a lowest hop count relative to the demand response application server.

13. The method of claim 10, wherein the peer data is received by a client included in the set of peer clients and the set of recipient peer clients does not include each of the peer clients associated with the client.

14. The method of claim 10, wherein the event response data is encrypted using a public key infrastructure to allow the demand response application server to determine that the event response data is authentic.

15. The method of claim 10 further comprising:

receiving additional event response data from one or more clients included in the set of peer clients;

determining the presence of duplicate event response data; and

deleting the duplicate event response data.

16. The method of claim 10 further comprising:

receiving additional event response data from one or more clients included in the set of peer clients; and

aggregating the event response data so that the demand response application server receives a reduced number of data packets.

17. A method comprising:

receiving peer data describing a set of peer clients associated with a demand response application server and how the peer clients communicate with one another, the peer data configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients in the set of peer clients;

receiving announcement data describing a set of events specified by the demand response application server;

receiving, by a first client included in the set of peer clients, beacon data describing events received by a second client included in the set of peer clients; and

determining that the beacon data describes an event not included in the set of events described by the announcement data.

18. The method of claim 17, further comprising determining which client from the set of peer clients is in possession of the event not included in the set of events described by the announcement data.

19. The method of claim 18, wherein the beacon data includes a flag including data that is used for determining which client from the set of peer clients is in possession of the event not included in the set of events described by the announcement data.

20. The method of claim 17, wherein the beacon data is encrypted using a public key to allow the first client to determine that the beacon data is authentic.