FlexiHybrid Solution Description

FlexiHybrid

Solution Description

A25000-A0300-G008-01-76P1

Issue: 1 Issue date: March 2010

2 A25000-A0300-G008-01-76P1Issue: 1 Issue date: March 2010


The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved.

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

A25000-A0300-G008-01-76P1Issue: 1 Issue date: March 2010

3


Table of ContentsThis document has 111 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 131.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Solution structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1 IDU-ODU interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1.1 Radio signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1.2 IDU/ODU service auxiliary channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1.3 ODU power supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.1 Modulations and capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2 Basic configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.2.1 Standard terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.2.2 Protected terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.2.3 Ring configuration (East-West) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.3 Equipment composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.4 Link Terminals with different configuration. . . . . . . . . . . . . . . . . . . . . . . 455.5 Ethernet payload Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.5.1 Maximum bit rate over the air . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.5.2 Port Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.5.3 Learning functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.5.4 Ethernet Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.5.5 Throughput and Back-to-Back Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . 515.5.6 Max packet size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.5.7 Buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.5.8 Counters, Link monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.5.9 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.5.9.1 QoS in Standard and Enhanced Master IO modules. . . . . . . . . . . . . . . 545.5.9.2 QoS in Standard2, Enhanced2 and 42xE1 Master IO modules. . . . . . . 555.5.9.3 QoS in GigEth and GigEth Enhanced Master IO module . . . . . . . . . . . 565.6 VLAN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585.6.1 HW/SW compatibility for VLAN Management functionlaity . . . . . . . . . . 585.6.2 Ethernet Ports Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585.6.3 VLAN Management Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.6.4 Default VLAN-ID configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.6.5 Behaviour for p-bit configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.6.6 Ingress Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60



