Client Device Subnet Management via Reserved Configuration List

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data communications networks, subnet conflicts occur when two or more subnets are configured with overlapping IP addresses, leading to data intended for one IP address being routed to multiple client devices, causing network address conflicts.

Innovation Solution

A client device in the network obtains a list of reserved subnet configurations from an external server and allows network devices to be configured with either reserved or non-reserved subnet configurations to prevent conflicts, ensuring unique IP addresses are assigned to each device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If network devices are configured with subnet configurations independently without centralized coordination, then device autonomy and ease of configuration is improved, but subnet conflicts occur when multiple subnets use overlapping IP addresses

Engineering Contradiction:
Improveease of configurationVSAvoidnetwork integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

An external server acts as an intermediary between network devices and the subnet configuration process. The server stores a centralized list of reserved subnet configurations and provides this information to client devices, which then use it to configure network devices. This mediator approach allows distributed configuration while preventing conflicts through centralized coordination of the reserved list.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary action by pre-populating a reserved subnet configuration list on the external server before network devices are configured. This list contains subnet configurations that should not be used, and it is made available to client devices in advance, allowing them to avoid conflicts before they occur during the configuration process.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a centralized list of reserved subnet configurations is implemented, then subnet conflict prevention is improved, but system complexity and coordination requirements increase

Engineering Contradiction:
Improvesubnet conflict preventionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The external server serves as a simplified intermediary that handles the complexity of maintaining the reserved subnet configuration list centrally. Individual client devices and network devices remain simple, as they only need to query and use the provided list, respectively. This distributes complexity appropriately rather than making all components complex.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Client devices automatically retrieve the reserved subnet configuration list from the external server and use it to configure network devices without manual intervention. The system serves itself by having devices autonomously obtain configuration information and apply it, reducing the need for complex manual coordination or centralized configuration management.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If client devices automatically obtain and apply subnet configurations from an external server, then configuration accuracy and conflict avoidance are improved, but network dependency and loss of local control increase

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidlocal control
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The external server performs preliminary action by preparing and storing the reserved subnet configuration list in advance. Client devices then simply retrieve this pre-prepared information, ensuring configuration accuracy without requiring complex real-time analysis or decision-making at the client level. The heavy lifting of conflict identification is done beforehand.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of having the external server directly configure network devices (which would centralize control), the system inverts the approach: the server provides information, and client devices perform the configuration themselves. This maintains local control while still achieving centralized coordination for conflict prevention.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS11831515B2Client device based home subnet management
Publication Date: 2023.11.28 ARRIS ENTERPRISES LLC
  • US11831515B2 patent drawing
  • US11831515B2 patent drawing
  • US11831515B2 patent drawing

AI summary

A system and method are provided for a client device for use with a first Wi-Fi network device, a second Wi-Fi network device, and an external server. The first Wi-Fi network device is configured with a first subnet configuration and the external server has a list of reserved subnet configurations stored therein. The client device comprises a memory and a processor configured to execute instructions stored on said memory to cause said client device to: access the list of reserved subnet configurations from the external server; choose a subnet configuration based on the list of reserved subnet configurations; and instruct the second Wi-Fi network device to establish a second network having the chosen subnet configuration.