Overview

This section should provide you an overview of the archicture of the FHoSS

The FHoSS implementation defines the Java version of three interfaces:

• The Sh interface, which can be used by application servers to access the HSS
• The Zh interface
• The Cx interface, wich is used to communicate with I-CSCF and S-CSCF

There is also an implementation of this interfaces which does a mapping of the interface functions to diameter based requests. The data objects used by the implementation where generated at build time. Code generation is based on the xml schema, found in the 3GPP specification for the related interface.

Core of the FHoSS is the HssDiameterStack. It uses the DiameterPeer to send requests to other entities and retrieves the requests and responses via CommandListener.

The operational data of the Hss is stored in a database. The Hibernate persistence framework was used to build a data access layer. That enables you to change the database system.

To manage and maintain the FHoSS, a web based management interface is provided. This as implemented using the servlet technology in combination with the Apache Struts Web framework. This provides a clear structure and seperation of logic and gui related tasks.

GUI

The GUI layer is used to manage and monitor FHoSS. The GUI is, as allready said, based on Struts. The implementation of the gui logic can be found at de.fhg.fokus.hss.web. The rendering is done by several Java Server Pages which can be found in src-web folder.

DAL - Data Access Layer

The Hibernate persistenc framework was used to build that layer. The related data classes can be found in the de.fhg.fokus.hss.db.model package. There you can also find the BO classes which provide additional service functionality to for the data classes.

Interface Layer

The interface layer describes the external behavior of the Hss. There are three interface specifications in there. They can be found in the de.fhg.fokus.hss.cx, de.fhg.fokus.hss.sh and the de.fhg.fokus.hss.zh package.

For each interface there is a direct implementation. For every method of the interface there is a related operation class in the op packages.

/**

---