No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE20E-S V800R010C10SPC500 Feature Description - VPN 01

This is NE20E-S V800R010C10SPC500 Feature Description - VPN
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Application of HVPN on an IP RAN

Application of HVPN on an IP RAN

Service Overview

As 3G and Long Term Evolution (LTE) services develop, mobile operators keep building and expanding RANs. This situation imposes high requirements on the bandwidth, scalability, and configuration flexibility of the IP RAN between base transceiver stations (BTSs)/NodeBs/eNodeBs and base station controllers (BSCs)/radio network controllers (RNCs)/mobility management entities (MMEs). IP datacom networks, as the mainstream of datacom networks, are large in scale and provide a variety of access modes. To maximize carriers' return on investment, reduce network construction costs, and evolve the existing network smoothly to an LTE network, an IP RAN solution is introduced.

In the HVPN bearer solution, the RAN provides excellent fixed-mobile convergence (FMC) capabilities and has simple and flexible networking. The hierarchical network between CSGs and radio service gateways (RSGs) can bear various types of services.

Networking Description

As shown in Figure 7-48, the HVPN bearer solution involves three types of devices:
  • CSG: On an HVPN, CSGs function as UPEs to provide access services for BTSs/NodeBs/eNodeBs.

  • Access service gateway (ASG): On an HVPN, ASGs function as SPEs to provide access services for UPEs.

  • RSG: On an HVPN, RSGs function as NPEs to connect to BSCs/RNCs/MMEs.

Figure 7-48 Networking diagram for the HVPN bearer solution

Feature Deployment

The HVPN bearer solution applies to large-scale networks with dynamic routing capabilities. Table 7-6 uses an HoVPN bearer solution as an example to describe feature deployment for E2E Ethernet service bearer and protection.

Table 7-6 Feature deployment in an HoVPN bearer solution

Feature

Description

Service

  • LTE S1/X2

  • 3G Eth

IGP

IGP multi-processes must be deployed between CSGs and RSGs to ensure proper data forwarding. A routing policy needs to be configured on ASGs to aggregate and filter routes. This configuration reduces bandwidth requirements for updating and maintaining routes.

Recommended routing protocol: IS-IS multi-processes

MPLS tunnel

MPLS tunnels must be established between CSGs and ASGs, and between ASGs and RSGs.

Recommended tunnel protocol: MPLS TE (tunnel selectors must be configured)

VPN

Hierarchical L3VPN must be configured between CSGs and ASGs, and between ASGs and RSGs to isolate services.

Protection switching

Protection switching must be configured for nodes and links to provide high availability:
  • BGP NSR and BGP GR must be enabled network-wide to ensure stability of neighbor relationships during protection switching.

  • BGP tracking must be enabled network-wide to speed up IBGP route convergence.

  • The ConnectRetry interval for re-establishing neighbor relationships must be prolonged between a CSG and the master ASG.

  • VPN FRR must be configured on CSGs, ASGs, and RSGs.

  • MPLS TE hot standby and BFD for TE CR-LSP must be configured to protect links between devices.

QoS

E2E QoS must be configured between CSGs and RSGs to ensure service quality.

Recommended QoS solutions: DiffServ

Clock synchronization

E2E clock synchronization must be configured between CSGs and RSGs to ensure real-time data transmission.

Recommended clock synchronization technologies: synchronous Ethernet and 1588v2

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055135

Views: 10097

Downloads: 17

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next