The architecture of the ECI system is defined in the ECI specification ETSI GS ECI 001-1 [1]. The ECI system is
based on requirements as defined in the ECI specification ETSI GS ECI 001-2 [2]. The present document specifies the
core functionality of an ECI Ecosystem, including CA/DRM Container, Loader, Interfaces and Revocation details. A
major advantage and innovation of the ECI Ecosystem, compared with currently deployed systems, is a complete
software-based architecture for the loading and exchange of CA/DRM systems, avoiding any detachable hardware
modules. Software containers provide a secure ("Sandbox") environment for either CA or DRM kernels, hereafter
named as ECI Clients, together with their individual Virtual Machine instances. Necessary and relevant Application
Programming Interfaces (API) between ECI Clients and ECI Host ensure that multiple ECI Clients can be operated in
a secure operation environment and completely isolated from the rest of the CPE firmware and are specified in full
detail. The installation and exchange of an ECI Host as well as multiple ECI Clients is the task of the ECI Loader,
which initially is loaded by a chip loader. ECI Host and ECI Clients are downloaded via the DVB data carousel for
broadcast services and/or via IP-based mechanisms from a server in case of broadband access.