Messaggio trovato oggi nel sito del distributore musicale Feiyr.com (Germania):
“In base alle nuove linee guida universali di iTunes, d´ora in avanti le cover devono essere create e caricate nella dimensione minima di 3000 x 3000 Pixel (max. 4000 x 4000, 10 MB).
Questo purtroppo riguarda anche i bundle attualmente in fase di approvazione.” Continua…
Sony rilancia la tecnologia di PS Vita con una console piccolissima. E sfida la Mela
Uscirà in Giappone il prossimo 14 novembre, costerà 9.480 yen, pari a 95 dollari circa o poco più di 140 dollari per la versione con controller DualShock 3 e memory card da 8Gb. Sarà una console microscopica (soli 6×10 centimetri, le dimensioni di certe batterie o hard-disk) e allo stesso tempo sarà nella fascia di prezzo di Apple TV: è PlayStation Vita TV, la mossa a sorpresa di Sony. La più piccola PlayStation di tutti i tempi, ma non solo il modo per giocare con i titoli per PS Vita sul proprio televisore. Continua…
United States Patent Application 20130021152
Kind Code A1
Vock; Curtis A. ; et al. January 24, 2013
SHOE WEAR-OUT SENSOR, BODY-BAR SENSING SYSTEM, UNITLESS ACTIVITY ASSESSMENT AND ASSOCIATED METHODS
Abstract
A body bar sensing system for sensing movement of a body bar may be provided. The body bar sensing system may include a housing having a coupling mechanism operative to couple to the body bar, a detector disposed within the housing and operative to sense movement of the body bar when the housing is coupled to the body bar, and a processor operative to determine a number of repetitions of the movement based on the sensed movement. The body bar sensing system may also include a display operative to display the determined number of repetitions of the movement to a user.
Inventors: Vock; Curtis A.; (Boulder, CO) ; Youngs; Perry; (Longmont, CO)
Assignee: APPLE INC.
Cupertino
CA
Serial No.: 544733
Series Code: 13
Filed: July 9, 2012
Current U.S. Class: 340/539.11; 340/540
Class at Publication: 340/539.11; 340/540
International Class: G08B 21/00 20060101 G08B021/00; G08B 1/08 20060101 G08B001/08
Claims
1-25. (canceled)
26. A body bar sensing system, comprising: a housing having at least one detector for sensing a physical metric that indicates repeated movement of the housing when attached to the body bar; a processor configured to process the physical metric, over time, to determine repetitions thereof; and a display for informing a user of the repetitions.
27. The system of claim 26, further comprising a wireless transmitter with the housing and a watch, with a wireless receiver, remote from the housing, wherein the user views repetition information at the watch.
28. The system of claim 26, further comprising a wireless transmitter with the housing and one of a MP3 player and cell phone, with a wireless receiver, remote from the housing, wherein the user views repetition information at the MP3 player or cell phone.
29. The system of claim 26, further comprising a clamp, integrated with the housing, to retain weights on the body bar.
30-43. (canceled)
44. A body bar sensing system for sensing movement of a body bar, the body bar sensing system comprising: a housing having a coupling mechanism operative to couple to the body bar; a detector disposed within the housing and operative to sense movement of the body bar when the housing is coupled to the body bar; and a processor operative to determine a number of repetitions of the movement based on the sensed movement.
45. The body bar sensing system of claim 44, wherein the detector comprises an accelerometer.
46. The body bar sensing system of claim 44, wherein the detector is further operative to output the sensed movement as an acceleration value.
47. The body bar sensing system of claim 44, wherein the detector comprises a Hall effect sensor.
48. The body bar sensing system of claim 44, wherein the detector is operative to sense the movement by detecting inversion of the body bar.
49. The body bar sensing system of claim 44 further comprising a display operative to display the determined number of repetitions of the movement.
50. The body bar sensing system of claim 49, wherein the display is remote from the housing.
51. The body bar sensing system of claim 44 further comprising a speaker operative to output at least one sound based on the determined number of repetitions of the movement.
52. The body bar sensing system of claim 51, wherein the at least one sound comprises at least one voice annunciation.
53. The body bar sensing system of claim 52, wherein the coupling mechanism is further operative to retain at least one weight to the body bar when the body bar sensing system is coupled to the body bar.
54. A method for detecting repetitive movements of a body bar using a motion sensing system, the method comprising: detecting a physical metric associated with the body bar; processing the detected physical metric to determine whether the detected physical metric indicates a repetitive motion of the body bar; determining a current number of repetitive movements of the body bar based on the processing; and providing the determined current number of repetitive movements to a user.
55. The method of claim 54, wherein the detecting comprises detecting an acceleration of the body bar.
56. The method of claim 54, wherein the processing comprises detecting when the body bar is at least one of raised and lowered within a predefined time interval.
57. The method of claim 54, wherein the detecting comprises detecting an inversion of the body bar.
58. The method of claim 54, wherein the providing comprises displaying the determined current number of repetitive movements.
59. The method of claim 54, wherein the providing comprises transmitting the determined current number of repetitive movements to an external device.
Description
RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional application No. 60/728,031, incorporated herein by reference.
BACKGROUND
[0002] Shoes (including sneakers or boots, for example) provide comfort and protection for feet. More importantly, shoes provide physical support for feet to reduce risk of foot injuries. A shoe is often necessary to provide support during intense physical activity, such as running, soccer and American football. As a shoe wears, physical support provided by the shoe decreases, thereby reducing associated protection from injury. When a critical wear level is reached, even if the shoe looks like it is not particularly worn, the shoe may not provide adequate support and may, in fact, cause damage to feet.
SUMMARY
[0003] In one embodiment, a shoe wear out sensor includes at least one detector for sensing a physical metric that changes as a shoe wears out, a processor configured to process the physical metric, over time, to determine if the shoe is worn out, and an alarm for informing a user of the shoe when the sole is worn out.
[0004] In another embodiment, a system determines the end of a shoe’s life. Use of the shoe is sensed by at least one detector. A processor is configured to measure the use of the shoe and to determine if the shoe is worn out. An alarm informs a user of the shoe when the shoe is worn out.
[0005] In another embodiment, a body bar sensing system includes a housing with at least one detector for sensing a physical metric that indicates repeated movement of the housing when attached to the body bar, a processor configured to process the physical metric, over time, to determine repetitions thereof, and a display for informing a user of the repetitions.
[0006] In another embodiment, a system assesses activity and displaying a unitless activity value and includes a detector for sensing activity of a user of the system, a processor for processing sensed activity data from the detector, a display for displaying the unitless activity value, and an enclosure for housing the detector and the processor. The processor periodically reads the sensed activity data from the detector and processes the data to generate an activity number, the number being used to generate the unitless activity value based upon a maximum number and a display range.
[0007] In another embodiment, a method determines a unitless activity value for a desired period of activity. A period accumulator is cleared prior to the start of the activity period. A detector is periodically sampled to obtain data that is processed to determine a number representative of the sampling period. The number is added to the period accumulator. The unitless activity value is then determined based upon the period accumulator, a maximum activity number and a display range. The unitless activity value is then displayed. The sampling, processing and adding are repeated until data is sampled for the desired period of activity.
[0008] In another embodiment, a method assesses activity unitlessly by detecting motion of a user, processing the detected motion, over time, to determine an activity value, ratioing the activity value to a maximum activity value, and reporting a scaled unitless activity value to the user based upon the ratio and a scale.
[0009] A software product has instructions, stored on computer-readable media, that, when executed by a computer, perform steps for determining a unitless activity value for a desired period of activity, including instructions for: detecting motion of a user, processing detected motion, over time, to determine an activity value, ratioing the activity value to a maximum activity value, and reporting a scaled unitless activity value to the user based upon the ratio and a scale.
BRIEF DESCRIPTION OF THE FIGURES
[0010] FIG. 1 shows one exemplary embodiment of a shoe wear-out sensor.
[0011] FIG. 2 shows one exemplary embodiment of a shoe with a shoe wear out sensor.
[0012] FIG. 3 shows another exemplary embodiment of a shoe with a shoe wear out sensor.
[0013] FIG. 4A shows one exemplary process for determining shoe wear out.
[0014] FIG. 4B shown one exemplary process for determining shoe wear out.
[0015] FIG. 4C shows one exemplary process for determining shoe wear out.
[0016] FIG. 4D shown one exemplary process for determining shoe wear out.
[0017] FIG. 5 shows one body bar sensing system embodiment.
[0018] FIG. 6 shows one part of an exemplary body bar with a body bar sensing system embodiment attached.
[0019] FIG. 7 shows one part of a body bar in an embodiment showing a weight and a body bar sensing system that secures the weight onto the body bar.
[0020] FIG. 8 shows one exemplary process for reporting body bar usage.
[0021] FIG. 9 shows an embodiment of a sensor that unitlessly assesses activity.
[0022] FIG. 10 shows a process for unitlessly determining activity.
DETAILED DESCRIPTION OF THE FIGURES
[0023] FIG. 1 shows one shoe-wear out sensor 100. Sensor 100 includes a processor 102, a detector 104 and an alarm 106. A battery 108 may be used to power processor 102, detector 104 and alarm 106; alternatively, a magnetic coil generator (not shown) or other mechanical motion-to-electricity conversion device may be employed with sensor 100 to power these elements. Detector 104 is for example an accelerometer and/or a force sensing resistor (FSR). Alarm 106 is for example a light emitting diode (LED) and/or a small speaker and/or a small sound actuator (e.g., a buzzer, piezoelectric beeper etc).
[0024] FIG. 2 shows a shoe 200 with a shoe-wear out sensor 210. Shoe 200 is for example a running or sport shoe, boot (e.g., a snowboard or hiking boot), slipper, dress shoe or flip-flop; shoe 200 may alternatively be an orthopedic shoe for providing special foot support. Sensor 210 may represent sensor 100, FIG. 1. In the illustrated embodiment, shoe 200 has a sole 202 and an upper part 204. Sole 202 has an outsole 206 and a heel 208. Sensor 210 is shown contained within heel 208; however sensor 210 may be placed elsewhere within or on the shoe to function similarly.
[0025] FIG. 3 shows one exemplary embodiment of a shoe with a shoe-wear out sensor 310. Sensor 310 may again represent sensor 100, FIG. 1. Shoe 300 is shown with a sole 302 and an upper part 304. Sole 302 has an outsole 306 and a heel 308. Shoe 300 may again represent, for example, a running shoe, sports shoe or orthopedic shoe (or other type of shoe or boot). Electronics 310a of sensor 310 are shown contained within heel 308; but detector 312 is shown located within outer sole 306, illustrating that the elements of sensor 100 (FIG. 1) may be dispersed to various locations of the shoe while providing similar functionality. Detector 312 is for example detector 104, FIG. 1; it may thereby be a force sensing resistor and/or a piezoelectric foil that is electrically connected, via connection 314, to electronics 310 of sensor 310. If detector 312 is a piezoelectric foil (or other piezoelectric device), use of shoe 300 results in flexing of detector 312 which may generate sufficient electricity to power electronics of sensor 310, avoiding the need for battery 108.
[0026] FIGS. 1, 2 and 3 are best viewed together with the following description. Sensor 100 may be embedded in a shoe (e.g., sensors 210, 310 within shoes 200, 300) and configured to determine when that shoe has “worn out”. It then informs the user, via alarm 106, that it is time to buy a new shoe (usually a new pair of shoes). In an embodiment, alarm 106 is an LED 217 that is positioned at the outside of the shoe such that it may be seen, when activated, by the user of the shoe, as illustratively shown in FIG. 2.
[0027] Processor 102 may operate under control of algorithmic software 103 (which is illustratively shown within processor 102, though it may reside elsewhere within sensor 100, for example as stand alone memory of sensor 100). Algorithmic software 103 for example includes algorithms for processing data from detector 104 to determine when a shoe is worn out.
[0028] FIG. 4A for example illustrates one process 400 performed by processor 102 of FIG. 1. In step 402, processor 102 samples detector 104 to determine a physical metric associated with the shoe. In an example of step 402, detector 104 is an accelerometer and thereby provides acceleration data resulting from movement of the shoe upon a surface as the physical metric. For example, as the shoe strikes the ground when in use, processor 102 takes a plurality of samples using detector 104 to form an impact profile. In step 404, processor 102 processes the physical metric and compares it against a predetermined threshold, response curve or other data reference. In an example of step 404, processor 102 compares the impact profile determined from the accelerometer against an impact profile of a “new” shoe. In another example of steps 402, 404, the physical metric is power spectral density corresponding to certain frequencies of interest; and the power spectral density is compared, during use of the shoe, to a data reference containing power spectral density of a new or acceptably performing shoe. If the current data (i.e., physical metric) is too large or exceeds the data reference, for example, then processor 102 sets off alarm 106 (e.g., lights LED 217) in step 406. In one embodiment, upon first use of the shoe, processor 102 determines an impact profile of the new shoe that is then used (e.g., as the threshold or data reference) in comparison against subsequently determined impact profiles. Or, upon first use of the shoe, for example, processor 102 may store the appropriate data reference (e.g., power spectral density or threshold) for comparison against data captured in latter uses of the shoe. In this way, therefore, process 400 may be efficiently used to inform a user of shoe wear out.
[0029] As noted, data from detector 104 may be processed in the frequency domain (e.g., using Fourier transforms of data from detector 104) so as to evaluate, for example, power spectral density of the physical metric (e.g., acceleration or force), in step 404. In this manner, therefore, a range of frequencies may be evaluated (e.g., an area under the curve for certain frequencies may be integrated) from detector 104 and then compared to similar data (as the threshold) of a new shoe. As a shoe wears, the elasticity of the material from which it is made changes; thus the ability of the material to absorb the shock of the shoe contacting the ground deteriorates, resulting in more shock force being transferred to the foot within the shoe. By determining the increase of the shock force above the threshold, in this embodiment, the wear on the shoe may be determined.
[0030] We now specifically incorporate by reference the teachings and disclosure of: U.S. Pat. No. 6,539,336; U.S. Pat. No. 6,266,623; U.S. Pat. No. 6,885,971; U.S. Pat No. 6,856,934; U.S. Pat. No. 6,8963,818; U.S. Pat. No. 6,499,000; and U.S. application Ser. No. 10/297,270. These patents and applications provide useful background, power sensing and weight/movement monitoring techniques suitable for use with the teachings of this present application.
[0031] In an embodiment, similar to the embodiment of FIG. 3, processor 102 determines wear of shoe 300 based upon weight of the user of shoe 300. By using signals from detector 312 to determine an approximate weight of the user of shoe 300 (for example by using a pressure sensor and fluid-filled cavity as detector 104), processor 102 may determine a life expectancy of shoe 300. Since the wear on the shoe is roughly proportional to the weight applied by the wearer, during activity, by determining the weight of the wearer and the amount the shoe is used (e.g., how often and how long the shoe is used), processor 102 may thus determine shoe wear with increased accuracy. That is, a shoe used by someone who spends most of their time sitting at a desk receives less wear that a shoe used by someone who spends most of the day standing on their feet.
[0032] In another embodiment, by sensing when the shoe is used–or for how long–the teachings herein may instead be applied so as to set off the alarm after a term or time of use has expired. For example, if a shoe is specified for use to at least 100 hours or 500 miles (or other similar metric specified by the shoe manufacturer), then by sensing weight or acceleration (or other physical metric, via detector 104) that use may be determined; processor 102 then activates alarm 106 when the use is exceeded. For example, using one or more accelerometers as detector 104, speed of the shoe may be determined through operation of processor 102 using an appropriate algorithm within software 103; this processor 102 then uses the speed information to determine distance traveled and sets off alarm 106 when, for example, the manufacturer’s specified distance use is met. Illustratively, in another example, if the manufacturer specifies that the shoe may be used under normal conditions for 500 hours (or some other time), then detector 104 in the form of an accelerometer may determine when the shoe is in use; processor 106 then determines the period of use, over time (e.g., weeks and months) and sets off alarm 106 when the accumulated use exceeds the specified limit.
[0033] FIG. 4B for example illustrates one process 450 performed by processor 102 of FIG. 1 for determining shoe wear out. In step 452, processor 102 samples detector 104 to determine one or more physical metrics associated with the shoe. In an example of step 402, detector 104 includes a fluid filled cavity and a pressure sensor and thereby provides a signal representative of force upon the shoe (e.g., a value representative of the weight of the user of the shoe). For example, as the shoe is used, processor 102 takes a plurality of pressure reading from detector 104. In step 454, processor 102 determines an approximate weight upon the shoe based upon samples of step 452. In one example of step 454, processor 102 utilizes algorithms of software 103 to determine an approximate weight of the user of the shoe based upon pressure values sensed by detector 104. In step 456, process 102 determines the duration of the shoe’s use. In one example of step 456, processor 102 utilizes algorithms of software 103 to measure the duration that the shoe is used based upon readings from detector 104 and an internal timer of processor 102. In step 458, processor 102 determines the shoe use for the sample period of step 452. In one example of step 458, processor utilizes algorithms of software 103 to determine a use factor based upon the determined weight of step 454 and the duration of use of step 458. In step 460, processor 102 determines remaining life of the shoe based upon the determined shoe use of step 458. In one example of step 460, processor 102 maintains a cumulative value of usage determined in step 458 for comparison against a manufacturer’s expected usage of the shoe. In step 462, processor 102 enables alarm 106 if the shoe’s life is exceeded. Steps 452 through 462 repeat periodically throughout the life of the shoe to monitor shoe usage based upon wear determined from the weight of the user and the duration of use.
[0034] In the above description of process 450, it is not necessary that weight be determined. Rather, in an embodiment, it may instead be determined that the shoe is in “use” based on an algorithm using the pressure or force based detector 104; and then this use is accumulated time-wise to determine when the shoe’s life expectancy is exceeded. For example, once a user puts weight onto this detector (in this embodiment), then processor 102 detects (through use of an algorithm as software 103) that the shoe is in use due to the presence of weight onto detector 104.
[0035] FIG. 4C for example illustrates one process 470 performed by processor 102 of FIG. 1 for determining shoe wear out. In step 471, processor 102 samples detector 104 periodically over a defined period. In one example of step 471, detector 104 is an accelerometer that is sampled periodically by processor 102 over a period of ten seconds. In step 472, processor 102 determines if the shoe is in use. In one example of step 472, processor 102 utilizes algorithms of software 103 to process the samples of step 471 to determine if the shoe is in use. Step 473 is a decision. If, in step 473, processor 102 determines that the shoe is in use, process 470 continues with step 474; otherwise process 470 continues with step 475. In step 474, processor 102 adds a value representative of the defined period of step 471 to an accumulator. In one example of step 474, a non-volatile accumulator is incremented by one, where the one represents a period of ten seconds. Step 475 is a decision. If, in step 475, processor 102 determines that the shoe is worn out, process 470 continues with step 476; otherwise process 470 continues with step 471. In one example of the decision of step 475, processor 102 compares the use accumulator of step 474 against a value representative of the expected life of the shoe. Steps 471 through 475 repeat throughout the lifetime of the shoe. As appreciated, power saving measures may be used within sensor 100 when it is determined that the shoe in which sensor 100 is installed is not in use. In step 476, processor 102 enables alarm 106. In one example of step 476, processor 102 may periodically activate LED 217, FIG. 2, until battery 108 is exhausted.
[0036] Process 470 thus determines the wear on a shoe by measuring the amount of use and comparing it against the expected use defined by a manufacturer, for example. In an embodiment, the use accumulator of step 474 is a timer within processor 102. This timer is started when step 473 determines that the shoe is in use and is stopped when step 473 determines that the shoe is not in use. This timer thus accumulates, in real time, the use of the shoe for comparison against a manufacturer’s expected use. In another embodiment, step 472 may determine the number of steps a shoe has taken such that the use accumulator of step 474 accumulates the total number of steps taken by the shoe. This total number of steps is then compared to the manufacturer’s recommended number of steps expected in the shoes life time.
[0037] FIG. 4D illustrates one process 480 performed by processor 102 of FIG. 1 for determining shoe wear out. In step 481, processor 102 samples detector 104 periodically over a defined period. In one example of step 481, detector 104 is an accelerometer and processor 102 samples acceleration values over a period of 1 second. In step 482, processor 102 determines if the shoe is in use. In one example of step 482, processor 102 utilizes algorithms of software 103 to determine if characteristics of samples values of step 481 indicate that the shoe is in use. Step 483 is a decision. If, in step 483, processor 102 determines that the shoe is in use, process 480 continues with step 484; otherwise process 480 continues with step 486. In step 484, processor 102 determines a distance traveled over the defined period of step 481. In one example of step 484, processor 102 utilizes algorithms of software 103 to first determine speed of the shoe, and then determines distance covered in one second. In step 485, processor 102 accumulates the distance traveled. In one example of step 485, processor 102 adds the distance determined in step 484 to a total distance traveled accumulator. In one example, this accumulator is stored in non-volatile memory. Step 486 is a decision. If, in step 486, processor 102 determines that the shoe is worn out, process 480 continues with step 487; otherwise process 480 continues with step 481. In one example of step 486, processor 102 compares the total accumulated distance of step 485 against the manufacturer’s recommended maximum distance for the shoe. Steps 481 through 486 repeat throughout the lifetime of the shoe. As appreciated, power saving measures may be used within sensor 100 when it is determined that the shoe is not in use. In step 487, processor 102 enables alarm 106. In one example of step 487, processor 102 may periodically activate LED 217, FIG. 2, until battery 108 is exhausted. Process 480 thus determines shoe wear by measuring the distance traveled by the shoe, using one or more accelerometers, and compares that distance to a manufacturer’s recommended maximum distance for the shoe.
[0038] FIG. 5 shows a body bar sensing system 500. System 500 includes a housing 502, a processor 504, a detector 506 and either an internal display 508 or an external display 512. A battery 510 may be used to power processor 504, detector 506 and display 508/512. Detector 506 is for example an accelerometer or a Hall Effect sensor. Display 508/512 is for example a liquid crystal display and/or a small speaker (e.g., that emits voice annunciations or other sounds generated by processor 504).
[0039] FIG. 6 shows one part of an exemplary body bar 602 with body bar sensing system 500 attached; a weight 604 and a retaining clip 606 are also shown to secure weight 604 onto body bar 602 (note, some body bars use no weights but weight is shown in FIG. 6 for illustrative purposes). Body bar 602 may represent a work out bar used by people in the gym, or a barbell, or other similar apparatus that requires a number of repetitions in exercise. FIG. 7 shows body bar 602 in an embodiment with another body bar sensing system 500 that secures weight 604 onto body bar 602. That is, sensing system 500 in addition operates as retaining clip 606, FIG. 6.
[0040] FIGS. 5, 6 and 7 are best viewed together with the following description. Housing 502 attaches to body bar 602 as shown in FIG. 6 or as shown in FIG. 7. Processor 504 utilizes detector 506 to determine when system 500 (as attached to body bar 602) has performed one repetition; it then informs the user, via display 508/512 for example, of a number of repetitions (or whether the user has performed the right number or any other number of planned repetitions as programmed into processor 504).
[0041] Where display 512 is used (i.e., remote from housing 502), a wireless transmitter (not shown) may be included within housing 502 to remotely provide data from processor 504 to remote display 512 (as shown in dotted outline). Where display 508 is integral with housing 502, then display 508 provides a visual display for a user when housing 502 attaches to the body bar. In one embodiment, display 512 (shown in dotted outline) is part of a watch (or a MP3 player or a cell phone) that may be seen when worn or used by the user when performing exercises; and measurements determined by processor 504 are transmitted to the watch (or to the MP3 player or cell phone) for display upon display 512.
[0042] Processor 504 may operate under control of algorithmic software 505 (which is illustratively shown within processor 504 although it may reside elsewhere within housing 502, such as stand alone memory within housing 502). Algorithmic software 505 for example includes algorithms for processing data from detector 506 to determine the repetitions performed by a user of body bar 602.
[0043] FIG. 8 shown one exemplary process 800 performed by processor 504. In step 802, detector 506 samples a physical metric associated with body bar 602. In an example of step 802, detector 506 is an accelerometer and thereby provides acceleration as the physical metric. In another example of step 802, detector is a Hall effect sensor which detects inversion (and thus repetition) of bar 602. In step 804, processor 504 processes the physical metric to assess whether the metric indicates a repetition of body bar 602. In an example of step 804, processor 504 evaluates the acceleration to determine if body bar 602 has been raised or lowered within a certain time interval. In step 806, repetition information is displayed to the user. In an example of step 806, the number of repetitions is relayed remotely (wirelessly) to a watch that includes display 512. That watch may also include a processor to store data and inform the user of repetitions for workouts, over time.
[0044] FIG. 9 shows one exemplary system 900 for unitlessly assessing activity of a user. System 900 has a processor 904, a detector 906 and a battery 908 within an enclosure 902 (e.g., a plastic housing). System 900 may include a display 910 for displaying unitless units to the user. Alternatively (or in addition), a remote display 912 is used to display the unitless units; in this case, enclosure 902 includes a wireless transmitter 913 in communication with, and controlled by, processor 904, so that transmitted unitless assessment numbers are sent to remote display 912.
[0045] In an embodiment, detector 906 is an accelerometer and processor 904 determines a value representing an activity level of the user of system 900 for display on display 910 or display 912. The accelerometer is for example positioned within housing 902 so that, when housing 902 is attached to a user, accelerometer 906 senses motion perpendicular to a surface (e.g., ground or a road or a floor) upon which the user moves (e.g., runs, dances, bounces). Data from the accelerometer is for example processed in the frequency domain as power spectral density (e.g., by frequency binning of the data). Multiple accelerometers (e.g., a triaxial accelerometer) may also be used as detector 906–for example to sense motion in other axes in addition to one perpendicular to the surface–and then processed together (e.g., in power spectral density domain) to arrive at a unitless value (as described below).
[0046] Processor 904 may utilize one or more algorithms, shown as software 905 within processor 904, for processing information obtained from detector 906 to assess the activity of the user. For example, processor 904 may periodically sample detector 906 to measure acceleration forces experienced by the user (when enclosure 902 is attached to the user, e.g., at the user’s belt or shoe). Processor 904 may then process these forces to assess the activity level of the user. This activity level may represent effort exerted by the user when skiing.
[0047] The following represents a typical use of system 900, in an embodiment. In this example, detector 906 is one or more accelerometers. First, processor 904 determines when system 900 is in use, for example by sensing movement of housing 902 that corresponds to known activity (e.g., skiing or running). Alternatively, system 900 includes a button 915 that starts processing (in which case, separate determination of a known activity is not necessary). In an embodiment, button 915 is located proximate to display 912, and communicated wirelessly with processor 904. In this case, wireless transmitter 913 is a transceiver and button 915 includes a transmitter or a transceiver.
[0048] Once processor 904 knows (by sensing motion) or is notified (by button 915) that system 900 is operating in the desired activity, then it collects data over a period of that activity–for example over 1 hour (a typical aerobic hour), 4 hours (a typical long run), 8 hours (a typical “ski” day) or over one full day, each of these being typical sport activity periods; however any time may be used and/or programmed in system 900. In an example, processor 904 integrates power spectral density of acceleration over this period of time to generate a number. This number in fact is a function of g’s, frequency units and time, which does not make intuitive sense to the user. For example, consider a professional athlete who snowboards down difficult, double diamond terrain for eight hours. When system 900 measures his activity over this period, his number will be high (e.g., 500 “units” of power spectral density) because of his extreme physical capabilities. Then, when a less capable user uses system 900, a number of, e.g., 250 units may be generated because the user is not as capable (physically and skilled) as the professional. Therefore, in this example, an expected maximum number, shown as MAX 914 within processor 904, may be set at 500. A display range, shown as RNG 916 within processor 904, may also be defined such that system 900 may display a unitless value that is relative to the maximum number. Continuing with the above example, if RNG 916 is set to 100, system 900 displays a unitless value of 100 for the professional athlete and a unitless value of 50 for the less capable user (i.e., the less capable user has a 50% value of the professional athlete). By setting RNG 916 to other values, the displayed output range of system 900 may be modified.
[0049] In one example of use, system 900 is formed as a wrist watch to facilitate attachment to a child’s wrist. System 900, when worn by the child, may then determine the child’s activity level for the day. In another example of use, system 900 may be attached to a person’s limb that is recuperating from injury (e.g., sporting injury, accident and/or operation etc.) such that system 900 may determine if the limb is receiving the right amount of activity to expedite recovery.
[0050] In another example of use, two skiers each use a system 900 when skiing for a day. The first skier, who is experienced and athletic, skis difficult ski runs (e.g., black double diamonds) all day, whereas the second skier is less experienced and skis easy runs (e.g., green runs) all day. At the end of the day, the first skier has a unitless activity value of 87 and the second skier has a unitless activity value of 12. Thus, these unitless activity values indicate the relative activity levels of each skier.
[0051] FIG. 10 shows a flowchart illustrating one process 1000 for determining and displaying a unitless value representative of a users activity. Process 1000 may represent algorithms within software 905 of FIG. 9, for example, to be executed by processor 904. In step 1002, process 1000 clears a period accumulator. In one example of step 1002, processor 904, under control of software 905, clears period accumulator 918. In step 1004, process 1000 samples the detector to obtain data. In one example of step 1004, processor 904 periodically samples detector 906 over a sample period to determine data representative of the user’s activity for that period. In step 1006, process 1000 processes the data of step 1004 to determine a number. In one example of step 1006, processor 904 integrates power spectral density of acceleration sampled in step 1004 over the sample period of step 1004 to generate a number. In step 1008, the number determined in step 1004 is added to the period accumulator. In one example of step 1006, processor 904 adds the number determined in step 1004 to period accumulator 918. In step 1010, process 1000 determines a unitless activity value from the accumulator. In one example of step 1010, processor 904 converts the accumulated value to a display value based upon MAX 914 and RNG 916. In step 1012, process 1000 displays the determined unitless activity value. In one example of step 1012, processor 904 sends the determined unitless activity value to display 912 via wireless transmitter 913. Step 1014 is a decision. If, in step 1014, the activity period for display has ended, process 1000 terminates; otherwise process 1000 continues with step 1004. Steps 1004 through 1014 thus repeat until the desired activity period is over.
[0052] Changes may be made to this application without departing from the scope hereof. It should thus be noted that the matter contained in the above description or shown in the accompanying drawings should be interpreted as illustrative and not in a limiting sense. The following claims are intended to cover all generic and specific features described herein, as well as all statements of the scope of the present method and system, which, as a matter of language, might be said to fall there between.
Questa volta è tutto vero: finisce la corsa per l’anti-iPod di Microsoft, spazzato via dagli smartphone
Se ne parlava già dallo scorso mese di marzo di una possibile dismissione della linea di lettori multimediali di Microsoft: stavolta Zune chiude per davvero. Dopo una ulteriore ridda di voci e una rapida smentita, altrettanto rapida è stata la smentita-bis: i player Zune cesseranno davvero di essere prodotti.
Dopotutto, come già si disse mesi addietro, Microsoft è orientata a potenziare i Windows Phone; e il resto del mercato vede la sfida Apple–Android (non a caso Google si era “pappata” Motorola Mobility lo scorso agosto).
Insomma in un momento in cui tablet e telefoni che sono di fatto dei minicomputer la fanno da padrone – sfidandosi su vari fronti, dall’hardware alle app ai contenuti multimediali – un player che avrebbe potuto fare molta strada e forse essere l’anti-iPod, ma che di fatto era giunto sulla scena con 5 anni di ritardo nel 2006, cominciava ad apparire più che obsoleto.
Inizialmente sbeffeggiato per il suo aspetto poco attraente, per il colore marrone e persino per il nome (che suonava esattamente come un termine ebraico relativo al rapporto sessuale); in evidenza per il controverso lancio pubblicitario con tanto di immagini allusive, la sua prima incarnazione (nome in codice: Argo) era basata sul Gigaset S della Toshiba, società con cui Redmond si era per l’occasione alleata. Pur con tutte le modifiche del caso – ne esistono 4 “generazioni”, l’ultima datata 2009, diretta concorrente dell’iPod Touch – Zune non aveva mai sfondato.
Una curiosità: chi scrive aveva notato mesi addietro uno strano trend; osservando dati relativi a streaming e download di alcuni artisti, sembrava che il Marketplace musicale dedicato a Zune stesse avendo più movimento di prima, nonostante le voci sullo stop alla commercializzazione.
Zune in declino e servizio online in ascesa? Pare proprio di sì; e questo perché ai suoi contenuti accedono anche utenti Xbox e Windows Phone; Microsoft deve aver certamente notato la tendenza. Il nome Zune continuerà almeno per ora a sopravvivere, associato appunto a software e servizi online come Zune Music Pass.
[Pubblicato su Mytech http://mytech.it/web/2011/10/05/microsoft-addio-zune-e-davvero/]
Research In Motion lancia un servizio cloud per BlackBerry: musica delle major in USA, Canada e Regno Unito
E’ partito a fine agosto in “closed Beta” e in tre paesi (Stati Uniti, Gran Bretagna e Canada): è BBM Music, ultimo nato tra i servizi musicali “cloud“. Il lancio vero e proprio è previsto a fine anno in diversi paesi e al costo di 4,99 dollari al mese. Le agenzie riferiscono di “una selezione” di musica delle quattro major del disco (Universal, Sony, Warner, EMI).
A quanto pare, Research In Motion, casa madre degli smartphone targati BlackBerry sembra voler dire “ci siamo anche noi”, e si butta a pesce in quella che sembra la moda del momento, unendola con un’altra delle ossessioni del nostro tempo, il social networking.
Così, si potrà costruire una rete di contatti interessati alla musica; i nostri amici vedranno cosa ascoltiamo noi e viceversa: ogni utente avrà un profilo di 50 brani preferiti e potrà “scambiarne” 25 al mese.
Sarà anche possibile creare delle playlist con i titoli dei brani presenti sul proprio profilo o in quelli degli amici e condividere le playlist stesse.
Insomma, Apple avrà forse poco da temere, ma è ancora un nome che si aggiunge a una scena cloud/social in rapido affollamento, un potenziale concorrente sia di servizi stile Spotify che di cose come Music Beta di Google.
[Pubblicato su Mytech http://mytech.it/web/2011/09/04/bbm-music-anche-il-blackberry-tra-le-nuvole-musica/]
Sezione speciale in Apple iTunes per la cantante prematuramente scomparsa: e i suoi album – come previsto – balzano ancora al top delle classifiche; intanto, in YouTube…
Il copione si ripete: come per Michael Jackson e per molti altri prima di lui, la morte di una star della musica equivale spesso a un ritorno del catalogo in classifica. Così, ecco che ad Amy Winehouse, assurta al successo troppo presto e scomparsa prematuramente, tocca ora questo onore di cui avrebbe probabilmente volentieri a meno…
Ovviamente, iTunes la fa da padrone: Apple ha allestito una sezione speciale per l’amatissima cantante britannica. E peraltro dispone anche della performance live all‘iTunes Festival del 2007, a Londra.
Con 16 videoclip e 34 (!) uscite disponibili (in realtà si tratta per la maggior parte di differenti edizioni degli stessi lavori, singoli, remix e via dicendo), non stupisce che nella notte tra il 24 e il 25 luglio, le classifiche digitali di mezzo mondo presentino album della Winehouse in testa e altre uscite sparse nelle posizioni successive della Top 10.
E’ “Back to Black” a dominare le charts, sia nell’edizione “base” che nella versione Deluxe.
Anche in YouTube molta attenzione per i video di Amy; piccola gaffe della major Universal che in Facebook segnala un link al portale Vevo invisibile fuori dagli Stati Uniti, ma gli stessi identici contenuti sono invece perfettamente visibili all’indirizzo www.youtube.com/user/AmyWinehouseVEVO.
Lo scorso giugno erano state rimosse da YouTube le immagini dell’ultimo concerto in Serbia (ufficialmente per violazione di copyright, ma come è noto Universal ha invece lasciato online moltissime altre apparizioni live della stessa artista…); quelle stesse impietose immagini vengono ora ripubblicate da più parti su questo ed altri siti di video. Persino da parte della Rai, nel proprio canale sul portale video di Google. Sempre in YouTube si può reperire l’ultima apparizione pubblica: guarda caso, ancora in un iTunes Festival. Quello dello scorso 20 luglio, che vide Amy ballare sul palco – ma non cantare – durante l’esibizione di Dionne Bromfield. Appena due giorni prima della tragica fine.
[Pubblicato su Mytech]
E così l’annunciato iCloud di Apple è stato puntualmente presentato a inizio giugno: e potrebbe essere una rivoluzione. Anche se, a ben vedere, per alcuni versi è una rivoluzione che ha almeno dieci anni. Intanto The Pirate Bay e Techdirt avvertono..
Di “cloud”, “nuvole” in cui immagazzinare i nostri dati se ne parla da anni, spesso troppo e a sproposito. Se è vero che molti già fanno uso di sistemi che consentono di immagazzinare e magari condividere dati sui propri diversi pc o con altre persone – pensiamo ad esempio alle cartelle condivise in Dropbox – è pur vero che molte società si sono buttate su questa idea senza sapere bene dove andare a parare. Continua…
Servizi “cloud” per la musica di Google e Amazon: pericolo per iTunes, o “nuvole” di fumo? Con una riflessione sul futuro prossimo della musica online
"Nuvole" di musica anche per Google, che lancia un servizio per certi versi simile a quello recentemente avviato da Amazon. Parte stasera (solo per gli USA: gli altri se vogliono, tramite un qualche servizio proxy possono ammirare la home page e rosicare…) Google Music. Anzi, per adesso, accanto alla parola “music” c’è un grosso “beta”, perché il tutto è in fase sperimentale. “Music Beta by Google”. L’indirizzo è music.google.com. Continua…
Un bizzarro caso di copyright del 2009 si chiude, almeno in parte: EMI risarcita da Bluebeat per i brani dei Beatles
La fantomatica tecnologia UltraViolet, un’accozzaglia di ben cinque (!?) tipi di diversi sistemi di protezione, quelle cose impropriamente note come “Digital Rights Management“, è una tecnologia per “cloud storing” destinata a sparire senza mai essere implementata seriamente e che – pur avendo il supporto di una cinquantina di società tra major del cinema, provider e altri nomi dell’alta tecnologia, da Nokia a Sony, di fatto non è supportata da due nomi chiave, Apple e Disney.
In pratica, secondo il DECE (Digital Entertainment Content Ecosystem) , il consorzio di società che sviluppano e supportano questo sistema, in un futuro prossimo avremo a disposizione l’accesso a un “diritto” permanente alla visione di un film, per esempio. E ciò al di là del formato o della periferica disponibile.
Un po’ come dire: hai pagato una volta, per te e la tua famiglia, per vedere questo film. Lo potrai rivedere – sempre nell’ambito del nucleo familiare – su computer, tablet, player portatili, tv e altro ancora, a vita e se occorre scaricandolo in formati diversi.
Un “locker” che anziché conservare file multimediali racchiude in pratica le licenze che ci consentono di accedere in una varietà di formati e situazioni al materiale che abbiamo acquistato.
L’idea non sarebbe di per sé malvagia ma la (non casuale, visto che l’azionista di riferimento è lo stesso…) sinergia di due leader come Apple e Disney per boicottarla e sviluppare un proprio sistema di Video on Demand, Keychest (annunciato sin dal 2009 e anch’esso di dubbia fattibilità), unita alla macchinosità del sistema, non lascia sperare troppo.
Bonus: se avete letto in merito l’articolo di Repubblica.it del 17 marzo, merita una segnalazione questa “perla”.
“Rispetto ad altre soluzioni avanzate in passato (una su tutte il PayForSure proposto nel 2004 da Microsoft)”… vogliamo ovviamente sperare in un banale refuso dovuto alla fretta.
Il “PayForSure” (lapsus freudiano? ;)) non esiste, si intendeva “PlaysForSure“, una risibile “certificazione” targata Microsoft che – a dispetto del nome – non veniva usata nemmeno dalla stessa casa produttrice…
Microsoft esce dal mercato dei player multimediali? Zune rimpiazzato da Ventura? Così dicono le voci riportate da Bloomberg. Fonti interne smentiscono. A metà.
Zune – la linea di player multimediali targati Microsoft che averebbero dovuto rappresentare il più pericoloso concorrente per iPod e simili di casa Apple – sarebbe al capolinea.
Così dicono le voci, che sembrerebbero ben informate, riportate un paio di giorni addietro da Bloomberg (che descrive la fonte come “a person familiar with the decision”). Microsoft si concentrerebbe sul software Zune e sulla sua diffusione in particolare sui cellulari, in modo da guadagnare sui contenuti audio e video così distribuiti.
Nel giro di 24 ore è apparsa una parziale smentita sul forum di Anythingbutipod.com: sa di poca ufficialità (non esiste un comunicato Microsoft né sulla cessazione della produzione dell’hardware targato Zune, né come smentita di quanto riportato da Bloomberg e ripreso praticamente da moltissimi altri mezzi d’informazione online e non) ma è già qualcosa.
A parlare è Dave McLauchlan, che lavora al business development dell’hardware Zune (e quindi si è ritrovato bombardato di messaggi sull’argomento), e che per ora resta al suo posto. La divisione hardware di Zune non chiude: non è previsto nessun nuovo modello al momento, perché l’hardware Zune di quest’anno sono i telefoni Windows Phone 7; ma allo stesso tempo non è detto che non si mettano in produzone nuovi lettori in futuro.
Di certo quel 77% del mercato in mano ad Apple, schiaccia anche un gigante come Microsoft e mette in difficoltà chiunque.
Unico elemento di certezza: al momento Redmond si concentra su software e contenuti; un settore in cui avendo a disposizione una miriade di piattaforme, dai PC alla XBox, dagli Zune già in circolazione agli smartphone, potenzialmente c’è ancora spazio.
Va detto che già da alcuni giorni (lo segnalava Mary Jo Foley in ZDNet l‘8 marzo) si parlava anche di una nuova piattaforma Microsoft in questo settore, ma sotto un nome – dobbiamo dirlo – purtroppo non originalissimo. Zune verrebbe rimpiazzato da Ventura. Un nome che brutto non è, ma che se fosse quello definitivo e non solo un “nome in codice” del progetto in via di sviluppo, potrebbe portare qualche problemino.
Abbiamo fatto una piccola verifica, notando che “Ventura” ricorre ben 192 volte tra i marchi registrati negli Stati Uniti (71 volte tra i marchi ancora attivi). Se a ciò aggiungiamo che tra i marchi attivi figurano “Corel Ventura” e “Ventura Publisher” – un software ormai non più aggiornato dal 2002, ma sempre un nome leggendario nella storia dell’informatica – il rischio di trovarsi davanti a qualche grana legale per problemi di trademark (Apple ne sa qualcosa) – è più che concreto.
Come alcune delle stesse schede dell’Ufficio Marchi e Brevetti statunitense segnalano, “ventura” è anche un termine di lingua spagnola che sta per “fortuna”.
Di “buona sorte”, se sarà davvero operata questa non brillante scelta per il nome di un futuro prodotto o servizio, dalle parti di Redmond ne avranno davvero bisogno… ;)
Pubblicato su: http://mytech.it/digitale/2011/03/16/microsoft-zune-e-morto-ma-anche-no/
E se una major del disco abbandonasse il lucrativo negozio di musica digitale targato Apple? I progetti di Sony: scatto d’orgoglio o suicidio commerciale?
Incredibile ma vero: la ghiotta occasione dell’uscita di materiale inedito di Michael Jackson convince Apple a piegarsi ad alcune delle richieste targate Sony. “This is it” non sarà disponibile come download singolo Continua…
Attacco frontale al modello Apple Store: ecco i negozi Microsoft. Oggi l’Arizona e la California. Dopodomani il mondo? Continua…
Spider-Woman, un serial a fumetti della Marvel sbarca su iTunes ed è un successo: e intanto Disney acquista Marvel. Continua…