5.6.6.1 Single Tag mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605.6.6.2 Double Tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.6.7 Forwarding Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.6.7.1 Port-Based Forwarding Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.6.7.2 VLAN-based Forwarding Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.6.7.3 Forwarding mode behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.6.8 Egress Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.6.9 Quality of Service management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.6.9.1 Behaviour: p-bit values are overwritten in some cases. . . . . . . . . . . . . . 705.6.10 Guidelines and Rules for VLAN configurations . . . . . . . . . . . . . . . . . . . 705.6.10.1 Single Tag mode vs Double Tag mode. . . . . . . . . . . . . . . . . . . . . . . . . . 705.6.10.2 Classification criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.6.10.3 Link with mixed configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.7 Ethernet Functionality Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.8 Particular behaviours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.9 100Mbps-PLUS Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.10 APC (Adaptive Power Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.11 ACM (Adaptive Coding / Modulation) . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.11.1 Scope of ACM Applicability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.11.2 Released configurations for ACM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.11.3 ACM Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.12 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.12.1 HW/SW compatibility for Performance Monitoring functionlaity . . . . . . . 835.12.2 Performance Monitoring principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.12.3 Measurements Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.12.4 Measurement Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.12.5 Measurements Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.12.6 Quality and Unavailability event counters . . . . . . . . . . . . . . . . . . . . . . . . 865.12.7 Radio Protection Switching (RPS) Parameters. . . . . . . . . . . . . . . . . . . . 865.12.8 Extended lists of available Performance Monitoring data . . . . . . . . . . . . 875.12.9 Performance Monitoring management behaviour . . . . . . . . . . . . . . . . . . 895.12.10 RF Power measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.12.11 Ethernet Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.13 Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.13.1 Termination Points identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.13.2 Bidirectional Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.13.3 Ring Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975.14 STM-1 Mux/Demux (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995.15 Loop-back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005.15.1 E1 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005.15.1.1 Loopbacks for the aggregate signal . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005.15.1.2 Loopbacks for a single E1 stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.15.2 STM-1 loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.15.2.1 Loopbacks with STM-1 transparent . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.15.2.2 Loopbacks with STM-1 with MUX/DEMUX option . . . . . . . . . . . . . . . . 102

6 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.1 IDU and Network management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103


5


6.2 IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.3 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.4 NMS Network Operational Principles. . . . . . . . . . . . . . . . . . . . . . . . . . 1036.5 Third Party Network Management Software Support . . . . . . . . . . . . . 104

7 Solution technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

8 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108



List of FiguresFigure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 2 Microwave Split Mount Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 3 “FlexiHybrid” Equipment in (1+0) configuration. . . . . . . . . . . . . . . . . . . . 21Figure 4 Applications 1 - Mobile Networks- 1st Mile . . . . . . . . . . . . . . . . . . . . . . . 23Figure 5 Applications 2 - Mobile Networks-Aggregation layer Hybrid backhaul (1) .

24Figure 6 Applications 2 - Mobile Networks-Aggregation layer Hybrid backhaul (2) .



25Figure 9 PDH Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 10 Ethernet Ring (1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 11 Ethernet Ring (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 12 Ethernet Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 13 1+0 (Standard) terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 14 1+1 protected diversity mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 15 1+1 protection in non-diversity mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 16 Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 17 1+0 system with integrated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 18 1+0 system with independent antenna . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 19 1+1 system with Hot Standby or FD with integrated antenna . . . . . . . . . 40Figure 20 1+1 system Hot Standby or FD with independent antenna. . . . . . . . . . . 41Figure 21 1+1 system with dual polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 22 1+1 SD system with two separated antennas. . . . . . . . . . . . . . . . . . . . . 43Figure 23 East-West (2+0 system with different destinations or Ring) with integrated

antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 24 Link terminals with different configuration. . . . . . . . . . . . . . . . . . . . . . . . 45Figure 25 Single Network Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 26 Two-Network Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 27 Priority assignment logic scheme (Standard and Enhanced Master IO Mod-

ules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 28 Priority assignment logic scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 29 Priority assignment logic scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 30 1+0 Radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 31 Example of Port connection configuration . . . . . . . . . . . . . . . . . . . . . . . 64Figure 32 1+0 Radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 33 QoS radio Radio with Standard2, Enhanced2 and 42E1 Master Modules .

75Figure 34 Rx side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Figure 35 Tx side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 36 Time diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 37 Measurement points in 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . 85Figure 38 Measurement points in 2+0 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Figure 39 Measurement point when STM1 and Mux/Demux functionality is present .

86


7


Figure 40 Physical location of E1 TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figure 41 TP name and associated Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Figure 42 Standard Cross connection with related syntax. . . . . . . . . . . . . . . . . . . 96Figure 43 E1 Data Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 44 Protected E1 data connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 45 Normal E1 data path within the IDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 46 Protected E1 data path within the IDU. . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 47 Ring Cross connection with related syntax . . . . . . . . . . . . . . . . . . . . . . 99Figure 48 STM-1 Mux/Demux Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Figure 49 Local LIU loop-back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 50 Local Modem loop-back. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 51 Remote LIU loop-back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 52 PC and IDU on same subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Figure 53 IDU on different subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104



List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 2 List of conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . 11Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 4 RF Channeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 5 Modulation format supported for each bandwidth . . . . . . . . . . . . . . . . . 28Table 6 Summary of Modes Supported up to SVR 2.1 . . . . . . . . . . . . . . . . . . . . 28Table 7 Modes and ETSI Class Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Table 8 Modulations, Channel bandwidth and supported payloads . . . . . . . . . . 29Table 9 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 10 Equipment composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Table 11 Equipment composition according to the configuration . . . . . . . . . . . . . 37Table 12 Over the air compatibility for Master IO modules (link terminals are intend-

ed to have the same SVR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Table 13 Over the air compatibility for Master IO modules (link terminals are intend-

ed to have the same SVR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Table 14 Standard and Enhanced Master I/O Card . . . . . . . . . . . . . . . . . . . . . . . 50Table 15 Gigabit Master I/O Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Table 16 42xE1Master I/O Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Table 17 Latency on Standard2 and Enhanced2 IO Modules . . . . . . . . . . . . . . . 51Table 18 Throughput on Standard2 and Enhanced2 IO Modules (%) . . . . . . . . . 52Table 19 Throughput on Standard2 and Enhanced2 IO Modules (Mbit/s) . . . . . . 52Table 20 Back-to-back frames limits on Standard2 and Enhanced2 IO Modules . 53Table 21 Ethernet Ports Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Table 22 VLAN Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 23 Ingress Policy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Table 24 Ingress frame Manipulation in Single Tag mode . . . . . . . . . . . . . . . . . . 60Table 25 Port Double Tag Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 61Table 26 Ingress frame manipulation in Double Tag mode . . . . . . . . . . . . . . . . . 62Table 27 Double tag (Stag + Ctag) mode: frame formats at both User and Network

ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Table 28 Double tag (Ctag + Ctag) mode: frame formats at both User and Network

ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Table 29 Forwarding modes applied on the base of VLAN Management . . . . . . 63Table 30 Port Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Table 31 VLAN connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Table 32 Forwarding behaviour for Standard2, Enh2, 42E1 Master IO . . . . . . . . 65Table 33 Egress Policy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Table 34 Egress Frame manipulation description . . . . . . . . . . . . . . . . . . . . . . . . . 66Table 35 Applicable QoS criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Table 36 Summary of Ethernet Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 72Table 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Table 38 Released ACM modes and Parameters . . . . . . . . . . . . . . . . . . . . . . . . 81Table 39 Measurement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Table 40 Validity condition for Measurement Points . . . . . . . . . . . . . . . . . . . . . . . 87Table 41 Complete list of PM measurements for SVR 2.2 . . . . . . . . . . . . . . . . . . 88Table 42 Validity condition for Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90


9


Table 43 Complete list of Statistics and raw Counters supported . . . . . . . . . . . . 90Table 44 Special values of measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Table 45 Validity condition for Ethernet Counters . . . . . . . . . . . . . . . . . . . . . . . . 91Table 46 Ethernet Statistics available via Web-LCT and SNMP . . . . . . . . . . . . . 91Table 47 Ethernet Statistics available via SNMP interface only . . . . . . . . . . . . . 92Table 48 TP identification and Prefix Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Table 49 Module interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Table 50 General technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Table 51 RTPC range (6-13 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Table 52 RTPC range (15-38 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Table 53 Max output power (at ODU flange) . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Table 54 BER = 10-6 Rx threshold (dBm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Table 55 Total power consumption (W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107




11

Solution Description Preface

1 PrefaceThis document provides the technical description and the technical specifications of the FlexiHybrid SVR 2.2, a radio system operating in the RF bands from 6 GHz to 38 GHz.

1.1 Intended audienceThis document is intended to the radio network planners and to the technicians in charge to operate and maintain the FlexiHybrid.

1.2 Structure of this documentThe document is divided into the following main chapters:

1.3 Symbols and conventionsThe following symbols and conventions are used in this document:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the document

Chapter 2 Overview Provides an overview on the FlexiHybrid

Chapter 3 Solution structure Provides a description of the parts of the equipment

Chapter 4 Applications Provides the main applications that can be implemented with the FlexiHybrid

Chapter 5 Features Provides the main features

Chapter 6 Management Provides the information regarding the management of the FlexiHybrid

Chapter 7 Solution technical specifica-tions

Lists the technical data

Chapter 8 Acronyms and abbreviations Lists the acronyms and abbreviations used in this document

Table 1 Structure of this document

Representation Meaning

Bold Text in the graphical user interface (window and wizard titles, field names, buttons, etc.) is represented in bold face.

Example: Click Shutdown and then click OK to turn off the com-puter.

Table 2 List of conventions used in this document


Solution DescriptionPreface

Italic Field values, file names, file extensions, folder and directory names are denoted by italic text.

Examples: Enter 192.168.0.1 in the IP address field. Click OK to produce a .pdf file.

Courier Command and screen output are denoted by courier font.

Example: ping -t 192.168.0.1<Angle brackets> Place holders for distinct names or values are represented by

enclosing them in <angle brackets>. If a file name is involved, italic text will also be used.

Example: The naming convention for the log files is <NEname>.txt, where <NEname> is the name of the NE sending the messages.

Keyboard button Keyboard keys are represented with a surrounding box.

Example: Press Enter .

[Square brackets] Keyboard shortcuts are represented using square brackets.

Example: Press [CTRL+ALT+DEL] to open the Task Manager.

> The “>” symbol is used as short form to define a path through indi-vidual elements of the graphical user interface, e.g., menus and menu commands.

Example: On the Windows taskbar, select Start > Programs > TNMS > Client menu command to start the TNMS Core/CDM Client.

☞ A tip provides additional information related to the topic described.

g A note provides important information on a situation that can cause property damage or data loss.

A note introduced in the text by the keyword NOTICE: describes a hazard that may result in property damage but not in personal injury.

f A safety message provides information on a dangerous situation that could cause bodily injury.

The different hazard levels are introduced in the text by the follow-ing keywords:

DANGER! - Indicates a hazardous situation which, if not avoided, will result in death or serious (irreversible) personal injury.

WARNING! - Indicates a hazardous situation which, if not avoided, could result in death or serious (irreversible) personal injury.

CAUTION! - Indicates a hazardous situation which, if not avoided, may result in minor or moderate (reversible) personal injury.

Representation Meaning

Table 2 List of conventions used in this document (Cont.)


13

Solution Description Preface

Screenshots of the graphical user interface are examples only to illustrate principles. This especially applies to a software version number visible in a screenshot.

1.4 History of changes

1.5 Waste electrical and electronic equipment (WEEE)All waste electrical and electronic products must be disposed of separately from the municipal waste stream via designated collection facilities appointed by the government or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.

Figure 1 WEEE label

The correct disposal and separate collection of waste equipment will help prevent poten-tial negative consequences for the environment and human health. It is a precondition for reuse and recycling of used electrical and electronic equipment.

For more detailed information about disposal of such equipment, please contact Nokia Siemens Networks.

The above statements are fully valid only for equipment installed in the countries of the European Union and is covered by the directive 2002/96/EC. Countries outside the European Union may have other regulations regarding the disposal of electrical and electronic equipment.

1.6 RoHS complianceFlexiHybrid complies with the European Union RoHS Directive 2002/95/EC on the restriction of use of certain hazardous substances in electrical and electronic equipment.

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-brominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical and electronic equipment put on the market after 1 July 2006.

Materials usage information on Nokia Siemens Networks Electronic Information Products imported or sold in the People’s Republic of ChinaFlexiHybrid complies with the Chinese standard SJ/T 11364-2006 on the restriction of the use of certain hazardous substances in electrical and electronic equipment. The

Issue Issue date Remarks

1 March 2010 1st version

Table 3 History of changes


Solution DescriptionPreface

standard applies to the use of lead, mercury, cadmium, hexavalent chromium, polybro-minated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical and electronic equipment put on the market after 1 March 2007.


15

Solution Description Overview

2 OverviewThe “FlexiHybrid” provides high capacity transmission, flexibility, features, and conve-nience for wireless digital communications networks.

The “FlexiHybrid” represent a new microwave architecture that is designed to address universal applications for both PDH and SDH platforms. This advanced technology platform is designed to provide the flexibility to customers for their current and future network needs.

The “FlexiHybrid” is based upon a common platform to support a wide range of network interfaces and configurations. It supports links up to 63 x E1, 2x 10/100BaseTX Ether-net, 4 x10/100/1000 BaseTX Ethernet, 1x1000 Base SX/LX and 1 x STM-1.

The “FlexiHybrid” is spectrum and data rate scalable, enabling service providers or organizations to trade-off system gain with spectral efficiency and channel availability for optimal network connectivity.

The “FlexiHybrid” enables network operators (mobile and private), government and access service providers to offer a portfolio of secure, scalable wireless applications for data, video, and Voice over IP (VoIP).

The “FlexiHybrid” includes integrated Operations, Administration, Maintenance, and Provisioning (OAM&P) functionality and design features enabling simple commissioning when the radio network is initially set up in the field at the customer’s premises. Further-more, a highlight of “FlexiHybrid” is scalability and the capability to support a ring-type architecture. This ring or consecutive point radio architecture is self-healing in the event of an outage in the link and automatically re-routes data traffic, thereby ensuring that service to the end user is not interrupted.

Split-mount architectureThe overall split mount architecture consists of a single 1RU rack mount “FlexiHybrid” with a cable connecting to an Outdoor Unit (ODU) with an external antenna.

The IDU has been designed to be frequency independent, and the ODU has been designed to be capacity independent.

The “FlexiHybrid” allows selection for multiple capacity options, modulation types, radio frequency channels and transmit output power levels to accommodate and adhere to worldwide regulatory and spectral efficiency requirements.

The ODU, mounted outdoors, can support frequency bands from 6 GHz to 38 GHz.

The “FlexiHybrid” supports 1+0 and 1+1 protection and ring architectures in a single 1 RU chassis. The modem and power supply functions are supported using easily replaceable plug-in modules.

An additional feature of the “FlexiHybrid” is provisioned for a second plug-in modem/IF module to provide repeater or east/west network configurations.


Solution DescriptionOverview

Figure 2 Microwave Split Mount Architecture

Equipment compositionThe equipment is made up of:

• indoor assembly (IDU) • patch panels • outdoor assembly (ODU)

The indoor assembly consists of an ETSI rack, equipped with one or two IDU sub-rack.

The outdoor assembly is a transceiver housed in a very compact tight container, installed on the antenna or on pole.

The two assemblies (IDU and ODU) are at IF level connected through a single coaxial cable.

The patch panels are used to terminate the E1 tributaries and to provide a connection interface between the FlexiHybrid and the station equipment.

RF channellingTable 4 shows the frequency bands (according to the RF channeling) of the radio digital system “FlexiHybrid”.

RF band

Frequencyranges (GHz)

ITU-R / CEPT Recommendations

RF Channel Spacing

(MHz)

ShifterFreq. (MHz)

6L 5.925-6.425 F.383-7 29.65/59.3 252

6U 6.430-7.110 F.384-8 40 340

Table 4 RF Channeling


17


7 7.425-7.725 F.385-9 Annex 1 7/28 154/161/168/196/2457.110-7.750 lower F.385-9 Annex 3

7.110-7.750 upper F.385-9 Annex 3

7.425-7.900 F.385-9 Annex 4

7.125-7.425 F.385-9 (f0=7275 MHz)

7.425-7.725 F.385-9 (f0=7575 MHz)

7.125-7.425 Custom (Finland)

7.485-7.695 Custom (Bielorussia)

7.138.5-7.711.5 Custom (Messico)

7.274.0-7.487.5 Custom (Kenya)

8 8.200-8.500 F.386-6 14/28/29.65 148.250/151.614/266/311.32

7.725-8.275 F.386-6 Annex 1

7.900-8.400 ITU-R/OIRT F.386-6 Annex 4

8.200-8.500 F.386-6 Annex 3

7.900-8.500 CEPT(02)-06 annex 2/Custom 3GIS Sweden

8.290-8.445 Custom (Equador)

7.770-7.960 Custom (Bulgaria)

11 10.700-11.700 F.387 Recommends 1 40 490/530

10.700-11.700 F.387 Annex 1

10.700-11.700 F.387 Annex 2

13 12.750-13.750 F.497-6 28 266

15 14.5 - 15.35 F.636 14/28 420/490

CEPT 12-07E 14/28 728

Client arrangement

“CHILE”

28 420

Client arrangement

“ARGENTINE”

28 322

Client arrangement

“Custom” F.636-3

28 644

RF band



RF Channel Spacing

(MHz)

ShifterFreq. (MHz)

Table 4 RF Channeling (Cont.)


Solution DescriptionOverview

TechnologySystem design is based on the use of the most advanced technologies and a big effort has been made to transfer complexity from analog to digital hardware to benefit of cus-tomised integration (ASlCs) and to improve system reliability.

The biggest and most sophisticated ASIC designed for communication systems is the core of the “FlexiHybrid” modem.

System design is based on a fully digital concept. This approach draws considerable advantage from the most recent technological achievements leading to VLSI circuit solutions, considered the most suitable for managing digital signals.

In addition, this approach ensures a very high manufacturing quality, with an extremely reliable performance.

System Power SupplyThe IDU requires an input of 48 volts dc ±10% on the front panel DC Input connector. The total power required depends on the option cards and protection configuration (1+0, 1+1). The IDU front panel power connector pin numbering is 1 thru’ 2, from left to right, when facing the unit front panel. Pin 1 is the power supply return and is internally con-nected to unit chassis ground. Pin 2 should be supplied with a nominal 48 V dc, with respect to the unit chassis (ground). A ground-isolated supply may be used, provided it will tolerate grounding of its most positive output.

The power input is -48 Vdc at 2 Amps minimum. It is suggested that any power supply used delivers a minimum of 100 W to the IDU.

The IDU supplies the ODU with all the necessary power via the ODU/IDU Interconnec-tion cable. The IDU does not have an on/off power switch. When DC power is con-nected to the IDU, the digital radio powers up and becomes operational. Up to 320 mW RF power can be present at the antenna port (external antenna version). The antenna should be directed safely when power is applied.

18 17.7 - 19.7 F.595-6 - T/R 12-03 27.5 1010

F.595 27.5 1560

Client arrangement

“IRAN”

28 1008

23 22 - 23.6 T/R 13-02 E 28 1008

Client arrangement

“MEXICO”

25 1200

F.637-3 Annex 1 28 1232

26 24.5 - 26.5 F.748 28 1008

32 31.8 - 33.4 F.1520-2 28 812

38 37 - 39.5 F.749 Annex 1 28 1260

RF band



RF Channel Spacing

(MHz)

ShifterFreq. (MHz)

Table 4 RF Channeling (Cont.)


19


Mechanical structureThe mechanical structure of the IDU and ODU meets the ETSI standard (ETS 300 119-1, 3, 4).

The plug-in IDU is installed in a 2200 mm (Height) x 600 mm (Length) x 300 mm (Depth) rack.

In the adopted solution, with only front access, particular efforts have been dedicated to the shielding of the plug-in indoor unit to meet the EMC and EMI specifications.

Installation solutions: wall-mounting and floor-mounting in the center of the room (for in-line and back to back configurations).

☞ The IDU can also be installed in the FOC (Flexi Outdoor Case). Refer to the FOC relevant documentation.


Solution DescriptionSolution structure

3 Solution structureThe “FlexiHybrid” digital radio system is characterized by the high operating frequency. For this reason, in order to minimize the feeder loss an indoor/outdoor split configuration has been chosen. The indoor part consists of an ETSI rack and one IDU. The IDU, with base band units and modem, is connected through a single coaxial IF cable to a very compact outdoor transceiver located close to the antenna (see Figure 3).

Two types of ODU are available: HC AP/CC and HC AP.

– Type HC AP/CC is available within the 6, 7, 8, 11, 13, 15, 18, 23 and 26 GHz bands for AP channelling and implements RF waveguide-connections towards the antenna, and cable-connections (IF) towards the IDU.

– Type HC AP is available within the 32 and 38 GHz bands for AP channelling and implements waveguide-connections (RF) towards the antenna and cable-connec-tions (IF) towards the IDU.


21

Solution Description Solution structure

Figure 3 “FlexiHybrid” Equipment in (1+0) configuration

OUTDOORSECTION

HC AP/CC OUTDOOR UNIT (ODU)Transceiver

IF COAXIAL CABLE

INDOOR UNIT (IDU)

ETSI RACK

INDOOR SECTION

HC AP (ODU)


Solution DescriptionSolution structure

3.1 IDU-ODU interconnectionThe IDU-ODU interconnection takes place through a single bi-directional line, carrying the aggregate signal (Tx/Rx radio signal, IDU/ODU auxiliary service channel and ODU power supply).

3.1.1 Radio signalThe IDU-ODU connection, concerning the Tx/Rx radio signals, includes the following IF signals:

• 350 MHz modulated signal to transmit the Tx signal (from IDU to ODU) • 140 MHz modulated signal to transmit the Rx signal (from ODU to IDU).

By using frequencies 350 MHz and 140 MHz it is possible to:

• optimize the length, the attenuation and the size of the connection cable IDU-ODU • minimize the filtering functions in IDU and ODU • minimize the interferences between the Tx and Rx sections of the ODU • minimize the interferences between the harmonics of the IF Tx frequency and the

shifter frequencies • obtain the dynamic interval necessary to the AGC circuit in IDU and ODU.

3.1.2 IDU/ODU service auxiliary channelAn auxiliary channel connects the IDU to the ODU, carrying all the information required by the equipment to operate properly (i.e., alarms, data channel, speech channel, etc.). The IDU-ODU service connection takes place through two 7 MHz and 10 MHz FSK-modulated sub-carriers.

3.1.3 ODU power supplyThe IDU-ODU interconnection cable is also used to carry the secondary DC voltage (-48 V) to supply the ODU. The DC voltage comes from the relevant MODEM/IF unit in the IDU.

In this unit are also present the soft-start circuits, the current limitation circuits and the alarm circuits to generate the open cable alarm and the short-circuit on the cable alarm.


23

Solution Description Applications

4 Applications

Figure 4 Applications 1 - Mobile Networks- 1st Mile

– Enabling all-PDH access network architectures– High speed 63xE1 capacity options– Mixed E1, Ethernet traffic (up to 100 Mbps)


Solution DescriptionApplications

Figure 5 Applications 2 - Mobile Networks-Aggregation layer Hybrid backhaul (1)



25





Solution DescriptionApplications

Figure 9 PDH Ring

Figure 10 Ethernet Ring (1)


27


Figure 11 Ethernet Ring (2)

Figure 12 Ethernet Applications


Solution DescriptionFeatures

5 Features

5.1 Modulations and capacitiesRegardless of the RF frequency band, the following modulations and channel band-widths are supported:

7 MHz 14 MHz 28 MHz

4 QAM x x x

16 QAM x x x

32 QAM - x x

64 QAM - - x

128 QAM - - x

Table 5 Modulation format supported for each bandwidth

Supported Modes (Minimum SVR#)

Signal BW

(MHz)

Modulation ETSI Equivalent PDH/SDH Rate

RF band (GHz)

6L 6U 7 8 11 13 15 18 23 26 32 38

7 QPSK 8 Mbit/s - - - - - - 2.1 2.1 2.1 - - -

16 QAM 2*8 Mbit/s - - - - - - 2.1 2.1 2.1 - - -

14 QPSK 2*8 Mbit/s - - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

16 QAM 34 Mbit/s - - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

32 QAM STM0 (51) - - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

28 QPSK 34 Mbit/s 1.3 - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

16 QAM 2*34Mbit/s 1.3 - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

32 QAM 2*STM0 1.3 - - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

64 QAM 2*STM0/STM1 1.3 1.3 - - - 1.2 1.1 1.1 1.2 1.3 1.4 1.4

128 QAM STM1 1.3 1.3 1.1 1.1 1.1 1.2 1.1 1.1 1.2 1.3 1.4 1.4

Note: “-” = Non-Supported Combinations.

Table 6 Summary of Modes Supported up to SVR 2.1


29

Solution Description Features

The table below shows the data rate (Mbps) by modulation type, channel bandwidth and supported payloads.

ETSI Class

Signal BW

(MHz)

Modulation ETSI Equivalent PDH/SDH Rate

RF band (GHz)

6L 6U 7 8 11 13 15 18 23 26 32 38

7 QPSK 8 Mbit/s - - - - - - 2 2 2 - - -

16 QAM 2*8 Mbit/s - - - - - - 4 4 4 - - -

14 QPSK 2*8 Mbit/s - - - - - 2 2 2 2 2 2 2

16 QAM 34 Mbit/s - - - - - 4 4 4 4 4 4 4

32 QAM STM0 (51) - - - - - 4 4 4 4 4 4 4

28 QPSK 34 Mbit/s 2 - - - - 2 2 2 2 2 2 2

16 QAM 2*34Mbit/s 4 - - - - 4 4 4 4 4 4 4

32 QAM 2*STM0 4 - - - - 4 4 4 4 4 4 4

64 QAM 2*STM0 (*) 4 5B2 - - - 4 4 4 4 4 4 4

128 QAM STM1 (**) 5A2 5B1 5A1 5A1 5B1 5A2 5A1 5A 5A 5A 5A 5A

Note: “-” = Non-Supported Combinations.

(*) The 13 GHz, 15 GHz, 18 GHz and 23 GHz bands were certified with ETSI EN 302 217-2-2 V1.1.3, which admitted for the 28MHz-64QAM modes (RIC equal to 122Mbit/s) the 2xSTM0 equivalent PDH/SDH rate, but not the STM1 equivalent PDH/SDH rate, for which this standard assigns 144 Mbit/s as the minimum RIC. Therefore the class of these modes is Class4. The L6 GHz, 26 GHz, 32 GHz and 38 GHz bands were certified with the new version ETSI EN 302 217-2-2 V1.2.3 (2007-09), which has decreased to 100Mbit/s the minimum RIC required for the STM1 equiv-alent PDH/SDH rate, thus allowing the classes 5A and 5B to be applied to the 28MHz-64QAM modes. However, for uniformity with the other RF bands, class 4 has been maintained.

(**) Because of non-compliance with the Adjacent Interference performance of Class 5B, the Class 5A has been certified for this modes. N.B. the U6 and 11GHz RF band channel step is 40 MHz.

Table 7 Modes and ETSI Class Certification

Row

ID

New

Mod

es N

ame

(BW

.Mod

-#e#

M#s

)

Mod

ulat

ion

Sign

al B

andw

idth

[M

Hz]

Payload Mix

ETSI

Nom

inal

BitR

ate

(Req

)

Min

imum

requ

ired

Lice

nse

Leve

l

Sym

bol R

ate

(Bau

d R

ate)

ba

ud

EMS

[Mbi

t/s]

E1#

Eth

Mbi

t/s

STM

1 #

1 7.4-8M QPSK 7 0 8 0 8 Mbit/s 1 5661915 0.7

2 7.4-2e4M QPSK 7 2 4 0 8 Mbit/s 1 5632914 0.5

Table 8 Modulations, Channel bandwidth and supported payloads



3 7.4-4e QPSK 7 4 0 0 8 Mbit/s 1 5665262 0.5

4 14.4-17M QPSK 14 0 17 0 2*8 Mbit/s 1 11395218 0.8

5 14.4-2e13M QPSK 14 2 13 0 2*8 Mbit/s 1 11399680 0.8

6 14.4-4e9M QPSK 14 4 9 0 2*8 Mbit/s 1 11330523 0.4

7 14.4-8e QPSK 14 8 0 0 2*8 Mbit/s 1 11330523 1.3

8 7.16-17M 16QAM 7 0 17 0 2*8 Mbit/s 1 5670281 0.7

9 7.16-2e13M 16QAM 7 2 13 0 2*8 Mbit/s 1 5629010 0.4

10 7.16-4e9M 16QAM 7 4 9 0 2*8 Mbit/s 1 5665262 0.4

11 7.16-8e 16QAM 7 8 0 0 2*8 Mbit/s 1 5665262 1.3

22 28.4-35M QPSK 28 0 35 0 34 Mbit/s 2 22696741 0.6

23 28.4-2e30M QPSK 28 2 30 0 34 Mbit/s 2 22732434 1.3

24 28.4-4e26M QPSK 28 4 26 0 34 Mbit/s 2 22799360 1.3

25 28.4-8e18M QPSK 28 8 18 0 34 Mbit/s 2 22662162 0.9

26 28.4-16e2M QPSK 28 16 2 0 34 Mbit/s 2 22774821 0.6

27 28.4-18e QPSK 28 18 0 0 34 Mbit/s 2 23843401 0.5

28 14.16-36M 16QAM 14 0 36 0 34 Mbit/s 2 11838043 1.1

29 14.16-2e32M 16QAM 14 2 32 0 34 Mbit/s 2 11865929 0.7

30 14.16-4e28M 16QAM 14 4 28 0 34 Mbit/s 2 11830235 0.6

31 14.16-8e20M 16QAM 14 8 20 0 34 Mbit/s 2 11815735 0.5

32 14.16-16e3M 16QAM 14 16 3 0 34 Mbit/s 2 11859794 1.1

33 14.16-18e 16QAM 14 18 0 0 34 Mbit/s 2 11855314 0.4

49 28.16-74M 16QAM 28 0 74 0 2*34Mbit/s 3 23883557 1.3

50 28.16-2e70M 16QAM 28 2 70 0 2*34Mbit/s 3 23843401 0.5

51 28.16-4e66M 16QAM 28 4 66 0 2*34Mbit/s 3 23843401 0.6

52 28.16-8e57M 16QAM 28 8 57 0 2*34Mbit/s 3 23843401 1.3

53 28.16-16e41M 16QAM 28 16 41 0 2*34Mbit/s 3 23843401 1

54 28.16-18e37M 16QAM 28 18 37 0 2*34Mbit/s 3 23883557 0.7

55 28.16-32e8M 16QAM 28 32 8 0 2*34Mbit/s 3 23843401 1

56 14.32-47M 32QAM 14 0 47 0 STM0 (51) 3 11852978 0.7

Row

ID

New

Mod

es N

ame

(BW

.Mod

-#e#

M#s

)

Mod

ulat

ion

Sign

al B

andw

idth

[M

Hz]

Payload Mix

ETSI

Nom

inal

BitR

ate

(Req

)

Min

imum

requ

ired

Lice

nse

Leve

l

Sym

bol R

ate

(Bau

d R

ate)

ba

ud

EMS

[Mbi

t/s]

E1#

Eth

Mbi

t/s

STM

1 #

Table 8 Modulations, Channel bandwidth and supported payloads (Cont.)


31


Row ID:It is the ID assigned to the row and it univocally identifies the mode (License masking is based on this number and link configuration negotiates this number)

57 14.32-2e42M 32QAM 14 2 42 0 STM0 (51) 3 11860786 1.4

58 14.32-4e38M 32QAM 14 4 38 0 STM0 (51) 3 11841266 1.2

59 14.32-8e30M 32QAM 14 8 30 0 STM0 (51) 3 11868594 1

60 14.32-16e14M 32QAM 14 16 14 0 STM0 (51) 3 11868594 0.8

61 14.32-18e10M 32QAM 14 18 10 0 STM0 (51) 3 11850809 0.5

82 28.32-95M 32QAM 28 0 95 0 2*STM0 4 23628743 0.5

83 28.32-2e90M 32QAM 28 2 90 0 2*STM0 4 23574521 0.5

84 28.32-4e86M 32QAM 28 4 86 0 2*STM0 4 23550663 0.5

85 28.32-8e78M 32QAM 28 8 78 0 2*STM0 4 23627442 0.5

86 28.32-16e61M 32QAM 28 16 61 0 2*STM0 4 23625273 1

87 28.32-18e57M 32QAM 28 18 57 0 2*STM0 4 23592740 1

88 28.32-32e29M 32QAM 28 32 29 0 2*STM0 4 23580160 0.4

89 28.32-42e8M 32QAM 28 42 8 0 2*STM0 4 23602283 0.5

119 28.64-16e86M 64QAM 28 16 86 0 STM1 5 24276847 0.5

120 28.64-18e82M 64QAM 28 18 82 0 STM1 5 24252003 0.5

131 28.128-2e144M 128QAM 28 2 144 0 STM1 5 25439742 2

132 28.128-4e136M 128QAM 28 4 136 0 STM1 5 25472695 7

133 28.128-8e128M 128QAM 28 8 128 0 STM1 5 25500000 6.5

134 28.128-16e112M 128QAM 28 16 112 0 STM1 5 25455748 7

135 28.128-18e112M 128QAM 28 18 112 0 STM1 5 25455748 3

136 28.128-32e88M 128QAM 28 32 88 0 STM1 5 25506591 1.3

137 28.128-42e68M 128QAM 28 42 68 0 STM1 5 25500000 1.3

138 28.128-63e26M 128QAM 28 63 26 0 STM1 5 25500000 0.5

139 28.128-1s 128QAM 28 0 0 1 STM1 5 25472382 0.6

140 28.128-P55-100M 128QAM 28 0 55+100 0 STM1 5 25474265 0.5

141 28.128-P78-77M 128QAM 28 0 78+77 0 STM1 5 25500000 0.5

Row

ID

New

Mod

es N

ame

(BW

.Mod

-#e#

M#s

)

Mod

ulat

ion

Sign

al B

andw

idth

[M

Hz]

Payload Mix

ETSI

Nom

inal

BitR

ate

(Req

)

Min

imum

requ

ired

Lice

nse

Leve

l

Sym

bol R

ate

(Bau

d R

ate)

ba

ud

EMS

[Mbi

t/s]

E1#

Eth

Mbi

t/s

STM

1 #

Table 8 Modulations, Channel bandwidth and supported payloads (Cont.)



Mode Name: It it the name of the mode displayed by GUI in the choice list:

<bandwidth>.<modulation>-<number of E1>e<Eth Mbps>M<number of STM1>s

Where:

<bandwidth>= Bandwidth value in MHz

<modulation> = Modulation levels, 4 for QPSK, 16 for 16QAM, etc…

e = short notation for E1

M = short notation for Mbps

s = short notation for STM1

Examples:

• 28.128-8e128M = 28MHz bandwidth, 128QAM that transports 8E1 and 128Mbps of Ethernet payload

• 56.128-16e100M1s = 56MHz bandwidth, 128QAM that transports 16E1, 100Mbps of Ethernet and 1 STM1.

There is one exception: the PLUS modes are named by inserting "Plus" after modula-tion. The "Plus" tag is followed by the Mbps configured for Port1 and Port2 respectively:

<bandwidth>.<modulation>-P<Eth Mbps for Port1>-< Eth Mbps for Port2>M

☞ In the configurations implementing the Gigabit Ethernet Master I/O module (P/N 612-315/10) the PDH capacities higher than 2xE1 need the additional use of the 16xE1 Expansion I/O module (P/N 612-315/05), which requires the 18xE1 mode. No intermediate capacities (example 4xE1, 8xE1 or 16xE1) can be selected.

5.2 Basic configurationsThe available configurations are listed in the following Table 9.

5.2.1 Standard terminalIn this configuration the equipment consists of:

– One ODU– One Antenna– One IDU– One coaxial cable for IDU-ODU interconnection

Type Description Channeling

1 1+0 (standard) terminal AP

2 1+1 protected diversity terminal AP

3 1+1 protected non diversity terminal (Hot Standby) AP

4 East-East (2+0 same destination) AP

5 East-West (2+0 different destination or Ring) AP

Table 9 Configurations


33


Figure 13 1+0 (Standard) terminal

5.2.2 Protected terminalThe equipment consists of:

– Two ODUs– One or two antennas– One IDU– One coaxial cable for each IDU-ODU interconnection

Following options are available for protected configuration:

– Hot Stand-by– Frequency Diversity– Space diversity

With two modems and two power supplies installed, the “FlexiHybrid” can also support 1+1 protection in a single 1 RU chassis as an option for a critical link.

The “FlexiHybrid” contains two power supplies and two modems. The power supply, ODU, IF/telemetry and modem are protected. The digital framing and LIUs are not. One modem is referred to as the west modem and the other as the east modem. 1+1 protec-tion can be run in two modes: Protected Non-Diversity and Protected Diversity.

1+1 protected diversityIn this case the link between each pair of modems is the same, providing complete redundancy.

This arrangement requires bandwidth for both links and non-interference between the links, but it provides hitless Rx and Tx switching.

The IDU supports both frequency and spatial diversity.

• Frequency diversity: two frequencies are used • Spatial diversity: one transmitter and two receivers (one in standby). Two non-inter-

fering paths are used

In either case, the proprietary framer chooses the best, or error-free, data stream and forwards it to the Line Interface Units (LIUs).



A 1+0 link may be provided as 1+1 link, allowing the standby MODEM and Power-Supply to be installed at a later date. Once installed, 1+1 protection will immediately be available.

In the Protected Diversity mode, the link between each pair of modems is the same, as shown in Figure 14, providing complete redundancy. This arrangement requires band-width for both links and non-interference between the links, but it provides hitless receive and transmit switching.

The “FlexiHybrid” supports both frequency and spatial diversity.

Figure 14 1+1 protected diversity mode

Frequency DiversityIn frequency diversity, two frequencies are used to achieve non-interference. The pro-prietary framer chooses the best, or error-free, data stream and forwards it to the Line Interface Units (LIUs).

Spatial DiversityIn spatial diversity, two non-interfering paths are used. The proprietary framer chooses the best, or error-free, data stream and forwards it to the Line Interface Units (LIUs).

• Single Transmitter: Protected Non-Diversity, or Hot Standby, is also refered to as Single Transmitter Spatial Diversity.

• Dual Transmitter:When using Dual Transmitter Spatial Diversity, two active transmitters are physically isolated toavoid crosstalk.

Protected Non-Diversity (Hot Standby)Figure 15 shows operation in the Protected Non-Diversity mode, also called Hot Standby. In this mode, one ODU at each location transmits to two ODUs at the other location. This mode does not require the extra bandwidth or interference protection. It provides hitless receive switching and hot standby. “FlexiHybrid” automatically switches transmit ODU upon appropriate ODU alarm or ODU interface error, minimizing transmit outage time.


35


Figure 15 1+1 protection in non-diversity mode

In this case one ODU at each location transmits to both two ODUs at the other location.

This arrangement does not require the extra bandwidth or interference protection of diversity mode and provides hitless receive switching and hot standby.

IDU automatically switches transmit ODU upon appropriate ODU alarm or ODU inter-face error, minimizing transmit outage time.

The power supply, ODU, IF/telemetry and modem are protected.

The digital framing and LIUs are not protected.

A 1+0 link may be provided as 1+1 link, allowing the standby MODEM and Power-Supply to be installed at a later date. Once installed, 1+1 protection will be immediately available.

The received signals are separately decoded, and a switch operating at base band level selects one of the two data streams.



5.2.3 Ring configuration (East-West)RING system type is characterized by two different radio directions and it employs two ODUs.

Ring configuration creates a self-healing redundancy that is more reliable than tradi-tional point-to-point networks.

Protection consists of two paths through the ring, the Active path (blue) and the Stand-by path (red). In case of outage, traffic is automatically rerouted from the Active to the Stand-by path on either side of the outage, thus recovering service interruption.

Figure 16 Ring

Ring configuration can be used to protect E1 circuits, as well as Ethernet payload.


37


5.3 Equipment compositionTable 10 below shows the composition of the equipment and it is used to transmit in all the available bands.

☞ Note 1: To interface the E1 tributaries between the FlexiHybrid and the station equipment are available the patch panels to be installed in the same ETSI rack.

☞ Note 2: The type of waveguide connection between the ODU and the antenna can be either flexible or elliptical.

☞ Note 3: The coupler can be balanced or unbalanced.

Indoor Section Outdoor Assembly

ETSI Rack

IDU Assembly

Patch panels

6L GHz

6U GHz

7 GHz

8 GHz

11 GHz

13 GHz

15 GHz

18 GHz

23 GHz

26 GHz

32 GHz

38 GHz

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP/CC

HC AP

HC AP

Table 10 Equipment composition

Configuration Name Ref. to Figure

1+0 1+0 system with integrated antenna Figure 17

1+0 system with independent antenna Figure 18

1+1 HSBY/FD 1+1 system with Hot Standby or FD with integrated antenna Figure 19

1+1 system with Hot Standby or FD with independent antenna Figure 20

1+1 DP 1+1 system with dual polarization with adjacent channels Figure 21

1+1 SD 1+1 spatial diversity system with two independent antennas Figure 22

East-West 2+0 system with different destinations or Ring with integrated antennas Figure 23

Table 11 Equipment composition according to the configuration



Figure 17 1+0 system with integrated antenna

INTEGRATED ANTENNA30 cm or 60 cm

COAXIAL CABLE

ETSI RACK (19”)

IDU

HC AP/CC ODU

HC AP ODU


39


Figure 18 1+0 system with independent antenna

COAXIAL CABLE

ODU FRAME

FLEXIBLEWAVEGUIDE

ETSI RACK (19”)

IDU

HC AP ODU

HC AP/CC ODU



Figure 19 1+1 system with Hot Standby or FD with integrated antenna

COAXIAL CABLE

1+1 INTEGRATED SUPPORTING FRAME

HC AP/CC ODU

ETSI RACK (19")

IDU

HC AP ODU


41


Figure 20 1+1 system Hot Standby or FD with independent antenna

COAXIAL CABLE

ETSI RACK (19”)

1+1 FRAME

FLEXIBLEWAVEGUIDE

HC AP/CC ODU

IDU

HC AP ODU



Figure 21 1+1 system with dual polarization

ODU FRAME

FLEXIBLEWAVEGUIDE

HC AP/CC ODU

COAXIAL CABLE

ODU FRAME

HC AP/CC ODU

HC AP ODU

ETSI RACK (19")

IDU


43


Figure 22 1+1 SD system with two separated antennas

ODU FRAME

FLEXIBLEWAVEGUIDE

COAXIAL CABLE

HC AP/CC ODU

HC AP ODU

ETSI RACK (19")

IDU

HC AP ODU

HC AP/CC ODU

ODU FRAME

FLEXIBLEWAVEGUIDE



Figure 23 East-West (2+0 system with different destinations or Ring) with integrated antennas

COAXIAL CABLE


HC AP/CC ODU

HC AP/CC ODU

ETSI RACK (19”)

IDU


HC AP ODU


45


5.4 Link Terminals with different configurationA link composed of two IDUs equipped with different HW modules can be setup (this link is called Mixed Link). This type of link allows using different payload interfaces for the two network elements (for example, STM1 interface in one terminal and 32 E1 interface in the other one).

Figure 24 Link terminals with different configuration

A mixed link is ensured by the fact that the configurations of the two terminals are over the air compatible. This requires that the following conditions are met:

1. The two modems are configured with compatible Modes files: the same RowIDs contain the same configuration for modem and payload parameters (and obviously the same mode is selected).

2. The Master IO modules of the IDUs have compatible framer structure.

Table 12 and Table 13 summarize the master IO modules with the over the air compat-ibility (starting from the SVR this is ensured).

Master Module equipped in IDU 2

Stan

dard

M

aste

r I/O

Enha

nced

M

aste

r I/O

42E1

M

aste

r I/O

Gig

E M

aste

r I/O

Stan

dard

2 M

aste

r I/O

Enha

nced

2 M

aste

r I/O

EnhG

igE

Mas

ter I

/O

Mas

ter M

odul

e eq

uipp

ed in

IDU

1

Standard Master I/O

From SVR 1.0

- - - - - -

Enhanced Master I/O

From SVR 1.0

From SVR 1.1

- - - - -

42E1 Master I/O

From SVR 1.2

From SVR 1.2

From SVR 1.2

- - - -

GigE Master I/O

From SVR 1.2

From SVR 1.2

From SVR 1.2

From SVR 1.1

- - -

Standard2 Master I/O

From SVR 2.1

From SVR 2.1

From SVR 2.1

From SVR 2.0

From SVR 2.0

- -

Enhanced2 Master I/O

From SVR 2.1

From SVR 2.1

From SVR 2.1

From SVR 2.0

From SVR 2.0

From SVR 2.0

-

EnhGigE Master I/O

From SVR 2.1

From SVR 2.1

From SVR 2.1

From SVR 2.0

From SVR 2.1

From SVR 2.1

From SVR 2.1

Table 12 Over the air compatibility for Master IO modules (link terminals are intended to have the same SVR)



☞ Table 13 summarizes which SVRs are over the air compatible. Note that it describes cases where different SVRs are loaded on the two link terminals. Although this con-dition is not supported as standard working condition it shall be considered during SVR upgrade phase, mostly if the upgrade is performed from remote site.

5.5 Ethernet payload ProcessingThe characteristics of Ethernet payload processing and features strictly depend on the equipped Master IO Module type.

There are seven types of Master IO:

– Standard Master IO– Standard2 Master IO– Enhanced Master IO with STM-1 – Enhanced2 Master IO with STM-1 – GE Master IO– GE Enhanced Master IO– 42xE1 Master IO

☞ The Ethernet payload processing of the Enhanced GigaE Master IO Module is the same of the GigaE Master IO Module.

The characteristics of Ethernet payload processing and features strictly depend on the equipped Master IO Module type. Standard2 and Enhanced2 Modules employ the same Ethernet switch and the same Ethernet payload processing as the 42E1 Master IO Module. For better readability, the Ethernet processing of the new modules is reported here, highlighting the differences from the Standard and Enhanced Master IO modules.

SVR loaded in IDU 2

SVR 1.0 SVR 1.1 SVR 1.2 SVR 1.3 SVR 1.4 SVR 2.0 SVR 2.1 SVR 2.2

SVR loaded in IDU 1

SVR 1.0 Yes - - - - - - -

SVR 1.1 No Yes - - - - - -

SVR 1.2 No No Yes - - - - -

SVR 1.3 No No Yes Yes - - - -

SVR 1.4 No No No Yes Ye - - -

SVR 2.0 No No No No Yes Yes - -

SVR 2.1 No No No No Yes Yes Yes -

SVR 2.2 No No No No Yes Yes Yes Yes

Table 13 Over the air compatibility for Master IO modules (link terminals are intended to have the same SVR)


47


5.5.1 Maximum bit rate over the air

A) Standard/Standard2 Master IO / Enhanced/Enhanced2 Master IO / 42xE1 Master IO characteristics

Payload rate can be increased up to 155Mbps by configuring the "Plus" mode (78 Mbps for Ethernet port 1 + 77 Mbps for Ethernet port 2 or 55 Mbps for Ethernet port 1 + 100 Mbps for Ethernet port 2): in this mode Ethernet payload rates of 155 Mbps can be achieved by utilizing both 100Base-TX front panel payload ports. In this configuration, two Ethernet channels are provided in the payload frame using internal Port-based VLAN (not accessible or configurable by the user).

The max traffic rate for each Ethernet channel to the framer is defined in the modes file. A user is not allowed to use these modes in a 2+0 (East/West) configuration.

Two applications are possible:

• two-network operation • single-network operation (this does not correspond to a different IDU configuration

but it is based on the usage of an external router).

Single Network Operation This configuration is considered with an external router in mind. This configuration is really an extension of the mode described above. There are no changes in the program-ming or operation of the IDU. This mode allows a user to transmit data from a single network at a rate greater than 100 Mbps. The external router is required to handle the management of the trunk. The router must ensure that the same MAC address is not delivered to both front panel ports. The setup for single network operation is shown in Figure 25.

They have 2 E/FE interfaces and the maximum supported rate over the air is up to 100Mbps for each radio interface 1)

1) The limitation to 100Mbps radio-side is determined by the framer capacity used in this module



Figure 25 Single Network Operation

Two-Network OperationThis mode allows the operator to provide access to two separate Fast Ethernet users, and guarantee the throughput level for each. Different rates for each port are supported, as configured in the modes file. In this mode, each channel operates as a single channel would in a single port mode. The setup for two-network operation is shown in Figure 26.


49


Figure 26 Two-Network Operation

B) GigEth and GigEth Enhanced Master IO characteristics:

This module has 4 10/100/1000 Mbps electrical Ethernet ports + 1 GigaEthernet SFP. The maximum supported payload rate over the air is 300Mbps for each radio interface 1)

1) From SVR 1.1 the widest supported signal bandwidth is 28MHz, therefore the 300Mbps cannot be reached even when the 128QAM modulation is used.

There is the possibility to increase the payload rate up to 155 Mbps by configuring the “Plus” mode (78 Mbps for Ethernet ports 1 and 2 + 77 Mbps for Ethernet ports 3 and 4 or 55 Mbps for Ethernet ports 1 and 2 + 100 Mbps for Ethernet ports 3 and 4. The SFP can be associated to the first port group or to the second port group): in this mode Ethernet payload rates of 155 Mbps may be achieved by utilizing the front panel payload ports. In this configuration, two Ethernet channels are provisioned in the payload frame and are associated to each interface.

The max traffic rate for each Ethernet channel to the framer is defined in the modes file. The available Plus modes contains rate up to 155Mbps. A user cannot use Plus modes in a 2+0 (East/West) configuration.



5.5.2 Port SettingAutonegotiation is supported for each interface. It can be Enabled and Disabled by the user.

When disabled the following parameters can be set by the user:

– Port Speed: For Standard/Standard2/Enhanced/Enhanced2/42xE1 Master IO the possible values are 10 or 100Mbps. For GigEth Master Io the possible values are 10, 100 or 1000Mbps.

– Port Duplex: possible values are Half and Full

When enabled the parameters value after the autonegotiation procedure is not available via WEB-LCT.

Flow Control is supported; it can be configured as Disabled or Symmetric (Enable). When enabled the IDU slows the egress from the Ethernet switch which will initiate flow-control via the front-panel ports. The scaling of Ethernet traffic will in effect limit the front-panel egress rate on the far end of the link. Flow control is supported in both full-duplex and half-duplex. Full-Duplex is implemented with respect for PAUSE packets as well as generation of PAUSE packets. Half-Duplex is implemented with back-pressure.

Ingress rate-limiting per front-panel port is not supported.

Master-Slave mode for clock is supported (in GigEth and GigEth Enhanced Master IO); it can be configured as Auto, Slave or Master mode.

The possibility to disable the Ethernet ports is not supported.

Shutdown port in Link failureWhen this is enabled, the output of Ethernet port is shut down if the radio link is down. After the restoring of the radio link the Ethernet port is automatically activated. It can be enabled or disabled by the user on per port basis (It is supported for all the master mod-ules).

5.5.3 Learning functionalityWithin the Standard2 and Enhanced2 Ethernet switch, the MAC DB can learn up to 1024 MAC Addresses, as in 42E1 Master IO Module, while both the Standard and Enhanced allowed up to 4096 MAC addresses in their MAC database.

It is not possible to add static entries and the MAC table is not available for the user.

Ageing time is not configurable and is fixed to 300 seconds.

5.5.4 Ethernet Latency

Packet size Minimum Latency (mS ) (64 bytes)

MaximumLatency(mS) (1518 bytes)

10 3.25 4.65

70 0.52 0.92

100 0.37 0.73

Table 14 Standard and Enhanced Master I/O Card


51


5.5.5 Throughput and Back-to-Back LimitsThe following tables contain the throughput and back-to-back limits related to the Fast Ethernet ports of the Standard2 and Enhanced2 IO Modules in case of error-free radio

Packet size Minimum Latency (mS ) (64 bytes)

MaximumLatency(mS) (1518 bytes)

10 3.29 4.60

50 0.72 1.09

100 0.42 0.68

150 0.26 0.37

200 0.19 0.28

Table 15 Gigabit Master I/O Card

Packet size Avarage Latency(µs)

64 430.2

128 451.7

256 493.1

512 574.6

1024 738.1

1280 820.2

1518 896.9

Table 16 42xE1Master I/O Card

Average Latency [µs]

Frame Size (bytes)

Ethernet Capacity

8 Mbit/s 26 Mbit/s 82 Mbit/s

64 560.2 301.6 334.4

128 638.4 334.5 354.7

256 785.0 403.8 399.5

512 1084.5 544.2 487.3

1024 1700.1 820.4 658.0

1280 1986.8 961.1 746.4

1518 2269.4 1094.2 826.5

2048 2903.2 1375.7 1002.5

Table 17 Latency on Standard2 and Enhanced2 IO Modules



channel (the same values apply also to the 42E1 Master IO module but not to former Standard and Enhanced modules). These values do not depend on the overall radio capacity, but to the capacity reserved to the Ethernet traffic.

Throughput [%]1)

1) The throughput values are based on the percentage of total line utilization which includes the Preamble (7 octets), Start of Frame Delimiter (SFD) (1 octet), Frame Check Sequence (FCS) (4 octets) and Inter Packet Gap (IPG) (12 octets). The frame size shown in the leftmost column includes the FCS, but excludes the Preamble, SFD and IPG (20 octets total).

Frame Size (bytes)

Ethernet Capacity


64 10.63 33.20 99.41

128 9.38 30.02 93.38

256 8.75 28.13 87.62

512 8.75 27.51 85.05

1024 8.12 26.86 83.79

1280 8.11 26.86 83.15

1518 8.11 26.86 83.18

2048 8.31 27.5 83.13

Table 18 Throughput on Standard2 and Enhanced2 IO Modules (%)

Throughput [Mbit/s]1)

1) The throughput values are based on the percentage of total line utilization which includes the Preamble (7 octets), Start of Frame Delimiter (SFD) (1 octet), Frame Check Sequence (FCS) (4 octets) and Inter Packet Gap (IPG) (12 octets). The frame size shown in the leftmost column includes the FCS, but excludes the Preamble, SFD and IPG (20 octets total).

Frame Size (bytes)

Ethernet Capacity


64 8.1 25.3 75.7

128 8.1 26.0 80.8

256 8.1 26.1 81.3

512 8.4 26.5 81.9

1024 8.0 26.3 82.2

1280 8.0 26.4 81.9

1518 8.0 26.5 82.1

2048 8.2 27.2 82.3

Table 19 Throughput on Standard2 and Enhanced2 IO Modules (Mbit/s)


53


5.5.6 Max packet sizeThe maximum packet size depends on the module type:

– Standard and Enhanced Master I/O card: Max packet size is 1536 bytes.– Standard2 and Enhanced2 Master I/O card: Max packet size is 2048 bytes.– GigEth Master IO card: Max packet size is 4000 bytes.– 42xE1 Master IO card: Max packet size is 2048 bytes.

5.5.7 Buffer sizeEthernet Buffer (Standard IO modules and Enhanced IO module)

– Layer 2 Ethernet switch contains 160 Kbytes of buffer– Divided into 640 blocks of 256 bytes– Blocks are dynamically allocated

Ethernet Buffer (GigEth Master IO module)

– Layer 2 Ethernet switch contains 128 Kbytes of buffer– Divided into 512 blocks of 256 bytes– Blocks are dynamically allocated

Ethernet Buffer (Standard2, Enhanced2, 42xE1 Master IO module)

– Total on-chip memory in Ethernet switch is 64 Kbyte

5.5.8 Counters, Link monitoringLink capacity is not variable and link capacity monitoring is not available. Packet moni-toring is provided in the form of Ethernet switch statistics (i.e. Tx Packets, Tx Bytes, Tx Errors, Rx Packets, Rx Bytes, Rx Errors).

Link Loss Failure (LLF) not supported.

Frame Size (bytes)

Ethernet Capacity


64 99 130 1270926

128 73 87 663

256 59 80 390

512 51 63 318

1024 27 35 139

1280 18 23 81

1518 18 22 87

2048 12 16 59

Table 20 Back-to-back frames limits on Standard2 and Enhanced2 IO Modules



5.5.9 QoS

5.5.9.1 QoS in Standard and Enhanced Master IO modules

Priority Assignment: For each frame entering the Ethernet user interface (Port1 or Port2) the following priority criterias are applied:

– Port-based– 802.1Q VLAN TAG priority– IPv4 ToS priority (first 3 bits of the DiffServ field)

Each criteria can be Enabled and Disabled (global setting) and the user can select which QoS criteria shall be resolved first (Priority Resolution configuration).

The Ethernet switch used on the Standard and Enhanced Master IO Module provides 2 switch priority levels (0-lowest, 1-highest). Each criterion can be assigned to one Switch Priority (refer to Figure 27).

Output queues:The radio port contains two independent output queues (High and Low).

Weighted Fair Queue ratios are fixed for 802.1Q VLAN TAG priority and for IPv4 TOS (even though they are selectable via the Web GUI).

Figure 27 Priority assignment logic scheme (Standard and Enhanced Master IO Modules)


55


5.5.9.2 QoS in Standard2, Enhanced2 and 42xE1 Master IO modules

Priority Assignment: For each frame entering the Ethernet user interfaces (Port1 and Port2) the following priority criteria are applied:

– Port-based– 802.1Q VLAN TAG priority– DiffServ priority

Each criterion can be Enabled or Disabled (global setting) with the following constraints:

– When Port-based is Enabled the other two criteria are automatically set to Disabled

– When Port-based is Disabled the other two criteria can be Enabled or Disabled (separately or both at the same time).

When 802.1Q and DiffServ priorities are Enabled, the user can select which QoS crite-rion shall be resolved first (Priority Resolution configuration) between 802.1Q VLAN and DiffServ priority.

Each frame entering the Ethernet user interface can be associated to one Tx output queue (refer to Figure 28).

Output queues:The Radio port (that is the internal switch interfaces connected to the Radio link) contains four independent output queues. The order the frames are transmitted out each port depends on the scheduling mode.

The unit supports:

– Weighted Fair Queuing (WFQ) scheduling modes with fixed weights 8, 4, 2, 1 (the user cannot configure them).

– Strict Priority Scheme: the Preemption of highest priority queue is available . It can be enabled or disabled by the user; when the Preemption is enabled the highest priority queue is serviced until it is empty before servicing lower priority queues.



Figure 28 Priority assignment logic scheme

5.5.9.3 QoS in GigEth and GigEth Enhanced Master IO module

Priority Assignment: For each frame entering the Ethernet user interfaces (Port1, Port2, Port3, Port4 and SFP) the following priority criteria are applied:

– Port-base– 802.1Q VLAN TAG priority– DiffServ priority

Each criterion can be wholly enabled or disabled. It is not possible to enable or disable the criteria on a per port-base.

When multiple priority schemes are enabled, the priority, determined for a specific packet, will be the highest available priority.

The Ethernet switch used on the GigEth Master IO module provides 8 switch priority levels (from 0-lowest to 7-highest). Each criterion can be assigned to one level (as sche-matically shown in Figure 29). (The granularity of 8 switch priorities could be used, for example, to mitigate priority conflicts between port priorities and DiffServ priorities).

Each Switch Priority level can be associated to a Tx priority queue for the transmission over the Radio link.

Output queues:The Radio ports (i.e. the internal switch interface connected to the Radio link) contain four independent output queues, one corresponding to different priority levels. The order with which the frames output each port depends on the scheduling mode.


57


The unit supports:

– Weighted Fair Queuing (WFQ) scheduling modes with configurable weights from 1 to 49.

– Preemption of highest priority queue can be enabled or disabled by the user; when the Preemption is enabled, the highest priority queue (queue 3) is serviced until it is empty. The lower priority queues are always serviced with the WFQ scheduling mode.

Figure 29 Priority assignment logic scheme



5.6 VLAN ManagementIn SVR 2.2 the support of single and double tag VLAN management is available.

5.6.1 HW/SW compatibility for VLAN Management functionlaityThe Ethernet payload manipulation is performed by the Ethernet switch device housed in the Master IO module. The VLAN Management as described in the following is sup-ported by the following Master IO and Controllers:

– Controller– Controller2– Standard2 Master IO– Enhanced2 Master IO– GigE Master IO– EnhGigE Master IO– 42E1 Master IO

Consequently, all the IDU combinations that has one of the Master modules listed here above support the VLAN manipulation functionalities.

Even if the Master modules adopt different Ethernet switch device ( ), if not differently specified, at user level the functionalities here described are intended to be the same for all the master modules.

When a Master Module that do not support the VLAN management is plugged (i.e.: Standard or Enhanced Master IO) the Ethernet payload management and relevant con-figuration parameters remain the same as previous SVRs. In particular the GUI shall not show configurations that are not supported.

The only exception is for Port Based Forwarding mode that in SVR 2.2 is extended also to Standard and Enhanced Master IO.

5.6.2 Ethernet Ports IdentificationThe number and type of available Ethernet ports depend on the type of the equipped Master module and on the system configuration. Table 21 shows when the possible Ethernet ports are available and the names that will be used in the present document.

Port Name When the port is available Physical Position

Equipped Master Module System Type

Port1 With all Master IO All Connector "1" of the Master IO front panel

Port2 With all Master IO All Connector "2" of the Master IO front panel

Port3 GigE OR EnhGigE All Connector "3" of the Master IO front panel

Port4 GigE OR EnhGigE All Connector "4" of the Master IO front panel

PortSFP (GigE OR EnhGigE) AND SFP module is equipped

All Connector "SFP" of the Master IO front panel

PortEast With all Master IO All Internal port, connected to the East Radio direc-tion, i.e. modem equipped in the Lower slot

Table 21 Ethernet Ports Identification


59


In the following the "Front Panel Port" will be used to indicate all the available ports of the front panel. Available Port East and Port West will be referred also as Radio or Trunk ports.

5.6.3 VLAN Management EnablingTo enable the VLAN manipulations and functionalities the global configuration "VLAN Management" is available to the user via LCT and via SNMP with the choice list described in Table 22.

In the following the actions and equipment behavior adopted for each case of VLAN Management are described

5.6.4 Default VLAN-ID configurationWhen the VLAN Management is different from "Disable", it is possible, per each avail-able port, to configure the Default VLAN ID assigned to the port. The Default VLAN ID is the value inserted in the VLAN tag added by the FHy. By default all ports are associ-ated to the DEFAULT group with VID=1.

The p-bit value to be used in the added tag is user configurable too. Note that the user cannot modify the p-bit in the tag that is already present in the ingress frame (replace-ment is not supported).

5.6.5 Behaviour for p-bit configurationIn the GigE and EnhGigE implementation the value of the p-bit is determined on the base of the Port priority value and cannot be independent. Note that the Web-LCT auto-matically aligns the port priority value to the p-bit value and vice versa, when the user change one of the two parameters.

PortWest With all Master IO 1+1, East/West, East/East

Internal port, connected to the West Radio direction, i.e. modem equipped in the Upper slot

Port Name When the port is available Physical Position

Equipped Master Module System Type

Table 21 Ethernet Ports Identification (Cont.)

Parameter Possible Values Description

VLAN Management

Disable VLAN manipulation is not enabled (Default)

Single Tag The equipment is configured to manage a single tag only

Double Tag (Stag + Ctag) "Stag + Ctag" means that the Q-in-Q as per 802.1ad is applied. The external S-tag has Ether-Type = 88-a8 The inner C-tag has the Ether-Type = 81-00

Double Tag (Ctag + Ctag) "Ctag + Ctag" means that two 802.1q tags are managed. The same Ether type = 81-00 is used in both tags

Table 22 VLAN Management Configuration



In the other modules (42E1, Standard2, Enhanced2) the default port p-bit can be spec-ified by the user. For the management of the p-bit within the transport network with those modules see paragraph 5.6.9.1.

5.6.6 Ingress PolicyThe possible Ingress Policy parameters are available to the user only in some cases of VLAN Management.

5.6.6.1 Single Tag modeWhen VLAN Management is equal to "Single Tag", the user can configure, per each Front Panel Port, which frame type can be admitted to the switch. This parameter is here referred as Ingress Policy and it is described in Table 23.

☞ The setting is available also via SNMP.

Parameter Possible Values Description When available

Ingress Policy Admit All All the frame types are admitted to enter the switch. (Default)

– VLAN Management = Single Tag – For Front Panel Ports only

Tagged Only Only tagged frames (with outer VLAN tag as per 802.1q) are admitted to enter the switch. The other frames are recognized as not tagged and dropped.

Note: Radio ports are always configured as "Admit all" (no user configurable).

Table 23 Ingress Policy Configuration

VLAN Management

value

Entering Frame type

Applied VLAN manipulation

Disable Unmodified

Single Tag Untagged If Ingress Policy = "Tagged only" if entering frame type is "untagged" then the packet will be dropped.

If Ingress Policy = "Admit all" if entering frame type is "untagged" then it will be tagged with the default VID of the Ingress port.

Single tagged Unmodified.

If the VLAN-ID does not match any VLAN associated to the ports the packets are dropped.

Table 24 Ingress frame Manipulation in Single Tag mode


61


Refer to paragraph 5.6.10 for the guideline about when and how this mode shall be con-figured.

5.6.6.2 Double Tag modeWhen VLAN Management is equal to Double Tag ("Double Tag (Stag + Ctag)" or "Double Tag (Ctag + Ctag)") a different parameter is available to the User, it is here named "Port DoubleTag Mode". It is configurable for each Front Panel Port and Table 25 contains the description of the possible values.

Note that also the Egress policy is configured with the Port DoubleTag Mode parameter (see par. 5.6.8).

Once entered the switch each frame is processed in order to apply the desired VLAN manipulation.

Double Tag (Stag + Ctag)

If Ingress Policy = "Tagged only" if entering frame type is "Double Tag (Stag + Ctag)" then the packet will be dropped.

If Ingress Policy = "Admit all" if entering frame type is "Double Tag (Stag + Ctag)" then another outer tag (C tag) will be added since the VLAN operates as per 802.1q standard and the frame entered is non com-pliant (i.e. outer tag has not the Ether Type equal to 81-00).The switch considers it as untagged packet and adds the tag with default VID of the ingress port.

Double Tag (Ctag + Ctag)

Unmodified.

If the VLAN-ID does not match any VLAN associated to the ports the packets are dropped.

VLAN Management

value

Entering Frame type

Applied VLAN manipulation

Table 24 Ingress frame Manipulation in Single Tag mode (Cont.)


Port Double-Tag Mode

User An additional tag is always added to the ingress frame, regardless the type of incoming frame. In case of frames that are already double tagged an extra tag is added. (Default)

– VLAN Management = Double Tag (Stag + Ctag) OR Double Tag (Ctag + Ctag).

– For Front Panel Ports only

Network The extra tag is added if the outer tag format of the entering frame is not according to the tag format in VLAN Management.

Note: The Radio ports are always set as Network port and different selection is not available to the user.

Table 25 Port Double Tag Mode Configuration



The tagging or un-tagging management of frames entering the switch is not explicitly user configurable but it is implicitly defined by the VLAN Management parameter. Table 26 summarizes the applied Ingress frame manipulation for each configuration.

Applying the abovementioned tables the behaviour across a radio link is described here below in Figure 30, Table 27 and Table 28."U" means that the port is configured as User. "N" means that the port is configured as Network

Figure 30 1+0 Radio link

Port Double Tag Mode

Action at Ingress Action at Egress

User An outer tag is always added:

C-tag in case of Double Tag (Ctag + Ctag)

S-tag in case of Double Tag (Stag + Ctag)

The outer tag is always removed

Network Unmodified if the outer tag type is

– C-tag in case of Double Tag (Ctag + Ctag)– S-tag in case of Double Tag (Stag + Ctag)

Otherwise an additional tag is added (1))

If the outer VLAN-ID does not match any VLAN associated to the ports the packets are dropped.

1) Note that this case should not happen if the network is properly configured because the packets enter the transport network via a User port and consequently at each network port they have already been tagged with the proper tag.

Unmodified

Table 26 Ingress frame manipulation in Double Tag mode

Ingress at U1 port Egress at N1 port Ingress at N2 port Egress at U2 port

Untagged S tagged S tagged Untagged

C-tagged S+C tagged S+C tagged C-tagged

S+C tagged S+S+C tagged S+S+C tagged S+C tagged

C+C tagged S+C+C tagged S+C+C tagged C+C tagged

Table 27 Double tag (Stag + Ctag) mode: frame formats at both User and Network ports


63


The cases above can be easily extended also to the cases where the NE is in East/West configuration.

Refer to paragraph 5.6.10 for the guideline about when and how this mode shall be con-figured.

5.6.7 Forwarding ModeTwo forwarding modes are supported:

– Port based– VLAN based

The two forwarding modes cannot be enabled at the same time, but they are automati-cally determined on the base of the VLAN Management configuration. Therefore the selection of the forwarding mode is not User configurable but it is managed as described in Table 29.

5.6.7.1 Port-Based Forwarding ModeWhen the forwarding mode is "Port Based" the user can configure which ports are con-nected to each other. Forwarding is allowed only among connected ports.

Table 30 shows an example of port connection table. "x" means that the port in the row is connected to the port in the column. The connection is bidirectional.

Ingress at U1 port Egress at N1 port Ingress at N2 port Egress at U2 port

Untagged C tagged C tagged Untagged

C-tagged C+C tagged C+C tagged C-tagged

S+C tagged C+S+C tagged C+S+C tagged S+C tagged

C+C tagged C+C+C tagged C+C+C tagged C+C tagged

Table 28 Double tag (Ctag + Ctag) mode: frame formats at both User and Network ports

VLAN Management Applied Forwarding

Mode

Description

Disable Port Based Frames are forwarded on the base of Port connection table and MAC (see par. 5.6.7.1)

Single Tag VLAN based Ports are intended to be fully con-nected and the forwarding is per-formed on the base of VLAN table and MAC address (see par. 5.6.7.2). In case of double tagged frames the value of outer tag is considered.

Double Tag (Stag + Ctag)

Double Tag (Ctag + Ctag)

Table 29 Forwarding modes applied on the base of VLAN Management



The LCT shows a table similar to Table 30 where a radio button permits to enable the connection between the ports.

Figure 31 shows an example of connection scheme and the related table to configure the shown connections.

Figure 31 Example of Port connection configuration

5.6.7.2 VLAN-based Forwarding ModeWhen the forwarding mode is "VLAN based" the user configures the VLAN to be managed and the ports that belong to each VLAN.

It is possible to configure up to 64 different VLANs and per each one the user selects the ports that belong to that VLAN.

The forwarding is allowed only between the ports that belong to the same VLAN

Port1 Port2 Port3 Port4 Port SFP Port East Port West

Port1 x x x

Port2 x x x x

Port3 x

Port4 x

Port SFP x

Port East

Table 30 Port Connection Table


65


5.6.7.3 Forwarding mode behaviourIn Double Tag (Stag + Ctag) mode, when a single tagged frame (C-tagged) enters a Network port it is forwarded on the base of the Inner VLAN tag instead of the outer.

This issue is present in Enhanced2, Standard2 and 42E1 Master IO.

It is not present in the GigE and EnhGigE module.

Figure 32 1+0 Radio link

The behaviour in all cases is in the following tables.

VLAN ID

Port1 Port2 Port3 Port4 Port SFP Port East Port West

Row #1 3 x x x

Row #2 5 x x x

...

Row #64 25 x x

Table 31 VLAN connection Table

From To Forwarding Note

User Network On the base of outer (added S-tag) OK

Network User On the base of outer (added S-tag) except for C-tagged frames that are forwarded on the base of the Inner (C-tag frame)

N-OK.

Anyway, in S+C mode at Network port there should be only frames with outer tag equal to "S" because they should have been injected in the network via a User port.

User User On the base of outer (added S-tag) OK

Table 32 Forwarding behaviour for Standard2, Enh2, 42E1 Master IO



If the network is properly configured, when Double Tag mode (Stag + Ctag) is configured the single C-tagged frames should not be present at Network interface (an outer S-Tag is added to all frames entering via User port), therefore the limitation is acceptable.

5.6.8 Egress PolicyOn the egress side (frames that are leaving the Ethernet switch), in case of VLAN Man-agement is Single tag it is possible to configure if the tag shall be preserved or removed using the Egress Policy configuration. This configuration is available for the Front Panel Ports only.

When the VLAN Management is “Double tag” the egress policy is not configured via a dedicated parameter but it is automatically determined on the base of the Port Double Tag Mode configuration.

Egress policy for each condition is summarized in the following Table 34.

Network Network On the base of outer (added S-tag) except for C-tagged frames that are forwarded on the base of the Inner (C-tag frame)

N-OK.

Anyway, in S+C mode at Network port there should be only frames with outer tag equal to "S" because they should have been injected in the network via a User port.

From To Forwarding Note

Table 32 Forwarding behaviour for Standard2, Enh2, 42E1 Master IO (Cont.)


Egress Policy Remove(Default)

Outer tag is removed – VLAN Management = Single Tag– For Front Panel Ports only

Note that "unmodified" means that the egress processing does not modify the frame as resulting after the ingress policy application.

Don't Remove The frame remains unmodified

Note: For the Radio ports the value is automatically set to "Don't Remove" and it is not user configurable.

Table 33 Egress Policy Configuration

VLAN Management Description of Applied Egress Port Policy

Disable -

Single Tag The tag is removed or don't removed on the base of a dedicated Egress Policy configuration detailed in Table 33

Table 34 Egress Frame manipulation description


67


5.6.9 Quality of Service managementThe following table lists the QoS classification criteria that can be applied for each VLAN Management mode. When the VLAN Management is different from disable the QoS classification criteria take into account the outer VLAN tag value (the tag is logically added on the base of the ingress port and it is added before the QoS classification). In Table 35 the frame type after the application of the Ingress policy is considered.

Double Tag (Ctag + Ctag) OR Double Tag (Stag + Ctag)

If the port has been configured as "Network" (see Table 25) its egress policy is automatically configured to "Don't Remove".

If the port has been configured as "User" (see Table 25) its egress policy is automatically con-figured as "Remove".

VLAN Management Description of Applied Egress Port Policy

Table 34 Egress Frame manipulation description (Cont.)

VLA

N

Man

agem

ent Frame type before the

Ingress policy has been applied

QoS classification criteria that can be applied

Notes

Port P-bit IPv4 ToS or Diff Serv

Dis

able

Untagged Yes - Yes

Single tagged Yes Yes Yes

Double Tag (Stag + Ctag) Yes No No DiffServ Priority does not work on double-tagged packets.Double Tag (Ctag + Ctag) Yes Yes No

Sing

le

Tag

Untagged Yes Yes 1) Yes

Single tagged Yes Yes Yes

Double Tag (Stag + Ctag) Yes No No DiffServ Priority does not work on double-tagged packets.Double Tag (Ctag + Ctag) Yes Yes No

Table 35 Applicable QoS criteria


Solution DescriptionFeaturesD

oubl

e Ta

g (S

tag

+ C

tag)

Untagged frame ingress on User Port

Yes Yes 1) Yes

Untagged frame ingress on Network Port

Yes Yes 1) Yes

