Solutions of DCN

www.huawei.com
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
1.1 Constitution of the DCN
1.2 Huawei DCN Solutions
In a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEs is called
an external DCN, and the DCN between NEs is called an internal DCN.
Internal DCN
>Using one Huawei-defined DCC byte in the microwave frame to transmit NM
message, if the capacity of the PDH microwave is lower than 16xE1.

> Using three Huawei-defined DCC bytes in the microwave frame to transmit
NM message, if the capacity of the PDH microwave is not lower than 16xE1.

> Using the D1-D3, D4-D12, or D1-D12 bytes in the SDH microwave frame
and the SDH frame to transmit NM message.

> Using three Huawei-defined bytes in the Hybrid microwave frame to
transmit NM message.

> Using the Ethernet NM interface or NE cascade interface to transmit NM
message.

> Using the DCC bytes that are transmitted through the external clock
interface to transmit NM message over an SDH/PDH network.

> Supporting the inband DCN function, and using the Ethernet service
bandwidth to transmit NM message through the hybrid microwave port or
FE/GE port.
1.1 Constitution of the DCN
NOTE
> The inband DCN refers to a DCN networking mode that uses partial service bandwidth as a data
communication channel. OptiX RTN 900 uses partial Ethernet service bandwidth at a Hybrid
microwave port or FE/GE port to transmit NM message.
> The outband DCN refers to a DCN networking mode whose data communication channel does not use
service bandwidth. OptiX RTN 900 uses DCC bytes (as in the microwave frame, SDH frame, or at the
external clock interface), an Ethernet NM interface, or a NE cascading interface to transmit NM
message.
1.2 Huawei DCN Solutions
HWECC Solution IP over DCC solution
OSI over DCC solution
DCC Transparent Transmission
DCC Transparent
Transmission Through the
External Clock Interface
Inband DCN Solution
Protocol Converter Solution
7- Protocol Converter Solution
protocol converter is used to convert the NM message carried by the Ethernet into a service that can be
transparently transmitted by the equipment in the center of the network, such as the RS-232 asynchronous
data service, 64 kbit/s synchronous data service, Nx64 bit/s data service (this service can be carried by E1).
To use the protocol converter solution, the corresponding protocol converter is selected according to the
bearing capacity of the equipment in the center of the network and the supported access data type.
The principle for selecting a protocol converter is based on the situation that the DCN communication
needs to be provided for only a small amount of edge equipment. If there is a large amount of edge
equipment, whether the bandwidth provided by the protocol converter can meet the requirement of the
communication between the NE and the NMS needs to be considered. In this case, it is recommended that
you use the E1/Ethernet protocol converter.
A- RS-232/Ethernet Protocol Converter Solution
With regard to the edge equipment, the RS-232/Ethernet protocol converter and the central equipment are external DCN, which
realizes the DCN communication between the NMS and the gateway NE.
When all the edge equipment is in the same domain, the RS-232/Ethernet protocol converter can be used on the NM side and the
edge equipment side to establish a DCN channel for the edge equipment, as shown in Figure 1-2. When the edge equipment is in
multiple domains and the central equipment supports multiple RS-232 asynchronous data services, the RS-232/ Ethernet protocol
converter is used to establish DCN channels for the edge equipment in each domain. Then, the services are aggregated to the
NMS by using the LAN switch, as shown in Figure 1-3. In this case, the concentrated RS-232/Ethernet protocol converter can be
used to aggregate DCN channels from multiple domains to the same NMS.

Note- in case the central equipment support RS\232 channel interface with
dedicated asynchronous channel , no need for the converter.

