User or patient monitoring systems with one or more analysis tools

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation in part of U.S. Ser. No. 13/923,909, U.S. Ser. No. 13/923,637, U.S. Pat. No. 923,614, U.S. Ser. No. 13/923,809, U.S. Ser. No. 13/923,750, U.S. Ser. No. 13/923,583, U.S. Ser. No. 13/923,560, U.S. Ser. No. 13/923,543, and U.S. Ser. No. 13/923,937, all filed Jun. 21, 2013 and all of which claim the benefit of U.S. 61/772,265, U.S. 61/812,083 and 61/823,502. All of the above-identified applications are fully incorporated herein by reference.

BACKGROUND

00021. Field of the Invention

0003The present invention is directed to monitoring user or patient parameters, and more particularly to systems that use a user activity manager, feedback control in combination with a monitoring device with a unique user ID and a telemetry system to provide for monitoring a user's activities using one or more analysis tools and provide feedback.

00042. Description of the Related Art

0005Patient monitoring was accomplished by electronic equipment maintained at the user's bedside. Vital signs derived from physiological waveforms were monitored with the bedside equipment and alarms were generated if predetermined limits were exceeded by the vital signs. This bedside monitoring equipment became larger, more complex and expensive as each bedside unit undertook to monitor more physiological data and provide more sophisticated displays, e.g. color, more and better communications and more in-depth analysis of the data, such as calculation of vital signs and trends which required memory and processing capability. The provision of such units at each appropriate user bedside introduces considerable additional expense to the hospital user care costs.

0006With the introduction of bedside monitoring units, attempts were made to provide a measure of remote monitoring by transmitting analog waveforms of physiological data from the bedside unit to equipment at a central station such as a nurse's station. Subsequently remote monitoring efforts included analog waveforms plus digital representations for display. Both the bedside and remote monitoring activity acted to give alarms upon sensing an abnormal condition and to store data and analyze data to obtain vital signs and trends. But these systems are basically one-way systems reporting physiological data from the user. There is no communication with the user as a part of an interactive integrated system.

0007Telemetry systems can be implemented to acquire and transmit data from a remote source. Some telemetry systems provide information about a user's activities.

0008It is becoming commonplace to use wireless packet data service networks for effectuating data sessions with. In some implementations, unique identifications (ID) need to be assigned to the devices in order to facilitate certain aspects of service provisioning, e.g., security, validation and authentication, et cetera. In such scenarios, it becomes imperative that no two devices have the same indicium (i.e., collision). Further, provisioning of such indicia should be flexible so as to maintain the entire pool of indicia to a manageable level while allowing for their widespread use in multiple service environments.

0009Medical telemetry systems may comprise an alarm adapted to identify high risk users and/or users requiring special assistance. Some medical procedures and diagnostic examinations require the removal of any telemetry system components attached directly to a user. One problem with conventional medical telemetry systems is that the process of removing telemetry system components for purposes of performing a medical procedure or diagnostic examination can generate a false alarm. False alarms unnecessarily tax hospital resources and interfere with the working environment.

0010There is a need for systems using telemetry devices configured to be used for user lifestyle management, monitoring user behavior, user activity and habits and health monitoring. There is a further need for wireless communication systems with monitoring devices that have sensors used for a monitoring user behavior, user activity and habits and health monitoring, analysis of the monitoring followed by feedback alerts.

SUMMARY OF THE INVENTION

0011An object of the present invention is to provide systems that provide tools for analysis and feedback for medical and lifestyle management.

0012Another object of the present invention is to provide systems for medical and lifestyle management using user habit information or user monitoring, analysis tools and feedback.

0013A further object of the present invention is to provide systems for medical and lifestyle management using monitoring devices with sensors that monitor one or more of a user's activities, behaviors and habit information, the use of analysis tools followed by providing user feedback.

0014Still another object of the present invention is to provide systems for medical and lifestyle management using one or more contexts selected from at least one of, time, location, type of user activity, duration of user activity and a status of the user activity, analysis tools used to provide user feedback.

0015Yet another object of the present invention is to provide systems that use an activity manager and feedback to manage and monitor user lifestyle or medical conditions in response to receiving information for a monitoring device with sensors that monitor one or more of a user's activities, behaviors and habit information, following by using analysis tools in response to the monitoring.

0016These and other objects of the present invention are achieved in a system for using telemetry data based on user habit information or user monitoring. A monitoring device has one or more sensors that detect or measure user information selected from of at least one of, a user's activities, behaviors and habit information, and a user's health. The monitoring device includes ID circuitry with an ID storage that contains a unique user ID, a communication system which reads and transmits the unique user ID from the ID storage, a power source and a pathway system. A telemetry system with a database receives the user information from the telemetry device. One or more analysis tools are at the telemetry system that analyze the user information and produce analysis information that is sent to the monitoring device.

BRIEF DESCRIPTION OF THE DRAWINGS

0017<figref idref="DRAWINGS">FIGS. 1(<i>a</i>) and 1(<i>b</i>)</figref> illustrate one embodiment of a wearable device of the present invention, where one size fits all.

0018<figref idref="DRAWINGS">FIG. 2</figref> illustrates one embodiment of electronics that can be included in the wearable device.

0019<figref idref="DRAWINGS">FIG. 3</figref> illustrates one embodiment of a telemetry system of the present invention.

0020<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of the programming input schematic of the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0021<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of the system of programming the sensor/transmitter(s) comprising the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0022<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of the jam command and security/randomization bits of the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0023<figref idref="DRAWINGS">FIG. 7</figref> is a logic circuit diagram of the sensor/transmitter programming input schematic in one embodiment of the present invention.

0024<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram of an embodiment of a computer implemented system for determining the location of a remote sensor utilizing the methods of the present invention.

0025<figref idref="DRAWINGS">FIG. 9</figref> is a block diagram illustrating one embodiment of a SNAPSHOT GPS receiver for use according to the present invention.

0026<figref idref="DRAWINGS">FIG. 10</figref> is a block diagram of a remote sensor shown in communication with two different external communication devices.

0027<figref idref="DRAWINGS">FIG. 11</figref> is a diagram of the active RF and RF backscatter antennas.

0028<figref idref="DRAWINGS">FIG. 12</figref> is a diagram of the encoding scheme for the symbols in the active RF protocol.

0029<figref idref="DRAWINGS">FIG. 13</figref> is a diagram of the packet structure in the IRDA protocol.

0030<figref idref="DRAWINGS">FIG. 14</figref> is a diagram of the encoding scheme in the IRDA protocol.

0031<figref idref="DRAWINGS">FIG. 15</figref> illustrates one embodiment of an activity manager that is included in the monitoring device, the telemetry system or as a standalone device.

0032<figref idref="DRAWINGS">FIG. 16</figref> illustrates one embodiment of an activity manager in one embodiment of the present invention.

0033<figref idref="DRAWINGS">FIGS. 17(<i>a</i>) and (<i>b</i>)</figref> illustrate an exemplary user interface for an activity management application according to an embodiment of the present invention.

0034<figref idref="DRAWINGS">FIG. 18</figref> is a timing diagram illustrating one example of monitoring an activity based on one or more contexts according to an embodiment of the present invention;

0035<figref idref="DRAWINGS">FIG. 19</figref> is a block diagram illustrating one embodiment of a monitoring device of the present invention.

0036<figref idref="DRAWINGS">FIG. 20</figref> illustrates an embodiment of the present invention that includes a feedback system or subsystem.

0037<figref idref="DRAWINGS">FIG. 21</figref> is a flow chart illustrating one embodiment of proving feedback and/or alerts to a user or patient.

0038<figref idref="DRAWINGS">FIG. 22</figref> is a flow chart illustrating one embodiment for a method of establishing control parameters for a monitoring device user or patient feedback or alert signal and a sensor signal threshold range for the feedback or alert signal.

DETAILED DESCRIPTION

0039As used herein, the term engine refers to software, firmware, hardware, or other component that can be used to effectuate a purpose. The engine will typically include software instructions that are stored in non-volatile memory (also referred to as secondary memory). When the software instructions are executed, at least a subset of the software instructions can be loaded into memory (also referred to as primary memory) by a processor. The processor then executes the software instructions in memory. The processor may be a shared processor, a dedicated processor, or a combination of shared or dedicated processors. A typical program will include calls to hardware components (such as I/O devices), which typically requires the execution of drivers. The drivers may or may not be considered part of the engine, but the distinction is not critical.

0040As used herein, the term database is used broadly to include any known or convenient means for storing data, whether centralized or distributed, relational or otherwise.

0041As used herein a mobile device includes, but is not limited to, a cell phone, such as Apple's iPhone®, other portable electronic devices, such as Apple's iPod Touches®, Apple's iPads®, and mobile devices based on Google's Android® operating system, and any other portable electronic device that includes software, firmware, hardware, or a combination thereof that is capable of at least receiving the signal, decoding if needed, exchanging information with a transaction server to verify the buyer and/or seller's account information, conducting the transaction, and generating a receipt. Typical components of mobile device may include but are not limited to persistent memories like flash ROM, random access memory like SRAM, a camera, a battery, LCD driver, a display, a cellular antenna, a speaker, a BLUETOOTH® circuit, and WIFI circuitry, where the persistent memory may contain programs, applications, and/or an operating system for the mobile device.

0042As used herein, the terms “social network” and “SNET” comprise a grouping or social structure of devices and/or individuals, as well as connections, links and interdependencies between such devices and/or individuals. Members or actors (including devices) within or affiliated with a SNET may be referred to herein as “nodes”, “social devices”, “SNET members”, “SNET devices”, “user devices” and/or “modules”. In addition, the terms “SNET circle”, “SNET group” and “SNET sub-circle” generally denote a social network that comprises social devices and, as contextually appropriate, human SNET members and personal area networks (“PANs”).

0043A used herein, the term “wearable device” is anything that can be worn by an individual and that has a back side that in some embodiments contacts a user's skin and a face side. Examples of wearable device include but are not limited to a cap, arm band, wristband, garment, and the like.

0044As used herein, the term “computer” is a general purpose device that can be programmed to carry out a finite set of arithmetic or logical operations. Since a sequence of operations can be readily changed, the computer can solve more than one kind of problem. A computer can include of at least one processing element, typically a central processing unit (CPU) and some form of memory. The processing element carries out arithmetic and logic operations, and a sequencing and control unit that can change the order of operations based on stored information. Peripheral devices allow information to be retrieved from an external source, and the result of operations saved and retrieved.

0045As used herein, the term “Internet” is a global system of interconnected computer networks that use the standard Internet protocol suite (TCP/IP) to serve billions of users worldwide. It is a network of networks that consists of millions of private, public, academic, business, and government networks, of local to global scope, that are linked by a broad array of electronic, wireless and optical networking technologies. The Internet carries an extensive range of information resources and services, such as the inter-linked hypertext documents of the World Wide Web (WWW) and the infrastructure to support email. The communications infrastructure of the Internet consists of its hardware components and a system of software layers that control various aspects of the architecture.

