hld guide to iptime mobile bearer hybrid rtn+cx b2b solution v1.1

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

Huawei Confidential

Security Level: INTERNAL

英文标题 :40-47pt

副标题 :26-30pt

字体颜色 : 反白内部使用字体 :

Arial

外部使用字体 : Arial

中文标题 :35-47pt

字体 : 黑体副标题 :24-28pt

字体颜色 : 反白字体 : 细黑体

2011-1-17

---Network solution design dept.

Ariel Jia (38990)

HLD Guide to IPTime Mobile Bearer Hybrid RTN+CX B2B Solution V1.1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Note: This document is for in

ternal use only.

It is forbidden to disclose it t

o customers. If

this document needs to be disclosed to

customers, review it s

trictly and delete

defects and workarounds (fonts in red) in

it.

History

Version Date Description

V0.1 10/11/2010 Draft

V0.2 22/11/2010 Modified the document based on comments of Li Kunyang.

V0.3 23/11/2010 Modified the document based on comments of Zhou Wei and Wei

Jiahong.

V0.4 27/11/2010 Modified the document based on comments of RTN experts Wang

Jianjun, Huang Kangyong, Cao Zhutao, and so on.

V0.5 03/12/2010 Updated the DCN part based on comments of Wu Jian.

V0.6 09/12/2010 Modified the synchronization part based on comments of Tang Xiaoyu,

Cao Zhutao, Hua Binshan, and Liang Bo.

V0.7 13/12/2010 Added new requirements for DCN priority configuration.

Supplemented the RTN ring & dual-hub scenario based on comments of

Huang Kangyong.

V0.8 15/12/2010 Rewritten the queue schedule technique of RTN.

V0.9 24/12/2010 Updated the document based on comments of Ruan Feng and Wu Jian.

V1.0 06/01/2011 Corrected the detailed description based on test results supplied by Ruan

Feng and Wu Jian.

V1.1 07/01/2011 Added the NMS part.

Product Version Limitation

Product Version Description

RTN900 V100R002C00SPC200

CX600 V600R001C00

U2000 V100R002C01

Architecture Overview Physical Topology

Forwarding Plane & Availability & Resiliency Single-Homed and Dual-Homed

QOS COS Definition, Flow Classification, Marking, and Scheduling

Control Plane Explanation

OAM Service Monitoring (Connectivity Check and Fault Locating)

U2000 Matching Description

Synchronization Frequency Synchronization

Network Management DCN

Contents

Glossary Acronyms and Abbreviations

Architecture Overview

• This presentation focuses on the B2B solution design in scenarios wherein the Hybrid RTN equipment is used on the access side and CX

equipment is used at the convergence layer and core layer. • It is recommended that the existing SDH network be used to carry TDM E1 and ATM services at the convergence layer. Hybrid RTN equipment

does not support ATM services but processes IAM E1 services as common E1 services. If RTN equipment is connected to the CX network, a

TDM board needs to be configured on CX equipment, which results in high cost. This presentation analyzes the case in which RTN equipment is

connected to the CX network. • RTN equipment is deployed in the chain and tree topologies. The ring topology is used only in few offices. This presentation will cover the chain

and tree topologies. • The current RTN equipment does not provide 10GE ports. Services from RTN equipment are transmitted upstream through GE ports to

equipment at the convergence layer in single-homed manner. In consideration of high reliability, this slide will describe a common requirement,

that is, RSG dual-homing. • CX equipment is deployed mostly in mesh and partial mesh topologies and the equipment is connected through GE or 10GE ports.• 2G TDM services are transmitted to BSCs through Ch STM-1s. 3G ATM services are transmitted to RNCs through ATM STM-1s and 3G Ethernet

services are transmitted to RNCs through GE ports.

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G

Last Mile Access Aggregation RNC/BSC

CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

SDHCh STM-1

英文目录标题 :35-40pt

颜色 : R153 G0 B0

内部使用字体 :

Arial


中文目录标题 :35-40pt

颜色 : R153 G0 B0

字体 : 黑体

英文目录正文 :28-30pt

子目录 (2-5 级 ) :20-30pt

颜色 : 黑色内部使用字体 :

Arial


中文目录正文 :28-30pt

子目录 (2-5 级 ):20-30pt

颜色 : 黑色字体 : 细黑体









Contents



Control Plane

The RTN equipment does not support the OSFP protocol on the control plane. Therefore, the OSFP protocol is

not involved in the HLD solution.

Note: The RTN equipment supports the OSFP protocol on the management plane only for internal interworking

on the RTN network. It does not support protocol interconnections with routers. For details, see the DCN part.

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

IS-IS/OSPF/RSVP-TE

T-LDP/R-LDP

MP-iBGP VLL/ VPN

Route Protocol










Contents



Single-Homing Scenario of TDM Services

In the Hybrid microwave ring networking, SNCP is configured for E1 services and the switching time is within 50 ms. In the chain or tree networking, the 1+1 HSB protection on the radio

link plane is recommended. The RTN equipment that functions as a hub node is interconnected to a single PE in LMSP 1:1 protection mode, which achieves protection for links within 200 ms. The CX equipment

supports 200 ms switching in LMSP 1:1 protection mode. The switching is actually within 50 ms in most cases according to tests and the switching time is longer than 100 ms in few

cases. It is not recommended that E1 cables be used to interconnect RTN equipment to CX equipment. Configuring a large number of services requires a lot of copper cables for

connections and the transmission distance is short, which does not facilitate future expansion. In addition, E1 ports on CX equipment are not protected. The current version does not support dual homing of TDM services from RTN equipment to CX equipment, which is planned to be solved in CX600 V600R003. The PE (that is, CX equipment) that supports TDM services can be configured with PW redundancy. The PE dual-homes services to two RSGs, and implements protection for RSG dual-

