Professional Documents
Culture Documents
Tellabs 8600 Overview
Tellabs 8600 Overview
Tellabs 8600
Introduction
The aim of this document is to give the reader a basic understanding of the Tellabs 8600
Managed Edge System and a vision as to where the platform is developing. It covers the
target market, the main applications and the component building blocks that make up the
system today and in a longer term. As a prerequisite, the reader should have a basic
knowledge of telecommunications and mobile networks. The document is written at a
relatively high level and starts with an overview of access networks from both a wireless and
wireline perspective. This is followed by a more detailed introduction to the Tellabs 8600
system and how it can operate in both of these types of networks. The final section
concentrates on the specific network elements and the network management system,
which is an essential and integrated part of the whole solution.
Tellabs operates globally and is a leading supplier of managed access transport platforms to
service providers around the world. Tellabs has a successful record of providing managed
access solutions to more than 300 customers over the past 15 years. The Tellabs 8600
system is a next-generation packet-based platform that is suitable for both access and
regional networks in mobile transport and converged networks. It is attractive not only to
new customers building long term network solutions but also to existing Tellabs 8100
Managed Access System customers wishing to extend the capabilities of their current
access networks.
Tellabs knows how important it is to provide our customers with a seamless migration from
their current solutions as they introduce new technology and provision new services. A lot of
effort has therefore been made to integrate all of the network elements under one
management system. A chapter of this guide is dedicated to what this means in practice
and the added value that it provides for the customer.
2
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
The Tellabs 8600 Managed Edge System in next-generation networks . . . . . . . . . . . . . . 4
The Tellabs 8600 systems benefits and role in wireless transport . . . . . . . . . . . . . . . . . . . 6
The Tellabs 8600 system in GSM and UMTS networks . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Customer cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
The Tellabs 8600 system in CDMA networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Tellabs 8600 system functionality in a mobile network . . . . . . . . . . . . . . . . . . . . . . . . . . 13
The Tellabs 8600 system in wireline transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Network and service deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Managed migration path from the Tellabs 8100 and Tellabs 6300 systems . . . . . . . . . . . 19
Network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Element architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Network management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Summary of product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Acronyms and initialisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
3
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Network evolution traffic in high volumes. The trend today is towards Ethernet- and IP-
based services, which offer a more natural fit to the predominately
The Tellabs 8600 Managed Edge System has been designed using
data traffic mix. They are also more economical for the service
feedback from many global telecommunications service providers.
provider to deploy, given the ubiquity of Ethernet-equipped network
Together they face the following market and technology challenges:
devices.
In wireless networks, the 3G and release 5 ratification is
This unified technology is blurring the boundary between the
accelerating the move of mobile services to an all-IP network;
customer and service provider networks. It therefore offers service
mobile service providers are therefore looking for a way to migrate
providers the opportunity to offer more value-added services such
their current Radio Access Networks (RANs) based on
as VPNs, storage backup and outsourced IT applications.
Asynchronous Transfer Mode (ATM) to a manageable Internet
Protocol (IP) implementation. Now that bandwidth is becoming a commodity, users service
expectations are rising. Simple connectivity as a service is no longer
In wireline networks, business and residential services are
adequate; service providers need the ability to differentiate their
becoming predominately IP- and Ethernet-based; with increasing
services. Users are demanding Service Level Agreements (SLAs)
bandwidth requirements and new service delivery models, the
from their service providers. These SLAs specify, for example, the
current infrastructure is becoming inefficient and expensive to
service availability, repair time and service quality parameters. To
maintain.
maintain these service levels, the service provider can also manage
Fixed and wireless convergence is taking place both in the the customer premises equipment directly on the customers behalf.
services and in the underlying networks; the distinction between
The main force for the growth of IP traffic has arisen from the ever-
these previously distinct applications is now becoming blurred.
increasing use of the Internet. This has been fueled recently by the
These challenges and the issues they raise are explained in more now widespread availability of broadband services to home users.
detail below. This is followed by a section explaining how the Tellabs New applications continue to be layered on IP, and legacy systems
8600 system helps to address them. are already being replaced with IP alternatives Voice over IP
(VoIP) being a prime example.
Wireless Networks As broadband services become an essential part of everyday home
After years of speculation, mobile network operators are finally life, the demand for bandwidth will continue to grow exponentially.
going through the evolution from 2G to 3G. This transition, which This is creating pressure on the bandwidth available to the end user
will call for major investments in the mobile network infrastructure, and is also creating scalability issues in the wider core network. The
is taking place globally in both GSM- and CDMA-dominated promise of triple-play services, where voice, data and video services
markets. In practice, the evolution of mobile networks will mean are available through a single access interface, is another challenge
upgrades to all mobile-network-specific components from the for service providers to deliver cost-effectively.
mobile cell stations, through the RAN, and right into the core
network. The underlying transport technologies are expected to The Wider Challenge
undergo a transformation from Time Division Multiplexing (TDM)
An IP infrastructure is the ideal choice for quickly and cost-
and Frame Relay (FR) to ATM and eventually IP. At the moment, the
effectively delivering different types of business and residential
use of Internet Protocol / Multiprotocol Label Switching (IP/MPLS) is
services. However, it is critical that it comply with the traditional
restricted to the core of next-generation mobile networks but is
requirements of the service provider: carrier-class operations and
gradually moving out into the RAN and towards the user. Eventually
manageability. For instance, wireless service providers need the
it will be used to provide an all-IP network, replacing the legacy
Quality of Service (QoS), predictability and reliability that up to now
ATM systems over the long term.
could be delivered only with connection-oriented networks. The
Because the RAN infrastructure is expected to rely sooner or later deployment of converged packet-based networks will enable
rely heavily on IP, it makes economic sense to converge the fixed wireless carriers to offer higher-value data services, which will
and mobile networks to use the same generic packet-based enhance their existing voice services and create new revenue
architecture. As an example, many mobile operators intend to offer streams. With the Tellabs 8600 system, Tellabs offers service
WiFi or WiMAX as complementary access methods in certain areas providers a scalable and potentially cost-effective solution to this
for different services. Additionally, business services such as the IP challenge.
Virtual Private Network (IP VPN) or Metro Ethernet can be used to
enhance the service portfolio.
Wireline Networks
The Tellabs 8600 Managed Edge System
in next-generation networks
The increased utilization of the Internet and the move to IP-based
applications and services is both a business and residential user The Tellabs 8600 system is a next-generation platform for building
phenomenon. advanced telecommunications networks and services. It has been
designed to meet the requirements of service providers who need
One of the most popular business services is Local Area Network to extend packet switching technologies more and more deeply into
(LAN) interconnection, which is used to build corporate intranets their access networks. While doing so, it provides the reassurance
and share company data and applications across remote sites. of a true carrier-class platform on which to build and deploy new
Traditionally, the technology for providing LAN interconnection has services.
been TDM, FR and ATM. However, these are all limited in their
capacity and are not very cost-efficient when used to transport data Tellabs understands that any investment made in the access
4
network has to last for many years. It has therefore designed a The key benefits of the Tellabs 8600 system, explained further in
system that is so scalable and extendable that it is intended handle the chapters that follow, include provision of:
years of new service deployment and change. Tellabs also A platform supporting technologies needed for evolving mobile
understands the pressures facing todays service providers. Falling networks
margins in both fixed and mobile voice revenues, plus increasing
An intelligent management system
regulatory and competitive pressure, are squeezing profit margins
dramatically. Design for an optimized cost structure
Working with its global customer base, Tellabs has designed the
Tellabs 8600 system to offer very low operation costs as well as Platform Supporting Technologies Needed for Evolving Mobile
rapid network and service deployment with an architecture that Networks
facilitates efficient use of the available network resources. Since The Tellabs 8600 system when combined with the intelligent
existing Tellabs customers have made significant investments in Tellabs 8000 manager is a solution for the needs of evolving mobile
their current access infrastructure, Tellabs provides a seamless networks. It is a scalable platform that can be positioned anywhere
transition and compatibility between its Tellabs 8100 Managed in the mobile RAN. At the Radio Network Controller (RNC) site it
Access System, the Tellabs 6300 Managed Transport System and can provide significant savings for the service provider in the overall
the new Tellabs 8600 system. Full management capabilities across transport cost by improving scalability and optimizing the RNC port
all of these platforms are provided by a single management system, costs. Additionally at the RNC site, the Tellabs 8600 system
the Tellabs 8000 Network Manager. platform can act as a Customer Edge (CE) network device.
The Tellabs 8600 system builds on the extensive experience Tellabs Positioned at the hub site, the Tellabs 8600 system can bring
has gained with managed access platforms in over 300 significant CAPEX and OPEX savings by optimizing the bandwidth
deployments of fixed and mobile networks worldwide. The addition and improving the management of the transport network through its
of IP/MPLS technology creates a robust, scalable and manageable testing capabilities and protection solutions. When positioned at the
platform for delivering next generation voice and data services. The base station site, the Tellabs 8600 system platform can aggregate
combination of IP and MPLS provides the predictable properties of different protocols, encapsulate them into MPLS Pseudo Wires and
ATM but at the lower cost of Ethernet based devices. Extending statistically multiplex them over various types of backhaul links.
MPLS into access and regional networks makes the entire network Mobile networks are evolving, and significant changes need to be
more controllable and efficient for transporting different types of made to enable new high-speed data services in the mobile RAN.
technologies. In a single platform, the Tellabs 8600 system supports the
technologies needed in mobile transport network evolution. It can
handle the transition in moving from 3G R99 ATM networks to 3G
R5 IP/MPLS and Ethernet networks in a cost-effective manner. At
the same time, the Tellabs 8600 system solution can still also carry
2G TDM traffic, providing a single platform for mobile network
transmission.
The Tellabs 8600 system platform optimizes network capacity by
using sophisticated Quality of Service and Traffic Engineering (TE)
tools to support the growth of mobile data services. By using
standards-based signaling and network control mechanisms
between the network elements, it is possible to reserve explicit
paths for time-critical, delay-sensitive or bandwidth-intensive
connections through the network. Less time-critical or bandwidth-
intensive connections can be allocated along shared paths, where
bandwidth and delay parameters are more flexibly defined. Wire-
Figure 1. The Tellabs 8600 systems position in service provider networks speed forwarding and full resiliency mechanisms are the keys to
very high-speed, predictable performance.
As is shown in Figure 1, the Tellabs 8600 system is positioned in The Tellabs 8600 system is designed for fixed and mobile network
the access network to provide four basic applications: convergence. In addition to the Ethernet connectivity, it can support
Mobile transport for 2G and 3G RAN any combination of mobile and fixed backhauling, such as E1, ATM
IMA, POS and channelized STM-1 interfaces, in the same network
Managed IP VPN and Ethernet services element.
Multiservice aggregation for existing Tellabs 8100 system and
Tellabs 6300 system services
Intelligent Management System
These applications are described further in the following chapters,
which outline the role of the Tellabs 8600 system in wireless and Because the number of network elements in the access and
wireline networks. In many of these applications, the Tellabs 8100 regional network is an order of magnitude larger than that in the
system and the Tellabs 6300 system solutions currently play an core network, effective network management is absolutely essential.
important role. These are expected to continue to remain in service This imposes additional scalability requirements for the
provider networks for many years to come. Integration between management system.
these Tellabs platforms is covered later in this document.
5
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
The Tellabs 8000 Network Manager is an integral part of the even with a small initial quantity of bandwidth and services. This is
whole solution. It provides a full set of tools based on an easy-to- because the cost of service entry is significantly lower than with a
use graphical user interface to manage element-, network- and traditional network elements, which can lead to reduced payback
service-level configurations. Since the operational management times and a quicker return on investment. With a distributed
expenses can be as high as 80% of the overall costs of the switching architecture, switching capacity is increased as new
network, this is a key feature of the overall solution. interface cards are added. This reduces the service entry cost,
The Tellabs 8000 manager offers significant advantages for the since the basic configuration is very simple, even with full element-
service provisioning process and management of large networks. and network-level redundancy features. Expanding the network to
Traditionally, service provisioning has been performed using support a larger number of services is achieved by simply adding
element management systems or even industry-standard new interface cards to the platform. Increasing the scope of the
command-line-based tools, which is often a complex and time- network to cover denser and larger geographical areas is as easy as
consuming process. Management complexity becomes much installing new network elements and follows the same pay as you
greater when the network grows and several technologies are grow principle.
involved. According to some service provider statistics, these tools
can result in a first-time success rate of just 60% for provisioning of
individual network elements. This low success rate leads to
significant costs and increased lead times in delivery of new
The Tellabs 8600 systems benefits
services. With the Tellabs 8000 manager, service provisioning is a
and role in wireless transport
highly automated process, with the system taking care of creating After years of speculation as to whether 3G evolution will ever
all of the parameters and configuring the relevant network elements. happen, network deployments have finally started and many
In the same way, making changes to services or network operators have already launched or are currently in the process of
connectivity is very straightforward and quick. Each connection or deploying 3G services. The most important 3G standards are UMTS
service can even be individually tested before launch or even while and CDMA2000. UMTS networks use WCDMA radio technology,
it is operational. For service assurance, the operator can see how and they are often referred to accordingly as WCDMA networks.
network or element interruptions are affecting individual services, This section of the document discusses how the Tellabs 8600
enabling much faster reaction to changes. Most importantly, with system can provide a solution for these networks.
the Tellabs 8000 manager, monitoring accuracy and management When determining the optimal solution and technology for a 3G
capabilities are not sacrificed, even when the network scales to tens network, the service provider should consider at least the following
of thousands of elements. This can give a huge competitive edge to issues:
a mobile operator with a network facing heavy growth.
The investment being made is for the long term, and the network
The Tellabs manager also operates with open interfaces enabling should be able to scale easily in the future.
data to be retrieved or sent to other Operational Support Systems
The solution must take into account the need for service and
(OSS) that are deployed in the service provider environment. All
network convergence, where multiple types of service can be
network- and service-related information is stored in a database,
offered on the same platform.
which is accessible using open Application Program Interface (API)
standards. The network management solution must support the business
processes and be able to lower the operational expenses
significantly.
Design for an Optimized Cost Structure
When compared to the alternatives, the Tellabs 8600 system offers
The network elements of the Tellabs 8600 system solution vary in an attractive and potentially long-term solution to the mobile RAN
size, which facilitates the best fit for every network location. The transport challenge. Typical RAN transport solutions on the market
platform is flexible, for various applications, and therefore it can today are based on TDM or ATM technologies. These are old
serve essentially all of the transport requirements in the access or technologies that have limited capacity and do not provide the long
regional network. The modular design of the Tellabs 8600 system term scalability and flexibility that mobile network evolution
platform provides the flexibility to equip each element with different demands. As IP eventually becomes the native transport protocol
capacities and interfaces as required. These are specified according throughout the mobile network, new data-rich services will drive the
to the service and network requirements, which typically vary with need for higher-bandwidth services to emerge. Also, with the need
the position in the network hierarchy. Depending on the changing for fixed and mobile network consolidation to reduce operating
requirements of the data communications infrastructure, the costs, service delivery using Ethernet and MPLS will become the
network capacity and interfaces can be adjusted and upgraded norm. Legacy technologies will not be able to support the
throughout the service life cycle. unstoppable move to converged network architectures.
With traditional network element solutions, the cost of separate The most significant benefits the Tellabs 8600 system solution
switching cards for each platform can become very significant brings to mobile RAN networks can be summarized as follows:
when one considers the overall cost of the network element. This is
A single-platform solution for 2G/3G architectures and beyond
especially true where some network elements are supporting only a
few customer interfaces. This can make the initial network A potentially long term investment with IP/MPLS support from day
deployment expensive for new services that may start off with low one
customer volumes but require the deployment of many network A single management platform for all Tellabs mobile solutions
elements to reach the target customer market. A highly integrated architecture with carrier-class operations and
With the Tellabs 8600 system, it is profitable build out the network low inventory cost
6
Single-platform Solution for 2G and 3G Otherwise, with both an ATM and an IP platform to look after,
In the move from 2G to 3G and beyond, the transport technology management and maintenance costs will remain high. The amount
moves from TDM and FR to ATM and eventually to IP. The use of of savings gained in terms of leased line rental is a highly market-
dedicated solutions for different transport needs is costly from both dependent figure and in certain markets can be huge.
a CAPEX and OPEX point of view. The Tellabs 8600 system can Once the Tellabs 8600 system solution is deployed close to the
handle the aggregation and transport of all of these protocols in Node-Bs in the access network, the transport infrastructure can be
parallel. This makes perfect sense at, for instance, new or existing further optimized with more cost efficient Ethernet interfaces. Also,
sites where 2G and 3G are collocated. The Tellabs 8600 system is the available bandwidth can be utilized in a more efficient way by
a vendor independent transport solution that can interoperate with allowing overbooking for data services. Ethernet interfaces can be
other vendors technology components in the BSS and RAN used to enable new Metro Ethernet services and Ethernet leased
infrastructure. And, most importantly, the transport network can be lines for backhaul. This use of Ethernet devices can further lower
managed even as a single entity. the total cost of the RAN.
7
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
The strict R99 ATM requirements do not go away with the Tellabs 8600 system network. In a similar way, dedicated paths
introduction of MPLS. But, by limiting ATM to the edge of the RAN, with specific priorities can be provisioned for any type of connection
the required level of efficiency and robustness can be achieved with across the Tellabs 8600 system network.
the deployment of a more modern access network. With a Tellabs Figure 4 below shows where the different Tellabs 8600 system
8600 system solution, the RAN network can simultaneously handle network elements can be positioned in the mobile RAN.
the access for any base station through each of the evolution
phases as illustrated in Figure 3.
8
Using the Tellabs 8600 system at the RNC site offers the service
provider the following potential advantages:
It improves the network scalability and allows more Node-B sites
to be controlled from one centralized RNC.
It reduces CAPEX by reducing the number of interface ports
needed on the RNC. This is as a result of performing the ATM
inverse multiplexing and VP/VC grooming on the Tellabs 8600
system platform.
It enables the use of lower-cost unchannelized interfaces at the Figure 6. Tellabs 8600 system at hub site
RNC site.
It can further reduce CAPEX since the same network element In summary, use of the Tellabs 8600 system at the hub sites can
can be used as part of the mobile core. bring the following business benefits:
The same platform used for 3G traffic aggregation can be used It allows a smooth network migration from TDM to ATM transport
for grooming 2G GSM traffic arriving on TDM links. and eventually to IP.
Bandwidth utilization is improved through traffic grooming and
Hub Sites network overbooking.
Positioning the Tellabs 8600 system platform closer to mobile base The solution is scalable for higher-bandwidth data services such
stations can yield additional business benefits. These include better as HSDPA.
bandwidth utilization, more options for backhaul technologies and ATM traffic can be monitored and tested over the whole
improved network management capabilities. The role of the hub site connection. This is particularly important when statistical gain is
is to aggregate different traffic streams, including voice and data, applied.
from the access network into the mobile core network over fewer Low-cost Ethernet interfaces can be used for implementing
connections. The introduction of a Tellabs-8600-like MPLS network Ethernet leased-line transport.
infrastructure can significantly optimize the bandwidth utilization,
Additional value-added services can be carried and managed on
enable use of cost-efficient Ethernet interfaces and reduce the
the same network infrastructure. These can include managed IP
number of leased lines required to carry the traffic. It also allows the
VPN and Ethernet services with differentiated SLAs.
traffic to be handled with finer granularity. Depending on the
bandwidth, port density and redundancy requirements, the hub site
can be implemented using the Tellabs 8660 Edge Switch, the Base Station Sites
Tellabs 8630 Access Switch or the Tellabs 8620 Access Switch. When the Tellabs 8600 system platform is used at the base station
The business case for utilizing the Tellabs 8600 system solution at sites, traffic can be consolidated onto a single access network
both RNC and hub sites is persuasive, and this solution can infrastructure, which brings savings in transport costs even in the
generate significant savings in both CAPEX and OPEX terms. Use of local loop. Additional savings are gained through statistical
the Tellabs 8600 system solution for the hub sites saves on multiplexing, which is significant when higher-speed data services
bandwidth costs, not only because of the number of lines required are brought into use. It is worth noting that, although there is only
but also due to the ability to move from Constant Bit Rate (CBR) to one physical connection, the different traffic streams can be
Variable Bit Rate (VBR) transport. This is the gain from statistical managed logically as independent connections with their individual
multiplexing, which makes sense with increasing and bursty data service quality requirements. Locating the Tellabs 8600 system unit
traffic. From some business case calculations with our customers, at the cell site, like in Figure 7, allows the access network to be
we have determined that distributing only one hub layer to the managed end to end so that modifications for instance, to the
network can yield more than 25% cost savings in E1 leased line capacity or service quality settings can be handled remotely.
costs. Naturally, if alternative, more cost efficient transport
When the Tellabs 8600 system is deployed to the cell site, there are
technologies are used, the percentage is higher. The Tellabs 8600
several alternative ways to arrange the access to the network.
system is flexible in this sense and offers various alternatives, such
Depending on the open infrastructure and service requirements, the
as Ethernet connectivity, which is becoming more and more
service provider can choose Ethernet, DSL or TDM. PDH and SDH
attractive (see Figure 6).
are the most popular alternatives today, since this infrastructure is
It should be remarked that in a converged network, customers can widely deployed and reasonable for voice transport. In the
be connected to other services over the same Tellabs 8600 system beginning, the 3G traffic is indeed mainly voice. However, when the
platform reaching the hub sites. In fact, the service can even be HSDPA-based services are launched, capacity requirements grow
implemented with the Tellabs 8600 system and related and other alternatives are likely to be worthy of consideration.
management system. Both of these improve the operators business
From a cost and availability point of view, DSL service is attractive
case and service manageability.
for connectivity. Because the base station can separate voice and
data traffic, voice can be directed to the TDM transport system and
data to DSL via Ethernet. This seems to be a cost-effective set-up.
For instance, DSLs cost advantage over E1 when backhauling
HSDPA data traffic in the local loop is about 50%. In the context of
RANs transport as a whole, even 59% cost savings can be
achieved over ATM-based RNC application.
9
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Another inviting option is to utilize the Metro Ethernet networks, links and rebuilds all of them at the selected interfaces of another
which are already widely deployed. Also, the bandwidth cost is element. This not only makes the process fast but also facilitates
typically significantly lower than that of traditional TDM networks. In correct configurations for all of the related network elements. In this
using Ethernet transport in the RAN, it is important to make sure context, the operator can even verify the connectivity remotely with
that the synchronization and service quality management can be the management system tools.
arranged properly. With Tellabs 8600 system functionality, these The Tellabs 8000 manager can offer the service provider the
important elements are well supported. Synchronization is following advantages:
discussed later in this document.
Fast response to network changes with remote configuring,
automated provisioning and testing
A single management solution for multiple access technologies,
including TDM, ATM, FR, IP and Ethernet
A carrier-class network manager built on the basis of service
provider needs, supporting 30,000 network elements and tens of
concurrent users
An easy-to-learn and -use management system with a graphical
user interface that hides the network complexity from the user
Potentially significant cost savings for operators through provision
of management for multiple technologies, remote management
and fast troubleshooting
Figure 7. Tellabs 8600 system at cell site
Network Convergence
The Tellabs 8600 system is very flexible, allowing the service
The boundaries between fixed and mobile services and networks
provider to use any of the mentioned technologies for access.
are vanishing. Deregulation is opening up new opportunities for
Naturally, it gives the service provider the choice of using the
service providers. The resulting competition is driving every service
platform for some base station sites while using traditional SDH
provider to extend its service portfolios.
platforms for the last-mile access for other sites. This, of course,
depends on the bandwidth and service requirements, plus the Ideally, the same network infrastructure and the same management
growth expectations for each area. system should be capable of handling all of these different services.
The Tellabs 8600 system is designed exactly for this purpose and
For a base station access solution, the Tellabs 8600 system
uses MPLS for convergence, as shown in Figure 8. Convergence
provides the following main benefits:
can be executed at various levels and depends greatly on the
It can aggregate different 2G- and 3G-related protocols and traffic organization boundaries. One way to segregate the various levels of
streams on the same platform. convergence is:
Connection and service parameters can be changed remotely via Mobile convergence in terms of providing 2G and 3G services
the network management system. with the same platform
New services can be implemented on the platform to attract new Fixed and mobile convergence where the service provider not
customers and increase revenue streams. only offers mobile services but also, e.g., produces broadband or
Cost-efficient and scalable Ethernet links can be used for business services, or just transport from a unified infrastructure
backhauling the traffic into the RAN. Service convergence, of which the IMS infrastructure and the
same service offering independent of the end-user device is a
Efficient Management in Mobile Networks good example
Mobile networks are by definition very dynamic in nature and are The access network is the most expensive part of the service
growing especially dramatically now. New base stations are often providers overall infrastructure. Therefore, the use of common
constructed, and bandwidth links are frequently upgraded or multiservice-capable elements and flexible management tools in the
added. When the network is first built, the sooner it can be put into access network offers the best potential savings for service
service, the sooner the service provider can turn on its revenue providers.
stream. Network management has a critical role in all of these
processes. The sophisticated tools of the Tellabs 8000 Network
Manager provide major benefits for the service provider throughout
the network life cycle. They support day-to-day operations
throughout the continuous evolution of the network, providing end-
to-end connectivity management.
Managed re-hosting capability is one excellent example of the
Tellabs 8000 managers competencies. When a selected group of
connections must be moved from one location to another, the
operator can with one command execute the whole operation. The
Tellabs 8000 manager automatically tears down all of the selected
10
The Tellabs 8630 switches were deployed to the aggregation sites
to allow utilization of a single platform for both 3G traffic and
residential DSL services. This lowered the CAPEX related to the use
of several devices at the hub sites and optimized the costs related
to the backhauling. With the help of the Tellabs 8630 switches,
operators were able to utilize cost-effective Ethernet backhauling for
RAN and solve synchronization challenges often related to ME
backhauling. The Tellabs 8600 system solution offered superior
QoS features and end to end resiliency as required in large-scale
Metro Ethernet backhauling cases. There are already hundreds of
Tellabs 8600 systems deployed in this network.
11
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
12
Potential benefits provided are: tunnel is terminated at the edge of the MPLS network domain,
Minimized cost of bandwidth where the label is removed and the TDM traffic is passed to the
destination element or out into the TDM network. This process is
One platform for various traffic needs and services (cost-
illustrated in Figure 12. All TDM traffic is carried transparently
efficiency in terms of investments and maintenance)
through the MPLS domain, and bandwidth can be reserved for
Improved management, fast response to network growth and each LSP that the Pseudo Wires traverse.
ease of topology changes
Readiness for convergence and flexibility for various technologies
A cost-efficient solution
13
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Trafc class Conversational RT Streaming RT Interactive best effort Background best effort
Fundamental charasteristics Preserve time relation (variation) Preserve time relation (variation) Request response pattern. Destination is not expecting the
between information entities of between information entities of Preserve payload content. data within a certain time.
the stream. conversational the stream. Preserve payload content.
pattern (stringent and low delay).
Example of the application Voice Streaming video Web browsing Background download of emails
the connections can be tested to ensure that they deliver the Service Quality Management
desired functionality. The service provider can also monitor each Current mobile services are predominately voice-based, a situation
connection in the Tellabs 8600 system network in real time and get that is likely to prevail until the beginning of UMTS deployments.
statistics and faults mapped to individual connections. This helps However, new types of data and multimedia services will become
the service provider to understand, for example, the impact that a more and more popular. This mixture of voice and data services will
network fault can have on specific connections or services. set new service quality requirements for the network. It will need to
be able to handle these requirements in an efficient and appropriate
Synchronization Management manner.
Synchronization plays an important role in mobile networks since The UMTS specifications define four service classes, which are
the base stations must be well synchronized to ensure good voice listed in Table 1. Each service within a given class has a common
quality and manage the call hand-overs. set of characteristics.
GSM and WCDMA networks typically obtain synchronization with The transport network must be able to implement these service
the cell site from the E1 or T1 leased line or the microwave link to classes in the appropriate way throughout the whole network. They
which they are connected. When the connectivity is TDM, can be supported using any of various transport technologies or
synchronization is not an issue. However, where Ethernet even with a combination of them.
connectivity is concerned, timing could become problematic. The Tellabs 8600 system has extensive support for traffic quality
Traditional Ethernet networks do not have the ability to provide a management. Traffic forwarding inside the network element is
clock-based signal to a cell site. Standardization bodies are performed at the hardware level to facilitate wire-speed
currently working with this issue, and some candidates are already performance for all traffic. For high-priority traffic, bandwidth can
present. These are IEEEs 1588 Precision Time Protocol (PTP) and be reserved through the network using the RSVP-TE signaling and
Synchronous Ethernet. IEEE 1588 was originally specified for Local connection admission control (CAC) protocols in the elements along
Area Networks for use with testing. The second version, which adds the signaled path. These protocols facilitate that the requested
support for the WAN environment, is still in progress. Synchronous connection can be established without disturbing the existing traffic
Ethernet is described in ITU-T G.8261, which specifies the method and that the reserved path is always available for this connection.
of distributing the synchronization via the Ethernet line signal. Tunnels run over MPLS LSPs, which can be configured to carry
Tellabs follows closely the standardization progress and has traffic for one QoS class or for a mixture of QoS classes. Each LSP
implemented the Synchronous Ethernet. PTP is intended to be can be configured with different parameters for path protection and
implemented soon after the specification exists. With the Tellabs bandwidth reservation depending on the type of traffic it is carrying.
8600 system, the synchronization can also be relayed to the cell The Tellabs 8600 system implements QoS management using IP
site by means of adaptive timing, where a TDM interface in the DiffServ and maps other protocols to the DiffServ traffic classes to
Tellabs 8600 system element can obtain synchronization through a provide end to end service quality.
TDM Pseudo Wire. It is worth mentioning that Tellabs 8600 system
For ATM service classes, the Tellabs 8600 system platform
elements are, in fact, part of the synchronization network so it can
supports CBR, VBR, UBR+ and UBR service categories. Traffic
distribute the clock to other elements in the network.
forwarding, queuing, scheduling and shaping is performed on a VP/
With CDMA networks, the synchronization and packet network VC basis. When ATM traffic is transported across an MPLS network,
issue does not arise from the transport point of view since CDMA each service category is tunneled through an MPLS LSP with the
uses GPS receivers at each cell site. This is, naturally, an option equivalent DiffServ class. Typically, CBR is mapped to EF and UBR
also with WCDMA networks, but it is not widely deployed. More to BE, whereas VBR and UBR+ are mapped to the chosen AFxy
often, since the 2G and 3G base stations are collocated and SDH is class.
present as well, one could obtain the synchronization through SDH.
As described for the service provider, Tellabs offers various options
for arrangement of the synchronization in the network and therefore
removes the barriers from migration to packet-based backhauling.
14
Network Resilience provides a lower-cost, more flexible and scalable alternative to
High network uptime is critical for a service provider. Building traditional leased lines. Large corporations, which have their own IT
resilience comes at a cost that is highly dependent on the departments in place, often prefer this type of service since they
mechanisms used to improve the network reliability. Therefore, it is wish to retain control of the routing network inside their company.
vital that the service provider specify the reliability needed. High- Using MPLS, the Tellabs 8600 system can deliver Ethernet services
priority services deserve faster protection mechanisms, whereas in two ways:
lower-priority ones can rely on slower alternatives or possibly no As a point-to-point Virtual Private Wire Service (VPWS)
protection at all.
As a multipoint-to-multipoint Virtual Private LAN Service (VPLS)
With the Tellabs 8600 system, connections can be protected in
Due to its simplicity and similarity to traditional leased lines, VPWS
different ways. Obviously, individual links can be protected between
is currently the predominant service provider offering. VPLS has
two network elements. But this same level of protection would apply
gained much interest recently but is still in its infancy in terms of
to all traffic classes using the link. MPLS provides a protection
technology and network deployments. However, it offers an
mechanism that can be used to enable much finer granularity.
interesting alternative for current deployments.
Using these protection mechanisms, individual LSPs can be
protected across the network or even along a selected path in the For example, LAN interconnection services often use a hub-and-
network. For instance, only paths that are carrying certain traffic spoke topology in which the headquarters acts as the hub site. This
classes could be protected across the network through allocation of kind of network can be created easily using VPWS point-to-point
dual paths. This could represent only a fraction of the interface Ethernet tunnels. However, each VPWS tunnel is terminated at a
capacity and makes efficient use of the available bandwidth. By separate port on the hub site switch. VPLS can provide a better
contrast, paths with lower-priority traffic classes can be protected alternative since the customer only needs one physical interface to
such that the recovery time in the event of failure can be a bit the service and still provides any-to-any connectivity between the
longer, whereas Best Effort traffic normally does not need any sites. With VPLS, the service provider network emulates a big
protection mechanisms and can tolerate some service breaks in the Ethernet switch from the end-customer point of view. All the sites
event of a network outage. look like they are physically on the same LAN, making service
cheaper to deliver and easier for the end user to manage.
IP VPN Services
The Tellabs 8600 system in wireline transport
An IP VPN service can be considered the next layer of value-added
The Tellabs 8600 system is adaptable to various applications and
service over and above basic Ethernet connectivity since it adds
enables mobile operators to broaden their service portfolio into
routing management to the service. But IP VPN services can also
wireline services. A wide range of interface technologies with
provide the platform for more value-added services, which can give
service intelligence, plus a superior network management system,
access to additional revenue and greater profitability for the service
enables the service provider to build a single platform that meets
provider.
both current and emerging business needs. A single upgradable
platform and one network management system is much more cost- IP VPNs are particularly attractive to customers with limited IT
effective than building parallel platforms to satisfy different service support skills. They are also requested by companies for whom IT is
needs. not a core competency and who wish to outsource as many
services as possible.
The Tellabs 8600 system is highly flexible. It can be used to
connect end users to multiple services with very different The Tellabs 8600 system implements IP VPNs based on RFC
requirements simultaneously. Multiservice delivery is more efficient 2547bis. This is the IETF standard that describes a mesh service
for the service provider since the same physical network and model for LAN interconnection and makes use of the Quality of
business management processes can be applied to many services. Service and Traffic Engineering capabilities offered by MPLS. This
IP VPN method uses a peering model in which the customers edge
In addition to wireless applications, the three main wireline service
routers exchange their routing messages with the Provider Edge
applications that can be implemented with the Tellabs 8600 system
(PE) routers. MP-BGP is then used within the service provider
are:
network to exchange the routes of a particular customer VPN
Ethernet services among the PE routers that are attached to that VPN. This is done in
IP VPN services a way that ensures that routes from different customer VPNs remain
Broadband Internet access distinct and separate, even if two VPNs have an overlapping
address space. The PE routers distribute the routes from the CE
In a typical service provider network, all of these services can be routers to the other CE routers in that particular VPN.
offered to satisfy the needs of different customer segments or for
the operators internal use. Tellabs believes that it makes the most This IP VPN model scales well in large customer networks and
sense to utilize the same access and core infrastructure for supports different network topologies, from hub-and-spoke to full
implementing all services. mesh. Customer routes are propagated in the service provider
network with the help of the MP-BGP routing protocol, which
automatically provides updates of the correct VPN routes in the
Ethernet Services respective PE routers. The Tellabs 8600 system introduces a similar
With an Ethernet service, the customer manages the end-to-end hierarchical model to that specified for VPLS services into the IP
routing and the service provider simply provides Ethernet VPN application. This is discussed later in this document, along
connectivity between each customer site. In most cases, this with a comparison with the standard IP VPN models.
15
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
16
IP VPN Services Inefficiencies arise from operation of multiple network
In the traditional IP VPN service deployment model, service technologies, such as TDM, ATM, FR or Ethernet in the access
implementation is the responsibility of the PE router at the edge of network and IP/MPLS in the core.
the IP/MPLS core. All of the intelligence needed for the IP VPN Difficulties occur in mapping IP and Ethernet services to ATM or
service resides in that router. The CE router is normally connected FR service models in the access network.
to the PE via a point-to-point connection, regardless of the network To address these limitations, Tellabs has created a new distributed
technology. The CE router is usually an ordinary router, owned by architecture to support IP VPN services, which makes scaling a
either the service provider or the end customer. network easier and faster. The architecture takes the hierarchical
model introduced by the IETF for VPLS services and extends it to
the IP VPN, a natural step since networks often will be used to
deliver both types of service. The Tellabs 8600 system can be used
to deliver the standard IP VPN model as well as this distributed
version. In practice, the two models are likely to coexist in the same
network: larger areas will be implemented with the new distributed
model and smaller areas, with limited growth expectations, using
the existing flat model.
Figure 14. Traditional IP VPN deployment model In the distributed model, the same procedure and protocols that
were used in the core between the PE routers are applied in the
Figure 14 shows the basic working principles of an IP VPN based access domain. In routing terms, distributing the network improves
on RFC 2547bis. PE routers are located at the edge of the service the management, scalability and stability of the network. Traffic
provider IP/MPLS core, and traffic from the CE routers is Engineering and protection mechanisms can be implemented
backhauled to the PE router using any of the available access optimally within the regional networks, regardless of the core
networks. The PE router dynamically peers with the CE router using network configurations and set-up.
BGP, OSPF or RIP routing protocols. Alternatively, the service
provider can define a static route in between the CE and PE. The
PE router separates the different customer VPNs into logical VPN
Routing and Forwarding (VRF) tables. These can be seen by only
the corresponding customer part of the VPN. Customer VPN
addresses are propagated over the core network using the MP-
iBGP routing protocol. This inserts the VPN routes in the correct
VRF table corresponding to the VPN on the PE routers.
Usually in a large or growing network, Route Reflector units are Figure 15. Distributed IP VPN enabled with the Tellabs 8600 system
used for BGP communication and scalability. Instead of having a
full mesh of BGP communication between all of the PE routers, The distributed IP VPN model is shown in Figure 15. PE routers are
each PE establishes a session with a Route Reflector, which divided into U-PE (user-facing PE) and N-PE (network-facing PE) as
distributes the routes to the relevant PEs. Normally, the Route is done in the hierarchical VPLS specification. The U-PE router has
Reflector is duplicated and an additional session is established from a direct connection at IP level with the CE. The N-PE is at the edge
a PE to the secondary Route Reflector. of the core and communicates with the other N-PE routers across
In this deployment model, a single PE router is typically responsible the core as in the existing flat model. MP-eBGP is used for VPN
for offering services to a large number of end customers. The route distribution in between the U-PE and N-PE as in the standard
processing power and reliability of the router are therefore critical to model. Where there are Tellabs 8600 system platforms or other IP/
the operation of the network. Enlarging the network often requires MPLS routers in the network between the U-PE and N-PE, they act
adding a new PE router: a significant financial and operational as simple MPLS Label Switch Routers (LSRs) just as P routers do in
investment that needs to be cost-justified on the basis of potential the core. They are indicated as P-a (P in access network) in the
customers and traffic. When some level of redundancy is required, diagram. P and P-a routers do not need to understand anything
the cost can become even more significant. about the VPNs since they only transport traffic on the basis of the
In summary, the limitations of the current deployment model are outer labels. It should be noted that, in a typical network, one
that: element has several roles. For example, for one service the router
can be a U-PE and for another a P-a router.
Scalability is limited by the cost and complexity of introducing a
new PE router. The limitations of the traditional IP VPN model can be addressed
with the distributed model. Full-mesh connectivity is required only
The cost per bit in the access network is relatively high since the
between the N-PE elements in the network. Also, the addition of a
legacy network technologies are not optimized for transporting
new U-PE to the network is more straightforward: it only needs
bursty data traffic.
connectivity within the access or regional network. All of the
Metro Ethernet deployments lack the required QoS capabilities customer VPN routes are communicated in a consolidated manner
and hence require heavy over-provisioning. in the regional network between U-PE and N-PE routers using a
End-to-end service management and monitoring is a challenge single MP-eBGP session. Where customer sites are in the same
across the disparate platforms and technologies currently region, traffic can be locally routed without loading the core
deployed, which often leads to SLAs covering only the PEPE network. Thanks to the element architecture, network growth can
part of the service.
17
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
be achieved with incremental investments making it more The Tellabs 8600 system in combination with its accompanying
economically attractive. Provisioning services with versatile access nodes supports many types of customer network access
resilience mechanisms over the access network or at the edge of technologies, including Ethernet, TDM, DSL and wireless access.
the core adds marginal cost in the distributed model. And MPLS Customer networks can be distinguished from each other by a
protections, dual homing and Traffic Engineering can be used in the combination of port, channel, circuit, VLAN ID and MPLS label at
regional network since it is a traffic engineered domain on its own. the Tellabs 8600 system interface used to connect to the chosen
The basic principle in the distributed model is to move the access network.
intelligence away from the core and closer to the customer Customer traffic entering the network is directed to the appropriate
demarcation point. The new access domain utilizes the same service on the basis of service-specific policy settings for the Tellabs
procedures that are traditionally used only in the core. In practice, 8660 switch. For example, certain VLANs can be forwarded to a
this has the added benefit of removing the single point of failure at VPWS while others are directed to an IP VPN service. A customers
the edge of the core network. This is all made possible through the broadband Internet access traffic can be directed to a dedicated
cost-efficient architecture of the Tellabs 8600 system. service network using:
The management components of the Tellabs 8600 system can IP routing where the customer Ethernet VLAN or ATM VC is
automatically set up the required LSPs and parameter terminated at an IP router. Traffic conditioning based on the
configurations for the network elements along the VPN route. A CE customer SLA and IP address relaying from the DHCP server is
router or switch in the end users LAN is connected to a Tellabs performed at the first Tellabs 8600 switch.
8600 system U-PE device either on customer premises or at the PW tunneling using either the Ethernet/VLAN ID or the ATM VC,
Local Exchange (LE) site, typically with an Ethernet interface. The from the DSLAM to the BRAS.
service provider connects all of the sites, which are part of a
Figure 16 shows multiple service provider networks with a
specific VPN, according to end user requirements. The service
centralized BRAS service selection gateway. These services are
provider also sets all of the QoS parameters for each VPN according
provided to customers across a regional network.
to the end-user requirements. With the Tellabs 8600 system,
different traffic types can be classified at the customer demarcation Traffic leaving the network toward the customer is combined from
point before entering the operators network. Another option is to do the multiple service networks. It is then queued and shaped
this at the first LE site using an Ethernet aggregation switch such as according to the service-specific policies at the Tellabs 8660 switch.
the Tellabs 8606 Ethernet Aggregator. Alternatively, this function Packet replication for predetermined groups is performed to support
can be performed by way of a CE router located on customer multicast services such as IPTV. Local content servers and caching
premises. This might be the preferred solution in cases where high can also be supported for additional service networks.
bandwidth fiber is used for the local loop or where true end-to-end
management is not an issue. All of the customer traffic is
transported over MPLS LSPs in the regional and core networks.
This results in a single LSP in the core network and separate LSPs
in the regional networks on either side of the core.
In summary, the benefits of the distributed Tellabs 8600 system in
delivering IP VPN services can be:
Improved scalability: a single PE takes care of a larger number of
customers and customer routes are communicated more
efficiently with one BGP session across the access domain.
A cost-efficient entry point for new networks: the system gives the
option of starting with limited services and gradually extending to
a large service delivery platform.
Operational efficiency in service provisioning and upgrade Figure 16. Tellabs 8600 system in broadband service aggregation
processes: the Tellabs 8000 manager enables fast service
creation. It is easy and accurate to use since the operator does In a next-generation broadband access architecture, the primary
not need to configure each element individually or have a deep application of the Tellabs 8600 system is to support multiple
technical understanding of each network element. services such as data, voice and video on a converged regional and
Better scalability of MPLS Traffic Engineering: with fewer PE access infrastructure. Quality of Service and bandwidth usage can
routers in the distributed solution, there are fewer tunnels to be controlled in the metro network, and both business and
traffic engineer over the core. residential services are supported by the same regional and access
infrastructure.
Broadband Service Aggregation
All of the applications supported by the Tellabs 8600 Managed
Edge System can benefit from the platforms broadband service
aggregation capabilities. In provision of Ethernet, IP VPN, Internet
access or value-added services, network traffic can be separated
and aggregated at the edge of the network according to the specific
service needs.
18
Managed migration path from the Tellabs 8100 and Tellabs when one is building a network connection, gathering service level
6300 systems data or troubleshooting the network.
In todays telecommunications environment, it takes time to Integration with third-party OSS systems is also faster and easier,
transition the network to new technologies, services and standards. since only one platform instead of two or three needs to be
Current production networks must operate in parallel with new integrated. Maintenance of the management platform is also much
developments in order to maintain revenue streams and maximize easier and less costly because there are fewer components to look
the profitability of the existing networks. after.
Tellabs has made a number of enhancements to its existing
platforms to support a smooth transition to next-generation IP- and Migration in Wireless Networks
Ethernet-based services and networks. In practice, this means that In wireless transport networks, a combination of the Tellabs 8100
new services can be introduced quickly and easily with small and the Tellabs 6300 systems is usually deployed for GSM
incremental investments while the established business processes networks. When starting to deploy 3G networks, the service
are continuously maintained. This is especially important for the provider has two options: to invest in new Tellabs 8600 system
Tellabs 8100 and Tellabs 6300 system solutions, which have a elements or to upgrade the existing elements to provide more
significant global installed customer base with extensive network capacity in the network. In high-density areas, it often makes sense
coverage in both wireline and wireless networks. to start immediately with the Tellabs 8600 system, since it is
Ethernet interfaces and switching are already available as add-ons optimized for ATM and IP and scales easily for future needs. In
for the Tellabs 8100 and Tellabs 6300 system platforms. An areas where the bandwidth capacities are not expected to grow
Ethernet interface is the most cost-efficient and flexible way to build rapidly, it may be sufficient to upgrade the existing systems. Both of
connectivity today towards IP-capable devices. With Ethernet these scenarios, as shown in Figure 18, give the service provider
switching, the TDM platform can be utilized in the most efficient various options for building the required connectivity. Both 2G and
manner and with more flexible connectivity for multisite networks. 3G traffic can be transported over the Tellabs 8100 and Tellabs
The service provider can choose the best option from among E1, 6300 system units toward the BSC and RNC site. The Tellabs 8600
STM-1, Fast Ethernet and gigabit Ethernet when connecting to its system solution can also transport both 2G and 3G traffic; hence,
Tellabs 8100 and 6300 system elements. the operator can choose the most economically feasible network
To make the transition to IP/MPLS as seamless as possible for configuration for each area in the wireless transport network.
service providers, Tellabs has ensured that even though the Tellabs
8600 and Tellabs 8100/6300 system platforms are based on
different technologies, they share a common management system,
as shown in Figure 17.
Figure 18. Combined 2G and 3G network with the Tellabs 8100, Tellabs 6300
and Tellabs 8600 systems
Figure 17. A single management solution for Tellabs networks Mobile networks are growing continuously, and setting up the new
cell sites and building connectivity quickly for them is a challenge
especially in cases when many technologies are involved. The
The Tellabs 8000 manager provides a single database with
Tellabs 8000 manager makes it possible to bring the new sites into
integrated network management tools providing the same look and
use quickly or remotely manage other network and connectivity
feel for service management functions. The service provider can
changes, which can be caused by network growth or maintenance.
save on CAPEX and OPEX by continuing to use the same servers
Connections starting from the Tellabs 8100 portion of the system
and operational environment. The same management logic is
solution and ending at the Tellabs 8600 system component can be
retained, which helps customers to learn quickly how to use the
provisioned and end to-end tested with the management system.
new tools and to maintain the same business processes. Training
This is something that normally would require totally separate tools
for service personnel is therefore kept to a minimum. Each service
and management systems and procedures with no interaction in
and connection or group of connections can be provisioned,
between. A technologically complex network becomes simple with
managed and monitored end to end regardless of the termination or
the intelligent management software.
origination platform for the service. This can be a major benefit
19
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Migration in Wireline Networks Access equipment typically has less capacity than aggregation
Figure 19 shows the role of the different Tellabs platforms in a nodes deployed in the regional network. The Tellabs 8620 and the
wireline service provider network. The integrated Tellabs 8100/6300 Tellabs 8630 switches are designed primarily for small hub sites.
system platform is generally used as an access platform for lower- The Tellabs 8660 switch is more suited to deployment in the
speed IP VPN, Ethernet service or Internet access tails ranging from regional network for aggregating traffic from the RAN network to the
n x 64 kbps to 10 Mbps, whereas the Tellabs 8600 system platform RNC site. Compact and cost-efficient, the Tellabs 8605 Access
is optimized for connectivity and services at speeds of 10 Mbps and Switch and the planned Tellabs 8607 Access Switch are optimized
above. for cell site access. The network elements are based on the same
technology platform, which facilitates interoperability. The managed
access solution may be complemented with a compact Ethernet
switch that can be managed similarly to all of the other Tellabs
8600 system elements.
20
point connections. Switching is performed on the LCs, while the LCs can be easily removed and reconnected with the help of hooks
CDC provides the information that the IFCs require for making their placed at the top and bottom of each card. In the lower part of the
forwarding and switching decisions. network element there are cable ducts, forced cooling modules with
To increase the flexibility and scalability of the chassis, every line filters and an air intake gap. Fan trays are also controllable via the
card can be loaded with up to two Interface Modules as different backplane.
combinations. Several interfaces support multiple protocols, which The Tellabs 8660 switch can operate at temperatures between 5
make usage very flexible and allow having a mixture of protocols C and 45 C, which is within the typical climate range of a telecoms
even within one interface. As a result, the entry cost of the device is equipment room.
very low compared to traditional, centralized switch-based
architectures. The backplane itself is passive and contains no active
Tellabs 8630 Access Switch
components.
The Tellabs 8630 switch is a more compact version of the Tellabs
This distributed switching architecture gives the following
8660 switch and has physical dimensions of 440 x 230 x 286 mm
advantages:
(W x H x D). Its smaller size makes it ideal for medium-sized hub or
It simplifies the card/slot placement rules and can radically traffic aggregation sites in the mobile RAN, where the compact
decrease the entry cost of the Tellabs 8660 switch network physical size saves on valuable rack space. The element is normally
element. installed in a standard 19 rack. All cards are positioned horizontally
It eliminates the potential for a single point of failure in the so that the power and control functions reside in CDC cards in the
element. bottom and top slots for a fully redundant configuration. In between
It provides more space for Line Cards that can deliver services these, four slots are available for LCs. These can be equipped with
and revenue. IFMs as in the Tellabs 8660 switch. The same cards and interfaces
can be used in both the Tellabs 8660 and Tellabs 8630 switch
Each LC contains an Interface Module Concentrator (or IFC, a sort
products, making management of spares easier. When all four slots
of baseboard for an LC) plus up to two Interface Modules (IFMs)
are used for interface cards, the element provides a maximum
and provides a bidirectional interface capacity of 3.5 Gbps. The
forwarding capacity of 14 Gbps. The functionality and flexibility of
total capacity of the node depends on the number of populated
the unit are identical to those of the Tellabs 8660 switch system.
interface slots. When the node is fully loaded, the total bidirectional
Figure 22 below shows the front view of the Tellabs 8630 switch.
interface capacity is 42 Gbps. For future scalability, the backplane
can handle 10-Gbps Interface Modules, such as those for 10-Gbps
Ethernet or STM 64/SONET 192c. Due to the hardware-based
design, all traffic can be forwarded at wire speed.
21
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
services in the access network allows the service provider to deliver that are part of the Tellabs 8000 manager.
more services using the same network and hence increase The elements have an identical appearance, the only difference
profitability. These different traffic streams can include mobile being the interface offering. Both products are configured with two
network connections as well as business services on the wireline gigabit Ethernet interfaces and additionally a fixed number of T1/E1
side. Each traffic stream can be mapped into specific tunnels or and Fast Ethernet interfaces. The Tellabs 8605 switch, shown in
service instances by the Tellabs 8620 switch. This allows the traffic Figure 24, has a combination of 16 T1/E1 and two Fast Ethernet
to be identified and delivered with full end-to-end security. ports, whereas the Tellabs 8607 switch has a combination of eight
T1/E1 and eight Fast Ethernet interfaces. The power supply is
selectable between 24 VDC, 48 VDC and AC. Due to their typical
role in the mobile network next to cell sites, the switches are
environmentally hardened so that they sustain a wider temperature
range than normal telecoms equipment.
Figure 23 shows the front view of the Tellabs 8620 switch. The unit
is a compact and modular network element with a bidirectional
interface capacity of up to 3.5 Gbps. It integrates all of the common
logic, such as power, switching and control functions, within the
same element. The two IFM slots can be equipped with a variety of Figure 24. Tellabs 8605 switch
IFMs. The Tellabs 8620 switch uses the same range of Interface
Modules available in the Tellabs 8660 switch and the Tellabs 8630 Tellabs 8606 Ethernet Aggregator
switch. The interfaces may be customer-facing or for connecting the
The Tellabs 8606 aggregator is a compact Layer 2 switch that can
element to the network.
be managed using the Tellabs 8000 manager in the same manner
The service capacity of the Tellabs 8620 switch has limits that can as all of the other Tellabs 8600 system network elements. It is
be flexibly specified by the service provider. The service provider specifically targeted at network applications where traffic from
can easily upgrade and test each service and individual connections multiple end users must be aggregated to the Local Exchange site
by using the management system when needed. This maintains full using Ethernet links over a fiber connection. As is shown in Figure
control of the network capacity and provides the capability to 25, the main applications are:
charge accordingly. It also allows upgrades to be kept under control.
MTU access aggregation applications
The network interface must be carefully chosen so that it suits both
the infrastructure and the capacity requirements, at installation time Port extension shelf for Tellabs 8600 IP/MPLS routers
and in the future. Various types of networking technologies are The switches are simple to configure, and services can be fully set
supported by the Interface Modules. up and managed using the Tellabs 8000 manager. Where multiple
Like all other Tellabs 8600 system network elements, the Tellabs customers each with partially filled interfaces need to be connected
8620 switch offers a diverse range of network protection features, to the network, these Ethernet aggregators can offer a very low-cost
such as LSP Fast Reroute, to meet even the toughest availability solution.
requirements.
22
The Tellabs 8606 aggregator (see Figure 26) supports 24 100Base- The BRAIN handles all of the routine functions for data forwarding
TX Fast Ethernet ports and 4 1000Base-X gigabit Ethernet ports, of and QoS procedures and enables the Tellabs 8600 system to
which two can be replaced with optical SFP connectors. The switch operate at wire speed. This intelligent design plays a significant role
is designed to act as a multiplexer where the aggregate bandwidth in delivering network resiliency mechanisms. It helps service
is well below the maximum bandwidth of the link. This avoids providers to build demanding, QoS-aware services with a high
network congestion along with any consequent impact on service degree of flexibility. A unique feature of the BRAIN is the inclusion
quality. At the first Tellabs 8600 system switch element in the of a test generator with which the service provider can test the
network, all traffic can be classified and any required QoS-related service or connection functionality. Test metrics supported include
procedures initiated. connectivity, delay, delay variance, packet loss and throughput.
These testing procedures can be executed with ease using the
Tellabs 8000 manager.
This chapter describes some of the important architectural features The control plane implements the IP stack functionality, the routing
that are implemented in the Tellabs 8600 system platform protocols and the configuration function for all routing and service-
elements. related parameters. The actual traffic forwarding is performed by
the hardware-based forwarding plane; any traffic that cannot be
handled by the hardware is forwarded to the control plane software
Hardware-based Forwarding Plane for processing.
The Tellabs 8600 system has been designed to support a wide The control plane software supports both IPv4 and IPv6. In order to
variety of services, from business connectivity to mobile support QoS aware services and connections, it includes a range of
transmission and even residential service aggregation. Each of routing and signaling protocols plus traffic extensions. For example:
these services has very different requirements, necessitating a For IP routing, the system supports static routing, OSPF(-TE), IS-
combination of hardware-based implementation and a distributed IS(-TE) and (MP-)BGP.
architecture for functions such as forwarding. Without a hardware-
based forwarding plane, it is not possible to satisfy the wide range For MPLS signaling, either LDP or RSVP-TE can be used to build
of requirements applying for different types of connectivity services. LSPs through the network.
For instance, traffic-aware QoS treatment, specific protection The basic IP stack functions include IP forwarding, TCP, UDP,
systems and guaranteed bandwidth per application cannot be ICMP and ARP modules.
handled efficiently at software level alone; the volume of packet The control plane supports hot swapping, which means that any
processing needed would overload a central-processor-based card can be changed without the need to power down the entire
environment. unit. The configuration information from all of the Interface Modules
To achieve the best combination of performance and cost- is stored on the CDC. If one Interface Module should fail, it can be
efficiency, all router elements that are part of the Tellabs 8600 replaced with a new one, which automatically copies the
system solution rely on the same core architecture. To implement parameters from the control card. New firmware versions can be
this architecture, Tellabs has designed a custom ASIC: the downloaded easily to the control and line cards without disturbing
Broadband Routing ASIC for IP Networks (BRAIN). This is the the traffic forwarding. The CDC software can be upgraded without
central building block for all of the customer premises equipment disruption to the current traffic and services.
and plug-in units. Within each network element, the BRAINs are The Tellabs 8600 system software supports graceful restart
connected in a full-mesh topology: the BRAIN in each plug-in unit mechanisms for OSPF, IS-IS, LDP, BGP and BGP with MPLS labels.
is connected to every other plug-in unit using point-to-point When two redundant CDCs are present, they copy data between
connections through the backplane. The architecture also allows the each other while operating. Should a CDC fail, graceful restart
use of general network processors to provide differentiated packet allows traffic forwarding to continue. The protecting CDC does not
processing for added flexibility. maintain a synchronized set of routing tables; therefore, the routing
23
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
tables cannot be used immediately in a failure situation. Instead, Currently, the following Interface Modules are available for the
the CDC obtains the up-to-date routing information from the Tellabs 8600 system platform:
network. Eight-port Ethernet 10/100Base-TX
IP routers are susceptible to various types of denial of service (DoS) Eight-port Fast Ethernet 100Base-X
attacks. The Tellabs 8600 system has multiple methods for
Two-port gigabit Ethernet 1000Base-X
protecting against such attacks. For instance, the system can
relieve the effects of a possible disturbance by dynamically Eight-port gigabit Ethernet 1000Base-X
restricting the traffic traversing an element. Additionally, all of the 2+6-port (2 x 1000Base-X + 10/100/1000Base-TX) Ethernet
incoming and outgoing traffic in an element can be filtered using a combo module
hardware based access control list (ACL) that is defined by the Eight-port STM-1/OC-3 POS
system administrator. The system administrator can also restrict the
number of routes propagated by the routing protocols learned from Four-port STM-4/OC-12 POS
the VRF tables. One-port STM-16 POS
One-port STM-16/OC-48 POS
Interface Module Concentrator Four-port STM-1/OC-3 ATM
For the Tellabs 8660 and Tellabs 8630 switches, the Interface Eight-port chE1/chT1 Multiservice
Module Concentrator is a universal baseboard for all LCs. As shown 24-port chE1/chT1 Multiservice
in Figure 27, the IFC can be equipped with two Interface Modules
One-port chSTM-1/chOC-3 Multiservice
to form a line card. The IFC is 28 mm wide and can hold any two
IFMs from the range available. The line card can then be placed in The platform is open for broadening to new interface types, which
any available Interface Module slot in the network element. The are added on the basis of customer requirements. All of the optical
Tellabs 8620 switch can also be configured with two IFMs that are Interface Modules can be equipped with standard SFP (Small
plugged directly into the fixed module slots of the network element. Form-Factor Pluggable) connectors, responsible for transmitting and
receiving the optical signals. This modularity means that interfaces
The advantage of this mechanism is that there is no need to buy
can be upgraded when needed and supports a pay as you grow
different types of line cards for each service. Use of a single line
approach.
card type reduces the total quantity of spare parts that must be
held in inventory and simplifies the service providers field Multiservice interfaces offer further flexibility for the service provider
operations. since a single interface can be configured to carry a mixture of
protocols.
24
basis in each network element. The LSPs created with the LDP standards for quality and reliability. Obviously, any service protection
protocol are never subjected to CAC. has to be justified on a cost/benefit basis, so networks are usually
Support for Strict Priority and WFQ scheduling enables efficient built with a mixture of various protection mechanisms to best match
delivery of real-time, premium data and Best Effort services in a the individual service requirements. The Tellabs 8600 system can
single network. With advanced traffic conditioning features such meet even the most demanding service requirements through a
as policing and shaping, it is possible to define CIR, PIR, CBS mixture of element-level resilience and network-level protections.
and PBS settings for each service. In fact, CAC combined with In the Tellabs 8600 system, all of the internal buses through the
priority-based queuing forms the key component for hard QoS. backplane are protected. These include power, battery and auxiliary
voltage, as well as synchronization buses. The backplane is passive,
which means that it is highly reliable. The data links between all of
the line cards are also duplicated, providing two serial buses
between each card.
The slot for the CDC can be protected by equipping the chassis
with two CDC cards. When the unit is thus protected, both the DC
feed for the element and the synchronization are protected, in
addition to the control plane functionality. When one of the two
units is in active mode, the other is in passive or standby mode.
However, the standby unit holds identical information to the active
one. The software continuously controls the state of the units and
dynamically makes changes if needed. Any changes made do not
affect the data traffic flow. The CDC includes graceful restart
mechanisms for protocols such as OSPF, BGP, BGP with MPLS
labels and LDP. These mechanisms are critical for service provider
networks that carry services with high availability requirements.
Graceful restart helps to minimize the impact of a routing protocol
failure on traffic forwarding; the forwarding plane continues working
for a certain time even though there is a problem in the control
Figure 28. Scenarios for QoS implementations in wireless networks
plane.
All cards in the network element are hot-swappable. When a card is
As shown in Figure 28, a service provider utilizing the Tellabs 8600
changed and replaced with an equivalent one, all of the original
system can use either L-LSPs or E-LSPs to carry differentiated
parameters are automatically copied to the new card. It is also
service classes through the network. Either LDP or RSVP-TE can be
worth noting that a failure in a single line card in the system does
used to signal the LSP through the network. The Tellabs 8600
not have an impact on any other traffic in the network element. The
system supports both L LSP and E-LSP signaling. The Tellabs 8600
control unit maintains up-to-date information on all of the
system is able to forward traffic on the basis of traffic class to the
parameters of the line cards, which can be requested when
correct LSPs.
needed.
When E-LSPs are used, multiple traffic classes can be carried over
For network protection, the Tellabs 8600 system supports both link-
the same LSP. The service provider may decide to carry certain
and MPLS level protection to provide very fast recovery times. At
traffic classes in one E-LSP and others in a different E-LSP, which
the lowest level, the Tellabs 8600 system elements support
can mean that not all E-LSPs in the network are equal. For
Multiplex Section Protection (MSP) for SDH interfaces. With MSP,
instance, traffic classes for data traffic may be carried in one E-LSP
one line is reserved for protecting an identical line. This method is
and all delay-sensitive traffic in another E-LSP.
called MSP 1+1 or APS protection and provides very fast SDH-layer
LSPs can be provisioned automatically with the Tellabs 8000 protection with less than 50 ms of switch-over time. MSP 1+1 and
manager. The Tellabs 8000 manager supports automatic updating APS protection options for SDH interfaces are enhanced with
of the LSPs in the service provisioning process. If the LSP for the equipment protection. In practice, this means data travel via an
required traffic type already exists, its bandwidth can be increased interface on a separate line card to the one offering the protected
if so required. This simplifies the workflow and reduces the number connection. With Ethernet interfaces, link aggregation can be used
of errors possible in the service provisioning phase. Manual route to provide two basic benefits. Firstly, it can be used to increase the
set-up is allowed also. If resource reservations are not needed or link capacity by combining several physical Ethernet links to form a
the traffic-engineered paths are not available, the LDP can be used higher-capacity link bundle. Secondly, if one of the links in the
for setting up the path. When explicit resource reservations are Ethernet bundle fails, the traffic can automatically be transported
required and Traffic Engineering is enabled, LSPs should be over the remaining links.
provisioned using RSVP-TE. LSPs over the core network can be
LSP protection can be implemented in several ways supported by
provisioned with the Tellabs 8000 manager in a similar fashion.
the Tellabs 8600 system:
Again RSVP-TE is used when resource reservation is needed.
RSVP-TE-based 1:1 LSP protection
The Tellabs 8600 system platform has been designed from the BFD-based 1:1 LSP (IETF) protection
outset to maximize network reliability and to conform to SDH Which is the best protection mechanism depends on the
25
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
interoperability requirements as well as on the required network displayed graphically in the Network Editor tool of the Tellabs 8000
availability. The RSVP-TE-based protection enables an approximate manager. This information can be used for Traffic Engineering
switch-over time of 400 ms to three seconds for the selected LSP in purposes for LSPs routed through the Tellabs 8600 system and
the network. The other three alternatives are capable of meeting the third-party network elements.
standard SDH 50-ms switch-over time.
Path protection based on RSVP-TE is implemented using RSVP Route Reflector
Hello messages, providing a 1:1 protection mechanism. This means
Route Reflector functionality is used to improve the scalability of the
that in normal circumstances the traffic is only sent along the
BGP routing protocol within an autonomous system. Instead of all
working LSP. If a failure is detected, the traffic is forwarded to the
routers in the AS running BGP forming a full mesh of iBGP sessions
protecting LSP. The switch-over time in this case is highly
with each other, each BGP router creates a session to the Router
dependent on the frequency of RSVP Hello messages sent between
Reflector, which reflects the BGP advertisements received from one
the end-points of the protection group.
of the routers to all others. One of the BGP routers in the AS can
MPLS-OAM-based 1+1 LSP protection uses MPLS OAM packets, function as a Route Reflector. Additionally, the Tellabs 8000
which are sent at a given frequency over the LSPs. Transported manager system offers the unique possibility of dedicating a
traffic is sent to both LSPs simultaneously, and the receiving end standalone Linux-based server to operation as the Route Reflector.
selects the best source. The OAM packets inform the remote end This solution can increase the BGP scalability further by enabling
about the prevailing path conditions. The OAM packet sending flexible upgrades in the processing performance of the Route
frequency can be set by the service provider. When a 10-ms Reflector without reconfiguration of the traffic-carrying network
frequency is used, a 50-ms switch-over time can be achieved. A elements.
lower OAM packet frequency results in a longer switch-over time.
The benefit with this model is that the intermediate nodes do not
take part in the protection mechanisms. When the working and
protecting LSPs are terminated by different line cards in the same Network management system
element, protection is provided also against the potential failure of
Network and connection management are becoming more and
one line card.
more important in todays networking world. The ability to manage a
Bidirectional Forwarding Detection (BFD) is a protocol that can complex and large network with limited non-specialized resources is
detect faults in the bidirectional path between two forwarding essential for service providers. An efficiently designed management
engines. It operates independently of media, data protocols and system can help to streamline processes and can shorten service
routing protocols. One potential application of BFD is to monitor the delivery and repair times considerably.
availability of an MPLS LSP. As such, BFD is a lightweight protocol
The network management system for the Tellabs 8600 system
that can be used to detect a data plane failure in the forwarding
follows the same ideology as the widely used and well-received
path of an MPLS LSP.
Tellabs 8100 system. The Tellabs 8000 manager is a single
platform that can manage both Tellabs 8600 and Tellabs 8100
Management Plane systems network elements, as well as the Tellabs 6300 system
All of the elements of the Tellabs 8600 system solution implement a network elements. This service-oriented network management
full range of SNMP MIBs and support command-line interface (CLI) system is one of the most important parts of a Tellabs solution. It
network management applications as well as the GUI-based has been designed on the basis of extensive operation experience
Tellabs 8000 Network Manager. However, within the Tellabs 8600 and customer feedback gained with the Tellabs 8100 systems
system solution, the Broadband Management Protocol (BMP) is previous network manager software. It allows customers with
used for communications between the Tellabs 8000 manager and Tellabs 8100 and Tellabs 6300 systems network elements to
the elements. BMP was chosen for its scalability, security and continue to use the same management system, which has been
flexibility. extended with new tools for newer applications. The key benefits of
this graphical-user-interface-based system are ease of use,
The software architecture allows simultaneous use of the different scalability and reliability.
management interfaces: SNMP, CLI and BMP. Several concurrent
Telnet or SSH sessions can be made to a single element. Both Each service type is managed with its own optimized tool. Links
Ethernet and serial interfaces are available on the CDC for local between the tools are designed so that operations staff can handle
management access of each network element. The Ethernet complex tasks without the need for a deep understanding of the
interface can also be used to build an external management network or the management structure. The system has been
network where required. The management plane is protected purposefully designed for ease of use by hiding the complexities of
whenever the CDC is duplicated for redundancy, which is typically the network behind a service-driven point-and-click interface. In a
the case. traditional management environment, setting up each new service
often requires extensive configuration of every network element
involved in the delivery of the service. With the Tellabs 8000
Online Core Network Monitoring manager, simple actions are translated into a series of commands,
Online Core Network Monitoring enables the partial management of which are then sent automatically to all relevant network elements.
third-party network elements in the same management domain with This enables very fast, lower error operations without the need for
Tellabs 8600 system elements. It collects information on network in-depth understanding of the underlying technology.
topology and capacity reservations by means of the OSPF-TE As shown in Figure 30, the normal CLI has been replaced by a
routing protocol. The topology and bandwidth information is then graphical user interface (GUI). This enables service providers to
26
Figure 29. Easy-to-learn, simple-to-use management system
focus their valuable expertise on the more challenging operational In addition to managing Tellabs elements, the Tellabs 8000
issues. The tools and applications can be launched by operators at manager also collects information on the operation and topology of
remote workstations. In this case, highly customizable user the core IP network elements for monitoring purposes. This allows
privileges determine the rights of each operator. the service provider to view the network structure as a unified
entity. With this view, the personnel can understand the network
status and identify any possible bottlenecks that could affect
service delivery.
27
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Fast troubleshooting with proactive and accurate fault applications or modules. Network management users can select
identification maximizes network availability. from these only the ones they need.
A single management solution for the Tellabs 8100, Tellabs 6300 The cornerstone of the system is the Basic Package, which contains
and Tellabs 8600 system platforms is complemented with all of the tools for planning and building the network, as well as for
external products from e.g. 3rd party mobile vendors. Support for element management. The element management tools include all
TDM, ATM, FR, IP and Ethernet technologies provides an easy functionality that is required for monitoring or configuring elements
upgrade path from TDM to IP. and their components in a Tellabs 8600 system network. It provides
Provisioning can be handled by fewer operators since no special tools for element configuration and element-level fault and
in-depth technology knowledge is needed. The advanced performance management. In addition, tools for user privilege
graphical user interface enables fast operations and is easy to management, customer information management tools and the
learn. The system includes comprehensive online help to support online help system are included in the Basic Package. All of the
the users. functionality is provided via a graphical user interface.
A significant amount of time is saved over the command-line In addition to the Basic Package, there are a number of network
approach, especially for large networks. The number of errors can and service level management applications. With the provisioning
be reduced dramatically through the use of automated tasks and and testing applications, the operator can configure, test and
service templates. monitor all of the services and connections in the network on an
end-to-end basis. Each service and connection can be tested
A central database is maintained by the system and is updated in
before it is put into active use. The fault and performance
real time with modifications made by multiple users using
information can be viewed at the service level, which helps the
different tools. A consistency check is made between the different
operator to respond quickly to customer issues. All of these end-to-
network elements. The database notifies the user of any mistakes
end management tools enable an operator to reduce the number of
and so prevents faulty configuration data from being entered.
steps and the risk of errors in the service delivery phase. This can
Service definitions need only be specified at the top level. The have a direct effect on delivery time and customer satisfaction.
system automatically handles all of the complex element
configuration work. Templates make it easy to learn and use
these processes. Using the Tellabs 8000 manager
More effective Traffic Engineering can be achieved through The basic design principle of the Tellabs 8000 manager is that all
network virtualization. Network elements, links and even services actions can be planned ahead of time. They are then implemented
can be simulated in the database without updating of the physical when the hardware is available, and activated when needed. Once
hardware involved. This allows different network planning options deployed, the services can be tested to confirm that they are
to be analyzed. For example, the effect of a new service on functioning properly. The activation of an element automatically
network congestion can be modeled without any actual changes triggers the monitoring function. The following sections illustrate
to the physical network. how the Tellabs 8000 manager assists with the daily operations and
service-related management tasks.
Fault and performance data are collected from network elements
and are associated with individual services and connections. The
overall state of a connection can be checked at a glance. The Service Provisioning Steps
fault management monitoring covers network elements, links The first step is to choose the service or connection end-points.
between the elements, network-wide parameters and the network The connection type can be multipoint-to-multipoint or point-to-
management system itself. point. Point-to-point connectivity is implemented as an MPLS
The entire Tellabs 8600 system based network devices, Pseudo Wire. This can carry Ethernet, ATM, TDM or FR traffic. The
configurations, services is automatically documented in the end-points are located in the interfaces/sub-interfaces of the Tellabs
Tellabs 8000 manager database. For example, service network elements. A sub-interface can be specified by a VLAN tag
configuration information is stored in the database when a service in an Ethernet interface or by an ATM VP/VC in an ATM interface.
or connection is provisioned. This is then kept constantly up to To speed up the operations, the operator can also create a number
date if any changes are made to the configuration. of Pseudo Wires at once. This group operation option applies also
The distributed architecture facilitates that there is no single point for connection end-point changes.
of failure. It also means that consistency is maintained between Once the connection is defined, the operator then specifies the
the physical network and its management. traffic constraints and traffic rate. The traffic constraints include
In summary, the Tellabs 8000 manager is designed to be quick to information about the traffic classification rules, QoS requirements
integrate, scalable and easy to use. It can deliver a reliably running and parameters for traffic shaping and policing. These traffic
network with simple service provisioning and monitoring. The constraints are then used to determine the DiffServ classification of
system is equally well suited for managing just the Tellabs 8100, the traffic, plus the routing and capacity reservations for the LSPs
6300 and 8600 system elements or for integration into the service assigned to the service.
providers wider umbrella management system. The next step is to set up the newly created connection or the
whole service. The service is first created only in the database,
using the Tellabs 8000 manager provisioning logic. The operator
System Components
can then check the results of this before actually implementing the
The Tellabs 8000 manager is a modular software system. The connection on the network hardware. If the connection operation
system functionality is divided into several, separately licensed fails for some reason, a descriptive error message is displayed to
28
Figure 31. Service provisioning tool window
To test the service or connection, the Packet Loop Testing tool can Service-level Fault Monitoring
be launched directly from the service provisioning window. Service
The Tellabs 8000 manager is designed to provide a coherent fault
testing is a logical step for ensuring that any newly provisioned or
monitoring structure that correlates equipment-level issues with the
modified services are working as expected. Testing at the service
specific services and individual connections involved. Element-level
level, including SLA-related parameters, is currently unique to the
monitoring information is mapped against each LSP and the
Tellabs 8600 system.
connections or services carried. This means that when an LSP goes
Once a service or connection is no longer needed, it can be deleted down, the operator has a complete picture of the equipment fault
from the network and from the Tellabs 8000 manager database in that has caused it and of the impact it has on services. This leads
a single operation. All configurations related to the deleted service to much faster fault resolution and allows the operator to react to
are removed from the network elements. the most critical service issues first. Service management allows the
operator to monitor faults for a group of objects as one service
Packet Loop Testing entity. The group can consist of, for instance, connections
terminating at a specific element, elements that are part of a special
End-to-end testing of services and connections is one of the most
network or have a special role, or trunks leased from another
important features of the Tellabs 8000 manager. A similar testing
service provider. This feature makes it possible to pay specific
tool, the Circuit Loop Test, is provided for TDM connections built
attention to certain parts of the network that could require more
with Tellabs 8100 system elements. The Packet Loop Test is made
attention or quicker responses.
possible by special test and loopback generators and analyzers that
are built into the hardware and software of the Tellabs 8600 system
network elements. Figure 32 shows the Packet Loop Test window in Performance Monitoring
which the tested service and results are displayed. In the Performance Monitoring component, an extensive array of
metrics related to the performance and traffic characteristics of the
The Packet Loop Test tool provides answers to questions such as: links and LSPs is gathered from the network. The information also
includes class-based packet statistics to provide a higher-granularity
Does basic end-to-end connectivity exist between all or only
picture of network performance. The information collected is
some of the chosen end-points of the service?
normalized and stored in the database. The performance
What are the values for packet loss, delay and jitter (delay management GUI tool includes a basic set of reports that the user
variation) for the connection being tested? can generate. All stored historical data can be viewed with the tool,
Is the provisioned connection able to perform transfer at full for analysis of the most utilized links and LSPs in the network. This
bandwidth? helps the operator know when a link in the network needs to be
If necessary, the test can be configured to be performed upgraded. The graphical tool can be used also to monitor the
automatically for a specified length of time at a given interval. For performance of a link in real time when one is diagnosing problems.
29
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
With trend lining, the operator may use historical data to predict software versions that can significantly increase integration and
when some links in the network need to be upgraded. The maintenance costs. The Tellabs 8000 manager provides support for
performance data can also be exported to external systems for the Tellabs 8600, Tellabs 8100 and Tellabs 6300 systems network
further analysis. elements through a single northbound interface. This means that
The Performance Monitoring tool is very important in a packet- any element version dependencies are completely hidden by the
based environment, for keeping link utilization at acceptable levels. Tellabs 8000 manager. Therefore, each tool that is part of the
It is a key function for compliance with end-user Service Level Tellabs 8000 manager platform always has the latest information
Agreements. available.
Tellabs has many years of experience of integration with a number
of third party OSS systems, including Micromuse Netcool, Cramer,
Web Reporter
HP TeMIP, NetCracker, EliteCore and Servion. In addition, some of
Tellabs Web Reporter offers online information on the network and our customers have successfully integrated the platform with other
services through a standard Web browser (as illustrated in Figure vendors solutions, such as Orchestream and Concord.
33). The tool is easy to use for service provider personnel who need
to read current status information or obtain reports at various levels
concerning the Tellabs network. There are a number of predefined Management Solution Components
report formats that show the network information in HTML form. Figure 34 shows the management system, which consists of a
At the client end, no special tools are required, only a Web browser. number of servers and workstations connected to the same Local
In the network management network, instead a separate server is Area Network.
needed that gathers the information from the database part of the
Tellabs 8000 manager and converts it into the appropriate format
when the report request from the client is generated.
30
The management server runs the processing logic for the Tellabs Scalability
8000 manager tools, ensuring the proper ordering of all operational The Tellabs 8000 manager is designed to scale with the network
actions. The management servers can be duplicated to increase size, number of users and required management capabilities. The
network management system scalability and improve availability. Tellabs 8600 system is designed for use in large national and even
Operations staff can access the network management system from international networks, which may consist of tens of thousands of
workstations. Using the workstation, the operator can run all of the network elements, so network scalability is obviously a critical issue.
licensed tools for network design, element configuration, service End-to-end manageability for every single connection and service in
provisioning, service testing, fault monitoring and network the network is preserved as the network grows.
performance monitoring. The service provider can delegate the The Tellabs proprietary communication protocol BMP facilitates
operational responsibilities between different groups by flexibly minimal error network management operations since it provides
defining the privileges for each person or group concerned. very efficient communication between the network elements and
The number of workstations needed depends on the number of the management system. The BMP protocol is similar to the proven
concurrent users. Each can be connected to the management LAN DXX protocol, used for communication with the Tellabs 8100
directly or over a Wide Area Network. The workstations operate as system elements.
thin clients with the processing logic hosted centrally. The network As the number of people operating the network increases, it is
management system enables the operator to easily monitor and possible to add more workstations to meet the network
configure the network elements and their respective services. If management needs. The service provider can also install additional
communication is lost between the management system and the servers in the management network to add management capacity
network, these functions are suspended while the connections in or for redundancy. In the latter case, the additional servers can
the network are not affected. All settings in the network elements share the management load and make the system even more fault-
remain unaltered until communication with the network tolerant.
management system is restored.
The Tellabs 8000 manager software includes several optional
The management system for the Tellabs 8600 system is built on the applications, thus allowing service providers to choose the right set
basis of open, standard interfaces. These interfaces are also used of tools for their specific management needs. When a network is
for communication within the Tellabs 8000 manager. Open small or a limited number of services are provided, the service
interfaces also enable easier integration at several levels with the provider can start with the basic management functionality. As the
third-party management systems that a service provider may be service portfolio is enhanced or the network grows, a wider
using. selection of applications can be deployed.
If required, all of the Tellabs 8600 system network elements can be
monitored with SNMP-capable systems. Standard MIBs are
Security for Network Management
implemented in all devices. Configuration can be carried out via a
CLI also, if necessary. Whichever method is used, the system The protocol used to communicate with the Tellabs 8600 system
maintains consistency between the database and the Tellabs 8600 network elements can support very large networks and handle a
system network elements to provide that all information is up to vast amount of information. The management traffic uses the UDP
date. protocol at the transport layer. Since the management traffic is
mixed in with the live data traversing the network, it is important to
The Route Master is a separate network element that provides two
make sure that the management commands can always get
important functions the Online Core Network Monitoring and
through, even when the network is busy. This is facilitated by giving
Route Reflector as described earlier. The Router Master can be
the management traffic a very high priority.
configured to perform either both functions or only one of them. As
mentioned previously, any Tellabs 8600 system network element It is also essential to make sure that the management traffic and the
can also function as a Route Reflector. If the Route Master is used associated applications are accessible only to authorized personnel
as a Route Reflector, it should always be duplicated, regardless of who have the appropriate security clearance. The following security
network size, due to the criticality of its role. The Route Master features have been implemented in the Tellabs 8000 manager:
server operates on a Linux server platform. The service providers administrator can define the user lists and
Windows 2003 and UNIX are available for the database server. All specify the privileges for each user. Privileges can be assigned
of the process logic servers and workstations work in a Windows for, e.g., a certain application only. For each application it is
2003 environment. possible to further limit the information available or the rights to
run certain tasks.
The computers associated with the Tellabs 8000 manager can also
be installed in a Tellabs 8100 system network management No server or workstation software may be started without entry of
configuration. For a current Tellabs 8100 system network manager a valid username and password.
customer, the introduction of the Tellabs 8600 system and related Each user is authenticated upon login to the system. The login
management tools is a simple task. All network data can be and all subsequent management actions performed by the
integrated into a single database, with one tool used for monitoring operator are tracked and logged on the database server.
the network. All of the new tools can be run according to the same IPSec can be used to secure the connections between the
business procedures used with the existing workstations. network management system and the network elements.
31
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
32
Summary of product features Performance QoS functionality
The table below provides a summary of Tellabs 8660 switch: 93.6 Mbps DiffServ, DiffServ aware MPLS Traffic
functionality and products of the Tellabs Tellabs 8630 switch: 31.2 Mbps Engineering (RFC 3270 and RFC 3564)
8600 Managed Edge System. It should be CBR, VBR, UBR+ and UBR ATM service
Tellabs 8620 switch: 7.8 Mbps
noted that some parts of the system or categories
functionality listed below are not yet
ATM Forum Traffic Management 4.1
generally available, but are part of the Interface Modules
planned future development. L-LSP and E-LSP support for MPLS
Fast Ethernet, gigabit Ethernet,
multiservice ch. STM-1/OC-3c, Queuing for up to eight QoS classes per
multiservice ch. E1/T1, STM-1/OC-3c port for DiffServ traffic and 1000
Applications additional queues for user-selectable
POS, STM-4/OC-12c POS, STM-16/OC-
Transport for 2G and 3G Radio Access services (e.g., VLANs) per IFC
48c POS, STM-1/OC-3c ATM
Network with ATM IMA, ML-PPP, ATM Traffic classification based on protocol,
VP/VC switching and TDM cross- Possibility of using all Interface Modules
in the Tellabs 8660, the Tellabs 8630 source and destination address, source
connections at DS0 level and destination port and Type of Service
and the Tellabs 8620 switches
PWE3 tunnels (Ethernet, ATM, HDLC, FR, (ToS) field
TDM) Policing with Two Rate Three Color
IP VPN (RFC 2547bis) IP/MPLS protocols Marker
H-VPLS (Lasserre-Vkompella IETF draft) Static routing, OSPF-TE, IS-IS-TE, (MP)- Queue-based RED, WRED and tail drop
BGP4 (RFC 1771 and RFC 2858), LDP for congestion control
Broadband service aggregation
(RFC 3036), RSVP-TE (RFC 3209)
SP/WFQ scheduling
PIM-SM Ipv4 Multicast
Physical dimensions (W x H x D) Optional traffic shaping per queue
Tellabs 8660 Edge Switch: 440 x 600 x
Resilience
300 mm Management
Common logic 1+1 protection, hot-
Tellabs 8630 Access Switch: 440 x 230 x Element, network and service
swappable plug-ins (Tellabs 8660 and
286 mm management with Tellabs 8000 Network
Tellabs 8630 products)
Tellabs 8620 Access Switch: 440 x 88 x Manager
1+1 MSP (APS), 1+1 (MPLS OAM) and
280 mm CLI as an option for element configuration
1:1 (RSVP-TE or BFD) LSP protections,
Tellabs 8606 Ethernet Aggregator: 440 x Ethernet link protection SNMPv2 MIB support in network
44.5 x 300 mm elements
OSPF, BGP, BGP with MPLS labels and
Tellabs 8605 Access Switch: 440 x 44 x LDP graceful restart mechanisms
280 mm Power requirements
Synchronization 48-VDC power for the Tellabs 8660 and
Switching capacity Tellabs 8630 products
SEC/Stratum-3 timing module
Tellabs 8660 switch: maximum of 42 100 240 VAC or 48 VDC for the
External clock input and output
Gbps bidirectional switching capacity (12 Tellabs 8620 switch
IFCs each with 3.5 Gbps switching Synchronous Ethernet
Universal VAC or 48 VDC for the Tellabs
capacity) Adaptive synchronization 8606 aggregator
Tellabs 8630 switch: 14-Gbps IEEE 1588 Precision Time Protocol 48 VDC, 24 VDC or 100 240 VAC for
bidirectional switching capacity Clock distribution capability the Tellabs 8605 switch
Tellabs 8620 switch: 3.5-Gbps
bidirectional switching capacity
Environmental conditions
Tellabs 8606 aggregator: wire speed on
all interfaces, 12.8-Gbps switching matrix ETS 300 019-1-3 Class 3.2 (In use)
Tellabs 8605 switch: 300-Mbps NEBS GR-63-CORE (In use)
forwarding capacity
33
OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
34
PE Provider Edge SP Strict Priority
PHB Per Hop Behavior SPF Shortest Path First
PIR Peak Information Rate SPT Special Problem Type
PLT Packet Loop Test STM Synchronous transmission mode
PMA Prompt Maintenance Alarm TCP Transmission Control Protocol
POS Packet over SONET TDM Time Division Multiplexing
PPP Point-to-Point Protocol TE Transit Exchange
PSC PHB Scheduling Class TE Traffic Engineering
PWE3 Pseudo Wire Emulation Edge to Edge TED Traffic Engineering Database
QoS Quality of Service TLV Type length value
RAN Radio Access Network ToS Type of Service
RED Random Early Detection TTSI Trail Termination Source Identifier
RFC Request For Comments (IETF documents) UDP User Datagram Protocol
RIP Routing Information Protocol U-PE User-facing Provider Edge router
RNC Radio Network Controller VBRrt Variable Bit Rate real-time
RR Route Reflector VDSL Very High Data Rate Digital Subscriber Line
RSVP Resource Reservation Protocol VLAN Virtual Local Area Network
RT Route Target VoIP Voice over Internet Protocol
RT Real Time VPLS Virtual Private LAN Service
SDH Synchronous Digital Hierarchy VPN Virtual Private Network
1 x RTT Single carrier Radio Transmission Technology VPWS Virtual Private Wire Service
SEC SDH Equipment Clock VRF VPN Routing and Forwarding
SFP Small Form-Factor Pluggable WCDMA Wideband CDMA
SIP Session Initiation Protocol WFQ Weighted Fair Queuing
SLA Service Level Agreement WiMAX Worldwide Interoperability for Microwave Access
SNMP Simple Network Management Protocol WRED Weighted Random Early Detection
SONET Synchronous Optical Network XML Extensible Markup Language
35
36 OVERVIEW TELLABS 8600 MANAGED EDGE SYSTEM
Statements in this document pertaining to (a) future market or technological trends or developments, (b) future Tellabs products or features, (c) cost-savings, profitability or other
commercial or technological advantages arising from a product, service or technology, (d) possible network or system designs or configurations, or (e) other future, speculative or
forward-looking statements are for discussion purposes only, subject to change and shall not be construed as recommendations, guarantees or warranties (expressed or implied).
Results, outcomes or conclusions may differ.
North America Asia Pacific Europe, Middle East & Latin America &
Africa Caribbean
Tellabs Tellabs The following trademarks and service marks are owned by
One Tellabs Center 3 Anson Road Tellabs Tellabs Tellabs Operations, Inc., or its affiliates in the United States
1415 West Diehl Road #1401 Springleaf Tower Abbey Place 1401 N.W. 136th Avenue and/or in other countries: TELLABS, TELLABS and T symbol,
Naperville, IL 60563 Singapore 079909 2428 Easton Street Suite 202 and T symbol. Any other company or product names may
U.S.A. Republic of Singapore High Wycombe, Bucks Sunrise, FL 33323 be trademarks of their respective companies.
+1 630 798 8800 +65 6215 6411 HP11 1NT U.S.A.
2006 Tellabs. All rights reserved.
Fax: +1 630 798 2000 Fax: +65 6215 6422 United Kingdom +1 954 839 2800
74.1747E Rev. A 11/06
+44 870 238 4700 Fax: +1 954 839 2828
Fax: +44 870 238 4851