Network Device Identification via mDNS and DHCP Hostname Assignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for identifying devices in computer networks are inadequate, particularly in automatically recognizing new devices and assigning user-friendly hostnames, especially with the increasing challenge of masked data due to privacy issues and changes in mobile operating systems.
Innovation Solution
The solution involves using network traffic data to identify devices through device fingerprinting, leveraging metadata from protocols like mDNS and DHCP, and assigning hostnames using multiple protocols, with a method that automatically configures hostnames and selects the appropriate hostname based on availability and logic rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If automated device identification methods are implemented, then device recognition accuracy is improved, but system complexity increases due to multiple protocol handling
Solution Approach 1:
The patent segments the device identification process into distinct protocol handlers (DHCP, mDNS, RARP) that operate independently. Each protocol handler extracts hostname information from its specific protocol packets, and the results are aggregated to form the final device identification. This modular segmentation reduces system complexity by making each component manageable and independently implementable.
Solution Approach 2:
The network apparatus is designed with multi-functionality to handle multiple protocols (DHCP, mDNS, RARP) simultaneously. A single device identification system performs the functions of what would otherwise require separate systems for each protocol, extracting hostnames from different protocol types and consolidating the results. This universality improves device recognition accuracy without proportionally increasing system complexity.
2Reliability
If multiple protocols are used for hostname assignment, then hostname availability is improved, but processing time increases
Solution Approach 1:
The system performs preliminary actions by monitoring and capturing protocol packets (DHCP, mDNS, RARP) as they naturally occur during device network initialization. Instead of waiting for a centralized identification process, the apparatus proactively extracts hostname information from these packets in real-time, making hostname assignment available immediately when the information becomes accessible through protocol exchange.
Solution Approach 2:
Devices essentially self-identify through their own protocol communications. The DHCP protocol provides hostname information during the standard DHCP handshake, mDNS allows devices to advertise their presence and names, and RARP enables automatic IP and hostname configuration. The network apparatus passively observes and extracts this self-provided information, minimizing processing overhead and time.
3Measurement precision
If device fingerprinting using network traffic metadata is implemented, then identification accuracy is improved, but data privacy concerns increase
Solution Approach 1:
The patent extracts only the necessary identification information (hostname, device type, manufacturer) from network traffic metadata through device fingerprinting. Rather than collecting or analyzing entire packet contents, the system selectively extracts specific fields from protocol packets that are already publicly transmitted during normal network operations. This extraction approach maintains identification accuracy while minimizing privacy intrusion by focusing only on voluntarily disclosed device information.
Data Source
AI summary
An apparatus in a computer network system extracts network traffic metadata related to a client computing device of a local network. The network traffic metadata is required by a device fingerprinting process. In response to detecting a multicast DNS (mDNS) packet query in the network traffic metadata, the apparatus collects an mDNS hostname related to the client computing device from the mDNS packet query. In response to determining, at a first point in time, that a dynamic host configuration protocol (DHCP) hostname related to the client computing device is unavailable in the network traffic metadata, the apparatus assigns the mDNS hostname to the client computing device.