ADAMv2

Objectives

Alcatel Bell Space is a unique provider for key components (building blocks) of DVB-RCS hubs including:


  • The Return Link Processor (RLP), managing the slot allocations in the return link,

  • The Forward Link Encapsulator (FLE), performing Multi-Protocol Encapsulation (MPE) and generating static DVB-(RC)S signalling,

  • The SIT Drive (SDR), a tool for statistics collection and Rain Fade Mitigation,

  • The BMD (Burst Mode Demodulator),

  • The ATM Multiplexer (ATMMUX), which combines 10 OC-3 inputs into 2 OC-3 outputs.
The elements are integrated into a hub by the suppliers of a complete solution.

The ADAMv2 project aims to extend the features in the existing building blocks, as well as provide a new building block, AMCS, which will provide essential management and control functions within the hub.

The project outcome is an enhanced product line differentiated by:

  • Improved performance for large broadband access networks,

  • Sizeable offer to answer the need of small private networks,

  • The provision of standard interfaces to the hub from other components,

  • The high level of interoperability required by the network integrators and operators.

Challenges

For the AMCS, an integrated approach will be used, using uniform interfaces for all devices based on standard, open protocols like XML and SNMP. In that respect, common parts can be re-used throughout the devices.

For the QoS on the RLP, a performance scheduling algorithm needs to be implemented, which answers the stringent requirements for Real Time traffic in the return and is open for future enhancements that may be required by the outcome of the SatLabs process.

The Validation Test Bed will be flexible enough to host the tests of future new features.

Benefits

Reduced operational costs (OPEX): 
Operation has been made simple, keeping most of the complexity within the system: the operator can easily observe tendencies of resource usage thanks to the performance monitoring tool and he can easily apply measures to extend resources thanks to the resource management function. 

Increased customer satisfaction:
The operator has a efficient overview of the network status by using alarm and state monitoring. He is also capable of conveying data and real time traffic at the same time over the network, while the required system behaviour for each traffic type is guaranteed.

Open product management interfaces:
The use of harmonised interfaces, based on standard protocols, render the integration of Alcatel devices into other management systems quite easy.

Features

The hub management function, AMCS, will present the following features:


  • A framework to provide basic functionality (configuration management, alarm management, state management),

  • A toolchain to generate documentation and the code for common parts,

  • Value added functionality:


    • A GUI for Service provisioning (add/change/delete terminals, SLAs and multicast),

    • A GUI for performance monitoring,

    • A GUI for alarm monitoring,

    • A GUI for state monitoring,

    • A GUI for resource configuration (to allow the operator to manage his satellite resources).
The return link function, RLSS, will be enhanced with the following features:

  • Inclusion of the QOS mechanism, by handling RBDC requests and Channel_Ids,

  • Usage of a CRA Session Manager, to handle terminal request for duration-based CRA capacity,

  • Measurement of the system nominal Round Trip Time.
A validation Test Bed will be created in order to validate the current and future new features, and ensure long term support to customers.

Plan













BDR:September 2005
IPR:December 2005
MTR:March 2006
FR:July 2006

      

Current status

The project Kick-Off with ESA was held beginning of May 2005.

The BDR was successfully held mid September 2005, an Intermediate Progress Review was successfully held mid December 2005, and the Mid Term Review was successfully passed end of March 2006.

A final review was held held in September 2006 and the development work is now finished.

 

Contacts

Status date

Monday, March 10, 2008 - 11:13