Communication device usage event profiling

[0001] This application is a continuation of and claims priority to U.S. patent application Ser. No. 11/449,078, now U.S. Pat. No. 7,801,518 B1, entitled “Communication Device Usage Event Profiling”, filed on Jun. 8, 2006 and issued on Sep. 21, 2010, which is incorporated herein by reference for all purposes.

[0002] Not applicable.

[0003] Not applicable.

[0004] The present disclosure is generally directed to usage event profiling on a communication device (e.g., a cellular telephone). More particularly, the present disclosure relates to detecting usage events indicative of how a user uses a communication device and the transmission of such detected events a remote system for storage and/or analysis.

[0005] Mobile communication devices, such as cellular telephones, communicate through networks provided by a services provider. Through the networks, the mobile communications devices are able to obtain content from various content providers. For example, users of cellular telephones can download audio clips (e.g., songs) to be played through the phone as a ringer. Various other content can be obtained, including games, software utilities, and images that serve as a background on the phone's display. Various services can also be accessed, including text messaging, email services, news alerts, etc. Providers of such content and services naturally desire to provide content or services that their customers prefer. The content or services that customers want, however, is difficult to ascertain.

[0006] The issues introduced above are addressed by, in accordance with at least some embodiments of the invention, a communication device that includes various hardware and software components. The communication device also comprises instrumentation logic that detects the occurrences of various user usage events and logs such events. The usage events impart information about how a user is actually using the communication device. The logged usage event information can be transmitted to a server (e.g., a data center) for subsequent storage and/or analysis. User behavior profiles can thus be analyzed to determine, for example, services that users seem to prefer.

[0007] According to at least one embodiment of the invention, the present disclosure is directed to a communication device that comprises a radio, a processor coupled to the radio, and instrumentation logic coupled to the processor. The instrumentation logic detects usage events associated with the communication device. Each usage event pertains to how a user uses said communication device.

[0008] According to another embodiment, the present disclosure describes a system that is separate from, and adapted to, communicate with a communication device. The system comprises a content service configured to be provided to the communication device. The system also comprises a device registry accessible to the content service to store usage event data transmitted to the system from the communication device. The usage event data is indicative of how a user of the communication device has used the communication device.

[0009] In yet another embodiment, a method comprises detecting a usage event associated with a person's use of a communication device. The method also comprises storing usage event data on the communication device. The usage event data is indicative of the detected usage events.

[0010] These and other features and advantages will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

[0014] It should be understood at the outset that although an illustrative implementation of one embodiment of the present invention is illustrated below, the present system may be implemented using any number of techniques, whether currently known or in existence. The present disclosure should in no way be limited to the implementations, drawings, and techniques illustrated below, but may be modified as desired and as would be understood by one of ordinary skill in the art.

[0015] Content and service providers for communication devices (e.g., cellular telephones), know that a user of a cellular telephone has downloaded a particular item or used a particular service (e.g., a particular ringer) when that content or service was obtained from that provider. Where multiple providers exist, each provider is only aware of what that user has obtained from that provider. Moreover, the provider generally does not know whether the user of the communication device ever actually uses downloaded content, or for what time period (or with what frequency) particular downloaded content or accessed services are used. For example, the provider of a particular ringer does not know whether the ringer was ever used, whether it was used for a short time period and abandoned, or whether the user was satisfied with the ringer and continues to use it. Embodiments of the present invention provide a mechanism, preferably implemented on the communication device itself, to provide knowledge to the content or services provider of how the user actually uses the communication device. The knowledge extends beyond just what content or services have been requested from a given provider, and includes information regarding what content or services have been requested from other providers, and if and how such content or services were actually used by the user. Such knowledge enables a provider to gain insight regarding customer desires, enabling the provider to more closely tailor offered content and services to better satisfy their customers.

[0016] In accordance with various embodiments of the invention, a communication device comprises various hardware and software components, including instrumentation logic that detects the occurrences of various usage events and logs such events. The events so detected comprise any one or more of a number of different types of events including the selection of a particular ringer for the communication device to be played upon the receipt of an in-coming phone call, the selection of a particular image to be the background image on the communication device's display, etc. Such events impart information about how a user is using the communication device, and accordingly, the logging of such events is referred to as “behavior profiling.” The logged events can be transmitted to a remote system (e.g., a data center) for subsequent storage and analysis. Each user's behavior profile (or the collective profiles of multiple users) can be analyzed by the remote system to determine, for example, content and services that users prefer.

