eclipse packet node in the mobile network ansi white paper

WHITE PAPER

September 23, 2010

ECLIPSE PACKET NODE IN THE MOBILE NETWORK ANSI

EXECUTIVE SUMMARY Base stations that can connect devices at up to 50 Mbit/s or more will be operational within the next few years. For the backhaul network, the extra capacity needed and the mix of services to support legacy 2G and emerging 3G and 4G technologies will require changes in the technology used—IP/Ethernet will be the transport technology of choice.

This paper introduces the technologies for transitioning wireless backhaul networks to Ethernet, and the transport and management solutions provided by EclipseTM Packet Node from Aviat Networks.

WHITE PAPER

Eclipse Packet Node in the Mobile Network - ANSI

2 AVIAT NETWORKS September 23, 2010

TABLE OF CONTENTS

EXECUTIVE SUMMARY ........................................................................................................................... 1

SUMMARY ................................................................................................................................................. 3

INTRODUCTION ....................................................................................................................................... 3

ECLIPSE PACKET NODE ......................................................................................................................... 4 PLATFORM ................................................................................................................................................................. 5 EXTENDED ODU AND RFU OPTIONS .................................................................................................................... 5 PLATFORM INTEROPERATION ............................................................................................................................... 6 OPERATIONAL MODES ............................................................................................................................................ 6

TDM ONLY ......................................................................................................................................... 6

MIXED-MODE TDM+ETHERNET ..................................................................................................... 6

MLPPP................................................................................................................................................ 7

ALL-ETHERNET ................................................................................................................................ 7 NETWORK RESILIENCE ........................................................................................................................................... 7

PLATFORM PROTECTION ............................................................................................................... 8

LINK/PATH PROTECTION ................................................................................................................ 8

INTERFACE PROTECTION .............................................................................................................. 8

NETWORK PROTECTION ................................................................................................................ 8 ETHERNET FEATURES ............................................................................................................................................ 8

SWITCH CAPACITY .......................................................................................................................... 8

TRAFFIC SHAPING ........................................................................................................................... 8

THROUGHPUT OPTIMIZATION ....................................................................................................... 9

SYNCHRONIZATION ........................................................................................................................ 9

LINK AGGREGATION ..................................................................................................................... 10

ETHERNET INTERFACE PROTECTION ....................................................................................... 11

CARRIER GRADE OPERATION ..................................................................................................... 11

CARRIER GRADE OAM .................................................................................................................. 11

LINK CAPACITY AND SPECTRAL EFFICIENCY .................................................................................. 12 ADAPTIVE CODING AND MODULATION .............................................................................................................. 12 CO-CHANNEL DUAL POLARIZED LINKS (CCDP) ................................................................................................ 14

STRONG SECURITY .............................................................................................................................. 15 PAYLOAD ENCRYPTION ........................................................................................................................................ 16 SECURE MANAGEMENT ........................................................................................................................................ 16 RADIUS CLIENT ....................................................................................................................................................... 16

CONCLUSION ......................................................................................................................................... 16

GLOSSARY ............................................................................................................................................. 17

WHITE PAPER


SUMMARY Data services will grow to use more network capacity than voice. More network capacity translates to more backhaul capacity. Coupled with this is the recognition that IP/Ethernet is the transport media of choice for expanded backhaul services.

For many operators the introduction of Ethernet will be on the back of existing TDM network connections given their huge investment in its infrastructure. This will typically involve gradual migration using data overlay, with a decision at some future point to change to an all packet-based network. The transition phases may well include instances where there is a need to transport Ethernet alongside TDM, or Ethernet over TDM, and do so in a flexible, secure and cost efficient way.

Whatever the need, Eclipse Packet Node provides optimized solutions through its unique packet and circuit switched architecture for Ethernet and TDM.

Assisting the upgrade route are Packet Node solutions for better spectrum efficiency. Using high-order modulation, adaptive modulation and co-channel options, more traffic can be transported more efficiently on existing channel bandwidths.

Carrier grade Ethernet performance is provided on an intelligent Layer 2 switch to ensure Ethernet data transport is no less secure than for TDM. When coupled with advanced traffic prioritization, RSTP, link aggregation, network synchronization, bandwidth optimization and traffic aggregation, there is a Packet Node solution for all microwave network topologies.

Security is also a high profile issue. Although microwave radios have security-like features such as scrambling, narrow beamwidth, proprietary airframe coding and other factors, it is not hard to break given the expertise and intent. The Strong Security suite for Eclipse offers solutions for strict wireless network protection through Payload Encryption, Secure Management, and RADIUS Client.

