Professional Documents
Culture Documents
Version 13
General Description
426006-2018-013-A01
BroadGate Product Line General Description
V13
Catalog No: X38443
November 2010
nd
2 Edition
Management........................................................................... 10-1
Layered Architecture ...................................................................................... 10-1
Client/Server Architecture .............................................................................. 10-2
Integration with Other Products ...................................................................... 10-3
LightSoft Network Manager ............................................................................ 10-3
Figure 5-15: Triple play network solution for IPTV, VoD, VoIP, and HSI services ...... 5-20
Figure 5-16: Metro network illustration......................................................................... 5-23
Figure 5-17: P2P MPLS tunnel example...................................................................... 5-26
Figure 5-18: EPL service.............................................................................................. 5-27
Figure 5-19: VPLS service example ............................................................................ 5-28
Figure 5-20: E-LAN service .......................................................................................... 5-30
Figure 5-21: CES Application ....................................................................................... 5-32
Figure 5-22: Multidomain Ethernet service OAM ......................................................... 5-34
Figure 5-23: CFM: Continuity check functionality ........................................................ 5-35
Figure 5-24: CFM: Loopback protocol ......................................................................... 5-36
Figure 5-25: CFM: Link trace ....................................................................................... 5-36
Figure 5-26: ACL description ....................................................................................... 5-37
Figure 5-27: Port mirroring ........................................................................................... 5-38
Figure 6-1: XIO30 general block diagram ...................................................................... 6-7
Figure 6-2: XIO64/XIO16_4 general block diagram ....................................................... 6-8
Figure 7-1: GbE Ethernet radio service with native TDM capabilities ........................... 7-3
Figure 7-2: BG-Wave multiservice radio transmission ................................................... 7-3
Figure 7-3: MRAN multiservice capabilities ................................................................... 7-4
Figure 7-4: BG-Wave product line ................................................................................. 7-6
Figure 7-5: MW network service for today and tomorrow ............................................ 7-10
Figure 7-6: WiMAX backhauling service ...................................................................... 7-12
Figure 7-7: Fixed-line access backhaul ....................................................................... 7-13
Figure 7-8: BGW-10 platform with MIF-10 and STM-1/OC-3 cards in the traffic
slots .............................................................................................................................. 7-15
Figure 7-9: BGW-10 slot allocation (2) ......................................................................... 7-16
Figure 7-10: BGW-20E expansion unit ........................................................................ 7-16
Figure 7-11: BGW-E/20E block diagram...................................................................... 7-17
Figure 7-12: BGW-E expansion unit ............................................................................ 7-18
Figure 7-13: BGW-E/20E slot allocation ...................................................................... 7-19
Figure 7-14: MW_2M with two MIF modules ............................................................... 7-20
Figure 7-15: MW_2 functional block diagram .............................................................. 7-20
Figure 7-16: MW_2M front panel with two MIF-E cards .............................................. 7-21
Figure 7-17: BGW-O ODU block diagram.................................................................... 7-22
Figure 7-18: Antenna/ODU combination ...................................................................... 7-24
Figure 7-19: 1+0 configuration for unprotected tail sites.............................................. 7-25
Figure 7-20: 1+1 protection, remote mount installation ............................................... 7-26
Figure 7-21: 4+0 and 1+1 configuration in a busy hub site.......................................... 7-27
Figure 7-22: 2+0 East-West configuration with XPIC capacity .................................... 7-28
Figure 7-23: Microwave radio transmissions in line of sight ........................................ 7-30
Figure 7-24: ACM with eight step-down and recovery levels....................................... 7-32
Figure 7-25: Diverse routing for increased bandwidth utilization ................................. 7-35
Figure 8-1: Integrating a variety of DCN schemes ......................................................... 8-6
Figure 8-2: DCC to VC-12 Clear Channel conversion ................................................... 8-8
Figure 9-1: Typical SNCP-protected network sites ........................................................ 9-2
Figure 9-2: SNCP-protected BG sites ............................................................................ 9-3
Figure 9-3: MSP protection modes ................................................................................ 9-5
Figure 9-4: Two-fiber protection ..................................................................................... 9-7
Figure 9-5: Ethernet ring protection ............................................................................. 9-10
Figure 10-1: ECI Telecom's layered architecture management concept ..................... 10-2
Figure 10-2: LightSoft main window ............................................................................. 10-4
Figure 10-3: Platform view as displayed in the EMS-BGF......................................... 10-10
Figure 10-4: Platform view as displayed in the LCT-BGF.......................................... 10-11
In this chapter:
Overview ......................................................................................................... 1-1
Dual Matrix Approach ..................................................................................... 1-2
BroadGate Product Line .................................................................................. 1-4
BG's Unique Value Proposition....................................................................... 1-5
Carrier Class Ethernet and MPLS ................................................................... 1-6
Overview
Traffic over transport networks keeps growing with increasing dominance of
packet based traffic. Service providers are facing the challenge to decouple the
linear linkage between the growing capacity needs and the infrastructure cost
associated with supporting it, and turn it into revenues. Common approaches
offered by equipment vendors include use of WDM ROADM to cope with the
increased capacity and shift to packet based infrastructure in order to handle the
traffic in a more cost effective way. At the same time, service providers still
have to keep their revenues generating TDM based services and are afraid to
build a new packet based infrastructure that will take over their well proven
and trusted SDH/SONET based infrastructure.
The need for data processing and connectivity across the WAN/MAN is ever
growing. Enterprises with geographically distributed offices want to expand
their Ethernet-based LANs to connect remote branches to their headquarters,
and their business to the Internet. Internet Service Providers (ISPs) and other
Application Service Providers (ASPs), such as Storage Service Providers
(SSPs), require data connectivity to connect their Points of Presence (PoPs) and
reach their customers. Moreover, mobile operators’ demand for Ethernet
connectivity is on the rise, as they seek to exploit their massive presence in
metro areas to provide new services.
Being equipped with a TDM based matrix, MSPP used to deliver Ethernet
traffic over SDH/SONET (Ethernet over SDH). With the new dual matrix
approach capabilities, Ethernet traffic can not only be processed natively but
can also be delivered over Ethernet interfaces without passing through the
TDM matrix thus making it suitable to be part of a pure packet based
infrastructure.
The µMSPP can get Ethernet traffic either over SDH or natively over Ethernet
interfaces, process it in its native form using its pure packet based matrix and
deliver it over Ethernet interfaces to an overlay of packet based network.
With the new capabilities the MSPP is position to optimally support the full
cycle of migration from TDM-based to pure Ethernet-based backhaul networks,
as follows:
TDM-based Metro network: Supports a wide range of TDM services
from E1 up to STM-64 with full LO/HO non-blocking TDM matrix.
Supports all metro Ethernet services: E-Line, E-LAN, Rooted Multicast
with Ethernet over TDM (EoP, L1/L2 EoS, MPLSoEoSDH/SONET) with
interfaces from FE up to 10 GbE.
Packet based and TDM based Metro networks in parallel: Delivers a
wide range of TDM services from E1 up to STM-64 with full LO/HO non
blocking matrix. Supports all Metro Ethernet services: E-Line, E-LAN,
Rooted Multicast with pure L2 Ethernet/MPLS switching supporting
interfaces from FE up to 10 GBE.
µMSPPs have begun to play a critical role in transition from legacy to NGNs.
BG enables carriers to leverage their SDH installed base while offering an
increasing mix of services to their customers. Its powerful networking and
protection capability and high scalability improve the cost-effectiveness of the
metro-access layer and private networks that integrate service access and
transmission functions. It can also give timely responses to network evolution
requirements.
Ethernet-over-SDH advantages:
Ethernet with carrier class reliability, operation, and management
A wide variety of protection schemes
Ethernet traffic carried over existing SDH infrastructures, exploiting
resources, footprint, and operational efforts
Low-cost EPL services provided in a node at the edge of a network
MAN Ethernet solutions with powerful functions
Ethernet-over-PDH advantages:
Enables the deployment of advanced Ethernet services over a legacy
PDH infrastructure
In this chapter:
Overview ......................................................................................................... 2-1
Data Applications ............................................................................................ 2-2
Metro-Access Applications ............................................................................. 2-3
Cellular Applications ....................................................................................... 2-3
WiMAX Applications...................................................................................... 2-7
Utelcos ........................................................................................................... 2-10
Private Network Applications ....................................................................... 2-12
Efficient Triple-Play Service Delivery .......................................................... 2-13
Overview
BG is a flexible µMSPP that can be deployed in various applications. Its
powerful networking and protection capabilities and high expandability,
combined with its small footprint and economical cost, make it ideal for
metro-access and cellular networks. BG boosts service provisioning,
aggregation, and transport, making it an essential element in today’s networks.
Data Applications
Ethernet services have been the driving force in the telecommunications
industry in recent years, providing a new approach to data service provisioning
and connectivity. This has brought about exceptional growth in the demand for
more bandwidth at reduced cost.
BG’s Layer 1, Layer 2 and MPLS capabilities offer carriers a clear migration
path from pure TDM-based legacy services to new value-added data services.
With BG, carriers can now provide services such as Ethernet Private Lines
(EPL), with Ethernet over SDH (EoS) or Ethernet over PDH (EoP) replacing
traditional TDM leased-line services, Ethernet Virtual Private Lines (EVPL)
using shared bandwidth, and Ethernet Private LAN (EPLAN)/Ethernet Virtual
Private LAN (EVPLAN) extending corporate LANs over the WAN. All
services can be offered with QoS and SLA assurances, controlled and managed
by ECI Telecom’s multidimensional LightSoft® Network Management System
(NMS).
Metro-Access Applications
Metro-access networks are characterized by an increasing demand from
residential and business customers for higher bandwidth to support voice, data,
and video services.
Although BG is very small, it offers scalable STM-1/4/16/64 aggregation of
access traffic in multiring and point-to-point topologies. The platform
adds/drops PDH, SDH, and Fast Ethernet (FE) services at local PoPs.
Cellular Applications
As the cellular market continues to boom, it is essential for operators to deal
with constant increases in traffic, changes in connectivity demands affecting
network topologies, and migration to new technologies (GSM to GPRS to 3G).
All of these changes require scalable and flexible optical infrastructure
expansions down to the Remote Access Network (RAN).
BG is very suitable for building RAN transmission networks:
It is compact and resilient, making it perfectly suited for both indoor and
outdoor enclosures and harsh environmental conditions.
It consolidates data traffic with TDM traffic for a shared infrastructure.
It supports point-to-point, ring, and mesh topologies, and can be upgraded
from STM-1 to STM-64 with a minimal effect on traffic.
It is highly flexible and low cost, improving the network’s cost
effectiveness.
EoP Services
EoP is a quick and cost effective way to add Ethernet services over existing
PDH based networks. One example is businesses using PDH leased lines to
connect their offices. While data requirements of enterprises are constantly
growing, the existing infrastructure is still in place. EoP supports data services
requirements such as E-Line and E-LAN over existing infrastructure, without
the hassle associated with supporting these attributes over a packet based
network. Adding Ethernet based services over the same infrastructure only
requires EoP support at the CLE or CPE equipment used to support the leased
lines network.
However, the primary application today for EoP is mobile backhauling. While
the shift to 3G IP is already in motion, projections indicate that even in the next
few years, 70% to 80% of the world’s cell site will be served exclusively by
TDM backhaul infrastructure, with the majority being radio PDH.
Supporting EoP lets service providers preserve the same transport network to
backhaul TDM, ATM, and Ethernet based data and voice traffic without a new
network overlay or replacing existing equipment. All additional functionality is
implemented only at the edge of the network and Ethernet is then carried
transparently over the existing TDM-based network.
With the addition of 64 Kbps switching and grooming capabilities and Ethernet
L2 concentration capabilities, several levels of concentration can be obtained.
Pushed as close as possible to the edge of the network, optimized bandwidth
utilization and substantial infrastructure cost savings are achieved, as follows:
Supporting Ethernet L2 concentration at the first aggregation point allows
several Ethernet links to be groomed and carried over the same PDH links.
Further statistical multiplexing provides bandwidth saving proportional to
the oversubscription ratio.
64 Kbps switching support and aggregation capabilities at the first
aggregation point allow all traffic types including TDM, 3G ATM, and 3G
IP to be aggregated and groomed over the same PDH links towards the hub
points.
Substantial additional savings is achieved at the hub points via TDM and
Ethernet L2 aggregation and concentration, similar to that performed at the
first aggregation point, but combining traffic from additional sites arriving
over partially populated PDH links. Traffic from the hub sites is then
carried over PDH/SDH or Ethernet links towards the metro network.
WiMAX Applications
WiMAX - Worldwide Interoperability Microwave Access, is an emerging
wireless technology that provides high-throughput broadband connectivity over
long distances.
In recent years, WiMAX has clearly become the leading technology among
wireless technologies and this trend is expected to continue. WiMAX offers the
capacity for service providers to deploy next generation broadband service
more cost effectively than today, to a wider customer base, while adding a
mobility aspect to those services.
ECI Telecom offers a wide range of solutions for all WiMAX deployments
scenarios, tailored to suit individual customer specifications. While focusing on
rapid rollout of WiMAX services ECI's offerings are fully scalable, supporting
both present and future needs.
Ethernet over SDH (EoSDH) is a cost-effective and shortest-time-to-market
method of providing WiMAX services on an existing installed SDH/SONET
network using NG-MSPP .It benefits from the price points of Ethernet with the
large geographic coverage of an existing network. This is efficiently
implemented by connecting a WiMAX access device to BroadGate (BG)
Ethernet cards in the access network. The powerful networking and protection
capabilities of the BG and its high expandability, combined with its small
footprint, economical cost, and efficient Ethernet/MPLS capabilities, make it
ideal for metro-access and WiMAX backhauling.
Another variation of Ethernet over TDM is Ethernet over PDH (EoPDH)
delivery, via the transparently connected WiMAX BTS over bonded E1 lines.
This method is usually for low bandwidth applications up to several E1s and
connect areas that are inaccessible by fiber, or have existing Radio PDH that
backhauls a collocated 2G/2.5G BTS. This scheme is made possible by the
EoPDH cards on the BroadGate platform.
Typical WiMAX applications include:
Fixed Broadband Access - WiMAX technology is an easy and fast
alternative for broadband access deployment, allowing fixed-line operators
to expand broadband coverage into areas where wireline infrastructure does
not exist or is unable to provide broadband services. ECI's WiMAX
solution allows mobile operators to supplement their service offering with
fixed-line triple play services.
Mobile Broadband Access - ECI's WiMAX solution can be used to
expand existing 2G/3G mobile operator networks in greenfield areas or as
the RAN for MVNO services. The deployment of a WiMAX network with
stationary applications and allowances for future requirements (supporting
mobility) is becoming increasingly popular.
WiMAX for Rural Areas - In rural areas, where broadband services has
until now been limited or even impossible, WiMAX makes high-speed
access a reality. It eliminates the need to run fiber across rough terrain, or
low-dense populated areas. WiMAX base stations can be built to service
the local area wireless, creating a new revenue source with considerably
lower investment.
Utelcos
In recent years, Utelcos have been installing more metering and monitoring
devices to improve their network visibility. This enables them to support
features like real-time control, computer networking, safe drinking water
monitoring, security access, and video for facilities monitoring. To facilitate
these added services, utilities are using fibers along their right of ways to meet
additional bandwidth demand, as well as upgrading their surveillance network
to support new Ethernet and IP-based communications.
Utelcos have recognized that their networks can be leveraged to provide
commercial telephony services. Many are therefore offering wholesale carrier
and enterprise services, as well as providing high-speed Internet and telephony
services to the residential market.
These new trends present a major challenge to utility network planners. The
optical transmission layer, a key part of the network, must be carefully
designed to support current services and be future-ready for new ones. Network
planners must select transmission equipment that will support evolving utility
needs over the next several years in a very dynamic environment. Failure to
plan properly puts utilities in the dangerous position of having to constantly
redesign their network and replace transmission equipment to respond
effectively to their customer service requirements.
Figure 2-7: ECI full solution for the utility telecom network
In this chapter:
Overview ......................................................................................................... 3-1
Modular Architecture ...................................................................................... 3-2
Control Subsystem........................................................................................... 3-3
Communication with External Equipment and Management .......................... 3-5
Timing ............................................................................................................. 3-5
Traffic and Cross-Connect Functionality ........................................................ 3-6
TDM Configuration Options ........................................................................... 3-7
Power Feed Subsystem .................................................................................... 3-9
Engineering Orderwire .................................................................................. 3-10
Overview
As a powerful µMSPP for access networks, BG can deliver a variety of
services. Designed for installation in Customer Premises Equipment/Customer
Located Equipment (CPE/CLE) and Central Offices (COs), BG integrates
Ethernet with SDH and PDH capabilities into a 1U (44 mm) unit, and for
expanded traffic capabilities, a 2U (88mm) unit can be coupled with the
standard BG unit.
BG eliminates the boundaries between data and voice communication
environments, and paves the way for service provisioning without sacrificing
equipment reliability, robustness, and QoS. Thus, both operators and service
providers benefit from the best of both worlds: the cost-effectiveness and
universality of Ethernet and QoS, and the scalability and survivability of SDH.
Modular Architecture
The BG product line is a miniature add/drop multiplexer optimized especially
for metro-access, access, and cellular networks.
With the BG build-as-you-grow strategy, network operators are able to provide
new services as needed, expanding traffic capacity with minimum investment.
The platform’s architecture allows expansion according to market demand,
including:
Adding or replacing plug-in modules while the system is in operation,
without affecting traffic in any way.
Optimizing aggregate matrix capacity and transceiver module assignment.
Three types of unified matrix/aggregate cards are available, each
supporting a different bitrate, from STM-1 through STM-4 to STM-16, and
STM-64.
Optimizing tributary I/O slot assignment. Three slots in the basic unit and
three additional slots in the expansion unit can accommodate different I/O
modules of different fan-out and technology types.
In-service scalability of SDH links. An optical connection operating at a
specific bitrate can be upgraded from STM-1 through STM-4 to STM-16,
and STM-64.
Control Subsystem
A single main controller card in the BG shelf controls the entire BG system via
a high-performance CPU, which also processes communication with the
EMS-BGF/LCT-BGF and other equipment. A large capacity flash memory
stores equipment configuration data and software versions (up to two). Both
online and remote software upgrades are supported. BG supports the
processing of RS DCC channels and MS DCC channels, plus up to two Clear
Channels (DCC over framed or unframed E1). The BG unit can send network
management information through third-party SDH or PDH networks using
these Clear Channels.
The BG main controller card is the most essential card of the system, creating
virtually a complete standalone MSPP system. Moreover, it accommodates one
service traffic slot for flexible configuration of virtually any type of PDH,
SDH, or Ethernet interfaces. This integrated flexible design ensures a very
compact equipment structure and reduces costs, making BG an ideal MSPP for
the access layer.
BG control and communication functions include:
Internal control and processing
Communication with external equipment and management
Network element (NE) software and configuration backup
Built-in Test (BIT)
Timing
BG provides high-quality system timing to all traffic modules and functions in
compliance with applicable ITU-T recommendations for functionality and
performance.
The main component in the BG synchronization subsystem is the timing and
synchronization unit (TMU). Timing is distributed redundantly from the TMUs
to all traffic and matrix cards, minimizing unit types and reducing operation
and maintenance costs.
The TMU and the internal and external timing paths are fully redundant. The
high-level distributed BIT mechanism ensures top performance and availability
of the synchronization subsystem. In case of hardware failure, the redundant
synchronization subsystem takes over the timing control with no traffic
disruption.
To support reliable timing, BG provides multiple synchronization reference
options. Up to four timing references can be monitored simultaneously.
In BG, any timing signal can be selected as a reference source. The TMU
provides direct control over the source selection (received from the system
software) and the frequency control loop. The definition of the synchronization
source depends on the source quality and synchronization mode of the network
timing topology (set by the EMS-BGF or LCT-BGF).
Synchronization references are classified at any given time according to a
predefined priority and prevailing signal quality. The BG synchronization
subsystem synchronizes to the best available timing source using the
Synchronization Status Marker (SSM) protocol. The TMU is frequency-locked
to this source, providing internal system and SDH line transmission timing.
The shelf is synchronized to this central timing source.
Engineering Orderwire
The Engineering Orderwire (BG-OW) provides 64 Kbps voice communication
channels between NEs through E1, E2, or F1 bytes in the STM-n interface
overhead, or via clear channels (in Framed E1 mode) provisioned between
NEs.
The BG-OW facility is based on a telephone “party line” concept, where all
connected parties, typically technicians, can participate in concurrent voice
based service calls. As such, it enables one or more technicians to make calls
simultaneously using dedicated orderwire (OW) channels rather than regular
SDH lines.
OW lines are normally used between a remote site and a central office during
initial installation of the system, or when no telephone line is available. All
calls are bidirectional.
The interface between the BG-OW and the BG shelf is based on a framed E1
interface. A special cable connects between the host BG unit and the BG-OW
unit providing the E1 connection. The framed E1 carries various information
from/to the BG-OW unit.
The OW module consists of an integrated Dual Tone MultiFrequency (DTMF)
handset, cable connections, and configuration interfaces. No other ancillary
equipment is required.
In this chapter:
Overview ......................................................................................................... 4-1
BG-20 .............................................................................................................. 4-2
BG-30 .............................................................................................................. 4-9
BG-64 ............................................................................................................ 4-14
Overview
This chapter describes each platform in the BG family. BG platforms are
organized into three groups – the BG-20, a miniature optical service access
platform, the BG-30, a scaleable optical service access platform, and the BG-64
supper compact cost-effective broad range optical service access platform.
BG shelves have been designed to facilitate simple installation and easy
maintenance. Hot insertion of cards and modules is allowed to support quick
maintenance and repair activities without affecting traffic. The cage design and
mechanical practice of all platforms conform to international mechanical
standards and specifications.
BG-20
The BG-20 is a miniature, low-cost, flexible ADM1/4 MSPP for access
networks, offered as part of the overall ECI Telecom solution.
The BG-20 platform includes two parts: BG-20B and BG-20E. BG-20B is the
base unit and can be deployed independently; BG-20E is the expansion unit
which can be added on top of BG-20B to provide more services and interfaces.
BG-20C Overview
BG-20C is a miniature, cost-effective demarcation platform; it is a small
TM/ADM-1/4 containing E1s and Ethernet L2 with MPLS capability.
The BG-20C shelf is housed in a 224 mm deep, 223.5 mm wide, and 44 mm
high equipment cage with all interfaces accessible from the front of the unit.
The shelf consists of a single MXC-20C card. The BG-20C can be installed in
2,200 mm or 2,600 mm ETSI racks or in 19" racks.
The BG-20C is available in two flavors according to the power supply:
BG-20C_DC - operates from -48 VDC power feed, provides two
connectors for external power line connection, and supports dual power
feed for redundancy.
BG-20C_AC - is fed from a 90-240 VAC power source, supports external
power line connection through a special power connector.
The BG-20C is a single board system, all traffic interfaces are housed on the
MXC-20C card and are identical on both BG-20C options, including:
21 x E1 1, 120 Ω
4 x 10/100BaseT interfaces
2 x STM-1/4 interfaces, SFP based.
BG-20B Overview
The BG-20B platform is housed in a 243 mm deep, 440 mm wide, and 44 mm
high equipment cage with all interfaces accessible from the front of the unit.
The platform consists of a matrix card, a power feed module, one traffic
daughter slot, and one traffic connector connecting the BG-20B and the
BG-20E or BGW-20E. The BG-20 can be installed in 2,200 mm or 2,600 mm
ETSI racks or in 19” racks.
1
MXC-20C can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external DDF with
balanced-to-unbalanced conversion should be used.
Either 220 VAC or -48 VDC power feeds can be selected. The -48 VDC power
feed supports a dual-channel power supply. BG-20B has one slot that is used
for configuring the power input module. Two types can be configured:
INF_20B, used in -48 VDC power feed, provides two D-type connectors
for external power line connection and supports dual power feed.
AC_CONV-20B, used in 90-240 VAC power feed to implement AC/DC
conversion, supports external power line connection through a special
power connector.
The BG-20B has one traffic slot that can be configured with the following
traffic modules:
SMD1H: dual-port STM-1 supporting optical or electrical STM-1
interfaces by installing the appropriate SFPs; supports hot swapping.
OMS4H: single-port STM-4 supporting optical SFP modules with LC
connectors; supports hot swapping.
ME1_42H: 42-port balanced 120 Ω E1; supports hot swapping.
ME1_21H: 21-port balanced 120 Ω E1; supports hot swapping.
M345_3: Triple E3/DS-3. Each interface can be configured separately to
E3 or DS-3.
MEoP_4H: 4-port EoP module with total WAN bandwidth of 32 x E1 and
Layer 2 functionality. Each Ethernet port supports a 10/100BaseT
interface; supports hot swapping.
MGE_1_L1: EoS module with one GbE combo port with total WAN
bandwidth of 4 x VC-4 and Layer 1 functionality; interface is copper and
optical selectable. 1000BaseT through an RJ-45 connector,
1000BaseSX/LX/ZX through SFP module.
ME_2G_4F: Layer 2/MPLS module supporting MPLS feature overlay
with two GbE combo ports, two FE ports, and two FX ports. The GbE ports
are configurable electrical (RJ45) or optical (SFP). The module supports
64 EoS/MoT ports with total WAN bandwidth of 4 x VC-4.
The following table lists the modules that can be configured in each slot of the
BG-20B.
Name Description MS DS PS
BG-20B_L1 Cross-connect, timing control, √
21 x E1/T1, 6 x FE L1, and
2 x STM-1/STM-4 interface card
BG-20B_L2M Cross-connect, timing control, √
21 x E1/T1, 6 x FE L2 with MPLS
capability, and 2 x STM-1/STM-4
interface card
SMD1H 2 x STM-1o/e module √
OMS4H 1 x STM-4 module √
ME1_42H 42 x E1/T1 module, 120 Ω √
ME1_21H 21 x E1/T1 module, 120 Ω √
M345_3 3 x E3/DS-3 module √
MEoP_4H 4 x EoP module with total WAN √
bandwidth of 32 x E1/T1 and L2
functionality
MGE_1_L1 1 x combo GbE module with total √
WAN bandwidth of 4 x VC-4 and
L1 functionality
ME_2G_4F 2 x combo GbE, 2 x FE, and √
2 x FX module with total WAN
bandwidth of 4 x VC-4 with L2
and MPLS functionality
INF_20B Power filter unit (-48 VDC) √
AC_CONV-20B Power conversion unit (220 VAC) √
BG-30E Overview
The BG-30E shelf is housed in a 243 mm deep, 443.4 mm wide, and 88.9 mm
high equipment cage with all interfaces accessible from the front. The shelf
consists of three expansion cards, redundant power feed modules, and an
extractable fan module. All cards in the BG-30E are connected using a
backplane that supports one traffic connector for the connection between the
BG-30E and the BG-30B or BG-64.
The BG-30E houses three traffic expansion slots supporting different types of
PDH, SDH, data, and PCM interface expansion cards.
Either 220 VAC or -48 VDC power feeds can be selected. BG-30E has one slot
that is used for configuring the power input module. Two types can be
configured: INF_30E and AC_CONV-30E:
INF_30E, used for -48 VDC power feed, provides two D-type connectors
for external power line connection, and supports dual power feed.
AC_CONV-30E is used for 220 VAC power feed to implement AC/DC
conversion. It supports external power line connection through a special
power connector.
BG-20E Overview
The BG-20E shelf is housed in a 243 mm deep, 440 mm wide, and 88.9 mm
high equipment cage with all interfaces accessible from the front. The shelf
consists of three expansion cards, a power feed module, and one Mini
Backplane for the connection between the BG-20B and the BG-20E. A
BG-20E shelf is an extension or slave unit of BG-20 and should always be
connected to a BG-20B shelf.
The BG-20E houses three traffic expansion slots supporting different types of
PDH, SDH, Data, or PCM interface expansion cards.
The fan unit, used to cool the system, is located on the right side of the shelf.
The fan control system is on the MXC20.
Either 220 VAC or -48 VDC power feeds can be selected. BG-20E has one slot
that is used for configuring the power input module. Two types can be
configured: INF_20E and AC_CONV-20E:
INF_20E, used for -48 VDC power feed, provides two D-type connectors
for external power line connection, and supports dual power feed.
AC_CONV-20E is used for 220 VAC power feed to implement AC/DC
conversion. It supports external power line connection through a special
power connector.
2
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
BG-30
The BG-30 is a miniature, low-cost, flexible redundant multi ADM1/4/16
µMSPP for access networks, offered as part of the overall ECI Telecom
solution.
BG-30B Overview
The BG-30B platform is housed in a 243 mm deep, 440 mm wide, and 44.4
mm high equipment cage with all interfaces accessible from the front of the
unit.
The following table lists the modules that can be configured in each slot in the
BG-30B.
3
Module is supported in slots TS2 and TS3 only.
4
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
5
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
BG-30E Overview
The BG-30E shelf is housed in a 243 mm deep, 443.4 mm wide, and 88.9 mm
high equipment cage with all interfaces accessible from the front. The shelf
consists of three expansion cards, redundant power feed modules, and an
extractable fan module. All cards in the BG-30E are connected using a
backplane that supports one traffic connector for the connection between the
BG-30E and the BG-30B or BG-64.
The BG-30E houses three traffic expansion slots supporting different types of
PDH, SDH, data, and PCM interface expansion cards.
Either 220 VAC or -48 VDC power feeds can be selected. BG-30E has one slot
that is used for configuring the power input module. Two types can be
configured: INF_30E and AC_CONV-30E:
INF_30E, used for -48 VDC power feed, provides two D-type connectors
for external power line connection, and supports dual power feed.
AC_CONV-30E is used for 220 VAC power feed to implement AC/DC
conversion. It supports external power line connection through a special
power connector.
6
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
7
Supported only for BG-30E installed on BG-30B.
8
Supported only for BG-30E installed on BG-30B.
BG-64
The BG-64 is a miniature, low-cost, flexible redundant ADM-64/MADM-16
MSPP for access networks, offered as part of the overall ECI Telecom solution.
It supports interoperability with the XDM Product Line and BG Product Line
in all aspects, including SDH, PDH, data, DCC, management, and other
net-wide functions.
BG-64 Overview
The BG-64 platform is housed in a 243 mm deep, 442.4 mm wide, and 88
.9mm high equipment cage with all interfaces accessible from the front of the
unit.
The BG-64 subrack can be expanded via an expansion unit, the BG-30E (the
same used to expand the BG-30B). The BG-30E contains two power supplies, a
fan unit, and three tributary slots. For a detailed description of the BG-30E, see
BG-30E Overview (on page 4-6) in the BroadGate General Description.
The following table lists the modules that can be configured in each slot in the
BG-64.
9
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
10
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
11
This is a double-slot module and can be installed only in slot pairs TS1+TS2 and TS6+TS7 of the XDM-300.
12
This is a double-slot module and can be installed only in slot pairs TS1+TS2 and TS6+TS7 of the XDM-300.
13
This module/card can provide only balanced E1 interfaces directly. For unbalanced E1 interfaces, an external
DDF with balanced-to-unbalanced conversion should be used.
14
Supported only for BG-30E installed on BG-30B.
15
Supported only for BG-30E installed on BG-30B.
In this chapter:
Overview ......................................................................................................... 5-2
Carrier Ethernet Data Value Proposition ......................................................... 5-3
What is MPLS?................................................................................................ 5-4
What is MPLS-TP?.......................................................................................... 5-6
Carrier Ethernet with MPLS Technology ........................................................ 5-9
Hierarchical VPLS for Scalability ................................................................. 5-10
E2E MPLS Service over IP/MPLS Core ....................................................... 5-12
Quality of Service .......................................................................................... 5-13
Traffic Management and Performance .......................................................... 5-13
Selective FDB Flush ...................................................................................... 5-16
E-Tree (Rooted-Multipoint) Service.............................................................. 5-17
BroadGate Product Line Ethernet Cards ....................................................... 5-21
Applications and MEF Services .................................................................... 5-25
Circuit Emulation Services (CES) ................................................................. 5-31
Timing and Synchronaization ........................................................................ 5-33
Network Connectivity Fault Management..................................................... 5-34
Access Control List ....................................................................................... 5-37
Port Mirroring ................................................................................................ 5-38
User Benefits with MPLS Enabled Cards ..................................................... 5-38
Unique Value Proposition ............................................................................. 5-39
Overview
The volume and patterns of telecommunication traffic are constantly changing.
Volume is growing exponentially, with most of the expansion driven by new
data services for businesses together with new residential triple play services
(voice, video, and HSI) offered by both fixed and mobile SPs. The data
services in greatest demand include:
Business Applications: Enterprises need increasing bandwidth to support
new applications like VoIP, video conferencing, instant messaging, file
sharing, and very high speed connections to the Internet and between
geographically dispersed branches. ISPs and other Application Service
Providers (ASPs), such as Storage Service Providers, require data
connectivity to connect their POPs and reach their customers.
Residential Triple Play: Always on the lookout for new revenues while
trying to keep their positioning competitive, SPs are extending their
business model to offer triple play service bundles including voice, HSI,
and video (IPTV and VoD). While downlink is still the dominant channel,
more and more bandwidth is also required for uplink to support
peer-to-peer applications.
Mobile: Data traffic growth in mobile networks is driven by several
factors. Mobile Internet is gaining momentum, as well as new multimedia
applications like mobile TV, gaming, and Multimedia Messaging Service
(MMS). The shift to 3G-based IP infrastructures for delivering more
bandwidth at a lower cost per bit is another factor. In addition, mobile
operators are expanding into new businesses, exploiting their massive
presence in metro areas to provide business services and to lease bandwidth
(Carrier of Carrier CoC service).
To meet these evolving demands, telecommunications is moving from voice
PSTN to VoIP, from TDM leased lines to Ethernet VPNs, from TDM-based 2G
and 2.5G mobile networks to 3G/4G data networks and from simple BE HSI
access to advanced triple play networks for SMB, enterprise, and home use.
Today's challenge is to build an infrastructure that maximizes bandwidth
capacity while minimizing costs. Operators must provide a carrier class
standard of service with more bandwidth at less cost per bit, and still get a
satisfactory ROI.
This is where Ethernet/MPLS solutions come into play. ECI Telecom's MSPP
platforms provide a cost-effective way to provide carrier class Ethernet-based
services supporting scalability, reliability, and the strict QoS requirements
dictated by modern communication applications.
What is MPLS?
MultiProtocol Label Switching (MPLS) is a mechanism for transporting data
using a connection-oriented approach. Standardized by the IETF, MPLS is a
scalable protocol-agnostic mechanism designed to carry both circuit and packet
traffic over virtual circuits known as LSPs. MPLS fits into the category of
packet-switched networks, falling in between the traditional OSI definitions of
the Data Link Layer (Layer 2) and the Network Layer (Layer 3). MPLS makes
packet-forwarding decisions based on the contents of the label without
examining the packet itself.
MPLS provides a unified data-carrying service for circuit-like packet-switching
client data. MPLS can be used to carry many different kinds of traffic,
including IP packets, native ATM, and Ethernet frames. MPLS has gradually
been replacing traditional transport technologies, such as frame relay and
ATM, mostly because it is better aligned with current and future technology
needs.
Many network operators now deploy MPLS networks in response to the
massive continued growth of data traffic, the demand for complete service
offerings, and the development of network convergence strategies. Ethernet
interfaces and Ethernet/MPLS services are the main toolbox supporting the
MPLS network operator's strategic goals.
MPLS addresses the needs of metro area SPs with a cost-effective solution that
supports all services with carrier class capabilities. MPLS addresses all key
attributes defined by MEF for carrier Ethernet:
Hard QoS, assuring service delivery with the right quality. MPLS is
connection-oriented, with intelligent traffic engineering (TE) and CAC, for
true E2E differentiated service for multiple CoS.
Reliability, with <50 msec FRR for failed nodes or links.
Scalability, for both number of elements and services, with one 20-bit
MPLS tag supporting 1 M service roots.
Smooth E2E service management, with ITU-T Y.1711 and IEEE 802.1ag
allowing verification of tunnel status.
MEF services are supported, including E-Line, E-LAN, and E-Tree.
Legacy services such as ATM, Frame Relay, and TDM are all supported.
What is MPLS-TP?
MPLS Transport Profile (MPLS-TP) is an MPLS profile currently being
defined under the auspices of the IETF and ITU-T. The emerging MPLS-TP
standard aims to define a feature list most relevant for transport networks and
to support packet transport services with a degree of predictability similar to
that found in existing transport networks.
MPLS-TP is a connection-oriented packet-switched (CO-PS) application for
Layer 2 transport network technology that incorporates elements of both MPLS
and PW architectures, such as the MPLS forwarding paradigm and PW
Emulation Edge to Edge (PWE3) client mapping. MPLS-TP is based on the
same architectural principles of layered networking used in transport network
technologies like SDH, SONET, and OTN.
The MPLS-TP design is a natural extension of work begun by ITU-T (SG15),
in a process similar to the development of T-MPLS. In February 2008 the
ITU-T and IETF agreed to work jointly on the MPLS-TP design. Specifications
will be defined in a number of RFCs. Many SPs are now requiring an
infrastructure that will also be capable of supporting MPLS-TP.
MPLS-TP is initially planned as a low-cost Layer 2 technology that provides
QoS, E2E OAM, and protection switching. Features not relevant to CO-PS
applications are removed, including:
Connectionless models
IP in data plane
Penultimate Hop Popping (PHP) for E2E OAM
Additional mechanisms supporting critical transport functionality are added,
including supplemental OAM, resiliency, bidirectional LSPs, new protection
schemes, and control/management features that enable maximum synergy with
existing optical transport network operations and management paradigms.
Essential features of MPLS-TP include:
Based on strict CO-PS network technology.
Operates independently of clients and associated control networks, enabling
network operators to maintain a clear separation between their own robust
packet transport network designs and the services and means used to carry
customer traffic.
May support a wide range of client layer networks and server layer
networks, including OTH, SDH, PDH, and ETH.
Robust OAM capabilities and resilience mechanisms without reliance upon
use of a control plane.
Connection management via management or control plane.
Common management and control of multilayer packet and optical
transport networks.
MPLS-TP uses the MPLS header with standard label swapping and stacking
and PWE3 mapping, supporting P2P, P2MP, and MP2MP connections that
match the ones already defined for MPLS and H-VPLS architectures.
MPLS-TP also supports bidirectional P2P connections (bidirectional LSPs) by
matching forward and backward connections along the same path. MPLS-TP
does not use MP2MP LSPs, Electronic Commerce Messaging Protocol
(ECMP), or PHP.
MPLS-TP QoS mechanisms are the same as those of MPLS-Traffic
Engineering (TE). MPLS-TP applies QoS on a per-connection basis. When
working with hierarchical LSPs, QoS is managed independently at each level.
The MPLS-TP protocol enables more affordable E2E MPLS deployments by
streamlining operations models and consolidating/simplifying network
topologies. For example, one of the key elements is eliminating the cost of
control plane functionality being distributed and integrated into each node
across an MPLS-based network and replacing it with a more affordable
transport-oriented static configuration through a transport-grade NMS. This
helps operators reduce their OPEX significantly and get networks ready to
offer real convergence of NG services.
With H-VPLS, the network is split into multiple VPLS domains. Spoke nodes
are connected only to their hubs, and full mesh is only created between hub
nodes. Traffic may be routed between tunnels of different VPLS domains. This
efficient approach improves MP2MP service scaling and allows less powerful
devices such as access switches to be used as spoke nodes, since it removes the
burden of unnecessary connections.
BroadGate Product Line platforms support static H-VPLS over MoT and MoE
interfaces, based on IETF standard RFC 4762. BroadGate Product Line
platforms also support an enhanced H-VPLS feature enabling definitions of
multiple SHGs with traffic switching between these groups.
The BroadGate Product Line H-VPLS implementation supports both two-tier
H-VPLS (hub and spoke) and multidomain H-VPLS. The following figure
illustrates an example of a network where the MCS gateway supports multiple
H-VPLS domains. Within each domain, member nodes are connected in a full
mesh VPLS. Each domain is connected to other NEs using H-VPLS. Multiple
domains are connected through each MCS gateway card.
Quality of Service
The TM supports the following QoS mechanisms:
Eight CoS levels per port used for service differentiation, maximizing SLA
diversity and optimizing packet handling throughout the network.
Queuing, with 128 K queues per MCS, for true E2E bandwidth guarantees
per MPLS tunnel.
WRED mechanism for TCP-friendly congestion management.
Shaping that provides rate limiting and burst smoothing.
Weighted Fair Queuing (WFQ) scheduling mechanism, ensuring that
bandwidth is distributed fairly between individual queues.
E-Tree (Rooted-Multipoint)
Service
E-Tree service provides Ethernet P2MP multicast tree connectivity, enabling
very efficient bandwidth use for broadcast TV or IPTV as well as E-Learning
applications using, for example, multicast/broadcast packet video. With this
approach, a single packet copy can be sent to all endpoints (leaves) that share a
single tree branch. Ethernet Private Tree (EP-Tree) services use dedicated
bandwidth with a single root and multiple leaves. Ethernet Virtual Private
Tree (EVP-Tree) services use shared bandwidth with rooted-multipoint
connectivity across a shared infrastructure.
The DMGE_2_L2, DMGE_4_L2, DMGE_8_L2, and DMXE_28_L2 cards
support both EP-Tree and EVP-Tree services for IPTV/BTV and E-Learning
capabilities.
Star VPLS topology to carry the VoIP, VoD, and HSI P2P services. The
star VPLS is built over the aggregation network from the root PE
(aggregator) device that connects to the edge router/BRAS to the leaf PE to
the IPDSLAM. This star VPLS also carries the bidirectional IPTV control
traffic that is either sent by the router downstream (IGMP query) or sent by
the subscriber set-top-box (STB) upstream (IGMP join/leave requests).
E2E interoperability with the DSLAM and MSER, through either the
Ethernet or the MPLS layer. The P2MP multicast tree continues from the
PIM-SM multicast tree over the core network.
A P2MP tunnel originates at the source PE and terminates at multiple
destination PEs. This tunnel has a tree-and-branch structure, where packet
replication occurs at branching points along the tree. This scheme achieves
high multicast efficiency since only one copy of each packet ever traverses an
MPLS P2MP tunnel. A MPLS service card can act as both a transit P and as a
destination PE within the same P2MP tunnel, in which case it may be called a
Transit PE (not Transit P).
The following figure illustrates a P2MP multicast tree with PE1 as the source
PE (root), P1 as a transit P, PE2 as a transit PE (leaf PE), and PE3, PE4, and
PE5 as the destination or leaf PEs. The link from PE1 to P1 is shared by all
transit and destination leaf PEs; therefore the data plane sends only one packet
copy on that link.
Figure 5-14: P2MP multicast tunnel example - physical and logical networks
The P2MP tunnels carry multicast content such as IPTV content in a triple play
network, but P2MP tunnels are not enough. Two other functionalities complete
the triple play solution:
Star VPLS
IGMP Snooping
The full triple play solution, incorporating P2MP multicast tunnels, star VPLS,
and IGMP snooping, is illustrated in the following figure. The P2MP multicast
tunnels carry IPTV content in an efficient drop&continue manner from the TV
channel source, headend router, and MultiService Edge Router (MSER),
through the root PE (PE1) to all endpoint leaf PEs. The VPLS star carries all
other P2P triple play services such as VoIP, VoD, and HSI. The VPLS star also
carries the IGMP messages both upstream (request/leave messages from the
customer) and downstream (query messages from the router). IGMP snooping
is performed at the endpoint leaf PEs to deliver only the IPTV channels
requested by the user. This allows scalability in the number of channels, as well
as freeing up bandwidth for other triple play services such VoD, VoIP, and
HSI.
Figure 5-15: Triple play network solution for IPTV, VoD, VoIP, and HSI services
Customers can provision multiple services on any single port, for example:
EVPL services
E-LAN with various QoS options
ISP connectivity services
Business connectivity services
The Layer 2 cards in each BroadGate in the network are connected to each
other via Network to Network Interface (NNI) EoS ports. These NNI ports can
serve either for dedicated traffic for specific customers or as a shared core for
multiple customers.
The Transit P provider devices simply swap the MPLS labels from the source
port to the destination port. The Destination PE terminates the tunnel and
identifies the packet VPN based on the VC label. The Destination PE then
looks up the MAC DA of the packet to find the destination Ethernet port,
removes (pops) the two MPLS labels, and forwards the packet to the Customer
Equipment (CE) port(s).
The BroadGate's Ethernet Layer 1 card set provides the following functional
features and benefits:
Adaptive rate control for each connection - from 2 Mbps to the full GbE
in appropriate increments (VC-12/3/4).
Virtual Concatenation (VCAT) - for variable bandwidth piping down to 2
Mbps, with the capability of capacity distribution across multiple fibers and
optical carriers, guaranteeing data transfer over any SDH infrastructure and
meeting the ITU-T G.707 standard.
Link Capacity Adjustment Scheme (LCAS) mechanism - for in-service
variation of pipe bandwidth and optional reuse of protection bandwidth.
The capacity of the Ethernet link automatically decreases if one or more
VCs fail, and automatically increases when the network fault is repaired,
meeting the ITU-T G.7042 standard.
Generic Framing Protocol (GFP) - for industry-standard mappings
meeting the ITU-T G.7041 standard.
Multitasking card sets - the same cards can be used for multiple levels of
service:
GbE and FE are supported within the same card.
VC-12/3/4 rates are supported within the same card.
Network protection - SDH and/or WDM protection mechanisms,
including SNCP and MS-SPRing, are applied to each connection.
Easy connectivity - point-and-click, E2E, real time, P2P, as in any SDH
trail.
Full interoperability between all Ethernet cards - including the
BroadGate MPLS cards and the XDM platforms, as well as seamless
interfacing with external third-party hardware.
Seamless integration and complete backward compatibility with the entire
product line.
Sites that belong to the same MPLS VPN expect their traffic to be forwarded to
the proper location. This is accomplished through the following means:
Establishing a full mesh of MPLS label switched paths (LSPs) or tunnels
between the PE sites.
MAC address learning on a per-site basis at the PE devices.
MPLS tunneling of customer Ethernet traffic over pseudowires (VPN)
while it is forwarded across the provider network.
Packet replication across MPLS tunnels at the PE devices, for
multicast/broadcast-type traffic and for flooding unknown unicast traffic.
Ethernet-based MP2MP
BroadGate platforms provide Ethernet LAN (E-LAN) services over SDH at
minimum cost and maximum efficiency. By integrating SDH and Ethernet
layers, the BroadGate achieves enhanced reliability and protection. This
solution provides an ideal multiservice platform, enabling ISP connectivity
with a mixture of full-mesh connectivity and dedicated services by using the
same cards and ports.
The BroadGate Layer 2 and MPLS cards provide the following features and
benefits:
High performance, wire speed Layer 2 switching for metro-access and
access networks in ring, multi-ring, star, and mesh topologies.
Provider Bridge capabilities (802.1ad), with double tagging, QinQ-based
switching for P2P, P2MP, and MP2MP connections - fully transparent and
secure Ethernet service over the provider's EoS network.
Up to eight QoS levels assigned per port, VLAN, or client CoS,
maximizing SLA diversity and optimizing packet handling throughout the
network.
High granularity policing and priority marking (802.1p) per SLA,
enabling the provider to control the amount of bandwidth for each
individual user and service. Two-rate three-color policing enhances the
service offering, combining high priority service with best effort traffic for
the same user.
Congestion avoidance mechanism based on user-configurable WRED.
Drops low priority packets first, preventing the network from reaching the
point where congestion increases the higher priority packet loss rate.
Remote Network Monitoring RMON-based PM.
Security capability per customer VPN.
Low cost per port achieved with statistical service multiplexing, offering
high density of 10/100/1000BaseT electrical interfaces per slot and Small
Form Factor Pluggable-based (SFP) optical FE/GbE ports.
Software upgrade to full MPLS support with the MPLS card set for
network scalability and TE in VPLS core networks.
The Ethernet Layer 2 and MPLS service cards also use multiple EoS ports to
connect the cards over SDH interfaces. EoS capabilities include:
Standard-based GFP and VCAT, meeting the ITU-T G.707 standard, for
interoperability with the BroadGate Layer 1 card set, XDM-100 and
XDM-1000 Product Line data cards, and third-party equipment. This
results in an E2E solution that integrates Layer 1 services at the access
layer with Layer 2 services at the metro-core.
Adaptive rate control for each connection (from 2Mbps and up to
2.5 Gbps in VC-12/3/4 increments).
LCAS protection - automatic adjustment of the Ethernet link capacity,
decreasing in case of VC failure and increasing when the network fault is
repaired, meeting the ITU-T G.7042 standard.
Network protection - including SNCP and MS-SPRing on each
connection.
Multi Spanning Tree Protocol (MSTP) for loop resolution and restoration
in ring and multi-ring configuration.
Equipment protection - carrier class, with no single point of failure.
General
Service providers are seeking a solution that will allow them use less
bandwidth to continue offering profitable services transparently over a lower
cost transport infrastructure. Structure Agnostic TDM over Packet (SAToP) is
an industry standard protocol designed specifically to address these issues.
SAToP functions as a Circuit Emulation Service (CES) that enables service
providers to deliver reliable, high-quality T1/E1 circuits over an Ethernet
infrastructure, thereby reducing or eliminating the need for a parallel TDM
network.
With the ongoing migration from TDM to Ethernet networks, service providers
can leverage SAToP in two layers of their networks:
Wide Area Network (WAN) trunks
Ethernet access circuits
By combining SAToP with their investment in an IP/MPLS core, service
providers can seamlessly change TDM circuits and long-haul trunks from
legacy SONET/SDH networks to the core MPLS infrastructure. SAToP easily
combines with Ethernet to give TDM traffic a transparent path on Ethernet
links. The transparent path readily translates into additional revenue streams
and reduced costs for service providers themselves, and investment protection
of TDM-based premises equipment for providers’ enterprise customers.
Cellular Application
Cellular operators plan to upgrade their base stations (2G BTSs) to nodeBs
(3G) with Ethernet based technology over time, depending on bandwidth
demands and economics. However, to maximize revenues they need a
migration strategy based on a cost-effective, scalable infrastructure that can
support 2G and 3G services. The chosen infrastructure must also be able to
protect operators’ existing network investments by offering more capacity at
lower cost. SAToP is an important technology that can help cellular operators
achieve a strategic, smooth path. Cellular operators that don't have their own
SDH infrastructure nearby, can install a small-scale, SAToP-compliant router
at each cell site. That router communicates with a larger, SAToP-compliant
router at an aggregation point, such as a Central Office (CO). By enabling the
transport of E1s over an Ethernet/MPLS pseudowire, SAToP allows wireless
operators to retain their E1 circuits and continue to add more.
Technology
RFC 4553 is the standard that describes SAToP. This is a method for
encapsulating Time Division Multiplexing (TDM) bit-streams (T1, E1, T3,
E3). It addresses only structure-agnostic transport, i.e., unframed E1, T1, E3
and T3. It segments all TDM services as bit streams and then encapsulates
them for transmission over a PW tunnel. This protocol can transparently
transmit TDM traffic data and synchronous timing information, which are two
of the elements of TDM emulation service. SAToP completely disregards any
structure and PEs have no need to interpret the TDM data or to participate in
the TDM signaling. The protocol is a simple way for transparent transmission
of PDH bit-streams. The implementation of the protocol is so easy that the
IETF released it as the earliest formal RFC.
IEEE 1588v2
IEEE 1588v2 is a packet-based synchronization method that offers both time
and frequency synchronization over an asynchronous packet network.
IEEE 1588v2 is based on the exchange of timing packets to synchronize many
slave/client elements to a master clock.
All BroadGate platforms support IEEE 1588v2 synchronization in slave mode.
BG-20 and BG-30, as well as, BGW-E expansion units working with a
BroadGate packet base platform also support IEEE 1588v2 synchronization in
master mode.
BGW-E expansion units working with BroadGate packet base platforms
support both input and output 1 pps signals as well as Time of Day (ToD)
signals.
Access-Controlled Management
Intelligent management access controls are needed at the customer edge to
prevent unauthorized users from accessing the network. Preventing denial of
service attacks involves deciding whether to accept, discard, or monitor certain
traffic.
Port Mirroring
Port mirroring helps the supervisor monitor the network. It copies ('mirrors')
the traffic from a specific port to a target port by copying packets entering or
exiting a port or entering a VLAN to a local port for local monitoring. This
mechanism helps track network errors or abnormal packet transmission without
interrupting the flow of data. Moreover, this feature enables a basic "lawful
interception" application for future development.
In this chapter:
Overview ......................................................................................................... 6-1
Overhead Processing ....................................................................................... 6-2
Main Controller Cards ..................................................................................... 6-3
SDH Interface .................................................................................................. 6-9
PDH Interface ................................................................................................ 6-11
Ethernet Interface and Switching .................................................................. 6-13
Optical Amplifiers and DCMs ....................................................................... 6-17
Dslot, Tslot and Eslot Data Traffic Functions ............................................... 6-18
Intelligent PCM Unit ..................................................................................... 6-18
Overview
BG processes voice and Ethernet data services over Ethernet and SDH lines. Its
modular architecture enables network operators to start small and simply and
cost-effectively expand their systems to higher capacities as demand grows.
This chapter describes the following BG components, cards and functions:
Overhead processing: This module provides flexible cross connects for all
STM-n interface section overhead bytes at the 64 Kbps level. It supports
transmission of RS-DCC, E1, F1, and E2 signals carried in multiple section
DCC bytes. Furthermore, it provides one V.11 overhead interface and one
orderwire interface. The orderwire interface connects to an external box
that supports the telephone device and both selected and conference calls in
any network topology.
Overhead Processing
The core of the overhead processing unit located in the BG-20’s MXC20 is a
full DS-0 cross-connect matrix. This matrix connects the section overhead
bytes of all STM-n interfaces, the DCC processing module in the control and
communication unit, the orderwire interface and processing module (located in
the optional BG-OW unit), the overhead interface module, one channel of a
framed E1 signal, and another channel which can be selected as framed or
unframed E1 (used to provide clear channels) so that all overhead bytes can be
flexibly cross connected.
In the BG-30 and in the BG-64 the cross-connect matrix, in the MCP30 or in
the MCP64, accordingly, cross connects between bytes from the following
sources:
Section overhead bytes of all STM-n interfaces
DCC bytes in clear-channel processing module, including two framed E1s
and two unframed E1s
Orderwire bytes from optional external BG-OW unit
Bytes from the V.11 (DCE mode) external input
MXC-20 Card
The MXC-20 card is the main card of the BG-20. It integrates functions such as
control and communication, cross connect, synchronization timing, overhead
processing, framing of SDH interfaces, and mapping of PDH and Ethernet
interfaces. The front panel of the MXC-20 has the following interfaces,
indicators, and buttons:
Network management interface
NE status indicator (Active), NE alarm severity indicator (Major, Minor),
and network management interface status indicator (Link)
System warm reset button (Reset)
21 E1 interfaces
One V.11 interface
One RS-232 interface
One orderwire unit connection interface
MXC-20C Card
The MXC-20C card is the main card of the BG-20C. It integrates functions
such as control and communication, cross connect, synchronization timing,
overhead processing, framing of SDH interfaces, and mapping of PDH and
Ethernet interfaces. The front panel of the MXC-20C has the following
interfaces, indicators, and buttons:
Network management interface
NE status indicator (Active), NE alarm severity indicator (Major, Minor),
and network management interface status indicator (Link)
System warm reset button (Reset)
21 E1 interfaces
Two SFP slots; each can house one optical or electrical SFP module
4 x 10/100BaseT interfaces
MCP30B Card
The heart of the BG-30 is the MCP30B card, which has the following
functions:
Communications and control
Alarm and maintenance
Routing and handling of 32 RS-DCC/32 MS-DCC channels (totally 32
channels) as well as two clear channels
The front panel of the MCP30B has the following interfaces, indicators, and
buttons:
Network management interface
NE status indicator (Active), NE alarm severity indicator (Major, Minor),
and network management interface status indicator (Link)
System warm reset button (Reset)
MCP64 Card
The heart of the BG-64 is the MCP64 card, which has the following functions:
Communications and control
Alarm and maintenance
Routing and handling of 32 x RS-DCC/32 x MS-DCC channels (totally 32
channels) as well as two clear channels
The front panel of the MCP64 has the following interfaces, indicators, and
buttons:
Network management interface
NE status indicator (Active), NE alarm severity indicator (Major, Minor),
and network management interface status indicator (Link)
System warm reset button (Reset)
Auxiliary connector supporting the following functions:
One V.11 interface
One RS-232 interface
One orderwire unit connection interface
Alarm input/output interfaces
T3/T4 external clock interfaces
The MCP64 card has a removable nonvolatile flash memory (NVM). The
Compact Flash memory can be accessed from the front of the MCP64 (no need
to extract the MCP64).
An MCP64 Interconnection Panel (ICP) can be used to spread the concentrated
Auxiliary connector into a dedicated connector for each function.
XIO30 Cards
The BG-30B shelf accommodates two identical XIO30 cards. There are four
types of XIO cards, each supporting different aggregate bandwidth and matrix
capacity. The XIO types are as follows:
XIO30_1: supports a 2.5 Gbps matrix and STM-1 SFP-based aggregate
interface
XIO30_4: supports a 2.5 Gbps matrix and STM-1/STM-4 SFP-based
aggregate interface
XIO30Q_1&4: supports a 15 Gbps matrix and 4 x STM-1/STM-4 or mix of
up to 4 x STM-1/-STM-4 SFP-based aggregate interface (each port
separately configurable)
XIO30_16: supports a 15 Gbps matrix and STM-4/STM-16 SFP-based
aggregate interface
By default, the lower XIO is the main card and the upper XIO is the protection
card. Both cards perform the following functions simultaneously in a 1+1
protection configuration:
Cross-connect
Timing and synchronization
Aggregate interface
In additional to the 1+1 protection of the cross-connect matrix, full 1:1
protection of timing functions is provided by the redundant XIO cards.
The two XIO cards operate in parallel. Each XIO matrix permits full
nonblocking connectivity at all VC levels. The matrices are connected to all
I/O modules, and provide the following capacity for each Tslot:
622 Mbps for every module with XIO30-1/4
2.5 Gbps for every module with XIO30-16 or XIO30Q_1&4
In case of a hardware failure in the active XIO, the I/O cards switch
automatically to the protection XIO within less than 50 msec. Similarly, in case
of a hardware failure in the Timing Unit (TMU) of the operational XIO card,
the backup TMU takes over the timing control with no disruption in traffic.
The main functions of the XIO30 matrix include:
HO and LO SDH 4/4/3/1 matrix cross connects at the VC-12, VC-3, VC-4,
and VC-4n order up to 16 or 96 STM-1 equivalents.
Traffic protection switching. The XIO30 supports MS linear protection,
bidirectional and unidirectional MSP, and SubNetwork Connection
Protection (SNCP).
Each I/O card is directly connected to the matrix cores (both main and
protection) and linked to every cross-connect direction and level. The link is
fully redundant at intershelf levels.
The following figure illustrates the simplified BG-30 overall block diagram. It
provides an overview of both the physical and functional partitioning of the
system.
XIO64 Cards
The BG-64 shelf accommodates two identical XIO64 cards. There are two
types of XIO cards, each supporting different aggregate bandwidth and matrix
capacity. The XIO types are as follows:
XIO64: supports a 40 Gbps matrix and an STM-64 XFP-based aggregate
interface with OTN support
XIO16_4: supports a 40 Gbps matrix and 4 x STM-1/4/16 SFP-based
aggregate interface
By default, the lower XIO is the main card and the upper XIO is the protection
card. Both cards perform the following functions simultaneously in a 1+1
protection configuration:
Cross-connect
Timing and synchronization
Aggregate interface
SDH Interface
BG supports various SDH interfaces, such as STM-1, STM-4, STM-16, and
STM-64.
BG-20
The BG-20 supports two onboard SDH interfaces, each supporting optical
STM-1,STM-4, or electrical STM-1 SFPs. An extractable daughterboard
installed in the BG-20B Dslot and an expansion card can add other SDH
interfaces. The following SDH traffic is supported:
SMD1H: a. hot-swappable extractable card installed in the BG-20B Dslot
that provides two SFP-based STM-1 interfaces, optical interfaces, electrical
STM-1 interfaces, or bidirectional STM-1 interfaces.
OMS4H: a hot-swappable extractable card installed in the BG-20B Dslot
that provides one STM-4 optical interface (such as S4.1, L4.1, and L4.2).
S1_4: a hot-swappable expansion card installed in the BG-20E expansion
slots that provides four SFP-based STM-1 interfaces, optical interfaces
such as S1.1, L1.1, L1.2, electrical STM-1 interfaces, or bidirectional
STM-1 interfaces. The S1_4 panel has four SFP module slots. Each slot
can support one optical or electrical STM-1 interface by installing the
appropriate SFP. Optical SFPs support LC connectors, while electrical
SFPs support DIN connectors. Each STM-1 interface has an LED that
indicates Laser On status.
BG-20C only supports two onboard SDH interfaces, each supporting optical
STM-1, STM-4, or electrical STM-1 SFPs.
BG-30
The BG-30 supports STM-1, STM-4, and STM-16 SDH interfaces. By flexibly
configuring various SDH interface cards in its Tslot and extension slots in the
BG-30E, the BG-30 provides different types and quantities of interfaces.
In addition to the Tslot and expansion SDH cards, each XIO30 card supports a
plug-in Small Form-factor Pluggable (SFP) transceiver according to the type of
XIO30:
XIO30_1 supports one STM-1o or STM-1e interface
XIO30_4 supports one STM-1/STM-4 compatible interface
XIO30Q_1&4 supports four STM-1/STM-4 compatible interfaces
XIO30_16 supports one STM-4/16 compatible interface
BG-64
The BG-64 supports STM-1, STM-4, STM-16 and STM-64 SDH interfaces.
By flexibly configuring various SDH interface cards in its Tslot and extension
slots in the BG-30E, the BG-64 provides different types and quantities of
interfaces.
In addition to the Tslot and expansion SDH cards, each XIO64 card supports a
plug-in Small Form-factor Pluggable (SFP or XFP) transceiver according to the
type of XIO cards. XIO64 supports one STM-64 interface; XIO16_4 supports
four STM-16 compatible interfaces.
The following SDH Tslot and extension cards are supported:
SMQ1&4 Tslot card: provides four SFP-based STM-1/4 compatible
interfaces. Each interface can be STM-1o, STM-1e or STM-4o.
SMQ1 Tslot card: provides four SFP-based STM-1 interfaces. Each
interface can be STM-1o or STM-1e.
PDH Interface
BG supports various PDH interfaces, such as E1, E3, and DS-3.
BG-20
By flexibly configuring various PDH interface cards in its Dslot and extension
slots in the BG-20E, the BG-20 provides different types and quantities of
interfaces, including:
Built-in E1 interfaces: provides 21 E1 interfaces and supports output
retiming (120 Ω only – external DDF with 120Ω-to-75Ω conversion
required for 75 Ω E1s).
ME1_21H Dslot module: hot-swappable extractable additional module
that provides 21 E1 interfaces (120 Ω only – external DDF with
120Ω-to-75Ω conversion required for 75 Ω E1s).
ME1_42H Dslot module: hot-swappable extractable additional module
that provides 42 E1 interfaces (120 Ω only – external DDF with
120Ω-to-75Ω conversion required for 75 Ω E1s).
PE1_63: a hot-swappable expansion card installed in the BG-20E
expansion slots providing 63 E1 interfaces and supporting output retiming
(120 Ω only – external DDF with 120Ω-to−75Ω conversion required for 75
Ω E1s). Its front panel has three double-VHDIC68 connectors that provide
interface cabling.
P345_3E: a hot-swappable expansion card installed in the BG 20E
expansion slots providing three E3/DS-3 interfaces, each of which can be
independently selected via the software. Its front panel has six coaxial
connectors that provide interface cabling. Each E3/DS-3 interface channel
has one indicator for its interface mode indication (E3 or DS-3).
M345_3: an extractable module installed in the traffic card of the MXC20
providing three E3/DS-3 interfaces, each of which can be independently
selected via the software.
When used at the network edge, the BG-20 needs only a small number of E1
interfaces. In this case, the interfaces can be provided directly through the
built-in E1 interface unit of the MXC20. Additional E1 interfaces can be
provided by E1 daughterboards in the BG-20B Dslot and/or E1 cards in the
BG-20E expansion slots. A single BG-20 shelf can provide up to 252 E1
interfaces.
BG-20C only supports built-in 21E1 interfaces.
BG-30/BG-64
By flexibly configuring various PDH interface cards in its Tslot and extension
slots in the BG-30E, the BG-30 and BG-64 provide different types and
quantities of interfaces.
All Tslot and extension cards support hot-swap functionality, allowing their
insertion and extraction to and from the NE without affecting traffic in other
cards.
PDH Tslot and extension cards include:
PME1_21 Tslot card: provides 21 E1 interfaces and supports output
retiming in the first eight channels (120 Ω only – external DDF with
120Ω-to-75Ω conversion required for 75 Ω E1s). Supports 1:2 or 1:1
tributary protection.
PME1_63 Tslot card: provides 63 E1 interfaces and supports output
retiming in the first eight channels (120 Ω only – external DDF with
120Ω-to-75Ω conversion required for 75 Ω E1s). Supports 1:2 or 1:1
tributary protection.
PM345_3 Tslot card: provides three E3/DS-3 configurable ports. Each
port can be set to DS-3 or E3 mode. Supports 1:1 tributary protection.
PE1_63 expansion card: an expansion card installed in the BG-30E
providing 63 E1 interfaces and supporting output retiming (120 Ω only –
external DDF with 120Ω-to-75Ω conversion required for 75 Ω E1s).
Supports 1:1 tributary protection.
P345_3E expansion card: an expansion card installed in the BG-30E
providing three E3/DS-3 interfaces, each of which can be independently
selected via the software. Supports 1:1 tributary protection.
For more Ethernet interfaces, the BG-20 supports the following cards:
MGE_1_L1 Dslot card: provides one optical or electric Gbe interface with
Layer 1 functionality over SDH virtual concatenated streams.
ME_2G_4F Dslot card: provides two GbE Combo interfaces, two FE
interfaces, and two FX interfaces with Layer 2 functionality over Ethernet
and SDH virtual concatenated streams. It supports 64 EoS interfaces, each
channel can be up to 4 x VC-4.
MPS_2G_8F expansion card: an expansion card installed in the BG 20E
providing two Combo GbE and eight electrical FE interfaces with Layer 2
and MPLS switch functionality over Ethernet and SDH virtual
concatenated streams. It supports 64 EoS interfaces, each channel can be up
to 4 x VC-4.
Support for EoP L1 services is achieved by using two EoP modules:
MEOP_4H: a Dslot module for the BG-20B unit supporting four FE LAN
interfaces with Layer 1 and Layer 2 functionality, and aggregation
functionality based on VLAN tag. Each LAN interface is connected to an
EoP internal interface supporting VCAT/GFP/LCAS standards at E1
granularity. The total supported capacity of all four L1 services is up to 64
Mbps (32 x E1), with up to 32 Mbps (16 x E1) for a single service. One
MEOP module can be installed in each BG-20 shelf.
SM_EOP: a traffic module for the SM_10E card supporting two FE LAN
interfaces with Layer 1 functionality. Up to nine SM_EOP modules can be
installed in each BG-20 shelf, with three modules per SM_10E card. Each
LAN interface is connected to an EoP internal interface supporting one of
the following two modes:
VCAT/GFP/LCAS standards at E1 granularity with a total capacity of
8 Mbps (4 x E1)
HDLC at 64 Kbps granularity with a total capacity of 2 Mbps per port
The BG-20 supports CES services using the following expansion card in the
BG-20E shelf:
DMCE1_32: an expansion card supporting 32 x E1 balanced interfaces (an
external xDDF-21 is required for unbalanced interfaces) on the TDM side.
E1 traffic can also be from the network STM-4 backplane interface or
native Ethernet. Connection to Ethernet traffic is supported via an FE/GbE
combo port.
Module name Traffic type Number of Ports per Max. ports per Max. ports per
modules per module SM_10E card BG-30E shelf
SM_10E
card
SM_V35_V11 V.35 ,or V.11/X.24, 3 2 6 18
or V.24 (64K)
configurable
Over N x 64K or
unframed E1
SM_24E V.24 3 8 24 72
Transparent mode
Async mode
Sync mode 4 12 36
2 6 18
SM_FXS_8E FXS 3 8 24 72
SM_FXO_8E FXO 3 8 24 72
SM_EM_ 2/4W E&M 3 6 18 54
24W_6E
SM_Codir_ Codir 3 4 12 36
4E
SM_Omni_E Omnibus 3 4 x 4W 12 x 4W 36 x 4W
8 conference 24 conference 72 conference
groups groups groups
SM_EoP EoP 3 2 6 18
SM_C37.94 C37.94 3 2 6 18
In this chapter:
Introduction ..................................................................................................... 7-2
Microwave Complementary Solution for BG and More ................................. 7-3
BG-Wave Product Line ................................................................................... 7-6
Benefits and Features....................................................................................... 7-7
BG-Wave's Value Proposition ......................................................................... 7-8
Applications ..................................................................................................... 7-9
Mobile Backhauling ...................................................................................... 7-10
WiMAX Backhauling .................................................................................... 7-11
Fixed-Line Access Backhaul ......................................................................... 7-12
BGW-10 Dedicated MRAN Platforms .......................................................... 7-14
BGW-E MRAN Expansion Shelves .............................................................. 7-16
MW_2 Base Cards ......................................................................................... 7-20
MIF Modules ................................................................................................. 7-21
BGW-O ODU ................................................................................................ 7-22
Modular Configuration Options .................................................................... 7-25
Timing and Synchronization ......................................................................... 7-28
Spectral Efficiency and Bandwidth Optimization ......................................... 7-30
Introduction
Mobile data traffic has already surpassed mobile voice traffic and is expected
to grow by an order of magnitude over the coming years. Mobile operators are
scrambling to meet this challenge.
To satisfy the ever-growing demand for services at an ever-lower cost, mobile
operators are turning to 3G IP and 4G wireless technologies to deliver voice
and data services. Wireless backhaul is expected to shift to a packet-based
infrastructure in order to cope with this huge traffic growth, lowering the cost
per bit while relieving bandwidth bottlenecks. The bandwidth scalability and
cost-reducing capability of next generation (NG) networks greatly relieve
network operators’ immediate pain. But their challenges go far beyond. An
optimized backhaul network capable of enabling new services and revenues
requires the enhanced Quality of Service (QoS) and performance management
capabilities intrinsic to NG networks. For all these reasons, the move to NG
wireless backhaul is essential.
Wireless communications means freedom. The freedom to get the services you
want in a wire-free environment. Cellular technology enables the freedom of
mobility, while microwave (MW) technology builds transport networks
without having to rely on a fiber or copper infrastructure.
Advantages of MW technology include support of higher data rates than those
available over copper leased lines, combined with lower cost and higher
availability than fiber, as well as faster provisioning and deployment. MW
equipment is also more portable, easily dismantled and moved as needed.
Wireless (cellular, WiMAX) and fixed line operators, enterprises, utilities, and
defense entities are all using MW for point-to-point (P2) transmission.
Additional MW applications include backhaul for mobile networks when
alternative backhaul means do not exist or are too costly to implement;
substitute for fiber when dealing with problematic terrain, no right of way, or
tight implementation schedules; backup for copper or fiber links; and ring
closure for metro and core fiber rings.
Despite its wide use, MW installation has been primarily through standalone
equipment, providing simple wireless transmission pipes. Great efforts have
been invested to make these links reliable and increase their capacity, but they
never extended beyond their role in the physical layer or became an integral
part of the network equipment. With the shift from TDM-based to
Ethernet-based infrastructure, new hybrid and pure Ethernet MW products
were introduced.
What service providers are expecting from MW equipment today is far beyond
this. The ECI Telecom BG-Wave product line provides:
A product for life with an ideal mix of scalability and growth options in a
single box
Future-proof, supporting any technology over any medium
No upfront costs - evolving as needed, when needed
Smooth and cost-effective migration to NG networks with advanced
networking and multiservice capabilities
Microwave Complementary
Solution for BG and More
The BG-Wave multiservice radio node (MRAN) provides integrated
microwave transport with full-blown networking and multiservice
capabilities. The BG-Wave provides GbE Ethernet radio service with native
TDM capabilities using field-proven RF system components. The BG-Wave’s
efficient combination of all-native hybrid and pure packet service provides
optimized carrier-grade service for any mixture of interfaces.
Figure 7-1: GbE Ethernet radio service with native TDM capabilities
Multiservice Capabilities
BG-Wave brings a new approach to MW-based transmission equipment.
Rather than adding limited networking functionality to MW equipment,
BG-Wave is a full-scale multiservice transport system with integrated MW
technology. BG-Wave is equipped to support any network topology,
technology mix, or migration phase of the service provider network.
The BG-Wave offers the best of all worlds with a complete range of interface
implementations for optimal efficiency in any context, including hybrid
products, providing native TDM and native Ethernet service as well as pure
packet products handling TDM via circuit emulation (CES). The flexible mix
of ADM, TDM cross connect, ETH/MPLS-TP switching, and CES
functionalities combined with microwave radio capabilities means that we can
help you design an infrastructure implementation tailored to your network
evolution requirements.
Applications
The BG-Wave product line provides a mobile service solution for network
operators in many different contexts:
Mobile operators, whether they are focusing only on mobile service or
adding multiplay services to their business plan. The BG-Wave’s spectral
efficiency provides maximum capacity per channel and the multiservice
capabilities make it a natural fit for any service mixture.
CoCs, CLECs, MSOs, and utilities that have positioned themselves as
wholesalers supplying wholesale services to a range of service providers.
The BG-Wave’s combination of flexibility and security make it the right
choice for complex open access systems as well as VLAN providers
supporting multiple client networks.
Homeland security requires secure, robust networking capabilities to fulfill
their mission. MW network infrastructures provide an excellent alternative
for these complex organizations, providing a flexible, cost-effective
infrastructure that is quick to implement and easy to manage as they enter
the world of networking. MW is an intelligent choice also for the
long-term, since it will continue to provide the enhanced power and
services they will need as their requirements grow over time.
Municipalities, universities, schools, and hospitals who are adding scalable
connectivity and high capacity networking services to their private
networks. Private networks serve as gateways to essential services under
many different contexts.
Mobile Backhauling
Most cellular networks currently deploy a blend of 2G and 3G infrastructures
as they look ahead to 4G and long term evolution (LTE) technology. To cope
efficiently with the complex realities of today’s cellular network
implementations, operators require a flexible scalable solution that can handle
the different technology permutations, including any combination of 2G TDM
(E1/T1 and STM-1), 3G hybrid TDM/Ethernet, and the all-Ethernet goal of
LTE and 4G networks.
ECI Telecom’s cellular backhaul solutions support all these interfaces and
technologies and enable a risk-free migration path in terms of scalability, traffic
mix, topology, synchronization, network protection, and E2E service
management. Precise synchronization through a choice of TDM-based, SyncE,
and IEEE 1588v2 clock synchronization mechanisms ensures the highest
quality cellular service over any combination of network technologies. The
BG-Wave is a powerful efficient choice ideally suited to the dynamic nature of
cellular backhauling networks, providing MW capabilities with enhanced
spectral efficiency for optimal bandwidth utilization, simultaneously supporting
legacy and modern technologies and interfaces.
WiMAX Backhauling
WiMAX backhauling is defined by the transport infrastructure between the
base stations and the WiMAX Access Service Network gateway (ASN-GW).
Base stations aggregate and control the wireless network toward client devices
and transport traffic to the operator Core Service Network (CSN). There are
several options for deploying WiMAX technology and the choice of method
critically influences the success of deployment.
WiMAX’s high-capacity service requires Ethernet connectivity between base
stations. The high-capacity all-IP networks require pure packet networking
implementations capable of delivering the necessary capacity with smooth
scalability at the lowest possible cost per bit. ECI Telecom’s BG-Wave
platforms provide exactly that - robust transport that meets the high standard of
WiMAX backhaul.
Figure 7-8: BGW-10 platform with MIF-10 and STM-1/OC-3 cards in the traffic slots
One INF-10 -48 VDC power supply subunit. This is a dual-feed subunit
with two connectors for redundancy, as well as accidental removal
protection.
One FCU-10 removable fan unit with four separate fans to support cooling
system redundancy, plus an optional air filter.
The following figure depicts the layout of the basic BGW-10 platform.
MW_2M
The MW_2M base card is for expansion shelves used with BroadGate Hybrid+
base platforms. The MW_2M supports hybrid traffic through the MIF radio
cards. The mixture of supported services includes:
Native Ethernet
Native TDM
EoS
Hybrid TDM and Ethernet mixtures
MW_2C
The MW_2C base card is for expansion shelves used with BroadGate packet
base platforms. The MW_2C supports pure Ethernet traffic. This module is the
ideal choice for pure packet network configurations that do not need to support
a mixture of different interface types.
MIF Modules
MIF modules are Modem Intermediate Frequency components that receive
incoming signals from a radio antenna and convert them to TDM or Ethernet
traffic for transmission through the rest of the network. (The radio signals are
actually collected by the radio antenna, converted to an intermediate frequency
by a modem, and transmitted through a coaxial cable to the MIF module.)
Supported features include:
Automatic Transmitter Power Control (ATPC)
Adaptive Coding and Modulation (ACM) for smooth flow control with no
packet loss and intelligent congestion management through profiling based
on CoS and color
Cross Polarization Interference Cancellation (XPIC) in the MIF-EX
For more information about the BG-Wave’s built-in optimization capabilities,
see Spectral Efficiency and Bandwidth Optimization (on page 7-30).
MIF-E
MIF-E modules transmit the intermediate frequency radio signal received on
the incoming coaxial cable from the ODU through a TNC connection. MIF-E
modules are used in MW_2 base cards in BGW-E/20E platforms.
MIF-EX
MIF-EX modules transmit the IF radio signal received on the incoming coaxial
cable from the ODU through a TNC connection. These modules provide
enhanced capacity through XPIC functionality described in XPIC (see "Cross
Polarization Interference Cancelation" on page 7-33). MIF-EX modules are
inserted into MW_2 base cards used in BGW-E/20E expansion platforms.
BGW-O ODU
The BGW-O is the ODU of the BG-Wave product line. The ODU is
responsible for signal amplification and frequency conversion between the RF
signal and the IF signal. Radio signals may be transmitting any combination of
SDH/SONET, SPDH, and/or GbE data interfaces within the RF frame.
An outgoing IF signal is converted to an RF signal, amplified, and transmitted
through the antenna. An incoming RF signal is filtered, demodulated into the
appropriate IF signal, and forwarded via the connecting coaxial cable to the
MIF card within the BG-Wave platform. The coaxial cable also transmits
management channel data, and provides power from the BG-Wave platform
power supply unit to the ODU.
BGW ODU modules support licensed ETSI and FCC frequency bands between
6 GHz and 38 GHz. Modulation schemes range from QPSK up to 256 QAM,
with both standard power and high power transmission models. Supported
channels depend on the licensing region:
ETSI: 7-56 MHz channels
FCC: 10-50 MHz
The output power setting range is software controllable, with an option to mute
transmission output power. BGW ODU platforms support Adaptive Transmit
Power Control (ATPC). TDM and Ethernet bandwidth in each channel spacing
and in each modulation are dynamically assigned within the ranges defined in a
configurable table. TDM traffic optimization is comparable to that of pure PDH
systems.
When a single ODU is used with a single antenna, the ODU is mounted
directly onto the back of the antenna. When two ODUs are used with a single
small antenna, the ODUs are connected to the antenna through a coupler
module, described in BG-Wave General Description. When two ODUs are
used with a larger or double-polarized antenna, the ODUs are connected
through a hybrid coupler using a remote mounting configuration. A simple
combination of antenna and ODU, about to be attached in a direct mount, is
illustrated in the following figure.
Modulation
MW radio signals are transmitted over specific channels within assigned
frequencies. BG-Wave platforms can be used with 6 GHz to 38 GHz
frequencies over 7 MHZ, 14 MHz, 28 MHz, 40 MHz, and 56 MHz channel
spacing (ETSI) or over 10 MHz, 20 MHz, 30 MHz, 40 MHz, and 50 MHz
channel spacing (FCC). Telecom signals are transmitted over these RFs
through the use of modulation schemes.
Modulation refers to the method by which a message signal is ‘inserted’ within
a high-capacity RF transmission signal. Modulation can be used, for example,
to transmit a digital bitstream over an analog channel such as an RF band.
Many different modulation schemes exist; the choice depends on several
technical considerations, including equipment capabilities and environmental
constraints. Generally, the higher the modulation, the greater the capacity.
BG-Wave platforms support modulation options ranging from QPSK to
256 QAM for all channel bandwidth, providing the maximum bandwidth
capacity possible in accordance with current standards.
Super PDH
Typical SDH STM-1 frames can transport 63 E1s or 84 T1s in a 155 Mbps
frame. An SDH radio link would need a 28/30 MHz channel to carry this
frame. Super PDH (SPDH) allows transmission of more traffic over the same
radio channel by eliminating SDH overhead. Using SPDH, the BG-Wave
provides up to 84 x E1/T1 per carrier, an increase of approximately 30% in
capacity. Combining SPDH with XPIC technology doubles that value to be
168 x E1/T1 per carrier.
SPDH can be combined with packet traffic in a hybrid radio frame. BG-Wave
platforms are designed for flexible bandwidth allocation for SPDH and
Ethernet traffic. TDM and Ethernet bandwidth in each channel spacing and in
each modulation are dynamically assigned within the ranges defined in a
configurable table. TDM traffic optimization is comparable to that of pure PDH
systems.
SPDH use enables BG-Wave platforms to add ACM, making it possible to use
high modulations for maximum spectral efficiency. SPDH service also supports
SNCP for high availability that matches the SDH standard.
Multi-Radio
Multi-radio refers to the simultaneous transmission of packet data over multiple
radio carriers. This configuration requires a separate ODU for each carrier link,
all transmitted through a single antenna. Transmissions may be over multiple
channels, or over a single channel using XPIC technology.
Multi-radio transmissions enable instantaneous automatic load balancing
between the carriers, achieving better radio link utilization. This system is
transparent to the user, who is only aware of a single high-capacity radio link.
Traffic is divided between the multiple carriers with no need for LAG
regardless of MAC addresses. Load balancing is accomplished on the physical
radio layer, independent of the packet flows or data traffic paths defined at a
higher level.
Since modulation for each radio carrier varies independently, multi-radio
service can be combined with ACM technology for optimal bandwidth
utilization.
Diverse Routing
Diverse routing is a method of utilizing extra radio link bandwidth that has
been set aside for protection purposes. Instead of than leaving this bandwidth
idle when protection is not required, network operators can use it for low
priority best effort traffic. If the main traffic links do go down, or if capacity is
reduced due to ACM downshifting, the high-priority protected traffic takes
precedence and is immediately rerouted to the backup links. The best effort
traffic is buffered or discarded until lower-priority bandwidth is available once
more.
In this chapter:
Routing and Forwarding Functionality............................................................ 8-1
Digital Communication Channel ..................................................................... 8-2
Communication Module .................................................................................. 8-9
Clear Channel
When a BroadGate network is interconnected with equipment from other
vendors, the BroadGate management may not be able to use the embedded
communication channels provided by the other vendor. For example, the other
equipment may not support IP packet forwarding. Nevertheless, the BroadGate
supports a complete range of alternate communication methods that enable full
interoperability with external vendor equipment despite any limitations.
Management traffic may be carried on a regular VC-12 crossing the external
network, using external equipment. BroadGate platforms, for example, can do
this internally, through a Clear Channel termination that operates in an identical
fashion to the RS-DCC/MS-DCC termination. The Clear Channel feature is
implemented when DCC management information must pass through an
external subnetwork that does not support the transport of transparent DCC
channels. To manage remote ECI Telecom equipment through other vendor
subnetworks, DCC channels are transported over 2 Mbps (VC-12) trails.
Communication Module
All platform configurations work with a built-in communications module. In
the BroadGate product line, the platforms work with the MCP, which features:
Electrical interface connectors that are integrated into the I/O modules,
eliminating the need for separate electrical interface modules
Easy routing of external management interfaces
Hot insertion of cards and modules to support quick maintenance and repair
activities, without affecting traffic
Monitoring system for acceptance test purposes
MCP
The MCP handles the management, OHA, and OW interfaces. It supports
standard OW as well as a special voice channel over the DCC when using VoIP
and a special router. This feature enables external calls from outside the
network to a particular site. In addition, the MCP generates system alarms and
activates indicators, for example software downloads, restarts, configurations,
and so on.
In this chapter:
Overview ......................................................................................................... 9-1
SDH Path Protection Schemes ........................................................................ 9-2
SDH Line Protection ....................................................................................... 9-5
Traffic Protection and Restoration................................................................... 9-8
Overview
BG features proven redundancy mechanisms to ensure the complete integrity of
all traffic transfers. System protection schemes offer highly reliable trail
protection arrangements and equipment duplication on all units. The platform
supports protection schemes at the line and service levels.
SNCP
SNCP provides independent trail protection for individual subnetworks
connected to BG, thus enhancing reliability against multiple failures. When
implemented in dual-node interconnections, SNCP, combined with the
drop-and-continue capability of BG, is even more powerful against multifailure
conditions in mesh topologies. By integrating SNCP into BG, operators achieve
superior traffic availability figures. SNCP is therefore extremely important for
leased lines or other traffic requiring superior SLA availability.
SNCP switching functions automatically in BG without operator intervention
or path redefinition. The result is an exceptionally fast protection switching
time of less than 30 msec, with typical switching time taking only a few msecs.
Protection switching is performed in a distributed way in the service cards.
A major SNCP advantage is its flexibility. SNCP is topology-independent and
can be implemented in ring, chain, star, mesh, and hybrid topologies. It can be
implemented with platforms from other vendors, enabling the creation of a ring
where traffic originating from other ADMs is fully protected.
Leased lines are provided through single-link connections. In the event of
failure, leased-line traffic is protected by SNCP switching at the service
termination point.
In typical multiring or mesh networks, the SNCP drop-and-continue
functionality provides better traffic reliability and link redundancy in the event
of a site failure. In these networks, four ADMs are typically required to enable
this functionality (see the following figure showing only one direction).
BG supports SNCP at all STM-n levels (STM-1 to STM-64) and for all VC
objects, as follows:
Any VC-4 in any STM-n
Any VC-4nc in any STM-n
Any VC-3 in any VC-4 in any STM-n
Any C-12 in any VVC-4 in any STM-n
BG supports the following SNCP types:
SNCP/I: SNC protection switching due to TU-AIS, AU-AIS, TU-LOP, or
AU-LOP events
SNCP/N: SNC protection switching due to TU-AIS, AU-AIS, TU-LOP, or
AU-LOP events, and any other path overhead alarms (signal label
mismatch, path trace error, EBER)
BG enables users to set EBER thresholds for BER and Signal Degradation
(SD) conditions. The SNCP function is complemented by the user option to set
the hold-off time for switching (0-10 sec in 100 msec intervals) and the Wait to
Restore (WTR) time (1-30 minutes), in accordance with applicable standards.
The EMS-BGF enables both automatic and manual switch to protection and
protection lockout commands. When an automatic switch occurs, notification is
sent to the subnetwork management station. The status of the selectors and the
subnetwork connections is displayed in the EMS-BGF window.
Revertive SNCP
BG platforms support revertive SNCP.
When the system is protected by regular SNCP, it uses the protection path in
the event a failure is detected in the main path, and does not revert to the main
path even after it recovers. The protected path may incorporate links that are
more expensive and less reliable (for instance, leased lines).
Revertive SNCP is useful when the user has a preferred path for traffic and can
switch back to the main path after recovery. The user can now define the
operating mode as revertive or nonrevertive SNCP, giving a higher degree of
flexibility.
The system provides several parameters to ensure that the failed (main) path is
stable and reliable before reverting to it after a fault condition. Most of these
are user-configured, including:
Wait to Restore (WTR): The period of time after which a failed unit is
fault-free and can be considered as available again by the protection processes.
Wait to Switch (WTS): Factory-defined timer issued to prevent excessive
switching events in a nonstable condition. This timer disables switching to the
protection path for X minutes if Y or more switches occurred in a period of
time of Z seconds.
Hold-off time: Useful for interworking of protection schemes and provisioned
on an individual equipment basis. The failure condition is monitored at the end
of the hold-off time before switching to the protection path.
Switch time: Traffic switch operating as quickly as possible. The target time is
50 msec.
MSP
MSP is designed to protect single optical links. This protection is most suitable
for appendage TM/star links or for four-fiber links in chain topologies.
BG supports MSP in all optical line cards (STM-1, STM-4, STM-16, and
STM-64). MSP 1+1 unidirectional and bidirectional modes are supported.
MSP 1+1 is implemented between two SDH interfaces (working and
protection) of the same bitrate that communicate with two interfaces on another
platform. As with SNCP and path protection, in MSP mode BG provides
protection for both fiber and hardware faults.
The following figure shows a four-fiber star BG with all links protected. This
ensures uninterrupted service even in the case of a double fault. BG
automatically performs MSP switching within 50 msec.
MS-SPRing
In addition to SNCP protection that may also be implemented in mesh
topologies, BG supports MS-SPRing that provides bandwidth advantages for
selected ring-based traffic patterns.
Two-fiber MS-SPRing supports any 2.5 Gbps rings closed by BG via the
XIO30_16/XIO16_4 card or 10Gbps rings closed by BG via XIO64 card, in
compliance with applicable ITU T standards. This is fully automatic and
performed in less than 50 msec.
MS-SPRing can support LO traffic arriving at the nodes in the same way it
does HO traffic. LO traffic support on MS-SPRing is unique to BG, as it is a
genuine MSPP.
In MS-SPRing modes, the STM-n signal is divided into working and protection
capacity per MS. In case of a failure in one MS of the ring, the protection
capacity loops back the affected traffic at both ends of the faulty MS. BG
supports the full squelching protocol to prevent traffic misconnections in cases
of failure at isolated nodes. Trails to be dropped at such nodes are muted to
prevent their being delivered to the wrong destination.
MS-SPRing is particularly beneficial in ring applications with uniform or
adjacent traffic patterns, as it offers significant capacity advantages compared
to other protection schemes.
The following figure shows a BG in a two-fiber MS-SPRing. In this
configuration, two fibers are connected between each site. Each fiber delivers
50% of the active and 50% of the shared protection traffic. For example, in an
STM-16 ring, eight VC-4s are active and eight VC-4s are reserved for shared
protection.
In the event of a fiber cut between sites A and D, traffic is transported through
sites B and C on the black portion of the counterclockwise fiber. The switch in
traffic is triggered by the APS protocol that transmits control signals over the
K1 and K2 bytes in the fiber from site D to site A.
Extra traffic capability is also supported, enabling users to use the protecting
VC-4s to carry extra traffic that is dropped in case of a failure in the protected
VC-4s. Thus, the total capacity of the ring is used, provided there are no
network failures. The extra traffic itself is, of course, not protected.
When a failure is detected, the nodes adjacent to the failure block the failed
link and report this failure to the ring, using a R-APS Signal Failure (SF)
message. The message triggers the RPL owner to unblock the RPL and all
nodes to perform FDB flushing. The ring is now in protection state.
When the failed link recovers, the nodes adjacent to the recovered link transmit
a R-APS No Request (NR) message, indicating they have no local request.
When the RPL owner receives the R-APS message it starts a Wait to Restore
(WTR) timer. Once the WTR expires, the RPL owner blocks the RPL and
transmits a R-APS (NR, RB) No Request, Root Blocked message. The nodes
receiving the message perform a selective FDB flush (on page 5-16) for the
relevant port and unblock their previously blocked port. The ring returns to
normal operation (idle state).
Equipment Protection
BG’s high-level reliability is achieved through comprehensive equipment
redundancy on all units. Automatic protection switching is initiated by a robust
internal BIT diagnostic system.
The TPS1_1 panel has 12 pairs of coaxial connectors that provide interface
cabling for customer and protected/protecting PM345_3 P345_3E, SMQ1&4 or
XIO30 cards. As the TPS1_1 provides four channels of E3/DS-3/STM-1e
protection per card, the connectors are arranged in three groups, as follows:
One group is used to connect customer equipment.
One group is connected to protected cards.
One group is connected to a protecting card.
The TP63_1 panel has seven interface connectors. These connectors are used as
follows:
Three are used to connect to the customer equipment
Two are connected to a protected PE1_63 card in BG-30E Eslots by
external cables.
Two are connected to a protecting PE1_63 card in a BG-30E Eslot by
external cables.
Common Unit
BG provides 1+1 and 1:1 protection of the power supply and XIO30/XIO64.
In this chapter:
Layered Architecture ..................................................................................... 10-1
Client/Server Architecture ............................................................................. 10-2
Integration with Other Products .................................................................... 10-3
LightSoft Network Manager .......................................................................... 10-3
Layered Architecture
ECI Telecom’s management concept is designed using a layered architecture in
accordance with applicable standards. Separate management layers make up
the management structure. The lowest level, the Network Element Layer
(NEL), constitutes the embedded agent software of the NEs. The second layer,
the Element Management Layer (EML), controls many individual NEs, while
the third layer, the Network Management Layer (NML), controls the main
network management functions.
Client/Server Architecture
LightSoft implements an advanced client/server software architecture that
supports a large number of processes. The LightSoft server can be run on either
single or multiple workstations. This distributed architecture enables you to
divide large complex networks among multiple operators. The
multiconfigurator feature of LightSoft gives each operator the means to initiate
sessions and manage the network simultaneously, either in whole or in part.
Management Interfaces
LightSoft supports an open CORBA-based interface both northbound and
southbound for managing or being managed by third-party applications. The
EMS-BGF also supports the same interface, northbound. The interface, which
supports alarms, configuration, and provisioning, complies with the
Multi-Technology Network Management (MTNM) information model being
developed by the TeleManagement Forum (TMF), a consortium of all major
telecom equipment vendors. EMS-BGF, which manages BG equipment,
supports a number of conventional interfaces, such as export of current alarms
via FTP.
Topology Management
LightSoft allows network administrators to commission and configure
equipment in local and remote subnetworks across the deployment. NEs can be
deployed in a wide range of topologies, including single or multiple rings with
appendages, or chains and composite topologies incorporating terminal
multiplexers. Users move intuitively from an overall survey of the network
landscape to detailed status and control views of any NE, transmission level,
system card, or trail.
This application enables you to manage NEs at multiple levels. It distinguishes
between the NEs (or managed elements [MEs]) that make up the network, and
the logical elements (LEs) that these MEs represent. An ME designates a piece
of equipment, like a shelf, whereas the LE is a technology-oriented
representation of the various physical elements in the network. You can
customize these elements by splitting them. For example, different icons on the
map may represent different ports belonging to a single NE.
This unique distinction enables true multidimensional network management by
allowing operators to:
Focus on MEs when creating and deleting NEs (physical layer)
Focus separately on the ports available at each technology level (for
example, SDH, optical, or data) when managing trails (technology layer)
Whenever an ME is added to the network at the physical layer of LightSoft, an
LE is automatically projected into the relevant technology layer, as shown in
the topology view in the interface. If an ME contains ports that belong to
multiple technologies, as is the case with BG shelves, LEs are created at each
technology layer containing only the ports relevant to that layer. Nested groups
are supported and can be defined differently in the various layers.
Trail Configuration
LightSoft provides powerful trail configuration tools. A detailed definition of
through and local XCs gives administrators a precise control of the system
structure, guaranteeing uninterrupted services and maximized use of
bandwidth. In addition to manual trail routing, the patent-pending path-finding
algorithm searches for and selects optimal end-to-end primary and protection
paths across complex topologies. Optimization criteria are user-defined and
may include such parameters as number of nodes, link cost, distance, shared
risk (such as common ducts), and so on. A powerful trail synchronization
function polls the entire network, keeping the LightSoft trail database up to
date. LightSoft also provides numerous protection and traffic reconfiguration
schemes in case of service disruption. The system provides full traffic
restoration via contingency traffic plans.
The LightSoft advanced trail management functions allow you to create, delete,
and modify SDH trails, and to acquire optical and data services from the
network.
Fault Management
LightSoft simplifies real-time status monitoring of the network and its
elements. The main window uses color-coded icons to show equipment status
at a glance. Customizable alarm listings, alarm counters, and alarm audio
indicators, which are updated in real time, are displayed in the main window.
Administrators can acknowledge alarms from the Current Alarms list, post
“sticky note”-type messages (User Notes) to other network personnel, and
customize their own alarm filters. They can click any element in the diagram to
open status windows listing the alarms for each object, including NEs, cards,
and physical ports.
The LightSoft fault management system is fully integrated and includes alarms
for all managed NEs, regardless of the layer (physical, SDH, data, or optical)
on view.
GUI Cut-Through
LightSoft uses a process called GUI cut-through to invoke EMS functions
without launching the EMS-BGF. You can:
Set, change, and propagate NE attributes
Configure shelves and cards
Change alarm severities
Set NE timing sources
Activate performance management functions on NEs
Perform maintenance functions on NEs or their objects
Redundancy
LightSoft and EMS-BGF provide a fully field-proven redundancy mechanism
called Remote Database Replication (RDR) that provides full network
management backup capabilities. RDR ensures system continuity by
maintaining a comprehensive and complete backup copy of the current network
configuration. LightSoft and EMS-BGF use duplicate management hardware,
with one station serving as the active site (primary server) and the other as the
standby site (backup server and mirror). One standby site can act as a backup
for multiple stations (1:n) running LightSoft, and various EMSs.
All the databases in the active site (NMS and EMS) are periodically duplicated
and transmitted over a direct link to the standby site. To make the backup
process efficient, only changes made since the last replication are included.
Should a failure occur in the active site, the operator quickly switches over to
the standby site and resumes management of the network within minutes. The
LightSoft and EMS-BGF databases’ signature feature intelligently updates the
standby site with all NE configuration data that has changed since the last
replication.
Security
LightSoft provides two main types of security functions:
User security
System security
User security controls the persons having access to the system (user groups),
which operations these users can perform (capability profiles), and the
elements of the network on which these operations can be performed
(domains). In LightSoft, all users are assigned to user groups, each of which is
then paired with a capability profile and a defined number of domains. Users in
a particular user group can perform only those functions provided for by their
capability profile assigned to the group, and only on those domains assigned to
the group.
LightSoft enables you to divide a network into many different VPNs, each one
having its own capability profile. This method provides each client with the
appropriate level of operational control, without infringing on the security
needs of any other client.
Passwords, user action logs, and an optional keyboard lock feature are used to
further ensure system security and integrity.
EMS-BGF
The EMS-BGF provides full-feature support for BroadGate, BG-Wave, and
CESR BG9300 platforms. The EMS-BGF functions at the EML in the TMN
scheme directly under LightSoft. It is designed as an open system in
compliance with the MTNM standard provided by CORBA.
ECI Telecom has enhanced the functionality and scalability of element
management in EMS-BGF V10 and above to the level of a carrier grade
application, providing a state-of-the-art GUI and superior user experience.
EMS-BGF V10 and above is based on Java together with a relational database,
allowing it to run on multiple platforms (e.g., Microsoft Windows, SUN™
Solaris) and support multiple operators concurrently.
Having a robust architecture enables the EMS to support hundreds of NEs at a
time, letting customers expand their network without the need to install more
EMSs.
The EMS-BGF supports the entire FCAPS requirement, providing a wide range
of management functions (alarms, configuration, inventory, provisioning, and
security).
LCT-BGF
The LCT-BGF is a PC-based BG installation, maintenance, commissioning,
and configuration tool for field technicians. LCT-BGF is an advanced graphical
craft terminal designed for convenience and efficiency. The GUI of LCT-BGF
is identical to the EMS-BGF, making this product extremely easy to use. It
provides rapid direct connection to deployed NEs using an Ethernet interface.
The LCT-BGF includes all the functionality required by a technician arriving at
a site: full installation, NE commissioning (including slot assignment, IP
routing, and DCC port configuration), and troubleshooting. It provides the user
with a clear view and control of NE internals (cards, objects, status,
configuration). Password protection ensures only authorized access to
field-installed equipment.
In this appendix:
Overview ........................................................................................................ A-1
CEPT: Conference of European Postal and Telecommunications
Administrations .............................................................................................. A-2
ETSI: European Telecommunications Standards Institute ............................. A-3
IEC: International Electrotechnical Commission ........................................... A-4
IEEE: Institute of Electrical and Electronic Engineers................................... A-4
IETF: Internet Engineering Task Force .......................................................... A-5
ISO: International Organization for Standardization ...................................... A-6
ITU-R: International Telecommunication Union (Radiocommunication
Sector)............................................................................................................. A-6
ITU-T: International Telecommunication Union ........................................... A-7
MEF: Metro Ethernet Forum ........................................................................ A-10
Overview
The following is a list of standards and reference documents that relate to the
BroadGate Product Line platform families. The standards are listed
alphabetically by groups.
ETSI: European
Telecommunications Standards
Institute
EN 300 019 class 3.2 & 3.3 Environmental.
EN 300 132 2: Power Supply Interface at the Input to Telecommunication
Equipment, Operated by Direct Current.
EN 300 386 CLASS B.
EN 300 386 2: Telecommunication Network Equipment EMC
Requirements.
EN 301 489- 4: Electromagnetic Compatibility and Radio Spectrum
Matters (ERM).
EN 302 217-2-2: Fixed Radio Systems; Characteristics and requirements
for point-to-point equipment and antennas.
BS EN 60870-2-2:Telecontrol equipment and System - Part 2 Operation
Condition – Section 2: Environmental Condition.
ETR 114: Functional Architecture of SDH Transport Networks.
ETS 300 119: European Telecommunication Standard for Equipment
Practice.
ETS 300 147: Synchronous Digital Hierarchy Multiplexing Structure.
ETS 300 232: Optical Interfaces for Equipment and Systems Relating to
the Synchronous Digital Hierarchy.
ETS 300 417: Generic Functional Requirements for Synchronous Digital
Hierarchy Equipment.
ETS 300 462 (Parts 1, 2, 3, 4, 5): Transmission and Multiplexing (TM) -
Generic Requirements for Synchronization Networks; Synchronization
Network Architecture; The Control of Jitter and Wander within
Synchronization; Timing Characteristics of Slave Clocks Suitable for
Operation in Synchronous Digital Hierarchy (SDH) Equipment.
ETS 300 746: Transmission and Multiplexing; Synchronous Digital
Hierarchy; Network Protection Schemes; Automatic Protection Switch
(APS) Operation.
IEC: International
Electrotechnical Commission
IEC 3309/BS ISO: Information Technology – Telecommunications and
Information Exchange between Systems – High-Level Data Link Control
(HDLC) Procedures – Frame Structure.
IEC/EN/UL 60950-1: Information Technology Equipment - Safety -
General Requirements.
IEC 60950-1: Equipment Safety Part-1: General Requirements.
IEC 917: Modular Order for the Development of Mechanical Structures for
Electronic Equipment Practices.
IEC 9595/BS ISO, Information Technology: Open Systems
Interconnection, Common Management Information Services.
Draft-ietf-pwe3-cesops.
Draft-ietf-pwe3-control-protocol.
Draft-ietf-pwe3-vccv.
MPLS-TP Requirements: Draft-jenkins-mpls-mpls-tp-requirements.
MPLS-TP OAM Analysis: Draft-sprecher-mpls-tp-oam-analysis.
Requirements for OAM in MPLS Transport Networks:
Draft-vigoureux-mpls-tp-oam-requirements.
Assignment of the Generic Associated Channel Header Label (GAL):
Draft-vigoureux-mpls-tp-gal.
A Framework for MPLS in Transport Networks:
Draft-blb-mpls-tp-framework.
"The OAM Acronym Soup": Draft-andersson-mpls-tp-oam-def.
MPLS Generic Associated Channel: Draft-bocci-pwe3-mpls-tp-ge-ach.
MPLS TP Network Management Requirements:
Draft-gray-mpls-tp-nm-req.
MPLS TP Survivability Framework: Draft-sprecher-mpls-tp-survive-fwk.
ITU-R: International
Telecommunication Union
(Radiocommunication Sector)
F.1191: Bandwidths and unwanted emissions of digital radio-relay systems.
F.383-6: Radio-frequency channel arrangements for high capacity
radio-relay systems operating in the lower 6 GHz band.
F.383-7: Radio-frequency channel arrangements for high capacity fixed
wireless systems operating in the lower 6 GHz (5 925 to 6 425 MHz) band.
F.384-7: Radio-frequency channel arrangements for medium and high
capacity analogue or digital radio-relay systems operating in the upper 6H
GHz band.
F.385-6: Radio-frequency channel arrangements for radio-relay systems
operating in the 7 GHz band.
ITU-T: International
Telecommunication Union
G.650: Definition and Test Methods for the Relevant Parameters of Single
mode Fibers.
G.651: Characteristics of a 50/125 µm Multimode Graded Index Optical
Fiber Cable.
G.652: Characteristics of a Single mode Optical Fiber Cable.
G.653: Characteristics of a Dispersion shifted Single mode Optical Fiber
Cable.
G.654: Characteristics of a Cut off Shifted Single Mode Optical Fiber
Cable.
C I
Cellular Applications • 2-3 Integration with Other Products • 10-3
Client/Server • 10-2 Inteligent PCM • 6-18
Commuinication with Management • 3-5 Internal Control and Processing • 3-3
Communication with External Equipment L
• 3-5
Components • 6-1 Layered Architecture • 10-1
Configuration Backup • 3-3 LCT-BGF • 10-11
Control Subsystem • 3-3 LightSoft Network Manager • 10-3
Cross-Connect Funcionality • 3-6 fault management • 10-7
GUI • 10-4
D
GUI cut-through • 10-8
Data Applications • 2-2 management interfaces • 10-3
Data Traffic Functions redundancy • 10-8
BG-30 • 6-18 redundancy and security • 10-8
BG-64 • 6-18 security functions • 10-9
Data Trffaic Functions • 1-6 topology management • 10-5
DCMs • 6-17 trail configuration • 10-6
E M
EMS-BGF • 10-9 Main Controller Cards • 6-3
Equipment Protection • 9-11 Management • 10-1
common unit • 9-12 layered architecture • 10-1
traffic unit • 9-11 third-party • 10-3
Ethernet • 1-6 MCP30 • 6-4
bandwidth scaling protection • 9-11 MCP64 • 6-5
traffic protection • 9-8 Metro-Access Applications • 2-3
Ethernet Interface and switching • 6-13 MIF modules • 7-21
BG-20 • 6-13 MIF-E • 7-22
BG-30 • 6-15 MIF-EX • 7-22
BG-64 • 6-15 MPLS • 1-6
Expansion Traffic Cards MSP • 9-5
BG-20E • 4-8 MS-SPRing • 9-6
BG-30E • 4-13 dual-node interconnection • 9-7
F Integration of SNCP • 9-7
Multi-ADM and Multi-TM Modes • 3-8
Fault Management • 10-7
MW_2 base cards • 7-20
Features and Benefits • 1-5
MW_2C • 7-21
G MW_2M • 7-21
GUI Cut-Through • 10-8 MXC20 • 6-3