AUTOMATED INFORMATION LOGGING AND VIEWING SYSTEM FOR HYDROCARBON RECOVERY OPERATIONS

• US 20160134693A1
• Filed: 07/24/2013
• Published: 05/12/2016
• Est. Priority Date: 07/24/2013
• Status: Active Grant

• Current Assignee: Halliburton Energy Services Incorporated (Halliburton Company)
• Original Assignee: Halliburton Energy Services Incorporated (Halliburton Company)
• Inventors: Li, Wanqiang
• Granted Patent: US 10,397,318 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

An example method for automated message logging may include receiving a message from a first client in communication with a server. The received message may be placed the in a first queue at the server. The received message may be processed at the server, and the processed received message may be placed in a second queue for broadcast to a second client in communication with the server. The example method may further include broadcasting the processed received message to the second client, and placing the processed received message in a third queue for persistent storage.

Claims

1. A method for automated message logging, comprising:

receiving a message from a first client in communication with a server;

placing the received message in a first queue at the server;

processing the received message at the server;

placing the processed received message in a second queue for broadcast to a second client in communication with the server;

broadcasting the processed received message to the second client; and

placing the processed received message in a third queue for persistent storage.

2. The method of claim 1, wherein the first client and the second client are registered with the server.

3. The method of claim 2, wherein the first client comprises a message generating client and the second client comprises a message receiving client.

4. The method of claim 1, further comprising receiving a heartbeat at the server from at least one of the first client and the second client.

5. The method of claim 1, wherein the message comprises at least one of well/run/descriptions;

a message code;

a message type; and

a message ID.

6. The method of claim 5, wherein processing the received message at the server comprises parsing the received message to determine at least one of the well/run/descriptions;

the message code;

the message type; and

the message ID.

7. The method of claim 1, wherein processing the received message at the server comprises retrieving the received message from the first queue when a first thread of the server is available

8. The method of claim 1, wherein broadcasting the processed received message to the second client comprises retrieving the processed received message from the second queue when the connection to the second client is available.

9. The method of claim 1, further comprising retrieving the processed received message from the third queue and storing the processed received message to a database coupled to the server.

10. The method of claim 1, wherein at least one of the first queue, the second queue, and the third queue comprises an asynchronous queue.

11. A system for automated message logging, comprising:

a first client;

a second client;

a server in communication with the first client and the second client, wherein the server comprises a processor and memory device coupled to the processor, and the memory device contains a set of instruction that, when executed by the processor, cause the processor to;

receive a message from the first client;

place the received message in a first queue at the server;

process the received message at the server;

place the processed received message in a second queue for broadcast to the second client;

broadcast the processed received message to the second client; and

place the processed received message in a third queue for persistent storage.

12. The system of claim 11, wherein the first client and the second client are registered with the server.

13. The system of claim 12, wherein the first client comprises a message generating client and the second client comprises a message receiving client.

14. The system of claim 11, wherein the set of instructions further cause the processor to receive a heartbeat at the server from at least one of the first client and the second client.

15. The system of claim 11, wherein the message comprises at least one of well/run/descriptions;

a message code;

a message type; and

a message ID.

16. The system of claim 15, wherein the set of instructions that cause the processor to process the received message at the server further cause the processor to parse the received message to determine at least one of the well/run/descriptions;

the message code;

the message type; and

the message ID.

17. The system of claim 11, wherein the set of instructions that cause the processor to process the received message at the server further cause the processor to retrieve the received message from the first queue when a first thread of the server is available.

18. The system of claim 11, wherein the set of instructions that cause the processor to broadcast the processed received message to the second client further cause the processor to retrieve the processed received message from the second queue when the connection to the second client is available.

19. The system of claim 11, wherein the set of instructions further cause the processor to retrieve the processed received message from the third queue and store the processed received message to a database coupled to the server.

20. The system of claim 11, wherein at least one of the first queue, the second queue, and the third queue comprises an asynchronous queue.