Providing a communications channel between instances of automated assistants
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.
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.
2 . 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.
3 . 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.
4 . 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.
5 . 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.
6 . The method of claim 1 , wherein the first action includes providing a notification to a user of the first client device.
7 . 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.
8 . The method of claim 6 , wherein the first graphical element is a selectable element that, when selected, acknowledges the notification.
9 . 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.
10 . 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.
11 . 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.
12 . 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.
13 . 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.
14 . The method of claim 13 , wherein the third action intent request identifies a third requested action and an identifier of the automobile sensor application.
15 . The method of claim 12 , wherein the generated data further indicates a pendency of the third action intent request.
16 . The method of claim 12 , further comprising:
storing the third action intent request at the first client device or the second client device.
17 . 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.
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 the automobile computer system of the 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.
19 . 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.
20 . 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.