MINI-LINK TN R3 ETSI. Technical Description MINI-LINK

Transcription

1 MINI-LINK TN R3 ETSI Technical Description MINI-LINK

2

3 MINI-LINK TN R3 ETSI Technical Description

4 Copyright Ericsson AB All Rights Reserved Disclaimer No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. 4/1555-CSH /1-V1 Uen B

5 Contents Contents 1 Introduction General Revision Information 2 2 System Overview Introduction Indoor Part with AMM Indoor Part with ATU Outdoor Part 7 3 Basic Node System Architecture Access Module Magazine (AMM) Node Processor Unit (NPU) E1 Interfaces STM-1 Interface Ethernet Traffic ATM Aggregation Traffic Routing Protection Mechanisms Synchronization Equipment Handling MINI-LINK E Co-siting Unstructured E3 Interface 57 4 Radio Terminals Overview Modem Unit (MMU) Radio Unit (RAU) Antennas PMP Functionality Protection Transmit Power Control Performance Management 92 4/1555-CSH /1-V1 Uen B

6 MINI-LINK TN R3 ETSI 5 Access Termination Unit (ATU) Overview ATU ATU C Management Fault Management Configuration Management Software Management License Management Performance Management Security Management Data Communication Network (DCN) Management Tools and Interfaces Accessories Interface Connection Field (ICF) PSU DC/DC Kit Small Form Factor Pluggable Optical splitter/combiner DCN LAN Switch 128 Glossary 131 Index 137 4/1555-CSH /1-V1 Uen B

7 15 GHz 15 GHz 15 GHz 15 GHz PFU3 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 and SDH multiplexing, Ethernet transport, ATM aggregation as well as protection mechanisms on link and network level. The software configurable traffic routing minimizes the use of cables, improves network quality and facilitates control from a remote location. With the high level of integration, rack space can be reduced by up to 70% compared to traditional solutions. Configurations range from small end sites with one single radio terminal to large hub sites where all the traffic from a number of southbound links is aggregated into one link, microwave or optical, in the northbound direction. 00/PFU3 01/PFU3 08/FAU2 07/NPU MMU2 F 155 MMU2 E 155 MMU2 E 155 MMU2 E 155 E1/DS1 E1/DS1 E1/DS1 15 GHz 15 GHz ALARM POWER ALIGNMENT 15 GHz 15 GHz ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER RADIO CABLE ALIGNMENT RADIO CABLE ALARM POWER RADIO CABLE ALIGNMENT PFU3 FAU2 NPU3 LTU Figure 1 A MINI-LINK TN R3 configuration /1555-CSH /1-V1 Uen B

8 MINI-LINK TN R3 ETSI The purpose of this description is to support the reader with detailed information on included products and accessories, from technical and functional points of view. Detailed technical system data is available in MINI-LINK TN ETSI Product Specification. Note: If there is any conflict between this document and information in MINI LINK TN ETSI Product Specification or compliance statements, the latter ones will supersede this document. Some functions described in this document are subject to license handling, that is 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 /1-V1 Uen B

9 15 GHz 15 GHz 15 GHz 15 GHz 15 GHz 15 GHz NPU3 PFU3 FAU2 PFU3 MMU2 E 155 System Overview 2 System Overview 2.1 Introduction This section gives a brief introduction to the system and its components. Indoor part with AMM Outdoor part with Antenna and RAU 00/PFU3 01/PFU3 08/FAU2 07/NPU LTU MMU2 F 155 MMU2 E 155 E1/DS1 E1/DS1 E1/DS1 NPU Indoor part with ATU Figure 2 Outdoor and indoor parts 9961 A MINI-LINK TN R3 Network Element (NE) can, from a hardware and installation point of view, be divided into two parts: Indoor part of two types: Access Module Magazine (AMM) with plug-in units, see Section 2.2 on 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 be divided into the following parts: 4/1555-CSH /1-V1 Uen B

10 MINI-LINK TN R3 ETSI Basic Node Radio Terminals The Basic Node holds the system platform providing traffic and system control, such as traffic routing, multiplexing, protection mechanisms and management functions. Specific plug-in units provide traffic interfaces, PDH, SDH and Ethernet, for connection to network equipment such as a radio base station, ADM or LAN. ATM aggregation is also supported. Finally, it includes indoor mechanical housing, power distribution and cooling. For more information, see Section 3 on page 9. Each Radio Terminal provides microwave transmission from 2x2to155Mbit/s,operatingwithinthe6to38GHzfrequency bands, utilizing C-QPSK and 16, 64, 128 QAM modulation schemes. It can be configured as unprotected (1+0) or protected (1+1). For more information, see Section 4 on page 59. Network Element Radio Terminals External Equipment Basic Node Figure 3 Basic Node and Radio Terminals 6731 The Basic Node and Radio Terminal concept does not apply to an NE with ATU. However, the self-contained unit implements applicable parts such as, traffic interfaces, control and management functions, power, cooling and the indoor part of an unprotected (1+0) Radio Terminal with C-QPSK modulation. The management features and tools are described in Section 6 on page /1555-CSH /1-V1 Uen B

11 PFU3 FAU2 INFORMATION MMU2 E 155 System Overview 2.2 Indoor Part with AMM NPU AMM 2p B AMM 6p D MMU2 B 4-34 LTU 16x2 LTU 155e/o NPU1 B 01/PFU3 07/NPU 08/FAU MMU2 F 155 MMU2 E 155 E1/DS1 E1/DS1 E1/DS1 08/FAU2 01/PFU3 LTU NPU3 PFU1 PFU3 00/PFU MMU2 E 155 E1/DS1 PFU3 FAU2 07/NPU LTU MMU2 F 155 E1/DS1 E1/DS1 NPU3 PFU3 00/PFU3 AMM 6p C AMM 20p 9686 Figure 4 AMMs The indoor part consists of an Access Module Magazine (AMM) with plug-in units interconnected through a backplane. One plug-in unit occupies one slot in the 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, further described in Section 3 on page 9 and Section 4 on page 59. Access Module Magazine (AMM) Node Processor Unit (NPU) Line Termination Unit (LTU) Modem Unit (MMU) Ethernet Interface Unit (ETU) ATM Aggregation Unit (AAU) The AMM houses the plug-in units and provides backplane interconnection of traffic, power and control signals. The NPU handles the system s control functions. It also provides traffic and management interfaces. The LTU provides PDH or SDH traffic interfaces. The MMU constitutes the indoor part of a Radio Terminal. It determines the traffic capacity and modulation scheme. The ETU provides Ethernet traffic interfaces. The AAU provides ATM aggregation of traffic on E1 links. 4/1555-CSH /1-V1 Uen B

12 60V RAU MINI-LINK TN R3 ETSI Switch Multiplexer Unit (SMU) Power Filter Unit (PFU) Fan Unit (FAU) The SMU provides traffic and DCN interfaces for MINI LINK E equipment. The PFU filters the external power and distributes the internal power to the plug-in units via the backplane. 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 TN R3 Edge Node. It can be used for transmission of PDH traffic and in Ethernet bridge applications. The ATU comprises one self-contained unit, with a height of 1U, for installation in 19 or metric racks. It can also be mounted on a wall, using a dedicated mounting set, or put on a desk. E1:11 E1:9 E1:7 E1:5 10/100BASE-T 0V DC -48V 10BASE-T O&M E1:10 E1:8 E1:6 E1:4 BR LAN Bridge Figure 5 ATU 9957 The ATU provides unprotected (1+0) microwave transmission within the 6 to 38 GHz frequency bands using C QPSK modulation, when connected to an RAU with antenna. The interconnection between the ATU and the outdoor part is one coaxial cable carrying full duplex traffic, DC supply voltage, and management data. Different ATU types are available offering traffic capacity from 2x2 to 17x2 Mbit/s, which can be shared between PDH traffic with a maximum of 8xE1 and Ethernet traffic over a maximum of 16xE1. The ATU is further described in Section 5 on page /1555-CSH /1-V1 Uen B

13 15 GHz 15 GHz ALARM POWER 15 GHz 15 GHz RADIO CABLE ALARM POWER ALIGNMENT System Overview 2.4 Outdoor Part The outdoor part is supplied for various frequency bands. It consists of an antenna, a Radio Unit (RAU) and associated installation hardware. For protected (1+1) systems, two RAUs and one or two antennas are used. When using one antenna, the two RAUs are connected to the antenna using a power splitter. The RAU and the antenna are easily installed on a wide range of support structures. The RAU is fitted directly to the antenna as standard, integrated installation. The RAU and the antenna can also be fitted separately and connected by a flexible waveguide. In all cases, the antenna is easily aligned and the RAU can be disconnected and replaced without affecting the antenna alignment. The RAU is described in Section 4.3 on page 69. The antennas are described in Section 4.4 on page 76. RADIO CABLE ALIGNMENT 1+0 terminal integrated installation 1+0 terminal separate installation 1+1 terminal integrated power splitter 8499 Figure 6 RAUs and antennas in different installation alternatives 4/1555-CSH /1-V1 Uen B

14 MINI-LINK TN R3 ETSI 8 4/1555-CSH /1-V1 Uen B

15 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. The buses are used for traffic handling, system control and power distribution. Plug-in Unit BPI Plug-in Unit Backplane TDM PCI SPI Power Power Filter Unit Node Processor Unit Figure 7 System architecture TDM Bus The Time Division Multiplexing (TDM) bus is used for traffic routing between the plug-in units. It is also used for routing of the DCN channels, used for O&M data transport. The lowest switching level is E1 for traffic connections and 64 kbit/s for DCN channels. The traffic connections on the TDM bus are unstructured with independent timing. The bus has a switching capacity of 820 Mbit/s. It is redundant for additional protection against hardware failures. 4/1555-CSH /1-V1 Uen B

16 MINI-LINK TN R3 ETSI PCI Bus The Peripheral Component Interconnect (PCI) bus is a high bandwidth multiplexed address/data bus used for control and supervision. Its main use is for communication between the NPU software and other plug-in units software and functional blocks SPI Bus The Serial Peripheral Interface (SPI) is a low speed synchronous serial interface 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 Power Bus The external power supply is connected to a PFU (or NPU2/NPU3 B for AMM 2p/AMM 2p B). The internal power supply is distributed via the Power bus to the other plug-in units. When using two PFUs in an AMM, the bus is redundant BPI Bus The Board Pair Interconnect (BPI) bus is used for communication between two plug-in units in a protected (1+1) configuration, for example when using two LTU 155 units in a Multiplexer Section Protection (MSP)1+1 configuration. It also interconnects groups of four plug-in units, enabling board protection schemes including three and four plug-in units PTP Connection The Point-to-Point (PTP) connection joins services to services (for example Ethernet over VCs dropped by ADM) and services to line interfaces (for example Ethernet over modem or ATM over SDH modem), see Figure 8 on page /1555-CSH /1-V1 Uen B

17 Basic Node ATM Ethernet ADM Ethernet ADM Services PTP Connections Line Interface LTU Radio Modem Radio Modem Line interface Figure 8 PTP Connections Access Module Magazine (AMM) The indoor part consists of an Access Module Magazine (AMM) with plug-in units. This section describes the AMM types and their associated cooling and power supply functions AMM 2p and AMM 2p B AMM 2p is suitable for end site and repeater site applications. There are two models: AMM 2p has two half-height slots equipped with one NPU2 and the optional LTU 12/1 Kit. AMM 2p B has two half-height slots equipped with one NPU3 and the optional LTU3 12/1. Two full-height slots can be equipped with MMU, LTU or ETU. The height of an AMM 2p or an AMM 2p B is 1U. The FAU4 is used depending on the configuration, see Section on page 13. AMM 2p and AMM 2p B can be fitted in a standard 19" or metric rack or on a wall using a dedicated mounting set. 4/1555-CSH /1-V1 Uen B

18 MINI-LINK TN R3 ETSI /NPU 00 LIFT LIFT LIFT LIFT ID Far 01 end NPU2 FAU4 L LTU3 12/1 NE Name IP addr.+mask 9976 Figure 9 AMM 2p NPU3 FAU4 L LTU3 12/ Figure 10 AMM 2p B 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 bus in the backplane of the AMM. External Power Supply 48 V DC or +24 V DC _ + NPU2 Figure 11 Power supply for AMM 2p 7019 AMM 2p B is power supplied by 48 V DC or +24 V DC redundant power. Two DC 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 /1-V1 Uen B

19 Basic Node Redundant Power Supply 48 V DC or +24 V DC _ + _ + NPU3 Figure 12 Power supply for AMM 2p B 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, placed vertically inside the AMM. FAU4 holds three internal fans. If the indoor location has other fan units, which provide sufficient cooling through the AMM, the FAU4 can be omitted. However, air filters should be present in the cabinet door. Complete rules for cooling are available in MINI-LINK TN ETSI Product Specification and the Product Catalog. Air out NPU3 MMU2 E Air in Figure 13 Cooling airflow in AMM 2p B 9715 The air enters at the right hand side of the AMM and exits at the left hand side of the AMM AMM 6p B/C/D AMM 6p B/C/D is suitable for medium-sized hub sites or prioritized small-sites with 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 on page 14. AMM 6p C or D have four (D) or five (C) full-height horizontal slots, four (D) or two (C) half-height horizontal slots and two half-height vertical slots. They house one or two NPU3, one or two PFU3 B and one FAU2, see Figure 15 on page 14 and Figure 16 on page 14. 4/1555-CSH /1-V1 Uen B

