User guide

EDA System Design
94 1/1551-HSC 901 35/3 Uen C 2005-12-02
10.2 Determining the EDA System Functions
The basic EDA System functions are based on requirements to services,
service selection, and security. The actual EDA scenario must provide
these functions while observing the remaining system requirements such
as the chosen MDF deployment scenario and the network performance
requirements. The latter covers for example the number of subscribers, the
bandwidth allocation policy, scalability options, and redundancy
requirements.
The EDA System functions involve the following design considerations and
choices:
• Service Requirements - Each service is connected to the end-user
through a PVC and each PVC is connected to a VLAN through the IP
DSLAM. The end-user can have up to 8 PVC connections.
− Access to voice services can be offered and implemented as
traditional base band telephony (POTS) or as high quality
Telephony over IP (ToIP). Both services can be implemented and
offered simultaneously.
− Access to the Internet.
− Access to a LAN (LAN to LAN).
− Access to multimedia services, such as video.
• Service Selection - The EDA System allows each individual PVC to be
configured to use one of the listed access methods to create
associations between the end-user and the Services Provider:
− DHCP - which means that the IP address of the end-user
equipment is set dynamically by the Service Broker’s DHCP server.
− Using PPPoE, where a PPP session is created towards a BRAS.
This solution offers integrated options for authentication,
authorization and accounting via RADIUS.
− Using PPPoA, where the IP DSLAM converts the PPPoA user to a
PPPoE user creating a PPP session as described above.
− Static IP address, where the end-user equipment is assigned a
static IP address.
− Transparent LAN, which sets LAN to LAN transparency