NDIS Driver Layer Network Configuration Acquisition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for acquiring network configuration information, such as DHCP clients, are not effective when a terminal device lacks a DHCP client function, hindering its ability to establish successful data services connections.
Innovation Solution
The method involves using a Network Driver Interface Standard (NDIS) driver layer to deliver a Query Network Configuration Information message to a wireless modem, acquiring and providing IP address and gateway information to the terminal device's application layer, enabling dial-up services without relying on a DHCP client.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a terminal device uses traditional DHCP client methods to acquire network configuration information, then the acquisition process is automated and efficient, but the method fails when the terminal device lacks DHCP client functionality
Solution Approach 1:
The patent introduces an NDIS driver layer as an intermediary between the application layer and the physical network interface. This driver layer acts as a mediator that can acquire network configuration information through alternative methods (direct modem commands) when DHCP client is unavailable, thereby resolving the contradiction between reliability and adaptability across different device configurations
Solution Approach 2:
The patent changes the operational parameters of the network stack by implementing configuration acquisition at the driver layer rather than relying on the application layer DHCP client. By modifying how network parameters are obtained (through NDIS port and modem commands instead of DHCP protocol), the system achieves compatibility with devices lacking DHCP client functionality
2Extent of automation
If network configuration information is acquired through DHCP protocol, then the process is standardized and automated, but it increases system complexity and requires additional protocol implementation
Solution Approach 1:
The patent extracts the network configuration acquisition function from the traditional DHCP client implementation and relocates it to the NDIS driver layer. By separating this function from the application layer DHCP protocol dependency, the system maintains automated configuration acquisition while reducing the complexity requirements for protocol implementation in the terminal device
3Device complexity
If manual static configuration is used for network settings, then no additional protocols are needed, but the process is time-consuming and error-prone
Solution Approach 1:
The patent implements preliminary action by having the NDIS driver layer automatically acquire network configuration information through modem commands immediately during the dial-up process. This automated preliminary configuration eliminates the need for manual static setup while maintaining simplicity, thereby reducing both configuration time and error rates
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A method and an apparatus for acquiring network configuration information are disclosed. The method includes: when a terminal device dials up and needs to carry out network data services, delivering, by a Network Driver Interface Standard NDIS driver layer of the terminal device, a Query Network Configuration Information message to a wireless modem; and acquiring, by the NDIS driver layer, the network configuration information returned from the wireless modem, and providing an application layer of the terminal device with the acquired network configuration information. In this way, when the terminal device does not provide the function of a DHCP client, the terminal device can effectively acquire needed network configuration information to implement dial-up successfully, and can carry out network data services online, so as to ensure that normal services can be carried out on the terminal device.