# US 2023/0410565 A1 · Providing a communications channel between instances of automated assistants

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

- Number: US 2023/0410565 A1
- Document ID: US20230410565A1
- Status: Published application
- Kind: A1
- Application number: 18/228,439
- Filed: 2023-07-31
- Published: 2023-12-21
- Earliest claimed: 2018-05-23
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Alexandr Maltsev; Vikram Aggarwal; Moises Morgenstern Gali; Joseph Pirozzo
- Web page: https://patentgrep.com/patent/US20230410565A1

## CPC

- G06F 9/54: Interprogram communication
- G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)}
- B60K 35/10: Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
- B60K 35/22: Display screens
- B60K 35/28: characterised by the type of the output information, e.g. video entertainment or vehicle dynamics information; characterised by the purpose of the output information, e.g. for attracting the attention of the driver
- B60K 35/29: Instruments characterised by the way in which information is handled, e.g. showing information on plural displays or prioritising information according to driving conditions
- B60K 35/80: Arrangements for controlling instruments
- B60K 35/85: Arrangements for transferring vehicle- or driver-related data
- G06F 3/00: Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F 3/0482: Interaction with lists of selectable items, e.g. menus
- G06F 3/04842: Selection of displayed objects or displayed text elements (G06F3/0482 takes precedence)
- G06F 3/167: {Audio in a user interface, e.g. using voice commands for navigating, audio feedback}
- G07C 5/006: {Indicating maintenance}
- G07C 5/0825: {using optical means}
- G10L 15/26: Speech to text systems (G10L15/08 takes precedence)
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/52: specially adapted for the location of the user terminal
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- B60K 2360/182: Distributing information between displays
- B60K 2360/563: Vehicle displaying mobile device information
- B60K 2360/566: Mobile devices displaying vehicle information
- B60K 2360/569: Vehicle controlling mobile device functions
- B60K 2360/573: Mobile devices controlling vehicle functions
- B60K 2360/589: Wireless data transfers
- G06F 3/03547: {Touch pads, in which fingers can move on a surface}
- G06F 3/0488: using a touch-screen or digitiser, e.g. input of commands through traced gestures
- H04M 1/724098: {Interfacing with an on-board device of a vehicle (for hands-free speaking in vehicles H04M1/6075)}
- H04M 1/72415: for remote control of appliances
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- B60K: ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
- G10L: SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

Implementations relate to interactions, over a wireless communication modality, between an automated assistant of an automobile computer system, and separate client device(s). In some of those implementations, the client device(s) can be paired with the automobile computer system, and the client device(s) and the automobile computer system can include separate instances of an automated assistant, which can be associated with different user accounts. In some additional or alternative implementations, particular actions to be performed by a local application of a client device can be advanced via user interaction with the automobile automated assistant, despite a counterpart to the local application not being installed directly on automobile computer system. For example, despite an automobile computer system not having a third-party messaging application installed, the automobile automated assistant can access requested actions to be performed by the third-party messaging application in order to further a requested action. The automobile computer system can transmit, via the wireless communication modality, content to cause the third-party application to further the requested action.

## Claims

### Claim 1

A computer-implemented method, comprising:
performing, by an automobile computer system of a vehicle, a first handshake with a first client device, to establish a first communication channel between the automobile computer system of the vehicle and the first client device,
wherein a first application is installed at the first client device but not installed at the automobile computer system of the vehicle;
performing, by the automobile computer system of a vehicle, a second handshake with a second client device, to establish a second communication channel between the automobile computer system of the vehicle and the second client device,
wherein a second application is installed at the second client device but not installed at the automobile computer system of the vehicle;
identifying, by the automobile computer system of the vehicle, a plurality of pending action intent requests, wherein the plurality of pending action intent requests include a first pending action intent request received from the first client device and a second pending action intent request received from the second client device,
wherein the first pending action intent request identifies a first action to be performed, a first identifier associated with the first application that is installed at the first client device, and first content data associated with the first action to be performed, and
wherein the second pending action intent request identifies a second action to be performed, a second identifier associated with the second application that is installed at the second client device, and second content data associated with the second action to be performed;
generating, at the automobile computer system of the vehicle, data indicating a pendency of the first pending action intent request and the second pending action intent request; and
causing, based on the generated data, one or more graphical elements to be rendered via the automobile computer system of the vehicle, wherein the one or more graphical elements include a first graphical element and/or a second graphical element, the first graphical element corresponding to the first pending action intent request, and the second graphical element corresponding to the second pending action intent request.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data indicating the pendency of the first pending action intent request and the second pending action intent request further indicates a priority of the first pending action intent request relative to the second pending action intent request.

