Prior art — US Patent 11119756

As a technical patent analyst, I have searched for US patent 11119756 and identified its prior art citations. The analysis below details each cited patent, its publication/filing date, a brief description, and which claims of US11119756 it potentially anticipates under 35 U.S.C. § 102.

The core innovative aspects of US11119756, as reflected in its independent claims (Claims 1, 14, 20), are:

A central computer system (e.g., switchboard server 110) receives state information from an update-receiving device (e.g., IoT device 120).
The central system determines readiness for update based on this state information.
The central system receives a separate indication to update from a different controlling device (e.g., first device 100).
After both the readiness determination and the update indication are received, the central system sends a "begin update" indication to the update-receiving device.
The update-receiving device initiates the update without any direct human interaction.

I will examine the cited prior art against these key features.

Prior Art Analysis for US Patent 11119756

1. US20040083471A1

Full Citation: US20040083471A1, Method of upgrading system software of a home appliance, LG Electronics Inc.
Publication/Filing Date: Priority date: 2002-10-21, Publication date: 2004-04-29.
Brief Description: This patent application describes a method for upgrading system software of a home appliance. It involves connecting a home appliance to a service server via a home gateway and the Internet, allowing the service server to download new software to the appliance and perform the upgrade. It mentions checking conditions before upgrading, such as whether a heating element is on.
Potential Anticipation:
- Claims 1, 14, 20 (Partially): This reference teaches a server-based remote update of a home appliance and checking conditions (state information) before the upgrade. However, it does not explicitly disclose a separate "another device" (first device 100 in US11119756) that sends an indication to update after the readiness determination, which is a key distinguishing feature of US11119756. The control flow originates from the service server and the appliance, not an intermediate user device. The "without any direct interaction" aspect is present for the final update execution from the server.

2. US20050039178A1

Full Citation: US20050039178A1, System and method for downloading update packages into a mobile handset in a carrier network, Sunil Marolia.
Publication/Filing Date: Priority date: 2003-06-27, Publication date: 2005-02-17.
Brief Description: This describes a system and method for downloading update packages to a mobile handset via a carrier network. It focuses on the secure and efficient delivery of software updates to mobile devices, possibly triggered by network events or user requests.
Potential Anticipation:
- None directly: While it deals with remote updates to a device (mobile handset), it lacks the specific multi-device control flow of US11119756 involving state information for readiness determination from the updated device, and an explicit indication to update from a separate user device mediated by a server.

3. US20070192462A1

Full Citation: US20070192462A1, System and method for managing applications of home network devices, [[Samsung Electronics Co.](/litigations/by-defendant/Samsung%20Electronics%20Co.), Ltd.](/litigations/by-plaintiff/Samsung%20Electronics%20Co.%2C%20Ltd.)
Publication/Filing Date: Priority date: 2006-02-15, Publication date: 2007-08-16.
Brief Description: This patent application describes managing applications on home network devices, including installing, updating, and removing applications. A management server can control the applications on home network devices.
Potential Anticipation:
- Claims 1, 14, 20 (Partially): This discloses remote management and updating of home network devices via a server. However, it doesn't clearly teach the specific sequence of receiving state information for readiness from the device, then receiving an update indication from a separate user device, followed by initiating an update without direct interaction. The management seems more direct from the server or through user interaction with the managed device.

4. US20080040713A1

Full Citation: US20080040713A1, Method for remotely upgrading the firmware of a target device using wireless technology, Stmicroelectronics Pvt. Ltd.
Publication/Filing Date: Priority date: 2004-05-31, Publication date: 2008-02-14.
Brief Description: This patent describes remotely upgrading firmware of a target device (e.g., embedded device) using wireless technology, where a host computer sends a firmware upgrade request to the target device via a transceiver.
Potential Anticipation:
- None directly: This focuses on the wireless remote upgrade mechanism itself. It does not teach the central server's role in determining readiness based on state information from the target device, nor the initiation by a separate user device in the manner of US11119756.

5. US20080301667A1

Full Citation: US20080301667A1, Dynamically Updating Software Applications on a Device, Google Inc.
Publication/Filing Date: Priority date: 2007-05-30, Publication date: 2008-12-04.
Brief Description: This describes dynamically updating software applications on a device, often in the context of mobile devices and applications that can update themselves. It also includes methods for a user to manage or choose when updates are applied.
Potential Anticipation:
- None directly: While it discusses user control over updates, it doesn't outline the specific three-device (first device, server, second device) interaction model for state-based readiness determination and remote, non-direct interaction update initiation as found in US11119756.

