Print Preview - C:Documents and SettingsQMATALM agtool...

MINI-LINK TN R3 ETSI

Technical Description

MINI-LINK™


Technical Description

Copyright

© Ericsson AB 2007 - All Rights Reserved

Disclaimer

No part of this document may be reproduced in any form without the writtenpermission of the copyright owner.

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Contents

Contents

1 Introduction 1

1.1 General 1

1.2 Revision Information 2

2 System Overview 3

2.1 Introduction 3

2.2 Indoor Part with AMM 5

2.3 Indoor Part with ATU 6

2.4 Outdoor Part 7

3 Basic Node 9

3.1 System Architecture 9

3.2 Access Module Magazine (AMM) 11

3.3 Node Processor Unit (NPU) 20

3.4 E1 Interfaces 25

3.5 STM-1 Interface 27

3.6 Ethernet Traffic 31

3.7 ATM Aggregation 36

3.8 Traffic Routing 42

3.9 Protection Mechanisms 44

3.10 Synchronization 52

3.11 Equipment Handling 55

3.12 MINI-LINK E Co-siting 56

3.13 Unstructured E3 Interface 57

4 Radio Terminals 59

4.1 Overview 59

4.2 Modem Unit (MMU) 61

4.3 Radio Unit (RAU) 69

4.4 Antennas 76

4.5 PMP Functionality 79

4.6 1+1 Protection 81

4.7 Transmit Power Control 90

4.8 Performance Management 92

4/1555-CSH 109 32/1-V1 Uen B 2007-09-14


5 Access Termination Unit (ATU) 93

5.1 Overview 93

5.2 ATU 94

5.3 ATU C 100

6 Management 105

6.1 Fault Management 105

6.2 Configuration Management 109

6.3 Software Management 109

6.4 License Management 110

6.5 Performance Management 111

6.6 Security Management 113

6.7 Data Communication Network (DCN) 114

6.8 Management Tools and Interfaces 119

7 Accessories 123

7.1 Interface Connection Field (ICF) 123

7.2 PSU DC/DC Kit 126

7.3 Small Form Factor Pluggable 128

7.4 Optical splitter/combiner 128

7.5 DCN LAN Switch 128

Glossary 131

Index 137

4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Introduction

1 Introduction

1.1 General

MINI-LINK is the world’s most deployed microwave transmission system.The MINI-LINK TN R3 product family is the latest addition, offering compact,scalable, and cost-effective solutions.

The system provides integrated traffic routing, high capacity traffic, PDH andSDH multiplexing, Ethernet transport, ATM aggregation as well as protectionmechanisms on link and network level. The software configurable traffic routingminimizes the use of cables, improves network quality and facilitates controlfrom a remote location. With the high level of integration, rack space can bereduced by up to 70% compared to traditional solutions.

Configurations range from small end sites with one single radio terminal to largehub sites where all the traffic from a number of southbound links is aggregatedinto one link, microwave or optical, in the northbound direction.

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

PFU3

PFU3FAU2

NPU3

MMU2 E 155

MMU2 E 155

MMU2 E 155

MMU2 F 155

E1/DS1E1/DS1

LTU3 12 1E1/DS1

9716

15 GHz

15 GHz

ALARMPOWER

ALIGNMENT

RADIOCABLE

15 GH

z

15 G

Hz

RADIOCABLE

ALIGNMENTALARM POWER

15 GH

z

15 G

Hz

RADIOCABLE


15 GH

z

15 G

Hz

RADIOCABLE


Figure 1 A MINI-LINK TN R3 configuration

14/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The purpose of this description is to support the reader with detailed informationon included products and accessories, from technical and functional pointsof view.

Detailed technical system data is available in MINI-LINK TN ETSI ProductSpecification.

Note: If there is any conflict between this document and information in MINILINK TN ETSI Product Specification or compliance statements, thelatter ones will supersede this document.

Some functions described in this document are subject to license handling, thatis a license is required to enable a specific function.

1.2 Revision Information

This document is updated due to the introduction of MINI-LINK TN R3.

Information about the following products and accessories is new or updated:

• AMM 2p B, AMM 6p C/D

• PFU3 B

• NPU3

• MMU2 D, MMU2 E/F 155 with XPIC functionality

• LTU3 12/1

• LTU 16/1

• DCN LAN Switch

• PMP Functionality

• Equipment and Line Protection (ELP)

• Enhanced Equipment Protection (EEP)

• Small Form Factor Pluggable (SFP)

• ServiceOn Microwave

• General document improvements

2 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

System Overview

2 System Overview

2.1 Introduction

This section gives a brief introduction to the system and its components.

9961

15 GH

z

15 G

Hz

15 GH

z

15 G

Hz

15 GHz

15 GHz

Indoor part with AMM

Outdoor part with Antennaand RAU

Indoor part with ATU0

20

3

0203

MMU2 E 155

NPU3

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

PFU3

PFU3FAU2

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

Figure 2 Outdoor and indoor parts

A MINI-LINK TN R3 Network Element (NE) can, from a hardware andinstallation point of view, be divided into two parts:

• Indoor part of two types:

− Access Module Magazine (AMM) with plug-in units, see Section 2.2on page 5.

− Access Termination Unit (ATU), see Section 2.3 on page 6.

• Outdoor part, see Section 2.4 on page 7.

An NE with AMM can from a functional and configuration point of view bedivided into the following parts:

34/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Basic Node The Basic Node holds the system platform providing trafficand system control, such as traffic routing, multiplexing,protection mechanisms and management functions.Specific plug-in units provide traffic interfaces, PDH, SDHand Ethernet, for connection to network equipment such asa radio base station, ADM or LAN. ATM aggregation is alsosupported.Finally, it includes indoor mechanical housing, powerdistribution and cooling.For more information, see Section 3 on page 9.

Radio Terminals Each Radio Terminal provides microwave transmission from2x2 to 155 Mbit/s, operating within the 6 to 38 GHz frequencybands, utilizing C-QPSK and 16, 64, 128 QAM modulationschemes. It can be configured as unprotected (1+0) orprotected (1+1).For more information, see Section 4 on page 59.

Basic NodeExternalEquipment

Radio Terminals

6731

Network Element

Figure 3 Basic Node and Radio Terminals

The Basic Node and Radio Terminal concept does not apply to an NE withATU. However, the self-contained unit implements applicable parts such as,traffic interfaces, control and management functions, power, cooling and theindoor part of an unprotected (1+0) Radio Terminal with C-QPSK modulation.

The management features and tools are described in Section 6 on page 105.

4 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

System Overview

2.2 Indoor Part with AMM

AMM 20p

AMM 6p D

9686

INF

OR

MAT

ION

PFU1

MM

U2 B 4-34

LTU 16x2

LTU 155e/o

NPU1 B

AMM 2p B

02

03

0203

MMU2 E 155

NPU3

AMM 6p C

07

/NP

U0

60

50

40

30

2

08/F

AU2

01/P

FU3

00/P

FU3

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

PFU3

PFU3FAU2

07

/NP

U0

60

50

40

30

2

08/F

AU2

01/P

FU3

00/P

FU3

PFU3

PFU3FAU2

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

Figure 4 AMMs

The indoor part consists of an Access Module Magazine (AMM) with plug-inunits interconnected through a backplane. One plug-in unit occupies one slot inthe AMM. The AMM fits into standard 19" or metric racks.

The following text introduces the standard indoor units and their main functions.For each unit there exist several types with different properties, furtherdescribed in Section 3 on page 9 and Section 4 on page 59.

Access Module Magazine (AMM) The AMM houses the plug-in units andprovides backplane interconnection of traffic,power and control signals.

Node Processor Unit (NPU) The NPU handles the system’s controlfunctions. It also provides traffic andmanagement interfaces.

Line Termination Unit (LTU) The LTU provides PDH or SDH trafficinterfaces.

Modem Unit (MMU) The MMU constitutes the indoor part of aRadio Terminal. It determines the trafficcapacity and modulation scheme.

Ethernet Interface Unit (ETU) The ETU provides Ethernet traffic interfaces.

ATM Aggregation Unit (AAU) The AAU provides ATM aggregation of trafficon E1 links.

54/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Switch Multiplexer Unit (SMU) The SMU provides traffic and DCN interfacesfor MINI LINK E equipment.

Power Filter Unit (PFU) The PFU filters the external power anddistributes the internal power to the plug-inunits via the backplane.

Fan Unit (FAU) The FAU provides cooling for the indoor part.

The indoor part also includes cables and installation accessories.

The interconnection between the outdoor part (Radio Units and antennas)and the indoor part is one coaxial cable per MMU carrying full duplex traffic,DC supply voltage, as well as management data.

2.3 Indoor Part with ATU

The Access Termination Unit implements the indoor part of a MINI-LINK TNR3 Edge Node. It can be used for transmission of PDH traffic and in Ethernetbridge applications.

The ATU comprises one self-contained unit, with a height of 1U, for installationin 19” or metric racks. It can also be mounted on a wall, using a dedicatedmounting set, or put on a desk.

9957

60V RAU

0V DC -48V

10BASE-T O&M BR

LAN

Brid

ge

E1:11

E1:10

E1:9

E1:8

E1:7

E1:6

E1:5

E1:4

10/100BASE-T

Figure 5 ATU

The ATU provides unprotected (1+0) microwave transmission within the 6 to38 GHz frequency bands using C QPSK modulation, when connected to anRAU with antenna. The interconnection between the ATU and the outdoorpart is one coaxial cable carrying full duplex traffic, DC supply voltage, andmanagement data.

Different ATU types are available offering traffic capacity from 2x2 to 17x2Mbit/s, which can be shared between PDH traffic with a maximum of 8xE1 andEthernet traffic over a maximum of 16xE1.

The ATU is further described in Section 5 on page 93.

6 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

System Overview

2.4 Outdoor Part

The outdoor part is supplied for various frequency bands. It consists of anantenna, a Radio Unit (RAU) and associated installation hardware. Forprotected (1+1) systems, two RAUs and one or two antennas are used. Whenusing one antenna, the two RAUs are connected to the antenna using a powersplitter.

The RAU and the antenna are easily installed on a wide range of supportstructures. The RAU is fitted directly to the antenna as standard, integratedinstallation. The RAU and the antenna can also be fitted separately andconnected by a flexible waveguide. In all cases, the antenna is easily alignedand the RAU can be disconnected and replaced without affecting the antennaalignment.

The RAU is described in Section 4.3 on page 69.

The antennas are described in Section 4.4 on page 76.

8499

1+1 terminalintegrated power splitter

1+0 terminalseparate installation

1+0 terminalintegrated installation

15 GH

z

15 G

Hz

RADIOCABLE


15 GH

z

15 G

Hz

ALARMPOWER

ALIGNMENT

RADIOCABLE

Figure 6 RAUs and antennas in different installation alternatives

74/1555-CSH 109 32/1-V1 Uen B 2007-09-14


8 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3 Basic Node

This section describes the Basic Node functions, hardware and traffic interfaces.

3.1 System Architecture

The system architecture is based on a Node Processor Unit (NPU)communicating with other plug-in units, via buses in the AMM backplane. Thebuses are used for traffic handling, system control and power distribution.

6625

Plug-in Unit Plug-in Unit

Power Filter Unit

Node Processor Unit

Backplane

TDM

PCI

SPI

Power

BPI

Figure 7 System architecture

3.1.1 TDM Bus

The Time Division Multiplexing (TDM) bus is used for traffic routing betweenthe plug-in units. It is also used for routing of the DCN channels, used forO&M data transport. The lowest switching level is E1 for traffic connectionsand 64 kbit/s for DCN channels. The traffic connections on the TDM bus areunstructured with independent timing.

The bus has a switching capacity of 820 Mbit/s. It is redundant for additionalprotection against hardware failures.

94/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.1.2 PCI Bus

The Peripheral Component Interconnect (PCI) bus is a high bandwidthmultiplexed address/data bus used for control and supervision. Its main use isfor communication between the NPU software and other plug-in units’ softwareand functional blocks

3.1.3 SPI Bus

The Serial Peripheral Interface (SPI) is a low speed synchronous serialinterface bus used for:

• Unit status control and LED indication

• Board Removal (BR) button used for unit replacement

• Inventory data

• Temperature and power supervision

• User I/O communication

• Reset of control and traffic logic

3.1.4 Power Bus

The external power supply is connected to a PFU (or NPU2/NPU3 B for AMM2p/AMM 2p B). The internal power supply is distributed via the Power bus tothe other plug-in units. When using two PFUs in an AMM, the bus is redundant.

3.1.5 BPI Bus

The Board Pair Interconnect (BPI) bus is used for communication between twoplug-in units in a protected (1+1) configuration, for example when using twoLTU 155 units in a Multiplexer Section Protection (MSP)1+1 configuration.

It also interconnects groups of four plug-in units, enabling board protectionschemes including three and four plug-in units.

3.1.6 PTP Connection

The Point-to-Point (PTP) connection joins services to services (for exampleEthernet over VCs dropped by ADM) and services to line interfaces (for exampleEthernet over modem or ATM over SDH modem), see Figure 8 on page 11.

10 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

Line Interface

RadioModemLTU Radio

Modem

ATM Ethernet ADMEthernet ADM

Services

Line interface

PTP Connections

9746

Figure 8 PTP Connections

3.2 Access Module Magazine (AMM)

The indoor part consists of an Access Module Magazine (AMM) with plug-inunits. This section describes the AMM types and their associated cooling andpower supply functions.

3.2.1 AMM 2p and AMM 2p B

AMM 2p is suitable for end site and repeater site applications. There are twomodels:

• AMM 2p has two half-height slots equipped with one NPU2 and the optionalLTU 12/1 Kit.

• AMM 2p B has two half-height slots equipped with one NPU3 and theoptional LTU3 12/1.

Two full-height slots can be equipped with MMU, LTU or ETU. The height ofan AMM 2p or an AMM 2p B is 1U.

The FAU4 is used depending on the configuration, see Section 3.2.1.2 onpage 13.

AMM 2p and AMM 2p B can be fitted in a standard 19" or metric rack or on awall using a dedicated mounting set.

114/1555-CSH 109 32/1-V1 Uen B 2007-09-14


01/N

PU

00

02

03

NE NameIP addr.+maskFarend 0100 0302

ID

LIFT

LIFT

NPU2 FAU4

9976

L

LTU3 12/1

Figure 9 AMM 2p

02

03

0203

NPU3

LTU3 12/1

FAU4

9972

L

LIFT

LIFT

Figure 10 AMM 2p B

3.2.1.1 Power Supply

AMM 2p is power supplied by –48 V DC or +24 V DC, connected to the NPU2.The power is distributed from the NPU2 to the plug-in units, via the power busin the backplane of the AMM.

+_External Power

Supply–48 V DC or

+24 V DC

7019

NPU2

Figure 11 Power supply for AMM 2p

AMM 2p B is power supplied by –48 V DC or +24 V DC redundant power. TwoDC connectors at the left side of the front panel are connected to the backplane.To achieve redundant power, two power sources must be connected.

12 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

9958

NPU3

+_

+_

Redundant PowerSupply

–48 V DC or+24 V DC

Figure 12 Power supply for AMM 2p B

3.2.1.2 Cooling

AMM 2p and AMM 2p B can be used with or without forced air-cooling,depending on the configuration. Forced air-cooling is provided by FAU4, placedvertically inside the AMM. FAU4 holds three internal fans.

If the indoor location has other fan units, which provide sufficient coolingthrough the AMM, the FAU4 can be omitted. However, air filters should bepresent in the cabinet door.

Complete rules for cooling are available in MINI-LINK TN ETSI ProductSpecification and the Product Catalog.

Air in

Air out

9715

02

03

0203

MMU2 E 155

NPU3

Figure 13 Cooling airflow in AMM 2p B

The air enters at the right hand side of the AMM and exits at the left handside of the AMM.

3.2.2 AMM 6p B/C/D

AMM 6p B/C/D is suitable for medium-sized hub sites or prioritized small-siteswith 1+1 protection.

AMM 6p B has six full-height horizontal slots and two half-height vertical slots.It houses one NPU1 B, one or two PFU3 and one FAU2, see Figure 14 onpage 14.

AMM 6p C or D have four (D) or five (C) full-height horizontal slots, four (D) ortwo (C) half-height horizontal slots and two half-height vertical slots. Theyhouse one or two NPU3, one or two PFU3 B and one FAU2, see Figure 15 onpage 14 and Figure 16 on page 14.

134/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The remaining slots in AMM 6p B/C/D can be equipped with MMU, LTU, ETU,AAU or SMU. Protected pairs, for example two MMUs in a protected (1+1) RadioTerminal, are positioned in adjacent slots starting with an even slot number.

AMM 6p B/C/D can be fitted in a standard 19" or metric rack or on a wall usinga dedicated mounting set. The height of AMM 6p B/C/D is 3U.

PFU307/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

LTU 155e

MMU2 B 4-34

MMU2 B 4-34

LTU 155e/o

LTU 16x2

PFU3

PFU3FAU2

NPU1 B

7855FAU2

NPU1 B

Figure 14 AMM 6p B

PFU3 B

FAU2

NPU3

9974

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

PFU3

PFU3FAU2

MMU2 F 155

Figure 15 AMM 6p C

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

PFU3

PFU3FAU2

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

PFU3 B

FAU2

NPU3

9975

Figure 16 AMM 6p D

14 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node


AMM 6p B is power supplied by –48 V DC, connected to the PFU3. AMM 6pC/D is power supplied by –48 V DC or +24 V DC, connected to the PFU3 B.The power is distributed from the PFU3 or PFU3 B to the other units, via thepower bus in the backplane of the AMM.

The power system is made redundant using either two PFU3 or PFU3 Bs,utilizing the redundant power bus.

Using the PSU DC/DC kit enables connection to a +24 V DC power supply,see Section 7.2 on page 126.

+_+_

PFU3 or PFU3 B

External Power Supply

9712

PFU3: –48V DCPFU3 B: –48V DC or +24V DC

Figure 17 Power supply for AMM 6p B, C or D

PFU3/PFU3 B provides input low voltage protection, transient protection, softstart and electronic fuse to limit surge currents at start-up, or overload currentsduring short circuit.

3.2.2.2 Cooling

Forced air-cooling is always required and provided by FAU2, which holds twointernal fans.

Air out

9707Air in

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

PFU3

PFU3FAU2

MMU2 E 155

MMU2 F 155

NPU3

E1/DS1E1/DS1

LTU3 12 1E1/DS1

Figure 18 Airflow in AMM 6p

The air enters at the front on the right hand side of the AMM and exits at therear on the left hand side of the AMM.

154/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.2.3 AMM 20p

The AMM 20p is suitable for large-sized hub sites, for example at theintersection between the optical network and the microwave network. It has20 full-height slots, one housing an NPU1 B and two half-height slots housingone or two PFU1.

The remaining slots can be equipped with MMU, LTU, ETU, AAU and SMU.Protected pairs, require two MMUs in a protected (1+1) Radio Terminal, andare positioned in adjacent slots starting with an even slot number.

A cable shelf is fitted directly underneath the AMM to enable neat handling ofcables connected to the fronts of the plug-in units.

An FAU1 is fitted on top of the AMM unless forced air-cooling is provided. Anair guide plate is fitted right above the FAU1.