Single tagged frame ingress on User Port

Yes Yes Yesfor 42E1, Standard2 and Enhanced2

Nofor GigE and EnhGigE

Single tagged frame ingress on Network Port



Double Tag (Stag + Ctag) frame ingress on User Port

Yes Yes No DiffServ Priority does not work on double-tagged packets on GigE and EnhGigE Master IO modules.

Double Tag (Stag + Ctag) frame ingress on Network Port



3 or more tags frame ingress on User Port

Yes Yes No

3 or more tags frame ingress on Network Port

Yes Yes

VLA

N

Man

agem




Notes


Table 35 Applicable QoS criteria (Cont.)


69


In GigE and EnhGigE Master IO card, if the packet doesn't meet any priority criteria, the switch priority is 0 by default. Each Switch Priority level can be configured to be associ-ated to a Tx priority and the default association for the Switch priority 0 is the lowest priority queue.

For 42E1, Standard2 and Enhanced2 Master IO cards, if the packet doesn't meet any priority criteria, the packet will enter Tx Queue 3 (The highest priority queue).

The same behaviour is present also in previous SVRs.

Dou

ble

Tag

(Cta

g +

Cta

g)

Untagged frame ingress on User Port

Yes Yes 1) Yes

Untagged frame ingress on Network Port

Yes Yes 1) Yes