0046As used herein, the term “extranet” is a computer network that allows controlled access from the outside. An extranet can be an extension of an organization's intranet that is extended to users outside the organization that can be partners, vendors, and suppliers, in isolation from all other Internet users. An extranet can be an intranet mapped onto the public Internet or some other transmission system not accessible to the general public, but managed by more than one company's administrator(s). Examples of extranet-style networks include but are not limited to: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0047">LANs or WANs belonging to multiple organizations and interconnected and accessed using remote dial-up</li><li id="ul0002-0002" num="0048">LANs or WANs belonging to multiple organizations and interconnected and accessed using dedicated lines</li><li id="ul0002-0003" num="0049">Virtual private network (VPN) that is comprised of LANs or WANs belonging to multiple organizations, and that extends usage to remote users using special “tunneling” software that creates a secure, usually encrypted network connection over public lines, sometimes via an ISP.</li></ul></li></ul>

0050As used herein, the term “Intranet” is a network that is owned by a single organization that controls its security policies and network management. Examples of intranets include but are not limited to: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0051">A LAN</li><li id="ul0004-0002" num="0052">A Wide-area network (WAN) that is comprised of a LAN that extends usage to remote employees with dial-up access</li><li id="ul0004-0003" num="0053">A WAN that is comprised of interconnected LANs using dedicated communication lines</li><li id="ul0004-0004" num="0054">A Virtual private network (VPN) that is comprised of a LAN or WAN that extends usage to remote employees or networks using special “tunneling” software that creates a secure, usually encrypted connection over public lines, sometimes via an Internet Service Provider (ISP).</li></ul></li></ul>

0055For purposes of the present invention, the Internet, extranets and intranets collectively are referred to as (“Network Systems”).

0056As used herein, the term “user” includes but is not limited to a person, under a physician's care, interested in maintaining health, interested in maintaining a healthy lifestyle and/or physiologic balance, interested in monitoring lifestyle conditions, including but not limited to, the way a person goes about daily living including but not limited to, habits, exercise, diet, medical conditions and treatments, career, financial means, emotional status, and the like.

0057As used herein, the term “user monitoring” includes: (i) Cardiac monitoring, which generally refers to continuous electrocardiography with assessment of the user's condition relative to their cardiac rhythm. A small monitor worn by an ambulatory user for this purpose is known as a Holter monitor. Cardiac monitoring can also involve cardiac output monitoring via an invasive Swan-Ganz catheter (ii) Hemodynamic monitoring, which monitors the blood pressure and blood flow within the circulatory system. Blood pressure can be measured either invasively through an inserted blood pressure transducer assembly, or noninvasively with an inflatable blood pressure cuff. (iii) Respiratory monitoring, such as: pulse oximetry which involves measurement of the saturated percentage of oxygen in the blood, referred to as SpO2, and measured by an infrared finger cuff, capnography, which involves CO2 measurements, referred to as EtCO2 or end-tidal carbon dioxide concentration. The respiratory rate monitored as such is called AWRR or airway respiratory rate). (iv) Respiratory rate monitoring through a thoracic transducer belt, an ECG channel or via capnography, (v) Neurological monitoring, such as of intracranial pressure. Special user monitors can incorporate the monitoring of brain waves electroencephalography, gas anesthetic concentrations, bispectral index (BIS), and the like, (vi) Blood glucose monitoring using glucose sensors. (vii) Childbirth monitoring with sensors that monitor various aspects of childbirth. (viii) Body temperature monitoring which in one embodiment is through an adhesive pad containing a thermoelectric transducer. (ix) Stress monitoring that can utilize sensors to provide warnings when stress levels signs are rising before a human can notice it and provide alerts and suggestions. (x) Epilepsy monitoring. (xi) Toxicity monitoring, (xii) general lifestyle parameters and the like.

0058Additionally the present invention can be used to detect differences for a variety of blood tests, including but not limited to tests for the following: sodium, potassium, chloride, urea, creatinine, calcium, albumin, fasting glucose, amylase, carcinoembryonic antigen, glycosylated hemoglobin, hemoglobin, erthrocytes hemoglobin and the like.

0059In various embodiments, the present invention provides a user monitoring device <b>10</b>, including but not limited to, a wearable device, where one size fits all, Telemetry device <b>10</b> can be a sensor enabled item <b>10</b>, including but not limited to a wearable device, gym bag, wallet, file, shoes, skis, and the like that has its own unique ID. As illustrated in <figref idref="DRAWINGS">FIGS. 1(<i>a</i>) and 1(<i>b</i>)</figref>, in one embodiment of the present invention, the user monitoring device <b>10</b> include a plurality of magnets <b>12</b>, with adjacent magnets having opposite polarity, with a length suitable to be worn by all people. In one embodiment, the length of the user monitoring device <b>10</b> can be 10-12 inches. The magnets <b>12</b> are positioned along an interior of the user monitoring device <b>10</b> to be provided for good conformation to a user's wrist.

0060One or more sensors <b>14</b> are coupled to the user monitoring device <b>10</b>. The sensors are measuring devices. As a non-limiting example, the measuring device or sensors <b>14</b> can include RTSS devices to detect a user's activities, motions, physical parameters, and the like, including but not limited to, a heart rate monitor, a body temperature probe, a conventional pedometer, an accelerometer and the like.

0061Alternatively, multifunctional sensors <b>14</b> which can perform all the aforementioned functions of RTSS may be attached or embedded in user monitoring device <b>10</b>. In one embodiment, each sensor can be in communication and or connect electronically and/or RF to a telemetry module <b>16</b>. A variety of different sensors <b>14</b> can be utilized, including but not limited to, an accelerometer based sensor, and pressure based sensors, voltage resistance sensor, a radio frequency sensor, and the like, as recited above.

0062As a non-limiting example, an accelerometer, well known to those skilled in the art, detects acceleration and thus user activity. The accelerometer provides a voltage output that is proportional to the detected acceleration. Accordingly, the accelerometer senses vibration. This voltage output provides an acceleration spectrum over time; and information about loft time can be ascertained by performing calculations on that spectrum. A microprocessor subsystem, such as disclosed in U.S. Pat. No. 8,352,211, incorporated herein by reference, stores the spectrum into memory and processes the spectrum information to determine activity. Other examples of suitable accelerometer sensors are disclosed in EP 2428774 A1, incorporated herein by reference. Suitable pressure sensors are disclosed in EP 1883798 B1, incorporated herein by reference. A suitable voltage resistance sensor is disclosed in EP 1883798 B1, incorporated herein by reference. A suitable radio frequency sensor is disclosed in EP 2052352 B1, incorporated herein by reference.

0063Referring to <figref idref="DRAWINGS">FIG. 2</figref>, in various embodiments, the user monitoring device <b>10</b>, also known as the user monitoring device, can include a power source <b>24</b>, such a battery that can be rechargeable. The battery <b>24</b> can be put into a sleep state when not actively used in order to preserve power. A wake up feature allows the battery <b>24</b> and other electronics of the user monitoring device <b>10</b> to “sleep” during non-use or and is initiated into the “wake up” mode by certain predestinated events.

0064In one embodiment, as illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, a telemetry system server <b>16</b> is coupled to a database <b>18</b>. Each user monitoring device <b>10</b> is assigned its own unique identification, ID.

0065The data transmitted by the user monitoring device <b>10</b> sensors <b>14</b> and its ID may be coded by appending a seed to digital data bits. As illustrated in <figref idref="DRAWINGS">FIG. 3</figref> central processor unit <b>20</b> (CPU) validates or rejects received upon detection of the seed string appended to the digital data bits. In the alternative, the digital data bits may be coded and decoded by applying a scrambling algorithm utilizing the seed. A programming device <b>22</b> may be configured to transmit data to a sensor <b>14</b>, also known as a user monitoring device, utilizing a variety of alternative transmission means, including, for example, RF, IR, optical, and the like, or a magnetic loop/induction system.

0066In one embodiment, sensors <b>14</b> are configured to be shipped to users in a non-programmable mode with all programming already performed at the factory. A random seed may be communicated to the programming device <b>22</b> can a variety of different mechanisms, including but not limited to, via scanning a bar code, manual input, magnetic strip, random number generation, and the like.

0067Referring again to <figref idref="DRAWINGS">FIG. 2</figref>, in one embodiment, the user monitoring device <b>10</b> includes a control unit <b>26</b> that puts the user monitoring device <b>10</b> in a low power state. A monitoring system <b>28</b> can be included that remains active. The monitoring system <b>28</b> wakes up the electronics <b>30</b> in the user monitoring device <b>10</b> from a low power state. The control unit <b>26</b> can be notified of awaking of the other components by the monitoring system <b>28</b>. The control unit <b>26</b> can set a status bit on the monitoring system <b>28</b> only when the battery <b>24</b> needs to be in a full power state. The control unit <b>26</b> then forces a power cycle.

0068Referring to <figref idref="DRAWINGS">FIG. 3</figref>, one embodiment of a telemetry system <b>32</b> is illustrated. The telemetry system <b>32</b> is in the communication with the sensors <b>14</b> and or user monitoring device <b>14</b> and ID of the user monitoring device <b>10</b> and can include one or more receivers <b>34</b>, a central server <b>36</b> with the CPU <b>20</b>. The telemetry system <b>32</b> can optionally include a display <b>42</b> and an alarm <b>44</b>. The telemetry system <b>32</b> receives information from sensors <b>14</b> and or the monitoring device of a user's habits, activities, and the like, and then processes this information. Monitoring device <b>10</b> with its unique ID and sensors <b>14</b> is assigned to a specific user in order to track and/or monitor that user. For illustrative purposes assume that three users A, B AND C are being tracked and monitored by the telemetry system <b>32</b>. It should, however, be appreciated that the telemetry system <b>32</b> may be implemented to track and/or monitor a much larger number of users.

0069In one embodiment of the present invention, radio frequency (RF) devices that are sensors <b>14</b> and/or chips may serve as the identifying devices. Each source, sensor <b>14</b>, ID and the like can carry a fixed radio frequency chip encoded with identifying data which may be correlated to the individual participants, parts or objects.

0070Telemetry system <b>32</b> of the present invention may include a Real-Time Location System (RTLS) <b>46</b> and Real-Time Sensing System (RTSS) <b>48</b> with RF technology. The RF technology may include active and/or passive RFID sensors <b>14</b> and an RF wireless array system as a receiver <b>34</b>. The RF technology in the RTLS <b>46</b> and RTSS <b>48</b> may include UWB technology (e.g., IEEE 802.15), WLAN technology (e.g., IEEE 802.11), SAW RFID positioning system technology, GPS technology, and the like.

0071The sensors <b>14</b> may communicate directly with each other and/or relay telemetry data directly to base receiving RF device(s) or base receivers <b>34</b>. The base receivers <b>34</b> may forward the telemetry data to a base computer either through a direct link or through a Network System. Alternatively the telemetry data may be forwarded to end user devices, including but not limited to, laptops, mobile devices and the like, either directly or through a Network System. The comprehensive telemetry system <b>32</b> using RF technologies such as UWB, ZigBee, Wi-Fi, GPS data system can be utilized as described above.

0072The readers/antennae may be interconnected using a LAN, such as Ethernet to provide a Network System communication infrastructure for the computers and servers. Active and passive RFID sensors <b>14</b> may be employed. The active sensors <b>14</b> (RFID) may have a two-way communication function, which allows the base computer system to dynamically manage the sensors <b>14</b>; vary update rates; send self-identification and telemetry data.

0073The active sensors <b>14</b> may employ dual-radio architecture. In one embodiment, active sensors <b>14</b> transmit radio pulses, which are used to determine precise two-dimensional or three-dimensional location and a conventional bi-directional radio, which is used as a control and telemetry channel with a sensor update rate.

