Hybrid Access

IETF #91
Hybrid Access Network
(Bonding Two or More Accesses)
draft-lhwxz-hybrid-access-network-architecture
N. Leymann, C. Heidemann
M. Wasserman
Li Xue (Speaker), D. Zhang
A. Petrescu
S. Gundavelli
IETF91, Honolulu
1
Typical Customer Edge (CE) Router
• A typical CE router today has one DSL link
in future a CE router will have a 3G/4G Link
• A typical CE router today supports IPv4
in future a CE router will support IPv6
Wi-Fi Client
Phone
PC
NAS
Fixed
TV
CE Router
Internet
xDSL
2
BBF Activity
Hybrid Access for Broadband Networks Work
project was approved in June 2014 BBF meeting
– 2014.546.03
3GPP
RG
Internet
Fixed
Hybrid Access
=
Gateway Function
Bonding
Gateway
3
Hybrid Access with Bonding Gateway
Wi-Fi Client
3G/4G
Phone
3G/4G
Internet
PC
NAS
Fixed
TV
xDSL
CE Router
Bonding
Gateway
Bonding
Multiple Interfaces (Physical or Logical) on the CE Router
4
Hybrid Access without Bonding Gateway
Wi-Fi Client
3G/4G
Phone
3G/4G
Internet/
Bonding Provider
PC
NAS
Fixed
TV
xDSL
CE Router
Bonding
Multiple Interfaces (Physical or Logical) on the CE Router
The 3G/4G and fixed networks may belong to the same operator or to different operators
5
Hybrid Access Requirements (1)
•
Cost effective way to provide higher bandwidth
–
•
Leverages existing network deployments
Bandwidth on demand
–
If the fixed access network is fully utilized or reaches a certain
congestion threshold, some bandwidth of the wireless access
network can be added on demand
•
Improved service reliability
–
If one access network fails or is degraded, the service can still be
provided without interruption through the other access network
6
Hybrid Access Requirements (2)
•
Decouples the life cycle for fixed and mobile access networks
–
Supplements the DSL network that may be difficult to upgrade,
especially in certain areas
•
Faster provisioning
–
A customer can receive early service through the mobile access
network while the fixed access network is being provisioned
•
Application based Path Selection
–
Traffic of specific applications may be statically associated with a
specific access network
• No software updates required on host
7
Traffic Distribution Schemes
Flow A
3G/4G
Host
Bonding
Gateway
CE Router
Flow B
Internet
Fixed
Flow-Based Distribution
Flow A
Host
3G/4G
Bonding
Gateway
CE Router
Internet
Fixed
Packet-Based Distribution
• Packet-based and flow-based distributions can be applied together
• Flow-based: jitter sensitive flows (e.g., real-time VoIP)
• Packet-based: higher bandwidth and jitter insensitive flows (e.g., data download)
• Certain traffic types may be routed directly over a specific network, rather than
through the bonded network
8
Flow-Based Distribution
Per-flow
3G/4G
Phone
PC
TV
3G/4G
LTE
LTE
DSL
DSL
CE Router
Fixed
xDSL
Bonding
Gateway
• Each traffic flow is carried over the 3G/4G network or over the fixed network
• Not over both networks
9
Packet-Based Distribution
Per-Packet
3G/4G
Phone
PC
TV
DSL first
3G/4G
LTE
LTE
DSL
CE Router
Fixed
xDSL
DSL
Bonding
Gateway
DSL offload
On 3G/4G
• If the traffic volume is lower than the fixed network bandwidth, all the traffic is
carried on the fixed access network
• If the traffic volume is higher than the fixed network bandwidth, the overflow
packets are carried on the 3G/4G network
10
Path Failure
3G/4G
Phone
PC
3G/4G
LTE
LTE
DSL
Fixed
TV
CE Router
xDSL
DSL
Bonding
Gateway
• If the 3G/4G path is down, the traffic is carried on the fixed network
• If the fixed path is down, the traffic is carried on the 3G/4G network
11
Possible IETF Work
• A mechanism to setup and bond multiple paths together
• A mechanism to negotiate a traffic distribution for specific types of
traffic (per-packet and/or per-flow)
– Distributed solution: control plane
– Centralized solution: centralized control entity
• A mechanism to describe the traffic distribution policy
– E.g., for flow-based distribution, flow A goes to 3G/4G, flow B goes to
DSL, etc.
• A mechanism to enable dynamic traffic distribution adjustments
– To account for latency, bandwidth, MTU, etc.
• A mechanism to monitor the state of each of the multiple paths
• Support for both IPv4 and IPv6
• An example of an address assignment for bonding
12
Discussion
• Any clarification question?
13
Thank You
14