Scrambler

Use Cases

Key Features

1 General information about the integration of SAIMOS Scrambler with Milestone XProtect^®

1.1      General workflow of the pixelation

Input stream –> SAIMOS Scrambler –> Output stream (RTSP, MPEG4)

1.2      Integration with Milestone XProtect^®

There are 3 different approaches:

1. Input (C3): Milestone (Protocol Integration) à Output: Milestone Universal Driver (1, 16, 64)
   1. An existing camera stream directly from Milestone is used as input for SAIMOS Scrambler. The output is then re-integrated as a virtual camera via the Universal Driver.
   2. The original stream is secured by advanced rights management of Milestone and only certain users can access the original stream.
   3. This is the option with the lowest latency due to the direct interfacing with Milestone XProtect
   4. Control of the scrambling (on/off) is possible via TCP commands (optional).
      

      ---

2. Input (C3 + Milestone): Camera (RTSP, HTTP) à Output: Milestone Universal Driver (1, 16, 64)
   1. In this variant the SAIMOS Scrambler retrieves the stream directly from the camera. Mostly the retrieved stream has a lower resolution (e. g. VGA). Additionally, the original high-resolution stream is recorded by Milestone. The output of the SAIMOS Scrambler is added to the Milestone system via the Universal Driver.
   2. The original stream is secured by advanced rights management of Milestone and only certain users can access the original stream.
   3. This variant can introduce latencies between the high-resolution stream and the scrambled stream as both are completely independent streams used by two different applications.
   4. Control of the scrambling (on/off) is possible via TCP commands (optional).
   5. This is the option with the lowest requirements regarding performance for the SAIMOS Scrambler and the Milestone XProtect Recording Server.
      

      ---

3. Input (C3): Camera (RTSP, HTTP) à Output: Milestone/Siveillance Universal Driver (1, 16, 64)
4. 1. In this variant the SAIMOS Scrambler retrieves the stream directly from the camera. Mostly the retrieved stream has a lower resolution (e. g. VGA). The output of the SAIMOS Scrambler is added to the Milestone system via the Universal Driver.
   2. There is no original stream without scrambling.
   3. Control of the scrambling (on/off) is possible via TCP commands (optional). Normally, if an alarm is triggered the scrambling is removed from the stream to ensure recording of the un-scrambled stream.
   4. This option has a high risk that information is lost in case of an emergency.

1.3      Performance

It is not possible to predict the performance of the SAIMOS Scrambler to 100 %. It depends on multiple factors like the size of the scrambling, the complexity of the scene and the chosen resolution (also input to output). The most performance of the application is consumed by the encoder. These are the general performance values:

• 800 Passmark with 360pà360p (1 Mbit),
  • 8×8 scrambling with 15 FPS, 25 % static scrambling
  • 30 – 80 MB RAM per channel
• 2100 Passmark with 720p à 720p (3 Mbit),
  • 16×16 scrambling with 15 FPS, 25 % static scrambling
  • 250 MB RAM per channel

For these performance values we assume a process with at least 4 real cores having a Single Thread Rating (by Passmark) of at least 2000 (mostly processors between 2.9 and 4 GHz). For pixelation we recommend to use a stream with low resolution as the most important details will be scrambled anyways. A scrambling of streams with more than 720p is not recommended by SAIMOS. The application is sandboxed and every channel runs as independent process on the OS. This means virtualization as well as multi socket system are perfectly possible and have no impact on performance of the SAIMOS Scrambler.

2 Dynamic Scrambling with SAIMOS Scrambler

2.1      Description

SAIMOS^® Scrambler is certified by an approved Austrian civil engineer and reliably scrambles moving objects and/or static areas within video streams. This functionality was developed to enable the protection of privacy in a monitored area.

SAIMOS^® Scrambler is configured via a user-friendly, browser-based interface with an appealing design. Automatic camera recognition and simple setup with polygonal shapes directly in the live video view enable basic configuration within a few minutes. SAIMOS^® Scrambler supports seamless integration with video management systems.

Use Cases

Key Features