Filter
Top Products
9Alcatel-Lucent 5580 Home Network Manager
Managing New Devices on the Fly
The Alcatel-Lucent 5580 HNM can
manage new device types or releases
on the fly. For that purpose, you can
simply load the object model of the
device in an XML form. The Alcatel-
Lucent 5580 HNM will take over
management of the device with no
need for further adaptation.
Interaction in Your
OSS Environment
The Alcatel-Lucent 5580 HNM pro -
vides a northbound interface to com -
mu nicate with higher level OSSs. This
interface is implemented through a set
of high-level primitives covering serv -
ice provisioning, device configuration,
software management, etc. These
primitives provide a powerful means
for OSS applications to perform
management operations on one or
several devices with a single command.
System Architecture
The Alcatel-Lucent 5580 HNM has
been developed as a J2EE application,
making it independent of the under -
lying operating system. The Java
Virtual Machine shields the applica -
tion server from the underlying hard -
ware. The Alcatel-Lucent uses BEA
WebLogic, but owing to the use of
J2EE, it can be easily adapted to other
middleware systems (e.g., Jboss).
Hibernate provides the same inde -
pendence for the database technology
and enables smooth migration from
Oracle to any other database system.
Zero-Touch Activation Processes
(All processes are fully automated; no customer or operator intervention)
Initial Device Status
(Factory pre-provisioning)
Default Credentials
Default Credentials
Unique Credentials
(User name, password,
management system URL)
Process Highlights
Set Unique Credentials
Configure Device for Service
Set Unique Credentials
Configure Device for Service
Configure Device
for Service
Pros
Devices Configured on the Fly
Support for Customer
Self-Ordering
Device Configured
on the Fly
Limited Upfront OSS
Adaptations
Cons
Need Upfront OSS
Adaptations
Need Upfront OSS
Adaptations
Factory Pre-Provisioning
Implies Logistic
Challenge and Device
Delivery Lead Time
Customer Self-Serve
Zero-Touch
Zero-TouchPre-Provisioning
Figure 5. Multiple Device Activation Scenarios