Single tagged frame ingress on User Port



Single tagged frame ingress on Network Port

Yes Yes Yes

Double Tag (Ctag + Ctag) frame ingress on User Port

Yes Yes No DiffServ Priority does not work on double-tagged packets on GigE and EnhGigE Master IO modules.

Double Tag (Ctag + Ctag) frame ingress on Network Port



3 or more tags frame ingress on User Port

Yes Yes No

3 or more tags frame ingress on Network Port

Yes Yes

1) They will be prioritized based on the default p-bit priority of the ingress port, if p-bit based QoS is enabled.

VLA

N

Man

agem




Notes


Table 35 Applicable QoS criteria (Cont.)



5.6.9.1 Behaviour: p-bit values are overwritten in some casesIn 42E1, Standard2 and Enhanced2 Master modules, when QoS criteria different from p-bit criterion are enable the p-bit of the incoming frames can be overwritten; moreover the p-bit value can be changed on the base of the type of crossed ports and other enable criteria.

The behaviour is here summarized:

In Single tag Mode

– When Port Based or DiffServ criteria are enabled the original p-bit of the incoming frame are overwritten by the equipment.

– When only the p-bit based criterion is enable the behaviour is correct (p-bit of the tagged frames are preserved, untagged frames are tagged with the default p-bit con-figured for the incoming port.

In Double Tag (Stag + Ctag) or Tag (Ctag + Ctag) mode

– At the egress of the transport network the original frame format (i.e.: the p-bit value of he tag or tags) is correctly preserved in any combination of QoS criteria enabling.

– When only port based QoS is enable: the p-bit value of the added outer tag is changed at each port by assigning the default p-bit of the ports the frames go through.

– When only p-bit based QoS is enable: the p-bit value of the added outer tag can be the copy of the inner one or the default value of the port p-bit.

– When DiffServ based QoS only is enable • If the ingress frames are IPv4/IPv6 Untagged or C-tagged the value of p-bit is

determined on the base of the selected TX output queue and consequently they are a sort of re-mapping of the DiffServ value.

• Otherwise the value of p-bit is changed at each port according to the default p-bit priority assigned to the ports.

Suggestions for configurations are contained in par. 5.6.10.2.

5.6.10 Guidelines and Rules for VLAN configurationsSome guidelines and suggestions for proper configuration of the VLAN management are summarized taking into account the system behaviors described in the previous sec-tions.

5.6.10.1 Single Tag mode vs Double Tag modeThe Single Tag mode shall be used when the following assumptions are valid:

– The frames entering the IDU are all of the same type (all tagged or all untagged). The reason is that at the egress side it is not possible to distinguish if the packet entered the network as tagged or untagged and consequently the egress policy (remove or don't remove) can alter the original frame format, e.g.: removing the tag from an originally tagged frame.

– In Single Tag mode the Double tagged frames (C-tag +C-tag) are not supported for the same reason of the pervious point, that is, the frame can be altered at the egress port.

Double tag mode shall be used whenever mixed types of frames are present at the ingress or double tag frames are present.


71


5.6.10.2 Classification criteriaAs described in par. 5.6.9.1, when 42E1, Standard2, Enhanced2 Master IO modules are used p-bit value of the entering frames can be overwritten by the equipment. The following configurations for the classification criteria are suggested:

In Single Tag Mode

– Only the p-bit based criteria has to be enabled (otherwise the original frame format is changed)

In Double Tag Mode

– When p-bit criterion is enable the other criteria shall be disabled– When DiffServ or Port based are enable the p-bit shall be disabled

With GigE and EnhGigE Master IO modules these behavious are not present.

5.6.10.3 Link with mixed configurationsWhen a link with mixed configuration (i.e.: different Master IO type) is present in the two sides of the link the behaviors of both types of Master shall be considered.



5.7 Ethernet Functionality SummaryThis section intends to summarise the characteristics of the Master IO Modules with respect to the Ethernet payload processing.

Master IO Module

Standard Enhanced Standard2 Enhanced2 GigE Enhanced GigE

42E1

User Ports 2 E/FE 2 E/FE 2 E/FE 2 E/FE 4 E/FE/GigE + 1 GigE SFP (el/opt)

4 E/FE/GigE + 1 GigE SFP (el/opt)

2 E/FE

Max Capacity Radio Ports1)

100 Mbit/s 100 Mbit/s 100 Mbit/s 100 Mbit/s 300 Mbit/s 300 Mbit/s 100 Mbit/s

Buffer Size 160 kbytes 160 kbytes 64 kbytes 64 kbytes 128 kbytes 128 kbytes 64 kbytes

Max Packet size

1536 bytes 1536 bytes 2048 bytes 2048 bytes 4000 bytes 2) 4000 bytes 2) 2048 bytes