0074The user monitoring device <b>10</b> gathers telemetry data, communicates that data to a base station, BLUETOOTH® enabled device, or smart phone and the like. From the base station, the user monitoring device <b>10</b> can receive firmware updates or via a BLUETOOTH® enabled device. The user monitoring device <b>10</b> can receive updates wirelessly. The base station can receive firmware updates from Network Systems, take telemetry data from the user monitoring device <b>10</b> and transfer it to Network Systems. Telemetry data received from the base station is analyzed by servers and presented to an end user. Any third party device can receive data from the user monitoring device <b>10</b> wirelessly and deliver information to the servers for processing.

0075In one embodiment, the user monitoring device <b>10</b> uses an accelerometer, gyroscope, GPS sensor, a BLUETOOTH® chip, and a heart rate monitor.

0076As a non-limiting example, for heart monitoring, the accelerometer, sensor <b>14</b>, determines when to sample the sensors <b>14</b> and to improve the accuracy of the heart rate monitor. The gyroscope detects movement and orientation and the GPS sensor is used to determine location of the user. A BLUETOOTH® chip allows the device to connect wirelessly to other third party devices.

0077As a non-limiting example, a heart rate monitor <b>14</b> detects the user's heart rate in order to accurately determine the user's activity level, behavioral patterns and the like.

0078An Artificial Intelligence (AI) or Machine Learning-grade algorithms is used to identify the user's activities, behaviors, behaviors and perform analysis. Examples of AI algorithms include Classifiers, Expert systems, case based reasoning, Bayesian Network Systems, and Behavior based AI, Neural networks, Fuzzy systems, Evolutionary computation, and hybrid intelligent systems. A brief description of these algorithms is provided in Wikipedia and stated below.

0079Classifiers are functions that can be tuned according to examples. A wide range of classifiers are available, each with its strengths and weaknesses. The most widely used classifiers are neural networks, support vector machines, k-nearest neighbor algorithms, Gaussian mixture models, naive Bayes classifiers, and decision trees. Expert systems apply reasoning capabilities to reach a conclusion. An expert system can process large amounts of known information and provide conclusions based on them.

0080A case-based reasoning system stores a set of problems and answers in an organized data structure called cases. A case based reasoning system upon being presented with a problem finds a case in its knowledge base that is most closely related to the new problem and presents its solutions as an output with suitable modifications. A behavior based AI is a modular method of building AI systems by hand. Neural networks are trainable systems with very strong pattern recognition capabilities.

0081Fuzzy systems provide techniques for reasoning under uncertainty and have been widely used in modern industrial and consumer product control systems. An Evolutionary Computation applies biologically inspired concepts such as populations, mutation and survival of the fittest to generate increasingly better solutions to the problem. These methods most notably divide into evolutionary algorithms (e.g., genetic algorithms) and swarm intelligence (e.g., ant algorithms). Hybrid intelligent systems are any combinations of the above. It is understood that any other algorithm, AI or otherwise, may also be used. Examples of suitable algorithms that can be used with the embodiments of the present invention are disclosed in, EP 1371004 A4, EP 1367534 A2, US 20120226639 and US 20120225719, all incorporated fully herein by reference.

0082In various embodiments, the user monitoring device <b>10</b> has additional features. In one embodiment, the user monitoring device <b>10</b> changes color, via infrared LEDs, to accurately match the wearer's skin tone. This creates a seamless and more personal integration of technology into the user's daily life. In this embodiment, there is skin contact with the user monitoring device <b>10</b>.

0083In another embodiment, the user monitoring device <b>10</b> remotely reminds and can be used to administer medications. As a non-limiting example, the user monitoring device <b>10</b> can inject adrenalin. In one embodiment, the user monitoring device <b>10</b> has sleep pattern recognition based on movement and heart rate.

0084In various embodiments, the user monitoring device <b>10</b> uses algorithms to determine activity type, behavioral patterns and user habits based on collected data.

0085In one embodiment, the user monitoring device <b>10</b> uses the accelerometer information to improve the heart rate monitor. As a non-limiting example, the user monitoring device <b>10</b> detects movement and speed. Addition of this data improves the accuracy of the heart rate monitor and corrects for any miscalculations in vibration, noise and skin color.

0086In one embodiment, velocity readouts and accelerometer data are used to measure when to sample heart rate. For example, if the user monitoring device <b>10</b> registers zero velocity readout, the user is probably at rest or engaged in a passive activity. Thus, the user monitoring device <b>10</b> knows not to sample heart rate. This results in conversation of time, energy and data storage.

0087User activity, performance and action can be based on the acceleration and angular velocity of the user monitoring device <b>10</b>. In one embodiment, the user monitoring device <b>10</b> has a feature where the user monitoring device <b>10</b> authorizes third party interaction based on hand gesture, on previous interactions or patterns of behavior. As a non-limiting example, if one purchases a coke every day for the last two weeks, the user monitoring device <b>10</b> can “orders” the person another one based on the prior history.

0088In one embodiment, the user monitoring device <b>10</b> features near-by user monitoring device <b>10</b> recognition that provides for other user monitoring device <b>10</b> devices to be recognized within a particular vicinity and are able to share and transfer data between them. The user monitoring device <b>10</b>'s data analysis and feedback can be based on current or previous sensor output. The user monitoring device <b>10</b> can alert the user when to charge the user monitoring device <b>10</b> and when it is the most convenient for the user.

0089In one embodiment, the user monitoring device <b>10</b> provides feedback via color change. An outer shell of the user monitoring device <b>10</b> can use visual feedback, including but not limited to pigment or color changes to indicate changes in user behavior or to prompt changes in user behavior. In one embodiment, the user monitoring device <b>10</b> is flexible in shape. As a non-limiting example, if the user puts the user monitoring device <b>10</b> over their hand it can expand or contract, morphing to change size and shape.

0090In one embodiment, the user monitoring device <b>10</b> can have a sync feature for multiple bands at the same time.

0091In one embodiment, the user monitoring device <b>10</b> has data transfer to an external device that can be included or not included in system <b>32</b>. Patient monitoring device <b>10</b> could be a data leaching device. For example, the user can relay information to someone else's device (intermediary device) to access Network Systems connected device.

0092In one embodiment, the user monitoring device <b>10</b> can disable the recording of one or more sensors <b>14</b> based on location, acceleration (or lack thereof) and the like.

0093In one embodiment, the user monitoring device <b>10</b> detects different types of transportation and activity based on sensor data. In one embodiment, user monitoring device <b>10</b> can unlock doors or cars. The user can turn it on and off. As a non-limiting example, it can be turned off by having a capacitor switch on top and bottom and is placed in a way that one couldn't accidentally turn it off. As a non-limiting example, turning it off can be done by rotating the user monitoring device <b>10</b> once.

0094In one embodiment, the user monitoring device <b>10</b> recognizes the wearer based on biometric information, previous data, movement pattern, and the like. In one embodiment, the user monitoring device <b>10</b> detects a new user based on an inability to match to user/usage patterns.

0095As non-limiting examples, a variety of different sensors <b>14</b> can be used such as, an altimeter, blood oxygen recognition, heart rate from wrist via sonar, Doppler, based on sound wave and movement, based on pressure, and the like. A pressure sensor <b>14</b> can be placed on a circulatory vessel such as a vein to detect pulse.

0096With the user monitoring device <b>10</b> of the present invention, mechanical actions of the user can be triggered, recognized and evaluated.

0097As a non-limiting example, with multiple users and wearable devices <b>10</b>, a separate user monitoring device <b>10</b> ID is assigned to each of the users A, B AND C, and thereafter the assigned transmitter/monitor <b>14</b> generates user activity data and/or user tracking data. For purposes of this disclosure, monitoring data is defined to include data acquired during the process of monitoring or evaluating a predefined characteristic. The user activity data tracks data from the sensors <b>14</b> is transferred to the receivers <b>34</b> via the wireless connections <b>38</b> represented by a dashed line.

0098A network of receivers <b>34</b> transfers the user activity and/or tracking data to system server <b>16</b> via connection <b>50</b>. System server <b>16</b> includes a processor <b>52</b> configured to process the user data in a known manner. For example, the processor <b>52</b> may convert raw user data acquired by the sensors <b>14</b> into more conveniently readable data.

0099As a non-limiting example, the display <b>42</b> can be implemented to graphically convey user information from system server <b>16</b> in a conveniently readable manner. As a non-limiting example, the user may be a cardiac user with user monitoring data graphically conveyed as a conventional ECG plot comprising a sequence of P-waves, a QRS complexes and a T-waves. As another example, user tracking data may be graphically conveyed as an icon superimposed onto a map to indicate the user's relative location. Alarm <b>44</b> may be included in this embodiment.

0100In some embodiments, system <b>32</b> ID circuitry delivers a unique ID to the wearable device from database <b>18</b>. BLUETOOTH® chips can be coupled with other wearable devices <b>10</b> in the area. This data is then stored, as more fully explained in the following paragraph. The unique ID can be utilized for a variety of different applications including but not limited to payments, social networking and the like.

0101The ID circuitry of system <b>32</b> can include a number of system/components: unique ID storage, communication system, which reads and transmits the unique ID from the unique ID storage, battery <b>24</b> or power system that provides power to enable communication with the user monitoring device <b>10</b>, a pathway system to route signals to through the circuitry, a cluster that crunches information, and a control system, to orchestrate the communication between different systems. All of these systems can be implemented in hardware, software or a combination thereof. Continuing with the telemetry system <b>32</b>, sensors <b>14</b> and sensing devices are disposed on wearable devices <b>10</b> worn by users. Data, such as movement, location, speed, acceleration, and the like, can be acquired, captured and provided to system <b>32</b>.

0102System <b>32</b> and an associated Network System can include an identification reference, including user activity, performance and reference information for each individual sensor <b>14</b> and location.

0103The user activity, performance metrics, data and the like captured by system <b>32</b> can be recorded into standard relational databases SQL server, and/or other formats and can be exported in real-time.

0104In various embodiments, the user monitoring device <b>10</b> and/or system <b>32</b> are fully sealed and have inductively charges. All communication is done wirelessly.

0105In one embodiment, there are no electrical contacts, physical contacts or connections with the user monitoring device <b>10</b>. The user monitoring device <b>10</b> is seamless. The telemetry system <b>32</b> can include a microprocessor with CPU <b>20</b>, memory, interface electronics and conditioning electronics <b>33</b> configured to receive a signal from the sensors <b>14</b>. In one embodiment, all or a portion of the conditioning electronics <b>33</b> are at the user monitoring device <b>10</b>.

0106In one embodiment, the CPU <b>20</b> includes a processor <b>52</b>, which can be a microprocessor, read only memory used to store instructions that the processor may fetch in executing its program, a random access memory (RAM) used by the processor <b>52</b> to store information and a master dock. The microprocessor is controlled by the master clock that provides a master timing signal used to sequence the microprocessor <b>52</b> through its internal states in its execution of each processed instruction. In one embodiment, the microprocessor <b>52</b>, and especially the CPU <b>20</b>, is a low power device, such as CMOS, as is the necessary logic used to implement the processor design. The telemetry system <b>32</b> can store information about the user's activity in memory.