AMM 20p can be fitted in a standard 19" or metric rack. The AMM with FAU1,cable shelf and air guide plate has a total height of 10U.

INF

OR

MAT

ION

PFU1

MM

U2 4-34

MM

U2 B 4-34

MM

U2 B 4-34

LTU 16x2

LTU 155e/o

NPU 8x2

-48VPower A

-48VFAN UNIT

Power BAlarm B

Alarm A

Fault Power

PFU1

FAU1

Air Guide Plate

Cable Shelf

7861

NPU1 B

NPU1 B

Figure 19 AMM 20p

16 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node


AMM 20p is power supplied by –48 V DC, connected to the PFU1 or via anInterface Connection Field (ICF1). The power is distributed from the PFU1 tothe plug-in units, via the power bus in the backplane of the AMM.

The power system is made redundant using two PFU1s, utilizing the redundantpower bus.

The PSU DC/DC kit enables connection to +24 V DC power supply, see Section7.2 on page 126. The ICF1 is not used in this installation alternative.

FAU1

PFU1

ICF1+_+_ +

_

+_

FAU1

PFU1

Power supply with ICF1 Power supply without ICF1

+_+_

External PowerSupply

–48 V DC

External PowerSupply

–48 V DC

6708

Figure 20 Power supply for AMM 20p

6709

–48 V DC

Fan alarmPowerBR

Fault

Fan alarm0V

PFU1

-48V DC

Figure 21 PFU1

PFU1 has one –48 V DC connector for external power supply and oneconnector for import of alarms from FAU1, as the FAU1 is not connected tothe AMM backplane.

174/1555-CSH 109 32/1-V1 Uen B 2007-09-14


PFU1 provides input low voltage protection, transient protection, soft start andelectronic fuse to limit surge currents at start-up, or overload currents duringshort circuit.

A redundant PFU1 can be extracted or inserted without affecting the powersystem.

3.2.3.2 Cooling

Forced air-cooling is provided by FAU1, fitted directly above the AMM. The airenters through the cable shelf, flows directly past the plug-in units and exits atthe top of the AMM through the air guide plate.

If the indoor location has other fan units, which provide sufficient coolingthrough the AMM, the FAU1 can be omitted. However, air filters should bepresent in the cabinet door.

Complete rules for cooling are available in MINI-LINK TN ETSI ProductSpecification and the Product Catalog.

Air Guide Plate

FAU1

AMM 20p

Air in

Air out

Cable Shelf

7214

Figure 22 Side view of the airflow in AMM 20p

18 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

-48VPower A

-48VFAN UNIT

Power BAlarm B

Alarm A

Fault Power

–48 V DC A

–48 V DC B

Fan alarm A

Fan alarm B

6710

Figure 23 FAU1

FAU1 has an automatic fan speed control and houses three internal fans.

FAU1 has two –48 V DC connectors for redundant power supply. Twoconnectors are also available for export of alarms to PFU1.

194/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.3 Node Processor Unit (NPU)

The NPU implements the system’s control functions. One NPU is alwaysrequired in the AMM. The NPU also provides traffic, DCN and managementinterfaces.

The NPU holds a Removable Memory Module (RMM) for storage of license andconfiguration information. The following NPUs are available:

3.3.1 Overview

NPU1 B Fits in an AMM 6p B or AMM 20p.

NPU2 Fits in an AMM 2p.

NPU3 Fits in an AMM 2p B, AMM 6p C or AMM 6p D.

NPU2

0V

0VDC

DC -48V

+24V

E1/DS1:3A-3D 10/100 Base-T

F P

O&M

NPU1 B

NPU2

10/100BASE-T

1x(4xE1)O&M

2x(4xE1) User I/O10/100BASE-T

O&M Not used

ERICSSON

NPU1 B

10/100Base-TConsole

O&M

E1:3A-3D E1:2A-2D User I/O:1A-1I

Faul

tPo

wer

BR

RMM

RMM

+24 V DC–48 V DC

NPU3

TR:4A-4D/User Out:E-F

10/100 Base-TF P

O&M

2x(10/100BASE-T)

4xE1 + 2xUser OutO&M

RMMNPU3

9959

E1/DS1 10/100 Base-T

LANTR:3

Figure 24 NPUs

The following summarizes the common functions of the NPUs:

• Traffic handling

20 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

• System control and supervision

• IP router for DCN handling

• SNMP Master Agent

• Ethernet interface for connection to a site LAN

• Storage and administration of inventory and configuration data

• USB interface for LCT connection

There are also some specific functions associated with each NPU type assummarized below.

NPU1 B • 2x(4xE1) for traffic connections• Three User Input ports• Three User Output ports

NPU2 • 1x(4xE1) for traffic connections• Filters the external power and distributes the internal power• The Ethernet interface can be used for Ethernet bridge

applications

NPU3 • 1x(4xE1) for traffic connections• Two User Output ports

3.3.2 Functional Blocks

This section describes the internal and external functions of the NPUs, basedon the block diagrams in Figure 25 on page 22, Figure 26 on page 22 andFigure 27 on page 23.

214/1555-CSH 109 32/1-V1 Uen B 2007-09-14


8358

SPI

TDMTDM Bus

PCI Bus

SPI Bus

PowerPower Bus

3 User In3 User Out

8xE1

10/100BASE-TEthernet

User I/O

PCI

USBO&M

NodeProcessor

Secondaryvoltages

LineInterface

Figure 25 Block diagram for NPU1 B

8280

PCI

SPI

TDMTDM Bus

PCI Bus

SPI Bus

PowerPower Bus

4xE1

10/100BASE-T

USBO&M

Ethernet

LineInterface

NodeProcessor

Secondaryvoltages

External power supply+24 V DC or –48 V DC

Figure 26 Block diagram for NPU2

22 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

9704

PCI

SPI

TDMTDM Bus

PCI Bus

SPI Bus

PowerPower Bus

2x10/100BASE-T

USBO&M

Ethernet

LineInterface

NodeProcessor

Secondaryvoltages

User Output

4xE1 + 2xUser Out

Figure 27 Block diagram for NPU3

3.3.2.1 TDM

This block interfaces the TDM bus by receiving and transmitting the traffic(nxE1) and DCN channels (nx64 kbit/s).

The Node Processor communicates with the TDM block via the PCI block.

3.3.2.2 PCI

This block interfaces the PCI bus used for control and supervisioncommunication. The block communicates with the Node Processor, whichhandles control and supervision of the whole NE.

3.3.2.3 SPI

This block interfaces the SPI bus used for equipment status communication.The block communicates with the Node Processor, which handles equipmentstatus of the whole NE.

Failure is indicated by LED’s on the front of the unit.

234/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.3.2.4 Power

This block interfaces the Power bus and provides secondary voltages for theunit. All plug-in units have a standard power module providing electronic softstart and short circuit protection, filter function, low voltage protection, DC/DCconverter and a pre-charge function.

NPU3 has no connector for external power. For AMM 2p B the power isdistributed to the backplane at the left hand side of the AMM.

3.3.2.5 Node Processor

The Node Processor is the central processor of the NE, responsible for thetraffic and control functions listed in Section 3.3.1 on page 20.

3.3.2.6 Line Interface

This block provides the E1 line interfaces for external connection.

3.3.2.7 Ethernet

This block provides a 10/100BASE-T connection to site LAN and 10/100BASE-Ttraffic in Ethernet bridge applications. The Ethernet traffic is mapped on nxE1,where n≤16, using one inverse multiplexer.

An IP telephone can be connected to the Ethernet interface, enabling servicepersonnel to make calls to other sites. This digital Engineering Order Wire(EOW) solution utilizes VoIP in the IP DCN. For more information on EOW forMINI-LINK, see MINI-LINK Engineering Order Wire Feature Description.

See Section 3.6 on page 31 for more information on Ethernet traffic.

3.3.2.8 O&M

This block provides the LCT connection to the NPU using a USB interface. Theequipment is accessed using a local IP address.

3.3.2.9 User I/O

This block handles the User Out ports on the NPU3 and the User In and UserOut ports on the NPU1 B, see Section 6.1.3 on page 108.

24 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.4 E1 Interfaces

This section describes the plug-in units providing short haul 120 Ω balanced E1(G.703) interfaces. In a mobile access network these are typically used for trafficconnection to a radio base station or for connection to leased line networks.

3.4.1 NPU

NPU2 and NPU3 provides four E1 interfaces, NPU1 B provides eight E1interfaces, see Section 3.3.1 on page 20.

3.4.2 LTU

3.4.2.1 Overview

The following LTUs with E1 interfaces are available:

LTU 16/1 Fits in any AMM. The LTU 16/1 provides 16 additional E1 interfaces.

LTU3 12/1 Fits in an AMM 2p (as LTU 12/1 Kit, incl. washer), AMM 2p B andAMM 6p C or D. For sites where the eight E1 interfaces on the NPU3are insufficient, the LTU3 12/1 provides 12 additional E1 interfaces.

LTU 16/1

LTU3 12/1

Pow

erFa

ultTR:3A-3D

E1/DS1E1/DS1

TR:2A-2D TR:1A-1D

LTU3 12 1E1/DS1

3x(4xE1)9977

E1:1A-1DE1:2A-2D

E1:3A-3DE1:4A-4D

ERICSSON

LTU 16/1

Faul

tPo

wer

BR

4x(4xE1)

Figure 28 LTUs with E1 interfaces

254/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.4.2.2 Functional Blocks

This section describes the internal and external functions of the LTUs with E1interfaces, based on the block diagram in Figure 29 on page 26.

6662

SPI

TDMTDM Bus

PCI Bus

SPI Bus

PowerPower Bus Secondary voltages

Line Interface

12xE1 or 16xE1

Control and Supervision

Figure 29 Block diagram for LTU 16/1 and LTU3 12/1

3.4.2.2.1 TDM

This block interfaces the TDM bus by receiving and transmitting the traffic(nxE1).

3.4.2.2.2 Control and Supervision

This block interfaces the PCI bus and handles control and supervision. Its mainfunctions are to collect alarms, control settings and tests.

The block communicates with the NPU over the PCI bus.

3.4.2.2.3 SPI

This block interfaces the SPI bus and handles equipment status. Failure isindicated by LED’s on the front of the unit.

3.4.2.2.4 Power


26 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.4.2.2.5 Line Interface

This block provides the E1 line interfaces for external connection.

3.5 STM-1 Interface

The LTU 155 plug-in units provide a channeled STM-1 Terminal Multiplexer(TM) interface. This interface terminates one STM-1 with 63xE1 (or 21xE1)mapped asynchronously into 63xVC-12 (or 21xVC-12), depending on the typeof plug-in unit. The E1s are available at the TDM bus for traffic routing to otherplug-in units.

If incoming SDH radio traffic on MMU2 E/F 155 shall be connected to the TDMbus, an LTU 155 is needed as a terminal multiplexer to extract the E1s from theSTM-1. See Section 4.2 on page 61.

3.5.1 Overview

• At aggregation sites where the high capacity optical network connects tothe microwave network. The LTU 155 provides an effective interface usingone STM-1 interconnection instead of nxE1.

• To build high capacity microwave networks, with for example ring topology,using a combination of MINI-LINK TN’s.

• Transmission of up to 21xE1 over channelized STM-1 interfacing 3G radiobase stations.

Both electrical and optical interfaces are available.

The STM-1 interface on LTU 155s can be equipment and line protected usingMSP 1+1, see Section 3.9.3 on page 48.

274/1555-CSH 109 32/1-V1 Uen B 2007-09-14


9978

63xE1

Electrical or optical interface

nxE1

LTU 155

LTU 16/1

nxE1

NPU1 B

nxE1

LTU 16/1

TDM Bus

Figure 30 An example of how to use the STM-1 interface

3.5.2 LTU 155

There are three versions of the LTU 155:

LTU 155e Provides one electrical interface (G.703), mapping 63xE1.

LTU 155e/o Provides one optical interface (short haul S-1.1) and one electricalinterface (G.703), mapping 63xE1. Note: only one at a time.

LTU B 155 Provides one optical interface (short haul S-1.1) and one electricalinterface (G.703), mapping 21xE1. Note: only one at a time.

The LTU 155 fits in all AMM types.

28 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

TX OPT. RX

RXTXEL.

ERICSSON

LTU B 155

Cau

tion

Invisib

leLas

er Ra

diation

When

Open

Class

1 Las

er

Faul

tPo

wer

BR

TX OPT. RX

RXTXEL.

ERICSSON

LTU 155e/o

Cau

tion

Invisib

leLas

er Ra

diation

When

Open

Class

1 Las

er

Faul

tPo

wer

BR

RXTXEL.

ERICSSON

LTU 155e

Faul

tPo

wer

BR

Optical

8278

LTU 155e

LTU 155e/o

LTU B 155

OpticalElectrical

Electrical

Electrical

Figure 31 LTU 155


This section describes the internal and external functions of the LTU 155,based on the block diagram in Figure 32 on page 30.

294/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6663

SPI

TDMTDM Bus

PCI Bus

SPI Bus


VC-12 STM-1MS/RS VC-4

SDH Equipment

Clock

BPI (MSP 1+1)


Figure 32 Block diagram for LTU 155

3.5.2.1.1 TDM

This block interfaces the TDM bus by receiving and transmitting the traffic(nxE1) and DCN channels (nx64 kbit/s).


This block interfaces the PCI bus and handles control and supervision. Itsmain functions are to collect alarms, control settings and tests. The blockcommunicates with the NPU over the PCI bus.

The block holds a Device Processor (DP) running plug-in unit specific software.

3.5.2.1.3 SPI


3.5.2.1.4 Power


30 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.5.2.1.5 VC-12

This block maps 63xE1 (or 21xE1) to/from 63xVC-12 (or 21xVC-12) addingoverhead bytes.

The LTU B 155 registers 21xE1 interfaces from the first TUG3, that is the KLMnumbers 1.1.1-1.1.3, 1.2.1-1.2.3 through 1.7.1-1.7.3.

3.5.2.1.6 MS/RS VC-4

This block maps the VC-12s to/from one VC-4 adding path overhead.

The block provides the electrical and optical STM-1 line interfaces for externalconnection.

3.5.2.1.7 SDH Equipment Clock

This block handles timing and synchronization.

The LTU 155 utilizes the synchronization functions described in Section 3.10on page 52.

3.6 Ethernet Traffic

3.6.1 Overview

• ETU2 provides five 10/100BASE-T interfaces and one 10/100/1000BASE-Tinterface. See Section 3.6.3 on page 33.

• NPU2 provides one 10/100BASE-T interface, combined for Ethernet Trafficand Ethernet Site LAN. See Section 3.3.1 on page 20.

• NPU3 provides two 10/100BASE-T interfaces, one for Ethernet Traffic andone for Ethernet Site LAN. See Section 3.3.1 on page 20

• ATU provides one 10/100BASE-T interface for Ethernet Traffic and one10BASE-T interface for Ethernet Site LAN. See Section 5.2 on page 94.

The Ethernet traffic is transported between NEs in multiple E1s, over a singlehop or through a network. Figure 33 on page 32 shows an example of how thedifferent units can be used in a network.

314/1555-CSH 109 32/1-V1 Uen B 2007-09-14


9963

AMM 2pNPU2

AMM 6p CNPU3

Ethernet corenetwork

ATU

AMM 2pNPU2

AMM 2p BNPU3

ATU 1 - 16xE1100BASE-T

AMM 6pETU2

AMM 6pETU2

AMM 20pETU2

Figure 33 Ethernet traffic in a MINI-LINK TN R3 network

The bandwidth of each Ethernet bridge connection is nxE1 per inversemultiplexer in the unit, where n≤48 for ETU2 (with a maximum of 96 E1s intotal), and n≤16 for NPU2 and ATU. NPU2, NPU3and ATU have one inversemultiplexer while ETU2 has six.

Ethernet traffic is connected to the units using RJ-45 connectors with supportfor shielded cable.

The Ethernet bridge connections have auto-negotiation 10/100 Mbit/s speedand full/half duplex. Transparency to all kinds of traffic is supported, includingIEEE 802.1Q VLAN, MAC address based VLAN, VLAN tag ID based anduntagged frames, frames with up to 2 VLAN tags or frames with ICS tag.

The number of E1s in each connection is configured from the managementsystem. The traffic is distributed over the E1s by an inverse multiplexer. Theload sharing is seamless and independent of the Ethernet layer.

Figure 34 on page 33 shows the protocol layers involved in an Ethernet bridgeconnection.

32 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

9532

EthernetEthernet traffic Ethernet trafficEthernet

G.703 G.703SDH/PDH

InverseMultiplexer

InverseMultiplexer

Figure 34 Protocol stack

3.6.2 Performance Management

The following performance counters for Ethernet traffic are available:

• Number of discarded packets, for example due to overflow or CRC-32errors

• Number of sent/received frames

• Number of sent/received octets

3.6.3 Ethernet Interface Unit (ETU)

The ETU2 provides five 10/100BASE-T interfaces and one 10/100/1000BASE-Tinterface. It can be fitted in any AMM.

ETU2

10/100BASE-T10/100/1000BASE-T

8359

:1

ERICSSON

ETU2

Faul

tPo

wer

BR

10/100BASE-T

10/100/1000BASE-T

10 100

1000

Link

Figure 35 ETU2


This section describes the ETU2 based on the block diagram in Figure 36on page 34.

334/1555-CSH 109 32/1-V1 Uen B 2007-09-14


7489

SPI

TDMTDM Bus

PCI Bus

SPI Bus



Inverse Multiplexers

Ethernet

10/100/1000BASE-T

10/100BASE-T

10/100BASE-T

10/100BASE-T

10/100BASE-T

10/100BASE-T

nxE1

nxE1

nxE1

nxE1

nxE1

nxE1

Figure 36 Block diagram for ETU2

3.6.3.1.1 TDM

This block interfaces the TDM bus by receiving and transmitting the E1s usedto carry Ethernet traffic.

3.6.3.1.2 Inverse Multiplexers

Each inverse multiplexer converts one Ethernet connection into nxE1, wheren≤16, transmitted to and received from the TDM block.

3.6.3.1.3 Ethernet

This block provides the unit’s external Ethernet interfaces. Each interface islinked to one inverse multiplexer.

The Ethernet Traffic function offers 8 priority queues in both directions to/fromthe Ethernet ports. The mapping follows IEEE 802.1D 2004 strict priorityqueuing and can be configured, per node, to use 1–8 of the queues. Whichqueue to use for untagged packets can be configured per port and direction.

34 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node


This block interfaces the PCI bus and handles control and supervision. Its mainfunctions are to collect alarms, control settings and tests.

The block communicates with the NPU over the PCI bus.

3.6.3.1.5 SPI


3.6.3.1.6 Power


354/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.7 ATM Aggregation

3.7.1 Overview

The growing demand for higher transmission capacity in access networks canbe handled by increasing the physical capacity, introducing traffic aggregationor combining the two approaches.

Traffic aggregation in MINI-LINK TN R3 is achieved by fitting an ATMAggregation Unit (AAU) in the AMM. This is typically done at hub sites whereHSDPA traffic is aggregated, thus reducing the number of required E1 links inthe northbound direction. The AAU performs ATM VP/VC cross-connectionproviding statistical gains.

