New MIMO and FDSW software
SBTS20B_ENB_0000_001458_000000.zip
Download: Click here
FDSW19 for FSMF
Download : Click here
2nd link : Click here
FDSW21 for ASIA/ASIB
Download : Click here
A plug-and-play (PaP) architecture to be applied for specification and execution of telecommunication systems functionality is presented. The architecture is based on a theatre metaphor. Plays define the functionality of the system. PaP components are realised by actors playing roles defined by manuscripts. An actor's capabilities define his possibilities for playing various roles. The usability of the architecture is validated through specification, implementation and testing of a PaP support system and a tele-school application demonstrator. A PaP support system that meets the flexibility and adaptability requirements and parts of the tele-school application has been implemented and validated. The implementation is based on Java RMI.
PaP components The entities in the system subject to PaP are the PaP components, which are real-world active hardware and/or software modules. These can be combined hardware/software modules with one or more external hardware interfaces, or pure software modules. These must interface with a software platform capable of running PaP application software. Pure hardware modules are not feasible in the context of dynamic PaP. PaP components will coexist with components that do not have the PaP functionality. These are denoted as non-PaP components. The properties of Functionality Class A, which are related to flexibility and adaptability require: 1) a system structure and functionality that is not fixed (adding, moving, removing components and changing component functionality according to needs and capabilities), 2) that new component, their external services capabilities and needs are found automatically (awareness of new components and capabilities, propagation of needed information about changes, propagation of needed new functionality), 3) a continuous adaptation to the environment and operation strategies/policies (new component functionality, new teleservices, new service and network management functionality, new policy functionality), 4) containment and aggregation. The functional object model to be defined in the following subsection aims to be a basis for satisfying these requirements.
