RCS system components must be suitably installed at both the operating center and, eventually, an Internet service provider. Typically divided in front end environments for all data collection, tapping and monitoring, and back end environment for data collection and backup.
The RCS server clearly separates activities in untrusted environment from those in trusted environment. The barrier limit is provided by a resident firewall.
Tapping data is collected in untrusted environment, eventually redirected to protect the addressee's identity (you) and sent to an information collector (Collector) and sent to the trusted environment via a specific service (Carrier). Remote entity status and settings are checked by a specific Collector machine component (Network Controller).
In trusted environment, evidence is managed, set and monitored (Master Node).
Lastly, RCS Console is a client that directly connects to Master Node. It can be installed on any computer to be used by the various RCS users.
Agents send collected data to the Collector. If communications fail, connectivity is down or the Collector does not work, agents can save a set amount of data until connectivity is restored. Data that exceed the admitted limit are lost.
If the Carrier cannot communicate with Master Node (disservice or maintenance in progress), received data is locally saved on the Collector until Master Node is restored. Once restored, data is automatically sent.
Master Node uses HTTPS digital certificates that guarantee communication security between Master Node, Collector and RCS Consoles.
Some agents require specific certificates that must be created and saved in folder
Worker service is installed with each Shard and decodes data before it is saved in the database. For distributed databases, each Shard has its own Worker that receives encrypted data from Master Node, decodes it and saves it in the database. The work load is automatically evenly distributed among all Shards in the same cluster.