Check next Example.
Huawei RTN provide two transparent channel that can be used to transmit other vendor supervision information
transparently, one is asynchronous RS232, the other is 64Kbps synchronous ITU-T G.703 , hence NEC Paso V4 and V4
can use the asynchronous RS232 to transmit back to back information to the other site
Asynchronous Data Services
The asynchronous data service is also called a transparent data service or a
broadcast data port service.
> The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errors occur.
> The equipment provides the RS-232 electrical port that complies with ITU-T V.24/V.28.
> The equipment supports only point-to-point communications.
> When the orderwire signals are transmitted over radio links, they are always transmitted through one customized overhead byte.
When the orderwire signals are transmitted over SDH fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes.
> The equipment supports the transmission of the overhead bytes in the asynchronous data service through the external clock ports
to realize the service spanning function.
> When the asynchronous data service is transmitted over the protected radio links or optical transmission lines, the asynchronous
data service is also protected.
> The equipment provides the asynchronous data ports on the SCC, cross-connect and clock board.
> The asynchronous data service is fully transparently transmitted. The
transmission rate and transmission control protocol need not be configured. The
transmission rate at the port is 19.2 kbit/s.
NOTE
> The external clock interface and wayside E1 interface are combined into one interface. This interface can
transparently transmit the DCC byte, orderwire overhead byte, and synchronous/asynchronous data
service overhead byte. One interface, however, can implement only one of the three functions: external
clock interface, wayside E1 service, and transparent transmission of the overhead byte.
> The 64 kbit/s synchronous data interface can transparently transmit the orderwire byte. One interface,
however, can implement only one of the two functions: 64 kbit/s synchronous data interface and
transparent transmission of the orderwire byte.
PIN External
Clock

EXT TI (1 PPS +
Time Information)

EXT TO (1 PPS +
Time Information)

EXT TI (DCLS)

EXT TO (DCLS)

1 RX(-)
2 RX(+)
3 PPS Input (-) PPS Output (-) Input (-) Output (-)
4 TX(-)
5 TX(+)
6 PPS Input (+) PPS Output (+) Input (+) Output (+)
7 Time Info Input (-) Time Info Output (-)
8 Time Info Input (+) Time Info Output (+)
Configuration Example (Asynchronous Data Services)
Service Planning
> In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line. Therefore, service spanning is
required. The two asynchronous data ports between NE2 and NE3 are interconnected with each other to realize the service
spanning function.
In this example, the SDH equipment is not required to jointly transmit the asynchronous data service. Hence, the overhead byte
is set to SERIAL1.
> The external clock port can also be used to realize service spanning between NE2 and NE3.
> In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active link is configured with
the asynchronous data service.
The OptiX RTN 900 supports the transmission of a channel of asynchronous data service with a maximum rate of 64 kbit/s
through a user-defined byte in the microwave frame or any byte within the range of SERIAL1-SERIAL4 in the STM-N frame. Such
a service is also called broadcast data port service.

Step 1 Select the NE from the Object Tree in the NE
Explorer. Choose Configuration > Orderwire
from the Function Tree.
Step 2 Click the Broadcast Data Port tab.
Prerequisite
B- 64k/Ethernet Protocol Converter Solution
With this solution, the
edge equipment side
and the NM side of
the edge equipment
converts the NM
message carried by
the Ethernet into the
64 kbit/s synchronous
data service in
compliance with ITU-
T G.703 by using the
64k/Ethernet protocol
converter, and the
central equipment
transparently
transmits the data
service. In this
manner, the DCN
transmission of the
edge equipment is
realized. To the edge
equipment, the
64k/Ethernet protocol
converter and the
central equipment
function as external
DCN, which realizes
the DCN
communication
between the NMS
and the gateway NE.
> The synchronous data service is fully transparently transmitted, and the transmission rate at the port is 64 kbit/s.
> The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors occur.
> The ports on the equipment comply with ITU-T G.703.
> When the orderwire signals are transmitted over a radio link, they are always transmitted through one customized overhead
byte. When the orderwire signals are transmitted over SDH fibers, they are always transmitted through the F1 byte.
> The equipment supports the transmission of the overhead bytes in the synchronous data service through the external clock
ports to realize the service spanning function.
> When the synchronous data service is transmitted over the protected radio links or optical transmission lines, the synchronous
data service is also protected.
> The equipment provides the synchronous data service ports on the SCC, cross-connect and clock board.
Synchronous Data Services
The synchronous data service is also called the F1 data service.
Example to be inserted here for ALU
solution
Configuration Example (Synchronous Data Services)
> NE1 and NE6 add or drop 64 kbit/s synchronous data services. NE2, NE3, and NE5 pass through 64 kbit/s
synchronous data services.
Service Planning
> In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line. Therefore, service spanning is
required. The two asynchronous data ports between NE2 and NE3 are interconnected with each other to realize the service
spanning function.
> The external clock port can also be used to realize service spanning between NE2 and NE3.
Procedure
Step 1 Select the NE from the Object Tree in the NE
Explorer. Choose Configuration > Orderwire from
the Function Tree.
Step 2 Click the F1 Data Port tab.
Step 3 Hold on the Ctrl key, select two data channels
from Available Data Path, and then click Prerequisite
C- E1/Ethernet Protocol Converter Solution
E1/Ethernet protocol converters are classified into four types: [point-to-point, concentrated, serially connected, and channelized].
This solution is adopted in three special scenarios: dedicated E1 , shared E1 and shared BTS service channel.

