US 7,698,101 B2Grant
Smart garment
Issue Date:2010-04-13
•43 Claims
•13 Drawing Sheets
Abstract
A sensor authenticated to a garment transfers information, either wirelessly or wired, to an external data processing device. Such information includes location information, physiometric data of the individual wearing the garment, garment performance and wear data (when the garment is an athletic shoe, for example). The external data processing device can be portable digital media players that are, in turn, in wireless communication with a server computer or other wireless devices.
Metadata
Assignee
- Apple Inc.
Inventors
- Brett G. Alten
- Robert Edward Borchers
Application Information
Application Number:US 11/683,391
Filing Date:2007-03-07
Priority Date:2007-03-07
Art Unit:2857
Classifications
IPC:
G08B29/00
Patent Drawings (13 sheets)
Description
Cross Reference to Related Applications
[0001] This application is related to i) U.S. patent application Ser. No. 11/439,521, filed May 22, 2006, and entitled “COMMUNICATION PROTOCOL FOR USE WITH PORTABLE ELECTRONIC DEVICES” and ii) U.S. patent application Ser. No. 11/419,737, filed May 22, 2006, and entitled “INTEGRATED MEDIA JUKEBOX AND PHYSIOLOGIC DATA HANDLING APPLICATION” each of which are hereby incorporated by reference herein in their entirety for all purposes.
Field of the Invention
[0002] The invention relates generally to performance monitoring. More particularly, methods and apparatus electronically pairing an authorized garment and a sensor that receives data from the garment are disclosed.
Description of Related Art
[0003] The use of devices to obtain exercise performance information is known. For example, simple mechanical pedometers have been used to obtain information relating to walking or running. A typical mechanical pedometer is a standalone device merely displays an indication of number of steps taken which, typically at most, can be converted to distance traveled by multiplying the number of steps taken by an estimated average stride distance.
[0004] More sophisticated devices are also known. For example, as described in U.S. Pat. No. 6,898,550 (the '550 patent), a foot-mounted unit, including a sensor for sensing motion of the foot of a user, is configured to provide motion information—wirelessly—to a wrist-device. The wrist device includes a display for displaying information to the user based upon data accumulated by the foot-mounted unit and transmitted wirelessly to the wrist device. In addition, as described in the '550 patent, the wrist device can be coupled to a computer and/or a network server via a network. The user can operate software running on the computer and/or the server to analyze received data and/or to select operating parameters for the wrist device and/or the foot-mounted unit.
[0005] Unfortunately, however, it is becoming more commonly practiced to place the sensor at locations on a garment (shoes, for example) that are not specifically designed to physically accommodate the sensor and/or calibrated to accurately reflect data supplied to the wrist device. For example, Nike Inc. and Apple Inc. have joined forces to provide what is referred to as the Nike iPod Sport Kit™ that is a wireless device kit that allows communication between a pair of specially configured Nike+™ shoes and an iPod nano™. The Nike iPod Sport Kit™ is arranged such that at least one of the Nike+™ shoes includes a sensor (that includes an accelerometer/transmitter) mounted under the inner sole and a receiver that communicates with the iPod nano™. In order to accommodate the sensor and provide appropriate data to the iPod nano™, the shoe must be a Nike+™ model with a special pocket in which to place the sensor. However, some people have taken it upon themselves to remove the sensor from the special pocket of the Nike+™ shoe and place it at inappropriate locations (shoelaces, for example) or place it on non-Nike+™ model shoes.
[0006] Therefore, what is desired is a method of electronically pairing a sensor and an authorized garment.
Summary
[0007] An embodiment of this invention pertains to linking an authenticated sensor with one or more authorized garments (such as running shoes, shirts, slacks, etc.) that can provide in addition to current physiologic data of the user, garment performance statistics (i.e., rate of wear of a running shoe), location of the garment and any related information (location of near-by eating establishments, for example) and any other garment related data. In one embodiment, the sensor can be authenticated for use with a particular garment using, for example, an identification device (such as an RFID type device). In this way, only an authenticated sensor can be used to provide information to the wearer of the garment.
[0008] The invention can be implemented in numerous ways, including as a method, system, or computer readable medium. Several embodiments of the invention are discussed below. One embodiment of the invention is a method of electronically pairing a sensor and a garment. The method can include, for example, at least: establishing a communication link between the sensor and the garment and electronically pairing the garment and the sensor only if the garment is authorized to be paired with the sensor.
[0009] As computer program product, another embodiment of the invention includes at least: computer code for establishing a communication link between the sensor and the garment, computer code for determining if the garment is an authorized garment, and computer code for electronically pairing the garment and the sensor only if the garment is authorized to do so.
[0010] As an electronic consumer product system, yet another embodiment of the invention includes, for example, at least: a sensor, and a garment electronically paired with the sensor, wherein the sensor receives data from the garment and passes a portion of the data to an external circuit for further processing.
[0011] Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
Brief Description of the Drawings
[0012] FIG. 1 illustrates an example of a physiologic data-gathering device (sensor) in the form of sensor in accordance with an embodiment of the invention.
[0013] FIGS. 2A and 2B illustrate authenticating sensor and garment in accordance with an embodiment of the invention.
[0014] FIG. 3 shows representative tag identifier database in accordance with an embodiment of the invention.
[0015] FIGS. 4-5 illustrates system for monitoring and/or controlling user exercise or other activity or physiology in accordance with an embodiment of the invention.
[0016] FIG. 6 is a flowchart illustrating an example of steps, mostly within the host computer to accomplish transfer of physiologic data between the portable media player and workout data service in accordance with an embodiment of the invention.
[0017] FIG. 7 shows a flowchart detailing a process for electronically pairing a sensor and a garment in accordance with an embodiment of the invention.
[0018] FIG. 8 shows a running shoe that has been electronically paired with a sensor in accordance with an embodiment of the invention.
[0019] FIGS. 9-10 shows the running shoe of FIG. 7 being used in a toe plant type stride.
[0020] FIGS. 11-12 shows the running shoe of FIG. 7 being used in a heel plant type stride.
[0021] FIG. 13 shows a representative running style profile template in accordance with an embodiment of the invention.
Detailed Description
[0022] Reference will now be made in detail to selected embodiments of the invention an example of which is illustrated in the accompanying drawings. While the invention will be described in conjunction with selected embodiments, it will be understood that it is not intended to limit the invention to one particular embodiment. To the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims.
[0023] Outdoors endurance activities have become very popular not only because they are enjoyable and healthy, but also because they provide opportunities for competition, camaraderie, and a structured regimen. It would be beneficial for an individual participating in an outdoor endurance activity such as running, cross-country skiing, in-line skating, or outdoor swimming to be able to monitor his or her performance in metrics such as speed, distance, slope, elevation, equipment used (thereby correlating an individual's performance to particular running shoes, for example). Furthermore, as part of a particular training program, a user will want to be able to keep track of his or her performance for a particular event as well as be able to store the information for later comparison with subsequent athletic events. For example, if a runner desires to track his or her performance over a period of time, various physical characteristics of the runner, such as age, weight, and gender, for example, could be used to evaluate the runner's performance against both his or her individual performances. In addition to being able to gauge their own particular athletic performances against their own historical record, a user might also like to be able to compare his or her own performance against a reference performance typical of, for example, a person having similar physical characteristics. In this way, a user could gauge his or her own athletic prowess and abilities against an accepted reference and be able to determine, for example, the performance percentile he or she falls in relation to his or her particular cohort of runners.
[0024] In addition to being able to ascertain one's own performance against a hypothetical norm, a user may also like to be able to compete against others. Such competitions historically have been held in meets, or other local physical competitions where athletes meet in person and compete. It would also be desirable to be able to compete against an opponent even in those situations where both opponents cannot be physically in the same location using a network such as the Internet. However, being able to track each individual, until recently, has been impractical. In addition, it would be beneficial to be able to correlate a user's performance to particular garments (running time vs. a particular shoe or shoe design) as well as tracking shoe characteristics (such as wear) over time or distance used.
[0025] The described embodiments provide an improved method, apparatus and system for automatic monitoring in real-time athletic performance of a user utilizing an authenticated sensor electronically paired with an authorized garment worn by the user in communication with (either wirelessly or wired) an external processing device. As used herein an authorized garment is a garment sanctioned to be electronically paired with an authenticated (i.e., certified) sensor. Once the garment and sensor are electronically paired, the sensor can receive (and in some cases process) sensing information (such as garment performance data or user performance data) received from the garment. Since only authorized garments are configured to electronically pair with authenticated sensors, a user (or manufacturer) can be assured that the sensing data received by the sensor is both accurate and consistent with its intended use (a sensor designed for use with running shoes can not properly be used with dance shoes, for example). In the case of running shoes, if a user owns a number of running shoes, he or she may want to determine if a particular shoe or shoe design facilitates superior performance by the user, determine which shoe design provides for better wear, evaluate a particular shoe against other shoes of similar design, and so on.
[0026] Improved security can be provided by authenticating the sensor to only a limited number of garments (such as running shoes) as determined by a user, shoe manufacturer, etc. thereby reducing the incentive for thieves to steal the sensor or finders of lost sensors to keep them. Since the sensor will function properly with only authorized garments, a thief (or recalcitrant finder) can use the sensor only if it is properly authenticated and only then with authorized garments thereby markedly reducing the incentive to steal (or keep) the sensor resulting in vastly improved security than would otherwise be possible.
[0027] Furthermore, in addition to performance and improved security, a sensor can provide notification to a user that a particular garment has reached an expected useful lifetime based upon any number of factors, such as, an amount of time that the garment has been used, an amount of wear detected by the sensor, etc. For example, in many cases, a runner will not notice that a running shoe has been worn down to the point where crucial support (arch support, for example) has eroded thereby increasing the likelihood of injury. In this way, by providing a notification that one or both of the running shoes should be replaced, the runner may be better able to avoid injuries related to outworn equipment.
[0028] A sensor can also include location-sensing devices (such as a GPS receiver) that provide velocity and/or location data to a processor unit that can be coupled to a database having information such as physical characteristic data such as weight, age, and gender. The database can, in turn, provide an updated readout to a display unit of the user's ongoing athletic performance statistics. Such statistics can include elevation gain, speed, heading, elevation, calories burned, anticipated calories burned (based upon a pre-selected course), and others. Furthermore, the sensor can be coupled to a distributed network of computers, such as the Internet, by way of a wireless device or directly by way of an I/O port coupled to external circuitry, such as a personal computer, personal digital assistant (PDA), modem, etc., or in some cases as part of a peer-to-peer type arrangement of like wireless sensors or other wireless devices. In this way, the user can download selected data (such as other athlete's performance data, selected courses, training programs, etc.) allowing the user to be part of a virtual community of athletes that can interact with each other in real time or virtually. In some embodiments, the sensor can optionally include one or more dead reckoning devices to provide direction information or change of location information. Such dead reckoning devices can include altimeters, accelerometers, cadence measurements sensors and the like.
[0029] FIG. 1 illustrates an example of sensor 100 in accordance with an embodiment of the invention. Sensor 100 can include processor 102 that can be used to control the overall operation of sensor 100. Data can be stored in RAM 104 that can provide volatile data storage and Read-Only Memory (ROM) 106 for storing programs, utilities or other processes to be executed. Sensor 100 can also include user input device 108 that allows a user to interact with sensor 100. For example, user input device 108 can take a variety of forms, such as a button, keypad, dial, etc. having associated labels to enable a user to know how to request an operation of sensor 100. In one embodiment, the labels are hard or permanent. Alternatively, the labels are soft or can be changed by the user according to a menu of operations. Data bus 110 can facilitate data transfer between at least ROM 106, RAM 104, processor 102 and one or more output devices 112 used to communicate with external circuitry. Such output devices 112 can include I/O data port 114 or wireless interface 116. More generally, they can include an audio and/or visual indicator 118 such as speakers and/or LEDs that can be used to notify a user of an event. Output devices 112 can be in communication with processor 102 directly (or by way of data bus 110). In the case of wireless interface 116, a wireless communication channel can be opened that can be used for transmitting and receiving data between sensor 100 and external circuitry using, for example, RF carrier waves, infrared (IR) signals, etc.
[0030] If GPS capable, sensor 100 can utilize line of sight to GPS antenna 120 to receive GPS satellite signals at GPS receiver 122 from one or more GPS satellites to determine a location of sensor 100 and/or a time of observation. In some embodiments, sensor 100 can include one or more dead reckoning devices 124 to provide direction information or change of location information. Such dead reckoning devices include altimeters, accelerometers, cadence measurement sensors and the like. For example, cadence measurement sensors utilize the rhythmic motion associated with the athletic performance (e.g., the user's strides) to extrapolate the user's speed and distance during periods of satellite blockage thereby further enhancing the robustness of the system in challenging environments with high levels of signal blockage. Authorization module 128 can be used to facilitate the electronic pairing of a garment and sensor 100 by processing garment identification credentials.
[0031] In those embodiments of sensor 100 that include GPS receiver 122, RAM 104 can store in addition to selected data such as measured user performance metrics, local elevation data in digital elevation model (DEM) database 126 in the form of DEM data. In addition to local elevation data, DEM database 126 can store local points of interest (such as restaurants, rest stops, parks, shops, etc.) that can be updated by the user or downloaded from external circuitry. DEM data can serve to improve the accuracy of the GPS elevation and speed measurements as well as to improve the tolerance of sensor 100 to satellite blockage. Processor 102 can be configured to calculate carrier-wave Doppler-shift based user velocity based upon data received from GPS receiver 122 and DEM database 126 and calculate selected athletic performance feedback data using the calculated user velocity and other data such as the elevation profile and the user physical characteristics. The use of Doppler based velocity measurements gives accuracies in the range of 0.1 mph in typical GPS receivers, which is the highest accuracy typically required for useful assessment of athletic activities.
[0032] Sensor 100 can be coupled to a distributed network of computers, such as the Internet, or other like sensors in a peer-to-peer arrangement by way of wireless interface 116 and/or I/O port 114 coupled to external circuitry, such as a personal computer, personal digital assistant (PDA), modem, and the like. In this way, a user can download selected data related to, for example, other athlete's performance data, selected courses, training programs, and so on. The user can also be part of a virtual community of athletes each of whom can interact with each other as well as provide for favorite-routes databases, regimen databases, performance benchmarking, and route mapping and planning, and so on.
[0033] As shown in FIG. 2A , wireless sensor 100 can periodically emit ping signal 204 that can include activation flag 206. In some embodiments, activation flag 206 can activate (i.e., wake up) identification module 202 only when signal strength Sr associated with ping signal 204 is greater than a preset threshold value Sth. In this way, only those sensors within range R appropriately programmed can be activated, thereby preventing sensors other than those intended for placement on or near the tagged garment from communicating with identification module 202. It should be noted that the actual activation process is not strictly limited to wireless technology. For example, various other activation technologies include, but are not limited to, magnetic activation (such as the Hall effect), resistor/capacitor activation/authorization. In addition to activation techniques discussed, sensor 100 can be automatically deactivated or placed into a hold state when sensor 100 is removed from garment 208 and/or when sensor 100 is moved beyond range R.
[0034] Identification module 202 can be attached to or otherwise associated with garment 208 by being sewn onto garment 208, secured to garment 208 by way of fasteners, woven into the fabric of garment 208, and so on. Since it is identification module 202 itself that provides the identification information used to electronically pair sensor 100 and garment 208, it is important that identification module 202 be securely connected to garment 208 such that it does not fall off or otherwise become detached during use (that can result in a warning from the sensor that the authentication has lapsed thereby helping to reduce the incidence of lost or stolen sensors). It should be noted that the identification module 202 could be dedicated to garment 208 (at the time of manufacture of the garment, for example) providing in addition to identification information other useful information (such as date of manufacture, time of use since date of manufacture, and so on) associated with a particular garment. In this way, identification module 202 can provide data storage functions such as backing up selected data, providing a database of information that is matched to garment 208 independent of any particular sensor and so on. This arrangement can be especially helpful in situations where a sensor has been lost or otherwise compromised to the degree where the chances of retrieving any data stored in the sensor would be very remote.
[0035] Identification module 202 can be fabricated using radio frequency identification (RFID) technology that can store and remotely retrieve data using devices called RFID tags or transponders. An RFID tag is an object that can be attached to or incorporated into a product, animal, or person for the purpose of identification using radio waves (chip-based RFID tags can contain silicon chips and antennas). Passive tags require no internal power source since they rely upon electrical current induced in the antenna by the incoming radio frequency signal to power up and transmit a response. It should be noted that the response of a passive RFID tag is not necessarily just an ID number, the passive RFID tag can contain non-volatile memory device (such as EEPROM) for storing data. Unlike passive RFID tags, active RFID tags have their own internal power source that is used to power any ICs that generate the outgoing signal. Active tags are typically much more reliable (e.g., fewer errors) than passive tags due to the ability for active tags to conduct a “session” with a reader. Active tags, due to their onboard power supply, also transmit at higher power levels than passive tags, allowing them to be more effective in “RF challenged” environments like water, metal, or at longer distances. A number of non-invasive and reliable power sources such as batteries and in some cases, piezoelectric or kinetic power sources activated by the use of the garment can be used to supply the requisite power for the active RFID tags.
[0036] With reference to FIG. 2B , identification module 202 can generate tag identifier signal 210 that can include tag identifier 212 that can include a number of garment identification indicia (e.g., numerical, alphanumeric). Some or all of the garment identification indicia can be encrypted providing additional security. Sensor 100 can wirelessly transmit tag identifier signal 210 (or any appropriate portion thereof) at wireless interface 116 that can be received at authorization module 128. Authorization module 128 can then forward tag identifier query 214 to tag identifier database 216. In the described embodiment, tag identifier database 216 can include a list authorized tag identifiers used to determine an authorization status of tag identifier 212 by, for example, comparing tag identifier 212 to the list of authorized tag identifiers stored in tag identifier database 216. Authorization status signal 218 can be generated indicating whether or not tag identifier 212 matches an authorized tag identifier stored in tag identifier database 216. Authorization status signal 218 can be forwarded to processor 102 that can, in turn, execute instructions based upon authorization status signal 218. For example, if authorization status signal 218 indicates that tag identifier 212 matches an entry in the list of authorized tag identifiers, then processor 102 can be directed to execute authorized garment instruction set 220. However, if authorization status signal 218 indicates tag identifier 212 does not match an entry in the list of authorized tag identifiers (i.e., no match), processor 102 can be directed to execute unauthorized garment instruction set 222 indicating that the garment identification information does not correspond to an authorized garment.
[0037] For example, when processor 102 executes unauthorized garment instruction set 222, sensor 100 can be instructed by processor 102 to perform a number of predetermined actions consistent with an unauthorized garment. Such pre-determined actions can include, for example, issuing an alert by way of audio/visual output device 118 (beep from a speaker, flashing LED, etc.) that notifies the user that the garment (or more accurately, the identification module associated with the garment) is not authorized to be used with sensor 100 and to display actions that can be taken by the user to rectify the condition. Such actions can include instructing the user to register the tag identifier associated with the unauthorized garment or instructing sensor 100 to shut down in order to prevent what appears to be an attempt to pair sensor 100 with an unauthorized garment. In this case, sensor 100 can then be restarted by a user entering an authorization code by way of user input device 108, for example, thereby preventing unauthorized pairing of sensor 100 with garment 208.
[0038] When processor 102 executes authorized garment instruction set 220, sensor 100 can be instructed by processor 102 to perform a number of predetermined actions consistent with an authorized garment. Such predetermined actions can include accessing tag identifier database 216 in preparation for a forthcoming activity for which sensor 100 would generate performance data of either (or both) garment 208 and/or the user. In the described embodiment, tag identifier database 216 can include information for all registered identification modules and associated garments an example of which is shown in FIG. 3 .
[0039] FIG. 3 shows representative tag identifier database 300 in accordance with an embodiment of the invention. It should be noted that tag identifier database 300 is a particular implementation of tag identifier database 216 described above and is therefore only exemplary in nature. Tag identifier database 300 can be constructed along the lines of a m×n memory array having m rows (302-1 through 302-m), each corresponding to a particular tag identifier (that, in turn, can be associated with a particular garment) and n columns each being of suitable size for storing data related to a particular garment in a data field of appropriate length. For example, row 302-1 includes data fields 304-1 through 304-n where data field 304-1 is used to store tag identifier “ID1” corresponding to tag identifier stored in sensor 306-1 attached to garment (in this case a running shoe) 308-1. Remaining data fields 304-2 through 304-n can be used to store any data deemed appropriate such as performance data, garment wear data, purchase date, and so on that can be used in subsequent analysis. It should be noted that at any time, any of sensors 306 can be swapped for any other sensor or interchanged between any of garments 308 thereby affording the user complete freedom of association between available sensors, garment inventory, or sensor/garment replacements.
[0040] In this way, an extensive database of pertinent garment data can be stored and made available for the user and any other interested party such as a manufacturer interested in garment wear patterns, a user interested in correlating specific garment design to user performance statistics as would be the case with running shoes and run times, for example. Such data can include specific performance data (number of hours of use from time of purchase, for example) and any other data deemed appropriate. It should be noted that there could be a one-to-one correspondence between a particular garment and a particular tag identifier at a time. However, at any time, a particular tag identifier can be re-assigned to any other garment simply by removing the identification module associated with the particular tag identifier from one garment and placing it onto or in another garment. Moreover, the tag identifier can itself be re-assigned by, for example, re-programming a non-volatile type memory device (incorporated in the identification module) into which the particular tag identifier had been previously programmed.
[0041] FIG. 4 illustrates system 400 for monitoring and/or controlling user exercise or other activity or physiology in accordance with an embodiment of the invention. System 400 can include sensor 100 coupled to garment 402 (which in this case takes the form of an athletic shoe) in communication with processing device 404 that can take the form of portable media player 404. User exercise data can be communicated (in this example, wirelessly) from sensor 100 configured for gathering physiological data of a user (such as a sensor to sense the foot motion of a user) to portable media player 404. In one example, the user exercise data is wirelessly transmitted via accessory 406 which can be configured to selectively attach to a data port of portable media player 404. An example of accessory 406, and the interoperation of the accessory with portable media player 404, is described in U.S. patent application Ser. No. 11/439,521 filed May 22, 2006, and entitled “COMMUNICATION PROTOCOL FOR USE WITH PORTABLE ELECTRONIC DEVICES” incorporated by reference herein.
[0042] User physiological data can be accumulated by sensor 100 and then provided wirelessly to portable media player 404. Meanwhile, cues relative to the exercise (e.g., audio cues) provided by, for example, exercise templates retrieved from portable media player 404 to the user (by way of, for example, wire 412 and headphones 414). In addition to providing the cues relative to the exercise, portable media player 404 can also be configured to provide playback of media (such as audio media) to user 408 (also via wire 412 and headphones 414 or any other appropriate communication channel) that could, for example, be coordinated with the exercise cues. For example, playback of media can be accomplished by playing back music from a play list created using iTunes® software application provided by Apple Computer, Inc., running on host computer 416 and then downloaded to portable media player 404 for subsequent playback. In this way, play lists (and any other suitable media) can be associated with exercise templates.
[0043] Portable media player 404 can also be configured to provide physiologic data to workout data service 418 via host computer 416 that can be configured to operate in any number of modes. For example, host computer 416 can operate as a conduit for providing the physiologic data to workout data service 418. Alternatively, host computer 416 can process the physiologic data and/or temporarily store the physiologic data for later forwarding such as, for example, during a temporary loss of connection between host computer 416 and service 418 via network 420. Furthermore, physiologic data can be processed at workout data service 418 in any number of ways. For example, physiologic data from one user can be processed in view of physiologic data from other users in order to compare the users in terms of performance. In another example, the physiologic data can be processed by workout data service 418 to determine a suggested template change such as changing the clues to provide motivation at a particular portion of the workout. As another example, based on play lists associated with that workout by other users, a different play list (or changes to the play list) can be suggested for a particular workout.
[0044] In addition to providing physiologic data, sensor 100 can provide indications of nearby locations of interest as shown in FIG. 5 . For example, when sensor 100 incorporates real time location technology (such as GPS), sensor 100 can periodically check for nearby points of interest (included in a DEM database in the case of a GPS enabled system) provided, in some cases, by the user and in other cases by a workout template specific for the area in which the user plans to exercise. For example, in a GPS based system, prior to a workout (or other anticipated excursion such as a hike or bike ride), the user can download a list of preferred establishments (restrooms, restaurants, etc.) to the DEM database 126 specific for the area in which the user plans to exercise (local parks, bike routes, jogging trails, etc). The downloading can be accomplished by, for example, accessing an external device (such as host computer 416 or media player unit 404) in which is stored preference file 424 that includes indicators of points of interest for the designated area. When the user approaches one of the points of interest (restaurant 426, for example) while exercising, sensor 100 can issue notification 428 that the user is within a pre-determined distance of the nearby point of interest thereby providing the user the option to stop or continue the planned excursion unabated. Moreover, the nearby point of interest (i.e., restaurant 426) can also push information 430 to the user by, for example, displaying advertisements in addition to the notification that the user is within the pre-determined distance.
[0045] FIG. 6 is a flowchart illustrating a process 600 to accomplish transfer of physiologic data between portable media player 404 and workout data service 418. At 602, a determination is made if accessory 406 is connected to portable media player 404 (which, if connected, would allow physiological data to be received by portable media player 404 from sensor 100). This determination can be accomplished by, for example, using configuration data provided to host computer 416 when portable media player 404 and host computer 416 are connected using a handshake protocol. The configuration data can include such information as device characteristics, capabilities and/or activities of portable media player 404 and so on. If it is determined at 602 that accessory 406 is not connected to portable media player 404, then process 600 ends, otherwise, at 604, a determination is made if the user has an account at workout data service 418. If it is determined that the user does have an account, then processing continues to 606, otherwise, the user is requested to open an account at 608 before going any further. If the user does not desire to open an account, then process 600 ends, otherwise, an account is opened at 610. Once an account is opened, at 606, computer 416 accesses the physiologic data, if any, stored in portable media player 404 and provides the physiologic data to workout data service 418 to be associated with the user's account. In some cases, some or all of the provided physiologic data can be retained on portable media player 404 for easy reference by the user (such as during or in preparation for a workout). For example, a portion of the physiologic data corresponding to the last few workouts can be retained in storage of portable media player 404 that can then be displayed by way of a display screen of the portable media player 404.
[0046] FIG. 7 shows a flowchart detailing a process 700 for electronically pairing a sensor and a garment in accordance with an embodiment of the invention. Process 700 begins at 702 by establishing a communication link between the garment and the sensor. The communication link can be a wireless communication link (RF, audio, etc.) or carried over a signal wire. In any case, once the communication link has been established, a determination is made at 704 if the garment is an authorized garment. By authorized it is meant that the garment has been identified for use with the sensor. For example, a clothing manufacturer may only want certain of its product line to belong to the class of garments that can electronically pair with a particular sensor. This may be due to any number of reasons, such as the garment must be specifically fabricated to be able to work with the sensor and therefore, not every garment would be suitable, or the manufacturer may only want those garments in a certain price range to be paired with the sensor.
[0047] If the garment is not authorized, then in one embodiment, an option can be provided at 706 for authorizing the garment by, for example, updating a list of authorized garment information to include the garment information of the unauthorized garment. This is particularly useful in those situations where, for example, a manufacturer wishes to update a product line that was heretofore has not been authorized to be used with the sensor. On the other hand, if the garment is authorized, then at 710 a determination is made if the sensor is an authenticated sensor. By authenticated it is meant that the sensor has been certified for use with the garment (or class of garments) that have been designed for use with the sensor. By assuring that only authenticated sensors are electronically paired with the garment, the likelihood that a stolen, lost, or otherwise compromised sensor can be used is substantially reduced. If the sensor is determined to be authenticated, then the sensor and garment are electronically paired at 712 thereby allowing sensing data associated with the paired garment to be transmitted by the sensor to external circuitry, such as a portable computing device. In some embodiments, if the sensor not authenticated, than an option to authenticate the sensor can be provided at 714. This is useful in situations where, for example, a previously lost sensor (and therefore rendered unauthenticated) has been found.
[0048] Sensor 100 can provide performance data that can be user to improve garment performance and/or user performance. FIG. 8 shows running shoe 800 that has been electronically paired with sensor 100 in accordance with an embodiment of the invention. Shoe 800 includes applied force sensing units 802, 804, and 806 placed in shoe sole 808 at heel location Xheel, midsole location Xmidsole and toe location Xtoe each arranged to respectively sense impact force Fheel, Fmidsole, and Ftoe. Sensors 802-806 each periodically send impact force sensing data Sheel, Smidsole, and Stoe to sensor 100 most of which is then forwarded to an external computing device, such as portable media player 404 for processing. Such processing can include characterizing a user's running style in real time. For example, by comparing the relative forces of impact (Ftoe vs. Fmidsole vs. Fheel) and the temporal relationship between the occurrence of the forces of impact Ftoe, Fmidsole, and Fheel (ttoe, tmidsole, theel), a user's stride can be characterized as either a toe plant type stride (see FIGS. 9 and 10 ) or a heel plant type stride (see FIGS. 11 and 12 ) where a user's stride can be defined as an amount of time between consecutive toe, heel, or mid-sole impacts for a particular shoe. Taken over a number of strides, a user's running style profile can be developed that provides a characterization of the user's overall running style.
[0049] Since, a runner's stride and stride type can vary over the course of a run (a sprint typically uses more of a toe plant style whereas a power walker would use more of a heel plant style), a user's running style profile can also vary over the course of the run (as well as well as over the course or months or years, or as the running shoes wear, or between different, but authorized, running shoes). Therefore, in order to more accurately gauge a user's overall running style, a user's average running style can be calculated. In some cases, the user's average running style is accumulated from a number of previous runs using the same running shoe or can incorporate average running styles from different (but authorized) running shoes, if desired. In this way, a user has the ability to compare running styles and/or performance not only from one run to another, but from one running shoe to another, or merely deduce an overall running style regardless of the running shoe used.
[0050] A virtual coach can provide real time feedback to a user either during or after a run by comparing a user's running style profile to a running style profile template 1300 as illustrated in FIG. 13 . Running style template 1300 incorporates what could be considered an optimal running style profile for a particular user based upon age, gender, distances run, frequency of running, type of running (hills, intervals, flats, etc.) each modified for the particular running shoes used. By periodically comparing a user's real time running style profile to the appropriate optimal running style template, media player 404, for example, can provide real time coaching suggestions (i.e., “increase stride”, “decrease stride”, “increase toe plant”, “increase heel plant”, and so on) to the user during the run, for example, or after a run by providing a summation of user's running style and suggestions for how to modify it.
[0051] While this invention has been described in terms of a preferred embodiment, there are alterations, permutations, and equivalents that fall within the scope of this invention. It should also be noted that there are many alternative ways of implementing both the process and apparatus of the present invention. It is therefore intended that the invention be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method of electronically pairing a sensor and a garment, comprising:
establishing a bi-directional communication link between the sensor and the garment;
accessing processing resources incorporated in the garment, the processing resources being independent of the sensor and used to determine if the garment is authorized, the processing resources including memory resources, the memory resources storing information including garment identification data, backup garment performance data and back up user performance data;
using the garment identification data to determine if the garment is an authorized garment; and
electronically pairing the garment and the sensor only if the garment is authorized and the sensor is authenticated, wherein if the garment is determined to be not authorized and the sensor is determined to be authenticated, then,
authorizing the garment by a garment user inputting an appropriate authorization code to the sensor.
2. A method as recited in claim 1, further comprising:
receiving the garment performance data and the garment user performance data when the garment and the sensor are electronically paired with each other; and
using the memory resources in the garment to back up the garment performance data and the garment user performance data.
3. A method as recited in claim 1, wherein the determining if the garment is the authorized garment comprises:
receiving the garment identification information by the sensor; and
comparing the garment identification information to authorized garment identification information stored in the sensor.
4. A method as recited in claim 1, further comprising:
receiving the garment data by the sensor; and
passing the garment data to an external circuit for further processing.
5. A method as recited in claim 4, wherein the garment data includes a garment manufacture date, garment wear data, a garment wear threshold value.
6. A method as recited in claim 5 comprising:
comparing a current garment wear data value to the garment wear threshold value; and
issuing a wear notification based upon the comparison of the current garment wear data value and the garment wear threshold value.
7. A method as recited in claim 1, further comprising:
receiving user performance data by the sensor; and
passing the user performance to an external circuit for further processing.
8. A method as recited in claim 7, wherein when the garment is a shoe, then the user performance data includes stride data, force of impact data and corresponding location of impact data.
9. A method as recited in claim 8, further comprising:
calculating a user running style profile based upon the stride data, the force of impact data and the corresponding point of impact data;
comparing the user running style profile to a running style profile template; and
issuing virtual coaching instructions based upon the comparison of the user running style profile and the running style profile template.
10. A method as recited in claim 9, wherein the external circuit is a computing device arranged to process the received data.
11. A method as recited in claim 10, wherein the computing device is part of a network of computing devices.
12. A method as recited in claim 11, wherein the data is processed by at least one of the network of computing devices.
13. A method as recited in claim 12, wherein at least one of the computing devices is a personal portable computing device.
14. A computer readable storage medium embodied in a tangible form and including at least computer program code for electronically pairing a sensor and a garment, the computer readable storage medium comprising:
computer code for establishing a bi-directional communication link between the sensor and the garment;
computer code for accessing processing resources incorporated in the garment, the processing resources being independent of the sensor and used to determine if the garment is authorized, the processing resources including memory resources, the memory resources storing information including garment identification data, backup garment performance data and back up user performance data;
computer code for using the garment identification data to determine if the garment is an authorized garment; and
computer code for electronically pairing the garment and the sensor only if the garment is authorized and the sensor is authenticated, wherein if the garment is determined to be not authorized and the sensor is determined to be authenticated, then, authorizing the garment by a garment user inputting an appropriate authorization code to the sensor.
15. The computer readable storage medium as recited in claim 14, further comprising:
computer code for receiving the garment performance data and the garment user performance data when the garment and the sensor are electronically paired with each other; and
computer code for using the memory resources in the garment to back up the garment performance data and the garment user performance data.
16. The computer readable storage medium as recited in claim 15, wherein the computer code for determining if the garment is an authorized garment further comprises:
computer code for receiving the garment identification information by the sensor; and
computer code for comparing the garment identification information to authorized garment identification information stored in the sensor.
17. The computer readable storage medium as recited in claim 15, further comprising:
computer code for receiving garment data by the sensor; and
computer code for passing the garment data to an external circuit for further processing.
18. The computer readable storage medium as recited in claim 17, wherein the garment data includes a garment date of manufacture, garment wear data, a garment wear threshold value.
19. The computer readable storage medium as recited in claim 18 comprising:
computer code for comparing a current garment wear data value to the garment wear threshold value; and
computer code for issuing a wear notification based upon the comparison of the current garment wear data value and the garment wear threshold value.
20. The computer readable storage medium as recited in claim 15, further comprising:
computer code for receiving user performance data by the sensor; and
computer code for passing the user performance to an external circuit for further processing.
21. The computer readable storage medium as recited in claim 20, wherein when the garment is a shoe, then the user performance data includes stride data, force of impact data and corresponding location of impact data.
22. The computer readable storage medium as recited in claim 21, further comprising:
computer code for calculating a user running style profile based upon the stride data, the force of impact data and the corresponding point of impact data;
computer code for comparing the user running style profile to a running style profile template;
computer code for issuing virtual coaching instructions based upon the comparison of the user running style profile and the running style profile template.
23. The computer readable storage medium as recited in claim 22, wherein the external circuit is a computing device arranged to process the received data.
24. The computer readable storage medium as recited in claim 23, wherein the computing device is part of a network of computing devices.
25. The computer readable storage medium as recited in claim 24, wherein the data is processed by at least one of the network of computing devices.
26. The computer readable storage medium as recited in claim 25, wherein at least one of the computing devices is a personal portable computing device.
27. A system, comprising:
a sensor having a bi-directional communication interface; and
a garment electronically paired with the sensor only if the garment is authorized and the sensor is authenticated, wherein the sensor determines if the garment is authorized by establishing a bi-directional communication channel with the garment, retrieving garment identification data from processing resources incorporated into the garment, using the bi-directional communication channel, and comparing the identification data to a database of authorized garment identifiers, wherein if the garment is determined to be not authorized and the sensor is determined to be authenticated, then the garment is authorized by a garment user inputting an appropriate authorization code directly to the sensor that updates the database of authorized garment identifiers, wherein when the garment and the sensor are electronically paired, the sensor receives data from the processing resources incorporated into the garment and passes the data to circuit external to the sensor and the garment for further processing.
28. A system as recited in claim 27, wherein the external circuit is a portable computing device in communication with the sensor.
29. A system as recited in claim 28, wherein the data received from the garment is user performance data.
30. A system as recited in claim 29, wherein when the garment is a shoe, then the user performance data includes stride data, force of impact data and corresponding location of impact data.
31. A system as recited in claim 30, wherein the further processing comprises:
calculating a user running style profile based upon the stride data, the force of impact data and the corresponding point of impact data;
comparing the user running style profile to a running style profile template;
issuing virtual coaching instructions based upon the comparison of the user running style profile and the running style profile template.
32. A system as recited in claim 31, wherein the portable computing device is part of a network of computing devices.
33. A system as recited in claim 32, wherein the user performance data is processed by at least one of the network of computing devices.
34. A system as recited in claim 33, wherein at least one of the computing devices is a portable multimedia player.
35. An sensor capable of being electronically paired with a garment, comprising:
a processor; and
a bi-directional communication interface arranged to establish a bi-directional communication link between the sensor and the garment,
wherein the processor electronically pairs the sensor with the garment by performing at least the following operations:
establishing a communication link between the sensor and the garment using the bi-directional communication interface;
accessing processing resources incorporated in the garment, the processing resources being independent of the sensor and used to determine if the garment is authorized, the processing resources including memory resources, the memory resources storing information including garment identification data, backup garment performance data and back up user performance data;
retrieving at least some of the garment information from the garment memory resources that includes the garment identification data;
using the garment identification data to determine if the garment is an authorized garment;
electronically pairing the garment and the sensor only if the garment is authorized and the sensor is authenticated, wherein if the garment is determined to be not authorized and the sensor is determined to be authenticated, then,
authorizing the garment by a garment user inputting an appropriate authorization code to the sensor.
36. The sensor as recited in claim 35, wherein once the sensor and the garment are electronically paired, then the sensor receives garment data and user performance data.
37. The sensor as recited in claim 36, wherein the garment data and user performance data are passed by the sensor to an external circuit for further processing.
38. The sensor as recited in claim 37, wherein the external circuit is incorporated into a portable consumer electronic product.
39. The sensor as recited in claim 36, wherein the garment data includes a garment manufacture date, garment wear data, a garment wear threshold value.
40. The sensor as recited in claim 39 wherein the external circuit compares a current garment wear data value to the garment wear threshold value, and issues a wear notification based upon the comparison of the current garment wear data value and the garment wear threshold value.
41. The sensor as recited in claim 36, wherein when the garment is a shoe, then the user performance data includes stride data, force of impact data and corresponding location of impact data.
42. The sensor as recited in claim 41, wherein the external circuit further processes the user performance data by,
calculating a user running style profile based upon the stride data, the force of impact data and the corresponding point of impact data;
comparing the user running style profile to a running style profile template; and
issuing virtual coaching instructions based upon the comparison of the user running style profile and the running style profile template.
43. The sensor as recited in claim 35, wherein the processor determines if the garment is the authorized garment by comparing garment identification information received from the garment to authorized garment identification information.
Patent Citations (459)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3612265(A) | 1971-10-01 | Dickerson | Applicant |
| US3807388(A) | 1974-04-01 | Orr et al. | Applicant |
| US3918058(A) | 1975-11-01 | Noyori et al. | Applicant |
| US3958459(A) | 1976-05-01 | Shimomura | Applicant |
| US3978725(A) | 1976-09-01 | Hadtke | Applicant |
| US4089057(A) | 1978-05-01 | Eriksson | Applicant |
| US4090216(A) | 1978-05-01 | Constable | Applicant |
| US4101873(A) | 1978-07-01 | Anderson et al. | Applicant |
| US4114450(A) | 1978-09-01 | Shulman et al. | Applicant |
| US4195642(A) | 1980-04-01 | Price et al. | Applicant |
| US4210024(A) | 1980-07-01 | Ishiwatari et al. | Applicant |
| US4223211(A) | 1980-09-01 | Allsen et al. | Applicant |
| US4248244(A) | 1981-02-01 | Charnitski et al. | Applicant |
| US4317126(A) | 1982-02-01 | Gragg, Jr. | Applicant |
| US4371188(A) | 1983-02-01 | Hull | Applicant |
| US4371945(A) | 1983-02-01 | Karr et al. | Applicant |
| US4375674(A) | 1983-03-01 | Thornton | Applicant |
| US4386345(A) | 1983-05-01 | Narveson et al. | Applicant |
| US4423630(A) | 1984-01-01 | Morrison | Applicant |
| US4434801(A) | 1984-03-01 | Jiminez et al. | Applicant |
| US4451849(A) | 1984-05-01 | Fuhrer | Applicant |
| US4516110(A) | 1985-05-01 | Overmyer | Applicant |
| US4516865(A) | 1985-05-01 | Hideo | Applicant |
| US4578769(A) | 1986-03-01 | Frederick | Applicant |
| US4589022(A) | 1986-05-01 | Prince et al. | Applicant |
| US4625733(A) | 1986-12-01 | Saynajakangas | Applicant |
| US4694694(A) | 1987-09-01 | Vlakancic et al. | Applicant |
| US4699379(A) | 1987-10-01 | Chateau et al. | Applicant |
| US4703445(A) | 1987-10-01 | Dassler | Examiner |
| US4720093(A) | 1988-01-01 | Del Mar | Applicant |
| US4722222(A) | 1988-02-01 | Purdy et al. | Applicant |
| US4736312(A) | 1988-04-01 | Dassler et al. | Applicant |
| US4745564(A) | 1988-05-01 | Tennes et al. | Applicant |
| US4757453(A) | 1988-07-01 | Nasiff | Applicant |
| US4757714(A) | 1988-07-01 | Purdy et al. | Applicant |
| US4759219(A) | 1988-07-01 | Cobb et al. | Applicant |
| US4763275(A) | 1988-08-01 | Carlin | Applicant |
| US4763284(A) | 1988-08-01 | Carlin | Applicant |
| US4763287(A) | 1988-08-01 | Gerhaeuser et al. | Applicant |
| US4771394(A) | 1988-09-01 | Cavanagh | Applicant |
| US4774679(A) | 1988-09-01 | Carlin | Applicant |
| US4775948(A) | 1988-10-01 | Dial et al. | Applicant |
| US4780837(A) | 1988-10-01 | Namekawa | Applicant |
| US4821218(A) | 1989-04-01 | Potsch | Applicant |
| US4822042(A) | 1989-04-01 | Landsman | Applicant |
| US4824107(A) | 1989-04-01 | French | Applicant |
| US4829812(A) | 1989-05-01 | Parks et al. | Applicant |
| US4830021(A) | 1989-05-01 | Thornton | Applicant |
| US4862394(A) | 1989-08-01 | Thompson et al. | Applicant |
| US4862395(A) | 1989-08-01 | Fey et al. | Applicant |
| US4873867(A) | 1989-10-01 | McPherson et al. | Applicant |
| US4876500(A) | 1989-10-01 | Wu | Applicant |
| US4883271(A) | 1989-11-01 | French | Applicant |
| US4903212(A) | 1990-02-01 | Yokouchi et al. | Applicant |
| US4908523(A) | 1990-03-01 | Snowden et al. | Applicant |
| US4928307(A) | 1990-05-01 | Lynn | Applicant |
| US4935887(A) | 1990-06-01 | Abdalah et al. | Applicant |
| US4951171(A) | 1990-08-01 | Tran et al. | Applicant |
| US4955980(A) | 1990-09-01 | Masuo | Applicant |
| US5033013(A) | 1991-07-01 | Kato et al. | Applicant |
| US5036467(A) | 1991-07-01 | Blackburn et al. | Applicant |
| US5056783(A) | 1991-10-01 | Matcovich et al. | Applicant |
| US5067081(A) | 1991-11-01 | Person | Applicant |
| US5088836(A) | 1992-02-01 | Yamada et al. | Applicant |
| US5117444(A) | 1992-05-01 | Sutton et al. | Applicant |
| US5144226(A) | 1992-09-01 | Rapp | Applicant |
| US5148002(A) | 1992-09-01 | Kuo et al. | Applicant |
| US5150310(A) | 1992-09-01 | Greenspun et al. | Applicant |
| US5162828(A) | 1992-11-01 | Furness et al. | Applicant |
| US5181181(A) | 1993-01-01 | Glynn | Applicant |
| US5200827(A) | 1993-04-01 | Hanson et al. | Applicant |
| US5243993(A) | 1993-09-01 | Alexander et al. | Applicant |
| US5258927(A) | 1993-11-01 | Havriluk et al. | Applicant |
| US5295085(A) | 1994-03-01 | Hoffacker | Applicant |
| US5316249(A) | 1994-05-01 | Anderson | Applicant |
| US5324038(A) | 1994-06-01 | Sasser | Applicant |
| US5335664(A) | 1994-08-01 | Nagashima | Applicant |
| US5339699(A) | 1994-08-01 | Carignan | Applicant |
| US5343445(A) | 1994-08-01 | Cherdak | Applicant |
| US5348519(A) | 1994-09-01 | Prince et al. | Applicant |
| US5382972(A) | 1995-01-01 | Kannes | Applicant |
| US5396429(A) | 1995-03-01 | Hanchett | Applicant |
| US5406305(A) | 1995-04-01 | Shimomura et al. | Applicant |
| US5420828(A) | 1995-05-01 | Geiger | Applicant |
| US5426595(A) | 1995-06-01 | Picard | Applicant |
| US5436838(A) | 1995-07-01 | Miyamori | Applicant |
| US5446775(A) | 1995-08-01 | Wright et al. | Applicant |
| US5450329(A) | 1995-09-01 | Tanner | Applicant |
| US5452269(A) | 1995-09-01 | Cherdak | Applicant |
| US5471405(A) | 1995-11-01 | Marsh | Applicant |
| US5475725(A) | 1995-12-01 | Nakamura | Applicant |
| US5476427(A) | 1995-12-01 | Fujima | Applicant |
| US5478006(A) | 1995-12-01 | Taguchi | Applicant |
| US5485402(A) | 1996-01-01 | Smith et al. | Applicant |
| US5486815(A) | 1996-01-01 | Wagner | Applicant |
| US5509082(A) | 1996-04-01 | Toyama et al. | Applicant |
| US5513854(A) | 1996-05-01 | Daver | Applicant |
| US5524637(A) | 1996-06-01 | Erickson | Applicant |
| US5526326(A) | 1996-06-01 | Fekete et al. | Applicant |
| US5528228(A) | 1996-06-01 | Wilk | Applicant |
| US5539336(A) | 1996-07-01 | Nguyen et al. | Applicant |
| US5541604(A) | 1996-07-01 | Meier | Applicant |
| US5546307(A) | 1996-08-01 | Mazur et al. | Applicant |
| US5546974(A) | 1996-08-01 | Bireley | Applicant |
| US5559945(A) | 1996-09-01 | Beaudet et al. | Applicant |
| US5564698(A) | 1996-10-01 | Honey et al. | Applicant |
| US5574669(A) | 1996-11-01 | Marshall | Applicant |
| US5583776(A) | 1996-12-01 | Levi et al. | Applicant |
| US5583993(A) | 1996-12-01 | Foster et al. | Applicant |
| US5590908(A) | 1997-01-01 | Carr | Applicant |
| US5592401(A) | 1997-01-01 | Kramer | Applicant |
| US5605336(A) | 1997-02-01 | Gaoiran et al. | Applicant |
| US5608698(A) | 1997-03-01 | Yamanoi et al. | Applicant |
| US5615132(A) | 1997-03-01 | Horton et al. | Applicant |
| US5616876(A) | 1997-04-01 | Cluts | Applicant |
| US5617084(A) | 1997-04-01 | Sears | Applicant |
| US5617386(A) | 1997-04-01 | Choi | Applicant |
| US5618995(A) | 1997-04-01 | Otto et al. | Applicant |
| US5627548(A) | 1997-05-01 | Woo et al. | Applicant |
| US5629131(A) | 1997-05-01 | De Keyzer et al. | Applicant |
| US5633070(A) | 1997-05-01 | Murayama et al. | Applicant |
| US5636146(A) | 1997-06-01 | Flentov et al. | Applicant |
| US5646857(A) | 1997-07-01 | McBurney et al. | Applicant |
| US5670985(A) | 1997-09-01 | Cappels, Sr. et al. | Applicant |
| US5671010(A) | 1997-09-01 | Shimbo et al. | Applicant |
| US5671162(A) | 1997-09-01 | Werbin | Applicant |
| US5673691(A) | 1997-10-01 | Abrams et al. | Applicant |
| US5680102(A) | 1997-10-01 | Xydis | Applicant |
| US5684513(A) | 1997-11-01 | Decker | Applicant |
| US5688183(A) | 1997-11-01 | Sabatino et al. | Applicant |
| US5690119(A) | 1997-11-01 | Rytky et al. | Applicant |
| US5690591(A) | 1997-11-01 | Kenmochi et al. | Applicant |
| US5690773(A) | 1997-11-01 | Fidalgo et al. | Applicant |
| US5694340(A) | 1997-12-01 | Kim | Applicant |
| US5701257(A) | 1997-12-01 | Miura et al. | Applicant |
| US5710922(A) | 1998-01-01 | Alley et al. | Applicant |
| US5712638(A) | 1998-01-01 | Issa | Applicant |
| US5712949(A) | 1998-01-01 | Kato et al. | Applicant |
| US5720200(A) | 1998-02-01 | Anderson et al. | Applicant |
| US5721539(A) | 1998-02-01 | Goetzl | Applicant |
| US5721949(A) | 1998-02-01 | Smith et al. | Applicant |
| US5723786(A) | 1998-03-01 | Klapman | Applicant |
| US5724265(A) | 1998-03-01 | Hutchings | Applicant |
| US5726672(A) | 1998-03-01 | Hernandez et al. | Applicant |
| US5734337(A) | 1998-03-01 | Kupersmit | Applicant |
| US5738104(A) | 1998-04-01 | Lo et al. | Applicant |
| US5739451(A) | 1998-04-01 | Winksy et al. | Applicant |
| US5740143(A) | 1998-04-01 | Suetomi | Applicant |
| US5743269(A) | 1998-04-01 | Okigami et al. | Applicant |
| US5745037(A) | 1998-04-01 | Guthrie et al. | Applicant |
| US5749615(A) | 1998-05-01 | Itson | Applicant |
| US5761096(A) | 1998-06-01 | Zakutin | Applicant |
| US5771485(A) | 1998-06-01 | Echigo | Applicant |
| US5779576(A) | 1998-07-01 | Smith, III et al. | Applicant |
| US5781155(A) | 1998-07-01 | Woo et al. | Applicant |
| US5790477(A) | 1998-08-01 | Hauke | Applicant |
| US5807284(A) | 1998-09-01 | Foxlin | Applicant |
| US5812056(A) | 1998-09-01 | Law | Applicant |
| US5815225(A) | 1998-09-01 | Nelson | Applicant |
| US5822288(A) | 1998-10-01 | Shinada | Applicant |
| US5835721(A) | 1998-11-01 | Donahue et al. | Applicant |
| US5835732(A) | 1998-11-01 | Kikinis et al. | Applicant |
| US5862803(A) | 1999-01-01 | Besson et al. | Applicant |
| US5864868(A) | 1999-01-01 | Contois | Applicant |
| US5870710(A) | 1999-02-01 | Ozawa et al. | Applicant |
| US5886739(A) | 1999-03-01 | Winningstad | Applicant |
| US5891042(A) | 1999-04-01 | Sham et al. | Applicant |
| US5895073(A) | 1999-04-01 | Moore | Examiner |
| US5897457(A) | 1999-04-01 | Mackovjak | Applicant |
| US5899963(A) | 1999-05-01 | Hutchings | Applicant |
| US5901303(A) | 1999-05-01 | Chew | Applicant |
| US5905460(A) | 1999-05-01 | Odagiri et al. | Applicant |
| US5918281(A) | 1999-06-01 | Nabulsi | Applicant |
| US5918303(A) | 1999-06-01 | Yamaura et al. | Applicant |
| US5920728(A) | 1999-07-01 | Hallowell et al. | Applicant |
| US5923757(A) | 1999-07-01 | Hocker et al. | Applicant |
| US5925001(A) | 1999-07-01 | Hoyt et al. | Applicant |
| US5929335(A) | 1999-07-01 | Carter | Applicant |
| US5930741(A) | 1999-07-01 | Kramer | Applicant |
| US5936523(A) | 1999-08-01 | West | Applicant |
| US5946643(A) | 1999-08-01 | Zakutin | Applicant |
| US5947917(A) | 1999-09-01 | Carte et al. | Applicant |
| US5952992(A) | 1999-09-01 | Helms | Applicant |
| US5955667(A) | 1999-09-01 | Fyfe | Applicant |
| US5959568(A) | 1999-09-01 | Woolley | Applicant |
| US5960380(A) | 1999-09-01 | Flentov et al. | Applicant |
| US5963523(A) | 1999-10-01 | Kayama et al. | Applicant |
| US5963891(A) | 1999-10-01 | Walker et al. | Applicant |
| US5976083(A) | 1999-11-01 | Richardson et al. | Applicant |
| US5977877(A) | 1999-11-01 | McCulloch et al. | Applicant |
| US5978972(A) | 1999-11-01 | Stewart et al. | Applicant |
| US5984842(A) | 1999-11-01 | Chu | Applicant |
| US6002982(A) | 1999-12-01 | Fry | Applicant |
| US6006274(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6009237(A) | 1999-12-01 | Hirabayashi et al. | Applicant |
| US6009629(A) | 2000-01-01 | Gnepf et al. | Applicant |
| US6011491(A) | 2000-01-01 | Goetzl | Applicant |
| US6011585(A) | 2000-01-01 | Anderson | Applicant |
| US6013007(A) | 2000-01-01 | Root et al. | Applicant |
| US6018677(A) | 2000-01-01 | Vidrine et al. | Applicant |
| US6018705(A) | 2000-01-01 | Gaudet et al. | Applicant |
| US6020851(A) | 2000-02-01 | Busack | Applicant |
| US6028617(A) | 2000-02-01 | Sawano et al. | Applicant |
| US6028625(A) | 2000-02-01 | Cannon | Applicant |
| US6028627(A) | 2000-02-01 | Helmsderfer | Applicant |
| US6032084(A) | 2000-02-01 | Anderson et al. | Applicant |
| US6032108(A) | 2000-02-01 | Seiple et al. | Applicant |
| US6032530(A) | 2000-03-01 | Hock | Applicant |
| US6041023(A) | 2000-03-01 | Lakhansingh | Applicant |
| US6043747(A) | 2000-03-01 | Altenhofen | Applicant |
| US6045364(A) | 2000-04-01 | Dugan et al. | Applicant |
| US6052654(A) | 2000-04-01 | Gaudet et al. | Applicant |
| US6057756(A) | 2000-05-01 | Engellenner | Applicant |
| US6059576(A) | 2000-05-01 | Brann | Applicant |
| US6073086(A) | 2000-06-01 | Marinelli | Applicant |
| US6074271(A) | 2000-06-01 | Derrah | Applicant |
| US6075443(A) | 2000-06-01 | Schepps et al. | Applicant |
| US6091342(A) | 2000-07-01 | Janesch et al. | Applicant |
| US6108426(A) | 2000-08-01 | Stortz | Applicant |
| US6111541(A) | 2000-08-01 | Karmel | Applicant |
| US6111571(A) | 2000-08-01 | Summers | Applicant |
| US6122340(A) | 2000-09-01 | Darley et al. | Applicant |
| US6122959(A) | 2000-09-01 | Hoshal et al. | Applicant |
| US6122960(A) | 2000-09-01 | Hutchings et al. | Applicant |
| US6125686(A) | 2000-10-01 | Haan et al. | Applicant |
| US6127931(A) | 2000-10-01 | Mohr | Applicant |
| US6145389(A) | 2000-11-01 | Ebeling et al. | Applicant |
| US6148271(A) | 2000-11-01 | Marinelli | Applicant |
| US6151647(A) | 2000-11-01 | Sarat | Applicant |
| US6157898(A) | 2000-12-01 | Marinelli | Applicant |
| US6160254(A) | 2000-12-01 | Zimmerman et al. | Applicant |
| US6161944(A) | 2000-12-01 | Leman | Applicant |
| US6163021(A) | 2000-12-01 | Mickelson | Applicant |
| US6167356(A) | 2000-12-01 | Squadron et al. | Applicant |
| US6172948(B1) | 2001-01-01 | Keller et al. | Applicant |
| US6179432(B1) | 2001-01-01 | Zhang et al. | Applicant |
| US6183425(B1) | 2001-02-01 | Whalen et al. | Applicant |
| US6191939(B1) | 2001-02-01 | Burnett | Applicant |
| US6196932(B1) | 2001-03-01 | Marsh et al. | Applicant |
| US6204813(B1) | 2001-03-01 | Wadell et al. | Applicant |
| US6208044(B1) | 2001-03-01 | Viswanadham et al. | Applicant |
| US6216131(B1) | 2001-04-01 | Liu et al. | Applicant |
| US6217183(B1) | 2001-04-01 | Shipman | Applicant |
| US6226622(B1) | 2001-05-01 | Dabbiere | Applicant |
| US6238338(B1) | 2001-05-01 | DeLuca et al. | Applicant |
| US6245002(B1) | 2001-06-01 | Beliakov | Applicant |
| US6248946(B1) | 2001-06-01 | Dwek | Applicant |
| US6249487(B1) | 2001-06-01 | Yano et al. | Applicant |
| US6254513(B1) | 2001-07-01 | Takenaka et al. | Applicant |
| US6263279(B1) | 2001-07-01 | Bianco et al. | Applicant |
| US6266623(B1) | 2001-07-01 | Vock et al. | Applicant |
| US6295541(B1) | 2001-09-01 | Bodnar et al. | Applicant |
| US6298314(B1) | 2001-10-01 | Blackadar et al. | Applicant |
| US6305221(B1) | 2001-10-01 | Hutchings | Applicant |
| US6332175(B1) | 2001-12-01 | Birrell et al. | Applicant |
| US6336365(B1) | 2002-01-01 | Blackadar et al. | Applicant |
| US6336727(B1) | 2002-01-01 | Kim | Applicant |
| US6341316(B1) | 2002-01-01 | Kloba et al. | Applicant |
| US6356856(B1) | 2002-03-01 | Damen et al. | Applicant |
| US6357147(B1) | 2002-03-01 | Darley et al. | Applicant |
| US6360597(B1) | 2002-03-01 | Hubbard, Jr. | Applicant |
| US6377530(B1) | 2002-04-01 | Burrows | Applicant |
| US6380597(B1) | 2002-04-01 | Gudesen et al. | Applicant |
| US6385473(B1) | 2002-05-01 | Haines et al. | Applicant |
| US6436052(B1) | 2002-08-01 | Nikolic et al. | Applicant |
| US6441747(B1) | 2002-08-01 | Khair et al. | Applicant |
| US6452610(B1) | 2002-09-01 | Reinhardt et al. | Applicant |
| US6456261(B1) | 2002-09-01 | Zhang | Applicant |
| US6459881(B1) | 2002-10-01 | Hoder et al. | Applicant |
| US6467924(B2) | 2002-10-01 | Shipman | Applicant |
| US6493652(B1) | 2002-12-01 | Ohlenbusch et al. | Applicant |
| US6498994(B2) | 2002-12-01 | Vock et al. | Applicant |
| US6501393(B1) | 2002-12-01 | Richards et al. | Applicant |
| US6504483(B1) | 2003-01-01 | Richards et al. | Applicant |
| US6516284(B2) | 2003-02-01 | Flentov et al. | Applicant |
| US6527711(B1) | 2003-03-01 | Stivoric et al. | Applicant |
| US6529131(B2) | 2003-03-01 | Wentworth | Applicant |
| US6531982(B1) | 2003-03-01 | White et al. | Applicant |
| US6536139(B2) | 2003-03-01 | Darley et al. | Applicant |
| US6539336(B1) | 2003-03-01 | Vock et al. | Applicant |
| US6549497(B2) | 2003-04-01 | Miyamoto et al. | Applicant |
| US6560903(B1) | 2003-05-01 | Darley | Applicant |
| US6563417(B1) | 2003-05-01 | Shaw | Applicant |
| US6570526(B1) | 2003-05-01 | Noller et al. | Applicant |
| US6587403(B1) | 2003-07-01 | Keller et al. | Applicant |
| US6587404(B1) | 2003-07-01 | Keller et al. | Applicant |
| US6595929(B2) | 2003-07-01 | Stivoric et al. | Applicant |
| US6600418(B2) | 2003-07-01 | Sainati et al. | Applicant |
| US6605038(B1) | 2003-08-01 | Teller et al. | Applicant |
| US6611782(B1) | 2003-08-01 | Wooster et al. | Applicant |
| US6611789(B1) | 2003-08-01 | Darley | Examiner |
| US6617962(B1) | 2003-09-01 | Horwitz et al. | Applicant |
| US6619835(B2) | 2003-09-01 | Kita | Applicant |
| US6621768(B1) | 2003-09-01 | Keller et al. | Applicant |
| US6623427(B2) | 2003-09-01 | Mandigo | Applicant |
| US6633743(B1) | 2003-10-01 | Berlinsky | Applicant |
| US6643608(B1) | 2003-11-01 | Hershey et al. | Applicant |
| US6714121(B1) | 2004-03-01 | Moore | Applicant |
| US6731312(B2) | 2004-05-01 | Robbin | Applicant |
| US6735630(B1) | 2004-05-01 | Gelvin et al. | Applicant |
| US6748902(B1) | 2004-06-01 | Boesch et al. | Applicant |
| US6760536(B1) | 2004-07-01 | Amir et al. | Applicant |
| US6762741(B2) | 2004-07-01 | Weindorf | Applicant |
| US6772331(B1) | 2004-08-01 | Hind et al. | Applicant |
| US6794566(B2) | 2004-09-01 | Pachet | Applicant |
| US6799226(B1) | 2004-09-01 | Robbin et al. | Applicant |
| US6801964(B1) | 2004-10-01 | Mahdavi | Applicant |
| US6813586(B1) | 2004-11-01 | Vock et al. | Applicant |
| US6825777(B2) | 2004-11-01 | Vock et al. | Applicant |
| US6837827(B1) | 2005-01-01 | Lee et al. | Applicant |
| US6856934(B2) | 2005-02-01 | Vock et al. | Applicant |
| US6870529(B1) | 2005-03-01 | Davis | Applicant |
| US6871063(B1) | 2005-03-01 | Schiffer | Applicant |
| US6876947(B1) | 2005-04-01 | Darley et al. | Applicant |
| US6882955(B1) | 2005-04-01 | Ohlenbusch et al. | Applicant |
| US6883694(B2) | 2005-04-01 | Abelow | Applicant |
| US6885971(B2) | 2005-04-01 | Vock et al. | Applicant |
| US6898550(B1) | 2005-05-01 | Blackadar et al. | Applicant |
| US6900732(B2) | 2005-05-01 | Richards | Applicant |
| US6911971(B2) | 2005-06-01 | Suzuki et al. | Applicant |
| US6914551(B2) | 2005-07-01 | Vidal | Applicant |
| US6918677(B2) | 2005-07-01 | Shipman | Applicant |
| US6934812(B1) | 2005-08-01 | Robbin et al. | Applicant |
| US6950087(B2) | 2005-09-01 | Knox et al. | Applicant |
| US6959259(B2) | 2005-10-01 | Vock et al. | Applicant |
| US7009517(B2) | 2006-03-01 | Wood | Applicant |
| US7042360(B2) | 2006-05-01 | Light et al. | Applicant |
| US7046230(B2) | 2006-05-01 | Zadesky | Applicant |
| US7054784(B2) | 2006-05-01 | Flentov et al. | Applicant |
| US7062225(B2) | 2006-06-01 | White | Applicant |
| US7064669(B2) | 2006-06-01 | Light et al. | Applicant |
| US7072789(B2) | 2006-07-01 | Vock et al. | Applicant |
| US7084856(B2) | 2006-08-01 | Huppi | Applicant |
| US7084921(B1) | 2006-08-01 | Ogawa | Applicant |
| US7092846(B2) | 2006-08-01 | Vock et al. | Applicant |
| US7146437(B2) | 2006-12-01 | Robbin et al. | Applicant |
| US7174130(B2) | 2007-02-01 | Kurisko et al. | Applicant |
| US7174277(B2) | 2007-02-01 | Vock et al. | Applicant |
| US7234026(B2) | 2007-06-01 | Robbin et al. | Applicant |
| US7254516(B2) | 2007-08-01 | Case et al. | Applicant |
| US2001/0022828(A1) | 2001-09-01 | Pyles | Applicant |
| US2001/0033244(A1) | 2001-10-01 | Harris et al. | Applicant |
| US2001/0041021(A1) | 2001-11-01 | Boyle et al. | Applicant |
| US2001/0042107(A1) | 2001-11-01 | Palm | Applicant |
| US2001/0049890(A1) | 2001-12-01 | Hirsch et al. | Examiner |
| US2002/0002413(A1) | 2002-01-01 | Tokue | Applicant |
| US2002/0013784(A1) | 2002-01-01 | Swanson | Applicant |
| US2002/0022551(A1) | 2002-02-01 | Watterson et al. | Applicant |
| US2002/0045961(A1) | 2002-04-01 | Gibbs et al. | Applicant |
| US2002/0046315(A1) | 2002-04-01 | Miller et al. | Applicant |
| US2002/0055934(A1) | 2002-05-01 | Lipscomb et al. | Applicant |
| US2002/0090912(A1) | 2002-07-01 | Cannon et al. | Applicant |
| US2002/0116082(A1) | 2002-08-01 | Gudorf | Applicant |
| US2002/0152045(A1) | 2002-10-01 | Dowling et al. | Applicant |
| US2002/0161865(A1) | 2002-10-01 | Nguyen | Applicant |
| US2002/0173273(A1) | 2002-11-01 | Spurgat et al. | Applicant |
| US2002/0189426(A1) | 2002-12-01 | Hirade et al. | Applicant |
| US2003/0016844(A1) | 2003-01-01 | Numaoka | Examiner |
| US2003/0037254(A1) | 2003-02-01 | Fischer et al. | Applicant |
| US2003/0046434(A1) | 2003-03-01 | Flanagin et al. | Applicant |
| US2003/0065805(A1) | 2003-04-01 | Barnes, Jr. | Applicant |
| US2003/0074457(A1) | 2003-04-01 | Kluth | Applicant |
| US2003/0076301(A1) | 2003-04-01 | Tsuk et al. | Applicant |
| US2003/0079038(A1) | 2003-04-01 | Robbin et al. | Applicant |
| US2003/0095096(A1) | 2003-05-01 | Robbin et al. | Applicant |
| US2003/0097379(A1) | 2003-05-01 | Ireton | Applicant |
| US2003/0133694(A1) | 2003-07-01 | Yeo | Applicant |
| US2003/0163287(A1) | 2003-08-01 | Vock et al. | Applicant |
| US2003/0167318(A1) | 2003-09-01 | Robbin et al. | Applicant |
| US2003/0229490(A1) | 2003-12-01 | Etter | Applicant |
| US2004/0001395(A1) | 2004-01-01 | Keller et al. | Applicant |
| US2004/0001396(A1) | 2004-01-01 | Keller et al. | Applicant |
| US2004/0012556(A1) | 2004-01-01 | Yong et al. | Applicant |
| US2004/0055446(A1) | 2004-03-01 | Robbin et al. | Applicant |
| US2004/0069122(A1) | 2004-04-01 | Wilson | Applicant |
| US2004/0076086(A1) | 2004-04-01 | Keller et al. | Applicant |
| US2004/0086120(A1) | 2004-05-01 | Akins, III et al. | Applicant |
| US2004/0094018(A1) | 2004-05-01 | Ueshima et al. | Applicant |
| US2004/0104845(A1) | 2004-06-01 | McCarthy | Applicant |
| US2004/0198436(A1) | 2004-10-01 | Alden | Applicant |
| US2004/0224638(A1) | 2004-11-01 | Fadell et al. | Applicant |
| US2004/0267825(A1) | 2004-12-01 | Novak et al. | Applicant |
| US2005/0015254(A1) | 2005-01-01 | Beaman | Applicant |
| US2005/0027910(A1) | 2005-02-01 | Barrett, Jr. et al. | Applicant |
| US2005/0080566(A1) | 2005-04-01 | Vock et al. | Applicant |
| US2005/0088275(A1) | 2005-04-01 | Valoteau et al. | Applicant |
| US2005/0166153(A1) | 2005-07-01 | Eytchison et al. | Applicant |
| US2005/5152294 | 2005-07-01 | Yu et al. | Applicant |
| US2005/0177929(A1) | 2005-08-01 | Greenwald et al. | Applicant |
| US2005/0245839(A1) | 2005-11-01 | Stivoric et al. | Applicant |
| US2005/0266798(A1) | 2005-12-01 | Moloney et al. | Applicant |
| US2005/0266961(A1) | 2005-12-01 | Shum et al. | Applicant |
| US2006/0013414(A1) | 2006-01-01 | Shih | Applicant |
| US2006/0068760(A1) | 2006-03-01 | Hameed et al. | Applicant |
| US2006/0097847(A1) | 2006-05-01 | Bervoets et al. | Applicant |
| US2006/0152377(A1) | 2006-07-01 | Beebe et al. | Applicant |
| US2006/0190577(A1) | 2006-08-01 | Yamada | Applicant |
| US2006/0221788(A1) | 2006-10-01 | Lindahl et al. | Applicant |
| US2006/0265503(A1) | 2006-11-01 | Jones et al. | Applicant |
| US2007/0011919(A1) | 2007-01-01 | Case | Examiner |
| US2007/0021269(A1) | 2007-01-01 | Shum | Applicant |
| US2007/0028009(A1) | 2007-02-01 | Robbin et al. | Applicant |
| US2007/0032195(A1) | 2007-02-01 | Kurisko et al. | Applicant |
| US2007/0124679(A1) | 2007-05-01 | Jeong et al. | Applicant |
| US2008/0125288(A1) | 2008-05-01 | Case | Examiner |
| DE4334773(A1) | 1994-04-01 | Applicant | |
| DE4445023(A1) | 1996-06-01 | Applicant | |
| DE10325805 | 2005-01-01 | Applicant | |
| EP127139 | 1984-05-01 | Applicant | |
| EP336782(A2) | 1989-10-01 | Applicant | |
| EP578604 | 1994-01-01 | Applicant | |
| EP757437 | 1997-02-01 | Applicant | |
| EP863469 | 1998-09-01 | Applicant | |
| EP917077 | 1999-05-01 | Applicant | |
| EP917893(B1) | 1999-05-01 | Applicant | |
| EP982732 | 2000-03-01 | Applicant | |
| EP1028425 | 2000-08-01 | Applicant | |
| EP1028426(A2) | 2000-08-01 | Applicant | |
| EP1076302 | 2001-02-01 | Applicant | |
| EP1289197 | 2003-03-01 | Applicant | |
| EP1455477 | 2004-09-01 | Applicant | |
| EP1536612 | 2005-06-01 | Applicant | |
| EP1566948 | 2005-08-01 | Applicant | |
| GB1567238 | 1980-05-01 | Applicant | |
| GB2137363 | 1984-10-01 | Applicant | |
| GB2384399 | 2003-07-01 | Applicant | |
| JP59-023610 | 1984-02-01 | Applicant | |
| JP3-152469 | 1991-06-01 | Applicant | |
| JP2000122044 | 2000-04-01 | Applicant | |
| JP2000-224099 | 2000-08-01 | Applicant | |
| JP2000-299834 | 2000-10-01 | Applicant | |
| JP2001-312338 | 2001-11-01 | Applicant | |
| JP2001321202 | 2001-11-01 | Applicant | |
| JP2002-076977 | 2002-03-01 | Applicant | |
| JP2002101908 | 2002-04-01 | Applicant | |
| WO95/16950 | 1995-06-01 | Applicant | |
| WO98/17032 | 1998-04-01 | Applicant | |
| WO98/06466 | 1998-12-01 | Applicant | |
| WO98/54581 | 1998-12-01 | Applicant | |
| WO/22820 | 2000-04-01 | Applicant | |
| WO/51259 | 2000-08-01 | Applicant | |
| WO/78170 | 2000-12-01 | Applicant | |
| WO1/01706(A1) | 2001-04-01 | Applicant | |
| WO1/33569 | 2001-05-01 | Applicant | |
| WO1/65413 | 2001-09-01 | Applicant | |
| WO1/67753 | 2001-09-01 | Applicant | |
| WO2/25610 | 2002-03-01 | Applicant | |
| WO3/023786 | 2003-03-01 | Applicant | |
| WO3/067202 | 2003-08-01 | Applicant | |
| WO2004/061850(A1) | 2004-07-01 | Applicant | |
| WO2004/055637 | 2004-07-01 | Applicant | |
| WO2004/084413(A2) | 2004-09-01 | Applicant | |
| WO2005/031737 | 2005-04-01 | Applicant | |
| WO2005/048644 | 2005-05-01 | Applicant | |
| WO2005/008505 | 2005-07-01 | Applicant | |
| WO2005/109781 | 2005-11-01 | Applicant | |
| WO2006071364 | 2006-06-01 | Applicant | |
| WO2006/094380 | 2006-09-01 | Applicant | |
| WO2007/022421 | 2007-02-01 | Applicant |
Non-Patent Literature (298)
- “Apple Announces iTunes 2,” Press Release, Apple Computer, Inc., Oct. 23, 2001.Applicant
- “Apple Introduces iTunes—World's Best and Easiest to Use Jukebox Software,” Macworld Expo, San Francisco, Jan. 9, 2001.Applicant
- “Apple's iPod Available in Stores Tomorrow,” Press Release, Apple Computer, Inc., Nov. 9, 2001.Applicant
- “Nomad Jukebox,” User Guide, Creative Technology Ltd., Version 1, Aug. 2000.Applicant
- “SoundJam MP Plus Manual, version 2.0” —MP3 Player and Encoder for Macintosh by Jeffrey Robbin, Bill Kincaid and Dave Heller, manual by Tom Negrino, published by Casady & Greene, Inc., 2000.Applicant
- “12.1” 925 Candela Mobile PC, downloaded from LCDHardware.com on Dec. 19, 2002, http://www.1cdharware.com/pane1/12—1—panel/default.asp.Applicant
- “BL82 Series Backlit Keyboards”, www.tg3electronics.corn/products/backlit/backlit.htm, downloaded Dec. 19, 2002.Applicant
- “Bluetooth PC Headsets—Enjoy Wireless VoIP Conversations: ‘Connecting’ Your Bluetooth Headset With Your Computer”, Bluetooth PC Headsets; downloaded on Apr. 29, 2006 from http://www.bluetoothpcheadsets.com/connect.htm.Applicant
- “Creative MuVo TX 256 MB,” T3 Magazine, Aug. 17, 2004, http://www.t3.co.uk/reviews/entertainment/mp3—player/creativemuvo—tx—256mb [downloaded Jun. 6, 2006].Applicant
- “Digital Still Cameras—Downloading Images to a Computer,” Mimi Chakarova et al., Multi-Media Reporting and Convergence, 2 pgs.Applicant
- “Eluminx Illuminated Keyboard”, downloaded Dec. 19, 2002, http://www.elumix.com/.Applicant
- “How to Pair a Bluetooth Headset & Cell Phone”, About.com; downloaded on Apr. 29, 2006 from http://mobileoffice.about.com/od/usingyourphone/ht/blueheadset—p.htm.Applicant
- “Peripherals for Industrial Keyboards & Pointing Devices”, Stealth Computer Corporation, downloaded on Dec. 19, 2002, http://www.stealthcomputer.com/peropherals—oem.htm.Applicant
- “Poly-Optical Fiber Optic Membrane Switch Backlighting”, downloaded Dec. 19, 2002, http://www.poly-optical.com/membrane—switches.html.Applicant
- “Public Safety Technologies Tracer 2000 Computer”, downloaded Dec. 19, 2002, http://www.pst911.com/traver.html.Applicant
- “QuickTime Movie Playback Programming Guide”, Apple Computer, Inc., Aug. 11, 2005.Applicant
- “QuickTime Overview”, Apple Computer, Inc., Aug. 11, 2005.Applicant
- “Rocky Matrix Backlit Keyboard”, downloaded Dec. 19, 2002, http://www.amrel.com/asi—matrixkeyboard.html.Applicant
- “Sony Ericsson to introduce Auto pairing to improve Bluetooth connectivity between headsets and phones”, Sep. 28, 2005 Press Release, Sony Ericsson Corporate; downloaded on Apr. 29, 2006 from http://www.sonyericsson.com/spg.jsp?cc=global&1c=en&ver=4001&template=pc3—1—1&z . . .Applicant
- “Taos, Inc., Announces industry's First Ambient Light Sensor to Convert Light Intensity to Digital Signals”, www.taosinc.com/pressrelease—090902.htm, downloaded Jan. 23, 2003.Applicant
- “Toughbook 28: Powerful, Rugged and Wireless”, Panasonic: Toughbook Models, downloaded Dec. 19, 2002, http:www.panasonic.com/computer/notebook/html/01a—s8.htm.Applicant
- “When it Comes to Selecting a Projection TV, Toshiba Makes Everything Perfectly Clear, Previews of New Releases”, www.bestbuy.com/HomeAudioVideo/Specials/ToshibaTVFeatures.asp, downloaded Jan. 23, 2003.Applicant
- “WhyBuy: Think Pad”, IBM ThinkPad Web Page Ease of Use, downloaded on Dec. 19, 2002, http://www.pc.ibm.com/us/thinkpad/easeofuse.html.Applicant
- 512MB Waterproof MP3 Player with FM Radio & Built-in Pedometer, Oregon Scientific, downloaded on Jul. 31, 2006 from http://www2.oregonscientific.com/shop/product.asp?cid=4&scid=11&pid=581.Applicant
- Adam C. Engst, “SoundJam Keeps on Jarmmin'” Jun. 19, 2000, http://db.tidbits.com/getbits.acgi?tbart=05988.Applicant
- Alex Veiga, “AT&T Wireless Launching Music Service,” Yahoo! Finance, Oct. 5, 2004, pp. 1-2.Applicant
- Andrew Birrell, “Personal Jukebox (PJB),” Oct. 13, 2000, http://birrell.org/andrew/talks/pjb-overview.ppt.Applicant
- Apple iPod Technical Specifications, iPod 20GB and 60GB Mac+PC, downloaded from http://www.apple.com/ipod/color/specs.html on Aug. 8, 2005.Applicant
- Bociurkiw, Michael, “Product Guide: Vanessa Matz,”, www.forbes.com/asap/2000/1127/vmartz—print.html, Nov. 27, 2000.Applicant
- Compaq, “Personal Jukebox,” Jan. 24, 2001, http://research.compaq.com/SRC/pjb/.Applicant
- Creative: “Creative NOmAD MuVo TX,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024175952/www.creative.com/products/pfriendly.asp?product=9672 [downloaded Jun. 6, 2006].Applicant
- Creative: “Creative NOMAD MuVo,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024075901/www.creative.com/products/product.asp?category=213&subcategory=215&product=110 [downloaded Jun. 7, 2006].Applicant
- Creative: “MP3 Player,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024074823/www.creative.com/products/product.asp?category=213&subcategory=216&product=4983 [downloaded Jun. 7, 2006].Applicant
- De Herrera, Chris, “Microsoft ActiveSync 3.1,” Version 1.02, Oct. 13, 2000.Applicant
- iAP Sports Lingo 0x09 Protocol V1.00, May 1, 2006.Applicant
- IEEE 1394—Wikipedia, 1995, littp://www.wikipedia.org/wiki/Firewire.Applicant
- Written Opinion of the International Searching Authority dated Nov. 24, 2006 in PCT Application No. PCT/US2005/046797.Applicant
- International Search Report dated Feb. 4, 2003 in corresponding application No. PCT/US2002/033330.Applicant
- International Search Report dated Jul. 10, 2007 in corresponding application No. PCT/US2006/048738.Applicant
- International Search Report dated Apr. 5, 2006 from corresponding International Application No. PCT/US2005/038819.Applicant
- International Search Report dated Jul. 2, 2007 in related case PCT/US2006/048669.Applicant
- International Search Report dated Jun. 19, 2007 in related Application PCT/US2006/048753.Applicant
- International Search Report dated May 21, 2007 from corresponding PCT Application No. PCT/US2006/048670.Applicant
- International Search Report in corresponding European Application No. 06256215.2 dated Feb. 20, 2007.Applicant
- Invitation to Pay Additional Fees and Partial Search Report for corresponding PCT Application No. PCT/US2005/046797 dated Jul. 3, 2006.Applicant
- iTunes 2, Playlist Related Help Screens, iTunes v2.0, Apple Computer, Inc., Oct. 23, 2001.Applicant
- iTunes, Playlist Related Help Screens, iTunes v1.0, Apple Computer, Inc., Jan. 2001.Applicant
- Jabra Bluetooth Headset User Manual; GN Netcom A/s, 2005.Applicant
- Jabra Bluetooth Introduction; GN Netcom A/S, Oct. 2004.Applicant
- Jabra FreeSpeak BT200 User Manual; Jabra Corporation, 2002.Applicant
- Kennedy, “Digital Data Storage Using Video Disc,” IBM Technical Disclosure Bulletin, vol. 24, No. 2, Jul. 1981.Applicant
- Miniman, “Applian Software's Replay Radio and Player v1.02,” Product review, pocketnow.com, http://www.pocketnow.com/reviews/replay/replay.htm, Jul. 31, 2001.Applicant
- Musicinatch, “Musicmatch and Xing Technology Introduce Musicrnatch Jukebox,” May 18, 1998, http://www.musicmatch.com/info/companylpress/releases/?year=1998&release=2.Applicant
- Nonhoff-Arps, et al., “Straβenmusik Portable MP3-Spieler mit USB-Anschluss,” CT Magazin Fuer Computer Technik, Verlag Heinz Heise GMBH, Hannover DE, No. 25, Dec. 4, 2000.Applicant
- International Search Report dated Nov. 24, 2006 in PCT Application No. PCT/US2005/046797.Applicant
- Personal Jukebox (PJB), “Systems Research Center and PAAD,” Compaq Computer Corp., Oct. 13, 2000, http://research.compaq.com/SRC/pjb/.Applicant
- Peter Lewis, “Two New Ways to Buy Your Bits,” CNN Money, Dec. 31, 2003, pp. 1-4.Applicant
- Sastry, Ravindra Wadali. “A Need for Speed: A New Speedometer for Runners”, submitted to the Department of Electrical Engineering and Computer Science at the Massachusetts Institute of Technology, May 28, 1999.Applicant
- Sinitsyn, Alexander. “A Synchronization Framework for Personal Mobile Servers,” Pervasice Computing and Communications Workshops, 2004. Proceedings of the Second IEEE Annual Conference on, Piscataway, NJ, USA, IEEE, Mar. 14, 2004, pp. 208-212.Applicant
- SoundJam MP Plus, Representative Screens, published by Casady & Greene, Inc., Salinas, CA, 2000.Applicant
- Specification Sheet, iTunes 2, Apple Computer, Inc., Oct. 31, 2001.Applicant
- Spiller, Karen. “Low—decibel earbuds keep noise at a reasonable level”, The Telegraph Online, dated Aug. 13, 2006, http://www.nashuatelegraph.com/apps/pbcs.d11/article?Date=20060813&Cate . . . Downloaded Aug. 16, 2006.Applicant
- Steinberg, “Sonicblue Rio Car,” Product Review, Dec. 12, 2000, http://electronics.cnet.com/electronics/0-6342420-1304-4098389.html.Applicant
- Travis Butler, “Archos Jukebox 6000 Challenges Nomad Jukebox,” Augus 13, 2001, http://db.tidbits.com/getbits.acgi?tbart=(06521.Applicant
- Travis Butler, “Portable MP3: The Nomad Jukebox,” Jan. 8, 2001, http://db.tidbits.com/getbits.acgi?tbart=06261.Applicant
- U.S. Appl. No. 11/621,541, “Personalized Podcasting Podmapping” filed Jan. 9, 2007.Applicant
- Waterproof Music Player with FM Radio and Pedometer User Manual, Oregon Scientific, 2005.Applicant
- U.S. Appl. No. 10/125,893, filed Apr. 18, 2002 and titled “Power Adapters for Powering and/or Charging Peripheral Devices.”.Applicant
- International Search Report dated Dec. 5, 2007 in PCT Application No. PCT/US2007/004810.Applicant
- Written Opinion dated Dec. 5, 2007 in PCT Application No. PCT/US2007/004810.Applicant
- Partial Search Report dated Sep. 6, 2007 in PCT Application No. PCT/US2007/004810.Applicant
- International Search Report dated Dec. 6, 2007 in PCT Application No. PCT/US2007/010888.Applicant
- Written Opinion dated Dec. 6, 2007 in PCT Application No. PCT/US2007/010888.Applicant
- Apple iTunes Smart Playlists, downloaded Apr. 5, 2005 from http://web.archive.org/web/20031002011316/www.apple.com/itunes/smartplaylists...pp. 1-2.Applicant
- Hart-Daves, Guy, “How to Do Everything with Your IPod & Mini IPod Mini”, 2004, McGraw-Hill Professional, p. 33.Applicant
- International Search Report in Patent Application No. PCT/US2006/048738 dated Jan. 29, 2008.Applicant
- International Search Report in Patent Application No. PCT/US2007/077020 dated Jan. 28, 2008.Applicant
- International Search Report in Patent Application No. PCT/US2007/076889 dated Jan. 28, 2008.Applicant
- iTunes, Wikipedia, the free encyclopedia; downloaded on Oct. 5, 2005, pp. 1-6.Applicant
- Nutzel et al., “Sharing Systems for Future HiFi Systems”, The Computer Society, Jun. 2004.Applicant
- Office Action Dated Feb. 1, 2008 in U.S. Appl. No. 11/327,544.Applicant
- Office Action Dated Feb. 4, 2008 in U.S. Appl. No. 11/566,072.Applicant
- Written Opinion in Patent Application No. PCT/US2006/048738 dated Jan. 29, 2008.Applicant
- Written Opinion in Patent Application No. PCT/US2007/076889 dated Jan. 28, 2008.Applicant
- Written Opinion in Patent Application No. PCT/US2007/077020 dated Jan. 28, 2008.Applicant
- Partial Search Report and Invitation to Pay Fees dated Apr. 8, 2008 in PCT Application No. PCT/US2007/012033.Applicant
- EP98928854.3 Supplementary Search Report Feb. 18, 2002.Applicant
- EP989288543 Supplementary European Search Report; Feb. 18, 2002.Applicant
- PCT/US98/11268 International Search Report mailed Jan. 11, 1999.Applicant
- PCT/US00/18237 International Search Report; Oct. 17, 2000.Applicant
- PCT/US01/51620 International Search Report mailed Sep. 25, 2002.Applicant
- PCT/US00/18237 International Preliminary Examination Report; Sep. 11, 2003.Applicant
- Civil Action No. 05-CV-02323; Complaint, Nov. 16, 2005.Applicant
- Civil Action No. 06-CV-01100-WDM-PAC, Complaint, Jun. 8, 2000.Applicant
- Civil Action No. 06-CV-01100-WDM-PAC, Defendants Polar Electro Inc.'s And Polar Electro Oy's Answer And Affirmative Defenses: Polar Electro Inc.'Counterclaim and Demand For Jury Trial, Jun. 29, 2006.Applicant
- Civil Action No. 06-CV-01447-MSK-BNB, Complaint, Jul. 26, 2006.Applicant
- Civil Action No. 06-Cv-01447 MSK-BNB, First Amended Complaint; Aug. 16, 2006.Applicant
- Civil Action No. 06-CV-01447-MSK-BNB, Answer, Affirmative Defenses, Counterclaim, And Demand For Jury Trial, Garmin; Sep. 26, 2006.Applicant
- Civil Action No. 06-CV-01447-MSK-BNB; Garmin Disclosure Statement; Sep. 26, 2006.Applicant
- Civil Action No. 06-CV-01447 MSK-BNB, Answer, Affirmative Defenses, Counterclaims and Demand for Jury Trial, Timex; Sep. 26, 2006.Applicant
- Civil Action No. 06-CV-01447-MSk-BNB; Timex Disclosure Statement; Sep. 26, 2006.Applicant
- Civil Action No. 06-CV-01447-MSK-BNB: PhatRat Technology, Inc.'s Supplemental Answers and Objections to Defendant, Timex Corporation's Interrogatories Nos. 1, 2, 5, 7-11, 13 and 15; Feb. 12, 2007.Applicant
- Civil Action No. 06-CV-02122-REB-MJW, Complaint, Oct. 24, 2006.Applicant
- Civil Action No. 06-CV-02122-REB-MJW, Apple Computer, Inc.'s Answer to Complaint and Counterclaims, Jan. 22, 2007.Applicant
- Civil Action No. 07-CV-00078-MSK-BNB, Complaint, Jan. 12, 2007.Applicant
- Civil Action No. 07-Cv-00078-MSK-BNB, Answer, Feb. 9, 2007.Applicant
- Civil Action No. 07-CV-00238-REB-PAC, Complaint, Mar. 19, 2007.Applicant
- Civil Action No. 07-CV-00238-REB, Apple Inc.'s Answer to Complaint, Counterclaims and Jury Demand, Mar. 19, 2007.Applicant
- Civil Action No. 07-CV-00238; Nike Inc.'s Answer, Affirmative Defenses to First Complaint, Mar. 19, 2007.Applicant
- U.S. Appl. No. 08/764,758, Office Action mailed Aug. 21, 1997.Applicant
- U.S. Appl. No. 08/764,758, Response to Office Action mailed Aug. 21, 1997.Applicant
- U.S. Appl. No. 08/764,758, Office Action mailed Dec. 15, 1998.Applicant
- U.S. Appl. No. 08/764,758, Response to Office Action mailed Dec. 15, 1998.Applicant
- U.S. Appl. No. 08/764,758, Office Action mailed May 8, 1998.Applicant
- U.S. Appl. No. 08/764,758, Response to Office Action mailed May 8, 1998, filed Oct. 8, 1998.Applicant
- U.S. Appl. No. 08/764,758, Notice of Allowance mailed Jun. 1, 1999.Applicant
- U.S. Appl. No. 08/764,758, Advisory Action mailed Apr. 29, 1999.Applicant
- U.S. Appl. No. 08/867,083, Office Action mailed Apr. 8, 1999.Applicant
- U.S. Appl. No. 08/764,758, Rule 116 Amendment filed Apr. 8, 1999.Applicant
- U.S. Appl. No. 08/764,758, Rule 116 Amendment filed May 13, 1999.Applicant
- U.S. Appl. No. 08/867,083, Response to Office Action mailed Apr. 8, 1999.Applicant
- U.S. Appl. No. 08/867,083, Supp. Response to Office Action mailed Apr. 8, 1999.Applicant
- U.S. Appl. No. 08/867,083, Final Office Action mailed Jan. 3, 2000.Applicant
- U.S. Appl. No. 08/867,083, Notice of Appeal mailed Jan. 3, 2000.Applicant
- U.S. Appl. No. 08/867,083, Notice of Appeal Response to Office Action mailed Jan. 3, 2000.Applicant
- U.S. Appl. No. 08/867,083, Advisory Action mailed Mar. 14, 2000.Applicant
- U.S. Appl. No. 08/867,083 Office Action mailed Jun. 26, 2000.Applicant
- U.S. Appl. No. 08/867,083 Amendment response to Office Action mailed Jun. 26, 2000.Applicant
- U.S. Appl. No. 08/867,083 Notice of Allowance, mailed Feb. 6, 2001.Applicant
- U.S. Appl. No. 09/089,232, Information Disclosure Statement mailed Oct. 23, 1998.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed Nov. 27, 1998.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed May 30, 2000.Applicant
- U.S. Appl. No. 09/089,232, Preliminary Amendment response to Office Action mailed May 30, 2000.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed Dec. 19, 2000.Applicant
- U.S. Appl. No. 09/089,232, Response to Office Action mailed Dec. 19, 2000.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed Aug. 8, 2001.Applicant
- U.S. Appl. No. 09/089,232, Notice of Appeal mailed Nov. 5, 2001.Applicant
- U.S. Appl. No. 09/089,232, Notice of Appeal mailed Nov. 7, 2001.Applicant
- U.S. Appl. No. 09/089,232, Appeal Brief mailed Jan. 2, 2002.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed Apr. 26, 2002.Applicant
- U.S. Appl. No. 09/089,232, Appeal Brief mailed Jul. 26, 2002.Applicant
- U.S. Appl. No. 09/089,232, Notice of Allowance mailed Oct. 2, 2002.Applicant
- U.S. Appl. No. 09/089,232, Conunents on Allowance mailed Oct. 16, 2002.Applicant
- U.S. Appl. No. 09/089,232, Office Action mailed Jan. 27, 2003.Applicant
- U.S. Appl. No. 09/698,659, Office Action mailed Mar. 19, 2002.Applicant
- U.S. Appl. No. 09/698,659, Response to Office Action of Mar. 19, 2002.Applicant
- U.S. Appl. No. 09/698,659, Office Action mailed Nov. 21, 2002.Applicant
- U.S. Appl. No. 09/698,659, Response to Office Action of Nov. 21, 2002.Applicant
- U.S. Appl. No. 09/698,659, Notice of Allowance mailed Apr. 9, 2003.Applicant
- U.S. Appl. No. 09/848,445, Preliminary Amendment mailed Dec. 5, 2001.Applicant
- U.S. Appl. No. 09/848,445, Office Action mailed Dec. 5, 2003.Applicant
- U.S. Appl. No. 09/848,445, Response to Office Action mailed Dec. 5, 2003.Applicant
- U.S. Appl. No. 09/848,445, Office Action mailed May 6, 2004.Applicant
- U.S. Appl. No. 09/848,445, Response to Office Action (Rule 116) mailed Jun. 5, 2004.Applicant
- U.S. Appl. No. 09/886,578, Preliminary Amendment mailed Jun. 21, 2001.Applicant
- U.S. Appl. No. 09/886,578, Office Action mailed Nov. 8, 2001.Applicant
- U.S. Appl. No. 09/886,578, Response to Office Action mailed Nov. 8, 2001.Applicant
- U.S. Appl. No. 09/886,578, Office Action mailed Jun. 5, 2002.Applicant
- U.S. Appl. No. 09/886,578, Response to Office Action mailed Jun. 5, 2002.Applicant
- U.S. Appl. No. 09/886,578, Notice of Allowance mailed Sep. 9, 2002.Applicant
- U.S. Appl. No. 09/992,966, Office Action mailed Feb. 3, 2003.Applicant
- U.S. Appl. No. 09/992,966, Response to Office Action mailed Feb. 3, 2003.Applicant
- U.S. Appl. No. 09/992,966, Office Action mailed Mar. 28, 2002.Applicant
- U.S. Appl. No. 09/992,966, Response to Office Action mailed Mar. 28, 2002.Applicant
- U.S. Appl. No. 09/992,966, Office Action mailed Jul. 18, 2003.Applicant
- U.S. Appl. No. 09/992,966, Response to Office Action mailed Jul. 18, 2003.Applicant
- U.S. Appl. No. 09/992,966, Examiner Summary mailed Oct. 27, 2003.Applicant
- U.S. Appl. No. 09/992,966, Notice of Allowance mailed Apr. 15, 2004.Applicant
- U.S. Appl. No. 09/992,966, Office Action mailed Jan. 6, 2004.Applicant
- U.S. Appl. No. 09/992,966, Response to Office Action mailed Jan. 6, 2004.Applicant
- U.S. Appl. No. 09/992,966, Notice of Allowance mailed Sep. 3, 2004.Applicant
- U.S. Appl. No. 10/234,660, Office Action mailed Mar. 31, 2003.Applicant
- U.S. Appl. No. 10/234,660, Response to Office Action mailed Mar. 31, 2003.Applicant
- U.S. Appl. No. 10/234,660, Final Office Action mailed Oct. 31, 2003.Applicant
- U.S. Appl. No. 10/234,660, 12/23/03 Response to Office Action mailed Oct. 31, 2003.Applicant
- U.S. Appl. No. 10/234,660 Response and Amendment Under 37 CFR Section 1.116 mailed Oct. 31, 2003.Applicant
- U.S. Appl. No. 10/234,660; Advisory Action mailed Jan. 27, 2004.Applicant
- U.S. Appl. No. 10/234,660; Appeal Brief filed Jun. 14, 2004.Applicant
- U.S. Appl. No. 10/234,660; Amendment filed Jul. 20, 2004.Applicant
- U.S. Appl. No. 10/234,660; Marked up Claims by USPTO dated Jul. 28, 2004.Applicant
- U.S. Appl. No. 10/234,660; Notice of Allowance; Aug. 2, 2004.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Jul. 29, 2004.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Jul. 29, 2004.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Dec. 13, 2004.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Dec. 13, 2004.Applicant
- U.S. Appl. No. 10/297,270 Request Deletion of Named Inventors Pursuant to 37 CFR § 1.63 (d)(2) received by the Patent Office on Oct. 4, 2002.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Jul. 13, 2005.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Jul. 13, 2005.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Feb. 9, 2006.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Feb. 9, 2006.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Sep. 25, 2006.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Sep. 25, 2006.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Jan. 11, 2007.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Jan. 11, 2007.Applicant
- U.S. Appl. No. 10/297,270 Office Action mailed Jul. 26, 2007.Applicant
- U.S. Appl. No. 10/297,270 Response to Office Action mailed Jul. 26, 2007.Applicant
- U.S. Appl. No. 10/601,208 Preliminary Amendment, mailed Jun. 20, 2003.Applicant
- U.S. Appl. No. 10/601,208 Office Action mailed Jun. 15, 2004.Applicant
- U.S. Appl. No. 10/601,208 Response to Office Action mailed Jun. 15, 2004.Applicant
- U.S. Appl. No. 10/601,208 Office Action mailed Aug. 26, 2004.Applicant
- U.S. Appl. No. 10/601,208 Response to Office Action mailed Aug. 26, 2004.Applicant
- U.S. Appl. No. 10/601,208 Second Response to Office Action mailed Aug. 26, 2004.Applicant
- U.S. Appl. No. 10/601,208 Office Action mailed May 11, 2005.Applicant
- U.S. Appl. No. 10/601,208 Response to Office Action mailed May 11, 2005.Applicant
- U.S. Appl. No. 10/601,208 Office Action mailed Feb. 15, 2006.Applicant
- U.S. Appl. No. 10/601,208 Response to Office Action mailed Feb. 15, 2006.Applicant
- U.S. Appl. No. 10/601,208 Office Action mailed Sep. 26, 2006.Applicant
- U.S. Appl. No. 10/601,208 Response to Office Action mailed Sep. 26, 2006.Applicant
- U.S. Appl. No. 10/601,208 Notice of Allowance mailed Dec. 8, 2006.Applicant
- U.S. Appl. No. 10/842,947, Preliminary Amendment mailed May 11, 2004.Applicant
- U.S. Appl. No. 10/842,947, Office Action mailed Nov. 30, 2004.Applicant
- U.S. Appl. No. 10/842,947, Response to Office Action mailed Nov. 30, 2004.Applicant
- U.S. Appl. No. 10/842,947, Office Action mailed Jun. 30, 2005.Applicant
- U.S. Appl. No. 10/842,947, Response to Office Action mailed Jun. 30, 2005.Applicant
- U.S. Appl. No. 10/842,947, Notice of Allowance mailed Feb. 9, 2006.Applicant
- U.S. Appl. No. 10/921,743; Office Action mailed Mar. 4, 2005.Applicant
- U.S. Appl. No. 10/921,743; Response to Office Action mailed Mar. 4, 2005.Applicant
- U.S. Appl. No. 10/921,743; Office Action mailed May 26, 2005.Applicant
- U.S. Appl. No. 10/921,743; Response to Office Action mailed May 26, 2005.Applicant
- U.S. Appl. No. 10/921,743; Office Action mailed Sep. 13, 2005.Applicant
- U.S. Appl. No. 10/921,743; Advisory mailed Nov. 25, 2005.Applicant
- U.S. Appl. No. 10/921,743; Response to Office Action mailed Sep. 13, 2005 and Advisory mailed Nov. 25, 2005.Applicant
- U.S. Appl. No. 10/921,743; Notice of Allowance; Feb. 16, 2006.Applicant
- U.S. Appl. No. 10/950,897, Notice of Allowance mailed Feb. 13, 2005.Applicant
- U.S. Appl. No. 10/950,897, Office Action mailed Mar. 7, 2005.Applicant
- U.S. Appl. No. 10/950,897, Response to Office Action mailed Mar. 7, 2005.Applicant
- U.S. Appl. No. 10/950,897, Office Action mailed Jun. 23, 2005.Applicant
- U.S. Appl. No. 10/950,897, Response to Office Action mailed Jun. 23, 2005.Applicant
- U.S. Appl. No. 10/950,897, Office Action mailed Sep. 9, 2005.Applicant
- U.S. Appl. No. 10/950,897, Response to Office Action mailed Sep. 9, 2005.Applicant
- U.S. Appl. No. 10/950,897, Office Action mailed Nov. 25, 2005.Applicant
- U.S. Appl. No. 10/950,897, Response to Office Action mailed Nov. 25, 2005.Applicant
- U.S. Appl. No. 10/950,897, Amendment to Notice of Allowance mailed Dec. 13, 2005.Applicant
- U.S. Appl. No. 11/221,029; Preliminary Amendment dated Aug. 22, 2006.Applicant
- U.S. Appl. No. 11/221,029; Office Action mailed Sep. 8, 2006.Applicant
- U.S. Appl. No. 11/221,029; Response to Office Action mailed Sep. 8, 2006.Applicant
- U.S. Appl. No. 11/221,029; Notice of Allowance; Oct. 3, 2006.Applicant
- U.S. Appl. No. 11/252,576; Notice of Allowance; Dec. 11, 2007.Applicant
- U.S. Appl. No. 11/358,508; Notice of Non Compliance mailed Sep. 12, 2006.Applicant
- U.S. Appl. No. 11/358,508, Preliminary Amendment mailed Mar. 30, 2006.Applicant
- U.S. Appl. No. 11/358,508, Preliminary Amendment mailed May 30, 2006.Applicant
- U.S. Appl. No. 11/358,508, Preliminary Amendment mailed Jul. 26, 2006.Applicant
- U.S. Appl. No. 11/358,508, Office Action mailed Aug. 14, 2006.Applicant
- U.S. Appl. No. 11/358,508, Response to Office Action mailed Aug. 14, 2006.Applicant
- U.S. Appl. No. 11/358,508. Notice of Non Compliance Amendment mailed Sep. 12, 2006.Applicant
- U.S. Appl. No. 11/358,508, Response to Notice mailed Sep. 12, 2006.Applicant
- U.S. Appl. No. 11/358,508, Notice of Allowability & Interview Summary mailed Oct. 18, 2006.Applicant
- U.S. Appl. No. 11/358,508, Rule 312 Amendment mailed Oct. 24, 2006.Applicant
- U.S. Appl. No. 11,434,588: Office Action mailed Jan. 31, 2007.Applicant
- U.S. Appl. No. 11,434,588; Response to Office Action mailed Jan. 31, 2007.Applicant
- U.S. Appl. No. 11,434,588; Notice of Allowance; Jul. 11, 2007.Applicant
- U.S. Appl. No. 11,434,588; Notice of Allowance; Nov. 6, 2007.Applicant
- U.S. Appl. No. 11/484,199 Preliminary Amendment; Sep. 7, 2006.Applicant
- U.S. Appl. No. 11/484,199 Notice of Allowance and Examiner Interview Summary; Oct. 6, 2006.Applicant
- U.S. Appl. No. 11/598,410, Office Action mailed Jun. 13, 2007.Applicant
- U.S. Appl. No. 11/598,410 Response to Office Action mailed Jun. 13, 2007.Applicant
- U.S. Appl. No. 11/598,410, Notice of Allowability Sep. 26, 2007.Applicant
- U.S. Appl. No. 11/646,768, Office Action mailed May 7, 2007.Applicant
- U.S. Appl. No. 11/646,768, Response to Office Action mailed May 7, 2007.Applicant
- U.S. Appl. No. 11/646,768, Office Action mailed Oct. 29, 2007.Applicant
- U.S. Appl. No. 11/646,768, Response to Office Action mailed Oct. 29, 2007.Applicant
- U.S. Appl. No. 11/646,768; Notice of Allowance; Jan. 18, 2008.Applicant
- U.S. Appl. No. 11/747,081; Office Action mailed Jan. 24, 2008.Applicant
- Cole, George, “The Little Label with an Explosion of Applications”, Financial Times, Ltd., 2002, pp. 1-3.Applicant
- Deem, “Fast Forward Go for a Ride on the World's Fastest Sailboat”, Popular Mechanics, www.popularmechanics.com, Feb. 2001, pp. 1-2.Applicant
- Desmarais, “Solutions in Hand”, BEI Technologies, Inc., www.sensormag.com, Jan. 2001, pp. 1-2.Applicant
- Desmarais et al., “How to select and use the right temperature,” www.sensorsmag.com, Jan. 2001, pp. 30-36.Applicant
- GPS Locator for Children, Klass Kids Foundation Jul. 15, 2004.Applicant
- Henkel, Research & Developments, Sensors, Nov. 2000. p. 18.Applicant
- Janssens et al., “Columbus: A Novel Sensor System for Domestic Washing Machines”, Sensors Magazine Online, Jun., 2002 , pp. 1-9.Applicant
- Licking, Special Report: E-Health, “This is the Future of Medicine”, Business Week E.Biz, Dec. 11, 2000, pp. 77 and 78 US.Applicant
- Li-Ron, Tomorrow's Cures, Health & Fitness Special Section Online, Newsweek, Dec. 10, 2001, pp. 3-10.Applicant
- Mark of Fitness Flyer, “High Quality, Self-Taking Blood Pressure Monitors”, four pages, Shrewsbury, NJ, US.Applicant
- Martella, Product News, “Temperature Monitoring System”, Nov. 2000, p. 77.Applicant
- Nobbe, “Olympic Athletes Get a Boost from Technology”, Machine Design, vol. 60, No. 19, Aug. 25, 1988.Applicant
- Paradiso et al., Design and Implementation of Expressive Footwear, May 12, 2000, IBM Systems Journal, vol. 39, Nos. 3&4, pp. 511-529.Applicant
- Paradiso, et al. “Instrumented Footwear for Interactive Dance” Version 1.1, Presented at the XII Colloquium on Musical Informatics, Gorizia, Italy, Sep. 24-26, 1998, pp. 1-4.Applicant
- Sellers. Gear to Go, Mitch Mandel Photography, Mar. 2001, pp. 61-62.Applicant
- Shannon P. Jackson and Harold Kirkham, “Weighing Scales Based on Low-Power Strain-Gauge Circuits”, Nasa Tech Briefs, Jun. 2001, p. 49 US.Applicant
- Sharp, A Sense of the Real World, www.idsystems.com/reader/2000—09/sens0900.htm, Sep., 2000, 4 pages.Applicant
- Skaloud et al., DGPS-Calibrated Accelerometric System for Dynamic Sports Events, Sep. 19-22, 2000, ION GPS 2000.Applicant
- Smith et al., “Flexible and Survivable Non-Volatile Memory Data Recorder”, AFRL Technology Horizons, Dec. 2000, p. 26.Applicant
- Webster's II New Riverside University Dictionary, 1988, The Riverside Publishing Company, p. 1138. (cited by examiner).Applicant
- Wysocki, Jr., Staff Reporter, “Do Devices Measuring Body Signs Appeal to the Sick or Healthy”, Pittsburgh, US.Applicant
- No author listed, “Your Next . . . ”, Newsweek, Jun. 25, 2001, p. 52 US.Applicant
- No author listed, The GPS Connection, Popular Mechanics, Feb. 2001, p. 65.Applicant
- No author listed, WarmMark Time Temperature Indicators, www.coldice.com/warmmark—temperature—indicators.html, Cold Ice., Inc.Applicant
- No author listed, Wireless Temperature Monitor, www.echo-on.net/mob/, Nov. 20. 2000.Applicant
- Unattributed, 3M MonitorMark Indicator Data Sheet [online), [retrieved on Aug. 9, 2004], retrieved from the Internet: URL: http://www.3m.com/us/healthcare/medicalspecialties/monitor/products.html; 4 pages.Applicant
- International Search Report dated Jul. 7, 2008 in PCT Application No. PCT/US2007/012033.Applicant
- Written Opinion dated Jul. 7, 2008 in PCT Application No. PCT/US2007/012033.Applicant
- Office Action dated May 13, 2009 in U.S. Appl. No. 11/585,721.Applicant
- Office Action dated Apr. 14, 2009 in U.S. Appl. No. 11/439,523.Applicant
- Office Action dated Oct. 29, 2008 in U.S. Appl. No. 11/566,072.Applicant
- Office Action dated Mar. 4, 2009 in U.S. Appl. No. 11/513,616.Applicant
- Notice of Allowance dated Oct. 8, 2009 in U.S. Appl. No. 11/439,523.Applicant
- Office Action dated Sep. 4, 2009 in U.S. Appl. No. 11/585,721.Applicant
- Office Action dated Aug. 20, 2009 in U.S. Appl. No. 11/513,616.Applicant