The backbone for this capability is the Eclipse INU where software applications and plug-in cards upgrade existing Eclipse Node capabilities to Eclipse Packet Node. There is maximum retention of existing Eclipse hardware and software, which equates to maximum value-add and minimum disruption to existing services.

Finally, Eclipse comes with an assurance from Aviat Networks that value-adds will continue to become available to existing and new Eclipse customers to deliver more features and more performance. It is a promise of low-risk, low incremental cost, and a future-proof investment in Eclipse.

INTRODUCTION Typically, a small number of DS1s has been sufficient to service 2G and 2.5G base stations, but with the data capacity needed for advanced 3G and 4G HSPA/LTE applications, new technologies and strategies are required.

This need for more capacity must be provided more intelligently, and more efficiently, especially so where the backhaul networks are, or will be required to support multiple services and customers—not just cellular mobile, and not just one operator. There is also a need to ensure service continuity for old and new technologies, given that operators will want to maximize investments in existing 2G/3G infrastructure.

Going forward, the most cost-effective backhaul technology to deliver more capacity, more intelligently, is Carrier Ethernet. It provides the scalability, flexibility and QoS features needed to provide a complete solution—from the core to base stations.

In networks where wireless provides the backhaul, these developments raise some issues. For example, how do you upgrade wireless connections for more capacity? Do you increase capacity of


WHITE PAPER


current TDM links? Do you overlay with Ethernet for extra capacity? Do you move to all-Ethernet?

Whichever way is forward, there is a cost efficient solution using Eclipse. Of special note is that one Eclipse Packet Node now supports up to six links and a programmable total nodal throughput of more than 2 Gbit/s Ethernet, and up to 127xDS1 or 2xOC3.

ECLIPSE PACKET NODE Eclipse Packet Node is the most flexible wireless platform for network migration. With a multi-link capability, advanced features for high capacity packet transport and intelligent IP networking, coupled with support for TDM, it delivers complete solutions for transitioning networks from TDM to IP.

At the heart of Eclipse Packet Node is a unique data packet plane (DPP) that operates independently of the circuit-switched backplane. The DPP routes Ethernet traffic directly between its GigE switch and packet radio modem(s) to deliver maximum payload efficiency with lowest latency. The backplane also connects radio modem(s) to support hybrid mixed-mode operation and to access wider aggregation and synchronization options. In combination, they optimize transport options for Ethernet and for Ethernet+TDM.

Plug-in-card and software options ensure there is always the right option available to meet current and projected needs. Cards are hot-swappable for easy reuse/relocation, as and when needed.

Packet Node features include:

• Advanced GigE switch with 1+1 redundancy options

• High-capacity links with QPSK to 256 QAM ACM and XPIC/CCDP options

• Advanced L1 and L2 link aggregation

• ML-PPP Ethernet over NxDS1

• Synchronous Ethernet

• Easy upgrades with low incremental cost

• Maximized flexibility and scalability for Ethernet or Ethernet +TDM

• Comprehensive OAM capabilities in conjunction with its ProVision EMS.

Figure 1. Packet Node High-level Architecture


WHITE PAPER


The data packet plane (DPP) supports multiple GigE connections with link capacities to 365 Mbit/s and L1 throughputs to 450 Mbit/s.

127xDS1. Mixed-mode operation accommodates a low-risk PDH now

s.

ore radio modem cards, which in turn

PLATFORM Packet Node comprises the INU or INUe, with ODUs for split-mount

IRU 600 for or all-indoor. The INU directly

city to 365 Mbit/s

rds the required performance and

EXTENDED ODU AND RFU OPTIONS There is a choice of two ODUs, or an all-indoor RFU.

for frequency bands 6 to 11 GHz

r consumption

based antenna coupler options

nfigurations

patible on bands 6-11 GHz

market. There is an optimized

The circuit plane (backplane) interoperates with the DPP to support native mixed mode Ethernet + TDM, with PDH capacities up toand Ethernet tomorrow transport philosophy.

• Packet Node backplane connections support Ethernet plus Super-PDH, with capacities up to 200 Mbit/s or 127xDS1 in 1.5 Mbit/s / DS1 step

• DPP connections support up to 2 Gbit/s aggregated.

• DPP and/or backplane traffic is connected to one or mconnect to an RF unit (ODU or IRU 600).

operation, or thesupports up to three links; the INUe up to six.

• Operation on licensed bands 5 to 38 GHz

• Each link can be configured for an air-capa

• With data optimization techniques, each supports L1 throughputs to 450 Mbit/s