0107This memory may be external to the CPU <b>20</b> but can reside in the RAM. The memory may be nonvolatile such as battery backed RAM or electrically erasable programmable read only memory (EEPROM). Signals from the sensors <b>14</b> can be in communication with conditioning electronics <b>33</b> that with a filter <b>35</b>, with scale and can determine the presence of certain conditions. This conditioning essentially cleans the signal up for processing by CPU <b>20</b> and in some cases preprocesses the information. These signals are then passed to interface electronics, which converts the analog voltage or currents to binary ones and zeroes understood by the CPU <b>20</b>. The telemetry system <b>32</b> can also provide for intelligence in the signal processing, such as achieved by the CPU <b>20</b> in evaluating historical data.

0108In one embodiment, the actions of the user wearing the user monitoring device <b>10</b> with the unique ID can be used for different activities and can have different classifications at system <b>32</b>.

0109The classification can be in response to the user's location, where the user spends it time, with which the user spends its time, determination of working relationships, family relationships, social relationships, and the like. These last few determinations can be based on the time of day, the types of interactions, comparisons of the amount of time with others, the time of day, a frequency of contact with others, the type of contact with others, the location and type of place where the user is at, and the like. These results are stored in database <b>18</b>.

0110In one embodiment, the user wearing the user monitoring device <b>10</b> can access this information from any place where data is presented to the user, including but not limited to mobile devices, the WEB, applications program identifiers, and the like.

0111As a non-limiting example, the user monitoring device <b>10</b> communicates with a base station at system <b>32</b>. The user monitoring device <b>10</b> can intelligently switch between data transfer and charging based on sensor readout. The user monitoring device <b>10</b> can represent data based on connected devices.

0112In one embodiment, the user monitoring device <b>10</b> has the capability of providing recommendations, popularity of locations or activities based on acquired data from the user.

0113In one embodiment, the user monitoring device <b>10</b> has the capability of introducing the user to other people or users based on their data and the user's data.

0114In one embodiment, the user monitoring device <b>10</b> can determine emotion of the user.

0115In one embodiment, the user monitoring device <b>10</b> uses incremental data transfer via BLUETOOTH® and the like. The user monitoring device <b>10</b> can transmit data through the inductive coupling for wireless charging. The user is also able to change the frequency of data transmission.

0116The user monitoring device <b>10</b> can engage in intelligent switching between incremental and full syncing of data based on available communication routes. As a non-limiting example, this can be via cellular Network Systems, WiFi, BLUETOOTH® and the like. In one embodiment, the user monitoring device <b>10</b> has data storage. As a non-limiting example, storage of telemetry data on user monitoring device <b>10</b> can be amounts up to about 16 mg.

0117In one embodiment, data transferred if it's in a selected proximity of a base station of system <b>32</b> or in proximity of an associated connected Network System. In one embodiment, the user monitoring device <b>10</b> has a dynamic change of data capture frequency. The user monitoring device <b>10</b> can be programmed to instantly change how often it samples any sensor <b>14</b> based upon the sensor data. Intelligent data sampling is based on sensor readout.

0118The user monitoring device <b>10</b> can receive firmware updates via a base station <b>110</b> of system <b>32</b>. In one embodiment, the user monitoring device <b>10</b> presents analyzed data and feedback on a website. In one embodiment, the user monitoring device <b>10</b>'s software is based on unique human movement. The user monitoring device <b>10</b> is able to identify its wearer based on the unique patterns of movement, location check-ins and daily habits of the user.

0119In one embodiment, the app can be used on a mobile device, including but not limited to a smart phone and the like.

0120In one embodiment, a breakdown of recounting data that has been collecting is presented for analysis of that data. Observation or recommendations can be presented based on historical information and live information. The importance of the data can be based on past user behavior.

0121In one embodiment, the user monitoring device <b>10</b> has artificial intelligence. A wearable device processor <b>54</b> implements logic resources that exist on user monitoring device <b>10</b>.

0122In one embodiment, user monitoring device <b>10</b> engages in the routing of user information to third parties based on predefined rules, based on system <b>32</b> analysis.

0123In one embodiment, user monitoring device <b>10</b> includes one or more processors <b>54</b> that implement intelligent algorithmic processing and transfer of information to third parties. Feedback can be provided to the end user that is based on visual, tactile, gesture information and the like.

0124The ID can be sent from the user monitoring device <b>10</b> in a variety of different transmit modes, which may be provided as part of the firmware or software of an ID or sensor transmitter <b>14</b>, and which may be utilized selectively during the operation of said sensor transmitter <b>14</b>, may include ‘burst” transmit modes, wherein a burst of data information is transmitted, or “parcel” transmit modes, wherein timed data packets of data, which may, as desired, comprise partial data strings, are transmitted, and, if desired, repeated during time intervals. Further, the sensors <b>14</b> may have programmed therein diagnostic routines or other test modes which assist during manufacture and use, providing the operator with operational status and verification information on said sensor/transmitter <b>14</b>, as needed. Referring to <figref idref="DRAWINGS">FIG. 4</figref>, system <b>32</b> includes data base <b>18</b> which contains the desired transmitter, sensor, <b>14</b> personality data, as well as, the address/device ID bits for each user monitoring device <b>10</b>.

0125In one embodiment, the initial programming of the user monitoring device <b>10</b> for the ID, as well as optionally other personal information of the user, is done securely, as unauthorized future alteration of same thereafter can be utilized as a means of violating system integrity.

0126In one embodiment, an inductive field coil is used for programming the sensors <b>14</b> and ID of user monitoring device <b>10</b>.

0127As illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the user monitoring device <b>10</b> can include a sensor <b>14</b> with an output that be received by an amplifier <b>56</b> and decoded by an I/O decoder <b>58</b> to determine 1/0 logic levels, as well as, both clock and data information <b>60</b>. Many such methods are commonly available including ratio encoding, Manchester encoding, Non-Return to Zero (NRZ) encoding, or the like; alternatively, a UART type approach can be used. Once so converted, clock and data signals containing the information bits are passed to a memory <b>62</b>. Any of these connections provides a logical link from the system's database <b>18</b> to the sensor <b>14</b>, ID of the user monitoring device <b>10</b>, as shown in <figref idref="DRAWINGS">FIG. 5</figref>.

0128In one embodiment, illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, the system <b>32</b> chooses the necessary programmable sensor functions and stores them into database <b>18</b>. In one embodiment, in order to insure that an unauthorized user cannot connect into and program user monitoring device <b>10</b> the following procedure may be used:

0129Both the sensor <b>14</b> and receiver <b>34</b> contain an identical, repeatable pseudo randomization algorithm in ROM or in ASIC logic.

0130Referring to <figref idref="DRAWINGS">FIG. 6</figref>, the algorithm is applied to outgoing programming data <b>64</b> from system <b>32</b> and produces a number of security/randomization bits <b>66</b> that can be appended to the outgoing programming message or message <b>68</b> and sent to a sensor <b>14</b>.

0131Referring to <figref idref="DRAWINGS">FIG. 7</figref> the sensor <b>14</b> likewise applies this pseudo randomization algorithm as the security/randomization bits <b>66</b> to the outgoing programming data, now forming the incoming programming data <b>70</b> to sensor <b>14</b> and produces a several bit result in the shift register <b>71</b>. The scrambling algorithm is devised such that a small difference in the programming bit stream causes a great difference in the pseudo randomization result. As a non-limiting example, the present invention can use a 16 bit polynomial to produce this pseudo randomization.

0132Optionally, in one embodiment, before a sensor <b>14</b> accepts this programming, stored in an address and personality register <b>73</b>, both the pseudo random code, stored in data in a shift register <b>75</b> from system <b>32</b> and a sensor <b>14</b>, in a shift register <b>71</b> must match via a comparator ID, <b>77</b>, indicating unauthorized acceptance use. In addition to insuring authorized access, this process also insures that the data itself is correct. The longer the polynomial sequence used, the greater the security.

0133In one embodiment, spread spectrum or other RF transmission is used and can include programming to determine that the frequency or spread spectrum code is unique to the area. If a spread spectrum code, system code, or frequency channel is found to be occupied at a future time of use. Re-programming of the user monitoring device <b>10</b> is then done with a new, unused spread spectrum code or system code or frequency channel can be selected, or, in the alternative, CPU <b>20</b>.

0134As illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, step “E” would include, for example, the step of the sensor <b>14</b>, inputting the programming message and saving a seed in memory <b>62</b>; with the sensor <b>14</b> utilizing the seed to code digital data bits transmitted.

0135As illustrated in <figref idref="DRAWINGS">FIG. 8</figref>, the location of a user monitoring device <b>10</b> with the ID and sensors <b>14</b> can be determined. As a non-limiting example, in one embodiment the user monitoring device <b>10</b> includes a sensor <b>14</b> that can provide a position signal having positioning data (e.g., raw GPD data or pseudo ranges) and the ID is transmitted from the user monitoring device <b>10</b> to system server <b>16</b>. Server <b>16</b> receives the position signal and analyzes the signal to generate information representing the location of the user monitoring device <b>10</b>. Server <b>16</b> transmits this location information to a client computer where the location of the user monitoring device <b>10</b>, allowing a user to identify the location of the remote sensor <b>14</b>.

0136In one embodiment, the position signal transmitted by the remote sensor <b>14</b> can also include an emergency code. For example, in the event of an emergency, such as a medical emergency or otherwise, a user may press a “panic button” that can be on the user monitoring device <b>10</b> or by use of a user's mobile device. Pressing the panic button may cause mobile device <b>74</b> to transmit an emergency signal to a cell site <b>76</b> where the emergency signal is relayed to server <b>16</b>. In response, server <b>16</b> can transmit Doppler information regarding in-view satellites, a fix command and a time trigger signal to the user monitoring device <b>10</b>.

0137When the location of the user monitoring device <b>10</b> has been determined, software running on server <b>16</b> configures server <b>16</b> such that a call or other signal is sent to a local emergency operator in the vicinity of remote sensor <b>14</b>. When the call or signal is received at the emergency operator station, the location of remote sensor <b>14</b> is transmitted and displayed. In some cases, where separate panic buttons are available for identifying medical, police, fire or other types of emergencies, the nature of the emergency is also displayed for the emergency operator. Based on this information, the emergency operator can initiate an emergency response by providing the location of remote sensor <b>14</b> to the required emergency service (police, fire department, ambulance service, etc.). In other embodiments, instead of or in addition to a position report for the remote sensor <b>14</b>, the emergency operator may also be provided with information which identifies an emergency response vehicle in close proximity to remote sensor <b>14</b>.

0138As illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, a sensor <b>14</b> of the user monitoring device <b>10</b> can include a SNAPSHOT GPS receiver <b>72</b>. As described above, sensor <b>14</b> uses information transmitted from separately located base station <b>110</b>, mobile devices, computers, and other devices, to assist in determining the position of the remote sensor <b>14</b>, as more fully disclosed in U.S. Pat. No. 6,661,372, incorporated herein by reference.

0139As non-limiting examples, and as illustrated in <figref idref="DRAWINGS">FIG. 10</figref>, the sensors <b>14</b> can be a thermal transducer <b>78</b>, an acoustic transducer <b>80</b>, and a magnetic transducer <b>82</b>. It will be appreciated that the present invention is not limited The transducers <b>78</b>, <b>80</b>, and <b>82</b> in the user monitoring device <b>10</b> can communicate with a microprocessor <b>84</b> also located in the user monitoring device <b>10</b>. The user monitoring device <b>10</b> can communicate with other devices via an RF transceiver <b>86</b>, an IRDA transceiver <b>88</b>, and/or an RF backscatter transceiver <b>90</b>. Each of the components in the user monitoring device <b>10</b> receives power as necessary from the battery <b>24</b>, which may include the rechargeable battery.