Figure 37 on page 36 shows an example of how Virtual Paths (VP) and VirtualChannels (VC), carried over E1s, can be cross-connected reducing the numberof required E1s.

VP/CBR11xE1

VC/UBR+

Shared13 Mbit/s

VC/UBR+

VP/CBR 8xE1

VC/UBR+11.3 Mbit/s

VC/CBR4.7 Mbit/s

VC/CBR4.7 Mbit/sVP/CBR 8xE1

VC/UBR+11.7 Mbit/s

VC/CBR4.3 Mbit/s

VC/CBR4.3 Mbit/s

8924

MINI-LINK TNwith AAU

Figure 37 VP/VC cross-connection

Often the transmission network is used for both GSM and WCDMA traffic. TheGSM traffic is handled as ordinary TDM traffic routed in the backplane andtransported transparently through the NE while WCDMA traffic is routed to theAAU for packet aggregation before it is routed to its destination port. WCDMAtraffic comprises both R99 standard (voice and data channel up to 384 kbit/s)and HSDPA traffic. The largest aggregation gain is however obtained for theHSDPA traffic, when the low priority traffic can be transported using best effortservice categories.

Figure 38 on page 37 shows how the different traffic types are routed in thebackplane.

36 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

TDM bus

8489

LTU

AAU MMU

MMU

RAU

MMU

WCDMA

GSM

RAU

RAU

Figure 38 Traffic types

3.7.2 ATM Aggregation Unit (AAU)

The main function of the AAU is to aggregate traffic from other plug-in units inthe AMM. It is fitted in an AMM 6p B, C, D or AMM 20p.

8490

ERICSSON

AAU

Faul

tPo

wer

BR

AAU

Figure 39 AAU

The AAU has no front connectors but interfaces up to 96 E1s in the backplane.The E1s can be used as single links with G.804 mapping or combined intoIMA groups. Each G.804 link or IMA group corresponds to one internal ATMinterface and the maximum number of ATM interfaces handled by the AAU is 31.

374/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The following is a summary of the AAU functions:

• Capacity of 96xE1. 24xE1 is the default capacity and additional groups of24xE1 are available as optional features.

• 31 ATM interfaces, IMA groups or G.804

• Up to 16xE1 in one IMA group

• Cross-connection capability of 622 Mbit/s, handling 1500 Virtual ChannelConnections (VCC) and 100 Virtual Path Connections (VPC).

• Service Categories support; CBR, rt-VBR, nrt-VBR.1,2,3, UBR andUBR+MDCR

• Policing

• Shaping

• F4/F5 OAM support for Fault Management


This section describes the internal and external functions of the AAU, based onthe block diagram in Figure 40 on page 38.

8491

SPI

TDMTDM Bus

PCI Bus

SPI Bus

PowerPower Bus Secondaryvoltages

IMA

Control andSupervision

ATMCross-connect

UtopiaInterface

Figure 40 Block diagram for AAU

38 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.7.2.1.1 TDM

This block interfaces the TDM bus by receiving and transmitting nxE1 (n≤96)for aggregation. The transmitted E1s need synchronization input utilizing theNetwork Synchronization mode.

3.7.2.1.2 IMA

This block implements the Inverse Multiplexing for ATM (IMA). The ATM cellsare broken up and transmitted across multiple IMA links, then reconstructedback into the original ATM cell order at the destination.

3.7.2.1.3 ATM Cross-connectt

This block handles the ATM cross-connection of traffic on a maximum of 31ATM interfaces. Each ATM interface corresponds to either an IMA group ora G.804 link.

When setting up cross-connections, Connection Admission Control (CAC)calculations are performed in order to accept or reject new connection requestsaccording to the available bandwidth.

The function of the ATM Cross-connect block can be summarized as:

• Policing

• VP/VC Cross-connection

• Buffering and Congestion Thresholds

• Scheduling and Shaping

Policing

The policing function is used to monitor the traffic flowing through a specificconnection in order to ensure that it conforms to the configured trafficdescriptor of the connection. It fully meets the relevant requirements andrecommendations from the ATM Forum Traffic Management and ITU-T I.371.

Policing is enabled by default for all the service categories and can be disabledon a per-connection basis.

VP/VC Cross-connection

The different ATM interfaces can be cross-connected, mapping ingressconnections to egress connections and vice versa.

In a VP cross-connection only VPI numbers are associated between two ATMinterfaces. In a VC cross-connection the VPC is terminated and the ingress andegress connections are associated using both VCI and VPI numbers.

394/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Buffering and Congestion Thresholds

After the cross-connection phase, the ingress cell streams flow into thebuffering section. Buffers are provided on a per-egress ATM interface basis forthree different groups of service categories:

• Real time services (CBR, rt-VBR.1)

• Non-real time services (UBR+MDCR, nrt-VBR.1, 2,3)

• Best effort services (UBR)

Individual queues are provided for each connection of the same group.

The following congestion thresholds exist:

• CLP1 discard

• CLP0+1 discard

• Partial Packet Discard (PPD)

• Early Packet Discard (EPD)

The thresholds are dynamic because they change depending on the amountof free buffer space available. The larger the free buffer space, the higherthe threshold.

Scheduling and Shaping

Shaping is intended as a traffic limitation on the peak rate. The ATMCross-connect provides 31 independent schedulers that are individuallymapped to any of the 31 ATM interfaces. The bandwidth assigned from theschedulers to each ATM interface is shaped at a value corresponding to thephysical bandwidth of the ATM interface, for example 2 Mbit/s for a G.804 link.



The block holds a Device Processor (DP) running plug-in unit specific software.

3.7.2.1.5 SPI


40 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.7.2.1.6 Power


3.7.2.2 Fault Management

The AAU supports the handling of F4/F5 O&M functions for Fault Management(FM), according to ITU-T I.610. The following FM indications are used:

• Alarm Indication Signal (AIS), for reporting defect indications in the forwarddirection. The AIS cells at VP or VC level are sent upon one of the followingconditions:

− Receiving transmission path defect indications from the physical layer

− Detecting Loss of Cell Delineation (LCD)

− Detecting Loss of Continuity (LOC)

• Remote Defect Indication (RDI), for reporting remote defect indicationsin the backward direction. RDI is sent to the far-end from a VPC/VCCendpoint as soon as it has detected an AIS condition.

• Loop Back (LB), allowing for “operations related” information to be insertedat one location along a VPC/VCC and returned (or looped back) at adifferent location, without having to take the connection out-of-service.This capability is performed by inserting an LB cell at an accessible pointalong the VPC/VCC without disrupting the sequence of user cells whileminimizing the user cells transfer delay. This cell is looped back at adownstream point according to the information contained in its informationfield. It is used mainly for:

− On-demand connectivity monitoring

− Fault localization

− Pre-service connectivity verification

• The AAU is transparent to Continuity Check (CC) cells, for monitoringcontinuity and detection of ATM layer defects in real time.

414/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.8 Traffic Routing

The main function of the microwave hub site is to collect traffic carried overmicrowave radio links from many sites and aggregate it into a higher capacitytransmission link through the access network towards the core network. Thetransmission link northbound may be microwave or optical.

These hub sites have usually been built by connecting individual microwaveRadio Terminals with cables through Digital Distribution Frames (DDF) andexternal cross-connection equipment.

MINI-LINK TN R3 provides a traffic routing function that facilitates the handlingof traffic aggregation. This function enables interconnection of all trafficconnections going through the NE. This means that an aggregation site canbe realized using one AMM housing several Radio Terminals with all thecross-connections done in the backplane.

Each plug-in unit connects nxE1 to the backplane, where the traffic iscross-connected to another plug-in unit. The E1s are unstructured withindependent timing.

One way of using this function at a large site is to cross-connect traffic fromseveral Radio Terminals to one LTU 155 (63xE1) for further connection tothe core network.

At a smaller site, it is possible to collect traffic from several Radio Terminalswith a low traffic capacity into one with a higher traffic capacity.

Plug-in Unit

Plug-in Unit

Plug-in Unit

Plug-in Unit

Plug-in Unit

TDM bus

nxE1 nxE1 nxE1 nxE1 nxE1

≈400xE1

6626

Plug-in Unit

nxE1Plug-in

Unit

nxE1Plug-in

Unit

nxE1Plug-in

Unit

nxE1

Figure 41 Traffic routing

42 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

Note that the TDM bus can carry close to 400 uni-directional E1s in AMM 20pand AMM 6p, half of this in AMM 2p, but some of the capacity is allocated forDCN and control information. To facilitate future software functional upgrades itis not recommended to route traffic on more than 366 uni-directional E1s overthe AMM 6p and AMM 20p TDB bus, half of this in AMM 2p.

The traffic routing function is controlled from the EEM, locally or remotely.

Traffic configuration can also be done using the SNMP interface.

3.8.1 MINI-LINK Connexion

The MINI-LINK Connexion application provides a way to provision end-to-endE1 connections in a network. The network can be planned in advance withoutthe need for the actual network. When the pre-configured E1 connections areapplied to the real network a consistency check is done.

All operations related to the E1 provisioning are done from a topology mapwith a graphical presentation of the E1 connections. Color codes are used tovisualize alarm status. Detailed alarm info and status are obtained by clickingon a connection on the map.

A number of different reports can be extracted periodically or on demand toview performance data and statistics related to an E1 end-to-end connection.

For more information, see MINI-LINK Connexion User Manual.

434/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.9 Protection Mechanisms

This section describes the protection mechanisms provided by the Basic Node.Protection of the radio link is described in Section 4.6 on page 81.

3.9.1 Overview

To ensure high availability, MINI-LINK TN R3 provides protection mechanismson various layers in the transmission network as illustrated in Figure 42 onpage 44.

• Network layer protection using the 1+1 E1 SNCP mechanism providesprotection for the sub-network connection a-b in Figure 42 on page 44.Network layer protection uses only signal failure as switching criterion.

• Physical link layer protection using MSP 1+1 indicated by the link cbetween two adjacent NEs 1 and 2 in Figure 42 on page 44. Physicallink layer protection uses both signal failure and signal degradation asswitching criteria.

• By routing the protected traffic in parallel through different physical units,equipment protection can also be achieved. An example using two plug-inunits is shown for the NEs 1 and 2 in Figure 42 on page 44.

1

2

43

65

a

b

c

=

= Plug-in unit6627

Equipment protection

Network layer protectionPhysical link layer protection

Network Element (NE)

Figure 42 MINI-LINK TN R3 provides high availability through variousprotection mechanisms

44 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

Network layer and physical link layer protection share the followingcharacteristics:

Permanently Bridged Identical traffic is transmitted on the active and thepassive physical link/connection.

Uni-directional Only the affected direction is switched to protection.The equipment terminating the physical link/connectionin either end will select which line to be activeindependently.

Non-revertive No switch back to the original link/connection isperformed after recovery from failure. The original activelink/connection is used as passive link/connection afterthe protection is re-established.

1+1 One active link/connection and one passive (standby)link/connection.

Automatic/Manualswitching mode

In automatic mode, the switching is done based on signalfailure or signal degradation. Switching can also beinitiated from the management system provided that thepassive link/connection is free from alarms.In manual mode, the switching is only initiated fromthe management system, regardless of the state of thelinks/connections.

3.9.2 Network layer protection

3.9.2.1 1+1 E1 SNCP

1+1 E1 Sub-Network Connection Protection (1+1 E1 SNCP) is a protectionmechanism used for network protection on E1 level, between two MINI-LINKTN R3 NEs. It is based on the simple principle that one E1 is transmitted ontwo separate E1 connections.

The switching is performed at the receiving end where the two connections areterminated. It switches automatically between the two incoming E1s in orderto use the better of the two. The decision to switch is based on signal failureof the signal received (LOS or AIS).

At each end of the protected E1 connection, two E1 connections must beconfigured to form a 1+1 E1 SNCP group.

An operator may also control the switch manually.

The connections may pass through other equipment in between, providedthat AIS is propagated end-to-end.

The 1+1 E1 SNCP function is independent of the 1+1 radio protection andthe MSP 1+1.

454/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6632

TxRx Tx

Rx

Protected E1

Unprotected E1Unprotected E1

Protected E1

1+1 E1 SNCP group1+1 E1 SNCP group

Link or sub-network

Figure 43 1+1 E1 SNCP principle

Performance data is collected and fault management is provided for unprotectedas well as protected E1 interfaces (that is the 1+1 E1 SNCP group). This givesaccurate information on the availability of network connections.

3.9.2.2 Ring Protection

6628

Ring

Tree

Star

Figure 44 Network topologies

The 1+1 E1 SNCP mechanism described in the previous section can be used tocreate protected ring structures in the microwave network. In a ring topology, allnodes are connected so that two nodes always have two paths between them.

An E1 connection entering a ring at one point and exiting at another point cantherefore be protected with a 1+1 E1 SNCP group configured at each end ofthe connection. The traffic is transmitted in both directions of the ring and thetraffic is received from two directions at the termination point.

46 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

In this solution, the ring network can tolerate one failure without losingtransmission. When the failure re-occurs, the affected connections are switchedin the other direction.

In a MINI-LINK TN R3 network, these ring structures can be built using PDHRadio Terminals with capacities of up to 32x2 Mbit/s, and using SDH RadioTerminals with the LTU 155 (STM-1 interface) with capacities up to 63x2 Mbit/s.

Capacity is distributed from a common feeder node to the ring nodes where it isdropped off to star or tree structures as shown in Figure 45 on page 47.

As an example, consider the nodes A and E in Figure 45 on page 47. To protectthe connection from A to E the two alternative connections from A to E must bedefined as a 1+1 E1 SNCP group at A and as a 1+1 E1 SNCP group at E.

Similarly, to protect the connection from A to C, the two alternative connectionsbetween A and C must also be configured as two 1+1 E1 SNCP groups atA and C.

6629

A

F

D

B

EC

Figure 45 Example of ring protection with 1+1 E1 SNCP

The 1+1 E1 SNCP function can be used to build protection in more complextopologies than rings, using the same principle.

474/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.9.3 MSP 1+1

The STM-1 interface supports Multiplexer Section Protection (MSP) 1+1.This SDH protection mechanism provides both link protection and equipmentprotection. Its main purpose is to provide maximum protection at the interfacebetween the microwave network and the optical network.

MSP 1+1 requires two LTU 155 plug-in units configured to work in an MSP 1+1pair, delivering only one set of 63xE1 (or 21xE1) to the backplane at a time asillustrated in Figure 46 on page 48. The unit intercommunication is done overthe BPI bus.

Active LTU155e/o

63xE1

SDH Mapping

Passive LTU155e/o

STM-1 electrical or optical

SDH Mapping

MSP 1+1 Switch

7468

BPI

TDM Bus

Figure 46 Two LTU 155e/o plug-in units in an MSP 1+1 configuration

The switching is done automatically if the following is detected:

• Signal Failure (SF): LOS, LOF, MS-AIS or RS-TIM

• Signal Degradation (SD) based on MS-BIP Errors (BIP-24)

• Local equipment failure

The operator can also initiate the switching manually.

The switch logic for MSP 1+1 is handled by the unit’s Device Processor.

48 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

E1->VC-12->VC-4

SF/SD

63xE1

MSP SwitchController

MS/RS

MS/RS

Tx

Tx

Tx

Rx

Rx

Rx

RxSwitch

6633

LTU 155

LTU 155

E1->VC-12->VC-4

63xE1

MSP SwitchController

Figure 47 MSP 1+1 principle

494/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.9.4 Equipment and Line Protection

9719

AMM 2p B AMM 2p BMMU2 E 155MMU2 E 155 MMU2 E 155

MMU2 E 155

ADM ADM

Figure 48 High capacity hop protected with ELP

The Equipment and Line Protection (ELP) functionality is able to simultaneouslyprotect the STM-1 line interface and the radio equipment against any singlepoint of failure (e.g. the single MMU). This is commonly used to protect a highcapacity hop.

On the radio side, it uses a single frequency (hot standby configuration). In thismode the radio section performs protection switching on the transmitter side.The ADMs at both ends carry out the line protection.

A full MINI-LINK high capacity equipment protection can also be achievedby using only one optical interface on the ADM (without the MSP protectionin the ADM).

In ELP configuration, in order to save radio bandwidth, only one of the twomultiplex sections of the MSP (working/protection) is sent over the air. For thisreason some limitations apply to the data contained in the MSOH, which (ifused) must be bridged on both channels.

The ADM shall be configured with MSP in unidirectional mode.

With DCCm configured as protected, it is not possible to use two different DCCconnections on working and protection section, but the same traffic shall bebridged on both sides.

50 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.9.5 Enhanced Equipment Protection

Enhanced Equipment Protection (EEP) (optical) protects the STM-1 line onMMU2 E/F 155. Through a Small Form Factor Pluggable (SFP), see Section7.3 on page 128, plus an external optical combiner/splitter, see Figure 49 onpage 51, the STM-1 input/output are protected; while one MMU Tx laser istransmitting, the other one must be switched off (Laser Shut Down). See alsoMMU2 F 155 in Section 4.2 on page 61.

9358

Figure 49 Optical splitter/combiner

514/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.10 Synchronization

3.10.1 Overview

MINI-LINK TN is by default working in Free Running mode. In this mode thenode is not a part of the synchronization network, and does not maintain aSEC. The node behavior can be described by how the different protocols areprocessed:

• Unstructured primary rate PDH channels are passed transparently exceptfor timing recovery and jitter attenuation. This is also valid for robbedtimeslot DCN channels.

• STM/STS interfaces are configured to take outgoing synch from localoscillator or loop timing. If SSM is enabled “Do Not Use” is transmitted.

• PDH primary rate channels terminated in an AAU/ATM switch areconfigured to take outgoing synch from local oscillator or loop timing.

• PDH primary rate channels used for Ethernet over PDH will have outgoingsynch generated by the local oscillators.

MINI-LINK TN ETSI can from release 3.1 also be configured to NetworkSynchronized mode where the node maintains a SEC and distributessynchronization and synchronization quality level status on cross connectedPDH channels (ITU-T G.813).

Note that unstructured primary rate PDH channels are still passed transparentlyas in the Free Running mode, but now with reduced jitter. This is also valid forPDH connections that are used for DCN including robbed timeslot DCN.

With Network Synchronized mode it possible to build a synchronized networkwhere all the NEs are synchronized to the same source. Figure 50 on page53 shows an example of a network where the synchronization information iscarried to all the NEs through an assigned path. In case of link failures thesynchronization may be reestablished using the unassigned synchronizationpaths.

52 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

Network Element

Assigned synchronization path

Unassigned synchronization path

9531

Figure 50 Master-slave synchronized network

In this mode MINI-LINK TN will use the Node Clock on all the protocol layersgenerated in the node.

The Network Synchronized mode includes the following functions:

3.10.2 SDH Equipment Clock

The SEC function maintains an equipment clock with network reference clockselection, clock generation, filtering and redundancy. As illustrated in Figure 51on page 54 a list of interfaces can be selected and prioritized as candidatesfor synchronization input to the SEC. All E1 and STM-1 interfaces, or whenprotected their 1+1 E1 SNCP or MSP 1+1 group, are available for nomination.It is also possible to use one of the E1 ports on the NPU1 B, NPU2 , and NPU3as an external 2048 kHz synchronization clock input interface.