homing nodes and links on the RSG AC side by means of MC-APS. Note: The PW redundancy of the CX600 V600R001C00 implements PW status notification in LDP Notification mode.

The switching of a single PW takes a few hundred milliseconds. The performance deteriorates if services increase. The switching rate is boosted by means of BFD for PW in CX600

V600R003. Dual-homing TDM services to RSGs is only tested in the current version but not deployed. If no dual-homing requirement is raised, link protection is implemented by means of MPLS APS for the CX network that supports TDM services and is implemented in LMSP 1:1 mode

between the CX network and base station controllers.

RTN900

BSC

CX600

BTS E12G


CSG1

PE2

2GBTS CSG2

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

Ch STM-1

Ch STM-1 GE/10GE

E1

E1E1 CES2G E1

Protect LMSP1:1 MC-APS/LMSP1:1

Ch STM-1

HSB & SNCP PW Redundancy / MPLS APS

Ch STM-1


Single-Homing Scenario of ATM Services

E1IMA E1 ATM PWE33G IME1

Protect LMSP1:1 MC-APS/LMSP1:1

Ch STM-1

HSB & SNCP PW Redundancy / MPLS APS

ATM STM-1

RTN900 CX600

NodeB

3G


CSG1

PE2IMAE1

CSG2

Hub 1

Hub 2

PE1 RSG1

RSG2

RNC

ATM STM-1

Ch STM-1/E1

Ch STM-1/E1

NodeB

3GIMAE1

In the Hybrid microwave ring networking, ATM services are not supported, SNCP is configured for IMA E1 services, and the switching time is within 50 ms. In

the chain or tree networking, the 1+1 HSB protection on the radio link plane is recommended. The RTN equipment that functions as a hub node is interconnected to a single PE in LMSP 1:1 protection mode, which achieves protection for links within 200

ms. The CX equipment supports 200 ms switching time in LMSP 1:1 protection mode. The switching is actually within 50 ms in most cases according to tests

and the switching time is longer than 100 ms in few cases. It is not recommended that E1 cables be used to interconnect RTN equipment to CX equipment.

Configuring a large number of services requires a lot of copper cables for connections and the transmission distance is short, which do not facilitate future

expansion. In addition, E1 ports the on CX equipment are not protected. The current version does not support dual homing of TDM services from RTN equipment to CX equipment, which is planned to be solved in CX V600R003. The PE (or CX equipment) that supports IAM E1 services can be decapsulated to ATM services and configured with PW redundancy. The PE dual-homes

services to two RSGs and implements protection for RSG dual-homing nodes and RSG AC links by means of MC-APS. Note: The PW redundancy of the CX

V600R001C00 implements PW status notification in LDP Notification mode. The switching of a single PW takes a few hundred milliseconds. The performance

deteriorates if services increase. The switching rate is boosted by means of BFD for PW in CX V600R003. Dual-homing ATM services to RSGs is only tested in

the current version but not deployed. If no dual-homing requirement is raised, link protection is implemented by means of MPLS APS for the CX network that supports ATM services and is

implemented in LMSP 1:1 mode between the CX network and base station controllers. Note: The CX equipment is weak in processing ATM services. It does not support N:1 ATM services.


Single-Homing Scenario of Ethernet Services

For Hybrid microwave Ethernet services, the RTN equipment is actually deployed in E-Line, E-LAN, or QinQ mode. E-Line and QinQ are applicable to chain networking and E-LAN is applicable to ring networking. The QinQ mode is rarely applied on the network.

If services from base stations do not carry a VLAN or base stations connected to one set of RTN equipment that functions as a hub node carry the same VLAN, VSIs (E-LAN services) can be configured on the RTN equipment first. The current equipment also supports 802.1ad bridge. That is, different CSGs forward E-LAN services after adding SVLANs to the services and implement 802.1ag based on SVLANs. If all base stations connected to one set of RTN equipment that functions as a hub node carry different VLANs, the E-Line service can be configured first. E-Line services of the Hybrid RTN microwave equipment can be configured in end-to-end manner in U2000 V100R003C00 and later versions. E-Line services can be configured only on a per-NE basis in versions earlier than U2000 V100R003C00. It is planned that E-LAN services can be configured in end-to-end manner in U2000 V100R006 and later versions.

E-Line services are protected only at the radio link layer. E-LAN services can be switched within 200 ms by means of ERPS. The switching time is as long as 500 ms if GE electrical interfaces exist on a ring.

Ethernet services converging on the RTN equipment that functions as a hub node are transmitted to the CX equipment through GE ports. Load sharing or working and protection LAGs are configured to implement protection. The CX equipment transmits the Ethernet services to the L3VPN.

RSGs works with active & standby boards (ports) on base station controllers over VRRP to implement RSG dual-homing protection. The auto-negotiation mode is used for interconnection and a single fiber fault occurs in full-duplex mode.

RNC

RTN900 CX600


CSG1

PE23G NodeB

FE

CSG2

Hub 1

Hub 2

PE1 RSG1

RSG2

GE

GE

3G NodeB

FE

E-Line / E-LAN / QinQETH IP/MPLS L3VPN3G ETH

Protect LAG VRRP & active and standby boards

GE

HSB & ERPS VPN FRR /TE FRR

/IGP Fast Convergence

GE

GE

GE/10GE


Dual-Homing Scenario of Ethernet Services — Option 1

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIVSIR

Ethernet subinterface

dot1.q subinterface

VLANIF subinterface

