User's Manual
Open Information
DESCRIPTION 16 ( 25 )
ERA/RGN/PD Jennie Bergström 5/1551-HRB 105 102/1 Uen
ERA/RKF/TU Carl Helander 2003-01-28 C
Prepared (also subject responsible if other) No
Approved Checked Date Rev Reference
E
• Presentation layer — holds the GUI, which consists of, for example, HTML
pages and Java applets. This includes work-flow oriented forms for
configuration of the system, support for reading and presenting the event
log, and so on. The presentation layer is implemented through web pages
and applets which run in a web browser on a PC or Unix workstation.
• Management adaptation layer — isolates the managed objects (MOs)
interface from the resource objects. The MOs contain read/write attributes,
and methods for operations on these objects. A MO may represent
an alarm/event generating object (for example, a plug-in-unit), and also
alarm/event handling objects such as logs and notification subscription
objects.
• Resource layer — hides the lower level implementation details of the MOs,
which reduces the impact of changes. The Resource Layer embraces
the Traffic Service Layer, Logical Resource Layer, Equipment Layer and
the Hardware Layer.
Fault detection functions in the resource layer, and also in the common platform,
ensure fault and error detection. The hardware layer within the resource layer
provides fault and error detection support on a low level. The management
adaptation layer and the common platform generate the corresponding alarms.
Events can have their origin in any part of the system, but the management
adaptation layer and the common platform generate the event reports.
5.2 Common Platform
The RNCs and RBSs are based on a Common Platform which consists of
modules including both software (such as programs that set up connections
and modify operating parameters) and hardware (such as processor boards,
switch boards, backplane connectors).
The C
¨
ommon Platform provides the following services to its application
programs:
Core
• Software execution platform
• Node O&M
• Java execution platform
• System upgrade during operation
• IP-routing for management
• Space switching of cells over multiple subracks within the node
• Database
• Loading of MP/BP, fundamental configuration and start/restart functions