MAC DB dimension [entry #]

4096 4096 1024 1024 4096 4096 1024

Ageing Time 300 s 300 s 300 s 300 s 300 s 300 s 300 s

Output Queues 3)

2 2 4 4 4 4 4

Scheduling WFQ (2, 1) WFQ (2, 1) WFQ (8, 4, 2, 1)

WFQ (8, 4, 2, 1)

WFQ (1..49) 4)

WFQ (1..49) 4)

WFQ (8, 4, 2, 1)

StrictPrior-ity 5)

StrictPrior-ity 5)

Pre-empt + WFQ

Pre-empt + WFQ

StrictPrior-ity 5)

Port Based Priority

Yes Yes For complete description of Classification criteria see par. 5.6.9 and Table 35

802.1Q VLAN Priority

Yes Yes

IPv4 ToS Priority 6)

Yes Yes

DiffServ Priority

No No

QoS Radio-Radio

No No Yes Yes Yes Yes Yes

Port Based Forwarding

Yes 7) Yes 7) Yes Yes Yes Yes Yes

Plus Modes (in 1+0/1+1)

Yes Yes Yes Yes Yes 8) Yes 8) Yes

2+0 East/West Segregated

Yes (*) Yes (*) Yes 9) Yes 9) Yes 9) Yes 9) Yes 9)

