This application is related to the following applications and issued U.S. patents: Co-Pending U.S. patent application Ser. No. 13/158,372, filed Jun. 10, 2011; Co-Pending U.S. patent application Ser. No. 13/180,320, filed Jul. 11, 2011; Co-Pending U.S. patent application Ser. No. 13/492,857, filed Jun. 9, 2012; Co-Pending U.S. patent application Ser. No. 13/181,495, filed Jul. 12, 2011; Co-Pending U.S. patent application Ser. No. 13/952,532, filed on Jul. 26, 2013, and titled “Radio Signal Pickup From An Electrically Conductive Substrate Utilizing Passive Slits”; Co-Pending U.S. patent application Ser. No. 14/144,517, filed on Dec. 30, 2013, and titled “Methods, Systems and Apparatus to Affect RF Transmission From a Non-Linked Wireless Client”; Co-Pending U.S. patent application Ser. No. 13/802,409, filed Mar. 13, 2013; and U.S. Pat. No. 8,446,275, issued on May 21, 2013, and titled “General Health And Wellness Management Method And Apparatus For A Wellness Application Using Data From A Data-Capable Band”; all of which are herein incorporated by reference in their entirety for all purposes.
The present application relates generally to electrical and electronic hardware, computer software, wired and wireless network communications, and computing devices. More specifically, techniques for a wireless enabled cap for a data-capable device are described.
More and more functionalities are being introduced into wearable devices. Conventional wearable devices, such as a data-capable band, are being implemented as data capture devices, and are beginning to include a multitude of components to increase functionality. Such components include a multitude of sensors, PCBAs, other circuits, complex user interfaces, volatile and non-volatile memory, and multifaceted communications capabilities. It is becoming increasingly desirable to implement all of these functionalities into smaller and smaller profile devices, and to create structural elements of a wearable device that may support multiple functions.
Thus, what is needed is a solution for a wireless enabled cap for a data-capable device without the limitations of conventional techniques.
Various embodiments of the present application are disclosed in the following detailed description and the accompanying drawings:
Although the above-described drawings depict various examples of the present application, the present application is not limited by the depicted examples. It is to be understood that, in the drawings, like reference numerals designate like structural elements. Also, it is understood that the drawings are not necessarily to scale.
Various embodiments or examples may be implemented in numerous ways, including as a system, a process, an apparatus, a user interface, or a series of program instructions on a non-transitory computer readable medium such as a non-transitory computer readable storage medium or a computer network where the program instructions are sent over optical, electronic, or wireless communication links. In general, operations of disclosed processes may be performed in an arbitrary order, unless otherwise provided in the claims.
A detailed description of one or more examples is provided below along with accompanying figures. The detailed description is provided in connection with such examples, but is not limited to any particular example. The scope is limited only by the claims and numerous alternatives, modifications, and equivalents are encompassed. Numerous specific details are set forth in the following description in order to provide a thorough understanding. These details are provided for the purpose of example and the described techniques may be practiced according to the claims without some or all of these specific details. For clarity, technical material that is known in the technical fields related to the examples has not been described in detail to avoid unnecessarily obscuring the description.
In some examples, the described techniques may be implemented as a computer program or application (“application” or “APP”) or as a plug-in, module, or sub-component of another application. The described techniques may be implemented as software, hardware, firmware, circuitry, or a combination thereof. If implemented as software, then the described techniques may be implemented using various types of programming, development, scripting, or formatting languages, frameworks, syntax, applications, protocols, objects, or techniques, including ASP, ASP.net, .Net framework, Ruby, Ruby on Rails, C, Objective C, C++, C#, Adobe® Integrated Runtime™ (Adobe® AIR™) ActionScript™, Flex™, Lingo™, Java™, Javascript™, Ajax, Perl, COBOL, Fortran, ADA, XML, MXML, HTML, DHTML, XHTML, HTTP, XMPP, PHP, and others. Software and/or firmware implementations may be embodied in a non-transitory computer readable medium configured for execution by a general purpose computing system or the like. The described techniques may be varied and are not limited to the examples or descriptions provided.
For example, band 102 may be implemented as a wearable data capture device, including one or more sensors (e.g., sensor(s) 418 in
In other examples, band 102 also may be configured to capture data from distributed sources (e.g., by communicating with mobile computing devices, other bands 102, mobile communications devices, wireless client devices (e.g., a smartphone or tablet), computers, laptops, tablets, pads, distributed sensors, GPS satellites, or the like) for processing with sensor data. Band 102 may wirelessly transmit sensor data (e.g., motion signals, biometric signals) to external wireless devices and/or wireless systems (e.g., other bands 102, wireless client devices, etc.), and may wirelessly receive data including sensor data from external wireless devices and/or wireless systems (e.g., from other bands 102, wireless client devices, etc.). Processing and/or storage of data (e.g., sensor data) may occur internal to band 102, external to band 102 or both. For example, resource 199 may be an external system that may include or have access to a data storage system 197 (e.g., a hard drive, SSD, RAID, NAS) and a compute engine 198 (e.g., a PC, a server, laptop, tablet, etc.). As another example, device 112 or device 114 may be an external system that may include data storage and computing resources that may be accessed by band 102.
In some examples, one or both of band 102 and cap 104 may be configured to communicate wirelessly 126 with other wireless devices, wireless systems, or applications, including, without limitation, mobile device 112 (e.g., a wireless client device such as a smartphone), laptop 114, tablet or pad 116, headset 118, miscellaneous application 120, one or more other bands 102a, resource 199 (e.g., the Cloud or the Internet), and the like. In some examples, cap 104 and/or band (102, 102a) may wirelessly communicate with other wireless devices or systems using another wireless device (e.g., 112 or 116) as an intermediary transceiver (e.g., a RF relay station), such as wireless communication between band/cap (102, 104) and resource 199 via device 112 using wireless links 126 and 146, or wireless communication between band/cap (102, 104) and band/cap 102a/104 via device 116 using wireless links 126 and 136. In some examples, wireless tag 106 may be implemented as a wireless controller configured to exchange data with said other wireless devices, for example, using short-range communication protocols (e.g., Bluetooth® (BT), Bluetooth® Low Energy (BTLE), ultra wideband, near field communication (NFC), or the like) or longer-range communication protocols (e.g., satellite, mobile broadband (e.g., 5G, 4G, 3G, 2G or the like), other cellular networks, GPS, one or more varieties of IEEE 802.x such as 802.11a/b/g/n (WiFi), WiMAX, other wireless local area network (WLAN), and the like). In some examples, cap 104 may be enabled with near-field communications (NFC) capabilities (e.g., from a NFC chip), and thus may be able to establish a two-way radio communication with another NFC-enabled device through touching the two devices together, or bringing them into close enough proximity to establish an NFC connection (e.g., a few centimeters or other close distance sufficient for establishing an NFC link).
For example, cap 104 may include a wireless or NFC tag, card or chip (hereinafter “tag”) 106, which may be configured to provide stored data, including data stored using microchip 108, using a radio frequency (RF) field. In some examples, wireless tag 106 may include microchip 108 and antenna 110, which may be electrically coupled to (e.g., able to transfer electrical energy or an electrical signal to and from) each other. In some examples, microchip 108 also may be electrically coupled to one or more other components of band 102. In some examples, wireless tag 106 may be implemented as an unpowered NFC tag, which may be powered or activated by coming within a threshold proximity (e.g., a few centimeters or other close distance sufficient for establishing an NFC link) of a powered NFC device (e.g., band 102, mobile device 112, laptop 114, tablet 116, headset 118, miscellaneous application 120, or the like). Once within a threshold proximity of a powered NFC device, wireless tag 106 may take one or more actions including but not limited to provide data, such as a biometric identifier, other identifier, verification information, authentication information, control data to cause an application (e.g., run or operated using mobile device 112, laptop 114, tablet 116, headset 118, miscellaneous application 120, or the like) to open, to pair Bluetooth® devices, to sync Bluetooth® devices, to turn on Bluetooth® or WiFi capabilities in band 102, to accept programming, to accept re-programming, to accept configuration, to accept re-configuration, to accept software updates, to accept operating system (OS) updates, to sync band 102 with an application (e.g., run or operated using mobile device 112, laptop 114, tablet 116, headset 118, miscellaneous application 120, or the like), to modify settings on another device, or the like), or other discreet stored data, to one or more of band 102, mobile device 112, laptop 114, tablet 116, headset 118, resource 199, miscellaneous application 120. In other examples, wireless tag 106 may include other wireless controller circuits. In still other examples, the quantity, type, function, structure, and configuration of the elements shown may be varied and are not limited to the examples provided. In still other examples, the quantity, type, function, structure, and configuration of the elements shown may be varied and are not limited to the examples provided.
In some examples, microchip 108 may be a passive electrical device that may not receive electrical power directly from band 102 or any circuitry or power source(s) in band 102. As one example, microchip 108 may include circuitry to passively receive electrical power from an external source other than circuitry or power sources in the band 102. The external source may be an externally generated RF signal that is electrically coupled with the microchip 108 through an antenna, such as antenna 110, for example. A device having a radio or the like that may generate an RF signal, such as devices 112, 114, 116, or 118 depicted in
In some examples, band 102 may be implemented with cap 104, which may be removably coupled to band 102. As used herein, “coupled” may be used to refer to electrical coupling, physical coupling, or both. For example, cap 104 may be configured to snap onto and off of an end of band 102. In another example, cap 104 may be tethered or leashed (not shown) to band 102 such that it may be uncapped, and still remain coupled to band 102. In some examples, cap 104 may be configured to cover a plug (e.g., plug 212 in
In some examples, cap 202 and plate 204 may be molded using any type of suitable material, including plastics, thermoplastics, thermoplastic elastomers (TPEs), polymers, elastomers, or any other organic or inorganic material. The material may be molded to form 202 and/or 204, for example. In some examples, cap 202 and plate 204 may be integrally molded as a monolithic cap. In some examples, microchip 208 may be mounted on (e.g., using insert molding, other molding techniques, or the like), embedded within, or otherwise disposed on, (hereinafter collectively “disposed on”) any side or surface (e.g., interior or exterior side) of, or within any wall of, inner housing 216 or outer housing 218. In some examples, multi-purpose antenna 210 may be disposed on plate 204, which may be configured to cover, or form a top side and surface of, or otherwise couple with, cap 202. In some examples, multi-purpose antenna 210 may be formed using conductive ink embedded, or disposed, onto plate 204, for example, in the shape of a logo or text (e.g., see 1230 in
In some examples, cap 304 may include opening 320, which may be configured to open into a cavity configured to receive a plug (e.g., plug 212 in
In some examples, cap 306 may include antennas 312a-312c, disposed on a top surface of inner housing 306a. In other examples, antennas 312a-312c may be disposed on a different surface (e.g., inner or outer, side or bottom, or the like) of inner housing 306a. In still other examples, antennas 312a-312c may be disposed on a side of outer housing 306b. In some examples, cap 306 also may include microchip 318, disposed on a side (e.g., inner or outer, side, top or bottom, or the like) of outer housing 306b. In other examples, microchip 318 may be disposed on a side of inner housing 306a. In some examples, antennas 312a-312c may be electrically coupled to microchip 318. In other examples, the quantity, type, function, structure, and configuration of the elements shown may be varied and are not limited to the examples provided.
In some examples, microchips 314-318 each also may be electrically coupled, wired or wirelessly, with one or more components of a band (e.g., band 102 in
In some examples, cap 402 may include a housing (e.g., inner housing 216 and outer housing 218 in
According to some examples, computing platform 500 performs specific operations by processor 504 executing one or more sequences of one or more instructions stored in system memory 506 (e.g., a non-transitory computer readable medium such as Flash memory or the like), and computing platform 500 may be implemented in a client-server arrangement, peer-to-peer arrangement, or as any mobile computing device, including smart phones and the like. Such instructions or data may be read into system memory 506 from another non-transitory computer readable medium, such as storage device 508. In some examples, hard-wired circuitry may be used in place of or in combination with software instructions for implementation. Instructions may be embedded in software or firmware. The term “computer readable medium” refers to any non-transitory medium that participates in providing instructions to processor 504 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks and the like. Volatile media includes dynamic memory, such as system memory 506.
Common forms of non-transitory computer readable media may include, for example, floppy disk, flexible disk, hard disk drive (HDD), solid state disk (SSD), magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, Flash Memory, FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer may read. Instructions may further be transmitted or received using a transmission medium. The term “transmission medium” may include any tangible or intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 502 for transmitting a computer data signal.
In some examples, execution of the sequences of instructions may be performed by computing platform 500. According to some examples, computing platform 500 may be coupled by communication link 521 (e.g., a wired network, such as LAN, PSTN, or any wireless network) to any other processor to perform the sequence of instructions in coordination with (or asynchronous to) one another. Computing platform 500 may transmit and receive messages, data, and instructions, including program code (e.g., application code) through communication link 521 and communication interface 513. Received program code may be executed by processor 504 as it is received, and/or stored in memory 506 or other non-volatile storage for later execution.
In the example shown, system memory 506 may include various modules that include executable instructions to implement functionalities described herein. As depicted in
As hardware and/or firmware, the above-described structures and techniques may be implemented using various types of programming or integrated circuit design languages, including but not limited to hardware description languages, such as any register transfer language (“RTL”) configured to design field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”), multi-chip modules, digital circuitry, analog circuitry, mixed-analog-digital circuitry, radio frequency (RF) circuitry, or any other type of integrated circuit. At least one of the elements in
According to some embodiments, the term “circuit” may refer, for example, to any system including a number of components through which current flows to perform one or more functions, the components including discrete and complex components. Examples of discrete components include transistors, resistors, capacitors, inductors, diodes, and the like, and examples of complex components include memory, processors, analog circuits, digital circuits, and the like, including field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”). Therefore, a circuit may include a system of electronic components and logic components (e.g., logic configured to execute instructions, such that a group of executable instructions of an algorithm, for example, and, thus, is a component of a circuit). According to some embodiments, the term “module” may refer, for example, to an algorithm or a portion thereof, and/or logic implemented in either hardware circuitry or software, or a combination thereof (e.g., a module may be implemented as a circuit). In some embodiments, algorithms and/or the memory in which the algorithms are stored are “components” of a circuit. Thus, the term “circuit” may also refer, for example, to a system of components, including algorithms. These may be varied and are not limited to the examples or descriptions provided.
Here, in flow 600, at the stage 602, the receiving the wireless signal by the wireless cap using the multipurpose antenna (e.g., 110) may include the wireless signal coupling with the antenna to generate a signal that is electrically coupled with the microchip 108 to cause the microchip 108 (e.g., the passively powered microchip) to be powered by the signal while the signal is persistent, as was described above. The electrical power generated by the wireless signal coupling with the antenna may operate to power the microchip 108 to generate the instruction using circuitry at the stage 604 and/or transmit the instruction at the stage 606.
Attention is now directed to
Cap 704 is depicted mounted to the band 702. Mounting may be accomplished by inserting plug 212 into a cavity 720 of cap 704. Cap 704 may include one or more structures (e.g., 811) configured to retain the cap 704 on the plug as will be described below in reference to
Chip 750 may comprise a wireless component such as a NFC chip, NFC tag, or the like. For example, chip 750 may comprise a NTAG203 NFC chip or other device for use in a NFC enabled device, such as cap (104, 704, 904). Chip 750 may conform to a protocol or standard such as that of the NFC Forum or other NFC standards for wireless devices. Chip 750 may be an ASIC that is custom designed for an application specific NFC device. Dimensions for chip 750 will be application specific; however, a typical die (e.g., from a semiconductor wafer) for chip 750 may be about 5 mm or less on a side (e.g., 2 mm by 2 mm or less). Accordingly, a cavity (e.g., 740, 940) in which the chip 750 is mounted in cap (104, 704, 904) may be dimensioned accordingly to accommodate mounting of the chip 750 in the cavity or other structure in the cap (104, 704, 904) that receives the chip 750. Chip 750 may comprise one of the above described chips (e.g., 108, 208, 318, 408, or 514) for a wireless NFC tag (e.g., 510, 404, or 106). The cap 704 when mounted or otherwise connected with a device, such as band 702 (see
In
In some examples, antenna 730 may be embedded in the structure 735 as depicted by antenna 730b. In yet other examples, antenna 730 may be embedded in the first material (e.g., 730 and/or 730a) and may also be embedded in the structure 735 as depicted by antenna 730b in configuration 800d (e.g., see antennas 730, 730a, 730b which may be embedded in materials 1131 and/or 1135 in configuration 1100a of
Moving on to
Antenna 930 may include a structure 951 operative to receive the chip 750. Structure 951 may be formed from the same material as antenna 930 or may be made from a different material (e.g., an electrically insulating material) that is connected with antenna 930. Structure 951 may be operative to align chip 750 and antenna 930 with each other to facilitate electrical connection (e.g., via soldering, etc.) of electrically conductive nodes on chip 750 with electrically conductive nodes on antenna 930. For example, the nodes may comprise pads, bumps, balls, or other electrically conductive structures. Structure 951 may be configured to fit inside cavity 940 when antenna 930 is positioned on first material 933. In
Attention is now directed to
Referring now to
RF isolation structure 1150 may comprise a ferrite coil, a ferrite core, tape wound core, or other type of RF isolation devices (e.g., made from high magnetic permeability and low electrical conductivity materials) operative to isolate antenna 730 and/or improve RF performance of the antenna 930 and/or chip 750. In some examples, metallic structures (e.g., plugs 212, 912) or other structures in close proximity of antenna 730 may interfere with RF signal reception by antenna 730. For example, in
Attention is now directed to
In example 1200c, cap 704 may include the logo antenna 1230, another antenna 1230a, or both. Antenna 1230a may be a flexible PC board, or some other electrically conductive substrate that is electrically coupled with chip 750 (not shown) and positioned on a structure 1241, for example. Either one or both of the antennas 1230, 1230a, may be used for the aforementioned wireless communications (126, 136). In example 1200d, the components of example 1200c may be coupled to form cap 704. Other embedded and/or non-embedded antennas (not shown) may be included in the cap 704 depicted in examples 1200a-1200d, such as those depicted in
The foregoing description, for purposes of explanation, uses specific nomenclature to provide a thorough understanding of the present application. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the present application. In fact, this description should not be read to limit any feature or aspect of the present application to any embodiment; rather features and aspects of one embodiment may readily be interchanged with other embodiments. Notably, not every benefit described herein need be realized by each embodiment of the present application; rather any specific embodiment may provide one or more of the advantages discussed above. In the claims, elements and/or operations do not imply any particular order of operation, unless explicitly stated in the claims. It is intended that the following claims and their equivalents define the scope of the present application. Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described inventive techniques are not limited to the details provided. There are many alternative ways of implementing the above-described present application techniques. The disclosed examples are illustrative and not restrictive.
Number | Name | Date | Kind |
---|---|---|---|
4788627 | Ehlert et al. | Nov 1988 | A |
4819860 | Hargrove et al. | Apr 1989 | A |
5019673 | Juskey et al. | May 1991 | A |
5246643 | Inaba et al. | Sep 1993 | A |
5426130 | Thurber et al. | Jun 1995 | A |
5692501 | Minturn | Dec 1997 | A |
5924979 | Swedlow et al. | Jul 1999 | A |
5974262 | Fuller et al. | Oct 1999 | A |
6139494 | Caimes | Oct 2000 | A |
6156461 | Grenon et al. | Dec 2000 | A |
D439981 | Kasabach et al. | Apr 2001 | S |
6246900 | Cosman et al. | Jun 2001 | B1 |
6254815 | Cheperak | Jul 2001 | B1 |
D451604 | Kasabach et al. | Dec 2001 | S |
6356940 | Short | Mar 2002 | B1 |
D460971 | Sica et al. | Jul 2002 | S |
6486801 | Jones | Nov 2002 | B1 |
6527711 | Stivoric et al. | Mar 2003 | B1 |
6595929 | Stivoric et al. | Jul 2003 | B2 |
6605038 | Teller et al. | Aug 2003 | B1 |
6665174 | Derr et al. | Dec 2003 | B1 |
6714859 | Jones | Mar 2004 | B2 |
6904359 | Jones | Jun 2005 | B2 |
6952645 | Jones | Oct 2005 | B1 |
6984886 | Ahn et al. | Jan 2006 | B2 |
7020508 | Stivoric et al. | Mar 2006 | B2 |
7030781 | Jones | Apr 2006 | B2 |
7060216 | Schuumans | Jun 2006 | B2 |
7101752 | Park et al. | Sep 2006 | B2 |
7153262 | Stivoric et al. | Dec 2006 | B2 |
7196972 | Pitocco et al. | Mar 2007 | B2 |
7261690 | Teller et al. | Aug 2007 | B2 |
7276802 | Hall et al. | Oct 2007 | B2 |
7285090 | Stivoric et al. | Oct 2007 | B2 |
7306567 | Loree, IV | Dec 2007 | B2 |
7336187 | Hubbard et al. | Feb 2008 | B2 |
7343260 | Kahn et al. | Mar 2008 | B1 |
7364445 | Ni et al. | Apr 2008 | B1 |
7400970 | Jones | Jul 2008 | B2 |
7457719 | Kahn et al. | Nov 2008 | B1 |
7502643 | Farringdon et al. | Mar 2009 | B2 |
7647195 | Kahn et al. | Jan 2010 | B1 |
7647196 | Kahn et al. | Jan 2010 | B2 |
7653508 | Kahn et al. | Jan 2010 | B1 |
7655508 | Johnson et al. | Feb 2010 | B2 |
7662065 | Kahn et al. | Feb 2010 | B1 |
7689437 | Teller et al. | Mar 2010 | B1 |
7690556 | Kahn et al. | Apr 2010 | B1 |
7705723 | Kahn et al. | Apr 2010 | B2 |
7723162 | Anderson et al. | May 2010 | B2 |
7733224 | Tran | Jun 2010 | B2 |
7747735 | Kahn et al. | Jun 2010 | B1 |
7753861 | Kahn et al. | Jul 2010 | B1 |
7766794 | Oliver et al. | Aug 2010 | B2 |
7769187 | Farrar et al. | Aug 2010 | B1 |
7788059 | Kahn et al. | Aug 2010 | B1 |
7800044 | Kahn et al. | Sep 2010 | B1 |
7839279 | Kahn et al. | Nov 2010 | B2 |
7841967 | Kahn et al. | Nov 2010 | B1 |
7849184 | Kahn et al. | Dec 2010 | B1 |
D631552 | Kasabach et al. | Jan 2011 | S |
D632396 | Kasabach et al. | Feb 2011 | S |
7881902 | Kahn et al. | Feb 2011 | B1 |
7907901 | Kahn et al. | Mar 2011 | B1 |
7917768 | Kahn et al. | Mar 2011 | B2 |
7959567 | Stivoric et al. | Jun 2011 | B2 |
7970586 | Kahn et al. | Jun 2011 | B1 |
7982770 | Kahn et al. | Jul 2011 | B1 |
7987070 | Kahn et al. | Jul 2011 | B2 |
7993276 | Nazarian et al. | Aug 2011 | B2 |
D645968 | Kasabach et al. | Sep 2011 | S |
8040382 | Kahn et al. | Oct 2011 | B2 |
8047966 | Dorogusker et al. | Nov 2011 | B2 |
8049614 | Kahn et al. | Nov 2011 | B2 |
8064759 | Kahn et al. | Nov 2011 | B1 |
8073707 | Teller et al. | Dec 2011 | B2 |
8083643 | Ng et al. | Dec 2011 | B2 |
8096960 | Loree, IV et al. | Jan 2012 | B2 |
20010004234 | Petelenz et al. | Jun 2001 | A1 |
20010037179 | Vock et al. | Nov 2001 | A1 |
20020019584 | Schulze et al. | Feb 2002 | A1 |
20020068873 | Nissila | Jun 2002 | A1 |
20020074877 | Lee et al. | Jun 2002 | A1 |
20020143491 | Scherzinger | Oct 2002 | A1 |
20020145571 | Hulick et al. | Oct 2002 | A1 |
20020183646 | Stivoric et al. | Dec 2002 | A1 |
20030046228 | Berney | Mar 2003 | A1 |
20030130595 | Mault | Jul 2003 | A1 |
20030137588 | Wang et al. | Jul 2003 | A1 |
20030236474 | Singh | Dec 2003 | A1 |
20040147818 | Levy et al. | Jul 2004 | A1 |
20040152957 | Stivoric et al. | Aug 2004 | A1 |
20040167409 | Lo et al. | Aug 2004 | A1 |
20050113650 | Pacione et al. | May 2005 | A1 |
20050140005 | Huang et al. | Jun 2005 | A1 |
20050245839 | Stivoric et al. | Nov 2005 | A1 |
20060065645 | Nakasu et al. | Mar 2006 | A1 |
20060074279 | Brover | Apr 2006 | A1 |
20060079740 | Silver et al. | Apr 2006 | A1 |
20060122474 | Teller et al. | Jun 2006 | A1 |
20060132477 | Kerr et al. | Jun 2006 | A1 |
20060224051 | Teller et al. | Oct 2006 | A1 |
20060237252 | Mobley et al. | Oct 2006 | A1 |
20070027370 | Brauker et al. | Feb 2007 | A1 |
20070072156 | Kaufman et al. | Mar 2007 | A1 |
20070105404 | Lee et al. | May 2007 | A1 |
20070173705 | Teller et al. | Jul 2007 | A1 |
20070185391 | Morgan | Aug 2007 | A1 |
20070186429 | Bonnet et al. | Aug 2007 | A1 |
20070197878 | Shklarski | Aug 2007 | A1 |
20070253602 | Amano | Nov 2007 | A1 |
20070254137 | Koppe et al. | Nov 2007 | A1 |
20070296571 | Kolen | Dec 2007 | A1 |
20080004904 | Tran | Jan 2008 | A1 |
20080032119 | Feldhahn et al. | Feb 2008 | A1 |
20080040615 | Carper et al. | Feb 2008 | A1 |
20080055074 | Gao et al. | Mar 2008 | A1 |
20080091089 | Guillory et al. | Apr 2008 | A1 |
20080154098 | Morris et al. | Jun 2008 | A1 |
20080167535 | Stivoric et al. | Jul 2008 | A1 |
20080176655 | James et al. | Jul 2008 | A1 |
20080183388 | Goodrich | Jul 2008 | A1 |
20080194928 | Bandic et al. | Aug 2008 | A1 |
20080208015 | Morris et al. | Aug 2008 | A1 |
20080216171 | Sano | Sep 2008 | A1 |
20080255979 | Slutzky et al. | Oct 2008 | A1 |
20080275309 | Stivoric et al. | Nov 2008 | A1 |
20090006458 | Stivoric et al. | Jan 2009 | A1 |
20090019374 | Logan et al. | Jan 2009 | A1 |
20090072955 | Cary | Mar 2009 | A1 |
20090076343 | James et al. | Mar 2009 | A1 |
20090077849 | Glass, Jr. et al. | Mar 2009 | A1 |
20090112626 | Talbot et al. | Apr 2009 | A1 |
20090118100 | Oliver et al. | May 2009 | A1 |
20090131759 | Sims et al. | May 2009 | A1 |
20090146947 | Ng | Jun 2009 | A1 |
20090150178 | Sutton et al. | Jun 2009 | A1 |
20090163774 | Thatha et al. | Jun 2009 | A1 |
20090192362 | Sweeney | Jul 2009 | A1 |
20090208756 | Kimura et al. | Aug 2009 | A1 |
20090218725 | Thelemann et al. | Sep 2009 | A1 |
20090264714 | Chou | Oct 2009 | A1 |
20090265183 | Pollard et al. | Oct 2009 | A1 |
20090292180 | Mirow | Nov 2009 | A1 |
20090311976 | Vanderaa et al. | Dec 2009 | A1 |
20090319221 | Kahn et al. | Dec 2009 | A1 |
20090319347 | Albrecht | Dec 2009 | A1 |
20100004947 | Nadeau et al. | Jan 2010 | A1 |
20100030578 | Siddique et al. | Feb 2010 | A1 |
20100041772 | Liversage et al. | Feb 2010 | A1 |
20100056878 | Partin et al. | Mar 2010 | A1 |
20100070867 | Lemmers | Mar 2010 | A1 |
20100119461 | Bicard-Benhamou et al. | May 2010 | A1 |
20100137106 | Oshima et al. | Jun 2010 | A1 |
20100156007 | Huang et al. | Jun 2010 | A1 |
20100217099 | LeBoeuf et al. | Aug 2010 | A1 |
20100221188 | Clark et al. | Sep 2010 | A1 |
20100240962 | Contant | Sep 2010 | A1 |
20100241465 | Amigo et al. | Sep 2010 | A1 |
20100268056 | Picard et al. | Oct 2010 | A1 |
20100279554 | Steijner | Nov 2010 | A1 |
20100284552 | Lasarov et al. | Nov 2010 | A1 |
20100305642 | Dong et al. | Dec 2010 | A1 |
20100315225 | Teague | Dec 2010 | A1 |
20100331146 | Kil | Dec 2010 | A1 |
20100331682 | Stein et al. | Dec 2010 | A1 |
20110004072 | Fletcher et al. | Jan 2011 | A1 |
20110010188 | Yoshikawa et al. | Jan 2011 | A1 |
20110046519 | Raheman | Feb 2011 | A1 |
20110054359 | Sazonov et al. | Mar 2011 | A1 |
20110066064 | Jangle et al. | Mar 2011 | A1 |
20110071003 | Watterson et al. | Mar 2011 | A1 |
20110087115 | Sackner et al. | Apr 2011 | A1 |
20110095916 | Kass et al. | Apr 2011 | A1 |
20110106627 | Le Boeuf et al. | May 2011 | A1 |
20110125063 | Shalon et al. | May 2011 | A1 |
20110160544 | Hayter | Jun 2011 | A1 |
20110184247 | Contant et al. | Jul 2011 | A1 |
20110230732 | Edman et al. | Sep 2011 | A1 |
20110245633 | Goldberg et al. | Oct 2011 | A1 |
20120313773 | Loree, IV | Dec 2012 | A1 |
20130095941 | Bentley et al. | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
2413148 | Dec 2001 | CA |
2413220 | Dec 2001 | CA |
2441962 | Oct 2002 | CA |
2454655 | Feb 2003 | CA |
2496579 | Mar 2004 | CA |
2560323 | Oct 2005 | CA |
1414340 | May 2004 | EP |
1534126 | Jun 2005 | EP |
1639939 | Mar 2006 | EP |
1702560 | Sep 2006 | EP |
1734858 | Dec 2006 | EP |
1743571 | Jan 2007 | EP |
2126828 | Dec 2009 | EP |
2358266 | Aug 2011 | EP |
153516 | Jul 2007 | IL |
160079 | Feb 2009 | IL |
153478 | Mar 2009 | IL |
158067 | Aug 2009 | IL |
167045 | Apr 2010 | IL |
178183 | Dec 2013 | IL |
200251105 | Sep 2002 | JP |
2004-500949 | Jan 2004 | JP |
2005-536260 | Dec 2005 | JP |
200750091 | Mar 2007 | JP |
4125132 | Jul 2008 | JP |
4283672 | Jun 2009 | JP |
1020027017160 | Dec 2002 | KR |
1020027017525 | Dec 2002 | KR |
1020037012845 | Sep 2003 | KR |
102004001744 | Feb 2004 | KR |
1020057003029 | Feb 2005 | KR |
PA2005002024 | Jun 2005 | MX |
WO0196986 | Dec 2001 | WO |
WO0200111 | Jan 2002 | WO |
WO02078538 | Oct 2002 | WO |
WO03015005 | Feb 2003 | WO |
WO2004019172 | Mar 2004 | WO |
WO2005016124 | Feb 2005 | WO |
WO2005092177 | Oct 2005 | WO |
WO2008101248 | Aug 2008 | WO |
WO2010064162 | Jun 2010 | WO |
WO2010065067 | Jun 2010 | WO |
WO2011046657 | Apr 2011 | WO |
Entry |
---|
U.S. Appl. No. 61/630,064, Ram David Adva Fish. |
U.S. Appl. No. 61/627,891, Ram David Adva Fish. |
U.S. Appl. No. 61/572,206, Rahman et al. |
U.S. Appl. No. 61/572,204, Rahman et al. |
U.S. Appl. No. 61/516,480, Fish et al. |
U.S. Appl. No. 61/516,479, Fish et al. |
U.S. Appl. No. 61/516,478, Fish et al. |
U.S. Appl. No. 61/516,477, Ram David Adva Fish. |
U.S. Appl. No. 61/511,541, Jeffery Miao. |
U.S. Appl. No. 61/507,091, Rahman et al. |
U.S. Appl. No. 61/495,997, Drysdale et al. |
U.S. Appl. No. 61/495,996, Drysdale et al. |
U.S. Appl. No. 61/495,995, Drysdale et al. |
U.S. Appl. No. 61/495,994, Drysdale et al. |
U.S. Appl. No. 61/404,381, Ram David Adva Fish. |
U.S. Appl. No. 61/404,379, Fish et al. |
U.S. Appl. No. 61/210,862, Ram David Adva Fish. |
U.S. Appl. No. 61/210,821, Ram David Adva Fish. |
U.S. Appl. No. 60/958,516, Andre et al. |
U.S. Appl. No. 60/901,952, Stivoric et al. |
U.S. Appl. No. 60/729,683, Stivoric et al. |
U.S. Appl. No. 60,729,663, Donald G. Stein. |
U.S. Appl. No. 60/727,357, Pacione et al. |
U.S. Appl. No. 60/555,280, Pacione et al. |
U.S. Appl. No. 60/510,013, Farringdon et al. |
U.S. Appl. No. 60/502,764, Stivoric et al. |
U.S. Appl. No. 60/502,746, Bucher et al. |
U.S. Appl. No. 60/417,163, Andre et al. |
U.S. Appl. No. 13/405,241, Rahman et al. |
U.S. Appl. No. 13/361,919, Rahman et al. |
U.S. Appl. No. 13/253,000, Ram David Adva Fish. |
U.S. Appl. No. 13/247,975, Sashittal et al. |
U.S. Appl. No. 13/181,513, Rahman et al. |
U.S. Appl. No. 13/181,512, Rahman et al. |
U.S. Appl. No. 13/181,511, Rahman et al. |
U.S. Appl. No. 13/181,500, Rahman et al. |
U.S. Appl. No. 13/181,498, Rahman et al. |
U.S. Appl. No. 13/181,495, Rahman et al. |
U.S. Appl. No. 13/181,486, Rahman et al. |
U.S. Appl. No. 13/180,320, Rahman et al. |
U.S. Appl. No. 13/180,000, Rahman et al. |
U.S. Appl. No. 13/158,416, Drysdale et al. |
U.S. Appl. No. 13/135,728, Drysdale et al. |
U.S. Appl. No. 11/876,601, Stivoric et al. |
U.S. Appl. No. 10/638,588, filed Feb. 19, 2004, Teller et al. |
U.S. Appl. No. 10/682,293, filed Jul. 8, 2004, Teller et al. |
U.S. Appl. No. 11/239,748, filed Nov. 23, 2006, Stivoric et al. |
U.S. Appl. No. 11/481,147, filed Feb. 15, 2007, Stivoric et al. |
U.S. Appl. No. 11/582,896, filed May 3, 2007, Stivoric et al. |
U.S. Appl. No. 11/930,091, filed Jul. 3, 2008, Teller et al. |
U.S. Appl. No. 11/930,081, filed Jul. 3, 2008, Teller et al. |
U.S. Appl. No. 11/928,027, filed Jul. 3, 2008, Stivoric et al. |
U.S. Appl. No. 11/930,101, filed Jul. 10, 2008, Teller et al. |
U.S. Appl. No. 11/930,053, filed Jul. 10, 2008, Teller et al. |
U.S. Appl. No. 11/930,048, filed Jul. 10, 2008, Teller et al. |
U.S. Appl. No. 11/930,036, filed Jul. 10, 2008, Teller et al. |
U.S. Appl. No. 11/928,051, filed Jul. 10, 2008, Stivoric et al. |
U.S. Appl. No. 11/928,039, filed Jul. 10, 2008, Stivoric et al. |
U.S. Appl. No. 11/930,100, filed Jul. 17, 2008, Teller et al. |
U.S. Appl. No. 11/930,094, filed Jul. 17, 2008, Teller et al. |
U.S. Appl. No. 11/930,092, filed Jul. 17, 2008, Teller et al. |
U.S. Appl. No. 11/925,965, filed Jul. 17, 2008, Stivoric et al. |
U.S. Appl. No. 11/925,908, filed Jul. 17, 2008, Teller et al. |
U.S. Appl. No. 11/930,405, filed Jul. 24, 2008, Teller et al. |
U.S. Appl. No. 11/928,302, filed Jul. 31, 2008, Farringdon et al. |
U.S. Appl. No. 11/925,906, filed Jul. 31, 2008, Teller et al. |
U.S. Appl. No. 11/925,903, filed Jul. 31, 2008, Teller et al. |
U.S. Appl. No. 11/928,059, filed Sep. 4, 2008, Stivoric et al. |
U.S. Appl. No. 11/927,365, filed Nov. 20, 2008, Stivoric et al. |
U.S. Appl. No. 11/927,276, filed Nov. 20, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,766, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,760, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,753, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,751, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,746, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,741, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,737, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,731, filed Dec. 25, 2008, Stivoric et al. |
U.S. Appl. No. 12/033,722, filed Jan. 1, 2009, Stivoric et al. |
U.S. Appl. No. 11/871,151, filed Apr. 16, 2009, Kahn et al. |
U.S. Appl. No. 11/925,902, filed May 7, 2009, Teller et al. |
U.S. Appl. No. 12/217,299, filed Jul. 9, 2009, Stivoric et al. |
U.S. Appl. No. 12/113,110, filed Nov. 5, 2009, Kahn et al. |
U.S. Appl. No. 12/469,633, filed Nov. 26, 2009, Kahn et al. |
U.S. Appl. No. 12/490,304, filed Dec. 24, 2009, Kahn et al. |
U.S. Appl. No. 12/202,206, filed Mar. 4, 2010, Kahn et al. |
U.S. Appl. No. 12/247,950, filed Apr. 8, 2010, Kahn et al. |
U.S. Appl. No. 12/560,069, filed Aug. 26, 2010, Nadkarni et al. |
U.S. Appl. No. 12/730,199, filed Sep. 23, 2010, Ram David Adva Fish. |
U.S. Appl. No. 12/730,194, filed Sep. 23, 2010, Ram David Adva Fish. |
U.S. Appl. No. 12/621,099, filed Sep. 30, 2010, Nadkarni et al. |
U.S. Appl. No. 12/840,109, filed Nov. 11, 2010, Farrington et al. |
U.S. Appl. No. 12/472,361, filed Dec. 2, 2010, Kahn et al. |
U.S. Appl. No. 12/823,280, filed Jan. 6, 2011, Bentley et al. |
U.S. Appl. No. 12/883,304, filed Mar. 17, 2011, Jangle et al. |
U.S. Appl. No. 12/684,881, filed Jul. 14, 2011, Kahn et al. |
U.S. Appl. No. 13/204,658, filed Nov. 24, 2011, Jangle et al. |
U.S. Appl. No. 13/182,352, filed Jan. 5, 2012, Nazarian et al. |
U.S. Appl. No. 13/405,240, filed Feb. 25, 2012, Drysdale et al. |
USPTO Office Action in U. S. Appl. No. 11/925,661, mailed Mar. 30, 2010. |
USPTO Office Action in U.S. Appl. No. 13/427,839, mailed Jul. 12, 2012. |
USPTO Office Action in U.S. Appl. No. 13/405,240, mailed Nov. 29, 2012. |
USPTO Office Action in U.S. Appl. No. 13/181,495, mailed Mar. 28, 2012. |
USPTO Office Action in U.S. Appl. No. 13/181,495, mailed Nov. 21, 2012. |
USPTO Office Action in U.S. Appl. No. 13/361,919, mailed Mar. 23, 2012. |
USPTO Office Action in U.S. Appl. No. 13/361,919, mailed Nov. 6, 2012. |
USPTO Office Action in U.S. Appl. No. 13/405,241, mailed Sep. 21, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/31319; Date of Mailing Jul. 20, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/41964; Date of Mailing Aug. 28, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/31322; Date of Mailing Jul. 13, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40797; Date of Mailing Aug. 10, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/38185; Date of Mailing Aug. 17, 2012. |
Blaine R. Copenheaver; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/039761; Date of Mailing Sep. 7, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/38201; Date of Mailing Jul. 20, 2012. |
Shane Thomas; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/41710; Date of Mailing Aug. 24, 2012. |
Blaine R. Copenheaver; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/41940; Date of Mailing Sep. 13, 2012. |
Blaine R. Copenheaver; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/38410; Date of Mailing Sep. 7, 2012. |
Blaine R. Copenheaver; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/41959; Date of Mailing Sep. 13, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/31325; Date of Mailing Jul. 24, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/41177; Date of Mailing Sep. 14, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40965; Date of Mailing Aug. 1, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/39763; Date of Mailing Aug. 7, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40047; Date of Mailing Aug. 16, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40328; Date of Mailing Aug. 17, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/31326; Date of Mailing Aug. 3, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40812; Date of Mailing Aug. 22, 2012. |
Lee W. Young; Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; International application No. PCT/US 12/40590; Date of Mailing Sep. 7, 2012. |
Lauren Goode; Sleep-Sensor Maker Lark Takes on Nike+ FuelBand With Larklife, All Things Digital, Oct. 8, 2012, The Wall Street Journal. |
Deborah Porterfield; Life Gets Easier with New Tech Accessories, USA Today, Oct. 18, 2012. |
Number | Date | Country | |
---|---|---|---|
20150237461 A1 | Aug 2015 | US |