FibeAir

IP-10
G-Series

TDM Adaptive Band Recovery (ABR) Path Protection

Proprietary and Confidential

BW utilization with standard SNCP

A major drawback of ring topology is the allocation of redundant bandwidth in
order to ensure network availability:
Active
Trail

For example, the widely-implemented

SNCP 1+1 unidirectional protection
scheme requires the simultaneous
transmission of information in both
directions on the ring
SNCP trails
consume double
BW, hence less is
available for ETH

This causes a loss of up to 50% of the

rings total bandwidth capacity!

Duplicated
(Protective)
Trail
2

Proprietary and Confidential

A novel approach to BW Efficiency

Ceragons FibeAir IP-10, is capable of protecting TDM services without
reserving large quantities of bandwidth

Ceragons novel approach improves the efficiency of ring-based protection,

using a technique called Protected Adaptive Bandwidth Recovery (ABR)
which enables full utilization of the bidirectional capabilities inherent in ring
technologies

In the event of a failure, the system reverts back to standard SNCP and the
unused capacity is re-allocated for TDM transmission

Proprietary and Confidential

A novel approach to BW Efficiency

With ABR, the TDM-based information
is transmitted in one direction only,
while the unused protection capacity is
allocated for Ethernet traffic

Unused or Pending
SNCP trail capacity is
allocated for ETH
services

Proprietary and Confidential

Active
Trail

ABR Operation

ABR SNCP Operation

The ABR feature consists of the following components:

1. Signaling is distributed between the end-points of every trail point to

exchange information about the quality of the received signals

2. Logic determines in which cases traffic can or cannot be sent through one of
the paths

3. Automatically freeing bandwidth whenever TDM traffic is not being sent

4. Selecting the incoming traffic normally as explained for SNCP trails

Proprietary and Confidential

ABR SNCP Operation: Signaling

1 of
4

Signaling is distributed between the end-points of every trail point to exchange

information about the quality of the received signals

Each end-point may send an RDI signal along each path (primary and
secondary) to the other end point

RDI is sent whenever a valid TDM trail signal is not received

Proprietary and Confidential

ABR SNCP Operation: Logics

2 of
4

Logic determines in which cases traffic can or cannot be sent through one of
the paths:

Under normal conditions, TDM traffic is sent only through the primary path
In order to make proper use of the freed capacity, it is necessary for the Ethernet
traffic to use the same path in both directions

For this reason, any failure in the primary path will cause both sides to revert to
the normal mode of operation (sending traffic through both paths). Traffic will
return to the primary path after the failure condition has been cleared (the
mechanism is revertive)

In order to prevent jittering of the path and unnecessary traffic switches in case of

intermittent primary path failures, there is a revertive timer. This timer determines
the amount of time require after no failure is detected in the primary path before
ceasing traffic transmission through the secondary path
Proprietary and Confidential

ABR SNCP Operation: Auto BW Release

3 of
4

Automatically freeing bandwidth whenever TDM traffic is not being sent:

Whenever valid TDM traffic is not available at the radio interface for transmission,
its bandwidth is automatically re-allocated for Ethernet traffic

This is relevant not only for ABR trails, but for all TDM traffic. In other words,
bandwidth is freed up whenever there is no information to transmit. This may
occur in the following circumstances:
1. A failure has occurred which interrupts TDM traffic in a certain trail. This
may take place in a radio link or an internal connection
2. No valid TDM input (E1/DS1 signal) is received at the end-point
3. AIS signal is detected at the input (if AIS detection feature is enabled)

Proprietary and Confidential

ABR SNCP Operation: Receiving Standard SNCP

Selecting the incoming traffic normally as explained for SNCP trails:

The ABR mechanism is relevant only for the transmission

Reception is dealt with in the same manner as normal SNCP trails

10

Proprietary and Confidential

4 of
4

ABR Configuration

ABR SNCP Configuration

A new type of trails (ABR trails) is defined, in addition to protected and
unprotected trails.
ABR trails are configured exactly in the same way as normal SNCP trails and
are subject to the same validations. This is because in the worst-case (failure
condition) ABR trails behave like normal SNCP trails, occupying bandwidth in
both paths.
The following are extra configuration and behavior exclusive for ABR trails:

Revertive timer: the same timer is used for all trails

Forcing ABR trails: when forcing reception of an ABR trail from the secondary path the
system will automatically cause both end-points to transmit traffic through that path,
regardless of failure conditions. The traffic will cease to be sent when force none is
configured

12

Proprietary and Confidential

ABR SNCP User Indications

The following indications are added for TDM trails:

RDI indication is given per trail to the user

Separate status indications are given for each path:
For SNCP trails, status is always given for primary and secondary paths
For ABR trails, status is given for paths which are currently transmitting; with no
failure conditions this means the primary path only.
PMs are collected as follows:
1. Primary is active No PM counted on secondary.
2. Secondary is active (due to primary failure or force to standby) PM
counted on primary and on secondary.

13

Proprietary and Confidential

Thank You !
training@ceragon.com

14