LAN Sync Candidate Discovery via IP Address Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing synchronized content management systems face challenges in efficiently synchronizing data across multiple client devices within a local area network (LAN) due to the reliance on central servers, which can lead to overburdened workloads, reduced stability, and increased costs, as well as issues with broadcast messages flooding the network and potential security concerns.
Innovation Solution
A system and method for identifying a synchronization candidate within a LAN by using public and local IP addresses, network characteristics, and subnet information to determine the best device for synchronization, allowing clients to initiate LAN sync without broadcasting and reducing the load on central servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a central server is used for data synchronization, then the implementation is straightforward and intuitive, but the central server becomes overburdened with excessive data processing and transfer workloads
Solution Approach 1:
The patent segments the centralized synchronization task into distributed peer-to-peer synchronization. Instead of one central server handling all data transfers, multiple client devices act as both clients and servers, dividing the workload across the network. This resolves the contradiction by maintaining ease of implementation through structured protocols while dramatically improving data processing efficiency through load distribution.
Solution Approach 2:
The patent merges the roles of client and server into a single entity. Each device can both request data (client function) and provide data (server function), combining previously separate functions. This allows the system to maintain simple implementation logic while achieving high productivity through parallel data operations across multiple devices.
2Device complexity
If a central server is used for data synchronization, then the system architecture is simple, but the system stability is compromised when the central server becomes unavailable
Solution Approach 1:
The patent segments the single point of failure (central server) into multiple distributed nodes. By distributing data storage and synchronization capabilities across multiple client devices, the system eliminates the critical dependency on a single server. This maintains relatively simple architecture through peer-to-peer protocols while dramatically improving reliability through redundancy.
Solution Approach 2:
The patent changes the system parameter from centralized to distributed architecture. This fundamental parameter change transforms the failure mode from single-point failure to distributed resilience, where the system can tolerate individual node failures. The architecture remains sufficiently simple through standardized peer-to-peer communication protocols.
3Ease of manufacture
If client devices synchronize through a central distributor via WAN, then the implementation is straightforward, but the communication cost increases and performance decreases
Solution Approach 1:
The patent removes the central server intermediary for LAN-based synchronization. Devices that were previously required to communicate through the central distributor can now communicate directly peer-to-peer within the local network. This eliminates the intermediary bottleneck, reducing communication costs and improving performance while maintaining implementation simplicity through established peer-to-peer protocols.
Solution Approach 2:
The patent adds a direct communication dimension to the existing centralized model. Instead of only allowing client-server communication through the WAN, the system enables a new direct peer-to-peer communication path within the LAN. This dimensional addition provides a faster, cheaper communication route while preserving the simpler centralized implementation for other scenarios.
4Ease of operation
If broadcast messages are used to discover shared files, then the implementation is simple, but the network becomes flooded with traffic and security concerns arise
Solution Approach 1:
The patent extracts the file sharing information from the broadcast message mechanism. Instead of broadcasting complete file lists that flood the network, the system uses targeted unicast requests where devices ask specifically for information they need. This removes the harmful flooding effect while preserving the simple operation of automatic file discovery through structured query-response protocols.
Solution Approach 2:
The patent implements a feedback-based discovery mechanism where devices send targeted requests and receive specific responses about shared files. This feedback loop replaces the broadcast-flood model with an efficient request-response pattern. The operation remains simple and automatic, but network traffic is minimized by only transmitting necessary information in response to specific queries.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, methods, and computer-readable storage media for identifying a LAN sync candidate are disclosed. A synchronized content management system may receive a request from a first client device to synchronize a content item. The synchronized content management system may identify a second client device that has a current copy of the content item. The second client device may belong in the same local area network as the first client device. The second client device can be identified based on a characteristic of the LAN as well as the public and local addresses of the first and second client devices. The synchronized content management system can send a LAN sync instruction to the first client device. The instruction may identify the second client device as a LAN sync candidate. The first client device may then initiate LAN sync by requesting synchronization of the content item from the second client device.