PATENT DOCUMENT

Publication Number: US-8044795-B2
Application Number: US-53556409-A
Country: US
Kind Code: B2

Title: Event recorder for portable media device

Abstract:
Operational parametric sensing and event recording capabilities are provided for portable electronic devices such as media players, cell phones, laptop computers, and the like that takes the form of a standalone sensing unit or as an integrated component of the portable electronic device.

Claims:
1. A portable electronic device, comprising:
 in the portable electronic device; 
 a sensing circuit adapted to monitor a physical status of the portable electronic device and generate corresponding physical status data; 
 a recording device coupled with the sensing circuit adapted to record the physical status data received from the sensing circuit; and 
 a processor coupled to the recording device, wherein the processor executes computer code for using the received physical status data to determine if a manner of operation of the portable electronic device by a user is improper and can damage or reduce the useful operating life of the portable electronic device. 
 
     
     
       2. The portable electronic device as recited in  claim 1 , wherein the processor executes computer code for determining a likely cause of a portable electronic device malfunction; wherein the portable electronic device is at least partially inoperative or damaged. 
     
     
       3. The portable electronic device as recited in  claim 2 , wherein the processor further executes computer code for determining if the likely cause of the portable electronic device malfunction is due to the improper manner of operation of the portable electronic device by the user. 
     
     
       4. The portable electronic device as recited in  claim 3 , wherein if it is determined that the improper manner of operation of the portable electronic device by the user is not the likely cause of the device malfunction, then the processor executes computer code for determining if the device malfunction is due to a manufacturing defect or a design defect. 
     
     
       5. The portable electronic device as recited in  claim 3 , wherein if it is determined that the improper manner of operation of the portable electronic device by the user is the likely cause of the device malfunction, then the processor further executes computer code for determining if a repair operation to correct the device malfunction is covered by a manufacturer warranty. 
     
     
       6. The portable electronic device as recited in  claim 1 , wherein the sensing circuit includes a plurality of sensing devices each adapted to monitor a corresponding physical parameter. 
     
     
       7. The portable electronic device as recited in  claim 6 , wherein the plurality of sensing devices includes at least a temperature sensing device, or an accelerometer, or a battery charging sensing device. 
     
     
       8. The portable electronic device as recited in  claim 1 , wherein the portable electronic device is a portable media player. 
     
     
       9. A method of evaluating an operational status of a portable electronic device having at least a processor, comprising:
 in the portable electronic device; 
 monitoring a physical status of the portable electronic device 
 generating corresponding physical status data in accordance with the monitoring; 
 recording the physical status data; 
 using at least some of the recorded plurality of physical status data to determine if a manner of operation of the portable electronic device by a user is improper and can damage or reduce the useful operating life of the portable electronic device. 
 
     
     
       10. The method as recited in  claim 9 , further comprising:
 determining a likely cause of a portable electronic device malfunction that renders the portable electronic device at least partially inoperative or damaged. 
 
     
     
       11. The method as recited in  claim 10 , further comprising:
 determining if the likely cause of the portable electronic device malfunction is due to the improper manner of operation of the portable electronic device by the user. 
 
     
     
       12. The method as recited in  claim 11 , further comprising:
 determining if the device malfunction is due to a manufacturing defect or a design defect if it is determined that the improper manner of operation of the portable electronic device by the user is not the likely cause of the device malfunction. 
 
     
     
       13. The method as recited in  claim 10 , further comprising:
 determining if a repair operation to correct the device malfunction is covered by a manufacturer warranty if it is determined that the improper manner of operation of the portable electronic device by the user is the likely cause of the device malfunction. 
 
     
     
       14. The method as recited in  claim 9 , wherein the monitoring is carried out by a plurality of sensing devices each adapted to monitor a corresponding physical status data. 
     
     
       15. The method as recited in  claim 14 , wherein the plurality of sensing devices includes at least a temperature sensing device, or an accelerometer, or a battery charging sensing device. 
     
     
       16. An automated troubleshooting guide of a portable electronic device to evaluate a cause of a malfunction in the operation of the portable electronic device and to provide a corrective action, comprising:
 in the portable electronic device; 
 a sensing circuit adapted to monitor a physical status of the portable electronic device and generate corresponding physical status data; 
 a recording device coupled with the sensing circuit adapted to record the physical status data received from the sensing circuit; and 
 a processor coupled to the recording device, wherein the processor provides a fault analysis based on at least recorded physical status data retrieved from the recording device, wherein the fault analysis includes at least a fault analysis summary, wherein the fault analysis summary includes at least an indication of a detected fault that renders the portable electronic device at least partially inoperative and an indication of a corrective action. 
 
     
     
       17. The automated troubleshooting guide as recited in  claim 16 , wherein when a fault analysis summary request is provided to the portable electronic device, the processor responds to the fault analysis summary by providing the requested fault analysis summary in real time. 
     
     
       18. The automated troubleshooting guide as recited in  claim 17 , wherein the user of the portable electronic device provides the fault analysis summary request. 
     
     
       19. The automated troubleshooting guide as recited in  claim 16 , wherein the user of the portable electronic device uses the corrective action to correct the detected fault without requiring customer service intervention. 
     
     
       20. A method of automatically providing a troubleshooting guide of a portable electronic device to evaluate a cause of a malfunction in the operation of the portable electronic device and to provide a corrective action, comprising:
 in the portable electronic device; 
 monitoring a physical status of the portable electronic device; 
 generating corresponding physical status data based on the monitoring; 
 recording the physical status data; and 
 providing a fault analysis based on at least recorded physical status data, wherein the fault analysis includes at least a fault analysis summary, wherein the fault analysis summary includes at least an indication of a detected fault that renders the portable electronic device at least partially inoperative and a corrective action. 
 
     
     
       21. The method as recited in  claim 20 , wherein when a fault analysis summary request is provided to the portable electronic device, the processor responds to the fault analysis summary by providing the requested fault analysis summary in real time. 
     
     
       22. The method as recited in  claim 21 , wherein the user of the portable electronic device provides the fault analysis summary request. 
     
     
       23. The method as recited in  claim 22 , wherein the user of the portable electronic device uses the corrective action to correct the detected fault without requiring customer service intervention.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This patent application is a continuation of and claims priority under 35 USC 120 to U.S. patent application Ser. No. 11/680,580 entitled “EVENT RECORDER FOR PORTABLE MEDIA DEVICE” by Tupman et al. filed on Feb. 28, 2007, presently issued as U.S. Pat. No. 7,589,629 on Sep. 15, 2009, that is incorporated by reference for all purposes. 
    
    
     FIELD OF INVENTION 
     The present invention relates generally to portable electronic devices. More particularly, the present invention relates to sensing devices used to record events that affect the operability of portable electronic devices. 
     DESCRIPTION OF RELEVANT ART 
     The small size and lightweight of many popular portable electronic consumer products (media players, cell phones, laptops) make such products particularly susceptible to events (e.g., dropping, immersion in water, exposure to temperature extremes, humidity, etc.) that can render them either completely or partially inoperable. For example, a severe shock or vibration can render display elements of a display on a portable electronic device inoperative. Sometimes, as a result, a user may request that the manufacturer repair the damaged device. Moreover, the user may also request that such repairs be made free of charge if the user believes the damage is a result of a product design defect or covered by a manufacturer&#39;s warranty. 
     It is therefore important for the manufacturer to be able to determine if the damage to the device was caused by product defect or by warranty voiding user actions. Such user actions include, for example, abusive behavior (e.g., immersion in water, dropping, throwing, etc.), unauthorized opening of the device housing, improper battery charging, etc. By being able to determine the likely cause of the damage, the manufacturer can distinguish defects from improper use. By recording relevant information, the manufacturer can also save the time and expense of dealing with device owners who may or may not understand the source of the problem. 
     Therefore it is desirable to be able to record an event in a portable electronic device that can be used to, at least, evaluate an operational status of a portable electronic device such as a hand-held, wearable, and other miniature device. 
     SUMMARY 
     The invention pertains to methods, systems, and apparatus for recording an event and associated event data in a portable electronic device. The recorded event data can be used at least to evaluate an operational status of a portable electronic device such as media players, cell phones, laptop computers, and the like. In one embodiment, the portable electronic device includes appropriate event monitoring and recording capabilities that can take the form of a standalone sensing unit. By providing monitoring and recording capabilities, more efficient and accurate fault analysis can be provided that, in turn, can facilitate product design and may reduce cost of repair by more clearly delineating if any recorded event (usually user initiated) has voided a current product warranty. 
     Several embodiments of the invention are discussed below. 
     As a method for recording an event in a portable electronic device the method is carried out by performing at least the following operations: monitoring the portable electronic device for at least one physical occurrence expressed as a parameter having a parameter value; designating the physical occurrence as an event when the associated parameter value reaches or exceeds a parameter threshold value; and recording event data corresponding to the event. In one aspect of the invention, the recorded event data can be used to evaluate the operational status of the portable electronic device. 
     As a portable electronic consumer product, one embodiment of the invention includes, at least: a sensing unit arranged to monitor the consumer electronic product for at least one physical occurrence expressed as a parameter having a parameter value; a processor coupled to the sensing unit arranged to, at least, receive the parameter value from the sensing unit and designate the physical occurrence as an event when the parameter value reaches or exceeds a parameter threshold value; and a recording device coupled to the processor arranged to, at least, record event data corresponding to the event. 
     As computer program product executable by a processor for recording an event in a portable electronic device, one embodiment of the invention includes at least: computer code for monitoring the portable electronic device for at least one physical occurrence expressed as a parameter having a parameter value; computer code for designating the physical occurrence as the event when the associated parameter value reaches or exceeds a parameter threshold value; computer code for recording event data corresponding to the event; and computer readable medium for storing the computer code. 
     As a system, one embodiment of the invention includes at least: a portable electronic consumer product, having a sensing unit arranged to monitor the consumer electronic product for at least one physical occurrence expressed as a parameter having a parameter value; a processor coupled to the sensing unit arranged to, at least, receive the parameter value from the sensing unit and designate the physical occurrence as an event when the parameter value reaches or exceeds a parameter threshold value; a recording device coupled to the processor arrange to, at least, record event data corresponding to the event, and an external circuit in communication with at least the portable electronic consumer product arranged to evaluate the current operational status of the portable electronic consume product using the recorded event data. 
     Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  illustrates an example of a data-gathering device (sensor) in the form of sensing unit in accordance with an embodiment of the invention. 
         FIG. 2  shows a representative response of sensor to the monitoring of a continuously variable parameter (such as temperature) in accordance with an embodiment of the invention. 
         FIG. 3  shows a representative response of a sensor to the monitoring of a short duration event (such as an impact) in accordance with an embodiment of the invention. 
         FIG. 4  shows portable media player in accordance with an embodiment of the invention. 
         FIG. 5  shows a system having an evaluator unit for evaluating recorded event data in accordance with an embodiment of the invention. 
         FIG. 6  shows a flowchart detailing a process for real time monitoring in accordance with an embodiment of the invention. 
         FIG. 7  illustrates a flowchart detailing a process used for updating threshold values in accordance with an embodiment of the invention. 
         FIG. 8  shows a flowchart detailing a process for evaluating an operational status of a portable electronic device in accordance with an embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION 
     Reference will now be made in detail to selected embodiments of the invention, an example of which is illustrated in the accompanying drawings. While the invention will be described in conjunction with selected embodiments, it will be understood that it is not intended to limit the invention to one particular embodiment. To the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims. 
     A portable electronic device can suffer loss of function due to manufacturing or product defects or user events. Such user events can include exposing the device to extreme temperatures (either high or low) or exposing the device to physical shock or stress (e.g., dropping the device or attempting to open the device housing). Other potentially damaging events include improper use of the device over an extended period of time (e.g., improper battery charging, repeatedly dropping the device). Since the occurrence of a single event may not, in itself, cause damage it may be necessary to record multiple events to distinguish between user and manufacturer related damage. For example, dropping the device once or even twice may not result in damage to the device, but numerous shocks over an extended time can have a cumulative effect that can result in the device being damaged. In addition to isolated events, a user may be operating the device in a manner that can damage the device or otherwise reduce its useful operating life. For example, if the user does not properly charge the battery, then the battery lifetime can be severely reduced. 
     It is also desirable for both the user and manufacturer that when such events are recorded, that a warning notice be issued that informs the user that a potentially damaging event has just occurred (i.e., the device has been dropped), or has occurred a number of times (i.e., the device has been repeatedly dropped), or that the user is operating the device in an improper manner (i.e., improperly charging the battery). In this way, not only does the manufacturer have the data to help determine the likely cause of damage, the user is put on notice that the device is being operated by the user in a manner that can result in damage to the device. 
     Generally, the invention relates to monitoring at least one parameter in a portable electronic device (e.g., a cell phone, laptop, or media player). An event occurs when a monitored parameter value reaches or exceeds a pre-determined threshold value. Event data can be recorded and subsequently analyzed (by a manufacturer, for example) to evaluate an operating status of the portable electronic device. For example, if the portable electronic device is not operating properly (or at all) or has been damaged in some way, the event data can be used to determine a likely cause of the device malfunction and/or device damage. Furthermore, in those situations where an event has been improperly or only partially recorded (due, for example, to the device failing during the recording or a defective recording device or a recording device that becomes defective due to the event being recorded and so on), the partially or improperly recorded data can be used to evaluate the current operational status of the device. For example, if an event occurs (such as a device being dropped) while another event (temperature over or under limit, for example) is being recorded, any event data in the process of being or already having been recorded can be corrupted leaving only a portion of the recorded data available for subsequent evaluation. In these situations, the uncorrupted data can be retrieved and used to evaluate the current operational status of the device. 
     Furthermore, a warning notice can be timely issued notifying a user that an event (or events) has occurred that may result in damage to the device if corrective actions are not taken. Sensors that can be used in embodiments of this invention include temperature sensors, pressure sensors, stress/strain sensors, accelerometers, shock sensors, vibration sensors, position sensors, sensors that detect thermal exposure, optical exposure, x-ray exposure, microwave exposure, pollutants, and the like many of which are commercially available. 
       FIG. 1  illustrates an example of a data-gathering device in the form of sensor  100  in accordance with an embodiment of the invention. Sensor  100  can include processor  102  for controlling the overall operation of sensor  100 . Sensor  100  can also include memory resources  103  that can include RAM  104  that can provide volatile data storage and Read-Only Memory (ROM)  106  that can store programs, utilities or processes each of which can be coupled to processor  102  by way of data bus  108 . Sensor  100  can also include input/output device  110  that can allow an external circuit (such as an external processor or an evaluator unit) to interact with sensor  100 . For example, input/output (I/O) device  110  can include wired data port  112  that can communicate with an external signal cable by way of a connector (not shown). I/O device  110  can also include wireless interface  114  that can provide a wireless communication channel that can be used for transmission and receiving data between sensor  100  and external circuitry. Such communication channels can be formed using, for example, RF carrier waves, infrared (IR) signals, etc. 
     Sensor  100  can also include sensing device(s)  116  that can detect a change in a parameter (expressed as a parameter value) associated with the one or more physical occurrences. Therefore, sensing device  116  can have a dynamic range that covers the expected parameter value of the physical occurrence to be monitored and can withstand the operating conditions to which it may be exposed. For example,  FIG. 2  shows a representative response of sensing unit  116  to the monitoring of a physical occurrence (exposure to heat/cold) expressed as continuously variable parameter (i.e., temperature) in accordance with an embodiment of the invention. In the context of this discussion, an event occurs whenever a physical occurrence has a parameter value that reaches or exceeds a parameter threshold P th . For example, event A can be said to occur when processor  102  determines that parameter value P (received from sensing unit  116  in the form of sensing signal S) exceeds parameter threshold P th  (at time t A0 , for example) for at least a duration of time (t A1 -t A0 ). Similarly, event B can be said to occur when processor  102  determines that parameter value P exceeds parameter threshold P th  (at time t B0 , for example) for at least a duration of time (t 14 -t B0 ). Some sensors (or corresponding constituent sensing units), however, are more suited for monitoring events of a discontinuous nature (such as an impact having a short or indeterminate duration) an example of which can be seen in  FIG. 3 . In these cases, an event can be said to occur when processor  102  determines that parameter value P has reached or exceeded the parameter threshold value P th  at a time t a  and/or t b . 
     Once processor  102  has determined that an event has occurred, processor  102  can process sensing data S received from sensing unit  116  into associated event data  118  that can then be forwarded and stored event log  120  in recording device  122 . Event data  118  can include time of occurrence, date of occurrence, duration of occurrence, maximum (or minimum) parameter value, and so on. For example, in  FIG. 2 , event data  118  can include information related to a difference between parameter threshold value P th  and maximum parameter value P max  (for example, with respect to event A, event data  118  can include information related to the difference between P Amax -P th ) or more simply as a maximum value of parameter value P during a particular event (P Amax  or P Bmax , for example). 
     If recording device  122  is electronic in nature (such as volatile memory devices), then event data  118  can be recorded as a change in bit values of the memory device whereas if recording device  122  is electro-mechanical or mechanical in nature, then event data  118  can be recorded as a non-reversible state change (such as the melting of a fuse, etc.). Examples of recording devices include electrical circuits, electromechanical circuits, mechanical latching mechanisms, programmable integrated circuits such as EPROMs, fusible links, magnetic circuits, acoustic circuits, optical/IR circuits, and the like. It should be noted that event data  118  could be stored in any appropriate memory device located either within sensor  100  or external to sensor  100 . 
     In some cases, in order to preserve power resources (which is especially important in battery powered electronic devices), recording device  122  can be configured to record an event in a non-reversible manner (such a melting of a thermocouple to indicate extreme temperature, or discoloration of a moisture sensitive tab to indicate high moisture). In this case “recording” usually means that some mechanical aspect of recording device  122  has changed in a non-reversible manner. In this way, even if sensor  100  becomes inoperable for whatever reason, an event can still be recorded even if sensor  100  is not powered or otherwise inoperable. For example, recording device  122  can be implemented as an electrical circuit having a particular resonance frequency in communication with sensing device  116  that can be a fuse in one leg of the circuit. 
     Furthermore, sensor  100  can be placed in an inactive, or sleep mode. However, in order to record event data when a parameter value (temperature, for example) passes a threshold value, sensor  100  can be activated (e.g., woken up). For example, if all that is required is that a temperature excursion (either hot or cold) be recorded, it is not necessary for sensor  100  to continually monitor the temperature of the device. All that is necessary is that at least one sensing unit  116  in sensor  100  provide appropriate notification to processor  102  that the monitored temperature has reached or exceeded the temperature threshold at which point processor  102  can wake up sensor  100  and complete the recordation of the event. Once the recordation of the event is complete, processor  102  can put sensor  100  back into sleep mode. By providing for a low power operational mode, valuable power resources can be preserved while still maintaining the ability to monitor parameters of interest. 
     It should be noted that if sensor  100  includes more than one sensing device, each sensing device could be configured to monitor different parameters, or the same parameter having different parameter threshold values in a cascade arrangement, or even different event types (e.g.; continuously variable type or impact type). In any case, each of the sensing devices can be placed in either active or sleep mode depending upon the particular event type, parameter to be monitored, and so on for which it is configured to monitor. For example, one sensing device can be configured to continuously monitor temperature and therefore be set to active mode whereas another sensing unit can be configured to concurrently monitor impacts and therefore can be set to low power mode. In this way, sensor  100  can be used to monitor separate parameters and provide corresponding event data that can be used in subsequent analysis either separately or together. For example, a piezoelectric strain sensor for measuring material strain (indicative of rough handling) can be used to determine if a device has undergone an impact type event. A temperature sensor can also be used to record any temperature events experienced by the device. The data provided by both sensing devices can be used separately or together (using cross correlation type analysis, for example) to determine if, for example, stress damage to a device housing was likely due to externally applied forces (i.e., if an impact event has been recorded but no temperature event) or related to thermal expansion/contraction (i.e., if temperature event has been recorded but no impact event). Subsequent analysis of any or all available data can be used to evaluate a likely cause of any damage or non-functionality of a device. 
     The invention will now be described in the context of a portable electronic consumer product that for the remainder of the discussion takes the form of a portable media player  400  that at least incorporates sensor  100 . 
       FIG. 4  shows portable media player  400  in accordance with an embodiment of the invention that can include central processing unit (CPU)  402  for controlling the overall operation of media player  400 . Media player  400  can store media data pertaining to media assets in file system  404  and/or cache  406 . File system  404  can take the form of a storage disk or a plurality of disks that can provide high capacity storage capability for the media player  400 . However, since the access time to file system  404  can be relatively slow, media player  400  can also include cache  406 . Even though the relative access time to cache  406  can be substantially shorter than for file system  404 , cache  406  typically does not have the large storage capacity of file system  404 . Media player  400  can also include memory resources  408 . In the described embodiment, memory resources can be configured to include RAM  410  (that can store programs, utilities or processes to be executed in a non-volatile manner) and Read-Only Memory (ROM)  412  that can store programs, utilities or processes to be executed in a non-volatile manner. Data bus  414  can facilitate data transfer between at least file system  404 , cache  406 , CPU  402 , and CODEC  416 . Media player  400  can also include data link  418  allowing media player  400  to couple to a host computer, for example. Media player  400  includes display  420  for displaying graphical, video, or images, user input  422  for receiving user supplied input commands, and speakers  424 . 
     Sensor  100  can be configured as a stand-alone type unit along the lines described with respect to  FIG. 1  and, as such, can be connected to CPU  402  by way of data bus  414 . Sensor  100  can also have its own power supply (not shown) independent of that provided for media player  400 . In this way, sensor  100  can monitor selected parameters and communicate with external circuitry when media player  400  is powered off or has been rendered inoperable. Sensor  100  can also be integrated with CPU  402  providing a less robust, but more cost effective embodiment since all memory and processing requirements of sensor  100  can then be performed by memory resources  408  and CPU  402 , respectively. It should be noted, by utilizing on board memory resources (either memory resources  103  or memory resources  408 ), various threshold values used to determine whether an event has or has not occurred can be updated in a timely manner. 
       FIG. 5  shows a system  500  used to evaluate recorded event data in accordance with an embodiment of the invention. Evaluation of recorded event data by system  500  can be put to any number of uses such as providing a repair technician information related to a likely cause of a device malfunction or defect. This information can be used to repair the device and/or inform the device owner that any repairs would or would not be covered by a warranty. For example, if the evaluation reveals that the damage to the device or device malfunction was most likely caused by improper use by the device user, then any repairs would most likely not be covered by a manufacturer warranty or at least would be at the option of the manufacturer. 
     Accordingly, when media player  400  is brought into a repair center, for example, for evaluation and possible repair, a repair technician can power on evaluator unit  502  that includes processor  504  for controlling operations of evaluator unit  502  and display  506  for displaying user interfaces and other relevant information/data. Once evaluator unit  502  is powered on, evaluation program  508  (typically stored in evaluator unit memory not shown for sake of clarity) can instruct processor  504  to orchestrate the evaluation process that can include, at least, displaying an evaluation interface  510  on display  506 . At this point, as part of the evaluation process, a repair technician can be requested to follow a set of specific instructions as part of the evaluation interface  510 . Such instructions can include, at least, visually inspecting the device and/or device housing for any external damage (a cracked housing, for example), entering a trouble code (or its equivalent) indicating the nature of the device problem if known, powering up the device (if possible), and so on. If media player  400  can not be powered up (due to a faulty power supply, for example), it may be necessary to connect evaluator unit  502  directly to sensor  100  by way of signal cable  512  or by way of wireless channel  514  if sensor  100  has wireless capabilities using RF, acoustic, or any appropriate wireless signal. Clearly, if media player  400  cannot provide power to sensor  100 , then sensor  100  must be self powered or at least be able to receive power from an external power supply. In some cases, however, sensor  100  can be configured in such a way that recording device  122  can be detachable or otherwise accessible to external circuitry in such a way that any recorded event data can be retrieved without either sensor  100  or media player  400  providing any power whatsoever. 
     In any case, once evaluator unit  502  is in communication with sensor  100  by way of I/O  110  (or indirectly by way of I/O  410  if media player  400  is active), evaluation program  508  instruct processor  504  to send event data request  516  to sensor  100  for processing by processor  102 . Processor  102  can, in turn, respond to event data request  516 , in part, by transmitting device identifier  518 . Device identifier  518  can provide any information that evaluation program  508  might require in order to carry out the evaluation process. For example, device identifier  518  can include information used to distinguish media player  400  from other, similar media players. In some embodiments, evaluation program  508  can use device identifier  518  to determine if media player  400  has had any previous repair sessions and if so retrieve data from those previous repair sessions stored in a server computer, for example, connected to evaluator unit  502  as part of a network of computers. In addition to device identifier  518 , processor  102  can be programmed to provide event data  118  from recording device  122  without waiting for a specific data request from evaluation program  508 . In any case, once evaluation program  508  has received event data  118 , evaluation program  508  can use event data  118  to evaluate the current operational status of media player  400  that could include determining a likely cause of a device defect or device malfunction. For example, one type of analysis that can be carried out by evaluation program  508  can be based upon pattern analysis where a pattern of occurrence of a particular event (such as repeated improper battery charging, repeated impacts, etc.) can be correlated to observed defects or operational problems with media player  400 . Another type of analysis that can be carried out by evaluation program  508  can be based upon performing a correlation analysis between certain aspects of event data  118  to known problems and their causes. For example, if it is observed that a battery in media player  400  cannot hold a proper charge and event data indicates that a user of media player  400  is not following proper charging procedures, then in all likelihood, that is the cause of the battery not holding a charge. Another example could be that event data  118  indicates that a number of warning notices have been issued by media player  400  over a period of time indicating that the media player  400  has, for example, been exposed to temperature extremes, repeated shocks, improper battery charging, etc. If media player  400  is exhibiting a problem that has been previously linked to any of the events associated with the issued warning(s), then a conclusion could be that the observed problem with media player  400  is due to that event(s) and not a design or product defect. In this case, a manufacturer could realistically decline to repair media player  400  under a manufacturer warranty. In any case, when evaluation program  508  has completed its analysis, a fault summary  520  can be displayed on display  506  indicating at least a list of faults, causes and any corrective actions. 
     In some cases, a user can also invoke an embedded fault analysis program  522  that can provide simplified fault analysis generated by, for example, CPU  402 . In this way, real time fault analysis summary  524  along the lines of an automated trouble shooting guide can be provided to, for example, a user, repair technician, etc. on display  420 . Real time fault analysis summary  524  can provide specific fault codes indicating faults detected, recommended corrective actions, and so on. In this way, a user, for example, can consult use real time fault analysis  524  to diagnose and potentially correct the problem without the need to deal with customer service thereby greatly reducing any device downtime lost in transporting the damaged device to a repair center. 
       FIG. 6  shows a flowchart detailing a process  600  for real time monitoring of a portable electronic device in accordance with an embodiment of the invention. Process  600  begins at  602  by configuring a sensing device to monitor a selected physical occurrence that can be expressed as a parameter value. Configuring the sensing device can include setting, or resetting, a parameter threshold value, setting an operational mode (for example, low power mode, or sleep mode), connecting the sensing device to other sensing devices to form a cascade arrangement, and so on. Once the sensing device has been configured, the sensing device monitors for a pre-determined physical occurrence at  604  and generates sensing data (i.e., temperature, pressure, impact, stress, etc.) at  606  that can be expressed as a corresponding parameter value (° F., nt/cm 2 , etc). If, at  608 , the parameter value reaches or exceeds a corresponding parameter threshold value, then an event flag is issued at  610  indicating that an event has occurred. At  612 , corresponding event data is recorded. Event data can include time of occurrence, date of occurrence, duration of occurrence, maximum (or minimum) parameter value, and so on. 
       FIG. 7  illustrates process  700  for updating parameter threshold values in accordance with an embodiment of the invention. Process  700  begins at  702  by retrieving stored parameter threshold values. At  704 , current parameter threshold values are compared to stored parameter threshold values. At  706 , based upon the comparison, any stored parameter threshold value not matching current parameter threshold values can be updated. 
       FIG. 8  illustrates a flowchart detailing a process  800  for evaluating an operational status of a portable electronic device in accordance with an embodiment of the invention. Process  800  begins at  802  establishing a communication link between the portable electronic device and an evaluation program. In the described embodiment, the evaluation program can be executed by a processor included in an external circuit that can be separate and distinct from the portable electronic device. The evaluation program can also be executed by a processing unit that is part of the portable electronic device under evaluation along the lines of a virtual troubleshooting guide. In any case, once the communication link has been established, a current operational status (that can include operational problems, defects, and so on) of the portable electronic device can be provided to the evaluation program at  804 . The evaluation program can request a manual entry of the current operational status by, for example, a repair technician, a user, and so on. The evaluation program can also request the portable electronic device automatically provide information over the communication link indicative of the operational status of the portable electronic device. Such operational problems can include the inability of the portable electronic device to power up properly or power up at all, some or all of the components (speakers, display, and so on) are not functioning properly, the battery (if the portable electronic device is battery powered) is not holding a proper charge or not holding a charge for as long as expected, etc. 
     At  806 , a determination can be made if any recorded event data is available. If no recorded event data is available, then processing ends, otherwise, any recorded event data can be passed to the evaluation program at  808 . At  810 , the evaluation program analyzes the operational status in view of the event data. Analysis of the event data can include pattern analysis, correlation analysis, and evaluation of any warning notices that have been issued and if there is any correlation to any operational problems. At  812 , once the evaluation program has completed the analysis, a summary report is issued. The summary report can include information about the operational status of the portable electronic device pointing out likely causes of any problems. In some cases, the summary report can include a probability analysis indicating a probability distribution of likely causes of any operational problems. For example, if the portable electronic device is experiencing short battery life and the event data indicates a history of improper battery charging, then there would be a high probability that the improper battery charging practices is the root cause of the reduced battery life and not a defective battery. In this case, since the likely cause of the reduced battery life stems from the user, a manufacturer can refuse to repair or replace the defective battery under a manufacturer&#39;s warranty. 
     While this invention has been described in terms of a preferred embodiment, there are alterations, permutations, and equivalents that fall within the scope of this invention. It should also be noted that there are many alternative ways of implementing both the process and apparatus of the present invention. It is therefore intended that the invention be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.

Metadata:
Filing Date: 20090804
Publication Date: 20111025
Grant Date: 20111025
Priority Date: 20070228
Inventors: TUPMAN DAVID
FADELL ANTHONY
Assignee: APPLE INC
CPC Classifications: [{"code": "G11B20/18", "inventive": true, "first": true, "tree": "[]"}, {"code": "G11B27/36", "inventive": true, "first": false, "tree": "[]"}, {"code": "G11B27/36", "inventive": true, "first": false, "tree": "[]"}, {"code": "G11B20/18", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 39715238