• An INU or INUe is simply populated with the mix of caneeded at any time to provideoperation

• Equipment, cabling and rack space is dramatically reduced

• Cards are hot-pluggable for easy upgrading and maintenance

• ODU 300hp for frequency bands 6 to 38 GHz

• ODU 300ep for 5 GHz

• IRU 600 all-indoor RFU

• Industry-leading system gain coupled with lowest powe

• 1+1 optimized

• Diplexer and filter

• Expansion port option

• Expandable to M+N co

• Air compatible with ODU 300hp

• ODU 300hp and IDU 600 are air-com

These ODU and RFU options have been fine-tuned for the wider U.S.solution for all platform preferences.


WHITE PAPER


PLATFORM INTEROPERATION Eclipse Packet Node supports over-air linking with the Aviat Networks IDU GE 20x or IDU ES for edge-

e radio terminals, comprising an IDU and ODU; unlike

terfaced to Eclipse Packet Node

ghputs to 243 Mbit/s

ide powerful, cost-efficient solutions where the multi-link capabilities

Eclipse Packet Node supports link configurations for TDM only, Mixed-mode Ethernet + TDM, MLPPP thernet. Transitioning from one mode to another is a straight-forward

upports link capacities to 127xDS1, 4xDS3, or 2xOC3.

DM. It enables Ethernet to be owing data demand. It means investments in existing

t

gE card, at which point an remotely configure the capacity split between PDH and Ethernet in DS1 or 1.5

nimal

of-network 1+0 connections. These IDUs arEclipse Packet Node they have no multi-link capability. They can be used as a single link, or networked where IDUs are back-to-back connected via their tributary ports at intermediate sites.

For IDU GE 20x a built-in Ethernet switch supports capabilities similar to those on Eclipse Packet Node. On the IDU ES the built-in switch function is more basic.

• Operation on licensed bands 6 to 38 GHz using ODU 300hp

• Configurable for air-capacities to 196 Mbit/s when air-in

• L1 throu

• Ethernet plus up to 20x DS1 trib circuits for IDU GE 20x, or up to 8xDS1 for IDU ES

Both IDU GE 20x and IDU ES provof Eclipse Packet Node are not needed for last-mile connections.

OPERATIONAL MODES

for Ethernet over NxDS1, or all-Eprocess.

TDM ONLY Eclipse s

MIXED-MODE TDM+ETHERNET Hybrid mixed-mode transports native Ethernet side-by-side with Toverlaid on a TDM network to meet the rapidly grTDM infrastructure can be maximized, and the risks associated with the introduction of Etherneminimized. Network synchronization is maintained via the TDM connections, something not possible with Ethernet without resort to purpose-built sync solutions.

The ratio of link capacity assigned between Ethernet and TDM can be changed at any time.

Figure 2. Mixed Mode

Adding Ethernet to an NxDS1 link simply requires installation of a Gioperator can locally orMbit/s steps. It means Ethernet can be activated when and where needed in the network with midisruption. There is no loss of transport efficiency when a mixed-mode link is ultimately migrated to anall-Ethernet payload.


WHITE PAPER


When more data capacity is needed, Eclipse options include adaptive modulation, or link aggregation with XPIC/CCDP to double or quadruple traffic bandwidth.

Figure 3. Mixed-mode Eclipse Packet Nodes

s based on PPP, a standards-based data-link-layer PPP bonds multiple PPP connections to support one connection with a capacity totalling

DM

gineered at any time. The transition can be directly from is replaced by Ethernet, or from an intermediary mixed-mode solution, where

rd(s) removed.

e card(s) removed.

NE NCE Eclipse Packet Node elements detect and recover from incidents without affecting priority users. Protection options support user interfaces, links, platform and network.

Figure 3 illustrates possible mixed-mode configurations. Capacities indicated are airlink capacities.

MLPPP MLPPP (Multi-Link Point-to-Point Protocol) iprotocol. MLthe individual connections. With Eclipse, MLPPP is used to leverage existing capacity on legacy Tlinks whereby multiple DS1 circuits are bonded together to support one high-capacity connection for Ethernet. It enables retention of end or mid-point legacy NxDS1 links (short or long term) within a network during migration to Ethernet.

Figure 4. MLPPP, Ethernet Over Multiple DS1s

ALL-ETHERNET Transition to all-Ethernet operation can be enTDM, where TDM traffic the TDM traffic is phased out in favour of Ethernet.

• Changing to all-Ethernet operation on existing Eclipse TDM links is a simple upgrade; an Ethernet switch card is installed and the TDM interface ca

