Patent Grant
9679494
Field of Invention
Our invention relates to modular personal network systems and methods. In particular this invention relates to wireless networks of individual components that can be easily added to or removed from the network to change its functions, and in which the individual components are worn, carried, or used on or about the person of the user.
Background Art
A number of individual portable personal devices are available today. Such personal devices provide specific functions to a person, in a number of different fields of use. For example, there are mobile phones, personal digital assistants, medical monitoring devices, personal entertainment systems, and athletic monitoring systems. These and other portable electronic devices have significantly improved the convenience of many activities.
However, each of these functions is provided individually. None of these individual devices can combine with any of the other devices to provide improved functions. If a user wishes to upgrade the capabilities of any of these devices, a new, expensive device must be purchased and the old device discarded.
What is needed is a system in which individual portable device modules can be combined in a multitude of ways to provide an infinite variety of functions. A portable system is needed in which new functions can be added by simply adding or replacing a single component. A portable system is needed in which the functions can be modified simply by downloading new software or other parameters. A system is needed in which functions in different fields of use can be easily combined. And a system is needed in which the economies of scale and scope of building devices across multiple fields of use can be used to benefit users of devices in all of the fields of use.
Wireless communication protocols have been defined. Bluetooth and IEEE 802.15 are two examples of protocols that may be used with personal portable devices. What is needed is a system that provides the advantages of a modular personal network, and that uses a standard wireless communication protocol such as one of these.
U.S. Pat. No. 6,047,301 (2000) and U.S. Pat. No. 6,336,126 (2002) both to Bjorklund, et al., disclose a wearable computer that communicates with a display device using an optical link, and with a local area network using a radio communications link. However, the system described is not modular, nor is it extensible.
U.S. Pat. No. 6,324,053 (2001) to Kamijo discloses a wearable data processing system. However, this system depends on a network of wiring stitched into the clothing of the user.
U.S. Pat. No. 6,108,197 (2000) to Janik discloses a flexible wearable computer.
However, this disclosure does not envision the needed extensibility.
U.S. Pat. No. 5,781,913 (1998) to Felsenstein, et al., discloses a wearable hypermedium system. It is designed to allow a user to access a large amount of electronic information using a hands-free system, but does not include provisions for extending to other unanticipated uses.
A personal area network has been disclosed. For example, U.S. Pat. No. 6,331,972 (2001) to Harris, et al., discloses a circuit and method for personalizing an electronic device through a personal area network. U.S. Pat. No. 6,314,091 (2001) to LaRowe, Jr., et al., discloses a wireless personal area network with a plurality of peripheral devices, wherein a hub device provides attachment and detachment of peripheral devices. U.S. Pat. No. 6,128,290 (2000) to Carvey discloses a personal data network that uses low duty cycle pulsed radio frequency energy to communicate and provide synchronization. U.S. Pat. No. 5,909,183 (1999) to Borgstahl, et al., discloses a method for programming an appliance by a controller in a personal area network. U.S. Pat. No. 5,898,831 (1999) to Hall, et al., discloses a method for including an appliance in a personal area network and programming security criteria. However, none of these systems provides the needed flexibility of our modular personal network (MPN). For example, each of them requires a controller to be one of the devices in the personal area network. These systems do not anticipate the needed methods for downloading data to a personal area network from a personal computer or other system, nor for retrieving data from a personal area network to a personal computer or other system. And the wide variety of components, configurations, and uses has not been anticipated.
Users need more flexibility in display devices, such as how they are worn so that they may be easily viewed during different activities. Users need display devices that can be easily modified in their position and orientation. Users need a variety of mounting options for individual components in an MPN. Users need an audio device that can be easily worn during various activities, that can be heard during activities with ambient noise, and that won't disturb other nearby people. Users need a system that provides multiple types of audio output in an intelligent fashion. Users need a variety of input devices for different types of activities, and which can be easily accessed during those activities.
Users need to be able to reuse the same components for multiple purposes. These purposes may include time keeping. Users need a network that allows communication with other individuals, who may or may not have their own MPNs. Users need a network that provides entertainment features, including playing music, playing games, and capturing audio and video. Users need a portable system that combines personal organization functions with other functions. Users need a mobile journal system that can be customized for different types of uses, such as travel, athletics, healthcare, or other purposes. Users need a system that provides guidance features, and combines them with other features, such as audio and video annotations, collection of personal data, and athletic workouts.
Users need a system that can provide a variety of athletic functions, such as downloading workout control parameters as well as uploading results of a workout. Users need a system that can interface with exercise equipment, bicycles, and other personal equipment. They need a system that collects performance data, detects and corrects errors in the collected data, and estimates secondary data, based on the collected primary data. Athletes need a mobile system to measure cadence and stride length. Some athletes need reminders to consume water, sodium, and food. Swimmers need a system to measure and log lap-swimming workouts. Runners and other athletes need a mobile system to provide form feedback. Athletes need a system that can work with another system to provide a competition between multiple athletes.
Physical therapist, doctors, and other healthcare professionals need a system that can provide a variety of functions, such as measuring user capabilities, monitoring changes, keeping a medical journal, measuring metabolic parameters, detecting medical problems, providing treatments, and providing medical databases. A system is needed that allows components to be ingested, injected, or implanted, as well as worn, carried, or mounted on personal equipment. A system is needed that provides alternate input, output, and mounting for a disabled user.
Travelers and outdoor users need a system that provides a variety of integrated features. For example, a system is needed that combines translation, travel information repository, wildlife recognition, weather, route guidance, local entertainment, and orienteering functions. A system is needed that can provide user identification functions and that can use that identification to provide other services, such as transfer of money and product purchasing and discounts. Users need a system that can provide personal security features, such as audible alerts, transmitted alerts, and storing emergency information. A system is also needed that can support military needs.
Our invention satisfies these and other needs by providing a modular personal network (MPN). A main aspect of our invention is a system that allows multiple individual network components (INCs), each with one or more primary functions, to be used in a wireless personal network, and that INCs may be added and removed modularly to add or remove functions of the MPN. This includes the ability to add INCs that were not anticipated when the MPN was first assembled. INCs are personal, in that they may be worn, carried, mounted on personal equipment, or otherwise used in proximity to the person associated with the MPN. Another aspect of our invention is that it supports INCs from different manufacturers, of different models, of different types, and with different capabilities. Another aspect is the ability to download software, data, settings, and other information into an INC to control functions of the MPN, and to upload data from an INC. Yet another aspect of our invention is the use of a common network identifier among the INCs of the MPN, to prevent interference between INCs that may be part of different MPNs, and to prevent the unauthorized use of an INC. Still another aspect of our invention is a single turn on or turn off command to turn on or off all INCs in an MPN.
Another aspects of our invention is a control unit, which may be an INC containing a processor and memory for controlling other INCs in the MPN. Alternatively, there may be no control unit, and each INC may provide its own control. A base station or personal computer may interact with the MPN, to download software, data, and settings, and to upload data that may have been collected by the MPN. The MPN may interact with a wide area network, such as the Internet, using the base station or personal computer in another aspect.
Another aspect of our invention is that one of the INCs may function as a display device. A display INC may be mounted on the back of the wrist in a manner similar to a wristwatch, it may be worn on the side of the wrist or hand, or it may be worn in any other suitable location. The orientation of the display may be changed to suit the needs of the user. In another aspect of our invention, the display INC or other INCs may be worn using a reconfigurable mount that allows easy repositioning and replacement of the INC.
Another aspect of our invention is that one of the INCs may function as an audio output device, which may provide audio cues, voice, music or other types of audio information. The audio output INC may include headphones, ear inserts, or speakers that mount in a hat or headband. If multiple types of audio output are supported, one audio signal may be paused or muted while the other is generated.
Another aspect of our invention is that one of the INCs may function as a user input device, and may include a device such as a button or pressure sensor, a touch pad and stylus, or a voice input. Pressure sensors may be worn on the hand, fingers, foot, or waist, where they may be easily operated by tapping.
Another aspect of our invention is that it may be used for one or many purposes, and that the purposes may be changed as INCs are added or removed, as software or data is downloaded, or as a user changes activities. Purposes may include time-related, communications, entertainment, personal organization, guidance, athletic, physical therapy, medical, disability-related, travel-related, outdoor-related, identification, security, military, or other purposes or combinations of purposes.
Time-related purposes of our invention may include providing the current time, multiple time zones, stopwatch functions, and interval timing functions, and may also be used to synchronize other functions of the MPN. Communications functions may include communicating with another MPN to provide games, competitions, and to transfer personal information, software, music, and other information. Other communications functions may include telephone, paging, instant messaging, and electronic mail. Entertainment functions may include playing recorded music or radio, recording audio or video, or playing a game. Audio, video and images recorded by the user may be linked to other personal data that may have been simultaneously collected by the MPN. Personal organization functions may include scheduling appointments, managing contacts, managing a task list, and keeping an electronic journal. An electronic journal may support text, audio, sketch, image, and video entries, may automatically tag journal entries with time or location, may allow journal entries to be linked to database entries, and may allow journal entries to be uploaded to a personal computer and converted to a standard file format. Guidance functions may include providing position, elevation, and speed information, providing route guidance, and collecting and annotating position information with text, audio, video, and personal data. Guidance functions may also include recommending an athletic training route based on desired workout parameters, and comparing personal data collected during multiple sessions.
Athletic functions may include controlling a workout, including controlling individual sections of a workout, and collecting results from a workout. A coaching interface may provide creation and monitoring of a workout plan. Both music and audio athletic cues may be provided. An INC of the MPN may control a setting on a piece of exercise equipment, or may collect data from a piece of exercise equipment. The MPN may measure distance, speed, heart rate, cadence, stride length, and other athletic data. Errors in collected data may be corrected. Secondary performance parameters may be estimated based on collected data and other stored information. An athlete may be reminded to consume water, sodium, food, or other consumables. Two athletes with MPNs may be provided a competition. The MPN may provide lap counts, workout logging, and other lap swimming functions. The MPN may provide form feedback to an athlete. An athletic journal may also be provided.
Physical therapy functions may include measuring range of motion, doing gait analysis and form feedback, testing muscle strength, monitoring changes in physical capabilities, and providing a physical therapy journal. Medical functions may include measuring a metabolic value, detecting a medical problem, controlling a treatment device or taking other medical actions, providing emergency communications, providing storage of medical databases, and providing a medical journal. INCs may be worn or carried by a doctor, patient, or nurse, mounted on equipment such as a wheelchair, or implanted, injected, or ingested into a patient. Functions for a disabled user may include alternate output methods, alternate input devices, and mounting an INC on a wheelchair or other equipment.
Travel-related functions may include language translation, currency conversion, time zone conversion, route guidance, local information, guidebook functions, wildlife recognition, a travel journal, weather information, transit information, local entertainment information, and expense tracking Outdoor-related functions may include direction, position, elevation, route, and weather features. Identity functions may use a smart card, personal code, or biometric information to identify a user to another person or system, and may provide exchange of money, product discounts, and purchasing features. Security functions may include an audible alert, an alert message to a public safety facility, and storing emergency contact and emergency medical information. Military functions may include communications, global positioning, guidance, and weather functions.
An MPN is a set of INCs that communicate using a wireless network. These INCs use a common communications protocol, such as the Bluetooth protocol or the IEEE 802.15 standard, to send messages between themselves. Using a common protocol means that the same electronic components and software can be used in each of them, keeping the cost low.
A common protocol also allows new INCs to be added more easily. This invention is “modular,” in that new INCs can be added at any time. This may change the function of the overall system. As INCs are added, the system's capabilities will grow. As one INC replaces another, the functions of the system change accordingly. The system will continue to function, with reduced capabilities, as INCs are removed. INCs may be built by various manufacturers, and may have different capabilities.
Our invention is also “personal.” This means that the MPN is small in size, roughly encompassing one person's “personal space.” INCs may be worn by the user, they may be carried by the user, or they may just be in close proximity, for example mounted on personal equipment. Also “personal” is the fact that MPNs provide exactly the functions that the individual wants, because the combination of INCs is virtually limitless.
The MPN may be changed at any time, and the functions of the system may change correspondingly. For example, a new INC may be added, and a new function may be enabled by the system. An INC may be removed, and a function of the system may be disabled. The system may automatically detect a change in the MPN, and correspondingly change the functions. Alternatively, a user may enter a changed configuration, for example into a base station, control unit, or personal computer.
Another advantage of our invention is that it is extensible. This means that an INC can be added at any later time, even though that specific INC and its functions may not have been anticipated at the time the system was first put together. Each new INC uses the same communications methods and protocols to send and receive data and commands. The functions of the system are controlled by downloaded software. This means that new software can be downloaded to support the unanticipated new INC.
Software may be downloaded into an INC in the MPN, such as a “control unit.” The control unit may include memory for holding software and data, and a processor. The control unit may send commands and data to some INCs and retrieve data from other INCs. By modifying the software in the control unit, the system may support previously unanticipated INCs. Software may also be downloaded into any other INC.
Software may be downloaded into an INC of the MPN by a personal computer. Software on the personal computer may control what is downloaded. The software on the personal computer may allow extensions to support unanticipated functions and INCs. The software extensions may allow the user to specify software modules to download, to configure parameters for the unanticipated INCs, or to perform other functions related to additional INCs and functions.
One of the INCs in the MPN may be a “base station.” This base station may used to download information, such as software, data, setup options, and time, into at least one of the other INCs, such as the control unit. The base station may, for example, be connected to a personal computer. The base station, in that embodiment, may provide wireless connectivity to one or more of the other INCs, while the personal computer provides storage and a user interface for manipulating the information sent to and from the INCs in the MPN. The base station may communicate with the personal computer over a standard connection, such as a universal serial bus (USB), serial port, Ethernet, wireless network, infrared, PC Card interface, or over a direct connection to the personal computer's bus.
The personal computer may provide a user interface for controlling the INCs in the MPN. For example, the computer may allow the user to specify what functions are to be enabled by the system, which may then determine what software to download. The user may set configuration parameters that would then be downloaded to the INC(s) in the MPN.
The base station or personal computer may also have a wide area network connection, such as an Internet connection. This may allow another person to control functions of the system. This could include a healthcare professional, if the system is being used for medical purposes. It might include a coach if the system is being used for athletic purposes. It might include a manufacturer or distributor of any of the INCs in the MPN, who may wish to download software and parameters into the system to support the INC.
The base station, personal computer, and/or computer over a network connection may also be used to upload data from any of the INCs in the MPN, such as a control unit or data collection INC. This data may be stored, modified, analyzed, displayed, or otherwise used on one of those other stations.
All of the INCs within a single MPN may be assigned a single unique identifier. This identifier may be downloaded, for example, from a base station or personal computer to each of the INCs. All communications between INCs may be tagged with this unique identifier. This will prevent interference between the two MPNs used by two different people. INCs in each system will only listen to messages tagged with that MPN's own identifier.
The unique identifier can also be used to deter theft and other misuse of any INC. Each INC can be programmed to not accept a different unique identifier without explicit authorization from the authorized user, for example on a base station or personal computer. The INCs may also be configured so that the unique identifier they use cannot be extracted to program into a different INC.
All of the INCs in a single MPN may be turned off or on with a single command. For example, a user may press a button or speak a command, which may be received by one of the INCs. The command to turn off may be sent to all of the INCs in the MPN. When any INC receives the turn off command, it may cease any data collection or control functions, stop sending any wireless communications, go into a low-power mode, and otherwise minimize power use. Other than periodically checking for a turn on message, the INC may cease all communications. The user input INC may continue monitoring for a turn on indication from the user. When the turn on command is received, the INC may resume its full capabilities. This feature may be useful to conserve power, as well as to minimize radio frequency interference in environments, such as on a commercial airliner, where wireless communication may cause interference.
Our invention may be controlled by a single module configured as a control unit. This may be an INC that is worn on the person like the other INCs in the MPN. The control unit may have the facility to allow software to be downloaded into it. The control unit may interface with and control the other INCs in the MPN over the wireless network, based on the downloaded software. This allows the functions of the system to be easily modified, simply by downloading different software. If desired, there may be no control unit, and some or all of the INCs may support software download. In addition to software or firmware, the control unit (or any other INCs in the MPN) may also allow the download of data, setup options and other configuration data, current time, or any other information. The control unit, or other INCs, may also allow the uploading of data to a base station or personal computer.
The control unit, if present, may be a separate INC, or it may be combined with another of the INCs, such as a display. In some cases, it may be more efficient to combine the functions of any two of the INCs into a single INC that provides multiple functions. Alternatively, any individual function may be provided by a single INC. The control unit, for example, may be a separate unit, worn on a waistband.
The control unit, if present, preferably has memory and a processor, in addition to its communication device. This memory and processor support downloading of information and software, as well as control of other INCs in the MPN.
For example, one of the INCs may be a display device. Traditionally, displays worn by a person have been in the form of a wrist display, such as a wristwatch. However, users of our invention can choose the type of display that best suits their needs. This may be a display worn on a wristband, carried in the hand or pocket, mounted on a piece of exercise equipment, mounted on a bicycle or in an automobile, or any other suitable method of carrying by the user. In fact, the user may have multiple display INCs, and pick the desired one at any time based on a specific activity.
Traditionally, a wristwatch-type display is worn on the back of the wrist. However, our invention allows the display to be worn or carried in any manner. For example, a runner who does not wish to turn the wrist to view the display may prefer a display that is mounted on the side of the wrist or hand, that can be viewed while maintaining proper running form. The display may be configured so that it can be worn on either the left or right side. It may be configured so that the top of the display is oriented toward the thumb, toward the back of the wrist, or at an angle between the two. Alternatively, it may allow the user to configure the orientation of the display by choosing between one or more options.
Our invention may provide a reusable wearable mount for a display INC or other INCs. This mount may allow the user to easily change one INC for another, to move the INC, or to reorient the INC.
Wrist displays today, such as wristwatches, typically have input controls and audio outputs built-in. These input controls are often tiny and difficult to use. These audio outputs, since they are located far from the user's ear, are often difficult to hear. Our invention does not require that these controls and outputs be integrated into the wrist display. In fact, our invention encourages each function to be placed where it is most usable. For example, the controls may be a set of switches, buttons, or other pressure-sensitive devices worn at convenient points on the body. For example, one sensor can be worn at the tip of each finger in a glove or partial glove. The user can then operate the system by tapping with different fingers or tapping specific sequences to enter different commands to the system. Alternatively, the sensors may be worn at different locations on a waistband, allowing the user to control the system by tapping different locations on the waist. The sensors may be worn on a foot, so that the system can be operated by tapping a foot. The controls may be mounted on a bicycle or piece of exercise equipment. Any other suitable types of controls may be used, including dials, levers, keyboards, voice inputs, touch pads and any suitable combination of multiple types of inputs.
Similarly, an audio output may be provided separately from the display and other INCs. For example, headphones or earphones may be used. Alternatively, one or more speakers may be worn inside a hat or headband, providing sound via conduction through the skull. Such embodiments allow the audio feedback to be loud enough to be easily heard by the user, even in poor conditions such as being on a busy street, while keeping the sounds quiet enough to not disturb other nearby people.
The system with an audio output INC may provide an audio output function. For example, music may be stored in a digital form in memory in the control unit or another INC with a storage capability and sent to the audio output INC. An INC may also generate audio feedback related to other functions provided by the system. For example, if the system is being used for athletic monitoring, audio feedback may be used to prompt the user to work out harder or easier, to provide performance information, or to inform the user what workout zone he or she is in.
The system may provide different audio outputs to signify different situations or conditions. For example, different sounds may be generated for different situations. Alternatively, different sound sequences may be generated for different conditions. As yet another embodiment, sound may be sent to different speakers for different conditions. Voice may also be synthesized. Any of these techniques may be combined.
The system may also provide both music and audio feedback. This is an example of one system providing multiple functions. In this case, the music may be paused, muted, or the volume may be lowered while the audio feedback is provided.
Our invention may be used for a wide variety of purposes or combination of purposes. If desired, one MPN may support different purposes at different times, as INCs are added or removed, as different software and data are downloaded, as the user performs different activities, etc.
One of the INCs in the MPN may be a clock. The time may be automatically downloaded to the clock from a base station or personal computer. The clock may support functions such as a stopwatch, an interval timer, a multiple event timer, a split timer, etc. The clock may also support other timing functions in the system, such as measuring speed, cadence, rate of elevation change, heart rate, etc. A clock may also be used to synchronize functions of the MPN.
The MPN may provide communication functions. For example, multiple MPNs may be used to send data from one user to another. This may be done, for example, with the same wireless transmitters and receivers used to communicate between INCs in a single MPN, as long as the users are close enough to each other. Alternatively, a stationary device may coordinate communications between two or more users.
Data sent between two systems may enable two or more users to play a game, for example, by sending commands, moves, results, etc. from one user to another. Data may allow two or more users to engage in an athletic competition, for example, by transmitting performance data between athletes. Personal data may also be sent between users, for example, name, contact information, etc. Users may also exchange recorded music, software, or any other data.
Our invention may be used to support personal communications. INCs may include a wireless telephone INC or a paging INC. INCs may support instant messaging, electronic mail, and other types of text communications. INCs may support voice communications or video communications. INCs may support transmission and receipt of any type of data, including image data, video data, audio data, and text data.
Our invention may be used for entertainment purposes. This may include allowing a user to play a game, to play music or view other media.
The MPN may allow collection of media data. For example, INCs may include a microphone or a video input. INCs may also include memory or another storage device to store media. The media collected, such as audio, video, or still images, may be replayed for the user by one of the INCs. The media may be uploaded to a base station or personal computer.
The MPN collecting media data may also collect other personal data. For example, the system may collect position data, heart rate data, athletic data such as speed, or other data. The media and personal data may be sent using the wireless network to a base station, and into a personal computer. The media data may be interpreted by a media interpretation unit or algorithm, such as a speech recognition system. The interpreted media data may be used to change the personal data collection functions.
A relationship may be defined when the media and personal data are collected. For example, the media data may be associated with the personal data collected at about the same time as the media was collected. That relationship may be noted in the data, and maintained as the data is uploaded to a base station or stored in a personal computer. For example, a voice note or a picture may be tagged as associated with data collected at a specific time during an athletic workout or other session.
An MPN may provide personal organizer functions. For example, the system may provide appointment scheduling, task management, and contact management. The system may also provide a mobile electronic journal. A journal may allow a user to create text or audio entries, and to annotate them with video, still images, audio, or sketches. The entries may be automatically tagged with the time and location. The user may be able to link a journal entry to an element in an application specific database, such as a medical database, a health database, a travel database, a music database, a work database, a school database, or a database related to any other suitable application. The MPN may support uploading the journal entries and related data to a personal computer, and converting them to a standard file format for viewing, editing, or printing on the personal computer. The journal may also include any other functions or features related to a specific application, such as medical features, health features, travel features, music features, work features, school features, or any other suitable application features.
Our invention may support guidance features. The MPN may include INCs such as a global positioning system monitor, an elevation monitor, or a compass. The system may display current location, direction, elevation, speed, or other related information. The system may provide route guidance, using downloaded map data. The system may collect location, direction, elevation, or speed data. The user may be allowed to annotate the collected data with audio, video, image, or other types of information. The system may automatically annotate the collected data with simultaneously collected personal information, such as heart rate data. The collected data and annotations may be uploaded to a personal computer, where they may be displayed. The data may be compared with map data. Data from multiple sessions may be compared. The system may use collected data to recommend a route in a later athletic session, based on a desired distance, elevation profile, or difficulty, and the user may be automatically guided through the recommended route. The system may also simulate a previous route.
Our invention may provide other athletic functions. For example, a workout plan may be created on an athlete's computer or a coach's computer. The plan may have a specific athletic or health goal, and may be used to define individual workout sessions. Individual workout sessions may include multiple sections, each of which may have an individual goal and individual control characteristics, such a parameter to control, a desired range of values for the parameter, data to collect, and duration. The control characteristics for a workout session may be downloaded into an INC of the MPN, and the system may use them to control aspects of the workout. Control may be accomplished by prompting the athlete, by sending a command to a piece of exercise equipment, or other suitable method. The system may use a servo algorithm to control the parameter. Results, such as speed, distance, heart rate, data from a piece of exercise equipment or bicycle, and other performance data, may be collected during the workout. Errors may be detected in the collected data, for example based on recognizing invalid sample values. Replacement data may be substituted for the invalid values, for example by interpolation. Secondary data, such as cadence, stride length, VO2 max, oxygen uptake, maximum heart rate, percent of maximum heart rate, percent of heart rate reserve, energy consumed, power exerted, or lactate threshold may be derived based on the collected personal data and other personal data. The collected data or the derived secondary data may be displayed for the user during a workout, and it may be used to modify a workout. The data may be uploaded to the athlete's computer, coach's computer, or other suitable location, where it may be stored, displayed, compared between sessions, or otherwise analyzed. The collected or uploaded data may be used to modify future workouts. Progress may be measured against the goal of the workout plan. Workout data, and other information, may be maintained in a mobile athletic journal supported by the MPN.
Our invention may provide consumable reminders to an athlete. For example, the athlete may be reminded to drink water or a sports drink or to take a sodium supplement, based on metabolic measurements taken of the athlete, measurements of the amount of consumable carried, the time since the most recent reminder, the amount of the consumable carried by the athlete, or other suitable factors.
One MPN may interface with one or more other MPNs to allow multiple athletes to compete.
The MPN may be configured to provide lap swimming information. By using one or more monitors worn by the swimmer, the MPN may count laps, distinguish between different strokes, calculate the swimmer's speed, estimate total distance, and provide a log of an entire lap-swimming workout.
Our invention may be configured to monitor the form of the athlete, such as an athlete's running, walking, swimming, bicycling, or rowing form, and provide feedback, either during a training session or afterwards. The form feedback may be based on collecting accelerometer data during the training session and comparing it with data representing ideal form.
Our invention may provide physical therapy features. The form feedback described above may be used to provide gait analysis and other types of activity monitoring. The system may also be used to measure range of motion, test muscle strength, measure and record changes in physical capabilities, provide a therapy journal, or provide other suitable functions.
Medical features may also be supported by our invention. The system may monitor metabolic parameters, such as heart rate, blood oxygen, blood pressure, temperature, and blood sugar. The monitored parameters and other data may be used to estimate or predict a medical problem. The system may also control a medical device such as a syringe pump or defibrillator. It may also provide emergency medical communication, provide storage of medical databases, provide a mobile electronic medical journal, or other suitable medical functions. INCs may be worn or carried by a doctor, patient, or nurse, or mounted on equipment such as a wheelchair. In addition, an INC may be implanted or injected into a patient, or ingested by a patient. Our invention may also be configured to support a disabled user. This may include alternate output methods, alternate input devices, and mounting an INC on a wheelchair or other equipment.
Our invention may provide travel-related functions. These may include language translation, currency conversion, time zone conversion, route guidance, local information, guidebook functions, weather information, transit information, local entertainment information, and expense tracking Our invention may provide a mobile travel journal. It may also provide automated or semi-automated wildlife recognition. Our invention may support users who enjoy outdoor activities. Functions for an outdoor user may include providing orientation (e.g., compass directions), determining position, displaying elevation, and providing route guidance. The system may provide weather features, such as environmental temperature, humidity, and barometric pressure.
Our invention may provide identity functions. The system may identify a user to another person or system. It may use a smart card, personal code, biometric information, or another suitable method to identify the user. Based on the identification, the system may provide exchange of money, product discounts, and purchasing features. The identification may also be used to prevent unauthorized use of the MPN or any of its INCs. Other personal security features may be provided. For example, the MPN may provide an audible alert or an alert message to a public safety facility. An INC of the MPN may store emergency contact or emergency medical information, and provide that information when needed. Our invention may also support military functions. These may include communications, global positioning, route guidance, and weather functions.
Our invention may support multiple purposes within a single MPN. For example, one INC may support a function related to athletics, and another INC may support a function related to personal organization. A single INC may be used for multiple purposes. Each user may easily configure his or her own MPN with exactly the INCs that are needed to meet that user's individual needs. This minimizes cost to each user by allowing him or her to acquire just the INCs that are desired. Also, because similar INCs are used to serve multiple purposes across several different types of users, the cost of INCs can be held down. In addition, because many INCs may use some of the same electronic components, such as power sources and radio frequency transceivers, the cost to manufacture INCs can be minimized.
Further features of our invention, its nature and various advantages will become more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
Second user 10 may have a second MPN. For example, second user 10 may be riding a bicycle. INC 11 may be mounted on the handlebars of the bicycle and may include display functions, user input functions, and control unit functions. INC 12 may be an audio output device, mounted on second user 10's helmet. INC 13 may be a sensor mounted on the bicycle to measure its speed. When second user 10 comes into range of first user 1's MPN, there is no interference. Each INC in either MPN is programmed with a network identifier that is common to all INCs in the MPN but unique among different MPNs. Each message sent from one INC in an MPN to another INC in the same MPN may be tagged with the common network identifier or with a unique component identifier of the target INC, so that no unintended INCs process the message. In addition, the network identifier may be stored in secure memory in each INC, so that the INC cannot be used in a different MPN without explicit authorization from the user who programmed the network identifier.
The MPN may interface with a more stationary device, such as base station 15 or personal computer 16. Base station 15 may act as part of the MPN when the MPN is within range. Base station 15 may include a wireless communication device to communicate with one or more of the INCs in the MPN. Alternatively, base station 15 may communicate with one of the INCs using another means, such as a serial cable, USB, a docking station, infrared, or other connection. Personal computer 16 may communicate with base station 15. Alternatively, personal computer 16 may communicate directly with one or more INCs, acting as a base station. Personal computer 16 or base station 15 may download software, data, settings, and other information to one or more INCs. For example, software may be downloaded to control one or more INCs, or to implement one or more features. As unanticipated INCs are added to the MPN, new software modules may be downloaded to control and interface with them, and an application on personal computer 16 may be used to configure settings related to the new INCs. Personal computer 16 and base station 15 may be used to program the common network identifier into each INC in the MPN. Data may be uploaded from one or more INCs to personal computer 16 to be stored, displayed, or analyzed. If desired, personal computer 16 may communicate with another computer 18 over a wide area network 17, such as the Internet. Software, data, settings, and other information may be sent from computer 18 to personal computer 16 for use with the MPN, and data from the MPN may be sent from personal computer 16 to computer 18.
An MPN may be used for one or more purposes. For example, the MPN may support a global turn on or turn off feature, in which all active devices may be disabled or re-enabled with a single command to a single INC. The MPN may provide clock functions 20, such as providing the current time and date, supporting multiple time zones, providing stopwatch features, and synchronizing other features of the MPN. The MPN may provide communication functions 25, such as communicating with another MPN to support games, competitions, and other types of data transfers, telephone features, paging features, instant messaging, and electronic mail. The MPN may provide entertainment functions 30, such as playing music, recording audio and video media, and games. The MPN may provide personal organization functions 35, such as scheduling appointments, managing contacts, tracking tasks, and maintaining a mobile electronic journal. The MPN may support guidance functions 40, such as showing current position, speed, and elevation, providing route guidance, collecting and annotating position and speed data, and recommending an athletic training route. The MPN may support athletic functions 45, such as supporting a workout plan, supporting workout definition, controlling a workout, communicating with exercise equipment, collecting athletic data, detecting and correcting errors in collected data, estimating secondary data based on collected data, providing competition between users of multiple MPNs, logging lap swim workouts, providing form feedback, and providing an athletic training journal.
The MPN may support physical therapy and medical functions 50, such as measuring range of motion, gait analysis, measuring muscle strength, measuring changes in physical therapy, monitoring a metabolic value, detecting a medical problem, controlling a treatment device, providing emergency communication, storing medical databases, providing an electronic medical journal, and supporting INCs that may be injected, ingested, or implanted. The MPN may provide disabled access 55, such as alternate input devices, alternate output devices, and alternate INC mounting means. The MPN may support travel functions 60, such as language translation, currency conversion, time zone conversion, route guidance, local information, guidebook features, wildlife recognition, a mobile electronic travel journal, weather information, local transit and entertainment schedules, and expense tracking. The MPN may support outdoor functions 65, such as compass direction, geographical location, route guidance, elevation reporting, and weather features. The MPN may support identity functions 70, such as identifying a user to another user or another system, providing exchange of money, providing product discounts, and providing product purchasing. The MPN may support personal security functions 75, such as an audible alert, an alert message to a public safety facility, and storage of emergency information. The MPN may support military functions 80, such as communications, geographical position, route guidance, and weather features. The MPN may support combinations of functions, and its functions may vary over time as INCs are added or removed, as different software or data is downloaded, or as the user's needs change.
Each INC also includes one or more other functions 130-137. These other functions may be provided by hardware and/or software incorporated into the INC. The software may be firmware provided with the INC, or it may be downloaded into the INC over communication path 140 or using other means.
Different manufacturers may manufacture INCs. Each manufacturer may be assigned a unique manufacturer identifier, as shown in table 210 of
There may also be defined a set of device types, as shown in table 230 of
For each device type, there may be a standard set of defined capabilities, which may or may not be supported by any specific INC with that device type. For example, as shown in table 240 of
The manufacturer identifier, model identifier, one or more device types, and any supported device capabilities and values may be stored in read-only memory in the INC, and provided over communication path 140 (
As shown in
Identity request message 300 of
Component identity message 310 of
Component identity message 310 may also include information about the type of INC and its capabilities that may be stored in read-only memory in the INC. For example, the message may include component identifier 313, which may be the identifier for this INC that is unique across all INCs. The message may also include manufacturer identifier 314, model identifier 315, one or more device types 316, and capability list 317.
Net address assignment message 320 of
On processing net address assignment message 320, the INC may respond with network acknowledgement message 330 of
Output data request message 340 of
After processing output data request message 340, the output INC may respond with output acknowledgement message 350 of
Input data request message 360 of
After processing input data request message 360, the input INC may respond with input acknowledgement message 370 of
An INC may also send unsolicited data message 380 of
A control unit, base station, or other INC may periodically send out network poll message 390 of
The message types shown in
Table 400 of
Table 400 is merely illustrative. Other columns may be included. Other data structures may be used. If desired, this information may be stored in multiple data structures.
In step 520, INCs may be changed dynamically. This may include substep 522 in which an INC may be removed. It may also include substep 524 in which a new INC may be added. In step 530, the change may be detected automatically, for example using messages 300 through 390 of the communications protocol of
In step 540, the functions of the MPN may be adjusted to compensate for the change. In substep 542, this may include removing a function from the MPN that may have been provided (or partly provided) by the removed INC. In substep 544, this may also include adding a function to the MPN that may be at least partly supported by the new INC.
Personal computer 610 may include control application 620, which may be configured to control downloading to an MPN and configuring various aspects of MPN functions. Control application 620 may support plug-ins for different types of INCs. For example, plug-in A 622 may support downloading code to support INC A 650. Plug-in A 622 may support loading driver A 626, for example from local storage such as a compact disk or over the Internet, as well as downloading driver A 626. It may also support configuring INC A 650, as well as downloading data to and uploading data from INC A 650.
Personal computer 610 may include communications device 612 for communicating with one of the INCs, such as a control unit 630, using communication path 670. Control unit 630 may include communications device 632 for communicating with personal computer 610. Communications device 612, communications device 632, and communication path 670 may be, for example: a docking station and connector; a Universal Serial Bus (USB) port; infrared transmitters and receivers; serial ports; Ethernet connectors; radio frequency (RF) transceivers; or any other suitable communications means. If desired, communications may be performed wirelessly, and communications device 632 may be the same as wireless communications device 636 used to communicate between control unit 630 and other INCs.
One of the INCs may be a control unit 630. Control unit 630 may include processor 634 and memory 638, as well as communications device 632 for communicating with personal computer 610, and wireless communications device 636 for communicating with other INCs over wireless communication path 675. Memory 638 may hold control software 640 which may include firmware, operating system, boot software, communication software, and the like. Memory 638 may also hold downloaded driver A 626 for controlling INC A 650.
MPN 600 may also include INC A 650. This component may include wireless communications device 652 for communicating with control unit 630 and other INCs over wireless communication path 675. INC A 650 may also include device hardware and firmware 654 for performing one or more primary functions of the INC.
In operation, a user may run control application 620 on personal computer 610. The user may load and run plug-in A 622 to configure MPN 600 to function with INC 650. The user may load driver A 626 and download it to control unit 630. Control unit 630 may subsequently use downloaded driver A 626 to control the functions of INC A 650. The user may also use plug-in A 622 to configure aspects of INC A 650, to download data to the INC, to upload data that may have been collected by the INC, or to perform other functions related to INC A 650.
In
Plug-in B 624 may be loaded into control application 620 on personal computer 610, for controlling aspects of INC B 660. Driver B 628 may be loaded into personal computer 610 and downloaded into control unit 630 for subsequently controlling INC B 660.
Although
All steps are optional and may be performed in any suitable order. In step 810, the unanticipated INC may be added to the MPN. The system may detect the INC using an identity request message 300 (
Flow chart 900 of
In step 920, data may be downloaded over a network, such as the Internet. For example, software or other data may be downloaded from an Internet site into a personal computer. In step 922, data may be downloaded from a computer, such as a personal computer. In step 924, data may be downloaded from a base station. A base station may be a stationary device that communicates with one or more INCs. The base station may be independent, or it may be connected to a personal computer. In step 930, the data may be downloaded into the INC to be controlled. In step 932, the data may be downloaded into a control unit. The control unit may be an INC configured with a processor and memory to control aspects of other INCs in the MPN. The control unit may send information or commands to the INC in step 934. In step 940, the downloaded data may be used to modify one or more functions of the INC.
Software and other data may also be downloaded, for example into a control unit, to coordinate the functions of multiple INCs.
Memory 1120 may be used to hold a common network identifier to be used within all INCs of a single MPN. It may also be used to hold information about the various INCs that have been configured using base station 1110.
INC 1130 may be a new INC, which has not yet been assigned a network identifier. Alternatively, it may already have been assigned a network identifier, which may be stored in secure memory 1140. Secure memory 1140 may be memory that can only be read or written by INC 1130, and cannot be accessed without a security code.
A user of base station 1110 may indicate that INC 1130 is to be programmed with the base station's network identifier. The user may make this indication by, for example, bringing INC 1130 into proximity of base station 1110, making a physical connection between base station 1110 and INC 1130, pressing a button on base station 1110, making a menu selection on base station 1110 (for example, if base station 1110 is a personal computer or is connected to a personal computer), or by taking other suitable actions. The user may also be required to enter a personal code, or to invoke other security measures to ensure his or her proper identity. Base station 1110 may then send a message to INC 1130 with the new common network identifier and the proper security code. If INC 1130 is a new INC, it may store the security code and the network identifier in secure memory 1140. If it has previously been programmed with a network identifier, it may compare its stored security code with the security code it just received, and if they match may store the new network identifier.
If desired, INC 1130 may also incorporate an algorithm to prevent a large number of consecutive attempts at changing the network identifier. For example, if INC 1130 receives more than three unsuccessful attempts to change the network identifier within a ten-minute period, it may lock out any further attempts for the next thirty minutes.
Using this configuration a user may assign any new INC into his or her MPN. A user may also move an INC from one MPN to another, but only with the authorization of the original owner of the INC.
These screens are purely illustrative and may be configured and designed in any suitable manner.
In step 1420, any messages sent from a first INC in the MPN to a second INC in the same MPN may contain the network identifier stored within the first INC. The second INC, on receiving the message, may compare the network identifier within the message to the network identifier stored in the secure memory in the second INC. If the two identifiers are different, the message may be ignored. If the two identifiers are the same, the second INC may assume that the message originated from an INC within the same MPN, and may process the message if appropriate.
In step 1430, an INC may be moved from one MPN to another. This may involve changing the network identifier stored in the INC to a new value. To do this may require explicit authorization from a user, in substep 1432. It may also require the entry of a password or code or another security measure to ensure that the user is authorized to make the change, in substep 1434.
Control unit 1510, and other INCs, may communicate over communication path 1545 with base station 1540. As shown, communications path 1545 may be a wireless communications path. Alternatively, base station 1540 may communication with one or more INCs using any suitable wired path. Base station 1540 may include communications device 1542 for communicating with control unit 1510 and other INCs, and a second communications device 1544 for communicating over communication path 1555 with personal computer 1550. If desired, communications device 1542 and communications device 1544 may be the same device. Communications device 1544 may communicate with communications device 1556 on personal computer 1550 using any suitable physical and logical protocol. This may include a serial port, USB, infrared, radio frequency, a docking station, or other means.
In addition to communications device 1556, personal computer 1550 may have display 1552, keyboard 1553, mouse, printer 1554, and modem 1551. Modem 1551 may be any suitable type of connection to a wide area network, and may include a telephone modem, a digital subscriber line modem, a cable modem, an Ethernet hub, and Ethernet router, or other suitable equipment. Personal computer 1550 may connect using path 1565 to wide area communications network 1560, which may be the Internet. Personal computer 1550 may be configured to send or receive information from another computer using wide area network 1560.
In step 1630, the information may be stored, for example by the base station, the personal computer, or by another computer accessed over the communications network. The information may be displayed for a user. The information may be analyzed, in step 1632. In step 1640, the uploaded information may be used, at least in part, to create information to download. This derived information may be downloaded to the same INC that originated the uploaded data, to the control unit, or to another INC in the MPN. Refer to the description of
In step 1830, data may be sent from the control unit to another INC within the MPN. For example, any of the data sent to the control unit in steps 1820, 1822, 1824, or 1826 may be sent to another INC. The control unit may also send information to another INC that is derived from downloaded data, from data collected from other INCs, or other suitable data.
In step 1832, the control unit may control a function of another INC. The control unit may accomplish this by sending one or more messages to the other INC, and possibly by receiving messages in response. The control may be based on downloaded software, downloaded data, downloaded parameters, time, or any derived data.
In step 1834, the control unit may collect data from another INC. The control unit may request the data by sending a message to the other INC. Alternatively, the other INC may send the data unsolicited. The data may be a single item, or it may consist of several samples collected over a period of time. The control unit may process the data, combine data samples, combine data from multiple INCs, or otherwise modify the collected data. In step 1850, data may be uploaded from the control unit, for example to a base station or personal computer. This may included collected data, derived data, or data generated by the control unit.
In step 1860, functions of the control unit may be integrated with other functions. For example, the control unit may also have a display or a user input device. The control unit may also include clock functions, in step 1840, and it may track time to coordinate functions of the MPN, to schedule actions, and to tag collected data. The control unit may treat the other integrated functions as though they were in another INC, without the need to send and receive wireless messages to communicate with them.
In step 1870, the control unit may support multiple other INCs with multiple functions. Some may be input INCs, some may be output INCs, and some may be a combination. Some INCs may be wholly contained without external input or output, such as a storage INC or a data processing INC. The control unit may maintain a table of active INCs, and communicate with the other INCs as required. The control unit may automatically detect when an INC is added to the MPN or removed from the MPN. When an INC is added to the MPN, the control unit may ignore it until it receives downloaded software or data related to the new INC. Alternatively, it may automatically make use of the capabilities of the new INC. When a INC is removed from the MPN, the control unit may wait for a period of time to make sure that communications with the INC were not temporarily lost. The control unit may continue functioning with reduced functions. In addition or alternatively it may generate an alert to the user.
If desired, an MPN need not include a control unit. Some or all of the functions of a control unit may be incorporated into one or more of the other INCs. If desired, each INC may provide its own control. If desired, software, data, configuration settings, and other information may be downloaded directly into some or all of the INCs by a base station or personal computer prior to mobile use.
In step 1920, the INC may be mounted on personal equipment that may be used by the user. For example, in substep 1922, the INC may be mounted on a bicycle, a car, a piece of exercise equipment, or other suitable personal equipment. The INC may provide an input or output function associated with the personal equipment.
In step 1930, the MPN may also include a relatively stationary INC, such as a base station or personal computer. The base station or personal computer may function as part of the MPN while the user is in proximity to the device. The communications connection with the stationary device may be the same wireless network used to communicate between the INCs, or it may be another type of connection. The other type of communication may be a docking station or other fixed method, USB or other wired method, or infrared or other wireless method. The stationary device may only support communications with one of the mobile INCs, such as a control unit, or it may support communications with several or substantially all of the INCs.
The options shown in
An INC may function as a display INC. A display INC may be worn or carried by the user or mounted on a piece of personal equipment. A display INC may be combined with other functions, such as user controls, audio output, or a control unit, or the INC may function solely as a display INC. A single display INC may be used to display different types of information at different times, depending on the other INCs in the MPN. The display INC may not need to be changed to provide new types of information display. Rather this may be accomplished by adding a new INC with a new function, downloading new software into the display INC or a control unit, or otherwise modifying other parts of the MPN. In addition, the user may switch to a different style of display INC without changing any other part of the MPN, and maintain all preexisting MPN settings and functions.
The display INC may include a wireless communications device for communicating with other INCs in the MPN. For example, the display INC may receive display commands and data from one of the other INCs, such as a control unit. The display INC may incorporate any appropriate display technology, such as liquid crystal displays (LCDs), light emitting diodes (LEDs), etc. It may also include means for mounting the INC to the user's body. If desired, a display INC may accept different types of input for display, such as text, bit-map or other graphics, video data, instructions to turn on or off specific visual indicators, instructions to turn on or off various display modes, or other suitable display items and instructions.
In a mounting similar to a wristwatch, a display INC 2215 may be mounted on the back of a wrist 2210, using wristband 2220, as shown in
A display may be provided in which the user may configure the position and/or orientation. For example, a user may wish to switch the display between the left wrist/hand and the right wrist/hand. A user may also be allowed to change the orientation of the display. For example, if the display is implemented using a dot-matrix liquid crystal display (LCD), the software within the MPN may support multiple orientations. A display may also be provided with multiple mounts—e.g., wristbands, partial gloves, and the like.
In step 2480, the display may be oriented in a direction desirable to the user. For example, in substep 2482, the display may be oriented toward the fingertips. In substep 2484, the display may be oriented toward the back of the hand or wrist. In substep 2486, the display may be oriented at an angle between those two options. In step 2490, the orientation of the display may be configurable by a user, allowing the user to select from one or more orientation options.
All steps are optional and may be performed in any suitable order. In step 2510, a reusable mount may be provided that may be worn on the user's body. In step 2515, the mount may be provided as part of an article of clothing, such as a glove, partial glove, wristband, waistband, shirt, or any other suitable article of clothing. In step 2520, the mount may use a hook and loop type of fastener. If desired, any other suitable type of fastener may be used on the article of clothing. In step 2525, the mount may be made directly to the user's skin. For example, a non-toxic adhesive may be used on the back of the INC to be mounted.
In step 2530, a plurality of mounts may be provided. For example, in substep 2532, mounts may be manufactured in different styles or colors. In substep 2534, mounts may be manufactured to be worn on different parts of the body. A user may choose one of the mounts based on style, whim, convenience, function, or for any other reason.
In step 2540, the mount may be used with an INC. The user may temporarily attach the INC to the mount. If desired, the mount may also be configured to allow devices that are not INCs to be attached. In step 2545, the INC attached to the mount may be a display INC. The display INC may be used to display current time and other information that may be provided by the MPN. In step 2550, the user may be allowed to reposition the INC on the mount. For example, the user may be allowed to change the placement and orientation of a display INC to make it more convenient to read the displayed information. In step 2560, the user may be allowed to mount various INCs onto a single mount. The INCs may be manufactured with different shapes, materials, colors, styles, functions, or otherwise may be of different value to a user at different times.
An INC may function as an audio output INC. An audio output INC may be worn or carried by the user or mounted on a piece of personal equipment. The audio output INC may be combined with other functions, such as user controls, display, or a control unit, or the INC may function solely as an audio output INC. A single audio output INC may be used to output different types of information at different times, depending on the other INCs in the MPN. The audio output INC may not need to be changed to provide new types of information output. Rather this may be accomplished by adding a new INC with a new function, downloading new software into the audio output INC or a control unit, or otherwise modifying other parts of the MPN. In addition, the user may switch to a different style of audio output INC without changing any other part of the MPN, and maintain all preexisting MPN functions.
The audio output INC may include a wireless communications device for communicating with other INCs in the MPN. For example, the audio output INC may receive digital audio data from one of the other INCs, such as a control unit. The audio output INC may include a digital-to-analog converter (DAC) for converting the digital audio data to an analog audio signal. Alternatively, the audio output INC may receive an analog audio signal from another INC. It may include one or more amplifiers and one or more speakers. It may also include means for mounting the INC to the user's body. If desired, the audio output INC may also include more advanced audio processing capabilities, including speech synthesis, recognition of various audio file formats, decryption of secure data formats, the ability to generate any of a predefined set of tones or audio segments, or other suitable circuits and algorithms.
In step 2920, the audio output INC may be configured to be worn. For example, in substep 2922, it may be configured as a headset. In substep 2924, it may be configured as one or more independent earphones, for example to be inserted inside an ear. In substep 2926, it may be configured to be worn with a hat. In substep 2928, it may be configured to be worn with a headband. In step 2930, the audio output INC may include one or more speakers. For example, it may be configured to provide stereo sound. Alternatively, multiple audio output INCs may be included as separate INCs in a single MPN, and may be controlled independently.
In step 2932, audio output INC may provide music. Music may be provided in stereo. In step 2934, synthesized voice may be provided. The synthesized voice may be provided to the audio output INC as digital or analog audio. Alternatively, the voice may be provided to the INC in another form, such as text or phonemes, and the audio output INC may create the synthesized voice. In step 2936, tones may be output. The tones may be provided to the audio output INC as digital or analog audio. Alternatively, the tones may be provided to the INC in another form, such as waveform descriptions or indexes into a table of predefined audio segments, and the audio output INC may create the tones.
In step 2940, the audio output INC may be used by the MPN to provide audio cues to the user. The audio cues may be for any purpose appropriate to the functions provided by the MPN and its other INCs. For example, cues may be provided to an athlete with performance information 2941, workout zone information 2942, workout prompt 2943, or change intensity prompt 2944. Route prompt 2945 or direction alert 2947 may be provided by an MPN that provides route guidance. Medical alert 2946 may be provided by an MPN that monitors medical conditions. Communication alert (e.g., notification of an incoming telephone call or message) 2948 and voice communication 2949 may be provided by an MPN that provides communication services.
In step 2950, sound may be used to indicate different conditions or different audio cues. For example, in substep 2952, different sounds (e.g., different tones) may be used to indicate different conditions. In substep 2954, different sound sequences may be used to indicate different conditions. In substep 2956, sound may be sent to different speakers or audio output INCs to indicate different conditions.
In step 2960, the audio output INC may be used for multiple purposes simultaneously. For example, in a system that provides both music and audible athletic workout feedback, both may be sent to the same audio output INC or INCs. When an audio cue, such as workout feedback, is output, the music may be muted in substep 2962 or the volume of the music may be lowered in substep 2964. Alternatively, the music may be paused in substep 2966 while the audio cue is presented. The volume changing or pausing of the music may be controlled, for example, by a control unit. For example, the control unit may send both music and audio cues to the audio output INC, and may send commands to the audio output INC to control the volume of both. To pause the music, which may be stored in digital form in memory in the control unit, the control unit may temporarily stop reading music data from its memory while the audio cue is presented, and then resume reading the music data from where it was left off. If desired, the pausing, muting, or volume reduction of the music itself may constitute the audio cue, with no additional sound generated. For example, the system may pause the music once for two seconds as one type of cue, and pause the music three times for one half second each time as a second type of cue.
In step 2970, an audio output INC may be provided separately from a display INC. This may be an advantage over many existing systems in which these two functions are combined into a single unit worn on the wrist. In these prior art devices, either the sound volume is so loud that it disturbs other nearby people, or it is too soft to be heard by the user at all times. In this invention, the audio output INC can be provided close to the ear, and the volume can be kept low while still allowing the user to hear the audio even in poor environmental conditions. If desired, the MPN may include the ability for a user to control the volume of audio output. The system may also allow a user to independently control the volume of different types of audio output. For example, the volume of the music may be controlled separately from the volume of the audio cues, and both of those may be controlled separately from the volume of voice communications.
In substep 2975, cues may be sent to either the audio output INC as audio cues, or to the display INC as visual cues, or both. The user may be allowed to configure where different types of cues are sent.
An INC may function as a user input INC. A user input INC may be worn or carried by the user or mounted on a piece of personal equipment. The user input INC may be combined with other functions, such as a display or control unit, or the INC may function solely as a user input INC. A single user input INC may be used to input different types of information at different times, depending on the other INCs in the MPN. The user input INC may not need to be changed to provide new types of information input. Rather this may be accomplished by adding a new INC with a new function, downloading new software into the user input INC or a control unit, or otherwise modifying other parts of the MPN. In addition, the user may switch to a different style of user input INC without changing any other part of the MPN, and maintain all preexisting MPN functions. An MPN may include multiple user input INCs, which may be of similar types or of different types.
The user input INC may include a wireless communications device for communicating with other INCs in the MPN. For example, the user input INC may send digital commands or data to one of the other INCs, such as a control unit. The user input INC may include an analog-to-digital converter (ADC) for converting analog inputs to digital data. It may also include means for mounting the INC to the user's body. If desired, the user input INC may also include more advanced input processing capabilities, including voice recognition, tensile, audible, or visual feedback of input commands, anticipation of likely commands, grouping and combining of similar inputs, or other suitable circuits and algorithms.
In step 3020, any suitable type of user input INC may be used. Preferably, the INC is one that may be used in a mobile environment. For example, a computer keyboard and mouse may not be appropriate except as attached to a personal computer or base station that may be used at times with the MPN. Appropriate types of input INC may include a pressure sensor or button 3021, multiple pressure sensors or buttons 3022, a touch pad 3023, a stylus 3024 used for example with a touch pad, a portable keyboard 3025, and a microphone 3026. Microphone 3026 may be used to capture audio data, or it may include speech recognition circuitry. If desired, an MPN may include multiple user input INCs. For example, one system may include several buttons, a microphone with speech recognition, and a touch pad with a stylus.
In step 3030, the user input INC may be configured to be worn or carried. For example, a pressure sensor may be attached to a fingertip 3032, hand 3031, foot 3035, or waist 3034. A touch pad or microphone may be worn at the waist 3034. A microphone may be worn on the wrist 3033 or other part of the arm, or may be configured as part of a headset. If desired, the user input INC may be designed to be mounted on an item of clothing in step 3040, such as glove 3041, partial glove 3042, wristband 3043, waistband 3044, or footband 3045, shoe, or sock. The user input INC may also be mounted on an item of personal equipment in step 3050, such as on a car 3051, bicycle 3052, or exercise equipment 3053.
In step 3060, if user input INC includes one or more pressure sensors or buttons, it may be operated by tapping. For example, the user may mount a pressure sensor on one or more fingertips, and they may be operated by tapping the fingertip against the palm of the hand, the thumb, other part of the body, or another surface. The user may mount a pressure sensor on the palm of the hand and operate it by tapping it with a fingertip, with the other hand, hitting another part of the body, or striking another surface. The user may mount a pressure sensor on a waistband and operate it by tapping it. The user may mount a pressure sensor on the foot and operate it by tapping an object with the toe or by pushing off the wall while swimming laps in a swimming pool. In substep 3062, the user may tap different sensors for different commands. For example, an athlete may tap with the sensor on one finger to start and stop a stopwatch function, and tap with the sensor on a different finger to capture a single lap split time. In substep 3064, the user may tap different sequences to indicate different commands. For example, the user may tap once, twice in quick succession, or other suitable sequences. In substep 3066, the user may tap a specific combination of sensors simultaneously to input a specific command.
An MPN may be used for many purposes. A single MPN may be used for a single purpose, or it may be used for multiple purposes. The uses of the MPN may change over time, as the user adds and removes INCs, downloads or removes software, changes configuration parameters, or just changes how he or she interacts with the system. A single INC may have a single purpose, or it may be used for multiple purposes. Some types of INCs, such as control units INCs, display INCs, audio output INCs, and user input INCs, may be general purpose.
Step 3205, providing time-related functions, is shown in more detail in
In step 3330, the INC may provide a clock function. This may include displaying the current day and time on a display INC. The INC may include a time zone function in step 3331. This may include displaying the current time in multiple time zones, or converting a time from one time zone to another. In step 3332, the INC may provide a stopwatch function. This may include allowing the user to time individual events. It may include step 3334 of providing a split timer function, in which the user is allowed to time individual portions of an event. It may also include step 3335 in which the user is allowed to time multiple events. In step 3333, the system may provide an interval timer function, allowing the user to mark one or more recurring intervals of specific durations.
In step 3340, the system may store collected time information. This may include collected stopwatch, split, and event times. This collected data may be tagged with the date and time on which it was stored. The user may also be allowed to input descriptive data related to the collected time data. The stored data may also include time zone settings, intervals settings, or other settings. In step 3342, the collected time information may be uploaded, for example to a base station or personal computer.
In step 3350, the clock functions may be used to synchronize other MPN functions. For example, a control unit may collect data from a particular INC on a regular interval, or update a display once per second. The control unit may be allowed to read the current time from the clock. The clock may also be configured to provide an unsolicited interrupt to the control unit or other INC at a regular interval. In step 3352, data collected from other INCs may be tagged with the current time retrieved from the clock.
More details of step 3230 (
In step 3620, wireless telephone communications may be provided, if one of the INCs includes a wireless telephone. The audio output INC for the MPN may output the incoming audio from a telephone call, and a microphone used as a user input INC for the MPN may be used to provide the outgoing audio for the telephone call. This allows the telephone INC itself to be smaller and less costly, since it does not require a built-in speaker or microphone.
In step 3625, paging services may be provided. For example, one of the INCs may include a paging receiver. Text pages may be shown on the display INC. Audio alerts and voice pages may be sent to the audio output INC. Two-way paging may be provided if desired. An instant messaging function may be provided in step 3630, with one INC receiving text messages for display on the display INC, and another INC allowing text messages to be composed and sent to another person elsewhere. Electronic mail messages may also be composed and received in a similar manner in step 3635.
Different types of communication may be provided as appropriate. For example, voice communications may be provided in step 3640. Text communication may be provided in step 3642. Video communication may be provided in step 3644. Other formats of communication may also be supported if desired.
In step 3650, data may be transmitted by a communications device in one of the INCs in the MPN. This may include substep 3652 transmitting image data, substep 3654 transmitting audio data, substep 3656 transmitting video data, and substep 3658 transmitting text data. The data to be transmitted may be provided by the user with a user input INC, may be stored in memory within the MPN, and may be transmitted among INCs in the MPN prior to sending.
In step 3660, data may be received by a communications device in one of the INCs in the MPN. This may include substep 3662 receiving image data, substep 3664 receiving audio data, substep 3666 receiving video data, and substep 3668 receiving text data. The data received may be transmitted among INCs in the MPN and stored in memory within the MPN, prior to its being provided to the user on one or more of the INCs, such as a display INC or audio output INC. If desired, a communications alert may be provided to the user on the display or audio output INC to let the user know that a message has been received.
If desired, input and output INCs in the MPN may be shared between a communications function and another function of the MPN. For example, music may be paused or muted while voice communications or communications alerts are being provided to the audio output INC.
The data may include personal data in step 3720. For example, if the two MPNs are configured to provide personal organization features, the data sent from one to the other may include contact information, such as a name, phone number, electronic mail address, or other suitable information.
In step 3730, the data sent between MPNs may include game data. This may allow the users to play a game that requires two or more players, if both users have the same game software installed.
In step 3740, the data may allow two users to compete athletically. For example, the two users may each be on a stationary bicycle, and performance data may be exchanged between them. The two MPNs may determine who wins the competition based on data gathered from the two stationary bicycles or other sensors.
In step 3750, one user may send software to another user. This may include, for example, software that enables an MPN to perform a specific feature or provide a specific function. In step 3760, one user may be allowed to send a digital music file, or other recorded media, to another.
Any other suitable type of data may be exchanged between MPNs. If desired, data may be exchanged between more than two MPNs simultaneously, for example allowing a game with more than two players.
Another example of two users with communicating MPNs is shown in
In step 4020, the system may allow audio to be recorded. For example, one of the INCs may include a microphone. The audio may be digitized and stored into memory in one of the INCs, such as a control unit. The recorded audio may be replayed by the user, using the audio output INC. Similarly, video segments may be captured in step 4022 and still video images may be captured in step 4024 by an INC with a video input. The video segments may be digitized and stored in memory in one of the INCs. If desired, the captured video segments and images may be viewed by the user on the display INC.
If desired, any stored music or any recorded media may be shared with a user of another MPN, as described above in conjunction with
In step 4030, the user may be allowed to play a game. The game may involve only the user of the MPN. Alternatively it may involve a user of another MPN, if one of the INCs in each MPN includes a communication device capable of communicating with the other MPN. For example, the wireless communications device within each of the INCs may be used to transfer game-related information between MPNs if the two users are in close proximity. An INC of the MPN may also be configured to communicate with an external game device.
Music and audio cues may both be provided by a single MPN, as described previously in conjunction with
In step 4150, the personal organizer data stored by the MPN may be synchronized with another system, such as a software application running on a personal computer. Appointments, contacts, tasks, and journal entries created on either system may be copied to the other system. This may allow the user to keep a permanent or backup copy of data created in the mobile system, and may also allow the user to take advantage of the keyboard, mouse, and full-sized monitor on the personal computer to enter significant amounts of information. In step 4160, information may be shared with another MPN, as described above in conjunction with
In step 4260, any journal entries stored in the MPN may be uploaded to a personal computer. This may include the voice, text, and drawing parts of the entries, as well as any linked images and time and location tags. It may also include links to any database elements that may be linked to the journal entries, or it may include the data from the database elements themselves. In step 4265, the uploaded journal may be converted into a standard file format, so that it may be easily viewed or printed with the personal computer. The file format may include HTML, PDF, or any other suitable format. Images and audio segments may also be stored in a common file format. The data may be loaded into a database on the personal computer if desired.
In step 4330, route guidance may be provided to a user. Turning to
Returning to
In step 4350, position information may be correlated with simultaneously collected performance information. This may be useful in an MPN that is also used to support athletic workouts. For example, the route may be an athletic training route or an athletic competition route. The performance information may, for example, be speed in substep 4351, heart rate in substep 4352, cadence, or any other suitable performance data. The personal data may be stored with the position data, and the system may also store links between the two data items. This collected performance data may be displayed during the session. It may also be displayed or printed on a personal computer at a later time. It may be displayed in a table, in a graph, on a map, on an elevation profile, or any other suitable format. In step 4353, performance data may be collected during multiple sessions. In step 4354, the performance data may be compared between sessions. The comparison may be for the entire sessions, or for portions of the sessions following the same route. For example, a table or graph may be used to show the performance differences between two sessions. Summary information, such as averages, may also be provided. Information may be displayed on an INC of the MPN, on a personal computer after being uploaded, to a computer accessed via a wide area network such as the Internet, or at any other suitable location.
The collected position information may be used to recommend a route for a later session in step 4360. For example, the MPN may store position information from one or more sessions, and may construct map data of routes that are available to the user. Prior to or during a later session, the constructed map data may be used to plan a route for the user. The system may also use the collected performance data to plan the route. If desired, the route may be that of an upcoming athletic competition, and the system may be used to collect information about the route, such as elevation profile, distance of individual segments, landmarks, or other information of interest. In substep 4361, a route may be recommended based on a desired workout intensity. For example, the system may use collected heart rate data or an elevation profile to choose a route with the desired difficulty. In substep 4362, a user may specify a desired elevation profile, and the system may choose a route that most closely matches the user's preference. In substep 4363, the system may recommend a route based on a desired distance chosen by the user. If desired, the system may allow the user to specify any other suitable criteria, or combination of criteria, for route selection. In step 4365, the MPN may provide directions or other guidance to the user during a session, based on the selected route. If desired, the guidance may be based on a route chosen ahead of time and downloaded. Alternatively, the directions may be made dynamically, as specific decision points are reached. For example, a prompt to take a specific turn may be shown on the display INC or played through the audio output INC. The system may also make modifications to the recommended route if the user does not follow the prompts. If desired, the chosen route may be based on map and elevation information loaded from a CD-ROM or other memory device or loaded from the Internet or other network, rather than using position information collected by the user.
Position data collected in one session may also be used to simulate the same route in a later session. For example, a user may travel the route of an upcoming competition in one or more sessions and collect position and elevation information. This collected position and elevation information may be used to control exercise equipment in later sessions to simulate the racecourse.
Data collection INC 5320 may have wireless communication device 5322 for sending collected data to control unit 5240 or other INC having storage capabilities. It may also have data collection circuit 5324. Data collection circuit 5324 may collect any athletic data, such as speed, heart rate, power, resistance, location, cadence, or any other suitable type of athletic data. Data collection INC 5320 may be worn by the athlete. If desired, data collection INC 5320 may be mounted on a piece of athletic equipment or a bicycle and may collect data from that equipment.
Output INC 5330 may have wireless communication device 5332 for receiving control commands from control unit 5240 or other suitable INC. It may also have output circuit 5334. Output circuit 5334 may output athletic control data using any appropriate method, such as displaying a prompt to the user, outputting a prompt to the user, controlling resistance, controlling speed, or any other suitable type of athletic control. Output INC 5330 may be worn by the athlete. If desired, output INC 5330 may be mounted on a piece of athletic equipment or a bicycle and may send control commands to that equipment.
In
In step 5740, the workout may be divided into sections. Each section may have its own goal, such as warm up, increasing anaerobic threshold, recovery, increasing endurance, cool down, or any other suitable goal. Each section may be provided its own set of workout parameters. For example, in step 5750, target intensity may be defined for a section. In step 5760, target heart rate, speed, power, cadence, or any other parameter to be controlled may be defined for the section. If desired, multiple parameters to be controlled may be defined. If desired, the desired profile of the parameter or parameters during the section may be specified. If desired, a section may be defined with no parameter to be controlled. For example, the desired heart rate for a section may be 100 beats per minute at the start of the section, and may increase linearly to a value of 130 beats per minute at the end of the section. In step 5770, the duration of each section may be defined. The duration may be measured in units of time, units of distance, or any other suitable units. In step 5780, the controlling parameter for the section may be defined. For example, to control the heart rate, the athlete's speed may be controlled by sending audible prompts, the speed may be controlled by sending commands to a piece of exercise equipment, or the resistance may be controlled by sending commands to a piece of exercise equipment. If desired, multiple controlling parameters may be specified. If desired, limits on the values or rate of change of the controlling parameter may be specified. In step 5790, repetitions of sections may be defined. For example, two sections may be alternated, and the combination may be repeated four times. Any other suitable attributes of a section may also be defined. If desired, the definition of one section may be copied from the definition of another section.
Section A definition 5925 may specify that the section is to have a duration of 15 minutes in duration definition 5926. It may specify that the heart rate is to be controlled in primary parameter definition 5927, and that the heart rate is to follow a linear curve from 100 beats per minute to 125 beats per minute in curve definition 5928. It may specify a secondary parameter of cadence, which is to be kept at a rate of 90 revolutions per minute in secondary parameter specification 5929. It may specify in controlling parameter definition 5930 that the heart rate is to be controlled by user audio prompt. In this definition, section A is to occur once during the workout session.
Section B definition 5945 may specify that the section is to have a duration of 5 minutes in duration definition 5946. It may specify that the heart rate is to be controlled in primary parameter definition 5947, and that the heart rate is to be maintained in a range between 150 beats per minute and 160 beats per minute in curve definition 5948. It may specify a secondary parameter of cadence, which is to be kept at a rate of 90 revolutions per minute in secondary parameter specification 5949. It may specify in controlling parameter definition 5950 that the heart rate is to be controlled using a resistance setting output.
Section C definition 5955 may specify that the section is to have a duration of 1 minute and 30 seconds in duration definition 5956. It may specify that speed is to be controlled in primary parameter definition 5957, and that the speed is to be maintained below 15 miles per hour in curve definition 5958. It may specify a secondary parameter of resistance, which is to be kept at the easy setting in secondary parameter specification 5959. It may specify in controlling parameter definition 5960 that the speed is to be controlled by user audio prompt. In this definition, section B and section C are combined into a single super section, which is to occur twice during the workout session.
Section D definition 5975 may specify that the section is to have a duration of 15 minutes in duration definition 5976. It may specify that the heart rate is to be controlled in primary parameter definition 5977, and that the heart rate is to be maintained at a constant rate of 110 beats per minute in curve definition 5978. It may specify a secondary parameter of cadence, which is to be kept at a rate of 90 revolutions per minute in secondary parameter specification 5979. It may specify in controlling parameter definition 5980 that the heart rate is to be controlled by user audio prompt. In this definition, section D is to occur once during the workout session.
In step 6030, the workout parameters for each section may be defined. This may include substep 6032 in which a performance parameter to be controlled may be specified. This may include, for example, heart rate, cadence, power, or speed. In substep 6034, the desired value, values, or profile of the performance parameter to be controlled may be specified. This may include specifying a constant level, a defined curve, the end points of a linear variation, or two values to maintain the parameter between. If desired, a range above and below the desired curve may be defined. In substep 6036, an output parameter to be used to control the performance parameter may be specified. In substep 6038, one or more secondary performance parameters with corresponding desired values may be specified. In substep 6040, the duration of the section may be specified, for example, in time or distance. After all workout parameters have been defined, they may be downloaded from the coach's computer or athlete's computer into memory in an INC of the MPN, such as a control unit, for use during the workout. If desired, the workout parameters may be transmitted directly from the coach's computer into an INC of the MPN, or they may be transmitted over a wide area network such as the Internet to the athlete's computer, and downloaded from the athlete's computer into an INC of the MPN.
In step 6050, data may be collected during the section of the workout session. That may include heart rate data in substep 6052, speed data in substep 6054, position data in substep 6056, cadence data in substep 6058, power data in substep 6060, data from a sensor mounted on a piece of exercise equipment in substep 6062, data from a sensor mounted on a bicycle in substep 6064, or any other suitable type of input data. Data collected during a workout may be presented to the athlete during the workout, for example on a display INC. If desired, collected data may be uploaded to a base station, the athlete's personal computer or the coach's personal computer, where they may be stored, displayed as a chart or graph, compared with results from previous workouts, or otherwise analyzed. If desired, collected workout results may be used to modify workout parameters of future workout sessions.
In step 6070, a performance parameter may be controlled during the section of the workout session. This may be done by prompting the user in substep 6072. The prompt may be a visual prompt in substep 6074 or an audible prompt in substep 6076. In substep 6078, the prompt may be to change speed, change intensity or level of effort, change route, or any other suitable prompt. In substep 6080, the control may be performed by changing a setting, such as a difficulty, speed, or resistance setting, on an output INC. In substep 6082, the control may be performed by changing a setting on a piece of exercise equipment.
In substep 6084, the control may be performed using a position-integral-derivative (PID) servo algorithm, in which the value of an input parameter, the rate of change of the input parameter, and previous values of the input parameter are used to calculate a new value for the controlling parameter. The system may also include a set of limits on the output value to prevent it from exceeding a minimum value, a maximum value, and/or a maximum rate of change. In substep 6086, the input data used in the algorithm may be data that was collected in step 6050, and the definition of the input parameter and the controlling parameter may be part of the workout parameters that were defined in step 6030. The constants in the servo equation may be standard values, may be entered or downloaded by a user, or may be derived and modified with use.
In substep 6088, one or more additional parameters may be controlled during the workout section, as specified in the workout parameters. For example, a secondary parameter may be maintained between two values in substep 6090, maintained at a constant level, controlled linearly, or controlled in any other suitable fashion.
In addition to directly collecting data to measure a performance parameter, an MPN may use stored information along with collected information to estimate a derived performance parameter. A process for doing so is illustrated in flow chart 6100 of
In step 6140, primary performance data may be collected, for example by an INC of the MPN during an athletic effort. The data may be a single sample, or it may be many samples collected over a period of time. In step 6150, a secondary performance parameter may be estimated using the stored personal data and the collected primary performance data. In substep 6162, maximum heart rate (MHR) may be calculated. MHR is the maximum rate at which the athlete's heart can beat during a maximal effort, and is commonly measured in beats per minute. The MEM value may be entered by the user as personal data. The MHR may be estimated by the system based on the age and gender entered by the user. For example, MHR is commonly estimated as 220-age in years. Alternatively it may be estimated as 214—(age*0.8) for males and 209—(age*0.7) for females. Another method of estimating MHR is 210—(0.5*age)−(0.05*weight in pounds)+(4 if male or 0 if female). The estimate may be modified based on the specific type of activity or other factors. Alternatively, MHR may be estimated based on actual heart rate measurements in a defined athletic effort.
Resting heart rate (RHR) may be entered by the athlete as personal data or it may be measured. RHR is a measure of the rate at which the athlete's heart beats when at complete rest, and is also measured in beats per minute. RHR may be estimated based on actual heart rate measurements taken over a period of time, for example while the athlete is asleep. Regardless of how MHR was entered, measured or estimated, the percent of maximum heart rate may be estimated by dividing actual heart rate (HR) by MHR, in substep 6154. Percent of heart rate reserve may be estimated as (HR-RHR)/(MHR-RHR), in substep 6156.
Another performance parameter of interest to athletes is oxygen uptake (VO2) and maximum oxygen uptake (VO2 max). VO2 is a measure of the amount of oxygen removed from the blood and used by the muscles during an athletic effort. VO2 max is a measure of the maximum amount of oxygen that can be used by the athlete during an effort. Both are commonly measured in units of ml/kg/min. Although the actual measurement of VO2 requires sophisticated equipment, there are several known methods to estimate it. For example, in “Jack Daniels, Conditioning for Distance Running—The Scientific Aspects,” Wiley & Sons, 1978, the following formulas are used:
Percent max=0.8+0.1894393*e(−0.012778*t)+0.2989558*e(−0.1932605*t)
VO2=−4.60+0.182258*v+0.000104*v2
VO2max=VO2/percent max
In the above formulas, t is the time to complete a race-level effort in minutes, and v is the speed during the race in meters per minute. Oxygen uptake may be estimated during an athletic effort in substep 6152, using the above formula or any other suitable method. VO2 max may similarly be estimated in substep 6166. The system may also estimate the speed, heart rate, or other parameter corresponding to the level of effort at which VO2 max is reached. If desired, time and speed data may have been entered by the athlete as personal data, or may be measured by the MPN.
In substep 6158, the system may estimate energy consumed during an athletic effort. Energy consumption may be expressed in calories, and may be estimated based on age, gender, height, and weight, which may be entered as personal data. It may also be estimated based on type of activity, HR, speed, elevation gain, and other factors that may be measured during an athletic effort. Similarly, the power exerted while exercising may be estimated in substep 6160.
Lactate threshold (LT) may be estimated in substep 6164. LT represents the highest level at which exercise may be maintained for an extended period without a build-up of lactate in the blood. It may be measured, for example as a percent of VO2 max or a percent of MHR above which lactic acid begins to accumulate in the blood. It may be estimated, for example, by using the average heart rate for a maximal athletic effort over a half hour. Alternatively, it may be estimated by measuring heart rate during a series of progressively more difficult efforts, and based on the rate of increase of heart rate between the efforts.
In step 6170, the estimated secondary parameter may be used to modify an athletic workout. For example, the intensity of a workout may be expressed as percent of LT, and during the workout the system may measure heart rate, estimate LT, and increase or decrease the speed setting of a piece of exercise equipment to maintain the proper level of effort. In step 6175, the user may be prompted to modify the level of effort based on an estimate of a secondary performance parameter. For example, the intensity of a workout may be expressed as percent of VO2 max, and during the workout the system may measure heart rate, estimate VO2, and prompt the user to speed up or slow down to maintain the proper level of effort. The estimated secondary parameter may also be displayed for the user by the MPN, or it may be uploaded to a base station or personal computer to be stored, displayed, or analyzed.
As described herein, the MPN may be used to collect data, such as heart rate and other athletic data. However, at times the data collection may be unreliable, for example because of interference with the wireless communications between INCs in the MPN. Temporary interference may be common because of nearby electro-mechanical devices, other radio frequency transmitters, poor contact between a metabolic sensor and the skin, and even static electricity between the athlete's body and clothing. One way of handling this is by including memory in the data collection INC, and retransmitting any lost data once the interference is gone. However, this may not be practical, as it may significantly increase the cost of the data collection INC. Also, at times data samples may not be collected successfully by the data collection INC, due to such factors as intermittent connections between the INC and the athlete's body. Therefore, the MPN may include algorithms to recognize invalid data samples and to estimate new values for the invalid samples.
In step 6620, one or more invalid samples may be recognized. The invalid samples may be recognized, for example, by a control unit while data is being collected or by a personal computer after collected data has been uploaded. In substep 6621, invalid samples may be recognized on the basis of missing values. In substep 6622, invalid samples may be recognized on the basis of zero values, i.e., samples with the value of zero. In substep 6623, invalid samples may be recognized on the basis of values outside a defined range, for example, heart rate data lower than the resting heart rate or greater than the maximum heart rate. In substep 6624, invalid samples may be recognized on the basis of a rapid change in values, for examples values that indicate a very significant change in heart rate in a very short period of time. In substep 6625, invalid samples may be recognized on the basis of values inconsistent with other data, for example significantly different from samples collected before and after, or for example heart rate data inconsistent with collected speed and elevation data.
In step 6630, replacement values may be estimated for the invalid samples. Replacement values may be interpolated based on valid samples collected before, after, or both before and after the invalid samples in substep 6631. Replacement values may be interpolated linearly in substep 6632. Replacement values may be interpolated based on the first derivative of valid samples in substep 6633. Replacement values may be interpolated linearly based on the first derivative in substep 6634. Replacement data may be interpolated using a quadratic equation in substep 6636. Replacement data may be interpolated using a polynomial equation in substep 6638, and may match the values and/or derivatives of valid samples at the end points of the interpolation range. The data may also be estimated based on data collected in previous sessions under similar conditions, for example, the rate of change of the data may be made to match the rate of change of data collected in the similar session.
In step 6640, the data samples may be listed, for example on personal computer 6510 (
An MPN may also be used to provide an athlete, such as a runner or walker, with cadence information and stride length information.
In step 7040, a position monitor may be provided as an INC in the MPN. The position monitor may be a GPS monitor in substep 7042. The position monitor may send position data to a control unit or other component with storage capabilities at regular intervals. The position monitor may also be worn by the user. In step 7050, the position monitor may be used to measure the user's speed, which can be calculated as distance traveled divided by time. In step 7060, stride length may be calculated based on the speed and cadence of the user. In substep 7062, the stride length may be calculated as speed divided by cadence. If desired, the units of stride length displayed to the user may be converted to feet, meters, or other appropriate units. If desired, any of speed, cadence, and stride length may be displayed for the user.
A significant impact on athletic performance is the loss of certain valuable consumables by the athlete during a training or competition event. For example, as the user continues at a high level of exertion, levels of water, sodium, carbohydrates, and other nutrients will decrease, and performance will correspondingly decrease. As levels decrease further, performance levels will decrease at an even higher rate, until the athlete is no longer able to continue. However, if the athlete consumes too much of any of these consumables, performance will also suffer, with conditions such as stomach distress and cramping, hyponatremia, and hypernatremia. The MPN can be used to measure the usage or loss of such consumables, and provide the athlete with reminders to take in specific amounts of one or more of them.
In step 7110, metabolic data may be collected from a user such as an athlete. For example, an INC in an MPN may include a sensor to measure a specific metabolic value. In substep 7112, heart rate data may be collected. In substep 7114, skin resistance data may be collected. In substep 7116, body temperature data may be collected. In substep 7118, blood pressure data may be collected. In step 7120, the loss of a consumable may be estimated based on the metabolic data. For example, water may be estimated in substep 7122, carbohydrates in substep 7124, and sodium in substep 7126. A rate of loss of each consumable based on level of effort indicated by heart rate may be used. Skin resistance may be used to measure the amount of sweat, which translates to water and sodium loss. An increasing body temperature or blood pressure may indicate a significant loss of water. Need may also be estimated based on information stored about the athlete, such as weight or gender. In step 7130, time may be measured since the most recent reminder, and the time may be used to refine the estimate of lost consumables. In step 7140, the MPN may include an INC to measure the amount of consumable, such as energy drink or water, carried by the user. The measured amount may be reported to the user. Additionally, the measured amount may be used to calculate the amount previously consumed by the user, and may be used to refine the estimate of needed consumables. In step 7150, the user may be reminded to consume a consumable based on the estimated loss. In substep 7152, the reminder may be presented when the loss or usage reaches a defined amount. In substep 7154, the user may be told a specific amount of the consumable to consume. In substep 7156, the user may be given an audible reminder. In substep 7158, the user may be given a visual reminder.
An MPN may be used by a swimmer to provide swimming-related information, such as lap counts. This is illustrated in flow chart 7400 of
In step 7440, the duration of the two or more characteristics may be measured, and this measurement may be used to provide a lap time in step 7445. If desired, the measured lap time may be compared with a typical lap time in step 7450, and validated that it falls within a normal range. For example, if two consecutive measured lap times are much less than the typical lap time, the user may have paused in the middle of a lap. Similarly, the turn time may be measured in step 7460, and may be validated in step 7465. Typical lap times and typical turn times may be standard values, they may be entered by the swimmer, they may be measured during a calibration swim, or they may be entered in any other suitable way. In a calibration swim, for example, the swimmer may swim a small number of laps of each stroke, while the system measures the characteristics of the data collected by the monitor and measures the typical lap times. Based on the data collected during a swim workout, the system may construct a model of the entire workout, including each swim, with type of stroke, speed, and distance for each swim, duration of rest periods, and other data. The data from the model may be stored, displayed, graphed, analyzed, or processed in any other suitable manner.
An MPN may be used to provide form or gait feedback to an athlete or other user. Through the use of one or more accelerometers mounted on a part of the body that is moved during a particular activity, the system may compare the measured movements with ideal movements, and provide feedback to the user. An example of such a process is shown in flow chart 7800 of
In step 7820, the user may be allowed to wear the accelerometer or accelerometers during a training activity. For example, one or more accelerometers may be worn while running in substep 7821, walking in substep 7822, swimming in substep 7823, bicycling in substep 7824, rowing, during a physical therapy activity in substep 7825, or during any other suitable activity. In step 7830, characteristics of desired movements of the monitored part or parts of the body may be stored. For example, the characteristics may have been captured by an expert in the activity wearing one or more accelerometers in the same location or locations. Alternatively, the characteristics may have been generated by monitoring multiple users and averaging the results, or by calculating optimum characteristics theoretically. If desired, the characteristics of desired motions may be stored in a personal computer, or they may be downloaded into memory in an INC of the MPN. If desired, a coach or physical therapist may wear the accelerometer or accelerometers and demonstrate the motion, while the MPN captures the characteristics of the coach's motions or therapist's motions.
In step 7835, data from the accelerometer or accelerometers may be collected during the training activity. If desired, the collected accelerometer data may be uploaded from the MPN into a personal computer. In step 7840, the system may compare the collected accelerometer data with the stored characteristics of desired motion. This comparison may be performed in the MPN, for example using a control unit, or it may be performed using a personal computer to which the data was uploaded. In step 7845, the comparison may be used to evaluate the user's form during the training activity, for example to determine incorrect aspects of the user's form. For example, while running, incorrect form may include over-striding, under-striding, lifting the feet too high, crossing the arms excessively in front of the body, or any other suitable type of incorrect form. Feedback on incorrect form may be provided to the user during the activity in step 7850. This may be audible feedback, for example using an audio output INC, and may be synthesized voice. The feedback may be visual feedback, for example using a display INC. In step 7855, feedback may be provided to the user after the training activity has been completed, for example using a personal computer. The raw data may be collected and uploaded to the personal computer, which may provide the comparison to create the feedback. Alternatively, the comparison may be performed in an INC of the MPN, and the results of the comparison may be collected and uploaded to the personal computer. The feedback may be in the form of a chart, table, or graph, it may be displayed or printed, or it may be presented in any other suitable form. Form feedback data may be combined with other suitable data when displayed, such as time, speed, or percent grade uphill or downhill. In step 7860, the collected data or the form feedback may be transmitted to a coach or physical therapist, for example over a network such as the Internet, and the coach or physical therapist may view the data or feedback.
Screen 8100 of
An MPN may be used to provide an athletic training journal.
As described in step 3255 of flow chart 3200 of
As described in step 3215 of flow chart 3200 of
The system may take an action to address the estimated medical problem in step 8530. For example, a prompt may be provided to the user, visually or audibly, in step 8540. That may include a prompt to drink in substep 8541, a prompt to consume sodium in substep 8542, a prompt to slow down in substep 8543, a prompt to cease activity in substep 8544, a prompt to eat in substep 8545, a prompt to take insulin in substep 8546, a prompt to take medication in substep 8547, a prompt to seek emergency medical attention in substep 8548, or any other suitable prompt. If desired, the system may send an alert message in step 8550. For example, a radio frequency message may be sent to emergency medical personnel. In step 8560, an audible alert may be sounded. If desired, the action may include control of a medical treatment device, such as a portable syringe pump, an implanted defibrillator, or other suitable device.
As described in step 3265 of
Step 8940 (
Step 8932 (
In step 9430, exchange of money may be provided based on the confirmed identity. In step 9440, the identity may be proven to another person. In step 9445, the identity may be proven to another system, such as another MPN. In step 9450, a product discount may be provided based on the confirmed identity. In step 9455, product purchasing may be provided based on the confirmed identity. If desired, the system may store purchasing information, such as a credit card number, a bank account number, a bank balance, or any other suitable information. If desired, the personal identification may also be used to prevent unauthorized use of the MPN or any of its INCs. The personal identification may also be used to provide secure access to restricted areas, features, and the like.
As described in step 3270 of
Another example of an MPN 9700 that may be used for multiple purposes is shown in
The ability to easily turn off all INCs in an MPN may be useful to conserve power. It may also be useful to terminate radio frequency transmission in an environment in which they may cause unwanted interference, such as on a commercial airliner. One of the commands received by the user input INC may be a turn on command, or a turn off command. These may be global commands applying to all INCs in the MPN. A process for handling a global turn on command and a global turn off command is shown in
In step 10112, the INC may send a turn off command to all of the INCs in the MPN. This may be a single message that is broadcast to all INCs with the same network identifier in substep 10114. Alternatively, individual messages may be sent addressed to each INC in substep 10116. In step 10118, the INC may wait for confirmation from each other INC. If confirmation is not received, the INC may resend the turn off command, display an error message, or perform another suitable action. If desired, the wait for confirmation step may be optional. Once all confirmations have been received, the INC may enter a low power mode, in step 10120. For example, if a processor with a sleep mode is used in the INC, it may enter the sleep mode, and it may configure an interrupt to be generated when a user input is received.
While in the low power turned off state, the INC may check for user input, in step 10122. For example, an interrupt may be generated when a user input is received. If no user input is received, the INC may remain in the turned off state. If user input is received, the INC may check to see if it is a turn on command, in step 10124. If not, the user input may be ignored and the INC may remain in the turned off state. If the turn on command is confirmed, the INC may resume its high power mode, in step 10126. Turn on messages may be sent to all components in step 10128, either as a single broadcast message or as individually addressed messages. The INC may resynchronize with the other components in step 10130. This may include waiting for acknowledgement from the turn on message, resending the turn on message if required, or synchronizing functions that may have been in progress prior to the turn off command. In step 10132, normal functioning may resume.
Flow chart 10150 of
While in low power mode, the INC may check for incoming messages, in step 10166. If no message is received, it may remain in low power mode. When a message is received, the INC may check to see if it is a turn on message, in step 10168. If the message is not a turn on message, the INC may ignore it and remain in the low power off state. When the turn on message is received, the INC may resume its high power mode in step 10170. An optional acknowledgement message may be sent in step 10172. Optionally, the INC may resynchronize with other INCs in the MPN, in step 10174. This may include synchronizing any functions that were in progress when the power off message was received. In step 10176, the INC may resume normal functions, and return to its normal “on” state.
Although various embodiments have been described herein in terms of an MPN, many of them are possible without all of the features and aspects of an MPN. For example, components may be designed specifically for a single purpose, and may not support dynamic configuration of a wireless network.
Although our present invention has been described in considerable detail with reference to certain preferred embodiments thereof, other embodiments are possible. This includes uses, functions, components, and combinations thereof that may not be fully described. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred embodiments contained herein.
This application is a continuation of U.S. application Ser. No. 13/794,011, filed Mar. 11, 2013, which is a continuation of U.S. application Ser. No. 13/789,266, filed Mar. 7, 2013, now U.S. Pat. No. 8,652,009, which is a continuation of U.S. application Ser. No. 12/617,871, filed Nov. 13, 2009, now U.S. Pat. No. 8,795,137, which is a divisional of U.S. application Ser. No. 10/645,713, filed Aug. 20, 2003, now U.S. Pat. No. 7,670,263, which is a continuation of International App. No. PCT/US02/04947, filed Feb. 20, 2002, which claims the benefit of U.S. Provisional App. No. 60/270,400, filed Feb. 20, 2001. The contents of each of these applications are expressly incorporated herein by reference thereto in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3742937 | Manuel et al. | Jul 1973 | A |
| 3802698 | Burian et al. | Apr 1974 | A |
| 3838684 | Manuel et al. | Oct 1974 | A |
| 3978849 | Geneen | Sep 1976 | A |
| 4027663 | Fischler et al. | Jun 1977 | A |
| 4038976 | Hardy et al. | Aug 1977 | A |
| 4120294 | Wolfe | Oct 1978 | A |
| 4120296 | Prinz | Oct 1978 | A |
| 4163216 | Arpino | Jul 1979 | A |
| 4221223 | Linden | Sep 1980 | A |
| 4248244 | Charnitski et al. | Feb 1981 | A |
| 4252128 | Kane | Feb 1981 | A |
| 4364556 | Otte | Dec 1982 | A |
| 4436096 | Dyck et al. | Mar 1984 | A |
| 4566461 | Lubell et al. | Jan 1986 | A |
| 4637536 | Wong | Jan 1987 | A |
| 4642606 | Tsuyama | Feb 1987 | A |
| 4647217 | Havel | Mar 1987 | A |
| 4652141 | Arai | Mar 1987 | A |
| 4653498 | New, Jr. et al. | Mar 1987 | A |
| 4761835 | Chen | Aug 1988 | A |
| 4776323 | Spector | Oct 1988 | A |
| 4788983 | Brink et al. | Dec 1988 | A |
| 4803487 | Willard et al. | Feb 1989 | A |
| 4862395 | Fey et al. | Aug 1989 | A |
| 4867442 | Matthews | Sep 1989 | A |
| 4938228 | Righter et al. | Jul 1990 | A |
| 5008647 | Brunt et al. | Apr 1991 | A |
| 5059126 | Kimball | Oct 1991 | A |
| 5081991 | Chance | Jan 1992 | A |
| 5095382 | Abe | Mar 1992 | A |
| 5119101 | Barnard | Jun 1992 | A |
| 5148002 | Kuo et al. | Sep 1992 | A |
| 5167230 | Chance | Dec 1992 | A |
| 5191792 | Gloor | Mar 1993 | A |
| 5210540 | Masumoto | May 1993 | A |
| 5243659 | Stafford et al. | Sep 1993 | A |
| 5291301 | Lee | Mar 1994 | A |
| 5314389 | Dotan | May 1994 | A |
| 5318487 | Golen et al. | Jun 1994 | A |
| 5335188 | Brisson | Aug 1994 | A |
| 5345244 | Gildea et al. | Sep 1994 | A |
| 5391080 | Bernacki et al. | Feb 1995 | A |
| 5408444 | Kita et al. | Apr 1995 | A |
| 5420592 | Johnson | May 1995 | A |
| 5456262 | Birnbaum | Oct 1995 | A |
| 5458548 | Crossing et al. | Oct 1995 | A |
| 5464021 | Birnbaum | Nov 1995 | A |
| 5471405 | Marsh | Nov 1995 | A |
| 5474083 | Church et al. | Dec 1995 | A |
| 5485163 | Singer et al. | Jan 1996 | A |
| 5486818 | Loponen | Jan 1996 | A |
| 5491474 | Suni et al. | Feb 1996 | A |
| 5506774 | Nobe et al. | Apr 1996 | A |
| 5516334 | Easton | May 1996 | A |
| 5524637 | Erickson | Jun 1996 | A |
| 5552794 | Colley et al. | Sep 1996 | A |
| 5564417 | Chance | Oct 1996 | A |
| 5575284 | Athan et al. | Nov 1996 | A |
| 5581492 | Janik | Dec 1996 | A |
| 5589835 | Gildea et al. | Dec 1996 | A |
| 5592401 | Kramer | Jan 1997 | A |
| 5610387 | Bard et al. | Mar 1997 | A |
| 5611346 | Heikkilä et al. | Mar 1997 | A |
| 5617477 | Boyden | Apr 1997 | A |
| 5622180 | Tammi et al. | Apr 1997 | A |
| 5627548 | Woo et al. | May 1997 | A |
| 5629668 | Downs | May 1997 | A |
| 5632279 | Heikkilä | May 1997 | A |
| 5648768 | Bouve | Jul 1997 | A |
| 5655028 | Soll et al. | Aug 1997 | A |
| 5680465 | Boyden | Oct 1997 | A |
| 5684918 | Abecassis | Nov 1997 | A |
| 5686938 | Batkhan | Nov 1997 | A |
| 5690119 | Rytky et al. | Nov 1997 | A |
| 5697791 | Nashner et al. | Dec 1997 | A |
| 5702323 | Poulton | Dec 1997 | A |
| 5708725 | Ito | Jan 1998 | A |
| 5719743 | Jenkins et al. | Feb 1998 | A |
| 5721539 | Goetzl | Feb 1998 | A |
| 5721783 | Anderson | Feb 1998 | A |
| 5722418 | Bro | Mar 1998 | A |
| 5724265 | Hutchings | Mar 1998 | A |
| 5731757 | Layson, Jr. | Mar 1998 | A |
| 5735799 | Baba et al. | Apr 1998 | A |
| 5740077 | Reeves | Apr 1998 | A |
| 5742922 | Kim | Apr 1998 | A |
| 5743269 | Okigami et al. | Apr 1998 | A |
| 5757929 | Wang et al. | May 1998 | A |
| 5769755 | Henry et al. | Jun 1998 | A |
| 5779631 | Chance | Jul 1998 | A |
| 5781155 | Woo et al. | Jul 1998 | A |
| 5781913 | Felsenstein et al. | Jul 1998 | A |
| 5794164 | Beckert et al. | Aug 1998 | A |
| 5810722 | Heikkilä | Sep 1998 | A |
| 5810736 | Pail | Sep 1998 | A |
| 5813009 | Johnson et al. | Sep 1998 | A |
| 5815126 | Fan et al. | Sep 1998 | A |
| 5825327 | Krasner | Oct 1998 | A |
| 5832296 | Wang et al. | Nov 1998 | A |
| 5840039 | Heikkilä | Nov 1998 | A |
| 5844824 | Newman et al. | Dec 1998 | A |
| 5852401 | Kita | Dec 1998 | A |
| 5857939 | Kaufman | Jan 1999 | A |
| 5862511 | Croyle et al. | Jan 1999 | A |
| 5864870 | Guck | Jan 1999 | A |
| 5884198 | Kese et al. | Mar 1999 | A |
| 5889493 | Endo | Mar 1999 | A |
| 5890074 | Rydbeck et al. | Mar 1999 | A |
| 5890128 | Diaz et al. | Mar 1999 | A |
| 5891042 | Sham et al. | Apr 1999 | A |
| 5898831 | Hall et al. | Apr 1999 | A |
| 5905460 | Odagiri et al. | May 1999 | A |
| 5908464 | Kishigami et al. | Jun 1999 | A |
| 5909183 | Borgstahl et al. | Jun 1999 | A |
| 5910799 | Carpenter et al. | Jun 1999 | A |
| 5913163 | Johansson | Jun 1999 | A |
| 5919133 | Taylor et al. | Jul 1999 | A |
| 5919239 | Fraker et al. | Jul 1999 | A |
| 5921890 | Miley | Jul 1999 | A |
| 5925001 | Hoyt et al. | Jul 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 5955667 | Fyfe | Sep 1999 | A |
| 5976083 | Richardson et al. | Nov 1999 | A |
| 6000000 | Hawkins et al. | Dec 1999 | A |
| 6002918 | Heiman et al. | Dec 1999 | A |
| 6002982 | Fry | Dec 1999 | A |
| 6012586 | Misra | Jan 2000 | A |
| 6013007 | Root et al. | Jan 2000 | A |
| 6027428 | Thomas et al. | Feb 2000 | A |
| 6028853 | Haartsen | Feb 2000 | A |
| 6032108 | Seiple et al. | Feb 2000 | A |
| 6032530 | Hock | Mar 2000 | A |
| 6038542 | Ruckdashel | Mar 2000 | A |
| 6041023 | Lakhansingh | Mar 2000 | A |
| 6041114 | Chestnut | Mar 2000 | A |
| 6047301 | Bjorklund et al. | Apr 2000 | A |
| 6050924 | Shea | Apr 2000 | A |
| 6066075 | Poulton | May 2000 | A |
| 6078825 | Hahn et al. | Jun 2000 | A |
| 6080110 | Thorgersen | Jun 2000 | A |
| 6080111 | Pao-Lang | Jun 2000 | A |
| 6083248 | Thompson | Jul 2000 | A |
| 6091832 | Shurman et al. | Jul 2000 | A |
| 6104947 | Heikkila et al. | Aug 2000 | A |
| 6108197 | Janik | Aug 2000 | A |
| 6118882 | Haynes | Sep 2000 | A |
| 6128290 | Carvey | Oct 2000 | A |
| 6133722 | Havel | Oct 2000 | A |
| 6135951 | Richardson et al. | Oct 2000 | A |
| 6140981 | Kuenster et al. | Oct 2000 | A |
| 6148262 | Fry | Nov 2000 | A |
| 6148280 | Kramer | Nov 2000 | A |
| 6152856 | Studor et al. | Nov 2000 | A |
| 6157533 | Sallam et al. | Dec 2000 | A |
| 6157824 | Bailey | Dec 2000 | A |
| 6157935 | Tran et al. | Dec 2000 | A |
| 6163718 | Fabrizio | Dec 2000 | A |
| 6164541 | Dougherty et al. | Dec 2000 | A |
| 6181237 | Gehlot | Jan 2001 | B1 |
| 6198431 | Gibson | Mar 2001 | B1 |
| 6199550 | Wiesmann et al. | Mar 2001 | B1 |
| 6212414 | Alameh et al. | Apr 2001 | B1 |
| 6212469 | Knepper | Apr 2001 | B1 |
| 6229454 | Heikkila et al. | May 2001 | B1 |
| 6230047 | McHugh | May 2001 | B1 |
| 6243573 | Jacklin | Jun 2001 | B1 |
| 6244988 | Delman | Jun 2001 | B1 |
| 6246362 | Tsubata et al. | Jun 2001 | B1 |
| 6249427 | Carroll | Jun 2001 | B1 |
| 6251048 | Kaufman | Jun 2001 | B1 |
| 6272359 | Kivela et al. | Aug 2001 | B1 |
| 6282362 | Murphy et al. | Aug 2001 | B1 |
| 6285314 | Nagatsuma et al. | Sep 2001 | B1 |
| 6301964 | Fyfe et al. | Oct 2001 | B1 |
| 6304459 | Toyosato et al. | Oct 2001 | B1 |
| 6311071 | Voroba et al. | Oct 2001 | B1 |
| 6314091 | LaRowe, Jr. et al. | Nov 2001 | B1 |
| 6321158 | DeLorme et al. | Nov 2001 | B1 |
| 6324053 | Kamijo | Nov 2001 | B1 |
| 6331972 | Harris et al. | Dec 2001 | B1 |
| 6336126 | Bjorklund et al. | Jan 2002 | B1 |
| 6339746 | Sugiyama et al. | Jan 2002 | B1 |
| 6345197 | Fabrizio | Feb 2002 | B1 |
| 6347290 | Bartlett | Feb 2002 | B1 |
| 6351629 | Altschul et al. | Feb 2002 | B1 |
| 6385434 | Chuprun et al. | May 2002 | B1 |
| 6388613 | Nagatsuma et al. | May 2002 | B1 |
| 6394960 | Shinogi et al. | May 2002 | B1 |
| 6401085 | Gershman et al. | Jun 2002 | B1 |
| 6427063 | Cook et al. | Jul 2002 | B1 |
| 6447424 | Ashby et al. | Sep 2002 | B1 |
| 6449583 | Sakumoto et al. | Sep 2002 | B1 |
| 6450922 | Henderson et al. | Sep 2002 | B1 |
| 6456854 | Chern et al. | Sep 2002 | B1 |
| 6463385 | Fry | Oct 2002 | B1 |
| 6466232 | Newell et al. | Oct 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6478736 | Mault | Nov 2002 | B1 |
| 6496695 | Kouji et al. | Dec 2002 | B1 |
| 6513532 | Mault et al. | Feb 2003 | B2 |
| 6515595 | Obradovich et al. | Feb 2003 | B1 |
| 6519207 | Lukacsko | Feb 2003 | B1 |
| 6539336 | Vock et al. | Mar 2003 | B1 |
| 6560651 | Katz et al. | May 2003 | B2 |
| 6571200 | Mault | May 2003 | B1 |
| 6572636 | Hagen et al. | Jun 2003 | B1 |
| 6582342 | Kaufman | Jun 2003 | B2 |
| 6585622 | Shum et al. | Jul 2003 | B1 |
| 6594370 | Anderson | Jul 2003 | B1 |
| 6601016 | Brown et al. | Jul 2003 | B1 |
| 6605038 | Teller et al. | Aug 2003 | B1 |
| 6607483 | Holland | Aug 2003 | B1 |
| 6607493 | Song | Aug 2003 | B2 |
| 6611789 | Darley | Aug 2003 | B1 |
| 6669600 | Warner | Dec 2003 | B2 |
| 6678535 | Narayanaswami | Jan 2004 | B1 |
| 6685634 | Fry | Feb 2004 | B1 |
| 6702719 | Brown et al. | Mar 2004 | B1 |
| 6716139 | Hosseinzadeh-Dolkhani et al. | Apr 2004 | B1 |
| 6734837 | Havel | May 2004 | B1 |
| 6736759 | Stubbs et al. | May 2004 | B1 |
| 6741864 | Wilcock et al. | May 2004 | B2 |
| 6745069 | Nissila et al. | Jun 2004 | B2 |
| 6749432 | French et al. | Jun 2004 | B2 |
| 6753882 | Nakazawa et al. | Jun 2004 | B2 |
| 6754472 | Williams et al. | Jun 2004 | B1 |
| 6757719 | Lightman et al. | Jun 2004 | B1 |
| 6758816 | Tsubata et al. | Jul 2004 | B1 |
| 6761637 | Weston | Jul 2004 | B2 |
| 6790178 | Mault et al. | Sep 2004 | B1 |
| 6816782 | Walters et al. | Nov 2004 | B1 |
| 6832109 | Nissila | Dec 2004 | B2 |
| 6872077 | Yeager | Mar 2005 | B2 |
| 6876845 | Tabata et al. | Apr 2005 | B1 |
| 6882955 | Ohlenbusch et al. | Apr 2005 | B1 |
| 6934461 | Strub et al. | Aug 2005 | B1 |
| 6947571 | Rhoads et al. | Sep 2005 | B1 |
| 7076291 | Pulkkinen et al. | Jul 2006 | B2 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7162392 | Vock et al. | Jan 2007 | B2 |
| 7181024 | Oba et al. | Feb 2007 | B1 |
| 7192387 | Mendel | Mar 2007 | B2 |
| 7192402 | Amano et al. | Mar 2007 | B2 |
| 7203721 | Ben-Efraim et al. | Apr 2007 | B1 |
| 7220220 | Stubbs et al. | May 2007 | B2 |
| 7229385 | Freeman et al. | Jun 2007 | B2 |
| 7261564 | Sutula, Jr. | Aug 2007 | B2 |
| 7353137 | Vock et al. | Apr 2008 | B2 |
| 7428471 | Darley et al. | Sep 2008 | B2 |
| 7428472 | Darley et al. | Sep 2008 | B2 |
| 7454002 | Gardner et al. | Nov 2008 | B1 |
| 7549947 | Hickman et al. | Jun 2009 | B2 |
| 7602301 | Stirling | Oct 2009 | B1 |
| 7905815 | Ellis et al. | Mar 2011 | B2 |
| 7931562 | Ellis et al. | Apr 2011 | B2 |
| RE44103 | Williams | Mar 2013 | E |
| 8579767 | Ellis et al. | Nov 2013 | B2 |
| 8649975 | Nesbitt | Feb 2014 | B2 |
| 8690735 | Watterson et al. | Apr 2014 | B2 |
| 8814754 | Weast | Aug 2014 | B2 |
| 8944960 | Dugan | Feb 2015 | B2 |
| 9028368 | Ashby et al. | May 2015 | B2 |
| 20010003542 | Kita | Jun 2001 | A1 |
| 20010004397 | Kita et al. | Jun 2001 | A1 |
| 20010011025 | Ohki et al. | Aug 2001 | A1 |
| 20010027375 | Machida et al. | Oct 2001 | A1 |
| 20010040627 | Obradovich | Nov 2001 | A1 |
| 20010049470 | Mault et al. | Dec 2001 | A1 |
| 20020000470 | Lanzaro et al. | Jan 2002 | A1 |
| 20020016235 | Ashby et al. | Feb 2002 | A1 |
| 20020022551 | Watterson et al. | Feb 2002 | A1 |
| 20020040255 | Neoh | Apr 2002 | A1 |
| 20020049535 | Rigo et al. | Apr 2002 | A1 |
| 20020054174 | Abbott et al. | May 2002 | A1 |
| 20020068604 | Prabhakar et al. | Jun 2002 | A1 |
| 20020068873 | Nissila | Jun 2002 | A1 |
| 20020091843 | Vaid | Jul 2002 | A1 |
| 20020094776 | Pulver | Jul 2002 | A1 |
| 20020094845 | Inasaka | Jul 2002 | A1 |
| 20020102988 | Myllymaki | Aug 2002 | A1 |
| 20020107433 | Mault | Aug 2002 | A1 |
| 20020109600 | Mault et al. | Aug 2002 | A1 |
| 20020123386 | Perlmutter | Sep 2002 | A1 |
| 20020198612 | Smith et al. | Dec 2002 | A1 |
| 20030028116 | Bimbaum | Feb 2003 | A1 |
| 20030069108 | Kaiserman et al. | Apr 2003 | A1 |
| 20030091964 | Yeager | May 2003 | A1 |
| 20030100315 | Rankin | May 2003 | A1 |
| 20030126250 | Jhanji | Jul 2003 | A1 |
| 20030171189 | Kaufman | Sep 2003 | A1 |
| 20030182052 | DeLorme et al. | Sep 2003 | A1 |
| 20030208409 | Mault | Nov 2003 | A1 |
| 20030226695 | Mault | Dec 2003 | A1 |
| 20040046692 | Robson et al. | Mar 2004 | A1 |
| 20050113650 | Pacione et al. | May 2005 | A1 |
| 20050121504 | Sanders et al. | Jun 2005 | A1 |
| 20050209052 | Ashby et al. | Sep 2005 | A1 |
| 20050250440 | Zhou et al. | Nov 2005 | A1 |
| 20070111858 | Dugan | May 2007 | A1 |
| 20070213126 | Deutsch | Sep 2007 | A1 |
| 20100062818 | Haughay, Jr. | Mar 2010 | A1 |
| 20140206955 | Stivoric et al. | Jul 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 197 12 672 | Jul 1998 | DE |
| 1 018 832 | Jul 2000 | EP |
| 1 050 793 | Nov 2000 | EP |
| 1195135 | Apr 2002 | EP |
| 2 350 749 | Dec 2000 | GB |
| 5-249899 | Sep 1993 | JP |
| WO 8705229 | Sep 1987 | WO |
| WO 9812599 | Mar 1998 | WO |
| WO 9838820 | Sep 1998 | WO |
| WO 9923524 | May 1999 | WO |
| WO 9923525 | May 1999 | WO |
| WO 9952050 | Oct 1999 | WO |
| WO 0036900 | Jun 2000 | WO |
| WO 0100281 | Jan 2001 | WO |
| WO 0141879 | Jun 2001 | WO |
| Entry |
|---|
| Barber, Jr. et al., “Designing for Wireless LAN Communications,” Circuits and Devices, vol. 12, No. 4, Jul. 1996, pp. 29-33. |
| Bhagwat et al., “A Routing Vector Method (RVM) for Routing in Bluetooth Scatternets,” Mobile Multimedia Communications, Nov. 1999, pp. 375-379. |
| Bukhres et al., “Mobile Computing in Military Ambulatory Care,” 10th IEEE Symposium on Computer-Based Medical Systems, Jun. 1997, pp. 58-63. |
| Hum, “Fabric area network—a new wireless communications infrastructure to enable ubiquitous networking and sensing on intelligent clothing,” Computer Networks, vol. 35, Issue 4, Mar. 2001, 2 pages. |
| Jones et al., “A Protocol for Automatic Sensor Detection and Identification in a Wireless Biodevice Network,” 11th IEEE Symposium on Computer-Based-Medical Systems, Jun. 1998, pp. 311-316. |
| Mann, Steve, “Wearable Computing: A First Step Toward Personal Imaging,” Computer, vol. 30, No. 2, Feb. 1997, 11 pages. |
| Santos, Roy, “FitSense. The FS-1 Pro promises highly accurate speed and distance readings for runners,” copyright 2004, website address: http://www.g4tv.com/articles/17027/fun-fitness-tech/. |
| Sayer, Peter, “New wired clothing line comes with personal network,” Aug. 18, 2000, CNN.com; website address: http://archives.cnn.com/2000/Tech/computing/08/18/wired.jacket.idg/index.html. |
| Website, Bluetooth, The Official Bluetooth® Wireless Info Site, regarding Bluetooth enabled devices, copyright 2004; website address: http://www.bluetooth.com/index.asp. |
| Website, Digiman, human-computer interface research, copyright 2003; website address: http://www.digiman.org/html/main.html. |
| Website, FitSense Technology, “FS-1 Speedometer. One Watch. Total Feedback. Speed, Distance & Heart Rate Monitoring System for Runners and Walkers,” copyright 2003; website address: http://fitsense.com. |
| Website, Institute of Electrical and Electronics Engineers, Inc., IEEE 802.11™ Wireless Local Area Networks—The Working Group for WLAN Standards, copyright 2004 IEEE; website address: http://grouper.ieee.org/groups/802/11/. |
| Website, ViA Inc., Computers that fit people, Jan. 2004; website address: http://www.via.pc.com/index.html. |
| Website article, “Visions of wearable Internet ware,” Jun. 26, 2000, CNN.com; website address: http://archives.cnn.com/2000/STYLE/fashion/06/26/wearable.computers/index.html. |
| Barber Jr., Thomas J., “BodyLAN: A Low-Power Communications System,” Thesis submitted to the Massachusetts Institute of Technology Department of Electrical Engineering and Computer Science, pp. 1-75 (Feb. 1996). |
| Adler, Ari T., “A Cost-Effective Portable Telemedicine Kit for Use in Developing Countries,” Thesis, Department of Mechanical Engineering, Massachusetts Institute of Technology, Cambridge (2000), 95 pages. |
| Benefon ESC! Owner's Manual, Benefon Oyj, Finland (2001), 169 pages. |
| eTrex Summit Personal Navigator: Owner's Manual and Reference Guide, Garmin International, Inc., Kansas (Feb. 2001), 73 pages. |
| GPS II Plus: Owner's Manual & Reference, Garmin Corporation, Taiwan (Feb. 1999), 112 pages. |
| NavTalk Cellular Phone/GPS Receiver: Owner's Manual and Reference Guide, Garmin International, Inc., Kansas (Jan. 2000), 128 pages. |
| Nokia 6120: Owner's Manual, Nokia Mobile Phones, Inc., Tampa (1998) 93 pages. |
| Satava et al., “The Physiologic Cipher at Altitude: Telemedicine and Real-Time Monitoring of Climbers on Mount Everest,” Telemedicine Journal and e-Health, vol. 6, No. 3 (2000), 11 pages. |
| Revised Joint Claim Construction Statement, Adidas AG and Adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., Civil Action No. 14-130-GMS (N.D. Del.), filed Mar. 2, 2015. |
| Defendant MapMyFitness, Inc.'s Supplemental Objections and Responses to Plaintiffs' First Set of Interrogatories (Nos. 6, 7, 10), adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., Civil Action No. 14-130-GMS, filed Sep. 18, 2014, 10 pages. |
| Defendant Under Armour, Inc.'s Supplemental Objections and Responses to Plaintiffs' First Set of Interrogatories (Nos. 6, 7, 10), adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., Civil Action No. 14-130-GMS, filed Sep. 18, 2014, 10 pages. |
| HP 620LX/660LX Palmtop User Guide, Hewlett-Packard Co. (1998), 172 pages. |
| Redin, Maria S., “Marathon Man,” Thesis, Department of Electrical Engineering and Computer Science, Massachusetts Institute of Technology (Jun. 15, 1998), 57 pages. |
| Screenshots from AustinExplorer.com via the Way Back Machine as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 19 pages. |
| Screenshots from GPS-Tour.info via the Way Back Machine as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 25 pages. |
| Screenshots from LocalHikes.com via the Way Back Machine as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 12 pages. |
| Screenshot from MapQuest.com via the Way Back Machine and “How it Works; Online Maps for Here, There and Everywhere” from The New York Times as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 4 pages. |
| Information about Quokka Sports from The Free Library, Inventing Interactive and Microsoft News Center as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 14 pages. |
| Screenshots from Palmtop.nl and My2Cents.info via the Way Back Machine and TomTom Maps-on-Line Information from PocketGPSWorld.com as provided by Defendants in adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., 1:2014-cv-00130 (D. Del.), 24 pages. |
| Second Revised Joint Claim Construction Statement, adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., Civil Action No. 14-130-GMS, filed Apr. 6, 2015, 12 pages. |
| Order Construing the Terms of U.S. Pat. No. 7,957,752; 8,244,226; 8,068,858; 7,905,815; 7,931,562; 8,652,009; 8,725,276; 8,579,767; 8,721,502, adidas AG and adidas America, Inc. v. Under Armour, Inc. and MapMyFitness, Inc., Civil Action No. 14-130-GMS, filed Jun. 15, 2015, 6 pages. |
| Stipulation of Dismissal, Adidas AG v. Under Armour, Inc. et al., D. Del, C.A. No. 14-130 (GMS), Document 225-226, ordered May 9, 2016. |
| Termination, Under Armour, Inc. v. Adidas AG, Paper 44, ordered May 9, 2016, in IPR2015-00697, (U.S. Pat. No. 7,905,815 B2); IPR2015-00698 (U.S. Pat. No. 8,092,345 B2); IPR2015-00700 (U.S. Pat. No. 8,579,767 B2); IPR2015-01528 (U.S. Pat. No. 8,721,502 B2); IPR2015-01532 (U.S. Pat. No. 8,652,009 B2); IPR2015-01891 (U.S. Pat. No. 8,725,276 B2). |
| Complaint for Patent Infringement, adidas AG and adidas America, Inc. v. Asics America Corporation and FitnessKeeper, Inc., 1:17-cv-00285 (D. Del.), filed Mar. 17, 2017. |
| Number | Date | Country | |
|---|---|---|---|
| 20160129309 A1 | May 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60270400 | Feb 2001 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10645713 | Aug 2003 | US |
| Child | 12617871 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13794011 | Mar 2013 | US |
| Child | 14980559 | US | |
| Parent | 13789266 | Mar 2013 | US |
| Child | 13794011 | US | |
| Parent | 12617871 | Nov 2009 | US |
| Child | 13789266 | US | |
| Parent | PCT/US02/04947 | Feb 2002 | US |
| Child | 10645713 | US |
