Table of Contents
Advertisement
MC Encryption and Access Control
The APEX1000 architecture uses a custom encryption FPGA as its encryption engine. In
the SEM, MediaCipher
APEX1000 still uses MCs, which are used to generate the encryption keys, but the
actual packet encryption is done by two Encryption FPGAs.
Each FPGA can support the encryption of 24 full rate MPTSs (48 MPTSs in total). Using
this architecture, the APEX1000 is able to support the encryption of up to 768 services
across all 48 QAM outputs.
Encryption Algorithms
The APEX1000 supports several encryption standards and algorithms. These algorithms
operate at the packet scrambling level, and are compatible with any of the access control
modes that the APEX1000 supports. Each APEX1000 chassis may be configured for a
single encryption algorithm, which is then applied to all encrypted streams on that
chassis.
The supported encryption algorithms are:
•
DES (DCII)
•
DES (SCTE-52)
•
DVB-CSA
•
DVB-CSA SimulCrypt
Supported Encryption Types
The APEX1000 supports three encryption types:
•
Broadcast Encryption (BE) — This encryption type is used with traditional broadcast
services in Manual Routing mode.
•
Common Tier Encryption (CTE) — This encryption type is typically used for legacy
VOD in UDP Port Mapping mode, or Session-Controlled mode.
•
Session VOD Encryption (SVE) — This encryption type is used for encrypting VOD
services in Session-Controlled mode. (Only available in MHA SDV mode.)
In addition, the APEX1000 can take in services which have been encrypted by another
device (either pre-encrypted by an OLES, or encrypted by an upstream Network
Encryptor), and properly mux in those services to the appropriate output(s).
NOTE: The APEX1000 will not re-encrypt a service that has already been encrypted.
Overview • MC Encryption and Access Control
APEX1000 All-Purpose Edge QAM Software Version 2.4.x • Installation and Operation Manual
573408-001-a
®
(MC) devices are used to encrypt transport streams. The
B
20
Advertisement
Table of Contents
