IPv4 to IPv6 Knowledge Mapping via Unique Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The transition to IPv6 infrastructure lacks the mature knowledge base for geographic location identification, IP address reputation, and IP-based protection that IPv4 has developed over decades, leading to inaccuracy and inefficiency in mapping and managing IP addresses.

Innovation Solution

A dual stack web server system that maps knowledge associated with IPv4 addresses to IPv6 addresses and vice versa by generating unique identifiers and using them to verify associations, ensuring accurate and real-time updates, and allowing offline gathering of mappings to deduce DHCP subnet levels for ISPs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IPv6 infrastructure is deployed without mapping to IPv4 knowledge base, then IPv6 adoption is enabled, but geographic location identification and IP address reputation accuracy deteriorate

Engineering Contradiction:
ImproveIPv6 adoptionVSAvoidgeographic location identification accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent uses a mapping system as an intermediary between IPv6 addresses and the existing IPv4 knowledge base. The mapping engine correlates IPv6 addresses with IPv4 addresses through network flow analysis and geographic location data, allowing IPv6 traffic to benefit from mature IPv4 reputation and location databases without requiring direct IPv4 deployment

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual copy of the IPv4 knowledge base structure for IPv6 addresses. By mapping IPv6 addresses to corresponding IPv4 addresses and copying over geographic location, reputation, and protection infrastructure data, the system enables IPv6 to leverage established IPv4 knowledge without direct modification of IPv6 protocols

Inventive Principle:
Principle #26Copying

2Reliability

If real-time mapping updates are implemented, then IP address association accuracy is improved, but system complexity and resource consumption increase

Engineering Contradiction:
ImproveIP address association accuracyVSAvoidmapping system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs mapping updates in advance by continuously monitoring network flows and pre-computing IPv6 to IPv4 address mappings. The system proactively updates the mapping database before queries are made, storing pre-computed geographic location and reputation data so that real-time lookups can be performed efficiently without complex computation at query time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mapping system automatically monitors its own accuracy by analyzing network flows and detecting when IPv6 addresses should be mapped to different IPv4 addresses. The system self-updates its mapping database based on observed network behavior, reducing the need for manual intervention and external complexity while maintaining high accuracy

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If mapping data is collected from 3rd party providers, then data collection is simplified, but data freshness and accuracy deteriorate due to delayed updates

Engineering Contradiction:
Improvedata collection simplicityVSAvoiddata freshness
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent implements continuous mapping data collection by constantly monitoring network flows between IPv6 and IPv4 addresses. Rather than relying on periodic updates from third parties, the system continuously observes actual network usage patterns and updates mappings in real-time, ensuring data freshness while maintaining automated collection simplicity

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system uses feedback from actual network traffic to validate and update mapping data. By monitoring whether mapped IPv6-IPv4 address pairs actually communicate with each other in practice, the system continuously refines its mappings based on real-world usage, ensuring both accuracy and freshness without relying on external providers

Inventive Principle:
Principle #23Feedback

4Productivity

If offline mapping gathering is performed, then processing efficiency is improved, but real-time update capability is reduced

Engineering Contradiction:
Improvemapping processing efficiencyVSAvoidreal-time update speed
Core Design Contradiction:
ProductivityVSSpeed

Solution Approach 1:

The patent performs bulk mapping computations offline by analyzing network flow data and pre-computing IPv6 to IPv4 mappings during periods of lower system load. These pre-computed mappings are stored in the database for efficient retrieval, while a background monitoring process continuously detects changes and triggers selective real-time updates only when necessary

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system combines periodic offline batch processing with event-driven real-time updates. Routine mapping computations are performed in offline batches for efficiency, while the system simultaneously monitors for specific events (such as new IPv6 addresses or changed network patterns) that trigger immediate real-time mapping updates, optimizing both processing efficiency and responsiveness

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10498694B2Mapping IPv4 knowledge to IPv6
Publication Date: 2019.12.03 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10498694B2 patent drawing
  • US10498694B2 patent drawing
  • US10498694B2 patent drawing

AI summary

Knowledge associated with an address of a first IP type may be mapped to an address of a second IP type. In response to receiving, at a first IP endpoint type, a request from a client associated with a first and second IP address type, a first address of the first IP type associated with the client is recorded. A unique identification of the request is generated. The unique identifier and instructions to make a second request to a second IP endpoint type are sent to the client. The second request, that includes the unique identifier and corresponds to the second IP address type associated with the client, is received at the second endpoint. Both the first address and the second address are determined as corresponding to the client by determining that the unique identifier was used in both requests. The first address is mapped to the second address.