The SEC will select and do automatic synchronization trail restoration basedon the priority table and the status of the inputs. In the event of failure of allsynchronization source inputs, the SEC will enter holdover mode using its owninternal clock as source. (Note: G.813 performance during trail restorationand holdover requires at least one MMU2 C, AAU or LTU 155 plug-in unit inthe AMM)

The SEC clock is distributed throughout the magazine. All terminated protocollayers interfaces (e.g. STM-1 and E1 from AAU) can be individually configuredto follow the SEC or to do Loop Timing, that is using the recovered receiveclock (RxClock) on the outgoing link.

534/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.10.3 Status

The synchronization status functions are used to propagate and signal thequality level of the SEC to the node interfaces.

The Synchronization Status Propagation logic distributes synchronizationstatus for transmission of synchronization status messages (SSM) on interfacessupporting and configured for this.

The Squelch logic distributes information on poor or lost synchronization inputto interfaces that cannot signal synchronization status messages, for these tosend AIS. From management squelch can be enabled/disabled for the wholenode as well as individually for all outgoing SDH and PDH interfaces.

Towards protected interfaces, squelch are configured onto the protected (1+1)interface, not on the individual interfaces.

The squelch ‘Wait To Restore Time’ is also configurable per interface.When protected interfaces are nominated to be synchronization sourcescandidates they should have their ‘Wait To Restore Time’ set longer then the‘Hold Off Time’ of the protected interface, to avoid unnecessary switching ofsynchronization sources.

9745

Free Running

Synchronization Logic

Squelch

E11+1 E1 SNCP

STM-1MSP 1+1

2 MHz

Interfaces

E1

Interfaces

STM-1

NetworkSynchronization

SynchronizationStatus Propagation

Selection

Loop Timingor NE Timing

T1

T2

T3

T0

T0, T1, T2 and T3:ITU-T SDH Equipment Clock (SEC) names

Logic

SEC Status

Figure 51 MINI-LINK TN Synchronization functions

54 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.11 Equipment Handling

The system offers several functions for easy operation and maintenance.

• Plug-in units can be inserted while the NE is in operation. This enablesadding of new Radio Terminals or other plug-in units without disturbingexisting traffic.

• Plug-in units can be removed while the NE is in operation.

• Each plug-in unit has a Board Removal button (BR). Pressing this buttoncauses a request for removal to be sent to the control system.

• When replacing a faulty plug-in unit, the new plug-in unit automaticallyinherits the configuration of the old plug-in unit.

• The system configuration is stored non-volatile on the RMM on the NPUand can also be backed up and restored using a local or central FTPserver. The RMM storage thus enables NPU replacement without using aFTP server.

• The backplane in all AMMs has an digital serial number which is also storedon the NPUs RMM. When inserting an NPU, for example as a replacement,the serial numbers are compared on power up.

• When an RAU is replaced, no new setup has to be performed.

• Various restarts can be ordered from the management system. A coldrestart can be initiated for an NE or single plug-in unit, this type of restartdisturbs the traffic. A warm restart is only available for the whole NE. Thiswill restart the control system and will not affect the traffic. This is possibledue to the separated control and traffic system.

• All plug-in units are equipped with temperature sensors. Overheatedboards, which exceed limit thresholds, are put in reduced service or outof service by the control system. This is to avoid hardware failures incase of a fan failure. The plug-in unit is automatically returned to normaloperation when temperature is below the high threshold level. There aretwo thresholds:

− Crossing the high temperature threshold shuts down the plug-in unit’scontrol system (reduced operation). The traffic function of the plug-inunit will still be in operation.

− Crossing the excessive temperature threshold shuts down the entireplug-in unit (out of service).

• Access to inventory data like software and hardware product number,serial number and version. User defined asset identification is supported,enabling tracking of hardware.

554/1555-CSH 109 32/1-V1 Uen B 2007-09-14


3.12 MINI-LINK E Co-siting

A SMU2 can be fitted in an AMM 2p B, AMM 6p B/C/D or AMM 20p to interfaceMINI-LINK E equipment on the same site. The following interfaces are provided:

• 1xE3 + 1xE1

• 1xE2 or 2xE2

• 2xE1

• 2xE0 (2x64 kbit/s) used for IP DCN

• O&M (V.24) access server

ERICSSON

SMU2

O&M

E3:3A E2:3B-3C E1:2A-2B DIG SC:1A-1B

Faul

tPo

wer

BR

E3/ 2xE2

2xE0O&M

SMU2

2xE1

6728

Figure 52 SMU2

All the traffic capacities are multiplexed/demultiplexed to nxE1 for connectionto the TDM bus.

SMU2

2xE0 2xE1, 1xE2, 2xE2 or 1xE3 + 1xE1

MINI-LINK E

2xE1 to 17xE1

7469

MINI-LINK TN

TDM Bus

Figure 53 MINI-LINK E co-siting

56 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Basic Node

3.13 Unstructured E3 Interface

The E3 interface on the SMU2 can be used to provide unstructured E3 trafficover a 1+1 radio link. Each side of the radio link comprise:

• Two RAUs

• Two antennas or one antenna with a power splitter

• Two MMU2s

• One SMU2

• Two radio cables for interconnection

The radio terminal is protected (1+1) with 34+2 Mbit/s traffic capacity.

9907

MMU2 RAU

MMU2 RAU

MMU2

MMU2

RAU

RAU

SMU2 SMU2E3 E3

Figure 54 Transmission solution for unstructured E3

574/1555-CSH 109 32/1-V1 Uen B 2007-09-14


58 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4 Radio Terminals

4.1 Overview

A Radio Terminal provides microwave transmission from 2x2 to 155 Mbit/s,operating within the 6–38 GHz frequency bands, utilizing C-QPSK and 16, 64or 128 QAM modulation schemes. It can be configured as unprotected (1+0) orprotected (1+1).

NPU 8x2

INF

OR

MAT

ION

MM

U2 4-34

MM

U2 4-34

LTU 16x2

LTU 155e/o

-48VPower A

-48V

FAN UNIT

Power BAlarm B

Alarm A

Fault Power

8483

NPU1 B MM

U2 4-34

15 GH

z

15 G

Hz

RADIOCABLE


15 GH

z

15 G

Hz

RADIOCABLE


15 GHz

15 GHz

ALARMPOWER

ALIGNMENT

RADIOCABLE

Figure 55 An unprotected (1+0) Radio Terminal (grayed)

An unprotected (1+0) Radio Terminal comprises:

• One RAU

• One antenna

• One MMU

594/1555-CSH 109 32/1-V1 Uen B 2007-09-14


• One radio cable for interconnection

A protected (1+1) Radio Terminal comprises:

• Two RAUs

• Two antennas or one antenna with a power splitter

• Two MMUs

• Two radio cables for interconnection

Automatic switching can be in hot standby or in working standby (frequencydiversity). Receiver switching is hitless.

In hot standby mode, one transmitter is working while the other one is instandby, it is not transmitting but ready to transmit if the active transmittermalfunctions. Both RAUs are receiving signals and the best signal is usedaccording to an alarm priority list.

In working standby mode, both radio paths are active in parallel using differentfrequencies.

For more information on 1+1 protection, see Section 4.6 on page 81.

Radio Cables

The radio cables between the Radio and Modem Units in the magazines areavailable in three different diameters:

• Ø7,6 mm — with lengths up to 100 m

This cable can be directly connected to the modem unit.

• Ø10 mm — with lengths up to 200 m or between 100 and 200 m

• Ø16 mm — with lengths between 200 and 400 m

60 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.2 Modem Unit (MMU)

4.2.1 Overview

The MMU is the indoor part of the Radio Terminal and determines the trafficcapacity and modulation. It is available in the following types:

MMU2 B A traffic capacity agile plug-in unit for C-QPSKmodulation, used for the following traffic capacities inMbit/s:

• 2xE1, 4xE1, 8xE1, 17xE1

MMU2 C A traffic capacity and modulation agile plug-in unit,used for the following modulation schemes and trafficcapacities in Mbit/s:

• C-QPSK: 2xE1, 4xE1, 8xE1, 17xE1

• 16 QAM: 8xE1, 17xE1, 32xE1

MMU2 D A high capacity PDH plug-in unit, used for the followingmodulation schemes and traffic capacities in Mbit/s:

• 16 QAM: 22xE1, 46xE1

• 128 QAM: 35xE1, 75xE1

MMU2 E 155 A high capacity SDH plug-in unit, used for the followingmodulation schemes and traffic capacities:

• 16 QAM: STM-1 + 1xE1

• 64 QAM: STM-1 + 1xE1

• 128 QAM: STM-1 + 1xE1

MMU2 F 155 A high capacity SDH plug-in unit with XPIC support,see Section 4.2.2.10 on page 68, used for the followingmodulation schemes and traffic capacities in Mbit/s.XPIC is only used in combination with 128 QAM, if notused MMU2 F 155 has the same modulation schemesand traffic capacities as MMU2 E 155:

• 16 QAM: STM-1 + 1xE1

• 64 QAM: STM-1 + 1xE1

• 128 QAM: 2xSTM-1 + 2xE1 (requires 2xMMU2 E/F155)

614/1555-CSH 109 32/1-V1 Uen B 2007-09-14


MMU2 B and MMU2 C have the same functionality regarding mechanics andinterfaces. However, there is an important difference when it comes to RAUcompatibility:

• MMU2 B and MMU2 C in C-QPSK mode are compatible with RAU1, RAU2,RAU1 N and RAU2 N.

• MMU2 C in 16 QAM mode is compatible with RAU1 N and RAU2 N.

MMU2 D is not compatible with MMU2 B or MMU2 C, that is it can not becombined with MMU2 B or MMU2 C in a 1+0 or 1+1 hop. MMU2 D can beplaced in the same AMM as MMU2 B or MMU2 C but can not be part of thesame radio terminal.

9720

MMU2 C

MMU2 C

60V RAUFaul

tPo

wer

BR

ERICSSON

MMU2 B

MMU2 B

60V RAUFaul

tPo

wer

BR

ERICSSON

RAU

MMU2 D

60V RAUFaul

tPo

wer

BR

ERICSSON

MMU2 D

Figure 56 MMU2 B, C and D

MMU2 E 155 and MMU2 F 155 have the same functionality regardingmechanics and interfaces except for XPIC support on MMU2 F 155. MMU2 E155 and MMU2 F 155 are compatible with both RAU2 N and RAU2 X. For theSTM-1 interface a Small Form Factor Pluggable (SFP) is needed. The SFP canbe either electrical (SFPe) or optical (SFPo), see Section 7.3 on page 128.

62 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

9696

MMU2 E 155 60V RAU

Faul

t

Pow

er

BRERICSSON

MMU2 F 155 60V RAU

Faul

t

Pow

er

BRERICSSON XPIC

TX

SFP

SFP

STM

-1S

TM-1

RX

TX RX

Figure 57 MMU2 E and F 155. Note: MMU2 F 155 has XPIC support.

4.2.2 Functional Block

This section describes the internal and external functions of the MMU, basedon the block diagram in Figure 58 on page 63.

6637

Radio Frame Multiplexer

Modulator

Cable Interface

DemodulatorRadio Frame Demultiplexer

SPI

TDM Multiplexer/

Demultiplexer

TDM Bus

PCI Bus

SPI Bus

HCC HCC

RCC

RAU

PowerPower Bus

Secondary voltages

DCC

Traffic

DCC

Traffic

BPI Bus (1+1) BPI Bus (1+1)


Figure 58 Block diagram for MMU2

634/1555-CSH 109 32/1-V1 Uen B 2007-09-14


9840

Radio FrameMultiplexer

Modulator

CableInterface

DemodulatorRadio FrameDemultiplexer

SPI

TDM(Wayside traffic,

E1 only)TDM Bus

PCI Bus

SPI Bus

HCC HCC

RCC

RAU

PowerPower Bus

Secondaryvoltages

DCC

Traffic

DCC

Traffic

BPI Bus (1+1) BPI Bus (1+1)


XPIC(MMU2 F 155)

STM-1Line interface

High-speed bus

Figure 59 Block diagram for MMU2 E/F 155

4.2.2.1 TDM Multiplexer/Demultiplexer

This block interfaces the TDM bus by receiving and transmitting the traffic(nxE1) and DCC.

It performs 2/8 and 8/34 multiplexing, depending on the traffic capacity, forfurther transmission to the Radio Frame Multiplexer.

In the receiving direction, it performs 34/8 and 8/2 demultiplexing , dependingon the traffic capacity. The demultiplexed traffic and DCC are transmitted tothe TDM bus.

In a protected system, the block interfaces the BPI bus, see Section 4.6.2on page 81.

Note: The TDM block in MMU2 E/F 155 performs no multiplexing/demultiplexing. The traffic in the receiving direction equals 1xE1.

Note: The high-speed bus will be possible to use with future functionality suchas integrated ADM. It is currently not enabled.

64 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.2.2.2 Radio Frame Multiplexer

The Radio Frame Multiplexer handles multiplexing of different data types intoone data stream, scrambling and FEC encoding.

In a protected system, the block interfaces the BPI bus, see Section 4.6.2on page 81.

The following data types are multiplexed into the composite data stream tobe transmitted over the radio path:

• Traffic

• Data Communication Channel (DCC)

• Hop Communication Channel (HCC)

Traffic

The transmit traffic data is first sent to the multiplexer to assure data rateadaptation (stuffing). If no valid data is present at the input, an AIS signal isinserted at nominal data rate. This means that the data traffic across the hop(only for PDH) is replaced with ones (1).

DCC

DCC comprises nx64 kbit/s channels used for DCN communication over thehop, where 2≤n≤9 depending on traffic capacity and modulation.

HCC

The Hop Communication Channel (HCC) is used for the exchange of controland supervision information between near-end and far-end MMUs.

Multiplexing

The three different data types together with check bits and frame lock bits aresent in a composite data format defined by the frame format that is loaded intoa Frame Format RAM. The 12 frame alignment signal bits are placed at thebeginning of the frame. Stuffing bits are inserted into the composite frame.

Scrambling and FEC Encoding

The synchronous scrambler has a length of 217–1 and is synchronized eacheighth frame (super frame). For C-QPSK, the FEC bits are inserted accordingto the frame format and calculated using an interleaving scheme. ReedSolomon coding is used for 16 QAM.

654/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.2.2.3 Modulator

The composite data stream from the Radio Frame Multiplexer is modulated, D/Aconverted and pulse shaped in a Nyqvist filter to optimize transmit spectrum.

Two different modulations techniques are used:

• C-QPSK (Constant envelope offset Qaudrature Phase Shift Keying) isan offset QPSK modulating technique. It has a high spectrum efficiencycompared to other constant envelope modulation.

• Square QAM (Quadrature Amplitude Modulation), consisting of twoindependent amplitude modulated quadratures. The carrier is amplitudeand phase modulated. The technique doubles the spectrum efficiencycompared to C-QPSK.

The Modulator consists of a phase locked loop (VCO) operating at 350 MHz.For test purposes an IF loop signal of 140 MHz is generated by mixing with a490 MHz signal.

4.2.2.4 Cable Interface

The following signals are frequency multiplexed in the Cable Interface forfurther distribution through a coaxial cable to the outdoor RAUs:

• 350 MHz transmitting IF signal

• 140 MHz receiving IF signal

• DC power supply

• Radio Communication Channel (RCC) signal as an Amplitude Shift Keying(ASK) signal

In addition to the above, the cable interface includes an over voltage protectioncircuit.

4.2.2.5 Demodulator

The received 140 MHz signal is AGC amplified and filtered prior to conversionto I/Q baseband signals. The baseband signals are pulse shaped in a Nyqvistfilter and A/D converted before being demodulated.

4.2.2.6 Radio Frame Demultiplexer

On the receiving side the received composite data stream is demultiplexed andFEC corrected. The frame alignment function searches and locks the receiverto the frame alignment bit patterns in the received data stream.

66 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

Descrambling and FEC Decoding

For C-QPSK, error correction is accomplished using FEC parity bits incombination with a data quality measurement from the Demodulator. A ReedSolomon decoder is used for 16 QAM.

The descrambler transforms the signal to its original state enabling theDemultiplexer to properly distribute the received information to its destinations.

Demultiplexing

Demultiplexing is performed according to the frame format used. TheDemultiplexer generates a frame fault alarm if frame synchronization is lost.The number of errored bits in the traffic data stream is measured using paritybits. These are used for BER detection and performance monitoring. Stuffingcontrol bits are processed for the traffic and service channels.

Traffic

On the receiving side the following is performed to the traffic data:

• AIS insertion (at signal loss or BER≤10-3)

• AIS detection

• Elastic buffering and clock recovery

• Data alignment compensation and measurement (to enable hitlessswitching)

• Hitless switching (for 1+1 protection)

DCC

On the receiving side, elastic buffering and clock recovery is performed onthe DCC.

HCC

The Hop Communication Channel (HCC) is used for the exchange of controland supervision information between near-end and far-end MMUs.

4.2.2.7 Control and Supervision


674/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The block holds a Device Processor (DP) running plug-in unit specific software.It handles BER collection and communicates with processors in the RAUthrough the RCC.

Exchange of control and supervision data over the hop is made through theHCC.

4.2.2.8 SPI


4.2.2.9 Power


Furthermore, this block provides a stable voltage for the RAU, distributed inthe radio cable.

4.2.2.10 Cross Polarization Interference Canceller

MMU2 F 155 is equipped with Cross Polarization Interference Canceller (XPIC)functionality.

Microwave signals can be transmitted in two separate and independent(orthogonal) polarizations, vertical and horizontal. The signals can betransmitted at the same time using one dual polarized antenna. The wantedpolarization is called co-polarization and the unwanted/interference polarizationis called cross-polarization.

Even though the polarizations are orthogonal there is a small interferencebetween them, in the antennas and due to propagation effects over thehop. The effect of this interference needs to be cancelled out with the XPICfunctionality

In XPIC, each polarization path receives both the polar signal and thecross-polar signal. The receiver subtracts the cross-polar signal from the polarsignal and cancels the cross-polar interference. XPIC processes and combinesthe signals from the two receiving paths to recover the original, independentsignals.

An XPIC solution doubles the wireless link capacity and enables operators toreduce cost in terms of their frequency license fee.

68 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.3 Radio Unit (RAU)

4.3.1 Overview

The basic function of the Radio Unit (RAU) is to generate and receive the RFsignal and convert it to/from the signal format in the radio cable, connectingthe RAU and the MMU. It can be combined with a wide range of antennas inintegrated or separate installation. The RAU connects to the antenna at thewaveguide interface. Disconnection and replacement of the RAU can be donewithout affecting the antenna alignment.

DC power to the RAU is supplied from the MMU through the radio cable.

The RAU is a weatherproof box painted light gray, with a handle for lifting andhoisting. There are also two hooks and catches to guide it for easier handling,when fitting to or removing from an integrated antenna. It comprises a cover,vertical frame, microwave sub-unit, control circuit board and filter unit.

The RAU is independent of traffic capacity. The operating frequency isdetermined by the RAU only and is pre-set at factory and configured on siteusing the LCT. Frequency channel arrangements are available according toITU-R and ETSI recommendations. For detailed information on frequencyversions, see the Product Catalog and MINI LINK TN ETSI ProductSpecification.

Two types of mechanical design exist, RAU1 and RAU2.