0140The acoustic transducer <b>80</b> may include a microphone, a low-pass filter, a gain amplifier, and a threshold comparator. The acoustic transducer <b>80</b> may include an omnidirectional microphone, although any other suitable acoustic transducer device would suffice. The microphone may be a surface mount MEMS device that has a frequency range of 100 Hz to 10 kHz. A single MCP602 operational amplifier is used on the acoustic sensor to amplify and low-pass filter the acoustic signal from the microphone. Another operational amplifier is used to generate a voltage reference used for single biasing and detection. The microphone output is biased to the midway point between the circuit supply voltage and ground to allow for both positive and negative signal swings. The biased signal is filtered with a second order low-pass Butterworth filter to remove upper frequency noise. It is then amplified with an adjustable gain that is controlled by a digital resistor potentiometer. This digital resistor operates on an I2C bus and is controlled by the microprocessor <b>84</b>. Lastly, the amplified acoustic signal is threshold detected against a static voltage to detect sufficiently large acoustic signals. The digital output of the threshold detector is connected to the microprocessor <b>84</b> for processing.

0141The magnetic transducer <b>82</b> can include a magnetic sensor integrated circuit, a differential instrumentation amplifier, a low-pass filter, two gain amplifiers, and a threshold detector. The magnetic transducer <b>82</b> may include an NVE AA002-02 GMR (giant magneto resistive) field sensor, although any suitable magnetic sensor would suffice. This sensor has a saturation field of 15 Oe, a linear range of 0 to 10.5 Oe, and a sensitivity of 3 mV/V/Oe. Two MCP602 CMOS operational amplifiers are used on the magnetic sensor to amplify and low-pass filter the analog output signal. An INA122UA instrumentation amplifier is used as a difference amplifier for the differential output from the magnetic sensor. The magnetic sensor IC can be based on Spintronics technology. Its output includes a differential voltage pair proportional to the detected magnetic field. The differential voltage pair is amplified and converted to a single voltage by the instrumentation amplifier. The AC-coupled signal is then amplified and filtered with a low-pass filter to remove upper frequency noise and boost the low-voltage signal output. The signal is amplified a second time by an adjustable gain controlled by a digital resistor similar to the acoustic sensor. Lastly, the amplified magnetic signal is threshold detected against a static voltage, to detect sufficiently large changes in magnetic fields. The digital output of the threshold detector can be connected to the microprocessor <b>84</b> for processing.

0142A DS1803E-010 digitally controlled 10 kOhm variable resistor can be used in both the acoustic and magnetic sensor circuits. It is used to adjust the gain of one gain stage in each circuit. The digital resistor is controlled through an I2C interface. A LMV393IPWR comparator is also used in both the magnetic and acoustic sensor circuits for determining when a sufficiently strong sensor signal has been detected. It compares the analog sensor signal against the voltage reference and its output is tied to the microprocessor <b>84</b> for data collection.

0143The thermal transducer <b>78</b> may include a Burr Brown TMP 100NA/250 12-bit digital temperature sensor, although any suitable thermal sensor would suffice. The digital temperature sensor has an operating range of −55 to +120. degree C., an accuracy of 0.5. degree C. and a maximum resolution of 0.0625 degree C.

0144Even though it is a 12-bit sensor, suitable results are achieved with only 9-bit conversions with only the 8 most significant bits used. The sensor has an I2C interface and is normally kept in sleep mode for low power operation. When directed by the microprocessor <b>84</b>, the thermal transducer can perform a 9-bit temperature conversion in 75 milliseconds.

0145The RF transceiver <b>86</b> may include an RF Monolithic DR3000 transceiver, although any suitable transceiver or separate transmitter and receiver <b>34</b> would suffice. This transceiver <b>86</b> allows for both digital transmission and reception. The transceiver <b>86</b> can have an operating frequency of 916.5 MHz and is capable of baud rates between 2.4 kbps and 19.2 kbps. It can use OOK modulation and has an output power of 0.75 mW. It also can use digital inputs and outputs for direct connection with the microprocessor <b>84</b>. The transceiver <b>86</b> can use an antenna <b>92</b> (<figref idref="DRAWINGS">FIG. 11</figref>) that may include a 17 mil thick plain steel electric guitar G-string cut to a length of 8.18 cm. It is used in a monopole over ground configuration and can require a matching circuit of one inductor and one capacitor. Alternatively, Frequency Shift Keying (FSK), Quadrature Phase Shift Keying (QPSK), or any other suitable modulation scheme may be utilized.

0146The IRDA transceiver <b>88</b> may include a Sharp GP2W0110YPS infrared transceiver, although any suitable IRDA compliant infrared transceiver would suffice. This transceiver <b>88</b> can be IRDA v1.2 compliant and in one embodiment has an operating range of 0.7 meters. In one embodiment, it is capable of 115.2 kbps data speeds.

0147The RF backscatter transmission device <b>90</b> may include circuitry available from Alien Technology (of Morgan Hill, Calif.) for receiving and transmitting signals via RF backscatter. Battery <b>24</b> may be a 3.6 volt ½ AA lithium battery with a capacity of 1.2 amp hours. The battery <b>24</b> can be a power source <b>24</b> that can include a Texas Instruments TPS76930DBVT voltage regulator to regulate the output signal to 3 volts and with a maximum current of 100 mA. The voltage regulator can include a LDO.

0148The RF backscatter transceiver <b>86</b> in the user monitoring device <b>10</b> communicates with an RF backscatter reader <b>94</b> such as a class <b>3</b> reader from Alien Technology. The reader <b>94</b> transmits data to the backscatter transceiver <b>90</b> of the user monitoring device <b>10</b> by broadcasting encoded RF pulses and receives data back from the transceiver <b>86</b> by continually broadcasting RF energy to the sensor <b>10</b> and monitoring the modulated RF reflections from the sensor <b>10</b>.

0149The RF backscatter transceiver <b>90</b> can include a printed circuit board (PCB) patch antenna for RF reception, and RF modulation, a Schotky diode detector circuit, a comparator circuit for signal decoding, and a logic circuit for wake-up. The logic circuit monitors the incoming data, and when an appropriate wake-up pattern is detected, it triggers the microprocessor <b>84</b> so that data reception can begin. In one embodiment, the reader <b>94</b> has an operating frequency between 2402 MHz and 2480 MHz, and uses frequency hopping in this band to reduce noise interference. A modulation method used by the reader <b>94</b> can be On-Off Keying (OOK). In one embodiment, the transmission power is 1 watt. The operation of the reader <b>94</b> may be controlled by an external computer (not shown) as directed by Labview software via a RS-232 serial link.

0150The RF transceiver <b>86</b> can communicate with an external RF transceiver <b>96</b> such as a DR3000 transceiver from Radio Monolithics, Inc. In one embodiment, it operates at 916.5 MHz, uses OOK modulation, has a communication range of 100 meters line of sight, and a baud rate of 19.2 kbps. The active RF antenna <b>92</b> can be a quarter-wavelength monopole made from a guitar G-string and appropriate matching circuitry. Two control lines from the microprocessor <b>84</b> can be used to select the mode of operation, choosing from transmit, receive, and sleep. The active RF receiver <b>34</b> consumes the most power in receive mode compared to the other two communication links.

0151<figref idref="DRAWINGS">FIG. 6</figref> shows the relative positioning and shape of the active RF antenna <b>92</b> and the RF backscatter antenna <b>98</b>.

0152The IRDA transceiver <b>88</b> of the user monitoring device <b>10</b> can communicate with an external IRDA transceiver <b>100</b> that may be identical to the IRDA transceiver <b>88</b>. Alternatively, the IRDA transceiver <b>100</b> can be one such as is provided in most personal digital assistants (PDA) as well as many other consumer devices. The IRDA communication link follows the standard IRDA signal and coding protocol and is modeled after a standard UART interface. In one embodiment, the IRDA transceiver <b>88</b> is capable of data speeds less than 115.2 kbps, and may only have a range of 0.7 meters for transmission. One advantage of the IRDA communication link is that it does not require any of the RF spectrums for operation, but it typically does require line-of-sight communication.

0153When any one of the transceivers <b>86</b>, <b>88</b> and <b>90</b> on the user monitoring device <b>10</b> detect the beginning of valid data on their respective communication link, all other transceivers are disabled, thereby preventing the corruption of incoming data with the noise or partial data packets on the other communication links. However, if the data on the active transceiver proves to be erroneous, the other transceivers will be re-enabled if appropriate to allow normal operation to continue. If the data received by the active transceiver is valid, however, the other transceivers will remain disabled for several hundred milliseconds longer in the high probability that the next data packet will be transmitted on the same communication link. If, after this extended delay, no additional packets are received, then the other transceivers will be re-enabled as appropriate.

0154In one embodiment, the active RF protocol has no wake-up or synchronization packets, and the packets sent to and from the sensor are identical. In one embodiment, the format of an active RF packet is shown in <figref idref="DRAWINGS">FIG. 16</figref>. It can include a preamble to reset and spin-up the state machine of the RF receiver <b>34</b> and to properly bias the receiver's <b>34</b> data slicer/threshold detector for optimum noise rejection and signal regeneration, two framing bits to indicate the beginning and end of the data bytes, and the data bytes themselves.

0155Furthermore, the encoding scheme for the three symbols is shown in <figref idref="DRAWINGS">FIG. 12</figref>. The entire packet is DC balanced to maintain an optimal level on the data slicer/threshold detector and the receiver <b>34</b>. Data is sent most significant bit first.

0156The IRDA communication link can follow the standard IRDA protocol for bit encoding and UART protocol for byte transmission. Packets transmitted on the IRDA link can contain no preamble or framing bits, but they do have a header that contains two bytes. The first byte is an ASCII “I” which denotes the beginning of a valid IRDA packet. The second byte equals the number of preceding bytes in the packet. This value is used by the receiver <b>34</b> to determine when the entire packet has been received and processing of information can begin. The packet structure is shown in <figref idref="DRAWINGS">FIG. 13</figref> and the IRDA/UART encoding scheme is shown in <figref idref="DRAWINGS">FIG. 14</figref>.

0157The data bytes contained in a packet transmitted to the sensor <b>10</b> through any of the communication links conform to a packet format. The CMD section of a packet is a single byte that identifies the type of packet being sent. The CMD byte appears above the beginning and end of the packet and the two must be identical. The reason for including the redundant byte is to further eliminate the chance of a packet's CMD identifier being corrupted at the receiver <b>34</b>, even if the CHECKSUM is correct.

0158The PAYLOAD contains all of the data that must be sent to, or returned from, the sensor. The PAYLOAD is broken down into individual bytes with the overall number of bytes and their content dependent on the type of packet being sent.

0159The CHECKSUM is a 16-bit CRC that is performed on all bytes in the data packet excluding the end CMD byte in packets generated by the external device. The CHECKSUM is sent most significant byte first.

0160The transceivers <b>86</b>, <b>88</b> and <b>90</b> may be required to communicate over a greater distance than do the components described herein. Upgrading these components to be suitable for longer distance transmission is considered to be within the spirit of this invention. The type of transducer is not limited to the specific transducer types described herein. In addition, the logic described herein for arbitrating between which communication device to use to communicate with the outside world and which sensor data to provide at what time is but one possible approach to arbitration logic within such a remote sensor <b>10</b>.