• Changing from mixed-mode Ethernet+TDM to all-Ethernet only requires a configuration change. Alllink capacity is simply directed to Ethernet, and the TDM interfac

• However, transition to all-Ethernet will require a sync solution where the supported equipment requires a network-sourced clock reference. Eclipse supports various options. See SYNCHRONIZATION.

TWORK RESILIE


WHITE PAPER


PLATFORM PROTECTION card.

LINK/PATH PROTECTION , space diversity, frequency diversity, or hybrid dual diversity.

INTERFACE PROTECTION omprehensive protection of Ethernet and TDM interfaces. A

card on failure of the operational card.

g networks using RSTP, and on link-aggregated links.

R™, which accelerates industry-standard RSTP (802.1D-2004) ide reconvergence (service restoration)

times as low as 50 ms on wireless links.

•

e offers Layer 1 (L1) and Layer 2 (L2) link aggregation

y ring

ization of devices supported from the network.

FPs

se INUe supports an aggregate capacity to 2+ Gbit/s - one DAC GE3

, plus six backplane ports. The front panel ports are for user-connections and direct Data Packet Plane (DPP) connection to high

•

e oversubscribed to ensure high priority traffic continues to get through – at the expense of lower priority traffic. Tools provided by

:

INU platform management and power supply functions are protected using an optional protection

Protection options include hot-standby

Card redundancy is used to provide csecond card of the same type is installed and configured so that traffic is transferred to the standby

NETWORK PROTECTION Network-based protection is provided for Ethernet and TDM.

Ethernet redundancy is supported on rin

• RSTP is enabled on Eclipse RWPwith a unique rapid failure detection (RFD) capability to prov

Link aggregation - sometimes referred to as N+0 protection. If one link fails, its traffic is directed onto the remaining link(s), typically within 10 ms. If the remaining link(s) do not have the capacity needed to avoid a traffic bottleneck, QoS settings are used to ensure higher priority traffic continues to get through. Uniquely, Eclipsoptions.

For TDM ring networks Eclipse Super PDH protects ring capacities to 100xDS1. Rings are implemented by east/west facing links to form a closed loop. Both North Gateway or Any-to-Antopologies are supported.

ETHERNET FEATURES An extensive range of switch-based options support the transport, aggregation and protection of Ethernet traffic, and the synchron

SWITCH CAPACITY The GigE switch has both electrical 10/100/1000Base-T and optical 1000Base-LX ports. Optical Sare available for 1300nm single or multimode, or 850nm multimode.

• One DAC GE3 in an Eclipdirectly supports up to six separate radio links.

• The switch has three RJ-45 and two optical SFP front panel ports

capacity radio modem cards. The backplane ports also provide connection to radio modem cards.

There is full bi-directional support for Jumbo frames to 10 Kbytes.

TRAFFIC SHAPING Traffic shaping and prioritization tools provide a means to efficiently manage traffic transiting Eclipse links. They particularly apply where available Ethernet bandwidth can b

Eclipse Packet Node include

• Queue management on 136 Kbytes of memory for each ingress/egress port pairing to provide good balance between burst management and latency.


WHITE PAPER


• Priority Mapping options on ports and on 802.1p and DiffServ tags to shape packet access to available bandwidth. Eight QoS queues per port maximize flexibility for transporting different traffic

and hybrid WRR + strict.

back data from sending devices and thereby reduce demands on

ves a

capacity is made available for payload data.

no payload data – they can therefore be suppressed for

es, 6 percent on

n a wireless backhaul network, required frequency synchronization has

en y a GPS receiver installed at the site.

uality of this clocking net;

erring a clock reference.

e

r an Ethernet

et transports timing information using a clock signal injected into the bit stream, ts

neighbor. It means every intervening node (switch/router) within the network must support

uch

types with related priorities.

• Priority Scheduling with extended options for WRR, strict,

• Traffic Classification by VLAN Q and Q-in-Q tagging using the CoS/802.1p prioritization bits. Tagging can be retained into an external network for downstream traffic management.

• Flow Control option to throttlerestricted Ethernet bandwidth.

THROUGHPUT OPTIMIZATION Ethernet throughputs are maximized through use of IFG and Preamble suppression. This involreduction of the byte-count used to transport Ethernet data end-to-end over a link, thereby increasingdata transport efficiency; more link

• The IFG and Preamble frame bytes carry transmission over a radio link and reinstated at the far end. The benefits are most apparent on small frame sizes where the IFG and Preamble bytes are a higher percentage of the frame total.

• The reduction in frame space improves throughput 23 percent on 64-byte framaverage-size 260-byte frames, reducing to 1% on 1518 byte frames.

