25.12.2012 Views

MPLS in Mobile Backhaul Networks Framework and Requirements ...

MPLS in Mobile Backhaul Networks Framework and Requirements ...

MPLS in Mobile Backhaul Networks Framework and Requirements ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>MPLS</strong> <strong>in</strong> <strong>Mobile</strong> <strong>Backhaul</strong> <strong>Networks</strong> <strong>Framework</strong> <strong>and</strong> <strong>Requirements</strong> Technical Specification IP/<strong>MPLS</strong> Forum 20.0.0<br />

___________________________________________________________________________________<br />

<strong>in</strong>terface between BS <strong>and</strong> aGW on one h<strong>and</strong> <strong>and</strong> over the <strong>in</strong>terface between BSs on the other h<strong>and</strong>. It is<br />

important to note that the same L3VPN <strong>MPLS</strong> transport solution [RFC4364] has to be used to backhaul<br />

both the BS-aGW <strong>in</strong>terface <strong>and</strong> the BS-BS <strong>in</strong>terface <strong>in</strong> order to have a homogeneous <strong>and</strong> efficient<br />

solution.<br />

The connectivity between the CSG <strong>and</strong> the L3VPN <strong>in</strong> the access network can be provided by a native<br />

layer 2 technology or emulated us<strong>in</strong>g e.g., VPWS or VPLS.<br />

BS1<br />

BS2<br />

BS3<br />

S1/R6<br />

IP TNL<br />

S1/R6<br />

IP TNL<br />

S1/R6<br />

IP TNL<br />

Access Aggregation<br />

CSG1<br />

CSG2<br />

CSG3<br />

CSG1<br />

CSG2<br />

CSG3<br />

CSG1<br />

CSG2<br />

CSG3<br />

Cell SIte<br />

Gateway<br />

(CSG)<br />

CSG1<br />

CSG2<br />

CSG3<br />

Access<br />

network<br />

Access<br />

Node<br />

Edge<br />

Node<br />

Edge<br />

Node<br />

Aggregation<br />

network<br />

Edge<br />

Node<br />

<strong>Mobile</strong><br />

Aggregation<br />

Site Gateway<br />

(MASG)<br />

L3VPN <strong>MPLS</strong> transport network solutions<br />

IP<br />

Access<br />

network<br />

IP<br />

L3VPN<br />

L3VPN<br />

L3VPN<br />

IP TNL<br />

S1/R6<br />

L3VPN<br />

<strong>MPLS</strong><br />

aGW<br />

aGW<br />

S5/S8a<br />

Core<br />

IP/<strong>MPLS</strong><br />

Core<br />

network<br />

Note: BS supports Ethernet<br />

<strong>in</strong>terface.<br />

One Cell Site Gateway can<br />

connect multiple BS.<br />

October 2008 Page 28<br />

R3<br />

VRF<br />

S3/S4<br />

R3<br />

SGSN<br />

S5/S8a PDN GW<br />

S6a<br />

HA<br />

HSS<br />

<strong>MPLS</strong> PE function could be<br />

<strong>in</strong>tegrated <strong>in</strong>to the aGW<br />

(MME GW, S-GW, ASN GW)<br />

Figure 13: Reference Architecture for Flat <strong>Mobile</strong> <strong>Networks</strong> with L3VPN <strong>MPLS</strong> Transport <strong>in</strong> the<br />

Access (optional)/Aggregation/Core networks.<br />

6.3 IP TNL Scenario<br />

As mentioned before, only the IP TNL is used <strong>in</strong> flat mobile networks (e.g., LTE, HSPA+ flat, mobile<br />

WiMAX, UMB) on the mobile <strong>in</strong>terfaces between BS <strong>and</strong> aGW, <strong>and</strong> on the mobile <strong>in</strong>terfaces between<br />

BSs for control plane <strong>and</strong> user plane (e.g. S1/X2 for LTE, R6/R8/R2 for WiMAX).<br />

This scenario covers RAN equipment communicat<strong>in</strong>g by means of IP packets. The <strong>MPLS</strong> PE function<br />

may transport the IP traffic us<strong>in</strong>g IPoEtho<strong>MPLS</strong> us<strong>in</strong>g e.g., L2VPNs or IPo<strong>MPLS</strong> us<strong>in</strong>g e.g., L3VPNs as<br />

a transport solution. Note that there is no explicit Ethernet TNL def<strong>in</strong>ed. It is envisioned that the IP TNL<br />

uses Ethernet as its underly<strong>in</strong>g layer 2 just as it could use other layer 2 protocols.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!