PROVIDING EVENT-CONTROLLED CONTINUOUS LOGGING FOR A MOBILE OPERATING ENVIRONMENT

• US 20080294384A1
• Filed: 01/07/2008
• Published: 11/27/2008
• Est. Priority Date: 05/21/2007
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Yip, Eric Chi Chung, Fok, Kenny, Lushin, Makhail A.
• Granted Patent: US 7,890,299 B2
• Time in Patent Office: Days
• US Class Current: 702/187
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: H04M 1/72484 wherein functions are triggered by incoming communication events
• CPC Class Codes: H04M 2250/10 including a GPS signal receiver
• CPC Class Codes: H04M 2250/60 logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs logging of telephone numbers H04M1/56, H04M1/57
• CPC Class Codes: H04W 8/24 Transfer of terminal data

Abstract

Providing for event-controlled continuous logging for a mobile operating environment is described herein. For instance, collection of mobile device operating system (OS) log data can be initiated and terminated as a result of one or more predetermined events. The events can both trigger collection as well as terminate collection of the log data. Further, limiting collection/termination of log data to particular log index codes is also described herein, enabling logging of data pertinent to one or more determinable events. As described, the subject specification discloses mechanisms to initiate and to terminate continuous logging of mobile OS log codes as a result of occurrence of one or more determinable events.

Claims

1. A method of providing programmable event-controlled continuous code logging for a mobile device operating system (OS), comprising:

establishing a first trigger that initiates continuous collection of a log code, event code or a request-response packet (log data) of a mobile OS;

establishing a second trigger that terminates collection of the log data;

conditioning execution of the first trigger and the second trigger on occurrence of a start event and a stop event, respectively, wherein at least one of the start event or the stop event is associated with a non-hardware start-up or a non-hardware shut down operation of a mobile device, and wherein the start event and stop event are determinable by an application or process of the mobile OS; and

providing a second application or process with access to selected ones of the continuously collected log data, selected based on a predetermined sampling function.

2. The method of claim 1, further comprising at least one of:

detecting occurrence of the start event, executing the first trigger and recording a log collection start time;

or

detecting occurrence of the stop event, executing the second trigger if collection of the log data has begun and recording a stop time associated with execution of the second trigger.

3. The method off claim 1, further comprising limiting the collection or the termination of the collection, or both, to log data that is pertinent to an index code of the mobile OS, wherein the index code categorizes mobile OS log data.

4. The method of claim 3, further comprising at least one of:

associating the index code with the start event;

detecting occurrence of the start event;

executing the first trigger;

collecting log data pertinent to the index code or ignoring log data not pertinent to the index code;

or

recording an index code start time associated with the collecting or the ignoring.

5. The method of claim 3, further comprising at least one of:

associating the index code with the stop event;

determining occurrence of the stop event;

executing the second trigger to terminate collection of log data associated with the index code or terminate ignoring of log data not pertinent to the index code;

or

recording an index code stop time associated with executing the second trigger.

6. The method of claim 1, further comprising enabling multiple start events to execute the first trigger and multiple stop events to execute the second trigger, the multiple start and stop events are each associated with one or more index codes.

7. The method of claim 6, further comprising tracking a number of start or stop events associated with a first index code and conditioning terminating collection of log data associated with the first index code on occurrence of an equivalent number of stop events associated with the first index code.

8. The method of claim 3, further comprising tracking a number of start events that execute the first trigger and conditioning execution of the second trigger on occurrence of a number of stop events equal to the number of start events.

9. The method of claim 1, further comprising:

defining an event flag that couples the first trigger with at least one of multiple second triggers; and

conditioning termination of log data collected as a result of the first trigger on execution of one of the multiple second triggers that is coupled with the first trigger by the event flag.

10. The method of claim 1, further comprising:

providing a continuous logging trigger that initiates perpetual recording of log data independent of the start event and the stop event; and

optionally employing a particular sampling rate, distinct from an event-triggered sampling rate, for collection of log data initiated by the continuous logging trigger.

11. The method of claim 1, further comprising employing a triggered sampling rate for collection of log data initiated by the first trigger.

12. An apparatus that provides continuous event-controlled code logging for a mobile operating environment, comprising:

a logging module configured to continuously collect log data in a mobile device OS;

a management module configured to establish a first trigger that initiates collection of the log data and a second trigger that terminates collection of the log data; and