20 PFU3 FAU2 PFU3 FAU2 PFU3 FAU2 MINI-LINK TN R3 ETSI 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) Radio Terminal, 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 using a dedicated mounting set. The height of AMM 6p B/C/D is 3U. PFU3 00/PFU3 01/PFU3 07/NPU 08/FAU NPU1 B NPU1 B LTU 16x2 LTU 155e/o PFU3 MMU2 B 4-34 MMU2 B 4-34 LTU 155e Figure 14 FAU2 AMM 6p B 7855 PFU3 B NPU3 00/PFU3 01/PFU3 07/NPU 08/FAU E1/DS1 LTU E1/DS1 E1/DS1 MMU2 F 155 NPU3 MMU2 F 155 PFU3 MMU2 E 155 Figure 15 FAU2 AMM 6p C /PFU3 01/PFU3 07/NPU 08/FAU E1/DS1 PFU3 B NPU3 LTU E1/DS1 E1/DS1 NPU3 MMU2 F 155 PFU3 MMU2 E 155 Figure 16 FAU2 AMM 6p D /1555-CSH /1-V1 Uen B

21 PFU3 FAU2 Basic Node Power Supply AMM 6p B is power supplied by 48 V DC, connected to the PFU3. AMM 6p C/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 the power 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. External Power Supply PFU3: 48V DC PFU3 B: 48V DC or +24V DC + + PFU3 or PFU3 B Figure 17 Power supply for AMM 6p B, C or D Cooling PFU3/PFU3 B provides input low voltage protection, transient protection, soft start and electronic fuse to limit surge currents at start-up, or overload currents during short circuit. Forced air-cooling is always required and provided by FAU2, which holds two internal fans. Air out 07/NPU E1/DS1 00/PFU3 01/PFU3 08/FAU2 LTU E1/DS1 E1/DS1 NPU3 MMU2 F 155 PFU3 MMU2 E 155 Figure 18 Airflow in AMM 6p Air in 9707 The air enters at the front on the right hand side of the AMM and exits at the rear on the left hand side of the AMM. 4/1555-CSH /1-V1 Uen B

22 INFORMATION MINI-LINK TN R3 ETSI AMM 20p The AMM 20p is suitable for large-sized hub sites, for example at the intersection between the optical network and the microwave network. It has 20 full-height slots, one housing an NPU1 B and two half-height slots housing one 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, and are positioned in adjacent slots starting with an even slot number. A cable shelf is fitted directly underneath the AMM to enable neat handling of cables connected to the fronts of the plug-in units. An FAU1 is fitted on top of the AMM unless forced air-cooling is provided. An air 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. Air Guide Plate FAU1-48V Power A Alarm A Fault Power Alarm B Power B -48V FAN UNIT PFU1 MMU MMU2 B 4-34 MMU2 B 4-34 LTU 16x2 LTU 155e/o NPU 8x2 NPU1 B PFU1 Cable Shelf NPU1 B Figure 19 AMM 20p /1555-CSH /1-V1 Uen B

23 Basic Node Power Supply AMM 20p is power supplied by 48 V DC, connected to the PFU1 or via an Interface Connection Field (ICF1). The power is distributed from the PFU1 to the plug-in units, via the power bus in the backplane of the AMM. The power system is made redundant using two PFU1s, utilizing the redundant power bus. The PSU DC/DC kit enables connection to +24 V DC power supply, see Section 7.2 on page 126. The ICF1 is not used in this installation alternative. External Power Supply 48 V DC Power supply with ICF1 _ + _ + FAU1 ICF1 External Power Supply 48 V DC Power supply without ICF1 _ + _ FAU1 PFU1 PFU Figure 20 Power supply for AMM 20p PFU1 Fault Fan alarm 48 V DC Power BR Fan alarm 0V -48V DC Figure 21 PFU PFU1 has one 48 V DC connector for external power supply and one connector for import of alarms from FAU1, as the FAU1 is not connected to the AMM backplane. 4/1555-CSH /1-V1 Uen B

24 MINI-LINK TN R3 ETSI Cooling PFU1 provides input low voltage protection, transient protection, soft start and electronic fuse to limit surge currents at start-up, or overload currents during short circuit. A redundant PFU1 can be extracted or inserted without affecting the power system. Forced air-cooling is provided by FAU1, fitted directly above the AMM. The air enters through the cable shelf, flows directly past the plug-in units and exits at the top of the AMM through the air guide plate. If the indoor location has other fan units, which provide sufficient cooling through the AMM, the FAU1 can be omitted. However, air filters should be present in the cabinet door. Complete rules for cooling are available in MINI-LINK TN ETSI Product Specification and the Product Catalog. Air Guide Plate FAU1 Air out AMM 20p Cable Shelf Air in Figure 22 Side view of the airflow in AMM 20p /1555-CSH /1-V1 Uen B

25 Basic Node Power A -48V Alarm A Fault Power Alarm B Power B -48V FAN UNIT Fan alarm 48 V DC A A Fan alarm B 48 V DC B Figure 23 FAU FAU1 has an automatic fan speed control and houses three internal fans. FAU1 has two 48 V DC connectors for redundant power supply. Two connectors are also available for export of alarms to PFU1. 4/1555-CSH /1-V1 Uen B

26 MINI-LINK TN R3 ETSI 3.3 Node Processor Unit (NPU) The NPU implements the system s control functions. One NPU is always required in the AMM. The NPU also provides traffic, DCN and management interfaces. The NPU holds a Removable Memory Module (RMM) for storage of license and configuration information. The following NPUs are available: 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. RMM NPU1 B ERICSSON Fault Power BR 10/100Base-T Console 10/100BASE-T O&M O&M E1:3A-3D E1:2A-2D User I/O:1A-1I Not used 2x(4xE1) User I/O NPU1 B NPU2 +24V DC 0V F P RMM NPU2 0V DC -48V E1/DS1:3A-3D 10/100 Base-T O&M +24 V DC 48 V DC 1x(4xE1) 10/100BASE-T O&M NPU3 E1/DS1 10/100 Base-T TR:4A-4D/User Out:E-F TR:3 10/100 Base-T F P LAN O&M RMM NPU3 4xE1 + 2xUser Out O&M 2x(10/100BASE-T) Figure 24 NPUs 9959 The following summarizes the common functions of the NPUs: Traffic handling 20 4/1555-CSH /1-V1 Uen B

27 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 as summarized below. NPU1 B NPU2 NPU3 2x(4xE1) for traffic connections Three User Input ports Three User Output ports 1x(4xE1) for traffic connections Filters the external power and distributes the internal power The Ethernet interface can be used for Ethernet bridge applications 1x(4xE1) for traffic connections Two User Output ports Functional Blocks This section describes the internal and external functions of the NPUs, based on the block diagrams in Figure 25 on page 22, Figure 26 on page 22 and Figure 27 on page 23. 4/1555-CSH /1-V1 Uen B

28 MINI-LINK TN R3 ETSI TDM Bus TDM Line Interface 8xE1 PCI Bus PCI Node Processor Ethernet 10/100BASE-T SPI Bus SPI User I/O 3 User In 3 User Out Power Bus Power Secondary voltages O&M USB Figure 25 Block diagram for NPU1 B 8358 TDM Bus TDM Line Interface 4xE1 PCI Bus PCI Node Processor Ethernet 10/100BASE-T SPI Bus SPI O&M USB Power Bus Power Secondary voltages External power supply +24 V DC or 48 V DC 8280 Figure 26 Block diagram for NPU2 22 4/1555-CSH /1-V1 Uen B

29 Basic Node User Output TDM Bus TDM Line Interface 4xE1 + 2xUser Out PCI Bus PCI Node Processor Ethernet 2x10/100BASE-T SPI Bus SPI O&M USB Power Bus Power Secondary voltages Figure 27 Block diagram for NPU TDM PCI SPI 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. This block interfaces the PCI bus used for control and supervision communication. The block communicates with the Node Processor, which handles control and supervision of the whole NE. This block interfaces the SPI bus used for equipment status communication. The block communicates with the Node Processor, which handles equipment status of the whole NE. Failure is indicated by LED s on the front of the unit. 4/1555-CSH /1-V1 Uen B

30 MINI-LINK TN R3 ETSI Power This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. NPU3 has no connector for external power. For AMM 2p B the power is distributed to the backplane at the left hand side of the AMM Node Processor Line Interface Ethernet O&M User I/O The Node Processor is the central processor of the NE, responsible for the traffic and control functions listed in Section on page 20. This block provides the E1 line interfaces for external connection. This block provides a 10/100BASE-T connection to site LAN and 10/100BASE-T traffic 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 service personnel to make calls to other sites. This digital Engineering Order Wire (EOW) solution utilizes VoIP in the IP DCN. For more information on EOW for MINI-LINK, see MINI-LINK Engineering Order Wire Feature Description. See Section 3.6 on page 31 for more information on Ethernet traffic. This block provides the LCT connection to the NPU using a USB interface. The equipment is accessed using a local IP address. This block handles the User Out ports on the NPU3 and the User In and User Out ports on the NPU1 B, see Section on page /1555-CSH /1-V1 Uen B

31 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 traffic connection to a radio base station or for connection to leased line networks NPU NPU2 and NPU3 provides four E1 interfaces, NPU1 B provides eight E1 interfaces, see Section on page LTU Overview The following LTUs with E1 interfaces are available: LTU 16/1 LTU3 12/1 Fits in any AMM. The LTU 16/1 provides 16 additional E1 interfaces. Fits in an AMM 2p (as LTU 12/1 Kit, incl. washer), AMM 2p B and AMM 6p C or D. For sites where the eight E1 interfaces on the NPU3 are insufficient, the LTU3 12/1 provides 12 additional E1 interfaces. LTU 16/1 ERICSSON Fault Power BR E1:4A-4D E1:3A-3D E1:2A-2D E1:1A-1D LTU 16/1 4x(4xE1) LTU E1/DS1 E1/DS1 E1/DS1 LTU3 12/1 TR:3A-3D TR:2A-2D TR:1A-1D Fault Power Figure 28 3x(4xE1) LTUs with E1 interfaces /1555-CSH /1-V1 Uen B

32 MINI-LINK TN R3 ETSI Functional Blocks This section describes the internal and external functions of the LTUs with E1 interfaces, based on the block diagram in Figure 29 on page 26. TDM Bus TDM Line Interface 12xE1 or 16xE1 PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Secondary voltages Figure 29 Block diagram for LTU 16/1 and LTU3 12/ TDM This block interfaces the TDM bus by receiving and transmitting the traffic (nxe1) Control and Supervision SPI Power This block interfaces the PCI bus and handles control and supervision. Its main functions are to collect alarms, control settings and tests. The block communicates with the NPU over the PCI bus. This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED s on the front of the unit. This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. 26 4/1555-CSH /1-V1 Uen B

33 Basic Node 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 type of plug-in unit. The E1s are available at the TDM bus for traffic routing to other plug-in units. If incoming SDH radio traffic on MMU2 E/F 155 shall be connected to the TDM bus, an LTU 155 is needed as a terminal multiplexer to extract the E1s from the STM-1. See Section 4.2 on page Overview At aggregation sites where the high capacity optical network connects to the microwave network. The LTU 155 provides an effective interface using one 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 radio base stations. Both electrical and optical interfaces are available. The STM-1 interface on LTU 155s can be equipment and line protected using MSP 1+1, see Section on page 48. 4/1555-CSH /1-V1 Uen B

34 MINI-LINK TN R3 ETSI Electrical or optical interface LTU xE1 TDM Bus LTU 16/1 LTU 16/1 NPU1 B Figure 30 nxe1 nxe1 nxe1 An example of how to use the STM-1 interface LTU 155 There are three versions of the LTU 155: LTU 155e LTU 155e/o LTU B 155 Provides one electrical interface (G.703), mapping 63xE1. Provides one optical interface (short haul S-1.1) and one electrical interface (G.703), mapping 63xE1. Note: only one at a time. Provides one optical interface (short haul S-1.1) and one electrical interface (G.703), mapping 21xE1. Note: only one at a time. The LTU 155 fits in all AMM types. 28 4/1555-CSH /1-V1 Uen B

35 Basic Node LTU 155e ERICSSON Fault Power BR RX EL. TX Electrical LTU 155e LTU 155e/o ERICSSON Fault Power BR Caution TX OPT. RX RX EL. TX LTU B 155 ERICSSON Fault Power BR Caution Invisible Invisible Laser Radiation When Open Class 1 Laser Laser Radiation When Open Class 1 Laser Optical Electrical LTU 155e/o Optical TX OPT. RX RX EL. TX Electrical LTU B 155 Figure 31 LTU Functional Blocks This section describes the internal and external functions of the LTU 155, based on the block diagram in Figure 32 on page 30. 4/1555-CSH /1-V1 Uen B

36 MINI-LINK TN R3 ETSI BPI (MSP 1+1) TDM Bus TDM VC-12 MS/RS VC-4 STM-1 PCI Bus Control and Supervision SPI Bus SPI SDH Equipment Clock Power Bus Power Secondary voltages Figure 32 Block diagram for LTU TDM This block interfaces the TDM bus by receiving and transmitting the traffic (nxe1) and DCN channels (nx64 kbit/s) Control and Supervision SPI Power This block interfaces the PCI bus and handles control and supervision. Its main functions are to collect alarms, control settings and tests. The block communicates with the NPU over the PCI bus. The block holds a Device Processor (DP) running plug-in unit specific software. This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED s on the front of the unit. This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. 30 4/1555-CSH /1-V1 Uen B