RAU1 RAU2

RADIOCABLE


8458

Figure 60 RAU1 and RAU2 mechanical design

694/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.3.2 External Interfaces

RADIOALARM

POWERALIGNMENT

RADIO CABLE

8464

4

4 21 3

1 2 3

ALIGNMENTRADIOCABLE

POWERALARM

Figure 61 External interfaces, RAU1 and RAU2 mechanical design

Item Description

1 Radio cable connection to the MMU, 50 Ω N-type connector. Theconnector is equipped with gas discharge tubes for lightning protection.

2 Protective ground point for connection to mast ground.

3 Test port for antenna alignment.

4 Red LED: Unit alarm. Green LED: Power on.

4.3.3 RAU Types

A RAU is designated as RAUX Y F, for example RAU2 N 23. When ordering,additional information about frequency sub-band and output power version isnecessary. The letters have the following significance:

• X indicates mechanical design 1 or 2.

• Y indicates MMU compatibility as follows:

− "blank", for example RAU2 23, indicates compatibility with a C-QPSKMMU.

− N or X, for example RAU2 N 23, indicates compatibility with a C-QPSKMMU and a QAM MMU.

70 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

− Xu, for example RAU2 Xu 23, indicates compatibility with a C-QPSKMMU and a QAM MMU within ML TN together with an optional feature(released in TN 4).

• F indicates frequency band.


This section describes the RAU internal and external functions based on theblock diagrams in Figure 62 on page 71and Figure 63 on page 72.

Transmit IF Signal

Processing

DC/DC Converter

Secondary Voltages

Cab

le In

terfa

ce

Bra

nchi

ng F

ilter

RCCControl and Supervision Processor

Alarm and

Control

DC

MMU

Alignment Port

Antenna

6623

Transmit RF Oscillator

Power Amplifier

Transmit IF Demodulator

Filter and Amplifier

RF Loop

Low Noise Amplifier

Received Signal

Strength Indicator

Receive RF Oscillator

Down- converter 1

Receive IF Oscillator

Down- converter 2

Figure 62 Block diagram for RAU1 and RAU2

714/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Transmit IF Signal

Processing

DC/DC Converter

Secondary Voltages

Cab

le In

terfa

ce

Bra

nchi

ng F

ilter

RCCControl and Supervision Processor

Alarm and

Control

DC

MMU

Alignment Port

Antenna

6624


Power Amplifier


Low Noise Amplifier

Received Signal

Strength Indicator

Receive RF Oscillator

RF Loop

Down- converter 1

Receive IF Oscillator

Down- converter 2

Transmit IF Oscillator

Up- converter 1

Transmit RF Oscillator

Up- converter 2

Figure 63 Block diagram for RAU1 N and RAU2 N


• Transmit IF signal, a modulated signal with a nominal frequency of 350MHz.

• Up-link Radio Communication Channel (RCC), an Amplitude Shift Keying(ASK) modulated command and control signal with a nominal frequencyof 6.5 MHz.

• DC supply voltage to the RAU.

Similarly, the outgoing signals from the RAU are multiplexed in the CableInterface:

• Receive IF signal, which has a nominal frequency of 140 MHz.

• Down-link RCC, an ASK modulated command and control signal with anominal frequency of 4.5 MHz.

In addition to the above, the Cable Interface includes an over voltage protectioncircuit.

72 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.3.4.2 Transmit IF Signal Processing

The input amplifier is automatically gain-controlled so that no compensation isrequired due to the cable length between the indoor and outdoor equipment.The level is used to generate an alarm, indicating that the transmit IF signallevel is too low due to excessive cable losses.

4.3.4.3 Transmit IF Demodulator

The transmit IF signal is amplified, limited and demodulated. The demodulatedsignal is fed to the Transmit RF Oscillator onto the RF carrier.

4.3.4.4 Transmit IF Oscillator

The frequency of the transmitter is controlled in a Phase Locked Loop (PLL),including a Voltage Control Oscillator (VCO). An unlocked VCO loop generatesa transmitter frequency alarm.

4.3.4.5 Up-converter 1

The first up-converter gives an IF signal of approximately 2 GHz.

4.3.4.6 Filter and Amplifier

The converted signal is amplified and fed through a bandpass filter.

4.3.4.7 Transmit RF Oscillator

This oscillator is implemented in the same way as the Transmit IF Oscillator.

4.3.4.8 Up-converter 2

The transmit IF signal is amplified and up-converted to the selected radiotransmit frequency.

4.3.4.9 Power Amplifier

The transmitter output power is controlled by adjustment of the gain in thePower Amplifier. The output power is set in steps of 1 dB from the LCT. It isalso possible to turn the transmitter on or off utilizing the Power Amplifier.

The output power signal level is monitored enabling an output power alarm.

4.3.4.10 RF Loop

The RF Loop is used for test purposes only. When the loop is set, thetransmitter frequency is set to receiver frequency and the transmitted signal inthe Branching Filter is transferred to the receiving side.

734/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.3.4.11 Branching Filter

On the transmitting side, the signal is fed to the antenna through an outputbranching filter. The signal from the antenna is fed to the receiving side throughan input branching filter. The antenna and both branching filters are connectedwith an impedance T-junction.

4.3.4.12 Low Noise Amplifier

The received signal is fed from the input branching filter into a Low NoiseAmplifier.

4.3.4.13 Receive RF Oscillator

The frequency of the receiver is controlled in a PLL, including a VCO. Anunlocked VCO loop generates a receiver frequency alarm.

4.3.4.14 Down-converter 1

The first down-converter gives an IF signal of approximately 1 GHz.

4.3.4.15 Receive IF Oscillator

This oscillator is used for the second downconversion to 140 MHz and consistsof a PLL, including a VCO. The VCO is also used for adjustment of the received140 MHz signal (through a control signal setting the division number in theIF PLL). A frequency error signal from the MMU is used to shift the receiveroscillator in order to facilitate an Automatic Frequency Control (AFC) loop.

4.3.4.16 Down-converter 2

The signal is down-converted a second time to the IF of 140 MHz.

4.3.4.17 Received Signal Strength Indicator (RSSI)

A portion of the 140 MHz signal is fed to a calibrated detector in the RSSI toprovide an accurate receiver input level measurement. The measured level isaccessible either as an analog voltage at the alignment port or in dBm from themanagement software.

The RSSI signal is also used for adjustment of the output power by means ofthe Automatic Transmit Power Control (ATPC).

4.3.4.18 Control and Supervision Processor

The Control and Supervision Processor has the following main functions:

• Collected alarms and status signals from the RAU are sent to the indoorMMU processor. Summary status signals are visualized by LEDs on theRAU.

74 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

• Commands from the indoor units are executed. These commands includetransmitter activation/deactivation, channel frequency settings, outputpower settings and RF loop activation/deactivation.

• The processor controls the RAU’s internal processes and loops.

4.3.4.19 DC/DC Converter

The DC/DC Converter provides a stable voltage for the RAU.

754/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.4 Antennas

4.4.1 Description

The antennas range from 0.2 m up to 3.7 m in diameter, in single and dualpolarized versions. All antennas are "compact", that is the design is compactwith a low profile. The antennas are made of aluminum and painted light gray.All antennas have a standard IEC 154 type B waveguide interface that can beadjusted for vertical or horizontal polarization.

All high performance antennas have an integrated radome.

4.4.2 Installation

4.4.2.1 Integrated Installation

For a 1+0 configuration, the RAU is fitted directly to the rear of the antenna inintegrated installation. Single polarized antennas up to 1.8 m in diameter arenormally fitted integrated with the Radio Unit (RAU).

15 GH

z

15 G

Hz

RADIOCABLE


15 GH

z

15 G

Hz

RADIOCABLE


15 GH

z

15 G

Hz

RADIOCABLE


8459

Figure 64 0.2 m, 0.3 m and 0.6 m compact antennas integrated with RAU2

6716

RADIOALARM

POWER RADIO CABLE

AGC

RADIOALARM

POWER RADIO CABLE

AGC

Figure 65 0.3 m and 0.6 m compact antennas integrated with RAU1

76 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

For a 1+1 configuration the RAU2 can be fitted directly to an integrated powersplitter. A similar solution is available for RAU1, using a waveguide betweenthe power splitter and the antenna.

A symmetrical power splitter version, with equal attenuation in both channels, isused in the majority of the installations.

RADIO 2

8500RAU1 RAU2

15 GH

z

15 G

Hz

ALARMPOWER

ALIGNMENT

RADIOCABLE

Figure 66 RAUs fitted to integrated power splitters

4.4.2.2 Separate Installation

All antennas with IEC 154 Type B waveguide interface can be installedseparately, by using a flexible waveguide to connect to the RAU. The dualpolarized antennas and the 2.4–3.7 m antennas are always installed separately.

8454

Figure 67 Separate installation in a 1+0 configuration

774/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.4.3 Mounting Kits

This section describes the mounting kits used for the 0.2 m, 0.3 m and 0.6 mantennas. A mounting kit consists of two rigid, extruded aluminum bracketsconnected with two stainless steel screws along the azimuth axis. The bracketsare anodized and have threaded and unthreaded holes to provide adjustmentof the antenna in azimuth and elevation.

The support can be clamped to poles with a diameter of 50–120 mm oron L-profiles 40x40x5–80x80x8 mm with two anodized aluminum clamps.All screws and nuts for connection and adjustment are in stainless steel.NORD-LOCK washers are used to secure the screws.

6717

Figure 68 Mounting kit for the 0.2 m compact antenna

The 0.2 m compact antenna mounting kit can be adjusted by ±13° in elevationand by ±90° in azimuth.

6718

Figure 69 Mounting kit for the 0.3 m and 0.6 m compact antennas

The mounting kit for 0.3 m and 0.6 m compact antenna can be adjusted by±15° in elevation and ±40° in azimuth. Both elevation and azimuth have amechanism for fine adjustment.

78 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.5 PMP Functionality

With Point-to-Multipoint (PMP) Functionality the number of antennas canbe limited at the hub site. The MINI-LINK TN, PMP Functionality is servedby a sector antenna which covers 45° or 90°. Within a sector up to fourfrequencies are allocated. Each terminal radio at the hub acts as a PTP linkto a dedicated terminal radio in the sector. Each of these links has its owndedicated sub-channel.

9427

Pow

er Splitter

Pow

er Splitter

Sectorantenna

Pow

er Splitter

Figure 70 Overview of MINI-LINK TN, PMP Functionality

The system is scalable and offers configurations with two, three or fourterminals per sector. Two types of mounting kits are available, where thechoice of mounting kit depends on the amount of terminals to be installed. Onekit supports configuration of up to four terminals connected to three integratedpower splitters. The other kit supports configuration of two terminals connectedto one integrated power splitter.

794/1555-CSH 109 32/1-V1 Uen B 2007-09-14


15 GH

z

15 G

Hz

15 GH

z

15 G

Hz

ALARMPOWER

ALIGNMENT

RADIOCABLE

RADIOCABLE


RADIOCABLE


9426

Figure 71 Mounting kits for installation of two (left) up to four (right) radio terminals

80 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

4.6 1+1 Protection

4.6.1 Overview

A Radio Terminal can be configured for 1+1 protection. This configurationprovides propagation protection and equipment protection on the MMU, RAUand antenna. Propagation protection may be used on radio links where fadingdue to meteorological and/or ground conditions make it difficult to meet therequired transmission quality.

Configurations for 1+1 protection can be in hot standby or working standby. Inhot standby mode, one transmitter is working while the other one, tuned to thesame frequency, is in standby. It is not transmitting but ready to transmit ifthe active transmitter malfunctions. Both RAUs receive signals. When usingtwo antennas, they can be placed for space diversity with a mutual distancewhere the impact of fading is reduced.

In working standby mode, both radio paths are active in parallel using differentfrequencies, realizing frequency diversity. Using two different frequenciesimproves availability, because the radio signals fade with little correlation toeach other. Space diversity can be implemented as for hot standby systems.

6654

f2

f1

Working Standby

f1

f1

Hot Standby

Figure 72 Radio link protection modes

For information specific for XPIC, Section 4.6.3 on page 86.

4.6.2 Functional Description

The following different protection cases can be identified:

814/1555-CSH 109 32/1-V1 Uen B 2007-09-14


• Tx Equipment Protection Working Standby

• Tx Equipment Protection Hot Standby

• Radio Segment Protection

• Rx Equipment Protection

4.6.2.1 Tx Equipment Protection Working Standby

This protection case involves two types of switch, TDM Tx switch and TrafficAlignment (TA) switch.

The TDM Tx switch is a logical switch used to switch over the traffic to theredundant MMU, in case of a failure in the TDM Multiplexer part of the activeMMU. This is accomplished by the NPU configuring the MMUs to listen to acertain TDM bus slot.

The TA switch is used to feed the multiplexed traffic signals to the Radio FrameMultiplexer block in both MMUs, which is a condition for being able to performhitless switching in the receiving end.

Alarms generated in the RAU and MMU are monitored by the NPU, which basedon the alarm severity commands the TDM and TA switches as appropriate.

The switching principles are illustrated in Figure 73 on page 83.

82 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

Radio Frame Multiplexer Modulator

Cable Interface

TDMMultiplexer/

DemultiplexerTDMPCI

RCC

RAU A

Node Processor

TA Switch

TA Switch

MMU A

NPU

Tx On/Off (Hot Standby)

Tx On/Off (Hot Standby)


Cable Interface


TDMMultiplexer/

DemultiplexerRCC

RAU B

MMU B

TDM

Tx

Sw

itch

BPI

6666


Figure 73 Tx Equipment Protection, Working and Hot Standby

4.6.2.2 Tx Equipment Protection Hot Standby

This protection case also involves the TDM Tx switch and the TA switch.The difference from Tx Equipment Working Standby is that only one RAU isactive. Hence, Tx must be switched off in the malfunctioning Radio Terminaland switched on in the standby. This is controlled by the DP in the Control andSupervision block of the MMU and communicated in the RCC.

Alarms generated in the RAU and MMU are monitored by the NPU, which basedon the alarm severity commands the TDM and TA switches as appropriate.


4.6.2.3 Radio Segment Protection

This protection case involves a Diversity switch in each MMU, providing hitlessand error free traffic switching in case of radio channel degradation. It is alsoused as equipment protection in case of a signal failure in the RAU Rx parts.

834/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The Diversity switches will work autonomous and are controlled by the switchlogic in the active MMU Rx. The switch logic is implemented as software in theDP in the Control and Supervision block.

The Diversity switch will react on the Early Warning (EW) signals, Input Powerthreshold alarm and FEC error alarm. The switch logic in one MMU needsinformation from the other MMU, which is sent over the BPI bus.

Note that this switching is done under no fault conditions.



ModulatorCable Interface

TDMMultiplexer/

Demultiplexer

TDM PCI

RAU A

Node Processor

MMU A

NPU

RAU B

TDM

Rx

Sw

itch

BPI

BPI

6667

Switch Logic

Diversity Switch


ModulatorCable Interface

TDMMultiplexer/

Demultiplexer

MMU B

Diversity Switch

Switch Logic



Figure 74 Radio Segment Protection and Rx Equipment Protection

4.6.2.4 Rx Equipment Protection

This protection case involves two types of switch, TDM Rx switch and Diversityswitch.

The TDM Rx switch is a logical switch used to switch over the traffic to theredundant MMU, in case of a failure in the TDM Demultiplexer part of the active

84 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

MMU. This is accomplished by the NPU configuring the MMUs to listen to acertain TDM bus slot.

The Diversity switches will work autonomous and is controlled by the switchlogic in the active MMU Rx. This is in accordance with the Radio SegmentProtection case, with the difference that signal failure alarms have a higherpriority level than the EW signals.

Alarms generated in the RAU and MMU are monitored by the NPU, whichbased on the alarm severity commands the TDM switch as appropriate.


854/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.6.3 1+1 Protection with XPIC (MMU2 F)

4.6.3.1 AMM Configurations

The protected 1+1 XPIC radio terminal configuration consists of four modemsMMU2 F 155 with XPIC capability, four RAUs, and two integrated dual-polarizedantennas or four separate antennas. See Figure 75 on page 86.

ML TN

MMU 2 F 155

MMU 2 F 155

MMU 2 F 155

MMU 2 F 155

ML TN

MMU 2 F 155

MMU 2 F 155

MMU 2 F 155

MMU 2 F 155

9966

Figure 75 1+1 XPIC configuration

The four modems MMU2 F 155 are housed in the AMM 6p or the AMM 20p, infour adjacent slots that share the same BPI-4 bus. See Figure 76 on page 87.

86 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

9967

MM

U2

F 15

5

AP

U1+1 XPICP

FU1

0/1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

AMM 20p

PFU

2

FAU

2

NPU 7

6

5

4

3

2

MMU2 F 155

APU

AMM 6p

1+1XPIC

0 1

MMU2 F 155

MMU2 F 155

MMU2 F 155

1+1 XPIC 1+1 XPIC 1+1 XPIC

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

MM

U2

F 15

5

PFU

1

NP

U

NP

U

AP

U

Figure 76 AMM 6p and AMM 20p in 1+1 XPIC configuration

Each pair of modems placed in adjacent BPI-2 sharing slots (for AMM 20p,2&3 and 4&5, 6&7 and 8&9, etc.) is related to the same polarization of thetransmitted signal over the same wireless channel. Therefore, the front panelXPIC cross-cable shall connect modems in alternate slots (2&4 and 3&5, etc.).See Figure 77 on page 87.

9968

PFU

2

FAU

2

NPU 7

6

5

4

3

2

MMU2 F 155

APU

AMM 6p

1+1XPIC

0 1

MMU2 F 155

MMU2 F 155

MMU2 F 155

Figure 77 XPIC cross-cable connections (AMM 6p)

4.6.3.2 Functional Description

The 1+1 XPIC configuration provides propagation protection and equipmentprotection on the MMU, RAU and antenna when using both polarizations inco-channel dual polarized (CCDP) mode of operation with XPIC.

874/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Configurations for 1+1 XPIC protection can be in either hot standby (see Figure78 on page 88) or working standby (see Figure 79 on page 89).

9969

f1, VA

Near end Node Far end Node

MMU2 F 155

Active Active

Active

f1, VB

f1, HAActive

f1, HB

XPIC cross-cables

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

Figure 78 1+1 XPIC in Hot Standby

88 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

9970

f1, VA

Near end Node Far end Node

MMU2 F 155

Active Active

Active

f2, VB

f1, HAActive

f2, HB

XPIC cross-cables

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

MMU2 F 155

Figure 79 1+1 XPIC in Working Standby

In both schemes the V (H) polarized branch labeled B protects the V (H)polarized branch labeled A, and vice versa if revertive mode is disabled andafter repairing the fault.

In 1+1 XPIC configuration the switching criteria are exactly the same criteriaused in 1+1 protected configuration with single polarization mode and the twoswitching processes for H and V branches are independent.

When a fault occurs on one polarization, e.g. V, and the switching criteriaare satisfied, the switching to the protection link is initiated, from VA to VB. Ifthe fault does not cause a high degradation of the cancelling signal on theorthogonal polarization (switching criteria for H polarization are not satisfied),the switching to the protection link, from HA to HB, is not initiated.