Figure 1-7 E1/Ethernet
protocol converter solution (in
the case that all the edge
equipment is
in multiple domains and the
PTP E1/Ethernet protocol
converter is used on the NM
side)
Figure 1-6
E1/Ethernet protocol
converter solution (in
the case that all the
edge equipment is
in the same domain)
A- Dedicated E1
Figure 1-8 The concentrated
E1/Ethernet protocol converter houses
several service boards. Each service board
equals a PTP E1/Ethernet protocol converter
and these protocol converters are
independent from each other.
B- Shared E1
When the edge equipment is large in scale and the
network needs to be divided into several sub-
networks, the shared E1 solution can be adopted.
With this solution, the serially connected E1/Ethernet
protocol converter on the gateway NE side in each
sub-network is used to aggregate Nx64 kbit/s
synchronous data services for DCN communication;
the channelized and concentrated E1/Ethernet
protocol converter on the NM side of the edge
equipment is used to demultiplex the Nx64 kbit/s
synchronous data services in the E1 and to convert
these services into corresponding Ethernet data,
>The sub-network at the end of the network is not involved in
the E1 aggregation. Hence, the costeffective PTP E1/Ethernet
protocol converter can be used for such a sub-network.
> In this figure, the gateway NE in each sub-network uses four
timeslots in the E1 to transmit NM messages. Specifically,
timeslots 1-4 on sub-network 3, timeslots 5-8 on sub-network
2, and timeslots 9-12 on sub-network 1 are occupied.
D- Hybrid Use Solution of Protocol Converters
1- HWECC Solution
the NM message is encapsulated in the private HWECC protocol for transmission. Hence, this solution can be adopted only when
the network is comprised of only the OptiX equipment that supports the HWECC protocol.
HWECC Protocol Stack
ITU-T G.784 defines the architecture of the ECC protocol stack
A- Basic ECC
Brief description of each layer functionality
Physical Layer
Maintains the status of the physical channel.
Port enabled state
Used overhead byte
Link status information
Provides the data communication service channels.
>> DCC channel
The SDH line port generally uses bytes D1 to D3 as DCCs.
The PDH microwave port with capacity of less than 16xE1 always uses byte
D1 as the DCC.
The PDH microwave port with capacity of not less than 16xE1 always uses
bytes D1-D3 as DCCs.
The SDH line port generally uses bytes D1 to D3 as DCCs.
The Hybrid microwave port generally uses bytes D1 to D3 as DCCs.

>> Extended channel
The extended channel uses the Ethernet between the Ethernet NM interfaces
or between the NE cascade interfaces as the communication path between
NEs.
Media Access Layer >> Establishes and maintains the MAC connection between adjacent NEs.
1- Each MAC connection includes [ the address of the opposite NE, the ID of the physical channel, the connection timer, and
other information].
2- A MAC connection exists between any two adjacent NEs that can communicate through the ECC.
3- A MAC connection is a bidirectional connection.
4 There is only one MAC connection between any two adjacent NEs that can communicate through the ECC, even if many
ports of the two NEs that support the DCC are interconnected.
5 The physical channel of the current MAC connection is also the current ECC route.
>> Provides the data communication service.
1- The MAC layer receives the data frame transferred from the physical layer. If the destination address is the address of the local
station, the MAC layer transfers the data frame to the network layer. Otherwise, the MAC layer discards the data frame.
2 The MAC layer sends the data frame from the network layer. If the destination address of the data frame has a MAC connection,
the MAC layer sends the data frame to the corresponding physical channel in the physical layer through the MAC connection.
Otherwise, the MAC layer discards the data frame.
Network Layer
Providing the route addressing function for data frames and the route management function for the DCC communication network.

