DMS – Device Manager Server
What is DMS?
(In our terminology device=media player=screen.)
DMS is a server application which is made to solve scalability (the system can handle more devices), poor network environments, and localized huge device clusters. The DMS sits between the master server (CMS – Content Manager Server) and the devices. A device can connect to the master directly or to a DMS, from it’s point of view there is no difference. This means you can freely move a device to a DMS anytime, but you have to know that there are some minor differences in the management.
Advantages of using DMS:
- The system can handle exponentially more devices. (Cloud and local DMS)
- Faster distribution of huge video files, contents, datasources to multiple devices under bad network environments. (With local DMS.)
Disadvantages of using DMS:
- Slight delay in some actions. (e.g. content assign, online-offline state change)
- Some minor features may not work. (e.g. preview template on device)
- DMS is durable and it updates itself but more components always means more management and maintenance cost (+installment and the hardware cost).
Common use case
Imagine you have a shop with 300 screens and all of them should play a video in synchronously. This means if you want to change the video all the 300 devices have to download it. On a 10Mbit/s internet a 4k video (let’s say 3GB) would take about 50 minutes to download. Now multiply it with 300. Our solution to this problem is to put a DMS inside the shops network and connect all the devices to it. The DMS will start to download the video the moment you upload it to the master server. After the download is complete and the new video is assigned to the devices the DMS will trigger the content change and let the devices to download it inside a local network. This method will be much more efficient though the speed still depends on the network capabilities.