Table 36 Summary of Ethernet Characteristics


73


Description of the Scheduling:

– WFQ (1, 2) = Weighted Fair Queuing, two queues are present with fixed weights (2, 1).

– WFQ (8, 4, 2, 1) = Weighted Fair Queuing, 4 queues are present with fixed weights (8, 4, 2, 1)

– WFQ (1..49) = Weighted Fair Queuing with configurable weights (values from 1 to 49 are available)

– StrictPriority = When Strict priority is enabled, the queues are served in the order Queue 3 > Queue 2 > Queue 1 > Queue 0. This approach can cause the lower priority queues to be starved out preventing them from transmitting any frames but also ensures that all high priority frames Egress the switch as soon as possible.

– Pre-empt + WFQ = When Preempt is enable the highest queue (queue 3) is served first and the other 3 queues are served with WFQ scheme.

☞ With respect to the previous SVRs, from SVR 2.2 the East/West Segregation for the Standard and Enhanced is supported but it is configured via different parameters: instead of selecting the East/West and then the Segregated mode, the East/West segregation is configured and then it is necessary to proceed in configuring the Port

2+0 East/East Trunked

No No No No Yes 10) Yes 10) No

2+0 East/East Segregated

No No No No Yes 9) Yes 9) No

Shut down port in Link failure

Yes Yes Yes Yes Yes Yes Yes

Support of Rapid STP

Yes Yes Yes Yes Yes Yes Yes

VLAN manipulation

No No Yes Yes Yes Yes Yes

1) Capacity of the Radio Ports of the Ethernet switch. For the Ethernet over-the-air capacity see modes file.2) QoS for GigE and EnhGigE is not supported for frames longer than 1518 bytes.3) Only on radio ports.4) A value lower than 30 is recommended.5) Limitation of StrictPriority is present when the payload has all packets of 64kbyte (see par. 5.8).6) IPv4 TOS can be emulated by using DiffServ.7) Even if the VLAN management is not supported for this module the forwarding functionality has been expanded

in this SVR adding the Port Based forwarding mode. See also the 2+0 East/West segregation functionality for the relationship between these two features.

8) Plus modes supported for capacity lower or equal to 100 Mbit/s per VLAN port group (ports 1&2 and ports 3&4).9) From SVR 2.2, in 2+0 the Segregation can be achieved as a particular scheme of configuration of Port Segre-

gation (a dedicated configuration parameter for segregation is no more available)10) In East/East Trunked mode the VLAN management is not supported. The behaviour of this system configura-

tion still remain the same as previous SVR.

Master IO Module

Standard Enhanced Standard2 Enhanced2 GigE Enhanced GigE

42E1

Table 36 Summary of Ethernet Characteristics (Cont.)



Based Forwarding scheme to connect the Port1 with PortEast and Port2 with PortWest.

☞ Note about SVR upgrade when East/West or East/East is configured: because of the change in configuration parameters related to Segregation or Trunking, after the upgrade it is necessary to check and in case reconfigure the parameters.

5.8 Particular behaviours1. Strict Priority when all Ethernet packets are 64 byte length: in Standard2 and

Enhanced2 master module, when the Ethernet packets have all the length equal to 64 bytes the Strict Priority does not work fine: packets with lower priority can be received. When the packet length is random (64-2048 bytes) or it is major or equal to 128 bytes, strict priority works fine. WFQ shows the correct behavior.

2. QoS in EnhGigE with Ethernet frame size longer than 1518 bytes: the WFQ ratio is not respected, when the all the frames has the size higher than 1518 bytes.

3. STM-1 optical remote loop: the looped signal contains errors if the remote fiber is inserted in the interface.

4. QoS Radio-Radio when port based criteria is assigned: in East/West configuration, when the port criteria is used to differentiate the payload coming from the front panel port with respect to the payload coming from the other radio direction for some par-ticular combinations of the priority values the configured WFQ is not respected. For example, the cases that are not working as expected are listed here below (the measured WFQ ratio is different from the expected one).

Other combinations of port priorities show the correct behavior.

This is present with Standard 2, Enhanced 2 and 42E1 Master IO only. More details are described in the following.

Priority assigned to Port 1

Priority assigned to Port West

Expected WFQ ratio

Measured WFQ ratio

3 (higher) 1 8:2 5:2

3 0 8:1 2.6:1

2 0 (lower) 4:1 2.5:1

Table 37


75


Figure 33 QoS radio Radio with Standard2, Enhanced2 and 42E1 Master Modules

Whenever the link between FHy-4 and FHy-2 is over subscribed in the direction FHy-4 > FHy-2, QoS behavior will be undefined on Master IO modules (42E1, Standard2 and Enhanced). The reason for this different behavior is that the Ethernet rate scaling is done by the framer for 42E1, Standard2 and Enhanced Master IO modules, whereas the Ethernet scaling is done by the switch for GigE and EnhGigE Master IO modules.

For the setup mentioned above, when the link in the direction FHy-4 > FHy-2 is over sub-scribed, Framer West will start sending PAUSE frames to the Ethernet switch and the switch will apply back pressure by sending PAUSE frames on Framer East since the flow control is enabled for the framer ports instead of dropping packets from its front panel port which causes the over subscription. This back pressure causes the FHy-3's Ethernet switch to drop packets from its front panel port.

This behavior is not observed in Master IO modules (GigE and EnhGigE) because Ethernet scaling is done by the switch and not by the Framer. Flow control is disabled for both the framer ports on these modules since the switch itself does the scaling and the framers will never be over subscribed.

So this QoS behavior on the 42E1, Standard2 and Enhanced modules is not related to the number of VLAN's or number of VLAN's per port or data rate. This behavior will occur only with the following conditions:

1. IDU with 42E1, Standard2 and Enhanced modules is configured in East-West oper-ational mode

2. When the Ethernet data coming from the front panel ports and one framer port is sent on the another framer port

3. When the data rate of its front panel ports are causing the over subscription of the link.

5.9 100Mbps-PLUS EthernetEthernet payload rates over 100 Mbps (155 Mbps) may be achieved by utilizing the front panel payload ports. In this configuration, two Ethernet channels are provided in the payload frame. The max traffic rate for each Ethernet channel to the framer is defined in the modes file.



5.10 APC (Adaptive Power Control)The Adaptive Power Control capability reduces interference in densely deployed net-works.

The Adaptive Power Control algorithm lowers the Tx Power to between the 1E-6 and 1E-12 BER rate level.

If SNR or signal-level decreases, the Tx Power is increased to maintain the 1E-6 BER.

Alarms are raised if maximum Tx Power is reached.

The implementation of ATPC loop is described by the following block diagram of receiv-ing and transmitting side (see Figure 34 and Figure 35 where CER means = Channel Error Rate).

Figure 34 Rx side


77


Figure 35 Tx side

Following diagram summarizes the expected time diagram for Ptx profile.

Figure 36 Time diagram



The Ptx is adjusted to maintain the RSL between R1 and R2 and CER below the spec-ified threshold. If the RSL is below R1 or the CER is above the specified threshold Ptx will be increased until the RSL is between R1 and R2, or until the CER is below the spec-ified threshold, or the Ptx is at Pmax.

5.11 ACM (Adaptive Coding / Modulation)FlexiHybrid Adaptive Coding / Modulation capability (or "ACM", in the following) provides for automatic changes of the link capacity in response to link performance. This capability will help ensure a link is maintained, at reduced capacity, during degraded link performance due to weather or other anomalous conditions; on the other hand, at link improvement ACM may allow carrying extra capacity for lower priority traffic

FlexiHybrid ACM foresees the configuration of three levels, each associated to one dif-ferent mode, which specifies the pattern of modulation, channel spacing and payload mix; of course, the modes selected for the three levels must be the same channel spacing.

Level1 is always associated to the highest capacity (i.e. highest modulation) mode, Level2 to the intermediate-capacity mode, and Level3 to the lowest-capacity mode. After ACM is enabled, it starts at Level1. If the link performance falls below the operating threshold configured for Level1, ACM automatically switches to Level2. If the link perfor-mance further degrades below the operating threshold configured for Level2, then ACM automatically switches to Level3.

The user will always have to set three levels. If the user wishes to make the ACM work with two levels only, the user must set Level2 and Level3 with the same mode. This allows enabling ACM in RF bands and channel spacing combinations where only two modulations are supported; for example, the 7 MHz channel spacing (in 15, 18 and 23 GHz RF bands in SVR 2.1) supports only QPSK and 16 QAM.

Both directions of the link always work at the same ACM level, so each ACM switch involves in the same way both directions of the link.

In order to allow automatic reversion from Level3 to Level2 or from Level2 to Level1 when link performances improve, the "Revertive switching" mode must be enabled. Oth-erwise, if revertive switching is disabled, any switch to higher-capacity levels must be done manually by the user, because in this case only switches to lower-capacity levels are automatic.

If the revertive switching is enabled, ACM will automatically switch either upwards or downwards among the three levels to ensure the highest capacity for current link condi-tions.

At link capacity variation, traffic is prioritized according to the traffic type.

– E1 Traffic Prioritization:If Level2 or Level3 has fewer E1 channels than Level1, higher numbered channels will be dropped first. For example:– Level1 supports a 16E1-mode: E1 channels 1 through 16 will be transmitted;– Level2 supports a 8E1-mode: E1 channels 1 through 8 will be transmitted, while

in this case E1 channels 9 through 16 will be dropped;– Level3 supports a 4E1-mode: E1 channels 1 through 4 will be transmitted, while

in this case E1 channels 5 through 16 will be dropped.


79


It is worth nothing here that number of E1 channels should be in descending order while going from Level1 to Level3 [#E1 Level 1 > #E2 Level 2 > #E1 Level 3].

– Ethernet Traffic Prioritization:Ethernet traffic is prioritized by means of QoS. Therefore higher priority Ethernet traffic will be assigned the highest priority when Ethernet capacity is reduced after an ACM switch (e.g. from Level2 to Level3), while lower-priority packets will be more likely dropped.

Changes between levels are not hitless, but will cause temporary traffic loss. ACM is designed so that at ±2 dB/s fading speed the maximum traffic loss will be 300 ms for both cases of ACM switches to lower or upper levels. Occasional traffic loss events of some second duration may be allowed.

☞ This 100msec value is achieved as a sum of (1) 'worst-case' latency of ACM switch between two sides of the link (2) 'worst-case' re-configuration time and (3) 'typical' acquisition time for the modem. Under worst-case modem acquisition scenarios, this may go higher.

Link quality is monitored through the CER and RM parameters.

– CER. CER is the Channel Error Rate in the Viterbi decoder, it corresponds to the rate of mismatches between hard decisions and decoded decisions (It corresponds to the "uncoded" BER, not to the BER at the user interface). It is periodically moni-tored, and when it rises above a configured threshold, it triggers an ACM switch to the next lower modulation ("down-1-level switch" in the following).

– RM (Revertive Margin). CER is used for down-1-level switches. It cannot be used also for switches to the next higher modulation ("up-1-level switch", in the following) since the estimated CER is often 0 when link is good. Therefore, if "Revertive Switching" is enabled, to allow up-1-level-switching, the "Alpha Flunk" rate (or AF) in the Viterbi decoder is internally considered. The user can set the desired hyster-esis margin to control the revertive switches.

5.11.1 Scope of ACM Applicability

Supported ModulesIn SVR 2.1 ACM is supported by both the Controller and Controller2 Modules, and by all the Master IO Modules supported in SVR 2.1.

Supported RF BandsIn SVR 2.1 ACM is supported for the 15, 18 and 23GHz, and within these RF bands, for all supported combinations of channel spacing and modulation, i.e.:

– 7 MHz with QPSK and 16 QAM;– 14 MHz with QPSK, 16 QAM and 32 QAM;– 28 MHz with QPSK, 16 QAM, 32 QAM, 64 QAM and 128 QAM.

Supported ModesAll modes with the same bandwidth can be used to configure the ACM levels with the following constraints:

– two modes with the same bandwidth and modulation but with different payload mix cannot be used as different ACM levels; in other words, different ACM levels require modes with different modulations;



– as the AF indicator does not allow revertive switching from QPSK to 64 QAM or from QPSK to 128 QAM, then QPSK and 64 QAM, or QPSK and 128 QAM will not be allowed as adjacent ACM levels;

– Level1, Level2, and Level3 must be associated to the highest, intermediate, and lowest modulation, respectively; moreover the number of E1 channels should be in descending order while going from Level1 to Level3 [#E1 Level 1 > #E2 Level 2 > #E1 Level 3];

– modes with STM-1 payload transport (i.e. mode #139) cannot be configured for ACM configuration;

– modes with Ethernet "Plus" mode (i.e. modes #140 and #141) cannot be configured for ACM configuration;

– the possible modes combinations released are listed in paragraph 5.11.2.

It may be worth remarking that the payload mix of each mode selected as an ACM level must be in accordance with the IDU composition. For example, selecting as an ACM level a mode with more than 100Mbit/s of Ethernet payload requires equipping a GigE Master IO module.

ACM with ATPCACM and ATPC have not to be enabled at the same time.

LicensingNo license level is associated to the ACM feature.


81


5.11.2 Released configurations for ACMTable 38 contains the released ACM mode combinations and the recommended config-uration parameters.

In East/East configuration the following behaviours have been implemented:

– when the ACM is switching it can happen that the changes in Ethernet payload throughput in the two directions (from one NE to the other) are not simultaneous (one direction can show some delay in reaching the final Ethernet rate with respect to the other);

– occasionally the Ethernet payload can be lost for about 30s;– ACM switch in one radio affects also the payload in the other radio;– when the Mux/Demux option is present the ACM switch causes the activation of

STM1 alarms.

5.11.3 ACM Configuration ParametersThe User can enable or disable ACM and to enable or disable the revertive switching when ACM has been enabled.

CER and RM thresholds for down- and up-1-level switching are not configurable by the user (they are fixed). The CER threshold (for down-1-level switches) is selected accord-ing to the following strategy:It provides the minimum distance from the BER=10-6 (at the user interface) that guarantees the ACM maximum switch time (i.e. that prevents the modem unlocking) with the declared fading speed.

Bandwidth Configurable ACM levels

Criteria Reference mode(for Certification)

28MHz Level1: 128QAMLevel2: 32QAMLevel3: QPSK 1)

CER thr = 10^-6Revertive margin = MediumSwitch delay and Revertive Switch delay = 1000 msRevertive Mode = Enabled

128QAM

Level1: 64QAMLevel2: 16QAMLevel3: QPSK


64QAM

14MHz Level1: 32QAMLevel2: 16QAMLevel3: QPSK


32QAM

7MHz Level1: 16QAMLevel2: QPSK

CER thr = 10^-6Revertive margin = Low 2)

Switch delay and Revertive Switch delay = 1000 msRevertive Mode = Enabled

16QAM

Table 38 Released ACM modes and Parameters

1) 16QAM at Level 3 is also allowed, QPSK has been certified because of is the worst condition.2) The value medium or High in this case are critical because they can cause the system to not return to the

higher level.



This strategy aims at:

– avoiding the long switching times (typically than 2 seconds) that occur when a receiver unlocks;

– employing a higher mode as long as possible before switching to a lower one. In fact, if ACM is disabled, a mode will be working until it reaches its BER=10-6 threshold; therefore, if ACM is enabled, that same mode should be used until its BER is as close as possible to its 10-6 threshold.According to this strategy, in SVR 2.1 the proper CER threshold is fixed to 10-6.

The revertive margin for the up-1-level switches guarantees a proper hysteresis for the revertive switching. Hysteresis margin reduces the chance of frequent changes between modulations; furthermore it prevents unstable conditions of the ACM loop, when ACM could be indefinitely bouncing between two levels even if link conditions are stable (e.g. after some fading activity).

The revertive margin is selected according to the following strategy:

– providing the lowest hysteresis margin that prevents ACM levels bouncing.

This is aimed at raising the probability of an up-1-level switch, i.e. of higher throughput, when the link conditions improve.

☞ The quality parameter AF used in SVR2.1 for the up-1-level switching does not make it possible to properly control the revertive margin within a specified range (e.g. 3 dB ±1dB) for all the RF bands.

Furthermore, for each ACM level the following parameters can be configured by the user:

– ACM Switch Delay. This delay is configurable in the range 1÷2 seconds with a granularity of ½ second. This parameter contains a delay value that describes the time between 2 samples for CER polling: it is necessary that two CER samples, one "ACM Delay Switch" seconds after the other, cross the CER threshold before the down-1-level switch procedure is initiated. Of course, ACM Delay Switch is not a configuration parameter of Level3.

– Revertive Switch Delay. This value is configurable only if revertive switching has been enabled, in the range 1÷2 seconds with a granularity of ½ second. This delay refers to the time between consecutive polling actions of the AF threshold: it is nec-essary that two AF samples, one "Revertive Delay Switch" seconds after the other, cross the AF threshold before the up-1-level switch procedure is initiated. Of course, Revertive Delay Switch is not a configuration parameter of Level1.


83