R

RR

RR

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSIVSI GE

GE

VRRP2

VLAN X

VLAN Y

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIVSIR


dot1.q subinterface

R

RR

RR

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSIVSI GE

GE

VRRP2

VLAN X/VLAN Y/VLAN Z

VLAN X/VLAN /VLAN Z

Active & standby boards or ports


Layer 3 interface

Layer 3 interface

Figure 1

Figure 2

VLANIF subinterface


Detailed Analysis of Dual-Homing Scenario of Ethernet Services — Option 1 When a set of RTN equipment dual-homes services to two sets of CX equipment, dual-homing protection is implemented for Ethernet services.

The description of service carrying in such a scenario is the same as that in single-homing scenarios. The following only analyzes the protection solution in detail.

Option 1 description — dominant solution for E-LAN services on the RTN equipment that functions as a hub node Prerequisite 1: If packets from base stations do not carry VLANs (the default VLAN is added to the services on the network), the DSCP value is

used to differentiate packets of different types. If packets from base stations carry the same VLAN, the Pri value is used to differentiate packets of different types. When VSIs (E-LAN services) are configured on the RTN network as shown in Figure 1, an Ethernet subinterface needs to be configured on the relevant port of the CX equipment (only one VLAN can be terminated).

Prerequisite 2: Each base station is configured with multiple VLANs, and services of the same type carry the same VLAN even if they are deployed on different base stations. For example, each base station is configured with three VLANs: OAM VLAN, signaling VLAN, and service VLAN. When VSIs (E-LAN services) are configured on the RTN equipment that functions as a hub node as shown in Figure 2, the dot1.q interface needs to be configured on the relevant port of CX equipment (a maximum of 16 VLAN segments can be terminated).

The auto-negotiation mode is preferred on the GE ports between RTN equipment and CX equipment. Subinterfaces on CX equipment are configured with VRRP. Heartbeat packets are transmitted between two sets of PE by passing through VSIs.

VRRP can be configured with BFD to achieve faster switching. EVRRP ensures switching to be completed within 500 ms in the case of a node failure. Tests show that the switching takes short than 500 ms.

In CX networking (two sets of CX equipment are insufficient) as shown in the figures, VRRP can be configured to achieve load sharing. IP addresses of base stations connected to one set of RTN equipment that functions as a hub node are planned to be in the same network

segment. They are also in the same network segment as IP addresses of corresponding subinterfaces. During tests, if a PE fault occurs, the downstream switching time is longer than one second, which is caused by the slow response of meters to

ARP packets. You can configure static ARP on the VRRP standby port to control the switching time within 500 ms. This does not occur in the actual deployment.

Assume that 1000 base stations are connected to one pair of CX equipment and microwave equipment connected to one set of RTN equipment that functions as a hub node does not exceed five hops (on the basis of 10-20 base stations), a total of 50 to 100 VRRP groups need to be configured on the CX equipment. The CX equipment can be configured with a maximum of 255 VRRP groups. Relevant performance needs to be tested if many VRRP groups are configured on the CX equipment.

Restrictions: When configuring E-LAN services on RTN equipment, ensure that heartbeat packets and BFD packets of VRRP can pass through and coupling is considered in the configuration between the RTN equipment and CX equipment.

If the 802.1ad bridge is configured on RTN equipment, packets transmitted to the CX equipment carry two VLANs, and therefore QinQ termination subinterfaces need to be configured on the CX equipment. The QinQ mode is rarely applied.



In Option 1, if RTN equipment and CX equipment are maintained by different O&M teams, VRRP heartbeat packets may not pass through the RTN

equipment. So, the management VRRP (mVRRP) mode is introduced. Here uses base stations that are connected to the RTN equipment that functions as a hub node and carry only one VLAN as an example. Ethernet

subinterfaces (only one VLAN can be terminated) and VRRP are configured on ports of CX equipment. mVRRP is configured on the link between two PEs.

This link can be configured with Ethernet-trunk to enhance the reliability and prevent the active/active mode. The service VRRP traces mVRRP. Note: In

consideration of faults on the link between the RTN equipment that functions as a hub node and the CX equipment, mVRRP requires tracing physical ports

configured with VRRP. mVRRPs with the same quantity as VRRPs need to be configured because there are multiple different physical ports. GE ports between RTN equipment and CX equipment adopt the auto-negotiation mode first. Restrictions: 1. Two PEs must be connected to each other physically. Otherwise, they transmit mVRRP heartbeat packets only over the CX network. 2. Like Option 1, a total of 100 to 200 VRRP groups need to be configured on a pair of CX equipment. The performance deteriorates if many VRRP groups

are configured. 3. The configuration is complex.

In conclusion, this option is not recommended.

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIVSIR

R

RR

RR

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSIVSIGE

GE

VRRP2

VLAN X

VLAN Y

mVRRP


dot1.q subinterface

VLANIF subinterface




Here uses the case where the VLANs of all base stations are different and the physical port used for interconnecting the RTN equipment that functions as a hub node to CX

equipment is configured with multiple VLANs as an example. The GE port between the RTN equipment and the CX equipment adopts the auto-negotiation mode first to prevent single fiber faults. E-Line services or E-LAN services can be configured on RTN equipment. Two dual-homing interfaces of the RTN equipment that functions as a hub node are configured with revertive working and protection LAGs manually. The configuration can be

across boards. The dot1.q termination subinterfaces are configured and VRRP protection is enabled on interfaces of CX equipment. A maximum of 16 VLAN segments can be terminated. If E-Line

services are configured on RTN equipment, the VRRP configuration mode is the same as that in Option 2. In this case, this option is not recommended. If E-LAN services are