6. US20090271507A1

Full Citation: US20090271507A1, System and method for assisted administration of remote device updates, Kodimer Marianne L.
Publication/Filing Date: Priority date: 2008-04-24, Publication date: 2009-10-29.
Brief Description: This patent describes a system for administering remote device updates where an administrator or user can manage updates for various devices through a central system. It can involve scheduling updates and receiving feedback.
Potential Anticipation:
- Claims 1, 14, 20 (Partially): This reference broadly covers remote update administration. It could be seen as having a "central system" (server) and "another device" (administrator's device). However, it lacks the explicit teaching of the "state information" from the updated device being used by the central system to determine readiness before the update is permitted, and the specific "without any direct interaction" clause tied to the final trigger from the server to the updated device.

7. US20090300595A1

Full Citation: US20090300595A1, System and Method for Remotely Updating Control Software in a Vehicle With an Electric Drive System, Ise Corporation.
Publication/Filing Date: Priority date: 2008-05-30, Publication date: 2009-12-03.
Brief Description: This patent describes remotely updating software in a vehicle, specifically an electric drive system. It involves a service center sending update information to a vehicle, and the vehicle performing the update. It mentions checking if the vehicle is in a "stoppable" state for the update.
Potential Anticipation:
- Claims 1, 14, 20 (Partially): This is highly relevant as it describes remote updates for a vehicle (an IoT device type), involves a "service center" (analogous to the switchboard server), and checks for a "stoppable state" (state information for readiness). However, similar to US20040083471A1, it primarily describes a direct interaction between the service center and the vehicle. It doesn't explicitly introduce a third party user device (first device 100) that initiates the update after readiness is determined by the server, as a distinct step. The "without any direct interaction" for the final update execution from the service center is implied. This is a strong candidate for anticipating some aspects but likely not the full claim combination of US11119756.

8. US20100082559A1

Full Citation: US20100082559A1, Method of managing a schedule-based software package update, General Motors Corporation.
Publication/Filing Date: Priority date: 2008-09-19, Publication date: 2010-04-01.
Brief Description: This relates to managing software updates based on a schedule, particularly for vehicle systems. It can involve a central server pushing updates to vehicles according to predefined schedules.
Potential Anticipation:
- None directly: This focuses on scheduled updates. It doesn't detail the dynamic state information exchange, readiness determination by a server, and user-initiated remote update via a separate device in the manner of US11119756.

9. US7831967B2

Full Citation: US7831967B2, Method of and apparatus for updating software of network device, Samsung Electronics Co., Ltd.
Publication/Filing Date: Priority date: 2004-08-06, Publication date: 2010-11-09.
Brief Description: This patent describes a method and apparatus for updating software of a network device by transmitting update files from a server to the device. It includes steps for checking the version of the software and performing the update.
Potential Anticipation:
- None directly: While it covers remote updates, it lacks the nuanced interaction with state information for readiness determination by a central server and a user-driven initiation from a separate device, which are central to US11119756.

10. US8561054B2

Full Citation: US8561054B2, Method for updating software components, Bayerische Motoren Werke Aktiengesellschaft.
Publication/Filing Date: Priority date: 2009-04-27, Publication date: 2013-10-15.
Brief Description: This patent describes a method for updating software components, particularly in a vehicle. It involves a central control unit receiving update data and distributing it to other control units in the vehicle. It focuses on the internal update process within a complex system.
Potential Anticipation:
- None directly: This focuses on internal software distribution within a vehicle. It does not address the remote control interaction from an external user device and a server to initiate updates based on state information.

11. US20130311611A1

Full Citation: US20130311611A1, Method and device for executing a device management command based on an execution time, LG Electronics Inc.
Publication/Filing Date: Priority date: 2011-12-12, Publication date: 2013-11-21.
Brief Description: This patent describes a method for a server to send a device management command (e.g., software update) to a device, where the command is executed at a specific "execution time." This execution time can be determined based on device usage patterns or other criteria.
Potential Anticipation:
- Claims 1, 14, 20 (Partially): This reference teaches a server sending a command (like an update) and considering device state/usage to determine an execution time. This is close to the "determine readiness based on state information" (element b of Claim 1). It also implies the update occurs "without direct interaction" at the device once the command is received. However, it still lacks the explicit "another device" (first device 100) providing a distinct "indication to update" (element c of Claim 1) after the readiness determination, which is a specific control flow aspect of US11119756.

12. US8997092B2

Full Citation: US8997092B2, Method, system, and computer readable medium for provisioning and remote distribution, Symantec Corporation.
Publication/Filing Date: Priority date: 2010-02-03, Publication date: 2015-03-31.
Brief Description: This patent focuses on remote provisioning and distribution of software or configurations to managed devices. It describes a server pushing updates to client devices.
Potential Anticipation:
- None directly: Similar to other remote update patents, it lacks the specific tripartite interaction (first device, server, second device) and the detailed state-based readiness determination and remote, non-interactive update trigger flow of US11119756.

13. US20160277195A1

Full Citation: US20160277195A1, Method of authenticating devices using certificates, Panasonic Intellectual Property Management Co., Ltd.
Publication/Filing Date: Priority date: 2013-12-16, Publication date: 2016-09-22.
Brief Description: This patent describes methods for authenticating devices using certificates, which is a security aspect relevant to device communication but not directly to the update control logic.
Potential Anticipation:
- None directly: This reference is tangential, focusing on device authentication rather than the method of update control itself.

14. US20160294614A1

Full Citation: US20160294614A1, Remote Embedded Device Update Platform Apparatuses, Methods and Systems, Symphony Teleca Corporation.
Publication/Filing Date: Priority date: 2014-07-07, Publication date: 2016-10-06.
Brief Description: This patent describes a remote embedded device update platform that allows a backend server to manage updates for embedded devices. It mentions using device telemetry (state information) to assess device health and readiness for updates.
Potential Anticipation:
- Claims 1, 14, 20 (Strong Candidate): This reference is a very strong candidate for anticipating many aspects of US11119756. It explicitly mentions a backend server managing updates, and critically, using device telemetry (state information) to assess readiness for updates. This covers elements (a) and (b) of Claim 1. The remote nature of the update implies "without any direct interaction" (element d). The main missing element for full anticipation of US11119756's independent claims would be the explicit and distinct step where a separate "another device" (first device 100) sends the final indication to update after the server has determined readiness. If the "platform" allows a user or administrator to trigger the update from a remote interface after readiness is assessed by the server, it would be extremely close to fully anticipating.

15. US20170300313A1

Full Citation: US20170300313A1, Method and system for downloading and installing a remote software update on a vehicle, GM Global Technology Operations LLC.
Publication/Filing Date: Priority date: 2016-04-14, Publication date: 2017-10-19.
Brief Description: This describes a method for remote software updates on a vehicle, where an update server downloads and installs updates. It may involve checking vehicle status (e.g., parked, ignition off) before commencing the update.
Potential Anticipation:
- Claims 1, 14, 20 (Strong Candidate): Similar to US20090300595A1 and US20160294614A1, this is highly relevant, focusing on vehicles (a key IoT device example in US11119756). It clearly teaches a remote server providing updates and checking "vehicle status" (state information) for readiness before installing the update. This covers elements (a) and (b) of Claim 1, and the "without any direct interaction" is inherent. Again, the primary distinction from US11119756's broadest claims would be the explicit presence of a separate "another device" (first device 100) providing a distinct "indication to update" after the server's readiness determination. If the system allows a user to initiate the update remotely from, for example, a mobile app after the server indicates the vehicle is ready, it would very closely anticipate the independent claims of US11119756.

Summary of Most Relevant Prior Art:

Based on the analysis, US20160294614A1 (Remote Embedded Device Update Platform) and US20170300313A1 (Remote Software Update on a Vehicle) appear to be the most relevant prior art. Both explicitly teach the use of a central server (or "platform" / "update server") that receives state information (telemetry / vehicle status) from a device (embedded device / vehicle) and determines readiness for an update based on this information. The updates are performed remotely, implying "without direct interaction."

The distinguishing feature of US11119756's independent claims (1, 14, 20) that these references might not fully anticipate is the precise control flow involving a third, distinct user device (the "first device" or "another device" in US11119756) that sends an explicit indication to update to the central server after the central server has determined the updated device is ready. While these prior arts might imply a user initiating the update through some interface, the explicit architectural split and the specific sequencing of these "indications" via a server acting as a switchboard for a remote user device and the IoT device is what US11119756 emphasizes. However, the differences may be subtle in a § 102 analysis, especially if the prior art documents imply such user interaction from a remote interface.