[0017] FIG. 1 shows an illustrative embodiment of the communication device. As shown, the communication device 50 comprises a processor 80 coupled to a wireless modem (“radio”) 82. The radio 82 includes, or is associated with, an antenna 84 thereby permitting two-way communications with another communication device, which may be a base station or another communication device like the one illustrated in FIG. 1. In some embodiments, the communication device is, or at least comprises, a mobile communication device such as a cellular telephone.

[0018] The processor 80 executes code. Such code is logically organized into various “layers” including, for example, a presentation layer 52, an application layer 60, a middleware layer 66, and an operating system 70. The software comprising layers 52-70 is stored in storage 55 (coupled to processor 80) and is executed by processor 80. The storage 55 comprises volatile memory such as random access memory (RAM), non-volatile storage such as Flash memory, read only memory (ROM), electrically-erasable programmable ROM (EEPROM), a hard disk drive, etc., or combinations thereof.

[0019] The operating system 70 can comprise any suitable operating system on which the most or all other software executes. It includes various device drivers for hardware components of the communication device 50 and may further include directory management and other low-level services that are useful to applications. The middleware 66 includes application management services (AMS) software that acts as an intermediary between different applications, both within the communications device and on remote systems. The middleware 66 may include communications protocol “stacks”, i.e., software that handles the standard communications protocol details so that applications can employ a communications simple interface. In some software architecture designs, the middleware 66 may be considered to be part of the operating system 70.

[0020] One or more applications 61 comprise the application layer 60. Such applications 61 comprise, for example, applications that provide any or all of the following functionality, as well as any of a variety of additional functionality:

• • [0021] Contacts—the management (adding, deleting, editing) of names, address, telephone numbers, etc.
  • [0022] VoiceSMS—functionality that enables the user of the communication device to talk to a user of another communication device without dialing such other user's phone number. This functionality permits the communication device to function similar to a “walkie-talkie”
  • [0023] Picture Mail MMS—functionality that enables sending and receiving of images and the viewing of such images on the communications device
  • [0024] Alerts—functionality that alerts the user to events such as missed calls, stock prices reaching a threshold, sports events, etc.
  • [0025] Call History—functionality that stores the identity (phone number, time, etc.) of previously placed calls and in-coming calls
  • [0026] Music Store—functionality that enables the user of the communication device to download audio
  • [0027] Text Messaging—functionality that enables a user exchange text messages with a user of another communication device
  • [0028] Media Player—functionality that enables the user to play audio and/or video clips
  • [0029] Settings—functionality that enables a user to change various settings (e.g., font, color, type size, etc.)
  • [0030] Dialer—functionality that enables a user to dial a phone number, auto redial, voice-activated dialing, etc.

[0031] The presentation layer 52 comprises one or more presentation applications 51 that interact with the applications in the application layer 60 to present audio and/or visual information to a user of the communication device 50. Such presentation applications 51 comprise, for example, applications provide to the user information about contacts, messages, missed alerts, settings, account self-service, etc.

[0032] Referring still to FIG. 1, the communication device 50 also comprises instrumentation logic 56 that detects usage events associated with the communication device, logs such usage events, and transfers the usage event logs to a remote system (e.g., a server). In the illustrative embodiment of FIG. 1, the instrumentation logic 56 comprises usage event detectors (UEDs) 54, 62, 68, and 72. One or more UEDs are located in, or associated with, each layer 52, 60, 66, and 70. In the embodiment shown in FIG. 1, the UEDs 54, 62, 68, and 72 are located in, or associated with, the presentation layer 52, the application layer 60, the middleware layer 66, and the operating system 70, respectively. As shown in FIG. 1, the functionality performed by the UEDs is distributed among the various layers. In other embodiments, however, the functionality performed by the UEDs is consolidated and not distributed. While each layer 52, 60, 66, and 70 comprises a UED as shown in FIG. 1, in other embodiments, not every layer comprises a UED.

[0033] Each of the UEDs 54, 62, 68, and 72 functions to detect usage events. As explained above, a usage event comprises an event that pertains in some way to how a user uses the communication device 50. Some usage events may pertain to the user's use of a particular type of downloaded content or a use of a particular service from a service provider, while other usage events may not relate to such content or services, but may instead pertain only to the user's configuration or usage of a device. Examples of usage events pertaining to the presentation layer 52 comprise such events as a user-initiated change to how contact information is displayed on the communication device or a user-initiated change to the presentation of alert information. The usage event detector 54 may detect changes to font sizes, changes to display colors, and changes to graphical user interface preferences (e.g., whether text labels, small icons, or large icons are preferred).

