Why L3 to Edge

X2 Traffics need L3 to Edge (ex: CoMP)

1 ATN950B
1

3
CX600

2 ATN950B IPBB
n n

n n n
CX600

1
ATN950B

3
1
1
2

X2 Traffics require <10ms latency. Microwave latency is longer than fiber (normally 1ms for each hop)
 Non-L3-to-Edge:
 (1) All eNodeB in same subnet/same VLAN - broadcast issue
 (2) All eNodeB in different subnet/different VLAN - latency issue

 L3-to-Edge: Solve broadcast and latency problem. Save at least 5% bandwidth.

Network Expansibility of L3 is better

MSTP Network Expansion IP Network Expansion

modified modified
ATN950B CX600 CX600

ATN950B

CX600 CX600
ATN950B

• MSTP is a static technology. It • IP network only requires re-assign IP

addresses of ports
requires re-configuration of • With the flexibility of IP technology, the
the whole network routes and service paths will be

• High risks of miss-operation. adjusted automatically

eNB Re-homing Needs L3 to Edge

eNodeB Re-homing frequently EE Target: No more involvement from MBH Ops.

EPC1 EPC2

No manual operation

L3 to Edge is flexible to meet the requirements of MBH and significantly

reduce the OPEX of transport network.
Comparison

List IP RAN MPLS-TP Comments

For L2, the GW of eNB is at AGG; but for L3, the GW of eNB is at CSG, to realize the nearest
LTE X2 Traffic Delay good bad
forwarding
Smooth Expansion good bad Scalability of L3 is better, and for the future evolution of IP-based
Large FIB good bad The FIB of router is better than MSTP+, PTN, LSW

QoS Capability good bad The QoS capability of router is better than switch,and MSTP+

Re-homing for eNodeB good bad

L2 network lack of the methods of fault location, the problem is difficult to locate and the fault path
Troubleshooting &
good bad can‘t be found; E2E L2, wireless failures and transmission failures coupling, need to co-locate and
Responsibility Demarcation
it is difficult to responsibility delimitation.

L2 Loop good bad

L3 supports the use of more sophisticated management capabilities such as ACL to enforce some
Security Capability good bad
degree of traffic partitioning

IP Multicast is used in M1 interfaces(an interface between e-MBMS GW and eNB) for point-to-
Multicast Traffic good bad
multipoint delivery of user packets
Any Connection good bad Dynamic routing in access, aggregation and mobile core
Skill of OAM good bad