US 11,943,075 B2
Adapting to differences in device state reporting of third party servers
Yuzhao Ni, Sunnyvale, CA (US)
Assigned to GOOGLE LLC, Mountain View, CA (US)
Filed by Google LLC, Mountain View, CA (US)
Filed on Dec. 6, 2021, as Appl. No. 17/543,069.
Application 17/543,069 is a continuation of application No. 16/343,927, granted, now 11,196,582, previously published as PCT/US2019/017335, filed on Feb. 8, 2019.
Prior Publication US 2022/0094564 A1, Mar. 24, 2022
Int. Cl. H04L 12/28 (2006.01); G10L 15/22 (2006.01); G10L 15/30 (2013.01)
CPC H04L 12/283 (2013.01) [G10L 15/22 (2013.01); G10L 15/30 (2013.01); H04L 12/282 (2013.01); G10L 2015/223 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A method implemented by one or more processors, the method comprising:
causing a client device to render content that characterizes a first status of another client device, wherein the client device and the other client device are connected to a common local area network, and the other client device is controlled using at least an automated assistant that is accessible via the client device;
determining, subsequent to causing the client device to render the content, that the client device has received a command for causing the other client device to operate according to a second status;
providing, in response to determining that the client device has received the command to cause the other client device to operate according to the second status, a request to a third party server device to cause the other client device to operate according to the second status;
receiving, subsequent to the request transmitted to the third party server device, status data from the third party server device, wherein the status data characterizes an operational status of the other client device;
when the status data indicates that the client device is operating according to the second status:
modifying, or bypassing modifying, one or more metrics, wherein the one or more metrics indicate the reliability of the third party server device to provide accurate status data, to characterize the third party server device as being reliable with respect to providing accurate status data, at least in response to the third party server device causing the other client device to exhibit any modified status relative to any previous status of the other client device;
when the status data indicates that the client device is not operating according to the second status:
modifying, or generating, the one or more metrics to indicate that the third party server device is unreliable with respect to providing the accurate status data, at least in response to the third party server device causing the other client device to exhibit any modified status relative to any previous status of the other client device.