1- Establishes and maintains ECC routes.
Each route item includes the following information:
Address of the destination NE
Address of the transfer NE
Transfer distance (the number of passed transfer NEs)
Route priority (The priority value ranges from 1 to 7. The priority of an automatically established route is 4 by default. The system
always selects the route with the highest priority.)
Mode (0 represents the automatic route and 1 represents the manual route)

2- Provides the data communication service.
The NET layer receives the packet transferred from the MAC layer. If the destination address of the packet is the local station,
the NET layer transfers the packet to the transport layer. Otherwise, the NET layer requests the MAC layer to transfer the packet
to the transfer station according to the route item that matches the destination address in the NET layer routing table.
The NET layer sends the packet from the transport layer. The NET layer requests the MAC layer to transfer the packet to the
transfer station according to the route item that matches the destination address of the packet in the NET layer routing table.


Transport Layer
NOTE
In the HWECC protocol stack, the NE address used by each layer is the ID of the NE.
the L4 provides only the end-to-end connectionless communication service,
B- Extended ECC >> Using the network cable
>> Using the hub
Extension Mode
>> Automatic mode
the NE with the largest IP address is automatically considered as the server and other NEs are automatically considered as clients.
The NEs automatically establish TCP connections between the server and clients and also establish corresponding MAC
connections according to the TCP connections.The maximum number of NEs (including the servers and clients) for the extended
ECC in automatic mode is 4.
>> Specified mode
NEs establish TCP connections between the server and clients according to the server, clients, IDs of connecting ports, which are set
manually, and other information that is entered manually.
They then establish corresponding MAC connections according to the TCP connections.a server can be connected to up to seven
clients. When the accessed NEs are more than seven, the multi level extended ECC mode can be used to access more NEs.
In below example Server 1 is connected to seven clients, namely, Client 11-Client 17.
Meanwhile, Client 17 functions as Server 2 and is connected to seven clients, namely, Client 21-Client 27. When the multi level
extended ECC is used, the IDs of the connected ports in the extended ECCs cannot be the same.

HWECC Availability
Relation with Other Features
>> The HWECC protocol stack of NEs can communicate with the IP protocol stack of IP over DCC.
>> The HWECC protocol stack of NEs can communicate with the OSI protocol stack in the same area on the L1 layer.
>> The HWECC protocol stack of NEs can communicate with the IP protocol stack of the inband DCN.

>> If DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used with the third-party
equipment to form a network, it is recommended that you adopt the HWECC protocol to manage the OptiX equipment.

>> If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX
equipment is used with third-party equipment to form a network, it is recommended that you adopt the HWECC protocol to
manage the OptiX equipment.

>> If the protocol manager is used to transparently transmit NM messages, it is recommended that you adopt the HWECC
protocol to manage the OptiX equipment.
Establishing ECC Routes
The HWECC solution adopts the OSPF to establish ECC routes. In this
context, the shortest path refers to the path with minimum number of stations.
1. The physical layer of an NE maintains the status information of the DCC to which each line port corresponds.
2. The MAC layer of the NE establishes the MAC connection to the adjacent NE. The steps are as follows:
(a) The NE broadcasts the connection request frame (MAC_REQ) to the adjacent NE in a periodical manner.
(b) On receiving the MAC_REQ, the adjacent NE returns the connection response frame (MAC_RSP).
(c) If the MAC_RSP is received within the specified time, the NE establishes a MAC connection to the adjacent