5.12 Performance MonitoringSVR 2.2 extends the Performance Monitoring management with respect to the previous SVRs.

Moreover the Performance Monitoring data are available for the TMN collection via SNMP interface.

In this paragraph also the Ethernet counters and measurements of received and transmit power levels are described, even if they are not collected as Performance Mon-itoring measurements.

5.12.1 HW/SW compatibility for Performance Monitoring functionlaityThe Performance Monitoring management is supported in all the IDU compositions sup-ported by SVR 2.2. When the management and support depends on the Master module type it will be explicitly stated.

5.12.2 Performance Monitoring principlesFrom the End-User point of view the "Performance Monitoring" is a collection of data that allows both the run time and history monitoring of the quality of the links and digital paths.

Equipment side the "Performance Monitoring" implementation can be divided into the following main areas:

– Measurement Types: the type of data and the associated measurements that are required to be monitored.

– Measurements Periods: 15 minute granularity.– Measurements Points: on the base of the equipment physical and processing

structure they are the points where the data are probed.

5.12.3 Measurements TypesTable 39 describes the Measurement Types and what can be applied to FlexiHybrid equipment structure and payload processing.

Measurement types class FlexiHybrid application

Quality event counters Measurement point at tributary side is available for STM1 with Mux/Demux option and it is applied to each STM1.

Unavailability event counters

Measurement point at tributary side is available for STM1 with Mux/Demux option and it is applied to each STM1.

RPS (Radio Protection Switching) event counters

Measurement point at each switching functionality

Transmit Power Level Current level of RF transmitted power. These measure-ments are not collected as "Performance" data but as simple counters.

Table 39 Measurement Types



– Quality event counters and unavailability event counters are measured in a way in line with ITU-T G.826 and G.828 and G.829 recommendations. • Implementation of SVR 2.2 adopts the RFC 2558 compliance for the line side

performance (STM1) with the addition that CV (Coding violation) are stopped when SES are present (as per RFC 3592).

– RSPI measurement types are not supported.– Only the local performance data are supported in SVR 2.2; the remote data are not

supported.

5.12.4 Measurement Periods The performance data are available with the 15 minutes granularity (24 hour registers, required by ITU-T G.784 recommendation, are not supported). The periods start each quarter: 00, 15, 30, 45 minutes.

The STM1 Performance measurements are available for the last 96 intervals (24 hours).

The Intervals are characterized by:

– all the applicable event counters/parameters;– a time counter for each measurement point (present only for current interval only):

the actual number of seconds in the interval.– a suspect interval flag for each measurement point (present for past intervals only),

indicating abnormal situation. Suspect Interval is binary information associated to each measurement point interval. It is set when the measurement has not been run on the complete interval or for any reason the results are not fully meaningful (for example because a threshold has been modified within the interval or a manual operation on the radio unit has impacted the performance results).

– The 15min intervals start at 00:00 of the current day.

The past intervals are stored in volatile memory.

5.12.5 Measurements PointsThere are different measurement point types, according to the network element config-uration:

– Tributary quality/unavailability events measurement point/s relevant to RST, MST, HOVC, LOVC termination point of STM-1 signal. This measurement points is available only when the STM1 interface and the Mux/Demux option are present too. Remote Performance Monitoring is not required (those based on the REI and RDI bytes of SDH overhead).

– RPS measurement point (one per network element, not present in non-protected system configurations).

Received Power Level Current level of RF received power. These measure-ments are not collected as "Performance" data but as simple measure of the current value.

Ethernet Ethernet statistics. These measurements are not col-lected as "Performance" data but as simple counters.

Measurement types class FlexiHybrid application

Table 39 Measurement Types (Cont.)


85


– Receive and Transmit Power level– Ethernet Statistics.

Figure 37, Figure 38 and Figure 39 in the following show the logical structure of the system and the positions of measurement points where each Measurements Types are evaluated.

In this paragraph:

– 1+1 refers to both "Protected non Diversity" (1+1 HSBY) and "Protected Diver-sity (1+1 FD)

– 2+0 refers to both "East/West" (2+0 different destination) and "East/East" (2+0 same destination).

Figure 37 Measurement points in 1+1 configuration

Figure 38 Measurement points in 2+0 systems



Figure 39 Measurement point when STM1 and Mux/Demux functionality is present

5.12.6 Quality and Unavailability event countersThese counters are often called Error Performance event counters; they apply to Radio and Tributary interfaces.

At the Radio side, in case of protection, they are evaluated on the protected signal/s and they must not be evaluated during unavailability periods.

Errored Blocks (EB) is the elementary unit used to measure equipment performances.

The tributary side measurements are available only in case of STM1 interface and Mux/Demux option. Since the incoming STM1 is completely terminated the performance have to be measured at the RST, MST, HP and LP. There is one set of event counters and one suspect flag for each section.

Quality event counters are listed in the following:

– ES: Errored Seconds, defined as the seconds in which at least one errored block is measured

– SES: Severely Errored Seconds. Defined as the seconds in which more than X % of Errored Blocks are measured, where "X" depends on the STM section. Note that a SES encloses an ES. SES belonging to a "unavailability period" (see below) have not to be counted.

– BBE: Number of Errored Blocks measured during a time period without SES.

Event counter that qualify the unavailability of the relevant channel:

– UAS: Unavailability Seconds, defined as the period during the link is out of service. It is detected counting the number of consecutive SES. The Unavailability is declared when 10 consecutive SES are detected on the radio/tributary link while it is removed when 10 consecutive non-SES are detected.

5.12.7 Radio Protection Switching (RPS) ParametersRPS parameters are referred to the Radio Protection Switching measurement point. Note that standards only address SDH radio systems and are extended to non SDH equipment proprietarily; the extension is obvious since these parameters are only related to radio performance and do not take into account any specific SDH feature.


87


FlexiHybrid has 1+1 system type only (N+1 and Double Tributary Interface is not sup-ported). As a consequence only the PSAC counter is applicable.

Channel switching performance is described by the following performance events, that are applicable to the protected system types only (and related to the switched that protect the system from the events due to propagation condition. i.e. the RX switch only is involved):

– PSAC: Protection Switch Actual Count, defined as the number of switching events: • for the protected channel it is the number of Protection Switch Actual (PSA) from

the protected channel to the protection channel during a fixed time interval (15 minutes);

• for the protection channel, it is the number of switching (PSA) towards the pro-tection channel from any protected channel during a fixed time interval (15 min-utes).

In 1+1 configuration, PSAC is applied to protected channel. PSAC for protection channel is not required since it would give the same number. While it is clear which is the pro-tected channel in case of revertive switching, in unrevertive situations (like in FHy) on system boot up, the Framer chooses the active receiver. The software will consider the initial active receiver chosen by the Framer as the protected channel for counting PSAC. Each 15 minute interval will contain the cumulative total switches toward the protected channel.

5.12.8 Extended lists of available Performance Monitoring dataThis section contains the detailed list of supported Performance Monitoring data. The presence and validity of each measurement is strictly related to the NE configuration (as described in par. 5.12.5). Table 40 defines, per each measurement point:

– the available time intervals;– the condition or system configuration that make the measurement point valid and

meaningful.

Per each Measurement point, if the condition listed in the column "when available" of Table 40 are not all true the Measurement Point is Invalid. Invalid means that the mea-surement point is meaningless respect to the current system conditions. Consequently

Measurement point

Intervals When available

Line Side Current interval+ 96 quarters

Mux/Demux finctionality is authorized AND

Master IO is inserted AND

Master IO supports the Mux/Demux functionality AND

Mini IO is present AND

Selected Mode is non-STM for all the available radio directions.

RPS Current interval+ 96 quarters

System configuration is 1+1 (Protected Diversity or Non diversity)

AND Master IO is present

Table 40 Validity condition for Measurement Points



no data are expected to be provided to the user/manager, or in other words, the data are not expected to be collected by the user for analysis because they do not give informa-tion applicable to the current system condition.

The complete list of all the supported measurement points with the details of the measures per each interval is contained in Table 41.

Side Measurement point

Time interval Type and ID

Measurements Note

Line Side RST (B1) Current Quarter ES Not supported in Web-LCT, available via SNMPSES

BBE1)

UAS

Elapsed time

Quarters -1 … -96

ES Graphs of Ratio values

SES

BBE

UAS

Suspect

MST (B2) Current Quarter The same as RST Not supported in Web-LCT, available via SNMP

Quarters -1 … -96

The same as RST Graphs of Ratio values

HOVC (B3) Current Quarter The same as RST Not supported in Web-LCT, available via SNMP

Quarters -1 … -96

The same as RST Not supported in Web-LCT, available via SNMP

LOVC (V5) VC12#1 Current Quarter The same as RST Not supported in Web-LCT, available via SNMP

Quarters -1 … -96

The same as RST Not supported in Web-LCT, available via SNMP

LOVC (V5) VC12#2…LOVC (V5) VC12#63

The same as VC12#1

RPS Current Quarter PSAC Currently Interval data dis-played with 10sec refreshElapsed time

Quarters -1 … -96

PSAC Displayed

Suspect

Table 41 Complete list of PM measurements for SVR 2.2


89


5.12.9 Performance Monitoring management behaviour

Data collection granularity inside IDUThe collecting of the PM data can and cannot be achieved at 1 sec intervals and the final effect is that the collected data contain fewer events than the actual number of occurred events.

When the software monitors only the RF Link performance East and West, RPS and Regenerator Section of STM, it is able to collect around 890 to 900 instances per 15 minutes interval.

But once if the software starts to monitor all the performance data i.e., RF Link East and West, RPS and all four STM layers, it is only able to collect 820 to 830 instances per 15 minutes interval.

STM1 LOF managementWhenever an STM1 LOF (Loss of Frame) alarm is generated the software stops moni-toring the performance.

5.12.10 RF Power measurementsAs mentioned the RSPI performance monitoring point is not supported. Anyway, the monitor of RF power levels is available as pure measurement as described in the follow-ing.

Info about D&T

Radio link Current Quarter Start

D&T Not supported in Web-LCT, available via SNMP

Quarter Start -1 … 672


STM Current Quarter Start


Quarter Start-1 … 96


RPS Current Quarter Start


Quarter Start-1 … 96


1) In implementation of SVR 2.2 the CV (Coding violation) instead of BBE have been implemented. The CV com-putation is in line with RFC approach, that is the number of errors is counted instead of the number of errored blocks.

Side Measurement point

Time interval Type and ID

Measurements Note

Table 41 Complete list of PM measurements for SVR 2.2 (Cont.)



The behaviour of RSL, SNR and TX power in special conditions is contained in the fol-lowing table:

5.12.11 Ethernet StatisticsEthernet counters are not required to be collected as performance monitoring. Ethernet counters are available as free running counters with the "Clear" command.

☞ In Master IO modules that have a unique HW command in the Ethernet switch to activate the clear for all the ports the time coherence is guaranteed by the Ethernet Switch. For the other Master IOs separated commands are available but the SW activates them in the same polling time, so also in this cases the time coherence is assured.

In the following the validity of the counters is listed and also the availability via Web-LCT and SNMP interface are detailed.

Measurement point When available

Prx East System configuration = All (1+0, 1+1, 2+0)

Prx West System configuration = East/West or East/East or 1+1

Ptx East System configuration = All (1+0, 1+1, 2+0)

Ptx West System configuration = East/West or East/East or 1+1

Table 42 Validity condition for Counters

Side

Prx East 1 sample every 90 seconds for 24 hours

Prx West The same as Prx East

Ptx East 1 sample every 90 seconds for 24 hours

Ptx West The same as Ptx East

Table 43 Complete list of Statistics and raw Counters supported

GUI graph SNMP

RSL level SNR level TX power level

RSL level TX power level

ODU disconnected at Start up

Not plotted Not plotted 0 0 0

ODU disconnected 0 No change 0 0 0

ODU disabled 0 No change 0 0 0

Transmitter mute No change No change No change No change No change

Modem disconnected Not plotted Not plotted Not plotted -11000 -11000

Table 44 Special values of measurements


91


Table 46 lists the set of Ethernet statistics available via Web-LCT and SNMP.

An additional set of Ethernet statistics is available via SNMP interface only. Their avail-ability depends on the Master IO module type. The portion of the standard IF-Table and IFX-Table that are supported in SVR 2.2 are listed in Table 47.

Measurement point When available

Ethernet Statistics

Port1 With all Master IO modules & the selected mode contains Eth payload

Port2 With all Master IO modules & the selected mode contains Eth payload

Port3 (GigE OR EnhGigE) & the selected mode contains Eth payload

Port4 (GigE OR EnhGigE) & the selected mode contains Eth payload

PortSFP (GigE OR EnhGigE) AND SFP module is equipped & the selected mode contains Eth payload

PortEast With all Master IO & the selected mode contains Eth payload

PortWest With all Master IO & System configuration is 2+0 & the selected mode contains Eth payload

Table 45 Validity condition for Ethernet Counters

Ethernet Statistics(per each valid port)

Description

STP status STP Port Status

Rx Bytes Number of bytes received on UPL Switch port

Rx Bytes/sec Number of bytes received per second on UPL Switch port

Tx Bytes Number of bytes transmitted on UPL Switch port

Tx Bytes/sec Number of bytes transmitted per second on UPL Switch port

Rx Frames Number of frames received on UPL Switch port

Rx Frames/sec Number of frames received per second on UPL Switch port

Tx Frames Number of frames transmitted on UPL Switch port

Tx Frames/sec Number of frames received per second on UPL Switch port

Errors Number of errors on UPL Switch port

Errors/sec Number of errors per second on UPL Switch port

Collisions Number of collisions on UPL Switch port

Collisions/sec Number of collisions per second on UPL Switch port

Table 46 Ethernet Statistics available via Web-LCT and SNMP



Ethernet Statistics(per each valid

port)

Description Master Modules

InOctets The total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur aftre-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime

All

fInErrors For packet-oriented interfaces, the number of inbound packets that contained errors reventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors prevent-ing them from being deliverable to a higher-layer protocol.

ifOutOctets The total number of octets transmitted out of the interface, including framing characters.

ifHCInOctets The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets.

ifHCOutOctets The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets.

ifInUcastPkts The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broad-cast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutUcastPkts.

GigE, EnhGigE 42E1,Standard2,Enhanced2

ifInMulticastPkts The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts.

ifInBroadcastPkts The number of packets, delivered by this sub-layer to a higher (sub) layer, which were addressed to a broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-ini-tialization of the management system, and at other times as indi-cated by the value of ifCounterDiscontinuityTime.

Table 47 Ethernet Statistics available via SNMP interface only


93


ifOutMulticastPkts The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

GigE, EnhGigE 42E1,Standard2,Enhanced2

ifOutBroadcastPkts The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. Dis-continuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

ifOutUcastPkts The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broad-cast address at this sub-layer, including those that were discarded or not sent.

ifInDiscards The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliv-erable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.

GigE, EnhGigE

ifOutDiscards The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.

Ethernet Statistics(per each valid

port)

Description Master Modules

Table 47 Ethernet Statistics available via SNMP interface only (Cont.)



5.13 Cross-Connections Cross-connection matrix capability is "any to any": E1 configured over the radio interface can be connected to any E1 of the other radio interface or to any E1 of the front panel; moreover an E1 of the front panel can be connected to any E1 radio side or to another E1 of the front panel.

In addition, when the Enhanced Master IO is equipped there is the possibility to add/dropp any E1 in the STM1 TUG3-VC12 structure.

In this section the "Termination Point" (TP) name will be used to identify each possible time slot logically managed by the Cross-connection matrix.

A Cross-connection is defined by the list of the TP that are connected and by the type of cross-connection.

Here below is given a description of:

– the available TP (section 5.13.1)– the connection types ( section 5.13.2 and section 5.13.3).

5.13.1 Termination Points identification Figure 40 shows the physical position of the payload interfaces. There are at most two radio ports: the East side, associated to the modem in the lower slot and the and West side, associated to the modem in the upper slot. The West port is present only in East/West configurations (2+0).

Payload interfaces line side are housed on the front panel of three different modules that can be equipped in the Master IO slot, the Mini IO slot and the Expansion slot. On the base of the type of module equipped the number and type of the interface connectors are different. .

Figure 40 Physical location of E1 TP

Figure 41 shows the logical scheme associated to the physical view that can be used to understand and manage the cross-connections.

The TPs of the three side of the cross-connection matrix are identified with a Prefix and a Number:

<Prefix><Number>

The prefixes contain the information of the matrix side and the cross-connection type. While the number identifies the time slot or the connectors.


95


Figure 41 summarizes the logical view of the cross connection matrix associated to the physical one and Table 1 details the syntax used to identify all possible TPs.

Figure 41 TP name and associated Prefix

General Notes about Range and TP availability

– The number of the E1 present on the Radio side depends on the number of E1 present in the configured mode (the mode is independent for each modem). In the figure the maximum hardware limits are represented: the maximum hardware capa-bility is 64 E1. Anyway, in SVR 1.2/1.3 the maximum number of E1 is 63.