SYNCHRONIZATION Mobile base stations must be synchronized to support hand-off between cells, and to ensure frequencies on the air-interfaces have the accuracy and stability needed to minimize channel interference.

• For GSM / UMTS nodes otraditionally been met by using the clocking from a TDM (DS1) connection.

• For CDMA nodes requiring a time-referenced phase sync source, clocking has typically beprovided b

• For next generation 4G/LTE base stations, phase synchronization is an expected requirement.

On networks where synchronization is provided via TDM network clocking, the qmust be maintained during migration to IP/Ethernet. At issue is the nature of standard 802.3 Etherit is asynchronous - it contains no provision for transf

But there are solutions through Synchronous Ethernet, or IEEE 1588v2 packet-based timing. EclipsPacket Node supports both, plus options for clock maintenance through mixed mode, or Eclipse Distributed Sync.

Currently only IEEE 1588v2 has an ability to support phase synchronization oveconnection.

Synchronous Ethernet

Synchronous Ethernmuch like TDM. Each device in the network recovers, cleans, and then distributes the clock to idownstream Synchronous Ethernet.

• SyncE can only distribute frequency; it cannot distribute phase alignment or time of day (ToD).

• SyncE clocking is unaffected by data delivery impairments in the higher packet-plane layers, sas the delays caused by queuing and re-routing on heavily loaded networks.


WHITE PAPER


• Clock quality requirements (jitter and wander) are equivalent to that specified for TDM networks within G.823 / G.824. Clock transfer is supported between TDM and SyncE sections of the same network.

• On Eclipse radio links the clocking to support SyncE operation uses Eclipse Distributed Sync.

• Upgrading to Synchronous Ethernet simply requires installation of a DAC GE3 switch card, and a SyncE feature license.

ithin the data packet stream to maintain a Master-Slave ationship.

e et

.

e network.

duced on the back of existing connections.

It supports flexible migration without compromising existing TDM synchronization. EDS also provides a totally reliable and risk-free timing solution for Eclipse SyncE

ll ng

vant to wireless links that require traffic capacities

higher than the maximum possible on one radio channel link - two links are operated in the same RF aggregated to provide one logical link of twice the capacity.

IEEE 1588v2

1588v2 is a Precision Timing Protocol (PTP) for phase and frequency synchronization. Dedicated timing packets are transmited wsynchronization rel

• Time-stamped PTP packets are sent from the master clock to the slave clocks, and from the slavclocks back to the master. A timing recovery algorithm uses these packets to calculate and offsthe delays and differences in delay (packet delay variation or PDV) across a network

• PDV represents the most significant impairment factor – synchronization accuracy can be affected on heavily loaded networks.

• Because it works in the IP data path it does add a small amount of additional traffic to th

1588v2 frames are transported transparently by Eclipse Packet Node.

Mixed Mode

Eclipse uses the TDM links within mixed mode Ethernet+TDM links to retain support for traditional TDM clocking. It particularly applies to networks where Ethernet is introTDM network

Eclipse Distributed Sync (EDS)

Eclipse Distributed Sync multicasts a DS1 circuit throughout the network to maintain existing TDM clock accuracy and stability.

connections.

• Instead of a dedicated DS1 circuit per destination, one DS1 is used throughout the network for adestinations. It is for sync purposes only. At network nodes the DS1 is captured from the incomilink, and included as required on outgoing links.

• While a DS1 is included alongside the Ethernet data on each link, the effective cost of this usage issmall compared to the time, risk and cost of implementing generic IEEE 1588v2 or Synchronous Ethernet solutions.

EDS provides a seamless frequency synchronization solution when migrating from TDM to an all-Ethernet backhaul. It is fully scalable from small to large networks, and its multicast nature means it is available at all points within an Eclipse network.

LINK AGGREGATION Link aggregation combines two or more links into a single logical link to provide a traffic capacity that isthe sum of the individual links. It is especially rele

channel using CCDP, then link

Link aggregation also provides redundancy. If one link fails, its traffic is redirected onto the remaining link(s). Effectively this is N+0 protection - all links in the aggregation group carry traffic, and provide protection for each other. If the remaining link(s) do not have the capacity needed to avoid a traffic bottleneck, QoS settings ensure all higher priority traffic continues to get through.


WHITE PAPER


Eclipse Packet Node has L1 and L2 link aggregation options:

• L1 aggregation acts on the byte data stream. Unlike L2 link aggregation, it provides optimum payload sharing regardless of individual connection throughput demands - ideal for router-routeconnections.

r

MAC address data in the Ethernet