If the depolarization is such that the H-polarization canceller is not able tocancel the cross-polar interference from H (switching criteria for H-polarizationare satisfied), the switching to the protection link, from HA to HB, is initiated.

A HW fault, for example on the V link, might cause a simultaneous degradationof the two polarizations, triggering a switch on both V and H link. Table 1 onpage 90 summarizes the consequent actions to a fault on V-polarization link.

894/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Table 1 Fault handling on a V-polarization link

Working Standby Hot Standby

Vertical Polarization HorizontalPolarization

Vertical Polarization HorizontalPolarization

Txside

Rx side Txside

Rx side Txside

Rx side Txside

Rx side

Startingcondition

f1-VAandf2-VB

f1-VA f1-HAandf2-HB

f1-HA VA VA HA HA

VA Txfaulthandling

N.A. f2-VB,disruptionaccepted

N.A. f1-HA orf2-HB,disruptionaccepted

VB VA or VB(quickestlocked-in),disruptionaccepted

Noaction

HA or HB(quickestlocked-in),disruptionaccepted

VA Txfaulthandling

N.A. f2-VB,disruptionaccepted

N.A. f1-HA orf2-HB,disruptionaccepted

N.A. VB,disruptionaccepted

N.A. HA or HB,disruptionaccepted

VApropaga-tion faulthandling

N.A. f2-VB,hitless

N.A. f1-HA orf2-HB,hitless

N.A. VB, hitless N.A. HA or HB,hitless

In case of not-hitless switching traffic disruption of a comparable entity on bothpolarizations may happen.

In hot-standby mode when the switching process is initiated the receivers willlock to the new active TX and the XPIC units will re-converge. The new activereceiver both for H link and V link will be the quicker receiver to lock.

4.7 Transmit Power Control

The radio transmit power can be controlled in Remote Transmit Power Control(RTPC) or Automatic Transmit Power Control (ATPC) mode, selectable fromthe management system including setting of associated parameters. In ATPCmode the transmit power can be increased rapidly during fading conditions andallows the transmitter to operate at less than the maximum power during normalpath conditions. The normally low transmit power allows more efficient use ofthe available spectrum while the high transmit power can be used as input topath reliability calculations, such as fading margin and carrier-to-interferenceratio.

The transmitter can be turned on or off from the management system.

90 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Radio Terminals

P

P

P

setP

outP

outP

Transmit power

PATPC max

ATPC min

fix min

max

5647

RTPC mode ATPC mode

Figure 80 Transmit power control

4.7.1 RTPC Mode

In RTPC mode the transmit power (Pout) ranges from a minimum level (Pfix min) toa maximum level (Pmax). The desired value (Pset) can be set in 1 dB increments.

4.7.2 ATPC Mode

ATPC is used to automatically adjust the transmit power (Pout) in order tomaintain the received input level at the far-end terminal at a target value. Thereceived input level is compared with the target value, a deviation is calculatedand sent to the near-end terminal to be used as input for possible adjustmentof the transmit power. ATPC varies the transmit power, between a selectedmaximum level (PATPC max) and a hardware specific minimum level (PATPC min).

914/1555-CSH 109 32/1-V1 Uen B 2007-09-14


4.8 Performance Management

The purpose of Performance Management for the Radio Terminal is to monitorthe performance of the RF Interface according to G.826.

The following parameters are used:

• RF output power from the transmitter and related alarm generation.

• RF input power into the receiver and related alarm generation with settablethresholds.

• BER of the composite signal and alarm generation with a configurablethreshold.

• Block based performance data on the received composite signal. This datais presented as Errored Seconds (ES), Severly Errored Seconds (SES),Background Block Error (BBE), Unavailable Seconds (UAS) and ElapsedTime.

In case of a protected system the block based performance data is evaluated atthe protected interface.

The BER and block based performance data are evaluated in-service by useof an error detection code in the composite signal.

92 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Access Termination Unit (ATU)

5 Access Termination Unit (ATU)

5.1 Overview

This section describes the ATU, which implements the indoor part of aMINI-LINK TN R3 Edge Node. It can be used for transmission of PDH andEthernet traffic. For more information on Ethernet traffic, see Section 3.6 onpage 31.

The ATU is a self-contained unit, with a height of 1U, for installation in astandard 19" or metric rack. It can also be mounted on a wall or put on a desk.

The ATU provides unprotected (1+0) microwave transmission, within the 6–38GHz frequency bands using C-QPSK modulation, when connected to an RAUwith antenna.

An NE with ATU utilizes the same outdoor part as an NE with AMM. In additionto this section, the following sections provide important information:

• Radio Unit (RAU), see Section 4.3 on page 69.

• Antennas (1+0 configuration), see Section 4.4 on page 76.

• Transmit Power Control, see Section 4.7 on page 90.

• Performance Management, see Section 4.8 on page 92.

From a technical point of view, two categories of ATU can be identified:

ATU Provides traffic capacity from 2x2 to 17x2 Mbit/s that can beshared between PDH and Ethernet traffic. Each ATU variant hasa specific default functionality which can be extended with anoptional feature, for example if both traffic types should be used.For more information on ATU variants and optional features, seethe Product Catalog.For more information on ATU, see Section 5.2 on page 94.

ATU C Provides traffic capacity from 2x2 to 4x2 for transmission of PDHtraffic. For more information on ATU C, see Section 5.3 on page100.

934/1555-CSH 109 32/1-V1 Uen B 2007-09-14


5.2 ATU

This section describes the functions of ATU.

The available traffic capacity, 2x2, 4x2, 8x2 and 17x2 Mbit/s, can be sharedbetween:

• PDH traffic with a maximum of 8xE1.

• Ethernet traffic over a maximum of 16xE1.

60V RAU

0V DC -48V

10BASE-T O&M BR

LAN

Brid

ge

E1:11

E1:10

E1:9

E1:8

E1:7

E1:6

E1:5

E1:4

10/100BASE-T

996410/100BASE-T RAU-48 V DC E1

10BASE-T USB

Figure 81 ATU

The following summarizes the ATU functions:

• Eight E1 interfaces

• One 10BASE-T Ethernet interface for connection to a site LAN

• One 10/100BASE-T Ethernet interface for Ethernet traffic

• System control and supervision

• IP router for DCN handling

• SNMP Master Agent

• USB interface for LCT connection

• Filtering of the external power, providing secondary voltages and powersupply to the RAU

• Storage and administration of inventory and configuration data

• Multiplexing and modulation of traffic signals in the transmitting direction

• Demodulation and demultiplexing of traffic signals in the receiving direction

94 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14



This section describes the functions of ATU based on the block diagram inFigure 82 on page 95.

8468

Power

USB

External PowerSupply -48 V DC

O&M

Ethernet

Modulator

Demodulator

DCC

DCCRCC

RAU

Traffic

Traffic

E1E1E1E1E1E1E1E1

10/100BASE-TTraffic

10BASE-TSite LAN

nxE1

nxE1HCC

HCC

LineInterface

Multiplexer/Demultiplexer

Radio FrameMultiplexer

Radio FrameDemultiplexer

CableInterface

Secondaryvoltages


Figure 82 Block diagram for ATU


This block provides the eight E1 line interfaces for connection of PDH traffic.It interfaces the Multiplexer/Demultiplexer block by transmitting and receivingthe traffic (nxE1).

5.2.1.2 Ethernet

This block provides the 10BASE-T interface for connection to a site LAN andthe 10/100BASE-T interface for Ethernet traffic in Ethernet bridge applications.

The Ethernet traffic is mapped on nxE1, where n≤16, using oneinverse multiplexer. The E1s are transmitted to and received from theMultiplexer/Demultiplexer block.

5.2.1.3 O&M

This block provides the LCT connection. The equipment is accessed using alocal IP address.

954/1555-CSH 109 32/1-V1 Uen B 2007-09-14


5.2.1.4 Power

The external power supply, –48 V DC, is connected to the unit.

This block provides secondary voltages for the unit and a stable voltage for theRAU, distributed in the radio cable. It also provides input low voltage protection,transient protection, soft start and electronic fuse to limit surge currents atstart-up, or overload currents during short circuit.

5.2.1.5 Multiplexer/Demultiplexer

This block interfaces the Line Interface and the Ethernet blocks by receivingand transmitting the traffic.

It performs 2/8 and 8/34 multiplexing, depending on the traffic capacity, forfurther transmission to the Radio Frame Multiplexer.

In the receiving direction, it performs 34/8 and 8/2 demultiplexing, dependingon the traffic capacity. The demultiplexed traffic is transmitted to the LineInterface and the Ethernet blocks.


This block handles system control and supervision. Its main functions are tocollect alarms, control settings and tests. It also holds an IP router for DCNhandling.

For the traffic over the hop it handles BER collection and communicates withprocessor in the RAU through the RCC.





• Traffic



Traffic

The transmit traffic data is first sent to the multiplexer to assure data rateadaptation (stuffing). If no valid data is present at the input, an AIS signal is

96 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14


inserted at nominal data rate. This means that the data traffic across the hop isreplaced with ones (1).

DCC

DCC comprises 2x64 kbit/s channels used for DCN communication over thehop.

HCC

The Hop Communication Channel (HCC) is used for exchange of control andsupervision information between the near-end and far-end.

Multiplexing



The synchronous scrambler has a length of 217–1 and is synchronized eacheighth frame (super frame). The FEC bits are inserted according to the frameformat and calculated using an interleaving scheme.

5.2.1.8 Modulator


C-QPSK (Constant envelope offset Qaudrature Phase Shift Keying), anoffset QPSK modulating technique, is used. It has a high spectrum efficiencycompared to other constant envelope schemes.



The following signals are frequency multiplexed in the Cable Interface forfurther distribution through a coaxial cable to the outdoor RAU:



• DC power supply

974/1555-CSH 109 32/1-V1 Uen B 2007-09-14


• Radio Communication Channel (RCC) signal as an Amplitude Shift Keying(ASK) signal.


5.2.1.10 Demodulator





Error correction is accomplished using FEC parity bits in combination with adata quality measurement from the Demodulator. The descrambler transformsthe signal to its original state enabling the Demultiplexer to properly distributethe received information to its destinations.

Demultiplexing

Demultiplexing is performed according to the used frame format. TheDemultiplexer generates a frame fault alarm if frame synchronization is lost.The number of errored bits in the traffic data stream is measured using paritybits. These are used for BER detection and performance monitoring. Stuffingcontrol bits are processed for the traffic and service channels.

Traffic



• AIS detection


DCC


98 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14


HCC

The Hop Communication Channel (HCC) is used for exchange of control andsupervision information between near-end and far-end.

994/1555-CSH 109 32/1-V1 Uen B 2007-09-14


5.3 ATU C

ATU C offers 2x2 or 4x2 traffic capacity for transmission of PDH traffic.

O&M RL

60V RAU

+ DC -

24-60VE1:4 E1:3 E1:2 E1:1

Power

8275

RAU24 - 60 V DCE1 O&M RL

Figure 83 ATU C


This section describes the functions of ATU C based on the block diagram inFigure 84 on page 100.

8276

Power

Secondary voltages

Line Interface

O&M RL

External Power Supply 24 – 60 V DC


Cable Interface

DemodulatorRadio Frame Demultiplexer

DCC

DCCRCC

RAU

Traffic

Traffic


E1E1

HCC

HCC

E1E1

Figure 84 Block diagram for ATU C


This block provides the 4 E1 line interfaces for connection of PDH traffic. Itinterfaces Radio Frame Multiplexer block by transmitting and receiving thetraffic (nxE1).

100 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14



This block handles system control and supervision. Its main functions are tocollect alarms, control settings and tests.

For the traffic over the hop it handles BER collection and communicates withprocessor in the RAU through the RCC.


Local management of ATU C is done with MSM software.

5.3.1.3 Power

The external power supply, 24–60 V DC, is connected to the unit.

This block provides secondary voltages for the unit and a stable voltage for theRAU, distributed in the radio cable.




• Traffic



Traffic

The transmit traffic data is first sent to the multiplexer to assure data rateadaptation (stuffing). If no valid data is present at the input, an AIS signal isinserted at nominal data rate. This means that the data traffic across the hop isreplaced with ones (1).

DCC

DCC comprises 2x64 kbit/s channels used for DCN communication over thehop.

HCC

The Hop Communication Channel (HCC) is used for exchange of control andsupervision information between the near-end and far-end.

1014/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Multiplexing



The synchronous scrambler has a length of 217–1 and is synchronized eacheighth frame (super frame). The FEC bits are inserted according to the frameformat and calculated using an interleaving scheme.

5.3.1.5 Modulator


C-QPSK (Constant envelope offset Qaudrature Phase Shift Keying), anoffset QPSK modulating technique, is used. It has a high spectrum efficiencycompared to other constant envelope schemes.



The following signals are frequency multiplexed in the Cable Interface forfurther distribution through a coaxial cable to the outdoor RAU:



• DC power supply

• Radio Communication Channel (RCC) signal as an Amplitude Shift Keying(ASK) signal


5.3.1.7 Demodulator


102 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14





Error correction is accomplished using FEC parity bits in combination with adata quality measurement from the Demodulator. The descrambler transformsthe signal to its original state enabling the Demultiplexer to properly distributethe received information to its destinations.

Demultiplexing

Demultiplexing is performed according to the used frame format. TheDemultiplexer generates a frame fault alarm if frame synchronization is lost.The number of bits with errors in the traffic data stream is measured usingparity bits. These are used for BER detection and performance monitoring.Stuffing control bits are processed for the traffic and service channels.

Traffic



• AIS detection


DCC


HCC

The Hop Communication Channel (HCC) is used for exchange of control andsupervision information between near-end and far-end.

1034/1555-CSH 109 32/1-V1 Uen B 2007-09-14


104 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6 Management

The management functionality described in this section can be accessed fromthe management tools and interfaces as described in Section 6.8 on page119. Shortly these are:

• Embedded Element Manager (EEM) accessed using a Web browser

• ServiceOn Microwave for remote O&M

• Simple Network Management Interface (SNMP)

6.1 Fault Management

All software and hardware in operation is monitored by the control system.The control system locates and maps faults down to the correct replaceablehardware unit. Faults that cannot be mapped to one replaceable unit result in afault indication of all suspect units (this may be the whole NE).

Hardware errors are indicated with a red LED found on each plug-in unit andRAU.

The control system will generally try to repair software faults by performingwarm restarts on a given plug-in unit or on the whole NE.

6.1.1 Alarm Handling

MINI-LINK TN R3 uses SNMP traps to report alarms to MINI-LINK Manageror any other SNMP based management system. To enable a managementsystem to synchronize alarm status, there is a notification log (alarm history log)where all traps are recorded. There is also a list of current active alarms. Boththese can be accessed by the management system using SNMP or from theEEM. The alarm status of specific managed objects can also be read.

In general, alarms are correlated to prevent alarm flooding. This is especiallyimportant for high capacity links like STM-1 where a defect on the physicallayer can result in many alarms at higher layer interfaces like VC-12 and E1.Correlation will cause physical defects to suppress alarms, like AIS, at thesehigher layers.

Alarm notifications can be enabled/disabled for an entire NE, for an individualplug-in unit and for individual interfaces. Disabling alarm notification means thatno new alarms or event notifications are sent to the management system.

Alarm and event notifications are sent as SNMP v2c/v3 traps with a formataccording to Ericsson’s Alarm IRP SNMP solution set version 1.2. The followingfields are included in such a notification:

1054/1555-CSH 109 32/1-V1 Uen B 2007-09-14


• Notification identifier: uniquely identifies each notification.

• Alarm identifier: only applicable for alarms, identifies all alarm notificationsthat relate to the same alarm.

• Managed object class: identifies the type of the source (E1, VC-4 etc).

• Managed object instance: identifies the instance of the source like 1/11/1Afor an E1 on the NPU.

• Event time: time when alarm/event was generated.

• Event type: X.73x compliant alarm/event type like communications alarmand equipment alarm.

• Probable cause: M.3100 and X.733 compliant probable cause, for exampleLoss Of Signal (LOS).

• Perceived severity: X.733 compliant severity, for example critical orwarning.

• Specific problem: free text string detailing the probable cause.

The system can also be configured to send SNMP v1 traps. These traps aretranslated from the IRP format using co-existence rules for v1 and v2/v3 traps(RFC 2576).

For a full description of alarms see user documentation.

6.1.2 Loops

Loops can be used to verify that the transmission system is working properly orthey can be used to locate a faulty unit or interface. The following loops areavailable on all units that carry traffic.

Connection Loop This loop can be initiated for an E1. The traffic connection islooped in the TDM bus back to its origin, see Figure 85 onpage 107. If an E1 interface is traffic routed an AIS is sent tothe other interface in the traffic routing.A Connection Loop can be used in combination with a BERTin another NE to test a network connection including thetermination plug-in unit, in case a Local Loop cannot be useddue to the lack of a traffic routing.

The following loops are available on units with a line interface (MS/RS, E3,E2 and E1).

106 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

Line Loop Loops an incoming line signal back to its origin. The loop isdone in the plug-in unit, close to the line interface, see Figure85 on page 107. An AIS is sent to the TDM bus.A Line Loop in combination with a BERT in an adjacent NE isused to test the transmission link between the two NEs.In the MMU2 E/F STM-1 the traffic signal that shall betransmitted is looped back just after base-band interface.

Local Loop Loops a line signal received from the TDM bus back to itsorigin, see Figure 85 on page 107. An AIS is sent to the lineinterface.A Local Loop in combination with a BERT in another NE canbe used to test a connection as far as possible in the loopedNE.In the MMU2 E/F a Local Loop at the far end loops back theSTM-1 traffic at base-band level.

The following loop is only supported on the MMU.

Rx Loop This loop is similar to the Connection Loop but the loop isdone in the plug-in unit close to the TDM bus, where a groupof E1s in the traffic connection is looped back to its origin,Figure 85 on page 107.An Rx Loop can be used on the far-end MMU to verify thecommunication over the radio path, see Figure 86 on page108.In the MMU2 E/F the RX Loop applies to the wayside E1 traffic.

nxE1

Plug-in Unit*

Plug-in Unit

nxE1

7470

nxE1

Plug-in Unit

Rx Loop

Connection Loop

AIS

AIS

AIS

Line LoopLocal Loop

TDM Bus

* Only MMU

Figure 85 Loops

1074/1555-CSH 109 32/1-V1 Uen B 2007-09-14


The following loops on the near-end Radio Terminal are supported in order tofind out if the MMU or RAU is faulty.

IF Loop In the MMU the traffic signal to be transmitted is, after beingmodulated, mixed with the frequency of a local oscillator andlooped back for demodulation (on the receiving side).

RF Loop In the RAU a fraction of the RF signal transmitted is shifted infrequency and looped back to the receiving side.

9971

MMU MMURAURAU

Rx LoopIF Loop RF Loop

Near-end Far-end

Note: For MMU2 E/F, also a Local Loopis available at the Far-end MMU.

Figure 86 Radio Terminal loops

The AAU supports a Loop Back function described in Section 3.7.2.2 on page41.

6.1.3 User Input/Output

The NPU1 B provides three User Input and three User Output ports. The NPU3provides two User Output ports.

The User Input ports can be used to connect user alarms to the MINI-LINKmanagement system. Applications like fire alarms, burglar alarms and lowpower indicator are easily implemented using these input ports. The User Inputports can be configured to be normally open or normally closed.

