Carrier-Tagged Paths for Access Network Service Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current access networks face complexity and overhead in supporting diverse communication services due to the need for multiple switches and parallel networks to handle different service types, leading to a large number of virtual access connections, which burdens network elements.

Innovation Solution

The implementation of carrier-tagged paths in the access network, using methods such as carrier-tagged flows and pseudowires, allows for efficient routing and management of communications by prepending and popping carrier tags to identify and route packets across the network, reducing the need for multiple switches and parallel networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple switches and parallel networks are used to handle different service types, then service diversity and adaptability are improved, but device complexity and network overhead increase

Engineering Contradiction:
Improveservice diversityVSAvoidnetwork complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal access network that can handle multiple service types (voice, data, video, mobile) through a single network infrastructure using carrier-tagged paths. The network elements perform multiple functions by routing different service types through the same physical infrastructure, eliminating the need for separate parallel networks for each service type.

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

Solution Approach 2:

The patent uses nested carrier tags to encapsulate multiple service flows within a single network path. Different service types are nested within carrier-tagged paths, allowing multiple services to share the same physical infrastructure. This nesting approach enables service diversity while reducing network complexity by consolidating multiple separate networks into a unified structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If traditional access networks route communications independently for each service type, then service quality is maintained, but the number of virtual access connections increases, burdening network elements

Engineering Contradiction:
Improveservice qualityVSAvoidnumber of virtual connections
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple independent service routes into a unified carrier-tagged path infrastructure. Instead of maintaining separate virtual connections for each service type, the network combines voice, data, video, and mobile services into a single routed infrastructure using carrier tags. This merging reduces the total number of virtual connections while maintaining service quality through prioritization mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces carrier tags as intermediary identifiers that mediate between different service types and the physical network infrastructure. These carrier tags allow the network to distinguish and prioritize different service types while routing them through a consolidated path, reducing the burden on network elements compared to managing numerous separate virtual connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If access networks provision each service type separately with different interfaces and protocols, then service-specific requirements are met, but overhead and processing complexity increase

Engineering Contradiction:
Improveservice-specific supportVSAvoidprocessing overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent changes the routing parameter from service-type-specific processing to carrier-tag-based routing. Instead of processing each service type independently with different interfaces and protocols, the network uses carrier tags as the primary routing parameter. This parameter change allows service-specific requirements to be met through tag-based prioritization and routing while significantly reducing processing overhead.

Inventive Principle:
Principle #35Parameter changes

4Device complexity

If a single access network handles diverse services, then network simplicity is improved, but the ability to evaluate and route different interface flows becomes more complex

Engineering Contradiction:
Improvenetwork simplicityVSAvoidflow evaluation complexity
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent extracts the service identification function from the data plane and implements it through carrier tags. By separating service evaluation from the routing decision process, the network can maintain simplicity in the data plane while using carrier tags to carry service information. This extraction simplifies flow evaluation by using standardized tag-based identification rather than complex service-specific processing.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8693323B1System and method for managing communications in an access network
Publication Date: 2014.04.08 VERIZON PATENT & LICENSING INC
  • US8693323B1 patent drawing
  • US8693323B1 patent drawing
  • US8693323B1 patent drawing

AI summary

System and method for managing communications in an access network is provided. The system and method utilizes carrier-tagged paths established between communicatively coupled terminating elements, such as a service or customer edge and network elements, such as a building aggregator, layer 2 switch, or the like. The carrier-tagged paths may be nested within one another, and carrier-tagged paths may be aggregated together to simplify switching. Carrier-tagged flows carried over the carrier-tagged paths include one or more carrier tags prepended to terminating element traffic. For example, in an embodiment, inbound carrier-tagged flows from multiple sources destined for a common service edge may be merged by prepending a common carrier tag. In another embodiment, outbound carrier-tagged flows are nested within other carrier-tagged flows.