configured on RTN equipment, the VRRP configuration mode is the same as that in Option 1. Restrictions: 1. The LAGs that are manually configured on the RTN equipment do not support WTR time settings. Services are switched to the original link immediately when the link

is restored. To handle this issue, when VRRP is set to be in revertive mode, the VRRP port on CX equipment needs to be configured with delay start (longer than the VRRP WTR

time) to prevent LAG switching prior to VRRP switching and prevent service interruption. Nevertheless, the LAG switching and VRRP switching cannot be synchronized completely.

The downstream services can be interrupted for a long time. 2. If LAGs and VRRP are set to be in non-revertive mode, more issues arise and the configuration is complex.

In conclusion, this option is not recommended. The RTN equipment does not support the ALS function. It is also different from the CX equipment that enables the ETH OAM function to transmit signals between ports (a port is

shut down in the transmit direction if a fault is detected by the protocol).

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R

R

RR

RR

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

VRRP2

VLAN X... VLAN Y

VLAN A... VLAN B

LAG1

LAG2


dot1.q subinterface

VLANIF subinterface




Option 4 is recommended and is described as follows: This option raises no requirement for the working mode of GE ports between RTN equipment and CX equipment. The switching time is shorter if the auto-negotiation

mode is adopted. E-Line services and E-LAN services can be configured on RTN equipment. If two VLANs need to be terminated on PE in QinQ mode, the QinQ termination subinterface needs to be configured.

Two dual-homing ports on the RTN equipment that functions as a hub node are configured with static working and protection LAGs. It is recommended that LAGs be configured across boards to achieve board-level protection.

Ports on two sets of CX equipment are configured with Ethernet-trunk protection groups. Ethernet-trunk ports are configured with dot1.q subinterfaces or Ethernet subinterfaces to remove the Layer 2 tag from packets and forward the packets at Layer 3. Dot1.q subinterfaces can process a maximum of 16 VLAN segments.

The Ethernet-trunk switching time is shortened when a node fault occurs. Ethernet-trunks are configured between two sets of CX equipment to improve the link reliability. In addition, Ethernet subinterfaces are configured and BFD is enabled. All active and standby ports configured with Ethernet-trunks trace the BFD between two sets of CX equipment.

Static LAGs on the RTN equipment do not support WTR time settings and the default WTR time is 0. The CX equipment supports WTR time settings but the settings do not take effect. If the faulty PE 1 recovers, the routes of the CX network are not updated but Ethernet-trunks are switched, which will interrupt services for a long time.

Workaround: Set the system priority of the LACP protocol on CX equipment higher than that on RTN equipment and configure delay start on Ethernet-trunk active ports to delay switching. The delay is often set to a value greater than 60s. In principle, the delay start time on a port is greater than the route convergence time of the CX network. Note: Static ARP needs to be configured on the standby PE during a test, to prevent long switching time due to a slow response of meters to ARP packets. This case does not occur in actual applications.

When LAGs and Ethernet-trunks are set to be in non-revertive mode, services are switched to the standby PE if the active PE is faulty. After the fault is rectified for the first time, the BFD cannot be traced if the active PE malfunctions again, and the switching takes several seconds (implemented in the current product). This mode is not recommended.

The switching time is shortened if a link fault occurs. The CX equipment supports BFD on interfaces. The RTN equipment does not support BFD but relies on the LACP protocol. Based on test results, if the link between the hub and PE is faulty or the PE is faulty, the switching time ranges from 200 ms to 400 ms. There is a low probability that the switching ranges from 400 ms to 500 ms.

IP addresses of base stations connected to one set of RTN equipment that functions as a hub node are planned to be in the same network segment. They are also in the same network segment as IP addresses of relevant subinterfaces.

Restrictions: The CX equipment supports only 64 Ethernet-trunks at most and one pair of CX equipment can be connected to only 64 sets of RTN equipment that functions as hub nodes at most. If only two sets of CX equipment on the network function as RSGs, there are more restrictions.

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R

R

R

R

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

...

...

BFD

BFD RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R

R

RR

RR

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

VLAN X...VLAN Y

VLAN A... VLAN B

BFD

BFD


dot1.q subinterface

VLANIF subinterface



Detailed Failure Description of Option 1 — Failure 1


Before a fault

Switching occurs when a fault occurs. Services are switched back to the original link after the fault is rectified.

Fault-free state

RNC

CX600

BTSFE

3G CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSI R

R

R

R

ETH -Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSI GEGE

VRRP2

RNC

CX600

BTSFE

3G CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIVSI R


R

RR

RR

ETH -Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSIVSI GEGE

VRRP2

dot1.q subinterface

VLANIF subinterface


Layer 3 interface

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSI R


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSI GEGE

VRRP2

Layer 3 interface

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIVSI R


dot1.q subinterface

VLANIF subinterface

R

RR

RR

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSIVSI GEGE

VRRP2

Layer 3 interface

11

Traffic Flow




RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIR


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSI GE

GE

VRRP2

Layer 3 interface

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

VSIR


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP1 VRRP3

BTSFE

3G CSG1

Hub 2

VSI GE

GE

VRRP2

Layer 3 interface

2

Before a fault


Fault-free state

Traffic Flow

Traffic Flow





RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

BFD

BFD

Before a fault


Fault-free state

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

BFD

BFD

1

Traffic Flow

Traffic Flow





RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

BFD

BFD

RNC

CX600

BTSFE

3G


CSG1

PE2

GE

Hub 1PE1 RSG1

RSG2

GE

GE

RTN900

R


dot1.q subinterface

VLANIF subinterface

R

R

R