User Output ports can be used to export summary alarms of the accumulatedseverity in the NE to other equipment’s supervision system. The User Outputports can be controlled by the operator or triggered by one or several alarmseverities.

The setup of the User Input/Output is done in the EEM.

108 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6.2 Configuration Management

The configuration can be managed locally and from the O&M center providedthat the DCN is set up. The following list gives examples of configuration areas:

• Transmission interface parameters

• Traffic routing

• Traffic protection, such as 1+1 E1 SNCP, MSP 1+1

• DCN parameters, such as host name, IP address

• Security parameters, such as enabling telnet, adding new SNMP users

• Radio Terminal parameters, such as frequency, output power, ATPC andprotection

6.3 Software Management

Software can be upgraded both locally and remotely. Software upgrade utilizesa local or remote FTP server to distribute the software to the NE. An FTPserver is provided on the MINI-LINK Service Software CD used when installingsoftware on site.

The MINI-LINK TN R3 system software consists of different software modulesfor different applications.

All traffic continues while the software is being loaded. During the execution ofthe software download a progress indication is provided in the user interface.

When the download is completed, the new software and the previous softwareversion are stored on the unit.

Performing a warm restart of the NE activates the new software version. Awarm restart only affects the control system. This restart can be performedimmediately or scheduled at a later time. The restart, depending on the newfunctionality, may influence the traffic. When the warm restart with the newsoftware is completed, the NE will wait for a “Commit” command from themanagement system. When “Commit” is received, the software upgradeprocess is completed.

The previous software revision remains stored on the unit in case a rollback isrequired. This may be the case if something goes wrong during the softwareupgrade or if no “Commit” is received within 15 minutes after the restart.

If plug-in units with old software versions are inserted into the NE, they canbe automatically upgraded.

1094/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6.4 License Management

License Key Files (LKF) can be installed both locally and remotely. Licenseinstallation utilizes a local or remote FTP server to distribute the LKF to theNE. An FTP server is provided on the MINI-LINK Service Software CD usedwhen installing software on site.

The LKF is bound to a fingerprint which is a unique ID of a RMM, and will onlyfunction when installed on the correct RMM.

Once installed, the NE features that is comprised within that LKF is allowed tobe used. Multiple LKF can be used simultaneously on one NE, as long as theycome from separate license generators. (Multiple license generators are afuture system solution.)

The NE has a license inventory view.

An attempt to configure a function without a suitable LKF installed causesan error and the service will be unavailable until the file is installed. Theerror is sent as a standard event message to the management software. Formigration, the error is reduced to a warning when introducing licensing, and theconfiguration still allowed. New SW versions will introduce the locking.

Since the licenses are critical to secure the desired operation of the NE, a graceperiod (30 days) has been introduced in the unusual case of a RMM failure.The LKF will seem available during this grace period, and should give sufficienttime to do a RMM repair. The RMM failure is indicated as a HW alarm.

There is no technical solution introduced for moving of licenses from one RMMto another. Commercial solutions exists.

110 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6.5 Performance Management

6.5.1 General

MINI-LINK TN R3 supports performance management according to ITU-Trecommendation G.826.

The following performance counters are used for the E1 and STM-1 interfaces:

• Errored Seconds (ES)

• Severely Errored Seconds (SES)

• Background Block Error (BBE) (only structured interfaces)

• Unavailable Seconds (UAS)

• Elapsed Time

The performance counters above are available for both 15 minutes and 24hours intervals. The start time of a 24 hours interval is configurable.

The following counters are stored in the NE:

• Current 15 minutes and the previous 96x15 minutes

• Current 24 hours and the previous 24 hours

Specific information on performance management is also available as listedbelow:

• Performance counters for Ethernet traffic are described in Section 3.6.2on page 33.

• Performance data for the Radio Terminal is described in Section 4.8 onpage 92.

Performance data is stored in a volatile memory, so that a restart will loseall gathered data.

6.5.2 Bit Error Testing

Each NE has a built-in Bit Error Ratio Tester (BERT) in all plug-in unitscarrying traffic. The BERT is used for measuring performance on E1 interfacesaccording to ITU standard O.151. A Pseudo Random Bit Sequence (PRBS)with a test pattern 215–1 is sent through the selected interface.

As with loop tests, bit error testing may be used for system verification or forfault location.

1114/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Plug-in Unit

BERT

E1

6668

TDM Bus

NE orExternal equipment

Figure 87 BERT in combination with an external loop

The BERT is started and stopped by the operator and the bit error rate as afunction of the elapsed time is the test result. The test can be started andstopped locally or remotely using the management system.

Several BERTs can be executed concurrently with the following limitations:

• One BERT per plug-in unit

• One BERT on a protected 1+1 E1 SNCP interface per NE

Note: BERT is not valid for MMU2 F/C.

112 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6.6 Security Management

All management access to the MINI-LINK TN R3 system is protected by a username and a password. The following user types are defined:

• view_user with read only access

• control_user with read and write access

Both user types have an associated password. Passwords can only bechanged by the control_user using the EEM or the SNMP v3 interface.

The following security mechanisms are used on the various O&M interfaces:

• Local and remote EEM access requires a user name and password. Adefault password is used for the local USB connection.

• For SNMP v3 access the regular user name and password protectionis used. In addition to this the User-based Security Model (USM) andView-based Access Model (VACM) are supported. This means thatadditional users and passwords might be defined by external SNMP v3managers. The security level is authentication/no privacy where MD5 isused as hash algorithm for authentication.

• For SNMP v1/v2c access the regular user name and password protectiondoes not apply. Instead a community based access protection is used.As default, a public and a private community are configured. The publiccommunity enables default read-access and the private communityprovides read and write access to MIB-II system information. Theseprivileges can be extended through either the EEM or SNMP v3 interface.The SNMP v1/v2c interface may by disabled.

• Access to the telnet port using CLI commands is protected by the regularuser name and password protection. The telnet port can be disabled fromthe EEM.

1134/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6.7 Data Communication Network (DCN)

This section covers the DCN functions provided by MINI-LINK TN R3.The MINI-LINK DCN Guideline ETSI gives recommendations on DCNimplementation, covering the different MINI-LINK product families.

6.7.1 IP Services

The following standard external IP network services are supported:

• All clocks, used for example for time stamping alarms and events, can besynchronized with a Network Time Protocol (NTP) server.

• File Transfer Protocol (FTP) is used as a file transfer mechanism forsoftware upgrade, and for backup and restore of system configuration.

• Domain Name System (DNS) enables the use of host names.

• Dynamic Host Configuration Protocol (DHCP) is used to allocate IPaddresses in the DCN. The NE has a DHCP relay agent for serving otherequipment on the site LAN.

NTP

FTP

DCN

DNS

DHCP

MINI-LINK TN

LCT

Site LAN

7853

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

LTU 155e

MMU2 B 4-34

SMU2

LTU 155e/o

LTU 16x2

PFU3

PFU3FAU2

NPU1 B

Figure 88 IP services

6.7.2 DCN Interfaces

MINI-LINK TN R3 provides an IP based DCN for transport of its O&M data.Each NE has an IP router for handling of the DCN traffic. A number of differentalternatives to connect and transport DCN traffic are supported. This diversity ofDCN interfaces provides the operator with a variety of options when deployinga DCN. Figure 89 on page 115 illustrates the different options, including waysof connecting to the equipment for DCN configuration.

114 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

8360

Router10/100BASE-T

USBPPP

DCCR/DCCM

Structured/Unstructured E1nx64 kbit/s

2xE0DCC Radio Terminal

Figure 89 DCN interfaces

The internal IP traffic is transported on nx64 kbit/s channels on the TDM bus inthe backplane. The internal channels are automatically established at power up.

6.7.2.1 DCN in SDH

4665

4665

1-9 10-274

1-3

4

5-9

RSOH

AU Pointers

MSOH

Payload+

RFCOH

Figure 90 Frame

The following channels can be used for DCN transportation in SDH:

• 128 kbit/s default channel available on radio side only (2*64 kbit/s in theRFCOH).

• 192 kbit/s channel available on line side and radio side by using EOC orDDC bites of the Regenerator Section Overhead Frame (RSOH) of theSDH Frame.

1154/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6.7.2.2 DCCr/DCCm

The DCCr/DCCm overhead sections in the STM-1 frame can be used totransport DCN traffic. A PPP connection is established over the overheadsegments between two end points. The default bandwidth is automaticallyestablished to DCCr=192 kbit/s and DCCm=192 kbit/s. DCCm is configurableto 384 kbit/s and 576 kbit/s.

The PPP connection in the overhead segments is implemented as PPP over bitsynchronous HDLC. Any 3rd party equipment that complies with this and thechannel bandwidth segmentation can interoperate with MINI-LINK TN. Typicallythe DCCr is used to connect MINI-LINK TN R3 to MINI-LINK HC over an STM-1connection. DCCm can be used to connect MINI-LINK TN R3 to MINI-LINK TNR3 over an STM-1 connection. Please note that for this connection there canbe no multiplexer between the two MINI-LINK TN R3 NEs.

6.7.2.3 Structured/Unstructured E1

MINI-LINK TN R3 can use up to two of its connected E1s for transport of IPDCN. The following options are available:

• Dedicated E1 for DCN

A structured or unstructured E1 can be dedicated for DCN. For thestructured E1, nx64 kbit/s timeslots can be configured for DCN transport.The remaining timeslots are unused, that is cannot be used to transporttraffic. For the unstructured E1, the entire 2 Mbit/s is used for DCNtransport.

• E1 with traffic pass-through

In a structured E1 used for traffic, nx64 kbit/s timeslots can be used forDCN transport. The DCN is inserted into the nx64 kbit/s timeslots internallyin the NE. The timeslots used for traffic is cross-connected in normalmanner through the NE.

6.7.2.4 nx64 kbit/s

nx64 kbit/s timeslots can be used for IP DCN as described in Section 6.7.2.3on page 116.

6.7.2.5 2xE0

A PPP/E0 connection can be established to an external device from the SMU2.

6.7.2.6 DCC Radio Terminal

Each Radio Terminal provides a DCC of nx64 Kbits, where 2≤n≤9 dependingon traffic capacity and modulation, transported in the radio frame overhead.

116 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6.7.2.7 10/100BASE-T

Each NE has a 10/100BASE-T Ethernet interface for connection to a site LAN.This interface offers a high speed DCN connection.

The interface is also used at sites holding MINI-LINK HC and MINI-LINK Ewith SAU IP(EX).

6.7.2.8 USB

The USB interface is used for LCT connection using a local IP address.

6.7.3 IP Addressing

MINI-LINK TN R3 supports both numbered and unnumbered IP addresses.Numbered IP addresses are used for the Ethernet interface and IP interfacesconfigured as ABR. All other IP interfaces should be set up with unnumberedIP addresses.

The IP interfaces with unnumbered IP address inherit the characteristics ofthe Ethernet interface.

The use of unnumbered interfaces has several advantages:

• The use of IP addresses is limited. Using numbered interfaces for the PPPlinks would normally require using one IP subnet with two addresses foreach radio hop. For a large aggregation site, this would imply a lot ofaddresses.

• The planning of the IP addresses is simplified.

• The amount of configuration is reduced because only one IP address isconfigured upon installation.

• Improved performance and smaller routing tables since the unnumberedPPP connections are not distributed by OSPF.

6.7.4 IP Router

The IP router supports the following routing mechanisms:

• Open Short Path First (OSPF), which is normally used for routers withinthe MINI-LINK domain.

• Static routing

There are two different ways to configure the IP router. The idea is that themost common configurations are done using the EEM. When complex routerconfiguration and troubleshooting is required, a Command Line Interface (CLI)is used, see Section 6.8.4 on page 120.

1174/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6.7.4.1 Open Shortest Path First Features

The following summarizes the (Open Shortest Path First ) OSPF features:

• An NE can be a part of a non-stub area, stub area or totally stub area.

• An NE can act as an Internal Router (IR) or an Area Border Router (ABR).

• Virtual links are supported, which is useful when an area needs to be splitin two parts.

• Link summarization is supported, which is used in the ABR to minimize therouting information distributed to the backbone and/or other areas.

118 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

6.8 Management Tools and Interfaces

This section gives a brief overview of the management tools and interfacesused for MINI-LINK TN R3.

Mobile Network OSS/NMSServiceOn Microwave

SNMP

SNMPSNMP

MINI-LINK HCMINI-LINK E

MINI-LINK BASDCN

MINI-LINK TN

LCT

Site LAN

7854

07/N

PU

06

05

04

03

02

08/F

AU2

01/P

FU3

00/P

FU3

LTU 155e

MMU2 B 4-34

SMU2

LTU 155e/o

LTU 16x2

PFU3

PFU3FAU2

NPU1 B

Figure 91 Management tools and interfaces

6.8.1 Element Management

The element management function provides tools for on site installation,configuration management, fault management, performance managementand software upgrade. It is also used to configure the traffic routing function,protection and DCN.

For local management, a Local Craft Terminal (LCT) is used, that is the NE isaccessed locally by connecting a PC to the NPU or ATU, with a USB cable.

The NE can also be accessed over the site LAN or remotely over the DCN.

A thorough description of the element management functions is available asonline help and in the MINI-LINK TN Operation Manual.

1194/1555-CSH 109 32/1-V1 Uen B 2007-09-14


6.8.2 ServiceOn Microwave

MINI-LINK TN R3 is managed remotely using the ServiceOn Microwaveplatform. ServiceOn Microwave provides functions such as FM, CM, AM, PMand SM based on the recommendations from Open Systems Interconnect (OSI)model. The CM functionality is either embedded or provided using dedicatedLocal Managers and Element Managers. ServiceOn Microwave can also beused to mediate FM, PM and Inventory data to other management systems.

The system provides:

• Fault Management

• Configuration Management

• Performance Management

• Security Management

• Remote Software Upgrade

ServiceOn Microwave provides element management services across a wholenetwork. Network elements can be managed on an individual basis, providingthe operator with remote access to several network elements, one by one.

ServiceOn Microwave supports a real time window reporting alarms and eventsfrom the managed network elements. It is possible to filter alarms on the basisof assigned resources and alarm filtering criteria.

6.8.3 SNMP

Each NE provides an SNMP agent enabling easy integration with any SNMPbased management system. The SNMP agent can be configured to supportSNMP v1/v2c/v3 for get and set operations. SNMP v3 is default. The SNMPagent sends SNMP v1, SNMP v2c and SNMP v3 traps.

The system is built on standard MIBs as well as some private MIBs.

6.8.4 Command Line Interfaces

A CLI is provided for advanced IP router configuration and troubleshooting.This interface is similar to Cisco’s industry standard router configuration and isaccessed from a Command Prompt window using telnet.

The CLI functions are described in the online Help and the MINI-LINK TNOperation Manual.

120 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Management

Figure 92 CLI

1214/1555-CSH 109 32/1-V1 Uen B 2007-09-14


122 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Accessories

7 Accessories

The MINI-LINK TN R3 product program contains a comprehensive set ofaccessories for installation and operation. This section gives additionaltechnical information for some accessories.

7.1 Interface Connection Field (ICF)

MINI-LINK TN R3 uses Sofix connectors for 120 Ω E1 traffic connections on theplug-in units in the AMM. Sofix is a high-density connector holding four E1s perconnector. It is optimized to occupy minimal space on the plug-in unit fronts,which enables very compact site solutions. D-sub connectors are used forconnection of power supply and User I/O.

The ATU uses RJ-45 connectors for E1 traffic.

For further details on connectors, see MINI-LINK TN ETSI Product Specificationand MINI-LINK TN ETSI Indoor Installation Manual.

Instead of connecting directly to the front of the units in the AMM, an InterfaceConnection Field (ICF) can be used. It provides a panel with connectorsand pre-assembled cables to be connected to the units. The use of an ICFenables easy on-site installation and flexibility, with a minimum of impact whenre-configuring traffic cables.

The following types of ICF are available:

ICF1 The ICF1 is used for AMM 20p. It provides connectors for E1 traffic(D-sub 120 Ω or SMZ 75 Ω), redundant power supply of PFU1 andFAU1, User I/O, and fuses for FAU1, see Figure 93 on page 124.

ICF2 The ICF2 is used for AMM 6p B. It provides connectors for E1 traffic(D-sub 120 Ω or SMZ 75 Ω) and User I/O, see Figure 94 on page 124.

ICF 16x2 The ICF 16x2 can be used for any AMM. It provides connectors for E1traffic (D-sub 120 Ω or SMZ 75 Ω), see Figure 95 on page 125.

ICF3 The ICF3 can be used for any AMM or ATU. It provides connectorsfor E1 traffic (BNC 75 Ω). ICF3 has a modular design with a framewith room for up to four connection boxes, each one with a specificcable connecting to the plug-in unit (Sofix) or ATU (RJ-45), see Figure96 on page 125.

The ICF fits in standard 19" or metric racks.

The following figures show examples of the different ICF types and the numberof connectors for each type.

1234/1555-CSH 109 32/1-V1 Uen B 2007-09-14


User I/O

4xE1

FAU1

8495

FAN

3A 3B 3C 3D

TRAFFIC E1

FUSE A FUSE B 2A 2B 2C 2D

USER I/O:1A-1F

01

-48V DC - + IN

00

-48V DC - + IN

E1 User I/O-48 V DC IN E1

PFU1

Figure 93 ICF1 120 Ω

3A 3B 3C 3D

TRAFFIC E1

2A 2B 2C 2D

USER I/O:1A-1F

User I/O

User I/O

4xE1

E1 E1

8496

Figure 94 ICF2 120 Ω

124 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Accessories

2A 2B 2C 2D 1A 1B 1C 1D

IN

4A 4B 4C 4D3A

TRAFFIC E1

3B 3C 3DOUT

E1 E1 E1 E1

8493

4xE1

Figure 95 ICF 16x2 75 Ω

8494

TRAFFIC E1IN

OUTA B C D

E1

4xE1

Figure 96 ICF3 with one connection box and connection cable (Sofix)

1254/1555-CSH 109 32/1-V1 Uen B 2007-09-14


7.2 PSU DC/DC Kit

The PSU DC/DC kit is used for AMM 6p B or AMM 20p, converting +24 V DC to–48 V DC with a maximum output power of 950 W. It consists of a sub-rack(3U high), one or two Power Supply Units (PSU) and an FAU3. Two PSUs areused for redundant power systems.

The +24 V DC external power supply is connected to the PSU front.

The sub-rack provides two –48 V DC connectors for PFU connection. Twofused –48 V DC connectors for FAU1 connection are also available.

The sub-rack can be mounted in a standard 19" or metric rack or on a wallusing a dedicated mounting set.

EARTHGROUNDING

FAU3

FaultPower

-48VDC Power

Alarm

-48VDC OUT

AB

0001

-48VDC 0V

-48VDC 0V3.15A250V

3.15A250V

-48VDC 0V

-48VDC 0V

+

+PS

U

Faul

tO

pera

tion

Info

rmat

ion

EC

Bus

DC

Out

DC

In

+

+PS

U

Faul

tO

pera

tion

Info

rmat

ion

EC

Bus

DC

Out

DC

In

FAU3

–48 V DC Out (FAU1)

–48 V DC Out (PFU1/PFU3)

