Mobile applications incorporating mobile-based transactions detection and monitoring means

Patent metadata

Field	Value
Publication number	US-9924293-B2
Application number	US-201414517452-A
Country	US
Kind code	B2
Filing date	Oct 17, 2014
Priority date	Oct 17, 2014
Publication date	Mar 20, 2018
Grant date	Mar 20, 2018

Abstract

Client to server service request and response interactions are monitored. The service requests have embedded therein mobility-dedicated and business organization oriented reporting headers. At the server side of the interactions, a snooping agent picks up information from the headers, combines it with service performance metrics (e.g., time to service the request) and stores the data in a relational database. Queries are afterwards submitted to the database to spot trends including those showing emerging problems and areas for improvement in providing customers who use mobile devices with seamless and high quality service.

First claim

What is claimed is:

1. A machine-implemented service request handling process for use with one or more servers receiving service requests from mobile devices, the process comprising:
automatically detecting if a mobility parameters providing first header is present as part of a received first request sent from a respective first mobile device to at least one of the servers;
automatically acquiring from the detected first header, first mobility parameter data relating to at least one of the first request and the first mobile device;
using the acquired first mobility parameter data to search for other service requests or performance reports generated for the other service requests where the other service requests respectively have respective other mobility parameters providing headers and at least respective parts of the other mobility parameters providing headers correlate with a specified part of the first mobility parameter data;
generating at least one performance metric for the first request measuring a predetermined aspect of at least one of the first request and its corresponding one or more request-servicing responses; and
generating an aggregation report where the generated aggregation report identifies the first request and at least one of the other service requests as being aggregated with one another and as being correlated to the specified part of the first mobility parameter data.

2. The machine-implemented process of claim 1 wherein the generated aggregation report identifies respective performance metrics generated for the first request and for the at least one of the other service requests as being aggregated with one another as well as being correlated to the specified part of the first mobility parameter data.

3. The machine-implemented process of claim 1 and further comprising:
automatically storing the data automatically acquired from the detected first header in a first database as data that is searchable for.

4. The machine-implemented process of claim 3 and further comprising:
automatically storing in the first database, and as logically associated with the first header data, a performance trace that traces a performance of the service requested by the first service request.

5. The machine-implemented process of claim 3 wherein the at least one performance report generated for the first request reports on a corresponding first response completion time as the predetermined metric for the received first request and for one of its corresponding one or more request-servicing responses, the process further comprising:
automatically storing the first response completion time in the first database in logical association with the data automatically acquired from the first header; and
logically associating with the first response completion time, at least one predetermined and respective other response completion time for the at least one of the other service requests of the aggregation report.

6. The machine-implemented process of claim 3 and further comprising:
automatically determining if a stall occurred or not during processing of the received first request and storing the stall yes or no indication in the first database in logical association with the data automatically acquired from the first header; and
logically associating with the stall yes or no indication of the first request, at least one predetermined and respective other stall yes or no indication for the at least one of the other service requests of the aggregation report.

7. The machine-implemented process of claim 3 and further comprising:
automatically determining if one or more errors occurred during processing of the received first request and storing the errors count in the first database in logical association with the data automatically acquired from the first header; and
logically associating with the errors count of the first request, at least one predetermined and respective errors count for the at least one of the other service requests of the aggregation report.

8. The machine-implemented process of claim 1 and further comprising:
automatically determining per interval metrics associated with a plurality of service requests received by the one or more servers where the automatically determined per interval metrics includes a per interval responses count associated with only an identified subset of originating mobile devices.

9. The machine-implemented process of claim 8 wherein the automatically determined per interval metrics includes a per interval responses count associated with only an identified subset of wireless providers.

10. The machine-implemented process of claim 3 as carried out for a plurality of the said service requests and further comprising:
automatically and repeatedly applying first pre-canned queries to the first database where the query criteria includes one or more of the mobility parameters provided by the respective headers of the plurality of service requests.

11. The machine-implemented process of claim 10 as carried out for the plurality of service requests and further comprising:
automatically and repeatedly storing results of the applied first pre-canned queries in a second database.

12. The machine-implemented process of claim 11 and further comprising:
automatically and repeatedly applying second pre-canned queries to the second database for detecting emerging trends including those of system underperformance and or growing strain on system resources.

13. The machine-implemented process of claim 1 wherein the mobility parameters providing first header provides one or more of the following parameters:
an originating mobile device's unique ID;
an identification of a wireless provider that the service request originator device is coupled to at the time of the request;
an identification of a wireless connection type that the originator device was utilizing at the time of the request;
an identification of a mobile device operating system used by the originator device;
an identification of a mobile device firmware used by the originator device;
an identification of a geographic location from which the request was sent;
an identification of a cellular coverage zone from which the request was sent;
an identification of a parent Business Service Name associated with application code responsible for originating the request;
an identification of a Business Transaction Name associated with application code responsible for originating the request;
a mobile device application name having the application code responsible for originating the request; and
an identification of one or more user gestures invoked immediately prior to the originating of the request.

14. The machine-implemented process of claim 1 wherein the first mobile device is a smart cellular phone.

15. The machine-implemented process of claim 1 wherein the first mobile device is a tablet computer having cellular phone connectivity capability.

16. A machine-implemented service request forming process implemented on respective mobile devices that are configured to communicate with a respective one or more service providing servers, the communication including a submitting of one or more service requests to one or more of the service providing servers, the service request forming process comprising:
instrumenting respective original application object code of respective ones of the mobile devices so as to thereby produce respective instrumented object code whose submitted service requests to one or more of the service providing servers include mobility parameter providing head

Assignees

• Ca Inc

Inventors

• Giral Erhan
• Cohen Corey

Classifications

• H04W24/02

  Arrangements for optimising operational condition · CPC title

• H04L41/0836

  to enhance reliability, e.g. reduce downtime · CPC title

• H04L43/10

  Active monitoring, e.g. heartbeat, ping or trace-route · CPC title

• H04L43/06

  Generation of reports · CPC title

• H04L41/0823

  characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability (for optimising operational conditions of wireless networks H04W24/02) · CPC title