37 Basic Node VC MS/RS VC-4 This block maps 63xE1 (or 21xE1) to/from 63xVC-12 (or 21xVC-12) adding overhead bytes. The LTU B 155 registers 21xE1 interfaces from the first TUG3, that is the KLM numbers , through 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 external connection SDH Equipment Clock This block handles timing and synchronization. The LTU 155 utilizes the synchronization functions described in Section 3.10 on page Ethernet Traffic Overview ETU2 provides five 10/100BASE-T interfaces and one 10/100/1000BASE-T interface. See Section on page 33. NPU2 provides one 10/100BASE-T interface, combined for Ethernet Traffic and Ethernet Site LAN. See Section on page 20. NPU3 provides two 10/100BASE-T interfaces, one for Ethernet Traffic and one for Ethernet Site LAN. See Section on page 20 ATU provides one 10/100BASE-T interface for Ethernet Traffic and one 10BASE-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 single hop or through a network. Figure 33 on page 32 shows an example of how the different units can be used in a network. 4/1555-CSH /1-V1 Uen B

38 MINI-LINK TN R3 ETSI 100BASE-T ATU 1-16xE1 AMM 2p B NPU3 AMM 6p ETU2 AMM 2p NPU2 ATU AMM 20p ETU2 Ethernet core network AMM 6p C NPU3 AMM 6p ETU2 AMM 2p NPU2 Figure 33 Ethernet traffic in a MINI-LINK TN R3 network 9963 The bandwidth of each Ethernet bridge connection is nxe1 per inverse multiplexer in the unit, where n 48 for ETU2 (with a maximum of 96 E1s in total), and n 16 for NPU2 and ATU. NPU2, NPU3and ATU have one inverse multiplexer while ETU2 has six. Ethernet traffic is connected to the units using RJ-45 connectors with support for shielded cable. The Ethernet bridge connections have auto-negotiation 10/100 Mbit/s speed and full/half duplex. Transparency to all kinds of traffic is supported, including IEEE 802.1Q VLAN, MAC address based VLAN, VLAN tag ID based and untagged frames, frames with up to 2 VLAN tags or frames with ICS tag. The number of E1s in each connection is configured from the management system. The traffic is distributed over the E1s by an inverse multiplexer. The load sharing is seamless and independent of the Ethernet layer. Figure 34 on page 33 shows the protocol layers involved in an Ethernet bridge connection. 32 4/1555-CSH /1-V1 Uen B

39 Basic Node Ethernet traffic Ethernet Ethernet Ethernet traffic Inverse Multiplexer Inverse Multiplexer SDH/PDH G.703 G.703 Figure 34 Protocol stack Performance Management The following performance counters for Ethernet traffic are available: Number of discarded packets, for example due to overflow or CRC-32 errors Number of sent/received frames Number of sent/received octets Ethernet Interface Unit (ETU) The ETU2 provides five 10/100BASE-T interfaces and one 10/100/1000BASE-T interface. ItcanbefittedinanyAMM. ETU2 ERICSSON Fault Power BR 1000 Link 10/100/1000BASE-T 10/100BASE-T :1 ETU2 10/100/1000BASE-T 10/100BASE-T Figure 35 ETU Functional Blocks This section describes the ETU2 based on the block diagram in Figure 36 on page 34. 4/1555-CSH /1-V1 Uen B

40 MINI-LINK TN R3 ETSI Inverse Multiplexers Ethernet nxe1 10/100/1000BASE-T nxe1 10/100BASE-T nxe1 10/100BASE-T TDM Bus TDM nxe1 nxe1 10/100BASE-T 10/100BASE-T nxe1 10/100BASE-T PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Secondary voltages Figure 36 Block diagram for ETU TDM This block interfaces the TDM bus by receiving and transmitting the E1s used to carry Ethernet traffic Inverse Multiplexers Ethernet Each inverse multiplexer converts one Ethernet connection into nxe1, where n 16, transmitted to and received from the TDM block. This block provides the unit s external Ethernet interfaces. Each interface is linked to one inverse multiplexer. The Ethernet Traffic function offers 8 priority queues in both directions to/from the Ethernet ports. The mapping follows IEEE 802.1D 2004 strict priority queuing and can be configured, per node, to use 1 8 of the queues. Which queue to use for untagged packets can be configured per port and direction. 34 4/1555-CSH /1-V1 Uen B

41 Basic Node Control and Supervision SPI Power This block interfaces the PCI bus and handles control and supervision. Its main functions are to collect alarms, control settings and tests. The block communicates with the NPU over the PCI bus. This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED s on the front of the unit. This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. 4/1555-CSH /1-V1 Uen B

42 MINI-LINK TN R3 ETSI 3.7 ATM Aggregation Overview The growing demand for higher transmission capacity in access networks can be handled by increasing the physical capacity, introducing traffic aggregation or combining the two approaches. Traffic aggregation in MINI-LINK TN R3 is achieved by fitting an ATM Aggregation Unit (AAU) in the AMM. This is typically done at hub sites where HSDPA traffic is aggregated, thus reducing the number of required E1 links in the northbound direction. The AAU performs ATM VP/VC cross-connection providing statistical gains. Figure 37 on page 36 shows an example of how Virtual Paths (VP) and Virtual Channels (VC), carried over E1s, can be cross-connected reducing the number of required E1s. VC/UBR Mbit/s VC/CBR 4.7 Mbit/s VP/CBR 8xE1 MINI-LINK TN with AAU 11xE1 VP/CBR VC/UBR+ VC/UBR+ Shared 13 Mbit/s VC/UBR Mbit/s VC/CBR 4.3 Mbit/s VP/CBR 8xE1 VC/CBR 4.7 Mbit/s VC/CBR 4.3 Mbit/s Figure 37 VP/VC cross-connection 8924 Often the transmission network is used for both GSM and WCDMA traffic. The GSM traffic is handled as ordinary TDM traffic routed in the backplane and transported transparently through the NE while WCDMA traffic is routed to the AAU for packet aggregation before it is routed to its destination port. WCDMA traffic comprises both R99 standard (voice and data channel up to 384 kbit/s) and HSDPA traffic. The largest aggregation gain is however obtained for the HSDPA traffic, when the low priority traffic can be transported using best effort service categories. Figure 38 on page 37 shows how the different traffic types are routed in the backplane. 36 4/1555-CSH /1-V1 Uen B

43 Basic Node WCDMA GSM RAU AAU MMU TDM bus LTU MMU MMU RAU RAU Figure 38 Traffic types ATM Aggregation Unit (AAU) The main function of the AAU is to aggregate traffic from other plug-in units in the AMM. It is fitted in an AMM 6p B, C, D or AMM 20p. AAU ERICSSON Fault Power BR AAU Figure 39 AAU 8490 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 into IMA groups. Each G.804 link or IMA group corresponds to one internal ATM interface and the maximum number of ATM interfaces handled by the AAU is 31. 4/1555-CSH /1-V1 Uen B

44 MINI-LINK TN R3 ETSI The following is a summary of the AAU functions: Capacity of 96xE1. 24xE1 is the default capacity and additional groups of 24xE1 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 Channel Connections (VCC) and 100 Virtual Path Connections (VPC). Service Categories support; CBR, rt-vbr, nrt-vbr.1,2,3, UBR and UBR+MDCR Policing Shaping F4/F5 OAM support for Fault Management Functional Blocks This section describes the internal and external functions of the AAU, based on the block diagram in Figure 40 on page 38. TDM Bus TDM IMA Utopia Interface ATM Cross-connect PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Secondary voltages Figure 40 Block diagram for AAU /1555-CSH /1-V1 Uen B

45 Basic Node TDM IMA This block interfaces the TDM bus by receiving and transmitting nxe1 (n 96) for aggregation. The transmitted E1s need synchronization input utilizing the Network Synchronization mode. This block implements the Inverse Multiplexing for ATM (IMA). The ATM cells are broken up and transmitted across multiple IMA links, then reconstructed back into the original ATM cell order at the destination ATM Cross-connectt This block handles the ATM cross-connection of traffic on a maximum of 31 ATM interfaces. Each ATM interface corresponds to either an IMA group or a G.804 link. When setting up cross-connections, Connection Admission Control (CAC) calculations are performed in order to accept or reject new connection requests according 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 specific connection in order to ensure that it conforms to the configured traffic descriptor of the connection. It fully meets the relevant requirements and recommendations from the ATM Forum Traffic Management and ITU-T I.371. Policing is enabled by default for all the service categories and can be disabled on a per-connection basis. VP/VC Cross-connection The different ATM interfaces can be cross-connected, mapping ingress connections to egress connections and vice versa. In a VP cross-connection only VPI numbers are associated between two ATM interfaces. In a VC cross-connection the VPC is terminated and the ingress and egress connections are associated using both VCI and VPI numbers. 4/1555-CSH /1-V1 Uen B

46 MINI-LINK TN R3 ETSI Buffering and Congestion Thresholds After the cross-connection phase, the ingress cell streams flow into the buffering section. Buffers are provided on a per-egress ATM interface basis for three 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 amount of free buffer space available. The larger the free buffer space, the higher the threshold. Scheduling and Shaping Shaping is intended as a traffic limitation on the peak rate. The ATM Cross-connect provides 31 independent schedulers that are individually mapped to any of the 31 ATM interfaces. The bandwidth assigned from the schedulers to each ATM interface is shaped at a value corresponding to the physical bandwidth of the ATM interface, for example 2 Mbit/s for a G.804 link Control and Supervision SPI This block interfaces the PCI bus and handles control and supervision. Its main functions are to collect alarms, control settings and tests. The block communicates with the NPU over the PCI bus. The block holds a Device Processor (DP) running plug-in unit specific software. This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED s on the front of the unit. 40 4/1555-CSH /1-V1 Uen B

47 Basic Node Power This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function 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 forward direction. The AIS cells at VP or VC level are sent upon one of the following conditions: 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 indications in the backward direction. RDI is sent to the far-end from a VPC/VCC endpoint as soon as it has detected an AIS condition. Loop Back (LB), allowing for operations related information to be inserted at one location along a VPC/VCC and returned (or looped back) at a different location, without having to take the connection out-of-service. This capability is performed by inserting an LB cell at an accessible point along the VPC/VCC without disrupting the sequence of user cells while minimizing the user cells transfer delay. This cell is looped back at a downstream point according to the information contained in its information field. 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 monitoring continuity and detection of ATM layer defects in real time. 4/1555-CSH /1-V1 Uen B

48 MINI-LINK TN R3 ETSI 3.8 Traffic Routing The main function of the microwave hub site is to collect traffic carried over microwave radio links from many sites and aggregate it into a higher capacity transmission link through the access network towards the core network. The transmission link northbound may be microwave or optical. These hub sites have usually been built by connecting individual microwave Radio Terminals with cables through Digital Distribution Frames (DDF) and external cross-connection equipment. MINI-LINK TN R3 provides a traffic routing function that facilitates the handling of traffic aggregation. This function enables interconnection of all traffic connections going through the NE. This means that an aggregation site can be realized using one AMM housing several Radio Terminals with all the cross-connections done in the backplane. Each plug-in unit connects nxe1 to the backplane, where the traffic is cross-connected to another plug-in unit. The E1s are unstructured with independent timing. One way of using this function at a large site is to cross-connect traffic from several Radio Terminals to one LTU 155 (63xE1) for further connection to the core network. At a smaller site, it is possible to collect traffic from several Radio Terminals with 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 nxe1 nxe1 nxe1 nxe1 nxe1 TDM bus 400xE1 nxe1 nxe1 nxe1 nxe1 Plug-in Unit Plug-in Unit Plug-in Unit Plug-in Unit 6626 Figure 41 Traffic routing 42 4/1555-CSH /1-V1 Uen B

49 Basic Node Note that the TDM bus can carry close to 400 uni-directional E1s in AMM 20p and AMM 6p, half of this in AMM 2p, but some of the capacity is allocated for DCN and control information. To facilitate future software functional upgrades it is not recommended to route traffic on more than 366 uni-directional E1s over the 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 MINI-LINK Connexion The MINI-LINK Connexion application provides a way to provision end-to-end E1 connections in a network. The network can be planned in advance without the need for the actual network. When the pre-configured E1 connections are applied to the real network a consistency check is done. All operations related to the E1 provisioning are done from a topology map with a graphical presentation of the E1 connections. Color codes are used to visualize alarm status. Detailed alarm info and status are obtained by clicking on a connection on the map. A number of different reports can be extracted periodically or on demand to view performance data and statistics related to an E1 end-to-end connection. For more information, see MINI-LINK Connexion User Manual. 4/1555-CSH /1-V1 Uen B

50 MINI-LINK TN R3 ETSI 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 Overview To ensure high availability, MINI-LINK TN R3 provides protection mechanisms on various layers in the transmission network as illustrated in Figure 42 on page 44. Network layer protection using the 1+1 E1 SNCP mechanism provides protection 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 c between two adjacent NEs 1 and 2 in Figure 42 on page 44. Physical link layer protection uses both signal failure and signal degradation as switching criteria. By routing the protected traffic in parallel through different physical units, equipment protection can also be achieved. An example using two plug-in units is shown for the NEs 1 and 2 in Figure 42 on page 44. Network layer protection Physical link layer protection Equipment protection c 2 a b 5 6 = Network Element (NE) = Plug-in unit 6627 Figure 42 MINI-LINK TN R3 provides high availability through various protection mechanisms 44 4/1555-CSH /1-V1 Uen B

51 Basic Node Network layer and physical link layer protection share the following characteristics: Permanently Bridged Uni-directional Non-revertive Identical traffic is transmitted on the active and the passive physical link/connection. Only the affected direction is switched to protection. The equipment terminating the physical link/connection in either end will select which line to be active independently. No switch back to the original link/connection is performed after recovery from failure. The original active link/connection is used as passive link/connection after the protection is re-established. 1+1 One active link/connection and one passive (standby) link/connection. Automatic/Manual switching mode In automatic mode, the switching is done based on signal failure or signal degradation. Switching can also be initiated from the management system provided that the passive link/connection is free from alarms. In manual mode, the switching is only initiated from the management system, regardless of the state of the links/connections Network layer protection E1 SNCP 1+1 E1 Sub-Network Connection Protection (1+1 E1 SNCP) is a protection mechanism used for network protection on E1 level, between two MINI-LINK TN R3 NEs. It is based on the simple principle that one E1 is transmitted on two separate E1 connections. The switching is performed at the receiving end where the two connections are terminated. It switches automatically between the two incoming E1s in order to use the better of the two. The decision to switch is based on signal failure of the signal received (LOS or AIS). At each end of the protected E1 connection, two E1 connections must be configured 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, provided that AIS is propagated end-to-end. The 1+1 E1 SNCP function is independent of the 1+1 radio protection and the MSP /1555-CSH /1-V1 Uen B

