User's Manual
Open Information
DESCRIPTION 13 ( 20 )
EAB/RWB/ZG Christina Wilson 18/1551–HRB 105 102/1 Uen
EAB/RWB/Z (Dennis Radenholt) 2003-06-16 B
Prepared (also subject responsible if other) No
Approved Checked Date Rev Reference
E
• The application program layer is the software executing on top of the
common platform. So, from the platform point of view, there is no specific
structure for the application program.
Traffic Control View
This view hides the specific RBS hardware from the actual services supplied
by the RBS. This is done to encapsulate the parts of the system that change
when hardware is modified. Modification normally takes place when an RBS
is updated (for example, capacity increase) or when different types of RBSs
are supported.
There are four layers in the traffic control view:
• Traffic service layer that carries out the application program procedures
using logical resources, for example, channels.
• Logical resource layer that provides logical resources for the traffic service
layer. It transforms operations on logical resources into operations on
devices.
• Equipment layer that makes functionality hardware independent by
providing devices to logical resource layer.
• Hardware layer that hides the hardware details.
Management View
The management view covers the application program and the common
platform. It hides implementation details from the user interface.
There are three layers in the management view:
• The presentation layer holds the GUI, which consists of, for example, HTML
pages and Java applets. They include, for example, workflow-oriented
forms for system configuration and support for reading and presenting an
event log. The presentation layer is implemented using web pages and
applets, which can be viewed using a standard web browser.
• The management adaptation layer represents objects visible through the
Mub management interface. These objects contain attributes, that can
be read or written, and methods for operations on these objects through
the standard web browser.
• The resource layer hides the lower level implementation details of the
objects, which reduces the impact of changes.
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. However, it has
no direct interface to the management adaptation layer. 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.