MFP DHCP Option Data Segmentation for Multi-Line Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multifunction peripherals (MFPs) with multiple communication interfaces face issues in communication settings due to different DHCP servers connected to different lines, leading to trouble in determining appropriate SMTP server address information when option data values are not unique across these servers.
Innovation Solution
The MFP employs an option-data requesting unit that distinguishes between required and non-unique option data types, only requesting unique data from each DHCP server, preventing unnecessary requests for non-unique data types across different lines.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the MFP requests all types of option data from each DHCP server connected to different lines, then complete communication setting information can be acquired, but trouble occurs when non-unique option data (such as SMTP server address) has different values from different DHCP servers
Solution Approach 1:
The patent segments the option data into two categories: unique option data (line-specific configuration) and non-unique option data (common configuration). This segmentation allows the MFP to selectively request only unique option data from each DHCP server, avoiding the conflict of receiving different values for non-unique data from multiple servers.
Solution Approach 2:
Instead of requesting all option data from every DHCP server, the patent applies partial action by requesting only the necessary unique option data from each server. This reduces the amount of data to be processed and eliminates the problem of conflicting non-unique option values while still achieving complete communication setting.
2Adaptability or versatility
If the MFP acquires option data from multiple DHCP servers, then comprehensive communication parameters are obtained, but the MFP cannot determine which value to use for non-unique option data
Solution Approach 1:
The patent segments the option data acquisition process into line-specific requests. Each DHCP server is requested only for its unique option data types, which are inherently appropriate for that specific line. This eliminates the need for complex determination logic while maintaining multi-line adaptability.
Solution Approach 2:
The patent applies local quality by making each DHCP server request tailored to the specific line's needs. Each server provides only the option data relevant to its line, ensuring that the data received is inherently appropriate for that local context without requiring global determination logic.
3Loss of information
If all option data types are requested from each DHCP server, then no data is missed, but unnecessary processing and potential conflicts occur for non-unique data types
Solution Approach 1:
The patent applies partial action by requesting only the necessary unique option data from each DHCP server rather than all option data types. This partial request strategy prevents receiving conflicting non-unique data while ensuring all necessary unique data is acquired, thus maintaining both completeness and reliability.
Solution Approach 2:
The patent extracts and separates the unique option data from the complete set of option data types. By identifying and requesting only the unique data types from each DHCP server, the system extracts the essential information needed for communication setting while eliminating sources of conflict.
Data Source
AI summary
An information processing apparatus capable of preventing trouble from occurring in communication setting due to respective different DHCP servers connected to lines. The information processing apparatus makes a request to the respective DHCP servers connected to a first line and a second line, for a plurality of types of option data required in communication setting of the information processing apparatus. The information processing apparatus makes no request to the DHCP server connected to either the first line or the second line, for a type of option data not required to have a unique value set for each of the first line and the second line, from the types of option data.