0161In one embodiment, illustrated in <figref idref="DRAWINGS">FIG. 15</figref>, an activity manager <b>218</b> is provided that is used for managing lifestyle activities of the user. Activity manager <b>218</b> can be a standalone device, or as part of the telemetry system <b>32</b> or monitoring device <b>10</b>. The dynamic activity manager <b>218</b> can associate one or more contexts such as time, location, and the like to an activity entered by a user. The dynamic activity manager <b>218</b> also manages an activity and any device or item associated with the activity.

0162In one embodiment, one or more of sensors <b>14</b> can be a lifestyle sensor. For example, the sensor <b>14</b> can be a physiological sensor such as a heart rate sensor, body temperature sensor, caloric sensor, or the like. Another example of a sensor is a pedometer. It should be noted that any sensor or device capable of taking measurements is applicable to the present invention. These sensors can be embedded, for example, in clothing and/shoes or can be stand-alone items. One specific example of these types of sensors is a sensor that is embedded in running shoes. As a user walks or runs, the sensor <b>14</b> monitors various functions such as speed, stride length, body functions (heart rate, temperatures, hydration, and the like), and the like.

0163This information can then be relayed back to the dynamic activity manager <b>218</b> if desired. A web service <b>124</b> can be any type of service subscribed to by the user over the Internet. For example, a user can be subscribed to a weather service that is used by the dynamic activity manager <b>218</b> when monitoring an activity such as running. The dynamic activity manager <b>218</b>, identifier enable items, including but not limited to RFID enabled items <b>220</b>, sensors <b>14</b>, and Network System <b>224</b> are discussed in greater detail below.

0164The dynamic activity manager <b>218</b> provides management for managing user lifestyle activities and is preferably included as part of the telemetry system <b>32</b>. In one embodiment, the activity manager <b>218</b> is in communication to a user interface <b>202</b>, which can be at the monitoring device <b>10</b>, for allowing a user to enter information associated with an activity that the user wants managed and/or monitored. As a non-limiting example, <figref idref="DRAWINGS">FIG. 17</figref> shows one example of the user interface <b>202</b> being displayed on the monitoring device <b>14</b>. It will be appreciated the sensors can generate this information and communicate it with telemetry system. It should be noted that some fields can be automatically populated based on user activity entry, activity history, rules, or the like.

0165In one embodiment, a name entry field <b>302</b> can be used that allows the user to enter the name of an existing activity or the field <b>302</b> can be a drop down box including existing activities. In another embodiment, the monitoring device <b>10</b> or the telemetry system <b>32</b> can perform this activity and function.

0166<figref idref="DRAWINGS">FIG. 16</figref> show that a user has entered the activity of “running”. Therefore, the user is configuring the activity manager <b>218</b> to manage and monitor a running activity. The user interface <b>202</b> can also include an activity description field <b>304</b>, which allows a user to enter a description of the activity. A date entry field <b>306</b> is also included on the user interface <b>202</b>. The date field <b>306</b> allows a user to enter the date or dates when the activity is to occur. A time start field <b>308</b> and an end time field <b>310</b> are also provided in the user interface <b>202</b>. The start time field <b>308</b> indicates when the activity begins and the end time field <b>310</b> indicates when the activity ends.

0167A user may also want the activity manager <b>218</b> to track specific items associated with the activity. For example, with respect to the running activity, a user may want to have her running shoes and headphones tracked to ensure that she has these items when she begins the activity. This information can be entered in the items to be tracked field <b>312</b>. The tracking process is discussed in further detail below. The user may also want to use specific sensors <b>14</b> during the activity such as sensors <b>14</b> in the running shoes and a heart rate monitor. The sensor IDs or names can be added into the sensor field <b>314</b>. A user can also configure the sensor parameters that she wants used during the activity. Alternatively, the sensor parameters can be transparent to a user. For example, the parameters can be pre-populated based on success of data collection of prior activity history. This information is entered in a sensor parameter field <b>316</b>. In addition to having items tracked and sensors <b>14</b> monitored during the activity, the user may want to associate a web service with the activity.

0168For example, a user may want to associate a weather service with the running activity so that the activity manager <b>218</b> can automatically and dynamically adjust settings on the sensors <b>14</b>; determine to track different items; and the like. For example, the activity manager <b>218</b> can monitor the web service to determine if the weather is sunny, cloudy, raining, or the like. If the weather is sunny, the activity manager may determine that a first pair of running shoes, sun glasses, and the like need to be tracked. On the other hand, if the weather is raining, the activity manager <b>218</b> can determine not to track sunglasses and to track a second pair of running shoes. It should be noted that the term “tracked” as used throughout this discussion refers to use of the ID of the monitoring device.

0169Alternatively, a user can setup rules that allow a web service to perform a function based on contexts. For example, if the weather is rainy, a user can have a rule setup that has a web service make a reservation at an indoor track. <figref idref="DRAWINGS">FIG. 16</figref> also shows a web sensor rule(s) entry field <b>320</b>. The web service field <b>320</b> allows a user to enter various rules associated with Network Systems. For example, a user can setup a web service via the web service rules field <b>320</b> to reserve a running track if the temperature outside is less than 60° F. or if it is raining.

0170It should also be noted that the user interface of <figref idref="DRAWINGS">FIG. 16</figref> is only one example of a user interface applicable to the present invention. One or more fields may be added or deleted. For example, the user interface <b>218</b> can also provide a mechanism to a user for reviewing all entered activities, deleting activities, and the like. It should also be noted that the user interface <b>202</b> can also reside on an information processing system coupled to the monitoring device <b>14</b>. For example, the activity manager <b>218</b> can have software loaded on a personal computer that allows the user to enter the above information or to interact with the activity manger <b>218</b>. The activity manager <b>218</b> can then sync with database <b>18</b> to update its data. In yet another embodiment, a user can enter information directly at an identifier enabled item <b>220</b> or a sensor <b>14</b>. For example, a sensor <b>14</b> can include a user interface with a calendar. Any information entered here can then be synced with the activity manager <b>216</b>. Any configuration parameters such as a heart rate baseline, stride length, and the like are then communicated to the activity manager <b>218</b>.

0171Referring again to <figref idref="DRAWINGS">FIG. 15</figref>, the information received from a user, for example, via the user interface <b>202</b> can also be provided to a calendar <b>204</b> residing within the monitoring device <b>14</b>. Alternatively, information from the calendar <b>204</b> can also be extracted by the activity manager <b>218</b>. For example, if the activity manager <b>218</b> determines that a user has entered a new activity in the calendar <b>204</b>, the activity manager <b>218</b> can prompt the user to determine if the user wants the activity manager <b>218</b> to monitor and manage that activity. Although shown residing outside of the activity manager <b>218</b>, the activity manager <b>218</b> can include an internal calendar for monitoring lifestyle activities. In other words, the monitoring device <b>14</b> can include a calendar and the activity manager <b>218</b> can also include an internal calendar used in conjunction with the wireless device calendar <b>204</b>.

0172Based upon the received activity information, the activity manager <b>218</b> creates activity profiles <b>210</b>, <b>212</b> that are stored in an activity management database <b>208</b>. <figref idref="DRAWINGS">FIGS. 17(<i>a</i>) and (<i>b</i>)</figref> shows an example of an activity profile <b>210</b> for a variety of activities. Although <figref idref="DRAWINGS">FIGS. 17(<i>a</i>) and (<i>b</i>)</figref> show a single table that includes multiple activities, each activity can be stored within a separate activity profile. <figref idref="DRAWINGS">FIG. 18</figref> also shows a calendar <b>204</b> comprising calendar events associated with an activity. The activity profile <b>210</b> includes various information associated with an activity such as a name <b>404</b> of an activity, an activity ID <b>406</b>, a sensor or device name <b>408</b> associated with the activity, an identifier/device IP address <b>410</b> if available, data configuration <b>412</b> for the sensor/device and the like.

0173Also, <figref idref="DRAWINGS">FIGS. 17(<i>a</i>) and (<i>b</i>)</figref> show Network Systems <b>414</b> and web service rules <b>416</b> associated with a web service. For example, a web service A is associated with the “running” activity. A web service rule is associated with the web service A that indicates that if the temperature outside is less than 60° F. then reserve an indoor track. As can be seen, the activity profile associates a sensor/device context with activity. The sensor/device context indicates what sensors <b>14</b>/devices or associated with the activity and their current configurations.

0174In the example of <figref idref="DRAWINGS">FIG. 18</figref>, the information within the activity profile <b>210</b> is independent of a time context or location context associated with an activity. In one embodiment, the calendar <b>204</b> associates a time context with and activity and an optional location context. For example, <figref idref="DRAWINGS">FIG. 18</figref> shows a calendar event <b>402</b> set for May 2nd with a “running” activity from 2 p.m. to 3 p.m. The calendar <b>204</b> can also show the location of the activity such as “Millennium Park”. Therefore, the “running” activity has a time context and a location context associated with it. The information within the activity profile <b>210</b> can be used by the activity manager <b>218</b> regardless of the time and location contexts.

0175For example, if the user has defined a “running” activity on two different days at two different times and at two different locations, the activity manager <b>218</b> can still refer to the “running” activity profile and use the information included therein for the two instances of the “running” activity. Therefore, the activity manger <b>218</b> monitors both the calendar <b>402</b> and the activity management database <b>208</b>. However, the activity profiles <b>210</b> can also include time and location contexts as well. In this example, a separate activity profile is stored in the activity management database for each instance of an activity.

0176Returning now to <figref idref="DRAWINGS">FIG. 16</figref>, the activity manager <b>218</b> also includes a context monitoring module <b>210</b>. In one embodiment, the content monitoring module <b>210</b> allows the activity manager to determine whether an activity is about to start, has started, or has ended and either monitor for identifier enabled items <b>220</b> and/or initialize sensors <b>14</b> associated with the activity. For example, the context monitoring module <b>210</b> monitors context such as time, location, device, and the like. The context monitoring module <b>210</b> can monitor the calendar <b>204</b>, GPS, or information entered by the user to determine the current and/or location of the wireless device. The activity manager <b>218</b> can compare activity profiles and/or calendar events with the determined time and/or location to determine whether an activity is starting, ending, or the like.

0177In one embodiment, the dynamic activity manager <b>218</b> is communicatively coupled to a GPS module <b>246</b> and a display <b>244</b>. The GPS module can be used by the dynamic activity manager <b>218</b> to determine the location of the monitoring device <b>14</b>. The display <b>244</b> can be used for, among other things, to display data/information, visual alerts to a user.

0178As discussed above, the activity manager <b>218</b> manages and monitors identifier, enabled items <b>220</b>, sensors <b>14</b>, and Network Systems <b>224</b> associated with a user activity. identifier enabled items <b>220</b> can be any item that is coupled to an identifier or other communication tag. The activity manager <b>218</b> monitors identifier enabled items <b>220</b> via an identifier enabled item monitor <b>206</b>, herein referred to as the “identifier monitor” <b>206</b>. The identifier monitor <b>206</b>, in one embodiment, can be an identifier transceiver embedded with monitoring software or can be a separate monitoring software module coupled to an identifier transceiver.