52 MINI-LINK TN R3 ETSI 1+1 E1 SNCP group 1+1 E1 SNCP group Tx Rx Protected E1 Link or sub-network Rx Tx Protected E1 Unprotected E1 Unprotected E1 Figure E1 SNCP principle 6632 Performance data is collected and fault management is provided for unprotected as well as protected E1 interfaces (that is the 1+1 E1 SNCP group). This gives accurate information on the availability of network connections Ring Protection Ring Star Tree Figure 44 Network topologies 6628 The 1+1 E1 SNCP mechanism described in the previous section can be used to create protected ring structures in the microwave network. In a ring topology, all nodes 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 can therefore be protected with a 1+1 E1 SNCP group configured at each end of the connection. The traffic is transmitted in both directions of the ring and the traffic is received from two directions at the termination point. 46 4/1555-CSH /1-V1 Uen B

53 Basic Node In this solution, the ring network can tolerate one failure without losing transmission. When the failure re-occurs, the affected connections are switched in the other direction. In a MINI-LINK TN R3 network, these ring structures can be built using PDH Radio Terminals with capacities of up to 32x2 Mbit/s, and using SDH Radio Terminals 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 is dropped 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 protect the connection from A to E the two alternative connections from A to E must be defined 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 connections between A and C must also be configured as two 1+1 E1 SNCP groups at A and C. A F B E C D Figure 45 Example of ring protection with 1+1 E1 SNCP 6629 The 1+1 E1 SNCP function can be used to build protection in more complex topologies than rings, using the same principle. 4/1555-CSH /1-V1 Uen B

54 MINI-LINK TN R3 ETSI MSP 1+1 The STM-1 interface supports Multiplexer Section Protection (MSP) 1+1. This SDH protection mechanism provides both link protection and equipment protection. Its main purpose is to provide maximum protection at the interface between the microwave network and the optical network. MSP 1+1 requires two LTU 155 plug-in units configured to work in an MSP 1+1 pair, delivering only one set of 63xE1 (or 21xE1) to the backplane at a time as illustrated in Figure 46 on page 48. The unit intercommunication is done over the BPI bus. STM-1 electrical or optical SDH Mapping BPI MSP 1+1 Switch Passive LTU155e/o TDM Bus SDH Mapping Active LTU155e/o 63xE1 Figure 46 Two LTU 155e/o plug-in units in an MSP 1+1 configuration 7468 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 /1-V1 Uen B

55 Basic Node LTU 155 MSP Switch Controller SF/SD E1->VC-12->VC-4 63xE1 Rx Switch MS/RS Rx Tx Tx LTU 155 Tx 63xE1 E1->VC-12->VC-4 Rx MS/RS Rx MSP Switch Controller 6633 Figure 47 MSP 1+1 principle 4/1555-CSH /1-V1 Uen B

56 MINI-LINK TN R3 ETSI Equipment and Line Protection AMM 2p B MMU2 E 155 MMU2 E 155 AMM 2p B MMU2 E 155 MMU2 E 155 Figure 48 ADM ADM High capacity hop protected with ELP 9719 The Equipment and Line Protection (ELP) functionality is able to simultaneously protect the STM-1 line interface and the radio equipment against any single point of failure (e.g. the single MMU). This is commonly used to protect a high capacity hop. On the radio side, it uses a single frequency (hot standby configuration). In this mode 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 achieved by using only one optical interface on the ADM (without the MSP protection in the ADM). In ELP configuration, in order to save radio bandwidth, only one of the two multiplex sections of the MSP (working/protection) is sent over the air. For this reason some limitations apply to the data contained in the MSOH, which (if used) 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 DCC connections on working and protection section, but the same traffic shall be bridged on both sides. 50 4/1555-CSH /1-V1 Uen B

57 Basic Node Enhanced Equipment Protection Enhanced Equipment Protection (EEP) (optical) protects the STM-1 line on MMU2 E/F 155. Through a Small Form Factor Pluggable (SFP), see Section 7.3 on page 128, plus an external optical combiner/splitter, see Figure 49 on page 51, the STM-1 input/output are protected; while one MMU Tx laser is transmitting, the other one must be switched off (Laser Shut Down). See also MMU2 F 155 in Section 4.2 on page 61. Figure 49 Optical splitter/combiner /1555-CSH /1-V1 Uen B

58 MINI-LINK TN R3 ETSI 3.10 Synchronization Overview MINI-LINK TN is by default working in Free Running mode. In this mode the node is not a part of the synchronization network, and does not maintain a SEC. The node behavior can be described by how the different protocols are processed: Unstructured primary rate PDH channels are passed transparently except for timing recovery and jitter attenuation. This is also valid for robbed timeslot DCN channels. STM/STS interfaces are configured to take outgoing synch from local oscillator or loop timing. If SSM is enabled Do Not Use is transmitted. PDH primary rate channels terminated in an AAU/ATM switch are configured to take outgoing synch from local oscillator or loop timing. PDH primary rate channels used for Ethernet over PDH will have outgoing synch generated by the local oscillators. MINI-LINK TN ETSI can from release 3.1 also be configured to Network Synchronized mode where the node maintains a SEC and distributes synchronization and synchronization quality level status on cross connected PDH channels (ITU-T G.813). Note that unstructured primary rate PDH channels are still passed transparently as in the Free Running mode, but now with reduced jitter. This is also valid for PDH connections that are used for DCN including robbed timeslot DCN. With Network Synchronized mode it possible to build a synchronized network where all the NEs are synchronized to the same source. Figure 50 on page 53 shows an example of a network where the synchronization information is carried to all the NEs through an assigned path. In case of link failures the synchronization may be reestablished using the unassigned synchronization paths. 52 4/1555-CSH /1-V1 Uen B

59 Basic Node Assigned synchronization path Unassigned synchronization path Network Element Figure 50 Master-slave synchronized network 9531 In this mode MINI-LINK TN will use the Node Clock on all the protocol layers generated in the node. The Network Synchronized mode includes the following functions: SDH Equipment Clock The SEC function maintains an equipment clock with network reference clock selection, clock generation, filtering and redundancy. As illustrated in Figure 51 on page 54 a list of interfaces can be selected and prioritized as candidates for synchronization input to the SEC. All E1 and STM-1 interfaces, or when protected 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 NPU3 as an external 2048 khz synchronization clock input interface. The SEC will select and do automatic synchronization trail restoration based on the priority table and the status of the inputs. In the event of failure of all synchronization source inputs, the SEC will enter holdover mode using its own internal clock as source. (Note: G.813 performance during trail restoration and holdover requires at least one MMU2 C, AAU or LTU 155 plug-in unit in the AMM) The SEC clock is distributed throughout the magazine. All terminated protocol layers interfaces (e.g. STM-1 and E1 from AAU) can be individually configured to follow the SEC or to do Loop Timing, that is using the recovered receive clock (RxClock) on the outgoing link. 4/1555-CSH /1-V1 Uen B

60 MINI-LINK TN R3 ETSI Status The synchronization status functions are used to propagate and signal the quality level of the SEC to the node interfaces. The Synchronization Status Propagation logic distributes synchronization status for transmission of synchronization status messages (SSM) on interfaces supporting and configured for this. The Squelch logic distributes information on poor or lost synchronization input to interfaces that cannot signal synchronization status messages, for these to send AIS. From management squelch can be enabled/disabled for the whole node 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 sources candidates they should have their Wait To Restore Time set longer then the Hold Off Time of the protected interface, to avoid unnecessary switching of synchronization sources. SEC Synchronization Logic Status Network Synchronization T0 Free Running Synchronization Status Propagation Logic Squelch STM-1 MSP 1+1 E1 1+1 E1 SNCP 2 MHz T1 T2 T3 Selection Interfaces Interfaces E1 STM-1 T0, T1, T2 and T3: ITU-T SDH Equipment Clock (SEC) names Loop Timing or NE Timing Figure 51 MINI-LINK TN Synchronization functions /1555-CSH /1-V1 Uen B

61 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 enables adding of new Radio Terminals or other plug-in units without disturbing existing 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 button causes a request for removal to be sent to the control system. When replacing a faulty plug-in unit, the new plug-in unit automatically inherits the configuration of the old plug-in unit. The system configuration is stored non-volatile on the RMM on the NPU and can also be backed up and restored using a local or central FTP server. The RMM storage thus enables NPU replacement without using a FTP server. The backplane in all AMMs has an digital serial number which is also stored on 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 cold restart can be initiated for an NE or single plug-in unit, this type of restart disturbs the traffic. A warm restart is only available for the whole NE. This will restart the control system and will not affect the traffic. This is possible due to the separated control and traffic system. All plug-in units are equipped with temperature sensors. Overheated boards, which exceed limit thresholds, are put in reduced service or out of service by the control system. This is to avoid hardware failures in case of a fan failure. The plug-in unit is automatically returned to normal operation when temperature is below the high threshold level. There are two thresholds: Crossing the high temperature threshold shuts down the plug-in unit s control system (reduced operation). The traffic function of the plug-in unit will still be in operation. Crossing the excessive temperature threshold shuts down the entire plug-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. 4/1555-CSH /1-V1 Uen B

62 MINI-LINK TN R3 ETSI 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 interface MINI-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 SMU2 ERICSSON Fault Power BR O&M E3:3A E2:3B-3C E1:2A-2B DIG SC:1A-1B SMU2 O&M E3/ 2xE2 2xE1 2xE0 Figure 52 SMU All the traffic capacities are multiplexed/demultiplexed to nxe1 for connection to the TDM bus. MINI-LINK E 2xE0 2xE1, 1xE2, 2xE2 or 1xE3 + 1xE1 SMU2 MINI-LINK TN 2xE1 to 17xE1 TDM Bus Figure 53 MINI-LINK E co-siting /1555-CSH /1-V1 Uen B

63 Basic Node 3.13 Unstructured E3 Interface The E3 interface on the SMU2 can be used to provide unstructured E3 traffic over 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. MMU2 RAU RAU MMU2 E3 SMU2 SMU2 E3 MMU2 RAU RAU MMU2 Figure 54 Transmission solution for unstructured E /1555-CSH /1-V1 Uen B

64 MINI-LINK TN R3 ETSI 58 4/1555-CSH /1-V1 Uen B

65 15 GHz 15 GHz 15 GHz 15 GHz INFORMATION -48V Power A Alarm A Fault Power Alarm B Power B -48V RADIO CABLE 15 GHz 15 GHz 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, 64 or 128 QAM modulation schemes. It can be configured as unprotected (1+0) or protected (1+1). ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER ALIGNMENT FAN UNIT MMU MMU NPU 8x2 LTU 16x2 LTU 155e/o NPU1 B MMU Figure 55 An unprotected (1+0) Radio Terminal (grayed) An unprotected (1+0) Radio Terminal comprises: One RAU One antenna One MMU 4/1555-CSH /1-V1 Uen B

66 MINI-LINK TN R3 ETSI 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 (frequency diversity). Receiver switching is hitless. In hot standby mode, one transmitter is working while the other one is in standby, it is not transmitting but ready to transmit if the active transmitter malfunctions. Both RAUs are receiving signals and the best signal is used according to an alarm priority list. In working standby mode, both radio paths are active in parallel using different frequencies. 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 are available 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 /1-V1 Uen B

67 Radio Terminals 4.2 Modem Unit (MMU) Overview The MMU is the indoor part of the Radio Terminal and determines the traffic capacity and modulation. It is available in the following types: MMU2 B A traffic capacity agile plug-in unit for C-QPSK modulation, used for the following traffic capacities in Mbit/s: 2xE1, 4xE1, 8xE1, 17xE1 MMU2 C A traffic capacity and modulation agile plug-in unit, used for the following modulation schemes and traffic capacities 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 following modulation 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 following modulation 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 on page 68, used for the following modulation schemes and traffic capacities in Mbit/s. XPIC is only used in combination with 128 QAM, if not used MMU2 F 155 has the same modulation schemes and traffic capacities as MMU2 E 155: 16 QAM: STM-1 + 1xE1 64 QAM: STM-1 + 1xE1 128 QAM: 2xSTM-1 + 2xE1 (requires 2xMMU2 E/F 155) 4/1555-CSH /1-V1 Uen B

68 MINI-LINK TN R3 ETSI MMU2 B and MMU2 C have the same functionality regarding mechanics and interfaces. However, there is an important difference when it comes to RAU compatibility: 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 be combined with MMU2 B or MMU2 C in a 1+0 or 1+1 hop. MMU2 D can be placed in the same AMM as MMU2 B or MMU2 C but can not be part of the same radio terminal. ERICSSON MMU2 B 60V RAU Fault Power BR MMU2 B RAU ERICSSON MMU2 C 60V RAU Fault Power BR MMU2 C ERICSSON MMU2 D 60V RAU Fault Power BR MMU2 D Figure 56 MMU2 B, C and D 9720 MMU2 E 155 and MMU2 F 155 have the same functionality regarding mechanics and interfaces except for XPIC support on MMU2 F 155. MMU2 E 155 and MMU2 F 155 are compatible with both RAU2 N and RAU2 X. For the STM-1 interface a Small Form Factor Pluggable (SFP) is needed. The SFP can be either electrical (SFPe) or optical (SFPo), see Section 7.3 on page /1555-CSH /1-V1 Uen B