[0034] Examples of usage events pertaining to the application layer 60 comprise such “in-application” events as a user-initiated change to the selection of a particular audio clip as the communication device's ringer or the selection of a particular graphics image as the device's background image. The usage event detector 62 may detect actions taken within applications running on the device, including changes to alert settings, changes to selected ring tones, and may aggregate events to, e.g., count numbers of Voice SMS messages sent, count text messages received, and count the number of times a game is played.

[0035] Examples of usage events pertaining to the middleware layer 66 comprise such events as counting the number of times each application is run, and tracking the first and last execution of each application (to enable determination of how long an application has been used on the communications device and how long since the last time it was used). Usage event detector 68 may detect the initiation of an application's execution and the time at which such initiation occurs.

[0036] Examples of usage events pertaining to the operating system 70 comprise such events as turning the communications device on and off, low battery warnings, recharge events, and running out of available memory. Usage event detector 72 may detect system events such as power-on, power-off, low-battery, charging, and out-of-memory errors. The aforementioned list of usage event examples is illustrative only of the described embodiments of the invention. Additional and/or alternative examples of usage events are within the scope of this disclosure.

[0037] The logged usage events provide information about the usage of a communication device that would otherwise not be known to providers of content to users of the communication devices. By way of an example and as alluded to above, a cellular telephone service provider will know when a user of a cellular telephone has downloaded a particular ringer from that provider. The service provider, however, without the embodiments disclosed herein would not necessarily know whether the user of the cellular telephone actually used the ringer, and would be unaware of ringers downloaded from other providers. The instrumentation logic 56, and in particular in this example UED 62 in the application layer which enables a user to select a ringer, will detect that the user has actually configured the communication device 50 to use a particular ringer.

[0038] The detected usage events are stored (logged) on the communication device 50 (e.g., in the storage 55). The embodiment of FIG. 1 also shows that the instrumentation logic 56 comprises an instrumentation client 76. In some embodiments, the instrumentation client 76 comprises a set of hardware registers that are used to temporarily store detected events until they can be communicated to a remote system. In other embodiments, the instrumentation client 76 comprises code that is executable by the processor 80. The instrumentation client 76 preferably manages the transfer of the stored usage event data to a remote system (shown in FIG. 2). Usage event data comprises data that describes the usage events. For example, a user-initiated change in a ringer would cause UED 62 to generate usage event data that specifies that the user has changed the ringer, the identity of the new ringer, a timestamp, etc. The usage event data transfer by the instrumentation client 76 can be initiated by the client or by the remote system to which the client transfers the data. That is, the client 76 can initiate the transfer or the remote system can request the usage event data to be transferred. In some embodiments, the usage event data can be transferred at pre-defined or programmable intervals (once per hour, once per day, etc.). In other embodiments, the usage event data is transferred asynchronously (i.e., not a specific intervals, but upon request whenever the request happens to be initiated).