### Claim 3 (depends on 2)

The method of claim 2, wherein the priority of the first pending action intent request relative to the second pending action intent request is determined based on the first identifier associated with the first application that is installed at the first client device and the second identifier associated with the second application that is installed at the second client device.

### Claim 4 (depends on 2)

The method of claim 2, wherein the first client device is associated with a driver of the vehicle, the second client device is associated with a passenger of the vehicle, and the priority reflects that the first pending action intent request is more prioritized relative to the priority of the second pending action intent request.

### Claim 5 (depends on 2)

The method of claim 2, wherein the priority of the first pending action intent request relative to the second pending action intent request is determined based on whether the first or second client device includes a primary automated assistant that communicates with more than one other automated assistant.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first action includes providing a notification to a user of the first client device.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first graphical element presents the notification to the user of the first client device via a display panel of the automobile computer system of the vehicle.

### Claim 8 (depends on 6)

The method of claim 6, wherein the first graphical element is a selectable element that, when selected, acknowledges the notification.

### Claim 9 (depends on 8)

The method of claim 8, wherein the second action includes providing a notification to a user of the second client device, and wherein the first graphical element, when selected, causes the second graphical element to be rendered at the display panel of the automobile computer system of the vehicle.

### Claim 10 (depends on 8)

The method of claim 8, wherein when the first graphical element is selected, the notification is acknowledged by dismissing the pendency of the first pending action intent request.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first handshake with the first client device is performed in response to a first user of the first client device entering the vehicle, and/or the second handshake with the second client device is performed in response to a second user of the second client device entering the vehicle.

### Claim 12 (depends on 1)

The method of claim 1, wherein the plurality of pending action intent requests further include a third action intent request received from the automobile computer system of the vehicle.

### Claim 13 (depends on 12)

The method of claim 12, wherein the third action intent request is generated by an automobile sensor application, based on sensor data from a sensor of the automobile computer system of the vehicle.

### Claim 14 (depends on 13)

The method of claim 13, wherein the third action intent request identifies a third requested action and an identifier of the automobile sensor application.

### Claim 15 (depends on 12)

The method of claim 12, wherein the generated data further indicates a pendency of the third action intent request.

### Claim 16 (depends on 12)

The method of claim 12, further comprising:
storing the third action intent request at the first client device or the second client device.

### Claim 17 (depends on 12)

The method of claim 12, wherein the data further indicates a priority of the third action intent request relative to the first pending action intent request and/or the second pending action intent request.

### Claim 18

A system comprising one or more processors, and memory configured to store instructions that, when executed by one or more processors, cause the one or more processors to perform operations that include:
performing, by an automobile computer system of a vehicle, a first handshake with a first client device, to establish a first communication channel between the automobile computer system of the vehicle and the first client device,
wherein a first application is installed at the first client device but not installed at the automobile computer system of the vehicle;
performing, by an automobile computer system of a vehicle, a second handshake with a second client device, to establish a second communication channel between the automobile computer system of the vehicle and the second client device,
wherein a second application is installed at the second client device but not installed at the automobile computer system of the vehicle;
identifying, by the automobile computer system of the vehicle, a plurality of pending action intent requests, wherein the plurality of pending action intent requests include a first pending action intent request received from the first client device and a second pending action intent request received from the second client device,
wherein the first pending action intent request identifies a first action to be performed, a first identifier associated with the first application that is installed at the first client device, and first content data associated with the first action to be performed, and
wherein the second pending action intent request identifies a second action to be performed, a second identifier associated with the second application that is installed at the second client device, and second content data associated with the second action to be performed;
generating, at the automobile computer system of the vehicle, data indicating a pendency of the first pending action intent request and the second pending action intent request; and
causing, based on the generated data, one or more graphical elements to be rendered via the automobile computer system of the vehicle, wherein the one or more graphical elements include a first graphical element and/or a second graphical element, the first graphical element corresponding to the first pending action intent request, and the second graphical element corresponding to the second pending action intent request.

### Claim 19 (depends on 18)

The system of claim 18, wherein the data indicating the pendency of the first pending action intent request and the second pending action intent request further indicates a priority of the first pending action intent request relative to the second pending action intent request.

### Claim 20 (depends on 19)

The system of claim 19, wherein the first client device is associated with a driver of the vehicle, the second client device is associated with a passenger of the vehicle, and the priority reflects that the first pending action intent request is more prioritized relative to the priority of the second pending action intent request.