ETH-Trunk

VRRP3

BTSFE

3G CSG1

Hub 2

GEGE

LAG1

LAG2

E-Trunk1

E-Trunk2

BFD

BFD

2

Traffic Flow

Traffic Flow

Active & standby boards

or ports

Active & standby boards

or ports

Before a fault


Fault-free state










Contents



DCN — Intra-Domain DCN on Service Ports

The DCN solution of routers is simple. The NMS can be connected to the management port or service port of an RSG through the DCN network, or can be directly connected to the management port of an RSG. The DCN network functions properly as long as the IP address is reachable. Principle: The destination IP addresses carried in OAM packets from the NMS are NEIPs of NEs. The NEIPs of NEs are recorded in routing entries of the forwarding plane. OAM packets are forwarded as common service packets and are protected as service packets.

When serving as a GNE, the RTN equipment that functions as a hub node supports a maximum of 64 non-gateway NEs and 4 neighbors. An RTN GNE can identify DCN packets transmitted from the NMS by using CX equipment in the following mode: Mode 1: Configuring service port gateway DCN on the RTN GNE An Ethernet port of the RTN equipment is configured with the DCN IP address (the NMS communicates with NEs by using this IP address rather than NEIPs in

this mode). The subinterface with the VLAN ID 4094 needs to be configured on the router and the IP address of the subinterface is in the same network segment as the DCN IP address. It is recommended that the subinterface be differentiated from the service subinterface. The RTN equipment adds VLAN 4094 to DCN packets and transmits the packets upstream. After receiving the packets, the router removes VLAN 4094. In the downstream direction, the router adds VLAN 4094 to packets transmitted to the RTN equipment.

Restrictions on mode 1: The next hop of the static route is CX equipment, which needs to be configured on the DCN port on the RTN equipment. The static route is not protected. RTN

equipment communicates with the NMS by using the IP address configured for the port. If the link connected to the port is broken and the DCN network cannot be rerouted, the RTN equipment becomes unreachable to the NMS. Even if the DCN port is the active port of an LAG, the DCN network cannot be restored after LAG switching. This is a new requirement and RTN equipment needs to support it.

DCN solution restriction: This DCN solution does not support protection. The DSCP priority of RTN DCN packets is the lowest. The Pri value is always zero after the management VLAN is added to the packets. Neither DSCP value

nor VLAN Pri value can be configured. So, the DSCP value needs to be changed if the CX network transparently transmits DCN packets. Otherwise, the CX network is congested, DCN packets of the RTN network may be discarded, and the communication between the NMS and NEs is interrupted.

Management port


dot1.q subinterface

VLANIF subinterface

Ethernet physical interface

Router’s DCN trail

RTN’s DCN trail

RNC

RTN900

BSC

CX600

Access Aggregation RNC/BSC

CSG1

PE2CSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

DCN网络DCN网络

GNE

GNE

NE

NE

NE

NE


DCN — Wrapping Solution

Mode 2: Wrapping the management port by using the service port on an RTN GNE An interface (the IP address of this interface is in the same network segment as the NEIP of the relevant RTN equipment that functions as a hub node) on the CX

equipment adds a specific VLAN to DCN packets. The RTN equipment transmits the DCN packets to the relevant service port by port+VLAN (for E-Line services) or by

VSI (for E-LAN services) to the management port. It removes the VLAN from packets on the service port. No VLAN is required for E-LAN services. A VLAN, however,

is recommended for the sake of O&M. The same VLAN can be used for CX equipment that is connected to different sets of RTN equipment that functions as hub nodes through different physical ports. The default route to the management port needs to be configured on the RTN GNE. Advantages: 1. When the RTN equipment transmits services to the CX equipment in single-homed or dual-homed manner, DCN packets use the same protection as

service packets. The DCN subinterface on the CX equipment needs to be configured with VRRP groups separately in VRRP+VSI interconnection mode, and the DCN

protection is the same as service protection. 2. The service port interconnected to the management port can add the VLAN Pri value of a high priority to DCN packets. The VLAN Pri value is processed for trust on

the CX network. This mode implements controllable DCN priority. This mode is recommended. Disadvantage: The wrapping on RTN equipment can incur additional faults. RTN GNEs communicate with non-gateway NEs through the intra-domain DCN network. By default, the communication is implemented by using the management

VLAN (default VLAN: 4094).

RNC

RTN900

BSC

CX600


CSG1

PE2CSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

DCN网络

Management port

GNE

GNE

NE

NE

NE

NE


dot1.q subinterface

VLANIF subinterface


RTN’s DCN Trail

RNC

RTN900

BSC

CX600


CSG1

PE2CSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

DCN网络DCN网络

Management port

GNE

GNE

NE

NE

NE

NE


dot1.q subinterface

VLANIF subinterface


RTN’s DCN Trail


DCN — Connecting a Service Port on CX equipment to the Management Port on RTN Equipment

Mode 3: Connecting a service port (FE port) on CX equipment to the management port on an RTN GNE The CX equipment transmits DCN packets to the management port of an RTN GNE through the special FE port. The IP address of the

FE port is in the same network segment as the NEIP of the RTN GNE. The default route to the management port needs to be configured on the management plane of the RTN GNE. Disadvantages: The DCN network is not under protection and an additional service port is required on the CX equipment. The CX equipment and RTN

equipment should be in the same telecommunications room and the transmission distance over twisted pairs is short. The DSCP of RTN DCN packets is the lowest and cannot be configured. So, the DSCP value needs to be changed to ensure the priority

if the CX network transparently transmits DCN packets. Otherwise, DCN packets of the RTN network may be discarded when the CX

