Integrated distribution management system channel adapter

• US 8,478,714 B2
• Filed: 01/20/2011
• Issued: 07/02/2013
• Est. Priority Date: 01/20/2011
• Status: Active Grant

• Current Assignee: Southern Company Services, Inc. (Southern Company)
• Original Assignee: Southern Company Services, Inc. (Southern Company)
• Inventors: Floyd, Gregory Ray, Hubbartt, Steven Kirk
• Primary Examiner(s): LE, UYEN T
• Application Number:
  US13/010,309
• Publication Number:
  US 20120191665A1
• Time in Patent Office: 894 Days
• Field of Search: None
• US Class Current: 707/602
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Disclosed are various embodiments for communicating with an integrated distribution management system (IDMS). An IDMS often employs a communications protocol that is incompatible with a service oriented architecture. Accordingly, embodiments of the disclosure can allow utility computing systems in a service oriented architecture or in a messaging based environment to communicate with an IDMS.

Claims

1. A method, comprising the steps of:

establishing, in at least one computing device, a session in a transmission control protocol (TCP) with an integrated distribution management system (IDMS) by opening a socket between the at least one computing device and the IDMS and communicating with the IDMS via the socket, the session having a protocol that is incompatible with an asynchronous messaging framework employed in a service oriented architecture;

receiving, in the at least one computing device, a request in the session from the IDMS to transmit a message to at least one recipient system;

translating the message into a message format compatible with an enterprise service bus and a table in a message history database, the message history database and the enterprise system bus being configured to communicate via the asynchronous messaging framework employed in the service oriented architecture;

publishing the message in a message history database and an enterprise system bus;

transmitting at least one of a message acknowledgement or an error message to the IDMS in the session;

creating an entry in the message history database corresponding to the at least one of the acknowledgement or the error message;

marking the entry as one of delivered or undelivered in the message history database; and

terminating the session with the IDMS.

2. The method of claim 1, wherein the step of establishing the session further comprises the steps of:

opening a socket between the at least one computing device and the IDMS; and

communicating with the IDMS via the socket.

3. The method of claim 1, wherein the message further comprises a request to receive data from the at least one recipient system, and the method further comprising the steps of:

publishing the request in the message format in the message history database and the enterprise service bus, wherein the request in the message format identifies the at least one recipient system; and

polling at least one of the message history database and the enterprise service for a response to the request; and

transmitting at least one of a request response and an error message to the IDMS in the session, wherein the request response is translated to an IDMS message format.

4. The method of claim 1, wherein the at least one recipient system further comprises at least one of a customer information system, a voice system, a workforce management system, or an advanced metering infrastructure head-end.

5. The method of claim 1, wherein the at least one recipient system is at least one advanced metering infrastructure utility meter.

6. The method of claim 1, wherein the message further comprises a request to receive data from an advanced metering infrastructure (AMI) utility metering device, and the method further comprising the steps of:

publishing the request in the message format in at least one of the message history database and the enterprise service bus, wherein the request in the message format designates the AMI utility metering device as a recipient of the request; and

polling at least one of the message history database and the enterprise service for a response to the request; and

transmitting at least one of a ping response and an error message to the IDMS in the session, wherein the response to the request is translated into an IDMS message format.

7. A system, comprising:

at least one computing device;

an integrated distribution management system (IDMS) channel adapter executable in the at least one computing device, comprising

logic that establishes a session in a transmission control protocol (TCP) with at least one integrated distribution management system (IDMS) by opening a socket between the at least one computing device and the IDMS and communicating with the IDMS via the socket, the session having a protocol that is incompatible with an asynchronous messaging framework employed in a service oriented architecture;

logic that receives a request in the session from the IDMS to transmit a message to at least one recipient system;

logic that translates the message into a message format compatible with an enterprise service bus and a table in a message history database, the message history database and the enterprise system bus being configured to communicate via the asynchronous messaging framework employed in the service oriented architecture;

logic that publishes the message in a message history database and an enterprise system bus (ESB);

logic that transmits at least one of a message acknowledgement or an error message to the IDMS in the session;

logic that creates an entry in the message history database corresponding to the at least one of the acknowledgement or the error message;

logic that marks the entry as one of delivered or undelivered in the message history database; and

logic that terminates the session with the IDMS.

8. The system of claim 7, wherein the logic that establishes the session further comprises:

logic that opens a socket between the at least one computing device and the IDMS; and

logic that communicates with the IDMS via the socket.

9. The system of claim 7, wherein the IDMS channel adapter further comprises logic that translates the message into a message format compatible with at least one of the enterprise service bus and a table in the message history database.

10. The system of claim 9, wherein the message further comprises a request to receive data from the at least one recipient system, and the IDMS channel adapter further comprises:

logic that publishes the request in the message format in at least one of the message history database and the enterprise service bus, wherein the request in the message format designates the at least one recipient system; and

logic that polls at least one of the message history database and the enterprise service for a response to the request; and

logic that transmits at least one of a request response and an error message to the IDMS in the session, wherein the request response is translated to an IDMS message format.

11. The system of claim 7, wherein the at least one recipient system further comprises at least one of a customer information system, a voice system, a workforce management system, or an advanced metering infrastructure head-end.

12. The system of claim 7, wherein the at least one recipient system is at least one advanced metering infrastructure utility meter.

13. The system of claim 7, wherein the IDMS channel adapter further comprises:

logic that polls the message history database for an IDMS destined message from the at least one recipient system; and

logic that transmits the IDMS destined message to the IDMS in the session.

14. The system of claim 7, wherein the message further comprises a request to receive data from an advanced metering infrastructure (AMI) utility metering device, and the IDMS channel adapter further comprises:

logic that publishes the request in the message format in at least one of the message history database and the enterprise service bus, wherein the request in the message format designates the AMI utility metering device as a recipient of the request; and

logic that polls at least one of the message history database and the enterprise service for a response to the request; and

logic that transmits at least one of a ping response and an error message to the IDMS in the session, wherein the response to the request is translated into an IDMS message format.