SYSTEM AND METHOD FOR REMOTE MONITORING OF API PERFORMANCE AND USER BEHAVIOR ASSOCIATED WITH USER INTERFACE

• US 20160277264A1
• Filed: 03/17/2016
• Published: 09/22/2016
• Est. Priority Date: 03/20/2015
• Status: Active Grant

• Current Assignee: Sony Interactive Entertainment LLC (Sony Group Corp.)
• Original Assignee: Sony Corporation (Sony Group Corp.), Sony Network Entertainment International LLC (Sony Group Corp.)
• Inventors: ZARN, MILES
• Granted Patent: US 10,110,688 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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:

one or more circuits in a server communicatively coupled to a client device, said one or more circuits being configured to;

register a metric associated with performance of an application program interface (API) and/or a 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, and

synchronize said assigned numeric value associated with said registered metric at said client device and said server, herein said performance of said API and/or said UI associated with said client device is determined based on receipt of said assigned numeric value from said client device.

2. The system according to claim 1, wherein said one or more circuits are 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 one or more 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, and/or a time offset value from said timestamp of said first metric.

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

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

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

5. The system according to claim 1, wherein said one or more circuits are 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 one or more circuits are further configured to determine a count related to number of times said UI of one or more UIs is accessed per session.

7. The system according to claim 1, wherein said one or more circuits are further configured to:

generate a visualization of a navigate flow between one or more UIs in a session, and

identify a source of traffic to said UI of said one or more UIs.

8. The system according to claim 1, wherein said one or more circuits are 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.

9. The system according to claim 1, wherein said one or more circuits are 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.

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

11. The system according to claim 1, wherein said one or more circuits are further configured to dynamically generate one or more reports related to said performance of said API and/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 using said unique namespace information corresponding to each metric.

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

one or more circuits in a server communicatively coupled to a client device, said one or more circuits being configured to;

register one or more metrics associated with performance of;

one or more application program interfaces (APIs) and/or one or more user interfaces (UIs) associated with said client device;

assign a unique numeric value to each of said one or more registered metrics to associate said assigned unique numeric value with a corresponding registered metric of said one or more registered metrics;

receive a plurality of numeric values from said client device, wherein each of said received plurality of numeric values corresponds to a registered metric of said one or more registered metrics; and

determine a missing sequence value associated with receipt of data for a session from said client device based on said received plurality of numeric values for one or more other sessions of a plurality of sessions, wherein said missing sequence value corresponds to a deviation from a pre-specified sequence for said receipt of said data for each session of said plurality of sessions.

13. The system according to claim 12, wherein each of said one or more metrics is registered as a unique namespace information.

14. The system according to claim 12, wherein said one or more UIs correspond to:

one or more cross-linked webpages that include one or more functional regions in each webpage, or one or more UIs of a software application accessed from said client device.

15. The system according to claim 12, wherein said one or more circuits are further configured to:

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

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

16. The system according to claim 12, wherein said one or more circuits are further configured to determine a missing sequence associated with a navigation flow within a first UI of sari one or more UIs and/or from said first UI to a second UI of said one or more UIs, based on said received plurality of numeric values, wherein said missing sequence corresponds to a deviation from one or more pre-specified navigation flows related to a sequence of visits to one or more functional regions associated with said one or more UIs in a session.

17. The system according to claim 16, wherein said navigation flow within said first UI of said one or more UIs corresponds to navigation from one functional region of said first UI to another functional region of said first UI.

18. The system according to claim 12, wherein said one or more circuits are further configured to determine a collective metric associated with a plurality of client devices based on an aggregation and/or filtering of said received plurality of numeric values from said client device and other plurality of numeric values received from other client devices of said plurality of client devices.

19. A client device comprising:

one or more circuits in said client device communicatively coupled to a server, said one or more circuits being configured to;

detect a start time aid an end time of a session based on an initiation of a user activity and/or inactivity for a pre-defined threshold time on a user interface (UI);

generate a new session identifier (ID) based on said detected said start time and said end time of said session;

measure a latency value associated with performance of an application program interface (API) and/or said UI associated with said client device;

store said measured latency value as a numeric value that corresponds to a metric; and

communicate a plurality of numeric values that includes said stored numeric value to said server.