a logic module that conditions execution of the first trigger on occurrence of a start event and execution of the second trigger on occurrence of a stop event, wherein at least one of the start event or the stop event is associated with a non-hardware start-up or a non-hardware shut down operation of a mobile device, and wherein the start and stop event are determinable by an application or process of the mobile OS or a remote network component, or both, and wherein the logic module provides a second application or process with access to selected ones of the continuously collected log data, selected based on a predetermined sampling function.

13. The apparatus of claim 12, further comprising a detection and timing module configured to record a log collection start time upon execution of the first trigger or record a log collection stop time upon execution of the second trigger, or both.

14. The apparatus off claim 12, further comprising an index parsing module that employs an index code that categorizes mobile OS log data to limit the collection or the termination of the collection, or both, to log data that is pertinent to the index code.

15. The apparatus of claim 14, wherein at least one of:

the management module is further configured to associate the index code with the start event;

the detection and timing module is configured to determine occurrence of the start event;

the logic module executes the first trigger;

the logging module is configured to collect log data pertinent to the index code or ignores log data not pertinent to the index code;

or

the detection and timing module is configured to record an index code start time upon collection of the log data pertinent to the index code.

16. The apparatus of claim 14, wherein at least one of:

the management module is further configured to associate the index code with the stop event;

the detection and timing module is configured to determine occurrence of the stop event;

the logic module is configured to execute the second trigger to terminate collection of log data associated with the index code;

or

the detection and timing module is configured to record an index code stop time upon termination of collection of the log data pertinent to the index code.

17. The apparatus of claim 12, wherein the logic module is configured to enable multiple start events to execute the first trigger and multiple stop events to execute the second trigger, the multiple start and stop events are each associated with one or more index codes that categorize mobile OS log data.

18. The apparatus of claim 17, further comprising a reference module that tracks a number of start events and stop events associated with a first index code, wherein the logic module conditions termination of log data associated with the first index code on occurrence of a number of the stop events equivalent to a number of the start events.

19. The apparatus of claim 12, wherein the logic module tracks a number of start events that execute the first trigger and conditions execution of the second trigger on occurrence of a number of stop events equal to the number of start events.

20. The apparatus of claim 12, wherein:

the management module is further configured to define an event flag that couples the first trigger with at least one of multiple second triggers; and

the logic module conditions termination of log data collection initiated by the first trigger on execution of one of the multiple second triggers that is coupled to the first trigger by the event flag.

21. The apparatus of claim 12, wherein at least one of:

the logging module includes a continuity trigger that, once initiated, records log data independent of the start event and the stop event;

or

the logging module optionally employs a particular sampling rate for collection of log data initiated by the continuous logging trigger different from a triggered sampling rate utilized for event-controlled logging.

22. The apparatus of claim 12, wherein the logging module employs a triggered sampling rate for collection of log data initiated by the first trigger.

23. At least one processor configured to provide programmable event-controlled continuous code logging for a mobile device OS, comprising:

a first module configured to establish a first trigger that initiates continuous collection of mobile OS log data;

a second module configured to establish a second trigger that terminates collection of the log data; and

a third module configured to condition execution of the first trigger and the second trigger on occurrence of a start event and a stop event, respectively, wherein at least one of the start event or the stop event is associated with a non-hardware start-up or a non-hardware shut down operation of a mobile device, and wherein the start event and stop event are determinable by an application or process of the mobile OS; and

a fourth module configured to provide a second application or process with access to selected ones of the continuously collected log data, selected based on a predetermined sampling function.

24. An apparatus configured to provide programmable event-controlled continuous code logging for a mobile device OS, comprising:

means for establishing a first trigger that initiates continuous collection of mobile OS log data;

means for establishing a second trigger that terminates collection of the log data; and

means for conditioning execution of the first trigger and the second trigger on occurrence of a start event and a stop event, respectively, wherein at least one of the start event or the stop event is associated with a non-hardware start-up or a non-hardware shut down operation of a mobile device, and wherein the start event and stop event are determinable by an application or process of the mobile OS; and

means for providing a second application or process with access to selected ones of the continuously collected log data, selected based on a predetermined sampling function.

25. A computer program product, comprising:

a computer-readable medium containing instructions configured to provide programmable event-controlled continuous code logging for a mobile device OS, comprising;

at least one instruction configured to cause a computer to establish a first trigger that initiates continuous collection of mobile OS log data;

at least one instruction configured to cause a computer to establish a second trigger that terminates collection of the log data; and

at least one instruction configured to cause a computer to condition execution of the first trigger and the second trigger on occurrence of a start event and a stop event, respectively, wherein at least one of the start event or the stop event is associated with a non-hardware start-up or a non-hardware shut down operation of a mobile device, and wherein the start event and stop event are determinable by an application or process of the mobile OS; and