0179The identifier monitor <b>206</b> can be configured by the user to automatically start monitoring for items associated with an activity or to continuously monitor for identifier enabled items <b>220</b>. For example, when the activity manager determines, based on a time context and/or a location context associated with an activity, that it is time for an activity to start, the activity manager <b>218</b> can begin monitoring for associated identifier enabled items <b>220</b>. For example, if the activity manager <b>218</b> determines that the running activity is about to begin, the identifier monitor analyzes the activity profile <b>210</b> to determine what items are needed for the activity. The identifier monitor <b>206</b> then determines if items such as running shoes and heart beat monitor are present. In other words, the identifier monitor <b>206</b> determines if an identifier signal from the running shoes and the heartbeat monitor has been detected. The activity manager <b>218</b> can then visually, audibly, and/or tactilely notify the user of the presence or non-presence of the items <b>220</b>.

0180Based on the activity profiles <b>210</b>, calendar <b>204</b>, and/or an internal clock the activity manager <b>218</b> can determine that the user has not left for work, to go running, or whatever the activity may be. For example, a user can have a calendar entry or an activity defined for “leave for work”, which begins at 8:00 a.m. Therefore, if the time is 7:30 a.m. the activity manager <b>218</b> can determine that the user has not left for work. In another example, a user can have an activity defined for “running”. The activity manager <b>218</b> can detect that the user has left the house, entered his/her car or the like either by passing an identifier sensor at a door or via GPS and analyzes the activity profiles <b>210</b> accordingly.

0181The activity manager <b>218</b>, based on activity profiles and/or calendar events determines that the user is going straight from work to her running activity. Therefore, the activity manager <b>218</b> monitors for the items associated with the running activity. The activity manager <b>218</b> then notifies the user if these items have been protected

0182In addition to monitoring for associated identifier enabled items <b>220</b> when an activity is to begin, the activity manager <b>218</b> manages sensors <b>14</b> associated with the activity. For example, when an activity is about to begin, the activity manager <b>218</b> analyzes the activity profile <b>210</b> associated with the activity and identifies the sensors <b>14</b> associated with the activity. If the sensor <b>14</b> has not been initialized, the activity manager <b>218</b> initializes the sensor <b>14</b> using the configuration parameters in the activity profile <b>210</b>. For example, the sensors <b>14</b> and the monitoring device <b>14</b> can communicate via a communication manager <b>212</b> within the activity manager <b>218</b>. The sensors <b>14</b> and the monitoring device <b>14</b> can communicate using a wireless connection such as BLUETOOTH®, Zigbee, or the like. In one embodiment, the dynamic activity manager also includes a data fusion module <b>214</b> for performing data fusion with respect to health and fitness information monitored by the sensors <b>14</b>.

0183<figref idref="DRAWINGS">FIG. 18</figref> shows a timing diagram for one example of initializing a sensor <b>14</b> based on the activity manager <b>218</b> detecting the start of an activity. In the example of <figref idref="DRAWINGS">FIG. 18</figref>, a user has a “running” activity defined on the user's monitoring device <b>14</b> and wants to invite a friend to the activity. At time T0 the activity manager <b>218</b> sends an invite associated with the “running” activity to another wireless device. The invite includes the time context, e.g., May 2nd at 2 p.m., and can include an optional location context. At time T1 the invitee wireless device sends an acceptance message to user's monitoring device <b>14</b>. At time T2, the activity manager <b>218</b> determines that the time is 2:00 p.m. and queries the activity management database <b>208</b> to identify the sensors <b>14</b> associated with the “running” activity. The activity manager <b>218</b> also obtains the IP address of the sensor(s) <b>14</b>. The IP address is used by the communication manager <b>212</b> to communicate with the sensor <b>14</b>. In one example, the sensors <b>14</b> associated with the running activity are a sensor within running shoes that measures average speed, distance traveled, and the like. Another sensor can be a hear rate monitor worn in the wrist or an audio headset of the user.

0184At time T3 the activity manager <b>218</b> pings the sensors <b>14</b> to determine if they have been initialized. If the sensors <b>14</b> have not been initialized the activity manager <b>218</b> identifies that configurations parameters of the sensor from the activity profile <b>210</b> and initializes the sensors <b>14</b> accordingly. The sensors <b>14</b>, at time T4, send a ready response to the activity manager <b>218</b>. At time T5 the activity manager <b>218</b> begins collecting data from the sensors <b>14</b>. The activity manager <b>218</b>, at time T6, determines that the activity has completed. At time T7, the activity manager <b>218</b> displays collected data from the sensors <b>14</b> to the user via the user interface <b>202</b>.

0185In another embodiment, a user can configure the activity manager <b>218</b> to only collect specific data from a sensor <b>14</b> or not all data. Also, the activity manager <b>218</b> does not have to communicate with a sensor <b>14</b> during an activity. For example, a user may have forgotten the monitoring device <b>10</b> at her house. The application manager <b>218</b> determines that an activity is starting, but sensors <b>14</b> are not in the vicinity. When sensors <b>14</b> come back into range with the monitoring device <b>14</b>, e.g., the user comes home from running, the activity manager <b>218</b> queries the sensor <b>14</b> for the data collected during the activity. In one example, the sensors <b>14</b> collect data continuously and in another example the sensor <b>14</b> only collects data during scheduled activities. For example, a user's watch may have a biometric sensor that collects data throughout the day. However, the user may only be concerned with plotting data during athletic activities such as bicycling. Therefore, the activity manager <b>218</b> can query the sensor <b>14</b> for data only collected during a bicycling activity. In the above embodiments, the sensors include memory for storing data.

0186As illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, the activity manager <b>218</b> can also monitor and manage Network Systems <b>224</b> associated with an activity. For example, a user can define rules associated with Network Systems <b>124</b> that are to be applied to the activity manager <b>218</b> with respect to an activity. One example is where a user subscribes to a weather service. The user can define a rule that states if the weather is rainy during the time period associated with an activity, then delay any monitoring or managing for that activity for 1 hour. Another rule can state to delay any managing or monitoring until a user prompt is received. The activity manager <b>218</b> can query the web service <b>124</b> at the start or prior to an activity starting to obtain the required information.

0187The activity manager <b>218</b> can also make dynamic decisions for when to monitor and/or manage an activity. For example, a user has an activity defined for “pick up dry-cleaning” at 3:00 p.m. However, at 12:00 p.m. the user runs errands and is approaching the dry cleaners. The activity manager <b>218</b> can detect the location of the user via GPS and determines that the user is near the dry cleaners. The activity manager then determines that the user needs to pick up the dry cleaning and prompts the user to pick up the dry cleaning even though the time is prior to the 3:00 p.m. scheduled pickup time.

0188<figref idref="DRAWINGS">FIG. 19</figref> is a block diagram illustrating a detailed view of the wireless device <b>104</b> according to an embodiment of the present invention. The wireless device <b>104</b> operates under the control of a device controller/processor <b>602</b>, that controls the sending and receiving of wireless communication signals. In receive mode, the device controller <b>602</b> electrically couples an antenna <b>604</b> through a transmit/receive switch <b>606</b> to a receiver <b>608</b>. The receiver <b>608</b> decodes the received signals and provides those decoded signals to the device controller <b>602</b>.

0189Referring now to <figref idref="DRAWINGS">FIG. 20</figref>, monitoring device <b>10</b> and/or telemetry system <b>32</b> can include a feedback system or subsystem <b>710</b> coupled to processor <b>20</b> and/or <b>34</b> to communicate feedback data back to the monitoring device <b>10</b>. In one embodiment, the feedback system or subsystem <b>710</b> can generate and communicate closed-loop control data (“CCD”) <b>712</b> to monitoring device <b>10</b>. For example, closed-loop control data <b>712</b> can provide feedback to the monitoring device user or patient. It will be appreciated that feedback system or system <b>710</b> can be included in monitoring device, telemetry system <b>32</b> or be a standalone system or subsystem.

0190In another embodiment, feedback system or subsystem <b>710</b> can generate and communicate signals <b>714</b> for video/audio data communication to the monitoring device user or patient.

0191In another embodiment feedback system or subsystem <b>710</b> can generate and communicate monitoring device user or patient control data (“PCD”) <b>716</b> to the monitoring device user or patient. In another embodiment, feedback system or subsystem <b>710</b> generates and communicates sensing control data (“SCD”) <b>718</b> to a feedback system <b>720</b> associated with the monitoring device <b>10</b> for providing feedback to the monitoring device user or patient. Signals and data <b>712</b> through <b>718</b> can be converted into signals for executing feedback information, visual, audio and the like, to the monitoring device user or patient.

0192An example of feedback system or subsystem <b>710</b> includes, but is not limited to, a feedback engine installed as software and/or firmware on any type at the telemetry system <b>32</b>. In one embodiment, the feedback system or subsystem <b>710</b> is at monitoring device <b>10</b> and receives feedback signals from telemetry system.

0193<figref idref="DRAWINGS">FIG. 21</figref> is a flow chart <b>700</b> illustrating one embodiment of proving feedback and/or alerts to a user through or without monitoring device <b>10</b>. Flow chart <b>700</b> and other flow charts presented herein are intended to illustrate the functional operation of the device feedback system or subsystem <b>710</b> and should not be construed as reflective of a specific form of software or hardware necessary to practice the methods described. It is believed that the particular form of software will be determined primarily by the particular system architecture employed in the device and by the particular detection and electrical stimulation delivery methodologies employed by the device.

0194At block <b>702</b>, user or patient feedback is detected. Examples of feedback include but are not limited to lifestyle parameters, medical conditions, lifestyle events, exercise parameters, battery <b>24</b> life of the monitoring device <b>10</b>, battery <b>24</b> replacement required, lead or sensor <b>14</b> function, pending therapy delivery, and the like. The type of feedback and alert conditions detected can vary.

0195At block <b>704</b>, a feedback or alert is selected that is associated with a detected feedback or alert condition. Selection of a feedback or alert signal may involve the selection of any of the above listed parameters listed above relative to user or patient, used to control the feedback or alert signal. At block <b>706</b> the feedback or alert signal is delivered according to settings selected at block <b>704</b>.

0196At block <b>708</b>, a sensor <b>14</b> signal is measured at telemetry system <b>32</b> or monitoring device <b>10</b>, analyzed and compared to a threshold level corresponding to the selected alert level at block <b>710</b>. An alert threshold level may be predefined or tailored to a given monitoring device user or patient. If the measured sensor <b>14</b> response does not correspond to an expected threshold signal level or characteristic pattern of the selected feedback or alert signal, the feedback or alert signal is adjusted at block <b>712</b> in a closed-loop feedback method until the sensor signal measured at block <b>708</b> falls within a desired range of an expected threshold level, as determined at block <b>710</b>. Once the desired feedback or alert signal level is reached, the feedback or alert signal stimulation parameters are maintained at the current settings at block <b>714</b> to maintain the sensor signal measurement within a desired range of the threshold. Maintaining the feedback or alert signal response within a desired threshold range promotes the reliability of the feedback or alert signal in informing the monitoring device user or patient of a detected parameter described above.

0197Determining that the sensor signal corresponds to a selected feedback or alert threshold at block <b>710</b> may involve detecting a magnitude of the a sensor signal amplitude or frequency, and/or recognizing an intended alert pattern (e.g. short-long burst sequences, strong-weak burst sequences, or the like) based on a morphology of the sensor signal. As such, measuring the sensor signal at block <b>708</b> may involve measuring signal magnitude as well as frequency characteristics during the feedback or alert signal delivery.

0198Additionally or alternatively, frequency characteristics of the sensor signal may be determined to detect sensor <b>10</b> signals. The frequency power band of the sensor may be analyzed for correspondence to frequency, amplitude and the like. Additionally, a sensor waveform may be evaluated for correspondence to a frequency or amplitude. A combination of the amplitude and frequency of the sensor signal may also be measured to determine a monitoring device user or patient medical or lifestyle condition.

