Digital audio players, such as MP3 players and iPods, that store and play digital audio files, are very popular. Such devices typically comprise a data storage unit for storing and playing the digital audio, and a headphone set that connects to the data storage unit, usually with a ¼″ or a 3.5 mm jack and associated cord. Often the headphones are in-ear type headphones. The cord, however, between the headphones and the data storage unit can be cumbersome and annoying to users, and the length of the cord limits the physical distance between the data storage unit and the headphones. Accordingly, some cordless headphones have been proposed, such as the Monster iFreePlay cordless headphones from Apple Inc., which include a docking port on one of the earphones that can connect directly to an iPod Shuffle. Because they have the docking port, however, the Monster iFreePlay cordless headphones from Apple are quite large and are not in-ear type phones. Recently, cordless headphones that connect wirelessly via IEEE 802.11 to a WLAN-ready laptop or personal computer (PC) have been proposed, but such headphones are also quite large and not in-ear type phones.
In one general aspect, the present invention is directed to a wireless earphone that comprises a transceiver circuit for receiving streaming audio from a data source, such as a digital audio player or a computer, over an ad hoc wireless network. When the data source and the earphone are out of range via the ad hoc wireless network, they may transition automatically to a common infrastructure wireless network (e.g., a wireless LAN). If there is no common infrastructure wireless network for both the data source and the earphone, the earphone may connect via an available infrastructure wireless network to a host server. The host server may, for example, broadcast streaming audio to the earphone and/or transmit to the earphone a network address (e.g., an Internet Protocol (IP) address) for a network-connected content server that streams digital audio. The earphone may then connect to the content server using the IP address. The content server may be an Internet radio server, including, for example, an Internet radio server that broadcasts streaming audio from the data source or some other content.
These and other advantageous, unique aspects of the wireless earphone are described below.
Various embodiments of the present invention are described herein by way of example in conjunction with the following figures.
In one general aspect, the present invention is directed to a wireless earphone that receives streaming audio data via ad hoc wireless networks and infrastructure wireless networks, and that transitions seamlessly between wireless networks. The earphone may comprise one or more in-ear, on-ear, or over-ear speaker elements. Two exemplary in-ear earphone shapes for the wireless earphone 10 are shown in
Although the example earphones 10 shown in
In various embodiments, the user may wear two discrete wireless earphones 10: one in each ear. In such embodiments, each earphone 10 may comprise a transceiver circuit. In such embodiments, the earphones 10 may be connected by a string or some other cord-type connector to keep the earphones 10 from being separated.
In other embodiments, as shown in
In other embodiments, the earphone 10 may comprise a hanger bar 17 that allows the earphone 10 to clip to, or hang on, the user's ear, as shown in the illustrated embodiment of
The wireless network adapter 22 may be an integral part of the data source 20, or it may be a separate device that is connected to the data source 20 to provide wireless connectivity for the data source 20. For example, the wireless network adapter 22 may comprise a wireless network interface card (WNIC) or other suitable transceiver that plugs into a USB port or other port or jack of the data source 20 (such as a TRS connector) to stream data, e.g., digital audio files, via a wireless network (e.g., the ad hoc wireless network 24 or an infrastructure wireless network). The digital audio transmitted from the data source 20 to the earphone 10 via the wireless networks may comprise compressed or uncompressed audio. Any suitable file format may be used for the audio, including mp3, lossy or lossless WMA, Vorbis, Musepack, FLAC, WAV, AIFF, AU, or any other suitable file format.
When in range, the data source 20 may communicate with the earphone 10 via the ad hoc wireless network 24 using any suitable wireless communication protocol, including Wi-Fi (e.g., IEEE 802.11a/b/g/n), WiMAX (IEEE 802.16), Bluetooth, Zigbee, UWB, or any other suitable wireless communication protocol. For purposes of the description to follow, it is assumed that the data source 20 and the earphone 10 communicate using a Wi-Fi protocol, although the invention is not so limited and other wireless communication protocols may be used in other embodiments of the invention. The data source 20 and the earphone 10 are considered in range for the ad hoc wireless network 24 when the signal strengths (e.g., the RSSI) of the signals received by the two devices are above a threshold minimum signal strength level. For example, the data source 20 and the earphone 10 are likely to be in range for an ad hoc wireless network when then are in close proximity, such as when the wearer of the earphone 10 has the data source 20 on his/her person, such as in a pocket, strapped to their waist or arm, or holding the data source in their hand.
When the earphone 10 and the data source 20 are out of range for the ad hoc wireless network 24, that is, when the received signals degrade below the threshold minimum signal strength level, both the earphone 10 and the data source 20 may transition automatically to communicate over an infrastructure wireless network (such as a wireless LAN (WLAN)) 30 that is in the range of both the earphone 10 and the data source 20, as shown in
For example, as shown in
If there is no suitable common infrastructure wireless network over which the earphone 10 and the data source 20 can communicate, as shown in
The digital audio content server 70 may be, for example, an Internet radio station server. The digital audio content server 70 may stream digital audio over the network 42 (e.g., the Internet), which the earphone 10 may receive and process. In one embodiment, the streaming digital audio content server 70 may stream digital audio received by the streaming digital audio content server 70 from the data source 20. For example, where the data source 20 is a wireless-capable device, such as a portable DAP, the data source 20 may connect to the streaming digital audio content server 70 via a wireless network 30b and the network 42. Alternatively, where for example the data source 20 is non-wireless-capable device, such as a PC, the data source 20 may have a direct wired connection to the network 42. After being authenticated by the streaming digital audio content server 70, the data source 20 may stream digital audio to the streaming digital audio content server 70, which may broadcast the received digital audio over the network 42 (e.g., the Internet). In such a manner, the user of the earphone 10 may listen to audio from the data source 20 even when (i) the earphone 10 and the data source 20 are not in communication via an ad hoc wireless network 24 and (ii) the earphone 10 and the data source 20 are not in communication via a common local infrastructure wireless network 30.
In various embodiments, the transceiver circuit 100 may be implemented as a single integrated circuit (IC), such as a system-on-chip (SoC), which is conducive to miniaturizing the components of the earphone 10, which is advantageous if the earphone 10 is to be relatively small in size, such as an in-ear earphone (see
The power source 102 may comprise, for example, a rechargeable or non-rechargeable battery (or batteries). In other embodiments, the power source 102 may comprise one or more ultracapacitors (sometimes referred to as supercapacitors) that are charged by a primary power source. In embodiments where the power source 102 comprises a rechargeable battery cell or an ultracapacitor, the battery cell or ultracapacitor, as the case may be, may be charged for use, for example, when the earphone 10 is connected to a docking station or computer. The docking station may be connected to or part of a computer device, such as a laptop computer or PC. In addition to charging the rechargeable power source 102, the docking station and/or computer may facilitate downloading of data to and/or from the earphone 10. In other embodiments, the power source 102 may comprise capacitors passively charged with RF radiation, such as described in U.S. Pat. No. 7,027,311. The power source 102 may be coupled to a power source control module 103 of transceiver circuit 100 that controls and monitors the power source 102.
The acoustic transducer(s) 106 may be the speaker element(s) for conveying the sound to the user of the earphone 10. According to various embodiments, the earphone 10 may comprise one or more acoustic transducers 106. For embodiments having more than one transducer, one transducer may be larger than the other transducer, and a crossover circuit (not shown) may transmit the higher frequencies to the smaller transducer and may transmit the lower frequencies to the larger transducer. More details regarding dual element earphones are provided in U.S. Pat. No. 5,333,206, assigned to Koss Corporation, which is incorporated herein by reference in its entirety.
The antenna 108 may receive and transmit the wireless signals from and to the wireless networks 24, 30. A RF (e.g., Wi-Fi) module 110 of the transceiver circuit 100 in communication with the antenna 108 may, among other things, modulate and demodulate the signals transmitted from and received by the antenna 108. The RF module 110 communicates with a baseband processor 112, which performs other functions necessary for the earphone 10 to communicate using the Wi-Fi (or other communication) protocol.
The baseband processor 112 may be in communication with a processor unit 114, which may comprise a microprocessor 116 and a digital signal processor (DSP) 118. The microprocessor 116 may control the various components of the transceiver circuit 100. The DSP 114 may, for example, perform various sound quality enhancements to the digital audio received by the baseband processor 112, including noise cancellation and sound equalization. The processor unit 114 may be in communication with a volatile memory unit 120 and a non-volatile memory unit 122. A memory management unit 124 may control the processor unit's access to the memory units 120, 122. The volatile memory 122 may comprise, for example, a random access memory (RAM) circuit. The non-volatile memory unit 122 may comprise a read only memory (ROM) and/or flash memory circuits. The memory units 120, 122 may store firmware that is executed by the processor unit 114. Execution of the firmware by the processor unit 114 may provide various functionality for the earphone 10, such as the automatic transition between wireless networks as described herein. The memory units 120, 122 may also cache received digital audio.
A digital-to-analog converter (DAC) 125 may convert the digital audio from the processor unit 114 to analog form for coupling to the acoustic transducer(s) 106. An I2S interface 126 or other suitable serial or parallel bus interface may provide the interface between the processor unit 114 and the DAC 125. An analog-to-digital converter (ADC) 128, which also communicates with the I2S interface 126, may convert analog audio signals picked up by the microphone 104 for processing by the processor unit 114.
The transceiver circuit 100 also may comprise a USB or other suitable interface 130 that allows the earphone 10 to be connected to an external device via a USB cable or other suitable link. As shown in
According to various embodiments, the earphone 10 may have an associated web page that a user may access through the host server 40 (see
At the web site for the earphone 10 hosted on the host server 40, in addition to establishing the identification of digital audio sources (e.g., IDs for the user's DAP or PC) and earphones, the user could set parental or other user controls. For example, the user could restrict certain Internet radio broadcasts based on content or parental ratings, etc. That is, for example, the user could configure a setting through the web site that prevents the host server 40 from sending an IP address for a streaming digital audio content server 70 that broadcasts explicit content based on a rating for the content. In addition, if a number of different earphones 10 are registered to the same user, the user could define separate controls for the different earphones 10 (as well as customize any other preferences or settings particular to the earphones 10, including Internet radio stations, sound quality settings, etc. that would later be downloaded to the earphones 10). In addition, in modes where the host server 40 streams audio to the earphone 10, the host server 40 may log the files or content streamed to the various earphones 10, and the user could view at the web site the files or content that were played by the earphones 10. In that way, the user could monitor the files played by the earphones 10.
In addition, the host server 40 may provide a so-called eavesdropping function according to various embodiments. The eavesdropping service could be activated via the web site. When the service is activated, the host server 40 may transmit the content that it is delivering to a first earphone 10a to another, second earphone 10b, as shown in
This function also could be present in the earphones 10 themselves, allowing a parent (or other user) to join an ad-hoc wireless network and listen to what their child (or other listener) is hearing. For example, with reference to
At the web site, the user may also specify the identification number (“ID”) of their earphone(s) 10, and the host server 40 may translate the ID to the current internet protocol (IP) addresses for the earphone 10 and for the data source 20. This allows the user to find his or her data source 20 even when it is behind a firewall or on a changing IP address. That way, the host server 40 can match the audio from the data source 20 to the appropriate earphone 10 based on the specified device ID. The user also could specify a number of different data sources 20. For example, the user's DAP may have one specified IP address and the user's home (or work) computer may have another specified IP address. Via the web site hosted by the host server 40, the user could specify or prioritize from which source (e.g., the user's DAP or computer) the earphone 10 is to receive content.
The host server 40 (or some other server) may also push firmware upgrades and/or data updates to the earphone 10 using the IP addresses of the earphone 10 via the networks 30, 42. In addition, a user could download the firmware upgrades and/or data updates from the host server 40 to the client computing device 202 (see
Whether the downloads are transmitted wirelessly to the earphone 10 or via the client computing device 202 may depend on the current data rate of the earphone 10 and the quantity of data to be transmitted to the earphone 10. For example, according to various embodiments, as shown in the process flow of
As mentioned above, the processor unit 114 of the speakerphones 14 may be programmed, via firmware stored in the memory 120, 122, to have the ability to transition automatically from the ad hoc wireless network 24 to an infrastructure wireless network 30 (such as a WLAN) when the quality of the signal on the ad hoc wireless network 24 degrades below a suitable threshold (such as when the data source 20 is out of range for an ad hoc wireless network). In that case, the earphone 10 and the data source 20 may connect to a common infrastructure wireless network (e.g., WLAN) (see, for example,
When none of the preferred infrastructure networks is in range, the earphone 10 may connect automatically to the host server 40 via an available infrastructure wireless network 30 (see
The data source 20 and the earphone 10 may continue to communicate via the ad hoc wireless network mode 24 until they are out of range (e.g., the signal strengths degrade below a minimum threshold level). If an ad hoc wireless network 24 is not available at block 61, the transceiver circuit 100 and the data source 20 may execute a process, shown at block 63, to connect to the user's highest prioritized infrastructure wireless network 30. For example, of the infrastructure wireless networks whose signal strength exceeded the minimum threshold for both the earphone 10 and the data source 20 determined at step 62, the earphone 10 and the data source 20 may both transition to the infrastructure wireless network 30 having the highest priority, as previously set by the user (seen
If, however, no ad hoc wireless network and none of the user's prioritized infrastructure wireless networks are available, the earphone 10 may transition automatically to connect to the host server 40 at block 66 (see
In another embodiment, the earphone 10 may be programmed to transition automatically to the host server 40 when the earphone 10 and the data source 20 are not in communication via the ad hoc wireless network 24. That is, in such an embodiment, the earphone 10 may not try to connect via a local infrastructure wireless network 30 with the data source 20, but instead transition automatically to connect to the host server 40 (see
In various embodiments, as shown in
The user song ratings also may be used by the host server 40 to determine the user's musical preferences and offer new music that the user might enjoy. More details about generating user play lists based on song ratings may be found in published U.S. patent applications Pub. No. 2006/0212444, Pub. No. 2006/0206487, and Pub. No. 2006/0212442, and U.S. Pat. No. 7,003,515, which are incorporated herein by reference in their entirety.
In addition or alternatively, the user could log onto a web site hosted by the host server 40 (or some other server) to view the approval/disapproval ratings that the user made via the button 11 on the earphone 10. The web site may provide the user with the option of downloading the rated songs/audio files (for the host server 40 or some other server system) to their client computer device 50. The user could then have their earphone 10 connect to their client computer device 50 as a data source 20 via an ad hoc wireless network 24 (see
Another application of the headsets may be in vehicles equipped with Wi-Fi or other wireless network connectivity. Published PCT application WO 2007/136620, which is incorporated herein by reference, discloses a wireless router for providing a Wi-Fi or other local wireless network for a vehicle, such as a car, truck, boat, bus, etc. In a vehicle having a Wi-Fi or other local wireless network, the audio for other media systems in the vehicle could be broadcast over the vehicle's wireless network. For example, if the vehicle comprises a DVD player, the audio from the DVD system could be transmitted to the router and broadcast over the vehicle's network. Similarly, the audio from terrestrial radio stations, a CD player, or an audio cassette player could be broadcast over the vehicle's local wireless network. The vehicle's passengers, equipped with the earphones 10, could cycle through the various audio broadcasts (including the broadcasts from the vehicle's media system as well as broadcasts from the host server 40, for example) using a selection button 11 on the earphone 10. The vehicle may also be equipped with a console or terminal, etc., through which a passenger could mute all of the broadcasts for direct voice communications, for example.
As described above, the earphones 10 may also include a microphone 104, as shown in the example of
Another exemplary use of the earphones 10 is in a factory, warehouse, construction site, or other environment that might be noisy. Persons (e.g., workers) in the environment could use the earphones 10 for protection from the surrounding noise of the environment. From a console or terminal, a person (e.g., a supervisor) could select a particular recipient for a communication over the Wi-Fi network (or other local wireless network). The console or terminal may have buttons, dials, or switches, etc., for each user/recipient, or it could have one button or dial through which the sender could cycle through the possible recipients. In addition, the console or terminal could have a graphical user interface, through which the sender may select the desired recipient(s).
As mentioned above, the earphones 10 may comprise a USB port. In one embodiment, as shown in
The examples presented herein are intended to illustrate potential and specific implementations of the embodiments. It can be appreciated that the examples are intended primarily for purposes of illustration for those skilled in the art. No particular aspect of the examples is/are intended to limit the scope of the described embodiments.
According to various embodiments, therefore, the present invention is directed to an earphone 10 that comprises a body 12, where the body 12 comprises: (i) at least one acoustic transducer 106 for converting an electrical signal to sound; (ii) an antenna 108; and (iii) a transceiver circuit 100 in communication with the at least one acoustic transducer 106 and the antenna 108. The transceiver circuit 100 is for receiving and transmitting wireless signals via the antenna 108, and the transceiver circuit 100 is for outputting the electrical signal to the at least one acoustic transducer 106. The wireless transceiver circuit also comprises firmware, which when executed by the transceiver circuit, causes the transceiver circuit to: (i) receive digital audio wirelessly from a data source 20 via an ad hoc wireless network 24 when the data source 20 is in wireless communication range with the earphone 10 via the ad hoc wireless network 24; and (ii) when the data source 20 is not in wireless communication range with the earphone 10 via the ad hoc wireless network 24, transition automatically to receive digital audio via an infrastructure wireless network 30.
According to various implementations, the data source may comprise a portable digital audio player, such as an MP3 player, iPod, or laptop computer, or a nonportable digital audio player, such as a personal computer. In addition, the transceiver circuit 100 may comprise: (i) a wireless communication module 110 (such as a Wi-Fi or other wireless communication protocol module); (ii) a processor unit 114 in communication with the wireless communication module 110; (iii) a non-volatile memory unit 122 in communication with the processor unit 114; and (iv) a volatile memory 120 unit in communication with the processor unit 114. The infrastructure wireless network may comprise a WLAN. The transceiver circuit 100 may receive digital audio from the data source 20 via the infrastructure wireless network 30 when the data source 20 is not in wireless communication range with the earphone 10 via the ad hoc wireless network 24. The transceiver circuit firmware, when executed by the transceiver circuit 100, may cause the transceiver circuit 100 of the earphone 10 to transition automatically to a pre-set infrastructure wireless network 30 that the data source 20 transitions to when the data source 20 is not in wireless communication range with the earphone 10 via the ad hoc wireless network 24 and when the pre-set infrastructure wireless network 30 is in range of both the earphone 10 and the data source 20. In addition, the transceiver circuit firmware, when executed by the transceiver circuit 100, may cause the transceiver circuit 100 of the earphone 10 to transmit data via the ad hoc wireless network 24 to the data source 20 regarding one or more infrastructure wireless networks 30 detected by the transceiver circuit 100 when the earphone 10 and the data source 20 are communicating via the ad hoc wireless network 24.
In addition, the transceiver circuit firmware, when executed by the transceiver circuit 100, may cause the transceiver circuit 100 of the earphone 10 to connect to a host server 40 via an available infrastructure wireless network 30 when the data source 20 is not in wireless communication range with the earphone 10 via the ad hoc wireless network 24. The earphone 10 may receive streaming digital audio from the host server 40 via the infrastructure wireless network 30. In addition, the earphone 10 may receive a first network address for a first streaming digital audio content server 70 from the host server 40 via the infrastructure wireless network 30. In addition, the earphone 10 may comprise a user control, such as button 11, dial, pressure switch, or other type of user control, that, when activated, causes the earphone 10 to transmit an electronic request via the infrastructure wireless network 30 to the host server 40 for a second network address for a second streaming digital audio content server 70.
In other embodiments, the present invention is directed to a system that comprises: (i) a data source 20 for wirelessly transmitting streaming digital audio; and (ii) a wireless earphone 10 that is in wireless communication with the data source 20. In yet other embodiments, the present invention is directed to a communication system that comprises: (i) a host server 40; (ii) a first streaming digital audio content server 70 that is connected to the host server 40 via a data network 42; and (iii) a wireless earphone 10 that is in communication with the host server 40 via a wireless network 30. The host server 40 is programmed to transmit to the earphone 10 a first network address for the first streaming digital audio content server 70 on the data network 42. The host server 40 and the streaming digital audio content server(s) 70 each may comprise one or more processor circuits and one or more memory circuits (e.g., ROM circuits and/or RAM circuits).
In yet another embodiment, the present invention is directed to a headset that comprises: (i) a first earphone 10a that comprises one or more acoustic transducers 10b for converting a first electrical signal to sound; and (ii) a second earphone 10b, connected to the first earphone 10a, wherein the second earphone 10b comprises one or more acoustic transducers 10b for converting a second electrical signal to sound. In one embodiment, the first earphone 10a comprises: (i) a first antenna 108; and (ii) a first transceiver circuit 100 in communication with the one or more acoustic transducers 106 of the first earphone 10a and in communication with the first antenna 108. The first transceiver circuit 100 is for receiving and transmitting wireless signals via the first antenna 108, and for outputting the first electrical signal to the one or more acoustic transducers 10b of the first earphone 10a. The first transceiver circuit 100 also may comprise firmware, which when executed by the first transceiver circuit 100, causes the first transceiver circuit 100 to: (i) receive digital audio wirelessly from a data source 20 via an ad hoc wireless network 24 when the data source 20 is in wireless communication range with the first earphone 10a via the ad hoc wireless network 24; and (ii) when the data source 20 is not in wireless communication range with the first earphone 10a via the ad hoc wireless network 24, transition automatically to receive digital audio via an infrastructure wireless network 30.
In various implementations, the headset further may comprise a head band 19 that is connected to the first and second earphones 10. In addition, the headset 19 further may comprise a microphone 104 having an output connected to the first transceiver circuit 100. In one embodiment, the first transceiver circuit 100 is for outputting the second electrical signal to the one or more acoustic transducers 106 of the second earphone 10b. In another embodiment, the second earphone 10b comprises: (i) a second antenna 108; and (ii) a second transceiver circuit 100 in communication with the one or more acoustic transducers 106 of the second earphone 10b and in communication with the second antenna 108. The second transceiver circuit 100 is for receiving and transmitting wireless signals via the second antenna 108, and for outputting the second electrical signal to the one or more acoustic transducers 106 of the second earphone 10b. The second transceiver circuit 100 may comprise firmware, which when executed by the second transceiver circuit 100, causes the second transceiver circuit 100 to: (i) receive digital audio wirelessly from the data source 20 via the ad hoc wireless network 24 when the data source 20 is in wireless communication range with the second earphone 10b via the ad hoc wireless network 24; and (ii) when the data source 20 is not in wireless communication range with the second earphone 10b via the ad hoc wireless network 24, transition automatically to receive digital audio via the infrastructure wireless network 30.
In addition, according to various embodiments, the first earphone 10a may comprise a first data port and the second earphone 10b may comprise a second data port. In addition, the headset may further comprise an adapter or dongle 150 connected to the first data port of the first earphone 10a and to the second data port of the second earphone 10b, wherein the adapter 150 comprises an output plug connector 152 for connecting to a remote device.
In addition, according to other embodiments, the present invention is directed to a method that comprises the steps of: (i) receiving, by a wireless earphone, via an ad hoc wireless network, digital audio from a data source when the data source is in wireless communication with the earphone via the ad hoc wireless network; (ii) converting, by the wireless earphone, the digital audio to sound; and (iii) when the data source is not in wireless communication with the earphone, transitioning automatically, by the earphone, to receive digital audio via an infrastructure wireless network.
In various implementations, the step of transitioning automatically by the earphone to receive digital audio via an infrastructure wireless network may comprises transitioning automatically to receive digital audio from the data source via an infrastructure wireless network when the data source is not in wireless communication range with the earphone via the ad hoc wireless network. In addition, the method may further comprise the step of receiving by the wireless earphone from the data source via the ad hoc wireless network data regarding one or more infrastructure wireless networks detected by data source when the earphone and the data source are communicating via the ad hoc wireless network.
In addition, the step of transitioning automatically by the earphone to receive digital audio via an infrastructure wireless network comprises may transitioning automatically to receive digital audio from a host sever via the infrastructure wireless network when the data source is not in wireless communication range with the earphone via the ad hoc wireless network. Additionally, the step of transitioning automatically by the earphone to receive digital audio via an infrastructure wireless network may comprise: (i) receiving, by the wireless earphone via the infrastructure wireless network, from a host server connected to the infrastructure wireless network, a network address for a streaming digital audio content server; and (ii) connecting, by the wireless earphone, to the streaming digital audio content server using the network address received from the host server.
It is to be understood that the figures and descriptions of the embodiments have been simplified to illustrate elements that are relevant for a clear understanding of the embodiments, while eliminating, for purposes of clarity, other elements. For example, certain operating system details for the various computer-related devices and systems are not described herein. Those of ordinary skill in the art will recognize, however, that these and other elements may be desirable in a typical processor or computer system. Because such elements are well known in the art and because they do not facilitate a better understanding of the embodiments, a discussion of such elements is not provided herein.
In general, it will be apparent to one of ordinary skill in the art that at least some of the embodiments described herein may be implemented in many different embodiments of software, firmware and/or hardware. The software and firmware code may be executed by a processor or any other similar computing device. The software code or specialized control hardware that may be used to implement embodiments is not limiting. For example, embodiments described herein may be implemented in computer software using any suitable computer software language type. Such software may be stored on any type of suitable computer-readable medium or media, such as, for example, a magnetic or optical storage medium. The operation and behavior of the embodiments may be described without specific reference to specific software code or specialized hardware components. The absence of such specific references is feasible, because it is clearly understood that artisans of ordinary skill would be able to design software and control hardware to implement the embodiments based on the present description with no more than reasonable effort and without undue experimentation.
Moreover, the processes associated with the present embodiments may be executed by programmable equipment, such as computers or computer systems and/or processors. Software that may cause programmable equipment to execute processes may be stored in any storage device, such as, for example, a computer system (nonvolatile) memory, an optical disk, magnetic tape, or magnetic disk. Furthermore, at least some of the processes may be programmed when the computer system is manufactured or stored on various types of computer-readable media.
A “computer,” “computer system,” “host,” “host server,” “server,” or “processor” may be, for example and without limitation, a processor, microcomputer, minicomputer, server, mainframe, laptop, personal data assistant (PDA), wireless e-mail device, cellular phone, pager, processor, fax machine, scanner, or any other programmable device configured to transmit and/or receive data over a network. Such components may comprise: one or more processor circuits; and one more memory circuits, including ROM circuits and RAM circuits. Computer systems and computer-based devices disclosed herein may include memory for storing certain software applications used in obtaining, processing, and communicating information. It can be appreciated that such memory may be internal or external with respect to operation of the disclosed embodiments. The memory may also include any means for storing software, including a hard disk, an optical disk, floppy disk, ROM (read only memory), RAM (random access memory), PROM (programmable ROM), EEPROM (electrically erasable PROM) and/or other computer-readable media.
In various embodiments disclosed herein, a single component may be replaced by multiple components and multiple components may be replaced by a single component to perform a given function or functions. Except where such substitution would not be operative, such substitution is within the intended scope of the embodiments. Any servers described herein, such as the host server 40, for example, may be replaced by a “server farm” or other grouping of networked servers (such as server blades) that are located and configured for cooperative functions. It can be appreciated that a server farm may serve to distribute workload between/among individual components of the farm and may expedite computing processes by harnessing the collective and cooperative power of multiple servers. Such server farms may employ load-balancing software that accomplishes tasks such as, for example, tracking demand for processing power from different machines, prioritizing and scheduling tasks based on network demand and/or providing backup contingency in the event of component failure or reduction in operability.
While various embodiments have been described herein, it should be apparent that various modifications, alterations, and adaptations to those embodiments may occur to persons skilled in the art with attainment of at least some of the advantages. The disclosed embodiments are therefore intended to include all such modifications, alterations, and adaptations without departing from the scope of the embodiments as set forth herein.
The present application claims priority as a continuation to U.S. nonprovisional patent application Ser. No. 17/812,911, filed Jul. 15, 2022, which is a continuation of nonprovisional patent application Ser. No. 17/178,946, filed Feb. 18, 2021, now U.S. Pat. No. 11,425,485, issued Aug. 23, 2022, which is a continuation of U.S. nonprovisional patent application Ser. No. 17/070,363, filed Oct. 14, 2020, now U.S. Pat. No. 10,959,012, issued Mar. 23, 2021, which is a continuation of U.S. nonprovisional patent application Ser. No. 16/900,035, filed Jun. 12, 2020, now U.S. Pat. No. 10,848,852, issued Nov. 24, 2020, which is a continuation of U.S. nonprovisional patent application Ser. No. 16/375,879, filed Apr. 5, 2019, now U.S. Pat. No. 10,469,934, issued Nov. 5, 2019, which is a continuation of U.S. nonprovisional patent application Ser. No. 16/182,927, filed Nov. 7, 2018, now U.S. Pat. No. 10,368,155, issued Jun. 30, 2019, which is a continuation of U.S. nonprovisional patent application Ser. No. 15/962,305, filed Apr. 25, 2018, now U.S. Pat. No. 10,206,025, issued Feb. 12, 2019, which is a continuation of U.S. nonprovisional patent application Ser. No. 15/650,362, filed Jul. 14, 2017, now U.S. Pat. No. 9,986,325, issued May 29, 2018, which is a continuation of U.S. nonprovisional patent application Ser. No. 15/293,785, filed Oct. 14, 2016, now U.S. Pat. No. 9,729,959, issued Aug. 8, 2017, which is a continuation of U.S. nonprovisional patent application Ser. No. 15/082,040, filed Mar. 28, 2016, now U.S. Pat. No. 9,497,535, issued Nov. 15, 2016, which is a continuation of U.S. nonprovisional patent application Ser. No. 14/695,696, filed Apr. 24, 2015, now U.S. Pat. No. 9,438,987, issued on Sep. 6, 2016, which is a continuation of U.S. nonprovisional patent application Ser. No. 13/609,409, filed Sep. 11, 2012, now U.S. Pat. No. 9,049,502, issued Jun. 2, 2015, which is a continuation of U.S. nonprovisional patent application Ser. No. 13/459,291, filed Apr. 30, 2012, now U.S. Pat. No. 8,571,544, issued Oct. 29, 2013, which is a continuation of U.S. patent application Ser. No. 12/936,488, filed Dec. 20, 2010, now U.S. Pat. No. 8,190,203, issued May 29, 2012, which is a national stage entry of PCT/US2009/039754, filed Apr. 7, 2009, which claims priority to U.S. provisional patent application Ser. No. 61/123,265, filed Apr. 7, 2008, all of which are incorporated herein by reference in their entireties. U.S. nonprovisional patent application Ser. No. 17/649,928, filed Feb. 4, 2022, now U.S. Pat. No. 11,425,486, issued Aug. 23, 2022, is a continuation of U.S. nonprovisional patent application Ser. No. 17/178,946. U.S. nonprovisional patent application Ser. No. 14/031,938, filed Sep. 13, 2013, now U.S. Pat. No. 8,655,420, issued Feb. 18, 2014, is also a continuation of U.S. nonprovisional patent application Ser. No. 13/609,409, filed Sep. 11, 2012, now U.S. Pat. No. 9,049,502, mentioned above. The present application is also related to the following U.S. applications: Ser. No. 16/528,701, now U.S. Pat. No. 10,491,982, issued Nov. 26, 2019; Ser. No. 16/528,703, now U.S. Pat. No. 10,506,325, issued Dec. 10, 2019; Ser. No. 16/528,705, now U.S. Pat. No. 10,848,850, issued Nov. 24, 2020; Ser. No. 16/528,706, now U.S. Pat. No. 10,757,498, issued Aug. 25, 2020; Ser. No. 16/881,488, now U.S. Pat. No. 10,827,251, issued Nov. 3, 2020; Ser. No. 16/884,691, now U.S. Pat. No. 10,848,851, issued Nov. 24, 2020; and Ser. No. 17/070,295, now U.S. Pat. No. 10,959,011, issued Mar. 23, 2020.
Number | Name | Date | Kind |
---|---|---|---|
4456795 | Saito | Jun 1984 | A |
5721783 | Anderson | Feb 1998 | A |
5761298 | Davis et al. | Jun 1998 | A |
5815582 | Claybaugh et al. | Sep 1998 | A |
5889870 | Norris | Mar 1999 | A |
5960094 | Jensen et al. | Sep 1999 | A |
5998275 | Richiuso | Dec 1999 | A |
6097809 | Lucey et al. | Aug 2000 | A |
6278786 | McIntosh | Aug 2001 | B1 |
6295366 | Haller et al. | Sep 2001 | B1 |
6499129 | Srinivasan et al. | Dec 2002 | B1 |
6690808 | Urwyler | Feb 2004 | B2 |
6856690 | Skulley | Feb 2005 | B1 |
7039944 | Cho et al. | May 2006 | B1 |
7065342 | Rolf | Jun 2006 | B1 |
7069452 | Hind et al. | Jun 2006 | B1 |
7072686 | Schrager | Jul 2006 | B1 |
7289775 | King et al. | Oct 2007 | B1 |
7343177 | Seshadri et al. | Mar 2008 | B2 |
7457649 | Wilson | Nov 2008 | B1 |
7551940 | Paulson et al. | Jun 2009 | B2 |
7564989 | Schanz | Jul 2009 | B2 |
7627289 | Huddart | Dec 2009 | B2 |
7738434 | Reuss et al. | Jun 2010 | B1 |
7881745 | Rao et al. | Feb 2011 | B1 |
8180078 | Zellner | May 2012 | B2 |
8311255 | Hankey et al. | Nov 2012 | B2 |
8401219 | Hankey et al. | Mar 2013 | B2 |
9438987 | Koss et al. | Sep 2016 | B2 |
9866962 | Boesen | Jan 2018 | B2 |
10206025 | Koss et al. | Feb 2019 | B2 |
20020041697 | MacDonald et al. | Apr 2002 | A1 |
20020068610 | Anvekar et al. | Jun 2002 | A1 |
20020098878 | Mooney et al. | Jul 2002 | A1 |
20020160820 | Winkler | Oct 2002 | A1 |
20020197956 | Annola et al. | Dec 2002 | A1 |
20030018810 | Karagiannis et al. | Jan 2003 | A1 |
20030065805 | Barnes, Jr. | Apr 2003 | A1 |
20030073460 | van Pelt et al. | Apr 2003 | A1 |
20030083058 | Mayer | May 2003 | A1 |
20030100274 | Brown | May 2003 | A1 |
20030228019 | Eichler et al. | Dec 2003 | A1 |
20040002862 | Kim | Jan 2004 | A1 |
20040032964 | Liang | Feb 2004 | A1 |
20040068653 | Fascenda | Apr 2004 | A1 |
20040078812 | Calvert | Apr 2004 | A1 |
20040133734 | Jordan et al. | Jul 2004 | A1 |
20040142693 | Feder et al. | Jul 2004 | A1 |
20040165720 | Paulson et al. | Aug 2004 | A1 |
20040204168 | Laurila | Oct 2004 | A1 |
20040210752 | Rao | Oct 2004 | A1 |
20050037818 | Seshadri et al. | Feb 2005 | A1 |
20050058313 | Virgil et al. | Mar 2005 | A1 |
20050073522 | Aholainen et al. | Apr 2005 | A1 |
20050089181 | Polk, Jr. | Apr 2005 | A1 |
20050094822 | Swartz | May 2005 | A1 |
20050160270 | Goldberg et al. | Jul 2005 | A1 |
20050201585 | Jannard | Sep 2005 | A1 |
20050286466 | Fagg et al. | Dec 2005 | A1 |
20060025828 | Armstrong et al. | Feb 2006 | A1 |
20060026304 | Price | Feb 2006 | A1 |
20060052144 | Seil et al. | Mar 2006 | A1 |
20060073787 | Lair et al. | Apr 2006 | A1 |
20060083331 | Kaczynski | Apr 2006 | A1 |
20060141950 | Kim et al. | Jun 2006 | A1 |
20060147078 | Neu et al. | Jul 2006 | A1 |
20060147079 | Jaakkola | Jul 2006 | A1 |
20060160270 | Brun et al. | Jul 2006 | A1 |
20060163358 | Biderman | Jul 2006 | A1 |
20060166705 | Seshadri et al. | Jul 2006 | A1 |
20060166716 | Sesadri et al. | Jul 2006 | A1 |
20060206776 | Nieto | Sep 2006 | A1 |
20060217827 | Hsu et al. | Sep 2006 | A1 |
20060229014 | Harada et al. | Oct 2006 | A1 |
20070080934 | Chen et al. | Apr 2007 | A1 |
20070092098 | Kaderavek | Apr 2007 | A1 |
20070110017 | Fulknier et al. | May 2007 | A1 |
20070116316 | Goldberg | May 2007 | A1 |
20070123171 | Slamka et al. | May 2007 | A1 |
20070136446 | Rezvani et al. | Jun 2007 | A1 |
20070143105 | Braho et al. | Jun 2007 | A1 |
20070147629 | Chiloyan | Jun 2007 | A1 |
20070149261 | Huddart | Jun 2007 | A1 |
20070149629 | Donovan et al. | Jun 2007 | A1 |
20070162169 | Watanuki | Jun 2007 | A1 |
20070165875 | Rezvani et al. | Jul 2007 | A1 |
20070167187 | Rezvani et al. | Jul 2007 | A1 |
20070206776 | Petel et al. | Sep 2007 | A1 |
20070224933 | Mayer | Sep 2007 | A1 |
20070253579 | Liu et al. | Nov 2007 | A1 |
20070258613 | Wright | Nov 2007 | A1 |
20070258614 | Langberg | Nov 2007 | A1 |
20080016205 | Svendsen | Jan 2008 | A1 |
20080031475 | Goldstein | Feb 2008 | A1 |
20080043676 | Mousseau et al. | Feb 2008 | A1 |
20080052698 | Olson et al. | Feb 2008 | A1 |
20080056526 | Dunn et al. | Mar 2008 | A1 |
20080062939 | Horn et al. | Mar 2008 | A1 |
20080076489 | Rosener et al. | Mar 2008 | A1 |
20080112581 | Kim et al. | May 2008 | A1 |
20080113689 | Bailey | May 2008 | A1 |
20080133551 | Wensley et al. | Jun 2008 | A1 |
20080166001 | Hankey et al. | Jul 2008 | A1 |
20080166005 | Terlizzi | Jul 2008 | A1 |
20080194209 | Haupt et al. | Aug 2008 | A1 |
20080226094 | Rutschman | Sep 2008 | A1 |
20080279409 | Hupkes | Nov 2008 | A1 |
20080298613 | Slamka | Dec 2008 | A1 |
20080311966 | Klein | Dec 2008 | A1 |
20090046869 | Griffin, Jr. et al. | Feb 2009 | A1 |
20090048669 | Flagle et al. | Feb 2009 | A1 |
20090109894 | Ueda et al. | Apr 2009 | A1 |
20090158214 | Arnold | Jun 2009 | A1 |
20100151788 | Rahman et al. | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
008799 | Dec 2006 | AT |
2002017564 | Feb 2002 | WO |
2006098584 | Sep 2006 | WO |
2009126614 | Oct 2009 | WO |
Entry |
---|
Snapdragon Platform; Qualcomm Chipset Solutions, www.cdmatech.com/snapdragon, p. 1-2. |
Advanced Audio Distribution Profile Specification; Adopted version 1.0; release date: May 22, 2003, p. 1-75. |
Casali et al., Attenuation Performance of Four Hearing Protectors under Dynamic Movement and Different User Fitting Conditions, Human Factors (Feb. 1990), 32(1):9-25. |
Skrainar et al., Do Personal Radio Headsets Provide Hearing Protection?, The Noise and Vibration Control Magazine, Sound and Vibration (May 1985), 19(5):16-19. |
Bose, Internet Archive of http://www.bose.com/controller?event=VIEW_PRODUCT_PAGE_EVENT&product-headphones_audio_subcategory (Nov. 1, 2007). |
File history for U.S. Appl. No. 60/879,177, filed Jan. 6, 2007. |
Jabra BT8010 User Manual, www.jabra.com, 2007, GN Netcom A/S, accessed from www.Manualslib.com, 31 pages. |
Jabra BT 620s User Manual, www.jabra.com, 2005, GN Netcom A/S, 30 pages. |
CSR BlueCore™ 3-Multimedia External, Single Chip Bluetooth® v1.2 System Production Information Data Sheet for BC352239A Data Sheet, Nov. 2004, 116 pages. |
Pogue, David, Grooving and Chatting, All in One, The New York Times, accessed https://www.nytimes.com/2006/07/06/technology/grooving-and-chatting-all-in-one.html, Jul. 6, 2006, 5 pages. |
SST datasheet, 2001 Silicon Storage Technology, Inc., 30 pages. |
Plantronics 610 User Manual, 2006, Plantronics, Inc., 151 pages. |
Plantronics 645 User Manual, 2005, Plantronics, Inc., 32 pages. |
Plantronics 925 Data Sheet, 2008, Plantronics, Inc., 2 pages. |
IPR2021-00297—Judgment, Final Written Decision in Bose Corporation (Petitioner) vs. Koss Corporation (Patent Owner), issued by the United States Patent and Trademark Office Before the Patent Trial and Appeal Board, dated May 31, 2022. |
IPR2021-00305—Judgment, Final Written Decision in Bose Corporation (Petitioner) vs. Koss Corporation (Patent Owner), issued by the United States Patent and Trademark Office Before the Patent Trial and Appeal Board, entered May 31, 2022. |
Hanlon, Koss Cobalt Wireless Headphones, https://newatlas.com/koss-cobalt-wireless-headphones/5983/ (Aug. 11, 2006), pp. 9. |
Murph, Koss Introduces Cobalt Bluetooth Headphones, https://www.engadget.com/2006-08-12-koss-introduces-cobalt-bluetooth-headphones.html (Aug. 12, 2006), pp. 4. |
IPR2021-00381—Judgment, Final Written Decision in Apple, Inc. (Petitioner) vs. Koss Corporation (Patent Owner), issued by the United States Patent and Trademark Office Before the Patent Trial and Appeal Board, entered Jun. 27, 2022. |
Bose Corp. v. Koss Corp., Case No. IPR2021-00680, Final Written Decision, Paper 37 (PTAB Oct. 7, 2022). |
Bose Corp. v. Koss Corp., Case No. IPR2021-00612, Final Written Decision, Paper 38 (PTAB Sep. 13, 2022). |
Koss Corp. v. Plantronics Inc., Case No. 21-cv-03854-JST, Order Granting Motion to Dismiss, Dkt. No. 88 (N.D. Cal. Nov. 16, 2022). |
Number | Date | Country | |
---|---|---|---|
20220386017 A1 | Dec 2022 | US |
Number | Date | Country | |
---|---|---|---|
61123265 | Apr 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17812911 | Jul 2022 | US |
Child | 17818475 | US | |
Parent | 17178946 | Feb 2021 | US |
Child | 17812911 | US | |
Parent | 17070363 | Oct 2020 | US |
Child | 17178946 | US | |
Parent | 16900035 | Jun 2020 | US |
Child | 17070363 | US | |
Parent | 16375879 | Apr 2019 | US |
Child | 16900035 | US | |
Parent | 16182927 | Nov 2018 | US |
Child | 16375879 | US | |
Parent | 15962305 | Apr 2018 | US |
Child | 16182927 | US | |
Parent | 15650362 | Jul 2017 | US |
Child | 15962305 | US | |
Parent | 15293785 | Oct 2016 | US |
Child | 15650362 | US | |
Parent | 15082040 | Mar 2016 | US |
Child | 15293785 | US | |
Parent | 14695696 | Apr 2015 | US |
Child | 15082040 | US | |
Parent | 13609409 | Sep 2012 | US |
Child | 14695696 | US | |
Parent | 13459291 | Apr 2012 | US |
Child | 13609409 | US | |
Parent | 12936488 | US | |
Child | 13459291 | US |