69 Radio Terminals MMU2 E 155 TX RX 60V RAU ERICSSON Fault Power BR SFP STM-1 MMU2 F 155 TX RX 60V RAU ERICSSON Fault Power BR SFP STM-1 XPIC Figure 57 MMU2 E and F 155. Note: MMU2 F 155 has XPIC support Functional Block This section describes the internal and external functions of the MMU, based on the block diagram in Figure 58 on page 63. BPI Bus (1+1) BPI Bus (1+1) TDM Bus TDM Multiplexer/ Demultiplexer DCC Traffic DCC Traffic Radio Frame Multiplexer Radio Frame Demultiplexer Modulator Demodulator Cable Interface RAU PCI Bus HCC HCC Control and Supervision RCC SPI Bus SPI Power Bus Power Secondary voltages Figure 58 Block diagram for MMU /1555-CSH /1-V1 Uen B

70 MINI-LINK TN R3 ETSI High-speed bus BPI Bus (1+1) BPI Bus (1+1) STM-1 Line interface TDM Bus TDM (Wayside traffic, E1 only) DCC Traffic DCC Traffic Radio Frame Multiplexer Radio Frame Demultiplexer Modulator Demodulator Cable Interface RAU HCC HCC PCI Bus Control and Supervision RCC XPIC (MMU2 F 155) SPI Bus SPI Power Bus Power Secondary voltages Figure 59 Block diagram for MMU2 E/F 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, for further transmission to the Radio Frame Multiplexer. In the receiving direction, it performs 34/8 and 8/2 demultiplexing, depending on the traffic capacity. The demultiplexed traffic and DCC are transmitted to the TDM bus. In a protected system, the block interfaces the BPI bus, see Section on page 81. Note: Note: The TDM block in MMU2 E/F 155 performs no multiplexing/demultiplexi ng. The traffic in the receiving direction equals 1xE1. The high-speed bus will be possible to use with future functionality such as integrated ADM. It is currently not enabled. 64 4/1555-CSH /1-V1 Uen B

71 Radio Terminals Radio Frame Multiplexer The Radio Frame Multiplexer handles multiplexing of different data types into one data stream, scrambling and FEC encoding. In a protected system, the block interfaces the BPI bus, see Section on page 81. The following data types are multiplexed into the composite data stream to be 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 rate adaptation (stuffing). If no valid data is present at the input, an AIS signal is inserted 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 the hop, where 2 n 9 depending on traffic capacity and modulation. HCC The Hop Communication Channel (HCC) is used for the exchange of control and supervision information between near-end and far-end MMUs. Multiplexing The three different data types together with check bits and frame lock bits are sent in a composite data format defined by the frame format that is loaded into a Frame Format RAM. The 12 frame alignment signal bits are placed at the beginning of the frame. Stuffing bits are inserted into the composite frame. Scrambling and FEC Encoding The synchronous scrambler has a length of and is synchronized each eighth frame (super frame). For C-QPSK, the FEC bits are inserted according to the frame format and calculated using an interleaving scheme. Reed Solomon coding is used for 16 QAM. 4/1555-CSH /1-V1 Uen B

72 MINI-LINK TN R3 ETSI Modulator Cable Interface The composite data stream from the Radio Frame Multiplexer is modulated, D/A converted 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) is an offset QPSK modulating technique. It has a high spectrum efficiency compared to other constant envelope modulation. Square QAM (Quadrature Amplitude Modulation), consisting of two independent amplitude modulated quadratures. The carrier is amplitude and phase modulated. The technique doubles the spectrum efficiency compared 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 a 490 MHz signal. The following signals are frequency multiplexed in the Cable Interface for further distribution through a coaxial cable to the outdoor RAUs: 350 MHz transmitting IF signal 140 MHz receiving IF signal DC power supply Demodulator Radio Communication Channel (RCC) signal as an Amplitude Shift Keying (ASK) signal In addition to the above, the cable interface includes an over voltage protection circuit. The received 140 MHz signal is AGC amplified and filtered prior to conversion to I/Q baseband signals. The baseband signals are pulse shaped in a Nyqvist filter and A/D converted before being demodulated Radio Frame Demultiplexer On the receiving side the received composite data stream is demultiplexed and FEC corrected. The frame alignment function searches and locks the receiver to the frame alignment bit patterns in the received data stream. 66 4/1555-CSH /1-V1 Uen B

73 Radio Terminals Descrambling and FEC Decoding For C-QPSK, error correction is accomplished using FEC parity bits in combination with a data quality measurement from the Demodulator. A Reed Solomon decoder is used for 16 QAM. The descrambler transforms the signal to its original state enabling the Demultiplexer to properly distribute the received information to its destinations. Demultiplexing Demultiplexing is performed according to the frame format used. The Demultiplexer generates a frame fault alarm if frame synchronization is lost. The number of errored bits in the traffic data stream is measured using parity bits. These are used for BER detection and performance monitoring. Stuffing control 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 hitless switching) Hitless switching (for 1+1 protection) DCC On the receiving side, elastic buffering and clock recovery is performed on the DCC. HCC The Hop Communication Channel (HCC) is used for the exchange of control and supervision information between near-end and far-end MMUs Control and Supervision This block interfaces the PCI bus and handles control and supervision. Its main functions are to collect alarms, control settings and tests. The block communicates with the NPU over the PCI bus. 4/1555-CSH /1-V1 Uen B

74 MINI-LINK TN R3 ETSI SPI Power The block holds a Device Processor (DP) running plug-in unit specific software. It handles BER collection and communicates with processors in the RAU through the RCC. Exchange of control and supervision data over the hop is made through the HCC. This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED s on the front of the unit. This block interfaces the Power bus and provides secondary voltages for the unit. All plug-in units have a standard power module providing electronic soft start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. Furthermore, this block provides a stable voltage for the RAU, distributed in the radio cable 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 be transmitted at the same time using one dual polarized antenna. The wanted polarization is called co-polarization and the unwanted/interference polarization is called cross-polarization. Even though the polarizations are orthogonal there is a small interference between them, in the antennas and due to propagation effects over the hop. The effect of this interference needs to be cancelled out with the XPIC functionality In XPIC, each polarization path receives both the polar signal and the cross-polar signal. The receiver subtracts the cross-polar signal from the polar signal and cancels the cross-polar interference. XPIC processes and combines the signals from the two receiving paths to recover the original, independent signals. An XPIC solution doubles the wireless link capacity and enables operators to reduce cost in terms of their frequency license fee. 68 4/1555-CSH /1-V1 Uen B

75 Radio Terminals 4.3 Radio Unit (RAU) Overview The basic function of the Radio Unit (RAU) is to generate and receive the RF signal and convert it to/from the signal format in the radio cable, connecting the RAU and the MMU. It can be combined with a wide range of antennas in integrated or separate installation. The RAU connects to the antenna at the waveguide interface. Disconnection and replacement of the RAU can be done without 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 and hoisting. 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 is determined by the RAU only and is pre-set at factory and configured on site using the LCT. Frequency channel arrangements are available according to ITU-R and ETSI recommendations. For detailed information on frequency versions, see the Product Catalog and MINI LINK TN ETSI Product Specification. Two types of mechanical design exist, RAU1 and RAU2. ALARM POWER RADIO CABLE ALIGNMENT Figure 60 RAU1 RAU1 and RAU2 mechanical design RAU /1555-CSH /1-V1 Uen B

76 MINI-LINK TN R3 ETSI External Interfaces RADIO POWER ALARM RADIO CABLE ALIGNMENT RADIO CABLE ALARM POWER ALIGNMENT Figure External interfaces, RAU1 and RAU2 mechanical design 8464 Item Description 1 Radio cable connection to the MMU, 50 Ω N-type connector. The connector 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 RAU Types A RAU is designated as RAUX YF, for example RAU2 N 23. When ordering, additional information about frequency sub-band and output power version is necessary. 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-QPSK MMU. NorX, for example RAU2 N 23, indicates compatibility with a C-QPSK MMU and a QAM MMU. 70 4/1555-CSH /1-V1 Uen B

77 Radio Terminals Xu, for example RAU2 Xu 23, indicates compatibility with a C-QPSK MMU and a QAM MMU within ML TN together with an optional feature (released in TN 4). F indicates frequency band Functional Blocks This section describes the RAU internal and external functions based on the block diagrams in Figure 62 on page 71and Figure 63 on page 72. Transmit IF Signal Processing Transmit IF Demodulator Transmit RF Oscillator Power Amplifier DC DC/DC Converter Secondary Voltages MMU Cable Interface Receive IF Oscillator Receive RF Oscillator RF Loop Branching Filter Antenna Downconverter 2 Filter and Amplifier Downconverter 1 Low Noise Amplifier Received Signal Strength Indicator RCC Alignment Port Control and Supervision Processor Alarm and Control Figure 62 Block diagram for RAU1 and RAU /1555-CSH /1-V1 Uen B

78 MINI-LINK TN R3 ETSI Transmit IF Oscillator Transmit RF Oscillator Transmit IF Signal Processing Upconverter 1 Filter and Amplifier Upconverter 2 Power Amplifier MMU Cable Interface DC DC/DC Converter Secondary Voltages Receive IF Oscillator Receive RF Oscillator RF Loop Branching Filter Antenna Downconverter 2 Filter and Amplifier Downconverter 1 Low Noise Amplifier Received Signal Strength Indicator Figure 63 RCC Alignment Port Control and Supervision Processor Alarm and Control Block diagram for RAU1 N and RAU2 N Cable Interface Transmit IF signal, a modulated signal with a nominal frequency of 350 MHz. Up-link Radio Communication Channel (RCC), an Amplitude Shift Keying (ASK) modulated command and control signal with a nominal frequency of 6.5 MHz. DC supply voltage to the RAU. Similarly, the outgoing signals from the RAU are multiplexed in the Cable Interface: Receive IF signal, which has a nominal frequency of 140 MHz. Down-link RCC, an ASK modulated command and control signal with a nominal frequency of 4.5 MHz. In addition to the above, the Cable Interface includes an over voltage protection circuit. 72 4/1555-CSH /1-V1 Uen B

79 Radio Terminals Transmit IF Signal Processing The input amplifier is automatically gain-controlled so that no compensation is required due to the cable length between the indoor and outdoor equipment. The level is used to generate an alarm, indicating that the transmit IF signal level is too low due to excessive cable losses Transmit IF Demodulator The transmit IF signal is amplified, limited and demodulated. The demodulated signal is fed to the Transmit RF Oscillator onto the RF carrier Transmit IF Oscillator Up-converter 1 The frequency of the transmitter is controlled in a Phase Locked Loop (PLL), including a Voltage Control Oscillator (VCO). An unlocked VCO loop generates a transmitter frequency alarm. The first up-converter gives an IF signal of approximately 2 GHz Filter and Amplifier The converted signal is amplified and fed through a bandpass filter Transmit RF Oscillator Up-converter 2 This oscillator is implemented in the same way as the Transmit IF Oscillator. The transmit IF signal is amplified and up-converted to the selected radio transmit frequency Power Amplifier RF Loop The transmitter output power is controlled by adjustment of the gain in the Power Amplifier. The output power is set in steps of 1 db from the LCT. It is also possible to turn the transmitter on or off utilizing the Power Amplifier. The output power signal level is monitored enabling an output power alarm. The RF Loop is used for test purposes only. When the loop is set, the transmitter frequency is set to receiver frequency and the transmitted signal in the Branching Filter is transferred to the receiving side. 4/1555-CSH /1-V1 Uen B

80 MINI-LINK TN R3 ETSI Branching Filter On the transmitting side, the signal is fed to the antenna through an output branching filter. The signal from the antenna is fed to the receiving side through an input branching filter. The antenna and both branching filters are connected with an impedance T-junction Low Noise Amplifier The received signal is fed from the input branching filter into a Low Noise Amplifier Receive RF Oscillator The frequency of the receiver is controlled in a PLL, including a VCO. An unlocked VCO loop generates a receiver frequency alarm Down-converter 1 The first down-converter gives an IF signal of approximately 1 GHz Receive IF Oscillator This oscillator is used for the second downconversion to 140 MHz and consists of a PLL, including a VCO. The VCO is also used for adjustment of the received 140 MHz signal (through a control signal setting the division number in the IF PLL). A frequency error signal from the MMU is used to shift the receiver oscillator in order to facilitate an Automatic Frequency Control (AFC) loop Down-converter 2 The signal is down-converted a second time to the IF of 140 MHz Received Signal Strength Indicator (RSSI) A portion of the 140 MHz signal is fed to a calibrated detector in the RSSI to provide an accurate receiver input level measurement. The measured level is accessible either as an analog voltage at the alignment port or in dbm from the management software. The RSSI signal is also used for adjustment of the output power by means of the Automatic Transmit Power Control (ATPC) 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 indoor MMU processor. Summary status signals are visualized by LEDs on the RAU. 74 4/1555-CSH /1-V1 Uen B

81 Radio Terminals Commands from the indoor units are executed. These commands include transmitter activation/deactivation, channel frequency settings, output power settings and RF loop activation/deactivation. The processor controls the RAU s internal processes and loops DC/DC Converter The DC/DC Converter provides a stable voltage for the RAU. 4/1555-CSH /1-V1 Uen B

