Mobilebackhaul-Design Guide Juniper

8/17/2019 Mobilebackhaul-Design Guide Juniper

1/186

Design Guide

Copyright © 2013, Juniper Networks, Inc.

UNIVERSAL ACCESS AND

AGGREGATION MOBILE

BACKHAUL DESIGN GUIDE


2/186

2 Copyright © 2013, Juniper Networks, Inc.

Design Guide - Juniper Networks Universal and Aggregation MBH 1.0

This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company.

Copyright © 1986-1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were

developed at private expense, and no part o them is in the public domain.

This product includes memory allocation sotware developed by Mark Moraes, copyright © 1988, 1989, 1993, University

o Toronto.

This product includes FreeBSD sotware developed by the University o Caliornia, Berkeley, and its contributors. All o

the documentation and sotware included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents o

the University o Caliornia. Copyright ©1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents o the

University o Caliornia. All rights reserved.

GateD sotware copyright © 1995, the Regents o the University. All rights reserved. Gate Daemon was originated and

developed through release 3.0 by Cornell University and its collaborators. GateD is based on Kirton’s EGP, UC Berkeley’s

routing daemon (routed), and DCN’s HELLO routing protocol. Development o GateD has been supported in part by the

National Science Foundation. Portions o the GateD sotware copyright © 1988, Regents o the University o Caliornia.

All rights reserved. Portions o the GateD sotware copyright © 1991, D.L. S. Associates.

This product includes sotware developed by Maker Communications, Inc., copyright © 1996, 1997, Maker

Communications, Inc.

Copyright 2013 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos and Fabric

are registered trademarks o Juniper Networks, Inc. in the United States and other countries. All other trademarks,

Service marks, registered marks, or registered service marks are the property o their respective owners. Juniper

Networks assumes no responsibility or any inaccuracies in this document. Juniper Networks reserves the right tochange, modiy, transer, or otherwise revise this publication without notice.

Juniper Networks assumes no responsibility or any inaccuracies in this document. Juniper Networks reserves the right

to change, modiy, transer, or otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereo might be covered by one or more o the ollowing

patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051,

6,333,650, 6,3 59,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,5 18, 6,538,899, 6,55 2,918, 6,567,902,

6,578,186, and 6,590,785.

Juni per Networks Universal Access and Aggr egatio n MBH Des ign Guide

Release 1.0

The inormation in this document is current as o the date on the title page.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject o this technical documentation consists o (or is intended or use

with) Juniper Networks sotware. Use o such sotware is subject to the terms and conditions o the End User License

Agreement (“EULA”) posted at http://www.juniper.net/support/eula.html. By downloading, installing, or using such

sotware, you agree to the terms and conditions o this EULA.

http://%20http//www.juniper.net/support/eula.htmlhttp://%20http//www.juniper.net/support/eula.html


3/186

Copyright © 2013, Juniper Networks, Inc. 3


Table of Contents

END USER LICENSE AGREEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Overview o the Universal Access and Aggregation Domain and

Mobile Backhaul. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Universal Access and Aggregation Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Market Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

MBH Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

What is MBH? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Types o MBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

MBH Network and Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

MBH Network Inrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Access Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Preaggregation and Aggregation Segments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Core Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

MBH Network Layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

End-to-End Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

End-to-End MPLS-Based Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

End-to-End MPLS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Seamless MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Type o Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

End-to-End Hierarchical LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Decoupling Services and Transport with Seamless MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Mobile Service Proiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2G Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3G Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

HSPA Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4G LTE Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

MBH Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Solution Value Proposition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Juniper Networks Solution Portolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Design Considerations Worklow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Gathering End-to-End Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Designing the Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Planning the Network Topology and Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34


4/186



Deciding on the Platorms to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Deining the MBH Network Service Proile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Designing the MPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Designing UNI Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Designing NNI CoS Proiles and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Designing the IP and MPLS Transport Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Designing Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Veriying the Network and Product Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Considering the Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Topology Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Planning the Network Segment and Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Access Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Preaggregation and Aggregation Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Core Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Number o Nodes in the Access and Preaggregation Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Sizing the MBH Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

MBH Service Proiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4G LTE Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Deining the CoS Attribute at the UNI Interace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

HSPA Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

End-to-End Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Layer 2 VPN to Layer 3 VPN Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

End-to-End Hierarchical VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3G and 2G Service Proiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

CoS Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Timing and Synchronization Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Synchronous Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

