Service Emulation Interface for Access Network Traffic Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current access networks face challenges in efficiently supporting diverse types of services, bandwidth, and quality of service (QoS) due to the need for separate provisioning and handling of different interface and framing standards, leading to increased complexity and burden in managing and aggregating traffic.
Innovation Solution
The implementation of a service emulation interface and interworking function that converts communications from one transport format to another, allowing for the termination and processing of service emulation communications, enabling the aggregation and routing of various types of traffic as carrier-tagged flows within the access network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate provisioning and handling of different interface and framing standards is used, then support for diverse services and bandwidth is achieved, but device complexity and operational burden increase
Solution Approach 1:
The patent introduces a service emulation interface as an intermediary layer between customer devices and the core network. This interface emulates different service types (ATM, Frame Relay, TDM, IP) without requiring the core network to directly handle multiple protocols. The intermediary handles protocol conversion and abstraction, allowing the core network to treat all services uniformly while maintaining support for diverse service types.
Solution Approach 2:
The service emulation interface provides multi-functionality by supporting multiple service types (ATM, Frame Relay, TDM, IP) through a single unified interface. Instead of requiring separate provisioning mechanisms for each service type, the system uses one interface that can emulate various service characteristics, thereby reducing operational complexity while maintaining versatility.
2Reliability
If separate provisioning of different services is used, then service-specific requirements are met, but traffic aggregation and routing complexity increases
Solution Approach 1:
The service emulation interface acts as a mediator that receives traffic from customer devices using their native protocols and converts it into a unified service emulation format. This abstraction layer maintains service quality by preserving QoS parameters while simplifying traffic aggregation, as the core network only needs to handle one type of emulated traffic regardless of the original service type.
Solution Approach 2:
The patent segments the network into two distinct parts: the access network side with service-specific interfaces and the core network side with unified service emulation handling. This segmentation allows service-specific requirements to be met at the access level while the core network maintains simplified, unified traffic management through the service emulation interface.
3Adaptability or versatility
If multiple interface standards are supported directly in core network, then service diversity is achieved, but scalability and ease of operation deteriorate
Solution Approach 1:
The service emulation interface serves as an intermediary that shields the core network from protocol diversity. Network operators interact with a single unified interface type rather than managing multiple interface standards directly in the core network. This intermediary layer maintains protocol support for various services while significantly improving operational simplicity through standardization.
Solution Approach 2:
The service emulation interface provides universal functionality by supporting multiple service types through a single standardized interface. This multi-functionality approach allows the core network to maintain broad protocol support while operators experience a simplified, uniform interface for provisioning and management, thereby improving ease of operation without sacrificing versatility.
Data Source
AI summary
System and method for providing a termination point for service emulation instances in an access network is provided. In an embodiment, the service emulation instances are implemented utilizing, for example, pseudowires. Communications to and from the access network are aggregated and transmitted via one or more pseudowires to a service emulation instance terminator. The service emulation instance terminator converts the traffic to its native form and, if necessary, converts the traffic to a different type of format or service. The service emulation instance terminator then frames the traffic for the appropriate type of service and transmits the traffic to the service edge. Traffic received from the service is removed prepended with a pseudowire label and aggregated with other traffic. The aggregated traffic is transmitted to the customer via the access network. If necessary, an interworking function may convert the traffic from one type of service to another type of service.