3. The NET layer of the NE establishes the NET layer routing table. The steps are as follows:
(1) According to the status of the MAC connection, the NE establishes an initial NET layer routing table.
(2) The NE broadcasts its routing table to the adjacent NE in a periodical manner through the routing response
message.
(3) The adjacent NE refreshes its NET layer routing table according to the received routing response message
and the shortest path first algorithm.
(4) At the next route broadcasting time, the NE broadcasts its current NET layer routing table to the adjacent.


Exercise
Describe in below network
How the ECC routes are
Established , start from NE1.
About Dijkstra's Algorithm to discover the shortest path :-
A
B
C
D
E
F
H
G
50
10 50
10
40
20
90
30
20
20
10
20
80
Packet Transfer
1-The NMS transfers application layer messages to the gateway NE through the TCP connection between them.
2. The gateway NE extracts the messages from the TCP/IP protocol stack and reports the messages to the application layer.
3. The application layer of the gateway NE queries the address of the destination NE in the messages. If the address of the
destination NE is not that of the local station, the gateway NE queries the core routing table of the application layer according to
the address of the destination NE to obtain the corresponding route and the communication protocol stack of the transfer NE.
4. On receiving the packet that encapsulates the messages, the NET layer of the transfer NE queries the address of the
destination NE of the packet. If the address of the destination NE is not that of the local station, the transfer NE queries the
NET layer routing table according to the address of the destination NE to obtain the corresponding route and then transfers
the packet.
5. After receiving the packet, the NET layer of the destination NE reports the packet to the application layer through the L4
because the address of the destination NE of the packet is the same as the address of the local station. The application layer
functions according to the message sent from the NMS.

The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Each route item
includes the following:
> ID of the destination NE
> Address of the transfer NE
> Communication protocol stack of the transfer NE
> Transfer distance


PIN usage
1 TX(+)
2 TX(-)
3 RX(+)
4 Ground (serial)
5 RX (serial)
6 RX(-)
7 ND
8 TX (serial)
NMS/COM
Note-
> The NMS/COM interface and the NE interface are equivalent to two ports on a hub. Thus, ensure that no external
Ethernet link is configured between the two interfaces during the networking process. Otherwise, an Ethernet loop is formed.
As a result, a network storm is generated, wherein repeated resets are performed on the NEs.

> When the OptiX RTN 950 is configured with two system control boards, the NM interfaces and NE cascade interfaces of
the system control boards are equivalent to four ports on a hub. To avoid network storms, you need to use the NM interface
and NE cascade interface of the working system control board, if possible.

IP over DCC Solution
With the IP over DCC solution, the NM message is encapsulated in the standard IP protocol stack for transmission. Hence, the
NM message can be transmitted only if the equipment supports the IP protocol stack.
Physical Layer
>> DCC channel
If the network is only comprised of the OptiX equipment, it is recommended that you use bytes D1 to D3 in SDH frames as DCCs.
If the OptiX equipment is connected to the third-party equipment by using the SDH line, it is recommended that you use the DCC
bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs.
In the PDH microwave frame, one or three DCC bytes in the frame can always be used as DCCs.
In the Hybrid microwave frame, three DCC bytes in the frame can always be used as DCCs.

>> Ethernet physical channel
The NE provides the Ethernet physical channel through the Ethernet NM port or the NE cascade port.
Data Link Layer
the NE applies the PPP protocol to realize the data link layer function.
Network Layer
The NE applies the IP and the matching ARP and ICMP to realize the network layer functions.
Routing Protocols
NE support OSPF and RIP

The OSPF protocol divides an autonomous system (AS) into several areas. Route nodes exchange routing information in an area.
The route nodes at the edge of an area make summary and exchange information with the routers in other areas. Areas are
identified by area IDs. The area ID has the same format as the IP address.

Currently, the OSPF protocol of the OptiX equipment supports only the routes within an area and does not support the routes
between areas. Hence, the gateway NE and all its managed nongateway NEs must be in the same OSPF area. By default, the
microwave or line port of the OptiX equipment is enabled with the OSPF protocol but the Ethernet port is not enabled with the
OSPF protocol. Hence, to form a network through the Ethernet port, you need to modify the OSPF setting of the NE.

