V100R001C00
Feature Description
Issue 01
Date 2014-04-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document describes the main features of the OptiX RTN 360 microwave transmission
system. It provides readers a comprehensive knowledge of the functionality, principles,
configuration, and maintenance of the product features.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 01 (2014-04-30)
This issue is the first release for the product version V100R001C00.
Contents
3 L2 DCN Solution.........................................................................................................................21
3.1 Introduction..................................................................................................................................................................22
3.2 Reference Standards and Protocols..............................................................................................................................25
3.3 Specifications................................................................................................................................................................25
3.4 Feature Updates............................................................................................................................................................26
3.5 Feature Dependencies and Limitations.........................................................................................................................26
3.6 Planning Guidelines......................................................................................................................................................27
3.7 Related Alarms.............................................................................................................................................................28
4 TDD................................................................................................................................................29
4.1 Introduction..................................................................................................................................................................30
4.2 Specifications................................................................................................................................................................32
4.3 Feature Updates............................................................................................................................................................32
4.4 Feature Dependencies and Limitations.........................................................................................................................32
4.5 Planning Guidelines......................................................................................................................................................32
4.6 Related Alarms.............................................................................................................................................................33
6 QinQ...............................................................................................................................................39
6.1 Introduction..................................................................................................................................................................40
6.2 Reference Standards and Protocols..............................................................................................................................43
6.3 Specifications................................................................................................................................................................43
6.4 Feature Updates............................................................................................................................................................44
6.5 Feature Dependencies and Limitations.........................................................................................................................44
6.6 Planning Guidelines......................................................................................................................................................44
6.7 Related Alarms.............................................................................................................................................................44
7 QoS.................................................................................................................................................45
7.1 Introduction..................................................................................................................................................................46
7.2 Reference Standards and Protocols..............................................................................................................................53
7.3 Specifications................................................................................................................................................................54
7.4 Feature Updates............................................................................................................................................................57
7.5 Feature Dependencies and Limitations.........................................................................................................................57
7.6 Planning Guidelines......................................................................................................................................................58
7.7 Related Alarms and Events...........................................................................................................................................60
8 ETH OAM.....................................................................................................................................62
8.1 Introduction..................................................................................................................................................................63
8.2 Reference Standards and Protocols..............................................................................................................................68
8.3 Specifications................................................................................................................................................................69
8.4 Feature Updates............................................................................................................................................................70
8.5 Feature Dependencies and Limitations.........................................................................................................................70
8.6 Planning Guidelines......................................................................................................................................................71
8.7 Related Alarms.............................................................................................................................................................72
A Glossary........................................................................................................................................81
1 Introduction to DCN
Through the data communication network (DCN), the NMS communicates with transmission
NEs to manage and maintain them.
DCN Composition
The DCN contains two types of node: NMS and NE. The DCN between the NMS and NEs are
called external DCN. The DCN among NEs are called internal DCN. The external DCN consists
of data communication devices, such as Ethernet switches and routers. The internal DCN consists
of NEs that are connected using DCN channels. Unless otherwise specified, the DCN mentioned
in this document refers to internal DCN.
DCN Channel
DCN channels fall into two types: outband DCN channel and inband DCN channel.
l Oubtband DCN channels do not occupy any service bandwidth. The RTN 300 supports
two types of outband DCN channel:
D1 to D3 bytes in microwave frames
Channels over NMS ports
l Inband DCN channels occupy some service bandwidth. The RTN 300 supports two types
of inband DCN channel:
Some Ethernet service bandwidth of microwave links
Some Ethernet service bandwidth of Ethernet links
DCN Solutions
The RTN 300 provides the following DCN solutions:
l IP DCN solution
In the IP DCN solution, network management messages are encapsulated into IP packets.
NEs forward the IP packets based on the IP addresses contained in them. This solution
supports a maximum of 200 NEs and ensures high network stability. This solution is the
default and preferred solution.
l L2 DCN solution
In the L2 DCN solution, network management messages are encapsulated into IP packets,
which are carried by Ethernet frames. NEs forward the Ethernet frames based on the MAC
addresses contained in them. This solution supports a maximum of 1024 NEs. However,
this solution has the risk of broadcast packet flooding and provides poor network stability.
The RTN 300 also supports the HWECC solution, which is eliminated gradually.
gateway NE. An NE located inside a DCN can also function as a gateway NE. The NEs between
the NMS and the gateway NE inside a DCN forward DCN packets at L2 or L3.
Non-gateway NE: The application layer of the NMS communications with the application layer
of a non-gateway NE through the application layer of a gateway NE. The NEs between the
gateway NE and non-gateway NE forward DCN packets at L2 or L3.
DCN Flags
An NE on the DCN must be configured with two DCN flags: NE ID and NE IP address.
2 IP DCN Solution
In the IP DCN solution, NEs use unified DCN channels to transmit TCP/IP protocol data, which
enables the NMS to manage the NEs.
2.1 Introduction
This section describes the basic knowledge about IP DCN.
2.3 Specifications
This section provides the IP data communication network (DCN) specifications that OptiX RTN
360 supports.
2.1 Introduction
This section describes the basic knowledge about IP DCN.
l The physical layer provides data transmission channels for data terminal equipment. The
OptiX RTN 300 provides the following DCN channels:
NMS port: all the bandwidth at the NMS port
DCC channel: three Huawei-defined DCC bytes in a microwave frame at a microwave
port
Inband DCN: a portion of Ethernet service bandwidth at an Ethernet or a microwave
port
l The data link layer ensures reliable data transmission across physical links. DCCs and
inband DCNs use the PPP protocol to set up data links. Therefore, IP addresses of adjacent
NEs do not need to be in the same IP network segment.
l The network layer specifies the network layer address for a network entity and provides
transferring and addressing functions. NEs implement network layer functions using the
IP protocol. The routes used for IP transferring can be dynamic routes generated running
the OSPF protocol, manually configured static routes, or direct routes discovered by
running link layer protocols. The OptiX RTN 300 provides various OSPF features. For
details, see the 2.3 Specifications.
l The transport layer provides end-to-end communication services for the upper layer. NEs
support the TCP/UDP protocol.
1. The NMS transfers application layer packets to the gateway NE through the TCP
connection.
2. The gateway NE extracts the packets from the TCP/IP protocol stack and delivers them to
the application layer.
3. The application layer of the gateway NE queries the destination NE address of the packets.
If the address does not belong to the gateway NE, the gateway NE queries the core routing
table of the application layer. The gateway NE obtains the route to the destination NE and
the communication protocol stack of the transit NE according to the destination NE address.
Because the transit NE uses the IP protocol stack, the gateway NE transfers the packets to
the transit NE through the IP protocol stack.
4. The network layer of the transit NE queries the destination IP address of the packets. If the
address does not belong to the transit NE, the transit NE queries the IP routing table to
obtain the route to the destination NE and then transfers the packets.
5. The network layer of the destination NE passes the packets to its application layer through
the transport layer because the destination IP address of the packets is the same as the IP
address of the destination NE. The application layer then processes the packets.
The original gateway NE acts as an ordinary transit NE, and packets are transferred at the network
layer.
The third-party L2 network may be located between the network consisting of OptiX RTN 300s
and the NMS or between two networks consisting of OptiX RTN 300s.
When the third-party L2 network is located between the network consisting of OptiX RTN 300s
and the NMS, the L2 network transmits Ethernet services and DCN packets between the NMS
and the gateway NE. In this instance, the NMS uses the LAN switch to remove the VLAN ID
carried by NMS messages and the access control function is enabled on the Ethernet port. After
the access control function is enabled:
l The Ethernet port functions as an Ethernet NMS port on the gateway NE.
l The IP address of the Ethernet port must be in the same network segment as that of the
NMS IP address and in a network segment different from that of NE IP addresses.
l The NMS communicates with the gateway NE based on the IP address of the Ethernet port.
When the third-party L2 network is located between two networks consisting of OptiX RTN
300s, NMS messages are encapsulated as L2 services for transmission. In this instance, the access
control function is enabled on the Ethernet ports of the two networks for connecting to the third-
party L2 network and their IP addresses are in the same network segment.
The third-party L2 network creates a dedicated L2VPN service for the DCN packets carrying a
specific inband DCN VLAN ID.
2.3 Specifications
This section provides the IP data communication network (DCN) specifications that OptiX RTN
360 supports.
Item Specifications
Item Specifications
Maximum number of 64
nodes in an area
Version Description
Item Description
NOTE
In the planning guidelines, OptiX equipment refers to Huawei OptiX transmission equipment that supports
IP DCN.
2.6.2 Planning Guidelines for NE IP Addresses and Routes in Typical Network Topologies
If operators do not have special requirements for NE IP addresses, you can set IP addresses to
simplify route settings.
On the OptiX gateway NE, configure a static route to the third-party NMS and enable
static route flooding.
On the OptiX NE connected to the third-party gateway NE, configure a static route to
the third-party gateway NE and enable static route flooding.
If the third-party NMS and the third-party gateway NE are on the same network segment,
enable proxy Address Resolution Protocol (ARP) on the OptiX NE connected to the
third-party gateway NE. If the OptiX gateway NE is also on the same network segment,
enable proxy ARP on the OptiX gateway NE.
l If a network has both OptiX and third-party equipment and they transmit OSPF packets to
each other, configure only a single OSPF area as follows:
Plan the OptiX NE closest to the external DCN as a gateway NE and the other OptiX
NEs as non-gateway NEs.
Configure the area ID, packet timer, area type, and router ID for each OptiX NE in
compliance with the requirements for third-party NEs.
On the NE connected to the external DCN, configure a static route to Huawei NMS and
a static route to the third-party NMS, and enable static route flooding.
l If a network has only OptiX NEs, the IP address of the gateway NE and the IP addresses
of non-gateway NEs must be on different network segments.
l If a network has both OptiX and third-party NEs, the IP addresses of the OptiX gateway
NE, the IP addresses of the OptiX non-gateway NEs not connected to a third-party NE, and
the IP address of the third-party gateway NE must be on different network segments. The
IP addresses of the OptiX non-gateway NEs connected to a third-party NE and the third-
party gateway NE must be on the same network segment.
Guidelines for planning NE IP addresses and routes in typical network topologies are described
in the following section.
Network Comprising Only OptiX NEs, with the IP Addresses of the NMS and
Gateway NE on the Same Network Segment
Figure 2-1 illustrates a network comprising only OptiX NEs. On the network, the IP addresses
of the network management system (NMS) and gateway NE are on the same network segment.
Figure 2-1 Diagram for planning NE IP addresses and routes (a network comprising only OptiX
NEs, with the IP addresses of the NMS and gateway NE on the same network segment)
NMS NE 1 NE 2 NE 3 NE 4
130.9.0.100
130.9.0.1 129.9.0.2 129.9.0.3 129.9.0.4
In Figure 2-1:
l The IP address of the gateway NE (NE 1) belongs to the network segment 130.9.0.0, and
the IP addresses of the non-gateway NEs belong to the segment 129.9.0.0.
l If the NMS requests direct access to a non-gateway NE (NE 2 or NE 3), configure a static
route from the NMS to the network segment 129.9.0.0, or set the IP address of NE 1
(130.9.0.1) as the default gateway.
Network Comprising Only OptiX NEs, with the IP Addresses of the NMS and
Gateway NE on Different Network Segments
Figure 2-2 illustrates a network comprising only OptiX NEs. On the network, the IP addresses
of the NMS and gateway NE are on different network segments.
Figure 2-2 Diagram for planning NE IP addresses and routes (a network comprising only OptiX
NEs, with the IP addresses of the NMS and gateway NE on different network segments)
NMS
10.2.0.200
RT 1
10.2.0.100
NE 1 NE 2 NE 3 NE 4
RT 2
130.9.0.100 130.9.0.1 129.9.0.2 129.9.0.3 129.9.0.4
In Figure 2-2:
l The IP address of the gateway NE (NE 1) belongs to the network segment 130.9.0.0, and
the IP addresses of the non-gateway NEs belong to the segment 129.9.0.0.
l On NE 1, configure a static route to the NMS (10.2.0.100), or set the IP address of RT 2
(130.9.0.100) as the default gateway.
l On the NMS, configure a static route to NE 1 (130.9.0.1), or set the IP address of RT 1
(10.2.0.200) as the default gateway.
l If the NMS requests direct access to a non-gateway NE (NE 2, NE 3, or NE 4), perform
the following configurations in addition to the preceding ones:
On NE 1, enable Open Shortest Path First (OSPF) route flooding, so that NE 2, NE 3,
and NE 4 can obtain routes to the NMS.
On the NMS, configure a static route to the network segment 129.9.0.0. Skip this
operation if the default gateway has been configured.
Configure routes from RT 1 and RT 2 to the network segment 129.9.0.0.
Network Comprising OptiX and Third-Party NEs, with the IP Addresses of the
Third-Party NMS and OptiX Gateway NE on the Same Network Segment (No
OSPF Interaction)
Figure 2-3 illustrates a network comprising OptiX and third-party NEs. On the network, the IP
addresses of the third-party NMS and OptiX gateway NE are on the same network segment, and
the OptiX NEs do not use OSPF to communicate with the third-party NEs.
Figure 2-3 Diagram for planning NE IP addresses and routes (a network comprising OptiX and
third-party NEs, with the IP addresses of the third-party NMS and OptiX gateway NE on the
same network segment)
NMS
130.9.0.100 External
DCN
Third-party
NMS NE 5 NE 6
NE 1 NE 2 NE 3 NE 4
130.9.0.200
131.9.0.5 131.9.0.6
130.9.0.1 129.9.0.2 129.9.0.3 131.9.0.4
Compared with the scenario where a network comprises only OptiX NEs and the IP addresses
of the NMS and gateway NE are on the same network segment, planning NE IP addresses and
routes for this scenario has the following characteristics:
l The IP addresses of the gateway NE (NE 1), non-gateway NEs (NE 2 and NE 3, which do
not connect to a third-party NE), and third-party gateway NE (NE 5) are on the network
segments 130.9.0.0, 129.9.0.0, and 131.9.0.0, respectively.
l The IP addresses of NE 4, a non-gateway NE connected to a third-party NE, and NE 5 are
on the same network segment.
l On the third-party NMS, configure a static route to the third-party gateway NE (131.9.0.5),
or set the IP address of NE 1 (130.9.0.1) as the default gateway.
l On NE 5, configure a static route to the third-party NMS (130.9.0.200), or set the IP address
of NE 4 (131.9.0.4) as the default gateway.
Network Comprising OptiX and Third-Party NEs, with the IP Addresses of the
Third-Party NMS and OptiX Gateway NE on Different Network Segments (No
OSPF Interaction)
Figure 2-4 illustrates a network comprising OptiX and third-party NEs. On the network, the IP
addresses of the third-party NMS and OptiX gateway NE are on different network segments,
and the OptiX NEs do not use OSPF to communicate with the third-party NEs.
Figure 2-4 Diagram for planning NE IP addresses and routes (a network comprising OptiX and
third-party NEs, with the IP addresses of the third-party NMS and OptiX gateway NE on different
network segments)
Third-party
NMS 10.2.0.200
RT 1
10.2.0.100
130.9.0.100
RT 2 NE 5 NE 6
NE 1 NE 2 NE 3 NE 4
130.9.0.200
Compared with the scenario where a network comprises only OptiX NEs and the IP addresses
of the NMS and gateway NE are on the same network segment, planning NE IP addresses and
routes for this scenario has the following characteristics:
l The IP addresses of the gateway NE (NE 1), non-gateway NEs (NE 2 and NE 3, which do
not connect to a third-party NE), and third-party gateway NE (NE 5) are on the network
segments 130.9.0.0, 129.9.0.0, and 131.9.0.0, respectively.
l The IP addresses of NE 4, a non-gateway NE connected to a third-party NE, and NE 5 are
on the same network segment.
l On NE 1, configure a static route to the third-party NMS (10.2.0.100).
l On NE 1, enable OSPF route flooding, so that NE 2, NE 3, and NE 4 can obtain routes to
the third-party NMS.
l On the third-party NMS, configure a static route to the third-party gateway NE (131.9.0.5),
or set the IP address of RT 1 (10.2.0.200) as the default gateway.
l On NE 5, configure a static route to the third-party NMS (10.2.0.100), or set the IP address
of NE 4 (131.9.0.4) as the default gateway.
l Configure routes from RT 1 and RT 2 to the third-party gateway NE (131.9.0.5).
Network Comprising OptiX and Third-Party NEs, with the IP Addresses of the
Third-Party NMS and OptiX Gateway NE on Different Network Segments (with
OSPF Interaction)
In this example, the OptiX and third-party NEs in Figure 2-4 use OSPF to communicate with
each other. On the network, the IP addresses of the third-party NMS and OptiX gateway NE are
on different network segments, and each NE runs OSPF.
Compared with the scenario where a network comprises only OptiX NEs and the IP addresses
of the NMS and gateway NE are on the same network segment, planning NE IP addresses and
routes for this scenario has the following characteristics:
l The IP addresses of the gateway NE (NE 1), non-gateway NEs (NE 2 and NE 3, which do
not connect to a third-party NE), and third-party gateway NE (NE 5) are on the network
segments 130.9.0.0, 129.9.0.0, and 131.9.0.0, respectively.
l The IP addresses of NE 4, a non-gateway NE connected to a third-party NE, and NE 5 are
on the same network segment.
l On NE 1, configure a static route to the third-party NMS (10.2.0.100).
l On NE 1, enable OSPF route flooding, so that NE 2, NE 3, NE 4, and NE 5 (a third-party
NE) obtain the routes to the third-party NMS.
l On the third-party NMS, configure a static route to the third-party gateway NE (131.9.0.5),
or set the IP address of RT 1 (10.2.0.200) as the default gateway.
l Configure routes from RT 1 and RT 2 to the third-party gateway NE (131.9.0.5).
Related Alarms
l DCNSIZE_OVER
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
l NEIP_CONFUSION
The NEIP_CONFUSION is an alarm indicating an NE IP address conflict.
l SUBNET_RT_CONFLICT
The SUBNET_RT_CONFLICT is an alarm indicating a subnetwork route conflict. This
alarm occurs when the subnet route of an NMS port, that is, the IP subnet route of an NE,
covers the learned route of an OSPF subnet whose mask is longer than that of the IP subnet.
3 L2 DCN Solution
In the Layer 2 data communication network (L2 DCN) solution, Ethernet-encapsulated DCN
packets are transmitted between NEs based on L2 forwarding, enabling the NMS to manage the
NEs.
3.1 Introduction
This section describes the basic information about the Layer 2 data communication network (L2
DCN) solution.
3.3 Specifications
This section provides the L2 DCN specifications that OptiX RTN 360 supports.
3.1 Introduction
This section describes the basic information about the Layer 2 data communication network (L2
DCN) solution.
The L2 DCN solution is mainly applied to scenarios in which network management must be
implemented based on L2 forwarding. Centralized network management is achieved, with
communication between microwave equipment within a subnet implemented through L2 DCN
and DCN communication between subnets implemented based on L3 IP forwarding.
If an OptiX RTN 300 constructs a network with third-party equipment that supports L2 DCN,
the OptiX RTN 300 can use the L2 DCN to communicate with the third-party equipment, which
simplifies network configurations and eliminates the need for extra static routes.
l Layer 1 of the protocol stack is the physical layer, which provides physical channels for
transmitting data between data terminal equipment. OptiX RTN 300 provides the following
DCN channels:
NMS port: transmitting DCN packets using all of its bandwidth
DCC channel on a microwave port: transmitting DCN packets using the three self-
defined DCC bytes in a microwave frame
Inband DCN channel on an Ethernet or microwave port: transmitting DCN packets using
part of Ethernet bandwidth
l Layer 2 is the data link layer, which provides reliable data transmission to the physical link
layer. The L2 DCN solution implements the functions of the data link layer based on MAC
address learning and forwarding.
l Layer 3 is the network layer, which performs addressing and packet forwarding. NEs run
the IP protocol to provide functions of the network layer.
If the NMS and the NE are in the same network segment, the process of DCN packet forwarding
is as follows:
1. The NMS obtains the MAC address of the destination NE using the ARP.
2. Intermediate NEs on the link between the NMS and the destination NE forward DCN
packets to the destination MAC address based on L2 forwarding.
3. When the destination NE returns DCN packets, the NE obtains the MAC address of the
NMS using the ARP.
4. Intermediate NEs on the link between the NMS and the destination NE forward DCN
packets to the destination MAC address based on L2 forwarding.
When the NMS and the NE are in the different network segments, the process of DCN packet
forwarding is as follows:
3.3 Specifications
This section provides the L2 DCN specifications that OptiX RTN 360 supports.
Table 3-1 Specifications of the L2 DCN solution that Table 3-1 supports
Item Specifications
Item Specifications
Maximum frame length 1522 bytes (maximum valid payloads: 1500 bytes)
supported in L2 DCN
forwarding
Type of entries in a MAC Dynamic entries are supported. Static entries are not supported.
address table
Transmission scheme of l Third-party DCN packets that are not identified by VLAN IDs
third-party DCN packets are forwarded by the system control unit and transmitted over
the DCN channel.
l Third-party DCN packets that are identified by VLAN IDs are
forwarded by the Ethernet service switching unit and
transmitted over the service channel.
Version Description
broadcast storms and further prevent OptiX RTN 360 NEs from being unreachable to the
NMS.
l When being loaded with software, NEs on an L2 DCN network can be loaded only one by
one instead of in diffusion mode.
l CPRI ports cannot transmit DCN packets. Microwave ports for transmitting CPRI services
do not support inband DCN. DCN packets can be transmitted only through DCCs.
l When CPRI services are transmitted, the P&E port always functions as the Ethernet NMS
port.
If the inband DCN is used for the L2 DCN solution, plan the inband DCN according to the
following principles:
l The NEs on the same subnet have the same management VLAN ID.
l The management VLAN ID used for the inband DCN is different from the VLAN IDs
carried by Ethernet services.
l The inband DCN bandwidth depends on the number of NEs on the subnet.
NOTE
Enable the STP/RSTP for a switch that is connected to the L2 DCN. Otherwise, loops may be generated
on an L2 DCN, causing broadcast storms and NEs to be unreachable to the NMS.
Related Alarms
l DCNSIZE_OVER
The DCNSIZE_OVER alarm indicates that the DCN network is oversized. The gateway
NE reports the DCNSIZE_OVER alarm after detecting that the number of nodes (NEs,
NMS servers, and NMS clients on a network segment) on an L2 DCN subnet is larger than
30. To clear this alarm, it is recommended that you further divide the DCN network,
ensuring that each subnet consists of less than 30 nodes.
l NEIP_CONFUSION
The NEIP_CONFUSION is an alarm indicating an NE IP address conflict.
4 TDD
4.1 Introduction
This section introduces time division duplex (TDD).
4.2 Specifications
This section lists the TDD specifications that OptiX RTN 360 supports.
4.1 Introduction
This section introduces time division duplex (TDD).
FDD vs TDD
The duplex technologies in digital communication include frequency division duplex (FDD) and
TDD.
FDD
In FDD mode, two independent symmetric channels are required; one transmits uplink services
and the other transmits downlink services. A hop of microwave link includes a TX high site and
a TX low site.
TDD
In TDD mode, a device alternately transmits and receives services using the same channel. The
devices at the two ends of a microwave link hop are not defined as TX high and TX low sites.
TDD Characteristics
l Frequency spectrum resources are not required in pairs.
OptiX RTN 360 uses frequency spectrum resources that do not require a license. Only one
frequency is required for a microwave link because both uplink and downlink services are
transmitted over the same channel.
l The devices at the two ends of a microwave link hop are not defined as TX high and TX
low sites.
One microwave link uses only one frequency. Therefore, the devices at the two ends of a
microwave link hop are not defined as TX high and TX low sites.
l Asymmetric transmission is allowed.
If a microwave link carries services with high downlink traffic (such as video services),
you can adjust the TDD timeslot ratio to implement asymmetric transmission of uplink and
downlink services. This ensures proper channel resource usage and service quality.
l The timeslot ratio on the slave device matches that on the master device. For example, if
the timeslot ratio on the master device is 3:1, the timeslot ratio on the slave device is 1:3.
l The slave device traces the clock of the master device through the microwave link.
l Automatic frequency selection is always initiated by the master device.
TDD Principles
Devices transmit and receive services through different timeslots, which is controlled by
switches.
1. In the transmit timeslot, the master device transmits services to the channel, and the slave
device receives the services from the channel.
2. In the interval between the transmit timeslot and receive timeslot, the master device turns
off the TX switch and turns on the RX switch. Meanwhile, the slave device turns off the
RX switch and turns on the TX switch.
3. In the receive timeslot, the slave device transmits services to the channel, and the master
device receives the services from the channel.
The service transmission duration ratio between the master and slave devices is the TDD timeslot
ratio. The default TDD timeslot ratio on the master device is 3:1.
4.2 Specifications
This section lists the TDD specifications that OptiX RTN 360 supports.
Item Specifications
Version Description
The TDD timeslot ratio can be configured only on the master device. The TDD timeslot ratio
on the slave device automatically matches that on the master device.
l Determine the master and slave devices on a hop of microwave link. Configure the device
on the macro base station side as the master device.
l Configure the timeslot ratio as required by services. For services with high downlink traffic,
you can configure the timeslot ratio as 2:1 or 3:1. For services with high uplink traffic, you
can configure the timeslot ratio as 1:2 or 1:3.
Alarms
None
Interference check and dynamic frequency selection can free you from frequency planning and
improve the anti-interference capability of microwave links.
5.1 Introduction
This section introduces interference check and dynamic frequency selection.
5.2 Specifications
This section lists the interference check and dynamic frequency selection specifications that
OptiX RTN 360 supports.
5.1 Introduction
This section introduces interference check and dynamic frequency selection.
Scenarios
The network life cycle involves two important scenarios: new network construction and network
maintenance.
Solutions:
l Interference check: checks for interference on microwave links, which will result in poor
link quality.
l Dynamic frequency selection: dynamically switches to an available frequency after link
interference is identified.
1. A user mutes the slave device through the NMS. The slave device starts the timer.
2. After interference check is started, the master device scans frequencies, starting from the
lowest frequency, at a step of 200 MHz channel spacing within the entire band.
3. After the frequency scan is complete, the master device outputs results indicating whether
there is interference on any frequency in the band.
4. After the timer expires, the slave device is unmuted.
1. After the slave device generates an MW_LOF alarm, it is muted. The slave device performs
an interference check to obtain the available frequency list and meanwhile determines the
transmit frequency of the master device.
2. After the slave device is muted, the master device generates an MW_LOF alarm. The master
device then performs an interference check to obtain the available frequency list.
3. The master device switches to a new available frequency f1 and transmits services to the
slave device. The master device also attempts to receive services from the slave device at
f1.
4. After identifying the transmit frequency of the master device, the slave device switches to
the new frequency f1 to receive services and then unmutes the transmit port.
5. After the master and slave devices receive services from each other, the microwave link
recovers.
5.2 Specifications
This section lists the interference check and dynamic frequency selection specifications that
OptiX RTN 360 supports.
Table 5-1 Interference check and dynamic frequency selection specifications that OptiX RTN
360 supports
Item Specifications
Frequency scan step in interference check 200 MHz, which is the same as the channel
spacing.
Version Description
Table 5-2 Dependencies and limitations of interference check and dynamic frequency selection
Item Description
Item Description
Alarms
None
6 QinQ
6.1 Introduction
This section introduces 802.1Q in 802.1Q (QinQ).
6.3 Specifications
This section provides the QinQ specifications that OptiX RTN 360 supports.
6.1 Introduction
This section introduces 802.1Q in 802.1Q (QinQ).
Definition
QinQ is a Layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. The QinQ technology
encapsulates a private virtual local area network (VLAN) tag into a public VLAN tag. Packets
carrying two VLAN tags are transmitted on the backbone network of an operator. QinQ provides
Layer 2 virtual private network (VPN) tunnels.
Purpose
Using QinQ based on VLAN stacking and nesting, services are differentiated by two VLAN
tags in data packets, which increases the number of available VLAN IDs. The inner VLAN tag
is a customer VLAN (C-VLAN) tag and the outer VLAN is a supplier VLAN (S-VLAN) tag.
l The number of available VLAN IDs can reach 4094 x 4094. This meets the increasing
requirements for VLAN IDs.
l Customers and operators can plan VLAN resources independently and flexibly. Network
configuration and maintenance are simplified.
l A cheaper and easier-to-implement Layer 2 VPN solution can be provided based on the
QinQ technology as compared with MPLS.
l Ethernet services can be extended from local area networks (LANs) to wide area networks
(WANs).
Frame Format
To identify S-VLANs carried in Ethernet packets, QinQ defines a C-TAG and an S-TAG based
on the tagged frame format specified in IEEE 802.1Q.
The default TPID of an S-TAG is 0x88A8 and the TPID can be modified according to the
requirement. In addition, a field indicating the S-TAG frame priority is added.
Before being transmitted from a user network to an operator network, Ethernet packets may be
untagged frames or tagged frames. When the Ethernet packets are transmitted within the operator
network, they carry only S-TAGs or a combination of C-TAGs and S-TAGs.
Basic Principle
When Ethernet packets are transmitted from a user network to an operator network, S-TAGs are
added to the packets based on PORT or PORT+C-VLAN and then these packets are forwarded
based on S-VLAN tags (carried by E-Line services) or S-VLAN tags and destination MAC
addresses (carried by E-LAN services). Swapping of S-VLAN tags is allowed when E-Line
services are created to carry Ethernet packets.
The Ethernet packets are transmitted to the user network from the operator network after their
S-VLAN tags are removed.
IEEE 802.1ad: Virtual Bridged Local Area Networks Amendment 4: Provider Bridges
6.3 Specifications
This section provides the QinQ specifications that OptiX RTN 360 supports.
Item Specifications
Setting of the QinQ type field Supported, with the default value being
0x88A8
QinQ operation type (QinQ-based E-Line Adding S-VLAN tags (from a UNI to an NNI)
services) Stripping S-VLAN tags (from an NNI to a
UNI)
Swapping S-VLAN tags (from an UNI to an
UNI)
QinQ operation type (802.1ad bridge-based Adding S-VLAN tags based on PORT (UNI
E-LAN services) port)
Adding S-VLAN tags based on PORT+C-
VLAN (UNI port)
Mounting ports based on PORT+S-VLAN
(NNI port)
Version Description
None
l Plan S-VLANs and QinQ service type (E-Line or E-LAN) based on service requirements.
l Set the same QinQ type field for the ports at both ends of a QinQ link (transmitting Ethernet
packets with S-VLAN IDs). The value 0x88A8 is recommended.
7 QoS
This section describes quality of service (QoS). QoS provides different levels of service quality
in certain aspects of services as required, such as bandwidth, delay, jitter, and packet loss ratio.
This ensures that the request and response of a user or application reaches an expected quality
level.
7.1 Introduction
This section introduces quality of service (QoS).
7.3 Specifications
This section lists the quality of service (QoS) specifications that OptiX RTN 360 supports.
7.1 Introduction
This section introduces quality of service (QoS).
Definition
QoS provides different levels of service quality in certain aspects of services as required, such
as bandwidth, delay, jitter, and packet loss ratio.
Purpose
QoS provides guaranteed bandwidth for important services, minimizes delay and jitter, and
properly allocates and monitors network resources.
The DS interior node performs traffic control based on packets' PHBs and forwards the packets
to the next-hop DS boundary node.
In the ingress direction, OptiX RTN 360 maps the incoming packets to different PHBs based on
the CoS trusted by the ingress port. If some packets do not carry the CoS trusted by the port,
OptiX RTN 360 maps them to the best effort (BE) queue.
The following figure shows the default mappings from priorities of ingress packets to PHBs.
In the egress direction, OptiX RTN 360 modifies the CoS information carried by packets based
on the mapping between the PHB and the trusted CoS.
The following figure shows the default mappings from PHBs to priorities of egress packets.
Simple traffic classification maps packets carrying different CoSs to specific PHBs.
CAR
Committed access rate (CAR) is a traffic policing technology. CAR assesses the traffic rate in
a certain period (long term or short term). CAR assigns a high priority to traffic that does not
exceed the rate limit and drops or downgrades traffic that exceeds the rate limit. In this manner,
CAR limits the traffic entering a transmission network.
The following CAR operations are performed for traffic policing:
l Packets whose rate is lower than or equal to the committed information rate (CIR) are
colored green.
l Packets whose rate is higher than the peak information rate (PIR) are colored red.
l Packets whose rate is higher than the CIR but is lower than or equal to the PIR are colored
yellow.
l If the traffic rate in a certain period is lower than or equal to the CIR, traffic bursts are
allowed. The maximum traffic of burst packets is determined by the committed burst size
(CBS).
l If the traffic rate in a certain period is higher than the CIR but is lower than or equal to the
PIR, traffic bursts are allowed. The maximum burst size is equal to the peak burst size
(PBS).
l Green packets pass traffic policing.
l Red packets are dropped.
l Yellow packets pass traffic policing but are re-marked. To be specific, yellow packets are
re-colored green or mapped to a newly specified PHB.
The following figure shows how traffic changes after CAR processing.
Red packets are directly dropped. Green packets and yellow packets pass traffic policing, and
yellow packets are re-marked.
Congestion Avoidance
Congestion avoidance is a traffic control mechanism that monitors the usage of network
resources, such as queues or memory buffers, and drops packets under overload or congestion.
OptiX RTN 360 supports two congestion avoidance algorithms: tail drop and weighted random
early detection (WRED).
Tail Drop
With tail drop enabled, all newly arriving packets are dropped if the buffer queue is filled to its
maximum capacity.
WRED
With WRED enabled, yellow and red packets are preferentially dropped and green packets are
always transmitted first in the case of network congestion.
Queue Scheduling
OptiX RTN 360 supports three queue scheduling algorithms: strict priority (SP), weighted round
robin (WRR), and SP+WRR.
SP
During SP scheduling, packets are transmitted in descending order of queue priorities. Packets
in a lower-priority queue can be transmitted only after a higher-priority queue becomes empty.
Therefore, important services are placed in higher-priority queues and are transmitted with
precedence over unimportant services.
SP scheduling uses all resources to ensure the quality of service (QoS) of higher-priority services.
If there are always packets in higher-priority queues, packets in lower-priority queues will never
be transmitted.
WRR
WRR allocates a weight to each queue and a service time segment to each queue based on the
weight. Packets in a WRR queue are transmitted at the allocated service time segment. If the
queue does not have packets, packets in the next queue are transmitted immediately. Therefore,
if a link is congested, WRR allocates bandwidth based on the weights of queues.
Unlike SP, WRR schedules packets in every queue based on weights, so even packets in lower-
priority queues have a chance to be transmitted.
SP+WRR
The SP+WRR algorithm ensures the precedence of higher-priority services (for example, voice
services) and assigns time segments to transmit lower-priority services.
l If CS7, CS6, and EF queues, which have higher priorities than WRR queues, have packets,
packets in the CS7, CS6, and EF queues are transmitted using SP whereas packets in the
WRR queues are not transmitted.
l If the CS7, CS6, and EF queues have no packets, packets in the WRR queues (AF4, AF3,
AF2, and AF1) are transmitted using WRR.
l If both WRR queues and CS7, CS6, and EF queues have no packets, packets in the lower-
priority queue (BE) are transmitted using SP.
Traffic Shaping
Shaping limits the traffic volume and burst size of an outgoing traffic stream, so that the traffic
stream can flow at a regular speed.
If shaping is enabled and the buffer queue is empty, OptiX RTN 360 processes incoming packets
as follows:
l Forwards packets directly if the packet arrival rate is lower than or equal to the preset peak
information rate (PIR).
l Pushes packets into the buffer queue if the packet arrival rate is higher than the PIR.
l Forwards some packets as burst packets if the packet arrival rate is lower than or equal to
the PIR in a certain period. The maximum burst size is equal to the peak burst size (PBS).
If the buffer queue is not empty, the system pushes newly arriving packets into the buffer queue
and then forwards them at the PIR.
QoS Model
The following figure shows QoS technologies applicable to each QoS application point in the
QoS model for Native Ethernet services.
7.3 Specifications
This section lists the quality of service (QoS) specifications that OptiX RTN 360 supports.
Item Specifications
DiffServ Maximum 1
number of
DiffServ (DS)
domains
Item Specifications
Per-hop l CS7
behaviors l CS6
(PHBs)
l EF
l AF4 (AF41, AF42, and AF43)
l AF3 (AF31, AF32, and AF33)
l AF2 (AF21, AF22, and AF23)
l AF1 (AF11, AF12, and AF13)
l BE
NOTE
l Packets mapped to the AF11, AF21, AF31, and AF41 queues are
green by default.
l Packets mapped to the AF12, AF22, AF32, and AF42 queues are
yellow by default.
l Packets mapped to the AF13, AF23, AF33, and AF43 queues are
red by default.
Item Specifications
Congesti Tail drop Both microwave ports and Ethernet ports support tail drop.
on
avoidanc WRED Both microwave ports and Ethernet ports support WRED.
e
Queue Maximum 8
scheduli number of
ng egress queues
Weight When WRR is applied to the AF4, AF3, AF2, and AF1 queues,
allocation of the default weight (25%) of each AF queue is changeable.
WRR
DSCP value
Protocol type
Version Description
Table 7-3 describes the self-limitations of QoS, and limitations and dependencies between QoS
and other features.
Item Description
Self- WRR At each port of the OptiX RTN 360, WRR queues must be
limitations consecutive. That is, WRR queues and SP queues cannot
interleave.
Item Description
CAR When creating CAR, specify the PHBs to which port traffic
will map, so that CAR coloring will take effect (yellow
packets can be re-colored green).
When creating port-based CAR, create a PORT+C/SVLAN-
based flow (VLAN ID = 0) and apply CAR.
l Bandwidths provided by the OptiX RTN 360 network and bandwidths required by service
access and transmission
l Special network situations (for example, whether there are ports that carry both services
with and without priorities)
l Select simple traffic classification using DS or complex traffic classification based on the
trusted CoS.
l Configure DS based on the mapping between service priorities and PHBs. If wireless
network engineers have not yet worked out the mapping, liaise with them to determine the
mapping.
CS6 and CS7 queues always have higher priorities, and the packets in these two queues
are always scheduled first. It is recommended that these queues be used for control
packets and management packets, which require the highest scheduling priority and
very low bandwidth.
Do not place services that require high bandwidth and are insensitive to delay in high-
priority strict priority (SP) queues, such as EF. Otherwise, high-priority SP queues will
occupy all port bandwidth. It is recommended that voice services be placed in the EF
queue.
It is recommended that data services be placed in AF1, AF2, AF3, and AF4 queues
using the weighted round robin (WRR) algorithm. The scheduling weights determine
the proportion of bandwidth allocated to each queue.
l If the OptiX RTN 360 network provides a bandwidth lower than the total bandwidth to be
guaranteed, expand the network capacity.
l To restrict the bandwidth of services entering the RTN network based on the service type,
specify the rate limits at ingress ports for flows that are created in complex traffic
classification.
l To restrict the bandwidth of services based on PHBs (queues), perform shaping for port
queues.
l To better share the air-interface link bandwidth, do not perform shaping for microwave
ports on OptiX RTN 360 unless necessary.
If low-priority services require a guaranteed minimum bandwidth, perform shaping for port
queues of high-priority services, or configure an appropriate queue scheduling policy.
To avoid congestion, it is recommended that you configure weighted random early detection
(WRED) for microwave ports on OptiX RTN 360. WRED ensures the transmission of high-
priority services.
Alarms
l PORT_EXC_TRAFFIC
This alarm indicates that the bandwidth utilization at an Ethernet port has crossed the
threshold because of heavy traffic at the Ethernet port.
l ETH_NO_FLOW
This alarm indicates that there is no traffic at an enabled Ethernet port or microwave port
when the connected link is in the Up state.
l FLOW_OVER
This alarm indicates that the traffic transmitted or received at an Ethernet port or microwave
port has crossed the threshold.
Performance Events
l RXGOODFULLFRAMESPEED
This performance event indicates the rate of receiving good packets at a port.
l TXGOODFULLFRAMESPEED
This performance event indicates the rate of transmitting good packets from a port.
8 ETH OAM
ETH OAM detects and monitors the connectivity and performance of service links using OAM
protocol data units (PDUs). ETH OAM does not affect services.
8.1 Introduction
This section introduces ETH OAM.
8.3 Specifications
This section provides the ETH OAM specifications that OptiX RTN 360 supports.
8.1 Introduction
This section introduces ETH OAM.
Definition
ETH OAM uses OAM protocol data units (PDUs) to perform OAM operations at Ethernet Layer
2. ETH OAM is a low-rate protocol that is independent of the transmission medium. It occupies
minimal bandwidth and, therefore, does not affect services.
MPs are classified into maintenance association end points (MEPs) and maintenance association
intermediate points (MIPs).
l MEP
An MEP specifies the start and end positions of an MA. It initiates or terminates an OAM
packet, and is associated with services.
l MIP
An MIP cannot initiate an OAM packet but can respond to an OAM test.
Ethernet service OAM performs end-to-end detection based on the MD. In OAM, an MD is a
collection of all the MPs in a service instance. These MPs include MEPs and MIPs.
On an operator network, one VLAN corresponds to one service instance. With regard to OAM,
one VLAN corresponds to one or more MAs. By defining MAs, you can detect faults in a VLAN
service instance.
Ethernet service OAM provides layered management by adding the management level fields to
OAM protocol packets.
Currently, the ETH OAM protocol supports an 8-level division, from level 0 to level 7, where
0 is the lowest level and 7 the highest. In addition, eight maintenance entity (ME) levels are
allocated for identifying OAM packets used by customers, service providers, and operators.
l Customer ME levels: 7, 6, 5
l Service provider ME levels: 4, 3
l Operator ME levels: 2, 1, 0
ME levels are ordered from highest to lowest as follows: customer ME levels > service provider
ME levels > operator ME levels. If OAM operations are performed based on different layers, a
high-layer MP must not be located between low-layer MPs.
The following table provides details on the operations and their application scenarios of Ethernet
service OAM.
Remote loopback The OAM entity at the local In a remote loopback, the
end transmits the loopback initiator transmits and
control OAM PDU to the receives a number of packets.
remote OAM entity to By comparing the two
request a loopback. The numbers, you can check the
loopback data is analyzed for bidirectional performance of
fault locating and link the link between the initiator
performance testing. and the responder.
l IEEE 802.1ag: Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault
Management
l IEEE 802.3ah: Media Access Control Parameters, Physical Layers, and Management
Parameters for Subscriber Access Networks
l ITU-T Y.1731: OAM functions and mechanisms for Ethernet based networks
8.3 Specifications
This section provides the ETH OAM specifications that OptiX RTN 360 supports.
Table 8-3 ETH OAM specifications that OptiX RTN 360 supports
Item Specifications
OAM operation CC
LB
LT
AIS activation
LM
DM
Service loopback
Item Specifications
Version Description
Item Description
All MEPs and MIPs involved in an OAM test must belong to the same MA.
The MAC addresses of the MEPs and MIPs involved in an OAM test must be different.
Each MP in a single MA must have a unique ID.
If a service being tested passes a packet switching unit, set the MEP direction to Ingress;
if a service being tested does not pass any packet switching unit, set the MEP direction
to Egress.
For each NE that has an MEP, configure a list of remote MEPs with which that MEP
interacts.
l When you plan OAM operations, follow these guidelines:
Select appropriate OAM operations.
When performing an LB/LT test, you can use an MP ID or a MAC address to identify
a sink.
Activate the CC function before you use an MP ID to identify a sink.
If the AIS is activated on an MEP, the level of the customer layer should be higher than
that of the MD to which the MEP belongs.
Service loop detection does not require the creation of MDs, MAs, or MPs.
Alarms
l ETH_CFM_AIS
This alarm indicates local MEP AIS. This alarm occurs when the system receives AIS
messages, indicating that a fault occurred at the server layer.
l ETH_CFM_LOC
This alarm indicates loss of continuity. When the system does not receive any CCMs from
its peer for an interval 3.5 times the CCM transmission period, the system reports an
ETH_CFM_LOC alarm.
l ETH_CFM_MISMERGE
This alarm indicates an incorrect connection. When the system receives a CCM with an
incorrect MA name, the system reports an ETH_CFM_MISMERGE alarm.
l ETH_CFM_RDI
This alarm indicates that the remote MEP fails to receive CCMs. When the system receives
a CCM that contains the RDI from its peer, the system reports an ETH_CFM_RDI alarm.
l ETH_CFM_UNEXPERI
This alarm indicates error frames. When the system receives an invalid CCM (that is, the
transmission period of the received CCM is different from the preset value), the system
reports an ETH_CFM_UNEXPERI alarm.
l ETH_EFM_DF
This alarm indicates the failure of OAM automatic discovery. When point-to-port OAM
protocol negotiation fails on Ethernet ports, the system reports an ETH_EFM_DF alarm.
l ETH_EFM_EVENT
This alarm indicates that a performance event occurs at the remote end. When the system
receives the event notification OAM PDU (indicating bit errors on the link) from its peer,
the system reports an ETH_EFM_EVENT alarm.
l ETH_EFM_LOOPBACK
This alarm indicates that a loopback is performed. When the system initiates or responds
to a loopback, the system reports an ETH_EFM_LOOPBACK alarm.
l ETH_EFM_REMFAULT
This alarm indicates that a fault occurs at the remote end. When the system receives the
event notification OAM PDU (indicating a fault at the remote end) from its peer, the system
reports an ETH_EFM_REMFAULT alarm.
l ETHOAM_SELF_LOOP
This alarm indicates that a local loopback occurs. After the local loopback detection is
enabled on a port, the port reports the ETHOAM_SELF_LOOP alarm if it receives the
OAM packet that it transmitted previously.
Physical layer clock synchronization enables RTN equipment to obtain clock information from
data code streams to implement clock synchronization.
9.1 Introduction
This section introduces the physical layer clock synchronization solution.
9.3 Specifications
This section lists the physical layer clock synchronization specifications that OptiX RTN 360
supports.
9.1 Introduction
This section introduces the physical layer clock synchronization solution.
Clock Synchronization
In a broad sense, clock synchronization includes frequency synchronization and time
synchronization. Generally, clock synchronization refers to frequency synchronization.
Frequency synchronization means that the frequencies or phases of signals maintain a certain
and strict relationship. The valid instants of these signals appear at the same average rate so that
all the equipment on the communications network can operate at the same rate. That is, the phase
difference between signals is constant.
l For mobile communication networks and other service networks, not only signal
transmission but also communication services require clock synchronization. If clock
synchronization is not implemented, exceptions will occur, such as call drops and inter-cell
handover failures.
Digital signals transmitted on lines or links are coded or scrambled to reduce consecutive '0's or
'1's. Therefore, the code stream carries plentiful clock information. The clock information can
be extracted by applying phase lock and filter technologies and used for synchronization
references.
Microwave links, synchronous Ethernet links, and SDH lines can all provide timing information.
For example, gigabit Ethernet uses 8B/10B encoding signals. Even all '0's or all '1's original data
can be converted into line encoding signals with balanced "0"s and "1"s.
Clock Source
A clock source is a signal source carrying timing reference information. To achieve clock
synchronization, an NE keeps its local clock in phase with the timing information by using the
phase-locked loop (PLL).
Multiple clock sources can be configured for an NE. Clock source protection is implemented
based on the priorities configured in the clock source priority list. When the clock source of a
higher priority fails, the clock source of a lower priority is used.
9.3 Specifications
This section lists the physical layer clock synchronization specifications that OptiX RTN 360
supports.
Table 9-1 Physical layer clock synchronization specifications that OptiX RTN 360 supports
Item Specification
Version Description
Table 9-2 describes the dependencies and limitations of physical layer clock synchronization.
Item Description
Synchronous Ethernet Ethernet ports that use SFP electrical modules or work in 10BASE-
T mode or half-duplex mode do not support synchronous Ethernet.
NOTE
OptiX RTN 360 is usually used for transmitting services from small cell base stations at the network tail.
The following describes only the clock planning guidelines of OptiX RTN 360. For the clock planning
guidelines of upstream NEs, see the planning guidelines of the corresponding products.
l When two OptiX RTN 360s form a microwave link hop, the OptiX RTN 360s at the two
ends of the link are configured as the master and slave NEs. By default, the master NE
traces the synchronous Ethernet clock, and the slave NE traces the microwave link clock.
Therefore, configure the OptiX RTN 360 on the macro base station side as the master NE,
and the OptiX RTN 360 on the small cell base station side as the slave NE.
l It is recommended that an OptiX RTN 360 chain network contain a maximum of three
microwave link hops, that is, 6 NEs.
l Small cell base stations at the network tail connected to OptiX RTN 360 can obtain
reference clock signals through synchronous Ethernet ports.
l The SYNC_C_LOS alarm indicates that the class of a synchronization source is lost.
A Glossary
Numerics
802.11n A wireless transmission standard released after 802.11a/b/g by Wi-Fi Alliance. As a new
member to the 802.11 protocol family, 802.11n supports the 2.4 GHz and 5 GHz
frequency bands and provides a higher bandwidth (300 Mbit/s, much higher than the 54
Mbit/s provided by 802.11a/g) for WLAN access users. In addition, 802.11n supports
the MIMO technology, which provides two methods of increasing the communication
rate: by increasing the bandwidth and by improving the channel usage.
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
(QinQ) implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN
tag to allow the frame with double VLAN tags to be transmitted over the service
provider's backbone network based on the public VLAN tag. This provides a layer 2
VPN tunnel for customers and enables transparent transmission of packets over private
VLANs.
A
AC alternating current
adjacent-channel Interference from the adjacent channel. Adjacent-channel interference is caused by the
interference defect in the receiver filter, which allows the signal on the adjacent channel to penetrate
into the transmission bandwidth.
B
baseband A form of modulation in which the information is applied directly onto the physical
transmission medium.
blacklist A list containing information about subscribers who are prohibited from using certain
permissions or services due to certain reasons.
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
C
CAR committed access rate
CBS See committed burst size.
CIR committed information rate
CPU See central processing unit.
cabinet Free-standing and self-supporting enclosure for housing electrical and/or electronic
equipment. It is usually fitted with doors and/or side panels which may or may not be
removable.
cell A cell is a radio coverage area identified by either base station identity code or cell global
identification (CGI). A cell with an omni-directional antenna is a BTS area.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
(CPU) and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
channel spacing The center-to-center difference in frequencies or wavelengths between adjacent channels
in a WDM device.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of an
IP packet to be forwarded.
D
DC direct current
DCC See data communications channel.
DCN See data communication network.
DIP switch dual in-line package switch
DSCP See differentiated services code point.
DiffServ See Differentiated Services.
Differentiated Services An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ) differentiated manner based on CoS settings to handle network congestion.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
channel (DCC) transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
differentiated services According to the QoS classification standard of the Differentiated Service (Diff-Serv),
code point (DSCP) the type of services (ToS) field in the IP header consists of six most significant bits and
two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It is
the combination of IP precedence and types of service. The DSCP value is used to ensure
that routers supporting only IP precedence can be used because the DSCP value is
compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB). Therefore,
terminal devices can identify traffic using the DSCP value.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
ESD electrostatic discharge
ETSI See European Telecommunications Standards Institute.
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable and
easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000
Mbit/s, or 10,000 Mbit/s.
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
(ETSI)
F
FDD See frequency division duplex.
FE fast Ethernet
FEC See forward error correction.
forward error A bit error correction technology that adds correction information to the payload at the
correction (FEC) transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
frequency division An application in which channels are divided by frequency. In an FDD system, the uplink
duplex (FDD) and downlink use different frequencies. Downlink data is sent through bursts. Both
uplink and downlink transmission use frames with fixed time length.
G
GE Gigabit Ethernet
GUI graphical user interface
H
hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
I
ICMP See Internet Control Message Protocol.
IDU See indoor unit.
IEC International Electrotechnical Commission
IF See intermediate frequency.
Internet Control A network layer protocol that provides message control and error reporting between a
Message Protocol host server and an Internet gateway.
(ICMP)
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF) signal.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations, and
control system instability.
L
LLDP See Link Layer Discovery Protocol.
LOS line of sight
LPT link-state pass through
Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch
transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Layer Discovery The Link Layer Discovery Protocol (LLDP) is an L2D protocol defined in IEEE 802.1ab.
Protocol (LLDP) Using the LLDP, the NMS can rapidly obtain the Layer 2 network topology and changes
in topology when the network scales expand.
M
MAC See Media Access Control.
MD5 See message digest algorithm 5.
MDI medium dependent interface
MPLS See Multiprotocol Label Switching.
MTBF See mean time between failures.
N
NE network element
NE Panel A graphical user interface, of the network management system, which displays subracks,
boards, and ports on an NE. On the NE Panel, the user can complete most of the
configuration, management and maintenance functions for an NE.
NM network management
NSF non-stop forwarding
NTP Network Time Protocol
O
O&M operation and maintenance
OAM See operation, administration and maintenance.
OSPF See Open Shortest Path First.
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
First (OSPF) cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
operation, A set of network management functions that cover fault detection, notification, location,
administration and and repair.
maintenance (OAM)
P
P&E power and Ethernet
PBS See peak burst size.
PIR peak information rate
PRBS See pseudo random binary sequence.
PSE See power sourcing equipment.
PoE power over Ethernet
patch An independent software unit used for fixing the bugs in software.
peak burst size (PBS) A parameter that defines the capacity of token bucket P, that is, the maximum burst IP
packet size when the information is transferred at the peak information rate.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
power sourcing A piece of equipment that provides power to network devices (switches or hubs for
equipment (PSE) instance) by setting up a Power over Ethernet (PoE).
pseudo random binary A sequence that is random in the sense that the value of each element is independent of
sequence (PRBS) the values of any of the other elements, similar to a real random sequence.
Q
QinQ See 802.1Q in 802.1Q.
QoS See quality of service.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS An authentication mode in which the BRAS sends the user name and the password to
authentication the RADIUS server by using the RADIUS protocol. The RADIUS server authenticates
the user, and then returns the result to the BRAS.
RF See radio frequency.
RFC remote feature control
S
S-VLAN service virtual local area network
SFTP See Secure File Transfer Protocol.
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SSID service set identifier
SSL See Secure Sockets Layer.
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Sockets Layer A security protocol that works at a socket level. This layer exists between the TCP layer
(SSL) and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
(SNMP) transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
T
TCP/IP Transmission Control Protocol/Internet Protocol
TDD time division duplex
TLS Transport Layer Security
TMN See telecommunications management network.
tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
telecommunications A protocol model defined by ITU-T for managing open systems in a communications
management network network. TMN manages the planning, provisioning, installation, and OAM of
(TMN) equipment, networks, and services.
throughput The maximum transmission rate of the tested object (system, equipment, connection,
service type) when no packet is discarded. Throughput can be measured with bandwidth.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.
U
UNI See user-to-network interface.
USB See Universal Serial Bus.
Universal Serial Bus A serial bus standard to interface devices. It was designed for computers such as PCs
(USB) and the Apple Macintosh, but its popularity has prompted it to also become commonplace
on video game consoles and PDAs.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-UNI See virtual user-network interface.
VLAN virtual local area network
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
W
WAN wide area network
WEEE waste electrical and electronic equipment
WRED See weighted random early detection.