–48 V DC Out (PFU1/PFU3)

+24 V DC InPSU

Fan alarm (NPU1 B)

8261

Figure 97 PSU DC/DC kit

7.2.1 Cooling

Forced air-cooling is always required and provided by FAU3, which holds twointernal fans. It is power supplied by an internal pre-assembled cable connectedto the front. A connector for alarm export to the NPU1 B is also available.

126 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Accessories

EARTHGROUNDING

FAU3

PSU +

+

PSU +

+

-48VDC OUT

AB

0001

Air in

Air in

Air outAir out

Air out

6724

Figure 98 Cooling airflow in the PSU DC/DC kit

The air enters at the front and gable on the right hand side of the sub-rack,flows past the plug-in units and exits at the rear, top and gable on the left handside of the sub-rack.

1274/1555-CSH 109 32/1-V1 Uen B 2007-09-14


7.3 Small Form Factor Pluggable

For MMU2 E/F 155 the Small Form Factor Pluggable (SFP) exists as electrical(SFPe) or optical (SFPo) transmitter/receiver.

SFP Optical (SFPo) 9694SFP Electrical (SFPe)

Figure 99 Electrical/optical SFP

7.4 Optical splitter/combiner

An optical splitter or combiner splits or combines the incoming/outgoing opticalsignal. It is used together with an optical SFP to form an EEP solution, seeSection 3.9.5 on page 51.

9358

Figure 100 Optical combiner/splitter

7.5 DCN LAN Switch

The DCN LAN Switch gives the possibility to connect up to 8 equipments toone DCN. The switch also provide IP-telephone connection through a Powerover Ethernet port. The port is powered via the battery back-up for the sitesupporting the use of the EoW telephone (IP-telephone) when the ordinary ACpower is down. The DCN LAN Switch runs on either +24 or -48 V DC.

Up to two DCN LAN Switches fits in a standard 19" or metric rack.

128 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Accessories

ERICSSONPoE

DLS

P1

PWR PoESELHOLD TO CONFIRM

P1 m

anu

al

P2-4

man

ual

P5-8

man

ual

100

Mb

ps

Full

du

ple

x

P1 p

rio

rity

P2 P3 P4 P5 P6 P7 P8

9467

Figure 101 DCN LAN Switch

ERICSSON

PoE

DLS

P1

PWRPoESEL

HOLD TO CONFIRM

P1 m

anu

al

P2-4

man

ual

P5-8

man

ual

100

Mb

ps

Full

du

ple

x

P1 p

rio

rity

P2 P3 P4 P5 P6 P7 P8

9466

Figure 102 DCN LAN Switch and 19” rack

1294/1555-CSH 109 32/1-V1 Uen B 2007-09-14


130 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Glossary

Glossary

AAUATM Aggregation Unit

ABRArea Border Router

ADMAdd Drop Multiplexer

AFCAutomatic Frequency Control

AGCAutomatic Gain Control

AISAlarm Indication Signal

AMMAccess Module Magazine

ASKAmplitude Shift Keying

ATMAsynchronous Transfer Mode

ATPCAutomatic Transmit Power Control

ATUAccess Termination Unit

BERBit Error Ratio

BIPBit Interleaved Parity

BPIBoard Pair Interconnect

BRBoard Removal

C-QPSKConstant envelope offset - Quadrature PhaseShift Keying

CBRConstant Bit Rate

CCContinuity Check

CLICommand Line Interface

CLPCell Loss Priority

CRCCyclic Redundancy Check

DCDirect Current

DCCData Communication Channel

DCCmDigital Communication Channel, MultiplexerSection

DCCrDigital Communication Channel, RegeneratorSection

DCNData Communication Network

DDFDigital Distribution Frame

DHCPDynamic Host Configuration Protocol

DNSDomain Name System

DPDevice Processor

1314/1555-CSH 109 32/1-V1 Uen B 2007-09-14


E0PDH traffic at 2x64 kbit/s

E1PDH traffic at 2 Mbit/s (2 048 kbit/s)



EEMEmbedded Element Manager

EEPEnhanced Equipment Protection

ELPEquipment and Line Protection

EOWEngineering Order Wire

EPDEarly Packet Discard

ETUEthernet Interface Unit

ESErrored Second

ETSIEuropean Telecommunications StandardsInstitute

EWEarly Warning

Far-endThe terminal with which the near-end terminalcommunicates

FAUFan Unit

FECForward Error Correction

FTPFile Transfer Protocol

GSMGlobal System for Mobile Communications

HCCHop Communication Channel

HDLCHigh-Level Data Link Control

HECHeader Error Correction

HopA radio link connection with a pair ofcommunicating terminals

HSDPAHigh Speed Data Packet Access

I/QInphase and Quadrature

ICSInternet Connection Sharing

ICFInterface Connection Field

IEEEInstitute of Electrical and ElectronicsEngineers

IFIntermediate Frequency

IMAInverse Multiplexing for ATM

IPInternet Protocol

IRInternal Router

IRPIntegrated Reference Point

ITUInternational Telecommunication Union

LANLocal Area Network

132 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Glossary

LBLoop Back

LCDLoss of Cell Delineation

LCTLocal Craft Terminal

LEDLight Emitting Diode

LKFLicense Key File

LOCLoss Of Continuity

LOFLoss Of Frame

LOSLoss Of Signal

LTULine Termination Unit

MACMedia Access Control

MDCRMinimum Desired Cell Rate

MIBManagement Information Base

MINI-LINK EProduct family for microwave transmission at2x2 to 17x2 Mbit/s

MINI-LINK HCProduct family for microwave transmission at155 Mbit/s

MINI-LINK TN R3Product family for microwave transmissionfeaturing comprehensive traffic handlingfunctions

MMUModem Unit

MSMultiplexer Section

MSMMINI-LINK Service Manager

MSPMultiplexer Section Protection

NENetwork Element

Near-endThe selected terminal

nrt-VBRnon-real time Variable Bit Rate

NPUNode Processor Unit

NTPNetwork Time Protocol

O&MOperation and Maintenance

OAMOperation, Administration, and Maintenance

OSPFOpen Shortest Path First

OSSOperations Support System

PCIPeripheral Component Interconnect

PDHPlesiochronous Digital Hierarchy

PFUPower Filter Unit

PLLPhase Locked Loop

PPDPartial Packet Discard

1334/1555-CSH 109 32/1-V1 Uen B 2007-09-14


PPPPoint-to-Point Protocol. Used for IP transportover serial links.

PSUPower Supply Unit

PTPPoint To Point

QAMQuadrature Amplitude Modulation

Radio linkTwo communicating Radio Terminals

Radio TerminalOne side of a radio link

RAURadio Unit

RCCRadio Communication Channel

RDIRemote Defect Indication

RMMRemovable Memory Module

RSRegenerator Section

RSSIReceived Signal Strength Indicator

rt-VBRreal time Variable Bit

RTPCRate Remote Transmit Power Control

SAUService Access Unit

SDSignal Degradation

SDHSynchronous Digital Hierarchy

SECBSeverely Errored Cell Blocks

SESSeverely Errored Second

SFSignal Failure

SFPSmall Form Factor Pluggable

SMUSwitch Multiplexer Unit

SNCPSubnetwork Connection Protection. 1+1E1 SNCP is used to create a protected E1interface from two unprotected E1 interfaces.

SNMPSimple Network Management Protocol

SONETSynchronous Optical Networking

SPISerial Peripheral Interface

STM-1Synchronous Transport Module 1(155 Mbit/s)

TCP/IPTransmission Control Protocol/InternetProtocol

TDMTime Division Multiplexing

TIMTrace Identifier Mismatch

TMTerminal Multiplexer

TUG3Tributary Unit Group

UBRUnspecified Bit Rate

134 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Glossary

URLUniform Resource Locator

USBUniversal Serial Bus

V.24Serial data interface

VBRVariable Bit Rate

VCVirtual Channel

VC-12Virtual Container 12 (2 Mbit/s)

VC-4Virtual Container 4 (155 Mbit/s)

VCCVirtual Channel Connection

VCIVirtual Channel Identifier

VLANVirtual Local Area Network

VPVirtual Path

VPCVirtual Path Connection

VPIVirtual Path Identifier

WCDMAWideband Code Division Multiple Access

XPICCross Polarization Interference Canceller

1354/1555-CSH 109 32/1-V1 Uen B 2007-09-14


136 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Index

Index

1+1 E1 SNCP..............................................................451+1 protection........................................................45, 81

XPIC.......................................................................8610/100/1000BASE-T..............................................31, 3310/100BASE-T.......................................................21, 332xE0

DCN ..................................................................... 116

A

AAU .............................................................................36block diagram.........................................................38overview.................................................................37

ABR ........................................................................... 118Access Module Magazine, See AMMAccess Termination Unit, See ATUAccessories ...............................................................123AIS...................................................................41, 67, 98Alarm handling...........................................................105Alarm Indication Signal, See AISAMM ........................................................................ 5, 11

cooling....................................................................13power supply ..........................................................12

AMM 20p .....................................................................16cooling....................................................................18power supply ..........................................................17

AMM 2p ....................................................................... 11cooling....................................................................13power supply ..........................................................12

AMM 2p B.................................................................... 11cooling....................................................................13power supply ..........................................................12

AMM 6pcooling....................................................................15power supply ..........................................................15

AMM 6p B/C/D.............................................................13power supply ..........................................................15

Amplitude Shift Keying, See ASKAntennas .....................................................................76

mounting kit............................................................78Area Border Router, See ABRASK .............................................................................72ATM...............................................................................5

interfaces................................................................38ATM Aggregation Unit, See AAU

ATM Cross-connect.....................................................39ATPC.....................................................................90–91ATU ...................................................................6, 93–94

block diagram.........................................................95ATU C........................................................................100

block diagram.......................................................100Automatic Transmit Power Control, See ATPC

B

Basic node.................................................................4, 9BERT......................................................................... 111Bit Error Ratio Tester, See BERTBlock diagram

AAU........................................................................38ATU........................................................................95ATU C ..................................................................100ETU2......................................................................34LTU 155 .................................................................30LTU 16/1 ................................................................26LTU3 12/1 ..............................................................26MMU2.....................................................................63MMU2 E/F 155.......................................................64NPU1 B ..................................................................22NPU2......................................................................22NPU3......................................................................23RAU........................................................................71

BPI bus........................................................................10BR button.....................................................................55Buffering ......................................................................40Buses.............................................................................9

C

C-QPSK.........................................................66, 97, 102MMU.......................................................................62

Cable interface ........................................66, 72, 97, 102CAC.............................................................................39CBR.............................................................................38CC ...............................................................................41CLI .............................................................................120CLP0+1 .......................................................................40CLP1............................................................................40

1374/1555-CSH 109 32/1-V1 Uen B 2007-09-14


Co-siting MINI-LINK E .................................................56Command Line Interfaces, See CLICompatibility, RAU ......................................................62Configuration management .......................................109Congestion thresholds.................................................40Connection loop.........................................................106Continuity Check, See CCCooling

AMM 20p................................................................18AMM 2p..................................................................13AMM 2p B ..............................................................13AMM 6p..................................................................15PSU DC/DC Kit ....................................................126

D

Data Communication Channel, See DCCData Communication Network, See DCNDCC................................................. 65, 96–97, 101, 116DCCm........................................................................ 116DCCr.......................................................................... 116DCN........................................................................... 114

2xE0..................................................................... 116E1......................................................................... 116interfaces.............................................................. 114nx64 kbit/s ............................................................ 116

DCN LAN Switch .......................................................128DHCP ........................................................................ 114DNS........................................................................... 114Domain Name System, See DNSDynamic Host Configuration Protocol, See DHCP

E

E1DCN ..................................................................... 116interface .................................................................25LTU ........................................................................25

E3 ................................................................................57Early Packet Discard, See EPDEEP .............................................................................51Electrical interface .......................................................28Element management ............................................... 119ELP..............................................................................50Engineering Order Wire

EOW.......................................................................24Enhanced Equipment Protection, See EEPEOW............................................................................24EPD .............................................................................40

Equipment and Line Protection, See ELPEquipment handling.....................................................55Equipment protection.......................................44, 83–84Ethernet

interface ............................................................... 117traffic ......................................................................31

Ethernet Interface Unit, See ETUETU .........................................................................5, 33ETU2

block diagram.........................................................34

F

F4/F5 ...........................................................................41Fan Unit, See FAUFAU ...............................................................................6FAU1 ...........................................................................19FAU2 ...........................................................................15FAU3 .........................................................................126FAU4 ..................................................................... 11, 13Fault management.....................................................105

AAU........................................................................38FEC ...........................................65, 67, 97–98, 102–103File Transfer Protocol, See FTPForward Error Correction, See FECFrequency diversity .....................................................81FTP............................................................................ 114

G

G.804 link ....................................................................39

H

HCC...............................................................65, 97, 101Hop Communication Channel, See HCCHot standby ...........................................................60, 81HSDPA ........................................................................36

I

ICF.............................................................................123ICF 16x2....................................................................125ICF1.....................................................................17, 124ICF2...........................................................................124

138 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Index

ICF3...........................................................................125IF loop........................................................................108IMA ..............................................................................39IMA group....................................................................39Indoor

part ...........................................................................5units..........................................................................5

Installationantennas ................................................................76integrated ...............................................................76separate .................................................................77

Integrated Installation ..................................................76Interface

DCN ..................................................................... 114E1...........................................................................25ethernet ................................................................ 117STM-1 ....................................................................27

Interface Connection Field, See ICFInternal Router, See IRInverse multiplexer ......................................................34Inverse Multiplexing for ATM.......................................39IP

addressing............................................................ 117router.................................................................... 117services................................................................ 114

IR............................................................................... 118IRP.............................................................................105

L

LCD .............................................................................41LCT............................................................................ 119License management ................................................ 110Licensing .......................................................................2Line loop....................................................................107Line Termination Unit, See LTULink summarization.................................................... 118LOC .............................................................................41Local Craft Terminal, See LCTLocal loop ..................................................................107Loops.........................................................................106Loss of Cell Delineation, See LCDLoss of Continuity, See LOCLTU................................................................................5

E1...........................................................................25STM-1 ....................................................................28

LTU 155block diagram.........................................................30

LTU 155e.....................................................................28LTU 155e/o..................................................................28

LTU 16/1......................................................................25block diagram.........................................................26

LTU B 155 ...................................................................28LTU3 12/1....................................................................25

block diagram.........................................................26

M

Management..............................................................105interfaces.............................................................. 119tools...................................................................... 119

MDCR..........................................................................38MINI-LINK Connexion..................................................43MINI-LINK E co-siting..................................................56MINI-LINK Manager...................................................120MMU........................................................................5, 61

C-QPSK .................................................................62QAM.......................................................................62

MMU2block diagram.........................................................63

MMU2 B.......................................................................61MMU2 C ......................................................................61MMU2 D ......................................................................61MMU2 E 155..........................................................61–62MMU2 E/F 155

block diagram.........................................................64MMU2 F 155..........................................................61–62Modem Unit, See MMUMounting Kit

antennas ................................................................78MSP 1+1......................................................................48Multiplexer Section Protection, See MSP 1+1

N

Network layer protection..............................................44Network Layer Protection ............................................45Network Time Protocol, See NTPNode Processor Unit, See NPUNon-revertive...............................................................45NPU.........................................................................5, 20NPU1 B..................................................................20–21

block diagram.........................................................22NPU2.....................................................................20–21

block diagram.........................................................22NPU3.....................................................................20–21

block diagram.........................................................23

1394/1555-CSH 109 32/1-V1 Uen B 2007-09-14


NTP ........................................................................... 114Numbered interfaces ................................................. 117nx64 kbit/s

DCN ..................................................................... 116

O

Open Short Path First, See OSPFOptical interface...........................................................28Optical splitter/combiner ............................................128OSPF......................................................................... 117Outdoor part ..................................................................7

P

Partial Packet Discard, See PPDPCI bus........................................................................10Performance management ........................................ 111

Ethernet..................................................................33Radio terminal ........................................................92

Peripheral Component Interconnect, See PCIPermanently bridged ...................................................45PFU ...............................................................................6PFU1 ...........................................................................17Physical link layer protection .......................................44PMP Functionality........................................................79Policing........................................................................39Power bus....................................................................10Power Filter Unit, See PFUPower Splitter ..............................................................77Power supply

AMM 20p................................................................17AMM 2p..................................................................12AMM 2p B ..............................................................12AMM 6p..................................................................15AMM 6p B/C/D .......................................................15

Power Supply Units, See PSUPPD .............................................................................40PRBS......................................................................... 111Protected (1+1)............................................................60Protection ..............................................................81, 86Protection mechanisms ...............................................44Pseudo Random Bit Sequence, See PRBSPSU ...........................................................................126PSU DC/DC Kit..........................................................126

cooling..................................................................126

Q

QAM ............................................................................66QAM, MMU..................................................................62

R

Radio Communication Channel, See RCCRadio segment protection............................................83Radio Terminal ........................................................4, 59

protected (1+1).......................................................60unprotected (1+0)...................................................59

Radio Unit, See RAURAU.............................................................................69

block diagram.........................................................71compatibility ...........................................................62external interfaces..................................................70types.......................................................................70

RCC...............................................................66, 98, 102RDI ..............................................................................41Received Signal Strength Indicator, See RSSIRemote Defect Indication

RDI .........................................................................41Remote Transmit Power Control, See RTPCRemovable Memory Module, See RMMRevision information ......................................................2RF loop ................................................................73, 108Ring protection ............................................................46RMM............................................................................20RSSI ............................................................................74RTPC.....................................................................90–91Rx equipment protection..............................................84Rx loop ......................................................................107

S

Scheduling...................................................................40Security management................................................ 113Separate installation ....................................................77Serial Peripheral Interface, See SPISFP............................................................................128SFPe..........................................................................128SFPo..........................................................................128Shaping .......................................................................40Simple Network Management Protocol, See SNMPSmall Form Factor Pluggable, See SFPSMU...............................................................................6SMU2...........................................................................56

140 4/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Index

SNCP...........................................................................45SNMP ................................................................105, 120Sofix...........................................................................123Software management ..............................................109Space diversity ............................................................81SPI bus........................................................................10Static routing.............................................................. 117STM-1

interface .................................................................27LTU ........................................................................28

Sub-Network Connection Protection, See SNCPSwitch Multiplexer Unit, See SMUSwitching mode ...........................................................45Synchronization.....................................................31, 52System

architecture ..............................................................9overview...................................................................3

T

TDM bus........................................................................9Time Division Multiplexing, See TDMTraffic routing...............................................................42Transmit Power Control...............................................90Tx equipment protection........................................82–83

U

UBR.............................................................................38Uni-directional..............................................................45Universal Serial Bus, See USBUnnumbered interfaces ............................................. 117Unprotected (1+0) .......................................................59USB ..................................................................... 21, 117User I/O ...............................................................21, 108

V

VBR .............................................................................38Virtual links ................................................................ 118VP/VC Cross-connection.............................................39

W

Working standby....................................................60, 81

1414/1555-CSH 109 32/1-V1 Uen B 2007-09-14

Print Preview - C:Documents and SettingsQMATALM agtool...

Documents

Transcript of Print Preview - C:Documents and SettingsQMATALM agtool...