Use the command cm-set-ospf-ineterface:lan,enable;

In addition to the dynamic routing protocol, the NE supports static routes. Static routes are manually configured routes.

Proxy ARP
It is used as supplement to routing table ; The proxy ARP enables the NEs in the same network segment but different domains to
Communicate with each other. Using below steps :-

1- source NE sends the ARP broadcast packet to address the route to the destination NE.

2- The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table
contains the destination address that the ARP broadcast packet looks for, the NE returns a ARP spoofing packet, which enables
the Source NE to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the
destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function
enabled and then forwarded to the destination NE.
Example
1- The OptiX transmission network uses the IP over DCC solution and all the NEs are in the same OSPF domain. Hence,
routes exist between NE1, NE2, and NE3.

2- The OSPF protocol diffuses the local route of the NE in the OSPF domain. Hence, NE1 owns the routes that are owned by
NE4, and NE4 owns the routes that are owned by the third-party NMS.

3- static route must be configured for all nodes between NE1 and NE3 , one NE3
[ ip route 130.9.0.4 255.255.255.255 130.9.0.3 , ip route 130.9.0.100 255.255.255.255 130.9.0.1 ]

4- The IP addresses of the third-party NMS and NE4 are in the 130.9.0.0 network segment Hence, when communicating with
NE4, the third-party NMS broadcasts the ARP packet that addresses routes to NE4. The routing table contains the routes to
NE4, so NE1 with the ARP function enabled sends an ARP spoofing packet to the third-party NMS so that the third-party NMS
sends the packet to NE1 instead of NE4. Then, NE1-NE3 forward the packet according to the routing table. Finally, the packet
arrives at NE4. In the same manner, the packet can be transmitted from NE4 to the third-party NMS over the proper routes.

If the third-party NMS owns a static route to NE4 (the IP address of the gateway is the IP address of NE1) and NE4 owns a
route to the third-party NMS (the IP address of the gateway is the IP address of NE3), NE1 and NE3 do not require the proxy
ARP function.
NMS Access Modes In the IP over DCC solution, there are two modes
A- Gateway Access Mode
In the gateway access mode, the NMS accesses a non-gateway NE through the gateway NE. The gateway NE queries the core
routing table of the application layer according to the ID of the NE to be accessed to obtain the corresponding route.
The core routing table refers to the transport layer routing tables of all communication protocol stacks. Each route item includes the
following:
> ID of the destination NE
> Address of the transfer NE
> Communication protocol stack of the transfer NE
> Transfer distance
B -Direct access mode

the NMS accesses an NE as the gateway NE. All transfer NEs on the access path query the IP routing table of the network layer
according to the IP address of the NE to be accessed to obtain the corresponding route.
The IP routing table is based on routing protocols. It includes both dynamic routes generated by routing protocols and static
routes configured by operators. Each route item includes the following:
> Destination IP address
> Subnet Mask
> IP address of the gateway
> Interface
When the NMS applies the direct access mode to access an NE, there must be an IP route between the NMS and the NE.
In the IP over DCC solution, theoretically, the NMS can access any NE using the direct access mode, that is, it can consider any
NE as the gateway NE. To improve the communication efficiency, there should not be too many NEs that are accessed in the
direct access mode in a network.
Availability
Configuration process
Select the NE from the Object Tree in the NE Explorer. Choose
Communication > DCC
Management from the Function Tree.

Click the DCC Rate Configuration tab.
Creating Static IP Routes
Step 1 Select the NE from the Object Tree in the NE Explorer.
Choose Communication > IP Protocol
Stack Management from the Function Tree.
Step 2 Click the IP Route Management tab.
DCC Transparent Transmission Solution
Availability
Configuration steps
Step 1 Select the NE from the Object Tree in the NE
Explorer. Choose Communication > DCC
Management from the Function Tree.
Step 2 Click the DCC Transparent Transmission
Management tab.
Step 3 Click Create.
DCC Transparent Transmission Through the External Clock Interface Solution
Direct Access Mode
Indirect Access Mode
Availability
Configuration
www.huawei.com
Thank you