Technical_Description_MINI-LINK_TN_ETSI.pdf

Technical Description MINI-LINK TN ETSI DESCRIPTION 12/221 02-CSH 109 32/1-V1 Uen N Copyright © Ericsson AB 2008–2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Contents Contents 1 Introduction 1 1.1 General 1 1.2 Revision Information 2 2 System Overview 4 2.1 Introduction 4 2.2 Indoor Part with Subrack 6 2.3 Outdoor Part 8 3 Basic Node 10 3.1 System Architecture 10 3.2 Access Module Magazine (AMM) 12 3.3 Node Processor Unit (NPU) 20 3.4 Service Access Unit (SAU) 28 3.5 E1 Interfaces 30 3.6 SDH Traffic 33 3.7 Ethernet Traffic 39 3.8 Ethernet Interface Unit (ETU) 52 3.9 ATM Aggregation 57 3.10 Traffic Routing 63 3.11 Protection Mechanisms 65 3.12 Synchronization 74 3.13 Equipment Handling 78 3.14 MINI-LINK E Co-siting 80 4 Radio Link 81 4.1 Overview 81 4.2 Modem Unit (MMU) 83 4.3 Hybrid Radio Link 101 4.4 Hitless Adaptive Modulation 102 4.5 Radio Unit (RAU) 104 4.6 Antennas 112 4.7 1+1 Protection 116 4.8 Cross Polarization Interference Canceller (XPIC) 121 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Technical Description 4.9 Transmit Power Control 130 4.10 Performance Management 132 5 Management 132 5.1 Fault Management 133 5.2 Configuration Management 139 5.3 Performance Management 139 5.4 Security Management 142 5.5 License Management 143 5.6 Software Management 144 5.7 Data Communication Network (DCN) 144 5.8 Management Tools and Interfaces 150 6 Accessories 154 6.1 Interface Connection Field (ICF) 154 6.2 PSU DC/DC Kit 157 6.3 Small Form Factor Pluggable 159 6.4 Optical splitter/combiner 159 6.5 DCN Site LAN Switch 160 6.6 MPH for MINI-LINK TN 161 6.7 TMR 9302 162 6.8 Engineering Order Wire 163 Glossary 165 Reference List 171 Index 173 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Introduction 1 Introduction 1.1 General MINI-LINK is the world’s most deployed microwave transmission system. The MINI-LINK TN R4 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. 15 GHz 15 GH zHG 51 z 15 GH z 15 GHz 1 G5 zH R POWE R POWE RADIO CABLE ALARM RADIO CABLE NT ALIGNME ALARM NT ALIGNME RADIO CABLE ALARM POWE R ALIGNME NT 15 GH z 15 GHz R POWE RADIO CABLE ALARM NT ALIGNME 08/FAU2 PFU3 FAU2 LTU3 12 1 E1/DS1 E1/DS1 07/NPU E1/DS1 06 01/PFU3 NPU3 05 MMU2 F 155 PFU3 04 MMU2 E 155 03 00/PFU3 MMU2 E 155 02 MMU2 E 155 9716 Figure 1 A MINI-LINK TN R4 Configuration 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 1 Technical Description 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 soft key is required to enable a specific function, see MINI-LINK TN Soft Keys, Reference [6]. 1.2 Revision Information This document is updated due to the introduction of MINI-LINK TN R4. Information about the following products and accessories is new or updated in TN 4.0: • AMM 2p B, AMM 6p C/D and AMM 20p B • NPU3 B • ETU3 • SAU3 • LTU 32/1 • RAU • MPH • 1+1 SDH SNCP • TMR 9302 • SXU3 B • Ethernet traffic • ATM Aggregation updated • General document improvements Information about the following products and accessories is new or updated in TN 4.1: • 2 AMM 1p 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Introduction • Compact Node • MMU2 CS • MMU2 D Information about the following products and accessories is new or updated in TN 4.1 FP: • MMU2 H Information about the following products and accessories is new or updated in TN 4.2: • MMU2 H: Hitless Adaptive Modulation • Link Aggregation Group (LAG) • MMU2 CS 4/E1 Information about the following products and accessories is new or updated in TN 4.2 FP: • MMU2 H and MMU2 D: L1 Radio Link Bonding • MMU2 H: New traffic capacities • ETU2 B • NPU: E1 as output sync • MMU2 D/MMU2 H: Radio Link RF as sync signal • NPU3 (B): Packet Aging Information about the following products and accessories is new or updated in TN 4.3: • NPU1 C • MMU2 H: New traffic capacities • Quality of Service (QoS) Support • Jumbo Frames • Ethernet Link Operation and Maintenance (O&M) 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 3 Technical Description 2 System Overview 2.1 Introduction This section gives a brief introduction to the system and its components. Outdoor part with Antenna and RAU Indoor part with AMM 15 GHz 15 GHz NPU3 zHG 51 02 02 03 03 MMU2 E 155 1 G5 zH PFU3 08/FAU2 FAU2 LTU3 12 1 E1/DS1 E1/DS1 07/NPU E1/DS1 06 01/PFU3 NPU3 05 MMU2 F 155 15 GHz PFU3 04 02 03 00/PFU3 15 GHz MMU2 E 155 9383 Figure 2 Outdoor and Indoor Parts A MINI-LINK TN R4 Network Element (NE) can, from a hardware and installation point of view, be divided into two parts: • Indoor part see Section 2.2 on page 6. • Outdoor part, see Section 2.3 on page 8. An NE with a subrack can from a functional and configuration point of view be divided into the following parts: 4 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 System Overview Basic Node 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 site LAN. ATM aggregation is also supported. Finally, it includes indoor mechanical housing, power distribution and cooling. For more information, see Section 3 on page 10. Radio Terminals A Radio Terminal provides microwave transmission from 4 to 325 Mbps, operating within the 6 to 38 GHz frequency bands, utilizing C-QPSK and 16, 64, 128 QAM modulation schemes. It can be configured as unprotected (1+0) or protected (1+1) and supports Hitless Adaptive Modulation (MMU2 H). For more information, see Section 4 on page 80. Network Element Radio Terminals External Equipment Basic Node 6731 Figure 3 Basic Node and Radio Terminals The management features and tools are described in Section 5 on page 132. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 5 Technical Description 2.2 Indoor Part with Subrack AMM 1p NPU3 03 MMU2 E 155 02 08/FAU2 FAU2 03 PFU3 LTU3 12 1 E1/DS1 E1/DS1 07/NPU E1/DS1 02 01/PFU3 NPU3 06 AMM 2p B 05 MMU2 F 155 PFU3 02 03 00/PFU3 04 MMU2 E 155 NPU1 B LTU 155e/o LTU 16x2 MMU2 B 4-34 AMM 6p D 08/FAU2 PFU3 FAU2 E1/DS1 E1/DS1 07/NPU E1/DS1 06 01/PFU3 NPU3 PFU1 LTU3 12 1 PFU3 05 MMU2 F 155 04 02 03 00/PFU3 MMU2 E 155 AMM 6p C AMM 20p B 11627 Figure 4 Subracks The AMM is a subrack. 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 subrack. The subrack 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 10 and Section 4 on page 80. Access Module Magazine (AMM) The AMM houses the plug-in units and provides backplane interconnection of traffic, power and control signals. 6 Node Processor Unit (NPU) The NPU handles the system’s control functions. It also provides traffic and management interfaces. Line Termination Unit (LTU) The LTU provides PDH or SDH traffic interfaces. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 System Overview Modem Unit (MMU) The MMU constitutes the indoor part of a Radio Terminal. It determines the traffic capacity and modulation scheme. Ethernet Interface Unit (ETU) The ETU provides Ethernet traffic interfaces. ATM Aggregation Unit (AAU) The AAU provides ATM aggregation of traffic on E1 links. Switch Multiplexer Unit (SMU) The SMU provides traffic and DCN interfaces for MINI LINK E equipment. Service Access Unit (SAU) The SAU3 provides additional DCN capabilities. SDH Cross connect Unit (SXU) The SXU provides mapping of Ethernet, PDH and SDH traffic to and from STM-1 frames. Power Filter Unit (PFU) The PFU filters the external power and distributes the internal power to the plug-in units via the backplane. Fan Unit (FAU) The FAU provides cooling for the indoor part. The indoor part also includes cables and installation accessories. The interconnection between the outdoor part (Radio Units and antennas) and the indoor part is one coaxial cable per MMU carrying full duplex traffic, DC supply voltage, as well as management data. 2.2.1 Compact Node A Compact Node is a basic stand-alone configuration consisting of one AMM 1p and one MMU2 CS. The MMU2 CS includes functionality that is normally provided by an NPU, allowing it to work as a single board in the AMM 1p. The Compact Node is suitable as a far-end node in a MINI-LINK TN network and can be connected directly to an RBS or to external equipment. It can be installed in 19" or metric racks, in an MPH or on a wall. Furthermore, a hop can be set up between two sites, each consisting of one RAU, one antenna, and one Compact Node. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 7 Technical Description 11619 Figure 5 2.3 Compact Node 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.5 on page 104. The antennas are described in Section 4.6 on page 112. 8 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 System Overview 15 GHz 15 GHz ALARM POWER ALIGNMENT 15 GHz 15 GHz RADIO CABLE RAD CAB IO LE ALARM POWE R ALIG NME NT 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 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 9 Technical Description 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 subrack backplane. The buses are used for traffic handling, system control and power distribution. Plug-in Unit BPI Plug-in Unit Backplane TDM High Speed PCI SPI Power Power Filter Unit Node Processor Unit 10065 Figure 7 3.1.1 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 kbps for DCN channels. The traffic connections on the TDM bus are unstructured with independent timing. The bus has a switching capacity of 820 Mbps. It is redundant for additional protection against hardware failures. 10 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.1.2 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 3.1.3 SPI Bus The Serial Peripheral Interface (SPI) is a low speed synchronous serial interface bus used for: 3.1.4 • 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. The internal power supply is distributed via the Power bus to the other plug-in units. When using two PFUs in a subrack, the bus is redundant. 3.1.5 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. 3.1.6 High Speed Bus The High Speed Bus joins services to services (for example Ethernet over VCs dropped by ADM) and services to line interfaces (for example Ethernet over modem), see Figure 7. The high speed bus has dedicated Point-to-Point connections from the NPU1 C and NPU3 B to other PIUs. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 11 Technical Description 3.2 Access Module Magazine (AMM) The indoor part consists of an Access Module Magazine (AMM) with plug-in units. This section describes the subrack types and their associated cooling and power supply functions. 3.2.1 AMM 1p AMM 1p is suitable for end sites. 11619 Figure 8 AMM 1p The subrack has one full-height slot, which can be equipped with an MMU2 CS only. The configuration with one AMM 1p and one MMU2 CS is referred to as a Compact Node. AMM 1p can be fitted on a wall, in an MPH, or in a standard 19" or metric rack using a dedicated mounting set. 3.2.1.1 Power Supply AMM 1p is power supplied by –48 V DC or +24 V DC. One DC connector at the left side of the front panel is connected to the backplane. 3.2.1.2 Cooling The AMM 1p does not require any forced-air cooling. However, air filters should be present in the cabinet door. 3.2.2 AMM 2p B AMM 2p B is suitable for end site and repeater site applications. 12 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node FAU4 NPU3 LIFT LIFT 02 02 03 03 L LTU3 12/1 9972 Figure 9 AMM 2p B It has two half-height slots, one equipped with NPU3 or NPU3 B, the remaining half-height slot can be equipped with LTU, ETU, SAU or SXU. Two full-height slots can be equipped with MMU, LTU or ETU. AMM 2p B can be fitted in a standard 19" or metric rack or on a wall using a dedicated mounting set. The height of an AMM 2p B is 1U. 3.2.2.1 Power Supply 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. Redundant Power Supply –48 V DC or +24 V DC _ + NPU _ + 10066 Figure 10 3.2.2.2 Power Supply for AMM 2p B Cooling 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 subrack. FAU4 holds three internal fans. If the indoor location has other fan units, which provide sufficient cooling through the subrack, the FAU4 can be omitted. However, air filters should be present in the cabinet door. For details on cooling and temperature requirements, see Installing Indoor Equipment, Reference [2]. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 13 Technical Description Air out NPU3 02 02 03 03 MMU2 E 155 Air in 9715 Figure 11 Cooling Airflow in AMM 2p B The air enters at the right hand side of the subrack and exits at the left hand side of the subrack. 3.2.3 AMM 6p C/D AMM 6p C/D is suitable for medium-sized hub sites or prioritized small-sites with 1+1 protection. 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/NPU3 B, one or two PFU3 B and one FAU2, see Figure 12 and Figure 13. The remaining slots in AMM 6p C/D can be equipped with MMU, LTU, SAU, AAU, SXU, SMU or ETU. 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 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 C/D is 3U. PFU NPU 08/FAU2 PFU3 FAU2 LTU3 12 1 E1/DS1 E1/DS1 07/NPU 01/PFU3 E1/DS1 NPU3 06 MMU2 F 155 05 MMU2 F 155 PFU3 02 03 00/PFU3 04 MMU2 E 155 FAU 10067 Figure 12 14 AMM 6p C 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node PFU NPU PFU3 08/FAU2 FAU2 LTU3 12 1 E1/DS1 E1/DS1 07/NPU E1/DS1 06 01/PFU3 NPU3 05 MMU2 F 155 PFU3 02 03 00/PFU3 04 MMU2 E 155 FAU 10068 Figure 13 3.2.3.1 AMM 6p D Power Supply 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 B to the other units, via the power bus in the backplane of the subrack. The power system is made redundant using two PFU3 Bs, utilizing the redundant power bus. PFU _ External Power Supply + PFU3 B: –48V DC or +24V DC _ + 10069 Figure 14 Power Supply for AMM 6p C or D 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. 3.2.3.2 Cooling Forced air-cooling is always required and provided by FAU2, which holds two internal fans. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 15 Technical Description Air out PFU3 08/FAU2 FAU2 LTU3 12 1 E1/DS1 E1/DS1 07/NPU E1/DS1 06 01/PFU3 NPU3 05 MMU2 F 155 PFU3 04 02 03 00/PFU3 MMU2 E 155 Air in Figure 15 9707 Airflow in AMM 6p The air enters at the front on the right hand side of the subrack and exits at the rear on the left hand side of the subrack. 3.2.4 AMM 20p B The AMM 20p B 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 or NPU1 C and two half-height slots housing one or two PFU1. The remaining slots can be equipped with MMU, LTU, AAU, SMU and ETU. 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 subrack to enable neat handling of cables connected to the fronts of the plug-in units. An FAU1 is fitted on top of the subrack unless forced air-cooling is provided. An air guide plate is fitted right above the FAU1. AMM 20p B can be fitted in a standard 19" or metric rack. The subrack with FAU1, cable shelf and air guide plate has a total height of 10U. 16 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node Air Guide Plate FAU Power A -48V Alarm A Fault Alarm B Power B -48V FAN UNIT NPU B NPU18x2 LTU 155e/o LTU 16x2 MMU2 B 4-34 MMU2 B 4-34 MMU2 4-34 PFU Power PFU1 Cable Shelf NPU 10070 Figure 16 3.2.4.1 AMM 20p B 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 subrack. 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 6.2 on page 157. The ICF1 is not used in this installation alternative. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 17 Technical Description Power supply with ICF1 External Power Supply 48 V DC Power supply without ICF1 _ + _ _ + _ + External Power + _ Supply + 48 V DC _ + ICF1 FAU1 FAU1 PFU1 PFU1 10084 Figure 17 Power Supply for AMM 20p B PFU1 Fault Power Fan alarm BR Fan alarm 0V –48 V DC -48V DC 6709 Figure 18 PFU1 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 subrack backplane. 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. 3.2.4.2 Cooling Forced air-cooling is provided by FAU1, fitted directly above the subrack. The air enters through the cable shelf, flows directly past the plug-in units and exits at the top of the subrack through the air guide plate. 18 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node If the indoor location has other fan units, which provide sufficient cooling through the subrack, 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. Air Guide Plate Air out FAU1 AMM 20p B Cable Shelf Air in 10071 Figure 19 Side View of the Airflow in AMM 20p B Power A -48V Alarm A Fault Fan alarm A –48 V DC A Alarm B Power B -48V Power FAN UNIT Fan alarm B –48 V DC B 6710 Figure 20 FAU1 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 19 Technical Description 3.3 Node Processor Unit (NPU) The NPU implements the system’s control functions. One NPU is always required in the subrack. 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: 3.3.1 20 Overview NPU1 B Fits in an AMM 20p B. NPU1 C Fits in an AMM 20p B. NPU3 Fits in an AMM 2p B, AMM 6p C or AMM 6p D. NPU3 B Fits in an AMM 2p B, AMM 6p C or AMM 6p D. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node RMM Fault Power BR NPU1 B ERICSSON 10/100Base-T O&M E1:3A-3D O&M User I/O:1A-1I 2x(4xE1) User I/O F P O&M BR ERICSSON E1:2A-2D Not used 10/100BASE-T NPU1 C NPU1 B Console TR:7/LAN T:R6 OUT TR:5 IN OUT TR:4 IN TR:3A-3D TR:2A-2D NPU1 C User I/O:1A-1I O&M 10/100/1000BASE-T User I/O 2xSFP, 2x(4xE1) Electrical or optical NPU3 E1/DS1 10/100 Base -T TR:4A-4D/Use r Out:E -F 10/100 Base -T TR:3 LAN RMM F P NPU3 O&M 4xE1 + 2xUser Out O&M 2x(10/100BASE-T) NPU3 B E1/DS1 10/100/100 0BAS E-T NPU3 B 10/100/100 0BAS E-T F TR:4A-4D/ User Out:E-F TR:3 TR:2/LAN P RMM O&M 4xE1 + 2xUser Out 2x(10/100/1000BASE-T) O&M 12184 Figure 21 NPUs The following summarizes the common functions of the NPUs: • Traffic handling • System control and supervision • IP router for DCN handling • SNMP Master Agent 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 21 Technical Description • Ethernet interface for connection to a site LAN • Storage and administration of inventory and configuration data • USB interface for MINI-LINK Craft connection There are also some specific functions associated with each NPU type as summarized below. NPU1 B • 2x(4xE1) for traffic connections • Three User Input ports • Three User Output ports NPU1 C • 2x(4xE1) for traffic connections • Three User Input ports • Three User Output ports • Two Ethernet traffic ports • Ethernet switch • Two 1000BASE-TX/LX/ZX/SX Small Form Factor Pluggables (SFP) interfaces NPU3 • 1x(4xE1) for traffic connections • Two User Output ports • Ethernet traffic port NPU3 B • 1x(4xE1) for traffic connections • Two User Output ports • Ethernet traffic port • Ethernet switch 3.3.2 Functional Blocks This section describes the internal and external functions of the NPUs, based on the block diagrams in Figure 22, Figure 24 and Figure 25. 22 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node TDM Bus TDM PCI Bus PCI SPI Bus SPI Power Bus Node Processor Secondary voltages Power Line Interface 8xE1 Ethernet 10/100BASE-T DCN / Site LAN User I/O 3 User In 3 User Out O&M USB 10072 Figure 22 Block Diagram for NPU1 B High Speed Bus TDM Bus High Speed Ethernet Switch Ethernet TDM Line Interface PCI Bus SPI Bus Power Bus Node Processor PCI User I/O SPI Power 1x1000 BASE-X SFP Module 1x1000 BASE-X SFP Module 1x10/100/1000BASE-T Ethernet Traffic 1x10/100/1000BASE-T Ethernet Traffic / 10/100BASE-T 4xE1 DCN / Site LAN 4xE1 3xUser In 3xUser Out Secondary voltages O&M USB 12168 Figure 23 Block Diagram for NPU1 C 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 23 Technical Description User Output TDM Bus PCI Bus SPI Bus Power Bus TDM PCI Node Processor 4xE1 + 2xUser Out Ethernet 1x10/100BASE-T DCN / Site LAN 1x10/100BASE-T Ethernet Traffic O&M SPI Power Line Interface USB Secondary voltages 10073 Figure 24 24 Block Diagram for NPU3 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node High Speed Bus High Speed TDM Bus TDM PCI Bus Ethernet Switch Line Interface Node Processor PCI SPI Bus Ethernet 1x10/100/1000BASE-T Ethernet Traffic 1x10/100/1000BASE-T Ethernet Traffic / 10/100BASE-T DCN / Site LAN 4xE1 + 2xUser Out User Output SPI Power Bus Power Secondary voltages O&M USB 12185 Figure 25 3.3.2.1 Block Diagram for NPU3 B TDM This block interfaces the TDM bus by receiving and transmitting the traffic (nxE1) and DCN channels (nx64 kbps). The Node Processor communicates with the TDM block via the PCI block. 3.3.2.2 PCI This block interfaces the PCI bus used for control and supervision communication. The block communicates with the Node Processor, which handles control and supervision of the whole NE. 3.3.2.3 SPI This block interfaces the SPI bus used for equipment status communication. The block communicates with the Node Processor, which handles equipment status of the whole NE. Failure is indicated by LED’s on the front of the unit. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 25 Technical Description 3.3.2.4 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. 3.3.2.5 Node Processor The Node Processor is the central processor of the NE, responsible for the traffic and control functions listed in Section 3.3.1 on page 20. 3.3.2.6 High Speed This block provides Point-to-Point connections to other PIUs via the High Speed Bus. 3.3.2.7 Line Interface This block provides the E1 line interfaces for external connection. 3.3.2.8 Ethernet This block provides a 10/100BASE-T connection to site LAN for NPU1 B and NPU3, but for NPU3 it also provides a 10/100BASE-T traffic connection for Ethernet applications. The Ethernet traffic is mapped on N×E1, where N≤16, using one inverse multiplexer. For NPU1 C and NPU3 B this block provides two 10/100/1000BASE-T interfaces, one for Ethernet Traffic and one for Ethernet Traffic or 10/100BASE-T Ethernet site LAN. For NPU1 C this block also provides two 1000BASE-TX/LX/ZX/SX SFP interfaces, which can be either electrical or optical. The Ethernet traffic is a switched service from the Ethernet switch. See Section 3.7 on page 39 for more information on Ethernet traffic. 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 Section 6.8 on page 163. 3.3.2.9 Ethernet Switch This block provides the Ethernet switching to and from the high speed bus. The Ethernet switch supports both site LAN and VLAN switching. The switch is also hardware prepared for Provider mode. 26 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.3.2.10 O&M This block provides the MINI-LINK Craft connection to the NPU using a USB interface. The equipment is accessed using a local IP address. 3.3.2.11 User I/O This block handles the User In and User Out ports on NPU1 B and NPU1 C, and the User Out ports on NPU3 and NPU3 B, see Section 5.1.4 on page 138. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 27 Technical Description 3.4 Service Access Unit (SAU) The SAU3 provides additional DCN capabilities, and User Input and Output ports. 3.4.1 Overview The SAU3 is fitted in an AMM 2p, AMM 2p B and AMM 6p C/D. The main feature is to provide additional DCN capabilities. Protocols supported are PPP, tunneling via IP, a Transparent Service Channel (TSC) and a terminal server mode for MINI-LINK E access. All IP based services are terminated at the NPU where the routing is performed and site LAN-, line- and radio interfaces are made available. For more information on DCN, see MINI-LINK DCN Guidelines, Reference [5]. G.703/V.28/V.11 AUX:2 AUX 2 G.703/V.28 AUX:1A / User I/O:1B-1J SAU3 Fault SAU3 AUX 1 10038 Figure 26 SAU3 The following front interfaces are available on the SAU3: • AUX 1, one auxiliary interface, where the following interface types can be configured: 0 0 V.28 G.703 E0 (64 kbps) And the following ports are supported: 0 0 • 28 Six User In ports Three User Out ports AUX 2, one auxiliary interface, where the following interface types can be configured: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 0 0 0 3.4.2 V.11 V.28 G.703 E0 (64 kbps) Functional Description This section describes the functions of SAU3, based on the block diagrams in Figure 27. TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power AUX V.11, V.28, G.703 (E0) User In/Out 6 User In 3 User Out Secondary voltages 10039 Figure 27 3.4.2.1 Block Diagram for SAU3 AUX SAU3 provides two auxiliary interfaces for serial communication. The interfaces can work as a converter to and from IP traffic, and can be configured as terminal server or PPP. The auxiliary interface AUX 2 can also work as a Transparent Service Channel (TSC). The following interface types can be configured. • V.11, synchronous or asynchronous, 1.2 to 64 kbps • V.28, synchronous or asynchronous, 1.2 to 64 kbps • G.703 E0 (64 kbps) Note: SAU3 is the Controlling equipment in a G.703 contradirectional interface. See Figure 3 on page 5 in ITU-T G.703 (11/2001). 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 29 Technical Description 3.4.2.2 User In/Out Six User In ports are available for connection of user alarms, such as fire or burglar alarms, to be displayed in MINI-LINK management systems. The User In ports can be configured to be normally open or normally closed. Three User Out ports are available. The User Out ports are intended for control of remote user’s functions and can be controlled by alarm severity or an operator. 3.4.2.3 TDM This block interfaces the TDM bus by receiving and transmitting the DCN channels (1x64 kbps). 3.4.2.4 Control & Supervision The block handles alarms and configuration. 3.4.2.5 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 3.4.2.6 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. 3.5 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. The MINI-LINK TN uses the same connectors for all E1 Interfaces. 3.5.1 NPU NPU1 B and NPU1 C provides eight E1 interfaces, NPU3 and NPU3 B provides four E1 interfaces, see Section 3.3.1 on page 20. 3.5.2 SXU SXU3 B provides one 4×E1 interface, see Section 3.6.3 on page 36. 30 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.5.3 LTU 3.5.3.1 Overview The following LTUs with E1 interfaces are available: LTU 32/1 Fits in any subrack. The LTU 32/1 provides 32 additional E1 interfaces. LTU 16/1 Fits in any subrack. The LTU 16/1 provides 16 additional E1 interfaces. LTU3 12/1 Fits in an AMM 2p B, AMM 6p C or D and in an AMM 2p (as LTU 12/1 Kit, incl. washer). For sites where the four E1 interfaces on the NPU3 are insufficient, the LTU3 12/1 provides 12 additional E1 interfaces. LTU 32/1 E1/DS1 E1/DS1 Fault Power BR E1/DS1 E1/DS1 E1/DS1 TR:8A-8D TR:7A-7D TR:6A-6D TR:5A-6D TR:4A-4D E1/DS1 TR:3A-3D E1/DS1 TR:3A-3D E1/DS1 LTU 32/1 TR:3A-3D 8x(4xE1) Fault Power BR LTU 16/1 ERICSSON E1:4A-4D E1:3A-3D E1:2A-2D E1:1A-1D LTU 16/1 4x(4xE1) LTU3 12 1 E1/DS1 LTU3 12/1 E1/DS1 E1/DS1 3x(4xE1) 10040 Figure 28 LTUs with E1 Interfaces 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 31 Technical Description 3.5.3.2 Functional Blocks This section describes the internal and external functions of the LTUs with E1 interfaces, based on the block diagram in Figure 29. TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Line Interface 12xE1, 16xE1 or 32xE1 Secondary voltages 10033 Figure 29 3.5.3.2.1 Block Diagram for LTU 32/1, LTU 16/1 and LTU3 12/1 TDM This block interfaces the TDM bus by receiving and transmitting the traffic (nxE1). 3.5.3.2.2 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. 3.5.3.2.3 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 3.5.3.2.4 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 32 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node start and short circuit protection, filter function, low voltage protection, DC/DC converter and a pre-charge function. 3.5.3.2.5 Line Interface This block provides the E1 line interfaces for external connection. 3.6 SDH Traffic 3.6.1 Overview The SDH portfolio consists of the SDH modems MMU2 E/F 155 and the SDH termination units LTU 155 and SXU3 B. These modems and traffic termination units together support a variety of applications: • For a pure point-to-point SDH microwave connection the STM-1 can be connected directly to the front of the modem. • The LTU 155 Terminal Multiplexer terminates one STM-1 with 63xE1 (or 21xE1) mapped asynchronously into 63xVC-12 (or 21xVC-12) depending on the type of LTU 155. The E1s are available at the TDM bus for traffic routing to other plug-in units. See Section 3.6.2 on page 34. 0 0 0 0 • At aggregation nodes the LTU 155 acts as an interface between the optical domain and the microwave domain by providing an effective optical northbound interface using one STM-1 connection instead of nxE1 interfaces. In ring configurations two LTU 155s can be connected “back-to-back” to allow local add/drop of up to 63xE1.For ring configuration, see also SXU3 B. The LTU 155 is also used if all incoming SDH radio traffic on MMU2 E/F 155 shall be connected to the TDM bus as 63xE1s. The LTU B 155 acts as an interface towards 3G radio base stations for transmission of up to 21xE1 over channelized STM-1 interface. SXU3 B is an SDH Add-Drop Multiplexer that supports PDH over SDH and Ethernet over SDH, see Section 3.6.3 on page 36. 0 0 SXU3 B supports SDH microwave rings with up to 21×E1 add/drop in each node. SXU3 B can aggregate partially filled STM-1s into one full northbound STM-1. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 33 Technical Description 0 3.6.2 SXU3 B allows Ethernet to be mapped into VCs for transportation over one or multiple STM-1s. LTU 155 There are three versions of the LTU 155: LTU 155e Provides one electrical interface (G.703), mapping 63xE1. LTU 155e/o Provides one optical interface (short haul S-1.1) and one electrical interface (G.703), mapping 63xE1. Note: only one at a time. LTU B 155 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 subrack types. The STM-1 interface on LTU 155s can be equipment and line protected using MSP 1+1, see Section 3.11.3 on page 70. ERICSSON Fault Power BR LTU 155e RX EL. TX LTU 155e Electrical Caution Invisible Laser Radiation When Open Class 1 Laser Fault Power BR LTU 155e/o ERICSSON TX OPT. RX RX Optical EL. TX LTU 155e/o Electrical Invisible Caution Laser Radiation When Open Class 1 Laser ERICSSON Fault Power BR LTU B 155 TX OPT. RX RX Optical EL. TX LTU B 155 Electrical 8278 Figure 30 34 LTU 155 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.6.2.1 Functional Blocks This section describes the internal and external functions of the LTU 155, based on the block diagram in Figure 31. BPI (MSP 1+1) TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power VC-12 MS/RS VC-4 STM-1 SDH Equipment Clock Secondary voltages 6663 Figure 31 3.6.2.1.1 Block Diagram for LTU 155 TDM This block interfaces the TDM bus by receiving and transmitting the traffic (nxE1) and DCN channels (nx64 kbps). 3.6.2.1.2 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. The block holds a Device Processor (DP) running plug-in unit specific software. 3.6.2.1.3 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 35 Technical Description 3.6.2.1.4 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. 3.6.2.1.5 VC-12 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 1.1.1-1.1.3, 1.2.1-1.2.3 through 1.7.1-1.7.3. 3.6.2.1.6 MS/RS VC-4 This block maps the VC-12s to/from one VC-4 adding path overhead. The block provides the electrical and optical STM-1 line interfaces for external connection. 3.6.2.1.7 SDH Equipment Clock This block handles timing and synchronization. The LTU 155 utilizes the synchronization functions described in Section 3.12 on page 74. 3.6.3 SXU3 B SXU3 B is an SDH Add-Drop Multiplexer that supports PDH over SDH (mapping 21×E1 to VC-12s) and Ethernet over SDH (up to 600 Mbps). The SXU3 B fits in an AMM 2p B, AMM 6p C or AMM 6p D, and provides one 4×E1 interface on the front. 36 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node SXU3 B E1/DS1 Fault TR:1A-1D SXU3 B 4xE1 10048 Figure 32 3.6.3.1 SXU3 B Functional Blocks This section describes the internal and external functions of the SXU3 B, based on the block diagram in Figure 33. Higs Speed Bus Ethernet over SDH High Speed SDH ADM (Cross Connection) PDH over SDH TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Line Interface 4xE1 Secondary voltages 10049 Figure 33 Block Diagram for SXU3 B 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 37 Technical Description 3.6.3.1.1 TDM This block interfaces the TDM bus by receiving and transmitting the traffic (n×E1) and DCN channels (n×64 kbps). 3.6.3.1.2 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. The block holds a Device Processor (DP) running plug-in unit specific software. 3.6.3.1.3 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LEDs on the front of the unit. 3.6.3.1.4 PDH over SDH This block maps the 21×E1 to VC-12s. 3.6.3.1.5 Ethernet over SDH This block maps the Ethernet frames (up to about 600 Mbps) into Generic Framing Procedure (GFP) frames. These frames build up the Virtual Concatenation Groups (VCGs). One VCG is a multiple of VC-12s, VC-3s or VC-4s and there is a maximum of 7 VCGs. 3.6.3.1.6 SDH ADM (Cross Connection) This block terminates and structures 4×STM-1 signals via radio. The corresponding DCN channels are terminated. The VC-12s, VC-3s and VC-4s of the corresponding VCGs respectively and the VC-12s of the corresponding E1s can be cross connected with the VCs of the 4×STM-1 signals. 3.6.3.1.7 High Speed This block provides a Point-to-Point connection towards the SDH modems and the NPU3 B. 3.6.3.1.8 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. 38 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.7 Ethernet Traffic This section describes Ethernet traffic handling in MINI-LINK TN. 3.7.1 Ethernet over PDH The Ethernet traffic is transported between NEs in multiple E1s, over a single hop or through a network. Figure 34 shows an example of how the different units can be used in a network. 100BASE-T AMM 2p B NPU3 1 - 16xE1 AMM 6p C/D NPU3 B ETU2 B/ETU3 AMM 2p B NPU3 AMM 20p B NPU1 C ETU2 (B) Ethernet core network 1 - 48xE1 AMM 2p B NPU3 B ETU2 B/ETU3 AMM 6p C/D NPU3 B ETU2 B/ETU3 12164 Figure 34 Ethernet Traffic over PDH in a MINI-LINK TN R4 Network The bandwidth of each Ethernet connection is n×E1 per inverse multiplexer in the unit, where n≤48 for ETU2, ETU2 B, and ETU3 (with a maximum of 96×E1s in total), and n≤16 for NPU3. NPU3 has one inverse multiplexer while ETU2, ETU2 B, and ETU3 have six. Ethernet traffic is connected to the units using RJ-45 connectors with support for shielded cable. The Ethernet connections have auto-negotiation 10/100 Mbps 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 39 Technical Description 3.7.2 Ethernet over SDH The Ethernet traffic is transported between NEs in one or multiple STM-1 frames, over a single hop or through a network. Figure 35 shows an example of how the different units can be used in a network. 100BASE-T 1xSTM-1 AMM 2p B NPU3 B SXU3 B 1 - 4xSTM-1 AMM 6p C/D NPU3 B SXU3 B AMM 20p B AMM 2p B NPU3 B SXU3 B OMS 846/ 860/ 870 Core network AMM 6p C/D NPU3 B SXU3 B 10053 Figure 35 Ethernet Traffic over SDH in a MINI-LINK TN R4 Network The bandwidth of each Ethernet connection is up to four STM-1s for SXU3 B. The Ethernet traffic is switched from the NPU3 B over the high speed bus to the SXU3 B. The SXU3 B maps the Ethernet traffic to and from STM-1 frames. Ethernet traffic is connected to the units using RJ-45 connectors with support for shielded cable. The Ethernet connections have auto-negotiation 10/100/1000 Mbps speed, supports full/half duplex, and supports but are not limited to the following: 3.7.3 • IEEE 802.1Q VLAN • MAC address based VLAN • VLAN tag ID based frames • VLAN untagged frames • Frames with up to 2 VLAN tags • Frames with ICS tag Native Ethernet The Ethernet traffic is sent over a single hop or through a network. Native Ethernet traffic is sent over a dedicated physical link instead of being transported 40 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node over PDH or SDH. Native Ethernet enables more efficient use of bandwidth and maximizes Ethernet throughput since no PDH overhead is added. Overhead Comparison The overhead for Native Ethernet is only 0.5%, in comparison to 6.0% for Ethernet over PDH. Native Ethernet is sent over a Hybrid Radio Link and the capacity range from 0 Mbps to total link capacity. The functionality is supported by MMU2 D and MMU2 H in combination with NPU3 B in an AMM 2p B or AMM 6p C/D, or with NPU1 C in an AMM 20p B. Native Ethernet is supported by MMU2 H in XPIC mode as well. For information on Hybrid Radio Link, see Section 4.3 on page 101. 3.7.4 Ethernet Switch Functionality NPU1 C and NPU3 B have an Ethernet switch. The Ethernet switch capacity for the different NPUs are presented in Table 1. Table 1 Ethernet Switch Capacity NPU1 C Switch Capacity • 4×1000BASE-T switch ports to front panel • 20×1 Gbps switch ports to back plane • 24 Gbps switch capacity, full-duplex NPU3 B • 2×1000BASE-T switch ports to front panel • 7×1 Gbps switch ports to back plane • 9 Gbps switch capacity, full-duplex The switch is a managed VLAN switch (IEEE 802.1Q and IEEE 802.1D) and HW prepared for provider mode switching (IEEE 802.1ad). The switch also supports Jumbo frames, which minimizes overhead for certain traffic types by supporting Ethernet packets with size up to 9216 bytes. The Ethernet site LAN ports on NPU3 B and NPU1 C have interfaces that support auto-negotiation 10/100/1000 Mbps speed and full/half duplex. The interfaces are physical RJ-45 connectors. 3.7.4.1 Security NPU3 B and NPU1 C supports: • White lists - a source MAC address based white list can provide port access control at the network edge. • Storm protection - The switch includes filters to prevent broadcast and multicast storms. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 41 Technical Description • Port blocking - Prevent forwarding of frames from a given ingress port to one or more egress ports. • Frame admittance - It is possible to block or admit the following frame types at the network edge: 0 Q-Tagged (priority bits/VID set in Q-tag) 0 Priority tagged (only priority bits set in Q-tag) 0 Untagged (no Q-tag) Other/unrecognized frame types (for example S-tags) are discarded at the network edge. 3.7.4.2 • MAC address limiting per port. It is possible to limit the MAC address table per port to prevent external devices/networks to flood the customer network with MAC addresses. • Optional VLAN ID tagging per port. Ethernet Protection NPU3 B and NPU1 C supports Link Aggregation Group (LAG), which aggregates several external Ethernet links into one logical link and provides line protection. Note: Only switch ports that have no VLANs connected can be included in the LAG. If a link in a LAG fails, traffic is redirected from the faulty link to the remaining links in the LAG. The traffic takeover is done through graceful degradation and is performed without traffic interruption. However, the total link capacity is decreased and traffic with low priority may be discarded to ensure that traffic with high priority is sent. Network rerouting according to Rapid/Multiple Spanning Tree Protocol (RSTP/MSTP) is not triggered unless all physical links in an LAG fails. RSTP/MSTP activates a redundant link in case of link failure and protects the network from infinite loops. 3.7.5 Quality of Service Support This section describes the Quality of Service (QoS) support in MINI-LINK TN. An overview of the execution order for different QoS functions is illustrated in Figure 36. 42 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node CoS Classification & Tagging Policing Ingress Egress Tail dropping Color dropping Weighted Random Early Detection Aging Weighted Fair Queuing Strict Priority 12187 Figure 36 QoS Execution Order Frames can be dropped at the ingress or egress side by the different QoS functions described in this section. 3.7.5.1 Class of Service and Tagging The Class of Service (CoS) value for a frame is a representation of the end user services, such as voice and best effort data. The CoS value is set in the priority bits in the Ethernet header and is typically defined at the network edge. The priority bits are set based on whether the port is trusted or not. The following options are supported: • DSCP value in IP header • Reuse Priority Code Point (PCP) value in customer Q-tag • Default value (based on port number) • EXP bits in MPLS header The defined CoS value is stored in the PCP value in the Q-tag in the Ethernet header and is used throughout the network. All site LAN/WAN Ethernet ports can be configured with 1-8 traffic classes, where 8 traffic classes are default. The CoS priority information is used to map the Ethernet frames into the 1-8 traffic classes (TCs). The mapping can be done according to either IEEE802.1D-2004, IEEE802.1Q-2005 or custom. Frames with no CoS information is mapped to the default traffic class (TC0). There are individual queues for each CoS. The Ethernet frames in the egress queues are either scheduled according to a strict priority scheme or according 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 43 Technical Description to Weighted Fair Queuing (WFQ). See Section 3.7.5.7 on page 46 for more information on strict priority, and Section 3.7.5.8 on page 47 for information on WFQ. 3.7.5.2 Policing and Color Marking Policing measures traffic stream characteristics on the network ingress side. The characteristics are compared to a bandwidth profile consisting of a set of parameters related to a committed characteristic and an excess characteristic. Color marking marks Ethernet frames with different colors, depending on bandwidth profile compliance. The color information is stored in the PCP value in the Q-tag in the Ethernet header. Color marking decreases the number of applied priorities in the network. If a stream does not comply with the excess parameters, frames are marked red and dropped at the ingress. If a stream complies with excess parameters, but not with committed parameters, frames are marked yellow (Y). If the traffic stream complies with the committed set of parameters the frames are marked with green (G) and receive QoS guarantees through the network. The network should be configured to keep green frames even if network congestion occurs. Color marking is configured in MINI-LINK Craft by specifying the number of network priorities and number of priorities with color dropping. The relation between priorities and number of priorities with color dropping is fixed. The four available PCP selection schemes are listed below. 8p0d 8 priorities, 0 priorities with color dropping 7p1d 7 priorities, 1 priority with color dropping 6p2d 6 priorities, 2 priorities with color dropping 5p3d 5 priorities, 3 priorities with color dropping Note: Color dropping is not applicable for the two highest priorities, 6 and 7. The PCP encoding according to priority and color for the four PCP selection schemes is shown in Table 2. PCP decoding is illustrated in Table 3. Table 2 PCP Encoding 7G 7Y 6G 6Y 5G 5Y 4G 4Y 3G 3Y 2G 2Y 1G 1Y 0G 0Y 8p0d 7 7 6 6 5 5 4 4 3 3 2 2 1 1 0 0 7p1d 7 7 6 6 5 4 5 4 3 3 2 2 1 1 0 0 6p2d 7 7 6 6 5 4 5 4 3 2 3 2 1 1 0 0 5p3d 7 7 6 6 5 4 5 4 3 2 3 2 1 0 1 0 Priority, drop eligible (1) PCP (1) Default configuration. 44 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node Table 3 PCP Decoding 7 6 5 4 3 2 1 0 8p0d 7 6 5 4 3 2 1 0 7p1d 7 6 4 4Y 3 2 1 0 6p2d 7 6 4 4Y 2 2Y 1 0 5p3d 7 6 4 4Y 2 2Y 0 0Y PCP (2) Priority, drop (1) eligible (1) Yellow frames are marked with Y, green frames are unmarked. (2) Default configuration. Example: 7p1d If the 7p1d selection scheme is used, 5Y and 4Y frames are marked with PCP 4, and 5G and 4G frames are marked with PCP 5, see Table 2. Frames marked with PCP 4 and 5 receive the same priority (4) but with different colors, see Table 3. In case of congestion, PCP 4 frames (yellow) are dropped before PCP 5 frames (green). 3.7.5.3 Tail Dropping All new packets that are scheduled to a CoS queue that is already full are dropped regardless of priority. 3.7.5.4 Color Dropping Frames are dropped based on the internal priority and color information in the PCP value. As shown in Table 2, incoming frames with same priority may receive different colors based on bandwidth profile compliance. See Section 3.7.5.2 on page 44, for an example of color dropping. 3.7.5.5 Weighted Random Early Detection Weighted Random Early Detection (WRED) increases throughput of aggregated traffic streams occurring from TCP sources in the network. TCP retransmits packets if packets are dropped. If a TCP packet is dropped, the TCP source interprets the packet loss as being caused by network congestion. To avoid network congestion, TCP reduces the transmission rate by half before slowly increasing it again until a new packet loss is detected. Without WRED, packet loss occurs as a result of a full switch buffer and causes a tail drop. The tail drop may have a massive impact on all TCP streams, which causes all streams to simultaneously reduce their transmission rate before simultaneously slowly increase them again. This behavior causes network throughput oscillations. WRED prevents this behavior by introducing an early detection of buffer queue build ups. In case of a queue build up, WRED starts dropping packets. The drop probability is low in the beginning and increases if the queue continues to grow, see Figure 37. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 45 Technical Description Buffer Queues Scheduler Treshold Incoming Ethernet traffic stream Aggregated Ethernet traffic streams 12190 Figure 37 Weighted Random Early Detection Thus, only a few TCP sources are affected and reduce their rate by half. As a result, the total load from the aggregated TCP streams is only slightly reduced and oscillations in network throughput are avoided. 3.7.5.6 Packet Aging It is possible to drop packets based on age. When Packet Aging is used, packets that have been stored too long and no longer can be delivered with purpose are dropped. Packet aging is configured per service per traffic class, where a service is the switch or one of the Ethernet Layer 1 Connection services. The default settings for Ethernet packet aging is shown in Figure 38. TC 0 TC 1 TC 2 TC 3 TC 4 TC 5 TC 6 TC 7 100 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 12138 Figure 38 3.7.5.7 Default Settings for Packet Aging Strict Priority With strict priority scheduling, the eight traffic class queues are handled one-by-one with the highest priority queue first. The scheduler always handles the queue with highest priority until it is empty. Once the queue with highest priority is empty the scheduler moves on to the next queue with lower priority. If 46 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node frames are placed in a queue with higher priority, the scheduler handles these frames before it returns to handle the frames in the queue with lower priority. 3.7.5.8 Weighted Fair Queuing A potential problem with strict priority scheduling is that queues with lower priorities may be starved, that is, the frames in the queues are not handled and eventually dropped. By using Weighted Fair Queuing (WFQ) it is possible to avoid starvation. When WFQ is used, queues can be configured with a weight parameter, which decides how large share of the available output port bandwidth that is dedicated to the specific queue, see Figure 39. The bandwidth unused by one or more of the queues configured with WFQ is shared by the remaining queues. Queue 2 (25% b/w) Scheduler Queue 1 (50% b/w) Order of packet transmission Queue 3 (25% b/w) 12188 Figure 39 WFQ It is possible to combine strict priority and WFQ and thereby enable both priority and fair share of output bandwidth. When strict priority is used, sync is always given the highest priority and voice the second highest priority. The remaining traffic can be given different priority but has always lower priority than sync and voice. On a site where both WFQ and strict priority is used, sync and voice traffic are placed in the highest priority queues, configured with strict priority. The remaining traffic is given a weight parameter first and is then placed in a priority queue. An example of combined strict priority and WFQ is illustrated in figure Figure 40. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 47 Technical Description Highest priority Sync Strict Priority Scheduler Voice (50% b/w) WFQ Radio interface Best Effort (50% b/w) Lowest priority 12189 Figure 40 WFQ and Strict Priority In Figure 40, traffic from a 3G Base Station and an LTE Base station is handled by MINI-LINK TN. Sync and voice traffic from the 3G Base Station and the LTE Base station are placed directly in priority queues configured with strict priority. The best effort traffic from the 3G Base Station is placed in one WFQ queue and the best effort traffic from the LTE Base Station is placed in another WFQ queue. When sync and voice queues have been served, the remaining output port bandwidth is shared between the WFQ queues according to their weight, in this case 50 % for each queue. The traffic in the WFQ queues has lower priority than sync and voice. 3.7.6 L1 Radio Link Bonding L1 Radio Link Bonding enables transparent transport of Ethernet frames over a number of parallel Packet Links, see Figure 41. The aggregated Packet Links are sometimes referred to as Gbit Ethernet Link as they can provide up to 1 Gbps Native Ethernet throughput. 48 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node Packet Links Switch or Layer 1 Connection MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H NPU1 C /NPU3 B RL-IME with Radio Link Bonding Eth RL-IME with Radio Link Bonding NPU1 C /NPU3 B Switch or Layer 1 Connection Eth 12172 Figure 41 L1 Radio Link Bonding When Native Ethernet is combined with PDH traffic in a Radio Link, referred to as Hybrid Radio Link, the total Radio Link capacity is shared between Native Ethernet sent over Packet Links, and PDH traffic sent over TDM Links. For information on Hybrid Radio Links, see Section 4.3 on page 101. For information on planning of L1 Radio Link Bonding, see Planning and Dimensioning L1 Radio Link Bonding, Reference [9]. L1 Radio Link Bonding is configured using Radio Link Inverse Multiplexing for Ethernet (RL-IME) and the Radio Link Bonding feature in MINI-LINK Craft. When the Radio Link Bonding feature is enabled, Ethernet frames are segmented into smaller parts before they are sent over the Packet Links. On the other side of the hop, packets are buffered and reassembled into Ethernet frames again before being forwarded. This enables a more efficient use of Radio Link capacity. In order to use L1 Radio Link Bonding the NE must be configured with NPU3 B, which provides five RL-IMEs, or NPU1 C which provides 16 RL-IMEs, and a modem unit supporting Native Ethernet, such as MMU2 D or MMU2 H. Depending on how many Packet Links that should be used for transport of Native Ethernet, an RL-IME can be configured as follows: • Single-link mode, applicable for all RL-IMEs. • Multiple-link mode, only applicable for two of the RL-IMEs on NPU3 B and four of the RL-IMEs on NPU1 C. Single-link Mode Single-link mode is used when only one Packet Link is assigned to an RL-IME, see Figure 42. No inverse multiplexing of Native Ethernet is performed in 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 49 Technical Description Single-link mode and due to that, no extra overhead is added. By default, RL-IMEs with only one Packet Link assigned are configured to run in Single-link mode. Packet Link NPU1 C/NPU3 B Eth Switch or Layer 1 Connection RL-IME NPU1 C/NPU3 B MMU2 D/ MMU2 H MMU2 D/ MMU2 H RL-IME Switch or Layer 1 Connection Eth 12166 Figure 42 Single-link Mode Multiple-link Mode Two of the RL-IMEs on NPU3 B and four of the RL-IMEs on NPU1 C can be configured to run in Multiple-link mode by enabling Radio Link Bonding. In Multiple-link mode it is possible to assign up to two or four Packet Links to these RL-IMEs and thereby enable up to 1 Gbps Native Ethernet throughput. On NPU3 B one RL-IME can be configured with up to four Packet Links, as illustrated in Figure 41, and another RL-IME with up to two Packet Links. On NPU1 C, all four RL-IMEs can be configured with four packet links. A number of different configurations are possible. For example, two Packet Links can be added to the RL-IMEs, respectively, as illustrated in Figure 43. Packet Links RL-IME with Radio Link Bonding RL-IME with Radio Link Bonding Eth Switch or Layer 1 Connection MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H MMU2 D/ MMU2 H Switch or Layer 1 Connection Eth RL-IME with Radio Link Bonding Eth Switch or Layer 1 Connection NPU1 C /NPU3 B RL-IME with Radio Link Bonding NPU1 C /NPU3 B Switch or Layer 1 Connection Eth 12170 Figure 43 L1 Radio Link Bonding with Two RL-IMEs It is possible to begin with adding just one Packet Link to the RL-IMEs respectively, and later on enable Radio Link Bonding for these RL-IMEs in 50 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node order to add additional Packet Links. However, during the enabling of Radio Link Bonding traffic disturbance will occur. Note: By enabling Radio Link Bonding from the beginning for RL-IMEs with only one Packet Link, it is possible to add more Packet Links later on without any traffic disturbance. Graceful Degradation Native Ethernet traffic is distributed over the Packet Links in an RL-IME. If a Packet Link is removed or faulty, the traffic is taken over by the remaining Packet Links in the RL-IME. The traffic takeover is done through graceful degradation and is performed without traffic interruption. However, the total link capacity is decreased and traffic with low priority may be discarded to ensure that traffic with high priority is sent. Example Four Packet Links of 155 Mbps, respectively, are aggregated into one logical link with a total capacity of 620 Mbps (4×155 Mbps). One Packet Link fails and the traffic is handled by the remaining three links and the new total link capacity is 465 Mbps. 3.7.7 Supported Frame Sizes The switch on NPU1 C and NPU3 B supports jumbo frames, which handles Ethernet packets with size up to 9216 bytes. The increased frame size minimizes the overhead data for certain traffic types and increases Ethernet throughput. Jumbo frames are supported by the physical LAN ports and the WAN ports connected to RL-IMEs. The LAN/WAN ports on NPU3 support frame size up to 2048 bytes. 3.7.8 Ethernet Link OAM Ethernet Link Operation, Administration and Maintenance (OAM) provides fault management on Ethernet links with support for the following: • Failure notification • Link monitoring • Remote loopback For more information on Ethernet Link OAM, see Section 5.1.2 on page 134. 3.7.9 Performance Management The following performance counters for Ethernet traffic are available: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 51 Technical Description 3.7.10 • Number of discarded packets, for example due to overflow or CRC-32 errors • Number of sent/received frames • Number of sent/received octets Plug-In Units Supporting Ethernet Traffic The following PIUs support Ethernet traffic: 3.8 • ETU2 provides five 10/100BASE-T interfaces and one 10/100/1000BASE-T interface. See Section 3.8 on page 52. • ETU2 B provides two 10/100/1000BASE-T interfaces and two 1000BASE-TX/LX/ZX/SX Small Form Factor Pluggables (SFP) interfaces, that can be either electrical or optical. See Section 3.8 on page 52. • ETU3 provides two 10/100/1000BASE-T interfaces and two 1000BASE-TX/LX/ZX/SX Small Form Factor Pluggables (SFP) interfaces, that can be either electrical or optical. See Section 3.8 on page 52. • NPU1 C provides two 10/100/1000BASE-T interfaces, one for Ethernet Traffic and one for Ethernet Traffic or 10/100/1000BASE-T Ethernet site LAN. It also provides two 1000BASE-TX/LX/ZX/SX Small Form Factor Pluggables (SFP) interfaces, that can be either electrical or optical. NPU1 C supports half and full duplex and provides an Ethernet switch. See Section 3.3.1 on page 20 • NPU3 provides two 10/100BASE-T interfaces, one for Ethernet Traffic and one for Ethernet site LAN. See Section 3.3.1 on page 20. • NPU3 B provides two 10/100/1000BASE-T interfaces, one for Ethernet Traffic and one for Ethernet Traffic or 10/100BASE-T Ethernet site LAN. NPU3 B supports half and full duplex and provides an Ethernet switch. See Section 3.3.1 on page 20. • MMU2 D provides one 60 V RAU connector and supports Hybrid Radio Link. See Section 4.2 on page 83. • MMU2 H provides one 60 V RAU connector and one XPIC connector. MMU2 H supports Hybrid Radio Link, XPIC, and Hitless Adaptive Modulation. See Section 4.2 on page 83. Ethernet Interface Unit (ETU) The following ETUs are available: 52 • ETU3 • ETU2 B 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node • ETU2 The ETUs are compared in Table 4 and illustrated in Figure 44. Table 4 ETU Comparison ETU3 Ethernet interfaces ETU2 B ETU2 2×1000BASE-TX/LX/ZX/SX SFP, (optical or electrical) 2×1000BASE-TX/LX/ZX/SX SFP, (optical or electrical) 1×10/100/1000BASE-T 2×10/100/1000BASE-T 2×10/100/1000BASE-T 5×10/100BASE-T Total Ethernet Capacity Up to 2 Gbps total throughput Up to 2 Gbps total throughput Up to 190 Mbps total throughput Ethernet over PDH Capacity Up to 190 Mbps throughput for IM groups Up to 190 Mbps throughput for IM groups Up to 190 Mbps throughput for IM groups Up to 95 Mbps per IM group Up to 95 Mbps per IM group Up to 95 Mbps per IM group (1) Up to 6 IM groups Up to 6 IM groups Up to 6 IM groups Quality of Service Priority awareness Priority awareness Priority awareness Connection to embedded Ethernet switch Supported (NPU3 B) Supported (NPU3 B / NPU1 C) – Standalone Ethernet – – Supported Size Half slot Full size Full size Subrack AMM 2p B All AMMs except AMM 1p All AMMs except AMM 1p AMM 6p C AMM 6p D (1) Depending on AMM slot capacity 10 100 1000 Link Fault BR Power ETU2 ERICSSON 10/100/1000B ASE-T ETU2 10/100BASE -T :1 ETU2 B Fault Power BR 10/100/1000BASE -T 10/100/1 000BASE-T ERICSSON TR:4 TR:3 1000BASE-T/X OUT TR:2 IN 1000BASE-T/X OUT TR:1 IN ETU2 B :1 ETU3 10/100/1000BASE-T 10/100/1000B ASE-T 1000BASE-T /X 1000BASE-T /X F P TR:4 TR:3 OUT TR:2 IN OUT TR:1 IN ETU3 11909 Figure 44 ETUs 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 53 Technical Description 3.8.1 Functional Blocks This section describes ETU2, ETU2 B, and ETU3 based on the block diagrams in Figure 45 and Figure 46. Inverse Multiplexers TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Ethernet nxE1 10/100/1000BASE-T nxE1 10/100BASE-T nxE1 10/100BASE-T nxE1 10/100BASE-T nxE1 10/100BASE-T nxE1 10/100BASE-T Secondary voltages 7489 Figure 45 54 Block Diagram for ETU2 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node High Speed Bus High Speed Inverse Multiplexers TDM Bus TDM Ethernet nxE1 1000BASE-TX nxE1 1000BASE-TX nxE1 10/100/1000BASE-T nxE1 10/100/1000BASE-T nxE1 nxE1 PCI Bus Control and Supervision SPI Bus SPI Power Bus Power Secondary voltages 10046 Figure 46 3.8.1.1 Block Diagram for ETU2 B and ETU3 TDM This block interfaces the TDM bus by receiving and transmitting the E1s used to carry Ethernet traffic. 3.8.1.2 Inverse Multiplexers Each Inverse Multiplexer (IM) converts one Ethernet connection into n×E1, where n≤48, transmitted to and received from the TDM block. There is a total of 48 E1s for three IM groups. 3.8.1.3 Ethernet This block provides the unit’s external Ethernet interfaces. For ETU2 each interface is linked to one inverse multiplexer, and for ETU2 B and ETU3 each interface is linked to the High Speed Bus. For ETU2, 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 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 55 Technical Description 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. 3.8.1.4 High Speed This block provides a Point-to-Point connection to other PIUs via the High Speed Bus. The High Speed Bus connects ETU2 B and ETU3 with the Ethernet Switch on NPU1 C and NPU3 B. 3.8.1.5 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. 3.8.1.6 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 3.8.1.7 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. 56 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.9 ATM Aggregation 3.9.1 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. ATM traffic aggregation in MINI-LINK is achieved by fitting an ATM Aggregation Unit (AAU) in the subrack. 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 47 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+ 11.3 Mbit/s VP/CBR 8xE1 VC/UBR+ VC/CBR 4.7 Mbit/s MINI-LINK TN with AAU VC/UBR+ 11.7 Mbit/s VP/CBR 8xE1 VC/CBR 4.3 Mbit/s Shared 13 Mbit/s 11xE1 VP/CBR VC/UBR+ VC/CBR 4.7 Mbit/s VC/CBR 4.3 Mbit/s 8924 Figure 47 VP/VC Cross-Connection 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 kbps) 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 48 shows how the different traffic types are routed in the backplane. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 57 Technical Description WCDMA RAU GSM MMU AAU TDM bus LTU MMU MMU RAU RAU 8489 Figure 48 3.9.2 Traffic Types ATM Aggregation Unit (AAU) The main function of the AAU is to aggregate traffic from other plug-in units in the subrack. It is fitted in an AMM 6p C or D or AMM 20p B. ERICSSON Fault Power BR AAU AAU 8490 Figure 49 AAU The AAU has no front connectors but interfaces up to 96 E1s in the backplane. The E1s can be used as single links with G.804 mapping or combined 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 16. 58 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node The following is a summary of the AAU functions: 3.9.2.1 • Capacity of 96xE1. 24xE1 is the default capacity and additional groups of 24xE1 are available as optional features. • 16 ATM interfaces, IMA groups or G.804 • Up to 16×E1 in one IMA group • Cross-connection capability of 622 Mbps, 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 50. Utopia Interface TDM Bus TDM PCI Bus Control and Supervision SPI Bus SPI Power Bus Power IMA ATM Cross-connect Secondary voltages 8491 Figure 50 Block Diagram for AAU 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 59 Technical Description 3.9.2.1.1 TDM This block interfaces the TDM bus by receiving and transmitting nxE1 (n≤96) for aggregation. The transmitted E1s need synchronization input utilizing the Network Synchronization mode. 3.9.2.1.2 IMA 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. 3.9.2.1.3 ATM Cross-connect This block handles the ATM cross-connection of traffic on a maximum of 16 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. 60 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 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 16 independent schedulers that are individually mapped to any of the 16 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 Mbps for a G.804 link. 3.9.2.1.4 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. The block holds a Device Processor (DP) running plug-in unit specific software. 3.9.2.1.5 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 61 Technical Description 3.9.2.1.6 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. 3.9.2.2 Fault Management The AAU supports the handling of F4/F5 O&M functions for Fault Management (FM), according to ITU-T I.610. The following FM indications are used: • 62 The AAU is transparent to Continuity Check (CC) and Loopback (LB) cells, for monitoring continuity and detection of ATM layer defects in real time. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.10 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 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 subrack 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 nxE1 Plug-in Unit nxE1 Plug-in Unit nxE1 Plug-in Unit nxE1 Plug-in Unit nxE1 nxE1 nxE1 nxE1 nxE1 Plug-in Unit Plug-in Unit Plug-in Unit Plug-in Unit TDM bus 10074 Figure 51 Traffic Routing 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 63 Technical Description Note that the TDM bus can carry close to 400 uni-directional E1s in AMM 20p B and AMM 6p C/D, half of this in AMM 2p B, 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 C/D and AMM 20p B TDM bus, half of this in AMM 2p B. The traffic routing function is controlled from MINI-LINK Craft, locally or remotely. Traffic configuration can also be done using the SNMP interface. 3.10.1 ServiceOn Network Manager The ServiceOn Network Manager (SO NM ) provides a way to provision end-to-end E1 connections in a network. All operations related to the E1 provisioning are done from a graphical representation of the network nodes and the E1 connections. Color codes are used to visualize alarm status. Detailed alarm info and status are shown in near real time. In addition the "Root Cause" feature at the Network level suppresses lower order alarms that occur as a consequence of higher level fault. This reduces the impact of major disruptions on the operators by only showing the major network faults. A number of different reports can be extracted on demand to view performance data and statistics related to an E1 end-to end connection. 64 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.11 Protection Mechanisms This section describes the protection mechanisms provided by the Basic Node. Protection of the radio link is described in Section 4.7 on page 116. 3.11.1 Overview To ensure high availability, MINI-LINK TN R4 provides protection mechanisms on various layers in the transmission network as illustrated in Figure 52. • Network layer protection using the 1+1 SNCP mechanism provides protection for the sub-network connection a-b in Figure 52. 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 52. 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 52. Network layer protection Physical link layer protection Equipment protection 2 c a 1 3 4 b 5 6 = Network Element (NE) = Plug-in unit 6627 Figure 52 MINI-LINK TN R4 Provides High Availability Through Various Protection Mechanisms Network layer and physical link layer protection share the following characteristics: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 65 Technical Description Permanently Bridged Identical traffic is transmitted on the active and the passive physical link/connection. Uni-directional 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. Non-revertive 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 reestablished. 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. 3.11.2 Network layer protection 3.11.2.1 1+1 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 R4 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 1+1. 66 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 1+1 E1 SNCP group Tx Rx Protected E1 1+1 E1 SNCP group Link or sub-network Unprotected E1 Rx Tx Protected E1 Unprotected E1 6632 Figure 53 1+1 E1 SNCP Principle Performance data is collected and fault management is provided for unprotected as well as protected VC interfaces (that is the 1+1 E1 SNCP group). This gives accurate information on the availability of network connections. 3.11.2.2 1+1 SDH SNCP 1+1 SDH Sub-Network Connection Protection (1+1 SDHSNCP) is a protection mechanism used for network protection on VC4, VC3 or VC12 level, between two MINI-LINK TN R4 NEs. It is based on the simple principle that one VC4, VC3 or VC12 is transmitted on two separate VC4, VC3 or VC12 connections (permanently bridged). The switching is performed at the receiving end where the two connections are terminated. It switches automatically between the two incoming VC4, VC3 or VC12s in order to use the better of the two. The decision to switch is based on signal failure of the signal received (LOP or AIS). At each end of the protected VC4, VC3 or VC12 connection, two VC4, VC3 or VC12 level connections must be configured to form a 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 VC SNCP function is independent of the 1+1 radio protection and the MSP 1+1. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 67 Technical Description 1+1 VC SNCP group Tx Rx Protected VC 1+1 VC SNCP group Link or sub-network Rx Tx Protected VC Unprotected VC Unprotected VC 10088 Figure 54 1+1 VC SNCP Principle Performance data is collected and fault management is provided for unprotected as well as protected VC4, VC3 or VC12 interfaces (that is the 1+1 VC SNCP group). This gives accurate information on the availability of network connections. 3.11.2.3 Ring Protection Ring Star Tree 6628 Figure 55 Network Topologies The 1+1 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. A connection entering a ring at one point and exiting at another point can therefore be protected with a 1+1 SNCP group configured at each end of the 68 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node connection. The traffic is transmitted in both directions of the ring and the traffic is received from two directions at the termination point. In this solution, the ring network can tolerate one failure without losing transmission. When the failure reoccurs, the affected connections are switched in the other direction. In a MINI-LINK TN R4 network, these ring structures can be built using PDH Radio Terminals with capacities of up to 80x2 Mbps, and using SDH Radio Terminals with the LTU 155 (STM-1 interface) with capacities up to 63x2 Mbps. 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 56. As an example, consider the nodes A and E in Figure 56. To protect the connection from A to E the two alternative connections from A to E must be defined as a 1+1 SNCP group at A and as a 1+1 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 SNCP groups at A and C. A B F E C D 6629 Figure 56 Example of Ring Protection with 1+1 SNCP The 1+1 SNCP function can be used to build protection in more complex topologies than rings, using the same principle. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 69 Technical Description 3.11.3 MSP 1+1 The LTU 155 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 57. The unit intercommunication is done over the BPI bus. STM-1 electrical or optical SDH Mapping BPI MSP 1+1 Switch Passive Active LTU155e/o LTU155e/o SDH Mapping 63xE1 TDM Bus 7468 Figure 57 Two LTU 155e/o Plug-In Units in an MSP 1+1 Configuration The switching is done automatically if the following is detected: • Signal Failure (SF): LOS, LOF, MS-AIS or RS-TIM • Signal Degradation (SD) based on MS-BIP Errors (BIP-24) • Local equipment failure The operator can also initiate the switching manually. The switch logic for MSP 1+1 is handled by the unit’s Device Processor. 70 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node LTU 155 SF/SD MSP Switch Controller E1->VC-12->VC-4 Rx 63xE1 Switch MS/RS Rx Tx Tx LTU 155 Tx 63xE1 Rx E1->VC-12->VC-4 MS/RS Rx MSP Switch Controller 6633 Figure 58 MSP 1+1 Principle 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 71 Technical Description 3.11.4 Equipment and Line Protection AMM 2p B MMU2 E 155 MMU2 E 155 ADM AMM 2p B MMU2 E 155 MMU2 E 155 ADM 9719 Figure 59 High Capacity Hop Protected with ELP 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 (for example 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. 72 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node 3.11.5 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 6.3 on page 159, plus an external optical combiner/splitter, see Figure 60, 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 83. 9358 Figure 60 Optical Splitter/Combiner 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 73 Technical Description 3.12 Synchronization 3.12.1 Overview For more information about network synchronization, see Network Synchronization Guidelines, Reference [7]. 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 sync 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 sync from local oscillator or loop timing. • PDH primary rate channels used for Ethernet over PDH will have outgoing sync generated by the local oscillators. • AAU or ATM switches should not be used in the Free Running Mode. MINI-LINK TN ETSI can 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). 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 61 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. 74 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node Active synchronization path Inactive synchronization path NE NE NE NE NE NE 9531 Figure 61 Master-Slave Synchronized Network 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: 3.12.2 • SDH Equipment Clock • Status SDH Equipment Clock The SEC function maintains an equipment clock with network reference clock selection, clock generation, filtering and redundancy. As illustrated in Figure 62 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, MSP 1+1 group, or Radio Link RF, are available for nomination. It is possible to use one of the E1 ports on the NPU1 B, NPU1 C, NPU3, and NPU3 B as an external 2048 kHz synchronization clock input interface. Note: For Compact Nodes the external synchronization clock input interface is 2048 kbps. The standard used for Compact Node regarding this, is G.703, paragraph 9. For MINI-LINK TN paragraph 13 in the same standard is used. When choosing Radio Link RF with SSM, the sync signal operates over the physical layer and does not occupy any bandwidth. It is therefore immune to the 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 75 Technical Description traffic load. Radio Link RF is available as sync signal for configurations including an MMU with support for Hybrid Radio Link, such as MMU2 D and MMU2 H. The SEC performs automatic synchronization trail restoration based on the priority table and the status of the inputs. In the event of failure of all synchronization source nominees, the SEC enters holdover mode using its own internal clock as source. Note: G.813 performance during trail restoration and holdover requires at least one NPU3 B, NPU3, SXU3 B, AAU, or LTU 155 plug-in unit in the subrack The SEC is distributed throughout the subrack. All terminated protocol layers interfaces (for example 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. On NPU1 B, NPU1 C, NPU3, and NPU3 B it is possible to also dedicate one E1 port for output of 2048 kHz synchronization clock signal for synchronization of other elements in the network. This can preferably be used in the peripheral parts of the network where an RBS is connected to a MINI-LINK TN. For more information on how to configure E1 output on the NPU, see MINI-LINK Craft User Interface Descriptions, Reference [4]. It is only possible to use E1 sync output when the chosen sync input also is an E1 (2048 kbps). In case the sync input is lost the 2048 kHz output sync signal will be stopped. The RBS will then enter holdover mode and use the internal clock until sync is reestablished. 3.12.3 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 SSM, for these to send AIS or to mute the signal. 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. If SSM is not supported, squelching may be used towards interfaces carrying a synchronization path towards other equipment as long as prioritized traffic is not interrupted. The parameter 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 than the 76 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node Hold Off Time of the protected interface, to avoid unnecessary switching of synchronization sources. Synchronization Logic SEC Network Synchronization T0 Free Running Logic STM-1 MSP 1+1 E1 1+1 E1 SNCP 2048 kHz Radio Link RF T1 T2 Status Synchronization Status Propagation Squelch Interfaces E1 Selection T3 Interfaces STM-1 T0, T1, T2 and T3: ITU-T SDH Equipment Clock (SEC) names Loop Timing or NE Timing Interfaces 2048 kHz Interfaces Synch over Radio Link 12100 Figure 62 MINI-LINK TN Synchronization Functions 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 77 Technical Description 3.13 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 subracks 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 over-temperature, for example due to a fan failure or a too high ambient temperature. The plug-in unit is automatically returned to normal operation when temperature is below the high threshold level. There are two thresholds: 0 Crossing the high temperature threshold: NPUs raises a temperature alarm (critical). The NPU will still though be in full operation. All plug-in units except NPUs raises a temperature alarm (minor) and shuts down the plug-in unit’s control system (reduced service). The traffic function of the plug-in unit will still be in operation. 0 Crossing the excessive temperature threshold: NPUs shuts down the entire NPU (out of service). 78 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Basic Node All plug-in-units except NPUs raises a temperature alarm (critical) and 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 79 Technical Description 3.14 MINI-LINK E Co-siting An SMU2 can be fitted in an AMM 2p B, AMM 6p C/D or AMM 20p B to interface MINI-LINK E equipment on the same site. The following interfaces are provided: • 1xE3 + 1xE1 • 1xE2 or 2xE2 • 2xE1 • 2xE0 (2x64 kbps) used for IP DCN • O&M (V.24) access server Fault Power BR SMU2 ERICSSON O&M E3:3A E2:3B-3C E3/ 2xE2 O&M E1:2A-2B 2xE1 SMU2 DIG SC:1A-1B 2xE0 6728 Figure 63 SMU2 All the traffic capacities are multiplexed/demultiplexed to nxE1 for connection to the TDM bus. MINI-LINK E 2xE1, 1xE2, 2xE2 or 1xE3 + 1xE1 2xE0 MINI-LINK TN SMU2 2xE1 to 17xE1 TDM Bus 7469 Figure 64 80 MINI-LINK E Co-Siting 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4 Radio Link 4.1 Overview A Radio Link provides microwave transmission from 2x2 to 155 Mbps, operating within the 6–38 GHz frequency bands, utilizing C-QPSK and 16, 64, 128 or 256 QAM modulation schemes. It can be configured as unprotected (1+0) or protected (1+1). 15 GHz 15 GHz POWER ALARM NT ALIGNME zHG 51 RADIO CABLE 15 GHz 1 G5 zH 15 GHz RADIO CABLE POWER ALARM NT ALIGNME ALARM POWER ALIGNMENT RADIO CABLE Power A -48V Alarm A Fault Power Alarm B Power B -48V FAN UNIT MMU2 4-34 NPU1 B LTU 155e/o LTU 16x2 NPU 8x2 MMU2 4-34 INFORMATION MMU2 4-34 8483 Figure 65 An Unprotected (1+0) Radio Terminal (grayed) An unprotected (1+0) Radio Terminal comprises: • One RAU • One antenna • One MMU 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 81 Technical Description • 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.7 on page 116. Radio Cables The radio cables between the Radio and Modem Units in the subracks 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. 82 • Ø10 mm — with lengths up to 200 m or between 100 and 200 m • Ø16 mm — with lengths between 200 and 400 m 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.2 Modem Unit (MMU) 4.2.1 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: • 2×E1, 4×E1, 8×E1, 17×E1 MMU2 C A traffic capacity and modulation agile plug-in unit, used for the following modulation schemes and traffic capacities: MMU2 CS 4/E1 • C-QPSK: 2×E1, 4×E1, 8×E1, 17×E1 • 16 QAM: 8×E1, 17×E1, 32×E1 A traffic capacity and modulation agile plug-in unit used for the following modulation schemes and traffic capacities: • C-QPSK: 2×E1, 4×E1, 8×E1, 17×E1 • 16 QAM: 8×E1, 17×E1 MMU2 CS 4/E1 has four additional 4×E1 traffic interfaces with support for 120 and 75 Ohm. However, only the first 4×E1 traffic interface is active. The other traffic interfaces are hard coded to Down and cannot be configured. Thus, no alarms are generated from the interfaces set to Down. The capacity and modulation are set in the same way as for MMU2 CS 16/E1. The front panel also provides one control interface (Ethernet) used for O&M and DCN traffic. The plug-in unit can only be used in an AMM 1p and provides the following functions: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 • Traffic handling • System control and supervision • IP router for DCN handling, supporting static routing only. • SNMP Master Agent 83 Technical Description Note: • Ethernet interface for MINI-LINK Craft connection • Storage and administration of inventory and configuration data • In field software upgrade MMU2 CS 4/E1 and MMU2 CS 16/E1 have the same physical interfaces. Information on modem unit type is found on the label on one of the latches. The label on MMU2 CS 4/E1 is marked MMU2 CS 4/E1 and the label on MMU2 CS 16/E1 is marked MMU2 CS. MMU2 CS 16/E1 A traffic capacity and modulation agile plug-in unit used for the following modulation schemes and traffic capacities: • C-QPSK: 2×E1, 4×E1, 8×E1, 17×E1 • 16 QAM: 8×E1, 17×E1 MMU2 CS 16/E1 has four additional 4×E1 traffic interfaces with support for 120 and 75 Ohm, and one control interface (Ethernet) used for O&M and DCN traffic. The plug-in unit can only be used in an AMM 1p and provides the following functions: 84 • Traffic handling • System control and supervision • IP router for DCN handling, supporting static routing only. • SNMP Master Agent • Ethernet interface for MINI-LINK Craft connection • Storage and administration of inventory and configuration data • In field software upgrade 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link MMU2 D A traffic capacity and modulation agile plug-in unit, used for the following modulation schemes and traffic capacities: • 16 QAM: 21 Mbps / 10×E1, 45 Mbps / 22×E1, 95 Mbps / 46×E1 • 64 QAM: 31 Mbps / 15×E1, 199 Mbps / 80xE1 • 128 QAM: 72 Mbps / 35×E1, 154 Mbps / 75×E1, 325 Mbps / 80×E1 MMU2 D supports control of the ratio between Native Ethernet and PDH traffic sent over Hybrid Radio Links. The Native Ethernet part of the aggregated capacity is set with E1 granularity. MMU2 D also supports an automatically activated power save function. The power save is done by a -48 V bypass when an MMU2 D is directly connected to a RAU that supports the same function. The prerequisites for the power save function to activate is that the system is: • fed with -48 V • grounded with the positive supply conductor connected to the output ground. MMU2 E 155 A high capacity SDH plug-in unit, used for the following modulation schemes and traffic capacities: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 • 16 QAM: STM-1 + 1×E1 • 64 QAM: STM-1 + 1×E1 • 128 QAM: STM-1 + 1×E1 85 Technical Description MMU2 F 155 A high capacity SDH plug-in unit with XPIC support, see Section 4.2.2.12 on page 99, used for the following modulation schemes and traffic capacities: • 16 QAM: STM-1 + 1×E1 • 64 QAM: STM-1 + 1×E1 • 128 QAM: STM-1 + 1×E1 Note: XPIC can be used in combinations with all above listed capacities. If XPIC is not used, MMU2 F 155 has the same modulation schemes and traffic capacities as MMU2 E 155. MMU2 H A high capacity PDH and Ethernet plug-in unit with support for XPIC, see Section 4.2.2.12 on page 99, and Hitless Adaptive Modulation, see Section 4.4 on page 102. XPIC and Hitless Adaptive Modulation both require a license and cannot be used simultaneously. MMU2 H supports control of the ratio between Native Ethernet and PDH traffic sent over Hybrid Radio Links. The Native Ethernet part of the aggregated capacity is set with E1 granularity. MMU2 H is used for the following modulation schemes and traffic capacities: • C-QPSK: 8 Mbps / 4×E1, 16 Mbps / 8×E1, 33 Mbps / 16×E1 • 4 QAM: 10 Mbps / 5×E1, 23 Mbps / 11×E1 • 16 QAM: 21 Mbps / 10×E1, 45 Mbps / 22×E1, 95 Mbps / 46×E1 • 128 QAM: 72 Mbps / 35×E1, 154 Mbps / 75×E1, 325 Mbps / 80×E1 • 256 QAM: 345 Mbps / 80×E1 XPIC is supported for the following modulation and channel spacing: 86 • 16 QAM: 14 MHz, 28 MHz • 64 QAM: 7 MHz • 128 QAM: 14 MHz, 28 MHz, 56 MHz 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link • 256 QAM: 56 MHz It is possible to enable XPIC and Adaptive Modulation at the same time when using a 28 MHz channel. It is possible to configure Adaptive Modulation physical modes as static physical modes by setting Max Capacity – Modulation and Min Capacity – Modulation to the same value, using MINI-LINK Craft. The Adaptive Modulation physical modes configured as static can only be used in hops configured with MMU2 H on both sides. No license for Adaptive Modulation is required when Max Capacity – Modulation and Min Capacity – Modulation are set to the same value. The following physical modes are available as static when using Hitless Adaptive Modulation: • 4 QAM: 10 Mbps / 4×E1, 21 Mbps / 10×E1, 45 Mbps / 21×E1, 93 Mbps / 45×E1 • 16 QAM: 21 Mbps / 10×E1, 42 Mbps / 20×E1, 91 Mbps / 44×E1, 189 Mbps / 80×E1 • 32 QAM: 237 Mbps / 80×E1 • 64 QAM: 30 Mbps / 14×E1, 63 Mbps / 30×E1, 134 Mbps / 65×E1, 285 Mbps /80×E1 • 128 QAM: 35 Mbps / 17×E1, 72 Mbps / 35×E1, 154 Mbps / 75×E1, 326 Mbps / 80×E1 • 256 QAM: 41 Mbps / 20×E1, 81 Mbs / 39×E1, 172 Mbps / 80×E1, 369 Mbps / 80×E1 • 512 QAM: 405 Mbps / 80×E1 for 56 MHz MMU2 B, MMU2 C and MMU2 D have the same functionality regarding mechanics and interfaces, but there is an important difference when it comes to compatibility. MMU2 D is not compatible with MMU2 B or MMU2 C, that is, it cannot be combined with MMU2 B or MMU2 C in a 1+0 or 1+1 hop. MMU2 D can be placed in the same subrack as MMU2 B or MMU2 C but cannot be part of the same Radio Link. However, MMU2 D is hop compatible with MMU2 H. For more information, see description of MMU2 H below. For RAU compatibility, see Table 5. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 87 Technical Description Fault Power BR MMU2 B ERICSSON 60V RAU MMU2 B RAU ERICSSON Fault Power BR MMU2 C 60V RAU MMU2 C Fault Power BR MMU2 D ERICSSON 60V RAU MMU2 D 10063 Figure 66 MMU2 B, C and D MMU2 CS 4/E1 and MMU2 CS 16/E1 has one Ethernet port, four 4xE1 ports, and one RAU connector on the front panel. The plug-in unit can be used in an AMM 1p only. Control functions normally provided by an NPU, such as traffic handling and system control and supervision, are included in the MMU2 CS allowing the modem to work as a stand alone plug-in unit in an AMM 1p. The Ethernet port (10/100 BaseT) enables connection to MINI-LINK Craft, which is used for O&M and DCN traffic handling. For RAU compatibility, see Table 5. 88 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Ethernet E1 RAU 11618 Figure 67 MMU2 CS 4/E1 and MMU2 CS 16/E1 MMU2 E 155 and MMU2 F 155 have the same functionality regarding mechanics and interfaces but MMU2 F 155 also has support for XPIC. 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 6.3 on page 159. For RAU compatibility, see Table 5. MMU2 E 155 MMU2 F 155 RAU RX 60V RAU STM-1 BR Fault 60V SFP TX Power ERICSSON RX STM-1 Fault BR ERICSSON Power TX SFP XPIC 9696 Figure 68 MMU2 E and F 155. Note: MMU2 F 155 has XPIC Support MMU2 H is a high capacity PDH and Ethernet plug-in unit with support for XPIC and Hitless Adaptive Modulation. MMU2 H is hop compatible with MMU2 D, unless static Adaptive Modulation physical modes are used. If static Adaptive Modulation physical modes are used, the hop must be configured with an MMU2 H on both sides. Some static Adaptive Modulation physical modes are designed for the same channel spacing and modulation as regular physical modes that are available for both MMU2 H and MMU2 D. However, the static Adaptive Modulation physical modes are not compatible with regular physical modes, that is, the different physical modes cannot be used together in a hop. Therefore, MMU2 D is only hop compatible with MMU2 H when regular physical modes are used. Like MMU2 D, MMU2 H can be placed in the same subrack as MMU2 C but cannot be part of the same Radio Link. Note: XPIC and Hitless Adaptive Modulation require a license. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 89 Technical Description For RAU compatibility, see Table 5. RAU XPIC 11747 Figure 69 Table 5 MMU2 H Compatibility Between RAUs and MMUs MMU and modulation RAU1 / RAU2 RAU1 N / X / Xu / RAU2 N / X / Xu MMU2 B, C-QPSK X X MMU2 C, C-QPSK X X MMU2 C, QAM MMU2 CS C-QPSK 4.2.2 X X X MMU2 CS QAM X MMU2 D, QAM X MMU2 E 155, QAM X MMU2 F 155, QAM X MMU2 H X Functional Block This section describes the internal and external functions of the MMU, based on the block diagram in Figure 70, Figure 72 and Figure 73. 90 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link BPI Bus (1+1) BPI Bus (1+1) DCC Radio Frame Multiplexer Traffic TDM Bus TDM Multiplexer/ Demultiplexer RAU Cable Interface DCC Radio Frame Demultiplexer Traffic HCC Demodulator HCC PCI Bus Control and Supervision SPI Bus SPI Power Bus Modulator Power RCC Secondary voltages 6637 Figure 70 Block Diagram for MMU2 B and MMU2 C 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 91 Technical Description Traffic E1 Line Interfaces LIU DCC Radio Frame Multiplexer Traffic TDM Multiplexer/ Demultiplexer Modulator RAU Cable Interface DCC Radio Frame Demultiplexer Traffic HCC HCC Demodulator RCC Control and Supervision SPI Bus Power Bus PHY Ethernet Interface SPI Power Secondary voltages 11625 Figure 71 92 Block Diagram for MMU2 CS 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link BPI Bus (1+1) BPI Bus (1+1) DCC High-speed Bus Radio Frame Multiplexer Traffic Modulator RAU Hybrid Radio Link TDM Bus Multiplexer/ Demultiplexer Cable Interface DCC Radio Frame Demultiplexer Traffic HCC Demodulator HCC PCI Bus Control and Supervision SPI Bus SPI Power Bus Internal Power RCC Secondary voltages External Power 11758 Figure 72 Block Diagram for MMU2 D 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 93 Technical Description High Speed High-speed bus Radio Frame Multiplexer DCC TDM Bus STM-1 Line interface BPI Bus (1+1) BPI Bus (1+1) TDM (Wayside traffic, E1 only) Modulator RAU Traffic Cable Interface DCC Radio Frame Demultiplexer Traffic HCC HCC PCI Bus Control and Supervision SPI Bus SPI Power Bus Demodulator Power RCC XPIC (MMU2 F 155) Secondary voltages 10080 Figure 73 94 Block Diagram for MMU2 E/F 155 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link BPI Bus (1+1) BPI Bus (1+1) Radio Frame Multiplexer DCC High-speed Bus Hybrid Radio Link Traffic Multiplexer/ Demultiplexer DCC TDM Bus RAU Cable Interface Radio Frame Demultiplexer Traffic HCC Demodulator HCC PCI Bus Control and Supervision SPI Bus SPI Power Bus Modulator Power RCC XPIC Secondary voltages 11748 Figure 74 4.2.2.1 Block Diagram for MMU2 H 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 4.7.2 on page 116. Note: The TDM block in MMU2 E/F 155 performs no multiplexing/demultiplexi ng. The traffic in the receiving direction equals 1xE1. Note: The high speed bus is used together with the integrated ADM – SXU3 B. The STM-1 Line interface on the front of the MMU is not available when the High Speed bus is used. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 95 Technical Description 4.2.2.2 Hybrid Radio Link Multiplexer/Demultiplexer This block interfaces the TDM and High-speed bus by receiving and transmitting the traffic (nxE1/Ethernet) and DCC. It performs flat multiplexing of nxE1 for further transmission to the Radio Frame Multiplexer. In the receiving direction, it performs demultiplexing of nxE1. The demultiplexed traffic and DCC are transmitted to the TDM bus while the Ethernet traffic is transmitted to the high speed bus. In a protected system, the block interfaces the BPI bus, see Section 4.7.2 on page 116. 4.2.2.3 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 4.7.2 on page 116. 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 kbps channels used for DCN communication over the hop, where 2≤n≤12 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. 96 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Multiplexing The three different data types together with check bits and frame lock bits are sent in a composite data format defined by the physical mode 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 217–1 and is synchronized each eighth frame (super frame). For C-QPSK, the FEC bits are inserted according to the physical mode and calculated using an interleaving scheme. Reed Solomon coding is used for QAM. 4.2.2.4 Modulator 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. • QAM (Quadrature Amplitude Modulation), consisting of two independent amplitude modulated quadratures. The carrier is amplitude and phase modulated. The technique enables high spectrum efficiency. 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. 4.2.2.5 Cable Interface 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 • 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 97 Technical Description 4.2.2.6 Demodulator 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. 4.2.2.7 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 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 QAM modulation. 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 physical mode 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. A fixed 10E-6 BER threshold is used when Native Ethernet is configured. Traffic On the receiving side the following is performed to the traffic data: • AIS insertion at signal loss or BER≤10-3 (BER=10E-6 for Native Ethernet) • 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. 98 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link HCC The Hop Communication Channel (HCC) is used for the exchange of control and supervision information between near-end and far-end MMUs. 4.2.2.8 AHigh Speed T2010his block provides a Point-to-Point connection to other PIUs via the High speed Bus. 4.2.2.9 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. 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. 4.2.2.10 SPI This block interfaces the SPI bus and handles equipment status. Failure is indicated by LED’s on the front of the unit. 4.2.2.11 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. Furthermore, this block provides a stable voltage for the RAU, distributed in the radio cable. 4.2.2.12 Cross Polarization Interference Canceller MMU2 F 155 and MMU2 H 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 99 Technical Description Even though the polarizations are orthogonal there is a small interference between them, in the antennas and due to installation tolerances and 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 co-polar signal and the cross-polar signal. The receiver subtracts the cross-polar signal from the co-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 radio link capacity and enables operators to reduce cost in terms of their frequency license fee. 100 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.2.2.13 PHY This block enables control and supervision over the physical Ethernet interface. 4.2.2.14 LIU This block provides physical termination of the E1 interfaces. 4.3 Hybrid Radio Link A Hybrid Radio Link is a Radio Link optimized for maximum throughput of Native Ethernet and PDH traffic. The functionality is supported by MMU2 D and MMU2 H. Hybrid Radio Link is supported by MMU2 H in XPIC mode as well. Note: To configure a Hybrid Radio Link, the NE must be equipped with NPU3 B or NPU1 C and MMU2 D or MMU2 H. Native Ethernet and PDH traffic are sent simultaneously over the Hybrid Radio Link, see Figure 75. Native Ethernet MINI-LINK TN MINI-LINK TN MMU2 D/H MMU2 D/H PDH 11745 Figure 75 Traffic over a Hybrid Radio Link A Hybrid Radio Link supports flat multiplexing of PDH traffic, which enables control of the number of E1s to be transported. PDH traffic is normally transported in sets of 4xE1 and 16xE1. With flat multiplexing it is possible to set an exact number of E1s to be transported, for example, 7xE1 or 23xE1. This allows optimized usage of bandwidth since all E1s fitting in the bandwidth also can be transported. Due to the use of one mux layer for all E1s, instead of one mux layer for each set of 4xE1 and 16xE1, the PDH overhead is decreased. A minimum of the total link capacity is used for overhead and PDH traffic and all remaining capacity can be used for Native Ethernet. The ratio between Native Ethernet and PDH traffic is configurable and is set with E1 granularity, see Figure 76 . 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 101 Technical Description Total Link Capacity = m + n m Mbps PDH n Mbps Ethernet PDH Native Ethernet E1 Granularity 11664 Figure 76 Packet sent over a Hybrid Radio Link Example • Total link capacity: 154 Mbps • PDH traffic capacity: 22xE1 (45 Mbps) • Native Ethernet capacity: 154 Mbps - 45 Mbps = 109 Mbps In Hybrid Radio Links, Native Ethernet capacity range from 0 to maximum link capacity, while PDH capacity range from 0 to 80xE1. The PDH capacity is limited by the backplane capacity of the modem. Both sides of a radio hop must have an MMU2 D or MMU2 H, and an Ethernet plug-in unit supporting the native packet radio interface, installed in order to send traffic over a Hybrid Radio Link. 4.4 Hitless Adaptive Modulation Hitless Adaptive Modulation is supported by MMU2 H and enables automatic switching between different modulations, depending on radio channel conditions. Hitless Adaptive Modulation makes it possible to increase the available capacity over the same frequency channel during periods of normal propagation conditions. Modulation, and thereby capacity, is high during normal radio channel conditions and lower during less favorable channel conditions, for example when affected by rain or snow. Modulation switches are hitless, that is, error free. In situations where traffic interruption normally would occur, it is possible to maintain parts of the traffic by switching to a lower modulation, using Hitless Adaptive Modulation. A hop with fixed modulation is normally planned to provide sufficient BER during the major part of time, for instance BER<10-6 during 99.995% of time. 102 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link This means that the channel during most of time could deliver higher capacity, still with good BER, by using a more capacity efficient modulation. For example, a hop designed to provide BER<10-6 during 99.995% of the time using 4 QAM in a 28 MHz channel, delivers 48 Mbps. However, during the majority of time, that is, all year except 4.5 hours, the channel could deliver 155 Mbps using 128 QAM. The availability for a 28 MHz channel is illustrated in Figure 77. Received signal 128 QAM 64 QAM 16 QAM 4 QAM Receiver Threshold Time Link throughput 155 Mbps 135 Mbps 90 Mbps 45 Mbps 99.9% Availability 99.95% Availability 99.99% Availability 99.995% Availability 11826 Figure 77 Example of Hitless Adaptive Modulation The TDM traffic in a channel must always fit into the lowest modulation. For example, in a 28 MHz channel with 4 QAM set as lowest modulation, the maximum TDM capacity is 21×E1 (45 Mbps). In order to handle channel variations, the channel conditions are continuously monitored on the Rx side by measurement of Signal to Noise and Interference Ratio (SNIR). When the receiver, based on this data, detects that channel conditions imply a change to the next higher or lower modulation, a message is sent to the transmitter on the other side requesting a higher or lower modulation. Upon receipt of such request the transmitter starts transmitting with the new modulation. At demodulation the receiver follows the modulation as a slave. The protection switching performance is the same as for Radio Terminals without Hitless Adaptive Modulation. In both working standby and hot standby 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 103 Technical Description the two receivers exchange information regarding wanted modulation and the higher of the two modulations is chosen. Hitless Adaptive Modulation can be configured to run in automatic or manual mode, where automatic mode is default. In manual mode it is possible to control and set static physical modes and thereby perform advanced fault tracing or advanced performance tests. Hitless Adaptive Modulation can be used in combination with L1 Radio Link Bonding in Single-link mode. However, static physical modes must be used with L1 Radio Link Bonding in Multiple-link mode. See Section 3.7.6 on page 48, for more information on L1 Radio Link Bonding. Hitless Adaptive Modulation is compatible with Automatic Transmit Power Control (ATPC), which is working in a closed loop only in the highest configured modulation. In lower modulations the output power is set as high as possible. Note: Hitless Adaptive Modulation is not supported when MMU2 H is in XPIC mode. 4.5 Radio Unit (RAU) 4.5.1 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 MINI-LINK Craft. 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. 104 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link R RADIO CABLE RAU1 ALARM POWE NT ALIGNME RAU2 8458 Figure 78 4.5.2 RAU1 and RAU2 Mechanical Design External Interfaces RADIO POWER ALARM 4 RADIO CABLE ALIGNMENT RADIO CABLE 1 3 2 1 POWER ALARM ALIGNMENT 4 2 3 8464 Figure 79 External Interfaces, RAU1 and RAU2 Mechanical Design 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 105 Technical Description 4.5.3 RAU Types A RAU is designated as RAUX Y F, for example RAU2 N 23. When ordering, additional information about frequency sub-band and output power version is necessary. The letters have the following significance: • X indicates mechanical design 1 or 2. • Y indicates MMU compatibility as follows: 0 0 0 • 4.5.4 "blank", for example RAU2 23, indicates compatibility with a C-QPSK MMU. N or X, for example RAU2 N 23, indicates compatibility with a C-QPSK MMU and a QAM MMU. Xu for example RAU2 Xu 23, indicates compatibility with a C-QPSK MMU but it can also be upgraded by a Soft Key to be compatible with a QAM MMU. F indicates frequency band. Functional Blocks This section describes the RAU internal and external functions based on the block diagrams in and Figure 81. 106 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Transmit IF Signal Processing Power Amplifier Secondary Voltages RF Loop Cable Interface MMU DC/DC Converter Transmit RF Oscillator Receive RF Oscillator Receive IF Oscillator Downconverter 2 Filter and Amplifier Downconverter 1 Branching Filter DC Transmit IF Demodulator Antenna Low Noise Amplifier Received Signal Strength Indicator RCC Control and Supervision Processor Alarm and Control Alignment Port 6623 Figure 80 Block Diagram for RAU1 and RAU2 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 107 Technical Description Transmit IF Oscillator Transmit IF Signal Processing Cable Interface DC/DC Converter MMU Filter and Amplifier Upconverter 2 Power Amplifier Secondary Voltages RF Loop Receive RF Oscillator Receive IF Oscillator Downconverter 2 Filter and Amplifier Downconverter 1 Branching Filter DC Upconverter 1 Transmit RF Oscillator Antenna Low Noise Amplifier Received Signal Strength Indicator RCC Control and Supervision Processor Alarm and Control Alignment Port 6624 Figure 81 4.5.4.1 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. 108 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.5.4.2 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. 4.5.4.3 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. 4.5.4.4 Transmit IF Oscillator The frequency of the transmitter is controlled in a Phase Locked Loop (PLL), including a Voltage Control Oscillator (VCO). An unlocked VCO loop generates a transmitter frequency alarm. 4.5.4.5 Up-converter 1 The first up-converter gives an IF signal of approximately 2 GHz. 4.5.4.6 Filter and Amplifier The converted signal is amplified and fed through a bandpass filter. 4.5.4.7 Transmit RF Oscillator This oscillator is implemented in the same way as the Transmit IF Oscillator. 4.5.4.8 Up-converter 2 The transmit IF signal is amplified and up-converted to the selected radio transmit frequency. 4.5.4.9 Power Amplifier 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 MINI-LINK Craft. 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. 4.5.4.10 RF Loop 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 109 Technical Description 4.5.4.11 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. 4.5.4.12 Low Noise Amplifier The received signal is fed from the input branching filter into a Low Noise Amplifier. 4.5.4.13 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. 4.5.4.14 Down-converter 1 The first down-converter gives an IF signal of approximately 1 GHz. 4.5.4.15 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. 4.5.4.16 Down-converter 2 The signal is down-converted a second time to the IF of 140 MHz. 4.5.4.17 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). 4.5.4.18 Control and Supervision Processor The Control and Supervision Processor has the following main functions: • 110 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.5.4.19 • 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 111 Technical Description 4.6 Antennas 4.6.1 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 standardized waveguide interface. The feed can be adjusted for vertical or horizontal polarization. All high performance antennas have an integrated radome. 4.6.2 Installation 4.6.2.1 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). GHz 15 GHz 15 15 15 GHz GHz 15 GHz 15 GHz POWER ALARM POWER ALARM NT ALIGNME POWER ALARM NT ALIGNME RADIO CABLE NT ALIGNME RADIO CABLE RADIO CABLE 8459 Figure 82 0.2 m, 0.3 m and 0.6 m Compact Antennas Integrated with RAU2 AGC AGC RADIO RADIO ALARM CABLE POWER RADIO RADIO ALARM CABLE POWER 6716 Figure 83 112 0.3 m and 0.6 m Compact Antennas Integrated with RAU1 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link For a 1+1 configuration the RAU2 can be fitted directly to an Integrated Power Splitter (IPS). A similar solution is available for RAU1, using a waveguide between the power splitter and the antenna. An asymmetrical power splitter is mainly used for 1+1 hot standby configurations, that is, hardware protection only. The IPS provides one main channel with low attenuation and one standby channel with higher attenuation. A symmetrical power splitter is mainly used for 1+1 working standby or 2+0 configurations, that is, hardware protection and frequency diversity. The IPS provides equal attenuation in both channels. 15 GH z 15 GHz RADIO CABL E ALAR M POW ER ALIGN MENT RADIO 2 RAU1 Figure 84 RAU2 8500 RAUs Fitted to Integrated Power Splitters The 0.3 m and 0.6 m Integrated dual polarized antennas is used with two RAU2s and works perfect in combination with XPIC, see Section 4.2.2.12 on page 99. 4.6.2.2 Separate Installation All antennas have a standardized waveguide interface and can be installed separately, by using a flexible waveguide to connect to the RAU. The 1.2–3.7 m dual polarized antennas and the 2.4–3.7 m single polarized antennas are always installed separately. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 113 Technical Description 8454 Figure 85 4.6.3 Separate Installation in a 1+0 Configuration 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 50–120 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. 6717 Figure 86 Mounting Kit for the 0.2 m Antenna The 0.2 m compact antenna mounting kit can be adjusted by ±13 in elevation and by ±90 in azimuth. 114 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 6718 Figure 87 Mounting Kit for the 0.3 m and 0.6 m Antennas The mounting kit for 0.3 m and 0.6 m compact antenna can be adjusted by ±15 in elevation and ±40 in azimuth. Both elevation and azimuth have a mechanism for fine adjustment. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 115 Technical Description 4.7 1+1 Protection 4.7.1 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 6654 Figure 88 Radio Link Protection Modes For information specific for XPIC, Section 4.8.2 on page 121. 4.7.2 Functional Description The following different protection cases can be identified: 116 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.7.2.1 • 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 89. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 117 Technical Description PCI TDM Multiplexer/ Demultiplexer TDM TA Switch MMU A Radio Frame Multiplexer Control and Supervision Modulator Cable Interface RAU A Tx On/Off (Hot Standby) RCC TDM Tx Switch BPI MMU B TA Switch TDM Multiplexer/ Demultiplexer Radio Frame Multiplexer Control and Supervision Modulator Cable Interface RCC RAU B Tx On/Off (Hot Standby) NPU Node Processor 6666 Figure 89 4.7.2.2 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 89. 4.7.2.3 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. 118 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 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 90. TDM PCI MMU A Modulator Diversity Switch TDM Multiplexer/ Demultiplexer BPI Switch Logic Control and Supervision BPI Switch Logic Control and Supervision TDM Rx Switch RAU A Cable Interface Radio Frame Multiplexer MMU B RAU B Cable Interface TDM Multiplexer/ Demultiplexer Modulator Radio Frame Multiplexer Diversity Switch NPU Node Processor 6667 Figure 90 4.7.2.4 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 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 119 Technical Description 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 90. 120 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 4.8 Cross Polarization Interference Canceller (XPIC) 4.8.1 1+0 XPIC Configuration The 1+0 XPIC Radio Link configuration consists of four MMU2 F 155 or MMU2 H with XPIC capability, four RAUs, and two integrated dual-polarized antennas or four separate antennas. It is possible to set up a 1+0 XPIC Radio Link configuration consisting of two MMU2 H and two MMU2 F 155. MMU2 H and MMU2 F 155 can be used in an XPIC pair, but not be part of the same Radio Link. Near-end Node Far-end Node f 1 , VA MMU2 F 155 MMU2 F 155 f 1 , HA MMU2 F 155 MMU2 F 155 XPIC cross-cable XPIC cross-cable 11827 Figure 91 1+0 XPIC Configuration with MMU2 F 155 Two MMU2 F 155 or MMU2 H are housed in the AMM 2p B, AMM 6p C/D or AMM 20p B. The modems are connected through the front panel XPIC cross-cable. Note: To facilitate future expansions, for example if 1+1 protection is added, it is recommended to install the modems in adjacent slots. See Section 4.8.2 on page 121, for more information. 4.8.2 1+1 Protection with XPIC for SDH (MMU2 F 155) 4.8.2.1 Subrack Configurations The protected 1+1 XPIC Radio Link configuration consists of eight MMU2 F 155 with XPIC capability, eight RAUs, and four integrated dual-polarized antennas or eight separate antennas. See Figure 92. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 121 Technical Description 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 9966 Figure 92 1+1 XPIC Configuration Four MMU2 F 155 are housed in the AMM 6p C/D or the AMM 20p B, in four adjacent slots that share the same BPI-4 bus. See Figure 93. PFU2 0 FAU2 AMM 6p NPU 7 APU 6 MMU2 F 155 5 MMU2 F 155 1+1 MMU2 F 155 XPIC 4 MMU2 F 155 2 3 1 0/1 2 1+1 XPIC 3 4 6 7 8 9 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 APU MMU2 F 155 NPU APU 1+1 XPIC 1+1 XPIC 5 NPU MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 MMU2 F 155 PFU1 PFU1 MMU2 F 155 AMM 20p 1+1 XPIC 10 11 12 13 14 15 16 17 18 19 20 21 9967 Figure 93 AMM 6p and AMM 20p in 1+1 XPIC Configuration Each pair of modems placed in adjacent BPI-2 sharing slots (for AMM 20p B, 2&3 and 4&5, 6&7 and 8&9, etc.) is related to the same polarization of the transmitted signal. Therefore, the front panel XPIC cross-cable shall connect modems in alternate slots (2&4 and 3&5, etc.). See Figure 94. 122 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link 0 FAU2 PFU2 AMM 6p NPU 7 APU 6 MMU2 F 155 5 MMU2 F 155 1+1 MMU2 F 155 XPIC 4 MMU2 F 155 2 3 1 9968 Figure 94 4.8.2.2 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 with XPIC. Configurations for 1+1 XPIC protection can be in either hot standby (see Figure 95) or working standby (see Figure 96). Near-end Node Active Far-end Node f1, VA Active MMU2 F 155 MMU2 F 155 f1, VB MMU2 F 155 MMU2 F 155 f1, HA Active Active XPIC cross-cables MMU2 F 155 MMU2 F 155 f1, HB MMU2 F 155 MMU2 F 155 9969 Figure 95 1+1 XPIC in Hot Standby 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 123 Technical Description Near-end Node Active Far-end Node f1, VA Active MMU2 F 155 MMU2 F 155 f2, VB MMU2 F 155 MMU2 F 155 f1, HA Active Active XPIC cross-cables MMU2 F 155 MMU2 F 155 f2, HB MMU2 F 155 MMU2 F 155 9970 Figure 96 1+1 XPIC in Working Standby In both schemes the V (H) polarized branch labeled B protects the V (H) polarized branch labeled A, and vice versa if revertive mode is disabled 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, for example V, and the switching criteria are satisfied, the switching to the protection link is initiated, from VA to VB. 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 HA to HB, 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 HA to HB, is initiated. A hardware 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 6 summarizes the consequent actions to a fault on V-polarization link. 124 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Table 6 Fault Handling on a V-polarization Link Working Standby Vertical Polariz ation Hot Standby Horizontal Polarization Vertical Polari zation Horizontal Polarization Tx side Rx side Tx side Rx side Tx side Rx side Tx side Rx side Starting condition f1-VA and f2-VB f1-VA f1-HA and f2-HB f1-HA VA VA HA HA VA Tx fault handling N.A. f2-VB, disruption accepted N.A. f1-HA or VB f2-HB, disruptio n accepte d VA or VB No (quickest actio locked-in), n disruption accepted HA or HB (quickest locked-in), disruption accepted VA Tx fault handling N.A. f2-VB, disruption accepted N.A. f1-HA or N.A. f2-HB, disruptio n accepte d VB , disruption accepted N.A. HA or HB, disruption accepted VA propag a-tion fault handling N.A. f2-VB, hitless N.A. f1-HA or f2-HB, hitless VB, hitless N.A. HA or HB, hitless N.A. 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.8.3 1+1 with XPIC for PDH, Ethernet and ATM (MMU2 H) 4.8.3.1 Subrack Configurations The protected 1+1 XPIC Radio Link configuration consists of eight MMU2 H with XPIC capability, eight RAUs, and four integrated dual-polarized antennas or eight separate antennas. See Figure 97. It is possible to set up a 1+1 XPIC Radio Link configuration consisting of four MMU2 Hs and four MMU2 F 155s, and the outdoor equipment specified above. However, an MMU2 H can only protect another MMU2 H, and an MMU2 F 155 can only protect another MMU2 F 155. This must be considered when installing the MMUs since they can be part of the same Radio Terminal but not part of the same Radio Link. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 125 Technical Description MMU2 H + MMU2 F MMU2 H ML TN ML TN ML TN ML TN MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 F 155 MMU2 F 155 MMU2 H MMU2 H MMU2 F 155 MMU2 F 155 12301 Figure 97 1+1 XPIC Configuration Four MMU2 H, or two MMU2 Hs and two MMU2 F 155s, are housed in the AMM 6p C/D or the AMM 20p B, in four adjacent slots that share the same BPI-4 bus. See Figure 98. MMU2 H MMU2 H 03 1+1 XPIC 1+1 XPIC 1+1 XPIC MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H MMU2 H NPU MMU2 H MMU2 H MMU2 H MMU2 H 04 MMU2 H 05 1+1 XPIC MMU2 H MMU2 H MMU2 H 06 MMU2 H PFU1 07 MMU2 H NPU PFU1 PFU3 B 08 FAU2 PFU3 B MMU2 H AMM 20p B AMM 6p C 01 1+1 XPIC 02 MMU2 F 155 MMU2 F 155 6 7 8 9 MMU2 F 155 5 03 10 11 12 13 14 15 16 17 18 19 20 21 1+1 XPIC 1+1 XPIC 1+1 XPIC MMU2 F 155 MMU2 F 155 MMU2 H MMU2 F 155 MMU2 H MMU2 F 155 MMU2 H MMU2 H NPU MMU2 F 155 04 MMU2 H PFU1 05 1+1 XPIC MMU2 H MMU2 H MMU2 F 155 MMU2 H MMU2 H 07 PFU1 PFU3 B NPU 06 FAU2 PFU3 B MMU2 H + MMU2 F 08 4 AMM 20p B AMM 6p C 01 3 MMU2 H 0/1 2 MMU2 F 155 00 1+1 XPIC 02 00 0/1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 12302 Figure 98 AMM 6p C and AMM 20p B in 1+1 XPIC Configuration Each pair of modems placed in adjacent BPI-2 sharing slots (for AMM 20p B, 2&3 and 4&5, 6&7 and 8&9, etc.) is related to the same polarization of the transmitted signal. Therefore, the front panel XPIC cross-cable shall connect modems in alternate slots (2&4 and 3&5, etc.). See Figure 99. 126 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link MMU2 H MMU2 H + MMU2 F 01 07 PFU3 B NPU 06 05 MMU2 H MMU2 H 1+1 XPIC MMU2 H 04 PFU3 B MMU2 H 03 02 00 08 NPU 07 06 FAU2 08 FAU2 PFU3 B PFU3 B 01 05 MMU2 H MMU2 H MMU2 F 155 MMU2 F 155 1+1 XPIC 04 03 02 00 12303 Figure 99 4.8.3.2 XPIC Cross-Cable Connections for AMM 6p C Functional Description The 1+1 XPIC configuration provides propagation protection and equipment protection on the MMU, RAU and antenna when using both polarizations in CCDP mode with XPIC. Configurations for 1+1 XPIC protection can be in either hot standby (see Figure 100 and Figure 101) or working standby (see Figure 102 and Figure 103). Near-end Node Active Far-end Node f1, VA Active MMU2 H MMU2 H f1, VB MMU2 H MMU2 H f1, HA Active Active MMU2 H MMU2 H XPIC cross-cables f1, HB MMU2 H MMU2 H 11752 Figure 100 1+1 XPIC in Hot Standby, MMU2 H 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 127 Technical Description Near-end Node Active Far-end Node f1, VA Active MMU2 H MMU2 H f1, VB MMU2 H MMU2 H f1, HA Active Active MMU2 F 155 MMU2 F 155 XPIC cross-cables f1, HB MMU2 F 155 MMU2 F 155 12304 Figure 101 1+1 XPIC in Hot Standby, MMU2 H and MMU2 F 155 Near-end Node Active Far-end Node f1, VA Active MMU2 H MMU2 H f2, VB MMU2 H MMU2 H f1, HA Active Active MMU2 H MMU2 H XPIC cross-cables f2, HB MMU2 H MMU2 H 11753 Figure 102 128 1+1 XPIC in Working Standby, MMU2 H 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Near-end Node Active Far-end Node f1, VA Active MMU2 H MMU2 H f2, VB MMU2 H MMU2 H f1, HA Active Active MMU2 F 155 MMU2 F 155 XPIC cross-cables f2, HB MMU2 F 155 MMU2 F 155 12305 Figure 103 1+1 XPIC in Working Standby, MMU2 H and MMU2 F 155 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, for example V, and the switching criteria are satisfied, the switching to the protection link is initiated, from VA to VB. 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 HA to HB, 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 HA to HB, is initiated. A hardware 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 7 summarizes the consequent actions to a fault on V-polarization link. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 129 Technical Description Table 7 Fault Handling on a V-polarization Link Working Standby Vertical Polariz ation Hot Standby Horizontal Polarization Vertical Polari zation Horizontal Polarization Tx side Rx side Tx side Rx side Tx side Rx side Tx side Rx side Starting condition f1-VA and f2-VB f1-VA f1-HA and f2-HB f1-HA VA VA HA HA VA Tx fault handling N.A. f2-VB, disruption accepted N.A. f1-HA or VB f2-HB, disruptio n accepte d VA or VB No (quickest actio locked-in), n disruption accepted HA or HB (quickest locked-in), disruption accepted VA Tx fault handling N.A. f2-VB, disruption accepted N.A. f1-HA or N.A. f2-HB, disruptio n accepte d VB, disruption accepted N.A. HA or HB, disruption accepted VA propag a-tion fault handling N.A. f2-VB, hitless N.A. f1-HA or f2-HB, hitless VB, hitless N.A. HA or HB, hitless N.A. 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.9 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. 130 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Radio Link Transmit power Pmax PATPC max Pset Pout Pout Pfix min PATPC min RTPC mode ATPC mode 5647 Figure 104 4.9.1 Transmit Power Control RTPC Mode In RTPC mode the transmit power (Pout) ranges from a minimum level (Pfix min) to a maximum level (Pmax). The desired value (Pset) can be set in 1 dB increments. 4.9.2 ATPC Mode ATPC is used to automatically adjust the transmit power (Pout) 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 (PATPC max) and a hardware specific minimum level (PATPC min). It is possible to enable a fallback mode for the ATPC, so that the transmitted power is decreased to a user settable level (PATPC, Fallback) if it has been stuck at PATPC, max for too long. The ATPC fallback can be enabled using MINI-LINK Craft. When fallback is done an alarm is raised and is not cleared as long as the system is in ATPC mode. PATPC, Fallback can be set between PATPC, max and PATPC, min. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 131 Technical Description 4.10 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. 5 Management The management functionality described in this section can be accessed from the management tools and interfaces as described in Section 5.8 on page 150. Shortly these are: 132 • MINI-LINK Craft for local O&M • ServiceOn Element Manager (SO EM) for remote O&M • ServiceOn Network Manager (SO NM) for end-to-end traffic management • ServiceOn Ethernet Service Activator (SO ESA) for Ethernet service management • Simple Network Management Interface (SNMP) 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management 5.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. 5.1.1 Alarm Handling MINI-LINK TN R4 uses SNMP traps to report alarms to ServiceOn Microwave 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 MINI-LINK Craft. 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 systems. 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: • 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 for an E1 on the NPU. • Event time: time when alarm/event was generated. • Event type: X.73x compliant alarm/event type like communications alarm and equipment alarm. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 133 Technical Description • 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). Alarm and event notifications can also be sent to (up to 3) syslog servers in the network. The information content is the same as for the SNMP traps. The messages use a fixed syslog facility of LOG_LOCAL6 and severity mapping and message text is based on RFC 5674 - Alarms in syslog. For a full description of alarms see user documentation. 5.1.2 Ethernet Link OAM Ethernet Link OAM supports fault management on Ethernet links according to IEEE 802.3ah and provides link monitoring, fault notification and loopback test. Note: Ethernet Link OAM is only supported for LAN interfaces (Layer 1 Connection and Layer 2). The three main Ethernet Link OAM areas are described below. Failure Notification Notification of an Ethernet link failure to or from far end for an NE in operation. The following three types of failures are supervised: • Link fault (RDI) The Link fault (RDI) alarm is generated when a failure in a physical layer has occurred in the receiving direction. • Dying gasp The Dying gasp alarm is generated when a plug-in unit is about to restart or is going to operational state Down. This occurs when an unrecoverable failure has occurred. Note: • Only supported in receiving direction (an event is raised). Critical event The Critical event event is generated when an unspecified critical event has occurred. 134 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management Note: Only supported in receiving direction (an event is raised). Link Monitoring Link monitoring is used for event notification on errored frames at both near and far end and is used on NEs in operation. The notifications are based on a threshold crossing within a specific time window. The following events are reported: • Errored Symbol Period Event Generated when the number of symbol errors exceeds a threshold in a given time window, which is defined by a number of symbols. • Errored Frame Event Generated when the number of errored frames exceeds a threshold in a given window, which is defined by a period of time. • Errored Period Event Generated when the number of errored frames exceeds a threshold in a given window, which is defined by a number of frames. • Errored Frame Seconds Summary Event Generated when the number of errored frame seconds exceeds a threshold in a given time period. An errored frame second is defined as a 1 second interval with one or more frame errors. Remote Loopback Link OAM remote loopback can be used for fault localization and link performance testing on LAN interfaces. Statistics from both near end and far end NE can be requested and compared at any time while the far end NE is in O&M remote loopback mode. The requests can be sent before, during, or after loopback frames have been sent to the far end NE. The loopback frames in the O&M sublayer can be analyzed to determine which frames are being dropped due to link errors. 5.1.3 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 units with E1/TDM bus connection: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 135 Technical Description 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 105. 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). Line 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 105. An AIS is sent to the TDM bus. A Line Loop in combination with a BERT in an adjacent NE is 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. Local Loop Loops a line signal received from the TDM bus back to its origin, see Figure 105. 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, Figure 105. An Rx Loop can be used on the far-end MMU to verify the communication over the radio path, see Figure 106. In the MMU2 E/F the RX Loop applies to the wayside E1 traffic. 136 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management nxE1 Plug-in unit TDM Bus AIS Line Loop AIS nxE1 Plug-in unit Connection Loop Rx Loop* nxE1 Plug-in unit AIS Local Loop Backplane * MMU Only Figure 105 11861 Loops 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 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). RF Loop In the RAU, a fraction of the RF signal transmitted is shifted in frequency and looped back to the receiving side. IF Loop MMU RF Loop RAU Near-end Rx Loop RAU MMU Far-end Note: For MMU2 E/F, also a Local Loop is available at the Far-end MMU. 9971 Figure 106 Radio Link Loops 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 137 Technical Description The AAU supports a Loopback function described in Section 3.9.2.2 on page 62. Remote Loopback Loops Ethernet traffic between two adjacent NEs, connected via a LAN interface, and is used for fault localization and link performance testing of Ethernet links. It is available on Ethernet traffic units with support for Ethernet Link OAM. Remote loopback can only be performed on LAN interfaces. 5.1.4 User Input/Output NPU1 B and NPU1 C provides three User Input and three User Output ports. The NPU3 and NPU3 B provides two User Output ports. The SAU3 provides six User In ports and three User Out ports. The User Input ports can be used to connect user alarms to MINI-LINK Craft. 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 MINI-LINK Craft. 138 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management 5.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 and SSH, and adding new SNMP users • Radio Terminal parameters, such as frequency, output power, ATPC and protection 5.3 Performance Management 5.3.1 General MINI-LINK TN R4 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 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: 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 139 Technical Description • Performance counters for Ethernet traffic are described in Section 3.7.9 on page 51. • Performance data for the Radio Terminal is described in Section 4.10 on page 132. Performance data is stored in a volatile memory, so that a restart will lose all gathered data. 5.3.2 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 215–1 is sent through the selected interface. As with loop tests, bit error testing may be used for system verification or for fault location. NE or External equipment Plug-in Unit E1 BERT TDM Bus 6668 Figure 107 BERT in Combination with an External Loop 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: 140 • One BERT per plug-in unit • One BERT on a protected 1+1 E1 SNCP interface per NE 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management Note: BERT is not valid for MMU2 E/F. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 141 Technical Description 5.4 Security Management All management access to the MINI-LINK TN R4 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 MINI-LINK Craft or the SNMP v3 interface. The following security mechanisms are used on the various O&M interfaces: 142 • Local and remote MINI-LINK Craft 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 MINI-LINK Craft 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 MINI-LINK Craft. • Secure Shell (SSH) protocol can be used for more secure remote access and use of CLI commands. The SSH protocol is enabled together with the Telnet protocol, using MINI-LINK Craft. When both protocols are enabled the operator can choose to use Telnet or the more secure SSH protocol. The SSH protocol is supported with the Security Software Package. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management 5.5 License Management Up to MINI-LINK TN R2 licenses were registered centrally on a per-customer basis. Keeping track of actual use of optional features can therefore be difficult in large networks. To give better support for license handling Ericsson has introduced license keys bound to individual NEs in MINI-LINK TN R3, that is, node-bound license keys. When the software in an NE is upgraded from MINI-LINK TN release R2 to release R3 or R4, the existing license keys must be migrated to the new license system. All NEs have a baseline of features that are available without licenses, depending on which plug-in units are installed. If the installed NPU is equipped with a Removable Memory Module (RMM), the set of optional features can be expanded by installing license keys that enables additional optional features. Licenses for optional features are distributed in a License Key File (LKF), which can be stored on the RMM in those NEs where additional functionality is required. In MINI-LINK TN R3 and R4 warnings will be issued to show where optional features are used without sufficient licenses. License warnings can be removed by purchasing and installing a license key for the feature in question. Future releases of MINI-LINK TN may include new licensing behavior, which will be announced well in advance. The license key installation can be made both locally and remotely, without disturbing the traffic through the NE. License keys can also be preinstalled at delivery, when a complete and preconfigured NE is purchased. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 143 Technical Description 5.6 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. An FTP server is also embedded in MINI-LINK Craft and can be enabled via the Tools/FTP Server option. The MINI-LINK TN R4 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 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 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. When switching to a system release with SSH, a product number switch will be performed. Once a migration to a system release with SSH has been made, additional software upgrades do not involve a product number switch. 5.7 Data Communication Network (DCN) This section covers the DCN functions provided by MINI-LINK TN R4. The MINI-LINK DCN Guidelines, Reference [5] gives recommendations on DCN implementation, covering the different MINI-LINK product families. 5.7.1 IP Services The following standard external IP network services are supported: • 144 All clocks, used for example for time stamping alarms and events, can be synchronized with a Network Time Protocol (NTP) server. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management • 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. • Syslog is used to forward log messages in the network and log alarms and events to a central syslog server. MINI-LINK TN NTP 08/FAU2 PFU3 FAU2 01/PFU3 07/NPU NPU1 B 06 LTU 16x2 DCN 05 LTU 155e/o PFU3 04 MMU2 B 4-34 03 00/PFU3 SMU2 02 LTU 155e FTP Site LAN DNS MINI-LINK Craft DHCP 10056 Figure 108 5.7.2 IP Services DCN Interfaces MINI-LINK TN R4 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 109 illustrates the different options, including ways of connecting to the equipment for DCN configuration. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 145 Technical Description DCCR/DCCM Router Structured/Unstructured E1 nx64 kbit/s PPP DCN over VLAN (NPU3 B/NPU1C only) 10/100BASE-T 2xE0 USB DCC Radio Terminal 12191 Figure 109 DCN Interfaces The internal IP traffic is transported on nx64 kbps channels on the TDM bus in the backplane. The internal channels are automatically established at power up. 5.7.2.1 DCN in SDH 1-9 1-3 4 10-274 RSOH AU Pointers Payload + RFCOH 4665 5-9 MSOH 4665 Figure 110 Frame The following channels can be used for DCN transportation in SDH: 146 • 128 kbps default proprietary channel available on radio side only (2×64 kbps in the RFCOH). • 192 kbps channel available on line side and radio side by using EOC or DCC bytes of the Regenerator Section Overhead Frame (RSOH) of the SDH Frame. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management 5.7.2.2 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. For LTU 155 the default bandwidth is automatically established to DCCr=192 kbps and DCCm=192 kbps and DCCm is configurable to 384 kbps and 576 kbps. SXU3 B supports the standard compliant DCCr and DCCm. The bandwidth is fixed to DCCr=192 kbps and DCCm=576 kbps. Between LTU 155 and SXU3 B only DCCr can currently be used due to DCCm compatibility issues. This will be corrected in future release. 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. DCCm can be used to connect MINI-LINK TN R4 to MINI-LINK TN R4 over an STM-1 connection. Please note that for this connection there can be no multiplexer between the two MINI-LINK TN R4 NEs. 5.7.2.3 Structured/Unstructured E1 MINI-LINK TN R4 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 kbps 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 Mbps is used for DCN transport. • E1 with traffic pass-through In a structured E1 used for traffic, nx64 kbps timeslots can be used for DCN transport. The DCN is inserted into the nx64 kbps timeslots internally in the NE. The timeslots used for traffic is cross-connected in normal manner through the NE. 5.7.2.4 nx64 kbps nx64 kbps timeslots can be used for IP DCN as described in Section 5.7.2.3 on page 147. 5.7.2.5 2xE0 A PPP/E0 connection can be established to an external device from the SMU2. 5.7.2.6 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 147 Technical Description 5.7.2.7 10/100BASE-T Each NE has a 10/100BASE-T Ethernet interface for connection to a site LAN. This interface offers a high speed DCN connection. The interface is also used at sites holding MINI-LINK HC and MINI-LINK E with SAU IP(EX). 5.7.2.8 USB The USB interface is used for a MINI-LINK Craft connection using a local IP address. 5.7.2.9 DCN over VLAN On NPU1 C and NPU3 B the management traffic can be transported in a logically separated VLAN together with the Ethernet traffic. An internal switch port in MINI-LINK TN forwards the management traffic to the IP DCN router. 5.7.3 IP Addressing MINI-LINK TN R4 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: 5.7.4 • 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: • 148 Open Short Path First (OSPF), which is normally used for routers within the MINI-LINK domain. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management • Static routing There are two different ways to configure the IP router. The idea is that the most common configurations are done using the MINI-LINK Craft. When complex router configuration and troubleshooting is required, a Command Line Interface (CLI) is used, see Section 5.8.6 on page 153. 5.7.4.1 Open Shortest Path First Features The following summarizes the (Open Shortest Path First ) OSPF features: • An NE can be a part of a non-stub area, stub area or totally stub area. • An NE can act as an Internal Router (IR) or an Area Border Router (ABR). • Virtual links are supported, which is useful when an area needs to be 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. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 149 Technical Description 5.8 Management Tools and Interfaces This section gives a brief overview of the management tools and interfaces used for MINI-LINK TN R4. ServiceOn Element Manager ServiceOn Network Manager/ServiceOn Ethernet Service Activator SNMP SNMP MINI-LINK TN Mobile Network OSS/NMS 08/FAU2 PFU3 SNMP FAU2 01/PFU3 07/NPU NPU1 B 06 LTU 16x2 LTU 155e/o DCN 05 PFU3 04 03 00/PFU3 SMU2 MMU2 B 4-34 02 LTU 155e Site LAN MINI-LINK E MINI-LINK Craft 10057 Figure 111 5.8.1 Management Tools and Interfaces MINI-LINK Craft MINI-LINK Craft 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. MINI-LINK Craft is used for local management, that is the NE is accessed locally by connecting a PC to the NPU, with a USB cable. On MMU2 CS, the NE is accessed locally by connecting a PC to the MMU2 CS, using an Ethernet cable. The NE can also be accessed over the site LAN or remotely over the DCN. A thorough description of MINI-LINK Craft is available as online help and in the MINI-LINK Craft User Guide, Reference [3]. 150 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management Figure 112 5.8.2 MINI-LINK Craft ServiceOn Element Manager MINI-LINK TN R4 is managed remotely using ServiceOn Element Manager. ServiceOn Element Manager 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 Element Manager can also be used to mediate FM, PM and Inventory data to other management systems. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 151 Technical Description The system provides: • Fault Management • Configuration Management • Performance Management • Security Management • Remote Software Upgrade ServiceOn Element Manager 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 Element Manager 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. 5.8.3 ServiceOn Network Manager ServiceOn Network Manager (SO NM) provides network management functionality to support circuit management and service provisioning. In the MINI-LINK network it is mainly the PDH Layer feature implemented on the SO NM product that is used in order to manage Microwave Radio network elements at the network management layer. The PDH Layer feature covers the functional areas of Configuration, Fault, Performance and Security Management. SO NM can manage the possible network scenarios: 5.8.4 • Only Microwave Network Elements • Microwave Network Elements inter-worked with SDH Optical Network Elements ServiceOn Ethernet Service Activator The ServiceOn Ethernet Service Activator (SO ESA) system is a network management level application providing operators with the ability to support the end to end configuration and management of Ethernet services on packet enabled Ericsson transport products. The SO ESA management application supports Integration with ServiceOn Element Manager for equipment level management and feature discovery. 5.8.5 SNMP Each NE provides an SNMP agent enabling easy integration with any SNMP based management system. The SNMP agent can be configured to support 152 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Management 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. 5.8.6 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 or SSH. The CLI functions are described in the online Help and the CLI User Guide, Reference [1]. Figure 113 CLI CLI Tool MINI-LINK CLI Tool makes it possible for a planning engineer to prepare a set of CLI commands in a standard text file, which can later be run on-site on a newly installed MINI-LINK node. For more information on creating these files, see Preparing a CLI Script File Offline. MINI-LINK CLI Tool is an application that runs on a field technician’s PC. This PC is connected through a USB cable to a MINI-LINK node that is being deployed. CLI Tool is not part of MINI-LINK Craft and does not interact with it, but MINI-LINK Craft may be used together with CLI Tool. The rest of this section gives details about installation and the CLI Tool user interface. For more information on using CLI Tool, see Transferring a CLI Script File to a MINI-LINK TN, Reference [10]. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 153 Technical Description 5.8.7 Syslog Logging of alarms and events to syslog servers can be managed through the DCN configuration in MINI-LINK Craft and MINI-LINK CLI Tool. 6 Accessories The MINI-LINK TN R4 product program contains a comprehensive set of accessories for installation and operation. This section gives additional technical information for some accessories. 6.1 Interface Connection Field (ICF) MINI-LINK TN R4 uses Sofix connectors for 120 E1 traffic connections on the plug-in units in the subrack. Sofix is a high-density connector holding four E1s per connector. It is optimized to occupy minimal space on the plug-in unit fronts, which enables very compact site solutions. D-sub connectors are used for connection of power supply and User I/O. For further details on connectors, see MINI-LINK TN ETSI Product Specification and Installing Indoor Equipment, Reference [2]. Instead of connecting directly to the front of the units in the subrack, an Interface Connection Field (ICF) can be used. It provides a panel with connectors and pre-assembled cables to be connected to the units. The use of an ICF enables easy on-site installation and flexibility, with a minimum of impact when reconfiguring traffic cables. The following types of ICF are available: 154 ICF1 The ICF1 is used for AMM 20p B. It provides connectors for E1 traffic (D-sub 120 or SMZ 75 ), redundant power supply of PFU1 and FAU1, User I/O, and fuses for FAU1, see Figure 114. ICF2 The ICF2 is used for AMM 6p C/D. It provides connectors for E1 traffic (D-sub 120 or SMZ 75 ) and User I/O, see Figure 115. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Accessories ICF 16x2 The ICF 16x2 can be used for any subrack. It provides connectors for E1 traffic (D-sub 120 or SMZ 75 ), see Figure 116. ICF3 The ICF3 can be used for any subrack. It provides connectors for E1 traffic (BNC 75 or Siemens 1.6/5.6 75 ). ICF3 has a modular design with a frame with room for up to four connection boxes, each one with a specific cable connecting to the plug-in unit (Sofix), see Figure 117. The ICF fits in standard 19" or metric racks. The following figures show examples of the different ICF types and the number of connectors for each type. E1 -48 V DC IN E1 User I/O -48V DC + IN FAN 01 TRAFFIC E1 -48V DC + IN 3A 00 FUSE A FUSE B 3B 3C 3D 2A 2B USER I/O:1A 2C -1F 2D PFU1 User I/O 4xE1 FAU1 8495 Figure 114 ICF1 120 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 155 Technical Description E1 E1 User I/O TRAFFIC E1 3A 3B 3C 3D 2A 2B USER I/O:1A 2C -1F 2D User I/O 4xE1 8496 Figure 115 ICF2 120 E1 E1 E1 E1 IN 4A 4B 4C 4D OUT TRAFFIC E1 3A 3B 3C 3D 2A 2B 2C 2D 1A 1B 1C 1D 4xE1 8493 Figure 116 ICF 16x2 75 TRAFFIC E1 IN A OUT B C D 4xE1 E1 8494 Figure 117 156 ICF3 with frame, one connection box and connection cable (Sofix) 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Accessories 6.2 PSU DC/DC Kit The PSU DC/DC kit is used for AMM 6p C/D or AMM 20p B, converting +24 V DC to –48 V DC with a maximum output power of 950 W. It consists of a sub-rack (3U high), one or two Power Supply Units (PSU) and an FAU3. Two PSUs are used for redundant power systems. The +24 V DC external power supply is connected to the PSU front. The sub-rack provides two –48 V DC connectors for PFU connection. Two fused –48 V DC connectors for FAU1 connection are also available. The sub-rack can be mounted in a standard 19" or metric rack or on a wall using a dedicated mounting set. FAU3 +24 V DC In PSU –48 V DC Out (PFU1/PFU3) FAU3 0V -48VDC 0V Alarm 00 -48VDC DC Out –48 V DC Out (PFU1/PFU3) + DC In 3.15A 250V + Fault Power DC In EC Bus + + DC Out Fault Operation Information -48VDC Power EC Bus 0V 3.15A 250V Fault Operation Information GROUNDING PSU -48VDC B EARTH A –48 V DC Out (FAU1) 0V PSU 01 -48VDC OUT -48VDC Fan alarm (NPU1 B) 8261 Figure 118 6.2.1 PSU DC/DC Kit Cooling Forced air-cooling is always required and provided by FAU3, which holds two internal fans. It is power supplied by an internal pre-assembled cable connected to the front. A connector for alarm export to the NPU1 B and NPU1 C is also available. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 157 Technical Description Air out Air out -48VDC OUT FAU3 + + PSU B 01 Air out EARTH + PSU Air in + 00 A GROUNDING Air in Figure 119 6724 Cooling Airflow in the PSU DC/DC Kit The air enters at the front and gable on the right hand side of the sub-rack, flows past the plug-in units and exits at the rear, top and gable on the left hand side of the sub-rack. 158 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Accessories 6.3 Small Form Factor Pluggable For MMU2 E/F 155 the Small Form Factor Pluggable (SFP) exists as electrical (SFPe) or optical (SFPo) transmitter/receiver, see Figure 120. SFP Electrical (SFPe) Figure 120 SFP Optical (SFPo) 9694 Electrical/Optical SFP For NPU1 C, ETU2 B, and ETU3 the Small Form Factor Pluggable (SFP) exists as electrical (SFPe) or optical (SFPo) transmitter/receiver, see Figure 121. SFP GB-TX Electrical Figure 121 6.4 SFP GB-LX/ZX Optical 10054 Electrical/Optical SFP Optical splitter/combiner An optical splitter or combiner splits or combines the incoming/outgoing optical signal. It is used together with an optical SFP to form an EEP solution, see Section 3.11.5 on page 73. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 159 Technical Description 9358 Figure 122 6.5 Optical Combiner/Splitter DCN Site LAN Switch The DCN Site LAN Switch gives the possibility to connect up to 8 equipments to one DCN. The switch also provide IP-telephone connection through a Power over Ethernet port. The port is powered via the battery back-up for the site supporting the use of the EoW telephone (IP-telephone) when the ordinary AC power is down. The DCN Site LAN Switch runs on either +24 or -48 V DC. Full duplex P1 priority P1 manual P2-4 manual P5-8 manual 100 Mbps Up to two DCN Site LAN Switches fits in a standard 19" or metric rack. PWR PoE P1 ERICSSON P2 P3 PoE SEL HOLD TO CONFIRM P5 P4 P6 P7 P8 DLS 9467 P1 manual P2-4 manual P5-8 manual 100 Mbps DCN Site LAN Switch Full duplex P1 priority Figure 123 PoE P1 P2 P3 P4 ERICSSON P5 P6 P7 P8 PWR PoE SEL HOLD TO CONFI RM DLS 9466 Figure 124 160 DCN Site LAN Switch and 19” Rack 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Accessories 6.6 MPH for MINI-LINK TN The MPH for MINI-LINK TN is a slim, water protected outdoor casing, used to house an AMM 1p or AMM 2p B connected to an RAU with antenna. RAU DC Traffic 10055 Figure 125 MPH The MPH can be installed on a pole with a diameter of 50-120 mm or on a wall. The subrack is placed vertically inside the MPH, which provides cooling fins on the inside and the outside. A sun shield is placed on the MPH, in order to reduce the effects of solar radiation. For AMM 2p installations, the FAU inside the AMM 2p B helps cooling the MPH. The bottom of the MPH holds 7 cable bushings and two adapters for connection of the radio cables. One traffic cable and one DC cable are always fed while the remaining cable bushings can be used for different cables. Note: When installing an AMM 1p in an MPH, the 75 be used. User I/O cable cannot The front of the MPH is easily opened, to get access to the subrack and its PIUs. The subrack is power supplied by -48 V DC or +24 V DC, from an external DC supply source or an optional dedicated AC/DC converter (PSU). The PSU converts 100-250 V AC to -48 V DC. The maximum output power is 420 W. The PSU fulfills Over Voltage Category II, according to IEC60950. 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 161 Technical Description 10058 Figure 126 PSU The PSU supports the same mounting alternatives as the MPH. 6.7 TMR 9302 TMR 9302 can house 19” units, placed in a vertical position and the available space in the cabinet is 6U. It holds an AMM 6p C/D or AMM 2p B with plug-in units. It can be mounted on a pole with diameter of 50 - 120 mm or on a wall. Two eyebolts are included for hoisting. 00/PFU 01/PFU FAU PFU3 B 02 03 04 06 07 08 LTU3 12/1 SXU3 B LTU 155e ETU2 MMU2 E 155 MMU2 E 155 05 NPU3 10082 Figure 127 TMR 9302 The cabinet has two doors, one on the front and one on the back. Cooling of the equipment is done by a heat exchanger, including four fans. One internal air loop and one external air loop divides the outdoor air from the indoor air. Two indoor fans and two outdoor fans provide redundancy. The fans are power supplied by -48 V DC. 162 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Accessories The cabinet can be equipped with an optional heater, including a thermostat, for operation in cold environments. The heater is power supplied by -48 V DC. The bottom of the cabinet holds 12 cable bushings where DC and traffic cables can be feed. The bottom also holds five adapters for radio cable connection. A fan alarm can be used to detect cooling system malfunction. Furthermore, a door sensor is mounted in the cabinet, which can be used to generate an alarm when the lockable door is opened. The TMR 9302 is power supplied by -48 V DC, from an external DC supply source or an optional dedicated AC/DC converter (PSU). The PSU converts 100-250 V AC to -48 V DC, see Figure 126. The maximum output power is 420 W. The PSU fulfills Over Voltage Category II, according to IEC60950. The PSU supports the same mounting alternatives as the TMR 9302. 6.8 Engineering Order Wire Engineering Order Wire (EOW) is an embedded service telephone feature, consisting of an analog and a digital IP based domain, connected through a gateway (GW). EOW enables calls between different sites or to the Operation and Maintenance Center (OMC), without impact on traffic capacity. Analogue EOW GW Digital EOW Digital EOW GW Analogue EOW GW 11835 Figure 128 Engineering Order Wire 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 163 Technical Description 6.8.1 Analogue EOW The analog EOW solution is used in MINI-LINK E networks and uses the following communication channels: Radio service channel A digital service channel for EOW transport over a hop. EAC channel Two NEs on the same site are connected through the External Alarm Channel (EAC) port on the SAU exp.2. EOW traffic is sent locally. An analog EOW cluster is equivalent with a MINI-LINK E O&M cluster. This means that a network consisting of multiple O&M clusters have a matching number of EOW clusters. Each service telephone is configured with a unique phone number and is always connected to the other service telephones in the EOW cluster. 6.8.2 Digital EOW The digital EOW solution is based on VOIP technology and uses the IP DCN network for MINI-LINK E with SAU IP and MINI-LINK TN, to transport EOW traffic. The digital service telephone is connected to an Ethernet port and is part of the local IP subnet. Each digital service telephone is locally configured with an IP address and an associated phone number. 6.8.3 EOW Gateway An EOW GW is used to connect analog and digital EOW domains. In MINI-LINK E, the GW is connected to the analog EOW domain through SAU exp. In MINI-LINK TN, the GW is connected to the digital EOW domain through the site LAN or directly to the Ethernet port in one of the NEs. The EOW GW is configured with a unique number on the analog and digital side. The numbers are used to call an EOW service telephone in a different domain. 164 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Glossary Glossary AAU ATM Aggregation Unit CBR Constant Bit Rate ABR Area Border Router CC Continuity Check ADM Add Drop Multiplexer CLI Command Line Interface AFC Automatic Frequency Control CLP Cell Loss Priority AGC Automatic Gain Control CRC Cyclic Redundancy Check AIS Alarm Indication Signal DC Direct Current AMM Access Module Magazine DCC Data Communication Channel ASK Amplitude Shift Keying DCCm Digital Communication Channel, Multiplexer Section ATM Asynchronous Transfer Mode ATPC Automatic Transmit Power Control BER Bit Error Ratio BIP Bit Interleaved Parity BPI Board Pair Interconnect BR Board Removal C-QPSK Constant envelope offset - Quadrature Phase Shift Keying 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 DCCr Digital Communication Channel, Regenerator Section DCN Data Communication Network DDF Digital Distribution Frame DHCP Dynamic Host Configuration Protocol DNS Domain Name System DP Device Processor E0 PDH traffic at 64 kbps 165 Technical Description E1 PDH traffic at 2 Mbps (2 048 kbps) GSM Global System for Mobile Communications E2 PDH traffic at 8 Mbps (8 448 kbps) HCC Hop Communication Channel E3 PDH traffic at 34 Mbps (34 368 kbps) Hop A radio link connection with a pair of communicating terminals EAC External Alarm Channel EEP Enhanced Equipment Protection ELP Equipment and Line Protection EOW Engineering Order Wire EPD Early Packet Discard ETU Ethernet Interface Unit ES Errored Second ETSI European Telecommunications Standards Institute EW Early Warning Far-end The terminal with which the near-end terminal communicates FAU Fan Unit FEC Forward Error Correction FTP File Transfer Protocol GFP Generic Framing Procedure 166 HSDPA High Speed Downlink Packet Access HSUPA High Speed Uplink Packet Access HSPA High Speed Packet Access Hybrid Radio Link A radio link optimized for maximum throughput of Native Ethernet and Native PDH traffic. The functionality is supported by MMU2 D. Native Ethernet and Native PDH traffic are sent simultaneously over a Hybrid radio link. I/Q Inphase and Quadrature ICS Internet Connection Sharing ICF Interface Connection Field IEEE Institute of Electrical and Electronics Engineers IF Intermediate Frequency IMA Inverse Multiplexing for ATM IP Internet Protocol IPS Integrated Power Splitters 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Glossary IR Internal Router IRP Integrated Reference Point ITU International Telecommunication Union LAN Local Area Network LB Loop Back LCAS Link Capacity Adjustment Scheme LCD Loss of Cell Delineation LED Light Emitting Diode LKF License Key File LOC Loss Of Continuity LOS Loss Of Signal LTU Line Termination Unit MAC Media Access Control MDCR Minimum Desired Cell Rate MIB Management Information Base MINI-LINK E Product family for microwave transmission at 2x2 to 17x2 Mbps MINI-LINK HC Product family for microwave transmission at 155 Mbps 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 MINI-LINK TN R4 Product family for microwave transmission featuring comprehensive traffic handling functions MMU Modem Unit MPH MINI-LINK Protective Housing MPLS Multiprotocol Label Switching MS Multiplexer Section MSP Multiplexer Section Protection Native Ethernet Ethernet traffic is sent over a dedicated physical link instead of being transported in E1s. Native Ethernet enables more efficient use of bandwidth and maximizes Ethernet throughput since no PDH overhead is added. NE Network Element Near-end The selected terminal nrt-VBR non-real time Variable Bit Rate NPU Node Processor Unit NTP Network Time Protocol O&M Operation and Maintenance OAM Operation, Administration, and Maintenance OSPF Open Shortest Path First 167 Technical Description PCI Peripheral Component Interconnect RSSI Received Signal Strength Indicator PDH Plesiochronous Digital Hierarchy RSTP Rapid Spanning Tree Protocol PFU Power Filter Unit rt-VBR real time Variable Bit PLL Phase Locked Loop RTPC Rate Remote Transmit Power Control PPD Partial Packet Discard SAU Service Access Unit PPP Point-to-Point Protocol. Used for IP transport over serial links. SD Signal Degradation PSU Power Supply Unit PTP Point To Point QAM Quadrature Amplitude Modulation Radio Link Two communicating Radio Terminals Radio Terminal One side of a radio link SDH Synchronous Digital Hierarchy SES Severely Errored Second SF Signal Failure SFP Small Form Factor Pluggable SMU Switch Multiplexer Unit RAU Radio Unit SNCP Subnetwork Connection Protection. 1+1 E1 SNCP is used to create a protected E1 interface from two unprotected E1 interfaces. RCC Radio Communication Channel SNIR Signal to Noise and Interference Ratio RDI Remote Defect Indication SNMP Simple Network Management Protocol RL-IME Radio Link Inverse Multiplexing for Ethernet SPI Serial Peripheral Interface RMM Removable Memory Module STM-1 Synchronous Transport Module 1(155 Mbps) RS Regenerator Section SXU SDH Cross-connect Unit 168 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Glossary TCP/IP Transmission Control Protocol/Internet Protocol TDM Time Division Multiplexing TIM Trace Identifier Mismatch TM Terminal Multiplexer TUG3 Tributary Unit Group VP Virtual Path VPC Virtual Path Connection VPI Virtual Path Identifier WCDMA Wideband Code Division Multiple Access XPIC Cross Polarization Interference Canceller UBR Unspecified Bit Rate URL Uniform Resource Locator USB Universal Serial Bus V.24 Serial data interface VBR Variable Bit Rate VC Virtual Channel VC-12 Virtual Container 12 (2 Mbps) VC-4 Virtual Container 4 (155 Mbps) VCC Virtual Channel Connection VCG Virtual Concatenation Groups VCI Virtual Channel Identifier VLAN Virtual Local Area Network 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 169 Technical Description 170 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Reference List Reference List [1] CLI User Guide, 2/1553-CSH 109 32/1-V1 [2] Installing Indoor Equipment, 1531-CSH 109 32/1-V1 [3] MINI-LINK Craft User Guide, 1/1553-CSH 109 32/1-V1 [4] MINI-LINK Craft User Interface Descriptions, 7/1551-CSH 109 32/1-V1 [5] MINI-LINK DCN Guidelines, 1/154 43-FGB 101 004/1-V1 [6] MINI-LINK TN R4 Soft Keys, 9/221 02-CSH 10932/1 [7] Network Synchronization Guidelines, 4/154 43-FGB 101 004/1-V1 [8] Physical/Electrical Characteristics of Hierarchy Digital Interface, ITU-T G.703 (11/2001) [9] Planning and Dimensioning L1 Radio Link Bonding, 6/154 43-CSH 109 32/1-V1 [10] Transferring a CLI Script File to a MINI-LINK TN , 17/1553-CSH 109 32/1-V1 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 171 Technical Description 172 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Index Index 1+0 protection XPIC 121 1+1 E1 SNCP 66 1+1 protection 66, 116 XPIC 121 1+1 SDH SNCP 67 10/100/1000BASE-T 52 2xE0 DCN 147 A AAU 57 block diagram 59 overview 58 ABR 149 Access Module Magazine, See AMM Accessories 154 AIS 98 Alarm handling 133 Alarm Indication Signal, See AIS AMM 6, 12 cooling 13 power supply 13 AMM 20p cooling 18 power supply 17 AMM 20p B 16 AMM 2p B 12 cooling 13 power supply 13 AMM 6p cooling 15 power supply 15 AMM 6p C/D 14 power supply 15 Amplitude Shift Keying, See ASK Antennas 112 mounting kit 114 Area Border Router, See ABR ASK 108 ATM 7 interfaces 59 ATM Aggregation Unit, See AAU ATM Cross-connect 60 ATPC 130–131 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Automatic Transmit Power Control, See ATPC B Basic node 5, 10 BERT 140 Bit Error Ratio Tester, See BERT Block diagram AAU 59 ETU2 54 ETU3 55 LTU 155 35 LTU 16/1 32 LTU 32/1 32 LTU3 12/1 32 MMU2 B 91 MMU2 C 91 MMU2 D 93 MMU2 E/F 155 94 NPU1 B 23 NPU3 24 NPU3 B 25 RAU 106 SXU3 B 37 BPI bus 11 BR button 78 Buffering 61 Buses 10 C C-QPSK 97 Cable interface 97, 108 CAC 60 CBR 59 CC 62 CLI 153 CLP0+1 61 CLP1 61 Co-siting MINI-LINK E 80 Command Line Interfaces, See CLI Configuration management 139 Congestion thresholds 61 Connection loop 136 Continuity Check, See CC 173 Technical Description Cooling AMM 20p 18 AMM 2p B 13 AMM 6p 15 PSU DC/DC Kit 157 D Data Communication Network, See DCN DCC 96, 147 DCCm 147 DCCr 147 DCN 144 2xE0 147 E1 147 interfaces 145 nx64 kbps 147 DCN LAN Switch 160 DHCP 145 DNS 145 Domain Name System, See DNS Dynamic Host Configuration Protocol, See DHCP E E1 DCN 147 interface 30 LTU 31 Early Packet Discard, See EPD EEP 73 Electrical interface 34 ELP 72 Engineering Order Wire EOW 26 Enhanced Equipment Protection, See EEP EOW 26 EPD 61 Equipment and Line Protection, See ELP Equipment handling 78 Equipment protection 65, 118–119 Ethernet interface 148 traffic 39 Ethernet Interface Unit, See ETU Ethernet Switch functionality Ethernet 41 ETU 7, 52 174 ETU2 block diagram 54 ETU3 block diagram 55 F F4/F5 62 Fan Unit, See FAU FAU 7 FAU1 19 FAU2 15 FAU3 157 FAU4 13 Fault management 133 AAU 59 FEC 97–98 File Transfer Protocol, See FTP Forward Error Correction, See FEC Frequency diversity 116 FTP 145 G G.804 link 60 H HCC 96 Hop Communication Channel, See HCC Hot standby 82, 116 HSDPA 57 I ICF 154 ICF 16x2 156 ICF1 17, 155 ICF2 156 ICF3 156 IF loop 137 IMA 60 IMA group 60 Indoor part 6 units 6 Installation 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Index Installation (cont.) antennas 112 integrated 112 separate 113 Integrated Installation 112 Integrated Power Splitter 113 Interface DCN 145 E1 30 ethernet 148 Interface Connection Field, See ICF Internal Router, See IR Inverse multiplexer 55 Inverse Multiplexing for ATM 60 IP addressing 148 router 148 services 144 IR 149 IRP 133 L License management 143 Licensing 2 Line loop 136 Line Termination Unit, See LTU Link summarization 149 Local loop 136 Loops 135 LTU 6 E1 31 STM-1 34 LTU 155 block diagram 35 LTU 155e 34 LTU 155e/o 34 LTU 16/1 31 block diagram 32 LTU 32/1 31 block diagram 32 LTU B 155 34 LTU3 12/1 31 block diagram 32 Management (cont.) tools 150 MDCR 59 MINI-LINK Craft 150 MINI-LINK E co-siting 80 MMU 7, 83 MMU2 B 83 block diagram 91 MMU2 C 83 block diagram 91 MMU2 D 85 block diagram 93 MMU2 E 155 85, 89 MMU2 E/F 155 block diagram 94 MMU2 F 155 86, 89 MMU2 H 86 Modem Unit, See MMU Mounting Kit antennas 114 MPH 161 MPH for MINI-LINK TN, See MPH MSP 1+1 70 Multiplexer Section Protection, See MSP 1+1 N Network layer protection 65 Network Layer Protection 66 Network Time Protocol, See NTP Node Processor Unit, See NPU Non-revertive 66 NPU 6, 20 NPU1 B 20, 22 block diagram 23 NPU1 C 20, 22 NPU3 20, 22 block diagram 24 NPU3 B 20, 22 block diagram 25 NTP 144 Numbered interfaces 148 nx64 kbps DCN 147 M O Management 132 interfaces 150 Open Short Path First, See OSPF Optical interface 34 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 175 Technical Description Optical splitter/combiner 159 OSPF 148 Outdoor part 8 P Partial Packet Discard, See PPD PCI bus 11 Performance management 139 Ethernet 51 Radio terminal 132 Peripheral Component Interconnect, See PCI Permanently bridged 66 PFU 7 PFU1 18 Physical link layer protection 65 Policing 60 Power bus 11 Power Filter Unit, See PFU Power supply AMM 20p 17 AMM 2p B 13 AMM 6p 15 AMM 6p C/D 15 Power Supply Units, See PSU PPD 61 PRBS 140 Protected (1+1) 82 Protection 116, 121 Protection mechanisms 65 Pseudo Random Bit Sequence, See PRBS PSU 157 PSU DC/DC Kit 157 cooling 157 Q QAM 97 R Radio Communication Channel, See RCC Radio Link 81 Radio segment protection 118 Radio Terminal 5 protected (1+1) 82 unprotected (1+0) 81 Radio Unit, See RAU 176 RAU 104 block diagram 106 external interfaces 105 types 106 RCC 97 Received Signal Strength Indicator, See RSSI Remote Transmit Power Control, See RTPC Removable Memory Module, See RMM Revision information 2 RF loop 109, 137–138 Ring protection 68 RMM 20 RSSI 110 RTPC 130–131 Rx equipment protection 119 Rx loop 136 S SAU 7, 28 Scheduling 61 SDH Traffic 33 SDH Multiplexer Unit, See SXU Security management 142 Separate installation 113 Serial Peripheral Interface, See SPI Service Access Unit, See SAU ServiceOn Element Manager 151 ServiceOn Ethernet Service Activator 152 ServiceOn Network Manager 64, 152 SFP 159 SFPe 159 SFPo 159 Shaping 61 Simple Network Management Protocol, See SNMP Small Form Factor Pluggable, See SFP SMU 7 SMU2 80 SNCP 66–67 SNMP 133, 152 Sofix 154 Software management 144 Space diversity 116 SPI bus 11 Static routing 149 STM-1 LTU 34 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 Index Sub-Network Connection Protection, See SNCP Switch Multiplexer Unit, See SMU Switching mode 66 SXU 7 SXU3 B 36 block diagram 37 Synchronization 36, 74 System architecture 10 overview 4 T TDM bus 10 Time Division Multiplexing, See TDM TMR 9302 162 Traffic SDH 33 Traffic routing 63 Transmit Power Control 130 Tx equipment protection 117–118 U UBR 59 Uni-directional 66 Universal Serial Bus, See USB Unnumbered interfaces 148 Unprotected (1+0) 81 USB 22, 148 User I/O 22, 138 V VBR 59 Virtual links 149 VP/VC Cross-connection 60 W Working standby 82, 116 12/221 02-CSH 109 32/1-V1 Uen N | 2010-04-20 177