[0039] In yet other embodiments, based on, for example, usage event data type, some usage event data may be transferred to the remote device at defined intervals (e.g., once per day or another time interval), while other usage event data may be transferred asynchronously such as when or “shortly after” such usage events are detected. The term “shortly after” includes any time period following the detection of the usage event up to, for example, 5 minutes, 10 minutes, 1 hour, etc. In general, “shortly after” is intended to include the usage event data transfer occurring substantially in “real-time” following detection of the usage event, which is application specific and thus can vary from situation to situation. An example of this latter instance (usage event data being transferred upon or shortly after its detection) comprises a user configuring the communication device to use a particular ringer. Upon the user interacting with the communication device (or shortly thereafter) to implement the desired ringer, the usage event (which was detected preferably by the communication device's UED 62) is transferred by the instrumentation client 76 to a remote system. Thus, for some types of the usage events, the remote system would be informed relatively quickly of the occurrence of the event, while for other types of usage events, there would be a more substantial delay before the remote system is informed. In at least some embodiments, the determination as to which types of data to transfer in real-time and which to transfer at defined time intervals is based on which layer 52, 60, 66, and 70 the detected usage event originated. Alternatively, the determination as to which types of data to transfer in real-time and which to transfer at defined time intervals is user-programmable. In one example, presentation layer originating usage events are transferred in real-time, while operating system-based usage events are transferred at defined time intervals.

[0040] The instrumentation client 76 can also enable and disable the UEDs 54, 62, 68, and 72 from operating to detect and store usage event data. The enablement and disablement may apply to the UEDs as a group (i.e., the UEDs are all enabled and disabled as a single group) or may apply to the UEDs individually (that is, one UED may be enabled and disabled separately from another UED). In some embodiments, the user of the communication device 50 can interact with the instrumentation client 76 to enable and disable usage event detection as desired.

[0041] FIG. 2 illustrates a remote system 100 configured to communicate with the communication device 50. The remote system 100 comprises a first content or services provider 102, a second content or service provider (“maintenance services”) 104, and a device registry 110. Other components may be provided as well. In some embodiments, the remote system 100 is a computer, such as a server. The remote system 100 may be a single computer in accordance with some embodiments, while in other embodiments, the remote system 100 comprises a plurality of computers installed in, for example, a data center. Broadly, the content/services provider 102, maintenance services 104, and device registry 110 can be implemented on one computer or each of the content/services provider 102, maintenance services 104, and device registry 110 is implemented on a separate computer as part of a network of computers. These various components (102, 104 and 110) may be implemented in software, hardware, or a combination thereof. As software, the code comprising the software executes on at least one processor 112. The device registry 110 may comprise storage such as non-volatile storage (e.g., a hard disk drive) or volatile memory (e.g., random access memory).

[0042] The content/services provider 102 provides downloadable content or a communications-device accessible service available to the communication device 50. An illustrative list of content and services includes:

• • [0043] Audio and/or video streaming on demand
  • [0044] Themes—a collections of background images, icons, fonts, and colors that can be used to customize the communication device's display
  • [0045] Music—a service by which a user of a communication device can download music to be used, for example, as a ringer
  • [0046] Contact Sync—a service by which a user can synchronize contacts on his or her communication device with a remote set of contacts
  • [0047] Visual Voicemail—a voice mail service that also provides images or video of the person leaving the message
  • [0048] E-mail—a electronic mail service

[0049] The maintenance services 104 similarly provide downloadable content or a network-accessible service for use by the communication device 50. An illustrative list of maintenance services includes:

• • [0050] Internet Over The Air (IOTA) Provisioning—IOTA profile downloads to configure various device parameters which can be set by the carrier or by the user, including, e.g., an IP address for a wireless web gateway, an IP address of a home agent used to issue temporary mobile IP addresses, a default home page, etc.
  • [0051] Firmware Maintenance—firmware downloads to update the operating system and middleware of communication devices
  • [0052] Diagnostics—software downloads to diagnose problems with a communications device
  • [0053] Application Maintenance—software downloads to update applications on communication devices

[0054] The device registry 110 comprises storage for storing the usage event data transferred to the remote system 100 by the communication device 50. The device registry 110 may also comprise information regarding services purchased or content downloaded to a particular communication device 50. That is, a record is made in the device registry 110 that a user has purchased or downloaded a particular content and/or services (e.g. purchased a new ringer). Such information is provided to the device registry 110 by the content/services provider 102 or maintenance services 104. If, and when, the user actually uses the service on his or her communication device (e.g., configured the communication device to use a newly downloaded ringer), that usage event detected by the communication device and transferred to the remote system 100 for storage in the device registry 110.

[0055] In some embodiments, the information (including the usage event data and the content and maintenance services) stored in the device registry is organized according to the users of the communication devices 50. That is, a log is provided in the device registry that indicates the usage event data and content and maintenance services associated with a given communication device and/or user.

[0056] The remote system 100, or other system, can analyze the information contained in the device registry for any of a variety of purposes. One such purpose would be to determine a set of content and services preferred by a number of communication device users. For example, a number of users may have not only downloaded a particular song to their communication device 50, but also actually used that song as a ringer. The information in the device registry 110 could be analyzed to make this determination. Based on the determination that a certain song is popular among a significant number of communication device users, a decision could then be made to provide additional songs by the same artist or additional songs of the same type or genre. In general, once knowledge of user likes is assessed (based on information in the device registry 110), the set of content and/or services could be optimized.

[0057] While various embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein, but may be modified within the scope of the appended claims along with their full scope of equivalents. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented. Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be coupled through some interface or device, such that the items may no longer be considered directly coupled to each other but may still be indirectly coupled and in communication, whether electrically, mechanically, or otherwise with one another. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.