Network Node VLAN Allocation for Local Service Cloud IP Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless radio networks, the non-unique Internet Protocol (IP) addresses allocated to User Equipment (UE) cause interference and routing issues, especially when UEs move between base stations, as the same private IP addresses can be reused, leading to confusion in local service clouds and broken connectivity during handovers.

Innovation Solution

Implementing Network Address Translation (NAT) between the UE and the local service cloud, and using Virtual Local Area Networks (VLANs) to ensure unique UE IP addresses within each realm, allowing traffic to be properly routed to the correct UE by isolating non-unique IP addresses and managing VLAN allocation dynamically based on IP address usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the same private IP addresses are reused for UEs moving between base stations, then IP address resources are efficiently utilized, but routing confusion and connectivity breakdown occur in local service clouds

Engineering Contradiction:
ImproveIP address utilization efficiencyVSAvoidrouting reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments the network into multiple VLANs (Virtual Local Area Networks) within the local service cloud. Each VLAN creates an isolated broadcast domain and Layer 2 network segment. When a UE with a reused IP address connects, the network node allocates it to a specific VLAN, effectively segmenting the network traffic so that IP address conflicts are contained within individual VLANs rather than affecting the entire network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces VLAN tags as an intermediary mechanism between the IP address layer and the physical network. These tags act as additional identifiers that mediate traffic routing, allowing packets with the same IP address to be distinguished by their VLAN membership. The network node uses these intermediate VLAN identifiers to properly route traffic even when IP addresses are reused across different UEs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If multiple UEs with the same IP address are served in the same VLAN, then network configuration is simplified, but traffic routing to the correct UE becomes ambiguous

Engineering Contradiction:
ImproveVLAN configuration complexityVSAvoidtraffic routing accuracy
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent adds another dimension to network identification by introducing VLAN tags as a Layer 2 identifier. Instead of relying solely on IP addresses (Layer 3), the system creates a two-dimensional identification space: IP address + VLAN ID. This dimensional addition allows the network to distinguish between multiple UEs with the same IP address by their VLAN membership, resolving routing ambiguity without complicating the IP address allocation scheme.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If dynamic VLAN allocation is implemented to ensure unique IP addresses per VLAN, then routing accuracy is improved, but network node complexity increases

Engineering Contradiction:
Improvetraffic flow routing reliabilityVSAvoidnetwork node processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-establishing multiple VLANs in the local service cloud before UEs connect. The network node maintains a mapping table that tracks which IP addresses are currently assigned to which VLANs. When a UE connects, the node proactively checks this table and allocates an appropriate VLAN before any traffic flow occurs, preventing routing conflicts from the outset rather than resolving them later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent incorporates feedback mechanisms where the network node continuously monitors IP address usage across VLANs and dynamically adjusts VLAN allocations. The node maintains state information about current VLAN assignments and uses this feedback to make intelligent allocation decisions, ensuring that IP address reuse does not cause conflicts while optimizing VLAN utilization based on current network conditions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10735372B2Network node and method for handling a traffic flow related to a local service cloud
Publication Date: 2020.08.04 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US10735372B2 patent drawing
  • US10735372B2 patent drawing
  • US10735372B2 patent drawing

AI summary

A method in a network node for handling a traffic flow of a User Equipment, UE is provided. The network node is related to a local service cloud. The traffic flow is related to an application session to be served by the local service cloud. The network node identifies (202) a UE Internet Protocol, IP, address of the UE. When the identified UE IP address is used by another UE in a first Virtual Local Area Network, VLAN, comprised in the local service cloud, the network node selects (204) a second VLAN comprised in the local service cloud for local break out of the traffic flow of the application session to the local service cloud. In the second VLAN, the identified UE IP address is not used by another UE.