Real-time data monitoring based on data push

• US 8,656,013 B2
• Filed: 06/14/2011
• Issued: 02/18/2014
• Est. Priority Date: 06/14/2011
• Status: Active Grant

• Current Assignee: Sony Interactive Entertainment LLC (Sony Group Corp.)
• Original Assignee: Sony Computer Entertainment America LLC (Sony Group Corp.)
• Inventors: He, Shawn
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US13/160,348
• Publication Number:
  US 20120324093A1
• Time in Patent Office: 980 Days
• Field of Search: 709/224
• US Class Current: 709/224
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3065 Monitoring arrangements determined by the means or processing involved in reporting the monitored data error or fault reporting or logging G06F11/0766
• CPC Class Codes: G06F 11/3093 Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: H04L 69/02 Protocol performance

Abstract

Data monitoring including: establishing a real-time connection between at least two processing entities; defining transfer preferences for data and metrics to be sent for monitoring; and sending the data and metrics from at least one sending entity to a collecting entity of the at least two processing entities using a data push process, wherein the data push process is based on the transfer preferences defined in advance for the data and metrics.

Claims

1. A data monitoring method, comprising:

establishing a real-time connection between at least two processing entities comprising at least one sending entity and a monitoring entity;

defining transfer preferences for data and metrics to be sent for the data monitoring after the real-time connection between the at least two processing entities has been established,

wherein the transfer preferences require periodic data push by the at least one sending entity; and

sending the data and metrics from the at least one sending entity to the monitoring entity using the periodic data push.

2. The method of claim 1, further comprising

performing mutual authentication between the at least one sending entity and the monitoring entity.

3. The method of claim 1, wherein the at least one sending entity comprises at least one client.

4. The method of claim 3, wherein the at least one client comprises at least one local application server.

5. The method of claim 1, wherein the monitoring entity comprises a server.

6. The method of claim 5, wherein the server comprises a data repository.

7. The method of claim 1, wherein establishing a real-time connection between at least two processing entities comprises

initiating a handshaking procedure to enable servers and clients to negotiate a stateful connection.

8. The method of claim 1, wherein defining transfer preferences for data and metrics to be sent for monitoring comprises

negotiating which parameters to use to establish the connection between the at least two processing entities.

9. A data monitoring system, comprising:

at least one sending entity;

a monitoring entity configured to establish a real-time connection with the at least one sending entity and define transfer preferences for data and metrics to be sent from the at least one sending entity to the monitoring entity for monitoring,

wherein the data and metrics are sent from the at least one sending entity to the monitoring entity using a data push process,

wherein the transfer preferences require periodic data push by the at least one sending entity to the monitoring entity defined in advance for the data and metrics.

10. The system of claim 9, wherein the at least one sending entity comprises at least one client.

11. The system of claim 10, wherein the at least one client comprises at least one local application server.

12. The system of claim 9, wherein the monitoring entity comprises a server.

13. The system of claim 12, wherein the server comprises a data repository.

14. A non-transitory computer-readable storage medium storing a computer program, the computer program comprising executable instructions that cause a computer to perform data monitoring, the computer program comprising executable instructions that cause a computer to:

establish a real-time connection between at least two processing entities comprising at least one sending entity and a monitoring entity;

define transfer preferences for data and metrics to be sent for the data monitoring after the real-time connection between the at least two processing entities has been established,

wherein the transfer preferences require periodic data push by the at least one sending entity; and

send the data and metrics from the at least one sending entity to the monitoring entity using the periodic data push.

15. The storage medium of claim 14, wherein executable instructions that cause a computer to establish a real-time connection between at least two processing entities comprise executable instructions that cause a computer to

initiate a handshaking procedure to enable servers and clients to negotiate a stateful connection.

16. The storage medium of claim 14, wherein executable instructions that cause a computer to define preferences for data and metrics to be sent for monitoring comprise executable instructions that cause a computer to

negotiate which parameters to use to establish the connection between the at least two processing entities.