annex7 microwave dcn solution proposal for astelit v3.2

Microwave DCN Solution Proposal for Astelit

GSM Project

Huawei Technologies Co., Ltd.

April, 2008

Version 1

Microwave DCN Solution Proposal for Astelit GSM Project

TABLE OF COTENTS

1.....................................................................................Overview3

2 Converter Solution.......................................................................................3

2.1 Principle..............................................................................................................3

2.2 Procedure...........................................................................................................3

3 EMS6 Board Solution...................................................................................3

3.1 Principle..............................................................................................................3

3.2 Procedure...........................................................................................................3

4 IP Plan and NE ID..........................................................................................3

4.1 Principles for planning NE IDs............................................................................3

4.2 Principles for planning IP addresses of NE........................................................3

4.3 Extended id and region code..............................................................................3


Huawei Confidential of 10


1 Overview In this document, Huawei would like to propose its Microwave DCN solution which is aimed to translate Astelit’s requirements into technical targets and results and then to achieve them. According Astelit’s requirements, we provide two solutions about DCN network. One is use converter change NMS data into E1, send back to OMC, another is use EMS6 board change NMS data into VC12 and send back to OMC. Both of solutions need Astelit’s provide TDM channel (E1 or/VC12) between OPT node and OMC.

AbbreviationAbbreviation Full Spelling

GNE Gateway NE

VB Various Bridge

EPVL Ethernet Virtual Private Line

VID Ethernet Virtual Private Line ID

LPs Logic Ports

TE region Topology




TE Region GNE Position




Remark: other region topology will be provided when topology finalized

2 Converter Solution

2.1 Principle

We use E1 protocol converter which can implement protocol conversion between the IP signal and the E1 signal, For example convert the protocol of the signal at one 10/100Base-TX Ethernet interface into the protocol of the E1 signal, We send this E1 back to OMC through Astelit’s OPT network, in NMS center, use another converter revert to NMS data.



DDF

E1E1 ETH

ConvertorOPT NodeOPT NodeT200

0

C-convertor

LAN Switch

NMS center

E1

DDF


In order to save converter quantity in OMC. We also use C-converter that supports protocol conversion between multiple data (E1/64kbit/s) signals and IP signals. The C-converter is used in the NM center to support convergence of remote multiple directions or used at the node for converging signals in multiple directions.

2.2 Procedure

1. Use network cable connect between SCC board and converter in OPT node

2. Use special OPT node collect nearby others OPT node’s E1

3. E1 service through OPT network back to NMS Center

4. Use C-converter conversion multi-E1s and NMS data



DDF

E1 ETH

DDF

DDF

E1

E1

ETH

ETH

E1

E1

E1

Multi E1s

T2000

C-converter

LAN Switch

NMS center

E1

DDF


3 EMS6 Board Solution

3.1 Principle

The EMS6 accesses 4xFE signals and 2xGE/FE signals, and supports transparent transmission services and Layer 2 switching services. And EMS6 board also supports the following encapsulation formats: HDLC, LAPS, and GFP, eight internal ports, that is, VCTURNK1 to VCTRUNK8.

For this project, we use VB and LPs function;. that’s means PORT-shared EVPL service. For example: The service between the headquarters and branch A is transmitted over the VLANs whose VIDs are from 100 to 110, and the service between the headquarters and branch B is transmitted over the VLANs whose VIDs are from 200 to 210. If the Ethernet board at NE1 supports VLAN, use an Ethernet port whose port attribute is tag aware to access the services from the headquarters. Then, map the services of different VLANs into different VCTRUNKs. In this way, the services of different VLANs are isolated during transmission.

For VB function, In the case of the Ethernet boards that have the Layer 2 switching

capability, the switching domain can be divided into multiple independent sub-

switching domains, A VB contains several logic ports (LPs). By configuring the

mounting relation, we can mount multiple external ports and VCTRUNK ports to one

VB.

The figure as fellow relations EMS6 position in network




In order to save consumer’s VC12 and quantity in OMC, we use EMS6 board VB

function. The figure as fellow relations how it is worked

3.2 Procedure

1. Use network cable make physics connection between SCC and EMS6

2. Make the logistic connection between EMS6 and SD1 (NMS data into VC12).

3. Use RTN600 collect the data and use L2 switch function to together it.

3. Send back VC12 to NMS Center through OPT network.