NTERFACE PROTECTION D

BFD is designed for fast path failure detection on Ethernet and other media. Separate connections are d the BFD protocol. If BFD detects a failure of

Essentially is about network transport infrastructure and service delivery. The underlying net are met in the Access, Metro and Core

ndards to provide an assurance that it will w and into the future.

ckhaul Group, whose aim is to ile/cellular networks.

layer

performance, . Features include:

Ethernet history, and Ethernet data-

N)

• L2 link aggregation (802.3ad) uses source and/or destination frame MAC/LLC header.

ETHERNET ITwo configurations are available to support protection of the GigE switch cards, one based on the BFprotocol (Bidirectional Forwarding Detection), the other on Y-cables.

established from paired GigE cards based on VLANs anthe primary VLAN or physical interface, all traffic is automatically allocated to the secondary VLAN to provide true 1+1 protection on Eclipse and the connected equipment.

Y-cable protection is used where the connected equipment does not support BFD. A single connection is established to the connected equipment from paired GigE cards. Full 1+1 protection is provided on Eclipse, but not on the connected equipment.

CARRIER GRADE OPERATION Carrier Ethernet is defined by the MEF (Metro Ethernet Forum) as a ubiquitous, standardized, carrier-class service. Various attributes distinguish it from familiar LAN based Ethernet.

principle is that the attributes of Carrier Ethernetworks to deliver a seamless, performance and cost optimized solution between all users.

For an Ethernet device to be considered carrier grade, it must meet relevant MEF requirements. Those for standardized services, reliability, scalability, QoS and service management are specified within MEF 9 and MEF 14.

• MEF 9 specifies the UNI (Universal Network Interface)

• MEF 14 specifies the QoS (Quality of Service) parameters.

Eclipse Packet Node is certified compliant with these stainteroperate with other certified carrier Ethernet devices, no

Aviat Networks is also a founding member of the MEF Mobile Bapromote and define the use of Carrier Ethernet services for mob

CARRIER GRADE OAM The ProVision EMS for Eclipse supports relevant requirements within ITU Y-1731 for the serviceand within IEEE 802.3ah for the link layer. Every Eclipse device in a network is visible to network operators together with the tools needed to determine device and network status andand to effect changes when needed

• Fully integrated management of the radio and its Ethernet traffic. For example, where Ethernet performance is being affected by radio performance, the problem is easily diagnosed using common user-friendly interfaces.

• Ethernet diagnostics with RMON performance data, dashboards for throughput, errors and discards.

• End-to-end network mapping, circuit provisioning and performance monitoring at service (VLAand link levels.


WHITE PAPER


• Strong security is supported via SNMPv3 and a RADIUS Server option.

• A Multi-Technology Operations System Interface (MTOSI : TMF 854) supports ProVision

probable cause and remedial advice.

t, fuel usage reporting

interfacing with MTOSI-standardized management systems.

• Error events with

• Site energy and security management with system status, fault managemenand energy control history.

Figure 5. Example ProVision EMS screens for Network Health and Bandwidth Utilization

LINK CAPACITY AND SPECTRAL EFFICIENCY Superior capacity and spectrum efficiency gains are a feature of Packet Node through adaptive coding

re than 99.5 percent of the time.

s is only needed to protect the link against worst-case fades that may occur just a few

to ensure

and modulation (ACM), and co-channel dual polarized (CCDP) link operation.

ADAPTIVE CODING AND MODULATION Instead of using a fixed modulation rate to provide a guaranteed capacity and service availability under all path conditions, the modulation rate, and hence capacity, is increased when path conditions permit to provide a higher capacity. Typically, this higher capacity will be available for mo

• Adaptive modulation is the dynamic adjustment of modulation rate to ensure maximum data bandwidth is provided most of the time, with a guaranteed bandwidth provided all the time.

• A link may be designed to have as much as 30 dB of fade margin to support 99.999% availability. However, thiminutes in a year. For the rest of the year, the margin is not used.

• By using less robust but more efficient modulation schemes, the available fade margin is transformed into delivering more data throughput - adaptive modulation dynamically changes the modulation so that the highest modulation and hence highest availability of capacity is provided at any given time.

• When used in conjunction with QoS traffic shaping and prioritization, it can be configured all high priority traffic continues to get through when path conditions deteriorate; only low priority “best effort” data is discarded.


WHITE PAPER


Figure 6 illustrates Packet Node modulation/capacity steps and typical percent availability over time for QPSK to 256 QAM ACM. QPSK, as the most robust modulation, is used to support the critical traffic.Less critical traffic is assigned to th

e higher modulations. Most importantly, the highest modulation is

a combination of

ynamically switched modulations - QPSK, 16 QAM, 64 QAM or r

in, to provide a total of eight modulation states, any four of which can be selected

l four modulations are selected (QPSK to 256 QAM) , each can be set for maximum

rate (any) can be ation.

ossible steps can be selected.

argin for best averaged throughputs.

typically available for more than 99.5 percent of the time and supports four times the capacity of QPSK.

Figure 6. Adaptive Modulation at Work

Packet Node adaptive modulation is an end-to-end solution for Ethernet only, orEthernet and TDM.

It uses one of four automatically and d256 QAM. Uniquely, each modulation has two coding options, one for maximum throughput, one fomaximum system gafor ACM.

• Maximum throughput delivers maximum data throughput - at the expense of some system gain. Maximum gain delivers best system gain - at the expense of some throughput.

• When althroughput or maximum gain.

• With three modulations selected, such as 16 QAM, 64 QAM and 256 QAM, oneset for maximum gain and additionally for maximum throughput, to provide four step AM operOr just three (any) of the four p

• With just two modulations selected, such as 64 QAM with 256 QAM, each can be set for maximumgain and additionally for maximum throughput, to provide four step AM operation. Or just two, or three out of the four possible steps can be selected.

• For FCC bands 6 to 11 GHz 64 QAM is the minimum permitted rate for adaptive modulation, meaning operation is restricted to between 64 QAM and 256 QAM. Here Eclipse ACM supports four-step operation to fine-tune on the available fade m


WHITE PAPER


• For a given RF channel bandwidth, ACM provides a nominal two-fold improvement in data throughput for a change from QPSK to 16 QAM, a three-fold improvement to 64 QAM and a fourfold improvement to 256 QAM.

-

ority .

best traffic efficiency (payload mapping) on each modulation.

/or increasing the modulation rate cannot provide the capacity needed, CCDP provides an answer. It enables two links to operate on the same

een the channels is effectively eliminated.

) support 4x the capacity of a single link, using two RF channels.