82 15 GHz 15 GHz 15 GHz 15 GHz 15 GHz 15 GHz MINI-LINK TN R3 ETSI 4.4 Antennas Description The antennas range from 0.2 m up to 3.7 m in diameter, in single and dual polarized versions. All antennas are "compact", that is the design is compact with 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 be adjusted for vertical or horizontal polarization. All high performance antennas have an integrated radome Installation Integrated Installation For a 1+0 configuration, the RAU is fitted directly to the rear of the antenna in integrated installation. Single polarized antennas up to 1.8 m in diameter are normally fitted integrated with the Radio Unit (RAU). ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER RADIO CABLE ALIGNMENT Figure m, 0.3 m and 0.6 m compact antennas integrated with RAU RADIO POWER RADIO CABLE AGC ALARM RADIO POWER RADIO CABLE AGC ALARM Figure m and 0.6 m compact antennas integrated with RAU /1555-CSH /1-V1 Uen B

83 15 GHz 15 GHz ALARM POWER ALIGNMENT Radio Terminals For a 1+1 configuration the RAU2 can be fitted directly to an integrated power splitter. A similar solution is available for RAU1, using a waveguide between the power splitter and the antenna. A symmetrical power splitter version, with equal attenuation in both channels, is used in the majority of the installations. RADIO CABLE RADIO 2 Figure 66 RAU1 RAUs fitted to integrated power splitters RAU Separate Installation All antennas with IEC 154 Type B waveguide interface can be installed separately, by using a flexible waveguide to connect to the RAU. The dual polarized antennas and the m antennas are always installed separately. Figure 67 Separate installation in a 1+0 configuration /1555-CSH /1-V1 Uen B

84 MINI-LINK TN R3 ETSI Mounting Kits This section describes the mounting kits used for the 0.2 m, 0.3 m and 0.6 m antennas. A mounting kit consists of two rigid, extruded aluminum brackets connected with two stainless steel screws along the azimuth axis. The brackets are anodized and have threaded and unthreaded holes to provide adjustment of the antenna in azimuth and elevation. The support can be clamped to poles with a diameter of mm or on 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. Figure 68 Mounting kit for the 0.2 m compact antenna 6717 The 0.2 m compact antenna mounting kit can be adjusted by ±13 in elevation and by ±90 in azimuth. Figure 69 Mounting kit for the 0.3 m and 0.6 m compact antennas 6718 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 a mechanism for fine adjustment. 78 4/1555-CSH /1-V1 Uen B

85 Radio Terminals 4.5 PMP Functionality With Point-to-Multipoint (PMP) Functionality the number of antennas can be limited at the hub site. The MINI-LINK TN, PMP Functionality is served by a sector antenna which covers 45 or 90. Within a sector up to four frequencies are allocated. Each terminal radio at the hub acts as a PTP link to a dedicated terminal radio in the sector. Each of these links has its own dedicated sub-channel. Power Splitter Power Splitter Power Splitter Sector antenna Figure 70 Overview of MINI-LINK TN, PMP Functionality 9427 The system is scalable and offers configurations with two, three or four terminals per sector. Two types of mounting kits are available, where the choice of mounting kit depends on the amount of terminals to be installed. One kit supports configuration of up to four terminals connected to three integrated power splitters. The other kit supports configuration of two terminals connected to one integrated power splitter. 4/1555-CSH /1-V1 Uen B

86 15 GHz ALARM POWER ALIGNMENT MINI-LINK TN R3 ETSI 15 GHz ALARM POWER RADIO CABLE ALIGNMENT ALARM POWER RADIO CABLE ALIGNMENT RADIO CABLE Figure 71 Mounting kits for installation of two (left) up to four (right) radio terminals /1555-CSH /1-V1 Uen B

87 Radio Terminals Protection Overview A Radio Terminal can be configured for 1+1 protection. This configuration provides propagation protection and equipment protection on the MMU, RAU and antenna. Propagation protection may be used on radio links where fading due to meteorological and/or ground conditions make it difficult to meet the required transmission quality. Configurations for 1+1 protection can be in hot standby or working standby. In hot standby mode, one transmitter is working while the other one, tuned to the same frequency, is in standby. It is not transmitting but ready to transmit if the active transmitter malfunctions. Both RAUs receive signals. When using two antennas, they can be placed for space diversity with a mutual distance where the impact of fading is reduced. In working standby mode, both radio paths are active in parallel using different frequencies, realizing frequency diversity. Using two different frequencies improves availability, because the radio signals fade with little correlation to each other. Space diversity can be implemented as for hot standby systems. f1 Hot Standby f1 f1 Working Standby f2 Figure 72 Radio link protection modes 6654 For information specific for XPIC, Section on page Functional Description The following different protection cases can be identified: 4/1555-CSH /1-V1 Uen B

88 MINI-LINK TN R3 ETSI Tx Equipment Protection Working Standby Tx Equipment Protection Hot Standby Radio Segment Protection Rx Equipment Protection Tx Equipment Protection Working Standby This protection case involves two types of switch, TDM Tx switch and Traffic Alignment (TA) switch. The TDM Tx switch is a logical switch used to switch over the traffic to the redundant MMU, in case of a failure in the TDM Multiplexer part of the active MMU. This is accomplished by the NPU configuring the MMUs to listen to a certain TDM bus slot. The TA switch is used to feed the multiplexed traffic signals to the Radio Frame Multiplexer block in both MMUs, which is a condition for being able to perform hitless switching in the receiving end. Alarms generated in the RAU and MMU are monitored by the NPU, which based on the alarm severity commands the TDM and TA switches as appropriate. The switching principles are illustrated in Figure 73 on page /1555-CSH /1-V1 Uen B

89 Radio Terminals PCI TDM TDM Multiplexer/ Demultiplexer TA Switch Radio Frame Multiplexer Control and Supervision Modulator RCC Cable Interface MMU A Tx On/Off (Hot Standby) RAU A BPI TDM Tx Switch TA Switch Radio Frame Multiplexer Modulator Cable Interface MMU B RAU B TDM Multiplexer/ Demultiplexer Control and Supervision RCC Tx On/Off (Hot Standby) Node Processor NPU Figure 73 Tx Equipment Protection, Working and Hot Standby 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 is active. Hence, Tx must be switched off in the malfunctioning Radio Terminal and switched on in the standby. This is controlled by the DP in the Control and Supervision block of the MMU and communicated in the RCC. Alarms generated in the RAU and MMU are monitored by the NPU, which based on the alarm severity commands the TDM and TA switches as appropriate. The switching principles are illustrated in Figure 73 on page Radio Segment Protection This protection case involves a Diversity switch in each MMU, providing hitless and error free traffic switching in case of radio channel degradation. It is also used as equipment protection in case of a signal failure in the RAU Rx parts. 4/1555-CSH /1-V1 Uen B

90 MINI-LINK TN R3 ETSI The Diversity switches will work autonomous and are controlled by the switch logic in the active MMU Rx. The switch logic is implemented as software in the DP in the Control and Supervision block. The Diversity switch will react on the Early Warning (EW) signals, Input Power threshold alarm and FEC error alarm. The switch logic in one MMU needs information from the other MMU, which is sent over the BPI bus. Note that this switching is done under no fault conditions. The switching principles are illustrated in Figure 74 on page 84. TDM PCI MMU A RAU A Cable Interface Modulator Radio Frame Multiplexer Diversity Switch TDM Multiplexer/ Demultiplexer BPI Switch Logic Control and Supervision MMU B BPI Switch Logic Control and Supervision TDM Rx Switch RAU B Cable Interface Modulator Radio Frame Multiplexer Diversity Switch TDM Multiplexer/ Demultiplexer NPU Node Processor Figure 74 Radio Segment Protection and Rx Equipment Protection Rx Equipment Protection This protection case involves two types of switch, TDM Rx switch and Diversity switch. The TDM Rx switch is a logical switch used to switch over the traffic to the redundant MMU, in case of a failure in the TDM Demultiplexer part of the active 84 4/1555-CSH /1-V1 Uen B

91 Radio Terminals MMU. This is accomplished by the NPU configuring the MMUs to listen to a certain TDM bus slot. The Diversity switches will work autonomous and is controlled by the switch logic in the active MMU Rx. This is in accordance with the Radio Segment Protection case, with the difference that signal failure alarms have a higher priority level than the EW signals. Alarms generated in the RAU and MMU are monitored by the NPU, which based on the alarm severity commands the TDM switch as appropriate. The switching principles are illustrated in Figure 74 on page 84. 4/1555-CSH /1-V1 Uen B

92 MINI-LINK TN R3 ETSI Protection with XPIC (MMU2 F) AMM Configurations The protected 1+1 XPIC radio terminal configuration consists of four modems MMU2 F 155 with XPIC capability, four RAUs, and two integrated dual-polarized antennas or four separate antennas. See Figure 75 on page 86. ML TN ML TN MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 MMU 2 F 155 Figure XPIC configuration 9966 The four modems MMU2 F 155 are housed in the AMM 6p or the AMM 20p, in four adjacent slots that share the same BPI-4 bus. See Figure 76 on page /1555-CSH /1-V1 Uen B

93 Radio Terminals PFU2 FAU2 AMM 6p 0 1 NPU APU MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F XPIC AMM 20p PFU1 PFU1 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F XPIC MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 APU NPU NPU APU MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F XPIC 1+1 XPIC 1+1 XPIC 0/ Figure 76 AMM 6p and AMM 20p in 1+1 XPIC configuration 9967 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 the transmitted signal over the same wireless channel. Therefore, the front panel XPIC cross-cable shall connect modems in alternate slots (2&4 and 3&5, etc.). See Figure 77 on page 87. PFU2 AMM 6p FAU2 NPU APU MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F XPIC Figure 77 XPIC cross-cable connections (AMM 6p) Functional Description The 1+1 XPIC configuration provides propagation protection and equipment protection on the MMU, RAU and antenna when using both polarizations in co-channel dual polarized (CCDP) mode of operation with XPIC. 4/1555-CSH /1-V1 Uen B

94 MINI-LINK TN R3 ETSI Configurations for 1+1 XPIC protection can be in either hot standby (see Figure 78 on page 88) or working standby (see Figure 79 on page 89). Near end Node Far end Node Active f 1, V A Active MMU2 F 155 MMU2 F 155 f 1, V B MMU2 F 155 MMU2 F 155 Active f 1, H A Active XPIC cross-cables MMU2 F 155 MMU2 F 155 f 1, H B MMU2 F 155 MMU2 F 155 Figure XPIC in Hot Standby /1555-CSH /1-V1 Uen B

95 Radio Terminals Near end Node Far end Node Active f 1, V A Active MMU2 F 155 MMU2 F 155 f 2, V B MMU2 F 155 MMU2 F 155 Active f 1, H A Active XPIC cross-cables MMU2 F 155 MMU2 F 155 f 2, H B MMU2 F 155 MMU2 F 155 Figure XPIC in Working Standby 9970 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 and after repairing the fault. In 1+1 XPIC configuration the switching criteria are exactly the same criteria used in 1+1 protected configuration with single polarization mode and the two switching processes for H and V branches are independent. When a fault occurs on one polarization, e.g. V, and the switching criteria are satisfied, the switching to the protection link is initiated, from V A to V B.If the fault does not cause a high degradation of the cancelling signal on the orthogonal polarization (switching criteria for H polarization are not satisfied), the switching to the protection link, from H A to H B, is not initiated. If the depolarization is such that the H-polarization canceller is not able to cancel the cross-polar interference from H (switching criteria for H-polarization are satisfied), the switching to the protection link, from H A to H B, is initiated. A HW fault, for example on the V link, might cause a simultaneous degradation of the two polarizations, triggering a switch on both V and H link. Table 1 on page 90 summarizes the consequent actions to a fault on V-polarization link. 4/1555-CSH /1-V1 Uen B

96 MINI-LINK TN R3 ETSI Table 1 Starting condition V A Tx fault handling V A Tx fault handling V A propaga -tion fault handling Fault handling on a V-polarization link Vertical Polarization Tx side Working Standby Rx side f1-v A f1-v A and f2-v B N.A. f2-v B, disruption accepted N.A. f2-v B, disruption accepted N.A. f2-v B, hitless Tx side f1-h A and f2-h B N.A. N.A. N.A. Horizontal Polarization Rx side Vertical Polarization Tx side Rx side Hot Standby Tx side Horizontal Polarization f1-h A V A V A H A H A f1-h A or f2-h B, disruption accepted f1-h A or f2-h B, disruption accepted f1-h A or f2-h B, hitless V B V A or V B (quickest locked-in), disruption accepted N.A. V B, disruption accepted No action Rx side H A or H B (quickest locked-in), disruption accepted N.A. H A or H B, disruption accepted N.A. V B,hitless N.A. H A or H B, hitless In case of not-hitless switching traffic disruption of a comparable entity on both polarizations may happen. In hot-standby mode when the switching process is initiated the receivers will lock to the new active TX and the XPIC units will re-converge. The new active receiver 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 from the management system including setting of associated parameters. In ATPC mode the transmit power can be increased rapidly during fading conditions and allows the transmitter to operate at less than the maximum power during normal path conditions. The normally low transmit power allows more efficient use of the available spectrum while the high transmit power can be used as input to path reliability calculations, such as fading margin and carrier-to-interference ratio. The transmitter can be turned on or off from the management system. 90 4/1555-CSH /1-V1 Uen B

97 Radio Terminals Transmit power P max P ATPC max Pset Pout P fix min Pout P ATPC min RTPC mode ATPC mode Figure 80 Transmit power control RTPC Mode In RTPC mode the transmit power (P out ) ranges from a minimum level (P fix min )to a maximum level (P max ). The desired value (P set ) can be set in 1 db increments ATPC Mode ATPC is used to automatically adjust the transmit power (P out ) in order to maintain the received input level at the far-end terminal at a target value. The received input level is compared with the target value, a deviation is calculated and sent to the near-end terminal to be used as input for possible adjustment of the transmit power. ATPC varies the transmit power, between a selected maximum level (P ATPC max ) and a hardware specific minimum level (P ATPC min ). 4/1555-CSH /1-V1 Uen B