network congests, and the communication between the NMS and NEs is interrupted. RTN GNEs communicate with non-gateway NEs through the intra-domain DCN network. By default, the communication is implemented

by using the management VLAN (default VLAN: 4094). The principles of IP planning relevant to the RTN DCN solution are described in later slides.

Management port


dot1.q subinterface

VLANIF subinterface


RTN’s DCN trail

RNC

RTN900

BSC

CX600


CSG1

PE2CSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

DCN网络DCN网络

GNE

GNE

NE

NE

NE

NE


DCN Planning — NE ID

Huawei transport equipment is identified by NE IDs. Hence, NE IDs should be

configured for the equipment. An NE ID is a 24-bit binary number.

When planning NE IDs, adhere to the following principles: Each NE must be configured with a unique NE ID. In the same DCN, NE IDs should not be duplicated with each other.

On a ring network, it is recommended that the NE IDs increase along one direction.

In the case of a complex network, divide the network into rings and chains. First

allocate NE IDs (1, 2, 3,…, N) to the NEs on the rings and then allocate NE IDs

(N+1, N+2, N+3,…) to the NEs on the chains.

For example, the NE ID format is XX.YY.YY. XX: Indicates the extended ID (can be the subnet number), which ranges from

1 to 254. It is recommended that the extended ID start from 11. The extended

ID of an NE on the traditional transport network may be 9. YY.YY: Indicates the basic ID, which starts from 1 and increases NE by NE. (1-

49135)


IP addresses are required for management communication between the gateway NE and the NMS. Each NE must be configured with a unique IP address. For NEs, the IP addresses of class A, B, and C can be configured. That is, the NE IP addresses range from

1.0.0.1 to 223.255.255.254, but exclude the broadcast IP addresses, network IP addresses, IP addresses in

the form of 127.x.x.x, and subnet IP addresses (192.168.x.x and 192.169.x.x). It is recommended to configure different IP subnets for the gateway NEs and non-gateway NEs. In the case of two separate networks with Ethernet connection, classify them into different IP subnets. The network segments of the IP addresses of all the service ports should not be duplicated with the network

segment of the management NE IP address. For example, the 129.9.0.0/16 network segment contains the

129.9.1.0/24 network segment. In the case of non-gateway NEs, it is recommended that the IP addresses change as NE IDs change.

DCN Planning — NE IP Address


Ethernet port:

In the case of a gateway NE, set the DCN bandwidth to 512 kbit/s. In other scenarios, set

the DCN bandwidth to the default value 512 kbit/s.

DCN Bandwidth Requirement







U2000 Matching Description Supplement to Comprehensive Test Results



Contents



Synchronization Overview

Frequency synchronization Synchronous Ethernet: The CX V600R001 does not support SSM, which is planned to be supported in CX V600R003. The

synchronous Ethernet feature cannot be commercially used. IEEE 1588v2 is currently recommended to implement frequency

synchronization. SDH synchronization IP clock server solution: If this solution adopts Huawei WCDMA base stations and only Ethernet services are configured, it is

recommended that the wireless IP clock server solution be used to implement frequency synchronization of base stations. Time synchronization: The RTN equipment V100R002 does not support IEEE 1588v2. There is no available time

synchronization solution in this scenario and only the GPS can be added to base stations. In general, dual BITSs for backup need to be considered to provide complete protection.

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

BITS 1

BITS 2


Frequency Synchronization Analysis

The BITS can transmit the frequency information to the CX equipment in two modes: Mode 1: Ethernet ports are used to transmit the frequency information. In this mode, the BITS is configured to the OC or BC. This mode is recommended. Mode 2: The frequency information is transmitted at the rate of 2 Mbit/s and the 1PPS+ToD interface is used to transmit the second pulse state. The second pulse state can be

converted to the clock class to implement switching in the case of a BITS fault. Note: This mode is not implemented yet and is unavailable currently. The CX equipment implements frequency synchronization over IEEE 1588v2 and implements protection by using the BMC algorithm. When the RTN equipment transmits services to the CX equipment in single-homed manner, the frequency can be synchronized by means of synchronous Ethernet (nodes are not

protected in this topology). When the RTN equipment dual-homes services to the CX equipment, SDH synchronization or synchronous Ethernet can be used for frequency

synchronization. The CX equipment currently cannot convert the clock class of equipment to SSM of the POS or Ethernet port. That is, the CX network cannot transmit the clock used

for protection to the RTN network. When the CX equipment enters the free running state, the equipment directly connected to the CX equipment does not support clock source

switching. The prerequisite is that the CX equipment becomes an isolated node. This scenario occurs only when a multi-point fault occurs. The RTN network internally can adopt synchronous Ethernet, SDH synchronization, E1 synchronization, or air interface synchronization. The SSM protocol must be enabled on the

RTN ring network. Note: If the RTN equipment transmits the frequency information to base stations by using E1 signals, the E1 retiming function must be enabled. Otherwise, the

performance cannot meet requirements. If base stations support synchronous Ethernet, the RTN equipment transmits the frequency information to base stations in this mode. If base stations do not support synchronous

Ethernet, the external clock port or E1 signal is used to transmit the frequency information.

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

BITS 1BITS 1

BITS 2BITS 2

1PPS+ToDETHport External clock interface: 2Mbit/s

1588V2

Sync ETH

SDH Sync

Sync ETH

Sync ETH

E1 Sync

SDH Sync


Frequency Synchronization Scale

If frequency synchronization is performed on the CX equipment, the performance

is excellent and passes the G.823 Sync template in the case of 30 hops.

