This section is intended to provide background information to facilitate a better understanding of various technologies described herein. As the section's title implies, this is a discussion of related art. That such art is related in no way implies that it is prior art. The related art may or may not be prior art. It should therefore be understood that the statements in this section are to be read in this light, and not as admissions of prior art.
Accurate data, including, for example, a count of fishing casts made, can be very useful for a fisherman. A device that can capture this data can provide advantages to a fisherman. Such advantages include requiring less time to record information, and collecting more accurate data.
Described herein are implementations of various technologies for an apparatus for determining whether motion and heart rate data correspond to a fishing activity. The apparatus is a wearable device. The wearable device includes a heart rate sensor and a motion sensor. The wearable device includes a computer system with a processor and memory. The memory has a plurality of executable instructions. In one implementation, when the executable instructions are executed by the processor, the processor may receive motion data from the motion sensor, receive heart rate data from the heart rate sensor, and determine whether the received motion and heart rate data corresponds to a fishing activity.
Described herein are also implementations of various technologies for a method for determining whether motion data and heart rate data correspond to a fishing activity. In one implementation, a non-transitory computer-readable medium having stored thereon computer-executable instructions which, when executed by a computer, cause the computer to perform various actions. The actions may include receiving motion data from a first sensor and heart rate data from a second sensor. The received motion data and heart rate data may be analyzed to determine whether the received data corresponds to a fishing activity.
Described herein are also implementations of various technologies for an apparatus for determining a level of physical exertion. The apparatus is a wearable device. The wearable device includes a motion sensor and a heart rate sensor. The wearable device includes a computer system with a processor and memory. The memory has a plurality of executable instructions. In one implementation, when the executable instructions are executed by the processor, the processor may receive motion data from the motion sensor, receive heart rate data from the heart rate sensor, and determine a level of physical exertion based on the motion data and the heart rate data. The level of physical exertion may correspond to an activity during fishing or sailing.
The above referenced summary section is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description section. The summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
Implementations of various techniques will hereafter be described with reference to the accompanying drawings. It should be understood, however, that the accompanying drawings illustrate only the various implementations described herein and are not meant to limit the scope of various techniques described herein.
The discussion below is directed to certain specific implementations. It is to be understood that the discussion below is only for the purpose of enabling a person with ordinary skill in the art to make and use any subject matter defined now or later by the patent “claims” found in any issued patent herein.
It is specifically intended that the claimed invention not be limited to the implementations and illustrations contained herein, but include modified forms of those implementations including portions of the implementations and combinations of elements of different implementations as come within the scope of the following claims. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure. Nothing in this application is considered critical or essential to the claimed invention unless explicitly indicated as being “critical” or “essential.”
Reference will now be made in detail to various implementations, examples of which are illustrated in the accompanying drawings and figures. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first object or step could be termed a second object or step, and, similarly, a second object or step could be termed a first object or step, without departing from the scope of the invention. The first object or step, and the second object or step, are both objects or steps, respectively, but they are not to be considered the same object or step.
The terminology used in the description of the present disclosure herein is for the purpose of describing particular implementations only and is not intended to be limiting of the present disclosure. As used in the description of the present disclosure and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. As used herein, the terms “up” and “down”; “upper” and “lower”; “upwardly” and downwardly”; “below” and “above”; and other similar terms indicating relative positions above or below a given point or element may be used in connection with some implementations of various technologies described herein.
Various implementations of fishing and sailing activity detection described herein will now be described in more detail with reference to
Fishing Activity Detection
Fishermen often record details of their fishing trips so that the information can be referenced at a later time, and so that the trip can be analyzed. Accordingly, various implementations described herein are directed to a wearable device that captures motion data and heart rate data, and that automatically determines when a fishing activity has occurred. Fishing data describing the fishing activity could then be recorded by a computer system. In this manner, a digital record of fishing activities and other information could be created without the need for significant user input. Accordingly,
The wearable device 100 may be made of a combination of plastics and rubbers, or of any other synthetic material. The wearable device 100 may include a housing in the shape of a band. The wearable device 100 may be waterproof. The wearable device 100 may include a clasp, or another mechanism to aid in removal of the wearable device 100 from a user's arm. The wearable device 100 may include buttons 110.
The heart rate sensor 150 may be located in the wearable device 100, or may communicate wirelessly with the wearable device 100. The heart rate sensor 150 may measure a user's pulse to determine heart rate. The heart rate sensor 150 may be any sensor capable of measuring heart rate or pulse. In one implementation, the heart rate sensor 150 may be an optical sensor used to detect pulse. For example, an optical sensor may be located on a wearable device 100 so that the optical sensor is in contact with a user's skin. The optical sensor may detect blood flow beneath the user's skin and use this information to determine the user's heart rate.
In another implementation, the heart rate sensor 150 may be an electromagnetic sensor. For example, the electromagnetic sensor may be located on a chest strap. The electromagnetic sensor may communicate wirelessly with the wearable device 100 using Bluetooth, the ANT wireless protocol, or through any other wireless method.
The heart rate sensor 150 may be activated whenever the wearable device 100 is in use. Alternately, the heart rate sensor 150 may be activated only when activity is detected. In one implementation, the motion sensor 130 may detect a threshold level of activity, and then the heart rate sensor 150 may be activated in response. In another implementation, the wearable device 100 may only receive or record data from the heart rate sensor 150 when activity is detected. For example, if the heart rate sensor 150 transmits data wirelessly, the wearable device 100 may only receive the data when activity is detected. By activating the heart rate sensor 150 only when activity is detected, the wearable device 100 may consume less electricity and store and process less data.
The computer 140 is described in more detail in
Continuing with describing
The wearable device may contain a display 120. The display may be a series of Light Emitting Diodes (LED). The display 120 may be a Liquid Crystal Display (LCD). The display 120 may be used to display a measure of physical exertion, illustrated in
The wearable device 100 may include wireless technology, such as Bluetooth, Wi-Fi, cellular technology such as GSM or CDMA, satellite communication, or any other wireless technology. In one implementation, the wearable device 100 may be connected wirelessly to a marine electronics device 700, which is described in more detail in
The marine electronics device 700 or a computer system 600, including a smart phone, may record additional data, such as location, speed, weather, or other data. The data from the marine electronics device 700 or computer system 600 and the wearable device 100 may then be combined to provide comprehensive data regarding a fishing trip. The combined data may then be transmitted to a remote server or cloud. In one implementation, the combined data may be transmitted to a smart phone device, which then transmits the data to a remote server or cloud. In another implementation, the combined data may be transmitted to the data logging device, which may then transmit the combined data at a later time. In yet another implementation, the data from the wearable device 100 may be transmitted to the remote server or cloud via the smart phone without using the marine electronics device 700. In still another implementation, the data from the wearable device may be transmitted to a data logging device prior to being transmitted to a remote server or cloud via the smart phone.
Fishing Activity Detection Software
As mentioned above, the computer 130 contained in a wearable device 100 may be loaded with a set of instructions (software) to analyze data received from one or more sensors. At block 310, the fishing activity detection software 300 may receive motion data from the at least one motion sensor 130 in the wearable device. The software may analyze the motion data to detect activity. If a threshold amount of activity is detected, the software may activate the heart rate sensor 150 at block 320. In one implementation, the motion sensor 130 is recording data throughout a fishing trip, and the heart rate sensor 150 is only recording data when activity is detected by the motion sensor 130. In a second implementation, both the motion sensor 130 and the heart rate sensor 150 record data throughout a fishing trip. In this second implementation, block 320 is skipped. In both implementations, blocks 310 and 330 may operate simultaneously. For example, the software may receive motion data and heart rate data simultaneously.
At block 330, the software may receive heart rate data from the heart rate sensor 150. The heart rate data may consist of a user's pulse. The heart rate data may be measured in beats per minute (BPM), or any other heart rate measurement. For example the heart rate data may consist of a transmission each time a heart beat is detected. In another example, the heart rate data may consist of the current BPM and may be transmitted every tenth of a second. Any data relating to heart rate, heartbeat, or pulse may be received.
At block 340, the software may analyze the motion data and the corresponding heart rate data to determine whether a fishing activity has occurred. The software may also determine what type of fishing activity has occurred. The fishing activity may be a catch, cast, bite, or any other fishing activity. The software may record the occurrence of the fishing activity and the time, e.g., a timestamp in memory inside the computer 130, of the activity. The record may be a database, a log, or any other method of recording the fishing data. The fishing activity may be shown on a display 150. For example, a count of casts may be displayed, or a count of bites. The software may also record a measure of physical exertion corresponding to the fishing activity, as described in
Fishing activity may be detected at block 340 using motion data, heart rate data, or both. Using both heart rate data and motion data to detect fishing activity may be more precise than using one type of data. Fishing activities, including making a cast or catch, may cause a fisherman's heart rate to increase due to physical exertion. For example, a motion sensor 130 may detect motion that appears to correspond to a catch, and data from the heart rate sensor 150 may indicate an increase in heart rate, confirming the occurrence of the catch. In a second example, the heart rate sensor 150 may detect a change in a user's heart rate, indicating that the user is engaged in a physical activity, and the motion sensor data may be used to determine what fishing activity occurred. In a third example, the software may analyze both heart rate data and motion data simultaneously to detect a fishing activity.
When the trip is over, the software may transmit the recorded data wirelessly to the connected device, e.g., the marine electronics device 700. For example, the recorded data may be a database of detected fishing activities and timestamps for those activities. In another example, the recorded data may include both motion data and heart rate data. In one implementation, the software may transmit the recorded data after each new entry, or at any other interval. For example, the transmission may be made after each cast. The transmission may be to a remote server or to any computer system, including a smart phone or a marine electronics device.
Exertion Monitoring Software
As mentioned above, the computer 140 contained in a wearable device 100 may be loaded with a set of instructions (software) to analyze data received from one or more sensors. At block 410, the exertion monitoring software 400 may receive motion data, heart rate data, or both. The received data may be recorded using a wearable device 100 during a fishing trip or a sailing trip.
At block 420, the software may detect physical exertion using the received motion data, heart rate data, or both. The physical exertion may correspond to a user's activities during a fishing trip or while sailing. For example, while fishing a user may be particularly active during a fishing catch, particularly during the fight portion of a catch. In another example, while sailing, a user may be particularly active during a turn (i.e. a tack), or while operating a winch. These activities may result in an increased heart rate, and increase in motion. These increases may be reflected in the data captured by the heart rate and motion sensors. The software may process the sensor data to determine the level of exertion.
The level of exertion detected at block 420 may be determined using motion data, heart rate data, or both. For example, the software may examine the amount of increase in heart rate and the length of time that heart rate is increased. In another example, the software may examine the amount of motion detected and the length of time that motion is detected.
At block 430, the software may output a measure of the physical exertion. The measure may be an estimate of calories burned, a numeral describing the level of physical exertion, or any other indicator of physical exertion. In one implementation, the numeral may range from 1, corresponding to low exertion, to 10, corresponding to high exertion. For example, a fishing catch with a routine two minute fight may have a rating of 2, while a catch with a vigorous forty minute fight may have a rating of 8. Although the numeral is described as ranging from 1 to 10, the numeral may have any range. Additionally, any other type of indicator may be used to display the level of exertion, for example, a symbol or a chart. Examples of output are further described in
The exertion monitoring software 400 may be used to measure fishing activities, such as casts, catches, fights during a catch, or any other fishing activity. The exertion monitoring software 400 may also be used to measure physical exertion during other activities, including sailing activities. For example, in a sailing trip, the exertion monitoring software 400 may be used to measure the exertion while tacking or during any other activity, or throughout an entire race or sailing trip.
The physical exertion level during a fishing activity or trip, or sailing activity or trip may be automatically recorded. The physical exertion level may be used in a competition. For example, multiple fishermen on a fishing trip may engage in a competition to determine which fishermen had the highest exertion level during a single fishing catch.
Physical Exertion Display
The level of physical exertion measured during fishing activities or while sailing may be displayed during an activity, immediately following an activity, or may be stored for later viewing. Additionally, a graph may be generated to display the level of exertion over time. In physical exertion display 500, a numeral is used to represent the exertion level measured during the last fishing catch. This type of display could also be used to represent the exertion level measured during the last tack in a sailing trip, or during any other fishing or sailing activity. Additionally, the display could represent the exertion level over a longer period of time, for example, an entire sailing trip or fishing trip.
Physical exertion display 510 shows a graph of exertion over a 60 minute time period. Although the period is shown as 60 minutes, any time period may be used. Although
Computing System
Implementations of various technologies described herein may be operational with numerous general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the various technologies described herein include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, smart phones, and the like.
The various technologies described herein may be implemented in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that performs particular tasks or implement particular abstract data types. Further, each program module may be implemented in its own way, and all need not be implemented the same way. While program modules may all execute on a single computing system, it should be appreciated that, in some implementations, program modules may be implemented on separate computing systems or devices adapted to communicate with one another. A program module may also be some combination of hardware and software where particular tasks performed by the program module may be done either through hardware, software, or both.
The various technologies described herein may also be implemented in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network, e.g., by hardwired links, wireless links, or combinations thereof. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The computing system 600 may include a central processing unit (CPU) 621, a system memory 622 and a system bus 623 that couples various system components including the system memory 622 to the CPU 621. Although only one CPU is illustrated in
The computing system 600 may further include a hard disk drive 627 for reading from and writing to a hard disk, a magnetic disk drive 628 for reading from and writing to a removable magnetic disk 629, and an optical disk drive 630 for reading from and writing to a removable optical disk 631, such as a CD ROM or other optical media. The hard disk drive 627, the magnetic disk drive 628, and the optical disk drive 630 may be connected to the system bus 623 by a hard disk drive interface 632, a magnetic disk drive interface 633, and an optical drive interface 634, respectively. The drives and their associated computer-readable media may provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computing system 600.
Although the computing system 600 is described herein as having a hard disk, a removable magnetic disk 629 and a removable optical disk 631, it should be appreciated by those skilled in the art that the computing system 600 may also include other types of computer-readable media that may be accessed by a computer. For example, such computer-readable media may include computer storage media and communication media. Computer storage media may include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules or other data. Computer storage media may further include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computing system 600. Communication media may embody computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism and may include any information delivery media. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above may also be included within the scope of computer readable media.
A number of program modules may be stored on the hard disk 627, magnetic disk 629, optical disk 631, ROM 624 or RAM 625, including an operating system 635, one or more application programs 636, program data 638, and a database system 655. The one or more application programs 636 may contain program instructions configured to perform methods 300 and 400 according to various implementations described herein. The operating system 635 may be any suitable operating system that may control the operation of a networked personal or server computer, such as Windows® XP, Mac OS® X, Unix-variants (e.g., Linux® and BSD®), and the like.
A user may enter commands and information into the computing system 600 through input devices such as a keyboard 640 and pointing device 642. Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, user input button, or the like. These and other input devices may be connected to the CPU 621 through a serial port interface 646 coupled to system bus 623, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 647 or other type of display device may also be connected to system bus 623 via an interface, such as a video adapter 648. In addition to the monitor 647, the computing system 600 may further include other peripheral output devices such as speakers and printers.
Further, the computing system 600 may operate in a networked environment using logical connections to one or more remote computers 649. The logical connections may be any connection that is commonplace in offices, enterprise-wide computer networks, intranets, and the Internet, such as local area network (LAN) 651 and a wide area network (WAN) 652. The remote computers 649 may each include application programs 636 similar to that as described above. The computing system 600 may use a Bluetooth radio to wirelessly communicate with another device.
When using a LAN networking environment, the computing system 600 may be connected to the local network 651 through a network interface or adapter 653. When used in a WAN networking environment, the computing system 600 may include a modem 654, wireless router or other means for establishing communication over a wide area network 652, such as the Internet. The modem 654, which may be internal or external, may be connected to the system bus 623 via the serial port interface 646. In a networked environment, program modules depicted relative to the computing system 600, or portions thereof, may be stored in a remote memory storage device 650. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
Marine Electronics Device
While the foregoing is directed to implementations of various techniques described herein, other and further implementations may be devised without departing from the basic scope thereof, which may be determined by the claims that follow. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/868,444, filed Aug. 21, 2013 titled FISHING DATA COLLECTION AND USE, and the disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4751787 | Jonsson | Jun 1988 | A |
4829493 | Bailey | May 1989 | A |
4879697 | Lowrance et al. | Nov 1989 | A |
5025423 | Earp | Jun 1991 | A |
5191341 | Gouard et al. | Mar 1993 | A |
5228228 | Meissner | Jul 1993 | A |
5321391 | Fox | Jun 1994 | A |
5446775 | Wright | Aug 1995 | A |
5537380 | Sprankle, Jr. et al. | Jul 1996 | A |
5546695 | Langer | Aug 1996 | A |
6045076 | Daniels | Apr 2000 | A |
6125571 | Sigwald | Oct 2000 | A |
6222449 | Twining | Apr 2001 | B1 |
6225984 | Crawford | May 2001 | B1 |
6252544 | Hoffberg | Jun 2001 | B1 |
6263147 | Tognazzini | Jul 2001 | B1 |
6321158 | DeLorme et al. | Nov 2001 | B1 |
6411283 | Murphy | Jun 2002 | B1 |
6418080 | Inouchi | Jul 2002 | B2 |
6421299 | Betts et al. | Jul 2002 | B1 |
6459372 | Branham et al. | Oct 2002 | B1 |
6567792 | Arnold | May 2003 | B1 |
6584722 | Walls | Jul 2003 | B1 |
6587740 | Byrne et al. | Jul 2003 | B2 |
6751626 | Brown et al. | Jun 2004 | B2 |
6761692 | Angelsen et al. | Jul 2004 | B2 |
6798378 | Walters | Sep 2004 | B1 |
6816782 | Walters et al. | Nov 2004 | B1 |
7002579 | Olson | Feb 2006 | B2 |
7236426 | Turner et al. | Jun 2007 | B2 |
7243457 | Smith et al. | Jul 2007 | B1 |
7319992 | Gaos | Jan 2008 | B2 |
7321824 | Nesbitt | Jan 2008 | B1 |
7430461 | Michaels | Sep 2008 | B1 |
7652952 | Betts et al. | Jan 2010 | B2 |
7669360 | Davidson | Mar 2010 | B2 |
7710825 | Betts et al. | May 2010 | B2 |
7722218 | Leung | May 2010 | B2 |
7729203 | Betts et al. | Jun 2010 | B2 |
7755974 | Betts et al. | Jul 2010 | B2 |
7812667 | Fagg | Oct 2010 | B2 |
7870496 | Sherwani | Jan 2011 | B1 |
7890867 | Margulis | Feb 2011 | B1 |
8019532 | Sheha et al. | Sep 2011 | B2 |
8040758 | Dickinson | Oct 2011 | B1 |
8063540 | Angelsen et al. | Nov 2011 | B2 |
8082100 | Grace et al. | Dec 2011 | B2 |
8364806 | Short et al. | Jan 2013 | B2 |
8452797 | Paleja et al. | May 2013 | B1 |
8468164 | Paleja et al. | Jun 2013 | B1 |
8512238 | Nissila | Aug 2013 | B2 |
8721453 | Rosing | May 2014 | B2 |
9439411 | Bailey | Sep 2016 | B2 |
9507562 | Bailey | Nov 2016 | B2 |
9572335 | Bailey | Feb 2017 | B2 |
9615562 | Bailey | Apr 2017 | B2 |
20010054961 | Twining | Dec 2001 | A1 |
20020035574 | Dumas | Mar 2002 | A1 |
20020093541 | Schileru-Key | Jul 2002 | A1 |
20020099457 | Fredlund et al. | Jul 2002 | A1 |
20020116421 | Fox et al. | Aug 2002 | A1 |
20030046689 | Gaos | Mar 2003 | A1 |
20030056419 | Squires et al. | Mar 2003 | A1 |
20030089020 | Dirito | May 2003 | A1 |
20030147981 | Gillam | Aug 2003 | A1 |
20040124297 | Steer | Jul 2004 | A1 |
20040162830 | Shirwadkar et al. | Aug 2004 | A1 |
20040193364 | Chojnacki | Sep 2004 | A1 |
20040198554 | Orr | Oct 2004 | A1 |
20040249860 | Stechschulte et al. | Dec 2004 | A1 |
20050011105 | Cameron et al. | Jan 2005 | A1 |
20050037872 | Fredlund et al. | Feb 2005 | A1 |
20050102101 | Beesley et al. | May 2005 | A1 |
20060013066 | Nishimori et al. | Jan 2006 | A1 |
20060048434 | Congel | Mar 2006 | A1 |
20060053028 | Congel | Mar 2006 | A1 |
20060119585 | Skinner | Jun 2006 | A1 |
20060224940 | Lee | Oct 2006 | A1 |
20060265931 | McFadden et al. | Nov 2006 | A1 |
20070011334 | Higgins et al. | Jan 2007 | A1 |
20070045010 | Kasperek | Mar 2007 | A1 |
20070058489 | Bratcher | Mar 2007 | A1 |
20070220798 | Davidson | Sep 2007 | A1 |
20080032666 | Hughes et al. | Feb 2008 | A1 |
20080126935 | Blomgren | May 2008 | A1 |
20080165022 | Herz et al. | Jul 2008 | A1 |
20080204424 | Jin et al. | Aug 2008 | A1 |
20080246627 | Guazzelli | Oct 2008 | A1 |
20090064055 | Chaudhri et al. | Mar 2009 | A1 |
20090099871 | Gadodia | Apr 2009 | A1 |
20090105952 | Grace et al. | Apr 2009 | A1 |
20090179789 | Haughay, Jr. et al. | Jul 2009 | A1 |
20090231190 | Grumbles | Sep 2009 | A1 |
20090240354 | Davidson | Sep 2009 | A1 |
20090241636 | Obori | Oct 2009 | A1 |
20090249247 | Tseng et al. | Oct 2009 | A1 |
20090258710 | Quatrochi | Oct 2009 | A1 |
20090271054 | Dokken | Oct 2009 | A1 |
20090287409 | Summers | Nov 2009 | A1 |
20090293336 | Lankinen | Dec 2009 | A1 |
20090295626 | Su | Dec 2009 | A1 |
20100049468 | Papadourakis | Feb 2010 | A1 |
20100080082 | Betts et al. | Apr 2010 | A1 |
20100121716 | Golan | May 2010 | A1 |
20100145601 | Kurtti et al. | Jun 2010 | A1 |
20100198650 | Shaw | Aug 2010 | A1 |
20100199225 | Coleman et al. | Aug 2010 | A1 |
20100226203 | Buttle et al. | Sep 2010 | A1 |
20100250122 | Kubota et al. | Sep 2010 | A1 |
20100295781 | Alameh et al. | Nov 2010 | A1 |
20100319235 | Panaro | Dec 2010 | A1 |
20110007035 | Shai | Jan 2011 | A1 |
20110013484 | Coleman et al. | Jan 2011 | A1 |
20110013485 | Maguire | Jan 2011 | A1 |
20110019887 | Roehrig et al. | Jan 2011 | A1 |
20110025720 | Jo et al. | Feb 2011 | A1 |
20110067290 | Miskatovic | Mar 2011 | A1 |
20110082644 | Imasaka et al. | Apr 2011 | A1 |
20110154183 | Burns et al. | Jun 2011 | A1 |
20110208479 | Chaves | Aug 2011 | A1 |
20110213515 | Haymart et al. | Sep 2011 | A1 |
20110214500 | Cabrera et al. | Sep 2011 | A1 |
20110257819 | Chen et al. | Oct 2011 | A1 |
20120001773 | Lyons et al. | Jan 2012 | A1 |
20120010478 | Kinnunen | Jan 2012 | A1 |
20120011437 | James et al. | Jan 2012 | A1 |
20120014220 | DePasqua | Jan 2012 | A1 |
20120047790 | Hess et al. | Mar 2012 | A1 |
20120069712 | Potanin et al. | Mar 2012 | A1 |
20120095978 | Levin et al. | Apr 2012 | A1 |
20120106300 | Maguire | May 2012 | A1 |
20120144384 | Baek | Jun 2012 | A1 |
20120144723 | Davidson | Jun 2012 | A1 |
20120185801 | Madonna et al. | Jul 2012 | A1 |
20120253485 | Weast et al. | Oct 2012 | A1 |
20120293323 | Kaib | Nov 2012 | A1 |
20120316456 | Rahman et al. | Dec 2012 | A1 |
20120316458 | Rahman et al. | Dec 2012 | A1 |
20120317167 | Rahman et al. | Dec 2012 | A1 |
20130007665 | Chaudhri et al. | Jan 2013 | A1 |
20130040714 | Rosing | Feb 2013 | A1 |
20130074051 | Freeman | Mar 2013 | A1 |
20130096575 | Olson | Apr 2013 | A1 |
20130107031 | Atkinson | May 2013 | A1 |
20130109997 | Linke | May 2013 | A1 |
20130271301 | Kabel et al. | Oct 2013 | A1 |
20130281087 | Ruhanen et al. | Oct 2013 | A1 |
20130307720 | Lilburn | Nov 2013 | A1 |
20130343151 | Shiraki et al. | Dec 2013 | A1 |
20140012587 | Park | Jan 2014 | A1 |
20140032468 | Anandaraj | Jan 2014 | A1 |
20140071059 | Girault | Mar 2014 | A1 |
20140111368 | Lee et al. | Apr 2014 | A1 |
20140135592 | Ohnemus | May 2014 | A1 |
20140135631 | Brumback | May 2014 | A1 |
20140164375 | Persson et al. | Jun 2014 | A1 |
20140180566 | Malhotra | Jun 2014 | A1 |
20140195297 | Abuelsaad et al. | Jul 2014 | A1 |
20140221854 | Wai | Aug 2014 | A1 |
20140358483 | da Rosa | Dec 2014 | A1 |
20150019135 | Kacyvenski | Jan 2015 | A1 |
20150051786 | Wang | Feb 2015 | A1 |
20150054655 | Bailey | Feb 2015 | A1 |
20150054732 | Bailey | Feb 2015 | A1 |
20150054828 | Bailey | Feb 2015 | A1 |
20150054829 | Bailey | Feb 2015 | A1 |
20150055827 | Bailey | Feb 2015 | A1 |
20150055930 | Bailey | Feb 2015 | A1 |
20150057929 | Bailey | Feb 2015 | A1 |
20150057965 | Gaynor | Feb 2015 | A1 |
20150057968 | Bailey | Feb 2015 | A1 |
20150058020 | Bailey | Feb 2015 | A1 |
20150058237 | Bailey | Feb 2015 | A1 |
20150058323 | Bailey | Feb 2015 | A1 |
20150245777 | Della Torre | Sep 2015 | A1 |
20150310524 | Gospodarek et al. | Oct 2015 | A1 |
20150313199 | Castaneda et al. | Nov 2015 | A1 |
20150342481 | Liu | Dec 2015 | A1 |
20160125348 | Dyer et al. | May 2016 | A1 |
Number | Date | Country |
---|---|---|
102004059619 | Jun 2006 | DE |
749687 | Dec 1996 | EP |
1 561 377 | Aug 2005 | EP |
1782687 | May 2007 | EP |
2356902 | Aug 2011 | EP |
2 613 223 | Jul 2013 | EP |
2244195 | Nov 1991 | GB |
2426680 | Dec 2006 | GB |
2470904 | Dec 2010 | GB |
2004 207812 | Jul 2004 | JP |
2006-158239 | Jun 2006 | JP |
2010 193284 | Sep 2010 | JP |
2011 139647 | Jul 2011 | JP |
199802037 | Jan 1998 | WO |
2004088572 | Oct 2004 | WO |
2010056392 | May 2010 | WO |
WO 2012059734 | May 2012 | WO |
2012170163 | Dec 2012 | WO |
2014088508 | Jun 2014 | WO |
200 308 052 | Jul 2004 | ZA |
Entry |
---|
Office Action Issued in Canadian Patent Application 2,921,317, dated Feb. 7, 2017. |
Allen, et al.; Upper Extremity Kinematic Trends of Fly-Casting; Establishing the Effects of Line Length; Sports Biomechanics; vol. 7, No. 1; Jan. 1, 2008; pp. 38-53. |
First look at new Mio Link ANT +/Bluetooth Smart optical heart rate wrist band; http://www.dcrainmaker.com/2014/01/mio-link-first-look.html; Jan. 6, 2014 (accessed Apr. 18, 2016). |
SAS, “SAS BI Dashboard 4.31 User's Guide”, Second Edition, by SAS Electronic book, Aug. 1, 2012, downloaded at http://support.sas.com/documentation/cdl/en/bidbrdug/ 65580/PDF/default/bidrdrug.pdf. |
PCT International Search Report and Written Opinion; PCT/IB2014/063974, dated Dec. 2, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063975, dated Dec. 3, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063976, dated Dec. 12, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063979, dated Jan. 7, 2015; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063980, dated Jan. 5, 2015; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063982, dated Dec. 22, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063983, dated Mar. 5, 2015; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063973, dated Nov. 28, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063981, dated Feb. 10, 2015; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063978, dated Dec. 19, 2014; all enclosed pages cited. |
PCT International Search Report and Written Opinion; PCT/IB2014/063977, dated Nov. 28, 2014; all enclosed pages cited. |
First look at new Mio Link ANT+/Bluetooth Smart optical heart rate wrist band; http://www.dcrainmaker.com/2014/01/mio-link-first-look.html; Jan. 6, 2014 (accessed Mar. 3, 2014). |
PCT International Search Report and Written Opinion; PCT/IB2013/060285; dated Feb. 18, 2014. |
PCT International Search Report and Written Opinion; PCT/US2013/048177; dated Oct. 21, 2013. |
PCT International Search Report and Written Opinion; PCT/US2013/047869; dated Oct. 21, 2013. |
PCT International Search Report and Written Opinion; PCT/US2013/048129; dated Oct. 17, 2013. |
PCT International Search Report and Written Opinion; PCT/US2013/047926; dated Oct. 11, 2013. |
PCT International Search Report and Written Opinion; PCT/US2013/047645; dated Sep. 27, 2013. |
McElderry; At-Sea Observing Using Video-Based Electronic Monitoring; Prepared for: Electronic Monitoring Workshop Jul. 29-30, 2008; Archipelago Marine Research Ltd. |
Cristando et al. “Nikeplus Ecosystem Strategy” retreived Sep. 1, 2017 from <http://studylib.net/doc/8718940/nikeplus-ecosystem-strategy> 12 pages. |
Joey Davidson, “Jaybird Reign REVIEW—Lightweight, simple, lacking” Feb. 28, 2016, Technobuffalo, retrieved Sep. 1, 2017 from <https://www.technobuffalo.com/reviews/jaybird-reign-review/> 14 pages. |
Number | Date | Country | |
---|---|---|---|
20150057965 A1 | Feb 2015 | US |
Number | Date | Country | |
---|---|---|---|
61868444 | Aug 2013 | US |