98 MINI-LINK TN R3 ETSI 4.8 Performance Management The purpose of Performance Management for the Radio Terminal is to monitor the 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 settable thresholds. BER of the composite signal and alarm generation with a configurable threshold. Block based performance data on the received composite signal. This data is presented as Errored Seconds (ES), Severly Errored Seconds (SES), Background Block Error (BBE), Unavailable Seconds (UAS) and Elapsed Time. In case of a protected system the block based performance data is evaluated at the protected interface. The BER and block based performance data are evaluated in-service by use of an error detection code in the composite signal. 92 4/1555-CSH /1-V1 Uen B

99 Access Termination Unit (ATU) 5 Access Termination Unit (ATU) 5.1 Overview This section describes the ATU, which implements the indoor part of a MINI-LINK TN R3 Edge Node. It can be used for transmission of PDH and Ethernet traffic. For more information on Ethernet traffic, see Section 3.6 on page 31. The ATU is a self-contained unit, with a height of 1U, for installation in a standard 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 38 GHz frequency bands using C-QPSK modulation, when connected to an RAU with antenna. An NE with ATU utilizes the same outdoor part as an NE with AMM. In addition to 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 ATU C Provides traffic capacity from 2x2 to 17x2 Mbit/s that can be shared between PDH and Ethernet traffic. Each ATU variant has a specific default functionality which can be extended with an optional feature, for example if both traffic types should be used. For more information on ATU variants and optional features, see the Product Catalog. For more information on ATU, see Section 5.2 on page 94. Provides traffic capacity from 2x2 to 4x2 for transmission of PDH traffic. For more information on ATU C, see Section 5.3 on page /1555-CSH /1-V1 Uen B

100 60V RAU MINI-LINK TN R3 ETSI 5.2 ATU This section describes the functions of ATU. The available traffic capacity, 2x2, 4x2, 8x2 and 17x2 Mbit/s, can be shared between: PDH traffic with a maximum of 8xE1. Ethernet traffic over a maximum of 16xE1. E1:11 E1:9 E1:7 E1:5 10/100BASE-T 0V DC -48V 10BASE-T O&M E1:10 E1:8 E1:6 E1:4 BR LAN Bridge 10BASE-T USB -48 V DC E1 10/100BASE-T RAU 9964 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 power supply 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 /1-V1 Uen B

101 Access Termination Unit (ATU) Functional Blocks This section describes the functions of ATU based on the block diagram in Figure 82 on page 95. E1 E1 E1 E1 E1 E1 E1 E1 10/100BASE-T Traffic 10BASE-T Site LAN Line Interface Ethernet nxe1 nxe1 Multiplexer/ Demultiplexer Control and Supervision Traffic Traffic DCC Radio Frame Multiplexer DCC HCC Radio Frame Demultiplexer HCC RCC Modulator Demodulator Cable Interface RAU USB O&M External Power Supply -48 V DC Power Secondary voltages Figure 82 Block diagram for ATU Line Interface Ethernet O&M This block provides the eight E1 line interfaces for connection of PDH traffic. It interfaces the Multiplexer/Demultiplexer block by transmitting and receiving the traffic (nxe1). This block provides the 10BASE-T interface for connection to a site LAN and the 10/100BASE-T interface for Ethernet traffic in Ethernet bridge applications. The Ethernet traffic is mapped on nxe1, where n 16, using one inverse multiplexer. The E1s are transmitted to and received from the Multiplexer/Demultiplexer block. This block provides the LCT connection. The equipment is accessed using a local IP address. 4/1555-CSH /1-V1 Uen B

102 MINI-LINK TN R3 ETSI 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 the RAU, distributed in the radio cable. It also provides input low voltage protection, transient protection, soft start and electronic fuse to limit surge currents at start-up, or overload currents during short circuit Multiplexer/Demultiplexer This block interfaces the Line Interface and the Ethernet blocks by receiving and transmitting the traffic. It performs 2/8 and 8/34 multiplexing, depending on the traffic capacity, for further transmission to the Radio Frame Multiplexer. In the receiving direction, it performs 34/8 and 8/2 demultiplexing, depending on the traffic capacity. The demultiplexed traffic is transmitted to the Line Interface and the Ethernet blocks Control and Supervision This block handles system control and supervision. Its main functions are to collect alarms, control settings and tests. It also holds an IP router for DCN handling. For the traffic over the hop it handles BER collection and communicates with processor in the RAU through the RCC. Exchange of control and supervision data over the hop is made through the HCC Radio Frame Multiplexer The Radio Frame Multiplexer handles multiplexing of different data types into one data stream, scrambling and FEC encoding. The following data types are multiplexed into the composite data stream to be 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 rate adaptation (stuffing). If no valid data is present at the input, an AIS signal is 96 4/1555-CSH /1-V1 Uen B

103 Access Termination Unit (ATU) inserted at nominal data rate. This means that the data traffic across the hop is replaced with ones (1). DCC DCC comprises 2x64 kbit/s channels used for DCN communication over the hop. HCC The Hop Communication Channel (HCC) is used for exchange of control and supervision information between the near-end and far-end. Multiplexing The three different data types together with check bits and frame lock bits are sent in a composite data format defined by the frame format that is loaded into a Frame Format RAM. The 12 frame alignment signal bits are placed at the beginning of the frame. Stuffing bits are inserted into the composite frame Modulator Cable Interface Scrambling and FEC Encoding The synchronous scrambler has a length of and is synchronized each eighth frame (super frame). The FEC bits are inserted according to the frame format and calculated using an interleaving scheme. The composite data stream from the Radio Frame Multiplexer is modulated, D/A converted and pulse shaped in a Nyqvist filter to optimize transmit spectrum. C-QPSK (Constant envelope offset Qaudrature Phase Shift Keying), an offset QPSK modulating technique, is used. It has a high spectrum efficiency compared to other constant envelope schemes. 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 a 490 MHz signal. The following signals are frequency multiplexed in the Cable Interface for further distribution through a coaxial cable to the outdoor RAU: 350 MHz transmitting IF signal 140 MHz receiving IF signal DC power supply 4/1555-CSH /1-V1 Uen B

104 MINI-LINK TN R3 ETSI Demodulator Radio Communication Channel (RCC) signal as an Amplitude Shift Keying (ASK) signal. In addition to the above, the cable interface includes an over voltage protection circuit. The received 140 MHz signal is AGC amplified and filtered prior to conversion to I/Q baseband signals. The baseband signals are pulse shaped in a Nyqvist filter and A/D converted before being demodulated Radio Frame Demultiplexer On the receiving side the received composite data stream is demultiplexed and FEC corrected. The frame alignment function searches and locks the receiver to the frame alignment bit patterns in the received data stream. Descrambling and FEC Decoding Error correction is accomplished using FEC parity bits in combination with a data quality measurement from the Demodulator. The descrambler transforms the signal to its original state enabling the Demultiplexer to properly distribute the received information to its destinations. Demultiplexing Demultiplexing is performed according to the used frame format. The Demultiplexer generates a frame fault alarm if frame synchronization is lost. The number of errored bits in the traffic data stream is measured using parity bits. These are used for BER detection and performance monitoring. Stuffing control 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 DCC On the receiving side, elastic buffering and clock recovery is performed on the DCC. 98 4/1555-CSH /1-V1 Uen B

105 Access Termination Unit (ATU) HCC The Hop Communication Channel (HCC) is used for exchange of control and supervision information between near-end and far-end. 4/1555-CSH /1-V1 Uen B

106 60V RAU MINI-LINK TN R3 ETSI 5.3 ATU C ATU C offers 2x2 or 4x2 traffic capacity for transmission of PDH traffic. E1:4 E1:3 E1:2 E1:1 Power 24-60V O&M RL + DC - E1 O&M RL V DC RAU 8275 Figure 83 ATU C Functional Blocks This section describes the functions of ATU C based on the block diagram in Figure 84 on page 100. E1 E1 E1 E1 Line Interface Traffic Traffic DCC Radio Frame Multiplexer HCC Radio Frame Demultiplexer Modulator Demodulator Cable Interface RAU O&M RL Control and Supervision DCC HCC RCC External Power Supply V DC Power Secondary voltages Figure 84 Block diagram for ATU C Line Interface This block provides the 4 E1 line interfaces for connection of PDH traffic. It interfaces Radio Frame Multiplexer block by transmitting and receiving the traffic (nxe1) /1555-CSH /1-V1 Uen B

107 Access Termination Unit (ATU) Control and Supervision Power This block handles system control and supervision. Its main functions are to collect alarms, control settings and tests. For the traffic over the hop it handles BER collection and communicates with processor in the RAU through the RCC. Exchange of control and supervision data over the hop is made through the HCC. Local management of ATU C is done with MSM software. The external power supply, V DC, is connected to the unit. This block provides secondary voltages for the unit and a stable voltage for the RAU, distributed in the radio cable Radio Frame Multiplexer The Radio Frame Multiplexer handles multiplexing of different data types into one data stream, scrambling and FEC encoding. The following data types are multiplexed into the composite data stream to be 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 rate adaptation (stuffing). If no valid data is present at the input, an AIS signal is inserted at nominal data rate. This means that the data traffic across the hop is replaced with ones (1). DCC DCC comprises 2x64 kbit/s channels used for DCN communication over the hop. HCC The Hop Communication Channel (HCC) is used for exchange of control and supervision information between the near-end and far-end. 4/1555-CSH /1-V1 Uen B

108 MINI-LINK TN R3 ETSI Multiplexing The three different data types together with check bits and frame lock bits are sent in a composite data format defined by the frame format that is loaded into a Frame Format RAM. The 12 frame alignment signal bits are placed at the beginning of the frame. Stuffing bits are inserted into the composite frame Modulator Cable Interface Scrambling and FEC Encoding The synchronous scrambler has a length of and is synchronized each eighth frame (super frame). The FEC bits are inserted according to the frame format and calculated using an interleaving scheme. The composite data stream from the Radio Frame Multiplexer is modulated, D/A converted and pulse shaped in a Nyqvist filter to optimize transmit spectrum. C-QPSK (Constant envelope offset Qaudrature Phase Shift Keying), an offset QPSK modulating technique, is used. It has a high spectrum efficiency compared to other constant envelope schemes. 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 a 490 MHz signal. The following signals are frequency multiplexed in the Cable Interface for further distribution through a coaxial cable to the outdoor RAU: 350 MHz transmitting IF signal 140 MHz receiving IF signal DC power supply Demodulator Radio Communication Channel (RCC) signal as an Amplitude Shift Keying (ASK) signal In addition to the above, the cable interface includes an over voltage protection circuit. The received 140 MHz signal is AGC amplified and filtered prior to conversion to I/Q baseband signals. The baseband signals are pulse shaped in a Nyqvist filter and A/D converted before being demodulated /1555-CSH /1-V1 Uen B

109 Access Termination Unit (ATU) Radio Frame Demultiplexer On the receiving side the received composite data stream is demultiplexed and FEC corrected. The frame alignment function searches and locks the receiver to the frame alignment bit patterns in the received data stream. Descrambling and FEC Decoding Error correction is accomplished using FEC parity bits in combination with a data quality measurement from the Demodulator. The descrambler transforms the signal to its original state enabling the Demultiplexer to properly distribute the received information to its destinations. Demultiplexing Demultiplexing is performed according to the used frame format. The Demultiplexer generates a frame fault alarm if frame synchronization is lost. The number of bits with errors in the traffic data stream is measured using parity bits. These are used for BER detection and performance monitoring. Stuffing control 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 DCC On the receiving side, elastic buffering and clock recovery is performed on the DCC. HCC The Hop Communication Channel (HCC) is used for exchange of control and supervision information between near-end and far-end. 4/1555-CSH /1-V1 Uen B

110 MINI-LINK TN R3 ETSI 104 4/1555-CSH /1-V1 Uen B

111 Management 6 Management The management functionality described in this section can be accessed from the management tools and interfaces as described in Section 6.8 on page 119. 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 replaceable hardware unit. Faults that cannot be mapped to one replaceable unit result in a fault 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 and RAU. The control system will generally try to repair software faults by performing warm restarts on a given plug-in unit or on the whole NE Alarm Handling MINI-LINK TN R3 uses SNMP traps to report alarms to MINI-LINK Manager or any other SNMP based management system. To enable a management system 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. Both these can be accessed by the management system using SNMP or from the EEM. The alarm status of specific managed objects can also be read. In general, alarms are correlated to prevent alarm flooding. This is especially important for high capacity links like STM-1 where a defect on the physical layer 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 these higher layers. Alarm notifications can be enabled/disabled for an entire NE, for an individual plug-in unit and for individual interfaces. Disabling alarm notification means that no new alarms or event notifications are sent to the management system. Alarm and event notifications are sent as SNMP v2c/v3 traps with a format according to Ericsson s Alarm IRP SNMP solution set version 1.2. The following fields are included in such a notification: 4/1555-CSH /1-V1 Uen B

112 MINI-LINK TN R3 ETSI Notification identifier: uniquely identifies each notification. Alarm identifier: only applicable for alarms, identifies all alarm notifications that 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/1A forane1onthenpu. Event time: time when alarm/event was generated. Event type: X.73x compliant alarm/event type like communications alarm and equipment alarm. Probable cause: M.3100 and X.733 compliant probable cause, for example Loss Of Signal (LOS). Perceived severity: X.733 compliant severity, for example critical or warning. Specific problem: free text string detailing the probable cause. The system can also be configured to send SNMP v1 traps. These traps are translated 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 Loops Loops can be used to verify that the transmission system is working properly or they can be used to locate a faulty unit or interface. The following loops are available on all units that carry traffic. Connection Loop This loop can be initiated for an E1. The traffic connection is looped in the TDM bus back to its origin, see Figure 85 on page 107. If an E1 interface is traffic routed an AIS is sent to the other interface in the traffic routing. A Connection Loop can be used in combination with a BERT in another NE to test a network connection including the termination plug-in unit, in case a Local Loop cannot be used due to the lack of a traffic routing. The following loops are available on units with a line interface (MS/RS, E3, E2 and E1) /1555-CSH /1-V1 Uen B