4. Use NMS center’s RTN600 converter VC12 into NMS data by EMS6.

5. Make physics connection between SCC and EMS6.



T2000 LAN Switch

NMS center

RTN600

OPT/VC12network

OPT/VC12network

Fiber Fiber

T2000 LAN Switch

NMS center

OPT/VC12network

OPT/VC12network

OPT/VC12network

OPT/VC12network

OPT/VC12network

OPT/VC12network

Fiber

Fiber

Fiber

For save VC12, we collect the data and use L2 switch function to together it


4 IP Plan and NE ID

4.1 Principles for planning NE IDs

ID – is unique address, which used by T2000, which is consist of two parts: Extended ID and Basic ID.

Huawei RTN6000 Basic ID has a range from 1 to 49136. Extended ID has range from 1 to 254.

Extended ID - represents Region and SubRack Number in the same time. Refer to fallowing table to get correct value of Extended ID:

Region Subrack #1 Subrack #2 Subrack #3 Subrack #4 Subrack #5

TE 111 112 113 114 115

KN 121 122 123 124 125

UZ 131 132 133 134 135

IF 141 142 143 144 145

CR 151 152 153 154 155

LK 161 162 163 164 165

RV 171 172 173 174 175

LV 181 182 183 184 185

KR 191 192 193 194 195

TR Sites 100 100 100 100 100

Basic ID - according to digits in the Site Name directly.

For example, LK2001: Extended ID: 161, Basic ID: 2001 for first IDU. We also change a Extended ID for situation that one site has several IDU. For example, LK2001 site has 3 sub-racks, for first IDU 161:2001; For second IDU ID is 162:2001; third IDU ID is 163:2001 and so on.

Subrack numbering (#) dedicated in chronological order and from up to down in cabinet.

For TR sites Extended ID is 100, in order to differentiate between general sites and TR sites. The Basic ID – is combination of Extended ID and Transmission Site Number.

For example LKTR01 site, the ID is 100:16101.

4.2 Principles for planning IP addresses of NE

Every IDU’s IP is used by Huawei proprietary management protocol and doesn’t matter for Operation Engineers, except GNE (Gateway Network Element).




GNE IP address should be chosen according to “IP Plan”. Huawei is responsible for “IP Plan”, and Astelit responsible for IP range dedication in each region.

Each Astelit F/O Site should be arranged as GNE (EMS6 Solution).

All RTN Subracks on the same Site (if more they then one), should be cascaded to GNE over Ethernet connectivity SCC boards.

Two or more GNE on the same Site can be arranged in case more then 50 managed Subracks per one GNE.

For the non GNE SubRacks – IP Address can be easy dedicated, according to fallowing rule:

All NE IP have a template 129.AA.BB.CC. Where AA - means Extended ID, BB and CC - means site name’s first two digits and last two digits accordingly.

TR Sites: 129.AA.BB.CC. Where AA - is 100, BB – is Extended ID; CC - means site name’s last two digits accordingly.

Example:

KRTR88: ID 100:19188 [IP 129.100.191.88] SubRack#1ID 100:19288 [IP 129.100.192.88] SubRack#2ID 100:19388 [IP 129.100.193.88] SubRack#3ID 100:19488 [IP 129.100.194.88] SubRack#4ID 100:19588 [IP 129.100.195.88] SubRack#5

KRTR89: ID 100:19189 [IP 129.100.191.89] SubRack#1ID 100:19289 [IP 129.100.192.89] SubRack#2ID 100:19389 [IP 129.100.193.89] SubRack#3ID 100:19489 [IP 129.100.194.89] SubRack#4ID 100:19589 [IP 129.100.195.89] SubRack#5

LK2001: ID 161:2001 [IP 129.161.20.01] SubRack#1ID 162:2001 [IP 129.162.20.01] SubRack#2ID 163:2001 [IP 129.163.20.01] SubRack#3ID 164:2001 [IP 129.164.20.01] SubRack#4ID 165:2001 [IP 129.165.20.01] SubRack#5

LK2002: ID 161:2001 [IP 129.161.20.02] SubRack#1ID 162:2001 [IP 129.162.20.02] SubRack#2ID 163:2001 [IP 129.163.20.02] SubRack#3ID 164:2001 [IP 129.164.20.02] SubRack#4ID 165:2001 [IP 129.165.20.02] SubRack#5



annex7 microwave dcn solution proposal for astelit v3.2

Documents