ATM / MPLS / V5 / Broadband
Trillium ATM / MPLS / V5 / Broadband protocol software enables network equipment providers to build a complete suite of communication devices – from core network elements to customer premise equipment – in technologies such as ATM, MPLS, DSL, Cable Modem and Frame Relay.
Increasing demand for ubiquitous, instant access to data, voice and video have fueled the growth of broadband technology, which provides high bandwidth and user-selectable Quality of Service (QoS). User-selectable QoS means that a user application can specify the transmission delay, error rate and bandwidth requirements on a per-connection basis.
Years ago, Frame Relay technology met the high-speed data demand within backbone networks. Later, ATM became the technology of choice for transporting data, voice and multimedia traffic.
Today, ATM is gaining additional prominence at the edge of the network within customer premises environment. The main technologies driving this trend are DSL, 3G Wireless and VoIP. For example, ATM-over-DSL enables cost-effective broadband communications over existing copper local loops. In 3G Wireless, ATM provides the capabilities to enable multimedia broadband communication over the wireless infrastructure.
Similarly, an unparalleled surge in the popularity of the Internet and the need to transport IP traffic seamlessly over different types of broadband technologies have driven the definition of a new overlay control protocol mechanism known as Multi-Protocol Label Switching (MPLS) to enable high-speed switching over ATM, Frame Relay and Gigabit Ethernet backbones.
ATM
ATM is essentially a packet-switched network with fixed-size packets known as cells. These cells are switched based on a Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI). A connection in an ATM network is achieved by tying together a series of VPIs/VCIs at multiple interfaces. A basic ATM network consists of a set of ATM switches and Network Interface Cards (NICs) connected by point-to-point ATM links.
Trillium ATM protocol offerings can be divided into five categories:
- The Signaling protocol is used to establish the ATM SVC, consisting of the Layer 2 data link management protocol and Layer 3 signaling protocol.
- The Routing protocol is used to route an ATM signaling control message through the ATM network. The ATM Forum defines the PNNI for dynamic routing and the IISP for static routing.
- The Application protocol is used to map IP applications and legacy Ethernet/Token-ring over ATM. The Internet Engineering Task Force (IETF) defines CIP and PPP over AAL5. The ATM Forum defines LANE and MPOA.
- The Interface Management protocol is used to manage ATM links and register ATM addresses.
- Drivers for ATM chipsets enable the ease of integration.
ATM Network Architecture

