TroiaDoc - ArmPods - Software - Concept
General
To achieve a modular architecture the software is split into several applications communicating via the TCP/IP protocol family. This allows the software to run on a single PC if possible or on multiple PCs if needed without redesigning.
Streaming Server
- on request, sends streams to Remote Arm Devices (audio and video, live and ondemand).
- on request, receives audio streams from Remote Arm Devices and redistributes them to on request to other Remote Arm Devices
Remote Arm Devices
- play video/audio produced in advance
- play video- and audio-streams from streaming server
- send audio stream to streaming server
- send position to tracking server, if this is needed by the tracking concept (will be most probably not, cause we will take UWB as an lokalization system here. tracking is done via tokens inside the arm-device and handled by an external application. the application (already done by ubisense) will send the tracking data to our tracking server or probably it will be the tracking server. needs to be elaborated. especially what kind of data (format?) we will get to process.
Control Software / ArmGui
- control of RemoteArmDevices
- loading of playlists
- editing of playlists
- direct control of the distinct components
- runs on PDAs
Tracking Server
- receives position dara from Remote Arm Devices, if this is needed by the tracking concept
- determines position data with help of tracking systems
- calculates several information from position data (e.g. Remote Arm Devices with greatest distance)