The RTN restrictions are as follows (prerequisites: The RTN equipment is

interconnected through air interfaces and services are not terminated): Hops supported between a base station controller and base stations are as follows:

10 hops if IF1 boards are used.

20 hops (21 NEs) if IFU2 and IFX2 boards are used.

The BITS needs to output the clock if the number of hops exceeds the specified value.

The actual network is complex and the clock solution is closely related to the

configuration and boards. For details, see the White Paper on Clock Transmission

Over Radio (V1.20) released for RTN equipment at http://3ms.huawei.com.


Frequency Synchronization Availability & Resiliency

Failure 1 & Failure 2: BITS 1 fails to trace the GPS, the BITS equipment is faulty, a board is faulty, the links between BITS 1 and RSG 1 is faulty, and the clock source of RSG 1 is switched and traces BITS 2. The clock path is BITS 2 ->RSG 2 ->RSG 1.

Failure 3: RSG 1 is faulty. The clock tracing path of the CX equipment is changed. The clock path is BITS 2-> RSG 2-> PE. Failure 4: The link between RSG 1 and PE 1 is faulty. The clock path is BITS 1-> RSG 1-> PE 2/RSG 2-> PE 1. Failure 5 & failure 6: PE 1 is faulty and the link between PE 1 and hub 1 is faulty. The clock path is BITS 1-> RSG 1-> PE 2-> Hub

1. Failure 7: The CX network does not transmit SSM information. So, CSG 2 cannot detect failure 7 and still traces the original path clock.

As a result, switching does not occur.

Workaround: Set the SSM value of the clock source to PRC or SSU on the input port of PE 2 whose clock is traced by hub 2. The downstream port on hub 2 transmits the SSM value downstream and switching is performed successfully if failure 7 occurs on CSG 2.

Impact of unprotected clocks: For IP base stations, services on base stations function properly within 90 days if a clock input fault occurs, and the clock reliability requirement is low. For traditional TDM base stations, equipment that carry E1 services, and source and sink nodes of the CES service need to be synchronized. Otherwise, bit errors or clock slips occur in TDM services. Unprotected clocks affect carried E1 services severely.

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

BITS 1BITS 1

BITS 2BITS 21588V2

Sync ETH

SDH Sync

Sync ETH

Sync ETH

E1 Sync

SDH Sync

11Primary synchronization trail

Secondary synchronous trail

22

4466

77

3355

1PPS+ToDETHport External clock interface: 2Mbit/s


IP Clock Server Solution

If this solution uses Huawei WCDMA base stations and only Ethernet services are configured, it is recommended that the wireless IP clock server

solution be used to implement frequency synchronization of base stations.

This solution is essentially a 1588 ACR solution involving the server and base stations (client). The frequency is restored at a base station, and therefore

the frequency offset tolerance of the base station can be as high as 50 ppb. The intermediate network requirement in this solution is far lower than that in

the ACR solution.

Network equipment needs to transparently transmit 1588 ACR packets. It is not recommended that the number of hops exceed 10 for microwave

equipment.

An IP clock server can support a maximum of 500 clients. It is recommended that active and standby servers be configured to achieve protection.

RNC

RTN900 CX600

NodeB

3G

3G


CSG1

PE23G

NodeB

FE

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

GEGE

Ch STM-1

Ch STM-1

Master IP clock server

Slave IP clock server

ETHPort

FE

1588 ACR

Primary synchronization trailSecondary synchronization trail










Contents



QoS — Overview

The QoS of a mobile backhaul network cannot be determined by network

engineers independently. The wireless department is required to provide

the following clear QoS requirements: QoS marking method for wireless services

Expected results achieved by QoS marking method for wireless services (including

packet loss rate, delay, jitter, and packet discarding priority in the case of

congestion)

Expected mapping mode of network equipment (This requirement is optional and

network design engineers design it based on the preceding two requirements.)

Different carriers raise different QoS requirements. The subsequent slides

focus on common design modes such as flow classification, marking, and

scheduling.


QoS — TDM Service

The requirements of wireless equipment for TDM services are low delay, low jitter, and fixed bandwidth. Characterized by timeslot cross-connection and fixed bandwidth, TDM services on an RTN network are provided with high

QoS innately. E1 services on a CX network can join EF queues for grooming after being encapsulated into PWs. They are high QoS

services. EXPs of PWs or tunnels on an entire CX network map to EF queues. As to QoS in the Diffserv model, the mapping

of E1 signals <-> queues <-> EXPs of PWs or tunnels is consistent on a CX network. E1 services can be encapsulated into PWs and tunnels. The bandwidths of PWs and tunnels can be configured.

E1E1 E1 EXPE1 EXPE1

RTN900 CX600RNC

RNC

BSCE1BTS

2G


CSG1

PE2E1

CSG2

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

GE

ATM STM-1

Ch STM-1

Ch STM-1BTS

2G

SPP

WFQ

CS7CS6EFAF4AF3AF2AF1BE

SP

WFQ


SP

E1

WFQ

SPP

SPP

WFQP

E1

SPP


QoS — ATM Service

ATM networks can carry voice services, video services, and Internet access services based on the service traffic type. Characterized by timeslot cross-connection and fixed bandwidth, E1 services on an RTN network are provided with

high QoS innately. IMA E1 services are converted to ATM services first on a CX network. ATM services of different types are

encapsulated into different PWs or tunnels, which map to queues of different priorities. As to the QoS in the Diffserv

model, the mapping of ATM traffic types <-> queues <-> EXPs of PWs or tunnels is consistent on a CX network. The bandwidth of PWs and tunnels can be configured.

E1E1 E1 EXPE1 EXPIMA E1

RTN900 CX600RNC

RNC

