System and method for remote monitoring of API performance and user behavior associated with user interface

• US 10,110,688 B2
• Filed: 03/17/2016
• Issued: 10/23/2018
• Est. Priority Date: 03/20/2015
• Status: Active Grant

• Current Assignee: Sony Interactive Entertainment LLC (Sony Group Corp.)
• Original Assignee: Sony Interactive Entertainment LLC (Sony Group Corp.)
• Inventors: Zarn, Miles
• Primary Examiner(s): Won, Michael Y
• Application Number:
  US15/073,128
• Publication Number:
  US 20160277264A1
• Time in Patent Office: 950 Days
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

Various aspects of a system and a method to remotely monitor API performance and user behavior associated with a user interface (UI) are disclosed herein. In accordance with an embodiment, the system includes a server that includes registration of a metric associated with performance of an application program interface (API) and/or the UI associated with a client device. The metric may be registered as a unique namespace information value. A numeric value is assigned to the registered metric to associate the assigned numeric value with the registered metric. The assigned numeric value associated with the registered metric is synchronized at the client device and the server. The performance of the API and/or the UI associated with the client device is determined based on receipt of the assigned numeric value from the client device.

Claims

1. A system for remote monitoring, said system comprising:

circuitry in a server communicatively coupled to a client device, said circuitry configured to;

register a metric associated with performance of one of an application program interface (API) or at least one user interface (UI) associated with said client device, as a unique namespace information value;

assign a numeric value to said registered metric to associate said assigned numeric value with said metric registered as said unique namespace information value;

synchronize said assigned numeric value associated with said registered metric at said client device and said server, wherein said performance of one of said API or said at least one UI associated with said client device is determined based on receipt of said assigned numeric value from said client device;

generate a visualization of a navigation flow of said at least one UI in a session; and

identify a source of traffic to said at least one UI.

2. The system according to claim 1, wherein said circuitry is further configured to receive a plurality of numeric values that includes said assigned numeric value from said client device, wherein said plurality of numeric values corresponds to at least one of:

a transport protocol version, a type of data packet, a session identifier (ID), a session sequence number, a timestamp of a first metric, an application build version value, a client device ID, a current metric numeric value, a previous metric numeric value, a latency value, or a time offset value from said timestamp of said first metric.

3. The system according to claim 1, wherein said server is at least one of:

a namespace server, a hypertext transfer protocol (HTTP) web server, an application server, a duster-computing device, or a database server.

4. The system according to claim 1, wherein said circuitry is further configured to determine a latency of a first load of said registered metric in said client device in said session, based on a plurality of numeric values received from said client device.

5. The system according to claim 1, wherein said circuitry is further configured to determine an average latency of a first load of each registered metric of a plurality of registered metrics, in said client device per session based on a plurality of numeric values received from said client device.

6. The system according to claim 1, wherein said circuitry is further configured to determine a count related to a number of times said at least one UI of is accessed per session.

7. The system according to claim 1, wherein said circuitry is further configured to determine a latency of said API when said client device invokes a plurality of serial calls to a plurality of APIs, based on a plurality of numeric values received from said client device.

8. The system according to claim 1, wherein said circuitry is further configured to identify said API that exhibits a higher latency in comparison to other APIs when said client device invokes a plurality of parallel calls to a plurality of APIs, based on a plurality of numeric values received from said client device.

9. The system according to claim 1, wherein said circuitry is further configured to determine one of a time spent on each element of said navigation flow or a total time spent on a plurality of elements of said navigation flow in said session, based on a plurality of numeric values received from said client device.

10. The system according to claim 1, wherein said circuitry is further configured to dynamically generate at least one report related to one of said performance of said API or user behavior associated with said UI, based on a conversion of a plurality of numeric values received from said client device to a plurality of metrics associated with said unique namespace information value corresponding to each metric.

11. A system for remote monitoring, said system comprising:

circuitry in a server communicatively coupled to a client device, said circuitry configured to;

register at least one metric associated with performance of one of at least one application program interface (API) or at least one user interface (UI) associated with said client device;

assign a unique numeric value to each of said at least one registered metric to associate said assigned unique numeric value with a corresponding registered metric of said at least one registered metric;

receive a plurality of first numeric values from said client device, wherein each of said received plurality of first numeric values corresponds to a registered metric of said at least one registered metric;

generate a visualization of a navigation flow of said at least one UI in a first session of a plurality of sessions; and

identify a source of traffic to said at least one UI; and

determine a missing sequence value associated with receipt of data for said first session from said client device based on said received plurality of first numeric values for at least one second session of said plurality of sessions, wherein said missing sequence value corresponds to a deviation from a specified sequence for said receipt of said data for each session of said plurality of sessions.

12. The system according to claim 11, wherein each of said at least one metric is registered as a unique namespace information value.

13. The system according to claim 11, wherein said at least one UI corresponds to one of at least one cross-linked webpage or at least one UI of a software application accessed from said client device, wherein said at least one cross-linked webpage includes at least one functional region.

14. The system according to claim 11, wherein said circuitry is further configured to:

compute a number of missing sequence values with respect to a count of said plurality of sessions for a user-defined time period, wherein said computed number is a quality indicator for said data received from said client device; and

generate an alert when said computed number is above a threshold.

15. The system according to claim 11, wherein said circuitry is further configured to determine a missing sequence associated with one of said navigation flow within a first UI of said at least one UI or said navigation flow from said first UI to a second UI of said at least one UI, based on said received plurality of first numeric values, wherein said missing sequence corresponds to a deviation from at least one specified navigation flow related to a sequence of user visits to at least one functional region associated with said at least one UI in said first session.

16. The system according to claim 15, wherein said navigation flow within said first UI of said at least one UI corresponds to navigation from a first functional region of said first UI to a second functional region of said first UI.

17. The system according to claim 11, wherein said circuitry is further configured to determine a collective metric associated with a plurality of client devices based on one of aggregation or filtering of said received plurality of first numeric values from said client device and plurality of second numeric values received from remaining client devices of said plurality of client devices.