ATM Solutions
Some of the architectural features of Trillium ATM solutions are:
- Extensive debugging/trace functionality
- Status and statistics information access, via the management interface
- Error-logging functionality
- Element control in the protocol software
- Q.93B Signaling Layer
- Q.SAAL Signaling Layer
- IME
- PNNI Routing
- PLOA
- AAL Driver
- ATM Convergence Driver
- MPC8260 Driver
- Motorola MPC860SAR Driver - AAL2
- Interworking Call Control
Trillium Q.93B Signaling Layer 3 supports
- UNI 3.0/3.1/4.0, Q.2931/Q.2971, IISP, and PNNI 1.0 signaling procedures
- Point-to-point and point-to-multipoint calls
- Virtual channel allocation
- Leaf-initiated join procedures
- ATM anycast and group addresses
- Proxy signaling, virtual UNI, and soft PVCs
- Partial decoding of signaling messages
- Fault-Tolerant/High-Availability (FT/HA), using the Q.93B Protocol-Specific Function (PSF)
- Signaling interworking using the Q.93B Protocol-Specific Interface Function(PSIF)
Trillium Q.SAAL Signaling Layer 2 supports
- Complete Q.SAAL1/Q.SAAL2 and Q.2110/Q.2130 procedures
- Error detection by selective retransmission
- Data retrieval by the local user
- Active or passive mode for the SAAL connection
- Multiple SAAL connections over the same ATM link
Trillium IME supports
- Complete ILMI 3.0/3.1/4.0 procedures
- Proxy agent procedures
- Auto-configuration procedures, including PVC
- Multiple variable bindings in a single SNMP PDU
- GetRequest, GetNextRequest, SetRequest, GetResponse, and Trap SNMPv1 PDUs
- Easy addition of new MIBs
- Periodic polling for keep-alive
- Flexible use of the VCCs
- Authentication and security features
Trillium PNNI Routing supports
- PNNI version 1.0 procedures
- Single- or multi-peer group models
- Inside and outside links; version negotiation; Hello protocol-over-inside or -outside links; physical links or virtual paths; ATM anycast; SVC-based RCC; SVC-based RCC Hello protocol
- Database synchronization upon startup using the neighbor peer-state machine
- PTSE flooding, aging, and refreshing
- PGL election procedure and capability
- LGN horizontal-link Hello protocol, and link and nodal aggregation
- Summarizing internal and external addresses
- DTL processing and generating, crankback and rerouting of calls, and reachable addresses
- Route catches (pre-computed and otherwise) to quickly look up popular destinations
- Using the Dijkstra algorithm with configurable optimization criteria for route computing
- Point-to-multipoint call topology tree for bandwidth-efficient call routing
Trillium PLOA supports
- IETF’s Classical IP over ATM (RFC 1577 and RFC 2225)-server and clients
- Multi-protocol encapsulation over ATM adaptation layer 5 (RFC 1483)
- MPOA Client (MPC), MPOA Server (MPS),LAN Emulation Client 2.0, LAN Emulation Services 2.0, and PPP-over-AAL5
- VC sharing among multiple applications using the LLC/SNAP encapsulation, to reduce VCC usage
- AESA (formerly NSAP) and E.164 format addresses
- UNI 3.0, UNI 3.1, UNI 4.0, and Q.2931 signaling
Trillium AAL Driver supports
- AAL5 implementation for MPC860 and MPC8260 processors
- Message mode operations
- Transmit and receive chaining
- Error detection during reassembly
- Maximum frame length of 1 to 65535 bytes
- Receive address filtering
- Programmable reassembly, time-out period selection for receive operations
- Up to 65534 virtual channels
- Cell scrambling for serial-mode SCCs
- Flexible configuration; that is, all the options for address matching, such as using an internal lookup table, external address compression, or CAM
- Loopback operation
The Trillium product line was the first to offer ATM Adaptation Layer 2 (AAL2), an ATM portable signaling software product that handles blocking, unblocking, reset and call routing based on the configured routing information. Its flexible APIs provide all the information required to allow the user application to manage resources and CIDs, as well as to allow user application-defined call routing during call establishment.
Trillium AAL2 supports
- AAL2 signaling procedures of Q.2630.1
- NNI-STC over MTP Level 3 (Q.2150.1)
- UNI-STC over SSCOP (Q.2150.2)
- Adding and deleting multiple AAL2 paths (ATM VCCs) between adjacent AAL2 nodes
- CID allocation
- Managing the AAL2 path
- Blocking
- Unblocking
- Reset - Call routing, based on the configured routing information
- Flexible APIs to provide all the information required to allow the user application to manage resources and CIDs, and to allow the user application-defined call routing during call establishment
- Provisioning multiple transport links between the adjacent AAL2 nodes, when the signaling transport is SAAL
Trillium Interworking Call Control supports
- Switching Call Control for Q.93B, B-ISUP, ISUP, and ISDN
- Voice Trunking Over ATM (VTOA) as specified in the AF-VTOA-0089 and AF-VTOA-0113 phase 1 ATM Forum specifications
- Interworking between
- B-ISUP (ITU) and ISUP (ANSI)
- B-ISUP (ITU) and ISUP (Q.767)
- B-ISUP (ITU) and ISUP (ITU)
- ISUP (ITU) and ISUP (ANSI)
- B-ISUP (ITU) and Q.930/Q.931
- Q.93B and B-ISUP
- Q.93B and Q.930/Q.931
- Q.930/Q.931 and ISUP - Enbloc and overlap signaling
- Distributed call processing
- Resource allocation and verification
- Flexible resource allocation algorithms
- Dynamic and static binding of resources
- Dynamic and static routing
- Connection Admission Control
- B-ISUP and ISUP maintenance procedures
- Call prioritization while routing
- Generating Call Detail Records
- Generating call flow traces
- Maintaining procedures for B-ISUP and ISUP
- Flow control at interface
MPLS
Trillium Multi-Protocol Label Switching (MPLS) software source code solutions enable end-to-end, high performance implementation of the MPLS standard across backbone networks. MPLS plays an important role in the routing, switching and forwarding of packets through the next-generation network to meet the service demands of network users.
MPLS is an emerging standard rapidly gaining acceptance by telecom equipment manufacturers, carriers and ISPs. MPLS addresses the “Four S” problem of achieving:
- Speed
- Security
- Scalability
- Service guarantees
MPLS initially grew as a way of improving the forwarding speed of routers; however, in today’s network, MPLS offers new capabilities for large scale, carrier-grade IP packet switched networks and optical networks.
MPLS is an accelerated data-forwarding technology using an identifier called label to identify, classify and forward data. A label is appended/swapped to the packets that traverse through an MPLS domain. Once that packet reaches the destination edge of the network, the label is stripped away. The MPLS protocol derives its performance by simply switching labels on packets within the network.
MPLS is an efficient way of integrating IP and ATM networks. It allows high-volume IP traffic to traverse core ATM infrastructures. It also allows the QoS provided by ATM be visible at the IP level. Traffic Engineering and Virtual Private Networks (VPNs) are some of the applications that can harness the MPLS technology.
MPLS network devices are called Label Switched Routers (LSRs), and are classified as Label Edge Routers (LERs), operating at the edge of the network, and Label Core Routers (LCRs), operating in the core of the network. LCRs may commonly be called LSRs.
In a MPLS network, the path that a data packet uses to reach its destination is referred to as the Label-Switched Path (LSP) and the distribution of labels within the MPLS domain is carried out by the signaling protocols such as LDP/CR-LDP or RSVP-TE.
Trillium MPLS enables a new era of IP services and integration between IP and ATM networks, combining the benefits of IP routing with the advanced traffic management provided by an ATM core.
MPLS Stack Diagram