BSC

NodeB

3G


CSG1

PE2IMAE1

CSG2

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

GE

ATM STM-1

Ch STM-1

Ch STM-1

3G

IMAE1NodeB

SPP

WFQ


SP

WFQ


SP

WFQ

SPP

SPP

WFQP

CBR

rt-VBR

nrt-VBR

UBR+UBR

CBR

rt-VBR

nrt-VBRUBR+UBR


QoS — Ethernet Service

The QoS of Ethernet services lies in the downstream direction. The priority of Ethernet services can be differentiated by the VLAN Pri value or DSCP

value. If Ethernet services carry no VLAN, the priority is differentiated only by the DSCP value. RTN and PTN equipment can classify services by the

Pri value or DSCP value and map the services to different queues for grooming.

As to the QoS in Diffserv model, the mapping of Ethernet services <-> queues <-> EXPs of PWs or tunnels is consistent on the entire network.

In addition to queue scheduling, Ethernet services can be configured with a CAR policy in the UNI ingress and shaping in the NNI egress on the CSG

or RSG.

Note: The RTN equipment does not support WFQ scheduling currently but supports only WRR.

RNC

RTN900

BSC

PTN3900/1900

BTSE1

2G


CSG1

SPE2

3G

NodeBFE

CSG2

GE

GE

Hub 1

Hub 2

SPE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

PRIEXP EXP EXPEXP EXPPRI

DSCPEXP EXP EXPEXP EXPDSCP

VoIP

VOD

BTV

HSI

VoIP

VOD

BTV

HSI

SPP

WFQ


WRR

SPP

SP

WFQ


SP

SPP

WFQP


QoS — Conclusion

QoS mechanisms enable the bearer network to implement

the following features:

Meeting requirements for packet loss rate, delay, and jitter of

wireless services of different types

Protecting services of high priority (such as voice services) if

congestion occurs


Description of the Hybrid RTN Queue Scheduling Technology

Scheduling Algorithm

Complexity Delay/Jitter Fairness

RR Simple implementation and low complexity

Delay and jitter are severe if the scheduling rate is low.

Dependent on packet length

WRR Simple implementation and low complexity

Delay and jitter are severe if the scheduling rate is low.

Dependent on packet length

WFQ High complexity The delay is controlled properly and the jitter is low.

Based on the byte granularity. The scheduling is fair.

The Hybrid RTN equipment supports SP and WRR scheduling modes and the CX

equipment supports SP, WRR, and WFQ scheduling modes. The QoS requirement is low if the Hybrid RTN equipment is deployed at the access

layer.






OAM Service Monitoring (Connectivity Check and Fault locating)




Contents



OAM — Real-Time Detection

In a B2B solution, there are few OAM features that can be used for interconnecting the RTN equipment to the CX equipment. ATM PWE3 or CES services on a CX network: The Y.1711 in tunnel technology is used to detect the connectivity, delay, jitter,

and packet loss rate of a tunnel. The Y.1731 mechanism is used in LSPs. ETH OAM: Both the RTN equipment and CX equipment support 802.1ag and 802.3ah.

Tunnel

PW

ETH

MPLS OAM (Y.1711) 　CV / FFD / FDI / BDI

PW OAM (Y.1711) 　CV / FFD / FDI / BDI

ETH OAM (802.1ag) 　

CC / LB / LTETH OAM (802.3ah) 　 ETH OAM (802.3ah) 　

Auto-discovery, link status detection, and remote loopback


RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

ETH OAM (802.3ah) 　



OAM — Manual Detection Overview

After service configuration is complete or a fault occurs, some mechanisms need to be triggered manually to detect the network connectivity or

locate the fault. The mechanisms that are commonly used on an IP network are ping test and traceroute. The ICMP ping or traceroute can be used to check the connection between base station controllers, CX network, and base stations. The RTN

service plane does not support ICMP ping or traceroute. The RTN management plane supports ICMP ping if the IP protocol is used.

Tunnel

PW

LSP pingLSP Traceroute

VCCV ping 　

RNC

RTN900

BSC

CX600

BTS

NodeB

E1

2G

3G


CSG1

PE23G

NodeB

IMAE1

FECSG2

GE

GE

Hub 1

Hub 2

PE1 RSG1

RSG2

Ch STM-1

RNC

GE

ATM STM-1

GE

Ch STM-1

Ch STM-1

ICMP Ping/TR 　










Contents




Based on preceding analysis, the Hybrid RTN+CX B2B solution can be deployed in end-to-

end manner in few base stations.

The NMS supports L3VPN configuration on CX equipment.

Hybrid microwave E-Line services can be configured in end-to-end manner in U2000

V100R003C00 and later versions. The services can be configured only on a per-NE basis in

earlier versions. It is planned that E-LAN services can be configured in end-to-end manner in

U2000 V100R006 and later versions.

The U2000 V100R003C00 supports the end-to-end clock view function. In U2000

V100R002C01SPC002, clock view is displayed incorrectly. That is, Ethernet and SDH clocks

are both displayed for RTN equipment. The issue is modified on RTN equipment and the

modification is incorporated into U2000 V100R002C01SPC003, which displays SDH clocks

regardless of SDH synchronization or synchronous Ethernet. The U2000 V100R003 displays

ETH clocks in synchronous Ethernet and SDH clocks in SDH synchronization.

Thank youwww.huawei.com

hld guide to iptime mobile bearer hybrid rtn+cx b2b solution v1.1

Documents

facilitate

vbr ubr ubr

rtns dcn trail

rtn gnes communicate

rncpe9 rsg9atm

scheduling

11 hsb protection

rncpe2 rsg2atm