US20140285313A1 - Proximity sensing device control architecture and data communication protocol - Google Patents
Proximity sensing device control architecture and data communication protocol Download PDFInfo
- Publication number
- US20140285313A1 US20140285313A1 US14/219,648 US201414219648A US2014285313A1 US 20140285313 A1 US20140285313 A1 US 20140285313A1 US 201414219648 A US201414219648 A US 201414219648A US 2014285313 A1 US2014285313 A1 US 2014285313A1
- Authority
- US
- United States
- Prior art keywords
- wireless
- threshold
- antenna
- signal strength
- received signal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
- G08C17/00—Arrangements for transmitting signals characterised by the use of a wireless electrical link
- G08C17/02—Arrangements for transmitting signals characterised by the use of a wireless electrical link using a radio link
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S11/00—Systems for determining distance or velocity not using reflection or reradiation
- G01S11/02—Systems for determining distance or velocity not using reflection or reradiation using radio waves
- G01S11/06—Systems for determining distance or velocity not using reflection or reradiation using radio waves using intensity measurements
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
- G01S5/18—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using ultrasonic, sonic, or infrasonic waves
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R1/00—Details of transducers, loudspeakers or microphones
- H04R1/02—Casings; Cabinets ; Supports therefor; Mountings therein
- H04R1/025—Arrangements for fixing loudspeaker transducers, e.g. in a box, furniture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R29/00—Monitoring arrangements; Testing arrangements
- H04R29/001—Monitoring arrangements; Testing arrangements for loudspeakers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R3/00—Circuits for transducers, loudspeakers or microphones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R1/00—Details of transducers, loudspeakers or microphones
- H04R1/02—Casings; Cabinets ; Supports therefor; Mountings therein
- H04R1/028—Casings; Cabinets ; Supports therefor; Mountings therein associated with devices performing functions other than acoustics, e.g. electric candles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R2227/00—Details of public address [PA] systems covered by H04R27/00 but not provided for in any of its subgroups
- H04R2227/003—Digital PA systems using, e.g. LAN or internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R2420/00—Details of connection covered by H04R, not provided for in its groups
- H04R2420/07—Applications of wireless loudspeakers or wireless microphones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R2499/00—Aspects covered by H04R or H04S not otherwise provided for in their subgroups
- H04R2499/10—General applications
- H04R2499/11—Transducers incorporated or for use in hand-held devices, e.g. mobile phones, PDA's, camera's
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
- H04R3/00—Circuits for transducers, loudspeakers or microphones
- H04R3/12—Circuits for transducers, loudspeakers or microphones for distributing signals to two or more loudspeakers
Definitions
- the present invention relates generally to electrical and electronic hardware, audio equipment, wired and wireless network communications, data processing, and computing devices. More specifically, techniques for mobile device speaker control are described.
- RSSI received signal strength
- Close proximity sensing can be utilized to improve intuitiveness on how two or more devices interact with one another rather than having a user interact with them.
- One example is for the user to place one of the devices close to another device, within boundaries of a set threshold RSSI for close proximity detection.
- close proximity sensing via RSSI may have a statistically high level of accuracy and a device may infer that two devices are close to one another, there still exists a small probability that a false alarm can be triggered (i.e., the device is detected as being in close proximity, but actually in reality the device is not in close proximity).
- use cases would require perfect or near perfect inference of close proximity of the devices.
- FIG. 1 illustrates an exemplary proximity sensing device control architecture and data communication protocol
- FIG. 2A illustrates another exemplary proximity sensing device control architecture and data communication protocol
- FIG. 2B illustrates yet another exemplary proximity sensing device control architecture and data communication protocol
- FIG. 2C illustrates a further exemplary proximity sensing device control architecture and data communication protocol
- FIG. 3A illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol
- FIG. 3B illustrates another alternative exemplary proximity sensing device control architecture and data communication protocol
- FIG. 3C illustrates yet another alternative exemplary proximity sensing device control architecture and data communication protocol
- FIG. 4A illustrates an exemplary mobile device architecture for proximity sensing device control architecture and data communication protocol
- FIG. 4B illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol
- FIG. 5A illustrates an exemplary process for proximity sensing device control and data communication
- FIG. 5B illustrates an alternative exemplary process for proximity sensing device control architecture and data communication
- FIG. 6 illustrates exemplary actions determined using an exemplary proximity sensing device control architecture and data communication protocol
- FIG. 7 illustrates an exemplary computer system suitable for use with proximity sensing device control architecture and data communication protocol
- FIG. 8A depicts an example of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system
- FIG. 8B depicts one example of an electrical termination of a node of an antenna
- FIG. 9A depicts another example of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system
- FIG. 9B depicts another example of an electrical termination of a node of an antenna
- FIG. 10 depicts an example of an antenna that may be detuned to be non-resonant at a frequency of interest
- FIG. 11 depicts another example of an antenna that may be detuned to be non-resonant at a frequency of interest
- FIG. 12A depicts an example of a chassis for wireless device and also depicts examples of different exterior and interior positions for one or more antennas that may be detuned to be non-resonant at a frequency of interest;
- FIG. 12B depicts a partial cut-away view of an example of a chassis for wireless device and also depicts examples of different positions for one or more antennas that may be detuned to be non-resonant at a frequency of interest;
- FIG. 13 depicts examples of connectors that may be used to electrically couple an antenna that may be detuned to be non-resonant at a frequency of interest with circuitry of a RF system;
- FIG. 14 depicts examples of different types of enclosures for a wireless device that may include one or more antennas that may be detuned to be non-resonant at a frequency of interest and wireless client devices having different near-field and far-field orientations relative to those antennas;
- FIG. 15 depicts examples of different types of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest;
- FIG. 16 depicts other examples of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest.
- FIG. 1 illustrates an exemplary proximity sensing device control architecture and data communication protocol.
- system 100 includes speaker box 102 , mobile device 104 , received signal strength indicator (RSSI) threshold 106 , Wi-Fi access point 108 , Cloud Service 110 , and mobile device 112 .
- speaker box 102 may refer to any type of speaker, speaker system, speaker network, single or group of speakers configured to render audible various types of media including music, song, audio, video, multi-media, or other types of media, without limitation to format, protocol, or other technical characteristics.
- Speaker box 102 may be configured for wired or wireless data communication in order to play files that may be digitally encoded without limitation to data formats, types, or data communication protocols (e.g., Bluetooth (BT), Bluetooth Low Energy (BTLE), Wi-Fi (also used interchangeably herein with “WiFi” or “wifi” without limitation), ZigBee, Near Field Communications (NFC), or others, without limitation). Speaker box 102 may also be configured to encode, decode, encrypt, or decrypt data for use with the techniques described herein. Speaker box 102 may, in some examples, be implemented using a device such as the JAMBOXTM from AliphCom of San Francisco, Calif.
- mobile devices 104 and 112 may be implemented as smart phones, mobile phones, cell phones, mobile computing devices (e.g., tablet computers, laptop computers, notebook computers, or any other portable or mobile computer, without limitation), personal digital assistants (PDA), portable media devices, electronic readers, and the like, without limitation.
- Mobile devices 104 and 112 and speaker box 102 may be configured to access Wi-Fi access point 108 in order to retrieve data from a Cloud Service 110 , which may also be in direct or indirect data communication with one or more data sources, databases, repositories, or other data storage facilities (not shown).
- RSSI threshold 106 may be used to determine which of mobile device 104 or 112 may control or interface with speaker box 102 .
- RSSI received signal strength indicator
- a pre-set received signal strength threshold e.g., threshold 106 . If the RSSI for mobile device 104 is greater than threshold 106 and the RSSI for mobile device 112 is less than threshold 106 , mobile device 104 may be prioritized over mobile device 112 for control of speaker box 102 .
- prioritization may be performed by ranking, prioritizing, or otherwise listing an address (e.g., media access control (MAC) address, internet protocol (IP), or other type of address that may be used to identify mobile device 104 , mobile device 112 , speaker box 102 , or Wi-Fi access point 108 (hereafter referred to as access point 108 ).
- an address e.g., media access control (MAC) address, internet protocol (IP), or other type of address that may be used to identify mobile device 104 , mobile device 112 , speaker box 102 , or Wi-Fi access point 108 (hereafter referred to as access point 108 ).
- MAC media access control
- IP internet protocol
- system 100 may be used to award or assign control of speaker box 102 to mobile device 104 , in some examples.
- access point 108 may be configured to handle any type of wired or wireless data communication protocol such as Wi-Fi, among others.
- the threshold comparison and determination of control and, as described below, other actions that may be taken may be initiated and performed when mobile device 104 is brought 107 in close proximity to speaker box 102 (e.g., mobile device 104 in contact with speaker box 102 , see 1650 on top of 1620 in FIG. 16 ).
- mobile device 104 may also be brought in close proximity to another device apart from speaker box 102 that may be used for configuring control of speaker box 102 .
- proximity may be determined using a variety of techniques to determine a distance or proximity of a source device (e.g., a device having media that may be played on speaker box 102 ).
- speaker box 102 or another device may be used to control speaker box 102 .
- a mobile device or other type of media device e.g., mobile device 104 , 112
- control may be established.
- actions may be initiated or performed to allow media to be played through speaker box 102 .
- system 100 and the above-described elements may be implemented differently in function, structure, configuration, or other aspects and are not limited to those shown and described.
- FIG. 2A illustrates another exemplary proximity sensing device control architecture and data communication protocol.
- system 200 includes speaker 202 (e.g., such as speaker box 102 of FIG. 1 ), control device 204 , data connections 206 , 214 , 216 , and 220 , threshold 208 , Cloud/Network 210 , database 212 , and mobile device 218 .
- speaker 202 e.g., such as speaker box 102 of FIG. 1
- control device 204 e.g., such as speaker box 102 of FIG. 1
- data connections 206 e.g., such as speaker box 102 of FIG. 1
- control device 204 e.g., data connections 206 , 214 , 216 , and 220
- threshold 208 e.g., Cloud/Network 210
- database 212 e.g., database 212
- mobile device 218 e.g., database 212
- mobile device 218 e.g., a mobile device 218
- FIG. 2B illustrates yet another exemplary proximity sensing device control architecture and data communication protocol.
- system 230 includes speaker 202 (e.g., such as speaker box 102 of FIG. 1 ), control device 204 , data connections 206 , 214 , 216 and 220 , RSSI threshold 208 (threshold 208 hereinafter), Cloud/Network 210 , database 212 , and mobile devices 218 and 232 , the latter of which may be in data communication with control device 204 using data connection 234 , which may be implemented as a wired, wireless, optical, or other type of data connection.
- speaker 202 e.g., such as speaker box 102 of FIG. 1
- control device 204 e.g., such as speaker box 102 of FIG. 1
- data connections 206 e.g., such as speaker box 102 of FIG. 1
- data connections 206 e.g., such as speaker box 102 of FIG. 1
- data connections 206 e.g., such as speaker
- techniques for mobile device speaker control may be implemented for mobile device 218 to control speaker 202 using control device 204 , all of which may be in data communication with each other using wired or wireless data communication protocols. If one or more other mobile devices (e.g., mobile device 232 ) are brought in close proximity, but not within threshold 208 , speaker control may still be assigned to mobile device 218 or another device with a RSSI that exceeds threshold 208 . In other examples, a determination as to which mobile device (e.g., 218 or 232 ) to assign control may be determined differently and is not limited to comparing RSSI values to threshold 208 . For example, control of speaker 202 (e.g., speaker box 102 of FIG. 1 ) may be awarded manually or assigned based on a more complex algorithm. Regardless and, in other examples, system 230 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described.
- FIG. 2C illustrates a further exemplary proximity sensing device control architecture and data communication protocol.
- system 240 includes speaker 202 (e.g., such as speaker box 102 of FIG. 1 ), control device 204 , data connections 206 , 214 , 216 , 234 and 244 , threshold 208 , Cloud/Network 210 , database 212 , mobile device 232 and mobile device 242 .
- techniques for mobile device speaker control may be implemented for mobile device 244 and/or mobile device 232 to control speaker 202 using control device 204 , all of which may be in data communication with each other using wired or wireless data communication protocols.
- speaker control may be configured to remain with the last device (e.g., either 232 or 242 ) to which it was assigned by control device 204 .
- system 240 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described.
- FIG. 3A illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol.
- system 300 includes speaker 302 , control device 304 included in speaker 302 , data connections 320 , 314 and 316 , RSSI threshold 308 (threshold 308 hereinafter), Cloud/Network 310 , database 312 , and mobile device 318 .
- Speaker 302 may be similar to the speaker box 102 of FIG. 1 ; however, unlike speaker box 102 , speaker 302 includes control device 304 .
- techniques for mobile device speaker control may be implemented for mobile device 318 to control speaker 302 using its internal control device 304 , all of which may be in data communication with each other using wired or wireless data communication protocols.
- system 300 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described.
- FIG. 3B illustrates another alternative exemplary proximity sensing device control architecture and data communication protocol.
- system 330 includes speaker 302 , control device 304 included in speaker 302 , data connections 314 , 316 and 320 , threshold 308 , Cloud/Network 310 , database 312 , and mobile devices 318 and 332 , the latter of which may be in data communication with control device 304 using data connection 334 , which may be implemented as a wired, wireless, optical, or other type of data connection.
- techniques for mobile device speaker control may be implemented for mobile device 318 to control speaker 302 using its internal control device 304 , all of which may be in data communication with each other using wired or wireless data communication protocols.
- speaker control may still be assigned to mobile device 318 or another device with a RSSI that exceeds threshold 308 .
- a determination as to which mobile device (e.g., 318 or 332 ) to assign control may be determined differently and is not limited to comparing RSSI values to threshold 308 .
- control of speaker 302 e.g., speaker box 102 of FIG. 1
- system 330 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described.
- FIG. 3C illustrates yet another alternative exemplary proximity sensing device control architecture and data communication protocol.
- system 340 includes speaker 302 , control device 304 included in speaker 302 , data connections 214 , 216 , 334 and 344 , threshold 308 , Cloud/Network 310 , database 312 , mobile device 332 and mobile device 342 .
- techniques for mobile device speaker control may be implemented for mobile device 344 and/or mobile device 332 to control speaker 302 using its internal control device 304 , all of which may be in data communication with each other using wired or wireless data communication protocols.
- speaker control may be configured to remain with the last device (e.g., either 332 or 342 ) to which it was assigned by control device 304 .
- system 340 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described.
- FIG. 4A illustrates an exemplary mobile device architecture for proximity sensing device control architecture and data communication protocol.
- mobile device architecture 400 may include a bus 402 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as memory 406 (e.g., non-volatile and/or volatile memory), speaker control application 408 (e.g., an Application), a power source 410 (e.g., an AC or DC power source), a processor (e.g., a CPU, controller, DSP, ⁇ P, ⁇ C, etc.), a communication facility 414 (e.g., for wired and/or wireless communication), and an Operating System (e.g., OS).
- OS 412 and/or speaker control application 408 may include executable instructions embodied in a non-transitory computer readable medium, such as memory 406 or other form of non-transitory data storage medium or system.
- FIG. 4B illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol.
- mobile device architecture 420 may include a bus 402 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as memory 406 (e.g., non-volatile and/or volatile memory), a power source 410 (e.g., an AC or DC power source), a processor (e.g., a CPU, controller, DSP, ⁇ P, ⁇ C, etc.), a communication facility 414 (e.g., for wired and/or wireless communication), and an Operating System (e.g., OS).
- memory 406 e.g., non-volatile and/or volatile memory
- power source 410 e.g., an AC or DC power source
- a processor e.g., a CPU, controller, DSP, ⁇ P, ⁇ C, etc.
- a communication facility 414 e.g., for wired and/or wireless communication
- an Operating System e
- OS 412 and/or speaker control application 408 may include executable instructions embodied in a non-transitory computer readable medium, such as memory 406 or other form of non-transitory data storage medium or system.
- Speaker control application 422 e.g., an Application
- FIG. 5A illustrates an exemplary process 500 for proximity sensing device control and data communication.
- Process 500 may include a stage 502 where monitoring of one or more devices over a wireless network may be performed by speaker box ( 102 , 202 , 302 ) or another device, using one or more of its respective radios (e.g., WiFi, Bluetooth, etc.).
- speaker box 102 , 202 , 302
- radios e.g., WiFi, Bluetooth, etc.
- the one or more devices may comprise one or more of the mobile devices described above ( 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342 ) or other mobile devices that emit RF signals that may be monitored by a RF system(s) and/or radio(s) of speaker box ( 102 , 202 , 302 ) or another device in communication with the speaker box, for example.
- the wireless network may comprise one or more wireless networks such as a WiFi network, a Bluetooth network, other networks, or a combination of the foregoing.
- Process 500 may include a stage 504 where data packets from the one or more wireless devices that were monitored (e.g., at the stage 502 ) are received.
- the data packets may be from a single wireless device or from a plurality of wireless devices.
- Data packets may be received by a RF system(s) and/or radio(s) of speaker box ( 102 , 202 , 302 ) or another device in communication with the speaker box.
- the data packets may be received by a RF receiver or a RF transceiver included in the RF system(s) and/or the radio(s) of speaker box ( 102 , 202 , 302 ) or another device in communication with the speaker box.
- Process 500 may include a stage 506 where received data packets (e.g., received at the stage 504 ) are filtered (or otherwise processed and/or analyzed) by evaluating a Received Signal Strength (e.g., RSSI) of the received packets.
- Process 500 may include a stage 508 where one or more of the devices are prioritized using an address based on the Received Signal Strength (e.g., RSSI) of the one or more devices (e.g., from the filtering and evaluating at the stage 506 ).
- prioritizing may comprise mobile device(s) having the highest Received Signal Strength (e.g., RSSI) being assigned a higher priority than mobile device(s) having lower Received Signal Strength (e.g., RSSI).
- Process 500 may include a stage 510 where Received Signal Strength (e.g., RSSI) is compared to a threshold value (e.g., threshold 106 , 208 , 308 ) to determine an action to be performed (e.g., streaming content, media, playback of music, video, etc., by speaker 108 , 208 , 308 ), if any.
- a determination as to assignment of control e.g., determining at the stage 510 an action to be performed, if any
- control may be awarded manually or assigned based on a more complex algorithm that may or may not include using Received Signal Strength (e.g., RSSI) values or comparing the Received Signal Strength values to some other metric such as the threshold (e.g., 106 , 208 , 308 ).
- Received Signal Strength e.g., RSSI
- the threshold e.g., 106 , 208 , 308 .
- FIG. 5B illustrates an alternative exemplary process 520 for proximity sensing device control architecture and data communication.
- Process 520 may include a stage 522 where one or more devices (e.g., mobile devices 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342 ) may be detected in proximity of a speaker box (e.g., 102 , 202 , 302 ).
- devices e.g., mobile devices 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342 .
- Detection of the one or more devices may comprise using the RF system(s) and/or radio(s) of the speaker box (e.g., a RF receiver or RF transceiver in 102 , 202 , 302 ) to detect Received Signal Strength (e.g., RSSI), address (e.g., MAC address and/or Bluetooth address) from a RF signal being broadcast or otherwise transmitted by the one or more devices.
- Proximity may comprise near field proximity (e.g., as in proximity for NFC) of the one or more devices (e.g., at a distance, such as a few inches, within the enclosed region for threshold 106 , 208 , 308 ).
- Process 520 may include a stage 524 where data packets received from the one or more devices may be filtered to determine Received Signal Strength (e.g., RSSI) of the RF signal (e.g., as received by the speaker box 102 , 202 , 302 ) and the Received Signal Strength may be compared to a threshold value (e.g., threshold 106 , 208 , 308 ).
- Process 520 may include a stage 528 where a determination of an action to be performed based on the comparison of the Received Signal Strength (e.g., RSSI) to the threshold value (e.g., threshold 106 , 208 , 308 ) may occur.
- the determination of the action to be performed may be determined differently and is not limited to comparing Received Signal Strength (e.g., RSSI) values to a threshold value (e.g., 106 , 208 , 308 ).
- control may be awarded manually or assigned based on a more complex algorithm that may or may not include using Received Signal Strength (e.g., RSSI) values or comparing those valued to some other metric such as the threshold (e.g., 106 , 208 , 308 ).
- another device in communication with the speaker box may perform one or more of the stages of process 520 .
- FIG. 6 illustrates exemplary actions 600 that may be determined using an exemplary proximity sensing device control architecture and data communication protocol.
- the Received Signal Strength e.g., RSSI
- the threshold e.g., 106 , 208 , 308
- branches 603 , 605 , 607 , and 609 lead to different stages at which specific actions may be taken.
- the speaker box may switch to an infrastructure mode (e.g., to WiFi) and connect to an access point (e.g., a WiFi or other type of wireless access point) and retrieve a file from a Cloud Service (e.g., 110 , 210 , 310 ).
- the file may comprise data for a song, music, audio, video, and other forms of data, for example.
- a mobile device e.g., 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342
- an access point e.g., a WiFi or other type of wireless access point.
- the media being streamed may comprise without limitation music, audio, video, or other media file types.
- the speaker box may establish a data communications link with a mobile device (e.g., 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342 ) to stream media from the mobile device and/or from a location (e.g., an address) provided by the mobile device over the data communications link.
- a mobile device e.g., 104 , 112 , 218 , 232 , 242 , 318 , 332 , 342
- the data communications link may comprise the data connections described above in reference to FIGS. 1-3C .
- a file stored in the speaker box may be accessed (e.g., by a mobile device).
- the file may comprise a song, music, audio, video or other file types, for example.
- the file may be stored in memory 206 of the speaker box.
- the stages 604 , 606 , 608 and 610 are non-limiting examples of actions that may be determined (e.g., at stages 510 or 528 of FIGS. 5A and 5B ), and actual actions that may be determined may be application dependent, dependent on file types or content type, the type(s) of mobile devices, the types of wireless networks, the types of Cloud Services, just to name a few for example.
- another device in communication with the speaker box may take the actions based on the determinations described above.
- FIG. 7 illustrates an exemplary computer system suitable for use with proximity sensing device control architecture and data communication protocol.
- computer system 700 may be used to implement computer programs, applications, methods, processes, or other software to perform the above-described techniques.
- Computer system 700 includes a bus 702 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as processor 704 , system memory 706 (e.g., RAM), storage device 708 (e.g., ROM), disk drive 710 (e.g., magnetic or optical), communication interface 712 (e.g., modem or Ethernet card), display 714 (e.g., CRT or LCD), input device 716 (e.g., keyboard), and cursor control 718 (e.g., mouse or trackball).
- processor 704 e.g., system memory 706 (e.g., RAM), storage device 708 (e.g., ROM), disk drive 710 (e.g., magnetic or optical), communication interface 712 (e.g., modem or Ethernet
- computer system 700 performs specific operations by processor 704 executing one or more sequences of one or more instructions stored in system memory 706 . Such instructions may be read into system memory 706 from another computer readable medium, such as static storage device 708 or disk drive 710 . In some examples, hard-wired circuitry may be used in place of or in combination with software instructions for implementation.
- Non-volatile media includes, for example, optical or magnetic disks, such as disk drive 710 .
- Volatile media includes dynamic memory, such as system memory 706 .
- non-transitory computer readable media includes, for example, floppy disk, flexible disk, hard disk, 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-EPROM, any other memory chip or cartridge, or any other non-transitory medium from which a computer can read.
- 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 702 for transmitting a computer data signal.
- execution of the sequences of instructions may be performed by a single computer system 700 .
- two or more computer systems 700 coupled by communication link 720 may perform the sequence of instructions in coordination with one another.
- Computer system 700 may transmit and receive messages, data, and instructions, including program, i.e., application code, through communication link 720 and communication interface 712 .
- Received program code may be executed by processor 704 as it is received, and/or stored in disk drive 710 , or other non-volatile storage for later execution.
- the description that follows includes additional exemplary information illustrating various techniques and embodiments associated with an exemplary proximity sensing device control architecture and data communication protocol.
- threshold may comprise a region surrounding a wireless device (e.g., speaker 102 , 202 , 302 and/or control device 204 , 304 ) and one or more other wireless devices (e.g., mobile device(s) 104 , 218 , 318 ) where Received Signal Strength (e.g., RSSI) when compared to the threshold may provide a reliable indication that the transmitting and receiving devices are within sufficiently close near field proximity of one another (e.g., about 30 cm or less) for establishing a wireless link (e.g., Bluetooth (BT), WiFi, or other) and wirelessly communicating data over the wireless link.
- BT Bluetooth
- Each frequency that data may be wirelessly communicated over will typically have a predetermined frequency range and associated wavelength, such as the 2.4 GHz frequency, for example.
- a RF receiver or transceiver in a radio or RF system of a device e.g., 102 , 202 , 302 and/or control device 204 , 304
- a device e.g., 102 , 202 , 302 and/or control device 204 , 304
- the frequency of interest e.g., WiFi or BT at 2.4 GHz or other
- the transmitting device(s) e.g., smartphone, tablet, pad, mobile devices 104 , 218 , 318 , etc.
- a far field space e.g., a space outside of the dashed lines for thresholds 106 , 208 , 308
- the RSSI signal received by the receiver may be weaker for a de-tuned antenna than an antenna that is tuned and optimized for that particular frequency band.
- an antenna formed from a long wire having a specific layout structure as will be described in greater detail below in regards to examples of such an antenna in FIGS. 8A-12 and 15 - 16 , may be used to ensure maximum signal pickup of the near field RF signals of devices in different orientations (see FIGS.
- FIGS. 8A-11 depict non-limiting examples of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system of a device(s) such as those described in reference to FIGS. 1-3C above (e.g., device(s) 102 , 202 , 302 and/or control device 204 , 304 , or other device).
- example 800 of a radio system 810 e.g., a radio receiver in a RF system of a device 102 , 202 , 302 and/or control device 204 , 304 , or other device
- a radio system 810 operating at an ultra-high frequency band including but not limited to BT, WiFi or other an operative to receive radio signal strength (e.g., RSSI) from a transmitting device (e.g., smartphone, tablet, pad, mobile devices 104 , 218 , 318 , etc.)
- a transmitting device e.g., smartphone, tablet, pad, mobile devices 104 , 218 , 318 , etc.
- a first end 803 of the antenna 801 may be electrically coupled with an input 802 of radio system 810 (e.g., electrically coupled with one or more RF receivers or RF transceivers) and a second end 805 of the antenna 801 may be un-coupled (e.g., electrically un-coupled as an open circuit) as depicted in FIG. 8A , or may be coupled with a potential, such as a ground (e.g., short-circuited) as depicted in example 850 of FIG. 8B where the second end 805 is coupled to a ground 819 .
- a potential such as a ground (e.g., short-circuited)
- Wire for antenna 801 may include a plurality of sections 807 having different orientations relative to one another including but not limited to a zig-zagged pattern depicted in example 800 of FIG. 8A .
- Each section 807 may oriented relative to an adjacent sections by a bend (e.g., at approximately 90 degrees, approximately 45 degrees, or some other angle).
- example 900 depicts a radio system 910 operating at an ultra-high frequency band and having its input 902 coupled with a first end 903 of an antenna 901 made from a wire or other electrically conductive structure and having a predefined length.
- a second end 905 of the antenna 901 may be un-coupled (e.g., an open circuit) as depicted in FIG. 9A , or may be coupled to a potential, such as a ground (e.g., short-circuited) as depicted in example 950 of FIG. 9B where the second end 905 is coupled to a ground 919 .
- Antenna 901 may include a plurality of sections 907 and 909 having different orientations relative to one another including but not limited to a zig-zagged pattern depicted in example 900 of FIG. 9 A., with sections 907 extending along a direction away from first end 903 and sections 909 folding back and extending in a direction towards the second end 905 .
- Each section ( 907 , 909 ) may oriented relative to an adjacent sections by a bend (e.g., at approximately 90 degrees, at approximately 45 degrees, or some other angle).
- dashed circle 971 denotes that sections 907 and 909 at their respective points of crossing over each other are not electrically connected at the cross over point, as depicted in greater detail in FIG.
- the sections 909 e.g., running left-to-right
- 907 e.g., into the drawing sheet
- An air gap between the sections ( 909 , 907 ), an electrically insulating material on a portion of one or both sections ( 909 , 907 ) or the like may be used to prevent electrical contact between the sections ( 909 , 907 ).
- sections 907 may be electrically conductive traces or wires on a first level and sections 909 as they fold back may be electrically conductive traces or wires on a second level that is above or below the first level.
- sections 907 may be conductive traces on a first layer of a PCB or flexible PCB and sections 909 may be conductive traces on a second layer of the PCB or flexible PCB that is spaced apart from and electrically isolated from the first layer.
- the zig-zagged patterns of antennas ( 801 , 901 ) may provide better coverage of a magnetic field in a RF signal (e.g., electromagnetic (EM) wave) being transmitted by one or more transmitting devices.
- a RF signal e.g., electromagnetic (EM) wave
- a quarter-wavelength of the frequency of interest e.g., BT, WiFi, 2.4 GHZ, etc.
- approximately one-half (1 ⁇ 2) a wavelength of the frequency of interest approximately one or more multiples of one-half (1 ⁇ 2) a wavelength of the frequency of interest
- Setting the electrical length may be used to ensure that a magnetic field strength of a magnetic field ( 1001 , 1003 , 1103 , 1105 ) in the transmitted RF signal is at a maximum magnetic field strength at a center ( 811 , 813 , 911 , 913 ) of each section ( 907 , 909 ).
- Lengths (L, L 1 , L 2 ) of sections ( 807 , 907 , 909 ) may be varied along a length of the zig-zag of their respective antennas ( 801 , 901 ) to shift where the magnetic field strength lies along the wire for those antennas ( 801 , 901 ).
- a device e.g., 102 , 202 , 302 and/or control device 204 , 304 , or other device
- a ground plane (not shown) (e.g., an electrically conductive surface that is either electrically coupled with an electrical ground and/or has a large surface area relative to the wavelength of the antenna 801 , 901 ) that is in close proximity to the wires for antennas ( 801 , 901 ) which may affect performance of the magnetic fields ( 1001 , 1003 , 1103 , 1105 ).
- a standing wave ratio (SWR) of the RF signal being received by the antenna ( 801 , 901 ) may be a maximum at the centers ( 811 , 813 , 911 , 913 ) of each section ( 907 , 909 ) and a current flow generated by the RF signal may be a maximum at the centers ( 811 , 813 , 911 , 913 ).
- the SWR may be minimum with a minimum magnetic field and a minimum current flow at points 815 , 817 , 915 , 917 ) of each section ( 907 , 909 ).
- lengths L 1 and L 2 may have different lengths or may have identical lengths (e.g., electrical lengths) for sections 907 and 909 .
- L 1 may vary among the sections 909 and L 2 may vary among the sections 907 .
- length L e.g., electrical lengths
- the antenna ( 801 , 901 ) may have a length determined by a frequency band of the wireless devices that will be transmitting the RF signal (e.g., a BT or WiFi device or other).
- a dimension and/or shape of a chassis or enclosure the antenna ( 801 , 901 ) is mounted on, mounted in, enclosed by, carried by or otherwise coupled with may determine a length of the antenna ( 801 , 901 ). Angles between sections may also be application dependent and are not limited by the examples depicted herein.
- an angle ⁇ and an angle ⁇ between sections 807 of FIG. 10 may be the same or different angles and may not be approximately 90 degree angles (e.g., may be approximately 45 degrees or some other angle).
- angles ⁇ , ⁇ and ⁇ between sections 909 and 907 of FIG. 11 may be the same or different angles and the angle may not be approximately 90 degree angles (e.g., approximately a right angle).
- the zig-zagged shape for antennas ( 801 , 901 ) depicted as examples in FIGS. 8A-11 are non-limiting examples and other shapes may be used.
- sections ( 807 , 907 , 909 ) need not be joined at points or an apex as depicted in FIGS. 8A-11 and other configurations may be used such as depicted in antennas 1201 and 1231 of FIGS. 12A and 12B , for example.
- Advantages of using the example antennas ( 801 , 901 ) described above in reference to FIGS. 8A-11 include but are not limited to: freedom in positioning the long wire for the antenna ( 801 , 901 ) for near field sensing (e.g., within threshold 106 , 208 , 308 ) to cover an area for sensing on a product (e.g., a wireless device, a client device, device(s) 102 , 202 , 302 and/or control device 204 , 304 , or other device); placement of the antenna ( 801 , 901 ) to cover areas where the object is obstructive compared to conventional antennas that may have to be strategically placed in order to be effective at receiving near field transmissions from other devices; flexibility in using arbitrary sized metal structures for sensing using the antenna ( 801 , 901 ); NFC for proximity sensing is not necessary in the device using the antenna ( 801 , 901 ); the antenna ( 801 , 901 ) is not limited to the area
- the example antennas ( 801 , 901 ) described above in reference to FIGS. 8A-11 may be utilized in a variety of end use scenarios including but not limited to: utilizing the detuned antennas ( 801 , 901 ) for high frequency sensing (e.g., in the GHz region of the RF spectrum, such as 2.4 GHz or other high frequency bands) to degrade RSSI signals received from other wireless devices operating (e.g., transmitting RF signals in the targeted high frequency band) in the far field (e.g., outside of threshold 106 , 208 , 308 ); utilize the long wire configuration of the antenna ( 801 , 901 ) to compensate for weaker magnetic field strength along sections of the wire; and utilizing a metal structure (e.g., a metal wall casing) of the receiving sensing device (e.g., a wireless device, a client device, device(s) 102 , 202 , 302 and/or control device 204 , 304 , or other device) as the
- Near field sensing of RF transmitting devices is not limited to devices depicted herein and may be implemented in other products and devices such as smartphones, laptops, and other non-obvious objects with radio capabilities.
- a metal poll structure of the lamp may be configured to act as a sensor by incorporating the antenna ( 801 , 901 ) into the metal structure.
- Bringing a RF enabled device that is transmitting RF signals (e.g., a smartphone) close to the lamp may cause the lamp to sense the RF enabled device and automatically switch from ON to OFF or from OFF to ON, or to control dimming of the lamp, for example.
- Secure access to a structure such as a building or other may a metal structure (e.g., a metal door frame or other) that acts as the non-resonating antenna ( 801 , 901 ) at the frequency band of interest, where a smartphone (or other radio device) is sensed in the near field of the structure to allow access to the structure.
- a surface such as a tabletop, may include the antenna ( 801 , 901 ) to sense the presence (e.g., in the near field) of other wireless devices.
- the foregoing are non-exhaustive examples of uses for the antenna ( 801 , 901 ).
- FIG. 12A an example 1200 a of a chassis for wireless device 1250 is depicted and examples of different exterior and interior positions for one or more antennas 1201 , 1211 and 1221 that may be detuned to be non-resonant at a frequency of interest are also depicted.
- device 1250 may include a portion 1270 that may be electrically conductive (e.g., a metal chassis and/or grill for a speaker—not shown) and a portion 1270 a that may be electrically non-conductive (e.g., a plastic or other material).
- a chassis of device 1250 may include one or more antennas one or more antennas 1201 , 1211 and 1221 that may be detuned to be non-resonant at a frequency of interest, such as frequencies (e.g., BT, WiFi, etc.) used by wireless devices (e.g., smartphones, laptops, pads, tablets, gaming devices, wireless routers, etc.).
- Antenna 1201 may be located on a top surface 1291 of device 1250 and may be positioned beneath the top surface 1291 as denoted by the dashed line for antenna 1201 .
- a first end 1203 of the antenna 1201 may be electrically coupled with a RF system (not shown) of device 1250 in a manner similar to first ends ( 803 , 903 ) of antennas ( 801 , 901 ) described above in FIGS. 8A and 9A .
- Second end 1205 may be un-coupled (e.g., open circuit) or coupled to a potential (e.g., a ground) in a manner similar to second ends ( 805 , 905 ) of antennas ( 801 , 901 ) described above in FIGS. 8B and 9B .
- Antenna 1250 may be routed around structure included in device 1250 such as device controls 1271 .
- a shape of antenna 1201 may be arcuate along its length (e.g., sinusoidal or wave shaped); however, antenna 1201 may have other shapes and is not limited to the shape depicted.
- Device 1250 may include antenna 1211 located on a front surface 1293 of the device 1250 and positioned beneath the front surface 1293 as denoted by the dashed line for antenna 1211 .
- First and second ends ( 1213 , 1215 ) may be coupled as described above for antenna 1201 .
- a shape of antenna 1211 may be zig-zagged along its length as depicted or may have some other shape.
- Device 1250 may include antenna 1221 located on a side surface 1297 of the device 1250 and positioned on the side surface 1297 (e.g., an electrically non-conductive material) as denoted by the solid line for antenna 1221 .
- First and second ends ( 1223 , 1225 ) may be coupled as described above for antenna 1201 .
- a shape of antenna 1221 may be zig-zagged and folded back along its length as depicted or may have some other shape.
- Device 1250 may include one or more antennas that may be detuned to be non-resonant at a frequency of interest, such as one or more of antennas 1201 , 1211 , or 1221 , for example.
- a plurality of antennas may be used to provide multiple locations upon which to physically place or to position in near field proximity other RF transmitting wireless devices (e.g., mobile devices, smartphones, etc.) to be sensed as described above.
- Device 1250 may include antennas in one or more other positions than those depicted, such as on a rear surface 1295 , or a bottom surface 1299 , for example.
- antennas 1201 , 1211 may not be positioned below surfaces 1291 and 1293 .
- a plurality of antenna ( 1201 , 1211 , 1221 ) may be electrically coupled with the same or different RF systems and/or radios the device 1250 .
- FIG. 12B where a partial cut-away view of an example of a chassis for wireless device 1250 b is depicted and examples of different positions for one or more antennas 1231 , 1241 , and 1251 that may be detuned to be non-resonant at a frequency of interest are also depicted.
- Device 1250 b may be a speaker box (e.g., 102 , 202 , 302 ) having one or more speakers 1231 and/or 1233 for playback of content and/or media, such as music, etc., for example.
- a top surface 1291 of device 1250 b may include an antenna 1231 and/or an antenna 1241 which may have lengths that span across the top surface such that an entire length of those antennas are not shown.
- Antennas 1231 and 1241 may have different lengths and/or dimensions.
- Antennas 1231 and 1241 may have different shapes as depicted or may have the same shape.
- Antenna 1231 may be routed around control elements 1281 a (e.g., volume up/down, playback controls).
- Device 1250 b may include an antenna 1251 positioned on a side surface 1297 adjacent to control and interface structures 1281 b .
- Antenna 1251 may have a zig-zagged and folded back shape or some other shape.
- First and second ends of the antennas depicted in FIG. 12B may be coupled or otherwise terminated as described above, with the first ends electrically coupled with RF systems and/or radios and the second ends either open-circuited or coupled to a potential, such as ground, for example.
- the antennas depicted in FIG. 12B may be positioned differently; such as not beneath structure 1270 of device 1250 b .
- structure 1270 is electrically non-conductive
- one or more of the antennas ( 1231 , 1241 , 1251 ) may be positioned on or formed in materials for structure 1270 .
- Device 1250 b may include one or more of the one or more antennas 1231 , 1241 , and 1251 and those antennas may be electrically coupled to the same or different RF system.
- the antennas depicted may be detuned to be non-resonant at the same or different frequencies of interest.
- examples 1300 a and 1300 b of connectors that may be used to electrically couple an antenna 1301 that may be detuned to be non-resonant at a frequency of interest with circuitry of a RF system (e.g., a WiFi and/or BT radio) is depicted.
- a first end 1303 of antenna 1301 may be coupled with a connector, such as a male SMA connector or other type of connector.
- a RF system 1310 may be disposed on a substrate such as a PCB or semiconductor die and may be coupled 1301 c with a connector 1321 , such as a female SMA connector or other type of connector (e.g., BNC).
- a male pin 1322 m on the connector 1320 may be configured to mate with a female receptacle 1323 f (not shown) on connector 1321 when the two connectors are joined (e.g., via threads on the connectors).
- the first end 1303 may be crimped or soldered to a node on the connector 1320 that is electrically coupled with male pin 1322 m .
- the connectors ( 1320 , 1321 ) are depicted after being connected 1350 (e.g., by screwing 1320 onto threads of 1321 ) to each other such that antenna 1301 is electrically coupled with RF system 1310 .
- Wire for antenna 1301 may be unshielded, or may include shielding along a portion of the wire, such as a portion 1305 adjacent to connector 1320 .
- the shielding may be coaxial and may have a 50 ohm impedance or other impedance (e.g., 75 ohms, etc.), for example.
- device 1250 b using one of its antennas may be operative to sense RSSI from a first device (not shown, but see devices 1540 and 1650 in examples 1500 c and 1600 a in FIGS. 15 and 16 ) placed on top of the device 1250 b (e.g., on surface 1291 ).
- the RSSI from the first device may be high with the first device placed in any orientation so long as the first device is close by in the near field region (e.g., threshold 106 , 208 , 308 ) of device 1250 b .
- the RSSI being within a threshold value or being compared to a threshold value may be used by the device 1250 b to take some action (e.g., handling of content or some other action to be performed as described in reference to FIGS. 5A-6 ). If the first device is replaced by a second device (not shown), the device 1250 b may detect the RSSI of the second device and handover operation (e.g., handling of content or taking some action to be performed as described in reference to FIGS. 5A-6 ).
- the wire for antenna 1231 may be several wavelengths long at the frequency of interest (e.g., 2.4 GHz or other).
- the antenna 1231 may have a resonant frequency that is lower than the frequency of interest (e.g., lower than 2.4 GHz). As one example, with a particular electrical length, antenna 1231 may resonate in the 100 MHz range. In some examples, antenna 1231 resonating in the 100 MHz range or some other frequency range may create harmonics at multiples of the resonating frequency. To ensure that those harmonics do not fall within the range of the frequency band that forbids WiFi transmission activities (e.g., GPS or other frequency bands), the antenna 1231 may be tuned to avoid harmonics that fall within those frequency ranges.
- wireless device 1420 may include one or more antennas that may be detuned to be non-resonant at a frequency of interest and wireless client devices 1450 having different near-field and far-field orientations relative to those antennas are depicted.
- wireless device 1420 may include an enclosure having a substantially rectangular shape with pillars or footings positioned at all four corners of the enclosure.
- One or more antennas 1410 a - 1401 e may be positioned at different locations on and/or in the enclosure for device 1420 .
- a surface 1470 of the enclosure may be electrically conductive and may be operative as an antenna or may be electrically non-conductive and the antenna may be formed in or on the electrically non-conductive material for 1470 .
- One or more wireless client devices 1450 may be positioned within threshold 1406 of device 1420 (e.g., within near field proximity) so that transmitted RF signals from those one or more devices 1450 may have RSSI or other RF signal data sensed by a RF system of device 1420 using the one or more antennas 1410 a - 1401 e .
- the one or more wireless client devices 1450 may be placed in direct contact with device 1420 (e.g., on surface 1470 ).
- Wireless client devices 1450 may have their RSSI or other RF signal data sensed with the wireless client devices 1450 disposed in different orientations relative to device 1420 as depicted in example 1400 a .
- antennas for wireless client devices 1450 may have different radiation patterns and/or signal strengths that vary with orientation of the wireless client device 1450
- the RSSI may be sensed regardless of the orientation of the wireless client devices 1450 .
- the one or more devices 1450 are positioned outside threshold 1406 at a far field distance 1409 , then RSSI received by device 1420 using its one or more antennas 1410 a - 1401 e may be insufficient (e.g., below a threshold value) to trigger an action being taken by device 1420 .
- orientation may be wireless client device having an orientation relative to some point of reference, such as X-Y-Z system 1499 where Tx, Ty, Tz, Rx, Ry, and Rz denote translations and rotations respectively about the X-Y-Z axes of X-Y-Z system 1499 .
- X-Y-Z system 1499 may be referenced to a point on device 1420 .
- any orientation of device 1450 in the far field 1409 should not trigger false sensing of device 1420 , that is, RSSI or other RF data being sensed from 1450 when positioned in the far field 1409 is not sufficient to trigger action from 1420 ; whereas, any orientation of device 1450 within the near field denoted by threshold 1406 should have RSSI that is sensed as being in the threshold 1406 and may trigger an appropriate action be device 1420 , such as described above in reference to FIGS. 5A-6 .
- Example 1400 b depicts another configuration for a chassis shape and placement of one or more antennas 1410 g - 1401 h on the chassis for device 1430 .
- wireless client devices 1450 while within threshold 1406 may have any orientation or be placed directly in contact with device 1430 for emitted RSSI to be sensed as being in the near field.
- orientation and/or position of the device(s) 1450 may be sensed by device 1420 as having RSSI that is not consistent with a near field location and no action may be taken by device 1430 relative to the far field devices that are sensed with below threshold value RSSI.
- FIGS. 15-16 depict examples 1500 a - 1600 b of different types of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest.
- the wireless client devices may have different orientations relative to the wireless devices they are in near field proximity of.
- wireless device 1520 includes antenna 1501 positioned at a front surface and a wireless client device 1550 is positioned within threshold 1506 and is resting against the front surface of device 1520 .
- wireless client device 1552 is within threshold 1506 of wireless device 1530 and is positioned adjacent to a front surface of the device 1530 that includes antenna 1501 .
- a plurality of client devices 1590 and 1560 are positioned within a threshold of wireless device 1540 that includes an antenna 1501 d on a side surface and an antenna 1501 e on a front surface.
- Wireless client devices ( 1590 , 1560 ) are positioned below and in contact with wireless device 1540 and have different orientations relative to wireless device 1540 .
- RSSI transmitted by wireless client devices ( 1590 , 1560 ) may be sensed by wireless device 1540 as being in the near field.
- Wireless client devices ( 1590 , 1560 ) may be configured similarly to device 1540 (e.g., 1590 and/or 1560 may be speaker boxes like wireless device 1540 ).
- Wireless client devices may include their own antennas ( 1501 a , 1501 b , 1501 c ) that may be detuned to be non-resonant at a frequency of interest (e.g., 2.4 GHz) and that frequency of interest may be the same or different than that for the antennas ( 1501 d , 1501 e ) for device 1540 , for example.
- a frequency of interest e.g., 2.4 GHz
- one or more of the devices 1540 , 1560 , 1590 may be a wireless device and one or more the devices may be wireless client devices.
- wireless device 1590 may regard device 1540 as a wireless client device and take some action with regard to content, data, media or other when device 1540 is placed on top of device 1590 .
- Moving device 1560 from the far field into threshold 1506 may result in device 1590 and/or device 1540 regarding the newly introduced device 1560 as wireless client device and devices 1590 and/or 1540 may take appropriate actions.
- the action taken may be to have content from device 1540 that was being played back on speakers of device 1590 to be played back in stereo using the speakers of devices 1590 and 1560 .
- example 1600 a depicts a wireless client device 1650 positioned within threshold 1606 and on top of and in direct contact with a wireless device 1620 that includes antenna 1601 .
- RSSI transmitted from client device 1650 will be sensed as being in the near field even if device 1650 is rotated 1611 by 180 degrees (e.g., flipped over such that the screen is face down on device 1620 ) or some other angle relative to wireless device 1620 .
- client device 1650 is positioned within threshold 1606 on a side of wireless device 1630 having antennas 1601 a and 1601 b , with antenna 1601 b being disposed on the side of device 1430 proximate the wireless client device 1650 .
- RSSI transmitted from client device 1650 will be sensed as being in the near field even if device 1650 is twisted 1621 by 180 degrees (e.g., spun around such that the screen is facing the side of the device 1630 ) or some other angle relative to wireless device 1630 .
- the number and placement of antennas on the wireless devices relative to the position and orientation of the wireless client devices may still allow for received RSSI to be sensed as being in the near field and appropriate action may be taken by the wireless devices relative to content, media, or other data carried by or accessible by the wireless client devices.
- Actual distances and/or ranges associated with near field, near field region, far field, far field region may be application specific and are not limited by the examples described and/or depicted herein.
Abstract
Description
- This application is a Continuation of pending U.S. patent application Ser. No. 14/205,215, Filed on Mar. 11, 2014, having Attorney Docket No. ALI-264, and Titled “Proximity Sensing Device Control Architecture And Data Communication Protocol”, and U.S. patent application Ser. No. 14/205,215 claims benefit and right of priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 61/802,344, Filed on Mar. 15, 2013, having Attorney Docket No. ALI-264P, and Titled “Proximity Sensing Device Control Architecture And Data Communication Protocol”, all of which are herein incorporated by reference in their entirety for all purposes.
- The present invention relates generally to electrical and electronic hardware, audio equipment, wired and wireless network communications, data processing, and computing devices. More specifically, techniques for mobile device speaker control are described.
- In conventional speaker systems, there are solutions for controlling individual speakers or using a control component for managing a group of speakers. However, these conventional solutions rely upon wired connections or, in the case of wireless connections, individual speakers are often controlled by a single device, which is often inflexible and confines media to that selected using the single control device. Further, conventional solutions are often time-consuming and technically complex to set up and manage, often requiring extensive training or expertise to operate.
- Conventional media playback solutions are typically found in mobile devices such as mobile phones, smart phones, or other devices. Unfortunately, conventional speaker control devices are often limited connections between a mobile device and a single speaker. Further, the range of actions that can be taken are often limited to the device that is in data communication with a given speaker. If different users with different playlists and mobile devices want to use a given speaker, individual connections often need to be established manually regardless of the type of data communication protocol used.
- Current radio standards (e.g., Bluetooth systems, WiFi systems) allow for a receiver to measure signal strength (e.g., of a RF signal) from a source transmitting data and one measure of signal strength includes received signal strength (RSSI). Although there have been studies that utilize RSSI information to understand how well RSSI values correlate to how far away a transmitter and a receiver are from one another, it is also known that it is difficult to utilize RSSI for distance measurements due to a number of factors. One of those factors may include a multipath effect where the RF signal being transmitted reflects off of surrounding objects, such as walls, stationary objects, and moving objects. Another factor may include antenna radiation pattern and polarization of antenna of the transmitter and the antenna of the receiver, both of which may contribute to RSSI error vs. distance. However, close distance measurements perform with higher accuracy than long distance measurement due to an inverse square power drop off (e.g., 1/R2 where R=Distance) in a far field region, and where for a near field region the inverse power drop can be greater than 1/R3 of the RF signal as a function of distance between the transmitter and the receiver. Close proximity sensing can be utilized to improve intuitiveness on how two or more devices interact with one another rather than having a user interact with them. One example is for the user to place one of the devices close to another device, within boundaries of a set threshold RSSI for close proximity detection. Although close proximity sensing via RSSI may have a statistically high level of accuracy and a device may infer that two devices are close to one another, there still exists a small probability that a false alarm can be triggered (i.e., the device is detected as being in close proximity, but actually in reality the device is not in close proximity). In conventional implementations, use cases would require perfect or near perfect inference of close proximity of the devices.
- Thus, a need exists for a for speaker control solution without the limitations of conventional techniques and a solution that does not trigger false alarms when a received RSSI value is within a pre-determined RSSI threshold value, but the devices are not within close proximity of one another.
- Various embodiments or examples (“examples”) are disclosed in the following detailed description and the accompanying drawings:
-
FIG. 1 illustrates an exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 2A illustrates another exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 2B illustrates yet another exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 2C illustrates a further exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 3A illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 3B illustrates another alternative exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 3C illustrates yet another alternative exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 4A illustrates an exemplary mobile device architecture for proximity sensing device control architecture and data communication protocol; -
FIG. 4B illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 5A illustrates an exemplary process for proximity sensing device control and data communication; -
FIG. 5B illustrates an alternative exemplary process for proximity sensing device control architecture and data communication; -
FIG. 6 illustrates exemplary actions determined using an exemplary proximity sensing device control architecture and data communication protocol; -
FIG. 7 illustrates an exemplary computer system suitable for use with proximity sensing device control architecture and data communication protocol; -
FIG. 8A depicts an example of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system; -
FIG. 8B depicts one example of an electrical termination of a node of an antenna; -
FIG. 9A depicts another example of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system; -
FIG. 9B depicts another example of an electrical termination of a node of an antenna; -
FIG. 10 depicts an example of an antenna that may be detuned to be non-resonant at a frequency of interest; -
FIG. 11 depicts another example of an antenna that may be detuned to be non-resonant at a frequency of interest; -
FIG. 12A depicts an example of a chassis for wireless device and also depicts examples of different exterior and interior positions for one or more antennas that may be detuned to be non-resonant at a frequency of interest; -
FIG. 12B depicts a partial cut-away view of an example of a chassis for wireless device and also depicts examples of different positions for one or more antennas that may be detuned to be non-resonant at a frequency of interest; -
FIG. 13 depicts examples of connectors that may be used to electrically couple an antenna that may be detuned to be non-resonant at a frequency of interest with circuitry of a RF system; -
FIG. 14 depicts examples of different types of enclosures for a wireless device that may include one or more antennas that may be detuned to be non-resonant at a frequency of interest and wireless client devices having different near-field and far-field orientations relative to those antennas; -
FIG. 15 depicts examples of different types of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest; and -
FIG. 16 depicts other examples of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest. - 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 computer readable medium such as a 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.
-
FIG. 1 illustrates an exemplary proximity sensing device control architecture and data communication protocol. Here,system 100 includesspeaker box 102,mobile device 104, received signal strength indicator (RSSI)threshold 106, Wi-Fi access point 108,Cloud Service 110, andmobile device 112. In some examples,speaker box 102 may refer to any type of speaker, speaker system, speaker network, single or group of speakers configured to render audible various types of media including music, song, audio, video, multi-media, or other types of media, without limitation to format, protocol, or other technical characteristics.Speaker box 102, in some examples, may be configured for wired or wireless data communication in order to play files that may be digitally encoded without limitation to data formats, types, or data communication protocols (e.g., Bluetooth (BT), Bluetooth Low Energy (BTLE), Wi-Fi (also used interchangeably herein with “WiFi” or “wifi” without limitation), ZigBee, Near Field Communications (NFC), or others, without limitation).Speaker box 102 may also be configured to encode, decode, encrypt, or decrypt data for use with the techniques described herein.Speaker box 102 may, in some examples, be implemented using a device such as the JAMBOX™ from AliphCom of San Francisco, Calif. - As used herein,
mobile devices Mobile devices speaker box 102 may be configured to access Wi-Fi access point 108 in order to retrieve data from aCloud Service 110, which may also be in direct or indirect data communication with one or more data sources, databases, repositories, or other data storage facilities (not shown). - In some examples, encrypted or unencrypted data packets may be transferred by
mobile device speaker box 102. However, RSSI threshold 106 (threshold 106 hereinafter) may be used to determine which ofmobile device speaker box 102. As an example, a received signal strength indicator (RSSI) may be detected for each ofmobile devices mobile device 104 is greater thanthreshold 106 and the RSSI formobile device 112 is less thanthreshold 106,mobile device 104 may be prioritized overmobile device 112 for control ofspeaker box 102. In some examples, prioritization may be performed by ranking, prioritizing, or otherwise listing an address (e.g., media access control (MAC) address, internet protocol (IP), or other type of address that may be used to identifymobile device 104,mobile device 112,speaker box 102, or Wi-Fi access point 108 (hereafter referred to as access point 108). - If
mobile device 104 is prioritized (e.g., listed by MAC address as having a RSSI that is greater thanthreshold 106 and greater than that ofmobile device 112 or any other mobile device (not shown)) higher than other mobile devices (e.g., mobile device 112), thensystem 100 may be used to award or assign control ofspeaker box 102 tomobile device 104, in some examples. As shown,access point 108 may be configured to handle any type of wired or wireless data communication protocol such as Wi-Fi, among others. As described above, the threshold comparison and determination of control and, as described below, other actions that may be taken may be initiated and performed whenmobile device 104 is brought 107 in close proximity to speaker box 102 (e.g.,mobile device 104 in contact withspeaker box 102, see 1650 on top of 1620 inFIG. 16 ). In other examples,mobile device 104 may also be brought in close proximity to another device apart fromspeaker box 102 that may be used for configuring control ofspeaker box 102. Using the techniques described above, proximity may be determined using a variety of techniques to determine a distance or proximity of a source device (e.g., a device having media that may be played on speaker box 102). In some examples, using pre-installed antennas and applications, as will be described below,speaker box 102 or another device (not shown) may be used to controlspeaker box 102. As an example, when a mobile device or other type of media device (e.g.,mobile device 104, 112) is brought 107 in close proximity to speaker box 102 (e.g., NFC within a few inches or Wi-Fi within 20 or 30 yards), control may be established. Further, after establishing control, actions may be initiated or performed to allow media to be played throughspeaker box 102. In still other examples,system 100 and the above-described elements may be implemented differently in function, structure, configuration, or other aspects and are not limited to those shown and described. -
FIG. 2A illustrates another exemplary proximity sensing device control architecture and data communication protocol. Here,system 200 includes speaker 202 (e.g., such asspeaker box 102 ofFIG. 1 ),control device 204,data connections threshold 208, Cloud/Network 210,database 212, andmobile device 218. In some examples, techniques for mobile device speaker control may be implemented formobile device 218 to controlspeaker 202 usingcontrol device 204, all of which may be in data communication with each other using wired or wireless data communication protocols. In other examples,system 200 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 2B illustrates yet another exemplary proximity sensing device control architecture and data communication protocol. Here,system 230 includes speaker 202 (e.g., such asspeaker box 102 ofFIG. 1 ),control device 204,data connections threshold 208 hereinafter), Cloud/Network 210,database 212, andmobile devices control device 204 usingdata connection 234, which may be implemented as a wired, wireless, optical, or other type of data connection. In some examples, techniques for mobile device speaker control may be implemented formobile device 218 to controlspeaker 202 usingcontrol device 204, all of which may be in data communication with each other using wired or wireless data communication protocols. If one or more other mobile devices (e.g., mobile device 232) are brought in close proximity, but not withinthreshold 208, speaker control may still be assigned tomobile device 218 or another device with a RSSI that exceedsthreshold 208. In other examples, a determination as to which mobile device (e.g., 218 or 232) to assign control may be determined differently and is not limited to comparing RSSI values tothreshold 208. For example, control of speaker 202 (e.g.,speaker box 102 ofFIG. 1 ) may be awarded manually or assigned based on a more complex algorithm. Regardless and, in other examples,system 230 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 2C illustrates a further exemplary proximity sensing device control architecture and data communication protocol. Here,system 240 includes speaker 202 (e.g., such asspeaker box 102 ofFIG. 1 ),control device 204,data connections threshold 208, Cloud/Network 210,database 212,mobile device 232 andmobile device 242. In some examples, techniques for mobile device speaker control may be implemented formobile device 244 and/ormobile device 232 to controlspeaker 202 usingcontrol device 204, all of which may be in data communication with each other using wired or wireless data communication protocols. As an example, if neither device (e.g., 232, 242) is withinthreshold 208, than speaker control may be configured to remain with the last device (e.g., either 232 or 242) to which it was assigned bycontrol device 204. In other examples,system 240 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 3A illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol. Here,system 300 includesspeaker 302,control device 304 included inspeaker 302,data connections threshold 308 hereinafter), Cloud/Network 310,database 312, andmobile device 318.Speaker 302 may be similar to thespeaker box 102 ofFIG. 1 ; however, unlikespeaker box 102,speaker 302 includescontrol device 304. In some examples, techniques for mobile device speaker control may be implemented formobile device 318 to controlspeaker 302 using itsinternal control device 304, all of which may be in data communication with each other using wired or wireless data communication protocols. In other examples,system 300 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 3B illustrates another alternative exemplary proximity sensing device control architecture and data communication protocol. Here,system 330 includesspeaker 302,control device 304 included inspeaker 302,data connections threshold 308, Cloud/Network 310,database 312, andmobile devices control device 304 usingdata connection 334, which may be implemented as a wired, wireless, optical, or other type of data connection. In some examples, techniques for mobile device speaker control may be implemented formobile device 318 to controlspeaker 302 using itsinternal control device 304, all of which may be in data communication with each other using wired or wireless data communication protocols. If one or more other mobile devices (e.g., mobile device 232) are brought in close proximity, but not withinthreshold 308, speaker control may still be assigned tomobile device 318 or another device with a RSSI that exceedsthreshold 308. In other examples, a determination as to which mobile device (e.g., 318 or 332) to assign control may be determined differently and is not limited to comparing RSSI values tothreshold 308. For example, control of speaker 302 (e.g.,speaker box 102 ofFIG. 1 ) may be awarded manually or assigned based on a more complex algorithm. Regardless and, in other examples,system 330 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 3C illustrates yet another alternative exemplary proximity sensing device control architecture and data communication protocol. Here,system 340 includesspeaker 302,control device 304 included inspeaker 302,data connections threshold 308, Cloud/Network 310,database 312,mobile device 332 andmobile device 342. In some examples, techniques for mobile device speaker control may be implemented formobile device 344 and/ormobile device 332 to controlspeaker 302 using itsinternal control device 304, all of which may be in data communication with each other using wired or wireless data communication protocols. As an example, if neither device (e.g., 332, 342) is withinthreshold 308, then speaker control may be configured to remain with the last device (e.g., either 332 or 342) to which it was assigned bycontrol device 304. In other examples,system 340 and the above-described elements may be implemented differently and are not limited to the functions, structures, or configurations shown and described. -
FIG. 4A illustrates an exemplary mobile device architecture for proximity sensing device control architecture and data communication protocol. Here,mobile device architecture 400 may include abus 402 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as memory 406 (e.g., non-volatile and/or volatile memory), speaker control application 408 (e.g., an Application), a power source 410 (e.g., an AC or DC power source), a processor (e.g., a CPU, controller, DSP, μP, μC, etc.), a communication facility 414 (e.g., for wired and/or wireless communication), and an Operating System (e.g., OS).OS 412 and/orspeaker control application 408 may include executable instructions embodied in a non-transitory computer readable medium, such asmemory 406 or other form of non-transitory data storage medium or system. -
FIG. 4B illustrates an alternative exemplary proximity sensing device control architecture and data communication protocol. Here,mobile device architecture 420 may include abus 402 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as memory 406 (e.g., non-volatile and/or volatile memory), a power source 410 (e.g., an AC or DC power source), a processor (e.g., a CPU, controller, DSP, μP, μC, etc.), a communication facility 414 (e.g., for wired and/or wireless communication), and an Operating System (e.g., OS).OS 412 and/orspeaker control application 408 may include executable instructions embodied in a non-transitory computer readable medium, such asmemory 406 or other form of non-transitory data storage medium or system. Speaker control application 422 (e.g., an Application) may be positioned externally tomobile device architecture 420 and may be in communication 424 (wired and/or wireless) with subsystems and devices ofmobile device architecture 420 viabus 402 and/orcommunication facility 414. -
FIG. 5A illustrates anexemplary process 500 for proximity sensing device control and data communication.Process 500 may include astage 502 where monitoring of one or more devices over a wireless network may be performed by speaker box (102, 202, 302) or another device, using one or more of its respective radios (e.g., WiFi, Bluetooth, etc.). The one or more devices may comprise one or more of the mobile devices described above (104, 112, 218, 232, 242, 318, 332, 342) or other mobile devices that emit RF signals that may be monitored by a RF system(s) and/or radio(s) of speaker box (102, 202, 302) or another device in communication with the speaker box, for example. The wireless network may comprise one or more wireless networks such as a WiFi network, a Bluetooth network, other networks, or a combination of the foregoing.Process 500 may include astage 504 where data packets from the one or more wireless devices that were monitored (e.g., at the stage 502) are received. The data packets may be from a single wireless device or from a plurality of wireless devices. Data packets may be received by a RF system(s) and/or radio(s) of speaker box (102, 202, 302) or another device in communication with the speaker box. For example, the data packets may be received by a RF receiver or a RF transceiver included in the RF system(s) and/or the radio(s) of speaker box (102, 202, 302) or another device in communication with the speaker box.Process 500 may include astage 506 where received data packets (e.g., received at the stage 504) are filtered (or otherwise processed and/or analyzed) by evaluating a Received Signal Strength (e.g., RSSI) of the received packets.Process 500 may include astage 508 where one or more of the devices are prioritized using an address based on the Received Signal Strength (e.g., RSSI) of the one or more devices (e.g., from the filtering and evaluating at the stage 506). For example, prioritizing may comprise mobile device(s) having the highest Received Signal Strength (e.g., RSSI) being assigned a higher priority than mobile device(s) having lower Received Signal Strength (e.g., RSSI).Process 500 may include astage 510 where Received Signal Strength (e.g., RSSI) is compared to a threshold value (e.g.,threshold speaker stage 510 an action to be performed, if any) may be determined differently and is not limited to comparing Received Signal Strength (e.g., RSSI) values to a threshold value (e.g., 106, 208, 308). In some examples, control may be awarded manually or assigned based on a more complex algorithm that may or may not include using Received Signal Strength (e.g., RSSI) values or comparing the Received Signal Strength values to some other metric such as the threshold (e.g., 106, 208, 308). -
FIG. 5B illustrates an alternativeexemplary process 520 for proximity sensing device control architecture and data communication.Process 520 may include astage 522 where one or more devices (e.g.,mobile devices threshold Process 520 may include astage 524 where data packets received from the one or more devices may be filtered to determine Received Signal Strength (e.g., RSSI) of the RF signal (e.g., as received by thespeaker box threshold Process 520 may include astage 528 where a determination of an action to be performed based on the comparison of the Received Signal Strength (e.g., RSSI) to the threshold value (e.g.,threshold speaker process 520. -
FIG. 6 illustratesexemplary actions 600 that may be determined using an exemplary proximity sensing device control architecture and data communication protocol. InFIG. 600 at astage 602 the Received Signal Strength (e.g., RSSI) value or values have been compared to the threshold (e.g., 106, 208, 308) andbranches branch 603 is taken from thestage 602 to astage 604, then the speaker box (102, 202, 302) may switch to an infrastructure mode (e.g., to WiFi) and connect to an access point (e.g., a WiFi or other type of wireless access point) and retrieve a file from a Cloud Service (e.g., 110, 210, 310). The file may comprise data for a song, music, audio, video, and other forms of data, for example. - If a
branch 605 is taken from thestage 602 to astage 606, then a mobile device (e.g., 104, 112, 218, 232, 242, 318, 332, 342) may stream media to the speaker box via an access point (e.g., a WiFi or other type of wireless access point). The media being streamed may comprise without limitation music, audio, video, or other media file types. - If a
branch 607 is taken from thestage 602 to astage 608, then the speaker box may establish a data communications link with a mobile device (e.g., 104, 112, 218, 232, 242, 318, 332, 342) to stream media from the mobile device and/or from a location (e.g., an address) provided by the mobile device over the data communications link. The data communications link may comprise the data connections described above in reference toFIGS. 1-3C . - If a
branch 609 is taken from thestage 602 to astage 610, then a file stored in the speaker box may be accessed (e.g., by a mobile device). The file may comprise a song, music, audio, video or other file types, for example. As one example, the file may be stored inmemory 206 of the speaker box. Thestages stages FIGS. 5A and 5B ), and actual actions that may be determined may be application dependent, dependent on file types or content type, the type(s) of mobile devices, the types of wireless networks, the types of Cloud Services, just to name a few for example. In some examples, another device in communication with the speaker box may take the actions based on the determinations described above. -
FIG. 7 illustrates an exemplary computer system suitable for use with proximity sensing device control architecture and data communication protocol. In some examples,computer system 700 may be used to implement computer programs, applications, methods, processes, or other software to perform the above-described techniques.Computer system 700 includes abus 702 or other communication mechanism for communicating information, which interconnects subsystems and devices, such asprocessor 704, system memory 706 (e.g., RAM), storage device 708 (e.g., ROM), disk drive 710 (e.g., magnetic or optical), communication interface 712 (e.g., modem or Ethernet card), display 714 (e.g., CRT or LCD), input device 716 (e.g., keyboard), and cursor control 718 (e.g., mouse or trackball). - According to some examples,
computer system 700 performs specific operations byprocessor 704 executing one or more sequences of one or more instructions stored insystem memory 706. Such instructions may be read intosystem memory 706 from another computer readable medium, such asstatic storage device 708 ordisk drive 710. In some examples, hard-wired circuitry may be used in place of or in combination with software instructions for implementation. - The term “computer readable medium” refers to any tangible non-transitory computer readable medium that participates in providing instructions to
processor 704 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, such asdisk drive 710. Volatile media includes dynamic memory, such assystem memory 706. - Common forms of non-transitory computer readable media includes, for example, floppy disk, flexible disk, hard disk, 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-EPROM, any other memory chip or cartridge, or any other non-transitory medium from which a computer can 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 702 for transmitting a computer data signal. - In some examples, execution of the sequences of instructions may be performed by a
single computer system 700. According to some examples, two ormore computer systems 700 coupled by communication link 720 (e.g., LAN, PSTN, or wireless network) may perform the sequence of instructions in coordination with one another.Computer system 700 may transmit and receive messages, data, and instructions, including program, i.e., application code, throughcommunication link 720 andcommunication interface 712. Received program code may be executed byprocessor 704 as it is received, and/or stored indisk drive 710, or other non-volatile storage for later execution. - The description that follows includes additional exemplary information illustrating various techniques and embodiments associated with an exemplary proximity sensing device control architecture and data communication protocol.
- As described above and depicted by way of example in
FIGS. 1-3B , threshold (106, 208, 308) may comprise a region surrounding a wireless device (e.g.,speaker control device 204, 304) and one or more other wireless devices (e.g., mobile device(s) 104, 218, 318) where Received Signal Strength (e.g., RSSI) when compared to the threshold may provide a reliable indication that the transmitting and receiving devices are within sufficiently close near field proximity of one another (e.g., about 30 cm or less) for establishing a wireless link (e.g., Bluetooth (BT), WiFi, or other) and wirelessly communicating data over the wireless link. Each frequency that data may be wirelessly communicated over will typically have a predetermined frequency range and associated wavelength, such as the 2.4 GHz frequency, for example. Utilization of an antenna(s) in a RF receiver or transceiver in a radio or RF system of a device (e.g., 102, 202, 302 and/orcontrol device 204, 304) that may be tuned or otherwise configured (e.g., detuned) to be non-resonant at the frequency of interest (e.g., WiFi or BT at 2.4 GHz or other) may be used ensure that radio performance is poor when the transmitting device(s) (e.g., smartphone, tablet, pad,mobile devices thresholds control device 204, 304). - For example, with a distance between transmitter and receiver that is in a far field region (e.g., greater than about 0.5 meters) for a particular frequency band, in some example, the RSSI signal received by the receiver may be weaker for a de-tuned antenna than an antenna that is tuned and optimized for that particular frequency band. In the near field region, an antenna formed from a long wire having a specific layout structure, as will be described in greater detail below in regards to examples of such an antenna in
FIGS. 8A-12 and 15-16, may be used to ensure maximum signal pickup of the near field RF signals of devices in different orientations (seeFIGS. 14-16 ) and/or locations relative to the sensing device (e.g., the receiving device such as 102, 202, 302 and/orcontrol device 204, 304) that includes the long wire with the specific layout.FIGS. 8A-11 depict non-limiting examples of an antenna that may be detuned to be non-resonant at a frequency of interest and coupled with a radio system of a device(s) such as those described in reference toFIGS. 1-3C above (e.g., device(s) 102, 202, 302 and/orcontrol device - Turning now to
FIGS. 8A-8B , where example 800 of a radio system 810 (e.g., a radio receiver in a RF system of adevice control device mobile devices antenna 801 made from a wire or other electrically conductive structure (e.g., electrically conductive trances on a PCB or flexible PCB) and having a predefined length. Afirst end 803 of theantenna 801 may be electrically coupled with aninput 802 of radio system 810 (e.g., electrically coupled with one or more RF receivers or RF transceivers) and asecond end 805 of theantenna 801 may be un-coupled (e.g., electrically un-coupled as an open circuit) as depicted inFIG. 8A , or may be coupled with a potential, such as a ground (e.g., short-circuited) as depicted in example 850 ofFIG. 8B where thesecond end 805 is coupled to aground 819. Wire forantenna 801 may include a plurality ofsections 807 having different orientations relative to one another including but not limited to a zig-zagged pattern depicted in example 800 ofFIG. 8A . Eachsection 807 may oriented relative to an adjacent sections by a bend (e.g., at approximately 90 degrees, approximately 45 degrees, or some other angle). - Referring now to
FIGS. 9A-9B , where example 900 depicts aradio system 910 operating at an ultra-high frequency band and having itsinput 902 coupled with afirst end 903 of anantenna 901 made from a wire or other electrically conductive structure and having a predefined length. Asecond end 905 of theantenna 901 may be un-coupled (e.g., an open circuit) as depicted inFIG. 9A , or may be coupled to a potential, such as a ground (e.g., short-circuited) as depicted in example 950 ofFIG. 9B where thesecond end 905 is coupled to aground 919.Antenna 901 may include a plurality ofsections sections 907 extending along a direction away fromfirst end 903 andsections 909 folding back and extending in a direction towards thesecond end 905. Each section (907, 909) may oriented relative to an adjacent sections by a bend (e.g., at approximately 90 degrees, at approximately 45 degrees, or some other angle). InFIG. 9A , dashedcircle 971 denotes thatsections FIG. 9B where inside the dashedcircle 971section 909 although part of thesame antenna 901 is not in contact withsection 907. InFIG. 9B , the sections 909 (e.g., running left-to-right) and 907 (e.g., into the drawing sheet) proximate thepoint 971 of crossing over each other may be spaced apart a distance D from each other so as not to make contact with each other. An air gap between the sections (909, 907), an electrically insulating material on a portion of one or both sections (909, 907) or the like may be used to prevent electrical contact between the sections (909, 907). As one example,sections 907 may be electrically conductive traces or wires on a first level andsections 909 as they fold back may be electrically conductive traces or wires on a second level that is above or below the first level. As another example,sections 907 may be conductive traces on a first layer of a PCB or flexible PCB andsections 909 may be conductive traces on a second layer of the PCB or flexible PCB that is spaced apart from and electrically isolated from the first layer. - Moving on to
FIGS. 10 and 11 , inFIGS. 8A and 9A the zig-zagged patterns of antennas (801, 901) may provide better coverage of a magnetic field in a RF signal (e.g., electromagnetic (EM) wave) being transmitted by one or more transmitting devices. InFIGS. 10 and 11 , each section (907, 909) may have a length (L, L1, L2) (e.g., its electrical length) including but not limited to an electrical length that may be: approximately one or more multiples of a quarter-wavelength of the frequency of interest (e.g., BT, WiFi, 2.4 GHZ, etc.); approximately one-half (½) a wavelength of the frequency of interest; approximately one or more multiples of one-half (½) a wavelength of the frequency of interest; an arbitrary fraction of a wavelength of the frequency of interest; and may be set to be greater than a wavelength of the frequency of interest (e.g., electrical length>1λ where λ=wavelength), for example. Setting the electrical length may be used to ensure that a magnetic field strength of a magnetic field (1001, 1003, 1103, 1105) in the transmitted RF signal is at a maximum magnetic field strength at a center (811, 813, 911, 913) of each section (907, 909). Lengths (L, L1, L2) of sections (807, 907, 909) may be varied along a length of the zig-zag of their respective antennas (801, 901) to shift where the magnetic field strength lies along the wire for those antennas (801, 901). In the examples, 800, 900, 1000, and 1100 ofFIGS. 8A-11 , a device (e.g., 102, 202, 302 and/orcontrol device antenna 801, 901) that is in close proximity to the wires for antennas (801, 901) which may affect performance of the magnetic fields (1001, 1003, 1103, 1105). A standing wave ratio (SWR) of the RF signal being received by the antenna (801, 901) may be a maximum at the centers (811, 813, 911, 913) of each section (907, 909) and a current flow generated by the RF signal may be a maximum at the centers (811, 813, 911, 913). In contrast, the SWR may be minimum with a minimum magnetic field and a minimum current flow atpoints FIG. 11 , lengths L1 and L2 may have different lengths or may have identical lengths (e.g., electrical lengths) forsections antenna 901, L1 may vary among thesections 909 and L2 may vary among thesections 907. InFIG. 10 , length L (e.g., electrical lengths) may be the same or different among thesections 807 ofantenna 801. - Actual shape, pattern and length (e.g., zig-zagged or other) of the antenna (801, 901) will be application dependent and are not limited to the exampled depicted herein. For example, the antenna (801, 901) may have a length determined by a frequency band of the wireless devices that will be transmitting the RF signal (e.g., a BT or WiFi device or other). A dimension and/or shape of a chassis or enclosure the antenna (801, 901) is mounted on, mounted in, enclosed by, carried by or otherwise coupled with may determine a length of the antenna (801, 901). Angles between sections may also be application dependent and are not limited by the examples depicted herein. As one example, an angle α and an angle Ω between
sections 807 ofFIG. 10 may be the same or different angles and may not be approximately 90 degree angles (e.g., may be approximately 45 degrees or some other angle). Similarly, angles α, Ω and β betweensections FIG. 11 may be the same or different angles and the angle may not be approximately 90 degree angles (e.g., approximately a right angle). The zig-zagged shape for antennas (801, 901) depicted as examples inFIGS. 8A-11 , are non-limiting examples and other shapes may be used. Furthermore, sections (807, 907, 909) need not be joined at points or an apex as depicted inFIGS. 8A-11 and other configurations may be used such as depicted inantennas FIGS. 12A and 12B , for example. - Advantages of using the example antennas (801, 901) described above in reference to
FIGS. 8A-11 include but are not limited to: freedom in positioning the long wire for the antenna (801, 901) for near field sensing (e.g., withinthreshold control device - The example antennas (801, 901) described above in reference to
FIGS. 8A-11 may be utilized in a variety of end use scenarios including but not limited to: utilizing the detuned antennas (801, 901) for high frequency sensing (e.g., in the GHz region of the RF spectrum, such as 2.4 GHz or other high frequency bands) to degrade RSSI signals received from other wireless devices operating (e.g., transmitting RF signals in the targeted high frequency band) in the far field (e.g., outside ofthreshold control device - Near field sensing of RF transmitting devices is not limited to devices depicted herein and may be implemented in other products and devices such as smartphones, laptops, and other non-obvious objects with radio capabilities. As one example, in a home WiFi environment where lamps may be enabled with radio devices, a metal poll structure of the lamp may be configured to act as a sensor by incorporating the antenna (801, 901) into the metal structure. Bringing a RF enabled device that is transmitting RF signals (e.g., a smartphone) close to the lamp may cause the lamp to sense the RF enabled device and automatically switch from ON to OFF or from OFF to ON, or to control dimming of the lamp, for example. Secure access to a structure such as a building or other may a metal structure (e.g., a metal door frame or other) that acts as the non-resonating antenna (801, 901) at the frequency band of interest, where a smartphone (or other radio device) is sensed in the near field of the structure to allow access to the structure. A surface, such as a tabletop, may include the antenna (801, 901) to sense the presence (e.g., in the near field) of other wireless devices. The foregoing are non-exhaustive examples of uses for the antenna (801, 901).
- Description is now directed to
FIG. 12A where an example 1200 a of a chassis forwireless device 1250 is depicted and examples of different exterior and interior positions for one ormore antennas device 1250 may include aportion 1270 that may be electrically conductive (e.g., a metal chassis and/or grill for a speaker—not shown) and aportion 1270 a that may be electrically non-conductive (e.g., a plastic or other material). A chassis ofdevice 1250 may include one or more antennas one ormore antennas Antenna 1201 may be located on atop surface 1291 ofdevice 1250 and may be positioned beneath thetop surface 1291 as denoted by the dashed line forantenna 1201. Afirst end 1203 of theantenna 1201 may be electrically coupled with a RF system (not shown) ofdevice 1250 in a manner similar to first ends (803, 903) of antennas (801, 901) described above inFIGS. 8A and 9A .Second end 1205 may be un-coupled (e.g., open circuit) or coupled to a potential (e.g., a ground) in a manner similar to second ends (805, 905) of antennas (801, 901) described above inFIGS. 8B and 9B .Antenna 1250 may be routed around structure included indevice 1250 such as device controls 1271. A shape ofantenna 1201 may be arcuate along its length (e.g., sinusoidal or wave shaped); however,antenna 1201 may have other shapes and is not limited to the shape depicted.Device 1250 may includeantenna 1211 located on afront surface 1293 of thedevice 1250 and positioned beneath thefront surface 1293 as denoted by the dashed line forantenna 1211. First and second ends (1213, 1215) may be coupled as described above forantenna 1201. A shape ofantenna 1211 may be zig-zagged along its length as depicted or may have some other shape.Device 1250 may includeantenna 1221 located on aside surface 1297 of thedevice 1250 and positioned on the side surface 1297 (e.g., an electrically non-conductive material) as denoted by the solid line forantenna 1221. First and second ends (1223, 1225) may be coupled as described above forantenna 1201. A shape ofantenna 1221 may be zig-zagged and folded back along its length as depicted or may have some other shape.Device 1250 may include one or more antennas that may be detuned to be non-resonant at a frequency of interest, such as one or more ofantennas Device 1250 may include antennas in one or more other positions than those depicted, such as on arear surface 1295, or abottom surface 1299, for example. In other examples,antennas surfaces device 1250. - Turning now to
FIG. 12B where a partial cut-away view of an example of a chassis forwireless device 1250 b is depicted and examples of different positions for one ormore antennas Device 1250 b may be a speaker box (e.g., 102, 202, 302) having one ormore speakers 1231 and/or 1233 for playback of content and/or media, such as music, etc., for example. Here atop surface 1291 ofdevice 1250 b may include anantenna 1231 and/or anantenna 1241 which may have lengths that span across the top surface such that an entire length of those antennas are not shown.Antennas Antennas Antenna 1231 may be routed aroundcontrol elements 1281 a (e.g., volume up/down, playback controls).Device 1250 b may include anantenna 1251 positioned on aside surface 1297 adjacent to control andinterface structures 1281 b.Antenna 1251 may have a zig-zagged and folded back shape or some other shape. First and second ends of the antennas depicted inFIG. 12B may be coupled or otherwise terminated as described above, with the first ends electrically coupled with RF systems and/or radios and the second ends either open-circuited or coupled to a potential, such as ground, for example. In some examples, the antennas depicted inFIG. 12B may be positioned differently; such as not beneathstructure 1270 ofdevice 1250 b. For example, ifstructure 1270 is electrically non-conductive, then one or more of the antennas (1231, 1241, 1251) may be positioned on or formed in materials forstructure 1270.Device 1250 b may include one or more of the one ormore antennas FIGS. 12A and 12B , the antennas depicted may be detuned to be non-resonant at the same or different frequencies of interest. - Referring now to
FIG. 13 where examples 1300 a and 1300 b of connectors that may be used to electrically couple anantenna 1301 that may be detuned to be non-resonant at a frequency of interest with circuitry of a RF system (e.g., a WiFi and/or BT radio) is depicted. Afirst end 1303 ofantenna 1301 may be coupled with a connector, such as a male SMA connector or other type of connector. ARF system 1310 may be disposed on a substrate such as a PCB or semiconductor die and may be coupled 1301 c with aconnector 1321, such as a female SMA connector or other type of connector (e.g., BNC). Here, amale pin 1322 m on theconnector 1320 may be configured to mate with afemale receptacle 1323 f (not shown) onconnector 1321 when the two connectors are joined (e.g., via threads on the connectors). Thefirst end 1303 may be crimped or soldered to a node on theconnector 1320 that is electrically coupled withmale pin 1322 m. In example 1300 b, the connectors (1320, 1321) are depicted after being connected 1350 (e.g., by screwing 1320 onto threads of 1321) to each other such thatantenna 1301 is electrically coupled withRF system 1310. Other types of connectors, male, female, or otherwise may be used and the foregoing are non-limiting examples. In other examples, soldering or crimping may be used to couplefirst end 1303 with an input to a RF system. Wire forantenna 1301 may be unshielded, or may include shielding along a portion of the wire, such as aportion 1305 adjacent toconnector 1320. The shielding may be coaxial and may have a 50 ohm impedance or other impedance (e.g., 75 ohms, etc.), for example. - Returning to
FIG. 12B ,device 1250 b using one of its antennas, such asantenna 1231 for example, may be operative to sense RSSI from a first device (not shown, but seedevices FIGS. 15 and 16 ) placed on top of thedevice 1250 b (e.g., on surface 1291). The RSSI from the first device may be high with the first device placed in any orientation so long as the first device is close by in the near field region (e.g.,threshold device 1250 b. The RSSI being within a threshold value or being compared to a threshold value may be used by thedevice 1250 b to take some action (e.g., handling of content or some other action to be performed as described in reference toFIGS. 5A-6 ). If the first device is replaced by a second device (not shown), thedevice 1250 b may detect the RSSI of the second device and handover operation (e.g., handling of content or taking some action to be performed as described in reference toFIGS. 5A-6 ). InFIG. 12B , the wire forantenna 1231 may be several wavelengths long at the frequency of interest (e.g., 2.4 GHz or other). Theantenna 1231 may have a resonant frequency that is lower than the frequency of interest (e.g., lower than 2.4 GHz). As one example, with a particular electrical length,antenna 1231 may resonate in the 100 MHz range. In some examples,antenna 1231 resonating in the 100 MHz range or some other frequency range may create harmonics at multiples of the resonating frequency. To ensure that those harmonics do not fall within the range of the frequency band that forbids WiFi transmission activities (e.g., GPS or other frequency bands), theantenna 1231 may be tuned to avoid harmonics that fall within those frequency ranges. - Advancing now to
FIG. 14 where examples 1400 a and 1400 b of different types of enclosures for a wireless device (1420, 1430) that may include one or more antennas that may be detuned to be non-resonant at a frequency of interest andwireless client devices 1450 having different near-field and far-field orientations relative to those antennas are depicted. In example 1400 a,wireless device 1420 may include an enclosure having a substantially rectangular shape with pillars or footings positioned at all four corners of the enclosure. One or more antennas 1410 a-1401 e may be positioned at different locations on and/or in the enclosure fordevice 1420. Asurface 1470 of the enclosure may be electrically conductive and may be operative as an antenna or may be electrically non-conductive and the antenna may be formed in or on the electrically non-conductive material for 1470. One or morewireless client devices 1450 may be positioned withinthreshold 1406 of device 1420 (e.g., within near field proximity) so that transmitted RF signals from those one ormore devices 1450 may have RSSI or other RF signal data sensed by a RF system ofdevice 1420 using the one or more antennas 1410 a-1401 e. The one or morewireless client devices 1450 may be placed in direct contact with device 1420 (e.g., on surface 1470).Wireless client devices 1450 may have their RSSI or other RF signal data sensed with thewireless client devices 1450 disposed in different orientations relative todevice 1420 as depicted in example 1400 a. In that antennas forwireless client devices 1450 may have different radiation patterns and/or signal strengths that vary with orientation of thewireless client device 1450, while withinthreshold 1406, the RSSI may be sensed regardless of the orientation of thewireless client devices 1450. On the other hand if the one ormore devices 1450 are positioned outsidethreshold 1406 at afar field distance 1409, then RSSI received bydevice 1420 using its one or more antennas 1410 a-1401 e may be insufficient (e.g., below a threshold value) to trigger an action being taken bydevice 1420. Here orientation may be wireless client device having an orientation relative to some point of reference, such asX-Y-Z system 1499 where Tx, Ty, Tz, Rx, Ry, and Rz denote translations and rotations respectively about the X-Y-Z axes ofX-Y-Z system 1499.X-Y-Z system 1499 may be referenced to a point ondevice 1420. Any orientation ofdevice 1450 in thefar field 1409 should not trigger false sensing ofdevice 1420, that is, RSSI or other RF data being sensed from 1450 when positioned in thefar field 1409 is not sufficient to trigger action from 1420; whereas, any orientation ofdevice 1450 within the near field denoted bythreshold 1406 should have RSSI that is sensed as being in thethreshold 1406 and may trigger an appropriate action bedevice 1420, such as described above in reference toFIGS. 5A-6 . - Example 1400 b depicts another configuration for a chassis shape and placement of one or more antennas 1410 g-1401 h on the chassis for
device 1430. Here, as in example 1400 a,wireless client devices 1450 while withinthreshold 1406 may have any orientation or be placed directly in contact withdevice 1430 for emitted RSSI to be sensed as being in the near field. When outside thethreshold 1406 at thefar field 1409, orientation and/or position of the device(s) 1450 may be sensed bydevice 1420 as having RSSI that is not consistent with a near field location and no action may be taken bydevice 1430 relative to the far field devices that are sensed with below threshold value RSSI. -
FIGS. 15-16 depict examples 1500 a-1600 b of different types of wireless client devices in near-field proximity of a wireless device including one or more antennas that may be detuned to be non-resonant at a frequency of interest. InFIGS. 15-16 the wireless client devices may have different orientations relative to the wireless devices they are in near field proximity of. In example 1500 a ofFIG. 15 ,wireless device 1520 includesantenna 1501 positioned at a front surface and awireless client device 1550 is positioned withinthreshold 1506 and is resting against the front surface ofdevice 1520. In example 1500 b,wireless client device 1552 is withinthreshold 1506 ofwireless device 1530 and is positioned adjacent to a front surface of thedevice 1530 that includesantenna 1501. In example 1500 c, a plurality ofclient devices wireless device 1540 that includes anantenna 1501 d on a side surface and anantenna 1501 e on a front surface. Wireless client devices (1590, 1560) are positioned below and in contact withwireless device 1540 and have different orientations relative towireless device 1540. RSSI transmitted by wireless client devices (1590, 1560) may be sensed bywireless device 1540 as being in the near field. Wireless client devices (1590, 1560) may be configured similarly to device 1540 (e.g., 1590 and/or 1560 may be speaker boxes like wireless device 1540). Wireless client devices (1590, 1560) may include their own antennas (1501 a, 1501 b, 1501 c) that may be detuned to be non-resonant at a frequency of interest (e.g., 2.4 GHz) and that frequency of interest may be the same or different than that for the antennas (1501 d, 1501 e) fordevice 1540, for example. In some example, one or more of thedevices device 1590 is a wireless device listening (e.g., using its RF system to receive RSSI from transmitting devices) for wireless client devices anddevice 1540 is moved from the far field intothreshold 1506 and near field proximity ofwireless device 1590, thenwireless device 1590 may regarddevice 1540 as a wireless client device and take some action with regard to content, data, media or other whendevice 1540 is placed on top ofdevice 1590. Movingdevice 1560 from the far field intothreshold 1506 may result indevice 1590 and/ordevice 1540 regarding the newly introduceddevice 1560 as wireless client device anddevices 1590 and/or 1540 may take appropriate actions. As one example, the action taken may be to have content fromdevice 1540 that was being played back on speakers ofdevice 1590 to be played back in stereo using the speakers ofdevices - In
FIG. 16 , example 1600 a depicts awireless client device 1650 positioned withinthreshold 1606 and on top of and in direct contact with awireless device 1620 that includesantenna 1601. RSSI transmitted fromclient device 1650 will be sensed as being in the near field even ifdevice 1650 is rotated 1611 by 180 degrees (e.g., flipped over such that the screen is face down on device 1620) or some other angle relative towireless device 1620. In example 1600 b,client device 1650 is positioned withinthreshold 1606 on a side ofwireless device 1630 havingantennas antenna 1601 b being disposed on the side ofdevice 1430 proximate thewireless client device 1650. Here, RSSI transmitted fromclient device 1650 will be sensed as being in the near field even ifdevice 1650 is twisted 1621 by 180 degrees (e.g., spun around such that the screen is facing the side of the device 1630) or some other angle relative towireless device 1630. - In the examples depicted in
FIGS. 15 and 16 , the number and placement of antennas on the wireless devices relative to the position and orientation of the wireless client devices may still allow for received RSSI to be sensed as being in the near field and appropriate action may be taken by the wireless devices relative to content, media, or other data carried by or accessible by the wireless client devices. Actual distances and/or ranges associated with near field, near field region, far field, far field region may be application specific and are not limited by the examples described and/or depicted herein. Actual shapes and span (e.g., distance arounddevices - 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 invention techniques. The disclosed examples are illustrative and not restrictive.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/219,648 US20140285313A1 (en) | 2013-03-15 | 2014-03-19 | Proximity sensing device control architecture and data communication protocol |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361802344P | 2013-03-15 | 2013-03-15 | |
US14/205,215 US20140286496A1 (en) | 2013-03-15 | 2014-03-11 | Proximity sensing device control architecture and data communication protocol |
US14/219,648 US20140285313A1 (en) | 2013-03-15 | 2014-03-19 | Proximity sensing device control architecture and data communication protocol |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/205,215 Continuation US20140286496A1 (en) | 2013-03-15 | 2014-03-11 | Proximity sensing device control architecture and data communication protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140285313A1 true US20140285313A1 (en) | 2014-09-25 |
Family
ID=51527182
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/210,234 Active 2034-05-06 US9349282B2 (en) | 2013-03-15 | 2014-03-13 | Proximity sensing device control architecture and data communication protocol |
US14/219,648 Abandoned US20140285313A1 (en) | 2013-03-15 | 2014-03-19 | Proximity sensing device control architecture and data communication protocol |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/210,234 Active 2034-05-06 US9349282B2 (en) | 2013-03-15 | 2014-03-13 | Proximity sensing device control architecture and data communication protocol |
Country Status (6)
Country | Link |
---|---|
US (2) | US9349282B2 (en) |
EP (1) | EP2974163A2 (en) |
AU (1) | AU2014232324A1 (en) |
CA (1) | CA2907370A1 (en) |
RU (1) | RU2015144122A (en) |
WO (1) | WO2014146002A2 (en) |
Cited By (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140354441A1 (en) * | 2013-03-13 | 2014-12-04 | Michael Edward Smith Luna | System and constituent media device components and media device-based ecosystem |
US9264839B2 (en) | 2014-03-17 | 2016-02-16 | Sonos, Inc. | Playback device configuration based on proximity detection |
US9348354B2 (en) | 2003-07-28 | 2016-05-24 | Sonos, Inc. | Systems and methods for synchronizing operations among a plurality of independently clocked digital data processing devices without a voltage controlled crystal oscillator |
US9367611B1 (en) | 2014-07-22 | 2016-06-14 | Sonos, Inc. | Detecting improper position of a playback device |
US9374607B2 (en) | 2012-06-26 | 2016-06-21 | Sonos, Inc. | Media playback system with guest access |
US9419575B2 (en) | 2014-03-17 | 2016-08-16 | Sonos, Inc. | Audio settings based on environment |
US9519454B2 (en) | 2012-08-07 | 2016-12-13 | Sonos, Inc. | Acoustic signatures |
US9538305B2 (en) | 2015-07-28 | 2017-01-03 | Sonos, Inc. | Calibration error conditions |
US20170085775A1 (en) * | 2014-06-18 | 2017-03-23 | Sony Corporation | Information processing apparatus, method, system and computer program |
US9648422B2 (en) | 2012-06-28 | 2017-05-09 | Sonos, Inc. | Concurrent multi-loudspeaker calibration with a single measurement |
US9668049B2 (en) | 2012-06-28 | 2017-05-30 | Sonos, Inc. | Playback device calibration user interfaces |
US9690539B2 (en) | 2012-06-28 | 2017-06-27 | Sonos, Inc. | Speaker calibration user interface |
US9693165B2 (en) | 2015-09-17 | 2017-06-27 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US9690271B2 (en) | 2012-06-28 | 2017-06-27 | Sonos, Inc. | Speaker calibration |
US9706323B2 (en) | 2014-09-09 | 2017-07-11 | Sonos, Inc. | Playback device calibration |
US9715367B2 (en) | 2014-09-09 | 2017-07-25 | Sonos, Inc. | Audio processing algorithms |
US9729115B2 (en) | 2012-04-27 | 2017-08-08 | Sonos, Inc. | Intelligently increasing the sound level of player |
US9734242B2 (en) | 2003-07-28 | 2017-08-15 | Sonos, Inc. | Systems and methods for synchronizing operations among a plurality of independently clocked digital data processing devices that independently source digital data |
US9743207B1 (en) | 2016-01-18 | 2017-08-22 | Sonos, Inc. | Calibration using multiple recording devices |
US9749763B2 (en) | 2014-09-09 | 2017-08-29 | Sonos, Inc. | Playback device calibration |
US9749760B2 (en) | 2006-09-12 | 2017-08-29 | Sonos, Inc. | Updating zone configuration in a multi-zone media system |
US9756424B2 (en) | 2006-09-12 | 2017-09-05 | Sonos, Inc. | Multi-channel pairing in a media system |
US9763018B1 (en) | 2016-04-12 | 2017-09-12 | Sonos, Inc. | Calibration of audio playback devices |
US9766853B2 (en) | 2006-09-12 | 2017-09-19 | Sonos, Inc. | Pair volume control |
US9781513B2 (en) | 2014-02-06 | 2017-10-03 | Sonos, Inc. | Audio output balancing |
US9787550B2 (en) | 2004-06-05 | 2017-10-10 | Sonos, Inc. | Establishing a secure wireless network with a minimum human intervention |
US9794710B1 (en) | 2016-07-15 | 2017-10-17 | Sonos, Inc. | Spatial audio correction |
US9794707B2 (en) | 2014-02-06 | 2017-10-17 | Sonos, Inc. | Audio output balancing |
US9860662B2 (en) | 2016-04-01 | 2018-01-02 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US9860670B1 (en) | 2016-07-15 | 2018-01-02 | Sonos, Inc. | Spectral correction using spatial calibration |
US9864574B2 (en) | 2016-04-01 | 2018-01-09 | Sonos, Inc. | Playback device calibration based on representation spectral characteristics |
US9891881B2 (en) | 2014-09-09 | 2018-02-13 | Sonos, Inc. | Audio processing algorithm database |
US9930470B2 (en) | 2011-12-29 | 2018-03-27 | Sonos, Inc. | Sound field calibration using listener localization |
US9977561B2 (en) | 2004-04-01 | 2018-05-22 | Sonos, Inc. | Systems, methods, apparatus, and articles of manufacture to provide guest access |
US10003899B2 (en) | 2016-01-25 | 2018-06-19 | Sonos, Inc. | Calibration with particular locations |
US20180213175A1 (en) * | 2017-01-24 | 2018-07-26 | Microsoft Technology Licensing, Llc | Linked Capture Session for Automatic Image Sharing |
US10127006B2 (en) | 2014-09-09 | 2018-11-13 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US10284983B2 (en) | 2015-04-24 | 2019-05-07 | Sonos, Inc. | Playback device calibration user interfaces |
US10299061B1 (en) | 2018-08-28 | 2019-05-21 | Sonos, Inc. | Playback device calibration |
US10306364B2 (en) | 2012-09-28 | 2019-05-28 | Sonos, Inc. | Audio processing adjustments for playback devices based on determined characteristics of audio content |
US10359987B2 (en) | 2003-07-28 | 2019-07-23 | Sonos, Inc. | Adjusting volume levels |
US10372406B2 (en) | 2016-07-22 | 2019-08-06 | Sonos, Inc. | Calibration interface |
US10459684B2 (en) | 2016-08-05 | 2019-10-29 | Sonos, Inc. | Calibration of a playback device based on an estimated frequency response |
US10585639B2 (en) | 2015-09-17 | 2020-03-10 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US10613817B2 (en) | 2003-07-28 | 2020-04-07 | Sonos, Inc. | Method and apparatus for displaying a list of tracks scheduled for playback by a synchrony group |
US10664224B2 (en) | 2015-04-24 | 2020-05-26 | Sonos, Inc. | Speaker calibration user interface |
US10734965B1 (en) | 2019-08-12 | 2020-08-04 | Sonos, Inc. | Audio calibration of a portable playback device |
US11106424B2 (en) | 2003-07-28 | 2021-08-31 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US11106423B2 (en) | 2016-01-25 | 2021-08-31 | Sonos, Inc. | Evaluating calibration of a playback device |
US11106425B2 (en) | 2003-07-28 | 2021-08-31 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US11206484B2 (en) | 2018-08-28 | 2021-12-21 | Sonos, Inc. | Passive speaker authentication |
US11265652B2 (en) | 2011-01-25 | 2022-03-01 | Sonos, Inc. | Playback device pairing |
US11294618B2 (en) | 2003-07-28 | 2022-04-05 | Sonos, Inc. | Media player system |
US11403062B2 (en) | 2015-06-11 | 2022-08-02 | Sonos, Inc. | Multiple groupings in a playback system |
US11429343B2 (en) | 2011-01-25 | 2022-08-30 | Sonos, Inc. | Stereo playback configuration and control |
US11481182B2 (en) | 2016-10-17 | 2022-10-25 | Sonos, Inc. | Room association based on name |
US11650784B2 (en) | 2003-07-28 | 2023-05-16 | Sonos, Inc. | Adjusting volume levels |
WO2023204578A1 (en) * | 2022-04-18 | 2023-10-26 | 삼성전자 주식회사 | Electronic device for providing audio service, and operation method therefor |
US11894975B2 (en) | 2004-06-05 | 2024-02-06 | Sonos, Inc. | Playback device connection |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11044451B2 (en) | 2013-03-14 | 2021-06-22 | Jawb Acquisition Llc | Proximity-based control of media devices for media presentations |
US9349282B2 (en) | 2013-03-15 | 2016-05-24 | Aliphcom | Proximity sensing device control architecture and data communication protocol |
US20140355389A1 (en) * | 2013-05-29 | 2014-12-04 | Nokia Corporation | Method and apparatus for establishing device communication |
US9866986B2 (en) | 2014-01-24 | 2018-01-09 | Sony Corporation | Audio speaker system with virtual music performance |
WO2015123658A1 (en) | 2014-02-14 | 2015-08-20 | Sonic Blocks, Inc. | Modular quick-connect a/v system and methods thereof |
US9232335B2 (en) * | 2014-03-06 | 2016-01-05 | Sony Corporation | Networked speaker system with follow me |
US9922094B1 (en) * | 2014-06-18 | 2018-03-20 | Symantec Corporation | Sharing data based on user ranking |
US20160301450A1 (en) * | 2015-01-13 | 2016-10-13 | Creating Revolutions Llc | Proximity Identification Device with Improved Orientation Features and User Feedback |
US20160259419A1 (en) * | 2015-03-05 | 2016-09-08 | Harman International Industries, Inc | Techniques for controlling devices based on user proximity |
US20160335886A1 (en) * | 2015-05-11 | 2016-11-17 | Electronics Tomorrow Limited | Wireless Alarm System |
US9999091B2 (en) | 2015-05-12 | 2018-06-12 | D&M Holdings, Inc. | System and method for negotiating group membership for audio controllers |
US11113022B2 (en) * | 2015-05-12 | 2021-09-07 | D&M Holdings, Inc. | Method, system and interface for controlling a subwoofer in a networked audio system |
US11209972B2 (en) | 2015-09-02 | 2021-12-28 | D&M Holdings, Inc. | Combined tablet screen drag-and-drop interface |
US11599328B2 (en) * | 2015-05-26 | 2023-03-07 | Disney Enterprises, Inc. | Methods and systems for playing an audio corresponding to a text medium |
US10588000B2 (en) * | 2015-06-19 | 2020-03-10 | Lenovo (Singapore) Pte. Ltd. | Determination of device at which to present audio of telephonic communication |
EP3128382B1 (en) * | 2015-08-05 | 2018-11-07 | ABB Schweiz AG | Secure mobile access for automation systems |
CN105608861B (en) * | 2015-10-29 | 2019-08-30 | 小米科技有限责任公司 | Control method of electronic device and device |
US9967884B2 (en) | 2015-11-10 | 2018-05-08 | Netgear, Inc. | Dedicated backhaul for whole home coverage |
KR102413328B1 (en) * | 2016-02-03 | 2022-06-27 | 엘지전자 주식회사 | Main speaker, sub speaker and system comprising main speaker and sub speaker |
US9693168B1 (en) | 2016-02-08 | 2017-06-27 | Sony Corporation | Ultrasonic speaker assembly for audio spatial effect |
US9826332B2 (en) | 2016-02-09 | 2017-11-21 | Sony Corporation | Centralized wireless speaker system |
US9924291B2 (en) | 2016-02-16 | 2018-03-20 | Sony Corporation | Distributed wireless speaker system |
US9826330B2 (en) | 2016-03-14 | 2017-11-21 | Sony Corporation | Gimbal-mounted linear ultrasonic speaker assembly |
US9693169B1 (en) | 2016-03-16 | 2017-06-27 | Sony Corporation | Ultrasonic speaker assembly with ultrasonic room mapping |
US10186910B2 (en) * | 2016-07-15 | 2019-01-22 | The United States Of America, As Represented By The Secretary Of The Army | Signal comparison and direction |
US10356681B2 (en) | 2016-09-21 | 2019-07-16 | Netgear, Inc. | Client roaming in a distributed multi-band wireless networking system |
US10111035B2 (en) * | 2016-10-03 | 2018-10-23 | Isaac Davenport | Real-time proximity tracking using received signal strength indication |
US10797947B2 (en) * | 2017-05-18 | 2020-10-06 | Bae Systems Controls Inc. | Initialization and configuration of end point devices using a mobile device |
US10686883B2 (en) * | 2017-07-07 | 2020-06-16 | Hewlett Packard Enterprise Development Lp | Bluetooth low energy devices |
CN110021156A (en) * | 2018-01-10 | 2019-07-16 | 金宝电子工业股份有限公司 | Remote control system and remote control method |
US10414629B2 (en) | 2018-01-22 | 2019-09-17 | Otis Elevator Company | Mechanical system service tool |
TWI682091B (en) * | 2018-12-14 | 2020-01-11 | 財團法人工業技術研究院 | Intelligent door lock, control method thereof, and unlocking apparatus and method thereof |
DE102019124217A1 (en) * | 2019-06-11 | 2020-12-17 | Huf Hülsbeck & Fürst Gmbh & Co. Kg | arrangement |
IT201900013962A1 (en) * | 2019-08-05 | 2021-02-05 | De Longhi Appliances Srl | CONDITIONING APPARATUS AND REGULATION METHOD |
US11443737B2 (en) | 2020-01-14 | 2022-09-13 | Sony Corporation | Audio video translation into multiple languages for respective listeners |
US11564148B2 (en) | 2020-07-08 | 2023-01-24 | Trane International Inc. | Systems and methods for seamlessly transferring a radio connection between components of a climate control system |
CN115377653A (en) * | 2021-05-18 | 2022-11-22 | 广州视源电子科技股份有限公司 | Loudspeaker module and electronic equipment |
CN115175454B (en) * | 2022-09-08 | 2023-01-20 | 荣耀终端有限公司 | Electronic equipment |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8467324B2 (en) * | 2010-11-03 | 2013-06-18 | Broadcom Corporation | Managing devices within a vehicular communication network |
US8634796B2 (en) * | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
US8705527B1 (en) * | 2011-01-14 | 2014-04-22 | Cisco Technology, Inc. | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US8897741B2 (en) * | 2009-11-13 | 2014-11-25 | William J. Johnson | System and method for mobile device usability by locational conditions |
US9020697B2 (en) * | 2012-03-14 | 2015-04-28 | Flextronics Ap, Llc | Vehicle-based multimode discovery |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1793326A3 (en) | 2002-01-09 | 2008-06-11 | Vue Technology, Inc. | Intelligent station using multiple RF antennae and inventory control system and method incorporating same |
AU2006200114B2 (en) * | 2005-03-31 | 2009-05-21 | Innovative Design Co Pty Ltd | Container closure |
US7573820B2 (en) | 2005-06-29 | 2009-08-11 | Intel Corporation | Techniques to control data transmission for a wireless system |
WO2007032173A1 (en) * | 2005-09-15 | 2007-03-22 | Sony Computer Entertainment Inc. | Information processor and controller device |
US20070116007A1 (en) | 2005-11-18 | 2007-05-24 | Weimin Xiao | Method and system for scheduling and resource allocation in a data communication network |
US8111684B2 (en) | 2007-03-30 | 2012-02-07 | Cisco Technology, Inc. | Path shortening in a wireless mesh network |
US8942219B2 (en) | 2007-04-13 | 2015-01-27 | Hart Communication Foundation | Support for network management and device communications in a wireless network |
US20090144456A1 (en) | 2007-11-30 | 2009-06-04 | Alexander David Gelf | Interface Device for Securely Extending Computer Functionality |
US8107999B2 (en) | 2009-09-08 | 2012-01-31 | Murata Manufacturing Co., Ltd. | Communication device and method of communicating transmissions |
US9167991B2 (en) | 2010-09-30 | 2015-10-27 | Fitbit, Inc. | Portable monitoring devices and methods of operating same |
US9560444B2 (en) * | 2013-03-13 | 2017-01-31 | Cisco Technology, Inc. | Kinetic event detection in microphones |
US9349282B2 (en) | 2013-03-15 | 2016-05-24 | Aliphcom | Proximity sensing device control architecture and data communication protocol |
-
2014
- 2014-03-13 US US14/210,234 patent/US9349282B2/en active Active
- 2014-03-17 CA CA2907370A patent/CA2907370A1/en not_active Abandoned
- 2014-03-17 RU RU2015144122A patent/RU2015144122A/en not_active Application Discontinuation
- 2014-03-17 WO PCT/US2014/030870 patent/WO2014146002A2/en active Application Filing
- 2014-03-17 EP EP14765027.9A patent/EP2974163A2/en not_active Withdrawn
- 2014-03-17 AU AU2014232324A patent/AU2014232324A1/en not_active Abandoned
- 2014-03-19 US US14/219,648 patent/US20140285313A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8634796B2 (en) * | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
US8897741B2 (en) * | 2009-11-13 | 2014-11-25 | William J. Johnson | System and method for mobile device usability by locational conditions |
US8467324B2 (en) * | 2010-11-03 | 2013-06-18 | Broadcom Corporation | Managing devices within a vehicular communication network |
US8705527B1 (en) * | 2011-01-14 | 2014-04-22 | Cisco Technology, Inc. | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US9020697B2 (en) * | 2012-03-14 | 2015-04-28 | Flextronics Ap, Llc | Vehicle-based multimode discovery |
Cited By (262)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11625221B2 (en) | 2003-07-28 | 2023-04-11 | Sonos, Inc | Synchronizing playback by media playback devices |
US9733893B2 (en) | 2003-07-28 | 2017-08-15 | Sonos, Inc. | Obtaining and transmitting audio |
US10754612B2 (en) | 2003-07-28 | 2020-08-25 | Sonos, Inc. | Playback device volume control |
US9348354B2 (en) | 2003-07-28 | 2016-05-24 | Sonos, Inc. | Systems and methods for synchronizing operations among a plurality of independently clocked digital data processing devices without a voltage controlled crystal oscillator |
US9354656B2 (en) | 2003-07-28 | 2016-05-31 | Sonos, Inc. | Method and apparatus for dynamic channelization device switching in a synchrony group |
US10031715B2 (en) | 2003-07-28 | 2018-07-24 | Sonos, Inc. | Method and apparatus for dynamic master device switching in a synchrony group |
US10747496B2 (en) | 2003-07-28 | 2020-08-18 | Sonos, Inc. | Playback device |
US10949163B2 (en) | 2003-07-28 | 2021-03-16 | Sonos, Inc. | Playback device |
US10956119B2 (en) | 2003-07-28 | 2021-03-23 | Sonos, Inc. | Playback device |
US10963215B2 (en) | 2003-07-28 | 2021-03-30 | Sonos, Inc. | Media playback device and system |
US10324684B2 (en) | 2003-07-28 | 2019-06-18 | Sonos, Inc. | Playback device synchrony group states |
US10970034B2 (en) | 2003-07-28 | 2021-04-06 | Sonos, Inc. | Audio distributor selection |
US10613817B2 (en) | 2003-07-28 | 2020-04-07 | Sonos, Inc. | Method and apparatus for displaying a list of tracks scheduled for playback by a synchrony group |
US11301207B1 (en) | 2003-07-28 | 2022-04-12 | Sonos, Inc. | Playback device |
US10133536B2 (en) | 2003-07-28 | 2018-11-20 | Sonos, Inc. | Method and apparatus for adjusting volume in a synchrony group |
US10140085B2 (en) | 2003-07-28 | 2018-11-27 | Sonos, Inc. | Playback device operating states |
US10146498B2 (en) | 2003-07-28 | 2018-12-04 | Sonos, Inc. | Disengaging and engaging zone players |
US10545723B2 (en) | 2003-07-28 | 2020-01-28 | Sonos, Inc. | Playback device |
US9658820B2 (en) | 2003-07-28 | 2017-05-23 | Sonos, Inc. | Resuming synchronous playback of content |
US11294618B2 (en) | 2003-07-28 | 2022-04-05 | Sonos, Inc. | Media player system |
US10303431B2 (en) | 2003-07-28 | 2019-05-28 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US10445054B2 (en) | 2003-07-28 | 2019-10-15 | Sonos, Inc. | Method and apparatus for switching between a directly connected and a networked audio source |
US10157035B2 (en) | 2003-07-28 | 2018-12-18 | Sonos, Inc. | Switching between a directly connected and a networked audio source |
US11080001B2 (en) | 2003-07-28 | 2021-08-03 | Sonos, Inc. | Concurrent transmission and playback of audio information |
US11106424B2 (en) | 2003-07-28 | 2021-08-31 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US10303432B2 (en) | 2003-07-28 | 2019-05-28 | Sonos, Inc | Playback device |
US9727302B2 (en) | 2003-07-28 | 2017-08-08 | Sonos, Inc. | Obtaining content from remote source for playback |
US9727303B2 (en) | 2003-07-28 | 2017-08-08 | Sonos, Inc. | Resuming synchronous playback of content |
US11106425B2 (en) | 2003-07-28 | 2021-08-31 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US9734242B2 (en) | 2003-07-28 | 2017-08-15 | Sonos, Inc. | Systems and methods for synchronizing operations among a plurality of independently clocked digital data processing devices that independently source digital data |
US9733891B2 (en) | 2003-07-28 | 2017-08-15 | Sonos, Inc. | Obtaining content from local and remote sources for playback |
US10175930B2 (en) | 2003-07-28 | 2019-01-08 | Sonos, Inc. | Method and apparatus for playback by a synchrony group |
US11132170B2 (en) | 2003-07-28 | 2021-09-28 | Sonos, Inc. | Adjusting volume levels |
US9733892B2 (en) | 2003-07-28 | 2017-08-15 | Sonos, Inc. | Obtaining content based on control by multiple controllers |
US9740453B2 (en) | 2003-07-28 | 2017-08-22 | Sonos, Inc. | Obtaining content from multiple remote sources for playback |
US10387102B2 (en) | 2003-07-28 | 2019-08-20 | Sonos, Inc. | Playback device grouping |
US10365884B2 (en) | 2003-07-28 | 2019-07-30 | Sonos, Inc. | Group volume control |
US10359987B2 (en) | 2003-07-28 | 2019-07-23 | Sonos, Inc. | Adjusting volume levels |
US10120638B2 (en) | 2003-07-28 | 2018-11-06 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US10157033B2 (en) | 2003-07-28 | 2018-12-18 | Sonos, Inc. | Method and apparatus for switching between a directly connected and a networked audio source |
US9727304B2 (en) | 2003-07-28 | 2017-08-08 | Sonos, Inc. | Obtaining content from direct source and other source |
US11200025B2 (en) | 2003-07-28 | 2021-12-14 | Sonos, Inc. | Playback device |
US10296283B2 (en) | 2003-07-28 | 2019-05-21 | Sonos, Inc. | Directing synchronous playback between zone players |
US9778897B2 (en) | 2003-07-28 | 2017-10-03 | Sonos, Inc. | Ceasing playback among a plurality of playback devices |
US10289380B2 (en) | 2003-07-28 | 2019-05-14 | Sonos, Inc. | Playback device |
US9778900B2 (en) | 2003-07-28 | 2017-10-03 | Sonos, Inc. | Causing a device to join a synchrony group |
US10282164B2 (en) | 2003-07-28 | 2019-05-07 | Sonos, Inc. | Synchronizing operations among a plurality of independently clocked digital data processing devices |
US10228902B2 (en) | 2003-07-28 | 2019-03-12 | Sonos, Inc. | Playback device |
US9778898B2 (en) | 2003-07-28 | 2017-10-03 | Sonos, Inc. | Resynchronization of playback devices |
US11650784B2 (en) | 2003-07-28 | 2023-05-16 | Sonos, Inc. | Adjusting volume levels |
US10216473B2 (en) | 2003-07-28 | 2019-02-26 | Sonos, Inc. | Playback device synchrony group states |
US10157034B2 (en) | 2003-07-28 | 2018-12-18 | Sonos, Inc. | Clock rate adjustment in a multi-zone system |
US11635935B2 (en) | 2003-07-28 | 2023-04-25 | Sonos, Inc. | Adjusting volume levels |
US10209953B2 (en) | 2003-07-28 | 2019-02-19 | Sonos, Inc. | Playback device |
US10185541B2 (en) | 2003-07-28 | 2019-01-22 | Sonos, Inc. | Playback device |
US10185540B2 (en) | 2003-07-28 | 2019-01-22 | Sonos, Inc. | Playback device |
US10175932B2 (en) | 2003-07-28 | 2019-01-08 | Sonos, Inc. | Obtaining content from direct source and remote source |
US10754613B2 (en) | 2003-07-28 | 2020-08-25 | Sonos, Inc. | Audio master selection |
US11556305B2 (en) | 2003-07-28 | 2023-01-17 | Sonos, Inc. | Synchronizing playback by media playback devices |
US11550539B2 (en) | 2003-07-28 | 2023-01-10 | Sonos, Inc. | Playback device |
US11550536B2 (en) | 2003-07-28 | 2023-01-10 | Sonos, Inc. | Adjusting volume levels |
US11467799B2 (en) | 2004-04-01 | 2022-10-11 | Sonos, Inc. | Guest access to a media playback system |
US9977561B2 (en) | 2004-04-01 | 2018-05-22 | Sonos, Inc. | Systems, methods, apparatus, and articles of manufacture to provide guest access |
US10983750B2 (en) | 2004-04-01 | 2021-04-20 | Sonos, Inc. | Guest access to a media playback system |
US11907610B2 (en) | 2004-04-01 | 2024-02-20 | Sonos, Inc. | Guess access to a media playback system |
US11025509B2 (en) | 2004-06-05 | 2021-06-01 | Sonos, Inc. | Playback device connection |
US10541883B2 (en) | 2004-06-05 | 2020-01-21 | Sonos, Inc. | Playback device connection |
US11894975B2 (en) | 2004-06-05 | 2024-02-06 | Sonos, Inc. | Playback device connection |
US10439896B2 (en) | 2004-06-05 | 2019-10-08 | Sonos, Inc. | Playback device connection |
US9960969B2 (en) | 2004-06-05 | 2018-05-01 | Sonos, Inc. | Playback device connection |
US9787550B2 (en) | 2004-06-05 | 2017-10-10 | Sonos, Inc. | Establishing a secure wireless network with a minimum human intervention |
US9866447B2 (en) | 2004-06-05 | 2018-01-09 | Sonos, Inc. | Indicator on a network device |
US10979310B2 (en) | 2004-06-05 | 2021-04-13 | Sonos, Inc. | Playback device connection |
US10965545B2 (en) | 2004-06-05 | 2021-03-30 | Sonos, Inc. | Playback device connection |
US10097423B2 (en) | 2004-06-05 | 2018-10-09 | Sonos, Inc. | Establishing a secure wireless network with minimum human intervention |
US11456928B2 (en) | 2004-06-05 | 2022-09-27 | Sonos, Inc. | Playback device connection |
US11909588B2 (en) | 2004-06-05 | 2024-02-20 | Sonos, Inc. | Wireless device connection |
US9766853B2 (en) | 2006-09-12 | 2017-09-19 | Sonos, Inc. | Pair volume control |
US11388532B2 (en) | 2006-09-12 | 2022-07-12 | Sonos, Inc. | Zone scene activation |
US10028056B2 (en) | 2006-09-12 | 2018-07-17 | Sonos, Inc. | Multi-channel pairing in a media system |
US10848885B2 (en) | 2006-09-12 | 2020-11-24 | Sonos, Inc. | Zone scene management |
US10897679B2 (en) | 2006-09-12 | 2021-01-19 | Sonos, Inc. | Zone scene management |
US11540050B2 (en) | 2006-09-12 | 2022-12-27 | Sonos, Inc. | Playback device pairing |
US10306365B2 (en) | 2006-09-12 | 2019-05-28 | Sonos, Inc. | Playback device pairing |
US9756424B2 (en) | 2006-09-12 | 2017-09-05 | Sonos, Inc. | Multi-channel pairing in a media system |
US9749760B2 (en) | 2006-09-12 | 2017-08-29 | Sonos, Inc. | Updating zone configuration in a multi-zone media system |
US10966025B2 (en) | 2006-09-12 | 2021-03-30 | Sonos, Inc. | Playback device pairing |
US11385858B2 (en) | 2006-09-12 | 2022-07-12 | Sonos, Inc. | Predefined multi-channel listening environment |
US10448159B2 (en) | 2006-09-12 | 2019-10-15 | Sonos, Inc. | Playback device pairing |
US9928026B2 (en) | 2006-09-12 | 2018-03-27 | Sonos, Inc. | Making and indicating a stereo pair |
US10228898B2 (en) | 2006-09-12 | 2019-03-12 | Sonos, Inc. | Identification of playback device and stereo pair names |
US9813827B2 (en) | 2006-09-12 | 2017-11-07 | Sonos, Inc. | Zone configuration based on playback selections |
US10555082B2 (en) | 2006-09-12 | 2020-02-04 | Sonos, Inc. | Playback device pairing |
US10469966B2 (en) | 2006-09-12 | 2019-11-05 | Sonos, Inc. | Zone scene management |
US10136218B2 (en) | 2006-09-12 | 2018-11-20 | Sonos, Inc. | Playback device pairing |
US11082770B2 (en) | 2006-09-12 | 2021-08-03 | Sonos, Inc. | Multi-channel pairing in a media system |
US9860657B2 (en) | 2006-09-12 | 2018-01-02 | Sonos, Inc. | Zone configurations maintained by playback device |
US11265652B2 (en) | 2011-01-25 | 2022-03-01 | Sonos, Inc. | Playback device pairing |
US11429343B2 (en) | 2011-01-25 | 2022-08-30 | Sonos, Inc. | Stereo playback configuration and control |
US11758327B2 (en) | 2011-01-25 | 2023-09-12 | Sonos, Inc. | Playback device pairing |
US9930470B2 (en) | 2011-12-29 | 2018-03-27 | Sonos, Inc. | Sound field calibration using listener localization |
US11290838B2 (en) | 2011-12-29 | 2022-03-29 | Sonos, Inc. | Playback based on user presence detection |
US10455347B2 (en) | 2011-12-29 | 2019-10-22 | Sonos, Inc. | Playback based on number of listeners |
US11528578B2 (en) | 2011-12-29 | 2022-12-13 | Sonos, Inc. | Media playback based on sensor data |
US10986460B2 (en) | 2011-12-29 | 2021-04-20 | Sonos, Inc. | Grouping based on acoustic signals |
US11849299B2 (en) | 2011-12-29 | 2023-12-19 | Sonos, Inc. | Media playback based on sensor data |
US11825290B2 (en) | 2011-12-29 | 2023-11-21 | Sonos, Inc. | Media playback based on sensor data |
US11910181B2 (en) | 2011-12-29 | 2024-02-20 | Sonos, Inc | Media playback based on sensor data |
US11197117B2 (en) | 2011-12-29 | 2021-12-07 | Sonos, Inc. | Media playback based on sensor data |
US11889290B2 (en) | 2011-12-29 | 2024-01-30 | Sonos, Inc. | Media playback based on sensor data |
US10945089B2 (en) | 2011-12-29 | 2021-03-09 | Sonos, Inc. | Playback based on user settings |
US11122382B2 (en) | 2011-12-29 | 2021-09-14 | Sonos, Inc. | Playback based on acoustic signals |
US11153706B1 (en) | 2011-12-29 | 2021-10-19 | Sonos, Inc. | Playback based on acoustic signals |
US11825289B2 (en) | 2011-12-29 | 2023-11-21 | Sonos, Inc. | Media playback based on sensor data |
US10334386B2 (en) | 2011-12-29 | 2019-06-25 | Sonos, Inc. | Playback based on wireless signal |
US10720896B2 (en) | 2012-04-27 | 2020-07-21 | Sonos, Inc. | Intelligently modifying the gain parameter of a playback device |
US10063202B2 (en) | 2012-04-27 | 2018-08-28 | Sonos, Inc. | Intelligently modifying the gain parameter of a playback device |
US9729115B2 (en) | 2012-04-27 | 2017-08-08 | Sonos, Inc. | Intelligently increasing the sound level of player |
US9374607B2 (en) | 2012-06-26 | 2016-06-21 | Sonos, Inc. | Media playback system with guest access |
US9913057B2 (en) | 2012-06-28 | 2018-03-06 | Sonos, Inc. | Concurrent multi-loudspeaker calibration with a single measurement |
US11368803B2 (en) | 2012-06-28 | 2022-06-21 | Sonos, Inc. | Calibration of playback device(s) |
US10045138B2 (en) | 2012-06-28 | 2018-08-07 | Sonos, Inc. | Hybrid test tone for space-averaged room audio calibration using a moving microphone |
US10791405B2 (en) | 2012-06-28 | 2020-09-29 | Sonos, Inc. | Calibration indicator |
US11516608B2 (en) | 2012-06-28 | 2022-11-29 | Sonos, Inc. | Calibration state variable |
US10296282B2 (en) | 2012-06-28 | 2019-05-21 | Sonos, Inc. | Speaker calibration user interface |
US11800305B2 (en) | 2012-06-28 | 2023-10-24 | Sonos, Inc. | Calibration interface |
US9749744B2 (en) | 2012-06-28 | 2017-08-29 | Sonos, Inc. | Playback device calibration |
US10284984B2 (en) | 2012-06-28 | 2019-05-07 | Sonos, Inc. | Calibration state variable |
US10674293B2 (en) | 2012-06-28 | 2020-06-02 | Sonos, Inc. | Concurrent multi-driver calibration |
US9736584B2 (en) | 2012-06-28 | 2017-08-15 | Sonos, Inc. | Hybrid test tone for space-averaged room audio calibration using a moving microphone |
US10390159B2 (en) | 2012-06-28 | 2019-08-20 | Sonos, Inc. | Concurrent multi-loudspeaker calibration |
US10129674B2 (en) | 2012-06-28 | 2018-11-13 | Sonos, Inc. | Concurrent multi-loudspeaker calibration |
US11516606B2 (en) | 2012-06-28 | 2022-11-29 | Sonos, Inc. | Calibration interface |
US9648422B2 (en) | 2012-06-28 | 2017-05-09 | Sonos, Inc. | Concurrent multi-loudspeaker calibration with a single measurement |
US9788113B2 (en) | 2012-06-28 | 2017-10-10 | Sonos, Inc. | Calibration state variable |
US9668049B2 (en) | 2012-06-28 | 2017-05-30 | Sonos, Inc. | Playback device calibration user interfaces |
US10412516B2 (en) | 2012-06-28 | 2019-09-10 | Sonos, Inc. | Calibration of playback devices |
US9961463B2 (en) | 2012-06-28 | 2018-05-01 | Sonos, Inc. | Calibration indicator |
US9690271B2 (en) | 2012-06-28 | 2017-06-27 | Sonos, Inc. | Speaker calibration |
US9820045B2 (en) | 2012-06-28 | 2017-11-14 | Sonos, Inc. | Playback calibration |
US9690539B2 (en) | 2012-06-28 | 2017-06-27 | Sonos, Inc. | Speaker calibration user interface |
US10045139B2 (en) | 2012-06-28 | 2018-08-07 | Sonos, Inc. | Calibration state variable |
US11064306B2 (en) | 2012-06-28 | 2021-07-13 | Sonos, Inc. | Calibration state variable |
US9519454B2 (en) | 2012-08-07 | 2016-12-13 | Sonos, Inc. | Acoustic signatures |
US10051397B2 (en) | 2012-08-07 | 2018-08-14 | Sonos, Inc. | Acoustic signatures |
US10904685B2 (en) | 2012-08-07 | 2021-01-26 | Sonos, Inc. | Acoustic signatures in a playback system |
US9998841B2 (en) | 2012-08-07 | 2018-06-12 | Sonos, Inc. | Acoustic signatures |
US11729568B2 (en) | 2012-08-07 | 2023-08-15 | Sonos, Inc. | Acoustic signatures in a playback system |
US10306364B2 (en) | 2012-09-28 | 2019-05-28 | Sonos, Inc. | Audio processing adjustments for playback devices based on determined characteristics of audio content |
US20140354441A1 (en) * | 2013-03-13 | 2014-12-04 | Michael Edward Smith Luna | System and constituent media device components and media device-based ecosystem |
US9794707B2 (en) | 2014-02-06 | 2017-10-17 | Sonos, Inc. | Audio output balancing |
US9781513B2 (en) | 2014-02-06 | 2017-10-03 | Sonos, Inc. | Audio output balancing |
US9521487B2 (en) | 2014-03-17 | 2016-12-13 | Sonos, Inc. | Calibration adjustment based on barrier |
US9419575B2 (en) | 2014-03-17 | 2016-08-16 | Sonos, Inc. | Audio settings based on environment |
US10129675B2 (en) | 2014-03-17 | 2018-11-13 | Sonos, Inc. | Audio settings of multiple speakers in a playback device |
US9743208B2 (en) | 2014-03-17 | 2017-08-22 | Sonos, Inc. | Playback device configuration based on proximity detection |
US9516419B2 (en) | 2014-03-17 | 2016-12-06 | Sonos, Inc. | Playback device setting according to threshold(s) |
US11540073B2 (en) | 2014-03-17 | 2022-12-27 | Sonos, Inc. | Playback device self-calibration |
US11696081B2 (en) | 2014-03-17 | 2023-07-04 | Sonos, Inc. | Audio settings based on environment |
US9439022B2 (en) | 2014-03-17 | 2016-09-06 | Sonos, Inc. | Playback device speaker configuration based on proximity detection |
US9439021B2 (en) | 2014-03-17 | 2016-09-06 | Sonos, Inc. | Proximity detection using audio pulse |
US9521488B2 (en) | 2014-03-17 | 2016-12-13 | Sonos, Inc. | Playback device setting based on distortion |
US10299055B2 (en) | 2014-03-17 | 2019-05-21 | Sonos, Inc. | Restoration of playback device configuration |
US10051399B2 (en) | 2014-03-17 | 2018-08-14 | Sonos, Inc. | Playback device configuration according to distortion threshold |
US9344829B2 (en) | 2014-03-17 | 2016-05-17 | Sonos, Inc. | Indication of barrier detection |
US9264839B2 (en) | 2014-03-17 | 2016-02-16 | Sonos, Inc. | Playback device configuration based on proximity detection |
US10863295B2 (en) | 2014-03-17 | 2020-12-08 | Sonos, Inc. | Indoor/outdoor playback device calibration |
US10791407B2 (en) | 2014-03-17 | 2020-09-29 | Sonon, Inc. | Playback device configuration |
US10412517B2 (en) | 2014-03-17 | 2019-09-10 | Sonos, Inc. | Calibration of playback device to target curve |
US10511924B2 (en) | 2014-03-17 | 2019-12-17 | Sonos, Inc. | Playback device with multiple sensors |
US9872119B2 (en) | 2014-03-17 | 2018-01-16 | Sonos, Inc. | Audio settings of multiple speakers in a playback device |
US10404903B2 (en) * | 2014-06-18 | 2019-09-03 | Sony Corporation | Information processing apparatus, method, system and computer program |
US20170085775A1 (en) * | 2014-06-18 | 2017-03-23 | Sony Corporation | Information processing apparatus, method, system and computer program |
US9367611B1 (en) | 2014-07-22 | 2016-06-14 | Sonos, Inc. | Detecting improper position of a playback device |
US9521489B2 (en) | 2014-07-22 | 2016-12-13 | Sonos, Inc. | Operation using positioning information |
US9778901B2 (en) | 2014-07-22 | 2017-10-03 | Sonos, Inc. | Operation using positioning information |
US9952825B2 (en) | 2014-09-09 | 2018-04-24 | Sonos, Inc. | Audio processing algorithms |
US10701501B2 (en) | 2014-09-09 | 2020-06-30 | Sonos, Inc. | Playback device calibration |
US10154359B2 (en) | 2014-09-09 | 2018-12-11 | Sonos, Inc. | Playback device calibration |
US9706323B2 (en) | 2014-09-09 | 2017-07-11 | Sonos, Inc. | Playback device calibration |
US9715367B2 (en) | 2014-09-09 | 2017-07-25 | Sonos, Inc. | Audio processing algorithms |
US10271150B2 (en) | 2014-09-09 | 2019-04-23 | Sonos, Inc. | Playback device calibration |
US9749763B2 (en) | 2014-09-09 | 2017-08-29 | Sonos, Inc. | Playback device calibration |
US10127006B2 (en) | 2014-09-09 | 2018-11-13 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US9936318B2 (en) | 2014-09-09 | 2018-04-03 | Sonos, Inc. | Playback device calibration |
US10599386B2 (en) | 2014-09-09 | 2020-03-24 | Sonos, Inc. | Audio processing algorithms |
US9910634B2 (en) | 2014-09-09 | 2018-03-06 | Sonos, Inc. | Microphone calibration |
US9891881B2 (en) | 2014-09-09 | 2018-02-13 | Sonos, Inc. | Audio processing algorithm database |
US11625219B2 (en) | 2014-09-09 | 2023-04-11 | Sonos, Inc. | Audio processing algorithms |
US10127008B2 (en) | 2014-09-09 | 2018-11-13 | Sonos, Inc. | Audio processing algorithm database |
US11029917B2 (en) | 2014-09-09 | 2021-06-08 | Sonos, Inc. | Audio processing algorithms |
US9781532B2 (en) | 2014-09-09 | 2017-10-03 | Sonos, Inc. | Playback device calibration |
US10664224B2 (en) | 2015-04-24 | 2020-05-26 | Sonos, Inc. | Speaker calibration user interface |
US10284983B2 (en) | 2015-04-24 | 2019-05-07 | Sonos, Inc. | Playback device calibration user interfaces |
US11403062B2 (en) | 2015-06-11 | 2022-08-02 | Sonos, Inc. | Multiple groupings in a playback system |
US9781533B2 (en) | 2015-07-28 | 2017-10-03 | Sonos, Inc. | Calibration error conditions |
US9538305B2 (en) | 2015-07-28 | 2017-01-03 | Sonos, Inc. | Calibration error conditions |
US10129679B2 (en) | 2015-07-28 | 2018-11-13 | Sonos, Inc. | Calibration error conditions |
US10462592B2 (en) | 2015-07-28 | 2019-10-29 | Sonos, Inc. | Calibration error conditions |
US9693165B2 (en) | 2015-09-17 | 2017-06-27 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US11706579B2 (en) | 2015-09-17 | 2023-07-18 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US11099808B2 (en) | 2015-09-17 | 2021-08-24 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US9992597B2 (en) | 2015-09-17 | 2018-06-05 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US11197112B2 (en) | 2015-09-17 | 2021-12-07 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US10419864B2 (en) | 2015-09-17 | 2019-09-17 | Sonos, Inc. | Validation of audio calibration using multi-dimensional motion check |
US11803350B2 (en) | 2015-09-17 | 2023-10-31 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US10585639B2 (en) | 2015-09-17 | 2020-03-10 | Sonos, Inc. | Facilitating calibration of an audio playback device |
US10841719B2 (en) | 2016-01-18 | 2020-11-17 | Sonos, Inc. | Calibration using multiple recording devices |
US9743207B1 (en) | 2016-01-18 | 2017-08-22 | Sonos, Inc. | Calibration using multiple recording devices |
US11800306B2 (en) | 2016-01-18 | 2023-10-24 | Sonos, Inc. | Calibration using multiple recording devices |
US11432089B2 (en) | 2016-01-18 | 2022-08-30 | Sonos, Inc. | Calibration using multiple recording devices |
US10063983B2 (en) | 2016-01-18 | 2018-08-28 | Sonos, Inc. | Calibration using multiple recording devices |
US10405117B2 (en) | 2016-01-18 | 2019-09-03 | Sonos, Inc. | Calibration using multiple recording devices |
US11106423B2 (en) | 2016-01-25 | 2021-08-31 | Sonos, Inc. | Evaluating calibration of a playback device |
US10735879B2 (en) | 2016-01-25 | 2020-08-04 | Sonos, Inc. | Calibration based on grouping |
US11006232B2 (en) | 2016-01-25 | 2021-05-11 | Sonos, Inc. | Calibration based on audio content |
US11516612B2 (en) | 2016-01-25 | 2022-11-29 | Sonos, Inc. | Calibration based on audio content |
US10390161B2 (en) | 2016-01-25 | 2019-08-20 | Sonos, Inc. | Calibration based on audio content type |
US10003899B2 (en) | 2016-01-25 | 2018-06-19 | Sonos, Inc. | Calibration with particular locations |
US11184726B2 (en) | 2016-01-25 | 2021-11-23 | Sonos, Inc. | Calibration using listener locations |
US11379179B2 (en) | 2016-04-01 | 2022-07-05 | Sonos, Inc. | Playback device calibration based on representative spectral characteristics |
US11212629B2 (en) | 2016-04-01 | 2021-12-28 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US11736877B2 (en) | 2016-04-01 | 2023-08-22 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US10405116B2 (en) | 2016-04-01 | 2019-09-03 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US10880664B2 (en) | 2016-04-01 | 2020-12-29 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US10884698B2 (en) | 2016-04-01 | 2021-01-05 | Sonos, Inc. | Playback device calibration based on representative spectral characteristics |
US10402154B2 (en) | 2016-04-01 | 2019-09-03 | Sonos, Inc. | Playback device calibration based on representative spectral characteristics |
US9860662B2 (en) | 2016-04-01 | 2018-01-02 | Sonos, Inc. | Updating playback device configuration information based on calibration data |
US9864574B2 (en) | 2016-04-01 | 2018-01-09 | Sonos, Inc. | Playback device calibration based on representation spectral characteristics |
US10299054B2 (en) | 2016-04-12 | 2019-05-21 | Sonos, Inc. | Calibration of audio playback devices |
US10750304B2 (en) | 2016-04-12 | 2020-08-18 | Sonos, Inc. | Calibration of audio playback devices |
US11218827B2 (en) | 2016-04-12 | 2022-01-04 | Sonos, Inc. | Calibration of audio playback devices |
US9763018B1 (en) | 2016-04-12 | 2017-09-12 | Sonos, Inc. | Calibration of audio playback devices |
US11889276B2 (en) | 2016-04-12 | 2024-01-30 | Sonos, Inc. | Calibration of audio playback devices |
US10045142B2 (en) | 2016-04-12 | 2018-08-07 | Sonos, Inc. | Calibration of audio playback devices |
US9794710B1 (en) | 2016-07-15 | 2017-10-17 | Sonos, Inc. | Spatial audio correction |
US9860670B1 (en) | 2016-07-15 | 2018-01-02 | Sonos, Inc. | Spectral correction using spatial calibration |
US11337017B2 (en) | 2016-07-15 | 2022-05-17 | Sonos, Inc. | Spatial audio correction |
US11736878B2 (en) | 2016-07-15 | 2023-08-22 | Sonos, Inc. | Spatial audio correction |
US10448194B2 (en) | 2016-07-15 | 2019-10-15 | Sonos, Inc. | Spectral correction using spatial calibration |
US10750303B2 (en) | 2016-07-15 | 2020-08-18 | Sonos, Inc. | Spatial audio correction |
US10129678B2 (en) | 2016-07-15 | 2018-11-13 | Sonos, Inc. | Spatial audio correction |
US11531514B2 (en) | 2016-07-22 | 2022-12-20 | Sonos, Inc. | Calibration assistance |
US10372406B2 (en) | 2016-07-22 | 2019-08-06 | Sonos, Inc. | Calibration interface |
US11237792B2 (en) | 2016-07-22 | 2022-02-01 | Sonos, Inc. | Calibration assistance |
US10853022B2 (en) | 2016-07-22 | 2020-12-01 | Sonos, Inc. | Calibration interface |
US11698770B2 (en) | 2016-08-05 | 2023-07-11 | Sonos, Inc. | Calibration of a playback device based on an estimated frequency response |
US10853027B2 (en) | 2016-08-05 | 2020-12-01 | Sonos, Inc. | Calibration of a playback device based on an estimated frequency response |
US10459684B2 (en) | 2016-08-05 | 2019-10-29 | Sonos, Inc. | Calibration of a playback device based on an estimated frequency response |
US11481182B2 (en) | 2016-10-17 | 2022-10-25 | Sonos, Inc. | Room association based on name |
US10740388B2 (en) * | 2017-01-24 | 2020-08-11 | Microsoft Technology Licensing, Llc | Linked capture session for automatic image sharing |
US20180213175A1 (en) * | 2017-01-24 | 2018-07-26 | Microsoft Technology Licensing, Llc | Linked Capture Session for Automatic Image Sharing |
US11206484B2 (en) | 2018-08-28 | 2021-12-21 | Sonos, Inc. | Passive speaker authentication |
US10299061B1 (en) | 2018-08-28 | 2019-05-21 | Sonos, Inc. | Playback device calibration |
US11877139B2 (en) | 2018-08-28 | 2024-01-16 | Sonos, Inc. | Playback device calibration |
US11350233B2 (en) | 2018-08-28 | 2022-05-31 | Sonos, Inc. | Playback device calibration |
US10848892B2 (en) | 2018-08-28 | 2020-11-24 | Sonos, Inc. | Playback device calibration |
US10582326B1 (en) | 2018-08-28 | 2020-03-03 | Sonos, Inc. | Playback device calibration |
US10734965B1 (en) | 2019-08-12 | 2020-08-04 | Sonos, Inc. | Audio calibration of a portable playback device |
US11728780B2 (en) | 2019-08-12 | 2023-08-15 | Sonos, Inc. | Audio calibration of a portable playback device |
US11374547B2 (en) | 2019-08-12 | 2022-06-28 | Sonos, Inc. | Audio calibration of a portable playback device |
WO2023204578A1 (en) * | 2022-04-18 | 2023-10-26 | 삼성전자 주식회사 | Electronic device for providing audio service, and operation method therefor |
Also Published As
Publication number | Publication date |
---|---|
CA2907370A1 (en) | 2014-09-18 |
WO2014146002A3 (en) | 2014-11-06 |
US20140270306A1 (en) | 2014-09-18 |
RU2015144122A (en) | 2017-04-24 |
WO2014146002A2 (en) | 2014-09-18 |
AU2014232324A1 (en) | 2015-11-05 |
EP2974163A2 (en) | 2016-01-20 |
US9349282B2 (en) | 2016-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20140285313A1 (en) | Proximity sensing device control architecture and data communication protocol | |
US20140286496A1 (en) | Proximity sensing device control architecture and data communication protocol | |
JP7307146B2 (en) | Near field antenna for wireless power transmission with four coplanar antenna elements | |
JP2008178114A (en) | Data transferring system, wireless communication apparatus, wireless communication method, and computer program | |
US8912968B2 (en) | True omni-directional antenna | |
US20190058617A1 (en) | Antenna and Cabling Unification | |
US20140203974A1 (en) | Electronic device and antenna unit thereof | |
US20150226777A1 (en) | Antenna testing device and method | |
KR20210034270A (en) | Electronic device for determinig path of line of sight(los) and method for the same | |
US20130342408A1 (en) | Electronic device | |
JP2020115741A (en) | Methods of selectively activating antenna zones of a near-field charging pad to maximize wireless power delivered | |
US9478866B2 (en) | Orientation agnostic millimeter-wave radio link | |
JP2007082194A (en) | Data transfer system, wireless communication apparatus and wireless communication method, and computer program | |
US20230361448A1 (en) | Multimode high-isolation antenna system | |
TWI434457B (en) | Omnidirectional wideband antenna | |
CN112956134A (en) | Method and apparatus for performing beam search in mobile communication system | |
CN112350057A (en) | Electronic device with multi-band antenna | |
KR102636588B1 (en) | Wireless circuitry desensitization detection | |
US20190305812A1 (en) | Headset Wire Selection for Device Antenna | |
KR20180093601A (en) | Antenna apparatus | |
KR20200140030A (en) | Method for controlling a plurality of antenna modules and electronic device thereof | |
JP2013187722A (en) | Communication device, communication system, and communication program | |
CN108418592B (en) | Method for controlling radiation stray and related equipment | |
Srividya et al. | Digital Convergence in Antenna Design: Applications for Real-Time Solutions | |
Rodrigues et al. | Genetic algorithm optimization of a CPW fed UWB circular ring monopole with modified ground plane |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ALIPHCOM, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LUNA, MICHAEL EDWARD SMITH;PANG, HAWK YIN;SIGNING DATES FROM 20150413 TO 20150414;REEL/FRAME:035495/0221 |
|
AS | Assignment |
Owner name: BLACKROCK ADVISORS, LLC, NEW JERSEY Free format text: SECURITY INTEREST;ASSIGNORS:ALIPHCOM;MACGYVER ACQUISITION LLC;ALIPH, INC.;AND OTHERS;REEL/FRAME:035531/0312 Effective date: 20150428 |
|
AS | Assignment |
Owner name: BLACKROCK ADVISORS, LLC, NEW JERSEY Free format text: SECURITY INTEREST;ASSIGNORS:ALIPHCOM;MACGYVER ACQUISITION LLC;ALIPH, INC.;AND OTHERS;REEL/FRAME:036500/0173 Effective date: 20150826 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: BLACKROCK ADVISORS, LLC, NEW JERSEY Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE APPLICATION NO. 13870843 PREVIOUSLY RECORDED ON REEL 036500 FRAME 0173. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST;ASSIGNORS:ALIPHCOM;MACGYVER ACQUISITION, LLC;ALIPH, INC.;AND OTHERS;REEL/FRAME:041793/0347 Effective date: 20150826 |
|
AS | Assignment |
Owner name: JB IP ACQUISITION LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALIPHCOM, LLC;BODYMEDIA, INC.;REEL/FRAME:049805/0582 Effective date: 20180205 |
|
AS | Assignment |
Owner name: J FITNESS LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:JB IP ACQUISITION, LLC;REEL/FRAME:049825/0907 Effective date: 20180205 Owner name: J FITNESS LLC, NEW YORK Free format text: UCC FINANCING STATEMENT;ASSIGNOR:JB IP ACQUISITION, LLC;REEL/FRAME:049825/0718 Effective date: 20180205 Owner name: J FITNESS LLC, NEW YORK Free format text: UCC FINANCING STATEMENT;ASSIGNOR:JAWBONE HEALTH HUB, INC.;REEL/FRAME:049825/0659 Effective date: 20180205 |
|
AS | Assignment |
Owner name: ALIPHCOM LLC, NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BLACKROCK ADVISORS, LLC;REEL/FRAME:050005/0095 Effective date: 20190529 |
|
AS | Assignment |
Owner name: J FITNESS LLC, NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:JAWBONE HEALTH HUB, INC.;JB IP ACQUISITION, LLC;REEL/FRAME:050067/0286 Effective date: 20190808 |