0199The feedback or alert signal may be terminated if a predetermined maximum alert duration has expired, as determined at block <b>716</b>. If a maximum feedback or alert signal duration is not reached, the feedback or alert signal may continue to be held at the current stimulation signal settings at block <b>714</b> until the alert expires. Alternatively, the process may return to block <b>708</b> to continue monitoring the sensor signal throughout the duration of the alert delivery in order to make further adjustments at block <b>712</b> as needed to maintain a desired strength and pattern of the monitoring device user or patient feedback or alert signal. If the feedback or alert signal maximum duration is reached, the signal may be immediately terminated at block <b>722</b>.

0200In some embodiments, if a monitoring device user or patient acknowledgement signal is received prior to the maximum signal duration expiring, as determined at decision block <b>718</b>, the feedback or alert signal is terminated at block <b>722</b>. A monitoring device user or patient acknowledgment may be in a variety of forms.

0201In one specific embodiment, if monitoring device user or patient acknowledgement is not received or detected at block <b>718</b>, the intensity of the feedback or alert signal may be increased at block <b>720</b>, steadily or in step-wise, pre-determined intervals within a feedback or alert signal maximum duration. It will be appreciated that monitoring device user or patient acknowledgement is not required. The intensity may be increased at block <b>720</b> according to a predefined pattern by increasing pulse amplitude (up to some maximum), increasing pulse width, increasing pulse frequency or other adjustment that causes a relatively stronger contraction, i.e., greater recruitment of the muscle being stimulated. Adjusting the intensity of the feedback or alert signal at block <b>720</b> may also be performed using sensor signal feedback control by returning to block <b>708</b> to compare measured sensor signal characteristics to a next higher feedback or alert signal threshold level. In other words, the sensor signal is compared to a different, increased intensity, threshold than an initial threshold in order to control the feedback or alert signal to elicit a stronger response as compared to the initial feedback or alert signal settings. Thus for a given alert condition, multiple alert intensity levels may be stored in the telemetry system <b>32</b> memory along with multiple expected sensor signal responses or thresholds for each intensity level. The sensor signal is used in a closed-loop feedback method to adjust feedback or alert signal control parameters to achieve a feedback or alert signal with the desired intensity at each level.

0202The feedback or alert signal may be delivered continuously, with continuous or stepwise increasing intensity according to a predefined pattern, until either a maximum alert duration is reached or a monitoring device user or patient acknowledgment is received. In other embodiments, a feedback or alert signal may be delivered intermittently until monitoring device user or patient acknowledgement or expiration of a maximum feedback or alert signal duration, whichever occurs earlier. When delivered intermittently, the feedback or alert signal is delivered at an initial intensity for a predefined alert interval. The feedback or alert signal is held at the current settings at block <b>714</b> until the alert interval has expired as determined at block <b>719</b>. If the alert interval expires, the intensity is increased at block <b>720</b> and the feedback or alert signal is resumed for another feedback or alert signal interval at block <b>721</b>. A pause between differing feedback and alert signal intensities may be applied. As a non-limiting example, the feedback or alert signal may be delivered for a 30 second interval at an initial intensity. This process may continue until a maximum alert duration is reached as determined at block <b>716</b>, or monitoring device user or patient acknowledgement is received at block <b>718</b>.

0203As non-limiting examples, a maximum alert duration may be set at 5 minutes, 10 minutes, 30 minutes, one hour or more and may be set differently for different alert conditions, e.g. according to the seriousness of a particular alert condition. Alert intervals applied during the maximum alert duration may be set differently for different alert conditions and different alert intervals may be applied during a given maximum alert duration. For example, the alert intervals may increase in length as feedback or alert signal intensity is increased.

0204The same is true relative to the amplitude and duration of the alert signal.

0205If a maximum alert duration is not reached the alert is terminated at block <b>722</b> and optionally repeated at a later time. As described above, a maximum alert duration may correspond to a continuously delivered feedback or alert signal, which may be increased in intensity according to a predefined pattern, or an intermittently delivered feedback or alert signal that includes successive intervals of increasing intensity of the feedback or alert signal with intervening pauses of no feedback or alert signal.

0206In some embodiments, initial feedback or alert signal settings may be “learned” over time, based on a monitoring device user or patient's response to prior alerting attempts. When a monitoring device user or patient acknowledgement is received at block <b>718</b>, the feedback or alert signal control parameters are stored at block <b>723</b>. These alert settings may be used as the initial feedback or alert signal settings the next time the same alert condition is detected (or another condition using the same feedback or alert signal). These stored settings can also be used for further analysis. In one embodiment, the user or patient can provide input relative to the feedback or alert signal. This input can be used to adjust the thresholds for the alerts. In this way, if a previous alert was generated and no monitoring device user or patient acknowledgement occurred until a particular sensor signal amplitude or frequency measurement was reached, the next time the alert is generated, the alert is delivered using a lower setting at which a monitoring device user or patient acknowledgement occurred to improve responsiveness of the monitoring device user or patient to feedback or alert signals.

0207Adjustment of user or patient parameters at block <b>712</b>, as the result of an input provided by the user or patient can be provided for maintaining a feedback or alert signal within a targeted threshold level.

0208The monitoring device <b>10</b> and/or the telemetry system <b>32</b> can include a feedback loop. User and patient profiles can be stored in database <b>18</b>, which can include a non-volatile memory. A user or patient can input information <b>64</b> about the desired circumstances or parameters relative to a parameter that is measured by a sensor <b>14</b>. The processor <b>20</b> and/or <b>34</b> can include a variety of different user and patient profiles relating to information obtained from sensors <b>14</b>. The processor <b>20</b> and/or <b>34</b> can customize by either scaling or modifying the user or patient profile based on additional user or patient input information.

0209Furthermore, feedback or alert signals corresponding to different alert conditions may be distinguished by the monitoring device user or patient by delivering the feedback or alert signals to different body locations. When feedback or alert signals are delivered to different body locations, multiple sensors may be required in the telemetry system <b>32</b> system such that a sensor signal responsive to alert stimulation at each body location is available. Depending on the number of body locations and relative distance there between, one or more sensors may be implanted in order to provide at least one sensor in operative relation to each of the targeted alert stimulation sites.

0210<figref idref="DRAWINGS">FIG. 22</figref> is a flow chart, illustrating one embodiment for a method of establishing control parameters for a monitoring device user or patient feedback or alert signal and a sensor signal threshold range for the feedback or alert signal. At block <b>802</b>, a set-up procedure is initiated. In one embodiment, this can be achieved using an external programmer having a user interface. In another embodiment, information from the telemetry system database <b>18</b> that has been collected is utilized, along with any user or patient input. The process shown in flow chart <b>800</b> may be performed at any time. In one embodiment, it is done at the time the user or patient is connected to monitoring device <b>10</b>. In another embodiment, it is done at a time subsequent the initial connection of the user or patient to the monitoring device <b>10</b>. The process allows the establishment alert conditions and corresponding feedback or alert signals tailored to a particular monitoring device user or patient's needs. An alert condition is selected at block <b>804</b>, which may be any of the parameters listed above, that receive input from a sensor <b>14</b>. Alert conditions may be predefined or customized for a monitoring device user or patient.

0211At block <b>806</b>, a feedback or alert signal pattern for the alert is selected from a person or from telemetry system database <b>18</b>, and the like, which may be a default pattern for a selected alert condition or customized using any combination signals from sensors <b>14</b>. Various parameters controlling the alert signal may be programmable.

0212Optionally, at block <b>808</b> a test signal is delivered to the monitoring device user or patient according to a selected sensor signal value. In one embodiment, the sensor signal is measured during the test signal at block <b>810</b>, which may include measurements of both signal magnitude and frequency characteristics. At block <b>812</b>, the patient/user may optionally provide input to establish whether the test signal is adequately perceivable and distinct from any other feedback or alert signals that have already been established. User or patient feedback may be received by a user interface included in a monitoring device <b>10</b>, home monitor, device programmer, or other external device in communication with the telemetry system <b>32</b>. User or patient feedback may be received by a variety of different ways known in the art when the signal is acceptable or using a signal transmitted by telemetry system <b>32</b> or monitoring device <b>10</b>. A feedback or alert signal may be unacceptable to the monitoring device user or patient.

0213If the signal is not acceptable to the monitoring device user or patient, or not adequately measured by a sensor <b>14</b> to facilitate closed-loop feedback of the signal, as determined at block <b>814</b>, one or more feedback or alert signal control parameters is adjusted at block <b>816</b>, and the process at blocks <b>808</b> through <b>814</b> repeats until an acceptable feedback or alert signal is established. The feedback or alert signal settings and the sensor signal characteristic(s) associated with the acceptable feedback or alert signal are stored at block <b>818</b> to establish a threshold range of the magnitude and/or frequency characteristics of the sensor signal for the given feedback or alert signal.

0214If additional alert conditions can be detected by the telemetry system <b>32</b>, as determined at block <b>820</b>, a unique feedback or alert signal pattern can be selected for the next alert condition by returning to block <b>804</b> and repeating the process shown in blocks <b>804</b> through <b>818</b>. Each alert condition may be assigned a unique monitoring device user or patient feedback or alert signal that is established by storing expected sensor signal characteristics with corresponding feedback or alert signal parameters. The monitoring device user or patient can provide feedback such that each feedback or alert signal is easily perceived, recognized and distinguished from other feedback or alert signals.

0215For each acceptable feedback or alert signal, a sensor threshold level is established, which may include both a magnitude component and a frequency component. The stored sensor signal thresholds allow the feedback or alert signal to be adjusted as needed during an actual monitoring device user or patient alert to most closely match the magnitude and/or frequency characteristics of the established feedback or alert signal. The monitoring device user or patient can be “trained” to recognize different feedback or alert signal patterns, intensities (strength or duration of the muscle response), and/or locations and their correspondence to different alert conditions.

0216Once all sensor-based threshold characteristics have been stored for all alert conditions, the process is terminated at block <b>822</b>. The stored sensor signal data can then be used in a closed-loop feedback method for controlling feedback or alert signal stimulation parameters during normal operation of the telemetry system <b>32</b> as described in conjunction with <figref idref="DRAWINGS">FIG. 21</figref>.

0217As illustrated in <figref idref="DRAWINGS">FIG. 21</figref>, one or more analysis tools at the telemetry system <b>32</b> the user information and produces analysis information that is sent to the telemetry system <b>32</b>. The one or more analysis tools can be part of or separate from the database <b>18</b>.

0218The database includes base standards for at least one of user, activities, behaviors, habit information and health information that is indicative of a healthy lifestyle of activities, behaviors, habit information, exercise programs and health condition. The user information received from the monitoring device <b>10</b> is analyzed relative to the base standards in the database. In one embodiment, the base standards in operation are updatable. The update information includes updated base standards.

0219The foregoing description of various embodiments of the claimed subject matter has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the claimed subject matter to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. Particularly, while the concept “component” is used in the embodiments of the systems and methods described above, it will be evident that such concept can be interchangeably used with equivalent concepts such as, class, method, type, interface, module, object model, and other suitable concepts. Embodiments were chosen and described in order to best describe the principles of the invention and its practical application, thereby enabling others skilled in the relevant art to understand the claimed subject matter, the various embodiments and with various modifications that are suited to the particular use contemplated.