Firmware Barrier Mechanism for Thin-Client Network Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Thin-client devices face challenges in automatically connecting and configuring themselves on enterprise networks without dedicated DHCP servers, and in safely updating firmware to prevent loss of enterprise network functionality.
Innovation Solution
Implementing a method where thin-client devices broadcast DHCPDiscover and DHCPInform messages to receive network and thin-client parameters, and setting a barrier level to prevent firmware downgrades below a minimum version necessary for enterprise network functionality, ensuring seamless integration and secure updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If thin-client devices automatically update firmware to the latest version, then firmware security and functionality are improved, but the risk of downgrading to incompatible versions increases
Solution Approach 1:
The patent applies preliminary anti-action by implementing a barrier level mechanism that prevents firmware downgrades before they can occur. The system proactively blocks update processes that would result in downgrading to versions below the barrier level, thereby preventing compatibility issues before they arise. This is achieved by comparing the proposed firmware version against the barrier level and rejecting updates that would result in a downgrade.
Solution Approach 2:
The patent utilizes parameter changes by introducing a configurable barrier level parameter that defines the minimum acceptable firmware version. This parameter can be dynamically adjusted based on network requirements and can be set through DHCP options or local configuration. The system changes the firmware update behavior based on this parameter, allowing flexible control over which firmware versions are acceptable.
2Reliability
If thin-client devices use dedicated networks for communication, then network security and performance are improved, but deployment complexity and cost increase
Solution Approach 1:
The patent applies universality by enabling thin-client devices to operate on standard enterprise networks rather than requiring dedicated networks. The devices use standard DHCP protocols and network infrastructure while maintaining thin-client functionality. This allows the same hardware and software to function in both dedicated and standard network environments, eliminating the need for separate dedicated network infrastructure.
Solution Approach 2:
The patent uses an intermediary approach by leveraging existing DHCP servers and network infrastructure as intermediaries to provide thin-client services. Instead of requiring direct dedicated network connections, the system uses standard network protocols and existing server infrastructure to mediate communication between thin-client devices and enterprise resources, thereby reducing deployment complexity.
3Ease of operation
If thin-client devices broadcast DHCP messages to discover networks, then automatic configuration capability is improved, but susceptibility to malicious or incorrect DHCP responses increases
Solution Approach 1:
The patent applies feedback by implementing verification mechanisms that provide feedback about the reliability and security of DHCP responses. The system receives DHCP offers, verifies them against criteria (such as checking for valid options and acceptable firmware versions), and only accepts responses that pass verification. This feedback loop prevents acceptance of malicious or incorrect DHCP responses while maintaining automatic configuration capability.
Data Source
AI summary
A thin-client device having an application program obtains a copy of an application update having an update barrier level via a network. The thin-client device receives a set of configuration parameters from a configuration server via the network and sets the barrier level value to a value specified by the set of configuration parameters. Alternatively, the thin-client device retrieves a default barrier level value stored in the thin-client device. If the set of configuration parameters does not specify a barrier level value, the barrier level value is set to the default barrier level value. The thin-client device compares the update barrier level to a barrier level value corresponding to a minimum application version necessary to maintain support for a critical feature. If the update barrier level is greater than or equal to the barrier level value, the thin-client device updates its application program.