# US 2026/0281619 A1 · Systems and methods for audio sharing

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0281619 A1
- Document ID: US20260281619A1
- Status: Published application
- Kind: A1
- Application number: 19/669,104
- Filed: 2026-05-06
- Published: 2026-09-17
- Earliest claimed: 2024-03-29
- Assignees: Adeia Guides Inc.
- Applicants: Adeia Guides Inc.
- Inventors: Jean-Yves Couleaud; Charles Dasher; Reda Harb
- Web page: https://patentgrep.com/patent/US20260281619A1

## CPC

- H04R 1/1041: {Mechanical or electronic switches, or control elements (switches in general H01H)}
- H04R 5/033: Headphones for stereophonic communication {(details thereof, e.g. relating to batteries, cables or control elements H04R1/10)}
- H04R 1/10: Earpieces; Attachments therefor {; Earphones; Monophonic headphones (H04R1/28 takes precedence; stereophonic headphones H04R5/033)}
- H04R 3/12: for distributing signals to two or more loudspeakers {(specially adapted for hearing aids H04R25/407)}
- H04R 3/14: Cross-over networks
- H04R 2420/07: Applications of wireless loudspeakers or wireless microphones
- H04R: LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; ELECTRIC HEARING AIDS; PUBLIC ADDRESS SYSTEMS (producing sounds with frequency not determined by supply frequency G10K)

## Abstract

Systems and methods are provided for enabling audio sharing. Inertial data is monitored at a first headset, and a tap input is detected, based on the inertial data, by detecting a movement of the headset in a first direction and a subsequent deceleration above a threshold. It is detected, at the first headset, that it is within a threshold proximity to a second headset, or a computing device associated with the second headset. It is determined, based on a predetermined factor, that the first headset is to receive audio associated with the second headset, and pairing information is transmitted to the first headset. Authorization to pair the first headset to the computing device is requested and received at the second headset. The first headset is paired to the computing device using the pairing information, and the first headset and the second headset receive the same audio from the computing device.

## Claims

### Claim 1

A method performed by a first headset, the method comprising:
receiving audio of a media asset from a device;
outputting the audio of the media asset received from the device;
receiving a connect request from a second headset;
determining that the second headset is within a threshold physical proximity to the first headset; and
based at least in part on (a) the connect request from the second headset and (b) the second headset being within the threshold physical proximity to the first headset, transmitting pairing information to the second headset to communicatively couple the second headset to the device, wherein when the second headset is communicatively coupled to the device based on the pairing information, the second headset is configured to output the audio of the media asset from the device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining that the first headset is moving in a first direction; and
determining, after the first headset is moving the first direction, that deceleration of the first headset exceeds a threshold, wherein the connect request is based at least in part on the deceleration.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving an indication from the device to continue outputting the audio; and
outputting the audio of the media asset starting at a given timepoint of the audio, wherein when the second headset outputs the audio of the media asset, the second headset outputs the audio of the media asset starting at the given timepoint used by the first headset.

### Claim 4 (depends on 1)

The method of claim 1, further comprising transmitting, to the second headset, authorization information indicating a duration for how long the second headset is to be communicatively coupled to the device, wherein the second headset is configured to cease being communicatively coupled to the device based on the duration.

### Claim 5 (depends on 1)

The method of claim 1, further comprising outputting a chime indicating that the pairing information was transmitted to the second headset.

### Claim 6 (depends on 1)

The method of claim 1, further comprising displaying a visual indicator indicating that the second headset is communicatively coupled to the device, wherein the second headset is configured to display the visual indicator based on being communicatively coupled to the device.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
determining a first account associated with the first headset; and
determining that the second headset is associated with a second account, wherein transmitting the pairing information is further based at least in part on (c) determining that the second account is comprised in an acceptable list of accounts to transmit the pairing information to.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
determining that the audio of the media asset is received from the device while the device is operating an audio sharing application; and
determining that the audio sharing application is comprised in a list of acceptable audio sharing applications, wherein transmitting the pairing information is further based at least in part on (c) determining that the audio sharing application is comprised in the list of acceptable audio sharing applications.

### Claim 9 (depends on 1)

The method of claim 1, wherein transmitting the pairing information comprises transmitting the pairing information over a near field communication (NFC) link.

### Claim 10 (depends on 1)

The method of claim 1, further comprising based on at least one of (a) not receiving the connect request or (b) the second headset not being within the threshold physical proximity to the first headset, monitoring inertial data of the first headset for a tap event.

### Claim 11

A system comprising a first headset, the first headset comprising:
input/output (I/O) circuitry configured to:
receive audio of a media asset from a device;
output the audio of the media asset received from the device; and
receive a connect request from a second headset; and
control circuitry configured to determine that the second headset is within a threshold physical proximity to the first headset; wherein:
the I/O circuitry is further configured to, based at least in part on (a) the connect request from the second headset and (b) the second headset being within the threshold physical proximity to the first headset, transmit pairing information to the second headset to communicatively couple the second headset to the device, wherein when the second headset is communicatively coupled to the device based on the pairing information, the second headset is configured to output the audio of the media asset from the device.

### Claim 12 (depends on 11)

The system of claim 11, wherein the control circuitry is further configured to:
determine that the first headset is moving in a first direction; and
determine, after the first headset is moving the first direction, that deceleration of the first headset exceeds a threshold, wherein the connect request is based at least in part on the deceleration.

### Claim 13 (depends on 11)

The system of claim 11, wherein the I/O circuitry is further configured to:
receive an indication from the device to continue outputting the audio; and
output the audio of the media asset starting at a given timepoint of the audio, wherein when the second headset outputs the audio of the media asset, the second headset outputs the audio of the media asset starting at the given timepoint used by the first headset.

### Claim 14 (depends on 11)

The system of claim 11, wherein the I/O circuitry is further configured to transmit, to the second headset, authorization information indicating a duration for how long the second headset is to be communicatively coupled to the device, wherein the second headset is configured to cease being communicatively coupled to the device based on the duration.

### Claim 15 (depends on 11)

The system of claim 11, wherein the I/O circuitry is further configured to output a chime indicating that the pairing information was transmitted to the second headset.

### Claim 16 (depends on 11)

The system of claim 11, wherein the I/O circuitry is further configured to display a visual indicator indicating that the second headset is communicatively coupled to the device, wherein the second headset is configured to display the visual indicator based on being communicatively coupled to the device.

### Claim 17 (depends on 11)

The system of claim 11, wherein the control circuitry is further configured to:
determine a first account associated with the first headset; and
determine that the second headset is associated with a second account, wherein transmitting the pairing information is further based at least in part on (c) determining that the second account is comprised in an acceptable list of accounts to transmit the pairing information to.

### Claim 18 (depends on 11)

The system of claim 11, wherein the control circuitry is further configured to:
determine that the audio of the media asset is received from the device while the device is operating an audio sharing application; and
determine that the audio sharing application is comprised in a list of acceptable audio sharing applications, wherein transmitting the pairing information is further based at least in part on (c) determining that the audio sharing application is comprised in the list of acceptable audio sharing applications.

### Claim 19 (depends on 11)

The system of claim 11, wherein the I/O circuitry, when transmitting the pairing information, is configured to transmit the pairing information over a near field communication (NFC) link.

### Claim 20 (depends on 11)

The system of claim 11, wherein the control circuitry is further configured to, based on at least one of (a) not receiving the connect request or (b) the second headset not being within the threshold physical proximity to the first headset, monitor inertial data of the first headset for a tap event.