– The number of MA and EX depends on the Master IO module and Expansion module equipped. For the modules supported in SVR 1.2/1.3 the number of E1 inter-faces and consequently the range to be used in the syntax is listed here below.

<Prefix> <Number>

Range Description

Ei E1.. E63 It identifies the E1 time slot number i of the Radio side East

Wi W1..W63 It identifies the E1 time slot number i of the Radio side West

Ri R1..R63 It identifies the E1 time slot number i of the Radio side for Ring cross-connection

MAi MA1..MA42 It identifies the E1#i front panel connector of the Master IO module

EXi EX1..21 It identifies the E1#i front panel connector of the Expan-sion IO module

STklm ST111..ST373 It identifies the VC12 (k,l,m) within the STM1 frame

The syntax reflects the (k,l,m) numbering of VC12 adopted in ITU-T G.707 for the TUG3-TUG2-TU2 mul-tiplex numbering). These type of TPs are present only if the Mux/Demux option is supported by the master IO module. Up to SVR 1.2 the module with this option is the Enhanced master IO only

Table 48 TP identification and Prefix Syntax



– The E1 interface on the Front panel are always active: their activation is not corre-lated to the configured radio capacity.

5.13.2 Bidirectional ConnectionsBidirectional cross-connection is defined by specifying the couple of TP that shall be connected.

Figure 42 Standard Cross connection with related syntax

Examples of Cross Connection

– MA1, W3 = the E1#1 present on the Master IO module is connected to the E1 timeslot #3 of the West side

– E6, W45 = the timeslot of E1#6 East side is connected to the E1 timeslot #3 of the West side

Module type Syntax and range to be used to address

module interface

Standard/Standard2/Enhanced/Enhanced2 Master IO module (16E1 interfaces)

MA1..16

42E1 Master IO module (42E1 interfaces) MA1..42

GigE/GigE Enhanced Master IO module (2E1 interfaces) MA1..2

16E1 Expansion IO module (16E1 interfaces) EX1..16

21E1 Expansion IO module (21E1 interfaces) EX1..21

Mini IO STM1 (1 STM1 interface) ST111…ST373

Table 49 Module interfaces


97


– EX3, MA2 = the E1#3 present on the Expansion module is connected to the E1#2 of the Master IO module

– ST221,W7 = E1 timeslot #7 west side is add/dropped to/from the VC12#221 of the STM1

5.13.3 Ring Cross-ConnectionsRing cross connections are used to set up protected E1 paths within a ring topology network.

Figure 43 and Figure 44 graphically describe the paths of a protected E1 within the ring, in case of normal operating condition and condition with a failure in the main path.

Figure 43 E1 Data Connection

Figure 44 Protected E1 data connection

At IDU level the Ring configuration consists in routing all the incoming E1 to be protected to the West side and use the opposite direction as protection path (see Figure 45).



Figure 45 Normal E1 data path within the IDU

When a link failure occurs, the two NEs of the link detects the RX failure the NEs start feeding the Rx failed signal with the signal incoming from the other path as shown in Figure 46.

Figure 46 Protected E1 data path within the IDU

The syntax used to configure the ring cross-connection has a dedicated prefix radio side: the radio side TPs are identified with the "R" letter. The differentiation of East and West is not required because East ans West assume the fixed role of Active and Pro-tection. The syntax for line side TPs still remain the same.

The possible cross-connection are:

– Drop from line side (to exteract/insert the E1 in the protection ring)– Pass-throug (to route the protected path towards the ring)


99


Figure 47 Ring Cross connection with related syntax

Constraints:

– Ring cross-connection can not be mixed with non-Ring cross connections, if one cross-connection is set up as Ring all the others shall be ring too.

5.14 STM-1 Mux/Demux (Optional) The IDU allows to demultiplex 63 x E1 PDH signals from the SDH signal. The demulti-plexed E1s are routed via the crosspoint switch to the east modem, west modem, or front panel, as shown in Figure 48.

The STM-1 Mux/Demux feature requires an Enhanced or an GigE Enhanced IO Module.



Figure 48 STM-1 Mux/Demux Capability

☞ The optional 16xE1 expansion I/O unit is not supported in the STM-1 Mux/Demux configuration.

5.15 Loop-back

5.15.1 E1 LoopbacksThe IDU provides system loopbacks as a means for test and verification of a unit, link, and/or network. A variety of loopback points, are available. Loopback points and duration are easily selected through the Graphical User Interface.

The E1 loop-backs are available for the aggregate signal or for a single E1 stream.

5.15.1.1 Loopbacks for the aggregate signalThese loopbacks operate on the aggregate signal and cause the loopback of all the E1 streams.

Three aggregate loopbacks are available:

– Local LIU loop-back– Local Modem loop-back– Remote LIU loop-back


101


Local LIU loop-backThe tributary signal can be looped back at LIU level. This type of loop-back when acti-vated allows testing the integrity of the line interface access circuitry.

Figure 49 Local LIU loop-back

Local Modem loop-backThe tributary signal can be looped back at MODEM level. This type of loop-back when activated allows testing the integrity of the line interface access circuitry.

Figure 50 Local Modem loop-back

Remote LIU loop-backEach E1 tributary stream can be looped back in the remote station, just before the E1 output interface. This type of loop-back, when activated, allows testing connection integ-rity between two terminals, with the only exception of the E1 physical output drivers of the remote terminal.

Figure 51 Remote LIU loop-back

5.15.1.2 Loopbacks for a single E1 streamThese loopbacks are performed on a single E1 stream.

Two loopbacks are available:

– Near End loopback: the transmission is sent back to the reception in the local NE.



– Far End loopback: the reception is sent back to the reception in the remote NE.

5.15.2 STM-1 loopbacksThere are different types of loopbacks according to the processing performed on the STM-1 signal. Two types of processing can be performed:

– STM-1 transparent– STM-1 with MUX/DEMUX option

5.15.2.1 Loopbacks with STM-1 transparentTwo loopbacks are available:

– Local loopback: the Tx side is loopped back to the Rx side in the local NE;– Remote loopback: the Rx side is loopped back to the Tx side in the remote NE.

5.15.2.2 Loopbacks with STM-1 with MUX/DEMUX optionTwo loopbacks are available:

– Facility loop: A signal received on the front-panel STM-1 port is looped back and transmitted out the STM-1 front-panel port;

– Terminal loop: A signal received from the RF link is looped back to the RF link.


103

Solution Description Management

6 Management

6.1 IDU and Network management There are three ways of accessing all the IDU parameters:

1. Via HTTP using a standard web-browser to access the built in webserver.2. Via SNMP using the fully featured MIB, to automatize data collection and network

management.3. Via a client line command accessible from a terminal client connected to the serial

port.

The GUI (HTTP), SNMP, and CLI interfaces are detailed in the OMN Manual.

6.2 IP address Each IDU is independently configured for network parameters such as IP address, subnet, and gateway. However, the IDU also supports the functionof DHCP client, in which case the IP address can be assigned to the IDU through a DHCP server. A specific IP address may be associated with a particular IDU by configuring the DHCP server to serve IP addresses based upon the IDU Ethernet MAC address.

6.3 Network The IDU uses an "Out-of-Band" NMS network which is separated from the payload Ethernet network. Each IDU contains a managed Layer 2 Ethernet switch that supports Spanning-Tree Protocol (STP) for NMS traffic management. This allows the IDU to be configured in a protected ring configuration where the STP will prevent an Ethernet loop in the ring. This will also allow the ring to re-configure should an outage occur. The IDU acts as a network bridge via the Ethernet switch and the STP. The IDU does not cur-rently support NMS routing facility.

6.4 NMS Network Operational Principles The IDU does not provide routing facility. Therefore, all IDUs must be on the same subnet as the PC being used to access the IDU. If the IDUs and/or the PC are on dif-ferent subnets, a router must be used, with the gateway addresses suitably. Figure 52 shows the PC and both IDUs in the same subnet. In this case, no router is required. Figure 52 shows the PC and one of the IDUs in one subnet and the other IDUs in another. In this case, a router is required. Note how the GW addresses are set to allow interaction between the PC and the IDU in the other subnet.


Solution DescriptionManagement

Figure 52 PC and IDU on same subnet

Figure 53 IDU on different subnets

6.5 Third Party Network Management Software Support The IDU supports SNMPv1, SNMPv2, and SNMPv3 protocols to be used with third party network management software. The SNMP agent will send SNMP slots to specific IP addresses when an alarm is set or cleared. Information contained in the slot includes:

– IP address– System uptime– System time– Alarm name– Alarm set/clear detail

The IDU may also be managed via HTTP, TELNET, and SSH protocols.


105

Solution Description Solution technical specifications

7 Solution technical specifications

RF bands from 6 GHz to 38 GHz

Architecture Split mount

Transmission capacity • Standard PDH configuration:– up to 16xE1 (E1 traffic only)– up to 155 Mbps (Eth traffic only)– several combinations of E1 and Eth traffic

depending on selected modulation and channel bandwidth

• Super PDH configuration:– up to 63xE1 (E1 traffic only)– up to 155 Mbps (Eth traffic only)– several combinations of E1 and Eth traffic

depending on selected modulation and channel bandwidth

• GigaEthernet configuration:– up to 300 Mbps in (1+0)

• SDH configuration:– 1xSTM-1 Optical or Electrical

Ethernet QoS The Ethernet frames are transmitted over the radio channel according to Quality Of Service rules

Configurations – 1+0 (standard) terminal – 1+1 protected diversity terminal – 1+1 protected non diversity terminal (Hot

Standby)– East-East (2+0 same destination)– East-West (2+0 different destination or Ring)

Radio protection switching 1+1 hitless revertive or not revertive

Battery protection Yes

APC Yes (APC dynamically adjusts the output power based on both the actual strength and quality of the signal)

ACM (Adaptive Coding/Modu-lation)

Yes

Modulation QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM

Table 50 General technical specifications


Solution DescriptionSolution technical specifications

FEC type Modulation FEC

QPSK 7/8

16 QAM 7/8

32 QAM 9/10

64 QAM 11/12

128 QAM 13/14

IDU-ODU cable Max. IDU/ODU distance:

• HC AP/CC ODU – 100 m (with braided 50 ohm coax. cable)

• HC AP ODU – 80 m (with braided 50 ohm coax. cable)

For installations that require cable longer than 100 m a 1/2” cable can be used.

The max cable lenghts are as follows:

• ODU HC AP/CC: max 250 m • ODU HC AP: max 230 m

ODU 6L GHz 6U GHz 7 GHz 8 GHz 11 GHz 13 GHz

HC AP/CC 10±2 dB 10±2 dB 10±2 dB 10±2 dB 10±2 dB 10±2 dB

HC AP - - - - - -

Table 51 RTPC range (6-13 GHz)

ODU 15 GHz 18 GHz 23 GHz 26 GHz 32 GHz 36 GHz

HC AP/CC 10±2 dB 10±2 dB 10±2 dB 10±2 dB - -

HC AP - - - - 10±2 dB 10±2 dB

Table 52 RTPC range (15-38 GHz)

Table 50 General technical specifications (Cont.)

6L GHz 6U GHz 7 GHz 8 GHz 11 GHz 13 GHz 15 GHz 18 GHz 23 GHz 26 GHz 32 GHz 38 GHz

+24 dBm

+24 dBm

+23 dBm

+23 dBm

+22 dBm

+21 dBm

+20 dBm

+19 dBm

+18 dBm

+17 dBm

+14 dBm

+14 dBm

Table 53 Max output power (at ODU flange)


107

Solution Description Solution technical specifications

Signal BW

Modulation ETSI Nominal Bit Rate

RF band [GHz]

L6 U6 7 8 11 13 15 18 23 26 32 38

7 MHz QPSK 8 Mbit/s - - - - - - -90.0 -90.5 -89.5 - - -

16QAM 2*8 Mbit/s - - - - - - -81.0 -81.5 -80.5 - - -

14 MHz QPSK 2*8 Mbit/s - - - - - -89 -88.5 -88 -86 -82 -83 -81

16QAM 34 Mbit/s - - - - - -83 -82.5 -82 -80 -80.5 -78 -79

32QAM STM0 (51) - - - - - -77 -77 -78 -75 -74 -74 -76

28 MHz QPSK 34 Mbit/s -84 - - - - -86 -85 -86 -83 -82 -83 -82

16QAM 2*34Mbit/s -78 - - - - -79 -80 -81 -78 -77 -76 -78

32QAM 2*STM0 -74 - - - - -76 -76 -77 -74 -72 -72 -74

64QAM 2*STM0 -72 - - - - -72.5 -72.5 -73 -72 -70 -68 -70

128QAM STM1 -66 -66 -68 -68 -68 -68 -68 -69 -67 -63.5 -64 -66

Table 54 BER = 10-6 Rx threshold (dBm)

Configu-ration

6L GHz

6U GHz

7 GHz 8 GHz 11 GHz

13 GHz

15 GHz

18 GHz

23 GHz

26 GHz

32 GHz

38 GHz

1+0 114 W 114 W 114 W 114 W 114 W 114 W 96 W 96 W 96 W 96 W 96 W 96 W

1+1 216 W 216 W 216 W 216 W 216 W 216 W 180 W 180 W 180 W 180 W 180 W 180 W

Table 55 Total power consumption (W)


Solution DescriptionAcronyms and abbreviations

8 Acronyms and abbreviationsACM Adaptive Coding / Modulation

AGC Automatic Gain Control

AIS Alarm Indication Signal

ALS Automatic Laser Shutdown

AP Alternate Polarization

APC Automatic Power Control

ASIC Application Specific Integrate Circuit

ATPC Automatic Transmit Power Control

BBE Background Block Error

BER Bit Error Ratio

C/I Carrier-to-Interference ratio

C/N Carrier-to-Noise ratio

CCI Co-Channel Interference

CLI Command Line Interface

CRC Cyclic Redundancy Check

DDF Digital Distribution Frame

DHCP Dynamic Host Configuration Protocol

DTI Double Tributary Interface

DSL Digital Signal Line

E2PROM see EEPROM

EEPROM Electrically Erasable PROM

EMS Element Manager System

EOW Engineering Order Wire

ETH Ethernet

ETSI European Telecommunication Standards Institute

FEC Forward Error Correction

FPGA Field Programmable Gate Array

GETH Giga Ethernet

HDB3 High Density Bipolar of order 3 code

HDLC High-level Data Link Control


109

Solution Description Acronyms and abbreviations

HSBY Hot Stand-By

i/f Interface

IDU Indoor Unit

IF Intermediate Frequency

ITU International Telecommunications Union

LAN Local Area Network

LCT Local Craft Terminal

LED Light Emitting Diode

LLC Logical Link Control

LO Local Oscillator

LOF Loss of Frame

LOM Loss of Multiframe

LOP Loss of Pointer

LOS (1) Line Of Sight

(2) Loss Of Signal

LP Lower Order Path

LSB Least Significant Bit

MAC Medium Access Control

MAN Metropolitan Area Network

MIB Management Information Base

MS Multiplex Section

MSB Most Significant Bit

MTBF Mean Time Between Failures

MTU Maximum Transmission Unit

NE Network Element

NF Noise Figure

ODU Outdoor Unit

PCB Printed Circuit Board

PDB Power Distribution Board

PDH Plesiochronous Digital Hierarchy

PDU Protocol Data Unit

PLM Path Label Mismatch


Solution DescriptionAcronyms and abbreviations

PM (1) Performance Monitoring

(2) Poll-Me Bit (IEEE only, not to be used)

PMP Point-to-Multipoint

ppm Part per Million

PPP Point-to-Point Protocol

PRBS Pseudo-Random Binary Sequence

PS (1) Power Supply

(2) This is also used for Physical Slot (IEEE only, not to be used)

PSK Phase Shift Keying

PtP Point to Point

QAM Quadrature Amplitude Modulation

QoS Quality Of Service

QPSK Quadrature Phase-Shift Keying

RAM Random Access Memory

RDI Remote Defect Indication

REI Remote Error Indication

RF Radio Frequency

RIP Routing Information Protocol

RLTS Received Level Threshold Seconds

ROM Read Only Memory

RPS Radio Protection Switching

RS (1) Reed-Solomon (Coding algorithm)

(2) Regenerator Section (SDH)

RSP Response

RSPI Radio Synchronous Physical Interface

RSS Received Signal Strength

RSSI Received Signal Strength Indicator

Rx Receiver / Reception

SDH Synchronous Digital Hierarchy

SDIDU Software defined IDU

SEEP Serial E2PROM

SES Severely Errored Second


111

Solution Description Acronyms and abbreviations

SNMP Simple Network Management Protocol

SVR Software Version Release

TCM Trellis Code Modulation

TIM Trace Identifier Mismatch

TNMP Trivial Network Management Protocol

ToS Type of Service

TV Televalue (Proprietary TNMP property)

Tx Transmitter / Transmission

USB Universal Serial Bus

VC-n Virtual Container - n

VLAN Virtual Local Area Network

VP Virtual Path

WFQ Weighted Fair Queueing

XML Extensible Markup Language

XPIC Cross Polar Interference Canceller

Documents

FlexiHybrid Solution Description