113 Management Line Loop Local Loop Loops an incoming line signal back to its origin. The loop is done in the plug-in unit, close to the line interface, see Figure 85 on page 107. An AIS is sent to the TDM bus. ALineLoopincombinationwithaBERTinanadjacentNEis used to test the transmission link between the two NEs. In the MMU2 E/F STM-1 the traffic signal that shall be transmitted is looped back just after base-band interface. Loops a line signal received from the TDM bus back to its origin, see Figure 85 on page 107. An AIS is sent to the line interface. A Local Loop in combination with a BERT in another NE can be used to test a connection as far as possible in the looped NE. In the MMU2 E/F a Local Loop at the far end loops back the STM-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 is done in the plug-in unit close to the TDM bus, where a group of E1s in the traffic connection is looped back to its origin, Figure85onpage107. An Rx Loop can be used on the far-end MMU to verify the communication over the radio path, see Figure 86 on page 108. In the MMU2 E/F the RX Loop applies to the wayside E1 traffic. * Only MMU Rx Loop Plug-in Unit* nxe1 AIS Connection Loop TDM Bus nxe1 nxe1 Local Loop Plug-in Unit Line Loop Plug-in Unit AIS AIS 7470 Figure 85 Loops 4/1555-CSH /1-V1 Uen B

114 MINI-LINK TN R3 ETSI The following loops on the near-end Radio Terminal are supported in order to find out if the MMU or RAU is faulty. IF Loop RF Loop In the MMU the traffic signal to be transmitted is, after being modulated, mixed with the frequency of a local oscillator and looped back for demodulation (on the receiving side). In the RAU a fraction of the RF signal transmitted is shifted in frequency and looped back to the receiving side. IF Loop RF Loop Rx Loop MMU RAU RAU MMU Near-end Far-end Note: For MMU2 E/F, also a Local Loop is available at the Far-end MMU. Figure 86 Radio Terminal loops 9971 The AAU supports a Loop Back function described in Section on page User Input/Output The NPU1 B provides three User Input and three User Output ports. The NPU3 provides two User Output ports. The User Input ports can be used to connect user alarms to the MINI-LINK management system. Applications like fire alarms, burglar alarms and low power indicator are easily implemented using these input ports. The User Input ports can be configured to be normally open or normally closed. User Output ports can be used to export summary alarms of the accumulated severity in the NE to other equipment s supervision system. The User Output ports can be controlled by the operator or triggered by one or several alarm severities. The setup of the User Input/Output is done in the EEM /1555-CSH /1-V1 Uen B

115 Management 6.2 Configuration Management The configuration can be managed locally and from the O&M center provided that 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 and protection 6.3 Software Management Software can be upgraded both locally and remotely. Software upgrade utilizes a local or remote FTP server to distribute the software to the NE. An FTP server is provided on the MINI-LINK Service Software CD used when installing software on site. The MINI-LINK TN R3 system software consists of different software modules for different applications. All traffic continues while the software is being loaded. During the execution of the software download a progress indication is provided in the user interface. When the download is completed, the new software and the previous software version are stored on the unit. Performing a warm restart of the NE activates the new software version. A warm restart only affects the control system. This restart can be performed immediately or scheduled at a later time. The restart, depending on the new functionality, may influence the traffic. When the warm restart with the new software is completed, the NE will wait for a Commit command from the management system. When Commit is received, the software upgrade process is completed. The previous software revision remains stored on the unit in case a rollback is required. This may be the case if something goes wrong during the software upgrade 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 can be automatically upgraded. 4/1555-CSH /1-V1 Uen B

116 MINI-LINK TN R3 ETSI 6.4 License Management License Key Files (LKF) can be installed both locally and remotely. License installation utilizes a local or remote FTP server to distribute the LKF to the NE. An FTP server is provided on the MINI-LINK Service Software CD used when installing software on site. The LKF is bound to a fingerprint which is a unique ID of a RMM, and will only function when installed on the correct RMM. Once installed, the NE features that is comprised within that LKF is allowed to be used. Multiple LKF can be used simultaneously on one NE, as long as they come from separate license generators. (Multiple license generators are a future system solution.) The NE has a license inventory view. An attempt to configure a function without a suitable LKF installed causes an error and the service will be unavailable until the file is installed. The error is sent as a standard event message to the management software. For migration, the error is reduced to a warning when introducing licensing, and the configuration still allowed. New SW versions will introduce the locking. Since the licenses are critical to secure the desired operation of the NE, a grace period (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 sufficient time 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 RMM to another. Commercial solutions exists /1555-CSH /1-V1 Uen B

117 Management 6.5 Performance Management General MINI-LINK TN R3 supports performance management according to ITU-T recommendation 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 24 hours 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 listed below: Performance counters for Ethernet traffic are described in Section on page 33. Performance data for the Radio Terminal is described in Section 4.8 on page 92. Performance data is stored in a volatile memory, so that a restart will lose all gathered data Bit Error Testing Each NE has a built-in Bit Error Ratio Tester (BERT) in all plug-in units carrying traffic. The BERT is used for measuring performance on E1 interfaces according to ITU standard O.151. A Pseudo Random Bit Sequence (PRBS) with a test pattern is sent through the selected interface. As with loop tests, bit error testing may be used for system verification or for fault location. 4/1555-CSH /1-V1 Uen B

118 MINI-LINK TN R3 ETSI NE or External equipment Plug-in Unit BERT E1 TDM Bus Figure 87 BERT in combination with an external loop 6668 The BERT is started and stopped by the operator and the bit error rate as a function of the elapsed time is the test result. The test can be started and stopped 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 /1555-CSH /1-V1 Uen B

119 Management 6.6 Security Management All management access to the MINI-LINK TN R3 system is protected by a user name 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 be changed 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. A default password is used for the local USB connection. For SNMP v3 access the regular user name and password protection is used. In addition to this the User-based Security Model (USM) and View-based Access Model (VACM) are supported. This means that additional users and passwords might be defined by external SNMP v3 managers. The security level is authentication/no privacy where MD5 is used as hash algorithm for authentication. For SNMP v1/v2c access the regular user name and password protection does not apply. Instead a community based access protection is used. As default, a public and a private community are configured. The public community enables default read-access and the private community provides read and write access to MIB-II system information. These privileges 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 regular user name and password protection. The telnet port can be disabled from the EEM. 4/1555-CSH /1-V1 Uen B

120 PFU /NPU NPU1 B LTU 16x2 LTU 155e/o SMU2 MMU2 B 4-34 LTU 155e MINI-LINK TN R3 ETSI 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 DCN implementation, covering the different MINI-LINK product families IP Services The following standard external IP network services are supported: All clocks, used for example for time stamping alarms and events, can be synchronized with a Network Time Protocol (NTP) server. File Transfer Protocol (FTP) is used as a file transfer mechanism for software 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 IP addresses in the DCN. The NE has a DHCP relay agent for serving other equipment on the site LAN. MINI-LINK TN 08/FAU2 PFU3 FAU2 NTP 00/PFU3 01/PFU3 DCN FTP Site LAN DNS LCT DHCP 7853 Figure 88 IP services 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 different alternatives to connect and transport DCN traffic are supported. This diversity of DCN interfaces provides the operator with a variety of options when deploying a DCN. Figure 89 on page 115 illustrates the different options, including ways of connecting to the equipment for DCN configuration /1555-CSH /1-V1 Uen B

121 Management DCC R /DCC M Structured/Unstructured E1 nx64 kbit/s 2xE0 DCC Radio Terminal PPP Router 10/100BASE-T USB 8360 Figure 89 DCN interfaces DCN in SDH The internal IP traffic is transported on nx64 kbit/s channels on the TDM bus in the backplane. The internal channels are automatically established at power up RSOH 4 AU Pointers Payload + RFCOH MSOH Figure 90 Frame 4665 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 the RFCOH). 192 kbit/s channel available on line side and radio side by using EOC or DDC bites of the Regenerator Section Overhead Frame (RSOH) of the SDH Frame. 4/1555-CSH /1-V1 Uen B

122 MINI-LINK TN R3 ETSI DCCr/DCCm The DCCr/DCCm overhead sections in the STM-1 frame can be used to transport DCN traffic. A PPP connection is established over the overhead segments between two end points. The default bandwidth is automatically established to DCCr=192 kbit/s and DCCm=192 kbit/s. DCCm is configurable to 384 kbit/s and 576 kbit/s. The PPP connection in the overhead segments is implemented as PPP over bit synchronous HDLC. Any 3rd party equipment that complies with this and the channel bandwidth segmentation can interoperate with MINI-LINK TN. Typically the DCCr is used to connect MINI-LINK TN R3 to MINI-LINK HC over an STM-1 connection. DCCm can be used to connect MINI-LINK TN R3 to MINI-LINK TN R3 over an STM-1 connection. Please note that for this connection there can be no multiplexer between the two MINI-LINK TN R3 NEs Structured/Unstructured E1 MINI-LINK TN R3 can use up to two of its connected E1s for transport of IP DCN. The following options are available: Dedicated E1 for DCN A structured or unstructured E1 can be dedicated for DCN. For the structured E1, nx64 kbit/s timeslots can be configured for DCN transport. The remaining timeslots are unused, that is cannot be used to transport traffic. For the unstructured E1, the entire 2 Mbit/s is used for DCN transport nx64 kbit/s xE0 E1 with traffic pass-through In a structured E1 used for traffic, nx64 kbit/s timeslots can be used for DCN transport. The DCN is inserted into the nx64 kbit/s timeslots internally in the NE. The timeslots used for traffic is cross-connected in normal manner through the NE. nx64 kbit/s timeslots can be used for IP DCN as described in Section on page 116. A PPP/E0 connection can be established to an external device from the SMU DCC Radio Terminal Each Radio Terminal provides a DCC of nx64 Kbits, where 2 n 9 depending on traffic capacity and modulation, transported in the radio frame overhead /1555-CSH /1-V1 Uen B

123 Management /100BASE-T USB 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 E with SAU IP(EX). The USB interface is used for LCT connection using a local IP address IP Addressing MINI-LINK TN R3 supports both numbered and unnumbered IP addresses. Numbered IP addresses are used for the Ethernet interface and IP interfaces configured as ABR. All other IP interfaces should be set up with unnumbered IP addresses. The IP interfaces with unnumbered IP address inherit the characteristics of the Ethernet interface. The use of unnumbered interfaces has several advantages: The use of IP addresses is limited. Using numbered interfaces for the PPP links would normally require using one IP subnet with two addresses for each radio hop. For a large aggregation site, this would imply a lot of addresses. The planning of the IP addresses is simplified. The amount of configuration is reduced because only one IP address is configured upon installation. Improved performance and smaller routing tables since the unnumbered PPP connections are not distributed by OSPF IP Router The IP router supports the following routing mechanisms: Open Short Path First (OSPF), which is normally used for routers within the MINI-LINK domain. Static routing There are two different ways to configure the IP router. The idea is that the most common configurations are done using the EEM. When complex router configuration and troubleshooting is required, a Command Line Interface (CLI) is used, see Section on page /1555-CSH /1-V1 Uen B

124 MINI-LINK TN R3 ETSI 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 split in two parts. Link summarization is supported, which is used in the ABR to minimize the routing information distributed to the backbone and/or other areas /1555-CSH /1-V1 Uen B

125 PFU3 FAU2 PFU /NPU NPU1 B LTU 16x2 LTU 155e/o SMU2 MMU2 B 4-34 LTU 155e Management 6.8 Management Tools and Interfaces This section gives a brief overview of the management tools and interfaces used for MINI-LINK TN R3. ServiceOn Microwave Mobile Network OSS/NMS SNMP MINI-LINK TN SNMP SNMP 01/PFU3 08/FAU2 00/PFU3 DCN MINI-LINK BAS Site LAN MINI-LINK HC MINI-LINK E LCT Figure 91 Management tools and interfaces Element Management The element management function provides tools for on site installation, configuration management, fault management, performance management and 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 is accessed 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 as online help and in the MINI-LINK TN Operation Manual. 4/1555-CSH /1-V1 Uen B

126 MINI-LINK TN R3 ETSI ServiceOn Microwave MINI-LINK TN R3 is managed remotely using the ServiceOn Microwave platform. ServiceOn Microwave provides functions such as FM, CM, AM, PM and SM based on the recommendations from Open Systems Interconnect (OSI) model. The CM functionality is either embedded or provided using dedicated Local Managers and Element Managers. ServiceOn Microwave can also be used 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 whole network. Network elements can be managed on an individual basis, providing the operator with remote access to several network elements, one by one. ServiceOn Microwave supports a real time window reporting alarms and events from the managed network elements. It is possible to filter alarms on the basis of assigned resources and alarm filtering criteria SNMP Each NE provides an SNMP agent enabling easy integration with any SNMP based management system. The SNMP agent can be configured to support SNMP v1/v2c/v3 for get and set operations. SNMP v3 is default. The SNMP agent sends SNMP v1, SNMP v2c and SNMP v3 traps. The system is built on standard MIBs as well as some private MIBs 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 is accessed from a Command Prompt window using telnet. The CLI functions are described in the online Help and the MINI-LINK TN Operation Manual /1555-CSH /1-V1 Uen B

127 Management Figure 92 CLI 4/1555-CSH /1-V1 Uen B