IEEE 1588v2 Precision Timing Protocol (PTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Ordinary Clock Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Ordinary Clock Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Synchronization Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

End-to-End IEEE 1588v2 with a Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

End-to-End IEEE 1588v2 with an Ordinary Clock in the Access Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Synchronous Ethernet Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

End-to-End IP/MPLS Transport Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


5/186



Implementing Routing Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Intradomain Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8

IGP Protocol Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8

Using IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Using OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Intradomain LSP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Deciding on the LSP Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Interdomain LSP Signaling with BGP-Labeled Unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

MPLS Services Design or the 4G LTE Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

End-to-End Layer 3 VPN Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

VRF Import and Export Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

U-Turn Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

IP/MPLS Transport and Service Full Picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8

MPLS Service Design or the HSPA Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Layer 2 VPN to Layer 3 VPN Termination Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hierarchical VPLS or Iub over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

MPLS Service Design or the 3G Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

MPLS Service Design or the 2G Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Intrasegment OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Intersegment OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

High Availability and Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Correcting a Convergence Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Detecting Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Flooding the Inormation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Finding an Alternate Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Updating the Forwarding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Components o a Complete Convergence Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Local Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Intrasegment Transport Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Intersegment Transport Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

End-to-End Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Layer 3 VPN End-to-End Protection or 4G LTE Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Pseudowire Redundancy or the HSPA Service Proile (Layer 3 VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Pseudowire Redundancy or the HSPA Service (H-VPLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89


6/186



Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Providing Transport Services or Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

MBH Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Design Consistency and Scalability Veriication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Sample MBH Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Cell Site Router Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

RIB and FIB Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

MPLS Label FIB (L-FIB) Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

CSR Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5

AG 1 Router Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96


MPLS Label FIB (L-FIB) Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

AG 1 Router Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97



MPLS Label FIB Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98



MPLS Label FIB Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Recommendations or IGP Region Numbering and Network Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Loopback and Inrastructure IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

UNI Addressing and Layer 3 VPN Identiier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Management (xp0) Interace Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Network Topology Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Hardware Inventory Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Coniguring IP and MPLS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 14

Coniguring the Network Segments and IS-IS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Coniguring Intrasegment MPLS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Coniguring Intrasegment OAM (RSVP LSP OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Coniguring Intersegment MPLS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Coniguring End-to-End Layer 3 VPN Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Coniguring MP-BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Coniguring the Routing Instance or the Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147


7/186



Coniguring Layer 2 VPN to Layer 3 VPN Termination Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 5

Coniguring Layer 2 Pseudowires in the Access Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Coniguring Inter-AS Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Coniguring a Layer 2 Pseudowire to Layer 3 VPN Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Coniguring a Layer 2 VPN to VPLS Termination Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Coniguring a Pseudowire in the Access Segment (VPLS Spoke) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 6

Coniguring a VPLS Hub in the Preaggregation Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Coniguring End-to-End Inter-Autonomous System VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Coniguring ATM Pseudowire and SAToP/CESoPSN Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Coniguring ATM and TDM Transport Pseudowire End-to-End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Coniguring Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Coniguring PTP Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Coniguring Synchronous Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Coniguring Class o Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Coniguring Class o Service on Cell Site Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Coniguring Class o Service on AG 1, AG 2, and AG 3 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183


8/186



List of Figures

Figure 1: Universal access solution extends universal edge intelligence to the access domain . . . . . . . . . . . . . . . . . . . . . . . . .15

Figure 2: Universal access and aggregation domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 3: Architectural transormation o mobile service proiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 4: MBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Figure 5: MBH network inrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 6: MBH network layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 7: Seamless MPLS unctional elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 8: Multiregion network within one autonomous system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 9: Multiregion network with numerous autonomous systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 10: Seamless MPLS unctions in a 4G LTE backhaul network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 11: Seamless MPLS unctions in an HSPA backhaul network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 12: MBH service proiles and deployment scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 13: Juniper Networks platorms in the MBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 14: Ring topology in an access segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 15: Hub-and-spoke topology in the access segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 16: Large-scale MBH network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 17: Network segment sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 18: Recommended service architecture or 4G LTE service proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 19: HSPA service proile with end-to-end layer 3VPN and pseudowire in the access segment . . . . . . . . . . . . . . . . . 44

Figure 20: HSPA service proile with end-to-end VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 21: 3G and 2G networks with ATM and TDM interaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 22: CoS marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 23: 802.1p and DSCP to EXP rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 24: IEEE 1588v2 end-to-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 25: IEEE 1588v2 end-to-end with boundary clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 26: IEEE 1588v2 and Synchronous Ethernet combined scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

F igu re 27: IEEE 15 88v 2, Sy nc hro nou s Eth er net, an d B ITS co mb in ed s ce nar io . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6

Figure 28: Semi-Independent access domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 29: IGP LSA boundaries within the access segment and semi-independent domain . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 30: Routing inormation isolation with the IS-IS protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 31: Routing inormation isolation with the OSPF Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 0

Figure 32: Establishing an inter-AS LSP with BGP-LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 33: Layer 3 VPN design or the 4G LTE service proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Figure 34: End-to-end Layer 3 VPN deployment scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 35: Layer 3 VPNs with a ull mesh topology—VPN-S1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 36: Layer 3 VPNs with a ull mesh topology—VPN-X2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 37: VRF import and export policies or S1 Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 38: Using VRF import and export policies or X2 Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66


9/186



Figure 39: End-to-end Layer 3 VRF deployment scenarios with U-turn VRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 40: End-to-end Layer 3 VPN and data low or eNodeB to 4G EPC connect iv ity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 41: End-to-end Layer 3 VPN and data low or eNodeB to eNodeB connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Fi gu re 42: Layer 2 VP N te rmi nati on in to Layer 3 VP N o r th e H SPA ser vi ce pro i le . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 43: End-to-end Layer 3 VPN with Layer 2 VPN terminat ion deployment scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 44: H-VPLS service model or the HSPA service proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Figure 45: End-to-end H-VPLS deployment scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 46 MPLS pseudowire or Iub over ATM (3G service proile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 47: End-to-End ATM and TDM pseudowire deployment scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 48: MPLS pseudowire or Abis over TDM or the 2G service proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 49: MPLS pseudowire or Abis over TDM (2G service proile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 50: OAM in the MBH solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 51: Intrasegment acility link and link-node protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Figure 52: Intrasegment acility protection with LDP tunneling over RSVP in the access segment . . . . . . . . . . . . . . . . . . . . 85

Fi gu re 53 : In traseg men t path pro tec ti on wi th LD P tu nn el in g over an RSV P LS P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Figure 54: Intersegment transport protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Figure 55: End-to-end protection or end-to-end Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 56: End-to-end protect ion or Layer 2 VPN to Layer 3 VPN terminat ion scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Figure 57: Maintaining traic path consistency or Layer 2 VPN termination to Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 58: End-to-end protection or HSPA service proile (H-VPLS deployment scenario) . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Figure 59: MBH network topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 60: Regional large-scale MBH network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Figure 61: Format or IS-IS area number addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 62: Sample MBH network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 63: Sample network topology with IP addressing, IS-IS, and BGP autonomous systems . . . . . . . . . . . . . . . . . . . . . . 114

Figure 64: Intrasegment MPLS deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Figure 65: Intersegment MPLS deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Figure 66: MP-BGP deployment or Layer 3 VPN services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Figure 67: End-to-end Layer 3 VPN deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Figure 68: Layer 2 VPN to Layer 3 VPN termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 5

F igu re 69 : Dep loy me nt s ce nar io o Layer 2 VP N to Layer 3 V PN ter mi nati on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2

Figure 70: Layer 2 VPN to VPLS termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Figure 71: Deployment scenario o Layer 2 VPN to VPLS termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 6

Figure 72: Deployment o SAToP and CESoPSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

Figure 73: PTP design overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Figure 74: Synchronous Ethernet deployment topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Figure 75: Topology or CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178


10/186



List of Tables

Table 1: Terms and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 2: Mobile Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 3: Mobile Network Interaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 4: MPLS Service Types Across the MBH Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 5: Juniper Networks Platorms Included in the Universal Access and Aggregation MBH Solution . . . . . . . . . . . . . . . 30

Table 6: Requirements or MBH Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 7: Sample Network Segment Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Table 8 4G LTE QoS Class Identiiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 9: MBH CoS with Six Forwarding Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 10: Mobile Network Service Mapping to CoS Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 11: Mobile Network Services Mapping to MBH CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Table 12: Node Functions and IGP Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Table 13: MPLS Service or the 4G LTE Service Proile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Table 14: MPLS Service or the HSPA Service Proile—Iub over IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Table 15: HSPA Services Iub over Ethernet Layer 2 VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Table 16: 3G Services on Iub over ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Table 17: Services on 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Table 18: Sample Network Segment Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table 19: Sample Network Services and Service Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table 20: Scaling Analysis and Veriication or the CSR FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Table 21: Cell Site Router Scaling Analysis or the L-FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Table 22: Cell Site Router Scaling Analysis or Service Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Table 23: Cell Site Router Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Table 24: AG 1 Router Scaling Analysis or the FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Table 25: AG 1 Router Scaling Analysis or the L-FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Table 26: AG 1 Router Scaling Analysis or Service Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Table 27: AG 1 Router Scaling Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Table 28: AG 2 Router Scaling Analysis or the FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Table 29: AG 2 Router Scaling Analysis or the L-FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Table 30: AG 2 Router Scaling Analysis or Service Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Table 31: AG 3 Router Scaling Analysis or the FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Table 32: AG 3 Router Scaling Analysis or the L-FIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Table 33: AG 3 Router Scaling Analysis or Service Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Table 34: IPv4 Addressing and IGP Region Numbering Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Table 35: Layer 3 VPN Attribute Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Table 36: Hardware Components or the Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Table 37: Sample MBH Network IP—Addressing Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107


11/186



Part 1: Introduction

This part includes the ollowing topics:

• Overview o the Universal Access and Aggregation Domain and Mobile Backhaul

• MBH Network and Service Architecture

• Juniper Networks Solution Portolio

Overview of the Universal Access and Aggregation Domain andMobile Backhaul

This guide provides the inormation you need to design a mobile backhaul (MBH) network solution in the access

and aggregation domain (oten reerred to as just the access domain in this document) based on Juniper Networks

sotware and hardware platorms. The universal access domain extends rom the customer in the mobile, residential,

or business—Carrier Ethernet Services (CES) and Carrier Ethernet Transport (CET)—segment to the universal edge. The

ocus o this guide is the mobile backhaul (MBH) network or customers in the mobile segment.

Customers are eager to learn about Juniper Networks MBH solutions or large and small networks. Solutions based

on seamless end-to-end MPLS, and the Juniper Networks® ACX Series Universal Access Routers and MX Series 3D

Universal Edge Routers allow Juniper to deliver solutions that address the legacy and evolution needs o the MBH,

combining operational intelligence and capital cost savings.

This document serves as a guide to all aspects o designing Juniper Networks MBH networks. The guide introduces key

concepts related to the access and aggregation network and to MBH, and includes working configurations. The advantageso the Juniper Networks Junos® operating system together with the ACX Series and MX Series routers are covered in detail

with various use cases and deployment scenarios. Connected to the MX Series routers, we use the Juniper Networks TCA

Series Timing Servers to provide highly accurate timing that is critical or mobile networks. This document is updated with

the latest Juniper Networks MBH solutions.

Audience

The primary audience or this guide consists o:

• Network architects—Responsible or creating the overall design o the network architecture that supports their

company’s business objectives.

• Sales engineers—Responsible or working with architects, planners, and operations engineers to design and implement

the network solution.

The secondary audience or this guide consists o:

• Network operations engineers—Responsible or creating the configuration that implements the overall design. Also

responsible or deploying the implementation and actively monitoring the network.

Terminology

Table 1 lists the terms, acronyms, and abbreviations used in this guide.

Table 1: Terms and Acronyms

Term Description

2G second generation

3G third generation

3GPP Third-Generation Partnership Project

4G LTE ourth-generation Long Term Evolution (reers to 4G wireless broadband technology)

Abis Interace between the BTS and the BSCABR area border router

AN access node

APN access point name

ARP Address Resolution Protocol

AS autonomous system

ATM Asynchronous Transer Mode

BA behavior aggregate (classifiers)

BBF Broadband Forum


12/186



Term Description

BCD binary-coded decimal

BFD Bidirectional Forwarding Detection (protocol)

BGP Border Gateway Protocol

BGP-LU BGP-labeled unicast

BIR bit error rate

BN border node

BS base station

BSC base station controller

BTS base transceiver station

CapEx capital expenditure

CE customer entity or customer edge, depending on the context

CES Carrier Ethernet Services

CESoPSN Circuit Emulation Service over Packet-Switched Network

CET Carrier Ethernet Transport

CFM connectivity ault management

CIR committed inormation rate

CLI command-line interace

CO central office

CoS class o service

CSG cell site gateway

CSR cell site router

DHCP Dynamic Host Configuration Protocol

DLCI data-link connection identifier

DSCP Differentiated Services code point

EBGP external BGP

EEC Ethernet Equipment Clock

eNodeB Enhanced NodeB

EPC evolved packet core

ESMC Ethernet Synchronization Messaging Channel

EV-DO Evolution-Data Optimized

EXP bit MPLS code point

FCAPS ault, configuration, accounting, perormance, and security management

FDD requency-division duplex

FEC orwarding equivalence class

FIB orwarding inormation base

FRR ast reroute (MPLS)

GbE Gigabit Ethernet

Gbps gigabits per second

GGSN Gateway GPRS Support Node

GM grandmaster

GNSS Global Navigation Satellite System

GPRS General Packet Radio Service

GSM Global System or Mobile Communications

HLR Home Location Register

HSPA high-speed packet access

H-VPLS hierarchical VPLS

IBGP internal BGP

IEEE Institute o Electrical and Electronics Engineers

IGP interior gateway protocol

IMA inverse multiplexing or ATM


13/186



Term Description

IP Internet Protocol

IS-IS Intermediate system-to-Intermediate system

ISSU unified in-service sofware upgrade (unified ISSU)

ITU International Telecommunication Union

Iub Interace UMTS branch—Interace between the RNC and the Node B

LAN local area network

LDP Label Distribution Protocol

LDP-DOD LDP downstream on demand

LFA loop-ree alternate

L-FIB label orwarding inormation base

LFM link ault management

LIU line interace unit

LOL loss o light

LSA link-state advertisement

LSI label-switched interace

LSP label-switched path (MPLS)

LSR label-switched router

LTE Long Term Evolution

LTE-TDD Long Term Evolution – Time Division Duplex

MBH mobile backhaul

MC-LAG multichassis link aggregation group

MEF Metro Ethernet Forum

MF multifield (classifiers)

MME mobility management entity

MP-BGP Multiprotocol BGP

MPC mobile packet core

MPLS Multiprotocol Label Switching

MSC Mobile Switching Center

MSP managed services provider. MSP can also stand or mobile service provider.

MTTR mean-time-to-resolution

NLRI network layer reachability inormation

NMS network management system

NNI network-to-network interace

NSR nonstop routing

NTP Network Time Protocol

OAM Operation, Administration, and Management

OpEx operational expenditure

OS operating system

OSI Open Systems Interconnection

OSPF Open Shortest Path First

OSS/BSS operations and business support systems

PCU Packet Control Unit

PDSN packet data serving node

PDU protocol data unit

PE provider edge

PFE Packet Forwarding Engine

PGW Packet Data Network Gateway

PLR point o local repair

POP point o presence

pps packets per second


14/186



Term Description

PRC primary reerence clock

PSN packet-switched network

PSTN public switched telephone network (or telecom network)

PTP Precision Timing Protocol

PWE3 IETF Pseudowire Emulation Edge to Edge

QoE quality o experience

QoS quality o service

RAN radio access network

RE Routing Engine

RIB routing inormation base, also known as routing table

RNC radio network controller

RSVP Resource Reservation Protocol

S1 Interace between the eNodeB and the SGW

SAFI subsequent address amily identifier

SAToP Structure-Agnostic Time Division Multiplexing (TDM) over Packet

SFP small orm-actor pluggable transceiver

SGSN Serving GPRS Support Node

SGW Serving Gateway

SH service helper

SLA service-level agreement

SMS short message service

SN service node

SPF shortest path first

TD-CDMA time division-code-division multiple access

TDD time division duplex

TDM time-division multiplexing

TD-SCDMA time-division–synchronous code-division multiple access

T-LDP targeted-LDP

TN transport node

UMTS universal mobile telecommunications system

UNI user-to-network interace

UTRAN UMTS Terrestrial Radio Access Network

VCI virtual circuit identifier

VLAN virtual LAN

VoD video on demand

VPI virtual path identifier

VPLS virtual private LAN service

VPN virtual private network

VRF VPN routing and orwarding (table)

VRRP Virtual Router Redundancy Protocol

WCDMA Wideband Code Division Multiple Access

X2 Interace between eNodeBs, or between eNodeB and the MME

Universal Access and Aggregation Domain

The universal access and aggregation domain (oten reerred to as just the access domain in this document) is

composed o the network that extends rom the customer in the mobile, residential, or business—Carrier Ethernet

Services (CES) and Carrier Ethernet Transport (CET)—segment to the universal edge. The ocus o this guide is the

mobile backhaul (MBH) network or customers in the mobile segment.

Universal access is the means by which disparate technologies developed or mobile, residential, and business purposes

converge into an integrated network architecture. The disparate technologies have evolved over time rom circuit

switched to packet switched, rom time-division multiplexing (TDM) to IP and Ethernet, and rom wireline to wireless.


15/186



The universal edge is the means by which service providers deliver services to the customer—services such as over-

the-top video, IPTV, high-speed Internet, video on demand (VoD), and transactional services. The converged universal

access network complements the universal edge with a seamless end-to-end service delivery system. (See Figure 1.)

Single OSSingle Control Plane

Seamless End-to-end ServiceOperational Simplicity and Scale

Financial Viability

IP/MPLS

UNIVERSAL ACCESS UNIVERSAL EDGE

DATACENTERS

ACX Series

Mobile

Residential

Business(CES/CET)

Backbone

IP /INTERNET

Figure 1: Universal access solution extends universal edge intelligence to the access domain

The access and aggregation domain is divided into three use cases: mobile or MBH, business or CES/CET, and

residential (see Figure 2). Each use case is urther divided into various service proiles, depending on the underlying

media, service provisioning, topology, and transport technology. Common to all use cases is the need to provide an

end-to-end network and service delivery, timing, synchronization, and network management. The ocus o this design

guide is the MBH use case.

MOBILE BACKHAUL BUSINESS ACCESS

D O M A I N

U S E

C A S E S

S E R

V I C E

P R O

F I L E S

RESIDENTIAL

ACCESS

ACCESS & AGGREGATION

Foundation Technologies (Seamless MPLS, End-to-End Service Restoration, Timing and Sync)

Network Management

2G 3G HSPA 4G LTE E-LINE E-LAN E-TREELegacy

TransportMigration

DifferentService

DeliveryModels

Figure 2: Universal access and aggregation domain


16/186



The mobile backhaul (MBH) use case covers the technologies that must be deployed to connect mobile service

provider cell sites (base stations) to the regional mobile controller site (BSC/RNC) or mobile packet core (SGW/PGW/

MME). This use case presents complexity due to the need to support various legacy and next-generation technologies

simultaneously. Mobile service providers must continue to support legacy service proiles that en able 2G and 3G service

as well as newer and next-generation service proiles that support HSPA and 4G LTE services. Each service proile adds

potential complexity and management overhead to the network. The service provider must deal with various transports

required to support these service proiles while also working to reduce capital and operational expenditures (CapEx/

OpEx) o the MBH network. Mobile operators also seek to increase the average revenue per user through a ocus on

implementing a lexible architecture that can easily change to allow or the integration o enhanced and uture services.

Market Segments

One o the main market actors ueling a movement toward a uniied and consolidated network is the rising cost o

MBH. Combine this cost increase with the ongoing exponential increase in mobile bandwidth consumption and the

introduction and rapid migration to 4G LTE, and the cost problem is urther exacerbated. The subscriber’s consumption

o high-bandwidth, delay-sensitive content such as video chat, multiplayer real-time gaming, and mobile video largely

uels the increasing demand or bandwidth. Another actor to consider is the security o the underlying inrastructure

that protects the packet core and access network. All these actors converge into a ormula that makes it diicult or

mobile operators to reduce CapEx and OpEx. The increasing complexity o the network makes these goals harder to

achieve, and this makes the drive to increase average revenue per user a much more diicult proposition.

Given the challenges in this market segment, an ideal MBH network is one that is designed with a ocus on consolidation

and optimization. This ocus allows or more efficient installation, service provisioning, and operation o the network.

MBH Use Case

The MBH use case described in this guide includes our service proiles or the dierent generations o wireless

technologies—2G, 3G, HSPA, and 4G Long Term Evolution (LTE). Each service proile represents a undamental change

in the nature o the cellular wireless service in terms o transport technology, protocols, and access inrastructure. The

changes include a move rom voice-oriented time-division multiplexing (TDM) technology toward data center-oriented

IP/Ethernet and the presence o many generations o mobile equipment, including 2G and 3G legacy as well as 4G LTE

adoption. Because the MBH solution supports any generation o mobile inrastructure, it is possible to design a smooth

migration to 4G using the inormation in this guide. (See Figure 3.)

Hierarchical to Flat

Hub-Spoke to Fully

Meshed

TDM/ATM to ALL-IP

INTERNET

MME

PCRF

HSS

3GPPEvolvedPacket Core

Enhanced Node B (eNodeB)

SGW PGW

IP

IP

INTERNET

PSTN

ATM/IP

TDM/ATM

IPHOSTED

SERVICES

PCRF

GGSN

SGSNGW/MSC

RNC/BSC

UTRAN

HLR

Node B Node B

OFF-NETSERVICE

ON-NETSERVICE

Figure 3: Architectural transformation of mobile service profiles


17/186



Problem Statement

The undamental problem with the MBH segment is the inherent complexity introduced by the various network

elements needed to properly support the multiple generations o technology required to operate a complete MBH

network. This complexity conlicts with the provider’s ability to provide increased average revenue per user. Increasing

margin per user can be achieved by decreasing the overall cost o the network inrastructure, but how? As users

demand more bandwidth and higher quality services, the traditional answer has been “more bandwidth.” To increase

average margin per user, a service provider has to either charge more per subscriber or lower the cost o the network.

The ability to lower network cost, rom an implementation, ongoing operational, and liecycle perspective is the ocus

o the MBH solution. The Juniper Networks MBH solution collapses the various MBH technologies into a converged

network designed to support the current ootprint o access technologies while reducing complexity and enabling

simpler, more cost-eective network operation and management. This optimization enables easier adoption o uture

technologies and new services aimed at enhancing the subscriber experience.

The service provider can achieve CapEx and OpEx reduction and acilitate higher average revenue per user by ocusing

on three key areas: implementing high-perormance transport, lowering the total cost o ownership o the network,

and enabling deployment lexibility. Providers have become used to the relative simplicity and reliability o legacy

TDM networks, and a packet-based network should provide similar reliability and operational simplicity and lexibility.

Additional challenges are emerging that place urther emphasis on the need or high-perormance transport. Flat

subscriber ees combined with an exponential increase in demand or a high-quality user experience (measured by

increased data and reliability) demand that new, more lexible business models be implemented to ensure the carrier’s

ongoing ability to provide this user experience. Lowering the total cost o ownership o the MBH network is at direct

odds with the need or high-perormance transport. The operating expense associated with MBH is increasing due

not only to the growth in user data but also the increasing cost o space, power, cooling, and hardware to support new

technologies (as well as maintaining existing inrastructure to support legacy services). As more sites are provisioned,

and as the network complexity increases, the need to deploy support to a wider ootprint o inrastructure urther

erodes the carrier’s ability to decease the total cost o ownership o the network. Finally, deployment lexibility is a

concern as the carrier’s move more into packet-based networks. The ability o a service provider to meet strict service-

level agreements (SLAs) requires deployment o new technologies to monitor and account or network perormance.

The addition o a wider array o management platorms also decreases the service provider’s ability to increase the

average margin per user o the MBH network.

The Juniper Networks universal access MBH solution is the irst ully integrated end-to-end network architecture

that combines operational intelligence with capital cost savings. It is based on end-to-end IP and MPLS combined

with high-perormance Juniper Networks inrastructure, which allows operators to have universal access and extend

the edge network and its capabilities to the customer, whether the customer is a cell tower, a multitenant unit, or a

residential aggregation point. This creates a seamless network architecture that is critical to delivering the beneits o

ourth-generation (4G) radio and packet core evolution with minimal truck rolls, paving the way or new revenue, newbusiness models, and a more lexible and eicient network.

Addressing the challenges aced in the access network by mobile service providers, this document describes the

Juniper Networks universal access MBH solution that addresses the legacy and evolution needs o the mobile network.

The solution describes design considerations and deployment choices across multiple segments o the network. It also

provides implementation guidelines to support services that can accommodate today’s mobile network needs, support

legacy services on 2G and 3G networks, and provide a migration path to LTE-based services.

Although this guide provides directions on how to design an MBH network or 2G, 3G, HSPA, and 4G LTE with concrete

examples, the major ocus is the more strategic plans or a ully converged access, aggregation and edge network

inrastructure. This inrastructure provides end-to-end services to all types o consumers, including business and

residential subscribers in agreement with industry standards and recommendations that come rom the Broadband

Forum (BBF), Metro Ethernet Forum (MEF), and Third-Generation Partnership Project (3GPP) working groups.

What is MBH?The backhaul is the portion o the network that connects the base station (BS) and the air interace to the base station

controllers (BSCs) and the mobile core network. The backhaul consists o a group o cell sites that are aggregated at a

series o hub sites. Figure 4 shows a high-level representation o mobile backhaul (MBH). The cell site consists o either

a single BS that is connected to the aggregation device or a collection o aggregated BSs.


18/186



MOBILE

BACKHAUL

3G RNCNodeB

BTS

eNodeB

2G BSC

4G EPC

Figure 4: MBH

The MBH network provides transport services and connectivity between network components o the mobile operator

network. Depending on the mobile network type, the mobile network might include a number o components that

require connectivity by means o a variety o data-level and network-level protocols. (See Table 2.)

Table 2: Mobile Network Elements

Mobile NetworkGeneration

Technology Network Element Function

2G GSM BTS Communication between air interace and the basestation controller (BSC)

BSC Controls multiple base stations (BSs)

MSC Handles voice calls and short message service (SMS)

2.5G GPRS BTS Communication between air interace and BSC

SGSN Mobility management, data delivery to and rom mobileuser devices

GGSN Gateway to external data network packets

BSC+PCU Controls multiple BSs and processes data

3G EV-DO BTS Communication between the air interace and radionetwork controller (RNC)

RNC Call processing and handoffs, communication with packet

data serving node (PDSN)PDSN Gateway to external network

UTRAN NodeB Perorms unctions similar to base transceiver station(BTS)

RNC Perorms unctions similar to BSC

MSC Handles voice calls and short message service (SMS)

SGSN Mobility management, data delivery to and rom mobileuser devices

GGSN Gateway to external data network packets

4G LTE eNodeB Perorms unctions similar to BTS and radio resourcemanagement

SGW Routing and orwarding o user data, mobility anchoring

MME Tracking idle user devices, handoff management

PGW Gateway to the external data network

Types of MBH

The connectivity type oered by the backhaul network is inluenced by the technology used in the radio access network

(RAN) and by actors such as the geographical location o the cell site, bandwidth requirements, and local regulations.

For instance, remote cell sites that cannot be connected over physical links use a microwave backhaul to connect to

the base station controller (BSC) and mobile core network. The amount o available requency spectrum and spectral

eiciency o the air interace inluence the bandwidth requirements o a cell site. Hence, the backhaul network can


19/186



consist o one or a combination o physical media and transport mechanisms. Selecting among the available options

depends upon the type o radio technology, the applications in use, and the transport mechanism.

Table 3 lists the technologies and the interaces that support those technologies.

Table 3: Mobile Network Interfaces

Mobile NetworkGeneration

Mobile Technology Radio Node to BSC,RNC, or EPC Interface

Interface Provided by MBH

2G/2.5G GSM/GPRS/CDMA Abis Channelized TDM

HSPA UMTS Iub IP/Ethernet

3G UMTS Iub ATM

4G LTE S1/X2 IP/Ethernet

The our connectivity types in the ourth column deine the our dierent service proiles that we conigure in the

MBH network.

MBH Network and Service Architecture

The mobile backhaul (MBH) network and service architecture can be divided into various segments—access,

preaggregation, aggregation, edge, and core. The access, preaggregation, and aggregation segments can each be a

combination o several dierent physical topologies, depending on the scale and resiliency needs o the individual

segment. You can build each segment by using one o the ollowing topologies—hub and spoke, ring, and partial

mesh, or by using a combination o these topologies. Mobile operators can also begin with a hub-and-spoke topology

and convert to a ring topology as the scale o the network grows. The key is to have an MBH network and service

architecture that supports multiple service models—2G, 3G, HSPA, and 4G LTE—to meet legacy and evolutionary needs

Legacy networks have relied on backhauling Layer 2 technologies and carrying traic over Ethernet VLANs, Frame Relay

data-link connection identiiers (DLCIs), TDM circuits, and ATM virtual circuits. The use o several technologies or

any given service results in tighter coupling o service provisioning with the underlying network topology and limits the

lexibility o operations.

A uniied network inrastructure is an important requirement and challenge or the next-generation access network.

This challenge is not new or the telecommunications industry and has been solved in the past by enabling MPLS

technology, which provides reliable transport and supports a variety o packet-based and circuit-based services.

For both wireline and mobile networks, MPLS has become the protocol o choice or packet transport and carrier

Ethernet, and the underlying protocol or service delivery. Some operators, having taken MPLS beyond the core to the

aggregation and metro area networks, also want to deploy MPLS in the access network to reap some o the beneitsthat MPLS has provided in the core. With MPLS in the access network, operators can have added lexibility in service

provisioning. They can deine the services topology independent o the transport layer and in line with the evolutionary

changes brought on by LTE.

The service topology itsel can have multiple components through the various segments o the network. For example,

the service can be initiated as a point-to-point Layer 2 pseudowire rom the access network and be mapped to a

multipoint virtual private LAN service (VPLS) or a multipoint Layer 3 MPLS VPN in the aggregation or edge layer.

However, taking MPLS to the access segment and making MPLS the packet orwarding technology end-to-end across

the MBH network raises new challenges in comparison with MPLS deployment in the core—challenges such as:

• Cost efficiency and scaling

• Out-o-band synchronization

The new network requires cost-effective access networks that consist o tens o thousands o MPLS routers. Juniper Networks

has addressed this challenge by producing the new ACX Series routers, which are specifically built or use in the access andaggregation segments o the MPLS-enabled network. A wide range o hardware-enabled technologies have been built into the

new ACX Series and the existing MX Series routers to meet the requirements or out-o-band sunchronization.

Cost eiciency and scaling require small CSRs with robust MPLS eatures. These devices have control planes that are

much less scalable; thus, using the devices in large IP/MPLS networks requires special tools and techniques that segment

the network into smaller parts and preserve end-to-end seamless MPLS transport with no touchpoints in the middle.

MPLS has been a widely successul connection-oriented packet transport technology or more than a decade. However

it requires a ew enhancements to provide unctionality and manageability that is equivalent to the current circuit-

switched transport networks. This set o enhancements is called MPLS transport proile (MPLS-TP). MPLS-TP extends


20/186



the already rich MPLS and Generalized MPLS (GMPLS) protocol suite to serve transport and service networks with

enhancements to the data plane, such as raming, orwarding, encapsulation, OAM, and resiliency. MPLS-TP is planned

or inclusion as part o seamless MPLS in uture versions o the access and aggregation solution.

Seamless MPLS addresses the requirements or extending MPLS to the access network and signiicantly inluences

the architectural ramework or building scalable and resilient MPLS networks with a lexible services delivery model.

The topic�

Date post:	06-Jul-2018
Category:	Documents
Upload:	da-lam
View:	216 times
Download:	1 times

Mobilebackhaul-Design Guide Juniper

Documents