• Modulation switching is hitless. During a change to a lower modulation, remaining higher pritraffic is not affected. Similarly, existing traffic is unaffected during a change to a higher modulationTraffic shaping is used to ensure

• Ethernet connections enjoy real synergy through the QoS awareness on the GigE card and the service provisioning provided by any MPLS or PBB-TE network overlay. All high priority traffic, such as voice and video, continues to get through when path conditions are poor.

• Any DS1 connections are dropped in user-specified order when link capacity is reduced , and restored when capacity is increased.

Figure 7 shows the air-link capacities for each modulation, by channel bandwidth.

Figure 7. Eclipse Packet Node Adaptive Modulation Steps

CO-CHANNEL DUAL POLARIZED LINKS (CCDP) In situations where increasing the channel bandwidth and

channel to double the wireless capacity.

• Under CCDP, two parallel communication links are operated on the same RF channel: one usingthe vertical polarization, the other the horizontal. Cross Polarized Interference Cancellation (XPIC)is used to ensure any interference betw

• The capacity on each link can be used for IP, or IP+TDM.

• If both links are configured for IP traffic, the two traffic streams can be link-aggregated (L1 or L2) to a single customer user interface.

• CCDP Links can be 1+1 or ring protected.

• Where even higher capacity links are needed, three or four links can be installed. For example, two CCDP link pairs (four links in total


WHITE PAPER


Figure 8 illustrates a CCDP mixed-mode link on a 50 MHz channel with 256 QAM maximum throughput modulation. The combined link capacity of 636 Mbit/s is used for Ethernet + 16xDS1. With IFG and Preamble suppression, the 611 Mbit/s available for Ethernet supports L1 throughputs to 758 Mbit/s.

Figure 8. 636 Mbit/s Link Aggregated Mixed-Mode Link

Figure 9 illustrates a CCDP RSTP node with east-west links on 50 MHz channels with 256 QAM, Maximum Throughput modulation. With IFG and Preamble suppression, the links support Ethernet throughputs to 790 Mbit/s.

Figure 9. 650 Mbit/s Link Aggregated RSTP CCDP Ring Node

STRONG SECURITY ta and voice communications are held

secure end-to-end. But given the reality that migration towards IP does provide increased opportunity on backhaul networks must be reviewed.

t

t, and e

Institutional and individual users assume their networked da

for data and call interception, security

As well as security for the payload there is also the issue of securing the physical network to prevenequipment being compromised or taken over by unauthorized parties. At the other end of the scale, there is potential for unintentional miss-configuration by low-level but unauthorized users.

What’s needed is a high level of security for both payload and management traffic. Traditionally, microwave networks have not included such purpose-built capabilities.

Uniquely, Eclipse provides strong solutions. With Payload Encryption, Secure ManagemenRADIUS Client, Eclipse Strong Security ensures there is no potential for non-secure access to thradio payload or to the management interfaces.


WHITE PAPER


PAYLOAD ENCRYPTION Payload Encryption secures wireless data and in-band and out-of-band management traffic. Operation is FIPS-197 compliant and features an AES-CCM cipher suite with AES counter mode data encryption and CBC-MAC data integrity validation.The integrity of each data frame sent over the link is checked to ensure that received data has been sent by the intended transmitter, and if it detects that received data has been modified (man-in-the-middle attack), then received data is replaced with AIS.

SECURE MANAGEMENT Secure Management offers secure management access to Eclipse Packet Node radios over unsecured networks. It protects the radio from accidental or intentional miss-configuration and provides centralized access control based on sophisticated permission attributes. An event logger records all management activity for proper accountability and optimum troubleshooting support.

Security is provided through use of encrypted communication protocols, a requirement for complex passwords, and protection against mechanized attacks. Communication encryption is based on a FIPS140-2. SNMPv3 is used to secure the management communication connections.

RADIUS CLIENT An integrated RADIUS capability enables authentication, authorization and accounting of user accounts from a remote RADIUS Server for central management of Eclipse user accounts.

The RADIUS remote server provides centralized management and authentication of user names, passwords, and access permissions, and ensures that all users have consistent access privileges throughout the network, using a common set of user credentials. When a user attempts to login to a RADIUS Client (Eclipse radio), the radio sends the authentication request to the RADIUS server. Communication between the RADIUS client and the RADIUS server is authenticated and encrypted, and the RADIUS server accounting database maintains a log of all requests, access times and durations.

CONCLUSION Eclipse Packet Node is optimized for transforming networks to all-IP. You can single-step from TDM to all-IP or go step-by-step starting with an overlay of Ethernet on existing TDM links and adjusting the overlay to ultimately reach an all-IP goal. At each step, there is a low-cost card or software based solution to support required network infrastructure for more capacity, better spectral and data efficiency, wider redundancy options, tighter QoS, sync options, legacy traffic support, and strong security.

This incremental approach has much to recommend it. Change can be made without the risk, downtime and expense often associated with a complete platform change-out. No other node offers the flexibility, scalability, low-cost migration, reliability and ultimate sophistication and capacity grunt for new generation wireless backhaul.


WHITE PAPER


GLOSSARY ACM Adaptive coding and modulation. AES Advanced encryption standard. An encryption standard adopted by the U.S.

government. It comprises three block ciphers, AES-128, AES-192 and AES-256. AIS Alarm indication signal. CCM Combined cipher machine. CBC Cipher block chaining. CCDP Co-channel dual polarized. EMS Element management system. FIPS Federal information processing standards. HSPA High speed packet access. LTE Long term evolution. Evolving standard for 4G mobile networks. MAC Media access control. MEF Metro Ethernet Forum. PDH Plesiosynchronous digital hierarchy. Asynchronous multiplexing scheme in which

multiple digital synchronous circuits run at slightly different clock rates. QAM Quadrature amplitude modulation. QoS Quality of service. QPSK Quadrature phase shift key. RADIUS Remote authentication dial In user service. RSTP Rapid spanning tree protocol. RWPR Resilient Wireless Packet Ring. SDH Synchronous digital hierarchy. Transmission rates range from 51.84 Mbit/s (STM0/OC1)

and 155.52 Mbit/s (STM1/OC3) through to 10-plus Gbit/s. SFP Small-form-factor pluggable. SLA Service level agreement. SNMP Simple network management protocol. TDM Time division multiplexing. Multiple low-speed signals are multiplexed to/from a high-

speed channel, with each signal assigned a fixed time slot in a fixed rotation. VLAN Virtual LAN. IEEE 802.1Q tagging mechanism. XPIC Cross-polarized interference cancellation. Some Eclipse Packet Node features may be subject to availability. Contact your Aviat Networks representative for details.



WHITE PAPER


WWW.AVIATNETWORKS.COM

Aviat, Aviat Networks, and Aviat logo are trademarks or registered trademarks of Aviat Networks, Inc.

© Aviat Networks, Inc. 2010. All Rights Reserved.

Data subject to change without notice.

_w_MobNet_EcliPktNode_ANSI_July2010

eclipse packet node in the mobile network ansi white paper

Documents