at least one instruction configured to cause a computer to provide a second application or process with access to selected ones of the continuously collected log data, selected based on a predetermined sampling function.

26. A method for configuring and/or consuming event-controlled log data compiled at one or more mobile OSs, comprising:

sending a query to a mobile device requesting log data from the mobile device;

sending a configuration parameter that specifies at least one event that is determinable by an OS of the mobile device, occurrence of the at least one event triggers termination of continuous log data collection; and

receiving collected log data from the mobile device, wherein continuous collection of the log data is based at least in part on selection according to a predetermined sampling function, and wherein the continuous collection of the log data at the mobile device was terminated upon occurrence of the at least one event.

27. The method of claim 26, further comprising specifying at least one start event that is determinable by the OS of the mobile device with the configuration parameter, wherein occurrence of the at least one start event is utilized to trigger collection of the log data.

28. The method of claim 26, further comprising including an index code, which categorizes log data of a mobile OS, with the at least one event, the index code limits the termination of log data collection to a category of log data associated with the index code.

29. The method of claim 26, further comprising including an event flag with the configuration parameter that pairs the at least one event with at least one start event that initiates collection of log data, the event flag limits termination of log data collection resulting from occurrence of the at least one event to log data initiated by the at least one start event.

30. The method of claim 26, further comprising utilizing the received log data in conjunction with a diagnostic, management or maintenance function of a network, or a combination thereof.

31. The method of claim 26, further comprising forwarding the received log data to a network service provider or a component thereof.

32. An apparatus that programs and/or consumes event-controlled log data compiled at one or more mobile OSs, comprising:

a transceiver that communicatively couples with at least one mobile device;

memory that contains a diagnostic application configured to send a query to the at least one mobile device requesting log data, and configured to provide a parameter identifying at least one event, the occurrence of the at least one event can be utilized to at least terminate continuous collection of the log data, wherein selection of log data for continuous collection is based at least in part on a predetermined sampling function; and

a processor that executes the diagnostic application and transmits and receives information related to the query and the configuration parameter.

33. The apparatus of claim 32, wherein the diagnostic application is further configured to specify at least one start event, wherein occurrence of the at least one start event is utilized to initiate collection of the log data.

34. The apparatus of claim 32, wherein the diagnostic application is further configured to include at least one index code with the at least one event, the at least one index code limits the termination of log data collection to log data that is pertinent to an index code of the OS.

35. The apparatus of claim 32, wherein the diagnostic application is further configured to include an event flag with the configuration parameter that pairs the at least one event with at least one start event that initiates collection of data, the event flag limits termination of log data collection resulting from occurrence of the at least one event to log data initiated by the at least one start event.

36. The apparatus of claim 32, wherein the diagnostic application is further configured to utilize the received log data in conjunction with a diagnostic, management or maintenance function of a network, or a combination thereof.

37. The apparatus of claim 32, wherein the diagnostic application is further configured to forward the received log data to a network service provider or a component thereof.

38. At least one processor configured to direct and/or consume event-controlled log data compiled at one or more mobile OSs, comprising:

a first module configured to send a query to a mobile device requesting log data from the mobile device;

a second module configured to specify at least one event that is determinable by an OS of the mobile device, occurrence of the at least one event triggers termination of continuous log data collection, wherein log data is selected for the continuous collection based at least in part on a predetermined sampling function; and

a third module configured to execute the diagnostic application and transmit and receive information related to the query and the configuration parameter.

39. An apparatus configured to program and/or consume event-controlled log data compiled at one or more mobile OSs, comprising:

a first module configured to send a query to a mobile device requesting log data from the mobile device;

a second module configured to specify at least one event that is determinable by an OS of the mobile device, occurrence of the at least one event triggers termination of continuous log data collection, wherein log data is selected for the continuous collection based at least in part on a predetermined sampling function; and

a third module configured to execute the diagnostic application and transmit and receive information related to the query and the configuration parameter.

40. A computer program product, comprising:

a computer-readable medium containing instructions configured to provide configuration and/or consumption of event-controlled log data compiled at one or more mobile OSs, comprising;

at least one instruction configured to cause a computer to send a query to a mobile device requesting log data from the mobile device;

at least one instruction configured to cause a computer to specify at least one event that is determinable by an OS of the mobile device, occurrence of the at least one event triggers termination of continuous log data collection, wherein log data is selected for the continuous collection based at least in part on a predetermined sampling function; and

at least one instruction configured to cause a computer to execute the diagnostic application and transmit and receive information related to the query and the configuration parameter.