Service Binding MAC Address Replacement for Network Traffic Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current IP networks face challenges in efficiently managing data traffic with the increasing number of user devices and service providers, particularly in providing higher quality of service without compromising data traffic quantity and routing efficiency, as existing solutions like MPLS result in reduced data traffic and slower routing capabilities.

Innovation Solution

The method and nodes for aggregating data traffic using service bindings over access domains, specifically by creating and enforcing service bindings at access edge nodes, which modify Unicast messages by replacing user device MAC addresses with virtual MAC addresses to manage data traffic between user domains and service provider domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If MPLS is used to provide higher quality of service, then quality of service is improved, but data traffic quantity is reduced and routing capabilities are slowed

Engineering Contradiction:
Improvequality of serviceVSAvoiddata traffic quantity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments data traffic into different types (service provider traffic and other traffic) and applies different handling mechanisms. Service provider traffic is aggregated and forwarded without MPLS label switching, while other traffic continues to use traditional routing. This segmentation allows QoS improvement for specific traffic without compromising overall network productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts service provider traffic from the general data traffic flow and handles it separately through service bindings. By taking out this specific traffic type and applying dedicated service bindings, the system improves QoS for these flows without subjecting them to the overhead that would reduce overall data traffic quantity and routing speed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Quantity of substance

If the number of user devices and service providers increases, then network capacity is improved, but routing efficiency is reduced

Engineering Contradiction:
Improvenumber of devicesVSAvoidrouting efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent merges multiple service bindings into a single aggregated data flow that is forwarded without individual label switching operations. By combining multiple service provider traffic flows into a unified service binding, the system supports an increasing number of devices and service providers while maintaining routing efficiency through reduced per-packet processing overhead.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal service binding mechanism that can handle multiple service providers and user devices through a common framework. This multi-functional approach allows the same service binding infrastructure to serve numerous devices and providers, scaling network capacity without proportionally increasing routing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If service bindings are created to manage data traffic, then quality of service is improved, but device complexity is increased

Engineering Contradiction:
Improvequality of serviceVSAvoidservice binding management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where access edge nodes automatically create and enforce service bindings based on service requests. The system performs self-configuration and self-management of service bindings without requiring complex manual configuration, thereby improving QoS while minimizing the operational complexity burden on network administrators.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-establishing service bindings at access edge nodes before data traffic needs to be managed. Service bindings are created in advance based on service requests, allowing the system to handle quality of service requirements efficiently without adding complexity during actual data traffic processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7660253B2Method and nodes for aggregating data traffic through unicast messages over an access domain using service bindings
Publication Date: 2010.02.09 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US7660253B2 patent drawing
  • US7660253B2 patent drawing
  • US7660253B2 patent drawing

AI summary

The present invention relates to a method and nodes for performing data traffic aggregation over an access domain using service bindings. Upon receipt of a service request related message at an access edge node for a first device of a user domain, the service request related message identifying the first device of the user domain and one of the service provider domains, a service binding is created at the access edge node. The service binding rules data traffic between the first device of the user domain and the service provider domain by committing an access node serving the user domain and the access edge node in a manner of managing data traffic therebetween over the access domain. An access node serving the user domain for which the service request related message is received is informed of the created service binding. The created service binding is enforced at the access node and the access edge node for data traffic over the access domain between the first device of the user domain and the service provider domain by removing a user device MAC address from Unicast messages exchanged therebetween over the access domain and replacing with a virtual MAC address recognized by the access node and the access edge node.