MPLS Network Architecture

MPLS Stack Components
The core MPLS components can be broken down into the following parts:
- Label Distribution Protocol (LDP)
An IETF standard signaling protocol for establishing and releasing Label Switched Path (LSP) and for label distribution. - Constraint-based Routing Label Distribution Protocol (CR-LDP)
An extension to LDP to support constraint-based routing and QoS in a MPLS network. - Resource Reservation Protocol – Traffic Engineering (RSVP-TE)
An enhancement of RSVP to support MPLS in terms of establishing and releasing Label Switched Path (LSP) and distribution of labels. RSVP is a protocol for reserving network resource to provide QoS.
- Generalized MPLS (GMPLS)
Extends the MPLS control plane to encompass time-division, wavelength and spatial switching. GMPLS is defined for network to network interface in an optical domain, that is the interface between the cross connects. Extensions to MPLS signaling protocol, such as RSVP-TE and CR-LDP, is defined to support it. - Optical user to network interface (O-UNI)
Where the user side is the packet switch network and the network side is the optical network. Extension of MPLS signaling protocol, such as CR-LDP and RSVP-TE, is defined to support this interface. - TCP/UDP Convergence Layer (TUCL)
A Trillium generic software layer that provides transparency to the underlying TCP/UDP/IP stack interfaces and enables portable implementation of TCP/UDP/IP applications such as MPLS.
MPLS Solutions
The Trillium MPLS solution implements LDP, CR-LDP, RSVP-TE, O-UNI and GMPLS protocols to set up and delete Label Switched Paths (LSP) and distribute labels. Trillium MPLS can work with any operating system, routing module, resource manager and forwarding engine.
Trillium MPLS supports:
- Label management
- Conservative or liberal label retention
- Request of Control-driven label bindings
- Basic and extended discovery mechanisms
- Downstream on Demand and Unsolicited label distribution
- CR-LDP
- RSVP-TE
- O-UNI (coming soon)
- GMPLS (coming soon)
- Label stacking
- Loop detection
- Load balancing
- LSP tunnel creation
- Stream merging
- Stream aggregation
- MIB support for LIB and FIB
Frame Relay and Frame Relay/ATM Interworking
Frame Relay is a protocol standard for LAN internetworking which provides a fast and efficient method of transmitting information from a user device to LAN bridges and routers.
Trillium Frame Relay Control Protocol (Q.933/LMI) provides status signaling for PVCs (LMI) and/or signaling to establish, maintain and release SVCs (Q.933). It supports UNI (user and network side) as well as NNI procedures (X.76). LMI provides procedures to maintain and manage PVCs. It provides auto detection of remote LMI protocol and support for multiple variants, Q.933 Annex A, ANSI Annex D., Q.933 Annex A-Bidirectional, ANSI Annex A-Bidirectional, and Gang of Four. It supports ANSI, ITU-T and Frame Relay Forum specifications, and it interworks with Trillium Frame Relay Data Link (Q.922) product.
Trillium Frame Relay Data Link (Q.922) provides core Frame Relay functions and/or control protocol for reliable transmission of frames (LAPF). It provides traffic and congestion management, DLCI switching, multicast and RFC 1490. It supports user and network side procedures, and ANSI, ITU-T and Frame Relay Forum specifications, including FRF.12. It interworks with Trillium Frame Relay Control Protocol (Q.933/LMI) and Frame Relay/ATM Interworking products.
ISDN
Integrated Services Digital Network (ISDN) enables transmission of voice, data, video and graphics at high speeds over standard lines. ISDN provides a single common interface with which to access digital communications services while remaining user-transparent. ISDN may be transmitted via the PSTN, packet-switched networks, telex, CATV networks, etc.
Trillium Q.930/Q.931 software supports the signaling protocol to establish, maintain and release circuit-switched connections across an ISDN network. It may act as user and/or network side.
Trillium Q.930/Q.931 software supports Basic Rate Interface and/or Primary Rate Interface, and ITU-T, AT&T 4ESS, AT&T 5ESS, Northern Telecom DMS-100, DMS-250, National ISDN-1, National ISDN-2, ETSI, VN2, VN3, 1TR^, NTT, Australian Telecom, TR-303, GR-303, Q.SIG and other variants. It also supports Fault-Tolerant/High Availability functionality utilizing an active/standby architecture.
Trillium LAPD software supports the LAPD link-level protocol. It may act as user and/or network side and supports TEI management procedures, ITU-T and other variants.
Trillium LAPB and LAPD software support LAPB and LAPD link level protocols. They may act as user and/or network side. They support TEI management procedures, ITU-T, ISO and other variants.
For information about Trillium ISDN over ATM Convergence Layer, please refer to the ATM product group within the Trillium Broadband category.
V5
Trillium V5 protocol software is used for connecting an Access Network (AN) to a Local Exchange (LE). It is used for:
- ISDN basic rate access
- ISDN primary rate access (V5.2)
- Analog telephone access
- Other analog or digital accesses for semi-permanent connections without associated outband signaling information
Trillium V5-LAPV supports the LAPV link level protocol used in V5.1 and V5.2 interfaces to establish and release multiple frame operations. It may act as Local Exchange and/or Access Network.
The Trillium V5-Envelope Function supports the V5 Envelope Function for the V5.1 or V5.2 interface. It includes support for the LAPV envelope function, mapping function and AN Frame Relay function.
Trillium V5 Layer 3 supports the V5 Layer 3 protocols to establish, maintain and release connections across a telephone network using the V5.1 or V5.2 interface as well as manage and control ports and links. It includes:
- V5/1V5.2 PSTN Protocol
- V5.1/V5.2 Control Protocol
- V5.2 Bearer Channel Connection Protocol
- V5.2 Protection Protocol
- V5.2 Link Control Protocol
Trillium V5 Layer 3 also includes the System Manager used to manage and coordinate activities of the V5 protocols and resources and may act as an Access Network and/or Local Exchange.
Protocols
TRILLIUM BROADBAND SOFTWARE
Signaling
SS7-related
FR: Frame Relay
- Q.933/LMI - Local Management Interface
ISDN: Integrated Services Digital Network
- LAPD - Link Access Procedure D
- Q.930/Q.931
MTSS: Multi-Threaded System Services
- Linux MTSS
- Solaris MTSS
- VxWorks
- Windows NT MTSS
- Software Development Kit (SDK) for MTSS
V5
Contact Us
Please use the form below to contact us and learn more about the Trillium ATM / MPLS / V5 / Broadband protocol software.
